diff --git a/.mtn-ignore b/.mtn-ignore new file mode 100644 index 00000000..a36f097b --- /dev/null +++ b/.mtn-ignore @@ -0,0 +1,6 @@ +env +pots +\.pyc$ +\.pyo$ +\.mo$ +~$ diff --git a/.tx/config b/.tx/config index 1d67b233..0e74a466 100644 --- a/.tx/config +++ b/.tx/config @@ -1,12 +1,60 @@ -[I2P.website] -source_file = ./messages.pot -source_lang = en -trans.de = i2p2www/translations/de/LC_MESSAGES/messages.po -trans.es = i2p2www/translations/es/LC_MESSAGES/messages.po -trans.fr = i2p2www/translations/fr/LC_MESSAGES/messages.po -trans.sv_SE = i2p2www/translations/sv/LC_MESSAGES/messages.po -type = PO - [main] -host = http://www.transifex.net +host = https://www.transifex.com +lang_map = ru_RU: ru + +[I2P.website_about] +file_filter = i2p2www/translations//LC_MESSAGES/about.po +source_file = pots/about.pot +source_lang = en +type = PO +minimum_perc = 2 + +[I2P.website_blog] +file_filter = i2p2www/translations//LC_MESSAGES/blog.po +source_file = pots/blog.pot +source_lang = en +type = PO +minimum_perc = 10 + +[I2P.website_comparison] +file_filter = i2p2www/translations//LC_MESSAGES/comparison.po +source_file = pots/comparison.pot +source_lang = en +type = PO +minimum_perc = 10 + +[I2P.website_docs] +file_filter = i2p2www/translations//LC_MESSAGES/docs.po +source_file = pots/docs.pot +source_lang = en +type = PO +minimum_perc = 1 + +[I2P.website_get-involved] +file_filter = i2p2www/translations//LC_MESSAGES/get-involved.po +source_file = pots/get-involved.pot +source_lang = en +type = PO +minimum_perc = 2 + +[I2P.website_misc] +file_filter = i2p2www/translations//LC_MESSAGES/misc.po +source_file = pots/misc.pot +source_lang = en +type = PO +minimum_perc = 10 + +[I2P.website_priority] +file_filter = i2p2www/translations//LC_MESSAGES/priority.po +source_file = pots/priority.pot +source_lang = en +type = PO +minimum_perc = 10 + +[I2P.website_research] +file_filter = i2p2www/translations//LC_MESSAGES/research.po +source_file = pots/research.pot +source_lang = en +type = PO +minimum_perc = 50 diff --git a/README b/README new file mode 100644 index 00000000..e6eae615 --- /dev/null +++ b/README @@ -0,0 +1,15 @@ +To run locally (for testing purposes): + +- Install proxychains, configure it for Tor + +- Pull in the dependencies: +$ proxychains ./setup_venv.sh +(you can also pull them non-anon by leaving out proxychains) + +- Compile translations (if you want to see them): +$ ./compile-messages.sh + +- Start the webserver: +$ ./runserver.py + +- Open the site at http://localhost:5000/ diff --git a/compile-messages-i2hq.sh b/compile-messages-i2hq.sh new file mode 100755 index 00000000..ff20d7ac --- /dev/null +++ b/compile-messages-i2hq.sh @@ -0,0 +1,13 @@ +#!/bin/sh +. ./etc/translation.vars + +export TZ=UTC + +if [ $# -ge 1 ] +then + pybabel compile -D $1 -d $TRANSDIR +else + for domain in $(ls $BABELCFG); do + pybabel compile -D $domain -d $TRANSDIR + done +fi diff --git a/compile-messages.sh b/compile-messages.sh index 819e4e81..8dddd6e3 100755 --- a/compile-messages.sh +++ b/compile-messages.sh @@ -1,4 +1,13 @@ #!/bin/sh -. ./translation.vars +. ./etc/translation.vars -TZ=UTC env/bin/pybabel compile -d $TRANSDIR +export TZ=UTC + +if [ $# -ge 1 ] +then + $PYBABEL compile -D $1 -d $TRANSDIR +else + for domain in $(ls $BABELCFG); do + $PYBABEL compile -D $domain -d $TRANSDIR + done +fi diff --git a/etc/babel.cfg/about b/etc/babel.cfg/about new file mode 100644 index 00000000..a8cc71cc --- /dev/null +++ b/etc/babel.cfg/about @@ -0,0 +1,2 @@ +[jinja2: **/pages/site/about/**.html] +extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension diff --git a/etc/babel.cfg/blog b/etc/babel.cfg/blog new file mode 100644 index 00000000..58f52396 --- /dev/null +++ b/etc/babel.cfg/blog @@ -0,0 +1,2 @@ +[jinja2: **/blog/**.rst] +extensions=jinja2.ext.autoescape,jinja2.ext.with_ diff --git a/etc/babel.cfg/comparison b/etc/babel.cfg/comparison new file mode 100644 index 00000000..e113121d --- /dev/null +++ b/etc/babel.cfg/comparison @@ -0,0 +1,2 @@ +[jinja2: **/pages/site/comparison/**.html] +extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension diff --git a/etc/babel.cfg/docs b/etc/babel.cfg/docs new file mode 100644 index 00000000..e37d7502 --- /dev/null +++ b/etc/babel.cfg/docs @@ -0,0 +1,2 @@ +[jinja2: **/pages/site/docs/**.html] +extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension diff --git a/etc/babel.cfg/get-involved b/etc/babel.cfg/get-involved new file mode 100644 index 00000000..2b9e70eb --- /dev/null +++ b/etc/babel.cfg/get-involved @@ -0,0 +1,2 @@ +[jinja2: **/pages/site/get-involved/**.html] +extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension diff --git a/etc/babel.cfg/misc b/etc/babel.cfg/misc new file mode 100644 index 00000000..ce64514f --- /dev/null +++ b/etc/babel.cfg/misc @@ -0,0 +1,2 @@ +[jinja2: **/pages/site/misc/**.html] +extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension diff --git a/etc/babel.cfg/priority b/etc/babel.cfg/priority new file mode 100644 index 00000000..6fbd837b --- /dev/null +++ b/etc/babel.cfg/priority @@ -0,0 +1,14 @@ +[jinja2: **/pages/blog/**.html] +extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension +[jinja2: **/pages/downloads/**.html] +extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension +[jinja2: **/pages/global/**.html] +extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension +[jinja2: **/pages/global/macros] +extensions=jinja2.ext.autoescape,jinja2.ext.with_ +[jinja2: **/pages/meetings/**.html] +extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension +[jinja2: **/pages/papers/**.html] +extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension +[jinja2: **/pages/site/*.html] +extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension diff --git a/etc/babel.cfg/research b/etc/babel.cfg/research new file mode 100644 index 00000000..59607bd9 --- /dev/null +++ b/etc/babel.cfg/research @@ -0,0 +1,2 @@ +[jinja2: **/pages/site/research/**.html] +extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension diff --git a/etc/multi-domain.patch b/etc/multi-domain.patch new file mode 100644 index 00000000..205f4275 --- /dev/null +++ b/etc/multi-domain.patch @@ -0,0 +1,115 @@ +--- env/lib/python2.7/site-packages/flaskext/babel.py 2013-07-13 00:00:00 +0000 ++++ env/lib/python2.7/site-packages/flaskext/babel.py 2013-07-13 00:00:00 +0000 +@@ -19,6 +19,7 @@ + from datetime import datetime + from flask import _request_ctx_stack + from babel import dates, numbers, support, Locale ++from gettext import NullTranslations + from werkzeug import ImmutableDict + try: + from pytz.gae import pytz +@@ -55,9 +56,11 @@ + }) + + def __init__(self, app=None, default_locale='en', default_timezone='UTC', +- date_formats=None, configure_jinja=True): ++ date_formats=None, configure_jinja=True, ++ default_domain=support.Translations.DEFAULT_DOMAIN): + self._default_locale = default_locale + self._default_timezone = default_timezone ++ self._default_domain = default_domain + self._date_formats = date_formats + self._configure_jinja = configure_jinja + self.app = app +@@ -77,6 +80,7 @@ + + app.config.setdefault('BABEL_DEFAULT_LOCALE', self._default_locale) + app.config.setdefault('BABEL_DEFAULT_TIMEZONE', self._default_timezone) ++ app.config.setdefault('BABEL_DEFAULT_DOMAIN', self._default_domain) + if self._date_formats is None: + self._date_formats = self.default_date_formats.copy() + +@@ -95,6 +99,7 @@ + + self.locale_selector_func = None + self.timezone_selector_func = None ++ self.domain_selector_func = None + + if self._configure_jinja: + app.jinja_env.filters.update( +@@ -142,6 +147,19 @@ + self.timezone_selector_func = f + return f + ++ def domainselector(self, f): ++ """Registers a callback function for domain selection. The default ++ behaves as if a function was registered that returns `None` all the ++ time. If `None` is returned, the domain falls back to the one from ++ the configuration. ++ ++ This has to return the domain as a list of strings (eg: ``['messages']``) ++ """ ++ assert self.domain_selector_func is None, \ ++ 'a localeselector function is already registered' ++ self.domain_selector_func = f ++ return f ++ + + def list_translations(self): + """Returns a list of all the locales translations exist for. The +@@ -178,6 +196,13 @@ + """ + return timezone(self.app.config['BABEL_DEFAULT_TIMEZONE']) + ++ @property ++ def default_domain(self): ++ """The default domain from the configuration as instance of a ++ `string` object. ++ """ ++ return self.app.config['BABEL_DEFAULT_DOMAIN'] ++ + + def get_translations(): + """Returns the correct gettext translations that should be used for +@@ -191,7 +216,10 @@ + translations = getattr(ctx, 'babel_translations', None) + if translations is None: + dirname = os.path.join(ctx.app.root_path, 'translations') +- translations = support.Translations.load(dirname, [get_locale()]) ++ locale = get_locale() ++ for domain in get_domains(): ++ dt = support.Translations.load(dirname, [locale], domain) ++ translations = dt if translations is None or not hasattr(translations, 'merge') else translations.merge(dt) + ctx.babel_translations = translations + return translations + +@@ -243,6 +271,29 @@ + return tzinfo + + ++def get_domains(): ++ """Returns the domains that should be used for this request as ++ `list` object. This returns `None` if used outside of ++ a request. ++ """ ++ ctx = _request_ctx_stack.top ++ if ctx is None: ++ return None ++ domains = getattr(ctx, 'babel_domains', None) ++ if domains is None: ++ babel = ctx.app.extensions['babel'] ++ if babel.domain_selector_func is None: ++ domains = [babel.default_domain] ++ else: ++ rv = babel.domain_selector_func() ++ if rv is None: ++ domains = [babel.default_domain] ++ else: ++ domains = rv ++ ctx.babel_domains = domains ++ return domains ++ ++ + def refresh(): + """Refreshes the cached timezones and locale information. This can + be used to switch a translation between a request and if you want diff --git a/project.vars b/etc/project.vars similarity index 100% rename from project.vars rename to etc/project.vars diff --git a/reqs.txt b/etc/reqs.txt similarity index 90% rename from reqs.txt rename to etc/reqs.txt index df74394b..baa1939c 100644 --- a/reqs.txt +++ b/etc/reqs.txt @@ -1,3 +1,4 @@ +pytz>=2012 Flask==0.9 Flask-Babel==0.8 Flask-Cache==0.10.1 diff --git a/etc/translation.vars b/etc/translation.vars new file mode 100644 index 00000000..cc7998cc --- /dev/null +++ b/etc/translation.vars @@ -0,0 +1,15 @@ +PROJECT=I2P +VERSION=website +BABELCFG=etc/babel.cfg +POTDIR=pots +PROJDIR=i2p2www +TRANSDIR=$PROJDIR/translations + +if [ -x env/bin/pybabel ]; then + PYBABEL=env/bin/pybabel +elif [ $(which pybabel) ]; then + PYBABEL=$(which pybabel) +else + echo "ERROR: pybabel was not found. Please run setup_venv.sh" >&2 + exit 1 +fi diff --git a/etc/update.vars b/etc/update.vars new file mode 100644 index 00000000..1d9b0230 --- /dev/null +++ b/etc/update.vars @@ -0,0 +1,3 @@ +MTNURL=127.0.0.1:8998 +MTNBRANCH=i2p.www.revamp +TOUCHFILE=/tmp/2fcd2f17-c293-4f77-b4c9-9b266ba70daa diff --git a/extract-messages.sh b/extract-messages.sh index 3c98a2a3..bdb277be 100755 --- a/extract-messages.sh +++ b/extract-messages.sh @@ -1,8 +1,36 @@ #!/bin/sh -. ./translation.vars +. ./etc/translation.vars -TZ=UTC ./pybabel extract --msgid-bugs-address="http://trac.i2p2.de" \ +export TZ=UTC + +if [ ! -e $POTDIR ]; then + mkdir $POTDIR +fi + +# By setting the PYTHONPATH here we can help pybabel find 'our' highlighting +# extension and we can use any pybabel +export PYTHONPATH=i2p2www:$PYTHONPATH + +if [ $# -ge 1 ] +then + $PYBABEL extract --msgid-bugs-address="http://trac.i2p2.de" \ --project=$PROJECT \ --version=$VERSION \ - -F $BABELCFG \ - -o $POTFILE $PROJDIR + -F $BABELCFG/$1 \ + -o $POTDIR/$1.pot $PROJDIR +else + for domain in $(ls $BABELCFG); do + if [ -e $POTDIR/$domain.pot ]; then + mv $POTDIR/$domain.pot $POTDIR/$domain.pot.old + fi + $PYBABEL extract --msgid-bugs-address="http://trac.i2p2.de" \ + --project=$PROJECT \ + --version=$VERSION \ + -F $BABELCFG/$domain \ + -o $POTDIR/$domain.pot $PROJDIR + diff -u $POTDIR/$domain.pot.old $POTDIR/$domain.pot | grep '^+' | grep -v '^+++' | grep -v '+"POT-Creation-Date' >/dev/null + if [ $? -eq 1 ]; then + mv $POTDIR/$domain.pot.old $POTDIR/$domain.pot + fi + done +fi diff --git a/i2p2www/__init__.py b/i2p2www/__init__.py index 8b0235fb..48f1a071 100644 --- a/i2p2www/__init__.py +++ b/i2p2www/__init__.py @@ -1,17 +1,33 @@ +# -*- coding: utf-8 -*- from flask import Flask, request, g, redirect, url_for, abort, render_template, send_from_directory, safe_join -from flaskext.babel import Babel -from flask.ext.cache import Cache +try: + from flaskext.babel import Babel +except ImportError: + from flask_babel import Babel +try: + from flask.ext.cache import Cache +except ImportError: + from flask_cache import Cache from docutils.core import publish_parts import os.path import os +try: + from i2p2www import settings +except ImportError: + settings = None + ########### # Constants -CURRENT_I2P_VERSION = '0.9.6' +CURRENT_I2P_VERSION = '0.9.9' -CANONICAL_DOMAIN = 'www.i2p2.de' +CANONICAL_DOMAIN = 'new.i2p-projekt.de' + +CACHE_CONFIG = settings.CACHE_CONFIG if settings and hasattr(settings, 'CACHE_CONFIG') else { + 'CACHE_DEFAULT_TIMEOUT': 600, + } BLOG_POSTS_PER_FEED = 10 BLOG_POSTS_PER_PAGE = 10 @@ -20,24 +36,54 @@ MEETINGS_PER_PAGE = 20 SUPPORTED_LANGS = [ 'en', 'es', -# 'zh', + 'zh_CN', 'de', 'fr', -# 'it', -# 'nl', -# 'ru', - 'sv', -# 'cs', -# 'ar', -# 'el', + 'it', + 'ja', + 'pl', + 'pt', + 'pt_BR', + 'ro', + 'ru', + 'sv_SE', ] +SUPPORTED_LANG_NAMES = { + 'en': u'English', + 'es': u'Castellano', + 'zh_CN': u'Chinese', + 'de': u'Deutsch', + 'fr': u'Français', + 'it': u'Italiano', + 'ja': u'Japanese', + 'pl': u'Polish', + 'pt': u'Portugese', + 'pt_BR': u'Brazilian Portugese', + 'ro': u'Romanian', + 'ru': u'Russian', + 'sv_SE': u'Svenska', + } + +DEFAULT_GETTEXT_DOMAIN = 'priority' +GETTEXT_DOMAIN_MAPPING = { + 'about': ['about'], + 'blog': ['blog'], + 'comparison': ['comparison'], + 'docs': ['docs'], + 'get-involved': ['get-involved'], + 'misc': ['misc'], + 'research': ['research'], + } + TEMPLATE_DIR = os.path.join(os.path.dirname(__file__), 'pages') STATIC_DIR = os.path.join(os.path.dirname(__file__), 'static') BLOG_DIR = os.path.join(os.path.dirname(__file__), 'blog') MEETINGS_DIR = os.path.join(os.path.dirname(__file__), 'meetings/logs') SITE_DIR = os.path.join(TEMPLATE_DIR, 'site') MIRRORS_FILE = os.path.join(TEMPLATE_DIR, 'downloads/mirrors') +ANONBIB_CFG = os.path.join(TEMPLATE_DIR, 'papers/anonbib.cfg') +ANONBIB_FILE = os.path.join(TEMPLATE_DIR, 'papers/anonbib.bib') ################### @@ -50,11 +96,8 @@ class MyFlask(Flask): app = application = MyFlask('i2p2www', template_folder=TEMPLATE_DIR, static_url_path='/_static', static_folder=STATIC_DIR) app.debug = bool(os.environ.get('APP_DEBUG', 'False')) -babel = Babel(app) -cache = Cache(app, config={ - 'CACHE_DEFAULT_TIMEOUT': 600, - #'CACHE_TYPE': '', # See http://packages.python.org/Flask-Cache/#configuring-flask-cache - }) +babel = Babel(app, default_domain=DEFAULT_GETTEXT_DOMAIN) +cache = Cache(app, config=CACHE_CONFIG) ################# @@ -67,7 +110,22 @@ def get_locale(): return g.lang # otherwise try to guess the language from the user accept # header the browser transmits. The best match wins. - return request.accept_languages.best_match(['en', 'es', 'zh', 'de', 'fr', 'it', 'nl', 'ru', 'sv', 'cs', 'ar']) + return request.accept_languages.best_match(SUPPORTED_LANGS) + +@babel.domainselector +def get_domains(): + domains = [] + frags = request.path.split('/', 2) + if len(frags) == 3: + path = frags[2] + for subpath in GETTEXT_DOMAIN_MAPPING: + if path.startswith(subpath): + domains.extend(GETTEXT_DOMAIN_MAPPING[subpath]) + # Always end with the priority domain, as it contains + # various template strings and is likely to be the most + # up-to-date (in case of any common translation strings). + domains.append(DEFAULT_GETTEXT_DOMAIN) + return domains ########################## @@ -161,7 +219,6 @@ def page_not_found(error): def server_error(error): return render_template('global/error_500.html'), 500 - # Import these to ensure they get loaded import templatevars import urls diff --git a/i2p2www/anonbib/BibTeX.py b/i2p2www/anonbib/BibTeX.py new file mode 100644 index 00000000..6d1df089 --- /dev/null +++ b/i2p2www/anonbib/BibTeX.py @@ -0,0 +1,1269 @@ +#!/usr/bin/python2 +# Copyright 2003-2008, Nick Mathewson. See LICENSE for licensing info. + +"""BibTeX.py -- parse and manipulate BibTeX files and entries. + + Based on perl code by Eddie Kohler; heavily modified. +""" + +import cStringIO +import re +import sys +import os + +import config + +import rank + +__all__ = [ 'ParseError', 'BibTeX', 'BibTeXEntry', 'htmlize', + 'ParsedAuthor', 'FileIter', 'Parser', 'parseFile', + 'splitBibTeXEntriesBy', 'sortBibTexEntriesBy', ] + +# List: must map from month number to month name. +MONTHS = [ None, + "January", "February", "March", "April", "May", "June", + "July", "August", "September", "October", "November", "December"] + +# Fields that we only care about for making web pages (BibTeX doesn't +# recognize them.) +WWW_FIELDS = [ 'www_section', 'www_important', 'www_remarks', + 'www_abstract_url', 'www_html_url', 'www_pdf_url', 'www_ps_url', + 'www_txt_url', 'www_ps_gz_url', 'www_amazon_url', + 'www_excerpt_url', 'www_publisher_url', + 'www_cache_section', 'www_tags' ] + +def url_untranslate(s): + """Change a BibTeX key into a string suitable for use in a URL.""" + s = re.sub(r'([%<>`#, &_\';])', + lambda m: "_%02x"%ord(m.group(1)), + s) + s = s.replace("/",":") + return s + +class ParseError(Exception): + """Raised on invalid BibTeX""" + pass + + +def smartJoin(*lst): + """Equivalent to os.path.join, but handle"." and ".." entries a bit better. + """ + lst = [ item for item in lst if item != "." ] + idx = 0 + while idx < len(lst): + if idx > 0 and lst[idx] == "..": + del lst[idx] + else: + idx += 1 + return os.path.join(*lst) + +class BibTeX: + """A parsed BibTeX file""" + def __init__(self): + self.entries = [] # List of BibTeXEntry + self.byKey = {} # Map from BibTeX key to BibTeX entry. + def addEntry(self, ent): + """Add a BibTeX entry to this file.""" + k = ent.key + if self.byKey.get(ent.key.lower()): + print >> sys.stderr, "Already have an entry named %s"%k + return + self.entries.append(ent) + self.byKey[ent.key.lower()] = ent + def resolve(self): + """Validate all entries in this file, and resolve cross-references""" + seen = {} + for ent in self.entries: + seen.clear() + while ent.get('crossref'): + try: + cr = self.byKey[ent['crossref'].lower()] + except KeyError: + print "No such crossref: %s"% ent['crossref'] + break + if seen.get(cr.key): + raise ParseError("Circular crossref at %s" % ent.key) + seen[cr.key] = 1 + del ent.entries['crossref'] + + if cr.entryLine < ent.entryLine: + print "Warning: crossref %s used after declaration"%cr.key + + for k in cr.entries.keys(): + if ent.entries.has_key(k): + print "ERROR: %s defined both in %s and in %s"%( + k,ent.key,cr.key) + else: + ent.entries[k] = cr.entries[k] + + ent.resolve() + newEntries = [] + rk = config.REQUIRE_KEY + if rk is None: + # hack: if no key is required, require "title", since every + # entry will have a title. + rk = "title" + + for ent in self.entries: + if ent.type in config.OMIT_ENTRIES or not ent.has_key(rk): + ent.check() + del self.byKey[ent.key.lower()] + else: + newEntries.append(ent) + self.entries = newEntries + +def buildAuthorTable(entries): + """Given a list of BibTeXEntry, return a map from parsed author name to + parsed canonical name. + """ + authorsByLast = {} + for e in entries: + for a in e.parsedAuthor: + authorsByLast.setdefault(tuple(a.last), []).append(a) + # map from author to collapsed author. + result = {} + for k,v in config.COLLAPSE_AUTHORS.items(): + a = parseAuthor(k)[0] + c = parseAuthor(v)[0] + result[c] = c + result[a] = c + + for e in entries: + for author in e.parsedAuthor: + if result.has_key(author): + continue + + c = author + for a in authorsByLast[tuple(author.last)]: + if a is author: + continue + c = c.collapsesTo(a) + result[author] = c + + if 0: + for a,c in result.items(): + if a != c: + print "Collapsing authors: %s => %s" % (a,c) + if 0: + print parseAuthor("Franz Kaashoek")[0].collapsesTo( + parseAuthor("M. Franz Kaashoek")[0]) + print parseAuthor("Paul F. Syverson")[0].collapsesTo( + parseAuthor("Paul Syverson")[0]) + print parseAuthor("Paul Syverson")[0].collapsesTo( + parseAuthor("Paul F. Syverson")[0]) + + return result + +def splitEntriesBy(entries, field): + """Take a list of BibTeX entries and the name of a bibtex field; return + a map from vield value to list of entry.""" + result = {} + for ent in entries: + key = ent.get(field) + try: + result[key].append(ent) + except: + result[key] = [ent] + return result + +def splitSortedEntriesBy(entries, field): + """Take inputs as in splitEntriesBy, where 'entries' is sorted by 'field'. + Return a list of (field-value, entry-list) tuples, in the order + given in 'entries'.""" + result = [] + curVal = "alskjdsakldj" + curList = [] + for ent in entries: + key = ent.get(field) + if key == curVal: + curList.append(ent) + else: + curVal = key + curList = [ent] + result.append((curVal, curList)) + return result + +def sortEntriesBy(entries, field, default): + """Take inputs as in splitEntriesBy, and return a list of entries sorted + by the value of 'field'. Entries without 'field' are sorted as if their + value were 'default'. + """ + tmp = [] + i = 0 + for ent in entries: + i += 1 + v = ent.get(field, default) + if v.startswith(""): + v = default + tmp.append((txtize(v), i, ent)) + tmp.sort() + return [ t[2] for t in tmp ] + +def splitEntriesByAuthor(entries): + """Take a list of entries, sort them by author names, and return: + a sorted list of (authorname-in-html, bibtex-entry-list) tuples, + a map from authorname-in-html to name-for-url. + Entries with multiple authors appear once per author. + """ + collapsedAuthors = buildAuthorTable(entries) + entries = sortEntriesByDate(entries) + result = {} # Name in sorting order -> entries + htmlResult = {} # name in sorting order -> Full name + url_map = {} # Full name -> Url + for ent in entries: + for a in ent.parsedAuthor: + canonical = collapsedAuthors[a] + url = canonical.getHomepage() + sortkey = canonical.getSortingName() + secname = canonical.getSectionName() + if url: + url_map[secname] = url + + htmlResult[sortkey] = secname + result.setdefault(sortkey, []).append(ent) + sortnames = result.keys() + sortnames.sort() + sections = [ (htmlResult[n], result[n]) for n in sortnames ] + return sections, url_map + +## def sortEntriesByAuthor(entries): +## tmp = [] +## i = 0 +## for ent in entries: +## i += 1 +## authors = [ txtize(" ".join(a.von+a.last+a.first+a.jr)) +## for a in ent.parsedAuthor ] +## tmp.append((tuple(authors), i, ent)) +## tmp.sort() +## return [ t[2] for t in tmp ] + +def sortEntriesByDate(entries): + """Sort a list of entries by their publication date.""" + tmp = [] + i = 0 + for ent in entries: + i += 1 + if (ent.get('month') == "forthcoming" or + ent.get('year') == "forthcoming"): + tmp.append((20000*13, i, ent)) + continue + try: + monthname = ent.get("month") + if monthname is not None: + match = re.match(r"(\w+)--\w+", monthname) + if match: + monthname = match.group(1) + mon = MONTHS.index(monthname) + except ValueError: + print "Unknown month %r in %s"%(ent.get("month"), ent.key) + mon = 0 + + try: + date = int(ent['year'])*13 + mon + except KeyError: + print "ERROR: No year field in %s"%ent.key + date = 10000*13 + except ValueError: + date = 10000*13 + tmp.append((date, i, ent)) + tmp.sort() + return [ t[2] for t in tmp ] + + +# List of fields that appear when we display the entries as BibTeX. +DISPLAYED_FIELDS = [ 'title', 'author', 'journal', 'booktitle', +'school', 'institution', 'organization', 'volume', 'number', 'year', +'month', 'address', 'location', 'chapter', 'edition', 'pages', 'editor', +'howpublished', 'key', 'publisher', 'type', 'note', 'series' ] + +class BibTeXEntry: + """A single BibTeX entry.""" + def __init__(self, type, key, entries): + self.type = type # What kind of entry is it? (@book,@injournal,etc) + self.key = key # What key does it have? + self.entries = entries # Map from key to value. + self.entryLine = 0 # Defined on this line number + def get(self, k, v=None): + return self.entries.get(k,v) + def has_key(self, k): + return self.entries.has_key(k) + def __getitem__(self, k): + return self.entries[k] + def __setitem__(self, k, v): + self.entries[k] = v + def __str__(self): + return self.format(70,1) + def getURL(self): + """Return the best URL to use for this paper, or None.""" + best = None + for field in ['www_pdf_url', 'www_ps_gz_url', 'www_ps_url', + 'www_html_url', 'www_txt_url', ]: + u = self.get(field) + if u: + if not best: + best = u + elif (best.startswith("http://citeseer.nj.nec.com/") + and not u.startswith("http://citeseer.nj.nec.com/")): + best = u + return best + + def format(self, width=70, indent=8, v=0, invStrings={}): + """Format this entry as BibTeX.""" + d = ["@%s{%s,\n" % (self.type, self.key)] + if v: + df = DISPLAYED_FIELDS[:] + for k in self.entries.keys(): + if k not in df: + df.append(k) + else: + df = DISPLAYED_FIELDS + for f in df: + if not self.entries.has_key(f): + continue + v = self.entries[f] + if v.startswith(""): + d.append("%%%%% ERROR: Missing field\n") + d.append("%% %s = {?????},\n"%f) + continue + np = v.translate(ALLCHARS, PRINTINGCHARS) + if np: + d.append("%%%%% "+("ERROR: Non-ASCII characters: '%r'\n"%np)) + d.append(" ") + v = v.replace("&", "&") + if invStrings.has_key(v): + s = "%s = %s,\n" %(f, invStrings[v]) + else: + s = "%s = {%s},\n" % (f, v) + d.append(_split(s,width,indent)) + d.append("}\n") + return "".join(d) + def resolve(self): + """Handle post-processing for this entry""" + a = self.get('author') + if a: + self.parsedAuthor = parseAuthor(a) + #print a + #print " => ",repr(self.parsedAuthor) + else: + self.parsedAuthor = None + + def isImportant(self): + """Return 1 iff this entry is marked as important""" + imp = self.get("www_important") + if imp and imp.strip().lower() not in ("no", "false", "0"): + return 1 + return 0 + + def check(self): + """Print any errors for this entry, and return true if there were + none.""" + errs = self._check() + for e in errs: + print e + return not errs + + def _check(self): + errs = [] + if self.type == 'inproceedings': + fields = 'booktitle', 'year' + elif self.type == 'incollection': + fields = 'booktitle', 'year' + elif self.type == 'proceedings': + fields = 'booktitle', 'editor' + elif self.type == 'article': + fields = 'journal', 'year' + elif self.type == 'techreport': + fields = 'institution', + elif self.type == 'misc': + fields = 'howpublished', + elif self.type in ('mastersthesis', 'phdthesis'): + fields = () + else: + fields = () + errs.append("ERROR: odd type %s"%self.type) + if self.type != 'proceedings': + fields += 'title', 'author', 'www_section', 'year' + + for field in fields: + if self.get(field) is None or \ + self.get(field).startswith(""): + errs.append("ERROR: %s has no %s field" % (self.key, field)) + self.entries[field] = "%s:??"%field + + if self.type == 'inproceedings': + if self.get("booktitle"): + if not self['booktitle'].startswith("Proceedings of") and \ + not self['booktitle'].startswith("{Proceedings of"): + errs.append("ERROR: %s's booktitle (%r) doesn't start with 'Proceedings of'" % (self.key, self['booktitle'])) + + if self.has_key("pages") and not re.search(r'\d+--\d+', self['pages']): + errs.append("ERROR: Misformed pages in %s"%self.key) + + if self.type == 'proceedings': + if self.get('title'): + errs.append("ERROR: %s is a proceedings: it should have a booktitle, not a title." % self.key) + + for field, value in self.entries.items(): + if value.translate(ALLCHARS, PRINTINGCHARS): + errs.append("ERROR: %s.%s has non-ASCII characters"%( + self.key, field)) + if field.startswith("www_") and field not in WWW_FIELDS: + errs.append("ERROR: unknown www field %s"% field) + if value.strip()[-1:] == '.' and \ + field not in ("notes", "www_remarks", "author"): + errs.append("ERROR: %s.%s has an extraneous period"%(self.key, + field)) + return errs + + def biblio_to_html(self): + """Return the HTML for the citation portion of entry.""" + if self.type in ('inproceedings', 'incollection'): + booktitle = self['booktitle'] + bookurl = self.get('bookurl') + if bookurl: + m = PROCEEDINGS_RE.match(booktitle) + if m: + res = ["In the ", m.group(1), + ''%bookurl, m.group(2), ""] + else: + res = ['In the %s' % (bookurl,booktitle)] + else: + res = ["In the ", booktitle ] + + if self.get("edition"): + res.append(",") + res.append(self['edition']) + if self.get("location"): + res.append(", ") + res.append(self['location']) + elif self.get("address"): + res.append(", ") + res.append(self['address']) + res.append(", %s %s" % (self.get('month',""), self['year'])) + if not self.get('pages'): + pass + elif "-" in self['pages']: + res.append(", pages %s"%self['pages']) + else: + res.append(", page %s"%self['pages']) + elif self.type == 'article': + res = ["In "] + if self.get('journalurl'): + res.append('%s'% + (self['journalurl'],self['journal'])) + else: + res.append(self['journal']) + if self.get('volume'): + res.append(" %s"%self['volume']) + if self.get('number'): + res.append("(%s)"%self['number']) + res.append(", %s %s" % (self.get('month',""), self['year'])) + if not self.get('pages'): + pass + elif "-" in self['pages']: + res.append(", pages %s"%self['pages']) + else: + res.append(", page %s"%self['pages']) + elif self.type == 'techreport': + res = [ "%s %s %s" % (self['institution'], + self.get('type', 'technical report'), + self.get('number', "")) ] + if self.get('month') or self.get('year'): + res.append(", %s %s" % (self.get('month', ''), + self.get('year', ''))) + elif self.type == 'mastersthesis' or self.type == 'phdthesis': + if self.get('type'): + res = [self['type']] + elif self.type == 'mastersthesis': + res = ["Masters's thesis"] + else: + res = ["Ph.D. thesis"] + if self.get('school'): + res.append(", %s"%(self['school'])) + if self.get('month') or self.get('year'): + res.append(", %s %s" % (self.get('month', ''), + self.get('year', ''))) + elif self.type == 'book': + res = [self['publisher']] + if self.get('year'): + res.append(" "); + res.append(self.get('year')); + # res.append(", %s"%(self.get('year'))) + if self.get('series'): + res.append(","); + res.append(self['series']); + elif self.type == 'misc': + res = [self['howpublished']] + if self.get('month') or self.get('year'): + res.append(", %s %s" % (self.get('month', ''), + self.get('year', ''))) + if not self.get('pages'): + pass + elif "-" in self['pages']: + res.append(", pages %s"%self['pages']) + else: + res.append(", page %s"%self['pages']) + else: + res = ["<Odd type %s>"%self.type] + + res[0:0] = [""] + res.append(".") + + bibtexurl = "./bibtex#%s"%url_untranslate(self.key) + res.append((" " + "(BibTeX entry)" + "") %bibtexurl) + return htmlize("".join(res)) + + def to_html(self, cache_path="./cache", base_url="."): + """Return the HTML for this entry.""" + imp = self.isImportant() + draft = self.get('year') == 'forthcoming' + if imp: + res = ["

  • " ] + elif draft: + res = ["

  • " ] + else: + res = ["

  • "] + + # TODO: CITE_CACHE_DIR has permission problems on eche's server. + if False: #imp or not draft: + # Add a picture of the rank + # Only if year is known or paper important! + r = rank.get_rank_html(self['title'], self.get('year'), + update=False, base_url=base_url) + if r is not None: + res.append(r) + + res.append("%s"%( + url_untranslate(self.key),htmlize(self['title']))) + + for cached in 0,1: + availability = [] + if not cached: + for which in [ "amazon", "excerpt", "publisher" ]: + key = "www_%s_url"%which + if self.get(key): + url=self[key] + url = unTeXescapeURL(url) + availability.append('%s' %(url,which)) + + cache_section = self.get('www_cache_section', ".") + if cache_section not in config.CACHE_SECTIONS: + if cache_section != ".": + print >>sys.stderr, "Unrecognized cache section %s"%( + cache_section) + cache_section="." + + for key, name, ext in (('www_abstract_url', 'abstract','abstract'), + ('www_html_url', 'HTML', 'html'), + ('www_pdf_url', 'PDF', 'pdf'), + ('www_ps_url', 'PS', 'ps'), + ('www_txt_url', 'TXT', 'txt'), + ('www_ps_gz_url', 'gzipped PS','ps.gz') + ): + if cached: + #XXXX the URL needs to be relative to the absolute + #XXXX cache path. + url = smartJoin(cache_path,cache_section, + "%s.%s"%(self.key,ext)) + fname = smartJoin(config.OUTPUT_DIR, config.CACHE_DIR, + cache_section, + "%s.%s"%(self.key,ext)) + if not os.path.exists(fname): continue + else: + url = self.get(key) + if not url: continue + url = unTeXescapeURL(url) + url = url.replace('&', '&') + availability.append('%s' %(url,name)) + + if availability: + res.append([" ", " "][cached]) + res.append("(") + if cached: res.append("Cached: ") + res.append(", ".join(availability)) + res.append(")") + + res.append("
    by ") + + #res.append("\n\n" % self.parsedAuthor) + htmlAuthors = [ a.htmlizeWithLink() for a in self.parsedAuthor ] + + if len(htmlAuthors) == 1: + res.append(htmlAuthors[0]) + elif len(htmlAuthors) == 2: + res.append(" and ".join(htmlAuthors)) + else: + res.append(", ".join(htmlAuthors[:-1])) + res.append(", and ") + res.append(htmlAuthors[-1]) + + if res[-1][-1] != '.': + res.append(".") + res.append("
    \n") + res.append(self.biblio_to_html()) + res.append("·"%url_untranslate(self.key)) + res.append("

    ") + + if self.get('www_remarks'): + res.append("

    %s

    "%htmlize( + self['www_remarks'])) + + if imp or draft: + res.append("") + res.append("
    • \n\n") + + return "".join(res) + +def unTeXescapeURL(s): + """Turn a URL as formatted in TeX into a real URL.""" + s = s.replace("\\_", "_") + s = s.replace("\\-", "") + s = s.replace("\{}", "") + s = s.replace("{}", "") + return s + +def TeXescapeURL(s): + """Escape a URL for use in TeX""" + s = s.replace("_", "\\_") + s = s.replace("~", "\{}~") + return s + +RE_LONE_AMP = re.compile(r'&([^a-z0-9])') +RE_LONE_I = re.compile(r'\\i([^a-z0-9])') +RE_ACCENT = re.compile(r'\\([\'`~^"c])([^{]|{.})') +RE_LIGATURE = re.compile(r'\\(AE|ae|OE|oe|AA|aa|O|o|ss)([^a-z0-9])') +ACCENT_MAP = { "'" : 'acute', + "`" : 'grave', + "~" : 'tilde', + "^" : 'circ', + '"' : 'uml', + "c" : 'cedil', + } +UNICODE_MAP = { 'ń' : 'ń', } +HTML_LIGATURE_MAP = { + 'AE' : 'Æ', + 'ae' : 'æ', + 'OE' : 'Œ', + 'oe' : 'œ', + 'AA' : 'Å', + 'aa' : 'å', + 'O' : 'Ø', + 'o' : 'ø', + 'ss' : 'ß', + } +RE_TEX_CMD = re.compile(r"(?:\\[a-zA-Z@]+|\\.)") +RE_PAGE_SPAN = re.compile(r"(\d)--(\d)") +def _unaccent(m): + accent,char = m.groups() + if char[0] == '{': + char = char[1] + accented = "&%s%s;" % (char, ACCENT_MAP[accent]) + return UNICODE_MAP.get(accented, accented) +def _unlig_html(m): + return "%s%s"%(HTML_LIGATURE_MAP[m.group(1)],m.group(2)) +def htmlize(s): + """Turn a TeX string into good-looking HTML.""" + s = RE_LONE_AMP.sub(lambda m: "&%s" % m.group(1), s) + s = RE_LONE_I.sub(lambda m: "i%s" % m.group(1), s) + s = RE_ACCENT.sub(_unaccent, s) + s = unTeXescapeURL(s) + s = RE_LIGATURE.sub(_unlig_html, s); + s = RE_TEX_CMD.sub("", s) + s = s.translate(ALLCHARS, "{}") + s = RE_PAGE_SPAN.sub(lambda m: "%s-%s"%(m.groups()), s) + s = s.replace("---", "—"); + s = s.replace("--", "–"); + return s + +def author_url(author): + """Given an author's name, return a URL for his/her homepage.""" + for pat, url in config.AUTHOR_RE_LIST: + if pat.search(author): + return url + return None + +def txtize(s): + """Turn a TeX string into decnent plaintext.""" + s = RE_LONE_I.sub(lambda m: "i%s" % m.group(1), s) + s = RE_ACCENT.sub(lambda m: "%s" % m.group(2), s) + s = RE_LIGATURE.sub(lambda m: "%s%s"%m.groups(), s) + s = RE_TEX_CMD.sub("", s) + s = s.translate(ALLCHARS, "{}") + return s + +PROCEEDINGS_RE = re.compile( + r'((?:proceedings|workshop record) of(?: the)? )(.*)', + re.I) + +class ParsedAuthor: + """The parsed name of an author. + + Eddie deserves credit for this incredibly hairy business. + """ + def __init__(self, first, von, last, jr): + self.first = first + self.von = von + self.last = last + self.jr = jr + self.collapsable = 1 + + self.html = htmlize(str(self)) + self.txt = txtize(str(self)) + + s = self.html + for pat in config.NO_COLLAPSE_AUTHORS_RE_LIST: + if pat.search(s): + self.collapsable = 0 + break + + def __eq__(self, o): + return ((self.first == o.first) and + (self.last == o.last) and + (self.von == o.von) and + (self.jr == o.jr)) + + def __hash__(self): + return hash(repr(self)) + + def collapsesTo(self, o): + """Return true iff 'o' could be a more canonical version of this author + """ + if not self.collapsable or not o.collapsable: + return self + + if self.last != o.last or self.von != o.von or self.jr != o.jr: + return self + if not self.first: + return o + + if len(self.first) == len(o.first): + n = [] + for a,b in zip(self.first, o.first): + if a == b: + n.append(a) + elif len(a) == 2 and a[1] == '.' and a[0] == b[0]: + n.append(b) + elif len(b) == 2 and b[1] == '.' and a[0] == b[0]: + n.append(a) + else: + return self + if n == self.first: + return self + elif n == o.first: + return o + else: + return self + else: + realname = max([len(n) for n in self.first+o.first])>2 + if not realname: + return self + + if len(self.first) < len(o.first): + short = self.first; long = o.first + else: + short = o.first; long = self.first + + initials_s = "".join([n[0] for n in short]) + initials_l = "".join([n[0] for n in long]) + idx = initials_l.find(initials_s) + if idx < 0: + return self + n = long[:idx] + for i in range(idx, idx+len(short)): + a = long[i]; b = short[i-idx] + if a == b: + n.append(a) + elif len(a) == 2 and a[1] == '.' and a[0] == b[0]: + n.append(b) + elif len(b) == 2 and b[1] == '.' and a[0] == b[0]: + n.append(a) + else: + return self + n += long[idx+len(short):] + + if n == self.first: + return self + elif n == o.first: + return o + else: + return self + + def __repr__(self): + return "ParsedAuthor(%r,%r,%r,%r)"%(self.first,self.von, + self.last,self.jr) + def __str__(self): + a = " ".join(self.first+self.von+self.last) + if self.jr: + return "%s, %s" % (a,self.jr) + return a + + def getHomepage(self): + s = self.html + for pat, url in config.AUTHOR_RE_LIST: + if pat.search(s): + return url + return None + + def getSortingName(self): + """Return a representation of this author's name in von-last-first-jr + order, unless overridden by ALPH """ + s = self.html + for pat,v in config.ALPHABETIZE_AUTHOR_AS_RE_LIST: + if pat.search(s): + return v + + return txtize(" ".join(self.von+self.last+self.first+self.jr)) + + def getSectionName(self): + """Return a HTML representation of this author's name in + last, first von, jr order""" + secname = " ".join(self.last) + more = self.first+self.von + if more: + secname += ", "+" ".join(more) + if self.jr: + secname += ", "+" ".join(self.jr) + secname = htmlize(secname) + return secname + + def htmlizeWithLink(self): + a = self.html + u = self.getHomepage() + if u: + return "%s"%(u,a) + else: + return a + +def _split(s,w=79,indent=8): + r = [] + s = re.sub(r"\s+", " ", s) + first = 1 + indentation = "" + while len(s) > w: + for i in xrange(w-1, 20, -1): + if s[i] == ' ': + r.append(indentation+s[:i]) + s = s[i+1:] + break + else: + r.append(indentation+s.strip()) + s = "" + if first: + first = 0 + w -= indent + indentation = " "*indent + if (s): + r.append(indentation+s) + r.append("") + return "\n".join(r) + +class FileIter: + def __init__(self, fname=None, file=None, it=None, string=None): + if fname: + file = open(fname, 'r') + if string: + file = cStringIO.StringIO(string) + if file: + it = iter(file.xreadlines()) + self.iter = it + assert self.iter + self.lineno = 0 + self._next = it.next + def next(self): + self.lineno += 1 + return self._next() + + +def parseAuthor(s): + try: + return _parseAuthor(s) + except: + print >>sys.stderr, "Internal error while parsing author %r"%s + raise + +def _parseAuthor(s): + """Take an author string and return a list of ParsedAuthor.""" + items = [] + + s = s.strip() + while s: + s = s.strip() + bracelevel = 0 + for i in xrange(len(s)): + if s[i] == '{': + bracelevel += 1 + elif s[i] == '}': + bracelevel -= 1 + elif bracelevel <= 0 and s[i] in " \t\n,": + break + if i+1 == len(s): + items.append(s) + else: + items.append(s[0:i]) + if (s[i] == ','): + items.append(',') + s = s[i+1:] + + authors = [[]] + for item in items: + if item == 'and': + authors.append([]) + else: + authors[-1].append(item) + + parsedAuthors = [] + # Split into first, von, last, jr + for author in authors: + commas = 0 + fvl = [] + vl = [] + f = [] + v = [] + l = [] + j = [] + cur = fvl + for item in author: + if item == ',': + if commas == 0: + vl = fvl + fvl = [] + cur = f + else: + j.extend(f) + cur = f = [] + commas += 1 + else: + cur.append(item) + + if commas == 0: + split_von(f,v,l,fvl) + else: + f_tmp = [] + split_von(f_tmp,v,l,vl) + + parsedAuthors.append(ParsedAuthor(f,v,l,j)) + + return parsedAuthors + +ALLCHARS = "".join(map(chr,range(256))) +PRINTINGCHARS = "\t\n\r"+"".join(map(chr,range(32, 127))) +LC_CHARS = "abcdefghijklmnopqrstuvwxyz" +SV_DELCHARS = ("ABCDEFGHIJKLMNOPQRSTUVWXYZ" + "abcdefghijklmnopqrstuvwxyz" + "@") +RE_ESCAPED = re.compile(r'\\.') +def split_von(f,v,l,x): + in_von = 0 + while x: + tt = t = x[0] + del x[0] + if tt[:2] == '{\\': + tt = tt.translate(ALLCHARS, SV_DELCHARS) + tt = RE_ESCAPED.sub("", tt) + tt = tt.translate(ALLCHARS, "{}") + if tt.translate(ALLCHARS, LC_CHARS) == "": + v.append(t) + in_von = 1 + elif in_von and f is not None: + l.append(t) + l.extend(x) + return + else: + f.append(t) + if not in_von: + l.append(f[-1]) + del f[-1] + + +class Parser: + """Parser class: reads BibTeX from a file and returns a BibTeX object.""" + ## Fields + # strings: maps entry string keys to their values. + # newStrings: all string definitions not in config.INITIAL_STRINGS + # invStrings: map from string values to their keys. + # fileiter: the line iterator we're parsing from. + # result: the BibTeX object that we're parsing into + # litStringLine: the line on which we started parsing a literal string; + # 0 for none. + # entryLine: the line on which the current entry started; 0 for none. + # + # curEntType: the type of the entry we're parsing now. (paper,article,etc) + def __init__(self, fileiter, initial_strings, result=None): + self.strings = config.INITIAL_STRINGS.copy() + self.strings.update(initial_strings) + self.newStrings = {} + self.invStrings = {} + for k,v in config.INITIAL_STRINGS.items(): + self.invStrings[v]=k + self.fileiter = fileiter + if result is None: + result = BibTeX() + self.result = result + self.litStringLine = 0 + self.entryLine = 0 + + def _parseKey(self, line): + it = self.fileiter + line = _advance(it,line) + m = KEY_RE.match(line) + if not m: + raise ParseError("Expected key at line %s"%self.fileiter.lineno) + key, line = m.groups() + return key, line + + def _parseValue(self, line): + it = self.fileiter + bracelevel = 0 + data = [] + while 1: + line = _advance(it,line) + line = line.strip() + assert line + + # Literal string? + if line[0] == '"': + line=line[1:] + self.litStringLine = it.lineno + while 1: + if bracelevel: + m = BRACE_CLOSE_RE.match(line) + if m: + data.append(m.group(1)) + data.append('}') + line = m.group(2) + bracelevel -= 1 + continue + else: + m = STRING_CLOSE_RE.match(line) + if m: + data.append(m.group(1)) + line = m.group(2) + break + m = BRACE_OPEN_RE.match(line) + if m: + data.append(m.group(1)) + line = m.group(2) + bracelevel += 1 + continue + data.append(line) + data.append(" ") + line = it.next() + self.litStringLine = 0 + elif line[0] == '{': + bracelevel += 1 + line = line[1:] + while bracelevel: + m = BRACE_CLOSE_RE.match(line) + if m: + #print bracelevel, "A", repr(m.group(1)) + data.append(m.group(1)) + bracelevel -= 1 + if bracelevel > 0: + #print bracelevel, "- '}'" + data.append('}') + line = m.group(2) + continue + m = BRACE_OPEN_RE.match(line) + if m: + bracelevel += 1 + #print bracelevel, "B", repr(m.group(1)) + data.append(m.group(1)) + line = m.group(2) + continue + else: + #print bracelevel, "C", repr(line) + data.append(line) + data.append(" ") + line = it.next() + elif line[0] == '#': + print >>sys.stderr, "Weird concat on line %s"%it.lineno + elif line[0] in "},": + if not data: + print >>sys.stderr, "No data after field on line %s"%( + it.lineno) + else: + m = RAW_DATA_RE.match(line) + if m: + s = self.strings.get(m.group(1).lower()) + if s is not None: + data.append(s) + else: + data.append(m.group(1)) + line = m.group(2) + else: + raise ParseError("Questionable line at line %s"%it.lineno) + + # Got a string, check for concatenation. + if line.isspace() or not line: + data.append(" ") + line = _advance(it,line) + line = line.strip() + assert line + if line[0] == '#': + line = line[1:] + else: + data = "".join(data) + data = re.sub(r'\s+', ' ', data) + data = re.sub(r'^\s+', '', data) + data = re.sub(r'\s+$', '', data) + return data, line + + def _parseEntry(self, line): #name, strings, entries + it = self.fileiter + self.entryLine = it.lineno + line = _advance(it,line) + + m = BRACE_BEGIN_RE.match(line) + if not m: + raise ParseError("Expected an opening brace at line %s"%it.lineno) + line = m.group(1) + + proto = { 'string' : 'p', + 'preamble' : 'v', + }.get(self.curEntType, 'kp*') + + v = [] + while 1: + line = _advance(it,line) + + m = BRACE_END_RE.match(line) + if m: + line = m.group(1) + break + if not proto: + raise ParseError("Overlong entry starting on line %s" + % self.entryLine) + elif proto[0] == 'k': + key, line = self._parseKey(line) + v.append(key) + elif proto[0] == 'v': + value, line = self._parseValue(line) + v.append(value) + elif proto[0] == 'p': + key, line = self._parseKey(line) + v.append(key) + line = _advance(it,line) + line = line.lstrip() + if line[0] == '=': + line = line[1:] + value, line = self._parseValue(line) + v.append(value) + else: + assert 0 + line = line.strip() + if line and line[0] == ',': + line = line[1:] + if proto and proto[1:] != '*': + proto = proto[1:] + if proto and proto[1:] != '*': + raise ParseError("Missing arguments to %s on line %s" % ( + self.curEntType, self.entryLine)) + + if self.curEntType == 'string': + self.strings[v[0]] = v[1] + self.newStrings[v[0]] = v[1] + self.invStrings[v[1]] = v[0] + elif self.curEntType == 'preamble': + pass + else: + key = v[0] + d = {} + for i in xrange(1,len(v),2): + d[v[i].lower()] = v[i+1] + ent = BibTeXEntry(self.curEntType, key, d) + ent.entryLine = self.entryLine + self.result.addEntry(ent) + + return line + + def parse(self): + try: + self._parse() + except StopIteration: + if self.litStringLine: + raise ParseError("Unexpected EOF in string (started on %s)" % + self.litStringLine) + elif self.entryLine: + raise ParseError("Unexpected EOF at line %s (entry started " + "on %s)" % (self.fileiter.lineno, + self.entryLine)) + + self.result.invStrings = self.invStrings + self.result.newStrings = self.newStrings + + return self.result + + def _parse(self): + it = self.fileiter + line = it.next() + while 1: + # Skip blank lines. + while not line or line.isspace() or OUTER_COMMENT_RE.match(line): + line = it.next() + # Get the first line of an entry. + m = ENTRY_BEGIN_RE.match(line) + if m: + self.curEntType = m.group(1).lower() + line = m.group(2) + line = self._parseEntry(line) + self.entryLine = 0 + else: + raise ParseError("Bad input at line %s (expected a new entry.)" + % it.lineno) + +def _advance(it,line): + while not line or line.isspace() or COMMENT_RE.match(line): + line = it.next() + return line + +# Matches a comment line outside of an entry. +OUTER_COMMENT_RE = re.compile(r'^\s*[\#\%]') +# Matches a comment line inside of an entry. +COMMENT_RE = re.compile(r'^\s*\%') +# Matches the start of an entry. group 1 is the type of the entry. +# group 2 is the rest of the line. +ENTRY_BEGIN_RE = re.compile(r'''^\s*\@([^\s\"\%\'\(\)\,\=\{\}]+)(.*)''') +# Start of an entry. group 1 is the keyword naming the entry. +BRACE_BEGIN_RE = re.compile(r'\s*\{(.*)') +BRACE_END_RE = re.compile(r'\s*\}(.*)') +KEY_RE = re.compile(r'''\s*([^\"\#\%\'\(\)\,\=\{\}\s]+)(.*)''') + +STRING_CLOSE_RE = re.compile(r'^([^\{\}\"]*)\"(.*)') +BRACE_CLOSE_RE = re.compile(r'^([^\{\}]*)\}(.*)') +BRACE_OPEN_RE = re.compile(r'^([^\{\}]*\{)(.*)') +RAW_DATA_RE = re.compile(r'^([^\s\},]+)(.*)') + +def parseFile(filename, result=None): + """Helper function: parse a single BibTeX file""" + f = FileIter(fname=filename) + p = Parser(f, {}, result) + r = p.parse() + r.resolve() + for e in r.entries: + e.check() + return r + +def parseString(string, result=None): + """Helper function: parse BibTeX from a string""" + f = FileIter(string=string) + p = Parser(f, {}, result) + r = p.parse() + r.resolve() + for e in r.entries: + e.check() + return r + +if __name__ == '__main__': + if len(sys.argv)>1: + fname=sys.argv[1] + else: + fname="testbib/pdos.bib" + + r = parseFile(fname) + + for e in r.entries: + if e.type in ("proceedings", "journal"): continue + print e.to_html() + diff --git a/i2p2www/anonbib/Makefile b/i2p2www/anonbib/Makefile new file mode 100644 index 00000000..90cb8e16 --- /dev/null +++ b/i2p2www/anonbib/Makefile @@ -0,0 +1,39 @@ +PYTHON=python +VERSION=0.3-dev + +all: + $(PYTHON) writeHTML.py anonbib.cfg + +clean: + rm -f *~ */*~ *.pyc *.pyo + +update: + $(PYTHON) updateCache.py anonbib.cfg + $(PYTHON) rank.py anonbib.cfg + +suggest: + $(PYTHON) rank.py suggest anonbib.cfg + +test: + $(PYTHON) test.py + +veryclean: clean + rm -f author.html date.html topic.html bibtex.html tmp.bib + +TEMPLATES=_template_.html _template_bibtex.html +CSS=css/main.css css/pubs.css +BIBTEX=anonbib.bib +SOURCE=BibTeX.py config.py metaphone.py reconcile.py updateCache.py \ + writeHTML.py rank.py tests.py +EXTRAS=TODO README Makefile ChangeLog anonbib.cfg gold.gif silver.gif \ + upb.gif ups.gif + +DISTFILES=$(TEMPLATES) $(CSS) $(BIBTEX) $(SOURCE) $(EXTRAS) + +dist: clean + rm -rf anonbib-$(VERSION) + mkdir anonbib-$(VERSION) + tar cf - $(DISTFILES) | (cd anonbib-$(VERSION); tar xf -) + mkdir anonbib-$(VERSION)/cache + tar czf anonbib-$(VERSION).tar.gz anonbib-$(VERSION) + rm -rf anonbib-$(VERSION) diff --git a/i2p2www/anonbib/README b/i2p2www/anonbib/README new file mode 100644 index 00000000..b15ea993 --- /dev/null +++ b/i2p2www/anonbib/README @@ -0,0 +1,52 @@ +anonbib 0.3 -- Code to generate the anonymity bibliography + +Copyright (c) 2003-2008 Nick Mathewson +Based on 'PDOSBib' perl code by Eddie Kohler + +This software is licensed under the GNU GPL, version 2 or later. + +To use this software, you need to understand BibTeX and Python a +little. If it breaks, you get to keep both pieces. You will need +Python 2.2 or later. + +To use this package: + - Get a good BibTeX file. You may want to mark it up with some of the + extra keys used in our "anonbib.bib" file. All of the additional + Bibtex keys we use have the prefix "www_"; check out anonbib.bib + for their usage. + + - Edit anonbib.cfg and _template_.html and _template_bibtex.html so they + refer to your files, authors, topics, and so on. + + - Run 'python updateCache.py anonbib.cfg' to create a local cache of the + papers in your bibliography based on their www_*_url entries. (By + default, the script will ignore any entries you have already cached. To + force a fresh download of a cached file, delete it.) + + - Run 'python rank.py anonbib.cfg' to download Google Scholar rankings of + all the papers. + + - Run 'python writeHTML.py anonbib.cfg'. Fix any errors you care about. + + - Re-run these scripts when you change the bibliography. + + - If you want to merge in big BibTeX files, try using the reconcile.py + script. See the comment at the start of the file for usage info. + + +New in 0.3: + - Support for Google Scholar rankings to denote hot/rising papers. + Implemented by George Danezis. + - Make reconcile script generate more useful output. + - Add support for multiple bibliographies generated from a single bibtex + source. This is done via 'tags' on bibtex entries. If an entry is + tagged, it appears in the corresponding bibliographies. This is good + for generating a master bibliography and one or more selected readings + lists from the same source. + - Handle more errors when downloading files. + - When fetching a paper with a .ps url, generate the .ps.gz file + automatically. + - Note an error when a crossref overrides an existing field in an entry. + - Handle the Proceedings type correctly. + - Enforce proper encoding on pages: it must be number--number. + - diff --git a/i2p2www/anonbib/TODO b/i2p2www/anonbib/TODO new file mode 100644 index 00000000..c208fc2e --- /dev/null +++ b/i2p2www/anonbib/TODO @@ -0,0 +1,33 @@ + + +- More general tasks + . Know about @book + . Write unit tests for everything + . Make name parsing vaguely sane + - Maybe uncrossref in tmp.bib + - Maybe pull important papers to the start of their sections? + . Clean \{}~ when going from note to url; add \{}~ when making + note from url. + . Also clean \_ to _ and back + - Look for urls in wherepublished. + . Forgive newlines in wherepublished, note. + - When sorting by date, entries with unknown months go into a magic + "month zero" before January. Is this right? + - Strip unused features. + o Take a configuration file on the command line instead of just + importing config.py. + +- Cache tasks + - Generate a list of broken links + - Re-download all cached items if requested + - Clear dead items from cache + - Use HTTP HEAD requests to decide whetherto update stale + elements in cache. + - Add ability to honor a "www_no_cache={1}" option for entries + if the authors ask us not to cache them. + - Maybe, add ability to cache images from an HTML page. + +- Reconcile tasks + - Document it. + - Notice when there is new or different information of certain kinds + (pages, dates, etc) in the new information. diff --git a/i2p2www/anonbib/__init__.py b/i2p2www/anonbib/__init__.py new file mode 100644 index 00000000..e69de29b diff --git a/i2p2www/anonbib/config.py b/i2p2www/anonbib/config.py new file mode 100644 index 00000000..c1b1b6ec --- /dev/null +++ b/i2p2www/anonbib/config.py @@ -0,0 +1,56 @@ +# Copyright 2003-2006, Nick Mathewson. See LICENSE for licensing info. + +import re + +_KEYS = [ "ALL_TAGS", + "ALPHABETIZE_AUTHOR_AS","AUTHOR_URLS","CACHE_DIR","CACHE_SECTIONS", + "CACHE_UMASK", + "CITE_CACHE_DIR", + "COLLAPSE_AUTHORS", + "DOWNLOAD_CONNECT_TIMEOUT","INITIAL_STRINGS", + "MASTER_BIB", "NO_COLLAPSE_AUTHORS", "OMIT_ENTRIES", + "OUTPUT_DIR", "TEMPLATE_FILE", "BIBTEX_TEMPLATE_FILE", + "REQUIRE_KEY", "TAG_TITLES", "TAG_DIRECTORIES", "TAG_SHORT_TITLES", + ] + +for _k in _KEYS: + globals()[_k]=None +del _k + +def load(cfgFile): + mod = {} + execfile(cfgFile, mod) + for _k in _KEYS: + try: + globals()[_k]=mod[_k] + except KeyError: + raise KeyError("Configuration option %s is missing"%_k) + + INITIAL_STRINGS.update(_EXTRA_INITIAL_STRINGS) + AUTHOR_RE_LIST[:] = [ + (re.compile(k, re.I), v,) for k, v in AUTHOR_URLS.items() + ] + + NO_COLLAPSE_AUTHORS_RE_LIST[:] = [ + re.compile(pat, re.I) for pat in NO_COLLAPSE_AUTHORS + ] + + ALPHABETIZE_AUTHOR_AS_RE_LIST[:] = [ + (re.compile(k, re.I), v,) for k,v in ALPHABETIZE_AUTHOR_AS.items() + ] + +_EXTRA_INITIAL_STRINGS = { + # MONTHS + 'jan' : 'January', 'feb' : 'February', + 'mar' : 'March', 'apr' : 'April', + 'may' : 'May', 'jun' : 'June', + 'jul' : 'July', 'aug' : 'August', + 'sep' : 'September', 'oct' : 'October', + 'nov' : 'November', 'dec' : 'December', +} + +AUTHOR_RE_LIST = [] + +NO_COLLAPSE_AUTHORS_RE_LIST = [] + +ALPHABETIZE_AUTHOR_AS_RE_LIST = [] diff --git a/i2p2www/anonbib/css/main.css b/i2p2www/anonbib/css/main.css new file mode 100644 index 00000000..ce589cc9 --- /dev/null +++ b/i2p2www/anonbib/css/main.css @@ -0,0 +1,111 @@ +img { + border: 0px; +} + +BODY { + background-color: #FFF; + color: #000; + margin: 0px; +} + +FORM { + margin-top: 0.5em; + margin-bottom: 0.5em; +} + +P, TD { + font-family: lucida, "Lucida Sans Unicode", Geneva, sans-serif; +} + +P.contact { + text-align: center; +} + +P.contact A { + font-family: lucida, "Lucida Sans Unicode", Geneva, sans-serif; + font-weight: normal; +} + +SPAN.email { + font-family: lucidatypewriter, "Lucida Typewriter", Monaco, "Lucida Sans Unicode", monospace; + font-weight: bold; +} + +P IMG { + vertical-align: text-bottom; +} + +P.crumbbreadth { + margin-top: 0.25em; +} + +.compact { + margin-top: -0.5em; + text-indent: 0em; +} + +SPAN.biblio { + font-style: italic; +} + +SPAN.biblio A { + font-family: lucida, "Lucida Sans Unicode", Geneva, sans-serif; + font-weight: normal; + text-decoration: underline; +} + +SPAN.availability { + font-family: lucidatypewriter, "Lucida Typewriter", Monaco, "Lucida Sans Unicode", monospace; + font-weight: normal; +} + +UL { + list-style: outside; +} + +UL.expand { + margin-bottom: 1em; +} + +UL.sections { + list-style: none; +} + +/* Font-level properties */ + +PRE { + font-family: lucidatypewriter, "Lucida Typewriter", Monaco, "Lucida Sans Unicode", monospace; +} + +STRONG, A { + font-family: lucidatypewriter, "Lucida Typewriter", Monaco, "Rockwell", "Lucida Sans Unicode", monospace; + font-weight: bold; +} + +A:link { + color: #B00; +} + +A:visited { + color: #903; +} + +H1, H2, H3, H4, H5, H6 { + font-family: lucidatypewriter, "Lucida Typewriter", "Lucida Console", Monaco, monospace; +} + +H1 A, H2 A, H3 A, H4 A, H5 A, H6 A { + font-family: lucidatypewriter, "Lucida Typewriter", "Lucida Console", Monaco, monospace; +} + +H1 { + color: #00B; +} + +H2 { + color: #006; +} + +H3 { + color: #006; +} diff --git a/i2p2www/anonbib/gold.gif b/i2p2www/anonbib/gold.gif new file mode 100644 index 00000000..44505dba Binary files /dev/null and b/i2p2www/anonbib/gold.gif differ diff --git a/i2p2www/anonbib/metaphone.py b/i2p2www/anonbib/metaphone.py new file mode 100644 index 00000000..f57135d7 --- /dev/null +++ b/i2p2www/anonbib/metaphone.py @@ -0,0 +1,193 @@ +#!/usr/bin/python2 +# Copyright 2003-2008, Nick Mathewson. See LICENSE for licensing info. + +"""metaphone.py -- Pure-python metaphone implementation. + + (This is not guaranteed to match the real metaphone algorithm; I + haven't tested it thorougly enough. Let me know if you find bugs. + + Based on the original C++ metaphone implementation.) +""" + +TRIPLES = { + 'dge': 'j', + 'dgi': 'j', + 'dgy': 'j', + 'sia': '+x', + 'sio': '+x', + 'tia': '+x', + 'tio': '+x', + 'tch': '', + 'tha': '0', + 'the': '0', + 'thi': '0', + 'tho': '0', + 'thu': '0', + } + +DOUBLES = { + 'ph' : 'f', + 'sh' : 'x' + } + +SINGLETONS = { + 'd': 't', + 'f': 'f', + 'j': 'j', + 'l': 'l', + 'm': 'm', + 'n': 'n', + 'r': 'r', + 'p': 'p', + 'q': 'k', + 'v': 'f', + 'x': 'ks', + 'z': 's', +} + +ALLCHARS = "".join(map(chr, range(256))) +NONLCCHARS = "".join([c for c in ALLCHARS if not c.islower()]) +def metaphone(s): + """Return the metaphone equivalent of a provided string""" + s = s.lower() + s = s.translate(ALLCHARS, NONLCCHARS) + + if not s: return "" + + # If ae, gn, kn, pn, wr then drop the first letter. + if s[:2] in ("ae", "gn", "kn", "pn", "wr"): + s = s[1:] + + # Change "x" to "s" + if s[0] == 'x': + s = "s%s" % s[1:] + + # Get rid of "h" in "wh". + if s[:2] == 'wh': + s = "w%s" % s[1:] + + # Get rid of s from end. + if s[-1] == 's': + s = s[:-1] + + result = [] + prevLtr = ' ' + vowelBefore = 0 + lastChar = len(s)-1 + for idx in range(len(s)): + curLtr = s[idx] + # If first char is a vowel, keep it. + if curLtr in "aeiou": + if idx == 0: + result.append(curLtr) + continue + + # Skip double letters. + if idx < lastChar: + if curLtr == s[idx+1]: + continue + + try: + r = TRIPLES[s[idx:idx+3]] + if r == "+x": + if idx > 1: + result.append("x") + continue + else: + result.append(r) + continue + except KeyError: + pass + try: + r = DOUBLES[s[idx:idx+2]] + result.append(r) + continue + except KeyError: + pass + try: + r = SINGLETONS[s[idx]] + result.append(r) + continue + except KeyError: + pass + + if idx > 0: + prevLtr = s[idx-1] + vowelBefore = prevLtr in "aeiou" + curLtr = s[idx] + + nextLtr2 = ' ' + if idx < lastChar: + nextLtr = s[idx+1] + vowelAfter = nextLtr in "aeiou" + frontvAfter = nextLtr in "eiy" + if idx+1 < lastChar: + nextLtr2 = s[idx+2] + else: + nextLtr = ' ' + vowelAfter = frontvAfter = 0 + + + if curLtr == 'b': + if idx == lastChar and prevLtr == 'm': + pass + else: + result.append(curLtr) + elif curLtr == 'c': + # silent 'sci', 'sce, 'scy', 'sci', etc OK. + if not (prevLtr == 's' and frontvAfter): + if nextLtr in 'ia': + result.append("x") + elif frontvAfter: + result.append("s") + elif prevLtr == 's' and nextLtr == 'h': + result.append('k') + elif nextLtr == 'h': + if idx == 0 and nextLtr2 in "aeiou": + result.append('k') + else: + result.append('x') + elif prevLtr == 'c': + result.append('c') + else: + result.append('k') + elif curLtr == 'g': + if (idx < lastChar-1) and nextLtr == 'h': + pass + elif s[idx:] == 'gned': + pass + elif s[idx:] == 'gn': + pass + elif prevLtr == 'd' and frontvAfter: + pass + else: + hard = (prevLtr == 'g') + if frontvAfter and not hard: + result.append('j') + else: + result.append('k') + elif curLtr == 'h': + if prevLtr in 'csptg': + pass + elif vowelBefore and not vowelAfter: + pass + else: + result.append('h') + elif curLtr == 'k': + if prevLtr != 'c': result.append('k') + elif curLtr in 'wy': + if vowelAfter: + result.append(curLtr) + + return "".join(result) + +def demo(a): + print a, "=>", metaphone(a) + +if __name__ == '__main__': + demo("Nick. Mathewson") + + demo("joe schmidt") + demo("Beethoven") + + demo("Because the world is round") diff --git a/i2p2www/anonbib/rank.py b/i2p2www/anonbib/rank.py new file mode 100644 index 00000000..175a10d6 --- /dev/null +++ b/i2p2www/anonbib/rank.py @@ -0,0 +1,202 @@ +# Make rankings of papers and authors for automatic classification of content hotness + +# Google Scholar address +# http://scholar.google.com/scholar?as_epq= + +# Take care of the caching setup +cache_expire = 60*60*24*30 # 30 days + +# Checks +import config +import os +import sys +from os.path import exists, isdir, join, getmtime +from os import listdir, remove + +def remove_old(): + # Remove all old cached files + filenames = listdir(cache_folder()) + from time import time + now = time() + for f in filenames: + pf = join(cache_folder(), f) + time_mt = getmtime(pf) + if now - time_mt > cache_expire: # 30 days + remove(pf) + +def cache_folder(): + r = join(config.OUTPUT_DIR, config.CITE_CACHE_DIR) + if not exists(r): + os.makedirs(r) + assert isdir(r) + return r + +import re +from urllib2 import urlopen, build_opener +from urllib import quote +from datetime import date +import hashlib + +# A more handy hash +def md5h(s): + m = hashlib.md5() + m.update(s) + return m.hexdigest() + +format_tested = 0 + +def getPageForTitle(title, cache=True, update=True, save=True): + #Returns (citation-count, scholar url) tuple, or (None,None) + global format_tested + if not format_tested and update: + format_tested = 1 + TestScholarFormat() + + # Do not assume that the title is clean + title = re.sub("\s+", " ", title) + title = re.sub("[^'a-zA-Z0-9\. \-\/:]", "", title) + title = re.sub("'\/", " ", title) + + # We rely on google scholar to return the article with this exact title + gurl = "http://scholar.google.com/scholar?as_q=&as_epq=%s&as_occt=title" + + url = gurl % quote(title) + + # Access cache or network + if exists(join(cache_folder(), md5h(url))) and cache: + return url, file(join(cache_folder(), md5h(url)),'r').read() + elif update: + print "Downloading rank for %r."%title + + # Make a custom user agent (so that we are not filtered by Google)! + opener = build_opener() + opener.addheaders = [('User-agent', 'Anon.Bib.0.1')] + + print "connecting..." + connection = opener.open(url) + print "reading" + page = connection.read() + print "done" + if save: + file(join(cache_folder(), md5h(url)),'w').write(page) + return url, page + else: + return url, None + +def getCite(title, cache=True, update=True, save=True): + url, page = getPageForTitle(title, cache=cache, update=update, save=save) + if not page: + return None,None + + # Check if it finds any articles + if len(re.findall("did not match any articles", page)) > 0: + return (None, None) + + # Kill all tags! + cpage = re.sub("<[^>]*>", "", page) + + # Add up all citations + s = sum([int(x) for x in re.findall("Cited by ([0-9]*)", cpage)]) + return (s, url) + +def getPaperURLs(title, cache=True, update=True, save=True): + url, page = getPageForTitle(title, cache=cache, update=update, save=save) + if not page: + return [] + pages = re.findall(r'\&\#x25ba\;.*class=fl href="([^"]*)"', page) + return pages + +def get_rank_html(title, years=None, base_url=".", update=True, + velocity=False): + s,url = getCite(title, update=update) + + # Paper cannot be found + if s is None: + return '' + + html = '' + + url = url.replace("&","&") + + # Hotness + H,h = 50,5 + if s >= H: + html += 'More than %s citations on Google Scholar' % (url,base_url,H,H) + elif s >= h: + html += 'More than %s citations on Google Scholar' % (url,base_url,h,h) + + # Only include the velocity if asked. + if velocity: + # Velocity + d = date.today().year - int(years) + if d >= 0: + if 2 < s / (d +1) < 10: + html += '' % base_url + if 10 <= s / (d +1): + html += '' % base_url + + return html + +def TestScholarFormat(): + # We need to ensure that Google Scholar does not change its page format under our feet + # Use some cases to check if all is good + print "Checking google scholar formats..." + stopAndGoCites = getCite("Stop-and-Go MIXes: Providing Probabilistic Anonymity in an Open System", False)[0] + dragonCites = getCite("Mixes protected by Dragons and Pixies: an empirical study", False, save=False)[0] + + if stopAndGoCites in (0, None): + print """OOPS.\n +It looks like Google Scholar changed their URL format or their output format. +I went to count the cites for the Stop-and-Go MIXes paper, and got nothing.""" + sys.exit(1) + + if dragonCites != None: + print """OOPS.\n +It looks like Google Scholar changed their URL format or their output format. +I went to count the cites for a fictitious paper, and found some.""" + sys.exit(1) + +def urlIsUseless(u): + if u.find("freehaven.net/anonbib/") >= 0: + # Our own cache is not the primary citation for anything. + return True + elif u.find("owens.mit.edu") >= 0: + # These citations only work for 'members of the MIT community'. + return True + else: + return False + +URLTYPES=[ "pdf", "ps", "txt", "ps_gz", "html" ] + +if __name__ == '__main__': + # First download the bibliography file. + import BibTeX + suggest = False + if sys.argv[1] == 'suggest': + suggest = True + del sys.argv[1] + + config.load(sys.argv[1]) + if config.CACHE_UMASK != None: + os.umask(config.CACHE_UMASK) + bib = BibTeX.parseFile(config.MASTER_BIB) + remove_old() + + print "Downloading missing ranks." + for ent in bib.entries: + getCite(ent['title'], cache=True, update=True) + + if suggest: + for ent in bib.entries: + haveOne = False + for utype in URLTYPES: + if ent.has_key("www_%s_url"%utype): + haveOne = True + break + if haveOne: + continue + print ent.key, "has no URLs given." + urls = [ u for u in getPaperURLs(ent['title']) if not urlIsUseless(u) ] + for u in urls: + print "\t", u + diff --git a/i2p2www/anonbib/reconcile.py b/i2p2www/anonbib/reconcile.py new file mode 100644 index 00000000..e601af48 --- /dev/null +++ b/i2p2www/anonbib/reconcile.py @@ -0,0 +1,292 @@ +#!/usr/bin/python2 +# Copyright 2003-2008, Nick Mathewson. See LICENSE for licensing info. + +"""Code to determine which entries are new and which are old. + + To scan a new file, run "python reconcile.py anonbib.cfg new-file.bib". This + will generate a new bibtex file called 'tmp.bib', with all the new entries + cleaned up a little, and all the duplicate entries commented out. +""" + +import sys +import re + +assert sys.version_info[:3] >= (2,2,0) + +import BibTeX +import config +import metaphone + +_MPCACHE = {} +def soundsLike(s1, s2): + c = _MPCACHE + s1 = clean(s1) + s2 = clean(s2) + try: + m1 = c[s1] + except KeyError: + m1 = c[s1] = metaphone.metaphone(s1) + try: + m2 = c[s2] + except KeyError: + m2 = c[s2] = metaphone.metaphone(s2) + + return m1 == m2 + +def mphone(s): + c = _MPCACHE + s = clean(s) + try: + return c[s] + except: + m = c[s] = metaphone.metaphone(s) + return m + +def clean(s): + s = re.sub(r'\s+', ' ', s) + s = s.strip() + return s + +class MasterBibTeX(BibTeX.BibTeX): + def __init__(self): + BibTeX.BibTeX.__init__(self) + + def buildIndex(self): + self.byTitle = {} + for ent in self.entries: + for t in self._titleForms(ent['title']): + self.byTitle.setdefault(t, []).append(ent) + + def _titleForms(self, title): + title = title.lower() + title = re.sub(r'\b(an|a|the|of)\b', "", title) + title = clean(title) + res = [ mphone(title) ] + if ':' in title: + for t in title.split(":"): + res.append(mphone(t.strip())) + #print "%r\n => %s" % (title,res) + return res + + def _titlesAlike(self, t1, t2): + t1 = clean(t1) + t2 = clean(t2) + if t1 == t2: + return 2 + tf1 = self._titleForms(t1) + tf2 = self._titleForms(t2) + for t in tf1: + if t in tf2: return 1 + return 0 + + def _authorsAlike(self, a1, a2): + if not soundsLike(" ".join(a1.last)," ".join(a2.last)): + return 0 + + if (a1.first == a2.first and a1.von == a2.von + and a1.jr == a2.jr): + return 2 + + + if soundsLike(" ".join(a1.first), " ".join(a2.first)): + return 1 + + if not a1.first or not a2.first: + return 1 + + if self._initialize(a1.first) == self._initialize(a2.first): + return 1 + + return 0 + + def _initialize(self, name): + name = " ".join(name).lower() + name = re.sub(r'([a-z])[a-z\.]*', r'\1', name) + name = clean(name) + return name + + def _authorListsAlike(self, a1, a2): + if len(a1) != len(a2): + return 0 + a1 = [ (a.last, a) for a in a1 ] + a2 = [ (a.last, a) for a in a2 ] + a1.sort() + a2.sort() + if len(a1) != len(a2): + return 0 + r = 2 + for (_, a1), (_, a2) in zip(a1,a2): + x = self._authorsAlike(a1,a2) + if not x: + return 0 + elif x == 1: + r = 1 + return r + + def _entryDatesAlike(self, e1, e2): + try: + if clean(e1['year']) == clean(e2['year']): + return 2 + else: + return 0 + except KeyError: + return 1 + + def includes(self, ent, all=0): + title = ent['title'] + candidates = [] + for form in self._titleForms(title): + try: + candidates.extend(self.byTitle[form]) + except KeyError: + pass + goodness = [] + for knownEnt in candidates: + match = (self._entryDatesAlike(ent, knownEnt) * + self._titlesAlike(ent['title'], knownEnt['title']) * + self._authorListsAlike(ent.parsedAuthor, + knownEnt.parsedAuthor) ) + if match: + goodness.append((match, knownEnt)) + goodness.sort() + if all: + return goodness + if goodness: + return goodness[-1] + else: + return None, None + + def demo(self): + for e in self.entries: + matches = self.includes(e, 1) + m2 = [] + mids = [] + for g,m in matches: + if id(m) not in mids: + mids.append(id(m)) + m2.append((g,m)) + matches = m2 + + if not matches: + print "No match for %s"%e.key + if matches[-1][1] is e: + print "%s matches for %s: OK."%(len(matches), e.key) + else: + print "%s matches for %s: %s is best!" %(len(matches), e.key, + matches[-1][1].key) + if len(matches) > 1: + for g, m in matches: + print "%%%% goodness", g + print m + + +def noteToURL(note): + " returns tp, url " + note = note.replace("\n", " ") + m = re.match(r'\s*(?:\\newline\s*)*\s*\\url{(.*)}\s*(?:\\newline\s*)*', + note) + if not m: + return None + url = m.group(1) + for suffix, tp in ((".html", "html"), + (".ps", "ps"), + (".ps.gz", "ps_gz"), + (".pdf", "pdf"), + (".txt", "txt")): + if url.endswith(suffix): + return tp,url + return "???", url + +all_ok = 1 +def emit(f,ent): + global all_ok + + errs = ent._check() + if master.byKey.has_key(ent.key.strip().lower()): + errs.append("ERROR: Key collision with master file") + + if errs: + all_ok = 0 + + note = ent.get("note") + if ent.getURL() and not note: + ent['note'] = "\url{%s}"%ent.getURL() + elif note: + m = re.match(r'\\url{(.*)}', note) + if m: + url = m.group(0) + tp = None + if url.endswith(".txt"): + tp = "txt" + elif url.endswith(".ps.gz"): + tp = "ps_gz" + elif url.endswith(".ps"): + tp = "ps_gz" + elif url.endswith(".pdf"): + tp = "pdf" + elif url.endswith(".html"): + tp = "html" + if tp: + ent['www_%s_url'%tp] = url + + if errs: + all_ok = 0 + for e in errs: + print >>f, "%%%%", e + + print >>f, ent.format(77, 4, v=1, invStrings=invStrings) + +def emitKnown(f, ent, matches): + print >>f, "%% Candidates are:", ", ".join([e.key for g,e in matches]) + print >>f, "%%" + print >>f, "%"+(ent.format(77,4,1,invStrings).replace("\n", "\n%")) + +if __name__ == '__main__': + if len(sys.argv) != 3: + print "reconcile.py expects 2 arguments" + sys.exit(1) + + config.load(sys.argv[1]) + + print "========= Scanning master ==========" + master = MasterBibTeX() + master = BibTeX.parseFile(config.MASTER_BIB, result=master) + master.buildIndex() + + print "========= Scanning new file ========" + try: + fn = sys.argv[2] + input = BibTeX.parseFile(fn) + except BibTeX.ParseError, e: + print "Error parsing %s: %s"%(fn,e) + sys.exit(1) + + f = open('tmp.bib', 'w') + keys = input.newStrings.keys() + keys.sort() + for k in keys: + v = input.newStrings[k] + print >>f, "@string{%s = {%s}}"%(k,v) + + invStrings = input.invStrings + + for e in input.entries: + if not (e.get('title') and e.get('author')): + print >>f, "%%\n%%%% Not enough information to search for a match: need title and author.\n%%" + emit(f, e) + continue + + matches = master.includes(e, all=1) + if not matches: + print >>f, "%%\n%%%% This entry is probably new: No match found.\n%%" + emit(f, e) + else: + print >>f, "%%" + print >>f, "%%%% Possible match found for this entry; max goodness",\ + matches[-1][0], "\n%%" + emitKnown(f, e, matches) + + if not all_ok: + print >>f, "\n\n\nErrors remain; not finished.\n" + + f.close() diff --git a/i2p2www/anonbib/silver.gif b/i2p2www/anonbib/silver.gif new file mode 100644 index 00000000..8a4ff291 Binary files /dev/null and b/i2p2www/anonbib/silver.gif differ diff --git a/i2p2www/anonbib/testbib/pdos.bib b/i2p2www/anonbib/testbib/pdos.bib new file mode 100644 index 00000000..65b24b72 --- /dev/null +++ b/i2p2www/anonbib/testbib/pdos.bib @@ -0,0 +1,1742 @@ +%% *** +%% *** ASK YOURSELF: +%% *** +%% *** Did I put it in the right section? +%% *** Did I include a `www_section' tag? +%% *** Did I include the page numbers? +%% *** Did I include the location of the conference (in the `address' tag)? +%% *** +%% *** When you are done editing this file, run this command: +%% *** ./mkpdospubs.pl pdos.bib ../pubs.html +%% *** + +@string{MIT = "Massachusetts Institute of Technology"} +@string{MIT-LCS = "{MIT} Laboratory for Computer Science"} +@string{ACMabbr = "{ACM}"} +@string{SOSP = ACMabbr # " {S}ymposium on {O}perating {S}ystems {P}rinciples"} +@string{IEEEabbr = "{IEEE}"} +@string{IEEECompSoc = IEEEabbr # " {C}omputer {S}ociety"} +@string{OSDI = "{USENIX} {S}ymposium on {O}perating {S}ystems {D}esign and {I}mplementation"} + +@string{PDOSWWW = "http://www.pdos.lcs.mit.edu"} + +%% P2P PAPERS + +@string{p2p = "Peer-to-peer Computing"} + +@inproceedings{ivy:osdi02, + title = "Ivy: A Read/Write Peer-to-peer File System", + author = "Athicha Muthitacharoen and Robert Morris and Thomer Gil and Benjie Chen", + crossref = osdi5, + www_section = p2p, + www_abstract_url = PDOSWWW # "/ivy/osdi02.html", + www_ps_url = PDOSWWW # "/ivy/osdi02.ps", + www_ps_gz_url = PDOSWWW # "/ivy/osdi02.ps.gz", + www_pdf_url = PDOSWWW # "/ivy/osdi02.pdf" +} + +@inproceedings{trie:iptps02, + title = "Efficient Peer-To-Peer Lookup Based on a Distributed Trie", + author = "Michael J. Freedman and Radek Vingralek", + crossref = "iptps02", + www_section = p2p, + www_abstract_url = PDOSWWW # "/papers/trie:iptps02/index.html", + www_ps_url = PDOSWWW # "/papers/trie:iptps02/trie:iptps02.ps", + www_ps_gz_url = PDOSWWW # "/papers/trie:iptps02/trie:iptps02.ps.gz", + www_pdf_url = PDOSWWW # "/papers/trie:iptps02/trie:iptps02.pdf" +} + +@inproceedings{chord:dns02, + title = "Serving DNS using Chord", + author = "Russ Cox and Athicha Muthitacharoen and Robert Morris", + crossref = "iptps02", + www_section = p2p, + www_abstract_url = PDOSWWW # "/papers/chord:dns02/index.html", + www_ps_url = PDOSWWW # "/papers/chord:dns02/chord:dns02.ps", + www_ps_gz_url = PDOSWWW # "/papers/chord:dns02/chord:dns02.ps.gz", + www_pdf_url = PDOSWWW # "/papers/chord:dns02/chord:dns02.pdf" +} + +@inproceedings{chord:security02, + title = "Security Considerations for Peer-to-Peer Distributed Hash Tables", + author = "Emil Sit and Robert Morris", + crossref = "iptps02", + www_section = p2p, + www_abstract_url = PDOSWWW # "/papers/chord:security02/index.html", + www_ps_url = PDOSWWW # "/papers/chord:security02/chord:security02.ps", + www_ps_gz_url = PDOSWWW # "/papers/chord:security02/chord:security02.ps.gz", + www_pdf_url = PDOSWWW # "/papers/chord:security02/chord:security02.pdf" +} + +@inproceedings{cfs:sosp01, + title = "Wide-area cooperative storage with {CFS}", + author = "Frank Dabek and M. Frans Kaashoek and David Karger and Robert Morris and Ion Stoica", + crossref = "sosp18", + pages = "", + www_section = p2p, + www_abstract_url = PDOSWWW # "/papers/cfs:sosp01/", + www_ps_url = PDOSWWW # "/papers/cfs:sosp01/cfs_sosp.ps", + www_ps_gz_url = PDOSWWW # "/papers/cfs:sosp01/cfs_sosp.ps.gz", + www_pdf_url = PDOSWWW # "/papers/cfs:sosp01/cfs_sosp.pdf", +} + +@inproceedings{chord:sigcomm01, + title = "Chord: A Scalable Peer-to-peer Lookup Service for Internet Applications", + author = "Ion Stoica and Robert Morris and David Karger and M. Frans Kaashoek and Hari Balakrishnan", + crossref = "sigcomm01", + pages = "", + www_section = p2p, + www_abstract_url = PDOSWWW # "/papers/chord:sigcomm01/", + www_ps_url = PDOSWWW # "/papers/chord:sigcomm01/chord_sigcomm.ps", + www_ps_gz_url = PDOSWWW # "/papers/chord:sigcomm01/chord_sigcomm.ps.gz", + www_pdf_url = PDOSWWW # "/papers/chord:sigcomm01/chord_sigcomm.pdf", +} + +@inproceedings{chord:hotos, + title = "Building Peer-to-Peer Systems With Chord, a Distributed Lookup Service", + author = "Frank Dabek and Emma Brunskill and M. Frans Kaashoek and David Karger and Robert Morris and Ion Stoica and Hari Balakrishnan", + crossref = "hotos8", + pages = "", + www_section = p2p, + www_abstract_url = PDOSWWW # "/papers/chord:hotos01/", + www_ps_url = PDOSWWW # "/papers/chord:hotos01/hotos8.ps", + www_ps_gz_url = PDOSWWW # "/papers/chord:hotos01/hotos8.ps.gz", + www_pdf_url = PDOSWWW # "/papers/chord:hotos01/hotos8.pdf", +} + + +%% NETWORKING PAPERS + +@string{networking = "Networking and Communication"} + +@inproceedings{click:asplos02, + title = "Programming Language Optimizations for Modular Router Configurations", + author = "Eddie Kohler and Robert Morris and Benjie Chen", + booktitle = "Proceedings of the 10th Conference on Architectural Support for Programming Languages and Operating Systems (ASPLOS)", + location = "San Jose, CA", + month = oct, + year = 2002, + www_section = networking, + www_pdf_url = PDOSWWW # "/papers/click:asplos02.pdf" +} + +@inproceedings{grid:hotnets02, + title = "Performance of Multihop Wireless Networks: Shortest Path is Not Enough", + author = "Douglas S. J. {De Couto} and Daniel Aguayo and Benjamin A. Chambers and Robert Morris", + crossref = "hotnets1", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/grid:hotnets02/", + www_ps_url = PDOSWWW # "/papers/grid:hotnets02/paper.ps", + www_ps_gz_url = PDOSWWW # "/papers/grid:hotnets02/paper.ps.gz", + www_pdf_url = PDOSWWW # "/papers/grid:hotnets02/paper.pdf" +} + +@techreport{grid:losstr01, + title = "Effects of Loss Rate on Ad Hoc Wireless Routing", + author = "Douglas S. J. {De Couto} and Daniel Aguayo and Benjamin A. Chambers and Robert Morris", + institution = MIT-LCS, + year = 2002, month = mar, + number = "MIT-LCS-TR-836", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/grid:losstr02/", + www_ps_url = PDOSWWW # "/papers/grid:losstr02/paper.ps", + www_ps_gz_url = PDOSWWW # "/papers/grid:losstr02/paper.ps.gz", + www_pdf_url = PDOSWWW # "/papers/grid:losstr02/paper.pdf" +} + + +@article{span:wireless01, + title = "Span: An Energy-Efficient Coordination Algorithm for Topology Maintenance in Ad Hoc Wireless Networks", + author = "Benjie Chen and Kyle Jamieson and Hari Balakrishnan and Robert Morris", + crossref = "journal:winet", + volume = 8, + number = "5", + year = 2002, + month = sep, + pages = "", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/span:wireless01/", + www_ps_url = PDOSWWW # "/papers/span:wireless01/paper.ps", + www_ps_gz_url = PDOSWWW # "/papers/span:wireless01/paper.ps.gz", + www_pdf_url = PDOSWWW # "/papers/span:wireless01/paper.pdf" +} + +@inproceedings{dnscache:sigcommimw01, + title = "DNS Performance and the Effectiveness of Caching", + author = "Jaeyeon Jung, Emil Sit, Hari Balakrishnan and Robert Morris", + crossref = "sigcommimw01", + www_section = networking, + www_abstract_url = "http://nms.lcs.mit.edu/papers/dns-imw2001.html", + www_ps_url = "http://nms.lcs.mit.edu/papers/dns-imw2001.ps", + www_ps_gz_url = "http://nms.lcs.mit.edu/papers/dns-imw2001.ps.gz", + www_pdf_url = "http://nms.lcs.mit.edu/papers/dns-imw2001.pdf" +} + +@inproceedings{ron:sosp01, + title = "Resilient Overlay Networks", + author = "David Andersen and Hari Balakrishnan and M. Frans Kaashoek and Robert Morris", + crossref = "sosp18", + pages = "", + www_section = networking, + www_abstract_url = "http://nms.lcs.mit.edu/papers/ron-sosp2001.html", + www_ps_url = "http://nms.lcs.mit.edu/papers/ron-sosp2001.ps", + www_ps_gz_url = "http://nms.lcs.mit.edu/papers/ron-sosp2001.ps.gz", + www_pdf_url = "http://nms.lcs.mit.edu/papers/ron-sosp2001.pdf", +} + +@techreport{grid:proxytr01, + title = "Location Proxies and Intermediate Node Forwarding for Practical Geographic Forwarding", + author = "Douglas S. J. {De Couto} and Robert Morris", + institution = MIT-LCS, + year = 2001, month = jun, + number = "MIT-LCS-TR-824", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/grid:proxytr01/", + www_ps_url = PDOSWWW # "/papers/grid:proxytr01/paper.ps", + www_ps_gz_url = PDOSWWW # "/papers/grid:proxytr01/paper.ps.gz", + www_pdf_url = PDOSWWW # "/papers/grid:proxytr01/paper.pdf", +} + +@inproceedings{span:mobicom01, + title = "Span: An Energy-Efficient Coordination Algorithm for Topology Maintenance in Ad Hoc Wireless Networks", + author = "Benjie Chen and Kyle Jamieson and Hari Balakrishnan and Robert Morris", + crossref = "mobicom01", + pages = "85--96", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/span:mobicom01/", + www_ps_url = PDOSWWW # "/papers/span:mobicom01/span.ps", + www_ps_gz_url = PDOSWWW # "/papers/span:mobicom01/span.ps.gz", + www_pdf_url = PDOSWWW # "/papers/span:mobicom01/span.pdf" +} + +@inproceedings{grid:mobicom01, + title = "Capacity of Ad Hoc Wireless Networks", + author = "Jinyang Li and Charles Blake and Douglas S. J. {De Couto} and Hu Imm Lee and Robert Morris", + crossref = "mobicom01", + pages = "61--69", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/grid:mobicom01/", + www_ps_url = PDOSWWW # "/papers/grid:mobicom01/paper.ps", + www_ps_gz_url = PDOSWWW # "/papers/grid:mobicom01/paper.ps.gz", + www_pdf_url = PDOSWWW # "/papers/grid:mobicom01/paper.pdf" +} + +@inproceedings{click:usenix01, + title = "Flexible Control of Parallelism in a Multiprocessor PC Router", + author = "Benjie Chen and Robert Morris", + crossref = "usenix01", + pages = "333--346", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/click:usenix01/", + www_ps_url = PDOSWWW # "/papers/click:usenix01/usenix01.ps", + www_ps_gz_url = PDOSWWW # "/papers/click:usenix01/usenix01.ps.gz", + www_pdf_url = PDOSWWW # "/papers/click:usenix01/usenix01.pdf", +} + +@inproceedings{ron:hotos8, + title = "Resilient Overlay Networks", + author = "David Andersen and Hari Balakrishnan and M. Frans Kaashoek and Robert Morris", + crossref = "hotos8", + www_section = networking, + www_abstract_url = "http://nms.lcs.mit.edu/papers/ron-hotos2001.html", + www_ps_url = "http://nms.lcs.mit.edu/papers/ron-hotos2001.ps", + www_ps_gz_url = "http://nms.lcs.mit.edu/papers/ron-hotos2001.ps.gz", + www_pdf_url = "http://nms.lcs.mit.edu/papers/ron-hotos2001.pdf", +} + +@techreport{click:rewritertr, + title = "Modular components for network address translation", + author = "Eddie Kohler and Robert Morris and Massimiliano Poletto", + institution = "MIT LCS Click Project", + year = 2000, month = dec, + note = "http://www.pdos.lcs.mit.edu/papers/click-rewriter/", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/click-rewriter/", + www_ps_url = PDOSWWW # "/papers/click-rewriter/paper.ps", + www_ps_gz_url = PDOSWWW # "/papers/click-rewriter/paper.ps.gz", + www_pdf_url = PDOSWWW # "/papers/click-rewriter/paper.pdf", +} + +@inproceedings{grid:sigops-euro9, + title = "{C}ar{N}et: A Scalable Ad Hoc Wireless Network System", + author = "Robert Morris and John Jannotti and Frans Kaashoek and Jinyang Li and Douglas S. J. {De Couto}", + crossref = "sigops-euro9", + pages = "", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/grid:sigops-euro9/", + www_ps_gz_url = PDOSWWW # "/papers/grid:sigops-euro9/paper.ps.gz", + www_ps_url = PDOSWWW # "/papers/grid:sigops-euro9/paper.ps", + www_pdf_url = PDOSWWW # "/papers/grid:sigops-euro9/paper.pdf", + note = "The published version incorrectly lists Douglas De Couto's name" +} + +@inproceedings{grid:mobicom00, + title = "A Scalable Location Service for Geographic Ad Hoc Routing", + author = "Jinyang Li and John Jannotti and Douglas S. J. {De Couto} and David R. Karger and Robert Morris", + crossref = "mobicom00", + pages = "120--130", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/grid:mobicom00/", + www_ps_url = PDOSWWW # "/papers/grid:mobicom00/paper.ps", + www_ps_gz_url = PDOSWWW # "/papers/grid:mobicom00/paper.ps.gz", + www_pdf_url = PDOSWWW # "/papers/grid:mobicom00/paper.pdf" +} + +@techreport{click:lcstr00, + title = "Programming language techniques for modular router configurations", + author = "Eddie Kohler and Benjie Chen and M. Frans Kaashoek and Robert Morris and Massimiliano Poletto", + institution = MIT-LCS, + year = 2000, month = aug, + number = "MIT-LCS-TR-812", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/click:lcstr00/", + www_ps_url = PDOSWWW # "/papers/click:lcstr00/tr.ps", + www_ps_gz_url = PDOSWWW # "/papers/click:lcstr00/tr.ps.gz", + www_pdf_url = PDOSWWW # "/papers/click:lcstr00/tr.pdf", +} + +@article{click:tocs00, + title = "The Click modular router", + author = "Eddie Kohler and Robert Morris and Benjie Chen and John Jannotti and M. Frans Kaashoek", + crossref = "journal:tocs", + volume = 18, number = 3, + year = 2000, month = aug, + pages = "263--297", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/click:tocs00/", + www_ps_url = PDOSWWW # "/papers/click:tocs00/paper.ps", + www_ps_gz_url = PDOSWWW # "/papers/click:tocs00/paper.ps.gz", + www_pdf_url = PDOSWWW # "/papers/click:tocs00/paper.pdf" +} + +@inproceedings{click:sosp99, + title = "The {C}lick modular router", + author = "Robert Morris and Eddie Kohler and John Jannotti and M. Frans Kaashoek", + crossref = "sosp17", + pages = "217--231", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/click:sosp99/", + www_ps_url = PDOSWWW # "/papers/click:sosp99/paper.ps", + www_ps_gz_url = PDOSWWW # "/papers/click:sosp99/paper.ps.gz", + www_pdf_url = PDOSWWW # "/papers/click:sosp99/paper.pdf" +} + +@inproceedings{prolac:sigcomm99, + title = "A readable {TCP} in the {Prolac} protocol language", + author = "Eddie Kohler and M. Frans Kaashoek and David R. Montgomery", + crossref = "sigcomm99", + pages = "3--13", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/prolac:sigcomm99/", + www_ps_url = PDOSWWW # "/papers/prolac:sigcomm99/paper.ps", + www_pdf_url = PDOSWWW # "/papers/prolac:sigcomm99/paper.pdf" +} + +@inproceedings{ash:sigcomm96, + title = "{ASHs}: application-specific handlers for high-performance messaging", + author = "Deborah A. Wallach and Dawson R. Engler and M. Frans Kaashoek", + crossref = "sigcomm96", + pages = "40--52", + www_section = networking, + www_ps_url = PDOSWWW # "/papers/ash-sigcomm96.ps" +} + +@inproceedings{dpf:sigcomm96, + title = "{DPF}: fast, flexible message demultiplexing using dynamic code generation", + author = "Dawson R. Engler and M. Frans Kaashoek", + crossref = "sigcomm96", + pages = "53--59", + www_section = networking, + www_ps_url = PDOSWWW # "/papers/dpf.ps" +} + +@inproceedings{oam:ppopp95, + title = "Optimistic active messages: a mechanism for scheduling communication with computation", + author = "Deborah A. Wallach and Wilson C. Hsieh and Kirk Johnson and M. Frans Kaashoek and William E. Weihl", + crossref = "ppopp95", + pages = "217--226", + www_section = networking, + www_ps_url = PDOSWWW # "/papers/oam.ps" +} + +@techreport{user-level-comm:tr, + title = "Efficient implementation of high-level languages on user-level communication architectures", + author = "Wilson C. Hsieh and Kirk L. Johnson and M. Frans Kaashoek and Deborah A. Wallach and William E. Weihl", + institution = MIT-LCS, + year = 1994, month = may, + number = "MIT-LCS-TR-616", + www_section = networking, + www_ps_url = PDOSWWW # "/papers/UserLevelCommunication.ps", +} + +@inproceedings{ipc-persistent-relevance:wwos4, + title = "The persistent relevance of IPC performance", + author = "Wilson C. Hsieh and M. Frans Kaashoek and William E. Weihl", + crossref = "wwos4", + pages = "186--190", + www_section = networking, + www_ps_url = PDOSWWW # "/papers/RelevanceOfIPC.ps", +} + +@inproceedings{pan:openarch99, + title = "{PAN}: a high-performance active network node supporting multiple mobile code systems", + author = "Erik L. Nygren and Stephen J. Garland and M. Frans Kaashoek", + crossref = "openarch99", + pages = "78--89", + www_section = networking, + www_abstract_url = PDOSWWW # "/papers/pan-openarch99/", + www_ps_url = PDOSWWW # "/papers/pan-openarch99/pan-openarch99.ps", + www_ps_gz_url = PDOSWWW # "/papers/pan-openarch99/pan-openarch99.ps.gz", + www_pdf_url = PDOSWWW # "/papers/pan-openarch99/pan-openarch99.pdf", +} + +%% DISTRIBUTED COMPUTING + +@string{distribcomp = "Distributed Computing"} + +@inproceedings{lbfs:sosp01, + title = "A Low-bandwidth Network File System", + author = "Athicha Muthitacharoen and Benjie Chen and David Mazi{\`e}res", + crossref = "sosp18", + pages = "174--187", + www_section = distribcomp, + www_abstract_url = PDOSWWW # "/papers/lbfs:sosp01/", + www_ps_url = PDOSWWW # "/papers/lbfs:sosp01/lbfs.ps", + www_ps_gz_url = PDOSWWW # "/papers/lbfs:sosp01/lbfs.ps.gz", + www_pdf_url = PDOSWWW # "/papers/lbfs:sosp01/lbfs.pdf", +} + +@inproceedings{server-os:sigops-euro, + title = "Server operating systems", + author = "M. Frans Kaashoek and Dawson R. Engler and Gregory R. Ganger and Deborah A. Wallach", + crossref = "sigops-euro7", + pages = "141--148", + www_section = distribcomp, + www_html_url = PDOSWWW # "/papers/serverOS.html" +} + +@inproceedings{amoeba-eval:dcs16, + title = "An evaluation of the {Amoeba} group communication system", + author = "M. Frans Kaashoek and Andrew S. Tanenbaum", + crossref = "dcs16", + pages = "436--448", + www_section = distribcomp, + www_ps_url = PDOSWWW # "/papers/group-dcs16.ps" +} + + +%% SECURITY AND PRIVACY + +@string{security = "Security and Privacy"} + +@techreport{sfs:rex, + title = "REX: Secure, modular remote execution through file descriptor passing", + author = "Michael Kaminsky and Eric Peterson and Kevin Fu and David Mazi{\`e}res and M. Frans Kaashoek", + institution = "MIT-LCS", + year = 2003, month = jan, + number = "MIT-LCS-TR-884", + note = "http://www.pdos.lcs.mit.edu/papers/sfs:rex/", + www_section = security, + www_abstract_url = PDOSWWW # "/papers/sfs:rex/", + www_ps_url = PDOSWWW # "/papers/sfs:rex/MIT-LCS-TR-884.ps", + www_ps_gz_url = PDOSWWW # "/papers/sfs:rex/MIT-LCS-TR-884.ps.gz", + www_pdf_url = PDOSWWW # "/papers/sfs:rex/MIT-LCS-TR-884.pdf", +} + +@inproceedings{tarzan:ccs9, + title = "Tarzan: A Peer-to-Peer Anonymizing Network Layer", + author = "Michael J. Freedman and Robert Morris", + crossref = "ccs9", + www_section = security, + www_abstract_url = PDOSWWW # "/papers/tarzan:ccs9/index.html", + www_ps_url = PDOSWWW # "/papers/tarzan:ccs9/tarzan:ccs9.ps", + www_ps_gz_url = PDOSWWW # "/papers/tarzan:ccs9/tarzan:ccs9.ps.gz", + www_pdf_url = PDOSWWW # "/papers/tarzan:ccs9/tarzan:ccs9.pdf" +} + +@inproceedings{tarzan:iptps02, + title = "Introducing Tarzan, a Peer-to-Peer Anonymizing Network Layer", + author = "Michael J. Freedman and Emil Sit and Josh Cates and Robert Morris", + crossref = "iptps02", + www_section = security, + www_abstract_url = PDOSWWW # "/papers/tarzan:iptps02/index.html", + www_ps_url = PDOSWWW # "/papers/tarzan:iptps02/tarzan:iptps02.ps", + www_ps_gz_url = PDOSWWW # "/papers/tarzan:iptps02/tarzan:iptps02.ps.gz", + www_pdf_url = PDOSWWW # "/papers/tarzan:iptps02/tarzan:iptps02.pdf" +} + +@article{sfsro:tocs2002, + title = "{F}ast and secure distributed read-only file system", + author = "Kevin Fu and M. Frans Kaashoek and David Mazi{\`e}res", + crossref = "journal:tocs", + volume = 20, number = 1, + year = 2002, month = feb, + pages = "1--24", + www_section = security, + www_abstract_url = "http://portal.acm.org/citation.cfm?doid=505452.505453" +} + + +@inproceedings{webauth:sec10, + title = "{D}os and Don'ts of Client Authentication on the Web", + author = "Kevin Fu and Emil Sit and Kendra Smith and Nick Feamster", + crossref = "sec10", + www_section = security, + www_abstract_url = PDOSWWW # "/papers/webauth.html", + www_ps_url = PDOSWWW # "/papers/webauth:sec10.ps", + www_pdf_url = PDOSWWW # "/papers/webauth:sec10.pdf", + www_ps_gz_url = PDOSWWW # "/papers/webauth:sec10.ps.gz", + note = "An extended version is available as MIT-LCS-TR-818", +} + +@techreport{webauth:tr, + title = "{D}os and Don'ts of Client Authentication on the Web", + author = "Kevin Fu and Emil Sit and Kendra Smith and Nick Feamster", + institution = MIT-LCS, + year = 2001, month = may, + number = "MIT-LCS-TR-818", + www_section = security, + www_abstract_url = PDOSWWW # "/papers/webauth.html", + www_ps_url = PDOSWWW # "/papers/webauth:tr.ps", + www_pdf_url = PDOSWWW # "/papers/webauth:tr.pdf", + www_ps_gz_url = PDOSWWW # "/papers/webauth:tr.ps.gz", +} + +@inproceedings{sfsro:osdi2000, + title = "{F}ast and secure distributed read-only file system", + author = "Kevin Fu and M. Frans Kaashoek and David Mazi{\`e}res", + crossref = "osdi4", + pages = "181-196", + www_section = security, + www_abstract_url = PDOSWWW # "/papers/sfsro.html", + www_ps_url = PDOSWWW # "/papers/sfsro:osdi2000.ps", + www_pdf_url = PDOSWWW # "/papers/sfsro:osdi2000.pdf", + www_ps_gz_url = PDOSWWW # "/papers/sfsro:osdi2000.ps.gz", +} + +@inproceedings{sfs:sosp99, + title = "{S}eparating key management from file system security", + author = "David Mazi{\`e}res and Michael Kaminsky and M. Frans Kaashoek and Emmett Witchel", + crossref = "sosp17", + pages = "", + www_section = security, + www_ps_gz_url = PDOSWWW # "/papers/sfs:sosp99.ps.gz", + www_pdf_url = PDOSWWW # "/papers/sfs:sosp99.pdf", +} + +@inproceedings{nymserver:ccs5, + title = "The design, implementation and operation of an email pseudonym server", + author = "David Mazi{\`e}res and M. Frans Kaashoek", + crossref = "ccs5", + pages = "27--36", + www_section = security, + www_ps_gz_url = PDOSWWW # "/papers/nymserver:ccs5.ps.gz", + www_pdf_url = PDOSWWW # "/papers/nymserver:ccs5.pdf", +} + +@inproceedings{sfs:sigops-euro8, + title = "Escaping the evils of centralized control with self-certifying pathnames", + author = "David Mazi{\`e}res and M. Frans Kaashoek", + crossref = "sigops-euro8", + pages = "", + www_section = security, + www_ps_gz_url = PDOSWWW # "/papers/sfs:sigops-euro8.ps.gz" +} + +@inproceedings{secure-apps:hotos6, + title = "Secure applications need flexible operating systems", + author = "David Mazi{\`e}res and M. Frans Kaashoek", + pages = "56--61", + crossref = "hotos6", + www_section = security, + www_ps_gz_url = PDOSWWW # "/papers/mazieres:hotos6.ps.gz", +} + + +%% MOBILE COMPUTING + +@string{mobilecomp = "Mobile Computing"} + +@inproceedings{migrate:hotos8, + title = "Reconsidering Internet Mobility", + author = "Alex C. Snoeren and Hari Balakrishnan and M. Frans Kaashoek", + crossref = "hotos8", + www_section = mobilecomp, + www_abstract_url = "http://nms.lcs.mit.edu/papers/migrate-hotOS.html", + www_ps_url = "http://nms.lcs.mit.edu/papers/migrate-hotOS.ps", + www_pdf_url = "http://nms.lcs.mit.edu/papers/migrate-hotOS.pdf", +} + +@misc{rover:rfs-wip, + title = "{RFS}: a mobile-transparent file system for the {Rover} toolkit", + author = "Anthony D. Joseph and George M. Candea and M. Frans Kaashoek", + howpublished = "Works-in-progress poster, the 16th " # SOSP, + crossref = "sosp16", + www_section = mobilecomp, + www_ps_url = PDOSWWW # "/papers/RFS_SOSP_WIP.ps" + www_show = no, +} + +@article{rover:winet, + title = "Building reliable mobile-aware applications using the {Rover} toolkit", + author = "Anthony D. Joseph and M. Frans Kaashoek", + crossref = "journal:winet", + volume = 3, number = 5, + year = 1997, + pages = "405--419", + www_section = mobilecomp, + www_ps_url = PDOSWWW # "/papers/winet.ps" + www_ps_gz_url = PDOSWWW # "/papers/winet.ps.gz" +} + +@article{rover:ieee-toc, + title = "Mobile computing with the {Rover} toolkit", + author = "Anthony D. Joseph and Joshua A. Tauber and M. Frans Kaashoek", + crossref = "journal:ieee-toc", + volume = 46, number = 3, + year = 1997, month = mar, + pages = "337--352", + www_section = mobilecomp, + www_ps_url = PDOSWWW # "/papers/toc.ps" + www_ps_gz_url = PDOSWWW # "/papers/toc.ps.gz" +} + +@inproceedings{rover:mobicom, + title = "Building reliable mobile-aware applications using the {Rover} toolkit", + author = "Anthony D. Joseph and Joshua A. Tauber and M. Frans Kaashoek", + crossref = "mobicom96", + www_section = mobilecomp, + www_ps_url = PDOSWWW # "/papers/mobicom96.ps", + www_ps_gz_url = PDOSWWW # "/papers/mobicom96.ps.gz", +} + +@inproceedings{rover:sosp95, + title = "{Rover}: a toolkit for mobile information access", + author = "Anthony D. Joseph and {deLespinasse}, Alan F. and Joshua A. Tauber and David K. Gifford and M. Frans Kaashoek", + crossref = "sosp15", + pages = "156--171", + www_section = mobilecomp, + www_ps_url = PDOSWWW # "/papers/rover-sosp95.ps", + www_ps_gz_url = PDOSWWW # "/papers/rover-sosp95.ps.gz", +} + +@inproceedings{dynamic-documents:wmcsa, + title = "Dynamic documents: mobile wireless access to the {WWW}", + author = "M. Frans Kaashoek and Tom Pinckney and Joshua A. Tauber", + crossref = "wmcsa94", + pages = "179--184", + www_section = mobilecomp, + www_abstract_url = PDOSWWW # "/papers/wmcsa94.abstract.html", + www_ps_url = PDOSWWW # "/papers/wmcsa94.ps", + www_ps_gz_url = PDOSWWW # "/papers/wmcsa94.ps.gz", +} + +@inproceedings{mobile-storage-alt:osdi1, + title = "Storage alternatives for mobile computers", + author = "Fred Douglis and Ramón Cáceres and M. Frans Kaashoek and Kai Li and Brian Marsh and Joshua A. Tauber", + crossref = "osdi1", + pages = "25--37", + www_section = mobilecomp, + www_ps_url = PDOSWWW # "/papers/storage-alternatives.ps" +} + +@inproceedings{dynamic-documents:www94, + title = "Dynamic documents: extensibility and adaptability in the {WWW}", + author = "M. Frans Kaashoek and Tom Pinckney and Joshua A. Tauber", + crossref = "www94", + edition = "developers' day track", + www_section = mobilecomp, + www_ps_url = PDOSWWW # "/papers/www94.ps", + www_ps_gz_url = PDOSWWW # "/papers/www94.ps.gz", + www_html_url = PDOSWWW # "/papers/www94.html", +} + + +%% STORAGE MANAGEMENT + +@string{storage = "Storage Management"} + +@inproceedings{cffs:usenix97, + title = "Embedded inodes and explicit grouping: exploiting disk bandwidth for small files", + author = "Gregory R. Ganger and M. Frans Kaashoek", + crossref = "usenix97", + pages = "1--17", + www_section = storage, + www_abstract_url = PDOSWWW # "/papers/cffs.html", + www_ps_url = PDOSWWW # "/papers/cffs-usenix97.ps", + www_ps_gz_url = PDOSWWW # "/papers/cffs-usenix97.ps.gz", +} + +@inproceedings{arus:dcs16, + title = "Atomic recovery units: failure atomicity for logical disks", + author = "Robert Grimm and Wilson C. Hsieh and Wiebren de Jonge and M. Frans Kaashoek", + crossref = "dcs16", + pages = "26--37", + www_section = storage, + www_ps_url = PDOSWWW # "/papers/arus.ps", +} + +@inproceedings{logicaldisk:sosp14, + title = "The logical disk: a new approach to improving file systems", + author = "Wiebren de Jonge and M. Frans Kaashoek and Wilson C. Hsieh", + crossref = "sosp14", + pages = "15--28", + www_section = storage, + www_ps_url = PDOSWWW # "/papers/LogicalDisk.ps" +} + + +%% EXOKERNEL PAPERS + +@string{exokernels = "Exokernels"} + +@article{exo:tocs2002, + title = "{F}ast and flexible Application-Level Networking on Exokernel Systems", + author = "Gregory R. Ganger and Dawson R. Engler and M. Frans Kaashoek and Hector M. Briceno and Russell Hunt and Thomas Pinckney", + crossref = "journal:tocs", + volume = 20, + number = 1, + year = 2002, + month = feb, + pages = "49--83", + www_section = exokernels, + www_abstract_url = PDOSWWW # "papers/exo:tocs.html", + www_pdf_url = PDOSWWW # "papers/exo:tocs.pdf", + www_ps_url = PDOSWWW # "papers/exo:tocs.ps", + www_ps_gz_url = PDOSWWW # "papers/exo:tocs.ps.gz" +} + +@inproceedings{exo:sosp97, + title = "Application performance and flexibility on exokernel systems", + author = "M. Frans Kaashoek and Dawson R. Engler and Gregory R. Ganger and H{\'e}ctor M. Brice{\~n}o and Russell Hunt and David Mazi{\`e}res and Thomas Pinckney and Robert Grimm and John Jannotti and Kenneth Mackenzie", + pages = "52--65", + crossref = "sosp16", + www_section = exokernels, + www_abstract_url = PDOSWWW # "/papers/exo-sosp97.html", + www_html_url = PDOSWWW # "/papers/exo-sosp97/exo-sosp97.html", + www_ps_url = PDOSWWW # "/papers/exo-sosp97/exo-sosp97.ps", + www_ps_gz_url = PDOSWWW # "/papers/exo-sosp97/exo-sosp97.ps.gz", +} + +@inproceedings{exo:sosp95, + title = "{E}xokernel: an operating system architecture for application-level resource management", + author = "Dawson R. Engler and M. Frans Kaashoek and James {O'Toole Jr.}", + pages = "251--266", + crossref = "sosp15", + www_section = exokernels, + www_ps_url = PDOSWWW # "/papers/exokernel-sosp95.ps", +} + +@inproceedings{exo:osdi1, + title = "The exokernel approach to extensibility (panel statement)", + author = "Dawson R. Engler and M. Frans Kaashoek and {O'Toole Jr.}, James W.", + pages = "198", + crossref = "osdi1", + www_section = exokernels, + www_ps_url = PDOSWWW # "/papers/exo-abstract.ps", +} + +@inproceedings{exo:hotos5, + title = "Exterminate all operating system abstractions", + author = "Dawson R. Engler and M. Frans Kaashoek", + pages = "78--83", + crossref = "hotos5", + www_section = exokernels, + www_ps_url = PDOSWWW # "/papers/hotos-jeremiad.ps", +} + +@article{exo:osr, + title = "The operating system kernel as a secure programmable machine", + author = "Dawson R. Engler and M. Frans Kaashoek and {O'Toole Jr.}, James W.", + crossref = "journal:osr", + year = 1995, month = jan, + volume = 29, number = 1, + pages = "78--82", + www_section = exokernels, + www_ps_url = PDOSWWW # "/papers/osr-exo.ps", +} + +@inproceedings{exo:sigops-euro, + title = "The operating system kernel as a secure programmable machine", + author = "Dawson R. Engler and M. Frans Kaashoek and {O'Toole Jr.}, James W.", + crossref = "sigops-euro6", + pages = "62--67", + www_section = exokernels, + www_ps_url = PDOSWWW # "/papers/xsigops.ps", +} + + +%% DYNAMIC CODE GENERATION + +@string{dcg = "Dynamic Code Generation"} + +@article{tickc:toplas, + title = "{`C} and {tcc}: A language and compiler for dynamic code generation" + author = "Massimiliano Poletto and Wilson C. Hsieh and Dawson R. Engler and M. Frans Kaashoek", + crossref = "journal:toplas", + volume = 21, number = 2, + year = 1999, month = mar, + pages = "324--369", + www_section = dcg, + www_ps_url = PDOSWWW # "/papers/tickc-toplas.ps", +} + +@article{linearscan, + title = "Linear scan register allocation", + author = "Massimiliano Poletto and Vivek Sarkar", + crossref = "journal:toplas", + volume = 21, number = 5, + year = 1999, month = sep, + pages = "895--913", + www_section = dcg, + www_ps_url = PDOSWWW # "/papers/toplas-linearscan.ps", +} + +@inproceedings{tickc:pldi97, + title = "tcc: a system for fast, flexible, and high-level dynamic code generation", + author = "Massimiliano Poletto and Dawson R. Engler and M. Frans Kaashoek", + crossref = "pldi97", + pages = "109--121", + www_section = dcg, + www_ps_url = PDOSWWW # "/papers/tcc-pldi97.ps", +} + +@inproceedings{tickc:popl96, + title = "{`C}: A language for efficient, machine-independent dynamic code generation", + author = "Dawson R. Engler and Wilson C. Hsieh and M. Frans Kaashoek", + crossref = "popl96", + pages = "131--144", + www_section = dcg, + www_ps_url = PDOSWWW # "/papers/popl96.ps", + note = "An earlier version is available as MIT-LCS-TM-526", +} + +@inproceedings{tickc:wcsss96, + title = "tcc: a template-based compiler for {`C}", + author = "Massimiliano Poletto and Dawson R. Engler and M. Frans Kaashoek", + crossref = "wcsss96", + pages = "1--7", + www_section = dcg, + www_ps_url = PDOSWWW # "/papers/tcc-wcsss96.ps" +} + +@inproceedings{vcode:pldi96, + title = "{VCODE}: a retargetable, extensible, very fast dynamic code generation system", + author = "Dawson R. Engler", + crossref = "pldi96", + pages = "160--170", + www_section = dcg, + www_ps_url = PDOSWWW # "/papers/vcode-pldi96.ps", +} + +@inproceedings{dcg:asplos6, + title = "{DCG}: an efficient, retargetable dynamic code generation system", + author = "Dawson R. Engler and Todd A. Proebsting", + crossref = "asplos6", + pages = "263--272", + www_section = dcg, + www_ps_url = PDOSWWW # "/papers/dcg.ps", +} + + +%% PROGRAMMING LANGUAGES + +@string{proglang = "Programming Languages"} + +@inproceedings{pct:usenix02, + title = "Simple and General Statistical Profiling with PCT", + author = "Charles Blake and Steve Bauer", + crossref = "usenix02", + pages = "333--346" + www_section = proglang, + www_abstract_url = PDOSWWW # "/papers/pct:usenix02/", + www_ps_url = PDOSWWW # "/papers/pct:usenix02/blake02:pct.ps", + www_ps_gz_url = PDOSWWW # "/papers/pct:usenix02/blake02:pct.ps.gz", + www_pdf_url = PDOSWWW # "/papers/pct:usenix02/blake02:pct.pdf", +} + +@inproceedings{evolving-software:wcsss99, + title = "Evolving software with an application-specific language", + author = "Eddie Kohler and Massimiliano Poletto and David R. Montgomery", + crossref = "wcsss99", + pages = "94--102", + www_section = proglang, + www_abstract_url = PDOSWWW # "/papers/evolving-software:wcsss99/", + www_ps_url = PDOSWWW # "/papers/evolving-software:wcsss99/paper.ps", + www_pdf_url = PDOSWWW # "/papers/evolving-software:wcsss99/paper.pdf", +} + + +%% STORAGE MANAGEMENT + +@string{storage = "Storage Management"} + +@inproceedings{cffs:usenix97, + title = "Embedded inodes and explicit grouping: exploiting disk bandwidth for small files", + author = "Gregory R. Ganger and M. Frans Kaashoek", + crossref = "usenix97", + pages = "1--17", + www_section = storage, + www_abstract_url = PDOSWWW # "/papers/cffs.html", + www_ps_url = PDOSWWW # "/papers/cffs-usenix97.ps", + www_ps_gz_url = PDOSWWW # "/papers/cffs-usenix97.ps.gz", +} + +@inproceedings{arus:dcs16, + title = "Atomic recovery units: failure atomicity for logical disks", + author = "Robert Grimm and Wilson C. Hsieh and Wiebren de Jonge and M. Frans Kaashoek", + crossref = "dcs16", + pages = "26--37", + www_section = storage, + www_ps_url = PDOSWWW # "/papers/arus.ps", +} + +@inproceedings{logicaldisk:sosp14, + title = "The logical disk: a new approach to improving file systems", + author = "Wiebren de Jonge and M. Frans Kaashoek and Wilson C. Hsieh", + crossref = "sosp14", + pages = "15--28", + www_section = storage, + www_ps_url = PDOSWWW # "/papers/LogicalDisk.ps" +} + + +%% VIRTUAL MEMORY + +@string{vm = "Virtual Memory"} + +@inproceedings{avm:hotos5, + title = "{AVM}: application-level virtual memory", + author = "Dawson R. Engler and Sandeep K. Gupta and M. Frans Kaashoek", + crossref = "hotos5", + pages = "72--77", + www_section = vm, + www_ps_url = PDOSWWW # "/papers/hotos-uvm.ps", +} + +@inproceedings{software-tlb-prefetch:osdi1, + title = "Software prefetching and caching for translation lookaside buffers", + author = "Kavita Bala and M. Frans Kaashoek and William Weihl", + crossref = "osdi1", + pages = "243--253", + www_section = vm, + www_ps_url = PDOSWWW # "/papers/tlb.ps", +} + + + + +%% DISTRIBUTED SHARED MEMORY AND PARALLEL COMPUTING + +@string{dsm/parallel = "Distributed Shared Memory and Parallel Computing"} + +@inproceedings{dynamic-migration:supercomp96, + title = "Dynamic computation migration in distributed +shared memory systems", + author = "Wilson C. Hsieh and M. Frans Kaashoek and William E. Weihl", + crossref = "supercomp96", + www_section = dsm/parallel, + www_ps_url = PDOSWWW # "/papers/mcrl.ps" +} + +@inproceedings{crl:sosp95, + title = "{CRL}: high-performance all-software distributed shared memory", + author = "Kirk L. Johnson and M. Frans Kaashoek and Deborah A. Wallach", + crossref = "sosp15", + pages = "213--226", + www_section = dsm/parallel, + www_ps_url = PDOSWWW # "/papers/crl-sosp95.ps" + note = "An earlier version of this work appeared as Technical Report MIT-LCS-TM-517, MIT Laboratory for Computer Science, March 1995", +} + +@inproceedings{formal-sequential-consistent:dcs15, + title = "Implementing sequentially consistent shared objects using broadcast and point-to-point communication", + author = "Alan Fekete and M. Frans Kaashoek and Nancy Lynch", + crossref = "dcs15", + pages = "439--449", + www_section = dsm/parallel, + www_ps_url = PDOSWWW # "/papers/formal.ps" +} + +@techreport{formal-sequential-consistent:tr, + title = "Implementing sequentially consistent shared objects using broadcast and point-to-point communication", + author = "Alan Fekete and M. Frans Kaashoek and Nancy Lynch", + institution = MIT-LCS, + year = 1995, month = jun, + number = "MIT-LCS-TR-518", + www_section = dsm/parallel, + www_ps_url = PDOSWWW # "/papers/formaltr.ps" +} + +%@inproceedings{triangle-puzzle:dimacs94, +% title = "A case study of shared-memory and +%message-passing implementations of parallel breadth-first search: The +%triangle puzzle", +% author = "Kevin Lew and Kirk Johnson and M. Frans Kaashoek", +% crossref = "dimacs94", +% www_section = dsm/parallel, +% www_ps_url = PDOSWWW # "/papers/dimacs94.ps" +%} + + +%% PHD THESES + +@string{phdtheses = "Ph.D. Theses"} + +@phdthesis{snoeren-phd, + title = "A Session-Based Architecture for Internet Mobility", + author = "Alex C. Snoeren", + school = MIT, + year = 2002, month = dec, + www_section = phdtheses, + www_ps_url = "http://nms.lcs.mit.edu/~snoeren/papers/thesis/thesis.ps", + www_ps_gz_url = "http://nms.lcs.mit.edu/~snoeren/papers/thesis/thesis.ps.gz" + www_pdf_url = "http://nms.lcs.mit.edu/~snoeren/papers/thesis/thesis.pdf", +} + +@phdthesis{jannotti-phd, + title = "Network Layer Support for Overlay Networks", + author = "John Jannotti", + school = MIT, + year = 2002, month = aug, + www_section = phdtheses, + www_ps_url = PDOSWWW # "/papers/jannotti-phd.ps", + www_ps_gz_url = PDOSWWW # "/papers/jannotti-phd.ps.gz", + www_pdf_url = PDOSWWW # "/papers/jannotti-phd.pdf" +} + +@phdthesis{click:kohler-phd, + title = "The Click modular router", + author = "Eddie Kohler", + school = MIT, + year = 2000, month = nov, + www_section = phdtheses, + www_ps_gz_url = PDOSWWW # "/papers/click:kohler-phd/thesis.ps.gz", + www_pdf_url = PDOSWWW # "/papers/click:kohler-phd/thesis.pdf" +} + +@phdthesis{sfs:mazieres-phd, + title = "Self-certifying File System", + author = "David Mazieres", + school = MIT, + year = 2000, month = may, + www_section = phdtheses, + www_ps_gz_url = PDOSWWW # "/papers/sfs:mazieres-phd.ps.gz" +} + +@phdthesis{tickc:poletto-phd, + title = "Language and compiler support for dynamic code generation", + author = "Massimiliano Poletto", + school = MIT, + year = 1999, month = jun, + www_section = phdtheses, + www_ps_url = PDOSWWW # "/papers/tickc-poletto-phd.ps", + www_ps_gz_url = PDOSWWW # "/papers/tickc-poletto-phd.ps.gz", + www_pdf_url = PDOSWWW # "/papers/tickc-poletto-phd.pdf" +} + +@phdthesis{exo:engler-phd, + title = "The exokernel operating system architecture", + author = "Dawson R. Engler", + school = MIT, + year = 1998, month = oct, + www_section = phdtheses, + www_ps_url = PDOSWWW # "/exo/theses/engler/thesis.ps", + www_ps_gz_url = PDOSWWW # "/exo/theses/engler/thesis.ps.gz", +} + +@phdthesis{fugu:mackenzie-phd, + title = "An efficient virtual network interface in the {FUGU} scalable workstation", + author = "Kenneth M. Mackenzie", + school = MIT, + year = 1998, month = feb, + www_section = phdtheses, + www_ps_gz_url = PDOSWWW # "/exo/theses/kenmac/thesis.ps.gz", +} + +@phdthesis{app-specific-networking:wallach-phd, + title = "High-performance application-specific networking", + author = "Deborah Anne Wallach", + school = MIT, + year = 1997, month = jan, + www_section = phdtheses, + www_ps_url = PDOSWWW # "/exo/theses/kerr/thesis.ps", + www_ps_gz_url = PDOSWWW # "/exo/theses/kerr/thesis.ps.gz", +} + +@phdthesis{crl:johnson-phd, + title = "High-performance all-software distributed shared memory", + author = "Kirk L. Johnson", + school = MIT, + year = 1995, month = dec, + www_section = phdtheses, + www_ps_gz_url = PDOSWWW # "/papers/crl:johnson-phd.ps.gz", + www_abstract_url = "http://www.cag.lcs.mit.edu/~tuna/papers/thesis.html", +} + +@phdthesis{dyn-comp-migration:hsieh-phd, + title = "Dynamic computation migration in distributed shared memory systems", + author = "Wilson C. Hsieh", + school = MIT, + year = 1995, month = sep, + www_section = phdtheses, + www_pdf_url = PDOSWWW # "/papers/dyn-comp-migration:hsieh-phd.pdf", + note = "Also available as MIT LCS tech report MIT-LCS-TR-665." +} + + +%% MASTERS THESES + +@string{masterstheses = "Master's Theses"} + +@mastersthesis{sfs:savvides-meng, + title = "Access Control Lists for the Self-Certifying Filesystem" + author = "George Savvides", + school = MIT, + year = 2002, month = Aug, + www_section = masterstheses, + www_pdf_url = PDOSWWW # "/papers/sfs:savvides-meng.pdf", + www_ps_url = PDOSWWW # "/papers/sfs:savvides-meng.ps", + www_ps_gz_url = PDOSWWW # "/papers/sfs:savvides-meng.ps.gz", +} + +@mastersthesis{sfs:euresti-meng, + title = "Self-Certifying Filesystem Implementation for Windows" + author = "David Euresti", + school = MIT, + year = 2002, month = Aug, + www_section = masterstheses, + www_pdf_url = PDOSWWW # "/papers/sfs:euresti-meng.pdf", + www_ps_url = PDOSWWW # "/papers/sfs:euresti-meng.ps", + www_ps_gz_url = PDOSWWW # "/papers/sfs:euresti-meng.ps.gz", +} + +@mastersthesis{sfs:zeldovich-meng, + title = "Concurrency Control for Multi-Processor Event-Driven Systems" + author = "Nickolai Zeldovich", + school = MIT, + year = 2002, month = May, + www_section = masterstheses, + www_pdf_url = PDOSWWW # "/papers/sfs:zeldovich-meng.pdf", + www_ps_url = PDOSWWW # "/papers/sfs:zeldovich-meng.ps", + www_ps_gz_url = PDOSWWW # "/papers/sfs:zeldovich-meng.ps.gz", +} + +@mastersthesis{chord:om_p-meng, + title = "A Keyword Set Search System for Peer-to-Peer Networks" + author = "Omprakash D Gnawali", + school = MIT, + year = 2002, month = Jun, + www_section = masterstheses, + www_pdf_url = PDOSWWW # "/papers/chord:om_p-meng.pdf", + www_ps_url = PDOSWWW # "/papers/chord:om_p-meng.ps", + www_ps_gz_url = PDOSWWW # "/papers/chord:om_p-meng.ps.gz", +} + +@mastersthesis{grid:bac-meng, + title = "The Grid Roofnet: a Rooftop Ad Hoc Wireless Network" + author = "Benjamin A. Chambers", + school = MIT, + year = 2002, month = May, + www_section = masterstheses, + www_pdf_url = PDOSWWW # "/papers/grid:bac-meng.pdf", + www_ps_url = PDOSWWW # "/papers/grid:bac-meng.ps", + www_ps_gz_url = PDOSWWW # "/papers/grid:bac-meng.ps.gz", +} + +@mastersthesis{tarzan:freedman-meng, + title = "A Peer-to-Peer Anonymizing Network Layer" + author = "Michael J. Freedman", + school = MIT, + year = 2002, month = May, + www_section = masterstheses, + www_abstract_url = PDOSWWW # "/papers/tarzan:freedman-meng/index.html", + www_pdf_url = PDOSWWW # "/papers/tarzan:freedman-meng/tarzan:freedman-meng.pdf", + www_ps_url = PDOSWWW # "/papers/tarzan:freedman-meng/tarzan:freedman-meng.ps", + www_ps_gz_url = PDOSWWW # "/papers/tarzan:freedman-meng/tarzan:freedman-meng.ps.gz", +} + + +@mastersthesis{chord:tburkard-meng, + title = "Herodotus: A Peer-to-Peer Web Archival System" + author = "Timo Burkard", + school = MIT, + year = 2002, month = May, + www_section = masterstheses, + www_pdf_url = PDOSWWW # "/papers/chord:tburkard-meng.pdf", + www_ps_url = PDOSWWW # "/papers/chord:tburkard-meng.ps", + www_ps_gz_url = PDOSWWW # "/papers/chord:tburkard-meng.ps.gz", +} + +@mastersthesis{cfs:dabek-meng, + title = "A Cooperative File System" + author = "Frank Dabek", + school = MIT, + year = 2001, month = September, + www_section = masterstheses, + www_pdf_url = PDOSWWW # "/papers/chord:dabek_thesis/dabek.pdf", + www_ps_url = PDOSWWW # "/papers/chord:dabek_thesis/dabek.ps", + www_ps_gz_url = PDOSWWW # "/papers/chord:dabek_thesis/tyan-meng.ps.gz", +} + +@mastersthesis{chord:tyan-meng, + title = "A Case Study of Server Selection", + author = "Tina Tyan", + school = MIT, + year = 2001, month = September, + www_section = masterstheses, + www_pdf_url = PDOSWWW # "/papers/chord:tyan-meng.pdf", + www_ps_url = PDOSWWW # "/papers/chord:tyan-meng.ps", + www_ps_gz_url = PDOSWWW # "/papers/chord:tyan-meng.ps.gz", +} + +@mastersthesis{click:gil-ms, + title = "MULTOPS: a data structure for denial-of-service attack detection", + author = "Thomer M. Gil", + school = "Vrije Universiteit", + year = 2000, month = August, + www_section = masterstheses, + www_ps_gz_url = PDOSWWW # "/papers/click:gil-ms.ps.gz", +} + +@mastersthesis{click:sit-ms, + title = "A Study of Caching in the Internet Domain Name System", + author = "Emil Sit", + school = MIT, + year = 2000, month = may, + www_section = masterstheses, + www_ps_gz_url = PDOSWWW # "/papers/click:sit-ms.ps.gz", +} + + +@mastersthesis{sfs:kaminsky-ms, + title = "Flexible Key Management with SFS Agents", + author = "Michael Kaminsky", + school = MIT, + year = 2000, month = may, + www_section = masterstheses, + www_ps_gz_url = PDOSWWW # "/papers/sfs:kaminsky-ms.ps.gz", + www_pdf_url = PDOSWWW # "/papers/sfs:kaminsky-ms.pdf", +} + +@mastersthesis{sfs:almeida-ms, + title = "Framework for Implementing File Systems in Windows NT", + author = "Danilo Almeida", + school = MIT, + year = 1998, month = may, + www_section = masterstheses, + www_ps_gz_url = PDOSWWW # "/papers/sfs:almeida-ms.ps.gz", + www_pdf_url = PDOSWWW # "/papers/sfs:almeida-ms.pdf", +} + +@mastersthesis{sfs:rimer-ms, + title = "The Secure File System under Windows NT", + author = "Matthew Rimer", + school = MIT, + year = 1999, month = June, + www_section = masterstheses, + www_ps_gz_url = PDOSWWW # "/papers/sfs:rimer-ms.ps.gz", + www_pdf_url = PDOSWWW # "/papers/sfs:rimer-ms.pdf", +} + +@mastersthesis{prolac:montgomery-meng, + title = "A fast {Prolac} {TCP} for the real world", + author = "Montgomery, Jr., David Rogers", + school = MIT, + year = 1999, month = may, + www_section = masterstheses, + www_ps_gz_url = PDOSWWW # "/papers/prolac:montgomery-meng.ps.gz", +} + +@mastersthesis{exo:coffing-meng, + title = "An x86 Protected Mode Virtual Machine Monitor for the MIT Exokernel", + author = "Charles L. Coffing", + school = MIT, + year = 1999, month = May, + www_section = masterstheses, + www_ps_url = PDOSWWW # "/papers/exo:coffing-meng.ps", + www_ps_gz_url = PDOSWWW # "/papers/exo:coffing-meng.ps.gz", +} + +@mastersthesis{exo:chen-meng, + title = "Multiprocessing with the Exokernel Operating System", + author = "Benjie Chen", + school = MIT, + year = 2000, month = February, + www_section = masterstheses, + www_html_url = PDOSWWW # "/papers/exo:chen-meng.html", + www_ps_url = PDOSWWW # "/papers/exo:chen-meng.ps", + www_pdf_url = PDOSWWW # "/papers/exo:chen-meng.pdf", + www_ps_gz_url = PDOSWWW # "/papers/exo:chen-meng.ps.gz", +} + +@mastersthesis{exo:candea-meng, + title = "Flexible and efficient sharing of protected abstractions", + author = "George M. Candea", + school = MIT, + year = 1998, month = may, + www_section = masterstheses, + www_abstract_url = PDOSWWW # "/papers/candea-meng.html", + www_ps_url = PDOSWWW # "/papers/ProtAbs.ps", + www_ps_gz_url = PDOSWWW # "/papers/ProtAbs.ps.gz", + www_pdf_url = PDOSWWW # "/papers/ProtAbs.pdf", +} + +@mastersthesis{exo-os:jj-meng, + title = "Applying Exokernel Principles to Conventional Operating Systems", + author = "John Jannotti", + school = MIT, + year = 1998, month = feb, + www_section = masterstheses, + www_ps_url = PDOSWWW # "/papers/jj-meng-exo-feb98.ps", + www_ps_gz_url = PDOSWWW # "/papers/jj-meng-exo-feb98.ps.gz", + www_pdf_url = PDOSWWW # "/papers/jj-meng-exo-feb98.pdf", +} + +@mastersthesis{pan:nygren-meng, + title = "The design and implementation of a high-performance active network node", + author = "Erik L. Nygren", + school = MIT, + year = 1998, month = feb, + www_section = masterstheses, + www_abstract_url = PDOSWWW # "/papers/nygren-mengthesis-pan-feb98.html", + www_ps_url = PDOSWWW # "/papers/nygren-mengthesis-pan-feb98.ps", + www_ps_gz_url = PDOSWWW # "/papers/nygren-mengthesis-pan-feb98.ps.gz", + www_pdf_url = PDOSWWW # "/papers/nygren-mengthesis-pan-feb98.pdf", +} + +@mastersthesis{exo:wyatt-meng, + title = "Shared libraries in an exokernel operating system", + author = "Douglas Karl Wyatt", + school = MIT, + year = 1997, month = sep, + www_section = masterstheses, + www_ps_url = PDOSWWW # "/exo/theses/dwyatt/thesis.ps", + www_ps_gz_url = PDOSWWW # "/exo/theses/dwyatt/thesis.ps.gz", +} + +@mastersthesis{prolac:kohler-ms, + title = "Prolac: a language for protocol compilation", + author = "Eddie Kohler", + school = MIT, + year = 1997, month = sep, + www_section = masterstheses, + www_ps_gz_url = PDOSWWW # "/papers/prolac:kohler-ms.ps.gz", + www_pdf_url = PDOSWWW # "/papers/prolac:kohler-ms.pdf", +} + +@mastersthesis{sfs:mazieres-ms, + title = "Security and decentralized control in the {SFS} global file system", + author = "David Mazi{\`e}res", + school = MIT, + year = 1997, month = aug, + www_section = masterstheses, + www_ps_gz_url = PDOSWWW # "/papers/sfs:mazieres-ms.ps.gz" +} + +@mastersthesis{exo:pinckney-meng, + title = "Operating system extensibility through event capture", + author = "Thomas {Pinckney III}", + school = MIT, + year = 1997, month = feb, + www_section = masterstheses, + www_ps_url = PDOSWWW # "/exo/theses/pinckney/thesis.ps", + www_ps_gz_url = PDOSWWW # "/exo/theses/pinckney/thesis.ps.gz", +} + +@mastersthesis{exo:briceno-meng, + title = "Decentralizing {UNIX} abstractions in the exokernel architecture", + author = "H{\'e}ctor Manuel {Brice{\~n}o Pulido}", + school = MIT, + year = 1997, month = feb, + www_section = masterstheses, + www_ps_url = PDOSWWW # "/exo/theses/hbriceno/thesis.ps", + www_ps_gz_url = PDOSWWW # "/exo/theses/hbriceno/thesis.ps.gz", +} + +@mastersthesis{rover:nntp, + title = "The {Rover} {NNTP} proxy", + author = "Constantine Cristakos", + school = MIT, + year = 1996, month = jun, + type = "Advanced Undergraduate Project", + www_section = masterstheses, + www_ps_url = PDOSWWW # "/papers/DeanAUP.ps", + www_ps_gz_url = PDOSWWW # "/papers/DeanAUP.ps.gz", +} + +@mastersthesis{exo:grimm-ms, + title = "Exodisk: maximizing application control over storage management", + author = "Robert Grimm", + school = MIT, + year = 1996, month = may, + www_section = masterstheses, + www_ps_url = PDOSWWW # "/exo/theses/rgrimm/thesis.ps", + www_ps_gz_url = PDOSWWW # "/exo/theses/rgrimm/thesis.ps.gz", +} + +@mastersthesis{rover:tauber-ms, + title = "Issues in building mobile-aware applications with the {Rover} toolkit", + author = "Joshua A. Tauber", + school = MIT, + year = 1996, month = may, + www_section = masterstheses, + www_ps_url = PDOSWWW # "/papers/JoshThesis.ps", + www_ps_gz_url = PDOSWWW # "/papers/JoshThesis.ps.gz", +} + +@mastersthesis{rover-mosaic:delespinasse-thesis, + title = "{Rover} {Mosaic}: e-mail communication for a full-function {Web} browser", + author = "Alan F. {deLespinasse}", + school = MIT, + year = 1995, month = jun, + www_section = masterstheses, + www_ps_url = PDOSWWW # "/papers/RoverMosaicThesis.ps", + www_ps_gz_url = PDOSWWW # "/papers/RoverMosaicThesis.ps.gz", +} + +@mastersthesis{r2over-mosaic:delespinasse-thesis, + title = {{Rover} {Mosaic}: e-mail communication for a full-function {Web} browser}, + author = "Alan F. {deLespinasse}", + school = MIT, + year = 1995, month = jun, + www_section = masterstheses, + www_ps_url = PDOSWWW # "/papers/RoverMosaicThesis.ps", + www_ps_gz_url = PDOSWWW # "/papers/RoverMosaicThesis.ps.gz", +} + + +%% PROCEEDINGS + +@proceedings{asplos6, + booktitle = "Proceedings of the 6th International Conference on Architectural Support for Programming Languages and Operating Systems ({ASPLOS-VI})", + year = 1994, month = oct, + address = "San Jose, California" +} + +@proceedings{ccs5, + booktitle = "Proceedings of the 5th {ACM} Conference on Computer and Communications Security ({CCS-5})", + year = 1998, month = nov, + address = "San Francisco, California", + bookurl = "http://www.bell-labs.com/user/reiter/ccs5/" +} + +@proceedings{ccs9, + booktitle = "Proceedings of the 9th {ACM} Conference on Computer and Communications Security ({CCS-9})", + year = 2002, month = nov, + address = "Washington, D.C.", + bookurl = "http://www.acm.org/sigs/sigsac/ccs/" +} + +@proceedings{dcs16, + booktitle = "Proceedings of the 16th International Conference on Distributed Computing Systems", + organization = IEEECompSoc, + year = 1996, month = may, + address = "Hong Kong", +} + +@proceedings{dcs15, + booktitle = "Proceedings of the 15th International Conference on Distributed Computing Systems", + organization = IEEECompSoc, + year = 1995, month = jun, + address = "Vancouver, British Columbia", +} + +@proceedings{hotnets1, + booktitle = "Proceedings of the First {W}orkshop on {H}ot {T}opics in {N}etworks ({HotNets-I})", + year = 2002, month = oct, + organization = "{ACM SIGCOMM}", + address = "Princeton, New Jersey", + bookurl = "http://www.cs.washington.edu/hotnets/", +} + +@proceedings{hotos8, + booktitle = "Proceedings of the 8th {W}orkshop on {H}ot {T}opics in {O}perating {S}ystems ({HotOS-VIII})", + year = 2001, month = may, + organization = IEEECompSoc, + address = "Schloss Elmau, Germany", + bookurl = "http://i30www.ira.uka.de/conferences/HotOS/", +} + +@proceedings{hotos6, + booktitle = "Proceedings of the 6th {W}orkshop on {H}ot {T}opics in {O}perating {S}ystems ({HotOS-VI})", + year = 1997, month = may, + organization = IEEECompSoc, + address = "Chatham, Cape Cod, Massachusetts", + bookurl = "http://www.eecs.harvard.edu/hotos", +} + +@proceedings{hotos5, + booktitle = "Proceedings of the 5th {W}orkshop on {H}ot {T}opics in {O}perating {S}ystems ({HotOS-V})", + year = 1995, month = may, + organization = IEEECompSoc, + address = "Orcas Island, Washington", + bookurl = "http://www.research.microsoft.com/research/os/HotOs/", +} + +@proceedings{mobicom96, + booktitle = "Proceedings of the 2nd {ACM} International Conference on Mobile Computing and Networking ({MobiCom} '96)", + year = 1996, month = nov, + address = "Rye, New York", + bookurl = "http://www.acm.org/sigmobile/conf/mobicom96/", +} + +@proceedings{usenix02, + booktitle = "Proceedings of the 2002 USENIX Annual Technical Conference (USENIX '02)", + year = 2002, month = jun, + address = "Monterey, California", + bookurl = "http://www.usenix.org/events/usenix02/", +} + +@proceedings{usenix01, + booktitle = "Proceedings of the 2001 USENIX Annual Technical Conference (USENIX '01)", + year = 2001, month = jun, + address = "Boston, Massachusetts", + bookurl = "http://www.usenix.org/events/usenix01/", +} + +@proceedings{mobicom01, + booktitle = "Proceedings of the 7th {ACM} International Conference on Mobile Computing and Networking", + year = 2001, month = jul, + address = "Rome, Italy", + bookurl = "http://www.research.ibm.com/acm_sigmobile_conf_2001/" +} + +@proceedings{mobicom00, + booktitle = "Proceedings of the 6th {ACM} International Conference on Mobile Computing and Networking ({MobiCom} '00)", + year = 2000, month = aug, + address = "Boston, Massachusetts", + bookurl = "http://www.argreenhouse.com/mobicom2000/", +} + +@proceedings{openarch99, + booktitle = "Proceedings of the 2nd {IEEE} Conference on Open Architectures and Network Programming ({OpenArch} '99)", + year = 1999, month = mar, + address = "New York, New York", + bookurl = "http://www.ctr.columbia.edu/comet/activities/openarch99/", +} + +@proceedings{osdi5, + booktitle = "Proceedings of the 5th {USENIX} {S}ymposium on {O}perating {S}ystems {D}esign and {I}mplementation ({OSDI} '02)", + year = 2002, month = dec, + address = "Boston, Massachusetts", +} + +@proceedings{osdi1, + booktitle = "Proceedings of the 1st {USENIX} {S}ymposium on {O}perating {S}ystems {D}esign and {I}mplementation ({OSDI} '94)", + year = 1994, month = nov, + address = "Monterey, California", + bookurl = "http://www2.cs.utah.edu/~lepreau/osdi94/", +} + +@proceedings{osdi4, + booktitle = "Proceedings of the 4th {USENIX} {S}ymposium on {O}perating {S}ystems {D}esign and {I}mplementation ({OSDI} 2000)", + year = 2000, month = oct, + address = "San Diego, California", + bookurl = "http://www.usenix.org/events/osdi2000/", +} + +@proceedings{pldi97, + booktitle = "Proceedings of the {ACM} {SIGPLAN} '97 Conference on Programming Design and Implementation ({PLDI} '97)", + year = 1997, month = jun, + address = "Las Vegas, Nevada", + bookurl = "http://cs-www.bu.edu/pub/pldi97/", +} + +@proceedings{pldi96, + booktitle = "Proceedings of the {ACM} {SIGPLAN} '96 Conference on Programming Design and Implementation ({PLDI} '96)", + year = 1996, month = may, + address = "Philadelphia, Pennsylvania", +} + +@proceedings{popl96, + booktitle = "Proceedings of the 23rd {ACM} {SIGPLAN}-{SIGACT} Symposium on Principles of Programming Languages ({POPL} '96)", + year = 1996, month = jan, + address = "St. Petersburg Beach, Florida", + bookurl = "ftp://parcftp.xerox.com/pub/popl96/popl96.html" +} + +@proceedings{ppopp95, + booktitle = "Proceedings of the 5th {ACM} {SIGPLAN} Symposium on Principles and Practice of Parallel Programming ({PPoPP} '95)", + year = 1995, month = jul, + address = "Santa Barbara, California", + bookurl = "http://www.cs.ucsb.edu/Conferences/PPOPP95/", +} + +@proceedings{sigcomm99, + booktitle = "Proceedings of the {ACM} {SIGCOMM} '99 Conference: Applications, Technologies, Architectures, and Protocols for Computer Communication", + year = 1999, month = aug, + address = "Cambridge, Massachusetts", + bookurl = "http://www.acm.org/sigcomm/sigcomm99/", +} + +@proceedings{sigcomm96, + booktitle = "Proceedings of the {ACM} {SIGCOMM} '96 Conference: Applications, Technologies, Architectures, and Protocols for Computer Communication", + year = 1996, month = aug, + address = "Stanford, California", + bookurl = "http://www.acm.org/sigcomm/sigcomm96/", +} + +@proceedings{sigcommimw01, + booktitle = "Proceedings of the {ACM} {SIGCOMM} Internet Measurement Workshop '01", + year = 2001, month = nov, + address = "San Francisco, California", + bookurl = "http://www.acm.org/sigcomm/measworkshop2001.html" +} + +@proceedings{sigcomm01, + booktitle = "Proceedings of the {ACM} {SIGCOMM} '01 Conference", + year = 2001, month = aug, + address = "San Diego, California", + bookurl = "http://www.acm.org/sigcomm/sigcomm2001/", +} + +@proceedings{iptps02, + booktitle = "Proceedings of the 1st International Workshop on Peer-to-Peer Systems (IPTPS)", + year = 2002, month = mar, + address = "Cambridge, MA", + bookurl = "http://www.cs.rice.edu/Conferences/IPTPS02/" +} + +@proceedings{sigops-euro9, + booktitle = "Proceedings of the 9th {ACM} {SIGOPS} {E}uropean workshop: Beyond the {PC}: New Challenges for the Operating System", + year = 2000, month = sep, + address = "Kolding, Denmark", + bookurl = "http://www.diku.dk/ew2000/", +} + +@proceedings{sigops-euro8, + booktitle = "Proceedings of the 8th {ACM} {SIGOPS} {E}uropean workshop: Support for composing distributed applications", + year = 1998, month = sep, + address = "Sintra, Portugal", + bookurl = "http://www.dsg.cs.tcd.ie/~vjcahill/sigops98/", +} + +@proceedings{sigops-euro7, + booktitle = "Proceedings of the 7th {ACM} {SIGOPS} {E}uropean workshop: Systems support for worldwide applications", + year = 1996, month = sep, + address = "Connemara, Ireland", + bookurl = "http://mosquitonet.stanford.edu/sigops96/", +} + +@proceedings{sigops-euro6, + booktitle = "Proceedings of the 6th {ACM} {SIGOPS} {E}uropean workshop: Matching operating systems to application needs", + year = 1994, month = sep, + address = "Dagstuhl Castle, Wadern, Germany", +} + +@proceedings{sosp18, + booktitle = "Proceedings of the 18th " # SOSP # " ({SOSP} '01)", + year = 2001, month = oct, + address = "Chateau Lake Louise, Banff, Canada", + bookurl = "http://www.cs.ucsd.edu/sosp01/", +} + +@proceedings{sosp17, + booktitle = "Proceedings of the 17th " # SOSP # " ({SOSP} '99)", + year = 1999, month = dec, + address = "Kiawah Island, South Carolina", + bookurl = "http://www.diku.dk/sosp99/", +} + +@proceedings{sosp16, + booktitle = "Proceedings of the 16th " # SOSP # " ({SOSP} '97)", + year = 1997, month = oct, + address = "Saint-Mal{\^o}, France", + bookurl = "http://www.cs.washington.edu/sosp16", +} + +@proceedings{sosp15, + booktitle = "Proceedings of the 15th " # SOSP # " ({SOSP} '95)", + year = 1995, month = dec, + address = "Copper Mountain Resort, Colorado", +} + +@proceedings{sosp14, + booktitle = "Proceedings of the 14th " # SOSP # " ({SOSP} '93)", + year = 1993, month = dec, + address = "Asheville, North Carolina", +} + +@proceedings{supercomp96, + booktitle = "Supercomputing '96 Conference Proceedings: The international conference on high performance computing and communications", + organization = ACMabbr, + year = 1996, month = nov, + address = "Pittsburgh, Pennsylvania", + bookurl = "http://www.supercomp.org/sc96/", +} + +@proceedings{usenix97, + booktitle = "Proceedings of the {USENIX} 1997 Annual Technical Conference", + year = 1997, month = jan, + address = "Anaheim, California", + bookurl = "http://www.usenix.org/ana97/", +} + +@proceedings{wcsss96, + booktitle = "Workshop Record of {WCSSS} '96: The Inaugural Workshop on Compiler Support for Systems Software", + organization = "{ACM} {SIGPLAN}", + year = 1996, month = feb, + address = "Tuscon, Arizona", + bookurl = "http://www.cs.arizona.edu/wcsss96/" +} + +@proceedings{wcsss99, + booktitle = "Workshop Record of {WCSSS} '99: The 2nd {ACM} {SIGPLAN} Workshop on Compiler Support for Systems Software", + year = 1999, month = may, + address = "Atlanta, Georgia", + bookurl = "http://www.irisa.fr/compose/wcsss99/" +} + +@proceedings{wmcsa94, + booktitle = "Proceedings of the Workshop on Mobile Computing Systems and Applications ({WMCSA} '94)", + organization = IEEECompSoc, + year = 1994, month = dec, + address = "Santa Cruz, California", +} + +@proceedings{wwos4, + booktitle = "Proceedings of the 4th Workshop on Workstation Operating Systems", + organization = IEEECompSoc, + year = 1993, month = oct, + address = "Napa, California" +} + +@proceedings{www94, + booktitle = "Proceedings of the 2nd International {WWW} Conference: Mosaic and the Web", + year = 1994, month = oct, + address = "Chicago, Illinois", + bookurl = "http://www.ncsa.uiuc.edu/SDG/IT94/IT94Info-old.html", +} + +@proceedings{sec10, + booktitle = "Proceedings of the 10th {USENIX} {S}ecurity {S}ymposium", + year = 2001, month = aug, + address = "Washington, D.C.", + bookurl = "http://www.usenix.org/events/sec01/", +} + + +%% JOURNALS + +@journal{journal:ieee-toc, + journal = IEEEabbr # " Transactions on Computers", +} + +@journal{journal:osr, + journal = "Operating Systems Review", + organization = ACM, +} + +@journal{journal:toplas, + journal = ACMabbr # " Transactions on Programming Languages and Systems", +} + +@journal{journal:tocs, + journal = ACMabbr # " Transactions on Computer Systems", +} + +@journal{journal:winet, + journal = ACMabbr # " Wireless Networks", +} + diff --git a/i2p2www/anonbib/tests.py b/i2p2www/anonbib/tests.py new file mode 100644 index 00000000..3caa1674 --- /dev/null +++ b/i2p2www/anonbib/tests.py @@ -0,0 +1,86 @@ +#!/usr/bin/python2 +# Copyright 2004-2008, Nick Mathewson. See LICENSE for licensing info. + +"""Unit tests for anonbib.""" + +import BibTeX +import metaphone +#import reconcile +#import writeHTML +#import updateCache + +import unittest + +class MetaphoneTests(unittest.TestCase): + def testMetaphone(self): + pass + +class BibTeXTests(unittest.TestCase): + def testTranslation(self): + ut = BibTeX.url_untranslate + self.assertEquals(ut("Fred"),"Fred") + self.assertEquals(ut("Hello, World."), "Hello_2c_20World.") + + te = BibTeX.TeXescapeURL + ute = BibTeX.unTeXescapeURL + self.assertEquals(te("http://example/~me/my_file"), + r"http://example/\{}~me/my\_file") + self.assertEquals(ute(r"http:{}//example/\{}~me/my\_file"), + "http://example/~me/my_file") + + h = BibTeX.htmlize + self.assertEquals(h("Hello, world"), "Hello, world") + self.assertEquals(h(r"\'a\`e\'{i}(\'\i)\"o&\^u"), + "áèí(í)ö&" + "û") + self.assertEquals(h(r"\~n and \c{c}"), "ñ and ç") + self.assertEquals(h(r"\AE---a ligature"), "Æ—a ligature") + self.assertEquals(h(r"{\it 33}"), " 33") + self.assertEquals(h(r"Pages 33--99 or vice--versa?"), + "Pages 33-99 or vice–versa?") + + t = BibTeX.txtize + self.assertEquals(t("Hello, world"), "Hello, world") + self.assertEquals(t(r"\'a\`e\'{i}(\'\i)\"o&\^u"), + "aei(i)o&u") + self.assertEquals(t(r"\~n and \c{c}"), "n and c") + self.assertEquals(t(r"\AE---a ligature"), "AE---a ligature") + self.assertEquals(t(r"{\it 33}"), " 33") + self.assertEquals(t(r"Pages 33--99 or vice--versa?"), + "Pages 33--99 or vice--versa?") + + def authorsParseTo(self,authors,result): + pa = BibTeX.parseAuthor(authors) + self.assertEquals(["|".join(["+".join(item) for item in + [a.first,a.von,a.last,a.jr]]) + for a in pa], + result) + + def testAuthorParsing(self): + pa = BibTeX.parseAuthor + PA = BibTeX.ParsedAuthor + apt = self.authorsParseTo + + apt("Nick A. Mathewson and Roger Dingledine", + ["Nick+A.||Mathewson|", "Roger||Dingledine|"]) + apt("John van Neumann", ["John|van|Neumann|"]) + apt("P. Q. Z. de la Paz", ["P.+Q.+Z.|de+la|Paz|"]) + apt("Cher", ["||Cher|"]) + apt("Smith, Bob", ["Bob||Smith|"]) + apt("de Smith, Bob", ["Bob|de|Smith|"]) + apt("de Smith, Bob Z", ["Bob+Z|de|Smith|"]) + #XXXX Fix this. + #apt("Roberts Smith Wilkins, Bob Z", ["Bob+Z||Smith+Wilkins|"]) + apt("Smith, Jr, Bob", ["Bob||Smith|Jr"]) + + #XXXX Fix this. + #apt("R Jones, Jr.", ["R||Jones|Jr."]) + apt("Smith, Bob and John Smith and Last,First", + ["Bob||Smith|", "John||Smith|", "First||Last|"]) + apt("Bob Smith and John Smith and John Doe", + ["Bob||Smith|", "John||Smith|", "John||Doe|"]) + + +if __name__ == '__main__': + unittest.main() + diff --git a/i2p2www/anonbib/upb.gif b/i2p2www/anonbib/upb.gif new file mode 100644 index 00000000..58528283 Binary files /dev/null and b/i2p2www/anonbib/upb.gif differ diff --git a/i2p2www/anonbib/updateCache.py b/i2p2www/anonbib/updateCache.py new file mode 100755 index 00000000..7b7fe645 --- /dev/null +++ b/i2p2www/anonbib/updateCache.py @@ -0,0 +1,169 @@ +#!/usr/bin/python +# Copyright 2003-2008, Nick Mathewson. See LICENSE for licensing info. + +"""Download files in bibliography into a local cache. +""" + +import os +import sys +import signal +import time +import gzip + +import BibTeX +import config +import urllib2 +import getopt +import socket +import errno +import httplib + +FILE_TYPES = [ "txt", "html", "pdf", "ps", "ps.gz", "abstract" ] +BIN_FILE_TYPES = [ 'pdf', 'ps.gz' ] + +class UIError(Exception): + pass + +def tryUnlink(fn): + try: + os.unlink(fn) + except OSError: + pass + +def getCacheFname(key, ftype, section): + return BibTeX.smartJoin(config.OUTPUT_DIR,config.CACHE_DIR, + section, + "%s.%s"%(key,ftype)) + +def downloadFile(key, ftype, section, url,timeout=None): + if timeout is None: + timeout = config.DOWNLOAD_CONNECT_TIMEOUT + fname = getCacheFname(key, ftype, section) + parent = os.path.split(fname)[0] + if not os.path.exists(parent): + os.makedirs(parent) + + fnameTmp = fname+".tmp" + fnameURL = fname+".url" + tryUnlink(fnameTmp) + + def sigalrmHandler(sig,_): + pass + signal.signal(signal.SIGALRM, sigalrmHandler) + signal.alarm(timeout) + try: + try: + infile = urllib2.urlopen(url) + except httplib.InvalidURL, e: + raise UIError("Invalid URL %s: %s"%(url,e)) + except IOError, e: + raise UIError("Cannot connect to url %s: %s"%(url,e)) + except socket.error, e: + if getattr(e,"errno",-1) == errno.EINTR: + raise UIError("Connection timed out to url %s"%url) + else: + raise UIError("Error connecting to %s: %s"%(url, e)) + finally: + signal.alarm(0) + + mode = 'w' + if ftype in BIN_FILE_TYPES: + mode = 'wb' + outfile = open(fnameTmp, mode) + try: + while 1: + s = infile.read(1<<16) + if not s: break + outfile.write(s) + finally: + infile.close() + outfile.close() + + urlfile = open(fnameURL, 'w') + print >>urlfile, time.strftime("%Y-%m-%d %H:%M:%S", time.localtime()) + if "\n" in url: url = url.replace("\n", " ") + print >>urlfile, url + urlfile.close() + + os.rename(fnameTmp, fname) + +def getURLs(entry): + r = {} + for ftype in FILE_TYPES: + ftype2 = ftype.replace(".", "_") + url = entry.get("www_%s_url"%ftype2) + if url: + r[ftype] = url.strip().replace("\n", " ") + return r + +def getCachedURL(key, ftype, section): + fname = getCacheFname(key, ftype, section) + urlFname = fname+".url" + if not os.path.exists(fname) or not os.path.exists(urlFname): + return None + f = open(urlFname, 'r') + lines = f.readlines() + f.close() + if len(lines) != 2: + print >>sys.stderr, "ERROR: unexpected number of lines in", urlFname + return lines[1].strip() + +def downloadAll(bibtex, missingOnly=0): + """returns list of tuples of key, ftype, url, error""" + errors = [] + for e in bibtex.entries: + urls = getURLs(e) + key = e.key + section = e.get("www_cache_section", ".") + for ftype, url in urls.items(): + if missingOnly: + cachedURL = getCachedURL(key, ftype, section) + if cachedURL == url: + print >>sys.stderr,"Skipping",url + continue + elif cachedURL is not None: + print >>sys.stderr,"URL for %s.%s has changed"%(key,ftype) + else: + print >>sys.stderr,"I have no copy of %s.%s"%(key,ftype) + try: + downloadFile(key, ftype, section, url) + print "Downloaded",url + except UIError, e: + print >>sys.stderr, str(e) + errors.append((key,ftype,url,str(e))) + except (IOError, socket.error), e: + msg = "Error downloading %s: %s"%(url,str(e)) + print >>sys.stderr, msg + errors.append((key,ftype,url,msg)) + if urls.has_key("ps") and not urls.has_key("ps.gz"): + # Say, this is something we'd like to have gzipped locally. + psFname = getCacheFname(key, "ps", section) + psGzFname = getCacheFname(key, "ps.gz", section) + if os.path.exists(psFname) and not os.path.exists(psGzFname): + # This is something we haven't gzipped yet. + print "Compressing a copy of",psFname + outf = gzip.GzipFile(psGzFname, "wb") + inf = open(psFname, "rb") + while 1: + s = inf.read(4096) + if not s: + break + outf.write(s) + outf.close() + inf.close() + + return errors + +if __name__ == '__main__': + if len(sys.argv) == 2: + print "Loading from %s"%sys.argv[1] + else: + print >>sys.stderr, "Expected a single configuration file as an argument" + sys.exit(1) + config.load(sys.argv[1]) + + if config.CACHE_UMASK != None: + os.umask(config.CACHE_UMASK) + + bib = BibTeX.parseFile(config.MASTER_BIB) + downloadAll(bib,missingOnly=1) diff --git a/i2p2www/anonbib/ups.gif b/i2p2www/anonbib/ups.gif new file mode 100644 index 00000000..36f01245 Binary files /dev/null and b/i2p2www/anonbib/ups.gif differ diff --git a/i2p2www/anonbib/venue-checklist.txt b/i2p2www/anonbib/venue-checklist.txt new file mode 100644 index 00000000..139a223a --- /dev/null +++ b/i2p2www/anonbib/venue-checklist.txt @@ -0,0 +1,41 @@ +This file is to keep track of which volumes of which publications have +been combed for anonymity papers and which we still have to add. + +=== DONE: + +ExampleConference (through 2008) + +PETS 2000-2003 + +=== CLAIMED: + +PETS 2000-2010 -- Nick (claimed 6/16) +ESORICS 1990-2010 -- Nick (claimed 6/16) +CCS -- George (claimed 6/17) +USENIX Security ("Oakland") -- George (claimed 6/17) + +=== SHOULD DO: + +Infohiding +IEEE Security and privacy +NDSS +WPES +WEIS +Financial Crypto +Eurocrypt +Asiacrypt + +Search: Papers that cite Chaum's paper +Search: Papers that cite the Tor paper +Search: Papers that cite the original onion routing papers +Search: Papers mentioning "anonymity" or "anonymous" +Search: Papers mentioning "mixnet" or "mix-net" + +=== UNDERSERVED CONTENT; PLEASE SUGGEST SEARCHES AND VENUES + +Private information retrieval; PIR +Anti-censorship; censorship +Location privacy +Anonymous credentials +Anonymizing data +Secure multiparty computation diff --git a/i2p2www/anonbib/views.py b/i2p2www/anonbib/views.py new file mode 100644 index 00000000..7e1434cf --- /dev/null +++ b/i2p2www/anonbib/views.py @@ -0,0 +1,70 @@ +from flask import render_template + +from i2p2www import ANONBIB_CFG, ANONBIB_FILE +from i2p2www.anonbib import BibTeX, config + +def papers_list(tag='', choice='date'): + config.load(ANONBIB_CFG) + rbib = BibTeX.parseFile(ANONBIB_FILE) + if tag: + rbib = [ b for b in rbib.entries if tag in b.get('www_tags', '').split() ] + else: + rbib = rbib.entries + + if choice == 'topic': + sectionType = 'Topics' + rbib = BibTeX.sortEntriesBy(rbib, 'www_section', 'ZZZZZZZZZZZZZZ') + rbib = BibTeX.splitSortedEntriesBy(rbib, 'www_section') + if rbib[-1][0].startswith(""): + rbib[-1] = ("Miscellaneous", rbib[-1][1]) + + rbib = [ (s, BibTeX.sortEntriesByDate(ents)) + for s, ents in rbib + ] + elif choice == 'author': + sectionType = 'Authors' + rbib, url_map = BibTeX.splitEntriesByAuthor(rbib) + else: + sectionType = 'Years' + choice = 'date' + rbib = BibTeX.sortEntriesByDate(rbib) + rbib = BibTeX.splitSortedEntriesBy(rbib, 'year') + + bib = { + 'tags': config.ALL_TAGS, + 'tag_titles': config.TAG_TITLES, + 'tag_short_titles': config.TAG_SHORT_TITLES, + 'tag': tag, + 'sectiontypes': sectionType, + 'field': choice, + } + + sections = [] + for section, entries in rbib: + s = { + 'name': section, + 'slug': BibTeX.url_untranslate(section), + 'entries': entries, + } + sections.append(s) + bib['sections'] = sections + + return render_template('papers/list.html', bib=bib) + +def papers_bibtex(tag=None): + config.load(ANONBIB_CFG) + rbib = BibTeX.parseFile(ANONBIB_FILE) + if tag: + rbib = [ b for b in rbib.entries if tag in b.get('www_tags', '').split() ] + else: + rbib = rbib.entries + entries = [ (ent.key, ent) for ent in rbib ] + entries.sort() + entries = [ ent[1] for ent in entries ] + + bib = { + 'title': 'Papers on I2P', + 'entries': rbib, + } + + return render_template('papers/bibtex.html', bib=bib) diff --git a/i2p2www/anonbib/writeHTML.py b/i2p2www/anonbib/writeHTML.py new file mode 100755 index 00000000..19a7c146 --- /dev/null +++ b/i2p2www/anonbib/writeHTML.py @@ -0,0 +1,246 @@ +#!/usr/bin/python +# Copyright 2003-2008, Nick Mathewson. See LICENSE for licensing info. + +"""Generate indices by author, topic, date, and BibTeX key.""" + +import sys +import re +import os +import json + +assert sys.version_info[:3] >= (2,2,0) +os.umask(022) + +import BibTeX +import config + +def getTemplate(name): + f = open(name) + template = f.read() + f.close() + template_s, template_e = template.split("%(entries)s") + return template_s, template_e + +def pathLength(s): + n = 0 + while s: + parent, leaf = os.path.split(s) + if leaf != '' and leaf != '.': + n += 1 + s = parent + return n + +def writeBody(f, sections, section_urls, cache_path, base_url): + '''f: an open file + sections: list of (sectionname, [list of BibTeXEntry]) + section_urls: map from sectionname to external url''' + for s, entries in sections: + u = section_urls.get(s) + sDisp = re.sub(r'\s+', ' ', s.strip()) + sDisp = sDisp.replace(" ", " ") + if u: + print >>f, ('

  • %s

    '%( + (BibTeX.url_untranslate(s), u, sDisp))) + else: + print >>f, ('

  • %s

    '%( + BibTeX.url_untranslate(s),sDisp)) + print >>f, "
      " + for e in entries: + print >>f, e.to_html(cache_path=cache_path, base_url=base_url) + print >>f, "
    • " + +def writeHTML(f, sections, sectionType, fieldName, choices, + tag, config, cache_url_path, section_urls={}): + """sections: list of (sectionname, [list of BibTeXEntry])''' + sectionType: str + fieldName: str + choices: list of (choice, url)""" + + title = config.TAG_TITLES[tag] + short_title = config.TAG_SHORT_TITLES[tag] + # + secStr = [] + for s, _ in sections: + hts = re.sub(r'\s+', ' ', s.strip()) + hts = s.replace(" ", " ") + secStr.append("

    %s

    \n"% + ((BibTeX.url_untranslate(s),hts))) + secStr = "".join(secStr) + + # + tagListStr = [] + st = config.TAG_SHORT_TITLES.keys() + st.sort() + root = "../"*pathLength(config.TAG_DIRECTORIES[tag]) + if root == "": root = "." + for t in st: + name = config.TAG_SHORT_TITLES[t] + if t == tag: + tagListStr.append(name) + else: + url = BibTeX.smartJoin(root, config.TAG_DIRECTORIES[t], "date.html") + tagListStr.append("%s"%(url, name)) + tagListStr = " | ".join(tagListStr) + + # + choiceStr = [] + for choice, url in choices: + if url: + choiceStr.append("%s"%(url, choice)) + else: + choiceStr.append(choice) + + choiceStr = (" | ".join(choiceStr)) + + fields = { 'command_line' : "", + 'sectiontypes' : sectionType, + 'choices' : choiceStr, + 'field': fieldName, + 'sections' : secStr, + 'otherbibs' : tagListStr, + 'title': title, + 'short_title': short_title, + "root" : root, + } + + header, footer = getTemplate(config.TEMPLATE_FILE) + print >>f, header%fields + writeBody(f, sections, section_urls, cache_path=cache_url_path, + base_url=root) + print >>f, footer%fields + +def jsonDumper(obj): + if isinstance(obj, BibTeX.BibTeXEntry): + e = obj.entries.copy() + e['key'] = obj.key + return e + else: + raise TypeError("Do not know how to serialize %s"%(obj.__class,)) + +def writePageSet(config, bib, tag): + if tag: + bib_entries = [ b for b in bib.entries + if tag in b.get('www_tags', "").split() ] + else: + bib_entries = bib.entries[:] + + if not bib_entries: + print >>sys.stderr, "No entries with tag %r; skipping"%tag + return + + tagdir = config.TAG_DIRECTORIES[tag] + outdir = os.path.join(config.OUTPUT_DIR, tagdir) + cache_url_path = BibTeX.smartJoin("../"*pathLength(tagdir), + config.CACHE_DIR) + if not os.path.exists(outdir): + os.makedirs(outdir, 0755) + ##### Sorted views: + + ## By topic. + + entries = BibTeX.sortEntriesBy(bib_entries, "www_section", "ZZZZZZZZZZZZZZ") + entries = BibTeX.splitSortedEntriesBy(entries, "www_section") + if entries[-1][0].startswith(""): + entries[-1] = ("Miscellaneous", entries[-1][1]) + + entries = [ (s, BibTeX.sortEntriesByDate(ents)) + for s, ents in entries + ] + + f = open(os.path.join(outdir,"topic.html"), 'w') + writeHTML(f, entries, "Topics", "topic", + (("By topic", None), + ("By date", "./date.html"), + ("By author", "./author.html") + ), + tag=tag, config=config, + cache_url_path=cache_url_path) + f.close() + + ## By date. + + entries = BibTeX.sortEntriesByDate(bib_entries) + entries = BibTeX.splitSortedEntriesBy(entries, 'year') + for idx in -1, -2: + if entries[idx][0].startswith(""): + entries[idx] = ("Unknown", entries[idx][1]) + elif entries[idx][0].startswith("forthcoming"): + entries[idx] = ("Forthcoming", entries[idx][1]) + sections = [ ent[0] for ent in entries ] + + first_year = int(entries[0][1][0]['year']) + try: + last_year = int(entries[-1][1][0].get('year')) + except ValueError: + last_year = int(entries[-2][1][0].get('year')) + + years = map(str, range(first_year, last_year+1)) + if entries[-1][0] == 'Unknown': + years.append("Unknown") + + f = open(os.path.join(outdir,"date.html"), 'w') + writeHTML(f, entries, "Years", "date", + (("By topic", "./topic.html"), + ("By date", None), + ("By author", "./author.html") + ), + tag=tag, config=config, + cache_url_path=cache_url_path) + f.close() + + ## By author + entries, url_map = BibTeX.splitEntriesByAuthor(bib_entries) + + f = open(os.path.join(outdir,"author.html"), 'w') + writeHTML(f, entries, "Authors", "author", + (("By topic", "./topic.html"), + ("By date", "./date.html"), + ("By author", None), + ), + tag=tag, config=config, + cache_url_path=cache_url_path, + section_urls=url_map) + f.close() + + ## The big BibTeX file + + entries = bib_entries[:] + entries = [ (ent.key, ent) for ent in entries ] + entries.sort() + entries = [ ent[1] for ent in entries ] + + ## Finding the root directory is done by writeHTML(), but + ## the BibTeX file doesn't use that, so repeat the code here + root = "../"*pathLength(config.TAG_DIRECTORIES[tag]) + if root == "": root = "." + + header,footer = getTemplate(config.BIBTEX_TEMPLATE_FILE) + f = open(os.path.join(outdir,"bibtex.html"), 'w') + print >>f, header % { 'command_line' : "", + 'title': config.TAG_TITLES[tag], + 'root': root } + for ent in entries: + print >>f, ( + ("%s" + "
    %s
    ") + %(BibTeX.url_untranslate(ent.key), ent.key, ent.format(90,8,1))) + print >>f, footer + f.close() + + f = open(os.path.join(outdir,"bibtex.json"), 'w') + json.dump(entries, f, default=jsonDumper) + f.close() + + +if __name__ == '__main__': + if len(sys.argv) == 2: + print "Loading from %s"%sys.argv[1] + else: + print >>sys.stderr, "Expected a single configuration file as an argument" + sys.exit(1) + config.load(sys.argv[1]) + + bib = BibTeX.parseFile(config.MASTER_BIB) + + for tag in config.TAG_DIRECTORIES.keys(): + writePageSet(config, bib, tag) diff --git a/i2p2www/babel.cfg b/i2p2www/babel.cfg deleted file mode 100644 index f25e938a..00000000 --- a/i2p2www/babel.cfg +++ /dev/null @@ -1,7 +0,0 @@ -[python: **.py] -[jinja2: **/pages/**.html] -extensions=jinja2.ext.autoescape,jinja2.ext.with_,i2p2www.extensions.HighlightExtension -[jinja2: **/pages/global/macros] -extensions=jinja2.ext.autoescape,jinja2.ext.with_ -[jinja2: **/blog/**.rst] -extensions=jinja2.ext.autoescape,jinja2.ext.with_ diff --git a/i2p2www/blog/2011/06/06/Ipredator-SoC.rst b/i2p2www/blog/2011/06/06/Ipredator-SoC.rst index 40c96634..870ff823 100644 --- a/i2p2www/blog/2011/06/06/Ipredator-SoC.rst +++ b/i2p2www/blog/2011/06/06/Ipredator-SoC.rst @@ -20,7 +20,7 @@ This work was the idea of Jan-Erik Fiske of `ViaEuropa`_ and Peter Sunde of `fla Current information can be found on `zzz's forum`_ and #i2p-dev on chat.freenode.net -.. _`zzz's forum`: http://zzz.i2p.to/topics/888 +.. _`zzz's forum`: http://{{ i2pconv('zzz.i2p') }}/topics/888 Cheers diff --git a/i2p2www/blog/2011/09/03/Ipredator-SoC-itoopie-released.rst b/i2p2www/blog/2011/09/03/Ipredator-SoC-itoopie-released.rst index 242a34d1..88fdb1cf 100644 --- a/i2p2www/blog/2011/09/03/Ipredator-SoC-itoopie-released.rst +++ b/i2p2www/blog/2011/09/03/Ipredator-SoC-itoopie-released.rst @@ -16,11 +16,9 @@ The aim of itoopie is to provide an interface that is simpler and has a lower lu I2PControl is an I2P plugin providing a JSONRPC interface for the I2P router. The interface supports setting basic settings (bandwidth, ports etc.), reading many stats and is provided over an SSL encrypted HTTP connection. -More information and instructions can be found at `itoopie.net`_, `itoopie.i2p.to`_ (via proxy)and `itoopie.i2p`_ (anonymously). +More information and instructions can be found at `{{ i2pconv('itoopie.i2p') }}`_. -.. _`itoopie.net`: http://itoopie.net -.. _`itoopie.i2p.to`: http://itoopie.i2p.to -.. _`itoopie.i2p`: http://itoopie.i2p +.. _`{{ i2pconv('itoopie.i2p') }}`: http://{{ i2pconv('itoopie.i2p') }} This project has been funded by the VPN services `Relakks`_ & `Ipredator`_ and was initiated by Jan-Erik Fiske and `Peter Sunde`_. diff --git a/i2p2www/blog/2013/07/15/0.9.7-Release.rst b/i2p2www/blog/2013/07/15/0.9.7-Release.rst new file mode 100644 index 00000000..794991af --- /dev/null +++ b/i2p2www/blog/2013/07/15/0.9.7-Release.rst @@ -0,0 +1,88 @@ +============= +{% trans %}0.9.7 Release{% endtrans %} +============= +.. meta:: + :date: 2013-07-15 + :category: release + :excerpt: {% trans %}0.9.7 includes significant bug fixes and improvements.{% endtrans %} + +{% trans %}0.9.7 includes significant bug fixes and improvements.{% endtrans %} + +{% trans -%} +For the first time, class 'N' routers (those with a minimumum of 128 KBytes/sec of shared bandwidth) +will automatically become floodfill (previously it was only 'O' routers with 256 KBps). This will +increase the floodfill population for additional resistance to certain attacks (see below). Floodfill routers +don't consume much additional bandwidth, but they do tend to use additional memory and concurrent +connections. If you do not wish your router to become floodfill, set the advanced configuration +router.floodfillParticipant=false . +{%- endtrans %} + +{% trans -%} +As we think the last release fixed the experimental update-via-torrent bugs, 3% of routers should +update over in-network bittorrent this cycle. +{%- endtrans %} + +{% trans -%} +Plugin update checks, possibly broken for several releases, are fixed. Your plugins should once again +auto-update after updating the router. +{%- endtrans %} + +{% trans -%} +We fixed a major streaming timer bug that contributed to frequent IRC disconnects. +{%- endtrans %} + +{% trans -%} +This release contains additional mitigations for the `"practical attacks" paper`_. +However, we have a lot more work to do to resist Sybil attacks on the floodfills, and resist +traffic analysis at the gateways and endpoints of exploratory tunnels. +It's a good reminder for everybody that our network is still relatively small and vulnerable. +We don't currently recommend any uses that would put anybody in serious jeopardy. +We'll keep working to improve it... please keep working to spread the word. A bigger network is a better network. +{%- endtrans %} + +.. _{% trans %}`"practical attacks" paper`{% endtrans %}: http://wwwcip.informatik.uni-erlangen.de/~spjsschl/i2p.pdf + +**{% trans %}RELEASE DETAILS{% endtrans %}** + +**{% trans %}Anonymity Improvements{% endtrans %}** + +- {% trans %}End-to-end encryption of responses to leaseset lookups{% endtrans %} +- {% trans %}Expand floodfill pool by enabling class 'N' floodfills{% endtrans %} +- {% trans %}Randomize padding inside encrypted SSU packets{% endtrans %} +- {% trans %}Preparation for better SSU protocol obfuscation{% endtrans %} + +**{% trans %}Bug Fixes{% endtrans %}** + +- {% trans %}Fix newer lease sets not getting stored or published{% endtrans %} +- {% trans %}Fix classpath bug when used with 4-year-old installations, causing the console not to start{% endtrans %} +- {% trans %}Fix addressbook database bug preventing update of the reverse index{% endtrans %} +- {% trans %}Fix i2psnark bug that changed the infohash of torrents created by Robert and fetched via magnet link{% endtrans %} +- {% trans %}Fix version checking for plugins{% endtrans %} +- {% trans %}Fix a streaming timer bug causing frequent IRC disconnects (also affects other close-on-idle tunnels){% endtrans %} + +**{% trans %}Other{% endtrans %}** + +- {% trans %}Don't install as a service on Windows by default{% endtrans %} +- {% trans %}Reduce transport idle timeouts{% endtrans %} +- {% trans %}Reduce tunnels on idle in i2psnark{% endtrans %} +- {% trans %}Change default in i2ptunnel GUI to 3 hops{% endtrans %} +- {% trans %}IE 10 support{% endtrans %} +- {% trans %}Individual expiration times in leases, for efficiency on destinations with a high number of tunnels{% endtrans %} +- {% trans %}Low-level encryption and XOR speedups{% endtrans %} +- {% trans %}Jetty 7.6.11{% endtrans %} +- {% trans %}Tomcat 6.0.37{% endtrans %} +- {% trans %}Translation updates: Chinese, French, German, Portuguese, Russian, Spanish{% endtrans %} +- {% trans %}New Turkish translation{% endtrans %} +- {% trans %}Wrapper 3.5.19 (new installs and PPA only){% endtrans %} +- {% trans %}Update GeoIP data (new installs and PPA only){% endtrans %} + +**{% trans %}SHA256 Checksums:{% endtrans %}** + +:: + + 48c10fe5c7455e134df44717215ed66ff79cfb2dd03fbfd64c14b3d5c179eab7 i2pinstall_0.9.7_windows.exe + c0a67051bb0c6f1e4ce3ac8a04257063c4b606b76309b39a6c3daeaaa3888e04 i2pinstall_0.9.7.jar + 497e2601ab7594c93e0866e7f6ad9c445f05f7660efcea596ab255677056b1cb i2psource_0.9.7.tar.bz2 + d0b8f0a2491c5ad401f87c94b3b805c03bccd69f9f1b57177a53287f29f85959 i2pupdate_0.9.7.zip + a620eafff86e8eb919acb5b8cd42578df68928b122dc3e715c0b431cdd4c0ef2 i2pupdate.su2 + 0d5723c361059a60431f3275ad5c0978c3b66097ecda1d1b8f5310c594f0a1ea i2pupdate.sud diff --git a/i2p2www/blog/2013/08/10/0.9.7.1-Release.rst b/i2p2www/blog/2013/08/10/0.9.7.1-Release.rst new file mode 100644 index 00000000..75e4231e --- /dev/null +++ b/i2p2www/blog/2013/08/10/0.9.7.1-Release.rst @@ -0,0 +1,39 @@ +=============== +{% trans %}0.9.7.1 Release{% endtrans %} +=============== +.. meta:: + :date: 2013-08-10 + :category: release + :excerpt: {% trans %}This unscheduled release disables the RouterInfo verification messages that were used in the attack published in the UCSB paper, which should make correlating a LeaseSet and a Router much more difficult. We have also included a limited number of other fixes listed below. Our 0.9.8 release, which will include IPv6 support, is still on-schedule for late September.{% endtrans %} + +{% trans %}This unscheduled release disables the RouterInfo verification messages that were used in the attack published in the UCSB paper, which should make correlating a LeaseSet and a Router much more difficult. We have also included a limited number of other fixes listed below. Our 0.9.8 release, which will include IPv6 support, is still on-schedule for late September.{% endtrans %} + +{% trans %}As usual, we recommend that all users update to this release.{% endtrans %} + +**{% trans %}RELEASE DETAILS{% endtrans %}** + +**{% trans %}Anonymity Improvements{% endtrans %}** + +- {% trans %}Disable RouterInfo verification messages{% endtrans %} + +**{% trans %}Other{% endtrans %}** + +- {% trans %}Extend inbound tunnel expiration{% endtrans %} +- {% trans %}i2prouter: bashism fix{% endtrans %} +- {% trans %}i2psnark: increase max piece size, mime type updates{% endtrans %} +- {% trans %}New reseed host{% endtrans %} +- {% trans %}New update hosts, thanks Meeh and dg{% endtrans %} +- {% trans %}Streaming: RTO changes{% endtrans %} +- {% trans %}Updater: Increase update-via-torrent to 30 percent{% endtrans %} +- {% trans %}UPnP fix for some hardware{% endtrans %} + +**{% trans %}SHA256 Checksums:{% endtrans %}** + +:: + + 293f445196a2f35c4d580f65b548135399e1f4443450b5ecf1cc53b1203fdad1 i2pinstall_0.9.7.1_windows.exe + 9fae874a4d680f50f5efd7be70cfcf55f2f4687e011bde9c4b4899bafb002e97 i2pinstall_0.9.7.1.jar + 7b73bdb23c53798054741cbaa4e7d8cce832ee566fbb17df0c803d0c22d099e1 i2psource_0.9.7.1.tar.bz2 + 69ca22a77a2de87f726d86555317f8688891d31f5312cf71d5a43febe2729b38 i2pupdate_0.9.7.1.zip + f59c9c80349c328b3e912113a3842146f647ff22ae323cef6b1e56a23f8c8cf1 i2pupdate.su2 + 52d1f32e2a72091da10312853e5df6bced12cb97770ba20732f2d9d6c4d2f5fe i2pupdate.sud diff --git a/i2p2www/blog/2013/09/30/0.9.8-Release.rst b/i2p2www/blog/2013/09/30/0.9.8-Release.rst new file mode 100644 index 00000000..fef85036 --- /dev/null +++ b/i2p2www/blog/2013/09/30/0.9.8-Release.rst @@ -0,0 +1,138 @@ +============= +{% trans %}0.9.8 Release{% endtrans %} +============= +.. meta:: + :date: 2013-09-30 + :category: release + :excerpt: {% trans %}0.9.8 includes the long-awaited support for IPv6. It's enabled by default, but of course you need a public IPv6 address to use it. Configuration is on the 'network' configuration tab in your console. We also have anonymity improvements including padding of SSU packets and longer router private keys.{% endtrans %} + +{% trans %}0.9.8 includes the long-awaited support for IPv6. It's enabled by default, but of course you need a public IPv6 address to use it. Configuration is on the 'network' configuration tab in your console. We also have anonymity improvements including padding of SSU packets and longer router private keys.{% endtrans %} + +{% trans %}30% of you will update via in-network torrent in this update cycle.{% endtrans %} + +**{% trans %}IPv6 Details{% endtrans %}** + +{% trans -%} +IPv6 is enabled and preferred by default. If you have a public IPv6 address +and you are connecting to another router with a published IPv6 address, it will +connect via IPv6. There is a new IPv6 configuration section on /confignet in +the router console. If IPv6 is causing problems you may disable it there. +{%- endtrans %} + +{% trans -%} +As a part of the IPv6 development effort, I2P now supports multiple +published IP addresses. If you have multiple public IP addresses (IPv4, IPv6, +or both), you may enable or disable them individually on /confignet. The +default is to use the first IPv4 and IPv6 addresses it discovers. If you have +multiple addresses you should review the configuration on /confignet and adjust +it if necessary. +Note that while you may enable multiple IPv4 and IPv6 addresses on /confignet, +we recommend that you use only one IPv4 and one IPv6 address. There are +bugs still to be fixed with multiple addresses of each type. +{%- endtrans %} + +{% trans -%} +While IPv6 support was designed and developed over several years, it has +only been tested by a limited number of users and is still beta. If you do have +a public IPv6 address, please monitor your router and the logs for problems, +and disable it necessary. Please report any bugs on +http://trac.i2p2.i2p. +{%- endtrans %} + +**{% trans %}Rekeying Details{% endtrans %}** + +{% trans -%} +For those of you running I2P on faster hardware (generally, 64-bit x86) the +router will generate a new identity using longer keys. This will substantially +reduce your participating traffic for 48 hours or more, while your router +re-integrates into the network. Due to the new keys, the large number of +torrent updates, and the recent network growth, we expect substantial +disruption to the network for a week or more after the update is released. +Please be patient and things should start to improve after a few days. +{%- endtrans %} + +{% trans -%} +These changes may result in higher CPU usage for some of you. We're doing +our best to increase efficiency, but stronger security generally requires more +computation. Performance may also be poor during the first week +due to the network churn. +We will evaluate the network performace before deciding whether to +change the key length on slower hardware in a future release. +{%- endtrans %} + +{% trans -%} +We are experiencing rapid network growth in the last few weeks, which is +causing a bit of a bumpy ride for some, especially on weekends. However, the +network is still performing fairly well, so keep spreading the word. +{%- endtrans %} + +**{% trans %}More Changes Coming{% endtrans %}** + +{% trans -%} +We're in the initial stages of desiging major changes to strengthen our +crypto. Stronger crypto will use more CPU and it may possibly +require a Java 7 JRE at a minimum. We understand your desire to run I2P on low-power +and/or older hardware. We're working hard to minimize the impacts, but some +loss of performance is inevitable. In addition, Java 5 and 6 are no longer +supported by Oracle. Now is a good time to upgrade to Java 7. Any change in +minimum requirements will be announced well in advance. +{%- endtrans %} + +**{% trans %}New Website{% endtrans %}** + +{% trans -%} +After a heroic effort by str4d, the new website preview is available at +http://i2hq.srv.i2p2.de. We hope to see it go live at +https://geti2p.net and http://www.i2p2.i2p soon. Please +contribute to the new website translations on Transifex, especially the +website_priority resource. +{%- endtrans %} + +**{% trans %}Community Participation{% endtrans %}** + +{% trans -%} +In early August, hottuna and zzz attended DEFCON 21 in Las Vegas. +Last weekend, echelon attended the CTS IV conference in Berlin and +psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass. +Several of us will be at 30C3 in Hamburg late this year. +It's great to see people participating at these events and representing I2P. +{%- endtrans %} + +**{% trans %}RELEASE DETAILS{% endtrans %}** + +**{% trans %}Major Changes{% endtrans %}** + +- {% trans %}IPv6 support for both NTCP and SSU{% endtrans %} + +**{% trans %}Anonymity Improvements{% endtrans %}** + +- {% trans %}SSU protocol obfuscation by adding random padding{% endtrans %} +- {% trans %}Longer encryption and DH private keys for users on faster platforms{% endtrans %} + +**{% trans %}Bug Fixes{% endtrans %}** + +- {% trans %}Fix I2PTunnel / I2CP locking and duplicates (partial){% endtrans %} +- {% trans %}Fix translation of HTTP proxy error pages{% endtrans %} +- {% trans %}Fix occasional runtime exception in NTCP{% endtrans %} + +**{% trans %}Other{% endtrans %}** + +- {% trans %}Big rework of transport code to accommodate multiple addresses and IPv6{% endtrans %} +- {% trans %}Streaming: Improved recovery from lost acks, other fixes{% endtrans %} +- {% trans %}Use Transifex for translation of initial news and HTTP proxy error pages{% endtrans %} +- {% trans %}Translation updates: Chinese, French, German, Portuguese, Russian, Swedish, Turkish{% endtrans %} +- {% trans %}New Romanian translation{% endtrans %} +- Jetty 7.6.12.v20130726 +- {% trans %}Wrapper 3.5.20 (new installs and PPA only){% endtrans %} +- {% trans %}Update GeoIP data (new installs and PPA only){% endtrans %} + +**{% trans %}SHA256 Checksums:{% endtrans %}** + +:: + + 5a863c43dc986087e5a5facd02b8ede32e1903bad1f4531bff95e61eab0facaf i2pinstall_0.9.8_windows.exe + 8af3f933346d76ac67ce814d7f991bbc00fa31c23124313841dbef9ae7bcf908 i2pinstall_0.9.8.jar + 787d1fe113398dfcec25d7daaca4e4093f309cb3e622b80757bcdf0558472041 i2psource_0.9.8.tar.bz2 + 24a08305228b817f87e251af74c4b5e9d1726de8d7d64c17bc2ede5511d42e58 i2pupdate_0.9.8.zip + 76b049da4e02b96e9e05eaf69b2e8214a6d6874385ab2d82c2885379ccd65278 i2pupdate.su2 + dba0f8e4660cb9147c50b7b3c4a0f95d342cfc65a51e0d37e445bc72026ed05f i2pupdate.sud diff --git a/i2p2www/blog/2013/10/02/0.9.8.1-Release.rst b/i2p2www/blog/2013/10/02/0.9.8.1-Release.rst new file mode 100644 index 00000000..a520bd45 --- /dev/null +++ b/i2p2www/blog/2013/10/02/0.9.8.1-Release.rst @@ -0,0 +1,36 @@ +=============== +{% trans %}0.9.8.1 Release{% endtrans %} +=============== +.. meta:: + :date: 2013-10-02 + :category: release + :excerpt: {% trans %}0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some people. New installs and non-Windows platforms are not affected, however all platforms will automatically update even if running 0.9.8.{% endtrans %} + +{% trans %}0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some people. New installs and non-Windows platforms are not affected, however all platforms will automatically update even if running 0.9.8.{% endtrans %} + +{% trans -%} +See the `Trac ticket`_ for details and workarounds. See +`the 0.9.8 release notes`_ for information on IPv6 and other changes. +{%- endtrans %} + +{% trans -%} +Due to recent attacks, logins are disabled on `Trac`_ and new registrations are +disabled on `zzz.i2p`_. Until those services are restored, please report all +bugs on IRC freenode or IRC2P #i2p-dev. +{%- endtrans %} + +.. _{% trans %}`Trac ticket`{% endtrans %}: http://{{ i2pconv('trac.i2p2.i2p') }}/ticket/1056 +.. _{% trans %}`the 0.9.8 release notes`{% endtrans %}: {{ url_for('blog_post', slug='2013/09/30/0.9.8-Release') }} +.. _`Trac`: http://{{ i2pconv('trac.i2p2.i2p') }}/ +.. _`zzz.i2p`: http://{{ i2pconv('zzz.i2p') }}/ + +**{% trans %}SHA256 Checksums:{% endtrans %}** + +:: + + e4a0a5929f20a5e176aad1ba4fe85d6c321c06fbc802cd715970ec380bb9e4fe i2pinstall_0.9.8.1_windows.exe + 8b933d55622743e3692585d09a1393a898dfd3d8c8f4c7f489adc23981273d30 i2pinstall_0.9.8.1.jar + 315072afc19b254a67062affe8b4515198ff64ecfcb4292b5f58b83975b3a1c3 i2psource_0.9.8.1.tar.bz2 + a340f84b5893ba0f193ec86e09f15c0ef724735eafb4c67c090f23be020b24ab i2pupdate_0.9.8.1.zip + 15d135f9923337df2092e42b9c5aa6ba5904b39c5ff403eef235843b1957b942 i2pupdate.su2 + d9902504d63556fa63a503fd088185dbbf3ace8b80e14dd4482b30e56b11f8d6 i2pupdate.sud diff --git a/i2p2www/blog/2013/12/07/0.9.9-Release.rst b/i2p2www/blog/2013/12/07/0.9.9-Release.rst new file mode 100644 index 00000000..290a2761 --- /dev/null +++ b/i2p2www/blog/2013/12/07/0.9.9-Release.rst @@ -0,0 +1,86 @@ +============= +{% trans %}0.9.9 Release{% endtrans %} +============= +.. meta:: + :date: 2013-12-07 + :category: release + :excerpt: {% trans %}0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and starts work on a year-long plan to increase the strength of the cryptographic signing algorithms used in the router, and support multiple algorithms and key lengths simultaneously. Automatic update files will now be signed with 4096-bit RSA keys.{% endtrans %} + +{% trans %}0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and starts work on a year-long plan to increase the strength of the cryptographic signing algorithms used in the router, and support multiple algorithms and key lengths simultaneously. Automatic update files will now be signed with 4096-bit RSA keys.{% endtrans %} + +{% trans -%} +We now support SSL between your router and your servers for security. +See `this development thread`_ for more information. +{%- endtrans %} + +.. _{% trans %}`this development thread`{% endtrans %}: http://{{ i2pconv('zzz.i2p') }}/topics/1495 + +{% trans -%} +As usual, we recommend that you update to this release. +The best way to maintain security and help the network is to run the latest release. +Several members of the I2P team will be at 30C3 in Hamburg this year. +Come say hello and ask for an I2P sticker. +Thanks to everyone for their support this year. +{%- endtrans %} + +**{% trans %}RELEASE DETAILS{% endtrans %}** + +**{% trans %}Anonymity Improvements{% endtrans %}** + +- {% trans %}Don't build client tunnels through zero-hop exploratory tunnels{% endtrans %} +- {% trans %}New "su3" file support using stronger keys{% endtrans %} +- {% trans %}Use su3 for updates{% endtrans %} + +**{% trans %}Bug Fixes{% endtrans %}** + +- {% trans %}Issues with losing data when closing streams{% endtrans %} +- {% trans %}Fix various streaming connection limit issues{% endtrans %} +- {% trans %}Issues with resource usage of closed connections{% endtrans %} +- {% trans %}Clean up timer threads in close-on-idle tunnels{% endtrans %} +- {% trans %}Several other streaming fixes{% endtrans %} +- {% trans %}Reject more non-public IPv6 addresses{% endtrans %} +- {% trans %}Fix IPv6 GeoIP{% endtrans %} +- {% trans %}Fix peer selection in first minutes after startup{% endtrans %} +- {% trans %}Several I2PTunnel bug fixes{% endtrans %} +- {% trans %}Fix major i2psnark DHT bug that prevented magnets from working well{% endtrans %} +- {% trans %}Fix client tunnels that fail due to name resolution failure at startup, particularly with b32 hostnames{% endtrans %} +- {% trans %}Fix changing client i2ptunnel target list{% endtrans %} +- {% trans %}Fix major bugs preventing reception of encrypted responses to leaseset lookups and verifies{% endtrans %} +- {% trans %}Fix bad links on some i2psnark buttons in Opera and text-mode browsers{% endtrans %} +- {% trans %}Fix NPE in Susimail{% endtrans %} + +**{% trans %}Other{% endtrans %}** + +- {% trans %}Start work on supporting stronger signing keys in the router{% endtrans %} +- {% trans %}Reduce thread usage for HTTP Server tunnels{% endtrans %} +- {% trans %}Auto-stop update torrent after some time{% endtrans %} +- {% trans %}Add ability to stop webapp via console{% endtrans %} +- {% trans %}New POST throttler in HTTP server tunnel{% endtrans %} +- {% trans %}Improve connection throttling{% endtrans %} +- {% trans %}More work to reduce number of connections{% endtrans %} +- {% trans %}Re-enable router info expiration job{% endtrans %} +- {% trans %}Extend router info expiration and other changes to reduce load on floodfills{% endtrans %} +- {% trans %}Support multiple servers through a single server tunnel{% endtrans %} +- {% trans %}Support specification of server port in i2ptunnel clients{% endtrans %} +- {% trans %}Add support for SSL connections from i2ptunnel to external server{% endtrans %} +- {% trans %}SSL and crypto code refactoring{% endtrans %} +- {% trans %}i2psnark storage code refactoring{% endtrans %} +- {% trans %}New destination cache{% endtrans %} +- {% trans %}Lots of code cleanup and resolution of findbugs warnings{% endtrans %} +- {% trans %}New Japanese translation (partial){% endtrans %} +- {% trans %}Translation updates: French, German, Italian, Romanian, Russian, Spanish, Swedish, and others{% endtrans %} +- Jetty 7.6.13.v20130916 +- {% trans %}Wrapper 3.5.22 (new installs and PPA only){% endtrans %} +- {% trans %}Update GeoIP data (new installs and PPA only){% endtrans %} + +**{% trans %}SHA256 Checksums:{% endtrans %}** + +:: + + 97dd4326ad8afdea0e78ffcb053b23793dfa79d89458be3fe3a1ed62a2d988e9 i2pinstall_0.9.9_windows.exe + 5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f i2pinstall_0.9.9.jar + cbbf25dea50a717c3376eb7af226f0b2a653e0372db8782ef37aa8b3d275436c i2psource_0.9.9.tar.bz2 + 533b0ce2d9e1bfc8762ba17eef3572ae7355ed8f21d5d3557b718a14b05794f2 i2pupdate_0.9.9.zip + 77824eb6f754f8b40301b7d260701eb2211ee51105d5f4b43d2c328f71736e0f i2pupdate.su2 + 78769de16a997730468e2e66c7519e2923d533cd96259dac352e04b07d80486c i2pupdate.su3 + 81b89ed00705668003b2715b930519bbeb939b9623c7e6e8d63c2762aa748bd8 i2pupdate.sud diff --git a/i2p2www/downloads.py b/i2p2www/downloads.py index 4313aaa0..7d40a4f6 100644 --- a/i2p2www/downloads.py +++ b/i2p2www/downloads.py @@ -45,10 +45,12 @@ def downloads_list(): # TODO: read mirror list or list of available files return render_template('downloads/list.html', def_mirror=DEFAULT_MIRROR) +# Debian-specific page +def downloads_debian(): + return render_template('downloads/debian.html') + # Specific file downloader def downloads_select(version, file): - if (file == 'debian'): - return render_template('downloads/debian.html', file=file) mirrors=read_mirrors() obj=[] for protocol in mirrors.keys(): @@ -71,4 +73,5 @@ def downloads_redirect(version, protocol, domain, file): if not domain in mirrors: abort(404) return redirect(mirrors[domain]['url'] % data) - return redirect(mirrors[randint(0, len(mirrors) - 1)]['url'] % data) + randomain = mirrors.keys()[randint(0, len(mirrors) - 1)] + return redirect(mirrors[randomain]['url'] % data) diff --git a/i2p2www/legacy.py b/i2p2www/legacy.py index cbd778b5..89457d51 100644 --- a/i2p2www/legacy.py +++ b/i2p2www/legacy.py @@ -6,12 +6,16 @@ from flask import g, redirect, url_for LEGACY_FUNCTIONS_MAP={ 'announcements': {'function': 'blog_index', 'params': {}}, - 'debian': {'function': 'downloads_select', 'params': {'file': 'debian'}}, + 'debian': {'function': 'downloads_debian', 'params': {}}, 'download': {'function': 'downloads_list', 'params': {}}, + 'installation': {'function': 'downloads_list', 'params': {}}, + 'meetings': {'function': 'meetings_index', 'params': {}}, + 'papers': {'function': 'papers_list', 'params': {}}, 'statusnotes': {'function': 'blog_index', 'params': {}}, } LEGACY_PAGES_MAP={ + 'api': 'docs', 'applications': 'get-involved/develop/applications', 'benchmarks': 'misc/benchmarks', 'bittorrent': 'docs/applications/bittorrent', @@ -33,28 +37,27 @@ LEGACY_PAGES_MAP={ 'clt': 'misc/clt', 'common_structures_spec': 'docs/spec/common-structures', 'configuration': 'docs/spec/configuration', - 'contact': 'about/contact', + 'contact': 'contact', 'cvs': 'misc/cvs', 'datagrams': 'docs/api/datagrams', 'dev-guidelines': 'get-involved/guides/dev-guidelines', 'developerskeys': 'get-involved/develop/developers-keys', 'donate': 'get-involved/donate', - 'faq': 'support/faq', 'getinvolved': 'get-involved', 'geoip': 'docs/spec/geoip', - 'glossary': 'support/glossary', + 'glossary': 'about/glossary', 'halloffame': 'about/hall-of-fame', 'how': 'docs', 'how_cryptography': 'docs/how/cryptography', 'how_elgamalaes': 'docs/how/elgamal-aes', 'how_garlicrouting': 'docs/how/garlic-routing', 'how_intro': 'docs/how/intro', - 'how_networkcomparisons': 'about/comparison', + 'how_networkcomparisons': 'comparison', 'how_networkdatabase': 'docs/how/network-database', 'how_peerselection': 'docs/how/peer-selection', 'how_threatmodel': 'docs/how/threat-model', 'how_tunnelrouting': 'docs/how/tunnel-routing', - 'htproxyports': 'support/browser-config', + 'htproxyports': 'about/browser-config', 'i2cp': 'docs/protocol/i2cp', 'i2cp_spec': 'docs/spec/i2cp', 'i2np': 'docs/protocol/i2np', @@ -83,13 +86,13 @@ LEGACY_PAGES_MAP={ 'newtranslators': 'get-involved/guides/new-translators', 'ntcp': 'docs/transport/ntcp', 'ntcp_discussion': 'docs/discussions/ntcp', - 'othernetworks': 'about/comparison/other-networks', - 'papers': 'research/papers', - 'performance-history': 'support/performance/history', - 'performance': 'support/performance/future', + 'othernetworks': 'comparison/other-networks', + 'performance-history': 'about/performance/history', + 'performance': 'about/performance/future', 'plugin_spec': 'docs/spec/plugin', 'plugins': 'docs/plugins', 'ports': 'docs/ports', + 'pressetext-0.7': 'misc/pressetext-0.7', 'protocols': 'docs/protocol', 'ratestats': 'misc/ratestats', 'release-signing-key': 'get-involved/develop/release-signing-key', @@ -103,6 +106,7 @@ LEGACY_PAGES_MAP={ 'supported_applications': 'docs/applications/supported', 'team': 'about/team', 'techintro': 'docs/how/tech-intro', + 'ticket1056': 'misc/ticket1056', 'ticket919': 'misc/ticket919', 'todo': 'get-involved/todo', 'transition-guide': 'misc/transition-guide', @@ -120,14 +124,75 @@ LEGACY_PAGES_MAP={ 'upgrade-0.6.1.30': 'misc/upgrade-0.6.1.30', } +LEGACY_BLOG_POSTS_MAP={ + 'statnotes0108': {'date': (2008, 2, 1), 'title': 'status'}, + 'summerofcode-2011': {'date': (2011, 6, 6), 'title': 'Ipredator-SoC'}, + 'summerofcode-2011-end': {'date': (2011, 9, 3), 'title': 'Ipredator-SoC-itoopie-released'}, +} + +LEGACY_RELEASES_MAP={ + '0.6.1.30': (2007, 10, 7), + '0.6.1.31': (2008, 2, 10), + '0.6.1.32': (2008, 3, 9), + '0.6.1.33': (2008, 4, 26), + '0.6.2': (2008, 6, 7), + '0.6.3': (2008, 8, 26), + '0.6.4': (2008, 10, 6), + '0.6.5': (2008, 12, 1), + '0.7': (2009, 1, 25), + '0.7.1': (2009, 3, 29), + '0.7.2': (2009, 4, 19), + '0.7.3': (2009, 5, 18), + '0.7.4': (2009, 6, 13), + '0.7.5': (2009, 6, 29), + '0.7.6': (2009, 7, 31), + '0.7.7': (2009, 10, 12), + '0.7.8': (2009, 12, 8), + '0.7.9': (2010, 1, 12), + '0.7.10': (2010, 1, 22), + '0.7.11': (2010, 2, 15), + '0.7.12': (2010, 3, 15), + '0.7.13': (2010, 4, 27), + '0.7.14': (2010, 6, 7), + '0.8': (2010, 7, 12), + '0.8.1': (2010, 11, 15), + '0.8.2': (2010, 12, 22), + '0.8.3': (2011, 1, 24), + '0.8.4': (2011, 3, 2), + '0.8.5': (2011, 4, 18), + '0.8.6': (2011, 5, 16), + '0.8.7': (2011, 6, 27), + '0.8.8': (2011, 8, 23), + '0.8.9': (2011, 10, 11), + '0.8.10': (2011, 10, 20), + '0.8.11': (2011, 11, 8), + '0.8.12': (2012, 1, 6), + '0.8.13': (2012, 2, 27), + '0.9': (2012, 5, 2), + '0.9.1': (2012, 7, 30), + '0.9.2': (2012, 9, 21), + '0.9.3': (2012, 10, 27), + '0.9.4': (2012, 12, 17), + '0.9.5': (2013, 3, 8), + '0.9.6': (2013, 5, 28), + '0.9.7': (2013, 7, 15), + '0.9.7.1': (2013, 8, 10), + '0.9.8': (2013, 9, 30), + '0.9.8.1': (2013, 10, 2), +} + def legacy_show(f): lang = 'en' if hasattr(g, 'lang') and g.lang: lang = g.lang + if lang == 'zh': + lang = 'zh_CN' if f in LEGACY_FUNCTIONS_MAP: return redirect(url_for(LEGACY_FUNCTIONS_MAP[f]['function'], lang=lang, **LEGACY_FUNCTIONS_MAP[f]['params'])) elif f in LEGACY_PAGES_MAP: return redirect(url_for('site_show', lang=lang, page=LEGACY_PAGES_MAP[f])) + elif f in LEGACY_BLOG_POSTS_MAP: + return legacy_blog(lang, LEGACY_BLOG_POSTS_MAP[f]['date'], LEGACY_BLOG_POSTS_MAP[f]['title']) else: return redirect(url_for('site_show', lang=lang, page=f)) @@ -135,4 +200,16 @@ def legacy_meeting(id): return redirect(url_for('meetings_show', id=id, lang='en')) def legacy_status(year, month, day): - return redirect(url_for('blog_post', lang='en', slug=('%s/%s/%s/status' % (year, month, day)))) + return legacy_blog('en', (year, month, day), 'status') + +def legacy_release(version): + lang = 'en' + if hasattr(g, 'lang') and g.lang: + lang = g.lang + if version in LEGACY_RELEASES_MAP: + return legacy_blog(lang, LEGACY_RELEASES_MAP[version], '%s-Release' % version) + else: + return legacy_show('release-%s' % version) + +def legacy_blog(lang, (year, month, day), title): + return redirect(url_for('blog_post', lang=lang, slug=('%d/%02d/%02d/%s' % (year, month, day, title)))) diff --git a/i2p2www/lexers.py b/i2p2www/lexers.py index aaf6718e..fe1c23b1 100644 --- a/i2p2www/lexers.py +++ b/i2p2www/lexers.py @@ -29,7 +29,9 @@ class DataSpecLexer(RegexLexer): (r'(-*)(//)(-+\+-)', bygroups(Text, Generic.Strong, Text)), ], 'content': [ + (r'(\s*)(\+-)', bygroups(Text, Text), '#pop', 'boundary'), (r'(\s*)([\+|])$', bygroups(Text, Text), '#pop'), + (r'(\s*)(\.\.\.)(\s)', bygroups(Text, Generic.Strong, Text)), (r'(\s*)(\.\.\.)$', bygroups(Text, Generic.Strong), '#pop'), (r'(\s*)(~)$', bygroups(Text, Generic.Strong), '#pop'), (r'(\s*)([\w=;]+)$', bygroups(Text, Name.Tag), '#pop'), diff --git a/i2p2www/meetings/helpers.py b/i2p2www/meetings/helpers.py index 204aff0a..622141f1 100644 --- a/i2p2www/meetings/helpers.py +++ b/i2p2www/meetings/helpers.py @@ -56,7 +56,10 @@ def get_meetings_ids(num=0): # ignore all non-.rst files if not f.endswith('.rst'): continue - meetings.append(int(f[:-4])) + try: + meetings.append(int(f[:-4])) + except ValueError: + continue meetings.sort() meetings.reverse() if (num > 0): @@ -65,7 +68,7 @@ def get_meetings_ids(num=0): def render_meeting_rst(id): # check if that file actually exists - name = str(id) + '.rst' + name = '%03d.rst' % id path = safe_join(MEETINGS_DIR, name) if not os.path.exists(path): abort(404) diff --git a/i2p2www/meetings/logs/1.log b/i2p2www/meetings/logs/001.log similarity index 100% rename from i2p2www/meetings/logs/1.log rename to i2p2www/meetings/logs/001.log diff --git a/i2p2www/meetings/logs/1.rst b/i2p2www/meetings/logs/001.rst similarity index 100% rename from i2p2www/meetings/logs/1.rst rename to i2p2www/meetings/logs/001.rst diff --git a/i2p2www/meetings/logs/2.log b/i2p2www/meetings/logs/002.log similarity index 100% rename from i2p2www/meetings/logs/2.log rename to i2p2www/meetings/logs/002.log diff --git a/i2p2www/meetings/logs/2.rst b/i2p2www/meetings/logs/002.rst similarity index 100% rename from i2p2www/meetings/logs/2.rst rename to i2p2www/meetings/logs/002.rst diff --git a/i2p2www/meetings/logs/3.log b/i2p2www/meetings/logs/003.log similarity index 100% rename from i2p2www/meetings/logs/3.log rename to i2p2www/meetings/logs/003.log diff --git a/i2p2www/meetings/logs/3.rst b/i2p2www/meetings/logs/003.rst similarity index 100% rename from i2p2www/meetings/logs/3.rst rename to i2p2www/meetings/logs/003.rst diff --git a/i2p2www/meetings/logs/4.log b/i2p2www/meetings/logs/004.log similarity index 100% rename from i2p2www/meetings/logs/4.log rename to i2p2www/meetings/logs/004.log diff --git a/i2p2www/meetings/logs/4.rst b/i2p2www/meetings/logs/004.rst similarity index 100% rename from i2p2www/meetings/logs/4.rst rename to i2p2www/meetings/logs/004.rst diff --git a/i2p2www/meetings/logs/7.log b/i2p2www/meetings/logs/007.log similarity index 100% rename from i2p2www/meetings/logs/7.log rename to i2p2www/meetings/logs/007.log diff --git a/i2p2www/meetings/logs/7.rst b/i2p2www/meetings/logs/007.rst similarity index 60% rename from i2p2www/meetings/logs/7.rst rename to i2p2www/meetings/logs/007.rst index dc72e56e..b057cee5 100644 --- a/i2p2www/meetings/logs/7.rst +++ b/i2p2www/meetings/logs/007.rst @@ -1,5 +1,5 @@ -I2P dev meeting, July 3 2002 -============================ +I2P dev meeting, July 3, 2002 +============================= (Courtesy of the wayback machine http://www.archive.org/) diff --git a/i2p2www/meetings/logs/8.log b/i2p2www/meetings/logs/008.log similarity index 100% rename from i2p2www/meetings/logs/8.log rename to i2p2www/meetings/logs/008.log diff --git a/i2p2www/meetings/logs/8.rst b/i2p2www/meetings/logs/008.rst similarity index 100% rename from i2p2www/meetings/logs/8.rst rename to i2p2www/meetings/logs/008.rst diff --git a/i2p2www/meetings/logs/9.log b/i2p2www/meetings/logs/009.log similarity index 100% rename from i2p2www/meetings/logs/9.log rename to i2p2www/meetings/logs/009.log diff --git a/i2p2www/meetings/logs/9.rst b/i2p2www/meetings/logs/009.rst similarity index 100% rename from i2p2www/meetings/logs/9.rst rename to i2p2www/meetings/logs/009.rst diff --git a/i2p2www/meetings/logs/10.log b/i2p2www/meetings/logs/010.log similarity index 100% rename from i2p2www/meetings/logs/10.log rename to i2p2www/meetings/logs/010.log diff --git a/i2p2www/meetings/logs/010.rst b/i2p2www/meetings/logs/010.rst new file mode 100644 index 00000000..57e44abf --- /dev/null +++ b/i2p2www/meetings/logs/010.rst @@ -0,0 +1,7 @@ +I2P dev meeting, September 4, 2002 +================================== + +Quick recap +----------- + +TODO diff --git a/i2p2www/meetings/logs/11.log b/i2p2www/meetings/logs/011.log similarity index 100% rename from i2p2www/meetings/logs/11.log rename to i2p2www/meetings/logs/011.log diff --git a/i2p2www/meetings/logs/11.rst b/i2p2www/meetings/logs/011.rst similarity index 100% rename from i2p2www/meetings/logs/11.rst rename to i2p2www/meetings/logs/011.rst diff --git a/i2p2www/meetings/logs/12.log b/i2p2www/meetings/logs/012.log similarity index 100% rename from i2p2www/meetings/logs/12.log rename to i2p2www/meetings/logs/012.log diff --git a/i2p2www/meetings/logs/12.rst b/i2p2www/meetings/logs/012.rst similarity index 100% rename from i2p2www/meetings/logs/12.rst rename to i2p2www/meetings/logs/012.rst diff --git a/i2p2www/meetings/logs/15.log b/i2p2www/meetings/logs/015.log similarity index 100% rename from i2p2www/meetings/logs/15.log rename to i2p2www/meetings/logs/015.log diff --git a/i2p2www/meetings/logs/15.rst b/i2p2www/meetings/logs/015.rst similarity index 100% rename from i2p2www/meetings/logs/15.rst rename to i2p2www/meetings/logs/015.rst diff --git a/i2p2www/meetings/logs/18.log b/i2p2www/meetings/logs/018.log similarity index 100% rename from i2p2www/meetings/logs/18.log rename to i2p2www/meetings/logs/018.log diff --git a/i2p2www/meetings/logs/18.rst b/i2p2www/meetings/logs/018.rst similarity index 100% rename from i2p2www/meetings/logs/18.rst rename to i2p2www/meetings/logs/018.rst diff --git a/i2p2www/meetings/logs/20.log b/i2p2www/meetings/logs/020.log similarity index 100% rename from i2p2www/meetings/logs/20.log rename to i2p2www/meetings/logs/020.log diff --git a/i2p2www/meetings/logs/20.rst b/i2p2www/meetings/logs/020.rst similarity index 100% rename from i2p2www/meetings/logs/20.rst rename to i2p2www/meetings/logs/020.rst diff --git a/i2p2www/meetings/logs/21.log b/i2p2www/meetings/logs/021.log similarity index 100% rename from i2p2www/meetings/logs/21.log rename to i2p2www/meetings/logs/021.log diff --git a/i2p2www/meetings/logs/21.rst b/i2p2www/meetings/logs/021.rst similarity index 100% rename from i2p2www/meetings/logs/21.rst rename to i2p2www/meetings/logs/021.rst diff --git a/i2p2www/meetings/logs/22.log b/i2p2www/meetings/logs/022.log similarity index 100% rename from i2p2www/meetings/logs/22.log rename to i2p2www/meetings/logs/022.log diff --git a/i2p2www/meetings/logs/22.rst b/i2p2www/meetings/logs/022.rst similarity index 100% rename from i2p2www/meetings/logs/22.rst rename to i2p2www/meetings/logs/022.rst diff --git a/i2p2www/meetings/logs/23.log b/i2p2www/meetings/logs/023.log similarity index 100% rename from i2p2www/meetings/logs/23.log rename to i2p2www/meetings/logs/023.log diff --git a/i2p2www/meetings/logs/23.rst b/i2p2www/meetings/logs/023.rst similarity index 100% rename from i2p2www/meetings/logs/23.rst rename to i2p2www/meetings/logs/023.rst diff --git a/i2p2www/meetings/logs/25.log b/i2p2www/meetings/logs/025.log similarity index 100% rename from i2p2www/meetings/logs/25.log rename to i2p2www/meetings/logs/025.log diff --git a/i2p2www/meetings/logs/25.rst b/i2p2www/meetings/logs/025.rst similarity index 100% rename from i2p2www/meetings/logs/25.rst rename to i2p2www/meetings/logs/025.rst diff --git a/i2p2www/meetings/logs/26.log b/i2p2www/meetings/logs/026.log similarity index 100% rename from i2p2www/meetings/logs/26.log rename to i2p2www/meetings/logs/026.log diff --git a/i2p2www/meetings/logs/26.rst b/i2p2www/meetings/logs/026.rst similarity index 100% rename from i2p2www/meetings/logs/26.rst rename to i2p2www/meetings/logs/026.rst diff --git a/i2p2www/meetings/logs/28.log b/i2p2www/meetings/logs/028.log similarity index 100% rename from i2p2www/meetings/logs/28.log rename to i2p2www/meetings/logs/028.log diff --git a/i2p2www/meetings/logs/28.rst b/i2p2www/meetings/logs/028.rst similarity index 100% rename from i2p2www/meetings/logs/28.rst rename to i2p2www/meetings/logs/028.rst diff --git a/i2p2www/meetings/logs/29.log b/i2p2www/meetings/logs/029.log similarity index 100% rename from i2p2www/meetings/logs/29.log rename to i2p2www/meetings/logs/029.log diff --git a/i2p2www/meetings/logs/29.rst b/i2p2www/meetings/logs/029.rst similarity index 100% rename from i2p2www/meetings/logs/29.rst rename to i2p2www/meetings/logs/029.rst diff --git a/i2p2www/meetings/logs/30.log b/i2p2www/meetings/logs/030.log similarity index 100% rename from i2p2www/meetings/logs/30.log rename to i2p2www/meetings/logs/030.log diff --git a/i2p2www/meetings/logs/30.rst b/i2p2www/meetings/logs/030.rst similarity index 100% rename from i2p2www/meetings/logs/30.rst rename to i2p2www/meetings/logs/030.rst diff --git a/i2p2www/meetings/logs/31.log b/i2p2www/meetings/logs/031.log similarity index 100% rename from i2p2www/meetings/logs/31.log rename to i2p2www/meetings/logs/031.log diff --git a/i2p2www/meetings/logs/31.rst b/i2p2www/meetings/logs/031.rst similarity index 100% rename from i2p2www/meetings/logs/31.rst rename to i2p2www/meetings/logs/031.rst diff --git a/i2p2www/meetings/logs/32.log b/i2p2www/meetings/logs/032.log similarity index 100% rename from i2p2www/meetings/logs/32.log rename to i2p2www/meetings/logs/032.log diff --git a/i2p2www/meetings/logs/32.rst b/i2p2www/meetings/logs/032.rst similarity index 100% rename from i2p2www/meetings/logs/32.rst rename to i2p2www/meetings/logs/032.rst diff --git a/i2p2www/meetings/logs/33.log b/i2p2www/meetings/logs/033.log similarity index 100% rename from i2p2www/meetings/logs/33.log rename to i2p2www/meetings/logs/033.log diff --git a/i2p2www/meetings/logs/33.rst b/i2p2www/meetings/logs/033.rst similarity index 100% rename from i2p2www/meetings/logs/33.rst rename to i2p2www/meetings/logs/033.rst diff --git a/i2p2www/meetings/logs/34.log b/i2p2www/meetings/logs/034.log similarity index 100% rename from i2p2www/meetings/logs/34.log rename to i2p2www/meetings/logs/034.log diff --git a/i2p2www/meetings/logs/34.rst b/i2p2www/meetings/logs/034.rst similarity index 100% rename from i2p2www/meetings/logs/34.rst rename to i2p2www/meetings/logs/034.rst diff --git a/i2p2www/meetings/logs/35.log b/i2p2www/meetings/logs/035.log similarity index 100% rename from i2p2www/meetings/logs/35.log rename to i2p2www/meetings/logs/035.log diff --git a/i2p2www/meetings/logs/35.rst b/i2p2www/meetings/logs/035.rst similarity index 100% rename from i2p2www/meetings/logs/35.rst rename to i2p2www/meetings/logs/035.rst diff --git a/i2p2www/meetings/logs/47.log b/i2p2www/meetings/logs/047.log similarity index 100% rename from i2p2www/meetings/logs/47.log rename to i2p2www/meetings/logs/047.log diff --git a/i2p2www/meetings/logs/47.rst b/i2p2www/meetings/logs/047.rst similarity index 100% rename from i2p2www/meetings/logs/47.rst rename to i2p2www/meetings/logs/047.rst diff --git a/i2p2www/meetings/logs/49.log b/i2p2www/meetings/logs/049.log similarity index 100% rename from i2p2www/meetings/logs/49.log rename to i2p2www/meetings/logs/049.log diff --git a/i2p2www/meetings/logs/49.rst b/i2p2www/meetings/logs/049.rst similarity index 100% rename from i2p2www/meetings/logs/49.rst rename to i2p2www/meetings/logs/049.rst diff --git a/i2p2www/meetings/logs/50.log b/i2p2www/meetings/logs/050.log similarity index 100% rename from i2p2www/meetings/logs/50.log rename to i2p2www/meetings/logs/050.log diff --git a/i2p2www/meetings/logs/50.rst b/i2p2www/meetings/logs/050.rst similarity index 100% rename from i2p2www/meetings/logs/50.rst rename to i2p2www/meetings/logs/050.rst diff --git a/i2p2www/meetings/logs/51.log b/i2p2www/meetings/logs/051.log similarity index 100% rename from i2p2www/meetings/logs/51.log rename to i2p2www/meetings/logs/051.log diff --git a/i2p2www/meetings/logs/51.rst b/i2p2www/meetings/logs/051.rst similarity index 100% rename from i2p2www/meetings/logs/51.rst rename to i2p2www/meetings/logs/051.rst diff --git a/i2p2www/meetings/logs/52.log b/i2p2www/meetings/logs/052.log similarity index 100% rename from i2p2www/meetings/logs/52.log rename to i2p2www/meetings/logs/052.log diff --git a/i2p2www/meetings/logs/52.rst b/i2p2www/meetings/logs/052.rst similarity index 100% rename from i2p2www/meetings/logs/52.rst rename to i2p2www/meetings/logs/052.rst diff --git a/i2p2www/meetings/logs/53.log b/i2p2www/meetings/logs/053.log similarity index 100% rename from i2p2www/meetings/logs/53.log rename to i2p2www/meetings/logs/053.log diff --git a/i2p2www/meetings/logs/53.rst b/i2p2www/meetings/logs/053.rst similarity index 100% rename from i2p2www/meetings/logs/53.rst rename to i2p2www/meetings/logs/053.rst diff --git a/i2p2www/meetings/logs/54.log b/i2p2www/meetings/logs/054.log similarity index 100% rename from i2p2www/meetings/logs/54.log rename to i2p2www/meetings/logs/054.log diff --git a/i2p2www/meetings/logs/54.rst b/i2p2www/meetings/logs/054.rst similarity index 100% rename from i2p2www/meetings/logs/54.rst rename to i2p2www/meetings/logs/054.rst diff --git a/i2p2www/meetings/logs/55.log b/i2p2www/meetings/logs/055.log similarity index 100% rename from i2p2www/meetings/logs/55.log rename to i2p2www/meetings/logs/055.log diff --git a/i2p2www/meetings/logs/55.rst b/i2p2www/meetings/logs/055.rst similarity index 100% rename from i2p2www/meetings/logs/55.rst rename to i2p2www/meetings/logs/055.rst diff --git a/i2p2www/meetings/logs/56.log b/i2p2www/meetings/logs/056.log similarity index 100% rename from i2p2www/meetings/logs/56.log rename to i2p2www/meetings/logs/056.log diff --git a/i2p2www/meetings/logs/56.rst b/i2p2www/meetings/logs/056.rst similarity index 100% rename from i2p2www/meetings/logs/56.rst rename to i2p2www/meetings/logs/056.rst diff --git a/i2p2www/meetings/logs/57.log b/i2p2www/meetings/logs/057.log similarity index 100% rename from i2p2www/meetings/logs/57.log rename to i2p2www/meetings/logs/057.log diff --git a/i2p2www/meetings/logs/57.rst b/i2p2www/meetings/logs/057.rst similarity index 100% rename from i2p2www/meetings/logs/57.rst rename to i2p2www/meetings/logs/057.rst diff --git a/i2p2www/meetings/logs/58.log b/i2p2www/meetings/logs/058.log similarity index 100% rename from i2p2www/meetings/logs/58.log rename to i2p2www/meetings/logs/058.log diff --git a/i2p2www/meetings/logs/58.rst b/i2p2www/meetings/logs/058.rst similarity index 100% rename from i2p2www/meetings/logs/58.rst rename to i2p2www/meetings/logs/058.rst diff --git a/i2p2www/meetings/logs/59.log b/i2p2www/meetings/logs/059.log similarity index 100% rename from i2p2www/meetings/logs/59.log rename to i2p2www/meetings/logs/059.log diff --git a/i2p2www/meetings/logs/59.rst b/i2p2www/meetings/logs/059.rst similarity index 100% rename from i2p2www/meetings/logs/59.rst rename to i2p2www/meetings/logs/059.rst diff --git a/i2p2www/meetings/logs/60.log b/i2p2www/meetings/logs/060.log similarity index 100% rename from i2p2www/meetings/logs/60.log rename to i2p2www/meetings/logs/060.log diff --git a/i2p2www/meetings/logs/60.rst b/i2p2www/meetings/logs/060.rst similarity index 100% rename from i2p2www/meetings/logs/60.rst rename to i2p2www/meetings/logs/060.rst diff --git a/i2p2www/meetings/logs/61.log b/i2p2www/meetings/logs/061.log similarity index 100% rename from i2p2www/meetings/logs/61.log rename to i2p2www/meetings/logs/061.log diff --git a/i2p2www/meetings/logs/61.rst b/i2p2www/meetings/logs/061.rst similarity index 100% rename from i2p2www/meetings/logs/61.rst rename to i2p2www/meetings/logs/061.rst diff --git a/i2p2www/meetings/logs/62.log b/i2p2www/meetings/logs/062.log similarity index 100% rename from i2p2www/meetings/logs/62.log rename to i2p2www/meetings/logs/062.log diff --git a/i2p2www/meetings/logs/62.rst b/i2p2www/meetings/logs/062.rst similarity index 100% rename from i2p2www/meetings/logs/62.rst rename to i2p2www/meetings/logs/062.rst diff --git a/i2p2www/meetings/logs/63.log b/i2p2www/meetings/logs/063.log similarity index 100% rename from i2p2www/meetings/logs/63.log rename to i2p2www/meetings/logs/063.log diff --git a/i2p2www/meetings/logs/63.rst b/i2p2www/meetings/logs/063.rst similarity index 100% rename from i2p2www/meetings/logs/63.rst rename to i2p2www/meetings/logs/063.rst diff --git a/i2p2www/meetings/logs/64.log b/i2p2www/meetings/logs/064.log similarity index 100% rename from i2p2www/meetings/logs/64.log rename to i2p2www/meetings/logs/064.log diff --git a/i2p2www/meetings/logs/64.rst b/i2p2www/meetings/logs/064.rst similarity index 100% rename from i2p2www/meetings/logs/64.rst rename to i2p2www/meetings/logs/064.rst diff --git a/i2p2www/meetings/logs/65.log b/i2p2www/meetings/logs/065.log similarity index 100% rename from i2p2www/meetings/logs/65.log rename to i2p2www/meetings/logs/065.log diff --git a/i2p2www/meetings/logs/65.rst b/i2p2www/meetings/logs/065.rst similarity index 100% rename from i2p2www/meetings/logs/65.rst rename to i2p2www/meetings/logs/065.rst diff --git a/i2p2www/meetings/logs/66.log b/i2p2www/meetings/logs/066.log similarity index 100% rename from i2p2www/meetings/logs/66.log rename to i2p2www/meetings/logs/066.log diff --git a/i2p2www/meetings/logs/66.rst b/i2p2www/meetings/logs/066.rst similarity index 100% rename from i2p2www/meetings/logs/66.rst rename to i2p2www/meetings/logs/066.rst diff --git a/i2p2www/meetings/logs/68.log b/i2p2www/meetings/logs/068.log similarity index 100% rename from i2p2www/meetings/logs/68.log rename to i2p2www/meetings/logs/068.log diff --git a/i2p2www/meetings/logs/68.rst b/i2p2www/meetings/logs/068.rst similarity index 100% rename from i2p2www/meetings/logs/68.rst rename to i2p2www/meetings/logs/068.rst diff --git a/i2p2www/meetings/logs/69.log b/i2p2www/meetings/logs/069.log similarity index 100% rename from i2p2www/meetings/logs/69.log rename to i2p2www/meetings/logs/069.log diff --git a/i2p2www/meetings/logs/69.rst b/i2p2www/meetings/logs/069.rst similarity index 100% rename from i2p2www/meetings/logs/69.rst rename to i2p2www/meetings/logs/069.rst diff --git a/i2p2www/meetings/logs/70.log b/i2p2www/meetings/logs/070.log similarity index 100% rename from i2p2www/meetings/logs/70.log rename to i2p2www/meetings/logs/070.log diff --git a/i2p2www/meetings/logs/70.rst b/i2p2www/meetings/logs/070.rst similarity index 100% rename from i2p2www/meetings/logs/70.rst rename to i2p2www/meetings/logs/070.rst diff --git a/i2p2www/meetings/logs/71.log b/i2p2www/meetings/logs/071.log similarity index 100% rename from i2p2www/meetings/logs/71.log rename to i2p2www/meetings/logs/071.log diff --git a/i2p2www/meetings/logs/71.rst b/i2p2www/meetings/logs/071.rst similarity index 100% rename from i2p2www/meetings/logs/71.rst rename to i2p2www/meetings/logs/071.rst diff --git a/i2p2www/meetings/logs/72.log b/i2p2www/meetings/logs/072.log similarity index 100% rename from i2p2www/meetings/logs/72.log rename to i2p2www/meetings/logs/072.log diff --git a/i2p2www/meetings/logs/72.rst b/i2p2www/meetings/logs/072.rst similarity index 100% rename from i2p2www/meetings/logs/72.rst rename to i2p2www/meetings/logs/072.rst diff --git a/i2p2www/meetings/logs/73.log b/i2p2www/meetings/logs/073.log similarity index 100% rename from i2p2www/meetings/logs/73.log rename to i2p2www/meetings/logs/073.log diff --git a/i2p2www/meetings/logs/73.rst b/i2p2www/meetings/logs/073.rst similarity index 100% rename from i2p2www/meetings/logs/73.rst rename to i2p2www/meetings/logs/073.rst diff --git a/i2p2www/meetings/logs/74.log b/i2p2www/meetings/logs/074.log similarity index 100% rename from i2p2www/meetings/logs/74.log rename to i2p2www/meetings/logs/074.log diff --git a/i2p2www/meetings/logs/74.rst b/i2p2www/meetings/logs/074.rst similarity index 100% rename from i2p2www/meetings/logs/74.rst rename to i2p2www/meetings/logs/074.rst diff --git a/i2p2www/meetings/logs/75.log b/i2p2www/meetings/logs/075.log similarity index 100% rename from i2p2www/meetings/logs/75.log rename to i2p2www/meetings/logs/075.log diff --git a/i2p2www/meetings/logs/75.rst b/i2p2www/meetings/logs/075.rst similarity index 100% rename from i2p2www/meetings/logs/75.rst rename to i2p2www/meetings/logs/075.rst diff --git a/i2p2www/meetings/logs/76.log b/i2p2www/meetings/logs/076.log similarity index 100% rename from i2p2www/meetings/logs/76.log rename to i2p2www/meetings/logs/076.log diff --git a/i2p2www/meetings/logs/76.rst b/i2p2www/meetings/logs/076.rst similarity index 100% rename from i2p2www/meetings/logs/76.rst rename to i2p2www/meetings/logs/076.rst diff --git a/i2p2www/meetings/logs/77.log b/i2p2www/meetings/logs/077.log similarity index 100% rename from i2p2www/meetings/logs/77.log rename to i2p2www/meetings/logs/077.log diff --git a/i2p2www/meetings/logs/77.rst b/i2p2www/meetings/logs/077.rst similarity index 100% rename from i2p2www/meetings/logs/77.rst rename to i2p2www/meetings/logs/077.rst diff --git a/i2p2www/meetings/logs/78.log b/i2p2www/meetings/logs/078.log similarity index 100% rename from i2p2www/meetings/logs/78.log rename to i2p2www/meetings/logs/078.log diff --git a/i2p2www/meetings/logs/78.rst b/i2p2www/meetings/logs/078.rst similarity index 100% rename from i2p2www/meetings/logs/78.rst rename to i2p2www/meetings/logs/078.rst diff --git a/i2p2www/meetings/logs/79.log b/i2p2www/meetings/logs/079.log similarity index 100% rename from i2p2www/meetings/logs/79.log rename to i2p2www/meetings/logs/079.log diff --git a/i2p2www/meetings/logs/79.rst b/i2p2www/meetings/logs/079.rst similarity index 100% rename from i2p2www/meetings/logs/79.rst rename to i2p2www/meetings/logs/079.rst diff --git a/i2p2www/meetings/logs/80.log b/i2p2www/meetings/logs/080.log similarity index 100% rename from i2p2www/meetings/logs/80.log rename to i2p2www/meetings/logs/080.log diff --git a/i2p2www/meetings/logs/80.rst b/i2p2www/meetings/logs/080.rst similarity index 100% rename from i2p2www/meetings/logs/80.rst rename to i2p2www/meetings/logs/080.rst diff --git a/i2p2www/meetings/logs/81.log b/i2p2www/meetings/logs/081.log similarity index 100% rename from i2p2www/meetings/logs/81.log rename to i2p2www/meetings/logs/081.log diff --git a/i2p2www/meetings/logs/81.rst b/i2p2www/meetings/logs/081.rst similarity index 100% rename from i2p2www/meetings/logs/81.rst rename to i2p2www/meetings/logs/081.rst diff --git a/i2p2www/meetings/logs/82.log b/i2p2www/meetings/logs/082.log similarity index 100% rename from i2p2www/meetings/logs/82.log rename to i2p2www/meetings/logs/082.log diff --git a/i2p2www/meetings/logs/82.rst b/i2p2www/meetings/logs/082.rst similarity index 100% rename from i2p2www/meetings/logs/82.rst rename to i2p2www/meetings/logs/082.rst diff --git a/i2p2www/meetings/logs/90.log b/i2p2www/meetings/logs/090.log similarity index 100% rename from i2p2www/meetings/logs/90.log rename to i2p2www/meetings/logs/090.log diff --git a/i2p2www/meetings/logs/90.rst b/i2p2www/meetings/logs/090.rst similarity index 100% rename from i2p2www/meetings/logs/90.rst rename to i2p2www/meetings/logs/090.rst diff --git a/i2p2www/meetings/logs/92.log b/i2p2www/meetings/logs/092.log similarity index 100% rename from i2p2www/meetings/logs/92.log rename to i2p2www/meetings/logs/092.log diff --git a/i2p2www/meetings/logs/92.rst b/i2p2www/meetings/logs/092.rst similarity index 100% rename from i2p2www/meetings/logs/92.rst rename to i2p2www/meetings/logs/092.rst diff --git a/i2p2www/meetings/logs/93.log b/i2p2www/meetings/logs/093.log similarity index 100% rename from i2p2www/meetings/logs/93.log rename to i2p2www/meetings/logs/093.log diff --git a/i2p2www/meetings/logs/93.rst b/i2p2www/meetings/logs/093.rst similarity index 100% rename from i2p2www/meetings/logs/93.rst rename to i2p2www/meetings/logs/093.rst diff --git a/i2p2www/meetings/logs/95.log b/i2p2www/meetings/logs/095.log similarity index 100% rename from i2p2www/meetings/logs/95.log rename to i2p2www/meetings/logs/095.log diff --git a/i2p2www/meetings/logs/95.rst b/i2p2www/meetings/logs/095.rst similarity index 100% rename from i2p2www/meetings/logs/95.rst rename to i2p2www/meetings/logs/095.rst diff --git a/i2p2www/meetings/logs/99.log b/i2p2www/meetings/logs/099.log similarity index 100% rename from i2p2www/meetings/logs/99.log rename to i2p2www/meetings/logs/099.log diff --git a/i2p2www/meetings/logs/99.rst b/i2p2www/meetings/logs/099.rst similarity index 100% rename from i2p2www/meetings/logs/99.rst rename to i2p2www/meetings/logs/099.rst diff --git a/i2p2www/meetings/logs/10.rst b/i2p2www/meetings/logs/10.rst deleted file mode 100644 index b5d141f6..00000000 --- a/i2p2www/meetings/logs/10.rst +++ /dev/null @@ -1,7 +0,0 @@ -I2P dev meeting, September 4 2002 -================================= - -Quick recap ------------ - -TODO diff --git a/i2p2www/meetings/logs/221.log b/i2p2www/meetings/logs/221.log new file mode 100644 index 00000000..d6a68c4d --- /dev/null +++ b/i2p2www/meetings/logs/221.log @@ -0,0 +1,319 @@ +21:01:00 So, who is here? +21:01:11 Me. +21:01:18 o/ +21:01:37 i'm here :) +21:02:10 eche|on, Meeh, KillYourTV, psi, hottuna +21:02:21 count me in too (as a spectator) +21:02:28 * nom is listening, while coding on some side projects +21:02:39 Feel free to contribute if you feel you have something to add. +21:03:04 * dg waits a minute or two more +21:03:27 rundown of topics in the meantime dg? +21:03:42 Topics: +21:03:45 * Motivating the community - "are bounties appropriate?" +21:03:45 * Managing money +21:03:46 ** Making the project "official" - benefits/negatives/how +21:04:24 i had something to add *thinks* +21:04:31 hm? +21:06:37 * lillith can't remember... probably nothing too important anyway :) +21:09:14 * dg frowns at the lack of others +21:09:44 * LaughingBuddha spectates +21:10:27 Let's start then +21:10:54 * lillith remembered! +21:10:59 hm? +21:11:14 RN: ping +21:11:25 as kytv|away pointed out, if we're deciding on voting we need some sort of elegibility criteria :) +21:11:49 aye +21:12:07 Let's get started +21:12:10 * Motivating the community - "are bounties appropriate?" +21:12:13 i expect asdfsdafsdafsd wishes to be invluded int points 1+2 :) +21:12:24 Are bounties working? +21:12:43 Everything merged into one big argument last time over bounties, management and BTC so trying to spread it out this time & be dignified. +21:12:53 Who's the guy for bounties? eche|on? +21:13:00 yep +21:13:11 Is he here? +21:13:11 Determining if bounties are working depends on what the defined purpose of a bounty is. +21:13:11 define "working". Are they, IMO, bringing in the developers or fixes we need? No. +21:13:18 he's in control of all money - point 2 :) +21:13:25 Then let's think of something else. +21:13:40 The bounty system does not seem to be working for even the bounties themselves. +21:13:54 i think there should be some sort of benefit or incentive further than loving i2p +21:14:09 A lot of the links on the page are 404s too but that's an unrelated issue +21:14:12 From the bounties page: " Instead, we are making use of a bounty system, whereby anyone can get support for working on something that people want implemented, and people who want to contribute to I2P can be assured that their support goes to what they care about." +21:14:12 we have to draw people in then keep them with our charm and civility ;) +21:14:23 Not that I'm in the position to work on any of the bounties, but they seemed to quite vague last time i looked at them +21:14:30 to be* +21:14:37 The only thing that will draw attention to I2P is content. +21:14:45 eche|on posted his thoughts here - http://zzz.i2p/topics/1359 - if he could not attend. +21:14:48 imo bounties do not work, because a code base is only as good as its maintenance, and paying someone for 'completion' gives the wrong ideas/incentives about what we need in terms of developers, for code to be worth using on a distributed scale, it has to be continually worked on by motivated people. having one person create a code base, get paid and possibly disappear does nothing to benefit the community +21:14:51 Title: zzz.i2p: Managing the project (at zzz.i2p) +21:14:57 str4d: instead, as opposed to...? +21:15:17 From that statement above, the purpose of bounties would seem to be to finance one-off drives to get specific features implemented. +21:15:20 are bounties appropriate? - I think it depends, imo bounties for devs, for particular project and where no contest/conmpetiotion is involved - in such cases they are appropriate +21:15:26 nom: it worked in the past if you look at the bounty page.. +21:15:30 str4d: Is that what we want? +21:15:41 nom: agreed +21:15:48 Does that work? Somewhat. +21:16:03 weltende, exactly. There are clear examples of bounties being taken. +21:16:18 http://www.i2p2.de/bounties.html +21:16:29 Title: Bounties - I2P (at www.i2p2.de) +21:16:34 Bounty uptake IS slow, due to a lack of visibility/advertising/marketing/whatever, but the bounties are slowly getting taken. +21:16:41 I don't know if the bounties which are being fufilled are perhaps not being fufilled the way we want too. +21:17:03 But, of the claimed bounties, not a single developer is currently with I2P. +21:17:10 For example: "Datastore over I2P" - "CLAIMED for 700 euro" - "duck, smeghead" +21:17:20 perhaps, change bounties to ..... and maintain your work for a reasonable time +21:17:23 to get actual continuous development going, a better model is one of project/stipends, where people donate to a project with stated goals, and the people running that project pay the money out continuously to people who are actively working to accomplish those goals +21:17:34 The solution was, IMO, hacky, the bountry $$$ was rather high for the hack and the two developers for that bounty are nowhere to be found. +21:17:46 dg: that's irrelevant - as per the current bounty outline, it is up to the donor to decide on the completion. +21:18:01 What if multiple donors exist? +21:18:08 First donor. +21:18:11 I don't like bounties. IMO, the one way to draw developers in is to draw attention to I2P. +21:18:15 (as per current outline) +21:18:21 lillith: not really needed imho if it's in the core router.. +21:18:25 If a bounty is funded by I2P, then it does become relevant as I2P itself is the judge. +21:18:32 Oh. That doesn't seem right. :s. +21:18:54 IMO, the best way to draw attention to I2P is by providing content. +21:19:06 Right, but some of the bounties can lead to content. +21:19:13 I'm not arguing for the current bounty system, just outlining it. +21:19:44 str4d: right, and thanks. +21:20:03 honestly i think a big part of the problem is that were conflating things that are directly part of the i2p code base, with things that are simply run ontop of i2p. ex translation vs datastore +21:20:03 The biggest problem with a semi-anonymous project like I2P is developer retention. The current bounty model does nothing to help that. +21:20:42 I'm against the bounty system as it doesn't help the ecosystem we have, evidently (none of the developers are here today..) and I feel project funds could be better allocated. +21:20:57 a bounty/payment for one person to do one specific part of the code base is fine in theory, but they don't work for creating continuous development of apps/systems that run ontop of i2p +21:21:12 I concur. +21:21:17 dg: well.. if there aren't taken, then the money isn't spent.. +21:21:54 weltende: The funds are in reserve, they cannot be spent as they are allocated for spending on $bounty. +21:21:57 like adding unit tests to i2p could be worth a bounty, but it would probably be better to make an arrangement with coders who will be paid a small amount continuously to keep adding more unit tests as needed +21:22:03 if you however think that for a certain bounty the code isn't good enough or so.. it might be a good idea to specify more clearly in the bounty description what needs to be done +21:22:26 dg: which is only a problem if we have to spend the money right away +21:23:01 it's not reserved forever as you can see in the bounty page.. funds have gone back to the money pool before +21:23:21 weltende: I doubt we will ever be at the point where we NEED the funds allocated to bounties but it seems redundant. +21:23:44 Fund allocation is beside the current point. +21:23:59 dg: exactly my point +21:24:11 dg: are competitions included in bounties or are they point 1.5? +21:24:14 There will always be money, in one way or another. +21:24:26 (Or not) +21:24:29 i think the datastore is a great example of where bounties shouldn't be used, for something as complex as a universal datastore to be viable, it has to be its own project with active developers, paying someone for completion will get you something that is marginally functional, but it will never improve +21:24:40 ^ +21:24:40 nom: agreed. +21:24:43 lillith: Competitions hadn't occurred to me but I suppose it would be the point after this. +21:24:46 Let me refer to the i2p artwork contest for 29c3 - Was that really a dev project? Was it appropriate to use bounties in it? While there was no even strict criteria stated? +21:24:57 The result will satisfy the bounty, but likely will not scale. +21:25:00 nom: Couldn't have said it better myself. +21:25:26 nom: torrents were nothing but a bounty either.. +21:25:34 Umlaut: i thought they were echelons personal funds? +21:25:54 if I was willing to contribute to the contest, the bounty would rather discourage me? +21:26:01 (most) bounties are set by users - between giving them a choice and them not donating at all, at least with a bounty they have some say in what happens +21:26:32 to put it another way... there are no bounties at google.... +21:26:32 LaughingBuddha really? then sorry, I wasn't aware about that +21:26:32 weltende yes but zzz is continuing to work on snark isn't he? +21:26:47 If I2P had an established structure for spinning off projects (or acting as an umbrella for them) then that would be a different matter (but that ties in to the later point about "official"ness). +21:26:51 Umlaut: I might be mistaken but I thought i read that somewhere +21:27:04 I think that bounties are useful, but not in the way that they are currently being marketed. +21:27:08 LaughingBuddha: all i2p's funds are technically eche|on's personal money +21:27:11 nom: zzz was around anyway though. I think his motivations and such are different than gaining rewards and the bounty program has little to do with it. I do not believe he gained anything from the torrent bounty either. +21:27:18 And that they shouldn't be the main focus. +21:27:21 nom: yes.. but without the bounty there wouldn't have been a codebase to begin with.. (and he was not part of the bounty dev team) +21:27:21 We'll get to the money later.. +21:27:40 lillith: Doesn't he "manage" it? +21:27:47 dg: ok +21:28:10 weltende, you are making a good point. +21:28:14 i2p is no legal entity, so it can't own anything. hence it is eche|on's personal money. +21:28:29 Bounties are useful for kickstarting code, not for continued development. +21:28:36 lillith: I see +21:28:36 if you want continuous development you should pay developers continuously to work on things they want to work on. donating money to get something done is fine, but it shouldn't be given as a lump sum to whoever can get an 0.0.1 working first, it should be used to fund project development over time +21:28:39 he could legally leave with it all one day (he wouldnt', but he could) +21:28:48 nom: and I don't really see your point with no bounties at google.. the people that work for google get paid to work there.. +21:28:52 ^this +21:29:27 But it seems we agree with the first part of nom's statement. No? +21:29:30 eg bounty of $X per month to work on something +21:29:45 Yeah +21:29:52 or perhaps define milestones in the bounty? +21:29:56 Seems like a good solution +21:30:07 (and upon reaching milestone $X you get $Y amount of money) +21:30:07 That sounds good. +21:30:14 milestones seem like a good idea +21:30:17 but they need to be clearly outlined +21:30:20 Milestones + continuous payment? +21:30:20 lol thats what my point was, they get paid, and they do work, and the work they do isn't directly connected with how they get paid. ofc if they stopped doing work, they would stop getting paid, but their not getting paid for completing a specific piece of code, their getting paid enough to live on and spend their lives coding +21:30:23 Milestones is sort of like what the Unit Tests bounty currently has. +21:30:27 is it eche|on we have to ask nicely to change the website etc? +21:30:38 no, website is in mtn +21:30:41 nom I agree with your point, paying to the devs who are reliable and known for being good contributors +21:30:44 lillith: no, anyone can change the website. +21:30:54 Or keep a part of the bounty as a "continued support" payment per month of the application/whatever +21:31:22 So we don't get outdated apps, libs, etc. +21:31:29 Would the project be judged at every milestone then? +21:31:44 LaughingBuddha: good point. Who by? +21:32:00 eh, milestones are just smaller bounties... a simpler solution is to have a pool of money for a project, and someone/group of someones who pay the money to people who are actively working on it +21:32:03 The "board"? (Againg, getting to this later). +21:32:10 Dev board? +21:32:10 yeah +21:32:29 generally you would end up with the dev board being the same people who are getting paid ofc... +21:32:46 to make anything decided upon here 'official', is that as simple as someone checking an update to the website into mtn? +21:32:55 how many active devs are there working on the i2p codebase? +21:32:58 also you need to take under consideration how the current donating system looks from the potential donor (someone new to i2p community especially) point of view +21:33:04 LaughingBuddha: one +21:33:07 lillith: Kinda. And posting ot zzz.i2p. ;_; +21:33:15 The dev board determine the state of $project and decide if it should continue to get funding? +21:33:18 i could be one of them +21:33:25 LaughingBuddha: 2, 3? +21:33:32 hmm +21:33:47 the board / employees model seems to work pretty well for 99% of the corporations in the world. you have a group of people who are the most committed and have already contributed a lot who manage the money, and you have people who join and contribute and get paid for their efforts based on the judgement of the long time contributors +21:33:54 What if we set up a board of min. 5 people who are knowledgeable on the subject? +21:34:01 Devs + Users +21:34:09 and i would trust the system more if there was more than one person, something like mentioned already dev-board which handles the money +21:34:24 What if you had to pay to be on the board? +21:34:31 wut +21:34:38 (this only works tho if you can separate i2p proper projects, from projects that just run on i2p, which should not be managed by the i2p dev team itself) +21:34:38 orion: not a good model. +21:34:47 inb4 Russian oligarch takes over I2P +21:34:57 haha +21:35:06 inb4 already happened, zzz = vladimir +21:35:10 Pay in code. +21:35:29 And how do you measure how much you have to pay? +21:35:32 200 lines of code? +21:35:35 some people are big contributers without coding +21:35:46 No idea, just brainstorming. +21:35:49 like any oligarchy the only natural system is election by the existing board +21:35:49 Exactly. +21:36:03 So, would the normal "dev" (team) board (coming up later) decide if $project is worth paying out to? +21:36:15 Overcomplication will lead to it not being done +21:36:22 3 tiers: inner circle, outer circle, others +21:36:30 lillith: i like that +21:36:37 other = new/ unknown people +21:36:51 outer circle = known/ trusted people +21:36:51 because we don't seem to have enough devs for a real judge panel +21:37:02 dg I would think so as the devs should know *best* what project are most important/urgent/worth spending money on +21:37:05 inner circle voted for by outer circle +21:37:20 its a hierarchy, the i2p project as a whole is more than just the i2p dev team, but they are the tip of the spear so to speak. they get / have the most donations / resources. but other projects built ontop of i2p wouldn't be managed by the i2p dev team, but could get funding from i2p proper +21:37:23 kind like meetings but more structured hierachally +21:38:13 imo <+dg> Overcomplication will lead to it not being done +21:38:37 +1 +21:39:15 The whole (team/dev) "board" idea ties in nicely as we will be discussing this next anyway +21:39:22 Should we leave this for another time or ...? +21:39:28 in short, zzz eche and whoever else they consider to be part of the 'board' of i2p are in charge of the money/decisions (they already are), and other projects on i2p should be structured similarly with their own boards of decision makers. instead of bounties for a sub project (datastore, btc client, etc) the bountie should be given to the board for that project, and let them decide how to spend it to get things done +21:39:39 so shall we get back on topic or has bouties been discussed to death? +21:40:49 and the decision to give a bounty to a board of devs for a project obviously has to be made by the board of i2p, that way you don't have 3 people show up, say their gonna do something, get the money and then never do it. +21:41:13 nom: +1 +21:41:21 nom: +1 +21:41:24 nom: I think it's payed out upon completion +21:41:34 nom++ +21:41:46 nom: +1 +21:41:54 I think that's a good note to end on? :) +21:42:14 Agreed +21:42:24 in the future it would be better for donators to give directly to the sub project if a board/group already exists, instead of donating to eche to create a bounty. since if theres already a group working on it, they would be the best to determine how to use the money to accomplish those goals +21:42:53 ok, moving on +21:42:58 nom that makes perfect sense +21:43:01 nom++ +21:43:11 * nom raises his glass, cheers mates +21:43:18 I feel we have covered "managing money" mostly and it comes under "making the project official" anyway +21:43:21 :) +21:43:21 So let's do the latter? +21:43:47 clarify the position on money first for lurkers? +21:43:54 for an e.V. we would at least 7 people who are willing to go public as members +21:43:55 Official = Register as Organisation? +21:44:26 LaughingBuddha: yes +21:44:29 in case register as a organization, in which country? +21:45:01 lillith: Bounty funds should go to teams assigned by the core I2P board.. if we go ahead with that. +21:45:04 Meeh: US, I assume? +21:45:07 that also need deanonymization of sertiant people +21:45:14 ok so who are the brave souls to give up their anonymity (if that means going official)? +21:45:17 What did you guys decide on? +21:45:20 Not necessarily the US +21:45:28 idk if 'offical' designation would really be all that useful... i honestly can't see what the benefit would be +21:45:31 presumably the people have to be in the US too? +21:45:54 nom: a legal entity to donate to +21:45:54 other than to put the project/people more on the radar of the powers that be... +21:46:06 I can give out my identity, so no problem for me.. But I guess I'm not allowed into the US, so yea. +21:46:17 Registration is stupid. +21:46:28 dg: What are the benefits? +21:46:39 Let's just spread out the money among different "accounts" managed by different people. +21:46:55 I.e, the eche|on account, the zzz account, the dg account, etc. +21:46:57 A wallet for each (sub)project? +21:47:04 LaughingBuddha: Managing the project's money under "I2P" and not a singular person, or persons. An official guise is far less suspicious and accountable. +21:47:09 No. +21:47:12 Do you think that going official would bring some real benefits to the i2p-world? +21:47:14 orion: not sure if the tax office might not find tht fishy +21:47:14 Just different "accounts". +21:47:32 * nom thinks the focus should be more on the logistics of the hierarchy of boards / democracy / voting thing. to actually have a system like that we would need either a well run website, or some sort of distributed system for it +21:47:35 dg: I see +21:47:46 it would certainly bring a lot of paperwork +21:47:54 Umlaut: no more complaining about eche|on holding the money +21:48:04 nom++ +21:48:13 * str4d@freenode clones nom's brain +21:48:14 nom: perhaps so, yeah. If we can arrange that, then we can come to a consensus on this.. +21:48:44 For the record, if you guys want to do something that requires giving up anonymity, I will do it. +21:48:57 git clone http://git.repo.i2p/repo/nom.git +21:49:00 I'd consider it +21:49:03 Going "official" is primarily a financial decision IMHO; it doesn't really contribute to the structure. +21:49:22 Even though I am opposed to the idea of going to the government, I will do it if that is what the project decides is best. +21:49:40 So, let's change the focus to the organizational structure +21:49:51 (As that supercedes this anyhow) +21:50:06 str4d: well.. e.V. requires the members to vote for an board once a year... so we already have procedure for voting for the board then ;) +21:50:14 "The Debian project only allows voting to be done by 'Debian Developers' (where "$developer" = "any sort of contributor"). If there is any sort of voting system enabled here it would need to be limited in a similar fashion, otherwise the system would be ripe for abuse, allowing for a small but vocal clique to push its demands through." +21:50:21 Should we adopt a similar approach? +21:50:25 (for the e.V.) +21:50:44 how much do you need to contribute to be a contributer? +21:50:59 The problem with the "Debian Developers" approach is the number of developers I2P has (very few) +21:51:05 ie is being active in #i2p-help enough? +21:51:25 we must find a definition on contributer +21:51:33 for what? +21:51:36 * lillith does not read 'contributer' as 'code contributer' +21:51:55 str4d: "any sort of contributor". +21:51:59 sigint: read scrollback on sighup ;) +21:52:10 will do +21:52:12 dg, yeah, just read that part *derp* +21:52:12 org structure is pretty simple in theory, just have a three tiered system of board members (elected by the existing board oligarchy), contributors (elected at large by the existing group of contributors), and users (everyone else, including people who /want/ to be seen as contributors, but havn't been around long enough for people generally to trust them) +21:52:27 sighup's like your little brother ;) +21:52:39 it all depends on the scale of contribution, reliability of the contributor and other factors +21:53:06 sorta like, royalty, nobility, and the commoners.... +21:53:13 reliability = being trusted by others +21:53:16 maybe a good start will be starting with rough numbers and working from there? +21:53:31 nom i'm actaually referring to what you have said +21:54:09 not reliable = someone who promised to do something, raised some hope and then run away (with a bounty..) +21:54:24 hmm yah +21:55:35 nom: "existing"? +21:56:15 I gotta go. In closing I just want to say that having funds in one central location makes it easier to steal by oppressive governments, and that if we need to do something which requires giving up my anonymity, I will do it. Cya +21:56:26 perhaps, supreme court(board), senate(contributors) and house(users) would be better... the board has the real control over all the decisions, but they take into account the votes of the contributors who are trusted identities, and the votes of the general population of users too, but you don't weigh that too much as theres no real protection against people making tons of user idents to vote with +21:56:33 bye orion :) +21:56:37 Should we cut now and continue this next week at the same time? +21:56:40 o/ orion +21:56:50 An hour is long, I don't want this to drag on. +21:57:04 Whatever you want. +21:57:07 dg: i'm up for that +21:57:17 I'm happy to continue next week. +21:57:26 gives time to ponder what has already been said +21:57:29 sure, sounds good +21:57:31 We need to think this over. +21:57:43 And hopefully a few more people show up then ^_^ +21:58:07 * nom thinks the main takeaway here is that we could use a site / system to have group decision making / voting on +21:58:07 yes... +21:58:14 I agree, sounds good guys. I'll update the zzz.i2p topic soon (poke me if I don't in 24 hours). +21:58:25 thanks all. :) +21:58:29 Good session +21:58:32 * lillith picks up the baffer menacingly +21:58:42 ;) go +21:58:53 thanks for letting me join +21:58:53 *baf* meeting closed :) +21:59:04 lights out! +21:59:06 thank you, and goodnight :) +21:59:19 Great. I joined in right at the end. I forgot that there even was one :| +21:59:22 inb4 massive well timed netsplit +21:59:25 brb, reading backlog +21:59:28 o/ +21:59:40 sigint timezone fail? +21:59:50 o/ sponge. +21:59:50 :-) +21:59:57 sigint: same time next week ;) say anything you missed the chance to then :) +22:00:12 orion wants to know about my ideas I see... +22:00:50 I pointed him in your direction sponge - figured pooling the creative juices was a good idea. +22:01:05 lillith: i hadn't explicitely planned on joining this meeting, but it would have been nice. no big deal though. i do have an idea that would be good to bring up in next week's meeting. +22:01:09 Yes, excellent. +22:01:32 I need people to help with my ideas... I have too many +22:01:35 idea: offer btc rewards for security vulnerabilities +22:01:39 sigint: it's dg you'll want to talk to on that then :) +22:01:41 (And orions work on i2pcpp has proven that he is good at implementing stuff ^_^) +22:01:58 sigint, post any ideas for next week in the zzz.i2p thread. +22:01:59 * lillith raises eyebrows +22:02:07 vairy interesting +22:02:10 will do diff --git a/i2p2www/meetings/logs/221.rst b/i2p2www/meetings/logs/221.rst new file mode 100644 index 00000000..aa831b9e --- /dev/null +++ b/i2p2www/meetings/logs/221.rst @@ -0,0 +1,19 @@ +I2P dev meeting, March 26, 2013 @ 21:00 UTC +=========================================== + +Quick recap +----------- + +* **Present:** + dg, + LaughingBuddha, + lillith, + Meeh, + nom, + orion, + str4d, + Umlaut, + weltende + +* **Next Meeting** + The next meeting is scheduled for Tuesday, April 2 @ 21:00 UTC (9:00PM) diff --git a/i2p2www/meetings/logs/222.log b/i2p2www/meetings/logs/222.log new file mode 100644 index 00000000..b5932209 --- /dev/null +++ b/i2p2www/meetings/logs/222.log @@ -0,0 +1,354 @@ +20:52:42 okay meeting topics for today: +20:54:22 1. Are bounties appropriate? +20:54:29 2. Managing money +20:54:29 2a. The ssl certs +20:54:32 3. Making the i2p project official +20:56:38 4. Procedure regarding decicions for the project (for example making it official) +20:56:53 for scrollback from last week if you were not here, http://sighup.i2p/irclogs/show?search=&user=&from_date=26+Mar+2013&to_date=26+Mar+2013&channels[]=#i2p-dev&per_page=3&page_format=Html +20:56:53 relevant zzz.i2p posts: http://zzz.i2p/topics/1359 for the meeting thread +20:56:53 http://zzz.i2p/topics/1366 for the bounties thread +20:57:07 Title: zzz.i2p: Managing the project (at zzz.i2p) +20:57:09 Title: zzz.i2p: I2P Bounty System - 2013 (at zzz.i2p) +20:57:55 chosen download bin file from zzz.i2p? +20:58:02 1. Are bounties appropriate, and further bounty discussion +20:58:05 Huh. Corruption again! +20:58:50 not sure who (if anyone) woud like to be pinged, so i'l go on +20:59:22 trolly: that's a bug +20:59:30 haha, no problem +20:59:41 Last week it was decided that while bounties can be a good thing they may well need some looking at +20:59:48 a trojan bug? just joking.. +20:59:59 try to nab the output of `http_proxy="http://127.0.0.1:4444/" http://zzz.i2p/whateverurlbrokebefore` and check /logs for anything important +21:00:05 it seems to be corruption, we saw this on id3nt.i2p in the past +21:00:19 i suggested some revisions of the 50 BTC syndie bounty to echelon, and he has updated it +21:01:06 which led me to two questions: can/should we employ people, ie give them a small amount of money regularly over an extended period? +21:01:57 and what exactly is the procedure on bounties funded by i2p's money, not directly from a donor +21:02:20 * lillith opens up the floor for discussion +21:04:50 dg: if it's occuring on another site, that suggests an I2P tunnel problem. +21:05:26 str4d_: This happened before, is what I am saying. I do not know if the person affected == trolly but it was a few months back and none of us had any answer. +21:05:41 * str4d_ was affected by it. +21:05:52 dg: !!! +21:05:56 Okay, more than one person. +21:06:10 I believe zab was still around at the time which may tell you the period.. +21:06:21 dr|z3d: !!! +21:06:24 But the issue is orthogonal to the current discussion =) +21:06:36 * dr|z3d lols. +21:06:47 str4d_: implying discussion ;) +21:08:32 should i2p employ people? yes and no IMO. yes the people that continue to provide services that make i2p of higher quality (such as running the default IRC network and the more popular things like id3nt.i2p) are the best candidates to receive funds... in addition to the developer stuff which may have bounties attached. +21:09:27 Shinobiwan: I wouldn't consider that employment though. +21:09:50 "Employment" would be payments for the purpose of direct I2P development (code or otherwise). +21:10:19 Shinobiwan: i2p should award effort and achievement. +21:10:43 what i had initially proposed was a small monthly payment for maintaining syndie, getting and keeping it into repos, bug fizing, etc +21:12:25 otoh, i2p should not award aspiration, lazinesss or failure to deliver. +21:12:32 That seems like a good compromise between the current bounty system and "proper" employment (which is hard for anonymous dev work) +21:13:20 Right. So if a monthly system were set up, the payment would be subject to "sufficient" work having been done. +21:13:31 dr|z3d: absolutely. there is plenty of money to give to people who deserve it +21:14:06 (So it would require a monthly meeting between the deciding people to analyze the various outputs during that period) +21:14:09 lillith: we're swimming in it. +21:14:35 I don't think that failure to deliver in one particular month should be cause for complete funding cuts, though. +21:15:03 commitment, dedication, service. +21:15:04 people have afk commitments as well as internet ones +21:15:07 derp, pingout. +21:15:37 remind me again why str4d_ isn't getting compensated? :) +21:16:07 I'd propose a more flexible system where the "employee" gets paid for the months they do sufficient work in. +21:16:07 (extended absences would be grounds for discontinuing funding though) +21:16:22 lillith: exactly (like zzz currently) +21:17:02 dr|z3d: under my proposed system, I wouldn't be at present =P +21:17:26 the threat of halebopp dropping indent inspires zzz to offer hosting costs. so why does str4d_ have to battle with eche|on to get hosting funding? +21:17:53 i offer one word: incompetence. +21:17:56 dr|z3d: that's on a tangent. +21:18:42 str4d_: more than likely. +21:18:45 what kind of maintenance work are we talking about here? shouldn't bugs and specific goals like repo inclusion be separate bounties so more than one person can claim them? +21:18:56 There are two kinds of potential funding that I can see - the bounty/employment hybrid above, and donations from I2P towards community services. These should be treated separately. +21:19:25 value added recompense. +21:20:00 anything else is jizz. like paying 10btc for dogpoo. +21:20:03 str4d_: and competitions too, if there were ever to be another +21:20:10 darrob: what we are trying to do is promote developers staying around. +21:20:13 lillith: true, that's a third category. +21:20:40 also beer. my bad. +21:21:34 I wouldn't mind being paid beer for my humor... ;) +21:21:43 from echelon.i2p: - the I2P general fund will cover all needed costs of I2P - discussed by dev team and will be noted here and on official webpage +21:22:09 i think most things would be acceptable as long as they are discussed and agreed upon beforehand +21:22:12 darrob: So rather than paying out a large lump sum for an arbitrary milestone and then the dev goes AWOL, we define smaller milestones and tasks within the confines of (what is currently called) the bounty, and the dev gets continual smaller payments. +21:23:55 The bounty system would still exist for bounties proposed by third parties (as they have control over how their funds are used), but for bounties that would be proposed by I2P itself from I2P funds, the new system should be better for I2P IMHO. +21:24:26 bounties are shit. hit and run contributors. +21:25:09 dr|z3d: hence why we are discussing a new system +21:25:12 not to mention "i paid $200, I'm important attitudes" +21:25:26 Part of the problem IMHO is that the current system only has a general description, with no concrete structure. +21:25:49 lillith: excuse me if i'm not quite following the finer points of the argument :) +21:25:52 For the new system, we need an agreed set of guidelines for proposing and managing funded tasks. +21:26:59 dr|z3d: if people want to waste/spend their money on bounties for improperly completed features, they should still be allowed to imho +21:27:58 lillith: yep. Or they can choose to use the new system, by donating their money to I2P and putting in a request through whatever process we decide on to set up a new funded task. +21:28:16 i agree - there is money there, and we might as well use it, so we might as well use it properly and effectively +21:28:56 and then if the donor goes awol it's still technically a community owned bounty +21:28:59 i'd like to see people sticking around too, of course, but i don't see how bounties are shit at all. on the other hand the monthly thing sounds like trouble but i don't mean to dismiss it too quickly. +21:29:02 Tasks funded via the new system need to be funded with money controlled by I2P, because it will be a panel of I2P representatives who decide what counts as "sufficient" work, not the donor themselves. +21:29:03 lillith: i disagree. donate to the project and let the project decide how to distribute rewards. +21:29:06 * Shinobiwan not sure if my other msgs went through +21:29:17 bounty and employment != donation ... both should take place I think... employment/bounty for dev specific stuff... and perhaps donations for things like community services +21:29:19 the employment part would need more of a specific set of conditions +21:29:24 the community service part, really just needs the community to decide what's worth supporting +21:29:27 and then dish out something appropriate +21:29:50 dr|z3d: both options will be there. +21:29:53 Shinobiwan: they didnt, now they did :) +21:30:04 Shinobiwan: http://killyourtv.i2p/irclogs/latest.log.html for scrollback. +21:30:07 Title: #i2p-dev logs for Tuesday, 2013-04-02 (at killyourtv.i2p) +21:30:12 "oh we need russian" no we don't. we need commitment. not money chasing rats that disappear as soon as the bounty is awarded. +21:30:24 thx str4d, K1773R +21:30:47 dr|z3d: a new, private infrastructure may well appear for paying individuals for work - it might as well all be in together +21:31:27 darrob: the reason most proposals sound like trouble is because we don't have a large enough developer base to properly run/support them. Therefore, a proposal that should result in a larger developer base is a good idea. +21:31:42 money should not be able to dictate the project. period. +21:32:01 and http://killyourtv.i2p/irclogs/%23i2p-dev.2013-04-02.log for "live" scrollback (the HTMLized logs are processed every 10 minutes or so) +21:32:16 sponsor the project, great, but don't tell us how to spend the money. +21:32:27 dr|z3d: i like it if a money chasing rat fixed certain features in syndie and ran. what's the problem? maybe someday syndie will get a real developer again but that person won't necessarily need payment then. actually, as far as committed maintainers are concerned, it might actually be counterproductive to offer a pay for the job. +21:33:05 thx KillYourTV +21:33:19 np +21:33:36 darrob: the "problem" is money thinking it can dictate the agenda. +21:33:39 dr|z3d: i2p isn't being told how to spend its money, because bounty money never was i2p's. i2p/echelon just act as an escrow service +21:33:39 Interesting point dr|z3d - I think part of this depends on what we define as the I2P project. +21:34:42 lillith: I think the point dr|z3d is making is that, rather than being told how to spend its money, I2P is being told how to proceed, i.e. the development path is decided by the person with the most money. +21:34:57 dr|z3d: bounties are just offers (or cries for help). where do you get the negative attitude? +21:35:21 And if the bounty process was adhered to as-is, that could potentially be rather problematic wrt the threat model. +21:36:18 that is a good point - i hadn't thought of it in that way before +21:36:47 a set of rules that says "This person must be paid on this date" is a good idea in that, that person can count on the income to be there when they need it. But on the other hand, it also may create drama when people fail to meet other people's expectations of what that money is really going towards... so I think it's probably not inappropriate to have meeting specifically for 'paydays' or whatever... if there's going to be a 'regular' thing. +21:37:35 bounties are shit. show me ongoing commitment from bounty hunters and i'll change my view. except you can't. hit and run merchants. +21:37:49 So maybe what needs to happen is that any tasks/sub-projects that affect I2P directly must be funded and controlled by I2P itself. +21:37:52 darrob: i get the "negative" attitudes from half complete work that's awarded a bounty, only to disappear before you can say "um, i think you missed..." +21:38:03 darrob: also, next time you pretend str4d_ is a css artist, don't bother. you insult yourself. +21:38:10 and you also lose a friend. +21:38:13 dr|z3d: didn't str4d_ and zzz claim some bounties for the unit tests? +21:38:17 dr|z3d: what? +21:38:20 dr|z3d: OT +21:38:55 str4d_: yeah. also, beer. darrob: if you don't get it, *yawn* +21:39:03 lillith: that was after the unit tests bounty was split up into sub-tasks/milestones (which I'd say was a step towards the proposed new system). +21:39:45 dr|z3d: keep on-topic in here please =) +21:39:56 I think everything has been said on this topic now no? +21:40:03 if bounties exist IMO they should go towards the things that nobody currently part of the community knows how to or can do, IMO... not the things they dont have time for. +21:40:06 * dr|z3d recalibrates. +21:40:06 i guess all i'm trying to say is that i question that hit and run improvements are necessarily a bad thing. +21:40:19 I2P will survive with everyone supporting it, not just the people who get paid +21:40:30 darrob: they are good for kickstarting development in a new area +21:40:37 But the I2P router/project is not a new area, IMHO +21:40:53 So, how about the following: +21:41:20 Shinobiwan: like design! *laughs* 5 years of asking for help, and not one iota of thought to offer a bounty *laughs* +21:41:58 Projects that directly affect the I2P program/network can be funded only from I2P funds, and donors who want to contribute just donate to I2P. +21:42:21 because designers aren't coders, ergo worth nothing. except when you're offering 10BTC/100$ for anything, including crayons. +21:42:47 Projects that don't directly affect the I2P program/network but are still I2P-related (e.g. syndie) are eligible for bounties on new/substantial work. +21:42:58 sorry, but I can't take this conversation _too_ seriously, built as it is on an anthill of incompetence. +21:43:01 (But can also be managed via I2P if the donor wants) +21:43:23 dr|z3d: i'l ping you when we move on then :) +21:43:26 But a bounty would need to be more accurately-defined than the current system allows. +21:43:46 lillith: very good, sir :) +21:44:04 s/allows/does +21:44:10 str4d_: does that imply that there will be an i2p management board to make those decisions? i think that was another week's discussion, right? +21:44:32 darrob: yes. +21:44:42 This is separate to any "official-ness". +21:45:05 str4d_: sounds good :) +21:45:32 But there would be a panel of (elected) developers (coders/designers/contributors) who are trusted with steering the I2P project. +21:45:46 I.e. something a bit more formal than what we currently have. +21:46:00 darrob: that's either coming up or later, depending on whether we want to continue +21:46:26 Mmm. My proposal works under the assumption that such a panel exists in some form. +21:47:05 (exact specifics being discussed later as above) +21:47:21 lulz +21:47:28 what's #i2p-dev then? +21:47:35 i disagree with the panel idea tbh +21:47:38 meetings seem to work well, and they let new people have a say too +21:47:38 it would need to be large enough to get a variety of perspectives +21:47:38 you never know who might offer then next amazing idea +21:48:04 lillith: exactly. +21:48:11 it's that panel, but yea... it would need to become officially official +21:48:18 But with the current size of the developer base, that's hard. +21:48:25 It's a chicken-and-egg problem. +21:48:35 And we need to break into the loop somewhere. +21:51:05 Shinobiwan: yea, thats basically what i'm trying to say :) +21:51:05 actually no it's not +21:51:05 #i2p-dev along with mailing lists, zzz.i2p, syndie, etc +21:51:05 anyone who wants a say should have a chance imho +21:52:35 lillith: yes, but there still needs to be a group of people with a final say. +21:52:53 people need to know eachother w/out knowing one another... to the point I can say, str4d, KYTV, dr|z3d ... (a lot more but just for example) have been on the network for so long, and IMO all make I2P of higher quality. Collectively I think people can figure out and reach an agreement who would go on such a panel... even though nobody really knows eachother AFK. Opinions from new people to the project should be listened to also +21:52:53 however +21:53:00 (i.e. the people who control the funds. Currently, that is a single person - eche) +21:53:25 At least to begin with. +21:53:52 The Debian developer model is a good one for making decisions like you suggest lillith - all done via voting. +21:53:55 so, everyone has a say, a few (3 or 4) people have the final say? +21:54:10 (And a "developer" is just someone who has contributed in some way IIRC) +21:54:25 But a voting system needs a larger base of "developers" first, I think. +21:54:51 lillith: anyone can suggest an idea - that's never going to change. +21:55:06 in my mind it's more than 3 or 4 people.. more like 12+ and growing... but people that fail to make the meetings don't get to vote... (and if their vote is especially important/relevant, then the meeting might happen another time) +21:55:12 But I2P has finite resources, and those resources need to be allocated appropriately. +21:56:06 (the biggest resource being time from continual developers) +21:56:20 as I wrote on zzz.i2p, I think votes such as via gpg signed messages to a mailing list would be better than irc. We've got mailing lists and they should be utilized. +21:56:20 s/biggest/most important but currently most limited/ +21:56:23 str4d_ meant: (the most important but currently most limited resource being time from continual developers) +21:56:28 KillYourTV: agreed. +21:56:43 ya gpg signed == much better +21:56:54 Provides a transparent and verifiable archive of votes. +21:57:09 is that topic 1 over then? +21:57:09 i agree also. don't expect to accomplish any serious discussion on irc. +21:57:12 * KillYourTV is 'stealing' ideas from Debian's system(s) +21:57:19 http://www.debian.org/vote/ +21:57:22 Title: Debian Voting Information (at www.debian.org) +21:57:39 it's all open source, its there to be 'stolen' :) +21:58:06 2. Managing money +21:58:10 and with mailing lists you have the oh-so-helpful 'plonk' mechanism available if needed to raise the signal to noise ratio. +21:58:21 eche|on: ping +21:58:24 KillYourTV: dont copy the "GPL Nazis" idea pls :P +21:59:46 afaict the money management wrt bounties has already been discussed enough +22:00:12 KillYourTV: if we go the mailing-list route, the mailing-list needs to be usable entirely within I2P (currently not the case). +22:00:23 (But also usable externally) +22:00:33 but there are other, non- bounty uses for money, for example purchasing ssl certificates +22:00:36 agreed +22:00:53 str4d_: the nntp interface should qualify. +22:00:53 and agreed to lillith's last point (ofc) +22:01:04 dr|z3d welt weltende welterde echelon +22:01:07 ...which i *think* is functional. +22:01:10 are they linked? +22:01:30 I know they were supposed to be but the last I checked (months ago) they weren't. +22:01:38 purchasing ssl certificates would go w/ donations IMO ... community services ... the same way to decide what the money goes towards as donations. +22:01:41 * KillYourTV fires up the nntp tunnel +22:01:41 you can at least read through it. +22:01:44 can we keep this ontopic guys, project management is coming up :) +22:02:01 i.e.. have a meeting... say "we need this"... "agree?" ... panel says OK ... majority of panel green light +22:02:32 not so quickly, but the general idea. +22:02:32 hehe +22:02:47 Shinobiwan: can fall under the same vote system proposed above. +22:03:14 yep +22:04:16 well the ML interface is accesible via i2p more or less.. http://vmfwbic2brek2ez223j6fc6bl5mmouzqvbsch45msvyyzih3iqua.b32.i2p/ still contains redirects to lists.i2p2.de.. not sure what to do about those +22:04:24 Title: lists.i2p2.de Mailing Lists (at vmfwbic2brek2ez223j6fc6bl5mmouzqvbsch45msvyyzih3iqua.b32.i2p) +22:04:32 if there is such a panel, it is not finalized at a fixed number of people... IMO... it should grow, and grow and grow... so, whatever panel currently exists, should have some procedure to bring in new panel members regularly +22:04:43 we need a central party with a politburo and the users' congress. :) +22:04:46 FTR, the mailing lists as currently set up are not available via nntp. +22:05:04 (haven't added it to the hosts.txt yet) +22:05:42 (at least not under i2p.*) +22:06:27 hmm.. they should be.. but maybe not under i2p.* +22:06:46 I didn't set it up.. so don't really know anymore ;) +22:06:58 KillYourTV: i think i2p. are welt's preexisting groups. the new ones are alt.privacy.i2p.dev/general and alt.privacy.syndie.dev/general. +22:08:42 ah...nvm me. now that I refreshed the list again I see those new ones. +22:09:00 sorry +22:09:03 ah.. right.. slrn didn't show them as they didn't contain unread messages +22:09:34 i'm still confused why there are no messages. i really thought i saw a couple of test messages before. +22:09:45 can we get back on topic please? +22:10:23 i, and surely others want to know what's going on with ssl certificates for the i2p domains +22:11:17 i didn't see the topic change, just but there are other, non- bounty uses for money, for example purchasing ssl certificates /me zips it +22:11:56 ahh, sorry +22:12:06 can we keep this ontopic guys, project management is coming up :) +22:12:23 and what's the topic? ;) (I didn't see that switch) +22:12:30 2. Managing money +22:12:41 afaict the money management wrt bounties has already been discussed enough +22:12:41 lillith: eche is currently sourcing the required money. +22:12:48 but there are other, non- bounty uses for money, for example purchasing ssl certificates +22:13:16 eche|on: any updates on the certificate situation? I haven't had to get "real "certs for a while and don't know how long the verification process takes nowadays. +22:13:19 kytv2: I am on the hunt for 3k euro and cert requests... +22:13:29 so it's under control then? +22:13:36 and pushed.. +22:14:14 yes, it's being taken care of +22:14:21 Can I reiterate my opinion that it's dangerous to have one person managing all the money? +22:14:45 ok +22:15:00 Current topic = ? +22:15:03 It's not being put in to some off-shore corporation, right? +22:15:14 2. Managing money +22:15:21 orion: no. +22:15:58 afair eche wanted to speak with an lawyer about making i2p an official entity of some kind +22:15:58 dr|z3d: ping :) +22:16:12 Currently our funds lie in a (bank?) account owned by eche|on and (mostly) in a Bitcoin wallet held by eche|on. +22:16:49 yes, that's right, in .at IIRC +22:17:07 (wrt: 'official entity') +22:18:46 at as in austria? +22:18:53 yes +22:19:19 (not australia *scnr*) +22:19:46 (running gag from EEVblog if you are curious) +22:20:26 okay, looks like we've moved on again +22:20:41 3. Making the project official +22:21:12 lillith: re: money management, it's rather dependent on both the "official" status of the project, and the project management status. +22:21:30 (The former re: where funds are kept, the latter re: how funds are spent) +22:22:14 ok, fair enough :) we can straddle points 2 and 3 for a while then :) +22:25:16 must go +22:25:19 bye +22:25:47 later I'll send yo new translaion str4d_ +22:29:26 or not, as the case may be +22:30:11 i'd suggest time to move on :) +22:30:28 Starting build #28 for job I2P-Bote +22:30:28 4. Procedure for making decisions in i2p +22:31:27 * KillYourTV votes for taking long discussions about important decisions to a mailing list +22:31:30 Project I2P-Bote build #28:SUCCESS in 1 min 3 sec: http://jenkins.killyourtv.i2p/job/I2P-Bote/28/ +22:31:34 so, mailing list, hierachy, etc +22:31:37 That way anyone can take part when he/she can +22:31:50 i'd like to put in an honourable mention for syndie here +22:31:56 +1 +22:32:03 (@ML) +22:32:04 everything is signed by default, for a start +22:33:18 I like syndie too (ofc), but mailing lists would be easier for outsiders to take part +22:33:45 but yes, i agree in principle. no point hanging around waiting for discussion that clearly isn't happening +22:33:48 that's not to say that discussions can't be mirrored to syndie... +22:34:33 yeah.. nntp syndie gateway or so would be nice to have +22:34:36 and of course, officially moving is only one thread away ;) +22:35:54 21:00 UTC isn't handy for everyone. On a mailing list time zones mean nothing. On a mailing list there no netsplits, relay problems, or ping outs. For meaningful discussions a mailing list (IMHO) is _THE_ way to go. +22:36:30 KillYourTV: I agree. +22:37:54 irc is good when you need pretty-damn-close-to-realtime...but "we need a new domain" doesn't have that kind of urgency. Post it and it'll be addressed when $user can address it. +22:37:54 imho syndie has all the benefits of mailing lists and more, the only issue is accessability for outsiders +22:38:32 then again, how many people that we want to include already use mailing lists? +22:39:03 There's been talk of a Syndie webapp" but I don't think that's gone (and will) go anywhere. +22:40:20 I'd gather that more use mailing lists than IRC. +22:40:31 i don't want to dominate a discussion on syndie vs ml here, but i think it's something woth considering +22:41:25 * weltende@freenode prefers his mail/nntp client tbh +22:42:04 syndie via mutt would = 'win' +22:43:14 this topic also includes hierachy, which was touched upon before but imo needs some expansion +22:45:09 I don't know if we can come to a consensus on anything AND have a discussion easily with IRC meetings anymore. +22:45:28 It worked in 2006 when it was more of a quick update on the project but it's not anymore and it involves lengthy debates/discussion. +22:46:40 having more time to think through things would result in on topic, well thought out, clear discussion +22:46:47 threading also = win +22:47:13 +1 +22:47:21 +1 +22:47:28 +1 +22:47:39 might I add: nntp, fuck yeah. +22:47:50 irc meetings were always an experimental thing, and the experiment failed :) +22:48:05 hey, lillith, at least we're having the discussions now, right? :) +22:49:40 imho we should keep irc meetings and move things that take a long time in the meeting or which has a lot of discussion to the ML +22:50:11 yep :) seems like no-one actually likes meetings anyway haha +22:50:15 I think it's mainly due to the timing. +22:50:18 And pressure to respond in a fast manner.. +22:50:18 postman: http://zzz.i2p/topics/1367 +22:50:18 but there's no chance of getting a time thats good for _everyone_ +22:50:18 plus some people have irregular schedules +22:50:18 Exactly. +22:50:25 Title: zzz.i2p: I2P and e-mail (at zzz.i2p) +22:50:30 with a heavy heart, and feeling rather poetic, i'd gladly baf the last meeting ;) +22:50:41 weltende: I was thinking this.. keep irc meetings for discussion of some things in the ML (actually doing something & such). W +22:50:44 go for it, lillith. +22:51:26 * lillith bafs the meeting closed +22:51:36 thank you, and goodnight :) +22:52:01 Starting build #103 for job I2P +22:52:09 can susimail handle mailing lists? +22:52:41 sure, but I'd use a 'real' client like claws or mutt +22:53:04 (just a matter or preference) +22:54:55 ahh, thats okay then :) +22:56:33 Project I2P build #103:SUCCESS in 4 min 34 sec: http://jenkins.killyourtv.i2p/job/i2p/103/ +23:01:15 Project I2P UnitTests build #74:SUCCESS in 4 min 31 sec: http://jenkins.killyourtv.i2p/job/UnitTests/74/ +23:04:51 and +1 to meetings continuing with the bigger things being taken to mailing lists/forums/syndie. +23:05:54 IRC is good for quick status updates..but a "newsletter" of sorts could work for that purpose too. +23:06:19 it's nice to have a start, with some goals, and an end, with a consensus +23:06:22 mailing list also works for alerts. see how tor do it with consensus issues. +23:06:46 'today THIS is what we decided and THIS is what we're going to do about it' +23:07:29 i'm not sure but i imagine ml discussions as dragging on with no distinct endpoint +23:07:52 +1 for newsletter though +23:08:33 they can, sure...but I think more will be accomplished on a long ML discussion than a 4-5 hour long irc meeting. +23:09:08 * lillith signs up with an open mind :) +23:09:38 * psi likes the idea of a mailing list +23:09:53 where is the ML? +23:10:01 * KillYourTV really likes MLs but they (the ones on the Internet) will probably cause his AFK identity to be leaked...heh +23:10:12 lists.i2p2.de i think +23:10:39 and (/me scrolls up) +23:10:54 http://vmfwbic2brek2ez223j6fc6bl5mmouzqvbsch45msvyyzih3iqua.b32.i2p/ +23:11:08 Title: lists.i2p2.de Mailing Lists (at vmfwbic2brek2ez223j6fc6bl5mmouzqvbsch45msvyyzih3iqua.b32.i2p) +23:11:24 it just redirects +23:11:55 there's also nntp.welterde.i2p +23:12:37 alt.privacy.i2p.*, alt.privacy.syndie.* +23:13:16 (cheers darrob for pointing me to the right usenet groups) +23:14:57 * RN wanders off to tinker with thundirbird +23:17:46 +1 to meetings continuing (but sticking to time) and +1 to "important" discussions on the ML. +23:19:32 for you interested.. posting is atm allowed for the following groups: +23:19:35 post: "i2p.*,alt.anonymous,alt.anonymous.*,alt.privacy.anon-server,alt.privacy.anon-server.*,alt.privacy.i2p.*,alt.privacy.syndie.*" +23:25:35 this will have to be fixed before "important" discussions make their way there http://lists.i2p2.de/pipermail/i2p-general/ +23:25:42 Title: The I2p-general Archives (at lists.i2p2.de) +23:26:27 ...unless the messages were purposely wiped (which wouldn't make sense) +23:30:13 hmm.. +23:30:21 no idea atm.. but heading to bed now diff --git a/i2p2www/meetings/logs/222.rst b/i2p2www/meetings/logs/222.rst new file mode 100644 index 00000000..6432b8b8 --- /dev/null +++ b/i2p2www/meetings/logs/222.rst @@ -0,0 +1,17 @@ +I2P dev meeting, April 2, 2013 @ 21:00 UTC +========================================== + +Quick recap +----------- + +* **Present:** + dg, + dr|z3d, + K1773R, + KillYourTV, + lillith, + orion, + RN, + Shinobiwan, + str4d, + weltende diff --git a/i2p2www/meetings/logs/223.log b/i2p2www/meetings/logs/223.log new file mode 100644 index 00000000..d870bf07 --- /dev/null +++ b/i2p2www/meetings/logs/223.log @@ -0,0 +1,165 @@ +19:56:52 Hi@all && (welt||welterde||weltende) +19:57:24 ;-) +20:00:33 Starting build #182 for job I2P +20:01:11 Mathiasdm, Meeh, postman, str4d, _sponge, KillYourTV, Complication +20:01:19 Alright, lets get this meeting started +20:01:33 meeting? hmm +20:01:33 Agenda: +20:01:39 * New bounty system +20:01:44 * New bounties +20:01:49 * Misc? +20:02:21 __New bounty system___ +20:03:25 During this summer I'll have some time over for I2P development, but I also have to pay my rent which is why a new bounty system or at least a new set of bounties and sub-bounties will be suggested +20:03:51 \o +20:04:37 Project I2P build #182:SUCCESS in 4 min 7 sec: http://jenkins.killyourtv.i2p/job/I2P/182/ +20:05:00 after discussing the idea with eche|on, it seems like the best option for payed work is via the bounty system +20:05:44 to make it work I'll suggest at least one large bounty and then create sub-bounties for it +20:06:27 the sub bounties will be created and closed on a bi-weekly schedule +20:06:41 (preferably by holding a meeting like this when a sub bounty is to be closed) +20:07:27 you know my opinion, and so I just wait for input ;-) +20:07:35 Currently the i2p project has a lot of funds which aren't doing us any good +20:08:10 and allowing me to contribute to some much needed problem areas in i2p should be a good thing overall +20:08:51 Does anyone have any questions or feedback at this idea? +20:09:26 I've talked to zzz, eche|on, postman and Mathiasdm earlier and they have approved +20:10:07 I've tried to reach welt/welterde/weltende, _sponge, badger and KillYourTV but have not gotten any response from them +20:10:23 Project I2P UnitTests build #153:SUCCESS in 5 min 36 sec: http://jenkins.killyourtv.i2p/job/UnitTests/153/ +20:10:35 But I'd like to know what the rest of the inhabitants of #i2p-dev think about the idea +20:10:52 I agree that we should be doing something with the funds +20:11:08 An organized method of doing so is useful, I don't disagree at all so I'm remaining mute +20:12:04 dg, does this seem like a good way of doing something useful? +20:13:00 yes. The bounty system already works, we should build upon it +20:13:19 you're proposing using existing funds? euros or BTC? +20:13:21 As far as bounty amounts go, 325€ per bi-weekly sub-bounty is what I need to cover my basic costs of living +20:13:47 euros are safer and simpler for me +20:14:07 but maybe parts could be payed in btc +20:14:42 in any case the bounty should be set in euros and then possibly payed out in btc +20:14:47 eche|on, whats our balances? +20:15:27 and to answer your question, Im proposing using existing funds +20:15:27 http://echelon.i2p/donations/index.html - still on those sums +20:15:32 Title: Donations (at echelon.i2p) +20:15:40 so ~28k€ and 626 BTC +20:16:47 hottuna: What work will you be performing? +20:17:22 appx. how many hours a week are you proposing to work? +20:17:35 that is point two on the agenda, but i'm primarily thinking about improving on our floodfill issues +20:17:57 40 h/week. So full time. +20:18:56 so round numbers, 8 euros/hour +20:19:18 nope. 4 euros/hour +20:19:20 in my mind that sounds reasonable/cheap +20:19:35 325/80 +20:20:13 mcdonalds isn't hiring? :) +20:20:35 i think burger king has payed me more an hour :P +20:21:06 you worked for a burger king? hell,... I should have visited your working office^^ +20:21:35 appx. how many weeks you propose to work? +20:21:56 lets see.. this will be a rough number +20:23:19 I should manage at least 8, but it could be more or less than that +20:24:10 so a 1300 euro commitment from us +20:24:24 yeah +20:24:49 more than that would have to be discussed in a meeting +20:25:18 anybody remember what we paid jrandom monthly? +20:26:08 let's see what the internet archive says +20:26:10 less. ~500$ IMHO +20:26:39 he was more of a hippie than tuna is :) +20:26:50 $465 USD/month +20:27:11 I'm hippying as hard as I can damnit! +20:27:52 hippy harder!! +20:28:49 alright, so does anyone have any objections or questions? +20:29:15 no objection +20:29:41 sounds good +20:30:25 ditto +20:30:54 Alright. Then we are all happy about this +20:31:32 For the record: As no complaints have been raised, we'll proceed with the new bounty system. +20:31:47 __New bounties__ +20:32:34 The floodfill system has some issues, including attack resistance and scalability. +20:33:02 Replacing it is the first bounty that I will suggest. +20:33:30 I've talked to zzz about some alternatives +20:33:47 and step one appears to be to move to a kademlia based netdb +20:34:30 zzz has in fact already started by implementing kademlia in i2psnark +20:34:59 this is probably a good base for for a netdb network +20:35:53 there are some modifications that can be made to kad to make it more probabilistic and avoid the worst aspects of eclipse and sybil attacks. +20:36:01 I'm not sure "replace" is the right word. And also not sure it's the top of my list. Our ff system is actually in pretty good shape right now. But I'm not sure how much you want to get into discussing it now. +20:36:27 A reasonable sub-bounty may be just to analyze the current situation and make proposals +20:36:41 replace would be a long term goal, initially adding a second netdb backend would be the goal +20:36:58 yeah, replace is the wrong word. +20:37:09 but sure, the UCSD folks highlighted some issues. +20:37:35 ignoring vulnerabilities for a moment, I think we're actually good for a couple years of growth w/o changes +20:38:06 22:37 < zzz> A reasonable sub-bounty may be just to analyze the current situation and make proposals <-- sounds like a good idea if it's time-boxed +20:38:53 spending two weeks on an analysis might be overkill, but having a meeting and discussing the alternatives after a week might be good +20:38:55 what's _not_ realistic is replacing ffs with R5N this summer. +20:39:09 zzz, agreed +20:41:24 there might also be a need for some work surrounding development like multirouter support +20:41:24 which would make development easier +20:41:24 fyi for everybody, the netdb roadmap in my head is 1) encrypted lookup responses and 2) migrate the snark kad back to router +20:41:24 like the ideas +20:41:35 ./roadmap +20:41:49 yeah +20:44:21 I don't think that 2 full weeks are needed for this +20:44:27 yea +20:45:21 "alternative exploration"? +20:45:30 as in the exploration tunnels right or? +20:45:30 depends how long before your head explodes +20:45:37 what else on your list? +20:45:45 "alternative exploration" = {what technology?, if dht-which?, what code-base?} +20:46:03 maybe one week, and if I have time to spare I'll start with the multirouter stuff. +20:47:09 I'm not sure, but some of the bounties like ipv6 will have to be completed soon as ipv6 looks to be actually deployed now +20:47:40 zzz is working on ipv6 a load but he my appreciate help +20:48:12 I try to add IPv6 on my root server for I2P use. +20:48:15 Resolving issues regarging an openitp submission has been suggested by zzz +20:48:22 as soon as I find time to understand and get it up... +20:48:57 I have a dev server that I can let developers into for testing.. It have multiple ipv6 adresses +20:49:00 having us accepted into OpenITP would be a major thing for us +20:49:07 Could setup more of them now for testing +20:49:22 and now gone for a good night time... +20:49:25 here's my list: IPv6 (incl. testing), Crypto (see trac wiki), OpenITP prep (see trac wiki), NTCP and SSU protocol obfuscation (old zzz.i2p post, Lance James might be able to help), other state firewall resistance, Symmetric NATs (ticket #873), ... +20:49:32 http://trac.i2p2.i2p/ticket/873 - (accepted defect) - Port changing .. obscurely +20:49:40 zzz: want access to a ipv6 server for testing? +20:49:51 hottuna: major thing, yes, but, in case you (or others) are not aware: OpenITP are not long term funders. They fund short, achievable goals to improve projects "quickly". +20:51:05 Meeh yes, in a couple weeks. I'd like to see the minor fix in 0.9.5 to ignore published IPv6 addresses get out there before we start publishing them +20:51:24 s/0.9.5/0.9.6/ +20:51:24 crypto is another thing that I know a bit about, so my time might be well spent there +20:51:27 zzz meant: Meeh yes, in a couple weeks. I'd like to see the minor fix in 0.9.6 to ignore published IPv6 addresses get out there before we start publishing them +20:51:48 ok :) I can setup multiple too if needed +20:51:51 maybe if we're lucky I'll be somewhat done with the floodfill system by the time zzz is done with ipv6 +20:51:58 got a /48 net +20:52:14 that way we could both attack the crypto problem +20:52:21 heck what about i2pcpp +20:52:37 orion is 404 atm +20:52:48 sindu might help there when he got time, great C coder +20:52:59 talked about it earlier, know him from RL +20:53:26 that sounds interesting +20:53:49 if orion is at least willing to accept help, that's a big step - he wasn't before - +20:53:52 but I think that I should spend time where makes the most difference which in my mind is floodfills/ipv6 and crypto +20:54:11 *it +20:54:14 sure, my list doesn't necessarily match your skills or interest +20:54:29 also, he should get some creds for spreading the i2p stickers around Oslo, Norway. He have placed it all around the city +20:54:44 hottuna: if you want, send more.. soon emtpy again:P +20:55:11 oh yeah, hottuna if you aren't coming to DEFCON I need some too +20:55:30 im planning on coming to defcon +20:55:44 i havent bought any plane tickets yet, but I will soon. +20:55:47 oh hella yes. +20:56:23 hottuna: if you got files, I might be able to get some free printups myself +20:56:43 the files are in the i2p.graphics branch +20:56:46 if you got the sticker in png/ai/whatever format +20:56:49 ok thanks +20:57:00 if im remembering correctly +20:57:16 alright. +20:57:51 Is everyone ok with the first bounty being for the floodfill system? +20:58:02 aye +20:58:25 yepp +20:58:50 ok, so first 1 week of research into the options, followed by implementation (currently most likely kademlia)? sounds good +20:59:06 yes, that's the idea +21:01:56 ok +21:03:15 For the record: The first bounty to be introduced is adding a new netdb backend. The first sub bounty should be divided into alternative exploration, multirouter research and discussion with you guys +21:03:26 __Misc__ +21:04:38 How is the website deployment going? +21:09:27 Everyone died? +21:09:31 str4d? +21:12:57 oh +21:13:04 I was curious :) +21:14:22 did I miss anything exciting? +21:14:29 only this: +21:14:32 23:10 -!- hottuna [hottuna@irc2p] has quit [Quit: leaving] +21:14:32 23:12 <+Mathiasdm> oh +21:14:35 23:13 <+Mathiasdm> I was curious :) +21:15:12 Alright, if no one knows, let's see next week +21:15:38 * hottuna baf's with the meeting ending hammer +21:19:59 * Mathiasdm lurks onward :) diff --git a/i2p2www/meetings/logs/223.rst b/i2p2www/meetings/logs/223.rst new file mode 100644 index 00000000..20fcb43f --- /dev/null +++ b/i2p2www/meetings/logs/223.rst @@ -0,0 +1,13 @@ +I2P dev meeting, May 21, 2013 @ 20:00 UTC +========================================= + +Quick recap +----------- + +* **Present:** + dg, + eche|on, + hottuna, + Mathiasdm, + Meeh, + zzz diff --git a/i2p2www/meetings/logs/224.log b/i2p2www/meetings/logs/224.log new file mode 100644 index 00000000..314f624d --- /dev/null +++ b/i2p2www/meetings/logs/224.log @@ -0,0 +1,489 @@ +19:52:28 zzz, christoph2: syn +19:54:26 yay, dev beating! +19:54:33 s/beating/meeting/ +19:54:37 topiltzin meant: yay, dev meeting! +20:00:03 * hottuna baf's the meeting opened +20:00:07 Agenda: +20:00:14 * The next NetDB backend +20:00:14 * Ticket #729 - properties location on osx +20:00:14 * Ticket #741 - process renamer on windows +20:00:14 * Misc? +20:00:22 http://trac.i2p2.i2p/ticket/729 - (assigned enhancement) - on OSX ~/.i2p -> ~/Library/Application Support/i2p +20:00:33 http://trac.i2p2.i2p/ticket/741 - (accepted enhancement) - Make I2P easier to deal with with Windows firewall software +20:00:45 __ The next NetDB backend__ +20:01:16 I've been working on a proposal, the first RFC is ready +20:01:35 http://trac.i2p2.de/wiki/NetDB/NextBackend +20:01:38 Title: NetDB/NextBackend – I2P (at trac.i2p2.de) +20:02:14 The general idea is to use a Kademlia base and extend it with features that improve performance and/or reliability. +20:02:59 Some of the initial code for Kademlia has already been written by zzz +20:03:34 In fact a full BEP5 implementation. BEP5 is the mainline bittorrent implementation of Kademlia. +20:04:13 Several DHTs have been considered: Chord, Freenet and Pastry. +20:04:47 However Kad is fast, extendible and relatively reliable. +20:05:05 some other Kad derivatives that are used in production: Azureus kad, eMule kad, Mojito Kad (Limewire) +20:05:24 Overnet (eDonkey, now defunct) +20:05:47 no p2p app uses chord or pastry (to my knowledge) +20:05:54 I've had a look through the Az-Kad and it's not very compatible. Mojito might be interesting +20:05:57 On top of Kad a few changes have been proposed. +20:06:05 Recursive tunnels for faster lookups. +20:06:20 And Random Recursive lookups for more reliable lookups. +20:07:13 Insertions will be standard Kad until Random Recursive Stores are implemented. +20:07:45 Alright, so that is the overview. Does anyone have any questions? +20:08:17 One objection to recursive tunnels is that it renders local ip banlists useless +20:08:40 for example, I could have manually added the ips of a hostile party to my ban list +20:09:18 the nodes that participate in the recursive lookup/store will not know that +20:09:37 That is true. +20:10:00 Recursive queries are somewhat frail, and should only be used for speed. +20:10:35 Random Recursive queries will however, eventually find a path which doesnt involve the banned nodes. +20:11:05 For what kind of situations would you not trust the ban-list of another node? +20:11:25 sponge: want udp +20:11:28 eche|on: count is not persistent after network changes ("soft restart") +20:11:51 for the situation where the operator of that node hasn't been diligent in updating the banlist +20:12:02 or for the situation where the other node has no banlist at all +20:12:29 But what would happen if the query passed through a 'banned' node? +20:12:51 Either it is forwarded, dropped or recorded. +20:13:31 iterative never passes thru anybody +20:13:34 whatever the sybil/eclipse attack does - probably droped? +20:14:38 That is the thing about Recursive. It's ok if it fails. We have more reliable methods for keys that are under attack. +20:15:09 Like Iterative or Random Recursive +20:15:24 how to select a mode? +20:15:35 theoretically you could include a small bloom filter of banned ips to the query +20:15:54 mode selection an open question. +20:15:57 is an* +20:16:28 In my mind a parallel version would be interesting +20:16:39 A sequential failover version would be slow +20:17:03 But it is a bandwidth vs. max_latency tradeof +20:17:51 topiltzin: R5N includes a bloomfilter in queries. But I don't think the really is needed. +20:18:14 We build this thing to work even if failures are encountered +20:18:14 how much slower is the iterative lookup, and is that slowness a bottleneck of any kind? Do we really need to be optimizing that? +20:18:45 I think we gotta start with adding stat code (where necessary) to netdb and snark and gathering stats on current performance of those two impls +20:18:52 When you visit an eepsite, a lookup has to be done. +20:19:25 topiltzin: the speed of lookups can be seen under the 'Lookup' part of http://trac.i2p2.de/wiki/NetDB/NextBackend +20:19:28 Title: NetDB/NextBackend – I2P (at trac.i2p2.de) +20:20:16 netdb has lots of stats, if we add stats to equivalent places in snark we can start to put a picture together +20:20:35 query latencies etc? +20:21:06 zzz: +1 on moar stats +20:21:06 latencies, queries-per-success, etc, yes +20:22:26 Having access to those stats would be interesting. Especially when developing something new. However comparing I2PSnark-DHT to FloodFill is comparing apples to oranges. +20:22:29 as I said the other day, I think the snark code could be moved back to netdb but only if we choose K and B to swallow the whole local netdb into the routing table +20:22:57 if the routing table is missing most of the local netdb we may as well just keep sorting +20:23:55 your proposal (and yes it's been my plan for a couple years as well) is to replace the orange with the apple, so it's kindof important to compare them. +20:23:58 Im am not against setting a high B, lookup latency is a real issue +20:24:55 regarding K I think keeping it at 8 may be reasonable. +20:25:18 of course the new dht would have to be evaluated. +20:26:05 you can't pick K in isolation. You have to pick K and B to make the routing table work as well as sorting does now, for a given local netdb size. +20:27:03 Both can be tweaked while deploying. +20:27:29 So I'd go for an initial guesstimation base on what we know and what we need. +20:28:17 also depends greatly on whether it's the ffs or everybody that's in the new dht +20:29:24 Not making every node a participant in the new dht would be a mistake an keep us vulnerable to attacks like that presented in the UCSB paper +20:30:15 I don't see info on who's in or out in your proposal +20:30:18 I suppose I wasn't very clear about that in the proposal. +20:30:25 ;) +20:31:30 not at all sure you want everybody (natted, android, hidden, chinese, mobile phones, etc) in it +20:31:46 check out jr's extensive comments on where it all went bad +20:31:53 node churn is not good for the dht. You should have some minimal uptime requirements +20:32:32 topiltzin: node churn isnt much of an issue since all our data is mutable and republished every 37 seconds - 30 minutes +20:33:09 nat:ed nodes should probably not participate. android probably should +20:33:17 sure, N=500 and B=-8 was the disaster he never figured out, but there were other causes too, that are still present in our network... and could get much much worse if android takes off +20:33:25 chinese.. i don't know.. +20:34:04 other than likely having higher churn, how is android different? +20:34:32 node churn affects routing negatively.. so if the goal of this effort is to improve routing you cannot ignore it +20:34:39 I mean phones, not android in particular +20:34:58 android==phnoes for me aswell +20:35:22 mobile devices have lower bandwidth and horsepower and intermittent connectivity +20:35:57 How is it done now? +20:36:12 what? +20:36:39 regarding android devices that want to be an ff? +20:36:42 christoph2: is lurking somewhere +20:36:49 * christoph2 hides +20:37:00 there are some criteria for becoming an FF, one of them is uptime +20:37:11 how would fast key-rotation interfere with an eclipse attack? +20:37:57 and how long does it take for a node to integrate into the netdb of the other nodes? (ie pollute their routing tables) +20:38:32 androids become ff automatically like anybody else, if they meet the criteria. But seems unlikely anybody would do that over the air +20:38:38 well you have time T it takes to integrate a node into I2P (untill it's reasonably well connected) and time t the rotation. you need T/t + safety nodes for eclipse +20:38:53 topiltzin: uptime is really not much of an issue. R5N has some pretty aggressive replication factors. So churn is not an issue +20:39:00 * nodes needed to actually eclipse +20:40:27 hottuna: not exactly following code changes. was less than 30 minutes in december +20:40:27 I did some quick calculations yesterday +20:40:27 well 0.9.2 iirc +20:40:27 nodes_needed_for_eclipse = (60/key_rot_interval)*eclipse_integration_time*attackers_per_eclipse +20:40:27 nodes_needed_for_eclipse = (60/10)*24*20 = 2880. Which might be prohibitive for an attacker. +20:40:27 hottuna, how would a new keyspace (either a different permutation formula, different rotation schedule, or both) work? I don't see how we could ever migrate over. +20:40:27 ok, that sounds reasonable +20:40:49 We'd use both in parallel? the current implementation will remain separate until we can safely move away from it. +20:41:26 what I really want to know is what can we do in the next two weeks to improve resistance +20:41:29 christoph2: are those calculations sensible? and would 2880 nodes be an issue at all? +20:41:36 if that's making the class N routers ff, lets do that. +20:41:36 I find it very hard to believe that node churn isn't an issue. The bigger the churn, the worse the routing table of each individual node +20:42:29 how could we ever 'move safely away' and maintain compatibility? How could we handle the conn limit issues of two parallel impls? How would we migrate from one to the other? +20:42:33 topiltzin: the value K, which is the size of each bucket in the routing table is chosen to be a number of nodes that are highly unlikely to drop out of the dht in an hour. +20:42:33 ^^ class F but !windoze +20:43:04 s/F/N/ +20:43:08 topiltzin meant: ^^ class N but !windoze +20:43:12 sure, we could do class N non-windows. No idea how many there are +20:43:35 it would also expose those routers as being non-windows, small anon issue +20:43:35 hottuna: you get ~20 on a moderately expensive server. 100 of these may or may not be a problem depending on whom you defend against. and I'm not sure if you couldn't get several times more nodes per server with proper code +20:44:22 alright, so it could be a bit of an issue. However it won't be for long the way technology tends to evolve +20:45:28 what else could we do for 0.9.7? +20:45:28 true re: anon issue.. so maybe just do all N and hope we don't piss users off too mch +20:46:18 didn't read everything. what was the issue with windows? +20:46:25 re connections: old nodes would carry on as usual. new nodes would balance their queries amongst both nets. +20:46:49 christoph2: baked in connection limits +20:46:52 christoph2: windows doesnt allow for a large number of connections +20:47:07 ah ok +20:47:27 christoph2: alright, so that answers the key rotation issue. it is probably not worthwhile +20:47:34 actually it's the rate at which new connections are opened that's limited +20:49:07 hottuna, I don't see how we get from here to there. I can see how to move the snark code to netdb with the same iterative lookups in the same keyspace. I don't know whether its worth it, but at least I can see how. After that it all seems really hard and mysterious. +20:50:02 We would change the key-space? Or what are you referring to as keyspace? +20:50:05 +1 with starting with snark code and figuring other stuff $later +20:50:40 keyspace = key->routing key algo, including rotation +20:52:14 so step one while deploying is having something that works (likely iterative only). then we add new KRPC messages for Recursive and Random Recursive +20:52:54 And when the net has upgraded to mostly support them we can enable them in the originator nodes. +20:53:27 deploying will even help us figure out performance while under massive attack +20:53:38 (for background, I started with the netdb kbucket code to make a generic library in i2p.zzz.kademlia, with arbitrary K, B, hash size, and eviction algo. Then I unit tested it to death. Then I moved it to snark for BEP 5 and more testing. The last part of the original plan is to move it back to netdb to complete the circle) +20:54:54 zzz.kad && i2psnark seems like a good base. I've been reading some of the code today, and it makes a lot of sense to me. +20:55:01 you're proposing different keyspace, different rotation, and different participants. i.e. a completely new overlay. +20:55:33 I'd like to do a completely new overlay. +20:56:04 oh good. code reading++. +20:56:47 alright. If this makes sense and no one has any objections I'd like to move this meeting along. +20:57:42 __Ticket #729 - properties location on osx__ +20:57:49 topiltzin, Meeh +20:58:11 yep, that's some very low-hanging fruit that's been dangling around +20:58:39 new overlay sounds like misery to me. +21:00:12 ... awkward moment ... +21:00:59 we still on dht? +21:02:09 imho discussion on dht isn't over but for the benefit of the meeting it should be +21:02:23 no decisions seem clear +21:02:26 * dg returns to shadows +21:03:16 I think the decision for the immediate future 0.9.7 is moar FFs .. the long-term view is still foggy +21:03:42 I'm gonna go ahead with #729 . Meeh, you around bro? +21:04:16 sry, I forgot about meeting +21:04:57 alright topiltzin, what's up with #729? +21:05:35 So, I've been running it for a while now, propagating trunk to branch i2p.i2p.729 +21:05:50 works fine, straight-forward +21:06:21 affects only new installs on OSX, so low impact, etc. +21:06:44 I'd like to merge it and get it over with +21:07:03 zzz, up for the #729 merge? +21:07:45 I don't have mac access, but Im assuming that topiltzin and Meeh does. +21:08:12 Yeah, we're probably the only osx users around here :) +21:08:15 here's a diff: +21:08:15 mtn diff -r h:i2p.i2p -r h:i2p.i2p.729 +21:09:14 I don't have repo access on this machine :/ +21:09:41 "access"? +21:10:00 as in set up :P +21:10:07 no objections +21:10:38 pastebin coming for those who care +21:10:50 just needs some testing, but probably wont get more unless its merged +21:10:50 thanks! +21:11:35 I lobbied for merging months ago as you will see in #729 comments +21:11:42 http://pastethis.i2p/show/3404/ +21:11:45 Title: Paste #3404 | LodgeIt! (at pastethis.i2p) +21:12:01 let's go ahead with the merge then +21:12:17 ok great. Meeh, speak now or forever hold your peace +21:12:28 (or whatever it is the priest says at the wedding) +21:13:18 I'd like him to speak later too if that's when he tests it :) +21:13:21 ok, I'll merge after the meeting +21:13:56 __Ticket #741 - process renamer on windows__ +21:14:11 str4d: you around for this? +21:15:54 mmk, this ticket is not so small +21:16:57 background - on windows, i2p runs with a process name of "java" +21:16:57 hi +21:17:24 meeting today? +21:17:27 which means any security settings that are applied to i2p become valid for any and every java application +21:17:41 sponge: yes. http://zzz.i2p/topics/1397?page=1#p6616 +21:17:48 Title: zzz.i2p: Meeting [4th June] (at zzz.i2p) +21:17:48 ty +21:17:59 bout time I made one of these... +21:18:48 this day is always difficult for me to do anything at this particular hour +21:18:55 can we do anything on 741 w/o str4d ? +21:19:29 I finally have a machine with windows on it +21:19:36 if we have a copy of visual studio then we can do everything without him +21:19:59 7 iirc, never use it though, so i can help/test +21:20:14 I could get a VS license from microsoft, if anyone knows how to use it.. +21:20:41 it's a good idea for the project to have such license +21:20:41 I mean as far as discussion. So back to the beginning, topiltzin you put this on the agenda why? just to try to get things moving? +21:20:41 vs is pretty painful from what I have heard +21:21:07 exactly - get some action going +21:21:37 Alright, str4d isn't around. Should we table this? +21:21:48 aye +21:22:28 * sponge has some 'misc' for discussion +21:22:41 let me know when I got the talking stick +21:23:03 Ill take that as a resounding yes. +21:23:03 Moving along.. +21:23:06 __Misc__ +21:23:09 if you guys want to table it fine, but let's not forget about it competely +21:23:21 topiltzin: agreed +21:23:46 (I will bring it up next meeting too) +21:23:57 ;-) +21:24:08 sponge: Misc was it? +21:24:51 MISC-- Bridge API for UDP (BOB) -- I have a few ideas on how it could be done, but I need some feedback, and need to know if it is even wanted +21:25:18 basically we need some sort of standard that is expandable +21:25:22 and to stick with it +21:25:43 it also has to be able to not mess with what is out there already +21:25:57 well-- adapt easily +21:26:56 So the question is what people would use it for? +21:27:03 we already have a thread going at http://zzz.i2p/topics/1393 --- how about putting your proposal there? +21:27:10 Title: zzz.i2p: UDP Trackers (at zzz.i2p) +21:27:10 two ways I am thinking of is either wrap a UDP packet with <> or <> +21:28:13 hottuna: trackers, voip? +21:28:16 I'm curious on demand +21:28:16 dare i say it, games +21:29:03 and I need people to discuss this. I have been trying for YEARS to talk with someine, to get more ideas, and nobody wants to think on the problem +21:29:03 oh, anonet. psi was pushing for that. +21:29:03 *someone +21:29:03 gotta read up on how SOCKS does it too +21:29:03 there are apps out there that do use IDP +21:29:06 *UDP +21:29:22 don't forget gnutella +21:29:25 voip (mumble) has been implemented and seen some use +21:29:44 that's tcp +21:29:47 bote uses a udp-ish packet too +21:29:54 gnutella can use udp +21:29:58 zzz: My bad +21:30:29 When is the next meeting? +21:30:40 Whenever someone wants to hold one +21:30:40 it's all easy inside the JVM. I could add udp to zzzot in a day. It's the external i/f that is a pita. +21:30:40 so is there demand? and if you got implementation ideas that can expand and not go stale, post +21:30:45 Oh crap. We're in a meeting. +21:30:45 I won't host one next week. +21:31:06 orion: we're at __Misc__ now.. +21:31:25 sponge: yes. +21:31:32 number 2 misc--- ipv6 and it's implications on de-anoning +21:31:35 hottuna: Thank you. +21:31:50 concerns? +21:32:01 haw close are we to using ipv6 +21:32:08 how +21:32:12 what concerns are you having sponge? +21:32:27 ipv6 can link to who you are very easily +21:32:46 damn, overslept the meeting -.- +21:32:53 IPv6 thread: http://zzz.i2p/topics/109 +21:32:56 since the address space is larger? +21:32:59 Title: zzz.i2p: IPV6 TODO (at zzz.i2p) +21:33:03 yes +21:33:03 I was thinking +21:33:14 zzz: this is different, but related +21:33:17 ipv6 does not deanonymize? WHOIS _may_ be more accurate as _may_ be determining if a NAT is in place (Bob and Ryan are behind a NAT, you do not know which is which) -- with IPv6, you can perhaps know if it is Bob or Ryan. +21:33:24 IMO, it makes no practical difference to I2P. +21:33:27 i2p could get an ipv6 space +21:33:39 socks 5 udp would be awesome +21:33:42 farm that out to users via tunnel +21:33:45 o/ +21:33:48 Side note: i2pcpp will have full ipv6 support. +21:33:54 Apologies for being late. +21:33:57 dg: I agree. +21:34:06 awaiting sponge to list his concerns (post #66) +21:34:20 hottuna: Can we move on if sponge has nothing to add? +21:34:35 i feel it's a non issue +21:34:35 schedule? merge for 0.9.8, enable by default in 0.9.9 +21:34:38 so in short.... will i2p provide an ipv6 tunnel for persons of high concern? +21:34:53 hey str4d, you missed the i2p.exe discussion :( +21:35:04 should wee? +21:35:07 I don't think our threat model includes I2P being illegal to run. +21:35:31 If that was the case ipv4 would be problematic as well. +21:35:42 orion, I'm trying to keep our docs up to date w.r.t IPv6. The docs should match what's in my ipv6 branch now. +21:35:45 ht: in some countries (china?) it is +21:36:20 And who runs i2p is the only additional information that would be leaked. +21:36:39 the best way thru the GFW may be via IPv6, hard to see how it's a negative +21:38:09 last misc from me--- So sorry I have been missing all the previous meetings. Again, difficult for me to do this day of the week, and hour. I will be more active very soon on everything as well... the talking stick is for the next persion... +21:38:13 zzz: Thank you. +21:39:03 Meeh: you missed #726, but are requested to do some testing of the patches that will be merged by topiltzin (i think that is the summary) +21:39:15 str4d: #741 was tabled for next meeting +21:39:22 sponge: nice :) +21:39:29 I say bring up 741 now +21:39:32 Okay, anything else? +21:39:32 hottuna: noted. +21:39:39 he's here, why not +21:39:46 fine by me +21:39:46 hottuna: Yes, minor thing. +21:40:01 ok, go orion! +21:40:04 de-tablizing 741 ... :) +21:40:20 I was wondering if someone could get me my credentials for the press@i2p2.de email account. +21:40:27 As well as update the website. +21:40:46 orion: website is in mtn +21:40:56 update what part of the website? +21:41:03 And no credentials required to update website. +21:41:18 (Just create a mtn key and go) +21:41:25 str4d: email account +21:41:43 welterde handles that domain as far as I know. +21:41:46 Or, nevermind. The team.html page has already been updated. +21:41:46 you'll be sorely disappointed, as I don't think we've ever gotten a single email there, but welterde is the person to ask to get added. It's just a redirector to a list, there's no account. +21:42:02 So right now it's just the email account. +21:42:20 I Will speak to welterde, thank you. I yield my time. +21:42:30 excellent +21:42:38 __Ticket #741 - process renamer on windows__ +21:42:45 Okay, so briefly de-tablizing 741? +21:42:45 topiltzin, str4d +21:42:52 yes +21:42:58 :-) +21:43:05 Current situation: the process renamer works. +21:43:12 (When called by the Tanuki wrapper) +21:43:23 (or passed CLI arguments) +21:44:01 I've tested it on Win7. topiltzin has verified that the code has been run on pretty much everything except Win8. +21:44:12 So it needs testing there. +21:44:34 Does anyone have win8 access? +21:44:37 32/64? +21:44:52 * KillYourTV can +21:44:59 The one part that is not working currently is the internal defaults - the arguments that are used if no arguments are provided externally (i.e. wrapper or CLI). +21:45:02 (win 8, x64 and/or x86) +21:45:09 My daughter was going to upgrade to 8, but we found out it is really bad. +21:45:12 zzz: I was running 64-bit Win7 +21:45:30 (IIRC) +21:45:30 so KillYourTV, you're up for some testing? +21:45:37 always +21:45:44 :) +21:45:52 Thanks KillYourTV :) +21:46:11 two remaining points I can see: +21:46:11 * KillYourTV will set up some VMs +21:46:14 Testing just requires dropping the new i2p.exe into the install folder, and tweaking wrapper.config to use "i2p" instead of "java". +21:46:21 1. Icons - need them in different sizes, alpha channels, b.s. +21:46:36 2. Strings like license, description, etc. need reviewing +21:46:55 1. - I've set the VS file to refer to the icon in the installer/ dir in i2p.i2p. +21:47:22 So it should be using the same icon as the launch4j-based i2p.exe uses. +21:47:25 I've not noticed but is the proposed "renamer" already in i2p.i2p? +21:47:36 2. - Agreed. +21:47:36 re Icons: i don't think that any high quality/svg files exist +21:47:51 KillYourTV: yes - installer/c/i2pExe +21:48:10 if it doesnt work w/o arguments, isnt that a problem? +21:48:10 cheers, I can handle the rest then ^^ +21:48:28 zzz: yes it is. +21:48:35 then some things like control panel are going to look weird +21:48:43 That needs to be fixed if it is going to replace the launch4j-based i2p.exe +21:48:54 str4d: are you sure it's a problem? I thought you hardcoded some defaults +21:49:17 topiltzin: I did, but it just crashes and I couldn't work out why at the time. +21:49:29 hardcodeing can be a bad thing, Do a path search first. +21:49:47 But when I pulled out (what should have been) the exact same arguments and used them via the CLI, it worked fine.. +21:50:02 sponge: different defaults. +21:50:13 ahh +21:50:35 sponge: these are the settings that I2P is run with if nothing else is there (no wrapper.config). See installer/i2pstandalone.xml +21:50:38 str4d: in order KillYourTV to test you need to build the actual i2p.exe or have you commited that in mtn? +21:50:46 (and the doBuildExe target in build.xml) +21:50:49 str4d: you may have to do like I did for BOB, basically a double main() +21:50:53 topiltzin: it's in mtn +21:51:07 * KillYourTV already asked ^^ +21:51:14 topiltzin: needs to be built - I wasn't going to commit the binary until we were close to actually using i. +21:51:21 KillYourTV: I meant that the source is in mtn ^_^ +21:51:24 the first main inserts missing args, passes it to the actual main() +21:51:31 oh...heh +21:51:58 sponge: that's pretty much what is done - if args are passed they are used, otherwise default args are constructed. +21:52:05 so you got main() and _main() +21:52:08 ok so the i2p.exe is not in mtn? +21:52:08 topiltzin: what is the format of launch.properties? +21:52:27 topiltzin: correct. Just installer/c/i2pExe/i2p.c etc. +21:52:30 the first is just a cleanup +21:52:37 sponge: see installer/c/i2pExe/i2p.c for the code. +21:52:37 topiltzin: src yes, binary no +21:52:48 will look, thanks +21:53:11 I'll get back to you on why it is broken +21:53:27 topiltzin: there were also several commented-out methods that I couldn't work out their purpose. +21:54:04 that's fine, I can explain offline +21:54:15 but KillYourTV needs a binary to test, can you build one? +21:54:54 topiltzin: sure. +21:55:21 launch.properties - I believe one line per property, need to double-check +21:55:39 (unless you already have VS2008 KillYourTV - that's what it is built with) +21:56:05 which brings up another interesting __misc__ point: +21:56:08 topiltzin: I'm thinking that launch.properties could be like wrapper.config but for the standalone case. +21:56:23 yeah +21:56:42 (Because the current standalone i2p.exe is not adjustable at all) +21:58:33 now that the project is loaded with cash (because some mysterious person donated 1000 BTC when they were still cheap) we should have some software licenses for things like vmware, visual studio, etc. +21:59:21 visual studio I can get for free or one of you guys +21:59:24 I'm sure that KillYourTV has legally purchased his copies of Windows 8 :-D but technically it's the project that should be funding that +21:59:39 microsoft is advertising $450 win8 computers on tv (Asus? Acer?), we could just buy one of those +22:00:05 excellent idea zzz +22:00:16 (dreamspark copies, "for educational use") +22:00:27 tiger direct often has deals for 300-400 on low end laptops +22:00:27 If Microsoft offers student discounts, I can get them. +22:00:34 If you want to go that route. +22:00:37 hottuna yes please (re VS) +22:00:51 wait +22:01:01 is the gamer laptop we bought win. 8? +22:01:19 do we really need toys? couldnt the testing be done on a vm? +22:01:27 echelon had his own windows. +22:01:45 and I do my testing in clean VMs +22:01:52 str4d: I have vs around some place (it is very old) but I won't be using that. I'll simply review your code once pull and apply is finished here and advise you +22:02:14 sponge: thanks. +22:02:59 a vm is always better +22:02:59 I agree with hottuna regarding the VM. +22:02:59 and we can pass around images for easier debugging etc. +22:02:59 alright. so are we happy with this topic/discussion? +22:02:59 str4d: no problem. I've head my head buried in C, C++ and ASM for the last month +22:03:02 a win8 netbook would be a hella lot cheaper than VS +22:03:52 zzz: What if I got a student copy of VS? +22:04:03 I was thinking of donating my student copy as well. +22:04:14 orion: if you get a student copy i2p cannot technically use it +22:04:21 My daughter could possibly get a student version too +22:04:27 s/technically/legally/ +22:04:31 topiltzin meant: orion: if you get a student copy i2p cannot legally use it +22:04:31 topiltzin: why not? +22:04:34 hottuna: yes over here. Two main action items: Fix the defaults (and provide a launch.properties); build an i2p.exe for KillYourTV to test. +22:04:37 It's for my education. +22:05:07 and not for a for-profit company/project +22:05:07 beause it is a student copy for orion's education - it means only he can use it +22:05:26 ok. in that case I cant provide VS. +22:05:49 what license does yours have? +22:05:58 and this stuff cant be built by mingw? +22:05:58 topiltzin: student +22:06:46 you can use it to build i2p.exe or other stuff for i2p, the only thing you can't do is give it to someone else +22:07:23 what about vs2008 express? Is that limited to 32bit only? +22:07:46 str4d: note! It is not good style to mix C++ comments in C code ;-) use /* */ +22:08:01 I suppose we need i2p.exe 64bit _and_ i2p.exe 32bit +22:08:32 I *think* 32-bit only is good enough +22:08:35 I also already see your problem +22:09:01 good enough = runs on both 64 and 32 bit windows +22:09:19 I'm not sure a 32bit i2p.exe can load the 64bit wrapper. The 32bit wrapper can't load the 64bit jvm +22:09:36 dunno though about this +22:10:48 str4d: i2p.c line 54, and the loop below -- you are not assiginging correctly... it should be '*new_argv[0]' not 'new_argv[0]' same for the loop below that. The final NULL should be OK +22:11:06 KillYourTV: how about a x86 which starts the x86 or x64 launcher? +22:11:44 str4d: Try that, and it should work for you +22:11:47 that's what I'm saying, I don't know if it can work. 32bit binaries _usually_ cannot call x64 binaries. +22:12:47 actually the first line may be OK, but the loop does need to be a * +22:13:26 read_options, if returning as a pointer, needs to copy the pointer +22:13:45 KillYourTV: trough cmd.exe it should work as last resort, tough thats a win problem +22:13:48 new_argv[i] = &(read_options[i-1]); +22:13:51 like so +22:14:57 sponge do you have access to a windows box? Can you help test this? +22:15:17 sponge: also post any comments on trac #741 +22:15:35 I have a win 7 laptop, but can't test today. I'm short on time, and had to budget time to be here +22:16:17 otherwise i would jump at it +22:16:52 point is that you have a pointer to an array of pointers +22:17:41 I can basically test any/all versions of Windows +22:17:44 you are not copying the pointer, your code is copying the first few chars, which will point to random crap and cause your crash +22:18:46 new_argv[0] = argv[0]; <-- that is okay +22:18:59 new_argv[i] = read_options[i-1]; <-- random crap +22:19:13 * hottuna is readying the meeting closing hammer +22:20:21 alright.. closing time +22:20:24 sponge: I'm pretty sure that section is still the same as it was for limewireExe +22:20:31 Before everyone goes, I've been thinking of "non profit 501(c)(3) status" for the Invisible Internet Project. Would this be the place to talk about that or somewhere else? +22:20:38 (Which *should* have been in a working state, according to topiltzin) +22:20:45 micster: yes +22:21:04 hottuna: we're done with #741? +22:21:22 i doubt we'll become done with it :P +22:21:29 str4d: problem 2 +22:21:33 free(read_options); +22:21:45 don't free them there +22:21:48 I saw a post in the forum about someone wanting to incorporate in Germany. I'm in the US and have an interest in pursuing this. +22:21:52 KillYourTV: re: 32/64, what currently happens with the launch4j-based i2p.exe? That starts a separate java.exe process; is it built separately for 32 and 64 bit? +22:21:55 sponge: I've gotta go. Could you take care of the rest of the meeting? +22:21:58 free them at the very end +22:22:09 I'm about to go too +22:22:15 it just needs a final baf, and it's done +22:22:18 darnit! +22:22:25 micster: Great! Sadly, timing's pretty bad. Post about it on zzz.i2p ("the forum") if you can? +22:22:28 sponge: I'll try your suggestion and report back. +22:22:31 I think it is done +22:22:38 Ok +22:22:41 (later though - afk now o/) +22:22:59 str4d: double check that it is a pointer +22:23:01 * hottuna baf's the meeting closing hammer +22:23:06 * hottuna **baf** +22:23:17 **BARF** :-) +22:23:35 summary posted at: http://zzz.i2p/topics/1397 +22:23:42 Title: zzz.i2p: Meeting [4th June] (at zzz.i2p) +22:23:50 :) +22:23:57 cool, I can now go run my errands +22:24:08 great meeting everyone! +22:24:19 micster: the meeting is now finishing up and everyone seems to have a lot they want to get across. You'll get more exposure and brain time if you post it there. +22:24:53 Ok, I'll make the post. Maybe it can be discussed in a future meeting. +22:25:01 Just wanted to see if I was in the right place. +22:26:52 lots of good discussion. thanks for making the time to particpate y'all +22:27:07 :) +22:28:54 micster, the correct thread for that is http://zzz.i2p/topics/1388 +22:28:58 Title: zzz.i2p: Official I2P group (at zzz.i2p) diff --git a/i2p2www/meetings/logs/224.rst b/i2p2www/meetings/logs/224.rst new file mode 100644 index 00000000..79146123 --- /dev/null +++ b/i2p2www/meetings/logs/224.rst @@ -0,0 +1,37 @@ +I2P dev meeting, June 4, 2013 @ 20:00 UTC +========================================= + +Quick recap +----------- + +* **Present:** + christoph2, + dg, + hottuna, + inscrutable, + KillYourTV, + Meeh, + orion, + psi, + sponge, + str4d, + topiltzin, + zzz + +* The next NetDB backend + * Fast key rotation is probably meaningless according to discussions with christop egger. + * Regarding building a completely new overlay, that may be difficult task. + +* Ticket #729 - properties location on osx + * zab/topiltzin will merge. Meehs attention is requested for some testing. + +* Ticket #741 - process renamer on windows + * KillYouTV agreed to some Win8 x84/x64 testing. + * Defaults of the new i2p exe are not set up/working yet. + * Icons for the I2P executables are not available in high quality/svg. -> Bad looks. + +* Misc? + * Sponge: Bridge API for UDP (BOB) RFC + * Sponge: IPV6 and de-anonymization since the address space is so large that each user and device is likely to have an address. + * Sponge: Will be around more Real Soon Now (tm). + * Orion: i2pcpp supports ipv6. diff --git a/i2p2www/meetings/logs/225.log b/i2p2www/meetings/logs/225.log new file mode 100644 index 00000000..466eb4fe --- /dev/null +++ b/i2p2www/meetings/logs/225.log @@ -0,0 +1,108 @@ +20:00:08 0) hi +20:00:23 1) RI verifies disabled in a point release? +20:00:30 2) misc. topics led by Meeh +20:00:33 3) baffer by Meeh +20:00:36 ------------- +20:00:36 0) hi +20:00:51 1) RI verifies disabled in a point release? +20:01:02 welterde brought this up the other day +20:01:33 if I'm going to do it it has to be in the next few days, as I'm AFK ~ 13th - 29th +20:01:53 echelon is traveling but for the moment we'll assume we can get a hold of him and he can do the news +20:02:14 so welterde, please make your case for why we should do this +20:03:08 the attack outlined in the paper is quite an serious attack for your not-well used destinations, as the required statistics are not very large +20:04:14 does it attack the server dests, or the (client) users that connect to them? +20:04:21 and for long-lived destinations it's even more dangerous as you can keep the attack going for as long as it takes to get enough statistics +20:05:08 zzz: the client that connects to some dest... say irc link tunnels over dedicated destination would be a prime target (if you get hold of the destination somehow) +20:06:29 zzz: however.. there is an option to disable RI verifies in the advanced options.. maybe news update to users to disable it? +20:06:29 have you always considered it serious or have you changed your mind recently? +20:06:56 I thought I just added that option last week? +20:07:15 oh +20:07:18 you did, I made the same mistake. +20:07:34 thought you just changed the default value of that option.. ok.. not an option then +20:07:57 maybe I didnt explain it well in some post... +20:08:59 zzz: and in the paper they also didn't take timing into account.. I guess that can be used to further improve the attack +20:09:02 We've had a preprint of their paper for almost 5 months, since March 10. If this is a drop-everything problem, we've done an incredibly poor job of responding. +20:09:33 So I'm wondering if you have always thought it critical or have changed your mind recently, if so why? +20:10:33 well.. I was under quite a bit of stress until recently.. so didn't really take a look until now +20:11:30 zzz: buts it's really hard to say as we don't really have that much data on these things.. +20:11:48 what happened to that page on trac with our openitp responses, and our lack of security criteria... +20:12:11 If it is a drop-everything problem, waiting 1 1/2 more months is a problem too. +20:12:30 sure +20:12:40 but is it +20:13:12 is the problem the RI verifies or is it Sybil? If it's Sybil then we don't have any near-term fixes +20:13:27 zzz: it's the RI verifies +20:13:46 i.e., is there a large class of hostile-ff attacks +20:14:16 zzz: and an variant of the attack might be possible with RI lookup and then waiting for an connect as well.. but that attack would be magnitudes more difficult.. so I wouldn't worry about that one just yet +20:14:35 if an attacker takes over a portion of the keyspace, isn't there any number of things he could do? +20:15:20 zzz: given enough time the attacker doesn't have to occupy an large portion of the keyspace +20:15:23 I guess I always looked at this as a Sybil issue. Doesnt me I was right. +20:15:30 *mean +20:16:07 he only has to occupy the space surrounding the target LS +20:16:53 zzz: hmm.. what would be nice for stats.i2p or so would be an visualization of the ff over the keyspace.. (if there is no such thing yet) +20:18:50 ok thanks for making the case welterde. Let me now ask for others to jump here with their opinions +20:18:53 non-subtle attacks might be visible there then +20:19:00 * welterde looks for the openitp page you mentioned +20:19:22 str4d set it up but I don't see it linked on the home page any more +20:19:35 q: Could someone pull off the RI attack without full keyspace Sybil? +20:19:45 I think yes but ??? +20:20:05 http://trac.i2p2.i2p/wiki/OpenITPReview/Criteria +20:20:35 Vulnerability Response Process Maturity and Transparency +20:21:20 we aren't ever talking about full keyspace sybil here. You're targeting a particular slice +20:21:31 dg: he only has to capture most LS lookups.. and as many RI lookups as possible; the latter portion only depends on how much time he has for the attack +20:22:17 "most"? For the network? +20:22:20 it's just really bugging me that we could have done this months ago for no effort. +20:22:39 right. it looks shit if we do it now, really. +20:22:49 but I guess that's irrelevant +20:23:14 who else has an opinion, please speak up +20:23:43 dd if=/dev/null of=opinion.txt +20:24:13 last call. we doing this? +20:24:27 of course if someone was bored he could whip up an simulation.. that would certainly help ;) +20:25:09 maybe I'm just pissed at myself that I didn't think of just turning off the verifies. +20:25:32 zzz: don't worry about it. you aren't expected to cover everything always. +20:25:43 ok everybody with an opinion please enter yes to do a release this week or no for don't +20:26:06 (or i am here if you don't care one way or the other..) +20:26:58 If I don't see any votes we arent doing it +20:27:21 will the release contain *only* disabling RI verifies? +20:27:32 vs. whatever is in trunk now? +20:27:35 maybe we shouldn't have skipped the who is here phase of the meeting +20:27:54 I'm just not qualified enough. +20:27:57 I don't care who is here. I care who has an opinion. +20:28:24 zzz: well.. who isn't here doesn't have an opinion ;) +20:28:46 zzz: I guess we are talking more about an small release, right? +20:28:59 welterde: what do you mean +20:29:02 It would be just RI verifies + anything else tiny we decide to pluck from trunk +20:29:17 and probably called 0.9.7.1? +20:29:28 yeah.. that's what I had in mind as well +20:29:39 no knowledge of this topic therefore no opinion, if we do it i'll of course be able to do the uploads to the various places, etc. +20:29:58 for gods sake somebody vote. welterde at least +20:30:13 who else has read the UCSB paper? +20:30:16 oh I am for it if that's not clear ;) +20:30:41 I've read it.. +20:31:16 I'm anxious to test the other stuff in trunk so the more we decide to pluck the more "Yes" my vote becomes. No opinion strictly on RI verification. +20:31:54 str4d: your opinion? you were quite active in the discussion on the forum ;) +20:33:56 zzz: maybe we should do the vote on the paper thread.. so str4d and tuna (and the others in the thread who are not here) have a say as well.. +20:33:56 I would want to keep the "other stuff" list very short as I would be doing this very fast and then blowing out of town, unable to fix problems +20:33:59 tuna is almost completely afk for a while yet +20:34:51 a no would be better than silence +20:35:03 zzz: well.. or kytv could do the build.. +20:35:10 in theory kytv can do releases too, he's the other one with signing keys, yes +20:36:35 ok then lets do it. I'll put a thread up on zzz.i2p if you want to propose other stuff to go in, final decision in about 24 hours, and I'll do the build maybe thursday. Can somebody contact echelon? +20:36:53 anything else on this topic? +20:37:37 I don't think so. +20:38:23 http://zzz.i2p/topics/1443 +20:38:40 please review the 17K line diff from 0.9.7 and history.txt for other pluck candidates +20:38:47 2) Meeh's topics +20:38:50 take it away Meeh +20:54:33 zzz: the tag is "i2p-0.9.7" +20:54:36 not "0.9.7" +20:54:47 * topiltzin preparing his plucklist +20:55:26 same here +20:55:32 thx +20:55:47 zzz: pm ok? +20:57:06 only if it's of zero interest to anybody else +20:58:51 draft for email to zooko +20:58:55 http://pastethis.i2p/show/0bZ3iFeE9uABCORkfXV6/ +20:58:58 Title: Paste #0bZ3iFeE9uABCORkfXV6 | LodgeIt! (at pastethis.i2p) +20:59:10 I didn't include status or anything yet. I may be way off base. Feedback appreciated. +21:01:00 3) /me *baf*s the meeting closed for Meeh +21:03:29 dg that's a really great start. diff --git a/i2p2www/meetings/logs/225.rst b/i2p2www/meetings/logs/225.rst new file mode 100644 index 00000000..28338222 --- /dev/null +++ b/i2p2www/meetings/logs/225.rst @@ -0,0 +1,12 @@ +I2P dev meeting, August 6, 2013 @ 20:00 UTC +=========================================== + +Quick recap +----------- + +* **Present:** + dg, + kytv, + topiltzin, + welterde, + zzz diff --git a/i2p2www/meetings/logs/226.log b/i2p2www/meetings/logs/226.log new file mode 100644 index 00000000..bf26e2ad --- /dev/null +++ b/i2p2www/meetings/logs/226.log @@ -0,0 +1,264 @@ +20:00:31 0) hi +20:00:38 1) website revamp (str4d) +20:00:55 2) console home page request for http://open4you.i2p/ +20:01:03 Title: open4you.i2p (at open4you.i2p) +20:01:11 3) disable outproxy (topiltzin / dg) +20:01:20 4) netdb project update (hottuna) +20:01:23 0) hi +20:01:25 hi +20:01:30 hi +20:01:35 hi +20:01:42 more info and links at http://zzz.i2p/topics/1460 +20:01:55 let's try something new and limit each agenda item to 15 minutes +20:02:00 Title: zzz.i2p: Meeting Tues. Sept. 10, 8 PM UTC (at zzz.i2p) +20:02:03 1) website revamp (str4d) +20:02:07 go str4d +20:04:12 skipping 1) for now +20:04:17 2) console home page request for http://open4you.i2p/ +20:04:21 Title: open4you.i2p (at open4you.i2p) +20:04:28 is the open4you requester here? +20:05:53 skipping 2) for now +20:05:59 3) disable outproxy (topiltzin / dg) +20:06:05 go dg or topiltzin +20:06:05 \o +20:06:13 I'll take it first. +20:06:50 Hi all, I've been mulling this over for some time: I think the outproxy for HTTP (and possibly HTTPS) being included by default isn't aligned with our goals; +20:07:25 most of the time, when asked on IRC about outproxying, community members recommend Tor and not to touch the outproxy for many/any uses +20:07:38 "we leave that to Tor" is something that's thrown around a lot +20:08:22 the outproxy is centralized which is obviously a big issue, there's problems with Tor having thousands of exit nodes even, let alone us having just one +20:08:43 security issues aside, it's a usability problem. What if someone trying to use I2P thinks I2P is just really slow because google.com loads slow? Oh, and it's in German? Huh? +20:09:14 We haven't built in the code for outproxying as a 'real' measure for a reason: we don't want to do it and hidden services are our target +20:09:58 I feel we're putting users at risk by inserting the outproxy by default and (possibly) confusing their perception of what I2P is and what it does. +20:10:04 iniial pitch over +20:10:17 topiltzin, you have anything to add? +20:10:52 that's a good list; I can also see KillYourTV 's point that the functionality should not be removed +20:11:22 ok let's throw it open to comments from others +20:11:23 but I strongly agree with dg that it's better to steer users away from using i2p for clearnet surfing +20:12:17 Someone (Pseudonemo) has suggested an explanation page as to why clearnet websites will not load and possibly a Tor recommendation. +20:12:19 a plugin that outproxies via tor locally would be nice.. +20:12:45 welterde: funny you say this.. jtor was introduced by ioerror to zzz a few weeks back. +20:13:26 dg: yeah.. that's what I was thinking about.. should be much cleaner than having to rely on an external running component +20:13:52 So, thoughts? +20:13:54 Usually the only time I observe topic of I2P's in discussion is answering questions like "Why doesnt it work like I want it to?" and supplying alternatives like Meeh's outproxy or just using Tor. Having the option for the outproxy is a good thing, and having users knowing that there is such an option is also nice. +20:13:56 I'm against removing it - it's a limited feature, yes, but what it does it actually does pretty well. We won't improve the usability of it by disabling it. We'll just make things harder and more confusing. +20:14:45 I think overall I agree with zzz (since my entrance) +20:14:58 perhaps when we have a better solution (a tor plugin) then we could disable echelon;s by default +20:15:19 options are always good, and I use the outproxies a lot, I know of course not to trust outproxies communications +20:15:21 Why should we do something that we (mostly) acknowledge is something Tor is better for? It seems like we're letting down people by even trying, it's a false impression. A well designed explanation page could ease the confusion/hardness +20:15:46 I don't suggest we remove the capability, just the default +20:15:47 sounds like dg is mainly describing a documentation / education problem, that won't be fixed by disabling it. +20:16:24 it would not be fixed but would be avoided +20:16:31 I don't know why the user should be trusting a third party by installing I2P +20:16:36 i2ptunnel is scary and I'd rather not have to point people in there to turn it on +20:16:36 Some people do not use tor and will not use tor for various reasons. They can have use for an I2P outproxy. +20:17:12 kytv's proposal to have a warning page that makes things clear would be a proper solution, no? +20:17:16 dg you are right, EpicCoffee too +20:17:26 On rare occasions I use the outproxy, mostly to check out links sent in i2prc +20:17:42 I understand we can say "well, the user should read" or similar but.. should we let them shoot themselves in the foot so easily? +20:17:49 like me EpicCoffee +20:17:51 to look at it another way, while it's on by default on the i2p side, it always takes affirmative action by the user to enable it in the browser. So you could say it is not on by default now, if you consider the browser too. +20:18:09 If the link cannot be loaded through the outproxy, I am unlikely to load it through the clearnet. +20:18:32 it takes affirmative action to browse eepsites, it is still confusing. If someone is aware of the risks, they can add the outproxy. +20:18:37 *** trolly_ is now known as trolly +20:18:37 Or load the maybe-coming tor plugin +20:18:49 I'm sure I'm not alone in this. +20:18:49 lol +20:18:55 does eche|on have an opinion? +20:19:03 This isn't an attack on echelon either but should we be trusting a single person with all outproxy traffic? +20:19:12 Regardless of who it is, it's a single point and a single person +20:19:37 would you rather trust one person you somewhat know, or 3000 people you don't? +20:19:41 An assumption could easily be made that I2P is performing a tor like mechanism +20:19:57 3000 people I don't +20:20:10 coming up on the 15 minute mark. do we have any sort of consensus? anybody else that has a thought on this? +20:20:34 imho we shouldn't disable it until we have the tor plugin +20:20:37 I think dg is primarily arguing from the perspective of new users. They don't know eche|on. +20:20:51 +1 Pseudonemo +20:20:59 *I* know eche|on, as a result, I don't mind the outproxy much but yes. +20:21:04 welterde: I can agree on this compromise. +20:21:21 nobody should use an outproxy for anything sensitive. that should be a given lol. +20:21:22 Let's leave it there? +20:21:33 assuming a tor plugin is in the works at all.. which it isn't +20:21:54 ok, interesting topic, thanks for bringing it up dg. May be worth talking about again after a while, whether we have a tor plugin or not +20:21:59 it is an education problem so it would be best to solve it through education +20:22:16 zzz: no problem, thank you. +20:22:39 any volunteers to look at the education / documentation issue and propose some improvements? +20:22:42 topiltzin: I don't think I would like a tor plugin in i2p. My opinion on that is I don't like/trust tor. +20:22:55 EpicCoffee: moved topic, save for next time :) +20:23:16 last call for volunteers and then we are done with this topic +20:23:43 ok then. +20:24:04 skipping 4) as hottuna is not here +20:24:04 lets circle back to 1), is str4d here? +20:24:45 skipping 1) again +20:24:49 * EpicCoffee must be oblivious to the "list" +20:25:01 EpicCoffee: you weren't here for the start, will pm. +20:25:09 2) open4you.i2p, which we will discuss whether or not the requestor is here. +20:25:12 ah thank you dg +20:25:13 open4you are you here? +20:25:15 EpicCoffee: channel is logged real-time http://killyourtv.i2p/irclogs/%23i2p-dev.2013-09-10.log +20:25:54 the request is at the bottom of http://zzz.i2p/topics/1429 +20:26:03 Title: zzz.i2p: 0.9.8 Release Summary (at zzz.i2p) +20:26:44 as a refresher, since we haven't done this in a while, my personal guidelines are at http://zzz.i2p/topics/236 +20:26:49 Title: zzz.i2p: How to get my Eepsite added to the Router Console home page (at zzz.i2p) +20:27:09 has anybody used this site? Does anybody have any thoughts about putting it on the console? +20:27:30 If open4you doesn't turn up, can I propose one? +20:27:31 loading the guidelines now +20:27:36 I like that the operator is upfront about what he can and cannot guarantee +20:28:08 *** trolly is now known as trolly_ +20:28:14 but besides that (positive) impression there isn't much to say... +20:28:15 we are considering open4you only today, at least in item 2). If you like you can have a new item 5) dg +20:28:28 I believe there should be available hosting on i2p, however I'm not sure I would trust a host lol. I'm conflicted on the hosting topic so I'll step aside on this one +20:28:29 zzz: ok, thx +20:28:42 his TOS looks ok to me +20:29:03 it's a new category not currently on the console so that's a plus +20:29:03 i know of no clients from open4you.i2p so I can't vouch for it but if the owner can turn up another time, I'm fine with discussing it again +20:29:56 no vouches makes me suspicious +20:30:24 the recent FreedomHosting thing makes eepsite hosting interesting +20:31:13 I get the gist this is free, right? +20:31:19 do we have any questions that the requestor must answer for us to make a decision? or can we make a decision today? +20:31:33 I didnt see whether it was free or not. the faq is only in russian. +20:31:45 it's free +20:31:45 If it's free, why not? There's no risk of a scam and it's definitely of 'interest'. +20:31:49 "9 months work free web hosting in i2p." +20:31:58 sorry guys, I was under the impression it was bitcoin +20:32:19 still, we have no idea if it actually works +20:32:46 Should we bite the bullet and find a volunteer to test it at some point from now to the release? +20:32:55 If it doesn't work, we pull it +20:33:15 I'm inclined to say yes now. I don't know what one person testing it would prove. We can always pull it later. +20:33:33 well, testing it at least works. There's not much else we can test. +20:33:39 I would hope people are at least vaguely aware of the trust issues involved in hosting +20:33:41 yeah, I'm also a yes. +20:34:10 there's no reason it shouldn't work. For one, I dont see any evidence of an automated process. +20:34:12 Any other votes? +20:34:26 it seems to be email drivne +20:34:28 driven +20:34:43 last call for opinions / objections +20:34:57 by works I mean whether the operator will actually do what he says he will do +20:35:14 do we have any testimonies from users on open4you? +20:35:22 as opposed to set up an eepsite and abandon it +20:35:24 no +20:35:28 psi: none, that's the problem +20:35:31 topiltzin: if that happens, we can remove it. +20:35:39 the owner is at least somewhat active as he requested +20:35:48 I'm for it. +20:35:53 yeah, i'd say not to go ahead with endorsement , first we get a test user in +20:35:56 my guess is he has almost no business so far. Let's give him a trial period of a couple of I2P releases with it in the console, and if its bogus then we pull it +20:36:09 or... if we endorse put a big fat warning on it +20:36:10 zzz: +1 +20:36:27 hmm +20:36:33 zzz has a good point +20:36:42 but... still +20:36:49 psi: it is free +20:36:56 psi pls clarify are you objecting or not +20:36:56 I'll email him the next few days +20:36:58 oh? it is? +20:37:04 yes +20:37:08 i am voicing caution +20:37:13 no objection +20:37:16 I guess I might as well put zab.i2p back up +20:37:22 I thought it was bitcoin but it isn't +20:37:25 It's free so.. I don't care much about testimonies yet +20:37:30 :) +20:37:40 topiltzin: You for or against? +20:37:52 abstaining +20:38:00 sounds like we have no objections and it's approved? if I'm wrong please speak up +20:38:01 I will test his hosting the next few days though +20:38:05 2 for, 0 against +20:38:12 abstain +20:38:19 abstain +20:38:26 im curious how files are transferred to open4you hosting account +20:38:47 EpicCoffee: ftp (huh?) or via a control panel it seems. +20:39:07 sftp? +20:39:18 ok I'll email him to get a logo and check the stuff into the console. Any of you so inclined, please sign up and report back +20:39:34 if it's bogus or doesnt work, we can always pull it just before the release. +20:39:35 "1 GB of available space, php5, mysql, ftp access, 3 tunnel \ 2 hop" +20:39:40 +1 +20:39:48 psi: doubt it.. +20:40:01 and that ends item 2) +20:40:18 no sign of hottuna or str4d so we're on to 5) dg's request +20:40:20 dg go +20:40:29 although it should work better over i2p (you know.. passive/active mode and so for ftp..) +20:41:36 I propose http://salt.i2p/ (not my site, efkt's) for inclusion in the router console. salt.i2p contains; a helpful, large wiki of eepsites and guides; xmpp; an IRC channel which is probably most active one on IRC2p +20:41:51 Title: salted (at salt.i2p) +20:42:00 It provides a lot of eepsite 'starting points' and is SFW. +20:42:02 ill say +1 for salt +20:42:07 I like the salt wiki +20:42:16 yep, #salt pwnz +1 +20:42:18 salt has grown to be a great resource for me and others in the community +20:42:28 the channel is #salt ftr +20:42:52 we really can only take requests from the eepsite owner. Could you ask him to apply following the guidelines on http://zzz.i2p/topics/236 ? then we can consider it for 0.9.9 +20:42:54 +1.. pretty much what that old wiki used to be now.. +20:43:06 Title: zzz.i2p: How to get my Eepsite added to the Router Console home page (at zzz.i2p) +20:43:33 I'm not familiar with the site +20:43:55 I don't think we want to start adding sites w/o permission +20:44:14 He was active not long ago, he may shoot up in a second +20:44:23 I agree with not adding w/o permission +20:44:34 figured it was worth a shot though +20:44:43 paging efkt +20:44:49 You have my permission as long as everyone's happy with it. I created the site with some of I2P's possible policies and ideas in mind about what content is appropriate for I2P. Im open to discussion if you don't like some of what might be there (Just saying) +20:44:53 efkt is the owner of salt? I presume such based on observations. +20:44:59 Yes, EpicCoffee. +20:45:10 Thus the disclaimer on the front page, explicit policies about gore/pr0n/etc +20:45:43 The wiki is not open to edit unless we end up knowing you, so it is unlikely to be vandalized. +20:46:03 * EpicCoffee also points out the salt xmpp +20:46:17 the XMPP is popular too and comes with guides. :) +20:46:50 yeah salt is pretty damn great.. has a real community feel to it +20:46:59 if you want to do it right now please answer the following questions. If it's too much to do now we can discuss in about 6 weeks before the next release +20:47:00 so long as users of it realize the admins can see what is said if not encrypted (I think the wiki article on it highly encourages otr) +20:47:06 We have enough XMPP servers floating around that in the future it might not be a bad idea to list a few in the console. Most of us running servers have S2S happening. +20:47:07 - An email address +20:47:07 - The URL to link to +20:47:07 - The URL of your English terms of service if available or necessary +20:47:07 - If the site is not in English, a brief description of the site in English +20:47:07 - (Optional) A URL to a transparent png icon to display. Size must be 32x32 (subject to change). If no icon is provided the icon will be "toopie". We will copy this icon into the router console source and serve it locally. +20:47:10 - If an icon is provided, the license of the image. +20:47:12 - (Optional) A one or two-word label in English. If not provided we will use example.i2p +20:47:14 - (Optional) a few words or a sentence in English for a popup (tooltip) +20:48:19 efkt@mail.i2p +20:48:23 site: http://salt.i2p +20:48:27 Title: salted (at salt.i2p) +20:48:38 site terms of service - Theres a disclaimer on the front page: http://salt.i2p +20:48:43 Title: salted (at salt.i2p) +20:49:15 I dont have a 32x32 icon to provide speedily but it would be the same as our favicon, a black star with transparent or white background +20:49:47 label name can be simply "salt" +20:49:59 efkt I can make a quick 32x32 icon if you want. well as quick as i2p will allow lol +20:50:25 we can give you a week for the icon :) +20:50:32 how long has the site been up? +20:50:34 EpicCoffee: If you like. Its just like the favicon - the black "anarchist star", you see the same kind of shape all over google images. It takes only a moment really +20:50:40 zzz: august 2012, IIRC +20:51:21 http://salt.i2p/wiki/index.php/Main_Page#Tutorials +20:51:21 Honestly, I'm very surprised I get so many users unable to reach the site as its not part of the default addressbook (or the XMPP) - Yet we get a lot of newcomers being directed there through IRC. Sorry to step off topic. +20:51:35 Title: Salted Wiki (at salt.i2p) +20:51:41 zzz: Oh, and the blurb "Cryptomunitions and tutorials' +20:51:46 Yeah, it's a problem (in addition to the annoying addressbook-not-found bug) when introducing users. +20:52:20 anybody on the console home page is automatically added to the default address book +20:52:42 Oh. That will be helpful for anyone who is new to I2P coming to IRC2P to explore. +20:52:52 one headache solved :) +20:52:59 1/2. +20:53:05 no xmpp.salt.i2p ;) +20:53:32 efkt to me your terms of service are insufficient for a wiki that we would recommend, as it describes only what you are not responsible for. It does not say what type of content if any is disallowed. +20:54:03 If anything goes then I cannot support the request. +20:54:04 zzz: Even though noone is allowed to edit the wiki, at all, unless I have personally vetted them and given them an account? +20:54:19 efkt: I believe he's saying the actual rules are unclear. pr0n, etc. +20:54:41 Hrm. +20:54:53 there are no rules stated at all. +20:54:56 32X32 blackstar.jpg, base64 encoded: http://pastethis.i2p/show/5437/ +20:54:57 Title: Paste #5437 | LodgeIt! (at pastethis.i2p) +20:55:00 wrt allowed content +20:55:54 I can easily add something. It's not a problem, only mulling over what "extra" things to add - Content such as Gore, Rape, Torture, Snuff, or weird sex will never be allowed on the site +20:56:23 so, family friendly - safe for work etc? +20:56:53 I don't think we should ask you to draft a content ToS in the next 30 seconds. Want to think about it and come back in a few weeks? +20:57:06 At this time no I cannot say salt is family friendly or safe for work. The onionland page explicitly links to drug onions. +20:57:43 zzz: Yes, I'd like that at least - Id rather work with everyone and produce something desirable that's useful to I2P +20:59:22 EpicCoffee: any image hosts on i2p? +20:59:24 my philosophy is that anything similar to postman's tracker rules are acceptable. +20:59:24 I don't want to tell you how to run your site or how to write your rules. You do what you like and then we'll decide if we want it in the console. +20:59:24 but you can survey the links we have now and get a feel +21:00:36 we're past 15 minutes so can we ask you to come back in a few weeks? Any site that has that much support from the folks here I think would be a good addition to the console, if you can work out the ToS stuff. +21:01:36 I'm happy to work out a ToS, and to talk about anything on the site the community feels doesn't belong. Thanks zzz. Yes that's fine +21:02:13 great. glad to hear about a new site I wasn't familiar with. I'll check it out. email me or post on zzz.i2p when you pull it all together +21:02:19 and that's the end of 5) +21:02:25 last call for str4d for 1) +21:02:36 hottuna still not here for 4) +21:02:47 * zzz warms up the baffer +21:03:50 * zzz *bafs* the meeting closed +21:07:16 thanks everybody, good meeting diff --git a/i2p2www/meetings/logs/226.rst b/i2p2www/meetings/logs/226.rst new file mode 100644 index 00000000..4febe3d8 --- /dev/null +++ b/i2p2www/meetings/logs/226.rst @@ -0,0 +1,17 @@ +I2P dev meeting, September 10, 2013 @ 20:00 UTC +=============================================== + +Quick recap +----------- + +* **Present:** + dbowie, + dg, + efkt, + EpicCoffee, + Pseudonemo, + psi, + topiltzin, + trolly, + welterde, + zzz diff --git a/i2p2www/meetings/logs/227.log b/i2p2www/meetings/logs/227.log new file mode 100644 index 00000000..c5fc3f0a --- /dev/null +++ b/i2p2www/meetings/logs/227.log @@ -0,0 +1,384 @@ +20:09:33 Meeting time. Who is here? +20:09:53 * psi is here +20:10:04 * dg here +20:11:34 * topiltzin . +20:11:51 hottuna, zzz, welterde, kytv: ping +20:12:17 * orion is here +20:13:01 * str4d loads meeting agenda +20:14:01 I can't reach zzz.i2p. Can anyone else get to http://zzz.i2p/topics/1480 ? +20:14:35 Got it. +20:14:43 1) Threat model +20:14:44 1a) Discuss merits of DREAD classification scheme (and choose another if necessary). +20:14:44 1b) Discuss threat model (and update if needed). +20:14:44 1c) Apply DREAD (or other scheme) to attack vectors in threat model. +20:14:44 2) Website revamp - check over in preparation for launch. +20:14:53 3) Roadmapping. +20:15:22 4) Docs discussion. +20:15:41 We already coverered 0) Say hi ;-P +20:15:42 1) Threat model +20:15:53 1a) Discuss merits of DREAD classification scheme (and choose another if necessary). +20:17:07 As I said in the forum post, I think that one of the things we can do to improve how other perceive I2P is to improve and clarify the threat model. +20:17:29 Right now, it is a wall of text, and difficult for users (and non-motivated devs) to find the main concerns. +20:17:45 It's hard to rank it also. +20:17:47 Understand urgency, etc. +20:18:03 And without any proper risk modelling, we really have no idea if we are focusing on the right aspects. +20:18:13 It would be great to get a short version of the threat model first and build off that +20:18:23 dg: exactly. +20:18:59 I did some research, and https://www.owasp.org/index.php/Threat_Risk_Modeling has a good threat risk modeling "layout", which is used by e.g. Cryptocat for their threat model. +20:19:04 Title: Threat Risk Modeling - OWASP (at www.owasp.org) +20:19:53 The DREAD scheme that they describe is not completely effective at identifying risk correctly, according to feedback mentioned in a subsequent post by the designer of the model - https://blogs.msdn.com/b/david_leblanc/archive/2007/08/13/dreadful.aspx +20:20:49 I propose that we use the modified DREAD model that he gives in the above post, to model the severity and priority of our attack vectors. +20:20:50 Discuss! +20:21:13 Give me some time to review the models? :) +20:21:40 dg: you were supposed to have done that already, I linked to it in the forum post... +20:21:44 :P +20:21:50 sorry +20:22:24 (but I didn't actually ask people to do so, my bad) +20:23:08 DREAD tl;dr - they rank a threat on five 1-10 scales, add the results and divide by 5. +20:23:12 Damage Potential +20:23:29 Reproducibility +20:23:29 Exploitability +20:23:29 Affected Users +20:23:30 Discoverability +20:24:12 modified DREAD tl;dr - same five parameters, but a 1-3 (low, med, high) scale and a "weighted" calculation. +20:25:09 I'm giving it a brief read; I obviously don't know all the details but any structured system is better. +20:25:18 The modified DREAD model makes better sense to me than the original. +20:26:06 I have a lot of respect for OWASP too. :P +20:26:10 "If we look at the five components, we see that none of these are highly correlated - one of them does not imply the other. This means we have independent factors, which is one of the strongest criteria for a solid model. Thus our task is to figure out how to properly weight the inputs. In WSC, we told you to rate them from 1-10, add them up, and divide by 5. If we apply some obvious tests, we find that a damage of 1, and all other factors 10 (a well known nuisance +20:26:10 , e.g., pop-ups) gets weighted the same as a discoverability of 1 and everything else 10 (hard to sort out, but causes the heat death of the universe). This is an obvious malfunction." +20:27:10 dg: so do I. They have many other potentially-useful models and docs there. +20:27:31 Anyone else have comments? +20:29:50 If no-one else has comments yet, then we will move on to the next topic while you think. +20:30:05 no comments +20:31:03 1b) Discuss threat model (and update if needed). +20:31:17 http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/docs/how/threat-model +20:31:18 * psi starts skimming threat model +20:31:39 Title: I2P's Threat Model - I2P (at vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p) +20:31:47 I notice a rating? +20:31:50 Is this new? +20:32:04 dg: I added the modified DREAD system. +20:32:12 (in anticipation of no one having objections) +20:32:31 (but not in anticipation of no comments at all :-P ) +20:32:53 The ratings are invalid. +20:33:03 It doesn't seem to match- +20:33:05 yeah +20:33:09 (this is what I want to change in this meeting) +20:33:25 While we are discussing the threat model itself, please think about possible ratings (for the next topic) +20:33:28 The design looks good so with actual values, I'd like it. We should order in value of severity too. +20:34:48 Our threat model page does not follow the "standard" threat model layout (e.g. OWASP page) +20:35:04 Identify Security Objectives +20:35:05 Survey the Application +20:35:05 Decompose it +20:35:05 Identify Threats +20:35:05 Identify Vulnerabilities +20:35:08 we're going to duscuss the values of these rating now... or later? +20:35:50 psi: next topic. Right now we are discussing the threat model itself - we can't rate threats if they are out-of-date. +20:35:58 right +20:36:17 (And FYI meeting will end at 10PM UTC) +20:36:29 (At least, I will be leaving then) +20:37:18 The threat model page does not clearly identify our security objectives. +20:37:21 Where is everyone? +20:37:29 We can't operate with 3 people. +20:37:54 topiltzin, hottuna, zzz, welterde, kytv: ping +20:37:55 there is more to "formalizing" the model than just rating each element +20:37:56 I think it is worth considering the methods outlined in todays guardian articles. The NSA tried to target the dev process +20:38:16 zzz: I know, but we have to start somewhere. +20:38:18 in particular, the major objection to our model is that we don't clearly specify what is in and what is out +20:38:40 What affects us and what doesn't? +20:38:43 which is a step that would need to happen before rating, should we care to address the critics +20:39:23 zzz: that is what we are doing now. +20:39:23 The threat model page does not clearly identify our security objectives. +20:39:29 the major point of a threat model is to specify what's NOT in it, e.g. the NSA. Projects use that to wave their hands and say "not our problem, not in our threat model" +20:39:44 we haven't done that. +20:40:07 . +20:40:10 Right. So let's do that. +20:40:29 If we make a formal model and omit the NSA, we can then stop working on protocol obfuscation, and perhaps even stronger crypto. +20:40:42 or, we could call that a copout. +20:41:18 From the start, it's clear that Tor can't save you from a GPA. Do we make this and other caveats clear? +20:41:26 and do we protect against NSA? +20:41:59 Global adversaries (that can monitor the entire internet) are out by nature of the onion routing design. +20:42:18 NSA, as big as it is, is not a global adversary. +20:42:37 the NSA as it is does have an extensive reach +20:42:38 Most of the current model is aspirational, as we are too small to realistically counter may of the items atm +20:42:50 Would we protect against GPA with some of the things in our roadmap? ;) +20:42:52 str4d: perhaps but they do work with others +20:43:01 the traditional terminology is "state-level" adversary, e.g. NSA +20:43:03 GPA? +20:43:11 equinox: likely. +20:43:13 zzz: thanks. +20:43:18 Global Passive Adversary +20:43:56 so if you want to make a strict model and exclude state-level, and use it to guide dev, then that would e.g. tell us not to work on obfuscation +20:44:47 It's a difficult enough task to maintain anonymity, let alone do obfuscation. +20:45:43 critics love formal threat models... does having one only enable the trolls, or would it actually help us promote and dev? +20:45:53 We have always stated that I2P does not do obfuscation (but not explicitly in the threat model) +20:46:19 That is a fair point. +20:46:28 a threat model is good for focus +20:46:34 The trolls have enough if they want to troll. Fuck that. +20:46:41 trolls are always around, I wouldn't take those into account +20:46:43 (sorry to jump in) +20:46:51 My goal with this meeting was not to have a strict threat model that we must absolutely follow to the letter. +20:47:02 Even if we wanted to have that, it would not be possible in a single meeting. +20:47:25 No problem. Nice to see you, Mathiasdm. +20:47:28 A formal threat model helps us to define what we're trying to protect against either +20:47:37 I've been around for almost a year and I'm still not sure exactly what. +20:47:40 The website page we call the "threat model" is a giant WoT and difficult to grep. That is really what I want to fix. +20:48:20 I want users to be able to look at it and quickly understand what we are trying to do. +20:48:50 We know the state agencies and actors on behalf of the state will only increase their scope as time goes on (if they are left unchecked). I think it is best to plan for that eventuallity rather than reacting to it. +20:49:16 Because misinformation and misunderstanding have been a problem with I2P for a long time. +20:50:28 I think the page is pretty good. Although perhaps it needs another page that's a summary. +20:51:12 The threat risk modelling (with DREAD) is something that is easy to do, and easy to remove if we decide that it doesn't give us valid information. +20:51:57 zzz: it is good for someone who is prepared to take the time to read it. It is not good for skimmers. +20:52:36 As the post I linked above says: "Warning! Do NOT apply this system, or any other system, without THINKING about it. This system may or may not help you arrive at the right conclusion, and if it does not, consider worth what you paid to get it, which is zero." +20:53:26 imho you have 3 orthogonal goals for the single page: 1) simplifying for the masses, 2) formalizing, and 3) risk modelling +20:54:38 1) and 3) are linked - having the ratings enables the masses to skim, find the "important" ones to them, and read. +20:54:49 But I agree that 2) is orthogonal (and also linked to 3) ) +20:56:04 If having a formal threat model becomes a blocker to other things, then we will need to pursue it. But when I originally said "formalize", I should have said "clarify". +20:57:43 Quick poll: does anyone here think that going through and applying DREAD to the attack vectors on our "threat model" page is useful or a good idea? +20:58:28 If yes, let's move to next topic and do so, then we can discuss the result. If no, let's forget about it and move on. +20:58:44 yes-as-long-as-its-someone-else-doing-it +20:58:46 What's the alternative? +20:59:09 hahaha +20:59:21 being honest :) +20:59:37 or depressing. :) +21:02:00 It isn't a bad idea but, I'm not sure that is the be-all-end-all solution for the threat model. +21:02:06 hmm + hottuna: I don't intend it as such, but I think it is a useful step. And no one else was suggesting or doing anything :-P + it depends if there are more people helping + if it's just 1 person no way + if there are collaborators, possibly + psi: I wanted to do it in-meeting right now, while we had more than one person. + "formalizing" is important to some - OpenITP, critics, reviewers, auditors, funders, others in our field, etc. + would it really be enough and structured well enough to just do it now in this meeting? + im not very familiar with the whole DREAD process though. + hottuna: we go through each attack vector, and rate the five categories as low, medium or high. That's all. + i am not familiar with DREAD as well + I chose that one because it was very simple to apply. + ah + (The five categories I outlined just above the index on the threat model page) + let's try an example one + each known attack vector? + psi, sure + I intentionally did everything beforehand to make it simple because I knew that getting anyone here to agree to do this would be hard :P + Okay, "timing attacks" + sure. + Damage Potential: If a threat exploit occurs, how much damage will be caused? + If it is used to identify a user, then that user is deanonymized -> high? + statistical exploits based on timing and packet sizes have been employed against tor to successfully find out which site was being visited + with very high success ratios (~90% if I remember correctly) + (use e.g. https://www.owasp.org/index.php/Threat_Risk_Modeling#DREAD to get an idea of scales - it already has three levels described) + Reliability: How reliable is the attack? - low? med? It is generally network-load-dependent. +21:12:28 to be able to time what exactly? +21:13:26 anything in general? +21:14:11 okay +21:14:27 I don't know. +21:14:47 But the descriptions seems messgae oriented. +21:14:52 (use e.g. https://www.owasp.org/index.php/Threat_Risk_Modeling#DREAD to get an idea of scales - it already has three levels described) +21:14:54 Title: Threat Risk Modeling - OWASP (at www.owasp.org) +21:14:56 Reliability: How reliable is the attack? - low? med? It is generally network-load-dependent. +21:15:33 psi: that's a good point - the "Timing attacks" section should probably be split into message-delivery attacks and message-content attacks +21:15:36 damage potential: 5? +21:15:51 Assume message-delivery for now. +21:15:55 " Complete system or data destruction " means the box explodes i assume? +21:16:08 as far as reliability goes, statistical models have been proven reliable in the case of tor.. +21:18:00 hottuna: we are using a 1-3 scale +21:19:08 the 1-10 scale described in the OWASP is harder to justify. +21:19:08 "What's the difference between discoverability of 6 and 7? Who the heck knows?" +21:19:08 Use the OWASP scale as an indicator of how to assign low/med/high +21:19:11 psi: In our case, I would say that "high" is complete correlation between a particular user and their activity. +21:19:13 timing i'd say 5 or 6 +21:19:13 (for dammage) +21:19:14 (for Damage) +21:19:17 https://blogs.msdn.com/b/david_leblanc/archive/2007/08/13/dreadful.aspx explains the categories possibly better. +21:20:00 i see +21:20:16 but the damage would be revealing some sort of information, which may be bad.. theoretically it could reveal that I'm running a certain application or talking to a certain destination +21:20:20 is that a 5-6? +21:20:34 Exploitability: What is needed to exploit this threat? - med? The attacker needs to monitor several locations along the possible path. +21:20:36 low? +21:20:49 it depends on the attacker +21:20:55 and it also depends on the network size +21:21:34 Exploitability is requirements before launching the attack. Reliability is how well it works once triggered. +21:21:48 ah +21:21:49 psi: yes, so these ratings will change over time. +21:22:05 (And this is an example of a limitation of the model, and a big flaw in the original DREAD) +21:22:06 exploitability would be med +21:22:18 Exploitability is only used to calculate priority, not severity. +21:22:25 just running a stock i2p router would be not enough +21:22:54 psi: right, so not high. +21:23:15 But not low because it doesn't need advanced computing power etc. +21:23:20 Affected Users: How many users will be affected? +21:23:27 You would have to be a part of a tunnel, and then just have a look at the message profile. If you're the ibgw for a service, you might be able to separate out a few users from the rest. Or at least cluster them inte different user groups +21:23:40 into* +21:24:23 mid may be a hit much for exploitability +21:24:29 bit* +21:24:36 mid-low +21:24:40 in the ibg case, I'd say it's pretty easy, but you wouldnt get a ton of information +21:24:45 ibgw* +21:25:06 psi: mid or low. It will only affect the priority score. +21:25:48 As far as eploitability goes, I think it's very doable. Especially in comparison to other exploits. +21:25:55 Discoverability: How easy is it to discover this threat? - mid? It requires at least some knowledge of how I2P works. +21:25:59 hottuna: agreeed +21:26:10 "Something that's highly discoverable is publicly known, or very similar to something that is publicly known. Low discoverability is that it takes intimate knowledge of the internal workings of your app to sort out." +21:26:22 mid +21:26:51 We would never know about the attack since it's passive +21:26:55 hottuna: exactly. The classification partly depends on what is chosen for other attacks. It's all relative. +21:27:26 str4d, are you noting some sort of value based on what's being said? +21:27:44 hottuna: yes. +21:29:02 good. +21:29:02 D: low +21:29:19 hmm +21:29:29 Affected users: High (all who actually do something) +21:29:37 Here's what I think we agreed on, and what it calculates: +21:29:37 Damage Potential: medium +21:29:37 Reliability: medium +21:29:37 Exploitability: medium +21:29:51 Affected Users: high +21:29:52 Discoverability: medium +21:29:53 Severity: 4/5 +21:29:54 Priority: 5/9 +21:30:23 timing attacks are pretty bad but they don't seem practical +21:30:29 at least, at the moment +21:30:41 Does that seem like a sensible result? Are the levels I set what we actually decided on? +21:30:58 I dont agree with discoverability. +21:31:01 And we should do at least one other attack vector, to get a sense of how this will compare them. +21:31:09 A passively logging node would never be discovered. +21:31:17 hottuna: you think it should be high? +21:31:17 Sure. +21:31:29 hottuna: wrong "discoverability". +21:31:47 whatever undiscoverable translates into +21:31:53 This is a defensive model. This is discoverability of the vulnerability by the attacker. +21:32:00 the resources used to launch an attack would be rather obvious unless they pwnd all the boxes +21:32:12 oh. I see. +21:32:18 Timing attacks are specific and maybe not as applicable to us anyway.. +21:32:25 Oh, in that case I agree. +21:33:28 to do a timing attack would require either a birds eye view or ownership of many nodes (how many? idk) +21:33:38 Severity is how bad we think the attack is, Priority is the order it thinks we should focus on. +21:33:55 Oh. +21:33:55 not sure if a bird's eye view would be enough too +21:33:57 Yeah, 4/5. +21:34:10 Let's leave that classification for now, and do another one for comparison. +21:34:30 reflecting on 4/5 IF they can do timing attacks then pretty much everything low latency is affect +21:34:33 affected* +21:34:54 priority... not sure 5/9 is appropriate +21:35:15 "Tagging attacks" should be easy to classify. +21:35:32 psi: we won't know what priority means until we have more classified. Classification is an iterative process. +21:35:38 okay +21:35:48 So, tagging attacks. +21:36:15 tagging messages? tagging routers? +21:36:48 Messages +21:36:59 (kinda) +21:37:07 Determining what path a message follows. +21:37:17 Damage potential: mid? +21:37:30 mid agreed +21:37:38 low in a sense +21:37:43 Damage potential: lo +21:37:47 low-mid +21:37:58 Tagging (if possible) is only going to reveal info within a particular. tunnel +21:37:58 it depends on the situation +21:38:01 Reliability: low. +21:38:01 yea +21:38:08 Or... +21:38:10 Hmm. +21:38:41 on what scope would the tagging be measured at? +21:38:58 if they were used in a situation where they could identify tunnel participants, they woulkd work every time, right? +21:39:00 Exploitability and discoverability are low - it should be impossible to tag messages themselves, and collusion requires exact placement of routers. +21:39:20 E:low +21:39:21 psi: a message going between two endpoints (a client or server). +21:39:23 D: low +21:39:39 i agree LOW +21:39:45 E and D +21:39:50 hottuna: exactly. If a tagging attack was discovered, it would work every time. +21:40:13 so, R: high? +21:40:21 But such discovery should be impossible because everything is signed. +21:40:51 But it depends on the tagging attack. +21:40:56 Message tagging: high. +21:40:57 if they have your keys then they can sign too +21:41:06 Collusion tagging: mid. +21:41:07 str4d, sure, but discoverability is another metric +21:41:13 * str4d says high for now. +21:41:28 * hottuna is sattisfied +21:41:44 Affected users: only users with malicious nodes in their tunnels are affected. +21:42:02 low +21:42:16 A: most likely low +21:42:26 Okay: +21:42:26 Damage Potential: low +21:42:27 Reliability: high +21:42:27 Exploitability: low +21:42:27 Affected Users: low +21:42:27 Discoverability: low +21:42:28 Severity: 2/5 +21:42:29 Priority: 2/9 +21:42:52 looks good +21:42:59 sounds good +21:43:22 feels good +21:43:57 onto an actual threat? +21:44:28 Shall we quickly go through the remaining meeting topics, and then come back to this? +21:44:37 ok +21:44:56 * str4d culls 4) Docs discussion, it will take too long. +21:45:12 2) Website revamp - check over in preparation for launch. +21:45:35 the site revamp is applying better CSS or is there more? +21:45:48 Apart from this classification process (or removing the classifications), what else needs doing before welterde "launches" the site revamp? +21:46:12 I dont know. +21:46:21 psi: "better" CSS, but a lot of structural and layout changes. +21:46:32 I think structurally, everything is ready. +21:46:50 How automatic is the translation update process? +21:46:50 Completely. +21:47:06 How frequent is it? +21:47:28 Whenever I update it. +21:47:45 Ok. +21:47:48 So far, whenever I have seen string changes I run the scripts to extract and update the translation strings. +21:47:50 i need to jet ill bbl in 30 minutes +21:47:56 I suppose that is good enough. +21:48:01 * str4d will be gone by then. +21:48:30 psi: you're welcome to continue the DREAD discussion then :) +21:48:44 oh, str4d: the giant download button on the front page doesnt seem to auto update to the latest version +21:48:45 There are known CSS problems in IE 7 and 8 IIRC +21:49:00 hottuna: that is another bug that I need to talk with welterde about. +21:49:09 ok. good. +21:49:25 Whenever a .py file changes, a script is meant to restart the server (and whenever translations change, it recompiles them) +21:49:49 But for some reason, changes to .py files are not being detected on welterde's server... +21:49:49 (They were before) +21:50:24 Okay, if there is nothing else, then I +21:50:43 'm happy with the revamp and once the .py bug is fixed, it can go live. +21:50:52 Alright! +21:51:11 (IE 7/8 CSS will be mitigated when I get a chance, but I don't consider it a blocker) +21:51:23 Sounds reasonable. +21:51:42 "live" == welterde will make it live at https://geti2p.net (the URL we decided on several meetings ago), but leave www.i2p2.de as-is. +21:51:52 Title: I2P Anonymous Network - I2P (at geti2p.net) +21:52:00 Why will i2p2.de be left as it is? +21:52:03 Then I will run tests, check Google etc. are happy with it. +21:52:30 hottuna: in case something catastrophic happens and we need to revert. +21:52:42 ok, so it's just temporary +21:52:51 Only when everything is absolutely checked and ready, will we 301 redirect i2p2.de to geti2p.net +21:53:15 that makes sense +21:53:23 Because 301 is a permanent move, and will cause search engines to update their links. +21:54:08 The legacy redirection code uses 302 redirects for now, but will be changed to 301 once everything is set (so that we don't lose pagerank from old links) +21:54:28 Okay, moving on: +21:54:28 3) Roadmapping. +21:54:42 hottuna: your turn. +21:55:44 You have about ten minutes of my time (maybe more for anyone else who is still here) +21:55:45 roadmap? All I know is that I've been having a little more time as of late, and I've been getting back into looking at the DHT code. Especially the reply handling code. +21:56:08 I don't really have anything else to add. +21:56:48 The current roadmap for 0.9: +21:56:48 Include some seed data in the distribution so a central reseed location isn't required? +21:56:48 Reachability Mapping / handle peers partially reachable / enhanced restricted routes +21:56:49 Improve help pages and website +21:56:49 More translations +21:56:56 SSU disconnect message +21:56:57 Iterative floodfill lookups +21:57:13 I have no idea where we are on some of that, or when it was last updated. +21:57:54 The floodfill lookups are iterative as far as I understand them. +21:57:59 1.0 - 3.0 were last updated in 2008. +21:58:14 0.9 was added in 2010. +21:58:14 restricted routes is unlikely +21:58:37 I'll have to go in a minute or two +21:58:42 I think proper evaluation of the roadmap needs another meeting, with more attendance. +21:59:01 Agreed. +21:59:14 hottuna: good to hear you are getting back into the DHT code. +21:59:29 Deferring until later. +21:59:33 And the actual threat model should be looked after. +21:59:43 Okay. +21:59:47 Could we have a long meeting next time for that? +22:00:35 hottuna: I had hoped 2 hours would be enough, but we spent at least an hour debating whether it was even worth doing >_< +22:00:36 I've gotta leave, but thanks for the meeting str4d. You're a natural! +22:01:19 We don't have time to return to 1c), so: +22:01:23 str4d *baf*s the meeting closed diff --git a/i2p2www/meetings/logs/227.rst b/i2p2www/meetings/logs/227.rst new file mode 100644 index 00000000..39adeb06 --- /dev/null +++ b/i2p2www/meetings/logs/227.rst @@ -0,0 +1,16 @@ +I2P dev meeting, October 4, 2013 @ 20:00 UTC +=============================================== + +Quick recap +----------- + +* **Present:** + dg, + equinox, + hottuna, + Mathiasdm, + orion, + psi, + str4d + topiltzin, + zzz diff --git a/i2p2www/meetings/logs/228.log b/i2p2www/meetings/logs/228.log new file mode 100644 index 00000000..b31a19e5 --- /dev/null +++ b/i2p2www/meetings/logs/228.log @@ -0,0 +1,232 @@ +20:00:54 http://zzz.i2p/topics/1490 - 15 minutes max per item, 5 minutes for brief items +20:00:54 0) hi +20:00:54 1) http://salt.i2p console home page request (carried over from Sept. 10 meeting) +20:00:55 2) http://no.i2p services request (Meeh) +20:00:55 2a) Add to default i2ptunnel jump list +20:00:55 2b) Add to recommended addressbook subscriptions on FAQ +20:00:57 2c) Add to registration help text on eepsite help +20:00:59 3) Additional backup release signer - Need new su3 keys, HH hasn't added his yet, do we need another person? +20:01:02 4) Console home page icons needed http://zzz.i2p/topics/1492 (brief) +20:01:04 5) Website revamp (str4d) (brief) +20:01:08 6) Trac update - thanks to Meeh and kytv (brief) +20:01:09 Title: zzz.i2p: Meeting Tues. Oct. 22 8 PM UTC (at zzz.i2p) +20:01:10 7) Allow marketplaces on eepsite registration services? (zab) +20:01:13 0) hi +20:01:14 1) http://salt.i2p console home page request (carried over from Sept. 10 meeting) +20:01:18 hi +20:01:18 Title: salted (at salt.i2p) +20:01:20 efkt_: +20:01:25 efkt_, are you here? +20:01:25 +1 for salt +20:01:36 Title: no.i2p registration service (at no.i2p) +20:01:37 Hi everyone. Yes I'm here. +20:01:41 Title: zzz.i2p: Console Home Page Icons (at zzz.i2p) +20:01:44 Title: salted (at salt.i2p) +20:02:20 +1 for salt +20:02:38 +1 for salt +20:02:43 I only have one question - where does the name come from,does it mean "salt" or does it stand for something? should it be translated? +20:03:00 Salt's a great community resource and efkt_ is extremely welcoming. I don't have a bad word to say about him :) +20:04:26 zzz: It really doesn't stand for anything. Unfortunately some security-thing startup recently opted to use "Salt" as well. The idea behind the name was: NaCl crypto, salted hashes as the "thematic choice" +20:05:07 Just having fun is all. +20:05:38 It leads to a lot of questions "what the hell is salt?" Why salt? +20:07:44 As for translation, I don't see that it would be useful to call it something other than what is used for the short url +20:07:47 so would we translate it in the console or not? +20:07:57 +1 for salt +20:08:51 "take everything you read on I2P with a pinch of salt" +20:09:09 hah +20:09:19 Haha. RN has ceaseless salt jokes. +20:11:36 ok. I noticed the icon you submitted doesn't have a transparent part. It might look better if it did. Or maybe not. May depend on the theme +20:11:36 if you're happy with the icon it's fine I guess +20:11:36 hearing no objections I think that's it for 1). I'll check it in. +20:11:36 moving on to 2) no.i2p - is Meeh here? +20:11:42 Perhaps it should be translated. +20:17:33 in the short term, only generating a public key, storing your private key somewhere safe, and checking it in +20:17:53 if me and kytv get hit by a bus, then you would be the one building and signing the releaase +20:18:07 which is basically running 'ant release' +20:18:08 I can do it also then. I won't be able to take responsibility for writing code though. +20:18:33 writing release notes, distributing the files, starting torrents, writing the news are all related activities +20:18:34 So, please look both ways before crossing! +20:19:00 basically you'd be a packager / release manager +20:19:23 yeah, I can do this. +20:19:41 I think str4d would be well-suited +20:20:40 dg have you done much with monotone? do you have checkin privs now? +20:21:14 zzz: I've not had checkin privs to i2p.i2p and I'm not a mtn pro. I get it enough to use it but advanced trickery is beyond me. +20:21:22 If str4d is more appropriate, that's fine. +20:21:50 other acks/nacks on str4d ? +20:29:18 ffs, I'll relay: +20:30:12 http://pastethis.i2p/show/5965 +20:30:13 Title: Paste #5965 | LodgeIt! (at pastethis.i2p) +20:30:14 bah +20:30:32 welcome back +20:30:43 ok +20:30:44 repost +20:30:50 hearing no objection let's welcome str4d as our newest backup release signer +20:30:55 str4d, kytv or I can help you generate your keys and check them in +20:31:03 excellent. I'm always worried about the bus. +20:31:06 4) Console home page icons needed http://zzz.i2p/topics/1492 (brief) +20:31:12 just wanted to mention the icons thing here, to highlight postman badger sponge eche|on kytv et al +20:31:20 Title: zzz.i2p: Console Home Page Icons (at zzz.i2p) +20:31:41 pick or design an icon or we will pick one for you +20:32:01 you have a couple weeks +20:32:17 thanks to str4d for his detailed post on what is in fux +20:32:32 anybody else have anything to say about this? +20:32:49 * kytv is indifferent +20:33:11 ok moving on +20:33:11 it'd be nice to have a prettier set of icons. I like the fux set. that's all. +20:33:12 5) Website revamp (str4d) (brief) +20:33:33 str4d, what's the status and what's blocking progress? +20:33:57 Status: .py files are not updating for some reason (they were) +20:34:22 When a .py file updates, the webserver needs to be restarted, but the script to do that has stopped working. +20:34:46 Other than that, not much. +20:35:28 CSS issues were shown on IE, it looks like on the frontpage the BG image is not displaying, but I can't test. +20:35:28 you need welterde_ or just time? +20:35:33 revamp site has issues with IE{7,8}. IE9 is untested. I don't know if we care about that. +20:35:57 IE10 works fine so I'm inclined to not worry about the older versions +20:36:05 On non-frontpage pages, IE{7,8} is terrible. +20:36:49 But that is not really a blocker. +20:37:02 wrt content, is everyone happy with the front page as-is? +20:37:13 ok. just would love to see us get past the finish line on this. On Sept. 1st on tx, you announced it would go live in a week :) +20:37:20 yes, str4d +20:37:53 zzz: yea, shortly after that I discovered the .py problem and ran out of time to fix. +20:38:20 ok thx for the update str4d. anything else on 5) ? +20:38:22 If .py -> restart is not working, then welterde_ (and every mirror operator) need to manually restart every time. +20:38:33 A few minor points: +20:38:55 When updating for a release, there are two locations to change: +20:39:16 i2p2www/__init__.py - CURRENT_I2P_VERSION +20:39:38 and i2p2www/pages/downloads/list.html - the hashes at the top. +20:39:50 maybe I can cut you short, no use training me until I need it, as I will ask again... +20:40:07 zzz: fair enough. But that ^ is it. +20:40:30 tl;dr - as soon as the .py problem is fixed, it is safe for live. +20:40:31 ok, I'll copypasta it, might lose it, might not. +20:41:01 (mine's updating/restarting FWIW (http://geti2pj2fl72u4m2.onion/ / http://kfri3jwfsi2uy7j3pbzykbbaoqoj4siyhf3hozln3wxcrkvvityq.b32.i2p/)) +20:41:04 Title: I2P Anonymous Network (at geti2pj2fl72u4m2.onion) +20:41:16 ok then let's ask welterde_ to help out here +20:41:49 ok thx for the update str4d. anything else on 5) ? +20:42:06 It's *much* simpler than current :-P +20:42:13 kytv: thanks - which script? +20:42:16 (but I'm done with 5) +20:42:25 bah. I got my sed script :) +20:42:25 Oh, one other point: +20:42:34 6) Trac update - thanks to Meeh and kytv (brief) +20:42:40 I want us to think about the /research page +20:42:42 (yw) +20:43:11 Just putting the thought out. +20:43:32 str4d: it's a modification of the one in i2p.www.revamp that I made for future appliance. I can pastebin it later. +20:43:35 I just put this on the agenda to thank kytv and his helpers Meeh and welterde_ for moving, hosting, upgrading, managing, etc and getting it back up +20:43:54 * dg thanks +20:44:18 kytv++ +20:44:20 it's an important resource that got hammered by spam and then disabled by me and then broken by kytv, but we won't mention that part since we're thanking him... +20:44:41 bwahaha +20:44:52 * str4d had plans to help, until kytv sabotaged those plans and took the glory for himself ;-P +20:45:17 oh yeah sorry str4d you did do quite a lot too in the early stages +20:45:42 ok enough of that, back to the beatings +20:45:47 7) Allow marketplaces on eepsite registration services? (zab) +20:46:18 I have 3 of them in the stats.i2p queue, everybody piling in after the silk road thing +20:46:49 Enforcing this is not trivial - we only know if the person registering makes it obvious in the domain or the about description. +20:46:51 I don't think anybody will target $registrar for saying yes +20:46:53 we had several silkroad* registrations last year, I approved them at the time, none were around for long +20:46:57 sorry I'm late, but here now +20:47:15 Meeh will be back to you shortly, we are on 7) +20:47:21 np +20:47:52 zab what would you like to say about this +20:48:00 ^^ topiltzin +20:48:00 In the interest of full disclosure, I have significant investment in bitcoin. So I'm naturally supportive of anything that promotes use of bitcoin +20:48:00 enforcing is never a sure thing +20:48:26 in fact, part of the reason I'm working on i2p is to prepare for a possible future where anonymous marketplaces cannot use tor anymore +20:48:42 +20:49:03 I could reject either on 1) its illegal 2) brings attention we dont need or 3) i2p really isnt safe enough for markets +20:49:13 but all those are shaky reasons +20:49:18 If 3), I don't know what we are safe for +20:49:21 But on the assumption that we can discover which domains are for marketplaces: +20:49:22 topiltzin ^ +20:49:35 I don't agree with ever saying "Hey, $group, come to us! We're like, safe and things!" but a little confidence is good too +20:49:49 as regards public perception, policies can help, even if they aren't perfectly enforcible, imo +20:50:01 3) is something the operators of the marketplaces need to decide for themselves +20:50:45 I agree with you there topiltzin, the operators choose +20:50:46 if 2) will happen it will happen regardless of addressbook policy +20:50:49 fyi the three I'm sitting on are silkroadreloaded.i2p, market.i2p, and freemart.i2p - you can jump to all thru stats.i2p +20:51:02 still unable to figure out why restart is not working? +20:51:35 (just arrived) +20:52:00 re 1) - that's the interesting one. I suggest the following policy: if a market place advertises $ILLEGAL_ACTIVITY then it does not indexed +20:52:08 welterde_: I haven't had time to investigate it. +20:52:18 but a market that simply says "anonymous marketplace" should not be banned automatically +20:52:28 ic +20:52:32 +1 on re 1) +20:52:34 most things here are anonymous +20:52:40 fwiw I think its reasonable to not outright ban all marketplaces and use a case-by-case basis, disallowing support for those who wish to use stats.i2p for drugs, assassination, arms, etc focusing on what is unsavory and not neccessarily what is illegal. +20:52:45 I think topiltzin's suggestion is a reasonable compromise, fwiw +20:52:59 stats.i2p is a voluntary service, not an "official" addressbook. +20:53:14 I find it hard to get too worked up about drugs. If they're advertising CP or contract killings that's another story. +20:53:27 * dg nods +20:53:35 Mmm. +20:53:43 str4d: it's still linked on the router console, which would be considered a tacit endorsement by many +20:53:51 agreed +20:54:00 IMHO the standard sort of T&C we require for routerconsole would be fine. +20:54:13 Pseudonemo: A link to a site that doesnt' really link to but can be contacted for info on a site people MAY not like? no +20:54:32 fair enough +20:54:43 I thnk I'll treat markets like forums and torrent sites, i.e. post a TOS and then I'll decide +20:54:48 (but that does not mean that a marketplace would be accepted for routerconsole, that is a separate decision) +20:56:05 that's fine. It would help if you publish some guidelines on what will NOT get indexed +20:56:12 thanks guys for your thoughts. this is more my problem than a project issue and I needed some advice. +20:57:07 if you feel uneasy about it, you are within your rights not to allow them zzz +20:57:24 but i think it's ok as long as it's not crossing any moral lines +20:57:54 it's all on http://stats.i2p/i2p/addkey.html - I guess I would just add 'markets' to the line about forums, trackers, file + image hosts... +20:57:54 ok enough on 7) +20:57:54 back around to: +20:57:54 2) http://no.i2p services request (Meeh) +20:57:54 2a) Add to default i2ptunnel jump list +20:57:54 2b) Add to recommended addressbook subscriptions on FAQ +20:57:56 2c) Add to registration help text on eepsite help +20:58:08 Title: Add a Key (at stats.i2p) +20:58:13 take it away Meeh what you got for us? +20:58:24 Title: no.i2p registration service (at no.i2p) +20:59:06 well, I've setup a registration service with a TOS somewhat the same as stats.i2p, to help "decentralize" the naming service in I2P if needed +20:59:16 ping Meeh +20:59:36 doesn't my messages get trough? +21:01:45 I hear ya +21:01:45 ok good, I checked freenode so iRelay does too +21:01:45 got it, lag +21:01:45 yeah we really need more of everything and my registration service really stands out by itself +21:01:45 just checked, I set it up in January of 2008 after orion.i2p vanished (snif) +21:02:08 yupp, so that's why I added it, to help "decentralize" it if needed +21:02:27 slow's inr.i2p service is great but his anything-goes policy isn't compatible with ours +21:02:40 other than that I haven't thought much on it, so if people want to contribute with ideas, go ahead +21:02:51 if you can work together on his software base, but have something managed, that's great +21:04:56 fwiw, inr.i2p is a thing. +21:05:24 anybody reviewed Meeh's TOS or have any thoughts? +21:05:24 I looked briefly, looked like copy-pasta of yours +21:05:24 yes, I will publish my changes. I've updated it to django 1.5 and added export-alive.txt "view" support +21:05:24 +1 on no.i2p based on nothing but general Meeh awesomeness :) +21:05:24 topiltzin: yes, it was copy paste :P +21:05:24 well, Meeh actually you have two pastas. one of slow's on no.i2p and one of mine on no.i2p/tos/ +21:05:24 I wrote some myself, and copied most of it, to make it as close to the official rules as possible, since I guessed zzz followed them closely +21:05:24 yea, a mix +21:05:24 can change it ofc +21:05:26 +1 for no.i2p. Giving people more jump links and subscriptions is a plus. If there will be more sites registered with no.i2p I think it would be helpful to inform existing userbase about such a change. +21:05:45 I didn't remove the policies that was "acceptable" from the original source +21:05:46 is it confusing to have overlapping stuff in two places? +21:05:51 actually 3 with /postkey/ +21:06:21 ok, I should fix that. but question is then, which is the best? +21:06:30 or, the most agreeable +21:06:37 which I can work more on +21:06:40 speaking from experience you have to shout the TOS loud and clear +21:07:17 fyi I'm getting about 75/month and rejecting about 3-5/month +21:07:54 any objections to 2a) or 2b) or 2c) ? +21:08:16 if not Meeh please do all the checkins yourself +21:08:23 ok, I get about 1-2 a week, but often they double register +21:08:26 both with you and me +21:08:32 for example silkroadreloaded +21:09:02 anybody have anything else while I warm up the baffer? +21:10:21 zzz: dg: kytv: topiltzin: str4d: Thank you. It means a lot to have support. +21:10:56 Maybe we should talk about the roadmap next time and our plans. +21:10:56 hosting for our downloads, unless there's already a plan, needs to be fleshed out. +21:10:56 ok. Then we say add to trunk? (no.i2p) +21:10:56 seems like we're on a new topic already :P +21:10:56 +1 for no.i2p (yes, add to trunk) +21:11:05 oh, I'll note that I wrote down some rather obvious meeting policies on http://zzz.i2p/topics/1491 to make it clear anybody can schedule a meeting for anything at any time +21:11:20 Title: zzz.i2p: Project Meetings (at zzz.i2p) +21:11:25 efkt_: No problem. You're great! +21:11:38 yeah, downloads and roadmap may be good for a future meeting +21:11:53 nothing for now from me +21:11:59 * zzz emphatically ***BAFS*** the meeting closed +21:12:12 :) diff --git a/i2p2www/meetings/logs/228.rst b/i2p2www/meetings/logs/228.rst new file mode 100644 index 00000000..a5e448ad --- /dev/null +++ b/i2p2www/meetings/logs/228.rst @@ -0,0 +1,16 @@ +I2P dev meeting, October 22, 2013 @ 20:00 UTC +============================================= + +Quick recap +----------- + +* **Present:** + dg, + efkt, + kytv, + Meeh, + Pseudonemo, + str4d + topiltzin, + welterde, + zzz diff --git a/i2p2www/meetings/views.py b/i2p2www/meetings/views.py index 1f3581c0..791dcb5f 100644 --- a/i2p2www/meetings/views.py +++ b/i2p2www/meetings/views.py @@ -29,8 +29,8 @@ def meetings_show(id, log=False, rst=False): Either display the raw IRC .log or render as html and include .rst as header if it exists """ # generate file name for the raw meeting file(and header) - lname = str(id) + '.log' - hname = str(id) + '.rst' + lname = '%03d.log' % id + hname = '%03d.rst' % id lfile = safe_join(MEETINGS_DIR, lname) hfile = safe_join(MEETINGS_DIR, hname) diff --git a/i2p2www/pages/blog/post.html b/i2p2www/pages/blog/post.html index 8f2ca980..4bc64e71 100644 --- a/i2p2www/pages/blog/post.html +++ b/i2p2www/pages/blog/post.html @@ -10,4 +10,8 @@ {% autoescape false %} {{ body }} {% endautoescape %} + +

    +Flattr this +

    {% endblock %} diff --git a/i2p2www/pages/downloads/debian.html b/i2p2www/pages/downloads/debian.html index f306a05b..e1e688b3 100644 --- a/i2p2www/pages/downloads/debian.html +++ b/i2p2www/pages/downloads/debian.html @@ -4,25 +4,24 @@

    {{ _('Debian I2P Packages') }}

    {% trans -%} -The packages hosted on the I2P Launchpad site +The Debian packages have been tested and should work on x86/x86_64 platforms running: {%- endtrans %} -{% trans trac=i2pconv('trac.i2p2.i2p') -%} +{% trans trac='http://trac.i2p2.de/newticket?component=package/debian&owner=killyourtv&cc=killyourtv@mail.i2p' -%} The I2P packages may work on systems not listed above. Please report any issues -with these packages on Trac at -http://{{ trac }}. +with these packages on Trac at +https://trac.i2p2.de. {%- endtrans %}
    • {% trans %}Option 1: Recent versions of Ubuntu and its derivatives (Try this if you're not using Debian){% endtrans %}
    • {% trans %}Option 2: Debian (including Debian-derivatives){% endtrans %}
      • -
    • {% trans %}Option 3: Non-Linux (and possibly Non-x86 architectures){% endtrans %}

    {{ _('Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like Linux Mint & Trisquel') }}

    @@ -79,69 +78,56 @@ After the installation process completes you can move on to the next part of starting I2P and configuring it for your system. {%- endtrans %} -

    {{ _('Instructions for Debian Lenny and newer') }}

    +

    {{ _('Instructions for Debian') }}

    -

    ({% trans %}For Squeeze you can follow the instructions here.{% endtrans %})

    +Currently supported architectures include amd64, i386, armel, armhf (for Raspbian), kfreebsd-amd64, kfreebsd-i386, and powerpc. -{% trans -%} -The steps below should be performed with root access (i.e., switching +

    {% trans -%} +Note: The steps below should be performed with root access (i.e., switching user to root with "su" or by prefixing each command with "sudo"). -{%- endtrans %} +{%- endtrans %}

      -
    1. - {% trans %}Add the GPG key that signs the repository with the following command:{% endtrans %}
      -     apt-key adv --keyserver keyserver.ubuntu.com --recv-keys EB2CC88B
      -{% trans %}You'll have output like the following if the command was successful:{% endtrans %}
      -     +
    2. {% trans file='/etc/apt/sources.list.d/i2p.list' -%} +Add lines like the following to {{ file }}.{% endtrans %}
      +For Squeeze:
      +
      +    deb http://deb.i2p2.no/ squeeze main
+    deb-src http://deb.i2p2.no/ squeeze main
+
      +
      +For Wheezy (stable):
      +
      +    deb http://deb.i2p2.no/ stable main
+    deb-src http://deb.i2p2.no/ stable main
+
      +
      +For Testing or Unstable:
      +
      +     deb http://deb.i2p2.no/ unstable main
+     deb-src http://deb.i2p2.no/ unstable main
+
      3. -
    3. - {% trans %}Add the following entries to /etc/apt/sources.list.d/i2p.list{% endtrans %}
      -     deb http://ppa.launchpad.net/i2p-maintainers/i2p/ubuntu raring main
      -    deb-src http://ppa.launchpad.net/i2p-maintainers/i2p/ubuntu raring main
      + +
    4. {% trans repokey=url_for('static', filename='debian-repo.pub') -%} +Download the key used to sign the repository and add it to apt: +{%- endtrans %}
      +    apt-key add debian-repo.pub
      5. +
    5. - {% trans %}Notify your package manager of the new PPA by entering{% endtrans %}
      + {% trans %}Notify your package manager of the new repository by entering{% endtrans %}
          apt-get update
      {% trans -%} This command will retrieve the latest list of software from every -repository enabled on your system, including the I2P PPA added in step +repository enabled on your system, including the I2P repository added in step 1. {%- endtrans %}
      6. -
    6. - {% trans %}You are now ready to install I2P!{% endtrans %}
      -     apt-get install i2p
      7. -
    - -{% trans -%} -After the installation process completes you can move on to the next part of starting I2P and configuring it for your system. -{%- endtrans %} - -

    {{ _('Instructions for Non-Linux / Non-x86') }}

    - -{% trans -%} -The steps below should be performed with root access (i.e., switching -user to root with "su" or by prefixing each command with "sudo"). +
  • {% trans -%} +You are now ready to install I2P! Installing the i2p-keyring +package will ensure that you receive updates to the repository's GPG key. {%- endtrans %}
    -
      -
    1. - {% trans ppa='http://ppa.launchpad.net/i2p-maintainers/i2p/ubuntu/pool/main/i/i2p/', -kytv='http://'+i2pconv('killyourtv.i2p')+'/debian/' -%} -Download the i2p-router package from the PPA. -Alternatively, there are unofficial packages available here for armel, armhf, and kfreebsd. - {%- endtrans %} -
      2. -
    2. - {% trans -%} - Make sure that you have Java installed. Running apt-get install default-jre should be sufficient.{% endtrans %}
      -{% trans %}You are now ready to install I2P!{% endtrans %}
      -     dpkg -i i2p-router_*.deb -
      3. -
    3. - {% trans jbigi=site_url('misc/jbigi') -%} - It is recommended to compile jbigi for your system to achieve better performance. Instructions are available here. - {%- endtrans %} -
      4. +     apt-get install i2p i2p-keyring
    {% trans -%} @@ -150,7 +136,6 @@ After the installation process completes you can move on to the next part of {{ _('Post-install work') }} - {% trans -%} Using these I2P packages the I2P router can be started in the following three ways: diff --git a/i2p2www/pages/downloads/list.html b/i2p2www/pages/downloads/list.html index 6f7e5510..f3e09fd3 100644 --- a/i2p2www/pages/downloads/list.html +++ b/i2p2www/pages/downloads/list.html @@ -1,19 +1,29 @@ {% extends "global/layout.html" %} {% block title %}{{ _('Download') }}{% endblock %} +{% set i2pinstall_windows_sig = '97dd4326ad8afdea0e78ffcb053b23793dfa79d89458be3fe3a1ed62a2d988e9' %} +{% set i2pinstall_jar_sig = '5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f' %} +{% set i2p_android_sig = 'a6120e19186246458a01e498eeb9e5afcb3901b9c058244410bda85d5a474113' %} +{% set i2psource_sig = 'cbbf25dea50a717c3376eb7af226f0b2a653e0372db8782ef37aa8b3d275436c' %} +{% set i2pupdate_sig = '533b0ce2d9e1bfc8762ba17eef3572ae7355ed8f21d5d3557b718a14b05794f2' %} {% block content %}

    {{ _('Download I2P') }}

    {{ _('Dependency') }}

    {% trans java='http://java.com/download/', openjdk='http://openjdk.java.net/install/', -icedtea='http://icedtea.classpath.org/wiki/Main_Page' %} +icedtea='http://icedtea.classpath.org/wiki/Main_Page', +oracle8='https://jdk8.java.net/download.html', +ibmsdk7='http://www.ibm.com/developerworks/java/jdk/linux/download.html', +detectjre='http://java.com/en/download/installed.jsp?detect=jre&try=1' %} Java Runtime 1.5 or higher. -(Oracle Java Version 6/7, -OpenJDK 6/7, or -IcedTea6/7 - recommended) +(Oracle Java Version 7, +OpenJDK 7, or +IcedTea7 + recommended, +except Raspberry Pi: Oracle 8 Early Access, +PowerPC: IBM SDK 7)
    -Determine your installed Java version here +Determine your installed Java version here or type java -version at your command prompt. {% endtrans %}

    @@ -26,8 +36,7 @@ or type java -version at your command prompt. i2pinstall_{{ ver() }}_windows.exe ({{ def_mirror.org }}) ({{ _('select alternate link') }})
    - (SHA256 -bf7d11f0a36acff9cd51ad3ef89d66975b0b0de344ca72719a5576159ec965d1 + (SHA256 {{ i2pinstall_windows_sig }} sig)
    @@ -44,8 +53,7 @@ or type java -version at your command prompt. i2pinstall_{{ ver() }}.jar ({{ def_mirror.org }}) ({{ _('select alternate link') }})
    - (SHA256 -2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371 + (SHA256 {{ i2pinstall_jar_sig }} sig)
    @@ -72,8 +80,7 @@ or type java -version at your command prompt. i2pinstall_{{ ver() }}.jar ({{ def_mirror.org }}) ({{ _('select alternate link') }})
    - (SHA256 -2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371 + (SHA256 {{ i2pinstall_jar_sig }} sig)
    @@ -97,31 +104,29 @@ or type java -version at your command prompt.

    Debian / Ubuntu

    - {% trans %}Packages for Debian & Ubuntu are available.{% endtrans %} + {% trans %}Packages for Debian & Ubuntu are available.{% endtrans %}

    Android

    - i2p-android-0.9.1-0_b1-API8.apk + i2p-android-0.9.7.1-0_b4-API8.apk
    - (SHA256 -66ed388e8038529dd3a18dcf2f18bd627a75156c98d094e92499fdb124bf4948 + (SHA256 {{ i2p_android_sig }} )
    - {% trans spongeurl='http://'+i2pconv('sponge.i2p') -%} - The Android version of I2P is being actively developed. - The latest dev build is version 0.9.3-5_b2-API8, and is available from - sponge's eepsite - - scan or click the QR code. + {% trans devbuild='0.9.7.1-23_b2-API8', str4durl='http://'+i2pconv('str4d.i2p')+'/android/' -%} + The above file is the current release build. + The latest dev build is version {{ devbuild }}, and is available from + str4d's eepsite. {%- endtrans %}
    {% trans -%} The release and dev versions of the I2P APK are not compatible, as they - are signed by zzz and sponge respectively. Uninstall one before installing + are signed by zzz and str4d respectively. Uninstall one before installing the other. {%- endtrans %}
    @@ -134,14 +139,13 @@ or type java -version at your command prompt. i2psource_{{ ver() }}.tar.bz2 ({{ def_mirror.org }}) ({{ _('select alternate link') }})
    - (SHA256 -fd2aa881d68b3164c43de9d91dcb04a93a36228d416582ada14ae40031436d18 + (SHA256 {{ i2psource_sig }} sig)
    {% trans monotoneurl=site_url('get-involved/guides/new-developers'), - gitrepo='http://git.repo.i2p/w/i2p.i2p.git', + gitrepo='http://'+i2pconv('git.repo.i2p')+'/w/i2p.i2p.git', github='https://github.com/i2p/i2p.i2p', i2pversion=ver() -%} Alternately, you can fetch the source from monotone @@ -201,7 +205,7 @@ as the default settings of 96 KBps down / 40 KBps up are fairly slow. If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy howto. {%- endtrans %}

    -

    {{ _('Updates from earlier releases:') }}

    +

    {{ _('Updates from earlier releases:') }}

    {% trans -%} Both automatic and manual upgrades are available for the release. @@ -264,8 +268,7 @@ receive the release. i2pupdate_{{ ver() }}.zip ({{ def_mirror.org }}) ({{ _('select alternate link') }})

    - (SHA256 -f322de7a9e3e89411d072d983a6577494981da488bb08f839c521ed340d77b92 + (SHA256 {{ i2pupdate_sig }} sig)
    diff --git a/i2p2www/pages/downloads/mirrors b/i2p2www/pages/downloads/mirrors index 84ca04ef..3016abd7 100644 --- a/i2p2www/pages/downloads/mirrors +++ b/i2p2www/pages/downloads/mirrors @@ -1,7 +1,6 @@ {"protocol": "http", "domain": "i2p.googlecode.com", "path": "/files/%(file)s", "org": "Google Code", "org_url": "http://code.google.com", "country": "us"} {"protocol": "https", "domain": "i2p.googlecode.com", "path": "/files/%(file)s", "org": "Google Code", "org_url": "https://code.google.com", "country": "us"} {"protocol": "https", "domain": "launchpad.net", "path": "/i2p/trunk/%(version)s/+download/%(file)s", "org": "Launchpad", "org_url": "https://launchpad.net", "country": "us"} -{"protocol": "http", "domain": "golden.mtveurope.org", "path": "/~yang/i2p_mirror/%(file)s", "org": "VServer.si", "org_url": "http://www.vserver.si", "country": "lu"} -{"protocol": "http", "domain": "a.mirror.geti2p.net", "path": "/releases/current/%(file)s", "org": "welterde", "country": "de"} -{"protocol": "http", "domain": "download.i2p2.no", "path": "/releases/current/%(file)s", "org": "meeh", "country": "no"} +{"protocol": "http", "domain": "a.mirror.geti2p.net", "path": "/releases/%(version)s/%(file)s", "org": "welterde", "country": "de"} +{"protocol": "http", "domain": "download.i2p2.no", "path": "/releases/%(version)s/%(file)s", "org": "meeh", "country": "no"} {"protocol": "https", "domain": "googledrive.com", "path": "/host/0B4jHEq5G7_EPWV9UeERwdGplZXc/%(version)s/%(file)s", "org": "Google Drive", "country": "us"} diff --git a/i2p2www/pages/global/footer.html b/i2p2www/pages/global/footer.html index f6f49979..657b1134 100644 --- a/i2p2www/pages/global/footer.html +++ b/i2p2www/pages/global/footer.html @@ -1,14 +1,14 @@

    {{ _('Mirrors') }}

    {{ _('Secure') }}

    diff --git a/i2p2www/pages/global/lang.html b/i2p2www/pages/global/lang.html index 314f7be4..e5f3d8d2 100644 --- a/i2p2www/pages/global/lang.html +++ b/i2p2www/pages/global/lang.html @@ -1,7 +1,4 @@
      -
    • English
      • -
    • Castellano
      • -
    • Deutsch
      • -
    • Français
      • -
    • Svenska
      • -
    +{% for lang in supported_langs -%} +
  • {{ lang_names[lang] }}
    • +{% endfor %} diff --git a/i2p2www/pages/global/macros b/i2p2www/pages/global/macros index 0f468f7d..89a748f1 100644 --- a/i2p2www/pages/global/macros +++ b/i2p2www/pages/global/macros @@ -6,6 +6,7 @@ {%- endif -%} {%- elif request.endpoint == 'blog_post' -%}{{ url_for('blog_post', lang=lang, slug=slug) }} {%- elif request.endpoint == 'meetings_show' -%}{{ url_for('meetings_show', lang=lang, id=id) }} +{%- elif request.endpoint == 'downloads_debian' -%}{{ url_for('downloads_debian', lang=lang) }} {%- elif request.endpoint == 'downloads_select' -%}{{ url_for('downloads_select', lang=lang, version=version, file=file) }} {%- elif request.endpoint == 'downloads_redirect' -%}{{ url_for('site_show', lang=lang) }} {%- elif request.endpoint -%}{{ url_for(request.endpoint, lang=lang) }} diff --git a/i2p2www/pages/global/nav.html b/i2p2www/pages/global/nav.html index 9dfa3751..c352bb29 100644 --- a/i2p2www/pages/global/nav.html +++ b/i2p2www/pages/global/nav.html @@ -29,40 +29,6 @@
  • {{ _('ElGamal/AES+SessionTags') }}
    • -
  • {{ _('Applications') }}
    - -
    • -
  • {{ _('API') }}
    - -
    • -
  • {{ _('Protocols') }}
    - -
    • -
  • {{ _('Transports') }}
    - -
  • {{ _('Specifications') }}
    • +
  • {{ _('API') }}
    + +
    • +
  • {{ _('Applications') }}
    + +
    • +
  • {{ _('Protocols') }}
    + +
    • +
  • {{ _('Transports') }}
    + +
  • {{ _('Tunnels') }}
    @@ -122,6 +119,7 @@
  • {{ _('Academic research') }}
    • +
  • {{ _('Open research questions') }}
  • {{ _('Guides') }}
  • {{ _('Bounties') }}
    • +
  • {{ _('Donate') }}
  • {{ _('Meetings') }}
  • {{ _('Roadmap') }}
  • {{ _('Task list') }}
    • diff --git a/i2p2www/pages/include/monotonerc.html b/i2p2www/pages/include/monotonerc.html index 7162b37b..2806b551 100644 --- a/i2p2www/pages/include/monotonerc.html +++ b/i2p2www/pages/include/monotonerc.html @@ -48,6 +48,8 @@ function get_revision_cert_trust(signers, id, name, val) "690f278ff6c6157cbaf23b0d602b6d6dcf368313", -- complication@mail.i2p "eb4ac08d5ddbb2bd73889f86c1211424025a6f07", -- dev@robertfoss.se "aae785027c240ebbb0a883fd8ebcf8d6ecee4104", -- dev@welterde.de + "86478595288d1b96b58f0c8cd8a8971bc430f8fd", -- dg2@mail.i2p + "5f75b8f0769770edc3267c21ddc9a00ddae31394", -- digit@mail.i2p "4ebaace9973913416af92ee8d0fb93d64753df4c", -- dream@mail.i2p "7e498ae94c9c322404adfc61b16bed388095906b", -- duck@mail.i2p "56c0064a8638fe180ed2f2726d6e2e404c788d3d", -- echelon@mail.i2p diff --git a/i2p2www/pages/meetings/show.html b/i2p2www/pages/meetings/show.html index c65da553..6605c51d 100644 --- a/i2p2www/pages/meetings/show.html +++ b/i2p2www/pages/meetings/show.html @@ -8,9 +8,8 @@ {% endautoescape %}

    {{ _('Full IRC Log') }}

    -
    +{% highlight lang='irc' %}
 {{ log|escape }}
-{# TODO: pygments #}
-
    +{% endhighlight %}
    {% endblock %} diff --git a/i2p2www/pages/papers/anonbib.bib b/i2p2www/pages/papers/anonbib.bib new file mode 100644 index 00000000..68ea60f1 --- /dev/null +++ b/i2p2www/pages/papers/anonbib.bib @@ -0,0 +1,205 @@ +% +% +% Magic fields: +% +% www_tags -- used to control which page groups the paper appears in. +% This is a space-separated list. +% www_section -- the topic used under 'topics.html' +% www_{ps|pdf|ps_gz|txt|html|abstract}_url -- link for text/abstract of +% an entry. +% www_important -- set for important entries +% www_remarks -- annotation for an entry + +%% List of sections +@string{comm = "Anonymous communication"} +@string{traffic = "Traffic analysis"} +@string{pub = "Anonymous publication"} +@string{proofs = "Provable shuffles"} +@string{methods = "Formal methods"} +@string{nym = "Pseudonymity"} +@string{pir = "Private Information Retrieval"} +@string{economics = "Economics"} +@string{censorship = "Communications Censorship"} +@string{credentials = "E-Cash / Anonymous Credentials"} +@string{misc = "Misc"} + +# +# Proposed new sections: application privacy, data anonymization, ... +# + +@string{lncs = "Lecture Notes in Computer Science"} + +@inproceedings{egger2013:practical-attacks, + title = {Practical Attacks Against the I2P Network}, + author = {Christoph Egger and Johannes Schlumberger and Christopher Kruegel and Giovanni Vigna}, + booktitle = {Proceedings of the 16th International Symposium on Research in Attacks, Intrusions and Defenses (RAID 2013)}, + year = {2013}, + month = {October}, + www_pdf_url = {http://wwwcip.informatik.uni-erlangen.de/~spjsschl/i2p.pdf}, + www_section = traffic, +} + +%% hal-00744922, version 1 +%% http://hal.inria.fr/hal-00744922 +@inproceedings{timpanaro:hal-00744922, + hal_id = {hal-00744922}, + url = {http://hal.inria.fr/hal-00744922}, + title = {{Improving Content Availability in the I2P Anonymous File-Sharing Environment}}, + author = {Timpanaro, Juan Pablo and Chrisment, Isabelle and Festor, Olivier}, + abstract = {{Anonymous communication has gained more and more interest from Internet users as privacy and anonymity problems have emerged. Dedicated anonymous networks such as Freenet and I2P allow anonymous file-sharing among users. However, one major problem with anonymous file-sharing networks is that the available content is highly reduced, mostly with outdated files, and non-anonymous networks, such as the BitTorrent network, are still the major source of content: we show that in a 30-days period, 21648 new torrents were introduced in the BitTorrent community, whilst only 236 were introduced in the anonymous I2P network, for four different categories of content. Therefore, how can a user of these anonymous networks access this varied and non-anonymous content without compromising its anonymity? In this paper, we improve content availability in an anonymous environment by proposing the first internetwork model allowing anonymous users to access and share content in large public communities while remaining anonymous. We show that our approach can efficiently interconnect I2P users and public BitTorrent swarms without affecting their anonymity nor their performance. Our model is fully implemented and freely usable.}}, + language = {English}, + affiliation = {MADYNES - INRIA Nancy - Grand Est / LORIA}, + booktitle = {{Proceedings of the 4th International Symposium on Cyberspace Safety and Security}}, + publisher = {Springer}, + pages = {77--92}, + address = {Melbourne, Australia}, + volume = {4}, + audience = {international }, + doi = {10.1007/978-3-642-35362-8 }, + year = {2012}, + month = Dec, + www_pdf_url = {http://hal.inria.fr/hal-00744922/PDF/Improving\_Content\_Availability\_in\_the\_I2P\_0AAnonymous\_File-Sharing\_Environment\_0A.pdf}, + www_section = comm, +} + +%% hal-00744919, version 1 +%% http://hal.inria.fr/hal-00744919 +@inproceedings{timpanaro:hal-00744919, + hal_id = {hal-00744919}, + url = {http://hal.inria.fr/hal-00744919}, + title = {{A Bird's Eye View on the I2P Anonymous File-sharing Environment}}, + author = {Timpanaro, Juan Pablo and Chrisment, Isabelle and Festor, Olivier}, + abstract = {{Anonymous communications have been gaining more and more interest from Internet users as privacy and anonymity problems have emerged. Among anonymous enabled services, anonymous file-sharing is one of the most active one and is increasingly growing. Large scale monitoring on these systems allows us to grasp how they behave, which type of data is shared among users, the overall behaviour in the system. But does large scale monitoring jeopardize the system anonymity? In this work we present the first large scale monitoring architecture and experiments on the I2P network, a low-latency message-oriented anonymous network. We characterize the file-sharing environment within I2P, and evaluate if this monitoring affects the anonymity provided by the network. We show that most activities within the network are file-sharing oriented, along with anonymous web-hosting. We assess the wide geographical location of nodes and network popularity. We also demonstrate that group-based profiling is feasible on this particular network.}}, + keywords = {Large scale monitoring, I2P, Security risks, Anonymous file-sharing}, + language = {English}, + affiliation = {MADYNES - INRIA Nancy - Grand Est / LORIA}, + booktitle = {{Proceedings of the 6th International Conference on Network and System Security}}, + address = {Wu Yi Shan, China}, + audience = {international }, + year = {2012}, + month = Nov, + www_pdf_url = {http://hal.inria.fr/hal-00744919/PDF/A\_Birda\_s\_Eye\_View\_on\_the\_I2P\_Anonymous\_0AFile-sharing\_Environment\_0A.pdf}, + www_section = traffic, +} + +%% hal-00744902, version 1 +%% http://hal.inria.fr/hal-00744902 +@inproceedings{timpanaro:hal-00744902, + hal_id = {hal-00744902}, + url = {http://hal.inria.fr/hal-00744902}, + title = {{I2P's Usage Characterization}}, + author = {Timpanaro, Juan Pablo and Chrisment, Isabelle and Festor, Olivier}, + abstract = {{We present the first monitoring study aiming to characterize the usage of the I2P network, a low-latency anonymous network based on garlic routing. We design a distributed monitoring architecture for the I2P network and show through three one-week measurement experiments the ability of the system to identify a significant number of all running applications, among web servers and file-sharing clients. Additionally, we identify 37\% of published I2P applications, which turn out to be unreachable after their publication on the I2P distributed database.}}, + language = {English}, + affiliation = {MADYNES - INRIA Nancy - Grand Est / LORIA}, + booktitle = {{Proceedings of the 4th International Workshop on Traffic Monitoring and Analysis (TMA 2012)}}, + address = {Vienne, Austria}, + audience = {international }, + year = {2012}, + month = Mar, + www_pdf = {http://hal.inria.fr/hal-00744902/PDF/TMA2012-LNCS.pdf}, + www_section = traffic, +} + +@misc{ehlert2011:usability-comparison-i2p-tor, + title = {I2P Usability vs. Tor Usability A Bandwidth and Latency Comparison}, + author = {Mathias Ehlert}, + howpublished = {Seminar, Humboldt University of Berlin}, + year = {2011}, + month = {November}, + www_pdf_url = {http://userpage.fu-berlin.de/~semu/docs/2011_seminar_ehlert_i2p.pdf}, + www_section = comm, +} + +%% inria-00632259, version 1 +%% http://hal.inria.fr/inria-00632259 +@misc{timpanaro:inria-00632259, + hal_id = {inria-00632259}, + url = {http://hal.inria.fr/inria-00632259}, + title = {{Monitoring the I2P network}}, + author = {Timpanaro, Juan Pablo and Chrisment, Isabelle and Festor, Olivier}, + howpublished = {Preprint}, + abstract = {{We present the first monitoring study aiming to characterize the usage of the I2P network, a low-latency anonymous network based on garlic routing. We design a distributed monitoring architecture for the I2P network and we show through a one week long experiment that we are able to identify 32\% of all running applications, among web servers and file- sharing clients. Additionally, we identify 37\% of published I2P applications, which turn out to be unreachable after its publication on the I2P distributed database.}}, + language = {English}, + affiliation = {MADYNES - INRIA Lorraine - LORIA}, + year = {2011}, + month = Oct, + www_pdf_url = {http://hal.inria.fr/inria-00632259/PDF/TMA2012-LNCS.pdf}, + www_section = traffic, +} + +@inproceedings{pets2011-i2p, + title = {Privacy Implications of Performance-Based Peer Selection by Onion Routers: A Real-World Case Study using I2P}, + author = {Michael Herrmann and Christian Grothoff}, + booktitle = {Proceedings of the 11th Privacy Enhancing Technologies Symposium (PETS 2011)}, + year = {2011}, + month = {July}, + location = {Waterloo, Canada}, + www_tags = {selected}, + www_pdf_url = {http://freehaven.net/anonbib/papers/pets2011/p9-herrmann.pdf}, + www_section = traffic, +} + +@mastersthesis{hermann2011-mthesis, + title = {Privacy-Implications of Performance-Based Peer Selection by Onion-Routers: A Real-World Case Study using I2P}, + author = {Michael Hermann}, + school = {TU-Munich}, + year = {2011}, + month = {March}, + www_section = traffic, +} + +@inproceedings{BlackHat2011-crenshaw, + url = {http://www.irongeek.com/i.php?page=security/darknets-i2p-identifying-hidden-servers}, + title = {Darknets and hidden servers: Identifying the true IP/network identity of I2P service hosts}, + author = {Adrian Crenshaw}, + booktitle = {Proceedings of Black Hat 2011}, + year = {2011}, + month = {January}, + location = {Washington, DC}, + www_pdf_url = {http://www.irongeek.com/downloads/Identifying%20the%20true%20IP%20of%20I2P%20service%20hosts.pdf}, + www_section = traffic, +} + +@mastersthesis{delmer-mthesis, + title = {L'{\'e}mergence au sein d'internet de communaut{\'e}s virtuelles et anonymes, Freenet et i2p}, + author = {Laurie Delmer}, + school = {Universit{\'e} catholique de Louvain - D{\'e}partement des sciences politiques et sociales}, + year = {2009}, + note = {Title : The rise in internet virtual and anonymous communities, Freenet and I2P. School: Catholic University of Leuven - Department of Political and Social Science}, + www_section = comm, +} + +@inproceedings{petcon2009-schomburg, + title = {Anonymity Techniques - Usability Tests of Major Anonymity Networks}, + author = {Jens Schomburg}, + booktitle = {Proceedings of PET-CON 2009.1}, + location = {Dresden, Germany}, + year = {2009}, + month = {March}, + pages = {49--58}, + www_pdf_url = {https://people.torproject.org/~karsten/petcon-proceedings-2009.1.pdf}, + www_section = comm, +} + +@inproceedings{petcon2009-zzz, + title = {Peer Profiling and Selection in the I2P Anonymous Network}, + author = {zzz (Pseudonym) and Lars Schimmer}, + booktitle = {Proceedings of PET-CON 2009.1}, + location = {Dresden, Germany}, + year = {2009}, + month = {March}, + pages = {59--70}, + www_pdf_url = {/_static/pdf/I2P-PET-CON-2009.1.pdf}, + www_section = comm, +} + +@misc{jrandom2003, + title = {Invisible Internet Project (I2P) Project Overview}, + author = {jrandom (Pseudonym)}, + howpublished = {Design document}, + year = {2003}, + month = Aug, + www_pdf_url = {/_static/pdf/i2p_philosophy.pdf}, + www_section = comm, +} diff --git a/i2p2www/pages/papers/anonbib.cfg b/i2p2www/pages/papers/anonbib.cfg new file mode 100644 index 00000000..be14ab8e --- /dev/null +++ b/i2p2www/pages/papers/anonbib.cfg @@ -0,0 +1,163 @@ +# Copyright 2003-2008, Nick Mathewson. See LICENSE for licensing info. + +# Our input filename. +MASTER_BIB = "./anonbib.bib" + +# Where do we put generated HTML? +OUTPUT_DIR = "." + +# Where do we put cached papers (relative to OUTPUT_DIR) +CACHE_DIR = "cache" + +# Where do we cache citations papers (relative to OUTPUT_DIR) +CITE_CACHE_DIR = "cite_cache" + +# Are there subsections for cached papers? This is useful for putting +# different Apache permission on different directories. +CACHE_SECTIONS = [ ] + +# Only include entries that have this key. This is one way to +# generate multiple bibliographies from the same source. Currently +# deprecated in favor of tags. +# +#example: REQUIRE_KEY = "www_selected" +# +REQUIRE_KEY = None + +# Timeout when downloading from a server while caching, in seconds. +DOWNLOAD_CONNECT_TIMEOUT = 15 + +# Template files. +TEMPLATE_FILE = "./_template_.html" +BIBTEX_TEMPLATE_FILE = "./_template_bibtex.html" + +# Map from author name regex to author homepage. +AUTHOR_URLS = { + 'Ross.*Anderson' : 'http://www.cl.cam.ac.uk/users/rja14/', + 'Alessandro.*Acquisti' : 'http://www.heinz.cmu.edu/~acquisti/index.html', + 'Agrawal' : 'http://www.research.ibm.com/people/a/agrawal/', + 'Adam.*Back' : 'http://www.cypherspace.org/~adam/', + 'Berthold' : 'http://page.inf.fu-berlin.de/~berthold/', + 'Borisov' : 'http://hatswitch.org/~nikita/', + 'Bettati' : 'http://faculty.cs.tamu.edu/bettati/', + 'Miguel.*Castro' : 'http://research.microsoft.com/users/mcastro/', + 'Chaum' : 'http://www.chaum.com/', + 'J.*Claessens' : 'http://www.esat.kuleuven.be/~joclaess/', + 'R.*Clayton' : 'http://www.cl.cam.ac.uk/~rnc1/', + 'Wei Dai' : 'http://www.eskimo.com/~weidai/', + 'Danezis' : 'http://homes.esat.kuleuven.be/~gdanezis/', + 'Claudia.*az' : 'http://www.esat.kuleuven.be/~cdiaz/', + 'Dingledine' : 'http://www.freehaven.net/~arma/cv.html', + 'Desmedt' : 'http://www.cs.fsu.edu/~desmedt/', + 'Douceur' : 'http://research.microsoft.com/~johndo/', + 'N.*Hopper' : 'http://www-users.cs.umn.edu/~hopper/', + 'Michael.*Freedman' : 'http://www.scs.cs.nyu.edu/~mfreed/', + 'Gergely' : 'http://www.planeforge.com/home/tgm', + 'Ian.*Goldberg' : 'http://www.cs.uwaterloo.ca/~iang/', + 'Christian.*Grothoff' : 'http://grothoff.org/christian/', + 'D.*Hopwood' : 'http://www.users.zetnet.co.uk/hopwood/', + 'Jakobsson' : 'http://www2.parc.com/csl/members/mjakobss/markus-jakobsson.htm', + 'Juels' : 'http://www.rsasecurity.com/rsalabs/staff/bios/ajuels/', + 'Kaashoek' : 'http://pdos.csail.mit.edu/~kaashoek/', + 'K.*Kurosawa' : 'http://kuro.cis.ibaraki.ac.jp/~kurosawa/', + 'H.*Langos' : 'http://www.wh9.tu-dresden.de/~heinrich/', + 'B.*Liskov' : 'http://www.pmg.lcs.mit.edu/barbara_liskov.html', + 'Mathewson' : 'http://www.wangafu.net/~nickm/', + 'Mazières' : 'http://www.scs.cs.nyu.edu/~dm/', + 'B.*Möller' : ('http://www.informatik.tu-darmstadt.de/TI/' + 'Mitarbeiter/moeller.html'), + 'U.*Möller' : 'http://www.ulfm.de/', + 'D.*Molnar' : 'http://www.cs.berkeley.edu/~dmolnar/', + 'R.*Morris' : 'http://www.pdos.lcs.mit.edu/~rtm/', + 'S.*Murdoch' : 'http://www.cl.cam.ac.uk/users/sjm217/', + 'A.*Pashalidis' : 'http://www.xrtc.com/', + 'A.*Pfitzmann' : 'http://dud.inf.tu-dresden.de/~pfitza/', + 'B.*Pfitzmann' : 'http://www.zurich.ibm.com/~bpf/', + 'B.*Preneel' : 'http://www.esat.kuleuven.be/~preneel/', + 'Daniel.*Simon' : 'http://research.microsoft.com/crypto/dansimon/me.htm', + 'Rackoff' : 'http://www.cs.toronto.edu/DCS/People/Faculty/rackoff.html', + 'Jean F' : 'http://www.geocities.com/j_f_raymond/', + 'M.*Rennhard' : 'http://www.tik.ee.ethz.ch/~rennhard/', + 'M.*Reiter' : 'http://www.ece.cmu.edu/~reiter/', + 'Rivest' : 'http://theory.lcs.mit.edu/~rivest/', + 'Avi.*Rubin' : 'http://avirubin.com/', + 'Sassaman' : 'http://homes.esat.kuleuven.be/~lsassama/', + 'Serjantov' : 'http://home.arachsys.com/~aas/', + 'S.*Seys' : 'http://www.esat.kuleuven.be/~sseys/', + 'Shoup' : 'http://www.shoup.net/', + 'Syverson' : 'http://www.syverson.org/', + 'Tsudik' : 'http://www.ics.uci.edu/~gts/c.html', + 'M.*Waidner' : 'http://www.zurich.ibm.com/~wmi/', + 'David.*Wagner' : 'http://www.cs.berkeley.edu/~daw/', + 'M.*Waldman' : 'http://cs1.cs.nyu.edu/~waldman/', + 'B.*Waters' : 'http://www.cs.utexas.edu/~bwaters/', + 'Chenxi.*Wang' : 'http://www.ece.cmu.edu/~chenxi/', + 'M.*Wright' : 'http://ranger.uta.edu/~mwright/', + 'B.*Levine' : 'http://prisms.cs.umass.edu/brian/', + 'T.*Benjamin' : 'http://www.cs.umass.edu/~tshb/', + 'B.*Defend' : 'http://www.cs.umass.edu/~defend/', + 'K.*Fu' : 'http://www.cs.umass.edu/~kevinfu/', + 'J.*Camenisch' : 'http://www.zurich.ibm.com/~jca/', + 'S.*Hohenberger' : 'http://www.cs.jhu.edu/~susan/', + 'M.*Kohlweiss' : 'http://homes.esat.kuleuven.be/~mkohlwei/', + 'A.*Lysyanskaya' : 'http://www.cs.brown.edu/~anna/', + 'M.*Meyerovich' : 'http://www.cs.brown.edu/~mira/', + 'P.*Zieli.*ski' : 'http://www.cl.cam.ac.uk/~pz215/', + 'S.*Zander' : 'http://caia.swin.edu.au/cv/szander/' + } + +# List of paterns for author names _not_ to do an initial-tolerant +# match on when building section list. E.g., if "J\\. Smith" is in +# this list, he won't be folded into "John Smith". +NO_COLLAPSE_AUTHORS = [ + +] + +# Map from LaTeX-style name of author to collapse to canonical name. +COLLAPSE_AUTHORS = { + "Nicholas Mathewson": "Nick Mathewson", + } + +# Map from author pattern to collation key. +# This keeps 'Zero Knowledge Systems' from getting alphabetized as "Systems, +# Zero Knowledge." +ALPHABETIZE_AUTHOR_AS = { + "Zero.*Knowledge.*Systems": "Zero Knowledge Systems", + "Carlos.*Aguilar.*Melchor": "Aguilar Melchor Carlos", + } + +# Map of strings to initialize BibTeX parsing with. +INITIAL_STRINGS = { + # SECTIONS + 'sec_mix' : "Mix Networks: Design", + 'sec_mixattacks' : "Mix Networks: Attacks", + 'sec_stream' : "Stream-based anonymity", + 'sec_traffic' : "Traffic analysis", + 'sec_pub' : "Anonymous publication", + 'sec_pir' : "Private Information Retrieval", + 'sec_nym' : "Pseudonymity" +} + +# Don't put in any entries of this type. +OMIT_ENTRIES = ("proceedings", "journal") + +# List of all recognized values for www_tags. +ALL_TAGS = ("selected", ) + +# Titles of page, by tag. +TAG_TITLES = { "": "I2P Bibliography", + "selected": "Selected I2P Papers" + } + +# As TAG_TITLES, but shorter. +TAG_SHORT_TITLES = { "": "I2P Bibliography", + "selected": "Selected I2P Papers", + } + +# Directories where tag pages get generated. +TAG_DIRECTORIES = { '': "full", + "selected": "" } + +# Make cached stuff group-writable. Make sure that your cache directories +# are sticky! +CACHE_UMASK = 002 diff --git a/i2p2www/pages/papers/bibtex.html b/i2p2www/pages/papers/bibtex.html new file mode 100644 index 00000000..7ba1750e --- /dev/null +++ b/i2p2www/pages/papers/bibtex.html @@ -0,0 +1,17 @@ +{% extends "global/layout.html" %} +{% block title %}{{ bib.title }}: BibTeX{% endblock %} +{% block headextra %} + +{% endblock %} +{% block content %} + +{% for entry in bib.entries %} + +{% endfor %} +
    +{{ entry.key }} +
    +{{ entry.format(90,8,1) }}
+
    +
    +{% endblock %} diff --git a/i2p2www/pages/papers/list.html b/i2p2www/pages/papers/list.html new file mode 100644 index 00000000..833e15d1 --- /dev/null +++ b/i2p2www/pages/papers/list.html @@ -0,0 +1,98 @@ +{% extends "global/layout.html" %} +{% block title %}{{ bib.tag_short_titles[bib.tag] }}{% endblock %} +{% block headextra %} + +{% endblock %} +{% block content %} +

    {{ bib.tag_titles[bib.tag] }}

    + +

    +{%- if bib.tag|length %} +{%- endif %}{{ bib.tag_titles[''] }} +{%- if bib.tag|length %}{% endif %} +{%- for tag in bib.tags %} |  +{%- if tag != bib.tag %} +{%- endif %}{{ bib.tag_titles[tag] }} +{%- if tag != bib.tag %}{% endif %} +{%- endfor -%} +

    + +

    +{%- if bib.field != 'topic' %}{% if bib.tag -%} + +{%- else -%} +{% endif %} +{%- endif %}{{ _('By topic') }}{%- if bib.field != 'topic' -%}{% endif -%} + |  +{%- if bib.field != 'date' -%}{% if bib.tag -%} + +{%- else -%} +{% endif %} +{%- endif %}{{ _('By date') }}{%- if bib.field != 'date' -%}{% endif -%} + |  +{%- if bib.field != 'author' -%}{% if bib.tag -%} + +{%- else -%} +{% endif %} +{%- endif %}{{ _('By author') }}{%- if bib.field != 'author' -%}{% endif -%} +

    + + + + + + + + + + + +
    + + + + + +

    {{ bib.sectiontypes }}:

    +{% for section in bib.sections %} +

    {{ section.name }}

    +{% endfor %} +
    +    		 + +

    Publications by {{ bib.field }}

    + +
      +{% for section in bib.sections %} +

    • {{ section.name }}

      +
        +{% for entry in section.entries %} +{{ entry.to_html()|safe }} +{% endfor %} +
      • +{% endfor %} +
    + +
    + +

    {% trans email="press@i2p2.de"|safe, +bibtex = get_url('papers_bibtex', tag=bib.tag) if bib.tag else get_url('papers_bibtex'), +citeseer = 'http://citeseer.ist.psu.edu/online-nature01/' -%} +Please send new or corrected entries to +.
    +If you can, please format them as BibTeX; see our +BibTeX source page for examples.
    +Remember to include URLs if possible: +offline papers are less useful. +{%- endtrans %}

    + +

    {% trans anonbib="https://gitweb.torproject.org/anonbib.git" -%} +The source code for this page was adapted from +Free Haven's anonymity bibliography. +{%- endtrans %}

    +{% endblock %} diff --git a/i2p2www/pages/site/about/browser-config.html b/i2p2www/pages/site/about/browser-config.html index e3b56988..488c6d12 100644 --- a/i2p2www/pages/site/about/browser-config.html +++ b/i2p2www/pages/site/about/browser-config.html @@ -80,9 +80,9 @@ Instead, it is meant to be used as an internal network. services are run by by private volunteers and could be shut down or unreachable at anytime. {%- endtrans %}

    -

    {% trans -%} -By default, I2P comes with two outproxies configured: false.i2p -(an HTTP-only proxy) and outproxyng.h2ik.i2p (an HTTPS proxy +

    {% trans http='false.i2p', https='outproxy-tor.meeh.i2p' -%} +By default, I2P comes with two outproxies configured: {{ http }} +(an HTTP-only proxy) and {{ https }} (an HTTPS proxy routed through Tor. {%- endtrans %}

    {% trans -%} @@ -91,12 +91,11 @@ that only set amount of accesses are allowed per client. Once the limit is reached, the client is blocked out for a timeframe of 1min/1h/1 day. Be respectful and do not overload these services with too many requests! {%- endtrans %}

    -

    {% trans tpb=i2pconv('tpb.i2p') -%} +

    {% trans -%} Filtering is active on these outproxies (for example, mibbit and torrent -tracker access is blocked). Note that even though the pirate bay is blocked -they host an official eepsite at {{ tpb }}. Eepsites +tracker access is blocked). Eepsites that are accessible via .i2p addresses are also not allowed via the outproxies. -As a convenience, False.i2p blocks ad servers. +As a convenience, false.i2p blocks ad servers. {%- endtrans %}

    {% trans -%} Tor is good application to use as an diff --git a/i2p2www/pages/site/about/hall-of-fame.html b/i2p2www/pages/site/about/hall-of-fame.html index be1615c3..161db01a 100644 --- a/i2p2www/pages/site/about/hall-of-fame.html +++ b/i2p2www/pages/site/about/hall-of-fame.html @@ -1,13 +1,13 @@ {% extends "global/layout.html" %} {% block title %}{{ _('Hall Of Fame') }}{% endblock %} {% block content %} - +

    {% trans %}I2P's Hall of Fame{% endtrans %}

    -{% trans date='2013-05-01' -%} +{% trans date='2013-08-25' -%} Current balance: as of {{ date }} {%- endtrans %}
    {{ _('General fund') }}: -{% trans euroval='28078,57', btcval='626,04640057' %}{{ euroval }} € and {{ btcval }} BTC{% endtrans %}
    +{% trans euroval='28829,12', btcval='607,49839100' %}{{ euroval }} € and {{ btcval }} BTC{% endtrans %}
    {{ _('Datastorage bounty') }}: {% trans euroval='145.0', btcval='2' %}{{ euroval }} € and {{ btcval }} BTC{% endtrans %}
    {{ _('Native IPv6 I2P') }}: @@ -15,9 +15,9 @@ Current balance: as of {{ date }} {{ _('I2PHex bounty') }}: {% trans euroval='100.0' %}{{ euroval }} €{% endtrans %}
    {{ _('I2P in debian mirrors') }}: -{% trans euroval='123.0' %}{{ euroval }} €{% endtrans %}
    +{% trans euroval='148.0' %}{{ euroval }} €{% endtrans %}
    {{ _('Bitcoin client for I2P') }}: -{% trans btcval='50.34' %}{{ btcval }} BTC{% endtrans %}
    +{% trans euroval='10', btcval='50.34' %}{{ euroval }} € and {{ btcval }} BTC{% endtrans %}
    {{ _('Unit Tests for I2P router') }}: {% trans euroval='2305' %}{{ euroval }} €{% endtrans %}
    {{ _('Bounty Robert') }}: 20
    @@ -113,6 +113,7 @@ with your name or nick (and optionally homepage) so we can list you here. Apr, 2013SSL cert i2p2.de2009,70 €General fund Apr, 2013anonymous4 €General fund Apr, 2013anonymous10 €General fund + Apr, 2013anonymous10 €I2PBTC native client Apr, 2013anonymous1 BTCGeneral fund Apr, 201329C3 contest25 BTCGeneral fund Apr, 201329C3 contest5 BTCGeneral fund @@ -128,6 +129,41 @@ with your name or nick (and optionally homepage) so we can list you here. May, 2013anonymous0.3 BTCGeneral fund May, 2013anonymous10 €Bounty CCR Microtic Board + May, 2013anonymous20 €General fund + May, 2013anonymous30 €General fund + May, 2013anonymous3.50 €General fund + May, 2013anonymous0.0008 BTCGeneral fund + May, 2013anonymous0.0991 BTCGeneral fund + + June, 2013anonymous10 €General fund + June, 2013anonymous20 €General fund + June, 2013anonymous30 €General fund + June, 2013DHT bounty325 €DHT bounty + June, 2013anonymous1 €General fund + June, 2013anonymous0.0000067 BTCGeneral fund + June, 2013anonymous0.01 BTCGeneral fund + June, 2013anonymous0.031 BTCGeneral fund + June, 2013anonymous0.25 BTCGeneral fund + + July, 2013first-leon1 €General fund + July, 2013anonymous5 €General fund + July, 2013anonymous2 €General fund + July, 2013anonymous20 €General fund + July, 2013anonymous0.05 €General fund + July, 2013anonymous30 €General fund + July, 2013JULLIAN David15 €General fund + July, 2013anonymous0.00567899 BTCGeneral fund + July, 2013anonymous0.00942744 BTCGeneral fund + July, 2013anonymous0.01807730 BTCGeneral fund + July, 2013fraud loss9 BTCGeneral fund + + Aug, 2013anonymous18 €General fund + Aug, 2013anonymous30 €General fund + Aug, 2013sell BTC820 €10 BTCGeneral fund + Aug, 2013anonymous20 €General fund + Aug, 2013anonymous25 €Bounty deb package + Aug, 2013anonymous0.0279 BTCGeneral fund +

    diff --git a/i2p2www/pages/site/about/media.html b/i2p2www/pages/site/about/media.html index 641326da..17b7a7b6 100644 --- a/i2p2www/pages/site/about/media.html +++ b/i2p2www/pages/site/about/media.html @@ -193,12 +193,10 @@ November 2007. {%- endtrans %}
  • {% trans link='http://www.gulli.com/news/i2p-an-anonymous-network-2009-03-09/', -german='http://www.gulli.com/news/i2p-anonymes-netzwerk-im-2009-03-09/', -russian='http://translated.by/you/i2p-an-anonymous-network-interrogated/into-ru/' -%} +german='http://www.gulli.com/news/i2p-anonymes-netzwerk-im-2009-03-09/' -%} zzz interviewed by gulli.com March 2009 German translation -Russian translation {%- endtrans %}
  • {% trans mp3='http://www.isdpodcast.com/podcasts/infosec-daily-podcast-episode-454.mp3' -%} diff --git a/i2p2www/pages/site/about/performance/history.html b/i2p2www/pages/site/about/performance/history.html index 59f92ba9..896de288 100644 --- a/i2p2www/pages/site/about/performance/history.html +++ b/i2p2www/pages/site/about/performance/history.html @@ -24,7 +24,7 @@ Rather than try to tune this method, we'll call out to ugha and duck are working on the C/JNI glue code, and the existing java code is already deployed with hooks for that whenever its ready. Preliminary results look fantastic - running the router with the native GMP modPow is providing over -a 800% speedup in encryption performance, and the load was cut in half. This +a 800% speedup in encryption performance, and the load was cut in half. This was just on one user's machine, and things are nowhere near ready for packaging and deployment, yet. {%- endtrans %}

    @@ -54,7 +54,7 @@ have to do the network database lookup.

    {% trans -%} For unpublished LeaseSets such as "shared clients", this is the only way to get the LeaseSet to Bob. Unfortunately this bundling every time adds -almost 100% overhead to a high-bandwidth connection, and much more to +almost 100% overhead to a high-bandwidth connection, and much more to a connection with smaller messages. {%- endtrans %}

    {% trans -%} @@ -71,7 +71,7 @@ going through the full (expensive) Diffie-Hellman handshaking to negotiate a private session key. This means that if someone's clock is really wrong, or their NAT/firewall/etc is improperly configured (or they're just running an incompatible version of the router), they're going to consistently (though not -constantly, thanks to the shitlist) cause a futile expensive cryptographic +constantly, thanks to the banlist) cause a futile expensive cryptographic operation on all the peers they know about. While we will want to keep some verification/validation within the encryption boundary, we'll want to update the protocol to do some of it first, so that we can reject them cleanly @@ -140,7 +140,7 @@ message based, with the router providing delivery guarantees by garlic wrapping an "ACK" message in with the payload, so once the data gets to the target, the ACK message is forwarded back to us [through tunnels, of course]). {%- endtrans %}

    -

    {% trans link='http://dev.i2p.net/pipermail/i2p/2004-March/000167.html' -%} +

    {% trans link='http://web.archive.org/web/20070607220008/http://dev.i2p.net/pipermail/i2p/2004-March/000167.html' -%} As I've said, having I2PTunnel (and the ministreaming lib) go this route was the best thing that could be done, but more efficient mechanisms are available. When we rip out the diff --git a/i2p2www/pages/site/about/team.html b/i2p2www/pages/site/about/team.html index 95e1cd31..27fcaa43 100644 --- a/i2p2www/pages/site/about/team.html +++ b/i2p2www/pages/site/about/team.html @@ -11,7 +11,7 @@ network. - + @@ -71,6 +71,16 @@ network. + + + + + + + + + + @@ -82,12 +92,12 @@ network. - + - + @@ -103,7 +113,7 @@ network. - + @@ -174,38 +184,11 @@ network. - - - + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -230,7 +213,7 @@ network. - + @@ -353,6 +336,33 @@ network. + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/i2p2www/pages/site/comparison/index.html b/i2p2www/pages/site/comparison/index.html index f87651a5..e473eb94 100644 --- a/i2p2www/pages/site/comparison/index.html +++ b/i2p2www/pages/site/comparison/index.html @@ -29,9 +29,9 @@ The following are discussed on the other networks
  • Haystack
    • -

    {% trans trac=i2pconv('trac.i2p2.i2p') -%} +

    {% trans trac='https://trac.i2p2.de/report/1' -%} The content of this page is subject to update, discussion and dispute, and we welcome comments and additions. -You may contribute an analysis by entering a new ticket on Trac. +You may contribute an analysis by entering a new ticket on Trac. {%- endtrans %}

    {% endblock %} diff --git a/i2p2www/pages/site/comparison/other-networks.html b/i2p2www/pages/site/comparison/other-networks.html index 61373ac3..34d60e3a 100644 --- a/i2p2www/pages/site/comparison/other-networks.html +++ b/i2p2www/pages/site/comparison/other-networks.html @@ -13,12 +13,12 @@ The following networks are discussed on this page.
  • Haystack
    • -

    {% trans comparison=site_url('comparison'), trac=i2pconv('trac.i2p2.i2p') -%} +

    {% trans comparison=site_url('comparison'), trac='https://trac.i2p2.de/report/1' -%} Most of the following sections are fairly old, and may not be accurate. For an overview of available comparisons, see the main network comparisons page. You may contribute an analysis by entering a -new ticket on {{ trac }}. +new ticket on Trac. {%- endtrans %}

    @@ -150,13 +150,11 @@ comparison of Tarzan, Crowds, Onion Routing (OR), and I2P:

    [Mixminion] [Mixmaster] -

    {% trans %} +

    {% trans syndie='http://syndie.i2p2.de/' %} Mixminion and Mixmaster are networks to support anonymous email against a very powerful adversary. High-latency messaging applications running on top of I2P -(for example -Syndie or -I2PBote) +(for example Syndie or I2PBote) may perhaps prove adequate to meet the threat model of those adversaries, while running in parallel along side the needs of low latency users, to provide a significantly larger anonymity set. @@ -219,25 +217,25 @@ particular issues can be addressed. {%- endtrans %}

    Haystack

    -

    {% trans docs=site_url('docs') -%} +

    {% trans torpost='http://blog.torproject.org/blog/ten-things-look-circumvention-tool', +docs=site_url('docs') -%} This was a closed-source network targeted at Iranian users. -Tor did a -good writeup on what to look for in a circumvention tool. +Tor did a good writeup on what to look for in a circumvention tool. Suffice it to say that being closed source and publicly targeting a specific country are not good ideas. I2P is, of course, open source. However, that source, and our technical documentation, need much more review. {%- endtrans %}

    {{ _('Paid VPN Services') }}

    -

    {% trans trac=i2pconv('trac.i2p2.i2p') -%} +

    {% trans trac='https://trac.i2p2.de/report/1' -%} You may contribute an analysis by entering a -new ticket on {{ trac }}. +new ticket on Trac. {%- endtrans %}

    {{ _('Others') }}

    -

    {% trans trac=i2pconv('trac.i2p2.i2p') -%} +

    {% trans trac='https://trac.i2p2.de/report/1' -%} You may contribute an analysis by entering a -new ticket on {{ trac }}. +new ticket on Trac. {%- endtrans %}

    diff --git a/i2p2www/pages/site/comparison/tor.html b/i2p2www/pages/site/comparison/tor.html index e1c15fd8..4b972f33 100644 --- a/i2p2www/pages/site/comparison/tor.html +++ b/i2p2www/pages/site/comparison/tor.html @@ -3,7 +3,7 @@ {% block content %}

    Tor / Onion Routing

    -[Tor] +[Tor] [Onion Routing]

    {% trans netdb=site_url('docs/how/network-database'), peerselection=site_url('docs/how/peer-selection') -%} Tor and Onion Routing are both anonymizing proxy networks, diff --git a/i2p2www/pages/site/contact.html b/i2p2www/pages/site/contact.html index e8c5502f..a85af313 100644 --- a/i2p2www/pages/site/contact.html +++ b/i2p2www/pages/site/contact.html @@ -1,6 +1,12 @@ {% extends "global/layout.html" %} {% block title %}{{ _('Contact') }}{% endblock %} {% block content %} +

    {{ _('Email') }}

    + +

    IRC

    {% trans -%} Our primary IRC network is the Irc2P network within I2P; a default tunnel to this network is set up with new router installs. diff --git a/i2p2www/pages/site/docs/api/i2pcontrol.html b/i2p2www/pages/site/docs/api/i2pcontrol.html index d3f50466..0faeecbe 100644 --- a/i2p2www/pages/site/docs/api/i2pcontrol.html +++ b/i2p2www/pages/site/docs/api/i2pcontrol.html @@ -2,7 +2,7 @@ {% block title %}I2PControl API{% endblock %} {% block content %}

    {% trans %}I2PControl - Remote Control Service{% endtrans %}

    -

    {% trans itoopie='http://itoopie.net/' -%} +

    {% trans itoopie='http://'+i2pconv('itoopie.i2p')+'/' -%} I2P enables a JSONRPC2 interface via the plugin I2PControl. The aim of the interface is to provide simple way to interface with a running I2P node. A client, itoopie, has been developed in parallel. The JSONRPC2 implementation for the client as well as the plugin is provided by the java libraries JSON-RPC 2.0. @@ -191,6 +191,7 @@ Parameters are only provided in a named way (maps).

  • -32700 – {% trans %}JSON parse error.{% endtrans %}
  • -32600 – {% trans %}Invalid request.{% endtrans %}
  • -32601 – {% trans %}Method not found.{% endtrans %}
    • +
  • -32602 – {% trans %}Invalid parameters.{% endtrans %}
  • -32603 – {% trans %}Internal error.{% endtrans %}
      • {% trans %}I2PControl specific error codes.{% endtrans %} diff --git a/i2p2www/pages/site/docs/api/i2ptunnel.html b/i2p2www/pages/site/docs/api/i2ptunnel.html index 608ab170..f06536cd 100644 --- a/i2p2www/pages/site/docs/api/i2ptunnel.html +++ b/i2p2www/pages/site/docs/api/i2ptunnel.html @@ -40,8 +40,8 @@ A HTTP proxy used for browsing I2P and the regular internet anonymously through Browsing internet through I2P uses a random proxy specified by the "Outproxies:" option. {%- endtrans %}
    • Irc2P - localhost:6668 - {% trans %}An IRC tunnel to the default anonymous IRC network, Irc2P.{% endtrans %}
      • -
    • mtn.i2p2.i2p - localhost:8998 - {% trans -%} -The anonymous monotone +
    • mtn.i2p2.i2p - localhost:8998 - {% trans monotone='http://en.wikipedia.org/wiki/Monotone_%28software%29' -%} +The anonymous monotone sourcecode repository for I2P {%- endtrans %}
    • smtp.postman.i2p - localhost:7659 - {% trans postman=i2pconv('hq.postman.i2p') -%} diff --git a/i2p2www/pages/site/docs/api/streaming.html b/i2p2www/pages/site/docs/api/streaming.html index a7c60e2a..d15c51c8 100644 --- a/i2p2www/pages/site/docs/api/streaming.html +++ b/i2p2www/pages/site/docs/api/streaming.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}{% trans %}Streaming Library{% endtrans %}{% endblock %} -{% block lastupdated %}{% trans %}November 2012{% endtrans %}{% endblock %} -{% block accuratefor %}0.9.3{% endblock %} +{% block lastupdated %}{% trans %}December 2013{% endtrans %}{% endblock %} +{% block accuratefor %}0.9.9{% endblock %} {% block content %}

      {% trans %}Overview{% endtrans %}

      @@ -134,10 +134,26 @@ Use the access list as a blacklist for incoming connections. As of release {{ release }}. {%- endtrans %}
     + + + + - + + + + + + + + + + + @@ -357,11 +413,37 @@ CLOSE packets may contain data as well. {%- endtrans %}

    +

    Ping / Pong

    +

    {% trans -%} +There is no ping function at the I2CP layer (equivalent to ICMP echo) or in datagrams. +This function is provided in streaming. +Pings and pongs may not be combined with a standard streaming packet; +if the ECHO option is set, then +most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. are ignored. +{%- endtrans %}

    + +

    {% trans -%} +A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED flags set. +The sendStreamId must be greater than zero, and the receiveStreamId is ignored. +The sendStreamId may or may not correspond to an existing connection. +{%- endtrans %}

    + +

    {% trans -%} +A pong packet must have the ECHO flag set. +The sendStreamId must be zero, and the receiveStreamId is the sendStreamId from the ping. +The pong packet does not include any payload that was contained in the ping. +{%- endtrans %}

    + +

    {% trans -%} +Streaming may be configured to disable sending pongs with the configuration i2p.streaming.answerPings=false. +{%- endtrans %}

    + +

    {% trans %}Control Block Sharing{% endtrans %}

    {% trans -%} The streaming lib supports "TCP" Control Block sharing. -This shares two important streaming lib parameters -(window size and round trip time) +This shares three important streaming lib parameters +(window size, round trip time, round trip time variance) across connections to the same remote peer. This is used for "temporal" sharing at connection open/close time, not "ensemble" sharing during a connection (See @@ -370,7 +452,14 @@ There is a separate share per ConnectionManager (i.e. per local Destination) so that there is no information leakage to other Destinations on the same router. The share data for a given peer expires after a few minutes. -{%- endtrans %}

    +The following Control Block Sharing parameters can be set per router: +{%- endtrans %} +
      +
    • RTT_DAMPENING = 0.75
      • +
    • RTTDEV_DAMPENING = 0.75
      • +
    • WINDOW_DAMPENING = 0.75
      • +
    +

    {% trans %}Other Parameters{% endtrans %}

    {% trans -%} @@ -381,10 +470,12 @@ The following parameters are hardcoded, but may be of interest for analysis:

  • MAX_RESEND_DELAY = 45*1000 (maximum RTO)
  • MIN_WINDOW_SIZE = 1
  • TREND_COUNT = 3 -
  • RTT_DAMPENING = 0.875
  • MIN_MESSAGE_SIZE = 512 (minimum MTU)
  • INBOUND_BUFFER_SIZE = maxMessageSize * (maxWindowSize + 2) -
  • INITIAL_TIMEOUT = 1.5 * initialRTT +
  • INITIAL_TIMEOUT (valid only before RTT is sampled) = 9000 +
  • "alpha" ( RTT dampening factor as per RFC 6298 ) = 0.125
    • +
  • "beta" ( RTTDEV dampening factor as per RFC 6298 ) = 0.25
    • +
  • "K" ( RTDEV multiplier as per RFC 6298 ) = 4
  • PASSIVE_FLUSH_DELAY = 250
  • Maximum RTT estimate: 60*1000 diff --git a/i2p2www/pages/site/docs/applications/bittorrent.html b/i2p2www/pages/site/docs/applications/bittorrent.html index 79320856..86744fa0 100644 --- a/i2p2www/pages/site/docs/applications/bittorrent.html +++ b/i2p2www/pages/site/docs/applications/bittorrent.html @@ -108,7 +108,7 @@ The peers key may be absent, or the peers value may be zero-length.

    {% trans -%} While compact response support is optional for both clients and trackers, it is highly -recommended as it reduces the nominal response size by over 90%. +recommended as it reduces the nominal response size by over 90%. {%- endtrans %}

    diff --git a/i2p2www/pages/site/docs/applications/supported.html b/i2p2www/pages/site/docs/applications/supported.html index f454e644..02f01c06 100644 --- a/i2p2www/pages/site/docs/applications/supported.html +++ b/i2p2www/pages/site/docs/applications/supported.html @@ -82,10 +82,10 @@ -

    {% trans trac=i2pconv('trac.i2p2.i2p') -%} +

    {% trans trac='https://trac.i2p2.de/report/1' -%} This is intended to be a comprehensive listing of applications used with I2P. If you know of something that's missing please submit a ticket on -Trac, and be sure to select the +Trac, and be sure to select the “www” component in the submission form. {%- endtrans %}

    @@ -310,6 +310,19 @@ email service by default. {%- endtrans %} [{{ _('bundled') }}]

    • + +
  • +

    Sylpheed Claws, Thunderbird, other MUAs — +{% trans reviews='http://'+i2pconv('hq.postman.i2p')+'/?page_id=9', +smtp='http://'+i2pconv('hq.postman.i2p')+'/?page_id=10', +pop3='http://'+i2pconv('hq.postman.i2p')+'/?page_id=11' -%} +Can be configured to use Postman's email service. See +this comparison of MUAs, +and configuration settings for +SMTP and POP3. +{%- endtrans %} + [{{ _('standalone') }}]

    +

    • {% trans %}File Sharing{% endtrans %}

    @@ -584,7 +597,7 @@ Source code available.
  • -

    {{ i2pconv('perv.i2p') }} — +

    {{ i2pconv('identiguy.i2p') }} — {% trans %}Dynamically updated eepsite index.{% endtrans %} [{{ _('service') }}]

    • @@ -632,6 +645,22 @@ Gateways allowing users on the public Internet to access eepsites. i2p.to — {% trans tino=i2pconv('tino.i2p') -%} tino's inproxy on the public Internet. +{%- endtrans %} + [{{ _('service') }}] + + +
  • + i2p.us — +{% trans -%} +Another inproxy on the public Internet. +{%- endtrans %} + [{{ _('service') }}] +
    • + +
  • + i2p.me — +{% trans -%} +Another inproxy on the public Internet. {%- endtrans %} [{{ _('service') }}]
    • @@ -645,7 +674,7 @@ Gateways allowing I2P users to access content hosted on the public Internet.
    • - {{ i2pconv('false.i2p') }} — + false.i2p — {% trans %}Publicly advertised outproxy running Squid, located in Germany.{% endtrans %} [{{ _('service') }}]
      • diff --git a/i2p2www/pages/site/docs/discussions/ntcp.html b/i2p2www/pages/site/docs/discussions/ntcp.html index 50409695..f5bf132e 100644 --- a/i2p2www/pages/site/docs/discussions/ntcp.html +++ b/i2p2www/pages/site/docs/discussions/ntcp.html @@ -144,10 +144,10 @@ Posted to new Syndie, 2007-03-27

      On the whole, I'm open to experimenting with this, though remember why NTCP is there in the first place - SSU failed in a congestion collapse. NTCP "just -works", and while 2-10% retransmission rates can be handled in normal -single-hop networks, that gives us a 40% retransmission rate with 2 hop +works", and while 2-10% retransmission rates can be handled in normal +single-hop networks, that gives us a 40% retransmission rate with 2 hop tunnels. If you loop in some of the measured SSU retransmission rates we saw -back before NTCP was implemented (10-30+%), that gives us an 83% retransmission +back before NTCP was implemented (10-30+%), that gives us an 83% retransmission rate. Perhaps those rates were caused by the low 10 second timeout, but increasing that much would bite us (remember, multiply by 5 and you've got half the journey). @@ -333,7 +333,7 @@ stream timeout. TCP in practice has retransmission timeouts orders of magnitude less, though yes, can get to 60s on links running through exposed wires or satellite transmissions ;) If we increase the streaming lib retransmission timeout to e.g. 75 seconds, we could go get a beer before a web page loads -(especially assuming less than a 98% reliable transport). That's one reason we +(especially assuming less than a 98% reliable transport). That's one reason we prefer NTCP.

      @@ -399,7 +399,7 @@ more often on NTCP, but maybe that's a hint on why NTCP performs worse. Posted to new Syndie, 2007-03-31

      measured SSU retransmission rates we saw back before NTCP was implemented -(10-30+%) +(10-30+%)

      Can the router itself measure this? If so, could a transport be selected based @@ -463,7 +463,7 @@ while still somewhat bothering to carry TCP streams. On that background, a small diversity of transports (as many as needed, but not more) appears sensible in either case. Which should be the main transport, depends on their performance-wise. I've seen nasty stuff on my line when I -tried to use its full capacity with UDP. Packet losses on the level of 35%. +tried to use its full capacity with UDP. Packet losses on the level of 35%.

      We could definitely try playing with UDP versus TCP priorities, but I'd urge @@ -502,7 +502,7 @@ build messages). On that background, a small diversity of transports (as many as needed, but not more) appears sensible in either case. Which should be the main transport, depends on their performance-wise. I've seen nasty stuff on my line when I -tried to use its full capacity with UDP. Packet losses on the level of 35%. +tried to use its full capacity with UDP. Packet losses on the level of 35%.

      diff --git a/i2p2www/pages/site/docs/discussions/tunnel.html b/i2p2www/pages/site/docs/discussions/tunnel.html index e8a3b5ce..0a172038 100644 --- a/i2p2www/pages/site/docs/discussions/tunnel.html +++ b/i2p2www/pages/site/docs/discussions/tunnel.html @@ -35,7 +35,7 @@ None of these are currently implemented.

      These padding strategies can be used on a variety of levels, addressing the exposure of message size information to different adversaries. After gathering -and reviewing some statistics +and reviewing some statistics from the 0.4 network, as well as exploring the anonymity tradeoffs, we're starting with a fixed tunnel message size of 1024 bytes. Within this however, the fragmented messages themselves are not padded by the tunnel at all (though for end to end @@ -165,7 +165,7 @@ vulnerability to predecessor attacks. While the endpoints and gateways of those tunnels will be randomly distributed across the network (perhaps even including the tunnel creator in that set), another alternative is to use the tunnel pathways themselves to pass along the request and response, as is done -in Tor. This, however, may lead to leaks +in Tor. This, however, may lead to leaks during tunnel creation, allowing peers to discover how many hops there are later on in the tunnel by monitoring the timing or packet count as diff --git a/i2p2www/pages/site/docs/how/cryptography.html b/i2p2www/pages/site/docs/how/cryptography.html index c0bb0602..19a0add8 100644 --- a/i2p2www/pages/site/docs/how/cryptography.html +++ b/i2p2www/pages/site/docs/how/cryptography.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}{% trans %}Low-level Cryptography Details{% endtrans %}{% endblock %} -{% block lastupdated %}{% trans %}March 2012{% endtrans %}{% endblock %} -{% block accuratefor %}0.8.13{% endblock %} +{% block lastupdated %}{% trans %}December 2013{% endtrans %}{% endblock %} +{% block accuratefor %}0.9.9{% endblock %} {% block content %}

      {% trans -%} This page specifies the low-level details of the cryptography in I2P. @@ -47,7 +47,7 @@ AES encrypted payload using that key and IV.

      {% trans -%} The unencrypted ElGamal contains: {%- endtrans %}

      -
      +{% highlight lang='dataspec' %}
    +----+----+----+----+----+----+----+----+
    |nonz|           H(data)                |
    +----+                                  +
@@ -58,9 +58,9 @@ The unencrypted ElGamal contains:
    |                                       |
    +    +----+----+----+----+----+----+----+
    |    |  data...
-   +----+----+----+--//                   
+   +----+----+----+-//
+{% endhighlight %}
 
-

      {% trans -%} The H(data) is the SHA256 of the data that is encrypted in the ElGamal block, and is preceded by a nonzero byte. @@ -77,10 +77,10 @@ Total length: typically 255 bytes. The encrypted ElGamal contains: {%- endtrans %}

      -
      +{% highlight lang='dataspec' %}
    +----+----+----+----+----+----+----+----+
    |  zero padding...       |              |
-   +----+----+----+--// ----+              +
+   +----+----+----+-//-+----+              +
    |                                       |
    +                                       +
    |       ElG encrypted part 1            |
@@ -88,7 +88,7 @@ The encrypted ElGamal contains:
    |                                       |
    +    +----+----+----+----+----+----+----+
    |    |   zero padding...      |         |
-   +----+----+----+----+--// ----+         +
+   +----+----+----+----+-//-+----+         +
    |                                       |
    +                                       +
    |       ElG encrypted part 2            |
@@ -97,8 +97,8 @@ The encrypted ElGamal contains:
    +         +----+----+----+----+----+----+
    |         +
    +----+----+
+{% endhighlight %}
 
-

      {% trans -%} Each encrypted part is prepended with zeros to a size of exactly 257 bytes. Total length: 514 bytes. @@ -108,7 +108,7 @@ This is encoded as two 256-byte encrypted parts, and there is a single byte of zero padding before each part at this layer. {%- endtrans %}

      -

      {% trans url='http://'+i2pconv('trac.i2p2.i2p')+'/browser/core/java/src/net/i2p/crypto/ElGamalEngine.java?rev=85a542c53d910dffbf34cdcefb8a2faeee96adc4' -%} +

      {% trans url='https://github.com/i2p/i2p.i2p/tree/master/core/java/src/net/i2p/crypto/ElGamalEngine.java' -%} See the ElGamal code. {%- endtrans %}

      @@ -139,19 +139,21 @@ or as a hexadecimal value: Using 2 as the generator. {%- endtrans %}

      -

      {% trans %}Short Exponent{% endtrans %}

      -

      {% trans commonstructures=site_url('docs/spec/common-structures'), -pdf='http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.14.5952&rep=rep1&type=pdf', -benchmarks=site_url('misc/benchmarks'), -oldbenchmarks='http://www.eskimo.com/~weidai/benchmarks.html' -%} +

      {% trans %}Short Exponent{% endtrans %}

      +

      {% trans commonstructures=site_url('docs/spec/common-structures') -%} While the standard exponent size is 2048 bits (256 bytes) and the I2P PrivateKey -is a full 256 bytes, +is a full 256 bytes, in some cases we use the short exponent size of 226 bits (28.25 bytes). +{%- endtrans %}

      + +

      {% trans pdf='http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.14.5952&rep=rep1&type=pdf', +benchmarks=site_url('misc/benchmarks'), +oldbenchmarks='http://www.eskimo.com/~weidai/benchmarks.html' -%} This should be safe for use with the Oakley primes, per On Diffie-Hellman Key Agreement with Short Exponents - van Oorschot, Weiner at EuroCrypt 96, and crypto++'s benchmarks. -Benchmarks originally at {{ oldbenchmarks }} (now dead), +Benchmarks originally at this link, now dead, rescued from the wayback machine, dated Apr 23, 2008. {%- endtrans %}

      @@ -164,6 +166,13 @@ Also, Koshiba & Kurosawa: Short Exponent Diffie-Hellman The remainder of the PrivateKey is padded with zeroes. {%- endtrans %}

      +

      {% trans -%} +Prior to release 0.9.8, all routers used the short exponent. +As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent. +Other routers continue to use the short exponent due to concerns about processor load. +The transition to a longer exponent for these platforms is a topic for further study. +{%- endtrans %}

      +

      {% trans %}Obsolescence{% endtrans %}

      {% trans -%} The vulnerability of the network to an ElGamal attack and the impact of transitioning to a longer bit length is to be studied. @@ -198,9 +207,9 @@ For encryption of periodic tunnel test mes

    {% trans rfc2313='http://tools.ietf.org/html/rfc2313', -code1='http://'+i2pconv('trac.i2p2.i2p')+'/browser/core/java/src/net/i2p/crypto/CryptixAESEngine.java?rev=85a542c53d910dffbf34cdcefb8a2faeee96adc4', -code2='http://'+i2pconv('trac.i2p2.i2p')+'/browser/core/java/src/net/i2p/crypto/CryptixRijndael_Algorithm.java?rev=85a542c53d910dffbf34cdcefb8a2faeee96adc4', -code3='http://'+i2pconv('trac.i2p2.i2p')+'/browser/core/java/src/net/i2p/crypto/ElGamalAESEngine.java?rev=85a542c53d910dffbf34cdcefb8a2faeee96adc4' -%} +code1='https://github.com/i2p/i2p.i2p/tree/master/core/java/src/net/i2p/crypto/CryptixAESEngine.java', +code2='https://github.com/i2p/i2p.i2p/tree/master/core/java/src/net/i2p/crypto/CryptixRijndael_Algorithm.java', +code3='https://github.com/i2p/i2p.i2p/tree/master/core/java/src/net/i2p/crypto/ElGamalAESEngine.java' -%} We use AES with 256 bit keys and 128 bit blocks in CBC mode. The padding used is specified in IETF RFC-2313 (PKCS#5 1.5, section 8.1 (for block type 02)). In this case, padding exists of pseudorandomly generated octets to match 16 byte blocks. @@ -277,7 +286,7 @@ It may be quite difficult to make any change backward-compatible.

    DSA

    -

    {% trans code='http://'+i2pconv('trac.i2p2.i2p')+'/browser/core/java/src/net/i2p/crypto/DSAEngine.java?rev=85a542c53d910dffbf34cdcefb8a2faeee96adc4' -%} +

    {% trans code='https://github.com/i2p/i2p.i2p/tree/master/core/java/src/net/i2p/crypto/DSAEngine.java' -%} Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), as implemented in [DSAEngine]. DSA was chosen because it is much faster for signatures than ElGamal. @@ -326,12 +335,12 @@ DSA was chosen because it is much faster for signatures than ElGamal. 

    - C1F4D27D 40093B42 9E962D72 23824E0B BC47E7C8 32A39236
- FC683AF8 48895810 75FF9082 ED32353D 4374D730 1CDA1D23
- C431F469 8599DDA0 2451824F F3697525 93647CC3 DDC197DE
- 985E43D1 36CDCFC6 BD5409CD 2F450821 142A5E6F 8EB1C3AB
- 5D0484B8 129FCF17 BCE4F7F3 3321C3CB 3DBB14A9 05E7B2B3
- E93BE470 8CBCC82
+ 0C1F4D27 D40093B4 29E962D7 223824E0 BBC47E7C 832A3923
+ 6FC683AF 84889581 075FF908 2ED32353 D4374D73 01CDA1D2
+ 3C431F46 98599DDA 02451824 FF369752 593647CC 3DDC197D
+ E985E43D 136CDCFC 6BD5409C D2F45082 1142A5E6 F8EB1C3A
+ B5D0484B 8129FCF1 7BCE4F7F 33321C3C B3DBB14A 905E7B2B
+ 3E93BE47 08CBCC82

    {% trans commonstructures=site_url('docs/spec/common-structures') -%} @@ -374,7 +383,7 @@ It may be quite difficult to make any change backward-compatible.

    SHA256

    -

    {% trans code='http://'+i2pconv('trac.i2p2.i2p')+'/browser/core/java/src/net/i2p/crypto/SHA256Generator.java?rev=85a542c53d910dffbf34cdcefb8a2faeee96adc4' -%} +

    {% trans code='https://github.com/i2p/i2p.i2p/tree/master/core/java/src/net/i2p/crypto/SHA256Generator.java' -%} Hashes within I2P are plain old SHA256, as implemented in [SHA256Generator] {%- endtrans %}

    diff --git a/i2p2www/pages/site/docs/how/elgamal-aes.html b/i2p2www/pages/site/docs/how/elgamal-aes.html index ec84bc47..9c44a9c3 100644 --- a/i2p2www/pages/site/docs/how/elgamal-aes.html +++ b/i2p2www/pages/site/docs/how/elgamal-aes.html @@ -103,7 +103,7 @@ and an encrypted AES block.

    {% trans -%} The encrypted message contains: {%- endtrans %}

    -
    +{% highlight lang='dataspec' %}
    +----+----+----+----+----+----+----+----+
    |                                       |
    +                                       +
@@ -121,8 +121,8 @@ The encrypted message contains:
    +         +----+----+----+----+----+----+
    |         +
    +----+----+
+{% endhighlight %}
 
-

    {% trans %}ElGamal Block{% endtrans %}

    {% trans -%} @@ -132,7 +132,7 @@ The encrypted ElGamal Block is always 514 bytes long.

    {% trans -%} The unencrypted ElGamal data is 222 bytes long, containing: {%- endtrans %}

    -
    +{% highlight lang='dataspec' %}
    +----+----+----+----+----+----+----+----+
    |                                       |
    +                                       +
@@ -159,7 +159,7 @@ The unencrypted ElGamal data is 222 bytes long, containing:
    +                             +----+----+
    |                             |
    +----+----+----+----+----+----+
-
    +{% endhighlight %}

    {% trans commonstructures=site_url('docs/spec/common-structures') -%} The 32-byte diff --git a/i2p2www/pages/site/docs/how/network-database.html b/i2p2www/pages/site/docs/how/network-database.html index c9c9dad6..6eb6b83b 100644 --- a/i2p2www/pages/site/docs/how/network-database.html +++ b/i2p2www/pages/site/docs/how/network-database.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}{% trans %}The Network Database{% endtrans %}{% endblock %} -{% block lastupdated %}{% trans %}June 2013{% endtrans %}{% endblock %} -{% block accuratefor %}0.9.6{% endblock %} +{% block lastupdated %}{% trans %}October 2013{% endtrans %}{% endblock %} +{% block accuratefor %}0.9.9{% endblock %} {% block content %}

    {% trans %}Overview{% endtrans %}

    @@ -43,6 +43,20 @@ to be present:
    • caps ({% trans %}Capabilities flags - used to indicate floodfill participation, approximate bandwidth, and perceived reachability{% endtrans %}) +
        +
      • B: {% trans %}SSU Testing{% endtrans %}
        • +
      • C: {% trans %}SSU Introducer{% endtrans %}
        • +
      • f: {% trans %}Floodfill{% endtrans %}
        • +
      • H: {% trans %}Hidden{% endtrans %}
        • +
      • K: {% trans amount='12KBps' %}Under {{amount }} shared bandwidth{% endtrans %}
        • +
      • L: {% trans amount='12 - 32KBps' %}{{ amount }} shared bandwidth{% endtrans %} ({% trans %}default{% endtrans %})
        • +
      • M: {% trans amount='32 - 64KBps' %}{{ amount }} shared bandwidth{% endtrans %}
        • +
      • N: {% trans amount='64 - 128KBps' %}{{ amount }} shared bandwidth{% endtrans %}
        • +
      • O: {% trans amount='128KBps' %}Over {{ amount }} shared bandwidth{% endtrans %}
        • +
      • R: {% trans %}Reachable{% endtrans %}
        • +
      • U: {% trans %}Unreachable{% endtrans %}
        • +
      +"Shared bandwidth" == (share %) * min(in bw, out bw)
    • coreVersion ({% trans %}The core library version, always the same as the router version{% endtrans %}) @@ -279,7 +293,7 @@ automatically enabled. {%- endtrans %}

      {% trans -%} -With the current rules for automatic opt-in, approximately 6% of +With the current rules for automatic opt-in, approximately 6% of the routers in the network are floodfill routers. {%- endtrans %}

      @@ -398,11 +412,11 @@ This message is sent back to one of the client's inbound tunnels.

      {% trans %}Flooding{% endtrans %}

      -

      {% trans -%} +

      {% trans floodsize=3 -%} After a floodfill router receives a DatabaseStoreMessage containing a valid RouterInfo or LeaseSet which is newer than that previously stored in its local NetDb, it "floods" it. -To flood a NetDb entry, it looks up several (currently 4) floodfill routers closest to the routing key +To flood a NetDb entry, it looks up several (currently {{ floodsize }}) floodfill routers closest to the routing key of the NetDb entry. (The routing key is the SHA256 Hash of the RouterIdentity or Destination with the date (yyyyMMdd) appended.) By flooding to those closest to the key, not closest to itself, the floodfill ensures that the storage gets to the right place, even if the storing router did not have good knowledge of the @@ -489,6 +503,13 @@ Given the current size of the network, a router has

      {% trans %}RouterInfo Storage Verification{% endtrans %}

      +

      {% trans egger2013='http://wwwcip.informatik.uni-erlangen.de/~spjsschl/i2p.pdf' -%} +Note: RouterInfo verification is disabled as of release 0.9.7.1 to prevent +the attack described in the paper +Practical Attacks Against the I2P Network. +It is not clear if verification can be redesigned to be done safely. +{%- endtrans %}

      +

      {% trans -%} To verify a storage was successful, a router simply waits about 10 seconds, then sends a lookup to another floodfill router close to the key @@ -567,16 +588,16 @@ Some scenarios are discussed below. {%- endtrans %}

      {% trans %}General Mitigation Through Growth{% endtrans %}

      -

      {% trans -%} -There are currently hundreds of floodfill routers in the network. +

      {% trans ffcount=600 -%} +There are currently around {{ ffcount }} floodfill routers in the network. Most of the following attacks will become more difficult, or have less impact, as the network size and number of floodfill routers increase. {%- endtrans %}

      {% trans %}General Mitigation Through Redundancy{% endtrans %}

      -

      {% trans -%} -Via flooding, all netdb entries are stored on the 8 floodfill routers closest to the key. +

      {% trans floodsize=3 -%} +Via flooding, all netdb entries are stored on the {{ floodsize }} floodfill routers closest to the key. {%- endtrans %}

      @@ -706,15 +727,6 @@ The extent of the issue, and methods for mitigation are a topic for further study. {%- endtrans %}

      -

      {% trans -%} -One consequence of daily keyspace rotation is that the distributed network database -may become unreliable for a few minutes after the rotation -- -lookups will fail because the new "closest" router has not received a store yet. -The extent of the issue, and methods for mitigation -(for example netdb "handoffs" at midnight) -are a topic for further study. -{%- endtrans %}

      -

      {% trans %}Bootstrap Attacks{% endtrans %}

      {% trans -%} @@ -819,7 +831,7 @@ more correlative. Of course, a larger network makes a Sybil attack that much har

      {% trans threatmodel=site_url('docs/how/threat-model') -%} However, the general issue of DHT information leakage in I2P needs further investigation. The floodfill routers are in a position to observe queries and gather information. -Certainly, at a level of f = 0.2 (20% malicious nodes, as specifed in the paper) +Certainly, at a level of f = 0.2 (20% malicious nodes, as specifed in the paper) we expect that many of the Sybil threats we describe (here, here and diff --git a/i2p2www/pages/site/docs/how/peer-selection.html b/i2p2www/pages/site/docs/how/peer-selection.html index fd26f061..d562e0b8 100644 --- a/i2p2www/pages/site/docs/how/peer-selection.html +++ b/i2p2www/pages/site/docs/how/peer-selection.html @@ -55,7 +55,7 @@ of client and exploratory tunnels, and a tunnel lifetime is only 10 minutes.

      {% trans %}Further Information{% endtrans %}

      {% trans pdf=url_for('static', filename='pdf/I2P-PET-CON-2009.1.pdf'), -url='http://www.pet-con.org/index.php/PET_Convention_2009.1' -%} +url='http://web.archive.org/web/20100413184504/http://www.pet-con.org/index.php/PET_Convention_2009.1' -%} For more information see the paper Peer Profiling and Selection in the I2P Anonymous Network presented at PET-CON 2009.1. @@ -237,7 +237,7 @@ To prevent some simple attacks, and for performance, there are the following res Two peers from the same /16 IP space may not be in the same tunnel. {%- endtrans %}

    • {% trans -%} -A peer may participate in a maximum of 33% of all tunnels created by the router. +A peer may participate in a maximum of 33% of all tunnels created by the router. {%- endtrans %}
    • {% trans -%} Peers with extremely low bandwidth are not used. diff --git a/i2p2www/pages/site/docs/how/tech-intro.html b/i2p2www/pages/site/docs/how/tech-intro.html index aa7fdc9e..230bfa78 100644 --- a/i2p2www/pages/site/docs/how/tech-intro.html +++ b/i2p2www/pages/site/docs/how/tech-intro.html @@ -681,7 +681,7 @@ See also the Network Comparisons Page. {%- endtrans %}

      Tor

      -

      {% trans %}website{% endtrans %}

      +

      {% trans %}website{% endtrans %}

      {% trans -%} At first glance, Tor and I2P have many functional and anonymity related @@ -1004,9 +1004,9 @@ It is hosted on http://{{ bob }}/Robert.h

      PyBit

      {% trans dev='Blub' -%}Developed by: {{ dev }}{%- endtrans %}

      -

      {% trans pebcache=i2pconv('pebcache.i2p') -%} +

      {% trans pybit='http://'+i2pconv('echelon.i2p')+'/pybit/' -%} PyBit is a Bittorrent client written in Python. -It is hosted on http://{{ pebcache }}/ +It is hosted on {{ pybit }} {%- endtrans %}

      I2Phex

      diff --git a/i2p2www/pages/site/docs/how/threat-model.html b/i2p2www/pages/site/docs/how/threat-model.html index 33f1cd35..e1e2db5f 100644 --- a/i2p2www/pages/site/docs/how/threat-model.html +++ b/i2p2www/pages/site/docs/how/threat-model.html @@ -2,6 +2,45 @@ {% block title %}{% trans %}I2P's Threat Model{% endtrans %}{% endblock %} {% block lastupdated %}{% trans %}November 2010{% endtrans %}{% endblock %} {% block accuratefor %}0.8.1{% endblock %} + +{% macro get_level(num) %} +{%- if num == 1 %}{{ _('low') }} +{%- elif num == 2 %}{{ _('medium') }} +{%- elif num == 3 %}{{ _('high') }} +{%- else %}ERR_INVALID +{%- endif %} +{%- endmacro %} + +{% macro calculate_severity(Da, R, A) %} +{%- if R + A > 4 %}{{ caller(Da + 2) }} +{%- elif R + A > 3 %}{{ caller(Da + 1) }} +{%- else %}{{ caller(Da) }} +{%- endif %} +{%- endmacro %} + +{% macro calculate_priority(Da, R, E, A, Di) %} +{%- call(severity) calculate_severity(Da, R, A) %} +{%- if E == 3 and Di == 3 %}{{ severity + 4 }} +{%- elif (E == 3 and Di == 2) or ( E == 2 and Di == 3) %}{{ severity + 3}} +{%- elif (E == 3 and Di == 1) or ( E == 1 and Di == 3) %}{{ severity + 2}} +{%- elif E == 2 and Di == 2 %}{{ severity + 1}} +{%- else %}{{ severity }} +{%- endif %} +{%- endcall %} +{%- endmacro %} + +{% macro DREAD_score(Da, R, E, A, Di) %} +
        +
      • {{ _('Damage Potential') }}: {{ get_level(Da) }}
        • +
      • {{ _('Reliability') }}: {{ get_level(R) }}
        • +
      • {{ _('Exploitability') }}: {{ get_level(E) }}
        • +
      • {{ _('Affected Users') }}: {{ get_level(A) }}
        • +
      • {{ _('Discoverability') }}: {{ get_level(Di) }}
        • +
      • {{ _('Severity') }}: {% call(S) calculate_severity(Da, R, A) %}{{ S }}{% endcall %}/5
        • +
      • {{ _('Priority') }}: {{ calculate_priority(Da, R, E, A, Di) }}/9
        • +
      +{% endmacro %} + {% block content %}

      {% trans %}What do we mean by "anonymous"?{% endtrans %}

      @@ -75,12 +114,12 @@ the current implementation does not. {%- endtrans %}

      -

      {% trans %}The Threat Model (Attacks){% endtrans %}

      +

      {% trans %}The Threat Model{% endtrans %}

      {% trans -%} I2P design started in 2003, not long after the advent of [Onion Routing], [Freenet], and -[Tor]. +[Tor]. Our design benefits substantially from the research published around that time. I2P uses several onion routing techniques, so we continue to benefit from the significant academic interest in Tor. @@ -118,7 +157,29 @@ The to review. {%- endtrans %}

      -

      {% trans %}Index{% endtrans %}

      +{# Hide DREAD ratings until we know how we want to use them + +

      {% trans DREAD='https://blogs.msdn.com/b/david_leblanc/archive/2007/08/13/dreadful.aspx' -%} +Attacks are judged using the modified DREAD model: +{%- endtrans %}

      + +
        +
      • {{ _('Damage Potential') }}: {% trans %}If a threat exploit occurs, how much damage will be caused?{% endtrans %}
        • +
      • {{ _('Reliability') }}: {% trans %}How reliable is the attack?{% endtrans %}
        • +
      • {{ _('Exploitability') }}: {% trans %}What is needed to exploit this threat?{% endtrans %}
        • +
      • {{ _('Affected Users') }}: {% trans %}How many users will be affected?{% endtrans %}
        • +
      • {{ _('Discoverability') }}: {% trans %}How easy is it to discover this threat?{% endtrans %}
        • +
      + +

      {% trans DREAD='https://blogs.msdn.com/b/david_leblanc/archive/2007/08/13/dreadful.aspx' -%} +Each category is given a rating of low, medium or high. The severity +and priority scores are calculated using the equations outlined +here. +{%- endtrans %}

      + +#} + +

      {% trans %}Index of Attacks{% endtrans %}

      • {% trans %}Brute force attacks{% endtrans %}
      • {% trans %}Timing attacks{% endtrans %}
        • @@ -142,6 +203,8 @@ to review.

        {% trans %}Brute force attacks{% endtrans %}

        +{# DREAD_score(2, 1, 1, 1, 3) #} +

        {% trans -%} A brute force attack can be mounted by a global passive or active adversary, watching all the messages pass between all of the nodes and attempting to correlate @@ -184,6 +247,8 @@ are discussed on the

        {% trans %}Timing attacks{% endtrans %}

        +{# DREAD_score(2, 2, 2, 3, 2) #} +

        {% trans -%} I2P's messages are unidirectional and do not necessarily imply that a reply will be sent. However, applications on top of I2P will most likely have @@ -219,6 +284,8 @@ References: Low-Resource Routing Attacks Against Anonymous S

        {% trans %}Intersection attacks{% endtrans %}

        +{# DREAD_score(3, 2, 2, 3, 3) #} +

        {% trans -%} Intersection attacks against low latency systems are extremely powerful - periodically make contact with the target and keep track of what peers are on @@ -301,18 +368,19 @@ Reference: One Cell Enough There are a whole slew of denial of service attacks available against I2P, each with different costs and consequences: {%- endtrans %}

        -
          -
        • {% trans -%} + +{# DREAD_score(1, 1, 2, 1, 3) #} +

          {% trans -%} Greedy user attack: This is simply people trying to consume significantly more resources than they are willing to contribute. The defense against this is: -{%- endtrans %} +{%- endtrans %}

          • {% trans comparisons=site_url('comparison') -%} Set defaults so that most users provide resources to the network. In I2P, users route traffic by default. In sharp distinction to other networks, -over 95% of I2P users relay traffic for others. +over 95% of I2P users relay traffic for others. {%- endtrans %}
          • {% trans -%} Provide easy configuration options so that users may increase their @@ -323,8 +391,10 @@ metrics such as "share ratio" so that users may see what they are contributing. Maintain a strong community with blogs, forums, IRC, and other means of communication. {%- endtrans %}
          -
          • -
        • {% trans peerselection=site_url('docs/how/peer-selection') -%} +
          + +{# DREAD_score(2, 1, 1, 2, 3) #} +

          {% trans peerselection=site_url('docs/how/peer-selection') -%} Starvation attack: A hostile user may attempt to harm the network by creating a significant number of peers in the network who are not identified as being under control of the same entity (as with Sybil). These nodes then @@ -340,8 +410,11 @@ them, or using them rarely. We have significantly enhanced the ability to recognize and avoid troublesome peers; however there are still significant efforts required in this area. -{%- endtrans %}

          • -
        • {% trans todo=site_url('get-involved/todo') -%} +{%- endtrans %}

          +
          + +{# DREAD_score(1, 2, 2, 2, 3) #} +

          {% trans todo=site_url('get-involved/todo') -%} Flooding attack: A hostile user may attempt to flood the network, a peer, a destination, or a tunnel. Network and peer flooding is possible, and I2P does nothing to prevent standard IP layer flooding. The flooding of @@ -356,8 +429,11 @@ larger load. If, on the other hand, the load is more than the client can deal with, they can instruct the tunnels to throttle the number of messages or bytes they should pass on (once the advanced tunnel operation is implemented). -{%- endtrans %}

          • -
        • {% trans -%} +{%- endtrans %}

          +
          + +{# DREAD_score(1, 1, 1, 1, 1) #} +

          {% trans -%} CPU load attack: There are currently some methods for people to remotely request that a peer perform some cryptographically expensive operation, and a hostile attacker could use these to flood that peer with @@ -366,8 +442,11 @@ engineering practices and potentially requiring nontrivial certificates (e.g. HashCash) to be attached to these expensive requests should mitigate the issue, though there may be room for an attacker to exploit various bugs in the implementation. -{%- endtrans %}

          • -
        • {% trans peerselection=site_url('docs/how/peer-selection'), +{%- endtrans %}

          +
          + +{# DREAD_score(2, 2, 3, 2, 3) #} +

          {% trans peerselection=site_url('docs/how/peer-selection'), netdb=site_url('docs/how/network-database') -%} Floodfill DOS attack: A hostile user may attempt to harm the network by becoming a floodfill router. The current defenses against unreliable, @@ -379,10 +458,13 @@ Some defenses and however there is much more to do. For more information see the network database page. -{%- endtrans %}

          • -
        +{%- endtrans %}

        +

        {% trans %}Tagging attacks{% endtrans %}

        + +{# DREAD_score(1, 3, 1, 1, 1) #} +

        {% trans todo=site_url('get-involved/todo') -%} Tagging attacks - modifying a message so that it can later be identified further along the path - are by themselves impossible in I2P, as messages @@ -399,6 +481,8 @@ as the links are encrypted and messages signed.

        {% trans %}Partitioning attacks{% endtrans %}

        +{# DREAD_score(3, 1, 1, 1, 2) #} +

        {% trans -%} Partitioning attacks - finding ways to segregate (technically or analytically) the peers in a network - are important to keep in mind when dealing with a @@ -437,6 +521,8 @@ Also discussed on the network database page (bo

        {% trans %}Predecessor attacks{% endtrans %}

        +{# DREAD_score(1, 1, 1, 1, 3) #} +

        {% trans -%} The predecessor attack is passively gathering statistics in an attempt to see what peers are 'close' to the destination by participating in their tunnels and @@ -479,6 +565,9 @@ which is an update to the 2004 predecessor attack paper

        {% trans %}Harvesting attacks{% endtrans %}

        + +{# DREAD_score(1, 1, 2, 2, 3) #} +

        {% trans -%} "Harvesting" means compiling a list of users running I2P. It can be used for legal attacks and to help @@ -523,6 +612,9 @@ enact other restricted route methods.

        {% trans %}Identification Through Traffic Analysis{% endtrans %}

        + +{# DREAD_score(1, 1, 2, 3, 3) #} +

        {% trans transport=site_url('docs/transport') -%} By inspecting the traffic into and out of a router, a malicious ISP or state-level firewall could identify that a computer is running I2P. @@ -574,18 +666,20 @@ Working directly with DPI and obfuscation experts {%- endtrans %}

      -

      {% trans pdf='http://www.cse.chalmers.se/%7Ejohnwolf/publications/hjelmvik_breaking.pdf' -%} +

      {% trans pdf='http://www.iis.se/docs/hjelmvik_breaking.pdf' -%} Reference: Breaking and Improving Protocol Obfuscation {%- endtrans %}

      {% trans %}Sybil attacks{% endtrans %}

      +{# DREAD_score(3, 2, 1, 3, 3) #} +

      {% trans -%} Sybil describes a category of attacks where the adversary creates arbitrarily large numbers of colluding nodes and uses the increased numbers to help mounting other attacks. For instance, if an attacker is in a network where peers -are selected randomly and they want an 80% chance to be one of those peers, they +are selected randomly and they want an 80% chance to be one of those peers, they simply create five times the number of nodes that are in the network and roll the dice. When identity is free, Sybil can be a very potent technique for a powerful adversary. The primary technique to address this is simply to make @@ -627,6 +721,9 @@ for more Sybil discussion.

      {% trans %}Buddy Exhaustion attacks{% endtrans %}

      + +{# DREAD_score(3, 2, 2, 1, 3) #} +

      {% trans pdf='http://www.eecs.berkeley.edu/~pmittal/publications/nisan-torsk-ccs10.pdf' -%} (Reference: In Search of an Anonymouns and Secure Lookup Section 5.2) {%- endtrans %}

      @@ -640,7 +737,7 @@ This is somewhat mitigated by our peer profiling methods used to monitor the performance of peers. However, this is a powerful attack as the number of routers approaches -f = 0.2, or 20% malicious nodes, as specifed in the paper. +f = 0.2, or 20% malicious nodes, as specifed in the paper. The malicous routers could also maintain connections to the target router and provide excellent forwarding bandwidth for traffic over those connections, in an attempt to manipulate the profiles managed by the target and appear attractive. @@ -650,6 +747,8 @@ Further research and defenses may be necessary.

      {% trans %}Cryptographic attacks{% endtrans %}

      +{# DREAD_score(3, 2, 1, 3, 1) #} +

      {% trans cryptography=site_url('docs/how/cryptography') -%} We use strong cryptography with long keys, and we assume the security of the industry-standard cryptographic primitives used in I2P, as documented @@ -689,6 +788,9 @@ end to end messages include simple random padding.

      {% trans %}Floodfill Anonymity attacks{% endtrans %}

      + +{# DREAD_score(3, 2, 1, 2, 2) #} +

      {% trans netdb=site_url('docs/how/network-database') -%} In addition to the floodfill DOS attacks described above, floodfill routers are uniquely positioned @@ -716,6 +818,9 @@ Several scenarios are discussed on the

      {% trans %}Central Resource Attacks{% endtrans %}

      + +{# DREAD_score(1, 1, 1, 3, 3) #} +

      {% trans -%} There are a few centralized or limited resources (some inside I2P, some not) that could be attacked or used as a vector for attacks. @@ -769,6 +874,8 @@ and would shrink the network (in the short-to-medium term), just as the loss of

      {% trans %}Development attacks{% endtrans %}

      +{# DREAD_score(2, 1, 1, 3, 1) #} +

      {% trans -%} These attacks aren't directly on the network, but instead go after its development team by either introducing legal hurdles on anyone contributing to the development @@ -807,6 +914,9 @@ should any defense be necessary. {%- endtrans %}

      {% trans %}Implementation attacks (bugs){% endtrans %}

      + +{# DREAD_score(2, 2, 1, 3, 1) #} +

      {% trans -%} Try as we might, most nontrivial applications include errors in the design or implementation, and I2P is no exception. There may be bugs that could be exploited to diff --git a/i2p2www/pages/site/docs/index.html b/i2p2www/pages/site/docs/index.html index 3a95ba2f..e176b8cc 100644 --- a/i2p2www/pages/site/docs/index.html +++ b/i2p2www/pages/site/docs/index.html @@ -16,10 +16,10 @@ the lower layers are inside the router itself. The interface between applications and the router is the I2CP (I2P Control Protocol) API. {%- endtrans %}

      -

      {% trans trac=i2pconv('trac.i2p2.i2p') -%} +

      {% trans trac='https://trac.i2p2.de/report/1' -%} The I2P Project is committed to maintaining accurate, current documentation. If you find any inaccuracies in the documents linked below, please -enter a ticket identifying the problem. +enter a ticket identifying the problem. {%- endtrans %}

      {% trans %}Index to Technical Documentation{% endtrans %}

      @@ -220,9 +220,9 @@ Traditionally used only by Java applications and higher-level APIs.
    • {{ _('Developer forum inside I2P') }}
    • -{{ _('Bug tracker') }} +{{ _('Bug tracker') }}
    • -{{ _('Viewmtn inside I2P') }}. +{{ _('Viewmtn inside I2P') }}.
    • {{ _('I2P Source exported to GitHub') }}
    • @@ -230,11 +230,13 @@ Traditionally used only by Java applications and higher-level APIs.
    • {{ _('Source translation at Transifex') }}
    • -{{ _('Roadmap wiki') }} +{{ _('Roadmap wiki') }}
    • {{ _('Old roadmap') }} ({{ _('not current') }})
    • {{ _('To Do List') }} ({{ _('not current') }}) +
    • +Ancient invisiblenet I2P documents (2003)
    diff --git a/i2p2www/pages/site/docs/naming.html b/i2p2www/pages/site/docs/naming.html index 405320df..7e3ff247 100644 --- a/i2p2www/pages/site/docs/naming.html +++ b/i2p2www/pages/site/docs/naming.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}{% trans %}Naming and Addressbook{% endtrans %}{% endblock %} -{% block lastupdated %}{% trans %}March 2012{% endtrans %}{% endblock %} -{% block accuratefor %}0.8.13{% endblock %} +{% block lastupdated %}{% trans %}December 2013{% endtrans %}{% endblock %} +{% block accuratefor %}0.9.9{% endblock %} {% block content %}

    {% trans %}Naming in I2P{% endtrans %}

    {% trans %}Overview{% endtrans %}

    @@ -50,8 +50,8 @@ The components are:
    1. {% trans -%} -The client application which does local lookups in hosts.txt -and also takes care of the Base32 hostnames. +The local naming service which does lookups +and also handles Base32 hostnames. {%- endtrans %}
    2. {% trans -%} The HTTP proxy which asks the router for lookups and points @@ -74,7 +74,7 @@ for addressbook configuration and viewing of the local host lists.
    -

    {% trans %}Naming Files and Lookups{% endtrans %}

    +

    {{ _('Naming Services') }}

    {% trans namingdiscussion=site_url('docs/discussions/naming'), todo=site_url('get-involved/todo') -%} All destinations in I2P are 516-byte (or longer) keys. @@ -89,38 +89,92 @@ One possible use of certificates is for proof of w If an application (i2ptunnel or the HTTP proxy) wishes to access a destination by name, the router does a very simple local lookup to resolve that name. -The client application (technically, the client side of I2CP in the I2P API) -does a linear search through three local files, in order, to -look up host names and convert them to a 516-byte destination key: {%- endtrans %}

    +

    {{ _('Hosts.txt Naming Service') }}

    + +

    {% trans -%} +The hosts.txt Naming Service does a simple linear search through +text files. This naming service was the default until +release 0.8.8 when it was replaced by the Blockfile Naming Service. +The hosts.txt format had become too slow after the file grew to thousands of entries. +{%- endtrans %}

    + +

    {% trans configuration=site_url('docs/spec/configuration') -%} +It does a linear search through three local files, in order, to +look up host names and convert them to a 516-byte destination key. +Each file is in a simple configuration file format, with hostname=base64, one per line. +The files are: +{%- endtrans %}

    1. privatehosts.txt
    2. userhosts.txt
    3. hosts.txt
    +

    {{ _('Blockfile Naming Service') }}

    +

    {% trans -%} +The Blockfile Naming Service stores multiple "addressbooks" in a single +database file named hostsdb.blockfile. +This Naming Service is the default since release 0.8.8. +{%- endtrans %}

    + +

    {% trans blockfile=site_url('docs/spec/blockfile') -%} +A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs), +implemented as skiplists. +The blockfile format is specified on the Blockfile page. +It provides fast Destination lookup in a compact format. While the blockfile overhead is substantial, +the destinations are stored in binary rather than in Base 64 as in the hosts.txt format. +In addition, the blockfile provides the capability of arbitrary metadata storage +(such as added date, source, and comments) for each entry to implement advanced addressbook features. +The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides +approximately 10x reduction in lookup times. +{%- endtrans %}

    + +

    {% trans -%} +On creation, the naming service imports entries from the three files used by the hosts.txt Naming Service. +The blockfile mimics the previous implementation by maintaining three maps that +are searched in-order, named privatehosts.txt, userhosts.txt, and hosts.txt. +It also maintains a reverse-lookup map to implement rapid reverse lookups. +{%- endtrans %}

    + +

    {{ _('Other Naming Service Facilities') }}

    + +

    {% trans nsjavadocs='http://docs.i2p-projekt.de/javadoc/net/i2p/client/naming/package-summary.html' -%} The lookup is case-insensitive. The first match is used, and conflicts are not detected. There is no enforcement of naming rules in lookups. +Lookups are cached for a few minutes. +Base 32 resolution is described below. +For a full description of the Naming Service API see the +Naming Service Javadocs. +This API was significantly expanded in release 0.8.7 to provide +adds and removes, storage of arbitrary properties with the hostname, +and other features. {%- endtrans %}

    +

    {{ _('Alternatives and Experimental Naming Services') }}

    +

    {% trans namingdiscussion=site_url('docs/discussions/naming') -%} -Lookups are cached for a few minutes. -There is an experimental facility for real-time lookups (a la DNS) over the network within the router, -although it is not enabled by default -(see "EepGet" under Alternatives on the discussion page). +The naming service is specified with the configuration property i2p.naming.impl=class. +Other implementations are possible. For example, +there is an experimental facility for real-time lookups (a la DNS) over the network within the router. +For more information see the alternatives on the discussion page. {%- endtrans %}

    -

    {% trans %}HTTP Proxy{% endtrans %}

    -

    {% trans -%} The HTTP proxy does a lookup via the router for all hostnames ending in '.i2p'. Otherwise, it forwards the request to a configured HTTP outproxy. Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-Top Level Domain '.i2p'. {%- endtrans %}

    +

    {% trans i2ptld='https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/', +rfc6761='http://tools.ietf.org/html/rfc6761' -%} +We have applied to reserve the .i2p TLD +following the procedures specified in RFC 6761. +{%- endtrans %}

    +

    {% trans -%} If the router fails to resolve the hostname, the HTTP proxy returns an error page to the user with links to several "jump" services. @@ -221,7 +275,7 @@ Must not contain '--' except in 'xn--' for IDN. {%- endtrans %}

  • {% trans -%} -Base32 hostnames (*.b32.i2p) are not allowed. +Base32 hostnames (*.b32.i2p) are reserved for base 32 use and so are not allowed to be imported. {%- endtrans %}
  • {% trans -%} @@ -247,7 +301,7 @@ Maximum key length 616 bytes (to account for certs up to 100 bytes).

    {% trans -%} -Any name received via subscription that passes all the checks is added to the local hosts.txt. +Any name received via subscription that passes all the checks is added via the local naming service. {%- endtrans %}

    {% trans -%} @@ -408,6 +462,9 @@ Example: ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2pproposal +to convert to an identical format of {52 chars}.onion for their hidden services. Base32 is implemented in the naming service, which queries the router over I2CP to lookup the LeaseSet to get the full Destination. Base32 lookups will only be successful when the Destination is up and publishing diff --git a/i2p2www/pages/site/docs/plugins.html b/i2p2www/pages/site/docs/plugins.html index 0f913c1f..562c1420 100644 --- a/i2p2www/pages/site/docs/plugins.html +++ b/i2p2www/pages/site/docs/plugins.html @@ -137,7 +137,7 @@ or easily add some feature. {%- endtrans %}

    {% trans %}Getting Started{% endtrans %}

    -

    {% trans url='http://'+i2pconv('trac.i2p2.i2p')+'/browser/plugin/makeplugin.sh?rev=776519571fda0689ef09c42f66e7398f30432e87' -%} +

    {% trans url='https://github.com/i2p/i2p.scripts/tree/master/plugin/makeplugin.sh' -%} To create a plugin from an existing binary package you will need to get makeplugin.sh from the i2p.scripts branch in monotone. {%- endtrans %}

    diff --git a/i2p2www/pages/site/docs/ports.html b/i2p2www/pages/site/docs/ports.html index 0c92f137..4c462dd2 100644 --- a/i2p2www/pages/site/docs/ports.html +++ b/i2p2www/pages/site/docs/ports.html @@ -54,6 +54,7 @@ in the 766x range.
    • + diff --git a/i2p2www/pages/site/docs/protocol/i2cp.html b/i2p2www/pages/site/docs/protocol/i2cp.html index 00f4eb96..842a13c4 100644 --- a/i2p2www/pages/site/docs/protocol/i2cp.html +++ b/i2p2www/pages/site/docs/protocol/i2cp.html @@ -1,33 +1,31 @@ {% extends "global/layout.html" %} {% block title %}I2CP{% endblock %} -{% block lastupdated %}{% trans %}November 2012{% endtrans %}{% endblock %} -{% block accuratefor %}0.9.3{% endblock %} +{% block lastupdated %}{% trans %}December 2013{% endtrans %}{% endblock %} +{% block accuratefor %}0.9.9{% endblock %} {% block content %}

    {% trans -%} The I2P Client Protocol (I2CP) exposes a strong separation of concerns between the router and any client that wishes to communicate over the network. It enables secure and asynchronous messaging by sending and receiving messages over a -single TCP socket, yet never exposing any private keys and authenticating itself -to the router only through signatures. With I2CP, a client application tells the +single TCP socket. +With I2CP, a client application tells the router who they are (their "destination"), what anonymity, reliability, and latency tradeoffs to make, and where to send messages. In turn the router uses I2CP to tell the client when any messages have arrived, and to request authorization for some tunnels to be used. {%- endtrans %}

    -

    {% trans url='http://docs.i2p-projekt.de/javadoc/net/i2p/client/package-summary.html' -%} -The protocol itself has only been implemented in Java, to provide the +

    {% trans url='http://docs.i2p-projekt.de/javadoc/net/i2p/client/package-summary.html', +libi2cp='http://git.repo.i2p/w/libi2cp.git', +streaming=site_url('docs/api/streaming') -%} +The protocol itself is implemented in Java, to provide the Client SDK. This SDK is exposed in the i2p.jar package, which implements the client-side of I2CP. Clients should never need to access the router.jar package, which contains the router itself and the router-side of I2CP. -{%- endtrans %}

    - -

    {% trans streaming=site_url('docs/api/streaming') -%} -While implementing the client side of I2CP in a non-Java language is certainly feasible, -a non-Java client would also have to implement the +There is also a C library implementation. +A non-Java client would also have to implement the streaming library for TCP-style connections. -Together, implementing I2CP and the streaming library would be a sizable task. {%- endtrans %}

    {% trans streaming=site_url('docs/api/streaming'), datagrams=site_url('docs/spec/datagrams'), @@ -64,6 +62,16 @@ Clients in the same JVM as the router pass messages directly to the router through an internal JVM interface. {%- endtrans %}

    +

    {% trans commonstructures=site_url('docs/spec/common-structures') -%} +The router also supports external connections over SSL. +While SSL is not the default, it is strongly recommended for any traffic that may +be exposed to the open Internet. The authorization user/password (if any), the +Private Key and +Signing Private Key for the +Destination +are all transmitted in-the-clear unless SSL is enabled. +{%- endtrans %}

    +

    {% trans %}I2CP Protocol Specification{% endtrans %}

    {% trans i2cp=site_url('docs/spec/i2cp') -%} Now on the I2CP Specification page. @@ -310,9 +318,11 @@ of sending a MessageStatus and awaiting a ReceiveMessageBegin.

    @@ -322,10 +332,6 @@ If the client is running in the same JVM as a router, this option is not require @@ -416,10 +422,12 @@ in the "unknown options" properties of the outbound tunnel pool's settings. Note: Large quantity, length, or variance settings may cause significant performance or reliability problems. {%- endtrans %}

    -

    {% trans -%} +

    {% trans commonstructures=site_url('docs/spec/common-structures') -%} Note: As of release 0.7.7, option names and values must use UTF-8 encoding. This is primarily useful for nicknames. Prior to that release, options with multi-byte characters were corrupted. +Since options are encoded in a Mapping, +all option names and values are limited to 255 bytes (not characters) maximum. {%- endtrans %}

    {% trans -%} @@ -645,21 +653,14 @@ specified by RFC 1952.

    {% trans %}Future Work{% endtrans %}

      -
    • {% trans -%} -Implement I2CP and the streaming library in another programming language. -{%- endtrans %}
      • - -
    • {% trans -%} -Is the initial Get Date / Set Date handshake required? -{%- endtrans %}
      • -
    • {% trans -%} The current authorization mechanism could be modified to use hashed passwords. {%- endtrans %}
    • {% trans -%} -Private Keys are included in the Create Lease Set message, -are they really required? Revocation is unimplemented. +The Signing Private Keys is included in the Create Lease Set message, +it is not required. Revocation is unimplemented. +It should be replaced with random data or removed. {%- endtrans %}
    • {% trans pdf1=url_for('static', filename='pdf/I2CP_spec.pdf'), pdf2=url_for('static', filename='pdf/datastructures.pdf') -%} @@ -673,5 +674,7 @@ That document also references the
    + +C library implementation {% endblock %} diff --git a/i2p2www/pages/site/docs/spec/blockfile.html b/i2p2www/pages/site/docs/spec/blockfile.html index f9ed3958..88ace4cd 100644 --- a/i2p2www/pages/site/docs/spec/blockfile.html +++ b/i2p2www/pages/site/docs/spec/blockfile.html @@ -169,8 +169,8 @@ The maximum number of entries per span is 16. {%- endtrans %}

    {% trans %}Properties Skiplist{% endtrans %}

    -

    {% trans -%} -"%%__INFO__%%" is the master database skiplist with String/Properties key/value entries containing only one entry: +

    {% trans INFO='"%%__INFO__%%"' -%} +{{ INFO }} is the master database skiplist with String/Properties key/value entries containing only one entry: {%- endtrans %}

         "info": a Properties (UTF-8 String/String Map), serialized as a Mapping:
@@ -182,8 +182,8 @@ The maximum number of entries per span is 16.

    {% trans %}Reverse Lookup Skiplist{% endtrans %}

    -

    {% trans -%} -"%%__REVERSE__%%" is the reverse lookup skiplist with Integer/Properties key/value entries +

    {% trans REVERSE='"%%__REVERSE__%%"' -%} +{{ REVERSE }} is the reverse lookup skiplist with Integer/Properties key/value entries (as of database version 2): {%- endtrans %}

    diff --git a/i2p2www/pages/site/docs/spec/common-structures.html b/i2p2www/pages/site/docs/spec/common-structures.html
index b3dec1e1..b07258f1 100644
--- a/i2p2www/pages/site/docs/spec/common-structures.html
+++ b/i2p2www/pages/site/docs/spec/common-structures.html
@@ -1,7 +1,7 @@
 {% extends "global/layout.html" %}
 {% block title %}{% trans %}Common structure Specification{% endtrans %}{% endblock %}
-{% block lastupdated %}{% trans %}June 2013{% endtrans %}{% endblock %}
-{% block accuratefor %}0.9.6{% endblock %}
+{% block lastupdated %}{% trans %}December 2013{% endtrans %}{% endblock %}
+{% block accuratefor %}0.9.9{% endblock %}
 {% block content %}
 
    {% trans %}Data types Specification{% endtrans %}
    
 
    {% trans i2np=site_url('docs/protocol/i2np'),
@@ -168,7 +168,7 @@ Defines an identifier that is unique to each router in a tunnel.
 4 byte Integer
 {% endtrans %}
    
 
-
    Javadoc
    
+
    Javadoc
    
 
 
    Certificate
    
 
    {% trans %}Description{% endtrans %}
    
@@ -270,9 +270,25 @@ For example,
 UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store Message will be corrupted.
 {%- endtrans %}
 
+
  • {% trans -%}
+The encoding allows duplicate keys, however in any usage where the mapping is signed,
+duplicates may cause a signature failure.
+{%- endtrans %}
    • 
+
 
  • {% trans -%}
 Mappings contained in I2NP messages (i.e. in a RouterAddress or RouterInfo)
 must be sorted by key so that the signature will be invariant.
+Duplicate keys are not allowed.
+{%- endtrans %}
    • 
+
+
  • {% trans i2cp=site_url('docs/spec/i2cp') -%}
+Mappings contained in an I2CP SessionConfig
+must be sorted by key so that the signature will be invariant.
+Duplicate keys are not allowed.
+{%- endtrans %}
    • 
+
+
  • {% trans -%}
+While it is application-dependent, keys and values are generally case-sensitive.
 {%- endtrans %}
    • 
 
 
  • {% trans -%}
@@ -381,6 +397,14 @@ certificate :: Certificate
 total length: 387+ bytes
 {% endhighlight %}
 
+
    Notes
    
+
    • 
+The public key of the destination was used for the old i2cp-to-i2cp encryption
+which was disabled in version 0.6, it is currently unused
+except for the IV for LeaseSet encryption,
+which is deprecated. The public key in the LeaseSet is used instead.
+
    
+
 
    Javadoc
    
 
 
    Lease
    
@@ -409,7 +433,7 @@ SHA256 Hash of the
 +----+----+----+----+
 
 tunnel_gw :: Hash of the RouterIdentity of the tunnel gateway
-             length -> >= 32 bytes
+             length -> 32 bytes
 
 tunnel_id :: TunnelId
              length -> 4 bytes
@@ -519,7 +543,7 @@ num :: Integer
        value: 0 <= num <= 16
 
 leases :: [Lease]
-          length -> >= $num*44 bytes
+          length -> $num*44 bytes
 
 signature :: Signature
              length -> 40 bytes
@@ -530,7 +554,7 @@ signature :: Signature
 
      
 
    • {% trans -%}
 The public key of the destination was used for the old i2cp-to-i2cp encryption
-which was disabled in version 0.6, it is currently unused?
+which was disabled in version 0.6, it is currently unused.
 {%- endtrans %}
      • 
 
 
    • {% trans elgamalaes=site_url('docs/how/elgamal-aes') -%}
@@ -593,7 +617,7 @@ cost :: Integer
         case 0 -> free
         case 255 -> expensive
 
-expiration :: Date
+expiration :: Date (must be all zeros, see notes below)
               length -> 8 bytes
 
               case null -> never expires
@@ -615,6 +639,12 @@ Expiration is currently unused, always null (all zeroes)).
 As of release 0.9.3, the expiration is assumed zero and not stored, so any non-zero expiration
 will fail in the RouterInfo signature verification.
 Implementing expiration (or another use for these bytes) will be a backwards-incompatible change.
+Routers MUST set this field to all zeros.
+{%- endtrans %}
      • 
+
+
    • {% trans -%}
+The following options, while not required, are standard and expected to be present in most router addresses:
+"host" (an IPv4 or IPv6 address or host name) and "port".
 {%- endtrans %}
      • 
 
    
 
@@ -707,14 +737,21 @@ signature :: Signature
 {% endhighlight %}
 
 
    {% trans %}Notes{% endtrans %}
    
-
    {% trans -%}
+
      
+
    • {% trans -%}
 The peer_size Integer may be followed by a list of that many router hashes.
 This is currently unused. It was intended for a form of restricted routes, which is unimplemented.
-{% endtrans %}
      
+{%- endtrans %}
      • 
 
-
      {% trans -%}
+
    • {% trans -%}
 The signature may be verified using the signing public key of the router_ident.
-{% endtrans %}
      
+{%- endtrans %}
      • 
+
+
    • {% trans netdb=site_url('docs/how/network-database') -%}
+See the network database page
+for standard options that are expected to be present in all router infos.
+{%- endtrans %}
      • 
+
    
 
 
    Javadoc
    
 
diff --git a/i2p2www/pages/site/docs/spec/geoip.html b/i2p2www/pages/site/docs/spec/geoip.html
index 66655450..dc452f4a 100644
--- a/i2p2www/pages/site/docs/spec/geoip.html
+++ b/i2p2www/pages/site/docs/spec/geoip.html
@@ -1,7 +1,7 @@
 {% extends "global/layout.html" %}
 {% block title %}{% trans %}GeoIP File Specification{% endtrans %}{% endblock %}
-{% block lastupdated %}{% trans %}May 2013{% endtrans %}{% endblock %}
-{% block accuratefor %}0.9.6{% endblock %}
+{% block lastupdated %}{% trans %}December 2013{% endtrans %}{% endblock %}
+{% block accuratefor %}0.9.9{% endblock %}
 {% block content %}
 
 
    {% trans %}Overview{% endtrans %}
    
@@ -60,8 +60,8 @@ The file is gzipped. Ungzipped format:
    Bytes 0-9: Magic number "I2PGeoIPv6"
    Bytes 10-11: Version (0x0001)
    Bytes 12-15 Options (0x00000000) (future use)
-   Bytes 16-23: Creation date (Java long)
-   Bytes 24-xx: Optional comment (UTF-8)
+   Bytes 16-23: Creation date (ms since 1970-01-01)
+   Bytes 24-xx: Optional comment (UTF-8) terminated by zero byte
    Bytes xx-255: null padding
    Bytes 256-: 18 byte records:
        8 byte from (/64)
@@ -71,11 +71,11 @@ The file is gzipped. Ungzipped format:
 
    {% trans %}NOTES:{% endtrans %}
    
 
      
 
    • Data must be sorted (SIGNED long twos complement), no overlap.
-So the order is 8000:: ... FFFF:: 0000:: ... 7FFF::
+So the order is 80000000 ... FFFFFFFF 00000000 ... 7FFFFFFF.
 
    • 
 The GeoIPv6.java class contains a program to generate this format from
 public sources such as the Maxmind GeoLite data.
 
    • 
-This specification is preliminary; I2P does not yet support IPv6 GeoIP lookup.
+IPv6 GeoIP lookup is supported as of release 0.9.8.
 
    
 {% endblock %}
diff --git a/i2p2www/pages/site/docs/spec/i2cp.html b/i2p2www/pages/site/docs/spec/i2cp.html
index 070fa709..b6550f93 100644
--- a/i2p2www/pages/site/docs/spec/i2cp.html
+++ b/i2p2www/pages/site/docs/spec/i2cp.html
@@ -1,7 +1,7 @@
 {% extends "global/layout.html" %}
 {% block title %}I2CP Specification{% endblock %}
-{% block lastupdated %}June 2013{% endblock %}
-{% block accuratefor %}0.9.6{% endblock %}
+{% block lastupdated %}December 2013{% endblock %}
+{% block accuratefor %}0.9.9{% endblock %}
 {% block content %}
 
    I2P Control Protocol (I2CP) Specification
    
 
    Overview
    
@@ -220,11 +220,16 @@ DSA Signa
 
    • 
 
 
    Notes
    
-
    
+
    • 
 The options are specified on the
 I2CP Overview page.
-
      
-
+
    • 
+The Mapping
+must be sorted by key so that the signature will be validated correctly in the router.
+
    • 
+The creation date must be within +/- 30 seconds of the current time when processed by
+the router, or the config will be rejected.
+
    
 
 
 
@@ -318,6 +323,20 @@ GetDateMessage
    {{ _('Admin') }}{{ _('Admin') }} {{ _('Project Manager') }} zzz {{ _('point of contact of last resort') }}[{{ _('vacant') }}] {{ _('threat model / crypto expert') }}
    Trac adminKillYourTV{{ _('Manage the project bug tracker') }}
    {{ _('Translation admins') }}eche|on, HungryHobo, KillYourTV, str4d, zzzAdmins on Transifex
    {{ _('User Advocate') }} [{{ _('vacant') }}]{{ _('manage the public project website content design') }}
    {% trans website=i2pconv('www.i2p2.i2p') %}Webserver admin{% endtrans %}{% trans website=site_url() %}Webserver admin{% endtrans %} welterde {{ _('manage the public project webservers') }}
    {% trans website=i2pconv('www.i2p2.i2p') %}Website admin{% endtrans %}{% trans website=site_url() %}Website admin{% endtrans %} str4d {{ _('manage the public project website content') }}
    {{ _('Dev') }}{{ _('Dev') }} {{ _('Core Lead') }} zzz {{ _('lead dev for the SDK and router') }}{{ _('C++ Router') }}
    {{ _('Console Translations') }}walking{{ _('Chinese') }}{{ _('Translators') }}{{ _('many many people!') }}Translators on Transifex
    monkeybrains{{ _('Dutch') }}
    magma{{ _('French') }}
    eche|on, mixxy{{ _('German') }}
    rus, 4get, slow{{ _('Russian') }}
    user{{ _('Spanish') }}
    thelastcode, hamada{{ _('Arabic') }}
    [{{ _('vacant') }}]{{ _('Other languages') }}
    {{ _('Contributors') }} cervantes
    {{ _('Past contributors') }}{{ _('Past contributors') }} mihi {{ _('I2PTunnel development, ministreaming library') }}
    dr|z3d {{ _('Console and website themes') }}
    walkingChinese translation
    monkeybrainsDutch translation
    magmaFrench translation
    eche|on, mixxyGerman translation
    rus, 4get, slowRussian translation
    userSpanish translation
    thelastcode, hamadaArabic translation
    {% trans %}… and many others{% endtrans %}
    i2p.streaming.answerPingstrue{% trans -%} Whether to respond to incoming pings {%- endtrans %}
    i2p.streaming.blacklistnull{% trans -%} Comma- or space-separated list of Base64 peer Hashes to be blacklisted for incoming connections to ALL destinations in the context. @@ -198,12 +214,31 @@ The initial value of the resend delay field in the packet header, times 1000. Not fully implemented; see below. {%- endtrans %}
    i2p.streaming.initialRTT8000 ({% trans %}if no sharing data available{% endtrans %})
    i2p.streaming.initialRTO9000{% trans -%} +Initial timeout +(if no sharing data available). +{%- endtrans %} {% trans release='0.9.8' -%} +As of release {{ release }}. +{%- endtrans %}
    i2p.streaming.initialRTT8000 {% trans -%} +Initial round trip time estimate +(if no sharing data available). +Disabled as of release 0.9.8; uses actual RTT. +{%- endtrans %}
    i2p.streaming.initialWindowSize6({% trans %}if no sharing data available{% endtrans %}) {% trans -%} In standard TCP, window sizes are in bytes, while in I2P, window sizes are in messages. {%- endtrans %}
    i2p.streaming.maxConcurrentStreams-1 {% trans -%} (0 or negative value means unlimited) This is a total limit for incoming and outgoing combined. @@ -273,6 +308,27 @@ while in I2P, window sizes are in messages. A higher number means slower growth. {%- endtrans %}
    i2p.streaming.tcbcache.rttDampening0.75{% trans -%} +Ref: RFC 2140. Floating point value. +May be set only via context properties, not connection options. +{%- endtrans %} {% trans release='0.9.8' -%} +As of release {{ release }}. +{%- endtrans %}
    i2p.streaming.tcbcache.rttdevDampening0.75{% trans -%} +Ref: RFC 2140. Floating point value. +May be set only via context properties, not connection options. +{%- endtrans %} {% trans release='0.9.8' -%} +As of release {{ release }}. +{%- endtrans %}
    i2p.streaming.tcbcache.wdwDampening0.75{% trans -%} +Ref: RFC 2140. Floating point value. +May be set only via context properties, not connection options. +{%- endtrans %} {% trans release='0.9.8' -%} +As of release {{ release }}. +{%- endtrans %}
    i2p.streaming.writeTimeout-1{% trans -%} How long to block on write/flush, in milliseconds. Negative means indefinitely. {%- endtrans %}
    8118Privoxy (reserve)
    8123Tor Polipo (reserve)
    8887Old default network port
    8888Freenet (reserve)
    8997Monotone Proxy (alt)
    8998Monotone Proxy
    8999Monotone Proxy (alt)
    string     -{% trans -%} +{% trans -%} For authorization, if required by the router. If the client is running in the same JVM as a router, this option is not required. +Warning - username and password are sent in the clear to the router, unless using SSL (i2cp.SSL=true). +Authorization is only recommended when using SSL. {%- endtrans %}
    string     -{% trans -%} -For authorization, if required by the router. -If the client is running in the same JVM as a router, this option is not required. -{%- endtrans %}
    32  
    + +HostLookupMessage + +C->R +38 +0.9.10 +
    + +HostReplyMessage + +R->C +39 +0.9.10 +
    MessagePayloadMessage @@ -450,7 +469,11 @@ As of release 0.7.2.

    Create Lease Set

    Description

    -This message is sent in response to a RequestLeaseSetMessage and contains all +This message is sent in response to a +Create Lease Set Message +or +Create Variable Lease Set Message +and contains all of the Lease structures that should be published to the I2NP Network Database. Sent from Client to Router.

    @@ -468,9 +491,9 @@ Sent from Client to Router.

    Notes

    The SigningPrivateKey matches the SigningPublicKey from within the -LeaseSet, as does the PrivateKey with the PublicKey. The Signing keys are +LeaseSet, as does the PrivateKey with the PublicKey. The Signing key is necessary to allow the router to revoke the LeaseSet if the client goes offline, -and the normal keys are necessary for decrypting garlic routed messages. The +and the encryption key is necessary for decrypting garlic routed messages. The LeaseSet granted may include Lease structures for tunnels pointing at another router if the client is actively connected to multiple routers with Leases granted to each. @@ -497,11 +520,16 @@ The router responds with a Session Status Message

    Notes

    -

    -The second message sent by the client after sending the Get Date Message and receiving the Set Date Message response. -If the Date in the Session Config is too far from the router's current time, the session will be rejected. +

     @@ -522,6 +550,7 @@ The router responds with a Dest Reply Message. As of release 0.7. As of release 0.8.3, multiple outstanding lookups are supported, and lookups are supported in both I2PSimpleSession and in standard sessions. +Host Lookup Message is preferred as of release 0.9.10.

    @@ -545,6 +574,7 @@ As of release 0.7. As of release 0.8.3, the requested Hash is returned if the lookup failed, so that the client may have multiple lookups outstanding and correlate the replies to the lookups. +To correlate a Destination response with a request, take the Hash of the Destination. Prior to release 0.8.3, the response was empty on failure.

    @@ -617,18 +647,111 @@ The router responds with a Set Date Message.

    Contents

    1. I2CP Version String +
    2. +Authentication Mapping +(optional, as of release 0.9.10)

    Notes

    -

    +

    • Generally the first message sent by the client after sending the protocol version byte. +
    • The version string is included as of release 0.8.7. This is only useful if the client and router are not in the same JVM. If it is not present, the client is version 0.8.6 or earlier. +
    • +Preliminary: As of release 0.9.10, the authentication +Mapping +may be included, with the keys i2cp.username and i2cp.password. +The Mapping need not be sorted as this message is not signed. +Prior to and including 0.9.10, authentication is included in the +Session Config Mapping, and +no authentication is enforced for GetDate, GetBandwidthLimits, or DestLookup. +The Get Date authentication will be enforced in a future release. +This is only useful outside router context. +This will be an incompatible change, but will only affect sessions outside +router context with authentication, which should be rare. +

    +

    Host Lookup

    +

    Description

    +

    +Sent from Client to Router. +The router responds with a Host Reply Message. +This replaces the Dest Lookup Message +and adds a request ID, a timeout, and host name lookup support. +As it also supports Hash lookups, it may be used for all lookups if the router supports it. +For host name lookups, the router will query its context's naming service. +This is only useful if the client is outside the router's context. +Inside router context, the client should query the naming service itself, +which is much more efficient. +

    + +

    Contents

    +
    1. +4 byte Integer request ID +
    2. +4 byte Integer timeout (ms) +
    3. +1 byte Integer request type +
    4. +SHA-256 Hash +or +host name String +
    + +

    Notes

    +
    • +Preliminary. As of release 0.9.10. +Use Dest Lookup Message for older routers. +
    • +The request ID will be returned in the Host Reply Message. +
    • +Timeout is useful for Hash lookups. Recommended minimum 10,000 (10 sec.). +In the future it may also be useful for remote naming service lookups. +The value may be not be honored for local host name lookups, which should be fast. +
    • +The request type is 0 for Hash and 1 for host name. +
    • +Base 32 host name lookup is supported but it is preferred to convert +it to a Hash first. +
    + + + +

    Host Reply

    +

    Description

    +

    +Sent from Router to Client in response to a +Host Lookup Message. +

    +

    Contents

    +
    1. +4 byte Integer request ID +
    2. +1 byte Integer result code +
    3. +Destination, +only present if result code is zero. +
    + +

    Notes

    +
    • +Preliminary. As of release 0.9.10. +See Host Lookup notes. +
    • +The request ID is that from the Host Lookup. +
    • +The result code is 0 for success, 1-255 for failure. +Only 1 is used for failure now, more specific failure codes may be defined in the future. +
    + + + +

    Message Payload

    Description

    @@ -684,10 +807,68 @@ guaranteed failed. The size Integer specifies the size of the available message and is only relevant for status = 0. Even though guaranteed is unimplemented, (best effort is the only service), the current router implementation uses the guaranteed status codes, not the best effort codes. -As of router version 0.9.5, additional status codes are defined. +As of router version 0.9.5, additional status codes are defined, +however they are not necessarily implemented. See the MessageStatusMessage Javadocs for details. +All status codes: + +
    Status CodeAs Of ReleaseNameDescription +
    0 AvailableFor incoming messages only. + The included size is the size in bytes of the available message. + This is unused in "fast receive" mode, which is the default as of release 0.9.4. + All other status codes below are for outgoing messages. +
    1 AcceptedOutgoing message accepted by the local router for delivery. + The included nonce matches the nonce in the + Send Message Message, and the included Message ID + will be used for subsequent success or failure notification. +
    2 Best Effort SuccessProbable success (unused) +
    3 Best Effort FailureProbable failure +
    4 Guaranteed SuccessProbable success +
    5 Guaranteed FailureGeneric failure, specific cause unknown. + May not really be a guaranteed failure. +
    60.9.5Local SuccessLocal delivery successful. + The destination was another client on the same router. +
    70.9.5Local FailureLocal delivery failure. + The destination was another client on the same router. +
    80.9.5Router FailureThe local router is not ready, has shut down, + or has major problems. + This is a guaranteed failure. +
    90.9.5Network FailureThe local computer apparently has no network connectivity at all. + This is a guaranteed failure. +
    100.9.5Bad SessionThe I2CP session is invalid or closed. + This is a guaranteed failure. +
    110.9.5Bad MessageThe message payload is invalid or zero-length or too big. + This is a guaranteed failure. +
    120.9.5Bad OptionsSomething is invalid in the message options, + or the expiration is in the past or too far in the future. + This is a guaranteed failure. +
    130.9.5Overflow FailureSome queue or buffer in the router is full and the message was dropped. + This is a guaranteed failure. +
    140.9.5Message ExpiredThe message expired before it could be sent. + This is a guaranteed failure. +
    150.9.5Bad Local LeasesetThe client has not yet signed a leaseset, or the local keys + are invalid, or it has expired, or it does not have any tunnels in it. + This is a guaranteed failure. +
    160.9.5No Local TunnelsLocal problems. No outbound tunnel to send through, + or no inbound tunnel if a reply is required. + This is a guaranteed failure. +
    170.9.5Unsupported EncryptionThe certs or options in the destination or its leaseset + indicate that it uses an encryption format that we don't support, so we can't talk to it. + This is a guaranteed failure. +
    180.9.5Bad DestinationSomething is wrong with the far-end destination. + Bad format, unsupported options, certificates, etc. + This is a guaranteed failure. +
    190.9.5Bad LeasesetWe got the far-end leaseset but something strange is wrong with it. + Unsupported options or certificates, no tunnels, etc. + This is a guaranteed failure. +
    200.9.5Expired LeasesetWe got the far-end leaseset but it's expired and we can't get a new one. + This is a guaranteed failure. +
    210.9.5No LeasesetCould not find the far-end leaseset. + This is a common failure, equivalent to a DNS lookup failure. + This is a guaranteed failure. +

    When status = 1 (accepted), the nonce matches the nonce in the @@ -720,6 +901,9 @@ message id specified in the ReceiveMessageBeginMessage is invalid or incorrect, the router may simply not reply, or it may send back a DisconnectMessage.

    +

    +This is unused in "fast receive" mode, which is the default as of release 0.9.4. +

    @@ -743,6 +927,9 @@ Sent from Client to Router. The ReceiveMessageBeginMessage is sent after a MessagePayloadMessage fully delivers a message's payload.

    +

    +This is unused in "fast receive" mode, which is the default as of release 0.9.4. +

    @@ -762,9 +949,14 @@ The router responds with a Session Status Message

    Notes

    -

    +

     @@ -775,7 +967,7 @@ As of release 0.7.1. Tell the other party (client or router) that they are under attack, potentially with reference to a particular messageId. If the router is under attack, the client may decide to migrate to another router, and if a client is under attack, the router may rebuild -its routers or shitlist some of the peers that sent it messages delivering the attack. +its routers or banlist some of the peers that sent it messages delivering the attack. Sent either from router to client or from client to router.

    Contents

    @@ -844,10 +1036,10 @@ The client responds with a Create LeaseSet Message
    1. Session ID
    2. -1 byte Integer number of tunnels +1 byte Integer number of tunnels
    3. That many - Leases + Leases

    Notes

    @@ -904,7 +1096,7 @@ i2cp.messageReliability=none for this message only.

    Send Message Expires

    Description

    -Sent from Client to Router. Same as Send Message Message, except includes an expiration. +Sent from Client to Router. Same as Send Message Message, except includes an expiration and options.

    Contents

    1. @@ -953,7 +1145,19 @@ Definitions are subject to change. Use the SendMessageOptions class to construct

      Bit order: 15...0

      -Bits 15-9: Unused, must be zero +Bits 15-11: Unused, must be zero +

      +Bits 10-9: Message Reliability Override (scheduled for release 0.9.10) + +
      Field valueDescription +
      00Use session setting i2cp.messageReliabiltiy (default) +
      01Use "best effort" message reliabiltiy for this message, + overriding the session setting. The router will send one or more MessageStatusMessages in response. +
      10Use "guaranteed" message reliabiltiy for this message, + overriding the session setting. The router will send one or more MessageStatusMessages in response. +
      11Unused. Use a nonce value of 0 to force "none" and override a session setting + of "best effort" or "guaranteed". +

      Bit 8: If 1, don't send lease set

      diff --git a/i2p2www/pages/site/docs/spec/i2np.html b/i2p2www/pages/site/docs/spec/i2np.html index 7533d2a5..4e6df9e0 100644 --- a/i2p2www/pages/site/docs/spec/i2np.html +++ b/i2p2www/pages/site/docs/spec/i2np.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}I2NP Specification{% endblock %} -{% block lastupdated %}June 2013{% endblock %} -{% block accuratefor %}0.9.6{% endblock %} +{% block lastupdated %}November 2013{% endblock %} +{% block accuratefor %}0.9.8.1{% endblock %} {% block content %}

      I2P Network Protocol (I2NP) Specification

      @@ -58,6 +58,9 @@ msg_id :: Integer length -> 4 bytes purpose -> uniquely identifies this message (for some time at least) + This is usually a locally-generated random number, but for + outgoing tunnel build messages it may be derived from + the incoming message. See below. expiration :: Date 8 bytes @@ -181,7 +184,7 @@ ElGamal encrypted: + + | | +----+----+----+----+----+----+----+----+ -| encrypted data ... | +| encrypted data... | ~ ~ | | +----+----+----+----+----+----+----+----+ @@ -189,7 +192,7 @@ ElGamal encrypted: ElGamal and AES encrypted: +----+----+----+----+----+----+----+----+ -| encrypted data ... | +| encrypted data... | ~ ~ | | +----+----+----+----+----+----+----+----+ @@ -526,6 +529,12 @@ The key is the "real" hash of the RouterIdentity or Destination, NOT the routing

      DatabaseLookup

      +

      Description

      +

      + A request to look up an item in the network database. + The response is either a DatabaseStore or a DatabaseSearchReply. +

      +

      Contents

      {% highlight lang='dataspec' %} +----+----+----+----+----+----+----+----+ | SHA256 hash as the key to look up | @@ -729,7 +738,7 @@ from ::
    2. The lookup key, peer hashes, and from hash are "real" hashes, NOT routing keys.
      3. - + @@ -868,6 +877,12 @@ Expiration :: Date (8 bytes)

      TunnelData

      +

      Description

      +

      + A message sent from a tunnel's gateway or participant to the next participant or endpoint. + The data is of fixed length, containing I2NP messages that are fragmented, batched, padded, and encrypted. +

      +

      Contents

      {% highlight lang='dataspec' %} +----+----+----+----+----+----+----+----+ | tunnnelID | data | @@ -894,12 +909,19 @@ data ::

      Notes

      TunnelGateway

      +

      Description

      +

      + Wraps another I2NP message to be sent into a tunnel at the tunnel's inbound gateway. +

      +

      Contents

      {% highlight lang='dataspec' %} +----+----+----+----+----+----+----+-// | tunnelId | length | data... @@ -931,17 +953,16 @@ data ::

      Data

      Description

      - Used as a wrapper for encrypted Garlic Messages and Garlic Cloves. - Also used previously for network load testing. + Used by Garlic Messages and Garlic Cloves to wrap arbitrary data.

      Contents

      A length Integer, followed by opaque data.

      {% highlight lang='dataspec' %} -+----+----+----+----+----+-// -| length | data... -+----+----+----+----+----+-// ++----+----+----+----+----+-//-+ +| length | data... | ++----+----+----+----+----+-//-+ {% endhighlight %}

      Definition

      @@ -980,9 +1001,12 @@ total size: 8*528 = 4224 bytes {% endhighlight %}

      Notes

      -

      +

        +
      • See also the tunnel creation specification. -

        +
      • + The I2NP message ID for this message must be set according to the tunnel creation specification. +

      TunnelBuildReply

      @@ -991,9 +1015,12 @@ same format as TunnelBuild message, with Build Response Records {% endhighlight %}

      Notes

      -

      +

        +
      • See also the tunnel creation specification. -

        +
      • + The I2NP message ID for this message must be set according to the tunnel creation specification. +

      VariableTunnelBuild

      {% highlight lang='dataspec' %} @@ -1020,6 +1047,8 @@ total size: 1 + $num*528 This message was introduced in router version 0.7.12, and may not be sent to tunnel participants earlier than that version.
    3. See also the tunnel creation specification. +
    4. + The I2NP message ID for this message must be set according to the tunnel creation specification.

      VariableTunnelBuildReply

      @@ -1039,6 +1068,8 @@ Same format as VariableTunnelBuild message, with Build Response Records. This message was introduced in router version 0.7.12, and may not be sent to tunnel participants earlier than that version.
    5. See also the tunnel creation specification. +
    6. + The I2NP message ID for this message must be set according to the tunnel creation specification. diff --git a/i2p2www/pages/site/docs/spec/plugin.html b/i2p2www/pages/site/docs/spec/plugin.html index 406d833e..8526379b 100644 --- a/i2p2www/pages/site/docs/spec/plugin.html +++ b/i2p2www/pages/site/docs/spec/plugin.html @@ -321,7 +321,7 @@ Other plugin guidelines
    7. See i2p.scripts branch or any of the sample plugins on zzz's page for a xpi2p file generator to make it easy.
    8. -Pack200 of jars and wars is strongly recommended for plugins, it generally shrinks plugins by 60-65%. +Pack200 of jars and wars is strongly recommended for plugins, it generally shrinks plugins by 60-65%. See any of the sample plugins on zzz's page for an example. Pack200 unpacking is supported on routers 0.7.11-5 or higher, which is essentially all routers that support plugins at all. diff --git a/i2p2www/pages/site/docs/spec/ssu.html b/i2p2www/pages/site/docs/spec/ssu.html index 083541b7..638f72db 100644 --- a/i2p2www/pages/site/docs/spec/ssu.html +++ b/i2p2www/pages/site/docs/spec/ssu.html @@ -1,11 +1,9 @@ {% extends "global/layout.html" %} {% block title %}SSU Protocol Specification{% endblock %} -{% block lastupdated %}June 2013{% endblock %} -{% block accuratefor %}0.9.6{% endblock %} +{% block lastupdated %}December 2013{% endblock %} +{% block accuratefor %}0.9.9{% endblock %} {% block content %} -Note: IPv6 information is preliminary. -

      See the SSU page for an overview of the SSU transport. @@ -119,11 +117,18 @@ the following bitfields:

      + + | | +----+----+----+----+----+----+----+----+ - |flag| time | (optionally | - +----+----+----+----+----+ | - | this may have 64 byte keying material | - | and/or a one+N byte extended options) | - +---------------------------------------| + |flag| time | | + +----+----+----+----+----+ + + | keying material (optional) | + + + + | | + ~ ~ + | | + + +----+----+----+ + | |#opt| | + +----+----+----+----+----+----+ + + | #opt extended option bytes (optional) | + ~ ~ {% endhighlight %} @@ -154,18 +159,13 @@ bytes.

      All messages contain 0 or more bytes of padding. Each message must be padded to a 16 byte boundary, as required by the AES256 encryption layer. -Currently, messages are not padded beyond the next 16 byte boundary. -The fixed-size tunnel messages of 1024 bytes (at a higher layer) -provide a significant amount of protection. -In the future, additional padding in the transport layer up to -a set of fixed packet sizes may be appropriate to further hide the data -fragmentation to external adversaries. -

      -Through release 0.9.6, messages were only padded to the next 16 byte boundary, +Through release 0.9.7, messages were only padded to the next 16 byte boundary, and messages not a multiple of 16 bytes could possibly be invalid. As of release 0.9.7, messages may be padded to any length as long as the current MTU is honored. Any extra 1-15 padding bytes beyond the last block of 16 bytes cannot be encrypted or decrypted and will be ignored. However, the full length and all padding is included in the MAC calculation. +As of release 0.9.8, transmitted messages are not necessarily a multiple of 16 bytes. +The SessionConfirmed message is an exception, see below.

      @@ -192,9 +192,9 @@ The key used for the MAC and encryption is specified for each message below.

      Notes

      IPv6 Notes

      -While the protocol specification supports 16-byte IPv6 addresses, -IPv6 addressing is not currently supported within I2P. -All IP addresses are currently 4 bytes. +The protocol specification allows both 4-byte IPv4 and 16-byte IPv6 addresses. +SSU-over-IPv6 is supported as of version 0.9.8. +See the documentation of individual messages below for details on IPv6 support.

      Timestamps

      While most of I2P uses 8-byte Date timestamps with @@ -392,7 +392,7 @@ bits 3-0: total identity fragments (F) 1-15
    		sessionKey
    - Fragment 0 through F-2 + Fragment 0 through F-2 (if F > 1): {% highlight lang='dataspec' %} +----+----+----+----+----+----+----+----+ |info| cursize | | @@ -407,7 +407,7 @@ bits 3-0: total identity fragments (F) 1-15

    • +----+----+----+----+----+----+----+----+ {% endhighlight %} - Fragment F-1: + Fragment F-1 (last or only fragment): {% highlight lang='dataspec' %} +----+----+----+----+----+----+----+----+ |info| cursize | | @@ -422,6 +422,7 @@ bits 3-0: total identity fragments (F) 1-15 | arbitrary amount of uninterpreted | | data, to 40 bytes prior to | | end of the current packet | + | Packet length must be mult. of 16 | +----+----+----+----+----+----+----+----+ | DSA signature | + + @@ -444,7 +445,9 @@ Typical size including header, in current implementation: 480 bytes In the current implementation, the maximum fragment size is 512 bytes.
  • The typical Router Identity -is 387 bytes, so no fragmentation is usually necessary. +is 387 bytes, so no fragmentation is ever necessary. +If new crypto extends the size of the RouterIdentity, the fragmentation scheme +must be tested carefully.
  • There is no mechanism for requesting or redelivering missing fragments.
  • @@ -453,6 +456,10 @@ The total fragments field F must be set identically in all fragments. See the Keys section above for details on DSA signatures.
  • Signed-on time appears to be unused or unverified in the current implementation. +
  • +Since the signature is at the end, the padding in the last or only packet must pad the total packet to +a multiple of 16 bytes, or the signature will not get decrypted correctly. +This is different from all the other message types, where the padding is at the end.
    • diff --git a/i2p2www/pages/site/docs/spec/streaming.html b/i2p2www/pages/site/docs/spec/streaming.html index c0a8c84b..c22ca15d 100644 --- a/i2p2www/pages/site/docs/spec/streaming.html +++ b/i2p2www/pages/site/docs/spec/streaming.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}{% trans %}Streaming Library Specification{% endtrans %}{% endblock %} -{% block lastupdated %}{% trans %}November 2012{% endtrans %}{% endblock %} -{% block accuratefor %}0.9.3{% endblock %} +{% block lastupdated %}{% trans %}December 2013{% endtrans %}{% endblock %} +{% block accuratefor %}0.9.9{% endblock %} {% block content %}

    {% trans -%} See the Streaming page for an overview of the Streaming Library. @@ -92,44 +92,50 @@ in the given order. Bit order: 15....0 (15 is MSB)

    -
    BitFlagOption DataFunction -
    0SYNCHRONIZE-- +
    BitFlagOption OrderOption DataFunction +
    0SYNCHRONIZE---- Similar to TCP SYN. Set in the initial packet and in the first response. FROM_INCLUDED and SIGNATURE_INCLUDED must be set also. -
    1CLOSE-- +
    1CLOSE---- Similar to TCP FIN. If the response to a SYNCHRONIZE fits in a single message, the response will contain both SYNCHRONIZE and CLOSE. SIGNATURE_INCLUDED must be set also. -
    2RESET-- +
    2RESET---- Abnormal close. SIGNATURE_INCLUDED must be set also. -
    3SIGNATURE_INCLUDED40 byte DSA Signature +
    3SIGNATURE_INCLUDED440 byte DSA Signature -Currently sent only with SYNCHRONIZE, CLOSE, and RESET, where it is required. +Currently sent only with SYNCHRONIZE, CLOSE, and RESET, where it is required, +and with ECHO, where it is required for a ping. The signature uses the Destination's DSA signing keys to sign the entire header and payload with the 40-byte space in the option data field for the signature being set to all zeroes. -
    4SIGNATURE_REQUESTED-- +
    4SIGNATURE_REQUESTED---- Unused. Requests every packet in the other direction to have SIGNATURE_INCLUDED -
    5FROM_INCLUDED387+ byte Destination +
    5FROM_INCLUDED2387+ byte Destination -Currently sent only with SYNCHRONIZE, where it is required. -
    6DELAY_REQUESTED2 byte Integer +Currently sent only with SYNCHRONIZE, where it is required, +and with ECHO, where it is required for a ping. +
    6DELAY_REQUESTED12 byte Integer Optional delay. How many milliseconds the sender of this packet wants the recipient to wait before sending any more data. A value greater than 60000 indicates choking. -
    7MAX_PACKET_SIZE_INCLUDED2 byte Integer +
    7MAX_PACKET_SIZE_INCLUDED32 byte Integer Currently sent with SYNCHRONIZE only. Was also sent in retransmitted packets until release 0.9.1. -
    8PROFILE_INTERACTIVE-- +
    8PROFILE_INTERACTIVE---- Unused or ignored; the interactive profile is unimplemented. -
    9ECHO-- -Unused except by ping programs -
    10NO_ACK-- +
    9ECHO---- +Unused except by ping programs. +If set, most other options, and the payload, are ignored. See +the streaming docs. +
    10NO_ACK---- This flag simply tells the recipient to ignore the ackThrough field in the header. -Currently unused, the ackThrough field is always valid. -
    11-15unused +Currently set in the inital SYN packet, otherwise the ackThrough field is always valid. +Note that this does not save any space, the ackThrough field is before the flags +and is always present. +
    11-15unused
    {% endblock %} diff --git a/i2p2www/pages/site/docs/spec/tunnel-message.html b/i2p2www/pages/site/docs/spec/tunnel-message.html index 9874fd0b..5dec4c6b 100644 --- a/i2p2www/pages/site/docs/spec/tunnel-message.html +++ b/i2p2www/pages/site/docs/spec/tunnel-message.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}Tunnel Message Specification{% endblock %} -{% block lastupdated %}October 2011{% endblock %} -{% block accuratefor %}0.8.10{% endblock %} +{% block lastupdated %}December 2013{% endblock %} +{% block accuratefor %}0.9.9{% endblock %} {% block content %}

    Tunnel Message Specification

    This document specifies the format of tunnel messages. @@ -122,7 +122,7 @@ IV :: Checksum :: 4 bytes - the first 4 bytes of the SHA256 hash of the remaining contents of the message concatenated with the IV + the first 4 bytes of the SHA256 hash of the contents of the message after the zero byte concatenated with the IV Nonzero_padding :: 0 or more bytes @@ -145,9 +145,14 @@ total size: 1028 Bytes +

    Notes

    +
    • +The padding, if any, must be before the instruction/message pairs. +There is no provision for padding at the end. +
    • +The checksum does NOT cover the padding or the zero byte. +
    -

    Note that the padding, if any, must be before the instruction/message pairs. -there is no provision for padding at the end.

    Delivery Instructions

    @@ -195,6 +200,7 @@ flag: bits 6-5: delivery type For tunnel messages: 0x0 = LOCAL, 0x01 = TUNNEL, 0x02 = ROUTER, 0x03 = unused + Note: LOCAL is used for inbound tunnels only, unimplemented for outbound tunnels For garlic cloves: 0x0 = LOCAL, 0x01 = DESTINATION, 0x02 = ROUTER, 0x03 = TUNNEL bit 4: delay included? Unimplemented, always 0 @@ -203,7 +209,7 @@ flag: If 1, the message is fragmented, and the instructions contain a Message ID bit 2: extended options? Unimplemented, always 0 If 1, extended options are included - bits 1-0: reserved + bits 1-0: reserved, set to 0 for compatibility with future uses Tunnel ID: 4 bytes @@ -239,12 +245,15 @@ Extended Options: size: 2 bytes + Required in a tunnel message; never present in a garlic clove. The length of the fragment that follows - Valid values: 1 to approx. 960 in a tunnel message; 1 to 64K - 1 in a garlic clove + Valid values: 1 to approx. 960 in a tunnel message Total length: Typical length is: - 3 bytes for LOCAL delivery (garlic clove); - 35 bytes for ROUTER / DESTINATION delivery or 39 bytes for TUNNEL delivery (unfragmented or garlic clove); + 1 byte for LOCAL delivery (garlic clove); + 3 bytes for LOCAL delivery (tunnel message); + 35 bytes for ROUTER / DESTINATION delivery or 39 bytes for TUNNEL delivery (unfragmented tunnel message); + 33 bytes for ROUTER / DESTINATION delivery or 37 bytes for TUNNEL delivery (garlic clove); 39 bytes for ROUTER delivery or 43 bytes for TUNNEL delivery (first fragment) @@ -268,7 +277,7 @@ frag :: Message_ID :: 4 bytes - the same ID specified in the first fragment + the same ID specified in the first fragment for this message ID size :: 2 bytes diff --git a/i2p2www/pages/site/docs/spec/updates.html b/i2p2www/pages/site/docs/spec/updates.html index be572f84..cad13b4f 100644 --- a/i2p2www/pages/site/docs/spec/updates.html +++ b/i2p2www/pages/site/docs/spec/updates.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}{% trans %}I2P Software Update Specification{% endtrans %}{% endblock %} -{% block lastupdated %}{% trans %}May 2013{% endtrans %}{% endblock %} -{% block accuratefor %}0.9.6{% endblock %} +{% block lastupdated %}{% trans %}October 2013{% endtrans %}{% endblock %} +{% block accuratefor %}0.9.9{% endblock %} {% block content %}

    {% trans %}Overview{% endtrans %}

    {% trans -%} @@ -33,19 +33,66 @@ The news.xml file may contain the following elements:

    {% trans -%} -The elements may be included inside XML comments to prevent interpretation by browsers. -The i2p.release element and version are required. All others are optional and are -currently unused. +Parameters in the i2p.release entry are as follows. +All keys are case-insensitive. All values must be enclosed in double quotes. {%- endtrans %}

    +
      +
    • +date: The release date of the router version. Unused. Format not specified. +
    • +minJavaVersion: The minimum version of Java required to run the current version. +As of release 0.9.9. +
    • +minVersion: The minimum version of the router required to update to the current version. +If a router is older than this, the user must (manually?) update to an intermediate version first. +As of release 0.9.9. +
    • +su3Clearnet: One or more HTTP URLs where the .su3 update file may +be found on the clearnet (non-I2P). +Multiple URLs must be separated by a space or comma. +As of release 0.9.9. +
    • +su3SSL: One or more HTTPS URLs where the .su3 update file may +be found on the clearnet (non-I2P). +Multiple URLs must be separated by a space or comma. +As of release 0.9.9. +
    • +sudTorrent: The magnet link for the .sud (non-pack200) torrent of the update. +As of release 0.9.4. +
    • +su2Torrent: The magnet link for the .su2 (pack200) torrent of the update. +As of release 0.9.4. +
    • +su3Torrent: The magnet link for the .su3 (new format) torrent of the update. +As of release 0.9.9. +
    • +version: Required. The latest current router version available. +
    +

    {% trans -%} -The news source is trusted only to indicate that a new version is available. -It does not specify the URL of the update, the checksum, or any other information. +The elements may be included inside XML comments to prevent interpretation by browsers. +The i2p.release element and version are required. All others are optional. +NOTE: Due to parser limitations an entire element must be on a single line. {%- endtrans %}

    {% trans %}Update File Specification{% endtrans %}

    {% trans -%} +As of release 0.9.9, the signed update file, named i2pupdate.su3, will +use the "su3" file format specified below. +Approved release signers will use 4096-bit RSA keys. +The X.509 public key certificates for these signers are distributed in the router installation packages. +The updates may contain certificates for new, approved signers, and/or contain +a list of certificates to delete for revocation. +{%- endtrans %}

    + + +

    {% trans %}Old Update File Specification{% endtrans %}

    +

    {% trans -%} +This format is obsolte as of release 0.9.9. +{%- endtrans %}

    +

    {% trans -%} The signed update file, traditionally named i2pupdate.sud, is simply a zip file with a prepended 56 byte header. The header contains: @@ -99,7 +146,7 @@ As of release 0.7.12, the router supports Pack200 decompression. Files inside the zip archive with a .jar.pack or .war.pack suffix are transparently decompressed to a .jar or .war file. Update files containing .pack files are traditionally named with a '.su2' suffix. -Pack200 shrinks the update files by about 60%. +Pack200 shrinks the update files by about 60%. {%- endtrans %}

    {% trans -%} @@ -126,10 +173,10 @@ The router will then delete the deletelist.txt file.

    {% trans %}New "su3" Update File Specification{% endtrans %}

    {% trans -%} -This specification is preliminary and is not yet implemented. +This specification is used for router updates and reseed data as of release 0.9.9. {%- endtrans %}

    -

    {% trans %}Issues with existing .sud/.su2 format:{% endtrans %}

    +

    {% trans %}Issues with the previous .sud/.su2 format:{% endtrans %}

    • {% trans -%} No magic number or flags @@ -177,30 +224,41 @@ existing version checkers 7 su3 file format version = 0 -8 unused +8-9 Signature type +
      • 0x0000 = DSA-160 +
      • 0x0001 = ECDSA-SHA256-P256 +
      • 0x0002 = ECDSA-SHA384-P384 +
      • 0x0003 = ECDSA-SHA512-P521 +
      • 0x0004 = RSA-SHA256-2048 +
      • 0x0005 = RSA-SHA384-3072 +
      • 0x0006 = RSA-SHA512-4096 +
      -9 Version length (in bytes not chars, including padding) +10-11 Signature length, e.g. 40 (0x0028) for DSA-160 + +12 unused + +13 Version length (in bytes not chars, including padding) must be at least 16 (0x10) for compatibility -10 unused +14 unused -11 Signer ID length (in bytes not chars) +15 Signer ID length (in bytes not chars) -12-19 Compressed content length (not including header or sig) - -20 unused - -21 Compressed type 0x00 = zip - -22 unused - -23 Content type 0x00 = router w/o pack200, 0x01 = router w/ pack200, 0x02 = plugin +16-23 Compressed content length (not including header or sig) 24 unused -25 Signature type 0x00 = DSA-160, 0x01 = new algo +25 Compressed type 0x00 = zip -26-27 Signature length 40 (0x0028) = DSA-160 +26 unused + +27 Content type +
      • 0x00 = unknown +
      • 0x01 = router update +
      • 0x02 = plugin or plugin update +
      • 0x03 = reseed data +
      28-39 unused diff --git a/i2p2www/pages/site/docs/transport/index.html b/i2p2www/pages/site/docs/transport/index.html index ab1b7b11..6cf01f95 100644 --- a/i2p2www/pages/site/docs/transport/index.html +++ b/i2p2www/pages/site/docs/transport/index.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}{% trans %}Transport Overview{% endtrans %}{% endblock %} -{% block lastupdated %}{% trans %}April 2013{% endtrans %}{% endblock %} -{% block accuratefor %}0.9.5{% endblock %} +{% block lastupdated %}{% trans %}December 2013{% endtrans %}{% endblock %} +{% block accuratefor %}0.9.9{% endblock %} {% block content %}

      {% trans %}Transports in I2P{% endtrans %}

      @@ -34,9 +34,16 @@ flow control, acknowledgments and retransmission. The transport subsystem in I2P provides the following services: {%- endtrans %}

        +
      • {% trans i2np=site_url('docs/protocol/i2np') -%} +Reliable delivery of I2NP messages. +Transports support I2NP message delivery ONLY. +They are not general-purpose data pipes. +{%- endtrans %}
      • {% trans -%} Maintain a set of router addresses, one or more for each transport, -that the router publishes as its global contact information (the RouterInfo) +that the router publishes as its global contact information (the RouterInfo). +Each transport may connect using one of these addresses, which may be +IPv4 or (as of version 0.9.8) IPv6. {%- endtrans %}
      • {% trans %}Selection of the best transport for each outgoing message{% endtrans %}
      • {% trans %}Queueing of outbound messages by priority{% endtrans %}
        • @@ -70,6 +77,7 @@ and refusing outbound and inbound connections to those peers

        {% trans -%} The transport subsystem maintains a set of router addresses, each of which lists a transport method, IP, and port. These addresses constitute the advertised contact points, and are published by the router to the network database. +Addresses may also contain an arbitrary set of additional options. {%- endtrans %}

        {% trans %}Typical scenarios are:{% endtrans %} @@ -90,7 +98,7 @@ directly-accessible IP and ports.

        {% trans i2np=site_url('docs/protocol/i2np'), streaming=site_url('docs/api/streaming'), datagrams=site_url('docs/api/datagrams') -%} -The transport system delivers I2NP messages. The transport selected for any message is +The transport system delivers I2NP messages only. The transport selected for any message is independent of the upper-layer protocols and contents (router or client messages, whether an external application was using TCP or UDP to connect to I2P, whether the upper layer was using the streaming library @@ -139,12 +147,6 @@ Additional transports may be developed, including:

      • {% trans %}An "indirect" transport for routers that are not reachable by all other routers (one form of "restricted routes"){% endtrans %}
      -

      {% trans thread='http://'+i2pconv('zzz.i2p')+'/topics/109' -%} -IPv6: The existing transports must be enhanced to support multiple addresses within a single transport, -including IPV6 addresses. Currently, a transport may only advertise a single IPV4 address. -See this thread for discussion. -{%- endtrans %}

      -

      {% trans -%} Work continues on adjusting default connection limits for each transport. I2P is designed as a "mesh network", where it is assumed that any router can connect to any other router. @@ -159,7 +161,7 @@ However, as NTCP buffers are partially in the kernel and SSU buffers are on the that assumption is difficult to verify. {%- endtrans %}

      -

      {% trans pdf='http://www.cse.chalmers.se/%7Ejohnwolf/publications/hjelmvik_breaking.pdf' -%} +

      {% trans pdf='http://www.iis.se/docs/hjelmvik_breaking.pdf' -%} Analyze Breaking and Improving Protocol Obfuscation and see how transport-layer padding may improve things. {%- endtrans %}

      diff --git a/i2p2www/pages/site/docs/transport/ntcp.html b/i2p2www/pages/site/docs/transport/ntcp.html index 25aac00e..7fda9370 100644 --- a/i2p2www/pages/site/docs/transport/ntcp.html +++ b/i2p2www/pages/site/docs/transport/ntcp.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}NTCP{% endblock %} -{% block lastupdated %}{% trans %}August 2010{% endtrans %}{% endblock %} -{% block accuratefor %}0.8{% endblock %} +{% block lastupdated %}{% trans %}December 2013{% endtrans %}{% endblock %} +{% block accuratefor %}0.9.9{% endblock %} {% block content %}

      {% trans %}NTCP (NIO-based TCP){% endtrans %}

      @@ -10,6 +10,7 @@ NTCP is one of two transports currently implement The other is SSU. NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22. Java NIO (new I/O) does not suffer from the 1 thread per connection issues of the old TCP transport. +NTCP-over-IPv6 is supported as of version 0.9.8. {%- endtrans %}

      {% trans -%} @@ -118,16 +119,18 @@ The mapping between these steps and the messages sent between I2P routers, is marked in bold. {%- endtrans %}

        -
      1. {% trans %}Alice generates a secret 226-bit integer x. She then calculates X = g^x mod p.{% endtrans %}
        2. +
      2. {% trans %}Alice generates a secret integer x. She then calculates X = g^x mod p.{% endtrans %}
      3. {% trans %}Alice sends X to Bob (Message 1).{% endtrans %}
        4. -
      4. {% trans %}Bob generates a secret 226-bit integer y. He then calculates Y = g^y mod p.{% endtrans %}
        5. +
      5. {% trans %}Bob generates a secret integer y. He then calculates Y = g^y mod p.{% endtrans %}
      6. {% trans %}Bob sends Y to Alice.(Message 2){% endtrans %}
      7. {% trans %}Alice can now compute sessionKey = Y^x mod p.{% endtrans %}
      8. {% trans %}Bob can now compute sessionKey = X^y mod p.{% endtrans %}
      9. {% trans %}Both Alice and Bob now have a shared key sessionKey = g^(x*y) mod p.{% endtrans %}
      -

      {% trans -%} +

      {% trans crypto=site_url('docs/how/cryptography') -%} The sessionKey is then used to exchange identities in Message 3 and Message 4. +The exponent (x and y) length for the DH exchange is documented on the +cryptography page. {%- endtrans %}

      {% trans %}Message 1 (Session Request){% endtrans %}

      diff --git a/i2p2www/pages/site/docs/transport/ssu.html b/i2p2www/pages/site/docs/transport/ssu.html index d846503c..131a3cc9 100644 --- a/i2p2www/pages/site/docs/transport/ssu.html +++ b/i2p2www/pages/site/docs/transport/ssu.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}{% trans %}SSU Transport{% endtrans %}{% endblock %} -{% block lastupdated %}{% trans %}May 2013{% endtrans %}{% endblock %} -{% block accuratefor %}0.9.6{% endblock %} +{% block lastupdated %}{% trans %}December 2013{% endtrans %}{% endblock %} +{% block accuratefor %}0.9.9{% endblock %} {% block content %}

      {% trans %}Secure Semireliable UDP{% endtrans %} (SSU)

      Note: IPv6 information is preliminary. @@ -16,6 +16,7 @@ The other is NTCP. SSU is the newer of the two transports, introduced in I2P release 0.6. In a standard I2P installation, the router uses both NTCP and SSU for outbound connections. +SSU-over-IPv6 is supported as of version 0.9.8. {%- endtrans %}

      {% trans %}SSU Services{% endtrans %}

      @@ -81,7 +82,7 @@ The MTU value is adjusted based on the percentage of packets that are retransmit {%- endtrans %}

      {% trans -%} -For both MTU values, it is desirable that (MTU % 16) == 12, so that +For both MTU values, it is desirable that (MTU % 16) == 12, so that the payload portion after the 28-byte IP/UDP header is a multiple of 16 bytes, for encryption purposes. {%- endtrans %}

      @@ -118,7 +119,8 @@ honor that when a connection is established.

      {% trans -%} For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes, -so we use an MTU where (MTN % 16 == 0), which is true for 1280. +so we use an MTU where (MTN % 16 == 0), which is true for 1280. +The maximum IPv6 MTU is 1472. {%- endtrans %}

      {% trans %}Message Size Limits{% endtrans %}

      @@ -239,6 +241,7 @@ The message sequence is as follows:

      {% trans %}Connection establishment (direct){% endtrans %}

      {% trans -%} Alice connects directly to Bob. +IPv6 is supported as of version 0.9.8. {%- endtrans %}

      {% highlight %} Alice Bob @@ -344,8 +347,9 @@ After the hole punch, the session is established between Alice and Charlie as in

      IPv6 notes: +IPv6 is supported as of version 0.9.8. Alice-Bob communication may be via IPv4 or IPv6. -Bob-Charlie and Alice-Charlie communication is via IPv4. +Bob-Charlie and Alice-Charlie communication is via IPv4 only.

      diff --git a/i2p2www/pages/site/docs/tunnels/old-implementation.html b/i2p2www/pages/site/docs/tunnels/old-implementation.html index 88c5c40d..456f0c25 100644 --- a/i2p2www/pages/site/docs/tunnels/old-implementation.html +++ b/i2p2www/pages/site/docs/tunnels/old-implementation.html @@ -492,7 +492,7 @@ vulnerability to predecessor attacks. While the endpoints and gateways of those tunnels will be randomly distributed across the network (perhaps even including the tunnel creator in that set), another alternative is to use the tunnel pathways themselves to pass along the request and response, as is done -in TOR. This, however, may lead to leaks +in TOR. This, however, may lead to leaks during tunnel creation, allowing peers to discover how many hops there are later on in the tunnel by monitoring the timing or packet count as the tunnel is built. Techniques could be used to minimize this issue, such as using each of diff --git a/i2p2www/pages/site/faq.html b/i2p2www/pages/site/faq.html index f0e8ac46..153de3f6 100644 --- a/i2p2www/pages/site/faq.html +++ b/i2p2www/pages/site/faq.html @@ -50,8 +50,8 @@

      {% trans %}What systems will I2P run on?{% endtrans %} ({{ _('link') }})

      -

      {% trans trac=i2pconv('trac.i2p2.i2p') -%} -While I2P has been reported to run PCs as meagre as a low-end Pentium II with 64 MB of RAM, you'll have a much better experience on a Pentium III (or better) with 128MB of RAM (or more). A chart comparing the performance of the various JREs can be found at http://{{ trac }}/wiki/java, but in short: it's at all possible, use Sun/Oracle Java or OpenJDK. +

      {% trans chart='https://trac.i2p2.de/wiki/java' -%} +While I2P has been reported to run PCs as meagre as a low-end Pentium II with 64 MB of RAM, you'll have a much better experience on a Pentium III (or better) with 128MB of RAM (or more). A chart comparing the performance of the various JREs can be found at {{ chart }}, but in short: it's at all possible, use Sun/Oracle Java or OpenJDK. {%- endtrans %}

      {% trans -%} @@ -66,7 +66,7 @@ I2P has been tested on Windows, Linux, FreeBSD (see the note -

    • {{ i2pconv('trac.i2p2.i2p') }} ticket (preferred method)
      • +
    • {{ i2pconv('trac.i2p2.i2p') }} ticket (preferred method)
    • {{ i2pconv('pastethis.i2p') }} and follow up on IRC in #i2p
    • {% trans -%} Discuss with the developers on IRC in #i2p-dev @@ -101,6 +101,7 @@ Presence on this list does not imply endorsement.
      • http://i2host.i2p/cgi-bin/i2hostetag
      • http://stats.i2p/cgi-bin/newhosts.txt
        • +
      • http://no.i2p/export/alive-hosts.txt
        • @@ -159,7 +160,7 @@ garbage collection. Increase the setting wrapper.java.maxmemory in
      • {% trans -%} -Is the CPU usage simply higher than you would like, or is it pegged at 100% for a long time? +Is the CPU usage simply higher than you would like, or is it pegged at 100% for a long time? If it's pegged, this could be a bug. Look in the logs for clues. {%- endtrans %}
        • @@ -203,7 +204,7 @@ All traffic you route is internal to the I2P network, you are not an {% trans %}Is my router an "exit node" to the regular Internet? I don't want it to be.{% endtrans %} ({{ _('link') }})

        {% trans -%} -No. Unlike Tor, +No. Unlike Tor, "exit nodes" or "outproxies" are not an inherent part of the network. Only volunteers who set up and run separate applications will relay traffic to the regular Internet. There are very, very few of these. @@ -290,7 +291,7 @@ and set your outproxy list to 'false.i2p' (only). Then stop and restart the eepProxy. If it doesn't work, the outproxy is not up. It is not I2P's fault. If your primary reason to use an anonymous network is to anonymously access sites -on the regular Internet, you should probably try Tor. +on the regular Internet, you should probably try Tor. {%- endtrans %}

        {% trans %}I can't access https:// or ftp:// sites through I2P.{% endtrans %} @@ -368,16 +369,16 @@ There is additional discussion about this on Tor. +If this type of service is required, try Tor. {%- endtrans %}

        {% trans %}Most of the eepsites within I2P are down?{% endtrans %} ({{ _('link') }})

        -

        {% trans perv=i2pconv('perv.i2p') -%} +

        {% trans eepstatus='http://'+i2pconv('identiguy.i2p') -%} If you consider every eepsite that has ever been created, yes, most of them are down. People and eepsites come and go. A good way to get started in I2P is check out a list of eepsites that are currently up. -{{ perv }} tracks active eepsites. +{{ eepstatus }} tracks active eepsites. {%- endtrans %}

        {% trans %}How do I set up my own eepsite?{% endtrans %} @@ -450,8 +451,8 @@ with
      • {% trans -%} -Go to http://localhost:7657/configadvanced.jsp -and add a new option: consolePassword=foo (or whatever password you want) +Go to http://localhost:7657/configui +and add a console username and password if desired. {%- endtrans %}
      • @@ -463,10 +464,10 @@ and hit "Graceful restart", which restarts the JVM and reloads the client applic

        {% trans -%} -After that fires up, you should now be able to reach your console remotely. -You will be prompted for a username and password though - the username is -"admin" and the password is whatever you specified in step 2 above. Note: the -0.0.0.0 above specifies an interface, not a network or netmask. 0.0.0.0 +After that fires up, you should now be able to reach your console remotely. Reload the router at +http://127.0.0.1:7657 and you will be prompted for the username and password you specified in step 2 +above if your browser supports the authentication popup. Note: the +0.0.0.0 above specifies an interface, not a network or netmask. 0.0.0.0 means "bind to all interfaces", so it can be reachable on 127.0.0.1:7657 as well as any LAN/WAN IP. {%- endtrans %}

        diff --git a/i2p2www/pages/site/get-involved/bounties/index.html b/i2p2www/pages/site/get-involved/bounties/index.html index 4ccb7c7d..3a8d5f91 100644 --- a/i2p2www/pages/site/get-involved/bounties/index.html +++ b/i2p2www/pages/site/get-involved/bounties/index.html @@ -49,13 +49,6 @@ etc), and the like.

        [{{ _('vacant') }}]

        €100 EUR

        - -

        {{ _('Make I2P IPv6 native') }}

        -

        {{ _('Proposal in development') }}

        -

        Amiga4000

        -

        [{{ _('vacant') }}]

        -

        €100 EUR and 50BTC

        -

        {{ _('I2P package in Debian and Ubuntu mirrors') }}

        {{ _('Proposal in development') }}

        @@ -68,7 +61,7 @@ etc), and the like.

        {{ _('Done, phase of verification') }}

        psychonaut

        giv

        -

        €30 EUR and 118,34BTC

        +

        €30 EUR and 118,34BTC, of which 30 EUR and 68BTC paid to giv

        {{ _('Unit tests and Multi-router Simulation') }}

        @@ -110,6 +103,13 @@ etc), and the like. + + + + + + + @@ -152,7 +152,7 @@ etc), and the like. - +

        {{ _('Name') }}

        {{ _('Status') }}

        {{ _('Dev team') }}*

        {{ _('Make I2P IPv6 native') }}

        done

        Amiga4000

        I2P team

        €100 EUR and 50BTC

        {{ _('Setting up a SILC server') }}

        withdrawn and bounty divided between ReturningNovice and the general fund

        GCJ support

        Claimed

        Claimed

        jrandom
        diff --git a/i2p2www/pages/site/get-involved/bounties/ipv6.html b/i2p2www/pages/site/get-involved/bounties/ipv6.html index 0da3382d..aa05ef8d 100644 --- a/i2p2www/pages/site/get-involved/bounties/ipv6.html +++ b/i2p2www/pages/site/get-involved/bounties/ipv6.html @@ -9,6 +9,8 @@ into I2P I withdrawal the vuze bounty and offer a IPv6 bounty. To claim this bounty, the I2P router needs to run full on native IPv6 connections like it does on IPv4. {%- endtrans %}

        +
        +Bounty is done as of I2P 0.9.8 and money paid to the I2P team. {% endblock %} {% block bountynotes %} diff --git a/i2p2www/pages/site/get-involved/bounties/netdb.html b/i2p2www/pages/site/get-involved/bounties/netdb.html index 2d0b1aed..48474a6f 100644 --- a/i2p2www/pages/site/get-involved/bounties/netdb.html +++ b/i2p2www/pages/site/get-involved/bounties/netdb.html @@ -27,7 +27,7 @@ completed and should therefore be minimized.
        Attack resilience
        The solution should ideally be (or be extensible to be) resilient against -sybil and eclipse attacks. +sybil and eclipse attacks.
        Scalability
        @@ -53,7 +53,7 @@ still maintain an unlimited search horizon. -Trac +Trac

        162.5€

        @@ -73,7 +73,7 @@ still maintain an unlimited search horizon.
        i2p.zzz.kademlia / i2psnarkdht is the most likely base implementation.
        -

        Trac

        +

        Trac

        162.5€

        diff --git a/i2p2www/pages/site/get-involved/bounties/unit-tests.html b/i2p2www/pages/site/get-involved/bounties/unit-tests.html index 9a14fe2c..6e61930a 100644 --- a/i2p2www/pages/site/get-involved/bounties/unit-tests.html +++ b/i2p2www/pages/site/get-involved/bounties/unit-tests.html @@ -93,7 +93,7 @@ To collect this bounty, the automated unit tests of the router

        {% trans -%} To collect this bounty, a new set of unit tests must meet a -measured code coverage of 90% of the streaming lib +measured code coverage of 90% of the streaming lib (i2p/apps/ministreaming/ and i2p/apps/streaming/). {%- endtrans %}


        @@ -104,7 +104,7 @@ measured code coverage of 90% of the streaming lib {%- endtrans %}

        {% trans -%} -To collect this bounty, all above unit tests must meet the 100% +To collect this bounty, all above unit tests must meet the 100% coverage marker (except for log statements). {%- endtrans %}


        diff --git a/i2p2www/pages/site/get-involved/develop/applications.html b/i2p2www/pages/site/get-involved/develop/applications.html index 79659d97..d23578d4 100644 --- a/i2p2www/pages/site/get-involved/develop/applications.html +++ b/i2p2www/pages/site/get-involved/develop/applications.html @@ -578,9 +578,9 @@ Contact us if you would like to contribute. I2Phex

      -See also all the plugins on plugins.i2p, -the applications and source code listed on echelon.i2p, -and the application code hosted on git.repo.i2p. +See also all the plugins on plugins.i2p, +the applications and source code listed on echelon.i2p, +and the application code hosted on git.repo.i2p.

      See also the bundled applications in the I2P distribution - SusiMail and I2PSnark.

      diff --git a/i2p2www/pages/site/get-involved/develop/developers-keys.html b/i2p2www/pages/site/get-involved/develop/developers-keys.html index 48d69fa4..7326151b 100644 --- a/i2p2www/pages/site/get-involved/develop/developers-keys.html +++ b/i2p2www/pages/site/get-involved/develop/developers-keys.html @@ -236,6 +236,21 @@ gO8flnqsOSGb2CtoQ3i3Fqk0HNq2if47LVyaLwgOyoPOhYkDDGr9Wg gBp+svAHALMoGvh0lemKQZpQfdMgZ33k2l2o3Udvj3tpB/KwIDAQAB [end] +[pubkey digit@mail.i2p] +MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDAo+xF9MoHp2S4T/ +smvUtDL7Qcjis5LyqDYELo/IqER5Nn4CNNA9SCrBKm6nlzDjAj7X8J +zbTTvOT9WqTzwHrWjNcG4rAWsG22kbvtlujy3sbgO7VckQolzm+psM +mySqVwAzOZm9ShSxBeb99oULNQwRaW+QrGiB2mBFeCnY1kywIDAQAB +[end] + + +[pubkey dg2-new@mail.i2p] +MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDtrD2xv9Hvsa+VY9 +ymQ2BgNzDenRz9xuSsrhVNqAjKVHs47J/qm7693NhnGlLxofeiF3py +982CcCjnyEa3IfBD82dsuBgYUj09GVhcJyaA1ttNBNSCh5pDJfGFBs +pLYjMbWl/TAdlxkWm+HgRCzhQe5vkLcx1R8nXCxmPjC0Ep3QIDAQAB +[end] +

      {{ _('Developer Transport Keys') }}

      {% trans monotone=site_url('get-involved/guides/monotone') -%} @@ -405,6 +420,13 @@ At7mOUETxO3sLrf70kR9Mn4p44c4NKuFF4APmeYaFfIP9N5ZkBxY+5 hMMlffgZFJeDIEEed3eIttUPsIdW8U+2XQM1zF9R77+K0ZJQIDAQAB [end] +[pubkey dg2-transport-new@mail.i2p] +MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC4YQS3iFx7unaWtY +FFX4VuT/m5o5012LF5UU9LFJmnnnPQpJzTwRrBN8WKFm5AACbg/pdR +PzTJpv6C0kKDavKddKxc4HIuNKnTsB1qd5zOpKBNlxm6TT4N3Pdhb5 +CEXZ1lvlv4PloKFIti7ptAa4HpTs6Gd3a6nMQyHwgP0Ke44wIDAQAB +[end] + {% endblock %} diff --git a/i2p2www/pages/site/get-involved/develop/license-agreements.html b/i2p2www/pages/site/get-involved/develop/license-agreements.html index 2a756ac0..e5219ff0 100644 --- a/i2p2www/pages/site/get-involved/develop/license-agreements.html +++ b/i2p2www/pages/site/get-involved/develop/license-agreements.html @@ -792,6 +792,33 @@ Zf9i4Wqw8wKgkWIIbZ2+V+zP83FLcX6ga+GMr8tf/bwWjSe1PN7mZAQlPB4p8Qc= =NxxT -----END PGP SIGNATURE----- +dg: + +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA1 + +I affirm the following with regard to I2P: + + * Unless marked otherwise, all code I commit is implicitly licensed under the component's primary license + * If specified in the source, the code may be explicitly licensed under one of the component's alternate licenses + * I have the right to release the code I commit under the terms I am committing it + +-----BEGIN PGP SIGNATURE----- + +iQIcBAEBAgAGBQJSbZwRAAoJEOLR0LYl1+FTlSIP/1+FGMm08vLk7V7v7fxKrHHf +GOmUa5p706sVMKVjM5cgBAkd1qkon5QKwjDOOHxeN9vu2EZbicRawn19YaOOHje5 +peW4n/guYb8osflGNkBH3vy3EekB/PfuppIxjM7HeO08rJ9VrrYa6hseYvdVpMsi +E2LtF4kMekXxOvuQI4kKL0gT+KCW7OtLWVkRzhsDqLMyP/5JG3uTcI/PAe+y2Iip +ZZBLLkf9gBdPGOk/NeSEX510jlKqSC7TcyVnQe+BH0oLNG2SzlzeFpiTKdKObiq8 +O9rxW2yga6+7bPIgoaoxEK2zzHEGubqqHKgMUQKHs4IW3TYEGBFeCK6HUXpvObIh +wuZK32JDZCytAzV8VcPWlA2tOInkdHZj5A5K1idvM7BLSQ2b1xzRbkflER9ZaPQ6 +NDpkz8fiJYgIU7G8CqTK/8y9bjD+zITz3yOSAM3BGax/NeIs86drovgu2B1CeE0L +BXB/UwWZQhSE1W9AZJvbkPm4wLd9g8DihOJHArbxpEDj97W+faLGLLejm8lLB2Z5 +uBQwb4YM5Lt3FKQPqT8h6yRNtU5inIdrzbQEcKlMfOGiuKxXFlTfxAAJkOLnnK8c +OFE4iD6nFr78yT/jo1BOOc1gs+xiq3P+Cxaa95v/F08JTwwwLqA/94PjTs57I2Ef +cFuIq+msmE5mtJW+czFE +=syT4 +-----END PGP SIGNATURE----- {% endblock %} diff --git a/i2p2www/pages/site/get-involved/donate.html b/i2p2www/pages/site/get-involved/donate.html index 3d4e7c3b..ca585707 100644 --- a/i2p2www/pages/site/get-involved/donate.html +++ b/i2p2www/pages/site/get-involved/donate.html @@ -7,7 +7,38 @@ The details of how you can make your contribution are provided below. {%- endtrans %}

      +

      Bitcoin

      +

      {% trans date='December 2010', +cointype='Bitcoin', +coinurl='http://bitcoin.org', +account='1HkJCceXf7of1sTNRVJbXiZHfDTLL71Siy' -%} +As of {{ date }}, eche|on has been running a +{{ cointype }} account for the I2P project. +If you'd like to donate using {{ cointype }}, just transfer your +desired amount of coins to the account {{ account }} +and leave eche|on a note if you'd like your donation to be +mentioned on the I2P webpage. +{%- endtrans %}

      +

      {% trans %}For easy usage, use the QR code below!{% endtrans %}

      +BTC donation QR code +
      +

      Litecoin

      +

      {% trans date='September 2013', +cointype='Litecoin', +coinurl='http://www.litecoin.org', +account='LefFK8mk55zzfNkongAeVSiJ5rmrCkxdx5' -%} +As of {{ date }}, eche|on has been running a +{{ cointype }} account for the I2P project. +If you'd like to donate using {{ cointype }}, just transfer your +desired amount of coins to the account {{ account }} +and leave eche|on a note if you'd like your donation to be +mentioned on the I2P webpage. +{%- endtrans %}

      +

      {% trans %}For easy usage, use the QR code below!{% endtrans %}

      +LTC donation QR code + +

      PayPal


      {% trans account='echelon@i2pmail.org' -%} @@ -86,12 +117,8 @@ You can donate direct via PayPal to the account "{{ account }}". {{ _('Flattr this') }}

      -

      Bitcoin

      -

      {% trans account='1HkJCceXf7of1sTNRVJbXiZHfDTLL71Siy' -%} -As of December 2010, eche|on has been running a Bitcoin account for the I2P project. -If you'd like to donate using Bitcoin, just transfer your desired amount of coins to the account -{{ account }} and leave eche|on a note if you'd like your donation to be mentioned on the I2P webpage. -{%- endtrans %}

      + +

      SnailMail

      {% trans -%} If you want to keep more or less anonymous, the option to send money via mail is also available. But it is less secure as the envelope can be lost on the way to us. diff --git a/i2p2www/pages/site/get-involved/guides/monotone.html b/i2p2www/pages/site/get-involved/guides/monotone.html index 362b62f1..075598a4 100644 --- a/i2p2www/pages/site/get-involved/guides/monotone.html +++ b/i2p2www/pages/site/get-involved/guides/monotone.html @@ -228,7 +228,7 @@

      {% trans -%} - The default Monotone trust policy is way too lax for our requirements: every comitter is trusted by default. + The default Monotone trust policy is way too lax for our requirements: every committer is trusted by default. That is not acceptable for I2P development. {%- endtrans %}

      @@ -349,7 +349,7 @@ directory where i2p.mtn was created and attempt a checkout of the I {% trans -%} If you are satisfied with results, restore the backup of monotonerc that was created above. If you didn't create a backup - as advised, re-read Setting up trust evaluation hools. + as advised, re-read Setting up trust evaluation hooks. {%- endtrans %}

      diff --git a/i2p2www/pages/site/get-involved/guides/new-developers.html b/i2p2www/pages/site/get-involved/guides/new-developers.html index 277b62f0..d935e00f 100644 --- a/i2p2www/pages/site/get-involved/guides/new-developers.html +++ b/i2p2www/pages/site/get-involved/guides/new-developers.html @@ -102,7 +102,7 @@ The initial pull may take several hours using the tunnel. If it fails after a partial pull, simply rerun it, it will start where it left off. If you are in a hurry, use the non-anonymous access. {%- endtrans %}

      -

      {% trans viewmtn='http://'+i2pconv('stats.i2p')+'/cgi-bin/viewmtn/' -%} +

      {% trans viewmtn='http://'+i2pconv('killyourtv.i2p')+'/viewmtn/' -%} A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn. {%- endtrans %}

      {% trans monotone=site_url('get-involved/guides/monotone') -%} @@ -131,10 +131,10 @@ see the application development guide. {%- endtrans %}

      {% trans %}Development ideas{% endtrans %}

      -

      {% trans zzz=i2pconv('zzz.i2p'), todo=site_url('get-involved/todo'), trac=i2pconv('trac.i2p2.i2p') -%} +

      {% trans zzz=i2pconv('zzz.i2p'), todo=site_url('get-involved/todo'), trac='https://trac.i2p2.de/report/1' -%} See zzz's TODO lists, this website's TODO list or -Trac +Trac for ideas. {%- endtrans %}

      diff --git a/i2p2www/pages/site/get-involved/index.html b/i2p2www/pages/site/get-involved/index.html index e73b584e..3d9636d6 100644 --- a/i2p2www/pages/site/get-involved/index.html +++ b/i2p2www/pages/site/get-involved/index.html @@ -22,9 +22,10 @@ Fix up the Wikipedia article about I2P in your language. Tell your friends. {%- endtrans %}
    • {{ _('Testing') }} — -{% trans monotone=site_url('get-involved/guides/monotone'), trac=i2pconv('trac.i2p2.i2p') -%} +{% trans monotone=site_url('get-involved/guides/monotone'), +trac='https://trac.i2p2.de/report/1' -%} Run the latest builds from monotone -and report results on #i2p or as bugs on Trac. +and report results on #i2p or as bugs on Trac. {%- endtrans %}
    • {{ _('Documentation') }} — {% trans -%} @@ -51,9 +52,11 @@ Write or port applications for I2P! There's some guidelines and a list of ideas on the applications page. {%- endtrans %}
    • {{ _('Coding') }} — -{% trans trac=i2pconv('trac.i2p2.i2p'), zzz=i2pconv('zzz.i2p'), newdevs=site_url('get-involved/guides/new-developers') -%} +{% trans trac='https://trac.i2p2.de/report/1', +zzz=i2pconv('zzz.i2p'), +newdevs=site_url('get-involved/guides/new-developers') -%} There's plenty to do if you know Java or are ready to learn. -Check for open tickets on Trac +Check for open tickets on Trac or the TODO list on {{ zzz }} for some ideas on where to start. See the new developer's guide for details. diff --git a/i2p2www/pages/site/index.html b/i2p2www/pages/site/index.html index a8e7237b..1b483657 100644 --- a/i2p2www/pages/site/index.html +++ b/i2p2www/pages/site/index.html @@ -13,13 +13,16 @@

      {{ _('What is I2P?') }}

      • {% trans -%} -I2P is a full darknet implementation - a network within a network, and is intended to protect against monitoring by third parties, such as hostile governments or ISPs. +I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs. {% endtrans %}
      • {% trans -%} -I2P is used by many people who care about their privacy, as well as those in high-risk situations. It is designed to protect activists, oppressed people, journalists and whistle-blowers - as well as the average person. +I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person. {% endtrans %}
      • {% trans -%} -I2P runs on Java and is therefore available anywhere Java will run, including desktops, embedded systems (like the Raspberry Pi) and Android phones. +No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review. +{% endtrans %}
        • +
      • {% trans -%} +I2P is available on desktops, embedded systems (like the Raspberry Pi) and Android phones. Help spread the word! {% endtrans %}
      • {% trans %}Read more…{% endtrans %} @@ -31,37 +34,37 @@ I2P runs on Java and is therefore available anywhere Java will run, including de
        • {% trans supported=site_url('docs/applications/supported') -%} - Email Integrated web mail interface, plugin for serverless email. + Email: Integrated web mail interface, plugin for serverless email. {%- endtrans %}
        • {% trans supported=site_url('docs/applications/supported') -%} - Web browsing Anonymous websites, gateways to and from the public Internet. + Web browsing: Anonymous websites, gateways to and from the public Internet. {%- endtrans %}
        • {% trans supported=site_url('docs/applications/supported') -%} - Blogging and forums Blogging and Syndie plugins. + Blogging and forums: Blogging and Syndie plugins. {%- endtrans %}
        • {% trans supported=site_url('docs/applications/supported') -%} - Website hosting Integrated anonymous web server. + Website hosting: Integrated anonymous web server. {%- endtrans %}
        • {% trans supported=site_url('docs/applications/supported') -%} - Real-time chat Instant messaging and IRC clients. + Real-time chat: Instant messaging and IRC clients. {%- endtrans %}
        • {% trans supported=site_url('docs/applications/supported') -%} - File sharing ED2K and Gnutella clients, integrated BitTorrent client. + File sharing: ED2K and Gnutella clients, integrated BitTorrent client. {%- endtrans %}
        • {% trans supported=site_url('docs/applications/supported') -%} - Decentralized file storage Tahoe-LAFS distributed filesystem plugin. + Decentralized file storage: Tahoe-LAFS distributed filesystem plugin. {%- endtrans %}
        • diff --git a/i2p2www/pages/site/links.html b/i2p2www/pages/site/links.html index eb137ba3..63b096e0 100644 --- a/i2p2www/pages/site/links.html +++ b/i2p2www/pages/site/links.html @@ -9,18 +9,26 @@ See also the page with
            +

            {{ _('I2P on the web') }}

            +
          • Free Software Directory
            • +
          • Freecode
            • +
          • Launchpad
            • +
          • Ohloh
            • +
          • Softpedia
            • +
          • Transifex
            • +
          • Wikipedia

            • {{ _('Friends of I2P') }}

          • Anomos Pseudonymous Encrypted Bittorrent
          • EFF
          • GNUnet
          • Ipredator
            • -
          • InfoSec Daily Podcast
            • +
          • Onioncat
          • Relakks
            • -
          • The Pegasus Project
            • -
          • The Pegasus Press
            • + +
          • Telecomix
            • -
          • Tor
            • +
          • Tor

            • {{ _('More Projects and Documentation') }}

          • Freehaven's Anonymity Bibliography
          • GNUNet's related projects
            • diff --git a/i2p2www/pages/site/misc/benchmarks.html b/i2p2www/pages/site/misc/benchmarks.html index cfad236b..6ff72db7 100644 --- a/i2p2www/pages/site/misc/benchmarks.html +++ b/i2p2www/pages/site/misc/benchmarks.html @@ -248,7 +248,7 @@ speeds because time is needed to transfer data to and from memory. For the ciphers that specify big endian byte order, the timing data listed include time needed to convert to and from little endian order. For some ciphers (WAKE and SHA) this is a large fraction (up -to 25%) of the total time. +to 25%) of the total time.
          • The RSA, RW, DH, MQV, and elliptic curve schemes come from the IEEE P1363 standard. For more info see diff --git a/i2p2www/pages/site/misc/clt.html b/i2p2www/pages/site/misc/clt.html index f3264513..ba330533 100644 --- a/i2p2www/pages/site/misc/clt.html +++ b/i2p2www/pages/site/misc/clt.html @@ -11,7 +11,7 @@ On 14th march of 2009 there will be a short talk about general introduction to I 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! {%- endtrans %}

            -

            {% trans petcon='http://www.pet-con.org/index.php/PET_Convention_2009.1' -%} +

            {% trans petcon='http://web.archive.org/web/20100413184504/http://www.pet-con.org/index.php/PET_Convention_2009.1' -%} Just 10 days later the Privacy and Data Security convention in Dresden will take place. Again, echelon will attend this event and hold a short talk about general introduction to I2P. Another talk about the profiling by the I2P clients will be held. {%- endtrans %}

            diff --git a/i2p2www/pages/site/misc/jbigi.html b/i2p2www/pages/site/misc/jbigi.html index caa4123f..48769133 100644 --- a/i2p2www/pages/site/misc/jbigi.html +++ b/i2p2www/pages/site/misc/jbigi.html @@ -123,7 +123,7 @@ info, it will be something like this: {%- endtrans %}
             native run time:  5842ms ( 57ms each)
 java run time:   41072ms (406ms each)
-native = 14.223802103622907% of pure java time
+native = 14.223802103622907% of pure java time
            {% trans %}If the native is indeed 5-7x faster (or more) then it looks all good. If not, please report.{% endtrans %}
          • {% trans %}Copy libjbigi.so to your i2p directory{% endtrans %}
            • diff --git a/www.i2p2/pages/translations/pressetext-0.7.html b/i2p2www/pages/site/misc/pressetext-0.7.html similarity index 99% rename from www.i2p2/pages/translations/pressetext-0.7.html rename to i2p2www/pages/site/misc/pressetext-0.7.html index 02050ba6..c7dd6d80 100644 --- a/www.i2p2/pages/translations/pressetext-0.7.html +++ b/i2p2www/pages/site/misc/pressetext-0.7.html @@ -1,4 +1,4 @@ -{% extends "_layout.html" %} +{% extends "global/layout.html" %} {% block title %}0.7 Release{% endblock %} {% block content %} 
            diff --git a/i2p2www/pages/site/misc/ratestats.html b/i2p2www/pages/site/misc/ratestats.html
index 6a1fb1ac..9318cd75 100644
--- a/i2p2www/pages/site/misc/ratestats.html
+++ b/i2p2www/pages/site/misc/ratestats.html
@@ -135,7 +135,7 @@ netDb.writeOut
 netDb.writePending
 netDb.writeTime
 ntcp.accept
-ntcp.attemptShitlistedPeer
+ntcp.attemptBanlistedPeer
 ntcp.attemptUnreachablePeer
 ntcp.bidRejectedLocalAddress
 ntcp.bidRejectedNoNTCPAddress
@@ -288,7 +288,7 @@ swarm." + getConnectionId() + ".totalReceived
 transport.bidFailAllTransports
 transport.bidFailNoTransports
 transport.bidFailSelf
-transport.bidFailShitlisted
+transport.bidFailBanlisted
 transport.expiredOnQueueLifetime
 transport.getBidsJobTime
 transport.noBidsYetNotAllUnreachable
@@ -304,7 +304,7 @@ transport.sendMessageMedium
 transport.sendMessageSize
 transport.sendMessageSmall
 transport.sendProcessingTime
-transport.shitlistOnUnreachable
+transport.banlistOnUnreachable
 tunnel.acceptLoad
 tunnel.batchCount
 tunnel.batchDelay
diff --git a/i2p2www/pages/site/misc/ticket1056.html b/i2p2www/pages/site/misc/ticket1056.html
new file mode 100644
index 00000000..4d53f14b
--- /dev/null
+++ b/i2p2www/pages/site/misc/ticket1056.html
@@ -0,0 +1,24 @@
+{% extends "global/layout.html" %}
+{% block title %}Ticket 1056 fix{% endblock %}
+{% block content %}
+
            The issue described on this page only affects some Windows systems upgrading from an earlier version to 0.9.8.
+Other operating systems are not affected.
+
            
+
            This issue has been corrected as of the 0.9.8.1 release.
            
+
+
+There are two possible ways to resolve this problem.
+
+
            Option 1
            
+
+
              
+	
            1. Stop I2P
              2. 
+	
            2. Browser to %APPDATA%\I2P or wherever your I2P data dir is
              3. 
+	
            3. Delete the files router.info and router.keys
              4. 
+	
            4. Start I2P
              5. 
+
            
+
+
            Option 2
            
+
+Upgrade your I2P installation to to 0.9.8.1 by following the instructions here.
+{% endblock %}
diff --git a/i2p2www/pages/site/misc/ticket919.html b/i2p2www/pages/site/misc/ticket919.html
index 98b64760..bf5e5bb8 100644
--- a/i2p2www/pages/site/misc/ticket919.html
+++ b/i2p2www/pages/site/misc/ticket919.html
@@ -5,7 +5,7 @@
 
            The issue described on this page only affects Windows systems that originally installed I2P
 with version 0.9.5. Other operating systems are not affected.
 
            
-
            This issue has been corrected as of the 0.9.5-win1 release.
            
+
            This issue has been corrected as of the 0.9.5-win1 release.
            
 
 
 
@@ -25,7 +25,7 @@ eepsite it is important to follow this procedure prior to upgrading to 0.9.6.
 
            
 
 
            
-   Tickets 919 & 920 correspond to this issue.
+   Tickets 919 & 920 correspond to this issue.
 
            
 
 
            Fixing the configuration
            
diff --git a/i2p2www/pages/site/research/index.html b/i2p2www/pages/site/research/index.html
index e9a7544c..e4cf2601 100644
--- a/i2p2www/pages/site/research/index.html
+++ b/i2p2www/pages/site/research/index.html
@@ -5,6 +5,20 @@
 Academic research and analysis of I2P is an important part of ensuring that the software and network performs as expected and is safe for users in hostile environments.
 {%- endtrans %}
            
 
+
            {% trans anonbib='http://freehaven.net/anonbib/' %}
+There is a large research community investigating a wide range of aspects of
+anonymity. For a current and comprehensive list of relevant papers, see the
+Free Haven Anonymity Bibliography.
+I2P benefits from much of the research into Tor and onion routing, but there is
+little dedicated research interest into the theory behind I2P, and the choices
+and tradeoffs that the network makes. This presents a unique opportunity for
+original research.
+{% endtrans %}
            
+
+
            {% trans papers=get_url('papers_list') -%}
+A list of known published papers about I2P is available here.
+{%- endtrans %}
            
+
 
            {{ _('Testing Attacks on I2P') }}
            
 
 
            {% trans -%}
@@ -29,10 +43,4 @@ Additionally, I2P can be started in a virtual network mode. This mode disables a
 
            {% trans contact=site_url('contact') -%}
 If you are planning on conducting research on the live I2P network, please contact us before you commence your testing. While we do not discourage researchers from responsibly testing their ideas on the live network, if an attack becomes apparent and we don't have any line of communication then we will end up taking countermeasures which could interfere with the test.
 {%- endtrans %}
            
-
-
            {{ _('Prior Research') }}
            
-
-
            {% trans papers=site_url('research/papers') -%}
-A list of known published papers about I2P is available here.
-{%- endtrans %}
            
 {% endblock %}
diff --git a/i2p2www/pages/site/research/papers.html b/i2p2www/pages/site/research/papers.html
deleted file mode 100644
index 674db864..00000000
--- a/i2p2www/pages/site/research/papers.html
+++ /dev/null
@@ -1,113 +0,0 @@
-{% extends "global/layout.html" %}
-{% block title %}{{ _('Papers on I2P') }}{% endblock %}
-{% block content %}
-
            {{ _('Papers on I2P') }}
            
-
            
-{% trans %}Following are links to research papers about I2P.{% endtrans %}
-
            
-
            {% trans email='press ~~~at~~~ i2p2.de' -%}
-To request an addition to this page, please send to {{ email }}.
-{%- endtrans %}
            
-
            
-{% trans %}Newest links are at the top of the page.{% endtrans %}
-
            
-
-
            
-
-
            {{ _('Papers and Research') }}
            
-
-
-
            
-{% endblock %}
diff --git a/i2p2www/pages/site/research/questions.html b/i2p2www/pages/site/research/questions.html
new file mode 100644
index 00000000..8ba55126
--- /dev/null
+++ b/i2p2www/pages/site/research/questions.html
@@ -0,0 +1,22 @@
+{% extends "global/layout.html" %}
+{% block title %}{{ _('Open research questions') }}{% endblock %}
+{% block content %}
+
            {{ _('Network database') }}
            
+
+
            {{ _('Peer selection') }}
            
+
+
            {{ _('Tunnels and Destinations') }}
            
+
+
            {{ _('Unidirectional tunnels') }}
            
+
              
+
            • What are the benefits of unidirectional tunnels over bidirectional tunnels? What are the tradeoffs?
              • 
+
            • More details are available here.
              • 
+
            
+
+
            {{ _('Multihoming') }}
            
+
              
+
            • How effective is multihoming at load-balancing?
              • 
+
            • How does it scale? What happens as more routers host the same Destination?
              • 
+
            • The benefit for anonymity is less correlation of router uptime to Destination uptime. Are there tradeoffs?
              • 
+
            
-
+
+
 -->
 
            
-
            2013-05-28: 0.9.6 Released
            
-
-
            0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to Jetty 7.6.10 (2013-03-12).
- See below for important information on the Jetty update. The Jetty 7 series is actively maintained and
- we plan to stay current with it in future I2P releases.
            
-
-
            Most users will update via HTTP. Those running development builds will attempt to update via the
- experimental in-network bittorrent with i2psnark. We've fixed some bugs that will enable more users
- to update via torrent in the 0.9.7 update cycle.
            
-
-
            Important fix for Windows Eepsites, first install 0.9.5 only
            
-
-
            If you first installed I2P with version 0.9.5, on Windows only, we recommend that you follow the
- following instructions to fix your eepsite location before you update to 0.9.6.
- Only original installations of 0.9.5-0 on Windows are affected by this issue. If your router version
- is 0.9.5-0-win1, you already have the fix and need not take any action.
-
            See www.i2p2.i2p/ticket919
- or www.i2p2.de/ticket919 for instructions.
            
-
-
            Jetty 7 Migration Details
            
-
-
             For most people, the update should just work. If you have multiple Jetty eepsites,
- OR have made changes to jetty.xml or other Jetty configuration files, including changing the port
- from 7658, you MUST take manual action AFTER updating.
            
-
-
            * After update, the router will migrate your jetty.xml files to the new Jetty 7 format.
            
-
-
            * The migration resets the port to 7658. If you have more than one Jetty eepsite, OR your eepsite
- is NOT on port 7658, OR you have made other modifications to jetty.xml (for example changing the
- listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml file for each eepsite to fix them up
- after updating, and restart again.
            
-
-
            The following files will be backed up with a ".jetty6" suffix and then migrated.
- If you have made local changes, you may have to edit them manually and restart.
- See http://wiki.eclipse.org/Jetty for assistance
- in configuring Jetty 7.
            
-
-
            * ~/.i2p/clients.config
-
            * ~/.i2p/eepsite/jetty.xml
-
            * ~/.i2p/eepsite/jetty-rewrite.xml
-
            * ~/.i2p/eepsite/jetty-ssl.xml
-
            * ~/.i2p/eepsite/contexts/base-context.xml
-
            * ~/.i2p/eepsite/contexts/cgi-context.xml
-
            * ~/.i2p/eepsite/etc/webdefault.xml
            
-
-
            Plugins
            
-
-
            Most plugins should work fine with Jetty 7.
- The I2PControl and zzzot plugins must be updated. Your router should download and install
- the new versions shortly after starting 0.9.6.
- If a plugin does not work, please contact the maintainer for that plugin.
-
-
            
-Say hello to the volunteers on the #i2p-help IRC channel.
-Get involved,
-spread the word,
-and donate!
-If you find a bug, please enter a report on trac.
-To help on translations,
-volunteer on IRC #i2p-dev
-or sign up on Transifex.
+
            2013-12-07: 0.9.9 Released
            
+
            0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel,
+and starts work on a year-long plan to increase the strength
+of the cryptographic signing algorithms used in the router, and support multiple algorithms
+and key lengths simultaneously. Automatic update files will now be signed with 4096-bit keys.
+We now support SSL between your router and your servers for security.
+See http://zzz.i2p/topics/1495 for more information.
            
+
            
+Several of us will be at 30C3 this year.
+Look for us under the I2P banner or at the
+YBTI Assembly.
+Come say hi and ask for stickers!
 
            
 
            
diff --git a/i2p2www/static/styles/duck/default.css b/i2p2www/static/styles/duck/default.css
index d6b86085..06e291ab 100644
--- a/i2p2www/static/styles/duck/default.css
+++ b/i2p2www/static/styles/duck/default.css
@@ -30,12 +30,20 @@ div#topbar {
     position:relative;
 }
 
+div#topbar #logo {
+    float: left;
+}
+
 div#topbar #logo img:hover {
     filter:alpha(opacity=60);
     -moz-opacity: 0.6;
     opacity: 0.6;
 }
 
+nav {
+    clear: both;
+}
+
 div#content {
     display:block;
 }
@@ -70,7 +78,6 @@ div#content .main h1 {
 .main .get-i2p {
     display:block;
     top:50%;
-    height:1em;
     padding:.5em;
     line-height:1em;
     font-size:2em;
@@ -166,13 +173,18 @@ div#content .inner h1, div#content .inner h2, div#content .inner h3, div#content
     color:white;
     text-shadow:1px 1px 1px rgba(0,0,0,.3);
     margin:1em 0 .5em;
-    border-bottom:1px solid white;
     padding-bottom:.2em;
+    clear:both;
+}
+
+div#content .inner h2, div#content .inner h3, div#content .inner h4 {
+    border-bottom:1px solid white;
 }
 
 div#content .inner h1 {
     font-size:2.2em;
     margin:0em 0 1em;
+    text-align: center;
     width:auto;
 }
 
@@ -239,6 +251,18 @@ div#content .inner td.blue {
     padding: 5px;
 }
 
+/*
+ * Threat model
+ */
+
+div#content .inner ul.DREAD {
+    border: 2px solid red;
+    float: left;
+    list-style: none;
+    margin: 1em 1.5em 1em 0;
+    padding: 0.5em;
+}
+
 /*
  * Additions to syntax.css
  */
diff --git a/i2p2www/static/styles/duck/desktop.css b/i2p2www/static/styles/duck/desktop.css
index 66cff02a..ba721875 100644
--- a/i2p2www/static/styles/duck/desktop.css
+++ b/i2p2www/static/styles/duck/desktop.css
@@ -19,8 +19,8 @@ div#topbar {width:80%; /*margin:1em auto;*/ margin: 1em auto 0; position:relativ
     div#topbar .title {
         font-family:"URW Gothic L", "Century Gothic", sans-serif; text-transform:uppercase; font-size:3.5em; 
         font-weight:bold; text-shadow:1px 1px 1px rgba(0,0,0,.2); color:#333333;
-        position:absolute; top:0; right:0; line-height:41px; vertical-align:middle;
-        max-width: 70%; text-align: right;
+        /*position:absolute;*/ top:0; right:0; line-height:41px; vertical-align:middle;
+        /*max-width: 70%;*/ text-align: right;
     }
     div#topbar .languages {
         display: none;
@@ -227,15 +227,17 @@ div#content .main {
     text-shadow:1px 1px 2px rgba(0,0,0,.3); color:white; margin-bottom:.5em;}
     .main .get-i2p {
         position:absolute; display:block; top:50%; right: 10%;
-        margin-top:-1em; height:1em; padding:.5em; line-height:1em;
+        margin-top:-1em; max-width:20%; padding:.5em; line-height:1em;
         font-size:2em; color:white; font-family:Arial, Helvetica, sans-serif; font-weight:bold; 
         text-transform:uppercase; text-decoration:none; text-align:center; 
         background:green; border-radius:.3em; -moz-transform:rotate(-5deg); 
+        transform:rotate(-5deg); -webkit-transform:rotate(-5deg);
+        -ms-transform:rotate(-5deg); -o-transform:rotate(-5deg);
         text-shadow:1px 1px 1px rgba(0,0,0,.2);
         box-shadow:2px 2px 4px rgba(0, 0, 0, 0.3), 1em 3em 2em 0.5em rgba(255, 255, 255, 0.3) inset, inset -.2em -.5em 1em -0em rgba(0,0,0,.3)}
     .main .get-i2p:hover {box-shadow:2px 2px 2px rgba(0, 0, 0, 0.3), inset 0 -2.2em 2.2em rgba(255, 255, 255, 0.3), inset .2em .5em 1em 0em rgba(0,0,0,.3);}
     div#content .aside-wrap {width:80%; margin:2em auto;}
-    div#content .aside {position:relative; width:30.9%; margin-left:3%;    display:inline-block; vertical-align:top; font-size:1.2em}
+    div#content .aside {position:relative; width:30.9%; margin-left:3%;    display:inline-block; vertical-align:top; font-size:1.3em}
         div#content .aside:first-child {margin-left:0%;}
         div#content .aside a {font-weight:bold;}
         div#content .aside h1 {padding:1em 0; border-bottom:1px solid rgba(171, 204, 113, 0.6); font-size:1.4em; color:#222200; text-shadow:1px 1px 1px rgba(0,0,0,.3)}
@@ -269,12 +271,8 @@ div#content .main {
         width:auto; margin: 0 5%; padding: 4em 5% 2em; position:relative;
         background: rgba(171, 204, 113, 0.6); border-top:2px solid #abcc71;
         border-left: 2px solid #abcc71; border-right: 2px solid #abcc71; border-radius: 5px 5px 0 0;
-        color:black; font-size:1.2em; line-height:1.4em;
+        color:black; font-size:1.3em; line-height:1.4em;
     }
-    div#content .inner h1, div#content .inner h2, div#content .inner h3 {color:white; text-shadow:1px 1px 1px rgba(0,0,0,.3); margin:1em 0 .5em; border-bottom:1px solid white; padding-bottom:.2em;}
-    div#content .inner h1 {font-size:2.2em; margin:0em 0 1em;  width:auto;}
-    div#content .inner h2 {font-size:1.6em;}
-    div#content .inner h3 {font-size:1.4em;}
     div#content .inner ol {margin:1.5em;}
     div#content .inner ul {margin:1.5em; 1em;}
     div#content .inner p {margin:1em 0;}
diff --git a/i2p2www/static/styles/pubs.css b/i2p2www/static/styles/pubs.css
new file mode 100644
index 00000000..5e234313
--- /dev/null
+++ b/i2p2www/static/styles/pubs.css
@@ -0,0 +1,140 @@
+SPAN.title {
+  font-family: lucida, "Lucida Sans Unicode", Geneva, sans-serif;
+  font-weight: bold;
+}
+
+SPAN.author {
+  font-family: lucida, "Lucida Sans Unicode", Geneva, sans-serif;
+  font-weight: normal;
+}
+
+SPAN.availability {
+  font-family: lucidatypewriter, "Lucida Typewriter", Monaco, "Lucida Sans Unicode", monospace;
+  font-weight: normal;
+}
+
+SPAN.author A {
+  font-family: lucida, "Lucida Sans Unicode", Geneva, sans-serif;
+  font-weight: normal;
+}
+
+SPAN.biblio {
+  font-family: lucida, "Lucida Sans Unicode", Geneva, sans-serif;
+  font-style: italic;
+}
+
+SPAN.biblio A {
+  font-family: lucida, "Lucida Sans Unicode", Geneva, sans-serif;
+  font-weight: normal;
+  text-decoration: underline;
+}
+
+SPAN.bad {
+  text-decoration: underline;
+  color: #000;
+  background-color: #FDF;
+}
+
+P.remarks {
+  font-family: serif;
+  margin-top: 0.3em;
+  margin-bottom: 0;
+  margin-left: 5em;
+  padding-left: 0.5em;
+  border-width: 0 0 0 5px;
+  border-color: black;
+  border-style: solid;
+}
+
+P.remarks A {
+  text-decoration: underline;
+}
+
+P.l1 {
+  margin-left: 0.5em;
+}
+
+P.l2 {
+  margin-left: 1em;
+  margin-top: 0.3em;
+  margin-bottom: 0.3em;
+}
+
+P.entry {
+  margin-top: 0.7em;
+  margin-bottom: 0;
+}
+
+DIV.impEntry {
+  border-width: 1px;
+  border-color: black;
+  border-style: solid;
+  background-color: #FFE;
+  padding: 0.3em;
+  margin-top: 0.7em;
+  margin-bottom: 0;
+}  
+
+P.impEntry {
+  background-color: #FFE;
+  padding: 0;
+  margin-top: 0;
+  margin-bottom: 0;
+}
+
+DIV.draftEntry {
+ /*
+  border-width: 1px;
+  border-color: black;
+  border-style: solid;
+  padding: 0.3em;
+  margin-top: 0.7em;
+  margin-bottom: 0;
+*/
+}  
+
+P.draftEntry {
+ color: #555;
+  padding: 0;
+  margin-top: 0;
+  margin-bottom: 0;
+}
+
+TABLE.sidebar {
+  border-width: 2px;
+  border-color: black;
+  border-style: solid;
+  background-color: #CFF;
+}
+
+TD {
+  border: none !important;
+  vertical-align: top;
+}
+
+TD.bibtex {
+  font-family: lucidatypewriter, "Lucida Typewriter", Monaco, "Lucida Sans Unicode", monospace;  
+  border-width: 2px;
+  font-weight: normal; 
+  border-color: black;
+  border-style: solid;
+  background-color: #DFF;
+}
+
+PRE.bibtex {
+  font-family: lucidatypewriter, "Lucida Typewriter", Monaco, "Lucida Sans Unicode", monospace; 
+  font-size: smaller;
+}
+
+UL {
+  list-style: outside;
+}
+
+UL.expand {
+  margin-bottom: 1em;
+}
+
+UL.sections {
+  list-style: none;
+  vertical-align: top;
+}
diff --git a/i2p2www/templatevars.py b/i2p2www/templatevars.py
index 219e6e0d..0a2e15b1 100644
--- a/i2p2www/templatevars.py
+++ b/i2p2www/templatevars.py
@@ -1,11 +1,12 @@
 from flask import g, request, safe_join, url_for
 import os.path
 
-from i2p2www import CANONICAL_DOMAIN, CURRENT_I2P_VERSION, STATIC_DIR, app
+from i2p2www import CANONICAL_DOMAIN, CURRENT_I2P_VERSION, SUPPORTED_LANGS, SUPPORTED_LANG_NAMES, STATIC_DIR, app
+
+INPROXY = '.us'
 
 I2P_TO_CLEAR = {
-    'www.i2p2.i2p': 'www.i2p2.de',
-    #'forum.i2p': 'forum.i2p2.de',
+    'forum.i2p': 'forum.i2p', # Don't convert forum.i2p, it is not accessible outside I2P
     'trac.i2p2.i2p': 'trac.i2p2.de',
     'mail.i2p': 'i2pmail.org',
     }
@@ -44,8 +45,8 @@ def utility_processor():
 
     # Provide the canonical link to the current page
     def get_canonical_link():
-        protocol = request.url.split('//')[0]
-        return protocol + '//' + CANONICAL_DOMAIN + request.path
+        # Canonical domain should always be HTTPS
+        return 'https://' + CANONICAL_DOMAIN + request.path
 
     # Convert an I2P url to an equivalent clearnet one
     def convert_url_to_clearnet(value):
@@ -61,7 +62,7 @@ def utility_processor():
             return I2P_TO_CLEAR[value]
         except KeyError:
             # The I2P site has no known clearnet address, so use an inproxy
-            return value + '.to'
+            return value + INPROXY
 
     # Convert a paginated URL to that of another page
     def url_for_other_page(page):
@@ -102,4 +103,6 @@ def utility_processor():
                 get_url=get_url_with_lang,
                 get_flag=get_flag,
                 ver=get_current_version,
-                canonical=get_canonical_link)
+                canonical=get_canonical_link,
+                supported_langs=SUPPORTED_LANGS,
+                lang_names=SUPPORTED_LANG_NAMES)
diff --git a/i2p2www/translations/de/LC_MESSAGES/about.po b/i2p2www/translations/de/LC_MESSAGES/about.po
new file mode 100644
index 00000000..56b528fa
--- /dev/null
+++ b/i2p2www/translations/de/LC_MESSAGES/about.po
@@ -0,0 +1,2203 @@
+# German translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# amiga4000 , 2008
+# D.A. Loader, 2013
+# SteinQuadrat, 2013
+# zeroflag , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-07-04 16:33+0000\n"
+"Last-Translator: D.A. Loader\n"
+"Language-Team: German "
+"(http://www.transifex.com/projects/p/I2P/language/de/)\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/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 ""
+
+#: 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 ""
+
+#: 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 "Das Invisible Internet Projekt"
+
+#: i2p2www/pages/site/about/intro.html:5
+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 \n"
+"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:17
+msgid "How does it work?"
+msgstr "Wie funktioniert es ?"
+
+#: i2p2www/pages/site/about/intro.html:19
+#, 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:33
+#, 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:44
+#, python-format
+msgid "More details about how I2P works are available."
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:48
+msgid "What can you do with it?"
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:50
+#, 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:60
+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:76
+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:90
+#, 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/de/LC_MESSAGES/blog.po b/i2p2www/translations/de/LC_MESSAGES/blog.po
new file mode 100644
index 00000000..ff9a58ad
--- /dev/null
+++ b/i2p2www/translations/de/LC_MESSAGES/blog.po
@@ -0,0 +1,1503 @@
+# German translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# amiga4000 , 2008
+# D.A. Loader, 2013
+# SteinQuadrat, 2013
+# zeroflag , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-12-12 06:16+0000\n"
+"PO-Revision-Date: 2013-08-12 10:32+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: German "
+"(http://www.transifex.com/projects/p/I2P/language/de/)\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/blog/2011/10/11/0.8.9-Release.rst:24
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:25
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:12
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:12
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:17
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:16
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:16
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:26
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:19
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:19
+msgid "Files are available on the `download page`_."
+msgstr "Die Dateien sind verfügbar auf der `Download Seite`_."
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:28
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:15
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:29
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:16
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:16
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:21
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:20
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:20
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:30
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:23
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:23
+msgid "`download page`"
+msgstr "`Download Seite`"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:30
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:17
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:31
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:18
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:19
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:18
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:22
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:22
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:32
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:25
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:79
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:45
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:13
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:101
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:26
+msgid "RELEASE DETAILS"
+msgstr "RELEASE DETAILS"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:32
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:19
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:33
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:40
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:50
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:24
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:24
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:34
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:103
+msgid "Major Changes"
+msgstr "Wesentliche Änderungen"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:44
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:24
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:43
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:55
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:47
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:58
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:43
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:32
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:30
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:39
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:81
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:54
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:112
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:34
+msgid "Bug Fixes"
+msgstr "Bug Fixes"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:54
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:30
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:47
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:69
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:63
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:68
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:54
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:41
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:36
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:51
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:43
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:94
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:63
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:19
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:118
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:52
+msgid "Other"
+msgstr "Andere"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:73
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:36
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:51
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:82
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:75
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:96
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:76
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:52
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:56
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:67
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:56
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:110
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:79
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:30
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:129
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:27
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:76
+msgid "SHA256 Checksums:"
+msgstr "SHA256 Checksumme:"
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39
+msgid "Major changes"
+msgstr ""
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47
+msgid "Wrapper Update"
+msgstr ""
+
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:23
+msgid "Update Info"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2
+msgid "0.9.2 Release"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9
+msgid ""
+"0.9.2 includes extensive low-level changes to improve the performance and"
+" efficiency of the router. We have updated our UPnP library, to hopefully"
+" make UPnP work for more people. I2PSnark now has DHT support, but it is "
+"not yet enabled by default, as we plan to do more testing during the "
+"upcoming 0.9.3 development cycle."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12
+msgid ""
+"As usual, there's also lots of bug fixes in this release, so updating is "
+"recommended."
+msgstr ""
+"Wie üblich gibt es in diesem Release eine Menge Bug Fixes. Deswegen "
+"empfehlen wir eine Aktualisierung."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26
+msgid ""
+"SSU: Fix several problems in our UDP transport, to improve efficiency and"
+" reliability for connection setup. Also improve defenses against various "
+"types of bad input."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27
+msgid ""
+"UPnP: Updated our library to fix several issues, should work for more "
+"routers now"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28
+msgid ""
+"Transport: Improve performance in both our TCP and UDP transports, to "
+"benefit high-bandwidth routers"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29
+msgid ""
+"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered "
+"are now much more flexible, which should lessen protocol overhead and "
+"reduce stalls caused by dropped tags."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30
+msgid ""
+"I2PSnark: Add DHT support, not yet enabled by default, will do further "
+"testing and plan to enable by default in 0.9.3."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34
+msgid ""
+"Fix various issues affecting memory usage and performance on high-"
+"bandwidth routers"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35
+msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36
+msgid "Fix i2psnark bug that prevented a completion announcement to the tracker"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37
+msgid "Fix a lock contention problem in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38
+msgid "Fix some OSX installation issues"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39
+msgid "Remove uses of direct byte buffers that may have been leaking"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43
+msgid "Reduce overhead in network messages"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44
+msgid "Add \"universal\" theme support"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45
+msgid "Theme updates"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46
+msgid "Add a jbigi library for Raspberry Pi"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47
+msgid "New Scala unit test framework"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48
+msgid "Translation updates for Czech, Dutch, German, and Greek"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49
+msgid "Update wrapper to 3.5.15 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:77
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:127
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:74
+msgid "Update GeoIP data (new installs and PPA only)"
+msgstr "GeoIP Daten Update (nur bei neuen Installationen oder PPA)"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:2
+msgid "0.9.3 Release"
+msgstr "0.9.3 Release"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9
+msgid ""
+"0.9.3 includes extensive low-level changes to the queueing of messages in"
+" the router.  We implement the CoDel Active Queue Management (AQM) "
+"algorithm.  We also unify the queueing and priority mechanisms in the "
+"transports to aid diagnosis and reduce network latency.  Work continues "
+"on fixing UDP transport bugs and making UDP more resistant to attacks.  "
+"There are more changes to improve the performance of the router and "
+"reduce its memory usage.  Also, we enable i2psnark's DHT support, "
+"introduced last release, by default."
+msgstr ""
+"0.9.3 beinhaltet erweiterte low-level Änderungen der "
+"Nachrichtenwarteschlange im Router. Wir haben den CoDel Active Queue "
+"Management (AQM) Algorithmus implementiert. Außerdem wurde der "
+"Transportwarteschlangen - und Transportprioritätsmechanismus  für bessere"
+" Diagnose und Netzwerk Latenz vereinheitlicht. Wir arbeiten weiterhin an "
+"der Beseitigung des UDP Transportbugs und machen UDP sicherer gegen "
+"Attacken. Des weiteren gibt es am Router änderungen zur "
+"Leistungssteigerung und Verringerung des Speicherverbrauchs. Ebenfalls "
+"wurde die DHT funktionalität von i2psnark, welche mit dem letzten Release"
+" eingeführt wurde, standardmäßig aktiviert."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26
+msgid "Active Queue Management"
+msgstr "Active Queue Management"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:27
+msgid "Priority queues"
+msgstr "Prioritäts Warteschlangen"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28
+msgid "I2PSnark DHT: Several bug fixes, enable by default."
+msgstr "I2PSnark DHT: Diverse Bug Fixes, standardmäßig aktiviert."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32
+msgid ""
+"Several SSU fixes including memory leak, and better handling of routers "
+"behind firewalls that change UDP ports; additional defenses for malicious"
+" packets."
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33
+msgid "Fix piece selection (rarest-first) bugs in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34
+msgid "Fix bug causing multiple browsers to open at startup"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38
+msgid "Improvements in caching"
+msgstr "Verbesserungen im Caching"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39
+msgid "Several synchronization fixes and lock contention reduction"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40
+msgid "Major reduction in SSU buffers memory use"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41
+msgid ""
+"Fix streaming connection timeout back to 1 minute, was inadvertently "
+"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was"
+" unlimited"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42
+msgid "Improved defenses in i2ptunnel for \"darkloris\""
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:43
+msgid "More validation at torrent creation in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44
+msgid "Several parameter changes in SSU to improve throughput"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45
+msgid ""
+"New event log for major events including restarts; show multiple restart "
+"lines on graphs"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46
+msgid "Remove duplicate messages from logs"
+msgstr "Entferne doppelte Einträge/Nachrichten im Log"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47
+msgid "Don't respond to blocked streaming connections with a reset, just drop"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48
+msgid "Remove all uses of inefficient SimpleTimer"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49
+msgid "More checks for valid IPs and ports entered in console"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50
+msgid "Fix bug that wasted a lot of entropy"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51
+msgid "Translation updates: Italian, Portuguese, Spanish, Swedish"
+msgstr "Übersetzungsupdates: Italienisch, Portugiesisch, Spanisch, Schwedisch"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52
+msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2
+msgid "0.9.4 Release"
+msgstr "0.9.4 Release"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9
+msgid ""
+"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, "
+"that was reducing network performance and reliability. It also includes "
+"major changes in the in-network update system, and adds the capability to"
+" update via in-network torrents."
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13
+msgid ""
+"We fixed several bugs in the i2psnark DHT implementation that was "
+"introduced\n"
+"last release. For those of you using console or http proxy passwords,\n"
+"we converted to the more-secure digest method and improved the security "
+"for console forms."
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19
+msgid ""
+"For those of you already running development builds, your router should "
+"automatically\n"
+"update to 0.9.4-0 using the new in-network torrent facility.\n"
+"For those running 0.9.3-0, you will update normally using in-network "
+"HTTP, and\n"
+"we will have more information for you when we release 0.9.5."
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36
+msgid ""
+"Big rework of the update system; Preliminary support for updates via "
+"i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37
+msgid "Add per-destination outbound priorities"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41
+msgid ""
+"Fix major bug that reduced SSU connection limits which reduced tunnel "
+"build success rates"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42
+msgid "Fix bug with external I2CP that prevented some external apps from working"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43
+msgid "Fixed several bugs in i2psnark DHT"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44
+msgid "Fixed bug in i2psnark PEX that inflated peer counts"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45
+msgid "Handle dropped I2CP messages better"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46
+msgid "Reduce overhead of I2CP messages"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47
+msgid "Enforce max size in transport outbound message queues"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48
+msgid "Fixes for Windows eepget.bat (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49
+msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53
+msgid ""
+"More performance improvements, memory reduction, and object churn "
+"reduction"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54
+msgid "Better detection of network disconnections"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55
+msgid "Further improvements in the SSU transport"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56
+msgid "Add console password form"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57
+msgid ""
+"Convert http proxy and console from basic to digest authentication for "
+"added security"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58
+msgid ""
+"Improved verification of console form submissions, using jsp sessions. "
+"Cookies may now be required on forms, except when the console password is"
+" enabled"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59
+msgid ""
+"Initial work on new interfaces to manage applications started via "
+"clients.config"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60
+msgid "Increase minimum peer port to 1024"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61
+msgid "Increase granularity of bandwidth limiter for smoother transmissions"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62
+msgid ""
+"Translation updates: Chinese, French, German, Italian, Polish, "
+"Portuguese, Swedish, and Ukrainian"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64
+msgid "Update wrapper to 3.5.16 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65
+msgid "New ARMv6 wrapper for Raspberry Pi"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:2
+msgid "0.9.5 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9
+msgid ""
+"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities"
+" that are being investigated by researchers at UCSB. We continue to work "
+"with them on additional improvements. This is a good opportunity to "
+"remind the community that while our network continues to grow rapidly, it"
+" is still relatively small. There may be multiple weaknesses or bugs that"
+" could compromise your anonymity. Help us grow the network by spreading "
+"the word and contributing where you can."
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13
+#, python-format
+msgid ""
+"In this upgrade cycle, a random 1% of routers, (plus all routers running "
+"a\n"
+"development build) will attempt to update via the experimental in-network"
+" bittorrent\n"
+"with i2psnark. If this doesn't work, it should fall back to standard in-"
+"network HTTP update."
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27
+msgid "Defenses and Bug Fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29
+msgid "Fix router bug causing lockup when using iMule"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30
+msgid "Recognize, handle, reject duplicate tunnel IDs"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31
+msgid "Fix changing of the log file name"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32
+msgid "Prevent hashcode attack in session tags"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33
+msgid "Add build request throttler based on previous hop"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34
+msgid "Limit concurrent next-hop lookups"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35
+msgid "Catch exceptions storing nonces in console"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36
+msgid "Fix saving graph settings in console"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37
+msgid "Fix eepget generation of URLs when not proxied"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38
+msgid ""
+"Encrypt database lookup messages end-to-end when sent through exploratory"
+" tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39
+msgid "Don't use multiple floodfills from the same /16 in a query"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40
+msgid "Randomize delay before verifying floodfill store"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41
+msgid "Increase number of floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:45
+msgid "Improve support for mobile browsers"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46
+msgid "Partial defenses for UCSB attacks"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47
+msgid "Add announce list support to i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48
+msgid "Jetty: upgrade Apache Tomcat to 6.0.36"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49
+msgid "Split router info files into multiple subdirectories"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50
+msgid "Add IP to hostname mapping option in SOCKS"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51
+msgid "Improve PRNG seeding"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52
+msgid ""
+"Translation updates: French, German, Hungarian, Italian, Norwegian, "
+"Polish, Portuguese, Russian, Swedish"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54
+msgid "Update wrapper to 3.5.17 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:2
+msgid "0.9.6 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:7
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9
+msgid ""
+"0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to "
+"Jetty 7.6.10 (2013-03-12). See below for important information on the "
+"Jetty update. The Jetty 7 series is actively maintained and we plan to "
+"stay current with it in future I2P releases."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13
+msgid ""
+"Most users will update via HTTP. Those running development builds will "
+"attempt to update via the\n"
+"experimental in-network bittorrent with i2psnark. We've fixed some bugs "
+"that will enable more users\n"
+"to update via torrent in the 0.9.7 update cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25
+msgid "Important fix for Windows Eepsites, first install 0.9.5 only"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27
+msgid ""
+"If you first installed I2P with version 0.9.5, on Windows only, we "
+"recommend that you follow the\n"
+"following instructions to fix your eepsite location **before** you update"
+" to 0.9.6.\n"
+"Only original installations of 0.9.5-0 on Windows are affected by this "
+"issue. If your router version\n"
+"is 0.9.5-0-win1, you already have the fix and need not take any action."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34
+msgid "See `this page`_ for instructions."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:38
+msgid "`this page`"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:40
+msgid "Jetty 7 Migration Details"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42
+msgid ""
+"For most people, the update should just work. If you have multiple Jetty "
+"eepsites,\n"
+"OR have made changes to jetty.xml or other Jetty configuration files, "
+"including changing the port\n"
+"from 7658, you MUST take manual action AFTER updating."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48
+msgid ""
+"After update, the router will migrate your jetty.xml files to the new "
+"Jetty 7 format."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50
+msgid ""
+"The migration resets the port to 7658. If you have more than one Jetty "
+"eepsite, OR your eepsite\n"
+"  is NOT on port 7658, OR you have made other modifications to jetty.xml "
+"(for example changing the\n"
+"  listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml "
+"file for each eepsite to fix them up\n"
+"  after updating, and restart again."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55
+msgid ""
+"**The following files will be backed up with a ".jetty6" suffix"
+" and then migrated.**\n"
+"If you have made local changes, you may have to edit them manually and "
+"restart.\n"
+"See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69
+msgid "Plugins"
+msgstr "Plugins"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:71
+msgid "Most plugins should work fine with Jetty 7."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:75
+msgid ""
+"The I2PControl and zzzot plugins must be updated. Your router should "
+"download and install the new versions shortly after starting 0.9.6."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77
+msgid "If a plugin does not work, please contact the maintainer for that plugin."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83
+msgid "Several bugs with Windows installation (see above)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:84
+msgid "Fix default form action in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85
+msgid "Fix links on iframed console pages"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86
+msgid "Better detection of 64-bit Windows to prevent crashes by systray"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87
+msgid "Fix bug preventing router update via torrent"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88
+msgid "Several SSU fixes for NATs that change UDP ports"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89
+msgid ""
+"Ignore unsupported IPs in RouterInfos when selecting an address (prep for"
+" IPv6)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90
+msgid ""
+"Ignore unused option bits in Database Lookup Message (prep for requesting"
+" encrypted response)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91
+msgid "Fix HTTP proxy error response for malformed URIs"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92
+msgid "Recognize UPnP devices without port forwarding capability"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96
+msgid "Jetty 7.6.10 (see above for migration information)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97
+msgid "Limit page size in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98
+msgid "Add data directory and page size configuration to i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99
+msgid "Support multiple i2psnark instances"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100
+msgid "Piece size adjustments in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101
+msgid "Add more graphing support for combined bandwidth graph"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102
+msgid "Block b32.i2p supercookies"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103
+msgid "Allow stopping clients on /configclients"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104
+msgid "Check for nonce count replays in HTTP client"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105
+msgid "Support SASL authentication in IRC proxy"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106
+msgid "Several cleanups and minor fixes in the update manager"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107
+msgid "Translation updates: German, Portuguese, Russian, Spanish, and Swedish"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:2
+msgid "0.9.7 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:7
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:9
+msgid "0.9.7 includes significant bug fixes and improvements."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:11
+msgid ""
+"For the first time, class 'N' routers (those with a minimumum of 128 "
+"KBytes/sec of shared bandwidth)\n"
+"will automatically become floodfill (previously it was only 'O' routers "
+"with 256 KBps). This will\n"
+"increase the floodfill population for additional resistance to certain "
+"attacks (see below). Floodfill routers\n"
+"don't consume much additional bandwidth, but they do tend to use "
+"additional memory and concurrent\n"
+"connections. If you do not wish your router to become floodfill, set the "
+"advanced configuration\n"
+"router.floodfillParticipant=false ."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:20
+#, python-format
+msgid ""
+"As we think the last release fixed the experimental update-via-torrent "
+"bugs, 3% of routers should\n"
+"update over in-network bittorrent this cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:25
+msgid ""
+"Plugin update checks, possibly broken for several releases, are fixed. "
+"Your plugins should once again\n"
+"auto-update after updating the router."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:30
+msgid ""
+"We fixed a major streaming timer bug that contributed to frequent IRC "
+"disconnects."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:34
+msgid ""
+"This release contains additional mitigations for the `\"practical "
+"attacks\" paper`_.\n"
+"However, we have a lot more work to do to resist Sybil attacks on the "
+"floodfills, and resist\n"
+"traffic analysis at the gateways and endpoints of exploratory tunnels.\n"
+"It's a good reminder for everybody that our network is still relatively "
+"small and vulnerable.\n"
+"We don't currently recommend any uses that would put anybody in serious "
+"jeopardy.\n"
+"We'll keep working to improve it... please keep working to spread the "
+"word. A bigger network is a better network."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:43
+msgid "`\"practical attacks\" paper`"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:47
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:15
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:107
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:28
+msgid "Anonymity Improvements"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:49
+msgid "End-to-end encryption of responses to leaseset lookups"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:50
+msgid "Expand floodfill pool by enabling class 'N' floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:51
+msgid "Randomize padding inside encrypted SSU packets"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:52
+msgid "Preparation for better SSU protocol obfuscation"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:56
+msgid "Fix newer lease sets not getting stored or published"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:57
+msgid ""
+"Fix classpath bug when used with 4-year-old installations, causing the "
+"console not to start"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:58
+msgid "Fix addressbook database bug preventing update of the reverse index"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:59
+msgid ""
+"Fix i2psnark bug that changed the infohash of torrents created by Robert "
+"and fetched via magnet link"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60
+msgid "Fix version checking for plugins"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:61
+msgid ""
+"Fix a streaming timer bug causing frequent IRC disconnects (also affects "
+"other close-on-idle tunnels)"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:65
+msgid "Don't install as a service on Windows by default"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:66
+msgid "Reduce transport idle timeouts"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:67
+msgid "Reduce tunnels on idle in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:68
+msgid "Change default in i2ptunnel GUI to 3 hops"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:69
+msgid "IE 10 support"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70
+msgid ""
+"Individual expiration times in leases, for efficiency on destinations "
+"with a high number of tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71
+msgid "Low-level encryption and XOR speedups"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:72
+msgid "Jetty 7.6.11"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:73
+msgid "Tomcat 6.0.37"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74
+msgid "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75
+msgid "New Turkish translation"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:76
+msgid "Wrapper 3.5.19 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:2
+msgid "0.9.7.1 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:7
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:9
+msgid ""
+"This unscheduled release disables the RouterInfo verification messages "
+"that were used in the attack published in the UCSB paper, which should "
+"make correlating a LeaseSet and a Router much more difficult. We have "
+"also included a limited number of other fixes listed below. Our 0.9.8 "
+"release, which will include IPv6 support, is still on-schedule for late "
+"September."
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:11
+msgid "As usual, we recommend that all users update to this release."
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:17
+msgid "Disable RouterInfo verification messages"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:21
+msgid "Extend inbound tunnel expiration"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:22
+msgid "i2prouter: bashism fix"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:23
+msgid "i2psnark: increase max piece size, mime type updates"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:24
+msgid "New reseed host"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:25
+msgid "New update hosts, thanks Meeh and dg"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:26
+msgid "Streaming: RTO changes"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:27
+msgid "Updater: Increase update-via-torrent to 30 percent"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:28
+msgid "UPnP fix for some hardware"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:2
+#, fuzzy
+msgid "0.9.8 Release"
+msgstr "0.9.4 Release"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9
+msgid ""
+"0.9.8 includes the long-awaited support for IPv6. It's enabled by "
+"default, but of course you need a public IPv6 address to use it. "
+"Configuration is on the 'network' configuration tab in your console. We "
+"also have anonymity improvements including padding of SSU packets and "
+"longer router private keys."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11
+#, python-format
+msgid "30% of you will update via in-network torrent in this update cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13
+msgid "IPv6 Details"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15
+msgid ""
+"IPv6 is enabled and preferred by default. If you have a public IPv6 "
+"address \n"
+"and you are connecting to another router with a published IPv6 address, "
+"it will \n"
+"connect via IPv6. There is a new IPv6 configuration section on /confignet"
+" in \n"
+"the router console. If IPv6 is causing problems you may disable it there."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22
+msgid ""
+"As a part of the IPv6 development effort, I2P now supports multiple \n"
+"published IP addresses. If you have multiple public IP addresses (IPv4, "
+"IPv6, \n"
+"or both), you may enable or disable them individually on /confignet. The"
+" \n"
+"default is to use the first IPv4 and IPv6 addresses it discovers. If you "
+"have \n"
+"multiple addresses you should review the configuration on /confignet and "
+"adjust \n"
+"it if necessary.\n"
+"Note that while you may enable multiple IPv4 and IPv6 addresses on "
+"/confignet,\n"
+"we recommend that you use only one IPv4 and one IPv6 address. There are\n"
+"bugs still to be fixed with multiple addresses of each type."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34
+msgid ""
+"While IPv6 support was designed and developed over several years, it has"
+" \n"
+"only been tested by a limited number of users and is still beta. If you "
+"do have \n"
+"a public IPv6 address, please monitor your router and the logs for "
+"problems, \n"
+"and disable it necessary. Please report any bugs on \n"
+"http://trac.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:42
+msgid "Rekeying Details"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44
+msgid ""
+"For those of you running I2P on faster hardware (generally, 64-bit x86) "
+"the \n"
+"router will generate a new identity using longer keys. This will "
+"substantially \n"
+"reduce your participating traffic for 48 hours or more, while your router"
+" \n"
+"re-integrates into the network. Due to the new keys, the large number of"
+" \n"
+"torrent updates, and the recent network growth, we expect substantial \n"
+"disruption to the network for a week or more after the update is "
+"released. \n"
+"Please be patient and things should start to improve after a few days."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54
+msgid ""
+"These changes may result in higher CPU usage for some of you. We're doing"
+" \n"
+"our best to increase efficiency, but stronger security generally requires"
+" more \n"
+"computation. Performance may also be poor during the first week\n"
+"due to the network churn.\n"
+"We will evaluate the network performace before deciding whether to\n"
+"change the key length on slower hardware in a future release."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63
+msgid ""
+"We are experiencing rapid network growth in the last few weeks, which is"
+" \n"
+"causing a bit of a bumpy ride for some, especially on weekends. However, "
+"the \n"
+"network is still performing fairly well, so keep spreading the word."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69
+msgid "More Changes Coming"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:71
+msgid ""
+"We're in the initial stages of desiging major changes to strengthen our \n"
+"crypto. Stronger crypto will use more CPU and it may possibly \n"
+"require a Java 7 JRE at a minimum. We understand your desire to run I2P "
+"on low-power \n"
+"and/or older hardware. We're working hard to minimize the impacts, but "
+"some \n"
+"loss of performance is inevitable. In addition, Java 5 and 6 are no "
+"longer \n"
+"supported by Oracle. Now is a good time to upgrade to Java 7. Any change "
+"in \n"
+"minimum requirements will be announced well in advance."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:81
+msgid "New Website"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:83
+msgid ""
+"After a heroic effort by str4d, the new website preview is available at \n"
+"http://i2hq.srv.i2p2.de. We hope to see it go live at \n"
+"https://geti2p.net and http://www.i2p2.i2p soon.  Please \n"
+"contribute to the new website translations on Transifex, especially the \n"
+"website_priority resource."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91
+msgid "Community Participation"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:93
+msgid ""
+"In early August, hottuna and zzz attended DEFCON 21 in Las Vegas.\n"
+"Last weekend, echelon attended the CTS IV conference in Berlin and\n"
+"psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass.\n"
+"Several of us will be at 30C3 in Hamburg late this year.\n"
+"It's great to see people participating at these events and representing "
+"I2P."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105
+msgid "IPv6 support for both NTCP and SSU"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:109
+msgid "SSU protocol obfuscation by adding random padding"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110
+msgid "Longer encryption and DH private keys for users on faster platforms"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114
+msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:115
+msgid "Fix translation of HTTP proxy error pages"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:116
+msgid "Fix occasional runtime exception in NTCP"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120
+msgid "Big rework of transport code to accommodate multiple addresses and IPv6"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121
+msgid "Streaming: Improved recovery from lost acks, other fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122
+msgid "Use Transifex for translation of initial news and HTTP proxy error pages"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123
+#, fuzzy
+msgid ""
+"Translation updates: Chinese, French, German, Portuguese, Russian, "
+"Swedish, Turkish"
+msgstr "Übersetzungsupdates: Italienisch, Portugiesisch, Spanisch, Schwedisch"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124
+msgid "New Romanian translation"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:126
+#, fuzzy
+msgid "Wrapper 3.5.20 (new installs and PPA only)"
+msgstr "GeoIP Daten Update (nur bei neuen Installationen oder PPA)"
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:2
+#, fuzzy
+msgid "0.9.8.1 Release"
+msgstr "0.9.4 Release"
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:7
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:9
+msgid ""
+"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some "
+"people. New installs and non-Windows platforms are not affected, however "
+"all platforms will automatically update even if running 0.9.8."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:11
+msgid ""
+"See the `Trac ticket`_ for details and workarounds. See\n"
+"`the 0.9.8 release notes`_ for information on IPv6 and other changes."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:16
+msgid ""
+"Due to recent attacks, logins are disabled on `Trac`_ and new "
+"registrations are\n"
+"disabled on `zzz.i2p`_. Until those services are restored, please report "
+"all\n"
+"bugs on IRC freenode or IRC2P #i2p-dev."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:22
+msgid "`Trac ticket`"
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:23
+#, fuzzy
+msgid "`the 0.9.8 release notes`"
+msgstr "0.9.4 Release"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:2
+#, fuzzy
+msgid "0.9.9 Release"
+msgstr "0.9.4 Release"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:7
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:9
+msgid ""
+"0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and "
+"starts work on a year-long plan to increase the strength of the "
+"cryptographic signing algorithms used in the router, and support multiple"
+" algorithms and key lengths simultaneously. Automatic update files will "
+"now be signed with 4096-bit RSA keys."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:11
+msgid ""
+"We now support SSL between your router and your servers for security.\n"
+"See `this development thread`_ for more information."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:16
+msgid "`this development thread`"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:18
+msgid ""
+"As usual, we recommend that you update to this release.\n"
+"The best way to maintain security and help the network is to run the "
+"latest release.\n"
+"Several members of the I2P team will be at 30C3 in Hamburg this year.\n"
+"Come say hello and ask for an I2P sticker.\n"
+"Thanks to everyone for their support this year."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:30
+msgid "Don't build client tunnels through zero-hop exploratory tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:31
+msgid "New \"su3\" file support using stronger keys"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:32
+msgid "Use su3 for updates"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:36
+msgid "Issues with losing data when closing streams"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:37
+msgid "Fix various streaming connection limit issues"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:38
+msgid "Issues with resource usage of closed connections"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:39
+msgid "Clean up timer threads in close-on-idle tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:40
+msgid "Several other streaming fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:41
+msgid "Reject more non-public IPv6 addresses"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:42
+msgid "Fix IPv6 GeoIP"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:43
+msgid "Fix peer selection in first minutes after startup"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:44
+msgid "Several I2PTunnel bug fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:45
+msgid "Fix major i2psnark DHT bug that prevented magnets from working well"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:46
+msgid ""
+"Fix client tunnels that fail due to name resolution failure at startup, "
+"particularly with b32 hostnames"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:47
+msgid "Fix changing client i2ptunnel target list"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:48
+msgid ""
+"Fix major bugs preventing reception of encrypted responses to leaseset "
+"lookups and verifies"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:49
+msgid "Fix bad links on some i2psnark buttons in Opera and text-mode browsers"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:50
+msgid "Fix NPE in Susimail"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:54
+msgid "Start work on supporting stronger signing keys in the router"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:55
+msgid "Reduce thread usage for HTTP Server tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:56
+msgid "Auto-stop update torrent after some time"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:57
+msgid "Add ability to stop webapp via console"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:58
+msgid "New POST throttler in HTTP server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:59
+msgid "Improve connection throttling"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:60
+msgid "More work to reduce number of connections"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:61
+msgid "Re-enable router info expiration job"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:62
+msgid ""
+"Extend router info expiration and other changes to reduce load on "
+"floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:63
+msgid "Support multiple servers through a single server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:64
+msgid "Support specification of server port in i2ptunnel clients"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:65
+msgid "Add support for SSL connections from i2ptunnel to external server"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:66
+msgid "SSL and crypto code refactoring"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:67
+msgid "i2psnark storage code refactoring"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:68
+msgid "New destination cache"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:69
+msgid "Lots of code cleanup and resolution of findbugs warnings"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:70
+msgid "New Japanese translation (partial)"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:71
+#, fuzzy
+msgid ""
+"Translation updates: French, German, Italian, Romanian, Russian, Spanish,"
+" Swedish, and others"
+msgstr "Übersetzungsupdates: Italienisch, Portugiesisch, Spanisch, Schwedisch"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:73
+#, fuzzy
+msgid "Wrapper 3.5.22 (new installs and PPA only)"
+msgstr "GeoIP Daten Update (nur bei neuen Installationen oder PPA)"
+
diff --git a/i2p2www/translations/de/LC_MESSAGES/comparison.po b/i2p2www/translations/de/LC_MESSAGES/comparison.po
new file mode 100644
index 00000000..9eb0e32c
--- /dev/null
+++ b/i2p2www/translations/de/LC_MESSAGES/comparison.po
@@ -0,0 +1,672 @@
+# German translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# amiga4000 , 2008
+# D.A. Loader, 2013
+# SteinQuadrat, 2013
+# zeroflag , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-10-26 22:39+0000\n"
+"PO-Revision-Date: 2013-07-04 16:33+0000\n"
+"Last-Translator: D.A. Loader\n"
+"Language-Team: German "
+"(http://www.transifex.com/projects/p/I2P/language/de/)\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/comparison/freenet.html:2
+msgid "I2P Compared to Freenet"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/freenet.html:8
+msgid ""
+"Freenet is a fully distributed, peer to peer anonymous publishing "
+"network, offering \n"
+"secure ways to store data, as well as some approaches attempting to "
+"address the loads\n"
+"of a flash flood.  While Freenet is designed as a distributed data store,"
+" people have\n"
+"built applications on top of it to do more generic anonymous "
+"communication, such as \n"
+"static websites and message boards."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/freenet.html:16
+#, python-format
+msgid ""
+"Compared to I2P, Freenet offers some substantial benefits - it is a "
+"distributed data\n"
+"store, while I2P is not, allowing people to retrieve the content "
+"published by others \n"
+"even when the publisher is no longer online.  In addition, it should be "
+"able to \n"
+"distribute popular data fairly efficiently.  I2P itself does not and will"
+" not provide \n"
+"this functionality.  On the other hand, there is overlap for users who "
+"simply want to \n"
+"communicate with each other anonymously through websites, message boards,"
+" file sharing\n"
+"programs, etc.  There have also been some attempts to develop a "
+"distributed data \n"
+"store to run on top of I2P,\n"
+"(most recently a port of Tahoe-LAFS)\n"
+"but nothing is yet ready for general use."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/freenet.html:29
+msgid ""
+"However, even ignoring any implementations issues, there are some "
+"concerns \n"
+"about Freenet's algorithms from both a scalability and anonymity "
+"perspective, owing \n"
+"largely to Freenet's heuristic driven routing.  The interactions of "
+"various techniques \n"
+"certainly may successfully deter various attacks, and perhaps some "
+"aspects of the \n"
+"routing algorithms will provide the hoped for scalability.  "
+"Unfortunately, not much\n"
+"analysis of the algorithms involved has resulted in positive results, but"
+" there is still\n"
+"hope.  At the very least, Freenet does provide substantial anonymity "
+"against an attacker\n"
+"who does not have the resources necessary to analyze it further."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/index.html:2
+msgid "Comparing I2P to other projects"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/index.html:4
+msgid ""
+"There are a great many other applications and projects working on "
+"anonymous \n"
+"communication and I2P has been inspired by much of their efforts.  This "
+"is not \n"
+"a comprehensive list of anonymity resources - both freehaven's \n"
+"Anonymity "
+"Bibliography\n"
+"and GNUnet's related "
+"projects\n"
+"serve that purpose well.  That said, a few systems stand out for further\n"
+"comparison. The following have individual comparison pages:"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/index.html:20
+#, python-format
+msgid ""
+"The following are discussed on the other "
+"networks page:"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/index.html:32
+#, python-format
+msgid ""
+"The content of this page is subject to update, discussion and dispute, "
+"and we welcome comments and additions.\n"
+"You may contribute an analysis by entering a new "
+"ticket on Trac."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:2
+msgid "I2P Compared to Other Anonymous Networks"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:5
+msgid "The following networks are discussed on this page."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:16
+#, python-format
+msgid ""
+"Most of the following sections are fairly old, and may not be accurate.\n"
+"For an overview of available comparisons, see the\n"
+"main network comparisons page.\n"
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:29
+#, python-format
+msgid ""
+"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
+" \n"
+"anonymizing proxies, allowing people to tunnel out through the low "
+"latency \n"
+"mix network.  Morphmix includes some very interesting collusion detection"
+" \n"
+"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
+"IP\n"
+"addresses to accomplish the same.  The two primary differences between \n"
+"these systems and I2P are related to I2P's threat model \n"
+"and their out-proxy design (as opposed to providing both sender and "
+"receiver \n"
+"anonymity).  There is source code available to both systems, but we are "
+"not aware \n"
+"of their use outside of academic environments."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:153
+#, python-format
+msgid ""
+"\n"
+"Mixminion and Mixmaster are networks to support anonymous email against a"
+" very\n"
+"powerful adversary.\n"
+"High-latency messaging applications running on top of I2P\n"
+"(for example Syndie or I2PBote)\n"
+"may perhaps prove adequate to meet the threat\n"
+"model of those adversaries, while running in parallel along side the "
+"needs of low latency users, to provide\n"
+"a significantly larger anonymity set.\n"
+"High-latency support within the I2P router itself may or may not be added"
+" in a distant future release.\n"
+"It is too early to say if I2P will meet the needs of users requiring "
+"extreme protection for email."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:165
+msgid ""
+"As with Tor and Onion Routing, \n"
+"both Mixminion and Mixmaster take the directory based approach as well."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:175
+#, python-format
+msgid ""
+"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
+"web requests,\n"
+"and as such it has a few centralized nodes (participants in the cascade) "
+"that blend\n"
+"and mix requests from clients through the sequence of nodes (the cascade)"
+" before \n"
+"proxying out onto the web.  The scope, threat model, and security is "
+"substantially \n"
+"different from I2P, but for those who don't require significant anonymity"
+" but still\n"
+"are not satisfied with an Anonymizer-like service, JAP is worth "
+"reviewing.  One\n"
+"caution to note is that anyone under the jurisdiction of the German "
+"courts may want\n"
+"to take care, as the German Federal Bureau of Criminal Investigation "
+"(FBCI) has \n"
+"successfully mounted an \n"
+"attack \n"
+"on the network.  Even though the method of this attack was later found to"
+" be illegal \n"
+"in the German courts, the fact that the data was successfully collected "
+"is the \n"
+"concern.  Courts change their minds based upon circumstance, and this is "
+"evidence that \n"
+"if a government body or intelligence agency wanted to, they could gather "
+"the data, even \n"
+"if it may be found inadmissible in some courts later)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:197
+#, python-format
+msgid ""
+"Both of these systems work through the same basic \n"
+"antnet routing, providing some degree of\n"
+"anonymity based on the threat model of providing plausible deniability "
+"against a simple \n"
+"non-colluding adversary.  With the antnet routing, they first either do a"
+" random walk or a \n"
+"broadcast search to find some peer with the data or identity desired, and"
+" then use a feedback\n"
+"algorithm to optimize that found path.  This works well for applications "
+"that merely want to know \n"
+"what other people around them have to offer - \"How are y'all doing\" vs."
+" \"Hey Alice, how are you\" - \n"
+"you basically get a local cluster of nodes that can share files with and "
+"maintain some degree of \n"
+"anonymity (though you don't have much control over who is in that group "
+"of peers)."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:209
+msgid ""
+"However, the algorithm does not scale well at all - if the application "
+"wants to speak with a \n"
+"particular peer it ends up doing a broadcast search or random walk "
+"(though if they are lucky enough\n"
+"for that to succeed, the antnet routing should optimize that found "
+"connection).  This means that \n"
+"while these networks can work great at small scales, they are not "
+"suitable for large networks where\n"
+"someone wants to get in touch with another specific peer.  That does not "
+"mean that there is no \n"
+"value in these systems, just that their applicability is limited to "
+"situations where their \n"
+"particular issues can be addressed."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:220
+#, python-format
+msgid ""
+"This was a closed-source network targeted at Iranian users.\n"
+"Tor did a good writeup on what to look for in a "
+"circumvention tool.\n"
+"Suffice it to say that being closed source and publicly targeting a "
+"specific country are not good ideas.\n"
+"I2P is, of course, open source. However, that source, and our\n"
+"technical documentation, need much more review."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:229
+msgid "Paid VPN Services"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:230
+#: i2p2www/pages/site/comparison/other-networks.html:236
+#, python-format
+msgid ""
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:235
+msgid "Others"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:2
+msgid "I2P Compared to Tor"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:8
+#, python-format
+msgid ""
+"Tor and Onion Routing are both anonymizing proxy networks, \n"
+"allowing people to tunnel out through their low latency mix \n"
+"network. The two primary differences between Tor / \n"
+"Onion-Routing and I2P are again related to differences in \n"
+"the threat model and the out-proxy design (though Tor\n"
+"supports hidden services as well).  In addition, Tor\n"
+"takes the directory-based approach - providing a \n"
+"centralized point to manage the overall 'view' of the \n"
+"network, as well as gather and report statistics, as \n"
+"opposed to I2P's distributed network \n"
+"database and peer selection."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:22
+msgid ""
+"The I2P/Tor outproxy functionality does have a few \n"
+"substantial weaknesses against certain attackers - \n"
+"once the communication leaves the mixnet, global passive\n"
+"adversaries can more easily mount traffic analysis.  In \n"
+"addition, the outproxies have access to the cleartext \n"
+"of the data transferred in both directions, and \n"
+"outproxies are prone to abuse, along with all of the \n"
+"other security issues we've come to know and love with \n"
+"normal Internet traffic."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:34
+msgid ""
+"However, many people don't need to worry about those \n"
+"situations, as they are outside their threat model.  It\n"
+"is, also, outside I2P's (formal) functional scope (if people want\n"
+"to build outproxy functionality on top of an anonymous\n"
+"communication layer, they can).  In fact, some I2P users\n"
+"currently take advantage of Tor to outproxy."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:48
+msgid "Comparison of Tor and I2P Terminology"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:49
+msgid ""
+"While Tor and I2P are similar in many ways, much of the terminology is "
+"different."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Cell"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Message"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Client"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Router or Client"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Circuit"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Tunnel"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "Directory"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "NetDb"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Directory Server"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Floodfill Router"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Entry Guards"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Fast Peers"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Entry Node"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Inproxy"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Exit Node"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Outproxy"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Hidden Service"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Eepsite or Destination"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "Hidden Service Descriptor"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "LeaseSet"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Introduction point"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Inbound Gateway"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:65
+msgid "Node"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:65
+#: i2p2www/pages/site/comparison/tor.html:67
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Router"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "Onion Proxy"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "I2PTunnel Client (more or less)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:67
+msgid "Relay"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "Rendezvous Point"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "somewhat like Inbound Gateway + Outbound Endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "Router Descriptor"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Server"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:73
+msgid "Benefits of Tor over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:76
+msgid ""
+"Much bigger user base; much more visibility in the academic and hacker "
+"communities; benefits from\n"
+"formal studies of anonymity, resistance, and performance;\n"
+"has a non-anonymous, visible, university-based leader"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:82
+msgid "Has already solved some scaling issues I2P has yet to address"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:83
+msgid "Has significant funding"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:84
+msgid "Has more developers, including several that are funded"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:86
+msgid ""
+"More resistant to state-level blocking due to TLS transport layer and "
+"bridges\n"
+"(I2P has proposals for \"full restricted routes\" but these are not yet "
+"implemented)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:91
+msgid "Big enough that it has had to adapt to blocking and DOS attempts"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:92
+msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:94
+msgid ""
+"Better documentation, has formal papers and specifications,\n"
+"better website, many more translations"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:99
+msgid "More efficient with memory usage"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:100
+msgid "Tor client nodes have very low bandwidth overhead"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:102
+msgid ""
+"Centralized control reduces the complexity at each\n"
+"node and can efficiently address Sybil attacks"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:108
+msgid ""
+"A core of high capacity nodes provides higher\n"
+"throughput and lower latency"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:113
+msgid "C, not Java (ewww)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:116
+msgid "Benefits of I2P over Tor"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:118
+msgid ""
+"Designed and optimized for hidden services, which are much faster than in"
+" Tor"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:119
+msgid "Fully distributed and self organizing"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:121
+msgid ""
+"Peers are selected by continuously profiling and ranking performance,\n"
+"rather than trusting claimed capacity"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:127
+msgid ""
+"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
+"rather than hardcoded"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:132
+msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:133
+msgid "Peer-to-peer friendly"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:134
+msgid "Packet switched instead of circuit switched"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:137
+msgid ""
+"implicit transparent load balancing of messages \n"
+"across multiple peers, rather than a single path"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:143
+msgid ""
+"resilience vs. failures by running multiple \n"
+"tunnels in parallel, plus rotating tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:149
+msgid ""
+"scale each client's connections at O(1) instead \n"
+"of O(N) (Alice has e.g. 2 inbound tunnels that are \n"
+"used by all of the peers Alice is talking with, \n"
+"rather than a circuit for each)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:159
+msgid ""
+"Unidirectional tunnels instead of bidirectional\n"
+"circuits, doubling the number of nodes a peer has to\n"
+"compromise to get the same information."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:166
+msgid ""
+"Protection against detecting client activity, even\n"
+"when an attacker is participating in the tunnel, as\n"
+"tunnels are used for more than simply passing end \n"
+"to end messages (e.g. netDb, tunnel management, \n"
+"tunnel testing)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:175
+msgid ""
+"Tunnels in I2P are short lived, decreasing the number\n"
+"of samples that an attacker can use to mount an \n"
+"active attack with, unlike circuits in Tor, which are\n"
+"typically long lived."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:183
+msgid ""
+"I2P APIs are designed specifically for anonymity and\n"
+"security, while SOCKS is designed for functionality."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:188
+msgid "Essentially all peers participate in routing for others"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:190
+msgid ""
+"The bandwidth overhead of being a full peer is low, \n"
+"while in Tor, while client nodes don't require much\n"
+"bandwidth, they don't fully participate in the mixnet."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:196
+msgid "Integrated automatic update mechanism"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:197
+msgid "Both TCP and UDP transports"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:198
+msgid "Java, not C (ewww)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:201
+msgid "Other potential benefits of I2P but not yet implemented"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:202
+msgid "...and may never be implemented, so don't count on them!"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:205
+msgid ""
+"Defense vs. message count analysis by garlic wrapping \n"
+"multiple messages"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:211
+msgid ""
+"Defense vs. long term intersection by adding delays \n"
+"at various hops (where the delays are not discernible\n"
+"by other hops)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:218
+msgid ""
+"Various mixing strategies at the tunnel level (e.g.\n"
+"create a tunnel that will handle 500 messages / minute,\n"
+"where the endpoint will inject dummy messages if there\n"
+"are insufficient messages, etc)"
+msgstr ""
+
diff --git a/i2p2www/translations/de/LC_MESSAGES/messages.po b/i2p2www/translations/de/LC_MESSAGES/docs.po
similarity index 55%
rename from i2p2www/translations/de/LC_MESSAGES/messages.po
rename to i2p2www/translations/de/LC_MESSAGES/docs.po
index 9bb75dea..3dd53a41 100644
--- a/i2p2www/translations/de/LC_MESSAGES/messages.po
+++ b/i2p2www/translations/de/LC_MESSAGES/docs.po
@@ -4,15 +4,17 @@
 #
 # Translators:
 # amiga4000 , 2008
+# D.A. Loader, 2013
+# Ashoka , 2013
 # SteinQuadrat, 2013
 # zeroflag , 2013
 msgid ""
 msgstr ""
 "Project-Id-Version:  I2P\n"
-"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
-"POT-Creation-Date: 2013-07-03 03:49+0000\n"
-"PO-Revision-Date: 2013-06-30 10:33+0000\n"
-"Last-Translator: driz \n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-12-12 06:19+0000\n"
+"Last-Translator: str4d \n"
 "Language-Team: German "
 "(http://www.transifex.com/projects/p/I2P/language/de/)\n"
 "Plural-Forms: nplurals=2; plural=(n != 1)\n"
@@ -21,6268 +23,18 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 "Generated-By: Babel 0.9.6\n"
 
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:24
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:25
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:12
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:12
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:17
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:16
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:16
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:26
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:19
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:19
-msgid "Files are available on the `download page`_."
-msgstr "Die Dateien sind verfügbar auf der `Download Seite`_."
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:28
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:15
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:29
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:16
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:16
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:21
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:20
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:20
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:30
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:23
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:23
-msgid "`download page`"
-msgstr "`Download Seite`"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:30
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:17
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:31
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:18
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:19
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:18
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:22
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:22
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:32
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:25
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:79
-msgid "RELEASE DETAILS"
-msgstr "RELEASE DETAILS"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:32
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:19
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:33
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:40
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:50
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:24
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:24
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:34
-msgid "Major Changes"
-msgstr "Wesentliche Änderungen"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:44
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:24
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:43
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:55
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:47
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:58
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:43
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:32
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:30
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:39
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:81
-msgid "Bug Fixes"
-msgstr "Bug Fixes"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:54
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:30
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:47
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:69
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:63
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:68
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:54
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:41
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:36
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:51
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:43
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:94
-msgid "Other"
-msgstr "Andere"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:73
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:36
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:51
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:82
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:75
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:96
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:76
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:52
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:56
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:67
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:56
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:110
-msgid "SHA256 Checksums:"
-msgstr "SHA256 Checksumme:"
-
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39
-msgid "Major changes"
-msgstr ""
-
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47
-msgid "Wrapper Update"
-msgstr ""
-
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:23
-msgid "Update Info"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2
-msgid "0.9.2 Release"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9
-msgid ""
-"0.9.2 includes extensive low-level changes to improve the performance and"
-" efficiency of the router. We have updated our UPnP library, to hopefully"
-" make UPnP work for more people. I2PSnark now has DHT support, but it is "
-"not yet enabled by default, as we plan to do more testing during the "
-"upcoming 0.9.3 development cycle."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12
-msgid ""
-"As usual, there's also lots of bug fixes in this release, so updating is "
-"recommended."
-msgstr ""
-"Wie üblich gibt es in diesem Release eine Menge Bug Fixes. Deswegen "
-"empfehlen wir eine Aktualisierung."
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26
-msgid ""
-"SSU: Fix several problems in our UDP transport, to improve efficiency and"
-" reliability for connection setup. Also improve defenses against various "
-"types of bad input."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27
-msgid ""
-"UPnP: Updated our library to fix several issues, should work for more "
-"routers now"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28
-msgid ""
-"Transport: Improve performance in both our TCP and UDP transports, to "
-"benefit high-bandwidth routers"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29
-msgid ""
-"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered "
-"are now much more flexible, which should lessen protocol overhead and "
-"reduce stalls caused by dropped tags."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30
-msgid ""
-"I2PSnark: Add DHT support, not yet enabled by default, will do further "
-"testing and plan to enable by default in 0.9.3."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34
-msgid ""
-"Fix various issues affecting memory usage and performance on high-"
-"bandwidth routers"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35
-msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36
-msgid "Fix i2psnark bug that prevented a completion announcement to the tracker"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37
-msgid "Fix a lock contention problem in i2ptunnel"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38
-msgid "Fix some OSX installation issues"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39
-msgid "Remove uses of direct byte buffers that may have been leaking"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43
-msgid "Reduce overhead in network messages"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44
-msgid "Add \"universal\" theme support"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45
-msgid "Theme updates"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46
-msgid "Add a jbigi library for Raspberry Pi"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47
-msgid "New Scala unit test framework"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48
-msgid "Translation updates for Czech, Dutch, German, and Greek"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49
-msgid "Update wrapper to 3.5.15 (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108
-msgid "Update GeoIP data (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:2
-msgid "0.9.3 Release"
-msgstr "0.9.3 Release"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9
-msgid ""
-"0.9.3 includes extensive low-level changes to the queueing of messages in"
-" the router.  We implement the CoDel Active Queue Management (AQM) "
-"algorithm.  We also unify the queueing and priority mechanisms in the "
-"transports to aid diagnosis and reduce network latency.  Work continues "
-"on fixing UDP transport bugs and making UDP more resistant to attacks.  "
-"There are more changes to improve the performance of the router and "
-"reduce its memory usage.  Also, we enable i2psnark's DHT support, "
-"introduced last release, by default."
-msgstr ""
-"0.9.3 beinhaltet erweiterte low-level Änderungen der "
-"Nachrichtenwarteschlange im Router. Wir haben den CoDel Active Queue "
-"Management (AQM) Algorithmus implementiert. Außerdem wurde der "
-"Transportwarteschlangen - und Transportprioritätsmechanismus  für bessere"
-" Diagnose und Netzwerk Latenz vereinheitlicht. Wir arbeiten weiterhin an "
-"der Beseitigung des UDP Transportbugs und machen UDP sicherer gegen "
-"Attacken. Des weiteren gibt es am Router änderungen zur "
-"Leistungssteigerung und Verringerung des Speicherverbrauchs. Ebenfalls "
-"wurde die DHT funktionalität von i2psnark, welche mit dem letzten Release"
-" eingeführt wurde, standardmäßig aktiviert."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26
-msgid "Active Queue Management"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:27
-msgid "Priority queues"
-msgstr "Prioritäts Warteschlangen"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28
-msgid "I2PSnark DHT: Several bug fixes, enable by default."
-msgstr "I2PSnark DHT: Diverse Bug Fixes, standardmäßig aktiviert."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32
-msgid ""
-"Several SSU fixes including memory leak, and better handling of routers "
-"behind firewalls that change UDP ports; additional defenses for malicious"
-" packets."
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33
-msgid "Fix piece selection (rarest-first) bugs in i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34
-msgid "Fix bug causing multiple browsers to open at startup"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38
-msgid "Improvements in caching"
-msgstr "Verbesserungen im Caching"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39
-msgid "Several synchronization fixes and lock contention reduction"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40
-msgid "Major reduction in SSU buffers memory use"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41
-msgid ""
-"Fix streaming connection timeout back to 1 minute, was inadvertently "
-"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was"
-" unlimited"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42
-msgid "Improved defenses in i2ptunnel for \"darkloris\""
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:43
-msgid "More validation at torrent creation in i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44
-msgid "Several parameter changes in SSU to improve throughput"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45
-msgid ""
-"New event log for major events including restarts; show multiple restart "
-"lines on graphs"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46
-msgid "Remove duplicate messages from logs"
-msgstr "Entferne doppelte Einträge/Nachrichten im Log"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47
-msgid "Don't respond to blocked streaming connections with a reset, just drop"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48
-msgid "Remove all uses of inefficient SimpleTimer"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49
-msgid "More checks for valid IPs and ports entered in console"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50
-msgid "Fix bug that wasted a lot of entropy"
-msgstr ""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51
-msgid "Translation updates: Italian, Portuguese, Spanish, Swedish"
-msgstr "Übersetzungsupdates: Italienisch, Portugiesisch, Spanisch, Schwedisch"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52
-msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2
-msgid "0.9.4 Release"
-msgstr "0.9.4 Release"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9
-msgid ""
-"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, "
-"that was reducing network performance and reliability. It also includes "
-"major changes in the in-network update system, and adds the capability to"
-" update via in-network torrents."
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13
-msgid ""
-"We fixed several bugs in the i2psnark DHT implementation that was "
-"introduced\n"
-"last release. For those of you using console or http proxy passwords,\n"
-"we converted to the more-secure digest method and improved the security "
-"for console forms."
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19
-msgid ""
-"For those of you already running development builds, your router should "
-"automatically\n"
-"update to 0.9.4-0 using the new in-network torrent facility.\n"
-"For those running 0.9.3-0, you will update normally using in-network "
-"HTTP, and\n"
-"we will have more information for you when we release 0.9.5."
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36
-msgid ""
-"Big rework of the update system; Preliminary support for updates via "
-"i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37
-msgid "Add per-destination outbound priorities"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41
-msgid ""
-"Fix major bug that reduced SSU connection limits which reduced tunnel "
-"build success rates"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42
-msgid "Fix bug with external I2CP that prevented some external apps from working"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43
-msgid "Fixed several bugs in i2psnark DHT"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44
-msgid "Fixed bug in i2psnark PEX that inflated peer counts"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45
-msgid "Handle dropped I2CP messages better"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46
-msgid "Reduce overhead of I2CP messages"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47
-msgid "Enforce max size in transport outbound message queues"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48
-msgid "Fixes for Windows eepget.bat (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49
-msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53
-msgid ""
-"More performance improvements, memory reduction, and object churn "
-"reduction"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54
-msgid "Better detection of network disconnections"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55
-msgid "Further improvements in the SSU transport"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56
-msgid "Add console password form"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57
-msgid ""
-"Convert http proxy and console from basic to digest authentication for "
-"added security"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58
-msgid ""
-"Improved verification of console form submissions, using jsp sessions. "
-"Cookies may now be required on forms, except when the console password is"
-" enabled"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59
-msgid ""
-"Initial work on new interfaces to manage applications started via "
-"clients.config"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60
-msgid "Increase minimum peer port to 1024"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61
-msgid "Increase granularity of bandwidth limiter for smoother transmissions"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62
-msgid ""
-"Translation updates: Chinese, French, German, Italian, Polish, "
-"Portuguese, Swedish, and Ukrainian"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64
-msgid "Update wrapper to 3.5.16 (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65
-msgid "New ARMv6 wrapper for Raspberry Pi"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:2
-msgid "0.9.5 Release"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9
-msgid ""
-"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities"
-" that are being investigated by researchers at UCSB. We continue to work "
-"with them on additional improvements. This is a good opportunity to "
-"remind the community that while our network continues to grow rapidly, it"
-" is still relatively small. There may be multiple weaknesses or bugs that"
-" could compromise your anonymity. Help us grow the network by spreading "
-"the word and contributing where you can."
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13
-#, python-format
-msgid ""
-"In this upgrade cycle, a random 1% of routers, (plus all routers running "
-"a\n"
-"development build) will attempt to update via the experimental in-network"
-" bittorrent\n"
-"with i2psnark. If this doesn't work, it should fall back to standard in-"
-"network HTTP update."
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27
-msgid "Defenses and Bug Fixes"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29
-msgid "Fix router bug causing lockup when using iMule"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30
-msgid "Recognize, handle, reject duplicate tunnel IDs"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31
-msgid "Fix changing of the log file name"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32
-msgid "Prevent hashcode attack in session tags"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33
-msgid "Add build request throttler based on previous hop"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34
-msgid "Limit concurrent next-hop lookups"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35
-msgid "Catch exceptions storing nonces in console"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36
-msgid "Fix saving graph settings in console"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37
-msgid "Fix eepget generation of URLs when not proxied"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38
-msgid ""
-"Encrypt database lookup messages end-to-end when sent through exploratory"
-" tunnels"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39
-msgid "Don't use multiple floodfills from the same /16 in a query"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40
-msgid "Randomize delay before verifying floodfill store"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41
-msgid "Increase number of floodfills"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:45
-msgid "Improve support for mobile browsers"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46
-msgid "Partial defenses for UCSB attacks"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47
-msgid "Add announce list support to i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48
-msgid "Jetty: upgrade Apache Tomcat to 6.0.36"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49
-msgid "Split router info files into multiple subdirectories"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50
-msgid "Add IP to hostname mapping option in SOCKS"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51
-msgid "Improve PRNG seeding"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52
-msgid ""
-"Translation updates: French, German, Hungarian, Italian, Norwegian, "
-"Polish, Portuguese, Russian, Swedish"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54
-msgid "Update wrapper to 3.5.17 (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:2
-msgid "0.9.6 Release"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:7
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9
-msgid ""
-"0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to "
-"Jetty 7.6.10 (2013-03-12). See below for important information on the "
-"Jetty update. The Jetty 7 series is actively maintained and we plan to "
-"stay current with it in future I2P releases."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13
-msgid ""
-"Most users will update via HTTP. Those running development builds will "
-"attempt to update via the\n"
-"experimental in-network bittorrent with i2psnark. We've fixed some bugs "
-"that will enable more users\n"
-"to update via torrent in the 0.9.7 update cycle."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25
-msgid "Important fix for Windows Eepsites, first install 0.9.5 only"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27
-msgid ""
-"If you first installed I2P with version 0.9.5, on Windows only, we "
-"recommend that you follow the\n"
-"following instructions to fix your eepsite location **before** you update"
-" to 0.9.6.\n"
-"Only original installations of 0.9.5-0 on Windows are affected by this "
-"issue. If your router version\n"
-"is 0.9.5-0-win1, you already have the fix and need not take any action."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34
-msgid "See `this page`_ for instructions."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:38
-msgid "`this page`"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:40
-msgid "Jetty 7 Migration Details"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42
-msgid ""
-"For most people, the update should just work. If you have multiple Jetty "
-"eepsites,\n"
-"OR have made changes to jetty.xml or other Jetty configuration files, "
-"including changing the port\n"
-"from 7658, you MUST take manual action AFTER updating."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48
-msgid ""
-"After update, the router will migrate your jetty.xml files to the new "
-"Jetty 7 format."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50
-msgid ""
-"The migration resets the port to 7658. If you have more than one Jetty "
-"eepsite, OR your eepsite\n"
-"  is NOT on port 7658, OR you have made other modifications to jetty.xml "
-"(for example changing the\n"
-"  listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml "
-"file for each eepsite to fix them up\n"
-"  after updating, and restart again."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55
-msgid ""
-"**The following files will be backed up with a ".jetty6" suffix"
-" and then migrated.**\n"
-"If you have made local changes, you may have to edit them manually and "
-"restart.\n"
-"See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69
-#: i2p2www/pages/global/nav.html:75 i2p2www/pages/global/nav.html:91
-#: i2p2www/pages/site/docs/plugins.html:2
-#: i2p2www/pages/site/docs/spec/configuration.html:65
-msgid "Plugins"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:71
-msgid "Most plugins should work fine with Jetty 7."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:75
-msgid ""
-"The I2PControl and zzzot plugins must be updated. Your router should "
-"download and install the new versions shortly after starting 0.9.6."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77
-msgid "If a plugin does not work, please contact the maintainer for that plugin."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83
-msgid "Several bugs with Windows installation (see above)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:84
-msgid "Fix default form action in i2ptunnel"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85
-msgid "Fix links on iframed console pages"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86
-msgid "Better detection of 64-bit Windows to prevent crashes by systray"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87
-msgid "Fix bug preventing router update via torrent"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88
-msgid "Several SSU fixes for NATs that change UDP ports"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89
-msgid ""
-"Ignore unsupported IPs in RouterInfos when selecting an address (prep for"
-" IPv6)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90
-msgid ""
-"Ignore unused option bits in Database Lookup Message (prep for requesting"
-" encrypted response)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91
-msgid "Fix HTTP proxy error response for malformed URIs"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92
-msgid "Recognize UPnP devices without port forwarding capability"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96
-msgid "Jetty 7.6.10 (see above for migration information)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97
-msgid "Limit page size in i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98
-msgid "Add data directory and page size configuration to i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99
-msgid "Support multiple i2psnark instances"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100
-msgid "Piece size adjustments in i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101
-msgid "Add more graphing support for combined bandwidth graph"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102
-msgid "Block b32.i2p supercookies"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103
-msgid "Allow stopping clients on /configclients"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104
-msgid "Check for nonce count replays in HTTP client"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105
-msgid "Support SASL authentication in IRC proxy"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106
-msgid "Several cleanups and minor fixes in the update manager"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107
-msgid "Translation updates: German, Portuguese, Russian, Spanish, and Swedish"
-msgstr ""
-
-#: i2p2www/pages/blog/category.html:2
-msgid "Blog Category"
-msgstr ""
-
-#: i2p2www/pages/blog/category.html:4
-#, python-format
-msgid "I2P Blog ATOM Feed for Category: %(category)s"
-msgstr ""
-
-#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
-#: i2p2www/pages/global/nav.html:95
-msgid "Blog"
-msgstr "Blog"
-
-#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:75
-msgid "I2P Blog ATOM Feed"
-msgstr ""
-
-#: i2p2www/pages/blog/index.html:17
-#, python-format
-msgid "Posted %(date)s by %(author)s"
-msgstr ""
-
-#: i2p2www/pages/blog/latest.html:5
-msgid "More blog posts…"
-msgstr ""
-
-#: i2p2www/pages/blog/post.html:6
-msgid "Posted:"
-msgstr ""
-
-#: i2p2www/pages/blog/post.html:7
-msgid "Author:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:4
-msgid "Debian I2P Packages"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:6
-#, python-format
-msgid ""
-"The packages hosted on the I2P Launchpad site\n"
-"have been tested and should work on x86/x86_64 platforms running:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:11
-msgid "Ubuntu (Precise 12.04 and newer)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:13
-msgid ""
-"Debian Linux (Wheezy and newer) & kFreeBSD"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:17
-#, python-format
-msgid ""
-"The I2P packages may work on systems not listed above. Please "
-"report any issues\n"
-"with these packages on Trac at\n"
-"http://%(trac)s."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:23
-msgid ""
-"Option 1: Recent versions of Ubuntu and its "
-"derivatives (Try this if you're not using Debian)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:24
-msgid "Option 2: Debian (including Debian-derivatives)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:25
-msgid ""
-"Option 3: Non-Linux (and possibly Non-x86 "
-"architectures)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:28
-msgid ""
-"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
-" Linux Mint & Trisquel"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:29
-msgid "Adding the PPA via the command line and installing I2P"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:32
-msgid "Open a terminal and enter:"
-msgstr "Öffne eine Konsole und gib ein:"
-
-#: i2p2www/pages/downloads/debian.html:34
-msgid ""
-"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
-"gpg key that the repository has been signed with. The GPG key ensures\n"
-"that the packages have not been tampered with since being built."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:41
-msgid "Notify your package manager of the new PPA by entering:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:43
-msgid ""
-"This command will retrieve the latest list of software from each\n"
-"repository that is enabled on your system, including the I2P PPA that\n"
-"was added with the earlier command."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:49
-#: i2p2www/pages/downloads/debian.html:112
-#: i2p2www/pages/downloads/debian.html:137
-msgid "You are now ready to install I2P!"
-msgstr "Sie/Du bist nun bereit I2P zu installieren!"
-
-#: i2p2www/pages/downloads/debian.html:53
-msgid "Adding the PPA Using Synaptic"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:56
-msgid ""
-"Open Synaptic (System -> Administration -> Synaptic Package "
-"Manager)."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:61
-msgid ""
-"Once Synaptic opens, select Repositories from the "
-"Settings menu."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:66
-msgid ""
-"Click the Other Sources tab and click Add. Paste "
-"ppa:i2p-maintainers/i2p into the APT-line field and click "
-"Add Source. Click the Close button then "
-"Reload."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:71
-msgid ""
-"In the Quick Filter box, type in i2p and press enter. When "
-"i2p is returned in the results list, right click "
-"i2p and select Mark for Installation. After doing "
-"so you may see a Mark additional required changes? popup. If so,"
-" click Mark then Apply."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:77
-msgid ""
-"After the installation process completes you can move on to the next\n"
-"part of starting I2P and configuring "
-"it for your system."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:82
-msgid "Instructions for Debian Lenny and newer"
-msgstr "Anleitungen für Debian Lenny und Neuere:"
-
-#: i2p2www/pages/downloads/debian.html:84
-msgid ""
-"For Squeeze you can follow the instructions here."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:86
-msgid ""
-"The steps below should be performed with root access (i.e., switching\n"
-"user to root with \"su\" or by prefixing each command with \"sudo\")."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:92
-msgid "Add the GPG key that signs the repository with the following command:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:94
-msgid "You'll have output like the following if the command was successful:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:98
-msgid "Add the following entries to /etc/apt/sources.list.d/i2p.list"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:103
-msgid "Notify your package manager of the new PPA by entering"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:105
-msgid ""
-"This command will retrieve the latest list of software from every\n"
-"repository enabled on your system, including the I2P PPA added in step\n"
-"1."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:116
-#: i2p2www/pages/downloads/debian.html:147
-msgid ""
-"After the installation process completes you can move on to the next part"
-" of starting I2P and configuring it "
-"for your system."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:120
-msgid "Instructions for Non-Linux / Non-x86"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:122
-msgid ""
-"The steps below should be performed with root access (i.e., switching\n"
-"user to root with \"su\" or by prefixing each command with "
-"\"sudo\")."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:128
-#, python-format
-msgid ""
-"Download the i2p-router package from the PPA.\n"
-"Alternatively, there are unofficial packages available here for armel, armhf, and kfreebsd."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:135
-msgid ""
-"Make sure that you have Java installed. Running apt-get install"
-" default-jre should be sufficient."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:141
-#, python-format
-msgid ""
-"It is recommended to compile jbigi for your "
-"system to achieve better performance. Instructions are available here."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:151
-#: i2p2www/pages/downloads/list.html:167
-msgid "Post-install work"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:154
-msgid ""
-"Using these I2P packages the I2P router can be started in the following\n"
-"three ways:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:160
-msgid ""
-""on demand" using the i2prouter script. Simply run "
-""i2prouter\n"
-"start" from a command prompt. (Note: Do "
-"not use\n"
-"sudo or run it as root!)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:167
-msgid ""
-""on demand" without the java service wrapper\n"
-"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
-"nowrapper\".\n"
-"(Note: Do not\n"
-"use sudo or run it as root!)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:175
-msgid ""
-"as a service that automatically runs when your system boots, even\n"
-"before logging in. The service can be enabled with \"dpkg-"
-"reconfigure\n"
-"i2p\" as root or using sudo. This is the recommended means of "
-"operation."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:183
-msgid ""
-"When installing for the first time, please remember to adjust your "
-"NAT/firewall\n"
-"if you can. The ports to forward can be found on the \n"
-"network configuration page in the router console. If guidance with "
-"respect to forwarding ports is needed,\n"
-"you may find portforward.com to be"
-" helpful."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:190
-msgid ""
-"Please review and adjust the bandwidth settings on the\n"
-"configuration page,\n"
-"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
-"conservative."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:196
-#: i2p2www/pages/downloads/list.html:200
-#, python-format
-msgid ""
-"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
-"howto."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
-#: i2p2www/pages/global/nav.html:3
-msgid "Download"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:4
-msgid "Download I2P"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:6
-msgid "Dependency"
-msgstr "Abhängigkeit"
-
-#: i2p2www/pages/downloads/list.html:7
-#, python-format
-msgid ""
-"\n"
-"Java Runtime 1.5 or higher.\n"
-"(Oracle Java Version 6/7,\n"
-"OpenJDK 6/7, or\n"
-"IcedTea6/7\n"
-" recommended)\n"
-"
            \n"
-"Determine"
-" your installed Java version here\n"
-"or type java -version at your command prompt.\n"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:20
-msgid "Clean installs"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:27 i2p2www/pages/downloads/list.html:45
-#: i2p2www/pages/downloads/list.html:73 i2p2www/pages/downloads/list.html:135
-#: i2p2www/pages/downloads/list.html:265
-msgid "select alternate link"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:35
-msgid "Download that file and run it."
-msgstr "Lade die Datei herunter und führe sie aus."
-
-#: i2p2www/pages/downloads/list.html:53
-#, python-format
-msgid ""
-"Download that file and double-click it (if that works) or\n"
-"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
-"terminal to run the\n"
-"    installer.\n"
-"    You may be able to right-click and select\n"
-"    "Open with Java"."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:61 i2p2www/pages/downloads/list.html:89
-msgid "Command line (headless) install:"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:62
-#, python-format
-msgid ""
-"Download the %(i2pversion)s OSX graphical installer file above and\n"
-"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
-"from the command line."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:81
-#, python-format
-msgid ""
-"Download that file and double-click it (if that works) or\n"
-"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
-"terminal to run the\n"
-"    installer.\n"
-"    On some platforms you may be able to right-click and select\n"
-"    "Open with Java"."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:90
-#, python-format
-msgid ""
-"Download the graphical installer file above and\n"
-"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
-"from the command line."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:100
-msgid "Packages for Debian & Ubuntu are available."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:115
-#, python-format
-msgid ""
-"The Android version of I2P is being actively developed.\n"
-"    The latest dev build is version 0.9.3-5_b2-API8, and is available "
-"from\n"
-"    sponge's eepsite -\n"
-"    scan or click the QR code."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:122
-msgid ""
-"The release and dev versions of the I2P APK are not compatible, as they\n"
-"      are signed by zzz and sponge respectively. Uninstall one before "
-"installing\n"
-"      the other."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:132
-msgid "Source package"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:143
-#, python-format
-msgid ""
-"Alternately, you can fetch the source from monotone\n"
-"    or via Git from git.repo.i2p or Github.\n"
-"    
            \n"
-"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
-"i2p-%(i2pversion)s ; ant pkg) then either\n"
-"    run the GUI installer or headless install as above."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:158
-#, python-format
-msgid ""
-"The files are signed by zzz,\n"
-"whose key is here."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:163
-msgid ""
-"I2P can also be downloaded from our project pages on Launchpad and Google Code."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:169
-msgid ""
-"After running the installer on windows, simply click on the \"Start I2P\""
-" button\n"
-"which will bring up the router console,\n"
-"which has further instructions."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:175
-msgid ""
-"On Unix-like systems, I2P can be started as a service\n"
-"using the \"i2prouter\" script, located in the directory you selected for"
-" I2P.\n"
-"Changing to that directory in a console and issuing \"sh i2prouter "
-"status\"\n"
-"should tell you the router's status. The arguments \"start\", \"stop\" "
-"and \"restart\"\n"
-"control the service. The router console\n"
-"can be accessed at its usual location.\n"
-"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
-" is not supported,\n"
-"start the router with \"sh runplain.sh\" instead."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:186
-#, python-format
-msgid ""
-"When installing for the first time, please remember to adjust your "
-"NAT/firewall\n"
-"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
-"described here among other ports.\n"
-"If you have successfully opened your port to inbound TCP, also enable "
-"inbound TCP on the\n"
-"configuration page."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:194
-msgid ""
-"Also, please review and adjust the bandwidth settings on the\n"
-"configuration page,\n"
-"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:204
-msgid "Updates from earlier releases:"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:206
-msgid "Both automatic and manual upgrades are available for the release."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:211
-msgid "Automatic updates"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:213
-msgid ""
-"If you are running 0.7.5 or later, your router should detect the\n"
-"new release. To upgrade simply click the 'Download Update' button on your"
-" router console\n"
-"when it appears."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:219
-msgid ""
-"Due to a bug in release 0.7.6, those whose first I2P installation was "
-"that version\n"
-"and have not upgraded manually\n"
-"may get a \"downloaded version is not greater than current version\" "
-"error,\n"
-"and should use the manual update method below."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:227
-#, python-format
-msgid ""
-"If you are running 0.7.4 or earlier, please see\n"
-"the 0.7.5 release notes\n"
-"for important information about how to configure your router to "
-"automatically\n"
-"receive the release."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:235
-#, python-format
-msgid ""
-"If you are running 0.6.1.30 or earlier, please see\n"
-"instructions\n"
-"for important information about how to configure your router to "
-"automatically\n"
-"receive the release."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:244
-#, python-format
-msgid ""
-"If you have reconfigured your router following the instructions, you should see a link on your"
-" \n"
-"    router console "
-"allowing\n"
-"    you to download and install the new release by just clicking on that\n"
-"    link."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:252
-msgid "Alternately, you can use the manual method specified below."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:262
-msgid "Manual updates"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:275
-msgid ""
-"Download that file to your I2P\n"
-"    installation directory and rename as i2pupdate.zip.\n"
-"    (alternately, you can get the source as above and run \"ant "
-"updater\", then copy the\n"
-"    resulting i2pupdate.zip to your I2P installation directory).  You do"
-" \n"
-"    NOT need to unzip that file."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:284
-msgid "Click \"Restart\""
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:289
-msgid "Grab a cup of coffee and come back in 11 minutes"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:297
-#, python-format
-msgid ""
-"The file is signed by zzz,\n"
-"whose key is here."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:302
-msgid "Previous Releases"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:304
-#, python-format
-msgid ""
-"Previous releases are available on Google "
-"Code\n"
-"and Launchpad\n"
-"and within the I2P network on %(echelon)s."
-msgstr ""
-
-#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
-msgid "Mirror selection"
-msgstr ""
-
-#: i2p2www/pages/downloads/select.html:5
-msgid "File:"
-msgstr ""
-
-#: i2p2www/pages/downloads/select.html:10
-msgid "Any mirror"
-msgstr ""
-
-#: i2p2www/pages/global/bounty.html:19
-msgid ""
-"To claim the bounty the author must not be paid by other organizations\n"
-"or teams for this work (e.g. GSoC students are not valid)."
-msgstr ""
-
-#: i2p2www/pages/global/bounty.html:29
-#, python-format
-msgid ""
-"Bounty amounts may be increased by further donations.  Do\n"
-"you think these are important? Add in your "
-"donation, \n"
-"marking the amount for the %(donatename)s bounty!"
-msgstr ""
-
-#: i2p2www/pages/global/error_404.html:3
-msgid "Not found"
-msgstr ""
-
-#: i2p2www/pages/global/error_404.html:9
-msgid ""
-"Yep... the resource, you were searching for, is named differently, "
-"doesn't exist or was removed."
-msgstr ""
-
-#: i2p2www/pages/global/error_500.html:5
-msgid "Server error"
-msgstr ""
-
-#: i2p2www/pages/global/error_500.html:13
-msgid "500 Server error"
-msgstr ""
-
-#: i2p2www/pages/global/error_500.html:17
-msgid "Umm... the server encountered some sort of error."
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:2
-msgid "Mirrors"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:10
-msgid "Secure"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:16
-msgid "Misc."
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
-msgid "Links"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:20
-msgid "Impressum"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:24
-msgid "T-Shirts!"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:26
-msgid "Europe"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:27
-msgid "USA"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:31
-#: i2p2www/pages/site/get-involved/donate.html:2
-#: i2p2www/pages/site/get-involved/index.html:74
-msgid "Donate"
-msgstr ""
-
-#: i2p2www/pages/global/layout.html:29
-msgid "Skip navigation"
-msgstr ""
-
-#: i2p2www/pages/global/layout.html:32
-msgid "I2P Logo"
-msgstr ""
-
-#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
-#: i2p2www/pages/site/about/intro.html:4
-msgid "The Invisible Internet Project"
-msgstr ""
-
-#: i2p2www/pages/global/layout.html:56
-#, python-format
-msgid ""
-"This page was last updated in %(lastupdated)s and is accurate for router "
-"version %(accuratefor)s."
-msgstr ""
-
-#: i2p2www/pages/global/layout.html:60
-#, python-format
-msgid "This page was last updated in %(lastupdated)s."
-msgstr ""
-
-#: i2p2www/pages/global/layout.html:64
-#, python-format
-msgid "This page is accurate for router version %(accuratefor)s."
-msgstr ""
-
-#: i2p2www/pages/global/macros:19
-msgid "Previous"
-msgstr ""
-
-#: i2p2www/pages/global/macros:34
-msgid "Next"
-msgstr ""
-
-#: i2p2www/pages/global/macros:41
-msgid "Posted in"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:4
-msgid "About"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:6
-msgid "Introduction to I2P"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:7
-msgid "Comparisons"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:9
-msgid "Overview of comparisons"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:13
-msgid "Other anonymous networks"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:16
-#: i2p2www/pages/site/get-involved/index.html:29
-msgid "Documentation"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:18
-msgid "Documentation index"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:19 i2p2www/pages/site/about/intro.html:17
-msgid "How does it work?"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:21
-msgid "Gentle intro"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:22
-msgid "Tech intro"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:23
-msgid "Threat model"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:24
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:292
-msgid "Garlic routing"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:25
-msgid "Network database"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:26
-msgid "Tunnel routing"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:27
-#: i2p2www/pages/site/docs/tunnels/unidirectional.html:21
-msgid "Peer selection"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:28
-#: i2p2www/pages/site/docs/how/tech-intro.html:17
-#: i2p2www/pages/site/docs/how/tech-intro.html:458
-msgid "Cryptography"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:29
-msgid "ElGamal/AES+SessionTags"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:32 i2p2www/pages/global/nav.html:116
-#: i2p2www/pages/site/docs/spec/configuration.html:75
-#: i2p2www/pages/site/get-involved/index.html:48
-msgid "Applications"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:34
-msgid "Supported applications"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:35
-msgid "Bittorrent"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:38
-#: i2p2www/pages/site/docs/api/streaming.html:58
-msgid "API"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:46 i2p2www/pages/global/nav.html:77
-#: i2p2www/pages/site/docs/how/tech-intro.html:808
-msgid "Streaming library"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:47
-msgid "Ministreaming library"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:48 i2p2www/pages/global/nav.html:71
-#: i2p2www/pages/site/docs/index.html:88
-#: i2p2www/pages/site/docs/api/datagrams.html:2
-#: i2p2www/pages/site/get-involved/develop/applications.html:277
-msgid "Datagrams"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:52
-msgid "Protocols"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:54
-msgid "Protocol stack"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:59
-#: i2p2www/pages/site/docs/how/cryptography.html:394
-msgid "Transports"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:61 i2p2www/pages/site/docs/index.html:158
-msgid "Transport layer overview"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:66
-msgid "Specifications"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:68
-msgid "Blockfile"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:69
-msgid "Common structures"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:70
-msgid "Configuration files"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:72
-msgid "GeoIP files"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:78
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:230
-msgid "Tunnel creation"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:79
-msgid "Tunnel messages"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:80
-msgid "Software updates"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:83 i2p2www/pages/site/docs/index.html:139
-#: i2p2www/pages/site/docs/how/tech-intro.html:14
-#: i2p2www/pages/site/docs/how/tech-intro.html:228
-msgid "Tunnels"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:85
-msgid "Tunnel implementation"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:86
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:288
-msgid "Unidirectional tunnels"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:87
-msgid "Old implementation"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:90
-msgid "Naming and addressbook"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:94 i2p2www/pages/site/about/team.html:2
-msgid "Team"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:96
-msgid "Hall of Fame"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:97
-msgid "Academic papers and peer review"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:98
-msgid "Presentations, tutorials and articles"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:99
-msgid "Contact us"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:102
-msgid "Help"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:104
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
-msgid "FAQ"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:105
-msgid "How to browse I2P"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:106 i2p2www/pages/site/about/glossary.html:2
-msgid "Glossary"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:107
-#: i2p2www/pages/site/about/performance/index.html:2
-#: i2p2www/pages/site/docs/index.html:183
-#: i2p2www/pages/site/get-involved/todo.html:52
-#: i2p2www/pages/site/get-involved/todo.html:456
-msgid "Performance"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:108 i2p2www/pages/site/contact.html:22
-msgid "Forums"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:111
-msgid "Volunteer"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:113
-msgid "Get involved!"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:114
-msgid "Develop"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:117
-#: i2p2www/pages/site/get-involved/develop/licenses.html:2
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115
-msgid "Licenses"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:118
-msgid "Release signing keys"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:119
-msgid "Signed keys"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:120
-msgid "Developers keys"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:121 i2p2www/pages/site/docs/index.html:223
-msgid "Bug tracker"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:124
-msgid "Academic research"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:125
-msgid "Guides"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:127
-msgid "New developers"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:128
-#: i2p2www/pages/site/get-involved/guides/ides.html:2
-msgid "Using an IDE with I2P"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:129
-msgid "Developer guidelines and coding style"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:130
-#: i2p2www/pages/site/get-involved/guides/monotone.html:2
-msgid "Monotone"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:131
-msgid "New translators"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:134
-#: i2p2www/pages/site/get-involved/bounties/index.html:2
-msgid "Bounties"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:135 i2p2www/pages/meetings/index.html:2
-msgid "Meetings"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:136
-#: i2p2www/pages/site/get-involved/roadmap.html:2
-msgid "Roadmap"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:137
-msgid "Task list"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:140
-msgid "Language"
-msgstr ""
-
-#: i2p2www/pages/meetings/index.html:4
-msgid "I2P Meetings ATOM Feed"
-msgstr ""
-
-#: i2p2www/pages/meetings/index.html:7
-msgid "Logs of past I2P meetings"
-msgstr ""
-
-#: i2p2www/pages/meetings/index.html:9
-msgid "Meetings are currently on hold until a more suitable time can be chosen."
-msgstr ""
-
-#: i2p2www/pages/meetings/index.html:13
-#, python-format
-msgid ""
-"If you have something to discuss, please find the developers on IRC in "
-"#i2p-dev.\n"
-"Status updates from developers are also "
-"available."
-msgstr ""
-
-#: i2p2www/pages/meetings/show.html:2
-#, python-format
-msgid "I2P Development Meeting %(id)s"
-msgstr ""
-
-#: i2p2www/pages/meetings/show.html:10
-msgid "Full IRC Log"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:2
-msgid "Contact"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:5
-msgid ""
-"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
-" to this network is set up with new router installs.\n"
-"  We are also present on multiple standard networks like OFTC,\n"
-"  EIN and Freenode.\n"
-"  All I2P-related channels on all these network are linked to the main "
-"channels on Irc2P via relay bots."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:13
-msgid "Channel list:"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:15
-msgid "General i2p discussion"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:16
-msgid "Offtopic"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:17
-msgid "Development talk"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:18
-msgid "Help channel"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:23
-#, python-format
-msgid ""
-"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
-" place to start with inquiries, if the dev IRC channel is inactive."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:27
-msgid "Mailing lists"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:28
-msgid ""
-"I2P does have a mailing list, but it is rarely used as the current small "
-"team of developers prefer to communicate via IRC or the developer forum. "
-"This may change in future."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:33
-msgid "Subscribing"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:34
-msgid ""
-"To subscribe to a mailing list, go to the list information page (linked "
-"below) and fill out the form. I2P-internal email addresses "
-"(foobar@mail.i2p) can be used."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:38
-msgid "Unsubscribing"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:39
-msgid ""
-"To unsubscribe from a mailing list or edit your subscription options, go "
-"to the list information page (linked below) and enter your subscription "
-"email address."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:43
-msgid "Lists"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:46
-msgid "Archive"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:47
-msgid ""
-"General I2P discussion - anything that doesn't fit in a different list "
-"goes here."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:53
-msgid ""
-"You don't like mailing lists? Then this is for you. All mailing lists are"
-" available via NNTP as well."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:58
-msgid "Group-List-mapping:"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:62
-msgid "Servers:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:2
-msgid "Frequently Asked Questions"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:4
-#: i2p2www/pages/site/docs/how/threat-model.html:121
-msgid "Index"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:7
-msgid "General"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
-msgid "What systems will I2P run on?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:10
-msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:263
-msgid "My router has very few active peers, is this OK?"
-msgstr "Mein Router hat sehr wenige  aktive Peers, ist das OK?"
-
-#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:498
-msgid "What do the Active x/y numbers mean in the router console?"
-msgstr "Was bedeuten die Active x/y Nummern in der Router Konsole?"
-
-#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:225
-msgid ""
-"My active peers / known peers / participating tunnels / connections / "
-"bandwidth vary dramatically over time! Is anything wrong?"
-msgstr ""
-"Meine active Peers / known Peers / Participating Tunnel / Verbindungen / "
-"Bandbeite ändern sich stark! Ist irgendwas kaputt?"
-
-#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:348
-msgid "Is using an outproxy safe?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:374
-msgid "Most of the eepsites within I2P are down?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:527
-msgid "What ports does I2P use?"
-msgstr "Welche Ports werden von I2P genutzt?"
-
-#: i2p2www/pages/site/faq.html:17
-msgid "Why is I2P listening for connections on port 32000?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
-msgid "I think I found a bug, where can I report it?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:107
-msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
-msgstr "Was passierte mit *.i2p.net? Was passierte mit jrandom? Ist I2P tot?"
-
-#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:845
-msgid "I have a question!"
-msgstr "Ich habe eine Frage!"
-
-#: i2p2www/pages/site/faq.html:22
-#: i2p2www/pages/site/docs/api/streaming.html:292
-msgid "Setup"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:232
-msgid ""
-"My router has been up for several minutes and has zero or very few "
-"connections"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:390
-msgid "Why is I2P so slow?"
-msgstr "Warum ist I2P so langsam?"
-
-#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
-msgid ""
-"I'm missing lots of hosts in my addressbook. What are some good "
-"subscription links?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:383
-msgid "How do I set up my own eepsite?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:416
-msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
-msgstr "Bittorrent / I2PSnark / Azureus I2P Plugin Fragen?"
-
-#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:423
-msgid "How do I connect to IRC within I2P?"
-msgstr "Wie verbinde ich mich mit dem IRC innerhalb von I2P?"
-
-#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:281
-msgid "I can't access regular Internet sites through I2P."
-msgstr "Ich kann keine normalen Internetseiten über I2P erreichen."
-
-#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:296
-msgid "I can't access https:// or ftp:// sites through I2P."
-msgstr "Ich kann keine https:// oder ftp:// Seiten ü I2P besuchen."
-
-#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:506
-msgid "Is it possible to use I2P as a SOCKS proxy?"
-msgstr "Ist es möglich, I2P als SOCKS Proxy zu nutzen?"
-
-#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:489
-msgid "How do I configure my browser?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:434
-msgid ""
-"How can I access the web console from my other machines or password "
-"protect it?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:474
-msgid "How can I use applications from my other machines?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:748
-msgid "How do I reseed manually?"
-msgstr "Wie reseede ich manuell?"
-
-#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:124
-msgid "My router is using too much CPU?!?"
-msgstr "Mein Router nutzt viel zu viel CPU?!?"
-
-#: i2p2www/pages/site/faq.html:39
-msgid "Misconception"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:366
-msgid ""
-"How do I access IRC, BitTorrent, or other services on the regular "
-"Internet?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:42
-msgid ""
-"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
-"want it to be."
-msgstr ""
-"Ist mein Router ein \"Exit Punkt\" ins normale Internet? Das will ich "
-"nicht!"
-
-#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:188
-msgid ""
-"I am opposed to certain types of content. How do I keep from "
-"distributing, storing, or accessing them?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:45
-msgid "Errors and Their Solutions"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:784
-msgid ""
-"I'm using FreeBSD and when I start I2P I receive an error about "
-"libm.so.4!"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:48
-msgid ""
-"In wrapper.log I see an error stating Protocol family "
-"unavailable when I2P is loading"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
-#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:108
-#: i2p2www/pages/site/faq.html:125 i2p2www/pages/site/faq.html:189
-#: i2p2www/pages/site/faq.html:226 i2p2www/pages/site/faq.html:233
-#: i2p2www/pages/site/faq.html:264 i2p2www/pages/site/faq.html:273
-#: i2p2www/pages/site/faq.html:282 i2p2www/pages/site/faq.html:297
-#: i2p2www/pages/site/faq.html:349 i2p2www/pages/site/faq.html:367
-#: i2p2www/pages/site/faq.html:375 i2p2www/pages/site/faq.html:384
-#: i2p2www/pages/site/faq.html:391 i2p2www/pages/site/faq.html:417
-#: i2p2www/pages/site/faq.html:424 i2p2www/pages/site/faq.html:435
-#: i2p2www/pages/site/faq.html:475 i2p2www/pages/site/faq.html:482
-#: i2p2www/pages/site/faq.html:490 i2p2www/pages/site/faq.html:499
-#: i2p2www/pages/site/faq.html:507 i2p2www/pages/site/faq.html:528
-#: i2p2www/pages/site/faq.html:736 i2p2www/pages/site/faq.html:749
-#: i2p2www/pages/site/faq.html:785 i2p2www/pages/site/faq.html:817
-#: i2p2www/pages/site/faq.html:846 i2p2www/pages/site/get-involved/todo.html:16
-#: i2p2www/pages/site/get-involved/todo.html:28
-#: i2p2www/pages/site/get-involved/todo.html:52
-msgid "link"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:53
-#, python-format
-msgid ""
-"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
-"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
-"(or better) with 128MB of RAM (or more). A chart comparing the performance of"
-" the various JREs can be found at http://%(trac)s/wiki/java, but in "
-"short: it's at all possible, use Sun/Oracle Java or OpenJDK."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:57
-msgid ""
-"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
-"underway to bring I2P to the Android platform."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:65
-msgid "Here are some places, pick one or more."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:71
-msgid "Discuss with the developers on IRC in #i2p-dev"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:75
-msgid "Please include relevant information from the router logs and wrapper logs."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:81
-msgid ""
-"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
-"updated rarely.\n"
-"If you don't have another subscription, you may often have to use "
-"\"jump\" links which\n"
-"is annoying."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:87
-msgid ""
-"Here are some other public addressbook subscription links. You may wish "
-"to add one or two\n"
-"to your susidns "
-"subscription list.\n"
-"You don't need to add all of them, as they sync with each other "
-"periodically.\n"
-"The links using a cgi-bin application employ various strategies to "
-"minimize\n"
-"the number of duplicate addresses delivered, so they should be more "
-"efficient.\n"
-"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
-" malicious\n"
-"subscription could give you incorrect addresses. So think about whether "
-"you\n"
-"want to trust any of these.\n"
-"The operators of these services may have various policies for listing "
-"hosts.\n"
-"Presence on this list does not imply endorsement."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:109
-msgid ""
-"Jrandom was the lead developer of I2P and\n"
-"Syndie for several years.\n"
-"We do not know if or when jrandom will return.\n"
-"The *.i2p.net domains were left in a non-functioning state after a power\n"
-"outage at the hosting company."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:117
-#, python-format
-msgid ""
-"See this page for jrandom's parting message "
-"and additional information\n"
-"on the migration of *.i2p.net to this website."
-msgstr ""
-"Sschaue auf diese Seite für Jrandoms "
-"Abschiedsnachricht und weitere Informationen zur Migration von *.i2p.net "
-"zu dieser Webseite."
-
-#: i2p2www/pages/site/faq.html:122
-msgid "I2P remains in active development."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:126
-msgid "There are many possible causes of high CPU usage. Here is a checklist:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:131
-msgid ""
-"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
-"system. You can check \n"
-"which version of java you have installed by typing java "
-"-version at a \n"
-"command/shell prompt. Performance tends to suffer with other "
-"implementations of java."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:138
-msgid ""
-"Are you running a BitTorrent client over I2P? Try reducing the number of "
-"torrents, the bandwidth limits,\n"
-"or try turning it off completely to see if that helps."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:144
-msgid ""
-"Are your bandwidth limits set too high? It is possible that too much "
-"traffic is going through your\n"
-"I2P router and it is overloaded. Try reducing the setting for share "
-"bandwidth percentage on the configuration page."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:149
-msgid ""
-"Make sure that you're running the latest version of I2P to get the "
-"benefits of increased performance and bug fixes."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:154
-msgid ""
-"Has enough memory been set aside for use by I2P? Look at the memory graph"
-" on the graphs page to see\n"
-"if the memory usage is \"pegged\"—the JVM is spending most of its "
-"time in\n"
-"garbage collection. Increase the setting "
-"wrapper.java.maxmemory in wrapper.config."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:161
-#, python-format
-msgid ""
-"Is the CPU usage simply higher than you would like, or is it pegged at "
-"100% for a long time?\n"
-"If it's pegged, this could be a bug. Look in the logs for clues."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:167
-#, python-format
-msgid ""
-"You may be using the Java-based BigInteger library instead of the native "
-"version,\n"
-"especially if you are running on a new or unusual OS or hardware "
-"(OpenSolaris, mipsel, etc.).\n"
-"See the jbigi page for instructions on\n"
-"diagnosing, building, and testing methods."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:175
-msgid ""
-"If your native jbigi library is working fine, the biggest user of\n"
-"CPU may be routing traffic for participating tunnels. This uses CPU\n"
-"because at each hop a layer of encryption must be decoded.\n"
-"You can limit participating traffic in two ways - by reducing the\n"
-"share bandwidth on\n"
-"confignet.jsp,\n"
-"or by setting router.maxParticipatingTunnels=nnn on\n"
-"configadvanced.jsp."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:190
-msgid ""
-"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
-"I2P is designed to withstand censorship, providing a means for everyone "
-"to communicate freely. \n"
-"The best way to keep your PC free of (encrypted) traffic that you dislike"
-" is to not use I2P.\n"
-"Freedom of speech has some costs.\n"
-"But let's address your question in three parts:"
-msgstr ""
-"Hmm. I2P ist ein anonymes Netzwerk, somit ist dieses Thema schwer zu "
-"lösen. I2P ist für jeden aufgebaut und nicht zum zensieren von "
-"ein paar/allen Daten. Der Beste Weg um deinen PC frei von "
-"(verschlüsseltem) Material, welches Du nicht magst, zu halten, ist "
-"I2P nicht zu nutzen. Die Redefreiheit für jeden (Freedom of Speech) "
-"hat gewisse Kosten, die wir akzeptieren müssen. Aber lass uns die "
-"Frage in 3 Teilen beantworten:"
-
-#: i2p2www/pages/site/faq.html:199
-#, python-format
-msgid ""
-"Distribution - All traffic on I2P is encrypted in multiple layers."
-" You don't know\n"
-"a message's contents, source, or destination.\n"
-"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
-"Your only alternative is to refuse to route\n"
-"any traffic, by setting your share bandwidth or maximum "
-"participating tunnels to 0 (see above).\n"
-"It would be nice if you didn't do this, you should help the network by "
-"routing traffic for others.\n"
-"Over 95% of users route traffic for others."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:210
-msgid ""
-"Storage - I2P does not do distributed storage of content. You must"
-" be thinking of\n"
-"Freenet.\n"
-"Nobody's content is being stored on your computer by running I2P."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:217
-msgid ""
-"Access - If there are some eepsites you don't like, don't go "
-"there.\n"
-"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:227
-msgid ""
-"No. This is normal.\n"
-"All routers adjust dynamically to changing network conditions and demands."
-msgstr ""
-"Nein, das ist normal. Alle Router passen sich dynamisch an die sich "
-"veränderne Netzwerkbedingunen und Anforderungen an."
-
-#: i2p2www/pages/site/faq.html:234
-msgid ""
-"You may need to reseed your I2P router. With recent versions of I2P you "
-"can go to http://localhost:7657/configreseed"
-" and click the Save Changes and Reseed Now button. If this "
-"method doesn't work—or you're using a very old version—you "
-"may need to reseed manually."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:237
-msgid ""
-"The reseed URL changed a few years ago. If this is your first install and"
-" you have installed\n"
-"an old (0.6.1.30 or earlier) release, or\n"
-"you have not run I2P in a long time, you must change the URL and then\n"
-"click \"Reseed\" on the console to find other routers.\n"
-"After your router is running,\n"
-"on configadvanced.jsp,"
-"\n"
-"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
-"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
-"work),\n"
-"then click \"Apply\", then click the \"reseed\" link on the left."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:248
-#, python-format
-msgid ""
-"This works if you are running 0.6.1.27 or later.\n"
-"If you are running release 0.6.1.31 or later, you probably don't need to "
-"do this.\n"
-"If you are running release 0.6.1.26 or earlier, either follow the\n"
-"manual reseed instructions below\n"
-"or install the latest release.\n"
-"Possible alternate method - add\n"
-"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
-"to wrapper.config, shutdown the router completely, then start again, then"
-" click \"reseed\".\n"
-"Let us know if this works."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:259
-#, python-format
-msgid ""
-"...but you *really* should upgrade to "
-"the latest version."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:265
-msgid ""
-"If your router has 10 or more active peers, everything is fine. Changes "
-"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
-"efficiency of the router and effectively reduced the number of active "
-"peers.\n"
-"The router should maintain connections to a few peers at all "
-"times.\n"
-"The best way to stay \"better-connected\" to the network is to share more bandwidth."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:272
-msgid ""
-"Is my router an \"exit node\" to the regular Internet? I don't want it to"
-" be."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:274
-msgid ""
-"No. Unlike Tor,\n"
-"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
-"\n"
-"Only volunteers who set up and run separate applications will relay "
-"traffic to the regular Internet.\n"
-"There are very, very few of these."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:283
-msgid ""
-"See above. There are very few HTTP \"outproxies\", they are not an "
-"inherent part of the network,\n"
-"and they may not be up.\n"
-"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
-"vanished.\n"
-"The only outproxy at the moment is false.i2p.\n"
-"To use it, edit your i2ptunnel "
-"settings for eepProxy\n"
-"and set your outproxy list to 'false.i2p' (only).\n"
-"Then stop and restart the eepProxy.\n"
-"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
-"If your primary reason to use an anonymous network is to anonymously "
-"access sites\n"
-"on the regular Internet, you should probably try Tor."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:298
-msgid ""
-"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
-"to-end.\n"
-"FTP is not supported for technical reasons."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:302
-msgid ""
-"There are no FTP \"outproxies\" to the Internet—it may not even be "
-"possible to set up one.\n"
-"Any other kind of outproxy may work if it's set up with a standard "
-"tunnel. \n"
-"If you would like to set up some type of outproxy, carefully research the"
-" potential risks.\n"
-"The I2P community may or may not be able to help with the technical "
-"aspects, feel free to ask."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:308
-msgid ""
-"As explained several times above, any existing outproxy isn't a core part"
-" of the network.\n"
-"They are services run by individuals and they may or may not\n"
-"be operational at any given time."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:313
-msgid ""
-"Update: Thanks to the work of h2ik, there is an https outproxy "
-"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
-"configured out of the box.
            \n"
-"In case the https outproxy is not available in your version of I2P, you "
-"can add it easily by doing the following:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:319
-msgid ""
-"Open i2p tunnel "
-"manager. Scroll down to the bottom."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:324
-msgid ""
-"Choose CONNECT from New Client Tunnel dropdown list, click "
-"Create"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:329
-#, python-format
-msgid ""
-"In the new page, name and describe your new https tunnel as"
-" you like.\n"
-"The Access Point is your local port for the new https proxy "
-"recommended port's 4445.\n"
-"Outproxy should be the outproxy's .i2p address which supports "
-"https. \n"
-"See this forum post of h2ik's for the "
-"address. \n"
-"Make sure Shared Client, Delay Connect, AutoStart "
-"are checked.\n"
-"Other options should be left at the defaults. Click Save. In tunnel "
-"manger, click the Start button next to your new tunnel."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:339
-msgid ""
-"In firefox, click through "
-"Tools>Options>Advanced>Network>Setting."
-"\n"
-"Untick Use this proxy for all protocol, set SSL proxy: to "
-"localhost:4445."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:344
-msgid "Done."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:350
-#, python-format
-msgid ""
-"\n"
-"This is a question that only you can answer because the correct answer "
-"depends on your behaviours, your\n"
-"threat model, and how much you trust the "
-"outproxy operator."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:354
-msgid ""
-"Like Tor, I2P does not magically encrypt the Internet.\n"
-"You are vulnerable to snooping by the outproxy operators.\n"
-"The Tor"
-" FAQ\n"
-"does a good job of explaining this."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:360
-#, python-format
-msgid ""
-"In addition, you may be vulnerable to collusion between the outproxy "
-"operator\n"
-"and operators of other I2P services, if you use the same tunnels "
-"(\"shared clients\").\n"
-"There is additional discussion about this on %(zzz)s."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:368
-msgid ""
-"Unless an outproxy has been set up for the service you want to connect "
-"to, this cannot be done.\n"
-"There are only three types of outproxies running right now: HTTP, HTTPS, "
-"and email. Note that there is not a SOCKS outproxy.\n"
-"If this type of service is required, try Tor."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:376
-#, python-format
-msgid ""
-"If you consider every eepsite that has ever been created, yes, most of "
-"them are down.\n"
-"People and eepsites come and go.\n"
-"A good way to get started in I2P is check out a list of eepsites that are"
-" currently up.\n"
-"%(perv)s tracks active eepsites."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:385
-msgid ""
-"Click on the Website link\n"
-"at the top of your router console for instructions."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:392
-msgid ""
-"Why are downloads, torrents, web browsing, and everything else so slow on"
-" I2P?\n"
-"The encryption and routing within the I2P network adds a substantial "
-"amount of overhead and limits bandwidth.\n"
-"Anonymity isn't free."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:397
-msgid ""
-"In addition, you and everybody else probably need to increase your "
-"bandwidth limits.\n"
-"Two key settings are the inbound and outbound bandwidth limiters on\n"
-"the configuration page.\n"
-"With the default settings of 32KBps you will generally get no better than"
-" 15KBps data transfer in I2PSnark.\n"
-"Increasing the settings (but keeping within your actual connection "
-"limitations)\n"
-"will increase the potential transfer rate for I2PSnark and all other "
-"applications."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:405
-msgid ""
-"Also, do you have sufficient share bandwidth configured to allow "
-"participating tunnels\n"
-"to route through your router? Believe it or not, allowing participating "
-"traffic\n"
-"keeps you well-integrated in the network and helps your own transfer "
-"speeds."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:410
-#, python-format
-msgid ""
-"I2P is a work in progress. Lots of improvements and fixes are being "
-"implemented, and\n"
-"generally speaking, running the latest release will help your "
-"performance.\n"
-"If you haven't, install the latest "
-"release."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:418
-#, python-format
-msgid ""
-"See the\n"
-"I2P Bittorrent FAQ"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:425
-msgid ""
-"\n"
-"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
-" installed (see\n"
-"the I2PTunnel "
-"configuration page),\n"
-"and is automatically started when the I2P router starts. To connect to "
-"it, tell your IRC\n"
-"client to connect to localhost 6668. XChat-like client users"
-" can create a\n"
-"new network with the server localhost/6668 (remember to tick"
-" "Bypass\n"
-"proxy server" if you have a proxy server configured)."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:436
-msgid ""
-"For security purposes, the router's admin console by default only listens"
-"\n"
-"for connections on the local interface.  However, with a little hacking,\n"
-"you can make it reachable remotely:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:444
-msgid ""
-"Open ~/.i2p/clients.config and replace
            \n"
-"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
-"with 
            \n"
-"clientApp.0.args=7657 0.0.0.0 ./webapps/"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:452
-msgid ""
-"Go to http://localhost:7657/configadvanced.jsp"
-"\n"
-"and add a new option: consolePassword=foo (or whatever "
-"password you want)"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:458
-msgid ""
-"Go to http://localhost:7657/index.jsp"
-"\n"
-"and hit \"Graceful restart\", which restarts the JVM and reloads the "
-"client applications"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:465
-msgid ""
-"After that fires up, you should now be able to reach your console "
-"remotely.\n"
-"You will be prompted for a username and password though - the username is"
-"\n"
-"\"admin\" and the password is whatever you specified in step 2 above.  "
-"Note: the\n"
-"0.0.0.0 above specifies an interface, not a network "
-"or netmask.  0.0.0.0\n"
-"means \"bind to all interfaces\", so it can be reachable on "
-"127.0.0.1:7657 as well as\n"
-"any LAN/WAN IP."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:476
-msgid ""
-"By default, the router I2CP interface (port 7654) binds to address "
-"127.0.0.1. To bind to 0.0.0.0, set the\n"
-"router advanced configuration option "
-"i2cp.tcp.bindAllInterfaces=true and restart."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:481
-msgid "Whats an \"eepsite\"?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:483
-msgid ""
-"An eepsite is a website that is hosted anonymously - you can access it by"
-"\n"
-"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
-"listens on localhost port 4444), and browsing to the site."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:491
-#, python-format
-msgid ""
-"The proxy config for different browsers is on a \n"
-"separate page with screenshots. More advanced configs with external "
-"tools\n"
-"are possible but could introduce leaks in your setup."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:500
-msgid ""
-"x is the number of peers you've sent or received a message from\n"
-"successfully in the last minute, y is the number of peers seen in the "
-"last\n"
-"hour or so."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:508
-msgid ""
-"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
-"supported.\n"
-"There is no SOCKS outproxy so it is of limited use."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:512
-msgid ""
-"In addition, many applications leak sensitive\n"
-"information that could identify you on the Internet. I2P only filters\n"
-"connection data, but if the program you intend to run sends this\n"
-"information as content, I2P has no way to protect your anonymity.  For\n"
-"example, some mail applications will send the IP address of the machine\n"
-"they are running on to a mail server. There is no way for I2P to filter\n"
-"this, thus using I2P to 'socksify' existing applications is possible, but"
-"\n"
-"extremely dangerous."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:522
-#, python-format
-msgid ""
-"If you would like more information on the socks proxy application anyway,"
-"\n"
-"there are some helpful hints on the socks page."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:529
-msgid ""
-"Okay, here's a rundown of the default ports (everything is configurable\n"
-"through various settings, of course):"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:538
-msgid ""
-"Internet-facing ports\n"
-"Note: New installs as of release 0.7.8 do not use port 8887; they select "
-"a random port\n"
-"between 9000 and 31000 when the program is run for the first time.\n"
-"The selected port is shown on the router configuration page."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:546
-msgid ""
-"Outbound UDP from the random port noted on the configuration page to "
-"arbitrary remote UDP ports, allowing replies\n"
-"    "
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:551
-msgid ""
-"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
-"    "
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:556
-msgid ""
-"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
-"arbitrary locations\n"
-"    "
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:561
-msgid ""
-"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
-"arbitrary locations
            \n"
-"Inbound TCP may be disabled on the configuration page."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:567
-msgid ""
-"Outbound UDP on port 123, allowing replies
            \n"
-"This is necessary for I2P's internal time sync (via SNTP - \n"
-"querying a random SNTP host in pool.ntp.org or another\n"
-"server you specify)"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:578
-msgid ""
-"Local I2P ports, listening only to local connections by default,\n"
-"except where noted:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:584
-msgid ""
-"1900: UPnP SSDP UDP multicast listener.\n"
-"Cannot be changed. Binds to all interfaces.\n"
-"May be disabled on confignet.jsp."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:591
-msgid ""
-"2827: BOB bridge, a higher level socket API for clients\n"
-"Disabled by default.\n"
-"May be enabled/disabled on configclients.jsp.\n"
-"May be changed in the bob.config file."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:599
-msgid ""
-"4444: HTTP proxy\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:606
-msgid ""
-"4445: HTTPS proxy\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:613
-msgid ""
-"6668: IRC proxy\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:620
-msgid ""
-"7652: UPnP HTTP TCP event listener.\n"
-"Binds to the LAN address.\n"
-"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
-"May be disabled on confignet.jsp."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:628
-msgid ""
-"7653: UPnP SSDP UDP search response listener.\n"
-"Binds to all interfaces.\n"
-"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
-"May be disabled on confignet.jsp."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:636
-msgid ""
-"7654: I2P Client Protocol port, used by client apps.\n"
-"May be changed to a different port on\n"
-"configclients.jsp"
-"\n"
-"but this is not recommended.\n"
-"May be to bind to a different interface or all interfaces, or disabled, "
-"on\n"
-"configclients.jsp."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:646
-msgid ""
-"7655: UDP for SAM bridge, a higher level socket API for clients\n"
-"Only opened when a SAM V3 client requests a UDP session.\n"
-"May be enabled/disabled on configclients.jsp.\n"
-"May be changed in the clients.config file with the SAM command line "
-"option sam.udp.port=nnnn."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:654
-msgid ""
-"7656: SAM bridge, a higher level socket API for clients\n"
-"Disabled by default for new installs as of release 0.6.5.\n"
-"May be enabled/disabled on configclients.jsp.\n"
-"May be changed in the clients.config file."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:662
-msgid ""
-"7657: Your router console\n"
-"May be disabled in the clients.config file.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces in that file."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:669
-msgid ""
-"7658: Your eepsite\n"
-"May be disabled in the clients.config file.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces in the jetty.xml file."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:676
-msgid ""
-"7659: Outgoing mail to smtp.postman.i2p\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:683
-msgid ""
-"7660: Incoming mail from pop.postman.i2p\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:690
-msgid ""
-"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:697
-msgid ""
-"31000: Local connection to the wrapper control channel port.\n"
-"Outbound to 32000 only, does not listen on this port.\n"
-"Starts at 31000 and will increment until 31999 looking for a free port.\n"
-"To change, see the\n"
-"wrapper documentation.\n"
-"For more information see below."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:707
-msgid ""
-"32000: Local control channel for the service wrapper.\n"
-"To change, see the\n"
-"wrapper documentation.\n"
-"For more information see below."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:719
-msgid ""
-"The local I2P ports and the I2PTunnel ports do not need to be reachable "
-"from \n"
-"remote machines, but *should* be reachable locally.  You can also create"
-" \n"
-"additional ports for I2PTunnel instances via "
-"http://localhost:7657/i2ptunnel/ \n"
-"(and in turn, would need to get your firewall to allow you local access, "
-"but \n"
-"not remote access, unless desired)."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:727
-msgid ""
-"So, to summarize, nothing needs to be reachable by unsolicited remote "
-"peers, but\n"
-"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
-"outbound facing port, you'll"
-"\n"
-"get better performance.  You will also need to be able to send outbound "
-"UDP packets\n"
-"to arbitrary remote peers (blocking IPs randomly with something like "
-"PeerGuardian\n"
-"only hurts you - don't do it)."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:735
-msgid "Why is I2P listening on port 32000?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:737
-msgid ""
-"The Tanuki java service wrapper that we use opens this port—bound "
-"to localhost—in order \n"
-"to communicate with software running inside the JVM. When the JVM is "
-"launched it is given a key \n"
-"so it can connect to the wrapper. After the JVM establishes its "
-"connection \n"
-"to the wrapper, the wrapper refuses any additional connections."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:743
-msgid ""
-"More information can be found in the  \n"
-"wrapper documentation."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:750
-msgid ""
-"An I2P router only needs to be seeded once, to join the network for the "
-"first time.\n"
-"Reseeding is nothing more than sending plain HTTP GET requests\n"
-"to fetch a directory listing and download multiple \"routerInfo\" files\n"
-"from a predefined reseed URL."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:757
-msgid ""
-"A typical symptom of a failed reseed is the \"Known\" indicator\n"
-"(on the left sidebar of the router console) displaying a very small value"
-"\n"
-"(often less than 5) which does not increase. This can occur, among other "
-"things,\n"
-"if your firewall limits outbound traffic, and blocked the reseed request."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:764
-msgid "To reseed an I2P router manually, do the following:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:767
-msgid "Stop your I2P router"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:770
-msgid ""
-"Open http://netdb.i2p2.de/ using a "
-"web browser"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:773
-msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:780
-msgid "Start your I2P router"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:787
-msgid ""
-"When trying to start the router using \"i2prouter start\", you may see "
-"output like the following:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:792
-msgid ""
-"\n"
-"In order to be inclusive and try to ensure that I2P will run on as many "
-"systems \n"
-"as possible, up until I2P 0.8.9 we used a java wrapper \n"
-"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
-"are missing the necessary compatibility libraries.\n"
-"These libraries may be installed by performing the following steps:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:800
-msgid ""
-"Switch to the root user with su or log in as "
-"root."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:806
-#, python-format
-msgid ""
-"If you cannot install these compatibility libraries (or do not want to), "
-"other\n"
-"possibilities would be to compile the wrapper for your\n"
-"system, starting I2P with the runplain.sh script, or you"
-" can\n"
-"replace the wrapper with one from the source tarball."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:812
-msgid ""
-"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
-"compiled on systems running FreeBSD 7.2."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:816
-msgid ""
-"In wrapper.log I see an error that states \"Protocol "
-"family unavailable\" when loading the Router Console"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:818
-msgid ""
-"Often this error will occur with any network enabled java software on "
-"some systems that are configured to use IPv6 by default. There are a few "
-"ways to solve this:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:823
-msgid ""
-"On Linux based systems, you can echo 0 > "
-"/proc/sys/net/ipv6/bindv6only"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:825
-msgid "Look for the following lines in wrapper.config."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:829
-msgid ""
-"If the lines are there, uncomment them by removing the \"#\"s. If the "
-"lines are not there, add them without the \"#\"s."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:832
-msgid ""
-"Another option would be to remove the ::1 from "
-"~/.i2p/clients.config"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:836
-msgid ""
-"WARNING: For any changes to wrapper.config "
-"to take effect, you must completely\n"
-"stop the router and the wrapper. Clicking Restart on your\n"
-"router console will NOT reread this file! You must\n"
-"click Shutdown, wait 11 minutes, then start I2P."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:847
-#, python-format
-msgid ""
-"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
-"the forum and we'll post it here (with\n"
-"the answer, hopefully)."
-msgstr ""
-"Bestens! Du findest uns im IRC auf irc.freenode.net im Kanal #i2p oder "
-"frage im Forum und wir werden das hier "
-"anfügen (mit der Antwort, hoffentlich)."
-
-#: i2p2www/pages/site/impressum.html:4
-msgid "German laws"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:2
-msgid "I2P Anonymous Network"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:4
-msgid ""
-"Anonymous peer-to-peer distributed communication layer built with open "
-"source tools and designed to run any traditional Internet service such as"
-" email, IRC or web hosting."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:7
-msgid "What does I2P do for you?"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:8
-msgid ""
-"The I2P network provides strong privacy protections for communication "
-"over the Internet. Many activities that would risk your privacy on the "
-"public Internet can be conducted anonymously inside I2P."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:9
-#, python-format
-msgid "Get I2P %(version)s"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:13
-msgid "What is I2P?"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:15
-msgid ""
-"I2P is a full darknet implementation - a network within a network, and is"
-" intended to protect against monitoring by third parties, such as hostile"
-" governments or ISPs.\n"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:18
-msgid ""
-"I2P is used by many people who care about their privacy, as well as those"
-" in high-risk situations. It is designed to protect activists, oppressed "
-"people, journalists and whistle-blowers - as well as the average person."
-"\n"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:21
-msgid ""
-"I2P runs on Java and is therefore available anywhere Java will run, "
-"including desktops, embedded systems (like the Raspberry Pi)  and Android"
-" phones.\n"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:25
-msgid "Read more…"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:30
-msgid "What can you do with I2P?"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:33
-#, python-format
-msgid ""
-"Email Integrated web mail interface, "
-"plugin for serverless email."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:38
-#, python-format
-msgid ""
-"Web browsing Anonymous "
-"websites, gateways to and from the public Internet."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:43
-#, python-format
-msgid ""
-"Blogging and forums "
-"Blogging and Syndie plugins."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:48
-#, python-format
-msgid ""
-"Website hosting Integrated "
-"anonymous web server."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:53
-#, python-format
-msgid ""
-"Real-time chat Instant "
-"messaging and IRC clients."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:58
-#, python-format
-msgid ""
-"File sharing ED2K and Gnutella"
-" clients, integrated BitTorrent client."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:63
-#, python-format
-msgid ""
-"Decentralized file "
-"storage Tahoe-LAFS distributed filesystem plugin."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:68
-#, python-format
-msgid "More supported applications…"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:76
-msgid "News & Updates"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:4
-msgid "Recommended Links & Resources"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:5
-#, python-format
-msgid ""
-"See also the page with\n"
-"links to presentations, videos, and tutorials about"
-" I2P."
-msgstr ""
-
-#: i2p2www/pages/site/links.html:12
-msgid "Friends of I2P"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:24
-msgid "More Projects and Documentation"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:34
-msgid "Press"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:38
-msgid "Boards, newssite, others"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:42
-msgid "Very Old Stuff"
-msgstr ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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
-msgid ""
-"By default, I2P comes with two outproxies configured: "
-"false.i2p\n"
-"(an HTTP-only proxy) and outproxyng.h2ik.i2p (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
-#, python-format
-msgid ""
-"Filtering is active on these outproxies (for example, mibbit and torrent\n"
-"tracker access is blocked). Note that even though the pirate bay is "
-"blocked\n"
-"they host an official eepsite at %(tpb)s. "
-"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:101
-msgid ""
-"Tor is good application to use"
-" as an\n"
-"outproxy to the Internet."
-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:137
-#: i2p2www/pages/site/about/hall-of-fame.html:138
-#: i2p2www/pages/site/about/hall-of-fame.html:139
-#: i2p2www/pages/site/about/hall-of-fame.html:140
-#: i2p2www/pages/site/about/hall-of-fame.html:142
-#: i2p2www/pages/site/about/hall-of-fame.html:143
-#: i2p2www/pages/site/about/hall-of-fame.html:144
-#: i2p2www/pages/site/about/hall-of-fame.html:147
-#: i2p2www/pages/site/about/hall-of-fame.html:148
-#: i2p2www/pages/site/about/hall-of-fame.html:149
-#: i2p2www/pages/site/about/hall-of-fame.html:152
-#: i2p2www/pages/site/about/hall-of-fame.html:153
-#: i2p2www/pages/site/about/hall-of-fame.html:154
-#: i2p2www/pages/site/about/hall-of-fame.html:155
-#: i2p2www/pages/site/about/hall-of-fame.html:156
-#: i2p2www/pages/site/about/hall-of-fame.html:157
-#: i2p2www/pages/site/about/hall-of-fame.html:158
-#: i2p2www/pages/site/about/hall-of-fame.html:159
-#: i2p2www/pages/site/about/hall-of-fame.html:160
-#: i2p2www/pages/site/about/hall-of-fame.html:161
-#: i2p2www/pages/site/about/hall-of-fame.html:162
-#: i2p2www/pages/site/about/hall-of-fame.html:163
-#: i2p2www/pages/site/about/hall-of-fame.html:164
-#: i2p2www/pages/site/about/hall-of-fame.html:167
-#: i2p2www/pages/site/about/hall-of-fame.html:168
-#: i2p2www/pages/site/about/hall-of-fame.html:169
-#: i2p2www/pages/site/about/hall-of-fame.html:170
-#: i2p2www/pages/site/about/hall-of-fame.html:171
-#: i2p2www/pages/site/about/hall-of-fame.html:172
-#: 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: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:181
-#: i2p2www/pages/site/about/hall-of-fame.html:182
-#: 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:186
-#: i2p2www/pages/site/about/hall-of-fame.html:187
-#: 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: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: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:208
-#: i2p2www/pages/site/about/hall-of-fame.html:209
-#: i2p2www/pages/site/about/hall-of-fame.html:210
-#: i2p2www/pages/site/about/hall-of-fame.html:212
-#: i2p2www/pages/site/about/hall-of-fame.html:213
-#: 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:217
-#: i2p2www/pages/site/about/hall-of-fame.html:218
-#: i2p2www/pages/site/about/hall-of-fame.html:219
-#: 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:227
-#: i2p2www/pages/site/about/hall-of-fame.html:230
-#: i2p2www/pages/site/about/hall-of-fame.html:231
-#: 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:236
-#: i2p2www/pages/site/about/hall-of-fame.html:237
-#: i2p2www/pages/site/about/hall-of-fame.html:238
-#: i2p2www/pages/site/about/hall-of-fame.html:243
-#: 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:247
-#: 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:252
-#: 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:265
-#: 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:271
-#: 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:275
-#: i2p2www/pages/site/about/hall-of-fame.html:276
-#: i2p2www/pages/site/about/hall-of-fame.html:277
-#: i2p2www/pages/site/about/hall-of-fame.html:278
-#: 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:289
-#: 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:292
-#: i2p2www/pages/site/about/hall-of-fame.html:293
-#: i2p2www/pages/site/about/hall-of-fame.html:294
-#: i2p2www/pages/site/about/hall-of-fame.html:295
-#: i2p2www/pages/site/about/hall-of-fame.html:297
-#: i2p2www/pages/site/about/hall-of-fame.html:298
-#: i2p2www/pages/site/about/hall-of-fame.html:299
-#: i2p2www/pages/site/about/hall-of-fame.html:300
-#: 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: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:314
-#: 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:322
-#: i2p2www/pages/site/about/hall-of-fame.html:324
-#: 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:332
-#: 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: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:348
-#: i2p2www/pages/site/about/hall-of-fame.html:349
-#: i2p2www/pages/site/about/hall-of-fame.html:351
-#: i2p2www/pages/site/about/hall-of-fame.html:352
-#: 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:374
-#: 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:378
-#: i2p2www/pages/site/about/hall-of-fame.html:379
-#: 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:382
-#: i2p2www/pages/site/about/hall-of-fame.html:383
-#: 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:386
-#: 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:389
-#: i2p2www/pages/site/about/hall-of-fame.html:390
-#: i2p2www/pages/site/about/hall-of-fame.html:391
-#: i2p2www/pages/site/about/hall-of-fame.html:392
-#: i2p2www/pages/site/about/hall-of-fame.html:393
-#: i2p2www/pages/site/about/hall-of-fame.html:394
-#: i2p2www/pages/site/about/hall-of-fame.html:395
-#: i2p2www/pages/site/about/hall-of-fame.html:396
-#: i2p2www/pages/site/about/hall-of-fame.html:397
-#: i2p2www/pages/site/about/hall-of-fame.html:398
-#: i2p2www/pages/site/about/hall-of-fame.html:399
-#: 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: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: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:420
-#: 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:436
-#: 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:442
-#: i2p2www/pages/site/about/hall-of-fame.html:445
-#: 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:449
-#: 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:455
-#: i2p2www/pages/site/about/hall-of-fame.html:456
-#: i2p2www/pages/site/about/hall-of-fame.html:457
-#: i2p2www/pages/site/about/hall-of-fame.html:458
-#: 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:465
-#: i2p2www/pages/site/about/hall-of-fame.html:466
-#: i2p2www/pages/site/about/hall-of-fame.html:467
-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
-#, 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
-#: i2p2www/pages/site/get-involved/bounties/index.html:67
-msgid "Bitcoin client for I2P"
-msgstr ""
-
-#: i2p2www/pages/site/about/hall-of-fame.html:20
-#, python-format
-msgid "%(btcval)s BTC"
-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:134
-msgid "2012 donations and costs:"
-msgstr ""
-
-#: i2p2www/pages/site/about/hall-of-fame.html:262
-msgid "2011 donations and costs:"
-msgstr ""
-
-#: i2p2www/pages/site/about/hall-of-fame.html:363
-msgid "Previous to 2011 donations:"
-msgstr ""
-
-#: i2p2www/pages/site/about/intro.html:2
-msgid "Intro"
-msgstr ""
-
-#: i2p2www/pages/site/about/intro.html:5
-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 \n"
-"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:19
-#, 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:33
-#, 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:44
-#, python-format
-msgid "More details about how I2P works are available."
-msgstr ""
-
-#: i2p2www/pages/site/about/intro.html:48
-msgid "What can you do with it?"
-msgstr ""
-
-#: i2p2www/pages/site/about/intro.html:50
-#, 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:60
-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:76
-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:90
-#, 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
-#: i2p2www/pages/site/research/papers.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\n"
-"Russian translation"
-msgstr ""
-
-#: i2p2www/pages/site/about/media.html:204
-#, python-format
-msgid ""
-"zzz interviewed on the InfoSec Daily Podcast Ep. 454 "
-"(mp3)\n"
-"August 18, 2011"
-msgstr ""
-
-#: i2p2www/pages/site/about/media.html:209
-#, python-format
-msgid ""
-"I2P - Anonymity for the Masses,\n"
-"Jonathan Cox,\n"
-"November 11, 2011."
-msgstr ""
-
-#: i2p2www/pages/site/about/media.html:215
-#, 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: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:76
-#: i2p2www/pages/site/about/team.html:81 i2p2www/pages/site/about/team.html:101
-#: i2p2www/pages/site/about/team.html:138
-#: i2p2www/pages/site/about/team.html:148
-#: i2p2www/pages/site/about/team.html:153
-#: 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:206
-#: i2p2www/pages/site/about/team.html:228
-#: i2p2www/pages/site/get-involved/bounties/index.html:35
-#: i2p2www/pages/site/get-involved/bounties/index.html:42
-#: i2p2www/pages/site/get-involved/bounties/index.html:49
-#: i2p2www/pages/site/get-involved/bounties/index.html:56
-#: i2p2www/pages/site/get-involved/bounties/index.html:63
-#: i2p2www/pages/site/get-involved/bounties/index.html:84
-#: i2p2www/pages/site/get-involved/bounties/index.html:104
-msgid "vacant"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:72
-msgid "threat model / crypto expert"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:75
-msgid "User Advocate"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:77
-msgid "gather, prioritize, advocate for user needs"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:80
-msgid "Web Designer"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:82
-msgid "manage the public project website content design"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:85
-#, python-format
-msgid "Webserver admin"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:87
-msgid "manage the public project webservers"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:90
-#, python-format
-msgid "Website admin"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:92
-msgid "manage the public project website content"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:95
-msgid "News Admin"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:97
-msgid "manage router console news feed"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:100
-msgid "Director of passion"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:102
-msgid "community motivator"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:106
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-msgid "Dev"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:107
-msgid "Core Lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:109
-msgid "lead dev for the SDK and router"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:112
-#, python-format
-msgid "I2P mail lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:114
-msgid "organize and develop the i2p mail system"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:117
-#, python-format
-msgid "I2Host lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:119
-msgid "I2Host addressbook application"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:122
-#, python-format
-msgid "BOB lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:124
-msgid "Basic Open Bridge"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:127
-#, python-format
-msgid "I2P-Bote lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:129
-msgid "I2PBote plugin"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:132
-#, python-format
-msgid "Robert lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:134
-msgid "Robert BitTorrent client"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:137
-#, python-format
-msgid "I2Phex lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:139
-msgid "I2Phex Gnutella client"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:142
-#, python-format
-msgid "I2PSnark lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:144
-msgid "Maintains the integrated Bittorrent client"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:147
-#, python-format
-msgid "iMule lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:149
-msgid "eMule client over I2P"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:152
-#, python-format
-msgid "Syndie lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:154
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3
-msgid "Syndie development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:157
-msgid "Susimail lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:159
-msgid "Susimail development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:162
-msgid "Console"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:164
-msgid "Router console HTML/CSS design"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:167
-msgid "SAM"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:169
-msgid "SAM maintainer"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:172
-msgid "I2PCPP lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:174
-msgid "C++ Router"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:177
-msgid "Console Translations"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:179
-msgid "Chinese"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:183
-msgid "Dutch"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:187
-msgid "French"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:191
-msgid "German"
-msgstr "Deutsch"
-
-#: i2p2www/pages/site/about/team.html:195
-msgid "Russian"
-msgstr "Russisch"
-
-#: i2p2www/pages/site/about/team.html:199
-msgid "Spanish"
-msgstr "Spanisch"
-
-#: i2p2www/pages/site/about/team.html:203
-msgid "Arabic"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:207
-msgid "Other languages"
-msgstr "Andere Sprachen"
-
-#: i2p2www/pages/site/about/team.html:210
-msgid "Contributors"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:212
-msgid "fire2pe dev, console enhancements"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:216
-msgid "desktopgui, dijjer port"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:220
-msgid "Debian/Ubuntu Packager and PPA maintainer"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:224
-msgid "Routerconsole backend and UI work, website revamp, unit tests work"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:229
-msgid "Help needed on many fronts!"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:233
-msgid "Past contributors"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:235
-msgid "I2PTunnel development, ministreaming library"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:239
-msgid "Project lead, Syndie lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:243
-msgid "Project lead, Syndie lead, I2Phex, support guru"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:247
-msgid "iMule lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:251
-#: i2p2www/pages/site/about/team.html:255
-#: i2p2www/pages/site/about/team.html:259
-msgid "I2Phex work"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:263
-msgid "Python SAM library, attack simulations"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:267
-msgid "i2pmail development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:271
-msgid "Syndie help"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:275
-msgid "i2p mail,susimail and susidns apps"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:279
-msgid "I2Phex (port of Phex to I2P)"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:283
-msgid "addressbook,i2p-bt,syndie client"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:287
-msgid "organize and develop the i2p-bt BitTorrent port"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:291
-msgid "addressbook, i2p-bt, syndie client development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:295
-msgid "encryption and signature routines, I2PIM"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:299
-msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:303
-msgid "installer, systray, bogobot"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:307
-msgid "jbigi development, wiki migration, doc cleanup"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:311
-msgid "java debugging and client development on I2PTunnel and the router console"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:315
-msgid "SAM perl module"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:319
-msgid "i2psnark work"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:323
-msgid "java cleanup"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:327
-msgid "docs. wiki migration"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:331
-msgid "translations into French"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:335
-msgid "C port of jcpuid"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:339
-msgid "C# SAM library, pants, fortuna integration"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:343
-msgid "libSAM"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:347
-#: i2p2www/pages/site/about/team.html:351
-msgid "i2p-bt tracker development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:355
-msgid "Console and website themes"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:358
-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
-#: i2p2www/pages/site/docs/api/bob.html:3
-#: i2p2www/pages/site/docs/api/datagrams.html:3
-#: i2p2www/pages/site/docs/how/garlic-routing.html:3
-#: i2p2www/pages/site/docs/protocol/index.html:3
-#: i2p2www/pages/site/docs/transport/ntcp.html:3
-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
-#, python-format
-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
-#, python-format
-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 shitlist) 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: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 ""
-
-#: i2p2www/pages/site/comparison/freenet.html:2
-msgid "I2P Compared to Freenet"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/freenet.html:8
-msgid ""
-"Freenet is a fully distributed, peer to peer anonymous publishing "
-"network, offering \n"
-"secure ways to store data, as well as some approaches attempting to "
-"address the loads\n"
-"of a flash flood.  While Freenet is designed as a distributed data store,"
-" people have\n"
-"built applications on top of it to do more generic anonymous "
-"communication, such as \n"
-"static websites and message boards."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/freenet.html:16
-#, python-format
-msgid ""
-"Compared to I2P, Freenet offers some substantial benefits - it is a "
-"distributed data\n"
-"store, while I2P is not, allowing people to retrieve the content "
-"published by others \n"
-"even when the publisher is no longer online.  In addition, it should be "
-"able to \n"
-"distribute popular data fairly efficiently.  I2P itself does not and will"
-" not provide \n"
-"this functionality.  On the other hand, there is overlap for users who "
-"simply want to \n"
-"communicate with each other anonymously through websites, message boards,"
-" file sharing\n"
-"programs, etc.  There have also been some attempts to develop a "
-"distributed data \n"
-"store to run on top of I2P,\n"
-"(most recently a port of Tahoe-LAFS)\n"
-"but nothing is yet ready for general use."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/freenet.html:29
-msgid ""
-"However, even ignoring any implementations issues, there are some "
-"concerns \n"
-"about Freenet's algorithms from both a scalability and anonymity "
-"perspective, owing \n"
-"largely to Freenet's heuristic driven routing.  The interactions of "
-"various techniques \n"
-"certainly may successfully deter various attacks, and perhaps some "
-"aspects of the \n"
-"routing algorithms will provide the hoped for scalability.  "
-"Unfortunately, not much\n"
-"analysis of the algorithms involved has resulted in positive results, but"
-" there is still\n"
-"hope.  At the very least, Freenet does provide substantial anonymity "
-"against an attacker\n"
-"who does not have the resources necessary to analyze it further."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:2
-msgid "Comparing I2P to other projects"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:4
-msgid ""
-"There are a great many other applications and projects working on "
-"anonymous \n"
-"communication and I2P has been inspired by much of their efforts.  This "
-"is not \n"
-"a comprehensive list of anonymity resources - both freehaven's \n"
-"Anonymity "
-"Bibliography\n"
-"and GNUnet's related "
-"projects\n"
-"serve that purpose well.  That said, a few systems stand out for further\n"
-"comparison. The following have individual comparison pages:"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:20
-#, python-format
-msgid ""
-"The following are discussed on the other "
-"networks page:"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:32
-#, python-format
-msgid ""
-"The content of this page is subject to update, discussion and dispute, "
-"and we welcome comments and additions.\n"
-"You may contribute an analysis by entering a new ticket on Trac."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:2
-msgid "I2P Compared to Other Anonymous Networks"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:5
-msgid "The following networks are discussed on this page."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:16
-#, python-format
-msgid ""
-"Most of the following sections are fairly old, and may not be accurate.\n"
-"For an overview of available comparisons, see the\n"
-"main network comparisons page.\n"
-"You may contribute an analysis by entering a\n"
-"new ticket on %(trac)s."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:29
-#, python-format
-msgid ""
-"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
-" \n"
-"anonymizing proxies, allowing people to tunnel out through the low "
-"latency \n"
-"mix network.  Morphmix includes some very interesting collusion detection"
-" \n"
-"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
-"IP\n"
-"addresses to accomplish the same.  The two primary differences between \n"
-"these systems and I2P are related to I2P's threat model \n"
-"and their out-proxy design (as opposed to providing both sender and "
-"receiver \n"
-"anonymity).  There is source code available to both systems, but we are "
-"not aware \n"
-"of their use outside of academic environments."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:153
-msgid ""
-"\n"
-"Mixminion and Mixmaster are networks to support anonymous email against a"
-" very\n"
-"powerful adversary.\n"
-"High-latency messaging applications running on top of I2P\n"
-"(for example\n"
-"Syndie or\n"
-"I2PBote)\n"
-"may perhaps prove adequate to meet the threat\n"
-"model of those adversaries, while running in parallel along side the "
-"needs of low latency users, to provide\n"
-"a significantly larger anonymity set.\n"
-"High-latency support within the I2P router itself may or may not be added"
-" in a distant future release.\n"
-"It is too early to say if I2P will meet the needs of users requiring "
-"extreme protection for email."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:167
-msgid ""
-"As with Tor and Onion Routing, \n"
-"both Mixminion and Mixmaster take the directory based approach as well."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:177
-#, python-format
-msgid ""
-"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
-"web requests,\n"
-"and as such it has a few centralized nodes (participants in the cascade) "
-"that blend\n"
-"and mix requests from clients through the sequence of nodes (the cascade)"
-" before \n"
-"proxying out onto the web.  The scope, threat model, and security is "
-"substantially \n"
-"different from I2P, but for those who don't require significant anonymity"
-" but still\n"
-"are not satisfied with an Anonymizer-like service, JAP is worth "
-"reviewing.  One\n"
-"caution to note is that anyone under the jurisdiction of the German "
-"courts may want\n"
-"to take care, as the German Federal Bureau of Criminal Investigation "
-"(FBCI) has \n"
-"successfully mounted an \n"
-"attack \n"
-"on the network.  Even though the method of this attack was later found to"
-" be illegal \n"
-"in the German courts, the fact that the data was successfully collected "
-"is the \n"
-"concern.  Courts change their minds based upon circumstance, and this is "
-"evidence that \n"
-"if a government body or intelligence agency wanted to, they could gather "
-"the data, even \n"
-"if it may be found inadmissible in some courts later)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:199
-#, python-format
-msgid ""
-"Both of these systems work through the same basic \n"
-"antnet routing, providing some degree of\n"
-"anonymity based on the threat model of providing plausible deniability "
-"against a simple \n"
-"non-colluding adversary.  With the antnet routing, they first either do a"
-" random walk or a \n"
-"broadcast search to find some peer with the data or identity desired, and"
-" then use a feedback\n"
-"algorithm to optimize that found path.  This works well for applications "
-"that merely want to know \n"
-"what other people around them have to offer - \"How are y'all doing\" vs."
-" \"Hey Alice, how are you\" - \n"
-"you basically get a local cluster of nodes that can share files with and "
-"maintain some degree of \n"
-"anonymity (though you don't have much control over who is in that group "
-"of peers)."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:211
-msgid ""
-"However, the algorithm does not scale well at all - if the application "
-"wants to speak with a \n"
-"particular peer it ends up doing a broadcast search or random walk "
-"(though if they are lucky enough\n"
-"for that to succeed, the antnet routing should optimize that found "
-"connection).  This means that \n"
-"while these networks can work great at small scales, they are not "
-"suitable for large networks where\n"
-"someone wants to get in touch with another specific peer.  That does not "
-"mean that there is no \n"
-"value in these systems, just that their applicability is limited to "
-"situations where their \n"
-"particular issues can be addressed."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:222
-#, python-format
-msgid ""
-"This was a closed-source network targeted at Iranian users.\n"
-"Tor did a\n"
-"good writeup on what to look for in a circumvention tool.\n"
-"Suffice it to say that being closed source and publicly targeting a "
-"specific country are not good ideas.\n"
-"I2P is, of course, open source. However, that source, and our\n"
-"technical documentation, need much more review."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:231
-msgid "Paid VPN Services"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:232
-#: i2p2www/pages/site/comparison/other-networks.html:238
-#, python-format
-msgid ""
-"You may contribute an analysis by entering a\n"
-"new ticket on %(trac)s."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:237
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
-msgid "Others"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:2
-msgid "I2P Compared to Tor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:8
-#, python-format
-msgid ""
-"Tor and Onion Routing are both anonymizing proxy networks, \n"
-"allowing people to tunnel out through their low latency mix \n"
-"network. The two primary differences between Tor / \n"
-"Onion-Routing and I2P are again related to differences in \n"
-"the threat model and the out-proxy design (though Tor\n"
-"supports hidden services as well).  In addition, Tor\n"
-"takes the directory-based approach - providing a \n"
-"centralized point to manage the overall 'view' of the \n"
-"network, as well as gather and report statistics, as \n"
-"opposed to I2P's distributed network \n"
-"database and peer selection."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:22
-msgid ""
-"The I2P/Tor outproxy functionality does have a few \n"
-"substantial weaknesses against certain attackers - \n"
-"once the communication leaves the mixnet, global passive\n"
-"adversaries can more easily mount traffic analysis.  In \n"
-"addition, the outproxies have access to the cleartext \n"
-"of the data transferred in both directions, and \n"
-"outproxies are prone to abuse, along with all of the \n"
-"other security issues we've come to know and love with \n"
-"normal Internet traffic."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:34
-msgid ""
-"However, many people don't need to worry about those \n"
-"situations, as they are outside their threat model.  It\n"
-"is, also, outside I2P's (formal) functional scope (if people want\n"
-"to build outproxy functionality on top of an anonymous\n"
-"communication layer, they can).  In fact, some I2P users\n"
-"currently take advantage of Tor to outproxy."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:48
-msgid "Comparison of Tor and I2P Terminology"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:49
-msgid ""
-"While Tor and I2P are similar in many ways, much of the terminology is "
-"different."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:54
-msgid "Cell"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:54
-#: i2p2www/pages/site/docs/protocol/i2np.html:91
-msgid "Message"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:55
-msgid "Client"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:55
-msgid "Router or Client"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:56
-msgid "Circuit"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:56
-msgid "Tunnel"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:57
-msgid "Directory"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:57
-msgid "NetDb"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:58
-msgid "Directory Server"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:58
-msgid "Floodfill Router"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:59
-msgid "Entry Guards"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:59
-msgid "Fast Peers"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:60
-msgid "Entry Node"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:60
-msgid "Inproxy"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:61
-msgid "Exit Node"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:61
-msgid "Outproxy"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:62
-msgid "Hidden Service"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:62
-msgid "Eepsite or Destination"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:63
-msgid "Hidden Service Descriptor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:63
-msgid "LeaseSet"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:64
-msgid "Introduction point"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:64
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
-#: i2p2www/pages/site/docs/tunnels/implementation.html:140
-msgid "Inbound Gateway"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:65
-msgid "Node"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:65
-#: i2p2www/pages/site/comparison/tor.html:67
-#: i2p2www/pages/site/comparison/tor.html:70
-#: i2p2www/pages/site/docs/spec/configuration.html:70
-msgid "Router"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:66
-msgid "Onion Proxy"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:66
-msgid "I2PTunnel Client (more or less)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:67
-msgid "Relay"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:68
-msgid "Rendezvous Point"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:68
-msgid "somewhat like Inbound Gateway + Outbound Endpoint"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:69
-msgid "Router Descriptor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:69
-msgid "RouterInfo"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:70
-msgid "Server"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:73
-msgid "Benefits of Tor over I2P"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:76
-msgid ""
-"Much bigger user base; much more visibility in the academic and hacker "
-"communities; benefits from\n"
-"formal studies of anonymity, resistance, and performance;\n"
-"has a non-anonymous, visible, university-based leader"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:82
-msgid "Has already solved some scaling issues I2P has yet to address"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:83
-msgid "Has significant funding"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:84
-msgid "Has more developers, including several that are funded"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:86
-msgid ""
-"More resistant to state-level blocking due to TLS transport layer and "
-"bridges\n"
-"(I2P has proposals for \"full restricted routes\" but these are not yet "
-"implemented)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:91
-msgid "Big enough that it has had to adapt to blocking and DOS attempts"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:92
-msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:94
-msgid ""
-"Better documentation, has formal papers and specifications,\n"
-"better website, many more translations"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:99
-msgid "More efficient with memory usage"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:100
-msgid "Tor client nodes have very low bandwidth overhead"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:102
-msgid ""
-"Centralized control reduces the complexity at each\n"
-"node and can efficiently address Sybil attacks"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:108
-msgid ""
-"A core of high capacity nodes provides higher\n"
-"throughput and lower latency"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:113
-msgid "C, not Java (ewww)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:116
-msgid "Benefits of I2P over Tor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:118
-msgid ""
-"Designed and optimized for hidden services, which are much faster than in"
-" Tor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:119
-msgid "Fully distributed and self organizing"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:121
-msgid ""
-"Peers are selected by continuously profiling and ranking performance,\n"
-"rather than trusting claimed capacity"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:127
-msgid ""
-"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
-"rather than hardcoded"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:132
-msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:133
-msgid "Peer-to-peer friendly"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:134
-msgid "Packet switched instead of circuit switched"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:137
-msgid ""
-"implicit transparent load balancing of messages \n"
-"across multiple peers, rather than a single path"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:143
-msgid ""
-"resilience vs. failures by running multiple \n"
-"tunnels in parallel, plus rotating tunnels"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:149
-msgid ""
-"scale each client's connections at O(1) instead \n"
-"of O(N) (Alice has e.g. 2 inbound tunnels that are \n"
-"used by all of the peers Alice is talking with, \n"
-"rather than a circuit for each)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:159
-msgid ""
-"Unidirectional tunnels instead of bidirectional\n"
-"circuits, doubling the number of nodes a peer has to\n"
-"compromise to get the same information."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:166
-msgid ""
-"Protection against detecting client activity, even\n"
-"when an attacker is participating in the tunnel, as\n"
-"tunnels are used for more than simply passing end \n"
-"to end messages (e.g. netDb, tunnel management, \n"
-"tunnel testing)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:175
-msgid ""
-"Tunnels in I2P are short lived, decreasing the number\n"
-"of samples that an attacker can use to mount an \n"
-"active attack with, unlike circuits in Tor, which are\n"
-"typically long lived."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:183
-msgid ""
-"I2P APIs are designed specifically for anonymity and\n"
-"security, while SOCKS is designed for functionality."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:188
-msgid "Essentially all peers participate in routing for others"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:190
-msgid ""
-"The bandwidth overhead of being a full peer is low, \n"
-"while in Tor, while client nodes don't require much\n"
-"bandwidth, they don't fully participate in the mixnet."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:196
-msgid "Integrated automatic update mechanism"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:197
-msgid "Both TCP and UDP transports"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:198
-msgid "Java, not C (ewww)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:201
-msgid "Other potential benefits of I2P but not yet implemented"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:202
-msgid "...and may never be implemented, so don't count on them!"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:205
-msgid ""
-"Defense vs. message count analysis by garlic wrapping \n"
-"multiple messages"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:211
-msgid ""
-"Defense vs. long term intersection by adding delays \n"
-"at various hops (where the delays are not discernible\n"
-"by other hops)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:218
-msgid ""
-"Various mixing strategies at the tunnel level (e.g.\n"
-"create a tunnel that will handle 500 messages / minute,\n"
-"where the endpoint will inject dummy messages if there\n"
-"are insufficient messages, etc)"
-msgstr ""
-
 #: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:25
 msgid "Index to Technical Documentation"
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:3 i2p2www/pages/site/docs/ports.html:3
 #: i2p2www/pages/site/docs/spec/datagrams.html:3
-#: i2p2www/pages/site/docs/spec/geoip.html:3
-#: i2p2www/pages/site/docs/spec/updates.html:3
-#: i2p2www/pages/site/docs/transport/ssu.html:3
-#: i2p2www/pages/site/get-involved/develop/applications.html:3
 msgid "May 2013"
-msgstr ""
+msgstr "May 2013"
 
 #: i2p2www/pages/site/docs/index.html:6
 msgid "How does I2P work"
-msgstr ""
+msgstr "Wie I2p funktioniert"
 
 #: i2p2www/pages/site/docs/index.html:8
 msgid "Following is an index to the technical documentation for I2P."
@@ -6303,8 +55,7 @@ msgid ""
 "The I2P Project is committed to maintaining accurate, current "
 "documentation.\n"
 "If you find any inaccuracies in the documents linked below, please\n"
-"enter a ticket identifying the "
-"problem."
+"enter a ticket identifying the problem."
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:27 i2p2www/pages/site/docs/naming.html:7
@@ -6321,13 +72,12 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/updates.html:6
 #: i2p2www/pages/site/docs/tunnels/implementation.html:67
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:6
-#: i2p2www/pages/site/misc/jbigi.html:6
 msgid "Overview"
-msgstr ""
+msgstr "Übersicht"
 
 #: i2p2www/pages/site/docs/index.html:29
 msgid "Technical Introduction"
-msgstr ""
+msgstr "Technische Einleitung"
 
 #: i2p2www/pages/site/docs/index.html:30
 msgid "A Less-Technical Introduction"
@@ -6335,7 +85,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:31
 msgid "Threat model and analysis"
-msgstr ""
+msgstr "Bedrohungsszenario und Analysen"
 
 #: i2p2www/pages/site/docs/index.html:32
 msgid "Comparisons to other anonymous networks"
@@ -6346,8 +96,6 @@ msgid "Protocol stack chart"
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:34
-#: i2p2www/pages/site/research/papers.html:2
-#: i2p2www/pages/site/research/papers.html:4
 msgid "Papers on I2P"
 msgstr ""
 
@@ -6368,7 +116,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:42
 msgid "Plugins Overview"
-msgstr ""
+msgstr "Plugins Übersicht"
 
 #: i2p2www/pages/site/docs/index.html:43
 msgid "Plugin Specification"
@@ -6376,7 +124,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:44
 msgid "Router software updates"
-msgstr ""
+msgstr "Router Software Updates"
 
 #: i2p2www/pages/site/docs/index.html:45
 #: i2p2www/pages/site/docs/applications/bittorrent.html:2
@@ -6444,6 +192,11 @@ msgstr ""
 msgid "Streaming Javadoc"
 msgstr ""
 
+#: i2p2www/pages/site/docs/index.html:88
+#: i2p2www/pages/site/docs/api/datagrams.html:2
+msgid "Datagrams"
+msgstr ""
+
 #: i2p2www/pages/site/docs/index.html:90
 msgid "Datagram Javadoc"
 msgstr ""
@@ -6483,26 +236,28 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:110
 msgid "End-to-End Encryption"
-msgstr ""
+msgstr "Ende zu Ende Verschlüsselung"
 
 #: i2p2www/pages/site/docs/index.html:111
 msgid "How client messages are end-to-end encrypted by the router."
 msgstr ""
+"Wie Client Nachrichten durch den Router \"Ende zu Ende\" verschlüsselt "
+"werden."
 
 #: i2p2www/pages/site/docs/index.html:113
 msgid "ElGamal/AES+SessionTag encryption"
-msgstr ""
+msgstr "ElGamal/AES + SessionTag Verschlüsselung"
 
 #: i2p2www/pages/site/docs/index.html:114
 #: i2p2www/pages/site/docs/index.html:147
 msgid "ElGamal and AES cryptography details"
-msgstr ""
+msgstr "ElGamal und AES Verschlüsselungsdetails"
 
 #: i2p2www/pages/site/docs/index.html:117
 #: i2p2www/pages/site/docs/how/tech-intro.html:15
 #: i2p2www/pages/site/docs/how/tech-intro.html:329
 msgid "Network Database"
-msgstr ""
+msgstr "Netzwerk Datenbank"
 
 #: i2p2www/pages/site/docs/index.html:118
 msgid ""
@@ -6524,7 +279,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:125
 msgid "Router Message Protocol"
-msgstr ""
+msgstr "Router Nachrichten Protokoll"
 
 #: i2p2www/pages/site/docs/index.html:126
 msgid ""
@@ -6544,6 +299,12 @@ msgstr ""
 msgid "I2NP Javadoc"
 msgstr ""
 
+#: i2p2www/pages/site/docs/index.html:139
+#: i2p2www/pages/site/docs/how/tech-intro.html:14
+#: i2p2www/pages/site/docs/how/tech-intro.html:228
+msgid "Tunnels"
+msgstr "Tunnel"
+
 #: i2p2www/pages/site/docs/index.html:140
 msgid ""
 "Selecting peers, requesting tunnels through those peers, and encrypting "
@@ -6604,6 +365,10 @@ msgstr ""
 msgid "The protocols for direct (point-to-point) router to router communication."
 msgstr ""
 
+#: i2p2www/pages/site/docs/index.html:158
+msgid "Transport layer overview"
+msgstr ""
+
 #: i2p2www/pages/site/docs/index.html:160
 msgid "TCP-based transport overview and specification"
 msgstr ""
@@ -6648,22 +413,23 @@ msgstr ""
 msgid "Time synchronization and NTP"
 msgstr ""
 
+#: i2p2www/pages/site/docs/index.html:183
+msgid "Performance"
+msgstr ""
+
 #: i2p2www/pages/site/docs/index.html:190
 msgid "Developer's Guides and Resources"
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:192
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
 msgid "New Developer's Guide"
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:194
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
 msgid "New Translator's Guide"
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:196
-#: i2p2www/pages/site/get-involved/guides/monotone.html:4
 msgid "Monotone Guide"
 msgstr ""
 
@@ -6714,6 +480,10 @@ msgstr ""
 msgid "Developer forum inside I2P"
 msgstr ""
 
+#: i2p2www/pages/site/docs/index.html:223
+msgid "Bug tracker"
+msgstr ""
+
 #: i2p2www/pages/site/docs/index.html:225
 msgid "Viewmtn inside I2P"
 msgstr ""
@@ -6744,13 +514,20 @@ msgid "not current"
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:237
-#: i2p2www/pages/site/get-involved/todo.html:2
 msgid "To Do List"
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:3
+#: i2p2www/pages/site/docs/api/streaming.html:3
 #: i2p2www/pages/site/docs/how/cryptography.html:3
-msgid "March 2012"
+#: i2p2www/pages/site/docs/protocol/i2cp.html:3
+#: i2p2www/pages/site/docs/spec/common-structures.html:3
+#: i2p2www/pages/site/docs/spec/geoip.html:3
+#: i2p2www/pages/site/docs/spec/streaming.html:3
+#: i2p2www/pages/site/docs/transport/index.html:3
+#: i2p2www/pages/site/docs/transport/ntcp.html:3
+#: i2p2www/pages/site/docs/transport/ssu.html:3
+msgid "December 2013"
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:6
@@ -6820,9 +597,8 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:52
 msgid ""
-"The client application which does local lookups "
-"in hosts.txt\n"
-"and also takes care of the Base32 hostnames."
+"The local naming service which does lookups\n"
+"and also handles Base32 hostnames."
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:56
@@ -6859,7 +635,7 @@ msgid ""
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:77
-msgid "Naming Files and Lookups"
+msgid "Naming Services"
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:79
@@ -6880,37 +656,113 @@ msgstr ""
 msgid ""
 "If an application (i2ptunnel or the HTTP proxy) wishes to access\n"
 "a destination by name, the router does a very simple local lookup\n"
-"to resolve that name.\n"
-"The client application (technically, the client side of I2CP in the I2P "
-"API)\n"
-"does a linear search through three local files, in order, to\n"
-"look up host names and convert them to a 516-byte destination key:"
+"to resolve that name."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:94
+msgid "Hosts.txt Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:96
+msgid ""
+"The hosts.txt Naming Service does a simple linear search through\n"
+"text files. This naming service was the default until\n"
+"release 0.8.8 when it was replaced by the Blockfile Naming Service.\n"
+"The hosts.txt format had become too slow after the file grew to thousands"
+" of entries."
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:103
+#, python-format
+msgid ""
+"It does a linear search through three local files, in order, to\n"
+"look up host names and convert them to a 516-byte destination key.\n"
+"Each file is in a simple configuration file"
+" format, with hostname=base64, one per line.\n"
+"The files are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:115
+msgid "Blockfile Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:117
+msgid ""
+"The Blockfile Naming Service stores multiple \"addressbooks\" in a single"
+"\n"
+"database file named hostsdb.blockfile.\n"
+"This Naming Service is the default since release 0.8.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:123
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is specified on the Blockfile page.\n"
+"It provides fast Destination lookup in a compact format. While the "
+"blockfile overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry to implement "
+"advanced addressbook features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:135
+msgid ""
+"On creation, the naming service imports entries from the three files used"
+" by the hosts.txt Naming Service.\n"
+"The blockfile mimics the previous implementation by maintaining three "
+"maps that\n"
+"are searched in-order, named privatehosts.txt, userhosts.txt, and "
+"hosts.txt.\n"
+"It also maintains a reverse-lookup map to implement rapid reverse lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:142
+msgid "Other Naming Service Facilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:144
+#, python-format
 msgid ""
 "The lookup is case-insensitive.\n"
 "The first match is used, and conflicts are not detected.\n"
-"There is no enforcement of naming rules in lookups."
+"There is no enforcement of naming rules in lookups.\n"
+"Lookups are cached for a few minutes.\n"
+"Base 32 resolution is described below.\n"
+"For a full description of the Naming Service API see the\n"
+"Naming Service Javadocs.\n"
+"This API was significantly expanded in release 0.8.7 to provide\n"
+"adds and removes, storage of arbitrary properties with the hostname,\n"
+"and other features."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:109
+#: i2p2www/pages/site/docs/naming.html:157
+msgid "Alternatives and Experimental Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:159
 #, python-format
 msgid ""
-"Lookups are cached for a few minutes.\n"
-"There is an experimental facility for real-time lookups (a la DNS) over "
-"the network within the router,\n"
-"although it is not enabled by default\n"
-"(see \"EepGet\" under Alternatives on the discussion"
-" page)."
+"The naming service is specified with the configuration property "
+"i2p.naming.impl=class.\n"
+"Other implementations are possible. For example,\n"
+"there is an experimental facility for real-time lookups (a la DNS) over "
+"the network within the router.\n"
+"For more information see the alternatives on the discussion"
+" page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:116
-msgid "HTTP Proxy"
-msgstr ""
-
-#: i2p2www/pages/site/docs/naming.html:118
+#: i2p2www/pages/site/docs/naming.html:166
 msgid ""
 "The HTTP proxy does a lookup via the router for all hostnames ending in "
 "'.i2p'.\n"
@@ -6919,23 +771,31 @@ msgid ""
 "Top Level Domain '.i2p'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:124
+#: i2p2www/pages/site/docs/naming.html:172
+#, python-format
+msgid ""
+"We have applied to reserve the .i2p TLD\n"
+"following the procedures specified in RFC "
+"6761."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:178
 msgid ""
 "If the router fails to resolve the hostname, the HTTP proxy returns\n"
 "an error page to the user with links to several \"jump\" services.\n"
 "See below for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:130
+#: i2p2www/pages/site/docs/naming.html:184
 #: i2p2www/pages/site/docs/spec/configuration.html:77
 msgid "Addressbook"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:131
+#: i2p2www/pages/site/docs/naming.html:185
 msgid "Incoming Subscriptions and Merging"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:133
+#: i2p2www/pages/site/docs/naming.html:187
 msgid ""
 "The addressbook application periodically\n"
 "retrieves other users' hosts.txt files and merges\n"
@@ -6944,7 +804,7 @@ msgid ""
 "basis."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:141
+#: i2p2www/pages/site/docs/naming.html:195
 msgid ""
 "Subscribing to another user's hosts.txt file involves\n"
 "giving them a certain amount of trust.\n"
@@ -6953,7 +813,7 @@ msgid ""
 "passing the new host/key entry to you."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:149
+#: i2p2www/pages/site/docs/naming.html:203
 msgid ""
 "For this reason, the only subscription configured by\n"
 "default is http://www.i2p2.i2p/hosts.txt,\n"
@@ -6964,23 +824,23 @@ msgid ""
 "href=\"#susidns\">SusiDNS)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:158
+#: i2p2www/pages/site/docs/naming.html:212
 msgid "Some other public addressbook subscription links:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:165
+#: i2p2www/pages/site/docs/naming.html:219
 msgid ""
 "The operators of these services may have various policies for listing "
 "hosts.\n"
 "Presence on this list does not imply endorsement."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:170
-#: i2p2www/pages/site/docs/naming.html:182
+#: i2p2www/pages/site/docs/naming.html:224
+#: i2p2www/pages/site/docs/naming.html:236
 msgid "Naming Rules"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:171
+#: i2p2www/pages/site/docs/naming.html:225
 msgid ""
 "While there are hopefully not any technical limitations within I2P on "
 "host names,\n"
@@ -6994,81 +854,83 @@ msgid ""
 "to other routers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:186
+#: i2p2www/pages/site/docs/naming.html:240
 msgid "Names are converted to lower case on import."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:190
+#: i2p2www/pages/site/docs/naming.html:244
 msgid ""
 "Names are checked for conflict with existing names in the existing "
 "userhosts.txt and hosts.txt\n"
 "(but not privatehosts.txt) after conversion to lower case."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:195
+#: i2p2www/pages/site/docs/naming.html:249
 msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:199
+#: i2p2www/pages/site/docs/naming.html:253
 msgid "Must not start with '.' or '-'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:203
+#: i2p2www/pages/site/docs/naming.html:257
 msgid "Must end with '.i2p'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:207
+#: i2p2www/pages/site/docs/naming.html:261
 msgid "67 characters maximum, including the '.i2p'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:211
+#: i2p2www/pages/site/docs/naming.html:265
 msgid "Must not contain '..'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:215
+#: i2p2www/pages/site/docs/naming.html:269
 msgid "Must not contain '.-' or '-.' (as of 0.6.1.33)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:219
+#: i2p2www/pages/site/docs/naming.html:273
 msgid "Must not contain '--' except in 'xn--' for IDN."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:223
-msgid "Base32 hostnames (*.b32.i2p) are not allowed."
+#: i2p2www/pages/site/docs/naming.html:277
+msgid ""
+"Base32 hostnames (*.b32.i2p) are reserved for base 32 use and so are not "
+"allowed to be imported."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:227
+#: i2p2www/pages/site/docs/naming.html:281
 msgid ""
 "Certain hostnames reserved for project use are not allowed\n"
 "(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
 "*.console.i2p, and others)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:232
+#: i2p2www/pages/site/docs/naming.html:286
 msgid "Keys are checked for base64 validity."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:236
+#: i2p2www/pages/site/docs/naming.html:290
 msgid ""
 "Keys are checked for conflict with existing keys in hosts.txt (but not "
 "privatehosts.txt)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:240
+#: i2p2www/pages/site/docs/naming.html:294
 msgid "Minimum key length 516 bytes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:244
+#: i2p2www/pages/site/docs/naming.html:298
 msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:249
+#: i2p2www/pages/site/docs/naming.html:303
 msgid ""
-"Any name received via subscription that passes all the checks is added to"
-" the local hosts.txt."
+"Any name received via subscription that passes all the checks is added "
+"via the local naming service."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:253
+#: i2p2www/pages/site/docs/naming.html:307
 msgid ""
 "Note that the '.' symbols in a host name are of no significance,\n"
 "and do not denote any actual naming or trust hierarchy.\n"
@@ -7080,7 +942,7 @@ msgid ""
 "are topics for future discussion."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:264
+#: i2p2www/pages/site/docs/naming.html:318
 msgid ""
 "International Domain Names (IDN) also work in i2p (using punycode 'xn--' "
 "form).\n"
@@ -7089,7 +951,7 @@ msgid ""
 "add 'network.IDN.whitelist.i2p (boolean) = true' in about:config."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:270
+#: i2p2www/pages/site/docs/naming.html:324
 msgid ""
 "As the addressbook application does not use privatehosts.txt at all, in "
 "practice\n"
@@ -7098,11 +960,11 @@ msgid ""
 "\"pet names\" for sites already in hosts.txt."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:276
+#: i2p2www/pages/site/docs/naming.html:330
 msgid "Outgoing Subscriptions"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:277
+#: i2p2www/pages/site/docs/naming.html:331
 msgid ""
 "Addressbook will publish the merged hosts.txt to a location\n"
 "(traditionally hosts.txt in the local eepsite's home directory) to be "
@@ -7111,7 +973,7 @@ msgid ""
 "This step is optional and is disabled by default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:285
+#: i2p2www/pages/site/docs/naming.html:339
 msgid ""
 "The addressbook application, together with eepget, saves the Etag and/or "
 "Last-Modified\n"
@@ -7120,13 +982,13 @@ msgid ""
 "return a '304 Not Modified' on the next fetch if nothing has changed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:292
+#: i2p2www/pages/site/docs/naming.html:346
 msgid ""
 "However the entire hosts.txt is downloaded if it has changed.\n"
 "See below for discussion on this issue."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:297
+#: i2p2www/pages/site/docs/naming.html:351
 msgid ""
 "Hosts serving a static hosts.txt or an equivalent CGI application\n"
 "are strongly encouraged to deliver\n"
@@ -7137,11 +999,11 @@ msgid ""
 "reduce chances of corruption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:306
+#: i2p2www/pages/site/docs/naming.html:360
 msgid "Host Add Services"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:307
+#: i2p2www/pages/site/docs/naming.html:361
 msgid ""
 "A host add service is a simple CGI application that takes a hostname and "
 "a Base64 key as parameters\n"
@@ -7150,7 +1012,7 @@ msgid ""
 "will be propagated through the network."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:314
+#: i2p2www/pages/site/docs/naming.html:368
 msgid ""
 "It is recommended that host add services impose, at a minimum, the "
 "restrictions imposed by the addressbook application listed above.\n"
@@ -7158,55 +1020,55 @@ msgid ""
 "keys, for example:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:319
+#: i2p2www/pages/site/docs/naming.html:373
 msgid "A limit on number of 'subdomains'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:323
+#: i2p2www/pages/site/docs/naming.html:377
 msgid "Authorization for 'subdomains' through various methods."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:327
+#: i2p2www/pages/site/docs/naming.html:381
 msgid "Hashcash or signed certificates."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:331
+#: i2p2www/pages/site/docs/naming.html:385
 msgid "Editorial review of host names and/or content."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:335
+#: i2p2www/pages/site/docs/naming.html:389
 msgid "Categorization of hosts by content."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:339
+#: i2p2www/pages/site/docs/naming.html:393
 msgid "Reservation or rejection of certain host names."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:343
+#: i2p2www/pages/site/docs/naming.html:397
 msgid "Restrictions on the number of names registered in a given time period."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:347
+#: i2p2www/pages/site/docs/naming.html:401
 msgid "Delays between registration and publication."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:351
+#: i2p2www/pages/site/docs/naming.html:405
 msgid "Requirement that the host be up for verification."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:355
+#: i2p2www/pages/site/docs/naming.html:409
 msgid "Expiration and/or revocation."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:359
+#: i2p2www/pages/site/docs/naming.html:413
 msgid "IDN spoof rejection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:364
+#: i2p2www/pages/site/docs/naming.html:418
 msgid "Jump Services"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:365
+#: i2p2www/pages/site/docs/naming.html:419
 msgid ""
 "A jump service is a simple CGI application that takes a hostname as a "
 "parameter\n"
@@ -7219,20 +1081,20 @@ msgid ""
 "address helper is not necessary until restart."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:375
+#: i2p2www/pages/site/docs/naming.html:429
 msgid ""
 "Note that, like with subscriptions, using a jump service\n"
 "implies a certain amount of trust, as a jump service could maliciously\n"
 "redirect a user to an incorrect destination."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:381
+#: i2p2www/pages/site/docs/naming.html:435
 msgid ""
 "To provide the best service, a jump service should be subscribed to\n"
 "several hosts.txt providers so that its local host list is current."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:387
+#: i2p2www/pages/site/docs/naming.html:441
 msgid ""
 "SusiDNS is simply a web interface front-end to configuring addressbook "
 "subscriptions\n"
@@ -7240,7 +1102,7 @@ msgid ""
 "All the real work is done by the 'addressbook' application."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:393
+#: i2p2www/pages/site/docs/naming.html:447
 msgid ""
 "Currently, there is little enforcement of addressbook naming rules within"
 " SusiDNS,\n"
@@ -7248,11 +1110,11 @@ msgid ""
 "the addressbook subscription rules."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:399
+#: i2p2www/pages/site/docs/naming.html:453
 msgid "Base32 Names"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:400
+#: i2p2www/pages/site/docs/naming.html:454
 msgid ""
 "I2P supports Base32 hostnames similar to Tor's .onion addresses.\n"
 "Base32 addresses are much shorter and easier to handle than the\n"
@@ -7261,12 +1123,18 @@ msgid ""
 "ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:407
+#: i2p2www/pages/site/docs/naming.html:461
+#, python-format
 msgid ""
 "In Tor, the address is 16 characters (80 bits), or half of the SHA-1 "
 "hash.\n"
 "I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n"
 "The form is {52 chars}.b32.i2p.\n"
+"Tor has recently published a\n"
+"proposal\n"
+"to convert to an identical format of {52 chars}.onion for their hidden "
+"services.\n"
 "Base32 is implemented in the naming service, which queries the\n"
 "router over I2CP to lookup the LeaseSet to get the full Destination.\n"
 "Base32 lookups will only be successful when the Destination is up and "
@@ -7277,7 +1145,7 @@ msgid ""
 "longer than a local address book lookup."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:419
+#: i2p2www/pages/site/docs/naming.html:476
 msgid ""
 "Base32 addresses can be used in most places where hostnames or full "
 "destinations\n"
@@ -7286,6 +1154,11 @@ msgid ""
 "the name does not resolve to a destination."
 msgstr ""
 
+#: i2p2www/pages/site/docs/plugins.html:2
+#: i2p2www/pages/site/docs/spec/configuration.html:65
+msgid "Plugins"
+msgstr "Plugins"
+
 #: i2p2www/pages/site/docs/plugins.html:3
 msgid "June 2012"
 msgstr ""
@@ -7570,6 +1443,13 @@ msgstr ""
 msgid "recommended spot for new plugins/applications"
 msgstr ""
 
+#: i2p2www/pages/site/docs/api/bob.html:3
+#: i2p2www/pages/site/docs/api/datagrams.html:3
+#: i2p2www/pages/site/docs/how/garlic-routing.html:3
+#: i2p2www/pages/site/docs/protocol/index.html:3
+msgid "August 2010"
+msgstr ""
+
 #: i2p2www/pages/site/docs/api/bob.html:5
 msgid "BOB - Basic Open Bridge"
 msgstr ""
@@ -8015,7 +1895,7 @@ msgid ""
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/datagrams.html:93
-#: i2p2www/pages/site/docs/api/streaming.html:325
+#: i2p2www/pages/site/docs/api/streaming.html:381
 msgid "Data Integrity"
 msgstr ""
 
@@ -8028,7 +1908,7 @@ msgid ""
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/datagrams.html:100
-#: i2p2www/pages/site/docs/api/streaming.html:333
+#: i2p2www/pages/site/docs/api/streaming.html:389
 msgid "Packet Encapsulation"
 msgstr ""
 
@@ -8048,7 +1928,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/api/datagrams.html:114
 #: i2p2www/pages/site/docs/spec/datagrams.html:10
-#: i2p2www/pages/site/docs/transport/ssu.html:567
+#: i2p2www/pages/site/docs/transport/ssu.html:571
 msgid "Specification"
 msgstr ""
 
@@ -8121,8 +2001,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:29
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:33
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:34
-#: i2p2www/pages/site/docs/protocol/i2cp.html:99
-#: i2p2www/pages/site/docs/protocol/i2cp.html:442
+#: i2p2www/pages/site/docs/protocol/i2cp.html:107
+#: i2p2www/pages/site/docs/protocol/i2cp.html:450
 #: i2p2www/pages/site/docs/spec/common-structures.html:16
 #: i2p2www/pages/site/docs/spec/common-structures.html:26
 #: i2p2www/pages/site/docs/spec/common-structures.html:37
@@ -8138,12 +2018,12 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/common-structures.html:162
 #: i2p2www/pages/site/docs/spec/common-structures.html:174
 #: i2p2www/pages/site/docs/spec/common-structures.html:227
-#: i2p2www/pages/site/docs/spec/common-structures.html:294
-#: i2p2www/pages/site/docs/spec/common-structures.html:343
-#: i2p2www/pages/site/docs/spec/common-structures.html:387
-#: i2p2www/pages/site/docs/spec/common-structures.html:432
-#: i2p2www/pages/site/docs/spec/common-structures.html:569
-#: i2p2www/pages/site/docs/spec/common-structures.html:625
+#: i2p2www/pages/site/docs/spec/common-structures.html:310
+#: i2p2www/pages/site/docs/spec/common-structures.html:359
+#: i2p2www/pages/site/docs/spec/common-structures.html:411
+#: i2p2www/pages/site/docs/spec/common-structures.html:456
+#: i2p2www/pages/site/docs/spec/common-structures.html:593
+#: i2p2www/pages/site/docs/spec/common-structures.html:655
 msgid "Description"
 msgstr ""
 
@@ -8539,36 +2419,40 @@ msgid "Method not found."
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:194
+msgid "Invalid parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:195
 msgid "Internal error."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:196
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
 msgid "I2PControl specific error codes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
 msgid "Invalid password provided."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
 msgid "No authentication token presented."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
 msgid "Authentication token doesn't exist."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
 msgid "The provided authentication token was expired and will be removed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
 msgid ""
 "The version of the I2PControl API used wasn't specified, but is required "
 "to be specified."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:203
 msgid ""
 "The version of the I2PControl API specified is not supported by "
 "I2PControl."
@@ -8629,9 +2513,7 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:43
 #, python-format
 msgid ""
-"The anonymous monotone"
-"\n"
+"The anonymous monotone\n"
 "sourcecode repository for I2P"
 msgstr ""
 
@@ -8953,12 +2835,6 @@ msgid ""
 "risks of socks proxies."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:3
-#: i2p2www/pages/site/docs/protocol/i2cp.html:3
-#: i2p2www/pages/site/docs/spec/streaming.html:3
-msgid "November 2012"
-msgstr ""
-
 #: i2p2www/pages/site/docs/api/streaming.html:8
 #, python-format
 msgid ""
@@ -9028,6 +2904,10 @@ msgid ""
 "it contains a full windowing implementation."
 msgstr ""
 
+#: i2p2www/pages/site/docs/api/streaming.html:58
+msgid "API"
+msgstr "API"
+
 #: i2p2www/pages/site/docs/api/streaming.html:60
 #, python-format
 msgid ""
@@ -9107,14 +2987,14 @@ msgid ""
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/streaming.html:117
-#: i2p2www/pages/site/docs/protocol/i2cp.html:94
-#: i2p2www/pages/site/docs/protocol/i2cp.html:437
+#: i2p2www/pages/site/docs/protocol/i2cp.html:102
+#: i2p2www/pages/site/docs/protocol/i2cp.html:445
 msgid "Option"
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/streaming.html:117
-#: i2p2www/pages/site/docs/protocol/i2cp.html:98
-#: i2p2www/pages/site/docs/protocol/i2cp.html:441
+#: i2p2www/pages/site/docs/protocol/i2cp.html:106
+#: i2p2www/pages/site/docs/protocol/i2cp.html:449
 msgid "Default"
 msgstr ""
 
@@ -9124,11 +3004,11 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/common-structures.html:58
 #: i2p2www/pages/site/docs/spec/common-structures.html:203
 #: i2p2www/pages/site/docs/spec/common-structures.html:257
-#: i2p2www/pages/site/docs/spec/common-structures.html:335
-#: i2p2www/pages/site/docs/spec/common-structures.html:421
-#: i2p2www/pages/site/docs/spec/common-structures.html:529
-#: i2p2www/pages/site/docs/spec/common-structures.html:607
-#: i2p2www/pages/site/docs/spec/common-structures.html:709
+#: i2p2www/pages/site/docs/spec/common-structures.html:351
+#: i2p2www/pages/site/docs/spec/common-structures.html:445
+#: i2p2www/pages/site/docs/spec/common-structures.html:553
+#: i2p2www/pages/site/docs/spec/common-structures.html:631
+#: i2p2www/pages/site/docs/spec/common-structures.html:739
 #: i2p2www/pages/site/docs/spec/datagrams.html:30
 #: i2p2www/pages/site/docs/spec/datagrams.html:89
 msgid "Notes"
@@ -9143,15 +3023,22 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/streaming.html:121
 #: i2p2www/pages/site/docs/api/streaming.html:127
 #: i2p2www/pages/site/docs/api/streaming.html:133
-#: i2p2www/pages/site/docs/api/streaming.html:147
-#: i2p2www/pages/site/docs/api/streaming.html:176
-#: i2p2www/pages/site/docs/api/streaming.html:184
-#: i2p2www/pages/site/docs/api/streaming.html:214
+#: i2p2www/pages/site/docs/api/streaming.html:140
+#: i2p2www/pages/site/docs/api/streaming.html:152
+#: i2p2www/pages/site/docs/api/streaming.html:163
+#: i2p2www/pages/site/docs/api/streaming.html:192
+#: i2p2www/pages/site/docs/api/streaming.html:200
 #: i2p2www/pages/site/docs/api/streaming.html:220
-#: i2p2www/pages/site/docs/api/streaming.html:226
-#: i2p2www/pages/site/docs/api/streaming.html:240
-#: i2p2www/pages/site/docs/api/streaming.html:247
-#: i2p2www/pages/site/docs/api/streaming.html:254
+#: i2p2www/pages/site/docs/api/streaming.html:237
+#: i2p2www/pages/site/docs/api/streaming.html:249
+#: i2p2www/pages/site/docs/api/streaming.html:255
+#: i2p2www/pages/site/docs/api/streaming.html:261
+#: i2p2www/pages/site/docs/api/streaming.html:275
+#: i2p2www/pages/site/docs/api/streaming.html:282
+#: i2p2www/pages/site/docs/api/streaming.html:289
+#: i2p2www/pages/site/docs/api/streaming.html:314
+#: i2p2www/pages/site/docs/api/streaming.html:321
+#: i2p2www/pages/site/docs/api/streaming.html:328
 #, python-format
 msgid "As of release %(release)s."
 msgstr ""
@@ -9164,11 +3051,11 @@ msgstr ""
 msgid "Use the access list as a blacklist for incoming connections."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:137
+#: i2p2www/pages/site/docs/api/streaming.html:145
 msgid "Whether to respond to incoming pings"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:141
+#: i2p2www/pages/site/docs/api/streaming.html:157
 msgid ""
 "Comma- or space-separated list of Base64 peer Hashes to be\n"
 "blacklisted for incoming connections to ALL destinations in the context.\n"
@@ -9179,13 +3066,13 @@ msgid ""
 "router in a separate JVM and context."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:151
+#: i2p2www/pages/site/docs/api/streaming.html:167
 msgid ""
 "How much transmit data (in bytes) will be accepted that hasn't been "
 "written out yet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:155
+#: i2p2www/pages/site/docs/api/streaming.html:171
 msgid ""
 "When we're in congestion avoidance, we grow the window size at the rate\n"
 "of 1/(windowSize*factor).  In standard TCP, window sizes are"
@@ -9194,7 +3081,7 @@ msgid ""
 "A higher number means slower growth."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:162
+#: i2p2www/pages/site/docs/api/streaming.html:178
 msgid ""
 "How long to wait after instantiating a new con \n"
 "before actually attempting to connect.  If this is\n"
@@ -9204,19 +3091,19 @@ msgid ""
 "or that many milliseconds pass, and include any initial data with the SYN."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:170
+#: i2p2www/pages/site/docs/api/streaming.html:186
 msgid ""
 "How long to block on connect, in milliseconds. Negative means "
 "indefinitely. Default is 5 minutes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:174
+#: i2p2www/pages/site/docs/api/streaming.html:190
 msgid ""
 "Whether to disable warnings in the logs when an incoming connection is "
 "rejected due to connection limits."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:180
+#: i2p2www/pages/site/docs/api/streaming.html:196
 msgid ""
 "Whether to listen only for the streaming protocol.\n"
 "Setting to true will prohibit communication with Destinations earlier "
@@ -9225,77 +3112,89 @@ msgid ""
 "Destination."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:188
+#: i2p2www/pages/site/docs/api/streaming.html:204
 msgid ""
 "(0=noop, 1=disconnect)\n"
 "What to do on an inactivity timeout - do nothing, disconnect, or send a "
 "duplicate ack."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:196
+#: i2p2www/pages/site/docs/api/streaming.html:212
 msgid ""
 "The initial value of the resend delay field in the packet header, times "
 "1000.\n"
 "Not fully implemented; see below."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:201
-#: i2p2www/pages/site/docs/api/streaming.html:203
+#: i2p2www/pages/site/docs/api/streaming.html:217
+msgid ""
+"Initial timeout\n"
+"(if no sharing data available)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:224
+msgid ""
+"Initial round trip time estimate\n"
+"(if no sharing data available).\n"
+"Disabled as of release 0.9.8; uses actual RTT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
 msgid "if no sharing data available"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:203
+#: i2p2www/pages/site/docs/api/streaming.html:230
 msgid ""
 "In standard TCP, window sizes are in bytes, while in I2P, window sizes "
 "are in messages."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:207
+#: i2p2www/pages/site/docs/api/streaming.html:242
 msgid ""
 "(0 or negative value means unlimited)\n"
 "This is a total limit for incoming and outgoing combined."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:212
+#: i2p2www/pages/site/docs/api/streaming.html:247
 msgid "Incoming connection limit (per peer; 0 means disabled)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:218
-#: i2p2www/pages/site/docs/api/streaming.html:224
+#: i2p2www/pages/site/docs/api/streaming.html:253
+#: i2p2www/pages/site/docs/api/streaming.html:259
 msgid "(per peer; 0 means disabled)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:230
+#: i2p2www/pages/site/docs/api/streaming.html:265
 msgid "The MTU in bytes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:234
+#: i2p2www/pages/site/docs/api/streaming.html:269
 msgid "Maximum number of retransmissions before failure."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:238
+#: i2p2www/pages/site/docs/api/streaming.html:273
 msgid "Incoming connection limit (all peers; 0 means disabled)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:244
-#: i2p2www/pages/site/docs/api/streaming.html:251
+#: i2p2www/pages/site/docs/api/streaming.html:279
+#: i2p2www/pages/site/docs/api/streaming.html:286
 msgid ""
 "(all peers; 0 means disabled)\n"
 "Use with caution as exceeding this will disable a server for a long time."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:260
+#: i2p2www/pages/site/docs/api/streaming.html:295
 msgid ""
 "(2=interactive not supported)\n"
 "This doesn't currently do anything, but setting it to a value other than "
 "1 will cause an error."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:265
+#: i2p2www/pages/site/docs/api/streaming.html:300
 msgid "How long to block on read, in milliseconds. Negative means indefinitely."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:269
+#: i2p2www/pages/site/docs/api/streaming.html:304
 msgid ""
 "When we're in slow start, we grow the window size at the rate\n"
 "of 1/(factor).  In standard TCP, window sizes are in bytes,\n"
@@ -9303,26 +3202,38 @@ msgid ""
 "A higher number means slower growth."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:276
+#: i2p2www/pages/site/docs/api/streaming.html:311
+#: i2p2www/pages/site/docs/api/streaming.html:318
+#: i2p2www/pages/site/docs/api/streaming.html:325
+msgid ""
+"Ref: RFC 2140. Floating point value.\n"
+"May be set only via context properties, not connection options."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:332
 msgid ""
 "How long to block on write/flush, in milliseconds. Negative means "
 "indefinitely."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:284
+#: i2p2www/pages/site/docs/api/streaming.html:340
 #: i2p2www/pages/site/docs/spec/streaming.html:10
 msgid "Protocol Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:286
+#: i2p2www/pages/site/docs/api/streaming.html:342
 msgid "See the Streaming Library Specification page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:290
+#: i2p2www/pages/site/docs/api/streaming.html:346
 msgid "Implementation Details"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:293
+#: i2p2www/pages/site/docs/api/streaming.html:348
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:349
 msgid ""
 "The initiator sends a packet with the SYNCHRONIZE flag set. This packet "
 "may contain the initial data as well.\n"
@@ -9330,7 +3241,7 @@ msgid ""
 " may contain the initial response data as well."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:298
+#: i2p2www/pages/site/docs/api/streaming.html:354
 msgid ""
 "The initiator may send additional data packets, up to the initial window "
 "size, before receiving the SYNCHRONIZE response.\n"
@@ -9340,11 +3251,11 @@ msgid ""
 "arrive out of order, in advance of the SYNCHRONIZE packet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:305
+#: i2p2www/pages/site/docs/api/streaming.html:361
 msgid "MTU Selection and Negotiation"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:306
+#: i2p2www/pages/site/docs/api/streaming.html:362
 msgid ""
 "The maximum message size (also called the MTU / MRU) is negotiated to the"
 " lower value supported by\n"
@@ -9357,7 +3268,7 @@ msgid ""
 "including overhead for the typical case."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:315
+#: i2p2www/pages/site/docs/api/streaming.html:371
 msgid ""
 "The first message in a connection includes a 387 byte (typical) "
 "Destination added by the streaming layer,\n"
@@ -9375,7 +3286,7 @@ msgid ""
 "connections."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:326
+#: i2p2www/pages/site/docs/api/streaming.html:382
 #, python-format
 msgid ""
 "Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
@@ -9383,7 +3294,7 @@ msgid ""
 "There is no checksum field in the streaming protocol."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:334
+#: i2p2www/pages/site/docs/api/streaming.html:390
 #, python-format
 msgid ""
 "Each packet is sent through I2P as a single message (or as an individual "
@@ -9397,11 +3308,11 @@ msgid ""
 "mechanism or payload length field in the streaming protocol."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:344
+#: i2p2www/pages/site/docs/api/streaming.html:400
 msgid "Windowing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:345
+#: i2p2www/pages/site/docs/api/streaming.html:401
 msgid ""
 "The streaming lib uses standard slow-start (exponential window growth) "
 "and congestion avoidance (linear window growth)\n"
@@ -9409,11 +3320,11 @@ msgid ""
 "Windowing and acknowledgments use packet count, not byte count."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:352
+#: i2p2www/pages/site/docs/api/streaming.html:408
 msgid "Close"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:353
+#: i2p2www/pages/site/docs/api/streaming.html:409
 msgid ""
 "Any packet, including one with the SYNCHRONIZE flag set, may have the "
 "CLOSE flag sent as well.\n"
@@ -9422,15 +3333,50 @@ msgid ""
 "CLOSE packets may contain data as well."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:360
+#: i2p2www/pages/site/docs/api/streaming.html:417
+msgid ""
+"There is no ping function at the I2CP layer (equivalent to ICMP echo) or "
+"in datagrams.\n"
+"This function is provided in streaming.\n"
+"Pings and pongs may not be combined with a standard streaming packet;\n"
+"if the ECHO option is set, then\n"
+"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. "
+"are ignored."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:425
+msgid ""
+"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED "
+"flags set.\n"
+"The sendStreamId must be greater than zero, and the receiveStreamId is "
+"ignored.\n"
+"The sendStreamId may or may not correspond to an existing connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:431
+msgid ""
+"A pong packet must have the ECHO flag set.\n"
+"The sendStreamId must be zero, and the receiveStreamId is the "
+"sendStreamId from the ping.\n"
+"The pong packet does not include any payload that was contained in the "
+"ping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:437
+msgid ""
+"Streaming may be configured to disable sending pongs with the "
+"configuration i2p.streaming.answerPings=false."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:442
 msgid "Control Block Sharing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:361
+#: i2p2www/pages/site/docs/api/streaming.html:443
 msgid ""
 "The streaming lib supports \"TCP\" Control Block sharing.\n"
-"This shares two important streaming lib parameters\n"
-"(window size and round trip time)\n"
+"This shares three important streaming lib parameters\n"
+"(window size, round trip time, round trip time variance)\n"
 "across connections to the same remote peer.\n"
 "This is used for \"temporal\" sharing at connection open/close time,\n"
 "not \"ensemble\" sharing during a connection (See\n"
@@ -9439,25 +3385,26 @@ msgid ""
 "Destination)\n"
 "so that there is no information leakage to other Destinations on the\n"
 "same router.\n"
-"The share data for a given peer expires after a few minutes."
+"The share data for a given peer expires after a few minutes.\n"
+"The following Control Block Sharing parameters can be set per router:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:375
+#: i2p2www/pages/site/docs/api/streaming.html:464
 msgid "Other Parameters"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:376
+#: i2p2www/pages/site/docs/api/streaming.html:465
 msgid ""
 "The following parameters are hardcoded, but may be of interest for "
 "analysis:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:393
-#: i2p2www/pages/site/docs/how/network-database.html:831
+#: i2p2www/pages/site/docs/api/streaming.html:484
+#: i2p2www/pages/site/docs/how/network-database.html:843
 msgid "History"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:394
+#: i2p2www/pages/site/docs/api/streaming.html:485
 msgid ""
 "The streaming library has grown organically for I2P - first mihi "
 "implemented the\n"
@@ -9480,33 +3427,33 @@ msgid ""
 "messages."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:408
+#: i2p2www/pages/site/docs/api/streaming.html:499
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:331
 #: i2p2www/pages/site/docs/how/garlic-routing.html:242
-#: i2p2www/pages/site/docs/how/network-database.html:836
+#: i2p2www/pages/site/docs/how/network-database.html:848
 #: i2p2www/pages/site/docs/how/peer-selection.html:265
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:255
-#: i2p2www/pages/site/docs/protocol/i2cp.html:646
+#: i2p2www/pages/site/docs/protocol/i2cp.html:654
 #: i2p2www/pages/site/docs/protocol/i2np.html:227
-#: i2p2www/pages/site/docs/spec/updates.html:222
-#: i2p2www/pages/site/docs/transport/ntcp.html:443
-#: i2p2www/pages/site/docs/transport/ssu.html:502
+#: i2p2www/pages/site/docs/spec/updates.html:280
+#: i2p2www/pages/site/docs/transport/ntcp.html:446
+#: i2p2www/pages/site/docs/transport/ssu.html:506
 #: i2p2www/pages/site/docs/tunnels/implementation.html:503
 msgid "Future Work"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:409
+#: i2p2www/pages/site/docs/api/streaming.html:500
 msgid ""
 "The behavior of the streaming library has a profound impact on\n"
 "application-level performance, and as such, is an important\n"
 "area for further analysis."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:415
+#: i2p2www/pages/site/docs/api/streaming.html:506
 msgid "Additional tuning of the streaming lib parameters may be necessary."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:418
+#: i2p2www/pages/site/docs/api/streaming.html:509
 #, python-format
 msgid ""
 "Another area for research is the interaction of the streaming lib with "
@@ -9515,7 +3462,7 @@ msgid ""
 "See the NTCP discussion page for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:423
+#: i2p2www/pages/site/docs/api/streaming.html:514
 msgid ""
 "The interaction of the routing algorithms with the streaming lib strongly"
 " affects performance.\n"
@@ -9530,32 +3477,32 @@ msgid ""
 "improvements."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:433
+#: i2p2www/pages/site/docs/api/streaming.html:524
 msgid "The data in the first SYN packet may exceed the receiver's MTU."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:436
+#: i2p2www/pages/site/docs/api/streaming.html:527
 msgid "The DELAY_REQUESTED field could be used more."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:439
+#: i2p2www/pages/site/docs/api/streaming.html:530
 msgid ""
 "Duplicate initial SYNCHRONIZE packets on short-lived streams may not be "
 "recognized and removed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:442
+#: i2p2www/pages/site/docs/api/streaming.html:533
 msgid "Don't send the MTU in a retransmission."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:445
+#: i2p2www/pages/site/docs/api/streaming.html:536
 msgid ""
 "Data is sent along unless the outbound window is full.\n"
 "(i.e. no-Nagle or TCP_NODELAY)\n"
 "Probably should have a configuration option for this."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:450
+#: i2p2www/pages/site/docs/api/streaming.html:541
 msgid ""
 "zzz has added debug code to the streaming library to log packets in a "
 "wireshark-compatible\n"
@@ -9564,7 +3511,7 @@ msgid ""
 "to TCP fields."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:455
+#: i2p2www/pages/site/docs/api/streaming.html:546
 msgid ""
 "There are proposals to replace the streaming lib with standard TCP\n"
 "(or perhaps a null layer together with raw sockets).\n"
@@ -9721,7 +3668,7 @@ msgstr ""
 msgid ""
 "While compact response support is optional for both clients and trackers,"
 " it is highly\n"
-"recommended as it reduces the nominal response size by over 90%."
+"recommended as it reduces the nominal response size by over 90%."
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:116
@@ -10014,82 +3961,82 @@ msgid "Email"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:26
-#: i2p2www/pages/site/docs/applications/supported.html:315
+#: i2p2www/pages/site/docs/applications/supported.html:328
 msgid "File Sharing"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:29
-#: i2p2www/pages/site/docs/applications/supported.html:317
+#: i2p2www/pages/site/docs/applications/supported.html:330
 msgid "BitTorrent clients"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:31
-#: i2p2www/pages/site/docs/applications/supported.html:359
+#: i2p2www/pages/site/docs/applications/supported.html:372
 msgid "BitTorrent trackers and indexers"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:40
-#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:439
 msgid "Network Administration"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:43
-#: i2p2www/pages/site/docs/applications/supported.html:428
+#: i2p2www/pages/site/docs/applications/supported.html:441
 msgid "General-purpose socket utilities"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:50
-#: i2p2www/pages/site/docs/applications/supported.html:469
+#: i2p2www/pages/site/docs/applications/supported.html:482
 msgid "Real-time Chat"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:53
-#: i2p2www/pages/site/docs/applications/supported.html:471
+#: i2p2www/pages/site/docs/applications/supported.html:484
 msgid "Instant messaging clients"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:55
-#: i2p2www/pages/site/docs/applications/supported.html:481
+#: i2p2www/pages/site/docs/applications/supported.html:494
 msgid "IRC clients"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:57
-#: i2p2www/pages/site/docs/applications/supported.html:532
+#: i2p2www/pages/site/docs/applications/supported.html:545
 msgid "IRC servers"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:62
-#: i2p2www/pages/site/docs/applications/supported.html:548
+#: i2p2www/pages/site/docs/applications/supported.html:561
 msgid "Web Browsing"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:65
-#: i2p2www/pages/site/docs/applications/supported.html:550
+#: i2p2www/pages/site/docs/applications/supported.html:563
 msgid "Anonymous websites"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:67
-#: i2p2www/pages/site/docs/applications/supported.html:599
+#: i2p2www/pages/site/docs/applications/supported.html:612
 msgid "Proxy software"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:69
-#: i2p2www/pages/site/docs/applications/supported.html:624
+#: i2p2www/pages/site/docs/applications/supported.html:637
 msgid "Inproxies"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:71
-#: i2p2www/pages/site/docs/applications/supported.html:640
+#: i2p2www/pages/site/docs/applications/supported.html:669
 msgid "Outproxies"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:76
-#: i2p2www/pages/site/docs/applications/supported.html:654
+#: i2p2www/pages/site/docs/applications/supported.html:683
 msgid "Website Hosting"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:79
-#: i2p2www/pages/site/docs/applications/supported.html:669
+#: i2p2www/pages/site/docs/applications/supported.html:698
 msgid "Web servers"
 msgstr ""
 
@@ -10098,8 +4045,7 @@ msgstr ""
 msgid ""
 "This is intended to be a comprehensive listing of applications used with\n"
 "I2P. If you know of something that's missing please submit a ticket on\n"
-"Trac, and be sure to select the"
-"\n"
+"Trac, and be sure to select the\n"
 "“www” component in the submission form."
 msgstr ""
 
@@ -10112,8 +4058,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:97
 #: i2p2www/pages/site/docs/applications/supported.html:279
 #: i2p2www/pages/site/docs/applications/supported.html:311
-#: i2p2www/pages/site/docs/applications/supported.html:323
-#: i2p2www/pages/site/docs/applications/supported.html:666
+#: i2p2www/pages/site/docs/applications/supported.html:336
+#: i2p2www/pages/site/docs/applications/supported.html:695
 msgid "bundled"
 msgstr ""
 
@@ -10131,10 +4077,10 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:228
 #: i2p2www/pages/site/docs/applications/supported.html:241
 #: i2p2www/pages/site/docs/applications/supported.html:292
-#: i2p2www/pages/site/docs/applications/supported.html:391
-#: i2p2www/pages/site/docs/applications/supported.html:413
-#: i2p2www/pages/site/docs/applications/supported.html:422
-#: i2p2www/pages/site/docs/applications/supported.html:510
+#: i2p2www/pages/site/docs/applications/supported.html:404
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:523
 msgid "plugin"
 msgstr ""
 
@@ -10154,30 +4100,31 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:241
 #: i2p2www/pages/site/docs/applications/supported.html:252
 #: i2p2www/pages/site/docs/applications/supported.html:261
-#: i2p2www/pages/site/docs/applications/supported.html:329
-#: i2p2www/pages/site/docs/applications/supported.html:340
-#: i2p2www/pages/site/docs/applications/supported.html:355
-#: i2p2www/pages/site/docs/applications/supported.html:401
-#: i2p2www/pages/site/docs/applications/supported.html:413
-#: i2p2www/pages/site/docs/applications/supported.html:422
-#: i2p2www/pages/site/docs/applications/supported.html:437
-#: i2p2www/pages/site/docs/applications/supported.html:443
-#: i2p2www/pages/site/docs/applications/supported.html:449
-#: i2p2www/pages/site/docs/applications/supported.html:459
-#: i2p2www/pages/site/docs/applications/supported.html:465
-#: i2p2www/pages/site/docs/applications/supported.html:477
-#: i2p2www/pages/site/docs/applications/supported.html:510
-#: i2p2www/pages/site/docs/applications/supported.html:516
-#: i2p2www/pages/site/docs/applications/supported.html:522
-#: i2p2www/pages/site/docs/applications/supported.html:528
-#: i2p2www/pages/site/docs/applications/supported.html:605
-#: i2p2www/pages/site/docs/applications/supported.html:614
-#: i2p2www/pages/site/docs/applications/supported.html:620
-#: i2p2www/pages/site/docs/applications/supported.html:666
-#: i2p2www/pages/site/docs/applications/supported.html:681
-#: i2p2www/pages/site/docs/applications/supported.html:687
-#: i2p2www/pages/site/docs/applications/supported.html:693
-#: i2p2www/pages/site/docs/applications/supported.html:699
+#: i2p2www/pages/site/docs/applications/supported.html:324
+#: i2p2www/pages/site/docs/applications/supported.html:342
+#: i2p2www/pages/site/docs/applications/supported.html:353
+#: i2p2www/pages/site/docs/applications/supported.html:368
+#: i2p2www/pages/site/docs/applications/supported.html:414
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:450
+#: i2p2www/pages/site/docs/applications/supported.html:456
+#: i2p2www/pages/site/docs/applications/supported.html:462
+#: i2p2www/pages/site/docs/applications/supported.html:472
+#: i2p2www/pages/site/docs/applications/supported.html:478
+#: i2p2www/pages/site/docs/applications/supported.html:490
+#: i2p2www/pages/site/docs/applications/supported.html:523
+#: i2p2www/pages/site/docs/applications/supported.html:529
+#: i2p2www/pages/site/docs/applications/supported.html:535
+#: i2p2www/pages/site/docs/applications/supported.html:541
+#: i2p2www/pages/site/docs/applications/supported.html:618
+#: i2p2www/pages/site/docs/applications/supported.html:627
+#: i2p2www/pages/site/docs/applications/supported.html:633
+#: i2p2www/pages/site/docs/applications/supported.html:695
+#: i2p2www/pages/site/docs/applications/supported.html:710
+#: i2p2www/pages/site/docs/applications/supported.html:716
+#: i2p2www/pages/site/docs/applications/supported.html:722
+#: i2p2www/pages/site/docs/applications/supported.html:728
 msgid "standalone"
 msgstr ""
 
@@ -10186,11 +4133,11 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:202
 #: i2p2www/pages/site/docs/applications/supported.html:208
 #: i2p2www/pages/site/docs/applications/supported.html:214
-#: i2p2www/pages/site/docs/applications/supported.html:349
-#: i2p2www/pages/site/docs/applications/supported.html:373
-#: i2p2www/pages/site/docs/applications/supported.html:382
-#: i2p2www/pages/site/docs/applications/supported.html:538
-#: i2p2www/pages/site/docs/applications/supported.html:544
+#: i2p2www/pages/site/docs/applications/supported.html:362
+#: i2p2www/pages/site/docs/applications/supported.html:386
+#: i2p2www/pages/site/docs/applications/supported.html:395
+#: i2p2www/pages/site/docs/applications/supported.html:551
+#: i2p2www/pages/site/docs/applications/supported.html:557
 msgid "standalone/mod"
 msgstr ""
 
@@ -10207,14 +4154,16 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:135
 #: i2p2www/pages/site/docs/applications/supported.html:302
-#: i2p2www/pages/site/docs/applications/supported.html:558
-#: i2p2www/pages/site/docs/applications/supported.html:568
-#: i2p2www/pages/site/docs/applications/supported.html:577
-#: i2p2www/pages/site/docs/applications/supported.html:583
-#: i2p2www/pages/site/docs/applications/supported.html:589
-#: i2p2www/pages/site/docs/applications/supported.html:595
-#: i2p2www/pages/site/docs/applications/supported.html:636
-#: i2p2www/pages/site/docs/applications/supported.html:650
+#: i2p2www/pages/site/docs/applications/supported.html:571
+#: i2p2www/pages/site/docs/applications/supported.html:581
+#: i2p2www/pages/site/docs/applications/supported.html:590
+#: i2p2www/pages/site/docs/applications/supported.html:596
+#: i2p2www/pages/site/docs/applications/supported.html:602
+#: i2p2www/pages/site/docs/applications/supported.html:608
+#: i2p2www/pages/site/docs/applications/supported.html:649
+#: i2p2www/pages/site/docs/applications/supported.html:657
+#: i2p2www/pages/site/docs/applications/supported.html:665
+#: i2p2www/pages/site/docs/applications/supported.html:679
 msgid "service"
 msgstr ""
 
@@ -10230,7 +4179,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:148
 #: i2p2www/pages/site/docs/applications/supported.html:220
-#: i2p2www/pages/site/docs/applications/supported.html:355
+#: i2p2www/pages/site/docs/applications/supported.html:368
 msgid "unmaintained"
 msgstr ""
 
@@ -10358,15 +4307,24 @@ msgid ""
 "email service by default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:322
+#: i2p2www/pages/site/docs/applications/supported.html:316
+#, python-format
+msgid ""
+"Can be configured to use Postman's email service. See\n"
+"this comparison of MUAs,\n"
+"and configuration settings for\n"
+"SMTP and POP3."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:335
 msgid "I2P's integrated BitTorrent client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:328
+#: i2p2www/pages/site/docs/applications/supported.html:341
 msgid "Modified version of I2PSnark."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:334
+#: i2p2www/pages/site/docs/applications/supported.html:347
 msgid ""
 "\n"
 "A fork of rufus that uses the Basic Open Bridge (BOB) and has many\n"
@@ -10375,49 +4333,49 @@ msgid ""
 "magnet-link like fetching of torrents within I2P.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:345
+#: i2p2www/pages/site/docs/applications/supported.html:358
 msgid ""
 "Clean, full-featured cross-platform BitTorrent client with official\n"
 "ports for several GUI toolkits."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:354
+#: i2p2www/pages/site/docs/applications/supported.html:367
 msgid "Has a plugin providing I2P support."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:361
+#: i2p2www/pages/site/docs/applications/supported.html:374
 #, python-format
 msgid ""
 "For a detailed feature comparison of I2P-enabled trackers/indexers, see\n"
 "here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:369
+#: i2p2www/pages/site/docs/applications/supported.html:382
 msgid ""
 "The code that powered one of the first major tracker/indexer sites on the"
 "\n"
 "Internet. Patched for I2P."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:378
+#: i2p2www/pages/site/docs/applications/supported.html:391
 #, python-format
 msgid ""
 "Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n"
 "branch of the I2P Monotone repository."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:387
+#: i2p2www/pages/site/docs/applications/supported.html:400
 #, python-format
 msgid ""
 "zzz's Java-based open tracker. More info\n"
 "here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:400
+#: i2p2www/pages/site/docs/applications/supported.html:413
 msgid "I2P port of the aMule ED2K client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:409
+#: i2p2www/pages/site/docs/applications/supported.html:422
 #, python-format
 msgid ""
 "Port of the Phex Gnutella "
@@ -10425,44 +4383,44 @@ msgid ""
 "for plugin version here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:418
+#: i2p2www/pages/site/docs/applications/supported.html:431
 #, python-format
 msgid ""
 "Cache for Gnutella peers on I2P. Website for plugin version\n"
 "here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:433
+#: i2p2www/pages/site/docs/applications/supported.html:446
 msgid ""
 "Unix standard tool for socket relaying. Several clones, ports, and forks\n"
 "have appeared over the years."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:442
+#: i2p2www/pages/site/docs/applications/supported.html:455
 msgid "Like netcat but more powerful."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:448
+#: i2p2www/pages/site/docs/applications/supported.html:461
 msgid ""
 "Proxy providing simple, transparent SOCKS-ification of network "
 "applications."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:458
+#: i2p2www/pages/site/docs/applications/supported.html:471
 msgid ""
 "Most popular implementation of the Secure Shell (SSH) protocol and "
 "related tools."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:464
+#: i2p2www/pages/site/docs/applications/supported.html:477
 msgid "Open source Secure Shell (SSH) client for Windows."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:476
+#: i2p2www/pages/site/docs/applications/supported.html:489
 msgid "IM client with multiple incarnations."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:483
+#: i2p2www/pages/site/docs/applications/supported.html:496
 msgid ""
 "Many IRC clients leak identifying information to servers or other\n"
 "clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound"
@@ -10479,7 +4437,7 @@ msgid ""
 "/me command) which isn't inherently dangerous."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:494
+#: i2p2www/pages/site/docs/applications/supported.html:507
 msgid ""
 "I2P's IRC filtering may not cover every possible leak — users should also"
 "\n"
@@ -10492,100 +4450,105 @@ msgid ""
 "developers; they may be able to solve it via additional filtering."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:506
+#: i2p2www/pages/site/docs/applications/supported.html:519
 #, python-format
 msgid ""
 "Small Java-based IRC client. Plugin available here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:515
+#: i2p2www/pages/site/docs/applications/supported.html:528
 msgid "Cross-platform graphical IRC client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:521
+#: i2p2www/pages/site/docs/applications/supported.html:534
 msgid "Unixy terminal-based IRC client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:527
+#: i2p2www/pages/site/docs/applications/supported.html:540
 msgid "Another Unixy terminal-based IRC client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:537
+#: i2p2www/pages/site/docs/applications/supported.html:550
 msgid "IRC server developed from scratch."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:543
+#: i2p2www/pages/site/docs/applications/supported.html:556
 msgid "Most popular IRC server."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:555
+#: i2p2www/pages/site/docs/applications/supported.html:568
 msgid ""
 "Any website hosted anonymously on I2P, reachable through the I2P router's"
 " HTTP proxy."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:563
+#: i2p2www/pages/site/docs/applications/supported.html:576
 msgid ""
 "Distributed anonymous websites hosted\n"
 "using Tahoe-LAFS-I2P, currently only reachable with Tahoe-LAFS-I2P\n"
 "clients or through the Tahoe-LAFS-I2P HTTP proxy."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:573
+#: i2p2www/pages/site/docs/applications/supported.html:586
 #, python-format
 msgid ""
 "Website for sponge's jump service.\n"
 "Source code available."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:582
+#: i2p2www/pages/site/docs/applications/supported.html:595
 msgid "Another jump service."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:588
+#: i2p2www/pages/site/docs/applications/supported.html:601
 msgid "Dynamically updated eepsite index."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:594
+#: i2p2www/pages/site/docs/applications/supported.html:607
 #, python-format
 msgid "Website for zzz's jump service."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:604
+#: i2p2www/pages/site/docs/applications/supported.html:617
 msgid "SOCKS-enabled caching web proxy with basic filtering capabilities."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:610
+#: i2p2www/pages/site/docs/applications/supported.html:623
 msgid ""
 "Privacy-focused non-caching web proxy with advanced filtering\n"
 "capabilities. Excels at removing ads and other junk."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:619
+#: i2p2www/pages/site/docs/applications/supported.html:632
 msgid "Venerable caching web proxy."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:626
+#: i2p2www/pages/site/docs/applications/supported.html:639
 msgid "Gateways allowing users on the public Internet to access eepsites."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:633
+#: i2p2www/pages/site/docs/applications/supported.html:646
 #, python-format
 msgid "tino's inproxy on the public Internet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:642
+#: i2p2www/pages/site/docs/applications/supported.html:654
+#: i2p2www/pages/site/docs/applications/supported.html:662
+msgid "Another inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:671
 msgid ""
 "Gateways allowing I2P users to access content hosted on the public "
 "Internet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:649
+#: i2p2www/pages/site/docs/applications/supported.html:678
 msgid "Publicly advertised outproxy running Squid, located in Germany."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:659
+#: i2p2www/pages/site/docs/applications/supported.html:688
 msgid ""
 "Lightweight web server and Java servlet container. I2P is tightly\n"
 "integrated with a bundled copy of Jetty which by default is configured to"
@@ -10597,26 +4560,26 @@ msgid ""
 "I2P."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:671
+#: i2p2www/pages/site/docs/applications/supported.html:700
 msgid ""
 "In addition to Jetty, any web server should function over I2P without\n"
 "modification so long as it's HTTP-compliant. Some web servers known to\n"
 "currently serve content on the I2P network are:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:680
+#: i2p2www/pages/site/docs/applications/supported.html:709
 msgid "Most popular web server on the public WWW."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:686
+#: i2p2www/pages/site/docs/applications/supported.html:715
 msgid "Web server and Java servlet container. More features than Jetty."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:692
+#: i2p2www/pages/site/docs/applications/supported.html:721
 msgid "Fast lightweight web server."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:698
+#: i2p2www/pages/site/docs/applications/supported.html:727
 msgid "High-performance lightweight web server."
 msgstr ""
 
@@ -11116,7 +5079,7 @@ msgid ""
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/cryptography.html:34
-#: i2p2www/pages/site/docs/how/cryptography.html:189
+#: i2p2www/pages/site/docs/how/cryptography.html:198
 #, python-format
 msgid ""
 "For encryption of some netDb stores and "
@@ -11197,19 +5160,25 @@ msgstr ""
 msgid ""
 "While the standard exponent size is 2048 bits (256 bytes) and the I2P\n"
 "PrivateKey\n"
-"is a full 256 bytes,\n"
-"we use the short exponent size of 226 bits (28.25 bytes).\n"
+"is a full 256 bytes, in some cases\n"
+"we use the short exponent size of 226 bits (28.25 bytes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:150
+#, python-format
+msgid ""
 "This should be safe for use with the Oakley primes, per\n"
 "On Diffie-Hellman Key Agreement with Short Exponents "
 "- van Oorschot, Weiner\n"
 "at EuroCrypt 96, and crypto++'s "
 "benchmarks.\n"
-"Benchmarks originally at %(oldbenchmarks)s (now dead),\n"
+"Benchmarks originally at this link, now dead,\n"
 "rescued from the wayback machine,"
 " dated Apr 23, 2008."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:158
+#: i2p2www/pages/site/docs/how/cryptography.html:160
 #, python-format
 msgid ""
 "Also, Koshiba & Kurosawa: Short Exponent Diffie-"
@@ -11220,36 +5189,46 @@ msgid ""
 "The remainder of the PrivateKey is padded with zeroes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:167
-#: i2p2www/pages/site/docs/how/cryptography.html:264
-#: i2p2www/pages/site/docs/how/cryptography.html:343
-#: i2p2www/pages/site/docs/how/cryptography.html:382
+#: i2p2www/pages/site/docs/how/cryptography.html:169
+msgid ""
+"Prior to release 0.9.8, all routers used the short exponent.\n"
+"As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent.\n"
+"Other routers continue to use the short exponent due to concerns about "
+"processor load.\n"
+"The transition to a longer exponent for these platforms is a topic for "
+"further study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:176
+#: i2p2www/pages/site/docs/how/cryptography.html:273
+#: i2p2www/pages/site/docs/how/cryptography.html:352
+#: i2p2www/pages/site/docs/how/cryptography.html:391
 msgid "Obsolescence"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:168
+#: i2p2www/pages/site/docs/how/cryptography.html:177
 msgid ""
 "The vulnerability of the network to an ElGamal attack and the impact of "
 "transitioning to a longer bit length is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:176
+#: i2p2www/pages/site/docs/how/cryptography.html:185
 msgid "AES is used for symmetric encryption, in several cases:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:181
+#: i2p2www/pages/site/docs/how/cryptography.html:190
 msgid "For transport encryption after DH key exchange"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:185
+#: i2p2www/pages/site/docs/how/cryptography.html:194
 #, python-format
 msgid ""
 "For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:195
+#: i2p2www/pages/site/docs/how/cryptography.html:204
 #, python-format
 msgid ""
 "For encryption of periodic tunnel "
@@ -11257,7 +5236,7 @@ msgid ""
 "tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:200
+#: i2p2www/pages/site/docs/how/cryptography.html:209
 #, python-format
 msgid ""
 "We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n"
@@ -11272,27 +5251,27 @@ msgid ""
 "ElGamalAESEngine.getPadding function."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:265
+#: i2p2www/pages/site/docs/how/cryptography.html:274
 msgid ""
 "The vulnerability of the network to an AES attack and the impact of "
 "transitioning to a longer bit length is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:270
-#: i2p2www/pages/site/docs/how/cryptography.html:362
-#: i2p2www/pages/site/docs/how/cryptography.html:388
-#: i2p2www/pages/site/docs/how/cryptography.html:456
+#: i2p2www/pages/site/docs/how/cryptography.html:279
+#: i2p2www/pages/site/docs/how/cryptography.html:371
+#: i2p2www/pages/site/docs/how/cryptography.html:397
+#: i2p2www/pages/site/docs/how/cryptography.html:465
 #: i2p2www/pages/site/docs/how/garlic-routing.html:281
 #: i2p2www/pages/site/docs/how/peer-selection.html:296
 msgid "References"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:273
+#: i2p2www/pages/site/docs/how/cryptography.html:282
 msgid "Feb. 7, 2006 Status Notes"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:280
+#: i2p2www/pages/site/docs/how/cryptography.html:289
 #, python-format
 msgid ""
 "Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), "
@@ -11301,11 +5280,11 @@ msgid ""
 "DSA was chosen because it is much faster for signatures than ElGamal."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:286
+#: i2p2www/pages/site/docs/how/cryptography.html:295
 msgid "The DSA constants"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:337
+#: i2p2www/pages/site/docs/how/cryptography.html:346
 #, python-format
 msgid ""
 "The Signing Public"
@@ -11314,7 +5293,7 @@ msgid ""
 "Private Key is 160 bits."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:344
+#: i2p2www/pages/site/docs/how/cryptography.html:353
 #, python-format
 msgid ""
 "NIST 800-57\n"
@@ -11323,7 +5302,7 @@ msgid ""
 "given key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:350
+#: i2p2www/pages/site/docs/how/cryptography.html:359
 msgid ""
 "The prime number was chosen in 2003,\n"
 "and the person that chose the number (TheCrypto) is currently no longer "
@@ -11333,38 +5312,42 @@ msgid ""
 "prime, and we will document the construction process."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:357
+#: i2p2www/pages/site/docs/how/cryptography.html:366
 msgid ""
 "The vulnerability of the network to a DSA attack and the impact of "
 "transitioning to longer keys is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:365
-#: i2p2www/pages/site/docs/how/cryptography.html:367
+#: i2p2www/pages/site/docs/how/cryptography.html:374
+#: i2p2www/pages/site/docs/how/cryptography.html:376
 #, python-format
 msgid "Meeting %(num)s"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:369
+#: i2p2www/pages/site/docs/how/cryptography.html:378
 msgid "Choosing the constants"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:377
+#: i2p2www/pages/site/docs/how/cryptography.html:386
 #, python-format
 msgid ""
 "Hashes within I2P are plain old SHA256, as implemented in\n"
 "[SHA256Generator]"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:383
+#: i2p2www/pages/site/docs/how/cryptography.html:392
 msgid ""
 "The vulnerability of the network to a SHA-256 attack and the impact of "
 "transitioning to a longer hash is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:395
+#: i2p2www/pages/site/docs/how/cryptography.html:403
+msgid "Transports"
+msgstr "Transports"
+
+#: i2p2www/pages/site/docs/how/cryptography.html:404
 msgid ""
 "At the lowest protocol layer,\n"
 "point-to-point inter-router communication is protected by the transport "
@@ -11380,11 +5363,11 @@ msgid ""
 "on the transport links."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:407
+#: i2p2www/pages/site/docs/how/cryptography.html:416
 msgid "NTCP connections"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:409
+#: i2p2www/pages/site/docs/how/cryptography.html:418
 #, python-format
 msgid ""
 "NTCP connections are negotiated with a 2048 Diffie-Hellman "
@@ -11401,35 +5384,35 @@ msgid ""
 "href=\"%(elgamalaes)s\">ElGamalAES+SessionTag does not."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:417
+#: i2p2www/pages/site/docs/how/cryptography.html:426
 msgid ""
 "In order to migrate to a more standardized implementation (TLS/SSL or "
 "even SSH), the following issues must be addressed:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:421
+#: i2p2www/pages/site/docs/how/cryptography.html:430
 msgid ""
 "Can we somehow reestablish sessions securely (ala session tags) or do we "
 "need to do full negotiation each time?"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:424
+#: i2p2www/pages/site/docs/how/cryptography.html:433
 msgid ""
 "Can we simplify/avoid the x509 or other certificate formats and use our "
 "own RouterInfo structure (which \n"
 "contains the ElGamal and DSA keys)?"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:429
+#: i2p2www/pages/site/docs/how/cryptography.html:438
 #, python-format
 msgid "See the NTCP specification for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:433
+#: i2p2www/pages/site/docs/how/cryptography.html:442
 msgid "UDP connections"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:434
+#: i2p2www/pages/site/docs/how/cryptography.html:443
 msgid ""
 "SSU (the UDP transport) encrypts each packet with AES256/CBC with both an"
 " explicit IV and MAC \n"
@@ -11442,12 +5425,12 @@ msgid ""
 "checking."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:442
+#: i2p2www/pages/site/docs/how/cryptography.html:451
 #, python-format
 msgid "See the SSU specification for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:446
+#: i2p2www/pages/site/docs/how/cryptography.html:455
 #, python-format
 msgid ""
 "WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n"
@@ -12835,9 +6818,8 @@ msgid "The Network Database"
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/network-database.html:3
-#: i2p2www/pages/site/docs/protocol/i2np.html:3
-#: i2p2www/pages/site/docs/spec/common-structures.html:3
-msgid "June 2013"
+#: i2p2www/pages/site/docs/spec/updates.html:3
+msgid "October 2013"
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/network-database.html:8
@@ -12908,28 +6890,74 @@ msgid ""
 "approximate bandwidth, and perceived reachability"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/network-database.html:47
+msgid "SSU Testing"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/network-database.html:48
-msgid "The core library version, always the same as the router version"
+msgid "SSU Introducer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:49
+#: i2p2www/pages/site/docs/how/network-database.html:246
+msgid "Floodfill"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:50
+msgid "Hidden"
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/network-database.html:51
+#, python-format
+msgid "Under %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+#: i2p2www/pages/site/docs/how/network-database.html:53
+#: i2p2www/pages/site/docs/how/network-database.html:54
+#, python-format
+msgid "%(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+msgid "default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:55
+#, python-format
+msgid "Over %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:56
+msgid "Reachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:57
+msgid "Unreachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:62
+msgid "The core library version, always the same as the router version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:65
 msgid ""
 "Basic network compatibility - A router will refuse to communicate with a "
 "peer having a different netId"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:54
+#: i2p2www/pages/site/docs/how/network-database.html:68
 msgid "Used to determine compatibility with newer features and messages"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:57
+#: i2p2www/pages/site/docs/how/network-database.html:71
 msgid ""
 "Always sent as 90m, for compatibility with an older scheme where routers "
 "published their actual uptime,\n"
 "and only sent tunnel requests to peers whose was more than 60m"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:62
+#: i2p2www/pages/site/docs/how/network-database.html:76
 msgid ""
 "These values are used by other routers for basic decisions.\n"
 "Should we connect to this router? Should we attempt to route a tunnel "
@@ -12943,7 +6971,7 @@ msgid ""
 " and network analysis."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:72
+#: i2p2www/pages/site/docs/how/network-database.html:86
 #, python-format
 msgid ""
 "Additional text options include\n"
@@ -12958,15 +6986,15 @@ msgid ""
 "Current statistics are limited to:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:83
+#: i2p2www/pages/site/docs/how/network-database.html:97
 msgid "Client and exploratory tunnel build success, reject, and timeout rates"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:84
+#: i2p2www/pages/site/docs/how/network-database.html:98
 msgid "1 hour average number of participating tunnels"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:87
+#: i2p2www/pages/site/docs/how/network-database.html:101
 msgid ""
 "The data published can be seen in the router's user interface,\n"
 "but is not used or trusted within the router.\n"
@@ -12976,19 +7004,19 @@ msgid ""
 "releases."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:95
+#: i2p2www/pages/site/docs/how/network-database.html:109
 msgid "RouterInfo specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:98
+#: i2p2www/pages/site/docs/how/network-database.html:112
 msgid "RouterInfo Javadoc"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:101
+#: i2p2www/pages/site/docs/how/network-database.html:115
 msgid "RouterInfo Expiration"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:102
+#: i2p2www/pages/site/docs/how/network-database.html:116
 msgid ""
 "RouterInfos have no set expiration time.\n"
 "Each router is free to maintain its own local policy to trade off the "
@@ -12997,17 +7025,17 @@ msgid ""
 "In the current implementation, there are the following general policies:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:109
+#: i2p2www/pages/site/docs/how/network-database.html:123
 msgid ""
 "There is no expiration during the first hour of uptime, as the persistent"
 " stored data may be old."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:112
+#: i2p2www/pages/site/docs/how/network-database.html:126
 msgid "There is no expiration if there are 25 or less RouterInfos."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:115
+#: i2p2www/pages/site/docs/how/network-database.html:129
 msgid ""
 "As the number of local RouterInfos grows, the expiration time shrinks, in"
 " an attempt to maintain\n"
@@ -13016,7 +7044,7 @@ msgid ""
 "while expiration time with 300 routers is around 30 hours."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:120
+#: i2p2www/pages/site/docs/how/network-database.html:134
 #, python-format
 msgid ""
 "RouterInfos containing SSU introducers expire in "
@@ -13024,24 +7052,24 @@ msgid ""
 "the introducer list expires in about that time."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:124
+#: i2p2www/pages/site/docs/how/network-database.html:138
 msgid ""
 "Floodfills use a short expiration time (1 hour) for all local "
 "RouterInfos, as valid RouterInfos will\n"
 "be frequently republished to them."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:130
+#: i2p2www/pages/site/docs/how/network-database.html:144
 msgid "RouterInfo Persistent Storage"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:132
+#: i2p2www/pages/site/docs/how/network-database.html:146
 msgid ""
 "RouterInfos are periodically written to disk so that they are available "
 "after a restart."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:139
+#: i2p2www/pages/site/docs/how/network-database.html:153
 msgid ""
 "The second piece of data distributed in the netDb is a \"LeaseSet\" - "
 "documenting\n"
@@ -13050,73 +7078,73 @@ msgid ""
 "Each of these leases specify the following information:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:145
+#: i2p2www/pages/site/docs/how/network-database.html:159
 msgid "The tunnel gateway router (by specifying its identity)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:146
+#: i2p2www/pages/site/docs/how/network-database.html:160
 msgid "The tunnel ID on that router to send messages with (a 4 byte number)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:147
+#: i2p2www/pages/site/docs/how/network-database.html:161
 msgid "When that tunnel will expire."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:149
+#: i2p2www/pages/site/docs/how/network-database.html:163
 msgid ""
 "The LeaseSet itself is stored in the netDb under\n"
 "the key derived from the SHA256 of the destination."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:154
+#: i2p2www/pages/site/docs/how/network-database.html:168
 msgid "In addition to these leases, the LeaseSet includes:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:158
+#: i2p2www/pages/site/docs/how/network-database.html:172
 msgid ""
 "The destination itself (a 2048bit ElGamal encryption key, 1024bit DSA "
 "signing key and a certificate)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:159
+#: i2p2www/pages/site/docs/how/network-database.html:173
 msgid ""
 "Additional encryption public key: used for end-to-end encryption of "
 "garlic messages"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:160
+#: i2p2www/pages/site/docs/how/network-database.html:174
 msgid ""
 "Additional signing public key: intended for LeaseSet revocation, but is "
 "currently unused."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:161
+#: i2p2www/pages/site/docs/how/network-database.html:175
 msgid ""
 "Signature of all the LeaseSet data, to make sure the Destination "
 "published the LeaseSet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:165
+#: i2p2www/pages/site/docs/how/network-database.html:179
 msgid "Lease specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:167
+#: i2p2www/pages/site/docs/how/network-database.html:181
 msgid "LeaseSet specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:170
+#: i2p2www/pages/site/docs/how/network-database.html:184
 msgid "Lease Javadoc"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:172
+#: i2p2www/pages/site/docs/how/network-database.html:186
 msgid "LeaseSet Javadoc"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:176
+#: i2p2www/pages/site/docs/how/network-database.html:190
 msgid "Unpublished LeaseSets"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:177
+#: i2p2www/pages/site/docs/how/network-database.html:191
 msgid ""
 "A LeaseSet for a destination used only for outgoing connections is "
 "unpublished.\n"
@@ -13128,11 +7156,11 @@ msgid ""
 "because of I2NP storage messages."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:187
+#: i2p2www/pages/site/docs/how/network-database.html:201
 msgid "Revoked LeaseSets"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:188
+#: i2p2www/pages/site/docs/how/network-database.html:202
 msgid ""
 "A LeaseSet may be revoked by publishing a new LeaseSet with zero "
 "leases.\n"
@@ -13144,11 +7172,11 @@ msgid ""
 "unused."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:195
+#: i2p2www/pages/site/docs/how/network-database.html:209
 msgid "Encrypted LeaseSets"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:196
+#: i2p2www/pages/site/docs/how/network-database.html:210
 msgid ""
 "In an encrypted LeaseSet, all Leases are encrypted with a separate"
 " DSA key.\n"
@@ -13163,32 +7191,32 @@ msgid ""
 "LeaseSets could be improved."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:205
+#: i2p2www/pages/site/docs/how/network-database.html:219
 msgid "LeaseSet Expiration"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:206
+#: i2p2www/pages/site/docs/how/network-database.html:220
 msgid ""
 "All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet "
 "expires\n"
 "10 minutes after the earliest creation time of all its Leases."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:211
+#: i2p2www/pages/site/docs/how/network-database.html:225
 msgid "LeaseSet Persistent Storage"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:212
+#: i2p2www/pages/site/docs/how/network-database.html:226
 msgid ""
 "There is no persistent storage of LeaseSet data since they expire so "
 "quickly."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:217
+#: i2p2www/pages/site/docs/how/network-database.html:231
 msgid "Bootstrapping"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:218
+#: i2p2www/pages/site/docs/how/network-database.html:232
 msgid ""
 "The netDb is decentralized, however you do need at\n"
 "least one reference to a peer so that the integration process\n"
@@ -13209,11 +7237,7 @@ msgid ""
 "one of these URLs, selected at random."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:232
-msgid "Floodfill"
-msgstr ""
-
-#: i2p2www/pages/site/docs/how/network-database.html:233
+#: i2p2www/pages/site/docs/how/network-database.html:247
 msgid ""
 "The floodfill netDb is a simple distributed storage mechanism.\n"
 "The storage algorithm is simple: send the data to the closest peer that "
@@ -13232,24 +7256,24 @@ msgid ""
 "href=\"#kademlia_closeness\">XOR-metric) to a specific key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:244
+#: i2p2www/pages/site/docs/how/network-database.html:258
 msgid ""
 "Determining who is part of the floodfill netDb is trivial - it is exposed"
 " in each \n"
 "router's published routerInfo as a capability."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:249
+#: i2p2www/pages/site/docs/how/network-database.html:263
 msgid ""
 "Floodfills have no central authority and do not form a \"consensus\" -\n"
 "they only implement a simple DHT overlay."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:256
+#: i2p2www/pages/site/docs/how/network-database.html:270
 msgid "Floodfill Router Opt-in"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:258
+#: i2p2www/pages/site/docs/how/network-database.html:272
 msgid ""
 "Unlike Tor, where the directory servers are hardcoded and trusted,\n"
 "and operated by known entities,\n"
@@ -13257,7 +7281,7 @@ msgid ""
 "change over time."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:265
+#: i2p2www/pages/site/docs/how/network-database.html:279
 msgid ""
 "To increase reliability of the netDb, and minimize the impact\n"
 "of netDb traffic on a router, floodfill is automatically enabled\n"
@@ -13269,7 +7293,7 @@ msgid ""
 "KBytes/sec."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:275
+#: i2p2www/pages/site/docs/how/network-database.html:289
 msgid ""
 "In addition, a router must pass several additional tests for health\n"
 "(outbound message queue time, job lag, etc.) before floodfill operation "
@@ -13277,14 +7301,13 @@ msgid ""
 "automatically enabled."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:281
-#, python-format
+#: i2p2www/pages/site/docs/how/network-database.html:295
 msgid ""
-"With the current rules for automatic opt-in, approximately 6% of\n"
+"With the current rules for automatic opt-in, approximately 6% of\n"
 "the routers in the network are floodfill routers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:286
+#: i2p2www/pages/site/docs/how/network-database.html:300
 msgid ""
 "While some peers are manually configured to be floodfill,\n"
 "others are simply high-bandwidth routers who automatically volunteer\n"
@@ -13295,11 +7318,11 @@ msgid ""
 "too many floodfills outstanding."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:296
+#: i2p2www/pages/site/docs/how/network-database.html:310
 msgid "Floodfill Router Roles"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:297
+#: i2p2www/pages/site/docs/how/network-database.html:311
 msgid ""
 "A floodfill router's only services that are in addition to those of non-"
 "floodfill routers\n"
@@ -13310,11 +7333,11 @@ msgid ""
 "their distributed database services."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:305
+#: i2p2www/pages/site/docs/how/network-database.html:319
 msgid "Kademlia Closeness Metric"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:306
+#: i2p2www/pages/site/docs/how/network-database.html:320
 msgid ""
 "The netDb uses a simple Kademlia-style XOR metric to determine closeness."
 "\n"
@@ -13333,22 +7356,22 @@ msgid ""
 "although it isn't strictly a rotation."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:318
+#: i2p2www/pages/site/docs/how/network-database.html:332
 msgid ""
 "Routing keys are never sent on-the-wire in any I2NP message, they are "
 "only used locally for\n"
 "determination of distance."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:325
+#: i2p2www/pages/site/docs/how/network-database.html:339
 msgid "Storage, Verification, and Lookup Mechanics"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:327
+#: i2p2www/pages/site/docs/how/network-database.html:341
 msgid "RouterInfo Storage to Peers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:328
+#: i2p2www/pages/site/docs/how/network-database.html:342
 #, python-format
 msgid ""
 "I2NP DatabaseStoreMessages containing the local "
@@ -13357,11 +7380,11 @@ msgid ""
 "or SSU transport connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:335
+#: i2p2www/pages/site/docs/how/network-database.html:349
 msgid "LeaseSet Storage to Peers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:336
+#: i2p2www/pages/site/docs/how/network-database.html:350
 #, python-format
 msgid ""
 "I2NP DatabaseStoreMessages containing the local "
@@ -13374,7 +7397,7 @@ msgid ""
 "Destinations to have published LeaseSets at all."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:344
+#: i2p2www/pages/site/docs/how/network-database.html:358
 msgid ""
 "The DatabaseStoreMessage should be sent to the floodfill that is closest\n"
 "to the current routing key for the RouterInfo or LeaseSet being stored.\n"
@@ -13386,7 +7409,7 @@ msgid ""
 "This provides a high degree of fault-tolerance."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:353
+#: i2p2www/pages/site/docs/how/network-database.html:367
 msgid ""
 "In traditional Kademlia, a peer would do a \"find-closest\" search before"
 " inserting\n"
@@ -13407,11 +7430,11 @@ msgid ""
 "the netdb item."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:366
+#: i2p2www/pages/site/docs/how/network-database.html:380
 msgid "RouterInfo Storage to Floodfills"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:367
+#: i2p2www/pages/site/docs/how/network-database.html:381
 #, python-format
 msgid ""
 "A router publishes its own RouterInfo by directly connecting to a "
@@ -13426,18 +7449,18 @@ msgid ""
 "with the Message ID set to the value of the Reply Token."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:381
+#: i2p2www/pages/site/docs/how/network-database.html:395
 msgid "LeaseSet Storage to Floodfills"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:382
+#: i2p2www/pages/site/docs/how/network-database.html:396
 msgid ""
 "Storage of LeaseSets is much more sensitive than for RouterInfos, as a "
 "router\n"
 "must take care that the LeaseSet cannot be associated with the router."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:387
+#: i2p2www/pages/site/docs/how/network-database.html:401
 #, python-format
 msgid ""
 "A router publishes a local LeaseSet by\n"
@@ -13453,18 +7476,19 @@ msgid ""
 "This message is sent back to one of the client's inbound tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:400
+#: i2p2www/pages/site/docs/how/network-database.html:414
 msgid "Flooding"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:401
+#: i2p2www/pages/site/docs/how/network-database.html:415
+#, python-format
 msgid ""
 "After a floodfill router receives a DatabaseStoreMessage containing a\n"
 "valid RouterInfo or LeaseSet which is newer than that previously stored "
 "in its\n"
 "local NetDb, it \"floods\" it.\n"
-"To flood a NetDb entry, it looks up several (currently 4) floodfill "
-"routers closest to the routing key\n"
+"To flood a NetDb entry, it looks up several (currently %(floodsize)s) "
+"floodfill routers closest to the routing key\n"
 "of the NetDb entry. (The routing key is the SHA256 Hash of the "
 "RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n"
 "By flooding to those closest to the key, not closest to itself, the "
@@ -13474,7 +7498,7 @@ msgid ""
 "DHT \"neighborhood\" for the routing key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:412
+#: i2p2www/pages/site/docs/how/network-database.html:426
 #, python-format
 msgid ""
 "The floodfill then directly connects to each of those peers\n"
@@ -13485,11 +7509,11 @@ msgid ""
 "The other routers do not reply or re-flood, as the Reply Token is zero."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:422
+#: i2p2www/pages/site/docs/how/network-database.html:436
 msgid "RouterInfo and LeaseSet Lookup"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:423
+#: i2p2www/pages/site/docs/how/network-database.html:437
 #, python-format
 msgid ""
 "The I2NP DatabaseLookupMessage is used to "
@@ -13499,13 +7523,13 @@ msgid ""
 "exploratory tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:429
+#: i2p2www/pages/site/docs/how/network-database.html:443
 msgid ""
 "Lookups are generally sent to the two \"good\" (the connection doesn't "
 "fail) floodfill routers closest to the requested key, in parallel."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:433
+#: i2p2www/pages/site/docs/how/network-database.html:447
 #, python-format
 msgid ""
 "If the key is found locally by the floodfill router, it responds with a\n"
@@ -13516,7 +7540,7 @@ msgid ""
 "containing a list of other floodfill routers close to the key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:441
+#: i2p2www/pages/site/docs/how/network-database.html:455
 msgid ""
 "LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n"
 "RouterInfo lookups are not encrypted and thus are vulnerable to snooping "
@@ -13526,7 +7550,7 @@ msgid ""
 "RouterInfo lookup encryption may be enabled in a future release."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:448
+#: i2p2www/pages/site/docs/how/network-database.html:462
 msgid ""
 "As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage"
 " or a DatabaseSearchReplyMessage)\n"
@@ -13537,14 +7561,14 @@ msgid ""
 " encryption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:455
+#: i2p2www/pages/site/docs/how/network-database.html:469
 #, python-format
 msgid ""
 "(Reference: Hashing it out in Public Sections "
 "2.2-2.3 for terms below in italics)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:459
+#: i2p2www/pages/site/docs/how/network-database.html:473
 msgid ""
 "Due to the relatively small size of the network and the flooding "
 "redundancy of 8x,\n"
@@ -13560,7 +7584,7 @@ msgid ""
 "to reduce the chance of query failure."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:470
+#: i2p2www/pages/site/docs/how/network-database.html:484
 msgid ""
 "As of release 0.8.9, iterative lookups are implemented with no "
 "lookup redundancy.\n"
@@ -13578,7 +7602,7 @@ msgid ""
 "or the maximum number of peers is queried."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:482
+#: i2p2www/pages/site/docs/how/network-database.html:496
 msgid ""
 "Node IDs are verifiable in that we use the router hash "
 "directly as both the node ID and the Kademlia key.\n"
@@ -13588,11 +7612,21 @@ msgid ""
 "detailed knowledge of the neighborhood of the destination ID space."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:491
+#: i2p2www/pages/site/docs/how/network-database.html:505
 msgid "RouterInfo Storage Verification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:492
+#: i2p2www/pages/site/docs/how/network-database.html:506
+#, python-format
+msgid ""
+"Note: RouterInfo verification is disabled as of release 0.9.7.1 to "
+"prevent\n"
+"the attack described in the paper\n"
+"Practical Attacks Against the I2P Network.\n"
+"It is not clear if verification can be redesigned to be done safely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:513
 msgid ""
 "To verify a storage was successful, a router simply waits about 10 "
 "seconds,\n"
@@ -13603,11 +7637,11 @@ msgid ""
 "outbound endpoint(OBEP)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:500
+#: i2p2www/pages/site/docs/how/network-database.html:521
 msgid "LeaseSet Storage Verification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:501
+#: i2p2www/pages/site/docs/how/network-database.html:522
 msgid ""
 "To verify a storage was successful, a router simply waits about 10 "
 "seconds,\n"
@@ -13621,7 +7655,7 @@ msgid ""
 "tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:511
+#: i2p2www/pages/site/docs/how/network-database.html:532
 msgid ""
 "As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a "
 "DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n"
@@ -13629,11 +7663,11 @@ msgid ""
 "to hide the reply from the inbound gateway (IBGW) of the reply tunnel."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:519
+#: i2p2www/pages/site/docs/how/network-database.html:540
 msgid "Exploration"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:520
+#: i2p2www/pages/site/docs/how/network-database.html:541
 #, python-format
 msgid ""
 "Exploration is a special form of netdb lookup, where a router "
@@ -13656,11 +7690,11 @@ msgid ""
 "the requested key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:534
+#: i2p2www/pages/site/docs/how/network-database.html:555
 msgid "Notes on Lookup Responses"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:535
+#: i2p2www/pages/site/docs/how/network-database.html:556
 msgid ""
 "The response to a lookup request is either a Database Store Message (on "
 "success) or a\n"
@@ -13673,11 +7707,11 @@ msgid ""
 "difficult to monitor the performance of the various floodfill routers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:545
+#: i2p2www/pages/site/docs/how/network-database.html:566
 msgid "MultiHoming"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:547
+#: i2p2www/pages/site/docs/how/network-database.html:568
 msgid ""
 "Destinations may be hosted on multiple routers simultaneously, by using "
 "the same\n"
@@ -13694,18 +7728,18 @@ msgid ""
 "services on the network."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:557
+#: i2p2www/pages/site/docs/how/network-database.html:578
 msgid "Threat Analysis"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:558
+#: i2p2www/pages/site/docs/how/network-database.html:579
 #, python-format
 msgid ""
 "Also discussed on the threat model "
 "page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:562
+#: i2p2www/pages/site/docs/how/network-database.html:583
 msgid ""
 "A hostile user may attempt to harm the network by\n"
 "creating one or more floodfill routers and crafting them to offer\n"
@@ -13713,43 +7747,45 @@ msgid ""
 "Some scenarios are discussed below."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:569
+#: i2p2www/pages/site/docs/how/network-database.html:590
 msgid "General Mitigation Through Growth"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:570
+#: i2p2www/pages/site/docs/how/network-database.html:591
+#, python-format
 msgid ""
-"There are currently hundreds of floodfill routers in the network.\n"
+"There are currently around %(ffcount)s floodfill routers in the network.\n"
 "Most of the following attacks will become more difficult, or have less "
 "impact,\n"
 "as the network size and number of floodfill routers increase."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:577
+#: i2p2www/pages/site/docs/how/network-database.html:598
 msgid "General Mitigation Through Redundancy"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:578
+#: i2p2www/pages/site/docs/how/network-database.html:599
+#, python-format
 msgid ""
-"Via flooding, all netdb entries are stored on the 8 floodfill routers "
-"closest to the key."
+"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill"
+" routers closest to the key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:583
+#: i2p2www/pages/site/docs/how/network-database.html:604
 msgid "Forgeries"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:584
+#: i2p2www/pages/site/docs/how/network-database.html:605
 msgid ""
 "All netdb entries are signed by their creators, so no router may forge a\n"
 "RouterInfo or LeaseSet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:589
+#: i2p2www/pages/site/docs/how/network-database.html:610
 msgid "Slow or Unresponsive"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:590
+#: i2p2www/pages/site/docs/how/network-database.html:611
 #, python-format
 msgid ""
 "Each router maintains an expanded set of statistics in the\n"
@@ -13759,31 +7795,31 @@ msgid ""
 "The set includes:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:597
+#: i2p2www/pages/site/docs/how/network-database.html:618
 msgid "Average response time"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:598
+#: i2p2www/pages/site/docs/how/network-database.html:619
 msgid "Percentage of queries answered with the data requested"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:599
+#: i2p2www/pages/site/docs/how/network-database.html:620
 msgid "Percentage of stores that were successfully verified"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:600
+#: i2p2www/pages/site/docs/how/network-database.html:621
 msgid "Last successful store"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:601
+#: i2p2www/pages/site/docs/how/network-database.html:622
 msgid "Last successful lookup"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:602
+#: i2p2www/pages/site/docs/how/network-database.html:623
 msgid "Last response"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:605
+#: i2p2www/pages/site/docs/how/network-database.html:626
 msgid ""
 "Each time a router needs to make a determination on which floodfill "
 "router is closest to a key,\n"
@@ -13796,11 +7832,11 @@ msgid ""
 "routers that are only sometimes malicious may be much harder to deal with."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:615
+#: i2p2www/pages/site/docs/how/network-database.html:636
 msgid "Sybil Attack (Full Keyspace)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:616
+#: i2p2www/pages/site/docs/how/network-database.html:637
 #, python-format
 msgid ""
 "An attacker may mount a Sybil attack\n"
@@ -13808,7 +7844,7 @@ msgid ""
 "keyspace."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:621
+#: i2p2www/pages/site/docs/how/network-database.html:642
 #, python-format
 msgid ""
 "(In a related example, a researcher recently created a\n"
@@ -13817,7 +7853,7 @@ msgid ""
 "network."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:627
+#: i2p2www/pages/site/docs/how/network-database.html:648
 msgid ""
 "If the floodfills are not sufficiently misbehaving to be marked as "
 "\"bad\" using the peer profile\n"
@@ -13829,7 +7865,7 @@ msgid ""
 "none of them is completely satisfactory:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:635
+#: i2p2www/pages/site/docs/how/network-database.html:656
 msgid ""
 "Compile a list of bad router hashes or IPs, and announce the list through"
 " various means\n"
@@ -13838,30 +7874,30 @@ msgid ""
 "add it to their local \"blacklist\"."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:640
+#: i2p2www/pages/site/docs/how/network-database.html:661
 msgid ""
 "Ask everyone in the network to enable floodfill manually (fight Sybil "
 "with more Sybil)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:641
+#: i2p2www/pages/site/docs/how/network-database.html:662
 msgid "Release a new software version that includes the hardcoded \"bad\" list"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:642
+#: i2p2www/pages/site/docs/how/network-database.html:663
 msgid ""
 "Release a new software version that improves the peer profile metrics and"
 " thresholds,\n"
 "in an attempt to automatically identify the \"bad\" peers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:646
+#: i2p2www/pages/site/docs/how/network-database.html:667
 msgid ""
 "Add software that disqualifies floodfills if too many of them are in a "
 "single IP block"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:647
+#: i2p2www/pages/site/docs/how/network-database.html:668
 msgid ""
 "Implement an automatic subscription-based blacklist controlled by a "
 "single individual or group.\n"
@@ -13873,15 +7909,15 @@ msgid ""
 "or even to completely shutdown or destroy the entire network."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:656
+#: i2p2www/pages/site/docs/how/network-database.html:677
 msgid "This attack becomes more difficult as the network size grows."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:662
+#: i2p2www/pages/site/docs/how/network-database.html:683
 msgid "Sybil Attack (Partial Keyspace)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:663
+#: i2p2www/pages/site/docs/how/network-database.html:684
 #, python-format
 msgid ""
 "An attacker may mount a Sybil attack\n"
@@ -13895,7 +7931,7 @@ msgid ""
 "eepsite, for example."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:672
+#: i2p2www/pages/site/docs/how/network-database.html:693
 msgid ""
 "As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,"
 "\n"
@@ -13907,7 +7943,7 @@ msgid ""
 "size, is unknown."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:680
+#: i2p2www/pages/site/docs/how/network-database.html:701
 msgid ""
 "As a partial defense against this attack,\n"
 "the algorithm used to determine Kademlia \"closeness\" varies over time.\n"
@@ -13924,7 +7960,7 @@ msgid ""
 "to the target key, or to each other."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:692
+#: i2p2www/pages/site/docs/how/network-database.html:713
 msgid ""
 "This attack becomes more difficult as the network size grows.\n"
 "However, recent research demonstrates that the keyspace rotation is not "
@@ -13934,8 +7970,7 @@ msgid ""
 "of the keyspace within a half hour after rotation."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:700
-#: i2p2www/pages/site/docs/how/network-database.html:709
+#: i2p2www/pages/site/docs/how/network-database.html:721
 msgid ""
 "One consequence of daily keyspace rotation is that the distributed "
 "network database\n"
@@ -13947,11 +7982,11 @@ msgid ""
 "are a topic for further study."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:719
+#: i2p2www/pages/site/docs/how/network-database.html:731
 msgid "Bootstrap Attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:720
+#: i2p2www/pages/site/docs/how/network-database.html:732
 msgid ""
 "An attacker could attempt to boot new routers into an isolated\n"
 "or majority-controlled network by taking over a reseed website,\n"
@@ -13959,38 +7994,38 @@ msgid ""
 "to the hardcoded list in the router."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:727
+#: i2p2www/pages/site/docs/how/network-database.html:739
 msgid "Several defenses are possible, and most of these are planned:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:731
+#: i2p2www/pages/site/docs/how/network-database.html:743
 msgid ""
 "Disallow fallback from HTTPS to HTTP for reseeding.\n"
 "A MITM attacker could simply block HTTPS, then respond to the HTTP."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:735
+#: i2p2www/pages/site/docs/how/network-database.html:747
 msgid ""
 "Changing the reseed task to fetch a subset of RouterInfos from\n"
 "each of several reseed sites rather than using only a single site"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:739
+#: i2p2www/pages/site/docs/how/network-database.html:751
 msgid ""
 "Creating an out-of-network reseed monitoring service that\n"
 "periodically polls reseed websites and verifies that the\n"
 "data are not stale or inconsistent with other views of the network"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:744
+#: i2p2www/pages/site/docs/how/network-database.html:756
 msgid "Bundling reseed data in the installer"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:747
+#: i2p2www/pages/site/docs/how/network-database.html:759
 msgid "Query Capture"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:748
+#: i2p2www/pages/site/docs/how/network-database.html:760
 #, python-format
 msgid ""
 "See also lookup\n"
@@ -13998,7 +8033,7 @@ msgid ""
 "2.2-2.3 for terms below in italics)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:753
+#: i2p2www/pages/site/docs/how/network-database.html:765
 msgid ""
 "Similar to a bootstrap attack, an attacker using a floodfill router could"
 " attempt to \"steer\"\n"
@@ -14006,7 +8041,7 @@ msgid ""
 "references."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:758
+#: i2p2www/pages/site/docs/how/network-database.html:770
 msgid ""
 "This is unlikely to work via exploration, because exploration is a low-"
 "frequency task.\n"
@@ -14016,7 +8051,7 @@ msgid ""
 "and each exploration query is directed to a random floodfill router."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:765
+#: i2p2www/pages/site/docs/how/network-database.html:777
 #, python-format
 msgid ""
 "As of release 0.8.9, iterative lookups are implemented.\n"
@@ -14041,16 +8076,16 @@ msgid ""
 "is much more difficult."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:784
+#: i2p2www/pages/site/docs/how/network-database.html:796
 msgid "DHT-Based Relay Selection"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:785
+#: i2p2www/pages/site/docs/how/network-database.html:797
 #, python-format
 msgid "(Reference: Hashing it out in Public Section 3)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:789
+#: i2p2www/pages/site/docs/how/network-database.html:801
 #, python-format
 msgid ""
 "This doesn't have much to do with floodfill, but see\n"
@@ -14058,18 +8093,18 @@ msgid ""
 "for a discussion of the vulnerabilities of peer selection for tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:795
+#: i2p2www/pages/site/docs/how/network-database.html:807
 msgid "Information Leaks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:796
+#: i2p2www/pages/site/docs/how/network-database.html:808
 #, python-format
 msgid ""
 "(Reference: In Search of an Anonymous and Secure "
 "Lookup Section 3)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:800
+#: i2p2www/pages/site/docs/how/network-database.html:812
 #, python-format
 msgid ""
 "This paper addresses weaknesses in the \"Finger Table\" DHT lookups used "
@@ -14086,7 +8121,7 @@ msgid ""
 "Also, peer selection is unrelated to any notion of DHT key-closeness."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:811
+#: i2p2www/pages/site/docs/how/network-database.html:823
 msgid ""
 "Some of this may actually be more interesting when the I2P network gets "
 "much larger.\n"
@@ -14100,14 +8135,14 @@ msgid ""
 "much harder."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:819
+#: i2p2www/pages/site/docs/how/network-database.html:831
 #, python-format
 msgid ""
 "However, the general issue of DHT information leakage in I2P needs "
 "further investigation.\n"
 "The floodfill routers are in a position to observe queries and gather "
 "information.\n"
-"Certainly, at a level of f = 0.2 (20%% malicious nodes, as "
+"Certainly, at a level of f = 0.2 (20% malicious nodes, as "
 "specifed in the paper)\n"
 "we expect that many of the Sybil threats we describe\n"
 "(here,\n"
@@ -14116,15 +8151,15 @@ msgid ""
 "become problematic for several reasons."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:833
+#: i2p2www/pages/site/docs/how/network-database.html:845
 msgid "Moved to the netdb discussion page"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:837
+#: i2p2www/pages/site/docs/how/network-database.html:849
 msgid "End-to-end encryption of additional netDb lookups and responses."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:841
+#: i2p2www/pages/site/docs/how/network-database.html:853
 msgid "Better methods for tracking lookup responses."
 msgstr ""
 
@@ -14488,10 +8523,9 @@ msgid "Two peers from the same /16 IP space may not be in the same tunnel."
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:239
-#, python-format
 msgid ""
-"A peer may participate in a maximum of 33% of all tunnels created by the "
-"router."
+"A peer may participate in a maximum of 33% of all tunnels created by "
+"the router."
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:242
@@ -14594,7 +8628,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/how/tech-intro.html:9
 #: i2p2www/pages/site/docs/how/tech-intro.html:24
-#: i2p2www/pages/site/docs/transport/ssu.html:278
+#: i2p2www/pages/site/docs/transport/ssu.html:281
 msgid "Introduction"
 msgstr ""
 
@@ -14607,6 +8641,11 @@ msgstr ""
 msgid "Transport protocols"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tech-intro.html:17
+#: i2p2www/pages/site/docs/how/tech-intro.html:458
+msgid "Cryptography"
+msgstr "Kryptographie"
+
 #: i2p2www/pages/site/docs/how/tech-intro.html:25
 msgid ""
 "I2P is a scalable, self organizing, resilient packet switched anonymous \n"
@@ -15925,6 +9964,10 @@ msgid ""
 "network applications provide further functionality for end users."
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tech-intro.html:808
+msgid "Streaming library"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/tech-intro.html:809
 msgid ""
 "The I2P streaming library can be viewed as a generic streaming interface "
@@ -16254,8 +10297,7 @@ msgstr ""
 #, python-format
 msgid ""
 "PyBit is a Bittorrent client written in Python.\n"
-"It is hosted on http://%(pebcache)s/"
-" "
+"It is hosted on %(pybit)s "
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/tech-intro.html:1015
@@ -16344,11 +10386,52 @@ msgstr ""
 msgid "November 2010"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:6
-msgid "What do we mean by \"anonymous\"?"
+#: i2p2www/pages/site/docs/how/threat-model.html:7
+msgid "low"
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/threat-model.html:8
+msgid "medium"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:9
+msgid "high"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:34
+msgid "Damage Potential"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:35
+msgid "Reliability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:36
+msgid "Exploitability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:37
+msgid "Affected Users"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:38
+msgid "Discoverability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:39
+msgid "Severity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:40
+#: i2p2www/pages/site/docs/protocol/i2np.html:94
+msgid "Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:45
+msgid "What do we mean by \"anonymous\"?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:47
 msgid ""
 "Your level of anonymity can be described as \"how hard it is for someone\n"
 "to find out information you don't want them to know?\" - who you are, "
@@ -16366,7 +10449,7 @@ msgid ""
 "data, to those fearful of discovery by powerful organizations or states."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:19
+#: i2p2www/pages/site/docs/how/threat-model.html:58
 msgid ""
 "The question of whether I2P provides sufficient anonymity for your \n"
 "particular needs is a hard one, but this page will hopefully assist in \n"
@@ -16375,7 +10458,7 @@ msgid ""
 "so that you may decide whether it meets your needs."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:26
+#: i2p2www/pages/site/docs/how/threat-model.html:65
 msgid ""
 "We welcome further research and analysis on I2P's resistance to the "
 "threats described below.\n"
@@ -16384,11 +10467,11 @@ msgid ""
 "work focused on I2P is needed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:32
+#: i2p2www/pages/site/docs/how/threat-model.html:71
 msgid "Network Topology Summary"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:33
+#: i2p2www/pages/site/docs/how/threat-model.html:72
 #, python-format
 msgid ""
 "I2P builds off the ideas of many other \n"
@@ -16397,7 +10480,7 @@ msgid ""
 "reviewing related literature:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:39
+#: i2p2www/pages/site/docs/how/threat-model.html:78
 msgid ""
 "I2P is a free route mixnet - the message creator explicitly "
 "defines the\n"
@@ -16408,7 +10491,7 @@ msgid ""
 "inbound tunnel)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:45
+#: i2p2www/pages/site/docs/how/threat-model.html:84
 msgid ""
 "I2P has no official entry and exit points - all peers fully "
 "participate in the \n"
@@ -16416,7 +10499,7 @@ msgid ""
 "application layer, a few proxies do exist)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:50
+#: i2p2www/pages/site/docs/how/threat-model.html:89
 msgid ""
 "I2P is fully distributed - there are no central controls or "
 "authorities.\n"
@@ -16431,7 +10514,7 @@ msgid ""
 "anonymity)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:60
+#: i2p2www/pages/site/docs/how/threat-model.html:99
 #, python-format
 msgid ""
 "We have documented plans to implement [Onion Routing],\n"
 "[Freenet], and\n"
-"[Tor].\n"
+"[Tor].\n"
 "Our design benefits substantially from the research published around that"
 " time.\n"
 "I2P uses several onion routing techniques, so we continue to benefit\n"
 "from the significant academic interest in Tor."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:89
+#: i2p2www/pages/site/docs/how/threat-model.html:128
 msgid ""
 "Taking from the attacks and analysis put forth in the \n"
 "anonymity "
@@ -16487,14 +10570,14 @@ msgid ""
 "this list to include new attacks as they are identified."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:98
+#: i2p2www/pages/site/docs/how/threat-model.html:137
 msgid ""
 "Included are some attacks that may be unique to I2P.\n"
 "We do not have good answers for all these attacks, however\n"
 "we continue to do research and improve our defenses."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:104
+#: i2p2www/pages/site/docs/how/threat-model.html:143
 msgid ""
 "In addition, many of these attacks are significantly easier than\n"
 "they should be, due to the modest size of the current network.\n"
@@ -16505,7 +10588,7 @@ msgid ""
 "these attacks will become much harder."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:114
+#: i2p2www/pages/site/docs/how/threat-model.html:153
 #, python-format
 msgid ""
 "The\n"
@@ -16515,94 +10598,98 @@ msgid ""
 "to review."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:123
-#: i2p2www/pages/site/docs/how/threat-model.html:143
+#: i2p2www/pages/site/docs/how/threat-model.html:182
+msgid "Index of Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:184
+#: i2p2www/pages/site/docs/how/threat-model.html:204
 msgid "Brute force attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:124
 #: i2p2www/pages/site/docs/how/threat-model.html:185
+#: i2p2www/pages/site/docs/how/threat-model.html:248
 msgid "Timing attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:125
-#: i2p2www/pages/site/docs/how/threat-model.html:220
+#: i2p2www/pages/site/docs/how/threat-model.html:186
+#: i2p2www/pages/site/docs/how/threat-model.html:285
 msgid "Intersection attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:126
-#: i2p2www/pages/site/docs/how/threat-model.html:298
+#: i2p2www/pages/site/docs/how/threat-model.html:187
+#: i2p2www/pages/site/docs/how/threat-model.html:365
 msgid "Denial of service attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:127
-#: i2p2www/pages/site/docs/how/threat-model.html:385
+#: i2p2www/pages/site/docs/how/threat-model.html:188
+#: i2p2www/pages/site/docs/how/threat-model.html:464
 msgid "Tagging attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:128
-#: i2p2www/pages/site/docs/how/threat-model.html:400
+#: i2p2www/pages/site/docs/how/threat-model.html:189
+#: i2p2www/pages/site/docs/how/threat-model.html:482
 msgid "Partitioning attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:129
-#: i2p2www/pages/site/docs/how/threat-model.html:438
+#: i2p2www/pages/site/docs/how/threat-model.html:190
+#: i2p2www/pages/site/docs/how/threat-model.html:522
 msgid "Predecessor attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:130
-#: i2p2www/pages/site/docs/how/threat-model.html:481
+#: i2p2www/pages/site/docs/how/threat-model.html:191
+#: i2p2www/pages/site/docs/how/threat-model.html:567
 msgid "Harvesting attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:131
-#: i2p2www/pages/site/docs/how/threat-model.html:525
+#: i2p2www/pages/site/docs/how/threat-model.html:192
+#: i2p2www/pages/site/docs/how/threat-model.html:614
 msgid "Identification Through Traffic Analysis"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:132
-#: i2p2www/pages/site/docs/how/threat-model.html:582
+#: i2p2www/pages/site/docs/how/threat-model.html:193
+#: i2p2www/pages/site/docs/how/threat-model.html:674
 msgid "Sybil attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:133
-#: i2p2www/pages/site/docs/how/threat-model.html:629
+#: i2p2www/pages/site/docs/how/threat-model.html:194
+#: i2p2www/pages/site/docs/how/threat-model.html:723
 msgid "Buddy Exhaustion attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:134
-#: i2p2www/pages/site/docs/how/threat-model.html:651
+#: i2p2www/pages/site/docs/how/threat-model.html:195
+#: i2p2www/pages/site/docs/how/threat-model.html:748
 msgid "Cryptographic attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:135
+#: i2p2www/pages/site/docs/how/threat-model.html:196
 msgid "Floodfill attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:136
-#: i2p2www/pages/site/docs/how/threat-model.html:707
+#: i2p2www/pages/site/docs/how/threat-model.html:197
+#: i2p2www/pages/site/docs/how/threat-model.html:809
 msgid "Other Network Database attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:137
+#: i2p2www/pages/site/docs/how/threat-model.html:198
 msgid "Attacks on centralized resources"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:138
-#: i2p2www/pages/site/docs/how/threat-model.html:770
+#: i2p2www/pages/site/docs/how/threat-model.html:199
+#: i2p2www/pages/site/docs/how/threat-model.html:875
 msgid "Development attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:139
+#: i2p2www/pages/site/docs/how/threat-model.html:200
 msgid "Implementation attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:140
-#: i2p2www/pages/site/docs/how/threat-model.html:849
+#: i2p2www/pages/site/docs/how/threat-model.html:201
+#: i2p2www/pages/site/docs/how/threat-model.html:959
 msgid "Other Defenses"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:145
+#: i2p2www/pages/site/docs/how/threat-model.html:208
 msgid ""
 "A brute force attack can be mounted by a global passive or active "
 "adversary, \n"
@@ -16623,7 +10710,7 @@ msgid ""
 "message)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:157
+#: i2p2www/pages/site/docs/how/threat-model.html:220
 msgid ""
 "However, a powerful attacker can use brute force to detect trends - if "
 "they \n"
@@ -16650,7 +10737,7 @@ msgid ""
 "not currently implemented."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:174
+#: i2p2www/pages/site/docs/how/threat-model.html:237
 #, python-format
 msgid ""
 "As a partial defense against a single router or group of routers trying "
@@ -16663,7 +10750,7 @@ msgid ""
 "peer selection page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:187
+#: i2p2www/pages/site/docs/how/threat-model.html:252
 msgid ""
 "I2P's messages are unidirectional and do not necessarily imply that a "
 "reply\n"
@@ -16679,7 +10766,7 @@ msgid ""
 "slow to have passed the message along."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:197
+#: i2p2www/pages/site/docs/how/threat-model.html:262
 msgid ""
 "This sort of attack is powerful, but its applicability to I2P is non "
 "obvious,\n"
@@ -16697,7 +10784,7 @@ msgid ""
 "DataMessage+DeliveryStatusMessage)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:207
+#: i2p2www/pages/site/docs/how/threat-model.html:272
 #, python-format
 msgid ""
 "Without protocol scrubbing or higher latency, global active adversaries "
@@ -16713,14 +10800,14 @@ msgid ""
 "but these are unimplemented in I2P."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:216
+#: i2p2www/pages/site/docs/how/threat-model.html:281
 #, python-format
 msgid ""
 "References: Low-Resource Routing Attacks Against "
 "Anonymous Systems"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:222
+#: i2p2www/pages/site/docs/how/threat-model.html:289
 msgid ""
 "Intersection attacks against low latency systems are extremely powerful -"
 "\n"
@@ -16736,7 +10823,7 @@ msgid ""
 "scenarios."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:232
+#: i2p2www/pages/site/docs/how/threat-model.html:299
 #, python-format
 msgid ""
 "In summary, if an attacker is at both ends of your tunnel at the same "
@@ -16747,61 +10834,61 @@ msgid ""
 "Tor provides a similar disclaimer."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:240
+#: i2p2www/pages/site/docs/how/threat-model.html:307
 msgid "Partial defenses implemented in I2P:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:244
+#: i2p2www/pages/site/docs/how/threat-model.html:311
 #, python-format
 msgid "strict ordering of peers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:247
+#: i2p2www/pages/site/docs/how/threat-model.html:314
 #, python-format
 msgid ""
 "peer profiling and selection from a "
 "small group that changes slowly"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:250
+#: i2p2www/pages/site/docs/how/threat-model.html:317
 msgid "Limits on the number of tunnels routed through a single peer"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:253
+#: i2p2www/pages/site/docs/how/threat-model.html:320
 msgid ""
 "Prevention of peers from the same /16 IP range from being members of a "
 "single tunnel"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:256
+#: i2p2www/pages/site/docs/how/threat-model.html:323
 msgid ""
 "For eepsites or other hosted services, we support\n"
 "simultaneous hosting on multiple routers, or\n"
 "multihoming"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:263
+#: i2p2www/pages/site/docs/how/threat-model.html:330
 msgid ""
 "Even in total, these defenses are not a complete solution.\n"
 "Also, we have made some design choices that may significantly increase "
 "our vulnerability:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:268
+#: i2p2www/pages/site/docs/how/threat-model.html:335
 msgid "We do not use low-bandwidth \"guard nodes\""
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:271
+#: i2p2www/pages/site/docs/how/threat-model.html:338
 msgid ""
 "We use tunnel pools comprised of several tunnels, and traffic can shift "
 "from tunnel to tunnel."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:274
+#: i2p2www/pages/site/docs/how/threat-model.html:341
 msgid "Tunnels are not long-lived; new tunnels are built every 10 minutes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:277
+#: i2p2www/pages/site/docs/how/threat-model.html:344
 msgid ""
 "Tunnel lengths are configurable.\n"
 "While 3-hop tunnels are recommended for full protection, several "
@@ -16809,7 +10896,7 @@ msgid ""
 "services use 2-hop tunnels by default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:284
+#: i2p2www/pages/site/docs/how/threat-model.html:351
 #, python-format
 msgid ""
 "In the future, it could\n"
@@ -16824,35 +10911,35 @@ msgid ""
 "as an adversary can't \"ping\" them to mount the attack.
            "
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:293
+#: i2p2www/pages/site/docs/how/threat-model.html:360
 #, python-format
 msgid "Reference: One Cell Enough"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:300
+#: i2p2www/pages/site/docs/how/threat-model.html:367
 msgid ""
 "There are a whole slew of denial of service attacks available against "
 "I2P,\n"
 "each with different costs and consequences:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:305
+#: i2p2www/pages/site/docs/how/threat-model.html:373
 msgid ""
 "Greedy user attack: This is simply\n"
 "people trying to consume significantly more resources than they are \n"
 "willing to contribute. The defense against this is:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:311
+#: i2p2www/pages/site/docs/how/threat-model.html:379
 #, python-format
 msgid ""
 "Set defaults so that most users provide resources to the network.\n"
 "In I2P, users route traffic by default. In sharp distinction to\n"
 "other networks,\n"
-"over 95%% of I2P users relay traffic for others."
+"over 95% of I2P users relay traffic for others."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:317
+#: i2p2www/pages/site/docs/how/threat-model.html:385
 msgid ""
 "Provide easy configuration options so that users may increase their\n"
 "contribution (share percentage) to the network. Display easy-to-"
@@ -16861,13 +10948,13 @@ msgid ""
 "contributing."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:322
+#: i2p2www/pages/site/docs/how/threat-model.html:390
 msgid ""
 "Maintain a strong community with blogs, forums, IRC, and other means of "
 "communication."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:327
+#: i2p2www/pages/site/docs/how/threat-model.html:397
 #, python-format
 msgid ""
 "Starvation attack: A hostile user may attempt to harm the network "
@@ -16896,7 +10983,7 @@ msgid ""
 "significant efforts required in this area."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:344
+#: i2p2www/pages/site/docs/how/threat-model.html:417
 #, python-format
 msgid ""
 "Flooding attack: A hostile user may attempt to flood the network,\n"
@@ -16927,7 +11014,7 @@ msgid ""
 "operation is implemented)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:360
+#: i2p2www/pages/site/docs/how/threat-model.html:436
 msgid ""
 "CPU load attack: There are currently some methods for people to \n"
 "remotely request that a peer perform some cryptographically expensive \n"
@@ -16942,7 +11029,7 @@ msgid ""
 "bugs in the implementation."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:370
+#: i2p2www/pages/site/docs/how/threat-model.html:449
 #, python-format
 msgid ""
 "Floodfill DOS attack: A hostile user may attempt to harm the "
@@ -16958,7 +11045,7 @@ msgid ""
 "network database page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:386
+#: i2p2www/pages/site/docs/how/threat-model.html:468
 #, python-format
 msgid ""
 "Tagging attacks - modifying a message so that it can later be identified"
@@ -16984,7 +11071,7 @@ msgid ""
 "as the links are encrypted and messages signed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:402
+#: i2p2www/pages/site/docs/how/threat-model.html:486
 msgid ""
 "Partitioning attacks - finding ways to segregate (technically or "
 "analytically)\n"
@@ -17013,7 +11100,7 @@ msgid ""
 "the moment)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:418
+#: i2p2www/pages/site/docs/how/threat-model.html:502
 #, python-format
 msgid ""
 "Partitioning the network analytically by looking for differences in how "
@@ -17043,14 +11130,14 @@ msgid ""
 "which other tunnels or messages have those delays)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:434
+#: i2p2www/pages/site/docs/how/threat-model.html:518
 #, python-format
 msgid ""
 "Also discussed on the network database "
 "page (bootstrap attack)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:440
+#: i2p2www/pages/site/docs/how/threat-model.html:526
 msgid ""
 "The predecessor attack is passively gathering statistics in an attempt to"
 " see\n"
@@ -17067,7 +11154,7 @@ msgid ""
 "target is located."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:450
+#: i2p2www/pages/site/docs/how/threat-model.html:536
 #, python-format
 msgid ""
 "I2P avoids this in four ways: first, the peers selected to participate in"
@@ -17092,7 +11179,7 @@ msgid ""
 "attackers will merely run into that gateway."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:467
+#: i2p2www/pages/site/docs/how/threat-model.html:553
 #, python-format
 msgid ""
 "The current tunnel build method\n"
@@ -17100,7 +11187,7 @@ msgid ""
 "See also the intersection attack."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:473
+#: i2p2www/pages/site/docs/how/threat-model.html:559
 #, python-format
 msgid ""
 "References: %(pdf2008)s\n"
@@ -17108,7 +11195,7 @@ msgid ""
 "%(pdf2004)s."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:482
+#: i2p2www/pages/site/docs/how/threat-model.html:571
 msgid ""
 "\"Harvesting\" means compiling a list of users running I2P.\n"
 "It can be used for legal attacks and to help\n"
@@ -17116,7 +11203,7 @@ msgid ""
 "harvesting whatever references to other peers it can find."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:489
+#: i2p2www/pages/site/docs/how/threat-model.html:578
 msgid ""
 "I2P itself is not designed with effective defenses against\n"
 "this attack, since there is the distributed network database \n"
@@ -17124,17 +11211,17 @@ msgid ""
 "The following factors make the attack somewhat harder in practice:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:496
+#: i2p2www/pages/site/docs/how/threat-model.html:585
 msgid ""
 "Network growth will make it more difficult to obtain a given proportion "
 "of the network"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:499
+#: i2p2www/pages/site/docs/how/threat-model.html:588
 msgid "Floodfill routers implement query limits as DOS protection"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:502
+#: i2p2www/pages/site/docs/how/threat-model.html:591
 msgid ""
 "\"Hidden mode\", which prevents a router from publishing its information "
 "to the netDb,\n"
@@ -17142,7 +11229,7 @@ msgid ""
 "could be."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:508
+#: i2p2www/pages/site/docs/how/threat-model.html:597
 #, python-format
 msgid ""
 "In future implementations,\n"
@@ -17156,7 +11243,7 @@ msgid ""
 "they can be reached (as well as their public keys, etc)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:517
+#: i2p2www/pages/site/docs/how/threat-model.html:606
 msgid ""
 "In the future, routers could use GeoIP to identify if they are in a "
 "particular\n"
@@ -17165,7 +11252,7 @@ msgid ""
 "enact other restricted route methods."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:526
+#: i2p2www/pages/site/docs/how/threat-model.html:618
 #, python-format
 msgid ""
 "By inspecting the traffic into and out of a router, a malicious ISP\n"
@@ -17179,21 +11266,21 @@ msgid ""
 "make it somewhat difficult to identify I2P traffic:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:536
+#: i2p2www/pages/site/docs/how/threat-model.html:628
 msgid "Random port selection"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:539
+#: i2p2www/pages/site/docs/how/threat-model.html:631
 msgid "Point-to-Point Encryption of all traffic"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:542
+#: i2p2www/pages/site/docs/how/threat-model.html:634
 msgid ""
 "DH key exchange with no protocol bytes or other unencrypted constant "
 "fields"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:545
+#: i2p2www/pages/site/docs/how/threat-model.html:637
 #, python-format
 msgid ""
 "Simultaneous use of both\n"
@@ -17203,62 +11290,61 @@ msgid ""
 " track."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:553
+#: i2p2www/pages/site/docs/how/threat-model.html:645
 msgid ""
 "In the near future, we plan to directly address traffic analysis issues "
 "by further obfuscation of I2P transport protocols, possibly including:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:557
+#: i2p2www/pages/site/docs/how/threat-model.html:649
 msgid ""
 "Padding at the transport layer to random lengths, especially during the "
 "connection handshake"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:560
+#: i2p2www/pages/site/docs/how/threat-model.html:652
 msgid ""
 "Study of packet size distribution signatures, and additional padding as "
 "necessary"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:563
+#: i2p2www/pages/site/docs/how/threat-model.html:655
 msgid ""
 "Development of additional transport methods that mimic SSL or other "
 "common protocols"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:566
+#: i2p2www/pages/site/docs/how/threat-model.html:658
 msgid ""
 "Review of padding strategies at higher layers to see how they affect "
 "packet sizes at the transport layer"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:569
+#: i2p2www/pages/site/docs/how/threat-model.html:661
 msgid ""
 "Review of methods implemented by various state-level firewalls to block "
 "Tor"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:572
+#: i2p2www/pages/site/docs/how/threat-model.html:664
 msgid "Working directly with DPI and obfuscation experts"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:577
+#: i2p2www/pages/site/docs/how/threat-model.html:669
 #, python-format
 msgid ""
 "Reference: Breaking and Improving Protocol "
 "Obfuscation"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:584
-#, python-format
+#: i2p2www/pages/site/docs/how/threat-model.html:678
 msgid ""
 "Sybil describes a category of attacks where the adversary creates "
 "arbitrarily\n"
 "large numbers of colluding nodes and uses the increased numbers to help \n"
 "mounting other attacks.  For instance, if an attacker is in a network "
 "where peers\n"
-"are selected randomly and they want an 80% chance to be one of those "
+"are selected randomly and they want an 80% chance to be one of those "
 "peers, they\n"
 "simply create five times the number of nodes that are in the network and "
 "roll \n"
@@ -17281,15 +11367,15 @@ msgid ""
 "scarcity)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:602
+#: i2p2www/pages/site/docs/how/threat-model.html:696
 msgid "Requiring HashCash Certificates in various places has two major problems:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:606
+#: i2p2www/pages/site/docs/how/threat-model.html:700
 msgid "Maintaining backward compatibility"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:609
+#: i2p2www/pages/site/docs/how/threat-model.html:703
 msgid ""
 "The classic HashCash problem -\n"
 "selecting HashCash values that are meaningful proofs of work on high-end "
@@ -17297,7 +11383,7 @@ msgid ""
 "while still being feasible on low-end machines such as mobile devices."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:616
+#: i2p2www/pages/site/docs/how/threat-model.html:710
 msgid ""
 "Various limitations on the number of routers in a given IP range restrict"
 "\n"
@@ -17307,21 +11393,21 @@ msgid ""
 "However, this is not a meaningful defense against a powerful adversary."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:623
+#: i2p2www/pages/site/docs/how/threat-model.html:717
 #, python-format
 msgid ""
 "See the network database page\n"
 "for more Sybil discussion."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:630
+#: i2p2www/pages/site/docs/how/threat-model.html:727
 #, python-format
 msgid ""
 "(Reference: In Search of an Anonymouns and Secure "
 "Lookup Section 5.2)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:634
+#: i2p2www/pages/site/docs/how/threat-model.html:731
 #, python-format
 msgid ""
 "By refusing to accept or forward tunnel build requests, except to a "
@@ -17335,7 +11421,7 @@ msgid ""
 "the performance\n"
 "of peers.\n"
 "However, this is a powerful attack as the number of routers approaches\n"
-"f = 0.2, or 20%% malicious nodes, as specifed in the paper.\n"
+"f = 0.2, or 20% malicious nodes, as specifed in the paper.\n"
 "The malicous routers could also maintain connections to the target router"
 " and provide\n"
 "excellent forwarding bandwidth for traffic over those connections, in an "
@@ -17344,7 +11430,7 @@ msgid ""
 "Further research and defenses may be necessary."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:653
+#: i2p2www/pages/site/docs/how/threat-model.html:752
 #, python-format
 msgid ""
 "We use strong cryptography with long keys, and\n"
@@ -17372,7 +11458,7 @@ msgid ""
 "shared secret values while maintaining backward compatibility."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:672
+#: i2p2www/pages/site/docs/how/threat-model.html:771
 #, python-format
 msgid ""
 "Upgrading the various data structures and protocols to support longer "
@@ -17385,7 +11471,7 @@ msgid ""
 "implement mechanisms to make it easier for future transitions."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:681
+#: i2p2www/pages/site/docs/how/threat-model.html:780
 msgid ""
 "In the future, several I2P protocols and data structures\n"
 "support securely padding messages to arbitrary sizes, so messages could "
@@ -17397,11 +11483,11 @@ msgid ""
 "end to end messages include simple random padding."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:691
+#: i2p2www/pages/site/docs/how/threat-model.html:790
 msgid "Floodfill Anonymity attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:692
+#: i2p2www/pages/site/docs/how/threat-model.html:794
 #, python-format
 msgid ""
 "In addition to the floodfill DOS attacks described\n"
@@ -17421,7 +11507,7 @@ msgid ""
 " future research."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:708
+#: i2p2www/pages/site/docs/how/threat-model.html:810
 #, python-format
 msgid ""
 "A hostile user may attempt to harm the network by\n"
@@ -17431,11 +11517,11 @@ msgid ""
 "network database page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:718
+#: i2p2www/pages/site/docs/how/threat-model.html:820
 msgid "Central Resource Attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:719
+#: i2p2www/pages/site/docs/how/threat-model.html:824
 msgid ""
 "There are a few centralized or limited resources (some inside I2P, some "
 "not)\n"
@@ -17450,14 +11536,14 @@ msgid ""
 "not the operation of the network itself."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:729
+#: i2p2www/pages/site/docs/how/threat-model.html:834
 #, python-format
 msgid ""
 "The website is mirrored and uses DNS round-robin"
 " for external public access."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:732
+#: i2p2www/pages/site/docs/how/threat-model.html:837
 #, python-format
 msgid ""
 "Routers now support multiple external reseed "
@@ -17467,17 +11553,17 @@ msgid ""
 "reseed hosts may need improvement."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:737
+#: i2p2www/pages/site/docs/how/threat-model.html:842
 msgid ""
 "Routers now support multiple update file locations.\n"
 "A malicious update host could feed a huge file, need to limit the size."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:741
+#: i2p2www/pages/site/docs/how/threat-model.html:846
 msgid "Routers now support multiple default trusted update signers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:744
+#: i2p2www/pages/site/docs/how/threat-model.html:849
 msgid ""
 "Routers now better handle multiple unreliable "
 "floodfill peers.\n"
@@ -17485,21 +11571,21 @@ msgid ""
 "href=\"#floodfill\">more study."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:748
+#: i2p2www/pages/site/docs/how/threat-model.html:853
 #, python-format
 msgid ""
 "The code is now stored in a distributed source "
 "control system."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:751
+#: i2p2www/pages/site/docs/how/threat-model.html:856
 msgid ""
 "Routers rely on a single news host, but there is a hardcoded backup URL "
 "pointing to a different host.\n"
 "A malicious news host could feed a huge file, need to limit the size."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:755
+#: i2p2www/pages/site/docs/how/threat-model.html:860
 #, python-format
 msgid ""
 "Naming system services, including addressbook "
@@ -17512,7 +11598,7 @@ msgid ""
 "the naming page for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:762
+#: i2p2www/pages/site/docs/how/threat-model.html:867
 msgid ""
 "We remain reliant on the DNS service for i2p2.de, losing this would cause"
 " substantial\n"
@@ -17521,7 +11607,7 @@ msgid ""
 "loss of i2p.net did."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:772
+#: i2p2www/pages/site/docs/how/threat-model.html:879
 msgid ""
 "These attacks aren't directly on the network, but instead go after its "
 "development team \n"
@@ -17537,11 +11623,11 @@ msgid ""
 "have a big problem."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:781
+#: i2p2www/pages/site/docs/how/threat-model.html:888
 msgid "However, two techniques help defend against these attacks:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:785
+#: i2p2www/pages/site/docs/how/threat-model.html:892
 #, python-format
 msgid ""
 "All components of the network must be open source to enable inspection, "
@@ -17557,7 +11643,7 @@ msgid ""
 "to restrict modifications to those previously approved."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:793
+#: i2p2www/pages/site/docs/how/threat-model.html:900
 #, python-format
 msgid ""
 "Development over the network itself, allowing developers to stay "
@@ -17571,18 +11657,18 @@ msgid ""
 "all available within I2P."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:804
+#: i2p2www/pages/site/docs/how/threat-model.html:911
 msgid ""
 "We also maintain relationships with various organizations that offer "
 "legal advice,\n"
 "should any defense be necessary."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:809
+#: i2p2www/pages/site/docs/how/threat-model.html:916
 msgid "Implementation attacks (bugs)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:810
+#: i2p2www/pages/site/docs/how/threat-model.html:920
 msgid ""
 "Try as we might, most nontrivial applications include errors in the "
 "design or \n"
@@ -17599,7 +11685,7 @@ msgid ""
 "obscurity."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:821
+#: i2p2www/pages/site/docs/how/threat-model.html:931
 msgid ""
 "In addition, the code is being \n"
 "treated the same way, with little aversion towards reworking or throwing "
@@ -17615,7 +11701,7 @@ msgid ""
 "enough to identify shortcomings and bugs."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:831
+#: i2p2www/pages/site/docs/how/threat-model.html:941
 msgid ""
 "Our software is likely, in particular, to contain bugs related to denial "
 "of service\n"
@@ -17625,7 +11711,7 @@ msgid ""
 "protocols."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:837
+#: i2p2www/pages/site/docs/how/threat-model.html:947
 #, python-format
 msgid ""
 "I2P is still a small network with a small development community and "
@@ -17637,11 +11723,11 @@ msgid ""
 "get involved and help."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:850
+#: i2p2www/pages/site/docs/how/threat-model.html:960
 msgid "Blocklists"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:851
+#: i2p2www/pages/site/docs/how/threat-model.html:961
 msgid ""
 "To some extent, I2P could be enhanced to avoid peers operating at IP "
 "addresses\n"
@@ -17651,7 +11737,7 @@ msgid ""
 "others."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:857
+#: i2p2www/pages/site/docs/how/threat-model.html:967
 msgid ""
 "To the extent that active peers actually do show up in the actual "
 "blocklist,\n"
@@ -17661,7 +11747,7 @@ msgid ""
 "enable it by default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:865
+#: i2p2www/pages/site/docs/how/threat-model.html:975
 msgid ""
 "Blocklists are only a part (perhaps a small part) of an array of defenses"
 "\n"
@@ -17672,7 +11758,7 @@ msgid ""
 "list above there are improvements we can make in detecting badness."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:874
+#: i2p2www/pages/site/docs/how/threat-model.html:984
 msgid ""
 "If a blocklist is hosted at a central location with automatic updates\n"
 "the network is vulnerable to a\n"
@@ -17682,7 +11768,7 @@ msgid ""
 "the i2p network down. Completely."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:882
+#: i2p2www/pages/site/docs/how/threat-model.html:992
 msgid ""
 "Currently, a default blocklist is distributed with our software,\n"
 "listing only the IPs of past DOS sources.\n"
@@ -17744,6 +11830,11 @@ msgstr ""
 msgid "Outbound Endpoint"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
+#: i2p2www/pages/site/docs/tunnels/implementation.html:140
+msgid "Inbound Gateway"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:31
 msgid "Inbound Participant"
 msgstr ""
@@ -18097,6 +12188,10 @@ msgid ""
 "profile."
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:230
+msgid "Tunnel creation"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:231
 #, python-format
 msgid ""
@@ -18161,10 +12256,18 @@ msgstr ""
 msgid "Tunnel creation specification"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:288
+msgid "Unidirectional tunnels"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:290
 msgid "Tunnel message specification"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:292
+msgid "Garlic routing"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:294
 msgid "ElGamal/AES+SessionTag"
 msgstr ""
@@ -18181,10 +12284,8 @@ msgid ""
 "It enables\n"
 "secure and asynchronous messaging by sending and receiving messages over "
 "a \n"
-"single TCP socket, yet never exposing any private keys and authenticating"
-" itself\n"
-"to the router only through signatures.  With I2CP, a client application "
-"tells the\n"
+"single TCP socket.\n"
+"With I2CP, a client application tells the\n"
 "router who they are (their \"destination\"), what anonymity, reliability,"
 " and \n"
 "latency tradeoffs to make, and where to send messages.  In turn the "
@@ -18197,28 +12298,19 @@ msgstr ""
 #: i2p2www/pages/site/docs/protocol/i2cp.html:18
 #, python-format
 msgid ""
-"The protocol itself has only been implemented in Java, to provide the\n"
+"The protocol itself is implemented in Java, to provide the\n"
 "Client SDK.\n"
 "This SDK is exposed in the i2p.jar package, which implements the client-"
 "side of I2CP.\n"
 "Clients should never need to access the router.jar package, which "
 "contains the\n"
-"router itself and the router-side of I2CP."
+"router itself and the router-side of I2CP.\n"
+"There is also a C library implementation.\n"
+"A non-Java client would also have to implement the\n"
+"streaming library for TCP-style connections."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:26
-#, python-format
-msgid ""
-"While implementing the client side of I2CP in a non-Java language is "
-"certainly feasible,\n"
-"a non-Java client would also have to implement the\n"
-"streaming library for TCP-style "
-"connections.\n"
-"Together, implementing I2CP and the streaming library would be a sizable "
-"task."
-msgstr ""
-
-#: i2p2www/pages/site/docs/protocol/i2cp.html:33
+#: i2p2www/pages/site/docs/protocol/i2cp.html:31
 #, python-format
 msgid ""
 "Applications can take advantage of the base I2CP plus the \n"
@@ -18234,7 +12326,7 @@ msgid ""
 "So there are several options for both Java and non-Java applications."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:45
+#: i2p2www/pages/site/docs/protocol/i2cp.html:43
 #, python-format
 msgid ""
 "Client-side end-to-end encryption (encrypting the data over the I2CP "
@@ -18250,7 +12342,7 @@ msgid ""
 " management of those keys."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:58
+#: i2p2www/pages/site/docs/protocol/i2cp.html:56
 msgid ""
 "In a standard I2P installation, port 7654 is used by external java "
 "clients to communicate\n"
@@ -18264,20 +12356,35 @@ msgid ""
 "through an internal JVM interface."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:67
+#: i2p2www/pages/site/docs/protocol/i2cp.html:65
+#, python-format
+msgid ""
+"The router also supports external connections over SSL.\n"
+"While SSL is not the default, it is strongly recommended for any traffic "
+"that may\n"
+"be exposed to the open Internet. The authorization user/password (if "
+"any), the\n"
+"Private Key and\n"
+"Signing Private "
+"Key for the\n"
+"Destination\n"
+"are all transmitted in-the-clear unless SSL is enabled."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:75
 msgid "I2CP Protocol Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:68
+#: i2p2www/pages/site/docs/protocol/i2cp.html:76
 #, python-format
 msgid "Now on the I2CP Specification page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:73
+#: i2p2www/pages/site/docs/protocol/i2cp.html:81
 msgid "I2CP Initialization"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:74
+#: i2p2www/pages/site/docs/protocol/i2cp.html:82
 #, python-format
 msgid ""
 "When a client connects to the router, it first sends a single protocol "
@@ -18295,11 +12402,11 @@ msgid ""
 "destinations."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:83
+#: i2p2www/pages/site/docs/protocol/i2cp.html:91
 msgid "I2CP Options"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:84
+#: i2p2www/pages/site/docs/protocol/i2cp.html:92
 #, python-format
 msgid ""
 "The following options are traditionally passed to the router via\n"
@@ -18309,54 +12416,54 @@ msgid ""
 "Message."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:90
+#: i2p2www/pages/site/docs/protocol/i2cp.html:98
 msgid "Router-side Options"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:95
-#: i2p2www/pages/site/docs/protocol/i2cp.html:438
+#: i2p2www/pages/site/docs/protocol/i2cp.html:103
+#: i2p2www/pages/site/docs/protocol/i2cp.html:446
 msgid "As Of Release"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:96
-#: i2p2www/pages/site/docs/protocol/i2cp.html:439
+#: i2p2www/pages/site/docs/protocol/i2cp.html:104
+#: i2p2www/pages/site/docs/protocol/i2cp.html:447
 msgid "Recommended Arguments"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:97
-#: i2p2www/pages/site/docs/protocol/i2cp.html:440
+#: i2p2www/pages/site/docs/protocol/i2cp.html:105
+#: i2p2www/pages/site/docs/protocol/i2cp.html:448
 msgid "Allowable Range"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:105
-#: i2p2www/pages/site/docs/protocol/i2cp.html:118
-#: i2p2www/pages/site/docs/protocol/i2cp.html:127
-#: i2p2www/pages/site/docs/protocol/i2cp.html:136
-#: i2p2www/pages/site/docs/protocol/i2cp.html:145
-#: i2p2www/pages/site/docs/protocol/i2cp.html:160
-#: i2p2www/pages/site/docs/protocol/i2cp.html:175
-#: i2p2www/pages/site/docs/protocol/i2cp.html:184
-#: i2p2www/pages/site/docs/protocol/i2cp.html:232
-#: i2p2www/pages/site/docs/protocol/i2cp.html:244
-#: i2p2www/pages/site/docs/protocol/i2cp.html:256
+#: i2p2www/pages/site/docs/protocol/i2cp.html:113
+#: i2p2www/pages/site/docs/protocol/i2cp.html:126
+#: i2p2www/pages/site/docs/protocol/i2cp.html:135
+#: i2p2www/pages/site/docs/protocol/i2cp.html:144
+#: i2p2www/pages/site/docs/protocol/i2cp.html:153
+#: i2p2www/pages/site/docs/protocol/i2cp.html:168
+#: i2p2www/pages/site/docs/protocol/i2cp.html:183
+#: i2p2www/pages/site/docs/protocol/i2cp.html:192
+#: i2p2www/pages/site/docs/protocol/i2cp.html:240
+#: i2p2www/pages/site/docs/protocol/i2cp.html:252
+#: i2p2www/pages/site/docs/protocol/i2cp.html:264
 #, python-format
 msgid "number from %(from)s to %(to)s"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:106
-#: i2p2www/pages/site/docs/protocol/i2cp.html:128
-#: i2p2www/pages/site/docs/protocol/i2cp.html:137
-#: i2p2www/pages/site/docs/protocol/i2cp.html:146
-#: i2p2www/pages/site/docs/protocol/i2cp.html:161
-#: i2p2www/pages/site/docs/protocol/i2cp.html:233
-#: i2p2www/pages/site/docs/protocol/i2cp.html:245
-#: i2p2www/pages/site/docs/protocol/i2cp.html:257
-#: i2p2www/pages/site/docs/protocol/i2cp.html:530
+#: i2p2www/pages/site/docs/protocol/i2cp.html:114
+#: i2p2www/pages/site/docs/protocol/i2cp.html:136
+#: i2p2www/pages/site/docs/protocol/i2cp.html:145
+#: i2p2www/pages/site/docs/protocol/i2cp.html:154
+#: i2p2www/pages/site/docs/protocol/i2cp.html:169
+#: i2p2www/pages/site/docs/protocol/i2cp.html:241
+#: i2p2www/pages/site/docs/protocol/i2cp.html:253
+#: i2p2www/pages/site/docs/protocol/i2cp.html:265
+#: i2p2www/pages/site/docs/protocol/i2cp.html:538
 #, python-format
 msgid "%(from)s to %(to)s"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:108
+#: i2p2www/pages/site/docs/protocol/i2cp.html:116
 msgid ""
 "Number of tunnels in.\n"
 "Limit was increased from 6 to 16 in release 0.9; however, numbers higher "
@@ -18365,25 +12472,25 @@ msgid ""
 " releases."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:119
-#: i2p2www/pages/site/docs/protocol/i2cp.html:176
-#: i2p2www/pages/site/docs/protocol/i2cp.html:185
+#: i2p2www/pages/site/docs/protocol/i2cp.html:127
+#: i2p2www/pages/site/docs/protocol/i2cp.html:184
+#: i2p2www/pages/site/docs/protocol/i2cp.html:193
 msgid "No limit"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:121
+#: i2p2www/pages/site/docs/protocol/i2cp.html:129
 msgid "Number of tunnels out"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:130
+#: i2p2www/pages/site/docs/protocol/i2cp.html:138
 msgid "Length of tunnels in"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:139
+#: i2p2www/pages/site/docs/protocol/i2cp.html:147
 msgid "Length of tunnels out"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:148
+#: i2p2www/pages/site/docs/protocol/i2cp.html:156
 msgid ""
 "Random amount to add or subtract to the length of tunnels in.\n"
 "A positive number x means add a random amount from 0 to x inclusive.\n"
@@ -18393,7 +12500,7 @@ msgid ""
 "The default variance was 1 prior to release 0.7.6."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:163
+#: i2p2www/pages/site/docs/protocol/i2cp.html:171
 msgid ""
 "Random amount to add or subtract to the length of tunnels out.\n"
 "A positive number x means add a random amount from 0 to x inclusive.\n"
@@ -18403,92 +12510,94 @@ msgid ""
 "The default variance was 1 prior to release 0.7.6."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:178
+#: i2p2www/pages/site/docs/protocol/i2cp.html:186
 msgid "Number of redundant fail-over for tunnels in"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:187
+#: i2p2www/pages/site/docs/protocol/i2cp.html:195
 msgid "Number of redundant fail-over for tunnels out"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:196
+#: i2p2www/pages/site/docs/protocol/i2cp.html:204
 msgid ""
 "Name of tunnel - generally used in routerconsole, which will\n"
 "use the first few characters of the Base64 hash of the destination by "
 "default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:208
+#: i2p2www/pages/site/docs/protocol/i2cp.html:216
 msgid "Name of tunnel - generally ignored unless inbound.nickname is unset."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:217
+#: i2p2www/pages/site/docs/protocol/i2cp.html:225
 msgid "If incoming zero hop tunnel is allowed"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:226
+#: i2p2www/pages/site/docs/protocol/i2cp.html:234
 msgid "If outgoing zero hop tunnel is allowed"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:235
-#: i2p2www/pages/site/docs/protocol/i2cp.html:247
+#: i2p2www/pages/site/docs/protocol/i2cp.html:243
+#: i2p2www/pages/site/docs/protocol/i2cp.html:255
 msgid ""
 "Number of IP bytes to match to determine if\n"
 "two routers should not be in the same tunnel. 0 to disable."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:259
+#: i2p2www/pages/site/docs/protocol/i2cp.html:267
 msgid ""
 "Priority adjustment for outbound messages.\n"
 "Higher is higher priority."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:271
+#: i2p2www/pages/site/docs/protocol/i2cp.html:279
 msgid "Should generally be set to true for clients and false for servers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:280
+#: i2p2www/pages/site/docs/protocol/i2cp.html:288
 msgid ""
 "Guaranteed is disabled;\n"
 "None implemented in 0.8.1; the streaming lib default is None as of 0.8.1,"
 " the client side default is None as of 0.9.4"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:292
-#: i2p2www/pages/site/docs/protocol/i2cp.html:571
+#: i2p2www/pages/site/docs/protocol/i2cp.html:300
+#: i2p2www/pages/site/docs/protocol/i2cp.html:579
 msgid ""
 "If true, the router just sends the MessagePayload instead\n"
 "of sending a MessageStatus and awaiting a ReceiveMessageBegin."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:304
+#: i2p2www/pages/site/docs/protocol/i2cp.html:312
 msgid ""
 "Comma-separated list of Base 64 Hashes of peers to build tunnels through;"
 " for debugging only"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:313
-#: i2p2www/pages/site/docs/protocol/i2cp.html:325
+#: i2p2www/pages/site/docs/protocol/i2cp.html:321
 msgid ""
 "For authorization, if required by the router.\n"
 "If the client is running in the same JVM as a router, this option is not "
-"required."
+"required.\n"
+"Warning - username and password are sent in the clear to the router, "
+"unless using SSL (i2cp.SSL=true).\n"
+"Authorization is only recommended when using SSL."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:337
+#: i2p2www/pages/site/docs/protocol/i2cp.html:343
 msgid ""
 "Number of ElGamal/AES Session Tags to send at a time.\n"
 "For clients with relatively low bandwidth per-client-pair (IRC, some UDP "
 "apps), this may be set lower."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:349
+#: i2p2www/pages/site/docs/protocol/i2cp.html:355
 msgid ""
 "Minimum number of ElGamal/AES Session Tags before we send more.\n"
 "Recommended: approximately tagsToSend * 2/3"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:361
+#: i2p2www/pages/site/docs/protocol/i2cp.html:367
 msgid ""
 "Set to false to disable ever bundling a reply LeaseSet.\n"
 "For clients that do not publish their LeaseSet, this option must be true\n"
@@ -18497,7 +12606,7 @@ msgid ""
 "with long connection times."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:368
+#: i2p2www/pages/site/docs/protocol/i2cp.html:374
 msgid ""
 "Setting to \"false\" may save significant outbound bandwidth, especially "
 "if\n"
@@ -18508,15 +12617,15 @@ msgid ""
 "There are several cases where \"false\" may be appropriate:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:376
+#: i2p2www/pages/site/docs/protocol/i2cp.html:382
 msgid "Unidirectional communication, no reply required"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:377
+#: i2p2www/pages/site/docs/protocol/i2cp.html:383
 msgid "LeaseSet is published and higher reply latency is acceptable"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:378
+#: i2p2www/pages/site/docs/protocol/i2cp.html:384
 msgid ""
 "LeaseSet is published, client is a \"server\", all connections are "
 "inbound\n"
@@ -18530,35 +12639,41 @@ msgid ""
 "HTTP servers may fit these requirements."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:396
+#: i2p2www/pages/site/docs/protocol/i2cp.html:402
 msgid ""
 "Any other options prefixed with \"inbound.\" are stored\n"
 "in the \"unknown options\" properties of the inbound tunnel pool's "
 "settings."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:408
+#: i2p2www/pages/site/docs/protocol/i2cp.html:414
 msgid ""
 "Any other options prefixed with \"outbound.\" are stored\n"
 "in the \"unknown options\" properties of the outbound tunnel pool's "
 "settings."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:415
+#: i2p2www/pages/site/docs/protocol/i2cp.html:421
 msgid ""
 "Note: Large quantity, length, or variance settings may cause significant "
 "performance or reliability problems."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:419
+#: i2p2www/pages/site/docs/protocol/i2cp.html:425
+#, python-format
 msgid ""
 "Note: As of release 0.7.7, option names and values must use UTF-8 "
 "encoding.\n"
 "This is primarily useful for nicknames.\n"
 "Prior to that release, options with multi-byte characters were corrupted."
+"\n"
+"Since options are encoded in a Mapping,\n"
+"all option names and values are limited to 255 bytes (not characters) "
+"maximum."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:425
+#: i2p2www/pages/site/docs/protocol/i2cp.html:433
 msgid ""
 "The following options are interpreted on the client side,\n"
 "and will be interpreted if passed to the I2PSession via the "
@@ -18567,76 +12682,76 @@ msgid ""
 "Other implementations may have different defaults."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:433
+#: i2p2www/pages/site/docs/protocol/i2cp.html:441
 msgid "Client-side Options"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:451
+#: i2p2www/pages/site/docs/protocol/i2cp.html:459
 msgid ""
 "Router hostname.\n"
 "If the client is running in the same JVM as a router, this option is "
 "ignored, and the client connects to that router internally."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:463
+#: i2p2www/pages/site/docs/protocol/i2cp.html:471
 msgid ""
 "Router I2CP port.\n"
 "If the client is running in the same JVM as a router, this option is "
 "ignored, and the client connects to that router internally."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:475
+#: i2p2www/pages/site/docs/protocol/i2cp.html:483
 msgid ""
 "Connect to the router using SSL.\n"
 "If the client is running in the same JVM as a router, this option is "
 "ignored, and the client connects to that router internally."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:487
+#: i2p2www/pages/site/docs/protocol/i2cp.html:495
 msgid "Gzip outbound data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:496
+#: i2p2www/pages/site/docs/protocol/i2cp.html:504
 msgid "Reduce tunnel quantity when idle"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:505
+#: i2p2www/pages/site/docs/protocol/i2cp.html:513
 msgid "Close I2P session when idle"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:512
-#: i2p2www/pages/site/docs/protocol/i2cp.html:521
+#: i2p2www/pages/site/docs/protocol/i2cp.html:520
+#: i2p2www/pages/site/docs/protocol/i2cp.html:529
 #, python-format
 msgid "%(num)s minimum"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:514
+#: i2p2www/pages/site/docs/protocol/i2cp.html:522
 msgid "(ms) Idle time required (default 20 minutes, minimum 5 minutes)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:523
+#: i2p2www/pages/site/docs/protocol/i2cp.html:531
 msgid "(ms) Idle time required (default 30 minutes)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:532
+#: i2p2www/pages/site/docs/protocol/i2cp.html:540
 msgid "Tunnel quantity when reduced (applies to both inbound and outbound)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:541
+#: i2p2www/pages/site/docs/protocol/i2cp.html:549
 msgid "Encrypt the lease"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:550
+#: i2p2www/pages/site/docs/protocol/i2cp.html:558
 msgid "Base64 SessionKey (44 characters)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:559
+#: i2p2www/pages/site/docs/protocol/i2cp.html:567
 msgid ""
 "Guaranteed is disabled;\n"
 "None implemented in 0.8.1; None is the default as of 0.9.4"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:578
+#: i2p2www/pages/site/docs/protocol/i2cp.html:586
 msgid ""
 "Note: All arguments, including numbers, are strings. True/false values "
 "are case-insensitive strings.\n"
@@ -18644,11 +12759,11 @@ msgid ""
 "All option names are case-sensitive."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:584
+#: i2p2www/pages/site/docs/protocol/i2cp.html:592
 msgid "I2CP Payload Data Format and Multiplexing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:585
+#: i2p2www/pages/site/docs/protocol/i2cp.html:593
 #, python-format
 msgid ""
 "The end-to-end messages handled by I2CP (i.e. the data sent by the client"
@@ -18669,61 +12784,52 @@ msgid ""
 "to work reliably in the presence of multiple channels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:599
+#: i2p2www/pages/site/docs/protocol/i2cp.html:607
 msgid ""
 "The gzip function cannot be completely turned off, however setting "
 "i2cp.gzip=false\n"
 "turns the gzip effort setting to 0, which may save a little CPU."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:605
+#: i2p2www/pages/site/docs/protocol/i2cp.html:613
 #: i2p2www/pages/site/docs/protocol/i2np.html:33
 msgid "Bytes"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:606
-#: i2p2www/pages/site/get-involved/index.html:38
+#: i2p2www/pages/site/docs/protocol/i2cp.html:614
 msgid "Content"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:611
+#: i2p2www/pages/site/docs/protocol/i2cp.html:619
 msgid "Gzip header"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:616
+#: i2p2www/pages/site/docs/protocol/i2cp.html:624
 msgid "Gzip flags"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:621
+#: i2p2www/pages/site/docs/protocol/i2cp.html:629
 msgid "I2P Source port (Gzip mtime)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:626
+#: i2p2www/pages/site/docs/protocol/i2cp.html:634
 msgid "I2P Destination port (Gzip mtime)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:631
+#: i2p2www/pages/site/docs/protocol/i2cp.html:639
 msgid "Gzip xflags"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:636
+#: i2p2www/pages/site/docs/protocol/i2cp.html:644
 msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:640
+#: i2p2www/pages/site/docs/protocol/i2cp.html:648
 msgid ""
 "Data integrity is verified with the standard gzip CRC-32 as\n"
 "specified by RFC 1952."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:648
-msgid "Implement I2CP and the streaming library in another programming language."
-msgstr ""
-
-#: i2p2www/pages/site/docs/protocol/i2cp.html:652
-msgid "Is the initial Get Date / Set Date handshake required?"
-msgstr ""
-
 #: i2p2www/pages/site/docs/protocol/i2cp.html:656
 msgid ""
 "The current authorization mechanism could be modified to use hashed "
@@ -18732,11 +12838,12 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/protocol/i2cp.html:660
 msgid ""
-"Private Keys are included in the Create Lease Set message,\n"
-"are they really required? Revocation is unimplemented."
+"The Signing Private Keys is included in the Create Lease Set message,\n"
+"it is not required. Revocation is unimplemented.\n"
+"It should be replaced with random data or removed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:665
+#: i2p2www/pages/site/docs/protocol/i2cp.html:666
 #, python-format
 msgid ""
 "Some improvements may be able to use messages previously defined but not "
@@ -18748,6 +12855,10 @@ msgid ""
 "Common Data Structures Specification Version 0.9."
 msgstr ""
 
+#: i2p2www/pages/site/docs/protocol/i2np.html:3
+msgid "June 2013"
+msgstr ""
+
 #: i2p2www/pages/site/docs/protocol/i2np.html:6
 msgid "I2P Network Protocol"
 msgstr ""
@@ -18884,12 +12995,12 @@ msgid ""
 "which is wrapped in a DataMessage."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2np.html:92
-msgid "Type"
+#: i2p2www/pages/site/docs/protocol/i2np.html:91
+msgid "Message"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2np.html:94
-msgid "Priority"
+#: i2p2www/pages/site/docs/protocol/i2np.html:92
+msgid "Type"
 msgstr ""
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:95
@@ -19333,8 +13444,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/blockfile.html:172
 #, python-format
 msgid ""
-"\"%%__INFO__%%\" is the master database skiplist with String/Properties "
-"key/value entries containing only one entry:"
+"%(INFO)s is the master database skiplist with String/Properties key/value"
+" entries containing only one entry:"
 msgstr ""
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:184
@@ -19344,8 +13455,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/blockfile.html:185
 #, python-format
 msgid ""
-"\"%%__REVERSE__%%\" is the reverse lookup skiplist with "
-"Integer/Properties key/value entries\n"
+"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties "
+"key/value entries\n"
 "    (as of database version 2):"
 msgstr ""
 
@@ -19404,14 +13515,13 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/common-structures.html:166
 #: i2p2www/pages/site/docs/spec/common-structures.html:178
 #: i2p2www/pages/site/docs/spec/common-structures.html:231
-#: i2p2www/pages/site/docs/spec/common-structures.html:298
-#: i2p2www/pages/site/docs/spec/common-structures.html:347
-#: i2p2www/pages/site/docs/spec/common-structures.html:391
-#: i2p2www/pages/site/docs/spec/common-structures.html:438
-#: i2p2www/pages/site/docs/spec/common-structures.html:573
-#: i2p2www/pages/site/docs/spec/common-structures.html:630
+#: i2p2www/pages/site/docs/spec/common-structures.html:314
+#: i2p2www/pages/site/docs/spec/common-structures.html:363
+#: i2p2www/pages/site/docs/spec/common-structures.html:415
+#: i2p2www/pages/site/docs/spec/common-structures.html:462
+#: i2p2www/pages/site/docs/spec/common-structures.html:597
+#: i2p2www/pages/site/docs/spec/common-structures.html:660
 #: i2p2www/pages/site/docs/spec/streaming.html:35
-#: i2p2www/pages/site/get-involved/develop/applications.html:8
 msgid "Contents"
 msgstr ""
 
@@ -19609,64 +13719,87 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:273
 msgid ""
-"Mappings contained in I2NP messages (i.e. in a RouterAddress or "
-"RouterInfo)\n"
-"must be sorted by key so that the signature will be invariant."
+"The encoding allows duplicate keys, however in any usage where the "
+"mapping is signed,\n"
+"duplicates may cause a signature failure."
 msgstr ""
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:278
 msgid ""
+"Mappings contained in I2NP messages (i.e. in a RouterAddress or "
+"RouterInfo)\n"
+"must be sorted by key so that the signature will be invariant.\n"
+"Duplicate keys are not allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:284
+#, python-format
+msgid ""
+"Mappings contained in an I2CP "
+"SessionConfig\n"
+"must be sorted by key so that the signature will be invariant.\n"
+"Duplicate keys are not allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:290
+msgid ""
+"While it is application-dependent, keys and values are generally case-"
+"sensitive."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:294
+msgid ""
 "Key and value string length limits are 255 bytes (not characters) each, "
 "plus the length byte. Length byte may be 0."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:282
+#: i2p2www/pages/site/docs/spec/common-structures.html:298
 msgid ""
 "Total length limit is 65535 bytes, plus the 2 byte size field, or 65537 "
 "total."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:291
+#: i2p2www/pages/site/docs/spec/common-structures.html:307
 msgid "Common structure specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:295
+#: i2p2www/pages/site/docs/spec/common-structures.html:311
 msgid "Defines the way to uniquely identify a particular router\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:299
+#: i2p2www/pages/site/docs/spec/common-structures.html:315
 msgid ""
 "PublicKey followed by SigningPublicKey and then a Certificate\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:336
+#: i2p2www/pages/site/docs/spec/common-structures.html:352
 msgid ""
 "The certificate for a RouterIdentity is currently unused and is always "
 "NULL."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:344
+#: i2p2www/pages/site/docs/spec/common-structures.html:360
 msgid ""
 "A Destination defines a particular endpoint to which messages can be "
 "directed for secure delivery.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:348
+#: i2p2www/pages/site/docs/spec/common-structures.html:364
 msgid ""
 "PublicKey followed by a SigningPublicKey and then a Certificate\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:388
+#: i2p2www/pages/site/docs/spec/common-structures.html:412
 msgid ""
 "Defines the authorization for a particular tunnel to receive messages "
 "targeting a Destination.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:392
+#: i2p2www/pages/site/docs/spec/common-structures.html:416
 msgid ""
 "SHA256 Hash of the\n"
 "RouterIdentity of the gateway "
@@ -19674,11 +13807,11 @@ msgid ""
 "end Date\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:423
+#: i2p2www/pages/site/docs/spec/common-structures.html:447
 msgid "Total size: 44 bytes"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:433
+#: i2p2www/pages/site/docs/spec/common-structures.html:457
 msgid ""
 "Contains all of the currently authorized Leases for a particular Destination.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:439
+#: i2p2www/pages/site/docs/spec/common-structures.html:463
 msgid ""
 "Destination, followed by a PublicKey for encryption, then a SigningPrivateKey"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:531
+#: i2p2www/pages/site/docs/spec/common-structures.html:555
 msgid ""
 "The public key of the destination was used for the old i2cp-to-i2cp "
 "encryption\n"
-"which was disabled in version 0.6, it is currently unused?"
+"which was disabled in version 0.6, it is currently unused."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:536
+#: i2p2www/pages/site/docs/spec/common-structures.html:560
 #, python-format
 msgid ""
 "The encryption key is used for end-to-end Integer defining the relative cost "
 "of using the address, where 0 is free and 255 is expensive, followed by "
@@ -19782,21 +13915,29 @@ msgid ""
 "IP address, port number, email address, URL, etc.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:609
+#: i2p2www/pages/site/docs/spec/common-structures.html:633
 msgid "Cost is typically 5 or 6 for SSU, and 10 or 11 for NTCP."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:613
+#: i2p2www/pages/site/docs/spec/common-structures.html:637
 msgid ""
 "Expiration is currently unused, always null (all zeroes)).\n"
 "As of release 0.9.3, the expiration is assumed zero and not stored, so "
 "any non-zero expiration\n"
 "will fail in the RouterInfo signature verification.\n"
 "Implementing expiration (or another use for these bytes) will be a "
-"backwards-incompatible change."
+"backwards-incompatible change.\n"
+"Routers MUST set this field to all zeros."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:626
+#: i2p2www/pages/site/docs/spec/common-structures.html:645
+msgid ""
+"The following options, while not required, are standard and expected to "
+"be present in most router addresses:\n"
+"\"host\" (an IPv4 or IPv6 address or host name) and \"port\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:656
 msgid ""
 "Defines all of the data that a router wants to publish for the network to"
 " see. The RouterInfo is one of two "
@@ -19806,27 +13947,34 @@ msgid ""
 "the contained RouterIdentity.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:631
+#: i2p2www/pages/site/docs/spec/common-structures.html:661
 msgid ""
 "RouterIdentity followed by the Date, when the entry was published\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:710
+#: i2p2www/pages/site/docs/spec/common-structures.html:741
 msgid ""
 "The peer_size Integer may be followed by a list of that many router "
 "hashes.\n"
 "This is currently unused. It was intended for a form of restricted "
-"routes, which is unimplemented.\n"
+"routes, which is unimplemented."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:715
+#: i2p2www/pages/site/docs/spec/common-structures.html:746
 msgid ""
 "The signature may be verified using the signing public key of the "
-"router_ident.\n"
+"router_ident."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:723
+#: i2p2www/pages/site/docs/spec/common-structures.html:750
+#, python-format
+msgid ""
+"See the network database page\n"
+"for standard options that are expected to be present in all router infos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:760
 #, python-format
 msgid ""
 "Defined in the Tunnel Message "
@@ -19958,10 +14106,18 @@ msgstr ""
 msgid "Enable/disable for each installed plugin."
 msgstr ""
 
+#: i2p2www/pages/site/docs/spec/configuration.html:70
+msgid "Router"
+msgstr ""
+
 #: i2p2www/pages/site/docs/spec/configuration.html:71
 msgid "Configured via /configadvanced in the router console."
 msgstr ""
 
+#: i2p2www/pages/site/docs/spec/configuration.html:75
+msgid "Applications"
+msgstr "Anwendungen"
+
 #: i2p2www/pages/site/docs/spec/configuration.html:78
 msgid "See documentation in SusiDNS."
 msgstr ""
@@ -20167,44 +14323,64 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/spec/updates.html:35
 msgid ""
+"Parameters in the i2p.release entry are as follows.\n"
+"All keys are case-insensitive. All values must be enclosed in double "
+"quotes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:73
+msgid ""
 "The elements may be included inside XML comments to prevent "
 "interpretation by browsers.\n"
-"The i2p.release element and version are required. All others are optional"
-" and are\n"
-"currently unused."
+"The i2p.release element and version are required. All others are "
+"optional.\n"
+"NOTE: Due to parser limitations an entire element must be on a single "
+"line."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:41
-msgid ""
-"The news source is trusted only to indicate that a new version is "
-"available.\n"
-"It does not specify the URL of the update, the checksum, or any other "
-"information."
-msgstr ""
-
-#: i2p2www/pages/site/docs/spec/updates.html:47
+#: i2p2www/pages/site/docs/spec/updates.html:80
 msgid "Update File Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:48
+#: i2p2www/pages/site/docs/spec/updates.html:81
+msgid ""
+"As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n"
+"use the \"su3\" file format specified below.\n"
+"Approved release signers will use 4096-bit RSA keys.\n"
+"The X.509 public key certificates for these signers are distributed in "
+"the router installation packages.\n"
+"The updates may contain certificates for new, approved signers, and/or "
+"contain\n"
+"a list of certificates to delete for revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:91
+msgid "Old Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:92
+msgid "This format is obsolte as of release 0.9.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:95
 msgid ""
 "The signed update file, traditionally named i2pupdate.sud,\n"
 "is simply a zip file with a prepended 56 byte header.\n"
 "The header contains:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:54
+#: i2p2www/pages/site/docs/spec/updates.html:101
 #, python-format
 msgid ""
 "A 40-byte DSA "
 "signature"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:57
+#: i2p2www/pages/site/docs/spec/updates.html:104
 msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:62
+#: i2p2www/pages/site/docs/spec/updates.html:109
 #, python-format
 msgid ""
 "The signature covers only the zip archive - not the prepended version.\n"
@@ -20215,14 +14391,14 @@ msgid ""
 " managers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:68
+#: i2p2www/pages/site/docs/spec/updates.html:115
 msgid ""
 "For version comparison purposes, version fields contain [0-9]*, field "
 "separators are\n"
 "'-', '_', and '.', and all other characters are ignored."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:73
+#: i2p2www/pages/site/docs/spec/updates.html:120
 msgid ""
 "As of version 0.8.8, the version must also be specified as a zip file "
 "comment in UTF-8,\n"
@@ -20234,11 +14410,11 @@ msgid ""
 "This prevents spoofing of the version number in the header."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:81
+#: i2p2www/pages/site/docs/spec/updates.html:128
 msgid "Download and Installation"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:82
+#: i2p2www/pages/site/docs/spec/updates.html:129
 msgid ""
 "The router first downloads the header of the update file from one in a "
 "configurable list of I2P URLs,\n"
@@ -20254,21 +14430,21 @@ msgid ""
 "explained above."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:93
+#: i2p2www/pages/site/docs/spec/updates.html:140
 msgid "The zip file is extracted in the base $I2P installation directory."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:97
+#: i2p2www/pages/site/docs/spec/updates.html:144
 msgid ""
 "As of release 0.7.12, the router supports Pack200 decompression.\n"
 "Files inside the zip archive with a .jar.pack or .war.pack suffix\n"
 "are transparently decompressed to a .jar or .war file.\n"
 "Update files containing .pack files are traditionally named with a '.su2'"
 " suffix.\n"
-"Pack200 shrinks the update files by about 60%."
+"Pack200 shrinks the update files by about 60%."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:105
+#: i2p2www/pages/site/docs/spec/updates.html:152
 msgid ""
 "As of release 0.8.7, the router will delete the libjbigi.so and "
 "libjcpuid.so files\n"
@@ -20277,93 +14453,95 @@ msgid ""
 "be extracted from jbigi.jar."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:111
+#: i2p2www/pages/site/docs/spec/updates.html:158
 msgid ""
 "As of release 0.8.12, if the zip archive contains a file deletelist.txt, "
 "the router will\n"
 "delete the files listed there. The format is:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:116
+#: i2p2www/pages/site/docs/spec/updates.html:163
 msgid "One file name per line"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:117
+#: i2p2www/pages/site/docs/spec/updates.html:164
 msgid ""
 "All file names are relative to the installation directory; no absolute "
 "file names allowed, no files starting with \"..\""
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:118
+#: i2p2www/pages/site/docs/spec/updates.html:165
 msgid "Comments start with '#'"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:121
+#: i2p2www/pages/site/docs/spec/updates.html:168
 msgid "The router will then delete the deletelist.txt file."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:126
+#: i2p2www/pages/site/docs/spec/updates.html:173
 msgid "New \"su3\" Update File Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:128
-msgid "This specification is preliminary and is not yet implemented."
+#: i2p2www/pages/site/docs/spec/updates.html:175
+msgid ""
+"This specification is used for router updates and reseed data as of "
+"release 0.9.9."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:132
-msgid "Issues with existing .sud/.su2 format:"
+#: i2p2www/pages/site/docs/spec/updates.html:179
+msgid "Issues with the previous .sud/.su2 format:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:134
+#: i2p2www/pages/site/docs/spec/updates.html:181
 msgid "No magic number or flags"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:137
+#: i2p2www/pages/site/docs/spec/updates.html:184
 msgid "No way to specify compression, pack200 or not, or signing algo"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:140
+#: i2p2www/pages/site/docs/spec/updates.html:187
 msgid ""
 "Version is not covered by signature, so it is enforced by requiring it\n"
 "to be in the zip file comment (for router files) or in the plugin.config\n"
 "file (for plugins)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:145
+#: i2p2www/pages/site/docs/spec/updates.html:192
 msgid "Signer not specified so verifier must try all known keys"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:148
+#: i2p2www/pages/site/docs/spec/updates.html:195
 msgid "Signature-before-data format requires two passes to generate file"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:154
+#: i2p2www/pages/site/docs/spec/updates.html:201
 msgid "Goals:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:157
+#: i2p2www/pages/site/docs/spec/updates.html:204
 msgid "Fix above problems"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:160
+#: i2p2www/pages/site/docs/spec/updates.html:207
 msgid "Migrate to more secure signature algorithm"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:163
+#: i2p2www/pages/site/docs/spec/updates.html:210
 msgid ""
 "Keep version info in same format and offset for compatibility with\n"
 "existing version checkers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:169
+#: i2p2www/pages/site/docs/spec/updates.html:216
 msgid "Specification:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:217
+#: i2p2www/pages/site/docs/spec/updates.html:275
 msgid "All unused fields must be set to 0 for compatibility with future versions."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:224
+#: i2p2www/pages/site/docs/spec/updates.html:282
 msgid ""
 "The network will eventually grow too large for update over HTTP.\n"
 "The built-in BitTorrent client, i2psnark, may be used as a distributed "
@@ -20371,7 +14549,7 @@ msgid ""
 "This development effort is ongoing and should be completed by late 2013."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:229
+#: i2p2www/pages/site/docs/spec/updates.html:287
 msgid ""
 "The router update mechanism is part of the web router console.\n"
 "There is currently no provision for updates of an embedded router lacking"
@@ -20382,10 +14560,6 @@ msgstr ""
 msgid "Transport Overview"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:3
-msgid "April 2013"
-msgstr ""
-
 #: i2p2www/pages/site/docs/transport/index.html:6
 msgid "Transports in I2P"
 msgstr ""
@@ -20432,35 +14606,45 @@ msgid "The transport subsystem in I2P provides the following services:"
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/index.html:37
+#, python-format
 msgid ""
-"Maintain a set of router addresses, one or more for each transport,\n"
-"that the router publishes as its global contact information (the "
-"RouterInfo)"
-msgstr ""
-
-#: i2p2www/pages/site/docs/transport/index.html:41
-msgid "Selection of the best transport for each outgoing message"
+"Reliable delivery of I2NP messages.\n"
+"Transports support I2NP message delivery ONLY.\n"
+"They are not general-purpose data pipes."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/index.html:42
+msgid ""
+"Maintain a set of router addresses, one or more for each transport,\n"
+"that the router publishes as its global contact information (the "
+"RouterInfo).\n"
+"Each transport may connect using one of these addresses, which may be\n"
+"IPv4 or (as of version 0.9.8) IPv6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:48
+msgid "Selection of the best transport for each outgoing message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:49
 msgid "Queueing of outbound messages by priority"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:43
+#: i2p2www/pages/site/docs/transport/index.html:50
 msgid ""
 "Bandwidth limiting, both outbound and inbound, according to router "
 "configuration"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:44
+#: i2p2www/pages/site/docs/transport/index.html:51
 msgid "Setup and teardown of transport connections"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:45
+#: i2p2www/pages/site/docs/transport/index.html:52
 msgid "Encryption of point-to-point communications"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:46
+#: i2p2www/pages/site/docs/transport/index.html:53
 msgid ""
 "Maintenance of connection limits for each transport, implementation of "
 "various thresholds for these limits,\n"
@@ -20468,80 +14652,81 @@ msgid ""
 "operational changes based on the status"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:50
+#: i2p2www/pages/site/docs/transport/index.html:57
 msgid "Firewall port opening using UPnP (Universal Plug and Play)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:51
+#: i2p2www/pages/site/docs/transport/index.html:58
 msgid "Cooperative NAT/Firewall traversal"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:52
+#: i2p2www/pages/site/docs/transport/index.html:59
 msgid ""
 "Local IP detection by various methods, including UPnP, inspection of "
 "incoming connections, and enumeration of network devices"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:53
+#: i2p2www/pages/site/docs/transport/index.html:60
 msgid ""
 "Coordination of firewall status and local IP, and changes to either, "
 "among the transports"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:54
-#: i2p2www/pages/site/docs/transport/ssu.html:32
+#: i2p2www/pages/site/docs/transport/index.html:61
+#: i2p2www/pages/site/docs/transport/ssu.html:33
 msgid ""
 "Communication of firewall status and local IP, and changes to either, to "
 "the router and the user interface"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:55
+#: i2p2www/pages/site/docs/transport/index.html:62
 msgid ""
 "Determination of a consensus clock, which is used to periodically update "
 "the router's clock, as a backup for NTP"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:56
+#: i2p2www/pages/site/docs/transport/index.html:63
 msgid ""
 "Maintenance of status for each peer, including whether it is connected, "
 "whether it was recently connected,\n"
 "and whether it was reachable in the last attempt"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:60
+#: i2p2www/pages/site/docs/transport/index.html:67
 msgid "Qualification of valid IP addresses according to a local rule set"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:61
+#: i2p2www/pages/site/docs/transport/index.html:68
 msgid ""
 "Honoring the automated and manual lists of banned peers maintained by the"
 " router,\n"
 "and refusing outbound and inbound connections to those peers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:68
+#: i2p2www/pages/site/docs/transport/index.html:75
 msgid "Transport Addresses"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:70
+#: i2p2www/pages/site/docs/transport/index.html:77
 msgid ""
 "The transport subsystem maintains a set of router addresses, each of "
 "which lists a transport method, IP, and port.\n"
 "These addresses constitute the advertised contact points, and are "
-"published by the router to the network database."
+"published by the router to the network database.\n"
+"Addresses may also contain an arbitrary set of additional options."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:75
+#: i2p2www/pages/site/docs/transport/index.html:83
 msgid "Typical scenarios are:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:77
+#: i2p2www/pages/site/docs/transport/index.html:85
 msgid ""
 "A router has no published addresses, so it is considered \"hidden\" and "
 "cannot receive incoming connections"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:78
+#: i2p2www/pages/site/docs/transport/index.html:86
 #, python-format
 msgid ""
 "A router is firewalled, and therefore publishes an SSU address which "
@@ -20550,22 +14735,22 @@ msgid ""
 "href=\"%(ssu)s\">the SSU spec for details)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:82
+#: i2p2www/pages/site/docs/transport/index.html:90
 msgid ""
 "A router is not firewalled or its NAT ports  are open; it publishes both "
 "NTCP and SSU addresses containing\n"
 "directly-accessible IP and ports."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:88
+#: i2p2www/pages/site/docs/transport/index.html:96
 msgid "Transport Selection"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:90
+#: i2p2www/pages/site/docs/transport/index.html:98
 #, python-format
 msgid ""
-"The transport system delivers I2NP messages. The"
-" transport selected for any message is\n"
+"The transport system delivers I2NP messages "
+"only. The transport selected for any message is\n"
 "independent of the upper-layer protocols and contents (router or client "
 "messages, whether an external application was using\n"
 "TCP or UDP to connect to I2P, whether the upper layer was using\n"
@@ -20577,7 +14762,7 @@ msgid ""
 "etc.)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:104
+#: i2p2www/pages/site/docs/transport/index.html:112
 msgid ""
 "For each outgoing message, the transport system solicits \"bids\" from "
 "each transport.\n"
@@ -20586,84 +14771,74 @@ msgid ""
 "A transport may refuse to bid."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:110
+#: i2p2www/pages/site/docs/transport/index.html:118
 msgid "Whether a transport bids, and with what value, depend on numerous factors:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:114
+#: i2p2www/pages/site/docs/transport/index.html:122
 msgid "Configuration of transport preferences"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:115
+#: i2p2www/pages/site/docs/transport/index.html:123
 msgid "Whether the transport is already connected to the peer"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:116
+#: i2p2www/pages/site/docs/transport/index.html:124
 msgid ""
 "The number of current connections compared to various connection limit "
 "thresholds"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:117
+#: i2p2www/pages/site/docs/transport/index.html:125
 msgid "Whether recent connection attempts to the peer have failed"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:118
+#: i2p2www/pages/site/docs/transport/index.html:126
 msgid ""
 "The size of the message, as different transports have different size "
 "limits"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:119
+#: i2p2www/pages/site/docs/transport/index.html:127
 msgid ""
 "Whether the peer can accept incoming connections for that transport, as "
 "advertised in its RouterInfo"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:120
+#: i2p2www/pages/site/docs/transport/index.html:128
 msgid "Whether the connection would be indirect (requiring introducers) or direct"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:121
+#: i2p2www/pages/site/docs/transport/index.html:129
 msgid "The peer's transport preference, as advertised in its RouterInfo"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:124
+#: i2p2www/pages/site/docs/transport/index.html:132
 msgid ""
 "In general, the bid values are selected so that two routers are only "
 "connected by a single transport\n"
 "at any one time. However, this is not a requirement."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:131
+#: i2p2www/pages/site/docs/transport/index.html:139
 msgid "New Transports and Future Work"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:133
+#: i2p2www/pages/site/docs/transport/index.html:141
 msgid "Additional transports may be developed, including:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:138
+#: i2p2www/pages/site/docs/transport/index.html:146
 msgid "A TLS/SSH look-alike transport"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:139
+#: i2p2www/pages/site/docs/transport/index.html:147
 msgid ""
 "An \"indirect\" transport for routers that are not reachable by all other"
 " routers (one form of \"restricted routes\")"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:142
-#, python-format
-msgid ""
-"IPv6: The existing transports must be enhanced to support multiple "
-"addresses within a single transport,\n"
-"including IPV6 addresses. Currently, a transport may only advertise a "
-"single IPV4 address.\n"
-"See this thread for discussion."
-msgstr ""
-
-#: i2p2www/pages/site/docs/transport/index.html:148
+#: i2p2www/pages/site/docs/transport/index.html:150
 msgid ""
 "Work continues on adjusting default connection limits for each transport."
 "\n"
@@ -20674,7 +14849,7 @@ msgid ""
 "routers that are behind restrictive state firewalls (restricted routes)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:155
+#: i2p2www/pages/site/docs/transport/index.html:157
 msgid ""
 "The current connection limits are higher for SSU than for NTCP, based on "
 "the assumption that\n"
@@ -20685,7 +14860,7 @@ msgid ""
 "that assumption is difficult to verify."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:162
+#: i2p2www/pages/site/docs/transport/index.html:164
 #, python-format
 msgid ""
 "Analyze Breaking and Improving Protocol "
@@ -20705,10 +14880,11 @@ msgid ""
 "The other is SSU.\n"
 "NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n"
 "Java NIO (new I/O) does not suffer from the 1 thread per connection "
-"issues of the old TCP transport."
+"issues of the old TCP transport.\n"
+"NTCP-over-IPv6 is supported as of version 0.9.8."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:15
+#: i2p2www/pages/site/docs/transport/ntcp.html:16
 msgid ""
 "By default, NTCP uses the IP/Port\n"
 "auto-detected by SSU. When enabled on config.jsp,\n"
@@ -20717,22 +14893,22 @@ msgid ""
 "Now you can enable inbound TCP without a static IP or dyndns service."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:23
+#: i2p2www/pages/site/docs/transport/ntcp.html:24
 msgid ""
 "The NTCP code within I2P is relatively lightweight (1/4 the size of the "
 "SSU code)\n"
 "because it uses the underlying Java TCP transport for reliable delivery."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:29
+#: i2p2www/pages/site/docs/transport/ntcp.html:30
 msgid "NTCP Protocol Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:31
+#: i2p2www/pages/site/docs/transport/ntcp.html:32
 msgid "Standard Message Format"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:32
+#: i2p2www/pages/site/docs/transport/ntcp.html:33
 msgid ""
 "After establishment,\n"
 "the NTCP transport sends individual I2NP messages, with a simple "
@@ -20740,7 +14916,7 @@ msgid ""
 "The unencrypted message is encoded as follows:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:42
+#: i2p2www/pages/site/docs/transport/ntcp.html:43
 msgid ""
 "The data is then AES/256/CBC encrypted. The session key for the "
 "encryption\n"
@@ -20752,7 +14928,7 @@ msgid ""
 "encrypted message."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:50
+#: i2p2www/pages/site/docs/transport/ntcp.html:51
 msgid ""
 "0-15 bytes of padding are required to bring the total message length\n"
 "(including the six size and checksum bytes) to a multiple of 16.\n"
@@ -20761,39 +14937,39 @@ msgid ""
 "The minimum data size is 1."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:58
+#: i2p2www/pages/site/docs/transport/ntcp.html:59
 msgid "Time Sync Message Format"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:59
+#: i2p2www/pages/site/docs/transport/ntcp.html:60
 msgid ""
 "One special case is a metadata message where the sizeof(data) is 0.  In\n"
 "that case, the unencrypted message is encoded as:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:70
+#: i2p2www/pages/site/docs/transport/ntcp.html:71
 msgid ""
 "Total length: 16 bytes. The time sync message is sent at approximately 15"
 " minute intervals.\n"
 "The message is encrypted just as standard messages are."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:76
+#: i2p2www/pages/site/docs/transport/ntcp.html:77
 msgid "Checksums"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:77
+#: i2p2www/pages/site/docs/transport/ntcp.html:78
 #, python-format
 msgid ""
 "The standard and time sync messages use the Adler-32 checksum\n"
 "as defined in the ZLIB Specification."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:83
+#: i2p2www/pages/site/docs/transport/ntcp.html:84
 msgid "Establishment Sequence"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:84
+#: i2p2www/pages/site/docs/transport/ntcp.html:85
 msgid ""
 "In the establish state, there is a 4-phase message sequence to exchange "
 "DH keys and signatures.\n"
@@ -20802,31 +14978,31 @@ msgid ""
 "connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:98
+#: i2p2www/pages/site/docs/transport/ntcp.html:99
 msgid "Legend:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:99
+#: i2p2www/pages/site/docs/transport/ntcp.html:100
 msgid "256 byte DH public keys"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:103
+#: i2p2www/pages/site/docs/transport/ntcp.html:104
 msgid "timestamps (4 bytes, seconds since epoch)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:104
+#: i2p2www/pages/site/docs/transport/ntcp.html:105
 msgid "32 byte Session key"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:105
+#: i2p2www/pages/site/docs/transport/ntcp.html:106
 msgid "2 byte size of Alice identity to follow"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:108
+#: i2p2www/pages/site/docs/transport/ntcp.html:109
 msgid "DH Key Exchange"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:109
+#: i2p2www/pages/site/docs/transport/ntcp.html:110
 #, python-format
 msgid ""
 "The initial 2048-bit DH key exchange\n"
@@ -20834,7 +15010,7 @@ msgid ""
 "ElGamal encryption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:115
+#: i2p2www/pages/site/docs/transport/ntcp.html:116
 msgid ""
 "The DH key exchange consists of a number of steps, displayed below.\n"
 "The mapping between these steps and the messages sent between I2P "
@@ -20842,51 +15018,54 @@ msgid ""
 "is marked in bold."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:121
-msgid ""
-"Alice generates a secret 226-bit integer x. She then calculates X ="
-" g^x mod p."
-msgstr ""
-
 #: i2p2www/pages/site/docs/transport/ntcp.html:122
-msgid "Alice sends X to Bob (Message 1)."
+msgid ""
+"Alice generates a secret integer x. She then calculates X = g^x mod"
+" p."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:123
-msgid ""
-"Bob generates a secret 226-bit integer y. He then calculates Y = "
-"g^y mod p."
+msgid "Alice sends X to Bob (Message 1)."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:124
-msgid "Bob sends Y to Alice.(Message 2)"
+msgid ""
+"Bob generates a secret integer y. He then calculates Y = g^y mod "
+"p."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:125
-msgid "Alice can now compute sessionKey = Y^x mod p."
+msgid "Bob sends Y to Alice.(Message 2)"
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:126
-msgid "Bob can now compute sessionKey = X^y mod p."
+msgid "Alice can now compute sessionKey = Y^x mod p."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:127
+msgid "Bob can now compute sessionKey = X^y mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:128
 msgid ""
 "Both Alice and Bob now have a shared key sessionKey = g^(x*y) mod "
 "p."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:129
+#: i2p2www/pages/site/docs/transport/ntcp.html:130
+#, python-format
 msgid ""
 "The sessionKey is then used to exchange identities in Message 3 "
-"and Message 4."
+"and Message 4.\n"
+"The exponent (x and y) length for the DH exchange is documented on the\n"
+"cryptography page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:133
+#: i2p2www/pages/site/docs/transport/ntcp.html:136
 msgid "Message 1 (Session Request)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:134
+#: i2p2www/pages/site/docs/transport/ntcp.html:137
 #, python-format
 msgid ""
 "This is the DH request. Alice already has Bob's\n"
@@ -20899,79 +15078,79 @@ msgid ""
 "Alice sends Bob:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:147
-#: i2p2www/pages/site/docs/transport/ntcp.html:190
-#: i2p2www/pages/site/docs/transport/ntcp.html:270
-#: i2p2www/pages/site/docs/transport/ntcp.html:353
+#: i2p2www/pages/site/docs/transport/ntcp.html:150
+#: i2p2www/pages/site/docs/transport/ntcp.html:193
+#: i2p2www/pages/site/docs/transport/ntcp.html:273
+#: i2p2www/pages/site/docs/transport/ntcp.html:356
 msgid "Size:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:149
+#: i2p2www/pages/site/docs/transport/ntcp.html:152
 msgid "Contents:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:167
+#: i2p2www/pages/site/docs/transport/ntcp.html:170
 msgid "256 byte X from Diffie Hellman"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:169
+#: i2p2www/pages/site/docs/transport/ntcp.html:172
 #, python-format
 msgid ""
 "SHA256 Hash(X) xored with SHA256 Hash(Bob's Router Identity)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:176
-#: i2p2www/pages/site/docs/transport/ntcp.html:257
-#: i2p2www/pages/site/docs/transport/ntcp.html:334
+#: i2p2www/pages/site/docs/transport/ntcp.html:179
+#: i2p2www/pages/site/docs/transport/ntcp.html:260
+#: i2p2www/pages/site/docs/transport/ntcp.html:337
 msgid "Notes:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:177
+#: i2p2www/pages/site/docs/transport/ntcp.html:180
 msgid ""
 "Bob verifies HXxorHI using his own router hash. If it does not verify,\n"
 "Alice has contacted the wrong router, and Bob drops the connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:183
+#: i2p2www/pages/site/docs/transport/ntcp.html:186
 msgid "Message 2 (Session Created)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:184
+#: i2p2www/pages/site/docs/transport/ntcp.html:187
 msgid "This is the DH reply. Bob sends Alice:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:192
-#: i2p2www/pages/site/docs/transport/ntcp.html:272
-#: i2p2www/pages/site/docs/transport/ntcp.html:355
+#: i2p2www/pages/site/docs/transport/ntcp.html:195
+#: i2p2www/pages/site/docs/transport/ntcp.html:275
+#: i2p2www/pages/site/docs/transport/ntcp.html:358
 msgid "Unencrypted Contents:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:214
-#: i2p2www/pages/site/docs/transport/ntcp.html:248
+#: i2p2www/pages/site/docs/transport/ntcp.html:217
+#: i2p2www/pages/site/docs/transport/ntcp.html:251
 msgid "256 byte Y from Diffie Hellman"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:216
+#: i2p2www/pages/site/docs/transport/ntcp.html:219
 msgid "SHA256 Hash(X concatenated with Y)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:219
-#: i2p2www/pages/site/docs/transport/ntcp.html:304
+#: i2p2www/pages/site/docs/transport/ntcp.html:222
+#: i2p2www/pages/site/docs/transport/ntcp.html:307
 msgid "4 byte timestamp (seconds since the epoch)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:221
+#: i2p2www/pages/site/docs/transport/ntcp.html:224
 msgid "12 bytes random data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:226
-#: i2p2www/pages/site/docs/transport/ntcp.html:316
-#: i2p2www/pages/site/docs/transport/ntcp.html:383
+#: i2p2www/pages/site/docs/transport/ntcp.html:229
+#: i2p2www/pages/site/docs/transport/ntcp.html:319
+#: i2p2www/pages/site/docs/transport/ntcp.html:386
 msgid "Encrypted Contents:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:250
+#: i2p2www/pages/site/docs/transport/ntcp.html:253
 #, python-format
 msgid ""
 "48 bytes AES encrypted using the DH "
@@ -20979,38 +15158,38 @@ msgid ""
 "                  the last 16 bytes of Y as the IV"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:258
+#: i2p2www/pages/site/docs/transport/ntcp.html:261
 msgid ""
 "Alice may drop the connection if the clock skew with Bob is too high as "
 "calculated using tsB."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:263
+#: i2p2www/pages/site/docs/transport/ntcp.html:266
 msgid "Message 3 (Session Confirm A)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:264
+#: i2p2www/pages/site/docs/transport/ntcp.html:267
 msgid ""
 "This contains Alice's router identity, and a DSA signature of the "
 "critical data. Alice sends Bob:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:298
+#: i2p2www/pages/site/docs/transport/ntcp.html:301
 msgid "2 byte size of Alice's router identity to follow (should always be 387)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:300
+#: i2p2www/pages/site/docs/transport/ntcp.html:303
 #, python-format
 msgid ""
 "Alice's 387 byte Router Identity"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:306
+#: i2p2www/pages/site/docs/transport/ntcp.html:309
 msgid "15 bytes random data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:308
+#: i2p2www/pages/site/docs/transport/ntcp.html:311
 #, python-format
 msgid ""
 "the 40 byte DSA "
@@ -21026,7 +15205,7 @@ msgid ""
 "href=\"%(commonstructures)s#struct_RouterIdentity\">Router Identity"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:326
+#: i2p2www/pages/site/docs/transport/ntcp.html:329
 #, python-format
 msgid ""
 "448 bytes AES encrypted using the DH"
@@ -21035,25 +15214,25 @@ msgid ""
 "of message #1) as the IV"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:336
+#: i2p2www/pages/site/docs/transport/ntcp.html:339
 msgid "Bob verifies the signature, and on failure, drops the connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:339
+#: i2p2www/pages/site/docs/transport/ntcp.html:342
 msgid ""
 "Bob may drop the connection if the clock skew with Alice is too high as "
 "calculated using tsA."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:346
+#: i2p2www/pages/site/docs/transport/ntcp.html:349
 msgid "Message 4 (Session Confirm B)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:347
+#: i2p2www/pages/site/docs/transport/ntcp.html:350
 msgid "This is a DSA signature of the critical data. Bob sends Alice:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:372
+#: i2p2www/pages/site/docs/transport/ntcp.html:375
 #, python-format
 msgid ""
 "the 40 byte DSA "
@@ -21069,11 +15248,11 @@ msgid ""
 "href=\"%(commonstructures)s#struct_RouterIdentity\">Router Identity"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:378
+#: i2p2www/pages/site/docs/transport/ntcp.html:381
 msgid "8 bytes random data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:393
+#: i2p2www/pages/site/docs/transport/ntcp.html:396
 #, python-format
 msgid ""
 "48 bytes AES encrypted using the DH "
@@ -21082,15 +15261,15 @@ msgid ""
 "#2 as the IV"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:401
+#: i2p2www/pages/site/docs/transport/ntcp.html:404
 msgid "Alice verifies the signature, and on failure, drops the connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:408
+#: i2p2www/pages/site/docs/transport/ntcp.html:411
 msgid "After Establishment"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:409
+#: i2p2www/pages/site/docs/transport/ntcp.html:412
 msgid ""
 "The connection is established, and standard or time sync messages may be "
 "exchanged.\n"
@@ -21102,11 +15281,11 @@ msgid ""
 " the next IV."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:418
+#: i2p2www/pages/site/docs/transport/ntcp.html:421
 msgid "Check Connection Message"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:419
+#: i2p2www/pages/site/docs/transport/ntcp.html:422
 msgid ""
 "Alternately, when Bob receives a connection, it could be a\n"
 "check connection (perhaps prompted by Bob asking for someone\n"
@@ -21116,54 +15295,54 @@ msgid ""
 "A check info connection will receive 256 bytes containing:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:428
+#: i2p2www/pages/site/docs/transport/ntcp.html:431
 msgid "32 bytes of uninterpreted, ignored data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:429
+#: i2p2www/pages/site/docs/transport/ntcp.html:432
 msgid "1 byte size"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:430
+#: i2p2www/pages/site/docs/transport/ntcp.html:433
 msgid ""
 "that many bytes making up the local router's IP address (as reached by "
 "the remote side)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:431
+#: i2p2www/pages/site/docs/transport/ntcp.html:434
 msgid "2 byte port number that the local router was reached on"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:432
+#: i2p2www/pages/site/docs/transport/ntcp.html:435
 msgid ""
 "4 byte i2p network time as known by the remote side (seconds since the "
 "epoch)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:433
+#: i2p2www/pages/site/docs/transport/ntcp.html:436
 msgid "uninterpreted padding data, up to byte 223"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:434
+#: i2p2www/pages/site/docs/transport/ntcp.html:437
 msgid ""
 "xor of the local router's identity hash and the SHA256 of bytes 32 "
 "through bytes 223"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:438
+#: i2p2www/pages/site/docs/transport/ntcp.html:441
 msgid "Discussion"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:439
+#: i2p2www/pages/site/docs/transport/ntcp.html:442
 #, python-format
 msgid "Now on the NTCP Discussion Page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:445
+#: i2p2www/pages/site/docs/transport/ntcp.html:448
 msgid "The maximum message size should be increased to approximately 32 KB."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:449
+#: i2p2www/pages/site/docs/transport/ntcp.html:452
 msgid ""
 "A set of fixed packet sizes may be appropriate to further hide the data \n"
 "fragmentation to external adversaries, but the tunnel, garlic, and end to"
@@ -21174,19 +15353,19 @@ msgid ""
 "to create a limited number of message sizes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:457
+#: i2p2www/pages/site/docs/transport/ntcp.html:460
 msgid ""
 "Memory utilization (including that of the kernel) for NTCP should be "
 "compared to that for SSU."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:461
+#: i2p2www/pages/site/docs/transport/ntcp.html:464
 msgid ""
 "Can the establishment messages be randomly padded somehow, to frustrate\n"
 "identification of I2P traffic based on initial packet sizes?"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:466
+#: i2p2www/pages/site/docs/transport/ntcp.html:469
 msgid "Review and possibly disable 'check connection'"
 msgstr ""
 
@@ -21213,14 +15392,15 @@ msgid ""
 "SSU is the newer of the two transports,\n"
 "introduced in I2P release 0.6.\n"
 "In a standard I2P installation, the router uses both NTCP and SSU for "
-"outbound connections."
+"outbound connections.\n"
+"SSU-over-IPv6 is supported as of version 0.9.8."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:21
+#: i2p2www/pages/site/docs/transport/ssu.html:22
 msgid "SSU Services"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:23
+#: i2p2www/pages/site/docs/transport/ssu.html:24
 msgid ""
 "Like the NTCP transport, SSU provides reliable, encrypted, connection-"
 "oriented, point-to-point data transport.\n"
@@ -21228,33 +15408,33 @@ msgid ""
 "including:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:29
+#: i2p2www/pages/site/docs/transport/ssu.html:30
 msgid ""
 "Cooperative NAT/Firewall traversal using introducers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:30
+#: i2p2www/pages/site/docs/transport/ssu.html:31
 msgid ""
 "Local IP detection by inspection of incoming packets and peer testing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:31
+#: i2p2www/pages/site/docs/transport/ssu.html:32
 msgid ""
 "Communication of firewall status and local IP, and changes to either to "
 "NTCP"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:36
+#: i2p2www/pages/site/docs/transport/ssu.html:37
 msgid "Protocol Details"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:38
+#: i2p2www/pages/site/docs/transport/ssu.html:39
 msgid "Congestion control"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:40
+#: i2p2www/pages/site/docs/transport/ssu.html:41
 msgid ""
 "SSU's need for only semireliable delivery, TCP-friendly operation,\n"
 "and the capacity for high throughput allows a great deal of latitude in\n"
@@ -21262,7 +15442,7 @@ msgid ""
 "meant to be both efficient in bandwidth as well as simple to implement."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:47
+#: i2p2www/pages/site/docs/transport/ssu.html:48
 msgid ""
 "Packets are scheduled according to the router's policy, taking care\n"
 "not to exceed the router's outbound capacity or to exceed the measured \n"
@@ -21277,7 +15457,7 @@ msgid ""
 "other messages."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:58
+#: i2p2www/pages/site/docs/transport/ssu.html:59
 msgid ""
 "The congestion detection techniques vary from TCP as well, since each \n"
 "message has its own unique and nonsequential identifier, and each message"
@@ -21293,7 +15473,7 @@ msgid ""
 "retransmitted with any new updates."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:70
+#: i2p2www/pages/site/docs/transport/ssu.html:71
 msgid ""
 "The current implementation does not pad the packets to\n"
 "any particular size, but instead just places a single message fragment "
@@ -21301,7 +15481,7 @@ msgid ""
 "a packet and sends it off (careful not to exceed the MTU)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:77
+#: i2p2www/pages/site/docs/transport/ssu.html:78
 msgid ""
 "As of router version 0.8.12,\n"
 "two MTU values are used for IPv4: 620 and 1484.\n"
@@ -21309,21 +15489,21 @@ msgid ""
 "retransmitted."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:83
+#: i2p2www/pages/site/docs/transport/ssu.html:84
 msgid ""
-"For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
+"For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
 "the payload portion after the 28-byte IP/UDP header is a multiple of\n"
 "16 bytes, for encryption purposes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:89
+#: i2p2www/pages/site/docs/transport/ssu.html:90
 msgid ""
 "For the small MTU value, it is desirable to pack a 2646-byte\n"
 "Variable Tunnel Build Message efficiently into multiple packets;\n"
 "with a 620-byte MTU, it fits into 5 packets with nicely."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:95
+#: i2p2www/pages/site/docs/transport/ssu.html:96
 msgid ""
 "Based on measurements, 1492 fits nearly all reasonably small I2NP "
 "messages\n"
@@ -21332,13 +15512,13 @@ msgid ""
 "into a live network MTU anyway)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:101
+#: i2p2www/pages/site/docs/transport/ssu.html:102
 msgid ""
 "The MTU values were 608 and 1492 for releases 0.8.9 - 0.8.11.\n"
 "The large MTU was 1350 prior to release 0.8.9."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:106
+#: i2p2www/pages/site/docs/transport/ssu.html:107
 msgid ""
 "The maximum receive packet size\n"
 "is 1571 bytes as of release 0.8.12.\n"
@@ -21346,7 +15526,7 @@ msgid ""
 "Prior to release 0.8.9 it was 2048 bytes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:113
+#: i2p2www/pages/site/docs/transport/ssu.html:114
 msgid ""
 "As of release 0.9.2, if a router's network interface MTU is less than "
 "1484,\n"
@@ -21354,17 +15534,18 @@ msgid ""
 "honor that when a connection is established."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:119
+#: i2p2www/pages/site/docs/transport/ssu.html:120
 msgid ""
 "For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes,\n"
-"so we use an MTU where (MTN % 16 == 0), which is true for 1280."
+"so we use an MTU where (MTN % 16 == 0), which is true for 1280.\n"
+"The maximum IPv6 MTU is 1472."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:124
+#: i2p2www/pages/site/docs/transport/ssu.html:126
 msgid "Message Size Limits"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:125
+#: i2p2www/pages/site/docs/transport/ssu.html:127
 msgid ""
 "While the maximum message size is nominally 32KB, the practical\n"
 "limit differs. The protocol limits the number of fragments to 7 bits, or "
@@ -21379,11 +15560,11 @@ msgid ""
 "For connections using the larger MTU, larger messages are possible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:136
+#: i2p2www/pages/site/docs/transport/ssu.html:138
 msgid "Keys"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:138
+#: i2p2www/pages/site/docs/transport/ssu.html:140
 msgid ""
 "All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n"
 "The MAC and session keys are negotiated as part of the DH exchange, used\n"
@@ -21391,7 +15572,7 @@ msgid ""
 "the publicly knowable introKey is used for the MAC and encryption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:145
+#: i2p2www/pages/site/docs/transport/ssu.html:147
 msgid ""
 "When using the introKey, both the initial message and any subsequent\n"
 "reply use the introKey of the responder (Bob) - the responder does \n"
@@ -21401,7 +15582,7 @@ msgid ""
 "Bob."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:154
+#: i2p2www/pages/site/docs/transport/ssu.html:156
 msgid ""
 "Upon receiving a message, the receiver checks the \"from\" IP address and"
 " port\n"
@@ -21414,7 +15595,7 @@ msgid ""
 "it may be dropped anyway."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:165
+#: i2p2www/pages/site/docs/transport/ssu.html:167
 msgid ""
 "If Alice and Bob have an established session, but Alice loses the \n"
 "keys for some reason and she wants to contact Bob, she may at any \n"
@@ -21426,7 +15607,7 @@ msgid ""
 "new one."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:176
+#: i2p2www/pages/site/docs/transport/ssu.html:178
 #, python-format
 msgid ""
 "For the DH key agreement,\n"
@@ -21434,18 +15615,18 @@ msgid ""
 "MODP group (#14) is used:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:186
+#: i2p2www/pages/site/docs/transport/ssu.html:188
 #, python-format
 msgid ""
 "These are the same p and g used for I2P's\n"
 "ElGamal encryption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:191
+#: i2p2www/pages/site/docs/transport/ssu.html:193
 msgid "Replay prevention"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:193
+#: i2p2www/pages/site/docs/transport/ssu.html:195
 msgid ""
 "Replay prevention at the SSU layer occurs by rejecting packets \n"
 "with exceedingly old timestamps or those which reuse an IV.  To\n"
@@ -21453,7 +15634,7 @@ msgid ""
 "\"decay\" periodically so that only recently added IVs are detected."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:200
+#: i2p2www/pages/site/docs/transport/ssu.html:202
 msgid ""
 "The messageIds used in DataMessages are defined at layers above\n"
 "the SSU transport and are passed through transparently.  These IDs\n"
@@ -21462,11 +15643,11 @@ msgid ""
 "replay prevention - higher layers should take that into account."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:208
+#: i2p2www/pages/site/docs/transport/ssu.html:210
 msgid "Addressing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:210
+#: i2p2www/pages/site/docs/transport/ssu.html:212
 msgid ""
 "To contact an SSU peer, one of two sets of information is necessary:\n"
 "a direct address, for when the peer is publicly reachable, or an\n"
@@ -21474,40 +15655,42 @@ msgid ""
 "There is no restriction on the number of addresses a peer may have."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:222
+#: i2p2www/pages/site/docs/transport/ssu.html:224
 msgid ""
 "Each of the addresses may also expose a series of options - special\n"
 "capabilities of that particular peer.  For a list of available\n"
 "capabilities, see below."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:228
+#: i2p2www/pages/site/docs/transport/ssu.html:230
 #, python-format
 msgid ""
 "The addresses, options, and capabilities are published in the network database."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:233
+#: i2p2www/pages/site/docs/transport/ssu.html:235
 msgid "Direct Session Establishment"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:234
+#: i2p2www/pages/site/docs/transport/ssu.html:236
 msgid ""
 "Direct session establishment is used when no third party is required for "
 "NAT traversal.\n"
 "The message sequence is as follows:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:239
+#: i2p2www/pages/site/docs/transport/ssu.html:241
 msgid "Connection establishment (direct)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:240
-msgid "Alice connects directly to Bob."
+#: i2p2www/pages/site/docs/transport/ssu.html:242
+msgid ""
+"Alice connects directly to Bob.\n"
+"IPv6 is supported as of version 0.9.8."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:254
+#: i2p2www/pages/site/docs/transport/ssu.html:257
 #, python-format
 msgid ""
 "After the SessionConfirmed message is received, Bob sends a small\n"
@@ -21520,7 +15703,7 @@ msgid ""
 "(i.e. 0x0000000000000002)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:263
+#: i2p2www/pages/site/docs/transport/ssu.html:266
 #, python-format
 msgid ""
 "After the status message is sent, the peers exchange\n"
@@ -21529,7 +15712,7 @@ msgid ""
 "RouterInfos."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:271
+#: i2p2www/pages/site/docs/transport/ssu.html:274
 msgid ""
 "It does not appear that the type of the status message or its contents "
 "matters.\n"
@@ -21538,7 +15721,7 @@ msgid ""
 "the status message can be eliminated."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:280
+#: i2p2www/pages/site/docs/transport/ssu.html:283
 msgid ""
 "Introduction keys are delivered through an external channel \n"
 "(the network database, where they are identical to the router Hash for "
@@ -21554,7 +15737,7 @@ msgid ""
 "not necessary to any intermediary relay peer)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:294
+#: i2p2www/pages/site/docs/transport/ssu.html:297
 msgid ""
 "Indirect session establishment by means of a third party introduction\n"
 "is necessary for efficient NAT traversal.  Charlie, a router behind a\n"
@@ -21582,25 +15765,25 @@ msgid ""
 "full direction session establishment with the specified IP and port."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:321
+#: i2p2www/pages/site/docs/transport/ssu.html:324
 msgid "Connection establishment (indirect using an introducer)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:323
+#: i2p2www/pages/site/docs/transport/ssu.html:326
 msgid "Alice first connects to introducer Bob, who relays the request to Charlie."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:341
+#: i2p2www/pages/site/docs/transport/ssu.html:344
 msgid ""
 "After the hole punch, the session is established between Alice and "
 "Charlie as in a direct establishment."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:352
+#: i2p2www/pages/site/docs/transport/ssu.html:356
 msgid "Peer testing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:354
+#: i2p2www/pages/site/docs/transport/ssu.html:358
 msgid ""
 "The automation of collaborative reachability testing for peers is\n"
 "enabled by a sequence of PeerTest messages.  With its proper \n"
@@ -21609,7 +15792,7 @@ msgid ""
 "quite simple:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:373
+#: i2p2www/pages/site/docs/transport/ssu.html:377
 msgid ""
 "Each of the PeerTest messages carry a nonce identifying the\n"
 "test series itself, as initialized by Alice.  If Alice doesn't \n"
@@ -21619,7 +15802,7 @@ msgid ""
 "that may be reached are as follows:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:383
+#: i2p2www/pages/site/docs/transport/ssu.html:387
 msgid ""
 "If she doesn't receive a response from Bob, she will retransmit\n"
 "up to a certain number of times, but if no response ever arrives,\n"
@@ -21629,7 +15812,7 @@ msgid ""
 "Charlie to reply."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:392
+#: i2p2www/pages/site/docs/transport/ssu.html:396
 msgid ""
 "If Alice doesn't receive a PeerTest message with the \n"
 "expected nonce from a third party (Charlie), she will retransmit\n"
@@ -21641,7 +15824,7 @@ msgid ""
 "IP and port that Bob offered up should be forwarded)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:403
+#: i2p2www/pages/site/docs/transport/ssu.html:407
 msgid ""
 "If Alice receives Bob's PeerTest message and both of Charlie's\n"
 "PeerTest messages but the enclosed IP and port numbers in Bob's \n"
@@ -21652,7 +15835,7 @@ msgid ""
 "remote connectivity, ignoring further port discovery."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:413
+#: i2p2www/pages/site/docs/transport/ssu.html:417
 msgid ""
 "If Alice receives Charlie's first message but not his second,\n"
 "she will retransmit her PeerTest message to Charlie up to a \n"
@@ -21660,7 +15843,7 @@ msgid ""
 "that Charlie is either confused or no longer online."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:421
+#: i2p2www/pages/site/docs/transport/ssu.html:425
 msgid ""
 "Alice should choose Bob arbitrarily from known peers who seem\n"
 "to be capable of participating in peer tests.  Bob in turn should\n"
@@ -21671,7 +15854,7 @@ msgid ""
 "to designate a new peer as Bob and try again with a different nonce."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:431
+#: i2p2www/pages/site/docs/transport/ssu.html:435
 msgid ""
 "Alice's introduction key is included in all of the PeerTest \n"
 "messages so that she doesn't need to already have an established\n"
@@ -21680,11 +15863,11 @@ msgid ""
 "with either Bob or Charlie, but it is not required."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:449
+#: i2p2www/pages/site/docs/transport/ssu.html:453
 msgid "Transmission window, ACKs and Retransmissions"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:450
+#: i2p2www/pages/site/docs/transport/ssu.html:454
 #, python-format
 msgid ""
 "The DATA message may contain ACKs of full messages and\n"
@@ -21694,7 +15877,7 @@ msgid ""
 "for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:458
+#: i2p2www/pages/site/docs/transport/ssu.html:462
 #, python-format
 msgid ""
 "The details of windowing, ACK, and retransmission strategies are not "
@@ -21709,11 +15892,11 @@ msgid ""
 "See the code for initial, min and max parameters."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:470
+#: i2p2www/pages/site/docs/transport/ssu.html:474
 msgid "Security"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:471
+#: i2p2www/pages/site/docs/transport/ssu.html:475
 msgid ""
 "UDP source addresses may, of course, be spoofed.\n"
 "Additionally, the IPs and ports contained inside specific\n"
@@ -21722,31 +15905,31 @@ msgid ""
 "Also, certain actions and responses may need to be rate-limited."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:479
+#: i2p2www/pages/site/docs/transport/ssu.html:483
 msgid ""
 "The details of validation are not specified\n"
 "here. Implementers should add defenses where appropriate."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:485
+#: i2p2www/pages/site/docs/transport/ssu.html:489
 msgid "Peer capabilities"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:489
+#: i2p2www/pages/site/docs/transport/ssu.html:493
 msgid ""
 "If the peer address contains the 'B' capability, that means \n"
 "they are willing and able to participate in peer tests as\n"
 "a 'Bob' or 'Charlie'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:495
+#: i2p2www/pages/site/docs/transport/ssu.html:499
 msgid ""
 "If the peer address contains the 'C' capability, that means\n"
 "they are willing and able to serve as an introducer - serving\n"
 "as a Bob for an otherwise unreachable Alice."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:504
+#: i2p2www/pages/site/docs/transport/ssu.html:508
 msgid ""
 "Analysis of current SSU performance, including assessment of window size "
 "adjustment\n"
@@ -21755,14 +15938,14 @@ msgid ""
 "performance, is a topic for future work."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:510
+#: i2p2www/pages/site/docs/transport/ssu.html:514
 msgid ""
 "The current implementation repeatedly sends acknowledgments for the same "
 "packets,\n"
 "which unnecessarily increases overhead."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:515
+#: i2p2www/pages/site/docs/transport/ssu.html:519
 msgid ""
 "The default small MTU value of 620 should be analyzed and possibly "
 "increased.\n"
@@ -21771,15 +15954,15 @@ msgid ""
 "Probably not."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:521
+#: i2p2www/pages/site/docs/transport/ssu.html:525
 msgid "The protocol should be extended to exchange MTUs during the setup."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:525
+#: i2p2www/pages/site/docs/transport/ssu.html:529
 msgid "Rekeying is currently unimplemented and may never be."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:529
+#: i2p2www/pages/site/docs/transport/ssu.html:533
 msgid ""
 "The potential use of the 'challenge' fields in RelayIntro and "
 "RelayResponse,\n"
@@ -21787,7 +15970,7 @@ msgid ""
 "undocumented."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:534
+#: i2p2www/pages/site/docs/transport/ssu.html:538
 msgid ""
 "Instead of a single fragment per packet, a more efficient\n"
 "strategy may be to bundle multiple message fragments into the same "
@@ -21795,7 +15978,7 @@ msgid ""
 "so long as it doesn't exceed the MTU."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:540
+#: i2p2www/pages/site/docs/transport/ssu.html:544
 msgid ""
 "A set of fixed packet sizes may be appropriate to further hide the data \n"
 "fragmentation to external adversaries, but the tunnel, garlic, and end to"
@@ -21803,34 +15986,34 @@ msgid ""
 "end padding should be sufficient for most needs until then."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:546
+#: i2p2www/pages/site/docs/transport/ssu.html:550
 msgid ""
 "Why are introduction keys the same as the router hash, should it be "
 "changed, would there be any benefit?"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:550
+#: i2p2www/pages/site/docs/transport/ssu.html:554
 msgid "Capacities appear to be unused."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:554
+#: i2p2www/pages/site/docs/transport/ssu.html:558
 msgid ""
 "Signed-on times in SessionCreated and SessionConfirmed appear to be "
 "unused or unverified."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:559
+#: i2p2www/pages/site/docs/transport/ssu.html:563
 msgid "Implementation Diagram"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:560
+#: i2p2www/pages/site/docs/transport/ssu.html:564
 msgid ""
 "This diagram\n"
 "should accurately reflect the current implementation, however there may "
 "be small differences."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:568
+#: i2p2www/pages/site/docs/transport/ssu.html:572
 msgid "Now on the SSU specification page"
 msgstr ""
 
@@ -22626,6 +16809,10 @@ msgstr ""
 msgid "Tunnel design discussion"
 msgstr ""
 
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:21
+msgid "Peer selection"
+msgstr ""
+
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:23
 msgid "Meeting 125 (~13:12-13:30)"
 msgstr ""
@@ -22801,5202 +16988,3 @@ msgid ""
 "conclusion is not supported by the paper."
 msgstr ""
 
-#: i2p2www/pages/site/get-involved/donate.html:4
-msgid ""
-"Thank you for your interest in contributing to I2P!\n"
-"The details of how you\n"
-"can make your contribution are provided below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:13
-#, python-format
-msgid "You can donate direct via PayPal to the account \"%(account)s\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:19
-msgid "One time donation:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:33
-msgid "Donate 10 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:41
-#: i2p2www/pages/site/get-involved/donate.html:53
-#: i2p2www/pages/site/get-involved/donate.html:65
-#: i2p2www/pages/site/get-involved/donate.html:77
-msgid "I2P donation "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:47
-msgid "Donate 20 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:59
-msgid "Donate 30 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:71
-msgid "Donate 50 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:86
-msgid "Flattr this"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:90
-#, python-format
-msgid ""
-"As of December 2010, eche|on has been running a Bitcoin account for the I2P project. \n"
-"If you'd like to donate using Bitcoin, just transfer your desired amount "
-"of coins to the account \n"
-"%(account)s and leave eche|on a note if you'd like your donation "
-"to be mentioned on the I2P webpage."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:95
-msgid ""
-"If you want to keep more or less anonymous, the option to send money via "
-"mail is also available. But it is less secure\n"
-"as the envelope can be lost on the way to us."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:99
-#, python-format
-msgid ""
-"If you'd like to donate via  snail mail, send an email to %(email)s\n"
-" and you'll receive an email with instructions detailing how to proceed."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:104
-#, python-format
-msgid ""
-"In the meantime, feel free to take a look at the generous donations that "
-"have been\n"
-"given in support of the I2P Project at the hall of fame."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:2
-msgid "Get Involved!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:4
-msgid "We need your help!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:5
-msgid ""
-"To get involved, please feel free to join us on the #i2p IRC channel (on\n"
-"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or "
-"irc.postman.i2p)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:9
-#, python-format
-msgid ""
-"If you're interested in joining our team, please"
-" get in\n"
-"touch as we're always looking for eager contributors!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:13
-msgid ""
-"We need help in many areas, and you don't need to know Java to "
-"contribute!\n"
-"Here's a list to help you get started!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:18
-msgid "Spread the Word!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:19
-msgid ""
-"Tell people about I2P on forums, blogs, and comments to articles.\n"
-"Fix up the Wikipedia article about I2P in your language.\n"
-"Tell your friends."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:24
-msgid "Testing"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:25
-#, python-format
-msgid ""
-"Run the latest builds from monotone\n"
-"and report results on #i2p or as bugs on Trac."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:30
-msgid ""
-"Help fix the parts of the website that are outdated or incomplete.\n"
-"Translate pages into other languages."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:34
-msgid "Pictures"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:35
-msgid "Make some more pictures, fix the old ones on the website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:39
-msgid "Make an eepsite! Add some content! Contribute to the community!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:42
-msgid "Services"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:43
-msgid ""
-"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n"
-"a naming service, a search engine, an eepsite monitor... many of these\n"
-"aren't that hard."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:49
-#, python-format
-msgid ""
-"Write or port applications for I2P! There's some guidelines and\n"
-"a list of ideas on the applications page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:53
-msgid "Coding"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:54
-#, python-format
-msgid ""
-"There's plenty to do if you know Java or are ready to learn.\n"
-"Check for open tickets on Trac\n"
-"or the TODO list on %(zzz)s for\n"
-"some ideas on where to start.\n"
-"See the new developer's guide for details."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:61
-msgid "Translation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:62
-#, python-format
-msgid ""
-"Help translate the website and the software into your language.\n"
-"See the new translator's guide for details."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:66
-msgid "Analysis"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:67
-#, python-format
-msgid ""
-"Study or test the code to look for vulnerabilities.\n"
-"Both anonymity vulnerabilities from the various\n"
-"threat models,\n"
-"and DOS and other weaknesses due to securities holes,\n"
-"need researching."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:7
-msgid ""
-"Include some seed data in the distribution so a central reseed location "
-"isn't required?"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:10
-#, python-format
-msgid ""
-"Reachability Mapping / handle peers partially reachable / enhanced restricted routes"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:13
-msgid "Improve help pages and website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:14
-msgid "More translations"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:15
-msgid "SSU disconnect message"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:16
-msgid "Iterative floodfill lookups"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:21
-msgid "Full review of anonymity issues and other vulnerabilities"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:22
-msgid ""
-"Reduce memory usage, remove debugging overhead, make it run better on "
-"slow and embedded machines"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:25
-msgid "Docs"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:30
-msgid "Full restricted routes"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:35
-msgid "Tunnel mixing and padding"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:36
-msgid "User defined message delays"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:39
-#, python-format
-msgid ""
-"Please see the TODO list for more detailed info "
-"about some of these tasks."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:4
-msgid "I2P Project Targets"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:5
-#, python-format
-msgid ""
-"Below is a more detailed (yet still incomplete) discussion of the major "
-"areas\n"
-"of future development on the core I2P network, spanning the plausibly "
-"planned\n"
-"releases. This does not include stego transports, porting to wireless "
-"devices,\n"
-"or tools to secure the local machine, nor does it include client "
-"applications\n"
-"that will be essential in I2P's success. There are probably other things "
-"that\n"
-"will come up, especially as I2P gets more peer review, but these are the "
-"main\n"
-"'big things'. See also the roadmap. Want to "
-"help?\n"
-"Get involved!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:16
-#: i2p2www/pages/site/get-involved/todo.html:54
-msgid "Core functionality"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:18
-#: i2p2www/pages/site/get-involved/todo.html:57
-msgid "NAT/Firewall bridging via 1-hop restricted routes"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:21
-#: i2p2www/pages/site/get-involved/todo.html:130
-msgid "High degree transport layer with UDP, NBIO, or NIO"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:24
-#: i2p2www/pages/site/get-involved/todo.html:218
-msgid "NetworkDB and profile tuning and ejection policy for large nets"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:28
-#: i2p2www/pages/site/get-involved/todo.html:242
-msgid "Security / anonymity"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:30
-#: i2p2www/pages/site/get-involved/todo.html:245
-msgid ""
-"Per-hop tunnel id & new permuted TunnelVerificationStructure "
-"encryption"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:33
-#: i2p2www/pages/site/get-involved/todo.html:295
-msgid "Strict ordering of participants within tunnels"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:36
-msgid "Randomly permuted tunnel lengths"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:39
-#: i2p2www/pages/site/get-involved/todo.html:357
-msgid "Full blown n-hop restricted routes with optional trusted links"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:42
-#: i2p2www/pages/site/get-involved/todo.html:376
-msgid "Hashcash for routerIdentity, destination, and tunnel request"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:45
-#: i2p2www/pages/site/get-involved/todo.html:405
-msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:48
-#: i2p2www/pages/site/get-involved/todo.html:442
-msgid "Stop & go mix w/ garlics & tunnels"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:62
-msgid "Implemented in I2P 0.6.0.6"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:63
-msgid ""
-"The functionality of allowing routers to fully participate within the "
-"network \n"
-"while behind firewalls and NATs that they do not control requires some "
-"basic \n"
-"restricted route operation (since those peers will not be able to receive"
-" \n"
-"inbound connections). To do this successfully, you consider peers one of"
-" \n"
-"two ways:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:73
-msgid ""
-"Peers who have reachable interfaces - these peers do not need to \n"
-"do anything special"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:77
-msgid ""
-"Peers who do not have reachable interfaces - these peers must "
-"build \n"
-"a tunnel pointing at them where the gateway is one of the peers they have"
-" \n"
-"established a connection with who has both a publicly reachable interface"
-" \n"
-"and who has agreed to serve as their 'introducer'."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:85
-msgid ""
-"To do this, peers who have no IP address simply connect to a few peers, \n"
-"build a tunnel through them, and publish a reference to those tunnels "
-"within \n"
-"their RouterInfo structure in the network database."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:90
-msgid ""
-"When someone wants to contact any particular router, they first must get"
-" \n"
-"its RouterInfo from the network database, which will tell them whether "
-"they \n"
-"can connect directly (e.g. the peer has a publicly reachable interface) \n"
-"or whether they need to contact them indirectly. Direct connections occur"
-" \n"
-"as normal, while indirect connections are done through one of the "
-"published \n"
-"tunnels."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:98
-msgid ""
-"When a router just wants to get a message or two to a specific hidden "
-"peer, \n"
-"they can just use the indirect tunnel for sending the payload. However, \n"
-"if the router wants to talk to the hidden peer often (for instance, as "
-"part \n"
-"of a tunnel), they will send a garlic routed message through the indirect"
-" \n"
-"tunnel to that hidden peer which unwraps to contain a message which "
-"should \n"
-"be sent to the originating router. That hidden peer then establishes an \n"
-"outbound connection to the originating router and from then on, those two"
-" \n"
-"routers can talk to each other directly over that newly established "
-"direct \n"
-"connection."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:109
-msgid ""
-"Of course, that only works if the originating peer can receive "
-"connections \n"
-"(they aren't also hidden). However, if the originating peer is hidden, "
-"they \n"
-"can simply direct the garlic routed message to come back to the "
-"originating \n"
-"peer's inbound tunnel."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:115
-msgid ""
-"This is not meant to provide a way for a peer's IP address to be "
-"concealed, \n"
-"merely as a way to let people behind firewalls and NATs fully operate "
-"within \n"
-"the network. Concealing the peer's IP address adds a little more work, as"
-" \n"
-"described below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:121
-msgid ""
-"With this technique, any router can participate as any part of a tunnel."
-" \n"
-"For efficiency purposes, a hidden peer would be a bad choice for an "
-"inbound \n"
-"gateway, and within any given tunnel, two neighboring peers wouldn't want"
-" \n"
-"to be hidden. But that is not technically necessary."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:133
-msgid "Both UDP and NIO have been Implemented in I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:134
-msgid ""
-"Standard TCP communication in Java generally requires blocking socket \n"
-"calls, and to keep a blocked socket from hanging the entire system, those"
-" \n"
-"blocking calls are done on their own threads. Our current TCP transport \n"
-"is implemented in a naive fashion - for each peer we are talking to, we \n"
-"have one thread reading and one thread writing. The reader thread simply"
-" \n"
-"loops a bunch of read() calls, building I2NP messages and adding them \n"
-"to our internal inbound message queue, and the writer thread pulls "
-"messages \n"
-"off a per-connection outbound message queue and shoves the data through \n"
-"write() calls."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:145
-msgid ""
-"We do this fairly efficiently, from a CPU perspective - at any time, \n"
-"almost all of these threads are sitting idle, blocked waiting for "
-"something \n"
-"to do. However, each thread consumes real resources (on older Linux "
-"kernels, \n"
-"for instance, each thread would often be implemented as a fork()'ed "
-"process). \n"
-"As the network grows, the number of peers each router will want to talk \n"
-"with will increase (remember, I2P is fully connected, meaning that any \n"
-"given peer should know how to get a message to any other peer, and "
-"restricted \n"
-"route support will probably not significantly reduce the number of "
-"connections \n"
-"necessary). This means that with a 100,000 router network, each router \n"
-"will have up to 199,998 threads just to deal with the TCP connections!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:157
-msgid ""
-"Obviously, that just won't work. We need to use a transport layer that \n"
-"can scale. In Java, we have two main camps:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:162
-#, python-format
-msgid ""
-"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:165
-msgid ""
-"Sending and receiving UDP datagrams is a connectionless operation - if \n"
-"we are communicating with 100,000 peers, we simply stick the UDP packets"
-" \n"
-"in a queue and have a single thread pulling them off the queue and "
-"shoving \n"
-"them out the pipe (and to receive, have a single thread pulling in any \n"
-"UDP packets received and adding them to an inbound queue)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:172
-msgid ""
-"However, moving to UDP means losing the benefits of TCP's ordering, "
-"congestion \n"
-"control, MTU discovery, etc. Implementing that code will take significant"
-" \n"
-"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n"
-"a while ago I was taking some measurements in the simulator and on the \n"
-"live net, and the vast majority of messages transferred would fit easily"
-" \n"
-"within a single unfragmented UDP packet, and the largest of the messages"
-" \n"
-"would fit within 20-30 packets. As mule pointed out, TCP adds a "
-"significant \n"
-"overhead when dealing with so many small packets, as the ACKs are within"
-" \n"
-"an order of magnitude in size. With UDP, we can optimize the transport \n"
-"for both efficiency and resilience by taking into account I2P's "
-"particular \n"
-"needs."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:185
-msgid "It will be a lot of work though."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:188
-msgid "NIO or NBIO"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:189
-msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:192
-msgid ""
-"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java"
-" \n"
-"developers to take advantage of the operating system's nonblocking IO \n"
-"capabilities - allowing you to maintain a large number of concurrent IO \n"
-"operations without requiring a separate thread for each. There is much \n"
-"promise with this approach, as we can scalable handle a large number of \n"
-"concurrent connections and we don't have to write a mini-TCP stack with \n"
-"UDP. However, the NIO packages have not proven themselves to be battle-"
-"ready, \n"
-"as the Freenet developer's found. In addition, requiring NIO support "
-"would \n"
-"mean we can't run on any of the open source JVMs like Kaffe, \n"
-"as GNU/Classpath has only "
-"limited \n"
-"support for NIO. (note: this may not be the case anymore, as there \n"
-"has been some progress on Classpath's NIO, but it is an unknown "
-"quantity)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:206
-#, python-format
-msgid ""
-"Another alternative along the same lines is the Non"
-" \n"
-"Blocking I/O package - essentially a cleanroom NIO implementation \n"
-"(written before NIO was around). It works by using some native OS code \n"
-"to do the nonblocking IO, passing off events through Java. It seems to \n"
-"be working with Kaffe, though there doesn't seem to be much development \n"
-"activity on it lately (likely due to 1.4's NIO deployment)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:221
-msgid ""
-"Within the current network database and profile management "
-"implementation, \n"
-"we have taken the liberty of some practical shortcuts. For instance, we \n"
-"don't have the code to drop peer references from the K-buckets, as we \n"
-"don't have enough peers to even plausibly fill any of them, so instead, \n"
-"we just keep the peers in whatever bucket is appropriate. Another example"
-" \n"
-"deals with the peer profiles - the memory required to maintain each "
-"peer's \n"
-"profile is small enough that we can keep thousands of full blown profiles"
-" \n"
-"in memory without problems. While we have the capacity to use trimmed \n"
-"down profiles (which we can maintain 100s of thousands in memory), we \n"
-"don't have any code to deal with moving a profile from a \"minimal "
-"profile\" \n"
-"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to"
-" simply \n"
-"eject a profile altogether. It just wouldn't be practical to write that \n"
-"code yet, since we aren't going to need it for a while."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:236
-msgid ""
-"That said, as the network grows we are going to want to keep these "
-"considerations \n"
-"in mind. We will have some work to do, but we can put it off for later."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:248
-#: i2p2www/pages/site/get-involved/todo.html:332
-#, python-format
-msgid ""
-"Addressed in I2P 0.5 as documented elsewhere"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:251
-msgid ""
-"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n"
-"going to Dave, then to Charlie, then Bob, and finally Alice "
-"(A<--B<--C<--D<--E), \n"
-"all five of them will know they are participating in tunnel \"123\", as \n"
-"the messages are tagged as such. What we want to do is give each hop "
-"their \n"
-"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n"
-"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n"
-"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n"
-"the tunnel had the same tunnel ID, collusion attacks aren't much work."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:261
-msgid ""
-"Adding a unique tunnel ID per hop isn't hard, but by itself, "
-"insufficient. \n"
-"If Dave and Bob are under the control of the same attacker, they wouldn't"
-" \n"
-"be able to tell they are in the same tunnel due to the tunnel ID, but \n"
-"would be able to tell by the message bodies and verification structures \n"
-"by simply comparing them. To prevent that, the tunnel must use layered \n"
-"encryption along the path, both on the payload of the tunneled message \n"
-"and on the verification structure (used to prevent simple tagging "
-"attacks). \n"
-"This requires some simple modifications to the TunnelMessage, as well \n"
-"as the inclusion of per-hop secret keys delivered during tunnel creation"
-" \n"
-"and given to the tunnel's gateway. We must fix a maximum tunnel length \n"
-"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n"
-"of the 16 delivered secret keys, in reverse order, and to encrypt the \n"
-"signature of the hash of the (encrypted) payload at each step. The "
-"gateway \n"
-"then sends that 16-step encrypted message, along with a 16-step and "
-"16-wide \n"
-"encrypted mapping to the first hop, which then decrypts the mapping and \n"
-"the payload with their secret key, looking in the 16-wide mapping for \n"
-"the entry associated with their own hop (keyed by the per-hop tunnel ID)"
-" \n"
-"and verifying the payload by checking it against the associated signed \n"
-"hash."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:282
-msgid ""
-"The tunnel gateway does still have more information than the other peers"
-" \n"
-"in the tunnel, and compromising both the gateway and a tunnel participant"
-" \n"
-"would allow those peers to collude, exposing the fact that they are both"
-" \n"
-"in the same tunnel. In addition, neighboring peers know that they are \n"
-"in the same tunnel anyway, as they know who they send the message to (and"
-" \n"
-"with IP-based transports without restricted routes, they know who they \n"
-"got it from). However, the above two techniques significantly increase \n"
-"the cost of gaining meaningful samples when dealing with longer tunnels."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:298
-msgid "Implemented in release 0.6.2"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:301
-#, python-format
-msgid ""
-"As Connelly proposed to deal with the\n"
-"predecessor attack (2008\n"
-"update), keeping the order of peers within our tunnels consistent \n"
-"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n"
-"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n"
-"get to substantially sample Alice's peer selection group. We may even \n"
-"want to explicitly allow Bob to participate in Alice's tunnels in only \n"
-"one way - receiving a message from Dave and sending it to Charlie - and \n"
-"if any of those peers are not available to participate in the tunnel (due"
-" \n"
-"to overload, network disconnection, etc), avoid asking Bob to participate"
-" \n"
-"in any tunnels until they are back online."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:316
-msgid ""
-"More analysis is necessary for revising the tunnel creation - at the \n"
-"moment, we simply select and order randomly within the peer's top tier \n"
-"of peers (ones with fast + high capacity)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:321
-msgid ""
-"Adding a strict ordering to peers in a tunnel also improves the anonymity"
-" \n"
-"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway"
-" \n"
-"is always the same would be particularly damning. However, peers with \n"
-"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n"
-"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n"
-"duration) minutes, use a 1-hop tunnel)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:338
-msgid ""
-"Without tunnel length permutation, if someone were to somehow detect that"
-" \n"
-"a destination had a particular number of hops, it might be able to use "
-"that \n"
-"information to identify the router the destination is located on, per the"
-" \n"
-"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n"
-"receives a tunnel message from Charlie and forwards it to Alice, Bob "
-"knows \n"
-"Alice is the final router in the tunnel. If Bob were to identify what "
-"destination \n"
-"that tunnel served (by means of colluding with the gateway and harvesting"
-" \n"
-"the network database for all of the LeaseSets), he would know the router"
-" \n"
-"on which that destination is located (and without restricted routes, that"
-" \n"
-"would mean what IP address the destination is on)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:350
-msgid ""
-"It is to counter user behavior that tunnel lengths should be permuted, \n"
-"using algorithms based on the length requested (for example, the 1/MTBF \n"
-"length change for 0-hop tunnels outlined above)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:360
-msgid ""
-"The restricted route functionality described before was simply a "
-"functional \n"
-"issue - how to let peers who would not otherwise be able to communicate \n"
-"do so. However, the concept of allowing restricted routes includes "
-"additional \n"
-"capabilities. For instance, if a router absolutely cannot risk "
-"communicating \n"
-"directly with any untrusted peers, they can set up trusted links through"
-" \n"
-"those peers, using them to both send and receive all of its messages. \n"
-"Those hidden peers who want to be completely isolated would also refuse \n"
-"to connect to peers who attempt to get them to (as demonstrated by the \n"
-"garlic routing technique outlined before) - they can simply take the "
-"garlic \n"
-"clove that has a request for delivery to a particular peer and tunnel \n"
-"route that message out one of the hidden peer's trusted links with "
-"instructions \n"
-"to forward it as requested."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:379
-#, python-format
-msgid ""
-"Within the network, we will want some way to deter people from consuming"
-" \n"
-"too many resources or from creating so many peers to mount a Sybil \n"
-"attack. Traditional techniques such as having a peer see who is "
-"requesting \n"
-"a resource or running a peer aren't appropriate for use within I2P, as \n"
-"doing so would compromise the anonymity of the system. Instead, we want \n"
-"to make certain requests \"expensive\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:387
-msgid ""
-"Hashcash is one technique that \n"
-"we can use to anonymously increase the \"cost\" of doing certain "
-"activities, \n"
-"such as creating a new router identity (done only once on installation),"
-" \n"
-"creating a new destination (done only once when creating a service), or \n"
-"requesting that a peer participate in a tunnel (done often, perhaps 2-300"
-" \n"
-"times per hour). We don't know the \"correct\" cost of each type of "
-"certificate \n"
-"yet, but with some research and experimentation, we could set a base "
-"level \n"
-"that is sufficiently expensive while not an excessive burden for people \n"
-"with few resources."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:398
-msgid ""
-"There are a few other algorithms that we can explore for making those \n"
-"requests for resources \"nonfree\", and further research on that front is"
-" \n"
-"appropriate."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:408
-#, python-format
-msgid ""
-"To powerful passive external observers as well as large colluding "
-"internal \n"
-"observers, standard tunnel routing is vulnerable to traffic analysis "
-"attacks \n"
-"- simply watching the size and frequency of messages being passed between"
-" \n"
-"routers. To defend against these, we will want to essentially turn some \n"
-"of the tunnels into its own mix cascade - delaying messages received at \n"
-"the gateway and passing them in batches, reordering them as necessary, \n"
-"and injecting dummy messages (indistinguishable from other \"real\" "
-"tunnel \n"
-"messages by peers in the path). There has been a significant amount of \n"
-"research \n"
-"on these algorithms that we can lean on prior to implementing the various"
-" \n"
-"tunnel mixing strategies."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:421
-msgid ""
-"In addition to the anonymity aspects of more varied tunnel operation, \n"
-"there is a functional dimension as well. Each peer only has a certain \n"
-"amount of data they can route for the network, and to keep any particular"
-" \n"
-"tunnel from consuming an unreasonable portion of that bandwidth, they \n"
-"will want to include some throttles on the tunnel. For instance, a tunnel"
-" \n"
-"may be configured to throttle itself after passing 600 messages (1 per \n"
-"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n"
-"last minute). Excess messages may be delayed or summarily dropped. With \n"
-"this sort of throttling, peers can provide ATM-like QoS support for their"
-" \n"
-"tunnels, refusing to agree to allocate more bandwidth than the peer has \n"
-"available."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:434
-msgid ""
-"In addition, we may want to implement code to dynamically reroute tunnels"
-" \n"
-"to avoid failed peers or to inject additional hops into the path. This \n"
-"can be done by garlic routing a message to any particular peer in a "
-"tunnel \n"
-"with instructions to redefine the next-hop in the tunnel."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:445
-msgid ""
-"Beyond the per-tunnel batching and mixing strategy, there are further \n"
-"capabilities for protecting against powerful attackers, such as allowing"
-" \n"
-"each step in a garlic routed path to define a delay or window in which \n"
-"it should be forwarded on. This would enable protections against the long"
-" \n"
-"term intersection attack, as a peer could send a message that looks "
-"perfectly \n"
-"standard to most peers that pass it along, except at any peers where the"
-" \n"
-"clove exposed includes delay instructions."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:457
-#, python-format
-msgid ""
-"Performance related improvements are listed on the\n"
-"Performance page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2
-msgid "Bounty Arabic translation of webpage and router console"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3
-#: i2p2www/pages/site/get-involved/bounties/index.html:119
-msgid "Arabic translation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2P echelon set out this bounty for translation\n"
-"of the I2P web page and I2P router console into Arabic."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12
-msgid "This bounty is set into 2 subparts:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14
-msgid "Part 1 is translation of the webpage."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17
-msgid ""
-"For collecting the bounty of 20 BTC you need to translate the following "
-"pages:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25
-msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27
-msgid ""
-"Part 2 is the translation of the router console. The router console was\n"
-"partly translated and the bounty of 80 BTC was paid to hamada."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34
-msgid "Judge is echelon."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2
-msgid "Bounty creating a I2P native Bitcoin client"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3
-msgid "BTC I2P native client"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6
-msgid ""
-"For a future of I2P and attract more people\n"
-"into I2P this bounty is to create a I2P native Bitcoin client. \n"
-"It should integrate with other client via the I2P network and via "
-"gateways to\n"
-"the existant bitcoin network."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15
-msgid "Judge is psychonaut who donated the first 30 € to this bounty."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
-msgid "Bounty datastorage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:3
-msgid "datastore"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:6
-msgid ""
-"To improve I2P's usage and to be independent of routers \n"
-"online status we want a datastorage as a extension to I2P.\n"
-"Like in Freenet the datastorage should be distributed and every\n"
-"participating node should be able to configure his options.\n"
-"The files should be saved in chunks and at least 2-3 times to\n"
-"obtain redundancy. Usage of storage space should be auto balanced.\n"
-"As it is a extra application, it should work flawless within I2P and\n"
-"cooperate nice with the I2P router. Maybe a integration within the\n"
-"webpage/router could be done."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:17
-msgid ""
-"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n"
-"\"eepsites in datastorage\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:21
-msgid ""
-"The frost for I2P datastorage bounty is paid for a frost like program \n"
-"with which files/messages are stored into database and got from database."
-"\n"
-"It needs to work with a GUI."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:26
-msgid ""
-"The eepsite served out of I2P datastorage extends a I2P router to send\n"
-"out eepsites out of the I2P datastorage. All files for eepsites need to "
-"be\n"
-"saved inside of datastorage and are taken from it.\n"
-"Extension:\n"
-"For better integration all datastorage participants could serve that "
-"eepsite."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:36
-msgid ""
-"For bounties to be declared done and paid, we need the program AND the "
-"source.\n"
-"Source and code need to be licensed under a free license (free to change "
-"and \n"
-"free to distribute)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2
-msgid "Bounty I2P package in Debian and Ubuntu mirrors"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3
-msgid "I2P Ubuntu/Debian package"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6
-msgid ""
-"For the future of I2P and in order to attract more people\n"
-"to I2P, this bounty was set for including an I2P package into the Ubuntu "
-"and Debian \n"
-"archive mirrors.\n"
-"To claim this bounty, the I2P router package needs to be available from\n"
-"Ubuntu and Debian archive mirrors and Debian bug \n"
-"448638 \n"
-"needs to be closed successfully."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2
-msgid "Bounty I2PHex code implementation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3
-msgid "i2phex code implementation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2PHex P2P ArneBab setout the bounty for implementing actual\n"
-"Phex code onto I2PHex."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:5
-msgid "Bounties for I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:6
-msgid ""
-"While we always gratefully accept any contributions of code, \n"
-"documentation, and the like, there are other ways to help I2P move \n"
-"forward.  As with any open source project, our goals would be achieved "
-"more \n"
-"rapidly if we were able to support all of our contributors to work on \n"
-"I2P full time.  However, as with any open source project, that's not a \n"
-"possibility.  Instead, we are making use of a bounty system, whereby \n"
-"anyone can get support for working on something that people want \n"
-"implemented, and people who want to contribute to I2P can be assured that"
-" \n"
-"their support goes to what they care about."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:18
-msgid ""
-"We are also keeping open the ability for people who want to support I2P \n"
-"but don't have strong feelings about the bounties available.  Those "
-"people\n"
-"can simply put their trust in the I2P team to do what we feel is best by\n"
-"donating to a catch-all general fund that will be used as deemed \n"
-"necessary - allocated to various bounties, covering incidentals (hosting,"
-" \n"
-"etc), and the like."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:27
-msgid "Current bounties"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-#: i2p2www/pages/site/get-involved/bounties/index.html:112
-msgid "Name"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-#: i2p2www/pages/site/get-involved/bounties/index.html:112
-msgid "Status"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-msgid "Judge"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-msgid "Bounty"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:32
-msgid "Frost for I2P datastorage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:33
-#: i2p2www/pages/site/get-involved/bounties/index.html:40
-#: i2p2www/pages/site/get-involved/bounties/index.html:47
-#: i2p2www/pages/site/get-involved/bounties/index.html:54
-#: i2p2www/pages/site/get-involved/bounties/index.html:61
-#: i2p2www/pages/site/get-involved/bounties/index.html:82
-#: i2p2www/pages/site/get-involved/bounties/index.html:89
-msgid "Proposal in development"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:39
-msgid "Eepsites served out of I2P datastorage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:46
-msgid "Backporting Phex code onto I2PHex"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:53
-msgid "Make I2P IPv6 native"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:60
-msgid "I2P package in Debian and Ubuntu mirrors"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:68
-msgid "Done, phase of verification"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:74
-msgid "Unit tests and Multi-router Simulation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:75
-msgid "Partly done, partly in work, partly still open"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:96
-msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:101
-msgid "Bundling bounties"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:102
-msgid "Proposed"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:109
-msgid "Claimed bounties"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:112
-msgid "Dev team"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:114
-msgid "Setting up a SILC server"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:124
-msgid "Datastore over I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:129
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
-msgid "Russian translation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:134
-msgid "Swarming file transfer"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:139
-msgid "Streaming library window size"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:144
-msgid "IRC connect time monitor"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:149
-msgid "Unit tests (part 1)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:161
-msgid ""
-"Dev lists anyone who may already be working on the bounty - collaboration"
-" is\n"
-"preferred, so if you're interested in working on it, please contact one "
-"of the\n"
-"people listed!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2
-msgid "Bounty I2P IPv6 native"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3
-msgid "native IPv6 I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6
-msgid ""
-"For a future of I2P and attract more people\n"
-"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n"
-"To claim this bounty, the I2P router needs to run full on native\n"
-"IPv6 connections like it does on IPv4."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:15
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
-msgid ""
-"For bounties to be declared done and paid, we need the plugin AND the "
-"source.\n"
-"Source and code need to be licensed under a free license (free to change "
-"and \n"
-"free to distribute)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:2
-msgid "NetDB Backend"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:3
-msgid "netDB backend"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:7
-msgid ""
-"The current NetDB implementation (namely the FloodFill system)\n"
-"needs to be extended with another backend to improve reliability,\n"
-"reduce attack surface and solve the scalability issue for the \n"
-"coming years."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:14
-msgid ""
-"A solution likely based on a DHT will be investigated and \n"
-"finally implemented."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2
-msgid "Bounty russian translation of webpage and router console"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2P a anonymous donator set out the bounty for translation\n"
-"of the I2P web page and I2P router console into russian language."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17
-msgid ""
-"For collecting the bounty of $115 USD you need to translate the following"
-" pages:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30
-msgid ""
-"Part 2 is the translation of the router console. The whole router console"
-" needs\n"
-"to be translated to collect the bounty of $115 USD."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37
-msgid "Judge is the russian donor."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:2
-msgid "Bounty migrate I2P IRC to SILC"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:3
-msgid "I2P silc server"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:7
-msgid ""
-"For a future of I2P and attract more people\n"
-"into I2P this bounty is to setup and host a I2P SILC server.   \n"
-"This will allow people to send files over their messaging servers and "
-"have intrinsic security built into the protocol."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:12
-msgid ""
-"A silc server needs to be set up and run for at least 3 month time to get"
-" payed. \n"
-"A second server should be set up, to."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:16
-msgid ""
-"Bounty was withdrawn and money donated to returningnovice and general "
-"fund."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:22
-msgid "Judge is An Anonymous Secret Society, society@mail.i2p."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7
-msgid ""
-"Beside of I2P we want to encourage users\n"
-"to care more about anonymity and security. As I2P is a low \n"
-"latency network with its natural limits, the software SYNDIE\n"
-"can overcome some of these limits and provide better anonymity\n"
-"for people who really need it."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14
-msgid ""
-"For our bad sake the syndie project was out of development for \n"
-"quite a long time yet (5 years). To get a fresh and new built \n"
-"with needed bugfixes we set out this bounty. Also syndie needs\n"
-"some enhancements and a better GUI for users to work with it.\n"
-"Current bounty sum is 50 Bitcoin."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22
-msgid ""
-"The latest Syndie coding rally did improve the situation of the\n"
-"Syndie package dramatically. A new Syndie package with bugfixes\n"
-"was created and made available on different webpages.\n"
-"As a result of this work, the bounty sum was reduced and\n"
-"the withdrawn money moved to the IPv6 bounty."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2
-msgid "Bounty unittests"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3
-msgid "unit test"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7
-msgid ""
-"To improve I2P's maintainability, we want to have a solid set of\n"
-"automated unit tests for the critical code.  While we do have some\n"
-"unit tests at the moment, they are ad-hoc and partly unfinished.  \n"
-"This bounty is for someone to check the existing tests and move over\n"
-"old ones to jUnit, automate their execution, extend them to provide \n"
-"better code coverage, and publish the report online.  Its a massive \n"
-"effort, but can be broken down into phases, listed below (phase 2 \n"
-"must occur first, but further phases may happen in any order).\n"
-"As this needs some reading of code, it is the best start point for\n"
-"new devs to get a good overview of I2P code and coding. A good job\n"
-"for college students, interns or anyone who is just interested."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20
-msgid ""
-"Take care! Jobs and bounties shuffled a bit!\n"
-"Phase 6,7 and 8 are still open!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112
-#, python-format
-msgid "Phase %(phase)s:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27
-msgid "CI jenkins and IRC bot"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114
-#, python-format
-msgid "Bounty: %(euro)s €"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29
-msgid "server runs and this section is blocked"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31
-msgid ""
-"To collect this bounty, a continuous integration server (Jenkins,\n"
-"old name was Hudson) must be set up and a connected IRC bot needs \n"
-"to set up in the channel #i2p-dev on IRC2p network to print out\n"
-"results of build tests.
            \n"
-"The server needs to be run long term."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41
-msgid "Check existing SDK tests"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69
-msgid "paid to str4d"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45
-#, python-format
-msgid ""
-"To collect this bounty, the existing SDK tests must be checked \n"
-"and made to work again. The need to be integrated into the ant \n"
-"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g."
-" \n"
-"Clover).  The ant script\n"
-"must be capable of generating test status results as a web page, \n"
-"which will be published online."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56
-msgid "SDK test coverage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80
-msgid "paid to unittests dev team"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60
-msgid ""
-"To collect this bounty, the automated unit tests of the SDK \n"
-"(i2p/core/java/src) must work again."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67
-msgid "Router test migration"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71
-msgid ""
-"As with phase 2, the existing unit tests for the router must be\n"
-"moved over to the automated system."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78
-msgid "Router test coverage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82
-msgid ""
-"To collect this bounty, the automated unit tests of the router \n"
-"(i2p/router/java/src) must work again."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89
-msgid "Streaming lib tests"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94
-#, python-format
-msgid ""
-"To collect this bounty, a new set of unit tests must meet a \n"
-"measured code coverage of 90% of the streaming lib \n"
-"(i2p/apps/ministreaming/ and i2p/apps/streaming/)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102
-msgid "Unit tests coverage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106
-msgid ""
-"To collect this bounty, all above unit tests must meet the 100%\n"
-"coverage marker (except for log statements)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113
-msgid "MultiRouter simulation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115
-msgid "will be split in more sub-tasks"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117
-msgid ""
-"To collect this bounty, the existing in-memory multi-router\n"
-"simulation must be checked, made work again and extend to simulate\n"
-"lots of routers in memory on a single machine. This bounty will\n"
-"be split in more fine grained subworks."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126
-msgid ""
-"Judge on all these works is the donor and donor decides if a phase is\n"
-"called succesfull done and money can be paid."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2
-msgid "Bounty I2P vuze plugin"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3
-msgid "vuze plugin"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2P torrent P2P I setout the bounty for a working I2P vuze\n"
-"plugin.\n"
-"The plugin needs to be official and submitted to vuze for publication\n"
-"on their webpage/repository for plugins.\n"
-"It should be easy to install and configured, work smooth and flawless.\n"
-"Configuration should be friendly to starters and made easy to be "
-"anonymous.\n"
-"It should work with *.b32.i2p destinations as with signed (516++ bits) \n"
-"destinations."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:2
-msgid "Application Development"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:6
-msgid "Application Development Guide"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:10
-#: i2p2www/pages/site/get-involved/develop/applications.html:16
-msgid "Why write I2P-specific code?"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:11
-#: i2p2www/pages/site/get-involved/develop/applications.html:102
-msgid "Important concepts"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:12
-#: i2p2www/pages/site/get-involved/develop/applications.html:190
-msgid "Development options"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:13
-#: i2p2www/pages/site/get-involved/develop/applications.html:303
-msgid "Start developing - a simple guide"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:18
-#, python-format
-msgid ""
-"There are multiple ways to use applications in I2P.\n"
-"Using I2PTunnel,\n"
-"you can use regular applications without needing to program explicit I2P "
-"support.\n"
-"This is very effective for client-server scenario's,\n"
-"where you need to connect to a single website.\n"
-"You can simply create a tunnel using I2PTunnel to connect to that "
-"website, as shown in Figure 1."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:26
-msgid ""
-"If your application is distributed, it will require connections to a "
-"large amount of peers.\n"
-"Using I2PTunnel, you will need to create a new tunnel for each peer you "
-"want to contact,\n"
-"as shown in Figure 2.\n"
-"This process can of course be automated, but running a lot of I2PTunnel "
-"instances creates a large amount of overhead.\n"
-"In addition, with many protocols you will need to force everyone to \n"
-"use the same set of ports for all peers - e.g. if you want to reliably "
-"run DCC \n"
-"chat, everyone needs to agree that port 10001 is Alice, port 10002 is "
-"Bob, port \n"
-"10003 is Charlie, and so on, since the protocol includes TCP/IP specific "
-"information\n"
-"(host and port)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:37
-msgid ""
-"General network applications often send a lot of additional data that "
-"could be used to identify users.\n"
-"Hostnames, port numbers, time zones, character sets, etc. are often sent "
-"without informing the user.\n"
-"As such, designing the network protocol specifically with anonymity in "
-"mind\n"
-"can avoid compromising user identities."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:43
-msgid ""
-"There are also efficiency considerations to review when determining how "
-"to \n"
-"interact on top of I2P.  The streaming library and things built on top of"
-" it\n"
-"operate with handshakes similar to TCP, while the core I2P protocols "
-"(I2NP and I2CP)\n"
-"are strictly message based (like UDP or in some instances raw IP).  The "
-"important\n"
-"distinction is that with I2P, communication is operating over a long fat "
-"network - \n"
-"each end to end message will have nontrivial latencies, but may contain "
-"payloads \n"
-"of up to several KB.  An application that needs a simple request and "
-"response can get rid\n"
-"of any state and drop the latency incurred by the startup and teardown "
-"handshakes\n"
-"by using (best effort) datagrams without having to worry about MTU "
-"detection or \n"
-"fragmentation of messages."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:57
-#: i2p2www/pages/site/get-involved/develop/applications.html:59
-msgid ""
-"Creating a server-client connection using I2PTunnel only requires "
-"creating a single tunnel."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:59
-msgid "Figure 1:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:64
-#: i2p2www/pages/site/get-involved/develop/applications.html:66
-msgid ""
-"Setting up connections for a peer-to-peer applications requires a very "
-"large amount of tunnels."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:66
-msgid "Figure 2:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:70
-msgid "In summary, a number of reasons to write I2P-specific code:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:74
-msgid ""
-"Creating a large amount of I2PTunnel instances consumes a non-trivial "
-"amount of resources,\n"
-"which is problematic for distributed applications (a new tunnel is "
-"required for each peer)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:78
-msgid ""
-"General network protocols often send a lot of additional data that can be"
-" used to identify users.\n"
-"Programming specifically for I2P allows the creation of a network "
-"protocol\n"
-"that does not leak such information, keeping users anonymous and secure."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:83
-msgid ""
-"Network protocols designed for use on the regular internet can be "
-"inefficient\n"
-"on I2P, which is a network with a much higher latency."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:90
-#, python-format
-msgid ""
-"I2P supports a standard plugins interface for"
-" developers\n"
-"so that applications may be easily integrated and distributed."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:96
-msgid ""
-"Applications written in Java and accessible/runnable\n"
-"using an HTML interface via the standard webapps/app.war\n"
-"may be considered for inclusion in the i2p distribution."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:104
-msgid "There are a few changes that require adjusting to when using I2P:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:108
-msgid "Destination ~= host+port"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:110
-msgid ""
-"An application running on I2P sends messages from and receives messages "
-"to a\n"
-"unique cryptographically secure end point - a \"destination\".  In TCP or"
-" UDP\n"
-"terms, a destination could (largely) be considered the equivalent of a "
-"hostname\n"
-"plus port number pair, though there are a few differences."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:118
-msgid ""
-"An I2P destination itself is a cryptographic construct - all data sent to"
-" one is \n"
-"encrypted as if there were universal deployment of IPsec with the "
-"(anonymized)\n"
-"location of the end point signed as if there were universal deployment of"
-" DNSSEC."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:123
-msgid ""
-"I2P destinations are mobile identifiers - they can be moved from one I2P "
-"router\n"
-"to another (or it can even \"multihome\" - operate on multiple routers at"
-"\n"
-"once).  This is quite different from the TCP or UDP world where a single "
-"end point (port)\n"
-"must stay on a single host."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:130
-msgid ""
-"I2P destinations are ugly and large - behind the scenes, they contain a "
-"2048 bit ElGamal\n"
-"public key for encryption, a 1024 bit DSA public key for signing, and a "
-"variable size \n"
-"certificate, which may contain proof of work or blinded data."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:135
-#, python-format
-msgid ""
-"There are existing ways to refer to these large and ugly destinations by "
-"short\n"
-"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not "
-"guarantee\n"
-"globally uniqueness (since they're stored locally in a database on each "
-"person's machine)\n"
-"and the current mechanism is not especially scalable nor secure (updates "
-"to the host list are\n"
-"managed using \"subscriptions\" to naming services).\n"
-"There may be some secure, human readable, scalable, and globally \n"
-"unique, naming system some day, but applications shouldn't depend upon it"
-" being in place,\n"
-"since there are those who don't think such a beast is possible.\n"
-"Further information on the naming system is "
-"available."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:149
-#, python-format
-msgid ""
-"While most applications do not need to distinguish protocols and ports,\n"
-"I2P does support them. Complex applications may specify a "
-"protocol,\n"
-"from port, and to port, on a per-message basis, to multiplex traffic on\n"
-"a single destination.\n"
-"See the datagram page for details.\n"
-"Simple applications operate by listening for \"all protocols\" on \"all "
-"ports\" of a destination."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:158
-msgid "Anonymity and confidentiality"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:160
-msgid ""
-"I2P has transparent end to end encryption\n"
-"and authentication for all data passed over the network - if Bob sends to"
-" Alice's destination,\n"
-"only Alice's destination can receive it, and if Bob is using the "
-"datagrams or streaming \n"
-"library, Alice knows for certain that Bob's destination is the one who "
-"sent the data."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:167
-msgid ""
-"Of course, I2P transparently anonymizes the\n"
-"data sent between Alice and Bob, but it does nothing to anonymize the "
-"content of what they\n"
-"send.  For instance, if Alice sends Bob a form with her full name, "
-"government IDs, and \n"
-"credit card numbers, there is nothing I2P can do.  As such, protocols and"
-" applications should \n"
-"keep in mind what information they are trying to protect and what "
-"information they are willing\n"
-"to expose."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:176
-msgid "I2P datagrams can be up to several KB"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:178
-#, python-format
-msgid ""
-"Applications that use I2P datagrams (either raw or repliable ones) can "
-"essentially be thought\n"
-"of in terms of UDP - the datagrams are unordered, best effort, and "
-"connectionless - but unlike\n"
-"UDP, applications don't need to worry about MTU detection and can simply "
-"fire off large datagrams.\n"
-"While the upper limit is nominally 32 KB, the message is fragmented for "
-"transport, thus dropping\n"
-"the reliability of the whole. Datagrams over about 10 KB are not "
-"currently recommended.\n"
-"See the datagram page for details.\n"
-"For many applications, 10 KB of data is sufficient for an\n"
-"entire request or response, allowing them to transparently operate in I2P"
-" as a UDP-like \n"
-"application without having to write fragmentation, resends, etc."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:192
-msgid ""
-"There are several means of sending data over I2P, each with their own "
-"pros and cons.\n"
-"The streaming lib is the recommended interface, used by the majority of "
-"I2P applications."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:197
-msgid "Streaming Lib"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:198
-#, python-format
-msgid ""
-"The full streaming library is now the "
-"standard\n"
-"interface. It allows programming using TCP-like sockets, as explained in "
-"the Streaming development guide."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:204
-#, python-format
-msgid ""
-"BOB is the Basic Open Bridge,\n"
-"allowing an application in any language to make streaming connections \n"
-"to and from I2P. At this point in time it lacks UDP support, but UDP "
-"support\n"
-"is planned in the near future. BOB also contains several tools, such as \n"
-"destination key generation, and verification that an address conforms to"
-" \n"
-"I2P specifications. Up to date info and applications that use BOB can be"
-" \n"
-"found at this eepsite."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:217
-msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:218
-#, python-format
-msgid ""
-"SAM is the Simple Anonymous Messaging protocol, "
-"allowing an\n"
-"application written in any language to talk to a SAM bridge through a "
-"plain TCP socket and have\n"
-"that bridge multiplex all of its I2P traffic, transparently coordinating "
-"the encryption/decryption\n"
-"and event based handling.  SAM supports three styles of operation:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:225
-msgid ""
-"streams, for when Alice and Bob want to send data to each other reliably "
-"and in order"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:228
-msgid ""
-"repliable datagrams, for when Alice wants to send Bob a message that Bob "
-"can reply to"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:231
-msgid ""
-"raw datagrams, for when Alice wants to squeeze the most bandwidth and "
-"performance as possible,\n"
-"and Bob doesn't care whether the data's sender is authenticated or not "
-"(e.g. the data transferred\n"
-"is self authenticating)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:237
-msgid ""
-"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n"
-"multiplexing/demultiplexing. Each I2P stream is handled by its own socket"
-" between the application\n"
-"and the SAM bridge. Besides, datagrams can be sent and received by the "
-"application through datagram\n"
-"communications with the SAM bridge."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:244
-#, python-format
-msgid ""
-"SAM V2 is a new version used by imule\n"
-"that fixes some of the problems in SAM.\n"
-"
            \n"
-"SAM V3 is used by imule since version 1.4.0."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:252
-msgid ""
-"The I2PTunnel application allows applications to build specific TCP-like "
-"tunnels to peers \n"
-"by creating either I2PTunnel 'client' applications (which listen on a "
-"specific port and connect\n"
-"to a specific I2P destination whenever a socket to that port is opened) "
-"or I2PTunnel 'server'\n"
-"applications (which listen to a specific I2P destination and whenever it "
-"gets a new I2P \n"
-"connection it outproxies to a specific TCP host/port).  These streams are"
-" 8-bit clean, and are\n"
-"authenticated and secured through the same streaming library that SAM "
-"uses, but there is a \n"
-"nontrivial overhead involved with creating multiple unique I2PTunnel "
-"instances, since each have\n"
-"their own unique I2P destination and their own set of tunnels, keys, etc."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:264
-msgid ""
-"I2P supports a SOCKS V4 and V5 proxy.\n"
-"Outbound connections work well. Inbound (server) and UDP functionality "
-"may be incomplete\n"
-"and untested."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:271
-msgid "Removed"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:272
-msgid ""
-"There used to be a simple \"ministreaming\" library,\n"
-"but now ministreaming.jar contains only the interfaces for the full "
-"streaming library."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:278
-msgid "Recommended for UDP-like applications"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:279
-#, python-format
-msgid ""
-"The Datagram library allows sending UDP-"
-"like packets.\n"
-"It's possible to use:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:284
-msgid "Repliable datagrams"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:285
-msgid "Raw datagrams"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:289
-msgid "Not recommended"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:290
-#, python-format
-msgid ""
-"I2CP itself is a language independent protocol, "
-"but to implement an I2CP library \n"
-"in something other than Java there is a significant amount of code to be "
-"written (encryption routines, \n"
-"object marshalling, asynchronous message handling, etc).  While someone "
-"could write an I2CP library in \n"
-"C or something else, it would most likely be more useful to use the C SAM"
-" library instead."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:297
-msgid "Web Applications"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:298
-msgid ""
-"I2P comes with the Jetty webserver, and configuring to use the Apache "
-"server instead is straightforward.\n"
-"Any standard web app technology should work."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:304
-msgid ""
-"Developing using I2P requires a working I2P installation and a "
-"development environment of your own choice.\n"
-"If you are using Java, you can start development with the streaming library or datagram library.\n"
-"Using another programming language, SAM or BOB can be used."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:310
-msgid "Developing with the streaming library"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:312
-msgid ""
-"The following example shows how to create TCP-like client and server "
-"applications\n"
-"using the streaming library."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:317
-msgid "This will require the following libraries in your classpath:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:321
-msgid "The streaming library itself"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:322
-msgid "Factory and interfaces for the streaming library"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:323
-msgid "Standard I2P classes, data structures, API, and utilities"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:326
-msgid ""
-"Network communication requires the usage of I2P network sockets.\n"
-"To demonstrate this, we will create an application where a client can "
-"send text messages to a server,\n"
-"who will print the messages and send them back to the client. In other "
-"words, the server will function as an echo."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:331
-msgid ""
-"We will start by initializing the server application. This requires "
-"getting an I2PSocketManager\n"
-"and creating an I2PServerSocket.\n"
-"We will not provide the I2PSocketManagerFactory with the saved keys for "
-"an existing Destination,\n"
-"so it will create a new Destination for us.\n"
-"So we will ask the I2PSocketManager for an I2PSession, so we can find out"
-" the Destination that\n"
-"was created, as we will need to copy and paste that information later so "
-"the client can connect to us."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:362
-msgid "Code example 1: initializing the server application."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:364
-msgid ""
-"Once we have an I2PServerSocket, we can create I2PSocket instances to "
-"accept connections from clients.\n"
-"In this example, we will create a single I2PSocket instance, that can "
-"only handle one client at a time.\n"
-"A real server would have to be able to handle multiple clients.\n"
-"To do this, multiple I2PSocket instances would have to be created, each "
-"in separate threads.\n"
-"Once we have created the I2PSocket instance, we read data, print it and "
-"send it back to the client.\n"
-"The bold code is the new code we add."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:448
-msgid "Code example 2: accepting connections from clients and handling messages."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:452
-msgid ""
-"When you run the above server code, it should print something like this "
-"(but without the line endings, it should just be\n"
-"one huge block of characters):"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:466
-msgid ""
-"This is the base64-representation of the server Destination. The client "
-"will need this string to reach the server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:470
-msgid ""
-"Now, we will create the client application. Again, a number of steps are "
-"required for initialization.\n"
-"Again, we will need to start by getting an I2PSocketManager.\n"
-"We won't use an I2PSession and an I2PServerSocket this time.\n"
-"Instead, we will use the server Destination string to start our "
-"connection.\n"
-"We will ask the user for the Destination string, and create an I2PSocket "
-"using this string.\n"
-"Once we have an I2PSocket, we can start sending and receiving data to and"
-" from the server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:554
-msgid ""
-"Code example 3: starting the client and connecting it to the server "
-"application."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:556
-msgid ""
-"Finally, you can run both the server and the client application.\n"
-"First, start the server application. It will print a Destination string "
-"(like shown above).\n"
-"Next, start the client application. When it requests a Destination "
-"string, you can enter the string printed by the server.\n"
-"The client will then send 'Hello I2P!' (along with a newline) to the "
-"server, who will print the message and send it back to the client."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:562
-msgid "Congratulations, you have successfully communicated over I2P!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:566
-msgid "Existing Applications"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:567
-msgid "Contact us if you would like to contribute."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:588
-msgid "Application Ideas"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:590
-msgid "NNTP server - there have been some in the past, none at the moment"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:593
-msgid ""
-"Jabber server - there have been some in the past, and there is one at the"
-" moment, with access to the public internet"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:596
-msgid "PGP Key server and/or proxy"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:599
-msgid ""
-"Content Distribution / DHT applications - resurrect feedspace,\n"
-"port dijjer, look for alternatives"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:603
-msgid "Help out with Syndie development"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:606
-msgid ""
-"Web-based applications - The sky is the limit for hosting web-server-"
-"based\n"
-"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n"
-"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:611
-msgid ""
-"Resurrect some old apps, several previously in the i2p source package -\n"
-"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2
-msgid "I2P Developer's MTN Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4
-msgid "MTN Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5
-msgid ""
-"Monotone servers used by the I2P project require two types of keys to be "
-"used."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
-msgid ""
-"Commit Keys to sign changes checked-in to the "
-"respository; and"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10
-msgid ""
-"Transport Keys to push changes to remote "
-"servers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13
-#, python-format
-msgid ""
-"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
-"import the\n"
-"developer commit keys, but only Monotone \n"
-"server operators will need to import the transport keys."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20
-msgid "Developer Commit keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:240
-msgid "Developer Transport Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:241
-#, python-format
-msgid ""
-"Note: Transport keys are only needed for setting up a\n"
-"Monotone server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
-msgid "License Agreements"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
-#, python-format
-msgid "For more information see the licenses page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8
-msgid ""
-"Following is a monotonerc file defining the current trust list.\n"
-"Developers must use this file in ~/.monotone/monotonerc or\n"
-"_MTN/montonerc in their i2p.i2p workspace."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17
-msgid "Agreements"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:4
-msgid "I2P Software Licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:5
-#, python-format
-msgid ""
-"As required by our\n"
-"threat model (among other reasons), the \n"
-"software developed to support the anonymous communication \n"
-"network we call I2P must be freely available, open source, \n"
-"and user modifiable.  To meet these criteria, we make use of\n"
-"a variety of legal and software engineering techniques so\n"
-"as to remove as many barriers to entry for those considering\n"
-"making use of or contributing to the I2P effort."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:16
-msgid ""
-"While the information below may be more confusing than just simply \n"
-"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
-"the short answer to the question \"How is I2P licensed?\" is this:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:22
-msgid "All software bundled in the I2P distributions will allow:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:24
-msgid "use without fee"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:25
-msgid ""
-"use with no restrictions on how, when, where, why, or by whom is running "
-"it"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:26
-msgid "access to the source code without fee"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:27
-msgid "modifications to the source"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:30
-msgid ""
-"Most of the software guarantees much more - the ability of anyone "
-"to \n"
-"distribute the modified source however they choose.  However, not all of "
-"the \n"
-"software bundled provides this freedom - the GPL restricts the ability of"
-" \n"
-"developers who wish to integrate I2P with their own applications that are"
-" not \n"
-"themselves open source applications.  While we applaud the noble goals of"
-" \n"
-"increasing the resources in the commons, I2P is best served by removing "
-"any\n"
-"barriers that stand in the way of its adoption - if a developer "
-"considering whether\n"
-"they can integrate I2P with their application has to stop and check with "
-"their lawyer,\n"
-"or conduct a code audit to make sure their own source can be released as "
-"GPL-compatible,\n"
-"we lose out."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:43
-msgid "Component licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:44
-msgid ""
-"The I2P distribution contains several resources, reflecting the "
-"partitioning of \n"
-"the source code into components.  Each component has its own license, "
-"which all \n"
-"developers who contribute to it agree to - either by explicitly declaring"
-" the release\n"
-"of code committed under a license compatible with that component, or by "
-"implicitly\n"
-"releasing the code committed under the component's primary license.  Each"
-" of these \n"
-"components has a lead developer who has the final say as to what license "
-"is compatible\n"
-"with the component's primary license, and the I2P project manager has the"
-" final say as\n"
-"to what licenses meet the above four guarantees for inclusion in the I2P "
-"distribution."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:57
-msgid "Component"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:58
-msgid "Source path"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:59
-msgid "Resource"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:60
-msgid "Primary license"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:61
-msgid "Alternate licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:62
-msgid "Lead developer"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:271
-msgid "GPL + java exception"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:272
-#, python-format
-msgid ""
-"While it may be redundant, just for clarity the\n"
-"GPL'ed code included within\n"
-"I2PTunnel and other apps must be released under the GPL with an "
-"additional \"exception\"\n"
-"explicitly authorizing the use of Java's standard libraries:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:288
-msgid ""
-"All source code under each component will by default be licensed under "
-"the\n"
-"primary license, unless marked otherwise in the code.  All of the above "
-"is\n"
-"summary of the license terms - please see the specific license for the "
-"component\n"
-"or source code in question for authoritative terms.  Component source "
-"locations and\n"
-"resource packaging may be changed if the repository is reorganized."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:296
-msgid "Commit privileges"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:297
-#, python-format
-msgid ""
-"Developers may push changes to a distributed monotone repository if you\n"
-"receive permission from the person running that repository.\n"
-"See the Monotone Page for details."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:303
-msgid ""
-"However, to have changes included in a release, developers\n"
-"must be trusted by the release manager (currently zzz).\n"
-"In addition, they must explicitly agree with the above terms to be "
-"trusted.\n"
-"That means that they must send one of the release managers a signed "
-"message affirming that:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:310
-msgid ""
-"Unless marked otherwise, all code I commit is implicitly licensed under\n"
-"the component's primary license"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:314
-msgid ""
-"If specified in the source, the code may be explicitly licensed under one"
-"\n"
-"of the component's alternate licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:318
-msgid ""
-"I have the right to release the code I commit under the terms I\n"
-"am committing it"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:324
-#, python-format
-msgid ""
-"If anyone is aware of any instances where the above conditions are not "
-"met,\n"
-"please contact the component lead and/or an I2P release manager with "
-"further\n"
-"information.\n"
-"See developers' license agreements."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
-msgid "Release Signing Key"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
-msgid "Releases 0.7.6 and later are signed by zzz. His public key is:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40
-msgid ""
-"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public "
-"key is:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2
-msgid "Signed Developer Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4
-msgid ""
-"Keys for zzz, Complication and welterde are provided clearsigned. The key"
-" for jrandom must be\n"
-"verified differently, since he's away, and only left a binary detached\n"
-"signature for his key."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16
-msgid "Monotone keys for zzz"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47
-msgid "Monotone keys for welterde"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79
-msgid "Monotone keys for Complication"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114
-msgid "Monotone keys for jrandom"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
-msgid ""
-"Tip: To find zzz's GPG key, on his eepsite locate the key "
-"`0xA76E0BED`, with\n"
-"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 "
-"B310 4155\n"
-"76BA A76E 0BED`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49
-msgid ""
-"Tip: To find welterde's GPG key, on public keyservers locate the "
-"key\n"
-"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720"
-" FD81\n"
-"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81
-msgid ""
-"Tip: To find Complication's GPG key, on his eepsite locate the key"
-"\n"
-"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint "
-"`73CF\n"
-"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116
-msgid ""
-"Tip: To find jrandom's GPG key for Syndie releases, on public "
-"keyservers locate\n"
-"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n"
-"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122
-msgid ""
-"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n"
-"deployed in the Syndie Monotone repository, in a file named `mtn-"
-"committers`.\n"
-"That file also had a GPG signature, `mtn-committers.sig`, but it was a "
-"binary\n"
-"detached signature. I am going to supply both files in GPG ASCII-armoured"
-" form\n"
-"below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130
-msgid ""
-"First, the file `mtn-committers` containing jrandom's Monotone key. Save "
-"as\n"
-"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers "
-"--dearmor\n"
-"mtn-committers.asc`:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151
-msgid ""
-"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n"
-"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-"
-"committers.sig\n"
-"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n"
-"`mtn-committers` file:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170
-#, python-format
-msgid ""
-"Some of the developers have included their Monotone keys in their signed license agreement."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2
-msgid "Developer Guidelines and Coding Style"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4
-#, python-format
-msgid "Read the new developers guide first."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8
-msgid "Basic Guidelines and Coding Style"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10
-msgid ""
-"Most of the following should be common sense for anybody who has worked "
-"on open source or in a commercial\n"
-"programming envrionment.\n"
-"The following applies mostly to the main development branch i2p.i2p.\n"
-"Guidelines for other branches, plugins, and external apps may be "
-"substantially different;\n"
-"check with the appropriate developer for guidance."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18
-msgid "Community"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20
-msgid ""
-"Please don't just \"write code\". If you can, participate in other "
-"development activities, including:\n"
-"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
-"testing;\n"
-"bug reporting and responses; documentation; code reviews; etc."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25
-msgid ""
-"Active devs should be available periodically on IRC #i2p-dev.\n"
-"Be aware of the current release cycle.\n"
-"Adhere to release milestones such as feature freeze, tag freeze, and\n"
-"the checkin deadline for a release."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35
-msgid ""
-"Have a basic understanding of distributed source control systems, even if"
-" you haven't\n"
-"used monotone before. Ask for help if you need it.\n"
-"Once pushed, checkins are forever, there is no undo. Please be careful.\n"
-"If you have not used monotone before, start with baby steps.\n"
-"Check in some small changes and see how it goes."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42
-msgid ""
-"Test your changes before checking them in.\n"
-"If you prefer the checkin-before-test development model,\n"
-"use your own development branch (e.g. i2p.i2p.yourname.test)\n"
-"and propagate back to i2p.i2p once it is working well.\n"
-"Do not break the build. Do not cause regressions.\n"
-"In case you do (it happens), please do not vanish for a long period after"
-"\n"
-"you push your change."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51
-msgid ""
-"If your change is non-trivial, or you want people to test it and need "
-"good test reports\n"
-"to know whether your change was tested or not, add a checkin comment to "
-"history.txt\n"
-"and increment the build revision in RouterVersion.java."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56
-msgid ""
-"Ensure that you have the latest monotonerc file in _MTN.\n"
-"Do not check in on top of untrusted revisions."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60
-msgid ""
-"Ensure that you pull the latest revision before you check in.\n"
-"If you inadvertently diverge, merge and push as soon as possible.\n"
-"Don't routinely make others merge for you.\n"
-"Yes, we know that monotone says you should push and then merge,\n"
-"but in our experience, in-workspace merge works just as well as in-"
-"database merge,\n"
-"without creating a merge revision."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
-msgid ""
-"Do not check in major changes into the main i2p.i2p branch late in the "
-"release cycle.\n"
-"If a project will take you more than a couple days, create your own "
-"branch in monotone\n"
-"and do the development there so you do not block releases."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75
-msgid "Coding Style"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77
-msgid ""
-"Coding style throughout most of the code is 4-spaces for indentation. Do "
-"not use tabs.\n"
-"Do not reformat code. If your IDE or editor wants to reformat everything,"
-" get control of it.\n"
-"Yes, we know 4 spaces is a pain, but perhaps you can configure your "
-"editor appropriately.\n"
-"In some places, the coding style is different.\n"
-"Use common sense. Emulate the style in the file you are modifying."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84
-msgid ""
-"New classes and methods require at least brief javadocs. Add @since "
-"release-number."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87
-msgid ""
-"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our "
-"official API.\n"
-"There are several out-of-tree plugins and other applications that rely on"
-" this API.\n"
-"Be careful not to make any changes that break compatibility.\n"
-"Don't add methods to the API unless they are of general utility.\n"
-"Javadocs for API methods should be clear and complete.\n"
-"If you add or change the API, also update the documentation on the "
-"website (i2p.www branch)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95
-msgid ""
-"Tag strings for translation where appropriate.\n"
-"Don't change existing tagged strings unless really necessary, as it will "
-"break existing translations.\n"
-"Do not add or change tagged strings after the \"tag freeze\" in the "
-"release cycle so that\n"
-"translators have a chance to update before the release."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101
-msgid ""
-"Use generics and concurrent classes where possible. I2P is a highly "
-"multi-threaded application."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104
-msgid ""
-"We require Java 6 to build but only Java 5 to run I2P.\n"
-"Do not use Java 6 classes or methods without handling the class not found"
-" exceptions\n"
-"and providing alternate Java 5 code. See classes in net.i2p.util for "
-"examples."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109
-msgid ""
-"Explicitly convert between primitive types and classes;\n"
-"don't rely on autoboxing/unboxing."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117
-msgid ""
-"Only check in code that you wrote yourself.\n"
-"Before checking in any code or library jars from other sources,\n"
-"justify why it is necessary,\n"
-"verify the license is compatible,\n"
-"and obtain approval from the lead developer."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124
-msgid ""
-"For any images checked in from external sources,\n"
-"it is your responsibility to first verify the license is compatible.\n"
-"Include the license and source information in the checkin comment."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131
-msgid "Bugs"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
-#, python-format
-msgid ""
-"Managing Trac tickets is everybody's job, please help.\n"
-"Monitor %(trac)s for tickets you have been assigned or can help with.\n"
-"Assign, categorize, comment on, fix, or close tickets if you can."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138
-msgid ""
-"Close a ticket when you think you've fixed it.\n"
-"We don't have a test department to verify and close tickets.\n"
-"If you arent sure you fixed it, close it and add a note saying\n"
-"\"I think I fixed it, please test and reopen if it's still broken\".\n"
-"Add a comment with the dev build number or revision and set\n"
-"the milestone to the next release."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:4
-msgid ""
-"The main I2P development branch (i2p.i2p) has been set up to"
-" enable developers to easily set up two of the commonly-used IDEs for "
-"Java development: Eclipse and NetBeans."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:10
-msgid ""
-"The main I2P development branches (i2p.i2p and branches from"
-" it) contain .project and .classpath Eclipse files, to enable the branch "
-"to be easily set up in Eclipse."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:16
-msgid ""
-"Check out the I2P branch into some directory (e.g. "
-"$HOME/dev/i2p.i2p)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:20
-msgid ""
-"Open Eclipse and create a new Workspace, based in the directory that the "
-"I2P branch was checked out to."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:24
-msgid ""
-"Select \"File - Import...\" and then under \"General\" select \"Existing "
-"Projects into Workspace\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:28
-msgid ""
-"For \"Select root directory:\" choose the directory that the I2P branch "
-"was checked out to."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:32
-msgid "If necessary, click \"Refresh\" to refresh the list of projects."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:36
-msgid "Select every project in the list, and click \"Finish\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:40
-msgid ""
-"Done! Your workspace should now contain all projects within the I2P "
-"branch, and their build dependencies should be correctly set up."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:48
-msgid ""
-"The main I2P development branches (i2p.i2p and branches from"
-" it) contain NetBeans project files."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:9
-msgid "Operating a Monotone client"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:11
-#: i2p2www/pages/site/get-involved/guides/monotone.html:63
-msgid "Generating Monotone keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:12
-msgid "Trust and initializing your repository"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:13
-#: i2p2www/pages/site/get-involved/guides/monotone.html:196
-msgid "Obtaining and deploying developers' keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:14
-#: i2p2www/pages/site/get-involved/guides/monotone.html:227
-msgid "Setting up trust evaluation hooks"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:15
-#: i2p2www/pages/site/get-involved/guides/monotone.html:268
-msgid ""
-"Pulling the i2p.i2p, i2p.www and "
-"i2p.syndie branches"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:16
-#: i2p2www/pages/site/get-involved/guides/monotone.html:308
-msgid "Verifying that trust evaluation works"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:17
-#: i2p2www/pages/site/get-involved/guides/monotone.html:357
-msgid "Checking out a working copy of the latest version"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:18
-#: i2p2www/pages/site/get-involved/guides/monotone.html:384
-msgid "Updating your working copy to the latest version"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:22
-#: i2p2www/pages/site/get-involved/guides/monotone.html:414
-msgid "Operating a Monotone Server"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:24
-msgid "Obtaining and deploying developers’ transport keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:25
-#: i2p2www/pages/site/get-involved/guides/monotone.html:424
-msgid "Granting push and pull access"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:26
-#: i2p2www/pages/site/get-involved/guides/monotone.html:469
-msgid "Running Monotone in server mode"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:27
-#: i2p2www/pages/site/get-involved/guides/monotone.html:494
-msgid "Differences under Debian GNU/Linux"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:34
-#, python-format
-msgid ""
-"This is a revised version of Complication's original\n"
-"  guide detailing the use of Monotone in I2P development.\n"
-"  For basic instructions see the quick-start "
-"guide."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:42
-#, python-format
-msgid ""
-"I2P has a distributed development model. The source code is replicated "
-"across\n"
-"  independently administered Monotone (\"MTN\") repositories.\n"
-"  Developers with commit rights are able to push their changes to the "
-"repository\n"
-"  (a license agreement needs to be "
-"signed\n"
-"  before commit rights are granted)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:52
-msgid ""
-"Some of Monotone's noteworthy qualities are: distributed\n"
-"  version control, cryptographic authentication, access control, its "
-"small size, having few\n"
-"  dependencies, storage of projects in a compressed SQLite database file,"
-" and\n"
-"  having the ability to resume interrupted synchronization attempts."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:61
-msgid "Operating a Monotone Client"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:66
-msgid ""
-"A transport key grants you the ability to push your changes to a Monotone"
-" repository server.\n"
-"  In order to commit code into Monotone (in essence signing your code), a"
-" commit key is also needed.\n"
-"  None of the public Monotone servers on I2P currently require a key in "
-"order to read (or pull) the source code."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:74
-msgid ""
-"Without a transport key, one cannot:\n"
-"  
              \n"
-"    
            • pull code from a server which doesn't allow global read "
-"access
              • \n"
-"    
            • push code to any server
              • \n"
-"    
            • run a Monotone server
              • \n"
-"  
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:85
-msgid ""
-"Without a commit key, one cannot:\n"
-"  
              \n"
-"    
            • commit any code
              • \n"
-"  
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:94
-msgid ""
-"If you only intend to retrieve code from MTN, feel free to skip to the\n"
-"  next section. "
-"If you want\n"
-"  to generate keys, read the following."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:102
-msgid ""
-"By convention keys are named like an e-mail addresses, but a "
-"corresponding e-mail\n"
-"  address does not need to exist. For example, your keys might be named:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:113
-msgid ""
-"Monotone stores keys under $HOME/.monotone/keys in "
-"text files which\n"
-"  are named identically to the keys. For example:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:123
-msgid ""
-"To generate transport and commit keys, enter the following commands at a "
-"prompt:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:133
-msgid ""
-"Monotone will prompt you for a password to protect your keys. You are "
-"very strongly encouraged to set a password\n"
-"  for the commit key. Many users will leave an empty password for the "
-"transport key, especially those running a\n"
-"  Monotone server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:141
-msgid "Trust, and initializing your repository"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:145
-msgid ""
-"Monotone's security model helps to ensure that nobody can easily "
-"impersonate a developer without\n"
-"  it being noticed. Since developers can make mistakes and become "
-"compromised,only manual review can\n"
-"  ensure quality of code. Monotone's trust model will ensure that you "
-"read the right diffs. It does\n"
-"  not replace reading diffs."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:155
-msgid ""
-"A Monotone repository is a single file (a compressed SQLite database) "
-"which contains all of the project's source code and history."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:161
-msgid ""
-"After importing the "
-"developers' keys into Monotone and\n"
-"  setting up trust "
-"evaluation hooks,\n"
-"  Monotone will prevent untrusted code from being checked out into your "
-"workspace.\n"
-"  There are commands available to clean untrusted code from your "
-"workspace but in practice they've not been\n"
-"  needed due to the push access policies in place."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:171
-msgid ""
-"A repository can hold many branches. For example, our repository holds "
-"the\n"
-"  following main branches:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:176
-msgid "The I2P router and associated programs"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:177
-msgid "The I2P project website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:178
-msgid "Syndie, a distributed forums tool"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:183
-msgid ""
-"By convention, the I2P Monotone repository is named i2p.mtn."
-" Before pulling\n"
-"  source code from servers, a database for your repository will need to "
-"be initialized.\n"
-"  To initialize your local repository, change into the directory that you"
-" want the\n"
-"  i2p.mtn file and branch directories to be stored and issue"
-" the following\n"
-"  command:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:199
-msgid ""
-"Keys which developers use to commit code are essential for trust "
-"evaluation in\n"
-"  Monotone. The other developers' transport keys are only required for "
-"Monotone server operators.\n"
-"  "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:206
-#, python-format
-msgid ""
-"Developers' commit keys are provided GPG-signed on another page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:212
-#, python-format
-msgid ""
-"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
-"  file. Create this file (e.g. keys.txt) in the same "
-"directory where i2p.mtn is located. Import the keys with the"
-" command:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:222
-msgid ""
-"Note: Never add keys to "
-"$HOME/.monotone/keys manually."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:230
-msgid ""
-"The default Monotone trust policy is way too lax for our requirements: "
-"every comitter is trusted by default.\n"
-"  That is not acceptable for I2P development."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:237
-msgid ""
-"Change into the directory $HOME/.monotone and open "
-"the file\n"
-"  monotonerc with a text editor. Copy and paste the "
-"following two functions into this file:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:246
-msgid ""
-"The first function determines an intersection between two sets, in our "
-"case a\n"
-"  revision's signers and trusted signers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:253
-msgid ""
-"The second function determines trust in a given revision, by calling the "
-"first\n"
-"  function with \"signers\" and \"trusted\" as arguments. If the "
-"intersection is\n"
-"  null, the revision is not trusted. If the intersection is not empty, "
-"the\n"
-"  revision is trusted. Otherwise, the revision is not trusted."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:262
-msgid ""
-"More information about Trust Evauluation Hooks can be found in the official Monotone "
-"documentation."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:271
-msgid ""
-"Enter the directory where you initialized i2p.mtn. Depending "
-"on whether you\n"
-"  want only I2P sources, or also sources for the I2P website and Syndie, "
-"you can\n"
-"  perform the pull operation in different ways."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:279
-msgid "If you only want I2P sources:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:288
-msgid "If you want all branches:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:294
-msgid ""
-"If the transfer aborts before completing sucessfully, simply repeating "
-"the pull command will resume the transfer."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:300
-msgid ""
-"Pulling in the above examples is done anonymously by specifying an empty "
-"transport key.\n"
-"  If everyone pulls anonymously it will be harder for an attacker who "
-"gains control of the server\n"
-"  to selectively provide some people with tampered data."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:311
-msgid "To verify that trust evaluation works:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:315
-msgid "Make a backup of your monotonerc file."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:316
-msgid ""
-"Modify monotonerc by setting the trusted_signers "
-"variable in the following way:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:322
-msgid ""
-"With monotonerc configured as above, Monotone will no"
-" longer trust any committers. Confirm this by changing into the\n"
-"directory where i2p.mtn was created and attempt a checkout "
-"of the I2P branch:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:332
-msgid ""
-"A directory named i2p.i2p should not appear. You "
-"should encounter many\n"
-"  error messages like:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:349
-msgid ""
-"If you are satisfied with results, restore the backup of\n"
-"  monotonerc that was created above. If you didn't create a "
-"backup\n"
-"  as advised, re-read Setting up trust evaluation hools."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:360
-msgid ""
-"If you already have a branch checked out, skip to the next\n"
-"  section."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:367
-msgid ""
-"Change into the directory where i2p.mtn is located. Over "
-"there issue:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:376
-msgid ""
-"The checkout should complete without error messages and a directory named"
-"\n"
-"  i2p.i2p should appear in the current directory. "
-"Congratulations! You have\n"
-"  successfully checked out the latest I2P sources, ready to be compiled."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:387
-msgid ""
-"If you haven't done this already, pull fresh code from the server to your"
-" local\n"
-"  Monotone repository. To accomplish this, change into the directory "
-"where\n"
-"  i2p.mtn is located and issue:\n"
-"  
              \n"
-"    
            • $ mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
-"i2p.i2p
              • \n"
-"  
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:398
-msgid "Now change into your i2p.i2p directory, and over there issue:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:407
-msgid ""
-"As long as there were no errors…Congratulations! You have "
-"successfully updated to the latest I2P sources. They\n"
-"  should be ready to compile."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:416
-msgid "Obtaining and deploying developers' transport keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:419
-msgid ""
-"As a server operator you may want to grant push access to certain "
-"developers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:427
-msgid "By default the Monotone server denies all access."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:433
-msgid "To grant pull access to all clients, set the following in"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:445
-msgid ""
-"No one will not be able to push code to your server without permission "
-"being explicitly granted. To grant push access:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:451
-msgid ""
-"Add the name of the user's transport key to\n"
-"$HOME/.monotone/write-permissions, such as\n"
-"
            \n"
-"    zzz-transport@mail.i2p\n"
-"    complication-transport@mail.i2p\n"
-"
            \n"
-"with one key per line."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:462
-msgid ""
-"Import the transport key(s) into your database. The procedure for "
-"importing transport keys is the same as for\n"
-"importing commit keys, which is described in the section Obtaining and deploying "
-"developers' keys."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:472
-msgid ""
-"A separate database should be used for your Monotone server because "
-"monotone will lock the database while it is served to others.\n"
-"  Make a copy of your development database, then start the server with:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:479
-msgid ""
-"If your key is protected with a passphrase, Monotone may request the "
-"passphrase\n"
-"  when the first client connects. You can work around this by connecting "
-"making the first client connection to your server\n"
-"  (or by clearing the password for your transport key)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:487
-msgid ""
-"For your server to be accessible for others over I2P, you will need to "
-"create a\n"
-"  server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" "
-"profile."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:497
-msgid ""
-"Debian (amongst other distributions) has integrated Monotone into their\n"
-"  framework of daemons/services. Although Monotone servers can still be "
-"run\n"
-"  \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may"
-" be more straightforward."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:505
-msgid ""
-"Permissions are granted by editing the files\n"
-"  /etc/monotone/read-permissions and\n"
-"  /etc/monotone/write-permissions. You'll also need to edit\n"
-"  /etc/default/monotone to enable monotone to start at boot "
-"or to\n"
-"  customize the host, port, or database location."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
-msgid ""
-"\n"
-"So you want to start work on I2P? Great!\n"
-"Here's a quick guide to getting started\n"
-"on contributing to the website or the software, doing development or "
-"creating translations."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
-#, python-format
-msgid ""
-"\n"
-"Not quite ready for coding?\n"
-"Try getting involved first."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
-msgid "Basic study"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
-msgid "Getting the I2P code"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
-msgid "Building I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
-msgid "Development ideas"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
-msgid "Making the results available"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
-msgid "Get to know us!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
-msgid "Translations"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
-msgid "Tools"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
-msgid ""
-"Basic development on the I2P router or the embedded applications uses "
-"Java as the main development language.\n"
-"If you don't have experience with Java, you can always have a look at Thinking in Java."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
-#, python-format
-msgid ""
-"Study the how intro,\n"
-"the other \"how\" documents,\n"
-"the tech intro,\n"
-"and associated documents.\n"
-"These will give you a good overview of how I2P is structured and what "
-"different things it does."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
-msgid ""
-"For development on the i2p router or the embedded applications,\n"
-"get the monotone source repository installed - short instructions:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
-msgid ""
-"Install monotone.\n"
-"Monotone is a version control system.\n"
-"We use it because it allows us to keep track of who does what changes to "
-"the source code (and for a lot of complicated things, but 'keeping track "
-"of changes' is the basic idea)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
-msgid ""
-"Skim over the monotone tutorial,"
-" to make sure you understand the concepts."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
-msgid ""
-"If you want to remain anonymous, you need to do an additional step, to "
-"set up a connection to a monotone server over I2P:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
-#, python-format
-msgid ""
-"Enable the i2ptunnel client tunnel on port "
-"8998 pointing to mtn.i2p2.i2p."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
-msgid ""
-"Pick a directory where you want to put all your I2P files, and create a "
-"monotone database:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
-msgid ""
-"Define the trust list by creating ~/.monotone/monotonerc (or"
-" _MTN/monotonerc in the i2p.i2p workspace) with the "
-"following contents:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
-#, python-format
-msgid ""
-"Copy and paste the developer's commit keys "
-"into a new file (e.g. keys.txt) in the same directory\n"
-"  that i2p.mtn is in. Import the keys into your database "
-"with 
                  mtn -d i2p.mtn read < keys.txt
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:76
-msgid ""
-"Pull the I2P sources to your machine. This may take a long time, "
-"especially if you are doing this over I2P!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:78
-msgid "Anonymously:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:81
-msgid "Non-anonymously:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:83
-msgid ""
-"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn"
-".i2p-projekt.de."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:90
-msgid ""
-"All the sources are now present on your machine, in the database file. To"
-" make them available in a directory, you need to check them out:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:92
-msgid ""
-"The above command creates a directory i2p.i2p, which contains all of the "
-"I2P sources."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:96
-msgid "Remarks"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:97
-msgid ""
-"\n"
-"To download the website files instead of the I2P source files, use "
-"'i2p.www' instead of 'i2p.i2p'."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:100
-msgid ""
-"The initial pull may take several hours using the tunnel.\n"
-"If it fails after a partial pull, simply rerun it, it will start where it"
-" left off.\n"
-"If you are in a hurry, use the non-anonymous access."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:105
-#, python-format
-msgid ""
-"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
-#, python-format
-msgid ""
-"A long explanation about using monotone is available on the monotone page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
-#, python-format
-msgid ""
-"To compile the code, you need the Sun Java Development Kit 6 or higher, "
-"or equivalent JDK\n"
-"(Sun JDK 6 strongly recommended) and\n"
-"Apache ant\n"
-"version 1.7.0 or higher.\n"
-"If you go are working on the main I2P code, you can go into the i2p.i2p "
-"directory and run 'ant' to see the build options."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
-msgid ""
-"To build or work on console translations, you need\n"
-"the xgettext, msgfmt, and msgmerge tools from the\n"
-"GNU gettext package."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
-#, python-format
-msgid ""
-"For development on new applications,\n"
-"see the application development guide."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
-#, python-format
-msgid ""
-"See zzz's TODO lists,\n"
-"this website's TODO list or\n"
-"Trac\n"
-"for ideas."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
-#, python-format
-msgid ""
-"See the bottom of the licenses page "
-"for\n"
-"commit privilege requirements. You need these to put code into i2p.i2p "
-"(not required for the website!)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
-msgid "Short version of how to generate and use keys if you plan to commit:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
-msgid "use an empty passphrase"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
-msgid "enter a passphrase"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
-#, python-format
-msgid ""
-"send this to a mtn repo operator to get "
-"push privileges"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
-#, python-format
-msgid ""
-"send this to a release manager to get "
-"commit privileges - not required for website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
-msgid "check in with this key"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
-msgid "push with this key"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
-#, python-format
-msgid "Long version: see the monotone page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
-#, python-format
-msgid ""
-"The developers hang around on IRC. They can be reached on the Freenode "
-"network, OFTC, and on the I2P internal networks. The usual place to look "
-"is #i2p-dev. Join the channel and say hi!\n"
-"We also have additional guidelines for regular"
-" developers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
-#, python-format
-msgid ""
-"Website and router console translators: See the New Translator's Guide\n"
-"for next steps."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
-msgid ""
-"I2P is open source software that is mostly developed using open sourced\n"
-"toolkits. The I2P project recently acquired a license for the YourKit "
-"Java\n"
-"Profiler. Open source projects are eligible to receive a free license "
-"provided\n"
-"that YourKit is referenced on the project web site. Please get in touch "
-"if you\n"
-"are interested in profiling the I2P codebase."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
-#, python-format
-msgid ""
-"YourKit is kindly supporting open source projects with its full-featured "
-"Java Profiler.\n"
-"YourKit, LLC is the creator of innovative and intelligent tools for "
-"profiling\n"
-"Java and .NET applications. Take a look at YourKit's leading software "
-"products:\n"
-"YourKit Java Profiler and\n"
-"YourKit .NET Profiler."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
-msgid "Here's a very quick guide to getting started."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
-msgid "How to Translate the Website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
-#, python-format
-msgid ""
-"Translation of the website is done with .po files. The easiest way by far"
-" to\n"
-"translate the website is to sign up for an account at \n"
-"Transifex and request to join a translation"
-" team. \n"
-"Alternatively it can be done \"the old way\" as outlined below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
-msgid "Preparation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
-#, python-format
-msgid ""
-"Come to #i2p-dev on irc and talk to people.\n"
-"Claim the language -\n"
-"To make sure other coworkers don't bump onto the files you are working "
-"on,\n"
-"please update the translation status on this wiki "
-"page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
-#, python-format
-msgid ""
-"Follow the new developer's guide,\n"
-"Including the installation of monotone,\n"
-"checking out i2p.www branch, and generate your own monotone keys.\n"
-"It is not required that you sign a dev agreement."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
-msgid ""
-"Create files:\n"
-"If the file for your language does not exist yet:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
-msgid ""
-"Run \"./extract-messages.sh\" to generate a "
-"messages.pot in the base directory.\n"
-"Edit the header of this file, then run \"./init-new-po.sh "
-"locale\" to generate the file\n"
-"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
-"\"mtn add\" this file."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
-msgid ""
-"Edit i2p2www/pages/global/lang.html and add a line for your "
-"language (copy an existing line)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
-msgid ""
-"Add a flag image file to i2p2www/static/images/flags/ for "
-"the menu (copy from the router)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
-msgid ""
-"Edit files:\n"
-"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
-"To work with .po files efficiently, you may wish to use POEdit"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
-msgid ""
-"Check in:\n"
-"\"mtn pull\", \"mtn update\". Then check in by "
-"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
-"This collects the diff info of your changed file into your local repo. "
-"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
-"i2p.i2p\".\n"
-"This synchronizes your local repo with the repo on the target machine."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
-msgid "Repeat. Check in often. Don't wait until it is perfect."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
-msgid "How to Translate the Router Console"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
-#, python-format
-msgid ""
-"The easiest way by far to translate the router console is to sign up for "
-"an account at \n"
-"Transifex and request to join a translation"
-" team. \n"
-"Alternatively it can be done \"the old way\" as outlined below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
-#, python-format
-msgid ""
-"Follow the new developer's guide,\n"
-"including the installation of monotone and the gettext tools,\n"
-"checking out i2p.i2p branch, and generate your own monotone keys."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
-msgid "Generate your own gpg key and sign the dev agreement."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
-msgid ""
-"Before starting a console translation, better help translate some i2p "
-"webpages first.\n"
-"At least an i2p homepage in your language would be great."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
-msgid ""
-"What to translate:\n"
-"There are about 15 files in the i2p.i2p branch that needs translation:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
-msgid ""
-"Where xx is your language code like fr/de/ch/zh/...\n"
-"There may be or may not be files with your lang code. If not, you can "
-"create your own. by copying and renaming other language files you know "
-"with your own lang code."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
-msgid ""
-"Create files:\n"
-"If the file for your language does not exist yet, copy another language "
-"file to a new file foo_xx.bar for your language.\n"
-"Then \"mtn add\" the file.\n"
-"After creating a .po file, edit the headers. Then run \"ant "
-"distclean poupdate\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
-msgid ""
-"Start to work:\n"
-"Edit the HTML files with any text editor.\n"
-"Be sure not to use an editor in HTML mode that reformats everything.\n"
-"To work with .po files efficiently, you may wish to use POEdit"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
-msgid ""
-"As you can see, it's not that difficult.\n"
-"If you have questions about the meaning of the terms in the console, ask "
-"in #i2p-dev on IRC."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
-msgid ""
-"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
-"and html, etc.? Why can't I just do a translation and email it to you?"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
-msgid "A: Several reasons:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
-#, python-format
-msgid ""
-"You might be interested in translating via Transifex. Request to join a "
-"translation team here."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
-msgid ""
-"We don't have anybody who has time to accept manual contributions and "
-"submit them to our source control system on your behalf. Even if we did, "
-"it doesn't scale."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
-msgid ""
-"Maybe you are thinking translation is a one-step process. It isn't. You "
-"can't do it all at once. You will make mistakes. You need to test it and "
-"tweak it to make it look right before you submit it. Developers "
-"will update or add to the English text, thus requiring a translation "
-"update."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
-msgid ""
-"Having translators use a source control system directly provides "
-"authentication and accountablility - we know who is doing what, and we "
-"can track changes, and revert them if necessary."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
-msgid ""
-".po files are not difficult. If you don't want to work directly with "
-"them, we recommend 'poedit'."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
-msgid ""
-"HTML files are not difficult. Just ignore the html stuff and translate "
-"the text."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
-msgid ""
-"Installing and using monotone is not that difficult. Several of the "
-"translators and other contributors to I2P are non-programmers, and they "
-"use monotone regularly. Monotone is simply a source control system, it is"
-" not about \"coding\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
-msgid ""
-"Our items to translate are not \"documents\". They are html files and po "
-"files, with a specific format and character encoding (UTF-8) that must be"
-" maintained, and not corrupted by email programs or other methods of "
-"transfer."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
-msgid ""
-"We looked at 'pootle' as a front-end for translators. It didn't work "
-"well, needed an administrator, and a pootle-based process would suffer "
-"from a number of the above flaws."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
-msgid ""
-"In summary:\n"
-"Yes, we know it is somewhat of a hurdle to get started. It's really the "
-"only possible way we can do it. Give it a try, it really isn't that hard."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
-msgid "More Information"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
-#, python-format
-msgid ""
-"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
-msgstr ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: i2p2www/pages/site/misc/transition-guide.html:21
-msgid "Guide"
-msgstr ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:44
-msgid "Click \"Save\""
-msgstr ""
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:51
-msgid "Add the following line:"
-msgstr ""
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:55
-msgid "Click \"Apply\""
-msgstr ""
-
-#: 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 ""
-
-#: i2p2www/pages/site/research/index.html:2
-msgid "Academic Research"
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:4
-msgid ""
-"Academic research and analysis of I2P is an important part of ensuring "
-"that the software and network performs as expected and is safe for users "
-"in hostile environments."
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:8
-msgid ""
-"I2P can be run as a separate test network by controlling the locations "
-"that a new router reseeds from so that it only finds other test routers. "
-"Additionally, the router can be run on its own in a virtual network mode "
-"to enable testing the router in isolation; to enable this mode, add "
-"i2p.vmCommSystem=true to the router.config before starting."
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:12
-#, python-format
-msgid ""
-"If you are planning on conducting research on the live I2P network, "
-"please contact us before you commence your "
-"testing. While we do not discourage researchers from responsibly testing "
-"their ideas on the live network, if an attack becomes apparent and we "
-"don't have any line of communication then we will end up taking "
-"countermeasures which could interfere with the test."
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:16
-msgid "Prior Research"
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:18
-#, python-format
-msgid ""
-"A list of known published papers about I2P is available here."
-msgstr ""
-
-#: i2p2www/pages/site/research/papers.html:6
-msgid "Following are links to research papers about I2P."
-msgstr ""
-
-#: i2p2www/pages/site/research/papers.html:12
-msgid "Newest links are at the top of the page."
-msgstr ""
-
-#: i2p2www/pages/site/research/papers.html:17
-msgid "Papers and Research"
-msgstr ""
-
diff --git a/i2p2www/translations/de/LC_MESSAGES/get-involved.po b/i2p2www/translations/de/LC_MESSAGES/get-involved.po
new file mode 100644
index 00000000..ea7cde65
--- /dev/null
+++ b/i2p2www/translations/de/LC_MESSAGES/get-involved.po
@@ -0,0 +1,4077 @@
+# German translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# amiga4000 , 2008
+# D.A. Loader, 2013
+# SteinQuadrat, 2013
+# zeroflag , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-07-04 16:33+0000\n"
+"Last-Translator: D.A. Loader\n"
+"Language-Team: German "
+"(http://www.transifex.com/projects/p/I2P/language/de/)\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/get-involved/donate.html:2
+#: i2p2www/pages/site/get-involved/index.html:77
+msgid "Donate"
+msgstr "Spenden"
+
+#: i2p2www/pages/site/get-involved/donate.html:4
+msgid ""
+"Thank you for your interest in contributing to I2P!\n"
+"The details of how you\n"
+"can make your contribution are provided below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:11
+#: i2p2www/pages/site/get-involved/donate.html:27
+#, python-format
+msgid ""
+"As of %(date)s, eche|on has been running a\n"
+"%(cointype)s account for the I2P project.\n"
+"If you'd like to donate using %(cointype)s, just transfer your\n"
+"desired amount of coins to the account %(account)s\n"
+"and leave eche|on a note if you'd like your donation to be\n"
+"mentioned on the I2P webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:22
+#: i2p2www/pages/site/get-involved/donate.html:38
+msgid "For easy usage, use the QR code below!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:44
+#, python-format
+msgid "You can donate direct via PayPal to the account \"%(account)s\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:50
+msgid "One time donation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:64
+msgid "Donate 10 €/month for 12 months:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:72
+#: i2p2www/pages/site/get-involved/donate.html:84
+#: i2p2www/pages/site/get-involved/donate.html:96
+#: i2p2www/pages/site/get-involved/donate.html:108
+msgid "I2P donation "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:78
+msgid "Donate 20 €/month for 12 months:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:90
+msgid "Donate 30 €/month for 12 months:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:102
+msgid "Donate 50 €/month for 12 months:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:117
+msgid "Flattr this"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:122
+msgid ""
+"If you want to keep more or less anonymous, the option to send money via "
+"mail is also available. But it is less secure\n"
+"as the envelope can be lost on the way to us."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:126
+#, python-format
+msgid ""
+"If you'd like to donate via  snail mail, send an email to %(email)s\n"
+" and you'll receive an email with instructions detailing how to proceed."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:131
+#, python-format
+msgid ""
+"In the meantime, feel free to take a look at the generous donations that "
+"have been\n"
+"given in support of the I2P Project at the hall of fame."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:2
+msgid "Get Involved!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:4
+msgid "We need your help!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:5
+msgid ""
+"To get involved, please feel free to join us on the #i2p IRC channel (on\n"
+"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or "
+"irc.postman.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:9
+#, python-format
+msgid ""
+"If you're interested in joining our team, please"
+" get in\n"
+"touch as we're always looking for eager contributors!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:13
+msgid ""
+"We need help in many areas, and you don't need to know Java to "
+"contribute!\n"
+"Here's a list to help you get started!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:18
+msgid "Spread the Word!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:19
+msgid ""
+"Tell people about I2P on forums, blogs, and comments to articles.\n"
+"Fix up the Wikipedia article about I2P in your language.\n"
+"Tell your friends."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:24
+msgid "Testing"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:25
+#, python-format
+msgid ""
+"Run the latest builds from monotone\n"
+"and report results on #i2p or as bugs on Trac."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:30
+msgid "Documentation"
+msgstr "Dokumentation"
+
+#: i2p2www/pages/site/get-involved/index.html:31
+msgid ""
+"Help fix the parts of the website that are outdated or incomplete.\n"
+"Translate pages into other languages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:35
+msgid "Pictures"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:36
+msgid "Make some more pictures, fix the old ones on the website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:39
+msgid "Content"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:40
+msgid "Make an eepsite! Add some content! Contribute to the community!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:43
+msgid "Services"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:44
+msgid ""
+"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n"
+"a naming service, a search engine, an eepsite monitor... many of these\n"
+"aren't that hard."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:49
+msgid "Applications"
+msgstr "Anwendungen"
+
+#: i2p2www/pages/site/get-involved/index.html:50
+#, python-format
+msgid ""
+"Write or port applications for I2P! There's some guidelines and\n"
+"a list of ideas on the applications page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:54
+msgid "Coding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:55
+#, python-format
+msgid ""
+"There's plenty to do if you know Java or are ready to learn.\n"
+"Check for open tickets on Trac\n"
+"or the TODO list on %(zzz)s for\n"
+"some ideas on where to start.\n"
+"See the new developer's guide for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:64
+msgid "Translation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:65
+#, python-format
+msgid ""
+"Help translate the website and the software into your language.\n"
+"See the new translator's guide for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:69
+msgid "Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:70
+#, python-format
+msgid ""
+"Study or test the code to look for vulnerabilities.\n"
+"Both anonymity vulnerabilities from the various\n"
+"threat models,\n"
+"and DOS and other weaknesses due to securities holes,\n"
+"need researching."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:2
+msgid "Roadmap"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:7
+msgid ""
+"Include some seed data in the distribution so a central reseed location "
+"isn't required?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:10
+#, python-format
+msgid ""
+"Reachability Mapping / handle peers partially reachable / enhanced restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:13
+msgid "Improve help pages and website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:14
+msgid "More translations"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:15
+msgid "SSU disconnect message"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:16
+msgid "Iterative floodfill lookups"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:21
+msgid "Full review of anonymity issues and other vulnerabilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:22
+msgid ""
+"Reduce memory usage, remove debugging overhead, make it run better on "
+"slow and embedded machines"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:25
+msgid "Docs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:30
+msgid "Full restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:35
+msgid "Tunnel mixing and padding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:36
+msgid "User defined message delays"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:39
+#, python-format
+msgid ""
+"Please see the TODO list for more detailed info "
+"about some of these tasks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:2
+msgid "To Do List"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:4
+msgid "I2P Project Targets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:5
+#, python-format
+msgid ""
+"Below is a more detailed (yet still incomplete) discussion of the major "
+"areas\n"
+"of future development on the core I2P network, spanning the plausibly "
+"planned\n"
+"releases. This does not include stego transports, porting to wireless "
+"devices,\n"
+"or tools to secure the local machine, nor does it include client "
+"applications\n"
+"that will be essential in I2P's success. There are probably other things "
+"that\n"
+"will come up, especially as I2P gets more peer review, but these are the "
+"main\n"
+"'big things'. See also the roadmap. Want to "
+"help?\n"
+"Get involved!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:54
+msgid "Core functionality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:52
+msgid "link"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:18
+#: i2p2www/pages/site/get-involved/todo.html:57
+msgid "NAT/Firewall bridging via 1-hop restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:21
+#: i2p2www/pages/site/get-involved/todo.html:130
+msgid "High degree transport layer with UDP, NBIO, or NIO"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:24
+#: i2p2www/pages/site/get-involved/todo.html:218
+msgid "NetworkDB and profile tuning and ejection policy for large nets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:242
+msgid "Security / anonymity"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:30
+#: i2p2www/pages/site/get-involved/todo.html:245
+msgid ""
+"Per-hop tunnel id & new permuted TunnelVerificationStructure "
+"encryption"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:33
+#: i2p2www/pages/site/get-involved/todo.html:295
+msgid "Strict ordering of participants within tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:36
+msgid "Randomly permuted tunnel lengths"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:39
+#: i2p2www/pages/site/get-involved/todo.html:357
+msgid "Full blown n-hop restricted routes with optional trusted links"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:42
+#: i2p2www/pages/site/get-involved/todo.html:376
+msgid "Hashcash for routerIdentity, destination, and tunnel request"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:45
+#: i2p2www/pages/site/get-involved/todo.html:405
+msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:48
+#: i2p2www/pages/site/get-involved/todo.html:442
+msgid "Stop & go mix w/ garlics & tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:52
+#: i2p2www/pages/site/get-involved/todo.html:456
+msgid "Performance"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:62
+msgid "Implemented in I2P 0.6.0.6"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:63
+msgid ""
+"The functionality of allowing routers to fully participate within the "
+"network \n"
+"while behind firewalls and NATs that they do not control requires some "
+"basic \n"
+"restricted route operation (since those peers will not be able to receive"
+" \n"
+"inbound connections). To do this successfully, you consider peers one of"
+" \n"
+"two ways:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:73
+msgid ""
+"Peers who have reachable interfaces - these peers do not need to \n"
+"do anything special"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:77
+msgid ""
+"Peers who do not have reachable interfaces - these peers must "
+"build \n"
+"a tunnel pointing at them where the gateway is one of the peers they have"
+" \n"
+"established a connection with who has both a publicly reachable interface"
+" \n"
+"and who has agreed to serve as their 'introducer'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:85
+msgid ""
+"To do this, peers who have no IP address simply connect to a few peers, \n"
+"build a tunnel through them, and publish a reference to those tunnels "
+"within \n"
+"their RouterInfo structure in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:90
+msgid ""
+"When someone wants to contact any particular router, they first must get"
+" \n"
+"its RouterInfo from the network database, which will tell them whether "
+"they \n"
+"can connect directly (e.g. the peer has a publicly reachable interface) \n"
+"or whether they need to contact them indirectly. Direct connections occur"
+" \n"
+"as normal, while indirect connections are done through one of the "
+"published \n"
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:98
+msgid ""
+"When a router just wants to get a message or two to a specific hidden "
+"peer, \n"
+"they can just use the indirect tunnel for sending the payload. However, \n"
+"if the router wants to talk to the hidden peer often (for instance, as "
+"part \n"
+"of a tunnel), they will send a garlic routed message through the indirect"
+" \n"
+"tunnel to that hidden peer which unwraps to contain a message which "
+"should \n"
+"be sent to the originating router. That hidden peer then establishes an \n"
+"outbound connection to the originating router and from then on, those two"
+" \n"
+"routers can talk to each other directly over that newly established "
+"direct \n"
+"connection."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:109
+msgid ""
+"Of course, that only works if the originating peer can receive "
+"connections \n"
+"(they aren't also hidden). However, if the originating peer is hidden, "
+"they \n"
+"can simply direct the garlic routed message to come back to the "
+"originating \n"
+"peer's inbound tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:115
+msgid ""
+"This is not meant to provide a way for a peer's IP address to be "
+"concealed, \n"
+"merely as a way to let people behind firewalls and NATs fully operate "
+"within \n"
+"the network. Concealing the peer's IP address adds a little more work, as"
+" \n"
+"described below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:121
+msgid ""
+"With this technique, any router can participate as any part of a tunnel."
+" \n"
+"For efficiency purposes, a hidden peer would be a bad choice for an "
+"inbound \n"
+"gateway, and within any given tunnel, two neighboring peers wouldn't want"
+" \n"
+"to be hidden. But that is not technically necessary."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:133
+msgid "Both UDP and NIO have been Implemented in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:134
+msgid ""
+"Standard TCP communication in Java generally requires blocking socket \n"
+"calls, and to keep a blocked socket from hanging the entire system, those"
+" \n"
+"blocking calls are done on their own threads. Our current TCP transport \n"
+"is implemented in a naive fashion - for each peer we are talking to, we \n"
+"have one thread reading and one thread writing. The reader thread simply"
+" \n"
+"loops a bunch of read() calls, building I2NP messages and adding them \n"
+"to our internal inbound message queue, and the writer thread pulls "
+"messages \n"
+"off a per-connection outbound message queue and shoves the data through \n"
+"write() calls."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:145
+msgid ""
+"We do this fairly efficiently, from a CPU perspective - at any time, \n"
+"almost all of these threads are sitting idle, blocked waiting for "
+"something \n"
+"to do. However, each thread consumes real resources (on older Linux "
+"kernels, \n"
+"for instance, each thread would often be implemented as a fork()'ed "
+"process). \n"
+"As the network grows, the number of peers each router will want to talk \n"
+"with will increase (remember, I2P is fully connected, meaning that any \n"
+"given peer should know how to get a message to any other peer, and "
+"restricted \n"
+"route support will probably not significantly reduce the number of "
+"connections \n"
+"necessary). This means that with a 100,000 router network, each router \n"
+"will have up to 199,998 threads just to deal with the TCP connections!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:157
+msgid ""
+"Obviously, that just won't work. We need to use a transport layer that \n"
+"can scale. In Java, we have two main camps:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:162
+#, python-format
+msgid ""
+"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:165
+msgid ""
+"Sending and receiving UDP datagrams is a connectionless operation - if \n"
+"we are communicating with 100,000 peers, we simply stick the UDP packets"
+" \n"
+"in a queue and have a single thread pulling them off the queue and "
+"shoving \n"
+"them out the pipe (and to receive, have a single thread pulling in any \n"
+"UDP packets received and adding them to an inbound queue)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:172
+msgid ""
+"However, moving to UDP means losing the benefits of TCP's ordering, "
+"congestion \n"
+"control, MTU discovery, etc. Implementing that code will take significant"
+" \n"
+"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n"
+"a while ago I was taking some measurements in the simulator and on the \n"
+"live net, and the vast majority of messages transferred would fit easily"
+" \n"
+"within a single unfragmented UDP packet, and the largest of the messages"
+" \n"
+"would fit within 20-30 packets. As mule pointed out, TCP adds a "
+"significant \n"
+"overhead when dealing with so many small packets, as the ACKs are within"
+" \n"
+"an order of magnitude in size. With UDP, we can optimize the transport \n"
+"for both efficiency and resilience by taking into account I2P's "
+"particular \n"
+"needs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:185
+msgid "It will be a lot of work though."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:188
+msgid "NIO or NBIO"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:189
+msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:192
+msgid ""
+"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java"
+" \n"
+"developers to take advantage of the operating system's nonblocking IO \n"
+"capabilities - allowing you to maintain a large number of concurrent IO \n"
+"operations without requiring a separate thread for each. There is much \n"
+"promise with this approach, as we can scalable handle a large number of \n"
+"concurrent connections and we don't have to write a mini-TCP stack with \n"
+"UDP. However, the NIO packages have not proven themselves to be battle-"
+"ready, \n"
+"as the Freenet developer's found. In addition, requiring NIO support "
+"would \n"
+"mean we can't run on any of the open source JVMs like Kaffe, \n"
+"as GNU/Classpath has only "
+"limited \n"
+"support for NIO. (note: this may not be the case anymore, as there \n"
+"has been some progress on Classpath's NIO, but it is an unknown "
+"quantity)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:206
+#, python-format
+msgid ""
+"Another alternative along the same lines is the Non"
+" \n"
+"Blocking I/O package - essentially a cleanroom NIO implementation \n"
+"(written before NIO was around). It works by using some native OS code \n"
+"to do the nonblocking IO, passing off events through Java. It seems to \n"
+"be working with Kaffe, though there doesn't seem to be much development \n"
+"activity on it lately (likely due to 1.4's NIO deployment)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:221
+msgid ""
+"Within the current network database and profile management "
+"implementation, \n"
+"we have taken the liberty of some practical shortcuts. For instance, we \n"
+"don't have the code to drop peer references from the K-buckets, as we \n"
+"don't have enough peers to even plausibly fill any of them, so instead, \n"
+"we just keep the peers in whatever bucket is appropriate. Another example"
+" \n"
+"deals with the peer profiles - the memory required to maintain each "
+"peer's \n"
+"profile is small enough that we can keep thousands of full blown profiles"
+" \n"
+"in memory without problems. While we have the capacity to use trimmed \n"
+"down profiles (which we can maintain 100s of thousands in memory), we \n"
+"don't have any code to deal with moving a profile from a \"minimal "
+"profile\" \n"
+"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to"
+" simply \n"
+"eject a profile altogether. It just wouldn't be practical to write that \n"
+"code yet, since we aren't going to need it for a while."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:236
+msgid ""
+"That said, as the network grows we are going to want to keep these "
+"considerations \n"
+"in mind. We will have some work to do, but we can put it off for later."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:248
+#: i2p2www/pages/site/get-involved/todo.html:332
+#, python-format
+msgid ""
+"Addressed in I2P 0.5 as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:251
+msgid ""
+"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n"
+"going to Dave, then to Charlie, then Bob, and finally Alice "
+"(A<--B<--C<--D<--E), \n"
+"all five of them will know they are participating in tunnel \"123\", as \n"
+"the messages are tagged as such. What we want to do is give each hop "
+"their \n"
+"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n"
+"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n"
+"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n"
+"the tunnel had the same tunnel ID, collusion attacks aren't much work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:261
+msgid ""
+"Adding a unique tunnel ID per hop isn't hard, but by itself, "
+"insufficient. \n"
+"If Dave and Bob are under the control of the same attacker, they wouldn't"
+" \n"
+"be able to tell they are in the same tunnel due to the tunnel ID, but \n"
+"would be able to tell by the message bodies and verification structures \n"
+"by simply comparing them. To prevent that, the tunnel must use layered \n"
+"encryption along the path, both on the payload of the tunneled message \n"
+"and on the verification structure (used to prevent simple tagging "
+"attacks). \n"
+"This requires some simple modifications to the TunnelMessage, as well \n"
+"as the inclusion of per-hop secret keys delivered during tunnel creation"
+" \n"
+"and given to the tunnel's gateway. We must fix a maximum tunnel length \n"
+"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n"
+"of the 16 delivered secret keys, in reverse order, and to encrypt the \n"
+"signature of the hash of the (encrypted) payload at each step. The "
+"gateway \n"
+"then sends that 16-step encrypted message, along with a 16-step and "
+"16-wide \n"
+"encrypted mapping to the first hop, which then decrypts the mapping and \n"
+"the payload with their secret key, looking in the 16-wide mapping for \n"
+"the entry associated with their own hop (keyed by the per-hop tunnel ID)"
+" \n"
+"and verifying the payload by checking it against the associated signed \n"
+"hash."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:282
+msgid ""
+"The tunnel gateway does still have more information than the other peers"
+" \n"
+"in the tunnel, and compromising both the gateway and a tunnel participant"
+" \n"
+"would allow those peers to collude, exposing the fact that they are both"
+" \n"
+"in the same tunnel. In addition, neighboring peers know that they are \n"
+"in the same tunnel anyway, as they know who they send the message to (and"
+" \n"
+"with IP-based transports without restricted routes, they know who they \n"
+"got it from). However, the above two techniques significantly increase \n"
+"the cost of gaining meaningful samples when dealing with longer tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:298
+msgid "Implemented in release 0.6.2"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:301
+#, python-format
+msgid ""
+"As Connelly proposed to deal with the\n"
+"predecessor attack (2008\n"
+"update), keeping the order of peers within our tunnels consistent \n"
+"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n"
+"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n"
+"get to substantially sample Alice's peer selection group. We may even \n"
+"want to explicitly allow Bob to participate in Alice's tunnels in only \n"
+"one way - receiving a message from Dave and sending it to Charlie - and \n"
+"if any of those peers are not available to participate in the tunnel (due"
+" \n"
+"to overload, network disconnection, etc), avoid asking Bob to participate"
+" \n"
+"in any tunnels until they are back online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:316
+msgid ""
+"More analysis is necessary for revising the tunnel creation - at the \n"
+"moment, we simply select and order randomly within the peer's top tier \n"
+"of peers (ones with fast + high capacity)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:321
+msgid ""
+"Adding a strict ordering to peers in a tunnel also improves the anonymity"
+" \n"
+"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway"
+" \n"
+"is always the same would be particularly damning. However, peers with \n"
+"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n"
+"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n"
+"duration) minutes, use a 1-hop tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:338
+msgid ""
+"Without tunnel length permutation, if someone were to somehow detect that"
+" \n"
+"a destination had a particular number of hops, it might be able to use "
+"that \n"
+"information to identify the router the destination is located on, per the"
+" \n"
+"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n"
+"receives a tunnel message from Charlie and forwards it to Alice, Bob "
+"knows \n"
+"Alice is the final router in the tunnel. If Bob were to identify what "
+"destination \n"
+"that tunnel served (by means of colluding with the gateway and harvesting"
+" \n"
+"the network database for all of the LeaseSets), he would know the router"
+" \n"
+"on which that destination is located (and without restricted routes, that"
+" \n"
+"would mean what IP address the destination is on)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:350
+msgid ""
+"It is to counter user behavior that tunnel lengths should be permuted, \n"
+"using algorithms based on the length requested (for example, the 1/MTBF \n"
+"length change for 0-hop tunnels outlined above)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:360
+msgid ""
+"The restricted route functionality described before was simply a "
+"functional \n"
+"issue - how to let peers who would not otherwise be able to communicate \n"
+"do so. However, the concept of allowing restricted routes includes "
+"additional \n"
+"capabilities. For instance, if a router absolutely cannot risk "
+"communicating \n"
+"directly with any untrusted peers, they can set up trusted links through"
+" \n"
+"those peers, using them to both send and receive all of its messages. \n"
+"Those hidden peers who want to be completely isolated would also refuse \n"
+"to connect to peers who attempt to get them to (as demonstrated by the \n"
+"garlic routing technique outlined before) - they can simply take the "
+"garlic \n"
+"clove that has a request for delivery to a particular peer and tunnel \n"
+"route that message out one of the hidden peer's trusted links with "
+"instructions \n"
+"to forward it as requested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:379
+#, python-format
+msgid ""
+"Within the network, we will want some way to deter people from consuming"
+" \n"
+"too many resources or from creating so many peers to mount a Sybil \n"
+"attack. Traditional techniques such as having a peer see who is "
+"requesting \n"
+"a resource or running a peer aren't appropriate for use within I2P, as \n"
+"doing so would compromise the anonymity of the system. Instead, we want \n"
+"to make certain requests \"expensive\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:387
+msgid ""
+"Hashcash is one technique that \n"
+"we can use to anonymously increase the \"cost\" of doing certain "
+"activities, \n"
+"such as creating a new router identity (done only once on installation),"
+" \n"
+"creating a new destination (done only once when creating a service), or \n"
+"requesting that a peer participate in a tunnel (done often, perhaps 2-300"
+" \n"
+"times per hour). We don't know the \"correct\" cost of each type of "
+"certificate \n"
+"yet, but with some research and experimentation, we could set a base "
+"level \n"
+"that is sufficiently expensive while not an excessive burden for people \n"
+"with few resources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:398
+msgid ""
+"There are a few other algorithms that we can explore for making those \n"
+"requests for resources \"nonfree\", and further research on that front is"
+" \n"
+"appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:408
+#, python-format
+msgid ""
+"To powerful passive external observers as well as large colluding "
+"internal \n"
+"observers, standard tunnel routing is vulnerable to traffic analysis "
+"attacks \n"
+"- simply watching the size and frequency of messages being passed between"
+" \n"
+"routers. To defend against these, we will want to essentially turn some \n"
+"of the tunnels into its own mix cascade - delaying messages received at \n"
+"the gateway and passing them in batches, reordering them as necessary, \n"
+"and injecting dummy messages (indistinguishable from other \"real\" "
+"tunnel \n"
+"messages by peers in the path). There has been a significant amount of \n"
+"research \n"
+"on these algorithms that we can lean on prior to implementing the various"
+" \n"
+"tunnel mixing strategies."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:421
+msgid ""
+"In addition to the anonymity aspects of more varied tunnel operation, \n"
+"there is a functional dimension as well. Each peer only has a certain \n"
+"amount of data they can route for the network, and to keep any particular"
+" \n"
+"tunnel from consuming an unreasonable portion of that bandwidth, they \n"
+"will want to include some throttles on the tunnel. For instance, a tunnel"
+" \n"
+"may be configured to throttle itself after passing 600 messages (1 per \n"
+"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n"
+"last minute). Excess messages may be delayed or summarily dropped. With \n"
+"this sort of throttling, peers can provide ATM-like QoS support for their"
+" \n"
+"tunnels, refusing to agree to allocate more bandwidth than the peer has \n"
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:434
+msgid ""
+"In addition, we may want to implement code to dynamically reroute tunnels"
+" \n"
+"to avoid failed peers or to inject additional hops into the path. This \n"
+"can be done by garlic routing a message to any particular peer in a "
+"tunnel \n"
+"with instructions to redefine the next-hop in the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:445
+msgid ""
+"Beyond the per-tunnel batching and mixing strategy, there are further \n"
+"capabilities for protecting against powerful attackers, such as allowing"
+" \n"
+"each step in a garlic routed path to define a delay or window in which \n"
+"it should be forwarded on. This would enable protections against the long"
+" \n"
+"term intersection attack, as a peer could send a message that looks "
+"perfectly \n"
+"standard to most peers that pass it along, except at any peers where the"
+" \n"
+"clove exposed includes delay instructions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:457
+#, python-format
+msgid ""
+"Performance related improvements are listed on the\n"
+"Performance page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2
+msgid "Bounty Arabic translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3
+#: i2p2www/pages/site/get-involved/bounties/index.html:119
+msgid "Arabic translation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P echelon set out this bounty for translation\n"
+"of the I2P web page and I2P router console into Arabic."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12
+msgid "This bounty is set into 2 subparts:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14
+msgid "Part 1 is translation of the webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17
+msgid ""
+"For collecting the bounty of 20 BTC you need to translate the following "
+"pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25
+msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27
+msgid ""
+"Part 2 is the translation of the router console. The router console was\n"
+"partly translated and the bounty of 80 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34
+msgid "Judge is echelon."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2
+msgid "Bounty creating a I2P native Bitcoin client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3
+msgid "BTC I2P native client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to create a I2P native Bitcoin client. \n"
+"It should integrate with other client via the I2P network and via "
+"gateways to\n"
+"the existant bitcoin network."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15
+msgid "Judge is psychonaut who donated the first 30 € to this bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
+msgid "Bounty datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:3
+msgid "datastore"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:6
+msgid ""
+"To improve I2P's usage and to be independent of routers \n"
+"online status we want a datastorage as a extension to I2P.\n"
+"Like in Freenet the datastorage should be distributed and every\n"
+"participating node should be able to configure his options.\n"
+"The files should be saved in chunks and at least 2-3 times to\n"
+"obtain redundancy. Usage of storage space should be auto balanced.\n"
+"As it is a extra application, it should work flawless within I2P and\n"
+"cooperate nice with the I2P router. Maybe a integration within the\n"
+"webpage/router could be done."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:17
+msgid ""
+"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n"
+"\"eepsites in datastorage\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:21
+msgid ""
+"The frost for I2P datastorage bounty is paid for a frost like program \n"
+"with which files/messages are stored into database and got from database."
+"\n"
+"It needs to work with a GUI."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:26
+msgid ""
+"The eepsite served out of I2P datastorage extends a I2P router to send\n"
+"out eepsites out of the I2P datastorage. All files for eepsites need to "
+"be\n"
+"saved inside of datastorage and are taken from it.\n"
+"Extension:\n"
+"For better integration all datastorage participants could serve that "
+"eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:36
+msgid ""
+"For bounties to be declared done and paid, we need the program AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2
+msgid "Bounty I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3
+msgid "I2P Ubuntu/Debian package"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6
+msgid ""
+"For the future of I2P and in order to attract more people\n"
+"to I2P, this bounty was set for including an I2P package into the Ubuntu "
+"and Debian \n"
+"archive mirrors.\n"
+"To claim this bounty, the I2P router package needs to be available from\n"
+"Ubuntu and Debian archive mirrors and Debian bug \n"
+"448638 \n"
+"needs to be closed successfully."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2
+msgid "Bounty I2PHex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3
+msgid "i2phex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2PHex P2P ArneBab setout the bounty for implementing actual\n"
+"Phex code onto I2PHex."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:2
+msgid "Bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:5
+msgid "Bounties for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:6
+msgid ""
+"While we always gratefully accept any contributions of code, \n"
+"documentation, and the like, there are other ways to help I2P move \n"
+"forward.  As with any open source project, our goals would be achieved "
+"more \n"
+"rapidly if we were able to support all of our contributors to work on \n"
+"I2P full time.  However, as with any open source project, that's not a \n"
+"possibility.  Instead, we are making use of a bounty system, whereby \n"
+"anyone can get support for working on something that people want \n"
+"implemented, and people who want to contribute to I2P can be assured that"
+" \n"
+"their support goes to what they care about."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:18
+msgid ""
+"We are also keeping open the ability for people who want to support I2P \n"
+"but don't have strong feelings about the bounties available.  Those "
+"people\n"
+"can simply put their trust in the I2P team to do what we feel is best by\n"
+"donating to a catch-all general fund that will be used as deemed \n"
+"necessary - allocated to various bounties, covering incidentals (hosting,"
+" \n"
+"etc), and the like."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:27
+msgid "Current bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Name"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Status"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Judge"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Dev"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Bounty"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:32
+msgid "Frost for I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:33
+#: i2p2www/pages/site/get-involved/bounties/index.html:40
+#: i2p2www/pages/site/get-involved/bounties/index.html:47
+#: i2p2www/pages/site/get-involved/bounties/index.html:54
+#: i2p2www/pages/site/get-involved/bounties/index.html:75
+#: i2p2www/pages/site/get-involved/bounties/index.html:82
+msgid "Proposal in development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:35
+#: i2p2www/pages/site/get-involved/bounties/index.html:42
+#: i2p2www/pages/site/get-involved/bounties/index.html:49
+#: i2p2www/pages/site/get-involved/bounties/index.html:56
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+#: i2p2www/pages/site/get-involved/bounties/index.html:97
+msgid "vacant"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:39
+msgid "Eepsites served out of I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:46
+msgid "Backporting Phex code onto I2PHex"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:53
+msgid "I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:60
+msgid "Bitcoin client for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:61
+msgid "Done, phase of verification"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:67
+msgid "Unit tests and Multi-router Simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:68
+msgid "Partly done, partly in work, partly still open"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:89
+msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:94
+msgid "Bundling bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:95
+msgid "Proposed"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:102
+msgid "Claimed bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:107
+msgid "Make I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:114
+msgid "Setting up a SILC server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:124
+msgid "Datastore over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:129
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
+msgid "Russian translation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:134
+msgid "Swarming file transfer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:139
+msgid "Streaming library window size"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:144
+msgid "IRC connect time monitor"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:149
+msgid "Unit tests (part 1)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:161
+msgid ""
+"Dev lists anyone who may already be working on the bounty - collaboration"
+" is\n"
+"preferred, so if you're interested in working on it, please contact one "
+"of the\n"
+"people listed!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2
+msgid "Bounty I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3
+msgid "native IPv6 I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n"
+"To claim this bounty, the I2P router needs to run full on native\n"
+"IPv6 connections like it does on IPv4."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:17
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
+msgid ""
+"For bounties to be declared done and paid, we need the plugin AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:2
+msgid "NetDB Backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:3
+msgid "netDB backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:7
+msgid ""
+"The current NetDB implementation (namely the FloodFill system)\n"
+"needs to be extended with another backend to improve reliability,\n"
+"reduce attack surface and solve the scalability issue for the \n"
+"coming years."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:14
+msgid ""
+"A solution likely based on a DHT will be investigated and \n"
+"finally implemented."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2
+msgid "Bounty russian translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P a anonymous donator set out the bounty for translation\n"
+"of the I2P web page and I2P router console into russian language."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17
+msgid ""
+"For collecting the bounty of $115 USD you need to translate the following"
+" pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30
+msgid ""
+"Part 2 is the translation of the router console. The whole router console"
+" needs\n"
+"to be translated to collect the bounty of $115 USD."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37
+msgid "Judge is the russian donor."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:2
+msgid "Bounty migrate I2P IRC to SILC"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:3
+msgid "I2P silc server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:7
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to setup and host a I2P SILC server.   \n"
+"This will allow people to send files over their messaging servers and "
+"have intrinsic security built into the protocol."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:12
+msgid ""
+"A silc server needs to be set up and run for at least 3 month time to get"
+" payed. \n"
+"A second server should be set up, to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:16
+msgid ""
+"Bounty was withdrawn and money donated to returningnovice and general "
+"fund."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:22
+msgid "Judge is An Anonymous Secret Society, society@mail.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3
+msgid "Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7
+msgid ""
+"Beside of I2P we want to encourage users\n"
+"to care more about anonymity and security. As I2P is a low \n"
+"latency network with its natural limits, the software SYNDIE\n"
+"can overcome some of these limits and provide better anonymity\n"
+"for people who really need it."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14
+msgid ""
+"For our bad sake the syndie project was out of development for \n"
+"quite a long time yet (5 years). To get a fresh and new built \n"
+"with needed bugfixes we set out this bounty. Also syndie needs\n"
+"some enhancements and a better GUI for users to work with it.\n"
+"Current bounty sum is 50 Bitcoin."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22
+msgid ""
+"The latest Syndie coding rally did improve the situation of the\n"
+"Syndie package dramatically. A new Syndie package with bugfixes\n"
+"was created and made available on different webpages.\n"
+"As a result of this work, the bounty sum was reduced and\n"
+"the withdrawn money moved to the IPv6 bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2
+msgid "Bounty unittests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3
+msgid "unit test"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7
+msgid ""
+"To improve I2P's maintainability, we want to have a solid set of\n"
+"automated unit tests for the critical code.  While we do have some\n"
+"unit tests at the moment, they are ad-hoc and partly unfinished.  \n"
+"This bounty is for someone to check the existing tests and move over\n"
+"old ones to jUnit, automate their execution, extend them to provide \n"
+"better code coverage, and publish the report online.  Its a massive \n"
+"effort, but can be broken down into phases, listed below (phase 2 \n"
+"must occur first, but further phases may happen in any order).\n"
+"As this needs some reading of code, it is the best start point for\n"
+"new devs to get a good overview of I2P code and coding. A good job\n"
+"for college students, interns or anyone who is just interested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20
+msgid ""
+"Take care! Jobs and bounties shuffled a bit!\n"
+"Phase 6,7 and 8 are still open!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112
+#, python-format
+msgid "Phase %(phase)s:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27
+msgid "CI jenkins and IRC bot"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114
+#, python-format
+msgid "Bounty: %(euro)s €"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29
+msgid "server runs and this section is blocked"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31
+msgid ""
+"To collect this bounty, a continuous integration server (Jenkins,\n"
+"old name was Hudson) must be set up and a connected IRC bot needs \n"
+"to set up in the channel #i2p-dev on IRC2p network to print out\n"
+"results of build tests.
            \n"
+"The server needs to be run long term."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41
+msgid "Check existing SDK tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69
+msgid "paid to str4d"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45
+#, python-format
+msgid ""
+"To collect this bounty, the existing SDK tests must be checked \n"
+"and made to work again. The need to be integrated into the ant \n"
+"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g."
+" \n"
+"Clover).  The ant script\n"
+"must be capable of generating test status results as a web page, \n"
+"which will be published online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56
+msgid "SDK test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80
+msgid "paid to unittests dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60
+msgid ""
+"To collect this bounty, the automated unit tests of the SDK \n"
+"(i2p/core/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67
+msgid "Router test migration"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71
+msgid ""
+"As with phase 2, the existing unit tests for the router must be\n"
+"moved over to the automated system."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78
+msgid "Router test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82
+msgid ""
+"To collect this bounty, the automated unit tests of the router \n"
+"(i2p/router/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89
+msgid "Streaming lib tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94
+msgid ""
+"To collect this bounty, a new set of unit tests must meet a \n"
+"measured code coverage of 90% of the streaming lib \n"
+"(i2p/apps/ministreaming/ and i2p/apps/streaming/)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102
+msgid "Unit tests coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106
+msgid ""
+"To collect this bounty, all above unit tests must meet the 100%\n"
+"coverage marker (except for log statements)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113
+msgid "MultiRouter simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115
+msgid "will be split in more sub-tasks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117
+msgid ""
+"To collect this bounty, the existing in-memory multi-router\n"
+"simulation must be checked, made work again and extend to simulate\n"
+"lots of routers in memory on a single machine. This bounty will\n"
+"be split in more fine grained subworks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126
+msgid ""
+"Judge on all these works is the donor and donor decides if a phase is\n"
+"called succesfull done and money can be paid."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2
+msgid "Bounty I2P vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3
+msgid "vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P torrent P2P I setout the bounty for a working I2P vuze\n"
+"plugin.\n"
+"The plugin needs to be official and submitted to vuze for publication\n"
+"on their webpage/repository for plugins.\n"
+"It should be easy to install and configured, work smooth and flawless.\n"
+"Configuration should be friendly to starters and made easy to be "
+"anonymous.\n"
+"It should work with *.b32.i2p destinations as with signed (516++ bits) \n"
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:2
+msgid "Application Development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:3
+msgid "May 2013"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:6
+msgid "Application Development Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:8
+msgid "Contents"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:10
+#: i2p2www/pages/site/get-involved/develop/applications.html:16
+msgid "Why write I2P-specific code?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:11
+#: i2p2www/pages/site/get-involved/develop/applications.html:102
+msgid "Important concepts"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:12
+#: i2p2www/pages/site/get-involved/develop/applications.html:190
+msgid "Development options"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:13
+#: i2p2www/pages/site/get-involved/develop/applications.html:303
+msgid "Start developing - a simple guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:18
+#, python-format
+msgid ""
+"There are multiple ways to use applications in I2P.\n"
+"Using I2PTunnel,\n"
+"you can use regular applications without needing to program explicit I2P "
+"support.\n"
+"This is very effective for client-server scenario's,\n"
+"where you need to connect to a single website.\n"
+"You can simply create a tunnel using I2PTunnel to connect to that "
+"website, as shown in Figure 1."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:26
+msgid ""
+"If your application is distributed, it will require connections to a "
+"large amount of peers.\n"
+"Using I2PTunnel, you will need to create a new tunnel for each peer you "
+"want to contact,\n"
+"as shown in Figure 2.\n"
+"This process can of course be automated, but running a lot of I2PTunnel "
+"instances creates a large amount of overhead.\n"
+"In addition, with many protocols you will need to force everyone to \n"
+"use the same set of ports for all peers - e.g. if you want to reliably "
+"run DCC \n"
+"chat, everyone needs to agree that port 10001 is Alice, port 10002 is "
+"Bob, port \n"
+"10003 is Charlie, and so on, since the protocol includes TCP/IP specific "
+"information\n"
+"(host and port)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:37
+msgid ""
+"General network applications often send a lot of additional data that "
+"could be used to identify users.\n"
+"Hostnames, port numbers, time zones, character sets, etc. are often sent "
+"without informing the user.\n"
+"As such, designing the network protocol specifically with anonymity in "
+"mind\n"
+"can avoid compromising user identities."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:43
+msgid ""
+"There are also efficiency considerations to review when determining how "
+"to \n"
+"interact on top of I2P.  The streaming library and things built on top of"
+" it\n"
+"operate with handshakes similar to TCP, while the core I2P protocols "
+"(I2NP and I2CP)\n"
+"are strictly message based (like UDP or in some instances raw IP).  The "
+"important\n"
+"distinction is that with I2P, communication is operating over a long fat "
+"network - \n"
+"each end to end message will have nontrivial latencies, but may contain "
+"payloads \n"
+"of up to several KB.  An application that needs a simple request and "
+"response can get rid\n"
+"of any state and drop the latency incurred by the startup and teardown "
+"handshakes\n"
+"by using (best effort) datagrams without having to worry about MTU "
+"detection or \n"
+"fragmentation of messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:57
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid ""
+"Creating a server-client connection using I2PTunnel only requires "
+"creating a single tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid "Figure 1:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:64
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid ""
+"Setting up connections for a peer-to-peer applications requires a very "
+"large amount of tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid "Figure 2:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:70
+msgid "In summary, a number of reasons to write I2P-specific code:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:74
+msgid ""
+"Creating a large amount of I2PTunnel instances consumes a non-trivial "
+"amount of resources,\n"
+"which is problematic for distributed applications (a new tunnel is "
+"required for each peer)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:78
+msgid ""
+"General network protocols often send a lot of additional data that can be"
+" used to identify users.\n"
+"Programming specifically for I2P allows the creation of a network "
+"protocol\n"
+"that does not leak such information, keeping users anonymous and secure."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:83
+msgid ""
+"Network protocols designed for use on the regular internet can be "
+"inefficient\n"
+"on I2P, which is a network with a much higher latency."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:90
+#, python-format
+msgid ""
+"I2P supports a standard plugins interface for"
+" developers\n"
+"so that applications may be easily integrated and distributed."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:96
+msgid ""
+"Applications written in Java and accessible/runnable\n"
+"using an HTML interface via the standard webapps/app.war\n"
+"may be considered for inclusion in the i2p distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:104
+msgid "There are a few changes that require adjusting to when using I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:108
+msgid "Destination ~= host+port"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:110
+msgid ""
+"An application running on I2P sends messages from and receives messages "
+"to a\n"
+"unique cryptographically secure end point - a \"destination\".  In TCP or"
+" UDP\n"
+"terms, a destination could (largely) be considered the equivalent of a "
+"hostname\n"
+"plus port number pair, though there are a few differences."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:118
+msgid ""
+"An I2P destination itself is a cryptographic construct - all data sent to"
+" one is \n"
+"encrypted as if there were universal deployment of IPsec with the "
+"(anonymized)\n"
+"location of the end point signed as if there were universal deployment of"
+" DNSSEC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:123
+msgid ""
+"I2P destinations are mobile identifiers - they can be moved from one I2P "
+"router\n"
+"to another (or it can even \"multihome\" - operate on multiple routers at"
+"\n"
+"once).  This is quite different from the TCP or UDP world where a single "
+"end point (port)\n"
+"must stay on a single host."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:130
+msgid ""
+"I2P destinations are ugly and large - behind the scenes, they contain a "
+"2048 bit ElGamal\n"
+"public key for encryption, a 1024 bit DSA public key for signing, and a "
+"variable size \n"
+"certificate, which may contain proof of work or blinded data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:135
+#, python-format
+msgid ""
+"There are existing ways to refer to these large and ugly destinations by "
+"short\n"
+"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not "
+"guarantee\n"
+"globally uniqueness (since they're stored locally in a database on each "
+"person's machine)\n"
+"and the current mechanism is not especially scalable nor secure (updates "
+"to the host list are\n"
+"managed using \"subscriptions\" to naming services).\n"
+"There may be some secure, human readable, scalable, and globally \n"
+"unique, naming system some day, but applications shouldn't depend upon it"
+" being in place,\n"
+"since there are those who don't think such a beast is possible.\n"
+"Further information on the naming system is "
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:149
+#, python-format
+msgid ""
+"While most applications do not need to distinguish protocols and ports,\n"
+"I2P does support them. Complex applications may specify a "
+"protocol,\n"
+"from port, and to port, on a per-message basis, to multiplex traffic on\n"
+"a single destination.\n"
+"See the datagram page for details.\n"
+"Simple applications operate by listening for \"all protocols\" on \"all "
+"ports\" of a destination."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:158
+msgid "Anonymity and confidentiality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:160
+msgid ""
+"I2P has transparent end to end encryption\n"
+"and authentication for all data passed over the network - if Bob sends to"
+" Alice's destination,\n"
+"only Alice's destination can receive it, and if Bob is using the "
+"datagrams or streaming \n"
+"library, Alice knows for certain that Bob's destination is the one who "
+"sent the data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:167
+msgid ""
+"Of course, I2P transparently anonymizes the\n"
+"data sent between Alice and Bob, but it does nothing to anonymize the "
+"content of what they\n"
+"send.  For instance, if Alice sends Bob a form with her full name, "
+"government IDs, and \n"
+"credit card numbers, there is nothing I2P can do.  As such, protocols and"
+" applications should \n"
+"keep in mind what information they are trying to protect and what "
+"information they are willing\n"
+"to expose."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:176
+msgid "I2P datagrams can be up to several KB"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:178
+#, python-format
+msgid ""
+"Applications that use I2P datagrams (either raw or repliable ones) can "
+"essentially be thought\n"
+"of in terms of UDP - the datagrams are unordered, best effort, and "
+"connectionless - but unlike\n"
+"UDP, applications don't need to worry about MTU detection and can simply "
+"fire off large datagrams.\n"
+"While the upper limit is nominally 32 KB, the message is fragmented for "
+"transport, thus dropping\n"
+"the reliability of the whole. Datagrams over about 10 KB are not "
+"currently recommended.\n"
+"See the datagram page for details.\n"
+"For many applications, 10 KB of data is sufficient for an\n"
+"entire request or response, allowing them to transparently operate in I2P"
+" as a UDP-like \n"
+"application without having to write fragmentation, resends, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:192
+msgid ""
+"There are several means of sending data over I2P, each with their own "
+"pros and cons.\n"
+"The streaming lib is the recommended interface, used by the majority of "
+"I2P applications."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:197
+msgid "Streaming Lib"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:198
+#, python-format
+msgid ""
+"The full streaming library is now the "
+"standard\n"
+"interface. It allows programming using TCP-like sockets, as explained in "
+"the Streaming development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:204
+#, python-format
+msgid ""
+"BOB is the Basic Open Bridge,\n"
+"allowing an application in any language to make streaming connections \n"
+"to and from I2P. At this point in time it lacks UDP support, but UDP "
+"support\n"
+"is planned in the near future. BOB also contains several tools, such as \n"
+"destination key generation, and verification that an address conforms to"
+" \n"
+"I2P specifications. Up to date info and applications that use BOB can be"
+" \n"
+"found at this eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:217
+msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:218
+#, python-format
+msgid ""
+"SAM is the Simple Anonymous Messaging protocol, "
+"allowing an\n"
+"application written in any language to talk to a SAM bridge through a "
+"plain TCP socket and have\n"
+"that bridge multiplex all of its I2P traffic, transparently coordinating "
+"the encryption/decryption\n"
+"and event based handling.  SAM supports three styles of operation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:225
+msgid ""
+"streams, for when Alice and Bob want to send data to each other reliably "
+"and in order"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:228
+msgid ""
+"repliable datagrams, for when Alice wants to send Bob a message that Bob "
+"can reply to"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:231
+msgid ""
+"raw datagrams, for when Alice wants to squeeze the most bandwidth and "
+"performance as possible,\n"
+"and Bob doesn't care whether the data's sender is authenticated or not "
+"(e.g. the data transferred\n"
+"is self authenticating)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:237
+msgid ""
+"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n"
+"multiplexing/demultiplexing. Each I2P stream is handled by its own socket"
+" between the application\n"
+"and the SAM bridge. Besides, datagrams can be sent and received by the "
+"application through datagram\n"
+"communications with the SAM bridge."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:244
+#, python-format
+msgid ""
+"SAM V2 is a new version used by imule\n"
+"that fixes some of the problems in SAM.\n"
+"
            \n"
+"SAM V3 is used by imule since version 1.4.0."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:252
+msgid ""
+"The I2PTunnel application allows applications to build specific TCP-like "
+"tunnels to peers \n"
+"by creating either I2PTunnel 'client' applications (which listen on a "
+"specific port and connect\n"
+"to a specific I2P destination whenever a socket to that port is opened) "
+"or I2PTunnel 'server'\n"
+"applications (which listen to a specific I2P destination and whenever it "
+"gets a new I2P \n"
+"connection it outproxies to a specific TCP host/port).  These streams are"
+" 8-bit clean, and are\n"
+"authenticated and secured through the same streaming library that SAM "
+"uses, but there is a \n"
+"nontrivial overhead involved with creating multiple unique I2PTunnel "
+"instances, since each have\n"
+"their own unique I2P destination and their own set of tunnels, keys, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:264
+msgid ""
+"I2P supports a SOCKS V4 and V5 proxy.\n"
+"Outbound connections work well. Inbound (server) and UDP functionality "
+"may be incomplete\n"
+"and untested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:271
+msgid "Removed"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:272
+msgid ""
+"There used to be a simple \"ministreaming\" library,\n"
+"but now ministreaming.jar contains only the interfaces for the full "
+"streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:277
+msgid "Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:278
+msgid "Recommended for UDP-like applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:279
+#, python-format
+msgid ""
+"The Datagram library allows sending UDP-"
+"like packets.\n"
+"It's possible to use:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:284
+msgid "Repliable datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:285
+msgid "Raw datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:289
+msgid "Not recommended"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:290
+#, python-format
+msgid ""
+"I2CP itself is a language independent protocol, "
+"but to implement an I2CP library \n"
+"in something other than Java there is a significant amount of code to be "
+"written (encryption routines, \n"
+"object marshalling, asynchronous message handling, etc).  While someone "
+"could write an I2CP library in \n"
+"C or something else, it would most likely be more useful to use the C SAM"
+" library instead."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:297
+msgid "Web Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:298
+msgid ""
+"I2P comes with the Jetty webserver, and configuring to use the Apache "
+"server instead is straightforward.\n"
+"Any standard web app technology should work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:304
+msgid ""
+"Developing using I2P requires a working I2P installation and a "
+"development environment of your own choice.\n"
+"If you are using Java, you can start development with the streaming library or datagram library.\n"
+"Using another programming language, SAM or BOB can be used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:310
+msgid "Developing with the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:312
+msgid ""
+"The following example shows how to create TCP-like client and server "
+"applications\n"
+"using the streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:317
+msgid "This will require the following libraries in your classpath:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:321
+msgid "The streaming library itself"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:322
+msgid "Factory and interfaces for the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:323
+msgid "Standard I2P classes, data structures, API, and utilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:326
+msgid ""
+"Network communication requires the usage of I2P network sockets.\n"
+"To demonstrate this, we will create an application where a client can "
+"send text messages to a server,\n"
+"who will print the messages and send them back to the client. In other "
+"words, the server will function as an echo."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:331
+msgid ""
+"We will start by initializing the server application. This requires "
+"getting an I2PSocketManager\n"
+"and creating an I2PServerSocket.\n"
+"We will not provide the I2PSocketManagerFactory with the saved keys for "
+"an existing Destination,\n"
+"so it will create a new Destination for us.\n"
+"So we will ask the I2PSocketManager for an I2PSession, so we can find out"
+" the Destination that\n"
+"was created, as we will need to copy and paste that information later so "
+"the client can connect to us."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:362
+msgid "Code example 1: initializing the server application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:364
+msgid ""
+"Once we have an I2PServerSocket, we can create I2PSocket instances to "
+"accept connections from clients.\n"
+"In this example, we will create a single I2PSocket instance, that can "
+"only handle one client at a time.\n"
+"A real server would have to be able to handle multiple clients.\n"
+"To do this, multiple I2PSocket instances would have to be created, each "
+"in separate threads.\n"
+"Once we have created the I2PSocket instance, we read data, print it and "
+"send it back to the client.\n"
+"The bold code is the new code we add."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:448
+msgid "Code example 2: accepting connections from clients and handling messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:452
+msgid ""
+"When you run the above server code, it should print something like this "
+"(but without the line endings, it should just be\n"
+"one huge block of characters):"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:466
+msgid ""
+"This is the base64-representation of the server Destination. The client "
+"will need this string to reach the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:470
+msgid ""
+"Now, we will create the client application. Again, a number of steps are "
+"required for initialization.\n"
+"Again, we will need to start by getting an I2PSocketManager.\n"
+"We won't use an I2PSession and an I2PServerSocket this time.\n"
+"Instead, we will use the server Destination string to start our "
+"connection.\n"
+"We will ask the user for the Destination string, and create an I2PSocket "
+"using this string.\n"
+"Once we have an I2PSocket, we can start sending and receiving data to and"
+" from the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:554
+msgid ""
+"Code example 3: starting the client and connecting it to the server "
+"application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:556
+msgid ""
+"Finally, you can run both the server and the client application.\n"
+"First, start the server application. It will print a Destination string "
+"(like shown above).\n"
+"Next, start the client application. When it requests a Destination "
+"string, you can enter the string printed by the server.\n"
+"The client will then send 'Hello I2P!' (along with a newline) to the "
+"server, who will print the message and send it back to the client."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:562
+msgid "Congratulations, you have successfully communicated over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:566
+msgid "Existing Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:567
+msgid "Contact us if you would like to contribute."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:588
+msgid "Application Ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:590
+msgid "NNTP server - there have been some in the past, none at the moment"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:593
+msgid ""
+"Jabber server - there have been some in the past, and there is one at the"
+" moment, with access to the public internet"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:596
+msgid "PGP Key server and/or proxy"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:599
+msgid ""
+"Content Distribution / DHT applications - resurrect feedspace,\n"
+"port dijjer, look for alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:603
+msgid "Help out with Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:606
+msgid ""
+"Web-based applications - The sky is the limit for hosting web-server-"
+"based\n"
+"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n"
+"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:611
+msgid ""
+"Resurrect some old apps, several previously in the i2p source package -\n"
+"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2
+msgid "I2P Developer's MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4
+msgid "MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5
+msgid ""
+"Monotone servers used by the I2P project require two types of keys to be "
+"used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
+msgid ""
+"Commit Keys to sign changes checked-in to the "
+"respository; and"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10
+msgid ""
+"Transport Keys to push changes to remote "
+"servers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13
+#, python-format
+msgid ""
+"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
+"import the\n"
+"developer commit keys, but only Monotone \n"
+"server operators will need to import the transport keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20
+msgid "Developer Commit keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:255
+msgid "Developer Transport Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:256
+#, python-format
+msgid ""
+"Note: Transport keys are only needed for setting up a\n"
+"Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
+msgid "License Agreements"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
+#, python-format
+msgid "For more information see the licenses page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8
+msgid ""
+"Following is a monotonerc file defining the current trust list.\n"
+"Developers must use this file in ~/.monotone/monotonerc or\n"
+"_MTN/montonerc in their i2p.i2p workspace."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17
+msgid "Agreements"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:2
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115
+msgid "Licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:4
+msgid "I2P Software Licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:5
+#, python-format
+msgid ""
+"As required by our\n"
+"threat model (among other reasons), the \n"
+"software developed to support the anonymous communication \n"
+"network we call I2P must be freely available, open source, \n"
+"and user modifiable.  To meet these criteria, we make use of\n"
+"a variety of legal and software engineering techniques so\n"
+"as to remove as many barriers to entry for those considering\n"
+"making use of or contributing to the I2P effort."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:16
+msgid ""
+"While the information below may be more confusing than just simply \n"
+"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
+"the short answer to the question \"How is I2P licensed?\" is this:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:22
+msgid "All software bundled in the I2P distributions will allow:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:24
+msgid "use without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:25
+msgid ""
+"use with no restrictions on how, when, where, why, or by whom is running "
+"it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:26
+msgid "access to the source code without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:27
+msgid "modifications to the source"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:30
+msgid ""
+"Most of the software guarantees much more - the ability of anyone "
+"to \n"
+"distribute the modified source however they choose.  However, not all of "
+"the \n"
+"software bundled provides this freedom - the GPL restricts the ability of"
+" \n"
+"developers who wish to integrate I2P with their own applications that are"
+" not \n"
+"themselves open source applications.  While we applaud the noble goals of"
+" \n"
+"increasing the resources in the commons, I2P is best served by removing "
+"any\n"
+"barriers that stand in the way of its adoption - if a developer "
+"considering whether\n"
+"they can integrate I2P with their application has to stop and check with "
+"their lawyer,\n"
+"or conduct a code audit to make sure their own source can be released as "
+"GPL-compatible,\n"
+"we lose out."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:43
+msgid "Component licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:44
+msgid ""
+"The I2P distribution contains several resources, reflecting the "
+"partitioning of \n"
+"the source code into components.  Each component has its own license, "
+"which all \n"
+"developers who contribute to it agree to - either by explicitly declaring"
+" the release\n"
+"of code committed under a license compatible with that component, or by "
+"implicitly\n"
+"releasing the code committed under the component's primary license.  Each"
+" of these \n"
+"components has a lead developer who has the final say as to what license "
+"is compatible\n"
+"with the component's primary license, and the I2P project manager has the"
+" final say as\n"
+"to what licenses meet the above four guarantees for inclusion in the I2P "
+"distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:57
+msgid "Component"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:58
+msgid "Source path"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:59
+msgid "Resource"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:60
+msgid "Primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:61
+msgid "Alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:62
+msgid "Lead developer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:271
+msgid "GPL + java exception"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:272
+#, python-format
+msgid ""
+"While it may be redundant, just for clarity the\n"
+"GPL'ed code included within\n"
+"I2PTunnel and other apps must be released under the GPL with an "
+"additional \"exception\"\n"
+"explicitly authorizing the use of Java's standard libraries:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:288
+msgid ""
+"All source code under each component will by default be licensed under "
+"the\n"
+"primary license, unless marked otherwise in the code.  All of the above "
+"is\n"
+"summary of the license terms - please see the specific license for the "
+"component\n"
+"or source code in question for authoritative terms.  Component source "
+"locations and\n"
+"resource packaging may be changed if the repository is reorganized."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:296
+msgid "Commit privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:297
+#, python-format
+msgid ""
+"Developers may push changes to a distributed monotone repository if you\n"
+"receive permission from the person running that repository.\n"
+"See the Monotone Page for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:303
+msgid ""
+"However, to have changes included in a release, developers\n"
+"must be trusted by the release manager (currently zzz).\n"
+"In addition, they must explicitly agree with the above terms to be "
+"trusted.\n"
+"That means that they must send one of the release managers a signed "
+"message affirming that:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:310
+msgid ""
+"Unless marked otherwise, all code I commit is implicitly licensed under\n"
+"the component's primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:314
+msgid ""
+"If specified in the source, the code may be explicitly licensed under one"
+"\n"
+"of the component's alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:318
+msgid ""
+"I have the right to release the code I commit under the terms I\n"
+"am committing it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:324
+#, python-format
+msgid ""
+"If anyone is aware of any instances where the above conditions are not "
+"met,\n"
+"please contact the component lead and/or an I2P release manager with "
+"further\n"
+"information.\n"
+"See developers' license agreements."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
+msgid "Release Signing Key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
+msgid "Releases 0.7.6 and later are signed by zzz. His public key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40
+msgid ""
+"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public "
+"key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2
+msgid "Signed Developer Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4
+msgid ""
+"Keys for zzz, Complication and welterde are provided clearsigned. The key"
+" for jrandom must be\n"
+"verified differently, since he's away, and only left a binary detached\n"
+"signature for his key."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16
+msgid "Monotone keys for zzz"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47
+msgid "Monotone keys for welterde"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79
+msgid "Monotone keys for Complication"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114
+msgid "Monotone keys for jrandom"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
+msgid "Others"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
+msgid ""
+"Tip: To find zzz's GPG key, on his eepsite locate the key "
+"`0xA76E0BED`, with\n"
+"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 "
+"B310 4155\n"
+"76BA A76E 0BED`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49
+msgid ""
+"Tip: To find welterde's GPG key, on public keyservers locate the "
+"key\n"
+"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720"
+" FD81\n"
+"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81
+msgid ""
+"Tip: To find Complication's GPG key, on his eepsite locate the key"
+"\n"
+"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint "
+"`73CF\n"
+"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116
+msgid ""
+"Tip: To find jrandom's GPG key for Syndie releases, on public "
+"keyservers locate\n"
+"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n"
+"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122
+msgid ""
+"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n"
+"deployed in the Syndie Monotone repository, in a file named `mtn-"
+"committers`.\n"
+"That file also had a GPG signature, `mtn-committers.sig`, but it was a "
+"binary\n"
+"detached signature. I am going to supply both files in GPG ASCII-armoured"
+" form\n"
+"below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130
+msgid ""
+"First, the file `mtn-committers` containing jrandom's Monotone key. Save "
+"as\n"
+"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers "
+"--dearmor\n"
+"mtn-committers.asc`:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151
+msgid ""
+"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n"
+"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-"
+"committers.sig\n"
+"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n"
+"`mtn-committers` file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170
+#, python-format
+msgid ""
+"Some of the developers have included their Monotone keys in their signed license agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2
+msgid "Developer Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4
+#, python-format
+msgid "Read the new developers guide first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8
+msgid "Basic Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10
+msgid ""
+"Most of the following should be common sense for anybody who has worked "
+"on open source or in a commercial\n"
+"programming envrionment.\n"
+"The following applies mostly to the main development branch i2p.i2p.\n"
+"Guidelines for other branches, plugins, and external apps may be "
+"substantially different;\n"
+"check with the appropriate developer for guidance."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18
+msgid "Community"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20
+msgid ""
+"Please don't just \"write code\". If you can, participate in other "
+"development activities, including:\n"
+"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
+"testing;\n"
+"bug reporting and responses; documentation; code reviews; etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25
+msgid ""
+"Active devs should be available periodically on IRC #i2p-dev.\n"
+"Be aware of the current release cycle.\n"
+"Adhere to release milestones such as feature freeze, tag freeze, and\n"
+"the checkin deadline for a release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35
+msgid ""
+"Have a basic understanding of distributed source control systems, even if"
+" you haven't\n"
+"used monotone before. Ask for help if you need it.\n"
+"Once pushed, checkins are forever, there is no undo. Please be careful.\n"
+"If you have not used monotone before, start with baby steps.\n"
+"Check in some small changes and see how it goes."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42
+msgid ""
+"Test your changes before checking them in.\n"
+"If you prefer the checkin-before-test development model,\n"
+"use your own development branch (e.g. i2p.i2p.yourname.test)\n"
+"and propagate back to i2p.i2p once it is working well.\n"
+"Do not break the build. Do not cause regressions.\n"
+"In case you do (it happens), please do not vanish for a long period after"
+"\n"
+"you push your change."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51
+msgid ""
+"If your change is non-trivial, or you want people to test it and need "
+"good test reports\n"
+"to know whether your change was tested or not, add a checkin comment to "
+"history.txt\n"
+"and increment the build revision in RouterVersion.java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56
+msgid ""
+"Ensure that you have the latest monotonerc file in _MTN.\n"
+"Do not check in on top of untrusted revisions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60
+msgid ""
+"Ensure that you pull the latest revision before you check in.\n"
+"If you inadvertently diverge, merge and push as soon as possible.\n"
+"Don't routinely make others merge for you.\n"
+"Yes, we know that monotone says you should push and then merge,\n"
+"but in our experience, in-workspace merge works just as well as in-"
+"database merge,\n"
+"without creating a merge revision."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
+msgid ""
+"Do not check in major changes into the main i2p.i2p branch late in the "
+"release cycle.\n"
+"If a project will take you more than a couple days, create your own "
+"branch in monotone\n"
+"and do the development there so you do not block releases."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75
+msgid "Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77
+msgid ""
+"Coding style throughout most of the code is 4-spaces for indentation. Do "
+"not use tabs.\n"
+"Do not reformat code. If your IDE or editor wants to reformat everything,"
+" get control of it.\n"
+"Yes, we know 4 spaces is a pain, but perhaps you can configure your "
+"editor appropriately.\n"
+"In some places, the coding style is different.\n"
+"Use common sense. Emulate the style in the file you are modifying."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84
+msgid ""
+"New classes and methods require at least brief javadocs. Add @since "
+"release-number."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87
+msgid ""
+"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our "
+"official API.\n"
+"There are several out-of-tree plugins and other applications that rely on"
+" this API.\n"
+"Be careful not to make any changes that break compatibility.\n"
+"Don't add methods to the API unless they are of general utility.\n"
+"Javadocs for API methods should be clear and complete.\n"
+"If you add or change the API, also update the documentation on the "
+"website (i2p.www branch)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95
+msgid ""
+"Tag strings for translation where appropriate.\n"
+"Don't change existing tagged strings unless really necessary, as it will "
+"break existing translations.\n"
+"Do not add or change tagged strings after the \"tag freeze\" in the "
+"release cycle so that\n"
+"translators have a chance to update before the release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101
+msgid ""
+"Use generics and concurrent classes where possible. I2P is a highly "
+"multi-threaded application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104
+msgid ""
+"We require Java 6 to build but only Java 5 to run I2P.\n"
+"Do not use Java 6 classes or methods without handling the class not found"
+" exceptions\n"
+"and providing alternate Java 5 code. See classes in net.i2p.util for "
+"examples."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109
+msgid ""
+"Explicitly convert between primitive types and classes;\n"
+"don't rely on autoboxing/unboxing."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117
+msgid ""
+"Only check in code that you wrote yourself.\n"
+"Before checking in any code or library jars from other sources,\n"
+"justify why it is necessary,\n"
+"verify the license is compatible,\n"
+"and obtain approval from the lead developer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124
+msgid ""
+"For any images checked in from external sources,\n"
+"it is your responsibility to first verify the license is compatible.\n"
+"Include the license and source information in the checkin comment."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131
+msgid "Bugs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
+#, python-format
+msgid ""
+"Managing Trac tickets is everybody's job, please help.\n"
+"Monitor %(trac)s for tickets you have been assigned or can help with.\n"
+"Assign, categorize, comment on, fix, or close tickets if you can."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138
+msgid ""
+"Close a ticket when you think you've fixed it.\n"
+"We don't have a test department to verify and close tickets.\n"
+"If you arent sure you fixed it, close it and add a note saying\n"
+"\"I think I fixed it, please test and reopen if it's still broken\".\n"
+"Add a comment with the dev build number or revision and set\n"
+"the milestone to the next release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:2
+msgid "Using an IDE with I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:4
+msgid ""
+"The main I2P development branch (i2p.i2p) has been set up to"
+" enable developers to easily set up two of the commonly-used IDEs for "
+"Java development: Eclipse and NetBeans."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:10
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain .project and .classpath Eclipse files, to enable the branch "
+"to be easily set up in Eclipse."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:16
+msgid ""
+"Check out the I2P branch into some directory (e.g. "
+"$HOME/dev/i2p.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:20
+msgid ""
+"Open Eclipse and create a new Workspace, based in the directory that the "
+"I2P branch was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:24
+msgid ""
+"Select \"File - Import...\" and then under \"General\" select \"Existing "
+"Projects into Workspace\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:28
+msgid ""
+"For \"Select root directory:\" choose the directory that the I2P branch "
+"was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:32
+msgid "If necessary, click \"Refresh\" to refresh the list of projects."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:36
+msgid "Select every project in the list, and click \"Finish\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:40
+msgid ""
+"Done! Your workspace should now contain all projects within the I2P "
+"branch, and their build dependencies should be correctly set up."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:48
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain NetBeans project files."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:2
+msgid "Monotone"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:4
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:9
+msgid "Operating a Monotone client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:11
+#: i2p2www/pages/site/get-involved/guides/monotone.html:63
+msgid "Generating Monotone keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:12
+msgid "Trust and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:13
+#: i2p2www/pages/site/get-involved/guides/monotone.html:196
+msgid "Obtaining and deploying developers' keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:14
+#: i2p2www/pages/site/get-involved/guides/monotone.html:227
+msgid "Setting up trust evaluation hooks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:15
+#: i2p2www/pages/site/get-involved/guides/monotone.html:268
+msgid ""
+"Pulling the i2p.i2p, i2p.www and "
+"i2p.syndie branches"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:16
+#: i2p2www/pages/site/get-involved/guides/monotone.html:308
+msgid "Verifying that trust evaluation works"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:17
+#: i2p2www/pages/site/get-involved/guides/monotone.html:357
+msgid "Checking out a working copy of the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:18
+#: i2p2www/pages/site/get-involved/guides/monotone.html:384
+msgid "Updating your working copy to the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:22
+#: i2p2www/pages/site/get-involved/guides/monotone.html:414
+msgid "Operating a Monotone Server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:24
+msgid "Obtaining and deploying developers’ transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:25
+#: i2p2www/pages/site/get-involved/guides/monotone.html:424
+msgid "Granting push and pull access"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:26
+#: i2p2www/pages/site/get-involved/guides/monotone.html:469
+msgid "Running Monotone in server mode"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:27
+#: i2p2www/pages/site/get-involved/guides/monotone.html:494
+msgid "Differences under Debian GNU/Linux"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:34
+#, python-format
+msgid ""
+"This is a revised version of Complication's original\n"
+"  guide detailing the use of Monotone in I2P development.\n"
+"  For basic instructions see the quick-start "
+"guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:42
+#, python-format
+msgid ""
+"I2P has a distributed development model. The source code is replicated "
+"across\n"
+"  independently administered Monotone (\"MTN\") repositories.\n"
+"  Developers with commit rights are able to push their changes to the "
+"repository\n"
+"  (a license agreement needs to be "
+"signed\n"
+"  before commit rights are granted)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:52
+msgid ""
+"Some of Monotone's noteworthy qualities are: distributed\n"
+"  version control, cryptographic authentication, access control, its "
+"small size, having few\n"
+"  dependencies, storage of projects in a compressed SQLite database file,"
+" and\n"
+"  having the ability to resume interrupted synchronization attempts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:61
+msgid "Operating a Monotone Client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:66
+msgid ""
+"A transport key grants you the ability to push your changes to a Monotone"
+" repository server.\n"
+"  In order to commit code into Monotone (in essence signing your code), a"
+" commit key is also needed.\n"
+"  None of the public Monotone servers on I2P currently require a key in "
+"order to read (or pull) the source code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:74
+msgid ""
+"Without a transport key, one cannot:\n"
+"  
              \n"
+"    
            • pull code from a server which doesn't allow global read "
+"access
              • \n"
+"    
            • push code to any server
              • \n"
+"    
            • run a Monotone server
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:85
+msgid ""
+"Without a commit key, one cannot:\n"
+"  
              \n"
+"    
            • commit any code
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:94
+msgid ""
+"If you only intend to retrieve code from MTN, feel free to skip to the\n"
+"  next section. "
+"If you want\n"
+"  to generate keys, read the following."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:102
+msgid ""
+"By convention keys are named like an e-mail addresses, but a "
+"corresponding e-mail\n"
+"  address does not need to exist. For example, your keys might be named:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:113
+msgid ""
+"Monotone stores keys under $HOME/.monotone/keys in "
+"text files which\n"
+"  are named identically to the keys. For example:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:123
+msgid ""
+"To generate transport and commit keys, enter the following commands at a "
+"prompt:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:133
+msgid ""
+"Monotone will prompt you for a password to protect your keys. You are "
+"very strongly encouraged to set a password\n"
+"  for the commit key. Many users will leave an empty password for the "
+"transport key, especially those running a\n"
+"  Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:141
+msgid "Trust, and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:145
+msgid ""
+"Monotone's security model helps to ensure that nobody can easily "
+"impersonate a developer without\n"
+"  it being noticed. Since developers can make mistakes and become "
+"compromised,only manual review can\n"
+"  ensure quality of code. Monotone's trust model will ensure that you "
+"read the right diffs. It does\n"
+"  not replace reading diffs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:155
+msgid ""
+"A Monotone repository is a single file (a compressed SQLite database) "
+"which contains all of the project's source code and history."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:161
+msgid ""
+"After importing the "
+"developers' keys into Monotone and\n"
+"  setting up trust "
+"evaluation hooks,\n"
+"  Monotone will prevent untrusted code from being checked out into your "
+"workspace.\n"
+"  There are commands available to clean untrusted code from your "
+"workspace but in practice they've not been\n"
+"  needed due to the push access policies in place."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:171
+msgid ""
+"A repository can hold many branches. For example, our repository holds "
+"the\n"
+"  following main branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:176
+msgid "The I2P router and associated programs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:177
+msgid "The I2P project website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:178
+msgid "Syndie, a distributed forums tool"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:183
+msgid ""
+"By convention, the I2P Monotone repository is named i2p.mtn."
+" Before pulling\n"
+"  source code from servers, a database for your repository will need to "
+"be initialized.\n"
+"  To initialize your local repository, change into the directory that you"
+" want the\n"
+"  i2p.mtn file and branch directories to be stored and issue"
+" the following\n"
+"  command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:199
+msgid ""
+"Keys which developers use to commit code are essential for trust "
+"evaluation in\n"
+"  Monotone. The other developers' transport keys are only required for "
+"Monotone server operators.\n"
+"  "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:206
+#, python-format
+msgid ""
+"Developers' commit keys are provided GPG-signed on another page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:212
+#, python-format
+msgid ""
+"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
+"  file. Create this file (e.g. keys.txt) in the same "
+"directory where i2p.mtn is located. Import the keys with the"
+" command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:222
+msgid ""
+"Note: Never add keys to "
+"$HOME/.monotone/keys manually."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:230
+msgid ""
+"The default Monotone trust policy is way too lax for our requirements: "
+"every committer is trusted by default.\n"
+"  That is not acceptable for I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:237
+msgid ""
+"Change into the directory $HOME/.monotone and open "
+"the file\n"
+"  monotonerc with a text editor. Copy and paste the "
+"following two functions into this file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:246
+msgid ""
+"The first function determines an intersection between two sets, in our "
+"case a\n"
+"  revision's signers and trusted signers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:253
+msgid ""
+"The second function determines trust in a given revision, by calling the "
+"first\n"
+"  function with \"signers\" and \"trusted\" as arguments. If the "
+"intersection is\n"
+"  null, the revision is not trusted. If the intersection is not empty, "
+"the\n"
+"  revision is trusted. Otherwise, the revision is not trusted."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:262
+msgid ""
+"More information about Trust Evauluation Hooks can be found in the official Monotone "
+"documentation."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:271
+msgid ""
+"Enter the directory where you initialized i2p.mtn. Depending "
+"on whether you\n"
+"  want only I2P sources, or also sources for the I2P website and Syndie, "
+"you can\n"
+"  perform the pull operation in different ways."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:279
+msgid "If you only want I2P sources:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:288
+msgid "If you want all branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:294
+msgid ""
+"If the transfer aborts before completing sucessfully, simply repeating "
+"the pull command will resume the transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:300
+msgid ""
+"Pulling in the above examples is done anonymously by specifying an empty "
+"transport key.\n"
+"  If everyone pulls anonymously it will be harder for an attacker who "
+"gains control of the server\n"
+"  to selectively provide some people with tampered data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:311
+msgid "To verify that trust evaluation works:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:315
+msgid "Make a backup of your monotonerc file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:316
+msgid ""
+"Modify monotonerc by setting the trusted_signers "
+"variable in the following way:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:322
+msgid ""
+"With monotonerc configured as above, Monotone will no"
+" longer trust any committers. Confirm this by changing into the\n"
+"directory where i2p.mtn was created and attempt a checkout "
+"of the I2P branch:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:332
+msgid ""
+"A directory named i2p.i2p should not appear. You "
+"should encounter many\n"
+"  error messages like:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:349
+msgid ""
+"If you are satisfied with results, restore the backup of\n"
+"  monotonerc that was created above. If you didn't create a "
+"backup\n"
+"  as advised, re-read Setting up trust evaluation hooks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:360
+msgid ""
+"If you already have a branch checked out, skip to the next\n"
+"  section."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:367
+msgid ""
+"Change into the directory where i2p.mtn is located. Over "
+"there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:376
+msgid ""
+"The checkout should complete without error messages and a directory named"
+"\n"
+"  i2p.i2p should appear in the current directory. "
+"Congratulations! You have\n"
+"  successfully checked out the latest I2P sources, ready to be compiled."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:387
+msgid ""
+"If you haven't done this already, pull fresh code from the server to your"
+" local\n"
+"  Monotone repository. To accomplish this, change into the directory "
+"where\n"
+"  i2p.mtn is located and issue:\n"
+"  
              \n"
+"    
            • $ mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
+"i2p.i2p
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:398
+msgid "Now change into your i2p.i2p directory, and over there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:407
+msgid ""
+"As long as there were no errors…Congratulations! You have "
+"successfully updated to the latest I2P sources. They\n"
+"  should be ready to compile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:416
+msgid "Obtaining and deploying developers' transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:419
+msgid ""
+"As a server operator you may want to grant push access to certain "
+"developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:427
+msgid "By default the Monotone server denies all access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:433
+msgid "To grant pull access to all clients, set the following in"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:445
+msgid ""
+"No one will not be able to push code to your server without permission "
+"being explicitly granted. To grant push access:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:451
+msgid ""
+"Add the name of the user's transport key to\n"
+"$HOME/.monotone/write-permissions, such as\n"
+"
            \n"
+"    zzz-transport@mail.i2p\n"
+"    complication-transport@mail.i2p\n"
+"
            \n"
+"with one key per line."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:462
+msgid ""
+"Import the transport key(s) into your database. The procedure for "
+"importing transport keys is the same as for\n"
+"importing commit keys, which is described in the section Obtaining and deploying "
+"developers' keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:472
+msgid ""
+"A separate database should be used for your Monotone server because "
+"monotone will lock the database while it is served to others.\n"
+"  Make a copy of your development database, then start the server with:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:479
+msgid ""
+"If your key is protected with a passphrase, Monotone may request the "
+"passphrase\n"
+"  when the first client connects. You can work around this by connecting "
+"making the first client connection to your server\n"
+"  (or by clearing the password for your transport key)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:487
+msgid ""
+"For your server to be accessible for others over I2P, you will need to "
+"create a\n"
+"  server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" "
+"profile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:497
+msgid ""
+"Debian (amongst other distributions) has integrated Monotone into their\n"
+"  framework of daemons/services. Although Monotone servers can still be "
+"run\n"
+"  \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may"
+" be more straightforward."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:505
+msgid ""
+"Permissions are granted by editing the files\n"
+"  /etc/monotone/read-permissions and\n"
+"  /etc/monotone/write-permissions. You'll also need to edit\n"
+"  /etc/default/monotone to enable monotone to start at boot "
+"or to\n"
+"  customize the host, port, or database location."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
+msgid "New Developer's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
+msgid ""
+"\n"
+"So you want to start work on I2P? Great!\n"
+"Here's a quick guide to getting started\n"
+"on contributing to the website or the software, doing development or "
+"creating translations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
+#, python-format
+msgid ""
+"\n"
+"Not quite ready for coding?\n"
+"Try getting involved first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
+msgid "Basic study"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
+msgid "Getting the I2P code"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
+msgid "Building I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
+msgid "Development ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
+msgid "Making the results available"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
+msgid "Get to know us!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
+msgid "Translations"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
+msgid "Tools"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
+msgid ""
+"Basic development on the I2P router or the embedded applications uses "
+"Java as the main development language.\n"
+"If you don't have experience with Java, you can always have a look at Thinking in Java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
+#, python-format
+msgid ""
+"Study the how intro,\n"
+"the other \"how\" documents,\n"
+"the tech intro,\n"
+"and associated documents.\n"
+"These will give you a good overview of how I2P is structured and what "
+"different things it does."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
+msgid ""
+"For development on the i2p router or the embedded applications,\n"
+"get the monotone source repository installed - short instructions:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
+msgid ""
+"Install monotone.\n"
+"Monotone is a version control system.\n"
+"We use it because it allows us to keep track of who does what changes to "
+"the source code (and for a lot of complicated things, but 'keeping track "
+"of changes' is the basic idea)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
+msgid ""
+"Skim over the monotone tutorial,"
+" to make sure you understand the concepts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
+msgid ""
+"If you want to remain anonymous, you need to do an additional step, to "
+"set up a connection to a monotone server over I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
+#, python-format
+msgid ""
+"Enable the i2ptunnel client tunnel on port "
+"8998 pointing to mtn.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
+msgid ""
+"Pick a directory where you want to put all your I2P files, and create a "
+"monotone database:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
+msgid ""
+"Define the trust list by creating ~/.monotone/monotonerc (or"
+" _MTN/monotonerc in the i2p.i2p workspace) with the "
+"following contents:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
+#, python-format
+msgid ""
+"Copy and paste the developer's commit keys "
+"into a new file (e.g. keys.txt) in the same directory\n"
+"  that i2p.mtn is in. Import the keys into your database "
+"with 
                  mtn -d i2p.mtn read < keys.txt
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:76
+msgid ""
+"Pull the I2P sources to your machine. This may take a long time, "
+"especially if you are doing this over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:78
+msgid "Anonymously:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:81
+msgid "Non-anonymously:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:83
+msgid ""
+"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn"
+".i2p-projekt.de."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:90
+msgid ""
+"All the sources are now present on your machine, in the database file. To"
+" make them available in a directory, you need to check them out:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:92
+msgid ""
+"The above command creates a directory i2p.i2p, which contains all of the "
+"I2P sources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:96
+msgid "Remarks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:97
+msgid ""
+"\n"
+"To download the website files instead of the I2P source files, use "
+"'i2p.www' instead of 'i2p.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:100
+msgid ""
+"The initial pull may take several hours using the tunnel.\n"
+"If it fails after a partial pull, simply rerun it, it will start where it"
+" left off.\n"
+"If you are in a hurry, use the non-anonymous access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:105
+#, python-format
+msgid ""
+"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
+#, python-format
+msgid ""
+"A long explanation about using monotone is available on the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
+#, python-format
+msgid ""
+"To compile the code, you need the Sun Java Development Kit 6 or higher, "
+"or equivalent JDK\n"
+"(Sun JDK 6 strongly recommended) and\n"
+"Apache ant\n"
+"version 1.7.0 or higher.\n"
+"If you go are working on the main I2P code, you can go into the i2p.i2p "
+"directory and run 'ant' to see the build options."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
+msgid ""
+"To build or work on console translations, you need\n"
+"the xgettext, msgfmt, and msgmerge tools from the\n"
+"GNU gettext package."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
+#, python-format
+msgid ""
+"For development on new applications,\n"
+"see the application development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
+#, python-format
+msgid ""
+"See zzz's TODO lists,\n"
+"this website's TODO list or\n"
+"Trac\n"
+"for ideas."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
+#, python-format
+msgid ""
+"See the bottom of the licenses page "
+"for\n"
+"commit privilege requirements. You need these to put code into i2p.i2p "
+"(not required for the website!)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
+msgid "Short version of how to generate and use keys if you plan to commit:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
+msgid "use an empty passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
+msgid "enter a passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
+#, python-format
+msgid ""
+"send this to a mtn repo operator to get "
+"push privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
+#, python-format
+msgid ""
+"send this to a release manager to get "
+"commit privileges - not required for website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
+msgid "check in with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
+msgid "push with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
+#, python-format
+msgid "Long version: see the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
+#, python-format
+msgid ""
+"The developers hang around on IRC. They can be reached on the Freenode "
+"network, OFTC, and on the I2P internal networks. The usual place to look "
+"is #i2p-dev. Join the channel and say hi!\n"
+"We also have additional guidelines for regular"
+" developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
+#, python-format
+msgid ""
+"Website and router console translators: See the New Translator's Guide\n"
+"for next steps."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
+msgid ""
+"I2P is open source software that is mostly developed using open sourced\n"
+"toolkits. The I2P project recently acquired a license for the YourKit "
+"Java\n"
+"Profiler. Open source projects are eligible to receive a free license "
+"provided\n"
+"that YourKit is referenced on the project web site. Please get in touch "
+"if you\n"
+"are interested in profiling the I2P codebase."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
+#, python-format
+msgid ""
+"YourKit is kindly supporting open source projects with its full-featured "
+"Java Profiler.\n"
+"YourKit, LLC is the creator of innovative and intelligent tools for "
+"profiling\n"
+"Java and .NET applications. Take a look at YourKit's leading software "
+"products:\n"
+"YourKit Java Profiler and\n"
+"YourKit .NET Profiler."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
+msgid "New Translator's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
+msgid "Here's a very quick guide to getting started."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
+msgid "How to Translate the Website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
+#, python-format
+msgid ""
+"Translation of the website is done with .po files. The easiest way by far"
+" to\n"
+"translate the website is to sign up for an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
+msgid "Preparation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
+#, python-format
+msgid ""
+"Come to #i2p-dev on irc and talk to people.\n"
+"Claim the language -\n"
+"To make sure other coworkers don't bump onto the files you are working "
+"on,\n"
+"please update the translation status on this wiki "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"Including the installation of monotone,\n"
+"checking out i2p.www branch, and generate your own monotone keys.\n"
+"It is not required that you sign a dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
+msgid ""
+"Run \"./extract-messages.sh\" to generate a "
+"messages.pot in the base directory.\n"
+"Edit the header of this file, then run \"./init-new-po.sh "
+"locale\" to generate the file\n"
+"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
+"\"mtn add\" this file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
+msgid ""
+"Edit i2p2www/pages/global/lang.html and add a line for your "
+"language (copy an existing line)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
+msgid ""
+"Add a flag image file to i2p2www/static/images/flags/ for "
+"the menu (copy from the router)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
+msgid ""
+"Edit files:\n"
+"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
+msgid ""
+"Check in:\n"
+"\"mtn pull\", \"mtn update\". Then check in by "
+"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
+"This collects the diff info of your changed file into your local repo. "
+"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
+"i2p.i2p\".\n"
+"This synchronizes your local repo with the repo on the target machine."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
+msgid "Repeat. Check in often. Don't wait until it is perfect."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
+msgid "How to Translate the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
+#, python-format
+msgid ""
+"The easiest way by far to translate the router console is to sign up for "
+"an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"including the installation of monotone and the gettext tools,\n"
+"checking out i2p.i2p branch, and generate your own monotone keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
+msgid "Generate your own gpg key and sign the dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
+msgid ""
+"Before starting a console translation, better help translate some i2p "
+"webpages first.\n"
+"At least an i2p homepage in your language would be great."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
+msgid ""
+"What to translate:\n"
+"There are about 15 files in the i2p.i2p branch that needs translation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
+msgid ""
+"Where xx is your language code like fr/de/ch/zh/...\n"
+"There may be or may not be files with your lang code. If not, you can "
+"create your own. by copying and renaming other language files you know "
+"with your own lang code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet, copy another language "
+"file to a new file foo_xx.bar for your language.\n"
+"Then \"mtn add\" the file.\n"
+"After creating a .po file, edit the headers. Then run \"ant "
+"distclean poupdate\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
+msgid ""
+"Start to work:\n"
+"Edit the HTML files with any text editor.\n"
+"Be sure not to use an editor in HTML mode that reformats everything.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
+msgid ""
+"As you can see, it's not that difficult.\n"
+"If you have questions about the meaning of the terms in the console, ask "
+"in #i2p-dev on IRC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
+msgid "FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
+msgid ""
+"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
+"and html, etc.? Why can't I just do a translation and email it to you?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
+msgid "A: Several reasons:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
+#, python-format
+msgid ""
+"You might be interested in translating via Transifex. Request to join a "
+"translation team here."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
+msgid ""
+"We don't have anybody who has time to accept manual contributions and "
+"submit them to our source control system on your behalf. Even if we did, "
+"it doesn't scale."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
+msgid ""
+"Maybe you are thinking translation is a one-step process. It isn't. You "
+"can't do it all at once. You will make mistakes. You need to test it and "
+"tweak it to make it look right before you submit it. Developers "
+"will update or add to the English text, thus requiring a translation "
+"update."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
+msgid ""
+"Having translators use a source control system directly provides "
+"authentication and accountablility - we know who is doing what, and we "
+"can track changes, and revert them if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
+msgid ""
+".po files are not difficult. If you don't want to work directly with "
+"them, we recommend 'poedit'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
+msgid ""
+"HTML files are not difficult. Just ignore the html stuff and translate "
+"the text."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
+msgid ""
+"Installing and using monotone is not that difficult. Several of the "
+"translators and other contributors to I2P are non-programmers, and they "
+"use monotone regularly. Monotone is simply a source control system, it is"
+" not about \"coding\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
+msgid ""
+"Our items to translate are not \"documents\". They are html files and po "
+"files, with a specific format and character encoding (UTF-8) that must be"
+" maintained, and not corrupted by email programs or other methods of "
+"transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
+msgid ""
+"We looked at 'pootle' as a front-end for translators. It didn't work "
+"well, needed an administrator, and a pootle-based process would suffer "
+"from a number of the above flaws."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
+msgid ""
+"In summary:\n"
+"Yes, we know it is somewhat of a hurdle to get started. It's really the "
+"only possible way we can do it. Give it a try, it really isn't that hard."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
+msgid "More Information"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
+#, python-format
+msgid ""
+"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
+msgstr ""
+
diff --git a/i2p2www/translations/de/LC_MESSAGES/misc.po b/i2p2www/translations/de/LC_MESSAGES/misc.po
new file mode 100644
index 00000000..09a90130
--- /dev/null
+++ b/i2p2www/translations/de/LC_MESSAGES/misc.po
@@ -0,0 +1,1232 @@
+# German translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# amiga4000 , 2008
+# D.A. Loader, 2013
+# SteinQuadrat, 2013
+# zeroflag , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-08-30 23:32+0000\n"
+"PO-Revision-Date: 2013-07-04 16:33+0000\n"
+"Last-Translator: D.A. Loader\n"
+"Language-Team: German "
+"(http://www.transifex.com/projects/p/I2P/language/de/)\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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: i2p2www/pages/site/misc/jbigi.html:6
+msgid "Overview"
+msgstr ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: i2p2www/pages/site/misc/transition-guide.html:21
+msgid "Guide"
+msgstr ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:44
+msgid "Click \"Save\""
+msgstr ""
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:51
+msgid "Add the following line:"
+msgstr ""
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:55
+msgid "Click \"Apply\""
+msgstr ""
+
+#: 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/de/LC_MESSAGES/priority.po b/i2p2www/translations/de/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..d3e3b669
--- /dev/null
+++ b/i2p2www/translations/de/LC_MESSAGES/priority.po
@@ -0,0 +1,2752 @@
+# German translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# amiga4000 , 2008
+# D.A. Loader, 2013
+# SteinQuadrat, 2013
+# echeloni2p , 2013
+# Ashoka , 2013
+# nextloop , 2013
+# zeroflag , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-11-27 00:30+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: German "
+"(http://www.transifex.com/projects/p/I2P/language/de/)\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/blog/category.html:2
+msgid "Blog Category"
+msgstr ""
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr ""
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:92
+msgid "Blog"
+msgstr "Blog"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "I2P Blog als ATOM-Feed"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr "verfasst %(date)s von %(author)s"
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "mehr Blogartikel…"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr "geschrieben:"
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "Autor:"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "I2P Debian Pakete"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Option 1: Neuste Versionen von Ubuntu und dessen "
+"Derivate (Versuche dies, wenn du kein Debian benutzt)."
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Die PPA per Terminal hinzufügen und I2p installieren"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Öffne eine Konsole und gib ein:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"Mit diesem Befehl wird die PPA sowie der dazugehörige GPG-Schlüssel mit "
+"dem die Paketquelle signiert wurde zur Sourceliste hinzugefügt.\n"
+"Der GPG-Schlüssel ist notwendig, um sicher zu stellen, dass die "
+"heruntergeladenen Pakete echte sind und nicht nachträglich manipuliert "
+"wurden."
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr ""
+"Informiere deinen Paketmanager über die neue PPA, indem du folgendes "
+"eingibst: "
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+"Dieser Befehl fragt jede auf deinem System eingeschaltet Paketquelle nach"
+" der neuesten Softwareliste ab. Inklusive der I2P PPA, welche mit dem "
+"vorherigen Befehl hinzugefügt wurde. "
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "Sie/Du bist nun bereit I2P zu installieren!"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "Die PPA über Synaptic hinzufügen"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+"Öffne Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+"Sobald sich Synaptic öffnet, wähle Paketquellen von dem "
+"Einstellungen Menü."
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"Klicke den Andere Quellen tab und klicke Hinzufügen. "
+"Füge den Code ppa:i2p-maintainers/i2p in das APT-Linien-Feld"
+" ein und klicke Quelle hinzufügen. Klicke den "
+"Schliessen Button und dann Reload."
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+"In der \"Schnell Filter Box\", schreibst du i2p und drückst "
+"Enter. Wenn i2p in der Ergebnisliste wiedergegeben wird, "
+"rechtsklicke i2p und wähle markiere für "
+"Installation. Anschliessend wirst du wahrscheinlich markiere "
+"zusätzliche benötigte Änderungen? in einem Popup sehen. Ist dies der"
+" Fall, klicke markieren dann Anwenden."
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+"Nach dem der Installationsprozess abgeschlossen ist, kannst du zu dem "
+"nächsten Teil von starting I2P "
+"wechseln und es für dein System konfigurieren."
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the  key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+"Nach der Installation kannst du I2P "
+"starten und es passend einrichten."
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "Arbeit nach der Installation"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+"Unter Benutzung dieser I2P Pakete kann der I2P Router mit 3 verschiedenen"
+" Möglichkeiten gestartet werden:"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+""Bei Bedarf" nutzen Sie das I2Prouter Script. Führen Sie "
+"einfach "i2prouter\n"
+"start" in einer Kommandozeile aus. (Hinweis: Nutzen Sie "
+"niemals \n"
+"sudo oder als root Benutzer starten)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""Bei Bedarf" ohne den Java Service Wrapper\n"
+"(immer auf nicht-Linux/nicht-x86 Systemen) durch ausführen von\"i2prouter-nowrapper            \".\n"
+"(Hinweis: Nutzen Sie nicht\n"
+"sudo oder als root starten)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"als ein Service, der automatisch beim Systemstart startet, auch\n"
+"vor dem Einloggen. Der Service kann mit \"dkpg-reconfigure\n"
+"i2p\" als root oder mit sudo aufgerufen aktiviert werden. Dieses "
+"ist auch die empfohlene Art."
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"Bitte kontrollieren und passen Sie die Bandbreiteneinstellungen "
+"auf der \n"
+"Einstellungsseite an,⏎\n"
+"da die Standardeinstellungen von 96 KB/sec Download / 40 KB/sec Upload "
+"gering gesetzt sind."
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"Wenn Sie Eepsites mit Ihrem Browser betrachten möchten, finden Sie auf "
+"der Browser Proxy Setup Webseite eine "
+"einfache Anleitung."
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Download"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Download I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Abhängigkeit"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "saubere Installationen"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr "wähle alternativen Link"
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Lade die Datei herunter und führe sie aus."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "Kommandozeilen (Textbasierter) Installation"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Downloaden Sie die Datei und klicken Sie doppelt darauf (falls dieses "
+"funktioniert) oder\n"
+"geben Sie java -jar i2pinstall_%(i2pversion)s.jar in ein "
+"Terminalfenster um den Installer auszuführen.\n"
+"Auf einigen Systemen können Sie mit Rechtsklick die Funktion "Öffnen"
+" mit Java" auswählen."
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Downloaden Sie den graphischen Installer von oben und\n"
+"führen Sie java -jar i2pinstall_%(i2pversion)s.jar -console "
+"in einer Kommandozeile aus."
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Pakete sind für Debian und Ubuntu verfügbar."
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+"    The latest dev build is version %(devbuild)s, and is available from\n"
+"    str4d's eepsite."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+"      are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+"      the other."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "Quell Pakete"
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+"    or via Git from git.repo.i2p or Github.\n"
+"    
            \n"
+"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Diese Dateien wurden durch zzz signiert, dessen Schlüssel hier ist."
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"I2p kann auch von unseren Projektseiten heruntergeladen werden, diese "
+"sind Launchpad und Google Code."
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"Nach der Installation unter Windows einfach den \"Start I2P\" Button "
+"drücken, wodurch die Router "
+"Konsole mit weiteren Anleitungen erscheint."
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"Auf Unix-artigen Systemen kann I2P als Service gestartet werden \n"
+"mit dem \"i2prouter\" script aus dem von Ihnen gewählten I2P "
+"Installationsverzeichnis.\n"
+"Aus dem Verzeichnis heraus \"sh i2prouter status\" aufruden sollte Ihnen "
+"den Status des Routers mitteilen.\n"
+"Die Argumente \"start\",\"stop\" und \"restart\" kontrollieren den "
+"Service. Die Router "
+"Konsole kann am gewohnten Ort erreicht werden.\n"
+"Für User von OpenSolaris und anderen Systemen, auf denen der Wrapper "
+"(i2psvc) nicht unterstützt wird, starten Sie\n"
+"den Router stattdessen mit \"sh runplain.sh\"."
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"Passen Sie bitte  bei der ersten Installation ihre Firewall/NAT "
+"Regeln, soweit möglich, an. Beachten Sie\n"
+"dabei die I2P Ports für die Internetverbindung, die neben anderen Ports "
+"hier beschrieben sind.\n"
+"Nachdem Sie erfolgreich Ihren Port für eingehende TCP Verbindungen "
+"geöffnet haben, aktivieren Sie bitte eingehenden\n"
+"TCP Verkehr auf der Konfigurationsseite."
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"Bitte kontrollieren und passen Sie die Bandbreiteneinstellungen "
+"auf der \n"
+"Einstellungsseite an,⏎\n"
+"da die Standardeinstellungen von 96 KB/sec Download / 40 KB/sec Upload "
+"gering gesetzt sind."
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "Updates von früheren Versionen:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr "Automatische und manuelle Updates sind für die Veröffentlichung verfügbar."
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "automatische Updates"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+"Wenn du I2P 0.7.5 oder eine spätere Version verwendest, sollte dein I2P-"
+"Router die neue Version selbständig finden. Um zur neuen Version "
+"aufzusteigen, klicke einfach den 'Download Update' Button in der Router-"
+"Konsole sobald dieser erscheint."
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"Bedingt durch einen Bug in Version 0.7.6 können Benutzer, die nicht "
+"manuell geupdated haben, einen \"heruntergeladene\n"
+"Version ist nicht neue als derzeitige Version\" Fehler bekommen. Diese "
+"Nutzer sollten die manuelle Update Methode nutzen."
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Falls Sie Version 0.7.4 oder eine ältere Version nutzen, schauen Sie "
+"bitte\n"
+"die Hinweise zur Version 0.7.5 durch⏎\n"
+"für wichtige Informationen zum Einrichten des automatischen Updates für "
+"ihren Router."
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Falls Sie Version 00.6.1.30 oder eine ältere Version nutzen, schauen Sie "
+"bitte\n"
+"die Anweisungen durch⏎\n"
+"für wichtige Informationen zum Einrichten des automatischen Updates für "
+"ihren Router."
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+"    router console "
+"allowing\n"
+"    you to download and install the new release by just clicking on that\n"
+"    link."
+msgstr ""
+"Falls Sie ihren Router nach den Hinweisen auf dieser Seite geändert haben, sollten Sie "
+"einen Link\n"
+"auf Ihrer Router Konsole "
+"sehen, der Ihnen mit einem einfachem Klick erlaubt, die aktuelle Version "
+"zu\n"
+"downloaden und zu installieren."
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr "Alternativ können Sie die unten beschriebene manuelle Methode nutzen."
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "manuelle Updates"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and rename as i2pupdate.zip.\n"
+"    (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+"    resulting i2pupdate.zip to your I2P installation directory).  You do"
+" \n"
+"    NOT need to unzip that file."
+msgstr ""
+"Downloaden Sie die Datei in ihr I2P Installationsverzeichnis und benennen"
+" Sie es in i2pupdate.zip.\n"
+"(Alternativ können Sie den Quelltext von oben downloaden und \"ant "
+"updater\" ausführen, das entstandene\n"
+"i2pupdate.zip kopieren Sie in ihr I2P Installationsverzeichnis).\n"
+"Das Archive müssen Sie NICHT entpacken."
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr "Klicke \"Restart\""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "Holen Sie sich eine Tasse Kaffee und kommen Sie in 11 Minuten wieder"
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Diese Datei wurde von zzz signiert, dessen "
+"Schlüssel hier zu finden ist."
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "Frühere Versionen"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"Frühere Veröffentlichungen sind verfügbar auf Google "
+"Code⏎\n"
+"und Launchpad⏎\n"
+"und im I2P Netzwerk auf %(echelon)s."
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "Mirror Auswahl"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "Datei:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "Irgendein Downloadmirror"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+"Um die Belohnung zu erhalten, darf der Autor nicht von einer anderen "
+"Organisation oder Gruppe\n"
+"für diese Arbeit bezahlt werden (z.B. sind GSoC Studenten hier nicht "
+"erlaubt)"
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations.  Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"Belohnungen können durch weitere Spenden anwachsen.\n"
+"Denken Sie, dieses ist wichtig?  Spenden Sie, "
+"⏎\n"
+"und geben Sie dabei die %(donatename)s Belohnung an!"
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "Nicht gefunden"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+"Yep... Die Seite, die Sie gesucht haben, nennt sich anders, existiert "
+"nicht oder wurde entfernt."
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "Server Fehler"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "500 Server Fehler"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "Upsi! Beim Server ist irgendwas explodiert."
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "Mirrors"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "Sicher"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "Sonstiges"
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Links"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "Impressum"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "T-Shirts!"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "Europa"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "USA"
+
+#: i2p2www/pages/global/footer.html:31 i2p2www/pages/global/nav.html:133
+msgid "Donate"
+msgstr "Spenden"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "I2P Logo"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "Das Invisible Internet Projekt"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+"Diese Seite wurde zuletzt %(lastupdated)s aktualisiert und ist korrekt "
+"für Router Version %(accuratefor)s."
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "Diese Seite wurde zuletzt %(lastupdated)s aktualisiert."
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "Diese Seite ist korrekt für Router Version %(accuratefor)s."
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr "vorheriger"
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr "nächsten"
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "Über"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Einführung zu I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "Vergleiche"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "Überblick der Vergleiche"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Andere anonyme Netzwerke"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Dokumentation"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Inhaltsverzeichnes der Dokumentation"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Wie funktioniert es ?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "Gutverständliche Einführung"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "Technische Einführung"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "Gefahrenanalyse"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Garlic-Routing"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "Netzwerk Datenbank"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "Tunnelung"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "Teilnehmerauswahl"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Kryptographie"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Spezifikationen"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "Blockfile"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "Gemeinsame Strukturen"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "Konfigurations Dateien"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:56
+msgid "Datagrams"
+msgstr "Datagramme"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr "GeoIP Daten"
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:88
+msgid "Plugins"
+msgstr "Plugins"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:55
+msgid "Streaming library"
+msgstr "Streaming-Bibliothek"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "Tunnelerstellung"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "Tunnelnachrichten"
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "Softwareaktualisierungen"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:60 i2p2www/pages/global/nav.html:113
+msgid "Applications"
+msgstr "Anwendungen"
+
+#: i2p2www/pages/global/nav.html:62
+msgid "Supported applications"
+msgstr "unterstüzte Anwendungen"
+
+#: i2p2www/pages/global/nav.html:63
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Protocols"
+msgstr "Protokolle"
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Protocol stack"
+msgstr "Protokoll Stack"
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Transports"
+msgstr "Transports"
+
+#: i2p2www/pages/global/nav.html:75
+msgid "Transport layer overview"
+msgstr "Übersicht über die Übetragungsschichten"
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Tunnels"
+msgstr "Tunnels"
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Tunnel implementation"
+msgstr "Tunnelimplementierung"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Unidirectional tunnels"
+msgstr "Einbahn-Tunnels"
+
+#: i2p2www/pages/global/nav.html:84
+msgid "Old implementation"
+msgstr "Alte Implementierung"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Naming and addressbook"
+msgstr "Namensauflösung und Addressbuch"
+
+#: i2p2www/pages/global/nav.html:91
+msgid "Team"
+msgstr "Team"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Hall of Fame"
+msgstr "Ruhmeshalle"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Academic papers and peer review"
+msgstr "Akademische Artikel und Peer Review"
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Presentations, tutorials and articles"
+msgstr "Präsentationen, Tutorials und Artikel"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Contact us"
+msgstr "Kontakt"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Help"
+msgstr "Hilfe"
+
+#: i2p2www/pages/global/nav.html:101
+msgid "FAQ"
+msgstr "Häufige Fragen"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "How to browse I2P"
+msgstr "Wie Sie das I2P Netz durchstöbern"
+
+#: i2p2www/pages/global/nav.html:103
+msgid "Glossary"
+msgstr "Glossar"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Performance"
+msgstr "Performanz"
+
+#: i2p2www/pages/global/nav.html:105 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Foren"
+
+#: i2p2www/pages/global/nav.html:108
+msgid "Volunteer"
+msgstr "Mithelfen"
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Get involved!"
+msgstr "Mach mit!"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Develop"
+msgstr "Entwickeln"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Licenses"
+msgstr "Lizenzen"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Release signing keys"
+msgstr "Unterschriftschlüssel für die Releases"
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Signed keys"
+msgstr "Unterschriebene Schlüssel"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Developers keys"
+msgstr "Die Schlüssel der Entwickler"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Bug tracker"
+msgstr "Bug-Tracker"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Academic research"
+msgstr "Forschung"
+
+#: i2p2www/pages/global/nav.html:122
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:123
+msgid "Guides"
+msgstr "Anleitungen"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "New developers"
+msgstr "Neue Entwickler"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Using an IDE with I2P"
+msgstr "Eine IDE für I2P verwenden"
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Developer guidelines and coding style"
+msgstr "Entwicklungsrichtlinien und Code-Richtlinien"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "New translators"
+msgstr "Neue Übersetzer"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Bounties"
+msgstr "Bounties"
+
+#: i2p2www/pages/global/nav.html:134 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Treffen"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Roadmap"
+msgstr "Entwicklungsplan"
+
+#: i2p2www/pages/global/nav.html:136
+msgid "Task list"
+msgstr "Aufgabenliste"
+
+#: i2p2www/pages/global/nav.html:139
+msgid "Language"
+msgstr "Sprache"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr "I2P Treffen ATOM Quelle"
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "Logdateien vergangener I2P Treffen"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"Wenn Sie etwas diskutieren möchten, finden Sie die Entwickler im IRC "
+"Kanal #i2p-dev.\n"
+"Status Aktualisierungen der Entwickler sind"
+" ebenfalls verfügbar."
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr ""
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "Nach Thema"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "Nach Datum"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "Nach Autor"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
            \n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
            \n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:94
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"Free Haven's anonymity bibliography."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Kontakt"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like OFTC,\n"
+"  EIN and Freenode.\n"
+"  All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Kanalliste:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "Generelle Diskussionen über I2P"
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "Offtopic"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "Entwickler Gespräche"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Hilfskanal"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"Die meisten Diskussionen über I2P Entwicklung geschieht im I2P Entwickler Forum. Dieses\n"
+"ist für gewöhnlich der beste Platz um Anfragen zu stellen, falls der IRC "
+"Kanal inaktiv ist."
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "Mailing Listen"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+"Es existieren I2P Mailinglisten, diese sind jedoch wenig genutzt bedingt "
+"durch die Präferenz der Entwickler zur Kommunikation über IRC oder dem "
+"Entwickler Forum. Dieses kann sich in Zukunft ändern."
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "Einschreiben"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+"Um sich bei einer Mailingliste einzuschreiben, gehen Sie zur "
+"Mailinglisten Informationsseite (unten verlinkt) und füllen Sie die "
+"Felder aus. I2P interne Email Adressen (foobar@mail.i2p) können auch "
+"genutzt werden."
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "Ausschreiben"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+"Um sich von einer Mailingliste abzumelden oder die Optionen zu ändern, "
+"gehen Sie zur Mailinglisten Informationsseite (unten verlinkt) und geben "
+"Sie ihre angemeldete EMail Adresse an."
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Listen"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Archive"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+"Generelle I2P Diskussionen - alles was nicht in eine andere Liste passt, "
+"passt hier"
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+"Sie mögen keine Mailinglisten? Dann ist diese Option für Sie. Alle "
+"Mailinglisten sind auch mit NNTP verfügbar."
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr "Mapping Gruppe-Liste"
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Server:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Häufig gestellte Fragen (FAQ)"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Index"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "Generelles"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "Auf welchen Systemen wird I2P laufen?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+"Was ist eine \"Eepsite\" und wie konfigurieren Sie Ihren Browser um diese"
+" zu nutzen?"
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "Mein Router hat sehr wenige aktive Peers, ist das OK?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr "Was bedeuten die Active x/y Nummern in der Router Konsole?"
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+"Meine active Peers / known Peers / Participating Tunnel / Verbindungen / "
+"Bandbeite ändern sich stark! Ist irgendwas kaputt?"
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "Ist es sicher einen Outproxie zu benutzen?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr "Sind die meisten Eepsites im I2P-Netzwerk nicht erreichbar?"
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Welche Ports werden von I2P genutzt?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "Warum lauscht I2P auf dem 32000 für Verbindungen?"
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "Ich glaube, ich habe eine Fehler gefunden. Wo kann ich diesen melden?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr "Was passierte mit *.i2p.net? Was passierte mit jrandom? Ist I2P tot?"
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "Ich habe eine Frage!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr "Einrichtung"
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+"Ihr Router ist für einige Minuten aktiv und hat keine oder wenige "
+"Verbindungen"
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "Warum ist I2P so langsam?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+"Sie vermissen viele Adressen in Ihrem Adressbuch. Was sind gute "
+"Subscription Links?"
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "Wie kann ich meine eigene Eepsite einrichten?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "Bittorrent / I2PSnark / Azureus I2P Plugin Fragen?"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "Wie verbinde ich mich mit dem IRC innerhalb von I2P?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "Ich kann keine normalen Internetseiten über I2P erreichen."
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "Ich kann keine https:// oder ftp:// Seiten ü I2P besuchen."
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr "Ist es möglich, I2P als SOCKS Proxy zu nutzen?"
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Wie kann ich meinen Browser entsprechend einstellen?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+"Wie können Sie die Webkonsole von anderen Systemen erreichen oder mit "
+"einem Passwort absichern?"
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr "Wie können Sie Applikationen von anderen Systemen aus nutzen?"
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr "Wie reseede ich manuell?"
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "Mein Router nutzt viel zu viel CPU?!?"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "Missverständnis"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr ""
+"Wie erreichen Sie IRC, BitTorrent oder andere Services im normalen "
+"Internet?"
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+"Ist mein Router ein \"Exit Punkt\" ins normale Internet? Das will ich "
+"nicht!"
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+"Ihnen sind manche Inhalte äusserst zuwider. Wie können Sie verhindern, "
+"das Sie diese verteilen, speichern oder abfrufen?"
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Fehler und derren Lösungen"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+"Sie nutzen FreeBSD und wenn Sie I2P starten, bekommen Sie einen Fehler "
+"über libm.so.4!"
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+"Im wrapper.log sehen Sie einen Fehler Protokoll "
+"Familie nicht verfügbar beim Start von I2P"
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "Link"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "Diskutiere mit den Entwicklern per IRC in #i2p-dev"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+"Sschaue auf diese Seite für Jrandoms "
+"Abschiedsnachricht und weitere Informationen zur Migration von *.i2p.net "
+"zu dieser Webseite."
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+"Hmm. I2P ist ein anonymes Netzwerk, somit ist dieses Thema schwer zu "
+"lösen. I2P ist für jeden aufgebaut und nicht zum zensieren von "
+"ein paar/allen Daten. Der Beste Weg um deinen PC frei von "
+"(verschlüsseltem) Material, welches Du nicht magst, zu halten, ist "
+"I2P nicht zu nutzen. Die Redefreiheit für jeden (Freedom of Speech) "
+"hat gewisse Kosten, die wir akzeptieren müssen. Aber lass uns die "
+"Frage in 3 Teilen beantworten:"
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+"Nein, das ist normal. Alle Router passen sich dynamisch an die sich "
+"veränderne Netzwerkbedingunen und Anforderungen an."
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
            \n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "Fertig."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface.  However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"with 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "Was ist eine \"Eepseite\" ?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+"Eine Eepsite ist eine Webseite, welche anonym gehostet ist - du kannst "
+"diese betreten"
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+"    "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+"    "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+"    "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
            \n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
            \n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally.  You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance.  You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr "Warum lauscht I2P auf dem Port 32000 ?"
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the  \n"
+"wrapper documentation."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr "Stoppe deinen I2P Router"
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr "Starte deinen I2P Router"
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+"Bestens! Du findest uns im IRC auf irc.freenode.net im Kanal #i2p oder "
+"frage im Forum und wir werden das hier "
+"anfügen (mit der Antwort, hoffentlich)."
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "Deutsche Gesetze"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr "I2P Anonymes Netzwerk"
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr "Was macht I2P für dich?"
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr "Bekomme I2P %(version)s"
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "Was ist I2P ?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr "Lese more…"
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr "Was kannst du mit I2P machen?"
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr "I2P im Netz"
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr "Freunde von I2P"
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr "Mehr Projekte und Dokumentationen"
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "Presse"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr ""
+
diff --git a/i2p2www/translations/de/LC_MESSAGES/research.po b/i2p2www/translations/de/LC_MESSAGES/research.po
new file mode 100644
index 00000000..708879b6
--- /dev/null
+++ b/i2p2www/translations/de/LC_MESSAGES/research.po
@@ -0,0 +1,133 @@
+# German translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# amiga4000 , 2008
+# D.A. Loader, 2013
+# SteinQuadrat, 2013
+# zeroflag , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-07-04 16:33+0000\n"
+"Last-Translator: D.A. Loader\n"
+"Language-Team: German "
+"(http://www.transifex.com/projects/p/I2P/language/de/)\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/research/index.html:2
+msgid "Academic Research"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:4
+msgid ""
+"Academic research and analysis of I2P is an important part of ensuring "
+"that the software and network performs as expected and is safe for users "
+"in hostile environments."
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:8
+#, python-format
+msgid ""
+"\n"
+"There is a large research community investigating a wide range of aspects"
+" of\n"
+"anonymity. For a current and comprehensive list of relevant papers, see "
+"the\n"
+"Free Haven Anonymity Bibliography.\n"
+"I2P benefits from much of the research into Tor and onion routing, but "
+"there is\n"
+"little dedicated research interest into the theory behind I2P, and the "
+"choices\n"
+"and tradeoffs that the network makes. This presents a unique opportunity "
+"for\n"
+"original research.\n"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:18
+#, python-format
+msgid ""
+"A list of known published papers about I2P is available here."
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:22
+msgid "Testing Attacks on I2P"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:24
+msgid ""
+"I2P can be run as a separate test network by controlling the locations "
+"that a new router reseeds from so that it only finds other test routers."
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:28
+msgid ""
+"The standard mode of operation is to have one JVM per router instance; "
+"hence running multiple copies of I2P on a single machine is inadvisable, "
+"both due to the potential resource drain and the certain port conflicts. "
+"To better facilitate setting up small test networks, I2P has a "
+"multirouter mode which enables multiple distinct routers to be run in the"
+" same JVM."
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:32
+msgid ""
+"MultiRouter can be started from the i2p base directory by running the "
+"below command."
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:37
+msgid ""
+"Additionally, I2P can be started in a virtual network mode. This mode "
+"disables all transports, allowing the router to be tested in isolation "
+"without network traffic. To enable this mode, add "
+"i2p.vmCommSystem=true to the router.config before starting."
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:41
+msgid "Testing the Live I2P Network"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:43
+#, python-format
+msgid ""
+"If you are planning on conducting research on the live I2P network, "
+"please contact us before you commence your "
+"testing. While we do not discourage researchers from responsibly testing "
+"their ideas on the live network, if an attack becomes apparent and we "
+"don't have any line of communication then we will end up taking "
+"countermeasures which could interfere with the test."
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:2
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:4
+msgid "Network database"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:6
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:8
+msgid "Tunnels and Destinations"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:10
+msgid "Unidirectional tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:16
+msgid "Multihoming"
+msgstr ""
+
diff --git a/i2p2www/translations/es/LC_MESSAGES/about.po b/i2p2www/translations/es/LC_MESSAGES/about.po
new file mode 100644
index 00000000..b6b66dcc
--- /dev/null
+++ b/i2p2www/translations/es/LC_MESSAGES/about.po
@@ -0,0 +1,2744 @@
+# Spanish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Adolfo Jayme Barrientos , 2013
+# Daniel Mustieles , 2013
+# m1xxy , 2011
+# olivertrash , 2013
+# strel, 2013
+# trolly, 2013
+# trolly , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-10-05 15:48+0000\n"
+"Last-Translator: trolly \n"
+"Language-Team: Spanish "
+"(http://www.transifex.com/projects/p/I2P/language/es/)\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/about/browser-config.html:2
+msgid "Web Browser Configuration"
+msgstr "Configuración del navegador web"
+
+#: 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 ""
+"Su navegador web necesita ser configurado para poder navegar eepsites y "
+"para utilizar los outproxies disponibles en I2P. Debajo tiene un paso a "
+"paso para configurar los navegadores más populares."
+
+#: i2p2www/pages/site/about/browser-config.html:11
+msgid "How to configure your browser"
+msgstr "Como configurar su navegador"
+
+#: i2p2www/pages/site/about/browser-config.html:17
+#: i2p2www/pages/site/about/browser-config.html:73
+msgid "Outproxy Terms Of Service"
+msgstr "Términos de servido del Outproxy"
+
+#: i2p2www/pages/site/about/browser-config.html:22
+msgid "Internet Explorer 8 or Chrome"
+msgstr "Internet Explorer 8 o 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 ""
+"En el menú de herramientas seleccione \"Opciones de Internet\" para abrir"
+" la configuración. En la ventana de configuración seleccione la pestaña "
+"de conexiones y pulse en configuración de LAN para configurar el puerto "
+"del proxy."
+
+#: i2p2www/pages/site/about/browser-config.html:28
+msgid "IE Internet Options"
+msgstr "Opciones de Internet de IE"
+
+#: 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 ""
+"Ahora active en la casilla de confirmación \"usar un servidor proxy para "
+"la LAN\"  y también en \"Ignorar servidor para conexiones locales\". "
+"Pulsando en opciones avanzadas abrirá la ventana para abrir puertos. "
+"Entre los valores de la imagen, IP 127.0.0.1y puerto 4444 para HTTP, "
+"puerto 4445 para HTTPS."
+
+#: i2p2www/pages/site/about/browser-config.html:36
+msgid "IE Proxy Settings"
+msgstr "Configuración proxy en 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 ""
+"Desde el menú de herramientas seleccione opciones y abra el menú de "
+"configuración de Firefox. Pulse en Avanzado, entonces pulse en "
+"la pestaña Red. En la sección de Conexiones, pulse el "
+"botón de Configuración. Se le mostrará una ventana como la siguiente:"
+
+#: i2p2www/pages/site/about/browser-config.html:46
+msgid "Firefox Network Options"
+msgstr "Opciones de red de 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 ""
+"En la ventana de  Configuración de Conexiones, pulse el círculo "
+"junto a Configuración manual del proxy, entonces añada "
+"127.0.0.1, puerto 4444 en el campo Proxy HTTP. Añada 127.0.0.1, puerto "
+"4445 en el campo Proxy SSL. Asegúrese de escribir 127.0.0.1 o localhost "
+"en el campo \"Sin proxy para\"."
+
+#: i2p2www/pages/site/about/browser-config.html:53
+msgid "Firefox Proxy Settings"
+msgstr "Configuración del Proxy de 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 ""
+"Desde el menú de Configuración, seleccione Configurar "
+"Konqueror. En el grupo Navegador Web en la parte izquierda "
+"seleccione Proxy. En esta ventana nueva seleccione la opción "
+"\"Especificar manualmente las opciones del Proxy\" y pulse en "
+"Configurar."
+
+#: i2p2www/pages/site/about/browser-config.html:63
+msgid "Konqueror Proxy Options"
+msgstr "Opciones del Proxy de 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 ""
+"Escriba 127.0.0.1 y puerto 4444 en la casilla HTTP. Escriba 127.0.0.1 y "
+"puerto 4445 en la casilla HTTPS. Pulse el botón de Nuevo en la "
+"sección de Excepciones. Escriba localhost y pulse Aceptar. Pulse otra vez"
+" el botón Nuevo y escriba 127.0.0.1 y aceptar. Pulse aceptar una"
+" vez más para salir de la ventana de configuración."
+
+#: i2p2www/pages/site/about/browser-config.html:70
+msgid "Konqueror Proxy Ports"
+msgstr "Puertos del Proxy de 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 ""
+"Recuerde: I2P no fue diseñado para crear proxies de salida al Internet.  "
+"En su lugar está diseñado para ser usado como una red interna."
+
+#: 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 ""
+"El proyecto I2P no ejecuta por sí mismo ningún proxy al Internet. Ese "
+"tipo de servicios proxy son ejecutados por voluntarios privados y pueden "
+"ser apagados o no estar accesibles en todo momento."
+
+#: 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 ""
+"Por defecto, I2P viene con dos proxys externos (`outproxies`) "
+"configurados:\n"
+"%(http)s (un proxy sólo-HTTP) and \n"
+"%(https)s (un proxy HTTPS enrutado hacia Tor)."
+
+#: 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 ""
+"Estos dos outproxies están configurados con límites de conexiones. Esto "
+"significa que sólo están permitidos un número determinado de accesos por "
+"cliente. Cuando se alcanza el límite el cliente es bloqueado por un "
+"periodo de tiempo 1 minuto/1 hora/1 día. Tenga cuidado y no sature estos "
+"servicios con demasiadas peticiones."
+
+#: 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 ""
+"El filtrado está activo sobre estos proxys externos (por ejemplo, mibbit "
+"y el \n"
+"acceso a tracker torrent están bloqueados). Los eepsites que son "
+"accesibles vía direcciones .i2p también son no permitidos vía los proxys"
+" \n"
+"externos. Por convenciencia, false.i2p bloquea servidores de"
+" publicidad."
+
+#: i2p2www/pages/site/about/browser-config.html:100
+msgid ""
+"Tor is good application to use"
+" as an\n"
+"outproxy to the Internet."
+msgstr ""
+"Tor es una buen aplicación "
+"para usar como outproxy al Internet."
+
+#: i2p2www/pages/site/about/glossary.html:2
+msgid "Glossary"
+msgstr "Glosario"
+
+#: i2p2www/pages/site/about/glossary.html:4
+msgid ""
+"This page lists often-used terminology when discussing I2P and "
+"cryptography."
+msgstr ""
+"Esta página muestra la terminología usada cuando se habla de I2P y "
+"cifrados."
+
+#: i2p2www/pages/site/about/hall-of-fame.html:2
+msgid "Hall Of Fame"
+msgstr "Pódium"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:5
+msgid "I2P's Hall of Fame"
+msgstr "Pódium de I2P"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:6
+#, python-format
+msgid "Current balance: as of %(date)s"
+msgstr "Balance actual a día %(date)s"
+
+#: 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 "Caja total"
+
+#: 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 "%(euroval)s € y %(btcval)s BTC"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:11
+msgid "Datastorage bounty"
+msgstr "Recompensa por almacenamiento"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:13
+msgid "Native IPv6 I2P"
+msgstr "IPV6 nativo en I2P"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:15
+msgid "I2PHex bounty"
+msgstr "Recompensa por 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 "Mirros de Debian para I2P"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:19
+msgid "Bitcoin client for I2P"
+msgstr "Cliente Bitcoin para I2P"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:21
+msgid "Unit Tests for I2P router"
+msgstr "Unit Tests para el ruter I2P"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:23
+msgid "Bounty Robert"
+msgstr "Recompensa por Robert"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:24
+msgid "Bounty Syndie"
+msgstr "Recompensa por Syndie"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:25
+msgid "Bounty I2P for CCR Microtic Board"
+msgstr "Recompensa I2P para una placa CCR Mikrotik"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:28
+msgid "Current monthly running costs:"
+msgstr "Gastos mensuales actuales:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:39
+msgid "Big thanks go to the following people who have donated to I2P!"
+msgstr "¡Muchas gracias a las siguientes personas que han donado a I2P!"
+
+#: 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 ""
+"Si ha hecho una donación , por favor envíe un email a echelon con su nombre o nick (y "
+"opcionalmente su página web) para que podamos listarle aquí."
+
+#: i2p2www/pages/site/about/hall-of-fame.html:45
+msgid "Current monthly subscriptions:"
+msgstr "Subscripciones mensuales actuales:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:51
+msgid "2013 donations and costs:"
+msgstr "Donaciones y coste en el 2013:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:170
+msgid "2012 donations and costs:"
+msgstr "Donaciones y coste en el 2012:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:298
+msgid "2011 donations and costs:"
+msgstr "Donaciones y coste en el 2011:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:399
+msgid "Previous to 2011 donations:"
+msgstr "Donaciones previas al 2011:"
+
+#: i2p2www/pages/site/about/intro.html:2
+msgid "Intro"
+msgstr "Introducción"
+
+#: i2p2www/pages/site/about/intro.html:4
+msgid "The Invisible Internet Project"
+msgstr "El proyecto de Internet Invisible"
+
+#: i2p2www/pages/site/about/intro.html:5
+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 \n"
+"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 ""
+"I2P es una red anónima que da acceso a una capa de red que las "
+"aplicaciones pueden utilizar para anonimizar y cifrar el envío de "
+"mensajes de uno a otro. La red en sí está estrictamente basada en el "
+"envío de mensajes (a la  IP), pero "
+"existe una librería disponible que permite la comunicación segura sobre "
+"él (a la TCP)."
+" Todas las comunicaciones están cifradas de extremo a extremo (en total "
+"de usan 4 capas de cifrados cifrados por cada mensaje enviado), e incluso"
+" el extremo final \n"
+"(\"destinaciones\") son identificados criptográficamente (básicamente con"
+" un par de claves "
+"públicas)."
+
+#: i2p2www/pages/site/about/intro.html:17
+msgid "How does it work?"
+msgstr "¿Cómo funciona?"
+
+#: i2p2www/pages/site/about/intro.html:19
+#, 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 ""
+"Para a anonimizar los mensajes enviados, cada aplicación cliente tiene su"
+" \"ruter\" I2P que crea unos cuantos túneles\"  de entrada y salida - una "
+"secuencia de pares que pasan el mensaje en una dirección (hacia y desde "
+"el cliente, respectivamente ). A su vez, cuando un cliente quiere enviar "
+"un mensaje a otro cliente, el cliente envía ese mensaje a través de uno "
+"de sus túneles de salida hacia uno de los túneles de entrada del otro "
+"cliente, eventualmente alcanzando su destino."
+
+#: i2p2www/pages/site/about/intro.html:33
+#, 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 ""
+"La primera vez que un cliente quiere contactar con otro cliente, "
+"consultan la \"base de datos distribuida de la "
+"red\" - unas  tablas de "
+"hash distribuidas propia (DHT) basada en el algoritmo Kademlia. "
+"Esto se hace para encontrar el túnel de entrada del otro cliente "
+"eficientemente, pero los mensajes siguientes entre los clientes "
+"usualmente incluye la información, con lo cual\n"
+"no hace falta buscar en la base de datos de la red otra vez."
+
+#: i2p2www/pages/site/about/intro.html:44
+#, python-format
+msgid "More details about how I2P works are available."
+msgstr ""
+"Tiene disponibles mas detalles de como funciona "
+"I2P."
+
+#: i2p2www/pages/site/about/intro.html:48
+msgid "What can you do with it?"
+msgstr "¿Qué puede hacer con él?"
+
+#: i2p2www/pages/site/about/intro.html:50
+#, 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 ""
+"Dentro de la red I2P las aplicaciones no tienen restricciones en como "
+"pueden comunicarse - aquellas que normalmente usan UDP pueden usar las "
+"funcionalidades básicas de I2P, y aquellas aplicaciones que normalmente "
+"usan TCP pueden utilizar la librería 'tipo TCP de streaming'. I2P incluye"
+"  una aplicación genérica de puente TCP/I2P (\"I2PTunnel\") que permite enviar flujos TCP "
+"dentro de la red I2P, también recibir flujos TCP de fuera de la red y  "
+"enviar estos a una dirección IP específica."
+
+#: i2p2www/pages/site/about/intro.html:60
+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 ""
+"El túnel I2P (I2Ptunnel) es actualmente usado para permitir a la gente "
+"tener su propia web anónima (\"eepsite\"), ejecutando un servidor web "
+"normal y creando un túnel 'servidor' hacia ella, esta eepsite podrá ser "
+"accedida anónimamente sobre I2P con un navegador web normal usando un "
+"túnel proxy I2P (\"eepproxy\"). Además usamos la misma técnica para "
+"ejecutar redes IRC anónimas (donde el servidor IRC esta hospedado "
+"anónimamente y los clientes normales de IRC usan un túnel I2P para "
+"conectarse). Se están haciendo esfuerzos para programar otras "
+"aplicaciones, como una aplicación optimizada para compartir archivos (a "
+"la \n"
+"BitTorrent), almacenamiento de"
+" datos distribuido (a la Freenet /MNet), y un sistema de blogs "
+"totalmente distribuido LiveJournal, pero estos \n"
+"no están listos totalmente todavía. "
+
+#: i2p2www/pages/site/about/intro.html:76
+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 ""
+"I2P no es inherentemente una red \"outproxy\" - el cliente al que envías "
+"un mensaje es un identificador criptográfico, no una dirección IP, por lo"
+" cual el mensaje debe ser enviado a alguien que use I2P. Aunque es "
+"posible que un cliente sea un 'outproxy', permitiendo el uso de una "
+"conexión a Internet anónima, el \"eepproxy\"  aceptará URLs normales no "
+"I2P (e.g. \"http://www.i2p.net\") y las reenviará a una destinación "
+"específica que usa un proxy HTTP squid, permitiendo navegar Internet de una forma anónima"
+" y fácil. Outproxies como estos no son siempre viables  por varias "
+"razones (incluyendo el coste de tener uno y los problemas de anonimato y "
+"seguridad que acarrea), pero en ciertas circunstancias su uso puede ser "
+"apropiado."
+
+#: i2p2www/pages/site/about/intro.html:90
+#, 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 ""
+"El equipo de desarrollo de I2P es un grupo "
+"abierto, todos los que estén interesados son bienvenidos a involucrarse en el proyecto, y todo el código "
+"es libre. El núcleo de I2P y la "
+"implementación del ruter están en java (actualmente trabajando con sun y "
+"kaffe, el soporte para gjc está planeado para mas adelante), y hay un  API simple para acceder a la red desde otros "
+"lenguajes (con una librería C disponible, y con Python y Perl en "
+"desarrollo). La red está en estos momentos en desarrollo activamente y "
+"aún no ha alcanzado la versión 1.0, pero la actual hoja de ruta describe nuestro programa."
+
+#: i2p2www/pages/site/about/media.html:2 i2p2www/pages/site/about/media.html:4
+msgid "Presentations on I2P"
+msgstr "Presentaciones sobre I2P"
+
+#: 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 ""
+"Los siguientes enlaces son presentaciones, vídeos y tutoriales sobre I2P."
+" Los enlaces para investigación sobre I2P están disponibles aquí."
+
+#: i2p2www/pages/site/about/media.html:8
+#, python-format
+msgid "To request an addition to this page, please send to %(email)s."
+msgstr "Para solicitar añadidos a esta web por favor envíelos a %(email)s."
+
+#: i2p2www/pages/site/about/media.html:11
+msgid ""
+"\n"
+"Newest links are at the bottom of each section."
+msgstr ""
+"\n"
+"Los enlaces más nuevos al final de cada sección."
+
+#: i2p2www/pages/site/about/media.html:16
+msgid "Presentations"
+msgstr "Presentaciones"
+
+#: 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 ""
+"IIP Presentación en CodeCon MP3 audio transcripción Lance James (0x90), Febrero"
+" 2002."
+
+#: 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 ""
+"IIP Presentación en  ToorCon MP3 audio diapositivas Lance James (0x90), Septiembre "
+"2002."
+
+#: 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 ""
+"To Be or I2P (Youtube Video) Una "
+"introducción a las comunicaciones anónimas con I2P. To Be or I2P (PDF presentation), Jens Kubieziel,"
+" 24C3 Berlin, Diciembre 28, 2007."
+
+#: 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 ""
+"Vídeo de charla I2P en Chemnitz Linux Tag, "
+"Lars Schimmer, Marzo 14-15, 2009"
+
+#: 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 ""
+"HOPE New York Julio 17, 2010 - Vista rápida sobre I2P by zzz, al final de"
+" la charla de  Adrian Hong \\\"Hackers for Human Rights\\\". MP3 audio"
+
+#: 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 ""
+"Into the I2P Darknet: Welcome to Cipherspace"
+" Adrian Crenshaw. Schmoocon Firetalk, Enero 2011"
+
+#: 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 ""
+"Usando la tecnología para mejorar la "
+"libertad (Youtube Vídeo) Eric Johnson. Agora I/O Unconference, Marzo "
+"27, 2011. I2P desde 10:00 a 20:00 en el vídeo."
+
+#: i2p2www/pages/site/about/media.html:69
+#, python-format
+msgid ""
+"The Bright side of darknets, FOSSCOMM Patras May "
+"2011"
+msgstr ""
+"The Bright side of darknets, FOSSCOMM Patras Mayo"
+" 2011"
+
+#: 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 ""
+"Common Darknet Weaknesses (Vídeo en Youtube) "
+"Adrian Crenshaw, AIDE, Julio "
+"11-15, 2011"
+
+#: 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 ""
+"I2P / Tor Workshop Notes Adrian Crenshaw. DEF "
+"CON 19, Las Vegas, Agosto 6, 2011."
+
+#: 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 ""
+"Cipherspaces/Darknets: An Overview Of Attack "
+"Strategies - DEF CON Vesión en vivo (Vídeo de Youtube), versión de \"estudio\"  (Youtube Video), Slides (ppt) Adrian Crenshaw. DEF CON 19, Las "
+"Vegas, Agosto 7, 2011."
+
+#: i2p2www/pages/site/about/media.html:94
+msgid ""
+"Modern cipherspace ecosystems, 0x375 "
+"0x06 4/11/2011"
+msgstr ""
+"Modern cipherspace ecosystems, 0x375 "
+"0x06 4/11/2011"
+
+#: i2p2www/pages/site/about/media.html:100
+msgid "Tutorials"
+msgstr "Tutoriales"
+
+#: 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 ""
+"I2P Windows Tutorial (Youtube Video) Esta guía "
+"le mostrará cono instalar I2P en Windows. Por Telecomix"
+
+#: 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 ""
+"I2P Debian Tutorial (Vídeo en Youtube) Esta guía"
+" le mostrará como instalar I2P en sistemas basados en Debian. Por Telecomix"
+
+#: 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 ""
+"How to set up anonymous site in I2P (Vídeo en "
+"Youtube) Como configurar una web anónima en I2P. Por Telecomix"
+
+#: 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 ""
+"I2P Tutorial Mac OS X (Vídeo en Youtube) Un "
+"tutorial de como ejecutar I2P en os X y como conectar a "
+"irc.telecomix.i2p. Por Telecomix"
+
+#: 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 ""
+"Felix Atari explains the basic principles of I2P"
+" (Vídeo en Youtube) Agent Felix Atari of the Telecomix Crypto Munitions "
+"Bureau. Por Telecomix"
+
+#: 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 ""
+"How to get onto I2P, the anonymous P2P Darknet "
+"(Windows Install) (Vídeo en Youtube) Esta guía muestra como instalar "
+"y configurar las aplicaciones necesarias para acceder a I2P."
+
+#: 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 ""
+"How to connect to I2P (Vídeo en Youtube) Como "
+"instalar I2P en Ubuntu."
+
+#: 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 ""
+"Installing the I2P darknet software in Linux "
+"(Vídeo) Adrian Crenshaw. Enero 2011"
+
+#: i2p2www/pages/site/about/media.html:159
+#, python-format
+msgid ""
+"Short garlic routing animation\n"
+"(Youtube Video)\n"
+"Adrian Crenshaw.\n"
+msgstr ""
+"Short garlic routing animation (Vídeo en "
+"Youtube) Adrian Crenshaw.\n"
+
+#: i2p2www/pages/site/about/media.html:167
+msgid "Articles and Interviews"
+msgstr "Artículos y entrevistas"
+
+#: 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 ""
+"0x90 Entrevistado por DistributedCity Parte 1 "
+"Parte 2 Julio 26, 2002."
+
+#: 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 ""
+"0x90 Entrevistado por El Pais (original en Castellano) Traducción al inglés Octubre 31, 2002."
+
+#: i2p2www/pages/site/about/media.html:185
+#, python-format
+msgid ""
+"2003 Business Week article referencing "
+"invisiblenet"
+msgstr ""
+"2003 Business Week article referencing "
+"invisiblenet"
+
+#: 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 ""
+"Artículo del Netzwelt.de sobre como permanecer "
+"anónimos en Internet (Alemán) Noviembre 2007."
+
+#: i2p2www/pages/site/about/media.html:195
+#, python-format
+msgid ""
+"zzz interviewed by gulli.com\n"
+"March 2009\n"
+"German translation"
+msgstr ""
+"zzz entrevistado por gulli.com\n"
+"Marzo de 2009\n"
+"Traducción al alemán"
+
+#: 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 ""
+"zzz entrevistado en el podcast diario de InfoSec  Ep."
+" 454 (mp3) Agosto 18, 2011"
+
+#: i2p2www/pages/site/about/media.html:207
+#, python-format
+msgid ""
+"I2P - Anonymity for the Masses,\n"
+"Jonathan Cox,\n"
+"November 11, 2011."
+msgstr ""
+"I2P - Anonymity for the Masses, Jonathan Cox, "
+"Noviembre 11, 2011."
+
+#: 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 ""
+"zzz y Lance James entrevistados en el podcast diario "
+"de InfoSec  Ep. 596 (mp3) Febrero 16, 2012"
+
+#: i2p2www/pages/site/about/team.html:2
+msgid "Team"
+msgstr "Equipo"
+
+#: i2p2www/pages/site/about/team.html:4
+msgid "I2P Project Members"
+msgstr "Miembros del proyecto 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 ""
+"Somos un pequeño grupo de personas repartidas por varios continentes, "
+"trabajando para mejorar diferentes aspectos del proyecto y discutir el "
+"diseño de la red.¿Únete!"
+
+#: i2p2www/pages/site/about/team.html:14
+msgid "Admin"
+msgstr "Administradores"
+
+#: i2p2www/pages/site/about/team.html:15
+msgid "Project Manager"
+msgstr "Director del proyecto"
+
+#: i2p2www/pages/site/about/team.html:17
+msgid "point of contact of last resort"
+msgstr "contacto como último recurso"
+
+#: i2p2www/pages/site/about/team.html:20
+msgid "Treasurer"
+msgstr "Tesorero"
+
+#: i2p2www/pages/site/about/team.html:22
+msgid "manage donations / accounts / bounties"
+msgstr "administra las donaciones / cuentas / recompensas"
+
+#: i2p2www/pages/site/about/team.html:25
+msgid "PR manager"
+msgstr "Administrador PR"
+
+#: i2p2www/pages/site/about/team.html:27
+msgid "press contact, manages public relations and affairs"
+msgstr "contacto con la prensa, relaciones públicas y negocios"
+
+#: i2p2www/pages/site/about/team.html:30
+#, python-format
+msgid "Forum admin"
+msgstr "Administrador del Foro"
+
+#: i2p2www/pages/site/about/team.html:32
+msgid "manage the public user forum"
+msgstr "administrador del foro público"
+
+#: i2p2www/pages/site/about/team.html:35
+msgid "Mirrors admin"
+msgstr "Administrador de mirrors"
+
+#: i2p2www/pages/site/about/team.html:37
+msgid "manage the project mirrors"
+msgstr "administrador de los proyectos de los mirrors"
+
+#: i2p2www/pages/site/about/team.html:40
+#, python-format
+msgid "Monotone guru"
+msgstr "Gurú de Monotone"
+
+#: i2p2www/pages/site/about/team.html:42
+msgid "manage the public monotone repositories"
+msgstr "administrador de los repositorios públicos de monotone"
+
+#: i2p2www/pages/site/about/team.html:45
+msgid "Packager; Linux"
+msgstr "Empaquetador; Linux"
+
+#: i2p2www/pages/site/about/team.html:47
+msgid "Linux (Debian/Ubuntu) distribution packager"
+msgstr "Mantenimiento de paquetes para distribuciones Linux (Debian/Ubuntu)"
+
+#: i2p2www/pages/site/about/team.html:50
+msgid "Packager; Windows"
+msgstr "Empaquetador; Windows"
+
+#: i2p2www/pages/site/about/team.html:52
+msgid "Windows installer packager"
+msgstr "Paquetes instaladores para Windows"
+
+#: i2p2www/pages/site/about/team.html:55
+msgid "Release Manager"
+msgstr "Administrador de versiones"
+
+#: i2p2www/pages/site/about/team.html:57
+msgid "Builds and signs the releases"
+msgstr "Compila y firma los paquetes"
+
+#: i2p2www/pages/site/about/team.html:60
+msgid "Update admin"
+msgstr "Administrador de actualizaciones"
+
+#: i2p2www/pages/site/about/team.html:62
+msgid "Monitors and recruits in-network update hosts"
+msgstr "Supervisa y adquiere hosts de actualizaciones en la red"
+
+#: i2p2www/pages/site/about/team.html:65
+msgid "Reseed admin"
+msgstr "Administrador de la resiembra"
+
+#: i2p2www/pages/site/about/team.html:67
+msgid "Monitors, advises and recruits reseed hosts"
+msgstr "Supervisa, asesora y adquiere hosts de resiembra"
+
+#: i2p2www/pages/site/about/team.html:70
+msgid "Security expert"
+msgstr "Experto en seguridad"
+
+#: 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 "vacante"
+
+#: i2p2www/pages/site/about/team.html:72
+msgid "threat model / crypto expert"
+msgstr "modelos de amenazas / experto en cifrados"
+
+#: i2p2www/pages/site/about/team.html:77
+#, fuzzy
+msgid "Manage the project bug tracker"
+msgstr "administrador de los proyectos de los mirrors"
+
+#: i2p2www/pages/site/about/team.html:80
+#, fuzzy
+msgid "Translation admins"
+msgstr "traducción al francés"
+
+#: i2p2www/pages/site/about/team.html:85
+msgid "User Advocate"
+msgstr "Defensor del usuario"
+
+#: i2p2www/pages/site/about/team.html:87
+msgid "gather, prioritize, advocate for user needs"
+msgstr "recogida, priorización y enfocado en las necesidades de los usuarios"
+
+#: i2p2www/pages/site/about/team.html:90
+msgid "Web Designer"
+msgstr "Diseñador web"
+
+#: i2p2www/pages/site/about/team.html:92
+msgid "manage the public project website content design"
+msgstr "administrar el diseño de la web del proyecto"
+
+#: i2p2www/pages/site/about/team.html:95
+#, python-format
+msgid "Webserver admin"
+msgstr "Administración del Webserver"
+
+#: i2p2www/pages/site/about/team.html:97
+msgid "manage the public project webservers"
+msgstr "administrador de los servidores web públicos del proyecto"
+
+#: i2p2www/pages/site/about/team.html:100
+#, python-format
+msgid "Website admin"
+msgstr "administración de la Website "
+
+#: i2p2www/pages/site/about/team.html:102
+msgid "manage the public project website content"
+msgstr "administrador del contenido del la web del proyecto"
+
+#: i2p2www/pages/site/about/team.html:105
+msgid "News Admin"
+msgstr "Administrador de noticias"
+
+#: i2p2www/pages/site/about/team.html:107
+msgid "manage router console news feed"
+msgstr "encargado de las noticias de la consola del ruter"
+
+#: i2p2www/pages/site/about/team.html:110
+msgid "Director of passion"
+msgstr "Director de pasión"
+
+#: i2p2www/pages/site/about/team.html:112
+msgid "community motivator"
+msgstr "Motivador de la comunidad"
+
+#: i2p2www/pages/site/about/team.html:116
+msgid "Dev"
+msgstr "Desarrolladores"
+
+#: i2p2www/pages/site/about/team.html:117
+msgid "Core Lead"
+msgstr "Encargado del núcleo"
+
+#: i2p2www/pages/site/about/team.html:119
+msgid "lead dev for the SDK and router"
+msgstr "encargado del SDK y del ruter"
+
+#: i2p2www/pages/site/about/team.html:122
+#, python-format
+msgid "I2P mail lead"
+msgstr "Encargado de I2P mail"
+
+#: i2p2www/pages/site/about/team.html:124
+msgid "organize and develop the i2p mail system"
+msgstr "organiza y desarrolla el sistema de mail de I2P"
+
+#: i2p2www/pages/site/about/team.html:127
+#, python-format
+msgid "I2Host lead"
+msgstr "Encargado del I2Host"
+
+#: i2p2www/pages/site/about/team.html:129
+msgid "I2Host addressbook application"
+msgstr "aplicación de la lista de direcciones de I2Host"
+
+#: i2p2www/pages/site/about/team.html:132
+#, python-format
+msgid "BOB lead"
+msgstr "Encargado de BOB"
+
+#: i2p2www/pages/site/about/team.html:134
+msgid "Basic Open Bridge"
+msgstr "Basic Open Bridge"
+
+#: i2p2www/pages/site/about/team.html:137
+#, python-format
+msgid "I2P-Bote lead"
+msgstr "Encargado de I2P-Bote"
+
+#: i2p2www/pages/site/about/team.html:139
+msgid "I2PBote plugin"
+msgstr "pluguin I2PBote"
+
+#: i2p2www/pages/site/about/team.html:142
+#, python-format
+msgid "Robert lead"
+msgstr "Encargado de Robert"
+
+#: i2p2www/pages/site/about/team.html:144
+msgid "Robert BitTorrent client"
+msgstr "cliente de bittorrent Robert"
+
+#: i2p2www/pages/site/about/team.html:147
+#, python-format
+msgid "I2Phex lead"
+msgstr "Encargado de I2Phex "
+
+#: i2p2www/pages/site/about/team.html:149
+msgid "I2Phex Gnutella client"
+msgstr "cliente de I2Phex Gnutella"
+
+#: i2p2www/pages/site/about/team.html:152
+#, python-format
+msgid "I2PSnark lead"
+msgstr "Encargado de I2PSnark"
+
+#: i2p2www/pages/site/about/team.html:154
+msgid "Maintains the integrated Bittorrent client"
+msgstr "Mantiene el cliente Bittorrent integrado"
+
+#: i2p2www/pages/site/about/team.html:157
+#, python-format
+msgid "iMule lead"
+msgstr "Encargado de iMule"
+
+#: i2p2www/pages/site/about/team.html:159
+msgid "eMule client over I2P"
+msgstr "cliente e2dk sobre I2P"
+
+#: i2p2www/pages/site/about/team.html:162
+#, python-format
+msgid "Syndie lead"
+msgstr "Encargado de Syndie"
+
+#: i2p2www/pages/site/about/team.html:164
+msgid "Syndie development"
+msgstr "Desarrollo de Syndie"
+
+#: i2p2www/pages/site/about/team.html:167
+msgid "Susimail lead"
+msgstr "Encargado de Susimail"
+
+#: i2p2www/pages/site/about/team.html:169
+msgid "Susimail development"
+msgstr "Desarrollo de Susimail"
+
+#: i2p2www/pages/site/about/team.html:172
+msgid "Console"
+msgstr "Consola"
+
+#: i2p2www/pages/site/about/team.html:174
+msgid "Router console HTML/CSS design"
+msgstr "Diseño del HTML/CSS de la consola del ruter"
+
+#: i2p2www/pages/site/about/team.html:177
+msgid "SAM"
+msgstr "SAM"
+
+#: i2p2www/pages/site/about/team.html:179
+msgid "SAM maintainer"
+msgstr "Encargado de SAM"
+
+#: i2p2www/pages/site/about/team.html:182
+msgid "I2PCPP lead"
+msgstr "Encargado de I2PCPP"
+
+#: i2p2www/pages/site/about/team.html:184
+msgid "C++ Router"
+msgstr "Ruter C++"
+
+#: 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 "Contribuidores"
+
+#: i2p2www/pages/site/about/team.html:195
+msgid "fire2pe dev, console enhancements"
+msgstr "Desarrollador de fire2pe, mejoras de la consola"
+
+#: i2p2www/pages/site/about/team.html:199
+msgid "desktopgui, dijjer port"
+msgstr "entorno de escritorio, puerto dijjer"
+
+#: i2p2www/pages/site/about/team.html:203
+msgid "Debian/Ubuntu Packager and PPA maintainer"
+msgstr "Encargado de los paquetes para Debian/Ubuntu y del PPA"
+
+#: i2p2www/pages/site/about/team.html:207
+msgid "Routerconsole backend and UI work, website revamp, unit tests work"
+msgstr ""
+"Trabajos en la consola del ruter y el interfaz gráfico, mejora de la web,"
+" y trabajos en los unit tests"
+
+#: i2p2www/pages/site/about/team.html:212
+msgid "Help needed on many fronts!"
+msgstr "Se necesita diversas formas de ayuda"
+
+#: i2p2www/pages/site/about/team.html:216
+msgid "Past contributors"
+msgstr "Participantes pasados"
+
+#: i2p2www/pages/site/about/team.html:218
+msgid "I2PTunnel development, ministreaming library"
+msgstr "Desarrollo de I2PTunnel, librería de ministreaming"
+
+#: i2p2www/pages/site/about/team.html:222
+msgid "Project lead, Syndie lead"
+msgstr "Encargado del proyecto, encargado de Syndie"
+
+#: i2p2www/pages/site/about/team.html:226
+msgid "Project lead, Syndie lead, I2Phex, support guru"
+msgstr "Encargado del proyecto, encargado de Syndie, I2Phex, soporte"
+
+#: i2p2www/pages/site/about/team.html:230
+msgid "iMule lead"
+msgstr "Encargado de IMule"
+
+#: 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 "Trabajo en I2Phex"
+
+#: i2p2www/pages/site/about/team.html:246
+msgid "Python SAM library, attack simulations"
+msgstr "librería SAM en Python, simulaciones de ataques"
+
+#: i2p2www/pages/site/about/team.html:250
+msgid "i2pmail development"
+msgstr "Desarrollo de i2pmail"
+
+#: i2p2www/pages/site/about/team.html:254
+msgid "Syndie help"
+msgstr "Ayuda de Syndie"
+
+#: i2p2www/pages/site/about/team.html:258
+msgid "i2p mail,susimail and susidns apps"
+msgstr "Mail de i2p, susimail y aplicaciones susidns"
+
+#: i2p2www/pages/site/about/team.html:262
+msgid "I2Phex (port of Phex to I2P)"
+msgstr "I2Phex (versión de Phex para I2P)"
+
+#: i2p2www/pages/site/about/team.html:266
+msgid "addressbook,i2p-bt,syndie client"
+msgstr "libreta de direcciones, i2p-bt,cliente syndie"
+
+#: i2p2www/pages/site/about/team.html:270
+msgid "organize and develop the i2p-bt BitTorrent port"
+msgstr "organización y desarrollo de la versión de Bittorrent i2p-bt"
+
+#: i2p2www/pages/site/about/team.html:274
+msgid "addressbook, i2p-bt, syndie client development"
+msgstr "libreta de direcciones, i2p-bt, y desarrollo del cliente de syndie"
+
+#: i2p2www/pages/site/about/team.html:278
+msgid "encryption and signature routines, I2PIM"
+msgstr "rutinas de cifrado y firma, I2P IM"
+
+#: i2p2www/pages/site/about/team.html:282
+msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)"
+msgstr "código jython de SAM, trabajo en stasher (DHT) y v2v (VoI2P)"
+
+#: i2p2www/pages/site/about/team.html:286
+msgid "installer, systray, bogobot"
+msgstr "instalador, bandeja de sistema, bogobot"
+
+#: i2p2www/pages/site/about/team.html:290
+msgid "jbigi development, wiki migration, doc cleanup"
+msgstr "desarrollo de jbigi, migración de la wiki, limpieza de la documentación"
+
+#: i2p2www/pages/site/about/team.html:294
+msgid "java debugging and client development on I2PTunnel and the router console"
+msgstr ""
+"depuración de java y desarrollo del cliente en I2PTunnel y en la consola "
+"del ruter"
+
+#: i2p2www/pages/site/about/team.html:298
+msgid "SAM perl module"
+msgstr "Módulo perl de SAM"
+
+#: i2p2www/pages/site/about/team.html:302
+msgid "i2psnark work"
+msgstr "trabajo en i2psnark"
+
+#: i2p2www/pages/site/about/team.html:306
+msgid "java cleanup"
+msgstr "limpieza de java"
+
+#: i2p2www/pages/site/about/team.html:310
+msgid "docs. wiki migration"
+msgstr "documentos, migración de la wiki"
+
+#: i2p2www/pages/site/about/team.html:314
+msgid "translations into French"
+msgstr "traducción al francés"
+
+#: i2p2www/pages/site/about/team.html:318
+msgid "C port of jcpuid"
+msgstr "port en C de jcpuid"
+
+#: i2p2www/pages/site/about/team.html:322
+msgid "C# SAM library, pants, fortuna integration"
+msgstr "librería C# de SAM, integración de fortuna"
+
+#: i2p2www/pages/site/about/team.html:326
+msgid "libSAM"
+msgstr "libSAM"
+
+#: i2p2www/pages/site/about/team.html:330
+#: i2p2www/pages/site/about/team.html:334
+msgid "i2p-bt tracker development"
+msgstr "desarrollo del tracker i2p-bt"
+
+#: i2p2www/pages/site/about/team.html:338
+msgid "Console and website themes"
+msgstr "Temas de la consola y la web"
+
+#: i2p2www/pages/site/about/team.html:368
+msgid "… and many others"
+msgstr "… y muchas otros"
+
+#: i2p2www/pages/site/about/performance/future.html:2
+msgid "Future Performance Improvements"
+msgstr "Mejoras futuras en el rendimiento"
+
+#: i2p2www/pages/site/about/performance/future.html:4
+msgid "August 2010"
+msgstr "Agosto del 2010"
+
+#: 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 ""
+"Hay varias técnicas para mejorar el rendimiento de I2P - algunas tienen "
+"que ver con la CPU, otras con el ancho de banda y otras relacionadas con "
+"los protocolos. Sin embargo, todas estas mejoras afectan la latencia, la "
+"cantidad de datos enviados y el rendimiento de la red, mientras que "
+"reducen la competencia por los recursos escasos. Esta lista no está "
+"completa, pero abarca las más importantes que se conocen."
+
+#: 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 ""
+"Para ver las mejoras de rendimiento pasadas vea  "
+"historial de rendimiento."
+
+#: i2p2www/pages/site/about/performance/future.html:20
+msgid "Better peer profiling and selection"
+msgstr "Mejor selección de pares y sus perfiles."
+
+#: 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 ""
+"Probablemente, una de las partes más importantes para conseguir una "
+"mejora en el rendimiento será mejorar como los ruters elijen los pares a "
+"través de los que construyen los túneles - asegurándose que no utiliza "
+"pares con enlaces lentos o con enlaces rápidos pero sobrecargados. etc. "
+"Además, tenemos que asegurarnos que no nos exponemos a un ataque Sybil de un adversario con muchos recursos y "
+"con máquinas muy rápidas."
+
+#: i2p2www/pages/site/about/performance/future.html:30
+msgid "Network database tuning"
+msgstr "Base de datos de la Red I2P"
+
+#: 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 ""
+"Queremos ser más eficientes en la reparación de la base de datos de la "
+"red y los algoritmos de mantenimiento - en vez de explorar la red "
+"constantemente buscando nuevos pares - causando un gran número de "
+"mensajes y carga en el ruter -  podemos frenar o incluso parar la "
+"búsqueda mientras no se detecte que hay algo nuevo por explorar (por "
+"ejemplo, ralentizar la tasa de exploración dependiendo de la última vez "
+"que algún par nos dio una referencia de algún otro par desconocido). "
+"También podemos mejorar lo que enviamos - cuantos pares recuperamos (o "
+"incluso si recuperamos una respuesta), también podemos mejorar cuantas "
+"búsquedas concurrentes hacemos."
+
+#: i2p2www/pages/site/about/performance/future.html:42
+msgid "Session Tag Tuning and Improvements"
+msgstr "Mejoras en las Etiquetas de Sesión"
+
+#: 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 ""
+"La forma en que funciona el algoritmo ElGamal/AES+SessionTag es administrando un "
+"conjunto de arrays de 32 bytes aleatorios de un solo uso, y desechándolos"
+" cuando no se usan los suficientemente rápido. Si los desechamos "
+"demasiado pronto, tenemos que crear otra vez un cifrado (muy caro) "
+"ElGamal, pero si no los desechamos a tiempo, tenemos que reducir su "
+"número o nos quedaremos sin memoria RAM (y si al destinatario de alguna "
+"forma se le corrompen y pierde algunas etiquetas, pueden ocurrir incluso "
+"más fallos en los cifrados). Con algoritmos con detección activa y de "
+"control, podemos ajustar de una forma más segura y eficientemente el "
+"tiempo de vida de una etiqueta, reemplazando el cifrado ElGamal con un "
+"algoritmo más trivial como AES."
+
+#: 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 ""
+"Algunas ideas adicionales para mejorar el envío de las Etiquetas de "
+"Sesión se describen en la página de "
+"ElGamal/AES+SessionTag."
+
+#: i2p2www/pages/site/about/performance/future.html:61
+msgid "Migrate sessionTag to synchronized PRNG"
+msgstr "Migrar las Etiquetas de sesión a PRNG sincronizado."
+
+#: 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 ""
+"Ahora mismo, nuestro algoritmo ElGamal/AES+SessionTag funciona etiquetando "
+"cada mensaje cifrado con un 'nonce' único de 32 bytes (una \"etiqueta de "
+"sesión\"), identificando el mensaje como un mensaje cifrado con la clave "
+"de sesión AES asociada. Esto previene que los pares distingan los "
+"mensajes que son parte de la misma sesión, ya que cada mensaje tiene una "
+"etiqueta nueva completamente aleatoria. Para llevar esto acabo, cada unos"
+" pocos mensajes se envuelven un nuevo conjunto de etiquetas de sesión "
+"dentro del mensaje cifrado, creando una forma transparente de identificar"
+" los mensajes futuros. Por lo tanto tenemos que llevar un control de "
+"cuales mensajes han llegado con éxito a su destino para saber que "
+"etiquetas debemos usar."
+
+#: 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 ""
+"Este sistema funciona bien y es muy robusto, aunque no es eficiente en el"
+" uso del ancho de banda, y necesita el envío de estas etiquetas antes de "
+"tiempo (y no todas las etiquetas serán necesarias, o se desperdician, "
+"debido al tiempo de expiración). De media, enviar con antelación las "
+"etiquetas de sesión cuesta 32 bytes por mensaje (el tamaño de una "
+"etiqueta). aunque como ha sugerido Taral, ese tamaño puede evitarse "
+"reemplazando el envío de etiquetas con un PRNG sincronizado - cuando una "
+"nueva sesión se establece (a través de un bloque cifrado ElGamal), ambos "
+"lados siembran un PRNG para generar las etiquetas de sesión cuando se "
+"necesite (con el destinatarios pre calculando los siguientes valores para"
+" poder manejar los envíos)"
+
+#: i2p2www/pages/site/about/performance/future.html:87
+msgid "Longer lasting tunnels"
+msgstr "Tiempo de duración máximo de los túneles."
+
+#: 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 ""
+"El tiempo de duración actual de 10 minutes es bastante arbitrario, aunque"
+" parece que funciona bien. Una vez que tengamos el código de reparación "
+"de túnel y un sistema de detección de fallos más eficiente, podremos "
+"cambiar estas duraciones de forma más segura, reduciendo la carga en la "
+"CPU y en la red (debido al excesivo costo al crear los mensajes de los "
+"túneles). "
+
+#: 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 ""
+"Esto parece un fácil arreglo para la carga de la CPU y el gasto de ancho "
+"de banda en los ruters, pero no podemos usarlos hasta que hayamos afinado"
+" mucho mejor los algoritmos de creación de túneles.\n"
+"Aún así, el tiempo de vida de 10 minutos está incluido en varios sitios, "
+"con lo que hará falta bastante esfuerzo para cambiar esta duración. "
+"Además, será dificil mantener la compatibilidad con versiones anteriores "
+"tras este cambio."
+
+#: 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 ""
+"Actualmente, ya que el éxito en la creación de túneles de la red es "
+"bastante alto, no existen planes para aumentar el tiempo de vida de los "
+"túneles."
+
+#: i2p2www/pages/site/about/performance/future.html:108
+msgid "Adjust the timeouts"
+msgstr "Ajustar tiempo máximo de espera"
+
+#: 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 ""
+"Otros truquitos arbitrarios que parece que \"funcionan bien\" usados son "
+"los tiempos de vida actuales de varias actividades. ¿Por qué tenemos 60 "
+"segundos para el tiempo de vida de \"par inaccesible\"?¿Por qué "
+"intentamos usar un diferente túnel que el LeaseSet nos avisa después de "
+"10 segundos?¿Por qué las consultas a la base de datos está limitada por "
+"60 o 20 segundos?¿Por qué están las destinaciones configuradas para "
+"preguntar por un nuevo grupo de túneles cada 10 minutos?¿Por qué "
+"permitimos a un par tardar 60 segundos en responder a la petición de "
+"unirse a un túnel?¿Por qué consideramos un túnel como \"muerto\" si no "
+"pasa nuestras pruebas en 60 segundos?"
+
+#: 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 ""
+"Todos estos imponderables pueden solucionarse con un código más "
+"adaptativo, al igual que con parámetros afinables que compensen el gasto "
+"entre el ancho de banda, latencia y el uso de CPU."
+
+#: i2p2www/pages/site/about/performance/future.html:125
+msgid "Full streaming protocol improvements"
+msgstr "Mejoras en el protocolo de transmisión"
+
+#: 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 ""
+"Quizás usando de nuevo el perfil de transmisión interactivo (la "
+"implementación actual sólo usa el perfil de transmisión normal)."
+
+#: 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 ""
+"Limitación del ancho de banda en el cliente (en una o las dos direcciones"
+" de una conexión, o posiblemente compartido entre varias conexiones). "
+"Esto será además del límite general de ancho de banda, por supuesto."
+
+#: i2p2www/pages/site/about/performance/future.html:141
+msgid ""
+"Access control lists (only allowing streams to or from certain other "
+"known \n"
+"destinations)."
+msgstr ""
+"Listas de control de acceso (sólo permitiendo conexiones desde o hacia "
+"otras destinaciones conocidas)."
+
+#: 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 ""
+"Control por web y monitorización del estado de varias conexiones, además "
+"de la posibilidad explícita de cerrarlas o regularlas."
+
+#: 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 ""
+"Varias ideas para mejorar la librería de straming se describen en la web de la librería de streaming."
+
+#: i2p2www/pages/site/about/performance/history.html:2
+msgid "Performance History"
+msgstr "Historia de rendimiento."
+
+#: 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 ""
+"Usando las técnicas de abajo se ha conseguido muchas mejoras en el "
+"rendimiento. Hay más por hacer, vea la web del Rendimiento para probelmas e ideas."
+
+#: i2p2www/pages/site/about/performance/history.html:10
+msgid "Native math"
+msgstr "Matemática nativa."
+
+#: 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 "implementado"
+
+#: 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 ""
+"Cuando examiné el código de I2P, la mayoría del tiempo se gastaba dentro "
+"de una función: java.math. En el modPow de "
+"BigInteger. En vez de intentar mejorar este método, usamos GNU MP - una librería matemática realmente rápida "
+"(con el ensamblador mejorado para varias arquitecturas).  (Editor: vea"
+" NativeBigInteger for faster public key "
+"cryptography)"
+
+#: 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 ""
+"\n"
+"ugha y duck están trabajando en el código de C/JNI, y el código java "
+"actual está  desplegado con los 'ganchos' para cuando esté listo. Los "
+"resultados preliminares se ven fantásticos - ejecutar el ruter con GMP "
+"modPow nativo proporciona un aumento de velocidad del 800% , y la "
+"carga se ha reducido ala mitad. Y esto sólo ha sido en la maquina de un "
+"solo usuario, y las cosas están casi listas para ser empaquetado y "
+"distribuidas."
+
+#: i2p2www/pages/site/about/performance/history.html:32
+msgid "Garlic wrapping a \"reply\" LeaseSet"
+msgstr "Envoltura Garlic par un LeaseSet de \"respuesta\""
+
+#: i2p2www/pages/site/about/performance/history.html:33
+msgid "implemented but needs tuning"
+msgstr "implementado pero necesita mejoras"
+
+#: 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 ""
+"Esta mejora en el algoritmo sólo afectará a las aplicaciones que quieran "
+"que los pares les responda (esto incluye todo lo que use I2PTunnel o la "
+"mini-librería de streaming de mihi):"
+
+#: 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 ""
+"Anteriormente, cuando Alice enviaba un mensaje a Bob, cuando Bob "
+"respondía tenía que hacer una búsqueda en la base de datos de la red - "
+"enviando varias peticiones para obtener el LeaseSet de Alice. Si ya tiene"
+" el LeaseSet de Alice, puede simplemente enviar su respuesta "
+"inmediatamente - esto es (en parte) por qué normalmente toma más tiempo "
+"conectar con alguien por primera vez, pero posteriormente es más rápido. "
+"Actualmente - para todos los clientes - empaquetamos el LeaseSet del "
+"remitente en el mensaje Garlic que es enviado al destinatario, para que "
+"cuando vaya a responder, siempre tendrán el LeaseSet almacenado "
+"localmente - eliminando completamente la necesidad de hacer búsquedas en "
+"la base de datos de la red al responder. Esto ahorra un gran ancho de "
+"banda  al remitente. Si no hiciésemos las búsquedas a menudo, el uso de "
+"ancho de banda disponible global de la red descendería, ya que el "
+"destinatario no necesita hacer la búsqueda en la base de datos de la red."
+
+#: 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 ""
+"Para los LeaseSets no publicados como los \"clientes compartidos\", esta "
+"es la única forma de enviar el LeaseSet a Bob. Desafortunadamente al "
+"construirlo cada vez se añade al menos un 100% de sobre gastos en una"
+" red con mucho ancho de banda, y mucho más en una red con mensajes más "
+"pequeños."
+
+#: 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 ""
+"Los cambios programados para la versión 0.6.2 empaquetará el LeaseSet "
+"sólo cuando sea necesario, al iniciar la conexión o cuando el LeaseSet "
+"cambie. Esto reducirá sustancialmente el gasto delos mensajes I2P."
+
+#: i2p2www/pages/site/about/performance/history.html:66
+msgid "More efficient TCP rejection"
+msgstr "Más eficiencia en las caídas y errores del protocolo TCP"
+
+#: i2p2www/pages/site/about/performance/history.html:68
+#, fuzzy
+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 ""
+"En este momento, todas las conexiones TCP se validan después de pasar a "
+"través del (caro) handshaking Diffie-Hellman al negociar una clave de "
+"sesión privada. Esto significa que si el reloj de alguien esta mal, o su "
+"NAT/cortafuegos no está bien configurado (o usan una versión incompatible"
+" del ruter), crearán (aunque no constantemente, gracias a la shitlist) un"
+" derroche innecesario y caro en cifrados con todos los pares que conozca."
+" Mientras que queremos seguir usando verificación/validación en los "
+"cifrados, queremos actualizar el protocolo para seguir verificando "
+"algunos de ellos primero, y así poder rechazarlos limpiamente si gastar "
+"mucha CPU u otros recursos."
+
+#: i2p2www/pages/site/about/performance/history.html:81
+msgid "Adjust the tunnel testing"
+msgstr "Ajustar las pruebas de túneles"
+
+#: 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 ""
+"En vez de usar el esquema bastante aleatorio que tenemos ahora, "
+"deberíamos usar un algoritmo más consciente del contexto para probar los "
+"túneles. Por ejemplo, si ya conocemos sus datos de validación "
+"correctamente, no hay necesidad de probarlo, mientras que si no hemos "
+"visto ningún dato recientemente, quizás valga la pena enviarle algunos "
+"datos. Esto reducirá el parón en los túneles debido a un número de "
+"mensajes excesivo, a la vez que mejorará la velocidad en la detección de "
+"los túneles fallidos."
+
+#: i2p2www/pages/site/about/performance/history.html:92
+msgid "Persistent Tunnel / Lease Selection"
+msgstr "Túneles persistentes / Selección del LeaseSet"
+
+#: 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 ""
+"La selección del túnel de salida se implementó en la versión 0.6.1.30, la"
+" selección del túnel de entrada se implementó en la versión 0.6.2."
+
+#: 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 ""
+"Seleccionar los túneles y leases aleatoriamente para cada mensaje crea un"
+" gran problema con el envío de mensajes desordenados, lo cual evita que "
+"la librería de streaming pueda aumentar el tamaño de su 'ventana' tanto "
+"como podría. Al persistir con las mismas selecciones para una conexión "
+"determinada, la velocidad de transferencia es mucho mayor."
+
+#: i2p2www/pages/site/about/performance/history.html:104
+msgid "Compress some data structures"
+msgstr "Comprimiendo algunas estructuras de datos"
+
+#: 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 ""
+"Los mensajes I2NP y los datos que contiene están ya definidos en una "
+"estructura bastante compacta, aunque un atributo de la estructura del "
+"RouterInfo no lo está - \"options\" está en texto ASCII plano en el "
+"formato nombre = valor. Ahora mismo, se está rellenado con estadísticas "
+"publicadas - alrededor de 3300 bytes por par. Implementar la compresión "
+"GZip, lo cual es trivial, ahorraría 1/3 de su tamaño, y cuando se "
+"considera las veces que se pasan las estructuras RouterInfo a través de "
+"la red, es un gran ahorro - cada vez que un ruter pregunta a otro por una"
+" entrada en la netDb que el par no posee, envía de vuelta de 3-10 "
+"estructuras RouterInfo."
+
+#: i2p2www/pages/site/about/performance/history.html:117
+msgid "Update the ministreaming protocol"
+msgstr "Actualizar el protocolo ministreaming"
+
+#: i2p2www/pages/site/about/performance/history.html:118
+msgid "replaced by full streaming protocol"
+msgstr "reemplazar por un protocolo full streaming"
+
+#: 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 ""
+"Actualmente la librería ministream de mihi tiene un protocolo de "
+"negociación bastante simple - Alice envía a Bob un mensaje SYN, Bob "
+"responde con un ACK, entonces Alice y Bob comparten información, hasta "
+"que uno le envíe a otro un mensaje CLOSE. Para conexiones de larga "
+"duración (por ejemplo a un servidor IRC), esta sobrecarga es "
+"despreciable, pero para situaciones de una sola repuesta (Una petición "
+"HTTP por ejemplo), es más del doble de los mensajes necesarios. Si, de "
+"otra forma, Alice hubiese adjuntado su primer payload con el mensaje SYN,"
+" y Bob hubiese adjuntado su primera respuesta en el ACK - e incluso "
+"incluyendo la etiqueta CLOSE - los envíos transitorios como las respuetas"
+" HTTP podrían reducirse a un par de mensajes, en vez del "
+"SYN+ACK+petición+respuesta+CLOSE."
+
+#: i2p2www/pages/site/about/performance/history.html:132
+msgid "Implement full streaming protocol"
+msgstr "Implementar el protocolo full streaming"
+
+#: 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 ""
+"El protocolo ministream toma ventaja de una decisión de diseño pobre en "
+"el protocolo del cliente de I2P (I2CP) - al exponer el "
+"\"mode=GUARANTEED\", permitiendo lo que de otra forma sería poco fiable, "
+"usar un protocolo como si fiable basado en mensajes para operaciones de "
+"bloqueo. (en el fondo, todavía es poco fiable y basado en mensajes, con "
+"el ruter proporcionando garantías de envío al adjuntar un mensaje \"ACK\""
+" en al payload,  con lo cual una vez que los datos han llegado al "
+"objetivo, el mensaje ACK es envíado de vuelta a nosotros [a través de "
+"túneles, por supuesto])."
+
+#: 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 ""
+"Como ya he dicho, permitir que el I2PTunnel (y "
+"la librería ministream) usen esta ruta es lo mejor que se pudo hacer, "
+"pero hay mecanismos más eficientes. Cuando eliminamos la funcionalidad "
+"\"mode=GUARANTEED\", estamos esencialmente dejando un I2CP que parece una"
+" capa IP anónima, y por eso, podremos ser capaces de implementar la "
+"librería de streaming para obtener ventajas de las experiencias de diseño"
+" de la capa TCP - ACKs selectivos, detección de congestión, etc."
+
+#: i2p2www/pages/site/about/performance/index.html:2
+msgid "Performance"
+msgstr "Rendimiento"
+
+#: 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 ""
+"¿Cómo funciona I2P, por qué es lento, y por qué no utiliza todo el ancho "
+"de banda?"
+
+#: 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 ""
+"Probablemente una de las preguntas más frecuentes es ¿cómo de rápido es "
+"I2P?, y parece que a nadie le gusta la respuesta - \"depende\". Después "
+"de probar I2P, la siguiente cosa que preguntan es ¿será más rápido?, y la"
+" respuesta a eso es un enfático sí."
+
+#: 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 ""
+"I2P es un red totalmente dinámica. Cada cliente es conocido por otros "
+"nodos y prueba los nodos conocidos localmente para comprobar su "
+"accesibilidad y su capacidad. Sólo los nodos accesibles y capaces son "
+"guardados en la NetDB local (Esto normalmente es sólo una parte de la "
+"red, sobre 500-1000). Cuando I2P construye túneles selecciona los mejores"
+" recursos de esta fuente. Por ejemplo, sólo unos 20-50 nodos están "
+"disponibles para construir túneles. Ya que las pruebas se hacen cada "
+"minuto la fuente de los nodos usados cambia cada minuto. Cada nodo I2P "
+"conoce una parte de la red total, haciendo que cada ruter tenga una lista"
+" diferente de nodos I2P para ser usados como túneles. Incluso si dos "
+"ruters tienen la misma subred de nodos conocidos las pruebas de "
+"accesibilidad y capacidad mostrarán diferentes resultados, ya que cuando "
+"un ruter hace las pruebas otros ruters pueden estar bajo carga, pero "
+"estar libre cuando es un segundo ruter el que hace las pruebas."
+
+#: 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 ""
+"El texto anterior explica porque cada nodo I2P usa diferentes nodos para "
+"construir sus túneles. Porque cada nodo I2P tienen una latencia y ancho "
+"de banda diferente, los túneles ( que se construyen con estos nodos) "
+"tienen valores diferentes de latencia y ancho de banda. Y ya que cada "
+"nodo I2P tiene diferentes nodos construidos, no hay dos nodos I2P con la "
+"misma configuración de túneles."
+
+#: 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 ""
+"Un servidor/cliente se conoce como \"destinación\"  y cada destinación "
+"tiene al menos un túnel de entrada y otro de salida. Por defecto son 3 "
+"saltos por túnel. Esto suman 12 saltos (osea 12 diferentes nodos I2P) "
+"para una ida y vuelta completa cliente-servidor-cliente."
+
+#: 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 ""
+"Cada paquete de datos es enviado a través de otros 6 nodos I2P hasta que "
+"alcanza el servidor:"
+
+#: i2p2www/pages/site/about/performance/index.html:40
+msgid "and on way back 6 different I2P nodes:"
+msgstr "y de vuelta por 6 nodos I2P diferentes:"
+
+#: 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 ""
+"Como la mayoría del tráfico I2P (www, torrent, ...) necesita paquetes ack"
+" hasta que la nueva información es enviada, necesita esperar hasta que un"
+" paquete ack regrese del servidor. Al final: envía información, espera "
+"por ack, envía mas información, espera por ack... Y ya que el RTT "
+"(RoundTripTime) añade latencia por cada nodo individual I2P y por cada "
+"conexión de esta ida y vuelta, normalmente tarda de 1-3 segundos hasta "
+"que un paquete ack regresa al cliente. Además el funcionamiento interno "
+"del transporte de TCP y de I2P hacen que un paquete de información tenga "
+"un tamaño limitado y no pueda ser tan grande como desearíamos que fuese. "
+"Estas condiciones unidas crean un límite de ancho de banda por túnel de "
+"20-50 kbyte/sec. Pero, si SÓLO un salto del túnel tiene solamente 5 "
+"kb/sec de ancho de banda para usar, el túnel completo estará limitado a 5"
+" kb/sec, independientemente de las latencia y otras limitaciones."
+
+#: 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 ""
+"Debido al cifrado usado y otras configuraciones de I2P (como se "
+"construyen los túneles, latencia, ...) se utiliza bastante tiempo de la "
+"CPU para crear un túnel. Esto es por lo que una destinación solo tiene "
+"permitido un máximo de 6 túneles de  de entrada y 6 de salida para enviar"
+" información. Con un máximo de 50 kb/sec por túnel una destinación podría"
+" usar aproximadamente 300 kb/sec (en realidad podría ser más si se "
+"utilizan túneles más cortos con poco o ningún anonimato). Los túneles "
+"usados son eliminados cada 10 minutos y se crean unos nuevos. Estos "
+"cambios en los túneles (y a veces los clientes que apagan de golpe usando"
+" \"apagar inmediatamente\" o por caídas de corriente) a veces rompen los "
+"túneles y las conexiones, como se puede ver en las pérdidas de conexiones"
+" en el IRC2P (ping timeout) o cuando se está usando eepget."
+
+#: 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 ""
+"Con un número limitado de destinaciones y un número limitado de túneles "
+"por destinación, un nodo I2P sólo utiliza un número limitado de túneles a"
+" través de otros nodos de I2P. Por ejemplo, si en el ejemplo de arriba un"
+" nodo I2P es \"hop1\", sólo tendríamos 1 túnel participante originado en "
+"el cliente. Si sumamos toda la red I2P, sólo un número limitado de "
+"túneles participantes pueden ser construidos con una cantidad limitada de"
+" ancho de banda. Si uno distribuye todo ese número limitado entre el "
+"número de nodos I2P, sólo hay disponible una fracción del ancho de "
+"banca/capacidad disponible para el uso."
+
+#: 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 ""
+"Para permanecer anónimos un ruter no debería usarse por toda la red para "
+"construir túneles, si un solo ruter funciona como túnel para TODOS los "
+"nodos de I2P se convierte en el centro de un problema, así como el punto "
+"central para obtener IPs e información de los clientes. Esto no es bueno."
+" I2P intenta repartir la carga a través de muchos nodos I2P justo por "
+"esta razón."
+
+#: 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 ""
+"Otro punto a tener en cuenta es la red mesh completa. Cada conexión "
+"salto-a-salto utiliza una conexión TCP o UDP en los nodos de I2P. Con "
+"1000 conexiones uno ve 1000 conexiones TCP. Eso es bastante y algunos "
+"ruters domésticos o de oficina (DSL, cable...) sólo permiten un cierto "
+"número de conexiones ( o simplemente se vuelven locos si se usa un número"
+" mayor de X conexiones). I2P intenta limitar esas conexiones por debajo "
+"de 1500 para UDP y TCP. Esto limita también la cantidad de tráfico "
+"enrutado a través de su nodo I2P."
+
+#: 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 ""
+"En resumen, I2P es muy complejo y no hay una forma fácil de determinar "
+"con precisión por qué su nodo no se utiliza. Si su ruter es accesible y "
+"tiene mas de 128 kbyte/sec de ancho de banda compartido y está accesible "
+"24/7, debería ser usado después de algún tiempo de tener tráfico "
+"participante. Si no esta activo siempre, las pruebas de otros nodos sobre"
+" su nodo I2P le dirá: no está accesible. Esto bloquea su nodo por al "
+"menos 24h para los otros nodos. Por lo cual los otros nodos que han "
+"testado su nodo cuando estaba caído no utilizarán su nodo para construir "
+"túneles durante 24h. Esto es por lo que su tráfico será menor después de "
+"un reinicio/apagado por lo menos durante 24h."
+
+#: 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 ""
+"Además: otros nodos I2P necesitan conocer su ruter I2P para probar la "
+"accesibilidad y capacidad. Toma tiempo que otros nodos lleguen a conocer "
+"su nodo. Será más rápido si utiliza I2P y crea más túneles, por ejemplo "
+"usando torrents o webs i2p durante algún tiempo."
+
+#: i2p2www/pages/site/about/performance/index.html:99
+msgid "Performance Improvements"
+msgstr "Mejoras en el rendimiento"
+
+#: i2p2www/pages/site/about/performance/index.html:101
+#, python-format
+msgid ""
+"For possible future performance improvements see\n"
+"Future Performance Improvements."
+msgstr ""
+"Para futuras mejoras en el rendimiento vea mejoras"
+" futuras en el rendimiento."
+
diff --git a/i2p2www/translations/es/LC_MESSAGES/blog.po b/i2p2www/translations/es/LC_MESSAGES/blog.po
new file mode 100644
index 00000000..fcc2e19e
--- /dev/null
+++ b/i2p2www/translations/es/LC_MESSAGES/blog.po
@@ -0,0 +1,1844 @@
+# Spanish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Fito Jayme , 2013
+# Daniel Mustieles , 2013
+# m1xxy , 2011
+# olivertrash , 2013
+# strel, 2013
+# trolly, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-12 06:16+0000\n"
+"PO-Revision-Date: 2013-12-16 22:51+0000\n"
+"Last-Translator: strel\n"
+"Language-Team: Spanish "
+"(http://www.transifex.com/projects/p/I2P/language/es/)\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/blog/2011/10/11/0.8.9-Release.rst:24
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:25
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:12
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:12
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:17
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:16
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:16
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:26
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:19
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:19
+msgid "Files are available on the `download page`_."
+msgstr "Los archivos están disponibles en la `página de descargas`_."
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:28
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:15
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:29
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:16
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:16
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:21
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:20
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:20
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:30
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:23
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:23
+msgid "`download page`"
+msgstr "`Página de Descargas`"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:30
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:17
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:31
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:18
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:19
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:18
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:22
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:22
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:32
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:25
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:79
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:45
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:13
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:101
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:26
+msgid "RELEASE DETAILS"
+msgstr "DETALLES DEL LANZAMIENTO"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:32
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:19
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:33
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:40
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:50
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:24
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:24
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:34
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:103
+msgid "Major Changes"
+msgstr "Cambios más importantes"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:44
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:24
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:43
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:55
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:47
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:58
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:43
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:32
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:30
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:39
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:81
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:54
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:112
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:34
+msgid "Bug Fixes"
+msgstr "Correcciones de errores"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:54
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:30
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:47
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:69
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:63
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:68
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:54
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:41
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:36
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:51
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:43
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:94
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:63
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:19
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:118
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:52
+msgid "Other"
+msgstr "Otro"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:73
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:36
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:51
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:82
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:75
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:96
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:76
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:52
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:56
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:67
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:56
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:110
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:79
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:30
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:129
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:27
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:76
+msgid "SHA256 Checksums:"
+msgstr "Sumas de comprobación SHA256:"
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39
+msgid "Major changes"
+msgstr "Cambios mayores"
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47
+msgid "Wrapper Update"
+msgstr "Actualización del Wrapper"
+
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:23
+msgid "Update Info"
+msgstr "Información de la actualización"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2
+msgid "0.9.2 Release"
+msgstr "Versión 0.9.2"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9
+msgid ""
+"0.9.2 includes extensive low-level changes to improve the performance and"
+" efficiency of the router. We have updated our UPnP library, to hopefully"
+" make UPnP work for more people. I2PSnark now has DHT support, but it is "
+"not yet enabled by default, as we plan to do more testing during the "
+"upcoming 0.9.3 development cycle."
+msgstr ""
+"0.9.2 incluye muchos cambios de bajo nivel para la mejora y eficiencia "
+"del ruter. Hemos actualizado la librería UPnP, para hacer que UPnP "
+"funcione para mas gente. I2PSnark ahora soporta DHT, pero no está activo "
+"por defecto, ya que tenemos planeado hacer más pruebas durante la el "
+"próximo ciclo de desarrollo de 0.9.3"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12
+msgid ""
+"As usual, there's also lots of bug fixes in this release, so updating is "
+"recommended."
+msgstr ""
+"Como es habitual, hay muchos cambios y arreglos en esta versión, "
+"recomendamos actualizar."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26
+msgid ""
+"SSU: Fix several problems in our UDP transport, to improve efficiency and"
+" reliability for connection setup. Also improve defenses against various "
+"types of bad input."
+msgstr ""
+"SSU: Arreglados varios problemas en el trasporte UDP, para mejorar la "
+"eficiencia y la seguridad en la conexión. También se han mejorado las "
+"defensas contra varios tipos de ataques por entradas malformadas."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27
+msgid ""
+"UPnP: Updated our library to fix several issues, should work for more "
+"routers now"
+msgstr ""
+"UPnP: Librería actualizada para arreglar varios errores, ahora debería "
+"funcionar en más ruters."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28
+msgid ""
+"Transport: Improve performance in both our TCP and UDP transports, to "
+"benefit high-bandwidth routers"
+msgstr ""
+"Transporte; Mejora del rendimiento en TCP y UDP, para aprovechar los "
+"ruters con mucho ancho de banda."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29
+msgid ""
+"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered "
+"are now much more flexible, which should lessen protocol overhead and "
+"reduce stalls caused by dropped tags."
+msgstr ""
+"Cifrado: Los umbrales y valores de las etiquetas de sesión ElGamal/AES "
+"ahora son mucho más flexibles, lo que debería hacer que hayan menos "
+"sobrecarga y reduzca los rodeos causados por las etiquetas caídas."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30
+msgid ""
+"I2PSnark: Add DHT support, not yet enabled by default, will do further "
+"testing and plan to enable by default in 0.9.3."
+msgstr ""
+"I2PSnark: Añadido soporte para DHT, no activado por defecto todavía, se "
+"harán más pruebas y se activará por defecto en la versión 0.9.3."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34
+msgid ""
+"Fix various issues affecting memory usage and performance on high-"
+"bandwidth routers"
+msgstr ""
+"Arreglados varios problemas que afectaban al uso de memoria y al "
+"rendimiento de los ruters con un gran ancho de banda."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35
+msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN"
+msgstr ""
+"Arreglado el problema en UDP para los ruters que usan una conexión MTU "
+"reducida, por ejemplo VPN"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36
+msgid "Fix i2psnark bug that prevented a completion announcement to the tracker"
+msgstr ""
+"Arreglado el problema de i2psnark que evitaba la finalización del anuncio"
+" en los trackers"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37
+msgid "Fix a lock contention problem in i2ptunnel"
+msgstr "Arreglado un problema de contención de bloqueos en el i2ptunnel"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38
+msgid "Fix some OSX installation issues"
+msgstr "Corregidos algunos problemas de instalación en OSX"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39
+msgid "Remove uses of direct byte buffers that may have been leaking"
+msgstr ""
+"Eliminado el uso de byte buffers directos que podrían haber estado "
+"filtrando información"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43
+msgid "Reduce overhead in network messages"
+msgstr "Reducida la sobrecarga en los mensajes de la red"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44
+msgid "Add \"universal\" theme support"
+msgstr "Añadido soporte para el tema \"universal\""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45
+msgid "Theme updates"
+msgstr "Actualizaciones en los temas"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46
+msgid "Add a jbigi library for Raspberry Pi"
+msgstr "Añadida una biblioteca jbigi para Raspberry Pi"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47
+msgid "New Scala unit test framework"
+msgstr "Nuevo sistema de unit test Scala"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48
+msgid "Translation updates for Czech, Dutch, German, and Greek"
+msgstr "Actualizaciones de las traducciones al checo, holandés, alemán y griego"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49
+msgid "Update wrapper to 3.5.15 (new installs and PPA only)"
+msgstr ""
+"Actualización del wrapper a la versión 3.5.15 (sólo para nuevas "
+"instalaciones y PPA)"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:77
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:127
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:74
+msgid "Update GeoIP data (new installs and PPA only)"
+msgstr "Actualizar datos de geolocalización IP (Sólo PPA y nuevas instalaciones)"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:2
+msgid "0.9.3 Release"
+msgstr "Versión 0.9.3"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9
+msgid ""
+"0.9.3 includes extensive low-level changes to the queueing of messages in"
+" the router.  We implement the CoDel Active Queue Management (AQM) "
+"algorithm.  We also unify the queueing and priority mechanisms in the "
+"transports to aid diagnosis and reduce network latency.  Work continues "
+"on fixing UDP transport bugs and making UDP more resistant to attacks.  "
+"There are more changes to improve the performance of the router and "
+"reduce its memory usage.  Also, we enable i2psnark's DHT support, "
+"introduced last release, by default."
+msgstr ""
+"0.9.3 incluye muchos arreglos de bajo nivel en la cola de mensajes en el "
+"ruter. Hemos implementado el algoritmo CoDel Active Queue Management "
+"(AQM). También hemos unificado los mecanismos de prioridades y colas en "
+"los transportes para ayudar al diagnóstico y reducir la latencia de la "
+"red. El trabajo continua arreglando el transporte UDP haciéndolo mas "
+"resistente a los ataques. Hay mas cambios para mejorar el rendimiento del"
+" ruter y reducir el uso de memoria. Además, hemos habilitado por defecto "
+"el suporte, introducido en la versión anterior, para DHT en i2psnark."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26
+msgid "Active Queue Management"
+msgstr "Gestión de cola activa"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:27
+msgid "Priority queues"
+msgstr "Listas de prioridades."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28
+msgid "I2PSnark DHT: Several bug fixes, enable by default."
+msgstr "DHT de I2PSnark: Solución de varios errores, activo por defecto."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32
+msgid ""
+"Several SSU fixes including memory leak, and better handling of routers "
+"behind firewalls that change UDP ports; additional defenses for malicious"
+" packets."
+msgstr ""
+"Varios arreglos en el SSU incluyendo la fuga de memoria, y mejor manejo "
+"de de los ruters detrás de cortafuegos que han cambiado sus puertos UDP; "
+"defensa extra contra paquetes maliciosos."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33
+msgid "Fix piece selection (rarest-first) bugs in i2psnark"
+msgstr ""
+"Solucionar fallos en la selección de porciones (las más raras primero) en"
+" i2psnark"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34
+msgid "Fix bug causing multiple browsers to open at startup"
+msgstr ""
+"Arreglo del error que causaba que se abriesen varios navegadores al "
+"iniciar."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38
+msgid "Improvements in caching"
+msgstr "Mejoras en almacenamiento en caché"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39
+msgid "Several synchronization fixes and lock contention reduction"
+msgstr ""
+"Varios arreglos en la sincronización y reducción de la contención del "
+"bloqueo"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40
+msgid "Major reduction in SSU buffers memory use"
+msgstr "Gran reducción en el uso de buffers de memoria en SSU"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41
+msgid ""
+"Fix streaming connection timeout back to 1 minute, was inadvertently "
+"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was"
+" unlimited"
+msgstr ""
+"Revertir tiempo máximo de respuesta de la conexión a 1 minuto, fue "
+"cambiado inadvertidamente a 5 minutos; establecer el tiempo máximo de "
+"lectura del servidor i2ptunnel, era ilimitado."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42
+msgid "Improved defenses in i2ptunnel for \"darkloris\""
+msgstr "Defensas mejoradas en i2ptunnel para \"darkloris\""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:43
+msgid "More validation at torrent creation in i2psnark"
+msgstr "Más verificación a la creación del torrent en i2psnark"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44
+msgid "Several parameter changes in SSU to improve throughput"
+msgstr "Varios cambios de parámetro en SSU para mejorar el rendimiento"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45
+msgid ""
+"New event log for major events including restarts; show multiple restart "
+"lines on graphs"
+msgstr ""
+"Nuevo registro de eventos para eventos principales incluyendo reinicios; "
+"muestra múltiples líneas de reinicio en los gráficos."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46
+msgid "Remove duplicate messages from logs"
+msgstr "Eliminar mensajes duplicados de los registros"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47
+msgid "Don't respond to blocked streaming connections with a reset, just drop"
+msgstr ""
+"No responder a conexiones de flujos multimedia (streaming) bloqueadas con"
+" un restablecimiento, simplemente desistir."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48
+msgid "Remove all uses of inefficient SimpleTimer"
+msgstr "Eliminar todos los usos del inficiente SimpleTimer"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49
+msgid "More checks for valid IPs and ports entered in console"
+msgstr "Más verificaciones de IPs y puertos válidos introducidos en la consola"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50
+msgid "Fix bug that wasted a lot of entropy"
+msgstr "Solucionar fallo que desperdiciaba mucha entropía"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51
+msgid "Translation updates: Italian, Portuguese, Spanish, Swedish"
+msgstr "Actualizaciones de traducciones: italiano, portugués, español y sueco"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52
+msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5"
+msgstr ""
+"Añadir configuración que NO es del tipo NIO a Jetty.xml, recomendado a "
+"partir de Java 5"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2
+msgid "0.9.4 Release"
+msgstr "Versión 0.9.4"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9
+msgid ""
+"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, "
+"that was reducing network performance and reliability. It also includes "
+"major changes in the in-network update system, and adds the capability to"
+" update via in-network torrents."
+msgstr ""
+"0.9.4 incluye un arreglo de la capacidad de la red, introducido en 0.9.2,"
+" que estaba reduciendo el rendimiento y estabilidad de la red. Además "
+"incluye cambios en el sistema de actualización de la red, y añade la "
+"capacidad de actualizar a través de torrents de dentro de la red I2P."
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13
+msgid ""
+"We fixed several bugs in the i2psnark DHT implementation that was "
+"introduced\n"
+"last release. For those of you using console or http proxy passwords,\n"
+"we converted to the more-secure digest method and improved the security "
+"for console forms."
+msgstr ""
+"Hemos arreglado varios errores en los cambios introducidos de la última "
+"versión liberada.\n"
+"Para todos quienes usáis consola o proxy's http con contraseña, hemos "
+"aumentado y mejorado la seguridad para los formularios de consola"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19
+msgid ""
+"For those of you already running development builds, your router should "
+"automatically\n"
+"update to 0.9.4-0 using the new in-network torrent facility.\n"
+"For those running 0.9.3-0, you will update normally using in-network "
+"HTTP, and\n"
+"we will have more information for you when we release 0.9.5."
+msgstr ""
+"Para aquellos que todavía ejecutan versiones de desarrollo, su ruter "
+"debería actualizarse automáticamente a la versión 0.9.4-0 usando la nueva"
+" vía a través de torrent. Para aquellos usando la versión 0.9.3-0, se "
+"actualizará normalmente usado HTTP, y tendremos más información sobre el "
+"tema cuando liberemos la versión 0.9.5."
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36
+msgid ""
+"Big rework of the update system; Preliminary support for updates via "
+"i2psnark"
+msgstr ""
+"Gran trabajo supervisado para la actualización del sistema; soporte "
+"preliminar para actualizaciones vía i2psnark"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37
+msgid "Add per-destination outbound priorities"
+msgstr "Añadir"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41
+msgid ""
+"Fix major bug that reduced SSU connection limits which reduced tunnel "
+"build success rates"
+msgstr ""
+"Arreglado un error grave para reducir el límite de conexión SSU, el cual "
+"reducía las posibilidades de éxito al crear un tunel"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42
+msgid "Fix bug with external I2CP that prevented some external apps from working"
+msgstr ""
+"Corregido un error del panel de control i2P EXTERNO que impedía el "
+"funcionamiento de aplicaciones externas"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43
+msgid "Fixed several bugs in i2psnark DHT"
+msgstr "Corregidos varios errorres en i2psnark DHT"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44
+msgid "Fixed bug in i2psnark PEX that inflated peer counts"
+msgstr "Corregido un error en ip2snark PEX que descuadraba los pares de cuentas"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45
+msgid "Handle dropped I2CP messages better"
+msgstr "Manejar mejor los mensajes I2CP descartados"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46
+msgid "Reduce overhead of I2CP messages"
+msgstr "Reducir la sobrecarga de mensajes del panel de control I2P (I2CP)"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47
+msgid "Enforce max size in transport outbound message queues"
+msgstr ""
+"Se fija el tamaño máximo para el transporte de las colas de los mensajes "
+"de salida"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48
+msgid "Fixes for Windows eepget.bat (new installs and PPA only)"
+msgstr ""
+"Correcciones para el archivo de Windows \"eepget.bat\" (sólo PPA y nuevas"
+" instalaciones)"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49
+msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU"
+msgstr "Arreglado un error que deshechaba los mensajes de 512 bytes en SSU"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53
+msgid ""
+"More performance improvements, memory reduction, and object churn "
+"reduction"
+msgstr ""
+"Otras optimizaciones de rendimiento, reducción de memoria y de los "
+"objetos CHURN "
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54
+msgid "Better detection of network disconnections"
+msgstr "Mejor detección de caídas y desconexión de red"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55
+msgid "Further improvements in the SSU transport"
+msgstr "Mejora en el transporte SSU"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56
+msgid "Add console password form"
+msgstr "Añadido formulario de contraseña en consola"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57
+msgid ""
+"Convert http proxy and console from basic to digest authentication for "
+"added security"
+msgstr ""
+"Se ha cambiado el proxy http y la consola para aceptar autenticación y se"
+" ha añadido más seguridad."
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58
+msgid ""
+"Improved verification of console form submissions, using jsp sessions. "
+"Cookies may now be required on forms, except when the console password is"
+" enabled"
+msgstr ""
+"Mejorada la verificación de los formularios de la consola, usando "
+"sesiones jsp. Puede ser que ahora los formularios requieran cookies, "
+"excepto cuando la contraseña de la consola esté activada."
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59
+msgid ""
+"Initial work on new interfaces to manage applications started via "
+"clients.config"
+msgstr ""
+"TRabajo inicial en nuevos interfaces pata manejar las palicaciones que se"
+" arranquen vía "
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60
+msgid "Increase minimum peer port to 1024"
+msgstr "Aumentar el número de puerto más bajo a 1024"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61
+msgid "Increase granularity of bandwidth limiter for smoother transmissions"
+msgstr ""
+"Aumentada el nivel de detalle del limitador del ancho de banda para "
+"obtener conexiones más suaves."
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62
+msgid ""
+"Translation updates: Chinese, French, German, Italian, Polish, "
+"Portuguese, Swedish, and Ukrainian"
+msgstr ""
+"Traducciones actualizadas: chino, francés, alemán, italiano, polaco, "
+"portugués, sueco y ucraniano"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64
+msgid "Update wrapper to 3.5.16 (new installs and PPA only)"
+msgstr "Wrapper actualizado a 3.5.16 (sólo en instalaciones nuevas y PPA)"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65
+msgid "New ARMv6 wrapper for Raspberry Pi"
+msgstr "Nuevo wrapper ARMv6 para el "
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:2
+msgid "0.9.5 Release"
+msgstr "Versión 0.9.5"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9
+msgid ""
+"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities"
+" that are being investigated by researchers at UCSB. We continue to work "
+"with them on additional improvements. This is a good opportunity to "
+"remind the community that while our network continues to grow rapidly, it"
+" is still relatively small. There may be multiple weaknesses or bugs that"
+" could compromise your anonymity. Help us grow the network by spreading "
+"the word and contributing where you can."
+msgstr ""
+"La versión 0.9.5 incluye arreglos de errores y defensas para algunos "
+"problemas y vulnerabilidades que están siendo estudiadas por "
+"investigadores en el UCSB. Seguimos trabajando con ellos en algunas "
+"mejoras. Esta es una buena oportunidad para recordar a la comunidad, que "
+"aunque la red crece rápido, todavía es relativamente pequeña. Podrían "
+"haber múltiples debilidades y errores que podrían comprometer su "
+"anonimato. Ayúdenos a hacer crecer la red difundiendo la palabra y "
+"contribuyendo donde pueda."
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13
+#, python-format
+msgid ""
+"In this upgrade cycle, a random 1% of routers, (plus all routers running "
+"a\n"
+"development build) will attempt to update via the experimental in-network"
+" bittorrent\n"
+"with i2psnark. If this doesn't work, it should fall back to standard in-"
+"network HTTP update."
+msgstr ""
+"En esta versión, un 1% o de ruters, aleatoriamente, (más todos los ruters"
+" que ejecuten la versión de desarrollo) intentarán actualizarse a través "
+"de torrent con i2psnark. Si no funciona, debería poder usar "
+"automáticamente el método HTTP tradicional."
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27
+msgid "Defenses and Bug Fixes"
+msgstr "Defensa y arreglo de errores."
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29
+msgid "Fix router bug causing lockup when using iMule"
+msgstr "Arreglado el problema del bloqueo del ruter cuando se usaba iMule."
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30
+msgid "Recognize, handle, reject duplicate tunnel IDs"
+msgstr "Reconocimiento, manejo y rechazo de IDs de túneles duplicados."
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31
+msgid "Fix changing of the log file name"
+msgstr "Corregido el cambio de nombre del archivo de registro"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32
+msgid "Prevent hashcode attack in session tags"
+msgstr "Prevención contra el ataque hashcode en las etiquetas de sesión"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33
+msgid "Add build request throttler based on previous hop"
+msgstr ""
+"Añadido el acelerador de construcción de peticiones basado en el salto "
+"anterior"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34
+msgid "Limit concurrent next-hop lookups"
+msgstr "Limitar las búsquedas concurrentes del siguiente salto"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35
+msgid "Catch exceptions storing nonces in console"
+msgstr "Capturar las excepciones almacenando nonces en la consola"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36
+msgid "Fix saving graph settings in console"
+msgstr "Arreglado el guardar la configuración gráfica en la consola"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37
+msgid "Fix eepget generation of URLs when not proxied"
+msgstr "Arreglada la creación de URLs eepget sin proxy"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38
+msgid ""
+"Encrypt database lookup messages end-to-end when sent through exploratory"
+" tunnels"
+msgstr ""
+"Cifrado delos mensajes fin-a-fin de búsqueda en la base de datos cuando "
+"son enviados a través de túneles exploratorios."
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39
+msgid "Don't use multiple floodfills from the same /16 in a query"
+msgstr ""
+"Cuando se consulta no se usan múltiples foodfills de la misma /16 , zona "
+"de red."
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40
+msgid "Randomize delay before verifying floodfill store"
+msgstr "Se aleatoriza el retardo antes de verificar el almacenamiento floodfill"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41
+msgid "Increase number of floodfills"
+msgstr "Aumento en el número de floodfills"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:45
+msgid "Improve support for mobile browsers"
+msgstr "Mejora del soporte para navegadores en móviles."
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46
+msgid "Partial defenses for UCSB attacks"
+msgstr "Defensa parcial contra los ataques UCSB"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47
+msgid "Add announce list support to i2psnark"
+msgstr "Se ha añadido suporte para lista de anuncios en i2psnark "
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48
+msgid "Jetty: upgrade Apache Tomcat to 6.0.36"
+msgstr "Jetty: actualización a Apache Tomcat versión 6.0.36"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49
+msgid "Split router info files into multiple subdirectories"
+msgstr "Se dividen los archivos de información del ruter en varios subdirectorios."
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50
+msgid "Add IP to hostname mapping option in SOCKS"
+msgstr "Se añade la IP a la opción hostname en SOCKS"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51
+msgid "Improve PRNG seeding"
+msgstr "Mejora en el sembrado de PRNG"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52
+msgid ""
+"Translation updates: French, German, Hungarian, Italian, Norwegian, "
+"Polish, Portuguese, Russian, Swedish"
+msgstr ""
+"Actualización de las traducciones: Francés, alemán, húngaro, italiano, "
+"noruego, polaco, portugués, ruso y sueco."
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54
+msgid "Update wrapper to 3.5.17 (new installs and PPA only)"
+msgstr "Actualizado el wrapper a 3.5.17 (sólo para instalaciones nuevas y PPA)"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:2
+msgid "0.9.6 Release"
+msgstr "Versión 0.9.6"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:7
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9
+msgid ""
+"0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to "
+"Jetty 7.6.10 (2013-03-12). See below for important information on the "
+"Jetty update. The Jetty 7 series is actively maintained and we plan to "
+"stay current with it in future I2P releases."
+msgstr ""
+"La versión 0.9.6 incluye varios arreglos y una actualización de Jetty "
+"6.1.26 (2010-11-10) a Jetty 7.6.10 (2013-03-12). Vea más abajo para ver "
+"información importante sobre esta actualización de Jetty. Las versiones 7"
+" de Jetty se desarrollan activamente y planeamos mantenerlas actualizadas"
+" con las versiones futuras de I2P."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13
+msgid ""
+"Most users will update via HTTP. Those running development builds will "
+"attempt to update via the\n"
+"experimental in-network bittorrent with i2psnark. We've fixed some bugs "
+"that will enable more users\n"
+"to update via torrent in the 0.9.7 update cycle."
+msgstr ""
+"La mayoría de los usuarios se actualizarán por HTTP. Aqueyos que utilicen"
+" versiones en desarrollo intentarán actualizarse a través del método "
+"experimental bittorrent con i2psnark. Arreglamos alguno errores que "
+"premitirán que más usuarios puedan actualizarse via torrent en las "
+"versiones 0.9.7."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25
+msgid "Important fix for Windows Eepsites, first install 0.9.5 only"
+msgstr ""
+"Arreglo importante para las eepsites en Windows, sólo para primeras "
+"instalaciones de 0.9.5"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27
+msgid ""
+"If you first installed I2P with version 0.9.5, on Windows only, we "
+"recommend that you follow the\n"
+"following instructions to fix your eepsite location **before** you update"
+" to 0.9.6.\n"
+"Only original installations of 0.9.5-0 on Windows are affected by this "
+"issue. If your router version\n"
+"is 0.9.5-0-win1, you already have the fix and need not take any action."
+msgstr ""
+"Si instaló por primera vez I2P con la versión 0.9.5, sólo en Windows, "
+"recomendamos que siga las instrucciones para arreglar la localización de "
+"su eepsite **antes** de actualizar a 0.9.6. Sólo las instalaciones "
+"originales de 0.9.5-0 en Windows están afectadas por este error. Si su "
+"versión del ruter es 0.9.5-0-win1, ya tiene el problema solucionado y no "
+"necesita hacer nada."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34
+msgid "See `this page`_ for instructions."
+msgstr "Vea `this page`_ para más instrucciones."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:38
+msgid "`this page`"
+msgstr "`this page`"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:40
+msgid "Jetty 7 Migration Details"
+msgstr "Detalles de la migración a Jetty 7"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42
+msgid ""
+"For most people, the update should just work. If you have multiple Jetty "
+"eepsites,\n"
+"OR have made changes to jetty.xml or other Jetty configuration files, "
+"including changing the port\n"
+"from 7658, you MUST take manual action AFTER updating."
+msgstr ""
+"Para la mayoría la actualización debería funcionar sin más. Si tiene "
+"varias webs Jetty, O hizo cambios en jetty.xml u otros archivos de "
+"configuración de Jetty, incluyendo el cambio de puerto desde 7658, TIENE "
+"que hacer cambios manualmente DESPUÉS de actualizar."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48
+msgid ""
+"After update, the router will migrate your jetty.xml files to the new "
+"Jetty 7 format."
+msgstr ""
+"Después de la actualización, el ruter migrará sus archivos jetty.xml al "
+"nuevo formato de Jetty 7."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50
+msgid ""
+"The migration resets the port to 7658. If you have more than one Jetty "
+"eepsite, OR your eepsite\n"
+"  is NOT on port 7658, OR you have made other modifications to jetty.xml "
+"(for example changing the\n"
+"  listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml "
+"file for each eepsite to fix them up\n"
+"  after updating, and restart again."
+msgstr ""
+"Al migrar se reajusta el puerto al 7658. Si tiene más de una eepsite "
+"Jetty, O su eepsite NO está en el puerto 7658, O hizo otras "
+"modificaciones en el archivo jetty.xml (por ejemplo cambiando la "
+"dirección de 127.0.0.1 a 0.0.0.0), TIENE que editar el archivo jetty.xml "
+"después de actualizar, y reiniciar de nuevo."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55
+msgid ""
+"**The following files will be backed up with a ".jetty6" suffix"
+" and then migrated.**\n"
+"If you have made local changes, you may have to edit them manually and "
+"restart.\n"
+"See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7."
+msgstr ""
+"**Se hará una copia de seguridad de los siguientes archivos con un sufijo"
+" ".jetty6" y entonces será migrado**\n"
+"SI ha hecho cambio locales, debería editarlos manualmente y reiniciar. "
+"Vea http://wiki.eclipse.org/Jetty para ver como confisurar Jetty 7."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69
+msgid "Plugins"
+msgstr "Complementos"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:71
+msgid "Most plugins should work fine with Jetty 7."
+msgstr "La mayoría de los pluguins deberían funcionar sin problemas con Jetty 7."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:75
+msgid ""
+"The I2PControl and zzzot plugins must be updated. Your router should "
+"download and install the new versions shortly after starting 0.9.6."
+msgstr ""
+"Los pluguins I2PCOntrol y zzzot tienen que actualizarse. Su ruter debería"
+" descargar e instalar las nuevas versiones nada más arrancar la versión "
+"0.9.6."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77
+msgid "If a plugin does not work, please contact the maintainer for that plugin."
+msgstr ""
+"Su algún pluguin no funciona, por favor pongase en contacto con el "
+"desarrollador de ese pluguin."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83
+msgid "Several bugs with Windows installation (see above)"
+msgstr "Varioes errores con la instalación de Windows (vea más arriba)"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:84
+msgid "Fix default form action in i2ptunnel"
+msgstr "Arreglado el formulario de acción por defecto en i2ptunnel"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85
+msgid "Fix links on iframed console pages"
+msgstr "Arreglados los enlaces en las webs de la consola"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86
+msgid "Better detection of 64-bit Windows to prevent crashes by systray"
+msgstr ""
+"Mejor detección de Windows 64-bits para prevenir las caidas de la bandeja"
+" de sistema"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87
+msgid "Fix bug preventing router update via torrent"
+msgstr "Arreglado el error que evitaba poder actualizar el router por torrent."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88
+msgid "Several SSU fixes for NATs that change UDP ports"
+msgstr "Varias arreglos en SSU para las NATs que cambian sus puertos UDP"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89
+msgid ""
+"Ignore unsupported IPs in RouterInfos when selecting an address (prep for"
+" IPv6)"
+msgstr ""
+"IPs no soportadas son ignoradas cuando se selecciona una dirección "
+"(preparado para IPv6)"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90
+msgid ""
+"Ignore unused option bits in Database Lookup Message (prep for requesting"
+" encrypted response)"
+msgstr ""
+"Se ignoran las opciones no usadas en los Mensajes de Búsqueda en la Base "
+"de Datos (preparado para solicitar respuestas cifradas)"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91
+msgid "Fix HTTP proxy error response for malformed URIs"
+msgstr "Arreglada la respuesta de error del proxy HTTP para URIs malformadas"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92
+msgid "Recognize UPnP devices without port forwarding capability"
+msgstr "Reconocimiento de dispositivos UPnP sin el reenvío de puertos habilitado."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96
+msgid "Jetty 7.6.10 (see above for migration information)"
+msgstr "Jetty 7.6.10 (vea más arriba para la migración)"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97
+msgid "Limit page size in i2psnark"
+msgstr "Se limita el tamaño de página en i2psnark"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98
+msgid "Add data directory and page size configuration to i2psnark"
+msgstr ""
+"Se añaden información de directorio y tamaño de página en la "
+"configuración de i2psnark."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99
+msgid "Support multiple i2psnark instances"
+msgstr "Soporte para múltiple instancias de i2psnark"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100
+msgid "Piece size adjustments in i2psnark"
+msgstr "Ajuste del tamaño de los trozos del torrent en i2psnark"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101
+msgid "Add more graphing support for combined bandwidth graph"
+msgstr ""
+"Añadido soporte para más gráficos en la gráfica del ancho de banda "
+"combinado."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102
+msgid "Block b32.i2p supercookies"
+msgstr "Bloque de las supercookies b32.i2p"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103
+msgid "Allow stopping clients on /configclients"
+msgstr "Se permite para los clientes en /configclients "
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104
+msgid "Check for nonce count replays in HTTP client"
+msgstr "Comprobar el número de respuestas nonce en el cliente HTTP"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105
+msgid "Support SASL authentication in IRC proxy"
+msgstr "Soporte de la autenticación SASL en el proxy IRC"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106
+msgid "Several cleanups and minor fixes in the update manager"
+msgstr "Varias mejoras y arreglos menores en al administrador de actualizaciones"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107
+msgid "Translation updates: German, Portuguese, Russian, Spanish, and Swedish"
+msgstr "Traducciones actualizadas: alemán, portugués, ruso, español y sueco"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:2
+msgid "0.9.7 Release"
+msgstr "Versión 0.9.7"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:7
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:9
+msgid "0.9.7 includes significant bug fixes and improvements."
+msgstr "0.9.7 Contiene significantes mejoras y arreglos de errores"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:11
+msgid ""
+"For the first time, class 'N' routers (those with a minimumum of 128 "
+"KBytes/sec of shared bandwidth)\n"
+"will automatically become floodfill (previously it was only 'O' routers "
+"with 256 KBps). This will\n"
+"increase the floodfill population for additional resistance to certain "
+"attacks (see below). Floodfill routers\n"
+"don't consume much additional bandwidth, but they do tend to use "
+"additional memory and concurrent\n"
+"connections. If you do not wish your router to become floodfill, set the "
+"advanced configuration\n"
+"router.floodfillParticipant=false ."
+msgstr ""
+"Por primera vez, los ruters de clase 'N' (aquellos con un mínimo de 128 "
+"KBytes/sec de ancho de banda compartido)class=\"marksource newline\" "
+"title=\"New line\"> se convertirán automáticamente en floodfills "
+"(anteriormente eran sólo las ruters 'O' con 256 KBps). Esto "
+"incrementaráclass=\"marksource newline\" title=\"New line\"> el número de"
+" floodfills para aumentar la resistencia ciertos ataques (ver más abajo)."
+" Los ruters Floodfill noclass=\"marksource newline\" title=\"New line\"> "
+"consumen mucho más ancho de banda, pero tieneden a utilizar más memoria y"
+" conexionesclass=\"marksource newline\" title=\"New line\" concurrentes. "
+"Si no desea que su ruter funcione como un Floodfill, cambie en la "
+"configuración avanzadaclass=\"marksource newline\" title=\"New line\"> a "
+"router.floodfillParticipant=false ."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:20
+#, python-format
+msgid ""
+"As we think the last release fixed the experimental update-via-torrent "
+"bugs, 3% of routers should\n"
+"update over in-network bittorrent this cycle."
+msgstr ""
+"Como pensamos que la anterior versión solucionó el problema de la "
+"actualización experimental sobre torrent, el 3% o de los ruters deberían "
+"actualizarse sobre la red bittorrent a partir de ahora."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:25
+msgid ""
+"Plugin update checks, possibly broken for several releases, are fixed. "
+"Your plugins should once again\n"
+"auto-update after updating the router."
+msgstr ""
+"Arreglado la comprobación de actualizaciones de los pluguins, "
+"probablemente roto en varias versiones. Sus pluguins deberían auto "
+"actualizarse después de actualizar el ruter."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:30
+msgid ""
+"We fixed a major streaming timer bug that contributed to frequent IRC "
+"disconnects."
+msgstr ""
+"Arreglamos un error mayor que hacía que el IRC tuviese desconexiones "
+"frecuentes."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:34
+msgid ""
+"This release contains additional mitigations for the `\"practical "
+"attacks\" paper`_.\n"
+"However, we have a lot more work to do to resist Sybil attacks on the "
+"floodfills, and resist\n"
+"traffic analysis at the gateways and endpoints of exploratory tunnels.\n"
+"It's a good reminder for everybody that our network is still relatively "
+"small and vulnerable.\n"
+"We don't currently recommend any uses that would put anybody in serious "
+"jeopardy.\n"
+"We'll keep working to improve it... please keep working to spread the "
+"word. A bigger network is a better network."
+msgstr ""
+"Esta versión contiene pequeñas mejoras contra el `estudio sobre \"ataques"
+" prácticos\"`_. Aún así, tenemos que hacer mucho más trabajo para "
+"resistir los ataques Sybil sobre los Floodfill, y resistir los ataques de"
+" análisis de tráfico sobre las puertas de salida y los puntos finales de "
+"los túneles exploratorios.  Es un buen momento para recordar a todos que "
+"la red es pequeña y por eso vulnerable. No recomendamos ningún uso de I2P"
+" que pudiera poner a alguien en serios peligros. Seguimos trabajando para"
+" mejorarlo... por favor, siga corriendo la voz sobre I2P. Una red más "
+"grande es una red mejor."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:43
+msgid "`\"practical attacks\" paper`"
+msgstr "`estudio sobre \"ataques prácticos\"`"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:47
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:15
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:107
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:28
+msgid "Anonymity Improvements"
+msgstr "MEjoras en el anonimato."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:49
+msgid "End-to-end encryption of responses to leaseset lookups"
+msgstr "Cifrado de fin a fin de las respuestas a las búsquedas leaseset."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:50
+msgid "Expand floodfill pool by enabling class 'N' floodfills"
+msgstr ""
+"Aumento del número de floodfills activando los ruters clase 'N' como "
+"floosfills."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:51
+msgid "Randomize padding inside encrypted SSU packets"
+msgstr "RElleno aleatorio dentro de los paquetes cifrados SSU"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:52
+msgid "Preparation for better SSU protocol obfuscation"
+msgstr "Preparación para la mejora del ocultamiento del protocolo SSU"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:56
+msgid "Fix newer lease sets not getting stored or published"
+msgstr "Arreglo de los nuevos leasesets no almacenados o publicados"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:57
+msgid ""
+"Fix classpath bug when used with 4-year-old installations, causing the "
+"console not to start"
+msgstr ""
+"Arreglado el error classpath cuando se usaban instlaciones de más de 4 "
+"años, provocando que la consola no iniciase."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:58
+msgid "Fix addressbook database bug preventing update of the reverse index"
+msgstr ""
+"Arreglado el problema de la base de datos que evitaba las actualizaciones"
+" del índice reverso."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:59
+msgid ""
+"Fix i2psnark bug that changed the infohash of torrents created by Robert "
+"and fetched via magnet link"
+msgstr ""
+"Arreglado el error de i2psnark que cambiaba el infohash de los torrents "
+"creados por Robert y descargados a traves de enlaces magnet."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60
+msgid "Fix version checking for plugins"
+msgstr "Arreglada la comprobación de versión de los pluguins"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:61
+msgid ""
+"Fix a streaming timer bug causing frequent IRC disconnects (also affects "
+"other close-on-idle tunnels)"
+msgstr ""
+"Arreglado el error que causaba desconexiones frecuentes en el IRC "
+"(también afectaba a otros tipos de túeneles)"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:65
+msgid "Don't install as a service on Windows by default"
+msgstr "En Windows no lo instale por defecto como un servicio"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:66
+msgid "Reduce transport idle timeouts"
+msgstr "Reducido los tiempos de reposo de transporte"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:67
+msgid "Reduce tunnels on idle in i2psnark"
+msgstr "Reducción de túneles en i2psnark en reposo"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:68
+msgid "Change default in i2ptunnel GUI to 3 hops"
+msgstr "Cambiado a 3 saltos por defecto en la configuración de i2ptunnel"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:69
+msgid "IE 10 support"
+msgstr "Soporte para IE 10"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70
+msgid ""
+"Individual expiration times in leases, for efficiency on destinations "
+"with a high number of tunnels"
+msgstr ""
+"Tiempos de vencimiento individuales para los leases, para mejorar la "
+"eficiencia en los destinos cuando hay un gran número de túneles."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71
+msgid "Low-level encryption and XOR speedups"
+msgstr "Mejora de la velocidad en cifrados de najo nivel y XOR"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:72
+msgid "Jetty 7.6.11"
+msgstr "Jetty 7.6.11"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:73
+msgid "Tomcat 6.0.37"
+msgstr "Tomcat 6.0.37"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74
+msgid "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish"
+msgstr ""
+"Actualizaciones en las traducciones: Chino, Francés, Portugués, Ruso y "
+"Castellano"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75
+msgid "New Turkish translation"
+msgstr "Nueva traducción al Turco"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:76
+msgid "Wrapper 3.5.19 (new installs and PPA only)"
+msgstr "Wrapper 3.5.19 (sólo en las instalaciones nuevas y en PPA)"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:2
+msgid "0.9.7.1 Release"
+msgstr "Versión 0.9.7.1"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:7
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:9
+msgid ""
+"This unscheduled release disables the RouterInfo verification messages "
+"that were used in the attack published in the UCSB paper, which should "
+"make correlating a LeaseSet and a Router much more difficult. We have "
+"also included a limited number of other fixes listed below. Our 0.9.8 "
+"release, which will include IPv6 support, is still on-schedule for late "
+"September."
+msgstr ""
+"Esta versión no programada desactiva los mensajes de verificación "
+"RouterInfo que se usaron en el ataque publicado en el estudio de UCSB, "
+"que debería hacer que sea mucho más difícil relacionar un LeaseSet y un "
+"Ruter. También hemos incluido un número limitado de mejoras, listadas más"
+" abajo. Nuestra versión 0.9.8, la cual incluirá soporte para IPV6, está "
+"prevista para finales de Septiembre."
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:11
+msgid "As usual, we recommend that all users update to this release."
+msgstr ""
+"Como siempre, recomendamos que todos los usuarios se actualicen a esta "
+"versión."
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:17
+msgid "Disable RouterInfo verification messages"
+msgstr "Desactivados los mensajes de verificación RouterInfo"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:21
+msgid "Extend inbound tunnel expiration"
+msgstr "Aumentado el tiempo de caducidad de los túneles de entrada"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:22
+msgid "i2prouter: bashism fix"
+msgstr "i2prouter: arreglo de bashism"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:23
+msgid "i2psnark: increase max piece size, mime type updates"
+msgstr ""
+"i2psnark: aumentado el tamaño máximo de cada cacho, actualizaciones de "
+"los mimetypes"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:24
+msgid "New reseed host"
+msgstr "Nuevo servidor de resiembra "
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:25
+msgid "New update hosts, thanks Meeh and dg"
+msgstr "Nuevo servidor de actualizaciones, gracias a Meeh y dg"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:26
+msgid "Streaming: RTO changes"
+msgstr "Streaming: cambios en RTO"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:27
+msgid "Updater: Increase update-via-torrent to 30 percent"
+msgstr ""
+"Actualizador: Aumento de las actualizaciones a través de torrents al 30 "
+"porcent"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:28
+msgid "UPnP fix for some hardware"
+msgstr "Arreglo de UPnP para algunos sistemas"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:2
+msgid "0.9.8 Release"
+msgstr "Versión 0.9.8"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9
+msgid ""
+"0.9.8 includes the long-awaited support for IPv6. It's enabled by "
+"default, but of course you need a public IPv6 address to use it. "
+"Configuration is on the 'network' configuration tab in your console. We "
+"also have anonymity improvements including padding of SSU packets and "
+"longer router private keys."
+msgstr ""
+"La versión 0.9.8 incluye el largamente esperado soporte para IPv6. Está "
+"habilitado por defecto, pero por supuesto necesita una dirección IPv6 "
+"pública para usarlo. La configuración está en la pestaña de configuración"
+" 'red' en su consola. También tenemos mejoras en el anonimato,  "
+"incluyendo el uso de datos de relleno en los paquetes SSU (UDP seguro "
+"semiconfiable) y claves privadas de router más largas."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11
+#, python-format
+msgid "30% of you will update via in-network torrent in this update cycle."
+msgstr ""
+"El 30% of ustedes actualizará a través de un torrent interno a la red en "
+"este ciclo de actualización."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13
+msgid "IPv6 Details"
+msgstr "Detalles de IPv6"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15
+msgid ""
+"IPv6 is enabled and preferred by default. If you have a public IPv6 "
+"address \n"
+"and you are connecting to another router with a published IPv6 address, "
+"it will \n"
+"connect via IPv6. There is a new IPv6 configuration section on /confignet"
+" in \n"
+"the router console. If IPv6 is causing problems you may disable it there."
+msgstr ""
+"IPv6 está habilitado y es preferido por defecto. Si tiene una dirección \n"
+"IPv6 pública y se está conectando a otro router con una dirección IPv6 \n"
+"publicada, se conectará mediante IPv6. Hay una nueva sección de \n"
+"configuración de IPv6 en /confignet en la consola del router. Si IPv6 "
+"está \n"
+"causando problemas puede deshabilitarlo allí."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22
+msgid ""
+"As a part of the IPv6 development effort, I2P now supports multiple \n"
+"published IP addresses. If you have multiple public IP addresses (IPv4, "
+"IPv6, \n"
+"or both), you may enable or disable them individually on /confignet. The"
+" \n"
+"default is to use the first IPv4 and IPv6 addresses it discovers. If you "
+"have \n"
+"multiple addresses you should review the configuration on /confignet and "
+"adjust \n"
+"it if necessary.\n"
+"Note that while you may enable multiple IPv4 and IPv6 addresses on "
+"/confignet,\n"
+"we recommend that you use only one IPv4 and one IPv6 address. There are\n"
+"bugs still to be fixed with multiple addresses of each type."
+msgstr ""
+"Como una parte del esfuerzo de desarrollo para IPv6, I2P ahora soporta \n"
+"múltiples direcciones IP publicadas. Si tiene múltiples direcciones IP \n"
+"públicas (IPv4, IPv6, o ambas), puede habilitarlas o deshabilitarlas \n"
+"individualmente en /confignet. La configuración por defecto es usar las \n"
+"primeras direcciones IPv4 e IPv6 que descubra. Si tiene múltiples \n"
+"direcciones debe revisar la configuración en /confignet y ajustarla si "
+"fuera \n"
+"necesario. Observe que aunque pueda habilitar múltiples direcciones IPv4 "
+"e \n"
+"IPv6 en /confignet, le recomendamos que sólo use una dirección IPv4 y una"
+" \n"
+"IPv6. Todavía hay fallos por arreglar con direcciones múltiples de cada "
+"tipo."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34
+msgid ""
+"While IPv6 support was designed and developed over several years, it has"
+" \n"
+"only been tested by a limited number of users and is still beta. If you "
+"do have \n"
+"a public IPv6 address, please monitor your router and the logs for "
+"problems, \n"
+"and disable it necessary. Please report any bugs on \n"
+"http://trac.i2p2.i2p."
+msgstr ""
+"Aunque el soporte IPv6 fue diseñado y desarrollado durante varios años, \n"
+"sólo ha sido probado por un limitado número de usuarios y todavía está en"
+" \n"
+"beta. Si no tiene una dirección IPv6 pública, por favor monitorice su "
+"router y \n"
+"los logs (registros) en busca de problemas, y deshabilítelo si fuera \n"
+"necesario. Por favor informe en http://trac.i2p2.i2p de cualquier fallo."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:42
+msgid "Rekeying Details"
+msgstr "Detalles de renovación de claves"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44
+msgid ""
+"For those of you running I2P on faster hardware (generally, 64-bit x86) "
+"the \n"
+"router will generate a new identity using longer keys. This will "
+"substantially \n"
+"reduce your participating traffic for 48 hours or more, while your router"
+" \n"
+"re-integrates into the network. Due to the new keys, the large number of"
+" \n"
+"torrent updates, and the recent network growth, we expect substantial \n"
+"disruption to the network for a week or more after the update is "
+"released. \n"
+"Please be patient and things should start to improve after a few days."
+msgstr ""
+"Para aquellos que ejecuten I2P en un hardware más rápido (generalmente \n"
+"x86 de 64-bits) el router generará una nueva identidad usando claves más"
+" \n"
+"largas. Esto reducirá sustancialmente su tráfico participante durante 48"
+" \n"
+"horas o más, mientras su router se re-integra en la red. Debido a las "
+"nuevas \n"
+"claves, el gran número de actualizaciones mediante torrent, y el reciente"
+" \n"
+"crecimiento de la red, esperamos una perturbación sustancial de la red \n"
+"durante la próxima semana o más después de que la actualización sea \n"
+"publicada. Por favor sea paciente, las cosas deberían comenzar a mejorar"
+" \n"
+"tras unos pocos días."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54
+msgid ""
+"These changes may result in higher CPU usage for some of you. We're doing"
+" \n"
+"our best to increase efficiency, but stronger security generally requires"
+" more \n"
+"computation. Performance may also be poor during the first week\n"
+"due to the network churn.\n"
+"We will evaluate the network performace before deciding whether to\n"
+"change the key length on slower hardware in a future release."
+msgstr ""
+"Estos cambios pueden resultar en mayor uso de la CPU para algunos de \n"
+"ustedes. Estamos dando lo mejor de nosotros para incrementar la "
+"eficiencia, \n"
+"pero una mayor seguridad generalmente requiere más computación. El "
+"rendimiento también puede ser pobre durante la primera semana debido a la"
+" \n"
+"agitación de la red. Evaluaremos el rendimiento de la red antes de "
+"decidir\n"
+"si cambiar la longitud de la clave sobre hardware más lento en una futura"
+" versión. "
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63
+msgid ""
+"We are experiencing rapid network growth in the last few weeks, which is"
+" \n"
+"causing a bit of a bumpy ride for some, especially on weekends. However, "
+"the \n"
+"network is still performing fairly well, so keep spreading the word."
+msgstr ""
+"Estamos experimentando un rápido crecimiento de la red en las últimas "
+"semanas, lo que está causando que el trayecto sea un poco accidentado \n"
+"para algunos, especialmente en fines de semana. Sin embargo la red \n"
+"está rindiendo bastante bien, así que siga extendiendo el mensaje."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69
+msgid "More Changes Coming"
+msgstr "Más cambios en camino"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:71
+msgid ""
+"We're in the initial stages of desiging major changes to strengthen our \n"
+"crypto. Stronger crypto will use more CPU and it may possibly \n"
+"require a Java 7 JRE at a minimum. We understand your desire to run I2P "
+"on low-power \n"
+"and/or older hardware. We're working hard to minimize the impacts, but "
+"some \n"
+"loss of performance is inevitable. In addition, Java 5 and 6 are no "
+"longer \n"
+"supported by Oracle. Now is a good time to upgrade to Java 7. Any change "
+"in \n"
+"minimum requirements will be announced well in advance."
+msgstr ""
+"Estamos en las etapas iniciales del diseño de cambios importantes para \n"
+"fortalecer nuestra criptografía. Una criptografía más fuerte usará más "
+"CPU y \n"
+"posiblemente puede requerir un Java 7 JRE (entorno de ejecución) al "
+"mínimo. \n"
+"Comprendemos su deseo de ejecutar I2P en hardware de menor consumo y/o "
+"más antiguo. Estamos trabajando duro para minimizar los \n"
+"impactos, pero cierta pérdida de rendimiento es inevitable. Además, Java "
+"5 y 6 ya no están soportados por Oracle. Ahora es un buen momento para "
+"actualizar a Java 7. Cualquier cambio en los requisitos mínimos será "
+"anunciado con una buena antelación."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:81
+msgid "New Website"
+msgstr "Nuevo sitio web"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:83
+msgid ""
+"After a heroic effort by str4d, the new website preview is available at \n"
+"http://i2hq.srv.i2p2.de. We hope to see it go live at \n"
+"https://geti2p.net and http://www.i2p2.i2p soon.  Please \n"
+"contribute to the new website translations on Transifex, especially the \n"
+"website_priority resource."
+msgstr ""
+"Tras un esfuerzo heroico de str4d, en http://i2hq.srv.i2p2.de está "
+"disponible \n"
+"una nueva previsualización del sitio web. Esperamos ver su puesta en "
+"activo \n"
+"en https://geti2p.net y http://www.i2p2.i2p pronto. Por favor, contribuya"
+" con \n"
+"las traducciones del nuevo sitio web en Transifex, especialmente sobre el"
+" \n"
+"recurso website_priority."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91
+msgid "Community Participation"
+msgstr "Participación de la comunidad"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:93
+msgid ""
+"In early August, hottuna and zzz attended DEFCON 21 in Las Vegas.\n"
+"Last weekend, echelon attended the CTS IV conference in Berlin and\n"
+"psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass.\n"
+"Several of us will be at 30C3 in Hamburg late this year.\n"
+"It's great to see people participating at these events and representing "
+"I2P."
+msgstr ""
+"A principios de agosto, hottuna y zzz acudieron al DEFCON 21 en Las "
+"Vegas. La última semana, echelon acudió a la conferencia CTS IV en Berlín"
+" y psi acudió al Tahoe-LAFS hackfest en GNU30 en Cambridge, "
+"Massachussets. Varios de nosotros estaremos en el 30C3 en Hamburgo a \n"
+"finales de este año. Es estupendo ver gente participando en estos eventos"
+" y representando a I2P."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105
+msgid "IPv6 support for both NTCP and SSU"
+msgstr ""
+"Soporte IPv6 para ambos NTCP (TCP basado en NIO) y SSU (UPD seguro "
+"semiconfiable)"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:109
+msgid "SSU protocol obfuscation by adding random padding"
+msgstr ""
+"Ofuscación del protocolo SSU mediante el uso de datos aleatorios de "
+"relleno."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110
+msgid "Longer encryption and DH private keys for users on faster platforms"
+msgstr ""
+"Claves privadas de cifrado más largas y DH (Diffie-Hellman) para usuarios"
+" en plataformas más rápidas"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114
+msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)"
+msgstr "Reparación del clausurado y duplicados de I2PTunnel/I2CP (parcial)"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:115
+msgid "Fix translation of HTTP proxy error pages"
+msgstr "Reparación de la traducción de páginas de error del proxy HTTP"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:116
+msgid "Fix occasional runtime exception in NTCP"
+msgstr "Reparación de excepciones ocasionales de tiempo de ejecución en NTCP"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120
+msgid "Big rework of transport code to accommodate multiple addresses and IPv6"
+msgstr ""
+"Gran remodelación del código de transporte para acomodar múltiples "
+"direcciones e IPv6"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121
+msgid "Streaming: Improved recovery from lost acks, other fixes"
+msgstr "Streaming: Recuperación mejorada desde ACKs perdidos y otras reparaciones"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122
+msgid "Use Transifex for translation of initial news and HTTP proxy error pages"
+msgstr ""
+"Use Transifex para la traducción de notificaciones iniciales y páginas de"
+" error de proxy HTTP"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123
+msgid ""
+"Translation updates: Chinese, French, German, Portuguese, Russian, "
+"Swedish, Turkish"
+msgstr ""
+"Actualizaciones de traducción: Chino, Francés, Alemán, Portugués, Ruso, "
+"Sueco, Turco"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124
+msgid "New Romanian translation"
+msgstr "Nueva traducción al Rumano"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:126
+msgid "Wrapper 3.5.20 (new installs and PPA only)"
+msgstr "Wrapper 3.5.20 (sólo nuevas instalaciones y PPA)"
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:2
+msgid "0.9.8.1 Release"
+msgstr "Versión 0.9.8.1"
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:7
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:9
+msgid ""
+"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some "
+"people. New installs and non-Windows platforms are not affected, however "
+"all platforms will automatically update even if running 0.9.8."
+msgstr ""
+"La versión 0.9.8.1 arregla un problemas con la actualización de 0.9.8 en "
+"Windows. Las nuevas instalaciones y los sistemas no Windows no están "
+"afectados, aún así, todas las plataformas se actualizarán automáticamente"
+" incluso si ejecutan 0.9.8."
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:11
+msgid ""
+"See the `Trac ticket`_ for details and workarounds. See\n"
+"`the 0.9.8 release notes`_ for information on IPv6 and other changes."
+msgstr ""
+"Vea el  `Trac ticket`_ para los detalles y soluciones. Vea las `notas de "
+"verisón de 0.9.8`_ para más información sobre IPv6 y otros cambios."
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:16
+msgid ""
+"Due to recent attacks, logins are disabled on `Trac`_ and new "
+"registrations are\n"
+"disabled on `zzz.i2p`_. Until those services are restored, please report "
+"all\n"
+"bugs on IRC freenode or IRC2P #i2p-dev."
+msgstr ""
+"Debido a recientes ataques, los logins están deshabilitados en el `Trac`_"
+" y los nuevos registros están desactivados en `zzz.i2p`_. Hasta que sean "
+"restaurados estos servicios, reporte los errores en el IRC freenode o en "
+"IRC2P #i2p-dev."
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:22
+msgid "`Trac ticket`"
+msgstr "`Trac ticket`"
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:23
+msgid "`the 0.9.8 release notes`"
+msgstr "`notas de versión de 0.9.8`"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:2
+msgid "0.9.9 Release"
+msgstr "Versión 0.9.9"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:7
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:9
+msgid ""
+"0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and "
+"starts work on a year-long plan to increase the strength of the "
+"cryptographic signing algorithms used in the router, and support multiple"
+" algorithms and key lengths simultaneously. Automatic update files will "
+"now be signed with 4096-bit RSA keys."
+msgstr ""
+"La versión 0.9.9 repara varios de los fallos en la netdb (base de datos "
+"de red), streaming (transporte de datos en flujo), y i2ptunnel (túnel "
+"I2P), y comienza a trabajar en un plan de por-un-año para incrementar la "
+"fortaleza de los algoritmos criptográficos de firma usados en el router, "
+"y soportar múltiples algoritmos y longitudes de clave simultáneamente. "
+"Los ficheros de actualización automática ahora se firmarán con claves RSA"
+" de 4096-bits."
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:11
+msgid ""
+"We now support SSL between your router and your servers for security.\n"
+"See `this development thread`_ for more information."
+msgstr ""
+"Ahora soportamos SSL entre su router y sus servidores por seguridad.\n"
+"Vea `este hilo de desarrollo`_ para más información."
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:16
+msgid "`this development thread`"
+msgstr "`este hilo de desarrollo`"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:18
+msgid ""
+"As usual, we recommend that you update to this release.\n"
+"The best way to maintain security and help the network is to run the "
+"latest release.\n"
+"Several members of the I2P team will be at 30C3 in Hamburg this year.\n"
+"Come say hello and ask for an I2P sticker.\n"
+"Thanks to everyone for their support this year."
+msgstr ""
+"Como es habitual, le recomendamos que actualice a esta versión.\n"
+"La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la"
+" última versión.\n"
+"Varios miembros del equipo I2P estarán en el 30C3 en Hamburgo este año.\n"
+"Pase a saludar y pedirnos una pegatina de I2P.\n"
+"Gracias a todos por vuestro soporte este año."
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:30
+msgid "Don't build client tunnels through zero-hop exploratory tunnels"
+msgstr ""
+"No construye túneles cliente a través de túneles exploratorios de cero-"
+"saltos"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:31
+msgid "New \"su3\" file support using stronger keys"
+msgstr "Nuevo soporte de fichero \"su3\" que usa claves más fuertes"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:32
+msgid "Use su3 for updates"
+msgstr "Usa su3 para las actualizaciones"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:36
+msgid "Issues with losing data when closing streams"
+msgstr "Problemas de pérdida de datos al cerrar streams"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:37
+msgid "Fix various streaming connection limit issues"
+msgstr "Arregla problemas con el límite para varias conexiones de streaming"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:38
+msgid "Issues with resource usage of closed connections"
+msgstr "Problemas con el uso de recursos de conexiones cerradas"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:39
+msgid "Clean up timer threads in close-on-idle tunnels"
+msgstr ""
+"Ordena los hilos de ejecución de los temporizadores en túneles con "
+"cierre-por-inactividad"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:40
+msgid "Several other streaming fixes"
+msgstr "Otros arreglos varias del streaming"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:41
+msgid "Reject more non-public IPv6 addresses"
+msgstr "Arregla más direcciones IPv6 no-públicas"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:42
+msgid "Fix IPv6 GeoIP"
+msgstr "Arregla la (geolocalización) GeoIP de IPv6"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:43
+msgid "Fix peer selection in first minutes after startup"
+msgstr ""
+"Arregla la selección de par ('peer') en los primeros minutos tras el "
+"arranque"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:44
+msgid "Several I2PTunnel bug fixes"
+msgstr "Arreglos varios de fallos de I2PTunnel"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:45
+msgid "Fix major i2psnark DHT bug that prevented magnets from working well"
+msgstr ""
+"Arregla un fallo importante de la (tabla de hash distribuida) DHT de "
+"I2PSnark que evitaba que los enlaces magnet funcionaran bien"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:46
+msgid ""
+"Fix client tunnels that fail due to name resolution failure at startup, "
+"particularly with b32 hostnames"
+msgstr ""
+"Arregla túneles cliente que fallaban debido a un error en la resolución "
+"de nombres al iniciar, particularmente con nombres de equipos b32"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:47
+msgid "Fix changing client i2ptunnel target list"
+msgstr "Arregla el cambio de lista de objetivos I2PTunnel cliente"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:48
+msgid ""
+"Fix major bugs preventing reception of encrypted responses to leaseset "
+"lookups and verifies"
+msgstr ""
+"Arregla fallos importantes que evitaban la recepción de respuestas "
+"cifradas a búsquedas de LeaseSets y verificaciones"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:49
+msgid "Fix bad links on some i2psnark buttons in Opera and text-mode browsers"
+msgstr ""
+"Arregla enlaces erróneos en algunos botones I2PSnark en Opera y "
+"navegadores en modo-texto"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:50
+msgid "Fix NPE in Susimail"
+msgstr "Arregla la NPE (excepción de puntero nulo) en SusiMail"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:54
+msgid "Start work on supporting stronger signing keys in the router"
+msgstr "Inicia trabajo para soportar claves de firmado más fuertes en el router"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:55
+msgid "Reduce thread usage for HTTP Server tunnels"
+msgstr "Reduce el uso del hilos de ejecución para túneles de servidor HTTP"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:56
+msgid "Auto-stop update torrent after some time"
+msgstr "Auto-detener actualización de torrents tras cierto tiempo"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:57
+msgid "Add ability to stop webapp via console"
+msgstr "Añade capacidad de detener la aplicación web mediante consola"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:58
+msgid "New POST throttler in HTTP server tunnel"
+msgstr "Nuevo regulador de llamadas POST en túneles de servidor HTTP"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:59
+msgid "Improve connection throttling"
+msgstr "Mejora el regulado de la conexión"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:60
+msgid "More work to reduce number of connections"
+msgstr "Más trabajo para reducir el número de conexiones"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:61
+msgid "Re-enable router info expiration job"
+msgstr "Re-habilita la tarea para la expiración de la información del router"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:62
+msgid ""
+"Extend router info expiration and other changes to reduce load on "
+"floodfills"
+msgstr ""
+"Extiende la expiración de la información del router y otros cambios para "
+"reducir la carga durante las inundaciones de red"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:63
+msgid "Support multiple servers through a single server tunnel"
+msgstr "Soporta múltiples servidores a través de un único túnel de servidor"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:64
+msgid "Support specification of server port in i2ptunnel clients"
+msgstr "Soporta la configuración de un puerto de servidor en clientes I2PTunnel"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:65
+msgid "Add support for SSL connections from i2ptunnel to external server"
+msgstr "Añade soporte para conexiones SSL desde I2PTunnel hacia servidor externo"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:66
+msgid "SSL and crypto code refactoring"
+msgstr "Refactorización del código SSL y de criptografía"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:67
+msgid "i2psnark storage code refactoring"
+msgstr "Refactorización del código del almacenamiento de I2PSnark"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:68
+msgid "New destination cache"
+msgstr "Caché de nuevo destino"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:69
+msgid "Lots of code cleanup and resolution of findbugs warnings"
+msgstr ""
+"Mucho acicalamiento del código y resolución de advertencias por fallos "
+"encontrados"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:70
+msgid "New Japanese translation (partial)"
+msgstr "Nueva traducción al japonés (parcial)"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:71
+msgid ""
+"Translation updates: French, German, Italian, Romanian, Russian, Spanish,"
+" Swedish, and others"
+msgstr ""
+"Actualización de traducciones: francés, alemán, italiano, rumano, ruso, "
+"español, sueco, y otros"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:73
+msgid "Wrapper 3.5.22 (new installs and PPA only)"
+msgstr "Wrapper 3.5.22 (sólo nuevas instalaciones y PPA)"
+
diff --git a/i2p2www/translations/es/LC_MESSAGES/comparison.po b/i2p2www/translations/es/LC_MESSAGES/comparison.po
new file mode 100644
index 00000000..2b1d563e
--- /dev/null
+++ b/i2p2www/translations/es/LC_MESSAGES/comparison.po
@@ -0,0 +1,863 @@
+# Spanish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Adolfo Jayme Barrientos , 2013
+# Daniel Mustieles , 2013
+# m1xxy , 2011
+# olivertrash , 2013
+# strel, 2013
+# trolly, 2013
+# trolly , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-10-26 22:39+0000\n"
+"PO-Revision-Date: 2013-09-20 10:34+0000\n"
+"Last-Translator: trolly \n"
+"Language-Team: Spanish "
+"(http://www.transifex.com/projects/p/I2P/language/es/)\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/comparison/freenet.html:2
+msgid "I2P Compared to Freenet"
+msgstr "Comparación de I2P con Freenet"
+
+#: i2p2www/pages/site/comparison/freenet.html:8
+msgid ""
+"Freenet is a fully distributed, peer to peer anonymous publishing "
+"network, offering \n"
+"secure ways to store data, as well as some approaches attempting to "
+"address the loads\n"
+"of a flash flood.  While Freenet is designed as a distributed data store,"
+" people have\n"
+"built applications on top of it to do more generic anonymous "
+"communication, such as \n"
+"static websites and message boards."
+msgstr ""
+"Freenet es una red completamente distribuida, red anónima de publicación "
+"par a par, que ofrece una forma segura de almacenar datos, y también "
+"enfocada en solucionar los problemas de carga y desbordamientos. Mientras"
+" que Freenet está diseñada como un almacén distribuido de datos, la gente"
+" ha construido aplicaciones sobre el sistema para tener otras "
+"comunicaciones anónimas genéricas, como webs estáticas y foros."
+
+#: i2p2www/pages/site/comparison/freenet.html:16
+#, python-format
+msgid ""
+"Compared to I2P, Freenet offers some substantial benefits - it is a "
+"distributed data\n"
+"store, while I2P is not, allowing people to retrieve the content "
+"published by others \n"
+"even when the publisher is no longer online.  In addition, it should be "
+"able to \n"
+"distribute popular data fairly efficiently.  I2P itself does not and will"
+" not provide \n"
+"this functionality.  On the other hand, there is overlap for users who "
+"simply want to \n"
+"communicate with each other anonymously through websites, message boards,"
+" file sharing\n"
+"programs, etc.  There have also been some attempts to develop a "
+"distributed data \n"
+"store to run on top of I2P,\n"
+"(most recently a port of Tahoe-LAFS)\n"
+"but nothing is yet ready for general use."
+msgstr ""
+"Comparado con I2P, Freenet ofrece substanciales beneficios - es un "
+"sistema distribuido de almacenamiento de datos, mientras que I2P no lo "
+"es, permitiendo a la gente obtener al contenido publicado por otros "
+"incluso cuando el que lo ha publicado no esté online. Además es capaz de "
+"distribuir eficientemente la información más utilizada. I2P no tiene ni "
+"tendrá esta funcionalidad. Por otro lado, hay demasiada redundancia para "
+"los usuarios que simplemente quieren comunicarse con otros anónimamente a"
+" través de webs, foros, aplicaciones de compartición de archivos, etc.  "
+"Ha habido varios intentos de desarrollar un sistema de almacenamiento "
+"distribuido funcionando sobre I2P, (más recientemente un port de Tahoe-LAFS) pero todavía no está listo para uso "
+"general."
+
+#: i2p2www/pages/site/comparison/freenet.html:29
+msgid ""
+"However, even ignoring any implementations issues, there are some "
+"concerns \n"
+"about Freenet's algorithms from both a scalability and anonymity "
+"perspective, owing \n"
+"largely to Freenet's heuristic driven routing.  The interactions of "
+"various techniques \n"
+"certainly may successfully deter various attacks, and perhaps some "
+"aspects of the \n"
+"routing algorithms will provide the hoped for scalability.  "
+"Unfortunately, not much\n"
+"analysis of the algorithms involved has resulted in positive results, but"
+" there is still\n"
+"hope.  At the very least, Freenet does provide substantial anonymity "
+"against an attacker\n"
+"who does not have the resources necessary to analyze it further."
+msgstr ""
+"Sin embargo, e incluso ignorando los problemas de implementación, hay "
+"algunas preocupaciones sobre la escalabilidad y el anonimato de algunos "
+"algoritmos de Freenet, debido básicamente a la heurística de ruteo  de "
+"Freenet. La unión de varias técnicas puede desalentar el hacer varios "
+"tipos de ataques, y quizás algunos aspectos del algoritmo de ruteo "
+"podrían proveer la escalabilidad esperada. Desafortunadamente, no muchos "
+"de los análisis sobre los algoritmos han dado resultados satisfactorios, "
+"pero aún hay esperanzas. Al final, Freenet nos proporciona bastante "
+"anonimato contra cualquier atacante que no tenga los recursos necesarios "
+"para análisis completos."
+
+#: i2p2www/pages/site/comparison/index.html:2
+msgid "Comparing I2P to other projects"
+msgstr "Comparando I2P con otros proyectos"
+
+#: i2p2www/pages/site/comparison/index.html:4
+msgid ""
+"There are a great many other applications and projects working on "
+"anonymous \n"
+"communication and I2P has been inspired by much of their efforts.  This "
+"is not \n"
+"a comprehensive list of anonymity resources - both freehaven's \n"
+"Anonymity "
+"Bibliography\n"
+"and GNUnet's related "
+"projects\n"
+"serve that purpose well.  That said, a few systems stand out for further\n"
+"comparison. The following have individual comparison pages:"
+msgstr ""
+"Hay muchas otras buenas aplicaciones y proyectos trabajando en "
+"comunicaciones anónimas, e I2P se ha inspirado en muchos de sus "
+"esfuerzos. Esto no es una lista completa de recursos para el anonimato - "
+"ambos \n"
+"Anonymity "
+"Bibliography y los proyectos relacionados con "
+"GNUnet sirven también para ese mismo propósito. Dicho eso, pocos "
+"proyectos destacan como para comparaciones adicionales. Los siguientes "
+"proyectos tienen webs con comparaciones individuales:"
+
+#: i2p2www/pages/site/comparison/index.html:20
+#, python-format
+msgid ""
+"The following are discussed on the other "
+"networks page:"
+msgstr ""
+"Los siguientes proyectos son discutidos en la página sobre otras redes:"
+
+#: i2p2www/pages/site/comparison/index.html:32
+#, fuzzy, python-format
+msgid ""
+"The content of this page is subject to update, discussion and dispute, "
+"and we welcome comments and additions.\n"
+"You may contribute an analysis by entering a new "
+"ticket on Trac."
+msgstr ""
+"El contenido de esta página puede ser objeto de actualizaciones, "
+"discusión y disputa, y aprobamos comentarios y adiciones. Puede "
+"contribuir al análisis creando una nueva entrada en el Trac."
+
+#: i2p2www/pages/site/comparison/other-networks.html:2
+msgid "I2P Compared to Other Anonymous Networks"
+msgstr "Comparación de I2P con otras redes anónimas"
+
+#: i2p2www/pages/site/comparison/other-networks.html:5
+msgid "The following networks are discussed on this page."
+msgstr "Las siguientes redes son discutidas en esta página."
+
+#: i2p2www/pages/site/comparison/other-networks.html:16
+#, fuzzy, python-format
+msgid ""
+"Most of the following sections are fairly old, and may not be accurate.\n"
+"For an overview of available comparisons, see the\n"
+"main network comparisons page.\n"
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+"La mayoría de las siguientes secciones son bastante viejas y podrían no "
+"ser precisas.  Para una vista general de comparaciones disponibles, vea "
+"la página principal de comparaciones entre "
+"redes. Pude contribuir al análisis creando un nuevo ticket en el %(trac)s."
+
+#: i2p2www/pages/site/comparison/other-networks.html:29
+#, python-format
+msgid ""
+"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
+" \n"
+"anonymizing proxies, allowing people to tunnel out through the low "
+"latency \n"
+"mix network.  Morphmix includes some very interesting collusion detection"
+" \n"
+"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
+"IP\n"
+"addresses to accomplish the same.  The two primary differences between \n"
+"these systems and I2P are related to I2P's threat model \n"
+"and their out-proxy design (as opposed to providing both sender and "
+"receiver \n"
+"anonymity).  There is source code available to both systems, but we are "
+"not aware \n"
+"of their use outside of academic environments."
+msgstr ""
+"Morphmix y Tarzan son las dos totalmente distribuidas, redes par a par "
+"anónimas con proxies para el anonimato, permitiendo a la gente enviar "
+"datos fuera a través de redes de mezcla de baja latencia. Morphmix "
+"incluye unos algoritmos de detección de colisiones bastante interesante y"
+" defensas contra Sybil, mientras que Tarzan hace uso de la escasez de "
+"direcciones IP para obtener lo mismo. Las dos principales diferencias "
+"entre estos dos sistemas e I2P tienen que ver con el modelo de amenazas de I2P y  su diseño de "
+"outproxies (al contrario que el anonimato proporcionado  para ambos, el "
+"que envía y el que recibe). El código está disponible para ambos "
+"sistemas, pero no sabemos de su uso fuera de ambientes académicos."
+
+#: i2p2www/pages/site/comparison/other-networks.html:153
+#, fuzzy, python-format
+msgid ""
+"\n"
+"Mixminion and Mixmaster are networks to support anonymous email against a"
+" very\n"
+"powerful adversary.\n"
+"High-latency messaging applications running on top of I2P\n"
+"(for example Syndie or I2PBote)\n"
+"may perhaps prove adequate to meet the threat\n"
+"model of those adversaries, while running in parallel along side the "
+"needs of low latency users, to provide\n"
+"a significantly larger anonymity set.\n"
+"High-latency support within the I2P router itself may or may not be added"
+" in a distant future release.\n"
+"It is too early to say if I2P will meet the needs of users requiring "
+"extreme protection for email."
+msgstr ""
+"\n"
+"Mixminion y Mixmaster son redes para el envío anónimo de emails. "
+"Aplicaciones de envío de mensajes de baja latencia sobre I2P (por ejemplo"
+" Syndie o I2PBote) podrían ser "
+"adecuadas para ese modelo de amenazas, ya que corriendo en paralelo "
+"cubren las necesidades de la baja latencia y crean una gran capa de "
+"anonimato. Soporte para alta latencia en los ruters de I2P puede que se "
+"añada en un futuro distante, o puede que no. Es demasiado pronto para "
+"decir si I2P podrá cubrir las necesidades de los usuarios con necesidades"
+" de protección extrema para sus emails."
+
+#: i2p2www/pages/site/comparison/other-networks.html:165
+msgid ""
+"As with Tor and Onion Routing, \n"
+"both Mixminion and Mixmaster take the directory based approach as well."
+msgstr ""
+"Al igual que con Tor y Onion routing, Mixminion y Mixmaster toman también"
+" la aproximación basada en directorios."
+
+#: i2p2www/pages/site/comparison/other-networks.html:175
+#, python-format
+msgid ""
+"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
+"web requests,\n"
+"and as such it has a few centralized nodes (participants in the cascade) "
+"that blend\n"
+"and mix requests from clients through the sequence of nodes (the cascade)"
+" before \n"
+"proxying out onto the web.  The scope, threat model, and security is "
+"substantially \n"
+"different from I2P, but for those who don't require significant anonymity"
+" but still\n"
+"are not satisfied with an Anonymizer-like service, JAP is worth "
+"reviewing.  One\n"
+"caution to note is that anyone under the jurisdiction of the German "
+"courts may want\n"
+"to take care, as the German Federal Bureau of Criminal Investigation "
+"(FBCI) has \n"
+"successfully mounted an \n"
+"attack \n"
+"on the network.  Even though the method of this attack was later found to"
+" be illegal \n"
+"in the German courts, the fact that the data was successfully collected "
+"is the \n"
+"concern.  Courts change their minds based upon circumstance, and this is "
+"evidence that \n"
+"if a government body or intelligence agency wanted to, they could gather "
+"the data, even \n"
+"if it may be found inadmissible in some courts later)"
+msgstr ""
+"JAP (Proxy Anónimo en Java) es una red de mezcla en cascadas para el "
+"anonimato de las solicitudes web que tiene varios nodos centrales "
+"(participantes en la cascada) que combinan y mezclan las solicitudes de "
+"los clientes a través de una secuencia de nodos (la cascada) antes de "
+"enviarlos por un proxy a la web. El alcance, modelo de amenazas y la "
+"seguridad son bastantes diferentes a las de I2P, pero para aquellos que "
+"requieran bastante anonimato pero no están satisfechos con un servicio de"
+" tipo anonimizador, puede venirles bien echarle un ojo a JAP. Un "
+"precaución que debe tener todo aquel que se encuentre bajo la "
+"jurisdicción de  los juzgados alemanes, es que el German Federal Bureau "
+"of Criminal Investigation (FBCI) ha montado un ataque con éxito sobre esta red. Incluso aunque el "
+"ataque se encontró más tarde ilegal en los juzgados alemanes, la realidad"
+" es que la información fue sustraída con éxito. Los jueces cambian sus "
+"mentes basados en las circunstancias, y esta es la evidencia de que si el"
+" gobierno quisiese la información podrían conseguirla, aunque fuese "
+"inadmisible más tarde en un juicio)"
+
+#: i2p2www/pages/site/comparison/other-networks.html:197
+#, python-format
+msgid ""
+"Both of these systems work through the same basic \n"
+"antnet routing, providing some degree of\n"
+"anonymity based on the threat model of providing plausible deniability "
+"against a simple \n"
+"non-colluding adversary.  With the antnet routing, they first either do a"
+" random walk or a \n"
+"broadcast search to find some peer with the data or identity desired, and"
+" then use a feedback\n"
+"algorithm to optimize that found path.  This works well for applications "
+"that merely want to know \n"
+"what other people around them have to offer - \"How are y'all doing\" vs."
+" \"Hey Alice, how are you\" - \n"
+"you basically get a local cluster of nodes that can share files with and "
+"maintain some degree of \n"
+"anonymity (though you don't have much control over who is in that group "
+"of peers)."
+msgstr ""
+"Estos dos sistemas trabajan con el rutado básico antnet, proporcionando anonimato al proveer "
+"negación plausible contra un simple adversario sin colisión. Con el "
+"rutado antnet, primero hacen una ruta aleatoria o una búsqueda broadcast"
+"  para encontrar  el par o la identidad deseada, y después usan esa "
+"algoritmo para optimizar la ruta. Esto funciona bien para aplicaciones "
+"que sólo quieren saber que tienen que ofrecer la gente que está alrededor"
+" - \"Cómo os va\" contra \"Hey Alice, como estás\" - básicamente se "
+"obtiene un conjunto de nodos que pueden compartit archivos y mantener el "
+"anonimato (aunque no se tiene mucho control sobre quién es ese grupo de "
+"pares)."
+
+#: i2p2www/pages/site/comparison/other-networks.html:209
+msgid ""
+"However, the algorithm does not scale well at all - if the application "
+"wants to speak with a \n"
+"particular peer it ends up doing a broadcast search or random walk "
+"(though if they are lucky enough\n"
+"for that to succeed, the antnet routing should optimize that found "
+"connection).  This means that \n"
+"while these networks can work great at small scales, they are not "
+"suitable for large networks where\n"
+"someone wants to get in touch with another specific peer.  That does not "
+"mean that there is no \n"
+"value in these systems, just that their applicability is limited to "
+"situations where their \n"
+"particular issues can be addressed."
+msgstr ""
+"Sin embargo, el algoritmo no escala bien del todo - si la aplicación "
+"quiere hablar con un par en particular termina haciendo una búsqueda "
+"broadcast o un paseo aleatorio (si son afortunados de que eso ocurra). "
+"Esto significa que mientras esas redes trabajan bien a escalas pequeñas, "
+"no son apropiadas para redes grandes donde alguien quiere ponerse en "
+"contacto con un par en particular. Esto no quiere decir que este sistema "
+"no tenga ningún valor, sólo que su aplicación está limitada a situaciones"
+" donde sus problemas pueden evitarse."
+
+#: i2p2www/pages/site/comparison/other-networks.html:220
+#, python-format
+msgid ""
+"This was a closed-source network targeted at Iranian users.\n"
+"Tor did a good writeup on what to look for in a "
+"circumvention tool.\n"
+"Suffice it to say that being closed source and publicly targeting a "
+"specific country are not good ideas.\n"
+"I2P is, of course, open source. However, that source, and our\n"
+"technical documentation, need much more review."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:229
+msgid "Paid VPN Services"
+msgstr "Servicios VPN de pago"
+
+#: i2p2www/pages/site/comparison/other-networks.html:230
+#: i2p2www/pages/site/comparison/other-networks.html:236
+#, fuzzy, python-format
+msgid ""
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+"Puede contribuir con análisis creando un nuevo ticket en %(trac)s."
+
+#: i2p2www/pages/site/comparison/other-networks.html:235
+msgid "Others"
+msgstr "Otros"
+
+#: i2p2www/pages/site/comparison/tor.html:2
+msgid "I2P Compared to Tor"
+msgstr "Comparación de I2P con Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:8
+#, python-format
+msgid ""
+"Tor and Onion Routing are both anonymizing proxy networks, \n"
+"allowing people to tunnel out through their low latency mix \n"
+"network. The two primary differences between Tor / \n"
+"Onion-Routing and I2P are again related to differences in \n"
+"the threat model and the out-proxy design (though Tor\n"
+"supports hidden services as well).  In addition, Tor\n"
+"takes the directory-based approach - providing a \n"
+"centralized point to manage the overall 'view' of the \n"
+"network, as well as gather and report statistics, as \n"
+"opposed to I2P's distributed network \n"
+"database and peer selection."
+msgstr ""
+"Tor y el rutado Onion son ambas redes de proxies anónimas, que permiten a"
+" la gente salir a través de su red ya mezclada de baja latencia. Las dos "
+"primeras diferencias entre Tor/Onion-Routing e I2P están de nuevo "
+"relacionas con las diferencias en el modelo de amenazas y el diseño de "
+"los outproxies (a través de Tor soporta también servicios ocultos). "
+"Además, Tor usa un enfoque basado en  directorios - creando un punto "
+"central para manejar la 'vista' general de las redes, y además se "
+"obtienen más estadísticas, al contrario que la base"
+" de datos de la red  dsitribuida de I2P y la selección de pares."
+
+#: i2p2www/pages/site/comparison/tor.html:22
+msgid ""
+"The I2P/Tor outproxy functionality does have a few \n"
+"substantial weaknesses against certain attackers - \n"
+"once the communication leaves the mixnet, global passive\n"
+"adversaries can more easily mount traffic analysis.  In \n"
+"addition, the outproxies have access to the cleartext \n"
+"of the data transferred in both directions, and \n"
+"outproxies are prone to abuse, along with all of the \n"
+"other security issues we've come to know and love with \n"
+"normal Internet traffic."
+msgstr ""
+"El outproxy de I2P/Tor tiene varias debilidades contra cierto tipo de "
+"ataques - una vez que la comunicación deja la red Tor, adversarios "
+"pasivos pueden hacer más fácilmente ataques de análisis. Además los "
+"outproxies tienen acceso al texto en claro transferido en las dos "
+"direcciones, y los outproxies son propensos a abusos, y además tenemos "
+"que tener en cuenta otros ataques posibles dentro del Internet normal."
+
+#: i2p2www/pages/site/comparison/tor.html:34
+msgid ""
+"However, many people don't need to worry about those \n"
+"situations, as they are outside their threat model.  It\n"
+"is, also, outside I2P's (formal) functional scope (if people want\n"
+"to build outproxy functionality on top of an anonymous\n"
+"communication layer, they can).  In fact, some I2P users\n"
+"currently take advantage of Tor to outproxy."
+msgstr ""
+"Aún así, mucha gente no tiene por que preocuparse por estas situaciones, "
+"ya que no están dentro del modelo de amenazas. Y además esto está fuera "
+"del alcance (formal) de I2P (si la gente desea construir un outproxy "
+"sobre la capa de comunicación anónima, pueden hacerlo). De hecho, "
+"actualmente  algunos usuarios utilizan el outproxy de Tor."
+
+#: i2p2www/pages/site/comparison/tor.html:48
+msgid "Comparison of Tor and I2P Terminology"
+msgstr "Comparación de la terminología de I2P y Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:49
+msgid ""
+"While Tor and I2P are similar in many ways, much of the terminology is "
+"different."
+msgstr ""
+"Mientras que Tor e I2p tienen algunas similitudes, mucha de la "
+"terminología cambia."
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Cell"
+msgstr "Celda"
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Message"
+msgstr "Mensaje"
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Client"
+msgstr "Cliente"
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Router or Client"
+msgstr "Ruter o Cliente"
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Circuit"
+msgstr "Circuito"
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Tunnel"
+msgstr "Túnel"
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "Directory"
+msgstr "Directorio"
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "NetDb"
+msgstr "NetDb, base de datos de la red"
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Directory Server"
+msgstr "Servidor de directorios"
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Floodfill Router"
+msgstr "Ruter Floodfill o de relleno"
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Entry Guards"
+msgstr "Control de entradas"
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Fast Peers"
+msgstr "Pares rápidos"
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Entry Node"
+msgstr "Nodo de entrada"
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Inproxy"
+msgstr "Inproxy, proxy de entrada"
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Exit Node"
+msgstr "Nodo de salida"
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Outproxy"
+msgstr "Outproxy, o proxy de salida"
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Hidden Service"
+msgstr "Servicio oculto"
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Eepsite or Destination"
+msgstr "Eepsite o destinación"
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "Hidden Service Descriptor"
+msgstr "Descriptor de servicio oculto"
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "LeaseSet"
+msgstr "LeaseSet"
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Introduction point"
+msgstr "Punto de introducción"
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Inbound Gateway"
+msgstr "Puerta de salida de entrada"
+
+#: i2p2www/pages/site/comparison/tor.html:65
+msgid "Node"
+msgstr "Nodo"
+
+#: i2p2www/pages/site/comparison/tor.html:65
+#: i2p2www/pages/site/comparison/tor.html:67
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Router"
+msgstr "Ruter"
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "Onion Proxy"
+msgstr "Proxy Onion"
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "I2PTunnel Client (more or less)"
+msgstr "Cliente de I2PTunnel (más o menos)"
+
+#: i2p2www/pages/site/comparison/tor.html:67
+msgid "Relay"
+msgstr "Relay"
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "Rendezvous Point"
+msgstr "Punto de reunión"
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "somewhat like Inbound Gateway + Outbound Endpoint"
+msgstr ""
+"algo así como inbound Gateway + Outbound Endpoint, puerta de salida de "
+"entrada + punto final de salida"
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "Router Descriptor"
+msgstr "Descriptor del ruter"
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "RouterInfo"
+msgstr "Información del ruter"
+
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Server"
+msgstr "Servidor"
+
+#: i2p2www/pages/site/comparison/tor.html:73
+msgid "Benefits of Tor over I2P"
+msgstr "Beneficios de Tor sobre I2p"
+
+#: i2p2www/pages/site/comparison/tor.html:76
+msgid ""
+"Much bigger user base; much more visibility in the academic and hacker "
+"communities; benefits from\n"
+"formal studies of anonymity, resistance, and performance;\n"
+"has a non-anonymous, visible, university-based leader"
+msgstr ""
+"El número de usuarios es mucho mayor; mucho más visible en entorno "
+"académicos y comunidades de hackers; tiene los beneficios de tener "
+"estudios formales sobre el anonimato, resistencia y rendimiento; y tienen"
+" un líder no anónimo universitario y visible"
+
+#: i2p2www/pages/site/comparison/tor.html:82
+msgid "Has already solved some scaling issues I2P has yet to address"
+msgstr "Ha resuelto ya algunos problemas de escalado que I2P aún debe arreglar. "
+
+#: i2p2www/pages/site/comparison/tor.html:83
+msgid "Has significant funding"
+msgstr "Tiene muchos fondos"
+
+#: i2p2www/pages/site/comparison/tor.html:84
+msgid "Has more developers, including several that are funded"
+msgstr "Tiene más desarrolladores, incluso algunos con fondos"
+
+#: i2p2www/pages/site/comparison/tor.html:86
+msgid ""
+"More resistant to state-level blocking due to TLS transport layer and "
+"bridges\n"
+"(I2P has proposals for \"full restricted routes\" but these are not yet "
+"implemented)"
+msgstr ""
+"Tiene un bloqueo de nivel de estado más resistente debido la capa de "
+"transporte TLS y a los puentes (I2P tienen propuestas de \"rutas "
+"completamente restringidas\" pero estas aún no están implementadas)"
+
+#: i2p2www/pages/site/comparison/tor.html:91
+msgid "Big enough that it has had to adapt to blocking and DOS attempts"
+msgstr "Es tan grande que incluso se ha adaptado para bloquear los intentos de DOS"
+
+#: i2p2www/pages/site/comparison/tor.html:92
+msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
+msgstr ""
+"Diseñado para optimizar el tráfico de salida, con un gran número de nodos"
+" de salida"
+
+#: i2p2www/pages/site/comparison/tor.html:94
+msgid ""
+"Better documentation, has formal papers and specifications,\n"
+"better website, many more translations"
+msgstr ""
+"Mejor documentación, tiene estudios formales y especificaciones, una web "
+"mejor, y muchas traducciones"
+
+#: i2p2www/pages/site/comparison/tor.html:99
+msgid "More efficient with memory usage"
+msgstr "Más eficiente con el uso de la memoria"
+
+#: i2p2www/pages/site/comparison/tor.html:100
+msgid "Tor client nodes have very low bandwidth overhead"
+msgstr "Los nodos cliente de Tor tienen muy poco gasto de ancho de nada"
+
+#: i2p2www/pages/site/comparison/tor.html:102
+msgid ""
+"Centralized control reduces the complexity at each\n"
+"node and can efficiently address Sybil attacks"
+msgstr ""
+"El control centralizado reduce la complejidad de cada nodo y puede evitar"
+" ataques Sybil fácilmente"
+
+#: i2p2www/pages/site/comparison/tor.html:108
+msgid ""
+"A core of high capacity nodes provides higher\n"
+"throughput and lower latency"
+msgstr ""
+"Un núcleo de nodos de gran capacidad proporciona una mayor rendimiento y "
+"menor latencia"
+
+#: i2p2www/pages/site/comparison/tor.html:113
+msgid "C, not Java (ewww)"
+msgstr "C, no java (ey!)"
+
+#: i2p2www/pages/site/comparison/tor.html:116
+msgid "Benefits of I2P over Tor"
+msgstr "Beneficios de I2P sobre Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:118
+msgid ""
+"Designed and optimized for hidden services, which are much faster than in"
+" Tor"
+msgstr ""
+"Diseñado para optimizar los servicios ocultos, que son mucho más rápidos "
+"que los de Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:119
+msgid "Fully distributed and self organizing"
+msgstr "Totalmente distribuido y auto organizado"
+
+#: i2p2www/pages/site/comparison/tor.html:121
+msgid ""
+"Peers are selected by continuously profiling and ranking performance,\n"
+"rather than trusting claimed capacity"
+msgstr ""
+"Los pares son seleccionados continuamente según el rendimiento y "
+"categoría, en vez de confiar en la capacidad indicada"
+
+#: i2p2www/pages/site/comparison/tor.html:127
+msgid ""
+"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
+"rather than hardcoded"
+msgstr ""
+"Los pares Floodfill (\"servidores de directorios\") cambian, en vez de "
+"estar siempre fijos."
+
+#: i2p2www/pages/site/comparison/tor.html:132
+msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
+msgstr "Tan pequeña que no ha sido bloqueada o Dosed."
+
+#: i2p2www/pages/site/comparison/tor.html:133
+msgid "Peer-to-peer friendly"
+msgstr "Amigable con las aplicaciones p2p"
+
+#: i2p2www/pages/site/comparison/tor.html:134
+msgid "Packet switched instead of circuit switched"
+msgstr "Conmutado por paquete en vez de conmutado por circuito"
+
+#: i2p2www/pages/site/comparison/tor.html:137
+msgid ""
+"implicit transparent load balancing of messages \n"
+"across multiple peers, rather than a single path"
+msgstr ""
+"Implica control de carga transparente de los mensajes a través de "
+"múltiples pares, en vez de por un sólo camino."
+
+#: i2p2www/pages/site/comparison/tor.html:143
+msgid ""
+"resilience vs. failures by running multiple \n"
+"tunnels in parallel, plus rotating tunnels"
+msgstr ""
+"Resistencia contra fallos ya que usa varios túneles en paralelo, además "
+"de rotar los túneles"
+
+#: i2p2www/pages/site/comparison/tor.html:149
+msgid ""
+"scale each client's connections at O(1) instead \n"
+"of O(N) (Alice has e.g. 2 inbound tunnels that are \n"
+"used by all of the peers Alice is talking with, \n"
+"rather than a circuit for each)"
+msgstr ""
+"el número de conexiones en i2p vienen dado por O(1) en vez de O(N) (por "
+"ejemplo, Alice tiene 2 túneles de entrada que son usados por todos los "
+"pares con lo que habla Alice, en vez de un circuito por cada par)"
+
+#: i2p2www/pages/site/comparison/tor.html:159
+msgid ""
+"Unidirectional tunnels instead of bidirectional\n"
+"circuits, doubling the number of nodes a peer has to\n"
+"compromise to get the same information."
+msgstr ""
+"Túneles unidireccionales en vez de circuitos bidireccionales, usando el "
+"doble de nodos un par se compromete más para obtener la misma "
+"información."
+
+#: i2p2www/pages/site/comparison/tor.html:166
+msgid ""
+"Protection against detecting client activity, even\n"
+"when an attacker is participating in the tunnel, as\n"
+"tunnels are used for more than simply passing end \n"
+"to end messages (e.g. netDb, tunnel management, \n"
+"tunnel testing)"
+msgstr ""
+"Protección contra la detección de la actividad de un cliente, incluso "
+"cuando un atacante participa en el túnel, ya que los túneles no son sólo "
+"usados para pasar el mensaje de punto a punto (por ejemplo, netDB, "
+"administración de túneles, pruebas en los túneles)"
+
+#: i2p2www/pages/site/comparison/tor.html:175
+msgid ""
+"Tunnels in I2P are short lived, decreasing the number\n"
+"of samples that an attacker can use to mount an \n"
+"active attack with, unlike circuits in Tor, which are\n"
+"typically long lived."
+msgstr ""
+"Los túneles de I2P tienen una vida corta, reduciendo el número de "
+"muestras que un atacante puede usar para lograr un ataque activo, al "
+"contrario que con los circuitos en Tor, que son típicamente de larga "
+"duración."
+
+#: i2p2www/pages/site/comparison/tor.html:183
+msgid ""
+"I2P APIs are designed specifically for anonymity and\n"
+"security, while SOCKS is designed for functionality."
+msgstr ""
+"Los APIs de I2P están específicamente diseñados para el anonimato y la "
+"seguridad, mientras que SOCKS está diseñado para su funcionalidad."
+
+#: i2p2www/pages/site/comparison/tor.html:188
+msgid "Essentially all peers participate in routing for others"
+msgstr "Básicamente todos los pares participan en el rutado de otros"
+
+#: i2p2www/pages/site/comparison/tor.html:190
+msgid ""
+"The bandwidth overhead of being a full peer is low, \n"
+"while in Tor, while client nodes don't require much\n"
+"bandwidth, they don't fully participate in the mixnet."
+msgstr ""
+"El uso de ancho de banda de cualquier par completo es bajo, mientras que "
+"en Tor, aunque un nodo cliente no necesita mucho ancho de banda, "
+"realmente no participan completamente en la red."
+
+#: i2p2www/pages/site/comparison/tor.html:196
+msgid "Integrated automatic update mechanism"
+msgstr "Sistema integrado de actualizaciones automáticas"
+
+#: i2p2www/pages/site/comparison/tor.html:197
+msgid "Both TCP and UDP transports"
+msgstr "Ambos tipos de transporte, TCP y UDP"
+
+#: i2p2www/pages/site/comparison/tor.html:198
+msgid "Java, not C (ewww)"
+msgstr "Java, en vez de C (ewww)"
+
+#: i2p2www/pages/site/comparison/tor.html:201
+msgid "Other potential benefits of I2P but not yet implemented"
+msgstr "Otros beneficios potenciales de I2P aún no implementados"
+
+#: i2p2www/pages/site/comparison/tor.html:202
+msgid "...and may never be implemented, so don't count on them!"
+msgstr ""
+"...y puede ser que nunca lleguen a ser implementados, ¡osea que no cuente"
+" con ellos!"
+
+#: i2p2www/pages/site/comparison/tor.html:205
+msgid ""
+"Defense vs. message count analysis by garlic wrapping \n"
+"multiple messages"
+msgstr ""
+"Defensa contra el análisis de conteo de mensajes envolviendo múltiples "
+"mensajes dentro de la red garlic"
+
+#: i2p2www/pages/site/comparison/tor.html:211
+msgid ""
+"Defense vs. long term intersection by adding delays \n"
+"at various hops (where the delays are not discernible\n"
+"by other hops)"
+msgstr ""
+"Defensa contra la intersección a largo plazo añadiendo demoras en varios "
+"saltos (donde las demoras no son perceptibles por los otros saltos)"
+
+#: i2p2www/pages/site/comparison/tor.html:218
+msgid ""
+"Various mixing strategies at the tunnel level (e.g.\n"
+"create a tunnel that will handle 500 messages / minute,\n"
+"where the endpoint will inject dummy messages if there\n"
+"are insufficient messages, etc)"
+msgstr ""
+"Varias estrategias de mezclado a nivel del túnel (por ejemplo, creando "
+"túneles que  manejarán 500 mensajes al minuto, donde el punto final "
+"inyectará mensajes de relleno si no hubiese suficientes mensajes, etc)"
+
diff --git a/i2p2www/translations/es/LC_MESSAGES/messages.po b/i2p2www/translations/es/LC_MESSAGES/docs.po
similarity index 54%
rename from i2p2www/translations/es/LC_MESSAGES/messages.po
rename to i2p2www/translations/es/LC_MESSAGES/docs.po
index f710158d..0c1a664c 100644
--- a/i2p2www/translations/es/LC_MESSAGES/messages.po
+++ b/i2p2www/translations/es/LC_MESSAGES/docs.po
@@ -3,19 +3,19 @@
 # This file is distributed under the same license as the I2P project.
 #
 # Translators:
-# Adolfo Jayme , 2013
+# Fito Jayme , 2013
 # Daniel Mustieles , 2013
 # m1xxy , 2011
 # olivertrash , 2013
-# strel , 2013
+# strel, 2013
 # trolly, 2013
 msgid ""
 msgstr ""
 "Project-Id-Version:  I2P\n"
-"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
-"POT-Creation-Date: 2013-07-03 03:49+0000\n"
-"PO-Revision-Date: 2013-07-02 10:52+0000\n"
-"Last-Translator: trolly\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-12-17 20:53+0000\n"
+"Last-Translator: strel\n"
 "Language-Team: Spanish "
 "(http://www.transifex.com/projects/p/I2P/language/es/)\n"
 "Plural-Forms: nplurals=2; plural=(n != 1)\n"
@@ -24,7419 +24,12 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 "Generated-By: Babel 0.9.6\n"
 
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:24
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:25
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:12
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:12
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:17
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:16
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:16
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:26
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:19
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:19
-msgid "Files are available on the `download page`_."
-msgstr "Los archivos están disponibles en la `página de descargas`_."
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:28
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:15
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:29
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:16
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:16
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:21
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:20
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:20
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:30
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:23
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:23
-msgid "`download page`"
-msgstr "`Página de Descargas`"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:30
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:17
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:31
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:18
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:19
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:18
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:22
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:22
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:32
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:25
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:79
-msgid "RELEASE DETAILS"
-msgstr "DETALLES DEL LANZAMIENTO"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:32
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:19
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:33
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:40
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:50
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:24
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:24
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:34
-msgid "Major Changes"
-msgstr "Cambios más importantes"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:44
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:24
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:43
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:55
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:47
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:58
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:43
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:32
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:30
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:39
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:81
-msgid "Bug Fixes"
-msgstr "Correcciones de errores"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:54
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:30
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:47
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:69
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:63
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:68
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:54
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:41
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:36
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:51
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:43
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:94
-msgid "Other"
-msgstr "Otro"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:73
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:36
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:51
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:82
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:75
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:96
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:76
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:52
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:56
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:67
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:56
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:110
-msgid "SHA256 Checksums:"
-msgstr "Sumas de comprobación SHA256:"
-
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39
-msgid "Major changes"
-msgstr "Cambios mayores"
-
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47
-msgid "Wrapper Update"
-msgstr ""
-
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:23
-msgid "Update Info"
-msgstr "Información de la actualización"
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2
-msgid "0.9.2 Release"
-msgstr "Versión 0.9.2"
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9
-msgid ""
-"0.9.2 includes extensive low-level changes to improve the performance and"
-" efficiency of the router. We have updated our UPnP library, to hopefully"
-" make UPnP work for more people. I2PSnark now has DHT support, but it is "
-"not yet enabled by default, as we plan to do more testing during the "
-"upcoming 0.9.3 development cycle."
-msgstr ""
-"0.9.2 incluye muchos cambios de bajo nivel para la mejora y eficiencia "
-"del ruter. Hemos actualizado la librería UPnP, para hacer que UPnP "
-"funcione para mas gente. I2PSnark ahora soporta DHT, pero no está activo "
-"por defecto, ya que tenemos planeado hacer más pruebas durante la el "
-"próximo ciclo de desarrollo de 0.9.3"
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12
-msgid ""
-"As usual, there's also lots of bug fixes in this release, so updating is "
-"recommended."
-msgstr ""
-"Como es habitual, hay muchos cambios y arreglos en esta versión, "
-"recomendamos actualizar."
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26
-msgid ""
-"SSU: Fix several problems in our UDP transport, to improve efficiency and"
-" reliability for connection setup. Also improve defenses against various "
-"types of bad input."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27
-msgid ""
-"UPnP: Updated our library to fix several issues, should work for more "
-"routers now"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28
-msgid ""
-"Transport: Improve performance in both our TCP and UDP transports, to "
-"benefit high-bandwidth routers"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29
-msgid ""
-"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered "
-"are now much more flexible, which should lessen protocol overhead and "
-"reduce stalls caused by dropped tags."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30
-msgid ""
-"I2PSnark: Add DHT support, not yet enabled by default, will do further "
-"testing and plan to enable by default in 0.9.3."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34
-msgid ""
-"Fix various issues affecting memory usage and performance on high-"
-"bandwidth routers"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35
-msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36
-msgid "Fix i2psnark bug that prevented a completion announcement to the tracker"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37
-msgid "Fix a lock contention problem in i2ptunnel"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38
-msgid "Fix some OSX installation issues"
-msgstr "Corregidos algunos problemas de instalación en OSX"
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39
-msgid "Remove uses of direct byte buffers that may have been leaking"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43
-msgid "Reduce overhead in network messages"
-msgstr "Reducida la sobrecarga en los mensajes de la red"
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44
-msgid "Add \"universal\" theme support"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45
-msgid "Theme updates"
-msgstr "Actualizaciones del tema"
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46
-msgid "Add a jbigi library for Raspberry Pi"
-msgstr "Añadida una biblioteca jbigi para Raspberry Pi"
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47
-msgid "New Scala unit test framework"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48
-msgid "Translation updates for Czech, Dutch, German, and Greek"
-msgstr "Actualizaciones de las traducciones al checo, holandés, alemán y griego"
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49
-msgid "Update wrapper to 3.5.15 (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108
-msgid "Update GeoIP data (new installs and PPA only)"
-msgstr "Actualizar datos de geolocalización IP (Sólo PPA y nuevas instalaciones)"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:2
-msgid "0.9.3 Release"
-msgstr "Versión 0.9.3"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9
-msgid ""
-"0.9.3 includes extensive low-level changes to the queueing of messages in"
-" the router.  We implement the CoDel Active Queue Management (AQM) "
-"algorithm.  We also unify the queueing and priority mechanisms in the "
-"transports to aid diagnosis and reduce network latency.  Work continues "
-"on fixing UDP transport bugs and making UDP more resistant to attacks.  "
-"There are more changes to improve the performance of the router and "
-"reduce its memory usage.  Also, we enable i2psnark's DHT support, "
-"introduced last release, by default."
-msgstr ""
-"0.9.3 incluye muchos arreglos de bajo nivel en la cola de mensajes en el "
-"ruter. Hemos implementado el algoritmo CoDel Active Queue Management "
-"(AQM). También hemos unificado los mecanismos de prioridades y colas en "
-"los transportes para ayudar al diagnóstico y reducir la latencia de la "
-"red. El trabajo continua arreglando el transporte UDP haciéndolo mas "
-"resistente a los ataques. Hay mas cambios para mejorar el rendimiento del"
-" ruter y reducir el uso de memoria. Además, hemos habilitado por defecto "
-"el suporte, introducido en la versión anterior, para DHT en i2psnark."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26
-msgid "Active Queue Management"
-msgstr "Gestión de cola activa"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:27
-msgid "Priority queues"
-msgstr "Listas de prioridades."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28
-msgid "I2PSnark DHT: Several bug fixes, enable by default."
-msgstr "DHT de I2PSnark: Solución de varios errores, activo por defecto."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32
-msgid ""
-"Several SSU fixes including memory leak, and better handling of routers "
-"behind firewalls that change UDP ports; additional defenses for malicious"
-" packets."
-msgstr ""
-"Varios arreglos en el SSU incluyendo la fuga de memoria, y mejor manejo "
-"de de los ruters detrás de cortafuegos que han cambiado sus puertos UDP; "
-"defensa extra contra paquetes maliciosos."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33
-msgid "Fix piece selection (rarest-first) bugs in i2psnark"
-msgstr ""
-"Solucionar fallos en la selección de porciones (las más raras primero) en"
-" i2psnark"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34
-msgid "Fix bug causing multiple browsers to open at startup"
-msgstr ""
-"Arreglo del error que causaba que se abriesen varios navegadores al "
-"iniciar."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38
-msgid "Improvements in caching"
-msgstr "Mejoras en almacenamiento en caché"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39
-msgid "Several synchronization fixes and lock contention reduction"
-msgstr ""
-"Varios arreglos en la sincronización y reducción de la contención del "
-"bloqueo"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40
-msgid "Major reduction in SSU buffers memory use"
-msgstr "Gran reducción en el uso de buffers de memoria en SSU"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41
-msgid ""
-"Fix streaming connection timeout back to 1 minute, was inadvertently "
-"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was"
-" unlimited"
-msgstr ""
-"Revertir tiempo máximo de respuesta de la conexión a 1 minuto, fue "
-"cambiado inadvertidamente a 5 minutos; establecer el tiempo máximo de "
-"lectura del servidor i2ptunnel, era ilimitado."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42
-msgid "Improved defenses in i2ptunnel for \"darkloris\""
-msgstr "Defensas mejoradas en i2ptunnel para \"darkloris\""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:43
-msgid "More validation at torrent creation in i2psnark"
-msgstr "Más verificación a la creación del torrent en i2psnark"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44
-msgid "Several parameter changes in SSU to improve throughput"
-msgstr "Varios cambios de parámetro en SSU para mejorar el rendimiento"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45
-msgid ""
-"New event log for major events including restarts; show multiple restart "
-"lines on graphs"
-msgstr ""
-"Nuevo registro de eventos para eventos principales incluyendo reinicios; "
-"muestra múltiples líneas de reinicio en los gráficos."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46
-msgid "Remove duplicate messages from logs"
-msgstr "Eliminar mensajes duplicados de los registros"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47
-msgid "Don't respond to blocked streaming connections with a reset, just drop"
-msgstr ""
-"No responder a conexiones de flujos multimedia (streaming) bloqueadas con"
-" un restablecimiento, simplemente desistir."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48
-msgid "Remove all uses of inefficient SimpleTimer"
-msgstr "Eliminar todos los usos del inficiente SimpleTimer"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49
-msgid "More checks for valid IPs and ports entered in console"
-msgstr "Más verificaciones de IPs y puertos válidos introducidos en la consola"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50
-msgid "Fix bug that wasted a lot of entropy"
-msgstr "Solucionar fallo que desperdiciaba mucha entropía"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51
-msgid "Translation updates: Italian, Portuguese, Spanish, Swedish"
-msgstr "Actualizaciones de traducciones: italiano, portugués, español y sueco"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52
-msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5"
-msgstr ""
-"Añadir configuración que NO es del tipo NIO a Jetty.xml, recomendado a "
-"partir de Java 5"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2
-msgid "0.9.4 Release"
-msgstr "Versión 0.9.4"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9
-msgid ""
-"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, "
-"that was reducing network performance and reliability. It also includes "
-"major changes in the in-network update system, and adds the capability to"
-" update via in-network torrents."
-msgstr ""
-"0.9.4 incluye un arreglo de la capacidad de la red, introducido en 0.9.2,"
-" que estaba reduciendo el rendimiento y estabilidad de la red. Además "
-"incluye cambios en el sistema de actualización de la red, y añade la "
-"capacidad de actualizar a través de torrents de dentro de la red I2P."
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13
-msgid ""
-"We fixed several bugs in the i2psnark DHT implementation that was "
-"introduced\n"
-"last release. For those of you using console or http proxy passwords,\n"
-"we converted to the more-secure digest method and improved the security "
-"for console forms."
-msgstr ""
-"Hemos arreglado varios errores en los cambios introducidos de la última "
-"versión liberada.\n"
-"Para todos quienes usáis consola o proxy's http con contraseña, hemos "
-"aumentado y mejorado la seguridad para los formularios de consola"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19
-msgid ""
-"For those of you already running development builds, your router should "
-"automatically\n"
-"update to 0.9.4-0 using the new in-network torrent facility.\n"
-"For those running 0.9.3-0, you will update normally using in-network "
-"HTTP, and\n"
-"we will have more information for you when we release 0.9.5."
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36
-msgid ""
-"Big rework of the update system; Preliminary support for updates via "
-"i2psnark"
-msgstr ""
-"Gran trabajo supervisado para la actualización del sistema; soporte "
-"preliminar para actualizaciones vía i2psnark"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37
-msgid "Add per-destination outbound priorities"
-msgstr "Añadir"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41
-msgid ""
-"Fix major bug that reduced SSU connection limits which reduced tunnel "
-"build success rates"
-msgstr ""
-"Arreglado un error grave para reducir el límite de conexión SSU, el cual "
-"reducía las posibilidades de éxito al crear un tunel"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42
-msgid "Fix bug with external I2CP that prevented some external apps from working"
-msgstr ""
-"Corregido un error del panel de control i2P EXTERNO que impedía el "
-"funcionamiento de aplicaciones externas"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43
-msgid "Fixed several bugs in i2psnark DHT"
-msgstr "Corregidos varios errorres en i2psnark DHT"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44
-msgid "Fixed bug in i2psnark PEX that inflated peer counts"
-msgstr "Corregido un error en ip2snark PEX que descuadraba los pares de cuentas"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45
-msgid "Handle dropped I2CP messages better"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46
-msgid "Reduce overhead of I2CP messages"
-msgstr "Reducir la sobrecarga de mensajes del panel de control I2P (I2CP)"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47
-msgid "Enforce max size in transport outbound message queues"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48
-msgid "Fixes for Windows eepget.bat (new installs and PPA only)"
-msgstr ""
-"Correcciones para el archivo de Windows \"eepget.bat\" (sólo PPA y nuevas"
-" instalaciones)"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49
-msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53
-msgid ""
-"More performance improvements, memory reduction, and object churn "
-"reduction"
-msgstr ""
-"Otras optimizaciones de rendimiento, reducción de memoria y de los "
-"objetos CHURN "
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54
-msgid "Better detection of network disconnections"
-msgstr "Mejor detección de caídas y desconexión de red"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55
-msgid "Further improvements in the SSU transport"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56
-msgid "Add console password form"
-msgstr "Añadido formulario de contraseña en consola"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57
-msgid ""
-"Convert http proxy and console from basic to digest authentication for "
-"added security"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58
-msgid ""
-"Improved verification of console form submissions, using jsp sessions. "
-"Cookies may now be required on forms, except when the console password is"
-" enabled"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59
-msgid ""
-"Initial work on new interfaces to manage applications started via "
-"clients.config"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60
-msgid "Increase minimum peer port to 1024"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61
-msgid "Increase granularity of bandwidth limiter for smoother transmissions"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62
-msgid ""
-"Translation updates: Chinese, French, German, Italian, Polish, "
-"Portuguese, Swedish, and Ukrainian"
-msgstr ""
-"Traducciones actualizadas: chino, francés, alemán, italiano, polaco, "
-"portugués, sueco y ucraniano"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64
-msgid "Update wrapper to 3.5.16 (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65
-msgid "New ARMv6 wrapper for Raspberry Pi"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:2
-msgid "0.9.5 Release"
-msgstr "Versión 0.9.5"
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9
-msgid ""
-"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities"
-" that are being investigated by researchers at UCSB. We continue to work "
-"with them on additional improvements. This is a good opportunity to "
-"remind the community that while our network continues to grow rapidly, it"
-" is still relatively small. There may be multiple weaknesses or bugs that"
-" could compromise your anonymity. Help us grow the network by spreading "
-"the word and contributing where you can."
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13
-#, python-format
-msgid ""
-"In this upgrade cycle, a random 1% of routers, (plus all routers running "
-"a\n"
-"development build) will attempt to update via the experimental in-network"
-" bittorrent\n"
-"with i2psnark. If this doesn't work, it should fall back to standard in-"
-"network HTTP update."
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27
-msgid "Defenses and Bug Fixes"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29
-msgid "Fix router bug causing lockup when using iMule"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30
-msgid "Recognize, handle, reject duplicate tunnel IDs"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31
-msgid "Fix changing of the log file name"
-msgstr "Corregido el cambio de nombre del archivo de registro"
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32
-msgid "Prevent hashcode attack in session tags"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33
-msgid "Add build request throttler based on previous hop"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34
-msgid "Limit concurrent next-hop lookups"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35
-msgid "Catch exceptions storing nonces in console"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36
-msgid "Fix saving graph settings in console"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37
-msgid "Fix eepget generation of URLs when not proxied"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38
-msgid ""
-"Encrypt database lookup messages end-to-end when sent through exploratory"
-" tunnels"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39
-msgid "Don't use multiple floodfills from the same /16 in a query"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40
-msgid "Randomize delay before verifying floodfill store"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41
-msgid "Increase number of floodfills"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:45
-msgid "Improve support for mobile browsers"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46
-msgid "Partial defenses for UCSB attacks"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47
-msgid "Add announce list support to i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48
-msgid "Jetty: upgrade Apache Tomcat to 6.0.36"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49
-msgid "Split router info files into multiple subdirectories"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50
-msgid "Add IP to hostname mapping option in SOCKS"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51
-msgid "Improve PRNG seeding"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52
-msgid ""
-"Translation updates: French, German, Hungarian, Italian, Norwegian, "
-"Polish, Portuguese, Russian, Swedish"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54
-msgid "Update wrapper to 3.5.17 (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:2
-msgid "0.9.6 Release"
-msgstr "Versión 0.9.6"
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:7
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9
-msgid ""
-"0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to "
-"Jetty 7.6.10 (2013-03-12). See below for important information on the "
-"Jetty update. The Jetty 7 series is actively maintained and we plan to "
-"stay current with it in future I2P releases."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13
-msgid ""
-"Most users will update via HTTP. Those running development builds will "
-"attempt to update via the\n"
-"experimental in-network bittorrent with i2psnark. We've fixed some bugs "
-"that will enable more users\n"
-"to update via torrent in the 0.9.7 update cycle."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25
-msgid "Important fix for Windows Eepsites, first install 0.9.5 only"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27
-msgid ""
-"If you first installed I2P with version 0.9.5, on Windows only, we "
-"recommend that you follow the\n"
-"following instructions to fix your eepsite location **before** you update"
-" to 0.9.6.\n"
-"Only original installations of 0.9.5-0 on Windows are affected by this "
-"issue. If your router version\n"
-"is 0.9.5-0-win1, you already have the fix and need not take any action."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34
-msgid "See `this page`_ for instructions."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:38
-msgid "`this page`"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:40
-msgid "Jetty 7 Migration Details"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42
-msgid ""
-"For most people, the update should just work. If you have multiple Jetty "
-"eepsites,\n"
-"OR have made changes to jetty.xml or other Jetty configuration files, "
-"including changing the port\n"
-"from 7658, you MUST take manual action AFTER updating."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48
-msgid ""
-"After update, the router will migrate your jetty.xml files to the new "
-"Jetty 7 format."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50
-msgid ""
-"The migration resets the port to 7658. If you have more than one Jetty "
-"eepsite, OR your eepsite\n"
-"  is NOT on port 7658, OR you have made other modifications to jetty.xml "
-"(for example changing the\n"
-"  listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml "
-"file for each eepsite to fix them up\n"
-"  after updating, and restart again."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55
-msgid ""
-"**The following files will be backed up with a ".jetty6" suffix"
-" and then migrated.**\n"
-"If you have made local changes, you may have to edit them manually and "
-"restart.\n"
-"See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69
-#: i2p2www/pages/global/nav.html:75 i2p2www/pages/global/nav.html:91
-#: i2p2www/pages/site/docs/plugins.html:2
-#: i2p2www/pages/site/docs/spec/configuration.html:65
-msgid "Plugins"
-msgstr "Complementos"
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:71
-msgid "Most plugins should work fine with Jetty 7."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:75
-msgid ""
-"The I2PControl and zzzot plugins must be updated. Your router should "
-"download and install the new versions shortly after starting 0.9.6."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77
-msgid "If a plugin does not work, please contact the maintainer for that plugin."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83
-msgid "Several bugs with Windows installation (see above)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:84
-msgid "Fix default form action in i2ptunnel"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85
-msgid "Fix links on iframed console pages"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86
-msgid "Better detection of 64-bit Windows to prevent crashes by systray"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87
-msgid "Fix bug preventing router update via torrent"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88
-msgid "Several SSU fixes for NATs that change UDP ports"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89
-msgid ""
-"Ignore unsupported IPs in RouterInfos when selecting an address (prep for"
-" IPv6)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90
-msgid ""
-"Ignore unused option bits in Database Lookup Message (prep for requesting"
-" encrypted response)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91
-msgid "Fix HTTP proxy error response for malformed URIs"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92
-msgid "Recognize UPnP devices without port forwarding capability"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96
-msgid "Jetty 7.6.10 (see above for migration information)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97
-msgid "Limit page size in i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98
-msgid "Add data directory and page size configuration to i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99
-msgid "Support multiple i2psnark instances"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100
-msgid "Piece size adjustments in i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101
-msgid "Add more graphing support for combined bandwidth graph"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102
-msgid "Block b32.i2p supercookies"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103
-msgid "Allow stopping clients on /configclients"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104
-msgid "Check for nonce count replays in HTTP client"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105
-msgid "Support SASL authentication in IRC proxy"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106
-msgid "Several cleanups and minor fixes in the update manager"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107
-msgid "Translation updates: German, Portuguese, Russian, Spanish, and Swedish"
-msgstr "Traducciones actualizadas: alemán, portugués, ruso, español y sueco"
-
-#: i2p2www/pages/blog/category.html:2
-msgid "Blog Category"
-msgstr ""
-
-#: i2p2www/pages/blog/category.html:4
-#, python-format
-msgid "I2P Blog ATOM Feed for Category: %(category)s"
-msgstr ""
-
-#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
-#: i2p2www/pages/global/nav.html:95
-msgid "Blog"
-msgstr "Blog"
-
-#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:75
-msgid "I2P Blog ATOM Feed"
-msgstr ""
-
-#: i2p2www/pages/blog/index.html:17
-#, python-format
-msgid "Posted %(date)s by %(author)s"
-msgstr "Publicado el %(date)s por %(author)s"
-
-#: i2p2www/pages/blog/latest.html:5
-msgid "More blog posts…"
-msgstr "Mas entradas en blog…"
-
-#: i2p2www/pages/blog/post.html:6
-msgid "Posted:"
-msgstr "Publicado:"
-
-#: i2p2www/pages/blog/post.html:7
-msgid "Author:"
-msgstr "Autor:"
-
-#: i2p2www/pages/downloads/debian.html:4
-msgid "Debian I2P Packages"
-msgstr "Paquetes de I2P para Debian"
-
-#: i2p2www/pages/downloads/debian.html:6
-#, python-format
-msgid ""
-"The packages hosted on the I2P Launchpad site\n"
-"have been tested and should work on x86/x86_64 platforms running:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:11
-msgid "Ubuntu (Precise 12.04 and newer)"
-msgstr "Ubuntu (Precise 12.04 y posterior)"
-
-#: i2p2www/pages/downloads/debian.html:13
-msgid ""
-"Debian Linux (Wheezy and newer) & kFreeBSD"
-msgstr ""
-"Debian Linux (Wheezy y posterior) y kFreeBSD"
-
-#: i2p2www/pages/downloads/debian.html:17
-#, python-format
-msgid ""
-"The I2P packages may work on systems not listed above. Please "
-"report any issues\n"
-"with these packages on Trac at\n"
-"http://%(trac)s."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:23
-msgid ""
-"Option 1: Recent versions of Ubuntu and its "
-"derivatives (Try this if you're not using Debian)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:24
-msgid "Option 2: Debian (including Debian-derivatives)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:25
-msgid ""
-"Option 3: Non-Linux (and possibly Non-x86 "
-"architectures)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:28
-msgid ""
-"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
-" Linux Mint & Trisquel"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:29
-msgid "Adding the PPA via the command line and installing I2P"
-msgstr "Añadir el PPA desde la línea de comandos e instalar I2P"
-
-#: i2p2www/pages/downloads/debian.html:32
-msgid "Open a terminal and enter:"
-msgstr "Abra una terminal y escriba:"
-
-#: i2p2www/pages/downloads/debian.html:34
-msgid ""
-"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
-"gpg key that the repository has been signed with. The GPG key ensures\n"
-"that the packages have not been tampered with since being built."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:41
-msgid "Notify your package manager of the new PPA by entering:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:43
-msgid ""
-"This command will retrieve the latest list of software from each\n"
-"repository that is enabled on your system, including the I2P PPA that\n"
-"was added with the earlier command."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:49
-#: i2p2www/pages/downloads/debian.html:112
-#: i2p2www/pages/downloads/debian.html:137
-msgid "You are now ready to install I2P!"
-msgstr "Ya puede instalar I2P"
-
-#: i2p2www/pages/downloads/debian.html:53
-msgid "Adding the PPA Using Synaptic"
-msgstr "Añadir el PPA usando Synaptic"
-
-#: i2p2www/pages/downloads/debian.html:56
-msgid ""
-"Open Synaptic (System -> Administration -> Synaptic Package "
-"Manager)."
-msgstr ""
-"Aba Synaptic (Sistema -> Administración -> Gestor de paquetes "
-"Synaptic)."
-
-#: i2p2www/pages/downloads/debian.html:61
-msgid ""
-"Once Synaptic opens, select Repositories from the "
-"Settings menu."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:66
-msgid ""
-"Click the Other Sources tab and click Add. Paste "
-"ppa:i2p-maintainers/i2p into the APT-line field and click "
-"Add Source. Click the Close button then "
-"Reload."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:71
-msgid ""
-"In the Quick Filter box, type in i2p and press enter. When "
-"i2p is returned in the results list, right click "
-"i2p and select Mark for Installation. After doing "
-"so you may see a Mark additional required changes? popup. If so,"
-" click Mark then Apply."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:77
-msgid ""
-"After the installation process completes you can move on to the next\n"
-"part of starting I2P and configuring "
-"it for your system."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:82
-msgid "Instructions for Debian Lenny and newer"
-msgstr "Instrucciones para Debian Lenny y posterior"
-
-#: i2p2www/pages/downloads/debian.html:84
-msgid ""
-"For Squeeze you can follow the instructions here."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:86
-msgid ""
-"The steps below should be performed with root access (i.e., switching\n"
-"user to root with \"su\" or by prefixing each command with \"sudo\")."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:92
-msgid "Add the GPG key that signs the repository with the following command:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:94
-msgid "You'll have output like the following if the command was successful:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:98
-msgid "Add the following entries to /etc/apt/sources.list.d/i2p.list"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:103
-msgid "Notify your package manager of the new PPA by entering"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:105
-msgid ""
-"This command will retrieve the latest list of software from every\n"
-"repository enabled on your system, including the I2P PPA added in step\n"
-"1."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:116
-#: i2p2www/pages/downloads/debian.html:147
-msgid ""
-"After the installation process completes you can move on to the next part"
-" of starting I2P and configuring it "
-"for your system."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:120
-msgid "Instructions for Non-Linux / Non-x86"
-msgstr "Instrucciones para sistemas no Linux / no x86"
-
-#: i2p2www/pages/downloads/debian.html:122
-msgid ""
-"The steps below should be performed with root access (i.e., switching\n"
-"user to root with \"su\" or by prefixing each command with "
-"\"sudo\")."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:128
-#, python-format
-msgid ""
-"Download the i2p-router package from the PPA.\n"
-"Alternatively, there are unofficial packages available here for armel, armhf, and kfreebsd."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:135
-msgid ""
-"Make sure that you have Java installed. Running apt-get install"
-" default-jre should be sufficient."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:141
-#, python-format
-msgid ""
-"It is recommended to compile jbigi for your "
-"system to achieve better performance. Instructions are available here."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:151
-#: i2p2www/pages/downloads/list.html:167
-msgid "Post-install work"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:154
-msgid ""
-"Using these I2P packages the I2P router can be started in the following\n"
-"three ways:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:160
-msgid ""
-""on demand" using the i2prouter script. Simply run "
-""i2prouter\n"
-"start" from a command prompt. (Note: Do "
-"not use\n"
-"sudo or run it as root!)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:167
-msgid ""
-""on demand" without the java service wrapper\n"
-"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
-"nowrapper\".\n"
-"(Note: Do not\n"
-"use sudo or run it as root!)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:175
-msgid ""
-"as a service that automatically runs when your system boots, even\n"
-"before logging in. The service can be enabled with \"dpkg-"
-"reconfigure\n"
-"i2p\" as root or using sudo. This is the recommended means of "
-"operation."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:183
-msgid ""
-"When installing for the first time, please remember to adjust your "
-"NAT/firewall\n"
-"if you can. The ports to forward can be found on the \n"
-"network configuration page in the router console. If guidance with "
-"respect to forwarding ports is needed,\n"
-"you may find portforward.com to be"
-" helpful."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:190
-msgid ""
-"Please review and adjust the bandwidth settings on the\n"
-"configuration page,\n"
-"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
-"conservative."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:196
-#: i2p2www/pages/downloads/list.html:200
-#, python-format
-msgid ""
-"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
-"howto."
-msgstr ""
-"Si desea navegar a una eepsite desde su navegador eche un vistazo a la "
-"web configuración del proxy del "
-"navegador para ver un tutorial sencillo."
-
-#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
-#: i2p2www/pages/global/nav.html:3
-msgid "Download"
-msgstr "Descargas"
-
-#: i2p2www/pages/downloads/list.html:4
-msgid "Download I2P"
-msgstr "Descarga I2P"
-
-#: i2p2www/pages/downloads/list.html:6
-msgid "Dependency"
-msgstr "Dependencias"
-
-#: i2p2www/pages/downloads/list.html:7
-#, fuzzy, python-format
-msgid ""
-"\n"
-"Java Runtime 1.5 or higher.\n"
-"(Oracle Java Version 6/7,\n"
-"OpenJDK 6/7, or\n"
-"IcedTea6/7\n"
-" recommended)\n"
-"
            \n"
-"Determine"
-" your installed Java version here\n"
-"or type java -version at your command prompt.\n"
-msgstr ""
-"\n"
-"Java Runtime 1.5 o mayor. (Oracle/Sun Java "
-"Version 6, OpenJDK 6, o IcedTea6  recomendado) 
             a "
-"href=\\\"http://java.com/en/download/installed.jsp?detect=jre&try=1\\\">Averigua"
-" tu versión de java aquí\n"
-" o escriba java -version en la terminal.\n"
-
-#: i2p2www/pages/downloads/list.html:20
-msgid "Clean installs"
-msgstr "Instalación"
-
-#: i2p2www/pages/downloads/list.html:27 i2p2www/pages/downloads/list.html:45
-#: i2p2www/pages/downloads/list.html:73 i2p2www/pages/downloads/list.html:135
-#: i2p2www/pages/downloads/list.html:265
-msgid "select alternate link"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:35
-msgid "Download that file and run it."
-msgstr "Descargue este archivo y ejecútelo."
-
-#: i2p2www/pages/downloads/list.html:53
-#, python-format
-msgid ""
-"Download that file and double-click it (if that works) or\n"
-"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
-"terminal to run the\n"
-"    installer.\n"
-"    You may be able to right-click and select\n"
-"    "Open with Java"."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:61 i2p2www/pages/downloads/list.html:89
-msgid "Command line (headless) install:"
-msgstr "Comando de instalación (headless):"
-
-#: i2p2www/pages/downloads/list.html:62
-#, python-format
-msgid ""
-"Download the %(i2pversion)s OSX graphical installer file above and\n"
-"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
-"from the command line."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:81
-#, python-format
-msgid ""
-"Download that file and double-click it (if that works) or\n"
-"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
-"terminal to run the\n"
-"    installer.\n"
-"    On some platforms you may be able to right-click and select\n"
-"    "Open with Java"."
-msgstr ""
-"Descargue el archivo y pulse dos veces sobre él (si funciona) o\n"
-"    escriba java -jar i2pinstall_%(i2pversion)s.jar en una "
-"terminal para ejecutar\n"
-"    el instalador.\n"
-"    En algunos sistemas debería poder pulsar botón derecho sobre el "
-"archivo y seleccionar\n"
-"    "Abrir con Java"."
-
-#: i2p2www/pages/downloads/list.html:90
-#, python-format
-msgid ""
-"Download the graphical installer file above and\n"
-"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
-"from the command line."
-msgstr ""
-"Descargue el instalador gráfico y ejecute java -jar "
-"i2pinstall_%(i2pversion)s.jar -console en una terminal."
-
-#: i2p2www/pages/downloads/list.html:100
-msgid "Packages for Debian & Ubuntu are available."
-msgstr "Hay disponibles paquetes para Debian & Ubuntu."
-
-#: i2p2www/pages/downloads/list.html:115
-#, python-format
-msgid ""
-"The Android version of I2P is being actively developed.\n"
-"    The latest dev build is version 0.9.3-5_b2-API8, and is available "
-"from\n"
-"    sponge's eepsite -\n"
-"    scan or click the QR code."
-msgstr ""
-"La versión de I2P para Android está actualmente desarrollándose "
-"activamente. La última versión compilada es 0.9.3-5_b2-API8, y está "
-"disponible en la eepsite de Sponge -  "
-"Escanee o pulse sobre el código QR."
-
-#: i2p2www/pages/downloads/list.html:122
-msgid ""
-"The release and dev versions of the I2P APK are not compatible, as they\n"
-"      are signed by zzz and sponge respectively. Uninstall one before "
-"installing\n"
-"      the other."
-msgstr ""
-"Las versiones 'release' y en desarrollo del paquete APK de I2P no son "
-"compatibles, \n"
-"    ya que están firmadas por zzz y sponge respectivamente. Desinstale "
-"una antes de \n"
-"    instalar la otra."
-
-#: i2p2www/pages/downloads/list.html:132
-msgid "Source package"
-msgstr "Archivo con el código fuente "
-
-#: i2p2www/pages/downloads/list.html:143
-#, fuzzy, python-format
-msgid ""
-"Alternately, you can fetch the source from monotone\n"
-"    or via Git from git.repo.i2p or Github.\n"
-"    
            \n"
-"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
-"i2p-%(i2pversion)s ; ant pkg) then either\n"
-"    run the GUI installer or headless install as above."
-msgstr ""
-"También puede obtener el código fuente de monotone.\n"
-"
             Ejecute (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
-"i2p-%(i2pversion)s ; ant pkg) y entonces ejecute el instalador "
-"gráfico o el instalador 'headless'."
-
-#: i2p2www/pages/downloads/list.html:158
-#, python-format
-msgid ""
-"The files are signed by zzz,\n"
-"whose key is here."
-msgstr ""
-"Estos archivos están firmados por zzz, cuya "
-"clave está aquí."
-
-#: i2p2www/pages/downloads/list.html:163
-msgid ""
-"I2P can also be downloaded from our project pages on Launchpad and Google Code."
-msgstr ""
-"I2P también puede ser descargado de la web de nuestro proyecto en Launchpad y en Google Code."
-
-#: i2p2www/pages/downloads/list.html:169
-msgid ""
-"After running the installer on windows, simply click on the \"Start I2P\""
-" button\n"
-"which will bring up the router console,\n"
-"which has further instructions."
-msgstr ""
-"Después de ejecutar el instalador en Windows simplemente pulse en el "
-"botón \"Start I2P\" \n"
-"lo cual abrirá laconsola del "
-"ruter,\n"
-"donde encontrará mas instrucciones."
-
-#: i2p2www/pages/downloads/list.html:175
-msgid ""
-"On Unix-like systems, I2P can be started as a service\n"
-"using the \"i2prouter\" script, located in the directory you selected for"
-" I2P.\n"
-"Changing to that directory in a console and issuing \"sh i2prouter "
-"status\"\n"
-"should tell you the router's status. The arguments \"start\", \"stop\" "
-"and \"restart\"\n"
-"control the service. The router console\n"
-"can be accessed at its usual location.\n"
-"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
-" is not supported,\n"
-"start the router with \"sh runplain.sh\" instead."
-msgstr ""
-"En los sistemas basados en Unix I2P puede ser ejecutado como un servicio\n"
-"usando el script \"i2prouter\" localizado en la carpeta seleccionada para"
-" I2P.\n"
-"Entrando a esa carpeta en al terminal y ejecutando \"sh i2prouter "
-"status\"\n"
-"debería mostrar el estado del ruter. Los argumentos \"start\", \"stop\" y"
-" \"restart\"\n"
-"controlan el servicio. A la consola del ruter\n"
-"puede accederse en la localización usual.\n"
-"Para usuarios de Opensolaris y otros sistemas donde el 'wrapper' (i2psvc)"
-" no está soportado,\n"
-"ejecute el ruter con \"sh runplain.sh\"."
-
-#: i2p2www/pages/downloads/list.html:186
-#, python-format
-msgid ""
-"When installing for the first time, please remember to adjust your "
-"NAT/firewall\n"
-"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
-"described here among other ports.\n"
-"If you have successfully opened your port to inbound TCP, also enable "
-"inbound TCP on the\n"
-"configuration page."
-msgstr ""
-"Cuando instale I2P por primera vez, por favor recuerde ajustar su "
-"NAT/cortafuegos\n"
-"si puede, sin olvidarse de los puertos que I2P abre a Internet,\n"
-"descritos aquí.\n"
-"Si ha abierto con éxito el puerto TCP de entrada en su NAT/cortafuegos, "
-"abra también el puerto TCP de \n"
-"entrada en la página de "
-"configuración."
-
-#: i2p2www/pages/downloads/list.html:194
-msgid ""
-"Also, please review and adjust the bandwidth settings on the\n"
-"configuration page,\n"
-"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
-msgstr ""
-"Además, por favor revise y ajuste su configuración de ancho de "
-"banda en la \n"
-"página de configuración,"
-"\n"
-"ya que la configuración por defecto de 96 KBps de descarga  / 40 KBps de "
-"subida es \n"
-"bastante lenta."
-
-#: i2p2www/pages/downloads/list.html:204
-msgid "Updates from earlier releases:"
-msgstr "Actualizaciones desde versiones anteriores:"
-
-#: i2p2www/pages/downloads/list.html:206
-msgid "Both automatic and manual upgrades are available for the release."
-msgstr "Están disponibles actualizaciones manuales y automáticas."
-
-#: i2p2www/pages/downloads/list.html:211
-msgid "Automatic updates"
-msgstr "Actualizaciones Auutomáticas"
-
-#: i2p2www/pages/downloads/list.html:213
-msgid ""
-"If you are running 0.7.5 or later, your router should detect the\n"
-"new release. To upgrade simply click the 'Download Update' button on your"
-" router console\n"
-"when it appears."
-msgstr ""
-"Si esta usando 0.7.5 o posterior su ruter debería detectar las nuevas \n"
-"versiones automáticamente. Para actualizar, cuando aparezca  el botón "
-"'Descargar actualización' en la consola, simplemente púlselo."
-
-#: i2p2www/pages/downloads/list.html:219
-msgid ""
-"Due to a bug in release 0.7.6, those whose first I2P installation was "
-"that version\n"
-"and have not upgraded manually\n"
-"may get a \"downloaded version is not greater than current version\" "
-"error,\n"
-"and should use the manual update method below."
-msgstr ""
-"Debido a un fallo en la versión 0.7.6, aquellos en los cuales su primera "
-"instalación \n"
-"es esta versión y no han actualizado manualmente pueden obtener el error "
-"\"downloaded version is not greater than current version\", y deben usar "
-"la actualización manual de abajo."
-
-#: i2p2www/pages/downloads/list.html:227
-#, python-format
-msgid ""
-"If you are running 0.7.4 or earlier, please see\n"
-"the 0.7.5 release notes\n"
-"for important information about how to configure your router to "
-"automatically\n"
-"receive the release."
-msgstr ""
-"Si utiliza la versión 0.7.4 o anterior, por favor lea las notas de la versión 0.7.5 para obtener "
-"información importante de como configurar el ruter para descargar las "
-"actualizaciones automáticamente."
-
-#: i2p2www/pages/downloads/list.html:235
-#, python-format
-msgid ""
-"If you are running 0.6.1.30 or earlier, please see\n"
-"instructions\n"
-"for important information about how to configure your router to "
-"automatically\n"
-"receive the release."
-msgstr ""
-"Si utiliza la versión 0.6.1.30 o anterior, por favor lea instrucciones\n"
-"para obtener ver información importante de como configurar el ruter para "
-"descargar las actualizaciones automáticamente."
-
-#: i2p2www/pages/downloads/list.html:244
-#, python-format
-msgid ""
-"If you have reconfigured your router following the instructions, you should see a link on your"
-" \n"
-"    router console "
-"allowing\n"
-"    you to download and install the new release by just clicking on that\n"
-"    link."
-msgstr ""
-"Si ha reconfigurado su ruter siguiendo las instrucciones, debería ver un enlace en su "
-"consola del ruter "
-"permitiéndole  descargar e instalar la nueva versión pulsando en ese "
-"enlace."
-
-#: i2p2www/pages/downloads/list.html:252
-msgid "Alternately, you can use the manual method specified below."
-msgstr "De otra forma puede usar el método manual especificado mas abajo."
-
-#: i2p2www/pages/downloads/list.html:262
-msgid "Manual updates"
-msgstr "Actualizaciones manuales"
-
-#: i2p2www/pages/downloads/list.html:275
-msgid ""
-"Download that file to your I2P\n"
-"    installation directory and rename as i2pupdate.zip.\n"
-"    (alternately, you can get the source as above and run \"ant "
-"updater\", then copy the\n"
-"    resulting i2pupdate.zip to your I2P installation directory).  You do"
-" \n"
-"    NOT need to unzip that file."
-msgstr ""
-"Descargue el archivo en su carpeta de instalación de I2P y renómbrelo "
-"como i2pupdate.zip.    (alternativamente, puede obtener el código al "
-"igual que arriba y ejecutar \"ant updater\", y  entonces copiar el "
-"archivo resultante i2pupdate.zip a la carpeta de instalación de I2P).  NO"
-" necesita descomprimir este archivo .zip."
-
-#: i2p2www/pages/downloads/list.html:284
-msgid "Click \"Restart\""
-msgstr ""
-"Pulse \"Reiniciar\""
-
-#: i2p2www/pages/downloads/list.html:289
-msgid "Grab a cup of coffee and come back in 11 minutes"
-msgstr "Vaya a por una taza de horchata/café/mate y vuelva en 11 minutos."
-
-#: i2p2www/pages/downloads/list.html:297
-#, python-format
-msgid ""
-"The file is signed by zzz,\n"
-"whose key is here."
-msgstr ""
-"El archivo está firmado por zzz,\n"
-"cuya clave está aquí."
-
-#: i2p2www/pages/downloads/list.html:302
-msgid "Previous Releases"
-msgstr "Versiones Anteriores"
-
-#: i2p2www/pages/downloads/list.html:304
-#, python-format
-msgid ""
-"Previous releases are available on Google "
-"Code\n"
-"and Launchpad\n"
-"and within the I2P network on %(echelon)s."
-msgstr ""
-"Versiones anteriores están disponibles en Google "
-"Code y Launchpad\n"
-"y dentro de la red I2P en %(echelon)s."
-
-#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
-msgid "Mirror selection"
-msgstr ""
-
-#: i2p2www/pages/downloads/select.html:5
-msgid "File:"
-msgstr "Archivo:"
-
-#: i2p2www/pages/downloads/select.html:10
-msgid "Any mirror"
-msgstr "Cualquier mirror"
-
-#: i2p2www/pages/global/bounty.html:19
-msgid ""
-"To claim the bounty the author must not be paid by other organizations\n"
-"or teams for this work (e.g. GSoC students are not valid)."
-msgstr ""
-
-#: i2p2www/pages/global/bounty.html:29
-#, python-format
-msgid ""
-"Bounty amounts may be increased by further donations.  Do\n"
-"you think these are important? Add in your "
-"donation, \n"
-"marking the amount for the %(donatename)s bounty!"
-msgstr ""
-
-#: i2p2www/pages/global/error_404.html:3
-msgid "Not found"
-msgstr "No encontrado"
-
-#: i2p2www/pages/global/error_404.html:9
-msgid ""
-"Yep... the resource, you were searching for, is named differently, "
-"doesn't exist or was removed."
-msgstr ""
-
-#: i2p2www/pages/global/error_500.html:5
-msgid "Server error"
-msgstr "Error del servidor"
-
-#: i2p2www/pages/global/error_500.html:13
-msgid "500 Server error"
-msgstr "500 Error del Servidor"
-
-#: i2p2www/pages/global/error_500.html:17
-msgid "Umm... the server encountered some sort of error."
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:2
-msgid "Mirrors"
-msgstr "Mirrors"
-
-#: i2p2www/pages/global/footer.html:10
-msgid "Secure"
-msgstr "Seguro"
-
-#: i2p2www/pages/global/footer.html:16
-msgid "Misc."
-msgstr "Varios"
-
-#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
-msgid "Links"
-msgstr "Links"
-
-#: i2p2www/pages/global/footer.html:20
-msgid "Impressum"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:24
-msgid "T-Shirts!"
-msgstr "Camisetas"
-
-#: i2p2www/pages/global/footer.html:26
-msgid "Europe"
-msgstr "Europea"
-
-#: i2p2www/pages/global/footer.html:27
-msgid "USA"
-msgstr "EEUU"
-
-#: i2p2www/pages/global/footer.html:31
-#: i2p2www/pages/site/get-involved/donate.html:2
-#: i2p2www/pages/site/get-involved/index.html:74
-msgid "Donate"
-msgstr "Donar"
-
-#: i2p2www/pages/global/layout.html:29
-msgid "Skip navigation"
-msgstr "Saltar Navegación"
-
-#: i2p2www/pages/global/layout.html:32
-msgid "I2P Logo"
-msgstr "Logo I2P"
-
-#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
-#: i2p2www/pages/site/about/intro.html:4
-msgid "The Invisible Internet Project"
-msgstr "El proyecto de Internet Invisible"
-
-#: i2p2www/pages/global/layout.html:56
-#, python-format
-msgid ""
-"This page was last updated in %(lastupdated)s and is accurate for router "
-"version %(accuratefor)s."
-msgstr ""
-"Esta pagina fue actualizada por última vez el %(lastupdated)s y, en "
-"concrento, es la versión %(accuratefor)s."
-
-#: i2p2www/pages/global/layout.html:60
-#, python-format
-msgid "This page was last updated in %(lastupdated)s."
-msgstr "Esta página fue actualizada por última vez el %(lastupdated)s."
-
-#: i2p2www/pages/global/layout.html:64
-#, python-format
-msgid "This page is accurate for router version %(accuratefor)s."
-msgstr "Esta página está diseñada para la versión de router %(accuratefor)s."
-
-#: i2p2www/pages/global/macros:19
-msgid "Previous"
-msgstr "Anterior"
-
-#: i2p2www/pages/global/macros:34
-msgid "Next"
-msgstr "Siguiente"
-
-#: i2p2www/pages/global/macros:41
-msgid "Posted in"
-msgstr "Publicado el"
-
-#: i2p2www/pages/global/nav.html:4
-msgid "About"
-msgstr "Sobre"
-
-#: i2p2www/pages/global/nav.html:6
-msgid "Introduction to I2P"
-msgstr "Introducción a I2P"
-
-#: i2p2www/pages/global/nav.html:7
-msgid "Comparisons"
-msgstr "Comparaciones"
-
-#: i2p2www/pages/global/nav.html:9
-msgid "Overview of comparisons"
-msgstr "Vista rápida de comparaciones"
-
-#: i2p2www/pages/global/nav.html:13
-msgid "Other anonymous networks"
-msgstr "Otras redes anónimas"
-
-#: i2p2www/pages/global/nav.html:16
-#: i2p2www/pages/site/get-involved/index.html:29
-msgid "Documentation"
-msgstr "Documentación"
-
-#: i2p2www/pages/global/nav.html:18
-msgid "Documentation index"
-msgstr "Indice de documentación"
-
-#: i2p2www/pages/global/nav.html:19 i2p2www/pages/site/about/intro.html:17
-msgid "How does it work?"
-msgstr "¿Cómo funciona?"
-
-#: i2p2www/pages/global/nav.html:21
-msgid "Gentle intro"
-msgstr "Una introducción simple"
-
-#: i2p2www/pages/global/nav.html:22
-msgid "Tech intro"
-msgstr "Introducción técnica"
-
-#: i2p2www/pages/global/nav.html:23
-msgid "Threat model"
-msgstr "Modelo de amenazas"
-
-#: i2p2www/pages/global/nav.html:24
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:292
-msgid "Garlic routing"
-msgstr "Garlic routing"
-
-#: i2p2www/pages/global/nav.html:25
-msgid "Network database"
-msgstr "Base de datos de la red"
-
-#: i2p2www/pages/global/nav.html:26
-msgid "Tunnel routing"
-msgstr "Enrutamiento de túneles"
-
-#: i2p2www/pages/global/nav.html:27
-#: i2p2www/pages/site/docs/tunnels/unidirectional.html:21
-msgid "Peer selection"
-msgstr "Selección de pares"
-
-#: i2p2www/pages/global/nav.html:28
-#: i2p2www/pages/site/docs/how/tech-intro.html:17
-#: i2p2www/pages/site/docs/how/tech-intro.html:458
-msgid "Cryptography"
-msgstr "Cifrado"
-
-#: i2p2www/pages/global/nav.html:29
-msgid "ElGamal/AES+SessionTags"
-msgstr "ElGamal/AES+SessionTags"
-
-#: i2p2www/pages/global/nav.html:32 i2p2www/pages/global/nav.html:116
-#: i2p2www/pages/site/docs/spec/configuration.html:75
-#: i2p2www/pages/site/get-involved/index.html:48
-msgid "Applications"
-msgstr "Aplicaciones"
-
-#: i2p2www/pages/global/nav.html:34
-msgid "Supported applications"
-msgstr "Aplicaciones soportadas"
-
-#: i2p2www/pages/global/nav.html:35
-msgid "Bittorrent"
-msgstr "Bittorrent"
-
-#: i2p2www/pages/global/nav.html:38
-#: i2p2www/pages/site/docs/api/streaming.html:58
-msgid "API"
-msgstr "API"
-
-#: i2p2www/pages/global/nav.html:46 i2p2www/pages/global/nav.html:77
-#: i2p2www/pages/site/docs/how/tech-intro.html:808
-msgid "Streaming library"
-msgstr "Librería de transmisión"
-
-#: i2p2www/pages/global/nav.html:47
-msgid "Ministreaming library"
-msgstr "Librería de minitransmisión"
-
-#: i2p2www/pages/global/nav.html:48 i2p2www/pages/global/nav.html:71
-#: i2p2www/pages/site/docs/index.html:88
-#: i2p2www/pages/site/docs/api/datagrams.html:2
-#: i2p2www/pages/site/get-involved/develop/applications.html:277
-msgid "Datagrams"
-msgstr "Datagramas"
-
-#: i2p2www/pages/global/nav.html:52
-msgid "Protocols"
-msgstr "Protocolos"
-
-#: i2p2www/pages/global/nav.html:54
-msgid "Protocol stack"
-msgstr "Pila del protocolo"
-
-#: i2p2www/pages/global/nav.html:59
-#: i2p2www/pages/site/docs/how/cryptography.html:394
-msgid "Transports"
-msgstr "Transportes"
-
-#: i2p2www/pages/global/nav.html:61 i2p2www/pages/site/docs/index.html:158
-msgid "Transport layer overview"
-msgstr "Visión general de la capa de transporte"
-
-#: i2p2www/pages/global/nav.html:66
-msgid "Specifications"
-msgstr "Especificaciones"
-
-#: i2p2www/pages/global/nav.html:68
-msgid "Blockfile"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:69
-msgid "Common structures"
-msgstr "Estructuras habituales"
-
-#: i2p2www/pages/global/nav.html:70
-msgid "Configuration files"
-msgstr "Archivos de configuración"
-
-#: i2p2www/pages/global/nav.html:72
-msgid "GeoIP files"
-msgstr "Archivos GeoIP"
-
-#: i2p2www/pages/global/nav.html:78
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:230
-msgid "Tunnel creation"
-msgstr "Creación de túneles"
-
-#: i2p2www/pages/global/nav.html:79
-msgid "Tunnel messages"
-msgstr "Mensajes de túneles"
-
-#: i2p2www/pages/global/nav.html:80
-msgid "Software updates"
-msgstr "Actualizaciones de software"
-
-#: i2p2www/pages/global/nav.html:83 i2p2www/pages/site/docs/index.html:139
-#: i2p2www/pages/site/docs/how/tech-intro.html:14
-#: i2p2www/pages/site/docs/how/tech-intro.html:228
-msgid "Tunnels"
-msgstr "Túneles"
-
-#: i2p2www/pages/global/nav.html:85
-msgid "Tunnel implementation"
-msgstr "Implementacion de túneles"
-
-#: i2p2www/pages/global/nav.html:86
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:288
-msgid "Unidirectional tunnels"
-msgstr "Túneles unidireccionales"
-
-#: i2p2www/pages/global/nav.html:87
-msgid "Old implementation"
-msgstr "Implementación antigua"
-
-#: i2p2www/pages/global/nav.html:90
-msgid "Naming and addressbook"
-msgstr "Nombres y lista de direcciones"
-
-#: i2p2www/pages/global/nav.html:94 i2p2www/pages/site/about/team.html:2
-msgid "Team"
-msgstr "Equipo"
-
-#: i2p2www/pages/global/nav.html:96
-msgid "Hall of Fame"
-msgstr "Pódium"
-
-#: i2p2www/pages/global/nav.html:97
-msgid "Academic papers and peer review"
-msgstr "Documentos académicos y revisión por pares"
-
-#: i2p2www/pages/global/nav.html:98
-msgid "Presentations, tutorials and articles"
-msgstr "Presentaciones, artículos y tutoriales"
-
-#: i2p2www/pages/global/nav.html:99
-msgid "Contact us"
-msgstr "Contacto"
-
-#: i2p2www/pages/global/nav.html:102
-msgid "Help"
-msgstr "Ayuda"
-
-#: i2p2www/pages/global/nav.html:104
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
-msgid "FAQ"
-msgstr "Preguntas frecuentes"
-
-#: i2p2www/pages/global/nav.html:105
-msgid "How to browse I2P"
-msgstr "Como navegar I2P"
-
-#: i2p2www/pages/global/nav.html:106 i2p2www/pages/site/about/glossary.html:2
-msgid "Glossary"
-msgstr "Glosario"
-
-#: i2p2www/pages/global/nav.html:107
-#: i2p2www/pages/site/about/performance/index.html:2
-#: i2p2www/pages/site/docs/index.html:183
-#: i2p2www/pages/site/get-involved/todo.html:52
-#: i2p2www/pages/site/get-involved/todo.html:456
-msgid "Performance"
-msgstr "Rendimiento"
-
-#: i2p2www/pages/global/nav.html:108 i2p2www/pages/site/contact.html:22
-msgid "Forums"
-msgstr "Foros"
-
-#: i2p2www/pages/global/nav.html:111
-msgid "Volunteer"
-msgstr "Voluntario"
-
-#: i2p2www/pages/global/nav.html:113
-msgid "Get involved!"
-msgstr "¡Únete!"
-
-#: i2p2www/pages/global/nav.html:114
-msgid "Develop"
-msgstr "Desarrollo"
-
-#: i2p2www/pages/global/nav.html:117
-#: i2p2www/pages/site/get-involved/develop/licenses.html:2
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115
-msgid "Licenses"
-msgstr "Licencias"
-
-#: i2p2www/pages/global/nav.html:118
-msgid "Release signing keys"
-msgstr "Publicar claves de firmas."
-
-#: i2p2www/pages/global/nav.html:119
-msgid "Signed keys"
-msgstr "Claves firmadas"
-
-#: i2p2www/pages/global/nav.html:120
-msgid "Developers keys"
-msgstr "Claves de los desarrolladores"
-
-#: i2p2www/pages/global/nav.html:121 i2p2www/pages/site/docs/index.html:223
-msgid "Bug tracker"
-msgstr "Bug tracker"
-
-#: i2p2www/pages/global/nav.html:124
-msgid "Academic research"
-msgstr "Búsqueda académica"
-
-#: i2p2www/pages/global/nav.html:125
-msgid "Guides"
-msgstr "Guías"
-
-#: i2p2www/pages/global/nav.html:127
-msgid "New developers"
-msgstr "Nuevos programadores"
-
-#: i2p2www/pages/global/nav.html:128
-#: i2p2www/pages/site/get-involved/guides/ides.html:2
-msgid "Using an IDE with I2P"
-msgstr "Usando un IDE con I2P"
-
-#: i2p2www/pages/global/nav.html:129
-msgid "Developer guidelines and coding style"
-msgstr "Guías de desarrollo y estilo del código"
-
-#: i2p2www/pages/global/nav.html:130
-#: i2p2www/pages/site/get-involved/guides/monotone.html:2
-msgid "Monotone"
-msgstr "Monotone"
-
-#: i2p2www/pages/global/nav.html:131
-msgid "New translators"
-msgstr "Nuevos traductores"
-
-#: i2p2www/pages/global/nav.html:134
-#: i2p2www/pages/site/get-involved/bounties/index.html:2
-msgid "Bounties"
-msgstr "Recompensas"
-
-#: i2p2www/pages/global/nav.html:135 i2p2www/pages/meetings/index.html:2
-msgid "Meetings"
-msgstr "Reuniones"
-
-#: i2p2www/pages/global/nav.html:136
-#: i2p2www/pages/site/get-involved/roadmap.html:2
-msgid "Roadmap"
-msgstr "Hoja de ruta"
-
-#: i2p2www/pages/global/nav.html:137
-msgid "Task list"
-msgstr "Lista de tareas"
-
-#: i2p2www/pages/global/nav.html:140
-msgid "Language"
-msgstr "Idioma"
-
-#: i2p2www/pages/meetings/index.html:4
-msgid "I2P Meetings ATOM Feed"
-msgstr "ATOM feed de reuniones de I2P"
-
-#: i2p2www/pages/meetings/index.html:7
-msgid "Logs of past I2P meetings"
-msgstr "Registros de las reuniones pasadas de I2P"
-
-#: i2p2www/pages/meetings/index.html:9
-msgid "Meetings are currently on hold until a more suitable time can be chosen."
-msgstr ""
-
-#: i2p2www/pages/meetings/index.html:13
-#, python-format
-msgid ""
-"If you have something to discuss, please find the developers on IRC in "
-"#i2p-dev.\n"
-"Status updates from developers are also "
-"available."
-msgstr ""
-"Por favor, si tienes algo que discutir busque a los desarrolladores en "
-"#i2p-dev en el IRC. Las actualizaciones del "
-"estado de los desarrolladores están también disponibles."
-
-#: i2p2www/pages/meetings/show.html:2
-#, python-format
-msgid "I2P Development Meeting %(id)s"
-msgstr ""
-
-#: i2p2www/pages/meetings/show.html:10
-msgid "Full IRC Log"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:2
-msgid "Contact"
-msgstr "Contacto"
-
-#: i2p2www/pages/site/contact.html:5
-msgid ""
-"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
-" to this network is set up with new router installs.\n"
-"  We are also present on multiple standard networks like OFTC,\n"
-"  EIN and Freenode.\n"
-"  All I2P-related channels on all these network are linked to the main "
-"channels on Irc2P via relay bots."
-msgstr ""
-"Nuestra red IRC principal es la red Irc2P dentro de I2P; tras la "
-"instalación inicial de I2P ya hay creado por defecto un túnel a esta red."
-"  Estamos presentes también en múltiples redes como OFTC,  EIN y Freenode. Todos los canales "
-"relacionados con I2P en esas redes están unidos a los canales principales"
-" de Irc2P a través de 'relay bots'."
-
-#: i2p2www/pages/site/contact.html:13
-msgid "Channel list:"
-msgstr "Lista de Canales:"
-
-#: i2p2www/pages/site/contact.html:15
-msgid "General i2p discussion"
-msgstr "Discusión general sobre I2P"
-
-#: i2p2www/pages/site/contact.html:16
-msgid "Offtopic"
-msgstr "Offtopic"
-
-#: i2p2www/pages/site/contact.html:17
-msgid "Development talk"
-msgstr "Charla sobre el desarrollo"
-
-#: i2p2www/pages/site/contact.html:18
-msgid "Help channel"
-msgstr "Canal de ayuda"
-
-#: i2p2www/pages/site/contact.html:23
-#, python-format
-msgid ""
-"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
-" place to start with inquiries, if the dev IRC channel is inactive."
-msgstr ""
-"La mayoría de discusiones sobre el desarrollo de I2P ocurre en el foro de desarrollo de I2P. Este es "
-"normalmente el mejor lugar para preguntar, si el canal IRC está inactivo."
-
-#: i2p2www/pages/site/contact.html:27
-msgid "Mailing lists"
-msgstr "Listas de email"
-
-#: i2p2www/pages/site/contact.html:28
-msgid ""
-"I2P does have a mailing list, but it is rarely used as the current small "
-"team of developers prefer to communicate via IRC or the developer forum. "
-"This may change in future."
-msgstr ""
-"I2P tiene un 'mailing list' , pero raramente se usa ya que el pequeño "
-"grupo de desarrolladores prefiere comunicarse vía IRC o en el foro. Esto "
-"podría cambiar en el futuro."
-
-#: i2p2www/pages/site/contact.html:33
-msgid "Subscribing"
-msgstr "Subscripción"
-
-#: i2p2www/pages/site/contact.html:34
-msgid ""
-"To subscribe to a mailing list, go to the list information page (linked "
-"below) and fill out the form. I2P-internal email addresses "
-"(foobar@mail.i2p) can be used."
-msgstr ""
-"Para subscribiese al mailing list, vaya a la página de información de la "
-"lista (enlazada debajo) y rellene el formulario. Puede usar la dirección "
-"interna de email de I2P (foobar@mail.i2p)."
-
-#: i2p2www/pages/site/contact.html:38
-msgid "Unsubscribing"
-msgstr "Darse de baja"
-
-#: i2p2www/pages/site/contact.html:39
-msgid ""
-"To unsubscribe from a mailing list or edit your subscription options, go "
-"to the list information page (linked below) and enter your subscription "
-"email address."
-msgstr ""
-"Para cancelar o cambiar las opciones de la subscripción a la lista de "
-"mails, vaya a la página de información de la lista (enlace debajo) y "
-"escriba el email de su subscripción."
-
-#: i2p2www/pages/site/contact.html:43
-msgid "Lists"
-msgstr "Listas"
-
-#: i2p2www/pages/site/contact.html:46
-msgid "Archive"
-msgstr "Archivo"
-
-#: i2p2www/pages/site/contact.html:47
-msgid ""
-"General I2P discussion - anything that doesn't fit in a different list "
-"goes here."
-msgstr ""
-"Discusión general sobre I2p - cualquier cosa que no encaje en otras "
-"listas va aquí."
-
-#: i2p2www/pages/site/contact.html:53
-msgid ""
-"You don't like mailing lists? Then this is for you. All mailing lists are"
-" available via NNTP as well."
-msgstr ""
-"¿No te gustan las mailing lists? Entonces esto es para ti. Todas las "
-"listas de mail están disponibles también por NNTP."
-
-#: i2p2www/pages/site/contact.html:58
-msgid "Group-List-mapping:"
-msgstr "Listado de la lista de grupos:"
-
-#: i2p2www/pages/site/contact.html:62
-msgid "Servers:"
-msgstr "Servidores:"
-
-#: i2p2www/pages/site/faq.html:2
-msgid "Frequently Asked Questions"
-msgstr "Preguntas frecuentes"
-
-#: i2p2www/pages/site/faq.html:4
-#: i2p2www/pages/site/docs/how/threat-model.html:121
-msgid "Index"
-msgstr "Índice"
-
-#: i2p2www/pages/site/faq.html:7
-msgid "General"
-msgstr "General"
-
-#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
-msgid "What systems will I2P run on?"
-msgstr "¿En qué sistemas operativos funciona I2P?"
-
-#: i2p2www/pages/site/faq.html:10
-msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
-msgstr "¿Qué es una \\\"eepsite\\\" y como configuro mi navegador para usarla?"
-
-#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:263
-msgid "My router has very few active peers, is this OK?"
-msgstr "Mi ruter tiene muy pocos pares activos, ¿Eso está bien?"
-
-#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:498
-msgid "What do the Active x/y numbers mean in the router console?"
-msgstr "¿Qué significa los números Activos x/y en la consola del ruter?"
-
-#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:225
-msgid ""
-"My active peers / known peers / participating tunnels / connections / "
-"bandwidth vary dramatically over time! Is anything wrong?"
-msgstr ""
-"¡Mis pares pares / pares conocidos / túneles participantes / conexiones /"
-" ancho de banda varían dramáticamente a lo largo del tiempo! ¿Algo está "
-"mal?"
-
-#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:348
-msgid "Is using an outproxy safe?"
-msgstr "¿Es seguro usar un outproxy (proxy de salida)?"
-
-#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:374
-msgid "Most of the eepsites within I2P are down?"
-msgstr "¿La mayoría de las eepsites en I2P están caídas?"
-
-#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:527
-msgid "What ports does I2P use?"
-msgstr "¿Qué puertos usa I2P?"
-
-#: i2p2www/pages/site/faq.html:17
-msgid "Why is I2P listening for connections on port 32000?"
-msgstr "¿Por qué I2p tiene abierto el puerto 32000?"
-
-#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
-msgid "I think I found a bug, where can I report it?"
-msgstr "Creo que he encontrado un error, ¿Dónde puedo reportarlo?"
-
-#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:107
-msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
-msgstr "¿Qué ha pasado con .i2p.net? ¿Qué ha pasado con jrandom? ¿I2P está muerto?"
-
-#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:845
-msgid "I have a question!"
-msgstr "¡Tengo una pregunta!"
-
-#: i2p2www/pages/site/faq.html:22
-#: i2p2www/pages/site/docs/api/streaming.html:292
-msgid "Setup"
-msgstr "Configuración"
-
-#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:232
-msgid ""
-"My router has been up for several minutes and has zero or very few "
-"connections"
-msgstr ""
-"Mi ruter ha estado encendido varios minutos y aún tiene ninguna o pocas "
-"conexiones"
-
-#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:390
-msgid "Why is I2P so slow?"
-msgstr "¿Por qué es tan lento I2P?"
-
-#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
-msgid ""
-"I'm missing lots of hosts in my addressbook. What are some good "
-"subscription links?"
-msgstr ""
-"Me faltan muchos dominios en mi lista de direcciones. ¿Dónde hay algunos "
-"buenos enlaces de subscripciones?"
-
-#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:383
-msgid "How do I set up my own eepsite?"
-msgstr "¿Cómo configuro mi propia eepsite?"
-
-#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:416
-msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
-msgstr "¿Preguntas sobre pluguins de I2P Bittorrent / I2PSnark / Azureus?"
-
-#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:423
-msgid "How do I connect to IRC within I2P?"
-msgstr "¿Cómo conecto a un IRC dentro de I2P?"
-
-#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:281
-msgid "I can't access regular Internet sites through I2P."
-msgstr "No puedo acceder a las webs normales a través de I2P."
-
-#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:296
-msgid "I can't access https:// or ftp:// sites through I2P."
-msgstr "No puedo acceder a webs https:// o ftp:// a través de I2P."
-
-#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:506
-msgid "Is it possible to use I2P as a SOCKS proxy?"
-msgstr "¿Es posible usar I2P como un proxy SOCKS?"
-
-#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:489
-msgid "How do I configure my browser?"
-msgstr "¿Cómo configuro mi navegador web?"
-
-#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:434
-msgid ""
-"How can I access the web console from my other machines or password "
-"protect it?"
-msgstr ""
-"¿Cómo puedo acceder a la consola web desde máquinas remotas y cómo lo "
-"protejo con contraseña?"
-
-#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:474
-msgid "How can I use applications from my other machines?"
-msgstr "¿Cómo puedo usar aplicaciones desde máquinas remotas?"
-
-#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:748
-msgid "How do I reseed manually?"
-msgstr "¿Cómo resiembro manualmente?"
-
-#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:124
-msgid "My router is using too much CPU?!?"
-msgstr "¿¡ Mi ruter usa demasiada CPU !?"
-
-#: i2p2www/pages/site/faq.html:39
-msgid "Misconception"
-msgstr "Errores comunes"
-
-#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:366
-msgid ""
-"How do I access IRC, BitTorrent, or other services on the regular "
-"Internet?"
-msgstr "¿Cómo accedo a IRC, Bittorrent u otros servicios en el internet normal?"
-
-#: i2p2www/pages/site/faq.html:42
-msgid ""
-"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
-"want it to be."
-msgstr ""
-"¿Es mi ruter un \\\"nodo de salida\\\"(outproxy) al internet normal? No "
-"quiero serlo."
-
-#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:188
-msgid ""
-"I am opposed to certain types of content. How do I keep from "
-"distributing, storing, or accessing them?"
-msgstr ""
-"Estoy en contra de cierto tipo de contenido. ¿Cómo evito almacenarlo, "
-"distribuirlo o acceder a él?"
-
-#: i2p2www/pages/site/faq.html:45
-msgid "Errors and Their Solutions"
-msgstr "Errores y sus soluciones"
-
-#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:784
-msgid ""
-"I'm using FreeBSD and when I start I2P I receive an error about "
-"libm.so.4!"
-msgstr ""
-"¡Utilizo FreeBSD y cuando ejecuto I2P recibo un error sobre "
-"libm.so.4!"
-
-#: i2p2www/pages/site/faq.html:48
-msgid ""
-"In wrapper.log I see an error stating Protocol family "
-"unavailable when I2P is loading"
-msgstr ""
-"Cuando I2P está cargando, en wrapper.log veo un error "
-"indicando Protocol family unavailable"
-
-#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
-#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:108
-#: i2p2www/pages/site/faq.html:125 i2p2www/pages/site/faq.html:189
-#: i2p2www/pages/site/faq.html:226 i2p2www/pages/site/faq.html:233
-#: i2p2www/pages/site/faq.html:264 i2p2www/pages/site/faq.html:273
-#: i2p2www/pages/site/faq.html:282 i2p2www/pages/site/faq.html:297
-#: i2p2www/pages/site/faq.html:349 i2p2www/pages/site/faq.html:367
-#: i2p2www/pages/site/faq.html:375 i2p2www/pages/site/faq.html:384
-#: i2p2www/pages/site/faq.html:391 i2p2www/pages/site/faq.html:417
-#: i2p2www/pages/site/faq.html:424 i2p2www/pages/site/faq.html:435
-#: i2p2www/pages/site/faq.html:475 i2p2www/pages/site/faq.html:482
-#: i2p2www/pages/site/faq.html:490 i2p2www/pages/site/faq.html:499
-#: i2p2www/pages/site/faq.html:507 i2p2www/pages/site/faq.html:528
-#: i2p2www/pages/site/faq.html:736 i2p2www/pages/site/faq.html:749
-#: i2p2www/pages/site/faq.html:785 i2p2www/pages/site/faq.html:817
-#: i2p2www/pages/site/faq.html:846 i2p2www/pages/site/get-involved/todo.html:16
-#: i2p2www/pages/site/get-involved/todo.html:28
-#: i2p2www/pages/site/get-involved/todo.html:52
-msgid "link"
-msgstr "enlace"
-
-#: i2p2www/pages/site/faq.html:53
-#, python-format
-msgid ""
-"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
-"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
-"(or better) with 128MB of RAM (or more). A chart comparing the performance of"
-" the various JREs can be found at http://%(trac)s/wiki/java, but in "
-"short: it's at all possible, use Sun/Oracle Java or OpenJDK."
-msgstr ""
-"Aunque se sabe que I2P se ha ejecutado en un pc tan exiguo como un "
-"Pentium II con 64Mb de RAM, tendrá una experiencia mucho mas gratificante"
-" en un Pentium III ( o mas nuevo) con 128MB de RAM (o más). Puede "
-"encontrar una tabla comparativa"
-" de rendimientos de varios JREs  en http://%(trac)s/wiki/java, "
-"pero si es posible use Sun/Oracle Java o OpenJDK."
-
-#: i2p2www/pages/site/faq.html:57
-msgid ""
-"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
-"underway to bring I2P to the Android platform."
-msgstr ""
-"I2P ha sido probado en Linux, Windows, FreeBSD ( vea la nota de abajo), OSX y Opensolaris. Se está trabajando "
-"para llevar I2P a la plataforma Android"
-
-#: i2p2www/pages/site/faq.html:65
-msgid "Here are some places, pick one or more."
-msgstr "Aquí tienen varios lugares, elija uno o mas."
-
-#: i2p2www/pages/site/faq.html:71
-msgid "Discuss with the developers on IRC in #i2p-dev"
-msgstr "Contacte con los desarrolladores en el canal #i2p-dev en el IRC"
-
-#: i2p2www/pages/site/faq.html:75
-msgid "Please include relevant information from the router logs and wrapper logs."
-msgstr ""
-"Por favor, incluya la información relevante de los registros del ruter y "
-"del wrapper."
-
-#: i2p2www/pages/site/faq.html:81
-msgid ""
-"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
-"updated rarely.\n"
-"If you don't have another subscription, you may often have to use "
-"\"jump\" links which\n"
-"is annoying."
-msgstr ""
-"La subscripción por defecto es http://www.i2p2.i2p/hosts.txt que "
-"raramente se actualiza. Si no tiene otra subscripción, a menudo tendrá "
-"que utilizar el servicio de \\\"salto\\\"  que es poco molesto."
-
-#: i2p2www/pages/site/faq.html:87
-msgid ""
-"Here are some other public addressbook subscription links. You may wish "
-"to add one or two\n"
-"to your susidns "
-"subscription list.\n"
-"You don't need to add all of them, as they sync with each other "
-"periodically.\n"
-"The links using a cgi-bin application employ various strategies to "
-"minimize\n"
-"the number of duplicate addresses delivered, so they should be more "
-"efficient.\n"
-"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
-" malicious\n"
-"subscription could give you incorrect addresses. So think about whether "
-"you\n"
-"want to trust any of these.\n"
-"The operators of these services may have various policies for listing "
-"hosts.\n"
-"Presence on this list does not imply endorsement."
-msgstr ""
-"Aquí tiene algunos enlaces públicos de subscripciones de listas de "
-"direcciones. Quizás quiera añadir uno o dos a su lista de "
-"subscripciones de susidns. No tiene que añadirlos todos, ya que se "
-"sincronizan entre ellos periódicamente. Los enlaces que utilizan una "
-"aplicación cgi-bin usan varias estrategias para minimizar el número de "
-"direcciones duplicadas enviadas, por lo que deberían ser mas eficientes. "
-"Dese cuenta que suscribirse a un servicio hosts.txt es de hecho un acto "
-"de \\\"confianza\\\", ya que una subscripción maliciosa podría darle una "
-"dirección incorrecta. Por lo que piensese bien si quiere confiar en "
-"alguno de ellos. Los operadores de estos servicios podrían tener reglas "
-"al listar los hosts. La presencia de estos servicios en esta lista no "
-"implica aprobación por nuestra parte."
-
-#: i2p2www/pages/site/faq.html:109
-msgid ""
-"Jrandom was the lead developer of I2P and\n"
-"Syndie for several years.\n"
-"We do not know if or when jrandom will return.\n"
-"The *.i2p.net domains were left in a non-functioning state after a power\n"
-"outage at the hosting company."
-msgstr ""
-"Jrandom fue el programador principal de I2P y de Syndie durante varios años. Pero "
-"no sabemos si jrandom regresará o cuando. Los dominios *.i2p.net fueron "
-"dejados sin funcionamiento después del corte por parte de la compañía de "
-"hosting."
-
-#: i2p2www/pages/site/faq.html:117
-#, python-format
-msgid ""
-"See this page for jrandom's parting message "
-"and additional information\n"
-"on the migration of *.i2p.net to this website."
-msgstr ""
-"En asta web tiene el mensaje de despedida"
-" de Jrandom e información de la migración de *.i2p.net a esta web."
-
-#: i2p2www/pages/site/faq.html:122
-msgid "I2P remains in active development."
-msgstr "I2P está en desarrollo constante."
-
-#: i2p2www/pages/site/faq.html:126
-msgid "There are many possible causes of high CPU usage. Here is a checklist:"
-msgstr "Hay varias razones para un uso excesivo de la CPU. Aquí tiene una lista:"
-
-#: i2p2www/pages/site/faq.html:131
-msgid ""
-"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
-"system. You can check \n"
-"which version of java you have installed by typing java "
-"-version at a \n"
-"command/shell prompt. Performance tends to suffer with other "
-"implementations of java."
-msgstr ""
-"Intente usar OpenJDK o Java de Sun/Oracle si está disponible en su "
-"sistema. Puede ver la versión instalada en su sistema ejecutando "
-"java -version en la terminal.El rendimiento tiende a sufrir "
-"con otras implementaciones de java."
-
-#: i2p2www/pages/site/faq.html:138
-msgid ""
-"Are you running a BitTorrent client over I2P? Try reducing the number of "
-"torrents, the bandwidth limits,\n"
-"or try turning it off completely to see if that helps."
-msgstr ""
-"¿Usa Bittorrent sobre I2P? Intente reducir el número de torrents, los "
-"límites de ancho de banda, o pruebe a apagarlo completamente a ver si eso"
-" ayuda."
-
-#: i2p2www/pages/site/faq.html:144
-msgid ""
-"Are your bandwidth limits set too high? It is possible that too much "
-"traffic is going through your\n"
-"I2P router and it is overloaded. Try reducing the setting for share "
-"bandwidth percentage on the configuration page."
-msgstr ""
-"¿Están los límites de ancho de banda demasiado altos? Es posible que pase"
-" demasiado tráfico a través de su ruter I2P y esté saturado. Intente "
-"reducir la configuración delporcentaje de ancho de banda "
-"compartidor en la web de configuración."
-
-#: i2p2www/pages/site/faq.html:149
-msgid ""
-"Make sure that you're running the latest version of I2P to get the "
-"benefits of increased performance and bug fixes."
-msgstr ""
-"Asegúrese de usar la última versión de I2P para beneficiarse de las "
-"mejoras de rendimiento y la solución de errores."
-
-#: i2p2www/pages/site/faq.html:154
-msgid ""
-"Has enough memory been set aside for use by I2P? Look at the memory graph"
-" on the graphs page to see\n"
-"if the memory usage is \"pegged\"—the JVM is spending most of its "
-"time in\n"
-"garbage collection. Increase the setting "
-"wrapper.java.maxmemory in wrapper.config."
-msgstr ""
-"¿Tiene suficiente memoria reservada para el uso de I2P? Mire la gráfica "
-"de memoria en la página de "
-"gráficos para ver si el uso de memoria está \\\"pegged\\\"—la "
-"máquina virtual de java pierde demasiado tiempo en la recogida de basura."
-" Aumente la configuración de wrapper.java.maxmemory en "
-"wrapper.config."
-
-#: i2p2www/pages/site/faq.html:161
-#, python-format
-msgid ""
-"Is the CPU usage simply higher than you would like, or is it pegged at "
-"100% for a long time?\n"
-"If it's pegged, this could be a bug. Look in the logs for clues."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:167
-#, python-format
-msgid ""
-"You may be using the Java-based BigInteger library instead of the native "
-"version,\n"
-"especially if you are running on a new or unusual OS or hardware "
-"(OpenSolaris, mipsel, etc.).\n"
-"See the jbigi page for instructions on\n"
-"diagnosing, building, and testing methods."
-msgstr ""
-"Puede que esté usando la librería BigInteger en vez de la versión nativa,"
-" especialmente si lo ejecuta en un sistema o hardware nuevo o inusual "
-"(OpenSolaris, mipsel, etc). Visite la web de "
-"jbigi que incluye instrucciones para el diagnóstico, compilado y "
-"métodos de testeo."
-
-#: i2p2www/pages/site/faq.html:175
-msgid ""
-"If your native jbigi library is working fine, the biggest user of\n"
-"CPU may be routing traffic for participating tunnels. This uses CPU\n"
-"because at each hop a layer of encryption must be decoded.\n"
-"You can limit participating traffic in two ways - by reducing the\n"
-"share bandwidth on\n"
-"confignet.jsp,\n"
-"or by setting router.maxParticipatingTunnels=nnn on\n"
-"configadvanced.jsp."
-msgstr ""
-"Si su librería jbigi nativa funciona bien, el uso excesivo de la CPU "
-"podría ser debido al tráfico enrutado de los túneles usados. Esto usa CPU"
-" porque en cada salto se debe decodificar una capa del cifrado.Puede "
-"limitar el tráfico usado de dos formas - reduciendo el ancho de banda "
-"compartido en confignet.jsp,o "
-"configurando router.maxParticipatingTunnels=nnn en configadvanced.jsp."
-
-#: i2p2www/pages/site/faq.html:190
-msgid ""
-"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
-"I2P is designed to withstand censorship, providing a means for everyone "
-"to communicate freely. \n"
-"The best way to keep your PC free of (encrypted) traffic that you dislike"
-" is to not use I2P.\n"
-"Freedom of speech has some costs.\n"
-"But let's address your question in three parts:"
-msgstr ""
-"Umm. Es un poco difícil, pues I2P es una red anónima. I2P está diseñada "
-"para evitar la censura, creando un medio para todos de comunicarse "
-"libremente.La mejor forma de mantener tu PC libre de tráfico (cifrado) "
-"que no desea es no usar I2P.La libertad de expresión tiene algunos "
-"costes.Pero respondamos su pregunta en tres partes:"
-
-#: i2p2www/pages/site/faq.html:199
-#, python-format
-msgid ""
-"Distribution - All traffic on I2P is encrypted in multiple layers."
-" You don't know\n"
-"a message's contents, source, or destination.\n"
-"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
-"Your only alternative is to refuse to route\n"
-"any traffic, by setting your share bandwidth or maximum "
-"participating tunnels to 0 (see above).\n"
-"It would be nice if you didn't do this, you should help the network by "
-"routing traffic for others.\n"
-"Over 95% of users route traffic for others."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:210
-msgid ""
-"Storage - I2P does not do distributed storage of content. You must"
-" be thinking of\n"
-"Freenet.\n"
-"Nobody's content is being stored on your computer by running I2P."
-msgstr ""
-"Almacenamiento - I2P no hace almacenamiento distribuido de "
-"contenidos. Debe estar pensando en Freenet.Ningún contenido de "
-"nadie está siendo almacenado en su computador por I2P."
-
-#: i2p2www/pages/site/faq.html:217
-msgid ""
-"Access - If there are some eepsites you don't like, don't go "
-"there.\n"
-"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
-msgstr ""
-"Acceso - Si hay eepsites que no le gustan, no navegue por ellas. O"
-" utilice un proxy de bloqueo como Privoxy o algún tipo de \\\"niñera de "
-"red\\\"."
-
-#: i2p2www/pages/site/faq.html:227
-msgid ""
-"No. This is normal.\n"
-"All routers adjust dynamically to changing network conditions and demands."
-msgstr ""
-"No, esto es normal.Todos los rutes se ajustan dinámicamente a las "
-"condiciones y necesidades de la red."
-
-#: i2p2www/pages/site/faq.html:234
-msgid ""
-"You may need to reseed your I2P router. With recent versions of I2P you "
-"can go to http://localhost:7657/configreseed"
-" and click the Save Changes and Reseed Now button. If this "
-"method doesn't work—or you're using a very old version—you "
-"may need to reseed manually."
-msgstr ""
-"Quizás necesite resembrar su ruter I2P. Con versiones recientes de I2P "
-"puede navegar a http://localhost:7657/configreseed"
-" y pulsar el botón Guardar cambios y resembrar ahora. Si este "
-"método no funciona—o está usando una versión muy vieja—podría"
-" necesitar resembrar manualmente."
-
-#: i2p2www/pages/site/faq.html:237
-msgid ""
-"The reseed URL changed a few years ago. If this is your first install and"
-" you have installed\n"
-"an old (0.6.1.30 or earlier) release, or\n"
-"you have not run I2P in a long time, you must change the URL and then\n"
-"click \"Reseed\" on the console to find other routers.\n"
-"After your router is running,\n"
-"on configadvanced.jsp,"
-"\n"
-"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
-"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
-"work),\n"
-"then click \"Apply\", then click the \"reseed\" link on the left."
-msgstr ""
-"El enlace de resiembra cambió hace unos años. Si es su primera "
-"instalación y ha instalado una versión vieja (0.6.1.30 o anterior), o no "
-"ha ejecutado I2P durante mucho tiempo , debe cambiar el enlace y entonces"
-" pulsar \\\"Resembrar\\\" en la consola para encontrar otros rutes. "
-"Después de tener el ruter funcionando, en configadvanced.jsp,"
-" añada la línea i2p.reseedURL=http://netdb.i2p2.de/ o "
-"i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (cualquiera debería "
-"funcionar), y entonces pulse en \\\"Aplicar\\\", entonces pulse el enlace"
-" \\\"Resembrar\\\" a la izquierda."
-
-#: i2p2www/pages/site/faq.html:248
-#, python-format
-msgid ""
-"This works if you are running 0.6.1.27 or later.\n"
-"If you are running release 0.6.1.31 or later, you probably don't need to "
-"do this.\n"
-"If you are running release 0.6.1.26 or earlier, either follow the\n"
-"manual reseed instructions below\n"
-"or install the latest release.\n"
-"Possible alternate method - add\n"
-"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
-"to wrapper.config, shutdown the router completely, then start again, then"
-" click \"reseed\".\n"
-"Let us know if this works."
-msgstr ""
-"Esto funciona si usa la versión 0.6.1.27 o posterior.Si usa la versión "
-"0.6.1.31 o posterior probablemente no necesite esto. Si usa la versión "
-"0.6.1.26 o anterior, o siga las instrucciones de resiembra manual abajo o"
-" instale la última versión. Un "
-"posible método alternativo - añada "
-"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/ "
-"a wrapper.config, apague el ruter completamente, y arránquelo de nuevo, "
-"entonces pulse \\\"Resembrar\\\". Háganos saber si esto funciona."
-
-#: i2p2www/pages/site/faq.html:259
-#, python-format
-msgid ""
-"...but you *really* should upgrade to "
-"the latest version."
-msgstr ""
-"Realmente debería actualizar a la "
-"última versión..."
-
-#: i2p2www/pages/site/faq.html:265
-msgid ""
-"If your router has 10 or more active peers, everything is fine. Changes "
-"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
-"efficiency of the router and effectively reduced the number of active "
-"peers.\n"
-"The router should maintain connections to a few peers at all "
-"times.\n"
-"The best way to stay \"better-connected\" to the network is to share more bandwidth."
-msgstr ""
-"Si su ruter tiene 10 o mas pares activos todo está bien. Los cambios en "
-"las versiones 0.6.1.31 y 0.6.1.32 han mejorado la eficiencia del ruter y "
-"han reducido el número de pares activos. El ruter debería tener "
-"todo el tiempo conexiones con unos pocos pares. La mejor forma de estar "
-"\\\"mejor-conectado\\\" a la red es compartiendo mas ancho de "
-"banda"
-
-#: i2p2www/pages/site/faq.html:272
-msgid ""
-"Is my router an \"exit node\" to the regular Internet? I don't want it to"
-" be."
-msgstr ""
-"¿Es mi ruter un \\\"nodo de salida\\\" al internet normal? No quiero "
-"serlo."
-
-#: i2p2www/pages/site/faq.html:274
-msgid ""
-"No. Unlike Tor,\n"
-"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
-"\n"
-"Only volunteers who set up and run separate applications will relay "
-"traffic to the regular Internet.\n"
-"There are very, very few of these."
-msgstr ""
-"No. A diferencia de Tor, "
-"los \\\"nodos de salida\\\" o \\\"outproxies\\\" no son una parte "
-"inherente de la red. Solo los voluntarios que configuran y ejecutan "
-"aplicaciones a parte reenviaran el tráfico al internet normal. Hay muy, "
-"muy pocos de estos."
-
-#: i2p2www/pages/site/faq.html:283
-msgid ""
-"See above. There are very few HTTP \"outproxies\", they are not an "
-"inherent part of the network,\n"
-"and they may not be up.\n"
-"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
-"vanished.\n"
-"The only outproxy at the moment is false.i2p.\n"
-"To use it, edit your i2ptunnel "
-"settings for eepProxy\n"
-"and set your outproxy list to 'false.i2p' (only).\n"
-"Then stop and restart the eepProxy.\n"
-"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
-"If your primary reason to use an anonymous network is to anonymously "
-"access sites\n"
-"on the regular Internet, you should probably try Tor."
-msgstr ""
-"Hay pocos \\\"outproxies\\\" HTTP, no son parte inherente de la red, y "
-"podrían no estar encendidos. Además, los viejos outproxies squid.i2p, "
-"true.i2p y krabs.i2p han desparecido. El único outproxy funcionando "
-"actualmente es false.i2p. Para usarlo, edita tu configuración"
-" de i2ptunnel para el eepProxy y pon tu lista de outproxy a "
-"'false.i2p' (sólo). Entonces reinicia el eepProxy.\n"
-"Si no funciona, el outproxy no funciona. No es un fallo de I2P. Si su "
-"razón principal para usar una red nónima es acceder a webs del Internet "
-"normal, debería probar Tor."
-
-#: i2p2www/pages/site/faq.html:298
-msgid ""
-"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
-"to-end.\n"
-"FTP is not supported for technical reasons."
-msgstr ""
-"Dentro de I2P no hay necesidad de HTTPS, todo el tráfico está cifrado de "
-"punta a punta. FTP no está soportado por razones técnicas."
-
-#: i2p2www/pages/site/faq.html:302
-msgid ""
-"There are no FTP \"outproxies\" to the Internet—it may not even be "
-"possible to set up one.\n"
-"Any other kind of outproxy may work if it's set up with a standard "
-"tunnel. \n"
-"If you would like to set up some type of outproxy, carefully research the"
-" potential risks.\n"
-"The I2P community may or may not be able to help with the technical "
-"aspects, feel free to ask."
-msgstr ""
-"No hay  \\\"outproxies\\\"  FTP hacia el Internet—pude que no sea "
-"posible configurar uno. Cualquier otro tipo de outproxy debería funcionar"
-" si está configurado con un túnel estándar. Si desea configurar algún "
-"tipo de outproxy, investigue atentamente los posibles riesgos. La "
-"comunidad I2P quizás sería capaz de ayudar con los aspectos técnicos, "
-"siéntase libre en preguntar."
-
-#: i2p2www/pages/site/faq.html:308
-msgid ""
-"As explained several times above, any existing outproxy isn't a core part"
-" of the network.\n"
-"They are services run by individuals and they may or may not\n"
-"be operational at any given time."
-msgstr ""
-"Como se ha explicado varias veces ya, cualquier outproxy existente no es "
-"parte principal de la red. Son servicios controlados por algunos usuarios"
-" y pueden estar funcionando, o no."
-
-#: i2p2www/pages/site/faq.html:313
-msgid ""
-"Update: Thanks to the work of h2ik, there is an https outproxy "
-"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
-"configured out of the box.
            \n"
-"In case the https outproxy is not available in your version of I2P, you "
-"can add it easily by doing the following:"
-msgstr ""
-"Actualización: Gracias al trabajo de h2ik, hay un outproxy https "
-"disponible para I2P. A partir de I2P 0.8.4 el túnel "
-"viene listo por defecto.
             En caso de que el outproxy https no esté "
-"disponible en su versión de I2P, puede añadirlo fácilmente haciendo esto:"
-
-#: i2p2www/pages/site/faq.html:319
-msgid ""
-"Open i2p tunnel "
-"manager. Scroll down to the bottom."
-msgstr ""
-"Abra el administrador de "
-"túneles I2P. Vaya al final de la página."
-
-#: i2p2www/pages/site/faq.html:324
-msgid ""
-"Choose CONNECT from New Client Tunnel dropdown list, click "
-"Create"
-msgstr ""
-"Seleccione CONECTAR de la lista desplegable de Nuevo túnel "
-"cliente, pulse Crear"
-
-#: i2p2www/pages/site/faq.html:329
-#, python-format
-msgid ""
-"In the new page, name and describe your new https tunnel as"
-" you like.\n"
-"The Access Point is your local port for the new https proxy "
-"recommended port's 4445.\n"
-"Outproxy should be the outproxy's .i2p address which supports "
-"https. \n"
-"See this forum post of h2ik's for the "
-"address. \n"
-"Make sure Shared Client, Delay Connect, AutoStart "
-"are checked.\n"
-"Other options should be left at the defaults. Click Save. In tunnel "
-"manger, click the Start button next to your new tunnel."
-msgstr ""
-"En la nueva página, nombre y describa su nuevo túnel https "
-"como guste. El Punto de acceso es su puerto local para el nuevo "
-"proxy https, puerto recomendado 4445. El outproxy debe ser "
-"la dirección .i2p del outproxy que soporta https. Lea el foro de h2ik para "
-"ver la dirección. Asegúrese de que Shared Client, Delay "
-"Connect y AutoStart están activados.Las demás opciones debería"
-" dejarlas como están. Pulse guardar. En el administrador de túneles, "
-"pulse el botón Iniciar junto al nuevo túnel."
-
-#: i2p2www/pages/site/faq.html:339
-msgid ""
-"In firefox, click through "
-"Tools>Options>Advanced>Network>Setting."
-"\n"
-"Untick Use this proxy for all protocol, set SSL proxy: to "
-"localhost:4445."
-msgstr ""
-"En Firefox pulse "
-"Herramientas>Opciones>Avanzado>Red>Configuración."
-" Desactive Usar el proxy para todos los protocolos, ponga en "
-"proxy SSL: localhost:4445."
-
-#: i2p2www/pages/site/faq.html:344
-msgid "Done."
-msgstr "Listo."
-
-#: i2p2www/pages/site/faq.html:350
-#, python-format
-msgid ""
-"\n"
-"This is a question that only you can answer because the correct answer "
-"depends on your behaviours, your\n"
-"threat model, and how much you trust the "
-"outproxy operator."
-msgstr ""
-"\n"
-"Eso es un cuestión que solo usted puede responder porque la respuesta "
-"correcta depende del su comportamiento, los riesgos, y cuanto confíe en el operador "
-"del outproxy."
-
-#: i2p2www/pages/site/faq.html:354
-msgid ""
-"Like Tor, I2P does not magically encrypt the Internet.\n"
-"You are vulnerable to snooping by the outproxy operators.\n"
-"The Tor"
-" FAQ\n"
-"does a good job of explaining this."
-msgstr ""
-"Al igual que Tor, I2P no cifra mágicamente Internet. Es siempre "
-"vulnerable a la inspección del tráfico por parte del operador del "
-"outproxy. El FAQ"
-" de Tor lo explica muy bien."
-
-#: i2p2www/pages/site/faq.html:360
-#, python-format
-msgid ""
-"In addition, you may be vulnerable to collusion between the outproxy "
-"operator\n"
-"and operators of other I2P services, if you use the same tunnels "
-"(\"shared clients\").\n"
-"There is additional discussion about this on %(zzz)s."
-msgstr ""
-"Además puede tener problemas por la confabulación del operador del "
-"outproxy y operadores de otros servicios de I2P si utiliza los mismos "
-"túneles (\\\"shared clients\\\"). Hay una discusión adicional sobre esto "
-"en %(zzz)s."
-
-#: i2p2www/pages/site/faq.html:368
-msgid ""
-"Unless an outproxy has been set up for the service you want to connect "
-"to, this cannot be done.\n"
-"There are only three types of outproxies running right now: HTTP, HTTPS, "
-"and email. Note that there is not a SOCKS outproxy.\n"
-"If this type of service is required, try Tor."
-msgstr ""
-"A no ser se haya configurado un outproxy para el servicio al que quiere "
-"conectar esto no se puede hacer. Sólo hay tres tipos de outproxies "
-"funcionando ahora mismo: HTTP, HTTPS, y email. Fíjese que no hay outproxy"
-" SOCKS. Si necesita este tipo de servicio pruebe Tor."
-
-#: i2p2www/pages/site/faq.html:376
-#, python-format
-msgid ""
-"If you consider every eepsite that has ever been created, yes, most of "
-"them are down.\n"
-"People and eepsites come and go.\n"
-"A good way to get started in I2P is check out a list of eepsites that are"
-" currently up.\n"
-"%(perv)s tracks active eepsites."
-msgstr ""
-"Si considera todas las eepsites que se han creado, si, la mayoría no "
-"funcionan. La gente y las eepsites van y vienen. Una buena forma de "
-"comenzar con I2P es mirar la lista de eepsites que funcionan actualmente."
-" %(perv)s informa qué "
-"páginas están activas."
-
-#: i2p2www/pages/site/faq.html:385
-msgid ""
-"Click on the Website link\n"
-"at the top of your router console for instructions."
-msgstr ""
-"Pulse en el enlace a la página "
-"web en la parte de arriba de las instrucciones de la consola del "
-"ruter."
-
-#: i2p2www/pages/site/faq.html:392
-msgid ""
-"Why are downloads, torrents, web browsing, and everything else so slow on"
-" I2P?\n"
-"The encryption and routing within the I2P network adds a substantial "
-"amount of overhead and limits bandwidth.\n"
-"Anonymity isn't free."
-msgstr ""
-"¿Por qué son tan lentas las descargas, torrents y la navegación web en "
-"I2P? El cifrado y ruteo de la red I2P añade bastante carga y limita el "
-"ancho de banda. El anonimato no es gratis."
-
-#: i2p2www/pages/site/faq.html:397
-msgid ""
-"In addition, you and everybody else probably need to increase your "
-"bandwidth limits.\n"
-"Two key settings are the inbound and outbound bandwidth limiters on\n"
-"the configuration page.\n"
-"With the default settings of 32KBps you will generally get no better than"
-" 15KBps data transfer in I2PSnark.\n"
-"Increasing the settings (but keeping within your actual connection "
-"limitations)\n"
-"will increase the potential transfer rate for I2PSnark and all other "
-"applications."
-msgstr ""
-"Además, probablemente necesite aumentar los límites de ancho de banda.Dos"
-" configuraciones importantes son los límites de entrada y salida en la página de "
-"configuración. Con la configuración por defecto de 32KBps "
-"probablemente no conseguirá mas de 15KBps de transferencia en I2PSnark. "
-"Aumentando estos valores (pero manteniéndolos dentro de las limitaciones "
-"de su conexión) Aumentará potencialmente la velocidad de transferencia de"
-" I2PSnark y otras aplicaciones."
-
-#: i2p2www/pages/site/faq.html:405
-msgid ""
-"Also, do you have sufficient share bandwidth configured to allow "
-"participating tunnels\n"
-"to route through your router? Believe it or not, allowing participating "
-"traffic\n"
-"keeps you well-integrated in the network and helps your own transfer "
-"speeds."
-msgstr ""
-"Además, ¿tiene configurado suficiente ancho de banda compartido para "
-"permitir a los túneles participantes enrutar a través de su ruter? lo "
-"crea o no, permitir tráfico participante le mantiene bien integrado en la"
-" red y le ayuda a mejorar la velocidad de transferencia."
-
-#: i2p2www/pages/site/faq.html:410
-#, python-format
-msgid ""
-"I2P is a work in progress. Lots of improvements and fixes are being "
-"implemented, and\n"
-"generally speaking, running the latest release will help your "
-"performance.\n"
-"If you haven't, install the latest "
-"release."
-msgstr ""
-"I2P es un trabajo en curso. Muchas mejoras y arreglos están siendo "
-"implementadas, y generalmente usando la última versión mejorará el "
-"rendimiento. Si no la tiene, instale la"
-" última versión."
-
-#: i2p2www/pages/site/faq.html:418
-#, python-format
-msgid ""
-"See the\n"
-"I2P Bittorrent FAQ"
-msgstr ""
-"Vea el FAQ de "
-"Bittorrent en I2P"
-
-#: i2p2www/pages/site/faq.html:425
-msgid ""
-"\n"
-"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
-" installed (see\n"
-"the I2PTunnel "
-"configuration page),\n"
-"and is automatically started when the I2P router starts. To connect to "
-"it, tell your IRC\n"
-"client to connect to localhost 6668. XChat-like client users"
-" can create a\n"
-"new network with the server localhost/6668 (remember to tick"
-" "Bypass\n"
-"proxy server" if you have a proxy server configured)."
-msgstr ""
-"\n"
-"Cuando instala I2P se crea un túnel hacia el servidor IRC de I2P, Irc2P, "
-"(vea la página "
-"de configuración de I2PTunnel), y se inicia automáticamente cuando se"
-" arranca el ruter I2P. Para conectarse a él configure su cliente IRC para"
-" conectarse a localhost 6668.  Los clientes de IRC como "
-"Xchat pueden crear una nueva conexión con el servidor "
-"localhost/6668 (recuerde pulsar "Bypassproxy "
-"server" si tiene el servidor proxy configurado)."
-
-#: i2p2www/pages/site/faq.html:436
-msgid ""
-"For security purposes, the router's admin console by default only listens"
-"\n"
-"for connections on the local interface.  However, with a little hacking,\n"
-"you can make it reachable remotely:"
-msgstr ""
-"Por razones de seguridad la consola de administración del ruter por "
-"defecto solo escucha en localhost. Aunque, con algún apaño, puede hacerla"
-" accesible remotamente:"
-
-#: i2p2www/pages/site/faq.html:444
-msgid ""
-"Open ~/.i2p/clients.config and replace
            \n"
-"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
-"with 
            \n"
-"clientApp.0.args=7657 0.0.0.0 ./webapps/"
-msgstr ""
-"Abra ~/.i2p/clients.config y cambie
             "
-"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
             por  clientApp.0.args=7657 0.0.0.0 ./webapps/"
-
-#: i2p2www/pages/site/faq.html:452
-msgid ""
-"Go to http://localhost:7657/configadvanced.jsp"
-"\n"
-"and add a new option: consolePassword=foo (or whatever "
-"password you want)"
-msgstr ""
-"Vaya a http://localhost:7657/configadvanced.jsp"
-" y añada un opción nueva: consolePassword=foo (o la "
-"contraseña que desee)"
-
-#: i2p2www/pages/site/faq.html:458
-msgid ""
-"Go to http://localhost:7657/index.jsp"
-"\n"
-"and hit \"Graceful restart\", which restarts the JVM and reloads the "
-"client applications"
-msgstr ""
-"Vaya a http://localhost:7657/index.jsp"
-" y pulse \\\"Graceful restart\\\", que reiniciará le máquina virtual y "
-"las aplicaciones clientes."
-
-#: i2p2www/pages/site/faq.html:465
-msgid ""
-"After that fires up, you should now be able to reach your console "
-"remotely.\n"
-"You will be prompted for a username and password though - the username is"
-"\n"
-"\"admin\" and the password is whatever you specified in step 2 above.  "
-"Note: the\n"
-"0.0.0.0 above specifies an interface, not a network "
-"or netmask.  0.0.0.0\n"
-"means \"bind to all interfaces\", so it can be reachable on "
-"127.0.0.1:7657 as well as\n"
-"any LAN/WAN IP."
-msgstr ""
-"Después de arrancar debería ser posible acceder a la consola remotamente."
-" Se le preguntará por el usuario y la contraseña - el usuario es "
-"\\\"admin\\\" y la contraseña la que puso en el paso 2. Nota;  "
-"0.0.0.0 especifica un dispositivo , no una red o máscara de "
-"red. 0.0.0.0 significa \\\"en todos los interfaces\\\" con lo cual es "
-"accesible tanto desde 127.0.0.1:7657 como desde la IP de LAN/WAN. "
-
-#: i2p2www/pages/site/faq.html:476
-msgid ""
-"By default, the router I2CP interface (port 7654) binds to address "
-"127.0.0.1. To bind to 0.0.0.0, set the\n"
-"router advanced configuration option "
-"i2cp.tcp.bindAllInterfaces=true and restart."
-msgstr ""
-"Por defecto el dispositivo del ruter I2CP (puerto 7654) escucha en "
-"127.0.0.1. Para que escuche en\\0.0.0.0, cambie la opción en "
-"configuración avanzada i2cp.tcp.bindAllInterfaces=true y "
-"reinicie."
-
-#: i2p2www/pages/site/faq.html:481
-msgid "Whats an \"eepsite\"?"
-msgstr "¿Qué es una \\\"eepsite\\\"?"
-
-#: i2p2www/pages/site/faq.html:483
-msgid ""
-"An eepsite is a website that is hosted anonymously - you can access it by"
-"\n"
-"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
-"listens on localhost port 4444), and browsing to the site."
-msgstr ""
-"Una eepsite es una página web hospedada anónimamente - se puede acceder a"
-" ella configurando el proxy de su navegador web (normalmente a localhost "
-"puerto 4444), y poniendo la dirección de la web en su navegador."
-
-#: i2p2www/pages/site/faq.html:491
-#, python-format
-msgid ""
-"The proxy config for different browsers is on a \n"
-"separate page with screenshots. More advanced configs with external "
-"tools\n"
-"are possible but could introduce leaks in your setup."
-msgstr ""
-"La configuración proxy para varios navegadores está en  una web aparte con capturas de "
-"pantalla. Una configuración mas avanzada con herramientas externas es "
-"posible, pero podría introducir fugas en su configuración."
-
-#: i2p2www/pages/site/faq.html:500
-msgid ""
-"x is the number of peers you've sent or received a message from\n"
-"successfully in the last minute, y is the number of peers seen in the "
-"last\n"
-"hour or so."
-msgstr ""
-"x es el número de pares a los cuales ha enviado o recibido mensajes "
-"satisfactoriamente en el último minuto, y es el número de pares vistos en"
-" la última hora."
-
-#: i2p2www/pages/site/faq.html:508
-msgid ""
-"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
-"supported.\n"
-"There is no SOCKS outproxy so it is of limited use."
-msgstr ""
-"El proxy SOCKS está soportado desde la versión 0.7.1.Está soportado SOCKS"
-" 4/4a/5.⏎ No hay proxy de salida SOCKS, con lo cual es de uso limitado."
-
-#: i2p2www/pages/site/faq.html:512
-msgid ""
-"In addition, many applications leak sensitive\n"
-"information that could identify you on the Internet. I2P only filters\n"
-"connection data, but if the program you intend to run sends this\n"
-"information as content, I2P has no way to protect your anonymity.  For\n"
-"example, some mail applications will send the IP address of the machine\n"
-"they are running on to a mail server. There is no way for I2P to filter\n"
-"this, thus using I2P to 'socksify' existing applications is possible, but"
-"\n"
-"extremely dangerous."
-msgstr ""
-"Además muchas aplicaciones tienen fugas de información sensible⏎ "
-"información que podría identificarle en Internet.⏎ I2P sólo filtra los "
-"datos de conexión, pero si el programa que ⏎ ejecuta envía esta "
-"información, I2P no tiene forma de proteger su anonimato.⏎ Por ejemplo, "
-"algunas aplicaciones de email envían la IP de la máquina ⏎ donde se "
-"ejecutan al servidor de email. No hay forma de que I2P filtre ⏎  esto, "
-"con lo cual usar I2P para 'sockificar' aplicaciones existente es posible,"
-" ⏎ pero extremadamente peligroso."
-
-#: i2p2www/pages/site/faq.html:522
-#, python-format
-msgid ""
-"If you would like more information on the socks proxy application anyway,"
-"\n"
-"there are some helpful hints on the socks page."
-msgstr ""
-"Si aún así desea mas información sobre el proxy socks,⏎hay algunas "
-"sugerencias útiles en la a href=\"%(socks)s\">web de socks"
-
-#: i2p2www/pages/site/faq.html:529
-msgid ""
-"Okay, here's a rundown of the default ports (everything is configurable\n"
-"through various settings, of course):"
-msgstr ""
-"De acuerdo, aquí hay un resumen con los puertos por defecto ( por "
-"supuesto todo es configurable a través de varias opciones):"
-
-#: i2p2www/pages/site/faq.html:538
-msgid ""
-"Internet-facing ports\n"
-"Note: New installs as of release 0.7.8 do not use port 8887; they select "
-"a random port\n"
-"between 9000 and 31000 when the program is run for the first time.\n"
-"The selected port is shown on the router configuration page."
-msgstr ""
-"Puertos abiertos al internet⏎ Nota: las nuevas instalaciones a "
-"partir de 0.7.8 no usan el puerto 8887; elijen un puerto aleatorio entre "
-"9000 y 31000 cuando el programa se ejecuta por primera vez. El puerto "
-"seleccionado se muestra en la página de configuración."
-" del ruter"
-
-#: i2p2www/pages/site/faq.html:546
-msgid ""
-"Outbound UDP from the random port noted on the configuration page to "
-"arbitrary remote UDP ports, allowing replies\n"
-"    "
-msgstr ""
-"Puerto aleatorio UDP de salida en la página de configuración "
-"hacia puertos UDP remotos, permitiendo respuestas."
-
-#: i2p2www/pages/site/faq.html:551
-msgid ""
-"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
-"    "
-msgstr ""
-"Puertos altos aleatorios de salida TCP hacia puertos aleatorios TCP "
-"remotos"
-
-#: i2p2www/pages/site/faq.html:556
-msgid ""
-"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
-"arbitrary locations\n"
-"    "
-msgstr ""
-"(opcional pero recomendado) UDP de entrada hacia el puerto indicado en"
-" la página de "
-"configuración  desde ubicaciones arbitrarias⏎"
-
-#: i2p2www/pages/site/faq.html:561
-msgid ""
-"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
-"arbitrary locations
            \n"
-"Inbound TCP may be disabled on the configuration page."
-msgstr ""
-"(opcional pero recomendado) TCP de entrada hacia el puerto indicado en"
-" la página de "
-"configuración  desde ubicaciones arbitrarias.⏎ TCP de entrada puede "
-"estar deshabilitado en la "
-"href=\"http://127.0.0.1:7657/confignet.jsp\">página de configuración "
-"
            "
-
-#: i2p2www/pages/site/faq.html:567
-msgid ""
-"Outbound UDP on port 123, allowing replies
            \n"
-"This is necessary for I2P's internal time sync (via SNTP - \n"
-"querying a random SNTP host in pool.ntp.org or another\n"
-"server you specify)"
-msgstr ""
-"Puerto 123 de salida UDP, permitiendo respuestas 
            ⏎  Este es "
-"necesario para la sincronización del reloj de I2P ( via SNTP- consultando"
-" un host SNTP aleatorio en ⏎ pool.ntp.org u otro servidor que "
-"especifique)"
-
-#: i2p2www/pages/site/faq.html:578
-msgid ""
-"Local I2P ports, listening only to local connections by default,\n"
-"except where noted:"
-msgstr ""
-"Puertos locales de I2P, escuchando por defecto solamente a "
-"conexiones locales, ⏎ excepto cuando se indique:"
-
-#: i2p2www/pages/site/faq.html:584
-msgid ""
-"1900: UPnP SSDP UDP multicast listener.\n"
-"Cannot be changed. Binds to all interfaces.\n"
-"May be disabled on confignet.jsp."
-msgstr ""
-"1900: UPnP SSDP UDP multicast listener.⏎  No puede cambiarse. "
-"Escucha en todos los dispositivos.⏎ Puede estar desactivado en confignet.jsp."
-
-#: i2p2www/pages/site/faq.html:591
-msgid ""
-"2827: BOB bridge, a higher level socket API for clients\n"
-"Disabled by default.\n"
-"May be enabled/disabled on configclients.jsp.\n"
-"May be changed in the bob.config file."
-msgstr ""
-"2827: Puente BOB, un API de alto nivel para clientes ⏎ "
-"Desactivado por defecto.⏎ Puede activarse/desactivarse en configclients.jsp.⏎ "
-"Puede cambiarse en el archivo de configuración bob.config."
-
-#: i2p2www/pages/site/faq.html:599
-msgid ""
-"4444: HTTP proxy\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-"4444: Proxy HTTP Puede activarse o cambiarse en la página de "
-"I2ptunnel en la consola del ruter. También puede configurarse para "
-"escuchar en un dispositivo determinado o en todos."
-
-#: i2p2www/pages/site/faq.html:606
-msgid ""
-"4445: HTTPS proxy\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-"4445: Proxy HTTPS  Puede cambiarse o activarse en la página de "
-"I2P túnel en la consola del ruter. También puede ser configurado para "
-"escuchar en un dispositivo determinado o en todos."
-
-#: i2p2www/pages/site/faq.html:613
-msgid ""
-"6668: IRC proxy\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-"6668: Proxy IRC Puede activarse o cambiarse en la página de "
-"I2ptunnel en la consola del ruter. También puede configurarse para "
-"escuchar en un dispositivo determinado o en todos."
-
-#: i2p2www/pages/site/faq.html:620
-msgid ""
-"7652: UPnP HTTP TCP event listener.\n"
-"Binds to the LAN address.\n"
-"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
-"May be disabled on confignet.jsp."
-msgstr ""
-"7652: UPnP HTTP TCP event listener. Escucha en la dirección de "
-"LAN. Puede cambiarse en la configuración avanzada "
-"i2np.upnp.HTTPPort=nnnn. Puede desactivarse en confignet.jsp."
-
-#: i2p2www/pages/site/faq.html:628
-msgid ""
-"7653: UPnP SSDP UDP search response listener.\n"
-"Binds to all interfaces.\n"
-"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
-"May be disabled on confignet.jsp."
-msgstr ""
-"7653: UPnP SSDP UDPsearch response listener.⏎  Escucha en todos"
-" los dispositivos.⏎ Puede cambiarse con la configuración avanzada "
-"i2np.upnp.SSDPPort=nnnn.⏎ Puede desactivarse en confignet.jsp."
-
-#: i2p2www/pages/site/faq.html:636
-msgid ""
-"7654: I2P Client Protocol port, used by client apps.\n"
-"May be changed to a different port on\n"
-"configclients.jsp"
-"\n"
-"but this is not recommended.\n"
-"May be to bind to a different interface or all interfaces, or disabled, "
-"on\n"
-"configclients.jsp."
-msgstr ""
-"7654: Puerto cliente del protocolo I2P, usado por varias "
-"aplicaciones Puede cambiarse a un puerto diferente en configclients.jsp "
-"pero no se recomienda. Puede escuchar en un dispositivo diferente, en "
-"todos o desactivarse en configclients.jsp."
-
-#: i2p2www/pages/site/faq.html:646
-msgid ""
-"7655: UDP for SAM bridge, a higher level socket API for clients\n"
-"Only opened when a SAM V3 client requests a UDP session.\n"
-"May be enabled/disabled on configclients.jsp.\n"
-"May be changed in the clients.config file with the SAM command line "
-"option sam.udp.port=nnnn."
-msgstr ""
-"7655: UDP para el puente SAM, un API para sockets de alto nivel "
-"para clientes.  Solo se abre cuando un cliente SAM V3 solicita una "
-"sesión UDP. Puede activarse/desactivarse en configclients.jsp. "
-"Puede cambiarse en el archivo clients.config en la línea "
-"sam.udp.port=nnnn."
-
-#: i2p2www/pages/site/faq.html:654
-msgid ""
-"7656: SAM bridge, a higher level socket API for clients\n"
-"Disabled by default for new installs as of release 0.6.5.\n"
-"May be enabled/disabled on configclients.jsp.\n"
-"May be changed in the clients.config file."
-msgstr ""
-"7656: Puente SAM, un API de alto nivel para clientes "
-"Desactivado por defecto para nuevas instalaciones desde la versión "
-"0.6.5. Puede activarse o desactivarse en configclients.jsp. "
-"Puede cambiarse en el archivo clients.config."
-
-#: i2p2www/pages/site/faq.html:662
-msgid ""
-"7657: Your router console\n"
-"May be disabled in the clients.config file.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces in that file."
-msgstr ""
-"7657: La consola del ruter. Puede desactivarse en el archivo "
-"clients.config. También puede ser configurado para escuchar en un "
-"dispositivo o en todos los dispositivos en ese mismo archivo."
-
-#: i2p2www/pages/site/faq.html:669
-msgid ""
-"7658: Your eepsite\n"
-"May be disabled in the clients.config file.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces in the jetty.xml file."
-msgstr ""
-"7658: Tu eepsite. Puede desactivarse en el archivo "
-"clients.config. Puede configurarse para escuchar en un dispositivo o en "
-"todos en el archivo jetty.xml."
-
-#: i2p2www/pages/site/faq.html:676
-msgid ""
-"7659: Outgoing mail to smtp.postman.i2p\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-"7659: Emails de salida hacia smtp.postman.i2p. Puede "
-"desactivarse o cambiarse en la página de i2ptunnel en la consola del "
-"ruter. También puede ser configurado para escuchar en un dispositivo o en"
-" todos."
-
-#: i2p2www/pages/site/faq.html:683
-msgid ""
-"7660: Incoming mail from pop.postman.i2p\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-"7660: Email de entrada desde pop.postman.i2p. Puede "
-"deshabilitarse o cambiarse en la página de i2ptunnel en la consola del "
-"ruter. También puede configurarse para escuchar en un dispositivo o en "
-"todos."
-
-#: i2p2www/pages/site/faq.html:690
-msgid ""
-"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-"8998:mtn.i2p2.i2p (Monotone - desactivado por defecto) Puede "
-"deshabilitarse o cambiarse en la página de i2ptunnel en la consola del "
-"ruter. También puede ser configurado para escuchar en un dispositivo o en"
-" todos."
-
-#: i2p2www/pages/site/faq.html:697
-msgid ""
-"31000: Local connection to the wrapper control channel port.\n"
-"Outbound to 32000 only, does not listen on this port.\n"
-"Starts at 31000 and will increment until 31999 looking for a free port.\n"
-"To change, see the\n"
-"wrapper documentation.\n"
-"For more information see below."
-msgstr ""
-"31000: Conexión local al puerto de control del wrapper. Salida "
-"sólo  hacia 32000, no escucha en este puerto. Empieza en 31000 y se "
-"incrementa hasta 31999 buscando un puerto libre. Para cambiarlo vea la documentación del wrapper. Para mas información vea mas abajo."
-
-#: i2p2www/pages/site/faq.html:707
-msgid ""
-"32000: Local control channel for the service wrapper.\n"
-"To change, see the\n"
-"wrapper documentation.\n"
-"For more information see below."
-msgstr ""
-"32000: Canal de conexión local para el servicio wrapper.   Para"
-" cambiarlo vea la decumentación del wrapper.. Para mas información "
-"vea mas abajo."
-
-#: i2p2www/pages/site/faq.html:719
-msgid ""
-"The local I2P ports and the I2PTunnel ports do not need to be reachable "
-"from \n"
-"remote machines, but *should* be reachable locally.  You can also create"
-" \n"
-"additional ports for I2PTunnel instances via "
-"http://localhost:7657/i2ptunnel/ \n"
-"(and in turn, would need to get your firewall to allow you local access, "
-"but \n"
-"not remote access, unless desired)."
-msgstr ""
-"Los puertos locales de I2P y los puertos de I2PTunnel no necesitan ser "
-"accesibles desde máquinas remotas, pero *deberían* ser accesibles "
-"localmente. Además puede crear también puertos adicionales para  "
-"instancias I2PTunnel vía http://localhost:7657/i2ptunnel/ ( y a su vez, "
-"necesitará permitir en su cortafuegos el acceso local, pero no remoto, a "
-"no ser que lo desee así)."
-
-#: i2p2www/pages/site/faq.html:727
-msgid ""
-"So, to summarize, nothing needs to be reachable by unsolicited remote "
-"peers, but\n"
-"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
-"outbound facing port, you'll"
-"\n"
-"get better performance.  You will also need to be able to send outbound "
-"UDP packets\n"
-"to arbitrary remote peers (blocking IPs randomly with something like "
-"PeerGuardian\n"
-"only hurts you - don't do it)."
-msgstr ""
-"Resumiendo, nada necesita ser accesible por pares remotos que no hayan "
-"sido solicitados, pero, si puede configurar son NAT/cortafuegos para "
-"permitir conexiones de entrada UDP y TCP hacia lospuertos de escucha de salida, "
-"tendrá mejor rendimiento. También necesitará ser capaz de enviar paquetes"
-" UDP de salida a pares remotos arbitrarios ( bloqueando IPs "
-"aleatoriamente con cosas como PeerGuardian solo le perjudica a usted - no"
-" lo haga)."
-
-#: i2p2www/pages/site/faq.html:735
-msgid "Why is I2P listening on port 32000?"
-msgstr "¿Porqué está escuchando I2P en el puerto 32000?"
-
-#: i2p2www/pages/site/faq.html:737
-msgid ""
-"The Tanuki java service wrapper that we use opens this port—bound "
-"to localhost—in order \n"
-"to communicate with software running inside the JVM. When the JVM is "
-"launched it is given a key \n"
-"so it can connect to the wrapper. After the JVM establishes its "
-"connection \n"
-"to the wrapper, the wrapper refuses any additional connections."
-msgstr ""
-"El servicio wrapper java Tunaki que usamos abre este puerto "
-"—escuchando en localhost—para poder comunicarse con "
-"aplicaciones dentro de la JVM máquina virtual de java. Cuando la JVM "
-"arranca se la da una clave para poder conectarse al wrapper. Después de "
-"que la  JVM establezca la conexión con el wrapper, el wrapper rechaza "
-"cualquier conexión adicional."
-
-#: i2p2www/pages/site/faq.html:743
-msgid ""
-"More information can be found in the  \n"
-"wrapper documentation."
-msgstr ""
-"Puede encontrar más información en la documentación del wrapper."
-
-#: i2p2www/pages/site/faq.html:750
-msgid ""
-"An I2P router only needs to be seeded once, to join the network for the "
-"first time.\n"
-"Reseeding is nothing more than sending plain HTTP GET requests\n"
-"to fetch a directory listing and download multiple \"routerInfo\" files\n"
-"from a predefined reseed URL."
-msgstr ""
-"Un ruter I2P sólo necesita sembrar una vez para unirse a la red por "
-"primera vez. Resembrar no es mas que enviar solicitudes normales HTTP GET"
-" para alcanzar una lista y descargar múltiples archivos \"routerInfo\" "
-"desde una URL de resembrado predefinida."
-
-#: i2p2www/pages/site/faq.html:757
-msgid ""
-"A typical symptom of a failed reseed is the \"Known\" indicator\n"
-"(on the left sidebar of the router console) displaying a very small value"
-"\n"
-"(often less than 5) which does not increase. This can occur, among other "
-"things,\n"
-"if your firewall limits outbound traffic, and blocked the reseed request."
-msgstr ""
-"Un síntoma típico de resembrado fallido es el indicador \"Conocidos\" ( "
-"en la parte izquierda del la consola del ruter) mostrando un valor muy "
-"pequeño (normalmente menos de 5) que no aumenta.. Esto puede ocurrir, "
-"además de por otras razones, si su cortafuegos limita el tráfico de "
-"salida, y ha bloqueado las solicitudes de resembrado."
-
-#: i2p2www/pages/site/faq.html:764
-msgid "To reseed an I2P router manually, do the following:"
-msgstr "Para resembrar el ruter I2P manualmente haga lo siguiente:"
-
-#: i2p2www/pages/site/faq.html:767
-msgid "Stop your I2P router"
-msgstr "Para el ruter I2P"
-
-#: i2p2www/pages/site/faq.html:770
-msgid ""
-"Open http://netdb.i2p2.de/ using a "
-"web browser"
-msgstr ""
-"Abra http://netdb.i2p2.de/ usando "
-"un explorador web."
-
-#: i2p2www/pages/site/faq.html:773
-msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
-msgstr ""
-"Guarde una docena de archivos \"routerInfo\" en el directorio \"netDb\" "
-"de su I2P"
-
-#: i2p2www/pages/site/faq.html:780
-msgid "Start your I2P router"
-msgstr "Encienda su ruter I2P"
-
-#: i2p2www/pages/site/faq.html:787
-msgid ""
-"When trying to start the router using \"i2prouter start\", you may see "
-"output like the following:"
-msgstr ""
-"Cuando intenta arrancar el ruter usando \"i2prouter start\", puede ver "
-"una salida del tipo:"
-
-#: i2p2www/pages/site/faq.html:792
-msgid ""
-"\n"
-"In order to be inclusive and try to ensure that I2P will run on as many "
-"systems \n"
-"as possible, up until I2P 0.8.9 we used a java wrapper \n"
-"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
-"are missing the necessary compatibility libraries.\n"
-"These libraries may be installed by performing the following steps:"
-msgstr ""
-"\n"
-"En el intento de hacer que I2P funcione en el mayor número de sistemas "
-"posibles, hasta I2P 0.8.9 usamos un wrapper java compilado "
-"por FreeBSD 6.x. Si recibe este error lo mas probable es que le falten "
-"las librerías necesarias. Esas librerías pueden instalarse siguiendo los "
-"pasos siguientes:"
-
-#: i2p2www/pages/site/faq.html:800
-msgid ""
-"Switch to the root user with su or log in as "
-"root."
-msgstr ""
-"Cambie al usuario root con su o inicie sesión como "
-"root."
-
-#: i2p2www/pages/site/faq.html:806
-#, python-format
-msgid ""
-"If you cannot install these compatibility libraries (or do not want to), "
-"other\n"
-"possibilities would be to compile the wrapper for your\n"
-"system, starting I2P with the runplain.sh script, or you"
-" can\n"
-"replace the wrapper with one from the source tarball."
-msgstr ""
-"Si no puede instalar estas librerías (o no lo desea), otra posibilidad "
-"sería compilar el wrapper para su "
-"sistema, arrancando con el script runplain.sh de I2P, o "
-"puede sobreescribir el wrapper por uno del archivo de las fuentes."
-
-#: i2p2www/pages/site/faq.html:812
-msgid ""
-"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
-"compiled on systems running FreeBSD 7.2."
-msgstr ""
-"A partir de la versión 0.8.9 de I2P, el wrapper ha sido actualizado a "
-"v3.5.12 y compilado en sistemas corriendo FreeBSD 7.2."
-
-#: i2p2www/pages/site/faq.html:816
-msgid ""
-"In wrapper.log I see an error that states \"Protocol "
-"family unavailable\" when loading the Router Console"
-msgstr ""
-"En el archivo wrapper.log veo un error que indica "
-"\"Protocol family unavailable\" cuando arranco la consola "
-"del ruter."
-
-#: i2p2www/pages/site/faq.html:818
-msgid ""
-"Often this error will occur with any network enabled java software on "
-"some systems that are configured to use IPv6 by default. There are a few "
-"ways to solve this:"
-msgstr ""
-"A menudo este error ocurre con cualquier aplicación java que active la "
-"red en sistemas configurados para usar IPV6 por defecto. Hay varias "
-"formas de arreglarlo:"
-
-#: i2p2www/pages/site/faq.html:823
-msgid ""
-"On Linux based systems, you can echo 0 > "
-"/proc/sys/net/ipv6/bindv6only"
-msgstr ""
-"En sistemas basados en Linix puede ejecutar echo 0 > "
-"/proc/sys/net/ipv6/bindv6only"
-
-#: i2p2www/pages/site/faq.html:825
-msgid "Look for the following lines in wrapper.config."
-msgstr "Busque por las siguientes líneas en wrapper.config."
-
-#: i2p2www/pages/site/faq.html:829
-msgid ""
-"If the lines are there, uncomment them by removing the \"#\"s. If the "
-"lines are not there, add them without the \"#\"s."
-msgstr ""
-"Si las líneas ya están ahí, descomentelas eliminando los \"#\". Si las "
-"líneas no están ahí añádalas sin los \"#\"."
-
-#: i2p2www/pages/site/faq.html:832
-msgid ""
-"Another option would be to remove the ::1 from "
-"~/.i2p/clients.config"
-msgstr ""
-"Otra opción sería borrar ::1 del archivo "
-"~/.i2p/clients.config"
-
-#: i2p2www/pages/site/faq.html:836
-msgid ""
-"WARNING: For any changes to wrapper.config "
-"to take effect, you must completely\n"
-"stop the router and the wrapper. Clicking Restart on your\n"
-"router console will NOT reread this file! You must\n"
-"click Shutdown, wait 11 minutes, then start I2P."
-msgstr ""
-"CUIDADO: Para que los cambios en "
-"wrapper.config tengan efecto debe apagar completamente el "
-"ruter y el wrapper. ¡Pulsando Reiniciar en la consola del ruter "
-"NO leerá de nuevo este archivo! Tiene que pulsar  apagar, "
-"esperar 11 minutos y entonces arrancar I2P."
-
-#: i2p2www/pages/site/faq.html:847
-#, python-format
-msgid ""
-"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
-"the forum and we'll post it here (with\n"
-"the answer, hopefully)."
-msgstr ""
-"¡Genial! Contáctenos en el IRC irc.freenode.net #i2p o escríbanos en el "
-"foro y lo publicaremos aquí (esperemos "
-"que con la respuesta)."
-
-#: i2p2www/pages/site/impressum.html:4
-msgid "German laws"
-msgstr "Leyes alemanas"
-
-#: i2p2www/pages/site/index.html:2
-msgid "I2P Anonymous Network"
-msgstr "Red anónima I2P"
-
-#: i2p2www/pages/site/index.html:4
-msgid ""
-"Anonymous peer-to-peer distributed communication layer built with open "
-"source tools and designed to run any traditional Internet service such as"
-" email, IRC or web hosting."
-msgstr ""
-"Capa anónima de comunicación distribuida par-a-par construida con "
-"herramientas de código libre y diseñada para usar cualquier servicio de "
-"internet tradicional como email, IRC, foros o páginas webs."
-
-#: i2p2www/pages/site/index.html:7
-msgid "What does I2P do for you?"
-msgstr "¿Qué hace I2P por ti?"
-
-#: i2p2www/pages/site/index.html:8
-msgid ""
-"The I2P network provides strong privacy protections for communication "
-"over the Internet. Many activities that would risk your privacy on the "
-"public Internet can be conducted anonymously inside I2P."
-msgstr ""
-"La red I2p proporciona una fuerte privacidad de las comunicaciones sobre "
-"Internet. Muchas actividades que podrían poner en riesgo su privacidad en"
-" Internet pueden hacerse anónimamente dentro de I2P."
-
-#: i2p2www/pages/site/index.html:9
-#, python-format
-msgid "Get I2P %(version)s"
-msgstr "Descarga I2P %(version)s"
-
-#: i2p2www/pages/site/index.html:13
-msgid "What is I2P?"
-msgstr "¿Qué es I2P?"
-
-#: i2p2www/pages/site/index.html:15
-msgid ""
-"I2P is a full darknet implementation - a network within a network, and is"
-" intended to protect against monitoring by third parties, such as hostile"
-" governments or ISPs.\n"
-msgstr ""
-"I2p es una implementación completa de una darkent - una red dentro de "
-"otra red, y está destinada a proteger contra la monitarización de "
-"terceras partes, como gobiernos hostiles o ISPs.\n"
-
-#: i2p2www/pages/site/index.html:18
-msgid ""
-"I2P is used by many people who care about their privacy, as well as those"
-" in high-risk situations. It is designed to protect activists, oppressed "
-"people, journalists and whistle-blowers - as well as the average person."
-"\n"
-msgstr ""
-"I2P es usado por mucha gente que se preocupa de su privacidad, y también "
-"por otras personas en situaciones de alto riesgo. Está diseñado para "
-"proteger activistas, periodistas y personas que denuncian la corrupción."
-"\n"
-
-#: i2p2www/pages/site/index.html:21
-msgid ""
-"I2P runs on Java and is therefore available anywhere Java will run, "
-"including desktops, embedded systems (like the Raspberry Pi)  and Android"
-" phones.\n"
-msgstr ""
-"I2p se ejecuta con Java por lo cual está disponible allí donde Java "
-"funcione, incluyendo sistemas de escritorio, embebidos (como Raspberry "
-"Pi) y móviles Android.\n"
-
-#: i2p2www/pages/site/index.html:25
-msgid "Read more…"
-msgstr "Leer mas…"
-
-#: i2p2www/pages/site/index.html:30
-msgid "What can you do with I2P?"
-msgstr "¿Qué puede hacer con I2P?"
-
-#: i2p2www/pages/site/index.html:33
-#, python-format
-msgid ""
-"Email Integrated web mail interface, "
-"plugin for serverless email."
-msgstr ""
-"Email Interfaz de correo web "
-"incluido, pluguin para emails sin servidorres."
-
-#: i2p2www/pages/site/index.html:38
-#, python-format
-msgid ""
-"Web browsing Anonymous "
-"websites, gateways to and from the public Internet."
-msgstr ""
-"Navegación web Webs anónimas, "
-"gateways desde y hacia el Internet público."
-
-#: i2p2www/pages/site/index.html:43
-#, python-format
-msgid ""
-"Blogging and forums "
-"Blogging and Syndie plugins."
-msgstr ""
-"Blogs y foros Blogs y "
-"pluguins para Syndie."
-
-#: i2p2www/pages/site/index.html:48
-#, python-format
-msgid ""
-"Website hosting Integrated "
-"anonymous web server."
-msgstr ""
-"Alojamiento web Servidor "
-"web anónimo integrado."
-
-#: i2p2www/pages/site/index.html:53
-#, python-format
-msgid ""
-"Real-time chat Instant "
-"messaging and IRC clients."
-msgstr ""
-"Chat en tiempo real "
-"Mensajería instantánea y clientes IRC."
-
-#: i2p2www/pages/site/index.html:58
-#, python-format
-msgid ""
-"File sharing ED2K and Gnutella"
-" clients, integrated BitTorrent client."
-msgstr ""
-"Compartición de archivos "
-"Clientes ED2K y Gnutella, cliente de BitTorrent integrado."
-
-#: i2p2www/pages/site/index.html:63
-#, python-format
-msgid ""
-"Decentralized file "
-"storage Tahoe-LAFS distributed filesystem plugin."
-msgstr ""
-"Almacenamiento de "
-"archivos descentralizado Pluguin para el sistema de archivos "
-"distribuido Tahoe-LAFS."
-
-#: i2p2www/pages/site/index.html:68
-#, python-format
-msgid "More supported applications…"
-msgstr "Más aplicaciones soportadas…"
-
-#: i2p2www/pages/site/index.html:76
-msgid "News & Updates"
-msgstr "Noticias & Actualizaciones"
-
-#: i2p2www/pages/site/links.html:4
-msgid "Recommended Links & Resources"
-msgstr "Enlaces recomendados y más recursos"
-
-#: i2p2www/pages/site/links.html:5
-#, python-format
-msgid ""
-"See also the page with\n"
-"links to presentations, videos, and tutorials about"
-" I2P."
-msgstr ""
-
-#: i2p2www/pages/site/links.html:12
-msgid "Friends of I2P"
-msgstr "Amigos de I2P"
-
-#: i2p2www/pages/site/links.html:24
-msgid "More Projects and Documentation"
-msgstr "Más proyectos y documentación"
-
-#: i2p2www/pages/site/links.html:34
-msgid "Press"
-msgstr "Prensa"
-
-#: i2p2www/pages/site/links.html:38
-msgid "Boards, newssite, others"
-msgstr "Anuncios, noticias y otros"
-
-#: i2p2www/pages/site/links.html:42
-msgid "Very Old Stuff"
-msgstr "Cosas muy antiguas"
-
-#: i2p2www/pages/site/about/browser-config.html:2
-msgid "Web Browser Configuration"
-msgstr "Configuración del navegador web"
-
-#: 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 ""
-"Su navegador web necesita ser configurado para poder navegar eepsites y "
-"para utilizar los outproxies disponibles en I2P. Debajo tiene un paso a "
-"paso para configurar los navegadores más populares."
-
-#: i2p2www/pages/site/about/browser-config.html:11
-msgid "How to configure your browser"
-msgstr "Como configurar su navegador"
-
-#: i2p2www/pages/site/about/browser-config.html:17
-#: i2p2www/pages/site/about/browser-config.html:73
-msgid "Outproxy Terms Of Service"
-msgstr "Términos de servido del Outproxy"
-
-#: i2p2www/pages/site/about/browser-config.html:22
-msgid "Internet Explorer 8 or Chrome"
-msgstr "Internet Explorer 8 o 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 ""
-"En el menú de herramientas seleccione \"Opciones de Internet\" para abrir"
-" la configuración. En la ventana de configuración seleccione la pestaña "
-"de conexiones y pulse en configuración de LAN para configurar el puerto "
-"del proxy."
-
-#: i2p2www/pages/site/about/browser-config.html:28
-msgid "IE Internet Options"
-msgstr "Opciones de Internet de IE"
-
-#: 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 ""
-"Ahora active en la casilla de confirmación \"usar un servidor proxy para "
-"la LAN\"  y también en \"Ignorar servidor para conexiones locales\". "
-"Pulsando en opciones avanzadas abrirá la ventana para abrir puertos. "
-"Entre los valores de la imagen, IP 127.0.0.1y puerto 4444 para HTTP, "
-"puerto 4445 para HTTPS."
-
-#: i2p2www/pages/site/about/browser-config.html:36
-msgid "IE Proxy Settings"
-msgstr "Configuración proxy en 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 ""
-"Desde el menú de herramientas seleccione opciones y abra el menú de "
-"configuración de Firefox. Pulse en Avanzado, entonces pulse en "
-"la pestaña Red. En la sección de Conexiones, pulse el "
-"botón de Configuración. Se le mostrará una ventana como la siguiente:"
-
-#: i2p2www/pages/site/about/browser-config.html:46
-msgid "Firefox Network Options"
-msgstr "Opciones de red de 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 ""
-"En la ventana de  Configuración de Conexiones, pulse el círculo "
-"junto a Configuración manual del proxy, entonces añada "
-"127.0.0.1, puerto 4444 en el campo Proxy HTTP. Añada 127.0.0.1, puerto "
-"4445 en el campo Proxy SSL. Asegúrese de escribir 127.0.0.1 o localhost "
-"en el campo \"Sin proxy para\"."
-
-#: i2p2www/pages/site/about/browser-config.html:53
-msgid "Firefox Proxy Settings"
-msgstr "Configuración del Proxy de 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 ""
-"Desde el menú de Configuración, seleccione Configurar "
-"Konqueror. En el grupo Navegador Web en la parte izquierda "
-"seleccione Proxy. En esta ventana nueva seleccione la opción "
-"\"Especificar manualmente las opciones del Proxy\" y pulse en "
-"Configurar."
-
-#: i2p2www/pages/site/about/browser-config.html:63
-msgid "Konqueror Proxy Options"
-msgstr "Opciones del Proxy de 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 ""
-"Escriba 127.0.0.1 y puerto 4444 en la casilla HTTP. Escriba 127.0.0.1 y "
-"puerto 4445 en la casilla HTTPS. Pulse el botón de Nuevo en la "
-"sección de Excepciones. Escriba localhost y pulse Aceptar. Pulse otra vez"
-" el botón Nuevo y escriba 127.0.0.1 y aceptar. Pulse aceptar una"
-" vez mas para salir de la ventana de configuración."
-
-#: i2p2www/pages/site/about/browser-config.html:70
-msgid "Konqueror Proxy Ports"
-msgstr "Puertos del Proxy de 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 ""
-"Recuerde: I2P no fue diseñado para crear proxies de salida al Internet.  "
-"En su lugar está diseñado para ser usado como una red interna."
-
-#: 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 ""
-"El proyecto I2P no ejecuta por sí mismo ningún proxy al Internet. Ese "
-"tipo de servicios proxy son ejecutados por voluntarios privados y pueden "
-"ser apagados o no estar accesibles en todo momento."
-
-#: i2p2www/pages/site/about/browser-config.html:83
-msgid ""
-"By default, I2P comes with two outproxies configured: "
-"false.i2p\n"
-"(an HTTP-only proxy) and outproxyng.h2ik.i2p (an HTTPS proxy"
-"\n"
-"routed through Tor."
-msgstr ""
-"Por defecto I2P viene con 2 outproxies configurados: "
-"code>false.i2p             (un proxy HTTP sólo) y "
-"outproxyng.h2ik.i2p (un proxy HTTPS a través de TOR."
-
-#: 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 ""
-"Estos dos outproxies están configurados con límites de conexiones. Esto "
-"significa que sólo están permitidos un número determinado de accesos por "
-"cliente. Cuando se alcanza el límite el cliente es bloqueado por un "
-"periodo de tiempo 1 minuto/1 hora/1 día. Tenga cuidado y no sature estos "
-"servicios con demasiadas peticiones."
-
-#: i2p2www/pages/site/about/browser-config.html:94
-#, python-format
-msgid ""
-"Filtering is active on these outproxies (for example, mibbit and torrent\n"
-"tracker access is blocked). Note that even though the pirate bay is "
-"blocked\n"
-"they host an official eepsite at %(tpb)s. "
-"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 ""
-"Hay filtros activos en estos outproxies (por ejemplo, el acceso a mibbit "
-"y tracker torrents están bloqueados) Desde cuenta que hasta The Pirate "
-"Bay está bloqueado, aunque hospedan una página eepisite en %(tpb)s. Las eepsites accesible en I2P "
-"también están bloqueadas a través de los outproxies. Por comodidad, "
-"False.i2p bloquea servidores de publicidad."
-
-#: i2p2www/pages/site/about/browser-config.html:101
-msgid ""
-"Tor is good application to use"
-" as an\n"
-"outproxy to the Internet."
-msgstr ""
-"Tor es una buen aplicación "
-"para usar como outproxy al Internet."
-
-#: i2p2www/pages/site/about/glossary.html:4
-msgid ""
-"This page lists often-used terminology when discussing I2P and "
-"cryptography."
-msgstr ""
-"Esta página muestra la terminología usada cuando se habla de I2P y "
-"cifrados."
-
-#: i2p2www/pages/site/about/hall-of-fame.html:2
-msgid "Hall Of Fame"
-msgstr "Pódium"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:5
-msgid "I2P's Hall of Fame"
-msgstr "Pódium de I2P"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:6
-#, python-format
-msgid "Current balance: as of %(date)s"
-msgstr "Balance actual a día %(date)s"
-
-#: 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:137
-#: i2p2www/pages/site/about/hall-of-fame.html:138
-#: i2p2www/pages/site/about/hall-of-fame.html:139
-#: i2p2www/pages/site/about/hall-of-fame.html:140
-#: i2p2www/pages/site/about/hall-of-fame.html:142
-#: i2p2www/pages/site/about/hall-of-fame.html:143
-#: i2p2www/pages/site/about/hall-of-fame.html:144
-#: i2p2www/pages/site/about/hall-of-fame.html:147
-#: i2p2www/pages/site/about/hall-of-fame.html:148
-#: i2p2www/pages/site/about/hall-of-fame.html:149
-#: i2p2www/pages/site/about/hall-of-fame.html:152
-#: i2p2www/pages/site/about/hall-of-fame.html:153
-#: i2p2www/pages/site/about/hall-of-fame.html:154
-#: i2p2www/pages/site/about/hall-of-fame.html:155
-#: i2p2www/pages/site/about/hall-of-fame.html:156
-#: i2p2www/pages/site/about/hall-of-fame.html:157
-#: i2p2www/pages/site/about/hall-of-fame.html:158
-#: i2p2www/pages/site/about/hall-of-fame.html:159
-#: i2p2www/pages/site/about/hall-of-fame.html:160
-#: i2p2www/pages/site/about/hall-of-fame.html:161
-#: i2p2www/pages/site/about/hall-of-fame.html:162
-#: i2p2www/pages/site/about/hall-of-fame.html:163
-#: i2p2www/pages/site/about/hall-of-fame.html:164
-#: i2p2www/pages/site/about/hall-of-fame.html:167
-#: i2p2www/pages/site/about/hall-of-fame.html:168
-#: i2p2www/pages/site/about/hall-of-fame.html:169
-#: i2p2www/pages/site/about/hall-of-fame.html:170
-#: i2p2www/pages/site/about/hall-of-fame.html:171
-#: i2p2www/pages/site/about/hall-of-fame.html:172
-#: 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: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:181
-#: i2p2www/pages/site/about/hall-of-fame.html:182
-#: 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:186
-#: i2p2www/pages/site/about/hall-of-fame.html:187
-#: 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: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: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:208
-#: i2p2www/pages/site/about/hall-of-fame.html:209
-#: i2p2www/pages/site/about/hall-of-fame.html:210
-#: i2p2www/pages/site/about/hall-of-fame.html:212
-#: i2p2www/pages/site/about/hall-of-fame.html:213
-#: 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:217
-#: i2p2www/pages/site/about/hall-of-fame.html:218
-#: i2p2www/pages/site/about/hall-of-fame.html:219
-#: 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:227
-#: i2p2www/pages/site/about/hall-of-fame.html:230
-#: i2p2www/pages/site/about/hall-of-fame.html:231
-#: 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:236
-#: i2p2www/pages/site/about/hall-of-fame.html:237
-#: i2p2www/pages/site/about/hall-of-fame.html:238
-#: i2p2www/pages/site/about/hall-of-fame.html:243
-#: 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:247
-#: 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:252
-#: 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:265
-#: 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:271
-#: 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:275
-#: i2p2www/pages/site/about/hall-of-fame.html:276
-#: i2p2www/pages/site/about/hall-of-fame.html:277
-#: i2p2www/pages/site/about/hall-of-fame.html:278
-#: 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:289
-#: 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:292
-#: i2p2www/pages/site/about/hall-of-fame.html:293
-#: i2p2www/pages/site/about/hall-of-fame.html:294
-#: i2p2www/pages/site/about/hall-of-fame.html:295
-#: i2p2www/pages/site/about/hall-of-fame.html:297
-#: i2p2www/pages/site/about/hall-of-fame.html:298
-#: i2p2www/pages/site/about/hall-of-fame.html:299
-#: i2p2www/pages/site/about/hall-of-fame.html:300
-#: 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: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:314
-#: 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:322
-#: i2p2www/pages/site/about/hall-of-fame.html:324
-#: 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:332
-#: 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: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:348
-#: i2p2www/pages/site/about/hall-of-fame.html:349
-#: i2p2www/pages/site/about/hall-of-fame.html:351
-#: i2p2www/pages/site/about/hall-of-fame.html:352
-#: 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:374
-#: 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:378
-#: i2p2www/pages/site/about/hall-of-fame.html:379
-#: 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:382
-#: i2p2www/pages/site/about/hall-of-fame.html:383
-#: 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:386
-#: 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:389
-#: i2p2www/pages/site/about/hall-of-fame.html:390
-#: i2p2www/pages/site/about/hall-of-fame.html:391
-#: i2p2www/pages/site/about/hall-of-fame.html:392
-#: i2p2www/pages/site/about/hall-of-fame.html:393
-#: i2p2www/pages/site/about/hall-of-fame.html:394
-#: i2p2www/pages/site/about/hall-of-fame.html:395
-#: i2p2www/pages/site/about/hall-of-fame.html:396
-#: i2p2www/pages/site/about/hall-of-fame.html:397
-#: i2p2www/pages/site/about/hall-of-fame.html:398
-#: i2p2www/pages/site/about/hall-of-fame.html:399
-#: 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: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: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:420
-#: 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:436
-#: 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:442
-#: i2p2www/pages/site/about/hall-of-fame.html:445
-#: 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:449
-#: 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:455
-#: i2p2www/pages/site/about/hall-of-fame.html:456
-#: i2p2www/pages/site/about/hall-of-fame.html:457
-#: i2p2www/pages/site/about/hall-of-fame.html:458
-#: 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:465
-#: i2p2www/pages/site/about/hall-of-fame.html:466
-#: i2p2www/pages/site/about/hall-of-fame.html:467
-msgid "General fund"
-msgstr "Caja total"
-
-#: 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
-#, python-format
-msgid "%(euroval)s € and %(btcval)s BTC"
-msgstr "%(euroval)s € y %(btcval)s BTC"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:11
-msgid "Datastorage bounty"
-msgstr "Recompensa por almacenamiento"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:13
-msgid "Native IPv6 I2P"
-msgstr "IPV6 nativo en I2P"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:15
-msgid "I2PHex bounty"
-msgstr "Recompensa por 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 "Mirros de Debian para I2P"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:19
-#: i2p2www/pages/site/get-involved/bounties/index.html:67
-msgid "Bitcoin client for I2P"
-msgstr "Cliente Bitcoin para I2P"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:20
-#, python-format
-msgid "%(btcval)s BTC"
-msgstr "%(btcval)s BTC"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:21
-msgid "Unit Tests for I2P router"
-msgstr "Unit Tests para el ruter I2P"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:23
-msgid "Bounty Robert"
-msgstr "Recompensa por Robert"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:24
-msgid "Bounty Syndie"
-msgstr "Recompensa por Syndie"
-
-#: 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 "Gastos mensuales actuales:"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:39
-msgid "Big thanks go to the following people who have donated to I2P!"
-msgstr "¡Muchas gracias a las siguientes personas que han donado a I2P!"
-
-#: 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 ""
-"Si ha hecho una donación , por favor envíe un email a echelon con su nombre o nick (y "
-"opcionalmente su página web) para que podamos listarle aquí."
-
-#: i2p2www/pages/site/about/hall-of-fame.html:45
-msgid "Current monthly subscriptions:"
-msgstr "Subscripciones mensuales actuales:"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:51
-msgid "2013 donations and costs:"
-msgstr "Donaciones y coste en el 2013:"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:134
-msgid "2012 donations and costs:"
-msgstr "Donaciones y coste en el 2012:"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:262
-msgid "2011 donations and costs:"
-msgstr "Donaciones y coste en el 2011:"
-
-#: i2p2www/pages/site/about/hall-of-fame.html:363
-msgid "Previous to 2011 donations:"
-msgstr "Donaciones previas al 2011:"
-
-#: i2p2www/pages/site/about/intro.html:2
-msgid "Intro"
-msgstr "Introducción"
-
-#: i2p2www/pages/site/about/intro.html:5
-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 \n"
-"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 ""
-"I2P es una red anónima que da acceso a una capa de red que las "
-"aplicaciones pueden utilizar para anonimizar y cifrar el envío de "
-"mensajes de uno a otro. La red en sí está estrictamente basada en el "
-"envío de mensajes.(a la  IP), pero "
-"existe una librería disponible que permite la comunicación segura sobre "
-"él (a la TCP)."
-" Todas las comunicaciones están cifradas de extremo a extremo ( en total "
-"de usan 4 capas de cifrados cifrados por cada mensaje enviado), e incluso"
-" el extremo final \n"
-"(\"destinaciones\") son identificados criptográficamente (básicamente con"
-" un par de claves "
-"públicas)."
-
-#: i2p2www/pages/site/about/intro.html:19
-#, 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 ""
-"Para a anonimizar los mensajes enviados, cada aplicación cliente tiene su"
-" \"ruter\" I2P que crea unos cuantos túneles\"  de entrada y salida - una "
-"secuencia de pares que pasan el mensaje en una dirección (hacia y desde "
-"el cliente, respectivamente ) A su vez, cuando un cliente \n"
-"quiere enviar un mensaje a otro cliente, el cliente envía ese mensaje a "
-"través de uno de sus túneles de salida hacia uno de los túneles de "
-"entrada del otro cliente, eventualmente alcanzando su destino."
-
-#: i2p2www/pages/site/about/intro.html:33
-#, 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 ""
-"La primera vez que un cliente quiere contactar con otro cliente, "
-"consultan la \"base de datos distribuida de la "
-"red\" - unas  tablas de "
-"hash distribuidas propia (DHT) basada en el algoritmo Kademlia. "
-"Esto se hace para encontrar el túnel de entrada del otro cliente "
-"eficientemente, pero los mensajes siguientes entre los clientes "
-"usualmente incluye la información, con lo cual\n"
-"no hace falta buscar en la base de datos de la red otra vez."
-
-#: i2p2www/pages/site/about/intro.html:44
-#, python-format
-msgid "More details about how I2P works are available."
-msgstr ""
-"Tiene disponibles mas detalles de como funciona "
-"I2P."
-
-#: i2p2www/pages/site/about/intro.html:48
-msgid "What can you do with it?"
-msgstr "¿Qué puede hacer con él?"
-
-#: i2p2www/pages/site/about/intro.html:50
-#, 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 ""
-"Dentro de la red I2P las aplicaciones no tienen restricciones en como "
-"pueden comunicarse - aquellas que normalmente usan UDP pueden usar las "
-"funcionalidades básicas de I2P, y aquellas aplicaciones que normalmente "
-"usan TCP pueden utilizar la librería 'TCP-like streaming'. I2P incluye  "
-"una aplicación genérica de puente TCP/I2P (\"I2PTunnel\") que permite enviar flujos TCP "
-"dentro de la red I2P, también recibir flujos TCP de fuera de la red y  "
-"enviar estos a una dirección IP específica."
-
-#: i2p2www/pages/site/about/intro.html:60
-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 ""
-"El túnel I2P (I2Ptunnel) es actualmente usado para permitir a la gente "
-"tener su propia web anónima (\"eepsite\"), ejecutando un servidor web "
-"normal y creando un túnel 'servidor' hacia ella, esta eepsite podrá ser "
-"accedida anónimamente sobre I2P con un navegador web normal usando un "
-"túnel proxy I2P (\"eepproxy\"). Además usamos la misma técnica para "
-"ejecutar redes IRC anónimas (donde el servidor IRC esta hospedado "
-"anónimamente y los clientes normales de IRC usan un túnel I2P para "
-"conectarse). Se están haciendo esfuerzos para programar otras "
-"aplicaciones, como una aplicación optimizada para compartir archivos (a "
-"la \n"
-"BitTorrent), almacenamiento de"
-" datos distribuido (a la Freenet /MNet), y un sistema de blogs "
-"totalmente distribuido LiveJournal, pero estos \n"
-"no están listos totalmente todavía. "
-
-#: i2p2www/pages/site/about/intro.html:76
-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 ""
-"I2P no es inherentemente una red \"outproxy\" - el cliente al que envías "
-"un mensaje es un identificador criptográfico, no una dirección IP, por lo"
-" cual el mensaje debe ser enviado a alguien que use I2P. Aunque es "
-"posible que un cliente sea un 'outproxy', permitiendo el uso de una "
-"conexión a Internet anónima, el \"eepproxy\"  aceptará URLs normales no "
-"I2P (e.g. \"http://www.i2p.net\") y las reenviará a una destinación "
-"específica que usa un proxy HTTP squid, permitiendo navegar Internet de una forma anónima"
-" y fácil. Outproxies como estos no son siempre viables  por varias "
-"razones (incluyendo el coste de tener uno y los problemas de anonimato y "
-"seguridad que acarrea), pero en ciertas circunstancias su uso puede ser "
-"apropiado."
-
-#: i2p2www/pages/site/about/intro.html:90
-#, 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 ""
-"El equipo de desarrollo de I2P es un grupo "
-"abierto, todos los que estén interesados son bienvenidos a involucrarse en el proyecto, y todo el código "
-"es libre. El núcleo de I2P y la "
-"implementación del ruter están en java (actualmente trabajando con sun y "
-"kaffe, el soporte para gjc está planeado para mas adelante), y hay un  API simple para acceder a la red desde otros "
-"lenguajes (con una librería C disponible, y con Python y Perl en "
-"desarrollo). La red está en estos momentos en desarrollo activamente y "
-"aún no ha alcanzado la versión 1.0, pero la actual hoja de ruta describe nuestro programa."
-
-#: i2p2www/pages/site/about/media.html:2 i2p2www/pages/site/about/media.html:4
-msgid "Presentations on I2P"
-msgstr "Presentaciones sobre I2P"
-
-#: 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 ""
-"Los siguientes enlaces son presentaciones, vídeos y tutoriales sobre I2P."
-" Los enlaces para investigación sobre I2P están disponibles aquí."
-
-#: i2p2www/pages/site/about/media.html:8
-#: i2p2www/pages/site/research/papers.html:8
-#, python-format
-msgid "To request an addition to this page, please send to %(email)s."
-msgstr "Para solicitar añadidos a esta web por favor envíelos a %(email)s."
-
-#: i2p2www/pages/site/about/media.html:11
-msgid ""
-"\n"
-"Newest links are at the bottom of each section."
-msgstr ""
-"\n"
-"Los enlaces mas nuevos al final de cada sección."
-
-#: i2p2www/pages/site/about/media.html:16
-msgid "Presentations"
-msgstr "Presentaciones"
-
-#: 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 ""
-"IIP Presentación en CodeCon MP3 audio transcripción Lance James (0x90), Febrero"
-" 2002."
-
-#: 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 ""
-"IIP Presentación en  ToorCon MP3 audio diapositivas Lance James (0x90), Septiembre "
-"2002."
-
-#: 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 ""
-"To Be or I2P (Youtube Video) Una "
-"introducción a las comunicaciones anónimas con I2P. To Be or I2P (PDF presentation), Jens Kubieziel,"
-" 24C3 Berlin, Diciembre 28, 2007."
-
-#: 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 ""
-"Vídeo de charla I2P en Chemnitz Linux Tag, "
-"Lars Schimmer, Marzo 14-15, 2009"
-
-#: 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 ""
-"HOPE New York Julio 17, 2010 - Vista rápida sobre I2P by zzz, al final de"
-" la charla de  Adrian Hong \\\"Hackers for Human Rights\\\". MP3 audio"
-
-#: 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 ""
-"Into the I2P Darknet: Welcome to Cipherspace"
-" Adrian Crenshaw. Schmoocon Firetalk, Enero 2011"
-
-#: 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 ""
-"Usando la tecnología para mejorar la "
-"libertad (Youtube Vídeo) Eric Johnson. Agora I/O Unconference, Marzo "
-"27, 2011. I2P desde 10:00 a 20:00 en el vídeo."
-
-#: i2p2www/pages/site/about/media.html:69
-#, python-format
-msgid ""
-"The Bright side of darknets, FOSSCOMM Patras May "
-"2011"
-msgstr ""
-"The Bright side of darknets, FOSSCOMM Patras Mayo"
-" 2011"
-
-#: 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 ""
-"Common Darknet Weaknesses⏎ (Vídeo en Youtube)⏎ "
-"Adrian Crenshaw, AIDE, Julio "
-"11-15, 2011"
-
-#: 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 ""
-"I2P / Tor Workshop Notes⏎ Adrian Crenshaw. DEF "
-"CON 19, Las Vegas, Agosto 6, 2011."
-
-#: 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 ""
-"Cipherspaces/Darknets: An Overview Of Attack "
-"Strategies -⏎ DEF CON Vesión en vivo (Vídeo de Youtube),⏎ versión de \"estudio\"  (Youtube Video),⏎ Slides (ppt)⏎ Adrian Crenshaw. DEF CON 19, Las "
-"Vegas, Agosto 7, 2011."
-
-#: i2p2www/pages/site/about/media.html:94
-msgid ""
-"Modern cipherspace ecosystems, 0x375 "
-"0x06 4/11/2011"
-msgstr ""
-"Modern cipherspace ecosystems, 0x375 "
-"0x06 4/11/2011"
-
-#: i2p2www/pages/site/about/media.html:100
-msgid "Tutorials"
-msgstr "Tutoriales"
-
-#: 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 ""
-"I2P Windows Tutorial (Youtube Video)⏎ Esta guía "
-"le mostrará cono instalar I2P en Windows. Por Telecomix"
-
-#: 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 ""
-"I2P Debian Tutorial⏎ (Vídeo en Youtube) Esta "
-"guía le mostrará como instalar I2P en sistemas basados en Debian. Por Telecomix"
-
-#: 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 ""
-"How to set up anonymous site in I2P⏎ (Vídeo en "
-"Youtube) Como configurar una web anónima en I2P. Por Telecomix"
-
-#: 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 ""
-"I2P Tutorial Mac OS X⏎ (Vídeo en Youtube) Un "
-"tutorial de como ejecutar I2P en os X y como conectar a "
-"irc.telecomix.i2p. Por Telecomix"
-
-#: 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 ""
-"Felix Atari explains the basic principles of I2P"
-" (Vídeo en Youtube) Agent Felix Atari of the Telecomix Crypto Munitions "
-"Bureau. Por Telecomix"
-
-#: 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 ""
-"How to get onto I2P, the anonymous P2P Darknet "
-"(Windows Install) (Vídeo en Youtube) Esta guía muestra como instalar "
-"y configurar las aplicaciones necesarias para acceder a I2P."
-
-#: 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 ""
-"How to connect to I2P (Vídeo en Youtube) Como "
-"instalar I2P en Ubuntu."
-
-#: 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 ""
-"Installing the I2P darknet software in Linux⏎ "
-"(Vídeo)⏎ Adrian Crenshaw.⏎ Enero 2011"
-
-#: i2p2www/pages/site/about/media.html:159
-#, python-format
-msgid ""
-"Short garlic routing animation\n"
-"(Youtube Video)\n"
-"Adrian Crenshaw.\n"
-msgstr ""
-"Short garlic routing animation (Vídeo en "
-"Youtube) Adrian Crenshaw.\n"
-
-#: i2p2www/pages/site/about/media.html:167
-msgid "Articles and Interviews"
-msgstr "Artículos y entrevistas"
-
-#: 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 ""
-"0x90 Entrevistado por DistributedCity Parte 1 "
-"Parte 2 Julio 26, 2002."
-
-#: 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 ""
-"0x90 Entrevistado por El Pais (original en Castellano) Traducción al inglés Octubre 31, 2002."
-
-#: i2p2www/pages/site/about/media.html:185
-#, python-format
-msgid ""
-"2003 Business Week article referencing "
-"invisiblenet"
-msgstr ""
-"2003 Business Week article referencing "
-"invisiblenet"
-
-#: 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 ""
-"Artículo del Netzwelt.de sobre como permanecer "
-"anónimos en Internet (Alemán) Noviembre 2007."
-
-#: i2p2www/pages/site/about/media.html:195
-#, python-format
-msgid ""
-"zzz interviewed by gulli.com\n"
-"March 2009\n"
-"German translation\n"
-"Russian translation"
-msgstr ""
-"zzz entrevistado por gulli.com⏎ Marzo 2009⏎ traducción en alemán traducción en ruso"
-
-#: i2p2www/pages/site/about/media.html:204
-#, python-format
-msgid ""
-"zzz interviewed on the InfoSec Daily Podcast Ep. 454 "
-"(mp3)\n"
-"August 18, 2011"
-msgstr ""
-"zzz entrevistado en el podcast diario de InfoSec  Ep."
-" 454 (mp3)⏎ Agosto 18, 2011"
-
-#: i2p2www/pages/site/about/media.html:209
-#, python-format
-msgid ""
-"I2P - Anonymity for the Masses,\n"
-"Jonathan Cox,\n"
-"November 11, 2011."
-msgstr ""
-"I2P - Anonymity for the Masses,⏎ Jonathan Cox,⏎ "
-"Noviembre 11, 2011."
-
-#: i2p2www/pages/site/about/media.html:215
-#, python-format
-msgid ""
-"zzz and Lance James interviewed on the InfoSec Daily "
-"Podcast Ep. 596 (mp3)\n"
-"February 16, 2012"
-msgstr ""
-"zzz y Lance James entrevistados en el podcast diario "
-"de InfoSec  Ep. 596 (mp3) Febrero 16, 2012"
-
-#: i2p2www/pages/site/about/team.html:4
-msgid "I2P Project Members"
-msgstr "Miembros del proyecto 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 ""
-"Somos un pequeño grupo de personas repartidas por varios continentes, "
-"trabajando para mejorar diferentes aspectos del proyecto y discutir el "
-"diseño de la red.¿Únete!"
-
-#: i2p2www/pages/site/about/team.html:14
-msgid "Admin"
-msgstr "Administradores"
-
-#: i2p2www/pages/site/about/team.html:15
-msgid "Project Manager"
-msgstr "Director del proyecto"
-
-#: i2p2www/pages/site/about/team.html:17
-msgid "point of contact of last resort"
-msgstr "contacto como último recurso"
-
-#: i2p2www/pages/site/about/team.html:20
-msgid "Treasurer"
-msgstr "Tesorero"
-
-#: i2p2www/pages/site/about/team.html:22
-msgid "manage donations / accounts / bounties"
-msgstr "administra las donaciones / cuentas / recompensas"
-
-#: i2p2www/pages/site/about/team.html:25
-msgid "PR manager"
-msgstr "Administrador PR"
-
-#: i2p2www/pages/site/about/team.html:27
-msgid "press contact, manages public relations and affairs"
-msgstr "contacto con la prensa, relaciones públicas y negocios"
-
-#: i2p2www/pages/site/about/team.html:30
-#, python-format
-msgid "Forum admin"
-msgstr "Administrador del Foro"
-
-#: i2p2www/pages/site/about/team.html:32
-msgid "manage the public user forum"
-msgstr "administrador del foro público"
-
-#: i2p2www/pages/site/about/team.html:35
-msgid "Mirrors admin"
-msgstr "Administrador de mirrors"
-
-#: i2p2www/pages/site/about/team.html:37
-msgid "manage the project mirrors"
-msgstr "administrador de los proyectos de los mirrors"
-
-#: i2p2www/pages/site/about/team.html:40
-#, python-format
-msgid "Monotone guru"
-msgstr "Gurú de Monotone"
-
-#: i2p2www/pages/site/about/team.html:42
-msgid "manage the public monotone repositories"
-msgstr "administrador de los repositorios públicos de monotone"
-
-#: i2p2www/pages/site/about/team.html:45
-msgid "Packager; Linux"
-msgstr "Empaquetador; Linux"
-
-#: i2p2www/pages/site/about/team.html:47
-msgid "Linux (Debian/Ubuntu) distribution packager"
-msgstr "Mantenimiento de paquetes para distribuciones Linux (Debian/Ubuntu)"
-
-#: i2p2www/pages/site/about/team.html:50
-msgid "Packager; Windows"
-msgstr "Empaquetador; Windows"
-
-#: i2p2www/pages/site/about/team.html:52
-msgid "Windows installer packager"
-msgstr "Paquetes instaladores para Windows"
-
-#: i2p2www/pages/site/about/team.html:55
-msgid "Release Manager"
-msgstr "Administrador de versiones"
-
-#: i2p2www/pages/site/about/team.html:57
-msgid "Builds and signs the releases"
-msgstr "Compila y firma los paquetes"
-
-#: i2p2www/pages/site/about/team.html:60
-msgid "Update admin"
-msgstr "Administrador de actualizaciones"
-
-#: i2p2www/pages/site/about/team.html:62
-msgid "Monitors and recruits in-network update hosts"
-msgstr "Supervisa y adquiere hosts de actualizaciones en la red"
-
-#: i2p2www/pages/site/about/team.html:65
-msgid "Reseed admin"
-msgstr "Administrador de la resiembra"
-
-#: i2p2www/pages/site/about/team.html:67
-msgid "Monitors, advises and recruits reseed hosts"
-msgstr "Supervisa, asesora y adquiere hosts de resiembra"
-
-#: i2p2www/pages/site/about/team.html:70
-msgid "Security expert"
-msgstr "Experto en seguridad"
-
-#: i2p2www/pages/site/about/team.html:71 i2p2www/pages/site/about/team.html:76
-#: i2p2www/pages/site/about/team.html:81 i2p2www/pages/site/about/team.html:101
-#: i2p2www/pages/site/about/team.html:138
-#: i2p2www/pages/site/about/team.html:148
-#: i2p2www/pages/site/about/team.html:153
-#: 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:206
-#: i2p2www/pages/site/about/team.html:228
-#: i2p2www/pages/site/get-involved/bounties/index.html:35
-#: i2p2www/pages/site/get-involved/bounties/index.html:42
-#: i2p2www/pages/site/get-involved/bounties/index.html:49
-#: i2p2www/pages/site/get-involved/bounties/index.html:56
-#: i2p2www/pages/site/get-involved/bounties/index.html:63
-#: i2p2www/pages/site/get-involved/bounties/index.html:84
-#: i2p2www/pages/site/get-involved/bounties/index.html:104
-msgid "vacant"
-msgstr "vacante"
-
-#: i2p2www/pages/site/about/team.html:72
-msgid "threat model / crypto expert"
-msgstr "modelos de amenazas / experto en cifrados"
-
-#: i2p2www/pages/site/about/team.html:75
-msgid "User Advocate"
-msgstr "Defensor del usuario"
-
-#: i2p2www/pages/site/about/team.html:77
-msgid "gather, prioritize, advocate for user needs"
-msgstr "recogida, priorización y enfocado en las necesidades de los usuarios"
-
-#: i2p2www/pages/site/about/team.html:80
-msgid "Web Designer"
-msgstr "Diseñador web"
-
-#: i2p2www/pages/site/about/team.html:82
-msgid "manage the public project website content design"
-msgstr "administrar el diseño de la web del proyecto"
-
-#: i2p2www/pages/site/about/team.html:85
-#, python-format
-msgid "Webserver admin"
-msgstr "Administrador del servidor web"
-
-#: i2p2www/pages/site/about/team.html:87
-msgid "manage the public project webservers"
-msgstr "administrador de los servidores web públicos del proyecto"
-
-#: i2p2www/pages/site/about/team.html:90
-#, python-format
-msgid "Website admin"
-msgstr "Administrador de la página web"
-
-#: i2p2www/pages/site/about/team.html:92
-msgid "manage the public project website content"
-msgstr "administrador del contenido del la web del proyecto"
-
-#: i2p2www/pages/site/about/team.html:95
-msgid "News Admin"
-msgstr "Administrador de noticias"
-
-#: i2p2www/pages/site/about/team.html:97
-msgid "manage router console news feed"
-msgstr "encargado de las noticias de la consola del ruter"
-
-#: i2p2www/pages/site/about/team.html:100
-msgid "Director of passion"
-msgstr "Director de pasión"
-
-#: i2p2www/pages/site/about/team.html:102
-msgid "community motivator"
-msgstr "Motivador de la comunidad"
-
-#: i2p2www/pages/site/about/team.html:106
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-msgid "Dev"
-msgstr "Desarrolladores"
-
-#: i2p2www/pages/site/about/team.html:107
-msgid "Core Lead"
-msgstr "Encargado del núcleo"
-
-#: i2p2www/pages/site/about/team.html:109
-msgid "lead dev for the SDK and router"
-msgstr "encargado del SDK y del ruter"
-
-#: i2p2www/pages/site/about/team.html:112
-#, python-format
-msgid "I2P mail lead"
-msgstr "Encargado de I2P mail"
-
-#: i2p2www/pages/site/about/team.html:114
-msgid "organize and develop the i2p mail system"
-msgstr "organiza y desarrolla el sistema de mail de I2P"
-
-#: i2p2www/pages/site/about/team.html:117
-#, python-format
-msgid "I2Host lead"
-msgstr "Encargado del I2Host"
-
-#: i2p2www/pages/site/about/team.html:119
-msgid "I2Host addressbook application"
-msgstr "aplicación de la lista de direcciones de I2Host"
-
-#: i2p2www/pages/site/about/team.html:122
-#, python-format
-msgid "BOB lead"
-msgstr "Encargado de BOB"
-
-#: i2p2www/pages/site/about/team.html:124
-msgid "Basic Open Bridge"
-msgstr "Basic Open Bridge"
-
-#: i2p2www/pages/site/about/team.html:127
-#, python-format
-msgid "I2P-Bote lead"
-msgstr "Encargado de I2P-Bote"
-
-#: i2p2www/pages/site/about/team.html:129
-msgid "I2PBote plugin"
-msgstr "pluguin I2PBote"
-
-#: i2p2www/pages/site/about/team.html:132
-#, python-format
-msgid "Robert lead"
-msgstr "Encargado de Robert"
-
-#: i2p2www/pages/site/about/team.html:134
-msgid "Robert BitTorrent client"
-msgstr "cliente de bittorrent Robert"
-
-#: i2p2www/pages/site/about/team.html:137
-#, python-format
-msgid "I2Phex lead"
-msgstr "Encargado de I2Phex "
-
-#: i2p2www/pages/site/about/team.html:139
-msgid "I2Phex Gnutella client"
-msgstr "cliente de I2Phex Gnutella"
-
-#: i2p2www/pages/site/about/team.html:142
-#, python-format
-msgid "I2PSnark lead"
-msgstr "Encargado de I2PSnark"
-
-#: i2p2www/pages/site/about/team.html:144
-msgid "Maintains the integrated Bittorrent client"
-msgstr "Mantiene el cliente Bittorrent integrado"
-
-#: i2p2www/pages/site/about/team.html:147
-#, python-format
-msgid "iMule lead"
-msgstr "Encargado de iMule"
-
-#: i2p2www/pages/site/about/team.html:149
-msgid "eMule client over I2P"
-msgstr "cliente e2dk sobre I2P"
-
-#: i2p2www/pages/site/about/team.html:152
-#, python-format
-msgid "Syndie lead"
-msgstr "Encargado de Syndie"
-
-#: i2p2www/pages/site/about/team.html:154
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3
-msgid "Syndie development"
-msgstr "Desarrollo de Syndie"
-
-#: i2p2www/pages/site/about/team.html:157
-msgid "Susimail lead"
-msgstr "Encargado de Susimail"
-
-#: i2p2www/pages/site/about/team.html:159
-msgid "Susimail development"
-msgstr "Desarrollo de Susimail"
-
-#: i2p2www/pages/site/about/team.html:162
-msgid "Console"
-msgstr "Consola"
-
-#: i2p2www/pages/site/about/team.html:164
-msgid "Router console HTML/CSS design"
-msgstr "Diseño del HTML/CSS de la consola del ruter"
-
-#: i2p2www/pages/site/about/team.html:167
-msgid "SAM"
-msgstr "SAM"
-
-#: i2p2www/pages/site/about/team.html:169
-msgid "SAM maintainer"
-msgstr "Encargado de SAM"
-
-#: i2p2www/pages/site/about/team.html:172
-msgid "I2PCPP lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:174
-msgid "C++ Router"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:177
-msgid "Console Translations"
-msgstr "Traducciones de la Consola"
-
-#: i2p2www/pages/site/about/team.html:179
-msgid "Chinese"
-msgstr "Chino"
-
-#: i2p2www/pages/site/about/team.html:183
-msgid "Dutch"
-msgstr "Holandés"
-
-#: i2p2www/pages/site/about/team.html:187
-msgid "French"
-msgstr "Francés"
-
-#: i2p2www/pages/site/about/team.html:191
-msgid "German"
-msgstr "Alemán"
-
-#: i2p2www/pages/site/about/team.html:195
-msgid "Russian"
-msgstr "Ruso"
-
-#: i2p2www/pages/site/about/team.html:199
-msgid "Spanish"
-msgstr "Castellano"
-
-#: i2p2www/pages/site/about/team.html:203
-msgid "Arabic"
-msgstr "Árabe"
-
-#: i2p2www/pages/site/about/team.html:207
-msgid "Other languages"
-msgstr "Otros idiomas"
-
-#: i2p2www/pages/site/about/team.html:210
-msgid "Contributors"
-msgstr "Contribuidores"
-
-#: i2p2www/pages/site/about/team.html:212
-msgid "fire2pe dev, console enhancements"
-msgstr "Desarrollador de fire2pe, mejoras de la consola"
-
-#: i2p2www/pages/site/about/team.html:216
-msgid "desktopgui, dijjer port"
-msgstr "entorno de escritorio, puerto dijjer"
-
-#: i2p2www/pages/site/about/team.html:220
-msgid "Debian/Ubuntu Packager and PPA maintainer"
-msgstr "Encargado de los paquetes para Debian/Ubuntu y del PPA"
-
-#: i2p2www/pages/site/about/team.html:224
-msgid "Routerconsole backend and UI work, website revamp, unit tests work"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:229
-msgid "Help needed on many fronts!"
-msgstr "Se necesita diversas formas de ayuda"
-
-#: i2p2www/pages/site/about/team.html:233
-msgid "Past contributors"
-msgstr "Participantes pasados"
-
-#: i2p2www/pages/site/about/team.html:235
-msgid "I2PTunnel development, ministreaming library"
-msgstr "Desarrollo de I2PTunnel, librería de ministreaming"
-
-#: i2p2www/pages/site/about/team.html:239
-msgid "Project lead, Syndie lead"
-msgstr "Encargado del proyecto, encargado de Syndie"
-
-#: i2p2www/pages/site/about/team.html:243
-msgid "Project lead, Syndie lead, I2Phex, support guru"
-msgstr "Encargado del proyecto, encargado de Syndie, I2Phex, soporte"
-
-#: i2p2www/pages/site/about/team.html:247
-msgid "iMule lead"
-msgstr "Encargado de IMule"
-
-#: i2p2www/pages/site/about/team.html:251
-#: i2p2www/pages/site/about/team.html:255
-#: i2p2www/pages/site/about/team.html:259
-msgid "I2Phex work"
-msgstr "Trabajo en I2Phex"
-
-#: i2p2www/pages/site/about/team.html:263
-msgid "Python SAM library, attack simulations"
-msgstr "librería SAM en Python, simulaciones de ataques"
-
-#: i2p2www/pages/site/about/team.html:267
-msgid "i2pmail development"
-msgstr "Desarrollo de i2pmail"
-
-#: i2p2www/pages/site/about/team.html:271
-msgid "Syndie help"
-msgstr "Ayuda de Syndie"
-
-#: i2p2www/pages/site/about/team.html:275
-msgid "i2p mail,susimail and susidns apps"
-msgstr "Mail de i2p, susimail y aplicaciones susidns"
-
-#: i2p2www/pages/site/about/team.html:279
-msgid "I2Phex (port of Phex to I2P)"
-msgstr "I2Phex (versión de Phex para I2P)"
-
-#: i2p2www/pages/site/about/team.html:283
-msgid "addressbook,i2p-bt,syndie client"
-msgstr "libreta de direcciones, i2p-bt,cliente syndie"
-
-#: i2p2www/pages/site/about/team.html:287
-msgid "organize and develop the i2p-bt BitTorrent port"
-msgstr "organización y desarrollo de la versión de Bittorrent i2p-bt"
-
-#: i2p2www/pages/site/about/team.html:291
-msgid "addressbook, i2p-bt, syndie client development"
-msgstr "libreta de direcciones, i2p-bt, y desarrollo del cliente de syndie"
-
-#: i2p2www/pages/site/about/team.html:295
-msgid "encryption and signature routines, I2PIM"
-msgstr "rutinas de cifrado y firma, I2P IM"
-
-#: i2p2www/pages/site/about/team.html:299
-msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)"
-msgstr "código jython de SAM, trabajo en stasher (DHT) y v2v (VoI2P)"
-
-#: i2p2www/pages/site/about/team.html:303
-msgid "installer, systray, bogobot"
-msgstr "instalador, bandeja de sistema, bogobot"
-
-#: i2p2www/pages/site/about/team.html:307
-msgid "jbigi development, wiki migration, doc cleanup"
-msgstr "desarrollo de jbigi, migración de la wiki, limpieza de la documentación"
-
-#: i2p2www/pages/site/about/team.html:311
-msgid "java debugging and client development on I2PTunnel and the router console"
-msgstr ""
-"depuración de java y desarrollo del cliente en I2PTunnel y en la consola "
-"del ruter"
-
-#: i2p2www/pages/site/about/team.html:315
-msgid "SAM perl module"
-msgstr "Módulo perl de SAM"
-
-#: i2p2www/pages/site/about/team.html:319
-msgid "i2psnark work"
-msgstr "trabajo en i2psnark"
-
-#: i2p2www/pages/site/about/team.html:323
-msgid "java cleanup"
-msgstr "limpieza de java"
-
-#: i2p2www/pages/site/about/team.html:327
-msgid "docs. wiki migration"
-msgstr "documentos, migración de la wiki"
-
-#: i2p2www/pages/site/about/team.html:331
-msgid "translations into French"
-msgstr "traducción al francés"
-
-#: i2p2www/pages/site/about/team.html:335
-msgid "C port of jcpuid"
-msgstr "port en C de jcpuid"
-
-#: i2p2www/pages/site/about/team.html:339
-msgid "C# SAM library, pants, fortuna integration"
-msgstr "librería C# de SAM, integración de fortuna"
-
-#: i2p2www/pages/site/about/team.html:343
-msgid "libSAM"
-msgstr "libSAM"
-
-#: i2p2www/pages/site/about/team.html:347
-#: i2p2www/pages/site/about/team.html:351
-msgid "i2p-bt tracker development"
-msgstr "desarrollo del tracker i2p-bt"
-
-#: i2p2www/pages/site/about/team.html:355
-msgid "Console and website themes"
-msgstr "Temas de la consola y la web"
-
-#: i2p2www/pages/site/about/team.html:358
-msgid "… and many others"
-msgstr "… y muchas otras"
-
-#: i2p2www/pages/site/about/performance/future.html:2
-msgid "Future Performance Improvements"
-msgstr ""
-
-#: i2p2www/pages/site/about/performance/future.html:4
-#: i2p2www/pages/site/docs/api/bob.html:3
-#: i2p2www/pages/site/docs/api/datagrams.html:3
-#: i2p2www/pages/site/docs/how/garlic-routing.html:3
-#: i2p2www/pages/site/docs/protocol/index.html:3
-#: i2p2www/pages/site/docs/transport/ntcp.html:3
-msgid "August 2010"
-msgstr "Agosto del 2010"
-
-#: 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 ""
-"Para ver las mejoras de rendimiento pasadas vea  "
-"Historial de rendimiento."
-
-#: 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 "Base de datos de la Red I2P"
-
-#: 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 "Ajustar tiempo máximo de espera"
-
-#: 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 "Gráfica Histórica de Rendimiento"
-
-#: 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 "añadido"
-
-#: 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
-#, python-format
-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 "añadido pero necesita más trabajo"
-
-#: 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
-#, python-format
-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 "Más eficiente con las caídas y errores del protocolo TCP"
-
-#: 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 shitlist) 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 "Comprimidos algunos datos estructurales"
-
-#: 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:5
-msgid ""
-"How does I2P work, why is it slow, and why does it not use my full "
-"bandwidth?"
-msgstr ""
-"¿Cómo funciona I2P, porqué es lento, y por que no utiliza todo el ancho "
-"de banda?"
-
-#: 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 ""
-"Probablemente una de las preguntas más frecuentes es ¿cómo de rápido es "
-"I2P?, y parece que a nadie le gusta la respuesta - \"depende\". Después "
-"de probar I2P, la siguiente cosa que preguntan es ¿será más rápido?, y la"
-" respuesta a eso es un enfático sí."
-
-#: 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 ""
-"I2P es un red totalmente dinámica. Cada cliente es conocido por otros "
-"nodos y prueba los nodos conocidos localmente para comprobar su "
-"accesibilidad y su capacidad. Sólo los nodos accesibles y capaces son "
-"guardados en la NetDB local (Esto normalmente es sólo una parte de la "
-"red, sobre 500-1000). Cuando I2P construye túneles selecciona los mejores"
-" recursos de esta fuente. Por ejemplo, sólo unos 20-50 nodos están "
-"disponibles para construir túneles. Ya que las pruebas se hacen cada "
-"minuto la fuente de los nodos usados cambia cada minuto. Cada nodo I2P "
-"conoce una parte de la red total, haciendo que cada ruter tenga una lista"
-" diferente de nodos I2P para ser usados como túneles. Incluso si dos "
-"ruters tienen la misma subred de nodos conocidos las pruebas de "
-"accesibilidad y capacidad mostrarán diferentes resultados, ya que cuando "
-"un ruter hace las pruebas otros ruters pueden estar bajo carga, pero "
-"estar libre cuando es un segundo ruter el que hace las pruebas."
-
-#: 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 ""
-"El texto anterior explica por que cada nodo I2P usa diferentes nodos para"
-" construir sus túneles. Por que cada nodo I2P tienen una latencia y ancho"
-" de banda diferente, los túneles ( que se construyen con estos nodos) "
-"tienen valores diferentes de latencia y ancho de banda. Y ya que cada "
-"nodo I2P tiene diferentes nodos construidos, no hay dos nodos I2P con la "
-"misma configuración de túneles."
-
-#: 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 ""
-"Un servidor/cliente se conoce como \"destinación\"  y cada destinación "
-"tiene al menos un túnel de entrada y otro de salida. Por defecto son 3 "
-"saltos por túnel. Esto suman 12 saltos (osea 12 diferentes nodos I2P) "
-"para una ida y vuelta completa cliente-servidor-cliente."
-
-#: 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 ""
-"Cada paquete de datos es enviado a través de otros 6 nodos I2P hasta que "
-"alcanza el servidor:"
-
-#: i2p2www/pages/site/about/performance/index.html:40
-msgid "and on way back 6 different I2P nodes:"
-msgstr "y de vuelta por 6 nodos I2P diferentes:"
-
-#: 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 ""
-"Como la mayoría del tráfico I2P (www, torrent, ...) necesita paquetes ack"
-" hasta que la nueva información es enviada, necesita esperar hasta que un"
-" paquete ack regrese del servidor. Al final: envía información, espera "
-"por ack, envía mas información, espera por ack... Y ya que el RTT "
-"(RoundTripTime) añade latencia por cada nodo individual I2P y por cada "
-"conexión de esta ida y vuelta, normalmente tarda de 1-3 segundos hasta "
-"que un paquete ack regresa al cliente. Además el funcionamiento interno "
-"del transporte de TCP y de I2P hacen que un paquete de información tenga "
-"un tamaño limitado y no pueda ser tan grande como desearíamos que fuese. "
-"Estas condiciones unidas crean un límite de ancho de banda por túnel de "
-"20-50 kbyte/sec. Pero, si SÓLO un salto del túnel tiene solamente 5 "
-"kb/sec de ancho de banda para usar, el túnel completo estará limitado a 5"
-" kb/sec, independientemente de las latencia y otras limitaciones."
-
-#: 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 ""
-"Debido al cifrado usado y otras configuraciones de I2P (como se "
-"construyen los túneles, latencia, ...) se utiliza bastante tiempo de la "
-"CPU para crear un túnel. Esto es por lo que una destinación solo tiene "
-"permitido un máximo de 6 túneles de  de entrada y 6 de salida para enviar"
-" información. Con un máximo de 50 kb/sec por túnel una destinación podría"
-" usar aproximadamente 300 kb/sec (en realidad podría ser más si se "
-"utilizan túneles más cortos con poco o ningún anonimato). Los túneles "
-"usados son eliminados cada 10 minutos y se crean unos nuevos. Estos "
-"cambios en los túneles (y a veces los clientes que apagan de golpe usando"
-" \"apagar inmediatamente\" o por caídas de corriente) a veces rompen los "
-"túneles y las conexiones, como se puede ver en las pérdidas de conexiones"
-" en el IRC2P (ping timeout) o cuando se está usando eepget."
-
-#: 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 ""
-"Con un número limitado de destinaciones y un número limitado de túneles "
-"por destinación, un nodo I2P sólo utiliza un número limitado de túneles a"
-" través de otros nodos de I2P. Por ejemplo, si en el ejemplo de arriba un"
-" nodo I2P es \"hop1\", sólo tendríamos 1 túnel participante originado en "
-"el cliente. Si sumamos toda la red I2P, sólo un número limitado de "
-"túneles participantes pueden ser construidos con una cantidad limitada de"
-" ancho de banda. Si uno distribuye todo ese número limitado entre el "
-"número de nodos I2P, sólo hay disponible una fracción del ancho de "
-"banca/capacidad disponible para el uso."
-
-#: 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 ""
-"Para permanecer anónimos un ruter no debería usarse por toda la red para "
-"construir túneles, si un solo ruter funciona como túnel para TODOS los "
-"nodos de I2P se convierte en el centro de un problema, así como el punto "
-"central para obtener IPs e información de los clientes. Esto no es bueno."
-" I2P intenta repartir la carga a través de muchos nodos I2P justo por "
-"esta razón."
-
-#: 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 ""
-"Otro punto a tener en cuenta es la red mesh completa. Cada conexión "
-"salto-a-salto utiliza una conexión TCP o UDP en los nodos de I2P. Con "
-"1000 conexiones uno ve 1000 conexiones TCP. Eso es bastante y algunos "
-"ruters domésticos o de oficina (DSL, cable...) sólo permiten un cierto "
-"número de conexiones ( o simplemente se vuelven locos si se usa un número"
-" mayor de X conexiones). I2P intenta limitar esas conexiones por debajo "
-"de 1500 para UDP y TCP. Esto limita también la cantidad de tráfico "
-"enrutado a través de su nodo I2P."
-
-#: 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 ""
-"En resumen, I2P es muy complejo y no hay una forma fácil de determinar "
-"con precisión por qué su nodo no se utiliza. Si su ruter es accesible y "
-"tiene mas de 128 kbyte/sec de ancho de banda compartido y está accesible "
-"24/7, debería ser usado después de algún tiempo de tener tráfico "
-"participante. Si no esta activo siempre, las pruebas de otros nodos sobre"
-" su nodo I2P les dirá: no está accesible. Esto bloquea su nodo por al "
-"menos 24h para los otros nodos. Por lo cual los otros nodos que han "
-"testado su nodo cuando estaba caído no utilizaran su nodo para construir "
-"túneles durante 24h. Esto es por lo que su tráfico será menor después de "
-"un reinicio/apagado por lo menos durante 24h."
-
-#: 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 ""
-"Además: otros nodos I2P necesitan conocer su ruter I2P para probar la "
-"accesibilidad y capacidad. Toma tiempo que otros nodos lleguen a conocer "
-"su nodo. Será más rápido si utiliza I2P y crea más túneles, por ejemplo "
-"usando torrents o webs i2p durante algún tiempo."
-
-#: i2p2www/pages/site/about/performance/index.html:99
-msgid "Performance Improvements"
-msgstr "Mejoras en el rendimiento"
-
-#: i2p2www/pages/site/about/performance/index.html:101
-#, python-format
-msgid ""
-"For possible future performance improvements see\n"
-"Future Performance Improvements."
-msgstr ""
-"Para futuras mejoras en el rendimiento vea mejoras"
-" futuras en el rendimiento."
-
-#: i2p2www/pages/site/comparison/freenet.html:2
-msgid "I2P Compared to Freenet"
-msgstr "Comparación de I2P con Freenet"
-
-#: i2p2www/pages/site/comparison/freenet.html:8
-msgid ""
-"Freenet is a fully distributed, peer to peer anonymous publishing "
-"network, offering \n"
-"secure ways to store data, as well as some approaches attempting to "
-"address the loads\n"
-"of a flash flood.  While Freenet is designed as a distributed data store,"
-" people have\n"
-"built applications on top of it to do more generic anonymous "
-"communication, such as \n"
-"static websites and message boards."
-msgstr ""
-"Freenet es una red completamente distribuida, red anónima de publicación "
-"par a par, que ofrece una forma segura de almacenar datos, y también "
-"enfocada en solucionar los problemas de carga y desbordamientos. Mientras"
-" que Freenet está diseñada como un almacén distribuido de datos, la gente"
-" ha construido aplicaciones sobre el sistema para tener otras "
-"comunicaciones anónimas genéricas, como webs estáticas y foros."
-
-#: i2p2www/pages/site/comparison/freenet.html:16
-#, python-format
-msgid ""
-"Compared to I2P, Freenet offers some substantial benefits - it is a "
-"distributed data\n"
-"store, while I2P is not, allowing people to retrieve the content "
-"published by others \n"
-"even when the publisher is no longer online.  In addition, it should be "
-"able to \n"
-"distribute popular data fairly efficiently.  I2P itself does not and will"
-" not provide \n"
-"this functionality.  On the other hand, there is overlap for users who "
-"simply want to \n"
-"communicate with each other anonymously through websites, message boards,"
-" file sharing\n"
-"programs, etc.  There have also been some attempts to develop a "
-"distributed data \n"
-"store to run on top of I2P,\n"
-"(most recently a port of Tahoe-LAFS)\n"
-"but nothing is yet ready for general use."
-msgstr ""
-"Comparado con I2P, Freenet ofrece substanciales beneficios - es un "
-"sistema distribuido de almacenamiento de datos, mientras que I2P no lo "
-"es, permitiendo a la gente obtener al contenido publicado por otros "
-"incluso cuando el que lo ha publicado no esté online. Además es capaz de "
-"distribuir eficientemente la información más utilizada. I2P ni tiene ni "
-"tendrá esta funcionalidad. Por otro lado, hay demasiada redundancia para "
-"los usuarios que simplemente quieren comunicarse con otros anónimamente a"
-" través de webs, foros, aplicaciones de compartición de archivos, etc.  "
-"Ha habido varios intentos de desarrollar un sistema de almacenamiento "
-"distribuido funcionando sobre I2P, (más recientemente un port de Tahoe-LAFS) pero todavía no está listo para uso "
-"general."
-
-#: i2p2www/pages/site/comparison/freenet.html:29
-msgid ""
-"However, even ignoring any implementations issues, there are some "
-"concerns \n"
-"about Freenet's algorithms from both a scalability and anonymity "
-"perspective, owing \n"
-"largely to Freenet's heuristic driven routing.  The interactions of "
-"various techniques \n"
-"certainly may successfully deter various attacks, and perhaps some "
-"aspects of the \n"
-"routing algorithms will provide the hoped for scalability.  "
-"Unfortunately, not much\n"
-"analysis of the algorithms involved has resulted in positive results, but"
-" there is still\n"
-"hope.  At the very least, Freenet does provide substantial anonymity "
-"against an attacker\n"
-"who does not have the resources necessary to analyze it further."
-msgstr ""
-"Sin ,embargo, e incluso ignorando los problemas de implementación, hay "
-"algunas preocupaciones sobre la escalabilidad y el anonimato de algunos "
-"algoritmos de Freenet, debido básicamente a la heurística de ruteo  de "
-"Freenet. La unión de varias técnicas puede desalentar el hacer varios "
-"tipos de ataques, y quizás algunos aspectos del algoritmo de ruteo "
-"podrían proveer la escalabilidad esperada. Desafortunadamente, no muchos "
-"de los análisis sobre los algoritmos han dado resultados satisfactorios, "
-"pero aún hay esperanzas. Al final, Freenet nos proporciona bastante "
-"anonimato contra cualquier atacante que no tenga los recursos necesarios "
-"para análisis completos."
-
-#: i2p2www/pages/site/comparison/index.html:2
-msgid "Comparing I2P to other projects"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:4
-msgid ""
-"There are a great many other applications and projects working on "
-"anonymous \n"
-"communication and I2P has been inspired by much of their efforts.  This "
-"is not \n"
-"a comprehensive list of anonymity resources - both freehaven's \n"
-"Anonymity "
-"Bibliography\n"
-"and GNUnet's related "
-"projects\n"
-"serve that purpose well.  That said, a few systems stand out for further\n"
-"comparison. The following have individual comparison pages:"
-msgstr ""
-"Hay muchas otras buenas aplicaciones y proyectos trabajando en "
-"comunicaciones anónimas, e I2P se ha inspirado en muchos de sus "
-"esfuerzos. Esto no es una lista completa de recursos para el anonimato - "
-"ambos \n"
-"Anonymity "
-"Bibliography y los proyectos relacionados con "
-"GNUnet sirven también para ese mismo propósito. Dicho eso, pocos "
-"proyectos destacan como para comparaciones adicionales. Los siguientes "
-"proyectos tienen webs con comparaciones individuales:"
-
-#: i2p2www/pages/site/comparison/index.html:20
-#, python-format
-msgid ""
-"The following are discussed on the other "
-"networks page:"
-msgstr ""
-"Los siguientes proyectos son discutidos en la página sobre otras redes:"
-
-#: i2p2www/pages/site/comparison/index.html:32
-#, python-format
-msgid ""
-"The content of this page is subject to update, discussion and dispute, "
-"and we welcome comments and additions.\n"
-"You may contribute an analysis by entering a new ticket on Trac."
-msgstr ""
-"El contenido de esta página puede ser objeto de actualizaciones, "
-"discusión y disputa, y aprobamos comentarios y adiciones. Puede "
-"contribuir al análisis creando una nueva entrada en el Trac."
-
-#: i2p2www/pages/site/comparison/other-networks.html:2
-msgid "I2P Compared to Other Anonymous Networks"
-msgstr "Comparación de I2P con otras redes anónimas"
-
-#: i2p2www/pages/site/comparison/other-networks.html:5
-msgid "The following networks are discussed on this page."
-msgstr "Las siguientes redes son discutidas en esta página."
-
-#: i2p2www/pages/site/comparison/other-networks.html:16
-#, python-format
-msgid ""
-"Most of the following sections are fairly old, and may not be accurate.\n"
-"For an overview of available comparisons, see the\n"
-"main network comparisons page.\n"
-"You may contribute an analysis by entering a\n"
-"new ticket on %(trac)s."
-msgstr ""
-"La mayoría de las siguientes secciones son bastante viejas y podrían no "
-"ser precisas.  Para una vista general de comparaciones disponibles, vea "
-"lapágina principal de comparaciones entre "
-"redes. Pude contribuir al análisis creando un nuevo ticket en el %(trac)s."
-
-#: i2p2www/pages/site/comparison/other-networks.html:29
-#, python-format
-msgid ""
-"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
-" \n"
-"anonymizing proxies, allowing people to tunnel out through the low "
-"latency \n"
-"mix network.  Morphmix includes some very interesting collusion detection"
-" \n"
-"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
-"IP\n"
-"addresses to accomplish the same.  The two primary differences between \n"
-"these systems and I2P are related to I2P's threat model \n"
-"and their out-proxy design (as opposed to providing both sender and "
-"receiver \n"
-"anonymity).  There is source code available to both systems, but we are "
-"not aware \n"
-"of their use outside of academic environments."
-msgstr ""
-"Morphmix y Tarzan son las dos totalmente distribuidas, redes para a par "
-"anónimas con proxies para el anonimato, permitiendo a la gente enviar "
-"datos fuera a través de redes de mezcla de baja latencia. Morphmix "
-"incluye unos algoritmos de detección de colisiones bastante interesante y"
-" defensas contra Sybil, mientras que Tarzan hace uso de la escasez de "
-"direcciones IP para obtener lo mismo. Las dos principales diferencias "
-"entre estos dos sistemas e I2P tienen que ver con el modelo de amenazas de I2p y  su diseño de "
-"outproxies (al contrario que el anonimato proporcionado  para ambos, el "
-"que envía y el que recibe) El código está disponible para ambos sistemas,"
-" pero no sabemos de su uso fuera de ambientes académicos."
-
-#: i2p2www/pages/site/comparison/other-networks.html:153
-msgid ""
-"\n"
-"Mixminion and Mixmaster are networks to support anonymous email against a"
-" very\n"
-"powerful adversary.\n"
-"High-latency messaging applications running on top of I2P\n"
-"(for example\n"
-"Syndie or\n"
-"I2PBote)\n"
-"may perhaps prove adequate to meet the threat\n"
-"model of those adversaries, while running in parallel along side the "
-"needs of low latency users, to provide\n"
-"a significantly larger anonymity set.\n"
-"High-latency support within the I2P router itself may or may not be added"
-" in a distant future release.\n"
-"It is too early to say if I2P will meet the needs of users requiring "
-"extreme protection for email."
-msgstr ""
-"\n"
-"Mixminion y Mixmaster son redes para el envío anónimo de emails. "
-"Aplicaciones de envío de mensajes de baja latencia sobre I2P (por ejemplo"
-" a href=\"http://syndie.i2p2.de/\">Syndie o⏎ I2PBote) podrían ser "
-"adecuadas para ese modelo de amenazas, ya que corriendo en paralelo cubre"
-" las necesidades de la baja latencia y crea una capa grande de anonimato."
-" Soporte para alta latencia en los ruters de I2P puede que se añada en un"
-" futuro distante, o puede que no. Es demasiado pronto para decir si I2P "
-"podrá cubrir las necesidades de los usuarios con necesidades de "
-"protección extrema para sus emails."
-
-#: i2p2www/pages/site/comparison/other-networks.html:167
-msgid ""
-"As with Tor and Onion Routing, \n"
-"both Mixminion and Mixmaster take the directory based approach as well."
-msgstr ""
-"Al igual que con Tor y Onion routing, Mixminion y Mixmaster toman también"
-" la aproximación basada en directorios."
-
-#: i2p2www/pages/site/comparison/other-networks.html:177
-#, python-format
-msgid ""
-"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
-"web requests,\n"
-"and as such it has a few centralized nodes (participants in the cascade) "
-"that blend\n"
-"and mix requests from clients through the sequence of nodes (the cascade)"
-" before \n"
-"proxying out onto the web.  The scope, threat model, and security is "
-"substantially \n"
-"different from I2P, but for those who don't require significant anonymity"
-" but still\n"
-"are not satisfied with an Anonymizer-like service, JAP is worth "
-"reviewing.  One\n"
-"caution to note is that anyone under the jurisdiction of the German "
-"courts may want\n"
-"to take care, as the German Federal Bureau of Criminal Investigation "
-"(FBCI) has \n"
-"successfully mounted an \n"
-"attack \n"
-"on the network.  Even though the method of this attack was later found to"
-" be illegal \n"
-"in the German courts, the fact that the data was successfully collected "
-"is the \n"
-"concern.  Courts change their minds based upon circumstance, and this is "
-"evidence that \n"
-"if a government body or intelligence agency wanted to, they could gather "
-"the data, even \n"
-"if it may be found inadmissible in some courts later)"
-msgstr ""
-"JAP (Proxy Anónimo en Java) es una red de mezcla en cascadas para el "
-"anonimato de las solicitudes web que tiene varios nodos centrales "
-"(participantes en la cascada) que combinan y mezclan las solicitudes de "
-"los clientes a través de una secuencia de nodos (la cascada) antes de "
-"enviarlos por un proxy a la web. El alcance, modelo de amenazas y la "
-"seguridad son bastantes diferentes a las de I2P, pero para aquellos que "
-"requieran bastante anonimato pero no están satisfechos con un servicio de"
-" tipo anonimizador, puede venirles bien echarle un ojo a JAP. Un "
-"precaución que debe tener todo aquel que se encuentre bajo la "
-"jurisdicción de  los juzgados alemanes, es que el German Federal Bureau "
-"of Criminal Investigation (FBCI) ha montado un ataque con éxito sobre esta red. Incluso aunque el "
-"ataque se encontró más tarde ilegal en los juzgados alemanes, la realidad"
-" es que la información fue sustraída con éxito. Los jueces cambian sus "
-"mentes basados en las circunstancias, y esta es la evidencia de que si el"
-" gobierno quisiese la información podrían conseguirla, aunque fuese "
-"inadmisible más tarde en un juicio)"
-
-#: i2p2www/pages/site/comparison/other-networks.html:199
-#, python-format
-msgid ""
-"Both of these systems work through the same basic \n"
-"antnet routing, providing some degree of\n"
-"anonymity based on the threat model of providing plausible deniability "
-"against a simple \n"
-"non-colluding adversary.  With the antnet routing, they first either do a"
-" random walk or a \n"
-"broadcast search to find some peer with the data or identity desired, and"
-" then use a feedback\n"
-"algorithm to optimize that found path.  This works well for applications "
-"that merely want to know \n"
-"what other people around them have to offer - \"How are y'all doing\" vs."
-" \"Hey Alice, how are you\" - \n"
-"you basically get a local cluster of nodes that can share files with and "
-"maintain some degree of \n"
-"anonymity (though you don't have much control over who is in that group "
-"of peers)."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:211
-msgid ""
-"However, the algorithm does not scale well at all - if the application "
-"wants to speak with a \n"
-"particular peer it ends up doing a broadcast search or random walk "
-"(though if they are lucky enough\n"
-"for that to succeed, the antnet routing should optimize that found "
-"connection).  This means that \n"
-"while these networks can work great at small scales, they are not "
-"suitable for large networks where\n"
-"someone wants to get in touch with another specific peer.  That does not "
-"mean that there is no \n"
-"value in these systems, just that their applicability is limited to "
-"situations where their \n"
-"particular issues can be addressed."
-msgstr ""
-"Sin embargo, el algoritmo no escala bien del todo - si la aplicación "
-"quiere hablar con un par en particular termina haciendo una búsqueda "
-"broadcast o un paseo aleatorio (si son afortunados de que eso ocurra). "
-"Esto significa que mientras esas redes trabajan bien a escalas pequeñas, "
-"no son apropiadas para redes grandes donde alguien quiere ponerse en "
-"contacto con un par en particular. Esto no quiere decir que este sistema "
-"no tenga ningún valor, sólo que su aplicación está limitada a situaciones"
-" donde sus problemas pueden evitarse."
-
-#: i2p2www/pages/site/comparison/other-networks.html:222
-#, python-format
-msgid ""
-"This was a closed-source network targeted at Iranian users.\n"
-"Tor did a\n"
-"good writeup on what to look for in a circumvention tool.\n"
-"Suffice it to say that being closed source and publicly targeting a "
-"specific country are not good ideas.\n"
-"I2P is, of course, open source. However, that source, and our\n"
-"technical documentation, need much more review."
-msgstr ""
-"Esta era un red de código cerrado orientada a los usuarios iraníes. Tor "
-"hizo un buen  artículo sobre el tema. Baste decir que siendo "
-"de código cerrado y publicado para un país específico no es una buena "
-"idea. I2P, por supuesto, es de código libre. Sin embargo, el código, y "
-"nuestra documentación técnica, necesitan mucho "
-"más revisión."
-
-#: i2p2www/pages/site/comparison/other-networks.html:231
-msgid "Paid VPN Services"
-msgstr "Servicios VPN de pago"
-
-#: i2p2www/pages/site/comparison/other-networks.html:232
-#: i2p2www/pages/site/comparison/other-networks.html:238
-#, python-format
-msgid ""
-"You may contribute an analysis by entering a\n"
-"new ticket on %(trac)s."
-msgstr ""
-"Puede contribuir con análisis creando un nuevo ticket en %(trac)s."
-
-#: i2p2www/pages/site/comparison/other-networks.html:237
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
-msgid "Others"
-msgstr "Otros"
-
-#: i2p2www/pages/site/comparison/tor.html:2
-msgid "I2P Compared to Tor"
-msgstr "Comparación de I2P con Tor"
-
-#: i2p2www/pages/site/comparison/tor.html:8
-#, python-format
-msgid ""
-"Tor and Onion Routing are both anonymizing proxy networks, \n"
-"allowing people to tunnel out through their low latency mix \n"
-"network. The two primary differences between Tor / \n"
-"Onion-Routing and I2P are again related to differences in \n"
-"the threat model and the out-proxy design (though Tor\n"
-"supports hidden services as well).  In addition, Tor\n"
-"takes the directory-based approach - providing a \n"
-"centralized point to manage the overall 'view' of the \n"
-"network, as well as gather and report statistics, as \n"
-"opposed to I2P's distributed network \n"
-"database and peer selection."
-msgstr ""
-"Tor y el rutado Onion son ambas redes de proxies anónimas, que permiten a"
-" la gente salir a través de su red ya mezclada de baja latencia. Las dos "
-"primeras diferencias entre Tor/Onion-Routing e I2P están de nuevo "
-"relacionas con las diferencias en el modelo de amenazas y el diseño de "
-"los out-proxies ( a través de Tor soporta también servicios ocultos) "
-"Además, Tor usa un enfoque basado en  directorios - creando un punto "
-"central para manejar la 'vista' general de las redes, y además se "
-"obtienen más estadísticas, al contrario que la base"
-" de datos de la red  dsitribuida de I2P y la selección de pares."
-
-#: i2p2www/pages/site/comparison/tor.html:22
-msgid ""
-"The I2P/Tor outproxy functionality does have a few \n"
-"substantial weaknesses against certain attackers - \n"
-"once the communication leaves the mixnet, global passive\n"
-"adversaries can more easily mount traffic analysis.  In \n"
-"addition, the outproxies have access to the cleartext \n"
-"of the data transferred in both directions, and \n"
-"outproxies are prone to abuse, along with all of the \n"
-"other security issues we've come to know and love with \n"
-"normal Internet traffic."
-msgstr ""
-"El outproxy de I2P/Tor tiene varias debilidades contra cierto tipo de "
-"ataques - una vez que la comunicación deja la red Tor, adversarios "
-"pasivos puede hacer más fácilmente ataques de análisis. Además los "
-"outproxies tienen acceso al texto en claro transferido en las dos "
-"direcciones, y los outproxies son propensos a abusos, y además tenemos "
-"que tener en cuenta otros ataques posibles dentro del Internet normal."
-
-#: i2p2www/pages/site/comparison/tor.html:34
-msgid ""
-"However, many people don't need to worry about those \n"
-"situations, as they are outside their threat model.  It\n"
-"is, also, outside I2P's (formal) functional scope (if people want\n"
-"to build outproxy functionality on top of an anonymous\n"
-"communication layer, they can).  In fact, some I2P users\n"
-"currently take advantage of Tor to outproxy."
-msgstr ""
-"Aún así, mucha gente no tiene por que preocuparse por estas situaciones, "
-"ya que no están dentro del modelo de amenazas. Y además esto está fuera "
-"del alcance (fromal) de I2P (si la gente desea construir un outproxy "
-"sobre la capa de comunicación anónima, pueden hacerlo). De hecho, "
-"actualmente  algunos usuarios utilizan el outproxy de Tor."
-
-#: i2p2www/pages/site/comparison/tor.html:48
-msgid "Comparison of Tor and I2P Terminology"
-msgstr "Comparación de la terminología de I2P y Tor"
-
-#: i2p2www/pages/site/comparison/tor.html:49
-msgid ""
-"While Tor and I2P are similar in many ways, much of the terminology is "
-"different."
-msgstr ""
-"Mientras que Tor e I2p tienen algunas similitudes, mucha de la "
-"terminología cambia."
-
-#: i2p2www/pages/site/comparison/tor.html:54
-msgid "Cell"
-msgstr "Celda"
-
-#: i2p2www/pages/site/comparison/tor.html:54
-#: i2p2www/pages/site/docs/protocol/i2np.html:91
-msgid "Message"
-msgstr "Mensaje"
-
-#: i2p2www/pages/site/comparison/tor.html:55
-msgid "Client"
-msgstr "Cliente"
-
-#: i2p2www/pages/site/comparison/tor.html:55
-msgid "Router or Client"
-msgstr "Ruter o Cliente"
-
-#: i2p2www/pages/site/comparison/tor.html:56
-msgid "Circuit"
-msgstr "Circuito"
-
-#: i2p2www/pages/site/comparison/tor.html:56
-msgid "Tunnel"
-msgstr "Túnel"
-
-#: i2p2www/pages/site/comparison/tor.html:57
-msgid "Directory"
-msgstr "Directorio"
-
-#: i2p2www/pages/site/comparison/tor.html:57
-msgid "NetDb"
-msgstr "NetDb, baso de datos de la red"
-
-#: i2p2www/pages/site/comparison/tor.html:58
-msgid "Directory Server"
-msgstr "Servidor de directorios"
-
-#: i2p2www/pages/site/comparison/tor.html:58
-msgid "Floodfill Router"
-msgstr "Ruter Floodfill o de relleno"
-
-#: i2p2www/pages/site/comparison/tor.html:59
-msgid "Entry Guards"
-msgstr "Control de entradas"
-
-#: i2p2www/pages/site/comparison/tor.html:59
-msgid "Fast Peers"
-msgstr "Pares rápidos"
-
-#: i2p2www/pages/site/comparison/tor.html:60
-msgid "Entry Node"
-msgstr "Nodo de entrada"
-
-#: i2p2www/pages/site/comparison/tor.html:60
-msgid "Inproxy"
-msgstr "Inproxy, proxy de entrada"
-
-#: i2p2www/pages/site/comparison/tor.html:61
-msgid "Exit Node"
-msgstr "Nodo de salida"
-
-#: i2p2www/pages/site/comparison/tor.html:61
-msgid "Outproxy"
-msgstr "Outproxy, o proxy de salida"
-
-#: i2p2www/pages/site/comparison/tor.html:62
-msgid "Hidden Service"
-msgstr "Servicio oculto"
-
-#: i2p2www/pages/site/comparison/tor.html:62
-msgid "Eepsite or Destination"
-msgstr "Eepsite o destinación"
-
-#: i2p2www/pages/site/comparison/tor.html:63
-msgid "Hidden Service Descriptor"
-msgstr "Descriptor de servicio oculto"
-
-#: i2p2www/pages/site/comparison/tor.html:63
-msgid "LeaseSet"
-msgstr "LeaseSet"
-
-#: i2p2www/pages/site/comparison/tor.html:64
-msgid "Introduction point"
-msgstr "Punto de introducción"
-
-#: i2p2www/pages/site/comparison/tor.html:64
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
-#: i2p2www/pages/site/docs/tunnels/implementation.html:140
-msgid "Inbound Gateway"
-msgstr "Salida entrante"
-
-#: i2p2www/pages/site/comparison/tor.html:65
-msgid "Node"
-msgstr "Nodo"
-
-#: i2p2www/pages/site/comparison/tor.html:65
-#: i2p2www/pages/site/comparison/tor.html:67
-#: i2p2www/pages/site/comparison/tor.html:70
-#: i2p2www/pages/site/docs/spec/configuration.html:70
-msgid "Router"
-msgstr "Ruter"
-
-#: i2p2www/pages/site/comparison/tor.html:66
-msgid "Onion Proxy"
-msgstr "Proxy Onion"
-
-#: i2p2www/pages/site/comparison/tor.html:66
-msgid "I2PTunnel Client (more or less)"
-msgstr "Cliente de I2PTunnel (más o menos)"
-
-#: i2p2www/pages/site/comparison/tor.html:67
-msgid "Relay"
-msgstr "Relay"
-
-#: i2p2www/pages/site/comparison/tor.html:68
-msgid "Rendezvous Point"
-msgstr "Punto de reunión"
-
-#: i2p2www/pages/site/comparison/tor.html:68
-msgid "somewhat like Inbound Gateway + Outbound Endpoint"
-msgstr ""
-"algo así como inbound Gateway + Outbound Endpoint, salida entrante + "
-"punto final de salida"
-
-#: i2p2www/pages/site/comparison/tor.html:69
-msgid "Router Descriptor"
-msgstr "Descriptor del ruter"
-
-#: i2p2www/pages/site/comparison/tor.html:69
-msgid "RouterInfo"
-msgstr "Información del ruter"
-
-#: i2p2www/pages/site/comparison/tor.html:70
-msgid "Server"
-msgstr "Servidor"
-
-#: i2p2www/pages/site/comparison/tor.html:73
-msgid "Benefits of Tor over I2P"
-msgstr "Beneficios de Tor sobre I2p"
-
-#: i2p2www/pages/site/comparison/tor.html:76
-msgid ""
-"Much bigger user base; much more visibility in the academic and hacker "
-"communities; benefits from\n"
-"formal studies of anonymity, resistance, and performance;\n"
-"has a non-anonymous, visible, university-based leader"
-msgstr ""
-"El número de usuarios es mucho mayor; mucho más visible en entorno "
-"académicos y comunidades de hackers; beneficios de tener estudios "
-"formales sobre el anonimato, resistencia y rendimiento; tienen un líder "
-"universitario no anónimo, de cara a público"
-
-#: i2p2www/pages/site/comparison/tor.html:82
-msgid "Has already solved some scaling issues I2P has yet to address"
-msgstr "Ha resuelto ya algunos problemas de escalado que I2P aún debe arreglar. "
-
-#: i2p2www/pages/site/comparison/tor.html:83
-msgid "Has significant funding"
-msgstr "Tiene muchos fondos"
-
-#: i2p2www/pages/site/comparison/tor.html:84
-msgid "Has more developers, including several that are funded"
-msgstr "Tiene más desarrolladores, incluso algunos con fondos"
-
-#: i2p2www/pages/site/comparison/tor.html:86
-msgid ""
-"More resistant to state-level blocking due to TLS transport layer and "
-"bridges\n"
-"(I2P has proposals for \"full restricted routes\" but these are not yet "
-"implemented)"
-msgstr ""
-"Tiene un bloqueo de nivel de estado más resistente debido la capa de "
-"transporte TLS y a los puentes (I2P tienen propuestas de \"rutas "
-"completamente restringidas\" pero estas aún no están implementadas)"
-
-#: i2p2www/pages/site/comparison/tor.html:91
-msgid "Big enough that it has had to adapt to blocking and DOS attempts"
-msgstr "Es tan grande que incluso se ha adaptado para bloquear los intentos de DOS"
-
-#: i2p2www/pages/site/comparison/tor.html:92
-msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
-msgstr ""
-"Diseñado para optimizar el tráfico de salida, con un gran número de nodos"
-" de salida"
-
-#: i2p2www/pages/site/comparison/tor.html:94
-msgid ""
-"Better documentation, has formal papers and specifications,\n"
-"better website, many more translations"
-msgstr ""
-"Mejor documentación, tiene estudios formales y especificaciones, una web "
-"mejor, y muchas traducciones"
-
-#: i2p2www/pages/site/comparison/tor.html:99
-msgid "More efficient with memory usage"
-msgstr "Más eficiente con el uso de la memoria"
-
-#: i2p2www/pages/site/comparison/tor.html:100
-msgid "Tor client nodes have very low bandwidth overhead"
-msgstr "Los nodos cliente de Tor tienen muy poco gasto de ancho de nada"
-
-#: i2p2www/pages/site/comparison/tor.html:102
-msgid ""
-"Centralized control reduces the complexity at each\n"
-"node and can efficiently address Sybil attacks"
-msgstr ""
-"El control centralizado reduce la complejidad de cada nodo y puede evitar"
-" ataques Sybil fácilmente"
-
-#: i2p2www/pages/site/comparison/tor.html:108
-msgid ""
-"A core of high capacity nodes provides higher\n"
-"throughput and lower latency"
-msgstr ""
-"Un núcleo de nodos de gran capacidad proporciona una mayor rendimiento y "
-"menor latencia"
-
-#: i2p2www/pages/site/comparison/tor.html:113
-msgid "C, not Java (ewww)"
-msgstr "C, no java (ey!)"
-
-#: i2p2www/pages/site/comparison/tor.html:116
-msgid "Benefits of I2P over Tor"
-msgstr "Beneficios de I2P sobre Tor"
-
-#: i2p2www/pages/site/comparison/tor.html:118
-msgid ""
-"Designed and optimized for hidden services, which are much faster than in"
-" Tor"
-msgstr ""
-"Diseñado para optimizar los servicios ocultos, que son mucho más rápidos "
-"que los de Tor"
-
-#: i2p2www/pages/site/comparison/tor.html:119
-msgid "Fully distributed and self organizing"
-msgstr "Totalmente distribuido y auto organizado"
-
-#: i2p2www/pages/site/comparison/tor.html:121
-msgid ""
-"Peers are selected by continuously profiling and ranking performance,\n"
-"rather than trusting claimed capacity"
-msgstr ""
-"Los pares son seleccionados continuamente según el rendimiento y "
-"categoría, en vez de confiar en la capacidad indicada"
-
-#: i2p2www/pages/site/comparison/tor.html:127
-msgid ""
-"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
-"rather than hardcoded"
-msgstr ""
-"Los pares Floodfill (\"servidores de directorios\") cambian, en vez de "
-"estar siempre fijos."
-
-#: i2p2www/pages/site/comparison/tor.html:132
-msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
-msgstr "Tan pequeña que no ha sido bloqueada o Dosed."
-
-#: i2p2www/pages/site/comparison/tor.html:133
-msgid "Peer-to-peer friendly"
-msgstr "Amigable con las aplicaciones p2p"
-
-#: i2p2www/pages/site/comparison/tor.html:134
-msgid "Packet switched instead of circuit switched"
-msgstr "Conmutado por paquete en vez de conmutado por circuito"
-
-#: i2p2www/pages/site/comparison/tor.html:137
-msgid ""
-"implicit transparent load balancing of messages \n"
-"across multiple peers, rather than a single path"
-msgstr ""
-"Implica control de carga transparente de los mensajes a través de "
-"múltiples pares, en vez de por un sólo camino."
-
-#: i2p2www/pages/site/comparison/tor.html:143
-msgid ""
-"resilience vs. failures by running multiple \n"
-"tunnels in parallel, plus rotating tunnels"
-msgstr ""
-"Resistencia contra fallos ya que usa varios túneles en paralelo, además "
-"de rotar los túneles"
-
-#: i2p2www/pages/site/comparison/tor.html:149
-msgid ""
-"scale each client's connections at O(1) instead \n"
-"of O(N) (Alice has e.g. 2 inbound tunnels that are \n"
-"used by all of the peers Alice is talking with, \n"
-"rather than a circuit for each)"
-msgstr ""
-"el número de conexiones en i2p vienen dado por O(1) en vez de O(N) (por "
-"ejemplo, Alice tiene 2 túneles de entrada que son usados por todos los "
-"pares con lo que habla Alice, en vez de un circuito por cada par)"
-
-#: i2p2www/pages/site/comparison/tor.html:159
-msgid ""
-"Unidirectional tunnels instead of bidirectional\n"
-"circuits, doubling the number of nodes a peer has to\n"
-"compromise to get the same information."
-msgstr ""
-"Túneles unidireccionales en vez de circuitos bidireccionales, usando el "
-"doble de nodos un par se compromete más par obtener la misma información."
-
-#: i2p2www/pages/site/comparison/tor.html:166
-msgid ""
-"Protection against detecting client activity, even\n"
-"when an attacker is participating in the tunnel, as\n"
-"tunnels are used for more than simply passing end \n"
-"to end messages (e.g. netDb, tunnel management, \n"
-"tunnel testing)"
-msgstr ""
-"Protección contra la detección de la actividad de un cliente, incluso "
-"cuando un atacante participa en el túnel, ya que los túneles no son sólo "
-"usados para pasar el mensaje de punto a punto (por ejemplo, netDB, "
-"administración de túneles, pruebas en los túneles)"
-
-#: i2p2www/pages/site/comparison/tor.html:175
-msgid ""
-"Tunnels in I2P are short lived, decreasing the number\n"
-"of samples that an attacker can use to mount an \n"
-"active attack with, unlike circuits in Tor, which are\n"
-"typically long lived."
-msgstr ""
-"Los túneles de I2P tienen una vida corta, reduciendo el número de "
-"muestras que un atacante puede usar para lograr un ataque activo, al "
-"contrario que con los circuitos en Tor, que son típicamente de larga "
-"duración."
-
-#: i2p2www/pages/site/comparison/tor.html:183
-msgid ""
-"I2P APIs are designed specifically for anonymity and\n"
-"security, while SOCKS is designed for functionality."
-msgstr ""
-"Los APIs de I2P están específicamente diseñados para el anonimato y la "
-"seguridad, mientras que SOCKS está diseñado para su funcionalidad."
-
-#: i2p2www/pages/site/comparison/tor.html:188
-msgid "Essentially all peers participate in routing for others"
-msgstr "Básicamente todos los pares participan en el rutado de otros"
-
-#: i2p2www/pages/site/comparison/tor.html:190
-msgid ""
-"The bandwidth overhead of being a full peer is low, \n"
-"while in Tor, while client nodes don't require much\n"
-"bandwidth, they don't fully participate in the mixnet."
-msgstr ""
-"El uso de ancho de banda de cualquier par completo es bajo, mientras que "
-"en Tor, aunque un nodo cliente no necesita mucho ancho de banda, "
-"realmente no participan completamente en la red."
-
-#: i2p2www/pages/site/comparison/tor.html:196
-msgid "Integrated automatic update mechanism"
-msgstr "Sistema integrado de actualizaciones automáticas"
-
-#: i2p2www/pages/site/comparison/tor.html:197
-msgid "Both TCP and UDP transports"
-msgstr "Ambos tipos de transporte, TCP y UDP"
-
-#: i2p2www/pages/site/comparison/tor.html:198
-msgid "Java, not C (ewww)"
-msgstr "Java, en vez de C (ewww)"
-
-#: i2p2www/pages/site/comparison/tor.html:201
-msgid "Other potential benefits of I2P but not yet implemented"
-msgstr "Otros beneficios potencial de I2P aún no implementados"
-
-#: i2p2www/pages/site/comparison/tor.html:202
-msgid "...and may never be implemented, so don't count on them!"
-msgstr ""
-"...y puede ser que nunca lleguen a ser implementados, ¡osea que no cuente"
-" con ellos!"
-
-#: i2p2www/pages/site/comparison/tor.html:205
-msgid ""
-"Defense vs. message count analysis by garlic wrapping \n"
-"multiple messages"
-msgstr ""
-"Defensa contra el análisis de conteo de mensajes envolviendo múltiples "
-"mensajes dentro de la red garlic"
-
-#: i2p2www/pages/site/comparison/tor.html:211
-msgid ""
-"Defense vs. long term intersection by adding delays \n"
-"at various hops (where the delays are not discernible\n"
-"by other hops)"
-msgstr ""
-"Defensa contra la intersección a largo plazo añadiendo demoras en varios "
-"saltos (donde las demoras no son perceptibles por los oros saltos)"
-
-#: i2p2www/pages/site/comparison/tor.html:218
-msgid ""
-"Various mixing strategies at the tunnel level (e.g.\n"
-"create a tunnel that will handle 500 messages / minute,\n"
-"where the endpoint will inject dummy messages if there\n"
-"are insufficient messages, etc)"
-msgstr ""
-"Varias estrategias de mezclado el nivel del túnel (por ejemplo, creando "
-"túneles que  manejaran 500 mensajes al minuto, donde el punto final "
-"inyectará mensajes de relleno si no hubiese suficientes mensajes, etc)"
-
 #: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:25
 msgid "Index to Technical Documentation"
-msgstr ""
+msgstr "Índice de la Documentación técnica"
 
 #: i2p2www/pages/site/docs/index.html:3 i2p2www/pages/site/docs/ports.html:3
 #: i2p2www/pages/site/docs/spec/datagrams.html:3
-#: i2p2www/pages/site/docs/spec/geoip.html:3
-#: i2p2www/pages/site/docs/spec/updates.html:3
-#: i2p2www/pages/site/docs/transport/ssu.html:3
-#: i2p2www/pages/site/get-involved/develop/applications.html:3
 msgid "May 2013"
 msgstr "Mayo de 2013"
 
@@ -7446,7 +39,7 @@ msgstr "Cómo funciona I2P"
 
 #: i2p2www/pages/site/docs/index.html:8
 msgid "Following is an index to the technical documentation for I2P."
-msgstr ""
+msgstr "A continuación hay in índice de la documentación técnica de I2P."
 
 #: i2p2www/pages/site/docs/index.html:12
 msgid ""
@@ -7456,6 +49,10 @@ msgid ""
 "The interface between applications and the router is the I2CP (I2P "
 "Control Protocol) API."
 msgstr ""
+"Este índice está ordenado desde la capa más alta a la más baja. Las capas"
+" más altas son para las aplicaciones \"clientes\"; Las capas menores son "
+"las que están dentro del propio ruter. El interfaz entre las aplicaciones"
+" y el ruter es el API I2CP (Protocolo de Control de I2P)."
 
 #: i2p2www/pages/site/docs/index.html:19
 #, python-format
@@ -7463,9 +60,12 @@ msgid ""
 "The I2P Project is committed to maintaining accurate, current "
 "documentation.\n"
 "If you find any inaccuracies in the documents linked below, please\n"
-"enter a ticket identifying the "
-"problem."
+"enter a ticket identifying the problem."
 msgstr ""
+"El proyecto I2P está comprometido a mantener una documentación precisas y"
+" actual. Si encuentra alguna inexactitud en los documentos enlazados más "
+"abajo, por favor cree un ticket identificando el "
+"problema."
 
 #: i2p2www/pages/site/docs/index.html:27 i2p2www/pages/site/docs/naming.html:7
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:12
@@ -7481,7 +81,6 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/updates.html:6
 #: i2p2www/pages/site/docs/tunnels/implementation.html:67
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:6
-#: i2p2www/pages/site/misc/jbigi.html:6
 msgid "Overview"
 msgstr "Vista general"
 
@@ -7491,23 +90,21 @@ msgstr "Introducción técnica"
 
 #: i2p2www/pages/site/docs/index.html:30
 msgid "A Less-Technical Introduction"
-msgstr ""
+msgstr "Una introducción no tan técnica"
 
 #: i2p2www/pages/site/docs/index.html:31
 msgid "Threat model and analysis"
-msgstr ""
+msgstr "Modelo de amenazas y análisis"
 
 #: i2p2www/pages/site/docs/index.html:32
 msgid "Comparisons to other anonymous networks"
-msgstr ""
+msgstr "Comparación con otras redes anónimas."
 
 #: i2p2www/pages/site/docs/index.html:33
 msgid "Protocol stack chart"
-msgstr ""
+msgstr "Gráfica de la pila del protocolo"
 
 #: i2p2www/pages/site/docs/index.html:34
-#: i2p2www/pages/site/research/papers.html:2
-#: i2p2www/pages/site/research/papers.html:4
 msgid "Papers on I2P"
 msgstr "Estudios sobre I2P"
 
@@ -7517,26 +114,28 @@ msgid ""
 "Invisible Internet Project (I2P) Project Overview"
 " August 28, 2003 (pdf)"
 msgstr ""
+"Vista general del Proyecto para un Internet Invisible"
+" (I2P) 28 de Agosto del 2003 (pdf)"
 
 #: i2p2www/pages/site/docs/index.html:38
 msgid "Application-Layer Topics"
-msgstr ""
+msgstr "Temas de la capa de aplicaciones"
 
 #: i2p2www/pages/site/docs/index.html:41 i2p2www/pages/site/docs/naming.html:2
 msgid "Naming and Addressbook"
-msgstr ""
+msgstr "Nombres de dominios y libreta de direcciones"
 
 #: i2p2www/pages/site/docs/index.html:42
 msgid "Plugins Overview"
-msgstr ""
+msgstr "Resumen de pluguins"
 
 #: i2p2www/pages/site/docs/index.html:43
 msgid "Plugin Specification"
-msgstr ""
+msgstr "Especificaciones de los pluguins"
 
 #: i2p2www/pages/site/docs/index.html:44
 msgid "Router software updates"
-msgstr ""
+msgstr "Actualizaciones de software del ruter"
 
 #: i2p2www/pages/site/docs/index.html:45
 #: i2p2www/pages/site/docs/applications/bittorrent.html:2
@@ -7545,29 +144,31 @@ msgstr "Bittorrent sobre I2P"
 
 #: i2p2www/pages/site/docs/index.html:46
 msgid "I2PControl Plugin API"
-msgstr ""
+msgstr "API del pluguin I2PControl"
 
 #: i2p2www/pages/site/docs/index.html:47
 msgid "hostsdb.blockfile Format"
-msgstr ""
+msgstr "Formato de hostsdb.blockfile "
 
 #: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:185
 msgid "Configuration File Format"
-msgstr ""
+msgstr "Formato del archivo de configuración"
 
 #: i2p2www/pages/site/docs/index.html:51
 msgid "Application Layer API and Protocols"
-msgstr ""
+msgstr "Protocolos y API de la capa de aplicación"
 
 #: i2p2www/pages/site/docs/index.html:52
 msgid ""
 "High-level, easy-to-use APIs for applications written in any language to "
 "send and receive data."
 msgstr ""
+"API de alto nivel y fácil de usar para enviar y recibir datos para "
+"aplicaciones escritas en cualquier lenguaje."
 
 #: i2p2www/pages/site/docs/index.html:54
 msgid "Application Development Overview and Guide"
-msgstr ""
+msgstr "Resumen y guía del desarrollo de aplicaciones"
 
 #: i2p2www/pages/site/docs/index.html:72
 msgid "SAM Protocol"
@@ -7587,30 +188,37 @@ msgstr "Protocolo BOB"
 
 #: i2p2www/pages/site/docs/index.html:81
 msgid "End-to-End Transport API and Protocols"
-msgstr ""
+msgstr "Protocolos y API del transporte de fin a fin."
 
 #: i2p2www/pages/site/docs/index.html:82
 msgid ""
 "The end-to-end protocols used by clients for reliable and unreliable "
 "communication."
 msgstr ""
+"Los protocolos fin a fin usados por los clientes para la comunicación "
+"segura y no segura."
 
 #: i2p2www/pages/site/docs/index.html:84
 #: i2p2www/pages/site/docs/api/streaming.html:2
 msgid "Streaming Library"
-msgstr ""
+msgstr "Librería de srteaming"
 
 #: i2p2www/pages/site/docs/index.html:86
 msgid "Streaming Javadoc"
-msgstr ""
+msgstr "Javadoc del streaming"
+
+#: i2p2www/pages/site/docs/index.html:88
+#: i2p2www/pages/site/docs/api/datagrams.html:2
+msgid "Datagrams"
+msgstr "Datagramas"
 
 #: i2p2www/pages/site/docs/index.html:90
 msgid "Datagram Javadoc"
-msgstr ""
+msgstr "Javadoc del datagrama"
 
 #: i2p2www/pages/site/docs/index.html:93
 msgid "Client-to-Router Interface API and Protocol"
-msgstr ""
+msgstr "Protocolo y API del interfaz cliente-a-ruter"
 
 #: i2p2www/pages/site/docs/index.html:94
 msgid ""
@@ -7618,10 +226,13 @@ msgid ""
 "traffic to a router.\n"
 "Traditionally used only by Java applications and higher-level APIs."
 msgstr ""
+"El API de menor nivel usado por los clientes (aplicaciones) para enviar y"
+" recibir tráfico a un ruter. Tradicionalmente usado sólo por aplicaciones"
+" en Java y APIs de mayor nivel."
 
 #: i2p2www/pages/site/docs/index.html:99
 msgid "I2CP - I2P Control Protocol / API overview"
-msgstr ""
+msgstr "I2CP - Protocolo de control de I2P / Resumen del API"
 
 #: i2p2www/pages/site/docs/index.html:101
 msgid "I2CP Specification"
@@ -7629,34 +240,34 @@ msgstr "Especificación I2CP"
 
 #: i2p2www/pages/site/docs/index.html:103
 msgid "I2CP API Javadoc"
-msgstr ""
+msgstr "Javadoc del API de I2CP"
 
 #: i2p2www/pages/site/docs/index.html:105
 #: i2p2www/pages/site/docs/index.html:134
 msgid "Common data structures specification"
-msgstr ""
+msgstr "Especificaciones de las estructuras de datos más usadas."
 
 #: i2p2www/pages/site/docs/index.html:107
 #: i2p2www/pages/site/docs/index.html:136
 msgid "Data Structures Javadoc"
-msgstr ""
+msgstr "Javadoc de las estructuras de datos"
 
 #: i2p2www/pages/site/docs/index.html:110
 msgid "End-to-End Encryption"
-msgstr ""
+msgstr "Cifrado de fin a fin"
 
 #: i2p2www/pages/site/docs/index.html:111
 msgid "How client messages are end-to-end encrypted by the router."
-msgstr ""
+msgstr "Cómo son cifrados por el ruter los mensajes de fin a fin."
 
 #: i2p2www/pages/site/docs/index.html:113
 msgid "ElGamal/AES+SessionTag encryption"
-msgstr ""
+msgstr "Cifrado ElGamal/AES+SessionTag"
 
 #: i2p2www/pages/site/docs/index.html:114
 #: i2p2www/pages/site/docs/index.html:147
 msgid "ElGamal and AES cryptography details"
-msgstr ""
+msgstr "Detalles criptográficos de ElGamal y AES"
 
 #: i2p2www/pages/site/docs/index.html:117
 #: i2p2www/pages/site/docs/how/tech-intro.html:15
@@ -7669,32 +280,38 @@ msgid ""
 "Distributed storage and retrieval of information about routers and "
 "clients."
 msgstr ""
+"Almacenamiento distribuido y obtención de información sobre los ruters y "
+"los clientes. "
 
 #: i2p2www/pages/site/docs/index.html:120
 msgid "Network database overview, details, and threat analysis"
 msgstr ""
+"Vista general, detalles y análisis de amenazas de la base de datos de la "
+"red"
 
 #: i2p2www/pages/site/docs/index.html:121
 msgid "Cryptographic hashes"
-msgstr ""
+msgstr "Hashes de cifrados"
 
 #: i2p2www/pages/site/docs/index.html:122
 msgid "Cryptographic signatures"
-msgstr ""
+msgstr "Firmas de cifrados"
 
 #: i2p2www/pages/site/docs/index.html:125
 msgid "Router Message Protocol"
-msgstr ""
+msgstr "Protocolo de los mensajes del ruter"
 
 #: i2p2www/pages/site/docs/index.html:126
 msgid ""
 "I2P is a message-oriented router. The messages sent between routers are "
 "defined by the I2NP protocol."
 msgstr ""
+"I2P es un ruter orientado a mensajes. Los mensajes que se envían entre "
+"los ruters son definidos por el protocolo I2NP."
 
 #: i2p2www/pages/site/docs/index.html:128
 msgid "I2NP - I2P Network Protocol Overview"
-msgstr ""
+msgstr "I2NP - Vista general del protocolo de red de I2P"
 
 #: i2p2www/pages/site/docs/index.html:130
 msgid "I2NP Specification"
@@ -7702,29 +319,37 @@ msgstr "Especificación I2NP"
 
 #: i2p2www/pages/site/docs/index.html:132
 msgid "I2NP Javadoc"
-msgstr ""
+msgstr "Javadoc de I2NP"
+
+#: i2p2www/pages/site/docs/index.html:139
+#: i2p2www/pages/site/docs/how/tech-intro.html:14
+#: i2p2www/pages/site/docs/how/tech-intro.html:228
+msgid "Tunnels"
+msgstr "Túneles"
 
 #: i2p2www/pages/site/docs/index.html:140
 msgid ""
 "Selecting peers, requesting tunnels through those peers, and encrypting "
 "and routing messages through these tunnels."
 msgstr ""
+"Seleccionando pares, solicitando túneles a través de esos pares, y "
+"cifrando y enrutando mensajes a través de esos túneles."
 
 #: i2p2www/pages/site/docs/index.html:142
 msgid "Peer profiling and selection"
-msgstr ""
+msgstr "Perfiles y selección de pares"
 
 #: i2p2www/pages/site/docs/index.html:143
 msgid "Tunnel routing overview"
-msgstr ""
+msgstr "Vista general del túnel de enrutado"
 
 #: i2p2www/pages/site/docs/index.html:144
 msgid "Garlic routing and \"garlic\" terminology"
-msgstr ""
+msgstr "Rutado Garlic y terminología \"garlic\""
 
 #: i2p2www/pages/site/docs/index.html:145
 msgid "Tunnel building and encryption"
-msgstr ""
+msgstr "Cifrado y construcción de los túneles"
 
 #: i2p2www/pages/site/docs/index.html:146
 msgid "ElGamal/AES"
@@ -7732,29 +357,29 @@ msgstr "ElGamal/AES"
 
 #: i2p2www/pages/site/docs/index.html:146
 msgid "for build request encryption"
-msgstr ""
+msgstr "para cifrado de solicitudes de construcción (`build`, de túneles)"
 
 #: i2p2www/pages/site/docs/index.html:148
 msgid "Tunnel building specification"
-msgstr ""
+msgstr "Especificaciones para la creación de túneles"
 
 #: i2p2www/pages/site/docs/index.html:149
 msgid "Low-level tunnel message specification"
-msgstr ""
+msgstr "Especificaciones de los mensajes de túnel de bajo nivel"
 
 #: i2p2www/pages/site/docs/index.html:150
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:2
 msgid "Unidirectional Tunnels"
-msgstr ""
+msgstr "Túneles unidireccionales"
 
 #: i2p2www/pages/site/docs/index.html:151
 #: i2p2www/pages/site/docs/how/peer-selection.html:299
 msgid "Peer Profiling and Selection in the I2P Anonymous Network"
-msgstr ""
+msgstr "Perfiles y selección de pares en la red anónima I2P"
 
 #: i2p2www/pages/site/docs/index.html:152
 msgid "2009 paper (pdf), not current but still generally accurate"
-msgstr ""
+msgstr "Estudio del 2009 (pdf), no es muy actual pero es bastante exacto"
 
 #: i2p2www/pages/site/docs/index.html:155
 msgid "Transport Layer"
@@ -7763,14 +388,20 @@ msgstr "Capa de transporte"
 #: i2p2www/pages/site/docs/index.html:156
 msgid "The protocols for direct (point-to-point) router to router communication."
 msgstr ""
+"Los protocolos para las comunicaciones directas (punto a punto) de ruter "
+"a ruter."
+
+#: i2p2www/pages/site/docs/index.html:158
+msgid "Transport layer overview"
+msgstr "Visión general de la capa de transporte"
 
 #: i2p2www/pages/site/docs/index.html:160
 msgid "TCP-based transport overview and specification"
-msgstr ""
+msgstr "Especificaciones y vista general de los transportes basados en TCP"
 
 #: i2p2www/pages/site/docs/index.html:162
 msgid "UDP-based transport overview"
-msgstr ""
+msgstr "Vista general de los transportes basados en UDP"
 
 #: i2p2www/pages/site/docs/index.html:164
 msgid "SSU specification"
@@ -7778,62 +409,63 @@ msgstr "Especificación SSU"
 
 #: i2p2www/pages/site/docs/index.html:166
 msgid "NTCP transport encryption"
-msgstr ""
+msgstr "Cifrado del transporte de NTCP"
 
 #: i2p2www/pages/site/docs/index.html:168
 msgid "SSU transport encryption"
-msgstr ""
+msgstr "Cifrado del transporte de SSU"
 
 #: i2p2www/pages/site/docs/index.html:170
 msgid "Transport Javadoc"
-msgstr ""
+msgstr "Jacadoc del transporte"
 
 #: i2p2www/pages/site/docs/index.html:172
 msgid "NTCP Javadoc"
-msgstr ""
+msgstr "Javadoc de NTCP"
 
 #: i2p2www/pages/site/docs/index.html:174
 msgid "SSU Javadoc"
-msgstr ""
+msgstr "Jacadoc de SSU"
 
 #: i2p2www/pages/site/docs/index.html:177
 msgid "Other Router Topics"
-msgstr ""
+msgstr "Otros temas sobre el Ruter"
 
 #: i2p2www/pages/site/docs/index.html:179
 msgid "Native BigInteger Library"
-msgstr ""
+msgstr "Librería BigInteger nativa"
 
 #: i2p2www/pages/site/docs/index.html:181
 msgid "Time synchronization and NTP"
-msgstr ""
+msgstr "NTP y sincronización de la fecha"
+
+#: i2p2www/pages/site/docs/index.html:183
+msgid "Performance"
+msgstr "Rendimiento"
 
 #: i2p2www/pages/site/docs/index.html:190
 msgid "Developer's Guides and Resources"
-msgstr ""
+msgstr "Recursos y guías para desarrolladores"
 
 #: i2p2www/pages/site/docs/index.html:192
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
 msgid "New Developer's Guide"
 msgstr "Guía para nuevos desarrolladores"
 
 #: i2p2www/pages/site/docs/index.html:194
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
 msgid "New Translator's Guide"
-msgstr ""
+msgstr "La nueva guía de los traductores"
 
 #: i2p2www/pages/site/docs/index.html:196
-#: i2p2www/pages/site/get-involved/guides/monotone.html:4
 msgid "Monotone Guide"
 msgstr "Guía de Monotone"
 
 #: i2p2www/pages/site/docs/index.html:198
 msgid "Developer Guidelines"
-msgstr ""
+msgstr "Directrizes para los desarrolladores"
 
 #: i2p2www/pages/site/docs/index.html:200
 msgid "Javadocs on the standard internet:"
-msgstr ""
+msgstr "Jacadocs en el Internet normal:"
 
 #: i2p2www/pages/site/docs/index.html:201
 #: i2p2www/pages/site/docs/index.html:205
@@ -7849,73 +481,86 @@ msgid ""
 "Note: always verify that javadocs are current by checking the release "
 "number."
 msgstr ""
+"Nota: verifique siempre que los Javadocs son actuales comprobando los "
+"números de versiones."
 
 #: i2p2www/pages/site/docs/index.html:204
 msgid "Javadocs inside I2P:"
-msgstr ""
+msgstr "Javadocs en I2P:"
 
 #: i2p2www/pages/site/docs/index.html:213
 msgid "Ports used by I2P"
-msgstr ""
+msgstr "Ports usados por I2P"
 
 #: i2p2www/pages/site/docs/index.html:215
 msgid "Automatic updates to development builds inside I2P"
-msgstr ""
+msgstr "Actualizaciones automáticas y compilaciones de desarrollo dentro de I2P"
 
 #: i2p2www/pages/site/docs/index.html:217
 msgid "Updating the wrapper manually"
-msgstr ""
+msgstr "Actualizando el wrapper manualmente"
 
 #: i2p2www/pages/site/docs/index.html:219
 msgid "User forum"
-msgstr ""
+msgstr "Foro para usuarios"
 
 #: i2p2www/pages/site/docs/index.html:221
 msgid "Developer forum inside I2P"
-msgstr ""
+msgstr "Foro para desarrolladores en I2P"
+
+#: i2p2www/pages/site/docs/index.html:223
+msgid "Bug tracker"
+msgstr "Bug tracker"
 
 #: i2p2www/pages/site/docs/index.html:225
 msgid "Viewmtn inside I2P"
-msgstr ""
+msgstr "Viewmtn en I2P"
 
 #: i2p2www/pages/site/docs/index.html:227
 msgid "I2P Source exported to GitHub"
-msgstr ""
+msgstr "El código de I2P exportado a GitHub"
 
 #: i2p2www/pages/site/docs/index.html:229
 msgid "I2P Source Git Repo inside I2P"
-msgstr ""
+msgstr "Repositorio Git del código de I2P en I2P"
 
 #: i2p2www/pages/site/docs/index.html:231
 msgid "Source translation at Transifex"
-msgstr ""
+msgstr "Fuentes para traducir en Transifex"
 
 #: i2p2www/pages/site/docs/index.html:233
 msgid "Roadmap wiki"
-msgstr ""
+msgstr "Wiki con el plan de trabajo"
 
 #: i2p2www/pages/site/docs/index.html:235
 msgid "Old roadmap"
-msgstr ""
+msgstr "Plan de trabajo antiguo"
 
 #: i2p2www/pages/site/docs/index.html:235
 #: i2p2www/pages/site/docs/index.html:237
 msgid "not current"
-msgstr ""
+msgstr "no actual"
 
 #: i2p2www/pages/site/docs/index.html:237
-#: i2p2www/pages/site/get-involved/todo.html:2
 msgid "To Do List"
 msgstr "Por hacer"
 
 #: i2p2www/pages/site/docs/naming.html:3
+#: i2p2www/pages/site/docs/api/streaming.html:3
 #: i2p2www/pages/site/docs/how/cryptography.html:3
-msgid "March 2012"
-msgstr "Marzo de 2012"
+#: i2p2www/pages/site/docs/protocol/i2cp.html:3
+#: i2p2www/pages/site/docs/spec/common-structures.html:3
+#: i2p2www/pages/site/docs/spec/geoip.html:3
+#: i2p2www/pages/site/docs/spec/streaming.html:3
+#: i2p2www/pages/site/docs/transport/index.html:3
+#: i2p2www/pages/site/docs/transport/ntcp.html:3
+#: i2p2www/pages/site/docs/transport/ssu.html:3
+msgid "December 2013"
+msgstr "Diciembre de 2013"
 
 #: i2p2www/pages/site/docs/naming.html:6
 msgid "Naming in I2P"
-msgstr ""
+msgstr "Dominios en I2P"
 
 #: i2p2www/pages/site/docs/naming.html:9
 msgid ""
@@ -7925,6 +570,14 @@ msgid ""
 "I2P also supports Base32 hostnames similar to "
 "Tor's .onion addresses."
 msgstr ""
+"I2P viene con una librería genérica de asignación de nombres y una \n"
+"implementación base diseñada para entregar un mapeado desde nombre local"
+" \n"
+"a destino, además de una aplicación add-on llamada libreta de direcciones \n"
+"(`adressbook`). I2P también soporta nombres de "
+"servidor Base32 \n"
+"similares a las direcciones .onion de Tor."
 
 #: i2p2www/pages/site/docs/naming.html:16
 msgid ""
@@ -7949,6 +602,27 @@ msgid ""
 "emulating\n"
 "traditional DNS."
 msgstr ""
+"La libreta de direcciones es un sistema de nombres asegurado mediante \n"
+"web-of-trust, distribuido, y legible por humanos, que tan solo sacrifica "
+"el \n"
+"que los nombres sean globalmente únicos, obligando a que sólo lo sean\n"
+"localmente. Mientras todos los mensajes en I2P son criptográficamente \n"
+"direccionados por su destino, diferentes personas puede tener diferentes"
+" \n"
+"entradas \"Alice\" en sus libros de direcciones locales que se refieran a"
+" \n"
+"diferentes destinos. El público aún puede descubrir nuevos nombres "
+"importando \n"
+"libros de direcciones publicados, de pares (`peers`) especificados en sus"
+"\n"
+"web-of-trust, incorporando las entradas provistas por terceros, o (si "
+"algunas \n"
+"personas organizan series de libros de direcciones publicados usando un \n"
+"sistema de registro tipo `primero en venir primero en ser servido`) la "
+"gente \n"
+"puede elegir tratar estos libros de direcciones como servidores de "
+"nombres, \n"
+"emulando al tradicional DNS."
 
 #: i2p2www/pages/site/docs/naming.html:30
 #, python-format
@@ -7959,16 +633,22 @@ msgid ""
 " discussion\n"
 "page."
 msgstr ""
+"NOTA: Para encontrar las razones detrás del sistema de nombres de I2P, \n"
+"los argumentos habituales contra él y las posibles alternativas, vea la \n"
+"página de discusión sobre el sistema de "
+"nombres."
 
 #: i2p2www/pages/site/docs/naming.html:37
 msgid "Naming System Components"
-msgstr ""
+msgstr "Componentes del sistema de nombres"
 
 #: i2p2www/pages/site/docs/naming.html:39
 msgid ""
 "There is no central naming authority in I2P.\n"
 "All hostnames are local."
 msgstr ""
+"No hay una autoridad central de nombres en I2P.\n"
+"Todos los nombres de servidor están en local."
 
 #: i2p2www/pages/site/docs/naming.html:44
 msgid ""
@@ -7977,13 +657,17 @@ msgid ""
 "the I2P distribution.\n"
 "The components are:"
 msgstr ""
+"El sistema de nombres es bastante simple, y la mayoria de él está \n"
+"implementado en aplicaciones externas al router pero \n"
+"empaquetadas con la distribución I2P. Los componentes son:"
 
 #: i2p2www/pages/site/docs/naming.html:52
 msgid ""
-"The client application which does local lookups "
-"in hosts.txt\n"
-"and also takes care of the Base32 hostnames."
+"The local naming service which does lookups\n"
+"and also handles Base32 hostnames."
 msgstr ""
+"El servicio de nombres local que hace búsquedas\n"
+"y también maneja los nombres de equipos Base32."
 
 #: i2p2www/pages/site/docs/naming.html:56
 msgid ""
@@ -7991,18 +675,28 @@ msgid ""
 "lookups and points\n"
 "the user to remote jump services to assist with failed lookups."
 msgstr ""
+"El proxy HTTP que realiza consultas al router"
+" \n"
+"y dirige al usuario a servicios remotos distribuidos (`jump`)\n"
+"para asistirle con las consultas fallidas."
 
 #: i2p2www/pages/site/docs/naming.html:60
 msgid ""
 "HTTP host-add forms which allow users to "
 "add hosts to their local hosts.txt"
 msgstr ""
+"Formularios de añadido de servidores HTTP "
+"que permiten \n"
+"a los usuarios añadir servidores a su hosts.txt local."
 
 #: i2p2www/pages/site/docs/naming.html:63
 msgid ""
 "HTTP jump services which provide their own"
 " lookups and redirection."
 msgstr ""
+"Servicios distribuidos (`jump`) HTTP que "
+"proporcionan \n"
+"sus propias consultas y redirecciones."
 
 #: i2p2www/pages/site/docs/naming.html:66
 msgid ""
@@ -8010,6 +704,9 @@ msgid ""
 "external\n"
 "host lists, retrieved via HTTP, with the local list."
 msgstr ""
+"La aplicación de libreta de direcciones que"
+" \n"
+"fusiona listas externas de servidores, con la lista local."
 
 #: i2p2www/pages/site/docs/naming.html:70
 msgid ""
@@ -8017,10 +714,14 @@ msgid ""
 "front-end\n"
 "for addressbook configuration and viewing of the local host lists."
 msgstr ""
+"La aplicación SusiDNS que es un sencillo frontal"
+" web para la configuración \n"
+"de la libreta de direcciones y el visionado de las listas locales de "
+"servidores."
 
 #: i2p2www/pages/site/docs/naming.html:77
-msgid "Naming Files and Lookups"
-msgstr ""
+msgid "Naming Services"
+msgstr "Servicios de nombres"
 
 #: i2p2www/pages/site/docs/naming.html:79
 #, python-format
@@ -8035,42 +736,195 @@ msgid ""
 "One possible use of certificates is for proof of work.)"
 msgstr ""
+"Todos los destinos en I2P son claves de 516-bytes (o más largas).\n"
+"(Para ser más precisos, es una clave pública de 256-bytes más una clave "
+"de \n"
+"firmado de 128-bytes más un certificado vacío, lo que en representación \n"
+"Base64 son 516 byles.\n"
+"Los certificados no se "
+"usan ahora,\n"
+"si se usaran, las claves serían más largas.\n"
+"Un posible uso de certificados es como prueba de trabajo.)"
 
 #: i2p2www/pages/site/docs/naming.html:88
 msgid ""
 "If an application (i2ptunnel or the HTTP proxy) wishes to access\n"
 "a destination by name, the router does a very simple local lookup\n"
-"to resolve that name.\n"
-"The client application (technically, the client side of I2CP in the I2P "
-"API)\n"
-"does a linear search through three local files, in order, to\n"
-"look up host names and convert them to a 516-byte destination key:"
+"to resolve that name."
 msgstr ""
+"Si una aplicación (i2ptunnel o el proxy HTTP) quiere acceder a un\n"
+"destino mediante el nombre, el router hace una búsqueda local\n"
+"muy simple para resolver ese nombre."
+
+#: i2p2www/pages/site/docs/naming.html:94
+msgid "Hosts.txt Naming Service"
+msgstr "Servicio de nombres hosts.txt"
+
+#: i2p2www/pages/site/docs/naming.html:96
+msgid ""
+"The hosts.txt Naming Service does a simple linear search through\n"
+"text files. This naming service was the default until\n"
+"release 0.8.8 when it was replaced by the Blockfile Naming Service.\n"
+"The hosts.txt format had become too slow after the file grew to thousands"
+" of entries."
+msgstr ""
+"El servicio de nombres hosts.txt hace una búsqueda lineal simple a través"
+"\n"
+"de ficheros de texto. Este servicio de nombres fue la norma hasta la\n"
+"versión 0.8.8 cuando fue reemplazado por el servicio de nombres blockfile"
+"\n"
+"(fichero de bloques). El formato de hosts.txt ha llegado a ser demasiado\n"
+"lento después de que el fichero creciera hasta las miles de entradas."
 
 #: i2p2www/pages/site/docs/naming.html:103
+#, python-format
+msgid ""
+"It does a linear search through three local files, in order, to\n"
+"look up host names and convert them to a 516-byte destination key.\n"
+"Each file is in a simple configuration file"
+" format, with hostname=base64, one per line.\n"
+"The files are:"
+msgstr ""
+"Realiza una búsqueda lineal a través de tres ficheros locales, en orden, "
+"para\n"
+"buscar nombres de equipos y convertirlos a claves de destinos de "
+"516-bytes.\n"
+"Cada fichero está en un formato de fichero "
+"de configuración simple,\n"
+"con (nombre de equipo) hostname=base64, uno por línea.\n"
+"Los ficheros son:"
+
+#: i2p2www/pages/site/docs/naming.html:115
+msgid "Blockfile Naming Service"
+msgstr "Servicio de nombres blockfile"
+
+#: i2p2www/pages/site/docs/naming.html:117
+msgid ""
+"The Blockfile Naming Service stores multiple \"addressbooks\" in a single"
+"\n"
+"database file named hostsdb.blockfile.\n"
+"This Naming Service is the default since release 0.8.8."
+msgstr ""
+"El servicio de nombres blockfile (fichero de bloques) almacena múltiples\n"
+"\"addressbooks\" (libretas de direcciones) en un único fichero de base de"
+" datos\n"
+"llamado hostsdb.blockfile. Este servicio de nombres es el predeterminado "
+"desde la versión 0.8.8."
+
+#: i2p2www/pages/site/docs/naming.html:123
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is specified on the Blockfile page.\n"
+"It provides fast Destination lookup in a compact format. While the "
+"blockfile overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry to implement "
+"advanced addressbook features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+"Un blockfile (fichero de bloques) es simplemente un almacenamiento en-"
+"disco de múltiples mapeados (pares clave-valor) ordenados\n"
+"implementados como listas por saltos ('skiplists'). \n"
+"El formato blockfile está especificado en la página de Blockfile.\n"
+"Proporciona búsqueda rápida de destinos en un formato compacto. Aunque el"
+" tráfico de control de blockfile es sustancial,\n"
+"los destinos están almacenados en binario en lugar de en Base 64 como en "
+"el formato hosts.txt .\n"
+"Además, blockfile proporciona la posibilidad de almacenar metadatos "
+"arbitrarios\n"
+"(tales como fecha añadida, fuente, y comentarios) por cada entrada, para "
+"implementar características avanzadas de libreta de direcciones.\n"
+"El requisito para el almacenamiento blockfile es un modesto incremento "
+"sobre el tamaño del formato hosts.txt, y el blockfile proporcionará una "
+"reducción en los tiempos de búsqueda por un factor aproximado de 10x."
+
+#: i2p2www/pages/site/docs/naming.html:135
+msgid ""
+"On creation, the naming service imports entries from the three files used"
+" by the hosts.txt Naming Service.\n"
+"The blockfile mimics the previous implementation by maintaining three "
+"maps that\n"
+"are searched in-order, named privatehosts.txt, userhosts.txt, and "
+"hosts.txt.\n"
+"It also maintains a reverse-lookup map to implement rapid reverse lookups."
+msgstr ""
+"Al crearse, el servicio de nombres importa entradas desde los tres "
+"ficheros usados por el servicio de nombres hosts.txt.\n"
+"El blockfile imita la anterior implementación al mantener tres mapeados "
+"que\n"
+"se buscan en-orden, llamados privatehosts.txt, userhosts.txt, y "
+"hosts.txt.\n"
+"También mantiene un mapeado de búsqueda-inversa para implementar "
+"búsquedas inversas rápidas."
+
+#: i2p2www/pages/site/docs/naming.html:142
+msgid "Other Naming Service Facilities"
+msgstr "Otras infraestructuras de servicio de nombres"
+
+#: i2p2www/pages/site/docs/naming.html:144
+#, python-format
 msgid ""
 "The lookup is case-insensitive.\n"
 "The first match is used, and conflicts are not detected.\n"
-"There is no enforcement of naming rules in lookups."
+"There is no enforcement of naming rules in lookups.\n"
+"Lookups are cached for a few minutes.\n"
+"Base 32 resolution is described below.\n"
+"For a full description of the Naming Service API see the\n"
+"Naming Service Javadocs.\n"
+"This API was significantly expanded in release 0.8.7 to provide\n"
+"adds and removes, storage of arbitrary properties with the hostname,\n"
+"and other features."
 msgstr ""
+"La búsqueda distingue mayúsculas/minúsculas.\n"
+"Se usa la primera coincidencia, y no se detectan los conflictos.\n"
+"No se hace aplicación de las reglas de nombres en las búsquedas.\n"
+"Las búsquedas se guardan en caché durante unos pocos minutos.\n"
+"La resolución Base32 se describe debajo.\n"
+"Para una descripción completa de la API del servicio de nombres vea los\n"
+"Javadocs del servicio de nombres.\n"
+"Esta API fue expandida significativamente en la versión 0.8.7 para "
+"proporcionar\n"
+"adiciones y eliminaciones, almacenamiento de propiedades arbitrarias "
+"junto al\n"
+"el nombre del equipo, y otras características."
 
-#: i2p2www/pages/site/docs/naming.html:109
+#: i2p2www/pages/site/docs/naming.html:157
+msgid "Alternatives and Experimental Naming Services"
+msgstr "Alternativas y servicios de nombres experimentales"
+
+#: i2p2www/pages/site/docs/naming.html:159
 #, python-format
 msgid ""
-"Lookups are cached for a few minutes.\n"
-"There is an experimental facility for real-time lookups (a la DNS) over "
-"the network within the router,\n"
-"although it is not enabled by default\n"
-"(see \"EepGet\" under Alternatives on the discussion"
-" page)."
+"The naming service is specified with the configuration property "
+"i2p.naming.impl=class.\n"
+"Other implementations are possible. For example,\n"
+"there is an experimental facility for real-time lookups (a la DNS) over "
+"the network within the router.\n"
+"For more information see the alternatives on the discussion"
+" page."
 msgstr ""
+"El servicio de nombres se especifica con la propiedad de configuración "
+"i2p.naming.impl=class.\n"
+"Otras implementaciones son posibles. Por ejemplo,\n"
+"hay una infraestructura experimental para búsquedas en tiempo-real "
+"(estilo DNS) sobre la red interior al router.\n"
+"Para más información vea la página de discusión sobre "
+"alternativas."
 
-#: i2p2www/pages/site/docs/naming.html:116
-msgid "HTTP Proxy"
-msgstr "Proxy HTTP"
-
-#: i2p2www/pages/site/docs/naming.html:118
+#: i2p2www/pages/site/docs/naming.html:166
 msgid ""
 "The HTTP proxy does a lookup via the router for all hostnames ending in "
 "'.i2p'.\n"
@@ -8078,24 +932,47 @@ msgid ""
 "Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-"
 "Top Level Domain '.i2p'."
 msgstr ""
+"El proxy HTTP hace una consulta vía router para todos los nombres de "
+"servidores \n"
+"terminados en `.i2p`. De otra manera este reenvía la solicitud \n"
+"hacia un \n"
+"proxy HTTP configurado de salida (`outproxy`). Así, en la práctica, todos"
+" los nombres \n"
+"de servidores HTTP (eepsites) deben terminar en un pseudo-dominio-de-"
+"primer-nivel `.i2p`."
 
-#: i2p2www/pages/site/docs/naming.html:124
+#: i2p2www/pages/site/docs/naming.html:172
+#, python-format
+msgid ""
+"We have applied to reserve the .i2p TLD\n"
+"following the procedures specified in RFC "
+"6761."
+msgstr ""
+"Tenemos solicitada la reserva del TLD (dominio de "
+"primer nivel) .i2p\n"
+"siguiendo los procedimientos especificados en la RFC 6761."
+
+#: i2p2www/pages/site/docs/naming.html:178
 msgid ""
 "If the router fails to resolve the hostname, the HTTP proxy returns\n"
 "an error page to the user with links to several \"jump\" services.\n"
 "See below for details."
 msgstr ""
+"Si el router falla en la resolución del nombre de servidor, el proxy \n"
+"HTTP devuelve una página de error al usuario con enlaces a varios \n"
+"servicios distribuidos (`jump`). Mire debajo para más detalles."
 
-#: i2p2www/pages/site/docs/naming.html:130
+#: i2p2www/pages/site/docs/naming.html:184
 #: i2p2www/pages/site/docs/spec/configuration.html:77
 msgid "Addressbook"
 msgstr "Libreta de direcciones"
 
-#: i2p2www/pages/site/docs/naming.html:131
+#: i2p2www/pages/site/docs/naming.html:185
 msgid "Incoming Subscriptions and Merging"
-msgstr ""
+msgstr "Suscripciones entrantes y fusionado"
 
-#: i2p2www/pages/site/docs/naming.html:133
+#: i2p2www/pages/site/docs/naming.html:187
 msgid ""
 "The addressbook application periodically\n"
 "retrieves other users' hosts.txt files and merges\n"
@@ -8103,8 +980,13 @@ msgid ""
 "Naming conflicts are resolved on a first-come first-served\n"
 "basis."
 msgstr ""
+"La aplicación de la libreta de direcciones obtiene periódicamente los "
+"ficheros hosts.txt de otros usuarios y los fusiona con el fichero "
+"hosts.txt local tras varias comprobaciones. Los conflictos de nombres se "
+"resuelven en base al criterio `el primero en venir es el primero en ser "
+"servido`."
 
-#: i2p2www/pages/site/docs/naming.html:141
+#: i2p2www/pages/site/docs/naming.html:195
 msgid ""
 "Subscribing to another user's hosts.txt file involves\n"
 "giving them a certain amount of trust.\n"
@@ -8112,8 +994,13 @@ msgid ""
 "by quickly entering in their own key for a new site before\n"
 "passing the new host/key entry to you."
 msgstr ""
+"Suscribirse al fichero hosts.txt de otros usuarios implica darles un \n"
+"cierto nivel de confianza. \n"
+"No querrá que ellos, por ejemplo, 'secuestren' un sitio nuevo \n"
+"introduciendo rápidamente su propia clave para el nuevo sitio antes \n"
+"de pasarle el nuevo servidor/clave a usted."
 
-#: i2p2www/pages/site/docs/naming.html:149
+#: i2p2www/pages/site/docs/naming.html:203
 msgid ""
 "For this reason, the only subscription configured by\n"
 "default is http://www.i2p2.i2p/hosts.txt,\n"
@@ -8123,24 +1010,31 @@ msgid ""
 "local addressbook application (via subscriptions.txt or SusiDNS)."
 msgstr ""
+"Por esta razón, la única suscripción configurada por defecto \n"
+"es http://www.i2p2.i2p/hosts.txt,"
 
-#: i2p2www/pages/site/docs/naming.html:158
+#: i2p2www/pages/site/docs/naming.html:212
 msgid "Some other public addressbook subscription links:"
 msgstr ""
+"Algunos enlaces extra de suscripciones públicas a libretas de "
+"direcciones: "
 
-#: i2p2www/pages/site/docs/naming.html:165
+#: i2p2www/pages/site/docs/naming.html:219
 msgid ""
 "The operators of these services may have various policies for listing "
 "hosts.\n"
 "Presence on this list does not imply endorsement."
 msgstr ""
+"Los operadores de estos servicios pueden tener diferentes políticas para"
+" \n"
+"listar servidores. La presencia en esta lista no implica su respaldo."
 
-#: i2p2www/pages/site/docs/naming.html:170
-#: i2p2www/pages/site/docs/naming.html:182
+#: i2p2www/pages/site/docs/naming.html:224
+#: i2p2www/pages/site/docs/naming.html:236
 msgid "Naming Rules"
-msgstr ""
+msgstr "Reglas de nombres"
 
-#: i2p2www/pages/site/docs/naming.html:171
+#: i2p2www/pages/site/docs/naming.html:225
 msgid ""
 "While there are hopefully not any technical limitations within I2P on "
 "host names,\n"
@@ -8153,82 +1047,110 @@ msgid ""
 "Any hostnames violating these rules may not be propagated\n"
 "to other routers."
 msgstr ""
+"Aunque afortunadamente no hay limitación técnica alguna en I2P para los \n"
+"nombres de servidor, la libreta de direcciones impone varias "
+"restricciones \n"
+"sobre los nombres de servidor importados desde suscripciones. Hace \n"
+"esto por higiene tipográfica básica y compatibilidad con navegadores, y \n"
+"por seguridad. Las reglas son esencialmente las mismas que aquellas de \n"
+"la Sección 3.2.2. en el RFC2396. Cualquier nombre de servidor que viole \n"
+"esas reglas puede no ser propagado a otros routers."
 
-#: i2p2www/pages/site/docs/naming.html:186
+#: i2p2www/pages/site/docs/naming.html:240
 msgid "Names are converted to lower case on import."
-msgstr ""
+msgstr "Los nombres se convierten a minúsculas al importarlos."
 
-#: i2p2www/pages/site/docs/naming.html:190
+#: i2p2www/pages/site/docs/naming.html:244
 msgid ""
 "Names are checked for conflict with existing names in the existing "
 "userhosts.txt and hosts.txt\n"
 "(but not privatehosts.txt) after conversion to lower case."
 msgstr ""
+"Se comprueban los conflictos entre los nombres y los nombres existentes "
+"en \n"
+"userhosts.txt y hosts.txt (pero no privatehosts.txt) tras su conversión a"
+" minúsculas."
 
-#: i2p2www/pages/site/docs/naming.html:195
+#: i2p2www/pages/site/docs/naming.html:249
 msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case."
 msgstr ""
+"Sólo deben contener  [a-z] [0-9] '.' y '-' tras su conversión a "
+"minúsculas."
 
-#: i2p2www/pages/site/docs/naming.html:199
+#: i2p2www/pages/site/docs/naming.html:253
 msgid "Must not start with '.' or '-'."
-msgstr ""
+msgstr "No deben comenzar con '.' o '-'."
 
-#: i2p2www/pages/site/docs/naming.html:203
+#: i2p2www/pages/site/docs/naming.html:257
 msgid "Must end with '.i2p'."
 msgstr "Debe terminar en «.i2p»."
 
-#: i2p2www/pages/site/docs/naming.html:207
+#: i2p2www/pages/site/docs/naming.html:261
 msgid "67 characters maximum, including the '.i2p'."
-msgstr ""
+msgstr "Máximo 67 caracteres, incluyendo el '.i2p'."
 
-#: i2p2www/pages/site/docs/naming.html:211
+#: i2p2www/pages/site/docs/naming.html:265
 msgid "Must not contain '..'."
 msgstr "No puede contener «..»."
 
-#: i2p2www/pages/site/docs/naming.html:215
+#: i2p2www/pages/site/docs/naming.html:269
 msgid "Must not contain '.-' or '-.' (as of 0.6.1.33)."
-msgstr ""
+msgstr "No deben contener '.-' o '-.' (a partir de la 0.6.1.33)."
 
-#: i2p2www/pages/site/docs/naming.html:219
+#: i2p2www/pages/site/docs/naming.html:273
 msgid "Must not contain '--' except in 'xn--' for IDN."
-msgstr ""
+msgstr "No deben contener '--' excepto en 'xn--' para IDN."
 
-#: i2p2www/pages/site/docs/naming.html:223
-msgid "Base32 hostnames (*.b32.i2p) are not allowed."
+#: i2p2www/pages/site/docs/naming.html:277
+msgid ""
+"Base32 hostnames (*.b32.i2p) are reserved for base 32 use and so are not "
+"allowed to be imported."
 msgstr ""
+"Los nombres de equipo Base32 (*.b32.i2p) están reservados para el uso de "
+"base 32 y por tanto no está permitida su importación."
 
-#: i2p2www/pages/site/docs/naming.html:227
+#: i2p2www/pages/site/docs/naming.html:281
 msgid ""
 "Certain hostnames reserved for project use are not allowed\n"
 "(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
 "*.console.i2p, and others)"
 msgstr ""
+"Ciertos nombres de servidor reservados para uso del proyecto no están "
+"autorizados \n"
+"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
+"*.console.i2p, y otros)"
 
-#: i2p2www/pages/site/docs/naming.html:232
+#: i2p2www/pages/site/docs/naming.html:286
 msgid "Keys are checked for base64 validity."
-msgstr ""
+msgstr "Se comprueba la validez base64 de las claves."
 
-#: i2p2www/pages/site/docs/naming.html:236
+#: i2p2www/pages/site/docs/naming.html:290
 msgid ""
 "Keys are checked for conflict with existing keys in hosts.txt (but not "
 "privatehosts.txt)."
 msgstr ""
+"Se comprueba si las claves tienen conflictos con claves existentes en \n"
+"hosts.txt (pero no privatehosts.txt)."
 
-#: i2p2www/pages/site/docs/naming.html:240
+#: i2p2www/pages/site/docs/naming.html:294
 msgid "Minimum key length 516 bytes."
-msgstr ""
+msgstr "La longitud mínima de clave es 516 bytes."
 
-#: i2p2www/pages/site/docs/naming.html:244
+#: i2p2www/pages/site/docs/naming.html:298
 msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)."
 msgstr ""
+"La longitud máxima de clave es 616 bytes (para contar con certificados de"
+" hasta 100 bytes)."
 
-#: i2p2www/pages/site/docs/naming.html:249
+#: i2p2www/pages/site/docs/naming.html:303
 msgid ""
-"Any name received via subscription that passes all the checks is added to"
-" the local hosts.txt."
+"Any name received via subscription that passes all the checks is added "
+"via the local naming service."
 msgstr ""
+"Cualquier nombre recibido vía suscripción que pase todas las "
+"comprobaciones, se añade a través del servicio de nombres local."
 
-#: i2p2www/pages/site/docs/naming.html:253
+#: i2p2www/pages/site/docs/naming.html:307
 msgid ""
 "Note that the '.' symbols in a host name are of no significance,\n"
 "and do not denote any actual naming or trust hierarchy.\n"
@@ -8239,8 +1161,18 @@ msgid ""
 "and the desirability and feasibility of these methods,\n"
 "are topics for future discussion."
 msgstr ""
+"Observe que los símbolos '.' en el nombre de servidor no tienen\n"
+"significado, y no denotan jerarquía de confianza o de nombres alguna. \n"
+"Si el nombre 'host.i2p' ya existe, no hay nada que evite que alguien "
+"añada \n"
+"un nombre 'a.host.i2p' a su(s) hosts.txt, y este nombre pueda ser "
+"importado \n"
+"por las libretas de direcciones de otros. Los métodos para denegar \n"
+"subdominios a propietarios de no-dominios (¿certificados?), y lo deseable"
+" \n"
+"y factible de estos métodos, son temas para futura discusión."
 
-#: i2p2www/pages/site/docs/naming.html:264
+#: i2p2www/pages/site/docs/naming.html:318
 msgid ""
 "International Domain Names (IDN) also work in i2p (using punycode 'xn--' "
 "form).\n"
@@ -8248,8 +1180,12 @@ msgid ""
 "bar,\n"
 "add 'network.IDN.whitelist.i2p (boolean) = true' in about:config."
 msgstr ""
+"Los Nombres de Dominio Internacionales (IDN) también funcionan con I2P \n"
+"(usando la forma punycode 'xn--'). Para ver nombres de dominio .i2p IDN \n"
+"correctamente formados en la barra de direcciones de Firefox, añada \n"
+"'network.IDN.whitelist.i2p (boolean) = true' en about:config"
 
-#: i2p2www/pages/site/docs/naming.html:270
+#: i2p2www/pages/site/docs/naming.html:324
 msgid ""
 "As the addressbook application does not use privatehosts.txt at all, in "
 "practice\n"
@@ -8257,12 +1193,18 @@ msgid ""
 "aliases or\n"
 "\"pet names\" for sites already in hosts.txt."
 msgstr ""
+"Como la aplicación libreta de direcciones no usa privatehosts.txt para "
+"nada, \n"
+"en la práctica este fichero es el único lugar donde es apropiado emplazar"
+" \n"
+"alias privados o \"nombres de mascota\" para sitios ya existentes en "
+"hosts.txt"
 
-#: i2p2www/pages/site/docs/naming.html:276
+#: i2p2www/pages/site/docs/naming.html:330
 msgid "Outgoing Subscriptions"
-msgstr ""
+msgstr "Suscripciones salientes"
 
-#: i2p2www/pages/site/docs/naming.html:277
+#: i2p2www/pages/site/docs/naming.html:331
 msgid ""
 "Addressbook will publish the merged hosts.txt to a location\n"
 "(traditionally hosts.txt in the local eepsite's home directory) to be "
@@ -8270,8 +1212,12 @@ msgid ""
 "for their subscriptions.\n"
 "This step is optional and is disabled by default."
 msgstr ""
+"La libreta de direcciones publicará el hosts.txt fusionado hacia un \n"
+"emplazamiento (tradicionalmente el hosts.txt del directorio home del \n"
+"eepsite) para que sea accesible para las suscripciones de otros. \n"
+"Este paso es opcional y está deshabilitado por defecto."
 
-#: i2p2www/pages/site/docs/naming.html:285
+#: i2p2www/pages/site/docs/naming.html:339
 msgid ""
 "The addressbook application, together with eepget, saves the Etag and/or "
 "Last-Modified\n"
@@ -8279,14 +1225,22 @@ msgid ""
 "This greatly reduces the bandwidth required, as the web server will\n"
 "return a '304 Not Modified' on the next fetch if nothing has changed."
 msgstr ""
+"La aplicación libreta de direcciones, junto con eepget, previene que la \n"
+"información del Etag y/o la de Última-modificación sea devuelta por el \n"
+"servidor web de la suscripción. Esto reduce enormemente el ancho de banda"
+" \n"
+"requerido ya que el servidor web devolverá un '304 No Modificado' en la \n"
+"la siguiente toma de datos (`fetch`) si nada ha cambiado."
 
-#: i2p2www/pages/site/docs/naming.html:292
+#: i2p2www/pages/site/docs/naming.html:346
 msgid ""
 "However the entire hosts.txt is downloaded if it has changed.\n"
 "See below for discussion on this issue."
 msgstr ""
+"Sin embargo, si ha cambiado se descarga el hosts.txt completo. \n"
+"Mire debajo las discusiones sobre este asunto."
 
-#: i2p2www/pages/site/docs/naming.html:297
+#: i2p2www/pages/site/docs/naming.html:351
 msgid ""
 "Hosts serving a static hosts.txt or an equivalent CGI application\n"
 "are strongly encouraged to deliver\n"
@@ -8296,12 +1250,19 @@ msgid ""
 "This will dramatically reduce the network bandwidth, and\n"
 "reduce chances of corruption."
 msgstr ""
+"Se recomienda que los servidores que sirven un archivo host.txt o una "
+"aplicación CGI equivalente, lleven una cabecera con el tqmaño del "
+"contenido, Content-Length header, y una Etag o la última cabecera "
+"modificada, Last-Modified header. Además asegúrese de que el servidor "
+"muestra el aviso '304 Not Modified' cuando sea apropiado. Esto reducirá "
+"dramáticamente el ancho de banda usado, y reducirá las posibilidades de "
+"corrupción."
 
-#: i2p2www/pages/site/docs/naming.html:306
+#: i2p2www/pages/site/docs/naming.html:360
 msgid "Host Add Services"
-msgstr ""
+msgstr "Servicio de gestión de dominios"
 
-#: i2p2www/pages/site/docs/naming.html:307
+#: i2p2www/pages/site/docs/naming.html:361
 msgid ""
 "A host add service is a simple CGI application that takes a hostname and "
 "a Base64 key as parameters\n"
@@ -8309,64 +1270,75 @@ msgid ""
 "If other routers subscribe to that hosts.txt, the new hostname/key\n"
 "will be propagated through the network."
 msgstr ""
+"Un servicio de gestión de dominios es una aplicación CGI simple que toma "
+"un nombre de dominio y una clave Base64 como parámetros y loa añade a su "
+"hosts.txt local. SI otros ruters se suscriben a ese host.txt, el nuevo "
+"nombre de domino/clave serán propagados a través de la red."
 
-#: i2p2www/pages/site/docs/naming.html:314
+#: i2p2www/pages/site/docs/naming.html:368
 msgid ""
 "It is recommended that host add services impose, at a minimum, the "
 "restrictions imposed by the addressbook application listed above.\n"
 "Host add services may impose additional restrictions on hostnames and "
 "keys, for example:"
 msgstr ""
+"Se recomienda que los servicios de gestión de dominios impongan, como "
+"mínimo, las restricciones impuestas por la aplicación libreta de "
+"direcciones listadas anteriormente. Los servicios de gestión de dominios "
+"deben imponer restricciones adicionales en los nombres de dominio y en "
+"las claves, por ejemplo:"
 
-#: i2p2www/pages/site/docs/naming.html:319
+#: i2p2www/pages/site/docs/naming.html:373
 msgid "A limit on number of 'subdomains'."
-msgstr ""
+msgstr "Un 'límite' en el número de 'subdominios'."
 
-#: i2p2www/pages/site/docs/naming.html:323
+#: i2p2www/pages/site/docs/naming.html:377
 msgid "Authorization for 'subdomains' through various methods."
-msgstr ""
+msgstr "Autorización para los 'subdominios' a través de varios métodos."
 
-#: i2p2www/pages/site/docs/naming.html:327
+#: i2p2www/pages/site/docs/naming.html:381
 msgid "Hashcash or signed certificates."
-msgstr ""
+msgstr "Hashcash o certificados firmados."
 
-#: i2p2www/pages/site/docs/naming.html:331
+#: i2p2www/pages/site/docs/naming.html:385
 msgid "Editorial review of host names and/or content."
-msgstr ""
+msgstr "Revisión editorial de los nombres de dominio y/o su contenido."
 
-#: i2p2www/pages/site/docs/naming.html:335
+#: i2p2www/pages/site/docs/naming.html:389
 msgid "Categorization of hosts by content."
-msgstr ""
+msgstr "Clasificación de los dominios según su contenido."
 
-#: i2p2www/pages/site/docs/naming.html:339
+#: i2p2www/pages/site/docs/naming.html:393
 msgid "Reservation or rejection of certain host names."
-msgstr ""
+msgstr "Reserva o rechazo de ciertos dominios."
 
-#: i2p2www/pages/site/docs/naming.html:343
+#: i2p2www/pages/site/docs/naming.html:397
 msgid "Restrictions on the number of names registered in a given time period."
 msgstr ""
+"Restricciones en el número de dominios registrados en un determinado "
+"periodo de tiempo."
 
-#: i2p2www/pages/site/docs/naming.html:347
+#: i2p2www/pages/site/docs/naming.html:401
 msgid "Delays between registration and publication."
-msgstr ""
+msgstr "Intervalos entre los registros y las publicaciones."
 
-#: i2p2www/pages/site/docs/naming.html:351
+#: i2p2www/pages/site/docs/naming.html:405
 msgid "Requirement that the host be up for verification."
-msgstr ""
+msgstr "Exigir que el servidor esté funcionando para su verificaión."
 
-#: i2p2www/pages/site/docs/naming.html:355
+#: i2p2www/pages/site/docs/naming.html:409
 msgid "Expiration and/or revocation."
 msgstr "Expiración y/o revocación."
 
-#: i2p2www/pages/site/docs/naming.html:359
+#: i2p2www/pages/site/docs/naming.html:413
 msgid "IDN spoof rejection."
-msgstr ""
+msgstr "Denegación de IDN spoof."
 
-#: i2p2www/pages/site/docs/naming.html:364
+#: i2p2www/pages/site/docs/naming.html:418
 msgid "Jump Services"
-msgstr ""
+msgstr "Servicios de salto"
 
-#: i2p2www/pages/site/docs/naming.html:365
+#: i2p2www/pages/site/docs/naming.html:419
 msgid ""
 "A jump service is a simple CGI application that takes a hostname as a "
 "parameter\n"
@@ -8378,41 +1350,62 @@ msgid ""
 "In addition, the proxy will cache that key so the\n"
 "address helper is not necessary until restart."
 msgstr ""
+"Un servicio de salto, jump service, es una aplicación CGI que toma un "
+"nombre de dominio como parámetro y devuelve una re-dirección 301 a la URL"
+" apropiada con una cadena de texto ?i2paddresshelper=key "
+"añadida. El servidor HTTP interpretará la cadena de texto añadida y usará"
+" la clave como la destinación actual. Además, el proxy cacheará esa clave"
+" para que el address helper no sea necesario hasta el próximo reinicio."
 
-#: i2p2www/pages/site/docs/naming.html:375
+#: i2p2www/pages/site/docs/naming.html:429
 msgid ""
 "Note that, like with subscriptions, using a jump service\n"
 "implies a certain amount of trust, as a jump service could maliciously\n"
 "redirect a user to an incorrect destination."
 msgstr ""
+"Dese cuenta que, al igual que con las suscripciones, el usar un servicio "
+"de salto implica confianza de su parte, debe fiarse del servicio de "
+"salto, ya que un servicio de salto podría redirigirle maliciosamente a "
+"una destinación incorrecta."
 
-#: i2p2www/pages/site/docs/naming.html:381
+#: i2p2www/pages/site/docs/naming.html:435
 msgid ""
 "To provide the best service, a jump service should be subscribed to\n"
 "several hosts.txt providers so that its local host list is current."
 msgstr ""
+"Para proporcionar un mejor servicio, un servicio de salto debería estar "
+"suscrito a varios proveedores de archivos host,.txt , para que su lista "
+"local de dominios esté al día."
 
-#: i2p2www/pages/site/docs/naming.html:387
+#: i2p2www/pages/site/docs/naming.html:441
 msgid ""
 "SusiDNS is simply a web interface front-end to configuring addressbook "
 "subscriptions\n"
 "and accessing the four addressbook files.\n"
 "All the real work is done by the 'addressbook' application."
 msgstr ""
+"SusiDNS es simplemente un interfaz web para configurar las suscripciones "
+"a la libreta de direcciones, y con acceso a los cuatro archivos de "
+"libretas de direcciones. Todo el trabajo duro es realizado por la "
+"aplicación 'addressbook', 'libreta de direcciones'."
 
-#: i2p2www/pages/site/docs/naming.html:393
+#: i2p2www/pages/site/docs/naming.html:447
 msgid ""
 "Currently, there is little enforcement of addressbook naming rules within"
 " SusiDNS,\n"
 "so a user may enter hostnames locally that would be rejected by\n"
 "the addressbook subscription rules."
 msgstr ""
+"Actualmente, hay poco control sobre las reglas de creación de los nombres"
+" de dominio dentro de SusiDNS, por lo que un usuario puede añadir nombres"
+" de dominios localmente que serían rechazados por las reglas de "
+"suscripción de la libreta de direcciones."
 
-#: i2p2www/pages/site/docs/naming.html:399
+#: i2p2www/pages/site/docs/naming.html:453
 msgid "Base32 Names"
-msgstr ""
+msgstr "Dominios Base32"
 
-#: i2p2www/pages/site/docs/naming.html:400
+#: i2p2www/pages/site/docs/naming.html:454
 msgid ""
 "I2P supports Base32 hostnames similar to Tor's .onion addresses.\n"
 "Base32 addresses are much shorter and easier to handle than the\n"
@@ -8420,13 +1413,24 @@ msgid ""
 "Example: "
 "ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p"
 msgstr ""
+"I2P soporta nombres de dominios Base32 similares a las direcciones .onion"
+" de Tor. Las direcciones Base32 son mucho más fáciles de manejar y mucho "
+"más cortas que los addresshelpers o las Destinaciones Base64 de 516 "
+"caracteres. Ejemplo:\n"
+"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p"
 
-#: i2p2www/pages/site/docs/naming.html:407
+#: i2p2www/pages/site/docs/naming.html:461
+#, python-format
 msgid ""
 "In Tor, the address is 16 characters (80 bits), or half of the SHA-1 "
 "hash.\n"
 "I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n"
 "The form is {52 chars}.b32.i2p.\n"
+"Tor has recently published a\n"
+"proposal\n"
+"to convert to an identical format of {52 chars}.onion for their hidden "
+"services.\n"
 "Base32 is implemented in the naming service, which queries the\n"
 "router over I2CP to lookup the LeaseSet to get the full Destination.\n"
 "Base32 lookups will only be successful when the Destination is up and "
@@ -8436,8 +1440,26 @@ msgid ""
 "significantly\n"
 "longer than a local address book lookup."
 msgstr ""
+"En Tor, la dirección es de 16 caracteres (80 bits), o la mitad del "
+"(identificador criptográfico) hash SHA-1.\n"
+"I2P usa 52 caracteres (256 bits) para representar el hash SHA-256 "
+"completo.\n"
+"La la forma es {52 chars}.b32.i2p .\n"
+"Tor ha publicado recientemente una propuesta para\n"
+"convertirlas a un formato idéntico de {52 chars}.onion para sus servicios"
+" ocultos.\n"
+"Base32 está implementado en el servicio de nombres, que realiza "
+"peticiones al router sobre I2CP para buscar el LeaseSet para obtener el "
+"destino completo.\n"
+"Las búsquedas Base32 sólo serán exitosas cuando el destino esté activo y "
+"publicando un LeaseSet.\n"
+"A causa de que la resolución puede requerir una búsqueda en la base de "
+"datos de red, puede llevar significativamente más tiempo que una búsqueda"
+" en la libreta de direcciones local."
 
-#: i2p2www/pages/site/docs/naming.html:419
+#: i2p2www/pages/site/docs/naming.html:476
 msgid ""
 "Base32 addresses can be used in most places where hostnames or full "
 "destinations\n"
@@ -8445,6 +1467,16 @@ msgid ""
 "name does not immediately resolve. I2PTunnel will fail, for example, if\n"
 "the name does not resolve to a destination."
 msgstr ""
+"Las direcciones Base32 pueden ser usadas en la mayoría de sitios donde se"
+" puedan usar los nombres de dominios o la Destinación completa, aunque "
+"hay algunas excepciones donde podría fallar sin el dominio no se resuelve"
+" inmediatamente, Por ejemplo, I2PTunnel fallará si el domino no resuelve "
+"una destinación."
+
+#: i2p2www/pages/site/docs/plugins.html:2
+#: i2p2www/pages/site/docs/spec/configuration.html:65
+msgid "Plugins"
+msgstr "Complementos"
 
 #: i2p2www/pages/site/docs/plugins.html:3
 msgid "June 2012"
@@ -8463,6 +1495,8 @@ msgid ""
 "I2P includes a plugin architecture\n"
 "to support easy development and installation of additional software."
 msgstr ""
+"I2P incluye una arquitectura de pluguins para dar soporte a la "
+"instalación fácil y desarrollo fácil de aplicaciones adicionales."
 
 #: i2p2www/pages/site/docs/plugins.html:14
 msgid ""
@@ -8470,20 +1504,27 @@ msgid ""
 "IRC\n"
 "clients, distributed file storage, wikis, and more."
 msgstr ""
+"Ahora hay plugins disponibles que soportan email distribuido, blogs, \n"
+"clientes IRC, almacenamiento de ficheros distribuido, wikis y más."
 
 #: i2p2www/pages/site/docs/plugins.html:19
 msgid "Benefits to i2p users and app developers:"
 msgstr ""
+"Los beneficios para los usuarios de I2P y los desarrolladores de "
+"aplicaciones son:"
 
 #: i2p2www/pages/site/docs/plugins.html:24
 msgid "Easy distribution of applications"
-msgstr ""
+msgstr "Fácil distribución de aplicaciones"
 
 #: i2p2www/pages/site/docs/plugins.html:28
 msgid ""
 "Allows innovation and use of additional libraries without worrying about\n"
 "increasing the size of i2pupdate.sud"
 msgstr ""
+"Permite la innovación y el uso de librerías adicionales sin preocuparse "
+"por el \n"
+"incremento de tamaño de i2pupdate.sud"
 
 #: i2p2www/pages/site/docs/plugins.html:33
 msgid ""
@@ -8491,50 +1532,67 @@ msgid ""
 "\n"
 "with the I2P installation"
 msgstr ""
+"Soporta aplicaciones grandes o de proposito-especial que nunca serían \n"
+"empaquetadas con la instalación de I2P"
 
 #: i2p2www/pages/site/docs/plugins.html:38
 msgid "Cryptographically signed and verified applications"
-msgstr ""
+msgstr "Aplicaciones criptográficamente firmadas y verificadas"
 
 #: i2p2www/pages/site/docs/plugins.html:42
 msgid "Automatic updates of applications, just like for the router"
-msgstr ""
+msgstr "Actualizaciones automáticas de aplicaciones, igual que para el router"
 
 #: i2p2www/pages/site/docs/plugins.html:46
 msgid ""
 "Separate initial install and update packages, if desired, for smaller "
 "update downloads"
 msgstr ""
+"Paquetes separados para la instalación inicial y las actualizaciones, si "
+"se \n"
+"desea, para tener descargas de actualizaciones más pequeñas"
 
 #: i2p2www/pages/site/docs/plugins.html:50
 msgid ""
 "One-click installation of applications. No more asking users to modify\n"
 "wrapper.config or clients.config"
 msgstr ""
+"Instalación de aplicaciones en un-sólo-clic. Sin preguntar más al usuario"
+" \n"
+"para modificar wrapper.config o clients.config"
 
 #: i2p2www/pages/site/docs/plugins.html:55
 msgid "Isolate applications from the base $I2P installation"
-msgstr ""
+msgstr "Aplicaciones aisladas desde la instalación base de $I2P"
 
 #: i2p2www/pages/site/docs/plugins.html:59
 msgid ""
 "Automatic compatibility checking for I2P version, Java version, Jetty\n"
 "version, and previous installed application version"
 msgstr ""
+"Comprobación automática de compatibilidad para la versión de I2P, la "
+"versión \n"
+"de Java, la versión de Jetty, y versiones de la aplicación previamente "
+"instaladas"
 
 #: i2p2www/pages/site/docs/plugins.html:64
 msgid "Automatic link addition in console"
-msgstr ""
+msgstr "Añadido automático de enlaces en la consola"
 
 #: i2p2www/pages/site/docs/plugins.html:68
 msgid ""
 "Automatic startup of application, including modifying classpath, without "
 "requiring a restart"
 msgstr ""
+"Inicio automático de la aplicación, incluyendo modificación de la ruta de"
+" \n"
+"clases (`classpath`), sin requerir un reinicio"
 
 #: i2p2www/pages/site/docs/plugins.html:72
 msgid "Automatic integration and startup of webapps into console Jetty instance"
 msgstr ""
+"Integración automática e inicio de aplicaciones web en la instancia de \n"
+"consola Jetty"
 
 #: i2p2www/pages/site/docs/plugins.html:76
 #, python-format
@@ -8542,22 +1600,25 @@ msgid ""
 "Facilitate creation of 'app stores' like the one at\n"
 "%(pluginsite)s"
 msgstr ""
+"Facilita la creación de 'app stores' (tiendas de aplicaciones) como la de"
+" \n"
+"%(pluginsite)s"
 
 #: i2p2www/pages/site/docs/plugins.html:81
 msgid "One-click uninstall"
-msgstr ""
+msgstr "Desinstalación en un-sólo-clic"
 
 #: i2p2www/pages/site/docs/plugins.html:85
 msgid "Language and theme packs for the console"
-msgstr ""
+msgstr "Paquetes de idioma y de temas para la consola"
 
 #: i2p2www/pages/site/docs/plugins.html:89
 msgid "Bring detailed application information to the router console"
-msgstr ""
+msgstr "Trae información detallada de la aplicación a la consola del router"
 
 #: i2p2www/pages/site/docs/plugins.html:93
 msgid "Non-java applications also supported"
-msgstr ""
+msgstr "Las aplicaciones no-Java también están soportadas"
 
 #: i2p2www/pages/site/docs/plugins.html:99
 msgid "Required I2P version"
@@ -8585,6 +1646,14 @@ msgid ""
 " at\n"
 "the top of your summary bar."
 msgstr ""
+"Para instalar e iniciar un plugin, copie el enlace de instalación "
+".xpi2p en \n"
+"el formulario al final de configclients.jsp"
+" en la consola de su router y \n"
+"haga clic en el botón \"instalar plugin\". Después de que un plugin sea "
+"instalado e iniciado, un enlace al plugin aparecerá normalmente en la "
+"parte superior de su barra de resumen."
 
 #: i2p2www/pages/site/docs/plugins.html:112
 msgid ""
@@ -8601,6 +1670,16 @@ msgid ""
 "including dev\n"
 "builds)."
 msgstr ""
+"Para actualizar un plugin a la última versión, tan solo haga clic en el "
+"botón de actualización sobre configclients.jsp."
+" También hay un botón para \n"
+"comprobar si el plugin tiene una versión más reciente, así como un botón"
+" \n"
+"para buscar actualizaciones para todos los plugins. Se comprobará si hay"
+" \n"
+"actualizaciones para los plugins automáticamente cuando se actualice a \n"
+"una nueva versión de I2P (sin incluir las versiones de desarrollo)."
 
 #: i2p2www/pages/site/docs/plugins.html:122
 msgid "Development"
@@ -8613,6 +1692,9 @@ msgid ""
 "the\n"
 "plugin forum on %(zzz)s."
 msgstr ""
+"Vea las últimas especificaciones de "
+"plugins y el \n"
+"forum de plugins en %(zzz)s."
 
 #: i2p2www/pages/site/docs/plugins.html:128
 #, python-format
@@ -8623,6 +1705,12 @@ msgid ""
 "developed\n"
 "specifically as examples."
 msgstr ""
+"Vea también las fuentes de los plugins desarrollados por diferentes "
+"personas. \n"
+"Algunos plugins como snowman, fueron "
+"desarrollados específicamente \n"
+"como ejemplos."
 
 #: i2p2www/pages/site/docs/plugins.html:134
 msgid ""
@@ -8630,6 +1718,8 @@ msgid ""
 "\n"
 "or easily add some feature."
 msgstr ""
+"¡Se buscan desarrolladores! Los plugins son una gran manera de \n"
+"aprender más acerca de I2P o de añadir fácilmente alguna característica."
 
 #: i2p2www/pages/site/docs/plugins.html:139
 msgid "Getting Started"
@@ -8642,6 +1732,10 @@ msgid ""
 "makeplugin.sh from the i2p.scripts branch in "
 "monotone."
 msgstr ""
+"Para crear un plugin desde un paquete binario existente necesitará "
+"obtener \n"
+"makeplugin.sh desde el ramal (`branch`) de "
+"i2p.scripts en monotone."
 
 #: i2p2www/pages/site/docs/plugins.html:146
 msgid "Known Issues"
@@ -8652,6 +1746,8 @@ msgid ""
 "Note that the router's plugin architecture does NOT currently\n"
 "provide any additional security isolation or sandboxing of plugins."
 msgstr ""
+"Observe que la arquitectura del plugin del router actualmente NO\n"
+"proporciona seguridad adicional, aislamiento o sandboxing de plugins."
 
 #: i2p2www/pages/site/docs/plugins.html:153
 msgid ""
@@ -8660,10 +1756,15 @@ msgid ""
 " the\n"
 "class cache; a full router restart is required."
 msgstr ""
+"Las actualizaciones de un plugin con jars (no wars) incluidos, no serán \n"
+"reconocidas si el plugin ya se está ejecutando, ya que requiere usar \n"
+"trucos en el cargador de clases ('class') para limpiar la caché de "
+"clases;\n"
+"se requiere un reinicio completo del router."
 
 #: i2p2www/pages/site/docs/plugins.html:159
 msgid "The stop button may be displayed even if there is nothing to stop."
-msgstr ""
+msgstr "El botón de parada podría mostarse incluso si no hay nada que parar."
 
 #: i2p2www/pages/site/docs/plugins.html:163
 msgid ""
@@ -8671,6 +1772,9 @@ msgid ""
 "in\n"
 "$CWD."
 msgstr ""
+"Los plugins ejecutandose en una JVM crean un directorio "
+"logs/ en \n"
+"$CWD."
 
 #: i2p2www/pages/site/docs/plugins.html:168
 msgid ""
@@ -8679,6 +1783,11 @@ msgid ""
 "same keys as for router update), so the first key seen for a signer is\n"
 "automatically accepted—there is no signing key authority."
 msgstr ""
+"No hay claves inciales presentes, excepto para aquellos de `jrandom` y "
+"`zzz` \n"
+"(que usan las mismas claves que para la actualización del router), por \n"
+"lo que la primera clave vista para un firmante es automáticamente \n"
+"aceptada—no hay autoridad de clave de firmado."
 
 #: i2p2www/pages/site/docs/plugins.html:174
 msgid ""
@@ -8686,6 +1795,9 @@ msgid ""
 "on\n"
 "Windows."
 msgstr ""
+"Cuando se borra un plugin el directorio no siempre se borra, "
+"especialmente \n"
+"sobre Windows."
 
 #: i2p2www/pages/site/docs/plugins.html:179
 msgid ""
@@ -8694,14 +1806,19 @@ msgid ""
 "\"plugin is corrupt\" message if pack200 compression of the plugin file "
 "is used."
 msgstr ""
+"Instalar un plugin que requiere Java 1.6 sobre una máquina Java 1.5 "
+"resultará \n"
+"en un mensaje \"el plugin está corrupto\" si se usó la compresión pack200"
+" \n"
+"en el fichero del plugin."
 
 #: i2p2www/pages/site/docs/plugins.html:184
 msgid "Theme and translation plugins are untested."
-msgstr ""
+msgstr "Los plugins de temas y traducciones no están probados."
 
 #: i2p2www/pages/site/docs/plugins.html:188
 msgid "Disabling autostart doesn't always work."
-msgstr ""
+msgstr "Deshabilitar autoinicio no siempre funciona."
 
 #: i2p2www/pages/site/docs/ports.html:2
 msgid "Ports Used by I2P"
@@ -8714,6 +1831,10 @@ msgid ""
 "common alternates,\n"
 "and some typical related applications."
 msgstr ""
+"Estos son los puertos usados o reservados por I2P, incluyendo aquellos "
+"para plugins conocidos, \n"
+"alternativas comunes, \n"
+"y algunas aplicaciones típicas relacionadas."
 
 #: i2p2www/pages/site/docs/ports.html:13
 #, python-format
@@ -8725,18 +1846,31 @@ msgid ""
 "For new plugins, we recommend using the next available port\n"
 "in the 766x range."
 msgstr ""
+"Observe que muchos de estos no están habilitados de forma predeterminada."
+" \n"
+"Hay más información en las FAQ. Vea también"
+" la documentación para plugins individuales. Los autores de los \n"
+"plugins por favor añadan cualquier puerto que usen aquí. Para nuevos \n"
+"plugins recomendamos usar el siguiente puerto disponible en el rango 766x."
 
 #: i2p2www/pages/site/docs/ports.html:53
 msgid "recommended spot for new plugins/applications"
-msgstr ""
+msgstr "punto recomendado para nuevos plugins/aplicaciones"
+
+#: i2p2www/pages/site/docs/api/bob.html:3
+#: i2p2www/pages/site/docs/api/datagrams.html:3
+#: i2p2www/pages/site/docs/how/garlic-routing.html:3
+#: i2p2www/pages/site/docs/protocol/index.html:3
+msgid "August 2010"
+msgstr "Agosto del 2010"
 
 #: i2p2www/pages/site/docs/api/bob.html:5
 msgid "BOB - Basic Open Bridge"
-msgstr ""
+msgstr "BOB- Basic Open Bridge (pasarela abierta básica)"
 
 #: i2p2www/pages/site/docs/api/bob.html:7
 msgid "Technical differences from SAM (for the better?)"
-msgstr ""
+msgstr "Diferencias técnicas con SAM (¿para mejorarlo?)"
 
 #: i2p2www/pages/site/docs/api/bob.html:9
 msgid ""
@@ -8747,12 +1881,24 @@ msgid ""
 "destination key, and to set the destination key to port bindings. \n"
 "All connections run in parallel."
 msgstr ""
+"BOB tiene canales separados de comandos y de datos. \n"
+"Uno, un socket de canal de comandos de aplicación hacia el router.\n"
+"Dos, los sockets de datos de aplicación hacia/desde el router, que portan"
+" \n"
+"sólo datos.\n"
+"El canal de comandos sólo es necesario para generar o establecer la clave"
+" \n"
+"de destino inicial, y para establecer las ligaduras (`bindings`)  de las "
+"claves \n"
+"de destino con los puertos. Todas las conexiones se ejecutan en paralelo."
 
 #: i2p2www/pages/site/docs/api/bob.html:18
 msgid ""
 "SAM has one connection that does everything, and you need to parse every "
 "packet."
 msgstr ""
+"SAM tiene una conexión que hace todo, y usted necesita procesar todos los"
+" paquetes."
 
 #: i2p2www/pages/site/docs/api/bob.html:22
 msgid ""
@@ -8762,22 +1908,27 @@ msgid ""
 "to\n"
 "your privacy."
 msgstr ""
+"BOB no retiene valores de parejas de claves, tampoco lo hace el router. \n"
+"La aplicación de usted retiene los valores de parejas de claves.\n"
+"Esto es para reducir cualquier complejidad extra en el código del router,"
+" \n"
+"también contribuye a su privacidad."
 
 #: i2p2www/pages/site/docs/api/bob.html:29
 msgid "SAM router stores every keypair you ever make."
-msgstr ""
+msgstr "El router SAM guarda cada par de claves que alguna vez haya generado."
 
 #: i2p2www/pages/site/docs/api/bob.html:33
 msgid "Those are the important differences."
-msgstr ""
+msgstr "Esas son las diferencias importantes."
 
 #: i2p2www/pages/site/docs/api/bob.html:37
 msgid "KEYS = keypair public+private, these are BASE64"
-msgstr ""
+msgstr "CLAVES = par de claves pública+privada, estas son BASE64"
 
 #: i2p2www/pages/site/docs/api/bob.html:40
 msgid "KEY = public key, also BASE64"
-msgstr ""
+msgstr "CLAVE = clave pública, también BASE64"
 
 #: i2p2www/pages/site/docs/api/bob.html:43
 msgid ""
@@ -8785,6 +1936,9 @@ msgid ""
 "\"+DESCRIPTION+\"\n"
 "\", where the DESCRIPTION is what went wrong."
 msgstr ""
+"ERROR como está implícito, devuelve el mensaje \"ERROR"
+" \"+DESCRIPCIÓN+\"\n"
+"\", donde la DESCRIPCIÓN es lo que fue mal."
 
 #: i2p2www/pages/site/docs/api/bob.html:46
 msgid ""
@@ -8792,12 +1946,17 @@ msgid ""
 "returned, it is on the same line. OK means the command is "
 "finished."
 msgstr ""
+"OK devuelve \"OK\", y si se van a devolver "
+"datos, se hará en la misma línea. OK significa que el "
+"comando ha finalizado."
 
 #: i2p2www/pages/site/docs/api/bob.html:49
 msgid ""
 "DATA lines contain information that you requested. There may"
 " be multiple DATA lines per request."
 msgstr ""
+"DATOS líneas conteniendo la información que usted solicitó. "
+"Puede haber múltiples líneas de DATOS por solicitud."
 
 #: i2p2www/pages/site/docs/api/bob.html:53
 msgid ""
@@ -8806,6 +1965,10 @@ msgid ""
 "the rules... it can actually return nothing! This is intentional, since\n"
 "help is a HUMAN and not an APPLICATION command."
 msgstr ""
+"NOTA: El comando `help` es el ÚNICO comando que tiene una \n"
+"excepción a las reglas... actualmente puede devolver ¡nada! Es "
+"intencionado, \n"
+"dado que `help` es un HUMANO y no un comando de APLICACIÓN."
 
 #: i2p2www/pages/site/docs/api/bob.html:59
 msgid ""
@@ -8815,28 +1978,35 @@ msgid ""
 "Just telnet to localhost 2827 and type help and you can get full "
 "documentation on each command."
 msgstr ""
+"POR FAVOR OBSERVE QUE: Para detalles ACTUALES de los comandos POR "
+"FAVOR use el comando interno `help`. \n"
+"Tan sólo haga telnet al localhost 2827, teclee `help` y podrá obtener la"
+" \n"
+"documentación completa para cada comando."
 
 #: i2p2www/pages/site/docs/api/bob.html:65
 msgid ""
 "Commands never get obsoleted or changed, however new commands do get "
 "added from time to time."
 msgstr ""
+"Los comandos nunca cambian o se vuelven obsoletos, sin embargo nuevos "
+"comandos son añadidos de cuando en cuando."
 
 #: i2p2www/pages/site/docs/api/bob.html:69
 msgid "Here are the commands we have as of this writing:"
-msgstr ""
+msgstr "Aquí están los comandos que tenemos en el momento de escirbir esto:"
 
 #: i2p2www/pages/site/docs/api/bob.html:74
 msgid "COMMAND"
-msgstr ""
+msgstr "COMANDO"
 
 #: i2p2www/pages/site/docs/api/bob.html:74
 msgid "OPERAND"
-msgstr ""
+msgstr "OPERANDO"
 
 #: i2p2www/pages/site/docs/api/bob.html:74
 msgid "RETURNS"
-msgstr ""
+msgstr "DEVUELVE"
 
 #: i2p2www/pages/site/docs/api/bob.html:101
 msgid ""
@@ -8849,6 +2019,12 @@ msgid ""
 "many streams in or out one socket -- that can't scale when you have alot "
 "of connections!"
 msgstr ""
+"Una vez configurado, todos los sockets TCP pueden y bloquearán según se \n"
+"necesite, y no hay necesidad de mensaje adicional alguno hacia/desde el \n"
+"canal de comandos. Esto permite al router marcar el paso del stream sin \n"
+"reventar con un OOM (out of memory/agotamiento de memoria) como lo hace \n"
+"SAM al ahogarse intentando empujar varios streams dentro o fuera de un \n"
+"socket -- ¡que no puede crecer cuando tiene muchas conexiones!"
 
 #: i2p2www/pages/site/docs/api/bob.html:108
 msgid ""
@@ -8871,6 +2047,24 @@ msgid ""
 "It will simply be fooled -- the destinations are not reachable, and that "
 "nothing is coming in."
 msgstr ""
+"Lo que también es agradable acerca de esta interfaz en particular es que"
+" \n"
+"escribir algo para la interfaz, es mucho mucho más fácil que para SAM. \n"
+"No hay ningún otro proceso que realizar después de configurarla. Su \n"
+"configuración es tan simple, que muchas aplicaciones sencillas, tales \n"
+"como nc (netcat) se pueden usar para apuntar a alguna aplicación. El "
+"valor \n"
+"ahí es que uno puede programar periodos de actividad e inactividad para \n"
+"una aplicación, sin tener que cambiar la aplicación para hacer eso, o \n"
+"incluso sin tener que detener esa aplicación. En su lugar, puede "
+"literalmente\n"
+"\"desenchufar\" el destino, y \"enchufarlo\" de nuevo. Mientras las "
+"mismas \n"
+"direcciones IP/puerto y claves de destino sean usadas al levantar la \n"
+"pasarela, a las aplicaciones TCP normales no les importará, y no lo "
+"notarán. Simplemente serán engañadas -- los destinos no son alcanzables,"
+" \n"
+"y así nada va a recibirse."
 
 #: i2p2www/pages/site/docs/api/bob.html:120
 msgid ""
@@ -8882,10 +2076,15 @@ msgid ""
 "that you\n"
 "can telnet into, and watch the pretty ASCII test puke forth."
 msgstr ""
+"Para el siguiente ejemplo, estableceremos un conexión loopback local \n"
+"muy simple, con dos destinos. El destino \"boca\" será el servicio \n"
+"CHARGEN desde el demonio superservidor INET. El destino \"oido\" será \n"
+"un puerto local sobre el que podrá hacer telnet, y observar el precioso \n"
+"ASCII de prueba vomitado."
 
 #: i2p2www/pages/site/docs/api/bob.html:128
 msgid "EXAMPLE SESSION DIALOGUE -- simple telnet 127.0.0.1 2827 works"
-msgstr ""
+msgstr "DIÁLOGO DE SESIÓN DE EJEMPLO -- un simple `telnet 127.0.0.1 2827` funciona"
 
 #: i2p2www/pages/site/docs/api/bob.html:129
 msgid "Application"
@@ -8893,7 +2092,7 @@ msgstr "Aplicación"
 
 #: i2p2www/pages/site/docs/api/bob.html:130
 msgid "BOB's Command response."
-msgstr ""
+msgstr "Respuesta al comando de BOB."
 
 #: i2p2www/pages/site/docs/api/bob.html:132
 #: i2p2www/pages/site/docs/api/bob.html:144
@@ -8902,7 +2101,7 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/bob.html:284
 #: i2p2www/pages/site/docs/api/bob.html:299
 msgid "FROM"
-msgstr ""
+msgstr "DESDE"
 
 #: i2p2www/pages/site/docs/api/bob.html:132
 #: i2p2www/pages/site/docs/api/bob.html:144
@@ -8911,7 +2110,7 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/bob.html:284
 #: i2p2www/pages/site/docs/api/bob.html:299
 msgid "TO"
-msgstr ""
+msgstr "HACIA"
 
 #: i2p2www/pages/site/docs/api/bob.html:132
 #: i2p2www/pages/site/docs/api/bob.html:144
@@ -8920,11 +2119,11 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/bob.html:284
 #: i2p2www/pages/site/docs/api/bob.html:299
 msgid "DIALOGUE"
-msgstr ""
+msgstr "DIÁLOGO"
 
 #: i2p2www/pages/site/docs/api/bob.html:139
 msgid "MAKE NOTE OF THE ABOVE DESTINATION KEY, YOURS WILL BE DIFFERENT!"
-msgstr ""
+msgstr "ANOTE LA CLAVE DE DESTINO ANTERIOR, ¡LA SUYA SERÁ DIFERENTE!"
 
 #: i2p2www/pages/site/docs/api/bob.html:153
 msgid ""
@@ -8934,10 +2133,15 @@ msgid ""
 "connect \n"
 "to the CHARGEN service on 19/TCP."
 msgstr ""
+"En este punto no hubo error, un destino con un apodo de \"boca\" está \n"
+"establecido. Cuando contacte con el destino proporcionado, en realidad \n"
+"conectará con el servicio CHARGEN sobre 19/TCP."
 
 #: i2p2www/pages/site/docs/api/bob.html:159
 msgid "Now for the other half, so that we can actually contact this destination."
 msgstr ""
+"Ahora para la otra mitad, para que realmente podamos contactar con este "
+"destino."
 
 #: i2p2www/pages/site/docs/api/bob.html:179
 msgid ""
@@ -8947,24 +2151,34 @@ msgid ""
 "In this case, we want to contact \"mouth\", all we do is paste in the\n"
 "key and it goes."
 msgstr ""
+"Ahora todo lo que necesitamos es hacer telnet a 127.0.0.1, puerto 37337,"
+" \n"
+"enviar la clave destino o la dirección del servidor de la libreta de "
+"direcciones \n"
+"con la que queramos contactar. En este caso, queremos contactar con \n"
+"\"boca\", todo lo que haremos es pegar la clave e irá."
 
 #: i2p2www/pages/site/docs/api/bob.html:186
 msgid ""
 "NOTE: The \"quit\" command in the command channel does NOT "
 "disconnect the tunnels like SAM."
 msgstr ""
+"NOTA: El comando \"quit\" en el canal de comandos NO desconecta \n"
+"los túneles como SAM."
 
 #: i2p2www/pages/site/docs/api/bob.html:203
 msgid "After a few virtual miles of this spew, press Control-]"
 msgstr ""
+"Después de unas pocas millas virtuales de esta eyección, presione "
+"Control-]"
 
 #: i2p2www/pages/site/docs/api/bob.html:215
 msgid "Here is what happened..."
-msgstr ""
+msgstr "Aquí está lo que sucedió..."
 
 #: i2p2www/pages/site/docs/api/bob.html:223
 msgid "You can connect to EEPSITES too!"
-msgstr ""
+msgstr "¡También puede conectar con EEPSITES!"
 
 #: i2p2www/pages/site/docs/api/bob.html:256
 msgid ""
@@ -8977,18 +2191,28 @@ msgid ""
 "They would be meaningless to the application, and are only presented for "
 "human debugging."
 msgstr ""
+"Bastante chulo ¿verdad? Pruebe con algún otro EEPSITE bien conocido si \n"
+"prefiere, o con los no existentes, etc. para conseguir una sensación de "
+"qué \n"
+"tipo de resultado esperar en diferentes situaciones. Para la mayor parte,"
+" se \n"
+"sugiere que ignore cualquier tipo de mensajes de error. No tendrían "
+"significado \n"
+"para la aplicación, y sólo son presentados para depuración por humanos."
 
 #: i2p2www/pages/site/docs/api/bob.html:263
 msgid "Let's put down our destinations now that we are all done with them."
 msgstr ""
+"Desactivemos nuestros destinos ahora que hemos terminado del todo con "
+"ellos."
 
 #: i2p2www/pages/site/docs/api/bob.html:267
 msgid "First, lets see what destination nicknames we have."
-msgstr ""
+msgstr "Primero, veamos que apodos de destino tenemos."
 
 #: i2p2www/pages/site/docs/api/bob.html:279
 msgid "Alright, there they are. First, let's remove \"mouth\"."
-msgstr ""
+msgstr "De acuerdo, ahí las tiene. Primero, eliminemos \"boca\" (`mouth`)."
 
 #: i2p2www/pages/site/docs/api/bob.html:293
 msgid ""
@@ -8996,6 +2220,10 @@ msgid ""
 "fast,\n"
 "and shows you what typical ERROR messages looks like."
 msgstr ""
+"Ahora para eliminar \"oido\" (`ear`), note que esto es lo que ocurre "
+"cuando teclea\n"
+"demasiado rápido, y le muestra el aspecto de los típicos mensajes de "
+"ERROR."
 
 #: i2p2www/pages/site/docs/api/bob.html:312
 msgid ""
@@ -9003,6 +2231,11 @@ msgid ""
 "because it is very simple. There are two possible settings for it, and\n"
 "it is toggled with the \"quiet\" command."
 msgstr ""
+"No le molestaré mostrando un ejemplo de un receptor final de una pasarela"
+" \n"
+"(`bridge`) porque es muy simple. Hay dos posibles configuraciones para "
+"ello, \n"
+"y se accionan con el comando \"quiet\" (silenciar)."
 
 #: i2p2www/pages/site/docs/api/bob.html:318
 msgid ""
@@ -9011,6 +2244,12 @@ msgid ""
 "single line consisting of the BASE64 address followed by a newline.\n"
 "Everything after that is for the application to actually consume."
 msgstr ""
+"La configuración por defecto es NO silenciado, a y los primeros datos en"
+" \n"
+"llegar a su socket de escucha es el destiono que está estableciendo el \n"
+"contacto. Es una sola línea consistente en una dirección BASE64 seguida \n"
+"de una nueva línea. Todo lo que viene después de aquello es en realidad \n"
+"para consumo de la aplicación."
 
 #: i2p2www/pages/site/docs/api/bob.html:325
 msgid ""
@@ -9021,6 +2260,19 @@ msgid ""
 "can use BOB to point a destination at a web server, for example, and\n"
 "you would not have to modify the web server at all."
 msgstr ""
+"En modo silencioso, piense en él como en una conexión regular a Internet."
+" \n"
+"No hay dato extra entrante alguno. Es tan solo como si estuviera "
+"conectado \n"
+"normalmente al Internet regular. Este modo permite una forma de "
+"transparencia \n"
+"muy parecida a la que está disponible en las páginas de configuración del"
+" \n"
+"túnel de la consola del router, así que usted puede, por ejemplo, usar "
+"BOB \n"
+"para apuntar hacia un destino en un servidor web, y no tendría que "
+"modificar \n"
+"para nada el servidor web."
 
 #: i2p2www/pages/site/docs/api/bob.html:334
 msgid ""
@@ -9036,10 +2288,28 @@ msgid ""
 "point to a set of backup machines depending on what is running, etc,\n"
 "etc. Only your imagination limits what you could do with BOB."
 msgstr ""
+"La ventaja de usar BOB para esto es la que fue discutida previamente. \n"
+"Puede programar periodos de actividad aleatorios para la aplicación, "
+"redirigirla \n"
+"a una máquina diferente, etc. Un uso de esto puede ser algo parecido a \n"
+"tratar de confundir acciones de estimación de la conectividad router-"
+"destino. \n"
+"Puede detener e iniciar el destino con un proceso totalmente diferente "
+"para \n"
+"establecer periodos aleatorios de actividad e inactividad para los "
+"servicios. De ese modo sólo se estaría deteniendo la capacidad de "
+"contactar con tal \n"
+"servicio, sin tener que preocuparse cerrándolo y reiniciándolo. Podría "
+"redirigir \n"
+"y apuntar a una máquina diferente de su LAN, mientras hace "
+"actualizaciones, \n"
+"o apuntar a un conjunto de máquinas de respaldo dependiendo de lo que se "
+"esté ejecuntando, etc, etc. Sólo su imaginación limita lo que podría "
+"hacer con BOB."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:6
 msgid "Datagram Overview"
-msgstr ""
+msgstr "Introducción a los datagramas"
 
 #: i2p2www/pages/site/docs/api/datagrams.html:7
 #, python-format
@@ -9056,6 +2326,19 @@ msgid ""
 "addition, the\n"
 "message and sender are authenticated by signing the payload."
 msgstr ""
+"Los datagramas se construyen sobre la base de I2CP para proporcionar \n"
+"autentificación y mensajes respondibles en un formato estandar. \n"
+"Esto permite a las aplicaciones leer con fiabilidad la dirección \"from\""
+" (desde)\n"
+"de los datragramas, y confirmar que la dirección envió efectivamente el "
+"mensaje. \n"
+"Esto es necesario para algunas aplicaciones ya que el mensaje base I2P es"
+" \n"
+"completamente crudo (`raw`) - no tiene dirección \"from\" (al contrario "
+"que los \n"
+"paquetes IP). Además el mensaje y el emisor son autentificados mediante \n"
+"el firmado de la carga."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:16
 #, python-format
@@ -9067,10 +2350,16 @@ msgid ""
 "the protocols are converted to I2NP messages by the router, and\n"
 "either protocol may be carried by either transport."
 msgstr ""
+"Los datagramas, al igual que los paquetes de la"
+" librería de streaming, son una construcción al nivel de aplicación. "
+"Estos protocolos son diferentes de los transportes de bajo nivel; estos protocolos "
+"son convertidos en mensajes I2NP por el ruter, y así cualquier protocolo "
+"puede ser llevado por cualquier transporte."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:25
 msgid "Application Guide"
-msgstr ""
+msgstr "Guía de aplicaciones"
 
 #: i2p2www/pages/site/docs/api/datagrams.html:26
 #, python-format
@@ -9083,6 +2372,12 @@ msgid ""
 "href=\"%(socks)s\">SOCKS proxy,\n"
 "the 'streamr' tunnel types, and udpTunnel classes."
 msgstr ""
+"Las aplicaciones escritas en Java pueden usar la API "
+"datagram, mientras que las aplicaciones en otros idomas pueden usar"
+" \n"
+"el soporte datagram de SAM. También hay soporte "
+"limitado en i2ptunnel en el proxy SOCKS, los \n"
+"tipos de túnel 'streamr', y las clases udpTunnel."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:37
 msgid "Datagram Length"
@@ -9102,6 +2397,16 @@ msgid ""
 "Messages over 16 KB cannot be delivered over NTCP, dropping delivery "
 "chances even more."
 msgstr ""
+"El diseñador de la aplicación debe considerar cuidadosamente las\n"
+"contrapartidas de datagramas respondibles frente a los no-respondibles. \n"
+"El tamaño del datagrama también afectaría a la fiabilidad, debido a la \n"
+"fragmentación del túnel en mensajes de túnel de 1KB. Cuantos más \n"
+"fragmentos de mensaje, más probable es que uno de ellos se pierda en un \n"
+"salto intermedio. Los mensajes más largos de unos pocos KB no están \n"
+"recomendados. Por encima de alrededor de 10KB, la probabilidad de entrega"
+" \n"
+"cae dramáticamente. Los mensajes por encima de 16KB no pueden ser \n"
+"entregados sobre NTCP (TCP basado en NIO)."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:47
 #, python-format
@@ -9120,10 +2425,20 @@ msgid ""
 "tune\n"
 "the ElGamal Session Tag parameters."
 msgstr ""
+"Observe también que el variado tráfico de control añadido por las capas \n"
+"inferiores, en particular la asimétrica ElGamal/AES, coloca una \n"
+"gran carga sobre los mensajes intermitentes tales como los usados por \n"
+"una aplicación Kademlia-sobre-UDP. Las implementaciones actualmente \n"
+"se ajustan para tráfico frecuente usando la librería streaming. Por \n"
+"ejemplo, si hay un alto número de etiquetas de sesión entregadas, y una \n"
+"vida corta de etiqueta de sesión. Actualmente no hay parámetros de \n"
+"configuración disponibles dentro de I2CP para ajustar los parametros de \n"
+"la Etiqueta de Sesión ElGamal."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:57
 msgid "I2CP Protocol Number and Ports"
-msgstr ""
+msgstr "Número de protocolo y puertos de I2CP"
 
 #: i2p2www/pages/site/docs/api/datagrams.html:58
 msgid ""
@@ -9133,6 +2448,12 @@ msgid ""
 "It must be set to demultiplex datagram and streaming traffic received on "
 "the same Destination."
 msgstr ""
+"El número stadard del protocolo I2CP (Protocolo de Cliente I2P) para \n"
+"datagramas es PROTO_DATAGRAM (17). Las aplicaciones pueden o no \n"
+"elegir establecer el protocolo en la cabecera I2CP. No está establecido "
+"por \n"
+"defecto. Debe ser establecido para demultiplexar el datagrama y el "
+"tráfico de streaming recibido en el mismo Destino."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:65
 #, python-format
@@ -9145,6 +2466,13 @@ msgid ""
 "described in\n"
 "the I2CP page."
 msgstr ""
+"Como los datagramas no están orientados a la conexión, la aplicación "
+"puede \n"
+"requerir números de puerto para correlacionar los datagramas con pares "
+"('peers') concrectos o sesiones de comunicaciones, como es tradicional "
+"con UDP sobre IP. Las aplicaciones pueden añadir puertos 'from' (origen) "
+"y 'to' (destino) a la cabecera (gzip) I2CP como se describe en la página de I2CP."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:73
 #, python-format
@@ -9164,6 +2492,19 @@ msgid ""
 "datagram\n"
 "for the reply, returning the nonce from the request."
 msgstr ""
+"No hay método dentro de la API datagram para especificar si es no-"
+"respondible (raw (crudo)) o respondible. La aplicación debe ser designada"
+" \n"
+"para esperar el tipo apropiado. El número de protocolo I2CP o el puerto \n"
+"debería ser usado por la aplicación para indicar el tipo de datagrama. "
+"Los \n"
+"números de protocolo I2CP `PROTO_DATAGRAM_RAW` se definen en la \n"
+"API I2PSession para este propósito. Un "
+"patrón de diseño común en aplicaciones datagrama cliente/servidor es usar"
+" \n"
+"datagramas firmados para una petición que incluye un nonce (valor de \n"
+"seguridad de un único uso), y usa un datagrama crudo (`raw`) para la \n"
+"respuesta, devolviendo el nonce desde la petición."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:85
 #, python-format
@@ -9173,9 +2514,13 @@ msgid ""
 "as implemented in\n"
 "I2PSessionMuxedImpl."
 msgstr ""
+"Los protocolos y puertos pueden ser establecidos en la API I2PSession \n"
+"de I2CP, tal como están implementados en I2PSessionMuxedImpl."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:93
-#: i2p2www/pages/site/docs/api/streaming.html:325
+#: i2p2www/pages/site/docs/api/streaming.html:381
 msgid "Data Integrity"
 msgstr "Integridad de los datos"
 
@@ -9186,9 +2531,13 @@ msgid ""
 "the I2CP layer.\n"
 "There is no checksum field in the datagram protocol."
 msgstr ""
+"La integridad de los datos está asegurada por el checksum CRC-32 de gzip"
+" \n"
+"implementado en la capa I2CP. No hay "
+"campo checksum en el protocolo datagram"
 
 #: i2p2www/pages/site/docs/api/datagrams.html:100
-#: i2p2www/pages/site/docs/api/streaming.html:333
+#: i2p2www/pages/site/docs/api/streaming.html:389
 msgid "Packet Encapsulation"
 msgstr "Encapsulado de paquetes"
 
@@ -9205,20 +2554,28 @@ msgid ""
 "There is no packet delimiter mechanism or length field in the datagram "
 "protocol."
 msgstr ""
+"Cada datagrama se envía a través de I2P como un mensaje único (o como un "
+"'clove' (diente) individual en un `Garlic "
+"Message)` (mensaje ajo). \n"
+"La encapsulación del mensaje se implementa en los I2CP, I2NP, y \n"
+"las capas de mensaje de túnel "
+"subyacentes. No hay mecanismo \n"
+"delimitador de paquetes o campo de tamaño en el protocolo datagram."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:114
 #: i2p2www/pages/site/docs/spec/datagrams.html:10
-#: i2p2www/pages/site/docs/transport/ssu.html:567
+#: i2p2www/pages/site/docs/transport/ssu.html:571
 msgid "Specification"
 msgstr "Especificación"
 
 #: i2p2www/pages/site/docs/api/datagrams.html:116
 msgid "See the Datagrams Specification page."
-msgstr ""
+msgstr "Vea la página de Especificaciones de Datagramas."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:4
 msgid "I2PControl - Remote Control Service"
-msgstr ""
+msgstr "I2PControl - Servicio de Control Remoto"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:5
 #, python-format
@@ -9235,10 +2592,25 @@ msgid ""
 "at the JSON-RPC "
 "wiki."
 msgstr ""
+"I2P habilita una interfaz JSONRPC2 a través del plugin I2PControl. \n"
+"El propósito de la interfaz es proporcionar un camino sencillo a la "
+"interacción con \n"
+"un nodo I2P en ejecución. Un cliente, itoopie, ha sido desarrollado en "
+"paralelo. \n"
+"La implementación JSONRPC2 para el cliente, así como el plugin, son \n"
+"proporcionados por las librerías Java JSON-RPC "
+"2.0. Una lista de \n"
+"implementaciones de JSON-RPC para diferentes lenguajes puede encontrarse "
+"en \n"
+"el wiki de JSON-"
+"RPC."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:12
 msgid "I2PControl is by default listening on localhost:7650"
-msgstr ""
+msgstr "I2PControl por defecto está escuchando en localhost:7650"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:14
 msgid "API, version 1."
@@ -9246,7 +2618,7 @@ msgstr "API, versión 1."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:15
 msgid "Parameters are only provided in a named way (maps)."
-msgstr ""
+msgstr "Los parámetros sólo se proporcionan a través del nombre (mapas)."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:19
 msgid "JSON-RPC 2 format"
@@ -9262,7 +2634,7 @@ msgstr "Formato JSON-RPC 2"
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:137
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:154
 msgid "Request:"
-msgstr ""
+msgstr "Petición:"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:23
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:32
@@ -9274,15 +2646,15 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:145
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:169
 msgid "Response:"
-msgstr ""
+msgstr "Respuesta:"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:26
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:28
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:29
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:33
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:34
-#: i2p2www/pages/site/docs/protocol/i2cp.html:99
-#: i2p2www/pages/site/docs/protocol/i2cp.html:442
+#: i2p2www/pages/site/docs/protocol/i2cp.html:107
+#: i2p2www/pages/site/docs/protocol/i2cp.html:450
 #: i2p2www/pages/site/docs/spec/common-structures.html:16
 #: i2p2www/pages/site/docs/spec/common-structures.html:26
 #: i2p2www/pages/site/docs/spec/common-structures.html:37
@@ -9298,12 +2670,12 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/common-structures.html:162
 #: i2p2www/pages/site/docs/spec/common-structures.html:174
 #: i2p2www/pages/site/docs/spec/common-structures.html:227
-#: i2p2www/pages/site/docs/spec/common-structures.html:294
-#: i2p2www/pages/site/docs/spec/common-structures.html:343
-#: i2p2www/pages/site/docs/spec/common-structures.html:387
-#: i2p2www/pages/site/docs/spec/common-structures.html:432
-#: i2p2www/pages/site/docs/spec/common-structures.html:569
-#: i2p2www/pages/site/docs/spec/common-structures.html:625
+#: i2p2www/pages/site/docs/spec/common-structures.html:310
+#: i2p2www/pages/site/docs/spec/common-structures.html:359
+#: i2p2www/pages/site/docs/spec/common-structures.html:411
+#: i2p2www/pages/site/docs/spec/common-structures.html:456
+#: i2p2www/pages/site/docs/spec/common-structures.html:593
+#: i2p2www/pages/site/docs/spec/common-structures.html:655
 msgid "Description"
 msgstr "Descripción"
 
@@ -9312,40 +2684,44 @@ msgid ""
 "Token used for authenticating every request (excluding the 'Authenticate'"
 " RPC method)"
 msgstr ""
+"Muestra usada para autentificar cada petición (excluyendo el método RPC "
+"'Authenticate')"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:38
 msgid "Implemented methods"
-msgstr ""
+msgstr "Métodos implemetados"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:39
 msgid ""
 "Creates and returns an authentication token used for further "
 "communication."
 msgstr ""
+"Crea y devuelve un token de autentificación usado para comunicaciones "
+"posteriores."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:41
 msgid "The version of the I2PControl API used by the client."
-msgstr ""
+msgstr "La versión del API de I2PControl usada por el cliente."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:42
 msgid "The password used for authenticating against the remote server."
-msgstr ""
+msgstr "La contraseña usada para autentificarse en el servidor remoto."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:45
 msgid "The primary I2PControl API version implemented by the server."
-msgstr ""
+msgstr "Versión del API principal de I2PControl implementado por el servidor."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:46
 msgid "The token used for further communication."
-msgstr ""
+msgstr "La muestra usada para la posterior comunicación."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:49
 msgid "Echoes the value of the echo key, used for debugging and testing."
-msgstr ""
+msgstr "Muestra el valor de la clave eco, se usa para depuración y pruebas."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:51
 msgid "Value will be returned in response."
-msgstr ""
+msgstr "Un valor será devuelto como respuesta."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:52
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:62
@@ -9356,16 +2732,20 @@ msgid ""
 "Token used for authenticating the client. Is provided by the server via "
 "the 'Authenticate' RPC method."
 msgstr ""
+"Token usado para autentificar el cliente. Es provisto por el servidor a "
+"través del método RPC 'Authenticate'"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:55
 msgid "Value of the key 'echo' in the request."
-msgstr ""
+msgstr "Valor de la clave 'echo', clave eco, en la petición."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:58
 msgid ""
 "Fetches rateStat from router statManager. Creates stat if not already "
 "created."
 msgstr ""
+"Obtiene el rateStat del StatManager del ruter. Crear el stat si no ha "
+"sido creado ya."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:60
 #, python-format
@@ -9373,55 +2753,65 @@ msgid ""
 "Determines which rateStat to fetch, see ratestats."
 msgstr ""
+"Determina que rateStat debe obtenerse, vea ratestats."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:61
 msgid "Determines which period a stat is fetched for. Measured in ms."
-msgstr ""
+msgstr "Determina para qué periodo de tiempo se obtendrá el stat. Se mide en ms."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:65
 msgid "Returns the average value for the reuested rateStat and period."
-msgstr ""
+msgstr "Devuelve el valor medio del periodo y del rateStat requerido."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:68
 msgid "Manages I2PControl. Ports, passwords and the like."
-msgstr ""
+msgstr "Administra I2PControl, Puertos, contraseñas y cosas de ese tipo."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:70
 msgid ""
 "Sets a new listen address for I2PControl (only 127.0.0.1 and 0.0.0.0 are "
 "implemented in I2PControl currently)."
 msgstr ""
+"Cambia la dirección donde escucha I2PControl (sólo se han implementado "
+"127.0.0.1 y 0.0.0.0 para I2PControl hasta ahora)."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:71
 msgid ""
 "Sets a new password for I2PControl, all Authentication tokens will be "
 "revoked."
 msgstr ""
+"Cambia la contraseña para I2PControl, todos los tokens de autentificación"
+" serán revocados."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:72
 msgid "Switches which port I2PControl will listen for connections on."
-msgstr ""
+msgstr "Cambia el puerto en el que I2PControl escuchará por conexiones."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:76
 msgid "Returned if address was changed"
-msgstr ""
+msgstr "Devuelto si la dirección fue cambiada"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:77
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:78
 msgid "Returned if setting was changed"
-msgstr ""
+msgstr "Devuelto si la configuración fue cambiada"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:79
 msgid "Returns true if any changes were made."
-msgstr ""
+msgstr "Devuelve verdadero si se hizo algún cambio."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:80
 msgid "Returns true if any changes requiring a restart to take effect were made."
 msgstr ""
+"Devuelve verdadero si se hizo algún cambio que necesite un reinicio para "
+"tener efecto."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:83
 msgid "Fetches basic information about the I2P router. Uptime, version etc."
 msgstr ""
+"Obtiene información básica sobre el ruter I2P. Tiempo encendido, versión,"
+" etc."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:102
 msgid "What the status of the router is."
@@ -9429,65 +2819,67 @@ msgstr "cuál es el estado del router."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:103
 msgid "What the uptime of the router is in ms."
-msgstr ""
+msgstr "Cuánto tiempo lleva encendido el ruter en ms."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:104
 msgid "What version of I2P the router is running."
-msgstr ""
+msgstr "Qué versión de I2P está ejecutando el ruter."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:105
 msgid "The 1 second average inbound bandwidth in Bps."
-msgstr ""
+msgstr "Media del ancho de banda de entrada durante 1 segundo, en Bps."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:106
 msgid "The 15 second average inbound bandwidth in Bps."
-msgstr ""
+msgstr "Media del ancho de banda de entrada durante 15 segundos, en Bps. "
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:107
 msgid "The 1 second average outbound bandwidth in Bps."
-msgstr ""
+msgstr "Media del ancho de banda de salida durante 1 segundo, en Bps."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:108
 msgid "The 15 second average outbound bandwidth in Bps."
-msgstr ""
+msgstr "Media del ancho de banda de salida durante 15 segundos, en Bps. "
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:109
 msgid "What the current network status is. According to the below enum:"
-msgstr ""
+msgstr "Cuál es el estado actual de la red. De acuerdo con la lista:"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:128
 msgid "How many tunnels on the I2P net are we participating in."
-msgstr ""
+msgstr "En cuántos túneles estamos participando en la red I2p."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:129
 msgid "How many peers have we communicated with recently."
-msgstr ""
+msgstr "Con cuántos túneles nos hemos comunicado recientemente."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:130
 msgid "How many peers are considered 'fast'."
-msgstr ""
+msgstr "Cuántos pares se consideran como 'rápidos'."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:131
 msgid "How many peers are considered 'high capacity'."
-msgstr ""
+msgstr "Cuántos pares se consideran de 'alta capacidad'"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:132
 msgid "Is the router reseeding hosts to its NetDB?"
-msgstr ""
+msgstr "¿Está el ruter resembrando servidores a su NetDB?"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:133
 msgid "How many peers are known to us (listed in our NetDB)."
-msgstr ""
+msgstr "Cuántos pares conocemos (listados en nuestra NetDB)."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:136
 msgid "Manages I2P router restart/shutdown."
-msgstr ""
+msgstr "Maneja el arrancado/apagado del ruter I2P."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:138
 msgid ""
 "Initiates a router reseed, fetching peers into our NetDB from a remote "
 "host."
 msgstr ""
+"Inicia el resembrado de un ruter, obteniendo los pares para nuestra NetDB"
+" desde un ordenador remoto."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:139
 msgid "Restarts the router."
@@ -9498,6 +2890,8 @@ msgid ""
 "Restarts the router gracefully (waits for participating tunnels to "
 "expire)."
 msgstr ""
+"Reinicia el ruter con cuidado (espera a que expiren los túneles "
+"participantes)."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:141
 msgid "Shuts down the router."
@@ -9508,98 +2902,126 @@ msgid ""
 "Shuts down the router gracefully (waits for participating tunnels to "
 "expire)."
 msgstr ""
+"Apaga el ruter con cuidado (espera a que expiren los túneles "
+"participantes)."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:146
 msgid "If requested, verifies that a reseed has been initiated."
-msgstr ""
+msgstr "Si se ha requerido, verifica que el resembrado ha sido iniciado."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:147
 msgid "If requested, verifies that a restart has been initiated."
-msgstr ""
+msgstr "Si se ha requerido, verifica que el reinicio ha sido iniciado."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:148
 msgid "If requested, verifies that a graceful restart has been initiated."
-msgstr ""
+msgstr "Si se ha requerido, verifica que el reinicio con cuidado ha sido iniciado."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:149
 msgid "If requested, verifies that a shutdown has been initiated"
-msgstr ""
+msgstr "Si se ha requerido, verifica que el apagado ha sido iniciado."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:150
 msgid "If requested, verifies that a graceful shutdown has been initiated"
-msgstr ""
+msgstr "Si se ha requerido, verifica que el apagado con cuidado ha sido iniciado."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:153
 msgid "Fetches or sets various network related settings. Ports, addresses etc."
 msgstr ""
+"Obtiene un conjunto de configuraciones relacionadas con la red. Puertos, "
+"direcciones, etc."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:155
 msgid ""
 "What port is used for the TCP transport. If null is submitted, current "
 "setting will be returned."
 msgstr ""
+"Qué puerto es usado para el transporte TCP. Si se ha enviado null, se "
+"devolverá la configuración actual."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:156
 msgid ""
 "What hostname is used for the TCP transport. If null is submitted, "
 "current setting will be returned."
 msgstr ""
+"Qué nombre de dominio es usado para el transporte TCP. Si se ha enviado "
+"null, se devolverá la configuración actual."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:157
 msgid ""
 "Use automatically detected ip for TCP transport. If null is submitted, "
 "current setting will be returned."
 msgstr ""
+"Usar la ip detectada automáticamente para el transporte TCP . Si se ha "
+"enciado null, se devolverá la configuración actual."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:158
 msgid ""
 "What port is used for the UDP transport. If null is submitted, current "
 "setting will be returned."
 msgstr ""
+"Qué puerto es usado para el transporte UDP. Si se ha enviado null, se "
+"devolverá la configuración actual."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:159
 msgid ""
 "What hostname is used for the UDP transport. If null is submitted, "
 "current setting will be returned."
 msgstr ""
+"Qué nombre de dominio es usado para el transporte UDP. Si se ha enviado "
+"null, se devolverá la configuración actual."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:160
 msgid ""
 "Which methods should be used for detecting the ip address of the UDP "
 "transport. If null is submitted, current setting will be returned."
 msgstr ""
+"Qué métodos deben susarse para detectar la dirección ip del transporte "
+"UDP. Si se ha enviado null, se devolverá la configuración actual."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:161
 msgid "What ip has been detected by the UDP transport."
-msgstr ""
+msgstr "Qué ip ha sido detectada para el transporte UDP."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:162
 msgid "Is UPnP enabled. If null is submitted, current setting will be returned."
 msgstr ""
+"Está UPnP activo. Si se ha enviado null, se devolverá la configuración "
+"actual."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:163
 msgid ""
 "How many percent of bandwidth is usable for participating tunnels. If "
 "null is submitted, current setting will be returned."
 msgstr ""
+"Qué tanto por ciento del ancho de banda es utilizable para los túneles "
+"participantes. Si se ha enviado null, se devolverá la configuración "
+"actual."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:164
 msgid ""
 "How many KB/s of inbound bandwidth is allowed. If null is submitted, "
 "current setting will be returned."
 msgstr ""
+"Cuántos KB/s se permiten para el ancho de banda entrante. Si se ha "
+"enviado null, se devolverá la configuración actual."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:165
 msgid ""
 "How many KB/s of outbound bandwidth is allowed. If null is submitted, "
 "current setting will be returned."
 msgstr ""
+"Cuántos KB/s se permiten para el ancho de banda de salida. Si se ha "
+"enviado null, se devolverá la configuración actual."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:166
 msgid ""
 "Is laptop mode enabled (change router identity and UDP port when IP "
 "changes ). If null is submitted, current setting will be returned."
 msgstr ""
+"Si está el modo laptop activado (el cambio de la identidad del ruter "
+"cuando cambia la IP). Si se ha enviado null, se devolverá la "
+"configuración actual."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:167
 msgid ""
@@ -9607,76 +3029,96 @@ msgid ""
 "the 'Authenticate' RPC method. If null is submitted, current setting will"
 " be returned."
 msgstr ""
+"El identificador (`token`) usado para la autentificación del cliente, es "
+"proporcionado por el servidor a través del método 'Authenticate' "
+"(autentificar) de RPC. Si se envía vacío ('null'), se devolverá el valor "
+"de configuración actual."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:170
 msgid "If requested, returns the port used for the TCP transport."
-msgstr ""
+msgstr "Si se solicita, devuelve el puerto usado para el transporte TCP."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:171
 msgid "If requested, returns the hostname used for the TCP transport."
 msgstr ""
+"Si se solicita, devuelve el nombre del servidor usado para el transporte "
+"TCP."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:172
 msgid ""
 "If requested, returns the method used for automatically detecting ip for "
 "the TCP transport."
 msgstr ""
+"Si se solicita, devuelve el método usado para detectar automáticamente la"
+" IP para el transporte TCP."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:173
 msgid "If requested, returns the port used for the UDP transport."
-msgstr ""
+msgstr "Si se solicita, devuelve el puerto usado para el transporte UDP."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:174
 msgid "If requested, returns the hostname used for the UDP transport."
 msgstr ""
+"Si se solicita, devuelve el nombre del servidor usado para el transporte "
+"UDP."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:175
 msgid ""
 "If requested, returns methods used for detecting the ip address of the "
 "UDP transport."
 msgstr ""
+"Si se solicita, devuelve los métodos usados para detectar la dirección IP"
+" del transporte UDP."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:176
 msgid "If requested, returns what ip has been detected by the UDP transport."
 msgstr ""
+"Si se solicita, devuelve la IP que ha sido detectada por el transporte "
+"UDP."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:177
 msgid "If requested, returns the UPNP setting."
-msgstr ""
+msgstr "Si se solicita, devuelve el valor de la configuración UPnP."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:178
 msgid ""
 "If requested, returns how many percent of bandwidth is usable for "
 "participating tunnels."
 msgstr ""
+"Si se solicita, devuelve el porcentaje de ancho de banda disponible para "
+"los túneles participantes."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:179
 msgid "If requested, returns how many KB/s of inbound bandwidth is allowed."
 msgstr ""
+"Si se solicita, devuelve el número de KB/s de ancho de banda de entrada "
+"que están permitidos."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:180
 msgid "If requested, returns how many KB/s of outbound bandwidth is allowed."
 msgstr ""
+"Si se solicita, devuelve el número de KB/s de ancho de banda de salida "
+"que están permitidos."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:181
 msgid "If requested, returns the laptop mode."
-msgstr ""
+msgstr "Si se solicita, devuelve el valor del modo laptop (portátil)."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:182
 msgid "Have the provided settings been saved."
-msgstr ""
+msgstr "Han sido guardadas las configuraciones proporcionadas."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:183
 msgid "Is a restart needed for the new settings to be used."
-msgstr ""
+msgstr "Se necesita un reinicio para que las nuevas configuraciones se usen."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:186
 msgid "denotes an optional value."
-msgstr ""
+msgstr "denota un valor opcional."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:187
 msgid "denotes a possibly occuring return value"
-msgstr ""
+msgstr "denota un valor de retorno que posiblemente ocurra"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:189
 msgid "Error codes"
@@ -9684,11 +3126,11 @@ msgstr "Códigos de error"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:190
 msgid "Standard JSON-RPC2 error codes."
-msgstr ""
+msgstr "Códigos de error estándar JSON-RPC2."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:191
 msgid "JSON parse error."
-msgstr ""
+msgstr "Error de procesado JSON."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:192
 msgid "Invalid request."
@@ -9699,40 +3141,48 @@ msgid "Method not found."
 msgstr "Método no encontrado."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:194
+msgid "Invalid parameters."
+msgstr "Parámetros no válidos."
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:195
 msgid "Internal error."
 msgstr "Error interno."
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:196
-msgid "I2PControl specific error codes."
-msgstr ""
-
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:197
-msgid "Invalid password provided."
-msgstr ""
+msgid "I2PControl specific error codes."
+msgstr "Códigos de error específicos de I2PControl."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:198
-msgid "No authentication token presented."
-msgstr ""
+msgid "Invalid password provided."
+msgstr "Se proporcionó una contraseña no válida."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:199
-msgid "Authentication token doesn't exist."
-msgstr ""
+msgid "No authentication token presented."
+msgstr "No se presentó la credencial (`token`) de autentificación."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:200
-msgid "The provided authentication token was expired and will be removed."
-msgstr ""
+msgid "Authentication token doesn't exist."
+msgstr "La credencial (`token`) de autentificación no existe"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:201
+msgid "The provided authentication token was expired and will be removed."
+msgstr "La credencial (`token`) de identificación ha expirado y será eliminada."
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
 msgid ""
 "The version of the I2PControl API used wasn't specified, but is required "
 "to be specified."
 msgstr ""
+"La versión de la API I2PControl usada no fue especificada, pero se "
+"requiere que sea especificada."
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:203
 msgid ""
 "The version of the I2PControl API specified is not supported by "
 "I2PControl."
 msgstr ""
+"La versión de la API I2PControl especificada no está soportada por "
+"I2PControl."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:13
 #, python-format
@@ -9753,6 +3203,21 @@ msgid ""
 "localhost:7657/i2ptunnel/."
 msgstr ""
+"I2PTunnel es una herramienta para intermediar con, y proveer servicios a\n"
+"I2P. El destino de un I2PTunnel puede ser definido usando un nombre de servidor \n"
+"Base32, o una clave de destino completa"
+" de 516-bytes. Un I2PTunnel establecido estará disponible sobre \n"
+"su máquina cliente en localhost:puerto Si desea proporcionar un servicio"
+" \n"
+"sobre la red I2P, simplemente cree un I2PTunnel hasta la dirección "
+"IP:puerto \n"
+"apropiada. Se generarará una clave de destino de 516-bytes "
+"correspondiente \n"
+"para el servicio, y se hará disponible a través de I2P. Una interfaz web "
+"para \n"
+"la administración del I2PTunnel está disponible en localhost:7657/i2ptunnel/."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:25
 msgid "Default Services"
@@ -9760,7 +3225,7 @@ msgstr "Servicios predeterminados"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:26
 msgid "Server tunnels"
-msgstr ""
+msgstr "Túneles de servidor"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:28
 msgid ""
@@ -9769,10 +3234,15 @@ msgid ""
 "and quick hosting on I2P.\n"
 "
            The document root is:"
 msgstr ""
+"Servidor web I2P - Un túnel apuntando a un servidor web Jetty se \n"
+"ejecuta en localhost:7658 para un "
+"hospedaje conveniente \n"
+"y rápido en I2P.\n"
+"
            El documento raíz es: "
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:36
 msgid "Client tunnels"
-msgstr ""
+msgstr "Túneles de cliente"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:38
 msgid ""
@@ -9781,19 +3251,24 @@ msgid ""
 "Browsing internet through I2P uses a random proxy specified by the "
 "\"Outproxies:\" option."
 msgstr ""
+"Un proxy HTTP usado para navegar por I2P y la Internet regular de forma "
+"anónima \n"
+"a través de I2P. La navegación por Internet a través de I2P usa un proxy "
+"aleatorio\n"
+"especificado por la opción \"Outproxies:\" (proxys de salida)."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:42
 msgid "An IRC tunnel to the default anonymous IRC network, Irc2P."
-msgstr ""
+msgstr "Un túnel IRC hasta la red IRC anónima por defecto, Irc2P."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:43
 #, python-format
 msgid ""
-"The anonymous monotone"
-"\n"
+"The anonymous monotone\n"
 "sourcecode repository for I2P"
 msgstr ""
+"El repositorio de código fuente monotone\n"
+"anónimo para I2P"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:47
 #, python-format
@@ -9801,6 +3276,8 @@ msgid ""
 "A SMTP service provided by postman at %(postman)s"
 msgstr ""
+"Un servicio SMTP proporcionado por postman en %(postman)s"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:50
 #, python-format
@@ -9808,10 +3285,12 @@ msgid ""
 "The accompanying POP sevice of postman at %(postman)s"
 msgstr ""
+"El servicio POP acompañante de postman en %(postman)s"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:55
 msgid "Client Modes"
-msgstr ""
+msgstr "Modos de cliente"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:56
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:138
@@ -9825,6 +3304,9 @@ msgid ""
 "The tunnel is directed to a random host from the comma seperated (\", \")"
 " list of destinations."
 msgstr ""
+"Abre un puerto TCP local que conecta con un servicio (como HTTP, FTP o \n"
+"SMTP) en un destino dentro de I2P. El túnel es dirigido a un servidor \n"
+"aleatorio desde la lista de destinos separados por comas (\", \")."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:63
 msgid ""
@@ -9833,6 +3315,12 @@ msgid ""
 "in a HTTP request. Supports proxying onto internet if an outproxy is "
 "provided. Strips HTTP connections of the following headers:"
 msgstr ""
+"Un túnel de cliente-HTTP. El túnel conecta con el destino especificado "
+"por la \n"
+"URL en una petición HTTP. Soporta proxificación en Internet si se "
+"proporciona \n"
+"un proxy externo (`outproxy`). Desnuda las conexiones HTTP de las \n"
+"siguientes cabeceras: "
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:68
 msgid ""
@@ -9840,18 +3328,26 @@ msgid ""
 " and Accept-Ranges             as they vary greatly between browsers and can be "
 "used as an identifier."
 msgstr ""
+"Accept, Accept-Charset, Accept-Encoding, Accept-Language y Accept-"
+"Ranges ya que varían bastante entre navegadores y pueden usarse como "
+"identificador."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:76
 msgid ""
 "HTTP client/server tunnels are via I2Ptunnel force-enabling compression "
 "via the following http headers:"
 msgstr ""
+"Los túneles HTTP de cliente/servidor vía I2PTunnel, están habilitando \n"
+"a la fuerza la compresión mediante las siguientes cabeceras HTTP:"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:83
 msgid ""
 "Depending on if the tunnel is using an outproxy or not it will append the"
 " following User-Agent:"
 msgstr ""
+"Dependiendo de si el túnel está usando un proxy externo (`outproxy`) o "
+"no, \n"
+"adherirá el siguiente Agente de Usuario (`User-Agent`):"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:87
 msgid "Outproxy:"
@@ -9859,7 +3355,7 @@ msgstr "Proxy de salida:"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:88
 msgid "Internal I2P use:"
-msgstr ""
+msgstr "Uso interno de I2P:"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:93
 msgid ""
@@ -9868,14 +3364,19 @@ msgid ""
 "list of destinations. Only a whitelisted subset of IRC commands are "
 "allowed due to anonymity concerns."
 msgstr ""
+"Crea una conexión a un servidor IRC aleatorio especificado por una lista "
+"de \n"
+"destinos separados por coma (\", \"). Sólo un subconjunto de comandos IRC"
+" \n"
+"de la lista blanca están permitidos debido a cuestiones de anonimato."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:97
 msgid "Whitelist:"
-msgstr ""
+msgstr "Lista blanca:"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:112
 msgid "Enables using the I2P router as a SOCKS proxy."
-msgstr ""
+msgstr "Habilita el uso del router I2P como un proxy SOCKS."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:117
 msgid ""
@@ -9883,12 +3384,18 @@ msgid ""
 "specified by\n"
 "IRC client mode."
 msgstr ""
+"Habilita el uso de un router I2P como un proxy SOCKS con la lista blanca"
+" \n"
+"de comandos especificada por el modo cliente del IRC."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:123
 msgid ""
 "Creates a HTTP tunnel and uses the HTTP request method \"CONNECT\" \n"
 "to build a TCP tunnel that usually is used for SSL and HTTPS."
 msgstr ""
+"Crea un túnel HTTP y usa el método de petición HTTP \"CONNECT\" para \n"
+"construir un túnel TCP que normalmente se usa para SSL y HTTPS."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:129
 msgid ""
@@ -9896,14 +3403,19 @@ msgid ""
 "client tunnel will \n"
 "subscribe to a streamr server tunnel."
 msgstr ""
+"Crea un servidor-UDP adosado a un I2PTunnel de cliente `Streamr`. El "
+"túnel \n"
+"del cliente streamr se suscribirá a un túnel de servidor streamr."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:137
 msgid "Server Modes"
-msgstr ""
+msgstr "Modos de servidor"
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:139
 msgid "Creates a destination to a local ip:port with an open TCP port."
 msgstr ""
+"Crea un destino hacia una dirección IP:puerto local con un puerto TCP "
+"abierto."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:144
 msgid ""
@@ -9912,6 +3424,11 @@ msgid ""
 "Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in"
 " such a request."
 msgstr ""
+"Crea un destino a un servidor HTTP local IP:puerto Soporta gzip para las"
+" \n"
+"peticiones con\n"
+"`Accept-encoding: x-i2p-gzip`, responde con `Content-encoding: x-i2p-"
+"gzip` a tal petición."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:150
 msgid ""
@@ -9921,6 +3438,13 @@ msgid ""
 " client-type\n"
 "requests, or loopback-testing an eepsite as a diagnostic tool."
 msgstr ""
+"Funciona tanto como un I2PTunnel de servidor HTTP, como un I2PTunnel \n"
+"de cliente HTTP sin capacidades de proxificación externa (`outproxying`)."
+" \n"
+"Una aplicación de ejemplo sería una aplicación web que realice peticiones"
+" \n"
+"tipo-cliente, o que realice pruebas-loopback a un eepsite a modo de \n"
+"herramienta de diagnóstico."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:157
 msgid ""
@@ -9928,21 +3452,27 @@ msgid ""
 "and passes \n"
 "the clients destination key as a hostname to the IRC-server."
 msgstr ""
+"Crea un destino que filtra la secuencia de registro de un cliente y pasa "
+"la \n"
+"clave de destino de los clientes como un nombre de servidor al servidor-"
+"IRC."
 
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:163
 msgid ""
 "A UDP-client that connects to a media server is created. The UDP-Client "
 "is coupled with a Streamr server I2PTunnel."
 msgstr ""
+"Se crea un cliente-UDP que conecta a los servidores de medios. El \n"
+"cliente-UDP está emparejado con el I2PTunnel de servidor Streamr."
 
 #: i2p2www/pages/site/docs/api/ministreaming.html:2
 #: i2p2www/pages/site/docs/api/ministreaming.html:17
 msgid "Ministreaming Library"
-msgstr ""
+msgstr "Librería ministreaming"
 
 #: i2p2www/pages/site/docs/api/ministreaming.html:5
 msgid "Note"
-msgstr ""
+msgstr "Nota"
 
 #: i2p2www/pages/site/docs/api/ministreaming.html:7
 #, python-format
@@ -9958,6 +3488,17 @@ msgid ""
 "Obsolete ministreaming classes and methods are clearly marked as "
 "deprecated in the Javadocs."
 msgstr ""
+"La librería ministreaming ha sido mejorada y extendida por la librería streaming\"completa\". Ministreaming "
+"está \n"
+"desechada y es incompatible con las aplicaciones actuales. La siguiente \n"
+"documentación es antigua. Observe también que esa libreria streaming \n"
+"extiende la ministreaming en el mismo paquete Java "
+"(net.i2p.client.streaming), \n"
+"así que la documentation de la API actual "
+"contiene \n"
+"ambas. Las obsoletas clases y métodos de ministreaming están claramente \n"
+"marcados como desechados en los Javadocs."
 
 #: i2p2www/pages/site/docs/api/ministreaming.html:19
 #, python-format
@@ -9977,6 +3518,18 @@ msgid ""
 " and to\n"
 "allow alternative optimized implementations."
 msgstr ""
+"\n"
+"La librería ministreaming es una capa encima del núcleo de I2CP \n"
+"que permite flujos (`streams`) confiables, ordenados y autentificados de "
+"mensajes para operar a través de una capa de mensajes no confiable, \n"
+"desordenada y no autentificada. Justo como la relación de TCP hacia IP,\n"
+"esta funcionalidad streaming tiene un completo conjunto de renuncias y "
+"optimizaciones disponibles, pero en lugar de embeber esta funcionalidad "
+"en el código base de I2P, ha sido desgajado en su propia \n"
+"librería, tanto para mantener separadas las complejidades propias de TCP"
+" \n"
+"como para permitir implementaciones optimizadas alternativas."
 
 #: i2p2www/pages/site/docs/api/ministreaming.html:30
 #, python-format
@@ -10004,6 +3557,28 @@ msgid ""
 "on average twice the time it takes to send a message before sending "
 "another."
 msgstr ""
+"La librería ministream fue escrita por mihi como parte de su aplicación \n"
+"I2PTunnel y después fue desgajada y \n"
+"publicada bajo la licencia BSD. Se la llama librería \"mini\"streaming \n"
+"porque hace algunas simplificaciones en la implementación, mientras una \n"
+"librería streaming más robusta podría seguir siendo optimizada para "
+"operar \n"
+"sobre I2P. Los dos principales problemas con la librería ministreaming "
+"son \n"
+"su uso del tradicional protocolo TCP de establecimiento en dos fases, y "
+"el \n"
+"actual tamaño fijo de ventana (TCP) de 1. El problema del establecimiento"
+" \n"
+"es menor para streams de vida larga, pero para los de corta, tales como "
+"las \n"
+"peticiones HTTP rápidas, el impacto puede ser significativo. Y en cuanto\n"
+"al tamaño de ventana (TCP), la librería ministreaming no mantiene "
+"identificador \n"
+"u orden alguno (o no incluye ACK o SACK de nivel aplicación alguno) junto"
+" \n"
+"con los mensajes enviados. así que, de media, debe esperar el doble de \n"
+"tiempo del que tarda en enviar un mensaje antes de enviar otro."
 
 #: i2p2www/pages/site/docs/api/ministreaming.html:45
 #, python-format
@@ -10020,6 +3595,19 @@ msgid ""
 "through\n"
 "SAM's streaming support."
 msgstr ""
+"Incluso con esos problemas, la librería ministreaming se comporta "
+"bastante \n"
+"bien en muchas situaciones, y su API es tanto \n"
+"bastante simple como capaz de mantenerse invariante mientras se "
+"introducen \n"
+"diferentes implementaciones streaming. La librería se despliega en su "
+"propio \n"
+"`ministreaming.jar`. Los desarrolladores en Java a los que les gustaría "
+"usarla \n"
+"pueden acceder directamente a la API, mientras que los desarrolladores en"
+" \n"
+"otros lenguajes pueden usarla a través del soporte streaming de SAM."
 
 #: i2p2www/pages/site/docs/api/socks.html:4
 msgid "SOCKS and SOCKS proxies"
@@ -10034,6 +3622,12 @@ msgid ""
 "Both shared-clients and non-shared are supported.\n"
 "There is no SOCKS outproxy so it is of limited use."
 msgstr ""
+"\n"
+"El proxy SOCKS está funcionando desde la versión `0.7.1`. SOCKS 4/4a/5 \n"
+"están soportados. Habilite SOCKS mediante la creación de un túnel de \n"
+"cliente SOCKS en I2PTunnel. Ambos clientes-compartidos están soportados."
+" \n"
+"No hay proxy externo (`outproxy`) SOCKS, así que es de uso limitado."
 
 #: i2p2www/pages/site/docs/api/socks.html:12
 #, python-format
@@ -10041,6 +3635,8 @@ msgid ""
 "\n"
 "As it says on the FAQ:"
 msgstr ""
+"\n"
+"Como lo dice en las FAQ: "
 
 #: i2p2www/pages/site/docs/api/socks.html:15
 msgid ""
@@ -10054,10 +3650,22 @@ msgid ""
 "\n"
 "extremely dangerous."
 msgstr ""
+"Muchas aplicaciones filtran información sensible que podría identificarle"
+" en \n"
+"Internet. I2P sólo filtra la conexión de datos, pero si el programa que "
+"usted \n"
+"intenta ejecutar envía esta información como contenido, I2P no tiene "
+"manera \n"
+"de proteger su anonimato. Por ejemplo, algunas aplicaciones de correo \n"
+"enviarán la dirección IP de la máquina sobre la que estén ejecutando el \n"
+"servidor de correo. No hay forma de I2P filtre esto, por lo que usar I2P "
+"para \n"
+"socksificar ('socksify') aplicaciones existentes es posible, pero \n"
+"extremadamente peligroso."
 
 #: i2p2www/pages/site/docs/api/socks.html:25
 msgid "And quoting from a 2005 email:"
-msgstr ""
+msgstr "Y citando a un email de 2005: "
 
 #: i2p2www/pages/site/docs/api/socks.html:28
 msgid ""
@@ -10067,6 +3675,13 @@ msgid ""
 "developers of anonymity and security software to have the safety of\n"
 "our end users foremost in our minds."
 msgstr ""
+"... hay una razón por la que ambos, los humanos y otros, hemos construido"
+" \n"
+"y abandonado los proxys SOCKS. Rebotar el tráfico arbitrario es "
+"simplemente \n"
+"bastante inseguro, y nos corresponde a nosotros, como desarrolladores \n"
+"de software de anonimato y seguridad, tener la seguridad de nuestros \n"
+"usuarios finales entre nuestras prioridades."
 
 #: i2p2www/pages/site/docs/api/socks.html:36
 msgid ""
@@ -10080,6 +3695,20 @@ msgid ""
 "anonymous environments is no small feat, orders of magnitude more\n"
 "work that simply using the existing I2P APIs."
 msgstr ""
+"Esperar que simplemente podamos adherir un cliente arbitrario sobre I2P \n"
+"sin auditar la seguridad y anonimato tanto de su comportamiento como de "
+"sus protocolos expuestos, es ingenuo. Casi cualquier aplicación y "
+"protocolo \n"
+"viola el anonimato, a menos que fuera específicamente diseñado para lo \n"
+"contrario, e incluso entonces la mayoría de aquellos también lo hace.\n"
+"Esa es la realidad. Los usuarios finales están mejor servidos con "
+"sistemas \n"
+"diseñados para el anonimato y la seguridad. Modificar sistemas existentes"
+" \n"
+"para trabajar en entornos anónimos no es una cuestión banal, supone "
+"varios órdenes de magnitud más de trabajo que simplemente usar las APIs"
+" \n"
+"existentes de I2P."
 
 #: i2p2www/pages/site/docs/api/socks.html:48
 msgid ""
@@ -10090,6 +3719,12 @@ msgid ""
 "UDP support is stubbed out but not working yet.\n"
 "Outproxy selection by port number is stubbed out."
 msgstr ""
+"El proxy SOCKS soporta los nombres de las libretas de direcciones \n"
+"estándar, pero no los destinos Base64. Los hashes Base32 deberían \n"
+"funcionar desde la versión `0.7`. Sólo soporta conexiones salientes, es \n"
+"decir, se erradicó el soporte para un I2PTunnel de cliente. Se forzó la "
+"inclusión del soporte UDP, pero no funciona aún. Se forzó la inclusión de"
+" la selección mediante número de puerto de proxy externo (`outproxy`)."
 
 #: i2p2www/pages/site/docs/api/socks.html:57
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:281
@@ -10102,22 +3737,20 @@ msgid ""
 "The notes for Meeting 81 and\n"
 "Meeting 82 in March 2004."
 msgstr ""
+"Las notas para la Reunión 81 y la Reunión 82 en marzo de 2004."
 
 #: i2p2www/pages/site/docs/api/socks.html:69
 msgid "If You Do Get Something Working"
-msgstr ""
+msgstr "Si consigue que algo funcione"
 
 #: i2p2www/pages/site/docs/api/socks.html:70
 msgid ""
 "Please let us know. And please provide substantial warnings about the\n"
 "risks of socks proxies."
 msgstr ""
-
-#: i2p2www/pages/site/docs/api/streaming.html:3
-#: i2p2www/pages/site/docs/protocol/i2cp.html:3
-#: i2p2www/pages/site/docs/spec/streaming.html:3
-msgid "November 2012"
-msgstr "Noviembre de 2012"
+"Por favor, permítanos saberlo. Y, por favor, proporcione advertencias \n"
+"sustanciales acerca de los riesgos de los proxys SOCKS."
 
 #: i2p2www/pages/site/docs/api/streaming.html:8
 #, python-format
@@ -10130,6 +3763,15 @@ msgid ""
 "The other end-to-end transport library for client communication is the\n"
 "datagram library."
 msgstr ""
+"La librería streaming técnicamente es parte de la capa de \"aplicación\","
+" ya \n"
+"que no es una función central del router. En la práctica, sin embargo, "
+"proporciona una función vital para casi todas las aplicaciones I2P \n"
+"existentes, proveyéndolas de flujos (`streams`) tipo-TCP sobre I2P, y "
+"permitiendo que las aplicaciones existentes sean fácilmente portadas \n"
+"a I2P. La otra librería de transporte extremo-a-extremo para la "
+"comunicación \n"
+"de clientes, es la librería datagram."
 
 #: i2p2www/pages/site/docs/api/streaming.html:18
 #, python-format
@@ -10148,6 +3790,18 @@ msgid ""
 " and to\n"
 "allow alternative optimized implementations."
 msgstr ""
+"La librería de streaming es una capa sobre el núcleo del API I2CP que permite que flujos (`streams`) de "
+"mensajes \n"
+"confiables, ordenados y autentificados, operen a través de una capa de \n"
+"mensaje no confiable, desordenada y no autentificada. Justo como la \n"
+"relación TCP hacia IP, esta funcionalidad streaming tiene un conjunto \n"
+"completo de renuncias y optimizaciones disponibles, pero \n"
+"en lugar de embeber esta funcionalidad junto al código base de I2P, ha "
+"sido \n"
+"desgajado en su propia librería para mantener las complejidades propias "
+"de \n"
+"TCP aparte, y para permitir implementaciones optimizadas alternativas."
 
 #: i2p2www/pages/site/docs/api/streaming.html:29
 msgid ""
@@ -10168,6 +3822,21 @@ msgid ""
 " browser \n"
 "immediately."
 msgstr ""
+"En consideración al relativamente alto coste de los mensajes, el "
+"protocolo \n"
+"de la librería streaming para programar y entregar esos mensajes ha \n"
+"sido optimizado para permitir que los mensajes individuales pasen a \n"
+"contener tanta información como esté disponible. Por ejemplo, una pequeña"
+" \n"
+"transacción HTTP proxificada a través de la librería streaming puede ser"
+" \n"
+"completada en un sólo viaje de ida y vuelta - los primeros mensajes \n"
+"empaquetan un SYN, FIN, y la pequeña carga de la petición HTTP, y la \n"
+"respuesta empaqueta el SYN, FIN, ACK, y la carga de la respuesta HTTP. \n"
+"Aunque un ACK adicional debe ser transmitido para decirle al servidor "
+"HTTP \n"
+"que el SYN/FIN/ACK ha sido recibido, el proxy HTTP local a menudo puede \n"
+"entregar la respuesta completa de forma inmediata al navegador. "
 
 #: i2p2www/pages/site/docs/api/streaming.html:42
 msgid ""
@@ -10178,6 +3847,11 @@ msgid ""
 "(ACK,\n"
 "SYN, FIN, RST, rto calculation, etc)."
 msgstr ""
+"La librería streaming presenta mucha semejanza a una abstracción de \n"
+"TCP, con sus ventanas (de protocolo) deslizantes, algoritmos de control \n"
+"de congestión (tanto de inicio lento como de elusión de congestión), y "
+"comportamiento general del paquete (ACK, SYN, FIN, RST, cálculo RTO, "
+"etc.)."
 
 #: i2p2www/pages/site/docs/api/streaming.html:49
 msgid ""
@@ -10187,6 +3861,15 @@ msgid ""
 "It has a one-phase setup, and\n"
 "it contains a full windowing implementation."
 msgstr ""
+"La librería streaming es \n"
+"una librería robusta\n"
+"que está optimizada para operar sobre I2P.\n"
+"Tiene una instalación de fase-única, y \n"
+"contiene una implementación de ventanización (protocolo) completa."
+
+#: i2p2www/pages/site/docs/api/streaming.html:58
+msgid "API"
+msgstr "API"
 
 #: i2p2www/pages/site/docs/api/streaming.html:60
 #, python-format
@@ -10199,6 +3882,14 @@ msgid ""
 "through the\n"
 "streaming library, to be interpreted by I2CP."
 msgstr ""
+"La API de la librería streaming proporciona un paradigma de socket \n"
+"estándar a las aplicaciones Java. La API de nivel-inferior de I2CP \n"
+"está completamente escondida, exceptuando que esas aplicaciones \n"
+"pueden pasar parámetros I2CP a través de"
+" \n"
+"la librería streaming, \n"
+"para que sean interpretados por I2CP."
 
 #: i2p2www/pages/site/docs/api/streaming.html:67
 #, python-format
@@ -10216,15 +3907,27 @@ msgid ""
 "or\n"
 "receive connections with an I2PServerSocket."
 msgstr ""
+"La interfaz estándar de la librería streaming es para que la aplicación "
+"use el \n"
+"I2PSocketManagerFactory para crear un I2PSocketManager. \n"
+"La aplicación pregunta entonces al administrador de socket por una \n"
+"I2PSession, que producirá una conexión al "
+"router vía I2CP. \n"
+"La aplicación puede entonces establecer conexiones con un I2PSocket \n"
+"o recibir conexiones con un I2PServerSocket."
 
 #: i2p2www/pages/site/docs/api/streaming.html:82
 #, python-format
 msgid "Here are the full streaming library Javadocs."
 msgstr ""
+"Aquí están los Javadocs de la librería streaming "
+"completa."
 
 #: i2p2www/pages/site/docs/api/streaming.html:86
 msgid "For a good example of usage, see the i2psnark code."
-msgstr ""
+msgstr "Para ver un buen ejemplo de uso, vea el código de i2psnark."
 
 #: i2p2www/pages/site/docs/api/streaming.html:91
 msgid "Options and Defaults"
@@ -10247,6 +3950,19 @@ msgid ""
 " _i2cpPort, opts).\n"
 "Time values are in ms."
 msgstr ""
+"Las opciones y los actuales valores predeterminados están listados "
+"debajo. \n"
+"Las opciones diferencian mayúsculas/minúsculas y pueden ser \n"
+"establecidas para todo el router, para un cliente concreto, o para un \n"
+"socket individual en base a cada conexión. Muchos valores son ajustados \n"
+"para el rendimiento HTTP sobre las condiciones típicas de I2P. Otras \n"
+"aplicaciones tales como los servicios entre pares (`peer-to-peer`) son \n"
+"fuertemente animadas a que los modifiquen como sea necesario, \n"
+"configurando las opciones y pasándolas a través de la llamada a \n"
+"I2PSocketManagerFactory.createManager(_i2cpHost,"
+" _i2cpPort, opts). \n"
+"Los valores de los tiempos están en ms."
 
 #: i2p2www/pages/site/docs/api/streaming.html:103
 #, python-format
@@ -10258,6 +3974,14 @@ msgid ""
 "Also note that many options only apply to servers listening for incoming "
 "connections."
 msgstr ""
+"Observe que las APIs de capa-superior, tales como SAM, BOB, e \n"
+"I2PTunnel, pueden imponer sus propias "
+"configuraciones \n"
+"predeterminadas sobre estas configuraciones por defecto. Observe también"
+" \n"
+"que muchas opciones sólo se aplican a los servidores que están \n"
+"escuchando conexiones entrantes."
 
 #: i2p2www/pages/site/docs/api/streaming.html:110
 msgid ""
@@ -10265,16 +3989,19 @@ msgid ""
 "active socket manager or session.\n"
 "See the javadocs for details."
 msgstr ""
+"Desde la versión 0.9.1 la mayoría de las opciones, pero no todas, pueden "
+"ser cambiadas en un administrador de socket activo o sesión. \n"
+"Vea los Javadocs para más detalles."
 
 #: i2p2www/pages/site/docs/api/streaming.html:117
-#: i2p2www/pages/site/docs/protocol/i2cp.html:94
-#: i2p2www/pages/site/docs/protocol/i2cp.html:437
+#: i2p2www/pages/site/docs/protocol/i2cp.html:102
+#: i2p2www/pages/site/docs/protocol/i2cp.html:445
 msgid "Option"
 msgstr "Opción"
 
 #: i2p2www/pages/site/docs/api/streaming.html:117
-#: i2p2www/pages/site/docs/protocol/i2cp.html:98
-#: i2p2www/pages/site/docs/protocol/i2cp.html:441
+#: i2p2www/pages/site/docs/protocol/i2cp.html:106
+#: i2p2www/pages/site/docs/protocol/i2cp.html:449
 msgid "Default"
 msgstr "Valor predeterminado"
 
@@ -10284,11 +4011,11 @@ msgstr "Valor predeterminado"
 #: i2p2www/pages/site/docs/spec/common-structures.html:58
 #: i2p2www/pages/site/docs/spec/common-structures.html:203
 #: i2p2www/pages/site/docs/spec/common-structures.html:257
-#: i2p2www/pages/site/docs/spec/common-structures.html:335
-#: i2p2www/pages/site/docs/spec/common-structures.html:421
-#: i2p2www/pages/site/docs/spec/common-structures.html:529
-#: i2p2www/pages/site/docs/spec/common-structures.html:607
-#: i2p2www/pages/site/docs/spec/common-structures.html:709
+#: i2p2www/pages/site/docs/spec/common-structures.html:351
+#: i2p2www/pages/site/docs/spec/common-structures.html:445
+#: i2p2www/pages/site/docs/spec/common-structures.html:553
+#: i2p2www/pages/site/docs/spec/common-structures.html:631
+#: i2p2www/pages/site/docs/spec/common-structures.html:739
 #: i2p2www/pages/site/docs/spec/datagrams.html:30
 #: i2p2www/pages/site/docs/spec/datagrams.html:89
 msgid "Notes"
@@ -10299,36 +4026,45 @@ msgid ""
 "Comma- or space-separated list of Base64 peer Hashes used for either "
 "access list or blacklist."
 msgstr ""
+"Lista separada por comas - o espacios -  de hashes de pares (`peers`) "
+"Base64 usada bien como lista de acceso, o como lista negra."
 
 #: i2p2www/pages/site/docs/api/streaming.html:121
 #: i2p2www/pages/site/docs/api/streaming.html:127
 #: i2p2www/pages/site/docs/api/streaming.html:133
-#: i2p2www/pages/site/docs/api/streaming.html:147
-#: i2p2www/pages/site/docs/api/streaming.html:176
-#: i2p2www/pages/site/docs/api/streaming.html:184
-#: i2p2www/pages/site/docs/api/streaming.html:214
+#: i2p2www/pages/site/docs/api/streaming.html:140
+#: i2p2www/pages/site/docs/api/streaming.html:152
+#: i2p2www/pages/site/docs/api/streaming.html:163
+#: i2p2www/pages/site/docs/api/streaming.html:192
+#: i2p2www/pages/site/docs/api/streaming.html:200
 #: i2p2www/pages/site/docs/api/streaming.html:220
-#: i2p2www/pages/site/docs/api/streaming.html:226
-#: i2p2www/pages/site/docs/api/streaming.html:240
-#: i2p2www/pages/site/docs/api/streaming.html:247
-#: i2p2www/pages/site/docs/api/streaming.html:254
+#: i2p2www/pages/site/docs/api/streaming.html:237
+#: i2p2www/pages/site/docs/api/streaming.html:249
+#: i2p2www/pages/site/docs/api/streaming.html:255
+#: i2p2www/pages/site/docs/api/streaming.html:261
+#: i2p2www/pages/site/docs/api/streaming.html:275
+#: i2p2www/pages/site/docs/api/streaming.html:282
+#: i2p2www/pages/site/docs/api/streaming.html:289
+#: i2p2www/pages/site/docs/api/streaming.html:314
+#: i2p2www/pages/site/docs/api/streaming.html:321
+#: i2p2www/pages/site/docs/api/streaming.html:328
 #, python-format
 msgid "As of release %(release)s."
-msgstr ""
+msgstr "Desde la versión %(release)s."
 
 #: i2p2www/pages/site/docs/api/streaming.html:125
 msgid "Use the access list as a whitelist for incoming connections."
-msgstr ""
+msgstr "Usar la lista de acceso como lista blanca para conexiones entrantes."
 
 #: i2p2www/pages/site/docs/api/streaming.html:131
 msgid "Use the access list as a blacklist for incoming connections."
-msgstr ""
+msgstr "Usar la lista de acceso como lista negra para conexiones entrantes."
 
-#: i2p2www/pages/site/docs/api/streaming.html:137
+#: i2p2www/pages/site/docs/api/streaming.html:145
 msgid "Whether to respond to incoming pings"
-msgstr ""
+msgstr "Responder o no a los pings entrantes."
 
-#: i2p2www/pages/site/docs/api/streaming.html:141
+#: i2p2www/pages/site/docs/api/streaming.html:157
 msgid ""
 "Comma- or space-separated list of Base64 peer Hashes to be\n"
 "blacklisted for incoming connections to ALL destinations in the context.\n"
@@ -10338,14 +4074,23 @@ msgid ""
 "outside the\n"
 "router in a separate JVM and context."
 msgstr ""
+"Lista separada por comas - o espacios - de hashes de pares (`peers`) \n"
+"Base64 que sera usada como lista negra para las conexiones entrantes a \n"
+"TODOS los destinos en el contexto. Esta opción debe ser configurada en \n"
+"las propiedades contextuales, NO en el argumento createManager() de las \n"
+"opciones. Observe que establecer esto en el contexto del router no "
+"afectará \n"
+"a clientes fuera del router en una JVM y contexto aparte."
 
-#: i2p2www/pages/site/docs/api/streaming.html:151
+#: i2p2www/pages/site/docs/api/streaming.html:167
 msgid ""
 "How much transmit data (in bytes) will be accepted that hasn't been "
 "written out yet."
 msgstr ""
+"Cuántos datos de transmisión (en bytes) serán aceptados que no hayan \n"
+"sido emitidos aún."
 
-#: i2p2www/pages/site/docs/api/streaming.html:155
+#: i2p2www/pages/site/docs/api/streaming.html:171
 msgid ""
 "When we're in congestion avoidance, we grow the window size at the rate\n"
 "of 1/(windowSize*factor).  In standard TCP, window sizes are"
@@ -10353,8 +4098,14 @@ msgid ""
 "while in I2P, window sizes are in messages.\n"
 "A higher number means slower growth."
 msgstr ""
+"Cuando estamos evitando la congestión, aumentamos el tamaño de la \n"
+"ventana (protocolo) al ritmo de 1/(tamañodeventana*factor)."
+" \n"
+"En TCP estándar, los tamaños de ventana se miden en bytes, mientras que \n"
+"en I2P los tamaños de ventana se miden en mensajes. Un número más alto \n"
+"significa un crecimiento más lento."
 
-#: i2p2www/pages/site/docs/api/streaming.html:162
+#: i2p2www/pages/site/docs/api/streaming.html:178
 msgid ""
 "How long to wait after instantiating a new con \n"
 "before actually attempting to connect.  If this is\n"
@@ -10363,20 +4114,32 @@ msgid ""
 "until the output stream is flushed, the buffer fills, \n"
 "or that many milliseconds pass, and include any initial data with the SYN."
 msgstr ""
+"Cuánto esperar después de crear una instancia de nueva conexión antes de"
+" \n"
+"intentar conectar realmente. Si esto es <= 0 conecta inmediatamente \n"
+"sin datos inciales. Si es mayor que 0, espera hasta que la salida del "
+"flujo de \n"
+"datos (`stream`) sea evacuada, se llene el buffer, o que pasen muchos \n"
+"milisegundos, e incluye cualquier dato inicial con el SYN."
 
-#: i2p2www/pages/site/docs/api/streaming.html:170
+#: i2p2www/pages/site/docs/api/streaming.html:186
 msgid ""
 "How long to block on connect, in milliseconds. Negative means "
 "indefinitely. Default is 5 minutes."
 msgstr ""
+"Durante cuánto bloquear al conectar, en milisegundos. Valores negativos \n"
+"significan indefinidamente. El valor predeterminado es 5 minutos."
 
-#: i2p2www/pages/site/docs/api/streaming.html:174
+#: i2p2www/pages/site/docs/api/streaming.html:190
 msgid ""
 "Whether to disable warnings in the logs when an incoming connection is "
 "rejected due to connection limits."
 msgstr ""
+"Desactivar o no las advertencias en los registros (`logs`), cuando se "
+"rechaza \n"
+"una conexión entrante debido a los límites de la conexión."
 
-#: i2p2www/pages/site/docs/api/streaming.html:180
+#: i2p2www/pages/site/docs/api/streaming.html:196
 msgid ""
 "Whether to listen only for the streaming protocol.\n"
 "Setting to true will prohibit communication with Destinations earlier "
@@ -10384,113 +4147,187 @@ msgid ""
 "(released March 2009). Set to true if running multiple protocols on this "
 "Destination."
 msgstr ""
+"Escuchar o no sólo el protocolo streaming. Configurando a verdadero \n"
+"(`true`) prohibirá la comunicación con Destinos que usen una versión más"
+" \n"
+"temprana que la 0.7.1 (publicada en marzo de 2009). Configure a \n"
+"verdadero si ejecuta múltiples protocolos sobre este Destino."
 
-#: i2p2www/pages/site/docs/api/streaming.html:188
+#: i2p2www/pages/site/docs/api/streaming.html:204
 msgid ""
 "(0=noop, 1=disconnect)\n"
 "What to do on an inactivity timeout - do nothing, disconnect, or send a "
 "duplicate ack."
 msgstr ""
+"(0=nada, 1=desconectar)\n"
+"Qúe hacer durante un periodo de inactividad - no hacer nada, desconectar,"
+" o enviar un ACK duplicado."
 
-#: i2p2www/pages/site/docs/api/streaming.html:196
+#: i2p2www/pages/site/docs/api/streaming.html:212
 msgid ""
 "The initial value of the resend delay field in the packet header, times "
 "1000.\n"
 "Not fully implemented; see below."
 msgstr ""
+"El valor incial del campo de demora del reenvío en la cabecera del "
+"paquete, \n"
+"marca 1000. No está implementado completamente; vea debajo."
 
-#: i2p2www/pages/site/docs/api/streaming.html:201
-#: i2p2www/pages/site/docs/api/streaming.html:203
-msgid "if no sharing data available"
+#: i2p2www/pages/site/docs/api/streaming.html:217
+msgid ""
+"Initial timeout\n"
+"(if no sharing data available)."
 msgstr ""
+"Tiempo límite inicial (si no hay datos "
+"compartidos disponibles)."
 
-#: i2p2www/pages/site/docs/api/streaming.html:203
+#: i2p2www/pages/site/docs/api/streaming.html:224
+msgid ""
+"Initial round trip time estimate\n"
+"(if no sharing data available).\n"
+"Disabled as of release 0.9.8; uses actual RTT."
+msgstr ""
+"Estimación de (RTT/RTD) tiempo de viaje de ida y vuelta (si no hay \n"
+"datos compartidos disponibles). Deshabilitado "
+"desde la \n"
+"versión 0.9.8; usa el RTT real."
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
+msgid "if no sharing data available"
+msgstr "si no hay datos compatidos disponibles"
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
 msgid ""
 "In standard TCP, window sizes are in bytes, while in I2P, window sizes "
 "are in messages."
 msgstr ""
+"En TCP estándar, los tamaños de las ventanas se miden en bytes, mientras"
+" \n"
+"que en I2P los tamaños de las ventanas se miden en mensajes."
 
-#: i2p2www/pages/site/docs/api/streaming.html:207
+#: i2p2www/pages/site/docs/api/streaming.html:242
 msgid ""
 "(0 or negative value means unlimited)\n"
 "This is a total limit for incoming and outgoing combined."
 msgstr ""
+"(0 o valores negativos significan ilimitado) \n"
+"Esto es un límite total para la combinación entrante y saliente."
 
-#: i2p2www/pages/site/docs/api/streaming.html:212
+#: i2p2www/pages/site/docs/api/streaming.html:247
 msgid "Incoming connection limit (per peer; 0 means disabled)"
 msgstr ""
+"Límite de conexión entrante (por pares ('peer`); 0 significa "
+"deshabilitado)"
 
-#: i2p2www/pages/site/docs/api/streaming.html:218
-#: i2p2www/pages/site/docs/api/streaming.html:224
+#: i2p2www/pages/site/docs/api/streaming.html:253
+#: i2p2www/pages/site/docs/api/streaming.html:259
 msgid "(per peer; 0 means disabled)"
-msgstr ""
+msgstr "(por pares (`peer`); 0 significa deshabilitado)"
 
-#: i2p2www/pages/site/docs/api/streaming.html:230
+#: i2p2www/pages/site/docs/api/streaming.html:265
 msgid "The MTU in bytes."
 msgstr "La MTU en bytes."
 
-#: i2p2www/pages/site/docs/api/streaming.html:234
+#: i2p2www/pages/site/docs/api/streaming.html:269
 msgid "Maximum number of retransmissions before failure."
-msgstr ""
+msgstr "Número máximo de retransmisiones antes de fallo."
 
-#: i2p2www/pages/site/docs/api/streaming.html:238
+#: i2p2www/pages/site/docs/api/streaming.html:273
 msgid "Incoming connection limit (all peers; 0 means disabled)"
 msgstr ""
+"Límite de conexión entrante (todos los pares (`peers`); 0 significa "
+"deshabilitado)"
 
-#: i2p2www/pages/site/docs/api/streaming.html:244
-#: i2p2www/pages/site/docs/api/streaming.html:251
+#: i2p2www/pages/site/docs/api/streaming.html:279
+#: i2p2www/pages/site/docs/api/streaming.html:286
 msgid ""
 "(all peers; 0 means disabled)\n"
 "Use with caution as exceeding this will disable a server for a long time."
 msgstr ""
+"(todos los pares (`peers`); 0 significa deshabilitado)\n"
+"Usar con precaución ya que exceder esto deshabilitará un servidor por un "
+"largo periodo."
 
-#: i2p2www/pages/site/docs/api/streaming.html:260
+#: i2p2www/pages/site/docs/api/streaming.html:295
 msgid ""
 "(2=interactive not supported)\n"
 "This doesn't currently do anything, but setting it to a value other than "
 "1 will cause an error."
 msgstr ""
+"(2=interactivo no soportado)\n"
+"Esto actualmente no hace nada, pero configurándolo a un valor distino de "
+"1 causará un error."
 
-#: i2p2www/pages/site/docs/api/streaming.html:265
+#: i2p2www/pages/site/docs/api/streaming.html:300
 msgid "How long to block on read, in milliseconds. Negative means indefinitely."
 msgstr ""
+"Durante cuánto bloquear al leer, en milisegundos. Valores negativos "
+"significan indefinidamente."
 
-#: i2p2www/pages/site/docs/api/streaming.html:269
+#: i2p2www/pages/site/docs/api/streaming.html:304
 msgid ""
 "When we're in slow start, we grow the window size at the rate\n"
 "of 1/(factor).  In standard TCP, window sizes are in bytes,\n"
 "while in I2P, window sizes are in messages.\n"
 "A higher number means slower growth."
 msgstr ""
+"Cuando estemos en un inicio lento, elevaremos el tamaño de la ventana \n"
+"(del protocolo) a un ritmo de 1/(factor). En TCP estándar, los tamaños de"
+" ventana se miden en bytes, mientras que en I2P los tamaños de ventana se"
+" miden en mensajes. Un número más alto significa un crecimiento más "
+"lento."
 
-#: i2p2www/pages/site/docs/api/streaming.html:276
+#: i2p2www/pages/site/docs/api/streaming.html:311
+#: i2p2www/pages/site/docs/api/streaming.html:318
+#: i2p2www/pages/site/docs/api/streaming.html:325
+msgid ""
+"Ref: RFC 2140. Floating point value.\n"
+"May be set only via context properties, not connection options."
+msgstr ""
+"Ref: RFC 2140. Valor del punto flotante.\n"
+"Puede ser establecido sólo mediante las propiedades contextuales, no las "
+"opciones de conexión"
+
+#: i2p2www/pages/site/docs/api/streaming.html:332
 msgid ""
 "How long to block on write/flush, in milliseconds. Negative means "
 "indefinitely."
 msgstr ""
+"Durante cuánto bloquear al escribir/limpiar, en milisegundos. Los valores"
+" negativos significan indefinidamente."
 
-#: i2p2www/pages/site/docs/api/streaming.html:284
+#: i2p2www/pages/site/docs/api/streaming.html:340
 #: i2p2www/pages/site/docs/spec/streaming.html:10
 msgid "Protocol Specification"
 msgstr "Especificación del protocolo"
 
-#: i2p2www/pages/site/docs/api/streaming.html:286
+#: i2p2www/pages/site/docs/api/streaming.html:342
 msgid "See the Streaming Library Specification page."
-msgstr ""
+msgstr "Vea la página Especificación de la librería streaming."
 
-#: i2p2www/pages/site/docs/api/streaming.html:290
+#: i2p2www/pages/site/docs/api/streaming.html:346
 msgid "Implementation Details"
 msgstr "Detalles de la implementación"
 
-#: i2p2www/pages/site/docs/api/streaming.html:293
+#: i2p2www/pages/site/docs/api/streaming.html:348
+msgid "Setup"
+msgstr "Configuración"
+
+#: i2p2www/pages/site/docs/api/streaming.html:349
 msgid ""
 "The initiator sends a packet with the SYNCHRONIZE flag set. This packet "
 "may contain the initial data as well.\n"
 "The peer replies with a packet with the SYNCHRONIZE flag set. This packet"
 " may contain the initial response data as well."
 msgstr ""
+"El iniciador envía un paquete con el distintitivo SYNCHRONIZE "
+"(sincronizar) \n"
+"establecido. Este paquete puede contener también los datos iniciales. El "
+"par (`peer`) responde con un paquete con el distintivo SYNCHRONIZE "
+"establecido. Este paquete puede contener también los datos de respuesta "
+"iniciales"
 
-#: i2p2www/pages/site/docs/api/streaming.html:298
+#: i2p2www/pages/site/docs/api/streaming.html:354
 msgid ""
 "The initiator may send additional data packets, up to the initial window "
 "size, before receiving the SYNCHRONIZE response.\n"
@@ -10499,12 +4336,21 @@ msgid ""
 "period of time, as they may\n"
 "arrive out of order, in advance of the SYNCHRONIZE packet."
 msgstr ""
+"El iniciador puede enviar paquetes de datos adicionales, hasta el tamaño "
+"de \n"
+"ventana inicial, antes de recibir la respuesta SYNCHRONIZE. Estos \n"
+"paquetes también tendrán el campo `envíar Identificador de Stream` \n"
+"establecido a 0. Los receptores deben guardar en el buffer los paquetes \n"
+"recibidos sobre flujos (`streams`) desconocidos durante un periodo corto "
+"de \n"
+"tiempo, ya que pueden llegar estropeados, adelantándose al paquete \n"
+"SYNCHRONIZE."
 
-#: i2p2www/pages/site/docs/api/streaming.html:305
+#: i2p2www/pages/site/docs/api/streaming.html:361
 msgid "MTU Selection and Negotiation"
-msgstr ""
+msgstr "Selección y negociación MTU"
 
-#: i2p2www/pages/site/docs/api/streaming.html:306
+#: i2p2www/pages/site/docs/api/streaming.html:362
 msgid ""
 "The maximum message size (also called the MTU / MRU) is negotiated to the"
 " lower value supported by\n"
@@ -10516,8 +4362,16 @@ msgid ""
 "I2NP tunnel messages,\n"
 "including overhead for the typical case."
 msgstr ""
+"El máximo tamaño de mensaje (también llamado MTU / MRU) es negociado \n"
+"al menor valor soportado por los dos pares (`peers`). Como los mensajes \n"
+"túnel están acotados a 1KB, una elección MTU pobre llevaría a una gran "
+"cantidad de tráfico de control. La MTU está especificada por la opción "
+"i2p.streaming.maxMessageSize. La MTU está especificada por la opción "
+"i2p.streaming.maxMessageSize. La MTU actual por defecto de 1720 fue \n"
+"elegida para encajar precisamente en dos mensajes túnel I2NP de 1K, \n"
+"incluyendo el tráfico de control para un caso típico."
 
-#: i2p2www/pages/site/docs/api/streaming.html:315
+#: i2p2www/pages/site/docs/api/streaming.html:371
 msgid ""
 "The first message in a connection includes a 387 byte (typical) "
 "Destination added by the streaming layer,\n"
@@ -10534,16 +4388,39 @@ msgid ""
 "latency, reliability, and efficiency, especially for long-lived "
 "connections."
 msgstr ""
+"El primer mensaje en una conexión incluye un Destino de 387 bytes "
+"(típico) \n"
+"añadido por la capa streaming, y usualmente un LeaseSet (todos los leases"
+" o túneles autorizados a recibir conexiones para un destino concreto) de "
+"898 \n"
+"bytes (típico), y claves de Sesión, empaquetadas en un mensaje Ajo \n"
+"(`Garlic`) por el router (El LeaseSet y las Claves de Sesión no serán \n"
+"empaquetadas si se estableció previamente una Sesión ElGamal). Por lo \n"
+"tanto, la meta de encajar una petición HTTP completa en un sólo \n"
+"mensaje I2NP (I2P Network Protocol) de 1KB no siempre es alcanzable. Sin"
+" \n"
+"embargo, la elección de MTU, junto con una cuidadosa implementación de \n"
+"fragmentación y estrategias de elaboración de lotes en el procesador del"
+" \n"
+"túnel de la pasarela de salida (`gateway`), son factores importantes en "
+"el \n"
+"ancho de banda, latencia, confiabilidad y eficiencia de la red, "
+"especialmente \n"
+"para conexión de vida-larga."
 
-#: i2p2www/pages/site/docs/api/streaming.html:326
+#: i2p2www/pages/site/docs/api/streaming.html:382
 #, python-format
 msgid ""
 "Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
 "the I2CP layer.\n"
 "There is no checksum field in the streaming protocol."
 msgstr ""
+"La integridad de los datos está asegurada por el checksum CRC-32 de gzip"
+" \n"
+"implementado en la capa I2CP. No hay un "
+"campo checksum en el protocolo streaming."
 
-#: i2p2www/pages/site/docs/api/streaming.html:334
+#: i2p2www/pages/site/docs/api/streaming.html:390
 #, python-format
 msgid ""
 "Each packet is sent through I2P as a single message (or as an individual "
@@ -10556,24 +4433,37 @@ msgid ""
 "packet delimiter\n"
 "mechanism or payload length field in the streaming protocol."
 msgstr ""
+"Cada paquete es enviado a través de I2P como un solo mensaje (o como un "
+"diente en un mensaje Garlic). La "
+"encapsulación de los mensajes es implementada en el I2CP subyacente, en el I2NP, y en las capas de los túneles de mensajes. No hay mecanismo "
+"delimitador o campo de tamaño del payload en el protocolo de streaming."
 
-#: i2p2www/pages/site/docs/api/streaming.html:344
+#: i2p2www/pages/site/docs/api/streaming.html:400
 msgid "Windowing"
-msgstr ""
+msgstr "Ventanización"
 
-#: i2p2www/pages/site/docs/api/streaming.html:345
+#: i2p2www/pages/site/docs/api/streaming.html:401
 msgid ""
 "The streaming lib uses standard slow-start (exponential window growth) "
 "and congestion avoidance (linear window growth)\n"
 "phases, with exponential backoff.\n"
 "Windowing and acknowledgments use packet count, not byte count."
 msgstr ""
+"La librería streaming utiliza fases estándar de inicio-lento (crecimiento"
+" \n"
+"exponencial de la ventana (del protocolo)) y de elusión de congestión \n"
+"(crecimiento lineal de la ventana), con retroceso exponencial. La \n"
+"ventanización y los acuses de recibo ('acknowledments') cuentan paquetes,"
+" no bytes."
 
-#: i2p2www/pages/site/docs/api/streaming.html:352
+#: i2p2www/pages/site/docs/api/streaming.html:408
 msgid "Close"
-msgstr ""
+msgstr "Cerrar"
 
-#: i2p2www/pages/site/docs/api/streaming.html:353
+#: i2p2www/pages/site/docs/api/streaming.html:409
 msgid ""
 "Any packet, including one with the SYNCHRONIZE flag set, may have the "
 "CLOSE flag sent as well.\n"
@@ -10581,16 +4471,75 @@ msgid ""
 "\n"
 "CLOSE packets may contain data as well."
 msgstr ""
+"Cualquier paquete, incluyendo uno con el distintivo SYNCHRONIZE "
+"establecido, puede haber enviado también el distintivo CLOSE. La \n"
+"conexión no está cerrada hasta que el par (`peer`) responde con el \n"
+"distintivo CLOSE. Los paquetes CLOSE también pueden contener datos."
 
-#: i2p2www/pages/site/docs/api/streaming.html:360
-msgid "Control Block Sharing"
+#: i2p2www/pages/site/docs/api/streaming.html:417
+msgid ""
+"There is no ping function at the I2CP layer (equivalent to ICMP echo) or "
+"in datagrams.\n"
+"This function is provided in streaming.\n"
+"Pings and pongs may not be combined with a standard streaming packet;\n"
+"if the ECHO option is set, then\n"
+"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. "
+"are ignored."
 msgstr ""
+"No hay función ping en la capa I2CP (equivalente a un echo ICMP) o en los"
+" datagramas.\n"
+"Esta función se proporciona en streaming.\n"
+"Los pings y pongs pueden no estar combinados con un paquete streaming "
+"estandar;\n"
+"Si la opción ECHO está establecida, entonces la mayoría de otros "
+"indicadores ('flags'),\n"
+"opciones, ackThrough(s), sequenceNum(s), NACK(s), cargas, etc. (ver "
+"arriba), son ignorados."
 
-#: i2p2www/pages/site/docs/api/streaming.html:361
+#: i2p2www/pages/site/docs/api/streaming.html:425
+msgid ""
+"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED "
+"flags set.\n"
+"The sendStreamId must be greater than zero, and the receiveStreamId is "
+"ignored.\n"
+"The sendStreamId may or may not correspond to an existing connection."
+msgstr ""
+"Un paquete de ping debe tener establecidos los indicadores ECHO (eco),\n"
+"SIGNATURE_INCLUDED (firma incluida), y FROM_INCLUDED (origen incluido).\n"
+"El sendStreamId (identificador de stream de envío) puede o no "
+"corresponder con una conexión existente."
+
+#: i2p2www/pages/site/docs/api/streaming.html:431
+msgid ""
+"A pong packet must have the ECHO flag set.\n"
+"The sendStreamId must be zero, and the receiveStreamId is the "
+"sendStreamId from the ping.\n"
+"The pong packet does not include any payload that was contained in the "
+"ping."
+msgstr ""
+"Un paquete pong debe tener el indicador ECHO establecido.\n"
+"El sendStreamId debe ser cero, y el receiveStreamId (identificador de "
+"stream de recepción) es el sendStreamId del ping.\n"
+"El paquete pong no incluye carga alguna que estuviera contenida en el "
+"ping."
+
+#: i2p2www/pages/site/docs/api/streaming.html:437
+msgid ""
+"Streaming may be configured to disable sending pongs with the "
+"configuration i2p.streaming.answerPings=false."
+msgstr ""
+"El protocolo de streaming puede ser configurado para deshabilitar el "
+"envío de pongs con la configuración i2p.streaming.answerPings=false ."
+
+#: i2p2www/pages/site/docs/api/streaming.html:442
+msgid "Control Block Sharing"
+msgstr "Compartición del bloque de control"
+
+#: i2p2www/pages/site/docs/api/streaming.html:443
 msgid ""
 "The streaming lib supports \"TCP\" Control Block sharing.\n"
-"This shares two important streaming lib parameters\n"
-"(window size and round trip time)\n"
+"This shares three important streaming lib parameters\n"
+"(window size, round trip time, round trip time variance)\n"
 "across connections to the same remote peer.\n"
 "This is used for \"temporal\" sharing at connection open/close time,\n"
 "not \"ensemble\" sharing during a connection (See\n"
@@ -10599,25 +4548,48 @@ msgid ""
 "Destination)\n"
 "so that there is no information leakage to other Destinations on the\n"
 "same router.\n"
-"The share data for a given peer expires after a few minutes."
+"The share data for a given peer expires after a few minutes.\n"
+"The following Control Block Sharing parameters can be set per router:"
 msgstr ""
+"La librería streaming (de flujo) soporta compartición del Bloque de "
+"Control \n"
+"\"TCP\" (protocolo de control de transmisiones). Esto comparte tres \n"
+"importantes parámetros de la librería streaming (tamaño de la ventana, \n"
+"tiempo de viaje de ida y vuelta (RTT/RTD), variación del RTT) entre las \n"
+"conexiones al mismo par (`peer`) remoto. Esto se usa para la compartición"
+" \n"
+"\"temporal\" en el momento de apertura/cierre de la conexión, no para la"
+" \n"
+"compartición \"coral\" durante una conexión (Vea RFC 2140). Hay una "
+"compartición separada por \n"
+"ConnectionManager (administrador de conexión) (ej: por destino local), "
+"así \n"
+"que no hay información sobre filtraciones a otros destinos en el mismo \n"
+"router. Los datos compartidos para un par (`peer`) dado expiran después "
+"de \n"
+"unos pocos minutos. Los siguientes parámetros de Compartición del Bloque"
+" \n"
+"de Control pueden ser establecidos en cada router."
 
-#: i2p2www/pages/site/docs/api/streaming.html:375
+#: i2p2www/pages/site/docs/api/streaming.html:464
 msgid "Other Parameters"
 msgstr "Otros parámetros"
 
-#: i2p2www/pages/site/docs/api/streaming.html:376
+#: i2p2www/pages/site/docs/api/streaming.html:465
 msgid ""
 "The following parameters are hardcoded, but may be of interest for "
 "analysis:"
 msgstr ""
+"Los siguientes parámetros son internos, pero pueden ser de interés para "
+"el análisis:"
 
-#: i2p2www/pages/site/docs/api/streaming.html:393
-#: i2p2www/pages/site/docs/how/network-database.html:831
+#: i2p2www/pages/site/docs/api/streaming.html:484
+#: i2p2www/pages/site/docs/how/network-database.html:843
 msgid "History"
-msgstr ""
+msgstr "Historia"
 
-#: i2p2www/pages/site/docs/api/streaming.html:394
+#: i2p2www/pages/site/docs/api/streaming.html:485
 msgid ""
 "The streaming library has grown organically for I2P - first mihi "
 "implemented the\n"
@@ -10639,34 +4611,55 @@ msgid ""
 "retransmitting lost messages, and the latency and overhead of multiple "
 "messages."
 msgstr ""
+"La librería streaming ha crecido orgánicamente para I2P - primero mihi \n"
+"implementó la \"librería mini streaming\" como parte de I2PTunnel, que \n"
+"estaba limitada a un tamaño de ventana de 1 mensaje (requiriendo un ACK \n"
+"antes de enviar el siguiente), y entonces fue desgajado en una interfaz \n"
+"streaming genérica (a semejanza de los sockets TCP) y la implementación \n"
+"streaming completa fue desplegada con un protocolo de ventanas "
+"deslizantes y optimizaciones para tener en cuenta el alto valor del "
+"producto \n"
+"(ancho-de-banda x demora). Los flujos (`streams`) individuales pueden \n"
+"ajustar su tamaño máximo de paquete y otras opciones. El tamaño \n"
+"predeterminado del mensaje se selecciona para encajar de forma precisa \n"
+"en dos mensajes túnel I2NP (I2P Network Protocol) de 1KB, y es un \n"
+"compromiso de equilibrio razonable entre el coste en ancho de banda de \n"
+"retransmitir mensajes perdidos, y la latencia y tráfico de control de \n"
+"múltiples mensajes."
 
-#: i2p2www/pages/site/docs/api/streaming.html:408
+#: i2p2www/pages/site/docs/api/streaming.html:499
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:331
 #: i2p2www/pages/site/docs/how/garlic-routing.html:242
-#: i2p2www/pages/site/docs/how/network-database.html:836
+#: i2p2www/pages/site/docs/how/network-database.html:848
 #: i2p2www/pages/site/docs/how/peer-selection.html:265
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:255
-#: i2p2www/pages/site/docs/protocol/i2cp.html:646
+#: i2p2www/pages/site/docs/protocol/i2cp.html:654
 #: i2p2www/pages/site/docs/protocol/i2np.html:227
-#: i2p2www/pages/site/docs/spec/updates.html:222
-#: i2p2www/pages/site/docs/transport/ntcp.html:443
-#: i2p2www/pages/site/docs/transport/ssu.html:502
+#: i2p2www/pages/site/docs/spec/updates.html:280
+#: i2p2www/pages/site/docs/transport/ntcp.html:446
+#: i2p2www/pages/site/docs/transport/ssu.html:506
 #: i2p2www/pages/site/docs/tunnels/implementation.html:503
 msgid "Future Work"
 msgstr "Trabajo futuro"
 
-#: i2p2www/pages/site/docs/api/streaming.html:409
+#: i2p2www/pages/site/docs/api/streaming.html:500
 msgid ""
 "The behavior of the streaming library has a profound impact on\n"
 "application-level performance, and as such, is an important\n"
 "area for further analysis."
 msgstr ""
+"El comportamiento de la librería streaming tiene un profundo impacto "
+"sobre\n"
+"el rendimiento en el nivel-aplicación, y como tal, es un área importante "
+"para análisis detallados."
 
-#: i2p2www/pages/site/docs/api/streaming.html:415
+#: i2p2www/pages/site/docs/api/streaming.html:506
 msgid "Additional tuning of the streaming lib parameters may be necessary."
 msgstr ""
+"Podrían ser necesarios ajustes adicionales de los parámetros de librería "
+"streaming."
 
-#: i2p2www/pages/site/docs/api/streaming.html:418
+#: i2p2www/pages/site/docs/api/streaming.html:509
 #, python-format
 msgid ""
 "Another area for research is the interaction of the streaming lib with "
@@ -10674,8 +4667,12 @@ msgid ""
 "NTCP and SSU transport layers.\n"
 "See the NTCP discussion page for details."
 msgstr ""
+"Otro área de investigación es la interacción de la librería streaming con"
+" las capas de transporte NTCP (TCP basado en NIO) y SSU (UDP Seguro \n"
+"Semiconfiable). Para mayor detalle vea la página"
+" de discusión sobre NTCP."
 
-#: i2p2www/pages/site/docs/api/streaming.html:423
+#: i2p2www/pages/site/docs/api/streaming.html:514
 msgid ""
 "The interaction of the routing algorithms with the streaming lib strongly"
 " affects performance.\n"
@@ -10689,33 +4686,51 @@ msgid ""
 "failure and tunnel selection algorithms should be reviewed for possible \n"
 "improvements."
 msgstr ""
+"La interacción de los algoritmos de enrutado con la librería streaming "
+"afecta \n"
+"fuertemente al rendimiento. En particular, la distribución aleatoria de \n"
+"mensajes a múltiples túneles entre los que están en depósito, lleva a un "
+"alto grado de entregas estropeadas que resultan en tamaños de ventana \n"
+"más pequeños de lo que serían en otro caso. Actualmente el router enruta"
+" \n"
+"mensajes para un único par desde/hacia el destino a través de un conjunto"
+" consistente de túneles, hasta la expiración del túnel o un fallo en la "
+"entrega. El fallo del router y los algoritmos de selección del túnel "
+"deben ser revisados en busca de posibles mejoras."
 
-#: i2p2www/pages/site/docs/api/streaming.html:433
+#: i2p2www/pages/site/docs/api/streaming.html:524
 msgid "The data in the first SYN packet may exceed the receiver's MTU."
 msgstr ""
+"Los datos en el primer paquete SYN (sincronizar) pueden exceder la MTU "
+"(Unidad Máxima de Transporte) del receptor."
 
-#: i2p2www/pages/site/docs/api/streaming.html:436
+#: i2p2www/pages/site/docs/api/streaming.html:527
 msgid "The DELAY_REQUESTED field could be used more."
-msgstr ""
+msgstr "El campo DELAY_REQUESTED (demora requerida) podría ser usado más."
 
-#: i2p2www/pages/site/docs/api/streaming.html:439
+#: i2p2www/pages/site/docs/api/streaming.html:530
 msgid ""
 "Duplicate initial SYNCHRONIZE packets on short-lived streams may not be "
 "recognized and removed."
 msgstr ""
+"Los paquetes iniciales SYNCHRONIZE duplicados sobre streams de \n"
+"vida-corta pueden ser no reconocidos y eliminados."
 
-#: i2p2www/pages/site/docs/api/streaming.html:442
+#: i2p2www/pages/site/docs/api/streaming.html:533
 msgid "Don't send the MTU in a retransmission."
-msgstr ""
+msgstr "No envía la MTU en una retransmisión."
 
-#: i2p2www/pages/site/docs/api/streaming.html:445
+#: i2p2www/pages/site/docs/api/streaming.html:536
 msgid ""
 "Data is sent along unless the outbound window is full.\n"
 "(i.e. no-Nagle or TCP_NODELAY)\n"
 "Probably should have a configuration option for this."
 msgstr ""
+"Los datos se envían al recorrido a menos que la ventana de salida esté \n"
+"llena (es decir sin-Nagle o TCP_NODELAY).\n"
+"Probablemente debe haber una opción de configuración para esto."
 
-#: i2p2www/pages/site/docs/api/streaming.html:450
+#: i2p2www/pages/site/docs/api/streaming.html:541
 msgid ""
 "zzz has added debug code to the streaming library to log packets in a "
 "wireshark-compatible\n"
@@ -10723,14 +4738,27 @@ msgid ""
 "The format may require enhancement to map more streaming lib parameters "
 "to TCP fields."
 msgstr ""
+"zzz ha añadido código de depuración a la librería streaming para "
+"registrar \n"
+"(`log`) paquetes en un formato compatible-wireshark (pcap); utilice esto "
+"para \n"
+"analizar el rendimiento con mayor detalle. El formato puede requerir "
+"mejoras \n"
+"para mapear más parámetros de librería streaming en campos TCP."
 
-#: i2p2www/pages/site/docs/api/streaming.html:455
+#: i2p2www/pages/site/docs/api/streaming.html:546
 msgid ""
 "There are proposals to replace the streaming lib with standard TCP\n"
 "(or perhaps a null layer together with raw sockets).\n"
 "This would unfortunately be incompatible with the streaming lib\n"
 "but it would be good to compare the performance of the two."
 msgstr ""
+"Hay propuestas para reemplazar la librería streaming con TCP estándar (o"
+" \n"
+"quizá con una capa vacía junto con sockets crudos (`raw`)). \n"
+"Desafortunadamente esto sería incompatible con la librería streaming pero"
+" \n"
+"sería bueno para comparar el rendimiento de los dos."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:3
 #: i2p2www/pages/site/docs/spec/configuration.html:3
@@ -10747,6 +4775,13 @@ msgid ""
 "Note carefully the guidelines for compatibility with older I2P clients "
 "and trackers."
 msgstr ""
+"Hay varios clientes bittorrent y trackers sobre I2P. Como el "
+"direccionamiento \n"
+"de I2P usa un Destino en lugar de IP y puerto, los cambios que se "
+"requieren \n"
+"en los softwares del tracker y del cliente para operar sobre I2P son \n"
+"menores. Estos cambios se especifican debajo. Observe con cuidado las \n"
+"directrices para compatibilidad con anteriores clientes y trackers I2P."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:15
 msgid ""
@@ -10754,14 +4789,21 @@ msgid ""
 "Specific clients and trackers may implement other unique features or "
 "protocols."
 msgstr ""
+"Esta página especifica detalles del protocolo comunes a todos los "
+"clientes \n"
+"y trackers. Los clientes y trackers específicos pueden implementar otras"
+" \n"
+"características únicas o protocolos."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:20
 msgid "We welcome additional ports of client and tracker software to I2P."
 msgstr ""
+"Son bienvenidos puertos adicionales de software de cliente y tracker para"
+" I2P."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:26
 msgid "Announces"
-msgstr ""
+msgstr "Anuncios"
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:27
 msgid ""
@@ -10769,6 +4811,10 @@ msgid ""
 " compatibility with older trackers.\n"
 "Trackers may ignore the port parameter, and should not require it."
 msgstr ""
+"Los clientes generalmente incluyen un parámetro falso port=6881 en el \n"
+"anuncio, por compatibilidad con anteriores trackers. Los trackers pueden"
+" \n"
+"ignorar el parámetro port (puerto), y no deberían necesitarlo."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:32
 #, python-format
@@ -10782,10 +4828,18 @@ msgid ""
 "compatibility with older trackers.\n"
 "Trackers should not require an appended \".i2p\"."
 msgstr ""
+"El parámetro IP es la base 64 de la Destinación del "
+"cliente, usando el alfabeto I2P Base 64  [A-Z][a-z][0-9]-~. Las Destinaciones son de"
+" 387+ bytes, con lo que la Base 64 es de 516+ bytes. Los clientes "
+"generalmente añaden \".i2p\" a la Destinación Base 64 para mantener la "
+"compatibilidad con los trackers antiguos. Los trackers no deberían "
+"necesitar añadir \".i2p\" al final."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:42
 msgid "Other parameters are the same as in standard bittorrent."
-msgstr ""
+msgstr "Otros parámetros son los mismos que en el bittorrent estandar."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:46
 msgid ""
@@ -10797,6 +4851,15 @@ msgid ""
 "below),\n"
 "the tracker should probably decode and reject bad Base64 when announced."
 msgstr ""
+"Aunque todos los Destinos actuales para clientes son exactamente de \n"
+"387 bytes, un tracker no debería presumir que siempre será así. Un valor"
+" \n"
+"máximo razonable a asumir, por ahora, es 475 bytes. Como el tracker debe"
+" \n"
+"decodificar la Base64 para entregar respuestas compactas (vea debajo), el"
+" \n"
+"tracker probablemente debe decodificar y rechazar las Base64 defectuosas "
+"cuando se anuncie."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:53
 msgid ""
@@ -10805,6 +4868,10 @@ msgid ""
 "the parameter compact=1. A tracker may, but is not required to, return\n"
 "a compact response when requested."
 msgstr ""
+"La respuesta tipo predeterminada es no-compacta. Los clientes pueden \n"
+"solicitar una respuesta compacta con el parámetro compact=1. Un tracker\n"
+"podría, pero no es un requisito, devolver una respuesta compacta cuando\n"
+"se le solicite."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:59
 msgid ""
@@ -10815,22 +4882,31 @@ msgid ""
 "it allows\n"
 "destination enforcement by the tracker (see below)."
 msgstr ""
+"A los desarrolladores de nuevos clientes I2P se les anima fuertemente a \n"
+"implementar anuncios sobre su propio túnel en lugar de sobre el proxy del"
+" \n"
+"cliente HTTP en el puerto 4444. Hacerlo así es tanto más eficiente como a"
+" su vez permite al tracker aplicar destinos (vea debajo)."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:66
 msgid ""
 "There are no known I2P clients or trackers that currently support UDP "
 "announce/responses."
 msgstr ""
+"No hay clientes o trackers I2P conocidos que actualmente soporten "
+"anuncios/respuestas UDP."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:71
 msgid "Non-Compact Tracker Responses"
-msgstr ""
+msgstr "Respuestas de tracker no-compactas"
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:72
 msgid ""
 "The non-compact response is just as in standard bittorrent, with an I2P "
 "\"ip\"."
 msgstr ""
+"La respuesta no-compacta es como la del bittorrent estándar, con una "
+"\"ip\" I2P."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:76
 msgid ""
@@ -10838,6 +4914,9 @@ msgid ""
 "announce, for compatibility with older clients.\n"
 "Clients must ignore the port parameter, and should not require it."
 msgstr ""
+"Los trackers generalmente incluyen un clave de puerto falsa, o usan el "
+"puerto del anuncio, por compatibilidad con anteriores clientes. Los \n"
+"clientes deben ignorar el parámetro port (puerto), y no deben solicitarlo."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:81
 #, python-format
@@ -10849,14 +4928,25 @@ msgid ""
 "wasn't in the announce ip, for compatibility with older clients.\n"
 "Clients should not require an appended \".i2p\" in the responses."
 msgstr ""
+"El valor de la clave ip es la base 64 del Destino del cliente,"
+" como se \n"
+"describe arriba. Los trackers generalmente añaden \".i2p\" al final del "
+"Destino \n"
+"Base 64 si no estaba en el ip del anuncio, por compatibilidad con "
+"anteriores \n"
+"clientes. Los clientes no deben solicitar un sufijo \".i2p\" en las "
+"respuestas."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:88
 msgid "Other response keys and values are the same as in standard bittorrent."
 msgstr ""
+"Otras claves y valores de respuesta son los mismos que en el bittorrent "
+"estandar."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:94
 msgid "Compact Tracker Responses"
-msgstr ""
+msgstr "Respuestas de tracker compactas"
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:95
 #, python-format
@@ -10876,17 +4966,35 @@ msgid ""
 "or X-I2P-DestB32 HTTP headers may be converted to binary and stored.\n"
 "The peers key may be absent, or the peers value may be zero-length."
 msgstr ""
+"En la respuesta compacta, el valor de la clave de diccionario de los "
+"\"peers\" (pares) es una única cadena de bytes, cuya longitud es un "
+"múltiplo de 32 \n"
+"bytes. Esta cadena contiene los Hashes SHA-256 de 32-bytes \n"
+"concatenados del binario Destinos de los "
+"pares. Este \n"
+"`hash` (identificador único) debe calcularse por el tracker, a menos que "
+"use \n"
+"aplicación en destino (vea debajo), en cuyo caso el identificador "
+"(`hash`) \n"
+"entregado en las cabeceras HTTP X-I2P-DestHash o X-I2P-DestB32 puede ser "
+"convertido a binario y almacenado. La clave de los pares (`peers`) \n"
+"puede estar ausente, o el valor de los pares puede tener longitud-cero."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:109
 msgid ""
 "While compact response support is optional for both clients and trackers,"
 " it is highly\n"
-"recommended as it reduces the nominal response size by over 90%."
+"recommended as it reduces the nominal response size by over 90%."
 msgstr ""
+"Aunque el soporte para respuesta compacta es opcional para ambos, \n"
+"clientes y trackers, es altamente recomendable ya que reduce el tamaño \n"
+"nominal de respuesta alrededor de un 90%."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:116
 msgid "Destination Enforcement"
-msgstr ""
+msgstr "Aplicación en destino"
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:117
 #, python-format
@@ -10905,6 +5013,15 @@ msgid ""
 "A tracker enforcing destinations need not require the ip announce "
 "parameter at all."
 msgstr ""
+"Algunos clientes de torrent de I2P, aunque no todos, anuncian sus propios"
+" túneles. Los trackers pueden elegir el prevenir engaños exigiéndolos, y "
+"verificando la Destinación de los "
+"clientes usando las cabeceras  añadidas por el túnel servidor HTTP "
+"I2PTunnel. Las cabeceras son X-I2P-DestHash, X-I2P-DestB64, y X-I2P-"
+"DestB32, que son diferentes formatos para la misma información. Estas "
+"cabeceras no pueden ser falseadas por el cliente. Un tracker exigiendo "
+"destinaciones no necesita el parámetro de anuncio de la ip para nada."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:129
 msgid ""
@@ -10914,6 +5031,11 @@ msgid ""
 "until\n"
 "those clients are converted to announcing over their own tunnel."
 msgstr ""
+"Como varios clientes usan el proxy HTTP en lugar de sus propios túneles \n"
+"para los anuncios, la aplicación de destino (en el tracker) prevendrá su "
+"uso \n"
+"por aquellos clientes a menos que, o hasta que, aquellos clientes se \n"
+"reconviertan para anunciarse sobre sus propios túneles. "
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:135
 msgid ""
@@ -10922,10 +5044,15 @@ msgid ""
 "so we expect that all trackers will eventually enforce destinations.\n"
 "Both tracker and client developers should anticipate it."
 msgstr ""
+"Desafortunadamente, al crecer la red, también lo hará la cantidad de \n"
+"maliciosidad, así que esperamos que en su momento todos los trackers \n"
+"apliquen los destinos. Ambos, desarrolladores de trackers y clientes "
+"deben \n"
+"anticiparlo."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:143
 msgid "Announce Host Names"
-msgstr ""
+msgstr "Nombres de Servidor de Anuncio"
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:144
 #, python-format
@@ -10939,22 +5066,36 @@ msgid ""
 "Non-open trackers should recognize their own host name in any of these "
 "formats."
 msgstr ""
+"Los nombres de servidor de URLs de anuncio en los archivos torrent siguen"
+"\n"
+"generalmente los estándares de nombres I2P. "
+"Además de los \n"
+"nombres de servidor de las libretas de direcciones y los nombre de "
+"servidor Base 32 \".b32.i2p\", el Destino Base 64 completo (con [¿o sin?]"
+" \n"
+"sufijo \".i2p\"] debe ser soportado. Los trackers no-abiertos deben \n"
+"reconocer sus propios nombres de servidor en cualquiera de estos formatos."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:152
 msgid ""
 "To preserve anonymity,\n"
 "clients should generally ignore non-I2P announce URLs in torrent files."
 msgstr ""
+"Para preservar el anonimato, los clientes por lo general deben ignorar "
+"URLs de anuncio no-I2P en los ficheros torrent."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:159
 msgid "Client Connections"
-msgstr ""
+msgstr "Conexiones entre clientes"
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:160
 msgid ""
 "Client-to-client connections use the standard protocol over TCP.\n"
 "There are no known I2P clients that currently support uTP communication."
 msgstr ""
+"Las conexiones cliente-a-cliente usan el protocolo estándar sobre TCP. \n"
+"Actualmente no hay clientes I2P conocidos que soporten comunicación uTP \n"
+"(Protocol de Transporte utorrent)."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:165
 #, python-format
@@ -10963,6 +5104,8 @@ msgid ""
 "href=\"%(commonstructures)s#struct_Destination\">Destinations\n"
 "for addresses, as explained above."
 msgstr ""
+"I2P usa Destinos "
+"de 387+ bytes para direcciones, como se explicó arriba."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:170
 msgid ""
@@ -10972,6 +5115,15 @@ msgid ""
 "Naming Service,\n"
 "which will return the full Destination if available."
 msgstr ""
+"Si el cliente tiene sólo el identificador criptográfico (`hash`) del "
+"destino \n"
+"(como el de una respuesta compacta o el PEX (protocolo de Intercambio de"
+" \n"
+"Pares)), debe realizar una búsqueda codificándolo con Base 32, añadiendo"
+" \n"
+"el sufijo \".b32.i2p\", y consultando en el Servicio de Nombres, que "
+"devolverá \n"
+"el Destino completo si está disponible."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:176
 msgid ""
@@ -10981,10 +5133,16 @@ msgid ""
 "Do not convert a Destination back to a Base 32 hash for lookup, this is "
 "quite inefficient."
 msgstr ""
+"Si el cliente tiene el Destino completo de un par (`peer`) que recibió en"
+" una \n"
+"respuesta no-compacta, debe usarlo directamente en el establecimiento de"
+" \n"
+"la conexión. No convierta un Destino de vuelta a un identificador \n"
+"criptográfico (`hash`) Base 32, esto es bastante ineficiente."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:183
 msgid "Cross-Network Prevention"
-msgstr ""
+msgstr "Prevención de redes-cruzadas."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:184
 msgid ""
@@ -10994,6 +5152,12 @@ msgid ""
 "I2P HTTP outproxies often block announces.\n"
 "There are no known SOCKS outproxies supporting bittorrent traffic."
 msgstr ""
+"Para preservar el anonimato, los clientes I2P bittorrent por lo general "
+"no soportan anuncios no-I2P, o conexiones de pares (`peers`). Los proxys"
+" \n"
+"al exterior (`outproxies`) HTTP de I2P con frecuencia bloquean anuncios. "
+"No \n"
+"hay proxys al exterior SOCKS conocidos que soporten tráfico bittorrent."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:191
 msgid ""
@@ -11003,6 +5167,11 @@ msgid ""
 "Trackers should reject standard network announces with IPv4 or IPv6 IPs, "
 "and not deliver them in responses."
 msgstr ""
+"Para prevenir el uso por clientes no-I2P a través de un proxy hacia el \n"
+"interior (`inproxy`) HTTP, los trackers I2P a menudo bloquean accesos o \n"
+"anuncios que contengan una cabecera HTTP X-Forwarded-For. Los \n"
+"trackers deben rechazar anuncios de red estándar con IPs IPv4 o IPv6, y \n"
+"no entregarlos en las respuestas."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:200
 #, python-format
@@ -11025,6 +5194,28 @@ msgid ""
 "response format specified above.\n"
 "The added.f value, if present, is the same as in ut_pex."
 msgstr ""
+"El PEX (protocolo de Intercambio de Pares) I2P está basado en ut_pex \n"
+"(utorrent PEX). Como no parece haber una especificación ut_pex formal \n"
+"disponible, puede ser necesario revisar el código fuente de libtorrent "
+"para \n"
+"obtener asistencia. Es un mensaje de extensión, identificado como \n"
+"\"i2p_pex\" en la extensión de "
+"toma de contacto (`handshake`). Contiene un diccionario \n"
+"b-codificado (`bencoded`) con hasta 3 claves, \"added\" (añadido), "
+"\"added.f\", \n"
+"y \"dropped\" (descartado). Los valores `added` y `dropped` son cada uno "
+"una \n"
+"única cadena de bytes, cuyo tamaño es un múltiplo de 32 bytes. Estas \n"
+"cadenas de bytes son los identificadores criptográficos ('hashes') "
+"SHA-256 \n"
+"concatenados del binario Destinos \n"
+"de los pares (`peers`). \n"
+"Este es el mismo formato que el de los valores de diccionario de los "
+"pares \n"
+"en el formato de respuesta compacta de I2P especificado arriba. Si está \n"
+"presente, el valor de added.f es el mismo que en ut_pex."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:218
 msgid ""
@@ -11034,6 +5225,13 @@ msgid ""
 "are described below, and are subject to change.\n"
 "Contact the I2P developers if you wish to develop a client supporting DHT."
 msgstr ""
+"El soporte DHT (tabla de hash dinámica) está incluido en el cliente "
+"i2psnark \n"
+"desde la versión 0.9.2. Las diferencias preliminares con la BEP 5 \n"
+"(Propuesta de Mejora de Bittorrent 5) están descritas debajo, y están \n"
+"sujetas a cambios. Contacte con los desarrolladores de I2P si quiere \n"
+"desarrollar un cliente con soporte DHT."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:226
 msgid ""
@@ -11045,6 +5243,15 @@ msgid ""
 "It contains a bencoded dictionary with two keys, \"port\" and \"rport\", "
 "both integers."
 msgstr ""
+"Al contario que DHT (tabla de hash dinámica), I2P DHT no usa bit alguno "
+"en \n"
+"las opciones de toma de contacto (`handshake`), o en el mensaje PORT \n"
+"(puerto). Se anuncia con un mensaje de extensión, identificado como \n"
+"\"i2p_dht\" en la extensión "
+"handshake. Contiene un diccionario b-codificado \n"
+"(`bencoded`) con dos claves, \"port\" y \"rport\" (puerto de respuesta), "
+"ambos enteros."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:233
 msgid ""
@@ -11055,6 +5262,13 @@ msgid ""
 "This is the \"port\" value from the extension message.\n"
 "Queries use I2CP protocol number 17."
 msgstr ""
+"Para recibir datagramas respondibles (firmados) se usa el puerto UDP\n"
+"(Protocolo de Datagrama de Usuario) listado en la información del nodo \n"
+"compacto. Este se usa para consultas, excepto para anuncios. Le \n"
+"llamamos el \"query port\" (puerto de consulta). Es el valor \"port\" "
+"(puerto) del \n"
+"mensaje de extensión. Las consultas usan el protocolo I2CP (Protocolo \n"
+"de Cliente I2P) número 17."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:242
 msgid ""
@@ -11068,6 +5282,16 @@ msgid ""
 "It must be 1 + the query port.\n"
 "Responses and announces use I2CP protocol number 18."
 msgstr ""
+"Además de ese puerto UDP, usamos un segundo puerto de datagrama igual \n"
+"al puerto de consulta + 1. Esto se usa para recibir datagramas no "
+"firmados \n"
+"(raw (crudos)) para las respuestas, errores, y anuncios. Este puerto \n"
+"proporciona una eficiencia aumentada ya que las respuestas contienen las"
+" \n"
+"credenciales (`tokens`) enviadas en la consulta, y no necesitan ser \n"
+"firmadas. Llamamos a esto el \"response port\" (puerto de respuesta). "
+"Este es el valor \"rport\" del mensaje de extensión. Las respuestas y los"
+" anuncios usan el protocolo I2CP número 18."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:254
 msgid ""
@@ -11076,6 +5300,11 @@ msgid ""
 "In a response, the \"values\" key is a list of strings, each containing a"
 " single compact peer info."
 msgstr ""
+"La información compacta del par (`peer`) son 32 bytes (identificador "
+"criptográfico (`hash`) SHA256 de 32 bytes) en lugar de 4 bytes de IP + 2 "
+"bytes de puerto. No hay puerto del par. En una respuesta, la clave \n"
+"\"values\" (valores) es una lista de cadenas, conteniendo cada una la \n"
+"información compacta de un único par."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:260
 msgid ""
@@ -11085,6 +5314,12 @@ msgid ""
 "In a response, the \"nodes\" key is a\n"
 "single byte string with concatenated compact node info."
 msgstr ""
+"La información de nodo compacto son 54 bytes (20 bytes de hash SHA1 + \n"
+"32 bytes de hash SHA256 + 2 bytes de puerto) en lugar de 20 bytes de \n"
+"hash SHA1 + 4 bytes de IP + 2 bytes de puerto. En una respuesta, la clave"
+" \n"
+"\"nodes\" (nodos) es una única cadena de bytes con la información \n"
+"concatenada de nodo compacto."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:267
 msgid ""
@@ -11095,6 +5330,14 @@ msgid ""
 "the\n"
 "destination hash exclusive-ORed with the port."
 msgstr ""
+"Requisito de identificador (`ID`) de nodo seguro: Para hacer más "
+"difíciles diferentes ataques DHT (tabla de hash distribuida) los primeros"
+" 4 bytes \n"
+"del identificador de nodo (`ID`) deben coincidir con los primeros 4 bytes"
+" del identificador criptográfico (`hash`) del destino, y los siguientes 2"
+" bytes del identificador de nodo deben coincidir con los siguientes 2 "
+"bytes del resultado de la operación OR-exclusivo del hash del destino con"
+" el puerto. "
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:274
 msgid ""
@@ -11106,6 +5349,14 @@ msgid ""
 "Alternatives: A single byte string with concatenated hashes,\n"
 "or a list of strings alone."
 msgstr ""
+"En un fichero torrent, la clave \"nodos\" del diccionario de un torrent "
+"sin \n"
+"tracker ha de ser determinada. Podría ser una lista de cadenas binarias "
+"de \n"
+"32 bytes (hashes SHA256) en lugar de una lista de listas que contengan \n"
+"una cadena de servidor y un valor entero de puerto. \n"
+"Alternativas: Una única cadena de bytes con hashes concatenados, o una  "
+"lista de cadenas por si solas."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:285
 #: i2p2www/pages/site/docs/how/intro.html:187
@@ -11118,6 +5369,8 @@ msgid ""
 "I2P bittorrent standards are generally discussed on %(zzz)s."
 msgstr ""
+"Los estandares bittorrent I2P se discuten generalmente en %(zzz)s."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:290
 #, python-format
@@ -11125,6 +5378,8 @@ msgid ""
 "A chart of current tracker software capabilities is also available there."
 msgstr ""
+"Una gráfica con las capacidades del actual software de tracker también "
+"está disponible allí."
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:293
 #, python-format
@@ -11132,11 +5387,13 @@ msgid ""
 "The\n"
 "I2P bittorrent FAQ"
 msgstr ""
+"El FAQ del bittorrent "
+"I2P"
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:297
 #, python-format
 msgid "DHT on I2P discussion"
-msgstr ""
+msgstr "Discusión de DHT sobre I2P"
 
 #: i2p2www/pages/site/docs/applications/supported.html:2
 #: i2p2www/pages/site/docs/applications/supported.html:5
@@ -11174,82 +5431,82 @@ msgid "Email"
 msgstr "Correo-e"
 
 #: i2p2www/pages/site/docs/applications/supported.html:26
-#: i2p2www/pages/site/docs/applications/supported.html:315
+#: i2p2www/pages/site/docs/applications/supported.html:328
 msgid "File Sharing"
 msgstr "Compartición de archivos"
 
 #: i2p2www/pages/site/docs/applications/supported.html:29
-#: i2p2www/pages/site/docs/applications/supported.html:317
+#: i2p2www/pages/site/docs/applications/supported.html:330
 msgid "BitTorrent clients"
 msgstr "Clientes de BitTorrent"
 
 #: i2p2www/pages/site/docs/applications/supported.html:31
-#: i2p2www/pages/site/docs/applications/supported.html:359
+#: i2p2www/pages/site/docs/applications/supported.html:372
 msgid "BitTorrent trackers and indexers"
 msgstr "Trackers e indexadores de BitTorrent"
 
 #: i2p2www/pages/site/docs/applications/supported.html:40
-#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:439
 msgid "Network Administration"
 msgstr "Administración de red"
 
 #: i2p2www/pages/site/docs/applications/supported.html:43
-#: i2p2www/pages/site/docs/applications/supported.html:428
+#: i2p2www/pages/site/docs/applications/supported.html:441
 msgid "General-purpose socket utilities"
 msgstr "Utilidades para sockets de uso general"
 
 #: i2p2www/pages/site/docs/applications/supported.html:50
-#: i2p2www/pages/site/docs/applications/supported.html:469
+#: i2p2www/pages/site/docs/applications/supported.html:482
 msgid "Real-time Chat"
 msgstr "Chat en tiempo real"
 
 #: i2p2www/pages/site/docs/applications/supported.html:53
-#: i2p2www/pages/site/docs/applications/supported.html:471
+#: i2p2www/pages/site/docs/applications/supported.html:484
 msgid "Instant messaging clients"
 msgstr "Clientes de mensajería instatánea"
 
 #: i2p2www/pages/site/docs/applications/supported.html:55
-#: i2p2www/pages/site/docs/applications/supported.html:481
+#: i2p2www/pages/site/docs/applications/supported.html:494
 msgid "IRC clients"
 msgstr "Clientes iRC"
 
 #: i2p2www/pages/site/docs/applications/supported.html:57
-#: i2p2www/pages/site/docs/applications/supported.html:532
+#: i2p2www/pages/site/docs/applications/supported.html:545
 msgid "IRC servers"
 msgstr "Servidores iRC"
 
 #: i2p2www/pages/site/docs/applications/supported.html:62
-#: i2p2www/pages/site/docs/applications/supported.html:548
+#: i2p2www/pages/site/docs/applications/supported.html:561
 msgid "Web Browsing"
 msgstr "Navegación web"
 
 #: i2p2www/pages/site/docs/applications/supported.html:65
-#: i2p2www/pages/site/docs/applications/supported.html:550
+#: i2p2www/pages/site/docs/applications/supported.html:563
 msgid "Anonymous websites"
 msgstr "Webs anónimas"
 
 #: i2p2www/pages/site/docs/applications/supported.html:67
-#: i2p2www/pages/site/docs/applications/supported.html:599
+#: i2p2www/pages/site/docs/applications/supported.html:612
 msgid "Proxy software"
 msgstr "Aplicaciones de Proxy"
 
 #: i2p2www/pages/site/docs/applications/supported.html:69
-#: i2p2www/pages/site/docs/applications/supported.html:624
+#: i2p2www/pages/site/docs/applications/supported.html:637
 msgid "Inproxies"
 msgstr "Proxies de entrada"
 
 #: i2p2www/pages/site/docs/applications/supported.html:71
-#: i2p2www/pages/site/docs/applications/supported.html:640
+#: i2p2www/pages/site/docs/applications/supported.html:669
 msgid "Outproxies"
 msgstr "Proxies de salida"
 
 #: i2p2www/pages/site/docs/applications/supported.html:76
-#: i2p2www/pages/site/docs/applications/supported.html:654
+#: i2p2www/pages/site/docs/applications/supported.html:683
 msgid "Website Hosting"
 msgstr "Alojamiento web"
 
 #: i2p2www/pages/site/docs/applications/supported.html:79
-#: i2p2www/pages/site/docs/applications/supported.html:669
+#: i2p2www/pages/site/docs/applications/supported.html:698
 msgid "Web servers"
 msgstr "Servidores web"
 
@@ -11258,14 +5515,13 @@ msgstr "Servidores web"
 msgid ""
 "This is intended to be a comprehensive listing of applications used with\n"
 "I2P. If you know of something that's missing please submit a ticket on\n"
-"Trac, and be sure to select the"
-"\n"
+"Trac, and be sure to select the\n"
 "“www” component in the submission form."
 msgstr ""
-"Esto es un intento de crear una lista de aplicaciones usadas en I2P. Si "
-"conoces alguna que falte en la lista, por favor cree un ticket en el Trac, y asegúrese de seleccionar "
-"el componente 'www' en el formulario."
+"Esto pretende ser una lista precisa de las aplicaciones usadas en I2P. Si"
+" conoce alguna que falte, por favor cree un ticket en el Trac, y asegúrese de seleccionar el componente "
+"\"www\" en el formulario."
 
 #: i2p2www/pages/site/docs/applications/supported.html:92
 msgid ""
@@ -11278,8 +5534,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:97
 #: i2p2www/pages/site/docs/applications/supported.html:279
 #: i2p2www/pages/site/docs/applications/supported.html:311
-#: i2p2www/pages/site/docs/applications/supported.html:323
-#: i2p2www/pages/site/docs/applications/supported.html:666
+#: i2p2www/pages/site/docs/applications/supported.html:336
+#: i2p2www/pages/site/docs/applications/supported.html:695
 msgid "bundled"
 msgstr "incluida"
 
@@ -11300,10 +5556,10 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:228
 #: i2p2www/pages/site/docs/applications/supported.html:241
 #: i2p2www/pages/site/docs/applications/supported.html:292
-#: i2p2www/pages/site/docs/applications/supported.html:391
-#: i2p2www/pages/site/docs/applications/supported.html:413
-#: i2p2www/pages/site/docs/applications/supported.html:422
-#: i2p2www/pages/site/docs/applications/supported.html:510
+#: i2p2www/pages/site/docs/applications/supported.html:404
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:523
 msgid "plugin"
 msgstr "pluguin"
 
@@ -11318,9 +5574,9 @@ msgid ""
 msgstr ""
 " Pluguins de terceras partes — el sistema de pluguins de I2P "
 "provee el despliegue de aplicaciones para I2P y permite una integración "
-"más estrecha con el ruter. Los pluguins son [revisados por la "
-"comunidad](http://%(plugins)s) para "
-"identificar problemas de seguridad y anonimato."
+"más estrecha con el ruter. Los pluguins son [revisados por la comunidad] "
+"(http://%(plugins)s) para identificar "
+"problemas de seguridad y anonimato."
 
 #: i2p2www/pages/site/docs/applications/supported.html:121
 #: i2p2www/pages/site/docs/applications/supported.html:220
@@ -11328,30 +5584,31 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:241
 #: i2p2www/pages/site/docs/applications/supported.html:252
 #: i2p2www/pages/site/docs/applications/supported.html:261
-#: i2p2www/pages/site/docs/applications/supported.html:329
-#: i2p2www/pages/site/docs/applications/supported.html:340
-#: i2p2www/pages/site/docs/applications/supported.html:355
-#: i2p2www/pages/site/docs/applications/supported.html:401
-#: i2p2www/pages/site/docs/applications/supported.html:413
-#: i2p2www/pages/site/docs/applications/supported.html:422
-#: i2p2www/pages/site/docs/applications/supported.html:437
-#: i2p2www/pages/site/docs/applications/supported.html:443
-#: i2p2www/pages/site/docs/applications/supported.html:449
-#: i2p2www/pages/site/docs/applications/supported.html:459
-#: i2p2www/pages/site/docs/applications/supported.html:465
-#: i2p2www/pages/site/docs/applications/supported.html:477
-#: i2p2www/pages/site/docs/applications/supported.html:510
-#: i2p2www/pages/site/docs/applications/supported.html:516
-#: i2p2www/pages/site/docs/applications/supported.html:522
-#: i2p2www/pages/site/docs/applications/supported.html:528
-#: i2p2www/pages/site/docs/applications/supported.html:605
-#: i2p2www/pages/site/docs/applications/supported.html:614
-#: i2p2www/pages/site/docs/applications/supported.html:620
-#: i2p2www/pages/site/docs/applications/supported.html:666
-#: i2p2www/pages/site/docs/applications/supported.html:681
-#: i2p2www/pages/site/docs/applications/supported.html:687
-#: i2p2www/pages/site/docs/applications/supported.html:693
-#: i2p2www/pages/site/docs/applications/supported.html:699
+#: i2p2www/pages/site/docs/applications/supported.html:324
+#: i2p2www/pages/site/docs/applications/supported.html:342
+#: i2p2www/pages/site/docs/applications/supported.html:353
+#: i2p2www/pages/site/docs/applications/supported.html:368
+#: i2p2www/pages/site/docs/applications/supported.html:414
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:450
+#: i2p2www/pages/site/docs/applications/supported.html:456
+#: i2p2www/pages/site/docs/applications/supported.html:462
+#: i2p2www/pages/site/docs/applications/supported.html:472
+#: i2p2www/pages/site/docs/applications/supported.html:478
+#: i2p2www/pages/site/docs/applications/supported.html:490
+#: i2p2www/pages/site/docs/applications/supported.html:523
+#: i2p2www/pages/site/docs/applications/supported.html:529
+#: i2p2www/pages/site/docs/applications/supported.html:535
+#: i2p2www/pages/site/docs/applications/supported.html:541
+#: i2p2www/pages/site/docs/applications/supported.html:618
+#: i2p2www/pages/site/docs/applications/supported.html:627
+#: i2p2www/pages/site/docs/applications/supported.html:633
+#: i2p2www/pages/site/docs/applications/supported.html:695
+#: i2p2www/pages/site/docs/applications/supported.html:710
+#: i2p2www/pages/site/docs/applications/supported.html:716
+#: i2p2www/pages/site/docs/applications/supported.html:722
+#: i2p2www/pages/site/docs/applications/supported.html:728
 msgid "standalone"
 msgstr "independiente"
 
@@ -11360,11 +5617,11 @@ msgstr "independiente"
 #: i2p2www/pages/site/docs/applications/supported.html:202
 #: i2p2www/pages/site/docs/applications/supported.html:208
 #: i2p2www/pages/site/docs/applications/supported.html:214
-#: i2p2www/pages/site/docs/applications/supported.html:349
-#: i2p2www/pages/site/docs/applications/supported.html:373
-#: i2p2www/pages/site/docs/applications/supported.html:382
-#: i2p2www/pages/site/docs/applications/supported.html:538
-#: i2p2www/pages/site/docs/applications/supported.html:544
+#: i2p2www/pages/site/docs/applications/supported.html:362
+#: i2p2www/pages/site/docs/applications/supported.html:386
+#: i2p2www/pages/site/docs/applications/supported.html:395
+#: i2p2www/pages/site/docs/applications/supported.html:551
+#: i2p2www/pages/site/docs/applications/supported.html:557
 msgid "standalone/mod"
 msgstr "independiente/mod"
 
@@ -11382,20 +5639,22 @@ msgstr ""
 "aplicaciones de red sólo necesitan una configuración cuidadosa para poder"
 " ser usadas anónimamente sobre I2P. Estas están etiquetadas como "
 "independientes. Algunas aplicaciones etiquetadas como "
-"independientes/mod, requieren der parcheadas para funcionar bien"
+"independientes/mod, requieren ser parcheadas para funcionar bien"
 " sobre I2P, o para evitar la revelación no intencionada de información "
 "tal como el hostname o la IP externa."
 
 #: i2p2www/pages/site/docs/applications/supported.html:135
 #: i2p2www/pages/site/docs/applications/supported.html:302
-#: i2p2www/pages/site/docs/applications/supported.html:558
-#: i2p2www/pages/site/docs/applications/supported.html:568
-#: i2p2www/pages/site/docs/applications/supported.html:577
-#: i2p2www/pages/site/docs/applications/supported.html:583
-#: i2p2www/pages/site/docs/applications/supported.html:589
-#: i2p2www/pages/site/docs/applications/supported.html:595
-#: i2p2www/pages/site/docs/applications/supported.html:636
-#: i2p2www/pages/site/docs/applications/supported.html:650
+#: i2p2www/pages/site/docs/applications/supported.html:571
+#: i2p2www/pages/site/docs/applications/supported.html:581
+#: i2p2www/pages/site/docs/applications/supported.html:590
+#: i2p2www/pages/site/docs/applications/supported.html:596
+#: i2p2www/pages/site/docs/applications/supported.html:602
+#: i2p2www/pages/site/docs/applications/supported.html:608
+#: i2p2www/pages/site/docs/applications/supported.html:649
+#: i2p2www/pages/site/docs/applications/supported.html:657
+#: i2p2www/pages/site/docs/applications/supported.html:665
+#: i2p2www/pages/site/docs/applications/supported.html:679
 msgid "service"
 msgstr "servicio"
 
@@ -11418,7 +5677,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:148
 #: i2p2www/pages/site/docs/applications/supported.html:220
-#: i2p2www/pages/site/docs/applications/supported.html:355
+#: i2p2www/pages/site/docs/applications/supported.html:368
 msgid "unmaintained"
 msgstr "sin mantenimiento"
 
@@ -11428,7 +5687,7 @@ msgid ""
 "and services which appear to be unmaintained and may be removed from\n"
 "this listing in the future."
 msgstr ""
-"Sin mantenimiento — Es usaao para etiquetar los pluguins, "
+"Sin mantenimiento — Es usado para etiquetar los pluguins, "
 "aplicaciones y servicios que no son actualizados o mantenidos y serán "
 "removidos de la lista en el futuro."
 
@@ -11486,7 +5745,7 @@ msgid ""
 "disclosing personally identifying information, and don't take\n"
 "shortcuts."
 msgstr ""
-"Tome responsabilidad por su propio seguridad y anonimato — busque siempre"
+"Tome responsabilidad por su propia seguridad y anonimato — busque siempre"
 " asesoramiento experto, edúquese usted mismo, use su buen juicio, sea "
 "consciente de si revela información personal, y no tome atajos."
 
@@ -11595,15 +5854,28 @@ msgstr ""
 "Interfaz web simple para emails. Configurado por defecto para usar el "
 "servidor de email Postman."
 
-#: i2p2www/pages/site/docs/applications/supported.html:322
+#: i2p2www/pages/site/docs/applications/supported.html:316
+#, python-format
+msgid ""
+"Can be configured to use Postman's email service. See\n"
+"this comparison of MUAs,\n"
+"and configuration settings for\n"
+"SMTP and POP3."
+msgstr ""
+"Puede configurarse para usar el servicio de email de Postman. Vea \n"
+"esta comparación de MUAs, y las opciones de "
+"configuración para \n"
+"SMTP y POP3."
+
+#: i2p2www/pages/site/docs/applications/supported.html:335
 msgid "I2P's integrated BitTorrent client."
 msgstr "Cliente de BitTorrent de I2P integrado."
 
-#: i2p2www/pages/site/docs/applications/supported.html:328
+#: i2p2www/pages/site/docs/applications/supported.html:341
 msgid "Modified version of I2PSnark."
 msgstr "Versión modificada de I2PSnark."
 
-#: i2p2www/pages/site/docs/applications/supported.html:334
+#: i2p2www/pages/site/docs/applications/supported.html:347
 msgid ""
 "\n"
 "A fork of rufus that uses the Basic Open Bridge (BOB) and has many\n"
@@ -11618,7 +5890,7 @@ msgstr ""
 "instalado, para los torrents sin tracker, y el uso de anlaces imán, "
 "magnet-link, para torrents dentro de I2P.\n"
 
-#: i2p2www/pages/site/docs/applications/supported.html:345
+#: i2p2www/pages/site/docs/applications/supported.html:358
 msgid ""
 "Clean, full-featured cross-platform BitTorrent client with official\n"
 "ports for several GUI toolkits."
@@ -11626,11 +5898,11 @@ msgstr ""
 "Cliente de BitTorrent completo multi plataforma con varios ports para "
 "varios GUIs diferentes."
 
-#: i2p2www/pages/site/docs/applications/supported.html:354
+#: i2p2www/pages/site/docs/applications/supported.html:367
 msgid "Has a plugin providing I2P support."
 msgstr "Contiene un pluguin para usarse con I2P."
 
-#: i2p2www/pages/site/docs/applications/supported.html:361
+#: i2p2www/pages/site/docs/applications/supported.html:374
 #, python-format
 msgid ""
 "For a detailed feature comparison of I2P-enabled trackers/indexers, see\n"
@@ -11639,7 +5911,7 @@ msgstr ""
 "Para una comparación detallada entre trackers/indexadores en I2P, mire aquí."
 
-#: i2p2www/pages/site/docs/applications/supported.html:369
+#: i2p2www/pages/site/docs/applications/supported.html:382
 msgid ""
 "The code that powered one of the first major tracker/indexer sites on the"
 "\n"
@@ -11648,7 +5920,7 @@ msgstr ""
 "El código que que hace funcionar uno de las mayores webs trackers en "
 "Internet. Parcheado para I2P."
 
-#: i2p2www/pages/site/docs/applications/supported.html:378
+#: i2p2www/pages/site/docs/applications/supported.html:391
 #, python-format
 msgid ""
 "Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n"
@@ -11658,20 +5930,20 @@ msgstr ""
 "i2p.opentracker del repositorio Monotone de "
 "I2P."
 
-#: i2p2www/pages/site/docs/applications/supported.html:387
+#: i2p2www/pages/site/docs/applications/supported.html:400
 #, python-format
 msgid ""
 "zzz's Java-based open tracker. More info\n"
 "here."
 msgstr ""
-"zzz's Tracker libre basado en Java. Más "
+"de zzz Tracker libre basado en Java. Más "
 "información aquí."
 
-#: i2p2www/pages/site/docs/applications/supported.html:400
+#: i2p2www/pages/site/docs/applications/supported.html:413
 msgid "I2P port of the aMule ED2K client."
 msgstr "Port para I2P del cliente aMule ED2K."
 
-#: i2p2www/pages/site/docs/applications/supported.html:409
+#: i2p2www/pages/site/docs/applications/supported.html:422
 #, python-format
 msgid ""
 "Port of the Phex Gnutella "
@@ -11682,7 +5954,7 @@ msgstr ""
 "href=\"http://www.phex.org/mambo/\">Phex. La web del pluguin aquí."
 
-#: i2p2www/pages/site/docs/applications/supported.html:418
+#: i2p2www/pages/site/docs/applications/supported.html:431
 #, python-format
 msgid ""
 "Cache for Gnutella peers on I2P. Website for plugin version\n"
@@ -11691,7 +5963,7 @@ msgstr ""
 "Caché de los pares de Gnutella en I2P. Web del pluguin aquí."
 
-#: i2p2www/pages/site/docs/applications/supported.html:433
+#: i2p2www/pages/site/docs/applications/supported.html:446
 msgid ""
 "Unix standard tool for socket relaying. Several clones, ports, and forks\n"
 "have appeared over the years."
@@ -11699,11 +5971,11 @@ msgstr ""
 "Herramienta estándar Unix para la manipulación de sockets. Durante los "
 "años han aparecido varios clons, ports y forks."
 
-#: i2p2www/pages/site/docs/applications/supported.html:442
+#: i2p2www/pages/site/docs/applications/supported.html:455
 msgid "Like netcat but more powerful."
 msgstr "Igual que netcat pero más potente."
 
-#: i2p2www/pages/site/docs/applications/supported.html:448
+#: i2p2www/pages/site/docs/applications/supported.html:461
 msgid ""
 "Proxy providing simple, transparent SOCKS-ification of network "
 "applications."
@@ -11711,7 +5983,7 @@ msgstr ""
 "Proxy que proporciona el uso transparente de SOCKS de las palicaciones de"
 " la red."
 
-#: i2p2www/pages/site/docs/applications/supported.html:458
+#: i2p2www/pages/site/docs/applications/supported.html:471
 msgid ""
 "Most popular implementation of the Secure Shell (SSH) protocol and "
 "related tools."
@@ -11719,15 +5991,15 @@ msgstr ""
 "La implementación más popular del protocolo Secure Shell (SSH) y varias "
 "herramientas relacionadas."
 
-#: i2p2www/pages/site/docs/applications/supported.html:464
+#: i2p2www/pages/site/docs/applications/supported.html:477
 msgid "Open source Secure Shell (SSH) client for Windows."
 msgstr "Cliente para Windows de Secure Shell (SSH) de código libre."
 
-#: i2p2www/pages/site/docs/applications/supported.html:476
+#: i2p2www/pages/site/docs/applications/supported.html:489
 msgid "IM client with multiple incarnations."
 msgstr "Cliente de mensajería, IM, con múltiples encarnaciones."
 
-#: i2p2www/pages/site/docs/applications/supported.html:483
+#: i2p2www/pages/site/docs/applications/supported.html:496
 msgid ""
 "Many IRC clients leak identifying information to servers or other\n"
 "clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound"
@@ -11751,9 +6023,9 @@ msgstr ""
 "de mensajes, DCC y CTCP, no pueden ser anonimizados sin cambios en el "
 "protocolo de los clientes y servidores de IRC, por lo que han sido "
 "completamente bloqueados, excepto para  CTCP ACTION (el mensaje emitido "
-"por el comando /me) que nos peligroso por sí mismo."
+"por el comando /me) que no es peligroso por sí mismo."
 
-#: i2p2www/pages/site/docs/applications/supported.html:494
+#: i2p2www/pages/site/docs/applications/supported.html:507
 msgid ""
 "I2P's IRC filtering may not cover every possible leak — users should also"
 "\n"
@@ -11774,7 +6046,7 @@ msgstr ""
 "los desarrolladores de I2P, podrían ser capaces de arreglarlo añadiendo "
 "algún filtro adicional."
 
-#: i2p2www/pages/site/docs/applications/supported.html:506
+#: i2p2www/pages/site/docs/applications/supported.html:519
 #, python-format
 msgid ""
 "Small Java-based IRC client. Plugin available aquí."
 
-#: i2p2www/pages/site/docs/applications/supported.html:515
+#: i2p2www/pages/site/docs/applications/supported.html:528
 msgid "Cross-platform graphical IRC client."
 msgstr "Cliente de IRC gráfico multi plataforma."
 
-#: i2p2www/pages/site/docs/applications/supported.html:521
+#: i2p2www/pages/site/docs/applications/supported.html:534
 msgid "Unixy terminal-based IRC client."
 msgstr "Cliente de IRC Unix para terminal."
 
-#: i2p2www/pages/site/docs/applications/supported.html:527
+#: i2p2www/pages/site/docs/applications/supported.html:540
 msgid "Another Unixy terminal-based IRC client."
 msgstr "Otro cliente de IRC Unix para terminal."
 
-#: i2p2www/pages/site/docs/applications/supported.html:537
+#: i2p2www/pages/site/docs/applications/supported.html:550
 msgid "IRC server developed from scratch."
 msgstr "Servidor IRC desarrollado desde cero."
 
-#: i2p2www/pages/site/docs/applications/supported.html:543
+#: i2p2www/pages/site/docs/applications/supported.html:556
 msgid "Most popular IRC server."
 msgstr "El servidor IRC más popular."
 
-#: i2p2www/pages/site/docs/applications/supported.html:555
+#: i2p2www/pages/site/docs/applications/supported.html:568
 msgid ""
 "Any website hosted anonymously on I2P, reachable through the I2P router's"
 " HTTP proxy."
@@ -11811,7 +6083,7 @@ msgstr ""
 "Cualquier web alojada anónimamente en I2P, accesible desde el proxy HTTP "
 "del ruter de I2P."
 
-#: i2p2www/pages/site/docs/applications/supported.html:563
+#: i2p2www/pages/site/docs/applications/supported.html:576
 msgid ""
 "Distributed anonymous websites hosted\n"
 "using Tahoe-LAFS-I2P, currently only reachable with Tahoe-LAFS-I2P\n"
@@ -11821,7 +6093,7 @@ msgstr ""
 "sólo accesibles con clientes Tahoe-LAFS-I2P o a través del proxy HTTP "
 "Tahoe-LAFS-I2P."
 
-#: i2p2www/pages/site/docs/applications/supported.html:573
+#: i2p2www/pages/site/docs/applications/supported.html:586
 #, python-format
 msgid ""
 "Website for sponge's jump service.\n"
@@ -11830,24 +6102,24 @@ msgstr ""
 "Web para el servicio de saltos de sponge. Con el código fuente desponible."
 
-#: i2p2www/pages/site/docs/applications/supported.html:582
+#: i2p2www/pages/site/docs/applications/supported.html:595
 msgid "Another jump service."
 msgstr "Otro servicio de saltos."
 
-#: i2p2www/pages/site/docs/applications/supported.html:588
+#: i2p2www/pages/site/docs/applications/supported.html:601
 msgid "Dynamically updated eepsite index."
 msgstr "Índice de eepsites actualizado dinámicamente."
 
-#: i2p2www/pages/site/docs/applications/supported.html:594
+#: i2p2www/pages/site/docs/applications/supported.html:607
 #, python-format
 msgid "Website for zzz's jump service."
 msgstr "Web para el servicio de saltos de zzz"
 
-#: i2p2www/pages/site/docs/applications/supported.html:604
+#: i2p2www/pages/site/docs/applications/supported.html:617
 msgid "SOCKS-enabled caching web proxy with basic filtering capabilities."
 msgstr "Web proxy con cacheo activo SOCKS con la capacidad de filtrado básico."
 
-#: i2p2www/pages/site/docs/applications/supported.html:610
+#: i2p2www/pages/site/docs/applications/supported.html:623
 msgid ""
 "Privacy-focused non-caching web proxy with advanced filtering\n"
 "capabilities. Excels at removing ads and other junk."
@@ -11855,24 +6127,29 @@ msgstr ""
 "Web proxy sin cacheo enfocado a la privacidad con capacidad de filtrado "
 "avanzado. Excelente a la hora de eliminar anuncios y otras mierdas."
 
-#: i2p2www/pages/site/docs/applications/supported.html:619
+#: i2p2www/pages/site/docs/applications/supported.html:632
 msgid "Venerable caching web proxy."
 msgstr "Venerable web proxy con caché."
 
-#: i2p2www/pages/site/docs/applications/supported.html:626
+#: i2p2www/pages/site/docs/applications/supported.html:639
 msgid "Gateways allowing users on the public Internet to access eepsites."
 msgstr ""
 "Salidas que permiten a los usuarios en el Internet público acceder a las "
 "eepsites en I2P."
 
-#: i2p2www/pages/site/docs/applications/supported.html:633
+#: i2p2www/pages/site/docs/applications/supported.html:646
 #, python-format
 msgid "tino's inproxy on the public Internet."
 msgstr ""
 "Proxy de entrada de tino en el Internet "
 "público."
 
-#: i2p2www/pages/site/docs/applications/supported.html:642
+#: i2p2www/pages/site/docs/applications/supported.html:654
+#: i2p2www/pages/site/docs/applications/supported.html:662
+msgid "Another inproxy on the public Internet."
+msgstr "Otro proxy de entrada en la Internet abierta."
+
+#: i2p2www/pages/site/docs/applications/supported.html:671
 msgid ""
 "Gateways allowing I2P users to access content hosted on the public "
 "Internet."
@@ -11880,13 +6157,13 @@ msgstr ""
 "Salidas que permiten a los usuarios de I2P acceder al contenido en el "
 "Internet público."
 
-#: i2p2www/pages/site/docs/applications/supported.html:649
+#: i2p2www/pages/site/docs/applications/supported.html:678
 msgid "Publicly advertised outproxy running Squid, located in Germany."
 msgstr ""
 "Proxy de salida públicamente anunciado que usa Squid, localizado en "
 "Alemania."
 
-#: i2p2www/pages/site/docs/applications/supported.html:659
+#: i2p2www/pages/site/docs/applications/supported.html:688
 msgid ""
 "Lightweight web server and Java servlet container. I2P is tightly\n"
 "integrated with a bundled copy of Jetty which by default is configured to"
@@ -11904,7 +6181,7 @@ msgstr ""
 "Jetty incluida también sirve la consola del ruter de I2P y las "
 "palicaciones web incluidas con I2P."
 
-#: i2p2www/pages/site/docs/applications/supported.html:671
+#: i2p2www/pages/site/docs/applications/supported.html:700
 msgid ""
 "In addition to Jetty, any web server should function over I2P without\n"
 "modification so long as it's HTTP-compliant. Some web servers known to\n"
@@ -11914,25 +6191,25 @@ msgstr ""
 "modificaciones mientras sea compatible con HTTP. Algunos servidores web "
 "usados actualmente para servir contenido en I2P son:"
 
-#: i2p2www/pages/site/docs/applications/supported.html:680
+#: i2p2www/pages/site/docs/applications/supported.html:709
 msgid "Most popular web server on the public WWW."
 msgstr "El servidor web más popular en la WWW pública."
 
-#: i2p2www/pages/site/docs/applications/supported.html:686
+#: i2p2www/pages/site/docs/applications/supported.html:715
 msgid "Web server and Java servlet container. More features than Jetty."
 msgstr "Servidor web en Java servlet container. Con mas funciones que Jetty."
 
-#: i2p2www/pages/site/docs/applications/supported.html:692
+#: i2p2www/pages/site/docs/applications/supported.html:721
 msgid "Fast lightweight web server."
 msgstr "Servidor web rápido y ligero"
 
-#: i2p2www/pages/site/docs/applications/supported.html:698
+#: i2p2www/pages/site/docs/applications/supported.html:727
 msgid "High-performance lightweight web server."
 msgstr "Servidor web ligero de alto rendimiento."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:2
 msgid "Naming discussion"
-msgstr ""
+msgstr "Discusión de nombres"
 
 #: i2p2www/pages/site/docs/discussions/naming.html:4
 #, python-format
@@ -11942,6 +6219,10 @@ msgid ""
 "common arguments and possible alternatives.\n"
 "See the naming page for current documentation."
 msgstr ""
+"NOTA: La siguiente es una discusión de las razones que hay detrás del \n"
+"sistema de nombres de I2P, argumentos comunes y posibles alternativas. \n"
+"Vea en la página de nombres la documentación "
+"actual."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:10
 msgid "Discarded alternatives"
@@ -11958,6 +6239,13 @@ msgid ""
 "DNS-style naming system is clearly out, as are \"majority rules\" voting "
 "systems."
 msgstr ""
+"Los nombres dentro de I2P han sido un tema a menudo debatido desde el "
+"principio mismo, con defensores de todas las posibilidades del espectro."
+" \n"
+"Sin embargo, dada la demanda inherente a I2P de comunicaciones \n"
+"seguras y operaciones descentralizadas, el sistema de nombres \n"
+"tradicional estilo-DNS está claramente desestimado, ya que son\n"
+"sistemas de voto donde la \"mayoría manda\"."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:19
 msgid ""
@@ -11983,6 +6271,23 @@ msgid ""
 " as \n"
 "hostile certificate authority attacks."
 msgstr ""
+"I2P no promociona el uso de servicios tipo-DNS, ya que el \n"
+"daño hecho al secuestrar un sitio puede ser tremedo - y los destinos "
+"inseguros no tienen valor. El propio DNSsec aún se respalda sobre los \n"
+"registradores y las autoridades de certificados, mientras que con I2P las"
+" solicitudes enviadas a un destino no pueden ser interceptadas, o la \n"
+"respuesta falseada (`spoofed`), ya que están cifradas hasta recibir las \n"
+"claves públicas del destino, y un destino en si mismo es sólo un par de "
+"claves públicas y un certificado. Por otra parte, los sistemas estilo-DNS"
+" \n"
+"permiten a cualquiera de los servidores de nombres en la ruta de la \n"
+"consulta, montar sencillos ataques de denegación de servicio (DoS) y de \n"
+"falsificación (`spoofing`). Añadir un certificado autentificando las "
+"respuestas \n"
+"como firmadas por alguna autoridad centralizada de certificados podría \n"
+"solventar muchos de los problemas con servidores de nombres hostiles, \n"
+"pero también dejaría abiertos los ataques de respuesta así como los "
+"ataques de autoridades de certificados hostiles."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:33
 msgid ""
@@ -11998,6 +6303,16 @@ msgid ""
 "if the\n"
 "full network is not queried, different sets of answers may be reachable."
 msgstr ""
+"El estilo de voto de nombres también es peligroso, especialmente \n"
+"dada la efectividad de ataques Sybil en sistemas anónimos - el atacante \n"
+"simplemente puede crear arbitrariamente un alto número de pares (`peers`)"
+" \n"
+"y \"votar\" con cada uno para conquistar un determinado nombre. Métodos "
+"prueba-de-trabajo pueden usarse para hacer la identidad no-gratuita, pero"
+" al crecer la red, la carga necesaria para contactar con todos para "
+"realizar una \n"
+"votación en línea no es plausible, o si no se consulta a la red completa "
+"diferentes grupos de respuestas pueden ser alcanzables."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:42
 msgid ""
@@ -12010,16 +6325,28 @@ msgid ""
 "plug into, allowing end users to drive what sort of naming tradeoffs they"
 " prefer."
 msgstr ""
+"Sin embargo, como sucede con Internet, I2P está manteniendo el diseño\n"
+"y las operaciones de un sistema de nombres fuera de la capa de "
+"comunicación \n"
+"(al estilo-IP). La librería de nombres empaquetada incluye una interfaz "
+"sencilla \n"
+"de proveedor de servicios a la que los sistemas"
+" de nombres alternativos \n"
+"pueden enchufarse, permitiendo a los usuarios finales dirigir la clase de"
+" compromisos de equilibrio con los nombres que ellos prefieran."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:50
 msgid ""
 "See also Names: "
 "Decentralized, Secure, Human-Meaningful: Choose Two."
 msgstr ""
+"Vea también Nombres:"
+" descentralizados, seguros, con-significado-humano: escoja dos."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:55
 msgid "(adapted from a post in the old Syndie, November 26, 2005)"
-msgstr ""
+msgstr "(adaptado desde un post en el antiguo Syndie, 26 de noviembre de 2005)"
 
 #: i2p2www/pages/site/docs/discussions/naming.html:58
 msgid ""
@@ -12029,6 +6356,10 @@ msgid ""
 " not? \n"
 "Who is the right source of a name?"
 msgstr ""
+"P: ¿Qué hacer si algunos servidores no están de acuerdo con una de las \n"
+"direcciones, y si algunas de las direcciones están funcionando y otras "
+"no? \n"
+"¿Quién es la fuente correcta de un nombre?"
 
 #: i2p2www/pages/site/docs/discussions/naming.html:64
 msgid ""
@@ -12040,6 +6371,12 @@ msgid ""
 "unique            .  This is by design, and an inherent part of our need for "
 "security."
 msgstr ""
+"R: Tú no. En realidad esta es una diferencia crítica entre los nombres en"
+" I2P \n"
+"y como funciona DNS - los nombres en I2P son legibles por humanos, \n"
+"seguros, pero no globalmente únicos. Esto es así por diseño, y una"
+" \n"
+"parte inherente de nuestra necesidad de seguridad."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:70
 msgid ""
@@ -12056,16 +6393,28 @@ msgid ""
 "buddy list.  Who you call \"Boss\" may be who someone else calls "
 "\"Sally\"."
 msgstr ""
+"Si yo pudiese convencerle de alguna forma de cambiar la destinación "
+"asociada a algún nombre, yo habría \"tomado control\" de la web, y esto "
+"no es aceptable bajo ninguna circunstancia.  En su lugar, lo que hacemos "
+"es hacer que los nombres sean únicos localmente: son lo que "
+"usted normalmente llamaría un web, al igual que puede llamar a las"
+" cosas como desea cuando las añade los favoritos de su navegador, o a su "
+"lista de amigos de su cliente de mensajería. Aquél al que llama \"jefe\" "
+"puede ser alguien llamado \"Sally\"."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:78
 msgid "Names will not, ever, be securely human readable and globally unique."
 msgstr ""
+"Los nombres no serán, nunca, legibles por humanos con-total-certeza, ni \n"
+"globalmente únicos."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:83
 msgid ""
 "The following from zzz is a review of several common\n"
 "complaints about I2P's naming system."
 msgstr ""
+"Lo siguiente, desde el sitio de zzz, es un compendio de varias quejas \n"
+"comunes acerca del sistema de nombres de I2P."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:89
 msgid ""
@@ -12074,6 +6423,11 @@ msgid ""
 "the etag and last-modified headers).\n"
 "It's about 400K right now for almost 800 hosts."
 msgstr ""
+"Ineficiencia: \n"
+"El fichero hosts.txt completo se descarga (si ha cambiado, ya que eepget"
+" \n"
+"usa la ETag (etiqueta de entidad HTTP) y las últimas cabeceras \n"
+"modificadas). Ahora ocupa alrededor de 400KB para casi 800 servidores."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:94
 msgid ""
@@ -12084,6 +6438,11 @@ msgid ""
 "If you downloaded a hosts.txt file from someone every 12 hours it "
 "averages out to about 10 bytes/sec."
 msgstr ""
+"Cierto, pero esto no es mucho tráfico en el contexto de I2P, que en si \n"
+"mismo es salvajemente ineficiente (bases de datos inundadas, enorme \n"
+"tráfico de control por la encriptación y tráfico por esquemas de relleno,"
+" enrutado ajo (`garlic`), etc.). Si usted descargó un fichero hosts.txt "
+"desde alguien cada 12 horas, esto hace una media de unos 10 bytes/s."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:99
 msgid ""
@@ -12096,6 +6455,16 @@ msgid ""
 " services do, but\n"
 "in a more automated fashion), possibly at a further cost in anonymity."
 msgstr ""
+"Como es habitualmente el caso en I2P, hay un compromiso de equilibrio \n"
+"fundamental aquí entre anonimato y eficiencia. Alguien diría que usar la"
+" \n"
+"ETag y las últimas cabeceras modificadas es arriesgado porque expone la "
+"última vez que solicitó los datos. Otros han sugerido pedir sólo claves"
+" \n"
+"específicas (similar a lo que otros servicios distribuidos ('jump') "
+"hacen, pero \n"
+"de una forma más automatizada), posiblemente a un coste superior en \n"
+"anonimato."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:106
 #, python-format
@@ -12109,6 +6478,18 @@ msgid ""
 "that could be both more efficient and more anonymous than the current "
 "hosts.txt with last-modified and etag."
 msgstr ""
+"Posibles mejoras serían un reemplazo o suplemento a la libreta de "
+"direcciones \n"
+"(vea %(i2host)sp), o algo sencillo "
+"como suscribirse a \n"
+"http://example.i2p/cgi-bin/recenthosts.cgi en lugar de "
+"http://example.i2p/hosts.txt, \n"
+"por ejemplo, si hubiera un hipotético recenthosts.cgi desplegado en todos"
+" \n"
+"los servidores en las últimas 24 horas, que pudiera ser tanto más "
+"eficiente \n"
+"como más anónimo que el actual hosts.txt con las últimas modificaciones\n"
+"y ETag."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:112
 #, python-format
@@ -12123,6 +6504,14 @@ msgid ""
 "\n"
 "does not know about, in an addressbook-compatible manner."
 msgstr ""
+"Una implementación de ejemplo está en stats.i2p en %(url)s.\n"
+"Este script devuelve un ETag con marcas de tiempo. Cuando una solicitud \n"
+"entra con el ETag If-None-Match (si ninguno coincide), el script SÓLO \n"
+"devuelve nuevos servidores desde esa marca de tiempo, o `304 No "
+"Modificado` si no hay ninguno. De esta manera el script devuelve \n"
+"eficientemente sólo los servidores de los que el suscriptor no tenga \n"
+"conocimiento, de una manera compatible-con-la-libreta-de-direcciones."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:121
 msgid ""
@@ -12130,6 +6519,8 @@ msgid ""
 "improve things without\n"
 "radical change."
 msgstr ""
+"Así que la ineficiencia no es un gran problema y hay varias formas de \n"
+"mejorar las cosas sin un cambio radical."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:127
 msgid ""
@@ -12137,6 +6528,10 @@ msgid ""
 "The 400K hosts.txt (with linear search) isn't that big at the moment and\n"
 "we can probably grow by 10x or 100x before it's a problem."
 msgstr ""
+"No escalable: \n"
+"El fichero hosts.txt de 400KB (con búsqueda lineal) no es tan grande de \n"
+"momento, y probablemente podamos crecer por un factor de 10x o 100x antes"
+" de que sea un problema."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:132
 msgid ""
@@ -12146,6 +6541,10 @@ msgid ""
 "a key, you need to have the whole set of keys stored locally, at a cost "
 "of about 500 bytes per key."
 msgstr ""
+"En cuanto al tráfico de red, vea más arriba. Pero a no ser que vaya a "
+"hacer una petición a tiempo real lenta sobre la red para obtener una "
+"clave, necesita tener todo el grupo de claves almacenadas localmente, con"
+" el coste de unos 500 bytes por clave."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:139
 msgid ""
@@ -12154,6 +6553,10 @@ msgid ""
 "http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n"
 "leading to poor new-user experience."
 msgstr ""
+"Requiere configuración y \"confianza\": La libreta de direcciones "
+"lista para usar sólo está suscrita a http://www.i2p2.i2p/hosts.txt, la "
+"cual raramente se actualiza, creando una experiencia pobre para los "
+"principiantes."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:144
 msgid ""
@@ -12163,6 +6566,10 @@ msgid ""
 "The configuration step attempts to force users to think about issues of "
 "trust in an anonymous network."
 msgstr ""
+"Esto es intencionado. jrandom quiere que un usuario \"confíe\" en un "
+"proveedor de host.txt, y como a él le gusta decir, \"la confianza no es "
+"una variable binaria\".  Los pasos de configuración intenta obligar a los"
+" usuarios a pensar sobre los problemas de confianza en una red anónima."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:149
 msgid ""
@@ -12174,6 +6581,11 @@ msgid ""
 "not enough to\n"
 "automatically go fetch the key from them."
 msgstr ""
+"Como otro ejemplo, la página de error \"Eepsite Unknown\" en el proxy "
+"HTTP muestra algunos servicios de salto, pero no \"recomienda\" ninguno "
+"en particular, y es elección del usuario el elegir uno (o no). jramdom "
+"diría que confiamos en los proveedores listados suficientemente como para"
+" mostrarlos pero no como para obtener la clave de ellos automáticamente."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:156
 msgid ""
@@ -12181,16 +6593,22 @@ msgid ""
 "But there must be some sort of hierarchy of trust for the naming system.\n"
 "To treat everyone equally may increase the risk of hijacking."
 msgstr ""
+"¿Cómo es de exitoso este sistema?. No estoy seguro. Pero tiene que haber "
+"algún tipo de jerarquía de confianza en el sistema de nombres/dominios. "
+"El tratar a todo el mundo igual puede aumentar el riesgo de secuestro de "
+"dominios."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:163
 msgid "It isn't DNS"
-msgstr ""
+msgstr "No es DNS"
 
 #: i2p2www/pages/site/docs/discussions/naming.html:166
 msgid ""
 "Unfortunately real-time lookups over i2p would significantly slow down "
 "web browsing."
 msgstr ""
+"Desafortunadamente, las búsquedas en tiempo real sobre I2P relentizarían "
+"significativamente la navegación web."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:169
 msgid ""
@@ -12198,16 +6616,20 @@ msgid ""
 "while i2p\n"
 "keys are permanent."
 msgstr ""
+"Además, DNS está basado en búsquedas con caché y tiempo de vida "
+"limitados, mientras que las claves de i2p son permanentes. "
 
 #: i2p2www/pages/site/docs/discussions/naming.html:173
 msgid "Sure, we could make it work, but why? It's a bad fit."
-msgstr ""
+msgstr "Seguro, podríamos hacerlo funcionar, pero ¿para qué? Sería un mal apaño."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:178
 msgid ""
 "Not reliable:\n"
 "It depends on specific servers for addressbook subscriptions."
 msgstr ""
+"No fiable: Depende de servidores específicos para las "
+"suscripciones de la libreta de direcciones."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:182
 msgid ""
@@ -12221,6 +6643,13 @@ msgid ""
 "something even simpler, like a script that adds everybody in your "
 "hosts.txt to your addressbook."
 msgstr ""
+"Si, depende de los pocos servidores que ha configurado. Dentro de i2p, "
+"los servidores y los servicios van y vienen. Cualquier otros sistema "
+"centralizado (por ejemplo servidores raíz DNS) tendrían los mismos "
+"problemas. Un sistema descentralizado completamente (todo el mundo es una"
+" autoridad) es posible implementando una solución tipo \"todo el mundo es"
+" un servidor raíz DNS\", o con algo incluso más simple, con un script que"
+" añada a todos los que estén en su hosts.txt a su libreta de direcciones."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:190
 msgid ""
@@ -12228,6 +6657,8 @@ msgid ""
 "through\n"
 "the issues of conflicts and hijacking, however."
 msgstr ""
+"La gente que defiende la solución de todos-son-autoridad generalmente no "
+"han pensado en los conflictos y en los secuestros de dominios."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:196
 msgid ""
@@ -12237,10 +6668,15 @@ msgid ""
 "eepsite status reporters.\n"
 "Jump servers and subscriptions are a pain, it should just work like DNS."
 msgstr ""
+"Embarazoso, no es en tiempo real: Es un lío de proveedores de "
+"hosts.txt, proveedores de formularios webs para el añadido de claves, "
+"proveedores de saltos, webs con el estado de las eepsites. Los servicios "
+"de saltos y las suscripciones son molestos, debería simplemente "
+"funcionar, al igual que los DNS."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:202
 msgid "See the reliability and trust sections."
-msgstr ""
+msgstr "Vea las secciones de confianza y seguridad."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:207
 msgid ""
@@ -12248,6 +6684,9 @@ msgid ""
 "or un-scalable,\n"
 "and proposals to \"just use DNS\" aren't well thought-through."
 msgstr ""
+"En resumen, el sistema actual no está terriblemente roto, no es "
+"ineficiente, o no es escalable, y las propuestas de \"simplemente usemos "
+"DNS\" no están bien pensadas."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:212
 msgid "Alternatives"
@@ -12259,28 +6698,37 @@ msgid ""
 "configuration options\n"
 "to enable experimentation with naming systems."
 msgstr ""
+"El código de I2P contiene varios sistemas de dominios listos para "
+"enchufar, y soporta opciones de configuración para permitir experimentar "
+"con sistemas de nombres."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:218
 msgid ""
 "Meta - calls two or more other naming systems in order.\n"
 "By default, calls PetName then HostsTxt."
 msgstr ""
+"Meta - llama a uno o más sistemas de nombres en orden. Por defecto"
+" llama a PetName y después a Hosts Txt."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:222
 msgid ""
 "PetName - Looks up in a petnames.txt file.\n"
 "The format for this file is NOT the same as hosts.txt."
 msgstr ""
+"PetName - busca en el archivo petnames.txt. El formato de este "
+"archivo NO es el mismo que el de "
 
 #: i2p2www/pages/site/docs/discussions/naming.html:226
 msgid "HostsTxt - Looks up in the following files, in order:"
-msgstr ""
+msgstr "HostsTxt - Busca en los siguentes archivos en orden:"
 
 #: i2p2www/pages/site/docs/discussions/naming.html:234
 msgid ""
 "AddressDB - Each host is listed in a separate file in a addressDb/"
 " directory."
 msgstr ""
+"AddressDB - Cada host es listado en un archivo separado en el "
+"directorio addressDb/."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:237
 msgid ""
@@ -12289,6 +6737,9 @@ msgid ""
 "This could augment or replace the jump system.\n"
 "Includes in-memory caching."
 msgstr ""
+"Eepget - hace una búsqueda HTTP en un servidor externo - debe ser "
+"usado después de la búsqueda en HostsTxt con Meta. Esto puede aumentar o "
+"reemplazar al sistema de saltos. Incluye cacheado en-memoria."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:243
 msgid ""
@@ -12297,10 +6748,16 @@ msgid ""
 "Can be used after HostsTxt or as the sole naming system.\n"
 "Includes in-memory caching."
 msgstr ""
+"Exec - llama a un programa externo para las búsquedas, permite "
+"experimentación adicional en los esquemas de búsquedas, "
+"independientemente de java. Puede ser usado después de HostsTxt o como un"
+" sistema de nombres en solitario. Incluye caché en-memoria."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:249
 msgid "Dummy - used as a fallback for Base64 names, otherwise fails."
 msgstr ""
+"Dummy - usado como apoyo para los nombres BAse64, do otra forma "
+"falla."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:253
 msgid ""
@@ -12309,6 +6766,9 @@ msgid ""
 "(restart required).\n"
 "See core/java/src/net/i2p/client/naming for details."
 msgstr ""
+"El sistema actual de dominios puede ser cambiado en la configuración "
+"avanzada 'i2p.naming.impl' (se necesita reiniciar). Vea "
+"core/java/src/net/i2p/client/naming para más detalles."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:258
 msgid ""
@@ -12317,6 +6777,10 @@ msgid ""
 "since addressbook\n"
 "only knows about the hosts.txt files and format."
 msgstr ""
+"Cualquier sistema nuevo debería usarse con HostsTxt, o debería "
+"implementar almacenamiento local o/y las funciones de suscripción de la "
+"libreta de direcciones, ya que la libreta de direcciones sólo conoce el "
+"archivo hosts.txt y su formato."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:264
 msgid "Certificates"
@@ -12335,6 +6799,13 @@ msgid ""
 " a\n"
 "destination. So these will have to be updated to implement certificates."
 msgstr ""
+"Las destinaciones I2P contiene un certificado, aunque hasta el momento "
+"ese certificado es siempre vacío, null. Con un certificado nulo, las "
+"destinaciones base64 son siempre de 516 bytes y terminan en \"AAAA\", y "
+"esto es comprobado en el mecanismo de unión de la libreta de direcciones,"
+" y posiblemente en otros sitios. Además, no hay ningún método disponible "
+"para generar un certificado o añadirlo a la destinación. Con lo que este "
+"debe ser actualizado para implementar los certificados."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:273
 #, python-format
@@ -12342,6 +6813,8 @@ msgid ""
 "One possible use of certificates is for proof of work."
 msgstr ""
+"Un posible uso para los certificados sería para la prueba de trabajo."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:276
 msgid ""
@@ -12350,6 +6823,9 @@ msgid ""
 "i2p uses a flat naming system) to be signed by the 2nd level domain's "
 "keys."
 msgstr ""
+"Otro es para que los \"subdominios\" (entre comillas porque realmente no "
+"existe tal cosa, I2P utiliza un sistema de dominios plano) sean firmados "
+"por las claves de dominio de segundo nivel ."
 
 #: i2p2www/pages/site/docs/discussions/naming.html:280
 msgid ""
@@ -12360,6 +6836,10 @@ msgid ""
 "Is there a method for multiple types of certificates, or multiple "
 "certificates?"
 msgstr ""
+"Con cualquier tipo de implementación de certificados tiene que venir "
+"algún método para verificar los certificados. Probablemente esto debería "
+"en al código de unión de la libreta de direcciones. ¿Hay un método para "
+"múltiples tipos de certificados, o múltiples certificados?"
 
 #: i2p2www/pages/site/docs/discussions/naming.html:286
 msgid ""
@@ -12370,14 +6850,19 @@ msgid ""
 " as \n"
 "hostile certificate authority attacks."
 msgstr ""
+"Añadiendo sobre un certificado, autentificando la respuesta como firmada "
+"por alguna autoridad certificada centralizada podría solucionar muchos de"
+" los problemas con los servidores de nombres hostiles, pero lo dejaría "
+"abierto a ataques de respuesta, al igual que a los ataques desde una "
+"autoridad de certificados hostil."
 
 #: i2p2www/pages/site/docs/how/cryptography.html:2
 msgid "Low-level Cryptography Details"
-msgstr ""
+msgstr "Detalles de bajo nivel de los cifrados"
 
 #: i2p2www/pages/site/docs/how/cryptography.html:6
 msgid "This page specifies the low-level details of the cryptography in I2P."
-msgstr ""
+msgstr "Esta página especifica los detalles de bajo nivel de los cifrados en I2P."
 
 #: i2p2www/pages/site/docs/how/cryptography.html:10
 #, python-format
@@ -12397,6 +6882,16 @@ msgid ""
 "technique used in ElGamal/AES+SessionTag "
 "(but we're sure others have done it)."
 msgstr ""
+"Hay bastantes algoritmos de cifrado en uso dentro de I2P, pero los hemos "
+"reducido al mínimo para ajustarse a nuestras necesidades - un cifrado "
+"simétrico, un cifrado asimétrico, un algoritmo de firma y un algoritmo de"
+" hashing. Sin embargo, los combinamos de forma especial para proporcionar"
+" integridad en los mensajes (en vez de depender de una MAC). Además, y "
+"aunque odiamos el crear cosas nuevas en los que se refiere a cifrados, no"
+" hemos podido encontrar ninguna referencia discutiendo (o incluso "
+"nombrando) la técnica usada en el  ElGamal/AES+SessionTag (pero estamos seguros "
+"que otros ya lo han usado)."
 
 #: i2p2www/pages/site/docs/how/cryptography.html:20
 msgid "ElGamal encryption"
@@ -12408,6 +6903,9 @@ msgid ""
 "ElGamal is used for asymmetric encryption.\n"
 "ElGamal is used in several places in I2P:"
 msgstr ""
+"\n"
+"ElGamal es usado para el cifrado asimétrico. ElGamal es usado en varios "
+"sitios de I2P."
 
 #: i2p2www/pages/site/docs/how/cryptography.html:27
 #, python-format
@@ -12415,6 +6913,8 @@ msgid ""
 "To encrypt router-to-router Tunnel Build "
 "Messages"
 msgstr ""
+"Para cifrar los mensajes de creación de "
+"túnel de ruter a ruter."
 
 #: i2p2www/pages/site/docs/how/cryptography.html:30
 #, python-format
@@ -12424,9 +6924,13 @@ msgid ""
 "using the encryption key in the LeaseSet"
 msgstr ""
+"Para el cifrado de fin a fin (destinación a destinación) como parte de  "
+"ElGamal/AES+SessionTag usando la clave de "
+"cifrado en el LeaseSet"
 
 #: i2p2www/pages/site/docs/how/cryptography.html:34
-#: i2p2www/pages/site/docs/how/cryptography.html:189
+#: i2p2www/pages/site/docs/how/cryptography.html:198
 #, python-format
 msgid ""
 "For encryption of some netDb stores and "
@@ -12434,6 +6938,10 @@ msgid ""
 "as a part of ElGamal/AES+SessionTag\n"
 "(destination-to-router or router-to-router)."
 msgstr ""
+"Para el cifrado de algunos almacenamientos"
+" en la netDb y peticiones enviadas a los ruters floodfill como parte "
+"de ElGamal/AES+SessionTag (destinación a "
+"ruter o ruter a ruter)"
 
 #: i2p2www/pages/site/docs/how/cryptography.html:41
 msgid ""
@@ -12443,10 +6951,15 @@ msgid ""
 "single block, followed by the \n"
 "AES encrypted payload using that key and IV."
 msgstr ""
+"Usamos primos comunes para el cifrado y descifrado de ElGamal 2048, como "
+"se indica en IETF "
+"RFC-3526. Actualmente sólo usamos ELGamal para cifrar el IV y la "
+"clave de sesión en un solo bloque, seguido por el payload cifrado AES "
+"usando la clave y el IV."
 
 #: i2p2www/pages/site/docs/how/cryptography.html:47
 msgid "The unencrypted ElGamal contains:"
-msgstr ""
+msgstr "ElGamal sin cifrar contiene: "
 
 #: i2p2www/pages/site/docs/how/cryptography.html:64
 msgid ""
@@ -12462,6 +6975,14 @@ msgid ""
 "the cleartext to 222 bytes with random data.\n"
 "Total length: typically 255 bytes."
 msgstr ""
+"La H(datos) es el SHA256 de los datos cifrados en al bloque ElGamal, y es"
+" precedido por un byte distinto de cero. El byte puede ser aleatorio, "
+"pero como está implementado es siempre 0xFF. Podría usarse en el futuro "
+"para las banderas. Los datos cifrados en el bloque pueden ser de hasta "
+"222 bytes de largo. Ya que los datos cifrados pueden contener un gran "
+"número de ceros si el texto en plano es menor de 222 bytes, se recomienda"
+" que las capas superiores rellenen el texto en plano con datos aleatorios"
+" hasta los 222 bytes. Tamaño total: normalmente 255 bytes."
 
 #: i2p2www/pages/site/docs/how/cryptography.html:76
 msgid "The encrypted ElGamal contains:"
@@ -12477,11 +6998,16 @@ msgid ""
 "This is encoded as two 256-byte encrypted parts,\n"
 "and there is a single byte of zero padding before each part at this layer."
 msgstr ""
+"Cada parte cifrada es precedida con ceros hasta el tamaño de 257 bytes. "
+"Tamaño total: 514 bytes. En un uso normal, las capas superiores colocan "
+"el texto en plano hasta los 222 bytes, resultando en un bloque no cifrado"
+" de 255 bytes. Esto es codificado como dos partes cifradas de 256 bytes, "
+"y hay un solo byte cero de relleno antes de cada parte de esta capa."
 
 #: i2p2www/pages/site/docs/how/cryptography.html:111
 #, python-format
 msgid "See the ElGamal code."
-msgstr ""
+msgstr "Vea el código ElGamal."
 
 #: i2p2www/pages/site/docs/how/cryptography.html:115
 msgid ""
@@ -12489,37 +7015,46 @@ msgid ""
 "[Oakley prime "
 "for 2048 bit keys]"
 msgstr ""
+"El primo compartido es el [primo Oakley para "
+"las claves de  2048 bits]"
 
 #: i2p2www/pages/site/docs/how/cryptography.html:122
 msgid "or as a hexadecimal value:"
-msgstr ""
+msgstr "o un valor hexadecimal:"
 
 #: i2p2www/pages/site/docs/how/cryptography.html:138
 msgid "Using 2 as the generator."
-msgstr ""
+msgstr "Usando 2 como generador."
 
 #: i2p2www/pages/site/docs/how/cryptography.html:142
 msgid "Short Exponent"
-msgstr ""
+msgstr "Exponente corto"
 
 #: i2p2www/pages/site/docs/how/cryptography.html:143
 #, python-format
 msgid ""
 "While the standard exponent size is 2048 bits (256 bytes) and the I2P\n"
 "PrivateKey\n"
-"is a full 256 bytes,\n"
-"we use the short exponent size of 226 bits (28.25 bytes).\n"
+"is a full 256 bytes, in some cases\n"
+"we use the short exponent size of 226 bits (28.25 bytes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:150
+#, python-format
+msgid ""
 "This should be safe for use with the Oakley primes, per\n"
 "On Diffie-Hellman Key Agreement with Short Exponents "
 "- van Oorschot, Weiner\n"
 "at EuroCrypt 96, and crypto++'s "
 "benchmarks.\n"
-"Benchmarks originally at %(oldbenchmarks)s (now dead),\n"
+"Benchmarks originally at this link, now dead,\n"
 "rescued from the wayback machine,"
 " dated Apr 23, 2008."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:158
+#: i2p2www/pages/site/docs/how/cryptography.html:160
 #, python-format
 msgid ""
 "Also, Koshiba & Kurosawa: Short Exponent Diffie-"
@@ -12529,45 +7064,70 @@ msgid ""
 "this sci.crypt thread.\n"
 "The remainder of the PrivateKey is padded with zeroes."
 msgstr ""
+"También Koshiba & Kurosawa: Short Exponent "
+"Diffie-Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186) (texto completo en Google Books) aparentemente "
+"los soporta, de acuerdo con este hilo "
+"sci.crypt. El resultado del PrivateKey es rellenado con ceros."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:167
-#: i2p2www/pages/site/docs/how/cryptography.html:264
-#: i2p2www/pages/site/docs/how/cryptography.html:343
-#: i2p2www/pages/site/docs/how/cryptography.html:382
-msgid "Obsolescence"
+#: i2p2www/pages/site/docs/how/cryptography.html:169
+msgid ""
+"Prior to release 0.9.8, all routers used the short exponent.\n"
+"As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent.\n"
+"Other routers continue to use the short exponent due to concerns about "
+"processor load.\n"
+"The transition to a longer exponent for these platforms is a topic for "
+"further study."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:168
+#: i2p2www/pages/site/docs/how/cryptography.html:176
+#: i2p2www/pages/site/docs/how/cryptography.html:273
+#: i2p2www/pages/site/docs/how/cryptography.html:352
+#: i2p2www/pages/site/docs/how/cryptography.html:391
+msgid "Obsolescence"
+msgstr "Obsolescencia "
+
+#: i2p2www/pages/site/docs/how/cryptography.html:177
 msgid ""
 "The vulnerability of the network to an ElGamal attack and the impact of "
 "transitioning to a longer bit length is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
-
-#: i2p2www/pages/site/docs/how/cryptography.html:176
-msgid "AES is used for symmetric encryption, in several cases:"
-msgstr ""
-
-#: i2p2www/pages/site/docs/how/cryptography.html:181
-msgid "For transport encryption after DH key exchange"
-msgstr ""
+"Las vulnerabilidades de la red a un ataque ElGamal y el impacto de una "
+"transición a un tamaño mayor no han sido aún estudiados. Podría ser muy "
+"difícil hacer cambios que fuesen compatibles hacia atrás. "
 
 #: i2p2www/pages/site/docs/how/cryptography.html:185
+msgid "AES is used for symmetric encryption, in several cases:"
+msgstr "AES es utilizado para el cifrado simétrico en varios casos:"
+
+#: i2p2www/pages/site/docs/how/cryptography.html:190
+msgid "For transport encryption after DH key exchange"
+msgstr ""
+"Para el cifrado de transporte después del "
+"intercambio de la clave DH."
+
+#: i2p2www/pages/site/docs/how/cryptography.html:194
 #, python-format
 msgid ""
 "For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag"
 msgstr ""
+"Para los cifrados de fin a fin (destinación a destinación) como parte de "
+"ElGamal/AES+SessionTag"
 
-#: i2p2www/pages/site/docs/how/cryptography.html:195
+#: i2p2www/pages/site/docs/how/cryptography.html:204
 #, python-format
 msgid ""
 "For encryption of periodic tunnel "
 "test messages sent from the router to itself, through its own "
 "tunnels."
 msgstr ""
+"Para el cifrado de los mensajes "
+"periódicos de pruebas de túnel, enviado desde un ruter a sí mismo a "
+"través de sus propios túneles."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:200
+#: i2p2www/pages/site/docs/how/cryptography.html:209
 #, python-format
 msgid ""
 "We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n"
@@ -12581,28 +7141,40 @@ msgid ""
 " in the\n"
 "ElGamalAESEngine.getPadding function."
 msgstr ""
+"Usamos AES con claves de 256 bytes y con bloques de 128 bits en modo CBC."
+" El rellenado usado está especificado en IETF "
+"RFC-2313 (PKCS#5 1.5, sección 8.1 (para bloques de tipo 02)). En este"
+" caso, el relleno es creado aleatoriamente en octetos para ajustarse a "
+"los bloques de 16 bytes. Específicamente vea [the "
+"CBC code] y el Cryptix AES [implementación], al igual que el relleno "
+"encontrado en la función ElGamalAESEngine.getPadding."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:265
+#: i2p2www/pages/site/docs/how/cryptography.html:274
 msgid ""
 "The vulnerability of the network to an AES attack and the impact of "
 "transitioning to a longer bit length is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
+"Las vulnerabilidades de la red a un ataque AES y el impacto del cambio a "
+"unas clave más grande no han sido estudiados aún. Podría ser realmente "
+"difícil hacer cambios que fuesen compatibles hacia atrás."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:270
-#: i2p2www/pages/site/docs/how/cryptography.html:362
-#: i2p2www/pages/site/docs/how/cryptography.html:388
-#: i2p2www/pages/site/docs/how/cryptography.html:456
+#: i2p2www/pages/site/docs/how/cryptography.html:279
+#: i2p2www/pages/site/docs/how/cryptography.html:371
+#: i2p2www/pages/site/docs/how/cryptography.html:397
+#: i2p2www/pages/site/docs/how/cryptography.html:465
 #: i2p2www/pages/site/docs/how/garlic-routing.html:281
 #: i2p2www/pages/site/docs/how/peer-selection.html:296
 msgid "References"
 msgstr "Referencias"
 
-#: i2p2www/pages/site/docs/how/cryptography.html:273
+#: i2p2www/pages/site/docs/how/cryptography.html:282
 msgid "Feb. 7, 2006 Status Notes"
-msgstr ""
+msgstr "Notas de estado, 7 Feb. 2006"
 
-#: i2p2www/pages/site/docs/how/cryptography.html:280
+#: i2p2www/pages/site/docs/how/cryptography.html:289
 #, python-format
 msgid ""
 "Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), "
@@ -12610,12 +7182,16 @@ msgid ""
 "[DSAEngine].\n"
 "DSA was chosen because it is much faster for signatures than ElGamal."
 msgstr ""
+"Las firmas son generadas y verificadas con DSA de 1024 bits (L=1024, "
+"N=160), al igual que está implementado en [DSAEngine]. DSA fue escogida porque es mucho más "
+"rápida para firmar que ElGamal."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:286
+#: i2p2www/pages/site/docs/how/cryptography.html:295
 msgid "The DSA constants"
-msgstr ""
+msgstr "Las constantes DSA"
 
-#: i2p2www/pages/site/docs/how/cryptography.html:337
+#: i2p2www/pages/site/docs/how/cryptography.html:346
 #, python-format
 msgid ""
 "The Signing Public"
@@ -12623,8 +7199,12 @@ msgid ""
 "The Signing "
 "Private Key is 160 bits."
 msgstr ""
+"La clave pública "
+"de firma es de 1024 bits. La clave privada de "
+"firma es de 160 bits."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:344
+#: i2p2www/pages/site/docs/how/cryptography.html:353
 #, python-format
 msgid ""
 "NIST 800-57\n"
@@ -12632,8 +7212,11 @@ msgid ""
 "This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a "
 "given key."
 msgstr ""
+"NIST 800-57 recomienda un mínimo de (L=2048, "
+"N=224) para su uso más allá del 2010. Esto puede mitigarse de alguna "
+"forma con el \"cryptoperiod\", o tiempo de vida dado a una clave."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:350
+#: i2p2www/pages/site/docs/how/cryptography.html:359
 msgid ""
 "The prime number was chosen in 2003,\n"
 "and the person that chose the number (TheCrypto) is currently no longer "
@@ -12642,39 +7225,56 @@ msgid ""
 "If a larger prime is chosen for future purposes, this should be a strong "
 "prime, and we will document the construction process."
 msgstr ""
+"El número primo fue escogido en el "
+"2003, y la persona que lo eligió (TheCrypto) no es ya un "
+"desarrollador de I2P. Por eso, no sabemos si el primo escogido es un "
+"'primo fuerte'. Si en el futuro se elige un nuevo primo, debería ser un "
+"primo fuerte y documentaremos el proceso de construcción."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:357
+#: i2p2www/pages/site/docs/how/cryptography.html:366
 msgid ""
 "The vulnerability of the network to a DSA attack and the impact of "
 "transitioning to longer keys is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
+"Las vulnerabilidades de la red a un ataque DSA y el impacto del cambio a "
+"unas clave más grande no han sido estudiados aún. Podría ser realmente "
+"difícil hacer cambios que fuesen compatibles hacia atrás."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:365
-#: i2p2www/pages/site/docs/how/cryptography.html:367
+#: i2p2www/pages/site/docs/how/cryptography.html:374
+#: i2p2www/pages/site/docs/how/cryptography.html:376
 #, python-format
 msgid "Meeting %(num)s"
-msgstr ""
+msgstr "Reunión %(num)s "
 
-#: i2p2www/pages/site/docs/how/cryptography.html:369
+#: i2p2www/pages/site/docs/how/cryptography.html:378
 msgid "Choosing the constants"
-msgstr ""
+msgstr "Eligiendo las constantes"
 
-#: i2p2www/pages/site/docs/how/cryptography.html:377
+#: i2p2www/pages/site/docs/how/cryptography.html:386
 #, python-format
 msgid ""
 "Hashes within I2P are plain old SHA256, as implemented in\n"
 "[SHA256Generator]"
 msgstr ""
+"Los hashes en I2P son hashes planos viejos SHA256, como se implementaron "
+"en [SHA256Generator]"
 
-#: i2p2www/pages/site/docs/how/cryptography.html:383
+#: i2p2www/pages/site/docs/how/cryptography.html:392
 msgid ""
 "The vulnerability of the network to a SHA-256 attack and the impact of "
 "transitioning to a longer hash is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
+"Las vulnerabilidades de la red a un ataque SHA-256 y el impacto del "
+"cambio a una hash más grande no han sido estudiados aún. Podría ser "
+"realmente difícil hacer cambios que fuesen compatibles hacia atrás."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:395
+#: i2p2www/pages/site/docs/how/cryptography.html:403
+msgid "Transports"
+msgstr "Transportes"
+
+#: i2p2www/pages/site/docs/how/cryptography.html:404
 msgid ""
 "At the lowest protocol layer,\n"
 "point-to-point inter-router communication is protected by the transport "
@@ -12689,12 +7289,20 @@ msgid ""
 "forward secrecy\n"
 "on the transport links."
 msgstr ""
+"En la capa del protocolo más baja, la comunicación entre ruters punto a "
+"punto es protegida por la seguridad de la capa de transporte. Ambos "
+"transportes usan claves de intercambio de 256 bytes (2048 bit) Diffie-"
+"Hellman usando el mismo primo y generador "
+"compartidos como se especifica arriba para ElGamal, seguido por el "
+"cifrado simétrico AES como se describe arriba. Esto proporciona un perfecto"
+" secreto en el envío en los enlaces de transporte."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:407
+#: i2p2www/pages/site/docs/how/cryptography.html:416
 msgid "NTCP connections"
 msgstr "Conexiones NTCP"
 
-#: i2p2www/pages/site/docs/how/cryptography.html:409
+#: i2p2www/pages/site/docs/how/cryptography.html:418
 #, python-format
 msgid ""
 "NTCP connections are negotiated with a 2048 Diffie-Hellman "
@@ -12710,36 +7318,53 @@ msgid ""
 "forward secrecy', while ElGamalAES+SessionTag does not."
 msgstr ""
+"Las conexiones NTCP son negociadas con una implementación 2048 Diffie-"
+"Hellman, usando la identidad del ruter para crear un acuerdo/contrato de "
+"estación a estación, seguido de algunos campos específicos para "
+"protocolos cifrados, con todos los datos subsecuentes cifrados con AES "
+"(como arriba). La principal razón para hacer la negociación DH en vez de "
+"usar ElGamalAES+SessionTag es que "
+"proporciona 'secreto de "
+"envío (perfecto)', mientras que ElGamalAES+SessionTag no lo hace."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:417
+#: i2p2www/pages/site/docs/how/cryptography.html:426
 msgid ""
 "In order to migrate to a more standardized implementation (TLS/SSL or "
 "even SSH), the following issues must be addressed:"
 msgstr ""
+"Para poder migrar a una implementación más estándar (TLS/SSL o incluso "
+"SSH), se deben arreglar los siguientes problemas:"
 
-#: i2p2www/pages/site/docs/how/cryptography.html:421
+#: i2p2www/pages/site/docs/how/cryptography.html:430
 msgid ""
 "Can we somehow reestablish sessions securely (ala session tags) or do we "
 "need to do full negotiation each time?"
 msgstr ""
+"¿Podemos restablecer sesiones de forma segura (tipo etiquetas de sesión) "
+"o necesitamos hacer una negociación completa cada vez?"
 
-#: i2p2www/pages/site/docs/how/cryptography.html:424
+#: i2p2www/pages/site/docs/how/cryptography.html:433
 msgid ""
 "Can we simplify/avoid the x509 or other certificate formats and use our "
 "own RouterInfo structure (which \n"
 "contains the ElGamal and DSA keys)?"
 msgstr ""
+"¿Podemos simplemente evitar el x509 u otros formatos de certificados "
+"usados en nuestra estructura del RouterInfo (la cual contiene las claves "
+"ElGamal y DSA)?"
 
-#: i2p2www/pages/site/docs/how/cryptography.html:429
+#: i2p2www/pages/site/docs/how/cryptography.html:438
 #, python-format
 msgid "See the NTCP specification for details."
-msgstr ""
+msgstr "Vea la especificación NTCP para más detalles."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:433
+#: i2p2www/pages/site/docs/how/cryptography.html:442
 msgid "UDP connections"
 msgstr "Conexiones UDP"
 
-#: i2p2www/pages/site/docs/how/cryptography.html:434
+#: i2p2www/pages/site/docs/how/cryptography.html:443
 msgid ""
 "SSU (the UDP transport) encrypts each packet with AES256/CBC with both an"
 " explicit IV and MAC \n"
@@ -12751,13 +7376,21 @@ msgid ""
 "integrity \n"
 "checking."
 msgstr ""
+"SSU (el transporte UDP) cifra cada paquete con AES256/CBC con un IV "
+"explícito y la MAC (HMAC-MD5-128) después de acordar una clave de sesión "
+"efímera a través del sistema de intercambio Diffie-Hellman de 2048 bits, "
+"autenticación estación a estación con la clave DSA del otro ruter, además"
+" cada mensaje de red tiene su propio hash para su comprobar su integridad"
+" localmente."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:442
+#: i2p2www/pages/site/docs/how/cryptography.html:451
 #, python-format
 msgid "See the SSU specification for details."
 msgstr ""
+"Vea las especificaciones de SSU para más "
+"detalles."
 
-#: i2p2www/pages/site/docs/how/cryptography.html:446
+#: i2p2www/pages/site/docs/how/cryptography.html:455
 #, python-format
 msgid ""
 "WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n"
@@ -12769,10 +7402,16 @@ msgid ""
 "the 2005-07-05 status notes\n"
 "for details."
 msgstr ""
+"CUIDADO - el HMAC-MD5-128 de I2P usado en el SSU aparentemente no es "
+"estándar. Aparentemente, una versión anterior de SSU usaba HMAC-SHA256, y"
+" después fue cambiada a MD5-128 por razones de rendimiento, pero dejaron "
+"el tamaño del buffer de 32 bytes intacto. Vea HMACGenerator.java y las notas de estado del 2005-07-05 para más "
+"detalles."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:2
 msgid "ElGamal/AES + SessionTag Encryption"
-msgstr ""
+msgstr "Cifrado ElGamal/AES + SessionTag"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:3
 msgid "February 2011"
@@ -12780,7 +7419,7 @@ msgstr "Febrero de 2011"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:7
 msgid "ElGamal/AES+SessionTags is used for end-to-end encryption."
-msgstr ""
+msgstr "ElGamal/AES+SessionTags es usado para los cifrados de fin a fin."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:11
 msgid ""
@@ -12794,6 +7433,13 @@ msgid ""
 "describe \n"
 "the use of 2048bit ElGamal, AES256, SHA256, and 32 byte nonces."
 msgstr ""
+"Como un sistema basado en mensajes no ordenados y no fiable que es, I2P "
+"usa una combinación simple de algoritmos de cifrados simétricos y "
+"asimétricos para proporcionar la confidencialidad de los datos y la "
+"integridad de los mensajes garlic. En conjunto, la combinación es llamada"
+" ElGamal/AES+SessionTags, pero es una forma excesivamente larga de "
+"describir el uso de ElGamal de 2048 bits, AES256, SHA256 y nonces de 32 "
+"bytes."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:19
 #: i2p2www/pages/site/docs/how/tech-intro.html:512
@@ -12877,12 +7523,13 @@ msgstr ""
 "ElGamal/AES elije cuando y cuantas etiquetas a enviar, poniendo a "
 "disposición del que recibe suficientes etiquetas para trabajar con un "
 "buen número de mensajes. Los mensajes Garlic pueden detectar la llegada "
-"exitosas de las etiquetas construyendo un mensaje adicional tipo clavo "
+"exitosas de las etiquetas construyendo un mensaje adicional tipo clove "
 "(un \"mensaje de estado de entrega\") - cuando el mensaje llega al "
 "destinatario elegido y es descifrado correctamente, este pequeño mensaje "
-"de estado de entrega es uno de los clavos expuestos y tiene instrucciones"
-" para el destinatario para que retorne al remitente original (a través de"
-" un túnel de entrada, claro). Cuando el remitente original \n"
+"de estado de entrega es uno de los dientes expuestos y tiene "
+"instrucciones para el destinatario para que retorne al remitente original"
+" (a través de un túnel de entrada, claro). Cuando el remitente original"
+" \n"
 "recibe el mensaje de estado de envío, sabe que la etiqueta de sesión "
 "incluida en el mensaje garlic ha sido enviada exitosamente."
 
@@ -12903,12 +7550,24 @@ msgid ""
 "A session will continue to exist until all its tags are exhausted or "
 "expire."
 msgstr ""
+"Las etiquetas de sesión tienen un vida muy corta, después de la cual son "
+"descartadas y no se usan más. Además, el número almacenado de ellas por "
+"cada clave es limitado, como también está limitado el número de claves - "
+"si llegan demasiadas, serán descartados los mensajes nuevos o los viejos."
+" El remitente lleva el seguimiento de los mensajes con etiquetas de "
+"sesión que pasan a través suyo, y si no hay comunicación suficiente "
+"podría descartar los mensajes supuestamente enviados correctamente, "
+"volviendo al costoso cifrado ElGamal. Una sesión continuará existiendo "
+"hasta que todas las etiquetas hayan expirado."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:61
 msgid ""
 "Sessions are unidirectional. Tags are delivered from Alice to Bob,\n"
 "and Alice then uses the tags, one by one, in subsequent messages to Bob."
 msgstr ""
+"Las sesiones son unidireccionales. Las etiquetas son enviadas desde Alice"
+" a Bob, y Alice entonces utiliza las etiquetas, una a una, en los "
+"siguientes mensajes hacia Bob."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:66
 msgid ""
@@ -12920,26 +7579,35 @@ msgid ""
 "Destinations\n"
 "to each other or a Router by adversaries."
 msgstr ""
+"Las sesiones puede establecerse entre Destinaciones, entre Ruters o entre"
+" Ruters y Destinaciones. Cada ruter y destinación mantiene su "
+"administrador de claves de sesión para hacer el seguimiento de las claves"
+" de sesión y las etiquetas de sesión. Al haber administradores de claves "
+"de sesión separados se previene que los adversarios puedan hacer "
+"correlación de las múltiples destinaciones que hay entre cada uno o entre"
+" ruters."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:77
 msgid "Message Reception"
-msgstr ""
+msgstr "Recepción del Mensaje"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:78
 msgid ""
 "Each message received has one of two\n"
 "the two possible conditions:
            "
-msgstr ""
+msgstr "Cada mensaje recibido tiene una de estas dos posibles condiciones:
            "
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:84
 msgid ""
 "It is part of an existing session and contains a Session Tag and an AES "
 "encrypted block"
 msgstr ""
+"Es parte de una sesión ya existente y contiene una etiqueta de sesión y "
+"un bloque cifrado AES."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:85
 msgid "It is for a new session and contains both ElGamal and AES encrypted blocks"
-msgstr ""
+msgstr "Es para una nueva sesión y contiene los bloques cifrados ElGamal y AES."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:88
 msgid ""
@@ -12949,10 +7617,14 @@ msgid ""
 "If that fails, it will assume it is for a new session and attempt to\n"
 "decrypt it using ElGamal."
 msgstr ""
+"Cuando un ruter recibe un mensaje, primero asumirá que es de una sesión "
+"ya existente e intentará buscar la etiqueta de sesión y descifrar los "
+"datos usando AES. Si esto falla, asumirá que es para una nueva sesión e "
+"intentará descifrarlo usando ElGamal."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:97
 msgid "New Session Message Specification"
-msgstr ""
+msgstr "Especificaciones de los mensajes de nueva sesión."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:98
 msgid ""
@@ -12960,6 +7632,8 @@ msgid ""
 "block\n"
 "and an encrypted AES block."
 msgstr ""
+"Un mensaje de nueva sesión ElGamal contiene dos partes, un bloque cifrado"
+" ElGamal y un bloque cifrado AES."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:103
 msgid "The encrypted message contains:"
@@ -12971,11 +7645,11 @@ msgstr "Bloque ElGamal"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:128
 msgid "The encrypted ElGamal Block is always 514 bytes long."
-msgstr ""
+msgstr "El bloque cifrado ElGamal es siempre de 514 bytes."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:132
 msgid "The unencrypted ElGamal data is 222 bytes long, containing:"
-msgstr ""
+msgstr "Los datos no cifrados ElGamal son de 222 bytes de largo, y contienen:"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:164
 #, python-format
@@ -12987,6 +7661,10 @@ msgid ""
 " follows;\n"
 "the IV is the first 16 bytes of the SHA-256 Hash of the Pre-IV."
 msgstr ""
+"La clave de sesión "
+"de 32 bytes es el identificador de sesión. El Pre-IV de 32 bytes es usado"
+" para generar el IV para el bloque AES siguiente; el IV son los primeros "
+"16 bytes del Hash SHA-256 del Pre-IV."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:172
 #, python-format
@@ -12996,6 +7674,9 @@ msgid ""
 "and the encrypted block is 514 bytes long.\n"
 "
            "
 msgstr ""
+"El payload de 222 bytes es cifrado usando ElGamal y el bloque cifrado "
+"es de 514 bytes de largo."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:179
 msgid "AES Block"
@@ -13003,12 +7684,14 @@ msgstr "Bloque AES"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:180
 msgid "The unencrypted data in the AES block contains the following:"
-msgstr ""
+msgstr "Los datos sin cifrar en el bloque AES contienen los siguiente:"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:224
 #, python-format
 msgid "2-byte Integer, 0-200"
 msgstr ""
+"Un entero  de 2 bytes, "
+"0-200"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:228
 #, python-format
@@ -13016,11 +7699,13 @@ msgid ""
 "That many 32-byte Session Tags"
 msgstr ""
+"Muchas etiquetas de "
+"sesión de 32 bytes"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:232
 #, python-format
 msgid "4-byte Integer"
-msgstr ""
+msgstr "Un entero de 4 bytes"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:236
 #, python-format
@@ -13028,10 +7713,14 @@ msgid ""
 "The 32-byte SHA256 Hash of"
 " the payload"
 msgstr ""
+"El Hash SHA256 de 32 bytes"
+" del payload"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:240
 msgid "A one-byte value. Normally == 0. If == 0x01, a Session Key follows"
 msgstr ""
+"Un valor de 1 byte. Normalmente == 0. Si == 0x01, lo siguiente es una "
+"clave de sesión"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:244
 #, python-format
@@ -13041,20 +7730,25 @@ msgid ""
 "                 to replace the old key, and is only present if preceding"
 " flag is 0x01"
 msgstr ""
+"Una clave de sesión "
+"de 32 bytes, para reemplazar la clave vieja, y sólo está presente si la "
+"bandera precedente es 0x01"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:249
 msgid "the data"
-msgstr ""
+msgstr "los datos"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:251
 msgid ""
 "Random data to a multiple of 16 bytes for the total length.\n"
 "         May contain more than the minimum required padding."
 msgstr ""
+"Datos aleatorios múltiplos de 16 bytes hasta el tamaño total. Puede "
+"contener más que el relleno mínimo requerido."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:256
 msgid "Minimum length: 48 bytes"
-msgstr ""
+msgstr "Tamaño mínimo : 48 bytes"
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:260
 #, python-format
@@ -13066,6 +7760,12 @@ msgid ""
 " bytes.\n"
 "
            "
 msgstr ""
+"Los datos están entonces Cifrados con "
+"AES, usando \n"
+"la clave de sesión y el IV (Vector de Inicialización, calculado con el "
+"pre-IV) \n"
+"desde la sección ElGamal. El tamaño del bloque cifrado con AES \n"
+"es variable, pero siempre es un múltiplo de 16 bytes."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:269
 #, python-format
@@ -13073,14 +7773,16 @@ msgid ""
 "Actual max payload length, and max block length, is less than 64 KB; see "
 "the I2NP Overview."
 msgstr ""
+"El tamaño de las actuales carga máxima, y tamaño máximo del bloque, es "
+"menor de 64 KB; vea la Introducción a I2NP."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:272
 msgid "New Session Key is currently unused and is never present."
-msgstr ""
+msgstr "La nueva clave de sesión actualmente está en desuso y nunca está presente."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:277
 msgid "Existing Session Message Specification"
-msgstr ""
+msgstr "Especificación de mensaje de sesión existente."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:278
 msgid ""
@@ -13090,12 +7792,17 @@ msgid ""
 "contains only an AES encrypted block, and is not preceded by an\n"
 "ElGamal block."
 msgstr ""
+"Las etiquetas de sesión entregadas exitosamente son recordadas durante \n"
+"un periodo breve (actualmente 15 minutos) hasta que se usan o se \n"
+"descartan. Se usa una etiqueta empaquetándola en un mensaje de sesión \n"
+"existente que sólo contiene un bloque cifrado con AES, y no está "
+"precedido por un bloque ElGamal."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:286
 msgid ""
 "The existing session message is\n"
 "as follows:"
-msgstr ""
+msgstr "El mensaje de sesión existente es como sigue: "
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:309
 #, python-format
@@ -13104,10 +7811,13 @@ msgid ""
 "Tag\n"
 "             previously delivered in an AES block"
 msgstr ""
+"Una etiqueta de "
+"sesión de 32-bytes previamente entregada \n"
+"en un bloque AES."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:314
 msgid "As specified above."
-msgstr ""
+msgstr "Como se especificó arriba."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:318
 msgid ""
@@ -13115,6 +7825,9 @@ msgid ""
 "the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the "
 "sessionTag."
 msgstr ""
+"La etiqueta de sesión también sirve como pre-IV. El IV (Vector de \n"
+"Inicialización) son los primeros 16 bytes del hash SHA-256 de la \n"
+"sessionTag (etiqueta de sesión)."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:323
 msgid ""
@@ -13125,6 +7838,13 @@ msgid ""
 "If the tag is not found, the message is assumed to be a New Session Message."
 msgstr ""
+"Para decodificar un mensaje desde una sesión existente, un router "
+"consulta \n"
+"la etiqueta de sesión para encontrar una clave de sesión asociada. Si se"
+" \n"
+"encuentra la etiqueta de sesión, el bloque AES es descifrado usando la "
+"clave de sesión asociada. Si no se encuentra la etiqueta, se asume que el"
+" mensaje es un nuevo mensaje de sesión."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:332
 msgid ""
@@ -13134,6 +7854,11 @@ msgid ""
 "significant\n"
 "impact on overall performance."
 msgstr ""
+"Hay muchas áreas posibles para ajustar los algoritmos del administrador \n"
+"de claves de sesión; algunos pueden interactuar con el comportamiento de"
+" \n"
+"la librería streaming, o tener un impacto significativo en el rendimiento"
+" conjunto."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:338
 msgid ""
@@ -13143,18 +7868,30 @@ msgid ""
 "We currently deliver 40 tags at a time (1280 bytes).\n"
 "32 (1024 bytes) may be better for tunnel fragmentation."
 msgstr ""
+"La entrega de demasiadas etiquetas de una vez puede imponer un tráfico de"
+" \n"
+"control sustancial para breves conexiones streaming o datagramas, e \n"
+"incrementar la posibilidad de pérdida del mensaje. Actualmente entregamos"
+" \n"
+"40 etiquetas de una vez (1280 bytes), 32 (1024 bytes) puede ser mejor "
+"para \n"
+"la fragmentación del túnel."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:345
 msgid ""
 "A few tags could be delivered in each of several messages, or lots of "
 "tags all at once."
 msgstr ""
+"Se podrían entregar unas pocas etiquetas en cada uno de los varios \n"
+"mensajes, o muchas etiquetas todas de una vez."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:349
 msgid ""
 "It is also important to study and tune\n"
 "the low-tag thresholds at which more tags are sent."
 msgstr ""
+"También es importante estudiar y ajustar los umbrales bajos de etiquetas "
+"en los que se envían más etiquetas."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:354
 msgid ""
@@ -13162,6 +7899,9 @@ msgid ""
 "mind\n"
 "the eventual padding to 1KB at the tunnel message layer."
 msgstr ""
+"El número de etiquetas entregadas podría depender del tamaño del \n"
+"mensaje, teniendo en cuenta el eventual esquema de relleno de 1KB en la \n"
+"capa de mensaje de túnel."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:359
 msgid ""
@@ -13169,12 +7909,16 @@ msgid ""
 "advisory\n"
 "on the number of tags required."
 msgstr ""
+"Los clientes podrían enviar una estimación del tiempo de vida de la "
+"sesión al router, a modo de aviso del número de etiquetas solicitado."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:364
 msgid ""
 "Delivery of too few tags causes the router to fall back to an expensive "
 "ElGamal encryption."
 msgstr ""
+"La entrega de demasiado pocas etiquetas provoca que el ruter regrese al "
+"costoso cifrado de respaldo ElGamal."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:368
 msgid ""
@@ -13182,6 +7926,9 @@ msgid ""
 "before using them;\n"
 "there are tradeoffs for each strategy."
 msgstr ""
+"El router puede asumir como un hecho la entrega de etiquetas de sesión, o"
+"  esperar acuse de recibo ('acknowledgement') antes de usarlas; cada "
+"estrategia tiene sus propios sacrificios."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:373
 msgid ""
@@ -13189,12 +7936,20 @@ msgid ""
 "padding fields in the ElGamal block\n"
 "could be used for the entire message, instead of establishing a session."
 msgstr ""
+"Para mensajes muy breves, casi la totalidad de los 222 bytes del pre-IV \n"
+"(pre-Vector de Inicialización) y los campos de esquemas de relleno en el "
+"bloque ElGamal podrían usarse para el mensaje completo, en lugar de \n"
+"para establecer una sesión."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:378
 msgid ""
 "Evaluate padding strategy; currently we pad to a minimum of 128 bytes.\n"
 "Would be better to add a few tags to small messages than pad."
 msgstr ""
+"Evaluar la estrategia de esquema de relleno; actualmente rellenamos hasta"
+" \n"
+"un mínimo de 128 bytes. Para los mensajes pequeños sería mejor añadirles "
+"unas pocas etiquetas que rellenarlos."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:383
 msgid ""
@@ -13206,6 +7961,12 @@ msgid ""
 "The router currently plays some tricks like this when sending\n"
 "tunnel test messages to itself."
 msgstr ""
+"Quizá las cosas podrían ser más eficientes si el sistema de etiqueta de "
+"sesión fuera bidireccional, así las etiquetas entregadas en la ruta "
+"'forward' (directa) podrían usarse en la ruta 'reverse' (inversa), "
+"evitando así ElGamal en la respuesta inicial. El router actualmente usa "
+"algunos trucos como este cuando se envían mensajes de prueba de túnel a "
+"si mismo."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:391
 #, python-format
@@ -13213,6 +7974,8 @@ msgid ""
 "Change from Session Tags to\n"
 "a synchronized PRNG."
 msgstr ""
+"Cambiar de las etiquetas de sesión a un "
+"PRNG (generador de números pseudo aleatorios) sincronizado."
 
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:396
 #, python-format
@@ -13224,6 +7987,14 @@ msgid ""
 "and accept a small risk of the random Session Key matching the magic "
 "number."
 msgstr ""
+"Varias de estas ideas pueden requerir un nuevo tipo de mensaje I2NP "
+"(Protocolo de Red I2P), o establecer un distintivo en las instrucciones de entrega, o "
+"establecer un número mágico en los primeros pocos bytes del campo de la "
+"clave \n"
+"de sesión y aceptar un pequeño riesgo de que la clave de sesión aleatoria"
+" \n"
+"coincida con el número mágico."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:2
 msgid "Garlic Routing"
@@ -13243,7 +8014,7 @@ msgstr ""
 "Los términos \"garlic routing, enrutado garlic\" y \"garlic encryption, "
 "cifrado garlic\"son usados a menudo imprecisamente para designar la "
 "tecnología de I2P.\n"
-"Aquí vamos a esplicar la historia de estos términos, su significados,y el"
+"Aquí vamos a explicar la historia de estos términos, su significados,y el"
 " uso de los métodos \"garlic\" en I2P."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:13
@@ -13255,6 +8026,11 @@ msgid ""
 "Section 8.1.1 (June 2000), as derived from \n"
 "Onion Routing."
 msgstr ""
+"\"Garlic Routing\" fue acuñado por Michael J. Freedman en "
+"la Master's thesis "
+"de Roger Dingledine en Free Haven. Sección 8.1.1 (Junio 2000), derivado "
+"de Onion Routing."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:21
 msgid ""
@@ -13270,7 +8046,7 @@ msgstr ""
 "porque implementa un forma de agrupación tal y como Freedman describió, o"
 " simplemente para enfatizar las diferencias con Tor. La razón exacta "
 "puede haberse perdido en el tiempo. Generalmente, cuando nos referimos al"
-" término \"garlic\", puede puede significar una de estas tres cosas:"
+" término \"garlic\", puede significar una de estas tres cosas:"
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:28
 #: i2p2www/pages/site/docs/how/garlic-routing.html:39
@@ -13313,13 +8089,12 @@ msgid ""
 "the tunnel."
 msgstr ""
 "El enrutado Onion es una técnica para construir caminos, o túneles, a "
-"través de una serie de pares, y después usar ese túnel. . Los mensajes "
-"son repetidamente cifrados por el creador, y después descifrados por cada"
-" salto. Durante la fase de construcción sólo las instrucciones de "
-"enrutado para el siguiente salto son expuestas a cada par. Durante la "
-"fase de operación los mensajes se pasan a través del túnel, y el mensaje "
-"y sus instrucciones de enrutado sólo son mostradas al punto final del "
-"túnel."
+"través de una serie de pares, y después usar ese túnel. Los mensajes son "
+"repetidamente cifrados por el creador, y después descifrados por cada "
+"salto. Durante la fase de construcción sólo las instrucciones de enrutado"
+" para el siguiente salto son expuestas a cada par. Durante la fase de "
+"operación los mensajes se pasan a través del túnel, y el mensaje y sus "
+"instrucciones de enrutado sólo son mostradas en el punto final del túnel."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:49
 #, python-format
@@ -13335,7 +8110,7 @@ msgid ""
 "encryption\n"
 "per hop along the path."
 msgstr ""
-"Esto es similar a cómo Mixmaster (vercomparación entre redes) envía mensajes - "
 "toma un mensaje, lo cifra con la clave pública del destinatario, toma ese"
 " mensaje cifrado y lo cifra (junto con instrucciones indicando el "
@@ -13401,11 +8176,11 @@ msgid ""
 "perhaps it is not, by itself, enough to justify a change in terminology."
 msgstr ""
 "Este concepto ha sido implementado en I2p como se describe más abajo.\n"
-"Nuestro término para \"bulbs, bulbos\" garlic es \"cloves, clavos\". "
-"Puede contener cualquier número de mensajes, en vez de un solo mensaje. "
-"Esta es una gran diferencia con la implementación de Tor. Aun así, es "
-"sólo una de las diferencias entre I2P y Tor; quizás por si misma no sea "
-"suficiente para justificar un cambio de terminología."
+"Nuestro término para \"bulbs, bulbos\" garlic es \"cloves, dientes del "
+"ajo\". Puede contener cualquier número de mensajes, en vez de un solo "
+"mensaje. Esta es una gran diferencia con la implementación de Tor. Aun "
+"así, es sólo una de las diferencias entre I2P y Tor; quizás por si misma "
+"no sea suficiente para justificar un cambio de terminología."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:87
 msgid ""
@@ -13491,7 +8266,7 @@ msgid ""
 "reply."
 msgstr ""
 "En I2P los túneles son unidireccionales. Cada parte construye dos "
-"túneles, uno para el tráfico de salido y otro para el de entrada. Por lo "
+"túneles, uno para el tráfico de salida y otro para el de entrada. Por lo "
 "tanto se necesitan cuatro túneles para una vuelta completa de un mensaje "
 "y su respuesta."
 
@@ -13507,9 +8282,9 @@ msgid ""
 "ElGamal/AES+SessionTag for the encryption."
 msgstr ""
 "Los túneles son usados y creados con un cifrado por capas. Esto se "
-"describe en página de implementación delos "
+"describe en página de implementación de los "
 "túneles. La construcción de los túneles es definida en  testa página. Para el cifrado usamos esta página. Para el cifrado usamos ElGamal/AES+SessionTag "
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:141
@@ -13535,7 +8310,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:152
 msgid "End-to-End Message Bundling"
-msgstr "Construcción de mensajes de fin a fin."
+msgstr "Agrupación de mensajes de fin a fin."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:153
 #, python-format
@@ -13554,6 +8329,18 @@ msgid ""
 "Garlic Message.\n"
 "Delivery Instructions may specify a Destination, Router, or Tunnel."
 msgstr ""
+"En la capa por encima de los túneles, I2P envía mensajes de fin a fin "
+"entre destinaciones. "
+"Dentro de un único túnel usamos ElGamal/AES+SessionTag para el cifrado. Cada "
+"mensaje cliente enviado al router a través del interfaz I2CP se convierte un solo Garlic Clove con su propias "
+"instrucciones de envío, dentro"
+" de un mensaje Garlic. Las "
+"instrucciones de envío pueden indicar una destinación, un router o un "
+"túnel."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:172
 msgid ""
@@ -13561,10 +8348,12 @@ msgid ""
 "However, the router will periodically bundle two additional\n"
 "cloves in the Garlic Message:"
 msgstr ""
+"Generalmente, un mensaje Garlic sólo contiene un clove. Aun así, el ruter"
+" agrupa periódicamente dos dientes adicionales en el mensaje Garlic:"
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:177
 msgid "Garlic Message Cloves"
-msgstr ""
+msgstr "Cloves, dientes, de los mensajes Garlic, ajo"
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:180
 #, python-format
@@ -13585,6 +8374,15 @@ msgid ""
 "Destination,\n"
 "or take other actions."
 msgstr ""
+"Un mensaje de estado de "
+"envío con las instrucciones de"
+" envío especificando que se envíe de vuelta al ruter original como "
+"confirmación. Esto es similar al \"reply block, bloque de respuesta\" o "
+"\"reply onion\" descritos en las referencias. Se usa para determinar el "
+"fallo o éxito  del envío del mensaje de fin a fin. El ruter original, "
+"tras el fallo de no recibir el mensaje de estado de envío en el tiempo "
+"esperado, puede modificar la ruta a una destinación lejana, o tomar otras"
+" acciones."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:194
 #, python-format
@@ -13605,6 +8403,18 @@ msgid ""
 "explained on the\n"
 "network database page."
 msgstr ""
+"Un mensaje de almacenamiento "
+"de la base de datos con un LeaseSet para la "
+"destinación original, con instrucciones de envío "
+"especificando el ruter con destinación remota. Agrupando un LeaseSet "
+"periódicamente, el ruter se asegura de que la destinación lejana será "
+"capaz de mantener las comunicaciones. De otra forma el ruter lejano "
+"tendría que consultar a un ruter floodfill por un registro en la base de "
+"datos , y todos los LeaseSets tendrían que ser publicados en la base de "
+"datos de la red, como se explica en la página de la"
+" base de datos de la red."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:213
 #, python-format
@@ -13616,6 +8426,11 @@ msgid ""
 "are delivered, or if the messages have not been bundled in the previous "
 "minute."
 msgstr ""
+"En la implementación actual, los mensajes de estado de envíos y los "
+"mensajes de almacenamiento de la base de datos son agrupados cuando el "
+"LeaseSet local cambia, cuando se envían etiquetas de sesión "
+"adicionales, o si el mensaje no ha sido agrupado en los minutos previos."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:220
 msgid ""
@@ -13623,10 +8438,12 @@ msgid ""
 "purposes,\n"
 "and not part of a general-purpose routing scheme."
 msgstr ""
+"Obviamente, los mensajes adicionales son agrupados por un propósito "
+"específico, y no son parte del esquema general de rutado."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:226
 msgid "Storage to the Floodfill Network Database"
-msgstr ""
+msgstr "Almacenamiento en la base de datos de un FloodFill"
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:227
 #, python-format
@@ -13641,6 +8458,14 @@ msgid ""
 "Garlic Message\n"
 "so it is not visible to the tunnel's outbound gateway."
 msgstr ""
+"Como se ha explicado en la página de la "
+"base de datos de la red, los LeaseSets locales son "
+"enviados a los ruters FloodFill en un mensaje de almacenamiento de la "
+"base de datos envuelto en un mensaje Garlic, con lo cual no es "
+"visible para la puerta de salida del túnel de salida."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:243
 #, python-format
@@ -13654,6 +8479,12 @@ msgid ""
 "a wide spectrum of batching, delay, mixing, and routing strategies are "
 "possible."
 msgstr ""
+"El mecanismo de los mensajes Garlic es muy flexible y proporciona una "
+"estructura para implementar muchos tipos de envíos mixnet. Junto con la "
+"opción de retardo no usada en las instrucciones de envío del mensaje "
+"del túnel, son posibles una gran cantidad de estrategias de retardo, "
+"mezclado, rutado y lotes."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:251
 msgid ""
@@ -13664,6 +8495,11 @@ msgid ""
 "tunnels\n"
 "for redundancy, or streaming audio and video."
 msgstr ""
+"En particular, hay potencial para mucha más flexibilidad en el punto "
+"final del túnel de salida. Los mensajes podrían ser rutados desde ahí a "
+"uno o varios túneles (con lo cual se minimizarían las conexiones de punto"
+" a punto), o enviar a varios túneles para hacerlo redundante, o hacer "
+"streming de audio o vídeo."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:258
 msgid ""
@@ -13674,6 +8510,11 @@ msgid ""
 "be forwarded along various paths, and enforcing certain message "
 "expiration times."
 msgstr ""
+"Estos experimentos pudrían entrar en conflicto con la necesidad de "
+"seguridad y anonimato, ya sea limitando ciertos caminos de enrutado, "
+"restringiendo los mensajes I2NP que puedan ser enviados a través de "
+"varios caminos, e imponiendo ciertos tiempos de espiración a los "
+"mensajes."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:264
 #, python-format
@@ -13687,6 +8528,11 @@ msgid ""
 "This is not currently used, beyond the requirement to pad to a multiple "
 "of 16 bytes."
 msgstr ""
+"Como parte de un cifrado ElGamal/AES, un "
+"mensaje Garlic contiene una cantidad especificada de datos de relleno, "
+"que permiten al transmisor tomar ciertas contramedidas activas contra el "
+"análisis de tráfico. Esto no se usa actualmente, mas allá de la necesidad"
+" de rellenar a un múltiplo de 16 bytes."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:273
 #, python-format
@@ -13694,6 +8540,8 @@ msgid ""
 "Encryption of additional messages to and from the\n"
 "floodfill routers."
 msgstr ""
+"El cifrado de mensajes adicionales hacia y desde los ruters floodfill."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:283
 msgid ""
@@ -13704,18 +8552,22 @@ msgid ""
 "see Section 8.1.1 authored by\n"
 "Michael J. Freedman."
 msgstr ""
+"El término de garlic routing, rutado de ajo, fue acuñado en la Master's thesis en Free"
+" Haven de Roger Dingledine (June 2000), ver sección 8.1.1 de Michael J. Freedman."
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:290
 msgid "Onion router publications"
-msgstr ""
+msgstr "Publicaciones sobre ruter Onion"
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:292
 msgid "Onion Routing on Wikipedia"
-msgstr ""
+msgstr "Rutado Onion en la Wikipedia"
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:294
 msgid "Garlic Routing on Wikipedia"
-msgstr ""
+msgstr "Rutado Garlic en la Wikipedia"
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:296
 #, python-format
@@ -13723,10 +8575,12 @@ msgid ""
 "I2P Meeting 58 (2003) discussing the "
 "implementation of garlic routing"
 msgstr ""
+"Reunión 58 de I2P (2003) discutiendo la "
+"implementación del rutado Garlic"
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:302
 msgid "Free Haven publications"
-msgstr ""
+msgstr "Publicaciones en Free Heaven"
 
 #: i2p2www/pages/site/docs/how/garlic-routing.html:304
 msgid ""
@@ -13734,6 +8588,10 @@ msgid ""
 "router.net/Publications/IH-1996.pdf\">Hiding Routing Information\n"
 "by David M. Goldschlag, Michael G. Reed, and Paul F. Syverson in 1996."
 msgstr ""
+"El rutado Onion fue descrito por primera vez en 1996 por David M. "
+"Goldschlag, Michael G. Reed, and Paul F. Syverson en Hiding Routing "
+"Information."
 
 #: i2p2www/pages/site/docs/how/intro.html:2
 msgid "A Gentle Introduction"
@@ -13788,17 +8646,17 @@ msgid ""
 "even taken over to attempt more malicious attacks."
 msgstr ""
 "A diferencia de la mayoría de las redes anónimas, I2P no intenta "
-"suministrar anonimato ocultándole sí al origen de una comunicación y no "
-"al destinatario, o vice versa. De lo contrario: I2P está diseñada para "
-"permitir a los pares comunicarse unos con otros anónimamente - ambos, "
-"quien envía y quien recibe, no son identificables entre ellos y tampoco "
-"por terceras partes. Por ejemplo, actualmente hay sitios web I2P internos"
-" (permitiendo publicación y hospedaje anónimo) además de proxies HTTP "
+"proporcionar anonimato ocultando al autor de una comunicación y no al "
+"destinatario, o vice versa. Al contrario: I2P está diseñada para permitir"
+" a los pares comunicarse unos con otros anónimamente - ambos, quien envía"
+" y quien recibe, no son identificables entre ellos y tampoco por terceras"
+" partes. Por ejemplo, actualmente hay sitios web I2P internos "
+"(permitiendo publicación y hospedaje anónimo) además de proxies HTTP "
 "hacia la web normal (permitiendo navegación anónima). Disponer de la "
 "posibilidad de correr servidores internamente en I2p es esencial,  ya que"
-" es bastante probable que cualquier proxy de salida hacia la Internet "
-"normal pudiera ser monitorizado, desactivado o comprometido con el "
-"intento de ataques más maliciosos."
+" es bastante probable que cualquier proxy de salida hacia el Internet "
+"normal pueda ser monitorizado, desactivado o incluso comprometido para "
+"luego intentar más ataques maliciosos."
 
 #: i2p2www/pages/site/docs/how/intro.html:28
 #, python-format
@@ -13821,8 +8679,8 @@ msgid ""
 " turn on and off various\n"
 "proxies to enable the anonymizing functionality."
 msgstr ""
-"La red es en sí misma orientada a mensajes - es en esencia una capa IP "
-"segura y anónima donde los mensajes son direccionados hacia claves "
+"La red es en sí misma está orientada a mensajes - es en esencia una capa "
+"IP segura y anónima donde los mensajes son direccionados hacia claves "
 "criptográficas (Destinos) y pueden ser considerablemente más largos que "
 "los paquetes IP. Algunos ejemplos del uso de la red incluyen \"eepsites\""
 "  (servidores web hospedando aplicaciones web normales dentro de I2P), un"
@@ -13884,13 +8742,11 @@ msgid ""
 "Internet, but we could not find any that met our needs or threat model."
 msgstr ""
 "Hay múltiples razones por las que necesitamos un sistema que soporte "
-"comunicaciones anónimas, y \n"
-"además cada uno tiene si propias razones. Hay muchos a "
-"href=\"%(comparisons)s\">otros\n"
-"proyectos  en Internet trabajando para encontrar formas de ofrecer "
-"varios niveles de anonimato para la gente,\n"
-"pero no habíamos encontrado ninguno que cumpliera nuestras necesidades o "
-"el modelo de amenazas."
+"comunicaciones anónimas, y además cada uno tiene si propias razones. Hay "
+"muchos otros proyectos en Internet "
+"trabajando para encontrar formas de ofrecer varios niveles de anonimato "
+"para la gente, pero no habíamos encontrado ninguno que cumpliera nuestras"
+" necesidades o el modelo de amenazas."
 
 #: i2p2www/pages/site/docs/how/intro.html:59
 msgid "How?"
@@ -13923,7 +8779,7 @@ msgstr ""
 "y salientes (Túneles, como se describen en la página tunnel routing). Cada ruter está "
 "identificado por una RouterIdentity cifrada que es e normalmente "
-"permanente. Estos ruters se comunican entre ellos a través de mecanismo "
+"permanente. Estos ruters se comunican entre ellos a través de mecanismos "
 "de transporte existentes (TCP, UDP, etc) enviándose distintos mensajes. "
 "Las aplicaciones clientes tienen su propio identificador criptográfico "
 "(\"Destino\") que las habilita para enviar y recibir mensajes. Estos "
@@ -13931,7 +8787,7 @@ msgstr ""
 "temporal (\"arrendamiento\") de varios túneles que serán usados para "
 "enviar y recibir mensaje a través de la red. I2P tiene su propia base de datos de red (utilizando una modificación "
-"del algoritmo Kadeemlia) para distribuir información de\n"
+"del algoritmo Kademlia) para distribuir información de\n"
 "rutas y contactos de forma segura."
 
 #: i2p2www/pages/site/docs/how/intro.html:74
@@ -13958,8 +8814,8 @@ msgid ""
 "which is constantly updated\n"
 "as new leases are authorized and old ones expire."
 msgstr ""
-"En la imagen, Alice, Bob, Charlie and Dave están corriendo ruters con una"
-" simple Destinación en su ruter local. Cada uno de ellos tiene un par de "
+"En la imagen, Alice, Bob, Charlie y Dave están corriendo ruters con una "
+"simple Destinación en su ruter local. Cada uno de ellos tiene un par de "
 "túneles de dos saltos entrantes por destino (etiquetados como 1, 2, 3, 4,"
 " 5 y 6), y una pequeña parte del grupo de los túneles de salida de esos "
 "ruters se representa con túneles de salida de dos saltos. Para "
@@ -13992,9 +8848,9 @@ msgstr ""
 " de los túneles de entrada de Alice (túnel 1 o 2). Para hacer las cosas "
 "más sencillas, la mayor parte de los mensajes enviados entre Alice y Bob "
 "usan el envoltorio de ajo, garlic, "
-"incluyendo la información de arrendamiento propia del remitente en el "
-"paquete, de esta forma el destinatario puede contestar inmediatamente sin"
-" necesidad de buscar el dato en su base de datos de red."
+"incluyendo la información del contrato, lease, del propio remitente para "
+"que el receptor pueda responder inmediatamente sin tener que mirar en la "
+"base de datos de la red por ellos."
 
 #: i2p2www/pages/site/docs/how/intro.html:96
 #, python-format
@@ -14017,7 +8873,7 @@ msgstr ""
 " red. De esta forma cada ruter debe guardar y mantener los perfiles de "
 "varios ruters y es responsable de seleccionar los pares apropiados para "
 "satisfacer el anonimato, rendimiento y fiabilidad requeridos por los "
-"usuarios tal y como se describe en la página deselección de pares."
 
 #: i2p2www/pages/site/docs/how/intro.html:105
@@ -14239,13 +9095,12 @@ msgstr "Vea el índice de la documentacón técnica."
 
 #: i2p2www/pages/site/docs/how/network-database.html:2
 msgid "The Network Database"
-msgstr ""
+msgstr "La base de datos de la red"
 
 #: i2p2www/pages/site/docs/how/network-database.html:3
-#: i2p2www/pages/site/docs/protocol/i2np.html:3
-#: i2p2www/pages/site/docs/spec/common-structures.html:3
-msgid "June 2013"
-msgstr "Junio de 2013"
+#: i2p2www/pages/site/docs/spec/updates.html:3
+msgid "October 2013"
+msgstr "Octubre de 2013"
 
 #: i2p2www/pages/site/docs/how/network-database.html:8
 msgid ""
@@ -14260,6 +9115,14 @@ msgid ""
 "replace\n"
 "older ones, and protection against certain classes of attack."
 msgstr ""
+"La netDb de I2P es una base de datos distribuida especializada que "
+"contiene 2 tipos de datos - información de contacto del ruter y la "
+"información de contacto de la destinación. Cada parte de los datos es "
+"firmada por la parte apropiada y verificada por cualquiera que las use o "
+"las almacene. Además, los datos tienen información cambiante, permitiendo"
+" que las entradas irrelevantes sean desechadas, que nuevas entradas "
+"puedan reemplazar las antiguas y protección contra cierto tipos de "
+"ataques."
 
 #: i2p2www/pages/site/docs/how/network-database.html:17
 msgid ""
@@ -14267,6 +9130,9 @@ msgid ""
 "where a subset of all routers, called \"floodfill routers\", maintains "
 "the distributed database."
 msgstr ""
+"La netDb se distribuye con una técnica simple llamada \"FloodFill\", "
+"donde un subconjunto de ruters, llamados ruters \"floodfill\", mantienen "
+"la base de datos distribuida."
 
 #: i2p2www/pages/site/docs/how/network-database.html:25
 msgid ""
@@ -14278,65 +9144,135 @@ msgid ""
 "SHA256 of the router's identity\n"
 "as the key. The structure itself contains:"
 msgstr ""
+"Cuando un ruter I2P quiere contactar con otro ruter, necesitan conocer "
+"algunas partes claves de los datos - estas partes están agrupadas y "
+"firmadas por el ruter dentro de una estructura llamda \"RouterInfo\", que"
+" es distribuida con el hash SHA256 de la identidad del ruter como una "
+"clave de cifrado. La estructura en sí misma contiene:"
 
 #: i2p2www/pages/site/docs/how/network-database.html:32
 msgid ""
 "The router's identity (a 2048bit ElGamal encryption key, a 1024bit DSA "
 "signing key, and a certificate)"
 msgstr ""
+"La identidad del ruter (una calve de cifrado ElGamal de 2048 bits, una "
+"clave de firmado DSA de 1024 bits y un certificado)"
 
 #: i2p2www/pages/site/docs/how/network-database.html:33
 msgid ""
 "The contact addresses at which it can be reached (e.g. TCP: example.org "
 "port 4108)"
 msgstr ""
+"La dirección de contacto en la que puede ser accedida (por ejemplo TCP: "
+"example.org puerto 4108)"
 
 #: i2p2www/pages/site/docs/how/network-database.html:34
 msgid "When this was published"
-msgstr ""
+msgstr "Cuándo fue publicada."
 
 #: i2p2www/pages/site/docs/how/network-database.html:35
 msgid "A set of arbitrary text options"
-msgstr ""
+msgstr "Un conjunto de opciones de texto arbitrarias"
 
 #: i2p2www/pages/site/docs/how/network-database.html:36
 msgid "The signature of the above, generated by the identity's DSA signing key"
 msgstr ""
+"La firma de todo lo anterior, generada por clave de firma DSA de la "
+"identidad."
 
 #: i2p2www/pages/site/docs/how/network-database.html:39
 msgid ""
 "The following text options, while not strictly required, are expected\n"
 "to be present:"
 msgstr ""
+"Las siguientes opciones de texto, que aunque no son requeridas "
+"explicitamente se espera que esten presentes:"
 
 #: i2p2www/pages/site/docs/how/network-database.html:45
 msgid ""
 "Capabilities flags - used to indicate floodfill participation, "
 "approximate bandwidth, and perceived reachability"
 msgstr ""
+"Datos de capacidad - usados para indicar si se participa como floodfill, "
+"ancho de banda aproximado y la accesibilidad observada."
+
+#: i2p2www/pages/site/docs/how/network-database.html:47
+msgid "SSU Testing"
+msgstr "Prueba de SSU"
 
 #: i2p2www/pages/site/docs/how/network-database.html:48
-msgid "The core library version, always the same as the router version"
-msgstr ""
+msgid "SSU Introducer"
+msgstr "Introductor de SSU"
+
+#: i2p2www/pages/site/docs/how/network-database.html:49
+#: i2p2www/pages/site/docs/how/network-database.html:246
+msgid "Floodfill"
+msgstr "FloodFill"
+
+#: i2p2www/pages/site/docs/how/network-database.html:50
+msgid "Hidden"
+msgstr "Oculto"
 
 #: i2p2www/pages/site/docs/how/network-database.html:51
+#, python-format
+msgid "Under %(amount)s shared bandwidth"
+msgstr "Por debajo del %(amount)s de ancho de banda compartido"
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+#: i2p2www/pages/site/docs/how/network-database.html:53
+#: i2p2www/pages/site/docs/how/network-database.html:54
+#, python-format
+msgid "%(amount)s shared bandwidth"
+msgstr "%(amount)s de ancho de banda compartido"
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+msgid "default"
+msgstr "predeterminado"
+
+#: i2p2www/pages/site/docs/how/network-database.html:55
+#, python-format
+msgid "Over %(amount)s shared bandwidth"
+msgstr "Por encima del %(amount)s de ancho de banda compartido"
+
+#: i2p2www/pages/site/docs/how/network-database.html:56
+msgid "Reachable"
+msgstr "Alcanzable"
+
+#: i2p2www/pages/site/docs/how/network-database.html:57
+msgid "Unreachable"
+msgstr "No alcanzable"
+
+#: i2p2www/pages/site/docs/how/network-database.html:62
+msgid "The core library version, always the same as the router version"
+msgstr ""
+"La versión de la librería del núcleo, siempre la misma que la versión del"
+" ruter"
+
+#: i2p2www/pages/site/docs/how/network-database.html:65
 msgid ""
 "Basic network compatibility - A router will refuse to communicate with a "
 "peer having a different netId"
 msgstr ""
+"Compatibilidad básica de la red - Un ruter no se comunicará con un par "
+"que tenga un netId diferente"
 
-#: i2p2www/pages/site/docs/how/network-database.html:54
+#: i2p2www/pages/site/docs/how/network-database.html:68
 msgid "Used to determine compatibility with newer features and messages"
 msgstr ""
+"Se utiliza para determinar la compatibilidad con las nuevas "
+"características y mensajes."
 
-#: i2p2www/pages/site/docs/how/network-database.html:57
+#: i2p2www/pages/site/docs/how/network-database.html:71
 msgid ""
 "Always sent as 90m, for compatibility with an older scheme where routers "
 "published their actual uptime,\n"
 "and only sent tunnel requests to peers whose was more than 60m"
 msgstr ""
+"Siempre a 90 min, para mantener la compatibilidad con el viejo esquema  "
+"donde los ruters publican su tiempo encendidos actual, y sólo envían "
+"peticiones de túneles a pares con mas de 60 min."
 
-#: i2p2www/pages/site/docs/how/network-database.html:62
+#: i2p2www/pages/site/docs/how/network-database.html:76
 msgid ""
 "These values are used by other routers for basic decisions.\n"
 "Should we connect to this router? Should we attempt to route a tunnel "
@@ -14349,8 +9285,16 @@ msgid ""
 "in the router, except for display in the user interface and for debugging"
 " and network analysis."
 msgstr ""
+"Estos valores pueden ser usados por otros ruters para tomar decisiones "
+"básicas. ¿Deberíamos conectar con este ruter? ¿Deberíamos intentar rutar "
+"un túnel a través de ese ruter?\n"
+"En particular, la opción de la capacidad de ancho de banda  sólo se usa "
+"para determinar cuando el ruter cumple un umbral para poder rutar "
+"túneles. Por encima del umbral mínimo el ancho de banda anunciado no es "
+"usado o confiable en ningún sitio del ruter, excepto para mostrar en el "
+"interfaz del usuario para depurar y para el análisis de tráfico."
 
-#: i2p2www/pages/site/docs/how/network-database.html:72
+#: i2p2www/pages/site/docs/how/network-database.html:86
 #, python-format
 msgid ""
 "Additional text options include\n"
@@ -14364,16 +9308,27 @@ msgid ""
 "with the side-effects that could result from revealing this data.\n"
 "Current statistics are limited to:"
 msgstr ""
+"La opciones de texto adicionales incluyen un pequeño número de "
+"estadísticas sobre la salud de los ruters, que son añadidas por las webs "
+"como %(stats)s, estadísticas, para el "
+"análisis del rendimiento de la red y su depuración. Estas estadísticas "
+"fueron elegidas para proporcionar datos importantes a los "
+"desarrolladores, como la tasa de éxito al construir los túneles, mientras"
+" se hace un balanceo de los posibles daños causados por la revelación de "
+"estos datos y necesidad de obtenerlos. Estas estadísticas están limitadas"
+" a:"
 
-#: i2p2www/pages/site/docs/how/network-database.html:83
+#: i2p2www/pages/site/docs/how/network-database.html:97
 msgid "Client and exploratory tunnel build success, reject, and timeout rates"
 msgstr ""
+"Éxito en la creación de túneles clientes y exploratorios, denegaciones, y"
+" valores de timeout."
 
-#: i2p2www/pages/site/docs/how/network-database.html:84
+#: i2p2www/pages/site/docs/how/network-database.html:98
 msgid "1 hour average number of participating tunnels"
-msgstr ""
+msgstr "Media del número de túneles participantes en 1 hora"
 
-#: i2p2www/pages/site/docs/how/network-database.html:87
+#: i2p2www/pages/site/docs/how/network-database.html:101
 msgid ""
 "The data published can be seen in the router's user interface,\n"
 "but is not used or trusted within the router.\n"
@@ -14382,20 +9337,24 @@ msgid ""
 "statistics to improve anonymity, and we plan to remove more in future "
 "releases."
 msgstr ""
+"Los datos publicados pueden verse en en interfaz del ruter,, pero el "
+"ruter no los usa ni confía en ellos. Según madura la red, hemos eliminado"
+" la mayoría de las estadísticas publicadas para mejorar el anonimato, y "
+"tenemos planeado eliminar más en las próximas versiones."
 
-#: i2p2www/pages/site/docs/how/network-database.html:95
+#: i2p2www/pages/site/docs/how/network-database.html:109
 msgid "RouterInfo specification"
-msgstr ""
+msgstr "Especifiaciones de RouterInfo"
 
-#: i2p2www/pages/site/docs/how/network-database.html:98
+#: i2p2www/pages/site/docs/how/network-database.html:112
 msgid "RouterInfo Javadoc"
-msgstr ""
+msgstr "Javadoc de RouterInfo"
 
-#: i2p2www/pages/site/docs/how/network-database.html:101
+#: i2p2www/pages/site/docs/how/network-database.html:115
 msgid "RouterInfo Expiration"
-msgstr ""
+msgstr "Caducidad de RouterInfo"
 
-#: i2p2www/pages/site/docs/how/network-database.html:102
+#: i2p2www/pages/site/docs/how/network-database.html:116
 msgid ""
 "RouterInfos have no set expiration time.\n"
 "Each router is free to maintain its own local policy to trade off the "
@@ -14403,18 +9362,24 @@ msgid ""
 "with memory or disk usage.\n"
 "In the current implementation, there are the following general policies:"
 msgstr ""
+"RouterInfo no tienen tiempo de caducidad. Cada ruter puede mantener su "
+"propia política local a la hora de controlar la frecuencia de las "
+"búsquedas de RouterInfo y el uso de memoria y espacio en le disco. En la "
+"implementación actual, estas son las políticas generales:"
 
-#: i2p2www/pages/site/docs/how/network-database.html:109
+#: i2p2www/pages/site/docs/how/network-database.html:123
 msgid ""
 "There is no expiration during the first hour of uptime, as the persistent"
 " stored data may be old."
 msgstr ""
+"No existe vencimiento durante la primera hora encendido, ya que los datos"
+" almacenados podrían ser viejos."
 
-#: i2p2www/pages/site/docs/how/network-database.html:112
+#: i2p2www/pages/site/docs/how/network-database.html:126
 msgid "There is no expiration if there are 25 or less RouterInfos."
-msgstr ""
+msgstr "No existe vencimiento si hay 25 o menos menos routerInfos"
 
-#: i2p2www/pages/site/docs/how/network-database.html:115
+#: i2p2www/pages/site/docs/how/network-database.html:129
 msgid ""
 "As the number of local RouterInfos grows, the expiration time shrinks, in"
 " an attempt to maintain\n"
@@ -14422,33 +9387,45 @@ msgid ""
 "routers is 72 hours,\n"
 "while expiration time with 300 routers is around 30 hours."
 msgstr ""
+"Según aumenta el número de RouterInfos, el tiempo de espiración "
+"disminuye, en el intento de mantener un número razonable de RouterInfos ."
+" El número de espiración con menos de 120 ruters es de 72 horas, mientras"
+" que el tiempo de caducidad con 300 ruters es de 30 horas."
 
-#: i2p2www/pages/site/docs/how/network-database.html:120
+#: i2p2www/pages/site/docs/how/network-database.html:134
 #, python-format
 msgid ""
 "RouterInfos containing SSU introducers expire in "
 "about an hour, as\n"
 "the introducer list expires in about that time."
 msgstr ""
+"Los RoutersInfos que contienen introductores SSU "
+"expiran en 1 hora más o menos, ya que la lista del introductor expiran en"
+" ese mismo tiempo."
 
-#: i2p2www/pages/site/docs/how/network-database.html:124
+#: i2p2www/pages/site/docs/how/network-database.html:138
 msgid ""
 "Floodfills use a short expiration time (1 hour) for all local "
 "RouterInfos, as valid RouterInfos will\n"
 "be frequently republished to them."
 msgstr ""
+"Los FloodFills tienen un tiempo de expiración corto (1 hora) para todos "
+"los RoutersInfos locales, ya que como RoutersInfos válidos serán re "
+"publicados."
 
-#: i2p2www/pages/site/docs/how/network-database.html:130
+#: i2p2www/pages/site/docs/how/network-database.html:144
 msgid "RouterInfo Persistent Storage"
-msgstr ""
+msgstr "Almacenamiento persistente de RouterInfo"
 
-#: i2p2www/pages/site/docs/how/network-database.html:132
+#: i2p2www/pages/site/docs/how/network-database.html:146
 msgid ""
 "RouterInfos are periodically written to disk so that they are available "
 "after a restart."
 msgstr ""
+"Los RoutersInfos son periodicamente escritos en el disco duro para que "
+"estén disponibles después de reiniciar."
 
-#: i2p2www/pages/site/docs/how/network-database.html:139
+#: i2p2www/pages/site/docs/how/network-database.html:153
 msgid ""
 "The second piece of data distributed in the netDb is a \"LeaseSet\" - "
 "documenting\n"
@@ -14456,74 +9433,88 @@ msgid ""
 "destination.\n"
 "Each of these leases specify the following information:"
 msgstr ""
+"La segunda parte de los datos distribuidos en la netDb es un \"LeaseSet\""
+" - el cual documenta un conjunto de puntos de entradas de túnel "
+"(leases o  contratos) para una destinación de un cliente en "
+"particular. Cada uno de estos leases especifica la siguiente información:"
 
-#: i2p2www/pages/site/docs/how/network-database.html:145
+#: i2p2www/pages/site/docs/how/network-database.html:159
 msgid "The tunnel gateway router (by specifying its identity)"
-msgstr ""
+msgstr "La puerta de salida de túnel del ruter (especificando su identidad)"
 
-#: i2p2www/pages/site/docs/how/network-database.html:146
+#: i2p2www/pages/site/docs/how/network-database.html:160
 msgid "The tunnel ID on that router to send messages with (a 4 byte number)"
-msgstr ""
+msgstr "El ID del túnel con los que el túnel envía mensajes (un número de 4 bytes)"
 
-#: i2p2www/pages/site/docs/how/network-database.html:147
+#: i2p2www/pages/site/docs/how/network-database.html:161
 msgid "When that tunnel will expire."
-msgstr ""
+msgstr "Cuando expirará ese túnel."
 
-#: i2p2www/pages/site/docs/how/network-database.html:149
+#: i2p2www/pages/site/docs/how/network-database.html:163
 msgid ""
 "The LeaseSet itself is stored in the netDb under\n"
 "the key derived from the SHA256 of the destination."
 msgstr ""
+"El propio LeaseSet es almacenado en la netDb bajo la clave derivada del "
+"hash SHA256 de la destinación."
 
-#: i2p2www/pages/site/docs/how/network-database.html:154
+#: i2p2www/pages/site/docs/how/network-database.html:168
 msgid "In addition to these leases, the LeaseSet includes:"
-msgstr ""
+msgstr "Además de estos leases, el LeaseSet incluye:"
 
-#: i2p2www/pages/site/docs/how/network-database.html:158
+#: i2p2www/pages/site/docs/how/network-database.html:172
 msgid ""
 "The destination itself (a 2048bit ElGamal encryption key, 1024bit DSA "
 "signing key and a certificate)"
 msgstr ""
+"La destinación en sí misma (una clave de 2048 bits ElGamal, una clave de "
+"firmado DSA de 1024 bits y un certificado)"
 
-#: i2p2www/pages/site/docs/how/network-database.html:159
+#: i2p2www/pages/site/docs/how/network-database.html:173
 msgid ""
 "Additional encryption public key: used for end-to-end encryption of "
 "garlic messages"
 msgstr ""
+"Una clave pública de cifrado adicional: usada para el cifrado de fin a "
+"fin de los mensajes garlic"
 
-#: i2p2www/pages/site/docs/how/network-database.html:160
+#: i2p2www/pages/site/docs/how/network-database.html:174
 msgid ""
 "Additional signing public key: intended for LeaseSet revocation, but is "
 "currently unused."
 msgstr ""
+"Una clave de firma pública adicional: para la revocación del LeaseSet, "
+"pero actualmente no se usa."
 
-#: i2p2www/pages/site/docs/how/network-database.html:161
+#: i2p2www/pages/site/docs/how/network-database.html:175
 msgid ""
 "Signature of all the LeaseSet data, to make sure the Destination "
 "published the LeaseSet."
 msgstr ""
+"La firma de toda la información del LeaseSet, para asegurarse de que la "
+"Destinación publicó ese LeaseSet."
 
-#: i2p2www/pages/site/docs/how/network-database.html:165
+#: i2p2www/pages/site/docs/how/network-database.html:179
 msgid "Lease specification"
-msgstr ""
+msgstr "Especificaciones del Lease"
 
-#: i2p2www/pages/site/docs/how/network-database.html:167
+#: i2p2www/pages/site/docs/how/network-database.html:181
 msgid "LeaseSet specification"
-msgstr ""
+msgstr "Especificaciones del LeaseSet"
 
-#: i2p2www/pages/site/docs/how/network-database.html:170
+#: i2p2www/pages/site/docs/how/network-database.html:184
 msgid "Lease Javadoc"
-msgstr ""
+msgstr "Javadoc del Lease"
 
-#: i2p2www/pages/site/docs/how/network-database.html:172
+#: i2p2www/pages/site/docs/how/network-database.html:186
 msgid "LeaseSet Javadoc"
-msgstr ""
+msgstr "Javadoc del LeaseSet"
 
-#: i2p2www/pages/site/docs/how/network-database.html:176
+#: i2p2www/pages/site/docs/how/network-database.html:190
 msgid "Unpublished LeaseSets"
-msgstr ""
+msgstr "LeaseSets no publicados"
 
-#: i2p2www/pages/site/docs/how/network-database.html:177
+#: i2p2www/pages/site/docs/how/network-database.html:191
 msgid ""
 "A LeaseSet for a destination used only for outgoing connections is "
 "unpublished.\n"
@@ -14534,12 +9525,19 @@ msgid ""
 "destinations,\n"
 "because of I2NP storage messages."
 msgstr ""
+"Una destinación LeaseSet sólo usada para conexiones de salida que no "
+"será publicada. Nunca será enviada para publicarse en los ruters "
+"floodfill. Los túneles \"Cliente\", como aquellos que se usan para "
+"navegarse o para los clientes IRC, nunca se publican. Los servidores "
+"podrán todavía enviar mensajes a esas destinaciones no publicadas, "
+"gracias a los mensajes de "
+"almacenamiento I2NP."
 
-#: i2p2www/pages/site/docs/how/network-database.html:187
+#: i2p2www/pages/site/docs/how/network-database.html:201
 msgid "Revoked LeaseSets"
-msgstr ""
+msgstr "LeaseSets Revocados"
 
-#: i2p2www/pages/site/docs/how/network-database.html:188
+#: i2p2www/pages/site/docs/how/network-database.html:202
 msgid ""
 "A LeaseSet may be revoked by publishing a new LeaseSet with zero "
 "leases.\n"
@@ -14550,12 +9548,17 @@ msgid ""
 "This is the only planned use for that signing key, so it is currently "
 "unused."
 msgstr ""
+"Un LeaseSet puede ser revocado publicando un nuevo LeaseSet sin "
+"leases. Las revocaciones tienen que ser firmadas por la clave de firmado "
+"adicional del LeaseSet. La revocación no está completamente implementada,"
+" y no está claro si tiene algún uso práctico. Este es el único uso "
+"planeado para la clave de firmado, por lo cual no se usa."
 
-#: i2p2www/pages/site/docs/how/network-database.html:195
+#: i2p2www/pages/site/docs/how/network-database.html:209
 msgid "Encrypted LeaseSets"
-msgstr ""
+msgstr "LeaseSets Cifrados"
 
-#: i2p2www/pages/site/docs/how/network-database.html:196
+#: i2p2www/pages/site/docs/how/network-database.html:210
 msgid ""
 "In an encrypted LeaseSet, all Leases are encrypted with a separate"
 " DSA key.\n"
@@ -14569,33 +9572,45 @@ msgid ""
 "research whether the user interface and implementation of encrypted "
 "LeaseSets could be improved."
 msgstr ""
+"En un LeaseSet cifrado, todos los Leases están cifrados con una clave DSA"
+" separada. Estos Leases sólo se decodificaran, y entonces se podrá "
+"contactar con la destinación, por aquellos que posean la clave. No hay "
+"ninguna marca u otra indicación directa de que un LeaseSer vaya cifrado. "
+"Los LEaseSets no son usados extensamente, y es un tema para trabajar en "
+"el futuro, cuando el interfaz de usuario y la implementación de los "
+"LeaseSets cifrados sean mejores."
 
-#: i2p2www/pages/site/docs/how/network-database.html:205
+#: i2p2www/pages/site/docs/how/network-database.html:219
 msgid "LeaseSet Expiration"
-msgstr ""
+msgstr "Expiración del LeaseSet"
 
-#: i2p2www/pages/site/docs/how/network-database.html:206
+#: i2p2www/pages/site/docs/how/network-database.html:220
 msgid ""
 "All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet "
 "expires\n"
 "10 minutes after the earliest creation time of all its Leases."
 msgstr ""
+"Todos los Leases (túneles) son válidos sólo durante 10 minutos; por lo "
+"tanto, un LeaseSet expira 10 minutos más tarde que el tiempo de creación "
+"de todos sus Leases."
 
-#: i2p2www/pages/site/docs/how/network-database.html:211
+#: i2p2www/pages/site/docs/how/network-database.html:225
 msgid "LeaseSet Persistent Storage"
-msgstr ""
+msgstr "Almacenamiento persistente del LeaseSet"
 
-#: i2p2www/pages/site/docs/how/network-database.html:212
+#: i2p2www/pages/site/docs/how/network-database.html:226
 msgid ""
 "There is no persistent storage of LeaseSet data since they expire so "
 "quickly."
 msgstr ""
+"No existe el almacenamiento persistente de LeaseSets ya que expiran muy "
+"rápido."
 
-#: i2p2www/pages/site/docs/how/network-database.html:217
+#: i2p2www/pages/site/docs/how/network-database.html:231
 msgid "Bootstrapping"
-msgstr ""
+msgstr "Secuencia de arranque"
 
-#: i2p2www/pages/site/docs/how/network-database.html:218
+#: i2p2www/pages/site/docs/how/network-database.html:232
 msgid ""
 "The netDb is decentralized, however you do need at\n"
 "least one reference to a peer so that the integration process\n"
@@ -14615,12 +9630,19 @@ msgid ""
 "from\n"
 "one of these URLs, selected at random."
 msgstr ""
+"La netDb es descentralizada, aún así se necesita al menos un par de "
+"referencia para que el proceso de integración nos una a la red. Esto se "
+"consigue \"resembrando\" el ruter con la RouterInfo de un par activo - "
+"específicamente, obteniendo el archivo routerInfo-$hash.dat "
+"y almacenándolo en su directorio netDb/. Cualquiera puede "
+"proporcionarle estos archivos - incluso se pueden proporcionar a otros "
+"exponiendo su propia directorio netDb. Esto simplifica el proceso, "
+"algunos voluntarios publican sus directorios netDb (o un subconjunto) en "
+"el Internet normal (fuera de I2P), y las URL de estos directorios están "
+"codificadas dentro de I2P. Cuando el ruter se arranca por primera vez, "
+"automáticamente se conecta a estas URLs aleatoriamente para obtenerlos."
 
-#: i2p2www/pages/site/docs/how/network-database.html:232
-msgid "Floodfill"
-msgstr ""
-
-#: i2p2www/pages/site/docs/how/network-database.html:233
+#: i2p2www/pages/site/docs/how/network-database.html:247
 msgid ""
 "The floodfill netDb is a simple distributed storage mechanism.\n"
 "The storage algorithm is simple: send the data to the closest peer that "
@@ -14638,33 +9660,52 @@ msgid ""
 "The peers selected are the ones closest (according to the XOR-metric) to a specific key."
 msgstr ""
+"El floodfill netDb is simplemente un mecanismo de almacenamiento "
+"distribuido. El algoritmo de almacenamiento es simple: envía los datos al"
+" par más cercano que se haya anunciado como floodfill. Espera 10 "
+"segundos, alije otro ruter floodfill y le pregunta por la entrada a "
+"enviar, verificando su propia introducción / distribución. Si el par de "
+"verificación no responde, o no tienen la entrada pedida, el transmisor "
+"repite el proceso. Cuando un par de la netDb floodfill recibe un "
+"almacenamiento netDb de un par que no está en la netDb floodfill, lo "
+"envía a un subconjunto del los pares floodfill netDb. Los pares "
+"seleccionados son los más cercanos a una clave especificada (de acuerdo "
+"con el XOR-metric)."
 
-#: i2p2www/pages/site/docs/how/network-database.html:244
+#: i2p2www/pages/site/docs/how/network-database.html:258
 msgid ""
 "Determining who is part of the floodfill netDb is trivial - it is exposed"
 " in each \n"
 "router's published routerInfo as a capability."
 msgstr ""
+"Determinar quien es parte del floodfill netDb es algo trivial - se "
+"muestra en el routerinfo publicado de cada ruter como una capacidad."
 
-#: i2p2www/pages/site/docs/how/network-database.html:249
+#: i2p2www/pages/site/docs/how/network-database.html:263
 msgid ""
 "Floodfills have no central authority and do not form a \"consensus\" -\n"
 "they only implement a simple DHT overlay."
 msgstr ""
+"Los flodfill no tienen inguna autoridad central y no forman ningún "
+"\"consenso\" - sólo implementan una capa DHT."
 
-#: i2p2www/pages/site/docs/how/network-database.html:256
+#: i2p2www/pages/site/docs/how/network-database.html:270
 msgid "Floodfill Router Opt-in"
-msgstr ""
+msgstr "Convertirse en un ruter floodfill"
 
-#: i2p2www/pages/site/docs/how/network-database.html:258
+#: i2p2www/pages/site/docs/how/network-database.html:272
 msgid ""
 "Unlike Tor, where the directory servers are hardcoded and trusted,\n"
 "and operated by known entities,\n"
 "the members of the I2P floodfill peer set need not be trusted, and\n"
 "change over time."
 msgstr ""
+"Al contrario que en Tor, donde los servidores están incluidos y son de "
+"confianza, y operados por identidades conocidas, los miembros de los "
+"pares floodfill de I2P no necesitas ser de confianza, y cambian con el "
+"tiempo."
 
-#: i2p2www/pages/site/docs/how/network-database.html:265
+#: i2p2www/pages/site/docs/how/network-database.html:279
 msgid ""
 "To increase reliability of the netDb, and minimize the impact\n"
 "of netDb traffic on a router, floodfill is automatically enabled\n"
@@ -14675,23 +9716,36 @@ msgid ""
 "The current minimum share bandwidth for a floodfill router is 128 "
 "KBytes/sec."
 msgstr ""
+"Para incrementar la seguridad de la netDb, y minimizar el impacto del "
+"tráfico de la netDb en un ruter, floodfill solo está activo por defecto "
+"en los ruters configurados para compartir un gran ancho de banda. Los "
+"ruters con límites grandes de compartición de ancho de banda (lo que se "
+"puede configurar manualmente, ya que por defecto es mucho más bajo) "
+"presuntamente tienen conexiones de baja latencia, y es más probable que "
+"estén disponibles 24/7. El ancho de banda mínimo a compartir para "
+"convertirse en floodfill es de 128 KBytes/sec. "
 
-#: i2p2www/pages/site/docs/how/network-database.html:275
+#: i2p2www/pages/site/docs/how/network-database.html:289
 msgid ""
 "In addition, a router must pass several additional tests for health\n"
 "(outbound message queue time, job lag, etc.) before floodfill operation "
 "is\n"
 "automatically enabled."
 msgstr ""
+"Además, un  ruter debe pasar varios pruebas adiciones para comprobar su "
+"salud (tiempo de espera de los mensajes de salida, retraso de los "
+"trabajos, etc) antes de que se active automáticamente como un floodfill."
 
-#: i2p2www/pages/site/docs/how/network-database.html:281
-#, python-format
+#: i2p2www/pages/site/docs/how/network-database.html:295
 msgid ""
-"With the current rules for automatic opt-in, approximately 6% of\n"
+"With the current rules for automatic opt-in, approximately 6% of\n"
 "the routers in the network are floodfill routers."
 msgstr ""
+"Con las reglas actuales para la aceptación automática, aproximadamente el"
+" \n"
+"6% de los routers en la red son routers floodfill."
 
-#: i2p2www/pages/site/docs/how/network-database.html:286
+#: i2p2www/pages/site/docs/how/network-database.html:300
 msgid ""
 "While some peers are manually configured to be floodfill,\n"
 "others are simply high-bandwidth routers who automatically volunteer\n"
@@ -14701,12 +9755,19 @@ msgid ""
 "In turn, these peers will un-floodfill themselves when there are\n"
 "too many floodfills outstanding."
 msgstr ""
+"Mientras que algunos pares se configuran manualmente para ser floodfill, "
+"otros son simplemente ruters con gran ancho de banda que son "
+"automáticamente convertidos en floodfill cuando el número de pares "
+"floodfill baja de un límite. Esto evita el daño por un tiempo largo "
+"cuando se pierden la mayoría de los ruters floodfill a causa de un "
+"ataque. A su vez, estos pares dejarán de ser floodfill cuando ya haya "
+"suficientes floodfills activos."
 
-#: i2p2www/pages/site/docs/how/network-database.html:296
+#: i2p2www/pages/site/docs/how/network-database.html:310
 msgid "Floodfill Router Roles"
-msgstr ""
+msgstr "El papel del ruter floodfill"
 
-#: i2p2www/pages/site/docs/how/network-database.html:297
+#: i2p2www/pages/site/docs/how/network-database.html:311
 msgid ""
 "A floodfill router's only services that are in addition to those of non-"
 "floodfill routers\n"
@@ -14716,12 +9777,19 @@ msgid ""
 "(i.e. be a \"relay\" for others), but this is not directly related to "
 "their distributed database services."
 msgstr ""
+"Los únicos servicios que tienen de más los ruters floodfill que no tienen"
+" los ruters no floodfill es aceptar almacenamientos en la netDb y el "
+"responder a las solicitudes de la netDb. Ya que normalmente tienen un "
+"gran ancho de banda, es más usual que participen en un gran número de "
+"túneles (por ejemplo como un \"relay\" para otros), pero esto no está "
+"relacionado directamente con sus servicios distribuidos de la base de "
+"datos."
 
-#: i2p2www/pages/site/docs/how/network-database.html:305
+#: i2p2www/pages/site/docs/how/network-database.html:319
 msgid "Kademlia Closeness Metric"
-msgstr ""
+msgstr "Medida de cercanía Kademlia"
 
-#: i2p2www/pages/site/docs/how/network-database.html:306
+#: i2p2www/pages/site/docs/how/network-database.html:320
 msgid ""
 "The netDb uses a simple Kademlia-style XOR metric to determine closeness."
 "\n"
@@ -14739,23 +9807,27 @@ msgid ""
 "rotation\",\n"
 "although it isn't strictly a rotation."
 msgstr ""
+"LA NetDb usa una medida XOR simple al estilo Kademlia para determinar la "
+"cercanía. "
 
-#: i2p2www/pages/site/docs/how/network-database.html:318
+#: i2p2www/pages/site/docs/how/network-database.html:332
 msgid ""
 "Routing keys are never sent on-the-wire in any I2NP message, they are "
 "only used locally for\n"
 "determination of distance."
 msgstr ""
+"Las claves de enrutado nunca se envían por-el-cable en ninguno de los \n"
+"mensajes I2NP, sólo se usan localmente para determinar la distancia."
 
-#: i2p2www/pages/site/docs/how/network-database.html:325
+#: i2p2www/pages/site/docs/how/network-database.html:339
 msgid "Storage, Verification, and Lookup Mechanics"
-msgstr ""
+msgstr "Mecanismos de almacenaje, verificación y bloqueo"
 
-#: i2p2www/pages/site/docs/how/network-database.html:327
+#: i2p2www/pages/site/docs/how/network-database.html:341
 msgid "RouterInfo Storage to Peers"
-msgstr ""
+msgstr "Almacenamiento del RouterInfo en los pares"
 
-#: i2p2www/pages/site/docs/how/network-database.html:328
+#: i2p2www/pages/site/docs/how/network-database.html:342
 #, python-format
 msgid ""
 "I2NP DatabaseStoreMessages containing the local "
@@ -14763,12 +9835,16 @@ msgid ""
 "as a part of the initialization of a NTCP\n"
 "or SSU transport connection."
 msgstr ""
+"Los mensajes I2NP DatabaseStoreMessages que "
+"contienen el RouterInfo local son intercambiados con pares como parte de "
+"la inicialización de una conexión de transporte NTCP o SSU."
 
-#: i2p2www/pages/site/docs/how/network-database.html:335
+#: i2p2www/pages/site/docs/how/network-database.html:349
 msgid "LeaseSet Storage to Peers"
-msgstr ""
+msgstr "Almacenamiento del LeaseSet en los pares"
 
-#: i2p2www/pages/site/docs/how/network-database.html:336
+#: i2p2www/pages/site/docs/how/network-database.html:350
 #, python-format
 msgid ""
 "I2NP DatabaseStoreMessages containing the local "
@@ -14780,8 +9856,15 @@ msgid ""
 "without requiring any LeaseSet lookups, or requiring the communicating "
 "Destinations to have published LeaseSets at all."
 msgstr ""
+"Los mensajes I2NP DatabaseStoreMessages que "
+"contienen el LeaseSet  local son intercambiados periódicamente con pares "
+"agrupándolos en un mensaje garlic junto con el tráfico normal desde la "
+"Destinación relacionada. Esto permite enviar una respuesta inicial, y una"
+" respuesta posterior, al Lease apropiado, sin necesidad de hacer "
+"búsquedas de LeaseSet, o tener que comunicarse con las Destinaciones para"
+" publicar los LeaseSets."
 
-#: i2p2www/pages/site/docs/how/network-database.html:344
+#: i2p2www/pages/site/docs/how/network-database.html:358
 msgid ""
 "The DatabaseStoreMessage should be sent to the floodfill that is closest\n"
 "to the current routing key for the RouterInfo or LeaseSet being stored.\n"
@@ -14792,8 +9875,18 @@ msgid ""
 "sending it to multiple other floodfills.\n"
 "This provides a high degree of fault-tolerance."
 msgstr ""
+"El DatabaseStoreMessage (mensaje de almacén de base de datos) debe \n"
+"enviarse al router de inundación (`floodfill`, extienden la red I2P al \n"
+"desplegarse en inundación portando la base de datos distribuida netDb) \n"
+"más cercano al lugar donde se esté guardando la clave de enrutado actual"
+" \n"
+"para el RouterInfo o el LeaseSet. Actualmente el router floodfill más \n"
+"cercano se obtiene mediante una búsqueda en la base de datos local. \n"
+"Incluso si ese router floodfill no es en realidad el más cercano, lo \n"
+"inundará \"hacia si\" enviándo el mensaje a otros múltiples routers de \n"
+"inundación. Esto proporciona un alto grado de tolerencia a fallos."
 
-#: i2p2www/pages/site/docs/how/network-database.html:353
+#: i2p2www/pages/site/docs/how/network-database.html:367
 msgid ""
 "In traditional Kademlia, a peer would do a \"find-closest\" search before"
 " inserting\n"
@@ -14813,12 +9906,30 @@ msgid ""
 "distant peer had\n"
 "the netdb item."
 msgstr ""
+"En el Kademlia tradicional, un par (`peer`) haría una búsqueda \"find-"
+"closest\" \n"
+"(encuentra al más cercano) antes de insertar un elemento en la DHT (tabla"
+" de hash dinámica) hacia el objetivo más cercano. Como la operación de \n"
+"verificación tenderá a descubrir los routers floodfills más \n"
+"cercanos si están presentes, un router mejorará rápidamente su \n"
+"conocimiento del \"vecindario\" de la DHT para el RouterInfo (información"
+" para \n"
+"contactar routers) y los LeaseSets (información para contactar destinos)"
+" \n"
+"que publica regularmente. Aunque I2NP no define un mensaje \"find-"
+"closest\", \n"
+"si fuera necesario un router simplemente podría hacer una búsqueda "
+"iterativa de la clave con el bit menos significativo invertido (es decir,"
+" la clave ^ 0x01) hasta que no se reciban pares más cercanos en los "
+"DatabaseSearchReplyMessages (mensajes de respuesta de búsqueda de la base"
+" de datos). Esto asegura que se encontrará al verdadero par más cercano "
+"incluso si un par más-distante tiene el elemento netDb."
 
-#: i2p2www/pages/site/docs/how/network-database.html:366
+#: i2p2www/pages/site/docs/how/network-database.html:380
 msgid "RouterInfo Storage to Floodfills"
-msgstr ""
+msgstr "Almacenamiento de RouterInfo en los Floodfills"
 
-#: i2p2www/pages/site/docs/how/network-database.html:367
+#: i2p2www/pages/site/docs/how/network-database.html:381
 #, python-format
 msgid ""
 "A router publishes its own RouterInfo by directly connecting to a "
@@ -14832,19 +9943,30 @@ msgid ""
 "I2NP DeliveryStatusMessage,\n"
 "with the Message ID set to the value of the Reply Token."
 msgstr ""
+"Un ruter publica su propia RouterInfo conectándose directamente a un "
+"ruter Floodfill y enviando un I2NP "
+"DatabaseStoreMessage con un token de respuesta no vacío. Este mensaje "
+"está cifrado de fin a fin como Garlic, y es una conexión directa, con lo "
+"cual no hay ruters en medio (no se necesita ocultar ninguna información)."
+" El ruter floodfill responde con un \n"
+"I2NP DeliveryStatusMessage, con el ID del "
+"mensaje puesto en el valor del token de respuesta."
 
-#: i2p2www/pages/site/docs/how/network-database.html:381
+#: i2p2www/pages/site/docs/how/network-database.html:395
 msgid "LeaseSet Storage to Floodfills"
-msgstr ""
+msgstr "Almacenamiento de LeaseSet en los Floodfills"
 
-#: i2p2www/pages/site/docs/how/network-database.html:382
+#: i2p2www/pages/site/docs/how/network-database.html:396
 msgid ""
 "Storage of LeaseSets is much more sensitive than for RouterInfos, as a "
 "router\n"
 "must take care that the LeaseSet cannot be associated with the router."
 msgstr ""
+"El almacenamiento de los LeaseSets es mucho más sensible que el de los "
+"RouterInfos, ya que un ruter debe de tener cuidad de que el LeaseSet no "
+"pueda ser asociado con el ruter."
 
-#: i2p2www/pages/site/docs/how/network-database.html:387
+#: i2p2www/pages/site/docs/how/network-database.html:401
 #, python-format
 msgid ""
 "A router publishes a local LeaseSet by\n"
@@ -14859,19 +9981,29 @@ msgid ""
 "with the Message ID set to the value of the Reply Token.\n"
 "This message is sent back to one of the client's inbound tunnels."
 msgstr ""
+"Un ruter publica un LeaseSet local enviando un I2NP DatabaseStoreMessage con un token de respuesta"
+" no vacío sobre un túnel cliente de salida desde esa Destinación. Este "
+"mensaje es cifrado de fin a fin con Garlic usando el administrador de "
+"claves de la sesión de la Destinación, para ocultar el mensaje en el "
+"punto final del túnel de salida. El ruter floodfill responde con un I2NP DeliveryStatusMessage, con el ID del mensaje "
+"puesto como el token de respuesta. Este mensaje es enviado de vuelta a "
+"los túneles de entrada del cliente."
 
-#: i2p2www/pages/site/docs/how/network-database.html:400
+#: i2p2www/pages/site/docs/how/network-database.html:414
 msgid "Flooding"
-msgstr ""
+msgstr "Inundación"
 
-#: i2p2www/pages/site/docs/how/network-database.html:401
+#: i2p2www/pages/site/docs/how/network-database.html:415
+#, python-format
 msgid ""
 "After a floodfill router receives a DatabaseStoreMessage containing a\n"
 "valid RouterInfo or LeaseSet which is newer than that previously stored "
 "in its\n"
 "local NetDb, it \"floods\" it.\n"
-"To flood a NetDb entry, it looks up several (currently 4) floodfill "
-"routers closest to the routing key\n"
+"To flood a NetDb entry, it looks up several (currently %(floodsize)s) "
+"floodfill routers closest to the routing key\n"
 "of the NetDb entry. (The routing key is the SHA256 Hash of the "
 "RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n"
 "By flooding to those closest to the key, not closest to itself, the "
@@ -14880,8 +10012,29 @@ msgid ""
 "knowledge of the\n"
 "DHT \"neighborhood\" for the routing key."
 msgstr ""
+"Después de que un router floodfill (de inundación) reciba un "
+"DatabaseStoreMessage\n"
+"conteniendo un RouterInfo (información para contactar con un router) o "
+"LeaseSet\n"
+"(información para contactar con un Destino) que esté más actualizado que "
+"el guardado\n"
+"previamente en su NetDb local, lo \"inunda\". Para inundar una entrada "
+"NetDb, busca\n"
+"varios (actualmente %(floodsize)s) routers floodfill más próximos a la "
+"clave de enrutamiento\n"
+"de la entrada NetDb. (La clave de enrutamiento es el (identificador "
+"criptográfico)\n"
+"Hash SHA256 de la RouterIdentity o Destino con la fecha (aaaaMMdd) como "
+"sufijo).\n"
+"Mediante la inundación a aquellos más próximos a la clave, no los más "
+"próximos a\n"
+"si mismos, el router flloodfill asegura que el almacenamiento llega al "
+"lugar adecuado,\n"
+"incluso si el router almacenante no tenía un buen conocimiento del "
+"\"vecindario\"\n"
+"DHT (tabla de hash distribuida) de la clave de enrutamiento."
 
-#: i2p2www/pages/site/docs/how/network-database.html:412
+#: i2p2www/pages/site/docs/how/network-database.html:426
 #, python-format
 msgid ""
 "The floodfill then directly connects to each of those peers\n"
@@ -14891,12 +10044,23 @@ msgid ""
 "(and no need to hide this data anyway).\n"
 "The other routers do not reply or re-flood, as the Reply Token is zero."
 msgstr ""
+"El router floodfill conecta entonces directamente a cada uno de esos \n"
+"pares y les envía un DatabaseStoreMessage I2NP "
+"con una \n"
+"credencial (`token`) de respueta cero. El mensaje no está cifrado \n"
+"extremo-a-extremo con garlic (ajo), ya que esta es una conexión directa,"
+" \n"
+"así que no hay routers intervinientes (y de todas formas no hay necesidad"
+" \n"
+"de esconder este dato). Los otros routers no responden ni re-inundan, ya"
+" \n"
+"que la credencial de respuesta es cero."
 
-#: i2p2www/pages/site/docs/how/network-database.html:422
+#: i2p2www/pages/site/docs/how/network-database.html:436
 msgid "RouterInfo and LeaseSet Lookup"
-msgstr ""
+msgstr "Búsquedas de RouterInfo y LeaseSet"
 
-#: i2p2www/pages/site/docs/how/network-database.html:423
+#: i2p2www/pages/site/docs/how/network-database.html:437
 #, python-format
 msgid ""
 "The I2NP DatabaseLookupMessage is used to "
@@ -14905,14 +10069,23 @@ msgid ""
 "The replies are specified to return via one of the router's inbound "
 "exploratory tunnels."
 msgstr ""
+"El DatabaseLookupMessage (mensaje de consulta a la base de datos) de \n"
+"I2NP se usa para solicitar una entrada netDb \n"
+"desde un router floodfill. \n"
+"Las consultas se transmiten por uno de los túneles exploratorios de "
+"salida del router. Las respuestas están definidas para volver a través de"
+" uno de los túneles exploratorios de entrada del router."
 
-#: i2p2www/pages/site/docs/how/network-database.html:429
+#: i2p2www/pages/site/docs/how/network-database.html:443
 msgid ""
 "Lookups are generally sent to the two \"good\" (the connection doesn't "
 "fail) floodfill routers closest to the requested key, in parallel."
 msgstr ""
+"Las consultas generalmente se envían a los dos routers floodfill \n"
+"\"buenos\" (en los que la conexión no falla) más próximos a la clave \n"
+"solicitada, en paralelo."
 
-#: i2p2www/pages/site/docs/how/network-database.html:433
+#: i2p2www/pages/site/docs/how/network-database.html:447
 #, python-format
 msgid ""
 "If the key is found locally by the floodfill router, it responds with a\n"
@@ -14922,8 +10095,16 @@ msgid ""
 "I2NP DatabaseSearchReplyMessage\n"
 "containing a list of other floodfill routers close to the key."
 msgstr ""
+"Si el router floodfill encuentra la clave localmente, \n"
+"responde con un DatabaseStoreMessage (mensaje de almacenaje en la \n"
+"base de datos) de I2NP. Si el router floodfill "
+"no encontró la clave \n"
+"localmente, responde con un DatabaseSearchReplyMessage (mensaje de \n"
+"respuesta a búsqueda en la base de datos) de I2NP conteniendo una \n"
+"lista de otros routers floodfill próximos a la clave."
 
-#: i2p2www/pages/site/docs/how/network-database.html:441
+#: i2p2www/pages/site/docs/how/network-database.html:455
 msgid ""
 "LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n"
 "RouterInfo lookups are not encrypted and thus are vulnerable to snooping "
@@ -14932,8 +10113,16 @@ msgid ""
 "encryption.\n"
 "RouterInfo lookup encryption may be enabled in a future release."
 msgstr ""
+"Las consultas de LeaseSet (información para contactar destinos) están "
+"cifradas extremo-a-extremo con garlic (ajo) desde la versión 0.9.5. Las "
+"consultas de RouterInfo (información para contactar routers) no están \n"
+"cifradas y por tanto son vulnerables a espionaje por el extremo exterior"
+" \n"
+"(outbound endpoint, OBEP) del túnel cliente. Esto es debido a lo caro del"
+" cifrado ElGamal. El cifrado de la consulta RouterInfo puede que sea "
+"habilitado en una futura versión."
 
-#: i2p2www/pages/site/docs/how/network-database.html:448
+#: i2p2www/pages/site/docs/how/network-database.html:462
 msgid ""
 "As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage"
 " or a DatabaseSearchReplyMessage)\n"
@@ -14943,15 +10132,26 @@ msgid ""
 "Responses to RouterInfo lookups will be encrypted if we enable the lookup"
 " encryption."
 msgstr ""
+"Desde la versión 0.9.7 las respuestas a una consulta de LeaseSet (un \n"
+"DatabaseStoreMessage o un DatabaseSearchReplyMessage) estarán \n"
+"cifradas mediante la inclusión de la clave de sesión y la etiqueta en la"
+" \n"
+"consulta. Esto esconde la respuesta desde la pasarela de entrada (inbound"
+" \n"
+"gateway, IBGW) del túnel de respuesta. Las respuestas a consultas a de \n"
+"RouterInfo serán cifradas si se habilita el cifrado de consultas."
 
-#: i2p2www/pages/site/docs/how/network-database.html:455
+#: i2p2www/pages/site/docs/how/network-database.html:469
 #, python-format
 msgid ""
 "(Reference: Hashing it out in Public Sections "
 "2.2-2.3 for terms below in italics)"
 msgstr ""
+"(Referencia: Hashing it out in Public "
+"(Discutiéndolo en público [juego de palabras]) Secciones 2.2-2.3 para los"
+" términos en itálica de debajo)"
 
-#: i2p2www/pages/site/docs/how/network-database.html:459
+#: i2p2www/pages/site/docs/how/network-database.html:473
 msgid ""
 "Due to the relatively small size of the network and the flooding "
 "redundancy of 8x,\n"
@@ -14966,8 +10166,23 @@ msgid ""
 "Queries were sent through multiple routes simultaneously\n"
 "to reduce the chance of query failure."
 msgstr ""
+"Debido al relativamente pequeño tamaño de la red y la redundancia de la \n"
+"inundación por un factor 8x, las consultas son habitualmente O(1) más "
+"bien que O(log n) -- un router es altamente probable que conozca un "
+"router floodfill suficientemente cercano a la clave para obtener la "
+"respuesta \n"
+"en el primer intento. En versiones anteriores a la 0.8.9, los routers "
+"usaban \n"
+"una redundancia de consulta de dos (esto es, se realizaban dos consultas"
+" \n"
+"en paralelo a direferentes pares), y ni el enrutado recursivo ni "
+"el \n"
+"iterativo estaba implementado para las consultas. Las peticiones "
+"se \n"
+"enviaban a través de múltiples rutas simultáneamente para "
+"reducir la posibilidad de fallo de consulta."
 
-#: i2p2www/pages/site/docs/how/network-database.html:470
+#: i2p2www/pages/site/docs/how/network-database.html:484
 msgid ""
 "As of release 0.8.9, iterative lookups are implemented with no "
 "lookup redundancy.\n"
@@ -14984,8 +10199,25 @@ msgid ""
 "lookup timeout is reached,\n"
 "or the maximum number of peers is queried."
 msgstr ""
+"Desede la versión 0.8.9 las consultas iterativas se implementaron "
+"sin \n"
+"redundancia en la consulta. Esta es una consulta más eficiente y fiable, "
+"que \n"
+"funcionará mucho mejor cuando no sean conocidos todos los pares de \n"
+"inundación (`floodfill peers`), y elimina una seria limitación al "
+"crecimiento de \n"
+"la red. Al crecer la red y que cada router conozca sólo un pequeño \n"
+"subconjunto de los pares de inundación, las consultas llegarán a ser "
+"O(log n). Incluso si los pares no devuelven referencias más cercanas a la"
+" clave, la \n"
+"consulta continúa con el par más-próximo-a-continuación, para añadir \n"
+"robustez, y para prevenir que un par de inundación malicioso acapare "
+"(`black-holing`) una parte del espacio de la clave. Las consultas "
+"continúan \n"
+"hasta que se alcance el total del tiempo límite de la consulta o se haya "
+"consultado al número de pares máximo."
 
-#: i2p2www/pages/site/docs/how/network-database.html:482
+#: i2p2www/pages/site/docs/how/network-database.html:496
 msgid ""
 "Node IDs are verifiable in that we use the router hash "
 "directly as both the node ID and the Kademlia key.\n"
@@ -14994,12 +10226,38 @@ msgid ""
 "Given the current size of the network, a router has\n"
 "detailed knowledge of the neighborhood of the destination ID space."
 msgstr ""
+"Los identificadores (`IDs`) de nodos son verificables en "
+"aquellos [nodos] en los que usamos el identificador criptográfico del "
+"router (`hash`) directamente tanto como identificador (`ID`) de nodo y "
+"como clave \n"
+"Kademlia. Las respuestas incorrectas que no sean más cercanas a la clave"
+" \n"
+"de búsqueda son ignoradas por lo general. Dado el actual tamaño de la "
+"red, \n"
+"un router tiene conocimiento detallado del vecindario del espacio del "
+"identicador (`ID`) del destino."
 
-#: i2p2www/pages/site/docs/how/network-database.html:491
+#: i2p2www/pages/site/docs/how/network-database.html:505
 msgid "RouterInfo Storage Verification"
-msgstr ""
+msgstr "Verificación del almacenamiento de la RouterInfo"
 
-#: i2p2www/pages/site/docs/how/network-database.html:492
+#: i2p2www/pages/site/docs/how/network-database.html:506
+#, python-format
+msgid ""
+"Note: RouterInfo verification is disabled as of release 0.9.7.1 to "
+"prevent\n"
+"the attack described in the paper\n"
+"Practical Attacks Against the I2P Network.\n"
+"It is not clear if verification can be redesigned to be done safely."
+msgstr ""
+"Nota: La verificación del RouterInfo (información para contactar con un\n"
+"router) está deshabilitada desde la versión 0.9.7.1 para prevenir el\n"
+"ataque descrito en el ensayo (ataques prácticos contra la red I2P)\n"
+"Practical Attacks Against the I2P Network.\n"
+"No está claro si la verificación puede rediseñarse para ser realizada de "
+"forma segura."
+
+#: i2p2www/pages/site/docs/how/network-database.html:513
 msgid ""
 "To verify a storage was successful, a router simply waits about 10 "
 "seconds,\n"
@@ -15009,12 +10267,20 @@ msgid ""
 "Lookups are end-to-end garlic encrypted to prevent snooping by the "
 "outbound endpoint(OBEP)."
 msgstr ""
+"Para verificar que un almacenamiento fue exitoso, un router simplemente "
+"espera cerca de 10 segundos, entonces envía una consulta a otro router de"
+" \n"
+"inundación (`floodfill`) cercano a la clave (pero no al que se envió el \n"
+"almacenamiento). Las consultas establecieron uno de los túneles \n"
+"exploratorios de salida del router. Las consultas están cifradas \n"
+"extremo-a-extremo con garlic (ajo) para prevenir la vigilancia en el "
+"extremo exterior (OutBound End Point, OBEP)."
 
-#: i2p2www/pages/site/docs/how/network-database.html:500
+#: i2p2www/pages/site/docs/how/network-database.html:521
 msgid "LeaseSet Storage Verification"
-msgstr ""
+msgstr "Verificación del almacenamiento del LeaseSet"
 
-#: i2p2www/pages/site/docs/how/network-database.html:501
+#: i2p2www/pages/site/docs/how/network-database.html:522
 msgid ""
 "To verify a storage was successful, a router simply waits about 10 "
 "seconds,\n"
@@ -15027,20 +10293,34 @@ msgid ""
 "The replies are specified to return via one of the client's inbound "
 "tunnels."
 msgstr ""
+"Para verificar que el almacenamiento fue exitoso, un router simplemente \n"
+"espera cerca de 10 segundos, y luego envía una consulta a otro router de "
+"inundación (`floodfill`) cercano a la clave (pero no al que se envió el "
+"almacenamiento). Las consultas establecieron uno de los túneles de salida"
+" del cliente para el destino del LeaseSet (grupo de túneles para un "
+"destino) que se está verificando. Para prevenir la vigilancia en el OBEP "
+"(extremo exterior) del túnel de salida, las consultas están cifradas\n"
+"extremo-a-extremo con garlic (ajo). Se especifica a las respuestas que "
+"vuelvan a través de uno de los túneles de entrada del cliente."
 
-#: i2p2www/pages/site/docs/how/network-database.html:511
+#: i2p2www/pages/site/docs/how/network-database.html:532
 msgid ""
 "As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a "
 "DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n"
 "will be encrypted,\n"
 "to hide the reply from the inbound gateway (IBGW) of the reply tunnel."
 msgstr ""
+"Desde la versión 0.9.7, las respuestas tanto para las consultas de "
+"RouterInfo como de LeaseSet (un DatabaseStoreMessage o un \n"
+"DatabaseSearchReplyMessage) estarán cifradas para ocultar la respuesta "
+"desde la pasarela de entrada (`inbound gateway`, IBGW) del túnel de "
+"respuesta."
 
-#: i2p2www/pages/site/docs/how/network-database.html:519
+#: i2p2www/pages/site/docs/how/network-database.html:540
 msgid "Exploration"
 msgstr "Exploración"
 
-#: i2p2www/pages/site/docs/how/network-database.html:520
+#: i2p2www/pages/site/docs/how/network-database.html:541
 #, python-format
 msgid ""
 "Exploration is a special form of netdb lookup, where a router "
@@ -15062,12 +10342,31 @@ msgid ""
 "The floodfill will then respond only with non-floodfill routers close to "
 "the requested key."
 msgstr ""
+"La exploración es una forma especial de consulta netDb, donde un \n"
+"router intenta aprender sobre nuevos routers. Esto lo hace enviando a un "
+"router de inundación (`floodfill`) un DatabaseLookupMessage I2NP, \n"
+"en busca de una clave aleatoria. Como esta consulta fallará, el router de"
+" inundación normalmente respondería con un DatabaseSearchReplyMessage \n"
+"I2NP conteniendo los identificacadores "
+"criptográficos (`hashes`) \n"
+"de routers de inundación cercanos a la clave. Esto no sería de ayuda ya \n"
+"que el router solicitante probablemente ya conoce esos routers de \n"
+"inundación, y no sería práctico añadirlos a TODOS al campo \"no incluir\""
+" de \n"
+"la consulta. Para una petición de exploración, el router solicitante "
+"añade un \n"
+"identificador criptográfico (`hash`) de router, con todo ceros, al campo"
+" \n"
+"\"no incluir\" del DatabaseLookupMessage de la consulta. El router de \n"
+"inundación entonces responderá sólo con routers no-de-inundación \n"
+"cercanos a la clave solicitada."
 
-#: i2p2www/pages/site/docs/how/network-database.html:534
+#: i2p2www/pages/site/docs/how/network-database.html:555
 msgid "Notes on Lookup Responses"
-msgstr ""
+msgstr "Notas sobre las respuestas a consultas"
 
-#: i2p2www/pages/site/docs/how/network-database.html:535
+#: i2p2www/pages/site/docs/how/network-database.html:556
 msgid ""
 "The response to a lookup request is either a Database Store Message (on "
 "success) or a\n"
@@ -15079,12 +10378,22 @@ msgid ""
 "requests in parallel, it is\n"
 "difficult to monitor the performance of the various floodfill routers."
 msgstr ""
+"La respuesta a una solicitud de consulta es o bien (si tiene éxito) un "
+"mensaje de alcemacenamiento en la base de datos (DSM), o (si falla) un "
+"mensaje de respuesta de búsqueda en la base de datos (DSRM). El DSRM \n"
+"contiene un campo 'from' (desde) en el hash del router para indicar la "
+"fuente de la respueta; el DSM no. El campo 'from' (desde) del DSRM no "
+"está \n"
+"autentificado y pude ser vigilado o inválido. No hay otras etiquetas de "
+"respuesta. Por lo tanto, cuando se hacen múltiples solicitudes en "
+"paralelo, es difícill monitorizar el rendimiento de los diferentes "
+"routers de inundación."
 
-#: i2p2www/pages/site/docs/how/network-database.html:545
+#: i2p2www/pages/site/docs/how/network-database.html:566
 msgid "MultiHoming"
-msgstr ""
+msgstr "MultiHoming, multihospedaje"
 
-#: i2p2www/pages/site/docs/how/network-database.html:547
+#: i2p2www/pages/site/docs/how/network-database.html:568
 msgid ""
 "Destinations may be hosted on multiple routers simultaneously, by using "
 "the same\n"
@@ -15100,63 +10409,89 @@ msgid ""
 "The multihoming function has been verified and is in use by several "
 "services on the network."
 msgstr ""
+"Las Destinaciones pueden ser alojadas simultáneamente en múltiples "
+"ruters, usando las mismas claves privadas y públicas (normalmente "
+"almacenadas en los archivos eepPriv.dat). Ya que ambas instancias "
+"publicarán periódicamente sus LeaseSets firmados a los pares floodfill, "
+"el LeaseSet publicado más recientemente será devuelto al par que hizo la "
+"búsqueda en la base de datos.  Ya que los LeaseSets tienen (como mucho) "
+"10 minutos de vida, si alguno de los ruters se cae, el corte será como "
+"mucho de 10 minutos, y normalmente mucho menos tiempo. El sistema de "
+"multihoming ha sido verificado y se usa en varios servicios de la red."
 
-#: i2p2www/pages/site/docs/how/network-database.html:557
+#: i2p2www/pages/site/docs/how/network-database.html:578
 msgid "Threat Analysis"
-msgstr ""
+msgstr "Análisis de amenazas"
 
-#: i2p2www/pages/site/docs/how/network-database.html:558
+#: i2p2www/pages/site/docs/how/network-database.html:579
 #, python-format
 msgid ""
 "Also discussed on the threat model "
 "page."
 msgstr ""
+"También se debate en la web de los "
+"modelos de amenazas."
 
-#: i2p2www/pages/site/docs/how/network-database.html:562
+#: i2p2www/pages/site/docs/how/network-database.html:583
 msgid ""
 "A hostile user may attempt to harm the network by\n"
 "creating one or more floodfill routers and crafting them to offer\n"
 "bad, slow, or no responses.\n"
 "Some scenarios are discussed below."
 msgstr ""
+"Un usuario hostil puede intentar dañar la red creando uno o más ruters "
+"floodfill y configurándolos para ofrecer respuestas malas, lentas o "
+"incluso no ofrecerlas. Algunos escenarios se discuten más abajo."
 
-#: i2p2www/pages/site/docs/how/network-database.html:569
+#: i2p2www/pages/site/docs/how/network-database.html:590
 msgid "General Mitigation Through Growth"
-msgstr ""
+msgstr "Mitigación general a través del crecimiento"
 
-#: i2p2www/pages/site/docs/how/network-database.html:570
+#: i2p2www/pages/site/docs/how/network-database.html:591
+#, python-format
 msgid ""
-"There are currently hundreds of floodfill routers in the network.\n"
+"There are currently around %(ffcount)s floodfill routers in the network.\n"
 "Most of the following attacks will become more difficult, or have less "
 "impact,\n"
 "as the network size and number of floodfill routers increase."
 msgstr ""
+"Actualmente hay alrededor de %(ffcount)s routers floodfill (de "
+"inundación) en la red.\n"
+"La mayoría de los ataques siguientes se harán más difíciles, o tendrán "
+"menos impacto,\n"
+"al incrementarse el tamaño de la red e incrementarse el número de routers"
+" floodfill."
 
-#: i2p2www/pages/site/docs/how/network-database.html:577
+#: i2p2www/pages/site/docs/how/network-database.html:598
 msgid "General Mitigation Through Redundancy"
-msgstr ""
+msgstr "Mitigación general a través de la redundancia"
 
-#: i2p2www/pages/site/docs/how/network-database.html:578
+#: i2p2www/pages/site/docs/how/network-database.html:599
+#, python-format
 msgid ""
-"Via flooding, all netdb entries are stored on the 8 floodfill routers "
-"closest to the key."
+"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill"
+" routers closest to the key."
 msgstr ""
+"Mediante la inundación, todas las entradas NetDb se almacenan en los\n"
+"%(floodsize)s routers floodfill (de inundación ) más próximos a la clave."
 
-#: i2p2www/pages/site/docs/how/network-database.html:583
+#: i2p2www/pages/site/docs/how/network-database.html:604
 msgid "Forgeries"
-msgstr ""
+msgstr "Falsificaciones"
 
-#: i2p2www/pages/site/docs/how/network-database.html:584
+#: i2p2www/pages/site/docs/how/network-database.html:605
 msgid ""
 "All netdb entries are signed by their creators, so no router may forge a\n"
 "RouterInfo or LeaseSet."
 msgstr ""
+"Todas las entradas de la netdb están firmadas por sus creadores, por lo "
+"que ningún ruter puede crear un RouterInfo o un LeaseSet."
 
-#: i2p2www/pages/site/docs/how/network-database.html:589
+#: i2p2www/pages/site/docs/how/network-database.html:610
 msgid "Slow or Unresponsive"
-msgstr ""
+msgstr "Lento o sin respuestas"
 
-#: i2p2www/pages/site/docs/how/network-database.html:590
+#: i2p2www/pages/site/docs/how/network-database.html:611
 #, python-format
 msgid ""
 "Each router maintains an expanded set of statistics in the\n"
@@ -15165,32 +10500,38 @@ msgid ""
 "covering various quality metrics for that peer.\n"
 "The set includes:"
 msgstr ""
+"Cada ruter mantiene un dilatado conjunto de estadísticas en el perfil del par por cada ruter floodfill, "
+"con información sobre varias medidas de calidad de ese par. Este conjunto"
+" incluye:"
 
-#: i2p2www/pages/site/docs/how/network-database.html:597
+#: i2p2www/pages/site/docs/how/network-database.html:618
 msgid "Average response time"
 msgstr "Tiempo medio de respuesta"
 
-#: i2p2www/pages/site/docs/how/network-database.html:598
+#: i2p2www/pages/site/docs/how/network-database.html:619
 msgid "Percentage of queries answered with the data requested"
-msgstr ""
+msgstr "Porcentaje de consultas respondidas con los datos solicitados"
 
-#: i2p2www/pages/site/docs/how/network-database.html:599
+#: i2p2www/pages/site/docs/how/network-database.html:620
 msgid "Percentage of stores that were successfully verified"
 msgstr ""
+"Porcentaje de los almacenamientos que fueron verificados "
+"satisfactoriamente"
 
-#: i2p2www/pages/site/docs/how/network-database.html:600
+#: i2p2www/pages/site/docs/how/network-database.html:621
 msgid "Last successful store"
-msgstr ""
+msgstr "El último almacenaje exitoso"
 
-#: i2p2www/pages/site/docs/how/network-database.html:601
+#: i2p2www/pages/site/docs/how/network-database.html:622
 msgid "Last successful lookup"
-msgstr ""
+msgstr "La última búsqueda exitosa"
 
-#: i2p2www/pages/site/docs/how/network-database.html:602
+#: i2p2www/pages/site/docs/how/network-database.html:623
 msgid "Last response"
 msgstr "Última respuesta"
 
-#: i2p2www/pages/site/docs/how/network-database.html:605
+#: i2p2www/pages/site/docs/how/network-database.html:626
 msgid ""
 "Each time a router needs to make a determination on which floodfill "
 "router is closest to a key,\n"
@@ -15202,20 +10543,30 @@ msgid ""
 "avoided,\n"
 "routers that are only sometimes malicious may be much harder to deal with."
 msgstr ""
+"Cada vez que un ruter necesita determinar cual ruter floodfill está más "
+"cercano a cierta clave, utiliza estas medidas para determinar que "
+"floodfills son \"buenos\". Estos métodos, y umbrales, usados para "
+"determinar \"lo bueno que es\" son relativamente nuevos, y pueden ser "
+"revisados y mejorados. Mientras que un ruter que no responda será "
+"identificado y evitado rápidamente, los ruters que sólo son maliciosos a "
+"veces pueden ser mucho más difíciles de manejar."
 
-#: i2p2www/pages/site/docs/how/network-database.html:615
+#: i2p2www/pages/site/docs/how/network-database.html:636
 msgid "Sybil Attack (Full Keyspace)"
-msgstr ""
+msgstr "Ataque Sybil (espacio de claves completo)"
 
-#: i2p2www/pages/site/docs/how/network-database.html:616
+#: i2p2www/pages/site/docs/how/network-database.html:637
 #, python-format
 msgid ""
 "An attacker may mount a Sybil attack\n"
 "by creating a large number of floodfill routers spread throughout the "
 "keyspace."
 msgstr ""
+"Un atacante puede crear un ataque Sybil creando "
+"un gran número de ruters floodfill repartidos a través del espacio de "
+"claves, keyspace."
 
-#: i2p2www/pages/site/docs/how/network-database.html:621
+#: i2p2www/pages/site/docs/how/network-database.html:642
 #, python-format
 msgid ""
 "(In a related example, a researcher recently created a\n"
@@ -15223,8 +10574,11 @@ msgid ""
 "If successful, this could be an effective DOS attack on the entire "
 "network."
 msgstr ""
+"(Como ejemplo relacionado, recientemente un investigador creó un gran número de relays Tor.) Si es exitoso, podría "
+"ser un ataque DOS efectivo en toda la red."
 
-#: i2p2www/pages/site/docs/how/network-database.html:627
+#: i2p2www/pages/site/docs/how/network-database.html:648
 msgid ""
 "If the floodfills are not sufficiently misbehaving to be marked as "
 "\"bad\" using the peer profile\n"
@@ -15235,8 +10589,15 @@ msgid ""
 "Some possible responses for the I2P network are listed below, however "
 "none of them is completely satisfactory:"
 msgstr ""
+"Si los floodfills no se comportan suficientemente mal para ser marcados "
+"como \"malos\" usando las medidas del perfil del par descritas antes, "
+"sería un escenario muy difícil de manejar. Las respuestas de la red Tor "
+"pueden ser mucho más ágiles en el caso de los relays, ya que los relays "
+"maliciosos pueden ser eliminados manualmente del consenso. Algunas "
+"respuestas factibles para la red I2P son listadas debajo, aunque ninguna "
+"de ellas es totalmente satisfactoria:"
 
-#: i2p2www/pages/site/docs/how/network-database.html:635
+#: i2p2www/pages/site/docs/how/network-database.html:656
 msgid ""
 "Compile a list of bad router hashes or IPs, and announce the list through"
 " various means\n"
@@ -15244,31 +10605,44 @@ msgid ""
 "download the list and\n"
 "add it to their local \"blacklist\"."
 msgstr ""
+"Crear una lista de hashes de ruters malos o IPs, y anunciar la lista de "
+"varias formas (noticias en la consola, web, forums, etc.); los usuarios "
+"tendrían que descargar la lista manualmente y añadirla a \"lista negra\" "
+"local."
 
-#: i2p2www/pages/site/docs/how/network-database.html:640
+#: i2p2www/pages/site/docs/how/network-database.html:661
 msgid ""
 "Ask everyone in the network to enable floodfill manually (fight Sybil "
 "with more Sybil)"
 msgstr ""
+"Pedir a todos los usuarios de la red el activar el floodfill manualmente "
+"(luchar contra Sybil con más Sybil)"
 
-#: i2p2www/pages/site/docs/how/network-database.html:641
+#: i2p2www/pages/site/docs/how/network-database.html:662
 msgid "Release a new software version that includes the hardcoded \"bad\" list"
 msgstr ""
+"Liberar una nueva versión del software que incluya la lista \"mala\" "
+"inscrustada en el código"
 
-#: i2p2www/pages/site/docs/how/network-database.html:642
+#: i2p2www/pages/site/docs/how/network-database.html:663
 msgid ""
 "Release a new software version that improves the peer profile metrics and"
 " thresholds,\n"
 "in an attempt to automatically identify the \"bad\" peers."
 msgstr ""
+"Liberar una versión del software nueva que mejore los umbrales y las "
+"medidas del perfil de los pares, para intentar identificar los pares "
+"\"malos\" automáticamente."
 
-#: i2p2www/pages/site/docs/how/network-database.html:646
+#: i2p2www/pages/site/docs/how/network-database.html:667
 msgid ""
 "Add software that disqualifies floodfills if too many of them are in a "
 "single IP block"
 msgstr ""
+"Añadir una ampliación que descalifique floodfills si hay demasiados de "
+"ellos en un único bloque de IPs"
 
-#: i2p2www/pages/site/docs/how/network-database.html:647
+#: i2p2www/pages/site/docs/how/network-database.html:668
 msgid ""
 "Implement an automatic subscription-based blacklist controlled by a "
 "single individual or group.\n"
@@ -15279,16 +10653,21 @@ msgid ""
 "block participation of any particular router or IP in the network,\n"
 "or even to completely shutdown or destroy the entire network."
 msgstr ""
+"Implementar una lista negra automática basada en suscripciones controlada"
+" por un único grupo individual. Esto esencialmente implementaría una "
+"parte del modelo de \"consenso\" de Tor. Desafortunadamente le daría a un"
+" solo grupo el poder de bloquear la participación de cualquier ruter o IP"
+" en la red, o incluso apagar o destruir la red entera."
 
-#: i2p2www/pages/site/docs/how/network-database.html:656
+#: i2p2www/pages/site/docs/how/network-database.html:677
 msgid "This attack becomes more difficult as the network size grows."
-msgstr ""
+msgstr "Este ataque se hace más difícil cuanto más grande es la red."
 
-#: i2p2www/pages/site/docs/how/network-database.html:662
+#: i2p2www/pages/site/docs/how/network-database.html:683
 msgid "Sybil Attack (Partial Keyspace)"
-msgstr ""
+msgstr "Ataque Sybil (espacio de claves parcial)"
 
-#: i2p2www/pages/site/docs/how/network-database.html:663
+#: i2p2www/pages/site/docs/how/network-database.html:684
 #, python-format
 msgid ""
 "An attacker may mount a Sybil attack\n"
@@ -15301,8 +10680,15 @@ msgid ""
 "If successful, this could be an effective DOS attack on a particular "
 "eepsite, for example."
 msgstr ""
+"Un atacante puede montar un ataque Sybil creando "
+"un pequeño número de ruters floodfill (8-15) cercanos en el espacio de "
+"claves, y distribuir los RouterInfos de esos ruters extensamente. "
+"Entonces, todas las búsquedas y almacenamientos de una clave en ese "
+"espacio de claves serán dirigidod a uno de los ruters del atacante. Si ha"
+" tenido éxito, esto podía provocar un ataque DOS efectivo sobre un "
+"eepsite en particular, por ejemplo."
 
-#: i2p2www/pages/site/docs/how/network-database.html:672
+#: i2p2www/pages/site/docs/how/network-database.html:693
 msgid ""
 "As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,"
 "\n"
@@ -15313,8 +10699,14 @@ msgid ""
 "on network\n"
 "size, is unknown."
 msgstr ""
+"Ya que el espacio de claves está indexado por el hash criptográfico "
+"(SHA256) de la clave, un atacante tiene que usar la fuerza bruta para "
+"generar repetidamente hashes de routers hasta que tenga suficientes que "
+"estén suficientemente cerca de la clave. La cantidad de potencia de "
+"cálculo requerida para esto, la cual depende del tamaño de la red, es "
+"desconocida. "
 
-#: i2p2www/pages/site/docs/how/network-database.html:680
+#: i2p2www/pages/site/docs/how/network-database.html:701
 msgid ""
 "As a partial defense against this attack,\n"
 "the algorithm used to determine Kademlia \"closeness\" varies over time.\n"
@@ -15330,8 +10722,17 @@ msgid ""
 "after the rotation, the attacking routers would no longer be close\n"
 "to the target key, or to each other."
 msgstr ""
+"Como una defensa parcial contra este ataque, el algoritmo usado para "
+"determinar la \"cercanía\" Kademlia varía con el tiempo. En vez de usar "
+"el hash de la clave (por ejemplo H(k)) para determinar la cercanía, "
+"usamos el Hash de la clave añadido a la cadena de datos actuales, por "
+"ejemplo H(k + YYYYMMDD). En otras palabras, el espacio de claves completo"
+" de la netdb \"rota\" cada día a la media noche UTC. Cualquier ataque "
+"parcial al espacio de claves tendría que regenerarse cada día, después de"
+" cada rotación los ruters atacantes no estarán ya cerca de la clave del "
+"objetivo."
 
-#: i2p2www/pages/site/docs/how/network-database.html:692
+#: i2p2www/pages/site/docs/how/network-database.html:713
 msgid ""
 "This attack becomes more difficult as the network size grows.\n"
 "However, recent research demonstrates that the keyspace rotation is not "
@@ -15340,9 +10741,14 @@ msgid ""
 "and only a few routers are sufficient to \"eclipse\" a portion\n"
 "of the keyspace within a half hour after rotation."
 msgstr ""
+"Este ataque se hace más difícil según crece la red. Aunque estudios "
+"recientes han demostrado que la rotación del espacio de claves no es "
+"particularmente efectiva. Un atacante podría pre-calcular numerosos "
+"hashes de ruters de antemano, y sólo son necesarios unos pocos ruters "
+"para \"eclipsar\" una parte del espacio de claves en sólo media hora "
+"después de la rotación."
 
-#: i2p2www/pages/site/docs/how/network-database.html:700
-#: i2p2www/pages/site/docs/how/network-database.html:709
+#: i2p2www/pages/site/docs/how/network-database.html:721
 msgid ""
 "One consequence of daily keyspace rotation is that the distributed "
 "network database\n"
@@ -15353,67 +10759,92 @@ msgid ""
 "(for example netdb \"handoffs\" at midnight)\n"
 "are a topic for further study."
 msgstr ""
+"Una de las consecuencias de la rotación diaria del espacio de claves es "
+"que la base de datos de la red distribuida se queda inaccesible durante "
+"unos minutos tras la rotación -- las búsquedas fallarán porque los nuevos"
+" ruters \"más cercanos\" no han recibido aún un almacenamiento. El "
+"alcance del problema, y los métodos para mitigarlo (por ejemplo con "
+"\"handoffs, manos fuera\" de la netdb a media noche) es un tema para "
+"futuros estudios."
 
-#: i2p2www/pages/site/docs/how/network-database.html:719
+#: i2p2www/pages/site/docs/how/network-database.html:731
 msgid "Bootstrap Attacks"
-msgstr ""
+msgstr "Ataques Bootstrap, de arranque"
 
-#: i2p2www/pages/site/docs/how/network-database.html:720
+#: i2p2www/pages/site/docs/how/network-database.html:732
 msgid ""
 "An attacker could attempt to boot new routers into an isolated\n"
 "or majority-controlled network by taking over a reseed website,\n"
 "or tricking the developers into adding his reseed website\n"
 "to the hardcoded list in the router."
 msgstr ""
+"Un atacante podría intentar arrancar nuevos ruters dentro de una red "
+"aislada o controlada en su mayoría por él tomando control de una web de "
+"resiembra, o engañando a los desarrolladores para que añadan su web de "
+"resembrado dentro del código del ruter."
 
-#: i2p2www/pages/site/docs/how/network-database.html:727
+#: i2p2www/pages/site/docs/how/network-database.html:739
 msgid "Several defenses are possible, and most of these are planned:"
-msgstr ""
+msgstr "Existen varias defensas posibles, y la mayoría ya están planeadas:"
 
-#: i2p2www/pages/site/docs/how/network-database.html:731
+#: i2p2www/pages/site/docs/how/network-database.html:743
 msgid ""
 "Disallow fallback from HTTPS to HTTP for reseeding.\n"
 "A MITM attacker could simply block HTTPS, then respond to the HTTP."
 msgstr ""
+"Desactivar el cambio de HTTPS a HTTP para el resembrado. Un atacante "
+"haciendo un MITM podría simplemente bloquear el HTTPS, y entonces "
+"responder al HTTP."
 
-#: i2p2www/pages/site/docs/how/network-database.html:735
+#: i2p2www/pages/site/docs/how/network-database.html:747
 msgid ""
 "Changing the reseed task to fetch a subset of RouterInfos from\n"
 "each of several reseed sites rather than using only a single site"
 msgstr ""
+"Cambiar la tarea de resembrado para obtener un subconjunto de RouterInfos"
+" desde varias webs de resiembra en vez de usar una única web."
 
-#: i2p2www/pages/site/docs/how/network-database.html:739
+#: i2p2www/pages/site/docs/how/network-database.html:751
 msgid ""
 "Creating an out-of-network reseed monitoring service that\n"
 "periodically polls reseed websites and verifies that the\n"
 "data are not stale or inconsistent with other views of the network"
 msgstr ""
+"Creando un servicio de monitoreo de resiembras fuera de la red, que "
+"periódicamente pregunte a las webs de resiembra y verifique que los datos"
+" no están corruptos o son inconsistentes con otras vistas de la red."
 
-#: i2p2www/pages/site/docs/how/network-database.html:744
+#: i2p2www/pages/site/docs/how/network-database.html:756
 msgid "Bundling reseed data in the installer"
-msgstr ""
+msgstr "Incluyendo los datos de resiembra en el instalador"
 
-#: i2p2www/pages/site/docs/how/network-database.html:747
+#: i2p2www/pages/site/docs/how/network-database.html:759
 msgid "Query Capture"
-msgstr ""
+msgstr "Captura de peticiones"
 
-#: i2p2www/pages/site/docs/how/network-database.html:748
+#: i2p2www/pages/site/docs/how/network-database.html:760
 #, python-format
 msgid ""
 "See also lookup\n"
 "(Reference: Hashing it out in Public Sections "
 "2.2-2.3 for terms below in italics)"
 msgstr ""
+"Vea también búsquedas (Referencia: Hashing it out in Public Secciones 2.2-2.3 para los "
+"términos en cursiva de abajo)"
 
-#: i2p2www/pages/site/docs/how/network-database.html:753
+#: i2p2www/pages/site/docs/how/network-database.html:765
 msgid ""
 "Similar to a bootstrap attack, an attacker using a floodfill router could"
 " attempt to \"steer\"\n"
 "peers to a subset of routers controlled by him by returning their "
 "references."
 msgstr ""
+"Similar a un ataque bootstrap, un atacante usando un ruter floodfill "
+"podría intentar \"dirigir\" a los pares a un subconjunto de ruters "
+"controlados por él devolviendo sus referencias."
 
-#: i2p2www/pages/site/docs/how/network-database.html:758
+#: i2p2www/pages/site/docs/how/network-database.html:770
 msgid ""
 "This is unlikely to work via exploration, because exploration is a low-"
 "frequency task.\n"
@@ -15422,8 +10853,14 @@ msgid ""
 "Exploration results are generally limited to a few router hashes,\n"
 "and each exploration query is directed to a random floodfill router."
 msgstr ""
+"Esto es raro que funcione vía exploración, porque la exploración es una "
+"tarea de baja frecuencia. Los ruters obtienen la mayoría de sus "
+"referencias sobre los pares cuando crean los túneles normales. Los "
+"resultados de exploración están generalmente limitados a unos pocos "
+"hashes de ruters, y cada petición de exploración es dirigida a un ruter "
+"floodfill aleatorio. "
 
-#: i2p2www/pages/site/docs/how/network-database.html:765
+#: i2p2www/pages/site/docs/how/network-database.html:777
 #, python-format
 msgid ""
 "As of release 0.8.9, iterative lookups are implemented.\n"
@@ -15447,36 +10884,58 @@ msgid ""
 "Hashing it out in Public\n"
 "is much more difficult."
 msgstr ""
+"A partir de la versión 0.8.9, se han implementado las búsquedas "
+"iterativas. Las referencias de los ruters floodfill devueltas en una "
+"respuesta de búsqueda I2NP "
+"DatabaseSearchReplyMessage, son seguidas si están más cerca (o la "
+"siguiente más cerca) a la clave de búsqueda. El ruter que hace la "
+"petición no confía en que las referencias estén más cerca a la clave (por"
+" ejemplo, son verificablemente correctas). Además la búsqueda no "
+"termina cuando la clave más cercana es encontrada, continúa haciendo "
+"peticiones al siguiente nodo más cercano, hasta que termine su tiempo o "
+"el número de peticiones. Esto previene que un floodfill malicioso haga un"
+" 'agujero negro' a una parte del espacio de claves. Además, la rotación "
+"diaria del espacio de claves requiere que el atacante regenere la "
+"información de un ruter dentro de la región del espacio de claves "
+"deseada. Este diseño asegura que el ataque de captura de peticiones "
+"descrito en Hashing it out in Public sea mucho "
+"más difícil."
 
-#: i2p2www/pages/site/docs/how/network-database.html:784
+#: i2p2www/pages/site/docs/how/network-database.html:796
 msgid "DHT-Based Relay Selection"
-msgstr ""
+msgstr "Selección del Relay basado en DHT"
 
-#: i2p2www/pages/site/docs/how/network-database.html:785
+#: i2p2www/pages/site/docs/how/network-database.html:797
 #, python-format
 msgid "(Reference: Hashing it out in Public Section 3)"
-msgstr ""
+msgstr "(Referencia: Hashing it out in Public Sección 3)"
 
-#: i2p2www/pages/site/docs/how/network-database.html:789
+#: i2p2www/pages/site/docs/how/network-database.html:801
 #, python-format
 msgid ""
 "This doesn't have much to do with floodfill, but see\n"
 "the peer selection page\n"
 "for a discussion of the vulnerabilities of peer selection for tunnels."
 msgstr ""
+"Esto no tiene mucho que ver con los floodfill, pero vea la página de selección de pares para ver una "
+"discusión de las vulnerabilidades de la selección de los pares para los "
+"túneles."
 
-#: i2p2www/pages/site/docs/how/network-database.html:795
+#: i2p2www/pages/site/docs/how/network-database.html:807
 msgid "Information Leaks"
-msgstr ""
+msgstr "Fugas de información"
 
-#: i2p2www/pages/site/docs/how/network-database.html:796
+#: i2p2www/pages/site/docs/how/network-database.html:808
 #, python-format
 msgid ""
 "(Reference: In Search of an Anonymous and Secure "
 "Lookup Section 3)"
 msgstr ""
+"(Referencia: In Search of an Anonymous and Secure "
+"Lookup Sección 3)"
 
-#: i2p2www/pages/site/docs/how/network-database.html:800
+#: i2p2www/pages/site/docs/how/network-database.html:812
 #, python-format
 msgid ""
 "This paper addresses weaknesses in the \"Finger Table\" DHT lookups used "
@@ -15492,8 +10951,17 @@ msgid ""
 "are used for tunnels.\n"
 "Also, peer selection is unrelated to any notion of DHT key-closeness."
 msgstr ""
+"Este estudio soluciona la debilidad en las búsquedas DHT \"Finger Table\""
+" usadas por Torks y NISAN. A primera vista, estos parecen que no se "
+"apliquen a I2P. Primero, el uso que hacen Torks y NISAN del DHT es "
+"bastante diferente que su uso en I2P. Segundo, las búsquedas en la base "
+"de datos de red de I2P sólo están un poco relacionadas con los procesos "
+"de selección de pares y de construcción de túneles; sólo los pares "
+"previamente conocidos son usados para los túneles. Además, la selección "
+"de pares no tiene relación con la noción de cercanía de claves DHT."
 
-#: i2p2www/pages/site/docs/how/network-database.html:811
+#: i2p2www/pages/site/docs/how/network-database.html:823
 msgid ""
 "Some of this may actually be more interesting when the I2P network gets "
 "much larger.\n"
@@ -15506,15 +10974,21 @@ msgid ""
 "more correlative. Of course, a larger network makes a Sybil attack that "
 "much harder."
 msgstr ""
+"Algunos de estos serán más interesantes cuando la red I2P sea mucho más "
+"grande. Ahora mismo, cada ruter conoce una gran porción de la red, con lo"
+" que mirando por un RouterInfo en particular en la base de datos de la "
+"red no indica que ese ruter se vaya a usar en un túnel. Quizás cuando la "
+"red sea 100 veces más grande, la búsqueda sea correlativa. Por supuesto, "
+"una red más grande hace que un ataque Sybil sea mucho más difícil."
 
-#: i2p2www/pages/site/docs/how/network-database.html:819
+#: i2p2www/pages/site/docs/how/network-database.html:831
 #, python-format
 msgid ""
 "However, the general issue of DHT information leakage in I2P needs "
 "further investigation.\n"
 "The floodfill routers are in a position to observe queries and gather "
 "information.\n"
-"Certainly, at a level of f = 0.2 (20%% malicious nodes, as "
+"Certainly, at a level of f = 0.2 (20% malicious nodes, as "
 "specifed in the paper)\n"
 "we expect that many of the Sybil threats we describe\n"
 "(here,\n"
@@ -15522,22 +10996,37 @@ msgid ""
 "here)\n"
 "become problematic for several reasons."
 msgstr ""
+"Sin embargo, el problema general de la filtración de información DHT "
+"(tabla \n"
+"de identificadores criptográficos (hash) dinámica) en I2P necesita "
+"posterior \n"
+"investigación. Los routers de inundacion (`floodfill`) están en posición "
+"de \n"
+"observar peticiones y reunir información. Ciertamente, a un nivel de \n"
+"f = 0.2 (20% nodos maliciosos, tal como detalla la "
+"especificación) \n"
+"esperamos que muchas de las amenazas Sybil que describimos  (aquí, \n"
+"aquí y aquí) se "
+"volverán problemáticas por varios motivos."
 
-#: i2p2www/pages/site/docs/how/network-database.html:833
+#: i2p2www/pages/site/docs/how/network-database.html:845
 msgid "Moved to the netdb discussion page"
-msgstr ""
+msgstr "Movido a la página de discusión de la netdb"
 
-#: i2p2www/pages/site/docs/how/network-database.html:837
+#: i2p2www/pages/site/docs/how/network-database.html:849
 msgid "End-to-end encryption of additional netDb lookups and responses."
 msgstr ""
+"Cifrado de fin a fin de las búsquedas y respuestas adicionales en la "
+"netDb."
 
-#: i2p2www/pages/site/docs/how/network-database.html:841
+#: i2p2www/pages/site/docs/how/network-database.html:853
 msgid "Better methods for tracking lookup responses."
-msgstr ""
+msgstr "Mejores métodos de seguimiento de las respuestas de las búsquedas."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:2
 msgid "Peer Profiling and Selection"
-msgstr ""
+msgstr "Perfilado y selección de pares"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:3
 msgid "July 2010"
@@ -15545,7 +11034,7 @@ msgstr "Julio de 2010"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:8
 msgid "Peer Profiling"
-msgstr ""
+msgstr "Perfiles de los pares"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:10
 #, python-format
@@ -15557,14 +11046,21 @@ msgid ""
 "the peer itself\n"
 "in the network database."
 msgstr ""
+"La creación de perfiles de los pares, profiling es el proceso de "
+"recolectar datos basados en el rendimiento observado de otros "
+"ruters o pares. La creación de estos perfiles no usa los datos de "
+"rendimiento publicados por el par mismo en la base "
+"de datos de la red."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:17
 msgid "Profiles are used for two purposes:"
-msgstr ""
+msgstr "Los perfiles se usan con dos fines:"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:19
 msgid "Selecting peers to relay our traffic through, which is discussed below"
 msgstr ""
+"Para seleccionar pares para enviar nuestro tráfico a través, lo que se "
+"discute más abajo."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:20
 #, python-format
@@ -15573,12 +11069,16 @@ msgid ""
 "database storage and queries,\n"
 "which is discussed on the network database page"
 msgstr ""
+"Para elegir pares de un conjunto de ruters floodfill para usar los "
+"servicios de almacenamiento y consultas de la base de datos de la red, lo"
+" que se discute en la página de la base de datos de"
+" la red"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:27
 #: i2p2www/pages/site/docs/how/peer-selection.html:187
 #: i2p2www/pages/site/docs/tunnels/implementation.html:286
 msgid "Peer Selection"
-msgstr ""
+msgstr "Selección de pares"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:28
 msgid ""
@@ -15592,6 +11092,14 @@ msgid ""
 "whether they seem to be overloaded or otherwise unable to perform what\n"
 "they agree to reliably."
 msgstr ""
+"La selección de pares es el proceso de escoger qué ruters de la "
+"red queremos para pasar nuestros mensajes a través (o a cuales pares les "
+"pedimos permiso para unir nuestros túneles). Para llevar esto acabo, "
+"llevamos el seguimiento de como funciona cada par (el \"perfil\" del par)"
+" y usamos estos datos para estimar cómo son de rápidos, cuando serán "
+"capaces de aceptar nuestras peticiones y de saber cuando están "
+"sobrecargados o cuando no son capaces de hacer con fiabilidad lo que "
+"acordaron."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:38
 #, python-format
@@ -15607,6 +11115,13 @@ msgid ""
 "timing attacks\n"
 "more difficult."
 msgstr ""
+"A diferencia de otras redes anónimas, en I2P el ancho de banda indicado "
+"no es de fiar y es sólo usado para evitar que esos pares anuncien "
+"anchos de banda insuficientes para rutar los túneles. Toda la selección "
+"de los pares se hace a través de lso perfiles. Esto evita ataques simples"
+" basados en pares que indican un gran ancho de banda para intentar "
+"capturar un gran número de túneles. También hace más difíciles los ataques de sincronización."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:50
 msgid ""
@@ -15615,6 +11130,9 @@ msgid ""
 "of client and exploratory tunnels, and a tunnel lifetime is only 10 "
 "minutes."
 msgstr ""
+"La selección de pares se hace frecuentemente, ya que el ruter mantiene un"
+" gran número de túneles clientes y exploratorios, y la vida de un túnel "
+"es de sólo 10 minutos."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:56
 msgid "Further Information"
@@ -15630,6 +11148,11 @@ msgid ""
 "See below for notes on minor changes since the "
 "paper was published."
 msgstr ""
+"Para más información vea el artículo Peer Profiling "
+"and Selection in the I2P Anonymous Network presentado en el PET-CON 2009.1. Mire más "
+"abajo para ver los cambios menores o las notas desde que el artículo "
+"fue publicado."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:65
 msgid "Profiles"
@@ -15650,6 +11173,13 @@ msgid ""
 "gathered\n"
 "can be found in the code."
 msgstr ""
+"Cada par tiene un conjunto de datos recogidos sobre ellos, incluyendo "
+"estadísticas sobre cuánto tardan en responder a una petición a la base de"
+" datos de la red, con qué frecuencia fallan sus túneles, y cuántos nuevos"
+" pares son capaces de presentarnos, y también datos simples como cuándo "
+"supimos de ellos por última vez o cuándo fue el uĺtimo error de "
+"comunicación. Los datos obtenidos específicos pueden encontrarse en el código."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:75
 msgid ""
@@ -15663,10 +11193,17 @@ msgid ""
 "thus allowing a router to quickly re-integrate into the network after "
 "startup."
 msgstr ""
+"Los perfiles son bastante pequeños, unos pocos KB. Para controlar el uso "
+"de la memoria usada, el tiempo de expiración de los perfiles disminuye "
+"cuando el número de perfiles aumenta. Los perfiles se mantienen en la "
+"memoria hasta que el ruter se apaga, entonces se escriben al disco duro. "
+"Al inicio, los perfiles son leídos para que el ruter no necesite "
+"reiniciar todos los perfiles, permitiendo al ruter integrarse rápidamente"
+" en la red después del arranque."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:85
 msgid "Peer Summaries"
-msgstr ""
+msgstr "Resúmenes de los pares"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:86
 msgid ""
@@ -15677,6 +11214,11 @@ msgid ""
 " well \n"
 "integrated into the network it is, and whether it is failing."
 msgstr ""
+"Aunque los perfiles por sí mismos puede considerarse un resumen del "
+"rendimiento de los pares, para tener una selección efectiva de los pares "
+"partimos cada resumen en cuatro valores simples, indicando la velocidad "
+"del par, su capacidad, cómo de bien está integrado en la red y cuándo "
+"fallan."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:93
 msgid "Speed"
@@ -15690,6 +11232,10 @@ msgid ""
 "this estimate it just looks at\n"
 "performance in the previous minute."
 msgstr ""
+"El cálculo de la velocidad se hace simplemente mirando el perfil y "
+"calculando cuantos datos podemos enviar o recibir a través de túnel de un"
+" par durante un minuto. Para esta estimación simplemente mira el "
+"rendimiento en el minuto anterior."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:101
 msgid "Capacity"
@@ -15708,6 +11254,13 @@ msgid ""
 "more than later activity,\n"
 "statistics up to 48 hours old may be included."
 msgstr ""
+"El cálculo de la capacidad simplemente mira en el perfil y estima el "
+"número de túneles en los que aceptará participar en un periodo de tiempo "
+"dado. Para esta estimación mira cuantos peticiones de construcción de "
+"túneles ha aceptado, denegado y tirado, y cuantos túneles de los "
+"aceptados han fallado después. Las actividades recientes importan más que"
+" las demás, pueden ser incluidas hasta estadísticas de hasta 48 horas de "
+"viejas."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:113
 msgid ""
@@ -15721,10 +11274,17 @@ msgid ""
 "peers, and uses that probability in the capacity calculation.\n"
 "Drops and test failures are weighted much higher than rejections."
 msgstr ""
+"Reconocer y evitar los pares no fiables e inalcanzables es de importancia"
+" crítica. Desafortunadamente, ya que la creación de los túneles requiere "
+"la participación de varios pares, es difícil identificar positivamente la"
+" causa de una petición caída o un fallo en la prueba. El ruter asigna una"
+" probabilidad de fallo a cada par, y usa esa probabilidad en el cálculo "
+"de la capacidad. Las caídas y los fallos de prueba pesan mucho más que "
+"las denegaciones."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:123
 msgid "Peer organization"
-msgstr ""
+msgstr "Organización de los pares"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:124
 msgid ""
@@ -15734,10 +11294,13 @@ msgid ""
 "three\n"
 "groups - fast, high capacity, and standard."
 msgstr ""
+"Como se ha mencionado arriba, nos sumergimos en el perfil de cada par "
+"para hacer unos pocos cálculos, y basado en esos cálculos, organizamos "
+"cada par dentro de estos tres grupos - rápido, con capacidad y estándar."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:130
 msgid "The groupings are not mutually exclusive, nor are they unrelated:"
-msgstr ""
+msgstr "Los grupos no se excluyen mutuamente, y están relacionados entre ellos:"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:134
 msgid ""
@@ -15745,6 +11308,8 @@ msgid ""
 "or \n"
 "exceeds the median of all peers."
 msgstr ""
+"Un par es considerado de \"alta capacidad\" si los cálculos cumplen o "
+"exceden la media de todos los pares."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:138
 msgid ""
@@ -15752,10 +11317,12 @@ msgid ""
 "their \n"
 "speed calculation meets or exceeds the median of all peers."
 msgstr ""
+"Un par es considerado \"rápido\" si ya es de \"alta capacidad\", y  los "
+"cálculos de velocidad cumplen o exceden la media de todos los pares."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:142
 msgid "A peer is considered \"standard\" if it is not \"high capacity\""
-msgstr ""
+msgstr "Un par es considerado \"estándar/normal\" si no es de \"alta capacidad\""
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:145
 #, python-format
@@ -15763,14 +11330,16 @@ msgid ""
 "These groupings are implemented in the router's\n"
 "ProfileOrganizer."
 msgstr ""
+"Estas agrupaciones están implementadas en el ProfileOrganizer del ruter."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:150
 msgid "Group size limits"
-msgstr ""
+msgstr "Límites del tamaño de los grupos"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:151
 msgid "The size of the groups may be limited."
-msgstr ""
+msgstr "El tamaño de los grupos puede estar limitado."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:156
 msgid ""
@@ -15778,6 +11347,8 @@ msgid ""
 "If there would be more, only the ones with the highest speed rating are "
 "placed in the group."
 msgstr ""
+"El grupo rápido está limitado a 30 pares. Si hubiese más, sólo los que "
+"tuviesen las mayores velocidades permanecerían en el grupo."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:160
 msgid ""
@@ -15786,6 +11357,9 @@ msgid ""
 "If there would be more, only the ones with the highest capacity rating "
 "are placed in the group."
 msgstr ""
+"El grupo de alta capacidad está limitado a 75 pares (incluido el grupo "
+"rápido). Si hubiese más, sólo los que tuviesen las mayores capacidades "
+"permanecerían en el grupo."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:164
 msgid ""
@@ -15796,16 +11370,23 @@ msgid ""
 "RouterInfos and 500 peer profiles\n"
 "(including those in the fast and high capacity groups)"
 msgstr ""
+"El grupo estándar no tiene un límite fijado, pero de alguna forma es "
+"menor que el número de RouterInfos almacenados en la base de datos de la "
+"red local. En un ruter activo de la red actual, puede haber como 1000 "
+"RouterInfoes y 500 perfiles de pares (incluyendo auqellos en los grupos "
+"rápidos y de alta capacidad)"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:172
 msgid "Recalculation and Stability"
-msgstr ""
+msgstr "Nuevos cálculos y estabilidad"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:173
 msgid ""
 "Summaries are recalculated, and peers are resorted into groups, every 45 "
 "seconds."
 msgstr ""
+"Cada 45 segundos, los resúmenes son re-calculados, y los pares son "
+"recolocados en grupos. "
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:177
 msgid ""
@@ -15816,20 +11397,26 @@ msgid ""
 " them, which increases their speed and capacity ratings,\n"
 "which reinforces their presence in the group."
 msgstr ""
+"Los grupos tienden a ser bastante estables, esto es, no hay mucha "
+"\"agitación\" en las clasificaciones tras cada nuevo cálculo."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:188
 msgid "The router selects peers from the above groups to build tunnels through."
 msgstr ""
+"Los ruters seleccionan pares de los grupos anteriores para construir "
+"túneles a través de ellos."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:193
 msgid "Peer Selection for Client Tunnels"
-msgstr ""
+msgstr "Selección de pares para los túneles cliente"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:194
 msgid ""
 "Client tunnels are used for application traffic, such as for HTTP proxies"
 " and web servers."
 msgstr ""
+"Los túneles cliente se usan para el tráfico de las aplicaciones, como los"
+" proxies HTTP y los servidores web."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:198
 msgid ""
@@ -15841,10 +11428,16 @@ msgid ""
 "There is no bias toward selecting peers that were previously participants"
 " in a tunnel for the same client."
 msgstr ""
+"Para reducir la propensión a algunos ataques, e incrementar el rendimiento, los"
+" pares para la construcción de los túneles cliente se eligen "
+"aleatoriamente del grupo más pequeño, el cual es el grupo \"rápido\". No "
+"existe una tendencia hacia la selección de pares que anteriormente hayan "
+"participado en un túnel para el mismo cliente."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:206
 msgid "Peer Selection for Exploratory Tunnels"
-msgstr ""
+msgstr "Selección de pares para los túneles exploratorios"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:207
 msgid ""
@@ -15856,6 +11449,11 @@ msgid ""
 "they are called \"exploratory\".\n"
 "These tunnels are usually low-bandwidth."
 msgstr ""
+"Los túneles exploratorios son usados para propósitos administrativos del "
+"ruter, como el tráfico de la base de datos de la red y los túneles "
+"cliente de prueba. También son usados para contactar con ruters "
+"anteriormente no contactados, que es por lo que se llaman "
+"\"exploratorios\". Estos túneles son normalmente de bajo ancho de banda."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:215
 msgid ""
@@ -15870,6 +11468,11 @@ msgid ""
 "There is no bias toward selecting peers that were previously participants"
 " in an exploratory tunnel."
 msgstr ""
+"Los pares para construir los túneles exploratorios son elegidos "
+"normalmente aleatoriamente del grupo estándar. En su lugar, si la tasa de"
+" éxito de esos intentos de construcción es baja comparada con la tasa de "
+"éxito exitosa de construcción, el ruter seleccionará un promedio "
+"balanceado aleatoriamente de pares del grupo de alta capacidad."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:223
 msgid ""
@@ -15879,6 +11482,10 @@ msgid ""
 "all peers,\n"
 "until the build success rate becomes too low."
 msgstr ""
+"Ya que el grupo estándar incluye una gran parte de todos los pares que el"
+" ruter conoce, los túneles exploratorios son construidos esencialmente a "
+"través de una selección aleatoria de todos los pares, hasta que la tasa "
+"de éxito de construcción sea demasiada baja."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:231
 msgid "Restrictions"
@@ -15889,29 +11496,34 @@ msgid ""
 "To prevent some simple attacks, and for performance, there are the "
 "following restrictions:"
 msgstr ""
+"Para prevenir algunos ataques simples, y para mejorar el rendimiento, "
+"existen las siguientes restricciones:"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:236
 msgid "Two peers from the same /16 IP space may not be in the same tunnel."
-msgstr ""
+msgstr "Dos pares en el mismo espacio de IPs /16 no deben estar en el mismo túnel."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:239
-#, python-format
 msgid ""
-"A peer may participate in a maximum of 33% of all tunnels created by the "
-"router."
+"A peer may participate in a maximum of 33% of all tunnels created by "
+"the router."
 msgstr ""
+"Un par (`peer`) puede participar en un máximo de 33% \n"
+"de todos los túneles creados por el router."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:242
 msgid "Peers with extremely low bandwidth are not used."
-msgstr ""
+msgstr "Los pares con el ancho de banda extremadamente bajo no son usados."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:245
 msgid "Peers for which a recent connection attempt failed are not used."
 msgstr ""
+"Los pares para los que un intento de conexión reciente ha fallado no son "
+"usados."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:252
 msgid "Peer Ordering in Tunnels"
-msgstr ""
+msgstr "Orden de los pares en los túneles"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:253
 #, python-format
@@ -15922,24 +11534,32 @@ msgid ""
 "More information is on the tunnel "
 "page."
 msgstr ""
+"Los pares son ordenados dentro de los túneles para hacer frente al ataque del predecesor (actualización del 2008). Hay más información en"
+" la página del túnel."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:268
 msgid "Continue to analyze an tune speed and capacity calculations as necessary"
 msgstr ""
+"Continuar analizando y afinando los cálculos de capacidad y velocidad "
+"según las necesidades."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:271
 msgid ""
 "Implement a more aggressive ejection strategy if necessary to control "
 "memory usage as the network grows"
 msgstr ""
+"Implementar una estrategia de expulsión más agresiva si se necesita para "
+"controlar el uso de memoria según crezca la red."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:274
 msgid "Evaluate group size limits"
-msgstr ""
+msgstr "Evaluar el tamaño de los límites de los grupos"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:277
 msgid "Use GeoIP data to include or exclude certain peers, if configured"
-msgstr ""
+msgstr "Usar datos GeoIP para incluir o excluir ciertos pares, si se configura"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:283
 #, python-format
@@ -15950,42 +11570,46 @@ msgid ""
 "please keep in mind the following minor changes in I2P since the paper's "
 "publication:"
 msgstr ""
+"Para aquellos leyendo el estudio Peer Profiling and "
+"Selection in the I2P Anonymous Network, por favor, tengan en cuenta "
+"los siguientes cambios menores en I2P desde la publicación de dicho "
+"estudio."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:289
 msgid "The Integration calculation is still not used"
-msgstr ""
+msgstr "Todavía no se usa el cálculo de integración"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:290
 msgid "In the paper, \"groups\" are called \"tiers\""
-msgstr ""
+msgstr "En el estudio, a los \"grupos\" se les llama \"tiers\"/\"niveles\""
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:291
 msgid "The \"Failing\" tier is no longer used"
-msgstr ""
+msgstr "El nivel \"Fallando\" no se usa más."
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:292
 msgid "The \"Not Failing\" tier is now named \"Standard\""
-msgstr ""
+msgstr "El nivel \"no fallando\" se llama ahora \"estándar\""
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:301
 msgid "One Cell Enough"
-msgstr ""
+msgstr "Una célula basta"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:303
 msgid "Tor Entry Guards"
-msgstr ""
+msgstr "Entry Guards de Tor"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:305
 msgid "Murdoch 2007 Paper"
-msgstr ""
+msgstr "Estudio Murdoch 2007"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:307
 msgid "Tune-up for Tor"
-msgstr ""
+msgstr "Ajustes para Tor"
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:309
 msgid "Low-resource Routing Attacks Against Tor"
-msgstr ""
+msgstr "Ataques de enrutado de bajo recurso contra Tor"
 
 #: i2p2www/pages/site/docs/how/tech-intro.html:2
 msgid "Introducing I2P"
@@ -16001,7 +11625,7 @@ msgstr "Tabla de contenidos"
 
 #: i2p2www/pages/site/docs/how/tech-intro.html:9
 #: i2p2www/pages/site/docs/how/tech-intro.html:24
-#: i2p2www/pages/site/docs/transport/ssu.html:278
+#: i2p2www/pages/site/docs/transport/ssu.html:281
 msgid "Introduction"
 msgstr "Introducción"
 
@@ -16014,6 +11638,11 @@ msgstr "Como funciona I2P"
 msgid "Transport protocols"
 msgstr "Protocolos de transporte"
 
+#: i2p2www/pages/site/docs/how/tech-intro.html:17
+#: i2p2www/pages/site/docs/how/tech-intro.html:458
+msgid "Cryptography"
+msgstr "Cifrado"
+
 #: i2p2www/pages/site/docs/how/tech-intro.html:25
 msgid ""
 "I2P is a scalable, self organizing, resilient packet switched anonymous \n"
@@ -16204,7 +11833,7 @@ msgstr ""
 "el mundo. Todo el trabajo realizado es software libre y disponible "
 "gratuitamente en la web. La mayoría del código "
 "es de dominio público, excepto algunas rutinas de cifrado que usan "
-"licencias del estilo BSD. La gente trabajando en I2P no controla bajo que"
+"licencias del estilo BSD. La gente trabajando en I2P no controla bajo qué"
 " licencias libera la gente sus aplicaciones clientes, y hay varias "
 "aplicaciones GPL disponibles (I2PTunnel, "
 "susimail, cifrado garlic \" permite al ruter de Alice "
+"href=\"#op.garlic\">cifrado garlic\" permite al ruter de Alice "
 "envolver varios mensajes en un simple \"mensaje garlic\", cifrado para "
 "una calve pública en particular y así los pares intermediarios no pueden "
 "determinar cuantos mensajes hay dentro del mensaje garlic, que dicen esos"
@@ -16578,8 +12207,8 @@ msgstr ""
 "diferencia surge en lo que hace el creador del túnel - para los túneles "
 "de entrada, el creador es el punto final y simplemente descifra todas las"
 " capas añadidas, mientras que para los túneles de salida, el creador es "
-"la puerta de salida y pre descifran todas las capas con lo que después de"
-" que todos las capas de cifrado por salto son añadidas, el mensaje llega "
+"la puerta de salida y pre descifra todas las capas con lo que después de "
+"que todos las capas de cifrado por salto son añadidas, el mensaje llega "
 "en claro al túnel de punto final."
 
 #: i2p2www/pages/site/docs/how/tech-intro.html:244
@@ -16604,18 +12233,18 @@ msgid ""
 "information \n"
 "has its own serious anonymity implications."
 msgstr ""
-"La elección del cada par al pasar un mensaje al igual que su orden es "
-"importante para entender el anonimato y el rendimiento de I2P. Mientras "
-"que la base de datos de la red (debajo) tiene su propio criterio al "
-"elegir en qué pares consultar y almacenar entradas, los creadores de los "
-"túneles pueden usar cualquier par en la red y en cualquier orden (e "
-"incluso cualquier número de veces) en un solo túnel. Si se conocen "
-"globalmente  la latencia exacta y capacidad de datos, la selección del "
-"orden vendrá dada por las necesidades particulares del cliente y su "
-"modelo de seguridad. Desafortunadamente, no es trivial obtener "
-"anónimamente la latencia y la capacidad de datos, y al dependerse de "
-"pares no confiables para obtener esta información crea serios problemas "
-"en el anonimato."
+"La elección de los pares específicos par pasar los mensajes al igual que "
+"su orden es importante para entender el anonimato y el rendimiento de "
+"I2P. Mientras que la base de datos de la red (debajo) tiene su propio "
+"criterio al elegir en qué pares consultar y almacenar entradas, los "
+"creadores de los túneles pueden usar cualquier par en la red y en "
+"cualquier orden (e incluso cualquier número de veces) en un solo túnel. "
+"Si se conocen globalmente  la latencia exacta y capacidad de datos, la "
+"selección del orden vendrá dada por las necesidades particulares del "
+"cliente y su modelo de seguridad. Desafortunadamente, no es trivial "
+"obtener anónimamente la latencia y la capacidad de datos, y al dependerse"
+" de pares no confiables para obtener esta información crea serios "
+"problemas en el anonimato."
 
 #: i2p2www/pages/site/docs/how/tech-intro.html:257
 msgid ""
@@ -16901,7 +12530,7 @@ msgid ""
 msgstr ""
 "Toda esta información es firmada par la parte publicadora y verificada "
 "por cualquier ruter I2P que use o almacene la información. Además, los "
-"datos contienen información de la fecha para evitar el almacenamiento de "
+"datos contienen información de la hora para evitar el almacenamiento de "
 "entradas antiguas y posibles ataques. Esto es por que I2P empaqueta el "
 "código necesario para mantener la fecha correcta, a veces consultando "
 "algunos servidores SNTP (por defecto I2Pmail's ( que realmente "
-"sólo son simples instancias \"servidores\" apuntando a servidores POP3 y "
+"POP3 y SMTP de I2Pmail ( que realmente sólo "
+"son simples instancias \"servidores\" apuntando a servidores POP3 y "
 "SMTP), también hay túneles apuntando al servidor CVS de I2P, permitiendo "
 "el desarrollo anónimo. Incluso a veces hay gente que ha ejecutado proxies"
 " \"clientes\" para acceder instancias de \"servidores\" apuntando a "
@@ -18417,12 +14051,10 @@ msgstr ""
 #, python-format
 msgid ""
 "PyBit is a Bittorrent client written in Python.\n"
-"It is hosted on http://%(pebcache)s/"
-" "
+"It is hosted on %(pybit)s "
 msgstr ""
-"PyBit es un cliente Bittorrent escrito en python. Se aloja en http://%(pebcache)s/ "
+"PyBit es un cliente Bittorrent escrito en Python. Está hospedado en %(pybit)s "
 
 #: i2p2www/pages/site/docs/how/tech-intro.html:1015
 msgid ""
@@ -18537,7 +14169,7 @@ msgstr ""
 "I2P-Messenger es un aplicación de comunicación cifrada de fin a fin. Para"
 " la comunicación entre 2 usuarios sólo necesitan compartir entre ellos "
 "las claves de destino. Soporta transferencia de archivos y búsqueda de "
-"otros usuarios, basada en Seedlees."
+"otros usuarios, basado en Seedlees."
 
 #: i2p2www/pages/site/docs/how/threat-model.html:2
 msgid "I2P's Threat Model"
@@ -18547,11 +14179,52 @@ msgstr "Modelos de riesgo en I2P"
 msgid "November 2010"
 msgstr "Noviembre 2010"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:6
+#: i2p2www/pages/site/docs/how/threat-model.html:7
+msgid "low"
+msgstr "bajo"
+
+#: i2p2www/pages/site/docs/how/threat-model.html:8
+msgid "medium"
+msgstr "medio"
+
+#: i2p2www/pages/site/docs/how/threat-model.html:9
+msgid "high"
+msgstr "alto"
+
+#: i2p2www/pages/site/docs/how/threat-model.html:34
+msgid "Damage Potential"
+msgstr "Posibles daños"
+
+#: i2p2www/pages/site/docs/how/threat-model.html:35
+msgid "Reliability"
+msgstr "Confiabilidad"
+
+#: i2p2www/pages/site/docs/how/threat-model.html:36
+msgid "Exploitability"
+msgstr "Explotabilidad"
+
+#: i2p2www/pages/site/docs/how/threat-model.html:37
+msgid "Affected Users"
+msgstr "Usuarios afectados"
+
+#: i2p2www/pages/site/docs/how/threat-model.html:38
+msgid "Discoverability"
+msgstr "Detección"
+
+#: i2p2www/pages/site/docs/how/threat-model.html:39
+msgid "Severity"
+msgstr "Severidad"
+
+#: i2p2www/pages/site/docs/how/threat-model.html:40
+#: i2p2www/pages/site/docs/protocol/i2np.html:94
+msgid "Priority"
+msgstr "Prioridad"
+
+#: i2p2www/pages/site/docs/how/threat-model.html:45
 msgid "What do we mean by \"anonymous\"?"
 msgstr "¿Qué quiere decir con \"anónimo\"?"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:8
+#: i2p2www/pages/site/docs/how/threat-model.html:47
 msgid ""
 "Your level of anonymity can be described as \"how hard it is for someone\n"
 "to find out information you don't want them to know?\" - who you are, "
@@ -18579,7 +14252,7 @@ msgstr ""
 "webs, o para aquellos que intercambian información, hasta aquellos con "
 "miedo de ser descubiertos por organizaciones poderosas o estados."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:19
+#: i2p2www/pages/site/docs/how/threat-model.html:58
 msgid ""
 "The question of whether I2P provides sufficient anonymity for your \n"
 "particular needs is a hard one, but this page will hopefully assist in \n"
@@ -18592,7 +14265,7 @@ msgstr ""
 "pregunta explorando como I2P opera ante varios atauqes y así puede "
 "decidir si se amolda a sus necesidades."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:26
+#: i2p2www/pages/site/docs/how/threat-model.html:65
 msgid ""
 "We welcome further research and analysis on I2P's resistance to the "
 "threats described below.\n"
@@ -18605,11 +14278,11 @@ msgstr ""
 " los textos ya existentes (la mayoría sobre Tor) y trabajos originales "
 "sobre I2P."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:32
+#: i2p2www/pages/site/docs/how/threat-model.html:71
 msgid "Network Topology Summary"
 msgstr "Sumario de la topología de la red"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:33
+#: i2p2www/pages/site/docs/how/threat-model.html:72
 #, python-format
 msgid ""
 "I2P builds off the ideas of many other \n"
@@ -18622,7 +14295,7 @@ msgstr ""
 "sistemas, pero a la hora de revisar la "
 "información hay que tener en cuenta varios puntos:"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:39
+#: i2p2www/pages/site/docs/how/threat-model.html:78
 msgid ""
 "I2P is a free route mixnet - the message creator explicitly "
 "defines the\n"
@@ -18637,7 +14310,7 @@ msgstr ""
 "salida), y el receptor del mensaje define explícitamente el camino por el"
 " cual serán recibidos los mensajes (el túnel de entrada)."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:45
+#: i2p2www/pages/site/docs/how/threat-model.html:84
 msgid ""
 "I2P has no official entry and exit points - all peers fully "
 "participate in the \n"
@@ -18649,7 +14322,7 @@ msgstr ""
 "o salida en la capa de red (aún así existen varios proxies de salida en "
 "la capa de aplicación)"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:50
+#: i2p2www/pages/site/docs/how/threat-model.html:89
 msgid ""
 "I2P is fully distributed - there are no central controls or "
 "authorities.\n"
@@ -18671,7 +14344,7 @@ msgstr ""
 "la red, pero por supuesto no es necesario hacer nada de esto (y además "
 "podría poner en peligro su anonimato)."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:60
+#: i2p2www/pages/site/docs/how/threat-model.html:99
 #, python-format
 msgid ""
 "We have documented plans to implement [Onion Routing],\n"
 "[Freenet], and\n"
-"[Tor].\n"
+"[Tor].\n"
 "Our design benefits substantially from the research published around that"
 " time.\n"
 "I2P uses several onion routing techniques, so we continue to benefit\n"
 "from the significant academic interest in Tor."
 msgstr ""
-"El diseño de I2P empezó en 2003, no mucho más tarde de la llegada de [Onion Routing], [Freenet], y [Tor]. Nuestro diseño se "
-"beneficia notablemente de los estudios publicados en esa época. I2p usa "
-"varias técnicas de de enrutado onion, con lo cual nos seguimos "
-"beneficiando del interés académico en Tor."
+"El diseño de I2P comenzó en 2003, no mucho tiempo después del llegada \n"
+"del [Onion Routing] "
+"(enrutamiento cebolla), [Freenet] (red libre), y [Tor].\n"
+"Nuestro diseño se beneficia sustancialmente de las investigaciones \n"
+"publicadas en torno a esa época. I2P usa varias técnicas de enrutamiento"
+" \n"
+"cebolla, así que continuamos beneficiándonos del significativo interés \n"
+"académico en Tor."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:89
+#: i2p2www/pages/site/docs/how/threat-model.html:128
 msgid ""
 "Taking from the attacks and analysis put forth in the \n"
 "anonymity "
@@ -18750,12 +14426,12 @@ msgstr ""
 "href=\"http://freehaven.net/anonbib/topic.html\">literatura sobre el "
 "anonimato (en gran parte Traffic Analysis: "
-"Protocols, Attacks, Design ⏎\n"
-"Issues and Open Problems), a continuación describimos brevemente un "
-"gran variedad de ataques así como las defensas en i2P.Actualizaremos esta"
-" lista según sean identificados nuevos ataques."
+"Protocols, Attacks, Design Issues and Open Problems), a continuación "
+"describimos brevemente un gran variedad de ataques así como las defensas "
+"en i2P. Actualizaremos esta lista según sean identificados nuevos "
+"ataques."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:98
+#: i2p2www/pages/site/docs/how/threat-model.html:137
 msgid ""
 "Included are some attacks that may be unique to I2P.\n"
 "We do not have good answers for all these attacks, however\n"
@@ -18765,7 +14441,7 @@ msgstr ""
 " soluciones perfectas para esos ataques, pero continuamos estudiando como"
 " defendernos de ellos."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:104
+#: i2p2www/pages/site/docs/how/threat-model.html:143
 msgid ""
 "In addition, many of these attacks are significantly easier than\n"
 "they should be, due to the modest size of the current network.\n"
@@ -18782,7 +14458,7 @@ msgstr ""
 "vayamos difundiendo la palabra y la red crezca, esos ataques serán mucho "
 "mas difíciles de llevar acabo."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:114
+#: i2p2www/pages/site/docs/how/threat-model.html:153
 #, python-format
 msgid ""
 "The\n"
@@ -18795,94 +14471,98 @@ msgstr ""
 "entre redes y \"terminología garlic"
 " sobre el tema."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:123
-#: i2p2www/pages/site/docs/how/threat-model.html:143
+#: i2p2www/pages/site/docs/how/threat-model.html:182
+msgid "Index of Attacks"
+msgstr "Índices de ataques"
+
+#: i2p2www/pages/site/docs/how/threat-model.html:184
+#: i2p2www/pages/site/docs/how/threat-model.html:204
 msgid "Brute force attacks"
 msgstr "Ataques de fuerza bruta"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:124
 #: i2p2www/pages/site/docs/how/threat-model.html:185
+#: i2p2www/pages/site/docs/how/threat-model.html:248
 msgid "Timing attacks"
-msgstr "Ataques de fecha"
+msgstr "Ataques de sincronización"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:125
-#: i2p2www/pages/site/docs/how/threat-model.html:220
+#: i2p2www/pages/site/docs/how/threat-model.html:186
+#: i2p2www/pages/site/docs/how/threat-model.html:285
 msgid "Intersection attacks"
 msgstr "Ataques por intersección"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:126
-#: i2p2www/pages/site/docs/how/threat-model.html:298
+#: i2p2www/pages/site/docs/how/threat-model.html:187
+#: i2p2www/pages/site/docs/how/threat-model.html:365
 msgid "Denial of service attacks"
 msgstr "Ataques de denegación de servicio"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:127
-#: i2p2www/pages/site/docs/how/threat-model.html:385
+#: i2p2www/pages/site/docs/how/threat-model.html:188
+#: i2p2www/pages/site/docs/how/threat-model.html:464
 msgid "Tagging attacks"
-msgstr "Ataques de etiquetas"
+msgstr "Ataques de etiquetado"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:128
-#: i2p2www/pages/site/docs/how/threat-model.html:400
+#: i2p2www/pages/site/docs/how/threat-model.html:189
+#: i2p2www/pages/site/docs/how/threat-model.html:482
 msgid "Partitioning attacks"
-msgstr "Ataques de particiones"
+msgstr "Ataques de particionamiento"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:129
-#: i2p2www/pages/site/docs/how/threat-model.html:438
+#: i2p2www/pages/site/docs/how/threat-model.html:190
+#: i2p2www/pages/site/docs/how/threat-model.html:522
 msgid "Predecessor attacks"
 msgstr "Ataques del predecesor"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:130
-#: i2p2www/pages/site/docs/how/threat-model.html:481
+#: i2p2www/pages/site/docs/how/threat-model.html:191
+#: i2p2www/pages/site/docs/how/threat-model.html:567
 msgid "Harvesting attacks"
 msgstr "Ataques de cosechado"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:131
-#: i2p2www/pages/site/docs/how/threat-model.html:525
+#: i2p2www/pages/site/docs/how/threat-model.html:192
+#: i2p2www/pages/site/docs/how/threat-model.html:614
 msgid "Identification Through Traffic Analysis"
 msgstr "Identificación a través de análisis del tráfico"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:132
-#: i2p2www/pages/site/docs/how/threat-model.html:582
+#: i2p2www/pages/site/docs/how/threat-model.html:193
+#: i2p2www/pages/site/docs/how/threat-model.html:674
 msgid "Sybil attacks"
 msgstr "Ataques Sybil"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:133
-#: i2p2www/pages/site/docs/how/threat-model.html:629
+#: i2p2www/pages/site/docs/how/threat-model.html:194
+#: i2p2www/pages/site/docs/how/threat-model.html:723
 msgid "Buddy Exhaustion attacks"
 msgstr "Ataques por agotamiento de amigos"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:134
-#: i2p2www/pages/site/docs/how/threat-model.html:651
+#: i2p2www/pages/site/docs/how/threat-model.html:195
+#: i2p2www/pages/site/docs/how/threat-model.html:748
 msgid "Cryptographic attacks"
 msgstr "Ataques de cifrados"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:135
+#: i2p2www/pages/site/docs/how/threat-model.html:196
 msgid "Floodfill attacks"
-msgstr "Ataques "
+msgstr "Ataques Floodfill"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:136
-#: i2p2www/pages/site/docs/how/threat-model.html:707
+#: i2p2www/pages/site/docs/how/threat-model.html:197
+#: i2p2www/pages/site/docs/how/threat-model.html:809
 msgid "Other Network Database attacks"
 msgstr "Otros ataques a la base de datos de la red"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:137
+#: i2p2www/pages/site/docs/how/threat-model.html:198
 msgid "Attacks on centralized resources"
 msgstr "Ataques a recursos centralizados"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:138
-#: i2p2www/pages/site/docs/how/threat-model.html:770
+#: i2p2www/pages/site/docs/how/threat-model.html:199
+#: i2p2www/pages/site/docs/how/threat-model.html:875
 msgid "Development attacks"
 msgstr "Ataques de desarrollo"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:139
+#: i2p2www/pages/site/docs/how/threat-model.html:200
 msgid "Implementation attacks"
 msgstr "Ataques de implementación"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:140
-#: i2p2www/pages/site/docs/how/threat-model.html:849
+#: i2p2www/pages/site/docs/how/threat-model.html:201
+#: i2p2www/pages/site/docs/how/threat-model.html:959
 msgid "Other Defenses"
 msgstr "Otras defensas"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:145
+#: i2p2www/pages/site/docs/how/threat-model.html:208
 msgid ""
 "A brute force attack can be mounted by a global passive or active "
 "adversary, \n"
@@ -18909,11 +14589,11 @@ msgstr ""
 " mensajes frecuentemente (de fin a fin y mensajes de mantenimiento de la "
 "red), además un mensaje de fin a fin cambia su tamaño y datos a lo largo "
 "de su camino. Además, un adversario externo tampoco tiene acceso al "
-"mensaje, ya que la comunicación interna entre ruters está cifrada y es "
-"enviada (haciendo que un mensaje de 1024 bytes sea indistinguible de un "
-"mensaje de 2048 bytes)"
+"mensaje, ya que la comunicación interna entre ruters está cifrada y "
+"después enviada (haciendo que un mensaje de 1024 bytes sea indistinguible"
+" de un mensaje de 2048 bytes)"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:157
+#: i2p2www/pages/site/docs/how/threat-model.html:220
 msgid ""
 "However, a powerful attacker can use brute force to detect trends - if "
 "they \n"
@@ -18953,7 +14633,7 @@ msgstr ""
 "usar leasesets cifrados o no publicados para las eepsites. Otras medidas,"
 " como retardos no triviales y rutas restringidas no se han implementado."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:174
+#: i2p2www/pages/site/docs/how/threat-model.html:237
 #, python-format
 msgid ""
 "As a partial defense against a single router or group of routers trying "
@@ -18972,7 +14652,7 @@ msgstr ""
 "selección y anulación de los ruters son discutidos en la página de selección de ruters."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:187
+#: i2p2www/pages/site/docs/how/threat-model.html:252
 msgid ""
 "I2P's messages are unidirectional and do not necessarily imply that a "
 "reply\n"
@@ -18996,7 +14676,7 @@ msgstr ""
 "de la red, un atacante podría inhabilitar algunos enlaces como mensajes "
 "demasiado lentos como para ser pasados."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:197
+#: i2p2www/pages/site/docs/how/threat-model.html:262
 msgid ""
 "This sort of attack is powerful, but its applicability to I2P is non "
 "obvious,\n"
@@ -19020,10 +14700,10 @@ msgstr ""
 "atacante sabe que una respuesta será enviada tan pronto como el mensaje "
 "llegue. Aunque hay varios escenarios en los cuales se exponen respuestas "
 "casi automáticas - la librería de streaming lo hace (con el SYN+ACK) al "
-"igual que que el modo de mensaje de la garantía del envío ( con el "
+"igual que que el modo de mensaje de la garantía del envío (con el "
 "DataMessage+DeliveryStatusMessage)."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:207
+#: i2p2www/pages/site/docs/how/threat-model.html:272
 #, python-format
 msgid ""
 "Without protocol scrubbing or higher latency, global active adversaries "
@@ -19047,7 +14727,7 @@ msgstr ""
 "href=\"%(todo)s#batching\">técnicas de enrutado avanzado de túneles, "
 "pero estas no están implementadas en I2P."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:216
+#: i2p2www/pages/site/docs/how/threat-model.html:281
 #, python-format
 msgid ""
 "References: Low-Resource Routing Attacks Against "
@@ -19056,7 +14736,7 @@ msgstr ""
 "Referencias: Low-Resource Routing Attacks Against "
 "Anonymous Systems"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:222
+#: i2p2www/pages/site/docs/how/threat-model.html:289
 msgid ""
 "Intersection attacks against low latency systems are extremely powerful -"
 "\n"
@@ -19079,7 +14759,7 @@ msgstr ""
 "mensaje pasa a través. El costo de este ataque aumenta según aumenta el "
 "tamaño de la red, pero puede ser válido en varios escenarios."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:232
+#: i2p2www/pages/site/docs/how/threat-model.html:299
 #, python-format
 msgid ""
 "In summary, if an attacker is at both ends of your tunnel at the same "
@@ -19095,16 +14775,16 @@ msgstr ""
 "enrutado onion de baja latencia. Tor proporciona una aclaración similar."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:240
+#: i2p2www/pages/site/docs/how/threat-model.html:307
 msgid "Partial defenses implemented in I2P:"
 msgstr "Defensa parcialmente implementada en I2P:"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:244
+#: i2p2www/pages/site/docs/how/threat-model.html:311
 #, python-format
 msgid "strict ordering of peers"
 msgstr "orden estricto de pares"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:247
+#: i2p2www/pages/site/docs/how/threat-model.html:314
 #, python-format
 msgid ""
 "peer profiling and selection from a "
@@ -19113,11 +14793,11 @@ msgstr ""
 "selección y perfiles de los pares de un"
 " pequeño grupo que cambia lentamente"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:250
+#: i2p2www/pages/site/docs/how/threat-model.html:317
 msgid "Limits on the number of tunnels routed through a single peer"
 msgstr "Límite en el número de túneles rutados a través de un solo par"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:253
+#: i2p2www/pages/site/docs/how/threat-model.html:320
 msgid ""
 "Prevention of peers from the same /16 IP range from being members of a "
 "single tunnel"
@@ -19125,7 +14805,7 @@ msgstr ""
 "Prevención de pares del mismo rango /16 de IPs por ser miembros del mismo"
 " único túnel."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:256
+#: i2p2www/pages/site/docs/how/threat-model.html:323
 msgid ""
 "For eepsites or other hosted services, we support\n"
 "simultaneous hosting on multiple routers, or\n"
@@ -19135,7 +14815,7 @@ msgstr ""
 "simultáneo en múltiples ruters, o multihoming"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:263
+#: i2p2www/pages/site/docs/how/threat-model.html:330
 msgid ""
 "Even in total, these defenses are not a complete solution.\n"
 "Also, we have made some design choices that may significantly increase "
@@ -19145,11 +14825,11 @@ msgstr ""
 "Además, hemos hecho algunas elecciones de diseño que podrían incrementar "
 "las vulnerabilidades: "
 
-#: i2p2www/pages/site/docs/how/threat-model.html:268
+#: i2p2www/pages/site/docs/how/threat-model.html:335
 msgid "We do not use low-bandwidth \"guard nodes\""
 msgstr "No utilizamos \"nodos guardianes\" de bajo ancho de banda"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:271
+#: i2p2www/pages/site/docs/how/threat-model.html:338
 msgid ""
 "We use tunnel pools comprised of several tunnels, and traffic can shift "
 "from tunnel to tunnel."
@@ -19157,13 +14837,13 @@ msgstr ""
 "Usamos grupos de túneles compuestos de varios túneles, y el tráfico puede"
 " pasar de túnel a túnel."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:274
+#: i2p2www/pages/site/docs/how/threat-model.html:341
 msgid "Tunnels are not long-lived; new tunnels are built every 10 minutes."
 msgstr ""
 "Los túneles no son de larga duración; los túneles se recrean cada 10 "
 "minutos."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:277
+#: i2p2www/pages/site/docs/how/threat-model.html:344
 msgid ""
 "Tunnel lengths are configurable.\n"
 "While 3-hop tunnels are recommended for full protection, several "
@@ -19174,7 +14854,7 @@ msgstr ""
 "por túnel para protección total, algunas aplicaciones y servicios usan "
 "túneles de 2 saltos por defecto."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:284
+#: i2p2www/pages/site/docs/how/threat-model.html:351
 #, python-format
 msgid ""
 "In the future, it could\n"
@@ -19190,19 +14870,19 @@ msgid ""
 msgstr ""
 "En el futuro, esto podría ocurrir para los cares que puedan permitirse "
 "retardos significativos (por retardos no "
-"triviales y estrategias de "
-"batching). Además, esto sólo es relevante para las destinaciones que "
-"pueden ser conocidas por otra gente - un grupo privado cuya destinación "
+"triviales y estrategias de procesado "
+"por lotes). Además, esto sólo es relevante para las destinaciones que"
+" pueden ser conocidas por otra gente - un grupo privado cuya destinación "
 "es sólo conocida por pares de confianza no tiene de que preocuparse, ya "
 "que un adversario no puede contactarles,\"ping\" them, para montar el "
 "ataque."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:293
+#: i2p2www/pages/site/docs/how/threat-model.html:360
 #, python-format
 msgid "Reference: One Cell Enough"
 msgstr "Referencia: One Cell Enough"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:300
+#: i2p2www/pages/site/docs/how/threat-model.html:367
 msgid ""
 "There are a whole slew of denial of service attacks available against "
 "I2P,\n"
@@ -19211,39 +14891,46 @@ msgstr ""
 "Hay un montón de ataques de denegación de servicio disponibles contra "
 "I2P, cada cual con sus costes y consecuencias:"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:305
+#: i2p2www/pages/site/docs/how/threat-model.html:373
 msgid ""
 "Greedy user attack: This is simply\n"
 "people trying to consume significantly more resources than they are \n"
 "willing to contribute. The defense against this is:"
 msgstr ""
-"Ataque del usuario codiciose: Esto es simplemente gente intentando"
+"Ataque del usuario codicioso: Esto es simplemente gente intentando"
 " consumir muchas más recursos de los que están dispuestos a compartir. La"
 " defensa contra este ataque es:"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:311
+#: i2p2www/pages/site/docs/how/threat-model.html:379
 #, python-format
 msgid ""
 "Set defaults so that most users provide resources to the network.\n"
 "In I2P, users route traffic by default. In sharp distinction to\n"
 "other networks,\n"
-"over 95%% of I2P users relay traffic for others."
+"over 95% of I2P users relay traffic for others."
 msgstr ""
-"Configurar por defecto para que la mayoría de los usuarios compartan "
-"recursos con la red. En I2P los usuarios rutean tráfico por defecto. A "
-"diferencia de otras redes, más del 95%% "
-"de los usuarios de I2P reenvían tráfico de otros usuarios."
+"Establezca las configuraciones por defecto de forma que la mayoría de los"
+" \n"
+"usuarios proporcionen recursos a la red. En I2P, los usuarios enrutan "
+"tráfico \n"
+"por defecto. En clara distinción con otras "
+"redes, \n"
+"más del 95% de los usuarios de I2P repiten tráfico para otros."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:317
+#: i2p2www/pages/site/docs/how/threat-model.html:385
 msgid ""
 "Provide easy configuration options so that users may increase their\n"
 "contribution (share percentage) to the network. Display easy-to-"
 "understand\n"
 "metrics such as \"share ratio\" so that users may see what they are "
 "contributing."
-msgstr "Proveer"
+msgstr ""
+"Proporcionar opciones de configuración fáciles para que los usuarios "
+"puedan incrementar su contribución (porcentaje de lo que se comparte) a "
+"la red. Mostrar medidas fáciles de entender como \"el ratio de lo que se "
+"comparte\" para que los usuarios puedan ver lo que contribbuyen."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:322
+#: i2p2www/pages/site/docs/how/threat-model.html:390
 msgid ""
 "Maintain a strong community with blogs, forums, IRC, and other means of "
 "communication."
@@ -19251,7 +14938,7 @@ msgstr ""
 "Manteniendo una comunidad fuerte con blogs, foros, IRC y otras formas de "
 "comunicación."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:327
+#: i2p2www/pages/site/docs/how/threat-model.html:397
 #, python-format
 msgid ""
 "Starvation attack: A hostile user may attempt to harm the network "
@@ -19294,7 +14981,7 @@ msgstr ""
 " problemáticos; aún así todavía se requieren grandes esfuerzos en este "
 "área."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:344
+#: i2p2www/pages/site/docs/how/threat-model.html:417
 #, python-format
 msgid ""
 "Flooding attack: A hostile user may attempt to flood the network,\n"
@@ -19342,7 +15029,7 @@ msgstr ""
 "implemente el funcionamiento avanzad de los"
 " túneles)."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:360
+#: i2p2www/pages/site/docs/how/threat-model.html:436
 msgid ""
 "CPU load attack: There are currently some methods for people to \n"
 "remotely request that a peer perform some cryptographically expensive \n"
@@ -19364,7 +15051,7 @@ msgstr ""
 "ejemplo HashCash) puede mitigarse el problema, aunque hay posibilidad "
 "también de que un atacante explote algún error en la implementación."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:370
+#: i2p2www/pages/site/docs/how/threat-model.html:449
 #, python-format
 msgid ""
 "Floodfill DOS attack: A hostile user may attempt to harm the "
@@ -19382,15 +15069,14 @@ msgstr ""
 "Ataque floodfill de denegación de servicio: Un usuario hostil "
 "puede intentar dañar la red convirtiéndose en un ruter floodfill. Las "
 "defensas actuales contra los ruters floodfill no confiables, "
-"intermitentes o maliciosos son pobres actualmente. Un ruter floodfill "
-"puede dar respuestas falsas o no darlas a las búsquedas, y puede también "
-"interferir en las comunicaciones entre floodfills. Se han implementado "
-"algunas defensas y elcontrol de "
-"perfiles, aún así hay mucho por hacer todavía. Para más información "
-"vea la web de la base de datos de la "
-"red."
+"intermitentes o maliciosos son pobres. Un ruter floodfill puede dar "
+"respuestas falsas o no darlas a las búsquedas, y puede también interferir"
+" en las comunicaciones entre floodfills. Se han implementado algunas "
+"defensas y el control de perfiles, aún "
+"así hay mucho por hacer todavía. Para más información vea la web de la base de datos de la red."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:386
+#: i2p2www/pages/site/docs/how/threat-model.html:468
 #, python-format
 msgid ""
 "Tagging attacks - modifying a message so that it can later be identified"
@@ -19429,7 +15115,7 @@ msgstr ""
 "entrada y en los de salida. Los atacantes externos tampoco pueden hacer "
 "nada, ya que los enlaces están cifrados y los mensajes firmados."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:402
+#: i2p2www/pages/site/docs/how/threat-model.html:486
 msgid ""
 "Partitioning attacks - finding ways to segregate (technically or "
 "analytically)\n"
@@ -19461,9 +15147,9 @@ msgstr ""
 "analíticamente) de separar los pares en la red - son a tener en cuenta "
 "cuando nos enfrentamos a adversarios poderosos, ya que el tamaño de la "
 "red juega un papel importante a la hora de determinar el anonimato. I2P "
-"ha resuelto el problema técnico del ataque por particiones que corta los "
-"enlaces entre los pares dentro de su base de datos de la red, la cual "
-"mantiene estadísticas sobre los pares a fin de permitir que las "
+"ha resuelto el problema técnico del ataque de particionamiento que corta "
+"los enlaces entre los pares dentro de su base de datos de la red, la cual"
+" mantiene estadísticas sobre los pares a fin de permitir que las "
 "conexiones fragmentadas sean reparadas usando otras partes de la red. "
 "Aunque si un atacante desconecta todos los enlaces de un par, aislando el"
 " objetivo completamente, la base de datos poco podrá hacer para reparar "
@@ -19472,7 +15158,7 @@ msgstr ""
 " a estar inaccesibles, y alertar al cliente de que está temporalmente "
 "desconectado (este tipo de detección no está aún implementada)."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:418
+#: i2p2www/pages/site/docs/how/threat-model.html:502
 #, python-format
 msgid ""
 "Partitioning the network analytically by looking for differences in how "
@@ -19518,7 +15204,7 @@ msgstr ""
 " parte de la red (y aún así sólo sería un ataque probabilístico, ya que "
 "no sabría que otros túneles o mensajes tienen esos retardos)."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:434
+#: i2p2www/pages/site/docs/how/threat-model.html:518
 #, python-format
 msgid ""
 "Also discussed on the network database "
@@ -19527,7 +15213,7 @@ msgstr ""
 "También se discute en la página de la base "
 "de datos de la red (ataque de bootstrap)."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:440
+#: i2p2www/pages/site/docs/how/threat-model.html:526
 msgid ""
 "The predecessor attack is passively gathering statistics in an attempt to"
 " see\n"
@@ -19544,7 +15230,7 @@ msgid ""
 "target is located."
 msgstr ""
 "El ataque del predecesor es obtener estadísticas pasivamente intentando "
-"ver que pares están 'cerca' de la destinación, participando en sus "
+"ver qué pares están 'cerca' de la destinación, participando en sus "
 "túneles y haciendo el seguimiento de los saltos anteriores o siguientes ("
 " para túneles de salida o entrada, respectivamente). Con el tiempo, un "
 "atacante usando un ejemplo aleatorio perfecto de pares y ordenación, "
@@ -19552,7 +15238,7 @@ msgstr ""
 " resto, y ese par podría llegar a estar donde el el objetivo se "
 "encuentra."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:450
+#: i2p2www/pages/site/docs/how/threat-model.html:536
 #, python-format
 msgid ""
 "I2P avoids this in four ways: first, the peers selected to participate in"
@@ -19588,11 +15274,11 @@ msgstr ""
 "negación plausible, ya que la variación ocasional de la puerta de salida "
 "parecerá un túnel normal. Cuarta, con las rutas restringidas (no "
-"implementado), sólo el para con una conexión restringida con el objetivo "
+"implementadas), sólo el par con una conexión restringida con el objetivo "
 "será capaz de contactar con el objetivo, mientras que los atacantes "
 "simplemente pasarán por la puerta de salida."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:467
+#: i2p2www/pages/site/docs/how/threat-model.html:553
 #, python-format
 msgid ""
 "The current tunnel build method\n"
@@ -19604,7 +15290,7 @@ msgstr ""
 "predecesor. Ver también el ataque de "
 "interesección."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:473
+#: i2p2www/pages/site/docs/how/threat-model.html:559
 #, python-format
 msgid ""
 "References: %(pdf2008)s\n"
@@ -19615,7 +15301,7 @@ msgstr ""
 "actualización del documento sobre el ataque del predecesor %(pdf2004)s."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:482
+#: i2p2www/pages/site/docs/how/threat-model.html:571
 msgid ""
 "\"Harvesting\" means compiling a list of users running I2P.\n"
 "It can be used for legal attacks and to help\n"
@@ -19628,7 +15314,7 @@ msgstr ""
 "par, y cosechando todas las referencias que pueda encontrar sobre otros "
 "pares."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:489
+#: i2p2www/pages/site/docs/how/threat-model.html:578
 msgid ""
 "I2P itself is not designed with effective defenses against\n"
 "this attack, since there is the distributed network database \n"
@@ -19640,7 +15326,7 @@ msgstr ""
 "esta información. Aunque los siguientes factores hacen este ataque sea un"
 " poco más difícil en la práctica:"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:496
+#: i2p2www/pages/site/docs/how/threat-model.html:585
 msgid ""
 "Network growth will make it more difficult to obtain a given proportion "
 "of the network"
@@ -19648,13 +15334,13 @@ msgstr ""
 "El crecimiento de la red hará más difícil el controlar una parte "
 "determinada de la red."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:499
+#: i2p2www/pages/site/docs/how/threat-model.html:588
 msgid "Floodfill routers implement query limits as DOS protection"
 msgstr ""
 "Los ruters floodfill implementan límites en las peticiones para prevenir "
 "ataques de denegación de servicio, DOS."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:502
+#: i2p2www/pages/site/docs/how/threat-model.html:591
 msgid ""
 "\"Hidden mode\", which prevents a router from publishing its information "
 "to the netDb,\n"
@@ -19664,7 +15350,7 @@ msgstr ""
 "\"Modo oculto\", evita que el ruter publique su información en la netDb, "
 "(pero también hace que no reenvíe datos), no se usa mucho por ahora."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:508
+#: i2p2www/pages/site/docs/how/threat-model.html:597
 #, python-format
 msgid ""
 "In future implementations,\n"
@@ -19685,7 +15371,7 @@ msgstr ""
 " túneles por los que puede ser cntactado (al igual que sus claves "
 "publicas y demás)."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:517
+#: i2p2www/pages/site/docs/how/threat-model.html:606
 msgid ""
 "In the future, routers could use GeoIP to identify if they are in a "
 "particular\n"
@@ -19698,7 +15384,7 @@ msgstr ""
 "peligroso. En ese caso, el ruter podrá activar el modo oculto "
 "automáticamente, o utilizar otros métodos de enrutado restringidos."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:526
+#: i2p2www/pages/site/docs/how/threat-model.html:618
 #, python-format
 msgid ""
 "By inspecting the traffic into and out of a router, a malicious ISP\n"
@@ -19719,15 +15405,15 @@ msgstr ""
 "protocolos y la capa de transporte hacen bastante difícil identificar"
 " el tráfico de I2P:"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:536
+#: i2p2www/pages/site/docs/how/threat-model.html:628
 msgid "Random port selection"
 msgstr "Selección de puertos aleatoria"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:539
+#: i2p2www/pages/site/docs/how/threat-model.html:631
 msgid "Point-to-Point Encryption of all traffic"
 msgstr "Cifrado de todo el tráfico de punto a punto"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:542
+#: i2p2www/pages/site/docs/how/threat-model.html:634
 msgid ""
 "DH key exchange with no protocol bytes or other unencrypted constant "
 "fields"
@@ -19735,7 +15421,7 @@ msgstr ""
 "Intercambio de clave DH sin bytes del protocolo u otros campos constantes"
 " no cifrados"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:545
+#: i2p2www/pages/site/docs/how/threat-model.html:637
 #, python-format
 msgid ""
 "Simultaneous use of both\n"
@@ -19749,7 +15435,7 @@ msgstr ""
 "inspeccionar y seguir con equipamiento DPI, (inspección profunda de "
 "paquetes)."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:553
+#: i2p2www/pages/site/docs/how/threat-model.html:645
 msgid ""
 "In the near future, we plan to directly address traffic analysis issues "
 "by further obfuscation of I2P transport protocols, possibly including:"
@@ -19758,7 +15444,7 @@ msgstr ""
 "trafico ofuscando los protocolos de transporte de I2P, probablemente "
 "incluyendo:"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:557
+#: i2p2www/pages/site/docs/how/threat-model.html:649
 msgid ""
 "Padding at the transport layer to random lengths, especially during the "
 "connection handshake"
@@ -19766,7 +15452,7 @@ msgstr ""
 "Rellenando la capa de transporte para que tenga determinados tamaños, "
 "especialmente durante el handshake de conexión"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:560
+#: i2p2www/pages/site/docs/how/threat-model.html:652
 msgid ""
 "Study of packet size distribution signatures, and additional padding as "
 "necessary"
@@ -19774,7 +15460,7 @@ msgstr ""
 "Estudiando las firmas de la distribución de los tamaños de los paquetes, "
 "y rellenando si es necesario."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:563
+#: i2p2www/pages/site/docs/how/threat-model.html:655
 msgid ""
 "Development of additional transport methods that mimic SSL or other "
 "common protocols"
@@ -19782,7 +15468,7 @@ msgstr ""
 "Creación de otros métodos de transporte camuflados como SSL u otros "
 "protocolos comunes."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:566
+#: i2p2www/pages/site/docs/how/threat-model.html:658
 msgid ""
 "Review of padding strategies at higher layers to see how they affect "
 "packet sizes at the transport layer"
@@ -19790,7 +15476,7 @@ msgstr ""
 "Revisión de las estrategias de relleno en las capas superiores para ver "
 "como afectan al tamaño de los paquetes en la capa de transporte."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:569
+#: i2p2www/pages/site/docs/how/threat-model.html:661
 msgid ""
 "Review of methods implemented by various state-level firewalls to block "
 "Tor"
@@ -19798,13 +15484,13 @@ msgstr ""
 "Revisar varios métodos implementados por varios cortafuegos de algunos "
 "estados para bloquear Tor"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:572
+#: i2p2www/pages/site/docs/how/threat-model.html:664
 msgid "Working directly with DPI and obfuscation experts"
 msgstr ""
 "Trabajar directamente con expertos en DPI, inspección profunda de "
 "paquetes, y expertos en ofuscación."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:577
+#: i2p2www/pages/site/docs/how/threat-model.html:669
 #, python-format
 msgid ""
 "Reference: Breaking and Improving Protocol "
@@ -19813,15 +15499,14 @@ msgstr ""
 "Referencia: Breaking and Improving Protocol "
 "Obfuscation"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:584
-#, python-format
+#: i2p2www/pages/site/docs/how/threat-model.html:678
 msgid ""
 "Sybil describes a category of attacks where the adversary creates "
 "arbitrarily\n"
 "large numbers of colluding nodes and uses the increased numbers to help \n"
 "mounting other attacks.  For instance, if an attacker is in a network "
 "where peers\n"
-"are selected randomly and they want an 80% chance to be one of those "
+"are selected randomly and they want an 80% chance to be one of those "
 "peers, they\n"
 "simply create five times the number of nodes that are in the network and "
 "roll \n"
@@ -19843,41 +15528,51 @@ msgid ""
 "appropriate value when necessary (or some other certificate proving "
 "scarcity)."
 msgstr ""
-"Sybil describe una categoría de ataques donde el adversario crea un gran "
-"número arbitrario de nodos y los usa para montar ataques. Por ejemplo, si"
-" un atacante está en una red donde los pares son seleccionados "
-"aleatoriamente y el atacante quiere tener el 80% c de posibilidades de "
-"ser uno de esos pares, simplemente crea 5 veces el número de nodos que "
-"hay en la red y a probar suerte. Cuando crear una identidad no cuesta "
-"esfuerzo, Sybil puede ser un ataque muy poderoso. La mejor técnica para "
-"evitar esto es simplemente hacer que crear una nueva identidad no sea "
-"'gratis' -  Tarzan "
-"(entro otros) usan el hecho de que el número de IPs es limitado, mientras"
-" que I2P utiliza HashCash para "
-"'cobrar' por la creación de un nueva identidad de ruter. Por ahora no "
-"hemos implementado ninguna técnica en particular para evitar los ataque "
-"Sybil, pero I2P incluye espacio en los certificados de los ruters y "
-"destinaciones para estructuras de datos que pueden contener un "
-"certificado HashCash válido, si fuese necesario (o algún otro certificado"
-" que proporcione este costo)."
+"Sybil describe una categoría de ataques donde el adversario crea números"
+" \n"
+"arbitrariamente grandes de nodos compinchados y usan el incremento \n"
+"numérico para ayudar a montar otros ataques. Por ejemplo, si un atacante"
+" \n"
+"esta en una red donde los pares se seleccionan aleatoriamente \n"
+"y quieren un 80% de posibilidades de ser uno de esos pares, \n"
+"simplemente crean cinco veces el número de nodos que están en la red y \n"
+"tiran el dado. Cuando la identidad es gratuita, Sybil puede ser una "
+"técnica \n"
+"muy potente para un adversario enérgico. La técnica primaria para "
+"enfrentar \n"
+"esto es simplemente hacer la identidad 'no gratuita' - Tarzan (entre otros)\n"
+"usa el hecho de que la dirección IP es limitada, mientras IIP (proyecto "
+"de IRC invisible) usaba HashCash"
+"\n"
+"para realizar un 'cargo' por crear una nueva identidad (prueba de "
+"trabajo). Actualmente no hemos implementado técnica particular alguna "
+"para enfrentar Sybil, pero incluimos certificados de posición en las "
+"estructuras de datos del router y el destino que pueden contener un "
+"certificado HashCash de un valor adecuado cuando sea necesario (o algún "
+"otro certificado que pruebe la escasez)."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:602
+#: i2p2www/pages/site/docs/how/threat-model.html:696
 msgid "Requiring HashCash Certificates in various places has two major problems:"
 msgstr "Requerir certificados HashCash en varios sitios tiene algunos problemas:"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:606
+#: i2p2www/pages/site/docs/how/threat-model.html:700
 msgid "Maintaining backward compatibility"
 msgstr "Mantener compatibilidad con versiones anteriores"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:609
+#: i2p2www/pages/site/docs/how/threat-model.html:703
 msgid ""
 "The classic HashCash problem -\n"
 "selecting HashCash values that are meaningful proofs of work on high-end "
 "machines,\n"
 "while still being feasible on low-end machines such as mobile devices."
 msgstr ""
+"El problema clásico del HashCash - seleccionar valores HashCash que sean "
+"pruebas significativas de gasto de trabajo en máquinas potentes, mientras"
+" que también sean factibles en máquinas no tan potentes como los "
+"dispositivos móviles."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:616
+#: i2p2www/pages/site/docs/how/threat-model.html:710
 msgid ""
 "Various limitations on the number of routers in a given IP range restrict"
 "\n"
@@ -19891,16 +15586,16 @@ msgstr ""
 "no pueden poner más computadoras en ese bloque de IPs. Aún así esto no es"
 " defensa contra un adversario con muchos recursos."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:623
+#: i2p2www/pages/site/docs/how/threat-model.html:717
 #, python-format
 msgid ""
 "See the network database page\n"
 "for more Sybil discussion."
 msgstr ""
-"Vea la a href=\"%(netdb)s#threat\">web de la base de datos de la red "
-"para obtener más información sobre Sybil."
+"Vea la web de la base de datos de la red"
+" para obtener más información sobre Sybil."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:630
+#: i2p2www/pages/site/docs/how/threat-model.html:727
 #, python-format
 msgid ""
 "(Reference: In Search of an Anonymouns and Secure "
@@ -19909,7 +15604,7 @@ msgstr ""
 "(Referencia: In Search of an Anonymouns and Secure "
 "Lookup Sección 5.2)"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:634
+#: i2p2www/pages/site/docs/how/threat-model.html:731
 #, python-format
 msgid ""
 "By refusing to accept or forward tunnel build requests, except to a "
@@ -19923,7 +15618,7 @@ msgid ""
 "the performance\n"
 "of peers.\n"
 "However, this is a powerful attack as the number of routers approaches\n"
-"f = 0.2, or 20%% malicious nodes, as specifed in the paper.\n"
+"f = 0.2, or 20% malicious nodes, as specifed in the paper.\n"
 "The malicous routers could also maintain connections to the target router"
 " and provide\n"
 "excellent forwarding bandwidth for traffic over those connections, in an "
@@ -19931,23 +15626,26 @@ msgid ""
 "to manipulate the profiles managed by the target and appear attractive.\n"
 "Further research and defenses may be necessary."
 msgstr ""
-"Negándose a aceptar túneles o el reenvío de las peticiones para crearlos,"
-" excepto para los pares en colisión, un ruter puede asegurarse que un "
-"túnel está formado completamente por un conjunto de ruters en colisión.  "
-"Las posibilidades de obtener éxito son aumentadas si hay un gran número "
-"de ruters en colisión, por ejemplo el ataque "
-"Sybil. Esto es en parte mitigado por losperfiles de los pares usados para "
-"monitorizar el rendimiento de los pares. Aún así este ataque es muy "
-"potente cuando el número de ruters se acerca a f = 0.2, o 20%%, "
-"siendo f el número de nodos maliciosos, como se indica en el estudio. Los"
-" ruters maliciosos también pueden mantener conexiones con el objetivo y "
-"proporcionarle un gran ancho de banda de reenvío  de tráfico en esas "
-"conexiones, intentando manipular los perfiles controlados por el objetivo"
-" y parecer atractivo. Hacen falta más estudios y defensas sobre este "
-"tema."
+"Al rechazar aceptar o remitir las solicitudes de construcción de túneles,"
+" \n"
+"excepto hacia un par (`peer`) compinchado, un router puede asegurar que \n"
+"un túnel está formado en su totalidad con su grupo de routers "
+"compinchados. Las posibilidades de éxito se incrementan si hay un gran \n"
+"número de routers compinchados, es decir, un ataque "
+"Sybil. Esto es mitigado de alguna manera por nuestros métodos de \n"
+"perfilado de pares usados para "
+"monitorizar el rendimiento de los pares. \n"
+"Sin embargo, esto es un ataque potente cuando el número de routers se \n"
+"aproxima a f = 0.2, o 20% nodos maliciosos, como se detalla en"
+" la especificación. Los routers maliciosos también pueden mantener "
+"conexiones con el router objetivo y proporcionar un excelente ancho de \n"
+"banda de reenvío para el tráfico sobre aquellas conexiones, en un intento"
+" de \n"
+"manipular los perfiles gestinados por el objetivo y parecer atractivos. "
+"Podría \n"
+"ser necesaria ulterior investigación y defensa."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:653
+#: i2p2www/pages/site/docs/how/threat-model.html:752
 #, python-format
 msgid ""
 "We use strong cryptography with long keys, and\n"
@@ -19993,7 +15691,7 @@ msgstr ""
 "cambio del tamaño de las claves o los secretos compartidos, manteniendo "
 "la compatibilidad con versiones anteriores."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:672
+#: i2p2www/pages/site/docs/how/threat-model.html:771
 #, python-format
 msgid ""
 "Upgrading the various data structures and protocols to support longer "
@@ -20013,7 +15711,7 @@ msgstr ""
 "planteamiento podamos minimizar los trastornos e implementar mecanismos "
 "que hagan más fáciles futuros cambios."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:681
+#: i2p2www/pages/site/docs/how/threat-model.html:780
 msgid ""
 "In the future, several I2P protocols and data structures\n"
 "support securely padding messages to arbitrary sizes, so messages could "
@@ -20031,11 +15729,11 @@ msgstr ""
 "más subpartes de lo que realmente tienen. Hasta el momento los túneles "
 "garlic y los mensajes de fin a fin utilizan un simple relleno aleatorio."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:691
+#: i2p2www/pages/site/docs/how/threat-model.html:790
 msgid "Floodfill Anonymity attacks"
 msgstr "Ataques de anonimato FloodFill"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:692
+#: i2p2www/pages/site/docs/how/threat-model.html:794
 #, python-format
 msgid ""
 "In addition to the floodfill DOS attacks described\n"
@@ -20068,7 +15766,7 @@ msgstr ""
 "profundamente. Los ataques específicos potenciales y sus defensas deberán"
 " ser discutidos en estudios futuros."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:708
+#: i2p2www/pages/site/docs/how/threat-model.html:810
 #, python-format
 msgid ""
 "A hostile user may attempt to harm the network by\n"
@@ -20082,11 +15780,11 @@ msgstr ""
 "respondan. Varios escenarios como este han sido discutidos en la web de la base de datos de la red."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:718
+#: i2p2www/pages/site/docs/how/threat-model.html:820
 msgid "Central Resource Attacks"
 msgstr "Ataque de Recurso Central"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:719
+#: i2p2www/pages/site/docs/how/threat-model.html:824
 msgid ""
 "There are a few centralized or limited resources (some inside I2P, some "
 "not)\n"
@@ -20109,7 +15807,7 @@ msgstr ""
 "ataques a los servicios externos afectan mayormente a cómo los nuevos "
 "usuarios pueden encontrarnos, no en la operación de la red en sí misma."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:729
+#: i2p2www/pages/site/docs/how/threat-model.html:834
 #, python-format
 msgid ""
 "The website is mirrored and uses DNS round-robin"
@@ -20118,7 +15816,7 @@ msgstr ""
 "La web tiene copias en varios lugares y usa "
 "round-robin DNS para el acceso público externo."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:732
+#: i2p2www/pages/site/docs/how/threat-model.html:837
 #, python-format
 msgid ""
 "Routers now support multiple external reseed "
@@ -20132,7 +15830,7 @@ msgstr ""
 "resiembra, y el manejo de los ruters maliciosos o no disponibles debería "
 "ser mejorado."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:737
+#: i2p2www/pages/site/docs/how/threat-model.html:842
 msgid ""
 "Routers now support multiple update file locations.\n"
 "A malicious update host could feed a huge file, need to limit the size."
@@ -20141,11 +15839,11 @@ msgstr ""
 "localizaciones. Un ruter malicioso de actualizaciones podría enviar un "
 "archivo enorme, se necesita limitar el tamaño."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:741
+#: i2p2www/pages/site/docs/how/threat-model.html:846
 msgid "Routers now support multiple default trusted update signers."
 msgstr "Los ruters ahora soportan múltiples actualizaciones de confianza firmadas."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:744
+#: i2p2www/pages/site/docs/how/threat-model.html:849
 msgid ""
 "Routers now better handle multiple unreliable "
 "floodfill peers.\n"
@@ -20156,7 +15854,7 @@ msgstr ""
 "múltiples no confiables. Los FloodFills maliciosos necesitan más estudio."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:748
+#: i2p2www/pages/site/docs/how/threat-model.html:853
 #, python-format
 msgid ""
 "The code is now stored in a distributed source "
@@ -20165,7 +15863,7 @@ msgstr ""
 "El cóodigo está ahora almacenado en un sistema "
 "distribuido de control de código fuente."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:751
+#: i2p2www/pages/site/docs/how/threat-model.html:856
 msgid ""
 "Routers rely on a single news host, but there is a hardcoded backup URL "
 "pointing to a different host.\n"
@@ -20176,7 +15874,7 @@ msgstr ""
 "malicioso de noticias podría enviar un archivo enorme, se necesita "
 "limitar el tamaño."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:755
+#: i2p2www/pages/site/docs/how/threat-model.html:860
 #, python-format
 msgid ""
 "Naming system services, including addressbook "
@@ -20196,7 +15894,7 @@ msgstr ""
 "dominios requieren algún cantidad de confianza, vea la web de dominios para más detalles."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:762
+#: i2p2www/pages/site/docs/how/threat-model.html:867
 msgid ""
 "We remain reliant on the DNS service for i2p2.de, losing this would cause"
 " substantial\n"
@@ -20209,7 +15907,7 @@ msgstr ""
 "reduciría la red (de corto a medio plazo), al igual que lo hizo la "
 "pérdida de i2p.net."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:772
+#: i2p2www/pages/site/docs/how/threat-model.html:879
 msgid ""
 "These attacks aren't directly on the network, but instead go after its "
 "development team \n"
@@ -20233,11 +15931,11 @@ msgstr ""
 "denuncia con secreto de sumario para que no pueda contarlo, con amenaza "
 "de cárcel), podríamos tener un gran problema."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:781
+#: i2p2www/pages/site/docs/how/threat-model.html:888
 msgid "However, two techniques help defend against these attacks:"
 msgstr "Sin embargo, estas técnicas ayudan a defenderse contra estos ataques:"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:785
+#: i2p2www/pages/site/docs/how/threat-model.html:892
 #, python-format
 msgid ""
 "All components of the network must be open source to enable inspection, "
@@ -20262,7 +15960,7 @@ msgstr ""
 "sistema de listas de confianza para restringir las modificaciones a sólo "
 "aquellos que han sido aprovados."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:793
+#: i2p2www/pages/site/docs/how/threat-model.html:900
 #, python-format
 msgid ""
 "Development over the network itself, allowing developers to stay "
@@ -20282,7 +15980,7 @@ msgstr ""
 "discusión (forum.i2p), y webs de distribución de las aplicaciones, todo "
 "disponible dentro de I2P."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:804
+#: i2p2www/pages/site/docs/how/threat-model.html:911
 msgid ""
 "We also maintain relationships with various organizations that offer "
 "legal advice,\n"
@@ -20291,11 +15989,11 @@ msgstr ""
 "También mantenemos relaciones con organizaciones que ofrecen consejo "
 "legal, en caso de que fuese necesario algún tipo de defensa legal."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:809
+#: i2p2www/pages/site/docs/how/threat-model.html:916
 msgid "Implementation attacks (bugs)"
 msgstr "Ataques de implementación  (errores de programación)"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:810
+#: i2p2www/pages/site/docs/how/threat-model.html:920
 msgid ""
 "Try as we might, most nontrivial applications include errors in the "
 "design or \n"
@@ -20321,7 +16019,7 @@ msgstr ""
 " la seguridad por "
 "oscuridad."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:821
+#: i2p2www/pages/site/docs/how/threat-model.html:931
 msgid ""
 "In addition, the code is being \n"
 "treated the same way, with little aversion towards reworking or throwing "
@@ -20344,7 +16042,7 @@ msgstr ""
 " ella sería raro que los programadores gastasen tanto tiempo en "
 "aprenderse el software como para identificar deficiencias y errores."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:831
+#: i2p2www/pages/site/docs/how/threat-model.html:941
 msgid ""
 "Our software is likely, in particular, to contain bugs related to denial "
 "of service\n"
@@ -20358,7 +16056,7 @@ msgstr ""
 " de memoria (OOMS), cross-site-scripting (XSS) en la consola del ruter, y"
 " otras vulnerabilidades no tan normales a causa de varios protocolos."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:837
+#: i2p2www/pages/site/docs/how/threat-model.html:947
 #, python-format
 msgid ""
 "I2P is still a small network with a small development community and "
@@ -20376,11 +16074,11 @@ msgstr ""
 "Continuamos reclutando gente para que se "
 "involucre y ayude."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:850
+#: i2p2www/pages/site/docs/how/threat-model.html:960
 msgid "Blocklists"
 msgstr "Blocklists, lista de bloqueos"
 
-#: i2p2www/pages/site/docs/how/threat-model.html:851
+#: i2p2www/pages/site/docs/how/threat-model.html:961
 msgid ""
 "To some extent, I2P could be enhanced to avoid peers operating at IP "
 "addresses\n"
@@ -20394,7 +16092,7 @@ msgstr ""
 "varios formatos estándar, con listados de organizaciones contrarias a "
 "I2P, estados potencialmente peligrosos, y otros."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:857
+#: i2p2www/pages/site/docs/how/threat-model.html:967
 msgid ""
 "To the extent that active peers actually do show up in the actual "
 "blocklist,\n"
@@ -20409,7 +16107,7 @@ msgstr ""
 "general. Por lo cual queremos llegar aun acuerdo en una lista de bloqueo "
 "en particular y activarla por defecto."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:865
+#: i2p2www/pages/site/docs/how/threat-model.html:975
 msgid ""
 "Blocklists are only a part (perhaps a small part) of an array of defenses"
 "\n"
@@ -20427,7 +16125,7 @@ msgstr ""
 " de arriba hay mejoras que se pueden implementar para detectar la "
 "malicia."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:874
+#: i2p2www/pages/site/docs/how/threat-model.html:984
 msgid ""
 "If a blocklist is hosted at a central location with automatic updates\n"
 "the network is vulnerable to a\n"
@@ -20442,7 +16140,7 @@ msgstr ""
 "automáticas a una lista ofrecen al proveedor la capacidad de apagar toda "
 "la red i2p. Completamente."
 
-#: i2p2www/pages/site/docs/how/threat-model.html:882
+#: i2p2www/pages/site/docs/how/threat-model.html:992
 msgid ""
 "Currently, a default blocklist is distributed with our software,\n"
 "listing only the IPs of past DOS sources.\n"
@@ -20462,7 +16160,7 @@ msgstr ""
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:2
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:6
 msgid "Tunnel Overview"
-msgstr ""
+msgstr "Introducción a los túenels."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:3
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:3
@@ -20475,6 +16173,9 @@ msgid ""
 "with\n"
 "links to more technical pages, details, and specifications."
 msgstr ""
+"Esta página contiene una introducción a la terminología y funcionamiento "
+"de los túneles I2P, con enlaces a páginas más técnicas, detalles y "
+"especificaciones."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:12
 #, python-format
@@ -20492,35 +16193,59 @@ msgid ""
 "to forward it to the gateway router for one of Bob's current inbound \n"
 "tunnels, which in turn passes it to Bob."
 msgstr ""
+"Como se ha explicado brevemente en el class=\"marksource tag\">%(intro)s\">introductionclass=\"marksource tag\">, I2P "
+"construye \"túneles\" virtuales -class=\"marksource newline\" title=\"New"
+" line\"> caminos temporales y unidireccionales a través de una secuencia "
+"de ruters. Estos class=\"marksource newline\" title=\"New line\"> túneles"
+" estan clasificados como túneles de entrada (sonde todo "
+"class=\"marksource newline\" title=\"New line\"> va hacia el creador del "
+"túnel) o túneles de salida class=\"marksource newline\" title=\"New "
+"line\"> (donde el creador del túnel envía los mensajes lejos de él). "
+"Cuando Alice class=\"marksource newline\" title=\"New line\"> quiere "
+"enviar un mensaje a Bob, ella (normalmente) lo envía a uno de "
+"lass=\"marksource newline\" title=\"New line\"> sus túneles de salida ya "
+"existentes con las instrucciones para el punto final de ese túnel "
+"class=\"marksource newline\" title=\"New line\"> para que sea enviado al "
+"ruter gateway hasta los túneles de entrada de Bob class=\"marksource "
+"newline\" title=\"New line\">, que por turnos lo llevarán hasta Bob."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:25
 msgid "Alice connecting through her outbound tunnel to Bob via his inbound tunnel"
 msgstr ""
+"Alice conectando a través de su túnel de salida hacia Bob vía su túnel de"
+" entrada"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:27
 msgid "Outbound Gateway"
-msgstr ""
+msgstr "Gateway de salida"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:28
 msgid "Outbound Participant"
-msgstr ""
+msgstr "Participante de salida"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:29
 #: i2p2www/pages/site/docs/tunnels/implementation.html:131
 msgid "Outbound Endpoint"
-msgstr ""
+msgstr "Punto final de salida"
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
+#: i2p2www/pages/site/docs/tunnels/implementation.html:140
+msgid "Inbound Gateway"
+msgstr "Puerta de salida de entrada"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:31
 msgid "Inbound Participant"
-msgstr ""
+msgstr "Participante de entrada"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:32
 msgid "Inbound Endpoint"
-msgstr ""
+msgstr "Punto final de entrada"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:36
 msgid "Tunnel vocabulary"
-msgstr ""
+msgstr "Vocabulario de los túneles"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:38
 #, python-format
@@ -20531,12 +16256,18 @@ msgid ""
 "network database.  For outbound tunnels, the\n"
 "gateway is the originating router.  (e.g. both A and D above)"
 msgstr ""
+"Túnel puerta de salida, gateway - el primer ruter en un túnel. "
+"Para los túneles de entrada, este es el mencionado en el LeaseSet "
+"publicado en la base de datos de la red. Para "
+"los túneles de salida, la gateway es el ruter original (ej, A y D arriba)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:44
 msgid ""
 "Tunnel endpoint - the last router in a tunnel.  (e.g. both C and F"
 " above)"
 msgstr ""
+"Túnel punto final, endpoint - el último ruter en un túnel (ej, C y"
+" F arriba)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:45
 msgid ""
@@ -20544,22 +16275,30 @@ msgid ""
 "gateway or\n"
 "endpoint (e.g. both B and E above)"
 msgstr ""
+"Túnel participante - todos los ruters en un túnel excepto la "
+"puerta de salida o el punto final (ej, B y E arriba)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:49
 msgid ""
 "n-Hop tunnel - a tunnel with a specific number of inter-router "
 "jumps, e.g.:"
 msgstr ""
+"Túnel de n saltos - un túnel con un número específico de saltos "
+"entre ruters, por ejemplo:"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:51
 msgid "0-hop tunnel - a tunnel where the gateway is also the endpoint"
 msgstr ""
+"Túnel de 0 saltos - un túnel donde la puerta de salida, gateway, "
+"es también el punto final, endpoint."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:52
 msgid ""
 "1-hop tunnel - a tunnel where the gateway talks directly to the "
 "endpoint"
 msgstr ""
+"Túnel de 1 salto - un túnel donde la puerta de salida habla "
+"directamente con el punto final."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:53
 msgid ""
@@ -20568,6 +16307,9 @@ msgid ""
 "tunnel participant. (the above diagram includes two 2-hop tunnels - one\n"
 "outbound from Alice, one inbound to Bob)"
 msgstr ""
+"Túnel de 2 (o más) saltos - un túnel donde hay al menos un túnel "
+"intermedio participante, (el diagrama de arriba incluye dos túneles de 2 "
+"saltos - uno de salida desde Alice, uno de entrada hacia Bob)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:60
 #, python-format
@@ -20578,10 +16320,14 @@ msgid ""
 "router.\n"
 "Chosen randomly by the tunnel creator."
 msgstr ""
+"ID del túnel - Un entero de 4 bytes "
+"diferente para cada salto en un túnel, y único a lo largo de todos los "
+"túneles en un ruter. Elegido aleatoriamente por el creador del túnel."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:67
 msgid "Tunnel Build Information"
-msgstr ""
+msgstr "Infomación de la construcción del túnel"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:68
 #, python-format
@@ -20592,10 +16338,14 @@ msgid ""
 "Tunnel Build Message\n"
 "to accomplish their tasks:"
 msgstr ""
+"A los ruters con los tres roles (puerta de salida, participante, punto "
+"final) le son dadas diferentes piezas de información en el mensaje de creación de túnel inicial para"
+" poder lleva a cabo sus tareas:"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:75
 msgid "The tunnel gateway gets:"
-msgstr ""
+msgstr "El túnel puerta de salida obtiene:"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:77
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:97
@@ -20606,6 +16356,9 @@ msgid ""
 "encrypting\n"
 "messages and instructions to the next hop"
 msgstr ""
+"Clave de cifrado de túnel - una clave privada AES para "
+"cifrar los mensajes, y las instrucciones para el siguiente salto."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:81
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:101
@@ -20616,6 +16369,9 @@ msgid ""
 "double-encrypting\n"
 "the IV to the next hop"
 msgstr ""
+"Clave IV del túnel - Una clave privada AES para "
+"cifrar doblemente el IV hasta el siguiente salto."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:85
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:105
@@ -20626,6 +16382,9 @@ msgid ""
 "encrypting\n"
 "the reply to the tunnel build request"
 msgstr ""
+"Clave de repuesta - Una clave privada AES para "
+"cifrar la respuesta a la petición de construcción del túnel."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:89
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:109
@@ -20633,37 +16392,44 @@ msgid ""
 "reply IV - the IV for encrypting the reply to the tunnel build "
 "request"
 msgstr ""
+"IV de respuesta - El IV para cifrar la respuesta de la petición de"
+" construcción del túnel."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:90
 msgid "tunnel id - 4 byte integer (inbound gateways only)"
 msgstr ""
+"ID del túnel - In entero de 4 bytes (sólo para las puertas de "
+"salida de entrada)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:91
 msgid ""
 "next hop - what router is the next one in the path (unless this is"
 " a 0-hop tunnel, and the gateway is also the endpoint)"
 msgstr ""
+"Siguiente salto - Cual es el siguiente ruter en el camino (a no "
+"ser que sea un túnel de 0 saltos, y la puerta de salida sea también el "
+"punto final)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:92
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:112
 msgid "next tunnel id - The tunnel ID on the next hop"
-msgstr ""
+msgstr "ID del túnel siguiente - La ID del túnel en el siguiente salto"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:95
 msgid "All intermediate tunnel participants get:"
-msgstr ""
+msgstr "Todos los túneles intermedios participantes obtienen:"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:110
 msgid "tunnel id - 4 byte integer"
-msgstr ""
+msgstr "ID del túnel - Un entero de 4 bytes"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:111
 msgid "next hop - what router is the next one in the path"
-msgstr ""
+msgstr "Siguiente salto - cuál es el siguiente ruter en el camino"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:115
 msgid "The tunnel endpoint gets:"
-msgstr ""
+msgstr "El túnel punto final obtiene:"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:117
 #, python-format
@@ -20673,6 +16439,9 @@ msgid ""
 "encrypting\n"
 "messages and instructions to the the endpoint (itself)"
 msgstr ""
+"Una clave de cifrado de túnel - una clave privada AES para "
+"cifrar los mensajes e instrucciones para el punto final (para sí mismo)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:121
 #, python-format
@@ -20682,6 +16451,9 @@ msgid ""
 "double-encrypting\n"
 "the IV to the endpoint (itself)"
 msgstr ""
+"Una clave IV de túnel -  una clave privada AES para "
+"cifrar dos veces el IV para el punto final (en sí mismo)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:125
 #, python-format
@@ -20691,28 +16463,40 @@ msgid ""
 "encrypting\n"
 "the reply to the tunnel build request (outbound endpoints only)"
 msgstr ""
+"IV de respuesta - una clave privada AES para "
+"cifrar la respuesta para la petición de construcción del túnel (sólo para"
+" los puntos finales de salida)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:129
 msgid ""
 "reply IV - the IV for encrypting the reply to the tunnel build "
 "request (outbound endpoints only)"
 msgstr ""
+"IV de respuesta - el IV para cifrar la respuesta para la petición "
+"de construcción del túnel (sólo para los puntos finales de salida)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:130
 msgid "tunnel id - 4 byte integer (outbound endpoints only)"
 msgstr ""
+"ID del túnel - Un entero de 4 bytes (sólo para los puntos finales "
+"de salida)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:131
 msgid ""
 "reply router - the inbound gateway of the tunnel to send the reply"
 " through (outbound endpoints only)"
 msgstr ""
+"Ruter de respuesta - para enviar la respuesta a través de la "
+"puerta de salida del túnel de entrada (sólo puntos finales de salida)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:132
 msgid ""
 "reply tunnel id - The tunnel ID of the reply router (outbound "
 "endpoints only)"
 msgstr ""
+"ID del túnel de respuesta - El ID del túnel del ruter de respuesta"
+" (sólo para puntos finales de salida)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:137
 #, python-format
@@ -20720,10 +16504,12 @@ msgid ""
 "Details are in the\n"
 "tunnel creation specification."
 msgstr ""
+"Los detalles están en las especificaciones"
+" de creación de túneles."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:142
 msgid "Tunnel pooling"
-msgstr ""
+msgstr "Agrupación de túneles"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:143
 #, python-format
@@ -20736,10 +16522,16 @@ msgid ""
 "The pools used by the router itself are called \"exploratory tunnels\".\n"
 "The pools used by applications are called \"client tunnels\"."
 msgstr ""
+"Varios túneles pueden ser agrupados en un \"grupo de túneles\" para algún"
+" fin en particular como se describe en las especificaciones de túneles. "
+"Los grupos de túneles usados por el ruter mismo se llaman \"túneles "
+"exploratorios\". Los grupos de túneles usados por las aplicaciones se "
+"llaman \"túneles cliente\"."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:154
 msgid "Tunnel length"
-msgstr ""
+msgstr "Tamaño del túnel"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:155
 #, python-format
@@ -20763,10 +16555,26 @@ msgid ""
 "I2CP options.\n"
 "The maximum number of hops in a tunnel is 7."
 msgstr ""
+"Como se menciona arriba, a cada una de los solicitudes de cliente a las \n"
+"que sus routers proporcionan túneles, incluyen al menos un cierto número"
+" \n"
+"de saltos. La decisión acerca del número de routers a tener en los "
+"túneles de entrada y salida del cliente, tiene un efecto importante en la"
+" latencia, la eficiencia, la fiabilidad, y el anonimato proporcionados "
+"por I2P - cuantos \n"
+"más pares (`peers`) tengan que atravesar los mensajes, más tardarán en \n"
+"llegar allí y más probable será que uno de esos routers falle \n"
+"prematuramente. Cuantos menos routers en un túnel, más fácil es para un \n"
+"adversario montar ataques de análisis de tráfico y socavar el anonimato "
+"de \n"
+"alguien. Las longitudes de los túneles se especifican por los clientes a"
+" \n"
+"través de las opciones I2CP. El número \n"
+"máximo de saltos en un túnel es 7."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:171
 msgid "0-hop tunnels"
-msgstr ""
+msgstr "Túneles de 0-saltos"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:172
 msgid ""
@@ -20784,10 +16592,22 @@ msgid ""
 "but could show similar information (though would be slightly harder to "
 "mount)."
 msgstr ""
+"Sin routers remotos en un túnel, el usuario tiene una denegabilidad "
+"plausible \n"
+"muy básica (ya que ninguno de nosotros sabe con seguridad si el par que \n"
+"les envió el mensaje no estaba simplemente reenviándolo al formar parte \n"
+"del túnel). Sin embargo, sería realmente fácil montar un ataque de "
+"análisis \n"
+"estadístico y observar que los mensajes apuntando a un destino específico"
+" siempre son enviados a través de una única pasarela (`gateway`). El "
+"análisis estadístico contra túneles de salida de 0-saltos son más "
+"complejos, pero \n"
+"podrían mostrar una información similar (aunque sería ligeramente más \n"
+"difícil de montar)."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:182
 msgid "1-hop tunnels"
-msgstr ""
+msgstr "Túneles de 1-salto"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:183
 #, python-format
@@ -20803,10 +16623,19 @@ msgid ""
 "be able\n"
 "to mount the above statistical traffic analysis attack."
 msgstr ""
+"Con sólo un router remoto en un túnel, el usuario tiene tanto "
+"denegabilidad plausible como anonimato básico, siempre que no se esté "
+"enfrentando a un adversario interno (como se describe en el modelo de amenaza).\n"
+"Sin embargo, si el adversario está ejecutando un número suficiente de \n"
+"routers de forma que el único router remoto del túnel sea con frecuencia "
+"uno \n"
+"de aquellos comprometidos, será capaz de montar el ataque de análisis \n"
+"estadístico de tráfico descrito anteriormente."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:192
 msgid "2-hop tunnels"
-msgstr ""
+msgstr "Túneles de 2-saltos"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:193
 msgid ""
@@ -20816,10 +16645,14 @@ msgid ""
 "compromised\n"
 "to mount it."
 msgstr ""
+"Con dos o más routers remotos en un túnel, los costes de montar el ataque"
+" \n"
+"de análisis de tráfico aumentan, ya que muchos routers remotos tendrían \n"
+"que estar comprometidos para montarlo."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:199
 msgid "3-hop (or more) tunnels"
-msgstr ""
+msgstr "Túneles de 3 (o más)-saltos"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:200
 #, python-format
@@ -20830,10 +16663,16 @@ msgid ""
 "also conclude that more than 3 hops does not provide additional "
 "protection."
 msgstr ""
+"Para reducir la susceptibilidad a algunos "
+"ataques, se recomiendan \n"
+"3 o más saltos para el mayor nivel de protección. Además, estudios \n"
+"recientes concluyen que más de 3 saltos no proporcionan protección \n"
+"adicional."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:208
 msgid "Tunnel default lengths"
-msgstr ""
+msgstr "Longitudes predeterminadas de los túneles"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:209
 #, python-format
@@ -20843,10 +16682,16 @@ msgid ""
 "I2CP options.\n"
 "Most applications use 2 or 3 hops as their default."
 msgstr ""
+"El router usa túneles de 2-saltos de forma predeterminada para sus \n"
+"túneles exploratorios. Las configuraciones por defecto de los túneles de "
+"cliente son establecidas \n"
+"por la aplicación usando las opciones "
+"I2CP. La mayoría de las aplicaciones usa 2 o 3 saltos como su "
+"configuración por defecto."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:218
 msgid "Tunnel testing"
-msgstr ""
+msgstr "Comprobación de túneles"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:219
 #, python-format
@@ -20862,6 +16707,19 @@ msgid ""
 "capacity rating in the peer "
 "profile."
 msgstr ""
+"Todos los túneles son probados periódicamente por sus creadores \n"
+"mediante la transmisión de un DeliveryStatusMessage (mensaje de estado de"
+" entrega) sobre un túnel de salida, ligado a otro túnel de entrada \n"
+"(probando ambos túneles a la vez). Si falla un número concreto \n"
+"de pruebas consecutivas, se marca como no funcional. Si se usó para un "
+"túnel de entrada de cliente, se crea un nuevo LeaseSet (grupo de túneles "
+"hacia un destino). Además, los fallos en las pruebas de túneles se "
+"reflejan en el ratio de capacidad "
+"en el perfil del par (`peer`)."
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:230
+msgid "Tunnel creation"
+msgstr "Creación de túneles"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:231
 #, python-format
@@ -20879,6 +16737,19 @@ msgid ""
 "Details are in the\n"
 "tunnel creation specification."
 msgstr ""
+"La creación de túneles se realiza mediante el enrutamiento garlic (ajo) \n"
+"de un mensaje de construcción de túnel hacia un router, requiriendole \n"
+"que participe en el túnel (proporcionándole toda la información "
+"necesaria, \n"
+"como la anteriormente descrita, junto con un certificado, que ahora mismo"
+" es un certificado 'null' (vacío), pero que soportará hashcash (un "
+"sistema de \n"
+"prueba de trabajo) u otros certificados no-gratuitos cuando sea "
+"necesario). \n"
+"Ese router reenvía el mensaje al siguiente salto en el túnel. Los "
+"detalles están en las especificaciones de "
+"creación de túneles."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:245
 #, python-format
@@ -20890,6 +16761,14 @@ msgid ""
 "tunnel specification.\n"
 "The IV of each hop is encrypted with a separate key as explained there."
 msgstr ""
+"El cifrado multi-capa es realizado por el cifrado garlic (ajo) de los mensajes de "
+"túnel. Los detalles están en la \n"
+"especificación de túneles. El IV (vector "
+"de \n"
+"inicialización) de cada salto está cifrado con una clave aparte, como se"
+" \n"
+"explica allí."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:257
 msgid ""
@@ -20897,10 +16776,14 @@ msgid ""
 "garlic wrapping a number of tests into cloves, testing individual tunnel\n"
 "participants separately, etc."
 msgstr ""
+"Podrían usarse otras técnicas de evaluación de túneles, tales como la \n"
+"envoltura garlic (`ajo`) de un número de pruebas en forma de dientes \n"
+"(`cloves`, del ajo), comprobando separadamente a los participantes \n"
+"individuales en los túneles, etc."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:263
 msgid "Move to 3-hop exploratory tunnels defaults."
-msgstr ""
+msgstr "Cambiar a configuración predeterminada de túneles de 3-saltos."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:267
 msgid ""
@@ -20908,6 +16791,9 @@ msgid ""
 "options specifying the pooling, mixing, and chaff generation settings may"
 " be implemented."
 msgstr ""
+"En una versión de un futuro lejano, opciones especificando las "
+"configuraciones de depositado, mezclado y generación de datos de relleno "
+"criptográficamente descartables,`chaff,` podrían ser implementadas."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:272
 msgid ""
@@ -20916,30 +16802,42 @@ msgid ""
 "tunnel's lifetime may be implemented (e.g. no more than 300 messages or\n"
 "1MB per minute)."
 msgstr ""
+"En una versión de un futuro lejano, límites en la cantidad y tamaño de "
+"los mensajes permitidos durante la vida del túnel podrían ser "
+"implementados (ej. no más de 300 mensajes o 1 MB por minuto)."
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:284
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:15
 msgid "Tunnel specification"
-msgstr ""
+msgstr "Especificación de túneles"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:286
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:17
 msgid "Tunnel creation specification"
-msgstr ""
+msgstr "Especificación de creación de túneles"
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:288
+msgid "Unidirectional tunnels"
+msgstr "Túneles unidireccionales"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:290
 msgid "Tunnel message specification"
-msgstr ""
+msgstr "Especificación de mensajes de túnel"
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:292
+msgid "Garlic routing"
+msgstr "Garlic routing"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:294
 msgid "ElGamal/AES+SessionTag"
-msgstr ""
+msgstr "ElGamal/AES+SessionTag (etiqueta de sesión)"
 
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:296
 msgid "I2CP options"
 msgstr "Opciones de I2CP"
 
 #: i2p2www/pages/site/docs/protocol/i2cp.html:6
+#, fuzzy
 msgid ""
 "The I2P Client Protocol (I2CP) exposes a strong separation of concerns "
 "between\n"
@@ -20947,10 +16845,8 @@ msgid ""
 "It enables\n"
 "secure and asynchronous messaging by sending and receiving messages over "
 "a \n"
-"single TCP socket, yet never exposing any private keys and authenticating"
-" itself\n"
-"to the router only through signatures.  With I2CP, a client application "
-"tells the\n"
+"single TCP socket.\n"
+"With I2CP, a client application tells the\n"
 "router who they are (their \"destination\"), what anonymity, reliability,"
 " and \n"
 "latency tradeoffs to make, and where to send messages.  In turn the "
@@ -20959,32 +16855,38 @@ msgid ""
 "authorization\n"
 "for some tunnels to be used."
 msgstr ""
+"El Protocolo de Cliente de I2P (I2CP) revela una fuerte separación de \n"
+"intereses entre el router y cualquier cliente que quiera comunicarse a \n"
+"través de la red. Habilita mensajería segura y asíncrona mediante el "
+"envío y \n"
+"recepción de mensajes sobre un único socket TCP, sin exponer nunca clave "
+"privada alguna y autentificándose a si mismo ante el router sólo a través"
+" de \n"
+"firmas. Con I2CP, una aplicación cliente le dice al router quienes son "
+"ellos \n"
+"(su \"destino\"), qué compromisos de equlibrio en anonimato, fiabilidad, "
+"y latencia hacer, y dónde enviar los mensajes. A cambio el router usa "
+"I2CP \n"
+"para decirle al cliente cuándo ha llegado algún mensaje, y para solicitar"
+" \n"
+"autorización para que sean usados algunos túneles."
 
 #: i2p2www/pages/site/docs/protocol/i2cp.html:18
 #, python-format
 msgid ""
-"The protocol itself has only been implemented in Java, to provide the\n"
+"The protocol itself is implemented in Java, to provide the\n"
 "Client SDK.\n"
 "This SDK is exposed in the i2p.jar package, which implements the client-"
 "side of I2CP.\n"
 "Clients should never need to access the router.jar package, which "
 "contains the\n"
-"router itself and the router-side of I2CP."
+"router itself and the router-side of I2CP.\n"
+"There is also a C library implementation.\n"
+"A non-Java client would also have to implement the\n"
+"streaming library for TCP-style connections."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:26
-#, python-format
-msgid ""
-"While implementing the client side of I2CP in a non-Java language is "
-"certainly feasible,\n"
-"a non-Java client would also have to implement the\n"
-"streaming library for TCP-style "
-"connections.\n"
-"Together, implementing I2CP and the streaming library would be a sizable "
-"task."
-msgstr ""
-
-#: i2p2www/pages/site/docs/protocol/i2cp.html:33
+#: i2p2www/pages/site/docs/protocol/i2cp.html:31
 #, python-format
 msgid ""
 "Applications can take advantage of the base I2CP plus the \n"
@@ -20999,8 +16901,19 @@ msgid ""
 "ministreaming.jar and streaming.jar.\n"
 "So there are several options for both Java and non-Java applications."
 msgstr ""
+"Las aplicaciones pueden aprovecharse de la base I2CP además de las \n"
+"librerías streaming y datagram mediante el uso de \n"
+"los protocolos Mensajería Anónima Simple (SAM) o "
+"BOB, que \n"
+"no requieren clientes para tratar con cualquier clase de criptografía. \n"
+"Además, los clientes pueden acceder a la red por uno de los varios proxys"
+" - HTTP, CONNECT, y SOCKS 4/4a/5. A modo de alternativa, los clientes "
+"Java pueden acceder a esas librerías en ministreaming.jar y "
+"streaming.jar. \n"
+"Así que hay varias opciones para aplicaciones tanto Java como no-Java."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:45
+#: i2p2www/pages/site/docs/protocol/i2cp.html:43
 #, python-format
 msgid ""
 "Client-side end-to-end encryption (encrypting the data over the I2CP "
@@ -21015,8 +16928,23 @@ msgid ""
 "Session Configurations, and"
 " management of those keys."
 msgstr ""
+"El cifrado extremo-a-extremo del lado-del-cliente (cifrando los datos "
+"sobre la \n"
+"conexión I2CP) fue deshabilitado en la versión 0.6 de I2P, dejando en su"
+" \n"
+"lugar un cifrado extremo-a-extremo "
+"ElGamal/AES que \n"
+"está implementado en el router. La única criptografía que las librerías "
+"del \n"
+"cliente todavía deben implementar es la firma de la clave publico/privada \n"
+"DSA (algoritmo de firma digital) para LeaseSets (grupo de túneles \n"
+"para un destino) y Configuraciones de sesión, y "
+"la gestión de esas claves."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:58
+#: i2p2www/pages/site/docs/protocol/i2cp.html:56
 msgid ""
 "In a standard I2P installation, port 7654 is used by external java "
 "clients to communicate\n"
@@ -21029,21 +16957,47 @@ msgid ""
 "router\n"
 "through an internal JVM interface."
 msgstr ""
+"En una instalación I2P estándar, el puerto 7654 es usado por clientes de "
+"Java \n"
+"externos para comunicarse con el router local vía I2CP. Por defecto, el "
+"router\n"
+"se liga a la dirección 127.0.0.1. Para ligarse a 0.0.0.0, establezca la "
+"opción \n"
+"de la configuración avanzada del router "
+"i2cp.tcp.bindAllInterfaces=true \n"
+"y reinicie. Los clientes en la misma JVM (Máquina Virtual Java), pasan "
+"los \n"
+"mensajes directamente al router a través de una interfaz JVM interna."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:67
-msgid "I2CP Protocol Specification"
+#: i2p2www/pages/site/docs/protocol/i2cp.html:65
+#, python-format
+msgid ""
+"The router also supports external connections over SSL.\n"
+"While SSL is not the default, it is strongly recommended for any traffic "
+"that may\n"
+"be exposed to the open Internet. The authorization user/password (if "
+"any), the\n"
+"Private Key and\n"
+"Signing Private "
+"Key for the\n"
+"Destination\n"
+"are all transmitted in-the-clear unless SSL is enabled."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:68
+#: i2p2www/pages/site/docs/protocol/i2cp.html:75
+msgid "I2CP Protocol Specification"
+msgstr "Especificación del protocolo I2CP"
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:76
 #, python-format
 msgid "Now on the I2CP Specification page."
-msgstr ""
+msgstr "Ahora sobre la página de la Especificación I2CP."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:73
+#: i2p2www/pages/site/docs/protocol/i2cp.html:81
 msgid "I2CP Initialization"
-msgstr ""
+msgstr "Inicialización I2CP"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:74
+#: i2p2www/pages/site/docs/protocol/i2cp.html:82
 #, python-format
 msgid ""
 "When a client connects to the router, it first sends a single protocol "
@@ -21060,12 +17014,27 @@ msgid ""
 "The client may now initiate or receive connections from other I2P "
 "destinations."
 msgstr ""
+"Cuando un cliente conecta con el router, primero envía un único byte de \n"
+"versión de protocolo (0x2A). Entonces envía un mensaje GetDate \n"
+"(obtener fecha) y espera la respuesta del mensaje SetDate (configurar fecha). \n"
+"A continuación, envía un mensaje "
+"CreateSession (crear sesión) \n"
+"conteniendo la sesión de configuración. Seguidamente espera un \n"
+"RequestLeaseSet Message "
+"(mensaje de solicitud de LeaseSet) desde \n"
+"el router, indicando que los túneles de entrada han sido erigidos y \n"
+"responden con un CreateLeaseSetMessage (mensaje de creación de \n"
+"LeaseSet) conteniendo el LeaseSet firmado. El cliente puede ahora iniciar"
+" \n"
+"o recibir conexiones desde otros destinos I2P."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:83
+#: i2p2www/pages/site/docs/protocol/i2cp.html:91
 msgid "I2CP Options"
 msgstr "Opciones de I2CP"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:84
+#: i2p2www/pages/site/docs/protocol/i2cp.html:92
 #, python-format
 msgid ""
 "The following options are traditionally passed to the router via\n"
@@ -21074,55 +17043,63 @@ msgid ""
 "a ReconfigureSession "
 "Message."
 msgstr ""
+"Las siguientes opciones se pasan tradicionalmente al router a través de "
+"un \n"
+"SessionConfig "
+"(configuración de la sesión) contenida en \n"
+"un mensaje CreateSession "
+"(crear sesión) o un \n"
+"Mensaje "
+"ReconfigureSession (reconfiguración de sesión)."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:90
+#: i2p2www/pages/site/docs/protocol/i2cp.html:98
 msgid "Router-side Options"
-msgstr ""
+msgstr "Opciones del lado-del-router"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:95
-#: i2p2www/pages/site/docs/protocol/i2cp.html:438
+#: i2p2www/pages/site/docs/protocol/i2cp.html:103
+#: i2p2www/pages/site/docs/protocol/i2cp.html:446
 msgid "As Of Release"
-msgstr ""
+msgstr "Desde la versión"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:96
-#: i2p2www/pages/site/docs/protocol/i2cp.html:439
+#: i2p2www/pages/site/docs/protocol/i2cp.html:104
+#: i2p2www/pages/site/docs/protocol/i2cp.html:447
 msgid "Recommended Arguments"
-msgstr ""
-
-#: i2p2www/pages/site/docs/protocol/i2cp.html:97
-#: i2p2www/pages/site/docs/protocol/i2cp.html:440
-msgid "Allowable Range"
-msgstr ""
+msgstr "Parámetros recomendados"
 
 #: i2p2www/pages/site/docs/protocol/i2cp.html:105
-#: i2p2www/pages/site/docs/protocol/i2cp.html:118
-#: i2p2www/pages/site/docs/protocol/i2cp.html:127
-#: i2p2www/pages/site/docs/protocol/i2cp.html:136
-#: i2p2www/pages/site/docs/protocol/i2cp.html:145
-#: i2p2www/pages/site/docs/protocol/i2cp.html:160
-#: i2p2www/pages/site/docs/protocol/i2cp.html:175
-#: i2p2www/pages/site/docs/protocol/i2cp.html:184
-#: i2p2www/pages/site/docs/protocol/i2cp.html:232
-#: i2p2www/pages/site/docs/protocol/i2cp.html:244
-#: i2p2www/pages/site/docs/protocol/i2cp.html:256
+#: i2p2www/pages/site/docs/protocol/i2cp.html:448
+msgid "Allowable Range"
+msgstr "Rango permitido"
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:113
+#: i2p2www/pages/site/docs/protocol/i2cp.html:126
+#: i2p2www/pages/site/docs/protocol/i2cp.html:135
+#: i2p2www/pages/site/docs/protocol/i2cp.html:144
+#: i2p2www/pages/site/docs/protocol/i2cp.html:153
+#: i2p2www/pages/site/docs/protocol/i2cp.html:168
+#: i2p2www/pages/site/docs/protocol/i2cp.html:183
+#: i2p2www/pages/site/docs/protocol/i2cp.html:192
+#: i2p2www/pages/site/docs/protocol/i2cp.html:240
+#: i2p2www/pages/site/docs/protocol/i2cp.html:252
+#: i2p2www/pages/site/docs/protocol/i2cp.html:264
 #, python-format
 msgid "number from %(from)s to %(to)s"
-msgstr ""
+msgstr "número desde %(from)s hasta %(to)s"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:106
-#: i2p2www/pages/site/docs/protocol/i2cp.html:128
-#: i2p2www/pages/site/docs/protocol/i2cp.html:137
-#: i2p2www/pages/site/docs/protocol/i2cp.html:146
-#: i2p2www/pages/site/docs/protocol/i2cp.html:161
-#: i2p2www/pages/site/docs/protocol/i2cp.html:233
-#: i2p2www/pages/site/docs/protocol/i2cp.html:245
-#: i2p2www/pages/site/docs/protocol/i2cp.html:257
-#: i2p2www/pages/site/docs/protocol/i2cp.html:530
+#: i2p2www/pages/site/docs/protocol/i2cp.html:114
+#: i2p2www/pages/site/docs/protocol/i2cp.html:136
+#: i2p2www/pages/site/docs/protocol/i2cp.html:145
+#: i2p2www/pages/site/docs/protocol/i2cp.html:154
+#: i2p2www/pages/site/docs/protocol/i2cp.html:169
+#: i2p2www/pages/site/docs/protocol/i2cp.html:241
+#: i2p2www/pages/site/docs/protocol/i2cp.html:253
+#: i2p2www/pages/site/docs/protocol/i2cp.html:265
+#: i2p2www/pages/site/docs/protocol/i2cp.html:538
 #, python-format
 msgid "%(from)s to %(to)s"
 msgstr "%(from)s a %(to)s"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:108
+#: i2p2www/pages/site/docs/protocol/i2cp.html:116
 msgid ""
 "Number of tunnels in.\n"
 "Limit was increased from 6 to 16 in release 0.9; however, numbers higher "
@@ -21130,26 +17107,30 @@ msgid ""
 "currently recommended, as this is untested and is incompatible with older"
 " releases."
 msgstr ""
+"Número de túneles dentro. El límite fue aumentado desde 6 a 16 en la \n"
+"versión 0.9; sin embargo, los números mayores de 6 actualmente no están "
+"recomendados ya que esto no está comprobado y es incompatible con \n"
+"versiones más antiguas."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:119
-#: i2p2www/pages/site/docs/protocol/i2cp.html:176
-#: i2p2www/pages/site/docs/protocol/i2cp.html:185
+#: i2p2www/pages/site/docs/protocol/i2cp.html:127
+#: i2p2www/pages/site/docs/protocol/i2cp.html:184
+#: i2p2www/pages/site/docs/protocol/i2cp.html:193
 msgid "No limit"
 msgstr "Sin límite"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:121
+#: i2p2www/pages/site/docs/protocol/i2cp.html:129
 msgid "Number of tunnels out"
-msgstr ""
+msgstr "Número de túneles hacia fuera"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:130
+#: i2p2www/pages/site/docs/protocol/i2cp.html:138
 msgid "Length of tunnels in"
-msgstr ""
+msgstr "Longitud de túneles de entrada."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:139
+#: i2p2www/pages/site/docs/protocol/i2cp.html:147
 msgid "Length of tunnels out"
-msgstr ""
+msgstr "Longitud de túneles de salida.."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:148
+#: i2p2www/pages/site/docs/protocol/i2cp.html:156
 msgid ""
 "Random amount to add or subtract to the length of tunnels in.\n"
 "A positive number x means add a random amount from 0 to x inclusive.\n"
@@ -21158,8 +17139,17 @@ msgid ""
 "\n"
 "The default variance was 1 prior to release 0.7.6."
 msgstr ""
+"Cantidad aleatoria a añadir o sustraer a la longitud de los túneles "
+"entrantes. \n"
+"Un número positivo significa añadir una cantidad aletoria de 0 a x ambos"
+" \n"
+"incluidos. Un número negativo -x significa añadir una cantidad aleatoria "
+"de \n"
+"-x a x ambos incluidos. El router limitará la longitud total del túnel de"
+" 0 a 7 \n"
+"ambos incluidos. La varianza por defecto era 1 antes de la versión 0.7.6."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:163
+#: i2p2www/pages/site/docs/protocol/i2cp.html:171
 msgid ""
 "Random amount to add or subtract to the length of tunnels out.\n"
 "A positive number x means add a random amount from 0 to x inclusive.\n"
@@ -21168,93 +17158,138 @@ msgid ""
 "\n"
 "The default variance was 1 prior to release 0.7.6."
 msgstr ""
+"Cantidad aleatoria a añadir o sustraer a la longitud de los túneles "
+"salientes. \n"
+"Un número positivo x significa añadir una cantidad aleatoria de 0 a x "
+"ambos \n"
+"incluidos. Un número negativo -x significa añadir una cantidad de -x a x"
+" \n"
+"ambos incluidos. El router limitará la longitud total del túnel de 0 a 7 "
+"ambos \n"
+"incluidos. La varianza por defecto era 1 antes de la versión 0.7.6."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:178
+#: i2p2www/pages/site/docs/protocol/i2cp.html:186
 msgid "Number of redundant fail-over for tunnels in"
 msgstr ""
+"Número de túneles de respaldo (`fail-over`) redundantes para túneles "
+"entrantes"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:187
+#: i2p2www/pages/site/docs/protocol/i2cp.html:195
 msgid "Number of redundant fail-over for tunnels out"
 msgstr ""
+"Número de túneles de respaldo (`fail-over`) redundantes para túneles "
+"salientes"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:196
+#: i2p2www/pages/site/docs/protocol/i2cp.html:204
 msgid ""
 "Name of tunnel - generally used in routerconsole, which will\n"
 "use the first few characters of the Base64 hash of the destination by "
 "default."
 msgstr ""
+"Nombre del túnel - usado por lo general en routerconsole, que usara los \n"
+"primeros pocos caracteres del identificador criptográfico (`hash`) Base64"
+" del \n"
+"destino por defecto."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:208
+#: i2p2www/pages/site/docs/protocol/i2cp.html:216
 msgid "Name of tunnel - generally ignored unless inbound.nickname is unset."
 msgstr ""
+"Nombre del túnel - ignorado por lo general a menos que inbound.nickname "
+"(apodo entrante) no esté establecido."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:217
+#: i2p2www/pages/site/docs/protocol/i2cp.html:225
 msgid "If incoming zero hop tunnel is allowed"
-msgstr ""
+msgstr "Si es de entrada están permitidos los túneles de cero saltos"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:226
+#: i2p2www/pages/site/docs/protocol/i2cp.html:234
 msgid "If outgoing zero hop tunnel is allowed"
-msgstr ""
+msgstr "Si es de salida están permitidos los túneles de cero saltos"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:235
-#: i2p2www/pages/site/docs/protocol/i2cp.html:247
+#: i2p2www/pages/site/docs/protocol/i2cp.html:243
+#: i2p2www/pages/site/docs/protocol/i2cp.html:255
 msgid ""
 "Number of IP bytes to match to determine if\n"
 "two routers should not be in the same tunnel. 0 to disable."
 msgstr ""
+"El número de bytes de la IP para comparar y determinar si los dos ruters "
+"están en el mismo túnel. 0 para deshabilitarlo"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:259
+#: i2p2www/pages/site/docs/protocol/i2cp.html:267
 msgid ""
 "Priority adjustment for outbound messages.\n"
 "Higher is higher priority."
 msgstr ""
+"Ajustes de prioridades para los mensajes de salida. Más alto indica más "
+"prioridad."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:271
+#: i2p2www/pages/site/docs/protocol/i2cp.html:279
 msgid "Should generally be set to true for clients and false for servers"
 msgstr ""
+"Generalmente suele ser verdadero para los clientes y falso para los "
+"servidores"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:280
+#: i2p2www/pages/site/docs/protocol/i2cp.html:288
 msgid ""
 "Guaranteed is disabled;\n"
 "None implemented in 0.8.1; the streaming lib default is None as of 0.8.1,"
 " the client side default is None as of 0.9.4"
 msgstr ""
+"Asegurarse de que está desactivado; None fue implementado en 0.8.1; la "
+"librería de straming por defecto es None como en 0.8.1, la parte cliente "
+"es None como en 0.9.4"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:292
-#: i2p2www/pages/site/docs/protocol/i2cp.html:571
+#: i2p2www/pages/site/docs/protocol/i2cp.html:300
+#: i2p2www/pages/site/docs/protocol/i2cp.html:579
 msgid ""
 "If true, the router just sends the MessagePayload instead\n"
 "of sending a MessageStatus and awaiting a ReceiveMessageBegin."
 msgstr ""
+"Si es verdadero, el ruter simplemente envía el MessagePayload, en  lugar "
+"de enviar MessageStatus y esperar por un ReceiveMessageBegin."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:304
+#: i2p2www/pages/site/docs/protocol/i2cp.html:312
 msgid ""
 "Comma-separated list of Base 64 Hashes of peers to build tunnels through;"
 " for debugging only"
 msgstr ""
+"Lista separada por comas de los Hashes Base 64 de los pares con los que "
+"construir túneles para pasar a través; sólo para depuración"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:313
-#: i2p2www/pages/site/docs/protocol/i2cp.html:325
+#: i2p2www/pages/site/docs/protocol/i2cp.html:321
 msgid ""
 "For authorization, if required by the router.\n"
 "If the client is running in the same JVM as a router, this option is not "
-"required."
+"required.\n"
+"Warning - username and password are sent in the clear to the router, "
+"unless using SSL (i2cp.SSL=true).\n"
+"Authorization is only recommended when using SSL."
 msgstr ""
+"Para la autorización, si es requerida por el router.\n"
+"Si el cliente está ejecutandose en la misma JVM (máquina virtual Java) "
+"que el router, no se requiere esta opción.\n"
+"Advertencia - el nombre de usuario y la contraseña se envían en claro al "
+"router, a menos que se use SSL (i2cp.SSL=true).\n"
+"La autorización sólo está recomendada cuando se usa SSL."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:337
+#: i2p2www/pages/site/docs/protocol/i2cp.html:343
 msgid ""
 "Number of ElGamal/AES Session Tags to send at a time.\n"
 "For clients with relatively low bandwidth per-client-pair (IRC, some UDP "
 "apps), this may be set lower."
 msgstr ""
+"Número de etiquetas de sesión ElGamal/AES para enviar de golpe. Para los "
+"clientes con anchos de baja relativamente bajos para el par cliente (IRC,"
+" algunas aplicaciones UDP), esto valor puede ser más bajo."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:349
+#: i2p2www/pages/site/docs/protocol/i2cp.html:355
 msgid ""
 "Minimum number of ElGamal/AES Session Tags before we send more.\n"
 "Recommended: approximately tagsToSend * 2/3"
 msgstr ""
+"Número mínimo de etiquetas de sesión ElGamal/AES antes de que enviemos "
+"más. Recomendado: aproximadamente 'tagsToSend * 2/3'"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:361
+#: i2p2www/pages/site/docs/protocol/i2cp.html:367
 msgid ""
 "Set to false to disable ever bundling a reply LeaseSet.\n"
 "For clients that do not publish their LeaseSet, this option must be true\n"
@@ -21262,8 +17297,13 @@ msgid ""
 " servers\n"
 "with long connection times."
 msgstr ""
+"Poner como falso para que nunca se construya una LeaseSet de respuesta . "
+"Para los clientes que no publican sus LeaseSet , esta opción tiene que "
+"ser verdadera para que las repuestas sean posibles. Se recomienda también"
+" usar \"true\", verdadero, para los servidores multi-hospedados con "
+"tiempos de conexión largos."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:368
+#: i2p2www/pages/site/docs/protocol/i2cp.html:374
 msgid ""
 "Setting to \"false\" may save significant outbound bandwidth, especially "
 "if\n"
@@ -21273,16 +17313,21 @@ msgid ""
 "the far-end client and the floodfill.\n"
 "There are several cases where \"false\" may be appropriate:"
 msgstr ""
+"Poniéndolo en \"false\", falso, puede ahorrar bastante ancho de banda de "
+"salida, especialmente si el cliente está configurado para usar un gran "
+"número de túneles de entrada (Leases). Si las respuestas son aún "
+"necesarias, esto puede cambiar la carga a el cliente más lejano final y "
+"en el floodfill. Hay varios casos donde \"false\" podría ser apropiado:"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:376
+#: i2p2www/pages/site/docs/protocol/i2cp.html:382
 msgid "Unidirectional communication, no reply required"
-msgstr ""
+msgstr "Dirección unidireccional, no se necesita respuesta"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:377
+#: i2p2www/pages/site/docs/protocol/i2cp.html:383
 msgid "LeaseSet is published and higher reply latency is acceptable"
-msgstr ""
+msgstr "El LeaseSet está publicado y un latencia de respuesta mayor es aceptable"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:378
+#: i2p2www/pages/site/docs/protocol/i2cp.html:384
 msgid ""
 "LeaseSet is published, client is a \"server\", all connections are "
 "inbound\n"
@@ -21295,36 +17340,62 @@ msgid ""
 "after expiration.\n"
 "HTTP servers may fit these requirements."
 msgstr ""
+"El LeaseSet está publicado, el cliente es un \"servidor\", todas las "
+"conexiones son de entrada, por lo que la destinación lejana que se está "
+"conectanda ya tiene el leaseset, obviamente. Las conexiones o son cortas,"
+" o son aceptables para la latencia o conexiones de larga duración para "
+"incrementar temporalmente mientras que la otra descarga de nuevo el "
+"LeaseSet después de expirar. Los servidores HTTP puede encajar en estos "
+"requerimientos."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:396
+#: i2p2www/pages/site/docs/protocol/i2cp.html:402
 msgid ""
 "Any other options prefixed with \"inbound.\" are stored\n"
 "in the \"unknown options\" properties of the inbound tunnel pool's "
 "settings."
 msgstr ""
+"Cualquier otra opción con el prefijo \"inbound\" es almacenada en las "
+"\"opciones desconocidas\" del grupo de configuraciones del túnel de "
+"entrada."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:408
+#: i2p2www/pages/site/docs/protocol/i2cp.html:414
 msgid ""
 "Any other options prefixed with \"outbound.\" are stored\n"
 "in the \"unknown options\" properties of the outbound tunnel pool's "
 "settings."
 msgstr ""
+"Cualquier otra opción con el prefijo \"outbound\" es almacenada en las "
+"\"opciones desconocidas\" del grupo de configuraciones del túnel de "
+"salida."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:415
+#: i2p2www/pages/site/docs/protocol/i2cp.html:421
 msgid ""
 "Note: Large quantity, length, or variance settings may cause significant "
 "performance or reliability problems."
 msgstr ""
+"Nota: Una gran cantidad de configuraciones, el tamaño o variaciones en "
+"las configuraciones pueden causar bastantes problemas en el rendimiento o"
+" en la seguridad."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:419
+#: i2p2www/pages/site/docs/protocol/i2cp.html:425
+#, fuzzy, python-format
 msgid ""
 "Note: As of release 0.7.7, option names and values must use UTF-8 "
 "encoding.\n"
 "This is primarily useful for nicknames.\n"
 "Prior to that release, options with multi-byte characters were corrupted."
+"\n"
+"Since options are encoded in a Mapping,\n"
+"all option names and values are limited to 255 bytes (not characters) "
+"maximum."
 msgstr ""
+"Nota: A partir de la versión 0.7.7, los nombres de opciones y los valores"
+" tienen que usar UTF-8. Esto es útil principalmente  para los apodos. "
+"Antes de esa versión, las opciones con caracteres multi-byte estaban "
+"corruptas."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:425
+#: i2p2www/pages/site/docs/protocol/i2cp.html:433
 msgid ""
 "The following options are interpreted on the client side,\n"
 "and will be interpreted if passed to the I2PSession via the "
@@ -21332,89 +17403,114 @@ msgid ""
 "The streaming lib should also pass these options through to I2CP.\n"
 "Other implementations may have different defaults."
 msgstr ""
+"Las siguientes opciones son interpretadas por la parte cliente, y serán "
+"interpretadas si pasan a la I2PSession a través de la llamada "
+"I2PClient.createSession(). La librería de streaming también debería pasar"
+" estas opciones a través de I2CP. Otras implementaciones pueden tener "
+"otros valores por defecto."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:433
+#: i2p2www/pages/site/docs/protocol/i2cp.html:441
 msgid "Client-side Options"
-msgstr ""
+msgstr "Opciones de la parte cliente"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:451
+#: i2p2www/pages/site/docs/protocol/i2cp.html:459
 msgid ""
 "Router hostname.\n"
 "If the client is running in the same JVM as a router, this option is "
 "ignored, and the client connects to that router internally."
 msgstr ""
+"Hostname del ruter. Si el cliente se ejecuta en la misma JVM como un "
+"ruter, esta opción es ignorada, y el cliente se conecta al ruter "
+"internamente."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:463
+#: i2p2www/pages/site/docs/protocol/i2cp.html:471
 msgid ""
 "Router I2CP port.\n"
 "If the client is running in the same JVM as a router, this option is "
 "ignored, and the client connects to that router internally."
 msgstr ""
+"Puerto I2CP del ruter. Si el cliente se ejecuta en la misma JVM como un "
+"ruter, esta opción es ignorada, y el cliente se conecta al ruter "
+"internamente."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:475
+#: i2p2www/pages/site/docs/protocol/i2cp.html:483
 msgid ""
 "Connect to the router using SSL.\n"
 "If the client is running in the same JVM as a router, this option is "
 "ignored, and the client connects to that router internally."
 msgstr ""
+"Conectar con el ruter usando SSL. Si el cliente se está ejecutando en la "
+"misma JVM que el ruter esta opción es ignorada, y el cliente conecta con "
+"el ruter internamente."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:487
+#: i2p2www/pages/site/docs/protocol/i2cp.html:495
 msgid "Gzip outbound data"
-msgstr ""
+msgstr "Gzip los datos de salida"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:496
+#: i2p2www/pages/site/docs/protocol/i2cp.html:504
 msgid "Reduce tunnel quantity when idle"
-msgstr ""
+msgstr "Reducir la cantidad de túneles cuando está inactivo"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:505
+#: i2p2www/pages/site/docs/protocol/i2cp.html:513
 msgid "Close I2P session when idle"
-msgstr ""
+msgstr "Cerrar las sesiones I2P cuando esté inactivo"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:512
-#: i2p2www/pages/site/docs/protocol/i2cp.html:521
+#: i2p2www/pages/site/docs/protocol/i2cp.html:520
+#: i2p2www/pages/site/docs/protocol/i2cp.html:529
 #, python-format
 msgid "%(num)s minimum"
-msgstr ""
+msgstr "mínimo %(num)s"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:514
+#: i2p2www/pages/site/docs/protocol/i2cp.html:522
 msgid "(ms) Idle time required (default 20 minutes, minimum 5 minutes)"
 msgstr ""
+"(ms) el tienpo inactivo requerido (por defecto 20 minutos, mínimo 5 "
+"minutos)"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:523
+#: i2p2www/pages/site/docs/protocol/i2cp.html:531
 msgid "(ms) Idle time required (default 30 minutes)"
-msgstr ""
+msgstr "(ms) tiempo inactivo requerido (por defecto 30 minutos)"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:532
+#: i2p2www/pages/site/docs/protocol/i2cp.html:540
 msgid "Tunnel quantity when reduced (applies to both inbound and outbound)"
 msgstr ""
+"Cantidad de túneles cuando se reduce el número (se aplica tanto a los de "
+"entrada como a los de salida)"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:541
+#: i2p2www/pages/site/docs/protocol/i2cp.html:549
 msgid "Encrypt the lease"
-msgstr ""
+msgstr "Cifrar el lease"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:550
+#: i2p2www/pages/site/docs/protocol/i2cp.html:558
 msgid "Base64 SessionKey (44 characters)"
-msgstr ""
+msgstr "Clave de sesión Base64 (44 caracteres)"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:559
+#: i2p2www/pages/site/docs/protocol/i2cp.html:567
 msgid ""
 "Guaranteed is disabled;\n"
 "None implemented in 0.8.1; None is the default as of 0.9.4"
 msgstr ""
+"Asegurarse de que está desactivado; None fue implementado en 0.8.1; None "
+"es el valor por defecto en 0.9.4"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:578
+#: i2p2www/pages/site/docs/protocol/i2cp.html:586
 msgid ""
 "Note: All arguments, including numbers, are strings. True/false values "
 "are case-insensitive strings.\n"
 "Anything other than case-insensitive \"true\" is interpreted as false.\n"
 "All option names are case-sensitive."
 msgstr ""
+"Nota: todos los argumentos, incluyendo los números, son cadenas de "
+"caracteres. Los valores True/false son cadenas de caracteres  y son "
+"sensibles a las mayúsculas o minúsculas. Cualquier otro que no sea "
+"\"true\" en minúsculas será interpretado como falso. Todas los nombres de"
+" opciones son sensibles a las mayúsculas/minúsculas."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:584
+#: i2p2www/pages/site/docs/protocol/i2cp.html:592
 msgid "I2CP Payload Data Format and Multiplexing"
-msgstr ""
+msgstr "Formato de los datos del payload I2CP y de Multiplexing"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:585
+#: i2p2www/pages/site/docs/protocol/i2cp.html:593
 #, python-format
 msgid ""
 "The end-to-end messages handled by I2CP (i.e. the data sent by the client"
@@ -21434,75 +17530,93 @@ msgid ""
 "datagrams\n"
 "to work reliably in the presence of multiple channels."
 msgstr ""
+"El mensaje de fin a fin manejado por I2CP (por ejemplo los dato enviados "
+"por el cliente en el SendMessageMessage y recibido por "
+"el cliente en un MessagePayloadMessage) están "
+"comprimidos con gzip con una cabecera de inicio de 10 bytes con  0x1F "
+"0x8B 0x08 como se especifica en el RFC 1952. A partir de la"
+" versión 0.7.1, I2P usa partes ignoradas de la cabecera gzip para incluir"
+" el protocolo, el puerto desde, y la información del puerto hacia, con lo"
+" que se soporta streamings y datagramas en la misma destinación, y "
+"permite peticiones/respuestas usando datagramas para trabajar de forma "
+"segura en presencia de múltiples canales."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:599
+#: i2p2www/pages/site/docs/protocol/i2cp.html:607
 msgid ""
 "The gzip function cannot be completely turned off, however setting "
 "i2cp.gzip=false\n"
 "turns the gzip effort setting to 0, which may save a little CPU."
 msgstr ""
+"La función gzip puede apagarse completamente, aunque si se pone la opción"
+" i2cp.gzip=false, se cambia el valor de esfuerzo de gzip a 0, lo que "
+"puede ahorrar un poco de CPU."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:605
+#: i2p2www/pages/site/docs/protocol/i2cp.html:613
 #: i2p2www/pages/site/docs/protocol/i2np.html:33
 msgid "Bytes"
 msgstr "Bytes"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:606
-#: i2p2www/pages/site/get-involved/index.html:38
+#: i2p2www/pages/site/docs/protocol/i2cp.html:614
 msgid "Content"
 msgstr "Contenido"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:611
+#: i2p2www/pages/site/docs/protocol/i2cp.html:619
 msgid "Gzip header"
 msgstr "Cabecera gzip"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:616
+#: i2p2www/pages/site/docs/protocol/i2cp.html:624
 msgid "Gzip flags"
 msgstr "Opciones de gzip"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:621
+#: i2p2www/pages/site/docs/protocol/i2cp.html:629
 msgid "I2P Source port (Gzip mtime)"
-msgstr ""
+msgstr "Puerto de origen I2P (mtime de Gzip)"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:626
+#: i2p2www/pages/site/docs/protocol/i2cp.html:634
 msgid "I2P Destination port (Gzip mtime)"
-msgstr ""
+msgstr "Puerto de destino de I2p (mtime de Gzip)"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:631
+#: i2p2www/pages/site/docs/protocol/i2cp.html:639
 msgid "Gzip xflags"
-msgstr ""
+msgstr "Zflags de Gzip"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:636
+#: i2p2www/pages/site/docs/protocol/i2cp.html:644
 msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)"
 msgstr ""
+"Protocolo I2P (6= Streaming, 17 = Datagram, 18 = Raw Datagrams) (OS de "
+"Gzip)"
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:640
+#: i2p2www/pages/site/docs/protocol/i2cp.html:648
 msgid ""
 "Data integrity is verified with the standard gzip CRC-32 as\n"
 "specified by RFC 1952."
 msgstr ""
-
-#: i2p2www/pages/site/docs/protocol/i2cp.html:648
-msgid "Implement I2CP and the streaming library in another programming language."
-msgstr ""
-
-#: i2p2www/pages/site/docs/protocol/i2cp.html:652
-msgid "Is the initial Get Date / Set Date handshake required?"
-msgstr ""
+"La integridad de los datos es verificada con el estándar gzip CRC-32 como"
+" es especificado por el RFC 1952."
 
 #: i2p2www/pages/site/docs/protocol/i2cp.html:656
 msgid ""
 "The current authorization mechanism could be modified to use hashed "
 "passwords."
 msgstr ""
+"El mecanismo actual de autorización puede modificarse para usar "
+"contraseñas 'hashed'."
 
 #: i2p2www/pages/site/docs/protocol/i2cp.html:660
+#, fuzzy
 msgid ""
-"Private Keys are included in the Create Lease Set message,\n"
-"are they really required? Revocation is unimplemented."
+"The Signing Private Keys is included in the Create Lease Set message,\n"
+"it is not required. Revocation is unimplemented.\n"
+"It should be replaced with random data or removed."
 msgstr ""
+"Las claves privadas están incluidas en el mensaje Create Lease Set, ¿son "
+"requeridos de verdad? La revocación está implementada."
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:665
+#: i2p2www/pages/site/docs/protocol/i2cp.html:666
 #, python-format
 msgid ""
 "Some improvements may be able to use messages previously defined but not "
@@ -21513,6 +17627,16 @@ msgid ""
 "That document also references the\n"
 "Common Data Structures Specification Version 0.9."
 msgstr ""
+"Algunas mejoras pueden ser capaces de usar los mensajes previamente "
+"definidos pero no implementados. Para más referencias, aquí está la especificación del protocolo 2CP versión 0.9 (PDF),"
+" del 28 de Agosto del 2003. Este documento también hace referencia al Especificación de las estructuras de datos comunes , "
+"Common Data Structures Specification, Versión 0.9. "
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:3
+msgid "June 2013"
+msgstr "Junio de 2013"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:6
 msgid "I2P Network Protocol"
@@ -21529,6 +17653,11 @@ msgid ""
 "multiple\n"
 "common transports supported."
 msgstr ""
+"El protocolo de red de I2P (I2NP), el cual está intercalado entre I2CP \n"
+"(Protocolo de Cliente I2P) y los diferentes protocolos de transporte I2P,"
+" administra el enrutado y mezclado de los mensajes entre routers, así "
+"como la seleccion de qué transportes se usan cuando se comunica con un "
+"par (`peer`) para el que hay múltiples transportes comunes soportados."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:15
 msgid "I2NP Definition"
@@ -21544,6 +17673,12 @@ msgid ""
 "Priority is only used locally at the origin, i.e. when queuing for "
 "outbound delivery."
 msgstr ""
+"Los mensajes I2PN (Protocolo de red I2P) pueden usarse para los mensajes "
+"punto a punto, router a router, de un solo salto. Al cifrar y envolver "
+"los mensajes dentro de otros mensajes, pueden ser enviados de forma "
+"segura a través de múltiples saltos hasta el destino final. Las "
+"prioridades sólo se usan localmente, en el origen, es decir cuando se "
+"hacen colas para entregas salientes."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:23
 #, python-format
@@ -21554,6 +17689,10 @@ msgid ""
 "for the current priority settings.\n"
 "Priority queueing implementation may vary."
 msgstr ""
+"Las prioridades listadas abajo pueden no ser actuales y están sujetas a "
+"cambios. Vea el OutNetMessage Javadocs "
+"para las prioridades actuales de las opciones. La implementación de las "
+"prioridades de las colas puede cambiar."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:30
 msgid "Message Format"
@@ -21575,15 +17714,15 @@ msgstr "Expiración"
 #: i2p2www/pages/site/docs/protocol/i2np.html:36
 #: i2p2www/pages/site/docs/protocol/i2np.html:93
 msgid "Payload Length"
-msgstr ""
+msgstr "Tamaño de la carga"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:37
 msgid "Checksum"
-msgstr ""
+msgstr "Checksum"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:38
 msgid "Payload"
-msgstr ""
+msgstr "Carga"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:41
 #, python-format
@@ -21597,6 +17736,13 @@ msgid ""
 "perfectly aligned,\n"
 "So the message must nominally fit in 63 fragments."
 msgstr ""
+"Aunque el máximo tamaño de carga normalmente es de 64 KB, el tamaño \n"
+"está restringido adicionalmente por el método de fragmentación de \n"
+"mensajes I2NP (Protocolo de Red I2P) en múltiples mensajes de túnel de \n"
+"1 KB, como se describe en la página de "
+"implementación de túnel. El número máximo de fragmentos es 64, y el "
+"mensaje podría no estar pefectamente alineado, así que el mensaje debe "
+"ajustarse nominalmente en 63 fragmentos."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:49
 msgid ""
@@ -21606,6 +17752,10 @@ msgid ""
 "Therefore the maximum size is approximately 956 + (62 * 996) = 62708 "
 "bytes, or 61.2 KB."
 msgstr ""
+"El tamaño máximo de un fragmento inicial es de 956 bytes (asumiendo el \n"
+"modo de entrega del TÚNEL); el tamaño máximo de un fragmento de "
+"continuación es de 996 bytes. Por lo tanto el tamaño máximo es de \n"
+"aproximadamente 956 + (62 * 996) = 62708 bytes, o 61,2 KB."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:55
 msgid ""
@@ -21614,6 +17764,10 @@ msgid ""
 "increased in a future release.\n"
 "The SSU limit is approximately 32 KB."
 msgstr ""
+"Además, los transportes pueden tener restricciones adicionales. NTCP (TCP"
+" basado en NIO) limita actualmente a 16KB - 6 = 16378 bytes, pero esto se"
+" incrementará en una versión futura. El límite SSU (UDP Seguro "
+"Semiconfiable) es aproximadamente de 32 KB."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:61
 msgid ""
@@ -21625,6 +17779,13 @@ msgid ""
 "Therefore the current datagram limit is about 10KB. This limit will be\n"
 "increased in a future release."
 msgstr ""
+"Observe que estos no son los límites para datagramas que el cliente ve, "
+"ya \n"
+"que el router puede empaquetar juntos un LeaseSet (grupo de túneles para "
+"un destino) de repuesta y/o etiquetas de sesión, junto con el mensaje del"
+" cliente, en un mensaje garlic (ajo). El LeaseSet y las etiquetas juntas "
+"pueden añadir unos 5,5 KB. Por lo tanto el límite de datagrama actual es "
+"de alrededor de 10 KB. Este límite se incrementará en una versión futura."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:69
 msgid "Message Types"
@@ -21641,6 +17802,18 @@ msgid ""
 "therefore may not be in the same queue unless the\n"
 "first hops happen to be on the same peer."
 msgstr ""
+"Las prioridades numeradas-más-elevadas, son prioridades más altas. La \n"
+"mayoría del tráfico son TunnelDataMessages (Mensajes de Datos de Túnel, \n"
+"prioridad 400), así que cualquier cosa por encima de 400 es esencialmente"
+" \n"
+"de alta prioridad, y cualquier cosa por debajo es de baja prioridad. "
+"Observe \n"
+"también que muchos de los mensajes están por lo general enrutados a \n"
+"través de túneles exploratorios, no túneles de cliente, y por lo tanto "
+"pueden \n"
+"no estar en la misma cola a menos que los primeros saltos resulte que se"
+" \n"
+"produzcan en el mismo par (`peer`)."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:81
 msgid ""
@@ -21649,32 +17822,40 @@ msgid ""
 "DeliveryStatusMessage, which is wrapped in a GarlicMessage,\n"
 "which is wrapped in a DataMessage."
 msgstr ""
+"Además, no todos los tipos de mensaje se envían sin encriptar. Por\n"
+"ejemplo, cuando probamos un túnel, el router envuelve un \n"
+"DeliveryStatusMessage (mensaje de estado de la entrega), que es \n"
+"envuelto a su vez en un GarlicMessage (mensaje ajo), que a su vez es \n"
+"envuelto en un DataMessage (mensaje de datos)."
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:91
+msgid "Message"
+msgstr "Mensaje"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:92
 msgid "Type"
 msgstr "Tipo"
 
-#: i2p2www/pages/site/docs/protocol/i2np.html:94
-msgid "Priority"
-msgstr "Prioridad"
-
 #: i2p2www/pages/site/docs/protocol/i2np.html:95
 msgid "Comments"
 msgstr "Comentarios"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:103
 msgid "May vary"
-msgstr ""
+msgstr "Puede variar"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:109
 msgid ""
 "Size is 65 + 32*(number of hashes) where typically, the hashes for\n"
 "three floodfill routers are returned."
 msgstr ""
+"El tamaño es 65 + 32*(número de hashes) donde típicamente, los hashes \n"
+"(identificadores criptográficos) para tres routers de inundación "
+"(`floodfill`) son devueltos."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:118
 msgid "Varies"
-msgstr ""
+msgstr "Varía"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:120
 msgid ""
@@ -21685,22 +17866,33 @@ msgid ""
 "RouterInfo\n"
 "as we approach release 1.0."
 msgstr ""
+"La prioridad puede variar. El tamaño es de 898 bytes para un LeaseSet de "
+"2-leases (túneles hacia un destino) típico. Las estructuras de RouterInfo"
+" están comprimidas, y el tamaño varía, sin embargo hay un esfuerzo "
+"continuo para reducir la cantidad de datos publicados en RouterInfo \n"
+"al aproximarnos a la versión 1.0."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:134
 msgid "Priority may vary on a per-destination basis"
-msgstr ""
+msgstr "La prioridad puede variar dependiendo del destino."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:144
 msgid ""
 "Used for message replies, and for testing tunnels - generally wrapped in "
 "a GarlicMessage"
 msgstr ""
+"Usado para respuestas de mensaje, y para probar túneles - por lo general"
+" \n"
+"envuelto en un GarlicMessage (mensaje ajo)."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:152
 msgid ""
 "Generally wrapped in a DataMessage -\n"
 "but when unwrapped, given a priority of 100 by the forwarding router"
 msgstr ""
+"Envuelto por lo general en un DataMessage (mensaje de datos) - pero "
+"cuando está desenvuelto, se le da una prioridad de 100 por el router "
+"reenviante."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:179
 msgid ""
@@ -21709,27 +17901,35 @@ msgid ""
 "reduced to 200 as of release 0.6.1.33.\n"
 "Outbound gateway messages (i.e. those originated locally) remains at 400."
 msgstr ""
+"El mensaje más común. La prioridad para participantes en el túnel, "
+"extremos de salida, y pasarelas (`gateways`) de entrada, se redujo a 200 "
+"desde la versión 0.6.1.33. Los mensajes de pasarela de salida (es decir, "
+"aquellos originados localmente) permanecen en 400."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:199
 msgid "Shorter TunnelBuildMessage as of 0.7.12"
 msgstr ""
+"Un TunnelBuildMessage (mensaje de establecimiento de túnel) más corto "
+"desde la versión 0.7.12"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:207
 msgid "Shorter TunnelBuildReplyMessage as of 0.7.12"
 msgstr ""
+"Un TunnelBuildReplyMessage (mensaje de respuesta de establecimiento de "
+"túnel) más corto desde la versión 0.7.12"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:210
 #, python-format
 msgid "Others listed in 2003 Spec"
-msgstr ""
+msgstr "Otros están listados en la Especificación 2003"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:216
 msgid "Obsolete, Unused"
-msgstr ""
+msgstr "Obsoleto, sin usar"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:220
 msgid "Full Protocol Specification"
-msgstr ""
+msgstr "Especificación completa del protocolo"
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:221
 #, python-format
@@ -21739,6 +17939,10 @@ msgid ""
 "Common Data Structure Specification "
 "page."
 msgstr ""
+"En la página de la Especificación I2NP.\n"
+"Vea también la página de la Especificación de la estructura de datos "
+"comunes."
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:228
 msgid ""
@@ -21748,6 +17952,10 @@ msgid ""
 "further.\n"
 "This is a topic for further research, analysis and testing."
 msgstr ""
+"No está claro si el actual esquema de prioridad es generalmente efectivo,"
+" y si las prioridades para diferentes mensajes deben seguir siendo "
+"ajustadas. Este es un tema para posterior investigación, análisis y "
+"pruebas."
 
 #: i2p2www/pages/site/docs/protocol/index.html:2
 msgid "Protocol Stack"
@@ -21759,6 +17967,8 @@ msgid ""
 "Here is the protocol stack for I2P.\n"
 "See also the Index to Technical Documentation."
 msgstr ""
+"Aquí está la pila de protocolo para I2P.\n"
+"Vea también el Índice a la documentación técnica."
 
 #: i2p2www/pages/site/docs/protocol/index.html:12
 msgid ""
@@ -21766,6 +17976,9 @@ msgid ""
 "The capabilities are listed below, starting at the bottom of the protocol"
 " stack."
 msgstr ""
+"Cada una de las capas en la pila proporciona capacidades extra. Las \n"
+"capacidades están listadas debajo, comenzando en el fondo de la pila de \n"
+"protocolo."
 
 #: i2p2www/pages/site/docs/protocol/index.html:18
 msgid "Internet Layer:"
@@ -21776,6 +17989,9 @@ msgid ""
 "IP: Internet Protocol, allow addressing hosts on the regular internet and"
 " routing packets across the internet using best-effort delivery."
 msgstr ""
+"IP: Protocolo de Internet, permite redireccionar hacia servidores en la \n"
+"Internet regular y enrutar paquetes a través de Internet usando entrega "
+"de mejor-esfuerzo (`best-effort`, sin garantías)"
 
 #: i2p2www/pages/site/docs/protocol/index.html:23
 msgid "Transport Layer:"
@@ -21786,12 +18002,16 @@ msgid ""
 "TCP: Transmission Control Protocol, allow reliable, in-order delivery of "
 "packets across the internet."
 msgstr ""
+"TCP: Protocolo de Control de Transmisiones, permite la entrega de \n"
+"paquetes confiable y ordenada a través de Internet."
 
 #: i2p2www/pages/site/docs/protocol/index.html:27
 msgid ""
 "UDP: User Datagram Protocol, allow unreliable, out-of-order delivery of "
 "packets across the internet."
 msgstr ""
+"UDP: Protocolo de Datagrama de Usuario, permite entrega de paquetes no \n"
+"confiable y desordenada a través de Internet."
 
 #: i2p2www/pages/site/docs/protocol/index.html:30
 msgid ""
@@ -21801,18 +18021,26 @@ msgid ""
 "Two protocols are implemented to provide these capabilities. NTCP builds "
 "on top of TCP, while SSU uses UDP."
 msgstr ""
+"Capa de Transporte I2P: proporciona conexiones cifradas entre 2 "
+"routers I2P. Estos no son aún anónimos, esta es estrictamente una \n"
+"conexión salto-a-salto. Se implementaron dos protocolos para \n"
+"proporcionar estas capacidades. NTCP (TCP basado en NIO) \n"
+"se construye encima de TCP, mientras que SSU (UDP Seguro \n"
+"Semiconfiable) usa UDP."
 
 #: i2p2www/pages/site/docs/protocol/index.html:35
 msgid "NIO-based TCP"
-msgstr ""
+msgstr "TCP basado-en-NIO"
 
 #: i2p2www/pages/site/docs/protocol/index.html:37
 msgid "Secure Semi-reliable UDP"
-msgstr ""
+msgstr "UDP Seguro Semi-confiable"
 
 #: i2p2www/pages/site/docs/protocol/index.html:40
 msgid "I2P Tunnel Layer: provide full encrypted tunnel connections."
 msgstr ""
+"Capa de Túnel I2P: proporciona conexiones de túnel con cifrado "
+"completo."
 
 #: i2p2www/pages/site/docs/protocol/index.html:42
 #, python-format
@@ -21825,6 +18053,13 @@ msgid ""
 "\n"
 "so it will be forwarded."
 msgstr ""
+"Mensajes de túnel: Los mensajes de \n"
+"túnel son mensajes grandes que contienen mensajes cifrados I2NP (vea "
+"debajo), e instrucciones cifradas para su entrega. El cifrado está "
+"dividido en \n"
+"capas. El primer salto descifrará el mensaje de túnel y leerá una parte. "
+"Otra parte puede aún ser cifrada (con otra clave), así que será "
+"reenviada."
 
 #: i2p2www/pages/site/docs/protocol/index.html:48
 #, python-format
@@ -21833,12 +18068,17 @@ msgid ""
 " used to pass messages through multiple routers. These I2NP messages are "
 "combined in tunnel messages."
 msgstr ""
+"Mensajes de I2NP: Los mensajes de Protocolo de \n"
+"Red I2P se usan para pasar mensajes a múltiples routers. Estos mensajes "
+"I2NP se combinan en mensajes de túnel."
 
 #: i2p2www/pages/site/docs/protocol/index.html:53
 msgid ""
 "I2P Garlic Layer: provide encrypted and anonymous end-to-end I2P "
 "message delivery."
 msgstr ""
+"Capa Garlic (ajo) de I2P: proporciona entrega de mensajes I2P \n"
+"extremo-a-extremo cifrada y anónima"
 
 #: i2p2www/pages/site/docs/protocol/index.html:55
 #, python-format
@@ -21847,6 +18087,11 @@ msgid ""
 " wrapped in each other and used to ensure encryption between two tunnels "
 "and are passed along from source to destination, keeping both anonymous."
 msgstr ""
+"Mensajes I2NP: Los mensajes de Protocolo de Red "
+"I2P se envuelven unos en otros y se usan para asegurar el cifrado \n"
+"entre dos túneles, y se transmiten desde la fuente al destino manteniendo"
+" a \n"
+"ambos anónimos."
 
 #: i2p2www/pages/site/docs/protocol/index.html:61
 msgid ""
@@ -21856,12 +18101,21 @@ msgid ""
 "However, each of these layers adds additional functionality, to allow "
 "applications simple and convenient I2P usage."
 msgstr ""
+"Las capas siguientes estrictamente hablando ya no forman parte de la pila"
+" \n"
+"del Protocolo I2P, no son parte de la funcionalidad central del 'router "
+"I2P'. \n"
+"Sin embargo, cada una de estas capas añade funcionalidad adicional, que \n"
+"permite a las aplicaciones un uso simple y conveniente de I2P."
 
 #: i2p2www/pages/site/docs/protocol/index.html:67
 msgid ""
 "I2P Client Layer: allow any client to use I2P functionality, "
 "without requiring the direct use of the router API."
 msgstr ""
+"Capa de cliente I2P: permite a cualquier cliente usar las \n"
+"funcionalidades de I2P, sin requerir el uso directo de la API (Interfaz "
+"de Programación de Aplicaciones) del router."
 
 #: i2p2www/pages/site/docs/protocol/index.html:69
 #, python-format
@@ -21870,12 +18124,18 @@ msgid ""
 "asynchronous messaging over I2P by communicating messages over the I2CP "
 "TCP socket."
 msgstr ""
+"I2CP: El Protocolo de Cliente I2P, permite una \n"
+"mensajería segura y asíncrona sobre I2P mediante la comunicación de "
+"mensajes sobre el socket TCP de I2CP."
 
 #: i2p2www/pages/site/docs/protocol/index.html:74
 msgid ""
 "I2P End-to-end Transport Layer: allow TCP- or UDP-like "
 "functionality on top of I2P."
 msgstr ""
+"Capa de transporte extremo-a-extremo: permite funcionalidades del"
+" \n"
+"tipo-TCP o tipo-UDP encima de I2P."
 
 #: i2p2www/pages/site/docs/protocol/index.html:76
 #, python-format
@@ -21884,6 +18144,9 @@ msgid ""
 "TCP-like streams over I2P. This allows easier porting of existing "
 "applications to I2P."
 msgstr ""
+"Librería de Streaming: una implementación "
+"de streams tipo TCP sobre I2P. Esto permite importar fácilemente "
+"aplicaciones ya existentes a I2P."
 
 #: i2p2www/pages/site/docs/protocol/index.html:80
 #, python-format
@@ -21892,21 +18155,28 @@ msgid ""
 "like messages over I2P. This allows easier porting of existing "
 "applications to I2P."
 msgstr ""
+"Librería de Datagramas: una implementación "
+"de mensajes tipo UDP sobre I2P. Esto permite importar más fácilmente  "
+"aplicaciones ya existentes a I2P."
 
 #: i2p2www/pages/site/docs/protocol/index.html:85
 msgid ""
 "I2P Application Interface Layer: additional (optional) libraries "
 "allowing easier implementations on top of I2P."
 msgstr ""
+"Capa del interfaz para aplicaciones I2P: librerías adicionales "
+"(opcionales) que permiten implementaciones más fáciles sobre I2P."
 
 #: i2p2www/pages/site/docs/protocol/index.html:93
 msgid "I2P Application Proxy Layer: proxy systems."
-msgstr ""
+msgstr "Capa proxy para las aplicaciones I2P: sistemas proxy."
 
 #: i2p2www/pages/site/docs/protocol/index.html:95
 #, python-format
 msgid "HTTP Client/Server, IRC Client, SOCKS, Streamr"
 msgstr ""
+"Servidor/Cliente HTTP, cliente IRC , SOCKS, "
+"Streamr."
 
 #: i2p2www/pages/site/docs/protocol/index.html:99
 msgid ""
@@ -21914,14 +18184,17 @@ msgid ""
 "a large number of applications on top of I2P.\n"
 "We can order this based on the I2P stack layer they use."
 msgstr ""
+"Finalmente, la que puede puede ser considerada la  'capa de aplicación"
+" de I2P', es un gran número de aplicaciones sobre I2P. Podemos "
+"ordenar esto basándonos en las capas I2P que usan."
 
 #: i2p2www/pages/site/docs/protocol/index.html:104
 msgid "Streaming/datagram applications: i2psnark, Syndie, i2phex..."
-msgstr ""
+msgstr "Aplicaciones de streaming/datagramas: i2psnark, Syndie, i2phex..."
 
 #: i2p2www/pages/site/docs/protocol/index.html:105
 msgid "SAM/BOB applications: IMule, i2p-bt, i2prufus, Robert..."
-msgstr ""
+msgstr "Aplicaciones SAM/BOB: IMule, i2p-bt, i2prufus, Robert..."
 
 #: i2p2www/pages/site/docs/protocol/index.html:106
 #, python-format
@@ -21929,12 +18202,16 @@ msgid ""
 "Other I2P applications: Syndie, EepGet, plugins..."
 msgstr ""
+"Otras aplicaciones I2P: Syndie, EepGet, complementos... "
 
 #: i2p2www/pages/site/docs/protocol/index.html:107
 msgid ""
 "Regular applications: Jetty, Apache, Monotone, CVS, browsers, "
 "e-mail..."
 msgstr ""
+"Aplicaciones regulares: Jetty, Apache, Monotone, CVS, navegadores,"
+" correo..."
 
 #: i2p2www/pages/site/docs/protocol/index.html:111
 msgid "I2P Network stack"
@@ -21942,15 +18219,15 @@ msgstr "Pila de red I2P"
 
 #: i2p2www/pages/site/docs/protocol/index.html:113
 msgid "Figure 1: The layers in the I2P Network stack."
-msgstr ""
+msgstr "Figura 1: Las capas en la pila de red de I2P."
 
 #: i2p2www/pages/site/docs/protocol/index.html:118
 msgid "Note: SAM/SAMv2 can use both the streaming lib and datagrams."
-msgstr ""
+msgstr "Nota: SAM/SAMv2 puede usar la librería de streaming y de datagramas."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:2
 msgid "I2P Blockfile Specification"
-msgstr ""
+msgstr "Especificaciones del Blockfile, archivo de bloqueo, de I2P"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:3
 msgid "January 2012"
@@ -21958,7 +18235,7 @@ msgstr "Enero de 2012:"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:6
 msgid "Blockfile and Hosts Database Specification"
-msgstr ""
+msgstr "Especificaciones de la base de datos de hosts y del Blockfile"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:8
 #, python-format
@@ -21968,6 +18245,9 @@ msgid ""
 "and the tables in the hostsdb.blockfile used by the Blockfile Naming Service."
 msgstr ""
+"Este documento especifica el formato del blockfile de I2P y las tablas en"
+" el hostsdb.blockfile usadas por el Servicio de "
+"Nombres del Blockfile."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:14
 msgid ""
@@ -21984,6 +18264,16 @@ msgid ""
 " format, and the blockfile provides\n"
 "approximately 10x reduction in lookup times."
 msgstr ""
+"El blockfile proporciona búsquedas rápidas de destinaciones en un formato"
+" compacto. Ya que el gasto de recursos de la página blockfile es "
+"substancial, las destinaciones son almacenadas en forma binaria en vez de"
+" Base64 como en el formato hosts.txt. Además, el blockfile proporciona la"
+" capacidad de almacenaje arbitrario de metadatos para cada entrada (como "
+"la fecha añadida, origen y comentarios) . Los metadatos pueden ser usados"
+" en el futuro para proporcionar características avanzadas en la libreta "
+"de direcciones. El espacio de almacenamiento del blockfile sólo aumenta "
+"un poco con respecto al formato hosts.txt, y el blockfile proporciona un "
+"ahorro de 10x en los tiempos de búsqueda."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:24
 #, python-format
@@ -21996,10 +18286,17 @@ msgid ""
 "First we will define the file format, then the use of that format by the "
 "BlockfileNamingService."
 msgstr ""
+"Un blockfile es simplemente el almacenamiento de múltiples mapeados "
+"ordenados (pares clave-valor),\n"
+"implementado como listas por saltos ('skiplists') .\n"
+"El formato blockfile fue adoptado de la\n"
+"base de datos Blockfile Metanotion.\n"
+"Primero definiremos el formato de fichero, después el uso de ese formato "
+"por parte del BlockfileNamingService (servicio de nombres blockfile)."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:32
 msgid "Blockfile Format"
-msgstr ""
+msgstr "Formato Blockfile"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:33
 msgid ""
@@ -22012,6 +18309,14 @@ msgid ""
 "The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in"
 " the file."
 msgstr ""
+"Las especificaciones originales del blockfile fueron modificadas para "
+"añadir números mágicos a cada página.\n"
+"El fichero está estructurado en páginas de 1024-bytes. Las páginas están "
+"numeradas empezando desde 1.\n"
+"El \"superblock\" (superbloque) siempre está en la página 1, es decir, "
+"comenzando en el byte 0 del fichero.\n"
+"La lista por saltos ('skiplist') del metaíndice está siempre en la página"
+" 2, es decir, comenzando en el byte 1024 del fichero."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:40
 msgid ""
@@ -22019,26 +18324,34 @@ msgid ""
 "All 4-byte integer values (page numbers) are signed and negative values "
 "are illegal."
 msgstr ""
+"Todos los valores enteros de 2 bytes son sin signo. Todos los valores "
+"enteros de 4 bytes (números de página) tienen signo y los valores "
+"negativos son ilegales."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:45
 msgid ""
 "The database is designed to be opened and accessed by a single thread.\n"
 "The BlockfileNamingService provides synchronization."
 msgstr ""
+"La base de datos está diseñada para ser abierta y accedida por un solo "
+"hilo. El BlockfileNamingService proporciona la sincronización."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:50
 msgid "Superblock format:"
-msgstr ""
+msgstr "Formato del Superblock, superbloque:"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:65
 msgid "Skip list block page format:"
-msgstr ""
+msgstr "Formato del bloque de  página de skiplist:"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:80
 msgid ""
 "Skip level block page format is as follows.\n"
 "All levels have a span. Not all spans have levels."
 msgstr ""
+"El formato del bloque de página del nivel de salto, skip level, es como "
+"sigue. Todos los niveles tienen un span, o segmento. No todos los "
+"segmentos tienen niveles."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:95
 msgid ""
@@ -22048,10 +18361,15 @@ msgid ""
 "Key/value structures are sorted by key within each span.\n"
 "Spans other than the first span may not be empty."
 msgstr ""
+"El formato del segmento de omisión del bloque de página es como sigue. "
+"Las estructuras clave/valor están ordenadas por la clave dentro de cada "
+"segmento a través de todos los segmentos. Las estructuras clave/valor "
+"están ordenadas por la clave entre cada segmento. Los segmentos "
+"diferentes del primer segmento pueden que no estén vacíos."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:112
 msgid "Span Continuation block page format:"
-msgstr ""
+msgstr "Formato del bloque de página de la continuación del segmento."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:123
 msgid ""
@@ -22064,14 +18382,22 @@ msgid ""
 "Key and value data may be split across pages.\n"
 "Max key and value lengths are 65535 bytes."
 msgstr ""
+"El formato de estructura clave/valor es como sigue. Los tramos de clave \n"
+"y valor no deben ser divididos entre las páginas, es decir, todos estos 4"
+" bytes deben estar en la misma página. Si no hay suficiente espacio, los "
+"últimos 1-3 bytes de la página quedan sin uso y estos tramos estarán en "
+"la posición 8 en la página de continuación. Los datos de clave y valor "
+"pueden ser divididos entre las páginas. Los tamaños máximos de clave y "
+"valor son \n"
+"de 65535 bytes."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:139
 msgid "Free list block page format:"
-msgstr ""
+msgstr "Formato de página de bloque de lista libre:"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:151
 msgid "Free page block format:"
-msgstr ""
+msgstr "Formato de bloque de página libre:"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:160
 msgid ""
@@ -22080,10 +18406,15 @@ msgid ""
 "The key is the name of the skiplist and the value is the page index of "
 "the skiplist."
 msgstr ""
+"El metaíndice (situado en la página 2) es un mapeado de cadenas US-ASCII"
+" \n"
+"a enteros de 4-bytes.\n"
+"La clave es el nombre de la lista por saltos ('skiplist') y el valor es "
+"el índice de la página de la lista por saltos."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:165
 msgid "Blockfile Naming Service Tables"
-msgstr ""
+msgstr "Tablas del servicio de nombres de ficheros de bloque"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:166
 msgid ""
@@ -22091,33 +18422,45 @@ msgid ""
 "\n"
 "The maximum number of entries per span is 16."
 msgstr ""
+"Las tablas creadas y usadas por el BlockfileNamingService (servicio de "
+"nombres de ficheros de bloque) son como sigue. El número máximo de "
+"entradas por segmento es de 16."
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:171
 msgid "Properties Skiplist"
-msgstr ""
+msgstr "Lista por saltos ('skiplist') de propiedades"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:172
 #, python-format
 msgid ""
-"\"%%__INFO__%%\" is the master database skiplist with String/Properties "
-"key/value entries containing only one entry:"
+"%(INFO)s is the master database skiplist with String/Properties key/value"
+" entries containing only one entry:"
 msgstr ""
+"%(INFO)s es la lista por saltos ('skiplist') de la base de datos maestra "
+"con entradas Cadena/Propiedades clave/valor, que contiene sólo una "
+"entrada:"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:184
 msgid "Reverse Lookup Skiplist"
-msgstr ""
+msgstr "Lista por saltos ('skiplist') de búsquedas inversas"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:185
 #, python-format
 msgid ""
-"\"%%__REVERSE__%%\" is the reverse lookup skiplist with "
-"Integer/Properties key/value entries\n"
+"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties "
+"key/value entries\n"
 "    (as of database version 2):"
 msgstr ""
+"%(REVERSE)s es la lista por saltos ('skiplist') de búsqueda inversa con "
+"entradas\n"
+"Entero/Propiedades clave/valor\n"
+"(desde la versión 2 de la base de datos):"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:199
 msgid "hosts.txt, userhosts.txt, and privatehosts.txt Skiplists"
 msgstr ""
+"Listas por saltos ('skiplists') de hosts.txt, userhosts.txt, y "
+"privatehosts.txt"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:200
 msgid ""
@@ -22125,22 +18468,29 @@ msgid ""
 "the hosts for that database.\n"
 "The keys/values in these skiplists are as follows:"
 msgstr ""
+"Para la base de datos de cada equipo, hay una lista por saltos "
+"('skiplist') que \n"
+"contiene\n"
+"los equipos para esa base de datos.\n"
+"Las claves/valores en estas listas por saltos son como sigue:"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:211
 msgid "The DestEntry Properties typically contains:"
-msgstr ""
+msgstr "Las propiedades DestEntry típicamente contienen:"
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:220
 msgid "Hostname keys are stored in lower-case and always end in \".i2p\"."
 msgstr ""
+"Las claves de nombre de servidor se guardan en minúsculas y siempre \n"
+"acaban en \".i2p\"."
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:2
 msgid "Common structure Specification"
-msgstr ""
+msgstr "Especificación de estructura común"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:6
 msgid "Data types Specification"
-msgstr ""
+msgstr "Especificación de tipos de datos"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:7
 #, python-format
@@ -22150,10 +18500,13 @@ msgid ""
 "I2NP, I2CP,\n"
 "SSU, etc."
 msgstr ""
+"Este documento describe algunos tipos de datos comunes a todos los\n"
+"protocolos I2P, como I2NP, I2CP, SSU, etc."
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:17
 msgid "Represents a non-negative integer.\n"
-msgstr ""
+msgstr "Representa un entero no-negativo.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:20
 #: i2p2www/pages/site/docs/spec/common-structures.html:31
@@ -22170,20 +18523,21 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/common-structures.html:166
 #: i2p2www/pages/site/docs/spec/common-structures.html:178
 #: i2p2www/pages/site/docs/spec/common-structures.html:231
-#: i2p2www/pages/site/docs/spec/common-structures.html:298
-#: i2p2www/pages/site/docs/spec/common-structures.html:347
-#: i2p2www/pages/site/docs/spec/common-structures.html:391
-#: i2p2www/pages/site/docs/spec/common-structures.html:438
-#: i2p2www/pages/site/docs/spec/common-structures.html:573
-#: i2p2www/pages/site/docs/spec/common-structures.html:630
+#: i2p2www/pages/site/docs/spec/common-structures.html:314
+#: i2p2www/pages/site/docs/spec/common-structures.html:363
+#: i2p2www/pages/site/docs/spec/common-structures.html:415
+#: i2p2www/pages/site/docs/spec/common-structures.html:462
+#: i2p2www/pages/site/docs/spec/common-structures.html:597
+#: i2p2www/pages/site/docs/spec/common-structures.html:660
 #: i2p2www/pages/site/docs/spec/streaming.html:35
-#: i2p2www/pages/site/get-involved/develop/applications.html:8
 msgid "Contents"
 msgstr "Contenido"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:21
 msgid "1 to 8 bytes in network byte order representing an unsigned integer\n"
 msgstr ""
+"De 1 a 8 bytes en el orden de bytes (endianness) de la red representando "
+"un entero sin signo\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:27
 msgid ""
@@ -22191,14 +18545,17 @@ msgid ""
 "timezone.\n"
 "If the number is 0, the date is undefined or null.\n"
 msgstr ""
+"El número de milisegundos desde la medianoche del 1 de enero de 1970 en "
+"la zona horaria GMT.\n"
+"Si el número es 0, la fecha no está definida o es nula.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:32
 msgid "8 byte Integer\n"
-msgstr ""
+msgstr "Entero de 8 bytes\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:38
 msgid "Represents a UTF-8 encoded string.\n"
-msgstr ""
+msgstr "Representa una cadena codificada en UTF-8.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:42
 msgid ""
@@ -22208,20 +18565,28 @@ msgid ""
 "UTF-8 encoded character array.\n"
 "Length limit is 255 bytes (not characters). Length may be 0.\n"
 msgstr ""
+"1 o más bytes donde el primer byte es el número de bytes (¡no de "
+"caracteres!) en la cadena,\n"
+"y los restantes de 0 a 255 bytes son la serie de caracteres codificados "
+"en UTF-8 no terminados en null (vacío).\n"
+"El límite de tamaño es de 255 bytes (no caracteres). El tamaño puede ser "
+"0.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:50
 msgid ""
 "A boolean value, supporting null/unknown representation\n"
 "0=false, 1=true, 2=unknown/null\n"
 msgstr ""
+"Un valor booleano, que soporta representación nulo/desconocido\n"
+"0=falso, 1=verdadero, 2=desconocido/nulo\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:55
 msgid "1 byte Integer\n"
-msgstr ""
+msgstr "1 byte entero\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:59
 msgid "Deprecated - unused\n"
-msgstr ""
+msgstr "Desestimado - sin uso\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:65
 #, python-format
@@ -22230,6 +18595,11 @@ msgid ""
 "exponent, not the primes, which are constant and defined in\n"
 "the cryptography specification.\n"
 msgstr ""
+"Esta estructura se usa en el cifrado ElGamal, representando sólo el "
+"exponente, no los números primos, que son constantes y están definidos en"
+"\n"
+"la especificación de "
+"criptografía.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:70
 #: i2p2www/pages/site/docs/spec/common-structures.html:83
@@ -22243,10 +18613,15 @@ msgid ""
 "exponent, not the primes which are constant and defined in\n"
 "the cryptography specification.\n"
 msgstr ""
+"Esta estructura se usa en el descifrado ElGamal, representando sólo el "
+"exponente, no los números primos, que son constantes y están definidos en"
+"\n"
+"la especificación de "
+"criptografía.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:91
 msgid "This structure is used for AES256 encryption and decryption.\n"
-msgstr ""
+msgstr "Esta estructura se usa por el cifrado y descrifrado AES256.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:95
 #: i2p2www/pages/site/docs/spec/common-structures.html:143
@@ -22260,6 +18635,8 @@ msgid ""
 "This structure is used for verifying DSA signatures.\n"
 msgstr ""
+"Esta estructura se usa para verificar firmas DSA.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:107
 msgid "128 bytes\n"
@@ -22271,6 +18648,8 @@ msgid ""
 "This structure is used for creating DSA signatures.\n"
 msgstr ""
+"Esta estructura se usa para crear las firmas DSA.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:119
 msgid "20 bytes\n"
@@ -22282,6 +18661,8 @@ msgid ""
 "This structure represents the DSA "
 "signature of some data.\n"
 msgstr ""
+"Esta estructura representa la firma DSA de algunos datos.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:131
 msgid "40 bytes\n"
@@ -22290,6 +18671,8 @@ msgstr "40 bytes\n"
 #: i2p2www/pages/site/docs/spec/common-structures.html:139
 msgid "Represents the SHA256 of some data.\n"
 msgstr ""
+"Representa el (identificador-criptográfico/hash) SHA256 de algunos datos."
+"\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:151
 msgid "A random number\n"
@@ -22297,17 +18680,19 @@ msgstr "Un número aleatorio\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:163
 msgid "Defines an identifier that is unique to each router in a tunnel.\n"
-msgstr ""
+msgstr "Define un identificador que es único para cada router en un túnel.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:167
 msgid "4 byte Integer\n"
-msgstr ""
+msgstr "4 bytes enteros\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:175
 msgid ""
 "A certificate is a container for various receipts or proof of works used "
 "throughout the I2P network.\n"
 msgstr ""
+"Un certificado es un contenedor para varios recibos o pruebas de trabajo "
+"usados por toda la red I2P.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:179
 msgid ""
@@ -22315,12 +18700,19 @@ msgid ""
 " followed by a 2 Integer specifying the "
 "size of the certificate payload, then that many bytes.\n"
 msgstr ""
+"1 byte entero que especifica el tipo de "
+"certificado, seguido por un entero de 2 "
+"bytes que especifica el tamaño del cargamento del certificado, después "
+"esos tantos bytes.\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:205
 msgid ""
 "For Router Identities, the "
 "Certificate is always NULL, no others are currently implemented."
 msgstr ""
+"Para las RouterIdentities, el "
+"certificado siempre es NULL (vacío), no hay otros implementados "
+"actualmente."
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:209
 #, python-format
@@ -22328,6 +18720,9 @@ msgid ""
 "For Garlic Cloves, the "
 "Certificate is always NULL, no others are currently implemented."
 msgstr ""
+"Para los dientes del ajo, el "
+"certificado siempre es NULL (vacío), no hay otros implementados "
+"actualmente."
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:213
 #, python-format
@@ -22335,6 +18730,8 @@ msgid ""
 "For Garlic Messages, the Certificate "
 "is always NULL, no others are currently implemented."
 msgstr ""
+"Para los mensajes ajo, el certificado"
+" siempre es NULL (vacío), no hay otros implementados actualmente."
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:217
 msgid ""
@@ -22343,26 +18740,36 @@ msgid ""
 "however non-NULL certs are not widely used, and any checking is left to "
 "the application-level."
 msgstr ""
+"Para los destinos, el certificado "
+"puede ser non-NULL (no-vacío),\n"
+"sin embargo los certificados non-NULL no son ampliamente usados , y\n"
+"cualquier comprobación se deja al nivel-de-aplicación."
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:228
 msgid "A set of key/value mappings or properties\n"
-msgstr ""
+msgstr "Un conjunto de mapeados de clave/valor o propiedades\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:232
 msgid "A 2-byte size Integer followed by a series of String=String; pairs\n"
 msgstr ""
+"Un entero de 2-bytes de tamaño seguido por una serie de pares "
+"String=String; (cadena)\n"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:259
 msgid ""
 "The encoding isn't optimal - we either need the '=' and ';' characters, "
 "or the string lengths, but not both"
 msgstr ""
+"La codificación no es óptima - o bien necesitamos los caracteres '=' y "
+"';' o los tamaños de cadena, pero no ambos"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:263
 msgid ""
 "Some documentation says that the strings may not include '=' or ';' but "
 "this encoding supports them"
 msgstr ""
+"Alguna documentación dice que las cadenas pueden no incluir '=' o ';' "
+"pero esta codificación los soporta"
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:267
 msgid ""
@@ -22372,79 +18779,144 @@ msgid ""
 "UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store "
 "Message will be corrupted."
 msgstr ""
+"Las cadenas están definidas para que sean UTF-8 pero en la implementación"
+" actual, I2CP usa UTF-8 pero I2NP no.\n"
+"Por ejemplo,\n"
+"las cadenas UTF-8 en un mapeado de opciones RouterInfo en un mensaje de "
+"almacenaje de base de datos I2NP estarán corruptas."
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:273
 msgid ""
-"Mappings contained in I2NP messages (i.e. in a RouterAddress or "
-"RouterInfo)\n"
-"must be sorted by key so that the signature will be invariant."
+"The encoding allows duplicate keys, however in any usage where the "
+"mapping is signed,\n"
+"duplicates may cause a signature failure."
 msgstr ""
+"La codificación permite claves duplicadas, sin embargo. en cualquier uso "
+"donde\n"
+"el mapeado esté firmado, los duplicados pueden causar un fallo de la "
+"firma."
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:278
 msgid ""
+"Mappings contained in I2NP messages (i.e. in a RouterAddress or "
+"RouterInfo)\n"
+"must be sorted by key so that the signature will be invariant.\n"
+"Duplicate keys are not allowed."
+msgstr ""
+"Los mapeados contenidos en mensajes I2NP (de protocolo de red I2P,\n"
+"es decir, en un RouterAdress o RouterInfo) deben ser ordenados por clave\n"
+"para que la firma resulte invariante.\n"
+"Las claves duplicadas no están permitidas."
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:284
+#, python-format
+msgid ""
+"Mappings contained in an I2CP "
+"SessionConfig\n"
+"must be sorted by key so that the signature will be invariant.\n"
+"Duplicate keys are not allowed."
+msgstr ""
+"Los mapeados contenidos en una I2CP SessionConfig (sesión de "
+"configuración de I2CP)\n"
+"deben estar ordenados por clave para que la firma resulte invariante.\n"
+"Las claves duplicadas no están permitidas."
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:290
+msgid ""
+"While it is application-dependent, keys and values are generally case-"
+"sensitive."
+msgstr ""
+"Aunque son dependientes-de-la-aplicación, las claves y valores "
+"generalmente distinguen mayúsculas/minúsculas."
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:294
+msgid ""
 "Key and value string length limits are 255 bytes (not characters) each, "
 "plus the length byte. Length byte may be 0."
 msgstr ""
+"Los tamaños de las cadenas clave y valor son de 255 bytes (no caracteres)"
+" cada una, más el byte de tamaño. El byte de tamaño puede ser 0."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:282
+#: i2p2www/pages/site/docs/spec/common-structures.html:298
 msgid ""
 "Total length limit is 65535 bytes, plus the 2 byte size field, or 65537 "
 "total."
 msgstr ""
+"El límite de tamaño total es de 65535 bytes, más el campo de tamaño de 2 "
+"bytes, o 65537 en total."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:291
+#: i2p2www/pages/site/docs/spec/common-structures.html:307
 msgid "Common structure specification"
-msgstr ""
+msgstr "Especificación de estructura común"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:295
+#: i2p2www/pages/site/docs/spec/common-structures.html:311
 msgid "Defines the way to uniquely identify a particular router\n"
 msgstr ""
+"Define la manera de identificar de forma unívoca un router (enrutador) "
+"específico\n"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:299
+#: i2p2www/pages/site/docs/spec/common-structures.html:315
 msgid ""
 "PublicKey followed by SigningPublicKey and then a Certificate\n"
 msgstr ""
+"Una PublicKey seguida de una SigningPublicKey y luego un certificate\n"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:336
+#: i2p2www/pages/site/docs/spec/common-structures.html:352
 msgid ""
 "The certificate for a RouterIdentity is currently unused and is always "
 "NULL."
 msgstr ""
+"El certificado para una RouterIdentity actualmente está sin uso y siempre"
+" es NULL (vacío)."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:344
+#: i2p2www/pages/site/docs/spec/common-structures.html:360
 msgid ""
 "A Destination defines a particular endpoint to which messages can be "
 "directed for secure delivery.\n"
 msgstr ""
+"Un destino define un punto de término específico al que los mensajes "
+"pueden ser dirigidos para una entrega segura.\n"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:348
+#: i2p2www/pages/site/docs/spec/common-structures.html:364
 msgid ""
 "PublicKey followed by a SigningPublicKey and then a Certificate\n"
 msgstr ""
+"Una PublicKey seguida por una SigningPublicKey y luego un certificado\n"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:388
+#: i2p2www/pages/site/docs/spec/common-structures.html:412
 msgid ""
 "Defines the authorization for a particular tunnel to receive messages "
 "targeting a Destination.\n"
 msgstr ""
+"Define la autorización para que un túnel específico reciba mensajes cuyo "
+"objetivo es un Destination.\n"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:392
+#: i2p2www/pages/site/docs/spec/common-structures.html:416
 msgid ""
 "SHA256 Hash of the\n"
 "RouterIdentity of the gateway "
 "router, then the TunnelId, and finally an "
 "end Date\n"
 msgstr ""
+"El hash SHA256 de la RouterIdentity de un router pasarela "
+"('gateway'), luego el TunnelId, y "
+"finalmente una fecha de término\n"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:423
+#: i2p2www/pages/site/docs/spec/common-structures.html:447
 msgid "Total size: 44 bytes"
 msgstr "Tamaño total: 44 bytes"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:433
+#: i2p2www/pages/site/docs/spec/common-structures.html:457
 msgid ""
 "Contains all of the currently authorized Leases for a particular Destination.\n"
 msgstr ""
+"Contiene todos los leases autorizados "
+"actualmente para un destino "
+"específico, la clave pública con la que "
+"los mensajes ajo ('garlic') pueden ser cifrados,\n"
+"y luego la clave pública firmante "
+"que puede usarse para revocar esta versión específica de la estructura. "
+"El LeaseSet es una de las dos "
+"estructuras guardadas en la base de datos de red\n"
+"(siendo la otra RouterInfo), y está "
+"asegurada con el (identificador-criptográfico/hash) SHA256 del destino contenido.\n"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:439
+#: i2p2www/pages/site/docs/spec/common-structures.html:463
 msgid ""
 "Destination, followed by a PublicKey for encryption, then a Destination's SigningPrivateKey"
 msgstr ""
+"Un destino, seguido por una clave pública para cifrado, luego una clave pública firmante que puede "
+"usarse para revocar esta versión del LeaseSet,\n"
+"luego un entero de 1 byte que especifica "
+"cuántas estructuras de lease hay en el set "
+"(conjunto), seguido por las estructuras de Leases actuales, y finalmente una firma de los\n"
+"bytes anteriores firmados por la clave pública firmante del destino"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:531
+#: i2p2www/pages/site/docs/spec/common-structures.html:555
 msgid ""
 "The public key of the destination was used for the old i2cp-to-i2cp "
 "encryption\n"
-"which was disabled in version 0.6, it is currently unused?"
+"which was disabled in version 0.6, it is currently unused."
 msgstr ""
+"La clave pública del destino era usada por el cifrado antiguo I2CP-a-I2CP"
+"\n"
+"que se deshabilitó en la versión 0.6, actualmente no se usa."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:536
+#: i2p2www/pages/site/docs/spec/common-structures.html:560
 #, python-format
 msgid ""
 "The encryption key is used for end-to-end ElGamal/AES+EtiquetadeSesión.\n"
+"Actualmente se genera de nuevo en cada arranque del router, no es "
+"persistente."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:541
+#: i2p2www/pages/site/docs/spec/common-structures.html:565
 msgid ""
 "The signature may be verified using the signing public key of the "
 "destination."
-msgstr ""
+msgstr "La firma puede verificarse usando la clave pública firmante del destino."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:545
+#: i2p2www/pages/site/docs/spec/common-structures.html:569
 msgid ""
 "The signing_key is currently unused. It was intended for LeaseSet "
 "revocation, which is unimplemented.\n"
 "It is currently generated anew at every router startup, it is not "
 "persistent."
 msgstr ""
+"La signing_key (clave firmante) actualmente no se usa. Se pensó para la "
+"revocación del LeaseSet, que no está implementado.\n"
+"Actualmente se genera de nuevo cada vez que arranca el router, no es "
+"persistente."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:549
+#: i2p2www/pages/site/docs/spec/common-structures.html:573
 msgid ""
 "The earliest expiration of all the Leases is treated as the timestamp or "
 "version of the LeaseSet.\n"
@@ -22516,8 +19023,20 @@ msgid ""
 "increment the expiration\n"
 "of the oldest Lease by at least 1 ms in that case."
 msgstr ""
+"La expiración más temprana entre todos los leases es tratada como una "
+"datación o versión\n"
+"del LeaseSet (conjunto de túneles para un mismo destino). Los routers, "
+"por lo general,\n"
+"no aceptarán el almacenaje de un LeaseSet a menos que sea \"más nuevo\" "
+"que el actual.\n"
+"Tenga cuidado al publicar un nuevo LeaseSet donde el lease más antiguo "
+"sea el mismo\n"
+"que el más antiguo en el anterior LeaseSet. El router que lo publica, por"
+" lo general, debe\n"
+"incrementar el periodo de expiración del lease más antiguo en, al menos, "
+"1 ms en ese caso."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:556
+#: i2p2www/pages/site/docs/spec/common-structures.html:580
 msgid ""
 "Prior to release 0.9.7, when included in a DatabaseStore Message sent by "
 "the originating router,\n"
@@ -22528,14 +19047,24 @@ msgid ""
 "This is an implementation detail and not part of the structures "
 "specification."
 msgstr ""
+"Antes de la versión 0.9.7, cuando se incluía en un mensaje de almacenaje "
+"de base de datos enviado por el router originante,\n"
+"el router establecía todas las expiraciones de los leases publicados al "
+"mismo valor, aquel del\n"
+"lease más precoz. Desde la versión 0.9.7, el router publica la expiración"
+" real del lease para cada lease.\n"
+"Esta es un detalle de implementación y no parte de la especificación de "
+"estructuras."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:570
+#: i2p2www/pages/site/docs/spec/common-structures.html:594
 msgid ""
 "This structure defines the means to contact a router through a transport "
 "protocol.\n"
 msgstr ""
+"Esta estructura define los medios para contactar con un router a través "
+"de un protocolo de transporte.\n"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:574
+#: i2p2www/pages/site/docs/spec/common-structures.html:598
 msgid ""
 "1 byte Integer defining the relative cost "
 "of using the address, where 0 is free and 255 is expensive, followed by "
@@ -22547,22 +19076,56 @@ msgid ""
 "specific options necessary to establish the connection, such as\n"
 "IP address, port number, email address, URL, etc.\n"
 msgstr ""
+"1 byte entero que define el coste relativo "
+"de usar la dirección, donde 0 es gratis y 255 es caro, seguido por la fecha de expiración  después de la cual la "
+"dirección no debe usarse, o si está vacía ('null'), la direccción nunca "
+"expira.\n"
+"Después de eso viene una cadena que define "
+"el protocolo de transporte que usa la dirección de este router. "
+"Finalmente hay un mapeado que contiene "
+"todas las opciones específicas de transporte necesarias para establecer "
+"la conexión, tales como\n"
+"dirección IP, número de puerto, dirección de correo electrónico, URL, "
+"etc.\n"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:609
+#: i2p2www/pages/site/docs/spec/common-structures.html:633
 msgid "Cost is typically 5 or 6 for SSU, and 10 or 11 for NTCP."
-msgstr ""
+msgstr "El coste normalmente es de 5 o 6 para SSU, y 10 u 11 para NTCP."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:613
+#: i2p2www/pages/site/docs/spec/common-structures.html:637
 msgid ""
 "Expiration is currently unused, always null (all zeroes)).\n"
 "As of release 0.9.3, the expiration is assumed zero and not stored, so "
 "any non-zero expiration\n"
 "will fail in the RouterInfo signature verification.\n"
 "Implementing expiration (or another use for these bytes) will be a "
-"backwards-incompatible change."
+"backwards-incompatible change.\n"
+"Routers MUST set this field to all zeros."
 msgstr ""
+"La fecha de expiración está actualmente sin uso, siempre nula (todo "
+"ceros).\n"
+"Desde la versión 0.9.3, la fecha de expiración se asume que es cero y no "
+"se\n"
+"almacena, así que cualquier expiración no-cero fallará en la verificacion"
+" de la\n"
+"firma de RouterInfo. La implementación de expiración (u otro uso para "
+"estos bytes) será un cambio retroactivamente-compatible.\n"
+"Los routers DEBEN establecer este campo a todo ceros."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:626
+#: i2p2www/pages/site/docs/spec/common-structures.html:645
+msgid ""
+"The following options, while not required, are standard and expected to "
+"be present in most router addresses:\n"
+"\"host\" (an IPv4 or IPv6 address or host name) and \"port\"."
+msgstr ""
+"Las siguentes opciones, aunque no son requeridas, son standard y se "
+"espera que estén presentes en la mayoría de las direcciones del router:"
+" \n"
+"\"equipo\" (una dirección IPv4 o IPv6, o un nombre de equipo ('host')) y "
+"\"puerto\"."
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:656
 msgid ""
 "Defines all of the data that a router wants to publish for the network to"
 " see. The RouterInfo is one of two "
@@ -22571,37 +19134,65 @@ msgid ""
 "\n"
 "the contained RouterIdentity.\n"
 msgstr ""
+"Define todos los datos que un router quiere publicar para que la red los "
+"vea. La RouterInfo es una de de las "
+"dos estructuras almacenadas en la base de datos de red (siendo la otra el"
+" LeaseSet), y está asegurada con el "
+"(identificador-criptográfico/hash) SHA256 de\n"
+"la RouterIdentity contenida.\n"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:631
+#: i2p2www/pages/site/docs/spec/common-structures.html:661
 msgid ""
 "RouterIdentity followed by the Date, when the entry was published\n"
 msgstr ""
+"La RouterIdentity seguida por la "
+"fecha de publicación de la entrada.\n"
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:710
+#: i2p2www/pages/site/docs/spec/common-structures.html:741
 msgid ""
 "The peer_size Integer may be followed by a list of that many router "
 "hashes.\n"
 "This is currently unused. It was intended for a form of restricted "
-"routes, which is unimplemented.\n"
+"routes, which is unimplemented."
 msgstr ""
+"El entero peer_size (tamaño del par) puede estar seguido por una lista de"
+"\n"
+"esos muchos identificadores criptográficos ('hashes') de routers.\n"
+"Actualmente esto no se usa. Estaba pensado para una forma de rutas "
+"restringidas,\n"
+"que está sin implementar."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:715
+#: i2p2www/pages/site/docs/spec/common-structures.html:746
 msgid ""
 "The signature may be verified using the signing public key of the "
-"router_ident.\n"
+"router_ident."
 msgstr ""
+"La firma puede verificarse usando la clave pública de firmado de la "
+"router_ident (identidad del router)."
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:723
+#: i2p2www/pages/site/docs/spec/common-structures.html:750
+#, python-format
+msgid ""
+"See the network database page\n"
+"for standard options that are expected to be present in all router infos."
+msgstr ""
+"Vea la página de la base de datos de "
+"red para opciones standard\n"
+"que se espera que estén presentes en todas las informaciones de routers."
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:760
 #, python-format
 msgid ""
 "Defined in the Tunnel Message "
 "Specification.\n"
 msgstr ""
+"Definido en la especificación de "
+"mensaje de túnel.\n"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:2
 msgid "Configuration File Specification"
-msgstr ""
+msgstr "Especificación de fichero de configuración"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:7
 msgid ""
@@ -22611,6 +19202,12 @@ msgid ""
 "files,\n"
 "and links to detailed documentation where available."
 msgstr ""
+"Esta página proporciona una especificación general de los archivos de \n"
+"configuración de I2P, usados por el router y diferentes aplicaciones. "
+"También \n"
+"da una visión general de la información contenida en los diferentes "
+"ficheros, \n"
+"y enlaces a la documentación detallada donde esté disponible."
 
 #: i2p2www/pages/site/docs/spec/configuration.html:15
 msgid "General Format"
@@ -22623,6 +19220,9 @@ msgid ""
 "Java Properties\n"
 "with the following exceptions:"
 msgstr ""
+"Un fichero de configuración I2P está formateado como se especifica en las"
+"  propiedades de Java con las siguientes "
+"excepciones:"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:22
 msgid "Encoding must be UTF-8"
@@ -22633,40 +19233,49 @@ msgid ""
 "Does not use or recognize any escapes, including '\\', so lines may not "
 "be continued"
 msgstr ""
+"No usa o reconoce caracteres de escape alguno, incluyendo '\\', por lo "
+"que las líneas no pueden ser continuadas"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:24
 msgid "'#' or ';' starts a comment, but '!' does not"
-msgstr ""
+msgstr "'#' o ';' inician un comentario, pero '!' no"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:25
 msgid ""
 "'#' starts a comment in any position but ';' must be in column 1 to start"
 " a comment"
 msgstr ""
+"'#' inicia un comentario en cualquier posición pero ';' debe estar en \n"
+"la columna 1 para iniciar un comentario"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:26
 msgid "Leading and trailing whitespace is not trimmed on keys"
-msgstr ""
+msgstr "Los espacios en blanco incial y final no están recortados en las claves"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:27
 msgid "Leading and trailing whitespace is trimmed on values"
-msgstr ""
+msgstr "Los espacios en blanco incial y final están recortados en los valores"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:28
 msgid "'=' is the only key-termination character (not ':' or whitespace)"
-msgstr ""
+msgstr "'=' es el único caracter de final-de-clave (no ':' o el espacio en blanco)"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:29
 msgid ""
 "Lines without '=' are ignored. It does not store the key with a value of "
 "\"\""
 msgstr ""
+"Las líneas sin '=' son ignoradas. No se guarda la clave con un valor de "
+"\"\""
 
 #: i2p2www/pages/site/docs/spec/configuration.html:30
 msgid ""
 "As there are no escapes, keys may not contain '#', '=', or '\n"
 "', or start with ';'"
 msgstr ""
+"Como no hay caracteres de escape, las claves no pueden contener \n"
+"'#', '=', o '\n"
+"', o comenzar con ';'"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:31
 msgid ""
@@ -22674,12 +19283,21 @@ msgid ""
 "', or start or end with '\r"
 "' or whitespace"
 msgstr ""
+"Como no hay caracteres de escape, los valores no pueden contener \n"
+"'#' o '\n"
+"', o un inicio o final con '\r"
+"' o un espacio en blanco"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:34
 msgid ""
 "The file need not be sorted, but most applications do sort by key when\n"
 "writing to the file, for ease of reading and manual editing."
 msgstr ""
+"El fichero no necesita ser ordenado, pero la mayoría de las aplicaciones"
+" \n"
+"lo ordenan por claves cuando escriben en el fichero, para facilitar la "
+"lectura o \n"
+"la edición manual."
 
 #: i2p2www/pages/site/docs/spec/configuration.html:39
 #, python-format
@@ -22690,10 +19308,17 @@ msgid ""
 "serialized format for I2P protocols specified in\n"
 "Mapping."
 msgstr ""
+"Las lecturas y escrituras están implementadas en las \n"
+" loadProps() y storeProps() de DataHelper (cargar"
+" propiedades y \n"
+"guardar propiedades del ayudante de datos). Observe que el formato de \n"
+"fichero es significativamente diferente que el formato serializado para \n"
+"protocolos I2P especificado en el mapeado."
 
 #: i2p2www/pages/site/docs/spec/configuration.html:48
 msgid "Core library and router"
-msgstr ""
+msgstr "Librería principal y router"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:50
 msgid "Clients"
@@ -22701,68 +19326,82 @@ msgstr "Clientes"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:51
 msgid "Configured via /configclients in the router console."
-msgstr ""
+msgstr "Configurado mediante /configclients en la consola del router."
 
 #: i2p2www/pages/site/docs/spec/configuration.html:55
 msgid "Logger"
-msgstr ""
+msgstr "Registrador (`logger`)"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:56
 msgid "Configured via /configlogging in the router console."
-msgstr ""
+msgstr "Configurado mediante /configlogging en la consola del router."
 
 #: i2p2www/pages/site/docs/spec/configuration.html:60
 msgid "Individual Plugin"
-msgstr ""
+msgstr "Complemento (`plugin`) individual"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:61
 #, python-format
 msgid "See the plugin specification."
 msgstr ""
+"Vea la especificación de plugins "
+"(complementos)."
 
 #: i2p2www/pages/site/docs/spec/configuration.html:66
 msgid "Enable/disable for each installed plugin."
-msgstr ""
+msgstr "Habilitar/deshabilitar para cada complemento (`plugin`) instalado"
+
+#: i2p2www/pages/site/docs/spec/configuration.html:70
+msgid "Router"
+msgstr "Router"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:71
 msgid "Configured via /configadvanced in the router console."
-msgstr ""
+msgstr "Configurado mediante /configadvanced en la consola del router."
+
+#: i2p2www/pages/site/docs/spec/configuration.html:75
+msgid "Applications"
+msgstr "Aplicaciones"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:78
 msgid "See documentation in SusiDNS."
-msgstr ""
+msgstr "Vea la documentación en SusiDNS."
 
 #: i2p2www/pages/site/docs/spec/configuration.html:83
 msgid "Configured via the application gui."
 msgstr ""
+"Configurado mediante la GUI (interfaz gráfica de usuario) de la "
+"aplicación."
 
 #: i2p2www/pages/site/docs/spec/configuration.html:88
 msgid "Configured via the /i2ptunnel application in the router console."
-msgstr ""
+msgstr "Configurado mediante la aplicación /i2ptunnel en la consola del router."
 
 #: i2p2www/pages/site/docs/spec/configuration.html:92
 msgid "Router Console"
-msgstr ""
+msgstr "Consola del router"
 
 #: i2p2www/pages/site/docs/spec/configuration.html:93
 msgid "The router console uses the router.config file."
-msgstr ""
+msgstr "La consola del router usa el fichero `router.config`."
 
 #: i2p2www/pages/site/docs/spec/configuration.html:98
 msgid "See post on zzz.i2p."
-msgstr ""
+msgstr "Vea el post en `zzz.i2p`. "
 
 #: i2p2www/pages/site/docs/spec/datagrams.html:2
 msgid "Datagram Specification"
-msgstr ""
+msgstr "Especificación de datagrama"
 
 #: i2p2www/pages/site/docs/spec/datagrams.html:6
 msgid "See the Datagrams page for an overview of the Datagrams API."
 msgstr ""
+"Vea en la página de datagramas una introducción a la API (interfaz de \n"
+"programación de aplicaciones) de datagramas."
 
 #: i2p2www/pages/site/docs/spec/datagrams.html:12
 msgid "Non-Repliable Datagrams"
-msgstr ""
+msgstr "Datagramas no-respondibles"
 
 #: i2p2www/pages/site/docs/spec/datagrams.html:13
 msgid ""
@@ -22774,10 +19413,16 @@ msgid ""
 "They are not handled by the datagram API.\n"
 "However, SAM and the I2PTunnel classes support \"raw datagrams\"."
 msgstr ""
+"Los datagramas no-respondibles no tienen dirección 'from' (desde) y no \n"
+"están autentificados. Se les llama datagramas \"raw\" (crudos). \n"
+"Estrictamente hablando, no son \"datagramas\" en absoluto, tan solo son \n"
+"datos crudos. No están gestionados por la API de datagramas. Sin embargo,"
+" SAM (mensajería simple anónima) y las clases I2PTunnel \n"
+"soportan \"raw datagrams\"."
 
 #: i2p2www/pages/site/docs/spec/datagrams.html:21
 msgid "Format"
-msgstr ""
+msgstr "Formato"
 
 #: i2p2www/pages/site/docs/spec/datagrams.html:31
 #, python-format
@@ -22789,16 +19434,23 @@ msgid ""
 "currently limit messages to about 32 KB, although this may be raised in "
 "the future."
 msgstr ""
+"La longitud es limitada por las capas más bajas de los protocolos - las "
+"especificaciones de los mensajes de "
+"túnel limita los mensajes a alrededor de 61,2 KB  y los transportes actualmente limitan los mensajes "
+"a alrededro de 32 KB, aunque esto puede aumentarse en el futuro."
 
 #: i2p2www/pages/site/docs/spec/datagrams.html:40
 msgid "Repliable Datagrams"
-msgstr ""
+msgstr "Datagramas respondibles"
 
 #: i2p2www/pages/site/docs/spec/datagrams.html:41
 msgid ""
 "Repliable datagrams contain a 'from' address and a signature. These add "
 "427 bytes of overhead."
 msgstr ""
+"Los datagramas respondibles tiene una dirección 'desde' y una firma. Esto"
+" añade 427 bytes de carga."
 
 #: i2p2www/pages/site/docs/spec/datagrams.html:91
 #, python-format
@@ -22809,24 +19461,32 @@ msgid ""
 "limited to about\n"
 "31.5 KB."
 msgstr ""
+"La longitud es limitada por las capas más bajas de los protocolos - los "
+"transportes actualmente limitan los "
+"mensajes a  32 KB , por lo que la lingitud de los datos está limitada a "
+"alrededor de 31.5 KB."
 
 #: i2p2www/pages/site/docs/spec/datagrams.html:97
 msgid "See important notes above about the reliability of large datagrams."
 msgstr ""
+"Vea las notas importantes arriba sobre la seguridad de los datagramas "
+"largos."
 
 #: i2p2www/pages/site/docs/spec/geoip.html:2
 msgid "GeoIP File Specification"
-msgstr ""
+msgstr "Especificación del archivo GeoIP"
 
 #: i2p2www/pages/site/docs/spec/geoip.html:8
 msgid ""
 "This page specifies the format of the various GeoIP files,\n"
 "used by the router to look up a country for an IP."
 msgstr ""
+"Esta página especifica el formato de varios archivos GEoIP, usados por el"
+" ruter para buscar el país de una IP."
 
 #: i2p2www/pages/site/docs/spec/geoip.html:14
 msgid "Country Name (countries.txt) Format"
-msgstr ""
+msgstr "Formato del nombre del país (countries.txt)"
 
 #: i2p2www/pages/site/docs/spec/geoip.html:15
 msgid ""
@@ -22834,10 +19494,12 @@ msgid ""
 "public sources.\n"
 "For example:"
 msgstr ""
+"Este formato es generado fácilmente a partir de archivos de datos "
+"disponibles en fuentes públicas. Por ejemplo:"
 
 #: i2p2www/pages/site/docs/spec/geoip.html:33
 msgid "IPv4 (geoip.txt) Format"
-msgstr ""
+msgstr "Format IPv4 (geoip.txt)"
 
 #: i2p2www/pages/site/docs/spec/geoip.html:34
 msgid ""
@@ -22845,44 +19507,50 @@ msgid ""
 "available from many public sources.\n"
 "For example:"
 msgstr ""
+"Este formato es tomado prestado de Tor y es fácilmete generado desde "
+"archivos de datos disponibles en fuentes públicas. Por ejemplo:"
 
 #: i2p2www/pages/site/docs/spec/geoip.html:54
 msgid "IPv6 (geoipv6.dat.gz) Format"
-msgstr ""
+msgstr "Formato IPv6 (geoipv6.dat.gz)"
 
 #: i2p2www/pages/site/docs/spec/geoip.html:55
 msgid ""
 "This is a compressed binary format designed for I2P.\n"
 "The file is gzipped. Ungzipped format:"
 msgstr ""
+"Este es un formato binario comprimido diseñado para I2P. El archivo es "
+"comprimido con gzip. Formato descomprimido:"
 
 #: i2p2www/pages/site/docs/spec/geoip.html:71
 msgid "NOTES:"
-msgstr ""
+msgstr "NOTAS:"
 
 #: i2p2www/pages/site/docs/spec/streaming.html:2
 msgid "Streaming Library Specification"
-msgstr ""
+msgstr "Especificación de la librería de streaming"
 
 #: i2p2www/pages/site/docs/spec/streaming.html:6
 msgid "See the Streaming page for an overview of the Streaming Library."
 msgstr ""
+"Vea la página sobre streaming para ver una introducción a la librería de "
+"srteaming."
 
 #: i2p2www/pages/site/docs/spec/streaming.html:11
 msgid "Packet Format"
-msgstr ""
+msgstr "Formato de paquete"
 
 #: i2p2www/pages/site/docs/spec/streaming.html:12
 msgid "The format of a single packet in the streaming protocol is:"
-msgstr ""
+msgstr "El formato para un sólo paquete en el protocolo de streaming es:"
 
 #: i2p2www/pages/site/docs/spec/streaming.html:35
 msgid "Length"
-msgstr ""
+msgstr "Longitud"
 
 #: i2p2www/pages/site/docs/spec/streaming.html:83
 msgid "Flags and Option Data Fields"
-msgstr ""
+msgstr "Flags/Banderas y opciones de los campos de datos"
 
 #: i2p2www/pages/site/docs/spec/streaming.html:84
 msgid ""
@@ -22892,10 +19560,14 @@ msgid ""
 "area\n"
 "in the given order."
 msgstr ""
+"El campo de banderas especifica algunos metadatos sobre el paquete, y a "
+"su vez requiere que se incluyan ciertos datos adicionales. Cualquier "
+"estructura de datos epecificada tiene que ser añadida al area de las "
+"opciones en el orden siguiente."
 
 #: i2p2www/pages/site/docs/spec/updates.html:2
 msgid "I2P Software Update Specification"
-msgstr ""
+msgstr "Especificación de la actualización de I2P"
 
 #: i2p2www/pages/site/docs/spec/updates.html:7
 msgid ""
@@ -22905,6 +19577,12 @@ msgid ""
 "There is a hardcoded backup URL pointing to the project website, in case\n"
 "the default project news host goes down."
 msgstr ""
+"I2P usa un sistema simple, pero seguro, para las actualizaciones "
+"automáticas del software. La consola del ruter periódicamente descarga un"
+" archivo de noticias desde una URL de I2P configurable. Hay una URL de "
+"respaldo incluida en el código del programa apuntando a la web del "
+"proyecto, en caso de que el servidor de noticias que está por defecto se "
+"cayese."
 
 #: i2p2www/pages/site/docs/spec/updates.html:14
 msgid ""
@@ -22915,6 +19593,11 @@ msgid ""
 "If the version is higher than the router's version number, it will\n"
 "display an indication to the user that an update is available."
 msgstr ""
+"El contenido del archivo de noticias se muestra en la página principal de"
+" la consola del ruter. Además, el archivo de noticias contiene el número "
+"de versión más reciente de la aplicación. Si la versión es mayor que la "
+"versión del ruter usado, mostrará una indicación al usuario de que hay "
+"una actualización disponible."
 
 #: i2p2www/pages/site/docs/spec/updates.html:21
 msgid ""
@@ -22922,55 +19605,100 @@ msgid ""
 "version\n"
 "if configured to do so."
 msgstr ""
+"El ruter opcionalmente puede descargar la nueva versión o descargarla e "
+"instalarla. Si se ha configurado para ello."
 
 #: i2p2www/pages/site/docs/spec/updates.html:26
 msgid "News File Specification"
-msgstr ""
+msgstr "Especificación del archivo de noticias"
 
 #: i2p2www/pages/site/docs/spec/updates.html:27
 msgid "The news.xml file may contain the following elements:"
-msgstr ""
+msgstr "El archivo news.xml puede ocntener los siguientes elementos:"
 
 #: i2p2www/pages/site/docs/spec/updates.html:35
 msgid ""
+"Parameters in the i2p.release entry are as follows.\n"
+"All keys are case-insensitive. All values must be enclosed in double "
+"quotes."
+msgstr ""
+"Los parámetros en la entrada i2p.release son como sigue.\n"
+"Todas las claves no distinguen mayúsculas/minúsculas.\n"
+"Todos los valores deben estar encerrados en dobles comillas."
+
+#: i2p2www/pages/site/docs/spec/updates.html:73
+msgid ""
 "The elements may be included inside XML comments to prevent "
 "interpretation by browsers.\n"
-"The i2p.release element and version are required. All others are optional"
-" and are\n"
-"currently unused."
+"The i2p.release element and version are required. All others are "
+"optional.\n"
+"NOTE: Due to parser limitations an entire element must be on a single "
+"line."
 msgstr ""
+"Los elementos puede incluirse dentro de comentarios XML para prevenir\n"
+"que sean interpretados por los navegadores. Se requieren los elementos\n"
+"i2p.release y la versión. Todos los demás son opcionales.\n"
+"NOTA: Debido a las limitaciones del analizador, un elemento completo debe"
+" estar en una sóla línea."
 
-#: i2p2www/pages/site/docs/spec/updates.html:41
-msgid ""
-"The news source is trusted only to indicate that a new version is "
-"available.\n"
-"It does not specify the URL of the update, the checksum, or any other "
-"information."
-msgstr ""
-
-#: i2p2www/pages/site/docs/spec/updates.html:47
+#: i2p2www/pages/site/docs/spec/updates.html:80
 msgid "Update File Specification"
-msgstr ""
+msgstr "Especificación del archivo de actualizaciones"
 
-#: i2p2www/pages/site/docs/spec/updates.html:48
+#: i2p2www/pages/site/docs/spec/updates.html:81
+msgid ""
+"As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n"
+"use the \"su3\" file format specified below.\n"
+"Approved release signers will use 4096-bit RSA keys.\n"
+"The X.509 public key certificates for these signers are distributed in "
+"the router installation packages.\n"
+"The updates may contain certificates for new, approved signers, and/or "
+"contain\n"
+"a list of certificates to delete for revocation."
+msgstr ""
+"Desde la versión 0.9.9, el fichero de actualización firmado, llamado\n"
+"i2pupdate.su3, usa el formato de fichero \"su3\" especificado debajo.\n"
+"Los firmantes aprobados de la versión usarán claves RSA de 4096-bits.\n"
+"Los certificados de clave pública X.509 para estos firmantes se "
+"distribuyen\n"
+"en los paquetes de instalación del router. Las actualizaciones pueden\n"
+"contener certificados para nuevos firmantes aprobados, y/o contener\n"
+"una lista de certificados a borrar para revocación."
+
+#: i2p2www/pages/site/docs/spec/updates.html:91
+msgid "Old Update File Specification"
+msgstr "Antigua especificación de fichero de actualización"
+
+#: i2p2www/pages/site/docs/spec/updates.html:92
+msgid "This format is obsolte as of release 0.9.9."
+msgstr "Este formato está obsoleto desde la versión 0.9.9."
+
+#: i2p2www/pages/site/docs/spec/updates.html:95
 msgid ""
 "The signed update file, traditionally named i2pupdate.sud,\n"
 "is simply a zip file with a prepended 56 byte header.\n"
 "The header contains:"
 msgstr ""
+"El archivo firmado de actualizaciones, tradicionalmente llamado "
+"i2pupdate.sud, no es más que un archivo zip con una cabecera de 56 bytes "
+"antepuesta. La cabecera contiene:"
 
-#: i2p2www/pages/site/docs/spec/updates.html:54
+#: i2p2www/pages/site/docs/spec/updates.html:101
 #, python-format
 msgid ""
 "A 40-byte DSA "
 "signature"
 msgstr ""
+"Una firma DSA de 40 "
+"bytes"
 
-#: i2p2www/pages/site/docs/spec/updates.html:57
+#: i2p2www/pages/site/docs/spec/updates.html:104
 msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary"
 msgstr ""
+"La versión de I2P de 16 bytes en UTF-8, rellenada con ceros si es "
+"necesario."
 
-#: i2p2www/pages/site/docs/spec/updates.html:62
+#: i2p2www/pages/site/docs/spec/updates.html:109
 #, python-format
 msgid ""
 "The signature covers only the zip archive - not the prepended version.\n"
@@ -22980,15 +19708,23 @@ msgid ""
 "which has a hardcoded default list of keys of the current project release"
 " managers."
 msgstr ""
+"La firma sólo cubre el archivo zip - no la versión antepuesta. La firma "
+"tiene que coincidir una de las claves públicas "
+"DSA configuradas en el ruter, el cual tiene en el código las claves "
+"de los administradores actuales del proyecto."
 
-#: i2p2www/pages/site/docs/spec/updates.html:68
+#: i2p2www/pages/site/docs/spec/updates.html:115
 msgid ""
 "For version comparison purposes, version fields contain [0-9]*, field "
 "separators are\n"
 "'-', '_', and '.', and all other characters are ignored."
 msgstr ""
+"Para comparar las versiones, los campos de versiones contienen [0-9]*, "
+"los separadores de campos son '-', '_', y '.', y los demás caracteres son"
+" ignorados."
 
-#: i2p2www/pages/site/docs/spec/updates.html:73
+#: i2p2www/pages/site/docs/spec/updates.html:120
 msgid ""
 "As of version 0.8.8, the version must also be specified as a zip file "
 "comment in UTF-8,\n"
@@ -22999,12 +19735,18 @@ msgid ""
 "signature.\n"
 "This prevents spoofing of the version number in the header."
 msgstr ""
+"A partir de la versión 0.8.8, la versión tiene también que ser "
+"especificada como un comentario en el archivo zip en UTF-8, sin ceros a "
+"la derecha. El ruter actualizándose verifica que la versión en la "
+"cabecera (no cubierta por la firma) coincide con la versión en el "
+"comentario del archivo zip, el cual si está cubierto por la firma. Esto "
+"previene la falsificación del número de versión en la cabecera."
 
-#: i2p2www/pages/site/docs/spec/updates.html:81
+#: i2p2www/pages/site/docs/spec/updates.html:128
 msgid "Download and Installation"
-msgstr ""
+msgstr "Descarga e instalación"
 
-#: i2p2www/pages/site/docs/spec/updates.html:82
+#: i2p2www/pages/site/docs/spec/updates.html:129
 msgid ""
 "The router first downloads the header of the update file from one in a "
 "configurable list of I2P URLs,\n"
@@ -23019,22 +19761,41 @@ msgid ""
 "verifes that the zip file comment matches the header version, as "
 "explained above."
 msgstr ""
+"El ruter primero descarga la cabecera del archivo de actualización de una"
+" lista configurable de URLs de I2P, usando el cliente HTTP y el proxy "
+"incluidos en él, y comprueba si la versión es más nueva. Esto soluciona "
+"el problema de que los servidores no tengan el último archivo. Entonces "
+"el ruter descarga el archivo de la actualización completa. El ruter "
+"verifica que la versión del archivo es más nueva antes de instalarlo. "
+"También, por supuesto, verifica la firma, y verifica que el comentario "
+"del archivo zip coincida con la versión de la cabecera, como se ha "
+"explicado antes."
 
-#: i2p2www/pages/site/docs/spec/updates.html:93
+#: i2p2www/pages/site/docs/spec/updates.html:140
 msgid "The zip file is extracted in the base $I2P installation directory."
-msgstr ""
+msgstr "El archivo zip es extraído en el directorio base de instalación de $i2P."
 
-#: i2p2www/pages/site/docs/spec/updates.html:97
+#: i2p2www/pages/site/docs/spec/updates.html:144
 msgid ""
 "As of release 0.7.12, the router supports Pack200 decompression.\n"
 "Files inside the zip archive with a .jar.pack or .war.pack suffix\n"
 "are transparently decompressed to a .jar or .war file.\n"
 "Update files containing .pack files are traditionally named with a '.su2'"
 " suffix.\n"
-"Pack200 shrinks the update files by about 60%."
+"Pack200 shrinks the update files by about 60%."
 msgstr ""
+"Desde la versión 0.7.12, el router soporta decompresión Pack200. Los \n"
+"ficheros dentro del archivo zip con un sufijo '.jar.pack' o '.war.pack' "
+"son \n"
+"descomprimidos transparentemente a un fichero '.jar' o '.war'. Los "
+"archivos \n"
+"de actualización conteniendo ficheros .pack son nombrados "
+"tradicionalmente \n"
+"con un sufijo '.su2'. Pack200 constriñe los ficheros de actualización "
+"cerca \n"
+"de un 60%."
 
-#: i2p2www/pages/site/docs/spec/updates.html:105
+#: i2p2www/pages/site/docs/spec/updates.html:152
 msgid ""
 "As of release 0.8.7, the router will delete the libjbigi.so and "
 "libjcpuid.so files\n"
@@ -23042,119 +19803,149 @@ msgid ""
 "will\n"
 "be extracted from jbigi.jar."
 msgstr ""
+"A partir de la versión 0.8.7, el ruter borrará los archivos libjbigi.so y"
+" libjcpuid.so si el archivo zip contiene un archivo lib/jbigi.jar, para "
+"que los nuevos archivos sean extraídos desde jbigi.jar."
 
-#: i2p2www/pages/site/docs/spec/updates.html:111
+#: i2p2www/pages/site/docs/spec/updates.html:158
 msgid ""
 "As of release 0.8.12, if the zip archive contains a file deletelist.txt, "
 "the router will\n"
 "delete the files listed there. The format is:"
 msgstr ""
+"A partir de la versión 0.8.12, el archivo zip contiene un archivo "
+"deletelist.txt, el ruter borrará los archivos listados ahí. Su formato "
+"es:"
 
-#: i2p2www/pages/site/docs/spec/updates.html:116
+#: i2p2www/pages/site/docs/spec/updates.html:163
 msgid "One file name per line"
-msgstr ""
+msgstr "Un nombre de archivo en cada línea"
 
-#: i2p2www/pages/site/docs/spec/updates.html:117
+#: i2p2www/pages/site/docs/spec/updates.html:164
 msgid ""
 "All file names are relative to the installation directory; no absolute "
 "file names allowed, no files starting with \"..\""
 msgstr ""
+"Los nombres de archivos son relativos al directorio de instalación; no se"
+" permiten nombres de archivos absolutos, ni archivos que comiencen por "
+"\"..\""
 
-#: i2p2www/pages/site/docs/spec/updates.html:118
+#: i2p2www/pages/site/docs/spec/updates.html:165
 msgid "Comments start with '#'"
-msgstr ""
+msgstr "Los comentarios comienzan con '#'"
 
-#: i2p2www/pages/site/docs/spec/updates.html:121
+#: i2p2www/pages/site/docs/spec/updates.html:168
 msgid "The router will then delete the deletelist.txt file."
-msgstr ""
+msgstr "El ruter borrará entonces el archivo deletelist.txt."
 
-#: i2p2www/pages/site/docs/spec/updates.html:126
+#: i2p2www/pages/site/docs/spec/updates.html:173
 msgid "New \"su3\" Update File Specification"
-msgstr ""
+msgstr "Nueva especificación para el archivo de actualizaciones \"su3\""
 
-#: i2p2www/pages/site/docs/spec/updates.html:128
-msgid "This specification is preliminary and is not yet implemented."
+#: i2p2www/pages/site/docs/spec/updates.html:175
+msgid ""
+"This specification is used for router updates and reseed data as of "
+"release 0.9.9."
 msgstr ""
+"Esta especificación se usa por las actualizaciones del router y por los "
+"datos de resembrado ('reseed') desde la versión 0.9.9. "
 
-#: i2p2www/pages/site/docs/spec/updates.html:132
-msgid "Issues with existing .sud/.su2 format:"
-msgstr ""
+#: i2p2www/pages/site/docs/spec/updates.html:179
+msgid "Issues with the previous .sud/.su2 format:"
+msgstr "Problemas con el anterior formato .sud/.su2:"
 
-#: i2p2www/pages/site/docs/spec/updates.html:134
+#: i2p2www/pages/site/docs/spec/updates.html:181
 msgid "No magic number or flags"
-msgstr ""
+msgstr "Sin números mágicos o banderas"
 
-#: i2p2www/pages/site/docs/spec/updates.html:137
+#: i2p2www/pages/site/docs/spec/updates.html:184
 msgid "No way to specify compression, pack200 or not, or signing algo"
 msgstr ""
+"No hay forma de especificar compresión, pack200 o no, o algoritmo de "
+"firma."
 
-#: i2p2www/pages/site/docs/spec/updates.html:140
+#: i2p2www/pages/site/docs/spec/updates.html:187
 msgid ""
 "Version is not covered by signature, so it is enforced by requiring it\n"
 "to be in the zip file comment (for router files) or in the plugin.config\n"
 "file (for plugins)"
 msgstr ""
+"La versión no está cubierta por la firma, lo que se consigue requiriendo "
+"que esté en el comentario del archivo zip (para los archivos del ruter) o"
+" en el archivo plugin.config (para los aomplementos)"
 
-#: i2p2www/pages/site/docs/spec/updates.html:145
+#: i2p2www/pages/site/docs/spec/updates.html:192
 msgid "Signer not specified so verifier must try all known keys"
 msgstr ""
+"El firmante no se especifica, por lo que el que lo verifica tiene que "
+"conocer todas las claves"
 
-#: i2p2www/pages/site/docs/spec/updates.html:148
+#: i2p2www/pages/site/docs/spec/updates.html:195
 msgid "Signature-before-data format requires two passes to generate file"
 msgstr ""
+"El formato de firma-antes-que-datos requiere 2 pasadas para generar el "
+"archivo."
 
-#: i2p2www/pages/site/docs/spec/updates.html:154
+#: i2p2www/pages/site/docs/spec/updates.html:201
 msgid "Goals:"
-msgstr ""
+msgstr "Objetivos:"
 
-#: i2p2www/pages/site/docs/spec/updates.html:157
+#: i2p2www/pages/site/docs/spec/updates.html:204
 msgid "Fix above problems"
-msgstr ""
+msgstr "Arreglas los problemas anteriores"
 
-#: i2p2www/pages/site/docs/spec/updates.html:160
+#: i2p2www/pages/site/docs/spec/updates.html:207
 msgid "Migrate to more secure signature algorithm"
-msgstr ""
+msgstr "Cambiar a un algoritmo de firma más seguro"
 
-#: i2p2www/pages/site/docs/spec/updates.html:163
+#: i2p2www/pages/site/docs/spec/updates.html:210
 msgid ""
 "Keep version info in same format and offset for compatibility with\n"
 "existing version checkers"
 msgstr ""
+"Mantener la información de versión en el mismo formato y lugar para que "
+"siga siendo compatible con las versiones de los los verificadores ya "
+"existentes"
 
-#: i2p2www/pages/site/docs/spec/updates.html:169
+#: i2p2www/pages/site/docs/spec/updates.html:216
 msgid "Specification:"
-msgstr ""
+msgstr "Especificación:"
 
-#: i2p2www/pages/site/docs/spec/updates.html:217
+#: i2p2www/pages/site/docs/spec/updates.html:275
 msgid "All unused fields must be set to 0 for compatibility with future versions."
 msgstr ""
+"Por compatibilidad, todos los campos no usados tienen que ser 0 en las "
+"futuras versiones."
 
-#: i2p2www/pages/site/docs/spec/updates.html:224
+#: i2p2www/pages/site/docs/spec/updates.html:282
 msgid ""
 "The network will eventually grow too large for update over HTTP.\n"
 "The built-in BitTorrent client, i2psnark, may be used as a distributed "
 "update method.\n"
 "This development effort is ongoing and should be completed by late 2013."
 msgstr ""
+"La red puede crecer demasiado como para actualizar por HTTP. El cliente "
+"de torrents integrado i2psnark puede usarse como un método de "
+"actualización distribuido. Este esfuerzo de desarrollo continúa, y "
+"debería estar completo en el 2013."
 
-#: i2p2www/pages/site/docs/spec/updates.html:229
+#: i2p2www/pages/site/docs/spec/updates.html:287
 msgid ""
 "The router update mechanism is part of the web router console.\n"
 "There is currently no provision for updates of an embedded router lacking"
 " the router console."
 msgstr ""
+"El mecanismo de actualización del ruter es parte de la web de la consola "
+"de ruter. Por el momento no hay posibilidad de actualizar un ruter "
+"embebido que carezca de la consola del ruter."
 
 #: i2p2www/pages/site/docs/transport/index.html:2
 msgid "Transport Overview"
-msgstr ""
-
-#: i2p2www/pages/site/docs/transport/index.html:3
-msgid "April 2013"
-msgstr ""
+msgstr "Introducción al los Transportes"
 
 #: i2p2www/pages/site/docs/transport/index.html:6
 msgid "Transports in I2P"
-msgstr ""
+msgstr "Transportes den I2P"
 
 #: i2p2www/pages/site/docs/transport/index.html:8
 msgid ""
@@ -23166,148 +19957,206 @@ msgid ""
 "contacted \n"
 "is the one who should receive a given message."
 msgstr ""
+"Un \"transporte\" en I2P es un método para la comunicación directa de "
+"punto a punto entre dos ruters. Los transportes tienen que proporcionar "
+"confidencialidad e integridad contra adversarios externos a la vez que se"
+" aseguran de que el ruter contactado es el que recibe el mensaje "
+"indicado."
 
 #: i2p2www/pages/site/docs/transport/index.html:16
 msgid ""
 "I2P supports multiple transports simultaneously.\n"
 "There are two transports currently implemented:"
 msgstr ""
+"I2P soporta múltiples transportes a la vez. Actualmente hay dos "
+"transportes implementados:"
 
 #: i2p2www/pages/site/docs/transport/index.html:21
 #, python-format
 msgid "NTCP, a Java New I/O (NIO) TCP transport"
-msgstr ""
+msgstr "NTCP, un nuevo transporte I/O (NIO) TCP en Java"
 
 #: i2p2www/pages/site/docs/transport/index.html:22
 #, python-format
 msgid " SSU, or Secure Semireliable UDP"
-msgstr ""
+msgstr "SSU, o UDP seguro semi-fiable"
 
 #: i2p2www/pages/site/docs/transport/index.html:25
 msgid ""
 "Each provides a \"connection\" paradigm, with authentication,\n"
 "flow control, acknowledgments and retransmission."
 msgstr ""
+"Cada uno proporciona un modelo de \"conexión\", con autenticación control"
+" de flujo, contestaciones y retransmisión."
 
 #: i2p2www/pages/site/docs/transport/index.html:31
 msgid "Transport Services"
-msgstr ""
+msgstr "Servicios de trasnporte"
 
 #: i2p2www/pages/site/docs/transport/index.html:33
 msgid "The transport subsystem in I2P provides the following services:"
-msgstr ""
+msgstr "El sub-sistema de transportes en I2P proporciona los siguientes servicios:"
 
 #: i2p2www/pages/site/docs/transport/index.html:37
+#, python-format
+msgid ""
+"Reliable delivery of I2NP messages.\n"
+"Transports support I2NP message delivery ONLY.\n"
+"They are not general-purpose data pipes."
+msgstr ""
+"Entrega confiable de mensajes I2NP.\n"
+"Los transportes soportan SÓLO la entrega de mensajes I2NP.\n"
+"No son conductos de datos de propósito general."
+
+#: i2p2www/pages/site/docs/transport/index.html:42
 msgid ""
 "Maintain a set of router addresses, one or more for each transport,\n"
 "that the router publishes as its global contact information (the "
-"RouterInfo)"
+"RouterInfo).\n"
+"Each transport may connect using one of these addresses, which may be\n"
+"IPv4 or (as of version 0.9.8) IPv6."
 msgstr ""
+"Mantiene un conjunto de direcciones de routers, una o más para cada "
+"transporte,\n"
+"que el router publica como su información global de contacto (la "
+"RouterInfo).\n"
+"Cada transporte puede conectarse usando una de estas direcciones,\n"
+"que pueden ser IPv4 o (desde la versión 0.9.8) IPv6."
 
-#: i2p2www/pages/site/docs/transport/index.html:41
+#: i2p2www/pages/site/docs/transport/index.html:48
 msgid "Selection of the best transport for each outgoing message"
-msgstr ""
+msgstr "Selección del mejor transporte para cada mensaje saliente"
 
-#: i2p2www/pages/site/docs/transport/index.html:42
+#: i2p2www/pages/site/docs/transport/index.html:49
 msgid "Queueing of outbound messages by priority"
-msgstr ""
+msgstr "Poner en cola los mensajes salientes según la prioridad"
 
-#: i2p2www/pages/site/docs/transport/index.html:43
+#: i2p2www/pages/site/docs/transport/index.html:50
 msgid ""
 "Bandwidth limiting, both outbound and inbound, according to router "
 "configuration"
 msgstr ""
+"Límite de ancho de banda, de entrada  y de salida, de acuerdo con la "
+"configuración del ruter."
 
-#: i2p2www/pages/site/docs/transport/index.html:44
+#: i2p2www/pages/site/docs/transport/index.html:51
 msgid "Setup and teardown of transport connections"
-msgstr ""
+msgstr "Configuración y desmontaje de las conexiones de trasnporte"
 
-#: i2p2www/pages/site/docs/transport/index.html:45
+#: i2p2www/pages/site/docs/transport/index.html:52
 msgid "Encryption of point-to-point communications"
-msgstr ""
+msgstr "Cifrado de las comunicaciones de fin a fin."
 
-#: i2p2www/pages/site/docs/transport/index.html:46
+#: i2p2www/pages/site/docs/transport/index.html:53
 msgid ""
 "Maintenance of connection limits for each transport, implementation of "
 "various thresholds for these limits,\n"
 "and communication of threshold status to the router so it may make "
 "operational changes based on the status"
 msgstr ""
+"Mantenimiento y límites de conexión para cada transporte, implementación "
+"de varios umbrales para esos límites, y la comunicación del estado de "
+"esos umbrales al ruter para que pueda hacer cambios operacionales basados"
+" en su estado."
 
-#: i2p2www/pages/site/docs/transport/index.html:50
+#: i2p2www/pages/site/docs/transport/index.html:57
 msgid "Firewall port opening using UPnP (Universal Plug and Play)"
-msgstr ""
+msgstr "Abrir puertos en el cortafuegos usando UPnP (Universal Plug and Play)"
 
-#: i2p2www/pages/site/docs/transport/index.html:51
+#: i2p2www/pages/site/docs/transport/index.html:58
 msgid "Cooperative NAT/Firewall traversal"
-msgstr ""
+msgstr "NAT/Cortafuegos cooperativo trasversal"
 
-#: i2p2www/pages/site/docs/transport/index.html:52
+#: i2p2www/pages/site/docs/transport/index.html:59
 msgid ""
 "Local IP detection by various methods, including UPnP, inspection of "
 "incoming connections, and enumeration of network devices"
 msgstr ""
+"Detección de la IP local por varios métodos, incluyendo UPnP, inspección "
+"de los paquetes entrantes y enumeración de los dispositivos de red"
 
-#: i2p2www/pages/site/docs/transport/index.html:53
+#: i2p2www/pages/site/docs/transport/index.html:60
 msgid ""
 "Coordination of firewall status and local IP, and changes to either, "
 "among the transports"
 msgstr ""
+"Coordinación del estado del cortafuegos y la IP local, y sus cambios, a "
+"lo largo de los transportes "
 
-#: i2p2www/pages/site/docs/transport/index.html:54
-#: i2p2www/pages/site/docs/transport/ssu.html:32
+#: i2p2www/pages/site/docs/transport/index.html:61
+#: i2p2www/pages/site/docs/transport/ssu.html:33
 msgid ""
 "Communication of firewall status and local IP, and changes to either, to "
 "the router and the user interface"
 msgstr ""
+"Coordinación del estado del cortafuegos y la IP local, y sus cambios, con"
+" el ruter y el interfaz del usuario"
 
-#: i2p2www/pages/site/docs/transport/index.html:55
+#: i2p2www/pages/site/docs/transport/index.html:62
 msgid ""
 "Determination of a consensus clock, which is used to periodically update "
 "the router's clock, as a backup for NTP"
 msgstr ""
+"Determinación de un reloj consensuado, que se usa para actualizar "
+"periódicamente  el reloj del ruter, como respaldo para NTP"
 
-#: i2p2www/pages/site/docs/transport/index.html:56
+#: i2p2www/pages/site/docs/transport/index.html:63
 msgid ""
 "Maintenance of status for each peer, including whether it is connected, "
 "whether it was recently connected,\n"
 "and whether it was reachable in the last attempt"
 msgstr ""
+"Mantenimiento del estado de cada par, incluyendo cuando está conectado, "
+"si se ha conectado recientemente y si estaba accesible en el último "
+"intento."
 
-#: i2p2www/pages/site/docs/transport/index.html:60
+#: i2p2www/pages/site/docs/transport/index.html:67
 msgid "Qualification of valid IP addresses according to a local rule set"
-msgstr ""
+msgstr "Calificación de una IP válida de acuerdo con un grupo de normas locales."
 
-#: i2p2www/pages/site/docs/transport/index.html:61
+#: i2p2www/pages/site/docs/transport/index.html:68
 msgid ""
 "Honoring the automated and manual lists of banned peers maintained by the"
 " router,\n"
 "and refusing outbound and inbound connections to those peers"
 msgstr ""
+"Honrar las listas manuales y automáticas mantenidas por el ruter de los "
+"pares baneados, y denegar las conexiones entrantes o salientes a esos "
+"pares"
 
-#: i2p2www/pages/site/docs/transport/index.html:68
+#: i2p2www/pages/site/docs/transport/index.html:75
 msgid "Transport Addresses"
-msgstr ""
+msgstr "Direcciones de trasnporte"
 
-#: i2p2www/pages/site/docs/transport/index.html:70
+#: i2p2www/pages/site/docs/transport/index.html:77
 msgid ""
 "The transport subsystem maintains a set of router addresses, each of "
 "which lists a transport method, IP, and port.\n"
 "These addresses constitute the advertised contact points, and are "
-"published by the router to the network database."
+"published by the router to the network database.\n"
+"Addresses may also contain an arbitrary set of additional options."
 msgstr ""
+"El subsistema de transporte mantiene un conjunto de direcciones de "
+"router, cada una de las cuales lista un método de transporte, IP, y "
+"puerto.\n"
+"Estas direcciones constituyen los puntos de contacto anunciados, y son "
+"publicadas por el router en la base de datos de red.\n"
+"Las direcciones también pueden contener un conjunto arbitrario de "
+"opciones adicionales."
 
-#: i2p2www/pages/site/docs/transport/index.html:75
+#: i2p2www/pages/site/docs/transport/index.html:83
 msgid "Typical scenarios are:"
-msgstr ""
+msgstr "Los espenarios típicos son:"
 
-#: i2p2www/pages/site/docs/transport/index.html:77
+#: i2p2www/pages/site/docs/transport/index.html:85
 msgid ""
 "A router has no published addresses, so it is considered \"hidden\" and "
 "cannot receive incoming connections"
 msgstr ""
+"Un ruter no tiene direcciones publicadas, con lo que es considerado "
+"\"oculto\" y no puede recibir conexiones entrantes"
 
-#: i2p2www/pages/site/docs/transport/index.html:78
+#: i2p2www/pages/site/docs/transport/index.html:86
 #, python-format
 msgid ""
 "A router is firewalled, and therefore publishes an SSU address which "
@@ -23315,23 +20164,30 @@ msgid ""
 "peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)"
 msgstr ""
+"Un ruter esta bloqueado por el cortafuegos, y por lo tanto publica una "
+"dirección SSU la cual contiene una lista de pares cooperantes o "
+"\"introductores\" que ayudarán con el NAT transversal (vea la especificación SSU para más detalles)"
 
-#: i2p2www/pages/site/docs/transport/index.html:82
+#: i2p2www/pages/site/docs/transport/index.html:90
 msgid ""
 "A router is not firewalled or its NAT ports  are open; it publishes both "
 "NTCP and SSU addresses containing\n"
 "directly-accessible IP and ports."
 msgstr ""
+"Un ruter no esta bloqueado por el firewall o sus puertos NAT están "
+"abiertos; publica ambas direcciones, NTCP y SSU, que contiene la IP y los"
+" puertos accesibles."
 
-#: i2p2www/pages/site/docs/transport/index.html:88
+#: i2p2www/pages/site/docs/transport/index.html:96
 msgid "Transport Selection"
-msgstr ""
+msgstr "Selección del transporte"
 
-#: i2p2www/pages/site/docs/transport/index.html:90
+#: i2p2www/pages/site/docs/transport/index.html:98
 #, python-format
 msgid ""
-"The transport system delivers I2NP messages. The"
-" transport selected for any message is\n"
+"The transport system delivers I2NP messages "
+"only. The transport selected for any message is\n"
 "independent of the upper-layer protocols and contents (router or client "
 "messages, whether an external application was using\n"
 "TCP or UDP to connect to I2P, whether the upper layer was using\n"
@@ -23342,8 +20198,19 @@ msgid ""
 "datagrams\n"
 "etc.)."
 msgstr ""
+"El sistema de transporte entrega sólo mensajes I2NP "
+"messages. El trasporte\n"
+"seleccionado por cualquier mensaje es independiente de las capas-"
+"superiores\n"
+"de protocolos y contenidos (mensajes de cliente o router, si una "
+"aplicación\n"
+"externa estaba usando TCP o UDP para conectarse a I2P, si la capa "
+"superior\n"
+"estaba usando el streaming o los datagramas"
+" de la\n"
+"librería streaming, datagramas, etc.)."
 
-#: i2p2www/pages/site/docs/transport/index.html:104
+#: i2p2www/pages/site/docs/transport/index.html:112
 msgid ""
 "For each outgoing message, the transport system solicits \"bids\" from "
 "each transport.\n"
@@ -23351,85 +20218,92 @@ msgid ""
 "the message for delivery.\n"
 "A transport may refuse to bid."
 msgstr ""
+"Para cada mensaje saliente, el sistema de transporte solicita \"ofertas\""
+" de cada transporte. El transporte que ofrece el valor más bajo (mejor) "
+"gana la apuesta y recibe el mensaje para ser entregado. Un transporte "
+"puede negarse a apostar."
 
-#: i2p2www/pages/site/docs/transport/index.html:110
+#: i2p2www/pages/site/docs/transport/index.html:118
 msgid "Whether a transport bids, and with what value, depend on numerous factors:"
 msgstr ""
+"Si un transporte apuesta o no, y con qué valor, depende de numerosos "
+"factores:"
 
-#: i2p2www/pages/site/docs/transport/index.html:114
+#: i2p2www/pages/site/docs/transport/index.html:122
 msgid "Configuration of transport preferences"
-msgstr ""
+msgstr "Configuarión de las preferencias de trasnporte"
 
-#: i2p2www/pages/site/docs/transport/index.html:115
+#: i2p2www/pages/site/docs/transport/index.html:123
 msgid "Whether the transport is already connected to the peer"
-msgstr ""
+msgstr "Si el transporte ya está conectado al par"
 
-#: i2p2www/pages/site/docs/transport/index.html:116
+#: i2p2www/pages/site/docs/transport/index.html:124
 msgid ""
 "The number of current connections compared to various connection limit "
 "thresholds"
 msgstr ""
+"El número de las conexiones actuales comparado con varios límites de "
+"conexión."
 
-#: i2p2www/pages/site/docs/transport/index.html:117
+#: i2p2www/pages/site/docs/transport/index.html:125
 msgid "Whether recent connection attempts to the peer have failed"
-msgstr ""
+msgstr "Si un intento de conexión reciente ha fallado"
 
-#: i2p2www/pages/site/docs/transport/index.html:118
+#: i2p2www/pages/site/docs/transport/index.html:126
 msgid ""
 "The size of the message, as different transports have different size "
 "limits"
 msgstr ""
+"El tamaño del mensaje, ya que diferentes transportes tienen diferentes "
+"límites de tamaño"
 
-#: i2p2www/pages/site/docs/transport/index.html:119
+#: i2p2www/pages/site/docs/transport/index.html:127
 msgid ""
 "Whether the peer can accept incoming connections for that transport, as "
 "advertised in its RouterInfo"
 msgstr ""
+"Si el par puede aceptar conexiones entrantes para ese transporte, como se"
+" indica en su RouterInfo"
 
-#: i2p2www/pages/site/docs/transport/index.html:120
+#: i2p2www/pages/site/docs/transport/index.html:128
 msgid "Whether the connection would be indirect (requiring introducers) or direct"
-msgstr ""
+msgstr "Si la conexión debería ser indirecta (requiriendo introductores) o directa"
 
-#: i2p2www/pages/site/docs/transport/index.html:121
+#: i2p2www/pages/site/docs/transport/index.html:129
 msgid "The peer's transport preference, as advertised in its RouterInfo"
-msgstr ""
+msgstr "El transporte preferido por el par, como se anuncia en el RouterInfo"
 
-#: i2p2www/pages/site/docs/transport/index.html:124
+#: i2p2www/pages/site/docs/transport/index.html:132
 msgid ""
 "In general, the bid values are selected so that two routers are only "
 "connected by a single transport\n"
 "at any one time. However, this is not a requirement."
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/index.html:131
-msgid "New Transports and Future Work"
-msgstr ""
-
-#: i2p2www/pages/site/docs/transport/index.html:133
-msgid "Additional transports may be developed, including:"
-msgstr ""
-
-#: i2p2www/pages/site/docs/transport/index.html:138
-msgid "A TLS/SSH look-alike transport"
-msgstr ""
+"En general, los valores de las ofertas son seleccionados para que los "
+"ruters sólo estén conectados a un solo transporte a la vez. Aunque esto "
+"no es obligatorio."
 
 #: i2p2www/pages/site/docs/transport/index.html:139
+msgid "New Transports and Future Work"
+msgstr "Nuevos transportes y trabajos futuros"
+
+#: i2p2www/pages/site/docs/transport/index.html:141
+msgid "Additional transports may be developed, including:"
+msgstr "Puede que se desarrollen transportes adicionales, incluyendo:"
+
+#: i2p2www/pages/site/docs/transport/index.html:146
+msgid "A TLS/SSH look-alike transport"
+msgstr "Un transporte que parezca TLS/SSH"
+
+#: i2p2www/pages/site/docs/transport/index.html:147
 msgid ""
 "An \"indirect\" transport for routers that are not reachable by all other"
 " routers (one form of \"restricted routes\")"
 msgstr ""
+"Un transporte \"indirecto\" para los ruters que no sean accesibles por "
+"todos los otros ruters (una forma de \"ruters restringidos\")"
 
-#: i2p2www/pages/site/docs/transport/index.html:142
-#, python-format
-msgid ""
-"IPv6: The existing transports must be enhanced to support multiple "
-"addresses within a single transport,\n"
-"including IPV6 addresses. Currently, a transport may only advertise a "
-"single IPV4 address.\n"
-"See this thread for discussion."
-msgstr ""
-
-#: i2p2www/pages/site/docs/transport/index.html:148
+#: i2p2www/pages/site/docs/transport/index.html:150
 msgid ""
 "Work continues on adjusting default connection limits for each transport."
 "\n"
@@ -23439,8 +20313,14 @@ msgid ""
 "connection limits, and by\n"
 "routers that are behind restrictive state firewalls (restricted routes)."
 msgstr ""
+"Seguimos trabajando para ajustar los límites de las conexiones de cada "
+"transporte. I2P está diseñado como una \"red mesh\", donde se asume que "
+"cada ruter puede conectar con cualquier otro ruter. Esta asunción puede "
+"ser falsa para los ruter que han excedido los límites de conexiones, y "
+"para los ruters detrás de cortafuegos de estado restrictivos (rutas "
+"restringidas)."
 
-#: i2p2www/pages/site/docs/transport/index.html:155
+#: i2p2www/pages/site/docs/transport/index.html:157
 msgid ""
 "The current connection limits are higher for SSU than for NTCP, based on "
 "the assumption that\n"
@@ -23450,18 +20330,29 @@ msgid ""
 "on the Java heap,\n"
 "that assumption is difficult to verify."
 msgstr ""
+"Los actuales límites de la conexión son más altos para SSU (UDP seguro \n"
+"semiconfiable) que para NTCP (TCP basado en NIO), partiendo de asumir \n"
+"que los requisitos de memoria para una conexión NTCP son mayores que \n"
+"para una SSU. Sin embargo, como los buffers (prealmacenamiento) NTCP "
+"están parcialmente en el kernel (núcleo del sistema) y los buffers SSU "
+"están en la pila de Java, esa asunción es difícil de verificar."
 
-#: i2p2www/pages/site/docs/transport/index.html:162
+#: i2p2www/pages/site/docs/transport/index.html:164
 #, python-format
 msgid ""
 "Analyze Breaking and Improving Protocol "
 "Obfuscation\n"
 "and see how transport-layer padding may improve things."
 msgstr ""
+"Analice Breaking and Improving Protocol "
+"Obfuscation (rompiendo y \n"
+"mejorando el protocolo de ofuscación) y vea como usar datos de relleno \n"
+"(descartables criptográficamente) en la capa-de-transporte puede mejorar "
+"las cosas."
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:6
 msgid "NTCP (NIO-based TCP)"
-msgstr ""
+msgstr "NTCP (TCP basado-en-NIO)"
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:8
 #, python-format
@@ -23471,10 +20362,19 @@ msgid ""
 "The other is SSU.\n"
 "NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n"
 "Java NIO (new I/O) does not suffer from the 1 thread per connection "
-"issues of the old TCP transport."
+"issues of the old TCP transport.\n"
+"NTCP-over-IPv6 is supported as of version 0.9.8."
 msgstr ""
+"NTCP es uno de los dos transportes "
+"implementados actualmente\n"
+"en I2P. El otro es SSU.\n"
+"NTCP es un transporte basado en Java NIO introducido en la versión "
+"0.6.1.22.\n"
+"Java NIO (nueva entrada/salida) no adolece de los problemas de\n"
+"1 hilo por conexión del antiguo transporte TCP.\n"
+"NTCP-sobre-IPv6 está soportado desde la versión 0.9.8."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:15
+#: i2p2www/pages/site/docs/transport/ntcp.html:16
 msgid ""
 "By default, NTCP uses the IP/Port\n"
 "auto-detected by SSU. When enabled on config.jsp,\n"
@@ -23482,31 +20382,47 @@ msgid ""
 "or when the firewall status changes.\n"
 "Now you can enable inbound TCP without a static IP or dyndns service."
 msgstr ""
+"Por defecto, NTCP usa la IP/puerto autodetectados por SSU. Cuando esté \n"
+"habilitado en config.jsp, SSU notificará/reiniciará NTCP cuando cambie "
+"una \n"
+"dirección externa o cuando cambie el estado del cortafuegos (`firewall`)."
+"\n"
+"Ahora puede habilitar la conexión TCP entrante sin una IP estática o un \n"
+"servicio DynDNS."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:23
+#: i2p2www/pages/site/docs/transport/ntcp.html:24
 msgid ""
 "The NTCP code within I2P is relatively lightweight (1/4 the size of the "
 "SSU code)\n"
 "because it uses the underlying Java TCP transport for reliable delivery."
 msgstr ""
+"El código de NTCP dentro de I2P es relativamente ligero (1/4 del tamaño "
+"del \n"
+"código de SSU) porque usa el transporte TCP Java subyacente para una "
+"entrega fiable."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:29
+#: i2p2www/pages/site/docs/transport/ntcp.html:30
 msgid "NTCP Protocol Specification"
-msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ntcp.html:31
-msgid "Standard Message Format"
-msgstr ""
+msgstr "Especificación del protocolo NTCP"
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:32
+msgid "Standard Message Format"
+msgstr "Formato de mensaje estándar"
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:33
 msgid ""
 "After establishment,\n"
 "the NTCP transport sends individual I2NP messages, with a simple "
 "checksum.\n"
 "The unencrypted message is encoded as follows:"
 msgstr ""
+"Después del establecimiento, el trasporte NTCP envía mensajes "
+"individuales \n"
+"I2NP (protocolo de red I2P), con un identificador criptográfico "
+"(`checksum`). \n"
+"El mensaje no cifrado está codificado de la siguiente manera:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:42
+#: i2p2www/pages/site/docs/transport/ntcp.html:43
 msgid ""
 "The data is then AES/256/CBC encrypted. The session key for the "
 "encryption\n"
@@ -23517,8 +20433,16 @@ msgid ""
 "The IV for AES/256/CBC encryption is the last 16 bytes of the previous "
 "encrypted message."
 msgstr ""
+"Los datos entonces son cifrados con AES/256/CBC (cadena de cifrado \n"
+"por bloques con el estándar avanzado de cifrado de 256 bits). La clave \n"
+"de sesión para el cifrado se negocia durante el establecimiento (usando \n"
+"Diffie-Hellman de 2048 bits). El establecimiento entre dos routers "
+"(enrutadores) está implementado en la clase EstablishState (estado del\n"
+"establecimiento) y detallado debajo. El IV (vector de inicialización) "
+"para el \n"
+"cifrado AES/256/CBC son los últimos 16 bytes del anterior mensaje cifrado."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:50
+#: i2p2www/pages/site/docs/transport/ntcp.html:51
 msgid ""
 "0-15 bytes of padding are required to bring the total message length\n"
 "(including the six size and checksum bytes) to a multiple of 16.\n"
@@ -23526,40 +20450,58 @@ msgid ""
 "Therefore the maximum data size is currently 16 KB - 6, or 16378 bytes.\n"
 "The minimum data size is 1."
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ntcp.html:58
-msgid "Time Sync Message Format"
-msgstr ""
+"Son necesarios datos de relleno (desechables criptográficamente) de entre"
+" \n"
+"0-15 bytes para llevar el tamaño total del mensaje (incluyendo el `tamaño"
+" \n"
+"seis` y los bytes del identificador criptográfico (`checksum`)) a un "
+"múltiplo de 16. El tamaño máximo de mensaje actualmente es de 16 KB. Por "
+"lo tanto el tamaño de dato máximo actualmente es de 16 KB - 6, o lo que "
+"es \n"
+"lo mismo 16378 bytes. El tamaño mínimo de dato es de 1 byte."
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:59
+msgid "Time Sync Message Format"
+msgstr "Formato de mensaje de sincronización de horaria"
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:60
 msgid ""
 "One special case is a metadata message where the sizeof(data) is 0.  In\n"
 "that case, the unencrypted message is encoded as:"
 msgstr ""
+"Un caso especial es un mensaje de metadatos donde el `sizeof(data)` \n"
+"(tamañode(dato)) sea 0. En ese caso, el mensaje no cifrado esta "
+"codificado como:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:70
+#: i2p2www/pages/site/docs/transport/ntcp.html:71
 msgid ""
 "Total length: 16 bytes. The time sync message is sent at approximately 15"
 " minute intervals.\n"
 "The message is encrypted just as standard messages are."
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ntcp.html:76
-msgid "Checksums"
-msgstr ""
+"Longitud total: 16 bytes. El mensaje de sincronización horaria se envía \n"
+"aproximadamente en intervalos de 15 minutos. El mensaje se cifra tal como"
+" se hace con los mensajes estándar."
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:77
+msgid "Checksums"
+msgstr "Identificadores criptográficos (`checksums`)"
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:78
 #, python-format
 msgid ""
 "The standard and time sync messages use the Adler-32 checksum\n"
 "as defined in the ZLIB Specification."
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ntcp.html:83
-msgid "Establishment Sequence"
-msgstr ""
+"Los mensajes estándar y de sincronización horaria usan el identificador \n"
+"criptográfico (`checksum`) Adler-32 tal como se define en la \n"
+"especificación ZLIB."
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:84
+msgid "Establishment Sequence"
+msgstr "Secuencia de establecimiento"
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:85
 msgid ""
 "In the establish state, there is a 4-phase message sequence to exchange "
 "DH keys and signatures.\n"
@@ -23567,92 +20509,118 @@ msgid ""
 "Then, DSA signatures of the critical data are exchanged to confirm the "
 "connection."
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ntcp.html:98
-msgid "Legend:"
-msgstr ""
+"En el estado de establecimiento, hay una secuencia de mensaje de 4-fases"
+" \n"
+"para intercambiar claves DH y firmas. En los dos primeros mensajes hay un"
+" \n"
+"intercambio Diffie Hellman de 2048-bits. Luego, las firmas DSA de los \n"
+"datos críticos se intercambian para confirmar la conexión."
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:99
-msgid "256 byte DH public keys"
-msgstr ""
+msgid "Legend:"
+msgstr "Leyenda:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:103
-msgid "timestamps (4 bytes, seconds since epoch)"
-msgstr ""
+#: i2p2www/pages/site/docs/transport/ntcp.html:100
+msgid "256 byte DH public keys"
+msgstr "Claves públicas DH de 256 bytes"
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:104
-msgid "32 byte Session key"
+msgid "timestamps (4 bytes, seconds since epoch)"
 msgstr ""
+"Marcas de tiempo (4 bytes, segundos desde epoch (época, origen de tiempo "
+"UNIX))"
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:105
-msgid "2 byte size of Alice identity to follow"
-msgstr ""
+msgid "32 byte Session key"
+msgstr "Clave de sesión de 32 bytes"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:108
-msgid "DH Key Exchange"
-msgstr ""
+#: i2p2www/pages/site/docs/transport/ntcp.html:106
+msgid "2 byte size of Alice identity to follow"
+msgstr "Identidad Alice de 2 bytes de tamaño a seguir"
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:109
+msgid "DH Key Exchange"
+msgstr "Intercambio de clave DH"
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:110
 #, python-format
 msgid ""
 "The initial 2048-bit DH key exchange\n"
 "uses the same shared prime (p) and generator (g) as that used for I2P's\n"
 "ElGamal encryption."
 msgstr ""
+"El intercambio de clave DH de 2048-bits inicial usa los mismos primo (p) "
+"y \n"
+"generador (g) compartidos que los usados por el cifrado ElGamal de I2P."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:115
+#: i2p2www/pages/site/docs/transport/ntcp.html:116
 msgid ""
 "The DH key exchange consists of a number of steps, displayed below.\n"
 "The mapping between these steps and the messages sent between I2P "
 "routers,\n"
 "is marked in bold."
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ntcp.html:121
-msgid ""
-"Alice generates a secret 226-bit integer x. She then calculates X ="
-" g^x mod p."
-msgstr ""
+"El intercambio de clave DH consiste en un determinado número de pasos, \n"
+"mostrados debajo. El mapeado entre estos pasos y los mensajes enviados \n"
+"entre los routers (enrutadores) I2P, está marcado en negrita."
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:122
-msgid "Alice sends X to Bob (Message 1)."
+#, fuzzy
+msgid ""
+"Alice generates a secret integer x. She then calculates X = g^x mod"
+" p."
 msgstr ""
+"Alice genera un entero x de 226-bits secreto. Luego calcula X = g^x"
+" mod p."
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:123
-msgid ""
-"Bob generates a secret 226-bit integer y. He then calculates Y = "
-"g^y mod p."
-msgstr ""
+msgid "Alice sends X to Bob (Message 1)."
+msgstr "Alice envía X a Bob (mensaje 1)."
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:124
-msgid "Bob sends Y to Alice.(Message 2)"
+#, fuzzy
+msgid ""
+"Bob generates a secret integer y. He then calculates Y = g^y mod "
+"p."
 msgstr ""
+"Bob genera un entero y de 226-bits secreto. Luego calcula Y = g^y "
+"mod p."
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:125
-msgid "Alice can now compute sessionKey = Y^x mod p."
-msgstr ""
+msgid "Bob sends Y to Alice.(Message 2)"
+msgstr "Bob envía Y a Alice (mensaje 2)."
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:126
-msgid "Bob can now compute sessionKey = X^y mod p."
-msgstr ""
+msgid "Alice can now compute sessionKey = Y^x mod p."
+msgstr "Alice puede ahora calcular sessionKey = Y^x mod p."
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:127
+msgid "Bob can now compute sessionKey = X^y mod p."
+msgstr "Bob puede ahora calcular sessionKey = X^y mod p."
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:128
 msgid ""
 "Both Alice and Bob now have a shared key sessionKey = g^(x*y) mod "
 "p."
 msgstr ""
+"Ambos, Alice y Bob, tienen una clave compartida sessionKey = "
+"g^(x*y) mod p."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:129
+#: i2p2www/pages/site/docs/transport/ntcp.html:130
+#, python-format
 msgid ""
 "The sessionKey is then used to exchange identities in Message 3 "
-"and Message 4."
+"and Message 4.\n"
+"The exponent (x and y) length for the DH exchange is documented on the\n"
+"cryptography page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:133
+#: i2p2www/pages/site/docs/transport/ntcp.html:136
 msgid "Message 1 (Session Request)"
-msgstr ""
+msgstr "Mensaje 1 (solicitud de sesión)"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:134
+#: i2p2www/pages/site/docs/transport/ntcp.html:137
 #, python-format
 msgid ""
 "This is the DH request. Alice already has Bob's\n"
@@ -23664,119 +20632,145 @@ msgid ""
 "network database.\n"
 "Alice sends Bob:"
 msgstr ""
+"Esta es la solicitud DH. Alice tiene ya la RouterIdentity "
+"(identidad del \n"
+"router) de Bob, la dirección IP, y el puerto, tal como los contiene su \n"
+"RouterInfo "
+"(información del router), que estaba publicada en la \n"
+"base de datos de red. Alice envía a Bob:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:147
-#: i2p2www/pages/site/docs/transport/ntcp.html:190
-#: i2p2www/pages/site/docs/transport/ntcp.html:270
-#: i2p2www/pages/site/docs/transport/ntcp.html:353
+#: i2p2www/pages/site/docs/transport/ntcp.html:150
+#: i2p2www/pages/site/docs/transport/ntcp.html:193
+#: i2p2www/pages/site/docs/transport/ntcp.html:273
+#: i2p2www/pages/site/docs/transport/ntcp.html:356
 msgid "Size:"
-msgstr ""
+msgstr "Tamaño:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:149
+#: i2p2www/pages/site/docs/transport/ntcp.html:152
 msgid "Contents:"
-msgstr ""
+msgstr "Contenidos:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:167
+#: i2p2www/pages/site/docs/transport/ntcp.html:170
 msgid "256 byte X from Diffie Hellman"
-msgstr ""
+msgstr "X de 256 bytes desde Diffie Hellman"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:169
+#: i2p2www/pages/site/docs/transport/ntcp.html:172
 #, python-format
 msgid ""
 "SHA256 Hash(X) xored with SHA256 Hash(Bob's Router Identity)"
 msgstr ""
+"`SHA256 Hash(X) XORedado con SHA256 Hash(RouterIdentity de"
+" Bob)`\n"
+"[HXxorHI]"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:176
-#: i2p2www/pages/site/docs/transport/ntcp.html:257
-#: i2p2www/pages/site/docs/transport/ntcp.html:334
+#: i2p2www/pages/site/docs/transport/ntcp.html:179
+#: i2p2www/pages/site/docs/transport/ntcp.html:260
+#: i2p2www/pages/site/docs/transport/ntcp.html:337
 msgid "Notes:"
-msgstr ""
+msgstr "Notas:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:177
+#: i2p2www/pages/site/docs/transport/ntcp.html:180
 msgid ""
 "Bob verifies HXxorHI using his own router hash. If it does not verify,\n"
 "Alice has contacted the wrong router, and Bob drops the connection."
 msgstr ""
+"Bob verifica HXxorHI usando su propio hash de router. Si no se verifica, "
+"Alice ha contactado el router equivocado, y Bob corta la conexión."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:183
+#: i2p2www/pages/site/docs/transport/ntcp.html:186
 msgid "Message 2 (Session Created)"
-msgstr ""
+msgstr "Mensaje 2 (sesión creada)"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:184
+#: i2p2www/pages/site/docs/transport/ntcp.html:187
 msgid "This is the DH reply. Bob sends Alice:"
-msgstr ""
+msgstr "Esta es la respuesta DH. Bob envía a Alice:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:192
-#: i2p2www/pages/site/docs/transport/ntcp.html:272
-#: i2p2www/pages/site/docs/transport/ntcp.html:355
+#: i2p2www/pages/site/docs/transport/ntcp.html:195
+#: i2p2www/pages/site/docs/transport/ntcp.html:275
+#: i2p2www/pages/site/docs/transport/ntcp.html:358
 msgid "Unencrypted Contents:"
-msgstr ""
+msgstr "Contenidos no cifrados:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:214
-#: i2p2www/pages/site/docs/transport/ntcp.html:248
+#: i2p2www/pages/site/docs/transport/ntcp.html:217
+#: i2p2www/pages/site/docs/transport/ntcp.html:251
 msgid "256 byte Y from Diffie Hellman"
-msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ntcp.html:216
-msgid "SHA256 Hash(X concatenated with Y)"
-msgstr ""
+msgstr "Y de 256 bytes desde Diffie Hellman"
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:219
-#: i2p2www/pages/site/docs/transport/ntcp.html:304
+msgid "SHA256 Hash(X concatenated with Y)"
+msgstr "SHA256 Hash(X concatenado con Y)."
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:222
+#: i2p2www/pages/site/docs/transport/ntcp.html:307
 msgid "4 byte timestamp (seconds since the epoch)"
 msgstr ""
+"Marca de tiempo de 4 bytes (segundos desde epoch (época, origen de tiempo"
+" UNIX))"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:221
+#: i2p2www/pages/site/docs/transport/ntcp.html:224
 msgid "12 bytes random data"
 msgstr "12 bytes datos aleatorios"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:226
-#: i2p2www/pages/site/docs/transport/ntcp.html:316
-#: i2p2www/pages/site/docs/transport/ntcp.html:383
+#: i2p2www/pages/site/docs/transport/ntcp.html:229
+#: i2p2www/pages/site/docs/transport/ntcp.html:319
+#: i2p2www/pages/site/docs/transport/ntcp.html:386
 msgid "Encrypted Contents:"
-msgstr ""
+msgstr "Contenidos cifrados:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:250
+#: i2p2www/pages/site/docs/transport/ntcp.html:253
 #, python-format
 msgid ""
 "48 bytes AES encrypted using the DH "
 "session key and\n"
 "                  the last 16 bytes of Y as the IV"
 msgstr ""
+"48 bytes cifrados con AES usando la "
+"clave de sesión DH \n"
+"y los últimos 16 bytes de Y usados como el IV (vector de inicialización)"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:258
+#: i2p2www/pages/site/docs/transport/ntcp.html:261
 msgid ""
 "Alice may drop the connection if the clock skew with Bob is too high as "
 "calculated using tsB."
 msgstr ""
+"Alice puede denegar la conexión si el desfase horario con el relog de Bob"
+" es demasiado alto al calcularse usando tsB."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:263
+#: i2p2www/pages/site/docs/transport/ntcp.html:266
 msgid "Message 3 (Session Confirm A)"
-msgstr ""
+msgstr "Mensaje 3 (Confirmar Sesión A)"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:264
+#: i2p2www/pages/site/docs/transport/ntcp.html:267
 msgid ""
 "This contains Alice's router identity, and a DSA signature of the "
 "critical data. Alice sends Bob:"
 msgstr ""
+"Este contiene la identidad del ruter de Alice, y la firma DSA de los "
+"datos críticos. Alice envía a Bob:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:298
+#: i2p2www/pages/site/docs/transport/ntcp.html:301
 msgid "2 byte size of Alice's router identity to follow (should always be 387)"
 msgstr ""
+"La identidad del ruter de Alice de 2 bytes para seguir (debería ser "
+"siempre 387)"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:300
+#: i2p2www/pages/site/docs/transport/ntcp.html:303
 #, python-format
 msgid ""
 "Alice's 387 byte Router Identity"
 msgstr ""
+"La identidad del "
+"ruter de Alice de 387 bytes."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:306
+#: i2p2www/pages/site/docs/transport/ntcp.html:309
 msgid "15 bytes random data"
 msgstr "15 bytes datos aleatorios"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:308
+#: i2p2www/pages/site/docs/transport/ntcp.html:311
 #, python-format
 msgid ""
 "the 40 byte DSA "
@@ -23791,8 +20785,17 @@ msgid ""
 "key in her Router Identity"
 msgstr ""
+"La firma DSA de 40 "
+"bytes de los siguientes datos datos concatenados: X, Y, RouterIdentity de"
+" Bob. tsA, tsB. Alice firma con la clave privada de "
+"firma asociada con la clave pública de "
+"firma en su RouterIdentity"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:326
+#: i2p2www/pages/site/docs/transport/ntcp.html:329
 #, python-format
 msgid ""
 "448 bytes AES encrypted using the DH"
@@ -23800,26 +20803,31 @@ msgid ""
 "                  the last 16 bytes of HXxorHI (i.e., the last 16 bytes "
 "of message #1) as the IV"
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ntcp.html:336
-msgid "Bob verifies the signature, and on failure, drops the connection."
-msgstr ""
+"448 bytes cifrados con AES usando la"
+" clave de sesión DH y los últimos 16 bytes de HXxorHI ( por ejemplo, los "
+"últimos 16 bytes del mensaje #1) como el IV"
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:339
+msgid "Bob verifies the signature, and on failure, drops the connection."
+msgstr "Bob verifica la firma, y si falla, rechaza la conexión."
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:342
 msgid ""
 "Bob may drop the connection if the clock skew with Alice is too high as "
 "calculated using tsA."
 msgstr ""
+"Bob puede rechazar la conexión si si el desfase horario con el reloj de "
+"Alice es demasiado alto al calcularse usando tsA."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:346
+#: i2p2www/pages/site/docs/transport/ntcp.html:349
 msgid "Message 4 (Session Confirm B)"
-msgstr ""
+msgstr "Mensaje 4 (Confirmar Sesión B)"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:347
+#: i2p2www/pages/site/docs/transport/ntcp.html:350
 msgid "This is a DSA signature of the critical data. Bob sends Alice:"
-msgstr ""
+msgstr "Esta es la firma DSA de los datos críticos. Bob envía a Alice:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:372
+#: i2p2www/pages/site/docs/transport/ntcp.html:375
 #, python-format
 msgid ""
 "the 40 byte DSA "
@@ -23834,12 +20842,21 @@ msgid ""
 "key in his Router Identity"
 msgstr ""
+"La firma DSA de 40 "
+"bytes de los siguientes datos datos concatenados: X, Y, RouterIdentity de"
+" Alice. tsA, tsB. Bob firma con la clave privada de "
+"firma asociada con la clave pública de "
+"firma en su RouterIdentity"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:378
+#: i2p2www/pages/site/docs/transport/ntcp.html:381
 msgid "8 bytes random data"
-msgstr ""
+msgstr "8 bytes de datos aleatorios"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:393
+#: i2p2www/pages/site/docs/transport/ntcp.html:396
 #, python-format
 msgid ""
 "48 bytes AES encrypted using the DH "
@@ -23847,16 +20864,19 @@ msgid ""
 "                  the last 16 bytes of the encrypted contents of message "
 "#2 as the IV"
 msgstr ""
+"48 bytes cifrados con AES usando la "
+"clave de sesión DH y los últimos 16 bytes del contenido cifrado del "
+"mensaje #2 como el IV"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:401
+#: i2p2www/pages/site/docs/transport/ntcp.html:404
 msgid "Alice verifies the signature, and on failure, drops the connection."
-msgstr ""
+msgstr "Alice verifica la firma, y en caso de fallo, rechaza la conexión."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:408
+#: i2p2www/pages/site/docs/transport/ntcp.html:411
 msgid "After Establishment"
-msgstr ""
+msgstr "Después del establecimiento"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:409
+#: i2p2www/pages/site/docs/transport/ntcp.html:412
 msgid ""
 "The connection is established, and standard or time sync messages may be "
 "exchanged.\n"
@@ -23867,12 +20887,18 @@ msgid ""
 "Bob will use the last 16 bytes of the encrypted contents of message #4 as"
 " the next IV."
 msgstr ""
+"La conexión está establecida, y pueden intercambiarse mensajes normales o"
+" mensajes de sincronización de tiempo. Todos los mensajes siguientes "
+"están cifrados con AES usado la clave de sesión DH antes acordada. Alice "
+"usará los últimos 16 bytes del contenido cifrado del mensaje #3 como el "
+"siguiente IV. Bob usará los últimos 16 bytes del contenido cifrado del "
+"mensaje #4 como el siguiente IV."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:418
+#: i2p2www/pages/site/docs/transport/ntcp.html:421
 msgid "Check Connection Message"
-msgstr ""
+msgstr "Mensaje de conexión del reloj"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:419
+#: i2p2www/pages/site/docs/transport/ntcp.html:422
 msgid ""
 "Alternately, when Bob receives a connection, it could be a\n"
 "check connection (perhaps prompted by Bob asking for someone\n"
@@ -23881,55 +20907,69 @@ msgid ""
 "However, for the record, check connections are formatted as follows.\n"
 "A check info connection will receive 256 bytes containing:"
 msgstr ""
+"Alternativamente, cuando Bob recibe una conexión, puede ser una conexión "
+"de prueba (quizás mostrada por Bob al preguntar a alguien para verificar "
+"a su interlocutor). Las conexiones de prueba no se usan actualmente. "
+"Aunque, para que quede en el registro, las conexiones de prueba son "
+"formateadas como sigue. Una conexión de prueba de información recibirá "
+"256 bytes que contienen:"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:428
+#: i2p2www/pages/site/docs/transport/ntcp.html:431
 msgid "32 bytes of uninterpreted, ignored data"
-msgstr ""
+msgstr "32 bytes sin interpretar, datos ignorados"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:429
+#: i2p2www/pages/site/docs/transport/ntcp.html:432
 msgid "1 byte size"
-msgstr ""
+msgstr "tamaño de 1 byte"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:430
+#: i2p2www/pages/site/docs/transport/ntcp.html:433
 msgid ""
 "that many bytes making up the local router's IP address (as reached by "
 "the remote side)"
 msgstr ""
+"el número de  bytes que componen la dirección IP del ruter local (como "
+"haya sido contactado por la parte remota)"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:431
+#: i2p2www/pages/site/docs/transport/ntcp.html:434
 msgid "2 byte port number that the local router was reached on"
-msgstr ""
+msgstr "el número de puerto de 2 bytes, en donde ha sido contactado el ruter local"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:432
+#: i2p2www/pages/site/docs/transport/ntcp.html:435
 msgid ""
 "4 byte i2p network time as known by the remote side (seconds since the "
 "epoch)"
 msgstr ""
+"la hora de la red i2p de 4 bytes según la parte remota (segundos desde la"
+" 'época')"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:433
+#: i2p2www/pages/site/docs/transport/ntcp.html:436
 msgid "uninterpreted padding data, up to byte 223"
-msgstr ""
+msgstr "datos de relleno sin interpretar, hasta 223 bytes"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:434
+#: i2p2www/pages/site/docs/transport/ntcp.html:437
 msgid ""
 "xor of the local router's identity hash and the SHA256 of bytes 32 "
 "through bytes 223"
 msgstr ""
+"xor del hash de la identidad del ruter local y el SHA256 de los bytes "
+"desde el 32 hasta el 223"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:438
+#: i2p2www/pages/site/docs/transport/ntcp.html:441
 msgid "Discussion"
-msgstr ""
+msgstr "Discusión"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:439
+#: i2p2www/pages/site/docs/transport/ntcp.html:442
 #, python-format
 msgid "Now on the NTCP Discussion Page."
-msgstr ""
+msgstr "Ahora en al Página de discusión de NTCP."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:445
+#: i2p2www/pages/site/docs/transport/ntcp.html:448
 msgid "The maximum message size should be increased to approximately 32 KB."
 msgstr ""
+"El tamaño máximo del mensaje debería aumentarse hasta aproximadamente 32 "
+"KB"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:449
+#: i2p2www/pages/site/docs/transport/ntcp.html:452
 msgid ""
 "A set of fixed packet sizes may be appropriate to further hide the data \n"
 "fragmentation to external adversaries, but the tunnel, garlic, and end to"
@@ -23939,30 +20979,41 @@ msgid ""
 "16-byte boundary,\n"
 "to create a limited number of message sizes."
 msgstr ""
+"Un conjunto de tamaños de paquetes fijos podría ser apropiado para "
+"ocultar aún más la fragmentación de los datos a adversarios externos, "
+"pero el túnel garlic y el relleno de fin a fin deberían ser suficientes "
+"para la mayoría de las necesidades hasta entonces. Sin embargo, "
+"actualmente no se realiza el relleno más allá del límite de 16 bytes, "
+"para crear un número limitado de tamaños de mensajes."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:457
+#: i2p2www/pages/site/docs/transport/ntcp.html:460
 msgid ""
 "Memory utilization (including that of the kernel) for NTCP should be "
 "compared to that for SSU."
 msgstr ""
+"La utilización de la memoria (incluyendo la del kerne) para NTCP debería "
+"compararse con la del SSU."
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:461
+#: i2p2www/pages/site/docs/transport/ntcp.html:464
 msgid ""
 "Can the establishment messages be randomly padded somehow, to frustrate\n"
 "identification of I2P traffic based on initial packet sizes?"
 msgstr ""
+"¿Pueden ser rellenado aleatoriamente de alguna forma el mensaje "
+"establecido, para evitar la identificación del tráfico I2P basado en el "
+"tamaño del paquete inicial?"
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:466
+#: i2p2www/pages/site/docs/transport/ntcp.html:469
 msgid "Review and possibly disable 'check connection'"
-msgstr ""
+msgstr "Revisar y posiblemente desactivar la ' conexión de prueba'"
 
 #: i2p2www/pages/site/docs/transport/ssu.html:2
 msgid "SSU Transport"
-msgstr ""
+msgstr "Transporte SSU"
 
 #: i2p2www/pages/site/docs/transport/ssu.html:6
 msgid "Secure Semireliable UDP"
-msgstr ""
+msgstr "UDP seguro sem-ifiable "
 
 #: i2p2www/pages/site/docs/transport/ssu.html:9
 #, python-format
@@ -23973,62 +21024,87 @@ msgid ""
 "implemented in I2P.\n"
 "The other is NTCP."
 msgstr ""
+"SSU (también llamado \"UDP\" en gran parte de la documentación de I2P y "
+"de los interfaces de usuario) es uno de los dos transportes actualmente implementados en I2P."
+" El otro es NTCP."
 
 #: i2p2www/pages/site/docs/transport/ssu.html:15
 msgid ""
 "SSU is the newer of the two transports,\n"
 "introduced in I2P release 0.6.\n"
 "In a standard I2P installation, the router uses both NTCP and SSU for "
-"outbound connections."
+"outbound connections.\n"
+"SSU-over-IPv6 is supported as of version 0.9.8."
 msgstr ""
+"SSU es el más reciente de los dos transportes,\n"
+"introducidos en la versión 0.6 de I2P.\n"
+"En una instalación I2P standard, el router usa tanto NTCP como SSU para "
+"conexiones salientes.\n"
+"SSU-sobre-IPv6 está soportado desde la versión 0.9.8."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:21
+#: i2p2www/pages/site/docs/transport/ssu.html:22
 msgid "SSU Services"
-msgstr ""
+msgstr "Servicios SSU"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:23
+#: i2p2www/pages/site/docs/transport/ssu.html:24
 msgid ""
 "Like the NTCP transport, SSU provides reliable, encrypted, connection-"
 "oriented, point-to-point data transport.\n"
 "Unique to SSU, it also provides IP detection and NAT traversal services, "
 "including:"
 msgstr ""
+"Al igual que el transporte NTCP, SSU proporciona un transporte de datos "
+"de punto apunto cifrado y seguro orientado a conexión. A diferencia de "
+"SSU, también proporciona detección de servicios de NAT trasversales, "
+"incluyendo:"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:29
+#: i2p2www/pages/site/docs/transport/ssu.html:30
 msgid ""
 "Cooperative NAT/Firewall traversal using introducers"
 msgstr ""
+"NAT/cortafuego trasversal cooperativo usando introductores"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:30
+#: i2p2www/pages/site/docs/transport/ssu.html:31
 msgid ""
 "Local IP detection by inspection of incoming packets and peer testing"
 msgstr ""
+"Detección de la IP local inspeccionado los paquetes de entrada y la prueba de pares "
 
-#: i2p2www/pages/site/docs/transport/ssu.html:31
+#: i2p2www/pages/site/docs/transport/ssu.html:32
 msgid ""
 "Communication of firewall status and local IP, and changes to either to "
 "NTCP"
 msgstr ""
+"Comunicación del estado del cortafuegos y de la IP local, y los cambios "
+"en cualquiera de ellos a NTCP "
 
-#: i2p2www/pages/site/docs/transport/ssu.html:36
+#: i2p2www/pages/site/docs/transport/ssu.html:37
 msgid "Protocol Details"
-msgstr ""
+msgstr "Detalles del protocolo"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:38
+#: i2p2www/pages/site/docs/transport/ssu.html:39
 msgid "Congestion control"
-msgstr ""
+msgstr "Control de congestión"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:40
+#: i2p2www/pages/site/docs/transport/ssu.html:41
 msgid ""
 "SSU's need for only semireliable delivery, TCP-friendly operation,\n"
 "and the capacity for high throughput allows a great deal of latitude in\n"
 "congestion control.  The congestion control algorithm outlined below is\n"
 "meant to be both efficient in bandwidth as well as simple to implement."
 msgstr ""
+"Gracias a sólo necesitar SSU el envío semi fiable, a las conexiones "
+"amigables con TCP, y  al haber capacidad para un gran rendimiento, se "
+"permite un amplio abanico de posibilidades en el control de gestión. El "
+"algoritmo de control de gestión esbozado abajo se supone eficiente en el "
+"gasto de ancho de banda y simple de implementar."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:47
+#: i2p2www/pages/site/docs/transport/ssu.html:48
 msgid ""
 "Packets are scheduled according to the router's policy, taking care\n"
 "not to exceed the router's outbound capacity or to exceed the measured \n"
@@ -24042,8 +21118,16 @@ msgid ""
 " \n"
 "other messages."
 msgstr ""
+"Los paquetes son programados de acuerdo con la política del ruter, "
+"teniendo cuidado de no exceder la capacidad de salida del ruter o de "
+"exceder la capacidad medida en el par remoto. La capacidad medida opera "
+"según el inicio lento y la prevención de la congestión de TCP, con "
+"aumentos que se suman a la capacidad de envío y disminuciones en caso de "
+"congestión. Al contrario que TCP, algunos ruters pueden renunciar a "
+"algunos mensajes despues de un periodo indicado o un número de "
+"retransmisiones, mientras que continúa transmitiendo otros mensajes."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:58
+#: i2p2www/pages/site/docs/transport/ssu.html:59
 msgid ""
 "The congestion detection techniques vary from TCP as well, since each \n"
 "message has its own unique and nonsequential identifier, and each message"
@@ -24058,38 +21142,61 @@ msgid ""
 "message has still not been fully received, the bitfield should be \n"
 "retransmitted with any new updates."
 msgstr ""
+"Las técnicas de detección de congestión tampoco son iguales a las de TCP,"
+" ya que cada mensaje tiene su identificador único y no secuencial, y cada"
+" mensaje tiene un tamaño limitado - como máximo, 32 KB.  Para transmitir "
+"eficientemente esta respuesta al remitente, el receptor periódicamente "
+"incluye una lista de identificadores de mensaje totalmente 'ACKed' y "
+"también puede incluir campos de bits, 'bitfields', para los mensajes "
+"recibidos parcialmente, donde cada bit representa la recogida de un "
+"fragmento. Si llegan fragmentos duplicados, el mensaje deber ser 'ACKed' "
+"de nuevo, o si el mensaje aún no ha sido recibido en su totalidad, el "
+"bitfield debería ser retransmitido con cualquier nuevo cambio."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:70
+#: i2p2www/pages/site/docs/transport/ssu.html:71
 msgid ""
 "The current implementation does not pad the packets to\n"
 "any particular size, but instead just places a single message fragment "
 "into\n"
 "a packet and sends it off (careful not to exceed the MTU)."
 msgstr ""
+"La implementación actual no rellena los paquetes a un tamaño en "
+"particular, en cambio simplemente coloca un solo fragmento de un mensaje "
+"dentro de un paquete y lo envía para fuera (con cuidado de no exceder el "
+"MTU)."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:77
+#: i2p2www/pages/site/docs/transport/ssu.html:78
 msgid ""
 "As of router version 0.8.12,\n"
 "two MTU values are used for IPv4: 620 and 1484.\n"
 "The MTU value is adjusted based on the percentage of packets that are "
 "retransmitted."
 msgstr ""
+"A partir de la versión del ruter 0.8.12 se usan dos valores de MTU para "
+"IPv4: 620 y 1484. El valor del MTU es reajustado dependiendo del "
+"porcentaje de paquetes que es retrasnmitido."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:83
+#: i2p2www/pages/site/docs/transport/ssu.html:84
 msgid ""
-"For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
+"For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
 "the payload portion after the 28-byte IP/UDP header is a multiple of\n"
 "16 bytes, for encryption purposes."
 msgstr ""
+"Para ambos valores MTU (unidad máxima de transmisión), es deseable que "
+"(MTU % 16 == 12), así que la porción de la carga tras la cabecera \n"
+"de 28-bytes IP/UDP es un múltiplo de 16 bytes, para propositos de cifrado."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:89
+#: i2p2www/pages/site/docs/transport/ssu.html:90
 msgid ""
 "For the small MTU value, it is desirable to pack a 2646-byte\n"
 "Variable Tunnel Build Message efficiently into multiple packets;\n"
 "with a 620-byte MTU, it fits into 5 packets with nicely."
 msgstr ""
+"Para el valor más pequeño de MTU, es preferible empaquetar un mensaje de "
+"construcción de túnel variable de 2646 bytes eficientemente dentro de "
+"múltiples paquetes; el MTU de 620 bytes encaja bien dentro de 5 paquetes."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:95
+#: i2p2www/pages/site/docs/transport/ssu.html:96
 msgid ""
 "Based on measurements, 1492 fits nearly all reasonably small I2NP "
 "messages\n"
@@ -24097,40 +21204,57 @@ msgid ""
 "to fit\n"
 "into a live network MTU anyway)."
 msgstr ""
+"Basado en las mediciones, 1492 encaja en casi todos los mensajes I2NP "
+"razonablemente pequeños (los mensajes I2NP más grandes pueden ser desde "
+"1900 hasta 4500 bytes, que de todas formas no encajarían dentro del MTU "
+"de la red)."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:101
+#: i2p2www/pages/site/docs/transport/ssu.html:102
 msgid ""
 "The MTU values were 608 and 1492 for releases 0.8.9 - 0.8.11.\n"
 "The large MTU was 1350 prior to release 0.8.9."
 msgstr ""
+"Los valores del MTU eran 608 y 1492 para las versiones 0.8.9 - 0.8.11. El"
+" MTU largo era de 1350 en las versiones anteriores a la 0.8.9."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:106
+#: i2p2www/pages/site/docs/transport/ssu.html:107
 msgid ""
 "The maximum receive packet size\n"
 "is 1571 bytes as of release 0.8.12.\n"
 "For releases 0.8.9 - 0.8.11 it was 1535 bytes.\n"
 "Prior to release 0.8.9 it was 2048 bytes."
 msgstr ""
+"Para la versión 0.8.12 el tamaño máximo del paquete recibido es de 1571 "
+"bytes. Para las versiones 0.8.9 - 0.8.11 era de 1535 bytes. Para las "
+"versiones anteriores a 0.8.9 era de 2048 bytes. "
 
-#: i2p2www/pages/site/docs/transport/ssu.html:113
+#: i2p2www/pages/site/docs/transport/ssu.html:114
 msgid ""
 "As of release 0.9.2, if a router's network interface MTU is less than "
 "1484,\n"
 "it will publish that in the network database, and other routers should\n"
 "honor that when a connection is established."
 msgstr ""
+"A partir de la versión 0.9.2, si el MTU del interfaz de red del ruter es "
+"menor de 1484, esto será publicado en la base de datos de la red, y los "
+"otros ruters deberían respetarlo cuando una conexión es establecida."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:119
+#: i2p2www/pages/site/docs/transport/ssu.html:120
 msgid ""
 "For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes,\n"
-"so we use an MTU where (MTN % 16 == 0), which is true for 1280."
+"so we use an MTU where (MTN % 16 == 0), which is true for 1280.\n"
+"The maximum IPv6 MTU is 1472."
 msgstr ""
+"Para IPv6, la mínima MTU (unidad de transmisión máxima) es 1280.\n"
+"La cabecera IP/UDP IPv6 es de 48 bytes, así que usamos una MTU\n"
+"donde (MTN % 16 == 0), lo que es cierto para 1280.\n"
+"La máxima MTU IPv6 es 1472."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:124
+#: i2p2www/pages/site/docs/transport/ssu.html:126
 msgid "Message Size Limits"
-msgstr ""
+msgstr "Límites de los tamaños de mensaje"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:125
+#: i2p2www/pages/site/docs/transport/ssu.html:127
 msgid ""
 "While the maximum message size is nominally 32KB, the practical\n"
 "limit differs. The protocol limits the number of fragments to 7 bits, or "
@@ -24144,20 +21268,35 @@ msgid ""
 "Further work is necessary to raise the UDP transport limit above 32KB.\n"
 "For connections using the larger MTU, larger messages are possible."
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ssu.html:136
-msgid "Keys"
-msgstr ""
+"Mientras que normalmente el tamaño máximo de un mensaje es de 32KB, los "
+"límites prácticos difieren. El protocolo limita el número de fragmentos a"
+" 7 bits, o 128. La implementación actual limita cada mensaje a un máximo "
+"de 64 fragmentos, lo cual es suficiente para, 64 * 534 = 33.3 KB, cuando "
+"se usa el MTU de 608. Debido al gasto de las claves de sesión y  los "
+"LeaseSets incluidos, el límite práctico en el nivel de aplicación es "
+"alrededor de 6KB menos, o alrededor de 26KB. Se necesita más trabajo para"
+" poder aumentar el límite del transporte UDP por encima de 32KB. Para las"
+" conexiones que usan un MTU más largo, son posibles mensajes más largos."
 
 #: i2p2www/pages/site/docs/transport/ssu.html:138
+msgid "Keys"
+msgstr "Claves"
+
+#: i2p2www/pages/site/docs/transport/ssu.html:140
 msgid ""
 "All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n"
 "The MAC and session keys are negotiated as part of the DH exchange, used\n"
 "for the HMAC and encryption, respectively.  Prior to the DH exchange, \n"
 "the publicly knowable introKey is used for the MAC and encryption."
 msgstr ""
+"Todo el cifrado usado es AES256/CBC con claves de 32 bytes e IVs \n"
+"(vectores de inicialización) de 16 bytes. Las claves de MAC (dirección "
+"hardware de la interfaz de red) y de sesión se negocian como parte del \n"
+"intercambio DH (Diffie Hellman), usado por el HMAC y el cifrado \n"
+"respectivamente. Previamente al intercambio DH, la introkey (clave de \n"
+"presentación) públicamente conocible se usa para la MAC y el cifrado."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:145
+#: i2p2www/pages/site/docs/transport/ssu.html:147
 msgid ""
 "When using the introKey, both the initial message and any subsequent\n"
 "reply use the introKey of the responder (Bob) - the responder does \n"
@@ -24166,8 +21305,17 @@ msgid ""
 "contacts him, though Alice's DSA key may not already be known by \n"
 "Bob."
 msgstr ""
+"Cuando use la introkey, ambos, tanto el mensaje inicial como cualquier \n"
+"respuesta subsiguiente usan las introkey del emisor de la respuesta (Bob)"
+" \n"
+"- este no necesita conocer la introKey del peticionario (Alice). La clave"
+" de \n"
+"firmado DSA (algoritmo de firma digital) usada por Bor debería ser "
+"conocida \n"
+"ya pro Alice cuando contacte con él, aunque la clave DSA de Alice puede \n"
+"que no sea conocida por Bob aún."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:154
+#: i2p2www/pages/site/docs/transport/ssu.html:156
 msgid ""
 "Upon receiving a message, the receiver checks the \"from\" IP address and"
 " port\n"
@@ -24179,8 +21327,16 @@ msgid ""
 "according to the message type, though if the receiver is overloaded,\n"
 "it may be dropped anyway."
 msgstr ""
+"Tras recibir un mensaje, el destinatario comprueba la dirección IP y el "
+"puerto \"desde\" de todas las sesiones establecidas - si hay "
+"coincidencias, las claves MAC de sesión son probadas en el HMAC. Si "
+"ninguna de esas se verifican, o si no coinciden con la IP, el receptor "
+"prueba su introKey en el MAC, si esta no se verifica, el paquete es "
+"denegado. Si se verifica, es interpretado de acuerdo el tipo de mensaje, "
+"aunque si el destinatario está sobrecargado, puede que también sea "
+"desechado."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:165
+#: i2p2www/pages/site/docs/transport/ssu.html:167
 msgid ""
 "If Alice and Bob have an established session, but Alice loses the \n"
 "keys for some reason and she wants to contact Bob, she may at any \n"
@@ -24191,35 +21347,49 @@ msgid ""
 "fails to reply, she will assume the key is lost and reestablish a \n"
 "new one."
 msgstr ""
+"Si Alice y Bob tienen una sesión establecida, pero Alice pierde las "
+"claves por alguna razón y quiere contactar con Bob, ella puede "
+"simplemente establecer una nueva sesión a través del SessionRequest y los"
+" mensajes relacionados. Si Bob ha perdido la clave pero Alice no lo sabe,"
+" ella primero intentará que le responda, y si Bob continúa sin responder,"
+" ella asumirá que la clave  se perdió y restablecerá una nueva."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:176
+#: i2p2www/pages/site/docs/transport/ssu.html:178
 #, python-format
 msgid ""
 "For the DH key agreement,\n"
 "RFC3526 2048bit\n"
 "MODP group (#14) is used:"
 msgstr ""
+"Para el acuerdo de la clave DH, RFC3526 grupo"
+" MODP de 2048bit (#14) se utiliza:"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:186
+#: i2p2www/pages/site/docs/transport/ssu.html:188
 #, python-format
 msgid ""
 "These are the same p and g used for I2P's\n"
 "ElGamal encryption."
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ssu.html:191
-msgid "Replay prevention"
-msgstr ""
+"Estos son los mismos p y g usados por el cifrado ElGamal de I2P."
 
 #: i2p2www/pages/site/docs/transport/ssu.html:193
+msgid "Replay prevention"
+msgstr "Prevención de Respuesta"
+
+#: i2p2www/pages/site/docs/transport/ssu.html:195
 msgid ""
 "Replay prevention at the SSU layer occurs by rejecting packets \n"
 "with exceedingly old timestamps or those which reuse an IV.  To\n"
 "detect duplicate IVs, a sequence of Bloom filters are employed to\n"
 "\"decay\" periodically so that only recently added IVs are detected."
 msgstr ""
+"La prevención de respuesta en la capa SSU ocurre denegando paquetes "
+"excesivamente viejos o aquellos que reutilizan un IV. Para detectar IVs "
+"duplicados, se utilizan una secuencia de filtros Bloom para "
+"\"destruirlos\", y así sólo se detecten los IVs añadidos recientemente."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:200
+#: i2p2www/pages/site/docs/transport/ssu.html:202
 msgid ""
 "The messageIds used in DataMessages are defined at layers above\n"
 "the SSU transport and are passed through transparently.  These IDs\n"
@@ -24227,53 +21397,74 @@ msgid ""
 "entirely random.  The SSU layer makes no attempt at messageId \n"
 "replay prevention - higher layers should take that into account."
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ssu.html:208
-msgid "Addressing"
-msgstr ""
+"Los mensajesId usados en los DataMessages son definidos en capas por "
+"encima del transporte SSU y son pasados a través transparentemente. Estos"
+" IDs no están en un orden en particular - de hecho, es probable que sean "
+"totalmente aleatorios. La capa SSU no intenta hacer prevención de "
+"respuesta en los messageId - las capas superiores deberían tener esto en "
+"cuenta."
 
 #: i2p2www/pages/site/docs/transport/ssu.html:210
+msgid "Addressing"
+msgstr "Direccionamiento"
+
+#: i2p2www/pages/site/docs/transport/ssu.html:212
 msgid ""
 "To contact an SSU peer, one of two sets of information is necessary:\n"
 "a direct address, for when the peer is publicly reachable, or an\n"
 "indirect address, for using a third party to introduce the peer.\n"
 "There is no restriction on the number of addresses a peer may have."
 msgstr ""
+"Para contactar un par SSU, se necesita uno de estos datos: una dirección "
+"directa, para cuando el par sea accesible públicamente, o una dirección "
+"indirecta, para usar a un tercero para que introduzca al par. No hay "
+"restricción en el número de direcciones que un par puede tener."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:222
+#: i2p2www/pages/site/docs/transport/ssu.html:224
 msgid ""
 "Each of the addresses may also expose a series of options - special\n"
 "capabilities of that particular peer.  For a list of available\n"
 "capabilities, see below."
 msgstr ""
+"Cada una de las direcciones puede mostrar una serie de opciones - "
+"capacidades especiales para un par en particular. Para una lista de "
+"capacidades disponibles, vea más abajo."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:228
+#: i2p2www/pages/site/docs/transport/ssu.html:230
 #, python-format
 msgid ""
 "The addresses, options, and capabilities are published in the network database."
 msgstr ""
+"Las direcciones, opciones y capacidades son publicadas en la base de datos de la red."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:233
+#: i2p2www/pages/site/docs/transport/ssu.html:235
 msgid "Direct Session Establishment"
-msgstr ""
+msgstr "Establecimiento de una sesión directa"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:234
+#: i2p2www/pages/site/docs/transport/ssu.html:236
 msgid ""
 "Direct session establishment is used when no third party is required for "
 "NAT traversal.\n"
 "The message sequence is as follows:"
 msgstr ""
+"El establecimiento de una sesión directa se usa cuando no hace falta un "
+"tercero para el NAT trasversal. La secuencia del mensaje es como sigue:"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:239
+#: i2p2www/pages/site/docs/transport/ssu.html:241
 msgid "Connection establishment (direct)"
-msgstr ""
+msgstr "Establecimiento de la conexión (directa)"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:240
-msgid "Alice connects directly to Bob."
+#: i2p2www/pages/site/docs/transport/ssu.html:242
+msgid ""
+"Alice connects directly to Bob.\n"
+"IPv6 is supported as of version 0.9.8."
 msgstr ""
+"Alice conecta directamente con Bob.\n"
+"IPv6 está soportado desde la versión 0.9.8."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:254
+#: i2p2www/pages/site/docs/transport/ssu.html:257
 #, python-format
 msgid ""
 "After the SessionConfirmed message is received, Bob sends a small\n"
@@ -24285,8 +21476,13 @@ msgid ""
 "\n"
 "(i.e. 0x0000000000000002)."
 msgstr ""
+"Después de que se haya recibido el SessionConfirmed, Bob envía un pequeño"
+" mensaje DeliveryStatus "
+"como confirmación. En este mensaje, el ID de 4 bytes es aleatorio, y el "
+"\"tiempo de llegada\" de 8 bytes es el ID de toda la red actual, el cual "
+"es 2 (por ejemplo 0x0000000000000002)."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:263
+#: i2p2www/pages/site/docs/transport/ssu.html:266
 #, python-format
 msgid ""
 "After the status message is sent, the peers exchange\n"
@@ -24294,8 +21490,12 @@ msgid ""
 "containing their\n"
 "RouterInfos."
 msgstr ""
+"Después de ser enviado el mensaje, los pares intercambia mensajes DatabaseStore "
+"conteniendo sus RouterInfos. "
 
-#: i2p2www/pages/site/docs/transport/ssu.html:271
+#: i2p2www/pages/site/docs/transport/ssu.html:274
 msgid ""
 "It does not appear that the type of the status message or its contents "
 "matters.\n"
@@ -24303,8 +21503,12 @@ msgid ""
 "several seconds; since the store is now sent immediately, perhaps\n"
 "the status message can be eliminated."
 msgstr ""
+"No parece que importe el tipo del mensaje de estado o su contenidos . Se "
+"añadió originalmente porque el mensaje DatabaseStore era retardado varios"
+" segundos, desde que el mensaje es enviado inmediatamente, quizás el "
+"mensaje de estado se pueda eliminar."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:280
+#: i2p2www/pages/site/docs/transport/ssu.html:283
 msgid ""
 "Introduction keys are delivered through an external channel \n"
 "(the network database, where they are identical to the router Hash for "
@@ -24319,8 +21523,20 @@ msgid ""
 "already know the public keys of the peer they are connecting to (but\n"
 "not necessary to any intermediary relay peer)."
 msgstr ""
+"Las claves introductorias son enviadas a través de un canal externo (la "
+"base de datos de la red, donde son idénticos al Hash del ruter, por "
+"ahora) y tienen que ser usados cuando se establece la clave de sesión. "
+"Para la dirección indirecta, el par primero tiene que contactar un "
+"relayhost y preguntar por una introducción para el par conocido en el "
+"relayhost bajo la etiqueta dada. Si es posible, el relayhost envía un "
+"mensaje al par direccionado diciéndole que contacte el par que está "
+"solicitando, y también indica al par solicitante la IP y el puerto den "
+"donde se encuentra el par direccionado. Además, el par que está "
+"estableciendo la conexión ya tiene que conocer las claves públicas del "
+"par con el que está conectando (pero no necesariamente a ninguno de los "
+"pares intermediarios)."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:294
+#: i2p2www/pages/site/docs/transport/ssu.html:297
 msgid ""
 "Indirect session establishment by means of a third party introduction\n"
 "is necessary for efficient NAT traversal.  Charlie, a router behind a\n"
@@ -24347,26 +21563,47 @@ msgid ""
 "and when Alice receives Bob's RelayResponse packet, she begins a new \n"
 "full direction session establishment with the specified IP and port."
 msgstr ""
+"El establecimiento de sesiones indirectas por parte de un tercero es "
+"necesario para el funcionamiento eficiente del NAT trasversal. Charlie, "
+"un ruter tras un NAT o cortafuegos que no permite paquetes UDP no "
+"solicitados de entrada, primero contacta con unos pocos pares, eligiendo "
+"algunos para usarlos como introductores. Cada uno de estos pares (Bob, "
+"Bill, Betty, etc) proporcionan a Charlie una etiqueta de introducción - "
+"un número aleatorio de 4 bytes -la cual él después hace público como una "
+"forma de contactarlo. Alice, un ruter que tiene publicado los métodos "
+"para contactar con Charlie, primero envía un paquete RelayReques a uno o "
+"más de los introductores, preguntando a cada uno para que le introduzca a"
+" Charlie (ofreciendo la etiqueta de introducción para identificar a "
+"Charlie). Bob entonces envía un paquete RelayIntro a Charlie incluyendo "
+"el puerto y la IP pública de Charlie. Cuando Charlie recibe el paquete "
+"RelayIntro, envía un pequeño paquete aleatorio al puerto e IP de Alice "
+"(creando un agujero en su NAT/cortafuegos), y cuando Alice recibe el "
+"paquete RelayResponse de Bob, ella empieza una establecimiento de sesión "
+"completamente nuevo con el puerto y la IP especificados. "
 
-#: i2p2www/pages/site/docs/transport/ssu.html:321
+#: i2p2www/pages/site/docs/transport/ssu.html:324
 msgid "Connection establishment (indirect using an introducer)"
-msgstr ""
+msgstr "Establecimiento de la conexión (usando un introductor indirecto)"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:323
+#: i2p2www/pages/site/docs/transport/ssu.html:326
 msgid "Alice first connects to introducer Bob, who relays the request to Charlie."
 msgstr ""
+"Alice primero se conecta al Bob introductor, que reenvía la petición a "
+"Charlie."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:341
+#: i2p2www/pages/site/docs/transport/ssu.html:344
 msgid ""
 "After the hole punch, the session is established between Alice and "
 "Charlie as in a direct establishment."
 msgstr ""
+"Después de la creación del agujero en el  NAT, la sesión es establecida "
+"entre Alice y Charlie como si fuese directa."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:352
+#: i2p2www/pages/site/docs/transport/ssu.html:356
 msgid "Peer testing"
-msgstr ""
+msgstr "Prueba del par"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:354
+#: i2p2www/pages/site/docs/transport/ssu.html:358
 msgid ""
 "The automation of collaborative reachability testing for peers is\n"
 "enabled by a sequence of PeerTest messages.  With its proper \n"
@@ -24374,8 +21611,13 @@ msgid ""
 "and may update its behavior accordingly.  The testing process is \n"
 "quite simple:"
 msgstr ""
+"La automatización del las pruebas colaborativas de accesibilidad de un "
+"par es habilitada por una secuencia de mensajes PeerTest. Con su buen "
+"funcionamiento, el par será capaz de determinar su estado de "
+"accesibilidad y puede actualizar su comportamiento de acuerdo con ello. "
+"El proceso de prueba es bastante simple:"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:373
+#: i2p2www/pages/site/docs/transport/ssu.html:377
 msgid ""
 "Each of the PeerTest messages carry a nonce identifying the\n"
 "test series itself, as initialized by Alice.  If Alice doesn't \n"
@@ -24384,8 +21626,14 @@ msgid ""
 "missing, she will know her reachability.  The various end states\n"
 "that may be reached are as follows:"
 msgstr ""
+"Cada uno de los mensajes PeerTest lleva un nonce identificando las series"
+" de pruebas, como fueron inicializadas por Alice. Si Alice no recibe un "
+"mensaje en particular que estuviese esperando, ella retransmitirá de "
+"acuerdo con ello, y basándose en los datos recibidos o en los mensajes "
+"perdidos, ella conocerá su estado de accesibilidad. Los estados a los que"
+" puede llegar son:"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:383
+#: i2p2www/pages/site/docs/transport/ssu.html:387
 msgid ""
 "If she doesn't receive a response from Bob, she will retransmit\n"
 "up to a certain number of times, but if no response ever arrives,\n"
@@ -24394,8 +21642,14 @@ msgid ""
 "outbound packet.  Alternately, Bob may be down or unable to get \n"
 "Charlie to reply."
 msgstr ""
+"Si no recibe una respuesta de Bob, ella retransmitirá un número de veces "
+"dado, pero si nunca llega una respuesta, ella sabrá que su cortafuegos o "
+"NAT están desconfigurados de alguna forma, denegando todos los paquetes "
+"UDP de entrada incluso con una respuesta directa a un paquete de salida. "
+"Alternativamente, Bob puede estar caído o incapaz de hacer que Charlie "
+"responda."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:392
+#: i2p2www/pages/site/docs/transport/ssu.html:396
 msgid ""
 "If Alice doesn't receive a PeerTest message with the \n"
 "expected nonce from a third party (Charlie), she will retransmit\n"
@@ -24406,8 +21660,16 @@ msgid ""
 "attempts and that port forwarding is not operating properly (the\n"
 "IP and port that Bob offered up should be forwarded)."
 msgstr ""
+"Si Alice no recibe un mensaje PeerTest con el nonce esperado de una "
+"tercera parte (Charlie), retransmitirá su petición inicial a Bob un "
+"cierto número de veces, incluso si ya ha recibido la respuesta de Bob. Si"
+" el primer mensaje de Charlie no pasa a través, pero el de Bob sí, ella "
+"sabe que está tras un NAT o cortafuegos que deniega los intentos de "
+"conexiones no solicitadas y que el reenvío de ese puerto no funciona "
+"correctamente (la IP y el puerto que Bob ofrece deberían estar "
+"reenviados/forwarded)."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:403
+#: i2p2www/pages/site/docs/transport/ssu.html:407
 msgid ""
 "If Alice receives Bob's PeerTest message and both of Charlie's\n"
 "PeerTest messages but the enclosed IP and port numbers in Bob's \n"
@@ -24417,16 +21679,27 @@ msgid ""
 "explicitly forward a port and always have that port exposed for \n"
 "remote connectivity, ignoring further port discovery."
 msgstr ""
+"Si Alice recibe el mensaje PeerTest de Bob y los dos mensajes PeerTest de"
+" Charle, pero la IP y el puerto de Bob adjuntos y el segundo mensaje de "
+"Charlie no coinciden, ella sabe que está bajo un NAT simétrico que está "
+"reescribiendo todos sus paquetes de salida con los puertos 'desde' "
+"cambiados para cada uno de los pares contactados. Ella necesitará abrir "
+"explícitamente un puerto y tener ese puesto expuesto siempre a las "
+"conexiones remotas, ignorando cualquier búsqueda de puertos futura."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:413
+#: i2p2www/pages/site/docs/transport/ssu.html:417
 msgid ""
 "If Alice receives Charlie's first message but not his second,\n"
 "she will retransmit her PeerTest message to Charlie up to a \n"
 "certain number of times, but if no response is received she knows\n"
 "that Charlie is either confused or no longer online."
 msgstr ""
+"Si Alice recibe el primer mensaje de Charlie pero no el segundo, ella "
+"retransmitirá su mensaje PeerTest a Charlie un cierto número de veces, "
+"pero si no se recibe ninguna respuesta sabrá que o Charlie está "
+"confundido o no está encendido."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:421
+#: i2p2www/pages/site/docs/transport/ssu.html:425
 msgid ""
 "Alice should choose Bob arbitrarily from known peers who seem\n"
 "to be capable of participating in peer tests.  Bob in turn should\n"
@@ -24436,8 +21709,16 @@ msgid ""
 "(Alice doesn't get PeerTest messages from Bob), Alice may decide\n"
 "to designate a new peer as Bob and try again with a different nonce."
 msgstr ""
+"Alice debería elegir a Bob arbitrariamente entre los pares conocidos que "
+"parezcan ser capaces de participar el las pruebas de pares. Bob a su vez "
+"debería elegir a Charlie arbitrariamente entre los pares conocidos que "
+"parezcan ser capaces de participar el las pruebas de pares y que están en"
+" una IP diferente a la de Bob y Alice. Si ocurre la primera condición de "
+"error (Alice no recibe el mensaje PeerTest de Bob), Alice puede decidir "
+"designar un nuevo par como Bob e intentar de nuevo con un nonce "
+"diferente."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:431
+#: i2p2www/pages/site/docs/transport/ssu.html:435
 msgid ""
 "Alice's introduction key is included in all of the PeerTest \n"
 "messages so that she doesn't need to already have an established\n"
@@ -24445,12 +21726,17 @@ msgid ""
 "any additional information.  Alice may go on to establish a session\n"
 "with either Bob or Charlie, but it is not required."
 msgstr ""
+"La clave de introducción de Alice es incluida en todos los mensajes "
+"PeerTest para que no necesite una conexión ya establecida con Bob y para "
+"que Charlie pueda contactar con ella sin necesidad de tener más datos. "
+"Alice puede establecer una sesión con Bob o Charlie, pero no es "
+"necesario."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:449
+#: i2p2www/pages/site/docs/transport/ssu.html:453
 msgid "Transmission window, ACKs and Retransmissions"
-msgstr ""
+msgstr "Window,ventana, de retransmisión, ACKs y Retrasmisiones"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:450
+#: i2p2www/pages/site/docs/transport/ssu.html:454
 #, python-format
 msgid ""
 "The DATA message may contain ACKs of full messages and\n"
@@ -24459,8 +21745,12 @@ msgid ""
 "the protocol specification page\n"
 "for details."
 msgstr ""
+"El mensaje de DATOS puede contener ACKs de mensajes completos y ACKs "
+"parciales de fragmentos individuales de un mensaje. Vea la sección de los"
+" mensajes de datos de la página de especificación"
+" del protocolo para más detalles."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:458
+#: i2p2www/pages/site/docs/transport/ssu.html:462
 #, python-format
 msgid ""
 "The details of windowing, ACK, and retransmission strategies are not "
@@ -24474,12 +21764,20 @@ msgid ""
 "or streaming.\n"
 "See the code for initial, min and max parameters."
 msgstr ""
+"Los detalles de las Windows, ACKS y las estrategias de retransmisión no "
+"se especifican aquí. Vea el código de Java para ver la implementación "
+"actual. Durante la fase de establecimiento, y para las pruebas de pares, "
+"los ruters deberían implementar backoff exponencial para la "
+"retransmisión. Para una conexión establecida, los ruters deberían "
+"implementar una ventana de retransmisión ajustable, RTT estimado y tiempo"
+" de espera, similar al TCP o streaming. Vea"
+" el código para los valores iniciales, mínimos y máximos."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:470
+#: i2p2www/pages/site/docs/transport/ssu.html:474
 msgid "Security"
-msgstr ""
+msgstr "Seguridad"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:471
+#: i2p2www/pages/site/docs/transport/ssu.html:475
 msgid ""
 "UDP source addresses may, of course, be spoofed.\n"
 "Additionally, the IPs and ports contained inside specific\n"
@@ -24487,32 +21785,45 @@ msgid ""
 "may not be legitimate.\n"
 "Also, certain actions and responses may need to be rate-limited."
 msgstr ""
+"La dirección de la fuente UDP puede, por supuesto, ser falseada. "
+"Adicionalmente, las IPs y los puertos contenidos en los mensajes SSU "
+"específicos (RelayRequest, RelayResponse, RelayIntro, PeerTest) puede que"
+" no sean legítimos. Además, algunas acciones y respuestas pueden "
+"necesitar de ser vueltas a limitar."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:479
+#: i2p2www/pages/site/docs/transport/ssu.html:483
 msgid ""
 "The details of validation are not specified\n"
 "here. Implementers should add defenses where appropriate."
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ssu.html:485
-msgid "Peer capabilities"
-msgstr ""
+"Los detalles de validación no están especificados aquí. Los "
+"desarrolladores deberían añadir defensas donde sea apropiado."
 
 #: i2p2www/pages/site/docs/transport/ssu.html:489
+msgid "Peer capabilities"
+msgstr "Capacidades del par"
+
+#: i2p2www/pages/site/docs/transport/ssu.html:493
 msgid ""
 "If the peer address contains the 'B' capability, that means \n"
 "they are willing and able to participate in peer tests as\n"
 "a 'Bob' or 'Charlie'."
 msgstr ""
+"Si la dirección del par contiene la capacidad 'B', esto significa que "
+"desea y puede participar en una prueba de par como un 'Bob' o como un "
+"'Charlie'."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:495
+#: i2p2www/pages/site/docs/transport/ssu.html:499
 msgid ""
 "If the peer address contains the 'C' capability, that means\n"
 "they are willing and able to serve as an introducer - serving\n"
 "as a Bob for an otherwise unreachable Alice."
 msgstr ""
+"Si la dirección del par contiene la capacidad 'C', esto significa que "
+"desea y puede servir como un introductor - funcionando como un Bob para "
+"un Alice, que de otra forma dería inaccesible."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:504
+#: i2p2www/pages/site/docs/transport/ssu.html:508
 msgid ""
 "Analysis of current SSU performance, including assessment of window size "
 "adjustment\n"
@@ -24520,15 +21831,21 @@ msgid ""
 "improve\n"
 "performance, is a topic for future work."
 msgstr ""
+"El análisis del rendimiento actual del SSU es un tema para un trabajo "
+"futuro, incluyendo la valoración del ajuste del tamaño de ventana y otros"
+" parámetros, y el ajuste de la implementación del protocolo para mejorar "
+"el rendimiento."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:510
+#: i2p2www/pages/site/docs/transport/ssu.html:514
 msgid ""
 "The current implementation repeatedly sends acknowledgments for the same "
 "packets,\n"
 "which unnecessarily increases overhead."
 msgstr ""
+"La implementación actual envía repetidamente reconocimientos para los "
+"mismos paquetes, lo que aumenta la sobrecarga innecesariamente."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:515
+#: i2p2www/pages/site/docs/transport/ssu.html:519
 msgid ""
 "The default small MTU value of 620 should be analyzed and possibly "
 "increased.\n"
@@ -24536,85 +21853,109 @@ msgid ""
 "Does a streaming lib 1730-byte packet fit in 3 small SSU packets? "
 "Probably not."
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ssu.html:521
-msgid "The protocol should be extended to exchange MTUs during the setup."
-msgstr ""
+"El pequeño valor por defecto del MTU de 620 debería ser analizado y "
+"probablemente aumentado. La estrategia actual de adaptación del MTU "
+"debería ser evaluada. ¿Cabe un paquete de streaming de 1730 bytes en 3 "
+"paquetes pequeños SSU? Probablemente no."
 
 #: i2p2www/pages/site/docs/transport/ssu.html:525
-msgid "Rekeying is currently unimplemented and may never be."
+msgid "The protocol should be extended to exchange MTUs during the setup."
 msgstr ""
+"El protocolo debería ser ampliado para intercambiar MTUs durante la "
+"configuración."
 
 #: i2p2www/pages/site/docs/transport/ssu.html:529
+msgid "Rekeying is currently unimplemented and may never be."
+msgstr "Rekeying no está implementado y puede que nunca lo esté."
+
+#: i2p2www/pages/site/docs/transport/ssu.html:533
 msgid ""
 "The potential use of the 'challenge' fields in RelayIntro and "
 "RelayResponse,\n"
 "and use of the padding field in SessionRequest and SessionCreated, is "
 "undocumented."
 msgstr ""
+"El uso potencial de los campos \"desafío\" en el RelayIntro y en el "
+"RelayResponse, y el uso del campo de relleno en el SessionRequest en el  "
+"SessionCreated, no están documentados."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:534
+#: i2p2www/pages/site/docs/transport/ssu.html:538
 msgid ""
 "Instead of a single fragment per packet, a more efficient\n"
 "strategy may be to bundle multiple message fragments into the same "
 "packet,\n"
 "so long as it doesn't exceed the MTU."
 msgstr ""
+"En vez de un sólo fragmento por paquete, una estrategia más eficiente "
+"podría ser el juntar varios fragmentos de mensajes dentro del mismo "
+"paquete, mientras no exceda el MTU."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:540
+#: i2p2www/pages/site/docs/transport/ssu.html:544
 msgid ""
 "A set of fixed packet sizes may be appropriate to further hide the data \n"
 "fragmentation to external adversaries, but the tunnel, garlic, and end to"
 " \n"
 "end padding should be sufficient for most needs until then."
 msgstr ""
+"Un conjunto de tamaños de paquetes podría ser apropiado para la "
+"ocultación futura de la fragmentación de los datos a adversarios "
+"externos, pero el túnel, garlic, y un relleno de fin a fin deberían ser "
+"suficiente para la mayoría de las necesidades hasta entonces."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:546
+#: i2p2www/pages/site/docs/transport/ssu.html:550
 msgid ""
 "Why are introduction keys the same as the router hash, should it be "
 "changed, would there be any benefit?"
 msgstr ""
-
-#: i2p2www/pages/site/docs/transport/ssu.html:550
-msgid "Capacities appear to be unused."
-msgstr ""
+"¿Por qué son las claves de introducción las mismas que el hash del ruter,"
+" deberían cambiarse, habría algún beneficio?"
 
 #: i2p2www/pages/site/docs/transport/ssu.html:554
+msgid "Capacities appear to be unused."
+msgstr "Las capacidades parecen estar sin usar."
+
+#: i2p2www/pages/site/docs/transport/ssu.html:558
 msgid ""
 "Signed-on times in SessionCreated and SessionConfirmed appear to be "
 "unused or unverified."
 msgstr ""
+"Los tiempos acordados en SessionCreated (sesión creada) y "
+"SessionConfirmed (sesión confirmada) parecen estar sin usar o verificar."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:559
+#: i2p2www/pages/site/docs/transport/ssu.html:563
 msgid "Implementation Diagram"
-msgstr ""
+msgstr "Diagrama de implementación"
 
-#: i2p2www/pages/site/docs/transport/ssu.html:560
+#: i2p2www/pages/site/docs/transport/ssu.html:564
 msgid ""
 "This diagram\n"
 "should accurately reflect the current implementation, however there may "
 "be small differences."
 msgstr ""
+"El diagrama debe reflejar con exactitud la implementación actual, sin "
+"embargo puede haber muchas diferencias pequeñas."
 
-#: i2p2www/pages/site/docs/transport/ssu.html:568
+#: i2p2www/pages/site/docs/transport/ssu.html:572
 msgid "Now on the SSU specification page"
 msgstr ""
+"En la actualidad en la página de especificación SSU (UDP seguro "
+"semiconfiable)"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:2
 msgid "Tunnel Implementation"
-msgstr ""
+msgstr "Implementación de túnel"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:3
 msgid "October 2010"
-msgstr ""
+msgstr "Octubre de 2010"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:7
 msgid "This page documents the current tunnel implementation."
-msgstr ""
+msgstr "Esta página documenta la implementación actual del túnel."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:9
 msgid "Tunnel overview"
-msgstr ""
+msgstr "Introducción a los túneles"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:11
 msgid ""
@@ -24631,6 +21972,23 @@ msgid ""
 "bundled up by the gateway and forwards them as instructed - either\n"
 "to another router, to another tunnel on another router, or locally."
 msgstr ""
+"Dentro de I2P, los mensajes se pasan en una dirección a través de un "
+"túnel \n"
+"virtual de pares (`peers`), usando cualquier medio que esté disponible "
+"para \n"
+"pasar el mensaje al siguiente salto. Los mensajes llegan a la "
+"pasarela \n"
+"(`gateway`) del túnel, son empaquetados y/o fragmentados en mensajes de \n"
+"túnel de tamaño-fijo, y son reenviados hacia el siguiente salto en el "
+"túnel, \n"
+"que procesa y verifica la validez del mensaje y lo envía al siguiente "
+"salto, y \n"
+"así sucesivamente, hasta que alcanza el extremo del túnel. Ese "
+"extremo \n"
+"toma los mensajes empaquetados por la pasarela y los reenvía como se \n"
+"se le ha indicado - bien hacia otro router, bien hacia otro túnel en otro"
+" router, \n"
+"o bien localmente."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:23
 msgid ""
@@ -24641,6 +21999,14 @@ msgid ""
 "tunnels, the tunnel creator serves as the gateway, passing messages\n"
 "out to the remote endpoint."
 msgstr ""
+"Los túneles funcionan todos de la misma forma, pero pueden estar \n"
+"segmentados en dos diferentes grupos - túneles de entrada o túneles de \n"
+"salida. Los túneles de entrada tienen una pasarela (`gateway`) no "
+"confiable \n"
+"que pasa mensajes hacia el creador del túnel, que sirve como extremo del "
+"túnel. Para túneles de salida, el creador del túnel hace de pasarela "
+"pasando \n"
+"mensajes al exterior hacia el extremo remoto."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:32
 msgid ""
@@ -24656,6 +22022,18 @@ msgid ""
 "peers are\n"
 "next to each other in the tunnel)."
 msgstr ""
+"El creador del túnel selecciona exactamente qué pares (`peers`) "
+"participarán \n"
+"en el túnel, y proporciona a cada uno los datos de configuración "
+"necesarios. \n"
+"Pueden tener cualquier número de saltos. La intención es hacer difícil, "
+"tanto \n"
+"a los partícipantes en el túnel como a terceros, determinar la longitud "
+"de un \n"
+"túnel, o incluso que unos participantes compinchados determinen si ellos"
+" \n"
+"forman parte de un mismo túnel (impidiendo la situación en la que pares "
+"compinchados estén próximos unos de otros en el túnel)."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:43
 msgid ""
@@ -24666,6 +22044,14 @@ msgid ""
 "of pools for participating in the network database and for managing\n"
 "the tunnels themselves."
 msgstr ""
+"En la práctica, una serie de depósitos (`pools`) de túneles se usan para "
+"diferentes propósitos - cada destino de cliente local tiene su propio \n"
+"conjunto de túneles de entrada configurados para alcanzar sus necesidades"
+" \n"
+"de anonimato y rendimiento. Además, el propio router mantiene una serie "
+"de depósitos para participar en la base de datos de red y para "
+"administrar \n"
+"los propios túneles."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:52
 msgid ""
@@ -24676,6 +22062,15 @@ msgid ""
 "available for client applications, exposing TCP-esque operation,\n"
 "including message reordering, retransmission, congestion control, etc."
 msgstr ""
+"I2P es inherentemente una red de paquetes conmutados, incluso con estos \n"
+"túneles, lo que le permite aprovechar la ventaja de múltiples túneles \n"
+"ejecutándose en paralelo, incrementando la flexibilidad y el equilibrado "
+"de la\n"
+"carga. Fuera del núcleo de la capa I2P, hay una librería streaming (de "
+"flujo) \n"
+"extremo a extremo opcional disponible para aplicaciones cliente, que \n"
+"ofrece operaciones estilo-TCP, incluyendo reordenamiento de mensajes, \n"
+"retransmisión, control de congestión, etc."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:61
 #, python-format
@@ -24683,10 +22078,12 @@ msgid ""
 "An overview of I2P tunnel terminology is\n"
 "on the tunnel overview page."
 msgstr ""
+"Encontrará una introducción a la terminología de túneles I2P en la página de introducción a los túneles."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:66
 msgid "Tunnel Operation (Message Processing)"
-msgstr ""
+msgstr "Operaciones de los túneles (procesamiento de mensajes)"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:69
 #, python-format
@@ -24696,6 +22093,11 @@ msgid ""
 "Tunnel operation has four distinct processes, taken on by various \n"
 "peers in the tunnel."
 msgstr ""
+"Después de que un túnel sea erigido, los mensajes "
+"I2NP (protocolo de red I2P) se procesan y se pasan a través de él. "
+"Las operaciones de los túneles comprenden cuatro procesos diferentes, "
+"llevados \n"
+"a cabo por diferentes pares (`peers`) en el túnel."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:75
 msgid ""
@@ -24703,12 +22105,16 @@ msgid ""
 "of I2NP messages and preprocesses them into tunnel messages for\n"
 "delivery."
 msgstr ""
+"Primero, la pasarela (`gateway`) del túnel acumula un número de mensajes "
+"I2NP y los preprocesa en mensajes de túnel para su entrega."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:80
 msgid ""
 "Next, that gateway encrypts that preprocessed data, then\n"
 "forwards it to the first hop."
 msgstr ""
+"Después, esa pasarela cifra los datos preprocesados, luego los reenvía al"
+" primer salto."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:84
 msgid ""
@@ -24716,6 +22122,10 @@ msgid ""
 "participants, unwrap a layer of the encryption, verifying that it isn't\n"
 "a duplicate, then forward it on to the next peer."
 msgstr ""
+"Ese par (`peer`), y los subsiguientes participantes en el túnel, "
+"desenvuelven \n"
+"una capa del cifrado, verificando que no esté duplicada, y luego la \n"
+"reenvían hacia el siguiente par."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:89
 msgid ""
@@ -24724,6 +22134,9 @@ msgid ""
 "originally bundled by the gateway are reassembled and forwarded on as \n"
 "requested."
 msgstr ""
+"Eventualmente, los mensajes de túnel llegan al extremo donde los mensajes"
+" I2NP fueron originalmente empaquetados por la pasarela, \n"
+"entonces son reensamblados y reenviados de la forma requerida."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:96
 msgid ""
@@ -24733,84 +22146,97 @@ msgid ""
 "to \"decrypt\" at the outbound tunnel gateway,\n"
 "so that the plaintext is revealed at the outbound endpoint."
 msgstr ""
+"Los participantes intermedios del túnel no saben si ellos están en un "
+"túnel\n"
+"de entrada o de salida; ellos siempre \"cifran\" para el siguiente salto."
+" Por lo \n"
+"tanto, aprovechamos la ventaja del cifrado AES simétrico para "
+"\"descifrar\" en \n"
+"la pasarela (`gateway`) del túnel de salida, así que el texto plano se "
+"revela \n"
+"en el extremo de salida."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:110
 msgid "Role"
-msgstr ""
+msgstr "Rol"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:111
 msgid "Preprocessing"
-msgstr ""
+msgstr "Preprocesado"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:112
 msgid "Encryption Operation"
-msgstr ""
+msgstr "Operación de cifrado"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:113
 msgid "Postprocessing"
-msgstr ""
+msgstr "Posprocesado"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:117
 msgid "Outbound Gateway (Creator)"
-msgstr ""
+msgstr "Pasarela (`gateway`) saliente (Creador)"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:118
 #: i2p2www/pages/site/docs/tunnels/implementation.html:141
 msgid "Fragment, Batch, and Pad"
-msgstr ""
+msgstr "Fragmento, lote, y fardo"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:119
 msgid "Iteratively encrypt (using decryption operations)"
-msgstr ""
+msgstr "Cifrar iterativamente (usando operaciones de descifrado)"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:120
 #: i2p2www/pages/site/docs/tunnels/implementation.html:127
 #: i2p2www/pages/site/docs/tunnels/implementation.html:143
 #: i2p2www/pages/site/docs/tunnels/implementation.html:150
 msgid "Forward to next hop"
-msgstr ""
+msgstr "Reenvíar al siguiente salto"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:124
 #: i2p2www/pages/site/docs/tunnels/implementation.html:147
 msgid "Participant"
-msgstr ""
+msgstr "Participante"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:126
 msgid "Decrypt (using an encryption operation)"
-msgstr ""
+msgstr "Descifrar (usando una operación de cifrado)"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:133
 msgid "Decrypt (using an encryption operation) to reveal plaintext tunnel message"
 msgstr ""
+"Descifrar (usando una operación de cifrado) para revelar el mensaje de "
+"túnel de texto plano"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:134
 msgid "Reassemble Fragments, Forward as instructed to Inbound Gateway or Router"
 msgstr ""
+"Reensamblar fragmentos, reenviar hacia la pasarela (`gateway`) o router "
+"entrante tal como se indicó"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:142
 #: i2p2www/pages/site/docs/tunnels/implementation.html:149
 msgid "Encrypt"
-msgstr ""
+msgstr "Cifrar"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:154
 msgid "Inbound Endpoint (Creator)"
-msgstr ""
+msgstr "Extremo de entrada (Creador)"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:156
 msgid "Iteratively decrypt to reveal plaintext tunnel message"
-msgstr ""
+msgstr "Descifrar iterativamente para revelar mensajes de túnel de texto plano"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:157
 msgid "Reassemble Fragments, Receive data"
-msgstr ""
+msgstr "Reensamblar fragmentos, recibir datos"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:163
 msgid "Gateway Processing"
-msgstr ""
+msgstr "Procesado de la pasarela (`gateway`)"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:164
 msgid "Message Preprocessing"
-msgstr ""
+msgstr "Preprocesado de mensaje"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:166
 #, python-format
@@ -24821,26 +22247,33 @@ msgid ""
 "and encrypt the tunnel messages.\n"
 "Tunnel messages contain the following:"
 msgstr ""
+"Una función de la pasarela (`gateway`) del túnel es fragmentar y "
+"empaquetar \n"
+"mensajes I2NP (protocolo de red I2P) en mensajes de túnel de tamaño-fijo y cifrar "
+"los mensajes de túnel. Los mensajes de túnel contienen lo siguiente: "
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:174
 msgid "A 4 byte Tunnel ID"
-msgstr ""
+msgstr "Un identificador (`ID`) de túnel de 4 bytes"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:175
 msgid "A 16 byte IV (initialization vector)"
-msgstr ""
+msgstr "Un IV (vector de inicialización) de 16 bytes"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:176
 msgid "A checksum"
-msgstr ""
+msgstr "Un identificador criptográfico (`checksum`)"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:177
 msgid "Padding, if necessary"
 msgstr ""
+"Relleno (datos inútiles desechables criptográficamente), si fuera "
+"necesario"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:178
 msgid "One or more { delivery instruction, I2NP message fragment } pairs"
-msgstr ""
+msgstr "Uno o más pares { instrucción de entrega, fragmento de mensaje I2NP }"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:181
 msgid ""
@@ -24853,6 +22286,18 @@ msgid ""
 "Even if subsequent tunnels are built using the same sequence of \n"
 "peers, each hop's tunnel ID will change."
 msgstr ""
+"Los identificadores (`IDs`) de túnel tienen números de 4 bytes usados en"
+" \n"
+"cada salto - los participantes saben con qué identificadores (`ID`) de "
+"túnel escuchar mensajes y sobre qué túneles deben ser reenviados hacia el"
+" siguiente salto, y cada salto elije el identificador (`ID`) de túnel "
+"sobre el cual \n"
+"recibe los mensajes. Los propios túneles son de vida-corta (10 minutos)."
+" \n"
+"Incluso si los subsiguientes túneles se erigen usando la misma secuencia"
+" \n"
+"de pares (`peers`), el identificador (`ID`) de túnel de cada salto "
+"cambiará."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:190
 msgid ""
@@ -24868,6 +22313,18 @@ msgid ""
 "from the\n"
 "fragments for a short period of time, but will discard them as necessary."
 msgstr ""
+"Para evitar que los adversarios marquen los mensajes a través de la ruta"
+" \n"
+"ajustando el tamaño del mensaje, todos los mensajes de túnel tienen un \n"
+"tamaño fijo de 1024 bytes. Para acomodar mensajes I2NP (protocolo de red"
+" \n"
+"I2P) más grandes así como para dar soporte a los más pequeños de forma \n"
+"más eficiente, la pasarela (`gateway`) divide los mensajes I2NP más \n"
+"grandes en fragmentos contenibles en cada mensaje de túnel. El extremo \n"
+"del túnel intentará reconstruir el mensaje I2NP partiendo de los "
+"fragmentos \n"
+"durante un corto periodo de tiempo, pero los descartará cuando sea "
+"necesario."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:199
 #, python-format
@@ -24875,10 +22332,12 @@ msgid ""
 "Details are in the\n"
 "tunnel message specification."
 msgstr ""
+"Los detalles están en la especificación de "
+"mensaje de túnel."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:205
 msgid "Gateway Encryption"
-msgstr ""
+msgstr "Cifrado de la pasarela (`gateway`)"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:207
 msgid ""
@@ -24889,6 +22348,14 @@ msgid ""
 "necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel "
 "message} to the next hop."
 msgstr ""
+"Después del preprocesado de mensajes hacia una carga con datos de "
+"relleno, \n"
+"la pasarela (`gateway`) construye un valor de IV (vector de "
+"inicialización) \n"
+"aleatorio de 16 bytes, cifrando a este y al mensaje de túnel "
+"iterativamente tanto como se necesite, y reenvía la tupla { tunnelID, IV,"
+" mensaje de túnel \n"
+"cifrado } al siguiente salto."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:213
 msgid ""
@@ -24908,10 +22375,25 @@ msgid ""
 "recover \n"
 "the initial preprocessed data."
 msgstr ""
+"Cómo se hace el cifrado en la pasarela (`gateway`) depende de si el túnel"
+" \n"
+"es de entrada o de salida. Para los túneles entrantes, simplemente eligen"
+" \n"
+"un IV (vector de inicialización) aleatorio, posprocesándolo y "
+"actualizándolo \n"
+"para generar el IV para la pasarela y usar ese IV junto con su propia "
+"clave \n"
+"de capa para cifrar los datos preprocesados. Para túneles salientes deben"
+" descifrar iterativamente el (no cifrado) IV y los datos preprocesados, "
+"con el IV y las claves de capa para todos los saltos en el túnel. El "
+"resultado \n"
+"del cifrado del túnel de salida es que cuando cada par (`peer`) lo cifra,"
+" el \n"
+"extremo recuperará los datos preprocesados iniciales."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:225
 msgid "Participant Processing"
-msgstr ""
+msgstr "Procesado de los participantes"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:227
 msgid ""
@@ -24934,6 +22416,24 @@ msgid ""
 "of the IV (both before and after use) help address a certain class of\n"
 "confirmation attacks."
 msgstr ""
+"Cuando un par (`peer`) recibe un mensaje de túnel, comprueba que el \n"
+"mensaje venga desde el mismo salto previo que antes (inicializado cuando"
+" \n"
+"el primer mensaje atraviesa el túnel). Si el par previo está en un router"
+" \n"
+"diferente, o si el mensaje ha sido visto ya, el mensaje es descartado. \n"
+"Entonces el participante cifra el IV (vector de inicialización) recibido "
+"con \n"
+"AES256/ECB usando su clave IV para determinar el IV actual, usa ese \n"
+"IV con la clave de capa del participante para cifrar los datos, cifra el "
+"actual \n"
+"IV con AES256/ECB usando la clave IV otra vez, y luego reenvía la tupla \n"
+"{nextTunnelId, nextIV, encryptedData} (siguiente identificador de túnel, "
+"siguiente IV, datos cifrados) al siguiente salto. Este doble cifrado del "
+"IV \n"
+"(tanto antes como después de su uso) ayuda a afrontar una cierta clase de"
+" \n"
+"ataques de confirmación."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:240
 msgid ""
@@ -24956,10 +22456,25 @@ msgid ""
 "from tagging a message by resending it with the IV and first block "
 "switched."
 msgstr ""
+"La detección de mensajes duplicados es gestionada por un filtro Bloom \n"
+"decadente (en el tiempo) sobre los IVs (vectores de inicialización) de "
+"los \n"
+"mensajes. Cada router mantiene un único filtro Bloom para guardar el XOR"
+" \n"
+"del IV con el primer bloque del mensaje recibido para todos los túneles "
+"en los que está participando, modificado (decadencia) para descartar "
+"entradas vistas después de 10-20 minutos (cuando los túneles habrán "
+"expirado). \n"
+"El tamaño del filtro Bloom y los parámetros usados son suficientes para "
+"más que saturar la conexión de red del router con una insignificante "
+"posibilidad de falso positivo. El único valor añadido en el filtro Bloom "
+"es el XOR del IV y el primer bloque como forma de prevenir que pares "
+"(`peers`) compinchados no secuenciales en el túnel, marquen un mensaje "
+"reenviándolo con el IV y el primer bloque cambiados."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:253
 msgid "Endpoint Processing"
-msgstr ""
+msgstr "Procesado en el extremo"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:255
 msgid ""
@@ -24977,6 +22492,19 @@ msgid ""
 " using the \n"
 "layer and IV keys of each step in reverse order."
 msgstr ""
+"Después de recibir y validar un mensaje de túnel en el último salto del "
+"túnel, la forma en la que el extremo recupera los datos codificados por "
+"la pasarela \n"
+"(`gateway`) depende de si el túnel es de entrada o de salida. Para "
+"túneles salientes, el extremo cifra el mensaje con su clave de capa tal "
+"como lo hace cualquier otro participante (en el túnel), exponiendo los "
+"datos \n"
+"preprocesados. Para túneles entrantes, el extremo también es el creador \n"
+"del túnel, así que pueden meramente descifrar iterativamente el IV "
+"(vector de \n"
+"inicialización) y el mensaje usando las claves de capa e IV de cada paso"
+" \n"
+"en orden inverso."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:265
 msgid ""
@@ -24986,10 +22514,15 @@ msgid ""
 "them as\n"
 "requested in their delivery instructions."
 msgstr ""
+"En este punto, el extremo del túnel tiene los datos preprocesados "
+"enviados por la pasarela (`gateway`), que pueden entonces ser separados "
+"en los mensajes I2NP incluidos, y reenviarlos tal como se requería en sus"
+" \n"
+"instrucciones de entrega."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:272
 msgid "Tunnel Building"
-msgstr ""
+msgstr "Construcción del túnel"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:274
 msgid ""
@@ -25009,6 +22542,18 @@ msgid ""
 "(and \n"
 "replies received), and how they are maintained."
 msgstr ""
+"Cuando se construye un túnel, el creador debe enviar una solicitud con "
+"los \n"
+"datos de configuración necesarios a cada uno de los saltos, y esperar \n"
+"que todos ellos accedan antes de habilitar el túnel. Las solicitudes se "
+"cifran de forma que sólo los pares (`peers`) que necesiten conocer un \n"
+"pedazo de la información (tales como las claves de capa del túnel o de IV"
+" (vector de inicialización)) tienen esos datos. Además, sólo el creador "
+"del \n"
+"túnel tendrá acceso a la respuesta del par. Hay tres dimensiones "
+"importantes a tener en cuenta al generar los túneles: qué pares se usan "
+"(y dónde), cómo se envían las solicitudes (y las respuestas recibidas), y"
+" cómo son mantenidas."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:288
 msgid ""
@@ -25019,10 +22564,16 @@ msgid ""
 "tunnel\n"
 "maintenance, while client tunnels are used for end to end client messages."
 msgstr ""
+"Más allá de los dos tipos de túneles - entrante y saliente - hay dos "
+"estilos de selección del par (`peer`) usados por diferentes túneles - "
+"exploratorio y cliente. Los túneles exploratorios se usan tanto para el "
+"mantenimiento de la \n"
+"base de datos de red como para el mantenimiento del túnel, mientras los \n"
+"túneles de cliente se usan para mensajes de cliente extremo-a-extremo."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:296
 msgid "Exploratory tunnel peer selection"
-msgstr ""
+msgstr "Selección de par de túnel exploratorio"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:298
 msgid ""
@@ -25040,6 +22591,14 @@ msgid ""
 " for\n"
 "use in client tunnels."
 msgstr ""
+"Los túneles exploratorios son construidos de una selección de pares "
+"aleatorios de un subconjunto de la red. Los subconjuntos varían en cada "
+"ruter local y según sean las necesidades de ese túnel. En general, los "
+"túneles exploratorios se construyen a partir de pares seleccionados "
+"aleatoriamente que están en categoría del perfil de par 'no se cae, está "
+"activo' . El segundo fin de los túneles, además de simplemente enrutar, "
+"es encontrar pares de alta capacidad libres para poder usarlos para los "
+"túneles clientes."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:308
 #, python-format
@@ -25047,10 +22606,12 @@ msgid ""
 "Exploratory peer selection is discussed further on the\n"
 "Peer Profiling and Selection page."
 msgstr ""
+"La selección de pares exploratorios se discute más en la página de perfil del par y selección."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:314
 msgid "Client tunnel peer selection"
-msgstr ""
+msgstr "Selección del par para el túnel cliente"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:316
 msgid ""
@@ -25064,6 +22625,13 @@ msgid ""
 "that \n"
 "should be adhered to, depending upon the client's anonymity needs."
 msgstr ""
+"Los túneles cliente son construidos con unos requerimientos más rigurosos"
+" - el ruter local selecciona los pares de la categoría de perfil "
+"\"rápidos y de gran capacidad\" para que el rendimiento y la seguridad se"
+" ajusten a las necesidades de la aplicación cliente. Aunque hay varios "
+"detalles importantes más allá de la selección básica que deben ser "
+"tomados en cuenta, dependiendo de las necesidades de anonimato que "
+"necesite el cliente."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:324
 #, python-format
@@ -25071,10 +22639,12 @@ msgid ""
 "Client peer selection is discussed further on the\n"
 "Peer Profiling and Selection page."
 msgstr ""
+"La selección del par cliente se discute más profundamente en la página de perfil del par y selección."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:329
 msgid "Peer Ordering within Tunnels"
-msgstr ""
+msgstr "Orden de los pares dentro del túnel"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:331
 #, python-format
@@ -25083,6 +22653,9 @@ msgid ""
 "predecessor attack\n"
 "(2008 update)."
 msgstr ""
+"Los pares son ordenados dentro de los túneles para evitar el ataque del predecesor (2008 "
+"update). "
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:338
 msgid ""
@@ -25093,6 +22666,10 @@ msgid ""
 "after A is always B, and the hop after\n"
 "B is always C."
 msgstr ""
+"Para evitar el ataque del predecesor, la selección del túnel mantiene a "
+"los pares seleccionados en estricto orden - si A, B, y C están en un "
+"túnel determinado para un grupo de túneles en particular, el salto "
+"después de A es siempre B, y el salto después de B siempre es C. "
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:345
 msgid ""
@@ -25106,6 +22683,12 @@ msgid ""
 "SHA256 Hash of (the peer's hash concatenated with the random key) from "
 "the random key"
 msgstr ""
+"El orden está implementado generando una clave aleatoria de 32 bytes para"
+" cada grupo de túneles al inicio. Los pares no deberían ser capaces de "
+"adivinar el orden, un atacante podría elaborar aparte dos hashes de ruter"
+" para maximizar las posibilidades de ser las dos puntas del túnel. Los "
+"pares están ordenados por la distancia XOR del hash SHA256 de (el hash "
+"del par concatenado con la clave aleatoria) de la clave aleatoria .  "
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:360
 msgid ""
@@ -25114,10 +22697,13 @@ msgid ""
 "within a single pool but not between different pools.\n"
 "New keys are generated at each router restart."
 msgstr ""
+"Ya que cada grupo de túneles utiliza una clave aleatoria diferente, el "
+"orden es consistente dentro de un mismo grupo pero no entre grupos. Las "
+"claves son generadas al reinicio de cada ruter."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:367
 msgid "Request delivery"
-msgstr ""
+msgstr "Solicitud de entrega"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:369
 #, python-format
@@ -25128,6 +22714,10 @@ msgid ""
 "Hashing it out in Public,\n"
 "this is \"non-interactive\" telescopic tunnel building."
 msgstr ""
+"Un túnel multi-salto es construido usando un solo mensaje de construcción"
+" que es descifrado y enviado repetidamente. En la terminología de Hashing it out in Public, esto es una construcción "
+"de túnel telescópica \"no interactiva\"."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:376
 #, python-format
@@ -25145,6 +22735,14 @@ msgid ""
 "in\n"
 "the \"Hashing it out\" paper.)"
 msgstr ""
+"Este método de preparación, envío y respuesta de la solicitud de túnel "
+"está diseñado para reducir el número "
+"de predecesores expuestos, cortar el número de mensajes transmitidos, "
+"verificar que la conectividad es apropiada y evitar el ataque clásico de "
+"conteo en la creación telescópica de los túneles tradicionales. (Este "
+"método, que envía mensajes para extender un túnel a través de la parte "
+"del túnel ya establecido, es llamado construcción de túnel telescópico "
+"\"interactivo\" en el estudio \"Hashing it out\")"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:387
 #, python-format
@@ -25153,6 +22751,8 @@ msgid ""
 "encryption,\n"
 "are specified here."
 msgstr ""
+"Los detalles de los mensajes de peticiones y respuestas, y su cifrado, se especifican aquí."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:392
 msgid ""
@@ -25168,6 +22768,13 @@ msgid ""
 "profile of\n"
 "the router in question."
 msgstr ""
+"Los pares pueden denegar las peticiones de creación de túnel por varias "
+"razones, a través de una serie de cuatro rechazos cada vez más graves: "
+"rechazo propabilístico (debido a que le ruter se acerca al límite de su "
+"capacidad, o en respuesta de una riada de peticiones), sobrecarga "
+"transitoria, sobrecarga del ancho de banda, y fallo crítico. Cundo son "
+"recibidos, estos cuatro son interpretados por el creador del túnel para "
+"ayudar a ajustar su perfil a la petición del ruter."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:401
 #, python-format
@@ -25175,10 +22782,12 @@ msgid ""
 "For more information on peer profiling, see the\n"
 "Peer Profiling and Selection page."
 msgstr ""
+"Para más información sobre los perfiles del par, vea la página de perfil del par y selección."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:407
 msgid "Tunnel Pools"
-msgstr ""
+msgstr "Grupos de túneles"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:409
 #, python-format
@@ -25200,6 +22809,16 @@ msgid ""
 "href=\"%(i2cp)s\">I2CP, or the router's defaults if\n"
 "not specified."
 msgstr ""
+"Para permitir un funcionamiento eficiente, el ruter mantiene una serie de"
+" grupos de túneles, cada uno manteniendo un conjunto de túneles usados "
+"para un fin específico con su propia configuración. Cuando un túnel se "
+"necesita para ese fin, el ruter selecciona aleatoriamente uno del grupo "
+"apropiado. En total, hay dos grupos de túneles exploratorios - uno de "
+"entrada y uno de salida - cada uno usando la configuración por defecto "
+"del túnel. Además, hay un par de grupos para cada destinación local - un "
+"grupo de entrada y un grupo de salida. Estos grupos usan la configuración"
+" especificada elegida cuando la destinación local conecta al ruter vía I2CP, o si el ruter no especifica una por defecto."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:421
 #, python-format
@@ -25215,18 +22834,25 @@ msgid ""
 "Configuration options are specified on the I2CP "
 "page."
 msgstr ""
+"Cada grupo tiene dentro de su configuración unas pocas opciones clave, "
+"que definen cuantos túneles se mantienen activos, cuantos túneles de "
+"respaldo se mantienen en caso de fallo, cuanto debe durar el túnel, si "
+"esos tamaños deben ser aleatorrizados, y también definen cualquier otra "
+"configuración permitida cuando se configuran los túneles individuales. "
+"Las opciones de configuración son especificadas en la página de I2CP."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:431
 msgid "Tunnel Lengths and Defaults"
-msgstr ""
+msgstr "Longitud de los túneles y valores por defecto"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:433
 msgid "On the tunnel overview page"
-msgstr ""
+msgstr "En la página de introducción al túnel"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:435
 msgid "Anticipatory Build Strategy and Priority"
-msgstr ""
+msgstr "Estrategia de construcción anticipatoria y prioridad"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:437
 msgid ""
@@ -25245,6 +22871,14 @@ msgid ""
 "or consuming too much CPU or bandwidth creating and sending the encrypted"
 " build messages."
 msgstr ""
+"La construcción de un túnel es cara, y los túneles expiran después de un "
+"tiempo fijo de haber sido creados. Sin embargo, el éxito de construcción "
+"de túnel puede variar enormemente según las condiciones de la red local y"
+" global. Por esto, es importante mantener una estrategia de construcción "
+"anticipatoria y adaptativa para asegurarse de que los túneles nuevos, "
+"antes de ser usados, son construidos exitosamente, no se construyen en "
+"exceso, no se construyen demasiado pronto, o consumen demasiada CPU o "
+"ancho de banda al crear y enviar los mensajes de construcción cifrados."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:448
 msgid ""
@@ -25258,6 +22892,14 @@ msgid ""
 "it starts multiple build attempts in parallel, and then\n"
 "will increase the number of parallel attempts if necessary."
 msgstr ""
+"Por cada tupla {esploratorio/cliente, entrada/salida, longitud, "
+"diferencia de longitud} el ruter mantiene estadísticas del tiempo "
+"necesario para la construcción con éxito de un túnel. Usando estas "
+"estadísticas, calcula cuando debe comenzar a intentar crear un reemplazo "
+"antes de la expiración del túnel. Cuando el tiempo de expiración se "
+"acerca sin un reemplazo exitoso, comienza a hacer múltiples intentos de "
+"construcción en paralelo, y entonces aumentará el número de intentos en "
+"paralelo si es necesario."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:459
 msgid ""
@@ -25267,10 +22909,15 @@ msgid ""
 "Critical builds (those for exploratory tunnels, and for pools that have\n"
 "run out of tunnels) are prioritized."
 msgstr ""
+"Para limitar el uso de CPU y ancho de banda, el ruter también limita el "
+"número máximo de intentos de construcción pendientes a través de todos "
+"los grupos. Las construcciones críticas (aquellas para los túneles "
+"exploratorios, y para los grupos que se han quedado sin túneles) son "
+"priorizadas."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:468
 msgid "Tunnel Message Throttling"
-msgstr ""
+msgstr "Límites de los mensajes de túnel"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:470
 msgid ""
@@ -25300,6 +22947,20 @@ msgid ""
 "the \n"
 "normal Internet."
 msgstr ""
+"Aunque los túneles dentro de I2P son parecidos a una red conmutada de "
+"circuito, todo dentro de I2P está basado en mensajes - los túneles no son"
+" más que trucos contables para ayudar a organizar el envío de mensajes. "
+"No se toman suposiciones con respecto a el orden o fiabilidad de los "
+"mensajes, y la retransmisiones son dejadas para los niveles superiores "
+"(por ejemplo para la capa cliente de la librería de streaming de I2P) . "
+"Esto permite a I2P aprovechar las técnicas de limitaciones disponibles en"
+" las redes conmutadas de paquetes y en las redes conmutadas de circuito. "
+"Por ejemplo, cada ruter puede hacer un seguimiento de la media cambiante "
+"de cuantos datos usa cada túnel, combinar eso con todas medias usadas "
+"poro otros túneles en los que participa el ruter, y ser capaz de aceptar "
+"o denegar las peticiones de participación adicional de túnel basándose en"
+" su capacidad y utilización. Por otro lado, cada ruter puede simplemente "
+"denegar los mensajes que están más allá de su capacidad."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:486
 msgid ""
@@ -25324,10 +22985,25 @@ msgid ""
 "network cost of\n"
 "dropping those messages is lower."
 msgstr ""
+"En la implementación actual, los ruters implementan una estrategia de "
+"rechazo temprano ponderada aleatoria, weighted random early discard "
+"(WRED) strategy. Para todos los túneles participantes (participante "
+"interno, puerta de salida de entrada y punto final de salida), el ruter "
+"empezará a denegar una parte de los mensajes según llegue a los límites "
+"del ancho de banda. Cuando el tráfico llega cerca, o excede los límites, "
+"se rechazan más mensajes. Para un participante interno, todos los "
+"mensajes están fragmentados y rellenados y por lo tanto son del mismo "
+"tamaño. En la puerta de salida de entrara y en el punto final de salida, "
+"sin embargo, la decisión de rechazo se hace en el mensaje completo "
+"(junto), y el tamaño del mensaje es tomado en cuenta. Es más fácil que "
+"sean eliminados los mensajes más largos. Además, es más fácil que los "
+"mensajes sean rechazados en el punto final de salida que en la puerta de "
+"salida de entrada, ya que esos mensajes no están tan \"a lo lejos\" en su"
+" camino y el coste del rechazo de esos mensajes es menor."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:504
 msgid "Mixing/batching"
-msgstr ""
+msgstr "Mezcla/lotes"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:506
 msgid ""
@@ -25342,10 +23018,16 @@ msgid ""
 "All of this is left as unknown, to be worked out for a distant future "
 "release."
 msgstr ""
+"¿Qué estrategias pueden usarse en la puerta de salida y en cada salto "
+"para retrasar, re-ordenar, re-enrutar o rellenar los mensajes? ¿En qué "
+"medida debe hacerse esto automáticamente, que configuraciones debemos "
+"poner por túnel o por salto, y cómo debe controlar esta operación el "
+"creador del túnel (y por lo tanto el usuario)?  Todo esto se queda en el "
+"aire, para ser estudiado en una versión futura distante."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:515
 msgid "Padding"
-msgstr ""
+msgstr "Relleno"
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:516
 msgid ""
@@ -25358,6 +23040,11 @@ msgid ""
 "to end \n"
 "messages, they may be padded as part of the garlic wrapping."
 msgstr ""
+"Las estrategias de relleno pueden ser usadas en varios niveles, evitando "
+"la exposición del tamaño de los mensajes a los adversarios. El tamaño "
+"actual fijo del túnel es de 1024 bytes. Pero los propios mensajes "
+"fragmentados no están rellenados por el túnel, por lo que en lo mensajes "
+"de fin a fin, deben ser rellenados como parte del envase garlic."
 
 #: i2p2www/pages/site/docs/tunnels/implementation.html:526
 msgid ""
@@ -25365,10 +23052,14 @@ msgid ""
 "and prevention of network congestion collapse.\n"
 "The current WRED strategy should be carefully evaluated and improved."
 msgstr ""
+"Las estrategias WRED tienen un impacto importante en el rendimiento de "
+"fin a fin, y en la prevención del colapso de la congestión de la red. "
+"Esta estrategia WRED actual debería ser evaluada cuidadosamente y "
+"mejorada."
 
 #: i2p2www/pages/site/docs/tunnels/old-implementation.html:2
 msgid "Old Tunnel Implementation"
-msgstr ""
+msgstr "Implementación vieja del túnel"
 
 #: i2p2www/pages/site/docs/tunnels/old-implementation.html:5
 #, python-format
@@ -25376,6 +23067,8 @@ msgid ""
 "Note: Obsolete - NOT used!  Replaced in 0.6.1.10 - see here for the current implementation"
 msgstr ""
+"Nota: Obsoleta - ¡NO se usa! Reemplazada en la versión 0.6.1.10 - vea esto para la implementación actual."
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:7
 msgid ""
@@ -25383,22 +23076,28 @@ msgid ""
 "tunnels.\n"
 "For further infomrmation see:"
 msgstr ""
+"Esta página describe el origen y el diseño de los túneles "
+"unidireccionales de I2P. Para más información vea:"
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:13
 msgid "Tunnel overview page"
-msgstr ""
+msgstr "Página de la introducción al túnel"
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:19
 msgid "Tunnel design discussion"
-msgstr ""
+msgstr "Discusión sobre el diseño de túnel"
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:21
+msgid "Peer selection"
+msgstr "Selección de pares"
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:23
 msgid "Meeting 125 (~13:12-13:30)"
-msgstr ""
+msgstr "Reunión 125 (~13:12-13:30)"
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:28
 msgid "Review"
-msgstr ""
+msgstr "Revisión"
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:30
 msgid ""
@@ -25416,6 +23115,21 @@ msgid ""
 "Having the response come back along a different path arguably \n"
 "makes it harder."
 msgstr ""
+"Aunque no estamos al tanto de investigación publicada alguna sobre las \n"
+"ventajas de túneles unidireccionales, estos parece que hacen más difícil"
+" \n"
+"detectar un patrón de solicitud/respuesta, lo cual es bastante posible "
+"que\n"
+"se detecte sobre un túnel bidireccional. Varias aplicaciones y "
+"protocolos, \n"
+"notablemente HTTP, transfieren datos de esta manera. Hacer que el tráfico"
+"\n"
+"siga la misma ruta hacia su destino y de vuelta puede ponerlo más fácil \n"
+"para un atacante que sólo disponga de datos tiempo y de volumen de "
+"tráfico \n"
+"para inferir la ruta que está tomando un túnel. Hacer que la respuesta "
+"vuelva \n"
+"a través de otra ruta es razonable que lo haga más difícil."
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:45
 msgid ""
@@ -25433,6 +23147,19 @@ msgid ""
 "the response would come back through one or more different inbound "
 "tunnels."
 msgstr ""
+"Cuando tratamos con un adversario interno o con la mayoría de adversarios"
+" \n"
+"externos, los túneles unidireccionales de I2P exponen como mucho la mitad"
+" \n"
+"de los datos de tráfico que se expondrían con circuitos bidireccionales \n"
+"simplemente observando los propios flujos - una solicitud y respuesta "
+"HTTP \n"
+"seguiría la misma ruta en Tor, mientras que en I2P los paquetes que \n"
+"componen la solicitud saldrían a través de uno o más túneles de salida, y"
+" \n"
+"los paquetes que componen la respuesta retornarían a traves de uno o más"
+" \n"
+"túneles de entrada diferentes."
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:55
 msgid ""
@@ -25460,10 +23187,34 @@ msgid ""
 "(peer selection and ordering strategies)\n"
 "should minimize the worries of the predecessor attack."
 msgstr ""
+"La estrategia de usar dos túneles separados para la comunicación de \n"
+"entrada y de salida no es la única técnica disponible, y tiene "
+"implicaciones \n"
+"en el anonimato. En el lado positivo, al usar túneles separados se "
+"reducen \n"
+"los datos de tráfico expuestos al análisis de los participantes en un "
+"túnel - \n"
+"por ejemplo, los pares (`peers´) en un túnel de entrada desde un "
+"navegador \n"
+"web sólo verían el tráfico de un HTTP GET, mientras que los pares en un \n"
+"túnel de entrada verían la carga entregada a través del túnel. Con "
+"túneles \n"
+"bidireccionales, todos los participantes tendrían acceso al hecho de que,"
+" \n"
+"por ejemplo, 1 KB fuera enviado en una dirección, y después 100 KB en la"
+" \n"
+"otra. En el lado negativo, usar túneles unidireccionales significa que "
+"hay dos \n"
+"conjuntos de pares (`peers`) precisan ser perfilados y fiscalizados, y "
+"que se debe tener una precaución adicional para afrontar el incremento de"
+" velocidad que se ha producido en los ataques de predecesor. El proceso "
+"de depositado (`pooling`) y erigido (selección de pares y estrategias de "
+"ordenación) debería minimizar las preocupaciones por los ataques de "
+"predecesor."
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:73
 msgid "Anonymity"
-msgstr ""
+msgstr "Anonimato"
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:75
 #, python-format
@@ -25472,6 +23223,9 @@ msgid ""
 "declared that I2P's unidirectional tunnels \"seems to be a bad design "
 "decision\"."
 msgstr ""
+"Un estudio reciente de Hermann and Grothoff decía"
+" que los túneles unidireccionales de I2p \"parecían ser una mala decisión"
+" de diseño\""
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:80
 msgid ""
@@ -25484,6 +23238,11 @@ msgid ""
 "disadvantage, at least\n"
 "with long-living eepsites."
 msgstr ""
+"El punto principal del estudio es que de-anonimizar los túneles "
+"unidireccionales toma más tiempo, lo que es una ventaja, pero que el "
+"atacante puede estar más seguro en el caso unidireccional. Por lo tanto, "
+"el estudio dice que no es ninguna ventaja, sino una desventaja, al menos "
+"para las eepsites de vida larga."
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:88
 msgid ""
@@ -25494,6 +23253,10 @@ msgid ""
 "attack in the paper\n"
 "with attacks on a bidirectional tunnel architecture."
 msgstr ""
+"Esta conclusión no está totalmente confirmada en el estudio. Los túneles "
+"unidireccionales mitigan claramente otros ataques y no está claro si es "
+"inteligente sacrificar el riesgo del ataque del estudio por los riesgos "
+"de la arquitectura de túneles bidireccionales."
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:95
 msgid ""
@@ -25506,6 +23269,13 @@ msgid ""
 "close \n"
 "may be good enough, or time may be more important."
 msgstr ""
+"Esta conclusión está basada en una certeza arbitraria vs. la medición del"
+" tiempo (compensación) que no es apreciable en la mayoría de los casos. "
+"Por ejemplo, alguien podría hacer una lista de IPs y entonces expedir "
+"citaciones a cada uno. O el atacante podría hacer DDos a cada uno por "
+"turnos y a través de un simple ataque de intersección ver si la eepsite "
+"se cae o si se ralentiza. Estar cerca puede ser lo suficientemente bueno,"
+" o el tiempo puede ser más importante."
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:104
 msgid ""
@@ -25517,6 +23287,10 @@ msgid ""
 "methods \n"
 "available for final confirmation."
 msgstr ""
+"La conclusión está basada en una forma de medir específica de la "
+"importancia de la certeza vs. el tiempo, y esa medida puede estar "
+"equivocada, y es definitivamente discutible, especialmente en el mundo "
+"real con citaciones, órdenes de registro y otros métodos disponibles."
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:111
 msgid ""
@@ -25530,6 +23304,12 @@ msgid ""
 "done that analysis, if it's even possible to do it\n"
 "effectively."
 msgstr ""
+"Un análisis completo de las compensaciones de los túneles "
+"unidireccionales vs. bidireccionales está claramente fuera del alcance "
+"del estudio, y no se ha hecho en ningún sitio. Por ejemplo, ¿cómo se "
+"compara este ataque con los numerosos posibles ataques publicados sobre "
+"la red onion? Claramente los autores no han hecho ese análisis, si "
+"pudiese ser posible hacerlo efectivamente."
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:120
 msgid ""
@@ -25558,6 +23338,21 @@ msgid ""
 "really a \n"
 "reason?"
 msgstr ""
+"Tor utiliza túneles bidireccionales y tiene mucha revisión académica. I2P"
+" usa túneles unidireccionales y tiene muy poca revisión. ¿Significa la "
+"falta de estudios defendiendo los túneles unidireccionales que son una "
+"mala elección de diseño, o sólo necesita más estudio? Contra los ataques "
+"de tiempo y los ataques distribuidos para I2P y tor es difícil defenderse"
+" para ambos. El intento de diseño (vea las referencias arriba) era que "
+"los túneles de diseño eran más resistentes a los ataques de tiempo. Sin "
+"embargo, el estudio presenta un tipo diferente de ataque de tiempo. ¿Es "
+"este ataque, innovador, suficiente para calificar la arquitectura de "
+"túneles de I2P (y por lo tanto a I2P al completo) de un \"mal diseño\", y"
+" por implicación, claramente inferior a Tor, o simplemente es una "
+"alternativa de diseño que claramente necesita más investigación y "
+"análisis?  Hay otras razones para considerar a I2p inferior a Tor y a "
+"otros proyectos (el pequeño tamaño de la red, falta de fondos, falta de "
+"revisión) ¿pero son los túneles unidireccionales de verdad una razón?"
 
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:137
 msgid ""
@@ -25566,5925 +23361,9 @@ msgid ""
 "tunnels are unequivocally inferior to bidirectional tunnels\", yet this \n"
 "conclusion is not supported by the paper."
 msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:4
-msgid ""
-"Thank you for your interest in contributing to I2P!\n"
-"The details of how you\n"
-"can make your contribution are provided below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:13
-#, python-format
-msgid "You can donate direct via PayPal to the account \"%(account)s\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:19
-msgid "One time donation:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:33
-msgid "Donate 10 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:41
-#: i2p2www/pages/site/get-involved/donate.html:53
-#: i2p2www/pages/site/get-involved/donate.html:65
-#: i2p2www/pages/site/get-involved/donate.html:77
-msgid "I2P donation "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:47
-msgid "Donate 20 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:59
-msgid "Donate 30 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:71
-msgid "Donate 50 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:86
-msgid "Flattr this"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:90
-#, python-format
-msgid ""
-"As of December 2010, eche|on has been running a Bitcoin account for the I2P project. \n"
-"If you'd like to donate using Bitcoin, just transfer your desired amount "
-"of coins to the account \n"
-"%(account)s and leave eche|on a note if you'd like your donation "
-"to be mentioned on the I2P webpage."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:95
-msgid ""
-"If you want to keep more or less anonymous, the option to send money via "
-"mail is also available. But it is less secure\n"
-"as the envelope can be lost on the way to us."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:99
-#, python-format
-msgid ""
-"If you'd like to donate via  snail mail, send an email to %(email)s\n"
-" and you'll receive an email with instructions detailing how to proceed."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:104
-#, python-format
-msgid ""
-"In the meantime, feel free to take a look at the generous donations that "
-"have been\n"
-"given in support of the I2P Project at the hall of fame."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:2
-msgid "Get Involved!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:4
-msgid "We need your help!"
-msgstr "¡Necesitamos tu ayuda!"
-
-#: i2p2www/pages/site/get-involved/index.html:5
-msgid ""
-"To get involved, please feel free to join us on the #i2p IRC channel (on\n"
-"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or "
-"irc.postman.i2p)."
-msgstr ""
-"Para unirse al proyecto, por favor únase a nosotros en el canal #i2p del "
-"IRC (en irc.freenode.net, o dentro de I2P en irc.freshcoffee.i2p o "
-"irc.postman.i2p)."
-
-#: i2p2www/pages/site/get-involved/index.html:9
-#, python-format
-msgid ""
-"If you're interested in joining our team, please"
-" get in\n"
-"touch as we're always looking for eager contributors!"
-msgstr ""
-"¡Si está interesado en unirse a nuestro equipo, "
-"por favor póngase en contacto con nosotros, ya que siempre estamos "
-"buscando ayudantes entusiastas!"
-
-#: i2p2www/pages/site/get-involved/index.html:13
-msgid ""
-"We need help in many areas, and you don't need to know Java to "
-"contribute!\n"
-"Here's a list to help you get started!"
-msgstr ""
-"¡Necesitamos ayuda en muchas áreas, y no necesita saber Java para "
-"contribuir! ¡Aquí hay una lista para ayudarle a decidirse!"
-
-#: i2p2www/pages/site/get-involved/index.html:18
-msgid "Spread the Word!"
-msgstr "¡Extienda la Palabra!"
-
-#: i2p2www/pages/site/get-involved/index.html:19
-msgid ""
-"Tell people about I2P on forums, blogs, and comments to articles.\n"
-"Fix up the Wikipedia article about I2P in your language.\n"
-"Tell your friends."
-msgstr ""
-"Háblele a la gente  sobre I2P en foros, blogs y comentarios de artículos."
-" Mejore la entrada en la Wikipedia sobre I2P en su idioma. Dígaselo a sus"
-" amigos."
-
-#: i2p2www/pages/site/get-involved/index.html:24
-msgid "Testing"
-msgstr "Pruebas"
-
-#: i2p2www/pages/site/get-involved/index.html:25
-#, python-format
-msgid ""
-"Run the latest builds from monotone\n"
-"and report results on #i2p or as bugs on Trac."
-msgstr ""
-"Ejecute las últimas versiones en monotone y "
-"reporte los resultados en #i2p como errores en el Trac."
-
-#: i2p2www/pages/site/get-involved/index.html:30
-msgid ""
-"Help fix the parts of the website that are outdated or incomplete.\n"
-"Translate pages into other languages."
-msgstr ""
-"Ayude a mejorar las partes de la web que están anticuadas o incompletas. "
-"Traduzca las páginas a otros idiomas."
-
-#: i2p2www/pages/site/get-involved/index.html:34
-msgid "Pictures"
-msgstr "Imágenes"
-
-#: i2p2www/pages/site/get-involved/index.html:35
-msgid "Make some more pictures, fix the old ones on the website"
-msgstr "Cree mas imágenes, mejore las viejas de la web"
-
-#: i2p2www/pages/site/get-involved/index.html:39
-msgid "Make an eepsite! Add some content! Contribute to the community!"
-msgstr "¡Cree una eepsite! ¡Añádale contenido! ¡Contribuya a la comunidad!"
-
-#: i2p2www/pages/site/get-involved/index.html:42
-msgid "Services"
-msgstr "Servicios"
-
-#: i2p2www/pages/site/get-involved/index.html:43
-msgid ""
-"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n"
-"a naming service, a search engine, an eepsite monitor... many of these\n"
-"aren't that hard."
-msgstr ""
-"Ejecute algún servicio en su eepsite. Puede ser un proxy, un foro, un "
-"tracker, un servidor de dominios, una motor de búsquedas, un monitor de "
-"eepsites... muchos de estos no son tan difíciles."
-
-#: i2p2www/pages/site/get-involved/index.html:49
-#, python-format
-msgid ""
-"Write or port applications for I2P! There's some guidelines and\n"
-"a list of ideas on the applications page."
-msgstr ""
-"¡Escriba o porte aplicaciones para I2P! Hay algunas guías y una lista de "
-"ideas en la pagina de aplicaciones."
-
-#: i2p2www/pages/site/get-involved/index.html:53
-msgid "Coding"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:54
-#, python-format
-msgid ""
-"There's plenty to do if you know Java or are ready to learn.\n"
-"Check for open tickets on Trac\n"
-"or the TODO list on %(zzz)s for\n"
-"some ideas on where to start.\n"
-"See the new developer's guide for details."
-msgstr ""
-"Hay mucho que hacer si sabe Java o está listo para aprender. Busque "
-"entradas abiertas en el Trac o "
-"en la lista TODO en %(zzz)s para saber "
-"donde empezar o ver algunas ideas. Vea la guía de"
-" nuevos desarrolladores para mas detalles."
-
-#: i2p2www/pages/site/get-involved/index.html:61
-msgid "Translation"
-msgstr "Traducciones"
-
-#: i2p2www/pages/site/get-involved/index.html:62
-#, python-format
-msgid ""
-"Help translate the website and the software into your language.\n"
-"See the new translator's guide for details."
-msgstr ""
-"Ayude a traducir la página web y las aplicaciones a su lenguaje. Vea la "
-"guía de nuevos traductores para más "
-"información."
-
-#: i2p2www/pages/site/get-involved/index.html:66
-msgid "Analysis"
-msgstr "Análisis"
-
-#: i2p2www/pages/site/get-involved/index.html:67
-#, python-format
-msgid ""
-"Study or test the code to look for vulnerabilities.\n"
-"Both anonymity vulnerabilities from the various\n"
-"threat models,\n"
-"and DOS and other weaknesses due to securities holes,\n"
-"need researching."
-msgstr ""
-"Estudie o pruebe el código buscando vulnerabilidades. Se necesita "
-"estudiar tanto las vulnerabilidades del anonimato de varios modelos de amenazas, como los ataques DOS y "
-"otras debilidades debidas a errores en la seguridad."
-
-#: i2p2www/pages/site/get-involved/roadmap.html:7
-msgid ""
-"Include some seed data in the distribution so a central reseed location "
-"isn't required?"
-msgstr ""
-"¿Asegurarnos de que I2P en la instalación automáticamente se una a la red"
-" y así no haría falta ninguna localización central para esto?"
-
-#: i2p2www/pages/site/get-involved/roadmap.html:10
-#, python-format
-msgid ""
-"Reachability Mapping / handle peers partially reachable / enhanced restricted routes"
-msgstr ""
-"Mapeado de accesibilidad / manejar los pares parcialmente accesibles / "
-"mejorar los ruters "
-"restringidos"
-
-#: i2p2www/pages/site/get-involved/roadmap.html:13
-msgid "Improve help pages and website"
-msgstr "Mejorar las páginas de ayuda y la página web."
-
-#: i2p2www/pages/site/get-involved/roadmap.html:14
-msgid "More translations"
-msgstr "Más traducciones"
-
-#: i2p2www/pages/site/get-involved/roadmap.html:15
-msgid "SSU disconnect message"
-msgstr "Mensaje de desconexión SSU"
-
-#: i2p2www/pages/site/get-involved/roadmap.html:16
-msgid "Iterative floodfill lookups"
-msgstr "Búsquedas iterativas en el algoritmo de relleno, \"floodfill\""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:21
-msgid "Full review of anonymity issues and other vulnerabilities"
-msgstr "Examen completo de las vulnerabilidades y problemas de anonimato."
-
-#: i2p2www/pages/site/get-involved/roadmap.html:22
-msgid ""
-"Reduce memory usage, remove debugging overhead, make it run better on "
-"slow and embedded machines"
-msgstr ""
-"Reducción del uso de memoria, eliminar el gasto superfluo de la "
-"depuración, hacer que corra más ligero en hardware pequeño y lento. "
-
-#: i2p2www/pages/site/get-involved/roadmap.html:25
-msgid "Docs"
-msgstr "Documentación"
-
-#: i2p2www/pages/site/get-involved/roadmap.html:30
-msgid "Full restricted routes"
-msgstr "Rutas restringidas"
-
-#: i2p2www/pages/site/get-involved/roadmap.html:35
-msgid "Tunnel mixing and padding"
-msgstr "Mezclado y relleno de los túneles"
-
-#: i2p2www/pages/site/get-involved/roadmap.html:36
-msgid "User defined message delays"
-msgstr "Mensajes con el retraso definido por los usuarios"
-
-#: i2p2www/pages/site/get-involved/roadmap.html:39
-#, python-format
-msgid ""
-"Please see the TODO list for more detailed info "
-"about some of these tasks."
-msgstr ""
-"Por favor, vea la lista TODO , por hacer, para "
-"obtener información mas detallada sobre estas tareas."
-
-#: i2p2www/pages/site/get-involved/todo.html:4
-msgid "I2P Project Targets"
-msgstr "Objetivos del proyecto I2P"
-
-#: i2p2www/pages/site/get-involved/todo.html:5
-#, python-format
-msgid ""
-"Below is a more detailed (yet still incomplete) discussion of the major "
-"areas\n"
-"of future development on the core I2P network, spanning the plausibly "
-"planned\n"
-"releases. This does not include stego transports, porting to wireless "
-"devices,\n"
-"or tools to secure the local machine, nor does it include client "
-"applications\n"
-"that will be essential in I2P's success. There are probably other things "
-"that\n"
-"will come up, especially as I2P gets more peer review, but these are the "
-"main\n"
-"'big things'. See also the roadmap. Want to "
-"help?\n"
-"Get involved!"
-msgstr ""
-"Más abajo hay una discusión detallada (aunque aún no completa) de las "
-"áreas más importantes del futuro desarrollo del núcleo de I2P, que abarca"
-" los posibles planes de desarrollo. Esto no incluye transporte oculto, "
-"portarlo a dispositivos Wireless o herramientas para asegurar la máquina "
-"local, tampoco incluye otras aplicaciones cliente que serían esenciales "
-"para el éxito de I2P. Probablemente aparecerán otros temas, especialmente"
-" si I2P recibe mas atención, pero estas son ls 'cosas importantes'. Vea "
-"también la hoja de ruta. ¿Quiere ayudar? ¡Únete!"
-
-#: i2p2www/pages/site/get-involved/todo.html:16
-#: i2p2www/pages/site/get-involved/todo.html:54
-msgid "Core functionality"
-msgstr "Funcionamiento del núcleo."
-
-#: i2p2www/pages/site/get-involved/todo.html:18
-#: i2p2www/pages/site/get-involved/todo.html:57
-msgid "NAT/Firewall bridging via 1-hop restricted routes"
-msgstr "Bridging de NAT/cortafuegos a través de ruters restringidos de 1 salto"
-
-#: i2p2www/pages/site/get-involved/todo.html:21
-#: i2p2www/pages/site/get-involved/todo.html:130
-msgid "High degree transport layer with UDP, NBIO, or NIO"
-msgstr "Capa de transporte de alto nivel con UDP, NBIO, o NIO"
-
-#: i2p2www/pages/site/get-involved/todo.html:24
-#: i2p2www/pages/site/get-involved/todo.html:218
-msgid "NetworkDB and profile tuning and ejection policy for large nets"
-msgstr ""
-"Base de datos de la red, NetworkDB, y ajustes del perfil y política de "
-"expulsión para grandes redes. "
-
-#: i2p2www/pages/site/get-involved/todo.html:28
-#: i2p2www/pages/site/get-involved/todo.html:242
-msgid "Security / anonymity"
-msgstr "Seguridad / anonimato"
-
-#: i2p2www/pages/site/get-involved/todo.html:30
-#: i2p2www/pages/site/get-involved/todo.html:245
-msgid ""
-"Per-hop tunnel id & new permuted TunnelVerificationStructure "
-"encryption"
-msgstr ""
-"Id por salto de túnel & nuevo cifrado permutado de la estructura de "
-"verificación del túnel, TunnelVerificationStructure"
-
-#: i2p2www/pages/site/get-involved/todo.html:33
-#: i2p2www/pages/site/get-involved/todo.html:295
-msgid "Strict ordering of participants within tunnels"
-msgstr "Orden estricto de los participantes dentro de los túneles"
-
-#: i2p2www/pages/site/get-involved/todo.html:36
-msgid "Randomly permuted tunnel lengths"
-msgstr "Tamaño de los túneles aleatorio."
-
-#: i2p2www/pages/site/get-involved/todo.html:39
-#: i2p2www/pages/site/get-involved/todo.html:357
-msgid "Full blown n-hop restricted routes with optional trusted links"
-msgstr ""
-"Mejor personalización de los ruters y un mejor control de los ruters "
-"usados."
-
-#: i2p2www/pages/site/get-involved/todo.html:42
-#: i2p2www/pages/site/get-involved/todo.html:376
-msgid "Hashcash for routerIdentity, destination, and tunnel request"
-msgstr ""
-"Añadir Hashcash a la identidad del ruter, destinación y solicitud de "
-"respuesta."
-
-#: i2p2www/pages/site/get-involved/todo.html:45
-#: i2p2www/pages/site/get-involved/todo.html:405
-msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
-msgstr ""
-"Control avanzado del funcionamiento del ruter (procesamiento por "
-"lotes/mezclado/control de velocidad)"
-
-#: i2p2www/pages/site/get-involved/todo.html:48
-#: i2p2www/pages/site/get-involved/todo.html:442
-msgid "Stop & go mix w/ garlics & tunnels"
-msgstr ""
-"Configuración avanzada del enrutamiento de los túneles y opciones para "
-"crear túneles de usar y tirar para su uso a corto plazo."
-
-#: i2p2www/pages/site/get-involved/todo.html:62
-msgid "Implemented in I2P 0.6.0.6"
-msgstr "Implementado en I2P 0.6.0.6"
-
-#: i2p2www/pages/site/get-involved/todo.html:63
-msgid ""
-"The functionality of allowing routers to fully participate within the "
-"network \n"
-"while behind firewalls and NATs that they do not control requires some "
-"basic \n"
-"restricted route operation (since those peers will not be able to receive"
-" \n"
-"inbound connections). To do this successfully, you consider peers one of"
-" \n"
-"two ways:"
-msgstr ""
-"Esta capacidad permite a los ruters participar totalmente dentro de la "
-"red incluso detrás de un NAT o cortafuegos de los que no se tienen "
-"control  (ya que estos pares no podrán recibir conexiones entrantes). "
-"Para hacer esto satisfactoriamente, consideramos a los pares de estas dos"
-" formas:"
-
-#: i2p2www/pages/site/get-involved/todo.html:73
-msgid ""
-"Peers who have reachable interfaces - these peers do not need to \n"
-"do anything special"
-msgstr ""
-"Pares que tienen algún dispositivo accesible estos pares no "
-"necesitan hacer nada especial"
-
-#: i2p2www/pages/site/get-involved/todo.html:77
-msgid ""
-"Peers who do not have reachable interfaces - these peers must "
-"build \n"
-"a tunnel pointing at them where the gateway is one of the peers they have"
-" \n"
-"established a connection with who has both a publicly reachable interface"
-" \n"
-"and who has agreed to serve as their 'introducer'."
-msgstr ""
-"Pares que no tienen dispositivos accesibles - estos pares tienen "
-"que construir un túnel hacia ellos mismos en donde la salida es uno de "
-"los pares con los que ya ha establecido una conexión y quien tiene un "
-"dispositivo accesible públicamente y ha aceptado servir como su "
-"'introductor'."
-
-#: i2p2www/pages/site/get-involved/todo.html:85
-msgid ""
-"To do this, peers who have no IP address simply connect to a few peers, \n"
-"build a tunnel through them, and publish a reference to those tunnels "
-"within \n"
-"their RouterInfo structure in the network database."
-msgstr ""
-"Para hacer esto, los pares que no tiene dirección IP simplemente se "
-"conectan a varios pares, construye un túnel a través de ellos, y publican"
-" una referencia de esos túneles dentro de la estructura RouterInfo en la "
-"base de datos dela red."
-
-#: i2p2www/pages/site/get-involved/todo.html:90
-msgid ""
-"When someone wants to contact any particular router, they first must get"
-" \n"
-"its RouterInfo from the network database, which will tell them whether "
-"they \n"
-"can connect directly (e.g. the peer has a publicly reachable interface) \n"
-"or whether they need to contact them indirectly. Direct connections occur"
-" \n"
-"as normal, while indirect connections are done through one of the "
-"published \n"
-"tunnels."
-msgstr ""
-"Cuando alguien quiere conectar con algún ruter en particular, el primero "
-"debe obtener su RouterInfo de la base de datos de la red, la que le "
-"indicará que puede conectarse directamente ( por ejemplo con un par que "
-"tiene un dispositivo accesible públicamente) o  que necesita conectar "
-"indirectamente. La conexiones directas se hacen directamente, pero las "
-"indirectas se hacen a través de los túneles publicados. "
-
-#: i2p2www/pages/site/get-involved/todo.html:98
-msgid ""
-"When a router just wants to get a message or two to a specific hidden "
-"peer, \n"
-"they can just use the indirect tunnel for sending the payload. However, \n"
-"if the router wants to talk to the hidden peer often (for instance, as "
-"part \n"
-"of a tunnel), they will send a garlic routed message through the indirect"
-" \n"
-"tunnel to that hidden peer which unwraps to contain a message which "
-"should \n"
-"be sent to the originating router. That hidden peer then establishes an \n"
-"outbound connection to the originating router and from then on, those two"
-" \n"
-"routers can talk to each other directly over that newly established "
-"direct \n"
-"connection."
-msgstr ""
-"Cuando un ruter simplemente quiere enviar un mensaje a un par oculto "
-"puede usar el túnel indirecto para enviar la información. Sin embargo, si"
-" el ruter quiere hablar con el par oculto a menudo (por ejemplo, como "
-"parte de un túnel), enviará un mensaje enrutado a través del túnel "
-"indirecto del par oculto. Entonces este par oculto establece una conexión"
-" de salida hacia el ruter original y a partir de entonces estos dos "
-"ruters puede hablar entre ellos directamente sobre la nueva conexión "
-"directa. "
-
-#: i2p2www/pages/site/get-involved/todo.html:109
-msgid ""
-"Of course, that only works if the originating peer can receive "
-"connections \n"
-"(they aren't also hidden). However, if the originating peer is hidden, "
-"they \n"
-"can simply direct the garlic routed message to come back to the "
-"originating \n"
-"peer's inbound tunnel."
-msgstr ""
-"Por supuesto esto solo funciona si el par original puede recibir "
-"conexiones (y no están también ocultas). Sin embargo, si el par original "
-"está oculto, pueden simplemente indicar la mensaje enrutado que vuelva "
-"por el túnel de entrada del par original. "
-
-#: i2p2www/pages/site/get-involved/todo.html:115
-msgid ""
-"This is not meant to provide a way for a peer's IP address to be "
-"concealed, \n"
-"merely as a way to let people behind firewalls and NATs fully operate "
-"within \n"
-"the network. Concealing the peer's IP address adds a little more work, as"
-" \n"
-"described below."
-msgstr ""
-"Esto no se ha creado para permitir que la IP de un par permanezca oculta,"
-" simplemente es una forma de permitir a la gente detrás de un NAT o "
-"cortafuegos funcionar completamente dentro de la red. Ocultar la IP de un"
-" par cuesta un poco más de trabajo, como se describe más abajo."
-
-#: i2p2www/pages/site/get-involved/todo.html:121
-msgid ""
-"With this technique, any router can participate as any part of a tunnel."
-" \n"
-"For efficiency purposes, a hidden peer would be a bad choice for an "
-"inbound \n"
-"gateway, and within any given tunnel, two neighboring peers wouldn't want"
-" \n"
-"to be hidden. But that is not technically necessary."
-msgstr ""
-"Con esta técnica cualquier ruter puede participar como una parte de un "
-"túnel. Con objeto de mejorar la eficiencia, un par oculto sería una mala "
-"elección como puerta de entrada, y dentro de un túnel dado, dos pares "
-"vecinos no desearían estar ocultos. Pero esto no es técnicamente "
-"necesario."
-
-#: i2p2www/pages/site/get-involved/todo.html:133
-msgid "Both UDP and NIO have been Implemented in I2P"
-msgstr "Ambos, UDP y NIO ya han sido implementados en I2P"
-
-#: i2p2www/pages/site/get-involved/todo.html:134
-msgid ""
-"Standard TCP communication in Java generally requires blocking socket \n"
-"calls, and to keep a blocked socket from hanging the entire system, those"
-" \n"
-"blocking calls are done on their own threads. Our current TCP transport \n"
-"is implemented in a naive fashion - for each peer we are talking to, we \n"
-"have one thread reading and one thread writing. The reader thread simply"
-" \n"
-"loops a bunch of read() calls, building I2NP messages and adding them \n"
-"to our internal inbound message queue, and the writer thread pulls "
-"messages \n"
-"off a per-connection outbound message queue and shoves the data through \n"
-"write() calls."
-msgstr ""
-"Las comunicaciones estándar TCP en java normalmente necesitan el bloqueo "
-"de llamadas al socket, y para evitar que el socket bloqueado pare todo el"
-" sistema, estos bloqueos se hacen en sus propios hilos. Nuestro sistema "
-"de transporte TCP actual está implementado de una forma sencilla - por "
-"cada par con el que hablamos, tenemos un hilo escribiendo y otro leyendo."
-" El hilo de lectura simplemente repite un puñado de llamadas read(), "
-"creando mensajes I2NP y añadiéndolos a la cola interna de mensajes de "
-"entrada, y el hilo de escritura envía mensajes hacia una cola de mensajes"
-" de salida y empuja los datos a través de llamadas write()."
-
-#: i2p2www/pages/site/get-involved/todo.html:145
-msgid ""
-"We do this fairly efficiently, from a CPU perspective - at any time, \n"
-"almost all of these threads are sitting idle, blocked waiting for "
-"something \n"
-"to do. However, each thread consumes real resources (on older Linux "
-"kernels, \n"
-"for instance, each thread would often be implemented as a fork()'ed "
-"process). \n"
-"As the network grows, the number of peers each router will want to talk \n"
-"with will increase (remember, I2P is fully connected, meaning that any \n"
-"given peer should know how to get a message to any other peer, and "
-"restricted \n"
-"route support will probably not significantly reduce the number of "
-"connections \n"
-"necessary). This means that with a 100,000 router network, each router \n"
-"will have up to 199,998 threads just to deal with the TCP connections!"
-msgstr ""
-"Desde la perspectiva del uso de CPU esto se hace bastante eficientemente "
-"- la mayoría del tiempo la mayoría de estos hilos están dormidos "
-"esperando por algo que hacer. Sin embargo, cada uno de estos hilos "
-"consume recursos (en kernels viejos de Linux, por ejemplo, cada hilo se "
-"implementa como un proceso fork()'ed). Al mismo tiempo que la red crece, "
-"el número de pares con el que se comunica un ruter aumentará (recuerde, "
-"I2P está totalmente conectado, esto quiere decir que cualquier par debe "
-"saber como enviar un mensaje a cualquier otro par). ¡Esto significa que "
-"con una red de 100.000 ruters, cada ruter tendrá 199.998 hilos "
-"simplemente para tratar con las conexiones TCP!"
-
-#: i2p2www/pages/site/get-involved/todo.html:157
-msgid ""
-"Obviously, that just won't work. We need to use a transport layer that \n"
-"can scale. In Java, we have two main camps:"
-msgstr ""
-"Obviamente esto no funcionará. Necesitamos una capa de transporte que "
-"pueda escalar. En Java tenemos dos posibles soluciones:"
-
-#: i2p2www/pages/site/get-involved/todo.html:162
-#, python-format
-msgid ""
-"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere"
-msgstr ""
-"Implementado en 2P 0.6 (\"SSU\") y documentado en en "
-"otra parte"
-
-#: i2p2www/pages/site/get-involved/todo.html:165
-msgid ""
-"Sending and receiving UDP datagrams is a connectionless operation - if \n"
-"we are communicating with 100,000 peers, we simply stick the UDP packets"
-" \n"
-"in a queue and have a single thread pulling them off the queue and "
-"shoving \n"
-"them out the pipe (and to receive, have a single thread pulling in any \n"
-"UDP packets received and adding them to an inbound queue)."
-msgstr ""
-"Enviar y recibir datagramas UDP es una operación que no necesita de "
-"conexión previa - si estamos comunicándonos con 1000.000 pares, "
-"simplemente ponemos los paquetes UDP en una cola y hacemos que un único "
-"hilo los envíe fuera de la cola hacia una tubería ( y para recibir, "
-"tenemos un único hilo tirando de cualquier paquete UDP recibido y "
-"añadiéndolos a una cola de entrada)"
-
-#: i2p2www/pages/site/get-involved/todo.html:172
-msgid ""
-"However, moving to UDP means losing the benefits of TCP's ordering, "
-"congestion \n"
-"control, MTU discovery, etc. Implementing that code will take significant"
-" \n"
-"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n"
-"a while ago I was taking some measurements in the simulator and on the \n"
-"live net, and the vast majority of messages transferred would fit easily"
-" \n"
-"within a single unfragmented UDP packet, and the largest of the messages"
-" \n"
-"would fit within 20-30 packets. As mule pointed out, TCP adds a "
-"significant \n"
-"overhead when dealing with so many small packets, as the ACKs are within"
-" \n"
-"an order of magnitude in size. With UDP, we can optimize the transport \n"
-"for both efficiency and resilience by taking into account I2P's "
-"particular \n"
-"needs."
-msgstr ""
-"Sin embargo, usar UDP significa perder los beneficios de usar el orden de"
-" TCP, el control de congestión, descubrimiento de MTU, etc. Implementar "
-"esto significaría mucho trabajo, sin embargo I2P no necesita ser tan "
-"fuerte como TCP. Hace algún tiempo estaba tomando medida en un simulador "
-"y en la red real, y la mayoría de los mensajes pueden ser transmitidas "
-"dentro de un único paquete UDP no fragmentado, y el más largo de los "
-"mensajes entraría dentro de 20-30 paquetes. Como mule indicó, TCP añade "
-"bastante gasto cuando tiene que encargarse de muchos paquetes pequeños. "
-"Con UDP, se puede optimizar el transporte para la eficiencia y la "
-"flexibilidad teniendo en cuenta las necesidades particulares de I2P."
-
-#: i2p2www/pages/site/get-involved/todo.html:185
-msgid "It will be a lot of work though."
-msgstr "Sería muchísimo trabajo por hacer."
-
-#: i2p2www/pages/site/get-involved/todo.html:188
-msgid "NIO or NBIO"
-msgstr "NIO o NBIO"
-
-#: i2p2www/pages/site/get-involved/todo.html:189
-msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")"
-msgstr "NIO fue implementada en la versión 0.6.1.22 de I2P (\"NTCP\")"
-
-#: i2p2www/pages/site/get-involved/todo.html:192
-msgid ""
-"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java"
-" \n"
-"developers to take advantage of the operating system's nonblocking IO \n"
-"capabilities - allowing you to maintain a large number of concurrent IO \n"
-"operations without requiring a separate thread for each. There is much \n"
-"promise with this approach, as we can scalable handle a large number of \n"
-"concurrent connections and we don't have to write a mini-TCP stack with \n"
-"UDP. However, the NIO packages have not proven themselves to be battle-"
-"ready, \n"
-"as the Freenet developer's found. In addition, requiring NIO support "
-"would \n"
-"mean we can't run on any of the open source JVMs like Kaffe, \n"
-"as GNU/Classpath has only "
-"limited \n"
-"support for NIO. (note: this may not be the case anymore, as there \n"
-"has been some progress on Classpath's NIO, but it is an unknown "
-"quantity)"
-msgstr ""
-"En Java 1.4 se introdujo paquetes \"I/O nuevos\", permitiendo a los "
-"desarrolladores de java usar las capacidades de los sistemas operativos "
-"sin bloquear las entradas y salidas - permitiendo tener un gran número de"
-" operaciones I/O concurrentes si necesitar un nuevo hilo para cada una. "
-"Hay muchas esperanzas puestas en este método, ya que podemos manejar un "
-"gran número de conexiones y no tendríamos que que reescribir un nuevo "
-"mini TCP stack con UDP. Sin embargo, los paquetes NIO no han probado aún "
-"estar listos, como averiguaron los desarrolladores de Freenet. Además, "
-"usar paquetes NIO significaría no poder usar ninguna JVM libre como Kaffe, ya que GNU/Classpath sólo tiene soporte "
-"limitado para NIO.(nota: puede que ahora esto ya no sea verdad, ya que"
-" se han hecho progreso en los NIO de Classpath, pero no sabemos su "
-"calidad)"
-
-#: i2p2www/pages/site/get-involved/todo.html:206
-#, python-format
-msgid ""
-"Another alternative along the same lines is the Non"
-" \n"
-"Blocking I/O package - essentially a cleanroom NIO implementation \n"
-"(written before NIO was around). It works by using some native OS code \n"
-"to do the nonblocking IO, passing off events through Java. It seems to \n"
-"be working with Kaffe, though there doesn't seem to be much development \n"
-"activity on it lately (likely due to 1.4's NIO deployment)."
-msgstr ""
-"Otra alternativa del mismo tipo es el paquete sin "
-"bloqueos I/O - básicamente es una implementación NIO tipo cleanroom "
-"(escrita antes de que NIO existiese). Funciona utilizando algo de código "
-"nativo del sistema operativo para hacer I/O sin bloqueos, pasando los "
-"eventos a través de Java. Parece que funciona con Kaffe, aunque no parece"
-" que haya mucha actividad últimamante en su desarrollo (debido "
-"probablemente al desarrollo de NIO 1.4) "
-
-#: i2p2www/pages/site/get-involved/todo.html:221
-msgid ""
-"Within the current network database and profile management "
-"implementation, \n"
-"we have taken the liberty of some practical shortcuts. For instance, we \n"
-"don't have the code to drop peer references from the K-buckets, as we \n"
-"don't have enough peers to even plausibly fill any of them, so instead, \n"
-"we just keep the peers in whatever bucket is appropriate. Another example"
-" \n"
-"deals with the peer profiles - the memory required to maintain each "
-"peer's \n"
-"profile is small enough that we can keep thousands of full blown profiles"
-" \n"
-"in memory without problems. While we have the capacity to use trimmed \n"
-"down profiles (which we can maintain 100s of thousands in memory), we \n"
-"don't have any code to deal with moving a profile from a \"minimal "
-"profile\" \n"
-"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to"
-" simply \n"
-"eject a profile altogether. It just wouldn't be practical to write that \n"
-"code yet, since we aren't going to need it for a while."
-msgstr ""
-"Nos hemos tomado la libertad de usar unos atajos prácticos dentro de la "
-"base de datos de la red y la implementación de la gestión del perfil. Por"
-" ejemplo, no tenemos el código para sacar los perfiles de los pares de "
-"K-buckets, al igual que no tenemos suficientes pares para llenar ninguno "
-"de ellos, en lugar de eso mantenemos los pares en cualquier cubo que "
-"pueda ser apropiado. Otro ejemplo tiene que ver con los perfiles de los "
-"pares - la memoria requerida para mantener cada perfil del par es "
-"suficientemente pequeña como para poder tener todos los perfiles en la "
-"memoria sin problemas (con lo que podemos mantener cientos de miles en la"
-" memoria), no tenemos ningún código para lidiar con el problema de mover "
-"un perfil de un \"perfil mínimo\" a un \"perfil completo\", de un "
-"\"perfil completo\" a un \"perfil mínimo\", o simplemente desechar un "
-"perfil completo. Simplemente no sería práctico escribir el código ya que "
-"no lo vamos a necesitar por un tiempo."
-
-#: i2p2www/pages/site/get-involved/todo.html:236
-msgid ""
-"That said, as the network grows we are going to want to keep these "
-"considerations \n"
-"in mind. We will have some work to do, but we can put it off for later."
-msgstr ""
-"Como ya hemos dicho, según siga creciendo la red volveremos a retomar "
-"estas consideraciones. Tendremos algún trabajo por hacer, pero se puede "
-"dejar para mas tarde."
-
-#: i2p2www/pages/site/get-involved/todo.html:248
-#: i2p2www/pages/site/get-involved/todo.html:332
-#, python-format
-msgid ""
-"Addressed in I2P 0.5 as documented elsewhere"
-msgstr ""
-"Conseguido en I2P 0.5 como se documenta aquí"
-
-#: i2p2www/pages/site/get-involved/todo.html:251
-msgid ""
-"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n"
-"going to Dave, then to Charlie, then Bob, and finally Alice "
-"(A<--B<--C<--D<--E), \n"
-"all five of them will know they are participating in tunnel \"123\", as \n"
-"the messages are tagged as such. What we want to do is give each hop "
-"their \n"
-"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n"
-"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n"
-"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n"
-"the tunnel had the same tunnel ID, collusion attacks aren't much work."
-msgstr ""
-"Ahora mismo si Alicia crea un túnel de entrada de cuatro saltos empezando"
-" en Elvis, yendo a través de Dave, después Charlie, después Bob y "
-"finalmente Alice (A<--B<--C<--D<--E), los cinco sabrán que "
-"están participando en el túnel \"123\", ya que el mensaje está etiquetado"
-" así. Lo que queremos hacer es dar a cada salto su propio ID de túnel - "
-"Charlie recibirá el mensaje en el túnel 234 y lo enviará al túnel 876 de "
-"Bob. Se intenta prevenir que Bob o Charlie sepan que están en el túnel de"
-" Alice, lo que ocurriría si en cada salto tuviesen el mismo ID de túnel "
-"haciendo que un ataque por colisión fuese más fácil."
-
-#: i2p2www/pages/site/get-involved/todo.html:261
-msgid ""
-"Adding a unique tunnel ID per hop isn't hard, but by itself, "
-"insufficient. \n"
-"If Dave and Bob are under the control of the same attacker, they wouldn't"
-" \n"
-"be able to tell they are in the same tunnel due to the tunnel ID, but \n"
-"would be able to tell by the message bodies and verification structures \n"
-"by simply comparing them. To prevent that, the tunnel must use layered \n"
-"encryption along the path, both on the payload of the tunneled message \n"
-"and on the verification structure (used to prevent simple tagging "
-"attacks). \n"
-"This requires some simple modifications to the TunnelMessage, as well \n"
-"as the inclusion of per-hop secret keys delivered during tunnel creation"
-" \n"
-"and given to the tunnel's gateway. We must fix a maximum tunnel length \n"
-"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n"
-"of the 16 delivered secret keys, in reverse order, and to encrypt the \n"
-"signature of the hash of the (encrypted) payload at each step. The "
-"gateway \n"
-"then sends that 16-step encrypted message, along with a 16-step and "
-"16-wide \n"
-"encrypted mapping to the first hop, which then decrypts the mapping and \n"
-"the payload with their secret key, looking in the 16-wide mapping for \n"
-"the entry associated with their own hop (keyed by the per-hop tunnel ID)"
-" \n"
-"and verifying the payload by checking it against the associated signed \n"
-"hash."
-msgstr ""
-"Añadir un Id único por cada salto no es difícil, pero sí insuficiente. Si"
-" Dave y Bob están bajo el control del mismo atacante no sería posible "
-"saber que están en el mismo túnel a causa del Id, pero podría se capaz de"
-" saber sobre el cuerpo del mensaje y las estructuras de verificación con "
-"solo compararlos. Para prevenir esto el túnel debe usar una capa de "
-"cifrado a lo largo del camino, en el payload tunelado y en la "
-"verificación de la estructura (usado para evitar ataques simples de "
-"etiquetado). Esto requiere algunos cambios simples en el TunnelMessage, y"
-" además, requiere del envío de claves secretas por cada salto durante la "
-"creación del túnel, y además hacer llegar estas claves a la salida del "
-"túnel. Tenemos que que crear un valor máximo del tamaño del túnel (por "
-"ejemplo 16), e instruir a la puerta de salida para que cifre el mensaje "
-"de cada una de las claves secretas enviadas, en orden inverso, y de que "
-"cifre la firma del hash del payload (cifrado) en cada salto. La puerta de"
-" salida envía entonces el mensaje cifrado de 16 pasos, junto con los 16 "
-"pasos y el mapeado cifrado de 16 de ancho al primer salto, el cual "
-"entonces  descifra el mapeado y el payload con su clave secreta, buscando"
-" en el mapeado de 16 de ancho por la entrada asociada con su propio salto"
-" (cifrado por el Id del túnel de cada salto) y verificando el pyload "
-"chequeándolo con el hash firmado asociado."
-
-#: i2p2www/pages/site/get-involved/todo.html:282
-msgid ""
-"The tunnel gateway does still have more information than the other peers"
-" \n"
-"in the tunnel, and compromising both the gateway and a tunnel participant"
-" \n"
-"would allow those peers to collude, exposing the fact that they are both"
-" \n"
-"in the same tunnel. In addition, neighboring peers know that they are \n"
-"in the same tunnel anyway, as they know who they send the message to (and"
-" \n"
-"with IP-based transports without restricted routes, they know who they \n"
-"got it from). However, the above two techniques significantly increase \n"
-"the cost of gaining meaningful samples when dealing with longer tunnels."
-msgstr ""
-"La salida del túnel todavía tiene más información que los otros pares del"
-" túnel, y comprometiendo la salida y un participante en el túnel "
-"permitiría a estos confabularse mostrando el hecho de que los dos "
-"pertenecen al mismo túnel. Además, los pares vecinos saben que están en "
-"el mismo túnel, ya que saben a quien envían el mensaje (y con transportes"
-" basados en IP con rutas restrictivas saben de donde lo reciben). Sin "
-"embargo, estas dos técnicas incrementan significativamente el coste de "
-"conseguir ejemplos con significado cuando se trata de túneles largos."
-
-#: i2p2www/pages/site/get-involved/todo.html:298
-msgid "Implemented in release 0.6.2"
-msgstr "Implementado en la versión 0.6.2"
-
-#: i2p2www/pages/site/get-involved/todo.html:301
-#, python-format
-msgid ""
-"As Connelly proposed to deal with the\n"
-"predecessor attack (2008\n"
-"update), keeping the order of peers within our tunnels consistent \n"
-"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n"
-"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n"
-"get to substantially sample Alice's peer selection group. We may even \n"
-"want to explicitly allow Bob to participate in Alice's tunnels in only \n"
-"one way - receiving a message from Dave and sending it to Charlie - and \n"
-"if any of those peers are not available to participate in the tunnel (due"
-" \n"
-"to overload, network disconnection, etc), avoid asking Bob to participate"
-" \n"
-"in any tunnels until they are back online."
-msgstr ""
-"Como propuso Connelly para tratar el ataque del predecesor(2008), manteniendo consistente el orden de los "
-"pares dentro de nuestros túneles (osea cuando Alice crea un túnel con Bob"
-" y Charlei en él, el siguiente salto de Bob es siempre Charlie), "
-"solucionamos el problema, ya que Bob no puede obtener una muestra del "
-"grupo de pares de Alice lo suficientemente grande. Incluso podríamos "
-"querer permitir explícitamente a Bob participar en el túnel de Alice en "
-"una dirección - recibiendo un mensaje de Dave y enviándolo a Charlie - y "
-"si unos de estos pares no están disponible para participar en el túnel "
-"(debido a saturación, desconexión de red, erc), evitar preguntar a Bob si"
-" participa en algún túnel hasta que vuelva a estar disponible."
-
-#: i2p2www/pages/site/get-involved/todo.html:316
-msgid ""
-"More analysis is necessary for revising the tunnel creation - at the \n"
-"moment, we simply select and order randomly within the peer's top tier \n"
-"of peers (ones with fast + high capacity)."
-msgstr ""
-"Aún hace falta un análisis más detallado de la creación del túnel - hasta"
-" el momento, simplemente seleccionamos y ordenamos aleatoriamente de "
-"entre uno de los mejores pares del par (uno rápido y con gran capacidad)"
-
-#: i2p2www/pages/site/get-involved/todo.html:321
-msgid ""
-"Adding a strict ordering to peers in a tunnel also improves the anonymity"
-" \n"
-"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway"
-" \n"
-"is always the same would be particularly damning. However, peers with \n"
-"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n"
-"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n"
-"duration) minutes, use a 1-hop tunnel)."
-msgstr ""
-"Añadiendo un orden estricto a los pares de un túnel también mejoramos el "
-"anonimato de los pares con túneles de 0 saltos, ya que de otra forma el "
-"hecho de que la salida del par fuese siempre la misma sería bastante "
-"dañino. Sin embargo, los pares con túneles de 0 saltos necesitarán usar "
-"periódicamente un túnel de 1 salto para simular el fallo de un par de "
-"salida normal (así cada MTBF*(duración del túnel) minutos, usaría un "
-"túnel de 1 salto)"
-
-#: i2p2www/pages/site/get-involved/todo.html:338
-msgid ""
-"Without tunnel length permutation, if someone were to somehow detect that"
-" \n"
-"a destination had a particular number of hops, it might be able to use "
-"that \n"
-"information to identify the router the destination is located on, per the"
-" \n"
-"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n"
-"receives a tunnel message from Charlie and forwards it to Alice, Bob "
-"knows \n"
-"Alice is the final router in the tunnel. If Bob were to identify what "
-"destination \n"
-"that tunnel served (by means of colluding with the gateway and harvesting"
-" \n"
-"the network database for all of the LeaseSets), he would know the router"
-" \n"
-"on which that destination is located (and without restricted routes, that"
-" \n"
-"would mean what IP address the destination is on)."
-msgstr ""
-"Sin los cambios de tamaño de los túneles, si alguien de alguna forma "
-"detectase que una destinación tiene un número determinado de saltos, "
-"sería capaz de usar esa información para identificar la localización de "
-"la destinación de ruter usando el ataque del predecesor.  Por ejemplo, si"
-" todo el mundo tiene túneles de 2 saltos, si Bob recibe un mensaje de "
-"Charlie y lo envía a Alice, Bob sabría que que Alice es el ruter final "
-"del túnel. Si Bob quisiese  identificar la destinación que ese túnel "
-"sirvió (confabulándose con el nodo de salida y buscando en la base de "
-"datos de la red a todos los LeaseSets), conocería el ruter que está en "
-"esa destinación ( y sin rutas restringidas, eso quiere decir que "
-"sabríamos la IP de la destinación)"
-
-#: i2p2www/pages/site/get-involved/todo.html:350
-msgid ""
-"It is to counter user behavior that tunnel lengths should be permuted, \n"
-"using algorithms based on the length requested (for example, the 1/MTBF \n"
-"length change for 0-hop tunnels outlined above)."
-msgstr ""
-"El tamaño de los túneles debe ser cambiante para contrarrestar el "
-"comportamiento de los usuarios, usando algoritmos basados en el tamaño "
-"requerido (por ejemplo, el cambio de tamaño a 1/MTBF de los túneles de 0 "
-"saltos)"
-
-#: i2p2www/pages/site/get-involved/todo.html:360
-msgid ""
-"The restricted route functionality described before was simply a "
-"functional \n"
-"issue - how to let peers who would not otherwise be able to communicate \n"
-"do so. However, the concept of allowing restricted routes includes "
-"additional \n"
-"capabilities. For instance, if a router absolutely cannot risk "
-"communicating \n"
-"directly with any untrusted peers, they can set up trusted links through"
-" \n"
-"those peers, using them to both send and receive all of its messages. \n"
-"Those hidden peers who want to be completely isolated would also refuse \n"
-"to connect to peers who attempt to get them to (as demonstrated by the \n"
-"garlic routing technique outlined before) - they can simply take the "
-"garlic \n"
-"clove that has a request for delivery to a particular peer and tunnel \n"
-"route that message out one of the hidden peer's trusted links with "
-"instructions \n"
-"to forward it as requested."
-msgstr ""
-"La funcionalidad restringida del ruter descrita antes era simplemente un "
-"problema funcional - como hacer que dos pares que de otra forma no "
-"estrían comunicados se comuniquen. Sin embargo, el concepto de permitir "
-"ruters restringidos incluye capacidades adicionales. Por ejemplo, si un "
-"ruter no puede arriesgarse de ninguna forma a una comunicación directa "
-"con un par sin confianza, pueden configurar enlaces seguros a través de "
-"esos pares,  usándolos para enviar y recibir todos sus mensajes. Esos "
-"pares ocultos que desean estar totalmente aislados pueden también negarse"
-" a conectar con pares que intenten alcanzarles (como se demuestra en la "
-"técnica de ruteado 'garlic' esbozada anteriormente)"
-
-#: i2p2www/pages/site/get-involved/todo.html:379
-#, python-format
-msgid ""
-"Within the network, we will want some way to deter people from consuming"
-" \n"
-"too many resources or from creating so many peers to mount a Sybil \n"
-"attack. Traditional techniques such as having a peer see who is "
-"requesting \n"
-"a resource or running a peer aren't appropriate for use within I2P, as \n"
-"doing so would compromise the anonymity of the system. Instead, we want \n"
-"to make certain requests \"expensive\"."
-msgstr ""
-"Dentro de la red necesitaremos una forma de disuadir al a gente de "
-"consumir demasiados recursos o de crear demasiados pares como para montar"
-" un ataque Sybil. Las técnicas tradicionales "
-"como dejar que un par vea quien solicita un recurso o quien ejecuta "
-"cierto par, no son apropiadas para I2P, ya que eso comprometería el "
-"anonimato del sistema. En su lugar queremos hacer que ciertas peticiones "
-"sean muy \"caras\"."
-
-#: i2p2www/pages/site/get-involved/todo.html:387
-msgid ""
-"Hashcash is one technique that \n"
-"we can use to anonymously increase the \"cost\" of doing certain "
-"activities, \n"
-"such as creating a new router identity (done only once on installation),"
-" \n"
-"creating a new destination (done only once when creating a service), or \n"
-"requesting that a peer participate in a tunnel (done often, perhaps 2-300"
-" \n"
-"times per hour). We don't know the \"correct\" cost of each type of "
-"certificate \n"
-"yet, but with some research and experimentation, we could set a base "
-"level \n"
-"that is sufficiently expensive while not an excessive burden for people \n"
-"with few resources."
-msgstr ""
-"Hashcash es una técnica que "
-"podemos usar anónimamente para incrementar el \"costo\" de hacer ciertas "
-"acciones., como crear una nueva identidad de ruter (se hace sólo cuando "
-"se instala por primera vez), crear una nueva destinación (se hace sólo "
-"cuando se crea un nuevo servicio), o solicitar que un par participe en un"
-" túnel (se hace a menudo, quizás 2-300 veces a la hora). No conocemos "
-"todavía el coste \"correcto\" de cada tipo de certificado, pero con algo "
-"de investigación y estudio, podemos crear un nivel básico que sea lo "
-"suficientemente caro pero no tan caro como para que agobie a la gente con"
-" pocos recursos."
-
-#: i2p2www/pages/site/get-involved/todo.html:398
-msgid ""
-"There are a few other algorithms that we can explore for making those \n"
-"requests for resources \"nonfree\", and further research on that front is"
-" \n"
-"appropriate."
-msgstr ""
-"Hay varios algoritmos que podemos explorar para hacer que esas peticiones"
-" de recursos \"tengan un costo\", sería conveniente seguir investigando "
-"sobre este tema."
-
-#: i2p2www/pages/site/get-involved/todo.html:408
-#, python-format
-msgid ""
-"To powerful passive external observers as well as large colluding "
-"internal \n"
-"observers, standard tunnel routing is vulnerable to traffic analysis "
-"attacks \n"
-"- simply watching the size and frequency of messages being passed between"
-" \n"
-"routers. To defend against these, we will want to essentially turn some \n"
-"of the tunnels into its own mix cascade - delaying messages received at \n"
-"the gateway and passing them in batches, reordering them as necessary, \n"
-"and injecting dummy messages (indistinguishable from other \"real\" "
-"tunnel \n"
-"messages by peers in the path). There has been a significant amount of \n"
-"research \n"
-"on these algorithms that we can lean on prior to implementing the various"
-" \n"
-"tunnel mixing strategies."
-msgstr ""
-"El rutado estándar de túneles es vulnerable al análisis de tráfico para "
-"los observadores externos pasivos con muchos medios y para un gran número"
-" de observadores internos si están confabulados, simplemente observando "
-"el tamaño y la frecuencia de los mensajes que pasan a través de los "
-"ruters.  Para defendernos de esto, queremos simplemente convertir algunos"
-" túneles en su propia mezcla de cascada - retrasando los mensajes "
-"recibidos en la puerta de salida y pasándolos en lotes, reordenándolas "
-"como sea necesario, e inyectando mensajes de relleno (indistinguibles de "
-"los túneles \"reales\" para los pares). Ha habido un gran número de estudios sobre estos algoritmos que podríamos "
-"utilizar para implementar varias estrategias de mezclado de túneles."
-
-#: i2p2www/pages/site/get-involved/todo.html:421
-msgid ""
-"In addition to the anonymity aspects of more varied tunnel operation, \n"
-"there is a functional dimension as well. Each peer only has a certain \n"
-"amount of data they can route for the network, and to keep any particular"
-" \n"
-"tunnel from consuming an unreasonable portion of that bandwidth, they \n"
-"will want to include some throttles on the tunnel. For instance, a tunnel"
-" \n"
-"may be configured to throttle itself after passing 600 messages (1 per \n"
-"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n"
-"last minute). Excess messages may be delayed or summarily dropped. With \n"
-"this sort of throttling, peers can provide ATM-like QoS support for their"
-" \n"
-"tunnels, refusing to agree to allocate more bandwidth than the peer has \n"
-"available."
-msgstr ""
-"Además de los aspectos del anonimato en las operaciones de los túneles, "
-"hay una dimensión funcional extra.  Cada par sólo tiene cierto número de "
-"datos que pueden rutar por la red, y para evitar que un túnel en "
-"particular consuma una gran parte del ancho de banda, necesitarán añadir "
-"algunas regulaciones en el túnel. Por ejemplo, un túnel puede estar "
-"configurado para pararse a sí mismo después de pasar 600 mensajes (1 par "
-"por segundo), 2.4MB (4KBps), o tras haber excedido algún promedio "
-"variable (8KBps en el último minuto). Los mensajes sobrantes pueden ser "
-"retardados o desechados. Con este tipo de control, los pares pueden "
-"ofrecer un soporte parecido al QoS en sus túneles, negándose a asignar "
-"más ancho de banda de la que el par tiene disponible."
-
-#: i2p2www/pages/site/get-involved/todo.html:434
-msgid ""
-"In addition, we may want to implement code to dynamically reroute tunnels"
-" \n"
-"to avoid failed peers or to inject additional hops into the path. This \n"
-"can be done by garlic routing a message to any particular peer in a "
-"tunnel \n"
-"with instructions to redefine the next-hop in the tunnel."
-msgstr ""
-"Además, queremos implementar el código para re-rutar los túneles "
-"dinámicamente, y así evitar que los pares fallidos añadan saltos "
-"adicionales en el camino. Esto lo puede hacer la red garlic rutando un "
-"mensaje a un par en particular con las instrucciones para redefinir el "
-"siguiente salto del túnel."
-
-#: i2p2www/pages/site/get-involved/todo.html:445
-msgid ""
-"Beyond the per-tunnel batching and mixing strategy, there are further \n"
-"capabilities for protecting against powerful attackers, such as allowing"
-" \n"
-"each step in a garlic routed path to define a delay or window in which \n"
-"it should be forwarded on. This would enable protections against the long"
-" \n"
-"term intersection attack, as a peer could send a message that looks "
-"perfectly \n"
-"standard to most peers that pass it along, except at any peers where the"
-" \n"
-"clove exposed includes delay instructions."
-msgstr ""
-"Además de las estrategias de mezclado y de procesado por lotes de cada "
-"túnel, hay más  formas de protegernos contra atacantes poderosos, como "
-"permitir crear un retraso en cada paso dentro de un camino de rutado "
-"garlic. Esto crearía protecciones contra un ataque largo de intersección,"
-" ya que un par podría enviar mensajes que parecen normales a la mayoría "
-"de los pares, excepto a cualquier par donde se hayan dado instrucciones "
-"de retardo."
-
-#: i2p2www/pages/site/get-involved/todo.html:457
-#, python-format
-msgid ""
-"Performance related improvements are listed on the\n"
-"Performance page."
-msgstr ""
-"Las mejoras en el rendimiento se listan en la página de rendimiento ."
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2
-msgid "Bounty Arabic translation of webpage and router console"
-msgstr ""
-"Recompensa por la traducción al árabe de la página web y la consola de "
-"ruter."
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3
-#: i2p2www/pages/site/get-involved/bounties/index.html:119
-msgid "Arabic translation"
-msgstr "Traducción al árabe."
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2P echelon set out this bounty for translation\n"
-"of the I2P web page and I2P router console into Arabic."
-msgstr ""
-"Para mejorar el uso de I2P y atraer más gente, echelon propone esta "
-"recompensa por la traducción al árabe de la web de I2P y la consola del "
-"ruter."
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12
-msgid "This bounty is set into 2 subparts:"
-msgstr "Esta recompensa de divide en 2 partes:"
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14
-msgid "Part 1 is translation of the webpage."
-msgstr "La parte 1 es la traducción de la página web."
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17
-msgid ""
-"For collecting the bounty of 20 BTC you need to translate the following "
-"pages:"
-msgstr ""
-"Para recibir la recompensa de 20 BTC necesita traducir las siguientes "
-"páginas:"
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25
-msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada."
-msgstr ""
-"El trabajo fue hecho por Amanda y la recompensa de 20 BTC fue pagada a "
-"Amanda."
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27
-msgid ""
-"Part 2 is the translation of the router console. The router console was\n"
-"partly translated and the bounty of 80 BTC was paid to hamada."
-msgstr ""
-"La parte 2 es la traducción de la consola del ruter. La consola del ruter"
-" fue parcialmente traducida y la recompensa de 80 BTC se pagó a hamada."
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34
-msgid "Judge is echelon."
-msgstr "El juez es echelon."
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2
-msgid "Bounty creating a I2P native Bitcoin client"
-msgstr "Recompensa por la creación de un cliente nativo para I2P."
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3
-msgid "BTC I2P native client"
-msgstr "Cliente nativo BTC para I2P"
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6
-msgid ""
-"For a future of I2P and attract more people\n"
-"into I2P this bounty is to create a I2P native Bitcoin client. \n"
-"It should integrate with other client via the I2P network and via "
-"gateways to\n"
-"the existant bitcoin network."
-msgstr ""
-"Para el futuro de I2P y para atraer más gente a I2P esta recompensa se "
-"pensó para crear un cliente de Bitcoin para I2P. Debería integrarse con "
-"otros clientes dentro de la red de I2P y vía las salidas, con la red de "
-"Bitcoin actual."
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15
-msgid "Judge is psychonaut who donated the first 30 € to this bounty."
-msgstr ""
-"El juez es psychonaut quien donó los primeros 30 € para esta "
-"recompensa."
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
-msgid "Bounty datastorage"
-msgstr "Recompensa por el almacenamiento de datos."
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:3
-msgid "datastore"
-msgstr "almacenamiento de datos"
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:6
-msgid ""
-"To improve I2P's usage and to be independent of routers \n"
-"online status we want a datastorage as a extension to I2P.\n"
-"Like in Freenet the datastorage should be distributed and every\n"
-"participating node should be able to configure his options.\n"
-"The files should be saved in chunks and at least 2-3 times to\n"
-"obtain redundancy. Usage of storage space should be auto balanced.\n"
-"As it is a extra application, it should work flawless within I2P and\n"
-"cooperate nice with the I2P router. Maybe a integration within the\n"
-"webpage/router could be done."
-msgstr ""
-"Para mejorar el uso de I2P y ser independiente del estados de los ruters "
-"en funcionamiento queremos un sistema de almacenamiento de datos como una"
-" extensión de I2P. Como en Freenet, el almacenamiento de información "
-"debería ser distribuido y cada nodo participante debería poder configurar"
-" sus propias opciones. Los archivos deberían ser guardados en trozos y al"
-" menos 2-3 veces para obtener redundancia. El uso del espacio de "
-"almacenamiento debería ser auto balanceado. Y aunque sea una aplicación "
-"extra, debería funcionar perfectamente dentro de I2P y cooperar bien con "
-"el ruter I2P. Quizás se puede hacer una integración dentro de la página "
-"web o del ruter."
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:17
-msgid ""
-"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n"
-"\"eepsites in datastorage\"."
-msgstr ""
-"Esta recompensa está unida con otras 2 recompensas, \"frost para I2P\" y "
-"\"eepsites en el almacenamiento de datos\""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:21
-msgid ""
-"The frost for I2P datastorage bounty is paid for a frost like program \n"
-"with which files/messages are stored into database and got from database."
-"\n"
-"It needs to work with a GUI."
-msgstr ""
-"La recompensa por frost para el almacenamiento de datos de I2P es pagada "
-"por un programa tipo frost en donde los archivos o mensajes son "
-"almacenados dentro de una base de datos y obtenidos de la base de datos. "
-"Debe funcionar con GUI, entorno gráfico."
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:26
-msgid ""
-"The eepsite served out of I2P datastorage extends a I2P router to send\n"
-"out eepsites out of the I2P datastorage. All files for eepsites need to "
-"be\n"
-"saved inside of datastorage and are taken from it.\n"
-"Extension:\n"
-"For better integration all datastorage participants could serve that "
-"eepsite."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:36
-msgid ""
-"For bounties to be declared done and paid, we need the program AND the "
-"source.\n"
-"Source and code need to be licensed under a free license (free to change "
-"and \n"
-"free to distribute)."
-msgstr ""
-"Para que una recompensa sea declarada pagada, necesitamos la aplicación y"
-" el código. El código debe estar bajo una licencia libre (libre de "
-"cambiar y de distribuir el código)."
-
-#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2
-msgid "Bounty I2P package in Debian and Ubuntu mirrors"
-msgstr "Recompensa por el paquete I2P en los repositorios de Debian y Ubuntu"
-
-#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3
-msgid "I2P Ubuntu/Debian package"
-msgstr "Paquetes I2P para Ubuntu/Debian"
-
-#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6
-msgid ""
-"For the future of I2P and in order to attract more people\n"
-"to I2P, this bounty was set for including an I2P package into the Ubuntu "
-"and Debian \n"
-"archive mirrors.\n"
-"To claim this bounty, the I2P router package needs to be available from\n"
-"Ubuntu and Debian archive mirrors and Debian bug \n"
-"448638 \n"
-"needs to be closed successfully."
-msgstr ""
-"Para el futuro y para atraer más gente a I2P, esta recompensa se creó "
-"para incluir los paquetes de I2P dentro de los repositorios de Ubuntu y "
-"Debian. Para reclamar esta recompensa, el paquete del ruter de I2P debe "
-"estar disponible desde los repositorios de Ubuntu y Debian y el bug 448638 debe cerrarse exitosamente."
-
-#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2
-msgid "Bounty I2PHex code implementation"
-msgstr "Recompensa por la implementación de I2PHex"
-
-#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3
-msgid "i2phex code implementation"
-msgstr "Implementación del código fuente de I2P"
-
-#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2PHex P2P ArneBab setout the bounty for implementing actual\n"
-"Phex code onto I2PHex."
-msgstr ""
-"Para mejorar el uso de I2P y atraer más gente a I2PHex P2P, ArneBab creó "
-"la recompensa por implementar el código actual de Phex dentro de I2PHex."
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:5
-msgid "Bounties for I2P"
-msgstr "Recompensas por I2P"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:6
-msgid ""
-"While we always gratefully accept any contributions of code, \n"
-"documentation, and the like, there are other ways to help I2P move \n"
-"forward.  As with any open source project, our goals would be achieved "
-"more \n"
-"rapidly if we were able to support all of our contributors to work on \n"
-"I2P full time.  However, as with any open source project, that's not a \n"
-"possibility.  Instead, we are making use of a bounty system, whereby \n"
-"anyone can get support for working on something that people want \n"
-"implemented, and people who want to contribute to I2P can be assured that"
-" \n"
-"their support goes to what they care about."
-msgstr ""
-"Aunque siempre aceptamos con agradecimiento cualquier contribución al "
-"código, documentación, y de ese tipo, hay otras formas de hacer que I2P "
-"siga adelante. Al igual que con otros proyectos libres nuestros fines se "
-"podrían conseguir más rápido si fuésemos capaces de compensar a todos los"
-" ayudantes para que trabajasen en I2P a jornada completa. Pero, y al "
-"igual que con cualquier otro proyecto libre, esto no es posible. En lugar"
-" de eso, estamos utilizando un sistema de recompensas en donde cualquiera"
-" pude tener compensación por trabajar en algo que desea implementar, y la"
-" gente que ayuda a I2P puede estar segura que su apoyo va dirigido a lo "
-"que a ellos les interesa."
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:18
-msgid ""
-"We are also keeping open the ability for people who want to support I2P \n"
-"but don't have strong feelings about the bounties available.  Those "
-"people\n"
-"can simply put their trust in the I2P team to do what we feel is best by\n"
-"donating to a catch-all general fund that will be used as deemed \n"
-"necessary - allocated to various bounties, covering incidentals (hosting,"
-" \n"
-"etc), and the like."
-msgstr ""
-"También mantenemos abierta una posibilidad para la gente que quiere "
-"ayudar a I2P pero no está convencida de las recompensas disponibles. Esta"
-" gente simplemente puede poner su confianza en el equipo de I2P para que "
-"este haga lo que piense que es mejor, donando a un fondo general que será"
-" usado en lo que se considere necesario - usado para las recompensas, "
-"cubrir imprevistos (alojamiento, etc), y cosas de ese tipo."
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:27
-msgid "Current bounties"
-msgstr "Recompensas actuales"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-#: i2p2www/pages/site/get-involved/bounties/index.html:112
-msgid "Name"
-msgstr "Nombre"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-#: i2p2www/pages/site/get-involved/bounties/index.html:112
-msgid "Status"
-msgstr "Estado"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-msgid "Judge"
-msgstr "Juez"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-msgid "Bounty"
-msgstr "Recompensas"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:32
-msgid "Frost for I2P datastorage"
-msgstr "Frost para el almacenamiento de datos de I2P"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:33
-#: i2p2www/pages/site/get-involved/bounties/index.html:40
-#: i2p2www/pages/site/get-involved/bounties/index.html:47
-#: i2p2www/pages/site/get-involved/bounties/index.html:54
-#: i2p2www/pages/site/get-involved/bounties/index.html:61
-#: i2p2www/pages/site/get-involved/bounties/index.html:82
-#: i2p2www/pages/site/get-involved/bounties/index.html:89
-msgid "Proposal in development"
-msgstr "Proposición en desarrollo"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:39
-msgid "Eepsites served out of I2P datastorage"
-msgstr "Eepsites disponibles fuera del almacenamiento de datos de I2P"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:46
-msgid "Backporting Phex code onto I2PHex"
-msgstr "Portar el código de Phex dentro de I2PHex"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:53
-msgid "Make I2P IPv6 native"
-msgstr "Hacer I2P IPV6 nativo"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:60
-msgid "I2P package in Debian and Ubuntu mirrors"
-msgstr "Paquetes I2P disponibles en los repositorios de Debian y Ubuntu"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:68
-msgid "Done, phase of verification"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:74
-msgid "Unit tests and Multi-router Simulation"
-msgstr "Unit tests y simulación multi-tuter"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:75
-msgid "Partly done, partly in work, partly still open"
-msgstr "Parcialmente hecho, parcialmente trabajando, parcialmente aún abierto"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:96
-msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
-msgstr "Recompensas paradas, paradas a causa de la desaparición de jrandom."
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:101
-msgid "Bundling bounties"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:102
-msgid "Proposed"
-msgstr "Propuesto"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:109
-msgid "Claimed bounties"
-msgstr "Recompensas reclamadas"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:112
-msgid "Dev team"
-msgstr "Equipo de desarrollo"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:114
-msgid "Setting up a SILC server"
-msgstr "Configurar un servidor SILC"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:124
-msgid "Datastore over I2P"
-msgstr "Almacenamiento de datos sobre I2P."
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:129
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
-msgid "Russian translation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:134
-msgid "Swarming file transfer"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:139
-msgid "Streaming library window size"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:144
-msgid "IRC connect time monitor"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:149
-msgid "Unit tests (part 1)"
-msgstr "Unit tests (parte 1)"
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:161
-msgid ""
-"Dev lists anyone who may already be working on the bounty - collaboration"
-" is\n"
-"preferred, so if you're interested in working on it, please contact one "
-"of the\n"
-"people listed!"
-msgstr ""
-"Los desarrolladores listan a cualquier persona que haya podido trabajar "
-"en la recompensa -  por lo cual si está interesado en trabajar en ello, "
-"¡por favor contacte con una de las personas listadas!"
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2
-msgid "Bounty I2P IPv6 native"
-msgstr "Recompensa por IPV6 nativo para I2P"
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3
-msgid "native IPv6 I2P"
-msgstr "IPV6 nativo para I2P"
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6
-msgid ""
-"For a future of I2P and attract more people\n"
-"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n"
-"To claim this bounty, the I2P router needs to run full on native\n"
-"IPv6 connections like it does on IPv4."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:15
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
-msgid ""
-"For bounties to be declared done and paid, we need the plugin AND the "
-"source.\n"
-"Source and code need to be licensed under a free license (free to change "
-"and \n"
-"free to distribute)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:2
-msgid "NetDB Backend"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:3
-msgid "netDB backend"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:7
-msgid ""
-"The current NetDB implementation (namely the FloodFill system)\n"
-"needs to be extended with another backend to improve reliability,\n"
-"reduce attack surface and solve the scalability issue for the \n"
-"coming years."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:14
-msgid ""
-"A solution likely based on a DHT will be investigated and \n"
-"finally implemented."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2
-msgid "Bounty russian translation of webpage and router console"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2P a anonymous donator set out the bounty for translation\n"
-"of the I2P web page and I2P router console into russian language."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17
-msgid ""
-"For collecting the bounty of $115 USD you need to translate the following"
-" pages:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30
-msgid ""
-"Part 2 is the translation of the router console. The whole router console"
-" needs\n"
-"to be translated to collect the bounty of $115 USD."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37
-msgid "Judge is the russian donor."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:2
-msgid "Bounty migrate I2P IRC to SILC"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:3
-msgid "I2P silc server"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:7
-msgid ""
-"For a future of I2P and attract more people\n"
-"into I2P this bounty is to setup and host a I2P SILC server.   \n"
-"This will allow people to send files over their messaging servers and "
-"have intrinsic security built into the protocol."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:12
-msgid ""
-"A silc server needs to be set up and run for at least 3 month time to get"
-" payed. \n"
-"A second server should be set up, to."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:16
-msgid ""
-"Bounty was withdrawn and money donated to returningnovice and general "
-"fund."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:22
-msgid "Judge is An Anonymous Secret Society, society@mail.i2p."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7
-msgid ""
-"Beside of I2P we want to encourage users\n"
-"to care more about anonymity and security. As I2P is a low \n"
-"latency network with its natural limits, the software SYNDIE\n"
-"can overcome some of these limits and provide better anonymity\n"
-"for people who really need it."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14
-msgid ""
-"For our bad sake the syndie project was out of development for \n"
-"quite a long time yet (5 years). To get a fresh and new built \n"
-"with needed bugfixes we set out this bounty. Also syndie needs\n"
-"some enhancements and a better GUI for users to work with it.\n"
-"Current bounty sum is 50 Bitcoin."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22
-msgid ""
-"The latest Syndie coding rally did improve the situation of the\n"
-"Syndie package dramatically. A new Syndie package with bugfixes\n"
-"was created and made available on different webpages.\n"
-"As a result of this work, the bounty sum was reduced and\n"
-"the withdrawn money moved to the IPv6 bounty."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2
-msgid "Bounty unittests"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3
-msgid "unit test"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7
-msgid ""
-"To improve I2P's maintainability, we want to have a solid set of\n"
-"automated unit tests for the critical code.  While we do have some\n"
-"unit tests at the moment, they are ad-hoc and partly unfinished.  \n"
-"This bounty is for someone to check the existing tests and move over\n"
-"old ones to jUnit, automate their execution, extend them to provide \n"
-"better code coverage, and publish the report online.  Its a massive \n"
-"effort, but can be broken down into phases, listed below (phase 2 \n"
-"must occur first, but further phases may happen in any order).\n"
-"As this needs some reading of code, it is the best start point for\n"
-"new devs to get a good overview of I2P code and coding. A good job\n"
-"for college students, interns or anyone who is just interested."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20
-msgid ""
-"Take care! Jobs and bounties shuffled a bit!\n"
-"Phase 6,7 and 8 are still open!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112
-#, python-format
-msgid "Phase %(phase)s:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27
-msgid "CI jenkins and IRC bot"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114
-#, python-format
-msgid "Bounty: %(euro)s €"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29
-msgid "server runs and this section is blocked"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31
-msgid ""
-"To collect this bounty, a continuous integration server (Jenkins,\n"
-"old name was Hudson) must be set up and a connected IRC bot needs \n"
-"to set up in the channel #i2p-dev on IRC2p network to print out\n"
-"results of build tests.
            \n"
-"The server needs to be run long term."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41
-msgid "Check existing SDK tests"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69
-msgid "paid to str4d"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45
-#, python-format
-msgid ""
-"To collect this bounty, the existing SDK tests must be checked \n"
-"and made to work again. The need to be integrated into the ant \n"
-"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g."
-" \n"
-"Clover).  The ant script\n"
-"must be capable of generating test status results as a web page, \n"
-"which will be published online."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56
-msgid "SDK test coverage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80
-msgid "paid to unittests dev team"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60
-msgid ""
-"To collect this bounty, the automated unit tests of the SDK \n"
-"(i2p/core/java/src) must work again."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67
-msgid "Router test migration"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71
-msgid ""
-"As with phase 2, the existing unit tests for the router must be\n"
-"moved over to the automated system."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78
-msgid "Router test coverage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82
-msgid ""
-"To collect this bounty, the automated unit tests of the router \n"
-"(i2p/router/java/src) must work again."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89
-msgid "Streaming lib tests"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94
-#, python-format
-msgid ""
-"To collect this bounty, a new set of unit tests must meet a \n"
-"measured code coverage of 90% of the streaming lib \n"
-"(i2p/apps/ministreaming/ and i2p/apps/streaming/)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102
-msgid "Unit tests coverage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106
-msgid ""
-"To collect this bounty, all above unit tests must meet the 100%\n"
-"coverage marker (except for log statements)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113
-msgid "MultiRouter simulation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115
-msgid "will be split in more sub-tasks"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117
-msgid ""
-"To collect this bounty, the existing in-memory multi-router\n"
-"simulation must be checked, made work again and extend to simulate\n"
-"lots of routers in memory on a single machine. This bounty will\n"
-"be split in more fine grained subworks."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126
-msgid ""
-"Judge on all these works is the donor and donor decides if a phase is\n"
-"called succesfull done and money can be paid."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2
-msgid "Bounty I2P vuze plugin"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3
-msgid "vuze plugin"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2P torrent P2P I setout the bounty for a working I2P vuze\n"
-"plugin.\n"
-"The plugin needs to be official and submitted to vuze for publication\n"
-"on their webpage/repository for plugins.\n"
-"It should be easy to install and configured, work smooth and flawless.\n"
-"Configuration should be friendly to starters and made easy to be "
-"anonymous.\n"
-"It should work with *.b32.i2p destinations as with signed (516++ bits) \n"
-"destinations."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:2
-msgid "Application Development"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:6
-msgid "Application Development Guide"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:10
-#: i2p2www/pages/site/get-involved/develop/applications.html:16
-msgid "Why write I2P-specific code?"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:11
-#: i2p2www/pages/site/get-involved/develop/applications.html:102
-msgid "Important concepts"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:12
-#: i2p2www/pages/site/get-involved/develop/applications.html:190
-msgid "Development options"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:13
-#: i2p2www/pages/site/get-involved/develop/applications.html:303
-msgid "Start developing - a simple guide"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:18
-#, python-format
-msgid ""
-"There are multiple ways to use applications in I2P.\n"
-"Using I2PTunnel,\n"
-"you can use regular applications without needing to program explicit I2P "
-"support.\n"
-"This is very effective for client-server scenario's,\n"
-"where you need to connect to a single website.\n"
-"You can simply create a tunnel using I2PTunnel to connect to that "
-"website, as shown in Figure 1."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:26
-msgid ""
-"If your application is distributed, it will require connections to a "
-"large amount of peers.\n"
-"Using I2PTunnel, you will need to create a new tunnel for each peer you "
-"want to contact,\n"
-"as shown in Figure 2.\n"
-"This process can of course be automated, but running a lot of I2PTunnel "
-"instances creates a large amount of overhead.\n"
-"In addition, with many protocols you will need to force everyone to \n"
-"use the same set of ports for all peers - e.g. if you want to reliably "
-"run DCC \n"
-"chat, everyone needs to agree that port 10001 is Alice, port 10002 is "
-"Bob, port \n"
-"10003 is Charlie, and so on, since the protocol includes TCP/IP specific "
-"information\n"
-"(host and port)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:37
-msgid ""
-"General network applications often send a lot of additional data that "
-"could be used to identify users.\n"
-"Hostnames, port numbers, time zones, character sets, etc. are often sent "
-"without informing the user.\n"
-"As such, designing the network protocol specifically with anonymity in "
-"mind\n"
-"can avoid compromising user identities."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:43
-msgid ""
-"There are also efficiency considerations to review when determining how "
-"to \n"
-"interact on top of I2P.  The streaming library and things built on top of"
-" it\n"
-"operate with handshakes similar to TCP, while the core I2P protocols "
-"(I2NP and I2CP)\n"
-"are strictly message based (like UDP or in some instances raw IP).  The "
-"important\n"
-"distinction is that with I2P, communication is operating over a long fat "
-"network - \n"
-"each end to end message will have nontrivial latencies, but may contain "
-"payloads \n"
-"of up to several KB.  An application that needs a simple request and "
-"response can get rid\n"
-"of any state and drop the latency incurred by the startup and teardown "
-"handshakes\n"
-"by using (best effort) datagrams without having to worry about MTU "
-"detection or \n"
-"fragmentation of messages."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:57
-#: i2p2www/pages/site/get-involved/develop/applications.html:59
-msgid ""
-"Creating a server-client connection using I2PTunnel only requires "
-"creating a single tunnel."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:59
-msgid "Figure 1:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:64
-#: i2p2www/pages/site/get-involved/develop/applications.html:66
-msgid ""
-"Setting up connections for a peer-to-peer applications requires a very "
-"large amount of tunnels."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:66
-msgid "Figure 2:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:70
-msgid "In summary, a number of reasons to write I2P-specific code:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:74
-msgid ""
-"Creating a large amount of I2PTunnel instances consumes a non-trivial "
-"amount of resources,\n"
-"which is problematic for distributed applications (a new tunnel is "
-"required for each peer)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:78
-msgid ""
-"General network protocols often send a lot of additional data that can be"
-" used to identify users.\n"
-"Programming specifically for I2P allows the creation of a network "
-"protocol\n"
-"that does not leak such information, keeping users anonymous and secure."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:83
-msgid ""
-"Network protocols designed for use on the regular internet can be "
-"inefficient\n"
-"on I2P, which is a network with a much higher latency."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:90
-#, python-format
-msgid ""
-"I2P supports a standard plugins interface for"
-" developers\n"
-"so that applications may be easily integrated and distributed."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:96
-msgid ""
-"Applications written in Java and accessible/runnable\n"
-"using an HTML interface via the standard webapps/app.war\n"
-"may be considered for inclusion in the i2p distribution."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:104
-msgid "There are a few changes that require adjusting to when using I2P:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:108
-msgid "Destination ~= host+port"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:110
-msgid ""
-"An application running on I2P sends messages from and receives messages "
-"to a\n"
-"unique cryptographically secure end point - a \"destination\".  In TCP or"
-" UDP\n"
-"terms, a destination could (largely) be considered the equivalent of a "
-"hostname\n"
-"plus port number pair, though there are a few differences."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:118
-msgid ""
-"An I2P destination itself is a cryptographic construct - all data sent to"
-" one is \n"
-"encrypted as if there were universal deployment of IPsec with the "
-"(anonymized)\n"
-"location of the end point signed as if there were universal deployment of"
-" DNSSEC."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:123
-msgid ""
-"I2P destinations are mobile identifiers - they can be moved from one I2P "
-"router\n"
-"to another (or it can even \"multihome\" - operate on multiple routers at"
-"\n"
-"once).  This is quite different from the TCP or UDP world where a single "
-"end point (port)\n"
-"must stay on a single host."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:130
-msgid ""
-"I2P destinations are ugly and large - behind the scenes, they contain a "
-"2048 bit ElGamal\n"
-"public key for encryption, a 1024 bit DSA public key for signing, and a "
-"variable size \n"
-"certificate, which may contain proof of work or blinded data."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:135
-#, python-format
-msgid ""
-"There are existing ways to refer to these large and ugly destinations by "
-"short\n"
-"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not "
-"guarantee\n"
-"globally uniqueness (since they're stored locally in a database on each "
-"person's machine)\n"
-"and the current mechanism is not especially scalable nor secure (updates "
-"to the host list are\n"
-"managed using \"subscriptions\" to naming services).\n"
-"There may be some secure, human readable, scalable, and globally \n"
-"unique, naming system some day, but applications shouldn't depend upon it"
-" being in place,\n"
-"since there are those who don't think such a beast is possible.\n"
-"Further information on the naming system is "
-"available."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:149
-#, python-format
-msgid ""
-"While most applications do not need to distinguish protocols and ports,\n"
-"I2P does support them. Complex applications may specify a "
-"protocol,\n"
-"from port, and to port, on a per-message basis, to multiplex traffic on\n"
-"a single destination.\n"
-"See the datagram page for details.\n"
-"Simple applications operate by listening for \"all protocols\" on \"all "
-"ports\" of a destination."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:158
-msgid "Anonymity and confidentiality"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:160
-msgid ""
-"I2P has transparent end to end encryption\n"
-"and authentication for all data passed over the network - if Bob sends to"
-" Alice's destination,\n"
-"only Alice's destination can receive it, and if Bob is using the "
-"datagrams or streaming \n"
-"library, Alice knows for certain that Bob's destination is the one who "
-"sent the data."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:167
-msgid ""
-"Of course, I2P transparently anonymizes the\n"
-"data sent between Alice and Bob, but it does nothing to anonymize the "
-"content of what they\n"
-"send.  For instance, if Alice sends Bob a form with her full name, "
-"government IDs, and \n"
-"credit card numbers, there is nothing I2P can do.  As such, protocols and"
-" applications should \n"
-"keep in mind what information they are trying to protect and what "
-"information they are willing\n"
-"to expose."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:176
-msgid "I2P datagrams can be up to several KB"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:178
-#, python-format
-msgid ""
-"Applications that use I2P datagrams (either raw or repliable ones) can "
-"essentially be thought\n"
-"of in terms of UDP - the datagrams are unordered, best effort, and "
-"connectionless - but unlike\n"
-"UDP, applications don't need to worry about MTU detection and can simply "
-"fire off large datagrams.\n"
-"While the upper limit is nominally 32 KB, the message is fragmented for "
-"transport, thus dropping\n"
-"the reliability of the whole. Datagrams over about 10 KB are not "
-"currently recommended.\n"
-"See the datagram page for details.\n"
-"For many applications, 10 KB of data is sufficient for an\n"
-"entire request or response, allowing them to transparently operate in I2P"
-" as a UDP-like \n"
-"application without having to write fragmentation, resends, etc."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:192
-msgid ""
-"There are several means of sending data over I2P, each with their own "
-"pros and cons.\n"
-"The streaming lib is the recommended interface, used by the majority of "
-"I2P applications."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:197
-msgid "Streaming Lib"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:198
-#, python-format
-msgid ""
-"The full streaming library is now the "
-"standard\n"
-"interface. It allows programming using TCP-like sockets, as explained in "
-"the Streaming development guide."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:204
-#, python-format
-msgid ""
-"BOB is the Basic Open Bridge,\n"
-"allowing an application in any language to make streaming connections \n"
-"to and from I2P. At this point in time it lacks UDP support, but UDP "
-"support\n"
-"is planned in the near future. BOB also contains several tools, such as \n"
-"destination key generation, and verification that an address conforms to"
-" \n"
-"I2P specifications. Up to date info and applications that use BOB can be"
-" \n"
-"found at this eepsite."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:217
-msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:218
-#, python-format
-msgid ""
-"SAM is the Simple Anonymous Messaging protocol, "
-"allowing an\n"
-"application written in any language to talk to a SAM bridge through a "
-"plain TCP socket and have\n"
-"that bridge multiplex all of its I2P traffic, transparently coordinating "
-"the encryption/decryption\n"
-"and event based handling.  SAM supports three styles of operation:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:225
-msgid ""
-"streams, for when Alice and Bob want to send data to each other reliably "
-"and in order"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:228
-msgid ""
-"repliable datagrams, for when Alice wants to send Bob a message that Bob "
-"can reply to"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:231
-msgid ""
-"raw datagrams, for when Alice wants to squeeze the most bandwidth and "
-"performance as possible,\n"
-"and Bob doesn't care whether the data's sender is authenticated or not "
-"(e.g. the data transferred\n"
-"is self authenticating)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:237
-msgid ""
-"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n"
-"multiplexing/demultiplexing. Each I2P stream is handled by its own socket"
-" between the application\n"
-"and the SAM bridge. Besides, datagrams can be sent and received by the "
-"application through datagram\n"
-"communications with the SAM bridge."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:244
-#, python-format
-msgid ""
-"SAM V2 is a new version used by imule\n"
-"that fixes some of the problems in SAM.\n"
-"
            \n"
-"SAM V3 is used by imule since version 1.4.0."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:252
-msgid ""
-"The I2PTunnel application allows applications to build specific TCP-like "
-"tunnels to peers \n"
-"by creating either I2PTunnel 'client' applications (which listen on a "
-"specific port and connect\n"
-"to a specific I2P destination whenever a socket to that port is opened) "
-"or I2PTunnel 'server'\n"
-"applications (which listen to a specific I2P destination and whenever it "
-"gets a new I2P \n"
-"connection it outproxies to a specific TCP host/port).  These streams are"
-" 8-bit clean, and are\n"
-"authenticated and secured through the same streaming library that SAM "
-"uses, but there is a \n"
-"nontrivial overhead involved with creating multiple unique I2PTunnel "
-"instances, since each have\n"
-"their own unique I2P destination and their own set of tunnels, keys, etc."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:264
-msgid ""
-"I2P supports a SOCKS V4 and V5 proxy.\n"
-"Outbound connections work well. Inbound (server) and UDP functionality "
-"may be incomplete\n"
-"and untested."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:271
-msgid "Removed"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:272
-msgid ""
-"There used to be a simple \"ministreaming\" library,\n"
-"but now ministreaming.jar contains only the interfaces for the full "
-"streaming library."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:278
-msgid "Recommended for UDP-like applications"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:279
-#, python-format
-msgid ""
-"The Datagram library allows sending UDP-"
-"like packets.\n"
-"It's possible to use:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:284
-msgid "Repliable datagrams"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:285
-msgid "Raw datagrams"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:289
-msgid "Not recommended"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:290
-#, python-format
-msgid ""
-"I2CP itself is a language independent protocol, "
-"but to implement an I2CP library \n"
-"in something other than Java there is a significant amount of code to be "
-"written (encryption routines, \n"
-"object marshalling, asynchronous message handling, etc).  While someone "
-"could write an I2CP library in \n"
-"C or something else, it would most likely be more useful to use the C SAM"
-" library instead."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:297
-msgid "Web Applications"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:298
-msgid ""
-"I2P comes with the Jetty webserver, and configuring to use the Apache "
-"server instead is straightforward.\n"
-"Any standard web app technology should work."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:304
-msgid ""
-"Developing using I2P requires a working I2P installation and a "
-"development environment of your own choice.\n"
-"If you are using Java, you can start development with the streaming library or datagram library.\n"
-"Using another programming language, SAM or BOB can be used."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:310
-msgid "Developing with the streaming library"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:312
-msgid ""
-"The following example shows how to create TCP-like client and server "
-"applications\n"
-"using the streaming library."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:317
-msgid "This will require the following libraries in your classpath:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:321
-msgid "The streaming library itself"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:322
-msgid "Factory and interfaces for the streaming library"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:323
-msgid "Standard I2P classes, data structures, API, and utilities"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:326
-msgid ""
-"Network communication requires the usage of I2P network sockets.\n"
-"To demonstrate this, we will create an application where a client can "
-"send text messages to a server,\n"
-"who will print the messages and send them back to the client. In other "
-"words, the server will function as an echo."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:331
-msgid ""
-"We will start by initializing the server application. This requires "
-"getting an I2PSocketManager\n"
-"and creating an I2PServerSocket.\n"
-"We will not provide the I2PSocketManagerFactory with the saved keys for "
-"an existing Destination,\n"
-"so it will create a new Destination for us.\n"
-"So we will ask the I2PSocketManager for an I2PSession, so we can find out"
-" the Destination that\n"
-"was created, as we will need to copy and paste that information later so "
-"the client can connect to us."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:362
-msgid "Code example 1: initializing the server application."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:364
-msgid ""
-"Once we have an I2PServerSocket, we can create I2PSocket instances to "
-"accept connections from clients.\n"
-"In this example, we will create a single I2PSocket instance, that can "
-"only handle one client at a time.\n"
-"A real server would have to be able to handle multiple clients.\n"
-"To do this, multiple I2PSocket instances would have to be created, each "
-"in separate threads.\n"
-"Once we have created the I2PSocket instance, we read data, print it and "
-"send it back to the client.\n"
-"The bold code is the new code we add."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:448
-msgid "Code example 2: accepting connections from clients and handling messages."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:452
-msgid ""
-"When you run the above server code, it should print something like this "
-"(but without the line endings, it should just be\n"
-"one huge block of characters):"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:466
-msgid ""
-"This is the base64-representation of the server Destination. The client "
-"will need this string to reach the server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:470
-msgid ""
-"Now, we will create the client application. Again, a number of steps are "
-"required for initialization.\n"
-"Again, we will need to start by getting an I2PSocketManager.\n"
-"We won't use an I2PSession and an I2PServerSocket this time.\n"
-"Instead, we will use the server Destination string to start our "
-"connection.\n"
-"We will ask the user for the Destination string, and create an I2PSocket "
-"using this string.\n"
-"Once we have an I2PSocket, we can start sending and receiving data to and"
-" from the server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:554
-msgid ""
-"Code example 3: starting the client and connecting it to the server "
-"application."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:556
-msgid ""
-"Finally, you can run both the server and the client application.\n"
-"First, start the server application. It will print a Destination string "
-"(like shown above).\n"
-"Next, start the client application. When it requests a Destination "
-"string, you can enter the string printed by the server.\n"
-"The client will then send 'Hello I2P!' (along with a newline) to the "
-"server, who will print the message and send it back to the client."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:562
-msgid "Congratulations, you have successfully communicated over I2P!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:566
-msgid "Existing Applications"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:567
-msgid "Contact us if you would like to contribute."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:588
-msgid "Application Ideas"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:590
-msgid "NNTP server - there have been some in the past, none at the moment"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:593
-msgid ""
-"Jabber server - there have been some in the past, and there is one at the"
-" moment, with access to the public internet"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:596
-msgid "PGP Key server and/or proxy"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:599
-msgid ""
-"Content Distribution / DHT applications - resurrect feedspace,\n"
-"port dijjer, look for alternatives"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:603
-msgid "Help out with Syndie development"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:606
-msgid ""
-"Web-based applications - The sky is the limit for hosting web-server-"
-"based\n"
-"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n"
-"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:611
-msgid ""
-"Resurrect some old apps, several previously in the i2p source package -\n"
-"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2
-msgid "I2P Developer's MTN Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4
-msgid "MTN Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5
-msgid ""
-"Monotone servers used by the I2P project require two types of keys to be "
-"used."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
-msgid ""
-"Commit Keys to sign changes checked-in to the "
-"respository; and"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10
-msgid ""
-"Transport Keys to push changes to remote "
-"servers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13
-#, python-format
-msgid ""
-"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
-"import the\n"
-"developer commit keys, but only Monotone \n"
-"server operators will need to import the transport keys."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20
-msgid "Developer Commit keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:240
-msgid "Developer Transport Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:241
-#, python-format
-msgid ""
-"Note: Transport keys are only needed for setting up a\n"
-"Monotone server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
-msgid "License Agreements"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
-#, python-format
-msgid "For more information see the licenses page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8
-msgid ""
-"Following is a monotonerc file defining the current trust list.\n"
-"Developers must use this file in ~/.monotone/monotonerc or\n"
-"_MTN/montonerc in their i2p.i2p workspace."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17
-msgid "Agreements"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:4
-msgid "I2P Software Licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:5
-#, python-format
-msgid ""
-"As required by our\n"
-"threat model (among other reasons), the \n"
-"software developed to support the anonymous communication \n"
-"network we call I2P must be freely available, open source, \n"
-"and user modifiable.  To meet these criteria, we make use of\n"
-"a variety of legal and software engineering techniques so\n"
-"as to remove as many barriers to entry for those considering\n"
-"making use of or contributing to the I2P effort."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:16
-msgid ""
-"While the information below may be more confusing than just simply \n"
-"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
-"the short answer to the question \"How is I2P licensed?\" is this:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:22
-msgid "All software bundled in the I2P distributions will allow:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:24
-msgid "use without fee"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:25
-msgid ""
-"use with no restrictions on how, when, where, why, or by whom is running "
-"it"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:26
-msgid "access to the source code without fee"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:27
-msgid "modifications to the source"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:30
-msgid ""
-"Most of the software guarantees much more - the ability of anyone "
-"to \n"
-"distribute the modified source however they choose.  However, not all of "
-"the \n"
-"software bundled provides this freedom - the GPL restricts the ability of"
-" \n"
-"developers who wish to integrate I2P with their own applications that are"
-" not \n"
-"themselves open source applications.  While we applaud the noble goals of"
-" \n"
-"increasing the resources in the commons, I2P is best served by removing "
-"any\n"
-"barriers that stand in the way of its adoption - if a developer "
-"considering whether\n"
-"they can integrate I2P with their application has to stop and check with "
-"their lawyer,\n"
-"or conduct a code audit to make sure their own source can be released as "
-"GPL-compatible,\n"
-"we lose out."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:43
-msgid "Component licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:44
-msgid ""
-"The I2P distribution contains several resources, reflecting the "
-"partitioning of \n"
-"the source code into components.  Each component has its own license, "
-"which all \n"
-"developers who contribute to it agree to - either by explicitly declaring"
-" the release\n"
-"of code committed under a license compatible with that component, or by "
-"implicitly\n"
-"releasing the code committed under the component's primary license.  Each"
-" of these \n"
-"components has a lead developer who has the final say as to what license "
-"is compatible\n"
-"with the component's primary license, and the I2P project manager has the"
-" final say as\n"
-"to what licenses meet the above four guarantees for inclusion in the I2P "
-"distribution."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:57
-msgid "Component"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:58
-msgid "Source path"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:59
-msgid "Resource"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:60
-msgid "Primary license"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:61
-msgid "Alternate licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:62
-msgid "Lead developer"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:271
-msgid "GPL + java exception"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:272
-#, python-format
-msgid ""
-"While it may be redundant, just for clarity the\n"
-"GPL'ed code included within\n"
-"I2PTunnel and other apps must be released under the GPL with an "
-"additional \"exception\"\n"
-"explicitly authorizing the use of Java's standard libraries:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:288
-msgid ""
-"All source code under each component will by default be licensed under "
-"the\n"
-"primary license, unless marked otherwise in the code.  All of the above "
-"is\n"
-"summary of the license terms - please see the specific license for the "
-"component\n"
-"or source code in question for authoritative terms.  Component source "
-"locations and\n"
-"resource packaging may be changed if the repository is reorganized."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:296
-msgid "Commit privileges"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:297
-#, python-format
-msgid ""
-"Developers may push changes to a distributed monotone repository if you\n"
-"receive permission from the person running that repository.\n"
-"See the Monotone Page for details."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:303
-msgid ""
-"However, to have changes included in a release, developers\n"
-"must be trusted by the release manager (currently zzz).\n"
-"In addition, they must explicitly agree with the above terms to be "
-"trusted.\n"
-"That means that they must send one of the release managers a signed "
-"message affirming that:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:310
-msgid ""
-"Unless marked otherwise, all code I commit is implicitly licensed under\n"
-"the component's primary license"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:314
-msgid ""
-"If specified in the source, the code may be explicitly licensed under one"
-"\n"
-"of the component's alternate licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:318
-msgid ""
-"I have the right to release the code I commit under the terms I\n"
-"am committing it"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:324
-#, python-format
-msgid ""
-"If anyone is aware of any instances where the above conditions are not "
-"met,\n"
-"please contact the component lead and/or an I2P release manager with "
-"further\n"
-"information.\n"
-"See developers' license agreements."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
-msgid "Release Signing Key"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
-msgid "Releases 0.7.6 and later are signed by zzz. His public key is:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40
-msgid ""
-"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public "
-"key is:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2
-msgid "Signed Developer Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4
-msgid ""
-"Keys for zzz, Complication and welterde are provided clearsigned. The key"
-" for jrandom must be\n"
-"verified differently, since he's away, and only left a binary detached\n"
-"signature for his key."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16
-msgid "Monotone keys for zzz"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47
-msgid "Monotone keys for welterde"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79
-msgid "Monotone keys for Complication"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114
-msgid "Monotone keys for jrandom"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
-msgid ""
-"Tip: To find zzz's GPG key, on his eepsite locate the key "
-"`0xA76E0BED`, with\n"
-"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 "
-"B310 4155\n"
-"76BA A76E 0BED`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49
-msgid ""
-"Tip: To find welterde's GPG key, on public keyservers locate the "
-"key\n"
-"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720"
-" FD81\n"
-"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81
-msgid ""
-"Tip: To find Complication's GPG key, on his eepsite locate the key"
-"\n"
-"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint "
-"`73CF\n"
-"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116
-msgid ""
-"Tip: To find jrandom's GPG key for Syndie releases, on public "
-"keyservers locate\n"
-"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n"
-"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122
-msgid ""
-"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n"
-"deployed in the Syndie Monotone repository, in a file named `mtn-"
-"committers`.\n"
-"That file also had a GPG signature, `mtn-committers.sig`, but it was a "
-"binary\n"
-"detached signature. I am going to supply both files in GPG ASCII-armoured"
-" form\n"
-"below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130
-msgid ""
-"First, the file `mtn-committers` containing jrandom's Monotone key. Save "
-"as\n"
-"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers "
-"--dearmor\n"
-"mtn-committers.asc`:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151
-msgid ""
-"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n"
-"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-"
-"committers.sig\n"
-"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n"
-"`mtn-committers` file:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170
-#, python-format
-msgid ""
-"Some of the developers have included their Monotone keys in their signed license agreement."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2
-msgid "Developer Guidelines and Coding Style"
-msgstr "Estilo del código y pautas a seguir para los desarrolladores."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4
-#, python-format
-msgid "Read the new developers guide first."
-msgstr "Primero lea la guía para nuevos programadores."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8
-msgid "Basic Guidelines and Coding Style"
-msgstr "Pautas básicas y estilo del código"
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10
-msgid ""
-"Most of the following should be common sense for anybody who has worked "
-"on open source or in a commercial\n"
-"programming envrionment.\n"
-"The following applies mostly to the main development branch i2p.i2p.\n"
-"Guidelines for other branches, plugins, and external apps may be "
-"substantially different;\n"
-"check with the appropriate developer for guidance."
-msgstr ""
-"La mayor parte de lo siguiente debería ser de sentido común para "
-"cualquiera que haya trabajado para proyectos de código libre o en "
-"ambientes de desarrollo comerciales. Lo siguiente se aplica sobre todo "
-"para el desarrollo de la rama principal i2p.i2p. Las guías para otras "
-"ramas, pluguins y aplicaciones externas pueden ser bastante diferentes, "
-"pregúntele al desarrollador indicado en tal caso."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18
-msgid "Community"
-msgstr "Comunidad"
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20
-msgid ""
-"Please don't just \"write code\". If you can, participate in other "
-"development activities, including:\n"
-"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
-"testing;\n"
-"bug reporting and responses; documentation; code reviews; etc."
-msgstr ""
-"Por favor no sólo \"escriba código\". Si puede, participe en otras "
-"actividades de desarrollo como: discusiones sobre el desarrollo y soporte"
-" en el IRC, zzz.i2p, y el foro de.i2p; reporte y solución de errores; "
-"documentación, revisión del código, etc."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25
-msgid ""
-"Active devs should be available periodically on IRC #i2p-dev.\n"
-"Be aware of the current release cycle.\n"
-"Adhere to release milestones such as feature freeze, tag freeze, and\n"
-"the checkin deadline for a release."
-msgstr ""
-"Los programadores activos deberían estar disponibles periódicamente en el"
-" canal #i2p-dev del IRC. Tenga en cuenta el ciclo de liberación de "
-"versiones actual. Fix this! not translated all yet!!! "
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35
-msgid ""
-"Have a basic understanding of distributed source control systems, even if"
-" you haven't\n"
-"used monotone before. Ask for help if you need it.\n"
-"Once pushed, checkins are forever, there is no undo. Please be careful.\n"
-"If you have not used monotone before, start with baby steps.\n"
-"Check in some small changes and see how it goes."
-msgstr ""
-"Debe tener conocimientos básicos del funcionamiento de sistemas de "
-"control de código, incluso si nunca ha usado monotone antes. Pida ayuda "
-"si lo necesita. Una vez subido algo no hay vuelta atrás, no se puede "
-"deshacer, por favor tenga cuidado. Si nunca ha usado monotone antes "
-"empiece con mucho cuidado. Suba pequeños cambios y observe como funciona."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42
-msgid ""
-"Test your changes before checking them in.\n"
-"If you prefer the checkin-before-test development model,\n"
-"use your own development branch (e.g. i2p.i2p.yourname.test)\n"
-"and propagate back to i2p.i2p once it is working well.\n"
-"Do not break the build. Do not cause regressions.\n"
-"In case you do (it happens), please do not vanish for a long period after"
-"\n"
-"you push your change."
-msgstr ""
-"Pruebe los cambios antes de subirlos. Si prefiere el modelo de desarrollo"
-" subir-antes-de-probar use su propia rama de desarrollo (por ejemplo "
-"i2p.i2p.yourname.test) y envíelo de vuelta a i2p.i2p una vez que funcione"
-" correctamente. No rompa la compilación. No cree regresiones. En caso de "
-"que lo haga (a veces ocurre), no desaparezca por mucho tiempo antes de "
-"subir el cambio."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51
-msgid ""
-"If your change is non-trivial, or you want people to test it and need "
-"good test reports\n"
-"to know whether your change was tested or not, add a checkin comment to "
-"history.txt\n"
-"and increment the build revision in RouterVersion.java."
-msgstr ""
-"Si su cambio no es trivial, o desea que otra gente lo pruebe y necesita "
-"reportes fiables para saber si su cambio ha sido probado o no, añada un "
-"comentario de confirmación en history.txt e incremente la versión de "
-"compilación en RouterVersion.java."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56
-msgid ""
-"Ensure that you have the latest monotonerc file in _MTN.\n"
-"Do not check in on top of untrusted revisions."
-msgstr ""
-"Asegúrese de que tiene  la última versión del archivo monotonerc en _MTN."
-" No lo sobrescriba con versiones no confiables."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60
-msgid ""
-"Ensure that you pull the latest revision before you check in.\n"
-"If you inadvertently diverge, merge and push as soon as possible.\n"
-"Don't routinely make others merge for you.\n"
-"Yes, we know that monotone says you should push and then merge,\n"
-"but in our experience, in-workspace merge works just as well as in-"
-"database merge,\n"
-"without creating a merge revision."
-msgstr ""
-"asegúrese que ha descargado la última revisión antes de subir los "
-"cambios. Si crea un divergencia accidentalmente, una y suba tan pronto "
-"como sea posible. No haga que otros lo fusionen rutinariamente por usted."
-" Si, sabemos que monotone indica que debe subir y unir, pero por nuestra "
-"experiencia sabemos que funciona tan bien la unión in-workspace como la "
-"unión n-database si crear una revisión de unión."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
-msgid ""
-"Do not check in major changes into the main i2p.i2p branch late in the "
-"release cycle.\n"
-"If a project will take you more than a couple days, create your own "
-"branch in monotone\n"
-"and do the development there so you do not block releases."
-msgstr ""
-"No suba cambios grandes a la rama principal i2p.i2p al final del ciclo de"
-" versión. Si un proyecto va a tardar más de varios días, cree si propia "
-"rama de monotone y programe allí para no no bloquear la salida de nueva "
-"versiones."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75
-msgid "Coding Style"
-msgstr "Estilo de programación"
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77
-msgid ""
-"Coding style throughout most of the code is 4-spaces for indentation. Do "
-"not use tabs.\n"
-"Do not reformat code. If your IDE or editor wants to reformat everything,"
-" get control of it.\n"
-"Yes, we know 4 spaces is a pain, but perhaps you can configure your "
-"editor appropriately.\n"
-"In some places, the coding style is different.\n"
-"Use common sense. Emulate the style in the file you are modifying."
-msgstr ""
-"El código de estilo en la mayoría de  los casos  es de usar la sangría de"
-" 4 espacios. No use tabulación. No cambie el formato del código. Si su "
-"editor o IDE quiere cambiar el formato configúrelo para que no lo haga. "
-"Sí, sabemos que usar 4 espacios es doloroso, pero probablemente pueda "
-"configurar su editor apropiadamente. En algunos casos el estilo de "
-"programar es diferente, use el sentido común, emule el estilo del archivo"
-" que está modificando."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84
-msgid ""
-"New classes and methods require at least brief javadocs. Add @since "
-"release-number."
-msgstr ""
-"Las nuevas clases y métodos necesitan al menos un javadocs básico. Añada "
-"@since numero-versión."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87
-msgid ""
-"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our "
-"official API.\n"
-"There are several out-of-tree plugins and other applications that rely on"
-" this API.\n"
-"Be careful not to make any changes that break compatibility.\n"
-"Don't add methods to the API unless they are of general utility.\n"
-"Javadocs for API methods should be clear and complete.\n"
-"If you add or change the API, also update the documentation on the "
-"website (i2p.www branch)."
-msgstr ""
-"Las clases del núcleo/ (i2p.jar) y partes de i2ptunnel están incluidas en"
-" el API oficial. \n"
-"Hay varios pluguins y otras aplicaciones que dependen de este API.\n"
-"Tenga cuidado en no hacer cambios que rompan la compatibilidad.\n"
-"No añada métodos al API a no ser que sean de utilidad general.\n"
-"Los Javadocs de los métodos del API deben ser claros y completos.\n"
-"Si añades cambios al API, debe también actualizar la documentación en la "
-"web (i2p.www branch)."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95
-msgid ""
-"Tag strings for translation where appropriate.\n"
-"Don't change existing tagged strings unless really necessary, as it will "
-"break existing translations.\n"
-"Do not add or change tagged strings after the \"tag freeze\" in the "
-"release cycle so that\n"
-"translators have a chance to update before the release."
-msgstr ""
-"Incluya cadenas de texto para la traducción cuando sea apropiado.\n"
-"No cambie las cadenas ya etiquetadas a no ser que sea necesario ya que "
-"rompería las traducciones existentes.\n"
-"No añada o cambie las cadenas después del \"tag freeze\" durante la "
-"liberación de la versión,\n"
-"así los programadores tienen la oportunidad de actualizarlo antes de su "
-"liberación"
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101
-msgid ""
-"Use generics and concurrent classes where possible. I2P is a highly "
-"multi-threaded application."
-msgstr ""
-"Siempre que pueda use clases genéricas y concurrentes. I2P es una "
-"aplicación multi-hilos."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104
-msgid ""
-"We require Java 6 to build but only Java 5 to run I2P.\n"
-"Do not use Java 6 classes or methods without handling the class not found"
-" exceptions\n"
-"and providing alternate Java 5 code. See classes in net.i2p.util for "
-"examples."
-msgstr ""
-"Necesita Java 6 para compilar I2P, pero sólo Java 5 para ejecutarlo.\n"
-"No use las clases o métodos de Java 6 sin encargase antes de las clases "
-"de excepciones not found\n"
-"y de proporcionar el código alternativo para Java 5. Vea los ejemplos de "
-"clases en net.i2p.util."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109
-msgid ""
-"Explicitly convert between primitive types and classes;\n"
-"don't rely on autoboxing/unboxing."
-msgstr ""
-"Convierta explícitamente entre tipos primitivos y clases;\n"
-"no confíe en autoboxing/unboxing."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117
-msgid ""
-"Only check in code that you wrote yourself.\n"
-"Before checking in any code or library jars from other sources,\n"
-"justify why it is necessary,\n"
-"verify the license is compatible,\n"
-"and obtain approval from the lead developer."
-msgstr ""
-"Sólo suba el código que ha escrito usted.\n"
-"Antes de subir el código o librerías de otras fuentes,\n"
-"verifique que la licencia es compatible,\n"
-"y obtenga permiso del desarrollador."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124
-msgid ""
-"For any images checked in from external sources,\n"
-"it is your responsibility to first verify the license is compatible.\n"
-"Include the license and source information in the checkin comment."
-msgstr ""
-"Para cualquier imagen subida de fuentes externas,\n"
-"es su responsabilidad verificar primero si la licencia es compatible.\n"
-"Incluya la licencia y la información de la fuente en el comentario de "
-"subida."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131
-msgid "Bugs"
-msgstr "Bugs"
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
-#, python-format
-msgid ""
-"Managing Trac tickets is everybody's job, please help.\n"
-"Monitor %(trac)s for tickets you have been assigned or can help with.\n"
-"Assign, categorize, comment on, fix, or close tickets if you can."
-msgstr ""
-"Mantener las entradas del Trac es trabajo de todos, por favor denos su "
-"ayuda.\n"
-"Observe el %(trac)s por entradas que le hayan sido asignadas o en las que"
-" pueda ayudar.\n"
-"Asigne, categorice, comente, arregle, o cierre entradas si puede."
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138
-msgid ""
-"Close a ticket when you think you've fixed it.\n"
-"We don't have a test department to verify and close tickets.\n"
-"If you arent sure you fixed it, close it and add a note saying\n"
-"\"I think I fixed it, please test and reopen if it's still broken\".\n"
-"Add a comment with the dev build number or revision and set\n"
-"the milestone to the next release."
-msgstr ""
-"Cierre la entrada cuando piense que la ha arreglado.\n"
-"No tenemos un departamento de pruebas para verificar las entradas "
-"cerradas.\n"
-"Si no está seguro de haberlo solucionado, ciérrela y añada una nota "
-"diciendo \"I think I fixed it, please test and reopen if it's still "
-"broken\".\n"
-"Añada un comentario con el número de compilación o la revisión y "
-"establezca el hito para la siguiente versión."
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:4
-msgid ""
-"The main I2P development branch (i2p.i2p) has been set up to"
-" enable developers to easily set up two of the commonly-used IDEs for "
-"Java development: Eclipse and NetBeans."
-msgstr ""
-"La rama principal de desarrollo de I2P (i2p.i2p) ha sido "
-"configurada para permitir a los desarrolladores configurar fácilmente los"
-" dos IDEs de desarrollo de JAVA más usados: Eclipse y NetBeans."
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:10
-msgid ""
-"The main I2P development branches (i2p.i2p and branches from"
-" it) contain .project and .classpath Eclipse files, to enable the branch "
-"to be easily set up in Eclipse."
-msgstr ""
-"Las ramas principales de desarrollo de I2P (i2p.i2p y sus "
-"ramas) contienen los archivos para Eclipse .project y .classpath, para "
-"permitir una configuración fácil de I2P en eclipse."
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:16
-msgid ""
-"Check out the I2P branch into some directory (e.g. "
-"$HOME/dev/i2p.i2p)."
-msgstr ""
-"Descarga a rama de I2P a algún directorio ( por ejemplo "
-"$HOME/dev/i2p.i2p)."
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:20
-msgid ""
-"Open Eclipse and create a new Workspace, based in the directory that the "
-"I2P branch was checked out to."
-msgstr ""
-"Abre Eclipse y crea un nuevo Espacio de Trabajo, Workspace, basado en el "
-"directorio donde se ha descargado la rama de I2P."
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:24
-msgid ""
-"Select \"File - Import...\" and then under \"General\" select \"Existing "
-"Projects into Workspace\"."
-msgstr ""
-"Seleccione \"Archivo - Importar...\" y entonces en \"General\" seleccione"
-" \"Proyectos existentes al Espacio de Trabajo\""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:28
-msgid ""
-"For \"Select root directory:\" choose the directory that the I2P branch "
-"was checked out to."
-msgstr ""
-"Para \"Seleccionar el directorio raíz:\" elija la carpeta donde ha "
-"descargado la rama de I2P."
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:32
-msgid "If necessary, click \"Refresh\" to refresh the list of projects."
-msgstr "Si es necesario, pulse \"Recargar\" para refrescar la lista de proyectos."
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:36
-msgid "Select every project in the list, and click \"Finish\"."
-msgstr "Seleccione cada proyecto de la lista y pulse \"Terminar\"."
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:40
-msgid ""
-"Done! Your workspace should now contain all projects within the I2P "
-"branch, and their build dependencies should be correctly set up."
-msgstr ""
-"¡Listo! Su espacio de trabajo debería incluir todos los proyectos de la "
-"rama de I2P, y sus dependencias deberían estar correctamente "
-"configuradas."
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:48
-msgid ""
-"The main I2P development branches (i2p.i2p and branches from"
-" it) contain NetBeans project files."
-msgstr ""
-"Las ramas principales del proyecto de I2P (i2p.i2p y sus "
-"ramas) contienen los archivos del proyecto necesarios para NetBeans."
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:9
-msgid "Operating a Monotone client"
-msgstr "Usando el cliente Monotone"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:11
-#: i2p2www/pages/site/get-involved/guides/monotone.html:63
-msgid "Generating Monotone keys"
-msgstr "Generando las claves de Monotone"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:12
-msgid "Trust and initializing your repository"
-msgstr "Confianza e iniciando su repositorio"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:13
-#: i2p2www/pages/site/get-involved/guides/monotone.html:196
-msgid "Obtaining and deploying developers' keys"
-msgstr "Obteniendo y desplegando las claves de los desarrolladores"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:14
-#: i2p2www/pages/site/get-involved/guides/monotone.html:227
-msgid "Setting up trust evaluation hooks"
-msgstr "Configurar las conexiones de confianza"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:15
-#: i2p2www/pages/site/get-involved/guides/monotone.html:268
-msgid ""
-"Pulling the i2p.i2p, i2p.www and "
-"i2p.syndie branches"
-msgstr ""
-"Descargar las ramas de i2p.i2p, i2p.www y "
-"i2p.syndie"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:16
-#: i2p2www/pages/site/get-involved/guides/monotone.html:308
-msgid "Verifying that trust evaluation works"
-msgstr "Verificar que la evaluación de confianza funciona"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:17
-#: i2p2www/pages/site/get-involved/guides/monotone.html:357
-msgid "Checking out a working copy of the latest version"
-msgstr "Descargar una copia funcional de la última versión"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:18
-#: i2p2www/pages/site/get-involved/guides/monotone.html:384
-msgid "Updating your working copy to the latest version"
-msgstr "Actualizar sus fuentes a la última versión"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:22
-#: i2p2www/pages/site/get-involved/guides/monotone.html:414
-msgid "Operating a Monotone Server"
-msgstr "Usando en servidor Monotone"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:24
-msgid "Obtaining and deploying developers’ transport keys"
-msgstr "Obteniendo y desplegando las claves de transporte de los desarrolladores"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:25
-#: i2p2www/pages/site/get-involved/guides/monotone.html:424
-msgid "Granting push and pull access"
-msgstr "Obtener acceso para subir y descargar"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:26
-#: i2p2www/pages/site/get-involved/guides/monotone.html:469
-msgid "Running Monotone in server mode"
-msgstr "Ejecutar Monotone en modo servidor"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:27
-#: i2p2www/pages/site/get-involved/guides/monotone.html:494
-msgid "Differences under Debian GNU/Linux"
-msgstr "Diferencias en Debian GNU/Linux"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:34
-#, python-format
-msgid ""
-"This is a revised version of Complication's original\n"
-"  guide detailing the use of Monotone in I2P development.\n"
-"  For basic instructions see the quick-start "
-"guide."
-msgstr ""
-"Esto es una versión revisada de la guía "
-"original de Complication detallando el uso de Monotone en el "
-"desarrollo de I2P. Para obtener instrucciones básicas vea la guía rápida."
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:42
-#, python-format
-msgid ""
-"I2P has a distributed development model. The source code is replicated "
-"across\n"
-"  independently administered Monotone (\"MTN\") repositories.\n"
-"  Developers with commit rights are able to push their changes to the "
-"repository\n"
-"  (a license agreement needs to be "
-"signed\n"
-"  before commit rights are granted)."
-msgstr ""
-"I2P usa un modelo distribuido de desarrollo. El código es replicado por "
-"administradores independientes en repositorios Monotone (\"MTN\"). Los "
-"desarrolladores con derechos para ello pueden subir sus cambios al "
-"repositorio (deben firmar un acuerdo de "
-"licencia antes de obtener estos derechos)"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:52
-msgid ""
-"Some of Monotone's noteworthy qualities are: distributed\n"
-"  version control, cryptographic authentication, access control, its "
-"small size, having few\n"
-"  dependencies, storage of projects in a compressed SQLite database file,"
-" and\n"
-"  having the ability to resume interrupted synchronization attempts."
-msgstr ""
-"Algunas de las notables cualidades de Monotone son: control de versiones "
-"distribuido, autenticación con cifrados, acceso de control, su pequeño "
-"tamaño, tiene pocas dependencias, el almacenamiento de los proyectos usa "
-"una base de datos SQLite comprimida, y además tiene la capacidad de "
-"reanudar  los intentos de sincronización interrumpidos."
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:61
-msgid "Operating a Monotone Client"
-msgstr "Usando un cliente Monotone"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:66
-msgid ""
-"A transport key grants you the ability to push your changes to a Monotone"
-" repository server.\n"
-"  In order to commit code into Monotone (in essence signing your code), a"
-" commit key is also needed.\n"
-"  None of the public Monotone servers on I2P currently require a key in "
-"order to read (or pull) the source code."
-msgstr ""
-"Una clave de transporte le permite subir sus cambios al repositorio del "
-"servidor Monotone. Para poder subir código a Monotone (firmando su "
-"código), es necesaria una clave de subida. Ninguno de los servidores "
-"públicos de Monotone en I2P necesita claves para poder leer (o descargar)"
-" el código."
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:74
-msgid ""
-"Without a transport key, one cannot:\n"
-"  
              \n"
-"    
            • pull code from a server which doesn't allow global read "
-"access
              • \n"
-"    
            • push code to any server
              • \n"
-"    
            • run a Monotone server
              • \n"
-"  
            "
-msgstr ""
-"Sin una clave de transporte no se puede:\n"
-"
              \n"
-"
            • descargar el código de un servidor que no permita acceso global de "
-"lectura
              • \n"
-"
            • subir código a cualquier servidor
              • \n"
-"
            • ejecutar un servidor Monotone
              • \n"
-"
            "
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:85
-msgid ""
-"Without a commit key, one cannot:\n"
-"  
              \n"
-"    
            • commit any code
              • \n"
-"  
            "
-msgstr ""
-"Sin una clave de subida no se puede:\n"
-"
              \n"
-"
            • subir ningún código
              • \n"
-"
            "
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:94
-msgid ""
-"If you only intend to retrieve code from MTN, feel free to skip to the\n"
-"  next section. "
-"If you want\n"
-"  to generate keys, read the following."
-msgstr ""
-"So sólo desea obtener el código de MTN salte a la siguiente sección. Si desea generar "
-"las claves siga leyendo aquí."
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:102
-msgid ""
-"By convention keys are named like an e-mail addresses, but a "
-"corresponding e-mail\n"
-"  address does not need to exist. For example, your keys might be named:"
-msgstr ""
-"Por convenio las claves son nombradas como una dirección de email, pero "
-"no es necesario que exista un email correspondiente. Por ejemplo, sus "
-"claves podrían llamarse:"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:113
-msgid ""
-"Monotone stores keys under $HOME/.monotone/keys in "
-"text files which\n"
-"  are named identically to the keys. For example:"
-msgstr ""
-"Monotone guarda las claves en $HOME/.monotone/keys en"
-" archivos de texto que se llaman exactamente igual que la clave. Por "
-"ejemplo:"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:123
-msgid ""
-"To generate transport and commit keys, enter the following commands at a "
-"prompt:"
-msgstr ""
-"Para generar las claves de transporte y subida ejecute los siguientes "
-"comandos en la terminal:"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:133
-msgid ""
-"Monotone will prompt you for a password to protect your keys. You are "
-"very strongly encouraged to set a password\n"
-"  for the commit key. Many users will leave an empty password for the "
-"transport key, especially those running a\n"
-"  Monotone server."
-msgstr ""
-"Monotone le pedirá una contraseña para proteger sus claves. Se recomienda"
-" encarecidamente usar una contraseña para la clave de subida. Muchos "
-"usuarios dejan la contraseña de transporte en blanco, sobre todo los que "
-"ejecutan un servidor Monotone."
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:141
-msgid "Trust, and initializing your repository"
-msgstr "Confianza e iniciando su repositorio"
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:145
-msgid ""
-"Monotone's security model helps to ensure that nobody can easily "
-"impersonate a developer without\n"
-"  it being noticed. Since developers can make mistakes and become "
-"compromised,only manual review can\n"
-"  ensure quality of code. Monotone's trust model will ensure that you "
-"read the right diffs. It does\n"
-"  not replace reading diffs."
-msgstr ""
-"El modelo de seguridad de Monotone ayuda a asegurar que nadie puede "
-"suplantar a un programador fácilmente si ser detectado. Ya que los "
-"programadores pueden cometer errores y pueden ser comprometidos, sólo una"
-" revisión manual puede asegurar la calidad del código. El modelo de "
-"confianza de Monotone se asegura de que usted sólo lea los cambios "
-"correctos. No reemplaza los cambios de lectura."
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:155
-msgid ""
-"A Monotone repository is a single file (a compressed SQLite database) "
-"which contains all of the project's source code and history."
-msgstr ""
-"Un repositorio Monotono es un solo archivo (comprimido en una base de "
-"datos SQLite) que contiene todo el código del proyecto y su historial."
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:161
-msgid ""
-"After importing the "
-"developers' keys into Monotone and\n"
-"  setting up trust "
-"evaluation hooks,\n"
-"  Monotone will prevent untrusted code from being checked out into your "
-"workspace.\n"
-"  There are commands available to clean untrusted code from your "
-"workspace but in practice they've not been\n"
-"  needed due to the push access policies in place."
-msgstr ""
-"Después de  importar"
-" las claves de los desarrolladores a Monotone y de configurar las conexiones de "
-"confianza, Monotone evitará que cualquier código que no sea de "
-"confianza sea subido a su espacio de trabajo.\n"
-"Existen comandos disponibles para limpiar el código no confiable de su "
-"espacio de trabajo, pero en práctica no han sido necesitados debido a las"
-" reglas de acceso de subida activas."
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:171
-msgid ""
-"A repository can hold many branches. For example, our repository holds "
-"the\n"
-"  following main branches:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:176
-msgid "The I2P router and associated programs"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:177
-msgid "The I2P project website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:178
-msgid "Syndie, a distributed forums tool"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:183
-msgid ""
-"By convention, the I2P Monotone repository is named i2p.mtn."
-" Before pulling\n"
-"  source code from servers, a database for your repository will need to "
-"be initialized.\n"
-"  To initialize your local repository, change into the directory that you"
-" want the\n"
-"  i2p.mtn file and branch directories to be stored and issue"
-" the following\n"
-"  command:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:199
-msgid ""
-"Keys which developers use to commit code are essential for trust "
-"evaluation in\n"
-"  Monotone. The other developers' transport keys are only required for "
-"Monotone server operators.\n"
-"  "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:206
-#, python-format
-msgid ""
-"Developers' commit keys are provided GPG-signed on another page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:212
-#, python-format
-msgid ""
-"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
-"  file. Create this file (e.g. keys.txt) in the same "
-"directory where i2p.mtn is located. Import the keys with the"
-" command:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:222
-msgid ""
-"Note: Never add keys to "
-"$HOME/.monotone/keys manually."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:230
-msgid ""
-"The default Monotone trust policy is way too lax for our requirements: "
-"every comitter is trusted by default.\n"
-"  That is not acceptable for I2P development."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:237
-msgid ""
-"Change into the directory $HOME/.monotone and open "
-"the file\n"
-"  monotonerc with a text editor. Copy and paste the "
-"following two functions into this file:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:246
-msgid ""
-"The first function determines an intersection between two sets, in our "
-"case a\n"
-"  revision's signers and trusted signers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:253
-msgid ""
-"The second function determines trust in a given revision, by calling the "
-"first\n"
-"  function with \"signers\" and \"trusted\" as arguments. If the "
-"intersection is\n"
-"  null, the revision is not trusted. If the intersection is not empty, "
-"the\n"
-"  revision is trusted. Otherwise, the revision is not trusted."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:262
-msgid ""
-"More information about Trust Evauluation Hooks can be found in the official Monotone "
-"documentation."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:271
-msgid ""
-"Enter the directory where you initialized i2p.mtn. Depending "
-"on whether you\n"
-"  want only I2P sources, or also sources for the I2P website and Syndie, "
-"you can\n"
-"  perform the pull operation in different ways."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:279
-msgid "If you only want I2P sources:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:288
-msgid "If you want all branches:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:294
-msgid ""
-"If the transfer aborts before completing sucessfully, simply repeating "
-"the pull command will resume the transfer."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:300
-msgid ""
-"Pulling in the above examples is done anonymously by specifying an empty "
-"transport key.\n"
-"  If everyone pulls anonymously it will be harder for an attacker who "
-"gains control of the server\n"
-"  to selectively provide some people with tampered data."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:311
-msgid "To verify that trust evaluation works:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:315
-msgid "Make a backup of your monotonerc file."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:316
-msgid ""
-"Modify monotonerc by setting the trusted_signers "
-"variable in the following way:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:322
-msgid ""
-"With monotonerc configured as above, Monotone will no"
-" longer trust any committers. Confirm this by changing into the\n"
-"directory where i2p.mtn was created and attempt a checkout "
-"of the I2P branch:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:332
-msgid ""
-"A directory named i2p.i2p should not appear. You "
-"should encounter many\n"
-"  error messages like:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:349
-msgid ""
-"If you are satisfied with results, restore the backup of\n"
-"  monotonerc that was created above. If you didn't create a "
-"backup\n"
-"  as advised, re-read Setting up trust evaluation hools."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:360
-msgid ""
-"If you already have a branch checked out, skip to the next\n"
-"  section."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:367
-msgid ""
-"Change into the directory where i2p.mtn is located. Over "
-"there issue:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:376
-msgid ""
-"The checkout should complete without error messages and a directory named"
-"\n"
-"  i2p.i2p should appear in the current directory. "
-"Congratulations! You have\n"
-"  successfully checked out the latest I2P sources, ready to be compiled."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:387
-msgid ""
-"If you haven't done this already, pull fresh code from the server to your"
-" local\n"
-"  Monotone repository. To accomplish this, change into the directory "
-"where\n"
-"  i2p.mtn is located and issue:\n"
-"  
              \n"
-"    
            • $ mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
-"i2p.i2p
              • \n"
-"  
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:398
-msgid "Now change into your i2p.i2p directory, and over there issue:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:407
-msgid ""
-"As long as there were no errors…Congratulations! You have "
-"successfully updated to the latest I2P sources. They\n"
-"  should be ready to compile."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:416
-msgid "Obtaining and deploying developers' transport keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:419
-msgid ""
-"As a server operator you may want to grant push access to certain "
-"developers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:427
-msgid "By default the Monotone server denies all access."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:433
-msgid "To grant pull access to all clients, set the following in"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:445
-msgid ""
-"No one will not be able to push code to your server without permission "
-"being explicitly granted. To grant push access:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:451
-msgid ""
-"Add the name of the user's transport key to\n"
-"$HOME/.monotone/write-permissions, such as\n"
-"
            \n"
-"    zzz-transport@mail.i2p\n"
-"    complication-transport@mail.i2p\n"
-"
            \n"
-"with one key per line."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:462
-msgid ""
-"Import the transport key(s) into your database. The procedure for "
-"importing transport keys is the same as for\n"
-"importing commit keys, which is described in the section Obtaining and deploying "
-"developers' keys."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:472
-msgid ""
-"A separate database should be used for your Monotone server because "
-"monotone will lock the database while it is served to others.\n"
-"  Make a copy of your development database, then start the server with:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:479
-msgid ""
-"If your key is protected with a passphrase, Monotone may request the "
-"passphrase\n"
-"  when the first client connects. You can work around this by connecting "
-"making the first client connection to your server\n"
-"  (or by clearing the password for your transport key)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:487
-msgid ""
-"For your server to be accessible for others over I2P, you will need to "
-"create a\n"
-"  server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" "
-"profile."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:497
-msgid ""
-"Debian (amongst other distributions) has integrated Monotone into their\n"
-"  framework of daemons/services. Although Monotone servers can still be "
-"run\n"
-"  \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may"
-" be more straightforward."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:505
-msgid ""
-"Permissions are granted by editing the files\n"
-"  /etc/monotone/read-permissions and\n"
-"  /etc/monotone/write-permissions. You'll also need to edit\n"
-"  /etc/default/monotone to enable monotone to start at boot "
-"or to\n"
-"  customize the host, port, or database location."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
-msgid ""
-"\n"
-"So you want to start work on I2P? Great!\n"
-"Here's a quick guide to getting started\n"
-"on contributing to the website or the software, doing development or "
-"creating translations."
-msgstr ""
-"\n"
-"¿Entonces, quiere empezar a trabajar en I2P? ¡Bien! Aquí tiene una "
-"pequeña guía de como empezar contribuyendo, con la web o con el software,"
-" programando código o traduciendo."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
-#, python-format
-msgid ""
-"\n"
-"Not quite ready for coding?\n"
-"Try getting involved first."
-msgstr ""
-"\n"
-"¿Aún no está listo para programar?  Pruebe primero a involucrarse en el proyecto."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
-msgid "Basic study"
-msgstr "Estudios básicos"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
-msgid "Getting the I2P code"
-msgstr "Obteniendo el código de I2P"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
-msgid "Building I2P"
-msgstr "Compilando I2P"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
-msgid "Development ideas"
-msgstr "Ideas para desarrollar"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
-msgid "Making the results available"
-msgstr "Haciendo que los resultados estén disponibles"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
-msgid "Get to know us!"
-msgstr "¡Conózcanos!"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
-msgid "Translations"
-msgstr "Traducciones"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
-msgid "Tools"
-msgstr "Herramientas"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
-msgid ""
-"Basic development on the I2P router or the embedded applications uses "
-"Java as the main development language.\n"
-"If you don't have experience with Java, you can always have a look at Thinking in Java."
-msgstr ""
-"El desarrollo básico del ruter de I2P y de las aplicaciones del núcleo "
-"utilizan Java como lenguaje de programación. Si no tiene experiencia con "
-"Java, siempre puede echarle un ojo a Thinking in Java."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
-#, python-format
-msgid ""
-"Study the how intro,\n"
-"the other \"how\" documents,\n"
-"the tech intro,\n"
-"and associated documents.\n"
-"These will give you a good overview of how I2P is structured and what "
-"different things it does."
-msgstr ""
-"Estudie la introducción de cómo, los otros \"como\" documentos, la a "
-"href=\"%(techintro)s\">introducción técnica, y los documentos "
-"asociados. Esto le dará una buena vista general de como está estructurado"
-" y de qué otras cosas hace I2P."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
-msgid ""
-"For development on the i2p router or the embedded applications,\n"
-"get the monotone source repository installed - short instructions:"
-msgstr ""
-"Para programar la consola de I2P o las aplicaciones principales, instale "
-"el código del repositorio de monotone - instrucciones rápidas:"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
-msgid ""
-"Install monotone.\n"
-"Monotone is a version control system.\n"
-"We use it because it allows us to keep track of who does what changes to "
-"the source code (and for a lot of complicated things, but 'keeping track "
-"of changes' is the basic idea)."
-msgstr ""
-"Instale monotone. Monotone es un "
-"sistema de control de versiones. Lo utilizamos porque nos permite llevar "
-"el control de quien cambia el código (y muchas cosas complicadas más, "
-"pero el control de los cambios es el motivo principal)"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
-msgid ""
-"Skim over the monotone tutorial,"
-" to make sure you understand the concepts."
-msgstr ""
-"Eche una ojeada al tutorial de "
-"monotone para asegurarse de que entiende los conceptos"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
-msgid ""
-"If you want to remain anonymous, you need to do an additional step, to "
-"set up a connection to a monotone server over I2P:"
-msgstr ""
-"Si desea permanecer anónimo necesita un paso adicional, configurar una "
-"conexión al servidor de monotone a través de I2P:"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
-#, python-format
-msgid ""
-"Enable the i2ptunnel client tunnel on port "
-"8998 pointing to mtn.i2p2.i2p."
-msgstr ""
-"Habilite el túnel cliente i2ptunnel en e "
-"puerto 8998 apuntando a mtn.i2p2.i2p."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
-msgid ""
-"Pick a directory where you want to put all your I2P files, and create a "
-"monotone database:"
-msgstr ""
-"Elija un directorio donde quiera poner todos los archivos de I2P, y cree "
-"una base de datos para monotone:"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
-msgid ""
-"Define the trust list by creating ~/.monotone/monotonerc (or"
-" _MTN/monotonerc in the i2p.i2p workspace) with the "
-"following contents:"
-msgstr ""
-"Defina la lista de confianza creando code>~/.monotone/monotonerc             "
-"(o _MTN/monotonerc en el área de trabajo de i2p.i2p ) con el"
-" siguiente contenido:"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
-#, python-format
-msgid ""
-"Copy and paste the developer's commit keys "
-"into a new file (e.g. keys.txt) in the same directory\n"
-"  that i2p.mtn is in. Import the keys into your database "
-"with 
                  mtn -d i2p.mtn read < keys.txt
            "
-msgstr ""
-"Copie y pegue las claves de los "
-"desarrolladores en un nuevo archivo (por ejemplo "
-"keys.txt) en el mismo directorio que está "
-"i2p.mtn. Importe las claves a su base de datos con "
-"
             mtn -d i2p.mtn read < keys.txt
            "
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:76
-msgid ""
-"Pull the I2P sources to your machine. This may take a long time, "
-"especially if you are doing this over I2P!"
-msgstr ""
-"Descargue el código de I2P a su ordenador. ¡Puede tardar bastante, sobre "
-"todo si lo hace a través de I2P!"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:78
-msgid "Anonymously:"
-msgstr "Anónimamente:"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:81
-msgid "Non-anonymously:"
-msgstr "Sin anonimato:"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:83
-msgid ""
-"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn"
-".i2p-projekt.de."
-msgstr ""
-"También puede descargarlo desde mtn.i2p-projekt.de además de "
-"'mtn.i2p2.de'."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:90
-msgid ""
-"All the sources are now present on your machine, in the database file. To"
-" make them available in a directory, you need to check them out:"
-msgstr ""
-"Todo el código esta ahora en su ordenador, en al archivo de la base de "
-"datos. Para hacerlo accesible en el directorio necesita ejecutar:"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:92
-msgid ""
-"The above command creates a directory i2p.i2p, which contains all of the "
-"I2P sources."
-msgstr ""
-"El comando anterior crea el directorio i2p.i2p, el cual contiene todo el "
-"código de I2P."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:96
-msgid "Remarks"
-msgstr "Notas"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:97
-msgid ""
-"\n"
-"To download the website files instead of the I2P source files, use "
-"'i2p.www' instead of 'i2p.i2p'."
-msgstr ""
-"\n"
-"Para descargar la página web en vez del código use 'i2p.www' en vez de "
-"'i2p.i2p'."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:100
-msgid ""
-"The initial pull may take several hours using the tunnel.\n"
-"If it fails after a partial pull, simply rerun it, it will start where it"
-" left off.\n"
-"If you are in a hurry, use the non-anonymous access."
-msgstr ""
-"La descarga inicial puede tardar varias horas. Si falla después de una "
-"descarga parcial, simplemente vuelva a ejecutar el mismo comando y "
-"empezará donde lo dejó. Si tiene prisa use el sistema de acceso no "
-"anónimo"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:105
-#, python-format
-msgid ""
-"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn."
-msgstr ""
-"Una lista completa de servidores de descarga, incluyendo i2p.i2p y "
-"i2p.www puede encontrarse en viewmtn."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
-#, python-format
-msgid ""
-"A long explanation about using monotone is available on the monotone page."
-msgstr ""
-"Una explicación completa de cómo usar monotone está disponible en la web de monotone."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
-#, python-format
-msgid ""
-"To compile the code, you need the Sun Java Development Kit 6 or higher, "
-"or equivalent JDK\n"
-"(Sun JDK 6 strongly recommended) and\n"
-"Apache ant\n"
-"version 1.7.0 or higher.\n"
-"If you go are working on the main I2P code, you can go into the i2p.i2p "
-"directory and run 'ant' to see the build options."
-msgstr ""
-"Para compilar el código necesita Sun Java Development Kit 6 o mayor, o el"
-" JDK equivalente (Sun JDK 6 recomendado) y Apache ant versión 1.7.0 o mayor. Si"
-" va a trabajar en al código principal de I2P puede entrar al directorio "
-"i2p.i2p y ejecutar 'ant' para ver las opciones de compilación."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
-msgid ""
-"To build or work on console translations, you need\n"
-"the xgettext, msgfmt, and msgmerge tools from the\n"
-"GNU gettext package."
-msgstr ""
-"Para trabajar en la traducción de la consola necesita las herramientas "
-"gettext, msgfmt, y msgmerge del paquete GNU gettext."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
-#, python-format
-msgid ""
-"For development on new applications,\n"
-"see the application development guide."
-msgstr ""
-"Para programar nuevas aplicaciones vea la guía de "
-"desarrollo de aplicaciones."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
-#, python-format
-msgid ""
-"See zzz's TODO lists,\n"
-"this website's TODO list or\n"
-"Trac\n"
-"for ideas."
-msgstr ""
-"Para una lista de ideas vea la lista "
-"de PORHACER de zzz, la lista de PORHACER de esta"
-" web o el Trac."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
-#, python-format
-msgid ""
-"See the bottom of the licenses page "
-"for\n"
-"commit privilege requirements. You need these to put code into i2p.i2p "
-"(not required for the website!)."
-msgstr ""
-"Mira en la parte de abajo de  la página "
-"de licencias para conocer los requisitos. Los necesita para poder "
-"aportar código a i2p.i2p (¡pero no para la página web!)"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
-msgid "Short version of how to generate and use keys if you plan to commit:"
-msgstr ""
-"Versión corta de cómo generar y usar las claves si tiene planeado hacer "
-"aportes:"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
-msgid "use an empty passphrase"
-msgstr "use una contraseña vacía, sin contraseña"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
-msgid "enter a passphrase"
-msgstr "escriba una contraseña"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
-#, python-format
-msgid ""
-"send this to a mtn repo operator to get "
-"push privileges"
-msgstr ""
-"envíe esto al administrador del "
-"repositorio de mtn para tener permisos para aportar:"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
-#, python-format
-msgid ""
-"send this to a release manager to get "
-"commit privileges - not required for website"
-msgstr ""
-"envíe esto al encargado de las versiones"
-" para obtener los permisos para aportar - no se requiere para la página "
-"web"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
-msgid "check in with this key"
-msgstr "loguee con esta clave"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
-msgid "push with this key"
-msgstr "envíe los cambios al servidor con esta clave"
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
-#, python-format
-msgid "Long version: see the monotone page."
-msgstr "Versión completa: vea la web de monotone."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
-#, python-format
-msgid ""
-"The developers hang around on IRC. They can be reached on the Freenode "
-"network, OFTC, and on the I2P internal networks. The usual place to look "
-"is #i2p-dev. Join the channel and say hi!\n"
-"We also have additional guidelines for regular"
-" developers."
-msgstr ""
-"Los desarrolladores suelen estar en el IRC. Puede contactar con ellos en "
-"la red Freenode, OFTC, y en la en el IRC de I2P. El lugar usual es #i2p-"
-"dev. ¡Únase al canal y diga hola!. También hay guías adicionales para desarrolladores."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
-#, python-format
-msgid ""
-"Website and router console translators: See the New Translator's Guide\n"
-"for next steps."
-msgstr ""
-"Traductores de la consola del ruter y la página web: Vea la guía de nuevos traductores."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
-msgid ""
-"I2P is open source software that is mostly developed using open sourced\n"
-"toolkits. The I2P project recently acquired a license for the YourKit "
-"Java\n"
-"Profiler. Open source projects are eligible to receive a free license "
-"provided\n"
-"that YourKit is referenced on the project web site. Please get in touch "
-"if you\n"
-"are interested in profiling the I2P codebase."
-msgstr ""
-"I2P es una aplicación de código libre y es desarrollada usando "
-"herramientas libres. El proyecto I2P ha adquirido recientemente una "
-"licencia para YourKit Java Profiler. Los proyectos libres pueden obtener "
-"una licencia gratis mientras se haga referencia a YourKit en las webs del"
-" proyecto. Por favor pónganse en contacto su está interesado en la "
-"depuración y optimización del código base de I2P."
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
-#, python-format
-msgid ""
-"YourKit is kindly supporting open source projects with its full-featured "
-"Java Profiler.\n"
-"YourKit, LLC is the creator of innovative and intelligent tools for "
-"profiling\n"
-"Java and .NET applications. Take a look at YourKit's leading software "
-"products:\n"
-"YourKit Java Profiler and\n"
-"YourKit .NET Profiler."
-msgstr ""
-"YourKit está apoyando amablemente a los proyectos  libres con el Java "
-"Profiler completo. LLC es el creador de inteligentes e innovadoras "
-"herramientas para el desarrollo de aplicaciones JAVA y .NET. Échele un "
-"ojo a los productos principales de YourKit: YourKit "
-"Java Profiler y YourKit .NET Profiler."
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
-msgid "Here's a very quick guide to getting started."
-msgstr "Aquí hay a guía rápida para comenzar."
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
-msgid "How to Translate the Website"
-msgstr "Como traducir la página web"
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
-#, python-format
-msgid ""
-"Translation of the website is done with .po files. The easiest way by far"
-" to\n"
-"translate the website is to sign up for an account at \n"
-"Transifex and request to join a translation"
-" team. \n"
-"Alternatively it can be done \"the old way\" as outlined below."
-msgstr ""
-"La traducción de las páginas web se hace con archivos .po. La forma mas "
-"fácil con diferencia para traducir una página web es crearse una cuenta "
-"en Transifex y solicitar unirse aun grupo "
-"de traducción. Alternativamente se puede hacer a la \"forma antigua \" "
-"como se muestra debajo."
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
-msgid "Preparation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
-#, python-format
-msgid ""
-"Come to #i2p-dev on irc and talk to people.\n"
-"Claim the language -\n"
-"To make sure other coworkers don't bump onto the files you are working "
-"on,\n"
-"please update the translation status on this wiki "
-"page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
-#, python-format
-msgid ""
-"Follow the new developer's guide,\n"
-"Including the installation of monotone,\n"
-"checking out i2p.www branch, and generate your own monotone keys.\n"
-"It is not required that you sign a dev agreement."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
-msgid ""
-"Create files:\n"
-"If the file for your language does not exist yet:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
-msgid ""
-"Run \"./extract-messages.sh\" to generate a "
-"messages.pot in the base directory.\n"
-"Edit the header of this file, then run \"./init-new-po.sh "
-"locale\" to generate the file\n"
-"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
-"\"mtn add\" this file."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
-msgid ""
-"Edit i2p2www/pages/global/lang.html and add a line for your "
-"language (copy an existing line)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
-msgid ""
-"Add a flag image file to i2p2www/static/images/flags/ for "
-"the menu (copy from the router)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
-msgid ""
-"Edit files:\n"
-"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
-"To work with .po files efficiently, you may wish to use POEdit"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
-msgid ""
-"Check in:\n"
-"\"mtn pull\", \"mtn update\". Then check in by "
-"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
-"This collects the diff info of your changed file into your local repo. "
-"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
-"i2p.i2p\".\n"
-"This synchronizes your local repo with the repo on the target machine."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
-msgid "Repeat. Check in often. Don't wait until it is perfect."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
-msgid "How to Translate the Router Console"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
-#, python-format
-msgid ""
-"The easiest way by far to translate the router console is to sign up for "
-"an account at \n"
-"Transifex and request to join a translation"
-" team. \n"
-"Alternatively it can be done \"the old way\" as outlined below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
-#, python-format
-msgid ""
-"Follow the new developer's guide,\n"
-"including the installation of monotone and the gettext tools,\n"
-"checking out i2p.i2p branch, and generate your own monotone keys."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
-msgid "Generate your own gpg key and sign the dev agreement."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
-msgid ""
-"Before starting a console translation, better help translate some i2p "
-"webpages first.\n"
-"At least an i2p homepage in your language would be great."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
-msgid ""
-"What to translate:\n"
-"There are about 15 files in the i2p.i2p branch that needs translation:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
-msgid ""
-"Where xx is your language code like fr/de/ch/zh/...\n"
-"There may be or may not be files with your lang code. If not, you can "
-"create your own. by copying and renaming other language files you know "
-"with your own lang code."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
-msgid ""
-"Create files:\n"
-"If the file for your language does not exist yet, copy another language "
-"file to a new file foo_xx.bar for your language.\n"
-"Then \"mtn add\" the file.\n"
-"After creating a .po file, edit the headers. Then run \"ant "
-"distclean poupdate\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
-msgid ""
-"Start to work:\n"
-"Edit the HTML files with any text editor.\n"
-"Be sure not to use an editor in HTML mode that reformats everything.\n"
-"To work with .po files efficiently, you may wish to use POEdit"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
-msgid ""
-"As you can see, it's not that difficult.\n"
-"If you have questions about the meaning of the terms in the console, ask "
-"in #i2p-dev on IRC."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
-msgid ""
-"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
-"and html, etc.? Why can't I just do a translation and email it to you?"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
-msgid "A: Several reasons:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
-#, python-format
-msgid ""
-"You might be interested in translating via Transifex. Request to join a "
-"translation team here."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
-msgid ""
-"We don't have anybody who has time to accept manual contributions and "
-"submit them to our source control system on your behalf. Even if we did, "
-"it doesn't scale."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
-msgid ""
-"Maybe you are thinking translation is a one-step process. It isn't. You "
-"can't do it all at once. You will make mistakes. You need to test it and "
-"tweak it to make it look right before you submit it. Developers "
-"will update or add to the English text, thus requiring a translation "
-"update."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
-msgid ""
-"Having translators use a source control system directly provides "
-"authentication and accountablility - we know who is doing what, and we "
-"can track changes, and revert them if necessary."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
-msgid ""
-".po files are not difficult. If you don't want to work directly with "
-"them, we recommend 'poedit'."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
-msgid ""
-"HTML files are not difficult. Just ignore the html stuff and translate "
-"the text."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
-msgid ""
-"Installing and using monotone is not that difficult. Several of the "
-"translators and other contributors to I2P are non-programmers, and they "
-"use monotone regularly. Monotone is simply a source control system, it is"
-" not about \"coding\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
-msgid ""
-"Our items to translate are not \"documents\". They are html files and po "
-"files, with a specific format and character encoding (UTF-8) that must be"
-" maintained, and not corrupted by email programs or other methods of "
-"transfer."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
-msgid ""
-"We looked at 'pootle' as a front-end for translators. It didn't work "
-"well, needed an administrator, and a pootle-based process would suffer "
-"from a number of the above flaws."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
-msgid ""
-"In summary:\n"
-"Yes, we know it is somewhat of a hurdle to get started. It's really the "
-"only possible way we can do it. Give it a try, it really isn't that hard."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
-msgid "More Information"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
-#, python-format
-msgid ""
-"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
-msgstr ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 "Lista de RateStat"
-
-#: 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 ""
-"La lista fue obtenida usando el siguiente comando en el directorio "
-"principal de la rama 2p.i2p:"
-
-#: i2p2www/pages/site/misc/ratestats.html:10
-msgid "All options aren't needed, but it works."
-msgstr "No son necesarias todas las opciones, pero funciona."
-
-#: 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 ""
-"El código fuente de i2p es mantenido en varios repositorios distribuidos "
-"de monotone. Vea la Web de "
-"Monotone para mas información sobre monotone. Vea este foro sobre i2p y "
-"monotone para obtener mas información de como comenzar y descargar el"
-" código fuente anónimamente. También hay una guía rápida en la web de nuevos desarrolladores."
-
-#: 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 ""
-"Si desea obtener el código fuente no anónimamente, descargue desde el "
-"servidor publico mtn.welterde.de.\n"
-"La rama del código fuente de i2p es \"i2p.i2p\"."
-
-#: i2p2www/pages/site/misc/transition-guide.html:21
-msgid "Guide"
-msgstr "Guía"
-
-#: i2p2www/pages/site/misc/transition-guide.html:22
-msgid ""
-"\n"
-"The following is a detailed guide by Complication."
-msgstr ""
-"\n"
-"Lo siguiente es una guía detallada hecha por Complication."
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:2
-msgid "How to Upgrade from 0.6.1.30 and Earlier"
-msgstr "Como actualizar desde la versión 0.6.1.30 y anteriores."
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:6
-msgid "Upgrading from 0.6.1.30 and Earlier Releases"
-msgstr "Actualizando desde 0.6.1.30 y versiones anteriores."
-
-#: 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 ""
-"Desde que el programador principal de i2p se "
-"ausentó sin avisar, AWOL, no tenemos su clave de actualización "
-"firmada o acceso a www.i2p[.net] o dev.i2p[.net]. Complication y zzz han "
-"generado nuevas claves de firmado, y ellos y Amiga proveen alojamiento a "
-"los archivos de actualización. Estos cambios tienen que ser configurados "
-"en su ruter para que tengan efecto. "
-
-#: 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 ""
-"Haga los siguientes cambios de configuración y su ruter instalará "
-"automáticamente la última versión"
-
-#: 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 ""
-"Recomendamos el proceso automático ya que verificará la clave del archivo"
-" de actualización firmado. Si no hace estos cambios, puede descargar "
-"manualmente el archivo i2pupdate.zip de la página de descargas."
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:34
-#, python-format
-msgid "Change the News URL to: %(url)s"
-msgstr "Cambie el enlace de noticias a: %(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 ""
-"Seleccione una de las siguientes enlaces de actualización aleatoriamente "
-"e introdúzcalo dentro de la casilla Update URL:"
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:43
-msgid "Check the box \"Update through the eepProxy?\""
-msgstr "Active la casilla \"Actualizar a través del eepProxy?\""
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:44
-msgid "Click \"Save\""
-msgstr "Pulse \"Guardar\""
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:51
-msgid "Add the following line:"
-msgstr "Añada la siguiente línea:"
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:55
-msgid "Click \"Apply\""
-msgstr "Pulse \"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 ""
-"Ahora estas listo para recibir automáticamente el archivo de "
-"actualización, ya sea configurando su política de actualizaciones a "
-"\"descargar e instalar\" o pulsando en el enlace \"actualización "
-"disponible\" cuando aparezca."
-
-#: 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 ""
-"Si deseas verificar las claves de actualización de confianza, se "
-"encuentran también subidas y firmadas aquí. "
-"Gracias por su ayuda durante la transición. Por favor, para pedir ayuda "
-"contacte con nosotros en #I2P."
-
-#: i2p2www/pages/site/research/index.html:2
-msgid "Academic Research"
-msgstr "Investigación académica"
-
-#: i2p2www/pages/site/research/index.html:4
-msgid ""
-"Academic research and analysis of I2P is an important part of ensuring "
-"that the software and network performs as expected and is safe for users "
-"in hostile environments."
-msgstr ""
-"El análisis y la investigación académica de I2P es una parte importante "
-"para asegurar que la aplicación y la red funcionan como deben y es segura"
-" para los usuarios en ambientes hostiles."
-
-#: i2p2www/pages/site/research/index.html:8
-msgid ""
-"I2P can be run as a separate test network by controlling the locations "
-"that a new router reseeds from so that it only finds other test routers. "
-"Additionally, the router can be run on its own in a virtual network mode "
-"to enable testing the router in isolation; to enable this mode, add "
-"i2p.vmCommSystem=true to the router.config before starting."
-msgstr ""
-"I2P puede ser ejecutado como una red aparte para  pruebas controlando la "
-"localización desde la que el nuevo ruter resiembra, con lo cual solo "
-"conectaría con otros ruters de pruebas. Adicionalmente el ruter se puede "
-"ejecutar él solo en una red virtual para permitir probar el ruter en "
-"aislamiento; para activar este modo, añada "
-"i2p.vmCommSystem=true en router.config antes de arrancar."
-
-#: i2p2www/pages/site/research/index.html:12
-#, python-format
-msgid ""
-"If you are planning on conducting research on the live I2P network, "
-"please contact us before you commence your "
-"testing. While we do not discourage researchers from responsibly testing "
-"their ideas on the live network, if an attack becomes apparent and we "
-"don't have any line of communication then we will end up taking "
-"countermeasures which could interfere with the test."
-msgstr ""
-"Si está planeando hacer algún estudio sobre la red de I2P online,  por "
-"favor contáctenos antes de comenzar las "
-"pruebas.  Aunque no desalentamos a los desarrolladores a probar sus ideas"
-" responsablemente en la red, si algún ataque se hace aparente y no "
-"tenemos una línea de comunicación terminaremos tomando medidas que "
-"podrían interferir con las pruebas."
-
-#: i2p2www/pages/site/research/index.html:16
-msgid "Prior Research"
-msgstr "Estudios anteriores"
-
-#: i2p2www/pages/site/research/index.html:18
-#, python-format
-msgid ""
-"A list of known published papers about I2P is available here."
-msgstr ""
-"Una lista de documentos publicados sobre I2P está disponible aquí."
-
-#: i2p2www/pages/site/research/papers.html:6
-msgid "Following are links to research papers about I2P."
-msgstr "A Continuación unos enlaces para investigar trabajos sobre I2P."
-
-#: i2p2www/pages/site/research/papers.html:12
-msgid "Newest links are at the top of the page."
-msgstr "Los enlaces mas nuevos se encuentran en el encabezado de la página."
-
-#: i2p2www/pages/site/research/papers.html:17
-msgid "Papers and Research"
-msgstr "Documentos e investigación"
+"En resumen, la \"mala decisión de diseño\" parece (ya que el estudio no "
+"califica a los túneles bidireccionales de \"malos\") otra forma de decir "
+"que los túneles \"unidireccionales son inequívocamente inferiores a los "
+"túneles bidireccionales\", aunque esta conclusión no está demostrada en "
+"el estudio."
 
diff --git a/i2p2www/translations/es/LC_MESSAGES/get-involved.po b/i2p2www/translations/es/LC_MESSAGES/get-involved.po
new file mode 100644
index 00000000..ef65773e
--- /dev/null
+++ b/i2p2www/translations/es/LC_MESSAGES/get-involved.po
@@ -0,0 +1,5561 @@
+# Spanish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Adolfo Jayme Barrientos , 2013
+# Daniel Mustieles , 2013
+# m1xxy , 2011
+# olivertrash , 2013
+# strel, 2013
+# trolly, 2013
+# trolly , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-10-06 09:13+0000\n"
+"Last-Translator: trolly \n"
+"Language-Team: Spanish "
+"(http://www.transifex.com/projects/p/I2P/language/es/)\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/get-involved/donate.html:2
+#: i2p2www/pages/site/get-involved/index.html:77
+msgid "Donate"
+msgstr "Donar"
+
+#: i2p2www/pages/site/get-involved/donate.html:4
+msgid ""
+"Thank you for your interest in contributing to I2P!\n"
+"The details of how you\n"
+"can make your contribution are provided below."
+msgstr ""
+"¡Gracias por su interés en contribuir a I2P! Los detalles de como puede "
+"hacer una contribución se indican más abajo."
+
+#: i2p2www/pages/site/get-involved/donate.html:11
+#: i2p2www/pages/site/get-involved/donate.html:27
+#, python-format
+msgid ""
+"As of %(date)s, eche|on has been running a\n"
+"%(cointype)s account for the I2P project.\n"
+"If you'd like to donate using %(cointype)s, just transfer your\n"
+"desired amount of coins to the account %(account)s\n"
+"and leave eche|on a note if you'd like your donation to be\n"
+"mentioned on the I2P webpage."
+msgstr ""
+"Desde %(date)s, eche|on ha estado ejecutando una cuenta %(cointype)s para el proyecto I2P. Si quisiera "
+"donar usando \n"
+"%(cointype)s, tan solo transfiera la cantidad de moneda que desee a la \n"
+"cuenta %(account)s y deje a eche|on una nota si desea que su \n"
+"donación sea mencionada en la página web de I2P."
+
+#: i2p2www/pages/site/get-involved/donate.html:22
+#: i2p2www/pages/site/get-involved/donate.html:38
+msgid "For easy usage, use the QR code below!"
+msgstr "¡Para usarla con facilidad, utilice el código QR de debajo!"
+
+#: i2p2www/pages/site/get-involved/donate.html:44
+#, python-format
+msgid "You can donate direct via PayPal to the account \"%(account)s\"."
+msgstr "Puede donar directamente vía PayPal a las cuentas \"%(account)s\"."
+
+#: i2p2www/pages/site/get-involved/donate.html:50
+msgid "One time donation:"
+msgstr "Una sola donación:"
+
+#: i2p2www/pages/site/get-involved/donate.html:64
+msgid "Donate 10 €/month for 12 months:"
+msgstr "Donar 10 €/mes por 12 meses:"
+
+#: i2p2www/pages/site/get-involved/donate.html:72
+#: i2p2www/pages/site/get-involved/donate.html:84
+#: i2p2www/pages/site/get-involved/donate.html:96
+#: i2p2www/pages/site/get-involved/donate.html:108
+msgid "I2P donation "
+msgstr "Donación I2P"
+
+#: i2p2www/pages/site/get-involved/donate.html:78
+msgid "Donate 20 €/month for 12 months:"
+msgstr "Donar 20 €/mes durante 12 meses:"
+
+#: i2p2www/pages/site/get-involved/donate.html:90
+msgid "Donate 30 €/month for 12 months:"
+msgstr "Donar 30 €/mes durante 12 meses:"
+
+#: i2p2www/pages/site/get-involved/donate.html:102
+msgid "Donate 50 €/month for 12 months:"
+msgstr "Donar 50 €/mes durante 12 meses:"
+
+#: i2p2www/pages/site/get-involved/donate.html:117
+msgid "Flattr this"
+msgstr "Donar con "
+
+#: i2p2www/pages/site/get-involved/donate.html:122
+msgid ""
+"If you want to keep more or less anonymous, the option to send money via "
+"mail is also available. But it is less secure\n"
+"as the envelope can be lost on the way to us."
+msgstr ""
+"Si desea permanecer más o menos anónimo, puede enviar el dinero por "
+"correo. Pero es menos seguro ya que la carta puede perderse en el camino."
+
+#: i2p2www/pages/site/get-involved/donate.html:126
+#, python-format
+msgid ""
+"If you'd like to donate via  snail mail, send an email to %(email)s\n"
+" and you'll receive an email with instructions detailing how to proceed."
+msgstr ""
+"Si desea donar a través de correo caracol, snail mail, envíe un email a "
+"%(email)s y recibirá un email con las instrucciones de "
+"como debe proceder."
+
+#: i2p2www/pages/site/get-involved/donate.html:131
+#, python-format
+msgid ""
+"In the meantime, feel free to take a look at the generous donations that "
+"have been\n"
+"given in support of the I2P Project at the hall of fame."
+msgstr ""
+"Mientras tanto, puede echar una ojeada a las generosas donaciones que han"
+" sido dadas para el soporte del proyecto I2P en el salón de la fama."
+
+#: i2p2www/pages/site/get-involved/index.html:2
+msgid "Get Involved!"
+msgstr "¡Involúcrese!"
+
+#: i2p2www/pages/site/get-involved/index.html:4
+msgid "We need your help!"
+msgstr "¡Necesitamos su ayuda!"
+
+#: i2p2www/pages/site/get-involved/index.html:5
+msgid ""
+"To get involved, please feel free to join us on the #i2p IRC channel (on\n"
+"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or "
+"irc.postman.i2p)."
+msgstr ""
+"Para unirse al proyecto, por favor únase a nosotros en el canal #i2p del "
+"IRC (en irc.freenode.net, o dentro de I2P en irc.freshcoffee.i2p o "
+"irc.postman.i2p)."
+
+#: i2p2www/pages/site/get-involved/index.html:9
+#, python-format
+msgid ""
+"If you're interested in joining our team, please"
+" get in\n"
+"touch as we're always looking for eager contributors!"
+msgstr ""
+"¡Si está interesado en unirse a nuestro equipo, "
+"por favor póngase en contacto con nosotros, ya que siempre estamos "
+"buscando ayudantes entusiastas!"
+
+#: i2p2www/pages/site/get-involved/index.html:13
+msgid ""
+"We need help in many areas, and you don't need to know Java to "
+"contribute!\n"
+"Here's a list to help you get started!"
+msgstr ""
+"¡Necesitamos ayuda en muchas áreas, y no necesita saber Java para "
+"contribuir! ¡Aquí hay una lista para ayudarle a decidirse!"
+
+#: i2p2www/pages/site/get-involved/index.html:18
+msgid "Spread the Word!"
+msgstr "¡Extienda la Palabra!"
+
+#: i2p2www/pages/site/get-involved/index.html:19
+msgid ""
+"Tell people about I2P on forums, blogs, and comments to articles.\n"
+"Fix up the Wikipedia article about I2P in your language.\n"
+"Tell your friends."
+msgstr ""
+"Háblele a la gente  sobre I2P en foros, blogs y comentarios de artículos."
+" Mejore la entrada en la Wikipedia sobre I2P en su idioma. Dígaselo a sus"
+" amigos."
+
+#: i2p2www/pages/site/get-involved/index.html:24
+msgid "Testing"
+msgstr "Pruebas"
+
+#: i2p2www/pages/site/get-involved/index.html:25
+#, fuzzy, python-format
+msgid ""
+"Run the latest builds from monotone\n"
+"and report results on #i2p or as bugs on Trac."
+msgstr ""
+"Ejecute las últimas versiones en monotone y "
+"reporte los resultados en #i2p como errores en el Trac."
+
+#: i2p2www/pages/site/get-involved/index.html:30
+msgid "Documentation"
+msgstr "Documentación"
+
+#: i2p2www/pages/site/get-involved/index.html:31
+msgid ""
+"Help fix the parts of the website that are outdated or incomplete.\n"
+"Translate pages into other languages."
+msgstr ""
+"Ayude a mejorar las partes de la web que están anticuadas o incompletas. "
+"Traduzca las páginas a otros idiomas."
+
+#: i2p2www/pages/site/get-involved/index.html:35
+msgid "Pictures"
+msgstr "Imágenes"
+
+#: i2p2www/pages/site/get-involved/index.html:36
+msgid "Make some more pictures, fix the old ones on the website"
+msgstr "Cree más imágenes, mejore las viejas de la web"
+
+#: i2p2www/pages/site/get-involved/index.html:39
+msgid "Content"
+msgstr "Contenido"
+
+#: i2p2www/pages/site/get-involved/index.html:40
+msgid "Make an eepsite! Add some content! Contribute to the community!"
+msgstr "¡Cree una eepsite! ¡Añádale contenido! ¡Contribuya a la comunidad!"
+
+#: i2p2www/pages/site/get-involved/index.html:43
+msgid "Services"
+msgstr "Servicios"
+
+#: i2p2www/pages/site/get-involved/index.html:44
+msgid ""
+"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n"
+"a naming service, a search engine, an eepsite monitor... many of these\n"
+"aren't that hard."
+msgstr ""
+"Ejecute algún servicio en su eepsite. Puede ser un proxy, un foro, un "
+"tracker, un servidor de dominios, una motor de búsquedas, un monitor de "
+"eepsites... muchos de estos no son tan difíciles."
+
+#: i2p2www/pages/site/get-involved/index.html:49
+msgid "Applications"
+msgstr "Aplicaciones"
+
+#: i2p2www/pages/site/get-involved/index.html:50
+#, python-format
+msgid ""
+"Write or port applications for I2P! There's some guidelines and\n"
+"a list of ideas on the applications page."
+msgstr ""
+"¡Escriba o porte aplicaciones para I2P! Hay algunas guías y una lista de "
+"ideas en la página de aplicaciones."
+
+#: i2p2www/pages/site/get-involved/index.html:54
+msgid "Coding"
+msgstr "Programando"
+
+#: i2p2www/pages/site/get-involved/index.html:55
+#, fuzzy, python-format
+msgid ""
+"There's plenty to do if you know Java or are ready to learn.\n"
+"Check for open tickets on Trac\n"
+"or the TODO list on %(zzz)s for\n"
+"some ideas on where to start.\n"
+"See the new developer's guide for details."
+msgstr ""
+"Hay mucho que hacer si sabe Java o está listo para aprender. Busque "
+"entradas abiertas en el Trac o "
+"en la lista TODO en %(zzz)s para saber "
+"donde empezar o ver algunas ideas. Vea la guía de"
+" nuevos desarrolladores para más detalles."
+
+#: i2p2www/pages/site/get-involved/index.html:64
+msgid "Translation"
+msgstr "Traducciones"
+
+#: i2p2www/pages/site/get-involved/index.html:65
+#, python-format
+msgid ""
+"Help translate the website and the software into your language.\n"
+"See the new translator's guide for details."
+msgstr ""
+"Ayude a traducir la página web y las aplicaciones a su lenguaje. Vea la "
+"guía de nuevos traductores para más "
+"información."
+
+#: i2p2www/pages/site/get-involved/index.html:69
+msgid "Analysis"
+msgstr "Análisis"
+
+#: i2p2www/pages/site/get-involved/index.html:70
+#, python-format
+msgid ""
+"Study or test the code to look for vulnerabilities.\n"
+"Both anonymity vulnerabilities from the various\n"
+"threat models,\n"
+"and DOS and other weaknesses due to securities holes,\n"
+"need researching."
+msgstr ""
+"Estudie o pruebe el código buscando vulnerabilidades. Se necesita "
+"estudiar tanto las vulnerabilidades del anonimato de varios modelos de amenazas, como los ataques DOS y "
+"otras debilidades debidas a errores en la seguridad."
+
+#: i2p2www/pages/site/get-involved/roadmap.html:2
+msgid "Roadmap"
+msgstr "Hoja de ruta"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:7
+msgid ""
+"Include some seed data in the distribution so a central reseed location "
+"isn't required?"
+msgstr ""
+"¿Asegurarnos de que I2P en la instalación automáticamente se una a la red"
+" y así no haría falta ninguna localización central para esto?"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:10
+#, python-format
+msgid ""
+"Reachability Mapping / handle peers partially reachable / enhanced restricted routes"
+msgstr ""
+"Mapeado de accesibilidad / manejar los pares parcialmente accesibles / "
+"mejorar los ruters "
+"restringidos"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:13
+msgid "Improve help pages and website"
+msgstr "Mejorar las páginas de ayuda y la página web."
+
+#: i2p2www/pages/site/get-involved/roadmap.html:14
+msgid "More translations"
+msgstr "Más traducciones"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:15
+msgid "SSU disconnect message"
+msgstr "Mensaje de desconexión SSU"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:16
+msgid "Iterative floodfill lookups"
+msgstr "Búsquedas iterativas en el algoritmo de relleno, \"floodfill\""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:21
+msgid "Full review of anonymity issues and other vulnerabilities"
+msgstr "Examen completo de las vulnerabilidades y problemas de anonimato."
+
+#: i2p2www/pages/site/get-involved/roadmap.html:22
+msgid ""
+"Reduce memory usage, remove debugging overhead, make it run better on "
+"slow and embedded machines"
+msgstr ""
+"Reducción del uso de memoria, eliminar el gasto superfluo de la "
+"depuración, hacer que corra más ligero en hardware pequeño y lento. "
+
+#: i2p2www/pages/site/get-involved/roadmap.html:25
+msgid "Docs"
+msgstr "Documentación"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:30
+msgid "Full restricted routes"
+msgstr "Rutas restringidas"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:35
+msgid "Tunnel mixing and padding"
+msgstr "Mezclado y relleno de los túneles"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:36
+msgid "User defined message delays"
+msgstr "Mensajes con el retraso definido por los usuarios"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:39
+#, python-format
+msgid ""
+"Please see the TODO list for more detailed info "
+"about some of these tasks."
+msgstr ""
+"Por favor, vea la lista TODO , por hacer, para "
+"obtener información mas detallada sobre estas tareas."
+
+#: i2p2www/pages/site/get-involved/todo.html:2
+msgid "To Do List"
+msgstr "Por hacer"
+
+#: i2p2www/pages/site/get-involved/todo.html:4
+msgid "I2P Project Targets"
+msgstr "Objetivos del proyecto I2P"
+
+#: i2p2www/pages/site/get-involved/todo.html:5
+#, python-format
+msgid ""
+"Below is a more detailed (yet still incomplete) discussion of the major "
+"areas\n"
+"of future development on the core I2P network, spanning the plausibly "
+"planned\n"
+"releases. This does not include stego transports, porting to wireless "
+"devices,\n"
+"or tools to secure the local machine, nor does it include client "
+"applications\n"
+"that will be essential in I2P's success. There are probably other things "
+"that\n"
+"will come up, especially as I2P gets more peer review, but these are the "
+"main\n"
+"'big things'. See also the roadmap. Want to "
+"help?\n"
+"Get involved!"
+msgstr ""
+"Más abajo hay una discusión detallada (aunque aún no completa) de las "
+"áreas más importantes del futuro desarrollo del núcleo de I2P, que abarca"
+" los posibles planes de desarrollo. Esto no incluye transporte oculto, "
+"portarlo a dispositivos Wireless o herramientas para asegurar la máquina "
+"local, tampoco incluye otras aplicaciones cliente que serían esenciales "
+"para el éxito de I2P. Probablemente aparecerán otros temas, especialmente"
+" si I2P recibe mas atención, pero estas son ls 'cosas importantes'. Vea "
+"también la hoja de ruta. ¿Quiere ayudar? ¡Únete!"
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:54
+msgid "Core functionality"
+msgstr "Funcionamiento del núcleo."
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:52
+msgid "link"
+msgstr "enlace"
+
+#: i2p2www/pages/site/get-involved/todo.html:18
+#: i2p2www/pages/site/get-involved/todo.html:57
+msgid "NAT/Firewall bridging via 1-hop restricted routes"
+msgstr "Puenteando el NAT/cortafuegos a través de ruters restringidos de 1 salto"
+
+#: i2p2www/pages/site/get-involved/todo.html:21
+#: i2p2www/pages/site/get-involved/todo.html:130
+msgid "High degree transport layer with UDP, NBIO, or NIO"
+msgstr "Capa de transporte de alto nivel con UDP, NBIO, o NIO"
+
+#: i2p2www/pages/site/get-involved/todo.html:24
+#: i2p2www/pages/site/get-involved/todo.html:218
+msgid "NetworkDB and profile tuning and ejection policy for large nets"
+msgstr ""
+"Base de datos de la red, NetworkDB, y ajustes del perfil y política de "
+"expulsión para grandes redes. "
+
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:242
+msgid "Security / anonymity"
+msgstr "Seguridad / anonimato"
+
+#: i2p2www/pages/site/get-involved/todo.html:30
+#: i2p2www/pages/site/get-involved/todo.html:245
+msgid ""
+"Per-hop tunnel id & new permuted TunnelVerificationStructure "
+"encryption"
+msgstr ""
+"Id por salto de túnel & nuevo cifrado permutado de la estructura de "
+"verificación del túnel, TunnelVerificationStructure"
+
+#: i2p2www/pages/site/get-involved/todo.html:33
+#: i2p2www/pages/site/get-involved/todo.html:295
+msgid "Strict ordering of participants within tunnels"
+msgstr "Orden estricto de los participantes dentro de los túneles"
+
+#: i2p2www/pages/site/get-involved/todo.html:36
+msgid "Randomly permuted tunnel lengths"
+msgstr "Tamaño de los túneles aleatorio."
+
+#: i2p2www/pages/site/get-involved/todo.html:39
+#: i2p2www/pages/site/get-involved/todo.html:357
+msgid "Full blown n-hop restricted routes with optional trusted links"
+msgstr ""
+"Mejor personalización de los ruters y un mejor control de los ruters "
+"usados."
+
+#: i2p2www/pages/site/get-involved/todo.html:42
+#: i2p2www/pages/site/get-involved/todo.html:376
+msgid "Hashcash for routerIdentity, destination, and tunnel request"
+msgstr ""
+"Añadir Hashcash a la identidad del ruter, destinación y solicitud de "
+"respuesta."
+
+#: i2p2www/pages/site/get-involved/todo.html:45
+#: i2p2www/pages/site/get-involved/todo.html:405
+msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
+msgstr ""
+"Control avanzado del funcionamiento del ruter (procesamiento por "
+"lotes/mezclado/control de velocidad)"
+
+#: i2p2www/pages/site/get-involved/todo.html:48
+#: i2p2www/pages/site/get-involved/todo.html:442
+msgid "Stop & go mix w/ garlics & tunnels"
+msgstr ""
+"Configuración avanzada del enrutamiento de los túneles y opciones para "
+"crear túneles de usar y tirar para su uso a corto plazo."
+
+#: i2p2www/pages/site/get-involved/todo.html:52
+#: i2p2www/pages/site/get-involved/todo.html:456
+msgid "Performance"
+msgstr "Rendimiento"
+
+#: i2p2www/pages/site/get-involved/todo.html:62
+msgid "Implemented in I2P 0.6.0.6"
+msgstr "Implementado en I2P 0.6.0.6"
+
+#: i2p2www/pages/site/get-involved/todo.html:63
+msgid ""
+"The functionality of allowing routers to fully participate within the "
+"network \n"
+"while behind firewalls and NATs that they do not control requires some "
+"basic \n"
+"restricted route operation (since those peers will not be able to receive"
+" \n"
+"inbound connections). To do this successfully, you consider peers one of"
+" \n"
+"two ways:"
+msgstr ""
+"Esta capacidad permite a los ruters participar totalmente dentro de la "
+"red incluso detrás de un NAT o cortafuegos de los que no se tienen "
+"control  (ya que estos pares no podrán recibir conexiones entrantes). "
+"Para hacer esto satisfactoriamente, consideramos a los pares de estas dos"
+" formas:"
+
+#: i2p2www/pages/site/get-involved/todo.html:73
+msgid ""
+"Peers who have reachable interfaces - these peers do not need to \n"
+"do anything special"
+msgstr ""
+"Pares que tienen algún dispositivo accesible - estos pares no "
+"necesitan hacer nada especial"
+
+#: i2p2www/pages/site/get-involved/todo.html:77
+msgid ""
+"Peers who do not have reachable interfaces - these peers must "
+"build \n"
+"a tunnel pointing at them where the gateway is one of the peers they have"
+" \n"
+"established a connection with who has both a publicly reachable interface"
+" \n"
+"and who has agreed to serve as their 'introducer'."
+msgstr ""
+"Pares que no tienen dispositivos accesibles - estos pares tienen "
+"que construir un túnel hacia ellos mismos en donde la salida es uno de "
+"los pares con los que ya ha establecido una conexión y quien tiene un "
+"dispositivo accesible públicamente y ha aceptado servir como su "
+"'introductor'."
+
+#: i2p2www/pages/site/get-involved/todo.html:85
+msgid ""
+"To do this, peers who have no IP address simply connect to a few peers, \n"
+"build a tunnel through them, and publish a reference to those tunnels "
+"within \n"
+"their RouterInfo structure in the network database."
+msgstr ""
+"Para hacer esto, los pares que no tiene dirección IP simplemente se "
+"conectan a varios pares, construye un túnel a través de ellos, y publican"
+" una referencia de esos túneles dentro de la estructura RouterInfo en la "
+"base de datos dela red."
+
+#: i2p2www/pages/site/get-involved/todo.html:90
+msgid ""
+"When someone wants to contact any particular router, they first must get"
+" \n"
+"its RouterInfo from the network database, which will tell them whether "
+"they \n"
+"can connect directly (e.g. the peer has a publicly reachable interface) \n"
+"or whether they need to contact them indirectly. Direct connections occur"
+" \n"
+"as normal, while indirect connections are done through one of the "
+"published \n"
+"tunnels."
+msgstr ""
+"Cuando alguien quiere conectar con algún ruter en particular, el primero "
+"debe obtener su RouterInfo de la base de datos de la red, la que le "
+"indicará que puede conectarse directamente ( por ejemplo con un par que "
+"tiene un dispositivo accesible públicamente) o  que necesita conectar "
+"indirectamente. La conexiones directas se hacen directamente, pero las "
+"indirectas se hacen a través de los túneles publicados. "
+
+#: i2p2www/pages/site/get-involved/todo.html:98
+msgid ""
+"When a router just wants to get a message or two to a specific hidden "
+"peer, \n"
+"they can just use the indirect tunnel for sending the payload. However, \n"
+"if the router wants to talk to the hidden peer often (for instance, as "
+"part \n"
+"of a tunnel), they will send a garlic routed message through the indirect"
+" \n"
+"tunnel to that hidden peer which unwraps to contain a message which "
+"should \n"
+"be sent to the originating router. That hidden peer then establishes an \n"
+"outbound connection to the originating router and from then on, those two"
+" \n"
+"routers can talk to each other directly over that newly established "
+"direct \n"
+"connection."
+msgstr ""
+"Cuando un ruter simplemente quiere enviar un mensaje a un par oculto "
+"puede usar el túnel indirecto para enviar la información. Sin embargo, si"
+" el ruter quiere hablar con el par oculto a menudo (por ejemplo, como "
+"parte de un túnel), enviará un mensaje enrutado a través del túnel "
+"indirecto del par oculto. Entonces este par oculto establece una conexión"
+" de salida hacia el ruter original y a partir de entonces estos dos "
+"ruters puede hablar entre ellos directamente sobre la nueva conexión "
+"directa. "
+
+#: i2p2www/pages/site/get-involved/todo.html:109
+msgid ""
+"Of course, that only works if the originating peer can receive "
+"connections \n"
+"(they aren't also hidden). However, if the originating peer is hidden, "
+"they \n"
+"can simply direct the garlic routed message to come back to the "
+"originating \n"
+"peer's inbound tunnel."
+msgstr ""
+"Por supuesto esto solo funciona si el par original puede recibir "
+"conexiones (y no están también ocultas). Sin embargo, si el par original "
+"está oculto, pueden simplemente indicar la mensaje enrutado que vuelva "
+"por el túnel de entrada del par original. "
+
+#: i2p2www/pages/site/get-involved/todo.html:115
+msgid ""
+"This is not meant to provide a way for a peer's IP address to be "
+"concealed, \n"
+"merely as a way to let people behind firewalls and NATs fully operate "
+"within \n"
+"the network. Concealing the peer's IP address adds a little more work, as"
+" \n"
+"described below."
+msgstr ""
+"Esto no se ha creado para permitir que la IP de un par permanezca oculta,"
+" simplemente es una forma de permitir a la gente detrás de un NAT o "
+"cortafuegos funcionar completamente dentro de la red. Ocultar la IP de un"
+" par cuesta un poco más de trabajo, como se describe más abajo."
+
+#: i2p2www/pages/site/get-involved/todo.html:121
+msgid ""
+"With this technique, any router can participate as any part of a tunnel."
+" \n"
+"For efficiency purposes, a hidden peer would be a bad choice for an "
+"inbound \n"
+"gateway, and within any given tunnel, two neighboring peers wouldn't want"
+" \n"
+"to be hidden. But that is not technically necessary."
+msgstr ""
+"Con esta técnica cualquier ruter puede participar como una parte de un "
+"túnel. Con objeto de mejorar la eficiencia, un par oculto sería una mala "
+"elección como puerta de entrada, y dentro de un túnel dado, dos pares "
+"vecinos no desearían estar ocultos. Pero esto no es técnicamente "
+"necesario."
+
+#: i2p2www/pages/site/get-involved/todo.html:133
+msgid "Both UDP and NIO have been Implemented in I2P"
+msgstr "Ambos, UDP y NIO ya han sido implementados en I2P"
+
+#: i2p2www/pages/site/get-involved/todo.html:134
+msgid ""
+"Standard TCP communication in Java generally requires blocking socket \n"
+"calls, and to keep a blocked socket from hanging the entire system, those"
+" \n"
+"blocking calls are done on their own threads. Our current TCP transport \n"
+"is implemented in a naive fashion - for each peer we are talking to, we \n"
+"have one thread reading and one thread writing. The reader thread simply"
+" \n"
+"loops a bunch of read() calls, building I2NP messages and adding them \n"
+"to our internal inbound message queue, and the writer thread pulls "
+"messages \n"
+"off a per-connection outbound message queue and shoves the data through \n"
+"write() calls."
+msgstr ""
+"Las comunicaciones estándar TCP en java normalmente necesitan el bloqueo "
+"de llamadas al socket, y para evitar que el socket bloqueado pare todo el"
+" sistema, estos bloqueos se hacen en sus propios hilos. Nuestro sistema "
+"de transporte TCP actual está implementado de una forma sencilla - por "
+"cada par con el que hablamos, tenemos un hilo escribiendo y otro leyendo."
+" El hilo de lectura simplemente repite un puñado de llamadas read(), "
+"creando mensajes I2NP y añadiéndolos a la cola interna de mensajes de "
+"entrada, y el hilo de escritura envía mensajes hacia una cola de mensajes"
+" de salida y empuja los datos a través de llamadas write()."
+
+#: i2p2www/pages/site/get-involved/todo.html:145
+msgid ""
+"We do this fairly efficiently, from a CPU perspective - at any time, \n"
+"almost all of these threads are sitting idle, blocked waiting for "
+"something \n"
+"to do. However, each thread consumes real resources (on older Linux "
+"kernels, \n"
+"for instance, each thread would often be implemented as a fork()'ed "
+"process). \n"
+"As the network grows, the number of peers each router will want to talk \n"
+"with will increase (remember, I2P is fully connected, meaning that any \n"
+"given peer should know how to get a message to any other peer, and "
+"restricted \n"
+"route support will probably not significantly reduce the number of "
+"connections \n"
+"necessary). This means that with a 100,000 router network, each router \n"
+"will have up to 199,998 threads just to deal with the TCP connections!"
+msgstr ""
+"Desde la perspectiva del uso de CPU esto se hace bastante eficientemente "
+"- la mayoría del tiempo la mayoría de estos hilos están dormidos "
+"esperando por algo que hacer. Sin embargo, cada uno de estos hilos "
+"consume recursos (en kernels viejos de Linux, por ejemplo, cada hilo se "
+"implementa como un proceso fork()'ed). Al mismo tiempo que la red crece, "
+"el número de pares con el que se comunica un ruter aumentará (recuerde, "
+"I2P está totalmente conectado, esto quiere decir que cualquier par debe "
+"saber como enviar un mensaje a cualquier otro par). ¡Esto significa que "
+"con una red de 100.000 ruters, cada ruter tendrá 199.998 hilos "
+"simplemente para tratar con las conexiones TCP!"
+
+#: i2p2www/pages/site/get-involved/todo.html:157
+msgid ""
+"Obviously, that just won't work. We need to use a transport layer that \n"
+"can scale. In Java, we have two main camps:"
+msgstr ""
+"Obviamente esto no funcionará. Necesitamos una capa de transporte que "
+"pueda escalar. En Java tenemos dos posibles soluciones:"
+
+#: i2p2www/pages/site/get-involved/todo.html:162
+#, python-format
+msgid ""
+"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere"
+msgstr ""
+"Implementado en 2P 0.6 (\"SSU\") y documentado en en "
+"otra parte"
+
+#: i2p2www/pages/site/get-involved/todo.html:165
+msgid ""
+"Sending and receiving UDP datagrams is a connectionless operation - if \n"
+"we are communicating with 100,000 peers, we simply stick the UDP packets"
+" \n"
+"in a queue and have a single thread pulling them off the queue and "
+"shoving \n"
+"them out the pipe (and to receive, have a single thread pulling in any \n"
+"UDP packets received and adding them to an inbound queue)."
+msgstr ""
+"Enviar y recibir datagramas UDP es una operación que no necesita de "
+"conexión previa - si estamos comunicándonos con 1000.000 pares, "
+"simplemente ponemos los paquetes UDP en una cola y hacemos que un único "
+"hilo los envíe fuera de la cola hacia una tubería ( y para recibir, "
+"tenemos un único hilo tirando de cualquier paquete UDP recibido y "
+"añadiéndolos a una cola de entrada)"
+
+#: i2p2www/pages/site/get-involved/todo.html:172
+msgid ""
+"However, moving to UDP means losing the benefits of TCP's ordering, "
+"congestion \n"
+"control, MTU discovery, etc. Implementing that code will take significant"
+" \n"
+"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n"
+"a while ago I was taking some measurements in the simulator and on the \n"
+"live net, and the vast majority of messages transferred would fit easily"
+" \n"
+"within a single unfragmented UDP packet, and the largest of the messages"
+" \n"
+"would fit within 20-30 packets. As mule pointed out, TCP adds a "
+"significant \n"
+"overhead when dealing with so many small packets, as the ACKs are within"
+" \n"
+"an order of magnitude in size. With UDP, we can optimize the transport \n"
+"for both efficiency and resilience by taking into account I2P's "
+"particular \n"
+"needs."
+msgstr ""
+"Sin embargo, usar UDP significa perder los beneficios de usar el orden de"
+" TCP, el control de congestión, descubrimiento de MTU, etc. Implementar "
+"esto significaría mucho trabajo, sin embargo I2P no necesita ser tan "
+"fuerte como TCP. Hace algún tiempo estaba tomando medida en un simulador "
+"y en la red real, y la mayoría de los mensajes pueden ser transmitidas "
+"dentro de un único paquete UDP no fragmentado, y el más largo de los "
+"mensajes entraría dentro de 20-30 paquetes. Como mule indicó, TCP añade "
+"bastante gasto cuando tiene que encargarse de muchos paquetes pequeños. "
+"Con UDP, se puede optimizar el transporte para la eficiencia y la "
+"flexibilidad teniendo en cuenta las necesidades particulares de I2P."
+
+#: i2p2www/pages/site/get-involved/todo.html:185
+msgid "It will be a lot of work though."
+msgstr "Sería muchísimo trabajo por hacer."
+
+#: i2p2www/pages/site/get-involved/todo.html:188
+msgid "NIO or NBIO"
+msgstr "NIO o NBIO"
+
+#: i2p2www/pages/site/get-involved/todo.html:189
+msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")"
+msgstr "NIO fue implementada en la versión 0.6.1.22 de I2P (\"NTCP\")"
+
+#: i2p2www/pages/site/get-involved/todo.html:192
+msgid ""
+"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java"
+" \n"
+"developers to take advantage of the operating system's nonblocking IO \n"
+"capabilities - allowing you to maintain a large number of concurrent IO \n"
+"operations without requiring a separate thread for each. There is much \n"
+"promise with this approach, as we can scalable handle a large number of \n"
+"concurrent connections and we don't have to write a mini-TCP stack with \n"
+"UDP. However, the NIO packages have not proven themselves to be battle-"
+"ready, \n"
+"as the Freenet developer's found. In addition, requiring NIO support "
+"would \n"
+"mean we can't run on any of the open source JVMs like Kaffe, \n"
+"as GNU/Classpath has only "
+"limited \n"
+"support for NIO. (note: this may not be the case anymore, as there \n"
+"has been some progress on Classpath's NIO, but it is an unknown "
+"quantity)"
+msgstr ""
+"En Java 1.4 se introdujo paquetes \"I/O nuevos\", permitiendo a los "
+"desarrolladores de java usar las capacidades de los sistemas operativos "
+"sin bloquear las entradas y salidas - permitiendo tener un gran número de"
+" operaciones I/O concurrentes si necesitar un nuevo hilo para cada una. "
+"Hay muchas esperanzas puestas en este método, ya que podemos manejar un "
+"gran número de conexiones y no tendríamos que que reescribir un nuevo "
+"mini TCP stack con UDP. Sin embargo, los paquetes NIO no han probado aún "
+"estar listos, como averiguaron los desarrolladores de Freenet. Además, "
+"usar paquetes NIO significaría no poder usar ninguna JVM libre como Kaffe, ya que GNU/Classpath sólo tiene soporte "
+"limitado para NIO.(nota: puede que ahora esto ya no sea verdad, ya que"
+" se han hecho progreso en los NIO de Classpath, pero no sabemos su "
+"calidad)"
+
+#: i2p2www/pages/site/get-involved/todo.html:206
+#, python-format
+msgid ""
+"Another alternative along the same lines is the Non"
+" \n"
+"Blocking I/O package - essentially a cleanroom NIO implementation \n"
+"(written before NIO was around). It works by using some native OS code \n"
+"to do the nonblocking IO, passing off events through Java. It seems to \n"
+"be working with Kaffe, though there doesn't seem to be much development \n"
+"activity on it lately (likely due to 1.4's NIO deployment)."
+msgstr ""
+"Otra alternativa del mismo tipo es el paquete sin "
+"bloqueos I/O - básicamente es una implementación NIO tipo cleanroom "
+"(escrita antes de que NIO existiese). Funciona utilizando algo de código "
+"nativo del sistema operativo para hacer I/O sin bloqueos, pasando los "
+"eventos a través de Java. Parece que funciona con Kaffe, aunque no parece"
+" que haya mucha actividad últimamante en su desarrollo (debido "
+"probablemente al desarrollo de NIO 1.4) "
+
+#: i2p2www/pages/site/get-involved/todo.html:221
+msgid ""
+"Within the current network database and profile management "
+"implementation, \n"
+"we have taken the liberty of some practical shortcuts. For instance, we \n"
+"don't have the code to drop peer references from the K-buckets, as we \n"
+"don't have enough peers to even plausibly fill any of them, so instead, \n"
+"we just keep the peers in whatever bucket is appropriate. Another example"
+" \n"
+"deals with the peer profiles - the memory required to maintain each "
+"peer's \n"
+"profile is small enough that we can keep thousands of full blown profiles"
+" \n"
+"in memory without problems. While we have the capacity to use trimmed \n"
+"down profiles (which we can maintain 100s of thousands in memory), we \n"
+"don't have any code to deal with moving a profile from a \"minimal "
+"profile\" \n"
+"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to"
+" simply \n"
+"eject a profile altogether. It just wouldn't be practical to write that \n"
+"code yet, since we aren't going to need it for a while."
+msgstr ""
+"Nos hemos tomado la libertad de usar unos atajos prácticos dentro de la "
+"base de datos de la red y la implementación de la gestión del perfil. Por"
+" ejemplo, no tenemos el código para sacar los perfiles de los pares de "
+"K-buckets, al igual que no tenemos suficientes pares para llenar ninguno "
+"de ellos, en lugar de eso mantenemos los pares en cualquier cubo que "
+"pueda ser apropiado. Otro ejemplo tiene que ver con los perfiles de los "
+"pares - la memoria requerida para mantener cada perfil del par es "
+"suficientemente pequeña como para poder tener todos los perfiles en la "
+"memoria sin problemas (con lo que podemos mantener cientos de miles en la"
+" memoria), no tenemos ningún código para lidiar con el problema de mover "
+"un perfil de un \"perfil mínimo\" a un \"perfil completo\", de un "
+"\"perfil completo\" a un \"perfil mínimo\", o simplemente desechar un "
+"perfil completo. Simplemente no sería práctico escribir el código ya que "
+"no lo vamos a necesitar por un tiempo."
+
+#: i2p2www/pages/site/get-involved/todo.html:236
+msgid ""
+"That said, as the network grows we are going to want to keep these "
+"considerations \n"
+"in mind. We will have some work to do, but we can put it off for later."
+msgstr ""
+"Como ya hemos dicho, según siga creciendo la red volveremos a retomar "
+"estas consideraciones. Tendremos algún trabajo por hacer, pero se puede "
+"dejar para mas tarde."
+
+#: i2p2www/pages/site/get-involved/todo.html:248
+#: i2p2www/pages/site/get-involved/todo.html:332
+#, python-format
+msgid ""
+"Addressed in I2P 0.5 as documented elsewhere"
+msgstr ""
+"Conseguido en I2P 0.5 como se documenta aquí"
+
+#: i2p2www/pages/site/get-involved/todo.html:251
+msgid ""
+"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n"
+"going to Dave, then to Charlie, then Bob, and finally Alice "
+"(A<--B<--C<--D<--E), \n"
+"all five of them will know they are participating in tunnel \"123\", as \n"
+"the messages are tagged as such. What we want to do is give each hop "
+"their \n"
+"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n"
+"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n"
+"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n"
+"the tunnel had the same tunnel ID, collusion attacks aren't much work."
+msgstr ""
+"Ahora mismo si Alicia crea un túnel de entrada de cuatro saltos empezando"
+" en Elvis, yendo a través de Dave, después Charlie, después Bob y "
+"finalmente Alice (A<--B<--C<--D<--E), los cinco sabrán que "
+"están participando en el túnel \"123\", ya que el mensaje está etiquetado"
+" así. Lo que queremos hacer es dar a cada salto su propio ID de túnel - "
+"Charlie recibirá el mensaje en el túnel 234 y lo enviará al túnel 876 de "
+"Bob. Se intenta prevenir que Bob o Charlie sepan que están en el túnel de"
+" Alice, lo que ocurriría si en cada salto tuviesen el mismo ID de túnel "
+"haciendo que un ataque por colisión fuese más fácil."
+
+#: i2p2www/pages/site/get-involved/todo.html:261
+msgid ""
+"Adding a unique tunnel ID per hop isn't hard, but by itself, "
+"insufficient. \n"
+"If Dave and Bob are under the control of the same attacker, they wouldn't"
+" \n"
+"be able to tell they are in the same tunnel due to the tunnel ID, but \n"
+"would be able to tell by the message bodies and verification structures \n"
+"by simply comparing them. To prevent that, the tunnel must use layered \n"
+"encryption along the path, both on the payload of the tunneled message \n"
+"and on the verification structure (used to prevent simple tagging "
+"attacks). \n"
+"This requires some simple modifications to the TunnelMessage, as well \n"
+"as the inclusion of per-hop secret keys delivered during tunnel creation"
+" \n"
+"and given to the tunnel's gateway. We must fix a maximum tunnel length \n"
+"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n"
+"of the 16 delivered secret keys, in reverse order, and to encrypt the \n"
+"signature of the hash of the (encrypted) payload at each step. The "
+"gateway \n"
+"then sends that 16-step encrypted message, along with a 16-step and "
+"16-wide \n"
+"encrypted mapping to the first hop, which then decrypts the mapping and \n"
+"the payload with their secret key, looking in the 16-wide mapping for \n"
+"the entry associated with their own hop (keyed by the per-hop tunnel ID)"
+" \n"
+"and verifying the payload by checking it against the associated signed \n"
+"hash."
+msgstr ""
+"Añadir un Id único por cada salto no es difícil, pero sí insuficiente. Si"
+" Dave y Bob están bajo el control del mismo atacante no sería posible "
+"saber que están en el mismo túnel a causa del Id, pero podría se capaz de"
+" saber sobre el cuerpo del mensaje y las estructuras de verificación con "
+"solo compararlos. Para prevenir esto el túnel debe usar una capa de "
+"cifrado a lo largo del camino, en el payload tunelado y en la "
+"verificación de la estructura (usado para evitar ataques simples de "
+"etiquetado). Esto requiere algunos cambios simples en el TunnelMessage, y"
+" además, requiere del envío de claves secretas por cada salto durante la "
+"creación del túnel, y además hacer llegar estas claves a la salida del "
+"túnel. Tenemos que que crear un valor máximo del tamaño del túnel (por "
+"ejemplo 16), e instruir a la puerta de salida para que cifre el mensaje "
+"de cada una de las claves secretas enviadas, en orden inverso, y de que "
+"cifre la firma del hash del payload (cifrado) en cada salto. La puerta de"
+" salida envía entonces el mensaje cifrado de 16 pasos, junto con los 16 "
+"pasos y el mapeado cifrado de 16 de ancho al primer salto, el cual "
+"entonces  descifra el mapeado y el payload con su clave secreta, buscando"
+" en el mapeado de 16 de ancho por la entrada asociada con su propio salto"
+" (cifrado por el Id del túnel de cada salto) y verificando el pyload "
+"chequeándolo con el hash firmado asociado."
+
+#: i2p2www/pages/site/get-involved/todo.html:282
+msgid ""
+"The tunnel gateway does still have more information than the other peers"
+" \n"
+"in the tunnel, and compromising both the gateway and a tunnel participant"
+" \n"
+"would allow those peers to collude, exposing the fact that they are both"
+" \n"
+"in the same tunnel. In addition, neighboring peers know that they are \n"
+"in the same tunnel anyway, as they know who they send the message to (and"
+" \n"
+"with IP-based transports without restricted routes, they know who they \n"
+"got it from). However, the above two techniques significantly increase \n"
+"the cost of gaining meaningful samples when dealing with longer tunnels."
+msgstr ""
+"La salida del túnel todavía tiene más información que los otros pares del"
+" túnel, y comprometiendo la salida y un participante en el túnel "
+"permitiría a estos confabularse mostrando el hecho de que los dos "
+"pertenecen al mismo túnel. Además, los pares vecinos saben que están en "
+"el mismo túnel, ya que saben a quien envían el mensaje (y con transportes"
+" basados en IP con rutas restrictivas saben de donde lo reciben). Sin "
+"embargo, estas dos técnicas incrementan significativamente el coste de "
+"conseguir ejemplos con significado cuando se trata de túneles largos."
+
+#: i2p2www/pages/site/get-involved/todo.html:298
+msgid "Implemented in release 0.6.2"
+msgstr "Implementado en la versión 0.6.2"
+
+#: i2p2www/pages/site/get-involved/todo.html:301
+#, python-format
+msgid ""
+"As Connelly proposed to deal with the\n"
+"predecessor attack (2008\n"
+"update), keeping the order of peers within our tunnels consistent \n"
+"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n"
+"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n"
+"get to substantially sample Alice's peer selection group. We may even \n"
+"want to explicitly allow Bob to participate in Alice's tunnels in only \n"
+"one way - receiving a message from Dave and sending it to Charlie - and \n"
+"if any of those peers are not available to participate in the tunnel (due"
+" \n"
+"to overload, network disconnection, etc), avoid asking Bob to participate"
+" \n"
+"in any tunnels until they are back online."
+msgstr ""
+"Como propuso Connelly para tratar el ataque del predecesor(2008), manteniendo consistente el orden de los "
+"pares dentro de nuestros túneles (osea cuando Alice crea un túnel con Bob"
+" y Charlei en él, el siguiente salto de Bob es siempre Charlie), "
+"solucionamos el problema, ya que Bob no puede obtener una muestra del "
+"grupo de pares de Alice lo suficientemente grande. Incluso podríamos "
+"querer permitir explícitamente a Bob participar en el túnel de Alice en "
+"una dirección - recibiendo un mensaje de Dave y enviándolo a Charlie - y "
+"si unos de estos pares no están disponible para participar en el túnel "
+"(debido a saturación, desconexión de red, erc), evitar preguntar a Bob si"
+" participa en algún túnel hasta que vuelva a estar disponible."
+
+#: i2p2www/pages/site/get-involved/todo.html:316
+msgid ""
+"More analysis is necessary for revising the tunnel creation - at the \n"
+"moment, we simply select and order randomly within the peer's top tier \n"
+"of peers (ones with fast + high capacity)."
+msgstr ""
+"Aún hace falta un análisis más detallado de la creación del túnel - hasta"
+" el momento, simplemente seleccionamos y ordenamos aleatoriamente de "
+"entre uno de los mejores pares del par (uno rápido y con gran capacidad)"
+
+#: i2p2www/pages/site/get-involved/todo.html:321
+msgid ""
+"Adding a strict ordering to peers in a tunnel also improves the anonymity"
+" \n"
+"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway"
+" \n"
+"is always the same would be particularly damning. However, peers with \n"
+"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n"
+"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n"
+"duration) minutes, use a 1-hop tunnel)."
+msgstr ""
+"Añadiendo un orden estricto a los pares de un túnel también mejoramos el "
+"anonimato de los pares con túneles de 0 saltos, ya que de otra forma el "
+"hecho de que la salida del par fuese siempre la misma sería bastante "
+"dañino. Sin embargo, los pares con túneles de 0 saltos necesitarán usar "
+"periódicamente un túnel de 1 salto para simular el fallo de un par de "
+"salida normal (así cada MTBF*(duración del túnel) minutos, usaría un "
+"túnel de 1 salto)"
+
+#: i2p2www/pages/site/get-involved/todo.html:338
+msgid ""
+"Without tunnel length permutation, if someone were to somehow detect that"
+" \n"
+"a destination had a particular number of hops, it might be able to use "
+"that \n"
+"information to identify the router the destination is located on, per the"
+" \n"
+"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n"
+"receives a tunnel message from Charlie and forwards it to Alice, Bob "
+"knows \n"
+"Alice is the final router in the tunnel. If Bob were to identify what "
+"destination \n"
+"that tunnel served (by means of colluding with the gateway and harvesting"
+" \n"
+"the network database for all of the LeaseSets), he would know the router"
+" \n"
+"on which that destination is located (and without restricted routes, that"
+" \n"
+"would mean what IP address the destination is on)."
+msgstr ""
+"Sin los cambios de tamaño de los túneles, si alguien de alguna forma "
+"detectase que una destinación tiene un número determinado de saltos, "
+"sería capaz de usar esa información para identificar la localización de "
+"la destinación de ruter usando el ataque del predecesor.  Por ejemplo, si"
+" todo el mundo tiene túneles de 2 saltos, si Bob recibe un mensaje de "
+"Charlie y lo envía a Alice, Bob sabría que que Alice es el ruter final "
+"del túnel. Si Bob quisiese  identificar la destinación que ese túnel "
+"sirvió (confabulándose con el nodo de salida y buscando en la base de "
+"datos de la red a todos los LeaseSets), conocería el ruter que está en "
+"esa destinación ( y sin rutas restringidas, eso quiere decir que "
+"sabríamos la IP de la destinación)"
+
+#: i2p2www/pages/site/get-involved/todo.html:350
+msgid ""
+"It is to counter user behavior that tunnel lengths should be permuted, \n"
+"using algorithms based on the length requested (for example, the 1/MTBF \n"
+"length change for 0-hop tunnels outlined above)."
+msgstr ""
+"El tamaño de los túneles debe ser cambiante para contrarrestar el "
+"comportamiento de los usuarios, usando algoritmos basados en el tamaño "
+"requerido (por ejemplo, el cambio de tamaño a 1/MTBF de los túneles de 0 "
+"saltos)"
+
+#: i2p2www/pages/site/get-involved/todo.html:360
+msgid ""
+"The restricted route functionality described before was simply a "
+"functional \n"
+"issue - how to let peers who would not otherwise be able to communicate \n"
+"do so. However, the concept of allowing restricted routes includes "
+"additional \n"
+"capabilities. For instance, if a router absolutely cannot risk "
+"communicating \n"
+"directly with any untrusted peers, they can set up trusted links through"
+" \n"
+"those peers, using them to both send and receive all of its messages. \n"
+"Those hidden peers who want to be completely isolated would also refuse \n"
+"to connect to peers who attempt to get them to (as demonstrated by the \n"
+"garlic routing technique outlined before) - they can simply take the "
+"garlic \n"
+"clove that has a request for delivery to a particular peer and tunnel \n"
+"route that message out one of the hidden peer's trusted links with "
+"instructions \n"
+"to forward it as requested."
+msgstr ""
+"La funcionalidad restringida del ruter descrita antes era simplemente un "
+"problema funcional - cómo hacer que dos pares que de otra forma no "
+"estrían comunicados se comuniquen. Sin embargo, el concepto de permitir "
+"ruters restringidos incluye capacidades adicionales. Por ejemplo, si un "
+"ruter no puede arriesgarse de ninguna forma a una comunicación directa "
+"con un par sin confianza, pueden configurar enlaces seguros a través de "
+"esos pares,  usándolos para enviar y recibir todos sus mensajes. Esos "
+"pares ocultos que desean estar totalmente aislados pueden también negarse"
+" a conectar con pares que intenten alcanzarles (como se demuestra en la "
+"técnica de ruteado 'garlic' esbozada anteriormente)"
+
+#: i2p2www/pages/site/get-involved/todo.html:379
+#, python-format
+msgid ""
+"Within the network, we will want some way to deter people from consuming"
+" \n"
+"too many resources or from creating so many peers to mount a Sybil \n"
+"attack. Traditional techniques such as having a peer see who is "
+"requesting \n"
+"a resource or running a peer aren't appropriate for use within I2P, as \n"
+"doing so would compromise the anonymity of the system. Instead, we want \n"
+"to make certain requests \"expensive\"."
+msgstr ""
+"Dentro de la red necesitaremos una forma de disuadir al a gente de "
+"consumir demasiados recursos o de crear demasiados pares como para montar"
+" un ataque Sybil. Las técnicas tradicionales "
+"como dejar que un par vea quien solicita un recurso o quien ejecuta "
+"cierto par, no son apropiadas para I2P, ya que eso comprometería el "
+"anonimato del sistema. En su lugar queremos hacer que ciertas peticiones "
+"sean muy \"caras\"."
+
+#: i2p2www/pages/site/get-involved/todo.html:387
+msgid ""
+"Hashcash is one technique that \n"
+"we can use to anonymously increase the \"cost\" of doing certain "
+"activities, \n"
+"such as creating a new router identity (done only once on installation),"
+" \n"
+"creating a new destination (done only once when creating a service), or \n"
+"requesting that a peer participate in a tunnel (done often, perhaps 2-300"
+" \n"
+"times per hour). We don't know the \"correct\" cost of each type of "
+"certificate \n"
+"yet, but with some research and experimentation, we could set a base "
+"level \n"
+"that is sufficiently expensive while not an excessive burden for people \n"
+"with few resources."
+msgstr ""
+"Hashcash es una técnica que "
+"podemos usar anónimamente para incrementar el \"costo\" de hacer ciertas "
+"acciones., como crear una nueva identidad de ruter (se hace sólo cuando "
+"se instala por primera vez), crear una nueva destinación (se hace sólo "
+"cuando se crea un nuevo servicio), o solicitar que un par participe en un"
+" túnel (se hace a menudo, quizás 2-300 veces a la hora). No conocemos "
+"todavía el coste \"correcto\" de cada tipo de certificado, pero con algo "
+"de investigación y estudio, podemos crear un nivel básico que sea lo "
+"suficientemente caro pero no tan caro como para que agobie a la gente con"
+" pocos recursos."
+
+#: i2p2www/pages/site/get-involved/todo.html:398
+msgid ""
+"There are a few other algorithms that we can explore for making those \n"
+"requests for resources \"nonfree\", and further research on that front is"
+" \n"
+"appropriate."
+msgstr ""
+"Hay varios algoritmos que podemos explorar para hacer que esas peticiones"
+" de recursos \"tengan un costo\", sería conveniente seguir investigando "
+"sobre este tema."
+
+#: i2p2www/pages/site/get-involved/todo.html:408
+#, python-format
+msgid ""
+"To powerful passive external observers as well as large colluding "
+"internal \n"
+"observers, standard tunnel routing is vulnerable to traffic analysis "
+"attacks \n"
+"- simply watching the size and frequency of messages being passed between"
+" \n"
+"routers. To defend against these, we will want to essentially turn some \n"
+"of the tunnels into its own mix cascade - delaying messages received at \n"
+"the gateway and passing them in batches, reordering them as necessary, \n"
+"and injecting dummy messages (indistinguishable from other \"real\" "
+"tunnel \n"
+"messages by peers in the path). There has been a significant amount of \n"
+"research \n"
+"on these algorithms that we can lean on prior to implementing the various"
+" \n"
+"tunnel mixing strategies."
+msgstr ""
+"El rutado estándar de túneles es vulnerable al análisis de tráfico para "
+"los observadores externos pasivos con muchos medios y para un gran número"
+" de observadores internos si están confabulados, simplemente observando "
+"el tamaño y la frecuencia de los mensajes que pasan a través de los "
+"ruters.  Para defendernos de esto, queremos simplemente convertir algunos"
+" túneles en su propia mezcla de cascada - retrasando los mensajes "
+"recibidos en la puerta de salida y pasándolos en lotes, reordenándolas "
+"como sea necesario, e inyectando mensajes de relleno (indistinguibles de "
+"los túneles \"reales\" para los pares). Ha habido un gran número de estudios sobre estos algoritmos que podríamos "
+"utilizar para implementar varias estrategias de mezclado de túneles."
+
+#: i2p2www/pages/site/get-involved/todo.html:421
+msgid ""
+"In addition to the anonymity aspects of more varied tunnel operation, \n"
+"there is a functional dimension as well. Each peer only has a certain \n"
+"amount of data they can route for the network, and to keep any particular"
+" \n"
+"tunnel from consuming an unreasonable portion of that bandwidth, they \n"
+"will want to include some throttles on the tunnel. For instance, a tunnel"
+" \n"
+"may be configured to throttle itself after passing 600 messages (1 per \n"
+"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n"
+"last minute). Excess messages may be delayed or summarily dropped. With \n"
+"this sort of throttling, peers can provide ATM-like QoS support for their"
+" \n"
+"tunnels, refusing to agree to allocate more bandwidth than the peer has \n"
+"available."
+msgstr ""
+"Además de los aspectos del anonimato en las operaciones de los túneles, "
+"hay una dimensión funcional extra.  Cada par sólo tiene cierto número de "
+"datos que pueden rutar por la red, y para evitar que un túnel en "
+"particular consuma una gran parte del ancho de banda, necesitarán añadir "
+"algunas regulaciones en el túnel. Por ejemplo, un túnel puede estar "
+"configurado para pararse a sí mismo después de pasar 600 mensajes (1 par "
+"por segundo), 2.4MB (4KBps), o tras haber excedido algún promedio "
+"variable (8KBps en el último minuto). Los mensajes sobrantes pueden ser "
+"retardados o desechados. Con este tipo de control, los pares pueden "
+"ofrecer un soporte parecido al QoS en sus túneles, negándose a asignar "
+"más ancho de banda de la que el par tiene disponible."
+
+#: i2p2www/pages/site/get-involved/todo.html:434
+msgid ""
+"In addition, we may want to implement code to dynamically reroute tunnels"
+" \n"
+"to avoid failed peers or to inject additional hops into the path. This \n"
+"can be done by garlic routing a message to any particular peer in a "
+"tunnel \n"
+"with instructions to redefine the next-hop in the tunnel."
+msgstr ""
+"Además, queremos implementar el código para re-rutar los túneles "
+"dinámicamente, y así evitar que los pares fallidos añadan saltos "
+"adicionales en el camino. Esto lo puede hacer la red garlic rutando un "
+"mensaje a un par en particular con las instrucciones para redefinir el "
+"siguiente salto del túnel."
+
+#: i2p2www/pages/site/get-involved/todo.html:445
+msgid ""
+"Beyond the per-tunnel batching and mixing strategy, there are further \n"
+"capabilities for protecting against powerful attackers, such as allowing"
+" \n"
+"each step in a garlic routed path to define a delay or window in which \n"
+"it should be forwarded on. This would enable protections against the long"
+" \n"
+"term intersection attack, as a peer could send a message that looks "
+"perfectly \n"
+"standard to most peers that pass it along, except at any peers where the"
+" \n"
+"clove exposed includes delay instructions."
+msgstr ""
+"Además de las estrategias de mezclado y de procesado por lotes de cada "
+"túnel, hay más  formas de protegernos contra atacantes poderosos, como "
+"permitir crear un retraso en cada paso dentro de un camino de rutado "
+"garlic. Esto crearía protecciones contra un ataque largo de intersección,"
+" ya que un par podría enviar mensajes que parecen normales a la mayoría "
+"de los pares, excepto a cualquier par donde se hayan dado instrucciones "
+"de retardo."
+
+#: i2p2www/pages/site/get-involved/todo.html:457
+#, python-format
+msgid ""
+"Performance related improvements are listed on the\n"
+"Performance page."
+msgstr ""
+"Las mejoras en el rendimiento se listan en la página de rendimiento ."
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2
+msgid "Bounty Arabic translation of webpage and router console"
+msgstr ""
+"Recompensa por la traducción al árabe de la página web y la consola de "
+"ruter."
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3
+#: i2p2www/pages/site/get-involved/bounties/index.html:119
+msgid "Arabic translation"
+msgstr "Traducción al árabe."
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P echelon set out this bounty for translation\n"
+"of the I2P web page and I2P router console into Arabic."
+msgstr ""
+"Para mejorar el uso de I2P y atraer más gente, echelon propone esta "
+"recompensa por la traducción al árabe de la web de I2P y la consola del "
+"ruter."
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12
+msgid "This bounty is set into 2 subparts:"
+msgstr "Esta recompensa de divide en 2 partes:"
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14
+msgid "Part 1 is translation of the webpage."
+msgstr "La parte 1 es la traducción de la página web."
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17
+msgid ""
+"For collecting the bounty of 20 BTC you need to translate the following "
+"pages:"
+msgstr ""
+"Para recibir la recompensa de 20 BTC necesita traducir las siguientes "
+"páginas:"
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25
+msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada."
+msgstr ""
+"El trabajo fue hecho por Amanda y la recompensa de 20 BTC fue pagada a "
+"Amanda."
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27
+msgid ""
+"Part 2 is the translation of the router console. The router console was\n"
+"partly translated and the bounty of 80 BTC was paid to hamada."
+msgstr ""
+"La parte 2 es la traducción de la consola del ruter. La consola del ruter"
+" fue parcialmente traducida y la recompensa de 80 BTC se pagó a hamada."
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34
+msgid "Judge is echelon."
+msgstr "El juez es echelon."
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2
+msgid "Bounty creating a I2P native Bitcoin client"
+msgstr "Recompensa por la creación de un cliente nativo para I2P."
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3
+msgid "BTC I2P native client"
+msgstr "Cliente nativo BTC para I2P"
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to create a I2P native Bitcoin client. \n"
+"It should integrate with other client via the I2P network and via "
+"gateways to\n"
+"the existant bitcoin network."
+msgstr ""
+"Para el futuro de I2P y para atraer más gente a I2P esta recompensa se "
+"pensó para crear un cliente de Bitcoin para I2P. Debería integrarse con "
+"otros clientes dentro de la red de I2P y vía las salidas, con la red de "
+"Bitcoin actual."
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15
+msgid "Judge is psychonaut who donated the first 30 € to this bounty."
+msgstr ""
+"El juez es psychonaut quien donó los primeros 30 € para esta "
+"recompensa."
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
+msgid "Bounty datastorage"
+msgstr "Recompensa por el almacenamiento de datos."
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:3
+msgid "datastore"
+msgstr "almacenamiento de datos"
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:6
+msgid ""
+"To improve I2P's usage and to be independent of routers \n"
+"online status we want a datastorage as a extension to I2P.\n"
+"Like in Freenet the datastorage should be distributed and every\n"
+"participating node should be able to configure his options.\n"
+"The files should be saved in chunks and at least 2-3 times to\n"
+"obtain redundancy. Usage of storage space should be auto balanced.\n"
+"As it is a extra application, it should work flawless within I2P and\n"
+"cooperate nice with the I2P router. Maybe a integration within the\n"
+"webpage/router could be done."
+msgstr ""
+"Para mejorar el uso de I2P y ser independiente del estados de los ruters "
+"en funcionamiento queremos un sistema de almacenamiento de datos como una"
+" extensión de I2P. Como en Freenet, el almacenamiento de información "
+"debería ser distribuido y cada nodo participante debería poder configurar"
+" sus propias opciones. Los archivos deberían ser guardados en trozos y al"
+" menos 2-3 veces para obtener redundancia. El uso del espacio de "
+"almacenamiento debería ser auto balanceado. Y aunque sea una aplicación "
+"extra, debería funcionar perfectamente dentro de I2P y cooperar bien con "
+"el ruter I2P. Quizás se puede hacer una integración dentro de la página "
+"web o del ruter."
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:17
+msgid ""
+"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n"
+"\"eepsites in datastorage\"."
+msgstr ""
+"Esta recompensa está unida con otras 2 recompensas, \"frost para I2P\" y "
+"\"eepsites en el almacenamiento de datos\""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:21
+msgid ""
+"The frost for I2P datastorage bounty is paid for a frost like program \n"
+"with which files/messages are stored into database and got from database."
+"\n"
+"It needs to work with a GUI."
+msgstr ""
+"La recompensa por frost para el almacenamiento de datos de I2P es pagada "
+"por un programa tipo frost en donde los archivos o mensajes son "
+"almacenados dentro de una base de datos y obtenidos de la base de datos. "
+"Debe funcionar con GUI, entorno gráfico."
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:26
+msgid ""
+"The eepsite served out of I2P datastorage extends a I2P router to send\n"
+"out eepsites out of the I2P datastorage. All files for eepsites need to "
+"be\n"
+"saved inside of datastorage and are taken from it.\n"
+"Extension:\n"
+"For better integration all datastorage participants could serve that "
+"eepsite."
+msgstr ""
+"El eepsite servido desde el almacén de datos de I2P despliega un "
+"enrutador\n"
+"('router') I2P para enviar eepsites desde el almacén de datos I2P. Todos "
+"los\n"
+"ficheros para los eepsites han de ser guardados dentro del almacén de "
+"datos\n"
+"y son tomados desde este.\n"
+"Extensión:\n"
+"Para mayor integración todos los participes del almacen de datos podrían\n"
+"servier ese eepsite."
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:36
+msgid ""
+"For bounties to be declared done and paid, we need the program AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+"Para que una recompensa sea declarada pagada, necesitamos la aplicación y"
+" el código. El código debe estar bajo una licencia libre (libre de "
+"cambiar y de distribuir el código)."
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2
+msgid "Bounty I2P package in Debian and Ubuntu mirrors"
+msgstr "Recompensa por el paquete I2P en los repositorios de Debian y Ubuntu"
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3
+msgid "I2P Ubuntu/Debian package"
+msgstr "Paquetes I2P para Ubuntu/Debian"
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6
+msgid ""
+"For the future of I2P and in order to attract more people\n"
+"to I2P, this bounty was set for including an I2P package into the Ubuntu "
+"and Debian \n"
+"archive mirrors.\n"
+"To claim this bounty, the I2P router package needs to be available from\n"
+"Ubuntu and Debian archive mirrors and Debian bug \n"
+"448638 \n"
+"needs to be closed successfully."
+msgstr ""
+"Para el futuro y para atraer más gente a I2P, esta recompensa se creó "
+"para incluir los paquetes de I2P dentro de los repositorios de Ubuntu y "
+"Debian. Para reclamar esta recompensa, el paquete del ruter de I2P debe "
+"estar disponible desde los repositorios de Ubuntu y Debian y el bug 448638 debe cerrarse exitosamente."
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2
+msgid "Bounty I2PHex code implementation"
+msgstr "Recompensa por la implementación de I2PHex"
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3
+msgid "i2phex code implementation"
+msgstr "Implementación del código fuente de I2P"
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2PHex P2P ArneBab setout the bounty for implementing actual\n"
+"Phex code onto I2PHex."
+msgstr ""
+"Para mejorar el uso de I2P y atraer más gente a I2PHex P2P, ArneBab creó "
+"la recompensa por implementar el código actual de Phex dentro de I2PHex."
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:2
+msgid "Bounties"
+msgstr "Recompensas"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:5
+msgid "Bounties for I2P"
+msgstr "Recompensas por I2P"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:6
+msgid ""
+"While we always gratefully accept any contributions of code, \n"
+"documentation, and the like, there are other ways to help I2P move \n"
+"forward.  As with any open source project, our goals would be achieved "
+"more \n"
+"rapidly if we were able to support all of our contributors to work on \n"
+"I2P full time.  However, as with any open source project, that's not a \n"
+"possibility.  Instead, we are making use of a bounty system, whereby \n"
+"anyone can get support for working on something that people want \n"
+"implemented, and people who want to contribute to I2P can be assured that"
+" \n"
+"their support goes to what they care about."
+msgstr ""
+"Aunque siempre aceptamos con agradecimiento cualquier contribución al "
+"código, documentación, y de ese tipo, hay otras formas de hacer que I2P "
+"siga adelante. Al igual que con otros proyectos libres nuestros fines se "
+"podrían conseguir más rápido si fuésemos capaces de compensar a todos los"
+" ayudantes para que trabajasen en I2P a jornada completa. Pero, y al "
+"igual que con cualquier otro proyecto libre, esto no es posible. En lugar"
+" de eso, estamos utilizando un sistema de recompensas en donde cualquiera"
+" pude tener compensación por trabajar en algo que desea implementar, y la"
+" gente que ayuda a I2P puede estar segura que su apoyo va dirigido a lo "
+"que a ellos les interesa."
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:18
+msgid ""
+"We are also keeping open the ability for people who want to support I2P \n"
+"but don't have strong feelings about the bounties available.  Those "
+"people\n"
+"can simply put their trust in the I2P team to do what we feel is best by\n"
+"donating to a catch-all general fund that will be used as deemed \n"
+"necessary - allocated to various bounties, covering incidentals (hosting,"
+" \n"
+"etc), and the like."
+msgstr ""
+"También mantenemos abierta una posibilidad para la gente que quiere "
+"ayudar a I2P pero no está convencida de las recompensas disponibles. Esta"
+" gente simplemente puede poner su confianza en el equipo de I2P para que "
+"este haga lo que piense que es mejor, donando a un fondo general que será"
+" usado en lo que se considere necesario - usado para las recompensas, "
+"cubrir imprevistos (alojamiento, etc), y cosas de ese tipo."
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:27
+msgid "Current bounties"
+msgstr "Recompensas actuales"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Name"
+msgstr "Nombre"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Status"
+msgstr "Estado"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Judge"
+msgstr "Juez"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Dev"
+msgstr "Desarrolladores"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Bounty"
+msgstr "Recompensas"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:32
+msgid "Frost for I2P datastorage"
+msgstr "Frost para el almacenamiento de datos de I2P"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:33
+#: i2p2www/pages/site/get-involved/bounties/index.html:40
+#: i2p2www/pages/site/get-involved/bounties/index.html:47
+#: i2p2www/pages/site/get-involved/bounties/index.html:54
+#: i2p2www/pages/site/get-involved/bounties/index.html:75
+#: i2p2www/pages/site/get-involved/bounties/index.html:82
+msgid "Proposal in development"
+msgstr "Proposición en desarrollo"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:35
+#: i2p2www/pages/site/get-involved/bounties/index.html:42
+#: i2p2www/pages/site/get-involved/bounties/index.html:49
+#: i2p2www/pages/site/get-involved/bounties/index.html:56
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+#: i2p2www/pages/site/get-involved/bounties/index.html:97
+msgid "vacant"
+msgstr "vacante"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:39
+msgid "Eepsites served out of I2P datastorage"
+msgstr "Eepsites disponibles fuera del almacenamiento de datos de I2P"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:46
+msgid "Backporting Phex code onto I2PHex"
+msgstr "Portar el código de Phex dentro de I2PHex"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:53
+msgid "I2P package in Debian and Ubuntu mirrors"
+msgstr "Paquetes I2P disponibles en los repositorios de Debian y Ubuntu"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:60
+msgid "Bitcoin client for I2P"
+msgstr "Cliente Bitcoin para I2P"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:61
+msgid "Done, phase of verification"
+msgstr "Hecho, fase de verificación"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:67
+msgid "Unit tests and Multi-router Simulation"
+msgstr "Unit tests y simulación multi-tuter"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:68
+msgid "Partly done, partly in work, partly still open"
+msgstr "Parcialmente hecho, parcialmente trabajando, parcialmente aún abierto"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:89
+msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
+msgstr "Recompensas paradas, paradas a causa de la desaparición de jrandom."
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:94
+msgid "Bundling bounties"
+msgstr "Ordenando las recompensas"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:95
+msgid "Proposed"
+msgstr "Propuesto"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:102
+msgid "Claimed bounties"
+msgstr "Recompensas reclamadas"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Dev team"
+msgstr "Equipo de desarrollo"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:107
+msgid "Make I2P IPv6 native"
+msgstr "Hacer I2P IPV6 nativo"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:114
+msgid "Setting up a SILC server"
+msgstr "Configurar un servidor SILC"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:124
+msgid "Datastore over I2P"
+msgstr "Almacenamiento de datos sobre I2P."
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:129
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
+msgid "Russian translation"
+msgstr "Traducción al ruso"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:134
+msgid "Swarming file transfer"
+msgstr "Agrupando para la transferencia de archivo"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:139
+msgid "Streaming library window size"
+msgstr "Tamaño de la ventana de la librería de streaming"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:144
+msgid "IRC connect time monitor"
+msgstr "Monitor del tiempo de conexión del IRC"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:149
+msgid "Unit tests (part 1)"
+msgstr "Unit tests (parte 1)"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:161
+msgid ""
+"Dev lists anyone who may already be working on the bounty - collaboration"
+" is\n"
+"preferred, so if you're interested in working on it, please contact one "
+"of the\n"
+"people listed!"
+msgstr ""
+"Los desarrolladores listan a cualquier persona que haya podido trabajar "
+"en la recompensa -  por lo cual si está interesado en trabajar en ello, "
+"¡por favor contacte con una de las personas listadas!"
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2
+msgid "Bounty I2P IPv6 native"
+msgstr "Recompensa por IPV6 nativo para I2P"
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3
+msgid "native IPv6 I2P"
+msgstr "IPV6 nativo para I2P"
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n"
+"To claim this bounty, the I2P router needs to run full on native\n"
+"IPv6 connections like it does on IPv4."
+msgstr ""
+"Por el futuro de I2P y para atraer a más gente a I2P, yo ofrezco una "
+"recompensa por el soporte IPv6 en I2P. Para obtener esta recompensa, los "
+"ruters de I2P deben funcionar nativa y completamente con conexiones IPv6 "
+"como lo hacen con conexiones IPv4."
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:17
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
+msgid ""
+"For bounties to be declared done and paid, we need the plugin AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+"Para que las recompensas sean declaradas hechas y pagadas, necesitamos el"
+" pluguin y las fuentes. El código y las fuentes tienen que ser liberados "
+"con licencias libres (libre para ser cambiado y distribuido)."
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:2
+msgid "NetDB Backend"
+msgstr "Sistema NetDB"
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:3
+msgid "netDB backend"
+msgstr "Sistema netDB"
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:7
+msgid ""
+"The current NetDB implementation (namely the FloodFill system)\n"
+"needs to be extended with another backend to improve reliability,\n"
+"reduce attack surface and solve the scalability issue for the \n"
+"coming years."
+msgstr ""
+"La implementación actual de NetDB (llamada sistema Floodfill) necesita "
+"ser extendida con otro sistema para mejorar la seguridad, reducir los "
+"ataques de superficie u arreglar los problemas de escalabilidad para los "
+"próximos años."
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:14
+msgid ""
+"A solution likely based on a DHT will be investigated and \n"
+"finally implemented."
+msgstr "Se investigará e y finalmente implementará una solución basada en DHT."
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2
+msgid "Bounty russian translation of webpage and router console"
+msgstr ""
+"Recompensa por la traducción al ruso de la página web y la consola del "
+"ruter."
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P a anonymous donator set out the bounty for translation\n"
+"of the I2P web page and I2P router console into russian language."
+msgstr ""
+"Para mejorar el uso de I2P y atraer más gente a I2P, un donante anónimo "
+"ha creado una recompensa para la traducción al ruso de la web de I2P y la"
+" consola del ruter."
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17
+msgid ""
+"For collecting the bounty of $115 USD you need to translate the following"
+" pages:"
+msgstr ""
+"Para recibir la recompensa de 115 dólares tiene que traducir estas "
+"páginas:"
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30
+msgid ""
+"Part 2 is the translation of the router console. The whole router console"
+" needs\n"
+"to be translated to collect the bounty of $115 USD."
+msgstr ""
+"La parte 2 es la traducción del a consola del ruter. Tiene que traducir "
+"la consola del ruter completa para recibir la recompensa de 115 dólares."
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37
+msgid "Judge is the russian donor."
+msgstr "Judge es el donante ruso."
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:2
+msgid "Bounty migrate I2P IRC to SILC"
+msgstr "Recompensa por migrar el IRC I2P a SILC"
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:3
+msgid "I2P silc server"
+msgstr "Servidor I2P silc"
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:7
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to setup and host a I2P SILC server.   \n"
+"This will allow people to send files over their messaging servers and "
+"have intrinsic security built into the protocol."
+msgstr ""
+"Para el futuro y para atraer a más gente a I2P, se ha creado una "
+"recompensa para configurar y mantener un servidor SILC I2P. Esto "
+"permitirá a la gente enviar archivos sobre los servidores de mensajes y "
+"tener asegurada la privacidad dentro del propio protocolo."
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:12
+msgid ""
+"A silc server needs to be set up and run for at least 3 month time to get"
+" payed. \n"
+"A second server should be set up, to."
+msgstr ""
+"El servidor silc tiene que ser configurado y funcionar durante 3 meses "
+"para ser pagado. Se debería también configurar un segundo servidor."
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:16
+msgid ""
+"Bounty was withdrawn and money donated to returningnovice and general "
+"fund."
+msgstr ""
+"La recompensa ha sido retirada y donada a returningnovice y al fondo "
+"general."
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:22
+msgid "Judge is An Anonymous Secret Society, society@mail.i2p."
+msgstr "Judge es una sociedad secreta anónima, society@mail.i2p."
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3
+msgid "Syndie development"
+msgstr "Desarrollo de Syndie"
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7
+msgid ""
+"Beside of I2P we want to encourage users\n"
+"to care more about anonymity and security. As I2P is a low \n"
+"latency network with its natural limits, the software SYNDIE\n"
+"can overcome some of these limits and provide better anonymity\n"
+"for people who really need it."
+msgstr ""
+"Además de usar I2P, queremos fomentar que los usuarios tengan más en "
+"cuenta el anonimato y la privacidad. Ya que I2P es una red baja latencia "
+"con límites naturales, el software SYNDIE puede vencer esos límites y "
+"provver más anonimato para la gente que relamente lo necesita."
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14
+msgid ""
+"For our bad sake the syndie project was out of development for \n"
+"quite a long time yet (5 years). To get a fresh and new built \n"
+"with needed bugfixes we set out this bounty. Also syndie needs\n"
+"some enhancements and a better GUI for users to work with it.\n"
+"Current bounty sum is 50 Bitcoin."
+msgstr ""
+"El proyecto syndie ha estado en desarrollo por demasiado tiempo (5 años)."
+" Para conseguir una nueva y fresca versión con los errores arreglados "
+"hemos creado esta recompensa. Además Syndie necesita algunas mejoras y "
+"una GUI mejor con la que trabajar. La recompensa actual es de 50 "
+"bitcoins."
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22
+msgid ""
+"The latest Syndie coding rally did improve the situation of the\n"
+"Syndie package dramatically. A new Syndie package with bugfixes\n"
+"was created and made available on different webpages.\n"
+"As a result of this work, the bounty sum was reduced and\n"
+"the withdrawn money moved to the IPv6 bounty."
+msgstr ""
+"Las últimas mejoras de Syndie en el código han mejorado dramáticamente la"
+" mejora de la aplicación. Se ha creado un nuevo paquete con arreglos y se"
+" ha puesto a disposición en varias páginas. Como resultado de este "
+"trabajo, la cantidad de la recompensa fue reducida y el dinero retirado "
+"se movido a la recompensa de IPv6."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2
+msgid "Bounty unittests"
+msgstr "Recompensa por unittests"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3
+msgid "unit test"
+msgstr "unit test"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7
+msgid ""
+"To improve I2P's maintainability, we want to have a solid set of\n"
+"automated unit tests for the critical code.  While we do have some\n"
+"unit tests at the moment, they are ad-hoc and partly unfinished.  \n"
+"This bounty is for someone to check the existing tests and move over\n"
+"old ones to jUnit, automate their execution, extend them to provide \n"
+"better code coverage, and publish the report online.  Its a massive \n"
+"effort, but can be broken down into phases, listed below (phase 2 \n"
+"must occur first, but further phases may happen in any order).\n"
+"As this needs some reading of code, it is the best start point for\n"
+"new devs to get a good overview of I2P code and coding. A good job\n"
+"for college students, interns or anyone who is just interested."
+msgstr ""
+"Para mejorar el mantenimiento de I2P, queremos un conjunto de unit tests "
+"automáticos para el código crítico. Aunque ya tenemos algunos unit tests,"
+" son ad-hoc y están parcialmente sin terminar. Esta recompensa es para "
+"alguien que compruebe los tests existentes y los mueva a jUnit, "
+"automatice su ejecución, los amplíe para mejorar la cobertura sobre el "
+"código, y lo publique el reporte online. Es un esfuerzo enorme, pero "
+"puede romperse en fases, listadas más abajo (la fase 2 debe hacerse "
+"primero, pero las demás fases pueden hacerse en cualquier orden). Ya que "
+"este trabajo necesita leer el código, es un buen punto de inicio para los"
+" nuevos desarrolladores echarle el ojo al código de I2P. Es un buen "
+"trabajo para estudiantes o cualquiera interesado."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20
+msgid ""
+"Take care! Jobs and bounties shuffled a bit!\n"
+"Phase 6,7 and 8 are still open!"
+msgstr ""
+"¡Tenga cuidad! ¡Los trabajos y recompensas han cambiado un poco! ¡Las "
+"fases 6,7 y 8 están aun abiertas!"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112
+#, python-format
+msgid "Phase %(phase)s:"
+msgstr "Fase %(phase)s:"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27
+msgid "CI jenkins and IRC bot"
+msgstr "CI jenkins e IRC bot"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114
+#, python-format
+msgid "Bounty: %(euro)s €"
+msgstr "Recompensa: %(euro)s €"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29
+msgid "server runs and this section is blocked"
+msgstr "el servidor ya se ejecuta y esta rección está bloqueada."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31
+msgid ""
+"To collect this bounty, a continuous integration server (Jenkins,\n"
+"old name was Hudson) must be set up and a connected IRC bot needs \n"
+"to set up in the channel #i2p-dev on IRC2p network to print out\n"
+"results of build tests.
            \n"
+"The server needs to be run long term."
+msgstr ""
+"Para obtener esta recompensa, un servidor de integración continuo "
+"(Jenkins, antes se llamaba Hudson) debe configurarse y un bot IRC debe "
+"configurarse y conectarse al canal #i2p-dev en la red IRC2p para poder "
+"mostrar los resultados de las pruebas de compilación.
            \n"
+"Este servidor debe ejecutarse por largo tiempo."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41
+msgid "Check existing SDK tests"
+msgstr "Comprobar las pruebas del SDK existentes"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69
+msgid "paid to str4d"
+msgstr "pagado a str4d"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45
+#, python-format
+msgid ""
+"To collect this bounty, the existing SDK tests must be checked \n"
+"and made to work again. The need to be integrated into the ant \n"
+"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g."
+" \n"
+"Clover).  The ant script\n"
+"must be capable of generating test status results as a web page, \n"
+"which will be published online."
+msgstr ""
+"Para obtener esta recompensa el SDK debe ser comprobado y hacer que "
+"funcione de nuevo. Debe ser integrado dentro de los scripts de "
+"compilación de ant (\"ant test\") y unido con una herramienta de "
+"cobertura (por ejemplo Clover). El script ant "
+"debe ser capaz de generar resultados de pruebas de estado como una página"
+" web, que se publicará online."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56
+msgid "SDK test coverage"
+msgstr "Cobertura de tests del SDK"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80
+msgid "paid to unittests dev team"
+msgstr "pagado al grupo de desarrollo de unittests"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60
+msgid ""
+"To collect this bounty, the automated unit tests of the SDK \n"
+"(i2p/core/java/src) must work again."
+msgstr ""
+"Para obtener esta recompensa, los unit tests automáticos del SDK "
+"(i2p/core/java/src) tienen que funcionar de nuevo."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67
+msgid "Router test migration"
+msgstr "Migración de las pruebas del ruter"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71
+msgid ""
+"As with phase 2, the existing unit tests for the router must be\n"
+"moved over to the automated system."
+msgstr ""
+"Como en la fase 2, los unit tests existentes del ruter tienen que ser "
+"movidos a un sistema automático."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78
+msgid "Router test coverage"
+msgstr "Covertura para los tests del ruter."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82
+msgid ""
+"To collect this bounty, the automated unit tests of the router \n"
+"(i2p/router/java/src) must work again."
+msgstr ""
+"Para obtener esta recompensa, los unit tests automáticos del ruter "
+"(i2p/core/java/src) tienen que funcionar de nuevo."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89
+msgid "Streaming lib tests"
+msgstr "Tests de la libreriá de streaming"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94
+msgid ""
+"To collect this bounty, a new set of unit tests must meet a \n"
+"measured code coverage of 90% of the streaming lib \n"
+"(i2p/apps/ministreaming/ and i2p/apps/streaming/)."
+msgstr ""
+"Para hacerse con esta recompensa, un nuevo grupo de tests de unidad \n"
+"debe satisfacer una covertura de código determinada de 90% de la \n"
+"librería streaming (i2p/apps/ministreaming/ y i2p/apps/streaming/)."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102
+msgid "Unit tests coverage"
+msgstr "Covertura de unit tests"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106
+msgid ""
+"To collect this bounty, all above unit tests must meet the 100%\n"
+"coverage marker (except for log statements)."
+msgstr ""
+"Para hacerse con esta recompensa, todos los tests de unidad \n"
+"anteriores deben satisfacer la marca de covertura 100% \n"
+"(excepto para las entradas de registro (`log`)."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113
+msgid "MultiRouter simulation"
+msgstr "Simulación multiruter"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115
+msgid "will be split in more sub-tasks"
+msgstr "será dividido en más sub-tareas"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117
+msgid ""
+"To collect this bounty, the existing in-memory multi-router\n"
+"simulation must be checked, made work again and extend to simulate\n"
+"lots of routers in memory on a single machine. This bounty will\n"
+"be split in more fine grained subworks."
+msgstr ""
+"Para obtener esta recompensa, debe comprobarse y hacer funcionar de nuevo"
+" la ya existente simulación multi-ruter en la memoria, además de poder "
+"simular muchos ruters en la memoria de una única máquina. Esta recompensa"
+" se partirá en otros trabajos menores."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126
+msgid ""
+"Judge on all these works is the donor and donor decides if a phase is\n"
+"called succesfull done and money can be paid."
+msgstr ""
+"El jurado de estas donaciones es el que decide, y el que dona decide si "
+"la fase se ha hecho exitosamente y el dinero puede pagarse."
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2
+msgid "Bounty I2P vuze plugin"
+msgstr "Rcompensa por el pluguin I2P vuze"
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3
+msgid "vuze plugin"
+msgstr "pluguin vuze"
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P torrent P2P I setout the bounty for a working I2P vuze\n"
+"plugin.\n"
+"The plugin needs to be official and submitted to vuze for publication\n"
+"on their webpage/repository for plugins.\n"
+"It should be easy to install and configured, work smooth and flawless.\n"
+"Configuration should be friendly to starters and made easy to be "
+"anonymous.\n"
+"It should work with *.b32.i2p destinations as with signed (516++ bits) \n"
+"destinations."
+msgstr ""
+"Para mejorar el suso de I2P y atraer a más usuarios al uso de torrents en"
+" I2P creo una recompensa por un pluguin de vuze que funcione. El pluguin "
+"tiene que ser oficial y debe aparecer en la web oficial de de vuze. Debe "
+"ser fácil de instalar y utilizar, y funcionar suave y sin problemas. La "
+"configuración debe ser sencillas para la gente nueva y debe proveer "
+"anonimato fácilmente. Debe funcionar con destinaciones b32 y con "
+"destinaciones firmadas (516++ bits)."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:2
+msgid "Application Development"
+msgstr "Desarrollo de aplicaciones "
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:3
+msgid "May 2013"
+msgstr "Mayo de 2013"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:6
+msgid "Application Development Guide"
+msgstr "Guía de desarrollo de aplicaciones"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:8
+msgid "Contents"
+msgstr "Contenido"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:10
+#: i2p2www/pages/site/get-involved/develop/applications.html:16
+msgid "Why write I2P-specific code?"
+msgstr "¿Porqué escribir código específico para I2P?"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:11
+#: i2p2www/pages/site/get-involved/develop/applications.html:102
+msgid "Important concepts"
+msgstr "Conceptos importantes"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:12
+#: i2p2www/pages/site/get-involved/develop/applications.html:190
+msgid "Development options"
+msgstr "Opciones de desarrollo"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:13
+#: i2p2www/pages/site/get-involved/develop/applications.html:303
+msgid "Start developing - a simple guide"
+msgstr "Empiece a programar - una guía simple"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:18
+#, python-format
+msgid ""
+"There are multiple ways to use applications in I2P.\n"
+"Using I2PTunnel,\n"
+"you can use regular applications without needing to program explicit I2P "
+"support.\n"
+"This is very effective for client-server scenario's,\n"
+"where you need to connect to a single website.\n"
+"You can simply create a tunnel using I2PTunnel to connect to that "
+"website, as shown in Figure 1."
+msgstr ""
+"Hay múltiples formas de usar aplicaciones en I2P. Usando los I2PTunnel puede utilizar aplicaciones normales"
+" sin que los programas tengan que tener soporte explícito para i2P. Esto "
+"es muy eficiente en escenarios cliente-servidor, cuando se necesita "
+"conectar con una sola web. Simplemente puede crear un túnel usando "
+"I2PTunnel para conectarse a la web, como se puede ver en la Figura 1."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:26
+msgid ""
+"If your application is distributed, it will require connections to a "
+"large amount of peers.\n"
+"Using I2PTunnel, you will need to create a new tunnel for each peer you "
+"want to contact,\n"
+"as shown in Figure 2.\n"
+"This process can of course be automated, but running a lot of I2PTunnel "
+"instances creates a large amount of overhead.\n"
+"In addition, with many protocols you will need to force everyone to \n"
+"use the same set of ports for all peers - e.g. if you want to reliably "
+"run DCC \n"
+"chat, everyone needs to agree that port 10001 is Alice, port 10002 is "
+"Bob, port \n"
+"10003 is Charlie, and so on, since the protocol includes TCP/IP specific "
+"information\n"
+"(host and port)."
+msgstr ""
+"Si su aplicación es distribuida, requerirá la conexión de un gran número "
+"de pares. Usando un I2PTunnel necesitaría crear un túnel por cada para "
+"que quiera conectar, como se ve en la Figura 2. Este procese puede ser "
+"automatizado, por supuesto, pero ejecutar muchas instancias de I2PTunnel "
+"crea mucha sobrecarga. Además, con muchos protocolos tendría que forzar a"
+" todos a usar los mismos puertos para todos los pares -  por ejemplo, si "
+"desea habilitar DCC, todos necesitarían llegar al acuerdo de que el "
+"puerto 10001 es para Alice, el puerto 10002 para Bob, el puerto 10003 "
+"para Charlie, y así, ya que el protocolo incluye información específica "
+"TCP/IP (servidor y puerto)."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:37
+msgid ""
+"General network applications often send a lot of additional data that "
+"could be used to identify users.\n"
+"Hostnames, port numbers, time zones, character sets, etc. are often sent "
+"without informing the user.\n"
+"As such, designing the network protocol specifically with anonymity in "
+"mind\n"
+"can avoid compromising user identities."
+msgstr ""
+"Las aplicaciones  de red habitualmente envían mucha información adicional"
+" que puede identificar a los usuarios. Los nombres de los hosts, puertos,"
+" horarios, etc, a veces son enviados sin informar al usuario. Por lo que "
+"el diseñar los protocolos de red con el anonimato en mente puede evitar "
+"comprometer las identidades de los usuarios."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:43
+msgid ""
+"There are also efficiency considerations to review when determining how "
+"to \n"
+"interact on top of I2P.  The streaming library and things built on top of"
+" it\n"
+"operate with handshakes similar to TCP, while the core I2P protocols "
+"(I2NP and I2CP)\n"
+"are strictly message based (like UDP or in some instances raw IP).  The "
+"important\n"
+"distinction is that with I2P, communication is operating over a long fat "
+"network - \n"
+"each end to end message will have nontrivial latencies, but may contain "
+"payloads \n"
+"of up to several KB.  An application that needs a simple request and "
+"response can get rid\n"
+"of any state and drop the latency incurred by the startup and teardown "
+"handshakes\n"
+"by using (best effort) datagrams without having to worry about MTU "
+"detection or \n"
+"fragmentation of messages."
+msgstr ""
+"También hay que tomar consideraciones sobre la eficiencia cuando se "
+"determina como funcionar sobre I2P. La librería de streaming y las cosas "
+"construidas sobre ellas funcionan con handshakes similares a los de TCP, "
+"mientras que los protocolos del núcleo de I2P (I2NP e I2CP) son "
+"estrictamente basados en mensajes (como UDP). La diferencia más "
+"importante es que con I2P las comunicaciones funcionan sobre una red "
+"grande y gorda, cada mensaje de fin a fin tendrá latencias no triviales, "
+"y puede contener cargas de varios KB. Una aplicación que necesite una "
+"simple petición y respuesta puede evitar cualquier estado y evitar los "
+"retardos con los handshakes de inicio usando (mejor esfuerzo) datagramas "
+"sin tener que preocuparse sobre la detección de MTU o la fragmentación de"
+" los mensajes."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:57
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid ""
+"Creating a server-client connection using I2PTunnel only requires "
+"creating a single tunnel."
+msgstr ""
+"Crear una conexión servidor-cliente usando un I2PTunnel sólo requiere "
+"crear un solo túnel."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid "Figure 1:"
+msgstr "Figura 1:"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:64
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid ""
+"Setting up connections for a peer-to-peer applications requires a very "
+"large amount of tunnels."
+msgstr ""
+"Configurar conexiones para aplicaciones p2p requiere un gran número de "
+"túneles."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid "Figure 2:"
+msgstr "Fugura 2:"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:70
+msgid "In summary, a number of reasons to write I2P-specific code:"
+msgstr ""
+"En resumen, hay bastantes razones para escribir el código específico para"
+" I2P:"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:74
+msgid ""
+"Creating a large amount of I2PTunnel instances consumes a non-trivial "
+"amount of resources,\n"
+"which is problematic for distributed applications (a new tunnel is "
+"required for each peer)."
+msgstr ""
+"Crear un gran número de I2PTunnles consume una cantidad de recursos nada "
+"triviales, lo cual es problemático para las aplicaciones distribuidas "
+"(hace falta un  nuevo túnel por cada par)."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:78
+msgid ""
+"General network protocols often send a lot of additional data that can be"
+" used to identify users.\n"
+"Programming specifically for I2P allows the creation of a network "
+"protocol\n"
+"that does not leak such information, keeping users anonymous and secure."
+msgstr ""
+"Los protocolos de red generales a menudo envían mucha información "
+"adicional que puede usarse para identificar a los usuarios. Programar "
+"específicamente para I2P permite la creación de protocolos de red que no "
+"filtran dicha información no deseada, permitiendo que los usuarios "
+"permanezcan seguros y anónimos."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:83
+msgid ""
+"Network protocols designed for use on the regular internet can be "
+"inefficient\n"
+"on I2P, which is a network with a much higher latency."
+msgstr ""
+"Los protocolos de red diseñados para el Internet normal pueden ser "
+"ineficientes sobre I2P, que es una red con una latencia mayor."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:90
+#, python-format
+msgid ""
+"I2P supports a standard plugins interface for"
+" developers\n"
+"so that applications may be easily integrated and distributed."
+msgstr ""
+"I2P soporta un interfaz de plugins estándar  "
+"para los desarrolladores, con lo que las aplicaciones pueden ser "
+"integradas y distribuidas más fácilmente."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:96
+msgid ""
+"Applications written in Java and accessible/runnable\n"
+"using an HTML interface via the standard webapps/app.war\n"
+"may be considered for inclusion in the i2p distribution."
+msgstr ""
+"Las aplicaciones escritas en Java y accesibles/ejecutables usando un "
+"interfaz HTML a través de aplicaciones web estándar pueden considerarse "
+"para incluirse en la distribución I2P."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:104
+msgid "There are a few changes that require adjusting to when using I2P:"
+msgstr "Hay varios cambios que se requieren ajustar cuando se usa I2P."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:108
+msgid "Destination ~= host+port"
+msgstr "Destinación ~= host+puerto"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:110
+msgid ""
+"An application running on I2P sends messages from and receives messages "
+"to a\n"
+"unique cryptographically secure end point - a \"destination\".  In TCP or"
+" UDP\n"
+"terms, a destination could (largely) be considered the equivalent of a "
+"hostname\n"
+"plus port number pair, though there are a few differences."
+msgstr ""
+"Una aplicación ejecutándose sobre I2P envía un mensaje desde, y recibe "
+"mensajes hacia un único punto seguro criptográfico. - una "
+"\"destinación\". En términos de TCP y UDP una destinación puede ser "
+"considerada (en gran parte) el equivalente a un hostname más el par de "
+"números de puertos, aunque hay unas pocas diferencias."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:118
+msgid ""
+"An I2P destination itself is a cryptographic construct - all data sent to"
+" one is \n"
+"encrypted as if there were universal deployment of IPsec with the "
+"(anonymized)\n"
+"location of the end point signed as if there were universal deployment of"
+" DNSSEC."
+msgstr ""
+"Una destinación I2P es en sí misma  una construcción criptográfica - toda"
+" la información enviada es cifrada tal y como si hubiera una "
+"implementación mundial de IPsec con la localización (anónima) del punto "
+"final firmado como si existiera una implementación universal de DNSSEC."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:123
+msgid ""
+"I2P destinations are mobile identifiers - they can be moved from one I2P "
+"router\n"
+"to another (or it can even \"multihome\" - operate on multiple routers at"
+"\n"
+"once).  This is quite different from the TCP or UDP world where a single "
+"end point (port)\n"
+"must stay on a single host."
+msgstr ""
+"Las destinaciones de I2P son identificadores móviles - pueden ser movidas"
+" de un ruter I2P a otro ( o incluso pueden ser \"multi-hogar\" - "
+"funcionar en varios ruters a la vez). Esto es bastante diferente a como "
+"funcionan TCP y UDP, donde un un solo punto final (puerto) tiene que "
+"estar en un solo host."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:130
+msgid ""
+"I2P destinations are ugly and large - behind the scenes, they contain a "
+"2048 bit ElGamal\n"
+"public key for encryption, a 1024 bit DSA public key for signing, and a "
+"variable size \n"
+"certificate, which may contain proof of work or blinded data."
+msgstr ""
+"Las destinaciones I2P son largas y feas - en el fondo contienen un clave "
+"pública ElGamal de 2048 bits para el cifrado, una calve pública  DSA de "
+"1024 bits para firmar, y un certificado de tamaño variable, que puede "
+"contener una prueba de trabajo realizado o información blindada."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:135
+#, python-format
+msgid ""
+"There are existing ways to refer to these large and ugly destinations by "
+"short\n"
+"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not "
+"guarantee\n"
+"globally uniqueness (since they're stored locally in a database on each "
+"person's machine)\n"
+"and the current mechanism is not especially scalable nor secure (updates "
+"to the host list are\n"
+"managed using \"subscriptions\" to naming services).\n"
+"There may be some secure, human readable, scalable, and globally \n"
+"unique, naming system some day, but applications shouldn't depend upon it"
+" being in place,\n"
+"since there are those who don't think such a beast is possible.\n"
+"Further information on the naming system is "
+"available."
+msgstr ""
+"Hay formas de referirse a esa larga y fea destinación acortándola con "
+"nombres bonitos (por ejemplo \"irc.duck.i2p\"), pero estas técnicas no "
+"garantizan una unicidad global (ya que están almacenadas localmente en la"
+" base de datos de la máquina de cada persona) y el mecanismo actual no es"
+" especialmente escalable o seguro (las actualizaciones de la lista de "
+"hosts son manejadas usando \"suscripciones\" a servicios de nombres). "
+"Quizás algún día habrá un sistema más seguro, legible por humanos, "
+"escalable y con unicidad global, pero las aplicaciones no deberían "
+"depender de su existencia, ya que hay gente que piensa que ese tipo de "
+"bestia no es posible. Hay disponible más "
+"información sobre el sistema de nombres."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:149
+#, python-format
+msgid ""
+"While most applications do not need to distinguish protocols and ports,\n"
+"I2P does support them. Complex applications may specify a "
+"protocol,\n"
+"from port, and to port, on a per-message basis, to multiplex traffic on\n"
+"a single destination.\n"
+"See the datagram page for details.\n"
+"Simple applications operate by listening for \"all protocols\" on \"all "
+"ports\" of a destination."
+msgstr ""
+"Mientras que la mayoría de las aplicaciones no necesitan distinguir "
+"protocolos o puertos, I2P si los soporta. Las aplicaciones "
+"complejas pueden especificar un protocolo, desde un puerto, y hacia un "
+"puerto, en un mensaje, hacia tráfico múltiple o sobre una sola "
+"destinación. Vea la página de datagrama "
+"para más detalles. Las aplicaciones simples funciona escuchando por "
+"\"todos los protocolos\" sobre \"todos los puertos\" de una destinación."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:158
+msgid "Anonymity and confidentiality"
+msgstr "Anonimato y confidencialidad."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:160
+msgid ""
+"I2P has transparent end to end encryption\n"
+"and authentication for all data passed over the network - if Bob sends to"
+" Alice's destination,\n"
+"only Alice's destination can receive it, and if Bob is using the "
+"datagrams or streaming \n"
+"library, Alice knows for certain that Bob's destination is the one who "
+"sent the data."
+msgstr ""
+"I2P tiene cifrado transparente y autenticación transparente de todos los "
+"datos que pasan por la red - si Bob envía a la destinación de Alice, sólo"
+" la destinación de Alice puede recibirlo, y si Bob está usando la "
+"librería de datagramas o streaming, Alice sabe seguro que la destinación "
+"de Bob es la que envió los datos."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:167
+msgid ""
+"Of course, I2P transparently anonymizes the\n"
+"data sent between Alice and Bob, but it does nothing to anonymize the "
+"content of what they\n"
+"send.  For instance, if Alice sends Bob a form with her full name, "
+"government IDs, and \n"
+"credit card numbers, there is nothing I2P can do.  As such, protocols and"
+" applications should \n"
+"keep in mind what information they are trying to protect and what "
+"information they are willing\n"
+"to expose."
+msgstr ""
+"Por supuesto, I2P anonimiza transparentemente los datos enviados entre "
+"Alice y Bob, pero no hace nada para anonimizar el contenido de lo que "
+"envían. Por ejemplo, si Alice envía a Bob un formulario con su nombre "
+"completo, ID del gobierno, y los números de sus tarjetas de crédito, no "
+"hay nada que I2P pueda hacer. Por eso, los protocolos y las aplicaciones "
+"deben tener en cuenta qué información están intentando proteger y qué "
+"información desean exponer."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:176
+msgid "I2P datagrams can be up to several KB"
+msgstr "Los datagramas I2P pueden ser hasta de varios KB"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:178
+#, python-format
+msgid ""
+"Applications that use I2P datagrams (either raw or repliable ones) can "
+"essentially be thought\n"
+"of in terms of UDP - the datagrams are unordered, best effort, and "
+"connectionless - but unlike\n"
+"UDP, applications don't need to worry about MTU detection and can simply "
+"fire off large datagrams.\n"
+"While the upper limit is nominally 32 KB, the message is fragmented for "
+"transport, thus dropping\n"
+"the reliability of the whole. Datagrams over about 10 KB are not "
+"currently recommended.\n"
+"See the datagram page for details.\n"
+"For many applications, 10 KB of data is sufficient for an\n"
+"entire request or response, allowing them to transparently operate in I2P"
+" as a UDP-like \n"
+"application without having to write fragmentation, resends, etc."
+msgstr ""
+"Las aplicaciones que usan datagramas I2P (ya sean en bruto o "
+"respondibles) pueden entenderse en términos de UDP - los datagramas no "
+"están ordenados, mejor esfuerzo, y sin-conexión - pero al contrario que "
+"UDP, las aplicaciones no tienen que preocuparse de la detección MTU y "
+"pueden simplemente enviar datagramas grandes. Cuando normalmente el "
+"límite superior es de 32 KB, el mensaje es troceado para el transporte, "
+"bajando la confiabilidad del todo. No se recomiendan datagramas de más de"
+" 10 KB. Ve la página de los datagramas para"
+" más detalles. Para muchas aplicaciones, esos 10 KB de datos es "
+"suficiente para una petición o respuesta completa, permitiendoles operar "
+"transparentemente en I2P como una aplicación tipo UDP si tener que crear "
+"fragmentaciones, re-eenvíos, etc."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:192
+msgid ""
+"There are several means of sending data over I2P, each with their own "
+"pros and cons.\n"
+"The streaming lib is the recommended interface, used by the majority of "
+"I2P applications."
+msgstr ""
+"Hay varias formas de enviar datos sobre I2P, cada una con sus ventajas e "
+"inconvenientes. La librería de streaming es el interfaz recomendado, "
+"usado por la mayoría de las aplicaciones de I2P."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:197
+msgid "Streaming Lib"
+msgstr "Librería Streaming"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:198
+#, python-format
+msgid ""
+"The full streaming library is now the "
+"standard\n"
+"interface. It allows programming using TCP-like sockets, as explained in "
+"the Streaming development guide."
+msgstr ""
+"La librería de streaming completa es ahora "
+"mismo el interfaz estándar. Permite programar usando sockets al estilo "
+"TCP, como se explica en la guía de "
+"desarrollo de Streaming."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:204
+#, python-format
+msgid ""
+"BOB is the Basic Open Bridge,\n"
+"allowing an application in any language to make streaming connections \n"
+"to and from I2P. At this point in time it lacks UDP support, but UDP "
+"support\n"
+"is planned in the near future. BOB also contains several tools, such as \n"
+"destination key generation, and verification that an address conforms to"
+" \n"
+"I2P specifications. Up to date info and applications that use BOB can be"
+" \n"
+"found at this eepsite."
+msgstr ""
+"BOB es el  Basic Open Bridge, puente básico "
+"abierto/libre, permite a cualquier aplicación en cualquier lenguaje "
+"hacer conexiones de streaming hacia y desde I2P. En este momento aún le "
+"falta el soporte UDP, pero el soporte UDP está planeado para un futuro "
+"cercano. BOB además contiene varias herramientas, como el generar claves "
+"de destino, y el verificar que una dirección  se ajusta a las "
+"especificaciones de I2P. Información actualizada y una lista de "
+"aplicaciones que usan BOB pueden encontrarse en esta eepsite."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:217
+msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
+msgstr "No se recomienda SAM, SAM v2 vale, pero se recomienda SAM v3"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:218
+#, python-format
+msgid ""
+"SAM is the Simple Anonymous Messaging protocol, "
+"allowing an\n"
+"application written in any language to talk to a SAM bridge through a "
+"plain TCP socket and have\n"
+"that bridge multiplex all of its I2P traffic, transparently coordinating "
+"the encryption/decryption\n"
+"and event based handling.  SAM supports three styles of operation:"
+msgstr ""
+"SAM es el protocolo de Simple Anonymous Messaging, "
+"mensajería anónima simple, que permite a una aplicación escrita en "
+"cualquier lenguaje entenderse con el puente SAM a través de sockets TCP y"
+" en donde ese puente multiplexa todo su tráfico I2P, coordinando el "
+"cifrado/descifrado transparentemente y el manejo de los eventos. SAM "
+"soporta tres tipos de operaciones:"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:225
+msgid ""
+"streams, for when Alice and Bob want to send data to each other reliably "
+"and in order"
+msgstr ""
+"streams, para cuando Alice y Bob quieren enviar datos de uno a otro "
+"seguramente y en orden"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:228
+msgid ""
+"repliable datagrams, for when Alice wants to send Bob a message that Bob "
+"can reply to"
+msgstr ""
+"datagramas respondibles, para cuando Alice quiere enviar a Bob un mensaje"
+" al que Bob puede responder."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:231
+msgid ""
+"raw datagrams, for when Alice wants to squeeze the most bandwidth and "
+"performance as possible,\n"
+"and Bob doesn't care whether the data's sender is authenticated or not "
+"(e.g. the data transferred\n"
+"is self authenticating)"
+msgstr ""
+"datagramas en bruto, para cuando Alice quiere ahorrar el máximo ancho de "
+"banda y obtener el mejor rendimiento, y a Bob no le importa si la "
+"información del remitente está autentificada o no (por ejemplo cuando los"
+" datos transferidos ya son auto autentificables)"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:237
+msgid ""
+"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n"
+"multiplexing/demultiplexing. Each I2P stream is handled by its own socket"
+" between the application\n"
+"and the SAM bridge. Besides, datagrams can be sent and received by the "
+"application through datagram\n"
+"communications with the SAM bridge."
+msgstr ""
+"SAM V3 apunta hacia la misma meta que SAM y SAM V2, pero no requiere \n"
+"multiplexado/demultiplexado. Cada flujo (`stream`) I2P es gestionado por "
+"su propio socket \n"
+"entre la aplicación y la pasarela (`bridge`) SAM. Además, pueden ser "
+"enviados y \n"
+"recibidos datagramas mediante la aplicación a través de comunicaciones de"
+" datagrama con\n"
+"la pasarela SAM."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:244
+#, python-format
+msgid ""
+"SAM V2 is a new version used by imule\n"
+"that fixes some of the problems in SAM.\n"
+"
            \n"
+"SAM V3 is used by imule since version 1.4.0."
+msgstr ""
+"SAM V2 es una nueva versión usada por imule que"
+"\n"
+"resuelve alguno de los problemas en SAM.\n"
+"
            \n"
+"SAM V3 es usado desde la versión 1.4.0 de imule."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:252
+msgid ""
+"The I2PTunnel application allows applications to build specific TCP-like "
+"tunnels to peers \n"
+"by creating either I2PTunnel 'client' applications (which listen on a "
+"specific port and connect\n"
+"to a specific I2P destination whenever a socket to that port is opened) "
+"or I2PTunnel 'server'\n"
+"applications (which listen to a specific I2P destination and whenever it "
+"gets a new I2P \n"
+"connection it outproxies to a specific TCP host/port).  These streams are"
+" 8-bit clean, and are\n"
+"authenticated and secured through the same streaming library that SAM "
+"uses, but there is a \n"
+"nontrivial overhead involved with creating multiple unique I2PTunnel "
+"instances, since each have\n"
+"their own unique I2P destination and their own set of tunnels, keys, etc."
+msgstr ""
+"La aplicación I2PTunnel permite a otras aplicaciones establecer túneles "
+"específicos\n"
+"tipo-TCP hacia los pares ('peers'), creando tanto aplicaciones I2PTunnel "
+"'cliente' (que escuchan\n"
+"en un puerto específico y se conectan a un destino I2P específico cuando "
+"un socket\n"
+"hacia ese puerto se abre) como aplicaciones I2PTunnel 'servidor' (que "
+"escuchan un destino\n"
+"I2P específico y cuando reciben una nueva conexión I2P se interponen "
+"repitiéndola\n"
+"hacia un anfitrión('host')/puerto específico). Estos flujos ('streams') "
+"son puros de 8-bits\n"
+"('8-bit clean') y son autentificados y asegurados a través de la misma "
+"librería que usa SAM,\n"
+"pero crear múltiples instancias I2PTunnel únicas reviste una sobrecarga "
+"no trivial, ya que\n"
+"cada una tiene su propio destino único I2P y su propio grupo de túneles, "
+"claves, etc."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:264
+msgid ""
+"I2P supports a SOCKS V4 and V5 proxy.\n"
+"Outbound connections work well. Inbound (server) and UDP functionality "
+"may be incomplete\n"
+"and untested."
+msgstr ""
+"I2P soporta un proxy SOCKS V4 y V5.\n"
+"Las conexiones salientes funcionan bien. La funcionalidad de las\n"
+"conexiones entrantes (servidor) y UDP puede ser incompleta y no testada."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:271
+msgid "Removed"
+msgstr "Eliminado"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:272
+msgid ""
+"There used to be a simple \"ministreaming\" library,\n"
+"but now ministreaming.jar contains only the interfaces for the full "
+"streaming library."
+msgstr ""
+"Suele haber una librería sencilla \"ministreaming\", pero "
+"ministreaming.jar\n"
+"ahora contiene sólo las interfaces para la librería streaming completa."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:277
+msgid "Datagrams"
+msgstr "Datagramas"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:278
+msgid "Recommended for UDP-like applications"
+msgstr "Recomendado para aplicaciones tipo-UDP"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:279
+#, python-format
+msgid ""
+"The Datagram library allows sending UDP-"
+"like packets.\n"
+"It's possible to use:"
+msgstr ""
+"La librería Datagram permite enviar "
+"paquetes tipo-UDP.\n"
+"Es posible usar:"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:284
+msgid "Repliable datagrams"
+msgstr "datagramas respondibles"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:285
+msgid "Raw datagrams"
+msgstr "Datagramas crudos ('raw')"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:289
+msgid "Not recommended"
+msgstr "No recomendado"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:290
+#, python-format
+msgid ""
+"I2CP itself is a language independent protocol, "
+"but to implement an I2CP library \n"
+"in something other than Java there is a significant amount of code to be "
+"written (encryption routines, \n"
+"object marshalling, asynchronous message handling, etc).  While someone "
+"could write an I2CP library in \n"
+"C or something else, it would most likely be more useful to use the C SAM"
+" library instead."
+msgstr ""
+"I2CP en si mismo es un protocolo independiente "
+"del lenguaje, pero para implementar\n"
+"una librería I2CP en cualquier otra cosa que no sea Java hay una cantidad"
+" de código significativa a escribir\n"
+"(rutinas de cifrado, serialización ('marshalling') de objetos, gestión de"
+" mensajes asíncronos, etc.). Aunque\n"
+"cualquiera pueda escribir una librería I2CP en C o algún otro lenguaje, "
+"probablemente sería más útil usar\n"
+"la librería C SAM en su lugar."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:297
+msgid "Web Applications"
+msgstr "Aplicaciones web"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:298
+msgid ""
+"I2P comes with the Jetty webserver, and configuring to use the Apache "
+"server instead is straightforward.\n"
+"Any standard web app technology should work."
+msgstr ""
+"I2P viene con el servidor web Jetty, pero configurar el servidor Apache "
+"para usarlo en su lugar también es apropiado.\n"
+"Cualquier tecnología de aplicaciones web estandar debería funcionar."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:304
+msgid ""
+"Developing using I2P requires a working I2P installation and a "
+"development environment of your own choice.\n"
+"If you are using Java, you can start development with the streaming library or datagram library.\n"
+"Using another programming language, SAM or BOB can be used."
+msgstr ""
+"Desarrollar usando I2P requiere una instalación I2P funcional y un "
+"entorno de desarrollo de su\n"
+"propia elección. Si esta usando Java puede iniciar el desarrollo con la "
+"librería streaming\n"
+"o la librería datagram. Usando otro lenguaje de programación, se puede\n"
+"usar SAM o BOB."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:310
+msgid "Developing with the streaming library"
+msgstr "Desarrollo con la librería streaming"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:312
+msgid ""
+"The following example shows how to create TCP-like client and server "
+"applications\n"
+"using the streaming library."
+msgstr ""
+"El siguiente ejemplo muestra como crear aplicaciones cliente y servidor "
+"tipo-TCP\n"
+"usando la librería streaming."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:317
+msgid "This will require the following libraries in your classpath:"
+msgstr ""
+"Esto requerirá las siguientes librerías en su ruta de clases "
+"('classpath'):"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:321
+msgid "The streaming library itself"
+msgstr "La librería streaming en si misma"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:322
+msgid "Factory and interfaces for the streaming library"
+msgstr "El patrón Factory e interfaces para la librería streaming."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:323
+msgid "Standard I2P classes, data structures, API, and utilities"
+msgstr "Clases I2P estandar, estructuras de datos, API y utilidades."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:326
+msgid ""
+"Network communication requires the usage of I2P network sockets.\n"
+"To demonstrate this, we will create an application where a client can "
+"send text messages to a server,\n"
+"who will print the messages and send them back to the client. In other "
+"words, the server will function as an echo."
+msgstr ""
+"La comunicación de red requiere el uso de sockets de red I2P.\n"
+"Para demostrar esto, crearemos una aplicación donde un cliente pueda "
+"enviar mensajes de texto a un servidor,\n"
+"que imprimirá los mensajes y los enviará de vuelta al cliente. En otras "
+"palabras, el servidor funcionará como un eco."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:331
+msgid ""
+"We will start by initializing the server application. This requires "
+"getting an I2PSocketManager\n"
+"and creating an I2PServerSocket.\n"
+"We will not provide the I2PSocketManagerFactory with the saved keys for "
+"an existing Destination,\n"
+"so it will create a new Destination for us.\n"
+"So we will ask the I2PSocketManager for an I2PSession, so we can find out"
+" the Destination that\n"
+"was created, as we will need to copy and paste that information later so "
+"the client can connect to us."
+msgstr ""
+"Comenzaremos por inicializar la aplicación servidor. Esto requiere "
+"obtener un gestor de socket I2P\n"
+"('I2PSocketManager') y crear un socket de servidor I2P "
+"('I2PServerSocket').\n"
+"No proporcionaremos el patrón I2PSocketManagerFactory con las claves "
+"guardadas para un\n"
+"Destino existente, por lo que creará un nuevo Destino para nosotros.\n"
+"Así que pediremos al gestor de socket I2P ('I2PSocketManager') una sesión"
+" I2P ('I2PSession'), para\n"
+"que podamos averiguar el Destino que fue creado, ya que necesitaremos "
+"copiar y pegar esa información\n"
+"más adelante para que el cliente pueda conectarse con nosotros."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:362
+msgid "Code example 1: initializing the server application."
+msgstr "Ejemplo de código 1: inicialización de la aplicación servidor."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:364
+msgid ""
+"Once we have an I2PServerSocket, we can create I2PSocket instances to "
+"accept connections from clients.\n"
+"In this example, we will create a single I2PSocket instance, that can "
+"only handle one client at a time.\n"
+"A real server would have to be able to handle multiple clients.\n"
+"To do this, multiple I2PSocket instances would have to be created, each "
+"in separate threads.\n"
+"Once we have created the I2PSocket instance, we read data, print it and "
+"send it back to the client.\n"
+"The bold code is the new code we add."
+msgstr ""
+"Una vez que tengamos un socket de servidor I2P ('I2PServerSocket'), "
+"podemos crear instancias\n"
+"de socket I2P ('I2PSocket') para aceptar conexiones desde los clientes. "
+"En este ejemplo crearemos\n"
+"una única instancia I2PSocket, que sólo puede gestionar un cliente cada "
+"vez.\n"
+"Un servidor real tendría que ser capaz de gestionar múltiples clientes.\n"
+"Para hacer esto, múltiples instancias I2PSocket tendrían que ser creadas,"
+" en hilos separados cada una.\n"
+"Una vez hayamos creado la instancia I2PSocket, leemos los datos y los "
+"imprimimos y enviamos de vuelta al cliente.\n"
+"El código en negrita es el código nuevo que añadimos."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:448
+msgid "Code example 2: accepting connections from clients and handling messages."
+msgstr ""
+"Ejemplo de código 2: aceptar conexiones desde clientes y gestionar "
+"mensajes."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:452
+msgid ""
+"When you run the above server code, it should print something like this "
+"(but without the line endings, it should just be\n"
+"one huge block of characters):"
+msgstr ""
+"Cuando ejecute el código servidor de arriba, debería imprimir algo como "
+"esto (pero sin los finales de línea,\n"
+"debería ser sólo un enorme bloque de caracteres):"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:466
+msgid ""
+"This is the base64-representation of the server Destination. The client "
+"will need this string to reach the server."
+msgstr ""
+"Esta es la representación-base64 del servidor Destino. El cliente "
+"necesitará esta cadena para alcanzar el servidor."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:470
+msgid ""
+"Now, we will create the client application. Again, a number of steps are "
+"required for initialization.\n"
+"Again, we will need to start by getting an I2PSocketManager.\n"
+"We won't use an I2PSession and an I2PServerSocket this time.\n"
+"Instead, we will use the server Destination string to start our "
+"connection.\n"
+"We will ask the user for the Destination string, and create an I2PSocket "
+"using this string.\n"
+"Once we have an I2PSocket, we can start sending and receiving data to and"
+" from the server."
+msgstr ""
+"Ahora crearemos la aplicación cliente. Otra vez se requiere un "
+"determinado número de pasos para la inicialización.\n"
+"De nuevo, necesitaremos comenzar obteniendo un gestor de socket I2P "
+"('I2PSocketManager').\n"
+"No usaremos una sesión I2P ('I2PSession') ni un socket de servidor I2P "
+"('I2PServerSocket') esta vez.\n"
+"En su lugar usaremos la cadena del servidor Destino para iniciar nuestra "
+"conexión.\n"
+"Preguntaremos al usuario por la cadena Destino, y crearemos un socket I2P"
+" ('I2PSocket') usando esta cadena.\n"
+"Una vez que tengamos el I2PSocket podemos comenzar a enviar y recibir "
+"datos hacia y desde el servidor."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:554
+msgid ""
+"Code example 3: starting the client and connecting it to the server "
+"application."
+msgstr ""
+"Ejemplo de código 3: iniciar el cliente y conectarlo a la aplicación "
+"servidor."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:556
+msgid ""
+"Finally, you can run both the server and the client application.\n"
+"First, start the server application. It will print a Destination string "
+"(like shown above).\n"
+"Next, start the client application. When it requests a Destination "
+"string, you can enter the string printed by the server.\n"
+"The client will then send 'Hello I2P!' (along with a newline) to the "
+"server, who will print the message and send it back to the client."
+msgstr ""
+"Finalmente puede ejecutar ambas aplicaciones cliente y servidor.\n"
+"Primero, inicie la aplicación servidor. Imprimirá una cadena Destino "
+"(como la mostrada arriba).\n"
+"Después inicie la aplicación cliente. Cuando esta solicite una cadena "
+"Destino, puede introducir la cadena impresa por el servidor.\n"
+"Entonces el cliente enviará 'Hello I2P!' (junto con un caracter de nueva "
+"línea ('newline')) al servidor, que imprimirá el mensaje\n"
+"y lo enviará de vuelta al cliente."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:562
+msgid "Congratulations, you have successfully communicated over I2P!"
+msgstr "¡Felicidades!, se ha comunicado con éxito sobre I2P"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:566
+msgid "Existing Applications"
+msgstr "Aplicaciones existentes"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:567
+msgid "Contact us if you would like to contribute."
+msgstr "Contáctenos si quiere contribuír."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:588
+msgid "Application Ideas"
+msgstr "Ideas para aplicaciones"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:590
+msgid "NNTP server - there have been some in the past, none at the moment"
+msgstr "Servidor NNTP - ha habido algunos en el pasado, ninguno en este momento"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:593
+msgid ""
+"Jabber server - there have been some in the past, and there is one at the"
+" moment, with access to the public internet"
+msgstr ""
+"Servidor Jabber - ha habido algunos en el pasado, y hay uno en este "
+"momento con acceso a la Internet pública"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:596
+msgid "PGP Key server and/or proxy"
+msgstr "Servidor de claves PGP y/o proxy"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:599
+msgid ""
+"Content Distribution / DHT applications - resurrect feedspace,\n"
+"port dijjer, look for alternatives"
+msgstr ""
+"Distribución de contenidos / Aplicaciones DHT - resucite Feedspace,\n"
+"porte Dijjer, busque alternativas"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:603
+msgid "Help out with Syndie development"
+msgstr "Contribuya al desarrollo de Syndie"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:606
+msgid ""
+"Web-based applications - The sky is the limit for hosting web-server-"
+"based\n"
+"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n"
+"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work."
+msgstr ""
+"Aplicaciones basadas-en-web - El cielo es el límite para el hospedaje de\n"
+"aplicaciones basadas-en-servidor-web tales como blogs, tablones de\n"
+"anotaciones ('pastebins'), almacenamiento, seguimiento, actualización de\n"
+"publicaciones ('feeds'), etc. Cualquier web o tecnología CGI como Perl,\n"
+"PHP, Python o Ruby funcionará."
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:611
+msgid ""
+"Resurrect some old apps, several previously in the i2p source package -\n"
+"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace"
+msgstr ""
+"Resucite algunas aplicaciones viejas, varias presentes previamente en el\n"
+"paquete fuente de I2P - Bogobot, Pants, Proxyscript, Q, Stasher,\n"
+"Socks Proxy, I2Ping, Feedspace"
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2
+msgid "I2P Developer's MTN Keys"
+msgstr "Claves MTN de desarrollador I2P"
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4
+msgid "MTN Keys"
+msgstr "Claves MTN"
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5
+msgid ""
+"Monotone servers used by the I2P project require two types of keys to be "
+"used."
+msgstr ""
+"Los servidores Monotone usados por el proyecto I2P requieren el uso de "
+"dos tipos de claves."
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
+msgid ""
+"Commit Keys to sign changes checked-in to the "
+"respository; and"
+msgstr ""
+"Claves de consignación ('commit') para firmar "
+"cambios registrados en el repositorio; y"
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10
+msgid ""
+"Transport Keys to push changes to remote "
+"servers."
+msgstr ""
+"Claves de transporte para impulsar cambios en "
+"servidores remotos."
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13
+#, python-format
+msgid ""
+"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
+"import the\n"
+"developer commit keys, but only Monotone \n"
+"server operators will need to import the transport keys."
+msgstr ""
+"Cualquiera que use Monotone para revisar el código fuente de I2P\n"
+"necesitará importar las claves de consignación ('commit') de\n"
+"desarrollador, pero sólo los operadores de servidor Monotone\n"
+"necesitarán importar las claves de transporte."
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20
+msgid "Developer Commit keys"
+msgstr "Claves de consignación ('commit') de desarrollador"
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:255
+msgid "Developer Transport Keys"
+msgstr "Claves de transporte de desarrollador"
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:256
+#, python-format
+msgid ""
+"Note: Transport keys are only needed for setting up a\n"
+"Monotone server."
+msgstr ""
+"Nota: Las claves de transporte sólo son necesarias para configurar"
+"\n"
+"un servidor "
+"Monotone."
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
+msgid "License Agreements"
+msgstr "Acuerdos de licencia"
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
+#, python-format
+msgid "For more information see the licenses page."
+msgstr ""
+"Para mayor información vea la página de "
+"licencias."
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8
+msgid ""
+"Following is a monotonerc file defining the current trust list.\n"
+"Developers must use this file in ~/.monotone/monotonerc or\n"
+"_MTN/montonerc in their i2p.i2p workspace."
+msgstr ""
+"A continuación está un archivo `monotonerc` que define el listado actual"
+" \n"
+"de confianza. Los desarrolladores deben usar este fichero en \n"
+"~/.monotone/monotonerc o _MTN/montonerc en sus espacio de trabajo i2p.i2p "
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17
+msgid "Agreements"
+msgstr "Acuerdos"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:2
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115
+msgid "Licenses"
+msgstr "Licencias"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:4
+msgid "I2P Software Licenses"
+msgstr "Licencias de software I2P"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:5
+#, python-format
+msgid ""
+"As required by our\n"
+"threat model (among other reasons), the \n"
+"software developed to support the anonymous communication \n"
+"network we call I2P must be freely available, open source, \n"
+"and user modifiable.  To meet these criteria, we make use of\n"
+"a variety of legal and software engineering techniques so\n"
+"as to remove as many barriers to entry for those considering\n"
+"making use of or contributing to the I2P effort."
+msgstr ""
+"Como requiere nuestro modelo de amenaza \n"
+"(entre otras razones), el software\n"
+"desarrollado para soportar la red de comunicación anónima que llamamos "
+"I2P, debe \n"
+"ser accesible libremente, de código abierto, y modificable por el "
+"usuario. Para alcanzar \n"
+"estos criterios hacemos uso de una variedad de técnicas legales y de "
+"ingeniería \n"
+"de software, además eliminamos cuantas barreras de entrada haya para "
+"aquellos que\n"
+"consideren hacer uso de, o contribuír al esfuerzo de I2P."
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:16
+msgid ""
+"While the information below may be more confusing than just simply \n"
+"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
+"the short answer to the question \"How is I2P licensed?\" is this:"
+msgstr ""
+"Aunque la información de debajo puede ser más bien confusa que sencilla,"
+" \n"
+"estableciendo que \"I2P es BSD\", \"I2P es GPL\", o \"I2P es dominio "
+"público\", \n"
+"la respuesta corta a la pregunta \"¿Cómo está licenciado I2P?\" es esta: "
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:22
+msgid "All software bundled in the I2P distributions will allow:"
+msgstr "Todo el software empaquetado en las distribuciones I2P permitirá:"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:24
+msgid "use without fee"
+msgstr "uso libre de cargo"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:25
+msgid ""
+"use with no restrictions on how, when, where, why, or by whom is running "
+"it"
+msgstr ""
+"uso sin restricciones acerca de cómo, cuándo, dónde, por qué o por quién"
+" \n"
+"se está ejecutando."
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:26
+msgid "access to the source code without fee"
+msgstr "acceso al código fuente libre de cargo"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:27
+msgid "modifications to the source"
+msgstr "modificaciones del código fuente"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:30
+msgid ""
+"Most of the software guarantees much more - the ability of anyone "
+"to \n"
+"distribute the modified source however they choose.  However, not all of "
+"the \n"
+"software bundled provides this freedom - the GPL restricts the ability of"
+" \n"
+"developers who wish to integrate I2P with their own applications that are"
+" not \n"
+"themselves open source applications.  While we applaud the noble goals of"
+" \n"
+"increasing the resources in the commons, I2P is best served by removing "
+"any\n"
+"barriers that stand in the way of its adoption - if a developer "
+"considering whether\n"
+"they can integrate I2P with their application has to stop and check with "
+"their lawyer,\n"
+"or conduct a code audit to make sure their own source can be released as "
+"GPL-compatible,\n"
+"we lose out."
+msgstr ""
+"La mayoría del software garantiza expresamente - la capacidad \n"
+"de cualquiera de distribuír el código fuente modificado de la "
+"manera que escoja. Sin embargo no todos los paquetes de software otorgan "
+"esta libertad - la GPL restringe la capacidad de los desarrolladores que "
+"deseen integrar I2P en sus propias aplicaciones si estas mismas no son \n"
+"aplicaciones de código abierto. Aunque aplaudimos las nobles metas de "
+"incrementar los recursos abiertos al público, se sirve mejor a I2P "
+"eliminando \n"
+"cualquier barrera que se encuentre en el camino de su adopción - si un "
+"desarrollador\n"
+"que considerando si puede o no integrar I2P con sus aplicaciones, tiene "
+"que parar \n"
+"a hacer comprobaciones con su abogado o realizar una aditoría para "
+"asegurarse \n"
+"de que su propio código puede ser liberado de forma compatible-con-GPL, "
+"lo estamos haciendo mal."
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:43
+msgid "Component licenses"
+msgstr "Licencias de componentes"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:44
+msgid ""
+"The I2P distribution contains several resources, reflecting the "
+"partitioning of \n"
+"the source code into components.  Each component has its own license, "
+"which all \n"
+"developers who contribute to it agree to - either by explicitly declaring"
+" the release\n"
+"of code committed under a license compatible with that component, or by "
+"implicitly\n"
+"releasing the code committed under the component's primary license.  Each"
+" of these \n"
+"components has a lead developer who has the final say as to what license "
+"is compatible\n"
+"with the component's primary license, and the I2P project manager has the"
+" final say as\n"
+"to what licenses meet the above four guarantees for inclusion in the I2P "
+"distribution."
+msgstr ""
+"La distribución I2P contiene varios recursos, que reflejan la "
+"fragmentación \n"
+"del código fuente en sus diferentes componentes. Cada componente tiene \n"
+"su propia licencia, que todos los desarrolladores que contribuyan con él"
+" \n"
+"tienen que aceptar - bien explícitamente declarando la versión del código"
+" \n"
+"consignada (`committed`) bajo una licencia compatible con ese componente,"
+"\n"
+"o implícitamente publicando el código consignado bajo la licencia "
+"primaria del componente. Cada uno de estos componentes tiene un "
+"desarrollador\n"
+"principal que tiene la última palabra acerca de si una licencia es "
+"compatible con la licencia primaria del compente, y el administrador del "
+"proyecto I2P \n"
+"tiene la última palabra acerca de qué licencias satisfacen las cuatro \n"
+"garantías anteriores para su inclusión en la distribución I2P."
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:57
+msgid "Component"
+msgstr "Componente"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:58
+msgid "Source path"
+msgstr "Ruta del código fuente"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:59
+msgid "Resource"
+msgstr "Recurso"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:60
+msgid "Primary license"
+msgstr "Licencia primaria"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:61
+msgid "Alternate licenses"
+msgstr "Licencias alternativas"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:62
+msgid "Lead developer"
+msgstr "Desarrollador principal"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:271
+msgid "GPL + java exception"
+msgstr "GPL + excepción java"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:272
+#, python-format
+msgid ""
+"While it may be redundant, just for clarity the\n"
+"GPL'ed code included within\n"
+"I2PTunnel and other apps must be released under the GPL with an "
+"additional \"exception\"\n"
+"explicitly authorizing the use of Java's standard libraries:"
+msgstr ""
+"Aunque puede ser redundante, y sólo para dejarlo claro,\n"
+"el código bajo GPL incluído con I2PTunnel\n"
+"y otras aplicaciones, debe ser publicado bajo la GPL con \n"
+"una \"excepción\" adicional explícita autorizando el uso de \n"
+"las librerías estándar de Java:"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:288
+msgid ""
+"All source code under each component will by default be licensed under "
+"the\n"
+"primary license, unless marked otherwise in the code.  All of the above "
+"is\n"
+"summary of the license terms - please see the specific license for the "
+"component\n"
+"or source code in question for authoritative terms.  Component source "
+"locations and\n"
+"resource packaging may be changed if the repository is reorganized."
+msgstr ""
+"Todo código fuente bajo cada componente será licenciado por defecto bajo"
+" \n"
+"la licencia primaria, a menos que otra cosa esté establecida en el "
+"código. \n"
+"Todo lo anterior resume los términos de la licencia - por favor revise la"
+" licencia\n"
+"específica para el componente, o el código fuente en cuestión en busca de"
+" cláusulas \n"
+"autorizativas. Los emplazamientos de los recursos del código de los "
+"componentes \n"
+"y los paquetes podrían cambiar si el repositorio es reorganizado."
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:296
+msgid "Commit privileges"
+msgstr "Privilegios de consignación (`commit`)"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:297
+#, python-format
+msgid ""
+"Developers may push changes to a distributed monotone repository if you\n"
+"receive permission from the person running that repository.\n"
+"See the Monotone Page for details."
+msgstr ""
+"Los desarrolladores pueden impulsar cambios en un repositorio Monotone\n"
+"si reciben permiso de la persona que mantiene ese repositorio.\n"
+"Vea la página de Monotone para mayor detalle."
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:303
+msgid ""
+"However, to have changes included in a release, developers\n"
+"must be trusted by the release manager (currently zzz).\n"
+"In addition, they must explicitly agree with the above terms to be "
+"trusted.\n"
+"That means that they must send one of the release managers a signed "
+"message affirming that:"
+msgstr ""
+"Sin embargo, para poder incluír los cambios en una versión, los \n"
+"desarrolladores deben recibir confianza por parte del administrador\n"
+"de versiones (actualmente `zzz`). Además, deben aceptar explícitamente\n"
+"los téminos anteriores para recibir confianza. Eso significa que deben \n"
+"enviar a uno de los administradores de versiones un mensaje firmado \n"
+"afirmando que:"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:310
+msgid ""
+"Unless marked otherwise, all code I commit is implicitly licensed under\n"
+"the component's primary license"
+msgstr ""
+"A menos que se establezca de otra manera, todo el código que \n"
+"yo consigne está implícitamente licenciado bajo la licencia primaria \n"
+"del componente."
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:314
+msgid ""
+"If specified in the source, the code may be explicitly licensed under one"
+"\n"
+"of the component's alternate licenses"
+msgstr ""
+"Si se especifica en el código fuente, el código puede estar "
+"explícitamente \n"
+"licenciado bajo una de las licencias alternativas del componente."
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:318
+msgid ""
+"I have the right to release the code I commit under the terms I\n"
+"am committing it"
+msgstr ""
+"Tengo derecho a publicar el código que consigne ('commit') bajo los \n"
+"términos con los que lo estoy consignando."
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:324
+#, python-format
+msgid ""
+"If anyone is aware of any instances where the above conditions are not "
+"met,\n"
+"please contact the component lead and/or an I2P release manager with "
+"further\n"
+"information.\n"
+"See developers' license agreements."
+msgstr ""
+"Si alguien advierte alguna instancia donde las condiciones anteriores no "
+"se \n"
+"cumplen, por favor contacte con el encargado del componente y/o con el \n"
+"administrador de versiones de I2P con información detallada. \n"
+"Vea los acuerdos de licencia del "
+"desarrollador."
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
+msgid "Release Signing Key"
+msgstr "Clave de firmado de la versión"
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
+msgid "Releases 0.7.6 and later are signed by zzz. His public key is:"
+msgstr ""
+"Las versiones 0.7.6 y posteriores están firmadas por `zzz`. \n"
+"Su clave pública es:"
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40
+msgid ""
+"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public "
+"key is:"
+msgstr ""
+"Las versiones de la 0.6.1.31 a la 0.7.5 fueron firmadas por "
+"`Complication`. \n"
+"Su clave pública es:"
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2
+msgid "Signed Developer Keys"
+msgstr "Claves firmadas de desarrollador"
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4
+msgid ""
+"Keys for zzz, Complication and welterde are provided clearsigned. The key"
+" for jrandom must be\n"
+"verified differently, since he's away, and only left a binary detached\n"
+"signature for his key."
+msgstr ""
+"Las claves para `zzz`, `Complication` y `welterde` se proporcionan "
+"firmadas de forma \n"
+"transparente (`clearsigned`). La clave para `jrandom` debe ser verificada"
+" de forma diferente, \n"
+"ya que él está fuera y sólo dejó una firma adosada (`detached signature`)"
+" \n"
+"binaria para su clave."
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16
+msgid "Monotone keys for zzz"
+msgstr "Claves Monotone para `zzz`."
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47
+msgid "Monotone keys for welterde"
+msgstr "Claves Monotone para `welterde`."
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79
+msgid "Monotone keys for Complication"
+msgstr "Claves Monotone para `Complication`"
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114
+msgid "Monotone keys for jrandom"
+msgstr "Claves Monotone para `jrandom`"
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
+msgid "Others"
+msgstr "Otros"
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
+msgid ""
+"Tip: To find zzz's GPG key, on his eepsite locate the key "
+"`0xA76E0BED`, with\n"
+"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 "
+"B310 4155\n"
+"76BA A76E 0BED`."
+msgstr ""
+"Consejo: Para encontrar la clave GPG de `zzz`, localice en su \n"
+"eepsite la clave `0xA76E0BED`, con el nombre `zzz@mail.i2p` y la \n"
+"huella de validación de clave (`fingerprint`) \n"
+"`4456 EBBE C805 63FE 57E6 B310 4155 76BA A76E 0BED`."
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49
+msgid ""
+"Tip: To find welterde's GPG key, on public keyservers locate the "
+"key\n"
+"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720"
+" FD81\n"
+"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
+msgstr ""
+"Consejo: Para encontrar la clave GPG de `welterde`, localice en \n"
+"los servidores públicos de claves la clave `0x62E011A1`, con el nombre\n"
+"`welterde@arcor.de` y la huella de validación de clave (`fingerprint`) \n"
+"`6720 FD81 3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81
+msgid ""
+"Tip: To find Complication's GPG key, on his eepsite locate the key"
+"\n"
+"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint "
+"`73CF\n"
+"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
+msgstr ""
+"Consejo: Para encontrar la clave GPG de `Complication`, localice \n"
+"en su eepsite la clave `0x79FCCE33`, con el nombre "
+"`complication@mail.i2p` \n"
+"y la huella de validación de clave (`fingerprint`) \n"
+"`73CF 2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116
+msgid ""
+"Tip: To find jrandom's GPG key for Syndie releases, on public "
+"keyservers locate\n"
+"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n"
+"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
+msgstr ""
+"Consejo: Para encontrar la clave GPG de `jrandom` para versiones \n"
+"de Syndie, localice en los servidores públicos de claves la clave "
+"`0x393F2DF9`, \n"
+"con el nombre `syndie-dist-key@i2p.net` y la huella de validación de "
+"clave (`fingerprint`) \n"
+"`AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122
+msgid ""
+"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n"
+"deployed in the Syndie Monotone repository, in a file named `mtn-"
+"committers`.\n"
+"That file also had a GPG signature, `mtn-committers.sig`, but it was a "
+"binary\n"
+"detached signature. I am going to supply both files in GPG ASCII-armoured"
+" form\n"
+"below."
+msgstr ""
+"`jrandom` tuvo que abandonar inesperadamente al final de 2007. Su clave "
+"de \n"
+"consignación (`commit`) fue desplegada en el repositorio Monotone de \n"
+"Syndie, en un fichero llamado `mtn-committers`. Ese fichero también tuvo"
+" \n"
+"una firma GPG, `mtn-committers.sig`, pero era una firma adosada \n"
+"(`detached signature`) binaria. Voy a suministrar ambos ficheros en la "
+"forma \n"
+"GPG con-armadura-ASCII (`ASCII-armoured`) siguiente."
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130
+msgid ""
+"First, the file `mtn-committers` containing jrandom's Monotone key. Save "
+"as\n"
+"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers "
+"--dearmor\n"
+"mtn-committers.asc`:"
+msgstr ""
+"Primero, el fichero `mtn-committers` conteniendo la clave Monotone de \n"
+"`jrandom`. Guárdelo como `mtn-committers.asc` y desempaquételo usando \n"
+"`gpg --output mtn-committers --dearmor mtn-committers.asc`:"
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151
+msgid ""
+"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n"
+"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-"
+"committers.sig\n"
+"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n"
+"`mtn-committers` file:"
+msgstr ""
+"Ahora el fichero `mtn-committers.sig`, que contiene la firma GPG. "
+"Guárdelo \n"
+"como `mtn-committers.sig.asc` y desempaquételo usando \n"
+"`gpg --output mtn-committers.sig --dearmor mtn-committers.sig.asc`. \n"
+"Úselo para verificar el fichero `mtn-committers` suministrado "
+"anteriormente."
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170
+#, python-format
+msgid ""
+"Some of the developers have included their Monotone keys in their signed license agreement."
+msgstr ""
+"Alguno de los desarrolladores ha incluído sus claves Monotone en sus acuerdos de licencia firmados."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2
+msgid "Developer Guidelines and Coding Style"
+msgstr "Estilo del código y pautas a seguir para los desarrolladores."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4
+#, python-format
+msgid "Read the new developers guide first."
+msgstr "Primero lea la guía para nuevos programadores."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8
+msgid "Basic Guidelines and Coding Style"
+msgstr "Pautas básicas y estilo del código"
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10
+msgid ""
+"Most of the following should be common sense for anybody who has worked "
+"on open source or in a commercial\n"
+"programming envrionment.\n"
+"The following applies mostly to the main development branch i2p.i2p.\n"
+"Guidelines for other branches, plugins, and external apps may be "
+"substantially different;\n"
+"check with the appropriate developer for guidance."
+msgstr ""
+"La mayor parte de lo siguiente debería ser de sentido común para "
+"cualquiera que haya trabajado para proyectos de código libre o en "
+"ambientes de desarrollo comerciales. Lo siguiente se aplica sobre todo "
+"para el desarrollo de la rama principal i2p.i2p. Las guías para otras "
+"ramas, pluguins y aplicaciones externas pueden ser bastante diferentes, "
+"pregúntele al desarrollador indicado en tal caso."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18
+msgid "Community"
+msgstr "Comunidad"
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20
+msgid ""
+"Please don't just \"write code\". If you can, participate in other "
+"development activities, including:\n"
+"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
+"testing;\n"
+"bug reporting and responses; documentation; code reviews; etc."
+msgstr ""
+"Por favor no sólo \"escriba código\". Si puede, participe en otras "
+"actividades de desarrollo como: discusiones sobre el desarrollo y soporte"
+" en el IRC, zzz.i2p, y el foro de.i2p; reporte y solución de errores; "
+"documentación, revisión del código, etc."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25
+msgid ""
+"Active devs should be available periodically on IRC #i2p-dev.\n"
+"Be aware of the current release cycle.\n"
+"Adhere to release milestones such as feature freeze, tag freeze, and\n"
+"the checkin deadline for a release."
+msgstr ""
+"Los programadores activos deberían estar disponibles periódicamente en el"
+" canal #i2p-dev del IRC. Tenga en cuenta el ciclo de liberación de "
+"versiones actual. Fix this! not translated all yet!!! "
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35
+msgid ""
+"Have a basic understanding of distributed source control systems, even if"
+" you haven't\n"
+"used monotone before. Ask for help if you need it.\n"
+"Once pushed, checkins are forever, there is no undo. Please be careful.\n"
+"If you have not used monotone before, start with baby steps.\n"
+"Check in some small changes and see how it goes."
+msgstr ""
+"Debe tener conocimientos básicos del funcionamiento de sistemas de "
+"control de código, incluso si nunca ha usado monotone antes. Pida ayuda "
+"si lo necesita. Una vez subido algo no hay vuelta atrás, no se puede "
+"deshacer, por favor tenga cuidado. Si nunca ha usado monotone antes "
+"empiece con mucho cuidado. Suba pequeños cambios y observe como funciona."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42
+msgid ""
+"Test your changes before checking them in.\n"
+"If you prefer the checkin-before-test development model,\n"
+"use your own development branch (e.g. i2p.i2p.yourname.test)\n"
+"and propagate back to i2p.i2p once it is working well.\n"
+"Do not break the build. Do not cause regressions.\n"
+"In case you do (it happens), please do not vanish for a long period after"
+"\n"
+"you push your change."
+msgstr ""
+"Pruebe los cambios antes de subirlos. Si prefiere el modelo de desarrollo"
+" subir-antes-de-probar use su propia rama de desarrollo (por ejemplo "
+"i2p.i2p.yourname.test) y envíelo de vuelta a i2p.i2p una vez que funcione"
+" correctamente. No rompa la compilación. No cree regresiones. En caso de "
+"que lo haga (a veces ocurre), no desaparezca por mucho tiempo antes de "
+"subir el cambio."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51
+msgid ""
+"If your change is non-trivial, or you want people to test it and need "
+"good test reports\n"
+"to know whether your change was tested or not, add a checkin comment to "
+"history.txt\n"
+"and increment the build revision in RouterVersion.java."
+msgstr ""
+"Si su cambio no es trivial, o desea que otra gente lo pruebe y necesita "
+"reportes fiables para saber si su cambio ha sido probado o no, añada un "
+"comentario de confirmación en history.txt e incremente la versión de "
+"compilación en RouterVersion.java."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56
+msgid ""
+"Ensure that you have the latest monotonerc file in _MTN.\n"
+"Do not check in on top of untrusted revisions."
+msgstr ""
+"Asegúrese de que tiene  la última versión del archivo monotonerc en _MTN."
+" No lo sobrescriba con versiones no confiables."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60
+msgid ""
+"Ensure that you pull the latest revision before you check in.\n"
+"If you inadvertently diverge, merge and push as soon as possible.\n"
+"Don't routinely make others merge for you.\n"
+"Yes, we know that monotone says you should push and then merge,\n"
+"but in our experience, in-workspace merge works just as well as in-"
+"database merge,\n"
+"without creating a merge revision."
+msgstr ""
+"asegúrese que ha descargado la última revisión antes de subir los "
+"cambios. Si crea un divergencia accidentalmente, una y suba tan pronto "
+"como sea posible. No haga que otros lo fusionen rutinariamente por usted."
+" Si, sabemos que monotone indica que debe subir y unir, pero por nuestra "
+"experiencia sabemos que funciona tan bien la unión in-workspace como la "
+"unión n-database si crear una revisión de unión."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
+msgid ""
+"Do not check in major changes into the main i2p.i2p branch late in the "
+"release cycle.\n"
+"If a project will take you more than a couple days, create your own "
+"branch in monotone\n"
+"and do the development there so you do not block releases."
+msgstr ""
+"No suba cambios grandes a la rama principal i2p.i2p al final del ciclo de"
+" versión. Si un proyecto va a tardar más de varios días, cree su propia "
+"rama de monotone y programe allí para no no bloquear la salida de nueva "
+"versiones."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75
+msgid "Coding Style"
+msgstr "Estilo de programación"
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77
+msgid ""
+"Coding style throughout most of the code is 4-spaces for indentation. Do "
+"not use tabs.\n"
+"Do not reformat code. If your IDE or editor wants to reformat everything,"
+" get control of it.\n"
+"Yes, we know 4 spaces is a pain, but perhaps you can configure your "
+"editor appropriately.\n"
+"In some places, the coding style is different.\n"
+"Use common sense. Emulate the style in the file you are modifying."
+msgstr ""
+"El código de estilo en la mayoría de  los casos  es de usar la sangría de"
+" 4 espacios. No use tabulación. No cambie el formato del código. Si su "
+"editor o IDE quiere cambiar el formato configúrelo para que no lo haga. "
+"Sí, sabemos que usar 4 espacios es doloroso, pero probablemente pueda "
+"configurar su editor apropiadamente. En algunos casos el estilo de "
+"programar es diferente, use el sentido común, emule el estilo del archivo"
+" que está modificando."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84
+msgid ""
+"New classes and methods require at least brief javadocs. Add @since "
+"release-number."
+msgstr ""
+"Las nuevas clases y métodos necesitan al menos un javadocs básico. Añada "
+"@since numero-versión."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87
+msgid ""
+"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our "
+"official API.\n"
+"There are several out-of-tree plugins and other applications that rely on"
+" this API.\n"
+"Be careful not to make any changes that break compatibility.\n"
+"Don't add methods to the API unless they are of general utility.\n"
+"Javadocs for API methods should be clear and complete.\n"
+"If you add or change the API, also update the documentation on the "
+"website (i2p.www branch)."
+msgstr ""
+"Las clases del núcleo/ (i2p.jar) y partes de i2ptunnel están incluidas en"
+" el API oficial. \n"
+"Hay varios pluguins y otras aplicaciones que dependen de este API.\n"
+"Tenga cuidado de no hacer cambios que rompan la compatibilidad.\n"
+"No añada métodos al API a no ser que sean de utilidad general.\n"
+"Los Javadocs de los métodos del API deben ser claros y completos.\n"
+"Si añade cambios al API, debe también actualizar la documentación en la "
+"web (i2p.www branch)."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95
+msgid ""
+"Tag strings for translation where appropriate.\n"
+"Don't change existing tagged strings unless really necessary, as it will "
+"break existing translations.\n"
+"Do not add or change tagged strings after the \"tag freeze\" in the "
+"release cycle so that\n"
+"translators have a chance to update before the release."
+msgstr ""
+"Incluya cadenas de texto para la traducción cuando sea apropiado.\n"
+"No cambie las cadenas ya etiquetadas a no ser que sea necesario ya que "
+"rompería las traducciones existentes.\n"
+"No añada o cambie las cadenas después del \"tag freeze\" durante la "
+"liberación de la versión,\n"
+"así los programadores tienen la oportunidad de actualizarlo antes de su "
+"liberación"
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101
+msgid ""
+"Use generics and concurrent classes where possible. I2P is a highly "
+"multi-threaded application."
+msgstr ""
+"Siempre que pueda use clases genéricas y concurrentes. I2P es una "
+"aplicación multi-hilos."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104
+msgid ""
+"We require Java 6 to build but only Java 5 to run I2P.\n"
+"Do not use Java 6 classes or methods without handling the class not found"
+" exceptions\n"
+"and providing alternate Java 5 code. See classes in net.i2p.util for "
+"examples."
+msgstr ""
+"Necesita Java 6 para compilar I2P, pero sólo Java 5 para ejecutarlo.\n"
+"No use las clases o métodos de Java 6 sin encargase antes de las clases "
+"de excepciones not found\n"
+"y de proporcionar el código alternativo para Java 5. Vea los ejemplos de "
+"clases en net.i2p.util."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109
+msgid ""
+"Explicitly convert between primitive types and classes;\n"
+"don't rely on autoboxing/unboxing."
+msgstr ""
+"Convierta explícitamente entre tipos primitivos y clases;\n"
+"no confíe en autoboxing/unboxing."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117
+msgid ""
+"Only check in code that you wrote yourself.\n"
+"Before checking in any code or library jars from other sources,\n"
+"justify why it is necessary,\n"
+"verify the license is compatible,\n"
+"and obtain approval from the lead developer."
+msgstr ""
+"Sólo suba el código que ha escrito usted.\n"
+"Antes de subir el código o librerías de otras fuentes,\n"
+"verifique que la licencia es compatible,\n"
+"y obtenga permiso del desarrollador."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124
+msgid ""
+"For any images checked in from external sources,\n"
+"it is your responsibility to first verify the license is compatible.\n"
+"Include the license and source information in the checkin comment."
+msgstr ""
+"Para cualquier imagen subida de fuentes externas,\n"
+"es su responsabilidad verificar primero si la licencia es compatible.\n"
+"Incluya la licencia y la información de la fuente en el comentario de "
+"subida."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131
+msgid "Bugs"
+msgstr "Bugs"
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
+#, python-format
+msgid ""
+"Managing Trac tickets is everybody's job, please help.\n"
+"Monitor %(trac)s for tickets you have been assigned or can help with.\n"
+"Assign, categorize, comment on, fix, or close tickets if you can."
+msgstr ""
+"Mantener las entradas del Trac es trabajo de todos, por favor denos su "
+"ayuda.\n"
+"Observe el %(trac)s por entradas que le hayan sido asignadas o en las que"
+" pueda ayudar.\n"
+"Asigne, categorice, comente, arregle, o cierre entradas si puede."
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138
+msgid ""
+"Close a ticket when you think you've fixed it.\n"
+"We don't have a test department to verify and close tickets.\n"
+"If you arent sure you fixed it, close it and add a note saying\n"
+"\"I think I fixed it, please test and reopen if it's still broken\".\n"
+"Add a comment with the dev build number or revision and set\n"
+"the milestone to the next release."
+msgstr ""
+"Cierre la entrada cuando piense que la ha arreglado.\n"
+"No tenemos un departamento de pruebas para verificar las entradas "
+"cerradas.\n"
+"Si no está seguro de haberlo solucionado, ciérrela y añada una nota "
+"diciendo \"I think I fixed it, please test and reopen if it's still "
+"broken\".\n"
+"Añada un comentario con el número de compilación o la revisión y "
+"establezca el hito para la siguiente versión."
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:2
+msgid "Using an IDE with I2P"
+msgstr "Usando un IDE con I2P"
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:4
+msgid ""
+"The main I2P development branch (i2p.i2p) has been set up to"
+" enable developers to easily set up two of the commonly-used IDEs for "
+"Java development: Eclipse and NetBeans."
+msgstr ""
+"La rama principal de desarrollo de I2P (i2p.i2p) ha sido "
+"configurada para permitir a los desarrolladores configurar fácilmente los"
+" dos IDEs de desarrollo de JAVA más usados: Eclipse y NetBeans."
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:10
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain .project and .classpath Eclipse files, to enable the branch "
+"to be easily set up in Eclipse."
+msgstr ""
+"Las ramas principales de desarrollo de I2P (i2p.i2p y sus "
+"ramas) contienen los archivos para Eclipse .project y .classpath, para "
+"permitir una configuración fácil de I2P en eclipse."
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:16
+msgid ""
+"Check out the I2P branch into some directory (e.g. "
+"$HOME/dev/i2p.i2p)."
+msgstr ""
+"Descargue la rama de I2P a algún directorio ( por ejemplo "
+"$HOME/dev/i2p.i2p)."
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:20
+msgid ""
+"Open Eclipse and create a new Workspace, based in the directory that the "
+"I2P branch was checked out to."
+msgstr ""
+"Abra Eclipse y cree un nuevo Espacio de Trabajo, Workspace, basado en el "
+"directorio donde se ha descargado la rama de I2P."
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:24
+msgid ""
+"Select \"File - Import...\" and then under \"General\" select \"Existing "
+"Projects into Workspace\"."
+msgstr ""
+"Seleccione \"Archivo - Importar...\" y entonces en \"General\" seleccione"
+" \"Proyectos existentes al Espacio de Trabajo\""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:28
+msgid ""
+"For \"Select root directory:\" choose the directory that the I2P branch "
+"was checked out to."
+msgstr ""
+"Para \"Seleccionar el directorio raíz:\" elija la carpeta donde ha "
+"descargado la rama de I2P."
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:32
+msgid "If necessary, click \"Refresh\" to refresh the list of projects."
+msgstr "Si es necesario, pulse \"Recargar\" para refrescar la lista de proyectos."
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:36
+msgid "Select every project in the list, and click \"Finish\"."
+msgstr "Seleccione cada proyecto de la lista y pulse \"Terminar\"."
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:40
+msgid ""
+"Done! Your workspace should now contain all projects within the I2P "
+"branch, and their build dependencies should be correctly set up."
+msgstr ""
+"¡Listo! Su espacio de trabajo debería incluir todos los proyectos de la "
+"rama de I2P, y sus dependencias deberían estar correctamente "
+"configuradas."
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:48
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain NetBeans project files."
+msgstr ""
+"Las ramas principales del proyecto de I2P (i2p.i2p y sus "
+"ramas) contienen los archivos del proyecto necesarios para NetBeans."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:2
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:4
+msgid "Monotone Guide"
+msgstr "Guía de Monotone"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:9
+msgid "Operating a Monotone client"
+msgstr "Usando el cliente Monotone"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:11
+#: i2p2www/pages/site/get-involved/guides/monotone.html:63
+msgid "Generating Monotone keys"
+msgstr "Generando las claves de Monotone"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:12
+msgid "Trust and initializing your repository"
+msgstr "Confianza e iniciando su repositorio"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:13
+#: i2p2www/pages/site/get-involved/guides/monotone.html:196
+msgid "Obtaining and deploying developers' keys"
+msgstr "Obteniendo y desplegando las claves de los desarrolladores"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:14
+#: i2p2www/pages/site/get-involved/guides/monotone.html:227
+msgid "Setting up trust evaluation hooks"
+msgstr "Configurar las conexiones de confianza"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:15
+#: i2p2www/pages/site/get-involved/guides/monotone.html:268
+msgid ""
+"Pulling the i2p.i2p, i2p.www and "
+"i2p.syndie branches"
+msgstr ""
+"Descargar las ramas de i2p.i2p, i2p.www y "
+"i2p.syndie"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:16
+#: i2p2www/pages/site/get-involved/guides/monotone.html:308
+msgid "Verifying that trust evaluation works"
+msgstr "Verificar que la evaluación de confianza funciona"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:17
+#: i2p2www/pages/site/get-involved/guides/monotone.html:357
+msgid "Checking out a working copy of the latest version"
+msgstr "Descargar una copia funcional de la última versión"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:18
+#: i2p2www/pages/site/get-involved/guides/monotone.html:384
+msgid "Updating your working copy to the latest version"
+msgstr "Actualizar sus fuentes a la última versión"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:22
+#: i2p2www/pages/site/get-involved/guides/monotone.html:414
+msgid "Operating a Monotone Server"
+msgstr "Usando un servidor Monotone"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:24
+msgid "Obtaining and deploying developers’ transport keys"
+msgstr "Obteniendo y desplegando las claves de transporte de los desarrolladores"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:25
+#: i2p2www/pages/site/get-involved/guides/monotone.html:424
+msgid "Granting push and pull access"
+msgstr "Obtener acceso para subir y descargar"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:26
+#: i2p2www/pages/site/get-involved/guides/monotone.html:469
+msgid "Running Monotone in server mode"
+msgstr "Ejecutar Monotone en modo servidor"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:27
+#: i2p2www/pages/site/get-involved/guides/monotone.html:494
+msgid "Differences under Debian GNU/Linux"
+msgstr "Diferencias en Debian GNU/Linux"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:34
+#, python-format
+msgid ""
+"This is a revised version of Complication's original\n"
+"  guide detailing the use of Monotone in I2P development.\n"
+"  For basic instructions see the quick-start "
+"guide."
+msgstr ""
+"Esto es una versión revisada de la guía "
+"original de Complication detallando el uso de Monotone en el "
+"desarrollo de I2P. Para obtener instrucciones básicas vea la guía rápida."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:42
+#, python-format
+msgid ""
+"I2P has a distributed development model. The source code is replicated "
+"across\n"
+"  independently administered Monotone (\"MTN\") repositories.\n"
+"  Developers with commit rights are able to push their changes to the "
+"repository\n"
+"  (a license agreement needs to be "
+"signed\n"
+"  before commit rights are granted)."
+msgstr ""
+"I2P usa un modelo distribuido de desarrollo. El código es replicado por "
+"administradores independientes en repositorios Monotone (\"MTN\"). Los "
+"desarrolladores con derechos para ello pueden subir sus cambios al "
+"repositorio (deben firmar un acuerdo de "
+"licencia antes de obtener estos derechos)"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:52
+msgid ""
+"Some of Monotone's noteworthy qualities are: distributed\n"
+"  version control, cryptographic authentication, access control, its "
+"small size, having few\n"
+"  dependencies, storage of projects in a compressed SQLite database file,"
+" and\n"
+"  having the ability to resume interrupted synchronization attempts."
+msgstr ""
+"Algunas de las notables cualidades de Monotone son: control de versiones "
+"distribuido, autenticación con cifrados, acceso de control, su pequeño "
+"tamaño, tiene pocas dependencias, el almacenamiento de los proyectos usa "
+"una base de datos SQLite comprimida, y además tiene la capacidad de "
+"reanudar  los intentos de sincronización interrumpidos."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:61
+msgid "Operating a Monotone Client"
+msgstr "Usando un cliente Monotone"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:66
+msgid ""
+"A transport key grants you the ability to push your changes to a Monotone"
+" repository server.\n"
+"  In order to commit code into Monotone (in essence signing your code), a"
+" commit key is also needed.\n"
+"  None of the public Monotone servers on I2P currently require a key in "
+"order to read (or pull) the source code."
+msgstr ""
+"Una clave de transporte le permite subir sus cambios al repositorio del "
+"servidor Monotone. Para poder subir código a Monotone (firmando su "
+"código), es necesaria una clave de subida. Ninguno de los servidores "
+"públicos de Monotone en I2P necesita claves para poder leer (o descargar)"
+" el código."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:74
+msgid ""
+"Without a transport key, one cannot:\n"
+"  
              \n"
+"    
            • pull code from a server which doesn't allow global read "
+"access
              • \n"
+"    
            • push code to any server
              • \n"
+"    
            • run a Monotone server
              • \n"
+"  
            "
+msgstr ""
+"Sin una clave de transporte no se puede:\n"
+"
              \n"
+"
            • descargar el código de un servidor que no permita acceso global de "
+"lectura
              • \n"
+"
            • subir código a cualquier servidor
              • \n"
+"
            • ejecutar un servidor Monotone
              • \n"
+"
            "
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:85
+msgid ""
+"Without a commit key, one cannot:\n"
+"  
              \n"
+"    
            • commit any code
              • \n"
+"  
            "
+msgstr ""
+"Sin una clave de subida no se puede:\n"
+"
              \n"
+"
            • subir ningún código
              • \n"
+"
            "
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:94
+msgid ""
+"If you only intend to retrieve code from MTN, feel free to skip to the\n"
+"  next section. "
+"If you want\n"
+"  to generate keys, read the following."
+msgstr ""
+"So sólo desea obtener el código de MTN salte a la siguiente sección. Si desea generar "
+"las claves siga leyendo aquí."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:102
+msgid ""
+"By convention keys are named like an e-mail addresses, but a "
+"corresponding e-mail\n"
+"  address does not need to exist. For example, your keys might be named:"
+msgstr ""
+"Por convenio las claves son nombradas como una dirección de email, pero "
+"no es necesario que exista un email correspondiente. Por ejemplo, sus "
+"claves podrían llamarse:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:113
+msgid ""
+"Monotone stores keys under $HOME/.monotone/keys in "
+"text files which\n"
+"  are named identically to the keys. For example:"
+msgstr ""
+"Monotone guarda las claves en $HOME/.monotone/keys en"
+" archivos de texto que se llaman exactamente igual que la clave. Por "
+"ejemplo:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:123
+msgid ""
+"To generate transport and commit keys, enter the following commands at a "
+"prompt:"
+msgstr ""
+"Para generar las claves de transporte y subida ejecute los siguientes "
+"comandos en la terminal:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:133
+msgid ""
+"Monotone will prompt you for a password to protect your keys. You are "
+"very strongly encouraged to set a password\n"
+"  for the commit key. Many users will leave an empty password for the "
+"transport key, especially those running a\n"
+"  Monotone server."
+msgstr ""
+"Monotone le pedirá una contraseña para proteger sus claves. Se recomienda"
+" encarecidamente usar una contraseña para la clave de subida. Muchos "
+"usuarios dejan la contraseña de transporte en blanco, sobre todo los que "
+"ejecutan un servidor Monotone."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:141
+msgid "Trust, and initializing your repository"
+msgstr "Confianza e iniciando su repositorio"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:145
+msgid ""
+"Monotone's security model helps to ensure that nobody can easily "
+"impersonate a developer without\n"
+"  it being noticed. Since developers can make mistakes and become "
+"compromised,only manual review can\n"
+"  ensure quality of code. Monotone's trust model will ensure that you "
+"read the right diffs. It does\n"
+"  not replace reading diffs."
+msgstr ""
+"El modelo de seguridad de Monotone ayuda a asegurar que nadie puede "
+"suplantar a un programador fácilmente si ser detectado. Ya que los "
+"programadores pueden cometer errores y pueden ser comprometidos, sólo una"
+" revisión manual puede asegurar la calidad del código. El modelo de "
+"confianza de Monotone se asegura de que usted sólo lea los cambios "
+"correctos. No reemplaza los cambios de lectura."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:155
+msgid ""
+"A Monotone repository is a single file (a compressed SQLite database) "
+"which contains all of the project's source code and history."
+msgstr ""
+"Un repositorio Monotono es un solo archivo (comprimido en una base de "
+"datos SQLite) que contiene todo el código del proyecto y su historial."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:161
+msgid ""
+"After importing the "
+"developers' keys into Monotone and\n"
+"  setting up trust "
+"evaluation hooks,\n"
+"  Monotone will prevent untrusted code from being checked out into your "
+"workspace.\n"
+"  There are commands available to clean untrusted code from your "
+"workspace but in practice they've not been\n"
+"  needed due to the push access policies in place."
+msgstr ""
+"Después de  importar"
+" las claves de los desarrolladores a Monotone y de configurar las conexiones de "
+"confianza, Monotone evitará que cualquier código que no sea de "
+"confianza sea subido a su espacio de trabajo.\n"
+"Existen comandos disponibles para limpiar el código no confiable de su "
+"espacio de trabajo, pero en práctica no han sido necesitados debido a las"
+" reglas de acceso de subida activas."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:171
+msgid ""
+"A repository can hold many branches. For example, our repository holds "
+"the\n"
+"  following main branches:"
+msgstr ""
+"Un repositorio puede almacenar muchas ramas. Por ejemplo, nuestro "
+"repositorio almacena las siguientes ramas principales:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:176
+msgid "The I2P router and associated programs"
+msgstr "El enrutador ('router') I2P y los programas asociados"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:177
+msgid "The I2P project website"
+msgstr "El sitio web del proyecto I2P"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:178
+msgid "Syndie, a distributed forums tool"
+msgstr "Syndie, una herramienta de forums distribuídos."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:183
+msgid ""
+"By convention, the I2P Monotone repository is named i2p.mtn."
+" Before pulling\n"
+"  source code from servers, a database for your repository will need to "
+"be initialized.\n"
+"  To initialize your local repository, change into the directory that you"
+" want the\n"
+"  i2p.mtn file and branch directories to be stored and issue"
+" the following\n"
+"  command:"
+msgstr ""
+"Por convención, el repositorio de I2P Monotone se llama "
+"i2p.mtn. Antes de obtener\n"
+"código fuente desde los servidores, es necesario que sea inicializada una"
+"\n"
+"base de datos para su repositorio. Para inicializar su repositorio local "
+"vaya al directorio donde quiera que el fichero i2p.mtn y los"
+" \n"
+"subdirectorios sean guardados, y use el siguiente comando:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:199
+msgid ""
+"Keys which developers use to commit code are essential for trust "
+"evaluation in\n"
+"  Monotone. The other developers' transport keys are only required for "
+"Monotone server operators.\n"
+"  "
+msgstr ""
+"Las claves que los desarrolladores usan para consignar ('commit') código "
+"son esenciales para la evaluación de confianza en Monotone. Las otras "
+"claves de transporte de desarrolladores sólo son requeridas para "
+"operadores de servidor Monotone."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:206
+#, python-format
+msgid ""
+"Developers' commit keys are provided GPG-signed on another page."
+msgstr ""
+"Las claves de consignación ('commit') de desarrolladores se proporcionan "
+"firmadas-con-GPG en otra página."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:212
+#, python-format
+msgid ""
+"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
+"  file. Create this file (e.g. keys.txt) in the same "
+"directory where i2p.mtn is located. Import the keys with the"
+" command:"
+msgstr ""
+"Para importar claves de desarrollador tras verificar sus autenticidades, "
+"copie todas las claves\n"
+"en un nuevo fichero. Cree este fichero (ej. keys.txt)"
+" en el mismo directorio\n"
+"donde i2p.mtn resida. Luego importe las claves con el "
+"comando:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:222
+msgid ""
+"Note: Never add keys to "
+"$HOME/.monotone/keys manually."
+msgstr ""
+"Nota: Nunca añada claves a "
+"$HOME/.monotone/keys manualmente."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:230
+msgid ""
+"The default Monotone trust policy is way too lax for our requirements: "
+"every committer is trusted by default.\n"
+"  That is not acceptable for I2P development."
+msgstr ""
+"La política de confianza de monotone es demasiada relajada para nuestras "
+"necesidades: todos los colaboradores son de confianza por defecto. Esto "
+"no es aceptable para el desarrollo de I2P."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:237
+msgid ""
+"Change into the directory $HOME/.monotone and open "
+"the file\n"
+"  monotonerc with a text editor. Copy and paste the "
+"following two functions into this file:"
+msgstr ""
+"Vaya al directorio $HOME/.monotone y abra el fichero "
+"monotonerc con un\n"
+"editor de texto. Copie y pegue las dos siguientes funciones en este "
+"fichero:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:246
+msgid ""
+"The first function determines an intersection between two sets, in our "
+"case a\n"
+"  revision's signers and trusted signers."
+msgstr ""
+"La primera función determina una intersección entre dos grupos, en "
+"nuestro caso los firmantes de la revisión y los firmantes de confianza."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:253
+msgid ""
+"The second function determines trust in a given revision, by calling the "
+"first\n"
+"  function with \"signers\" and \"trusted\" as arguments. If the "
+"intersection is\n"
+"  null, the revision is not trusted. If the intersection is not empty, "
+"the\n"
+"  revision is trusted. Otherwise, the revision is not trusted."
+msgstr ""
+"La segunda función determina la confianza en una revisión dada, mediante "
+"una llamada a la primera con \"signers\" (firmantes) y \"trusted\" "
+"(confiables) como argumentos. Si la intersección de ambos \n"
+"es nula, no es confiable. Si la intersección no está vacía, la revisión \n"
+"es confiable. De otra manera, la revisión no es confiable."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:262
+msgid ""
+"More information about Trust Evauluation Hooks can be found in the official Monotone "
+"documentation."
+msgstr ""
+"Puede encontrar más información acerca de los Enganches (`Hooks´) de "
+"Evaluación de Confianza en la documentación oficial de "
+"Monotone"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:271
+msgid ""
+"Enter the directory where you initialized i2p.mtn. Depending "
+"on whether you\n"
+"  want only I2P sources, or also sources for the I2P website and Syndie, "
+"you can\n"
+"  perform the pull operation in different ways."
+msgstr ""
+"Entre en el directorio donde inicializó i2p.mtn. Dependiendo "
+"de si \n"
+"quiere sólo el código fuente de I2P, o también quiere el código del sitio"
+" web \n"
+"de I2P y Syndie, puede realizar pull (obtención) \n"
+"de diferentes maneras."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:279
+msgid "If you only want I2P sources:"
+msgstr "Si sólo quiere el código fuente de I2P: "
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:288
+msgid "If you want all branches:"
+msgstr "Si quiere todas las ramas de desarrollo (`branches`): "
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:294
+msgid ""
+"If the transfer aborts before completing sucessfully, simply repeating "
+"the pull command will resume the transfer."
+msgstr ""
+"Si la transferencia se interrumpe antes de completarse con éxito, \n"
+"simplemente repitiendo el comando pull se retomará la transferencia."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:300
+msgid ""
+"Pulling in the above examples is done anonymously by specifying an empty "
+"transport key.\n"
+"  If everyone pulls anonymously it will be harder for an attacker who "
+"gains control of the server\n"
+"  to selectively provide some people with tampered data."
+msgstr ""
+"La obtención (`pulling`) en los ejemplos anteriores se realiza "
+"anónimamente \n"
+"especificando una clave de transporte vacía. Si todos realizaran "
+"obtenciones anónimas\n"
+"será más difícil para un atacante que gane control en el servidor, "
+"proporcionar datos falsos selectivamente a algunas personas."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:311
+msgid "To verify that trust evaluation works:"
+msgstr "Para verificar que la evaluación de confianza funciona:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:315
+msgid "Make a backup of your monotonerc file."
+msgstr "Haga una copia de respaldo de su fichero monotonerc."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:316
+msgid ""
+"Modify monotonerc by setting the trusted_signers "
+"variable in the following way:"
+msgstr ""
+"Modifique monotonerc estableciendo la variable "
+"trusted_signers (firmantes confiables) de la siguiente manera:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:322
+msgid ""
+"With monotonerc configured as above, Monotone will no"
+" longer trust any committers. Confirm this by changing into the\n"
+"directory where i2p.mtn was created and attempt a checkout "
+"of the I2P branch:"
+msgstr ""
+"Con monotonerc configurado de la forma previa, "
+"Monotone no confiará en adelante en ninguno de los consignadores "
+"(`committers`). Confirme esto llendo al directorio donde "
+"i2p.mtn fue creado, e intente una revisión de la rama de "
+"I2P:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:332
+msgid ""
+"A directory named i2p.i2p should not appear. You "
+"should encounter many\n"
+"  error messages like:"
+msgstr ""
+"Un directorio llamado i2p.i2p no debería aparecer. "
+"Debería encontrar muchos mensajes de error como: "
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:349
+msgid ""
+"If you are satisfied with results, restore the backup of\n"
+"  monotonerc that was created above. If you didn't create a "
+"backup\n"
+"  as advised, re-read Setting up trust evaluation hooks."
+msgstr ""
+"Si está satisfecho con el resultado, vuelva  aponer en su lugar la copia "
+"de seguridad de monotonerc que fue creada antes. Si no creó "
+"una copia de seguridad, vuelva a leer Setting up trust evaluation hooks."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:360
+msgid ""
+"If you already have a branch checked out, skip to the next\n"
+"  section."
+msgstr ""
+"Si ya ha comprobado (`checkout`) un ramal de desarrollo (`branch`),\n"
+"pase a la siguiente sección."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:367
+msgid ""
+"Change into the directory where i2p.mtn is located. Over "
+"there issue:"
+msgstr "Cambie al directorio donde se emplace i2p.mtn. Allí ejecute:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:376
+msgid ""
+"The checkout should complete without error messages and a directory named"
+"\n"
+"  i2p.i2p should appear in the current directory. "
+"Congratulations! You have\n"
+"  successfully checked out the latest I2P sources, ready to be compiled."
+msgstr ""
+"La comprobacion (`checkout`) debería completarse sin mensajes de error, y"
+" un \n"
+"directorio llamado i2p.i2p debería aparecer en el directorio"
+" actual. \n"
+"¡Felicidades! Ha comprobado el último código fuente de I2P con éxito. "
+"está listo \n"
+"para ser compilado."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:387
+msgid ""
+"If you haven't done this already, pull fresh code from the server to your"
+" local\n"
+"  Monotone repository. To accomplish this, change into the directory "
+"where\n"
+"  i2p.mtn is located and issue:\n"
+"  
              \n"
+"    
            • $ mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
+"i2p.i2p
              • \n"
+"  
            "
+msgstr ""
+"Si no ha hecho esto ya, sincronice su repositorio local con código \n"
+"fresco desde el servidor. Para lograr esto, vaya al directorio donde se \n"
+"emplace i2p.mtn y ejecute:\n"
+"
              \n"
+"
            • $ mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
+"i2p.i2p
              • \n"
+"
            "
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:398
+msgid "Now change into your i2p.i2p directory, and over there issue:"
+msgstr "Ahora vaya a su directorio i2p.i2p, y allí ejecute:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:407
+msgid ""
+"As long as there were no errors…Congratulations! You have "
+"successfully updated to the latest I2P sources. They\n"
+"  should be ready to compile."
+msgstr ""
+"En tanto no haya errores…¡Felicidades! Ha realizado la "
+"actualización \n"
+"al último código fuente de I2P con éxito. Debe estar listo para compilar."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:416
+msgid "Obtaining and deploying developers' transport keys"
+msgstr "Obtención y despliegue de claves de transporte de desarrolladores"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:419
+msgid ""
+"As a server operator you may want to grant push access to certain "
+"developers."
+msgstr ""
+"Como operador de servidor, podría querer otorgar acceso a modificación\n"
+"(`push`) del código a ciertos desarrolladores."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:427
+msgid "By default the Monotone server denies all access."
+msgstr "El servidor Monotone deniega todo acceso por defecto."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:433
+msgid "To grant pull access to all clients, set the following in"
+msgstr ""
+"Para garantizar acceso de sincronización local (`pull`) a todos los "
+"clientes, \n"
+"configure lo siguiente en "
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:445
+msgid ""
+"No one will not be able to push code to your server without permission "
+"being explicitly granted. To grant push access:"
+msgstr ""
+"Nadie será capaz de modificar código en su servidor (`push`) sin serle \n"
+"otorgado permiso explícito. Para otorgar acceso de modificación:"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:451
+msgid ""
+"Add the name of the user's transport key to\n"
+"$HOME/.monotone/write-permissions, such as\n"
+"
            \n"
+"    zzz-transport@mail.i2p\n"
+"    complication-transport@mail.i2p\n"
+"
            \n"
+"with one key per line."
+msgstr ""
+"Añada el nombre de la clave de transporte del usuario en \n"
+"$HOME/.monotone/write-permissions como\n"
+"
            \n"
+"zzz-transport@mail.i2p\n"
+"complication-transport@mail.i2p\n"
+"
            \n"
+"con una clave por línea."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:462
+msgid ""
+"Import the transport key(s) into your database. The procedure for "
+"importing transport keys is the same as for\n"
+"importing commit keys, which is described in the section Obtaining and deploying "
+"developers' keys."
+msgstr ""
+"Importe la(s) clave(s) de transporte a su base de datos. El procedimiento"
+" \n"
+"para importar claves \n"
+"de transporte es el mismo que para importar claves de consignación "
+"(`commit`), que se describe en \n"
+"la sección Obtención"
+" y despliegue de claves de transporte de desarrolladores."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:472
+msgid ""
+"A separate database should be used for your Monotone server because "
+"monotone will lock the database while it is served to others.\n"
+"  Make a copy of your development database, then start the server with:"
+msgstr ""
+"Se debe usar una base de datos aparte para su servidor Monotone porque "
+"Monotone bloqueará la base de datos mientras sea servida a otros. \n"
+"Haga una copia de su base de datos de desarrollo, y luego inicie el "
+"servidor con: "
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:479
+msgid ""
+"If your key is protected with a passphrase, Monotone may request the "
+"passphrase\n"
+"  when the first client connects. You can work around this by connecting "
+"making the first client connection to your server\n"
+"  (or by clearing the password for your transport key)."
+msgstr ""
+"Si su clave está protegida con una frase-contraseña, Monotone puede "
+"requerir\n"
+"la frase-contraseña cuando conecte el primer cliente. Puede evitar esto "
+"realizando \n"
+"usted la primera conexión de cliente a su servidor (o eliminando la "
+"contraseña \n"
+"para su clave de transporte)."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:487
+msgid ""
+"For your server to be accessible for others over I2P, you will need to "
+"create a\n"
+"  server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" "
+"profile."
+msgstr ""
+"Para que su servidor sea accesible para otros sobre I2P, tendrá que crear"
+" un \n"
+"túnel de servidor para él. Use el tipo de túnel \"Standard\" y el perfil "
+"\"Bulk\" (masivo)."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:497
+msgid ""
+"Debian (amongst other distributions) has integrated Monotone into their\n"
+"  framework of daemons/services. Although Monotone servers can still be "
+"run\n"
+"  \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may"
+" be more straightforward."
+msgstr ""
+"Debian (entre otras distribuciones) tiene integrado Monotone en sus \n"
+"estructuras demonios/servicios. Aunque los servidores Monotone aún\n"
+"se pueden ejecutar \"de la forma corriente\" en sistemas Debian, hacerlo\n"
+"\"de la forma Debian\" podría ser más apropiado."
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:505
+msgid ""
+"Permissions are granted by editing the files\n"
+"  /etc/monotone/read-permissions and\n"
+"  /etc/monotone/write-permissions. You'll also need to edit\n"
+"  /etc/default/monotone to enable monotone to start at boot "
+"or to\n"
+"  customize the host, port, or database location."
+msgstr ""
+"Los permisos se otorgan editando los ficheros\n"
+"/etc/monotone/read-permissions y \n"
+"/etc/monotone/write-permissions. También tendrá que editar \n"
+"/etc/default/monotone para hacer que Monotone se inicie \n"
+"en el arranque o para ajustar anfitrión (`host`), puerto, o emplazamiento"
+" \n"
+"de la base de datos."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
+msgid "New Developer's Guide"
+msgstr "Guía para nuevos desarrolladores"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
+msgid ""
+"\n"
+"So you want to start work on I2P? Great!\n"
+"Here's a quick guide to getting started\n"
+"on contributing to the website or the software, doing development or "
+"creating translations."
+msgstr ""
+"\n"
+"¿Entonces, quiere empezar a trabajar en I2P? ¡Bien! Aquí tiene una "
+"pequeña guía de como empezar contribuyendo, con la web o con el software,"
+" programando código o traduciendo."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
+#, python-format
+msgid ""
+"\n"
+"Not quite ready for coding?\n"
+"Try getting involved first."
+msgstr ""
+"\n"
+"¿Aún no está listo para programar?  Pruebe primero a involucrarse en el proyecto."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
+msgid "Basic study"
+msgstr "Estudios básicos"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
+msgid "Getting the I2P code"
+msgstr "Obteniendo el código de I2P"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
+msgid "Building I2P"
+msgstr "Compilando I2P"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
+msgid "Development ideas"
+msgstr "Ideas para desarrollar"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
+msgid "Making the results available"
+msgstr "Haciendo que los resultados estén disponibles"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
+msgid "Get to know us!"
+msgstr "¡Conózcanos!"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
+msgid "Translations"
+msgstr "Traducciones"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
+msgid "Tools"
+msgstr "Herramientas"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
+msgid ""
+"Basic development on the I2P router or the embedded applications uses "
+"Java as the main development language.\n"
+"If you don't have experience with Java, you can always have a look at Thinking in Java."
+msgstr ""
+"El desarrollo básico del ruter de I2P y de las aplicaciones del núcleo "
+"utilizan Java como lenguaje de programación. Si no tiene experiencia con "
+"Java, siempre puede echarle un ojo a Thinking in Java."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
+#, python-format
+msgid ""
+"Study the how intro,\n"
+"the other \"how\" documents,\n"
+"the tech intro,\n"
+"and associated documents.\n"
+"These will give you a good overview of how I2P is structured and what "
+"different things it does."
+msgstr ""
+"Estudie la introducción de cómo, los otros \"como\" documentos, la introducción técnica, y los documentos "
+"asociados. Esto le dará una buena vista general de como está estructurado"
+" y de qué otras cosas hace I2P."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
+msgid ""
+"For development on the i2p router or the embedded applications,\n"
+"get the monotone source repository installed - short instructions:"
+msgstr ""
+"Para programar la consola de I2P o las aplicaciones principales, instale "
+"el código del repositorio de monotone - instrucciones rápidas:"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
+msgid ""
+"Install monotone.\n"
+"Monotone is a version control system.\n"
+"We use it because it allows us to keep track of who does what changes to "
+"the source code (and for a lot of complicated things, but 'keeping track "
+"of changes' is the basic idea)."
+msgstr ""
+"Instale monotone. Monotone es un "
+"sistema de control de versiones. Lo utilizamos porque nos permite llevar "
+"el control de quien cambia el código (y muchas cosas complicadas más, "
+"pero el control de los cambios es el motivo principal)"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
+msgid ""
+"Skim over the monotone tutorial,"
+" to make sure you understand the concepts."
+msgstr ""
+"Eche una ojeada al tutorial de "
+"monotone para asegurarse de que entiende los conceptos"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
+msgid ""
+"If you want to remain anonymous, you need to do an additional step, to "
+"set up a connection to a monotone server over I2P:"
+msgstr ""
+"Si desea permanecer anónimo necesita un paso adicional, configurar una "
+"conexión al servidor de monotone a través de I2P:"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
+#, python-format
+msgid ""
+"Enable the i2ptunnel client tunnel on port "
+"8998 pointing to mtn.i2p2.i2p."
+msgstr ""
+"Habilite el túnel cliente i2ptunnel en e "
+"puerto 8998 apuntando a mtn.i2p2.i2p."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
+msgid ""
+"Pick a directory where you want to put all your I2P files, and create a "
+"monotone database:"
+msgstr ""
+"Elija un directorio donde quiera poner todos los archivos de I2P, y cree "
+"una base de datos para monotone:"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
+msgid ""
+"Define the trust list by creating ~/.monotone/monotonerc (or"
+" _MTN/monotonerc in the i2p.i2p workspace) with the "
+"following contents:"
+msgstr ""
+"Defina la lista de confianza creando ~/.monotone/monotonerc "
+"(o _MTN/monotonerc en el área de trabajo de i2p.i2p ) con el"
+" siguiente contenido:"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
+#, python-format
+msgid ""
+"Copy and paste the developer's commit keys "
+"into a new file (e.g. keys.txt) in the same directory\n"
+"  that i2p.mtn is in. Import the keys into your database "
+"with 
                  mtn -d i2p.mtn read < keys.txt
            "
+msgstr ""
+"Copie y pegue las claves de los "
+"desarrolladores en un nuevo archivo (por ejemplo "
+"keys.txt) en el mismo directorio que está "
+"i2p.mtn. Importe las claves a su base de datos con "
+"
             mtn -d i2p.mtn read < keys.txt
            "
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:76
+msgid ""
+"Pull the I2P sources to your machine. This may take a long time, "
+"especially if you are doing this over I2P!"
+msgstr ""
+"Descargue el código de I2P a su ordenador. ¡Puede tardar bastante, sobre "
+"todo si lo hace a través de I2P!"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:78
+msgid "Anonymously:"
+msgstr "Anónimamente:"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:81
+msgid "Non-anonymously:"
+msgstr "Sin anonimato:"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:83
+msgid ""
+"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn"
+".i2p-projekt.de."
+msgstr ""
+"También puede descargarlo desde mtn.i2p-projekt.de además de "
+"'mtn.i2p2.de'."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:90
+msgid ""
+"All the sources are now present on your machine, in the database file. To"
+" make them available in a directory, you need to check them out:"
+msgstr ""
+"Todo el código esta ahora en su ordenador, en al archivo de la base de "
+"datos. Para hacerlo accesible en el directorio necesita ejecutar:"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:92
+msgid ""
+"The above command creates a directory i2p.i2p, which contains all of the "
+"I2P sources."
+msgstr ""
+"El comando anterior crea el directorio i2p.i2p, el cual contiene todo el "
+"código de I2P."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:96
+msgid "Remarks"
+msgstr "Notas"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:97
+msgid ""
+"\n"
+"To download the website files instead of the I2P source files, use "
+"'i2p.www' instead of 'i2p.i2p'."
+msgstr ""
+"\n"
+"Para descargar la página web en vez del código use 'i2p.www' en vez de "
+"'i2p.i2p'."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:100
+msgid ""
+"The initial pull may take several hours using the tunnel.\n"
+"If it fails after a partial pull, simply rerun it, it will start where it"
+" left off.\n"
+"If you are in a hurry, use the non-anonymous access."
+msgstr ""
+"La descarga inicial puede tardar varias horas. Si falla después de una "
+"descarga parcial, simplemente vuelva a ejecutar el mismo comando y "
+"empezará donde lo dejó. Si tiene prisa use el sistema de acceso no "
+"anónimo"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:105
+#, python-format
+msgid ""
+"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn."
+msgstr ""
+"Una lista completa de servidores de descarga, incluyendo i2p.i2p y "
+"i2p.www puede encontrarse en viewmtn."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
+#, python-format
+msgid ""
+"A long explanation about using monotone is available on the monotone page."
+msgstr ""
+"Una explicación completa de cómo usar monotone está disponible en la web de monotone."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
+#, python-format
+msgid ""
+"To compile the code, you need the Sun Java Development Kit 6 or higher, "
+"or equivalent JDK\n"
+"(Sun JDK 6 strongly recommended) and\n"
+"Apache ant\n"
+"version 1.7.0 or higher.\n"
+"If you go are working on the main I2P code, you can go into the i2p.i2p "
+"directory and run 'ant' to see the build options."
+msgstr ""
+"Para compilar el código necesita Sun Java Development Kit 6 o mayor, o el"
+" JDK equivalente (Sun JDK 6 recomendado) y Apache ant versión 1.7.0 o mayor. Si"
+" va a trabajar en al código principal de I2P puede entrar al directorio "
+"i2p.i2p y ejecutar 'ant' para ver las opciones de compilación."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
+msgid ""
+"To build or work on console translations, you need\n"
+"the xgettext, msgfmt, and msgmerge tools from the\n"
+"GNU gettext package."
+msgstr ""
+"Para trabajar en la traducción de la consola necesita las herramientas "
+"gettext, msgfmt, y msgmerge del paquete GNU gettext."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
+#, python-format
+msgid ""
+"For development on new applications,\n"
+"see the application development guide."
+msgstr ""
+"Para programar nuevas aplicaciones vea la guía de "
+"desarrollo de aplicaciones."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
+#, fuzzy, python-format
+msgid ""
+"See zzz's TODO lists,\n"
+"this website's TODO list or\n"
+"Trac\n"
+"for ideas."
+msgstr ""
+"Para una lista de ideas vea la lista "
+"de PORHACER de zzz, la lista de PORHACER de esta"
+" web o el Trac."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
+#, python-format
+msgid ""
+"See the bottom of the licenses page "
+"for\n"
+"commit privilege requirements. You need these to put code into i2p.i2p "
+"(not required for the website!)."
+msgstr ""
+"Mira en la parte de abajo de  la página "
+"de licencias para conocer los requisitos. Los necesita para poder "
+"aportar código a i2p.i2p (¡pero no para la página web!)"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
+msgid "Short version of how to generate and use keys if you plan to commit:"
+msgstr ""
+"Versión corta de cómo generar y usar las claves si tiene planeado hacer "
+"aportes:"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
+msgid "use an empty passphrase"
+msgstr "use una contraseña vacía, sin contraseña"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
+msgid "enter a passphrase"
+msgstr "escriba una contraseña"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
+#, python-format
+msgid ""
+"send this to a mtn repo operator to get "
+"push privileges"
+msgstr ""
+"envíe esto al administrador del "
+"repositorio de mtn para tener permisos para aportar:"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
+#, python-format
+msgid ""
+"send this to a release manager to get "
+"commit privileges - not required for website"
+msgstr ""
+"envíe esto al encargado de las versiones"
+" para obtener los permisos para aportar - no se requiere para la página "
+"web"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
+msgid "check in with this key"
+msgstr "loguee con esta clave"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
+msgid "push with this key"
+msgstr "envíe los cambios al servidor con esta clave"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
+#, python-format
+msgid "Long version: see the monotone page."
+msgstr "Versión completa: vea la web de monotone."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
+#, python-format
+msgid ""
+"The developers hang around on IRC. They can be reached on the Freenode "
+"network, OFTC, and on the I2P internal networks. The usual place to look "
+"is #i2p-dev. Join the channel and say hi!\n"
+"We also have additional guidelines for regular"
+" developers."
+msgstr ""
+"Los desarrolladores suelen estar en el IRC. Puede contactar con ellos en "
+"la red Freenode, OFTC, y en la en el IRC de I2P. El lugar usual es #i2p-"
+"dev. ¡Únase al canal y diga hola!. También hay guías adicionales para desarrolladores."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
+#, python-format
+msgid ""
+"Website and router console translators: See the New Translator's Guide\n"
+"for next steps."
+msgstr ""
+"Traductores de la consola del ruter y la página web: Vea la guía de nuevos traductores."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
+msgid ""
+"I2P is open source software that is mostly developed using open sourced\n"
+"toolkits. The I2P project recently acquired a license for the YourKit "
+"Java\n"
+"Profiler. Open source projects are eligible to receive a free license "
+"provided\n"
+"that YourKit is referenced on the project web site. Please get in touch "
+"if you\n"
+"are interested in profiling the I2P codebase."
+msgstr ""
+"I2P es una aplicación de código libre y es desarrollada usando "
+"herramientas libres. El proyecto I2P ha adquirido recientemente una "
+"licencia para YourKit Java Profiler. Los proyectos libres pueden obtener "
+"una licencia gratis mientras se haga referencia a YourKit en las webs del"
+" proyecto. Por favor pónganse en contacto su está interesado en la "
+"depuración y optimización del código base de I2P."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
+#, python-format
+msgid ""
+"YourKit is kindly supporting open source projects with its full-featured "
+"Java Profiler.\n"
+"YourKit, LLC is the creator of innovative and intelligent tools for "
+"profiling\n"
+"Java and .NET applications. Take a look at YourKit's leading software "
+"products:\n"
+"YourKit Java Profiler and\n"
+"YourKit .NET Profiler."
+msgstr ""
+"YourKit está apoyando amablemente a los proyectos  libres con el Java "
+"Profiler completo. LLC es el creador de inteligentes e innovadoras "
+"herramientas para el desarrollo de aplicaciones JAVA y .NET. Échele un "
+"ojo a los productos principales de YourKit: YourKit "
+"Java Profiler y YourKit .NET Profiler."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
+msgid "New Translator's Guide"
+msgstr "Guía para el nuevo traductor"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
+msgid "Here's a very quick guide to getting started."
+msgstr "Aquí hay a guía rápida para comenzar."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
+msgid "How to Translate the Website"
+msgstr "Cómo traducir la página web"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
+#, python-format
+msgid ""
+"Translation of the website is done with .po files. The easiest way by far"
+" to\n"
+"translate the website is to sign up for an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+"La traducción de las páginas web se hace con archivos .po. La forma mas "
+"fácil con diferencia para traducir una página web es crearse una cuenta "
+"en Transifex y solicitar unirse aun grupo "
+"de traducción. Alternativamente se puede hacer a la \"forma antigua \" "
+"como se muestra debajo."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
+msgid "Preparation"
+msgstr "Preparación"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
+#, python-format
+msgid ""
+"Come to #i2p-dev on irc and talk to people.\n"
+"Claim the language -\n"
+"To make sure other coworkers don't bump onto the files you are working "
+"on,\n"
+"please update the translation status on this wiki "
+"page."
+msgstr ""
+"Venga a #i2p-dev en el IRC para hablar con la gente.\n"
+"Reclame el idioma - \n"
+"Para asegurarse de que otros colaboradores no trabajen sobre los ficheros"
+" \n"
+"sobre los que usted está trabajando, actualice el estatus de la "
+"traducción \n"
+"en esta página wiki."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"Including the installation of monotone,\n"
+"checking out i2p.www branch, and generate your own monotone keys.\n"
+"It is not required that you sign a dev agreement."
+msgstr ""
+"Siga la Guía para el nuevo desarrollador,\n"
+"que incluye la instalación de monotone, comprobación (`checkout`) del\n"
+"ramal de desarrollo (`branch`) i2p.www, y la generación de sus propias \n"
+"claves monotone. No se requiere que firme un nuevo acuerdo de "
+"desarrollador."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet:"
+msgstr ""
+"Cree ficheros \n"
+"si el fichero para su idioma no existe aún: "
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
+msgid ""
+"Run \"./extract-messages.sh\" to generate a "
+"messages.pot in the base directory.\n"
+"Edit the header of this file, then run \"./init-new-po.sh "
+"locale\" to generate the file\n"
+"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
+"\"mtn add\" this file."
+msgstr ""
+"Ejecute \"./extract-messages.sh\" para generar "
+"messages.pot en el directorio base. Edite la cabecera de "
+"este archivo, y entonces ejecute \"./init-new-po.sh locale\""
+" para generar el archivo "
+"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
+"\"mtn add\" este archivo."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
+msgid ""
+"Edit i2p2www/pages/global/lang.html and add a line for your "
+"language (copy an existing line)."
+msgstr ""
+"Edite i2p2www/pages/global/lang.html y añada una línea para "
+"su idioma (replique una existente)."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
+msgid ""
+"Add a flag image file to i2p2www/static/images/flags/ for "
+"the menu (copy from the router)."
+msgstr ""
+"Añada un archivo de imagen con una bandera a "
+"i2p2www/static/images/flags/ para el menú (cópielo desde el "
+"enrutador (`router`))."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
+msgid ""
+"Edit files:\n"
+"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+"Edite los ficheros: \n"
+"Edite i2p2www/translations/locale/LC_MESSAGES/messages.po. \n"
+"Para trabajar con ficheros .po eficientemente, podría querer usar POEdit"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
+msgid ""
+"Check in:\n"
+"\"mtn pull\", \"mtn update\". Then check in by "
+"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
+"This collects the diff info of your changed file into your local repo. "
+"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
+"i2p.i2p\".\n"
+"This synchronizes your local repo with the repo on the target machine."
+msgstr ""
+"Regístrelos:\n"
+"Haga \"mtn pull\", \"mtn update\". Luego "
+"regístrelos como \"mtn ci -k yourname@mail.i2p file1 file2 "
+"...\".\n"
+"Esto recopila la información de diferencias (diff) de su archivo "
+"modificado en \n"
+"su repositorio local.\n"
+"Entonces haga \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p"
+" i2p.i2p\".\n"
+"Esto sincroniza su repositorio local con el respositorio en la máquina "
+"objetivo."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
+msgid "Repeat. Check in often. Don't wait until it is perfect."
+msgstr ""
+"Repita. Registre traducciones con frecuencia. No espere hasta que estén "
+"perfectas."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
+msgid "How to Translate the Router Console"
+msgstr "Cómo traducir la consola del enrutador (`router`)"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
+#, python-format
+msgid ""
+"The easiest way by far to translate the router console is to sign up for "
+"an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+"La forma más fácil de largo para traducir la consola del enrutador "
+"(`router`) \n"
+"es abrir una cuenta en Transifex y "
+"solicitar \n"
+"unirse a un equipo de traducción. Alternativamente puede hacerse \n"
+"\"a la vieja usanza\" como se describe debajo."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"including the installation of monotone and the gettext tools,\n"
+"checking out i2p.i2p branch, and generate your own monotone keys."
+msgstr ""
+"Siga la Guía para el nuevo desarrollador, \n"
+"que incluye la instalación de monotone y las herramientas gettext, la \n"
+"comprobación (`checkout`) del ramal de desarrollo (`branch`) i2p.i2p , \n"
+"y genere sus propias claves monotone."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
+msgid "Generate your own gpg key and sign the dev agreement."
+msgstr "Genere su propia clave GPG y firme el acuerdo de desarrollador."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
+msgid ""
+"Before starting a console translation, better help translate some i2p "
+"webpages first.\n"
+"At least an i2p homepage in your language would be great."
+msgstr ""
+"Antes de inciar una traducción de la consola, mejor ayude primero a \n"
+"traducir alguna de las páginas web de I2P. Sería genial si al menos\n"
+"tradujera la página principal de I2P a su idioma."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
+msgid ""
+"What to translate:\n"
+"There are about 15 files in the i2p.i2p branch that needs translation:"
+msgstr ""
+"Qué traducir: \n"
+"Hay cerca de 15 ficheros en el ramal de desarrollo (`branch`) i2p.i2p\n"
+"que precisan traducción:"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
+msgid ""
+"Where xx is your language code like fr/de/ch/zh/...\n"
+"There may be or may not be files with your lang code. If not, you can "
+"create your own. by copying and renaming other language files you know "
+"with your own lang code."
+msgstr ""
+"Donde xx es su código de idioma como fr/de/ch/zh...\n"
+"Podría o no haber archivos con su código de idioma. Si no, puede crear "
+"los suyos propios copiando y renombrando otros ficheros de idiomas con su"
+" propio código de idioma."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet, copy another language "
+"file to a new file foo_xx.bar for your language.\n"
+"Then \"mtn add\" the file.\n"
+"After creating a .po file, edit the headers. Then run \"ant "
+"distclean poupdate\"."
+msgstr ""
+"Cree los ficheros:\n"
+"Si el fichero para su idioma no existe aún, copie otro fichero de idioma "
+"a un nuevo fichero foo_xx.bar para su idioma.\n"
+"Entonces haga \"mtn add\" sobre el fichero.\n"
+"Después de crear un fichero .po, edite las cabeceras. Luego ejecute "
+"ant distclean poupdate\"."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
+msgid ""
+"Start to work:\n"
+"Edit the HTML files with any text editor.\n"
+"Be sure not to use an editor in HTML mode that reformats everything.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+"Comience a trabajar:\n"
+"Edite los ficheros HTML con cualquier editor de texto.\n"
+"Asegúrese de no usar un editor en modo HTML que reformatee todo.\n"
+"Para trabajar con ficheros .po eficientemente, podría querer usar POEdit"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
+msgid ""
+"As you can see, it's not that difficult.\n"
+"If you have questions about the meaning of the terms in the console, ask "
+"in #i2p-dev on IRC."
+msgstr ""
+"Como puede ver, no es tan difícil.\n"
+"Si tiene preguntas acerca del significado de los términos en la consola, "
+"pregunte en #i2p-dev en el IRC."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
+msgid "FAQ"
+msgstr "Preguntas frecuentes"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
+msgid ""
+"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
+"and html, etc.? Why can't I just do a translation and email it to you?"
+msgstr ""
+"P: ¿Por qué tengo que instalar Monotone, Java, JSP, aprender acerca de "
+"los ficheros .po y HTML, etc.? ¿Por qué no puedo simplemente hacer una "
+"traducción y enviársela vía email?"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
+msgid "A: Several reasons:"
+msgstr "R: Por diferentes razones:"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
+#, python-format
+msgid ""
+"You might be interested in translating via Transifex. Request to join a "
+"translation team here."
+msgstr ""
+"Podría estar interesado en traducir a través de Transifex. Solicite "
+"unirse a un equipo de traducción aquí."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
+msgid ""
+"We don't have anybody who has time to accept manual contributions and "
+"submit them to our source control system on your behalf. Even if we did, "
+"it doesn't scale."
+msgstr ""
+"No tenemos a nadie que tenga tiempo para aceptar contribuciones manuales "
+"y las entregue a nuestro sistema de control de código fuente \n"
+"en su lugar. Incluso si lo hicieramos, no sería adecuado."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
+msgid ""
+"Maybe you are thinking translation is a one-step process. It isn't. You "
+"can't do it all at once. You will make mistakes. You need to test it and "
+"tweak it to make it look right before you submit it. Developers "
+"will update or add to the English text, thus requiring a translation "
+"update."
+msgstr ""
+"Quizá esté pensando que la traducción es un proceso de un sólo paso. No "
+"lo es. No puede hacerlo todo de una vez. Cometerá errores. Ha de probarla"
+" y ajustarla para hacer que luzca correcta antes de entregarla. "
+"Los desarrolladores actualizarán o añadirán sobre el texto en Inglés, y "
+"así será como soliciten una actualización de la traducción."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
+msgid ""
+"Having translators use a source control system directly provides "
+"authentication and accountablility - we know who is doing what, and we "
+"can track changes, and revert them if necessary."
+msgstr ""
+"Hacer que los traductores usen directamente un sistema de control de "
+"código fuente proporciona autentificación y registrabilidad - conocemos "
+"quién está haciendo qué, y podemos seguir los cambios y revertirlos si "
+"fuese necesario."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
+msgid ""
+".po files are not difficult. If you don't want to work directly with "
+"them, we recommend 'poedit'."
+msgstr ""
+"Los ficheros .po no son difíciles. Si no quiere trabajar directamente con"
+" ellos, le recomendamos 'poedit'."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
+msgid ""
+"HTML files are not difficult. Just ignore the html stuff and translate "
+"the text."
+msgstr ""
+"Los ficheros HTML no son difíciles. Tan sólo ignore todo el material HTML"
+" y traduzca el texto."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
+msgid ""
+"Installing and using monotone is not that difficult. Several of the "
+"translators and other contributors to I2P are non-programmers, and they "
+"use monotone regularly. Monotone is simply a source control system, it is"
+" not about \"coding\"."
+msgstr ""
+"Instalar y usar Monotone no es tan difícil. Varios de los traductores y "
+"otros contribuidores a I2P son no-programadores, y usan Monotone "
+"regularmente. Monotone es sencillamente un sistema de control de código "
+"fuente, no tiene que ver con la \"programación\"."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
+msgid ""
+"Our items to translate are not \"documents\". They are html files and po "
+"files, with a specific format and character encoding (UTF-8) that must be"
+" maintained, and not corrupted by email programs or other methods of "
+"transfer."
+msgstr ""
+"Nuestros elementos a traducir no son \"documentos\". Son ficheros HTML y "
+"ficheros .po, con un formato específico y una codificación de caracteres "
+"(UTF-8), que debe mantenerse y no corromperse por programas de email u "
+"otros métodos de transferencia."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
+msgid ""
+"We looked at 'pootle' as a front-end for translators. It didn't work "
+"well, needed an administrator, and a pootle-based process would suffer "
+"from a number of the above flaws."
+msgstr ""
+"Nos fijamos en 'pootle' como una herramienta intermedia para traductores."
+" No funcionó bien, necesitaba un administrador, y un proceso basado-en-"
+"pootle adolecería de algunos de los defectos anteriores."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
+msgid ""
+"In summary:\n"
+"Yes, we know it is somewhat of a hurdle to get started. It's really the "
+"only possible way we can do it. Give it a try, it really isn't that hard."
+msgstr ""
+"En resumen: \n"
+"Sí, sabemos que comenzar es como una carrera de obstáculos. En realidad "
+"es la única forma posible de la que podemos hacerlo. Inténtelo, realmente"
+" no es tan difícil."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
+msgid "More Information"
+msgstr "Más información"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
+#, python-format
+msgid ""
+"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
+msgstr ""
+"El canal #i2p-dev del IRC, o el forum de traducción en %(zzz)s."
+
diff --git a/i2p2www/translations/es/LC_MESSAGES/misc.po b/i2p2www/translations/es/LC_MESSAGES/misc.po
new file mode 100644
index 00000000..00591303
--- /dev/null
+++ b/i2p2www/translations/es/LC_MESSAGES/misc.po
@@ -0,0 +1,1686 @@
+# Spanish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Adolfo Jayme Barrientos , 2013
+# Daniel Mustieles , 2013
+# m1xxy , 2011
+# olivertrash , 2013
+# strel , 2013
+# trolly, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-08-30 23:32+0000\n"
+"PO-Revision-Date: 2013-08-12 09:33+0000\n"
+"Last-Translator: trolly\n"
+"Language-Team: Spanish "
+"(http://www.transifex.com/projects/p/I2P/language/es/)\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 "I2P en el CLT y el PetCon 2009.1"
+
+#: 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 ""
+"Miembros de I2P darán una charla en el CLT y PetCon 2009.1. Dos miembros "
+"de equipo de I2P estarán en los 2 próximos Linux day y en concenciones de"
+" seguridad."
+
+#: 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 ""
+"El 14 de mayo del 2009 habrá un corta charla sobre una introducción "
+"general a I2P en la Chemnitz Linux Tag "
+"2009 guiada por echelon. Echelon y algunos otros miembros de la "
+"familia I2P estarán en la conferencia los dos días (sábado y Domingo) y "
+"serán reconocibles como parte de la familia I2P. Conócelos, pregúntales, "
+"muéstreles sus propuestas."
+
+#: 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 ""
+"Justo 10 días después se llevará a cabo la Privacy"
+" and Data Security convention en Dresden.. De igual forma, echelon "
+"estará en el evento y dará una pequeña charla introductoria sobre I2P. "
+"También se dará otra charla sobre los perfiles de los clientes I2P."
+
+#: 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 ""
+"El código fuente de I2P se guardaba en un repositorio CVS. En estos "
+"momentos se guarda en un repositorio Monotone. Para aquellos que no estén "
+"familiarizados con CVS, existe un libro fantásrico sobre este tema (los "
+"desarrolladores sólo necesitan familiarizarse con el primer capítulo - "
+"\"An Overview of\n"
+"CVS\", ya que los siguientes capítulos tratan sobre algunos feos detalles"
+" que pocas personas necesitarán)."
+
+#: 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 ""
+"Nota humorística en WinCVS: \"¿Sabía que nunca debería experimentar los "
+"nuevos comandos CVS en el repositorio de trabajo?. Es mejor crear un "
+"módulo de ejemplo.\""
+
+#: i2p2www/pages/site/misc/i2ptunnel-migration.html:2
+#: i2p2www/pages/site/misc/i2ptunnel-migration.html:4
+msgid "I2PTunnel migration"
+msgstr "Migración de los I2PTunnel"
+
+#: 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 ""
+"Después de actualizar la nueva arquitectura, deberá realizar un pequeño "
+"esfuerzo para hacer funcionar de nuevo sus servidores antiguos manejados "
+"por los I2PTunnel. Para una eepsite con la configuración clientApp "
+"antigua, debe:"
+
+#: i2p2www/pages/site/misc/i2ptunnel-migration.html:16
+msgid "To provide that same functionality on the new web architecture:"
+msgstr "Para proporcionar la misma duncionalidad en la nueva arquitectura:"
+
+#: i2p2www/pages/site/misc/i2ptunnel-migration.html:18
+#, python-format
+msgid "Jump to %(url)s"
+msgstr "Saltar a %(url)s "
+
+#: i2p2www/pages/site/misc/i2ptunnel-migration.html:19
+msgid "Click on Add new: [Server tunnel] \"GO\""
+msgstr "Pulse en Añadir un nuevo:[Rúnel Servidor] \"GO\""
+
+#: i2p2www/pages/site/misc/i2ptunnel-migration.html:21
+msgid "For the name: \"eepsite\""
+msgstr "Nombre: \"eepsite\" "
+
+#: i2p2www/pages/site/misc/i2ptunnel-migration.html:22
+msgid "For the description: \"My eepsite, isn't it pretty?\""
+msgstr "Descripción:\"Mi eepsite, ¿no es bonita?\""
+
+#: i2p2www/pages/site/misc/i2ptunnel-migration.html:23
+msgid ">For the target host:"
+msgstr ">Servidor de destino:"
+
+#: i2p2www/pages/site/misc/i2ptunnel-migration.html:24
+msgid "For the target port:"
+msgstr "Puerto de destino:"
+
+#: 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 ""
+"Archivo con la clave privada: path de \"myWebPriv.dat\"
             (se recomienda que copie ese archivo .dat al nuevo directorio de "
+"instalación)"
+
+#: i2p2www/pages/site/misc/i2ptunnel-migration.html:29
+msgid "Check the \"Start automatically?\" checkbox"
+msgstr "Active la casilla de \"Iniciar automáticamente\"."
+
+#: i2p2www/pages/site/misc/i2ptunnel-migration.html:30
+msgid "Click \"Save\""
+msgstr "Pulse \"Guardar\""
+
+#: i2p2www/pages/site/misc/i2ptunnel-migration.html:32
+msgid "It will come back saying:"
+msgstr "Responderá diciendo:"
+
+#: 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 ""
+"¡Ya está! Para crear el nuevo servidor I2PTunnel funciona de la misma "
+"forma, excepto que no necesita \"copiar el archivo antiguo\". "
+"Internamente está todo controlado por el archivo "
+"i2ptunnel.config, el cual puede editar externamente (si lo "
+"hace, pulse \"Recargar configuración\" en la página web del I2PTunnel, "
+"que apagará todos los túneles existentes y los construirá y levantará de "
+"nuevo)."
+
+#: 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 ""
+"Dese cuenta que TENDRÁ que esperar hasta que el ruter esté integrado en "
+"la red antes de poder usar el interfaz web para /i2ptunnel/. Le dirá "
+"\"Por favor sea paciente\" si ya lo ha intentado anteriormente, lo que "
+"significa que aún está intentando de construir las sesiones de los "
+"túneles que ha configurado para ser creados."
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:2
+msgid "I2PTunnel services"
+msgstr "Servicios I2PTunnel."
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:4
+msgid "Below is quick copy of aum's eepsite deployment guide."
+msgstr ""
+"Más abajo tiene una copia de la guía de aum de como crear una eepsite "
+"rápidamente."
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:8
+msgid "1. - Deploy a local server"
+msgstr "1. - Instalar un servidor local"
+
+#: 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 ""
+"Para simplificar, seguiremos los pasos de cómo crear un servidor web; aún"
+" así, este procedimiento es le mismo independientemente del protocolo del"
+" servidor o/y los clientes que esté configurando."
+
+#: 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 ""
+"Recomiendo el servidor web Tiny Httpd, thttpd, (hay una versión "
+"disponible en su web para windows) aunque puede usar cualquier servidor "
+"con el que se encuantre confortable."
+
+#: 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 ""
+"Otra opción robusta podría ser usar EasyPHP, el cual es también libre. "
+"Viene con PHP, PHPmyamin, mySQL y el servidor web Apache. Para los "
+"principiantes que no tengan experiencia en configurar un domino o "
+"servidores de contenido, vea la web de hosting/servidores para más ayuda."
+
+#: 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 ""
+"En el servidor web que haya elegido, configúrelo para que escuche en un "
+"puerto de su elección, y sirva los documentos de un directorio de su "
+"elección. Para este ejemplo supondremos que usamos el puerto 10880."
+
+#: 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 ""
+"Asegúrese que su cortafuegos está configurado para bloquear las "
+"conexiones entrantes a este puerto (si no, al poder acceder directamente "
+"a este puerto, eliminaría su anonimato)"
+
+#: 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 ""
+"Pruebe el servidor web abriendo en su navegador web (el navegador con "
+"\"conexión directa\") la dirección http://localhost:10880 (cambiando el puerto 10880 "
+"por el número que haya elejido)."
+
+#: 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 ""
+"Una vez que el servidor esté funcionando, y pueda acceder a él localmente"
+" con su explorador, continue con el siguiente paso."
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:33
+msgid "2 - Generate an I2P Destination Keypair"
+msgstr "2 - Genere el par de claves de destino de I2P"
+
+#: 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 ""
+"I2P no funciona con su dirección IP. Para proteger su anonimato funciona "
+"con direcciones únicas llamadas claves de destino."
+
+#: 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 ""
+"Una clave de Destino funciona como una dirección IP normal, excepto que "
+"no se puede seguir dicha dirección hasta tu localización local. Cuando "
+"los usuarios hacen una petición para hablarle, sus puertas de salida, "
+"gateways son las que responden por usted. Con lo que los usuarios sólo "
+"pueden saber las IP de sus gateways. Además, las gateways no saben su IP,"
+" ya que las gateways son los últimos nodos de sus túneles, y los túneles "
+"han sido creado anónimamante con el rutado Garlic. (Las gateways son como"
+" mascotas que no pueden ver a sus dueños, y todo el mundo se comunica a "
+"través de estas mascotas)"
+
+#: 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 ""
+"Para crear un servicio en I2P, se crean un par de claves de destino. Se "
+"utiliza la clave privada para autentificar sur servidor cuando se conecta"
+" a I2P, y se hace pública la clave pública (también llamada clave de "
+"destino), así otros pueden conectarse a su servidor. (indirectamente, a "
+"través de sus gateways)"
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:44
+msgid "Each service you run on I2P requires a different keypair."
+msgstr "Cada servicio que ejecute en I2P necesita un par de claves diferente."
+
+#: 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 ""
+"Para generar el par de claves, ejecute el comando: java -jar "
+"lib/i2ptunnel.jar -nogui -e \"genkeys myWebPrivKey.dat "
+"myWebPubKey.dat\" (en una sola línea)"
+
+#: 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 ""
+"Para generar el par de claves en windows, ejecute el comando: java "
+"-jar lib/i2ptunnel.jar -nogui -e \"genkeys myWebPrivKey.dat "
+"myWebPubKey.dat\""
+
+#: 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 ""
+"Los nombres de archivo myWebPrivKey.dat y "
+"myWebPubKey.dat son arbitrarios - elija el que desee, al "
+"menos mientras entienda sus elecciones."
+
+#: 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 ""
+"Ahora necesitamos exportar su clave pública al formato base64, el cual "
+"compartirá con otros."
+
+#: 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 ""
+"Para convertir su archivo myWebPubKey.dat al formato base64 compartible, "
+"ejecute el comando java -cp lib/i2p.jar net.i2p.data.Base64 encode "
+"myWebPubKey.dat > myWebPubKey.txt (todo en la misma línea)."
+
+#: 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 ""
+"El archivo que acaba de generar, myWebPubKey.txt, contiene "
+"una cadena larga base64 (con 516 caracteres), lo que llamamos una clave "
+"de destino. Todo lo que necesita saber por el momento es que esta clave "
+"de destino permite que los clientes remotos localicen con precisión su "
+"servicio y se conecten a él, justamente de la misma forma que una IP "
+"permite que las máquinas remotas puedan localizar su máquina y se "
+"conecten a ella."
+
+#: 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 ""
+"Aunque, y a diferencia de una dirección IP, no hay forma de rastrear la "
+"localización física de su máquina - aunque el servidor pueda ser accedido"
+" desde I2P, su dirección IP no puede ser rastreada o asociada a esta "
+"clave de destino."
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:70
+msgid "3 - Open a 'Tunnel' from I2P To Your Server"
+msgstr "3 - Abra un 'Túnel' desde I2P hacia su servicio/servidor"
+
+#: 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 ""
+"Para que los clientes de I2P sean capaces de acceder a su servidor, tiene"
+" que ejecutar un 'bridge', puente, o un 'túnel', los cuales cogen las "
+"conexiones desde esos clientes y las reenvían hasta su servidor local."
+
+#: 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 ""
+"Para activar este tipo de túneles, ejecute el comando java -jar "
+"lib/i2ptunnel.jar -nogui -e \"server localhost 10880 "
+"myWebPrivKey.dat\" (todo en la misma línea)."
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:78
+msgid ""
+"If you used different filenames or port number earlier on, change these "
+"accordingly"
+msgstr ""
+"Si anteriormente ha usado nombres diferentes en los archivos, o usado "
+"números de puertos diferentes, cámbielos de acuerdo a ello."
+
+#: 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 ""
+"Para usuarios de windows; recuerden cambiar los apostrofes con comillas "
+"dobles. Tal que: java -jar lib/i2ptunnel.jar -nogui -e \"server "
+"localhost 10880 myWebPrivKey.dat\""
+
+#: 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 ""
+"En unos pocos segundos el 'túnel' debería estar activo, y los clientes "
+"remotos deberían poder acceder al servicio anónimamante. Recuerde dejar "
+"su ruter \"calentarse\" antes de permitir que los clientes se conecten."
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:89
+msgid "4 - Update Your hosts.txt File "
+msgstr "4 - Actualice su archivo 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 ""
+"Para probar su propio servicio localmente debe crear una entrada en su "
+"archivo host.txt, para que I2P pueda traducir la URL sencilla que "
+"introduce en la barra de direcciones de su navegador en la clave pública "
+"completa que necesita para encontrar su servidor."
+
+#: 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 ""
+"Edite su archivo host.txt y añada la línea myserver.i2p=blahblahblah, "
+"donde myserver.i2p es un 'dominio' I2P que desea asociar con su web, y en"
+" donde el blahblahblah es el texto de la clave pública base64 que ha "
+"creado anteriormente en el archivo "
+
+#: 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 ""
+"Una vez hecho esto, usted y otros pueden acceder a su servidor "
+"simplemente poniendo el nombre de dominio myserver.i2p en la barra de "
+"direcciones del navegador."
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:102
+msgid "5 - Surf Your Site Within I2P"
+msgstr "5 - Navegue hasta su web dentro de 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 ""
+"Usando su navegador web secundario -  el que anteriormente ha configurado"
+" para usar el proxy localhost:4444 - acceda en su navegador a la "
+"dirección "
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:107
+msgid "You should see the main page of your webserver come up."
+msgstr "Debería aparecerle la página web principal de su servidor."
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:112
+msgid "6 - Create a Local Client Tunnel Connection "
+msgstr "6 - Crear un Túnel cliente local para la conexión"
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:114
+msgid "We now have to think beyond just web servers."
+msgstr "Ahora debemos pensara más allá de los servidores web."
+
+#: 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 ""
+"Según use más I2P y lo conozca mejor, deseará usar todo tipo de "
+"servidores y clientes."
+
+#: 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 ""
+"La belleza de I2P radica en que permite que los clientes y servidores de "
+"la mayoría de los protocolos sean 'tunelados' transparentemente a través "
+"de la red anónima I2P."
+
+#: 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 ""
+"Puede ejecutar servidores/clientes de email, servidores/clientes de "
+"nombres, servidores/clientes de noticias - realmente casi caulquier cosa "
+"- quizás incluso FTP en modo pasivo."
+
+#: 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 ""
+"Ahora vamos a crear un túnel cliente. Este es como el túnel servidor que "
+"hemos creado anteriormente, pero funciona al revés. Escucha en un puerto "
+"en su máquina local; su cliente local se conecta a este puerto; la "
+"conexión se reenvía a través de I2P hasta el servicio de destino."
+
+#: 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 ""
+"Para abrir el túnel cliente para su servidor, ejecute el comando "
+"java -jar lib/i2ptunnel.jar -nogui -e \"config localhost 7654\" -e "
+"\"client 10888 textofbase64key\" (todo en una línea)."
+
+#: 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 ""
+"El puerto10888 es arbitrario -  simplemente es necesario que sea un "
+"puerto diferente al que ocupa su servidor, y que no esté usado por ningún"
+" otro servicio."
+
+#: 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 ""
+"textofbase64key no es más que el contenido del archivo de la clave "
+"pública myWebPubKey.txt, reproducido completamente en una línea "
+"(alternativamente, en vez de usar textofbase64key, puede especificar el "
+"nombre en su hosts.txt - por ejemplo myserver.i2p)"
+
+#: 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 ""
+"Después de un minuto o dos de haber ejecutado este comando, el túnel "
+"cliente desde su máquina local hacia I2P estará abierto y listo para "
+"usar."
+
+#: 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 ""
+"Apunte su navegador web normal (no el que ha configurado para usar "
+"localhost:4444), hacia http://localhost:10888"
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:144
+msgid ""
+"Verify that the main page of your server eventually comes up in your "
+"browser."
+msgstr ""
+"Asegúrese que la página principal de su servidor aparece en su navegador "
+"web."
+
+#: 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 ""
+"Usará el mismo procedimiento para que cualquier aplicación cliente local "
+"pueda acceder a un servidor remoto I2P - simplemente consiga la clave "
+"pública base64 (llamada clave de destino) del servidor remoto, elija un "
+"puerto local para conectarse al servidor remoto, abra el túnel, y conecte"
+" con su cliente al contenido deseado. "
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:152
+msgid "7 - Share your server details with others"
+msgstr "7 - Comparta los datos del servidor con otros"
+
+#: 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 ""
+"Usando un medio anónimo (por ejemplo unos los servidores IRC en I2P o la "
+"wiki de ugha), anuncie su nombre de dominio ( por ejemplo www.mynick.i2p) así "
+"como su clave de destino. Entonces otros podrán conectarse a su servidor "
+"remotamente sin comprometer su anonimato o el de ellos."
+
+#: 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 ""
+"Recuerde, pude ir a What's on I2P y buscar las últimas claves públicas "
+"enlazadas a su URL. También debería añadir su clave pública y URL allí. "
+"Pero por supuesto, quiere hacer esto anónimamente. Drupal.i2p.net es sólo"
+" accesible desde la clearnet. Por lo que para acceder a la WWW "
+"anónimamante desde I2P, necesitará ejecutar el script startSquid. Hágalo "
+"de la misma forma que ha ejecutado otros scripts. Vuelva a configurar su "
+"navegador web para que use localhost:5555 como proxy, como se ha definido"
+" en el script, y cuando el script haya generado sus claves, ya puede "
+"acceder el proxy squid. Ponga cualquier URL WWW (como Google o esta web "
+"de I2P) en su navegador y estará navegando la clearnet anónimamante. "
+"Ahora puede añadir su clave pública seguro, y nadie puede averiguar si "
+"IP."
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:162
+msgid "8 - Write Some Scripts To Handle All This Menial Nonsense"
+msgstr "8 - Cree algunos scripts para manejar todo este sinsentido"
+
+#: 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 ""
+"Repetir estos pasos cada vez que se configura un cliente o servidor I2P "
+"puede volver loco a mucha gente."
+
+#: 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 ""
+"En la web de Aum http://www.freenet.org.nz/i2p/ hay un script "
+"llamado setupServer.py que automatiza todo este sinsentido en un comando "
+"de una sola línea."
+
+#: 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 ""
+"Siéntase libre de usar o cambiar etupServer.py para probarlo, o para "
+"escribir su propio script en Python o en cualquier otro lenguaje."
+
+#: 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 ""
+"También pude querer escribir para que maneje el inicio del Ruter I2P, el "
+"eepProxy y los túneles que esté usando. Yo uso un script llamado "
+"startEverything.sh, que se ejecuta al iniciar al sistema. (Estos scripts "
+"no son necesarios en las nuevas versiones de I2P)."
+
+#: i2p2www/pages/site/misc/i2ptunnel-services.html:176
+msgid "Exercise for Windows users - port setupServer.py into a MS-DOS .BAT file."
+msgstr ""
+"Un ejercicio para los usuarios de Windows - portar setupServer.py a un "
+"archivo MS-DOS .BAT."
+
+#: i2p2www/pages/site/misc/invisiblenet.html:2
+msgid "Old Documents"
+msgstr "Documentos viejos"
+
+#: 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 ""
+"Aquí hay una lista de documentos originarios de www.invisiblenet.net/i2p/"
+" y rescatado gracias a la Wayback "
+"Machine. Son bastantes antiguos y pueden que ya no sean precisos. Aún"
+" así, los documentos sobre I2CP e I2NP tienen información bastante buena."
+
+#: i2p2www/pages/site/misc/jbigi.html:3
+msgid "August 2011"
+msgstr "Agosto 2011"
+
+#: i2p2www/pages/site/misc/jbigi.html:6
+msgid "Overview"
+msgstr "Vista general"
+
+#: 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 ""
+"Usando JNI (Interfaz nativo de Java), un poco de código C (¡gracias "
+"ugha!), un poco de trabajo manual y un trozo de chicle hemos hecho que "
+"varias operaciones de cifrados sean un poco más rápidas."
+
+#: 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 ""
+"El aumento de velocidad se debe a la súper rápida librería GNU MP Bignum (libgmp). Sólo usamos una "
+"función de libgmp - mpz_powm() como reemplazo de"
+" la modPow() BigInteger en la librería Java "
+"Math. Ya que modPow() es una importante parte de los cálculos de "
+"cifrados, se consigue un beneficio sognificante."
+
+#: 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 ""
+"La instalación estándar de I2P incluye como 20 versiones de la librería "
+"para diferentes plataformas, dentro del archivo jbigi.jar, cada una sobre"
+" 50kb. El inicio de la librería JBigl, la identificación de la CPU, "
+"selección y extracción del módulo correcto a cargar es manejado por la clase NativeBigInteger. Si no hay un "
+"módulo disponible para la plataforma usada, se usará la librería estándar"
+"  modPow() BigInteger de Java Math library."
+
+#: i2p2www/pages/site/misc/jbigi.html:38
+msgid "Rebuilding and Testing JBigI"
+msgstr "Recompilando y probando 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 ""
+"Aquí están las instrucciones para compilar una nueva librería jbigi para "
+"su propia plataforma y poder probar su rendimiento."
+
+#: i2p2www/pages/site/misc/jbigi.html:42
+msgid "Requirements"
+msgstr "Dependencias"
+
+#: 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 ""
+"Funciona en Linux con unos pocos cambios en build.sh, probablemente "
+"también en otras plataformas. En Kaffe el aumento de velocidad es muy "
+"pequeño, porque ya usa internamente el BitInteger nativo. Blackdown "
+"parece producir errores extraños. Ya que va a compilar necesita JDK; el "
+"JRE no funcionará."
+
+#: i2p2www/pages/site/misc/jbigi.html:50
+msgid ""
+"The required code is available in monotone database and the latest source"
+" tarball. "
+msgstr ""
+"El código necesario está disponible en monotone y en el último tarball de"
+" las fuentes."
+
+#: 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 ""
+"Necesita instalar la librería GNU MP Bignu (libgmp), si no está incluida "
+"en su OS / distribución puede obtenerla de http://gmplib.org/#DOWNLOAD. "
+"Incluso si ya tiene instalada como un binario, vale la pena compilar GMP "
+"por usted mismo, ya que de esta forma será capaz de usar las "
+"instrucciones específicas de su procesador. Probablemente se pueda usar "
+"la última versión de GMP en vez de la 5.0.2, pero no ha sido probado por "
+"nosotros."
+
+#: i2p2www/pages/site/misc/jbigi.html:61
+msgid "Step-by-step instructions"
+msgstr "Instrucciones paso a paso"
+
+#: 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 ""
+"Mire en , en la web de los "
+"registros, el entorno que está ejecutando . Deberían aparecer uno o dos "
+"mensajes sobre JBigi"
+
+#: i2p2www/pages/site/misc/jbigi.html:66
+msgid "Locally optimized native BigInteger loaded from the library path"
+msgstr ""
+"Librería nativa local optimizada BigInteger has sido cargada "
+"satisfactoriamente."
+
+#: i2p2www/pages/site/misc/jbigi.html:68
+msgid "or"
+msgstr "o"
+
+#: i2p2www/pages/site/misc/jbigi.html:70
+msgid "Native BigInteger library jbigi not loaded - using pure java"
+msgstr "La librería nativa BigInteger jbigi no ha sido cargada - usando java puro."
+
+#: 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 ""
+"Si la librería nativa BigInteger NO ha sida cargada, definitivamente "
+"necesita compilarla. Algunas plataformas, como OS X, OpenSolaris y los "
+"sistemas de 64 bits, pueden necesitar que compile su propia librería. Si "
+"la librería BigInteger se ha cargado, al menos haga el siguiente paso "
+"para comprobar su rendimiento."
+
+#: 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 ""
+"Mire en http://localhost:7657/stats.jsp"
+" para ver cuales son los valores medios del tiempo de vida para "
+"crypto.elGamal.decrypt y "
+"crypto.elGamal.encrypt. Los números son el tiempo en mili "
+"segundos. Cópielos para poder compararlos más tarde.   El tiempo medio de"
+" cifrado es alrededor de 20ms. Si el tiempo de cifrado es menor de 50ms "
+"para un procesador relativamente nuevo, o menos de 100ms para un "
+"procesador viejo, y la librería BigIntefer ha sido cargada, probablemente"
+" esté todo bien."
+
+#: 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 ""
+"Obtenga las últimas sources de I2P desde la "
+"página de descargas, u obtenga el código más actualizado desde la "
+"base de datos de monotone en mtn.i2p2.de"
+
+#: i2p2www/pages/site/misc/jbigi.html:92
+msgid "Inside the source tree change directory to: core/c/jbigi"
+msgstr ""
+"Dentro del directorio de las fuentes cambie a la carpeta: "
+"core/c/jbigi"
+
+#: 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 ""
+"Lea el archivo README. Si ya tiene un archivo /usr/lib/libgmp.so, no "
+"necesita descargar GMP. Use la opción 'dynamic' para build.sh. De otra "
+"forma, también puede descargar la versión 5.0.2 de GMP desde "
+"href=\"http://gmplib.org/#DOWNLOAD\">http://gmplib.org/#DOWNLOAD, "
+"guardándolo como  gmp-5.0.2.tar.bz2. Si decide usar una versión más "
+"nueva, cambie la línea VER= en core/c/jbigi/build.sh. "
+
+#: 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 ""
+"Échele un vistazo a build.sh, si su variable de entorno "
+"JAVA_HOME está puesta y usa Linux, simplemente debería "
+"funcionar. En caso contrario, cambie las configuraciones. Recuerde, "
+"necesita tener instalado el SDK de Java."
+
+#: 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 ""
+"Ejecute build.sh (si ha descargado GMP) o build.sh "
+"dynamic (si ya tiene /usr/lib/libgmp.so).
             Quizás al compilar "
+"le arroje algunos errores sobre la falta de los archivos jni.h y "
+"jni_md.h. Puede copiar estos archivos desde su instalación de java al "
+"directorio core/c/jbigi/jbigi/include/, o arregle su $JAVA_HOME.
             "
+"Puede ejecutar build.sh desde el directorio "
+"core/c/, lo cual compilará todas las librerías jbigi "
+"disponibles dentro de jbigi.jar.
            . En dicho directorio debería "
+"crearse un archivo llamado libjbigi.so. Si no aparece y/o "
+"obtiene errores, por favor repórtelo."
+
+#: 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 ""
+"Siga las instrucciones de core/c/README para instalar la librería y "
+"ejecutar las pruebas de velocidad. Lea las últimas líneas del test de "
+"velocidad para obtener información adicional, debería ser algo como esto:"
+
+#: 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 ""
+"Si el nativo es 5-7 veces más rápido (o más), entonces todo está bien. Si"
+" no, avísenos."
+
+#: i2p2www/pages/site/misc/jbigi.html:129
+msgid "Copy libjbigi.so to your i2p directory"
+msgstr "Copie libjbigi.so a su carpeta i2p"
+
+#: i2p2www/pages/site/misc/jbigi.html:130
+msgid "Restart your I2P programs."
+msgstr "Reinicie sus 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 ""
+"En http://localhost:7657/stats.jsp"
+" las velocidades en crypto.elGamal.decrypt y "
+"crypto.elGamal.encrypt deberían ser mucho más rápidas."
+
+#: i2p2www/pages/site/misc/jrandom-awol.html:2
+msgid "Jrandom's Announcement"
+msgstr "Aviso de 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 ""
+"El siguiente mensaje fue recibido a mediados de Noviembre del 2007. No "
+"tenemos más información sobre jrandom."
+
+#: 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 ""
+"Más tarde, en un incidente no relacionado, la compañía de hosting de "
+"todos los servidores *.i2p.net (excepto forum.i2p.net) sufrió una perdida"
+" de corriente el 13 de Enero del 2008, y los servidores i2p.net no "
+"volvieron a funcionar. Ya que sólo jrandom tiene las credenciales para "
+"restaurar el servicio, y no puede ser contactado, movimos todos los "
+"servicios públicos a www.i2p2.de."
+
+#: 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 ""
+"Dos meses más tarde, aproximadamente, y por otras razones, forum.i2p.net "
+"fue movido a %(forum)s. "
+
+#: i2p2www/pages/site/misc/manual-wrapper.html:2
+#: i2p2www/pages/site/misc/manual-wrapper.html:4
+msgid "Manually Installing the Java Wrapper"
+msgstr "Instalar manualmente el Wrapper de 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 ""
+"El paquete de instalación para el ruter I2P"
+" viene con un wrapper de Java para las arquitecturas más comunes. Si su "
+"sistema no está soportado por nuestro instalador, o si desea actualizar "
+"el wrapper a una nueva versión, los siguientes pasos describen como "
+"instalar el wrapper a mano."
+
+#: 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 ""
+"Compruebe la página"
+" de descargas de Tanuki Software por su plataforma. ¿Está su "
+"plataforma listada? Si es así, ¡está de suerte! Descargue la versión más "
+"reciente para su sistema operativo y su CPU y vaya al siguiente paso."
+
+#: 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 ""
+"Si su plataforma no tiene todavía un wrapper disponible compilado, podría"
+" ser capaz de compilarlo usted mismo. Si desea hacerlo, vaya a compilar el wrapper para su sistema."
+
+#: i2p2www/pages/site/misc/manual-wrapper.html:27
+msgid "Using existing binaries"
+msgstr "Usando binarios ya existentes"
+
+#: i2p2www/pages/site/misc/manual-wrapper.html:28
+msgid "In the steps below, $I2P means the location I2P was installed to."
+msgstr ""
+"En los pasos de más abajo, $I2P significa el lugar donde ha sido "
+"instalado I2P."
+
+#: 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 "Intente iniciar I2P usando $I2P/i2prouter start"
+
+#: 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 "tail -f /tmp/wrapper.log y busque los problemas."
+
+#: 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 ""
+"Si esto no funciona necesitará ejecutar runplain.sh para "
+"arrancar I2P."
+
+#: i2p2www/pages/site/misc/manual-wrapper.html:43
+msgid "Compiling from source"
+msgstr "Compilando desde las fuentes"
+
+#: 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 ""
+"Estos pasos han funcionado para compilar el wrapper en un sistema mipsel "
+"ejecutando debian. Estos pasos tendrán que ser cambiados"
+" dependiendo de su sistema."
+
+#: 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 ""
+"Descargue el archivo con las fuentes para la versión del wrapper desde la página de "
+"descarga del wrapper."
+
+#: i2p2www/pages/site/misc/manual-wrapper.html:49
+msgid "Extract the tarball"
+msgstr "Descompriba el archivo"
+
+#: i2p2www/pages/site/misc/manual-wrapper.html:51
+msgid ""
+"Set environment variables ANT_HOME and "
+"JAVA_HOME. For example, in Debian:"
+msgstr ""
+"Ajuste las variables ANT_HOME y JAVA_HOME. For "
+"ejemplo en Debian:"
+
+#: 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 ""
+"Ya que no existe un Makefile para Mipsel, haremos una copia de un "
+"makefile ya existente:"
+
+#: i2p2www/pages/site/misc/manual-wrapper.html:56
+msgid "Now we can attempt to compile the wrapper:"
+msgstr "Ahora podemos intentar compilar el wrapper:"
+
+#: i2p2www/pages/site/misc/manual-wrapper.html:57
+msgid "use ./build64.sh if you have a 64bit CPU and JVM"
+msgstr "use ./build64.sh si tiene una CPU y JVM de 64bit"
+
+#: i2p2www/pages/site/misc/manual-wrapper.html:58
+msgid "Copy the wrapper into its proper place:"
+msgstr "Copie el wrapper al su lugar correcto:"
+
+#: 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 ""
+"Aquí hay un esquema para una aplicación proxy WWW mínima para usar sobre "
+"I2P "
+
+#: 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 ""
+"Usar HTTP sobre I2P usando un I2PTunnel. Cuando la librería base "
+"SocketLibrary esté lista, los únicos cambios significantes serán que el "
+"'wrapRequest' y 'unwrapRequest' serán alojados funcionalmente en la "
+"librería socketLibrary, no en el ruter (pero las versiones más nuevas de "
+"SocketLibrary serán capaces de usar ACK selectivo y windows de grandes "
+"tamaños, permitiendo que sean omitidos más Acks)"
+
+#: 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 ""
+"Un clase optimizada, diseñada para manejar archivos y páginas de "
+"sólo128KB [1], pude funcionar mucho más rápida:"
+
+#: 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 ""
+"La diferencia en la carga y latencia de la red es significante - esto es "
+"esencialmente una versión UDP de HTTP. En las webs normales no podemos "
+"hacer esto, ya que la mayoría de las peticiones y respuestas HTTP son "
+"mayores de lo que permiten los paquetes UDP, pero en I2P, los mensajes "
+"pueden ser más grandes. El ahorro para la red viene de que no necesitamos"
+" enviar ningún mensaje ACK - al contrario que las peticiones wrap/unwrap "
+"anteriores (que unen un DataMessage con un DeliveryStatusMessage para "
+"asegurarse que que ha sido entregado), el proxy MinWWW se encarga de "
+"estos reenvíos (si es necesario - en los I2PTunnel no hay reenvíos)."
+
+#: 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 ""
+"Los datos que el servidor y el proxy MinWWW necesitan envolver son "
+"triviales - cuando el proxy quiere enviar un \"GET /\", lo antepone con "
+"la destinación I2P y envía la petición, seguido por un ID de petición de "
+"4 bytes. El servidor MinWWW recibe entonces estas peticiones, contacta "
+"con el servidor HTTP apropiado, envía la petición, espera por la "
+"respuesta, y envía una respuesta al proxy MinWWW con la respuesta dentro,"
+" y con el ID original de la petición como prefijo. Esa respuesta se toma "
+"y se envía de vuelta al navegador, y se cierra la conexión."
+
+#: 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 ""
+"Además, el proxy MinWWW puede elegir el servidor MinWWW a usar de una "
+"lista, a través de round robin u otro algoritmo, con lo que habría "
+"múltiples outproxies unidos transparentemente. El ancho de banda "
+"necesario para ejecutar estos outproxies se reduce drásticamente, ya que "
+"sólo maneja archivos de 128KB (tambien conocido como: nadie va a bajar "
+"porno, software, etc)."
+
+#: 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 ""
+"Esta funcionalidad /está/ limitada, pero 128KB es mucho para una simple "
+"respuesta o petición HTTP. Los diagramas de más arriba además no son "
+"realistas en sus saltos - ROUTERA nunca conectará directamente con "
+"ROUTERB, ROUTERA enviará sus mensajes a través de dos ruters de salida "
+"adicionales, entonces se reenviará a dos túneles adicionales hacia "
+"ROUTERB, con lo que el retraso es significante - mientras que lo anterior"
+"  sólo ahorra 11 pasos, 8 de estos pasos necesitan atravesar el camino "
+"entero de túneles (4 saltos más remotos cada vez), dejando MinWWW con "
+"sólo dos recorridos completos (uno para la petición, otro para la "
+"respuesta), en vez de 10."
+
+#: 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 ""
+"Implementar el proxy y el servidor MinWWW debería ser bastante fácil - "
+"leer una petición HTTP del cliente (quizás sólo empezar con un HTTP GET; "
+"dejando HTTP POST para más tarde), envolver el mensaje, y esperar por la "
+"respuesta. El servidor de turno sólo necesita  analizar la petición para "
+"abrir un socket o una URL, enviar la petición, esperar por la respuesta y"
+" enviarlo de vuelta a través de la red. ¡Si alguien implementase esto, "
+"sería Genial!  :)"
+
+#: 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 ""
+"[1] ¿Por qué archivos de 128KB? Actualmente I2P permite mensajes de "
+"tamaño arbitrario, pero eso se eliminará ya que implica un gasto de "
+"memoria en los ruters intermedios. Los túneles I2P están limitados a "
+"128KB y no ha sido un problema, son lo que quizás podría ampliarse a "
+"256KB cuando las espcificaciones de I2CP se actualicen)"
+
+#: 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 ""
+"Ha habido discusiones durante unos meses sobre una aplicación de blogging"
+" llamada ahora \"MyI2P\". Aunque la discusión original se perdió, fuimos "
+"capaces de conseguirla con el cache de "
+"Google. "
+
+#: 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 ""
+"La aplicación en si misma no está implementada, y las ideas detrás de "
+"ella se han hecho menos ambiciosas con el tiempo, pero aún son válidas y "
+"el plan actual es tener el núcleo de MyI2P "
+"disponible con la versión 1.0 de I2P. Esto incluirá una libreta de "
+"direcciones distribuida para permitir un sistema de nombres seguro y "
+"distribuido aunque signifique sacrificar la necesidad de unicidad global "
+"- básicamente cada uno tiene su libreta de direcciones locales y puede "
+"'suscribirse' a las libretas de direcciones de otros usuarios, "
+"permitiendo a MyI2P obtener periódicamente nuevos nombres de destinos "
+"(dejando al usuario arreglar los conflictos). Ademas de la libreta de "
+"direcciones, habrá un sistema de blogs distribuidos usando una parte "
+"segura de bbcode, para "
+"proveer un LiveJournal "
+"anónimo, una 'lista de amigos' y un control de acceso transparente "
+"(autentificado por los datagramas de I2P "
+"con normas definidas basadas en la libreta de direcciones)."
+
+#: 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 ""
+"Las funcionalidades adicionales, como la integración del almacenamiento "
+"de copias DHT o la transferencia de archivos cmoo 'adjuntos' puede "
+"añadirse más tarde. El email puede estar listo o no en esta primera "
+"versión, aunque su implementación es esencialmente simplemente una "
+"entrada de blog con acceso privado, con lo que quizás algún diseñador de "
+"aplicaciones gráficas podría hacer algo. Esportando los datos a RSS o el "
+"acceso a través de ATOM podría ser unas opciones también."
+
+#: i2p2www/pages/site/misc/ratestats.html:2
+#: i2p2www/pages/site/misc/ratestats.html:5
+msgid "RateStat list"
+msgstr "Lista de RateStat"
+
+#: i2p2www/pages/site/misc/ratestats.html:6
+msgid "I2P enables the collection of a wide range of rates."
+msgstr "I2p permite un gran número de diferentes velocidades."
+
+#: 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 ""
+"La lista fue obtenida usando el siguiente comando en el directorio "
+"principal de la rama 2p.i2p:"
+
+#: i2p2www/pages/site/misc/ratestats.html:10
+msgid "All options aren't needed, but it works."
+msgstr "No son necesarias todas las opciones, pero funciona."
+
+#: 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 ""
+"El código fuente de i2p es mantenido en varios repositorios distribuidos "
+"de monotone. Vea la Web de "
+"Monotone para mas información sobre monotone. Vea este foro sobre i2p y "
+"monotone para obtener mas información de como comenzar y descargar el"
+" código fuente anónimamente. También hay una guía rápida en la web de nuevos desarrolladores."
+
+#: 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 ""
+"Si desea obtener el código fuente no anónimamente, descargue desde el "
+"servidor publico mtn.welterde.de.\n"
+"La rama del código fuente de i2p es \"i2p.i2p\"."
+
+#: i2p2www/pages/site/misc/transition-guide.html:21
+msgid "Guide"
+msgstr "Guía"
+
+#: i2p2www/pages/site/misc/transition-guide.html:22
+msgid ""
+"\n"
+"The following is a detailed guide by Complication."
+msgstr ""
+"\n"
+"Lo siguiente es una guía detallada hecha por Complication."
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:2
+msgid "How to Upgrade from 0.6.1.30 and Earlier"
+msgstr "Como actualizar desde la versión 0.6.1.30 y anteriores."
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:6
+msgid "Upgrading from 0.6.1.30 and Earlier Releases"
+msgstr "Actualizando desde 0.6.1.30 y versiones anteriores."
+
+#: 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 ""
+"Desde que el programador principal de i2p se "
+"ausentó sin avisar, AWOL, no tenemos su clave de actualización "
+"firmada o acceso a www.i2p[.net] o dev.i2p[.net]. Complication y zzz han "
+"generado nuevas claves de firmado, y ellos y Amiga proveen alojamiento a "
+"los archivos de actualización. Estos cambios tienen que ser configurados "
+"en su ruter para que tengan efecto. "
+
+#: 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 ""
+"Haga los siguientes cambios de configuración y su ruter instalará "
+"automáticamente la última versión"
+
+#: 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 ""
+"Recomendamos el proceso automático ya que verificará la clave del archivo"
+" de actualización firmado. Si no hace estos cambios, puede descargar "
+"manualmente el archivo i2pupdate.zip de la página de descargas."
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:34
+#, python-format
+msgid "Change the News URL to: %(url)s"
+msgstr "Cambie el enlace de noticias a: %(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 ""
+"Seleccione una de las siguientes enlaces de actualización aleatoriamente "
+"e introdúzcalo dentro de la casilla Update URL:"
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:43
+msgid "Check the box \"Update through the eepProxy?\""
+msgstr "Active la casilla \"Actualizar a través del eepProxy?\""
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:44
+msgid "Click \"Save\""
+msgstr "Pulse \"Guardar\""
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:51
+msgid "Add the following line:"
+msgstr "Añada la siguiente línea:"
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:55
+msgid "Click \"Apply\""
+msgstr "Pulse \"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 ""
+"Ahora estas listo para recibir automáticamente el archivo de "
+"actualización, ya sea configurando su política de actualizaciones a "
+"\"descargar e instalar\" o pulsando en el enlace \"actualización "
+"disponible\" cuando aparezca."
+
+#: 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 ""
+"Si deseas verificar las claves de actualización de confianza, se "
+"encuentran también subidas y firmadas aquí. "
+"Gracias por su ayuda durante la transición. Por favor, para pedir ayuda "
+"contacte con nosotros en #I2P."
+
diff --git a/i2p2www/translations/es/LC_MESSAGES/priority.po b/i2p2www/translations/es/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..c1a87769
--- /dev/null
+++ b/i2p2www/translations/es/LC_MESSAGES/priority.po
@@ -0,0 +1,3348 @@
+# Spanish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Fito Jayme , 2013
+# Daniel Mustieles , 2013
+# m1xxy , 2011
+# olivertrash , 2013
+# strel, 2013
+# trolly, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-12-25 13:02+0000\n"
+"Last-Translator: strel\n"
+"Language-Team: Spanish "
+"(http://www.transifex.com/projects/p/I2P/language/es/)\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/blog/category.html:2
+msgid "Blog Category"
+msgstr "Categorías del Blog"
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr "ATOM Feed del Blog de I2P para la Categoría: %(category)s"
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:92
+msgid "Blog"
+msgstr "Blog"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "ATOM feed del blog de I2P"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr "Publicado el %(date)s por %(author)s"
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "Mas entradas del blog…"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr "Publicado:"
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "Autor:"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Paquetes de I2P para Debian"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+"Los paquetes de Debian han sido probados y deberían funcionar en"
+" las plataformas x86/x86_64 ejecutando:"
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr "Ubuntu (Precise 12.04 y posteriores)"
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr "Debian Linux (Squeeze y más nuevos) & kFreeBSD"
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+"Los paquetes I2P puede que funcionen en los sistemas no listados"
+" más abajo. Por favor, reporte cualquier problema con los paquetes en el"
+"  Trac en https://trac.i2p2.de. "
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Opción 1: Versiones recientes de Ubuntu y sus "
+"derivados (Pruebe esto si no usa Debian)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr "Opción 2: Debian (Incluidos derivados de Debian)"
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+"Instrucciones para Ubuntu Precise Pangolin (y más nuevos) y derivados "
+"como Linux Mint & Trisquel"
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Añadir el PPA desde la línea de comandos e instalar I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Abra un terminal e introduzca:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"Este comando añadirá el PPA (archivo de paquetes personal) a su "
+"/etc/apt/sources.list.d\n"
+"y obtendrá la clave GPG del repositorio que lo ha firmado. La clave GPG "
+"garantiza que los paquetes no han sido modificados desde que se crearon."
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "Notifique a su gestor de paquetes el nuevo PPA introduciendo:"
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+"Este comando obtendrá la última lista de aplicaciones de cada\n"
+"repositorio que esté habilitado en su sistema, incluyendo\n"
+"el PPA de I2P que hemos añadido anteriormente."
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "¡Ahora está listo para instalar I2P!"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "Añadir el PPA usando Synaptic"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+"Abra Synaptic (Sistema -> Administración -> Gestor de paquetes "
+"Synaptic)."
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+"Una vez se abra Synaptic, seleccione Repositorios en el menú "
+"Configuración."
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"Haga clic en la pestaña Otras fuentes y seleccione "
+"Añadir. Pegue ppa:i2p-maintainers/i2p en el campo  "
+"la línea-APT y pulse Añadir fuente. Pulse el botón "
+"Cerrar y luego Recargar."
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+"En la casilla de Filtrado Rápido escriba i2p y pulse Intro. "
+"Cuando devuelva i2p en la lista de resultados, haga clic con"
+" el botón secundario sobre i2p y seleccione Marcar para "
+"instalación.  Después de hacer esto puede que vea un cuadro "
+"emergente que diga ¿Marcar cambios adicionales?. Si es así, "
+"pulse Marcar y luego Aplicar."
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+"Tras completar el proceso de instalación puede pasar a la siguiente\n"
+"parte de la inicialización de I2P, y "
+"configurarlo para su sistema."
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr "Instrucciones para Debian"
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+"Nota: Los siguientes pasos deberían ejecutarse con acceso de "
+"administrador (por ejemplo cambiando al usuario root con \"su\" o "
+"ejecutando los comandos con \"sudo\" delante)."
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr "Añada líneas como las siguientes al %(file)s."
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the  key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+"Descargue la clave usada para firmar el "
+"repositorio y añádala con apt:"
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr "Notifique a su gestor de paquetes del nuevo repositorio ejecutando"
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+"Este comando descargará la uĺtima lista de aplicaciones de cada "
+"repositorio activo en sus sistema, incluyendo el repositorio de I2P "
+"añadido en el paso 1."
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+"¡Ahora está listo para instalar I2P! Al instalar el paquete con el "
+"anillo de claves se asegurará que recibe las actualizaciones"
+" para la clave GPG del repositorio."
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+"Tras completar el proceso de instalación puede pasar a la siguiente parte"
+" de la inicialización de I2P, y "
+"configurarlo para su sistema."
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "Tareas post-instalación"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+"El router I2P se puede iniciar usando estos paquetes I2P de las tres "
+"maneras siguientes:"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+""a petición" usando el script i2prouter. Simplemente ejecute\n"
+""i2prouter start" en una línea de comandos.\n"
+"(Nota: ¡No utilice sudo ni lo ejecute como root!)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""a petición" sin el java service "
+"wrapper (encapsulador como servicio para java, \n"
+"necesario en sistemas no-Linux/no-x86) ejecutando \"i2prouter-"
+"nowrapper\".\n"
+"(Nota: ¡No utilice sudo ni lo ejecute como root!)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"como un servicio que se ejecuta automáticamente al arrancar el sistema, \n"
+"incluso antes de abrir sesión de usuario del sistema. Este servicio puede"
+" \n"
+"activarse ejecutando \"dpkg-reconfigure i2p\" como root, o "
+"usando sudo. \n"
+"Esta es la forma recomendada de hacerlo."
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+"Si puede, cuando instale por primera vez, recuerde ajustar su "
+"NAT/cortafuegos. Los puertos a abrir pueden verse en la web de configuración de la "
+"red en la consola del ruter. Si necesita un guía para abrir sus "
+"puertos, la web portforward.com "
+"puede serle de utilidad."
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"Por favor revise y ajuste las configuraciones de ancho de banda\n"
+"en la página de "
+"configuración, ya que los valores por defecto de\n"
+"96 KB/s de bajada / 40 KB/s de subida son bastante conservadores. "
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"Si quiere acceder a eepsites (sitios web en la red I2P) a través su "
+"navegador, eche un vistazo a la página sobre configuración para proxy del navegador "
+"para ver unas instrucciones sencillas."
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Descargas"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Descargar I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Dependencias"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+"\n"
+"Java Runtime 1.5 o superior. (Recomendado Oracle "
+"Java Versión 7, OpenJDK 7, o IcedTea7, excepto para Raspberry Pi: Oracle 8 Early Access, PowerPC: IBM SDK 7) 
             Determine su versión instalada de Java aquí o "
+"escriba java -version en su terminal.\n"
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "Instalación"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr "o seleccione un enlace alternativo"
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Descargue este archivo y ejecútelo."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Descargue el archivo y pulse dos veces sobre él (si eso funciona) o "
+"ejecute java -jar i2pinstall_%(i2pversion)s.jar en la "
+"terminal para iniciar el instalador. Puede ser que pueda pulsar botón "
+"derecho y seleccionar "Abrir con Java"."
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "Instalación desde línea de comandos (sistemas headless):"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Descargue el instalador gráfico %(i2pversion)s OSX de abajo y ejecute "
+"java -jar i2pinstall_%(i2pversion)s.jar -console en la "
+"terminal."
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Descargue este archivo y haga doble clic sobre él (si eso funciona) o "
+"escriba\n"
+"java -jar i2pinstall_%(i2pversion)s.jar en un terminal para "
+"ejecutar el instalador. \n"
+"En algunas plataformas puede que sea capaz de hacer clic con el botón \n"
+"secundario y seleccionar "Abrir con Java"."
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Descargue este archivo de instalador gráfico y ejecute \n"
+"java -jar i2pinstall_%(i2pversion)s.jar -console desde la "
+"línea de comandos."
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Hay paquetes disponibles para Debian y Ubuntu."
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+"    The latest dev build is version %(devbuild)s, and is available from\n"
+"    str4d's eepsite."
+msgstr ""
+"El fichero de arriba es la versión actual estable. La última versión de \n"
+"desarrollo es la versión %(devbuild)s, y está disponible desde el \n"
+"eepsite de str4d."
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+"      are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+"      the other."
+msgstr ""
+"La versión estable y en desarrollo del APK I2P no son compatibles, ya que"
+" están firmadas por zzz y str4d respectivamente. Desinstale una antes de "
+"instalar la otra."
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "Paquete de código fuente "
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+"    or via Git from git.repo.i2p or Github.\n"
+"    
            \n"
+"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+"También puede descargar las fuentes desde monotone o a través de Git desde git.repo.i2p o Github. 
             Ejecute (tar xjvf "
+"i2psource_%(i2pversion)s.tar.bz2 ; cd i2p-%(i2pversion)s ; ant "
+"pkg) y después ejecute el instalador gráfico o la instalación "
+"headless como más arriba."
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Estos archivos están firmados por zzz, cuya "
+"clave está aquí."
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"I2P también puede descargarse desde las páginas de nuestro proyecto en Launchpad y en Google Code."
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"Después de ejecutar el instalador en Windows simplemente pulse en el "
+"botón \n"
+"\"Iniciar I2P\" que abrirá la consola del router I2P, \n"
+"donde encontrará más instrucciones."
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"En sistemas tipo-Unix, I2P puede ser ejecutado como un servicio usando \n"
+"el script \"i2prouter\" ubicado en el directorio seleccionado para I2P.\n"
+"En un terminal, llendo a ese directorio y ejecutando \"sh i2prouter "
+"status\" debería \n"
+"mostrarle el estado del router I2P. Los argumentos \"start\", \"stop\" y "
+"\"restart\" \n"
+"controlan el servicio. A la consola del router se puede "
+"acceder en su \n"
+"ubicación habitual. Para usuarios de OpenSolaris y otros sistemas para "
+"los que \n"
+"no está soportado el wrapper (i2psvc, encapsulador como servicio para "
+"Java), ejecute el router I2P con \"sh runplain.sh\" en lugar del "
+"anterior."
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"Cuando instale I2P por primera vez, por favor recuerde ajustar su \n"
+"NAT/cortafuegos sin olvidarse de los puertos que I2P usa para "
+"Internet, \n"
+"descritos aquí. Si ha abierto con éxito su "
+"puerto TCP de entrada en su \n"
+"NAT/cortafuegos, habilítelo también en la página de configuración."
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"Además, por favor revise y ajuste su configuración de ancho de "
+"banda \n"
+"en la página de "
+"configuración, \n"
+"ya que la configuración por defecto de 96 KBps de bajada  / 40 KBps de "
+"subida \n"
+"es bastante lenta."
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "Actualizaciones desde versiones anteriores:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr ""
+"Hay disponibles actualizaciones de cambio de versión manuales y "
+"automáticas."
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "Actualizaciones automáticas"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+"Si esta ejecutando la versión 0.7.5 o posterior su router I2P debería "
+"detectar \n"
+"las nuevas versiones automáticamente. Para actualizar, cuando aparezca el"
+" \n"
+"botón 'Descargar actualización' en la consola de su router simplemente "
+"púlselo."
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"Debido a un fallo en la versión 0.7.6, aquellos cuya primera instalación "
+"de I2P \n"
+"fuera con esa versión y no la hayan actualizado manualmente, pueden "
+"obtener \n"
+"un error \"la versión descargada no es mayor que la versión actual\", y "
+"deben \n"
+"usar la actualización manual de debajo."
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Si utiliza la versión 0.7.4 o anterior, por favor lea las notas de la versión 0.7.5 \n"
+"para obtener información importante acerca de cómo configurar su router "
+"I2P \n"
+"para descargar las actualizaciones automáticamente."
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Si utiliza la versión 0.6.1.30 o anterior, por favor lea las instrucciones \n"
+"para obtener información importante acerca de cómo configurar su router "
+"I2P \n"
+"para descargar las actualizaciones automáticamente."
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+"    router console "
+"allowing\n"
+"    you to download and install the new release by just clicking on that\n"
+"    link."
+msgstr ""
+"Si ha reconfigurado su router I2P siguiendo las instrucciones, debería ver \n"
+"un enlace en la consola de su"
+" router permitiéndole descargar \n"
+"e instalar la nueva versión pulsando en ese enlace."
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr "Como alternativa, puede usar el método manual especificado debajo."
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "Actualizaciones manuales"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and rename as i2pupdate.zip.\n"
+"    (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+"    resulting i2pupdate.zip to your I2P installation directory).  You do"
+" \n"
+"    NOT need to unzip that file."
+msgstr ""
+"Descargue este archivo a su directorio de instalación de I2P y "
+"renómbrelo \n"
+"como i2pupdate.zip. (Como alternativa, puede obtener el código "
+"fuente, \n"
+"como el del enlace de arriba, y ejecutar \"ant updater\", luego copie el "
+"archivo \n"
+"resultante i2pupdate.zip al directorio de instalación de I2P). NO "
+"necesita descomprimir ese archivo."
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+"Pulse \"Reiniciar\""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "Vaya a por una taza de horchata/café/cacao/mate y vuelva en 11 minutos."
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"El archivo está firmado por zzz, cuya clave "
+"está aquí."
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "Versiones anteriores"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"Las versiones anteriores están disponibles en Google "
+"Code y \n"
+"Launchpad, y dentro de la"
+" red I2P en %(echelon)s."
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "Selección de servidor espejo ('mirror')"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "Archivo:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "Cualquier servidor espejo ('mirror')"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+"Para reclamar la recompensa, el autor no ha de estar pagado por ninguna "
+"otra\n"
+"organización por este trabajo (ej. los estudiantes del GSoC no son "
+"válidos)."
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations.  Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"La cuantía de las recompensas puede aumentar por posteriores donaciones. "
+"¿Cree que son importantes? ¡Haga su donación "
+"indicando la cantidad \n"
+"que destina a la recompensa %(donatename)s!"
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "No encontrado"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+"Lo que estaba buscando... se llama de otra forma, no existe o ha sido "
+"borrado."
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "Error del servidor"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "Error 500 del servidor"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "Humm... el servidor ha encontrado algún problema."
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "Servidores espejo"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "Seguro"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "Varios"
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Enlaces"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "Aviso legal"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "¡      Camisetas!"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "Europa"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "EEUU"
+
+#: i2p2www/pages/global/footer.html:31 i2p2www/pages/global/nav.html:133
+msgid "Donate"
+msgstr "Donar"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr "Saltar navegación"
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "Logo de I2P"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "El Proyecto de Internet Invisible"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+"Esta página fue actualizada por última vez el %(lastupdated)s y es "
+"precisa con la versión %(accuratefor)s del router I2P."
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "Esta página fue actualizada por última vez el %(lastupdated)s."
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "Esta página es precisa con la versión %(accuratefor)s del router I2P."
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr "Anterior"
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr "Siguiente"
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr "Publicado en"
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "Acerca de"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Introducción a I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "Comparaciones"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "Introducción a las comparaciones"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Otras redes anónimas"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Documentación"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Índice de la documentación"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "¿Cómo funciona?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "Introducción suave"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "Introducción técnica"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "Modelo de amenazas"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Enrutamiento ajo ('garlic')"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "Base de datos de red"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "Enrutamiento de túneles"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "Selección de pares ('peers')"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Cifrado"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Especificaciones"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "Fichero por bloques ('Blockfile')"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "Estructuras comunes"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "Ficheros de configuración"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:56
+msgid "Datagrams"
+msgstr "Datagramas"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr "Archivos GeoIP"
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:88
+msgid "Plugins"
+msgstr "Complementos"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:55
+msgid "Streaming library"
+msgstr "Librería de streaming"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "Creación de túneles"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "Mensajes de túneles"
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "Actualizaciones de software"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:60 i2p2www/pages/global/nav.html:113
+msgid "Applications"
+msgstr "Aplicaciones"
+
+#: i2p2www/pages/global/nav.html:62
+msgid "Supported applications"
+msgstr "Aplicaciones soportadas"
+
+#: i2p2www/pages/global/nav.html:63
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Protocols"
+msgstr "Protocolos"
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Protocol stack"
+msgstr "Pila del protocolo"
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Transports"
+msgstr "Transportes"
+
+#: i2p2www/pages/global/nav.html:75
+msgid "Transport layer overview"
+msgstr "Introducción a la capa de transporte"
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Tunnels"
+msgstr "Túneles"
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Tunnel implementation"
+msgstr "Implementación de túneles"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Unidirectional tunnels"
+msgstr "Túneles unidireccionales"
+
+#: i2p2www/pages/global/nav.html:84
+msgid "Old implementation"
+msgstr "Implementación antigua"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Naming and addressbook"
+msgstr "Nombres y libreta de direcciones"
+
+#: i2p2www/pages/global/nav.html:91
+msgid "Team"
+msgstr "Equipo"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Hall of Fame"
+msgstr "Salón de la fama"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Academic papers and peer review"
+msgstr "Documentos académicos y revisión por pares"
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Presentations, tutorials and articles"
+msgstr "Presentaciones, tutoriales y artículos"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Contact us"
+msgstr "Contacte con nosotros"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Help"
+msgstr "Ayuda"
+
+#: i2p2www/pages/global/nav.html:101
+msgid "FAQ"
+msgstr "Preguntas frecuentes (FAQ)"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "How to browse I2P"
+msgstr "Como navegar en I2P"
+
+#: i2p2www/pages/global/nav.html:103
+msgid "Glossary"
+msgstr "Glosario"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Performance"
+msgstr "Rendimiento"
+
+#: i2p2www/pages/global/nav.html:105 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Foros"
+
+#: i2p2www/pages/global/nav.html:108
+msgid "Volunteer"
+msgstr "Voluntario"
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Get involved!"
+msgstr "¡Implíquese!"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Develop"
+msgstr "Desarrollo"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Licenses"
+msgstr "Licencias"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Release signing keys"
+msgstr "Claves de firmado de versiones"
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Signed keys"
+msgstr "Claves firmadas de desarrolladores"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Developers keys"
+msgstr "Claves de los desarrolladores"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Bug tracker"
+msgstr "Monitorizador de fallos"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Academic research"
+msgstr "Investigación académica"
+
+#: i2p2www/pages/global/nav.html:122
+msgid "Open research questions"
+msgstr "Preguntas de investigación"
+
+#: i2p2www/pages/global/nav.html:123
+msgid "Guides"
+msgstr "Guías"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "New developers"
+msgstr "Nuevos desarrolladores"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Using an IDE with I2P"
+msgstr "Usar un IDE con I2P"
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Developer guidelines and coding style"
+msgstr "Directrices de desarrollo y estilo del código"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "New translators"
+msgstr "Nuevos traductores"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Bounties"
+msgstr "Recompensas"
+
+#: i2p2www/pages/global/nav.html:134 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Reuniones"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Roadmap"
+msgstr "Hoja de ruta"
+
+#: i2p2www/pages/global/nav.html:136
+msgid "Task list"
+msgstr "Lista de tareas"
+
+#: i2p2www/pages/global/nav.html:139
+msgid "Language"
+msgstr "Idioma"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr "ATOM feed de las reuniones de I2P"
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "Registros ('logs') de anteriores reuniones de I2P"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr "Las reuniones no se llevarán acabo hasta que se elija una fecha adecuada."
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"Si tiene algo que discutir por favor busque a los desarrolladores en "
+"#i2p-dev en el IRC. Las actualizaciones del "
+"estado de los desarrolladores  también están disponibles."
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr "Reuniones %(id)s de desarrollo de I2P"
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr "Registro completo del IRC"
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "Por asunto"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "Por fecha"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "Por autor"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
            \n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
            \n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+"Por favor, envíe las entradas nuevas o corregidas a class=\"marksource "
+"newline\" title=\"New line\"> class=\"marksource tag\">class=\"marksource tag\">class=\"marksource var\">%(email)sclass=\"marksource "
+"tag\">class=\"marksource tag\">.class=\"marksource tag\">
            class=\"marksource newline\" title=\"New line\">\n"
+"Si puede . use el formato  BibTeX; vea ourclass=\"marksource newline\" "
+"title=\"New line\"> class=\"marksource tag\">%(bibtex)s\">BibTeX source pageclass=\"marksource tag\"> for "
+"examples.class=\"marksource tag\">
            class=\"marksource newline\" "
+"title=\"New line\">\n"
+"Recuerde incluir las URLs si es posible:class=\"marksource newline\" "
+"title=\"New line\">\n"
+"class=\"marksource tag\">%(citeseer)s\">offline papers are less usefulclass=\"marksource "
+"tag\">."
+
+#: i2p2www/pages/papers/list.html:94
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"Free Haven's anonymity bibliography."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Contacto"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr "Correo electrónico"
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like OFTC,\n"
+"  EIN and Freenode.\n"
+"  All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+"Nuestra red IRC principal es la red Irc2P dentro de I2P; tras la "
+"instalación inicial de I2P ya hay creado por defecto un túnel a esta red."
+"  Estamos presentes también en múltiples redes como OFTC,  EIN y Freenode. Todos los canales "
+"relacionados con I2P en esas redes están unidos a los canales principales"
+" de Irc2P a través de 'relay bots'."
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Lista de canales:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "Discusión general sobre I2P"
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "Temas aparte"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "Charla sobre el desarrollo"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Canal de ayuda"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"La mayoría de las discusiones sobre el desarrollo de I2P ocurren en el foro de desarrolladores de I2P. "
+"Normalmente este es el mejor lugar para comenzar a preguntar, si el canal"
+" de desarrollo del IRC está inactivo."
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "Listas de correo"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+"I2P tiene una lista de correo, pero raramente se usa ya que el pequeño "
+"grupo de desarrolladores actual prefiere comunicarse vía IRC o vía foro "
+"de desarrolladores. Esto podría cambiar en el futuro."
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "Suscripción"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+"Para suscribirse a una lista de correos vaya a la página de información "
+"de la lista (enlazada debajo) y rellene el formulario. Puede usar la "
+"dirección de email  interna de I2P ( foobar@mail.i2p )."
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "Darse de baja"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+"Para desuscribirse de una lista de correos o cambiar las opciones de su "
+"suscripción, vaya a la página de información de la lista (enlazada "
+"debajo) e introduzca el correo electrónico de su suscripción."
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Listas"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Archivo"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+"Discusión general sobre I2P - cualquier cosa que no encaje en otras "
+"listas va aquí."
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+"¿No le gustan las listas de correo? Entonces esto es para usted. Todas "
+"las listas de correo también están disponibles por NNTP."
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr "Mapeado-de-lista-de-grupos:"
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Servidores:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Preguntas frecuentes (FAQ)"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Índice"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "General"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "¿Sobre qué sistemas funcionará I2P?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+"¿Qué es un \"eepsite\" y cómo configuro mi navegador para que pueda "
+"usarlo?"
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "Mi router tiene muy pocos pares ('peers') activos, ¿está bien esto?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr "¿Qué significan los números activos x/y en la consola del router?"
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+"¡Mis pares activos / pares conocidos / túneles participantes / conexiones"
+" / ancho de banda, varían dramáticamente a lo largo del tiempo! ¿Está mal"
+" algo?"
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "¿Es seguro usar un proxy de salida de I2P a Internet?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr "¿La mayoría de los eepsites dentro de I2P están caídos?"
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "¿Qué puertos usa I2P?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "¿Por qué I2P tiene abierto el puerto 32000 escuchando conexiones?"
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "Creo que he encontrado un error, ¿dónde puedo reportarlo?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr ""
+"¿Qué ha pasado con *.i2p.net? ¿Qué ha pasado con jrandom? ¿Está muerto "
+"I2P?"
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "¡Tengo una pregunta!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr "Configuración"
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+"Mi router ha estado activo durante varios minutos y aún tiene ninguna o "
+"muy pocas conexiones"
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "¿Por qué es tan lento I2P?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+"Me faltan montones de equipos en mi libreta de direcciones. ¿Cuáles son "
+"buenos enlaces para suscribirse?"
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "¿Cómo configuro mi propio eepsite?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "¿Preguntas sobre el complementos de I2P Bittorrent / I2PSnark / Azureus?"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "¿Cómo conecto a un IRC dentro de I2P?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "No puedo acceder a la Internet regular a través de I2P."
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "No puedo acceder a sitios https:// o ftp:// a través de I2P."
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr "¿Es posible usar I2P como un proxy SOCKS?"
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "¿Cómo configuro mi navegador web?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+"¿Cómo puedo acceder a la consola web desde máquinas remotas y cómo la "
+"protejo con contraseña?"
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr "¿Cómo puedo usar aplicaciones desde máquinas remotas?"
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr "¿Cómo resiembro ('reseed') manualmente?"
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "¿¡ Mi router está usando demasiada CPU !?"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "Errores de concepto"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr "¿Cómo accedo al IRC, Bittorrent u otros servicios en la Internet regular?"
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+"¿Es mi router un \"nodo de salida\" (outproxy) hacia la Internet regular?"
+" No quiero que lo sea."
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+"Estoy en contra de ciertos tipos de contenido. ¿Cómo evito almacenarlos, "
+"distribuirlos o acceder a ellos?"
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Errores y sus soluciones"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+"¡Utilizo FreeBSD y cuando ejecuto I2P recibo un error sobre "
+"libm.so.4!"
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+"En wrapper.log (registro del encasulador como servicio para "
+"Java) veo un error indicando Protocol family unavailable "
+"(familia de protocolos no disponible) ocurrido cuando I2P estaba "
+"cargandose. "
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "enlace"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+"Aunque se sabe que I2P se ha ejecutado en sistemas tan pobres como un "
+"Pentium II de 64MB de RAM, tendrá una experiencia mucho mejor en un "
+"Pentium III (o mejor) con 128 MB de RAM (o más). Un comparación de rendimiento de varios JREs puede "
+"encontrarse en %(chart)s, pero resumiendo: si "
+"es posible, utilice Sun/Oracle Java o OpenJDK."
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+"I2P ha sido probado en Windows, Linux, FreeBSD (vea la nota de debajo), OSX y OpenSolaris. Se está trabajando "
+"para llevar I2P a la plataforma Android."
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr "Aquí tienen algunos sitios, elija uno o más."
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "Discútalo con los desarrolladores en el canal #i2p-dev en el IRC"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+"Por favor, incluya la información relevante de los registros ('logs') del"
+" router y del wrapper (encapsulador como servicio para Java)."
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+"La suscripción por defecto es a http://www.i2p2.i2p/hosts.txt que "
+"raramente se actualiza. Si no tiene otra suscripción, a menudo tendrá que"
+" utilizar enlaces de \"salto\" (de servicios de enlazado distribuidos) lo"
+" que es molesto."
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+"Aquí tiene algunos otros enlaces públicos de suscripciones para libreta "
+"de direcciones. \n"
+"Quizás quiera añadir uno o dos a su lista de "
+"suscripciones de SusiDNS. \n"
+"No tiene que añadirlos todos, ya que se sincronizan entre ellos "
+"periódicamente.  \n"
+"Los enlaces que usan una aplicación CGI-bin utilizan diferentes "
+"estrategias para minimizar \n"
+"el número de direcciones duplicadas entregadas, por lo que deberían ser "
+"más eficientes. \n"
+"Observe que suscribirse a un servicio hosts.txt es un acto de "
+"\"confianza\", ya que una \n"
+"suscripción maliciosa podría suministrarle direcciones incorrectas. Así "
+"que piense \n"
+"bien si quiere confiar en alguno de ellos. \n"
+"Los operadores de estos servicios pueden tener diferentes políticas para "
+"listar equipos. \n"
+"La presencia de esos servicios en esta lista no implica respaldo por "
+"nuestra parte."
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+"jrandom fue el programador principal de I2P y \n"
+"de Syndie durante varios años."
+" \n"
+"No sabemos si jrandom regresará o cuándo. \n"
+"Los dominios *.i2p.net se dejaron en un estado no funcional después \n"
+"de un corte de energía en la compañía de alojamiento ('hosting')."
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+"En esta página tiene el mensaje de "
+"despedida de jrandom \n"
+"e información adicional sobre la migración de *.i2p.net a este sitio web."
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr "El desarrollo de I2P continúa activo."
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+"Hay muchas causas posibles para un elevado uso de la CPU. Aquí tiene una "
+"lista para su comprobación:"
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+"Intente usar OpenJDK o Java de Sun/Oracle si está disponible en su "
+"sistema. Puede ver la versión instalada en su sistema ejecutando "
+"java -version en la terminal. El rendimiento tiende a sufrir"
+" con otras implementaciones de java."
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+"¿Usa Bittorrent sobre I2P? Intente reducir el número de torrents, los "
+"límites de ancho de banda, o pruebe a apagarlo completamente a ver si eso"
+" ayuda."
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+"¿Están los límites de ancho de banda demasiado altos? Es posible que pase"
+" demasiado tráfico a través de su ruter I2P y esté saturado. Intente "
+"reducir la configuración delporcentaje de ancho de banda "
+"compartidor en la web de configuración."
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+"Asegúrese de usar la última versión de I2P para beneficiarse de las "
+"mejoras de rendimiento y la solución de errores."
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+"¿Tiene suficiente memoria reservada para el uso de I2P? Mire la gráfica "
+"de memoria en la página de "
+"gráficos para ver si el uso de memoria está \\\"pegged\\\"—la "
+"máquina virtual de java pierde demasiado tiempo en la recogida de basura."
+" Aumente la configuración de wrapper.java.maxmemory en "
+"wrapper.config."
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+"¿Es simplemente el uso de CPU mayor del que le gustaría, o lleva mucho "
+"tiempo fijo al 100%?\n"
+"Si está fijo, esto podría ser un fallo, 'bug'. Busque pistas en los "
+"registros, 'logs'."
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+"Puede que esté usando la librería BigInteger en vez de la versión nativa,"
+" especialmente si lo ejecuta en un sistema o hardware nuevo o inusual "
+"(OpenSolaris, mipsel, etc). Visite la web de "
+"jbigi que incluye instrucciones para el diagnóstico, compilado y "
+"métodos de testeo."
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+"Si su librería jbigi nativa funciona bien, el uso excesivo de la CPU "
+"podría ser debido al tráfico enrutado de los túneles usados. Este usa CPU"
+" porque en cada salto se debe decodificar una capa del cifrado. Puede "
+"limitar el tráfico usado de dos formas - reduciendo el ancho de banda "
+"compartido en confignet.jsp, o "
+"configurando router.maxParticipatingTunnels=nnn en configadvanced.jsp."
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+"Umm. Es un poco difícil, pues I2P es una red anónima. I2P está diseñada "
+"para evitar la censura, creando un medio para todos de comunicarse "
+"libremente. La mejor forma de mantener tu PC libre de tráfico (cifrado) "
+"que no desea es no usar I2P. La libertad de expresión tiene algunos "
+"costes. Pero respondamos su pregunta en tres partes:"
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+"Distribución - Todo el tráfico sobre I2P está cifrado en múltiples"
+" capas. Usted no conoce el contenido de ningún mensaje, ni su origen o\n"
+"destino. Todo el tráfico que enrute es interno a la red I2P si usted no "
+"es un \n"
+"nodo de salida (`outproxy`). Su única alternativa "
+"es \n"
+"rehusar a enrutar cualquier tráfico, configurando su ancho de "
+"banda \n"
+"compartido, o su máximo de túneles participantes a 0 (vea arriba). "
+"Estaría \n"
+"bien si no lo hace, debería ayudar a la red enrutando el tráfico de "
+"otros. Más \n"
+"de 95% usuarios enrutan tráfico para otros."
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+"Almacenamiento - I2P no hace almacenamiento distribuido de "
+"contenidos. Debe estar pensando en Freenet. Ningún contenido de "
+"nadie está siendo almacenado en su computador por I2P."
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+"Acceso - Si hay eepsites que no le gustan, no navegue por ellas. O"
+" utilice un proxy de bloqueo como Privoxy o algún tipo de \\\"niñera de "
+"red\\\"."
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+"No, esto es normal.Todos los ruters se ajustan dinámicamente a las "
+"condiciones y necesidades de la red."
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+"Quizás necesite resembrar su ruter I2P. Con versiones recientes de I2P "
+"puede navegar a http://localhost:7657/configreseed"
+" y pulsar el botón Guardar cambios y resembrar ahora. Si este "
+"método no funciona—o está usando una versión muy vieja—podría"
+" necesitar resembrar manualmente."
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+"El enlace de resiembra cambió hace unos años. Si es su primera "
+"instalación y ha instalado una versión vieja (0.6.1.30 o anterior), o no "
+"ha ejecutado I2P durante mucho tiempo, debe cambiar el enlace y entonces "
+"pulsar \\\"Resembrar\\\" en la consola para encontrar otros rutes. "
+"Después de tener el ruter funcionando, en configadvanced.jsp,"
+" añada la línea i2p.reseedURL=http://netdb.i2p2.de/ o "
+"i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (cualquiera debería "
+"funcionar), y entonces pulse en \\\"Aplicar\\\", después pulse el enlace "
+"\\\"Resembrar\\\" a la izquierda."
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+"Esto funciona si usa la versión 0.6.1.27 o posterior.Si usa la versión "
+"0.6.1.31 o posterior probablemente no necesite esto. Si usa la versión "
+"0.6.1.26 o anterior, o siga las instrucciones de resiembra manual abajo o"
+" instale la última versión. Un "
+"posible método alternativo - añada "
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/ "
+"a wrapper.config, apague el ruter completamente, y arránquelo de nuevo, "
+"entonces pulse \\\"Resembrar\\\". Háganos saber si esto funciona."
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+"Realmente debería actualizar a la "
+"última versión..."
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+"Si su ruter tiene 10 o más pares activos todo está bien. Los cambios en "
+"las versiones 0.6.1.31 y 0.6.1.32 han mejorado la eficiencia del ruter y "
+"han reducido el número de pares activos. El ruter debería tener "
+"todo el tiempo conexiones con unos pocos pares. La mejor forma de estar "
+"\\\"mejor-conectado\\\" a la red es compartiendo mas ancho de "
+"banda"
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+"¿Es mi ruter un \\\"nodo de salida\\\" al Internet normal? No quiero "
+"serlo."
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+"No. Al contrario que Tor, los"
+" \n"
+"\"nodos de salida\" o los \"proxys externos\", 'outproxies' no son una "
+"parte \n"
+"inherente de la red. Sólo voluntarios que hayan configurado y ejecutado \n"
+"aplicaciones separadas repetirán tráfico a la Internet regular. Hay muy, "
+"muy\n"
+"pocos de estos."
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+"Vea arriba. Hay muy pocos proxys al exterior HTTP \"outproxies\", no son"
+" \n"
+"una parte inherente de la red, y pueden no estar activos. Además, los \n"
+"antiguos outproxies squid.i2p, true.i2p, y krabs.i2p se han desvanecido. "
+"El \n"
+"único proxy al exterior en este momento es false.i2p. Para usarlo, edite "
+"sus \n"
+"configuraciones"
+" de i2ptunnel para eepProxy y establezca su lista de proxys al "
+"exterior \n"
+"a `false.i2p' (sólo). Luego pare y reinice el eepProxy. Si no funciona, "
+"el \n"
+"proxy al exterior no está activo. No es un fallo de I2P. Si su razón "
+"principal \n"
+"para usar una red anónima es acceder anónimamente a sitios en la \n"
+"Internet regular, probablemente debería probar con Tor."
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+"Dentro de I2P no hay necesidad de HTTPS, todo el tráfico está cifrado de "
+"punta a punta. FTP no está soportado por razones técnicas."
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+"No hay  \\\"outproxies\\\"  FTP hacia el Internet—pude que no sea "
+"posible configurar uno. Cualquier otro tipo de outproxy debería funcionar"
+" si está configurado con un túnel estándar. Si desea configurar algún "
+"tipo de outproxy, investigue atentamente los posibles riesgos. La "
+"comunidad I2P quizás sería capaz de ayudar con los aspectos técnicos, "
+"siéntase libre en preguntar."
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+"Como se ha explicado varias veces ya, cualquier outproxy existente no es "
+"parte principal de la red. Son servicios controlados por algunos usuarios"
+" y pueden estar funcionando, o no."
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
            \n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+"Actualización: Gracias al trabajo de h2ik, hay un outproxy https "
+"disponible para I2P. A partir de I2P 0.8.4 el túnel "
+"viene listo por defecto.
             En caso de que el outproxy https no esté "
+"disponible en su versión de I2P, puede añadirlo fácilmente haciendo esto:"
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+"Abra el administrador de "
+"túneles I2P. Vaya al final de la página."
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+"Seleccione CONECTAR de la lista desplegable de Nuevo túnel "
+"cliente, pulse Crear"
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+"En la nueva página, nombre y describa su nuevo túnel https "
+"como guste. El Punto de acceso es su puerto local para el nuevo "
+"proxy https, puerto recomendado 4445. El outproxy debe ser "
+"la dirección .i2p del outproxy que soporta https. Lea el foro de h2ik para ver"
+" la dirección. Asegúrese de que Shared Client, Delay "
+"Connect y AutoStart están activados.Las demás opciones debería"
+" dejarlas como están. Pulse guardar. En el administrador de túneles, "
+"pulse el botón Iniciar junto al nuevo túnel."
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+"En Firefox pulse "
+"Herramientas>Opciones>Avanzado>Red>Configuración."
+" Desactive Usar el proxy para todos los protocolos, ponga en "
+"proxy SSL: localhost:4445."
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "Listo."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+"\n"
+"Eso es un cuestión que solo usted puede responder porque la respuesta "
+"correcta depende del su comportamiento, los riesgos, y cuanto confíe en el operador "
+"del outproxy."
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+"Al igual que Tor, I2P no cifra mágicamente Internet. Es siempre "
+"vulnerable a la inspección del tráfico por parte del operador del "
+"outproxy. El FAQ"
+" de Tor lo explica muy bien."
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+"Además puede tener problemas por la confabulación entre el operador del "
+"outproxy y los operadores de otros servicios de I2P si utiliza los mismos"
+" túneles (\\\"shared clients\\\"). Hay una discusión adicional sobre esto"
+" en %(zzz)s."
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+"A menos que su proxy al exterior haya sido configurado para el servicio "
+"al \n"
+"que quieres conectarse, esto no puede hacerse. Hay sólo tres tipos de \n"
+"proxys al exterior, 'outproxies', ejecutándose en este instante: HTTP, \n"
+"HTTPS, y email. Observe que no hay un proxy al exterior SOCKS. Si se \n"
+"requiere este tipo de servicio, pruebe con Tor."
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+"Si consideramos cada eepsite que ha sido creada, sí, la mayoría de ellas "
+"están caídas. La gente y las eepsites van y vienen. Una buena forma de "
+"comenzar en I2P es ver la lista de las eepsites que están funcionando. %(eepstatus)s tiene una lista de las eepsites"
+" activas. "
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+"Pulse en el enlace a la página "
+"web en la parte de arriba de las instrucciones de la consola del "
+"ruter."
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+"¿Por qué son tan lentas las descargas, torrents y la navegación web en "
+"I2P? El cifrado y ruteo de la red I2P añade bastante carga y limita el "
+"ancho de banda. El anonimato no es gratis."
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+"Además, probablemente necesite aumentar los límites de ancho de banda. "
+"Dos configuraciones importantes son los límites de entrada y salida en la página de "
+"configuración. Con la configuración por defecto de 32KBps "
+"probablemente no conseguirá mas de 15KBps de transferencia en I2PSnark. "
+"Aumentando estos valores (pero manteniéndolos dentro de las limitaciones "
+"de su conexión) Aumentará potencialmente la velocidad de transferencia de"
+" I2PSnark y otras aplicaciones."
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+"Además, ¿tiene configurado suficiente ancho de banda compartido para "
+"permitir a los túneles participantes enrutar a través de su ruter? lo "
+"crea o no, permitir tráfico participante le mantiene bien integrado en la"
+" red y le ayuda a mejorar la velocidad de transferencia."
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+"I2P es un trabajo en curso. Muchas mejoras y arreglos están siendo "
+"implementadas, y generalmente usando la última versión mejorará el "
+"rendimiento. Si no la tiene, instale la "
+"última versión."
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+"Vea el FAQ de "
+"Bittorrent en I2P"
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+"\n"
+"Cuando instala I2P se crea un túnel hacia el servidor IRC de I2P, Irc2P, "
+"(vea la página de"
+" configuración de I2PTunnel), y se inicia automáticamente cuando se "
+"arranca el ruter I2P. Para conectarse a él configure su cliente IRC para "
+"conectarse a localhost 6668.  Los clientes de IRC como Xchat"
+" pueden crear una nueva conexión con el servidor "
+"localhost/6668 (recuerde pulsar "Bypassproxy "
+"server" si tiene el servidor proxy configurado)."
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface.  However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+"Por razones de seguridad la consola de administración del ruter por "
+"defecto solo escucha en localhost. Aunque, con algún apaño, puede hacerla"
+" accesible remotamente:"
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"with 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+"Abra ~/.i2p/clients.config y cambie
             "
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
             por  clientApp.0.args=7657 0.0.0.0 ./webapps/"
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+"Vaya a http://localhost:7657/configui"
+" y añada un nombre de usuario de consola y una contraseña si lo desea."
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+"Vaya a http://localhost:7657/index.jsp"
+" y pulse \\\"Graceful restart\\\", que reiniciará le máquina virtual y "
+"las aplicaciones clientes."
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+"Tras establecer eso, ahora debería ser capaz de alcanzar su consola "
+"remotamente. Vuelva a cargar el router en http://127.0.0.1:7657 y \n"
+"se le solicitará el nombre de usuario y la contraseña que especificó en "
+"el \n"
+"paso 2 de arriba si su navegador soporta el diálogo emergente de \n"
+"autentificación. Nota: el 0.0.0.0 de arriba especifica una \n"
+"interfaz, no una red o máscara de red. 0.0.0.0 significa \"ligarla"
+" con todas las interfaces\", por lo que puede ser alcanzada en "
+"127.0.0.1:7657 así como en cualquier IP LAN/WAN."
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+"Por defecto el dispositivo del ruter I2CP (puerto 7654) escucha en "
+"127.0.0.1. Para que escuche en 0.0.0.0, cambie la opción en configuración"
+" avanzada i2cp.tcp.bindAllInterfaces=true y reinicie."
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "¿Qué es una \\\"eepsite\\\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+"Una eepsite es una página web hospedada anónimamente - se puede acceder a"
+" ella configurando el proxy de su navegador web (normalmente a localhost "
+"puerto 4444), y poniendo la dirección de la web en su navegador."
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+"La configuración proxy para varios navegadores está en  una web aparte con capturas de "
+"pantalla. Una configuración mas avanzada con herramientas externas es "
+"posible, pero podría introducir fugas en su configuración."
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+"x es el número de pares a los cuales ha enviado o recibido mensajes "
+"satisfactoriamente en el último minuto, y es el número de pares vistos en"
+" la última hora."
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+"El proxy SOCKS está soportado desde la versión 0.7.1. Está soportado "
+"SOCKS 4/4a/5. No hay proxy de salida SOCKS, con lo cual es de uso "
+"limitado."
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+"Además, muchas aplicaciones tienen fugas de información sensible, "
+"información que podría identificarle en Internet. I2P sólo filtra los "
+"datos de conexión, pero si el programa que ejecuta envía esta "
+"información, I2P no tiene forma de proteger su anonimato. Por ejemplo, "
+"algunas aplicaciones de email envían la IP de la máquina donde se "
+"ejecutan al servidor de email. No hay forma de que I2P filtre esto, con "
+"lo cual usar I2P para 'sockificar' aplicaciones existente es posible, "
+"pero extremadamente peligroso."
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+"Si aún así desea mas información sobre el proxy socks, hay algunas "
+"sugerencias útiles en la web de socks"
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+"De acuerdo, aquí hay un resumen con los puertos por defecto ( por "
+"supuesto todo es configurable a través de varias opciones):"
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+"Puertos abiertos al internet Nota: las nuevas instalaciones a "
+"partir de 0.7.8 no usan el puerto 8887; elijen un puerto aleatorio entre "
+"9000 y 31000 cuando el programa se ejecuta por primera vez. El puerto "
+"seleccionado se muestra en la página de configuración "
+"del ruter"
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+"    "
+msgstr ""
+"Puerto aleatorio UDP de salida en la página de configuración "
+"hacia puertos UDP remotos, permitiendo respuestas."
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+"    "
+msgstr ""
+"Puertos altos aleatorios de salida TCP hacia puertos aleatorios TCP "
+"remotos"
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+"    "
+msgstr ""
+"(opcional pero recomendado) UDP de entrada hacia el puerto indicado en"
+" la página de "
+"configuración desde ubicaciones arbitrarias"
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
            \n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+"(opcional pero recomendado) TCP de entrada hacia el puerto indicado en"
+" la página de "
+"configuración desde ubicaciones arbitrarias.
             TCP de entrada"
+" puede estar deshabilitado en la página de configuración"
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
            \n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+"Puerto 123 de salida UDP, permitiendo respuestas 
              Este es "
+"necesario para la sincronización del reloj de I2P (via SNTP- consultando "
+"un host SNTP aleatorio en pool.ntp.org u otro servidor que especifique)"
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+"Puertos locales de I2P, escuchando por defecto solamente a "
+"conexiones locales, excepto cuando se indique:"
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"1900: UPnP SSDP UDP multicast listener.  No puede cambiarse. "
+"Escucha en todos los dispositivos. Puede estar desactivado en confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+"2827: Puente BOB, un API de alto nivel para clientes  "
+"Desactivado por defecto. Puede activarse/desactivarse en configclients.jsp. "
+"Puede cambiarse en el archivo de configuración bob.config."
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4444: Proxy HTTP Puede activarse o cambiarse en la página de "
+"I2ptunnel en la consola del ruter. También puede configurarse para "
+"escuchar en un dispositivo determinado o en todos."
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4445: Proxy HTTPS  Puede cambiarse o activarse en la página de "
+"I2P túnel en la consola del ruter. También puede ser configurado para "
+"escuchar en un dispositivo determinado o en todos."
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"6668: Proxy IRC Puede activarse o cambiarse en la página de "
+"I2ptunnel en la consola del ruter. También puede configurarse para "
+"escuchar en un dispositivo determinado o en todos."
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7652: UPnP HTTP TCP event listener. Escucha en la dirección de "
+"LAN. Puede cambiarse en la configuración avanzada "
+"i2np.upnp.HTTPPort=nnnn. Puede desactivarse en confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7653: UPnP SSDP UDPsearch response listener.  Escucha en todos "
+"los dispositivos. Puede cambiarse con la configuración avanzada "
+"i2np.upnp.SSDPPort=nnnn. Puede desactivarse en confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+"7654: Puerto cliente del protocolo I2P, usado por varias "
+"aplicaciones Puede cambiarse a un puerto diferente en configclients.jsp "
+"pero no se recomienda. Puede escuchar en un dispositivo diferente, en "
+"todos o desactivarse en configclients.jsp."
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+"7655: UDP para el puente SAM, un API para sockets de alto nivel "
+"para clientes.  Solo se abre cuando un cliente SAM V3 solicita una "
+"sesión UDP. Puede activarse/desactivarse en configclients.jsp. "
+"Puede cambiarse en el archivo clients.config en la línea "
+"sam.udp.port=nnnn."
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+"7656: Puente SAM, un API de alto nivel para clientes "
+"Desactivado por defecto para nuevas instalaciones desde la versión "
+"0.6.5. Puede activarse o desactivarse en configclients.jsp. "
+"Puede cambiarse en el archivo clients.config."
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+"7657: La consola del ruter. Puede desactivarse en el archivo "
+"clients.config. También puede ser configurado para escuchar en un "
+"dispositivo o en todos los dispositivos en ese mismo archivo."
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+"7658: Tu eepsite. Puede desactivarse en el archivo "
+"clients.config. Puede configurarse para escuchar en un dispositivo o en "
+"todos en el archivo jetty.xml."
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7659: Emails de salida hacia smtp.postman.i2p. Puede "
+"desactivarse o cambiarse en la página de i2ptunnel en la consola del "
+"ruter. También puede ser configurado para escuchar en un dispositivo o en"
+" todos."
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7660: Email de entrada desde pop.postman.i2p. Puede "
+"deshabilitarse o cambiarse en la página de i2ptunnel en la consola del "
+"ruter. También puede configurarse para escuchar en un dispositivo o en "
+"todos."
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"8998:mtn.i2p2.i2p (Monotone - desactivado por defecto) Puede "
+"deshabilitarse o cambiarse en la página de i2ptunnel en la consola del "
+"ruter. También puede ser configurado para escuchar en un dispositivo o en"
+" todos."
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"31000: Conexión local al puerto de control del wrapper. Salida "
+"sólo  hacia 32000, no escucha en este puerto. Empieza en 31000 y se "
+"incrementa hasta 31999 buscando un puerto libre. Para cambiarlo vea la documentación del wrapper. Para mas información vea más abajo."
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"32000: Canal de conexión local para el servicio wrapper.   Para"
+" cambiarlo vea la decumentación del wrapper.. Para mas información "
+"vea más abajo."
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally.  You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+"Los puertos locales de I2P y los puertos de I2PTunnel no necesitan ser "
+"accesibles desde máquinas remotas, pero *deberían* ser accesibles "
+"localmente. Además puede crear también puertos adicionales para  "
+"instancias I2PTunnel vía http://localhost:7657/i2ptunnel/ (y a su vez, "
+"necesitará permitir en su cortafuegos el acceso local, pero no remoto, a "
+"no ser que lo desee así)."
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance.  You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+"Resumiendo, nada necesita ser accesible por pares remotos que no hayan "
+"sido solicitados, pero, si puede configurar su NAT/cortafuegos para "
+"permitir conexiones de entrada UDP y TCP hacia los puertos de escucha de salida, "
+"tendrá mejor rendimiento. También necesitará ser capaz de enviar paquetes"
+" UDP de salida a pares remotos arbitrarios ( bloqueando IPs "
+"aleatoriamente con cosas como PeerGuardian solo le perjudica a usted - no"
+" lo haga)."
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr "¿Porqué está escuchando I2P en el puerto 32000?"
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+"El servicio wrapper java Tunaki que usamos abre este puerto "
+"—escuchando en localhost—para poder comunicarse con "
+"aplicaciones dentro de la JVM, máquina virtual de java. Cuando la JVM "
+"arranca se la da una clave para poder conectarse al wrapper. Después de "
+"que la  JVM establezca la conexión con el wrapper, el wrapper rechaza "
+"cualquier conexión adicional."
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the  \n"
+"wrapper documentation."
+msgstr ""
+"Puede encontrar más información en la documentación del wrapper."
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+"Un ruter I2P sólo necesita sembrar una vez para unirse a la red por "
+"primera vez. Resembrar no es mas que enviar solicitudes normales HTTP GET"
+" para alcanzar una lista y descargar múltiples archivos \"routerInfo\" "
+"desde una URL de resembrado predefinida."
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+"Un síntoma típico de resembrado fallido es el indicador \"Conocidos\" (en"
+" la parte izquierda del la consola del ruter) mostrando un valor muy "
+"pequeño (normalmente menos de 5) que no aumenta.. Esto puede ocurrir, "
+"además de por otras razones, si su cortafuegos limita el tráfico de "
+"salida, y ha bloqueado las solicitudes de resembrado."
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr "Para resembrar el ruter I2P manualmente haga lo siguiente:"
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr "Parar el ruter I2P"
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+"Abra http://netdb.i2p2.de/ usando "
+"un explorador web."
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr ""
+"Guarde una docena de archivos \"routerInfo\" en el directorio \"netDb\" "
+"de I2P"
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr "Encienda su ruter I2P"
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+"Cuando intenta arrancar el ruter usando \"i2prouter start\", puede ver "
+"una salida del tipo:"
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+"\n"
+"En el intento de hacer que I2P funcione en el mayor número de sistemas "
+"posibles, hasta I2P 0.8.9 usábamos un wrapper java compilado "
+"por FreeBSD 6.x. Si recibe este error lo mas probable es que le falten "
+"las librerías necesarias. Esas librerías pueden instalarse siguiendo los "
+"pasos siguientes:"
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+"Cambie al usuario root con su o inicie sesión como "
+"root."
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+"Si no puede instalar estas librerías (o no lo desea), otra posibilidad "
+"sería compilar el wrapper para su "
+"sistema, arrancando con el script runplain.sh de I2P, o "
+"puede sobreescribir el wrapper por uno del archivo de las fuentes."
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+"A partir de la versión 0.8.9 de I2P, el wrapper ha sido actualizado a "
+"v3.5.12 y compilado en sistemas corriendo FreeBSD 7.2."
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+"En el archivo wrapper.log veo un error que indica "
+"\"Protocol family unavailable\" cuando arranco la consola "
+"del ruter."
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+"A menudo este error ocurre con cualquier aplicación java que active la "
+"red en sistemas configurados para usar IPV6 por defecto. Hay varias "
+"formas de arreglarlo:"
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+"En sistemas basados en Linux puede ejecutar echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr "Busque por las siguientes líneas en wrapper.config."
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+"Si las líneas ya están ahí, descomentelas eliminando los \"#\". Si las "
+"líneas no están ahí añádalas sin los \"#\"."
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+"Otra opción sería borrar ::1 del archivo "
+"~/.i2p/clients.config"
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+"CUIDADO: Para que los cambios en "
+"wrapper.config tengan efecto debe apagar completamente el "
+"ruter y el wrapper. ¡Pulsando Reiniciar en la consola del ruter "
+"NO leerá de nuevo este archivo! Tiene que pulsar  apagar, "
+"esperar 11 minutos y entonces arrancar I2P."
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+"¡Genial! Contáctenos en el IRC irc.freenode.net #i2p o escríbanos en el "
+"foro y lo publicaremos aquí (esperemos "
+"que con la respuesta)."
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "Leyes alemanas"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr "Red anónima I2P"
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+"Capa anónima de comunicación distribuida par-a-par construida con "
+"herramientas de código libre y diseñada para usar cualquier servicio de "
+"internet tradicional como email, IRC, foros o páginas webs."
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr "¿Qué hace I2P por ti?"
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+"La red I2p proporciona una gran privacidad para las comunicaciones sobre "
+"Internet. Muchas actividades que podrían poner en riesgo su privacidad en"
+" Internet pueden hacerse anónimamente dentro de I2P."
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr "Descarga I2P %(version)s"
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "¿Qué es I2P?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+"I2P es una red de capa anónima - una red dentro de una red. Está pensada"
+" \n"
+"para proteger la comunicación del seguimiento de las redes de vigilancia "
+"y la \n"
+"monitorización por terceras partes como los ISPs (proveedores de \n"
+"Internet).\n"
+"\n"
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+"I2P es usado por muchas personas que se preocupan por su privacidad: \n"
+"activistas, poblaciones oprimidas, periodistas, denunciantes, así como "
+"por \n"
+"el ciudadano medio.\n"
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+"Ninguna red puede ser \"perfectamente anónima\". El objetivo continuado "
+"de \n"
+"I2P es hacer los ataques más y más difíciles de montar. Su anónimato se \n"
+"volverá más fuerte al crecer el tamaño de la red, y con la revisión "
+"académica que está en marcha.\n"
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+"I2P está disponible para escritorios, sistemas embebidos (como el \n"
+"Rapsberry Pi) y teléfonos Android. ¡Ayude a extender el mensaje!\n"
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr "Leer más…"
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr "¿Qué puede hacer con I2P?"
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+"Email Interfaz de correo web "
+"integrado, complemento para correos sin servidor, 'serverless'."
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+"Navegación web Webs anónimas, "
+"gateways o puertas de salida, desde y hacia el Internet público."
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+"Blogs y foros Blogs y "
+"pluguins Syndie."
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+"Alojamiento web Servidor "
+"web anónimo integrado. "
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+"Chat en tiempo real "
+"Mensajería instantánea y clientes IRC."
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+"Intercambio de archivos "
+"Clientes ED2K y Gnutella, cliente de BitTorrent integrado."
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+"Almacenamiento de "
+"archivos descentralizado Pluguin para el sistema de archivos "
+"distribuido Tahoe-LAFS."
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr "Más aplicaciones soportadas…"
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr "Noticias & Actualizaciones"
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr "Enlaces recomendados y más recursos"
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+"Vea también la web con a href=\"%(media)s\">enlaces a presentaciones, "
+"vídeos, y manuales sobre I2P."
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr "I2P en la web"
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr "Amigos de I2P"
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr "Más proyectos y documentación"
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "Prensa"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr "Anuncios, noticias y otros"
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr "Cosas muy antiguas"
+
diff --git a/i2p2www/translations/es/LC_MESSAGES/research.po b/i2p2www/translations/es/LC_MESSAGES/research.po
new file mode 100644
index 00000000..1a4a574c
--- /dev/null
+++ b/i2p2www/translations/es/LC_MESSAGES/research.po
@@ -0,0 +1,163 @@
+# Spanish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Adolfo Jayme Barrientos , 2013
+# Daniel Mustieles , 2013
+# m1xxy , 2011
+# olivertrash , 2013
+# strel, 2013
+# trolly, 2013
+# trolly , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-10-05 16:18+0000\n"
+"Last-Translator: trolly \n"
+"Language-Team: Spanish "
+"(http://www.transifex.com/projects/p/I2P/language/es/)\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/research/index.html:2
+msgid "Academic Research"
+msgstr "Investigación académica"
+
+#: i2p2www/pages/site/research/index.html:4
+msgid ""
+"Academic research and analysis of I2P is an important part of ensuring "
+"that the software and network performs as expected and is safe for users "
+"in hostile environments."
+msgstr ""
+"El análisis y la investigación académica de I2P es una parte importante "
+"para asegurar que la aplicación y la red funcionan como deben y es segura"
+" para los usuarios en ambientes hostiles."
+
+#: i2p2www/pages/site/research/index.html:8
+#, python-format
+msgid ""
+"\n"
+"There is a large research community investigating a wide range of aspects"
+" of\n"
+"anonymity. For a current and comprehensive list of relevant papers, see "
+"the\n"
+"Free Haven Anonymity Bibliography.\n"
+"I2P benefits from much of the research into Tor and onion routing, but "
+"there is\n"
+"little dedicated research interest into the theory behind I2P, and the "
+"choices\n"
+"and tradeoffs that the network makes. This presents a unique opportunity "
+"for\n"
+"original research.\n"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:18
+#, python-format
+msgid ""
+"A list of known published papers about I2P is available here."
+msgstr ""
+"Una lista de documentos publicados sobre I2P está disponible aquí."
+
+#: i2p2www/pages/site/research/index.html:22
+msgid "Testing Attacks on I2P"
+msgstr "Probando ataques sobre I2P"
+
+#: i2p2www/pages/site/research/index.html:24
+msgid ""
+"I2P can be run as a separate test network by controlling the locations "
+"that a new router reseeds from so that it only finds other test routers."
+msgstr ""
+"I2P puede ejecutarse como una red de pruebas separada controlando las "
+"localizaciones que el nuevo ruter resiembra y así hacer que sólo "
+"encuentre los otros ruters de pruebas."
+
+#: i2p2www/pages/site/research/index.html:28
+msgid ""
+"The standard mode of operation is to have one JVM per router instance; "
+"hence running multiple copies of I2P on a single machine is inadvisable, "
+"both due to the potential resource drain and the certain port conflicts. "
+"To better facilitate setting up small test networks, I2P has a "
+"multirouter mode which enables multiple distinct routers to be run in the"
+" same JVM."
+msgstr ""
+"El modo normal de funcionamiento es tener una JVM por cada instancia de "
+"ruter; Por lo tanto no se recomienda ejecutar varias copias de I2P en la "
+"misma máquina, a causa del gasto de recursos y a causa de los conflictos "
+"que pueden tener entre ellas. Para facilitar la configuración de pequeñas"
+" redes de pruebas, I2P tiene un modo multiruter que permite ejecutar "
+"varios ruters en la misma JVM."
+
+#: i2p2www/pages/site/research/index.html:32
+msgid ""
+"MultiRouter can be started from the i2p base directory by running the "
+"below command."
+msgstr ""
+"EL modo MultiRouter puede arrancarse desde el directorio base de i2p con "
+"el siguiente comando."
+
+#: i2p2www/pages/site/research/index.html:37
+msgid ""
+"Additionally, I2P can be started in a virtual network mode. This mode "
+"disables all transports, allowing the router to be tested in isolation "
+"without network traffic. To enable this mode, add "
+"i2p.vmCommSystem=true to the router.config before starting."
+msgstr ""
+"Además, I2P pude arrancarse en el modo de red virtual. Este modo "
+"desactiva todos los transportes, permitiendo al ruter ser probado en "
+"solitario sin tráfico de red. Para activar este modo, añada "
+"i2p.vmCommSystem=true al archivo router.config antes de "
+"arrancar."
+
+#: i2p2www/pages/site/research/index.html:41
+msgid "Testing the Live I2P Network"
+msgstr "Probando la red I2P en vivo."
+
+#: i2p2www/pages/site/research/index.html:43
+#, python-format
+msgid ""
+"If you are planning on conducting research on the live I2P network, "
+"please contact us before you commence your "
+"testing. While we do not discourage researchers from responsibly testing "
+"their ideas on the live network, if an attack becomes apparent and we "
+"don't have any line of communication then we will end up taking "
+"countermeasures which could interfere with the test."
+msgstr ""
+"Si está planeando hacer algún estudio sobre la red de I2P en vivo,  por "
+"favor contáctenos antes de comenzar las "
+"pruebas.  Aunque no desalentamos a los desarrolladores a probar sus ideas"
+" responsablemente en la red, si algún ataque se hace aparente y no "
+"tenemos una línea de comunicación terminaremos tomando medidas que "
+"podrían interferir con las pruebas."
+
+#: i2p2www/pages/site/research/questions.html:2
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:4
+msgid "Network database"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:6
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:8
+msgid "Tunnels and Destinations"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:10
+msgid "Unidirectional tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:16
+msgid "Multihoming"
+msgstr ""
+
diff --git a/i2p2www/translations/fr/LC_MESSAGES/about.po b/i2p2www/translations/fr/LC_MESSAGES/about.po
new file mode 100644
index 00000000..861373db
--- /dev/null
+++ b/i2p2www/translations/fr/LC_MESSAGES/about.po
@@ -0,0 +1,2980 @@
+# French translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Boxoa590, 2013
+# magma , 2011
+# syl_, 2013
+# Towatowa441, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-11-10 10:28+0000\n"
+"Last-Translator: Towatowa441\n"
+"Language-Team: French "
+"(http://www.transifex.com/projects/p/I2P/language/fr/)\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/about/browser-config.html:2
+msgid "Web Browser Configuration"
+msgstr "Configuration du navigateur Web"
+
+#: 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 ""
+"Votre navigateur Web devra être configuré pour pouvoir naviguer sur les "
+"eepsites et\n"
+"utiliser les outproxies disponibles dans I2P. Voici les procédures pour "
+"certains des\n"
+"navigateurs les plus populaires."
+
+#: i2p2www/pages/site/about/browser-config.html:11
+msgid "How to configure your browser"
+msgstr "Comment configurer votre navigateur"
+
+#: i2p2www/pages/site/about/browser-config.html:17
+#: i2p2www/pages/site/about/browser-config.html:73
+msgid "Outproxy Terms Of Service"
+msgstr "Outproxy Conditions de service"
+
+#: i2p2www/pages/site/about/browser-config.html:22
+msgid "Internet Explorer 8 or Chrome"
+msgstr "Internet Explorer 8 ou 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 ""
+"Dans le menu Outils, sélectionnez la ligne \"Options Internet\" pour "
+"ouvrir les paramètres. Dans la\n"
+"fenêtre de paramètres choisissez l'onglet \"Connexions\" et cliquez sur "
+"\"Paramètres réseau\" pour la\n"
+"configuration du port proxy."
+
+#: i2p2www/pages/site/about/browser-config.html:28
+msgid "IE Internet Options"
+msgstr "IE Internet options"
+
+#: 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 ""
+"Maintenant, cochez la case \"Utiliser un serveur proxy pour votre réseau "
+"local\" et \"Ne pas\n"
+"utiliser de serveur proxy pour les adresses locales\". Cliquez sur le "
+"bouton \"Avancé\" pour ouvrir la\n"
+"fenêtre afin d'ouvrir les ports. Entrez les valeurs comme sur la photo, "
+"IP 127.0.0.1\n"
+"et le port 4444 pour le protocole HTTP, le port 4445 pour le protocole "
+"HTTPS. Cliquez sur OK, vous enregistrez les\n"
+"réglages et votre navigateur est configuré pour utiliser le proxy I2P."
+
+#: i2p2www/pages/site/about/browser-config.html:36
+msgid "IE Proxy Settings"
+msgstr "Paramètres proxy 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 ""
+"Dans le menu Outils, sélectionnez Options pour faire apparaître le "
+"panneau de configuration de Firefox.\n"
+"Cliquez sur l'icône intitulée Avancé, puis cliquez sur l'onglet "
+"réseau.\n"
+"Dans la section Connexions, cliquez sur le bouton Paramètres. "
+"Vous allez\n"
+"voir une fenêtre comme celle-ci :"
+
+#: i2p2www/pages/site/about/browser-config.html:46
+msgid "Firefox Network Options"
+msgstr "Firefox options réseau"
+
+#: 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 ""
+"Dans la fenêtre paramètres de connexion, cliquez sur le cercle à"
+" côté de configuration\n"
+"manuelle du proxy, puis entrez dans le champ Proxy HTTP 127.0.0.1, "
+"port 4444.\n"
+"Entrez dans le champ Proxy SSL : 127.0.0.1, port 4445.\n"
+"Dans la boîte \"Pas de proxy pour\" entrez \"localhost, 127.0.0.1\"."
+
+#: i2p2www/pages/site/about/browser-config.html:53
+msgid "Firefox Proxy Settings"
+msgstr "Firefox paramètres proxy"
+
+#: 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 ""
+"Dans le menu Paramètres, sélectionner Configurer "
+"Konqueror. Dans le\n"
+"groupe de navigation Web sur le côté gauche, sélectionnez Services Proxy."
+" \n"
+"Dans cette nouvelle fenêtre, sélectionnez l'option \"Spécifier "
+"manuellement les paramètres de proxy\" puis\n"
+"cliquez sur la boîte Paramètres."
+
+#: i2p2www/pages/site/about/browser-config.html:63
+msgid "Konqueror Proxy Options"
+msgstr "Konqueror options proxy "
+
+#: 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 ""
+"Dans la zone HTTP entrez 127.0.0.1 et le port 4444. Dans la boîte HTTPS "
+"entrez 127.0.0.1 et le port 4445.\n"
+"Dans la section Exceptions cliquez sur le bouton Nouveau. Entrez"
+"\n"
+"localhost puis cliquez sur OK. Cliquez sur le bouton Nouveau une"
+" fois de plus puis entrez\n"
+"127.0.0.1 et OK. Cliquez sur OK à nouveau pour fermer la fenêtre de "
+"configuration."
+
+#: i2p2www/pages/site/about/browser-config.html:70
+msgid "Konqueror Proxy Ports"
+msgstr "Konqueror ports proxy"
+
+#: 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 ""
+"Rappelez-vous : I2P n'a pas été conçu pour créer des proxy vers "
+"l'Internet externe.\n"
+"Au lieu de cela, il est destiné à être utilisé comme un réseau interne."
+
+#: 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 ""
+"Le projet I2P en lui-même ne fait pas fonctionner de proxys vers "
+"l'Internet. Tous tels services\n"
+"proxys sont gérés par des bénévoles privés et pourraient être fermées ou\n"
+"être inaccessibles à tout moment."
+
+#: 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 ""
+"Par défaut, I2P vient avec deux outproxies configurés : "
+"%(http)s\n"
+"(un proxy HTTP-seulement) et %(https)s (un proxy HTTPS\n"
+"routé à travers Tor."
+
+#: 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 ""
+"Ces deux outproxies sont configurés avec des limites de connexion. Cela "
+"signifie\n"
+"que seul un montant d'accès est autorisé par client. Une fois que la "
+"limite est\n"
+"atteinte, le client est bloqué pour une période de 1min/1h/1 jour. Soyez\n"
+"respectueux et ne surchargez pas ces services avec trop de demandes !."
+
+#: 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 ""
+"Le filtrage est actif sur ces outproxies (par exemple, mibbit et l'accès\n"
+"au tracker detorrent est bloqué). Les Eepsites\n"
+"qui sont accessibles via des adresses en .i2p ne sont pas autorisées via "
+"les outproxies.\n"
+"Par commodité, false.i2p bloque les serveurs de publicités."
+
+#: i2p2www/pages/site/about/browser-config.html:100
+msgid ""
+"Tor is good application to use"
+" as an\n"
+"outproxy to the Internet."
+msgstr ""
+"Tor est une bonne application "
+"à utiliser\n"
+"en tant que outproxy vers l'Internet."
+
+#: i2p2www/pages/site/about/glossary.html:2
+msgid "Glossary"
+msgstr "Glossaire"
+
+#: i2p2www/pages/site/about/glossary.html:4
+msgid ""
+"This page lists often-used terminology when discussing I2P and "
+"cryptography."
+msgstr ""
+"Cette page liste la terminologie souvent utilisée lors des discussions de"
+" I2P et de cryptographie."
+
+#: i2p2www/pages/site/about/hall-of-fame.html:2
+msgid "Hall Of Fame"
+msgstr "Hall de gloire"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:5
+msgid "I2P's Hall of Fame"
+msgstr "Hall de Gloire de I2P"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:6
+#, python-format
+msgid "Current balance: as of %(date)s"
+msgstr "Balance actuelle : en date de %(date)s"
+
+#: 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 "Fond général"
+
+#: 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 "%(euroval)s € and %(btcval)s BTC"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:11
+msgid "Datastorage bounty"
+msgstr "Prime Datastorage"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:13
+msgid "Native IPv6 I2P"
+msgstr "I2P IPv6 natif"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:15
+msgid "I2PHex bounty"
+msgstr "Prime 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 dans les miroirs debian"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:19
+msgid "Bitcoin client for I2P"
+msgstr "Client Bitcoin pour I2P"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:21
+msgid "Unit Tests for I2P router"
+msgstr "Tests d'unité pour routeur I2P"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:23
+msgid "Bounty Robert"
+msgstr "Prime Robert"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:24
+msgid "Bounty Syndie"
+msgstr "Prime Syndie"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:25
+msgid "Bounty I2P for CCR Microtic Board"
+msgstr "Prime I2P pour carte CCR Microtic"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:28
+msgid "Current monthly running costs:"
+msgstr "t"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:39
+msgid "Big thanks go to the following people who have donated to I2P!"
+msgstr "Un grand merci aux personnes suivantes qui ont donné à I2P !"
+
+#: 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 ""
+"Si vous avez fait un don, s'il vous plaît envoyez un courriel à echelon\n"
+"avec votre nom ou pseudo (et éventuellement page web personnelle) afin "
+"que nous puissions vous énumérer ici."
+
+#: i2p2www/pages/site/about/hall-of-fame.html:45
+msgid "Current monthly subscriptions:"
+msgstr "Abonnements mensuels actuels :"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:51
+msgid "2013 donations and costs:"
+msgstr "2013 dons et coûts :"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:170
+msgid "2012 donations and costs:"
+msgstr "2012 dons et coûts :"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:298
+msgid "2011 donations and costs:"
+msgstr "2011 dons et coûts :"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:399
+msgid "Previous to 2011 donations:"
+msgstr "Donations précédentes à 2011 :"
+
+#: i2p2www/pages/site/about/intro.html:2
+msgid "Intro"
+msgstr "Intro"
+
+#: i2p2www/pages/site/about/intro.html:4
+msgid "The Invisible Internet Project"
+msgstr "The Invisible Internet Project (le projet internet invisible)"
+
+#: i2p2www/pages/site/about/intro.html:5
+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 \n"
+"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 ""
+"I2P est un réseau anonyme, qui fournit une simple couche logicielle que "
+"les applications peuvent\n"
+"utiliser pour communiquer entre elles de manière anonyme et sécurisée.  "
+"Le réseau lui-même est\n"
+"strictement basé paquets (à la manière de IP), mais il "
+"y a \n"
+"une bibliotèque disponible pour permettre des communications en streaming"
+" par dessus de cela (à la\n"
+"manière de TCP)."
+"\n"
+"Toute la communication est chiffrée de bout en bout (au total il y a "
+"quatre couches de\n"
+"chiffrage utilisées en envoyant un paquet) et même les points de fin "
+"(\"destinations\")\n"
+"sont des identifiants cryptographiques (essentiellement une paire de clés "
+"publiques)."
+
+#: i2p2www/pages/site/about/intro.html:17
+msgid "How does it work?"
+msgstr "Comment ça marche ?"
+
+#: i2p2www/pages/site/about/intro.html:19
+#, 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 ""
+"Pour anonymiser les messages envoyés, chaque application cliente fait "
+"construire à son \"routeur\" I2P\n"
+"quelques \"tunnels\" entrants et "
+"sortants - une\n"
+"séquence de pairs qui passent des messages dans un sens (vers et à partir"
+" du client,\n"
+"respectivement). À son tour, quand un client veut envoyer un message à un"
+" autre client,\n"
+"le client transmet ce message sur l'un des tunnels sortants ciblant l'un "
+"des\n"
+"tunnels entrants d'autres clients, pour finalement atteindre la "
+"destination. Chaque\n"
+"participant au réseau choisit la longueur de ses tunnels, et, ce faisant,"
+"\n"
+"fait un compromis entre anonymat, latence, et débit, en fonction de leurs"
+"\n"
+"besoins propres. Le résultat est que le nombre de pairs relayant chaque "
+"message\n"
+"d'extrémité en extrémité soit le strict minimum nécessaire pour répondre "
+"au modèle de menace\n"
+"à la fois de l'expéditeur et du récepteur."
+
+#: i2p2www/pages/site/about/intro.html:33
+#, 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 ""
+"La première fois qu'un client veut contacter un autre client, ils font "
+"une requête\n"
+"envers la \"base de données\" complètement "
+"distribuée - \n"
+"c'est une \n"
+"table de hachage distribuée (DHT) à la structure personnalisée basée "
+"depuis l'\n"
+"algorithme "
+"Kademlia. Cela est fait\n"
+"pour trouver plus efficacement les tunnels entrants de l'autre pair, mais"
+" les messages ultérieurs\n"
+"entre eux incluent habituellement cette donnée donc il n'est pas requis "
+"de faire d'autres\n"
+"consultation de la base de données réseau."
+
+#: i2p2www/pages/site/about/intro.html:44
+#, python-format
+msgid "More details about how I2P works are available."
+msgstr ""
+"Plus de détails sur la façon dont I2P fonctionne sont disponibles."
+
+#: i2p2www/pages/site/about/intro.html:48
+msgid "What can you do with it?"
+msgstr "Que pouvez-vous faire avec ?"
+
+#: i2p2www/pages/site/about/intro.html:50
+#, 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 ""
+"Dans le réseau I2P, les applications ne sont pas restreintes dans la "
+"façon dont elles peuvent\n"
+"communiquer - celles qui utilisent habituellement UDP peut faire usage de"
+" la fonctionnalité I2P\n"
+"de base, et celles qui utilisent généralement TCP peuvent utiliser le "
+"protocole bibliothèque streaming\n"
+"TCP-like. Nous avons une application pont TCP/I2P générique\n"
+"(\"I2PTunnel\") qui permet aux gens de "
+"transmettre des flux TCP\n"
+"dans le réseau I2P ainsi que de recevoir des flux depuis le réseau et\n"
+"de les transmettre vers une adresse TCP / IP spécifique."
+
+#: i2p2www/pages/site/about/intro.html:60
+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 ""
+"I2PTunnel est actuellement utilisé pour laisser les gens faire "
+"fonctionner leur propre\n"
+"site Web anonyme (\"Eepsite\") en faisant fonctionner  un serveur web "
+"normal et\n"
+"en dirigeant I2PTunnel vers lui, auquel les gens peuvent avoir accès "
+"anonymement à travers I2P avec un navigateur web normal en faisant "
+"fonctionner un proxy HTTP I2PTunnel (\"eepproxy\"). De plus, nous "
+"utilisons le même\n"
+"technique pour faire fonctionner un réseau IRC anonyme (où le serveur IRC"
+" est hébergé anonymement, et des clients IRC standard utilisent un "
+"I2PTunnel pour le contacter). Il y a d'autres efforts de développement "
+"d'applications qui ont aussi lieu, comme de construise une application "
+"optimisée de transfert de fichier par essaimage (à la BitTorrent), un système de "
+"stockage distribué (à la Freenet / MNet), et un système de blog (un LiveJournal pleinement "
+"distribué), mais celles-ci ne sont pas encore prête pour être utilisées."
+
+#: i2p2www/pages/site/about/intro.html:76
+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 ""
+"I2P n'est pas en soi un réseau \"outproxy\" - le client auquel vous "
+"envoyez un message \n"
+"est l'identifiant cryptographique, pas une certaine adresse IP, donc le "
+"message doit\n"
+"se doit d'être adressé à quelqu'un exécutant I2P. Cependant, il est "
+"possible pour ce client \n"
+"d'être un outproxy, vous permettant de se servir de sa connexion Internet"
+" anonymement.\n"
+"Pour démontrer ceci, le \"eepproxy\" va accepter des URLs non normales à "
+"I2P\n"
+"(par exemple \"http://www.i2p.net\") et les expédier à une destination "
+"spécifique\n"
+"qui exécute un proxy HTTP squid/a"
+" >, permettant\n"
+"la navigation anonyme simple sur le Web normal. De simple outproxies "
+"comme celui-là\n"
+"ne sont pas viables à long terme pour plusieurs raisons (incluant le coût"
+" d'en faire\n"
+"tourner un aussi bien que les problèmes d'anonymat et de sécurité qu'ils "
+"amènent), mais dans\n"
+"certaines circonstances cette technique peut se révéler appropriée."
+
+#: i2p2www/pages/site/about/intro.html:90
+#, 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 ""
+"L'équipe de développement I2P est un groupe "
+"ouvert, bienvenue à tous\n"
+"ceux qui sont intéressés à s'impliquer , et"
+" tout\n"
+"le code est open source. Le noyau I2P SDK et"
+"\n"
+"la mise en œuvre actuelle du routeur sont faites en Java (qui marche "
+"actuellement avec\n"
+"soleil et kaffe, support gcj prévu pour plus tard), et il y a une\n"
+"API basée sur socket simple pour accéder au "
+"réseau depuis\n"
+"d'autres langues (avec une bibliothèque en langage C, tandis que Python "
+"et Perl sont\n"
+"en  développement). Le réseau est activement développé et n'a pas encore "
+"atteint\n"
+"la version 1.0, mais l'actuelle  feuille de "
+"route décrit\n"
+"notre calendrier."
+
+#: i2p2www/pages/site/about/media.html:2 i2p2www/pages/site/about/media.html:4
+msgid "Presentations on I2P"
+msgstr "Présentations sur I2P"
+
+#: 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 ""
+"Ce qui suit sont des liens vers des présentations, des vidéos et des "
+"tutoriels sur I2P. Des liens vers des documents de recherche sur I2P sont"
+" disponibles ici."
+
+#: i2p2www/pages/site/about/media.html:8
+#, python-format
+msgid "To request an addition to this page, please send to %(email)s."
+msgstr "Pour demander un ajout à cette page, s'il vous plaît envoyez à %(email)s."
+
+#: i2p2www/pages/site/about/media.html:11
+msgid ""
+"\n"
+"Newest links are at the bottom of each section."
+msgstr ""
+"\n"
+"Les nouveaux liens sont au bas de chaque section."
+
+#: i2p2www/pages/site/about/media.html:16
+msgid "Presentations"
+msgstr "Présentations"
+
+#: 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 ""
+"IIP Présentation à Codecon\n"
+"audio MP3\n"
+"transcription\n"
+"Lance James (0x90), Février 2002."
+
+#: 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 ""
+"Présentation IIP à ToorCon⏎\n"
+"audio MP3⏎\n"
+"diapositives⏎\n"
+" Lance James (0x90), Septembre 2002."
+
+#: 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 ""
+"Être ou I2P (To Be or I2P)\n"
+"(Vidéo Youtube)\n"
+"Une introduction à la communication anonyme avec I2P.\n"
+"To Be or I2P(PDF présentation) ,\n"
+"Jens Kubieziel, 24C3 Berlin, le 28 Décembre 2007."
+
+#: 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 ""
+"Vidéo du discours I2P à Chemnitz Linux Tag ,\n"
+"Lars Schimmer,\n"
+"14 au 15 mars 2009"
+
+#: 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 ""
+"HOPE New York 17 Juillet 2010 - Bref aperçu de I2P par zzz, à la fin de "
+"l'exposé de Adrian Hong\n"
+"\"Des hackers pour les droits de l'homme\".\n"
+"audio MP3 "
+
+#: 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 ""
+"Into the I2P Darknet : Bienvenue au Cipherspace "
+"\n"
+"Adrian Crenshaw. Schmoocon Firetalk, Janvier 2011"
+
+#: 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 ""
+"Utiliser la technologie pour faire avancer la "
+"liberté\n"
+"(Vidéo Youtube)\n"
+"Eric Johnson. \n"
+"a href=\"http://agora.io/etienne\"> Agora I/O Unconference, le 27 "
+"Mars 2011. \n"
+"I2P couvert de 10:00 à 20:00 dans la vidéo."
+
+#: i2p2www/pages/site/about/media.html:69
+#, python-format
+msgid ""
+"The Bright side of darknets, FOSSCOMM Patras May "
+"2011"
+msgstr ""
+"Le côté lumineux des darknets (The Bright side of "
+"darknets), FOSSCOMM Patras mai 2011"
+
+#: 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 ""
+"Faiblesses communes du darknet (Common Darknet "
+"Weaknesses)\n"
+"(Vidéo Youtube)\n"
+"Adrian Crenshaw, AIDE, 11-15 "
+"Juillet 2011."
+
+#: 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 ""
+" I2P / Tor notes d'atelier\n"
+"Adrian Crenshaw. DEF CON 19, Las Vegas, 6 Août 2011."
+
+#: 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 ""
+" Cipherspaces / Darknets : un aperçu des stratégies "
+"d'attaque -\n"
+"DEF CON Live version (vidéo Youtube) ,\n"
+"Version \"Studio\" (vidéo Youtube) ,\n"
+"Diapositives (ppt)\n"
+"Adrian Crenshaw. DEF CON 19, Las Vegas, 7 Août 2011."
+
+#: i2p2www/pages/site/about/media.html:94
+msgid ""
+"Modern cipherspace ecosystems, 0x375 "
+"0x06 4/11/2011"
+msgstr ""
+"Ecosystèmes cipherspace modernes, 0x375"
+" 0x06 4/11/2011"
+
+#: i2p2www/pages/site/about/media.html:100
+msgid "Tutorials"
+msgstr "Tutoriels"
+
+#: 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 ""
+"Tutorial I2P sous Windows\n"
+"(Vidéo Youtube)\n"
+"Ce guide va vous montrer comment installer I2P sous Windows XP.\n"
+"Par Telecomix"
+
+#: 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 ""
+"Tutorial I2P Debian\n"
+"(Vidéo Youtube)\n"
+"Cela vous guidera à travers l'installation de I2P sur un système Debian "
+"Linux.\n"
+"Par Telecomix"
+
+#: 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 ""
+"Comment mettre en place un site anonyme dans I2P"
+"\n"
+"(Vidéo Youtube)\n"
+"Comment mettre en place un site web anonyme dans I2P.\n"
+"Par Telecomix"
+
+#: 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 ""
+"Tutorial I2P Mac OS X\n"
+"(Vidéo Youtube)\n"
+"Un tutorial sur la façon d'exécuter I2P sur Mac OS X et comment se "
+"connecter à irc.telecomix.i2p.\n"
+"Par Telecomix"
+
+#: 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 ""
+"Felix Atari explique les principes de base de "
+"I2P\n"
+"(Vidéo Youtube)\n"
+"Agent Felix Atari du Telecomix Crypto Munitions Bureau.\n"
+"Par Telecomix"
+
+#: 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 ""
+" Comment aller sur I2P, le darknet P2P anonyme "
+"(Installeur Windows) \n"
+"(Vidéo Youtube)\n"
+"Ce tutoriel montre comment installer et configurer le logiciel nécessaire"
+" pour accéder à I2P."
+
+#: 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 ""
+"Comment se connecter à I2P\n"
+"(Vidéo Youtube)\n"
+"Comment installer I2P sur Ubuntu."
+
+#: 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 ""
+"Installation du logiciel darknet I2P sous Linux\n"
+"(Vidéo)\n"
+"Adrian Crenshaw.\n"
+"janvier 2011"
+
+#: i2p2www/pages/site/about/media.html:159
+#, python-format
+msgid ""
+"Short garlic routing animation\n"
+"(Youtube Video)\n"
+"Adrian Crenshaw.\n"
+msgstr ""
+"Courte animation du routage en oignon\n"
+"(Vidéo Youtube)\n"
+"Adrian Crenshaw.\n"
+
+#: i2p2www/pages/site/about/media.html:167
+msgid "Articles and Interviews"
+msgstr "Articles et interviews"
+
+#: 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 ""
+"0x90 interviewé par DistributedCity\n"
+"Partie 1\n"
+"Partie 2\n"
+"26 juillet 2002."
+
+#: 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 ""
+"0x90 interviewé par El Pais\n"
+"(en espagnol)\n"
+"Traduction anglaise\n"
+"31 octobre 2002."
+
+#: i2p2www/pages/site/about/media.html:185
+#, python-format
+msgid ""
+"2003 Business Week article referencing "
+"invisiblenet"
+msgstr ""
+"Article de Business Week de 2003 référençant le net "
+"invisible"
+
+#: 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 ""
+"Article de Netzwelt.de traitant de l'anonymat sur "
+"Internet\n"
+"(Allemand)\n"
+"Novembre 2007."
+
+#: i2p2www/pages/site/about/media.html:195
+#, python-format
+msgid ""
+"zzz interviewed by gulli.com\n"
+"March 2009\n"
+"German translation"
+msgstr ""
+"zzz interviewé par gulli.com\n"
+"Mars 2009\n"
+"Traduction allemande"
+
+#: 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 ""
+"zzz interviewé sur le podcast InfoSec Daily Ep. 454 "
+"(mp3)\n"
+"18 août 2011"
+
+#: i2p2www/pages/site/about/media.html:207
+#, python-format
+msgid ""
+"I2P - Anonymity for the Masses,\n"
+"Jonathan Cox,\n"
+"November 11, 2011."
+msgstr ""
+"I2P - Anonymity for the Masses,\n"
+"Jonathan Cox,\n"
+"11 novembre 2011."
+
+#: 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 ""
+"zzz et Lance James interviewés sur le podcast InfoSec"
+" Daily Ep. 596 (mp3)\n"
+"16 février 2012"
+
+#: i2p2www/pages/site/about/team.html:2
+msgid "Team"
+msgstr "Équipe"
+
+#: i2p2www/pages/site/about/team.html:4
+msgid "I2P Project Members"
+msgstr "Membres du projet 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 ""
+"Nous sommes un petit groupe disséminé sur tous les continents qui "
+"travaille\n"
+"à l'amélioration des différents aspects du projet et qui étudie et débat "
+"sur la\n"
+"conception du réseau.\n"
+"Impliquez-vous !"
+
+#: i2p2www/pages/site/about/team.html:14
+msgid "Admin"
+msgstr "Administration"
+
+#: i2p2www/pages/site/about/team.html:15
+msgid "Project Manager"
+msgstr "Chef de projet"
+
+#: i2p2www/pages/site/about/team.html:17
+msgid "point of contact of last resort"
+msgstr "contact en dernier ressort"
+
+#: i2p2www/pages/site/about/team.html:20
+msgid "Treasurer"
+msgstr "Trésorier"
+
+#: i2p2www/pages/site/about/team.html:22
+msgid "manage donations / accounts / bounties"
+msgstr "gère les dons / les comptes / les primes"
+
+#: i2p2www/pages/site/about/team.html:25
+msgid "PR manager"
+msgstr "Responsable des relations publiques"
+
+#: i2p2www/pages/site/about/team.html:27
+msgid "press contact, manages public relations and affairs"
+msgstr "contact presse, gère les relations publiques et les affaires"
+
+#: i2p2www/pages/site/about/team.html:30
+#, python-format
+msgid "Forum admin"
+msgstr "Admin du forum"
+
+#: i2p2www/pages/site/about/team.html:32
+msgid "manage the public user forum"
+msgstr "gère le forum utilisateurs public"
+
+#: i2p2www/pages/site/about/team.html:35
+msgid "Mirrors admin"
+msgstr "gère les miroirs du projet"
+
+#: i2p2www/pages/site/about/team.html:37
+msgid "manage the project mirrors"
+msgstr "gére les miroirs du projet"
+
+#: i2p2www/pages/site/about/team.html:40
+#, python-format
+msgid "Monotone guru"
+msgstr "Monotone guru"
+
+#: i2p2www/pages/site/about/team.html:42
+msgid "manage the public monotone repositories"
+msgstr "gére les référentiels monotones publics"
+
+#: i2p2www/pages/site/about/team.html:45
+msgid "Packager; Linux"
+msgstr "Packager des distribution Linux"
+
+#: i2p2www/pages/site/about/team.html:47
+msgid "Linux (Debian/Ubuntu) distribution packager"
+msgstr "Packager des distribution Linux (Debian/Ubuntu)"
+
+#: i2p2www/pages/site/about/team.html:50
+msgid "Packager; Windows"
+msgstr "Packager; Windows"
+
+#: i2p2www/pages/site/about/team.html:52
+msgid "Windows installer packager"
+msgstr "Packager de l'installateur sous Windows"
+
+#: i2p2www/pages/site/about/team.html:55
+msgid "Release Manager"
+msgstr "Responsable des versions"
+
+#: i2p2www/pages/site/about/team.html:57
+msgid "Builds and signs the releases"
+msgstr "Compile et signe les versions"
+
+#: i2p2www/pages/site/about/team.html:60
+msgid "Update admin"
+msgstr "Admin des update"
+
+#: i2p2www/pages/site/about/team.html:62
+msgid "Monitors and recruits in-network update hosts"
+msgstr "Surveille et recrute des hôtes de mise à jour dans le réseau"
+
+#: i2p2www/pages/site/about/team.html:65
+msgid "Reseed admin"
+msgstr "Admin réamorçage"
+
+#: i2p2www/pages/site/about/team.html:67
+msgid "Monitors, advises and recruits reseed hosts"
+msgstr "Surveille, conseille et recrute des hôtes de réamorçage"
+
+#: i2p2www/pages/site/about/team.html:70
+msgid "Security expert"
+msgstr "Expert en sécurité"
+
+#: 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 "vacant"
+
+#: i2p2www/pages/site/about/team.html:72
+msgid "threat model / crypto expert"
+msgstr "Modèle de menace / expert crypto"
+
+#: i2p2www/pages/site/about/team.html:77
+#, fuzzy
+msgid "Manage the project bug tracker"
+msgstr "gére les miroirs du projet"
+
+#: i2p2www/pages/site/about/team.html:80
+#, fuzzy
+msgid "Translation admins"
+msgstr "traductions en français"
+
+#: i2p2www/pages/site/about/team.html:85
+msgid "User Advocate"
+msgstr "Avocat des utilisateurs"
+
+#: i2p2www/pages/site/about/team.html:87
+msgid "gather, prioritize, advocate for user needs"
+msgstr "Rassemble, priorise, défend les besoins exprimés"
+
+#: i2p2www/pages/site/about/team.html:90
+msgid "Web Designer"
+msgstr "Concepteur web"
+
+#: i2p2www/pages/site/about/team.html:92
+msgid "manage the public project website content design"
+msgstr "Gère le design du site web public du projet"
+
+#: i2p2www/pages/site/about/team.html:95
+#, python-format
+msgid "Webserver admin"
+msgstr "Admin du serveur Web"
+
+#: i2p2www/pages/site/about/team.html:97
+msgid "manage the public project webservers"
+msgstr "Gère les serveurs web publics du projet"
+
+#: i2p2www/pages/site/about/team.html:100
+#, python-format
+msgid "Website admin"
+msgstr "Admin du site web"
+
+#: i2p2www/pages/site/about/team.html:102
+msgid "manage the public project website content"
+msgstr "Gère le contenu du site web public du projet"
+
+#: i2p2www/pages/site/about/team.html:105
+msgid "News Admin"
+msgstr "Admin actualités"
+
+#: i2p2www/pages/site/about/team.html:107
+msgid "manage router console news feed"
+msgstr "Gérer le fil d'actualités de la console du routeur"
+
+#: i2p2www/pages/site/about/team.html:110
+msgid "Director of passion"
+msgstr "Directeur de passion"
+
+#: i2p2www/pages/site/about/team.html:112
+msgid "community motivator"
+msgstr "motivateur de communauté"
+
+#: i2p2www/pages/site/about/team.html:116
+msgid "Dev"
+msgstr "Développement"
+
+#: i2p2www/pages/site/about/team.html:117
+msgid "Core Lead"
+msgstr "Meneur principal"
+
+#: i2p2www/pages/site/about/team.html:119
+msgid "lead dev for the SDK and router"
+msgstr "Dirige le développement du SDK et du routeur"
+
+#: i2p2www/pages/site/about/team.html:122
+#, python-format
+msgid "I2P mail lead"
+msgstr "Meneur de I2P mail"
+
+#: i2p2www/pages/site/about/team.html:124
+msgid "organize and develop the i2p mail system"
+msgstr "organise et développe le système de courrier d'i2p"
+
+#: i2p2www/pages/site/about/team.html:127
+#, python-format
+msgid "I2Host lead"
+msgstr "Meneur de I2Host"
+
+#: i2p2www/pages/site/about/team.html:129
+msgid "I2Host addressbook application"
+msgstr "Application carnet d'adresses I2Host "
+
+#: i2p2www/pages/site/about/team.html:132
+#, python-format
+msgid "BOB lead"
+msgstr "Meneur de BOB"
+
+#: i2p2www/pages/site/about/team.html:134
+msgid "Basic Open Bridge"
+msgstr "Basic Open Bridge"
+
+#: i2p2www/pages/site/about/team.html:137
+#, python-format
+msgid "I2P-Bote lead"
+msgstr "Meneur de I2P-Bote"
+
+#: i2p2www/pages/site/about/team.html:139
+msgid "I2PBote plugin"
+msgstr "Plugin I2PBote"
+
+#: i2p2www/pages/site/about/team.html:142
+#, python-format
+msgid "Robert lead"
+msgstr "Meneur de Robert"
+
+#: i2p2www/pages/site/about/team.html:144
+msgid "Robert BitTorrent client"
+msgstr "Client BitTorrent Robert"
+
+#: i2p2www/pages/site/about/team.html:147
+#, python-format
+msgid "I2Phex lead"
+msgstr "Meneur de I2Phex"
+
+#: i2p2www/pages/site/about/team.html:149
+msgid "I2Phex Gnutella client"
+msgstr "Client Gnutella I2Phex"
+
+#: i2p2www/pages/site/about/team.html:152
+#, python-format
+msgid "I2PSnark lead"
+msgstr "Meneur de I2PSnark"
+
+#: i2p2www/pages/site/about/team.html:154
+msgid "Maintains the integrated Bittorrent client"
+msgstr "Maintient le client Bittorrent intégré"
+
+#: i2p2www/pages/site/about/team.html:157
+#, python-format
+msgid "iMule lead"
+msgstr "Meneur iMule"
+
+#: i2p2www/pages/site/about/team.html:159
+msgid "eMule client over I2P"
+msgstr "Client eMule sur I2P"
+
+#: i2p2www/pages/site/about/team.html:162
+#, python-format
+msgid "Syndie lead"
+msgstr "Meneur Syndie"
+
+#: i2p2www/pages/site/about/team.html:164
+msgid "Syndie development"
+msgstr "Développement de Syndie"
+
+#: i2p2www/pages/site/about/team.html:167
+msgid "Susimail lead"
+msgstr "Meneur de Susimail"
+
+#: i2p2www/pages/site/about/team.html:169
+msgid "Susimail development"
+msgstr "Développement de Susimail"
+
+#: i2p2www/pages/site/about/team.html:172
+msgid "Console"
+msgstr "Console"
+
+#: i2p2www/pages/site/about/team.html:174
+msgid "Router console HTML/CSS design"
+msgstr "Design HTML/CSS de la console routeur"
+
+#: i2p2www/pages/site/about/team.html:177
+msgid "SAM"
+msgstr "SAM"
+
+#: i2p2www/pages/site/about/team.html:179
+msgid "SAM maintainer"
+msgstr "Maintient SAM"
+
+#: i2p2www/pages/site/about/team.html:182
+msgid "I2PCPP lead"
+msgstr "Meneur I2PCPP"
+
+#: i2p2www/pages/site/about/team.html:184
+msgid "C++ Router"
+msgstr "Routeur C++"
+
+#: 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 "Contributeurs"
+
+#: i2p2www/pages/site/about/team.html:195
+msgid "fire2pe dev, console enhancements"
+msgstr "Fire2pe dev, améliorations console"
+
+#: i2p2www/pages/site/about/team.html:199
+msgid "desktopgui, dijjer port"
+msgstr "Interface graphique utilisateur, portage dijjer"
+
+#: i2p2www/pages/site/about/team.html:203
+msgid "Debian/Ubuntu Packager and PPA maintainer"
+msgstr "Packager Debian/Ubuntu et mainteneur de PPA "
+
+#: i2p2www/pages/site/about/team.html:207
+msgid "Routerconsole backend and UI work, website revamp, unit tests work"
+msgstr ""
+"Arrière-plan et travail sur l'UI de la console routeur, réorganisation du"
+" site Web, travail sur les tests d'unité"
+
+#: i2p2www/pages/site/about/team.html:212
+msgid "Help needed on many fronts!"
+msgstr "Aide nécessaire sur beaucoup de fronts !"
+
+#: i2p2www/pages/site/about/team.html:216
+msgid "Past contributors"
+msgstr "Anciens contributeurs"
+
+#: i2p2www/pages/site/about/team.html:218
+msgid "I2PTunnel development, ministreaming library"
+msgstr "développement I2PTunnel, mini bibliothèque de flux"
+
+#: i2p2www/pages/site/about/team.html:222
+msgid "Project lead, Syndie lead"
+msgstr "Responsable du projet, idem pour Syndie"
+
+#: i2p2www/pages/site/about/team.html:226
+msgid "Project lead, Syndie lead, I2Phex, support guru"
+msgstr "Responsable du projet, meneur de Syndie, I2Phex, gourou en support"
+
+#: i2p2www/pages/site/about/team.html:230
+msgid "iMule lead"
+msgstr "Meneur iMule"
+
+#: 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 "Travail I2Phex"
+
+#: i2p2www/pages/site/about/team.html:246
+msgid "Python SAM library, attack simulations"
+msgstr "Bibliothèque Python SAM, simulations d'attaques"
+
+#: i2p2www/pages/site/about/team.html:250
+msgid "i2pmail development"
+msgstr "Développement de i2pmail"
+
+#: i2p2www/pages/site/about/team.html:254
+msgid "Syndie help"
+msgstr "Aide pour Syndie"
+
+#: i2p2www/pages/site/about/team.html:258
+msgid "i2p mail,susimail and susidns apps"
+msgstr "Apps i2p mail, susimail et susidns"
+
+#: i2p2www/pages/site/about/team.html:262
+msgid "I2Phex (port of Phex to I2P)"
+msgstr "I2Phex (portage de Phex vers I2P)"
+
+#: i2p2www/pages/site/about/team.html:266
+msgid "addressbook,i2p-bt,syndie client"
+msgstr "carnet d'adresses, i2p-bt, client Syndie"
+
+#: i2p2www/pages/site/about/team.html:270
+msgid "organize and develop the i2p-bt BitTorrent port"
+msgstr "Organise et développe le portage BitTorrent i2p-bt"
+
+#: i2p2www/pages/site/about/team.html:274
+msgid "addressbook, i2p-bt, syndie client development"
+msgstr "Carnet d'adresses, i2p-bt, développement du client Syndie"
+
+#: i2p2www/pages/site/about/team.html:278
+msgid "encryption and signature routines, I2PIM"
+msgstr "Routines d'encryption et de signature, I2PIM"
+
+#: i2p2www/pages/site/about/team.html:282
+msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)"
+msgstr "Code jython de SAM, travail sur stasher (DHT) et v2v (VoI2P)"
+
+#: i2p2www/pages/site/about/team.html:286
+msgid "installer, systray, bogobot"
+msgstr "installateur, zone de notification, bogobot"
+
+#: i2p2www/pages/site/about/team.html:290
+msgid "jbigi development, wiki migration, doc cleanup"
+msgstr "Développement jbigi, migration du wiki, nettoyage de la doc"
+
+#: i2p2www/pages/site/about/team.html:294
+msgid "java debugging and client development on I2PTunnel and the router console"
+msgstr ""
+"Débogage java debugging et développement de client sur I2PTunnel et la "
+"console du routeur"
+
+#: i2p2www/pages/site/about/team.html:298
+msgid "SAM perl module"
+msgstr "Module perl de SAM"
+
+#: i2p2www/pages/site/about/team.html:302
+msgid "i2psnark work"
+msgstr "travail i2psnark"
+
+#: i2p2www/pages/site/about/team.html:306
+msgid "java cleanup"
+msgstr "Nettoyage Java"
+
+#: i2p2www/pages/site/about/team.html:310
+msgid "docs. wiki migration"
+msgstr "Docs. Migration du wiki"
+
+#: i2p2www/pages/site/about/team.html:314
+msgid "translations into French"
+msgstr "traductions en français"
+
+#: i2p2www/pages/site/about/team.html:318
+msgid "C port of jcpuid"
+msgstr "Portage en C de jcpuid"
+
+#: i2p2www/pages/site/about/team.html:322
+msgid "C# SAM library, pants, fortuna integration"
+msgstr "Bibliothèque SAM C#, pants, fortuna integration"
+
+#: i2p2www/pages/site/about/team.html:326
+msgid "libSAM"
+msgstr "libSAM"
+
+#: i2p2www/pages/site/about/team.html:330
+#: i2p2www/pages/site/about/team.html:334
+msgid "i2p-bt tracker development"
+msgstr "Développement tracker bt-i2p"
+
+#: i2p2www/pages/site/about/team.html:338
+msgid "Console and website themes"
+msgstr "Thèmes console et site web"
+
+#: i2p2www/pages/site/about/team.html:368
+msgid "… and many others"
+msgstr "… et de nombreux autres"
+
+#: i2p2www/pages/site/about/performance/future.html:2
+msgid "Future Performance Improvements"
+msgstr "Améliorations de la performance dans le futur"
+
+#: i2p2www/pages/site/about/performance/future.html:4
+msgid "August 2010"
+msgstr "Août 2010"
+
+#: 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 ""
+"Il y a quelques techniques majeures qui peuvent être faites pour "
+"s'améliorer\n"
+"la performance perçue de I2P - certaines des suivantes sont liées au CPU,"
+" d'autres\n"
+"sont liées à la bande passante, et d'autres sont liées au protocole. "
+"Cependant, toutes\n"
+"ces dimensions affectent la latence, le débit, et la performance perçue "
+"du\n"
+"réseau, comme elles réduisent le conflit pour des ressources rares. Cette"
+" liste est bien sûr\n"
+"incomplète, mais elle couvre vraiment les points majeurs qui sont vus."
+
+#: 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 ""
+"Pour les améliorations de performance passées voir l'\n"
+"histoire de performance."
+
+#: i2p2www/pages/site/about/performance/future.html:20
+msgid "Better peer profiling and selection"
+msgstr "Meilleure sélection et profilage du pair"
+
+#: 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 ""
+"Une des parties probablement les plus importantes pour obtenir la "
+"performance plus rapide sera\n"
+"d'améliorer comment les routeurs choisissent les pairs( au travers "
+"desquels ils construisent leurs tunnels -\n"
+"en s'assurant qu'ils n'utilisent pas de pairs avec des liens lents ou "
+"avec des liens rapides qui\n"
+"seraient surchargés, etc. De plus, nous devons nous assurer que nous ne "
+"nous exposons pas\n"
+"nous-mêmes à une attaque Sybil\n"
+"lancée depuis un adversaire puissant avec beaucoup de machines rapides."
+
+#: i2p2www/pages/site/about/performance/future.html:30
+msgid "Network database tuning"
+msgstr "Réglage de la base de données réseau"
+
+#: 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 ""
+"Nous allons vouloir être plus efficaces en guérissant la base de données "
+"de réseau\n"
+"et les algorithmes de maintenance - plutôt que constamment explorer le "
+"keyspace pour de nouveaux\n"
+"pairs - cause d'un nombre important de messages de réseau et de charge de"
+" routeur - nous\n"
+"pouvons ralentir ou peut même arrêter d'explorer jusqu'à ce que nous "
+"détections qu'il y a\n"
+"quelque chose de nouveau méritant d'être trouvé (ex: dégrader le taux "
+"d'exploration en se basant sur la dernière fois que quelqu'un nous a "
+"donné une référence de quelqu'un dont nous n'avions jamais entendu "
+"parler). Nous pouvons aussi faire certains\n"
+"réglages sur ce que nous envoyons actuellement - sur combien de pairs "
+"nous rebondissons (ou même si nous\n"
+"rebondissons en retour une réponse), aussi bien que combien de recherches"
+" simultanées nous accomplissons."
+
+#: i2p2www/pages/site/about/performance/future.html:42
+msgid "Session Tag Tuning and Improvements"
+msgstr "Réglage et améliorations de Tag de session"
+
+#: 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 ""
+"La façon dont l'algorithme ElGamal/AES+SessionTag\n"
+"fonctione est en gérant un ensemble de tableaux de 32 octets à usage "
+"unique, et en\n"
+"les faisant expirer s'ils ne sont pas utilisés assez rapidement. Si nous "
+"les faisons expirer trop tôt, nous\n"
+"sommes obligés de nous replier en ayant recours à un (coûteux) plein "
+"chiffrage ElGamal, mais si nous ne\n"
+"les faisons pas expirer assez rapidement, nous devons réduire leur "
+"quantité pour que nous ne soyons pas \n"
+"à court de mémoire (et si le destinataire est d'une façon ou d'une autre "
+"corrompu et perd certaines étiquettes, encore plus d'échecs de chiffrage "
+"peuvent se produire avant la détection). Avec une certaine détection plus"
+" active et\n"
+"des algorithmes de retour d'information, nous pouvons sans risque et plus"
+" efficacement ajuster la durée de vie des étiquettes, remplaçant le "
+"chiffrage ElGamal avec une insignifiante opération AES."
+
+#: 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 ""
+"Des idées supplémentaires pour améliorer la livraison d'étiquette de "
+"session (Session Tag) sont décrites sur la\n"
+"page ElGamal/AES+SessionTag page."
+
+#: i2p2www/pages/site/about/performance/future.html:61
+msgid "Migrate sessionTag to synchronized PRNG"
+msgstr "Migrer l'étiquette de session (sessionTag) vers un PRNG synchronisé"
+
+#: 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 ""
+"Dès maintenant, notre algorithme ElGamal/AES+SessionTag\n"
+"fonctionne en étiquetant chaque message crypté avec un \"nonce\" "
+"(occasion ?) unique aléatoire\n"
+"de 32 octets (\"une étiquette de session\"), identifiant ce message comme"
+" étant crypté\n"
+"avec la clé de la session AES associée. Ceci empêche des pairs de "
+"distinguer\n"
+"les messages faisant partie de la même session, sachant que chaque "
+"message a une nouvelle étiquette complètement aléatoire. Pour accomplir "
+"ceci, tous les quelques messages empaquette un tout\n"
+"nouvel ensemble d'étiquettes de session dans le message crypté lui-même, "
+"livrant d'une manière transparente\n"
+"une façon d'identifier des messages futurs. Nous devons alors garder la "
+"trace\n"
+"de quels messages sont livrés avec succès afin que nous sachions quelles "
+"étiquettes\n"
+"nous pouvons utiliser."
+
+#: 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 ""
+"Ceci marche bien et c'est assez robuste, cependant c'est inefficace en "
+"termes\n"
+"d'utilisation de bande passante, comme cela exige la livraison de ces "
+"étiquettes en avance de\n"
+"temps (et toutes les étiquettes peuvent ne pas être nécessaires, ou "
+"certaines peuvent être gaspillés, en raison de\n"
+"leur expiration). En moyenne cependant, pré délivrer l'étiquette de "
+"session coûte\n"
+"32 octets par message (la taille d'une étiquette). Comme Taral l'a "
+"suggéré, cette\n"
+"taille peut être évitée en remplaçant la livraison des étiquettes par un "
+"PRNG synchronisé\n"
+" - quand une nouvelle session est établie (via un block ElGamal crypté),\n"
+"les deux côtés essaiment un PRNG pour utilisation et produisent les "
+"étiquettes de session sur\n"
+"demande (avec le destinataire pré calculant à l'avance les quelques peu "
+"de valeurs suivantes possibles\n"
+"afin de traiter la panne de livraison)."
+
+#: i2p2www/pages/site/about/performance/future.html:87
+msgid "Longer lasting tunnels"
+msgstr "Tunnels de longue durée"
+
+#: 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 ""
+"La durée actuelle de tunnel est par défaut de 10 minutes, c'est assez "
+"arbitraire, quoique\n"
+"cela \"va bien\". Une fois que nous aurons le code de guérison de tunnel "
+"et un code de détection d'échec plus efficace, nous pourrons sans risque "
+"varier ces durées, réduisant les\n"
+"charges réseau et UC (dues aux coûteux messages de création de tunnel)."
+
+#: 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 ""
+"Ceci semble être une réparation facile pour une haute charge sur des "
+"routeurs à grande bande passante, mais\n"
+"nous ne devrions pas y recourir jusqu'à ce que nous ayons ajusté le "
+"tunnel construisant des algorithmes plus loin. \n"
+"Cependant, la durée de vie de tunnel de 10  minutes est codée en dur dans"
+" un bon nombre d'endroits,\n"
+"donc un effort substantiel serait exigé pour changer la durée.\n"
+"Aussi, il serait difficile de maintenir la compatibilité descendante avec"
+" un tel changement."
+
+#: 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 ""
+"Actuellement, puisque dans le réseau le taux de réussite de construction "
+"de tunnel est en moyenne assez élevé,\n"
+"il n'y a actuellement aucun plan visant à étendre la durée de vie de "
+"tunnel."
+
+#: i2p2www/pages/site/about/performance/future.html:108
+msgid "Adjust the timeouts"
+msgstr "Ajuster les temps d'échéance"
+
+#: 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 ""
+"Encore une autre des choses assez arbitraires mais avec le \"sentiment "
+"que ça va bien\" que nous avons : ce sont\n"
+"les temps d'échéance (time out) actuels pour les diverses activités. "
+"Pourquoi avons-nous un temps d'échéance\n"
+"de 60 secondes en cas de \"pair inaccessible\" ? Pourquoi essayons-nous "
+"d'envoyer à travers un tunnel différent\n"
+"qu'un LeaseSet annonce après 10 secondes ? Pourquoi les questions à la "
+"base de données de réseau\n"
+"sont limitées par des plafonds de 60 ou 20 secondes ? Pourquoi les "
+"destinations sont-elles configurées pour demander un nouvel ensemble de "
+"tunnels toutes les 10 minutes ? Pourquoi permettons-nous 60 secondes à un"
+" pair pour répondre à notre requête à se joindre un tunnel ? Pourquoi "
+"considérons-nous un tunnel qui\n"
+"ne passe pas notre test dans les 60 secondes \"mort\" ?"
+
+#: 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 ""
+"Chacun de ces impondérables peut être abordé avec du code plus adaptatif,"
+" et aussi\n"
+"avec des paramètres ajustables pour tenir compte de différences plus "
+"appropriées entre\n"
+"bande passante, latence et utilisation de CPU."
+
+#: i2p2www/pages/site/about/performance/future.html:125
+msgid "Full streaming protocol improvements"
+msgstr "Améliorations du protocole full streaming"
+
+#: 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 ""
+"Peut-être re-permettre le profil stream interactif (la\n"
+"mise en œuvre actuelle utilise seulement le profil stream en vrac (bulk)."
+
+#: 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 ""
+"Limitation de bande passante au niveau du client (ou dans les deux "
+"directions sur un flux stream,\n"
+"ou probablement partagée à travers de multiples flux stream). Ceci serait"
+" bien sûr en supplément à\n"
+"la limitation de bande passante globale du routeur."
+
+#: i2p2www/pages/site/about/performance/future.html:141
+msgid ""
+"Access control lists (only allowing streams to or from certain other "
+"known \n"
+"destinations)."
+msgstr ""
+"Listes de contrôle d'accès (permettant seulement des flux vers ou depuis "
+"certaines autres\n"
+"destinations connues)."
+
+#: 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 ""
+"Le contrôle Web et le contrôle de la santé des divers flux, autant\n"
+"que la capacité de, explicitement, les fermer ou les étrangler."
+
+#: 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 ""
+"Des idées supplémentaires pour améliorer la bibliothèque de streaming "
+"sont décrites sur la\n"
+"page de bibliothèque streaming."
+
+#: i2p2www/pages/site/about/performance/history.html:2
+msgid "Performance History"
+msgstr "Historique performance"
+
+#: 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 ""
+"Des améliorations notables de performance ont été faites en utilisant les"
+" techniques ci-dessous.\n"
+"Il y a plus pour faire, voir la page performance\n"
+"pour les problèmes actuels et les pensées."
+
+#: i2p2www/pages/site/about/performance/history.html:10
+msgid "Native math"
+msgstr "maths natales"
+
+#: 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 "implémenté"
+
+#: 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 ""
+"Quand j'ai dernièrement établi le profil du code d'I2P, la grande "
+"majorité du temps a été passée dans\n"
+"une fonction : java.math.BigInteger's\n"
+"modPow.\n"
+"Plutôt que d'essayer d'accorder cette méthode, nous ferons appel à\n"
+"GNU MP - une bibliothèque mathématique follement "
+"rapide\n"
+"(avec assembleur accordé pour beaucoup d'architectures). (éditeur : "
+"voir\n"
+"NativeBigInteger pour cryptographie clé publique "
+"plus rapide)"
+
+#: 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 ""
+"\n"
+"ugha et duck travaillent sur le code glue de C/JNI, et le code Java "
+"existant\n"
+"est déjà déployé avec des crochets pour cela quand ce sera prêt. Les "
+"résultats préliminaires\n"
+"semblent fantastiques - faire tourner le routeur avec le modPow GMP natal"
+" fournit\n"
+"une accélération de 800* *37; de la performance en chiffrage, et la "
+"charge a été réduite à moitié. Ceci\n"
+"était juste sur la machine d'un utilisateur et les choses sont très loin "
+"d'être prêtes pour le paquetage\n"
+"ni le déploiement, pour le moment."
+
+#: i2p2www/pages/site/about/performance/history.html:32
+msgid "Garlic wrapping a \"reply\" LeaseSet"
+msgstr "Oignon enveloppant un jeux de baux \"réponse\""
+
+#: i2p2www/pages/site/about/performance/history.html:33
+msgid "implemented but needs tuning"
+msgstr "implémenté mais aurait besoin d'ajustement"
+
+#: 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 ""
+"Ce tweak d'algorithme sera seulement approprié pour les applications qui "
+"veulent que leurs\n"
+"pairs leur répondent à elles (quoique cela inclue toutes les utilisations"
+" de I2PTunnel ou\n"
+"de Mihi's ministreaming lib) :"
+
+#: 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 ""
+"Précédemment, quand Alice envoyait un message à Bob, quand Bob répondait "
+"qu'il avait dû faire une\n"
+"consultation dans la base de données de réseau - émettant quelques "
+"requêtes pour obtenir le jeu de bail\n"
+"actuel d'Alice. S'il a déjà le jeu de bail actuel d'Alice, il peut au "
+"lieu de cela\n"
+"juste envoyer sa réponse immédiatement - c'est (une partie de) pourquoi "
+"cela prend typiquement\n"
+"un peu plus longtemps de parler à quelqu'un la première fois que vous "
+"vous connectez, mais ultérieur\n"
+"la communication est plus rapide. Actuellement - pour tous les clients - "
+"nous enveloppons\n"
+"le jeu de bail actuel de l'expéditeur dans l'oignon qui est livré au "
+"destinataire,\n"
+"afin que quand ils vont répondre, ils vont toujours avoir le jeu "
+"de bail stocké localement\n"
+"- ceci enlevant complètement n'importe quel besoin d'une consultation de "
+"base de données de réseau sur réponses.\n"
+"Cela compromet une grande partie de la bande passante de l'expéditeur "
+"pour cette réponse plus rapide.\n"
+"Si nous ne faisons pas ceci très souvent,\n"
+"l'utilisation globale de la bande passante du réseau diminuerait, puisque"
+" le destinataire n'a pas à\n"
+"faire la consultation de base de données du réseau."
+
+#: 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 ""
+"Pour les jeux de baux non publiés comme \"clients partagés\", ceci est la"
+" seule façon\n"
+"d'obtenir le bail vers Bob. Malheureusement ce groupage ajoute chaque "
+"fois\n"
+"presque 100% au-dessus d'une connexion à haute bande passante et "
+"beaucoup plus à\n"
+"une connexion avec des plus petits messages."
+
+#: 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 ""
+"Les changements prévus pour la sortie 0.6.2 grouperont le jeu de bail "
+"seulement quand\n"
+"nécessaire, au début d'une connexion ou quand le jeu de bail change.\n"
+"Ceci va considérablement réduire la charge totale au-dessus de la "
+"messagerie d'I2P."
+
+#: i2p2www/pages/site/about/performance/history.html:66
+msgid "More efficient TCP rejection"
+msgstr "Rejet TCP plus efficace"
+
+#: i2p2www/pages/site/about/performance/history.html:68
+#, fuzzy
+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 ""
+"À l'heure actuelle, toutes les connexions TCP font toute leur validation "
+"de pair après\n"
+"être passées à travers la (coûteuse) poignée de mains Diffie-Hellman afin"
+" de négocier\n"
+"une clé de session privée. Cela signifie que si l'horloge de quelqu'un "
+"est vraiment fausse, ou\n"
+"que leur NAT/FIREWALL/etc est configuré incorrectement (ou qu'ils font "
+"simplement fonctionner une\n"
+"version incompatible du routeur), ils vont systématiquement (quoique pas"
+" \n"
+"constamment, grâce à la liste noire) causer un futile et coûteuse "
+"opération cryptographique\n"
+"sur tous les pairs qu'ils connaissent. Tandis que allons vouloir garder "
+"certaines\n"
+"vérifications/validations en dedans de la frontière de chiffrage, nous "
+"allons vouloir mettre à jour le \n"
+"protocole afin de faire d'abord un peu de cela, afin que nous puissions "
+"les rejeter proprement\n"
+"sans gaspiller beaucoup de CPU ni d'autres ressources."
+
+#: i2p2www/pages/site/about/performance/history.html:81
+msgid "Adjust the tunnel testing"
+msgstr "Ajuster le test de tunnel"
+
+#: 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 ""
+"Plutôt qu'aller avec le plan assez aléatoire que nous avons maintenant, "
+"nous devrions utiliser un\n"
+"algorithme plus conscient du contexte pour tester des tunnels. Par "
+"exemple si nous savons déjà qu'il\n"
+"passe des données valables correctement, il n'y a aucun besoin de le "
+"tester, tandis que si nous n'avons pas\n"
+"vu aucune données passer à travers récemment, peut-être qu'il est digne "
+"d'intérêt de jeter quelques données vers\n"
+"son chemin. Ceci réduira le conflit de tunnel en raison de l'excès de "
+"messages aussi bien qu'améliorer\n"
+"la vitesse à laquelle nous détectons - et adressons - les tunnels en "
+"échec."
+
+#: i2p2www/pages/site/about/performance/history.html:92
+msgid "Persistent Tunnel / Lease Selection"
+msgstr "Tunnel persistant / Sélection de bail"
+
+#: 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 ""
+"La sélection de tunnel en partance est mise en œuvre dans 0.6.1.30, la "
+"sélection de bail arrivant\n"
+"est mise en œuvre dans la release 0.6.2."
+
+#: 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 ""
+"Sélectionner au hasard des tunnels et des baux pour chaque message crée "
+"une grande\n"
+"incidence de défaillance de livraison, laquelle empêche la lib streaming "
+"d'\n"
+"augmenter sa taille de fenêtre autant qu'elle le pourrait. En persistant "
+"avec les\n"
+"mêmes sélections pour une connexion donné, le taux de transfert est "
+"beaucoup plus rapide."
+
+#: i2p2www/pages/site/about/performance/history.html:104
+msgid "Compress some data structures"
+msgstr "Compresse certaines structures de données"
+
+#: 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 ""
+"Les messages I2NP et les données qu'ils contiennent sont déjà définis "
+"dans une la structure assez\n"
+"compacte, quoiqu'un attribut de la structure de RouterInfo ne l'est pas -"
+" \n"
+"\"options\" est le nom ASCII plain = la cartographie de valeur. Tout de "
+"suite, nous le remplissons\n"
+"avec ceux statistiques publiées - autour de 3300 octets par pair. "
+"Insignifiante à\n"
+"mettre en œuvre, la compression GZIP la réduirait presque à 1/3 de sa "
+"taille, et quand vous\n"
+"considérez combien de structures RouterInfo sont passées à travers le "
+"réseau, c'est\n"
+"une économie significative - chaque fois qu'un routeur demande à un autre"
+" routeur une entrée\n"
+"networkDb que le pair n'a pas, cela renvoie 3-10 RouterInfo d'entre eux."
+
+#: i2p2www/pages/site/about/performance/history.html:117
+msgid "Update the ministreaming protocol"
+msgstr "Mise à jour du protocole ministreaming"
+
+#: i2p2www/pages/site/about/performance/history.html:118
+msgid "replaced by full streaming protocol"
+msgstr "remplacé par le protocole plein ministreaming"
+
+#: 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 ""
+"Actuellement la bibliothèque ministreaming de mihi a un protocole de "
+"négociation\n"
+"de flux assez simple - Alice envoie à Bob un message SYN, Bob répond avec"
+" un message ACK, puis\n"
+"Alice et Bob s'envoient quelques données, jusqu'à ce que l'un d'entre eux"
+" envoie à l'autre\n"
+"un message CLOSE. Pour des connexion durant longtemps (à un serveur IRC, "
+"par exemple),\n"
+"cette overhead est négligeable, mais pour des situations de simples "
+"uniques demandes/réponses \n"
+"(une demande/réponse HTTP, par exemple), c'est plus que deux fois plus de"
+" messages que\n"
+"nécessaire. Si, cependant, Alice a superposé sa première charge utile "
+"dans avec le message SYN,\n"
+"et Bob a superposé sa première réponse avec l'ACK - et peut-être aussi\n"
+"inclus le drapeau CLOSE - des flux passagers tels que des requêtes HTTP "
+"pourraient être\n"
+"réduits à une paire de messages, au lieu du SYN+ACK+requête+réponse+CLOSE."
+
+#: i2p2www/pages/site/about/performance/history.html:132
+msgid "Implement full streaming protocol"
+msgstr "Implémenter protocole full streaming"
+
+#: 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 ""
+"Le protocole ministreaming profite d'une décision de pauvre conception "
+"dans le\n"
+"protocole client I2P (I2CP) - l'exposition de \"mode=GUARANTEED\", "
+"permettant ce\n"
+"qui autrement serait incertain, le meilleur effort, le protocole basé "
+"message qui est utilisé\n"
+"comme fiable, opération bloquante (sous les couvertures, il est toujours "
+"incertain et\n"
+"basé message, avec le routeur fournissant des garanties de livraison de "
+"l'emballage oignon\n"
+"par un message \"ACK\" dans la charge utile, si une fois que les données "
+"arrivent à l'objectif, le\n"
+"message ACK nous est expédié en retour [à travers des tunnels, bien sûr])."
+
+#: 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 ""
+"Comme je l'ai dit, avoir\n"
+"I2PTunnel (et la bibliothèque ministreaming) suivent cette route qui "
+"était la meilleure chose qui\n"
+"pouvait être faite, mais des mécanismes plus efficaces sont disponibles. "
+"Quand nous retirons la\n"
+"fonctionnalité \"Mode=GUARANTEED\" , nous nous laissons essentiellement "
+"avec un\n"
+"I2CP qui ressemble à une couche IP anonyme, et comme telle, nous serons "
+"capables de\n"
+"mettre en œuvre la bibliothèque streaming pour profiter des expériences "
+"de conception\n"
+"de la couche TCP - ACKs sélectifs, détection de congestion, nagle, etc."
+
+#: i2p2www/pages/site/about/performance/index.html:2
+msgid "Performance"
+msgstr "Performance"
+
+#: 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 ""
+"Comment est-ce que I2P fonctionne, pourquoi est-il lent, et pourquoi "
+"n'utilise-t-il pas complètement ma bande passante ?"
+
+#: 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 ""
+"Probablement qu'une de choses la plus fréquemment demandée par les gens "
+"est \"à quelle vitesse est I2P ?\",\n"
+"et aucun ne semble aimer la réponse - \"cela dépend\". Après avoir essayé"
+" I2P, la\n"
+"chose suivante qu'ils demandent est \"deviendra-t-il plus rapide ?\", et "
+"la réponse à cela est plus\n"
+"emphatique oui."
+
+#: 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 ""
+"I2P est un réseau complètement dynamique. Chaque client est connu par les"
+" autres noeuds et teste des noeuds connus localement pour leur "
+"accessibilité et leur capacité.\n"
+"Seuls des noeuds accessibles et capables sont sauvegardés dans la NetDB "
+"(base de données réseau) locale (ceci est généralement seulement une "
+"portion du réseau, autour de 500-1000).\n"
+"Quand I2P construit des tunnels, il sélectionne la meilleure ressource "
+"depuis ce bassin. Par exemple, un petit sous-ensemble de 20-50 noeuds est"
+" seulement disponible pour construire des tunnels avec.\n"
+"Parce que le test se produit chaque minute, le bassin de noeuds utilisés "
+"change chaque minute.\n"
+"Chaque noeud I2P connaît une partie différente du réseau, cela signifiant"
+" que chaque routeur a un ensemble différent de noeuds I2P pouvant être "
+"utilisé pour des tunnels.\n"
+"Même si deux routeurs ont le même sous-ensemble de noeuds connus, les "
+"tests d'accessibilité et de capacité montreront probablement des "
+"résultats différents, parce que les autres routeurs pourraient être "
+"chargés pendant qu'un autre routeur teste, mais être libres si le "
+"deuxième routeur teste."
+
+#: 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 ""
+"Le texte ci-dessus décrit pourquoi chaque noeud I2P a des noeuds "
+"différents pour construire des tunnels.\n"
+"Parce que chaque noeud I2P a une latence différente et une largeur de "
+"bande passante, des tunnels (qui sont construits via ces noeuds) ont une "
+"latence différente et des valeurs différentes de bande passante.\n"
+"Et parce que chaque noeud I2P a différents tunnels construits, aucun de "
+"deux noeud I2P n'a les mêmes ensembles de tunnels."
+
+#: 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 ""
+"Un serveur/client est connu comme une \"destination\" et chaque "
+"destination a au moins un tunnel arrivant et un en partance. Par défaut "
+"il y a 3 étapes par tunnel.\n"
+"Ceci s'élève à 12 étapes (c'est-à-dire 12 noeuds I2P différents) pour un "
+"aller-retour complet client-serveur-client."
+
+#: 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 ""
+"Chaque paquet de données est envoyé par 6 autres noeuds I2P jusqu'à ce "
+"qu'il atteigne le serveur :"
+
+#: i2p2www/pages/site/about/performance/index.html:40
+msgid "and on way back 6 different I2P nodes:"
+msgstr "et au retour 6 noeuds I2P différents :"
+
+#: 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 ""
+"Comme la plupart du trafic sur I2P (www, torrent, ...) a besoin de "
+"paquets ack jusqu'à ce que de nouvelles données soient envoyées, il doit "
+"attendre jusqu'à ce qu'un paquet ack revienne du serveur.\n"
+"Au final : envoyer des données, attendre ack, envoyer plus de données, "
+"attendre ack, ...\n"
+"Comme le RTT (RoundTripTime) s'additionne de la latence de chaque noeud "
+"individuel I2P et chaque connexion de cet aller-retour, cela prend "
+"d'habitude 1-3 secondes jusqu'à ce qu'un paquet ack revienne au client.\n"
+"Avec quelques composants de TCP et du transport d'I2P, un paquet de "
+"données a une taille limitée et ne peut pas être aussi grand que nous le "
+"voudrions.\n"
+"Ensemble, ces conditions mettent une limite de bande passante maximum par"
+" tunnel de 20-50 Ko/sec.\n"
+"Mais si SEULEMENT UNE étape dans le tunnel a une bande passante de "
+"seulement 5 Ko/sec à dépenser, le tunnel entier est limité à 5 Ko/sec, "
+"indépendamment de la\n"
+"latence et d'autres limitations."
+
+#: 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 ""
+"En raison du chiffrement utilisé et autres configurations dans I2P "
+"(comment les tunnels sont construits, latence, ...) c'est assez coûteux "
+"en temps CPU de construire un tunnel. C'est\n"
+"pourquoi il est seulement permis à une destination d'avoir un max de "
+"tunnels de transport de données de : 6 ENTRANTS et 6 SORTANTS. Avec un "
+"max de 50 Ko/sec par tunnel, une destination pourrait\n"
+"utiliser grossièrement 300 Ko/sec de trafic combiné (en réalité cela "
+"pourrait être davantage si des tunnels plus courts étaient utilisés avec "
+"un anonymat disponible bas ou nul).\n"
+"Les tunnels utilisés sont renoncés - mis au rebut - toutes les 10 minutes"
+" et de nouveaux sont créés.\n"
+"Ce changement de tunnels (et parfois des clients qui se ferment durement "
+"en raison de l'utilisation de l'\"arrêt immédiat\" ou des situations où "
+"il y a une perte d'alimentation électrique) fait\n"
+"parfois se produire des cassures de tunnels et de connexions, comme vu "
+"sur le réseau IRC2P dans perte de connexion (échéance de ping) ou durant "
+"utilisation de eepget."
+
+#: 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 ""
+"Avec un ensemble limité de destinations et un ensemble limité de tunnels "
+"par destination, un noeud I2P utilise seulement un ensemble limité de "
+"tunnels à travers d'autres noeuds I2P.\n"
+"Par exemple, si un noeud I2P est \"hop1\" dans le petit exemple ci-"
+"dessus, nous voyons seulement 1 tunnel participant provenant du client.\n"
+"Si nous résumons le réseau I2P entier, seul un nombre plutôt limité de "
+"tunnels participants pourrait être construit avec une quantité limitée de"
+" bande passante tous ensemble.\n"
+"Si on distribue ces nombres limités à travers le numéro de noeuds I2P, il"
+" y a seulement une fraction de bande passante/capacité disponible "
+"disponible pour utilisation."
+
+#: 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 ""
+"Pour garder l'anonymat un routeur ne devrait pas être utilisé par "
+"l'ensemble du réseau pour la construction de tunnels.\n"
+"Si un routeur agit comme un routeur de tunnel pour tous les nœuds de I2P,"
+" il devient un véritable point central de défaillance, ainsi qu'un point "
+"central pour récolter des adresses IP et des données des clients. Ce "
+"n'est pas bon.\n"
+"I2P tente de répartir la charge sur un grand nombre de nœuds I2P à cause "
+"de cette raison."
+
+#: 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 ""
+"Un autre point est le réseau complètement maillé. Chaque connexion "
+"saut-à-saut utilise une connexion TCP ou UDP sur les nœuds I2P. Avec 1000"
+" connexions, on voit\n"
+"1000 connexions TCP. C'est beaucoup et certains routeurs (DSL, câble, "
+"...) domestique ou de petit bureau permettent seulement un petit nombre "
+"de connexions (ou deviennent simplement fous si vous utilisez plus de X "
+"connexions.)\n"
+"I2P essaie de limiter le nombre de ces connexions pour être en dessous de"
+" 1500 par UDP et par type TCP.\n"
+"Ce qui limite la quantité de trafic acheminé à travers votre nœud I2P "
+"aussi."
+
+#: 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 ""
+"En résumé, I2P est très complexe et il n'y a aucune façon facile de "
+"définir exactement pourquoi votre noeud n'est pas utilisé.\n"
+"Si votre noeud est accessible et a un réglage de bande passante partagée "
+"> à 128 Ko/secondes et est accessible 24/7, il devrait être utilisé après"
+" quelque temps pour le trafic de participation. \n"
+"Si il est coupé (down) entre temps, le test de votre noeud I2P fait par "
+"d'autres noeuds le leur dira : vous n'êtes pas accessible. Cela bloque "
+"votre noeud sur d'autres noeuds pour au moins\n"
+"24h. Ainsi, les autres noeuds qui vous ont testé n'utiliseront pas votre "
+"noeud pour construire des tunnels durant 24h. C'est pourquoi votre trafic"
+"\n"
+"sera inférieur après une rédémarrage/arrêt durant un minimum de 24h."
+
+#: 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 ""
+"Aussi : les autres noeuds I2P doivent connaître votre routeur I2P pour "
+"tester son accessibilité et sa capacité. Cela prend du temps pour que les"
+" autres noeuds prennent connaissance de votre noeud.\n"
+"Cela sera plus rapide si vous utilisez I2P et construisez davantage de "
+"tunnels, par exemple utilisez un torrent ou www pendant quelque temps."
+
+#: i2p2www/pages/site/about/performance/index.html:99
+msgid "Performance Improvements"
+msgstr "Améliorations de performance"
+
+#: i2p2www/pages/site/about/performance/index.html:101
+#, python-format
+msgid ""
+"For possible future performance improvements see\n"
+"Future Performance Improvements."
+msgstr ""
+"Pour de possible futures améliorations de performance voir\n"
+"Améliorations de performance future."
+
diff --git a/i2p2www/translations/fr/LC_MESSAGES/blog.po b/i2p2www/translations/fr/LC_MESSAGES/blog.po
new file mode 100644
index 00000000..aeda4ba5
--- /dev/null
+++ b/i2p2www/translations/fr/LC_MESSAGES/blog.po
@@ -0,0 +1,1563 @@
+# French translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Boxoa590, 2013
+# magma , 2011
+# Towatowa441, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-12 06:16+0000\n"
+"PO-Revision-Date: 2013-12-12 06:18+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: French "
+"(http://www.transifex.com/projects/p/I2P/language/fr/)\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/blog/2011/10/11/0.8.9-Release.rst:24
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:25
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:12
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:12
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:17
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:16
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:16
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:26
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:19
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:19
+msgid "Files are available on the `download page`_."
+msgstr "Les fichiers sont disponibles sur la `download page`_."
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:28
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:15
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:29
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:16
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:16
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:21
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:20
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:20
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:30
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:23
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:23
+msgid "`download page`"
+msgstr "`download page`"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:30
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:17
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:31
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:18
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:19
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:18
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:22
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:22
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:32
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:25
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:79
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:45
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:13
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:101
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:26
+msgid "RELEASE DETAILS"
+msgstr "DETAILS SUR CETTE VERSION"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:32
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:19
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:33
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:40
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:50
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:24
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:24
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:34
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:103
+msgid "Major Changes"
+msgstr "Changements majeurs"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:44
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:24
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:43
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:55
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:47
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:58
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:43
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:32
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:30
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:39
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:81
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:54
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:112
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:34
+msgid "Bug Fixes"
+msgstr "Corrections de bugs"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:54
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:30
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:47
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:69
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:63
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:68
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:54
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:41
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:36
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:51
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:43
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:94
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:63
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:19
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:118
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:52
+msgid "Other"
+msgstr "Autre"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:73
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:36
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:51
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:82
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:75
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:96
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:76
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:52
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:56
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:67
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:56
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:110
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:79
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:30
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:129
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:27
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:76
+msgid "SHA256 Checksums:"
+msgstr "Sommes de contrôle SHA256 :"
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39
+msgid "Major changes"
+msgstr "Changements majeurs"
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47
+msgid "Wrapper Update"
+msgstr "Mise à jour du wrapper"
+
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:23
+msgid "Update Info"
+msgstr "Info de mise à jour"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2
+msgid "0.9.2 Release"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9
+msgid ""
+"0.9.2 includes extensive low-level changes to improve the performance and"
+" efficiency of the router. We have updated our UPnP library, to hopefully"
+" make UPnP work for more people. I2PSnark now has DHT support, but it is "
+"not yet enabled by default, as we plan to do more testing during the "
+"upcoming 0.9.3 development cycle."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12
+msgid ""
+"As usual, there's also lots of bug fixes in this release, so updating is "
+"recommended."
+msgstr ""
+"Comme d'habitude, il ya aussi beaucoup de corrections de bugs dans cette "
+"version, alors il est recommandé d'effectuer la mise à jour."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26
+msgid ""
+"SSU: Fix several problems in our UDP transport, to improve efficiency and"
+" reliability for connection setup. Also improve defenses against various "
+"types of bad input."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27
+msgid ""
+"UPnP: Updated our library to fix several issues, should work for more "
+"routers now"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28
+msgid ""
+"Transport: Improve performance in both our TCP and UDP transports, to "
+"benefit high-bandwidth routers"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29
+msgid ""
+"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered "
+"are now much more flexible, which should lessen protocol overhead and "
+"reduce stalls caused by dropped tags."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30
+msgid ""
+"I2PSnark: Add DHT support, not yet enabled by default, will do further "
+"testing and plan to enable by default in 0.9.3."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34
+msgid ""
+"Fix various issues affecting memory usage and performance on high-"
+"bandwidth routers"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35
+msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36
+msgid "Fix i2psnark bug that prevented a completion announcement to the tracker"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37
+msgid "Fix a lock contention problem in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38
+msgid "Fix some OSX installation issues"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39
+msgid "Remove uses of direct byte buffers that may have been leaking"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43
+msgid "Reduce overhead in network messages"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44
+msgid "Add \"universal\" theme support"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45
+msgid "Theme updates"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46
+msgid "Add a jbigi library for Raspberry Pi"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47
+msgid "New Scala unit test framework"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48
+msgid "Translation updates for Czech, Dutch, German, and Greek"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49
+msgid "Update wrapper to 3.5.15 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:77
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:127
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:74
+msgid "Update GeoIP data (new installs and PPA only)"
+msgstr "Mise à jour données GeoIP (nouvelles installations et PPA seulement)"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:2
+msgid "0.9.3 Release"
+msgstr "Release 0.9.3"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9
+msgid ""
+"0.9.3 includes extensive low-level changes to the queueing of messages in"
+" the router.  We implement the CoDel Active Queue Management (AQM) "
+"algorithm.  We also unify the queueing and priority mechanisms in the "
+"transports to aid diagnosis and reduce network latency.  Work continues "
+"on fixing UDP transport bugs and making UDP more resistant to attacks.  "
+"There are more changes to improve the performance of the router and "
+"reduce its memory usage.  Also, we enable i2psnark's DHT support, "
+"introduced last release, by default."
+msgstr ""
+"0.9.3 inclut de vastes changements de bas niveau de la file d'attente de "
+"messages dans le routeur. Nous mettons en oeuvre l'algorithme CODEL "
+"Active Queue Management (AQM). Nous unissons aussi la queue et mécanismes"
+" de priorité dans les transports pour faciliter le diagnostic et de "
+"réduire la latence du réseau. Les travaux se poursuivent sur ​​la "
+"résolution de bogues de transport UDP et rendre UDP plus résistant aux "
+"attaques. Il n'y a plus de changements pour améliorer les performances du"
+" routeur et réduire son utilisation de la mémoire. En outre, nous "
+"activons dans  i2psnark le support de DHT, introduit dans la dernière "
+"version, par défaut."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26
+msgid "Active Queue Management"
+msgstr "Gestion de la file d'attente active"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:27
+msgid "Priority queues"
+msgstr "Priorités files d'attente"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28
+msgid "I2PSnark DHT: Several bug fixes, enable by default."
+msgstr "I2PSnark DHT : plusieurs corrections de bugs, activée par défaut."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32
+msgid ""
+"Several SSU fixes including memory leak, and better handling of routers "
+"behind firewalls that change UDP ports; additional defenses for malicious"
+" packets."
+msgstr ""
+"Plusieurs corrections dans SSU incluant fuite de mémoire, et une "
+"meilleure gestion des routeurs derrière les pare-feux qui changent les "
+"ports UDP; défenses supplémentaires contre les paquets malveillants."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33
+msgid "Fix piece selection (rarest-first) bugs in i2psnark"
+msgstr "Résolu bugs sélection de tronçons (le plus rare le premier) dans i2psnark"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34
+msgid "Fix bug causing multiple browsers to open at startup"
+msgstr ""
+"Correction d'un bug causant l'ouverture de multiples navigateurs au "
+"démarrage"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38
+msgid "Improvements in caching"
+msgstr "Amélioration de la mise en cache"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39
+msgid "Several synchronization fixes and lock contention reduction"
+msgstr ""
+"Plusieurs corrections de synchronisation de et réduction de la contention"
+" de verrouillage"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40
+msgid "Major reduction in SSU buffers memory use"
+msgstr "Réduction importante de l'utilisation de mémoire des buffers SSU"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41
+msgid ""
+"Fix streaming connection timeout back to 1 minute, was inadvertently "
+"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was"
+" unlimited"
+msgstr ""
+"Corrigé le timeout de connexion streaming à 1 minute, qui avait été été "
+"modifié par inadvertance à 5 minutes; mise le timeout de lecture de "
+"serveur i2ptunnel à 5 minutes, il était illimité"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42
+msgid "Improved defenses in i2ptunnel for \"darkloris\""
+msgstr "Amélioration des défenses dans i2ptunnel pour \"darkloris\""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:43
+msgid "More validation at torrent creation in i2psnark"
+msgstr "Davantage de validation lors de la création de torrent dans i2psnark"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44
+msgid "Several parameter changes in SSU to improve throughput"
+msgstr "Plusieurs changements de paramètres dans SSU pour améliorer le débit"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45
+msgid ""
+"New event log for major events including restarts; show multiple restart "
+"lines on graphs"
+msgstr ""
+"Nouveau journal d'événements pour les événements majeurs, y compris ceux "
+"incluant des redémarres, montre sur les graphes plusieurs lignes de "
+"redémarrage"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46
+msgid "Remove duplicate messages from logs"
+msgstr "Suppression des doublons de messages depuis les logs"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47
+msgid "Don't respond to blocked streaming connections with a reset, just drop"
+msgstr ""
+"Ne répond par un reset pas aux connexions streaming bloquées, abandonne "
+"simplement"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48
+msgid "Remove all uses of inefficient SimpleTimer"
+msgstr "Retire toutes les utilisations inefficaces de SimpleTimer"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49
+msgid "More checks for valid IPs and ports entered in console"
+msgstr ""
+"Davantage de contrôles de la validité des IP et des ports entrés dans la "
+"console"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50
+msgid "Fix bug that wasted a lot of entropy"
+msgstr "Correction d'un bug qui a gaspillé beaucoup d'entropie"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51
+msgid "Translation updates: Italian, Portuguese, Spanish, Swedish"
+msgstr "Mises à jour de traduction : Italien, Portugais, Espagnol, Suédois"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52
+msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5"
+msgstr "Ajoute configuration non-NIO dans jetty.xml, recommandé pour Java 5"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2
+msgid "0.9.4 Release"
+msgstr "Release 0.9.4"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9
+msgid ""
+"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, "
+"that was reducing network performance and reliability. It also includes "
+"major changes in the in-network update system, and adds the capability to"
+" update via in-network torrents."
+msgstr ""
+"0.9.4 inclue un correctif pour un bug de capacité du réseau, introduit "
+"dans la 0.9.2, qui a réduit les performances et la fiabilité du réseau. "
+"Il comprend également des changements majeurs dans le système de mise à "
+"jour en réseau, et ajoute la possibilité de mettre à jour en réseau via "
+"des torrents."
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13
+msgid ""
+"We fixed several bugs in the i2psnark DHT implementation that was "
+"introduced\n"
+"last release. For those of you using console or http proxy passwords,\n"
+"we converted to the more-secure digest method and improved the security "
+"for console forms."
+msgstr ""
+"Nous avons corrigé plusieurs bugs dans la mise en œuvre de DHT i2psnark "
+"qui ont été introduits ⏎\n"
+"depuis la dernière version. Pour ceux d'entre vous qui utilisent la "
+"console ou des mots de passe de proxy HTTP, ⏎  nous avons converti à la "
+"méthode digest plus sécurisé, et amélioré la sécurité des formulaires de "
+"la console."
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19
+msgid ""
+"For those of you already running development builds, your router should "
+"automatically\n"
+"update to 0.9.4-0 using the new in-network torrent facility.\n"
+"For those running 0.9.3-0, you will update normally using in-network "
+"HTTP, and\n"
+"we will have more information for you when we release 0.9.5."
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36
+msgid ""
+"Big rework of the update system; Preliminary support for updates via "
+"i2psnark"
+msgstr ""
+"Gros remaniement du système de mise à jour; Support préliminaire pour les"
+" mises à jour via i2psnark"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37
+msgid "Add per-destination outbound priorities"
+msgstr "Ajouter de priorités sortantes par destination"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41
+msgid ""
+"Fix major bug that reduced SSU connection limits which reduced tunnel "
+"build success rates"
+msgstr ""
+"Résolu bug majeur that réduisait les limites de connexion SSU ce qui "
+"réduisait le taux de succès de construction de tunnel"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42
+msgid "Fix bug with external I2CP that prevented some external apps from working"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43
+msgid "Fixed several bugs in i2psnark DHT"
+msgstr "Correction de plusieurs bugs dans i2psnark DHT"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44
+msgid "Fixed bug in i2psnark PEX that inflated peer counts"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45
+msgid "Handle dropped I2CP messages better"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46
+msgid "Reduce overhead of I2CP messages"
+msgstr "Reduit l'entête des messages I2CP"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47
+msgid "Enforce max size in transport outbound message queues"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48
+msgid "Fixes for Windows eepget.bat (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49
+msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53
+msgid ""
+"More performance improvements, memory reduction, and object churn "
+"reduction"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54
+msgid "Better detection of network disconnections"
+msgstr "Meilleure détection des déconnexions réseau"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55
+msgid "Further improvements in the SSU transport"
+msgstr "D'autres améliorations dans le transport SSU"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56
+msgid "Add console password form"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57
+msgid ""
+"Convert http proxy and console from basic to digest authentication for "
+"added security"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58
+msgid ""
+"Improved verification of console form submissions, using jsp sessions. "
+"Cookies may now be required on forms, except when the console password is"
+" enabled"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59
+msgid ""
+"Initial work on new interfaces to manage applications started via "
+"clients.config"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60
+msgid "Increase minimum peer port to 1024"
+msgstr "Augmente le port minimum de port de pair à 1024"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61
+msgid "Increase granularity of bandwidth limiter for smoother transmissions"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62
+msgid ""
+"Translation updates: Chinese, French, German, Italian, Polish, "
+"Portuguese, Swedish, and Ukrainian"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64
+msgid "Update wrapper to 3.5.16 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65
+msgid "New ARMv6 wrapper for Raspberry Pi"
+msgstr "Nouveau wrapper ARMv6 pour Raspberry Pi"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:2
+msgid "0.9.5 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9
+msgid ""
+"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities"
+" that are being investigated by researchers at UCSB. We continue to work "
+"with them on additional improvements. This is a good opportunity to "
+"remind the community that while our network continues to grow rapidly, it"
+" is still relatively small. There may be multiple weaknesses or bugs that"
+" could compromise your anonymity. Help us grow the network by spreading "
+"the word and contributing where you can."
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13
+#, python-format
+msgid ""
+"In this upgrade cycle, a random 1% of routers, (plus all routers running "
+"a\n"
+"development build) will attempt to update via the experimental in-network"
+" bittorrent\n"
+"with i2psnark. If this doesn't work, it should fall back to standard in-"
+"network HTTP update."
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27
+msgid "Defenses and Bug Fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29
+msgid "Fix router bug causing lockup when using iMule"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30
+msgid "Recognize, handle, reject duplicate tunnel IDs"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31
+msgid "Fix changing of the log file name"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32
+msgid "Prevent hashcode attack in session tags"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33
+msgid "Add build request throttler based on previous hop"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34
+msgid "Limit concurrent next-hop lookups"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35
+msgid "Catch exceptions storing nonces in console"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36
+msgid "Fix saving graph settings in console"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37
+msgid "Fix eepget generation of URLs when not proxied"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38
+msgid ""
+"Encrypt database lookup messages end-to-end when sent through exploratory"
+" tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39
+msgid "Don't use multiple floodfills from the same /16 in a query"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40
+msgid "Randomize delay before verifying floodfill store"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41
+msgid "Increase number of floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:45
+msgid "Improve support for mobile browsers"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46
+msgid "Partial defenses for UCSB attacks"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47
+msgid "Add announce list support to i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48
+msgid "Jetty: upgrade Apache Tomcat to 6.0.36"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49
+msgid "Split router info files into multiple subdirectories"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50
+msgid "Add IP to hostname mapping option in SOCKS"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51
+msgid "Improve PRNG seeding"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52
+msgid ""
+"Translation updates: French, German, Hungarian, Italian, Norwegian, "
+"Polish, Portuguese, Russian, Swedish"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54
+msgid "Update wrapper to 3.5.17 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:2
+msgid "0.9.6 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:7
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9
+msgid ""
+"0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to "
+"Jetty 7.6.10 (2013-03-12). See below for important information on the "
+"Jetty update. The Jetty 7 series is actively maintained and we plan to "
+"stay current with it in future I2P releases."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13
+msgid ""
+"Most users will update via HTTP. Those running development builds will "
+"attempt to update via the\n"
+"experimental in-network bittorrent with i2psnark. We've fixed some bugs "
+"that will enable more users\n"
+"to update via torrent in the 0.9.7 update cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25
+msgid "Important fix for Windows Eepsites, first install 0.9.5 only"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27
+msgid ""
+"If you first installed I2P with version 0.9.5, on Windows only, we "
+"recommend that you follow the\n"
+"following instructions to fix your eepsite location **before** you update"
+" to 0.9.6.\n"
+"Only original installations of 0.9.5-0 on Windows are affected by this "
+"issue. If your router version\n"
+"is 0.9.5-0-win1, you already have the fix and need not take any action."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34
+msgid "See `this page`_ for instructions."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:38
+msgid "`this page`"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:40
+msgid "Jetty 7 Migration Details"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42
+msgid ""
+"For most people, the update should just work. If you have multiple Jetty "
+"eepsites,\n"
+"OR have made changes to jetty.xml or other Jetty configuration files, "
+"including changing the port\n"
+"from 7658, you MUST take manual action AFTER updating."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48
+msgid ""
+"After update, the router will migrate your jetty.xml files to the new "
+"Jetty 7 format."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50
+msgid ""
+"The migration resets the port to 7658. If you have more than one Jetty "
+"eepsite, OR your eepsite\n"
+"  is NOT on port 7658, OR you have made other modifications to jetty.xml "
+"(for example changing the\n"
+"  listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml "
+"file for each eepsite to fix them up\n"
+"  after updating, and restart again."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55
+msgid ""
+"**The following files will be backed up with a ".jetty6" suffix"
+" and then migrated.**\n"
+"If you have made local changes, you may have to edit them manually and "
+"restart.\n"
+"See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69
+msgid "Plugins"
+msgstr "Plugins"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:71
+msgid "Most plugins should work fine with Jetty 7."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:75
+msgid ""
+"The I2PControl and zzzot plugins must be updated. Your router should "
+"download and install the new versions shortly after starting 0.9.6."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77
+msgid "If a plugin does not work, please contact the maintainer for that plugin."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83
+msgid "Several bugs with Windows installation (see above)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:84
+msgid "Fix default form action in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85
+msgid "Fix links on iframed console pages"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86
+msgid "Better detection of 64-bit Windows to prevent crashes by systray"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87
+msgid "Fix bug preventing router update via torrent"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88
+msgid "Several SSU fixes for NATs that change UDP ports"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89
+msgid ""
+"Ignore unsupported IPs in RouterInfos when selecting an address (prep for"
+" IPv6)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90
+msgid ""
+"Ignore unused option bits in Database Lookup Message (prep for requesting"
+" encrypted response)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91
+msgid "Fix HTTP proxy error response for malformed URIs"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92
+msgid "Recognize UPnP devices without port forwarding capability"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96
+msgid "Jetty 7.6.10 (see above for migration information)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97
+msgid "Limit page size in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98
+msgid "Add data directory and page size configuration to i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99
+msgid "Support multiple i2psnark instances"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100
+msgid "Piece size adjustments in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101
+msgid "Add more graphing support for combined bandwidth graph"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102
+msgid "Block b32.i2p supercookies"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103
+msgid "Allow stopping clients on /configclients"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104
+msgid "Check for nonce count replays in HTTP client"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105
+msgid "Support SASL authentication in IRC proxy"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106
+msgid "Several cleanups and minor fixes in the update manager"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107
+msgid "Translation updates: German, Portuguese, Russian, Spanish, and Swedish"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:2
+msgid "0.9.7 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:7
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:9
+msgid "0.9.7 includes significant bug fixes and improvements."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:11
+msgid ""
+"For the first time, class 'N' routers (those with a minimumum of 128 "
+"KBytes/sec of shared bandwidth)\n"
+"will automatically become floodfill (previously it was only 'O' routers "
+"with 256 KBps). This will\n"
+"increase the floodfill population for additional resistance to certain "
+"attacks (see below). Floodfill routers\n"
+"don't consume much additional bandwidth, but they do tend to use "
+"additional memory and concurrent\n"
+"connections. If you do not wish your router to become floodfill, set the "
+"advanced configuration\n"
+"router.floodfillParticipant=false ."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:20
+#, python-format
+msgid ""
+"As we think the last release fixed the experimental update-via-torrent "
+"bugs, 3% of routers should\n"
+"update over in-network bittorrent this cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:25
+msgid ""
+"Plugin update checks, possibly broken for several releases, are fixed. "
+"Your plugins should once again\n"
+"auto-update after updating the router."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:30
+msgid ""
+"We fixed a major streaming timer bug that contributed to frequent IRC "
+"disconnects."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:34
+msgid ""
+"This release contains additional mitigations for the `\"practical "
+"attacks\" paper`_.\n"
+"However, we have a lot more work to do to resist Sybil attacks on the "
+"floodfills, and resist\n"
+"traffic analysis at the gateways and endpoints of exploratory tunnels.\n"
+"It's a good reminder for everybody that our network is still relatively "
+"small and vulnerable.\n"
+"We don't currently recommend any uses that would put anybody in serious "
+"jeopardy.\n"
+"We'll keep working to improve it... please keep working to spread the "
+"word. A bigger network is a better network."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:43
+msgid "`\"practical attacks\" paper`"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:47
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:15
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:107
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:28
+msgid "Anonymity Improvements"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:49
+msgid "End-to-end encryption of responses to leaseset lookups"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:50
+msgid "Expand floodfill pool by enabling class 'N' floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:51
+msgid "Randomize padding inside encrypted SSU packets"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:52
+msgid "Preparation for better SSU protocol obfuscation"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:56
+msgid "Fix newer lease sets not getting stored or published"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:57
+msgid ""
+"Fix classpath bug when used with 4-year-old installations, causing the "
+"console not to start"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:58
+msgid "Fix addressbook database bug preventing update of the reverse index"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:59
+msgid ""
+"Fix i2psnark bug that changed the infohash of torrents created by Robert "
+"and fetched via magnet link"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60
+msgid "Fix version checking for plugins"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:61
+msgid ""
+"Fix a streaming timer bug causing frequent IRC disconnects (also affects "
+"other close-on-idle tunnels)"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:65
+msgid "Don't install as a service on Windows by default"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:66
+msgid "Reduce transport idle timeouts"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:67
+msgid "Reduce tunnels on idle in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:68
+msgid "Change default in i2ptunnel GUI to 3 hops"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:69
+msgid "IE 10 support"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70
+msgid ""
+"Individual expiration times in leases, for efficiency on destinations "
+"with a high number of tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71
+msgid "Low-level encryption and XOR speedups"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:72
+msgid "Jetty 7.6.11"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:73
+msgid "Tomcat 6.0.37"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74
+msgid "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75
+msgid "New Turkish translation"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:76
+msgid "Wrapper 3.5.19 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:2
+msgid "0.9.7.1 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:7
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:9
+msgid ""
+"This unscheduled release disables the RouterInfo verification messages "
+"that were used in the attack published in the UCSB paper, which should "
+"make correlating a LeaseSet and a Router much more difficult. We have "
+"also included a limited number of other fixes listed below. Our 0.9.8 "
+"release, which will include IPv6 support, is still on-schedule for late "
+"September."
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:11
+msgid "As usual, we recommend that all users update to this release."
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:17
+msgid "Disable RouterInfo verification messages"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:21
+msgid "Extend inbound tunnel expiration"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:22
+msgid "i2prouter: bashism fix"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:23
+msgid "i2psnark: increase max piece size, mime type updates"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:24
+msgid "New reseed host"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:25
+msgid "New update hosts, thanks Meeh and dg"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:26
+msgid "Streaming: RTO changes"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:27
+msgid "Updater: Increase update-via-torrent to 30 percent"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:28
+msgid "UPnP fix for some hardware"
+msgstr "Corrections UPnP pour certains matériels"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:2
+msgid "0.9.8 Release"
+msgstr "Sortie 0.9.8"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9
+msgid ""
+"0.9.8 includes the long-awaited support for IPv6. It's enabled by "
+"default, but of course you need a public IPv6 address to use it. "
+"Configuration is on the 'network' configuration tab in your console. We "
+"also have anonymity improvements including padding of SSU packets and "
+"longer router private keys."
+msgstr ""
+"0.9.8 inclut le soutien pour IPV6 attendu depuis longtemps. Il est activé"
+" par défaut, mais bien sûr vous avez besoin d'une adresse publique IPv6 "
+"pour l'utiliser. La configuration est dans l'onglet de configuration "
+"'réseau' de votre console. Nous avons aussi des améliorations d'anonymat "
+"incluant le remplissage de paquets SSU et de plus longues clés privées de"
+" routeur."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11
+#, python-format
+msgid "30% of you will update via in-network torrent in this update cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13
+msgid "IPv6 Details"
+msgstr "Détails IPv6"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15
+msgid ""
+"IPv6 is enabled and preferred by default. If you have a public IPv6 "
+"address \n"
+"and you are connecting to another router with a published IPv6 address, "
+"it will \n"
+"connect via IPv6. There is a new IPv6 configuration section on /confignet"
+" in \n"
+"the router console. If IPv6 is causing problems you may disable it there."
+msgstr ""
+"IPv6 est activé et préféré par défaut. Si vous avez une adresse publique "
+"IPv6\n"
+"et que vous vous connectez à un autre routeur avec une adresse IPv6 "
+"publiée, il sera\n"
+"connecté via IPv6. Il y a une nouvelle section de configuration IPv6 sur "
+"/confignet dans\n"
+"la console de routeur. Si IPv6 cause des problèmes vous pouvez le mettre "
+"hors de service là."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22
+msgid ""
+"As a part of the IPv6 development effort, I2P now supports multiple \n"
+"published IP addresses. If you have multiple public IP addresses (IPv4, "
+"IPv6, \n"
+"or both), you may enable or disable them individually on /confignet. The"
+" \n"
+"default is to use the first IPv4 and IPv6 addresses it discovers. If you "
+"have \n"
+"multiple addresses you should review the configuration on /confignet and "
+"adjust \n"
+"it if necessary.\n"
+"Note that while you may enable multiple IPv4 and IPv6 addresses on "
+"/confignet,\n"
+"we recommend that you use only one IPv4 and one IPv6 address. There are\n"
+"bugs still to be fixed with multiple addresses of each type."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34
+msgid ""
+"While IPv6 support was designed and developed over several years, it has"
+" \n"
+"only been tested by a limited number of users and is still beta. If you "
+"do have \n"
+"a public IPv6 address, please monitor your router and the logs for "
+"problems, \n"
+"and disable it necessary. Please report any bugs on \n"
+"http://trac.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:42
+msgid "Rekeying Details"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44
+msgid ""
+"For those of you running I2P on faster hardware (generally, 64-bit x86) "
+"the \n"
+"router will generate a new identity using longer keys. This will "
+"substantially \n"
+"reduce your participating traffic for 48 hours or more, while your router"
+" \n"
+"re-integrates into the network. Due to the new keys, the large number of"
+" \n"
+"torrent updates, and the recent network growth, we expect substantial \n"
+"disruption to the network for a week or more after the update is "
+"released. \n"
+"Please be patient and things should start to improve after a few days."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54
+msgid ""
+"These changes may result in higher CPU usage for some of you. We're doing"
+" \n"
+"our best to increase efficiency, but stronger security generally requires"
+" more \n"
+"computation. Performance may also be poor during the first week\n"
+"due to the network churn.\n"
+"We will evaluate the network performace before deciding whether to\n"
+"change the key length on slower hardware in a future release."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63
+msgid ""
+"We are experiencing rapid network growth in the last few weeks, which is"
+" \n"
+"causing a bit of a bumpy ride for some, especially on weekends. However, "
+"the \n"
+"network is still performing fairly well, so keep spreading the word."
+msgstr ""
+"Nous éprouvons une croissance du réseau au cours des dernières semaines, "
+"ce qui cause un peu cahoteux pour certains, particulièrement les week-"
+"ends. Cependant, le réseau fonctionne toujours assez bien, donc continuez"
+" à passer le mot."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69
+msgid "More Changes Coming"
+msgstr "Changements majeurs à venir"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:71
+msgid ""
+"We're in the initial stages of desiging major changes to strengthen our \n"
+"crypto. Stronger crypto will use more CPU and it may possibly \n"
+"require a Java 7 JRE at a minimum. We understand your desire to run I2P "
+"on low-power \n"
+"and/or older hardware. We're working hard to minimize the impacts, but "
+"some \n"
+"loss of performance is inevitable. In addition, Java 5 and 6 are no "
+"longer \n"
+"supported by Oracle. Now is a good time to upgrade to Java 7. Any change "
+"in \n"
+"minimum requirements will be announced well in advance."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:81
+msgid "New Website"
+msgstr "Nouveau site web"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:83
+msgid ""
+"After a heroic effort by str4d, the new website preview is available at \n"
+"http://i2hq.srv.i2p2.de. We hope to see it go live at \n"
+"https://geti2p.net and http://www.i2p2.i2p soon.  Please \n"
+"contribute to the new website translations on Transifex, especially the \n"
+"website_priority resource."
+msgstr ""
+"Après un effort héroïque par str4d, la prévisualisation du nouveau site "
+"Web est disponible à http: // i2hq.srv.i2p2.de. Nous espérons le voir "
+"vivant à https: //geti2p.net et http://www.i2p2.i2p bientôt. S'il vous "
+"plaît contribuez aux traductions d nouveau site Web sur Transifex, "
+"particulièrement la ressource website_priority."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91
+msgid "Community Participation"
+msgstr "Participation communauté"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:93
+msgid ""
+"In early August, hottuna and zzz attended DEFCON 21 in Las Vegas.\n"
+"Last weekend, echelon attended the CTS IV conference in Berlin and\n"
+"psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass.\n"
+"Several of us will be at 30C3 in Hamburg late this year.\n"
+"It's great to see people participating at these events and representing "
+"I2P."
+msgstr ""
+"Début août, hottuna et zzz ont assisté au DEFCON 21 à Las Vegas. \n"
+"Le dernier week-end, echelon a assisté à la conférence  CTS IV à Berlin "
+"et\n"
+"psi a assisté au hackfest Tahoe-LAFS au GNOU 30 à Cambridge, Mass.\n"
+"Plusieurs d'entre nous seront au 30C3 à Hambourg vers la fin de cette "
+"année. \n"
+"C'est super de voir des gens participer à ces événements et représenter "
+"I2P."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105
+msgid "IPv6 support for both NTCP and SSU"
+msgstr "Soutient IPv6 pour à la fois NTCP et SSU"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:109
+msgid "SSU protocol obfuscation by adding random padding"
+msgstr "Obscurcissement de protocole SSU par ajout de remplissage aléatoire"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110
+msgid "Longer encryption and DH private keys for users on faster platforms"
+msgstr ""
+"Chiffrage plus long et clés privées DH pour utilisateurs sur plates-"
+"formes plus rapides"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114
+msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)"
+msgstr "Répare I2PTunnel / verrouillage I2CP et duplicatas (partiel)"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:115
+msgid "Fix translation of HTTP proxy error pages"
+msgstr "Corrige les traductions des pages d'erreur de proxy HTTP"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:116
+msgid "Fix occasional runtime exception in NTCP"
+msgstr "Répare une exception occasionnelle de runtime dans NTCP"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120
+msgid "Big rework of transport code to accommodate multiple addresses and IPv6"
+msgstr ""
+"Grand re-travail du code de transport afin de s'accommoder des adresses "
+"multiples et de IPv6"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121
+msgid "Streaming: Improved recovery from lost acks, other fixes"
+msgstr "Streaming : rétablissement amélioré des acks perdus, d'autres corrections"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122
+msgid "Use Transifex for translation of initial news and HTTP proxy error pages"
+msgstr ""
+"Utilise Transifex pour la traduction des nouvelles initiales et des pages"
+" d'erreur de proxy HTTP"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123
+msgid ""
+"Translation updates: Chinese, French, German, Portuguese, Russian, "
+"Swedish, Turkish"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124
+msgid "New Romanian translation"
+msgstr "Nouvelle traduction Roumaine"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:126
+msgid "Wrapper 3.5.20 (new installs and PPA only)"
+msgstr "Wrapper 3.5.20 (nouvelles installations et PPA seulement)"
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:2
+msgid "0.9.8.1 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:7
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:9
+msgid ""
+"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some "
+"people. New installs and non-Windows platforms are not affected, however "
+"all platforms will automatically update even if running 0.9.8."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:11
+msgid ""
+"See the `Trac ticket`_ for details and workarounds. See\n"
+"`the 0.9.8 release notes`_ for information on IPv6 and other changes."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:16
+msgid ""
+"Due to recent attacks, logins are disabled on `Trac`_ and new "
+"registrations are\n"
+"disabled on `zzz.i2p`_. Until those services are restored, please report "
+"all\n"
+"bugs on IRC freenode or IRC2P #i2p-dev."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:22
+msgid "`Trac ticket`"
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:23
+msgid "`the 0.9.8 release notes`"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:2
+msgid "0.9.9 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:7
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:9
+msgid ""
+"0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and "
+"starts work on a year-long plan to increase the strength of the "
+"cryptographic signing algorithms used in the router, and support multiple"
+" algorithms and key lengths simultaneously. Automatic update files will "
+"now be signed with 4096-bit RSA keys."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:11
+msgid ""
+"We now support SSL between your router and your servers for security.\n"
+"See `this development thread`_ for more information."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:16
+msgid "`this development thread`"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:18
+msgid ""
+"As usual, we recommend that you update to this release.\n"
+"The best way to maintain security and help the network is to run the "
+"latest release.\n"
+"Several members of the I2P team will be at 30C3 in Hamburg this year.\n"
+"Come say hello and ask for an I2P sticker.\n"
+"Thanks to everyone for their support this year."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:30
+msgid "Don't build client tunnels through zero-hop exploratory tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:31
+msgid "New \"su3\" file support using stronger keys"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:32
+msgid "Use su3 for updates"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:36
+msgid "Issues with losing data when closing streams"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:37
+msgid "Fix various streaming connection limit issues"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:38
+msgid "Issues with resource usage of closed connections"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:39
+msgid "Clean up timer threads in close-on-idle tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:40
+msgid "Several other streaming fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:41
+msgid "Reject more non-public IPv6 addresses"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:42
+msgid "Fix IPv6 GeoIP"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:43
+msgid "Fix peer selection in first minutes after startup"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:44
+msgid "Several I2PTunnel bug fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:45
+msgid "Fix major i2psnark DHT bug that prevented magnets from working well"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:46
+msgid ""
+"Fix client tunnels that fail due to name resolution failure at startup, "
+"particularly with b32 hostnames"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:47
+msgid "Fix changing client i2ptunnel target list"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:48
+msgid ""
+"Fix major bugs preventing reception of encrypted responses to leaseset "
+"lookups and verifies"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:49
+msgid "Fix bad links on some i2psnark buttons in Opera and text-mode browsers"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:50
+msgid "Fix NPE in Susimail"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:54
+msgid "Start work on supporting stronger signing keys in the router"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:55
+msgid "Reduce thread usage for HTTP Server tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:56
+msgid "Auto-stop update torrent after some time"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:57
+msgid "Add ability to stop webapp via console"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:58
+msgid "New POST throttler in HTTP server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:59
+msgid "Improve connection throttling"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:60
+msgid "More work to reduce number of connections"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:61
+msgid "Re-enable router info expiration job"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:62
+msgid ""
+"Extend router info expiration and other changes to reduce load on "
+"floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:63
+msgid "Support multiple servers through a single server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:64
+msgid "Support specification of server port in i2ptunnel clients"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:65
+msgid "Add support for SSL connections from i2ptunnel to external server"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:66
+msgid "SSL and crypto code refactoring"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:67
+msgid "i2psnark storage code refactoring"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:68
+msgid "New destination cache"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:69
+msgid "Lots of code cleanup and resolution of findbugs warnings"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:70
+msgid "New Japanese translation (partial)"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:71
+msgid ""
+"Translation updates: French, German, Italian, Romanian, Russian, Spanish,"
+" Swedish, and others"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:73
+msgid "Wrapper 3.5.22 (new installs and PPA only)"
+msgstr ""
+
diff --git a/i2p2www/translations/fr/LC_MESSAGES/comparison.po b/i2p2www/translations/fr/LC_MESSAGES/comparison.po
new file mode 100644
index 00000000..d2cf929e
--- /dev/null
+++ b/i2p2www/translations/fr/LC_MESSAGES/comparison.po
@@ -0,0 +1,933 @@
+# French translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Boxoa590, 2013
+# magma , 2011
+# syl_, 2013
+# Towatowa441, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-10-26 22:39+0000\n"
+"PO-Revision-Date: 2013-10-03 08:17+0000\n"
+"Last-Translator: Towatowa441\n"
+"Language-Team: French "
+"(http://www.transifex.com/projects/p/I2P/language/fr/)\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/comparison/freenet.html:2
+msgid "I2P Compared to Freenet"
+msgstr "I2P comparé à Freenet"
+
+#: i2p2www/pages/site/comparison/freenet.html:8
+msgid ""
+"Freenet is a fully distributed, peer to peer anonymous publishing "
+"network, offering \n"
+"secure ways to store data, as well as some approaches attempting to "
+"address the loads\n"
+"of a flash flood.  While Freenet is designed as a distributed data store,"
+" people have\n"
+"built applications on top of it to do more generic anonymous "
+"communication, such as \n"
+"static websites and message boards."
+msgstr ""
+"Freenet est entièrement distribué, c'est un réseau pair to pair de "
+"publication anonyme, offrant\n"
+"des moyens sûrs pour stocker des données, ainsi que des approches qui "
+"tentent de répondre aux charges\n"
+"d'une crue éclair. Alors que Freenet est conçu comme un magasin de "
+"données distribuées, des gens ont\n"
+"construit des applications par dessus celui-ci afin de faire de la "
+"communication anonyme plus générique, tels\n"
+"que des sites web statiques et des forums électroniques."
+
+#: i2p2www/pages/site/comparison/freenet.html:16
+#, python-format
+msgid ""
+"Compared to I2P, Freenet offers some substantial benefits - it is a "
+"distributed data\n"
+"store, while I2P is not, allowing people to retrieve the content "
+"published by others \n"
+"even when the publisher is no longer online.  In addition, it should be "
+"able to \n"
+"distribute popular data fairly efficiently.  I2P itself does not and will"
+" not provide \n"
+"this functionality.  On the other hand, there is overlap for users who "
+"simply want to \n"
+"communicate with each other anonymously through websites, message boards,"
+" file sharing\n"
+"programs, etc.  There have also been some attempts to develop a "
+"distributed data \n"
+"store to run on top of I2P,\n"
+"(most recently a port of Tahoe-LAFS)\n"
+"but nothing is yet ready for general use."
+msgstr ""
+"Comparé à I2P, Freenet offre des avantages considérables - c'est un "
+"magasin de données distribuées,\n"
+"tandis que I2P ne l'est pas, ce qui permet aux gens de récupérer les "
+"contenus publiés par les autres\n"
+"même lorsque l'éditeur n'est plus en ligne. En outre, il devrait être en "
+"mesure de\n"
+"distribuer des données populaires assez efficacement. I2P par lui-même ne"
+" fait pas et ne fournira pas\n"
+"cette fonctionnalité. D'autre part, il existe un chevauchement pour les "
+"utilisateurs qui veulent simplement\n"
+"communiquer les uns avec les autres de manière anonyme par les sites web,"
+" forums, logiciels de partage de fichiers,\n"
+"etc. Il ya aussi eu des tentatives pour développer un magain de données "
+"distribuées\n"
+"pour fonctionner par dessus I2P,\n"
+"(plus récemment un port de Tahoe-LAFS)\n"
+"mais rien n'est encore prêt pour une utilisation générale."
+
+#: i2p2www/pages/site/comparison/freenet.html:29
+msgid ""
+"However, even ignoring any implementations issues, there are some "
+"concerns \n"
+"about Freenet's algorithms from both a scalability and anonymity "
+"perspective, owing \n"
+"largely to Freenet's heuristic driven routing.  The interactions of "
+"various techniques \n"
+"certainly may successfully deter various attacks, and perhaps some "
+"aspects of the \n"
+"routing algorithms will provide the hoped for scalability.  "
+"Unfortunately, not much\n"
+"analysis of the algorithms involved has resulted in positive results, but"
+" there is still\n"
+"hope.  At the very least, Freenet does provide substantial anonymity "
+"against an attacker\n"
+"who does not have the resources necessary to analyze it further."
+msgstr ""
+"Cependant, même sans tenir compte des questions relatives aux mises en "
+"œuvre, il ya des préoccupations\n"
+"sur les algorithmes de Freenet à la fois sur l'évolutivité et la "
+"perspective d'anonymat, en raison\n"
+"en grande partie du routage de Freenet, axée heuristique. Les "
+"interactions des différentes techniques\n"
+"peuvent certainement réussi à dissuader diverses attaques, et peut-être "
+"certains aspects de la\n"
+"des algorithmes de routage peuvent faire espérer de l'évolutivité. "
+"Malheureusement, peu\n"
+"d'analyses des algorithmes concernés ont abouti à des résultats positifs,"
+" mais il reste encore\n"
+"de l'espoir. À tout le moins, Freenet fournit un anonymat substantielle "
+"contre un attaquant\n"
+"qui n'aurait pas les ressources nécessaires pour l'analyser davantage."
+
+#: i2p2www/pages/site/comparison/index.html:2
+msgid "Comparing I2P to other projects"
+msgstr "I2P comparé à d'autres projets"
+
+#: i2p2www/pages/site/comparison/index.html:4
+msgid ""
+"There are a great many other applications and projects working on "
+"anonymous \n"
+"communication and I2P has been inspired by much of their efforts.  This "
+"is not \n"
+"a comprehensive list of anonymity resources - both freehaven's \n"
+"Anonymity "
+"Bibliography\n"
+"and GNUnet's related "
+"projects\n"
+"serve that purpose well.  That said, a few systems stand out for further\n"
+"comparison. The following have individual comparison pages:"
+msgstr ""
+"Il existe un grand nombre d'autres applications et projets travaillant "
+"sur les communication\n"
+"anonymes et I2P a été inspiré par une grande partie de leurs efforts. Ce "
+"n'est pas\n"
+"une liste complète des ressources de l'anonymat - à la fois la bibliographie "
+"anonymat de Freehaven\n"
+"et les projets liés à "
+"GNUnet\n"
+"servent bien à cette fin. Cela dit, quelques systèmes se distinguent pour"
+" davantage\n"
+"de comparaison. Les suivantes ont des pages individuelles de comparaison :"
+
+#: i2p2www/pages/site/comparison/index.html:20
+#, python-format
+msgid ""
+"The following are discussed on the other "
+"networks page:"
+msgstr ""
+"Ce qui suit est discuté sur la page autres "
+"réseaux"
+
+#: i2p2www/pages/site/comparison/index.html:32
+#, fuzzy, python-format
+msgid ""
+"The content of this page is subject to update, discussion and dispute, "
+"and we welcome comments and additions.\n"
+"You may contribute an analysis by entering a new "
+"ticket on Trac."
+msgstr ""
+"Le contenu de cette page est sujet à mise à jour, discussion et "
+"contestation, et nous nous félicitons des commentaires et ajouts.\n"
+"Vous pouvez contribuer par votre analyse en entrant un nouveau ticket sur ​​Trac."
+
+#: i2p2www/pages/site/comparison/other-networks.html:2
+msgid "I2P Compared to Other Anonymous Networks"
+msgstr "I2P comparé à d'autres réseaux anonymes"
+
+#: i2p2www/pages/site/comparison/other-networks.html:5
+msgid "The following networks are discussed on this page."
+msgstr "Les réseaux suivants sont abordés sur cette page."
+
+#: i2p2www/pages/site/comparison/other-networks.html:16
+#, fuzzy, python-format
+msgid ""
+"Most of the following sections are fairly old, and may not be accurate.\n"
+"For an overview of available comparisons, see the\n"
+"main network comparisons page.\n"
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+"La plupart des sections suivantes sont assez vieilles, et peuvent ne pas "
+"être exactes.\n"
+"Pour un aperçu des comparaisons disponibles, consultez la\n"
+"page de comparaison des réseaux "
+"principaux.\n"
+"Vous pouvez contribuer par votre analyse en entrant un\n"
+"nouveau ticket sur​​ %(trac)s."
+
+#: i2p2www/pages/site/comparison/other-networks.html:29
+#, python-format
+msgid ""
+"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
+" \n"
+"anonymizing proxies, allowing people to tunnel out through the low "
+"latency \n"
+"mix network.  Morphmix includes some very interesting collusion detection"
+" \n"
+"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
+"IP\n"
+"addresses to accomplish the same.  The two primary differences between \n"
+"these systems and I2P are related to I2P's threat model \n"
+"and their out-proxy design (as opposed to providing both sender and "
+"receiver \n"
+"anonymity).  There is source code available to both systems, but we are "
+"not aware \n"
+"of their use outside of academic environments."
+msgstr ""
+"Morphmix et Tarzan sont tous les deux à la fois complètement distribués, "
+"et des réseaux pair à pair de\n"
+"proxies anonymes, permettant aux gens des tunnels  à travers le réseau "
+"mix à faible latence.\n"
+"Morphmix comprend certains très intéressant algorithmes de détection de "
+"collusion\n"
+"et défenses Sybil, tandis que Tarzan fait usage de la rareté d'adresses "
+"IP\n"
+"pour accomplir la même chose. Les deux principales différences entre\n"
+"ces systèmes et I2P sont liées au modèle de "
+"menace de I2P\n"
+"et à leur conception out-proxy (au lieu de fournir de l'anonymat à la "
+"fois à l'émetteur et au récepteur).\n"
+"Il y a le code source disponible pour les deux systèmes, mais nous ne "
+"sommes pas au courant\n"
+"de leur utilisation en dehors des milieux universitaires."
+
+#: i2p2www/pages/site/comparison/other-networks.html:153
+#, fuzzy, python-format
+msgid ""
+"\n"
+"Mixminion and Mixmaster are networks to support anonymous email against a"
+" very\n"
+"powerful adversary.\n"
+"High-latency messaging applications running on top of I2P\n"
+"(for example Syndie or I2PBote)\n"
+"may perhaps prove adequate to meet the threat\n"
+"model of those adversaries, while running in parallel along side the "
+"needs of low latency users, to provide\n"
+"a significantly larger anonymity set.\n"
+"High-latency support within the I2P router itself may or may not be added"
+" in a distant future release.\n"
+"It is too early to say if I2P will meet the needs of users requiring "
+"extreme protection for email."
+msgstr ""
+"\n"
+"Mixminion et Mixmaster sont des réseaux pour permettre le courriel "
+"anonyme contre\n"
+"un adversaire très puissant.\n"
+"Les applications de messagerie à latence élevée fonctionnant sur I2P\n"
+"(par exemple\n"
+"Syndie ou\n"
+"I2PBote)\n"
+"peuvent peut-être se révéler suffisantes pour répondre au modèle\n"
+"de menace de ces adversaires, tout en fonctionnant en parallèle au côté "
+"des besoins des utilisateurs à faible latence, pour fournir\n"
+"un ensemble d'anonymat significativement plus grand.\n"
+"Le support de la latence élevée dans le routeur I2P lui-même pourrait ou "
+"ne pourrait pas être ajouté dans une version lointaine.\n"
+"Il est trop tôt pour dire si I2P répondra aux besoins des utilisateurs "
+"nécessitant une protection extrême pour le courrier électronique."
+
+#: i2p2www/pages/site/comparison/other-networks.html:165
+msgid ""
+"As with Tor and Onion Routing, \n"
+"both Mixminion and Mixmaster take the directory based approach as well."
+msgstr ""
+"Comme avec Tor et Oignon Routing,\n"
+"les deux Mixminion et Mixmaster prennent aussi l'approche basée sur "
+"répertoire."
+
+#: i2p2www/pages/site/comparison/other-networks.html:175
+#, python-format
+msgid ""
+"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
+"web requests,\n"
+"and as such it has a few centralized nodes (participants in the cascade) "
+"that blend\n"
+"and mix requests from clients through the sequence of nodes (the cascade)"
+" before \n"
+"proxying out onto the web.  The scope, threat model, and security is "
+"substantially \n"
+"different from I2P, but for those who don't require significant anonymity"
+" but still\n"
+"are not satisfied with an Anonymizer-like service, JAP is worth "
+"reviewing.  One\n"
+"caution to note is that anyone under the jurisdiction of the German "
+"courts may want\n"
+"to take care, as the German Federal Bureau of Criminal Investigation "
+"(FBCI) has \n"
+"successfully mounted an \n"
+"attack \n"
+"on the network.  Even though the method of this attack was later found to"
+" be illegal \n"
+"in the German courts, the fact that the data was successfully collected "
+"is the \n"
+"concern.  Courts change their minds based upon circumstance, and this is "
+"evidence that \n"
+"if a government body or intelligence agency wanted to, they could gather "
+"the data, even \n"
+"if it may be found inadmissible in some courts later)"
+msgstr ""
+"JAP (Java Anonymous Proxy) est un réseau de mélange en cascades pour "
+"l'anonymisation de demandes Web,\n"
+"et comme tel il a quelques nœuds centraux (participants à la cascade) qui"
+" mixent\n"
+"et mélangent les requêtes de clients à travers la séquence de nœuds (la "
+"cascade) avant\n"
+"les transmettre sur le web via serveur mandataire - proxy -. Le champ "
+"d'application, modèle de la menace, et sécurité sont sensiblement\n"
+"différents de I2P, mais pour ceux qui n'ont pas besoin d'anonymat "
+"importante mais cependant\n"
+"ne sont pas satisfaits avec un service Anonymizer-like, JAP mérite d'être"
+" examiné. Une\n"
+"précaution à noter pour quelqu'un relèvant de la compétence des "
+"juridictions allemandes,\n"
+"comme le Bureau fédéral allemand des enquêtes criminelles (FBCI) a\n"
+"monté avec succès une  attaque  sur le réseau. "
+"Même si la méthode de cette attaque a ensuite été jugée illégale\n"
+"devant les juridictions allemandes, le fait que les données ont été "
+"recueillies avec succès est une\n"
+"préoccupation. Les tribunaux changent d'avis sur la base de circonstance,"
+" et c'est la preuve que\n"
+"si un organisme gouvernemental ou un organisme de renseignement "
+"voulaient, ils pourraient recueillir les données, même\n"
+"si cela peut être déclarée irrecevable dans certains tribunaux plus tard)"
+
+#: i2p2www/pages/site/comparison/other-networks.html:197
+#, python-format
+msgid ""
+"Both of these systems work through the same basic \n"
+"antnet routing, providing some degree of\n"
+"anonymity based on the threat model of providing plausible deniability "
+"against a simple \n"
+"non-colluding adversary.  With the antnet routing, they first either do a"
+" random walk or a \n"
+"broadcast search to find some peer with the data or identity desired, and"
+" then use a feedback\n"
+"algorithm to optimize that found path.  This works well for applications "
+"that merely want to know \n"
+"what other people around them have to offer - \"How are y'all doing\" vs."
+" \"Hey Alice, how are you\" - \n"
+"you basically get a local cluster of nodes that can share files with and "
+"maintain some degree of \n"
+"anonymity (though you don't have much control over who is in that group "
+"of peers)."
+msgstr ""
+"Ces deux systèmes fonctionnent au moyen du même\n"
+"routage basique antnet, fournissant un certain"
+" degré\n"
+"d'anonymat basé sur le modèle de menace de fournir un plausible déni "
+"(deniability plausible) contre un simple \n"
+"adversaire non associant (non-colluding adversary). Avec le routage "
+"d'antnet, ils font d'abord soit une promenade aléatoire (random walk) ou "
+"une\n"
+"recherche large (broadcast search) pour trouver un certain pair ayant les"
+" données ou l'identité désirée, et ensuite utilisent un algorithme \n"
+"de retour d'information pour optimiser ce chemin trouvé. Cela marche bien"
+" pour des applications qui veulent simplement savoir ce que les autres "
+"personnes autour d'elles ont à offrir - \"Comment allez vous tous\" "
+"contre \"Hé Alice, comment vas-tu\" -\n"
+"vous obtenez essentiellement un groupe local de noeuds pouvant partager "
+"des fichiers entre eux et entretenir un certain degré\n"
+"d'anonymat (quoique vous n'ayez pas beaucoup de contrôle sur qui est dans"
+" ce groupe de pairs)."
+
+#: i2p2www/pages/site/comparison/other-networks.html:209
+msgid ""
+"However, the algorithm does not scale well at all - if the application "
+"wants to speak with a \n"
+"particular peer it ends up doing a broadcast search or random walk "
+"(though if they are lucky enough\n"
+"for that to succeed, the antnet routing should optimize that found "
+"connection).  This means that \n"
+"while these networks can work great at small scales, they are not "
+"suitable for large networks where\n"
+"someone wants to get in touch with another specific peer.  That does not "
+"mean that there is no \n"
+"value in these systems, just that their applicability is limited to "
+"situations where their \n"
+"particular issues can be addressed."
+msgstr ""
+"Cependant, l'algorithme d'adaptation en taille (scale) ne se fait pas du "
+"tout - si l'application veut parler avec un\n"
+"pair en particulier cela finit par faire une large recherche (broadcast) "
+"ou une promenade aléatoire (random walk) (quoique s'ils ont assez\n"
+"de chance pour que cela réussisse, le routage antnet devrait optimiser "
+"cette connexion trouvée). Cela signifie que\n"
+"tandis que ces réseaux peuvent très bien marcher à petite échelle, ils ne"
+" sont pas appropriés pour de grands réseaux où\n"
+"quelqu'un veut se mettre en contact avec un autre pair spécifique. Cela "
+"ne signifie pas qu'il n'y a pas\n"
+"de valeur dans ces systèmes, juste que leur applicabilité est limitée aux"
+" situations où leur\n"
+"problèmes (issues) particuliers peuvent être adressés."
+
+#: i2p2www/pages/site/comparison/other-networks.html:220
+#, python-format
+msgid ""
+"This was a closed-source network targeted at Iranian users.\n"
+"Tor did a good writeup on what to look for in a "
+"circumvention tool.\n"
+"Suffice it to say that being closed source and publicly targeting a "
+"specific country are not good ideas.\n"
+"I2P is, of course, open source. However, that source, and our\n"
+"technical documentation, need much more review."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:229
+msgid "Paid VPN Services"
+msgstr "Services VPN payants"
+
+#: i2p2www/pages/site/comparison/other-networks.html:230
+#: i2p2www/pages/site/comparison/other-networks.html:236
+#, fuzzy, python-format
+msgid ""
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+"Vous pouvez ajouter votre analyse en entrant un\n"
+"nouveau ticket sur %(trac)s."
+
+#: i2p2www/pages/site/comparison/other-networks.html:235
+msgid "Others"
+msgstr "Autres"
+
+#: i2p2www/pages/site/comparison/tor.html:2
+msgid "I2P Compared to Tor"
+msgstr "I2P Comparé à Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:8
+#, python-format
+msgid ""
+"Tor and Onion Routing are both anonymizing proxy networks, \n"
+"allowing people to tunnel out through their low latency mix \n"
+"network. The two primary differences between Tor / \n"
+"Onion-Routing and I2P are again related to differences in \n"
+"the threat model and the out-proxy design (though Tor\n"
+"supports hidden services as well).  In addition, Tor\n"
+"takes the directory-based approach - providing a \n"
+"centralized point to manage the overall 'view' of the \n"
+"network, as well as gather and report statistics, as \n"
+"opposed to I2P's distributed network \n"
+"database and peer selection."
+msgstr ""
+"Tor et le routage en onion sont tous deux des réseaux de proxy "
+"d'anonymisation,\n"
+"permettant aux gens d'utiliser des tunnel à travers leur réseau à faible "
+"latence.\n"
+"Les deux principales différences entre Tor / Routage en oignon et I2P "
+"sont encore liées à des différences dans \n"
+"le modèle de menace et le design de proxy sortant (quoique Tor\n"
+"prend en charge les services cachés aussi). En outre, Tor\n"
+"utilise l'approche basée sur répertoire (\"directory based\") - "
+"fournissant un \n"
+"point central pour gérer la vue d'ensemble du\n"
+"réseau, ainsi que recueillir et de communiquer les statistiques, à\n"
+"l'opposée de la base de données réseau\n"
+"distribuée de I2P et la sélection de "
+"pairs."
+
+#: i2p2www/pages/site/comparison/tor.html:22
+msgid ""
+"The I2P/Tor outproxy functionality does have a few \n"
+"substantial weaknesses against certain attackers - \n"
+"once the communication leaves the mixnet, global passive\n"
+"adversaries can more easily mount traffic analysis.  In \n"
+"addition, the outproxies have access to the cleartext \n"
+"of the data transferred in both directions, and \n"
+"outproxies are prone to abuse, along with all of the \n"
+"other security issues we've come to know and love with \n"
+"normal Internet traffic."
+msgstr ""
+"La fonctionnalité outproxy de I2P/Tor a un peu\n"
+"de faiblesses importantes contre certains agresseurs -\n"
+"une fois que la communication quitte le mixnet, les adversaires\n"
+"passifs globaux peuvent plus facilement monter une analyse du trafic. En\n"
+"outre, les outproxies ont accès au texte en clair des données transférées"
+" \n"
+"dans les deux sens, et les outproxies sont sujets à des abus,\n"
+"ainsi que toutes les autres questions de sécurité, que nous\n"
+"avons appris à connaître et à aimer avec le trafic Internet normal."
+
+#: i2p2www/pages/site/comparison/tor.html:34
+msgid ""
+"However, many people don't need to worry about those \n"
+"situations, as they are outside their threat model.  It\n"
+"is, also, outside I2P's (formal) functional scope (if people want\n"
+"to build outproxy functionality on top of an anonymous\n"
+"communication layer, they can).  In fact, some I2P users\n"
+"currently take advantage of Tor to outproxy."
+msgstr ""
+"Cependant, la plupart de personnes ne doivent pas s'inquiéter des\n"
+"ses situations, car elles sont à l'extérieur de leur modèle de menace. "
+"Cela \n"
+"est, aussi, à l'extérieur du périmètre fonctionnel (formel) de I2P (si "
+"les gens veulent\n"
+"construire la fonctionnalité outproxy au-dessus d'une couche de "
+"communication anonyme, ils peuvent).\n"
+"En fait, quelques utilisateurs I2P profitent actuellement de Tor comme "
+"proxy sortant."
+
+#: i2p2www/pages/site/comparison/tor.html:48
+msgid "Comparison of Tor and I2P Terminology"
+msgstr "Comparaison de terminologie entre Tor et I2P"
+
+#: i2p2www/pages/site/comparison/tor.html:49
+msgid ""
+"While Tor and I2P are similar in many ways, much of the terminology is "
+"different."
+msgstr ""
+"Alors que Tor et I2P sont similaires à bien des égards, une grande partie"
+" de la terminologie est différente."
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Cell"
+msgstr "Cellule"
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Message"
+msgstr "Message"
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Client"
+msgstr "Client"
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Router or Client"
+msgstr "Routeur ou client"
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Circuit"
+msgstr "Circuit"
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Tunnel"
+msgstr "Tunnel"
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "Directory"
+msgstr "Répertoire"
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "NetDb"
+msgstr "NetDb"
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Directory Server"
+msgstr "Serveur répertoire"
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Floodfill Router"
+msgstr "Routeur floodfill"
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Entry Guards"
+msgstr "Seuils de portes (entry guards)"
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Fast Peers"
+msgstr "Pairs rapides"
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Entry Node"
+msgstr "Noeud d'entrée"
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Inproxy"
+msgstr "Proxy entrant"
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Exit Node"
+msgstr "Noeud de sortie"
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Outproxy"
+msgstr "Proxy sortant"
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Hidden Service"
+msgstr "Service caché"
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Eepsite or Destination"
+msgstr "Eepsite ou Destination"
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "Hidden Service Descriptor"
+msgstr "Descripteur de service caché"
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "LeaseSet"
+msgstr "Jeu de baux"
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Introduction point"
+msgstr "Point d'introduction"
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Inbound Gateway"
+msgstr "Passerelle entrante"
+
+#: i2p2www/pages/site/comparison/tor.html:65
+msgid "Node"
+msgstr "Noeud"
+
+#: i2p2www/pages/site/comparison/tor.html:65
+#: i2p2www/pages/site/comparison/tor.html:67
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Router"
+msgstr "Routeur"
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "Onion Proxy"
+msgstr "Proxy Onion"
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "I2PTunnel Client (more or less)"
+msgstr "Client I2PTunnel (plus ou moins)"
+
+#: i2p2www/pages/site/comparison/tor.html:67
+msgid "Relay"
+msgstr "Relai"
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "Rendezvous Point"
+msgstr "Point Rendezvous"
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "somewhat like Inbound Gateway + Outbound Endpoint"
+msgstr "un peu comme passerelle entrante + extrémité sortante (outbound endpoint)"
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "Router Descriptor"
+msgstr "Descripteur de routeur"
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "RouterInfo"
+msgstr "Info routeur (RouterInfo)"
+
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Server"
+msgstr "Serveur"
+
+#: i2p2www/pages/site/comparison/tor.html:73
+msgid "Benefits of Tor over I2P"
+msgstr "Avantages de Tor sur I2P"
+
+#: i2p2www/pages/site/comparison/tor.html:76
+msgid ""
+"Much bigger user base; much more visibility in the academic and hacker "
+"communities; benefits from\n"
+"formal studies of anonymity, resistance, and performance;\n"
+"has a non-anonymous, visible, university-based leader"
+msgstr ""
+"Plus grand nombre d'utilisateurs; beaucoup plus de visibilité dans les "
+"communautés académiques et hacker; bénéficie\n"
+"d'études formelles d'anonymat, de résistance, et performance;\n"
+"a un chef de file universitaire non-anonyme, visible"
+
+#: i2p2www/pages/site/comparison/tor.html:82
+msgid "Has already solved some scaling issues I2P has yet to address"
+msgstr ""
+"A déjà résolu certains problèmes d'échelle que I2P n'a pas eu encore à "
+"aborder"
+
+#: i2p2www/pages/site/comparison/tor.html:83
+msgid "Has significant funding"
+msgstr "A un financement important"
+
+#: i2p2www/pages/site/comparison/tor.html:84
+msgid "Has more developers, including several that are funded"
+msgstr "A davantage de développeurs, dont plusieurs sont financés"
+
+#: i2p2www/pages/site/comparison/tor.html:86
+msgid ""
+"More resistant to state-level blocking due to TLS transport layer and "
+"bridges\n"
+"(I2P has proposals for \"full restricted routes\" but these are not yet "
+"implemented)"
+msgstr ""
+"Plus résistant aux blocage à niveau état en raison de couche transport "
+"TLS et ponts\n"
+"(I2P a des propositions pour des \"routes restreintes pleines\" mais "
+"celles-ci ne sont pas encore mises en œuvre)"
+
+#: i2p2www/pages/site/comparison/tor.html:91
+msgid "Big enough that it has had to adapt to blocking and DOS attempts"
+msgstr "Assez grand pour avoir dû s'adapter aux tentatives de blocage et de DOS"
+
+#: i2p2www/pages/site/comparison/tor.html:92
+msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
+msgstr ""
+"Conçus et optimisé pour le traffic sortant, avec un grand nombre de "
+"noeuds de sortie"
+
+#: i2p2www/pages/site/comparison/tor.html:94
+msgid ""
+"Better documentation, has formal papers and specifications,\n"
+"better website, many more translations"
+msgstr ""
+"Une meilleure documentation, a des papiers et des spécifications "
+"formelles, \n"
+"meilleur site web, beaucoup plus de traductions"
+
+#: i2p2www/pages/site/comparison/tor.html:99
+msgid "More efficient with memory usage"
+msgstr "Utilisation de la mémoire plus efficace"
+
+#: i2p2www/pages/site/comparison/tor.html:100
+msgid "Tor client nodes have very low bandwidth overhead"
+msgstr ""
+"Les nœuds clients Tor subissent une très légère surcharge de bande "
+"passante"
+
+#: i2p2www/pages/site/comparison/tor.html:102
+msgid ""
+"Centralized control reduces the complexity at each\n"
+"node and can efficiently address Sybil attacks"
+msgstr ""
+"Le contrôle centralisé réduit la complexité à chaque\n"
+"nœud et peut répondre efficacement à des attaques Sybil"
+
+#: i2p2www/pages/site/comparison/tor.html:108
+msgid ""
+"A core of high capacity nodes provides higher\n"
+"throughput and lower latency"
+msgstr ""
+"Un coeur de nœuds à grande capacité fournit un\n"
+"plus haut débit et de faible latence"
+
+#: i2p2www/pages/site/comparison/tor.html:113
+msgid "C, not Java (ewww)"
+msgstr "C, not Java"
+
+#: i2p2www/pages/site/comparison/tor.html:116
+msgid "Benefits of I2P over Tor"
+msgstr "Avantages d'I2P sur Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:118
+msgid ""
+"Designed and optimized for hidden services, which are much faster than in"
+" Tor"
+msgstr ""
+"Conçu et optimisé pour les services cachés, qui sont beaucoup plus rapide"
+" que dans Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:119
+msgid "Fully distributed and self organizing"
+msgstr "Entièrement distribué et auto-organisé"
+
+#: i2p2www/pages/site/comparison/tor.html:121
+msgid ""
+"Peers are selected by continuously profiling and ranking performance,\n"
+"rather than trusting claimed capacity"
+msgstr ""
+"es pairs sont choisis par profilage  continu et classement de leurs "
+"performances,\n"
+"plutôt que de faire confiance à la capacité qu'ils revendiquent"
+
+#: i2p2www/pages/site/comparison/tor.html:127
+msgid ""
+"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
+"rather than hardcoded"
+msgstr ""
+"Les pairs floodfill (\"serveurs d'annuaire\") sont variables et non "
+"éprouvés (en anglais untrusted),\n"
+"plutôt que codés en dur (en anglais hardcoded)"
+
+#: i2p2www/pages/site/comparison/tor.html:132
+msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
+msgstr ""
+"Tellement petit qu'il n'a pas été bloqué ni subi beaucoup de DOS, ou pas "
+"du tout"
+
+#: i2p2www/pages/site/comparison/tor.html:133
+msgid "Peer-to-peer friendly"
+msgstr "Pair à pair friendly"
+
+#: i2p2www/pages/site/comparison/tor.html:134
+msgid "Packet switched instead of circuit switched"
+msgstr "Commutation de paquets à la place de commutation de circuit"
+
+#: i2p2www/pages/site/comparison/tor.html:137
+msgid ""
+"implicit transparent load balancing of messages \n"
+"across multiple peers, rather than a single path"
+msgstr ""
+"Équilibrage de charge transparent et implicite des messages\n"
+"à travers plusieurs pairs, plutôt qu'un seul chemin"
+
+#: i2p2www/pages/site/comparison/tor.html:143
+msgid ""
+"resilience vs. failures by running multiple \n"
+"tunnels in parallel, plus rotating tunnels"
+msgstr ""
+"résistance contre les défaillances par exécution de plusieurs\n"
+"tunnels en parallèle, ainsi que rotation des tunnels"
+
+#: i2p2www/pages/site/comparison/tor.html:149
+msgid ""
+"scale each client's connections at O(1) instead \n"
+"of O(N) (Alice has e.g. 2 inbound tunnels that are \n"
+"used by all of the peers Alice is talking with, \n"
+"rather than a circuit for each)"
+msgstr ""
+"s'adapte à l'échelle des connexions de chaque client à O(1) au lieu\n"
+"de O(N) (Alice a par exemple 2 tunnels entrants qui sont\n"
+"utilisés par tous les pairs avec lesquels parle Alice,\n"
+"plutôt que d'un circuit de chaque)"
+
+#: i2p2www/pages/site/comparison/tor.html:159
+msgid ""
+"Unidirectional tunnels instead of bidirectional\n"
+"circuits, doubling the number of nodes a peer has to\n"
+"compromise to get the same information."
+msgstr ""
+"Tunnels unidirectionnels au lieu de circuits\n"
+"bidirectionnel, doublant le nombre de nœuds qu'un\n"
+"pair doit avoir à compromettre pour obtenir la même information."
+
+#: i2p2www/pages/site/comparison/tor.html:166
+msgid ""
+"Protection against detecting client activity, even\n"
+"when an attacker is participating in the tunnel, as\n"
+"tunnels are used for more than simply passing end \n"
+"to end messages (e.g. netDb, tunnel management, \n"
+"tunnel testing)"
+msgstr ""
+"Protection contre la détection d'activité du client, même\n"
+"quand un attaquant participe au tunnel, puisque\n"
+"les tunnels sont utilisés pour davantage que simplement passer\n"
+"des messages de bout en bout (par exemple netDb, gestion de tunnel,\n"
+"essais de tunnel)"
+
+#: i2p2www/pages/site/comparison/tor.html:175
+msgid ""
+"Tunnels in I2P are short lived, decreasing the number\n"
+"of samples that an attacker can use to mount an \n"
+"active attack with, unlike circuits in Tor, which are\n"
+"typically long lived."
+msgstr ""
+"Dans I2P les tunnels sont de courte durée de vie, diminuant le nombre\n"
+"d'échantillons qu'un attaquant peut utiliser pour monter une\n"
+"attaque active avec, contrairement aux circuits de Tor, qui ont\n"
+"généralement une longue durée de vie."
+
+#: i2p2www/pages/site/comparison/tor.html:183
+msgid ""
+"I2P APIs are designed specifically for anonymity and\n"
+"security, while SOCKS is designed for functionality."
+msgstr ""
+"Les API de I2P sont conçues spécifiquement pour l'anonymat et\n"
+"la sécurité, tandis que SOCKS est conçu pour la fonctionnalité."
+
+#: i2p2www/pages/site/comparison/tor.html:188
+msgid "Essentially all peers participate in routing for others"
+msgstr "Par essence, tous les pairs participent à acheminer pour d'autres"
+
+#: i2p2www/pages/site/comparison/tor.html:190
+msgid ""
+"The bandwidth overhead of being a full peer is low, \n"
+"while in Tor, while client nodes don't require much\n"
+"bandwidth, they don't fully participate in the mixnet."
+msgstr ""
+"Faible surcharge de bande passante d'un pair à part entière, plutôt que "
+"minime dans Tor où les nœuds ne participent pas pleinement au réseau "
+"croisé (en anglais mixnet)."
+
+#: i2p2www/pages/site/comparison/tor.html:196
+msgid "Integrated automatic update mechanism"
+msgstr "Mécanisme intégré de mise à jour automatique"
+
+#: i2p2www/pages/site/comparison/tor.html:197
+msgid "Both TCP and UDP transports"
+msgstr "Tous les deux transports : TCP et UDP"
+
+#: i2p2www/pages/site/comparison/tor.html:198
+msgid "Java, not C (ewww)"
+msgstr "Java, not C"
+
+#: i2p2www/pages/site/comparison/tor.html:201
+msgid "Other potential benefits of I2P but not yet implemented"
+msgstr "Autres avantages potentiels de I2P mais pas encore mis en œuvre"
+
+#: i2p2www/pages/site/comparison/tor.html:202
+msgid "...and may never be implemented, so don't count on them!"
+msgstr ""
+"... et pourraient ne jamais être mis en œuvre, alors ne comptez pas sur "
+"eux !"
+
+#: i2p2www/pages/site/comparison/tor.html:205
+msgid ""
+"Defense vs. message count analysis by garlic wrapping \n"
+"multiple messages"
+msgstr ""
+"Défense contre l'analyse du nombre de messages par enveloppement en "
+"oignon\n"
+"de plusieurs messages"
+
+#: i2p2www/pages/site/comparison/tor.html:211
+msgid ""
+"Defense vs. long term intersection by adding delays \n"
+"at various hops (where the delays are not discernible\n"
+"by other hops)"
+msgstr ""
+"Défense contre intersection long terme en ajoutant des retards\n"
+"à différents sauts (où les retards ne sont pas discernables\n"
+"par d'autres sauts)"
+
+#: i2p2www/pages/site/comparison/tor.html:218
+msgid ""
+"Various mixing strategies at the tunnel level (e.g.\n"
+"create a tunnel that will handle 500 messages / minute,\n"
+"where the endpoint will inject dummy messages if there\n"
+"are insufficient messages, etc)"
+msgstr ""
+"Diverses stratégies de mélange au niveau du tunnel (par exemple\n"
+"créer un tunnel qui va gérer 500 messages / minute,\n"
+"dans lequel le point final va injecter des messages factices si\n"
+"il y a une nombre de messages insuffisant, etc)"
+
diff --git a/i2p2www/translations/fr/LC_MESSAGES/messages.po b/i2p2www/translations/fr/LC_MESSAGES/docs.po
similarity index 53%
rename from i2p2www/translations/fr/LC_MESSAGES/messages.po
rename to i2p2www/translations/fr/LC_MESSAGES/docs.po
index a4c6dde9..b9e35f84 100644
--- a/i2p2www/translations/fr/LC_MESSAGES/messages.po
+++ b/i2p2www/translations/fr/LC_MESSAGES/docs.po
@@ -5,13 +5,15 @@
 # Translators:
 # Boxoa590, 2013
 # magma , 2011
+# syl_, 2013
+# Towatowa441, 2013
 msgid ""
 msgstr ""
 "Project-Id-Version:  I2P\n"
-"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
-"POT-Creation-Date: 2013-07-03 03:49+0000\n"
-"PO-Revision-Date: 2013-06-29 11:32+0000\n"
-"Last-Translator: Boxoa590\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-12-12 06:19+0000\n"
+"Last-Translator: str4d \n"
 "Language-Team: French "
 "(http://www.transifex.com/projects/p/I2P/language/fr/)\n"
 "Plural-Forms: nplurals=2; plural=(n > 1)\n"
@@ -20,6937 +22,22 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 "Generated-By: Babel 0.9.6\n"
 
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:24
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:25
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:12
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:12
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:17
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:16
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:16
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:26
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:19
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:19
-msgid "Files are available on the `download page`_."
-msgstr "Les fichiers sont disponibles sur la `download page`_."
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:28
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:15
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:29
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:16
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:16
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:21
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:20
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:20
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:30
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:23
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:23
-msgid "`download page`"
-msgstr "`download page`"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:30
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:17
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:31
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:18
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:19
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:18
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:22
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:22
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:32
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:25
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:79
-msgid "RELEASE DETAILS"
-msgstr "DETAILS SUR CETTE VERSION"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:32
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:19
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:33
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:40
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:50
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:24
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:24
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:34
-msgid "Major Changes"
-msgstr "Changements majeurs"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:44
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:24
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:43
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:55
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:47
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:58
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:43
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:32
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:30
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:39
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:81
-msgid "Bug Fixes"
-msgstr "Corrections de bugs"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:54
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:30
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:47
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:69
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:63
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:68
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:54
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:41
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:36
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:51
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:43
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:94
-msgid "Other"
-msgstr "Autre"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:73
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:36
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:51
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:82
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:75
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:96
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:76
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:52
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:56
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:67
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:56
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:110
-msgid "SHA256 Checksums:"
-msgstr "Sommes de contrôle SHA256 :"
-
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39
-msgid "Major changes"
-msgstr ""
-
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47
-msgid "Wrapper Update"
-msgstr ""
-
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:23
-msgid "Update Info"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2
-msgid "0.9.2 Release"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9
-msgid ""
-"0.9.2 includes extensive low-level changes to improve the performance and"
-" efficiency of the router. We have updated our UPnP library, to hopefully"
-" make UPnP work for more people. I2PSnark now has DHT support, but it is "
-"not yet enabled by default, as we plan to do more testing during the "
-"upcoming 0.9.3 development cycle."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12
-msgid ""
-"As usual, there's also lots of bug fixes in this release, so updating is "
-"recommended."
-msgstr ""
-"Comme d'habitude, il ya aussi beaucoup de corrections de bugs dans cette "
-"version, alors il est recommandé d'effectuer la mise à jour."
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26
-msgid ""
-"SSU: Fix several problems in our UDP transport, to improve efficiency and"
-" reliability for connection setup. Also improve defenses against various "
-"types of bad input."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27
-msgid ""
-"UPnP: Updated our library to fix several issues, should work for more "
-"routers now"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28
-msgid ""
-"Transport: Improve performance in both our TCP and UDP transports, to "
-"benefit high-bandwidth routers"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29
-msgid ""
-"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered "
-"are now much more flexible, which should lessen protocol overhead and "
-"reduce stalls caused by dropped tags."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30
-msgid ""
-"I2PSnark: Add DHT support, not yet enabled by default, will do further "
-"testing and plan to enable by default in 0.9.3."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34
-msgid ""
-"Fix various issues affecting memory usage and performance on high-"
-"bandwidth routers"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35
-msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36
-msgid "Fix i2psnark bug that prevented a completion announcement to the tracker"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37
-msgid "Fix a lock contention problem in i2ptunnel"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38
-msgid "Fix some OSX installation issues"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39
-msgid "Remove uses of direct byte buffers that may have been leaking"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43
-msgid "Reduce overhead in network messages"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44
-msgid "Add \"universal\" theme support"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45
-msgid "Theme updates"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46
-msgid "Add a jbigi library for Raspberry Pi"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47
-msgid "New Scala unit test framework"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48
-msgid "Translation updates for Czech, Dutch, German, and Greek"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49
-msgid "Update wrapper to 3.5.15 (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108
-msgid "Update GeoIP data (new installs and PPA only)"
-msgstr "Mise à jour données GeoIP (nouvelles installations et PPA seulement)"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:2
-msgid "0.9.3 Release"
-msgstr "Release 0.9.3"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9
-msgid ""
-"0.9.3 includes extensive low-level changes to the queueing of messages in"
-" the router.  We implement the CoDel Active Queue Management (AQM) "
-"algorithm.  We also unify the queueing and priority mechanisms in the "
-"transports to aid diagnosis and reduce network latency.  Work continues "
-"on fixing UDP transport bugs and making UDP more resistant to attacks.  "
-"There are more changes to improve the performance of the router and "
-"reduce its memory usage.  Also, we enable i2psnark's DHT support, "
-"introduced last release, by default."
-msgstr ""
-"0.9.3 inclut de vastes changements de bas niveau de la file d'attente de "
-"messages dans le routeur. Nous mettons en oeuvre l'algorithme CODEL "
-"Active Queue Management (AQM). Nous unissons aussi la queue et mécanismes"
-" de priorité dans les transports pour faciliter le diagnostic et de "
-"réduire la latence du réseau. Les travaux se poursuivent sur ​​la "
-"résolution de bogues de transport UDP et rendre UDP plus résistant aux "
-"attaques. Il n'y a plus de changements pour améliorer les performances du"
-" routeur et réduire son utilisation de la mémoire. En outre, nous "
-"activons dans  i2psnark le support de DHT, introduit dans la dernière "
-"version, par défaut."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26
-msgid "Active Queue Management"
-msgstr "Gestion de la file d'attente active"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:27
-msgid "Priority queues"
-msgstr "Priorités files d'attente"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28
-msgid "I2PSnark DHT: Several bug fixes, enable by default."
-msgstr "I2PSnark DHT : plusieurs corrections de bugs, activée par défaut."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32
-msgid ""
-"Several SSU fixes including memory leak, and better handling of routers "
-"behind firewalls that change UDP ports; additional defenses for malicious"
-" packets."
-msgstr ""
-"Plusieurs corrections dans SSU incluant fuite de mémoire, et une "
-"meilleure gestion des routeurs derrière les pare-feux qui changent les "
-"ports UDP; défenses supplémentaires contre les paquets malveillants."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33
-msgid "Fix piece selection (rarest-first) bugs in i2psnark"
-msgstr "Résolu bugs sélection de tronçons (le plus rare le premier) dans i2psnark"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34
-msgid "Fix bug causing multiple browsers to open at startup"
-msgstr ""
-"Correction d'un bug causant l'ouverture de multiples navigateurs au "
-"démarrage"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38
-msgid "Improvements in caching"
-msgstr "Amélioration de la mise en cache"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39
-msgid "Several synchronization fixes and lock contention reduction"
-msgstr ""
-"Plusieurs corrections de synchronisation de et réduction de la contention"
-" de verrouillage"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40
-msgid "Major reduction in SSU buffers memory use"
-msgstr "Réduction importante de l'utilisation de mémoire des buffers SSU"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41
-msgid ""
-"Fix streaming connection timeout back to 1 minute, was inadvertently "
-"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was"
-" unlimited"
-msgstr ""
-"Corrigé le timeout de connexion streaming à 1 minute, qui avait été été "
-"modifié par inadvertance à 5 minutes; mise le timeout de lecture de "
-"serveur i2ptunnel à 5 minutes, il était illimité"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42
-msgid "Improved defenses in i2ptunnel for \"darkloris\""
-msgstr "Amélioration des défenses dans i2ptunnel pour \"darkloris\""
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:43
-msgid "More validation at torrent creation in i2psnark"
-msgstr "Davantage de validation lors de la création de torrent dans i2psnark"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44
-msgid "Several parameter changes in SSU to improve throughput"
-msgstr "Plusieurs changements de paramètres dans SSU pour améliorer le débit"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45
-msgid ""
-"New event log for major events including restarts; show multiple restart "
-"lines on graphs"
-msgstr ""
-"Nouveau journal d'événements pour les événements majeurs, y compris ceux "
-"incluant des redémarres, montre sur les graphes plusieurs lignes de "
-"redémarrage"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46
-msgid "Remove duplicate messages from logs"
-msgstr "Suppression des doublons de messages depuis les logs"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47
-msgid "Don't respond to blocked streaming connections with a reset, just drop"
-msgstr ""
-"Ne répond par un reset pas aux connexions streaming bloquées, abandonne "
-"simplement"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48
-msgid "Remove all uses of inefficient SimpleTimer"
-msgstr "Retire toutes les utilisations inefficaces de SimpleTimer"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49
-msgid "More checks for valid IPs and ports entered in console"
-msgstr ""
-"Davantage de contrôles de la validité des IP et des ports entrés dans la "
-"console"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50
-msgid "Fix bug that wasted a lot of entropy"
-msgstr "Correction d'un bug qui a gaspillé beaucoup d'entropie"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51
-msgid "Translation updates: Italian, Portuguese, Spanish, Swedish"
-msgstr "Mises à jour de traduction : Italien, Portugais, Espagnol, Suédois"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52
-msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5"
-msgstr "Ajoute configuration non-NIO dans jetty.xml, recommandé pour Java 5"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2
-msgid "0.9.4 Release"
-msgstr "Release 0.9.4"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9
-msgid ""
-"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, "
-"that was reducing network performance and reliability. It also includes "
-"major changes in the in-network update system, and adds the capability to"
-" update via in-network torrents."
-msgstr ""
-"0.9.4 inclue un correctif pour un bug de capacité du réseau, introduit "
-"dans la 0.9.2, qui a réduit les performances et la fiabilité du réseau. "
-"Il comprend également des changements majeurs dans le système de mise à "
-"jour en réseau, et ajoute la possibilité de mettre à jour en réseau via "
-"des torrents."
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13
-msgid ""
-"We fixed several bugs in the i2psnark DHT implementation that was "
-"introduced\n"
-"last release. For those of you using console or http proxy passwords,\n"
-"we converted to the more-secure digest method and improved the security "
-"for console forms."
-msgstr ""
-"Nous avons corrigé plusieurs bugs dans la mise en œuvre de DHT i2psnark "
-"qui ont été introduits ⏎\n"
-"depuis la dernière version. Pour ceux d'entre vous qui utilisent la "
-"console ou des mots de passe de proxy HTTP, ⏎  nous avons converti à la "
-"méthode digest plus sécurisé, et amélioré la sécurité des formulaires de "
-"la console."
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19
-msgid ""
-"For those of you already running development builds, your router should "
-"automatically\n"
-"update to 0.9.4-0 using the new in-network torrent facility.\n"
-"For those running 0.9.3-0, you will update normally using in-network "
-"HTTP, and\n"
-"we will have more information for you when we release 0.9.5."
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36
-msgid ""
-"Big rework of the update system; Preliminary support for updates via "
-"i2psnark"
-msgstr ""
-"Gros remaniement du système de mise à jour; Support préliminaire pour les"
-" mises à jour via i2psnark"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37
-msgid "Add per-destination outbound priorities"
-msgstr "Ajouter de priorités sortantes par destination"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41
-msgid ""
-"Fix major bug that reduced SSU connection limits which reduced tunnel "
-"build success rates"
-msgstr ""
-"Résolu bug majeur that réduisait les limites de connexion SSU ce qui "
-"réduisait le taux de succès de construction de tunnel"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42
-msgid "Fix bug with external I2CP that prevented some external apps from working"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43
-msgid "Fixed several bugs in i2psnark DHT"
-msgstr "Correction de plusieurs bugs dans i2psnark DHT"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44
-msgid "Fixed bug in i2psnark PEX that inflated peer counts"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45
-msgid "Handle dropped I2CP messages better"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46
-msgid "Reduce overhead of I2CP messages"
-msgstr "Reduit l'entête des messages I2CP"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47
-msgid "Enforce max size in transport outbound message queues"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48
-msgid "Fixes for Windows eepget.bat (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49
-msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53
-msgid ""
-"More performance improvements, memory reduction, and object churn "
-"reduction"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54
-msgid "Better detection of network disconnections"
-msgstr "Meilleure détection des déconnexions réseau"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55
-msgid "Further improvements in the SSU transport"
-msgstr "D'autres améliorations dans le transport SSU"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56
-msgid "Add console password form"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57
-msgid ""
-"Convert http proxy and console from basic to digest authentication for "
-"added security"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58
-msgid ""
-"Improved verification of console form submissions, using jsp sessions. "
-"Cookies may now be required on forms, except when the console password is"
-" enabled"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59
-msgid ""
-"Initial work on new interfaces to manage applications started via "
-"clients.config"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60
-msgid "Increase minimum peer port to 1024"
-msgstr "Augmente le port minimum de port de pair à 1024"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61
-msgid "Increase granularity of bandwidth limiter for smoother transmissions"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62
-msgid ""
-"Translation updates: Chinese, French, German, Italian, Polish, "
-"Portuguese, Swedish, and Ukrainian"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64
-msgid "Update wrapper to 3.5.16 (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65
-msgid "New ARMv6 wrapper for Raspberry Pi"
-msgstr "Nouveau wrapper ARMv6 pour Raspberry Pi"
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:2
-msgid "0.9.5 Release"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9
-msgid ""
-"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities"
-" that are being investigated by researchers at UCSB. We continue to work "
-"with them on additional improvements. This is a good opportunity to "
-"remind the community that while our network continues to grow rapidly, it"
-" is still relatively small. There may be multiple weaknesses or bugs that"
-" could compromise your anonymity. Help us grow the network by spreading "
-"the word and contributing where you can."
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13
-#, python-format
-msgid ""
-"In this upgrade cycle, a random 1% of routers, (plus all routers running "
-"a\n"
-"development build) will attempt to update via the experimental in-network"
-" bittorrent\n"
-"with i2psnark. If this doesn't work, it should fall back to standard in-"
-"network HTTP update."
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27
-msgid "Defenses and Bug Fixes"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29
-msgid "Fix router bug causing lockup when using iMule"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30
-msgid "Recognize, handle, reject duplicate tunnel IDs"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31
-msgid "Fix changing of the log file name"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32
-msgid "Prevent hashcode attack in session tags"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33
-msgid "Add build request throttler based on previous hop"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34
-msgid "Limit concurrent next-hop lookups"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35
-msgid "Catch exceptions storing nonces in console"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36
-msgid "Fix saving graph settings in console"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37
-msgid "Fix eepget generation of URLs when not proxied"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38
-msgid ""
-"Encrypt database lookup messages end-to-end when sent through exploratory"
-" tunnels"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39
-msgid "Don't use multiple floodfills from the same /16 in a query"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40
-msgid "Randomize delay before verifying floodfill store"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41
-msgid "Increase number of floodfills"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:45
-msgid "Improve support for mobile browsers"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46
-msgid "Partial defenses for UCSB attacks"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47
-msgid "Add announce list support to i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48
-msgid "Jetty: upgrade Apache Tomcat to 6.0.36"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49
-msgid "Split router info files into multiple subdirectories"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50
-msgid "Add IP to hostname mapping option in SOCKS"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51
-msgid "Improve PRNG seeding"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52
-msgid ""
-"Translation updates: French, German, Hungarian, Italian, Norwegian, "
-"Polish, Portuguese, Russian, Swedish"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54
-msgid "Update wrapper to 3.5.17 (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:2
-msgid "0.9.6 Release"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:7
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9
-msgid ""
-"0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to "
-"Jetty 7.6.10 (2013-03-12). See below for important information on the "
-"Jetty update. The Jetty 7 series is actively maintained and we plan to "
-"stay current with it in future I2P releases."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13
-msgid ""
-"Most users will update via HTTP. Those running development builds will "
-"attempt to update via the\n"
-"experimental in-network bittorrent with i2psnark. We've fixed some bugs "
-"that will enable more users\n"
-"to update via torrent in the 0.9.7 update cycle."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25
-msgid "Important fix for Windows Eepsites, first install 0.9.5 only"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27
-msgid ""
-"If you first installed I2P with version 0.9.5, on Windows only, we "
-"recommend that you follow the\n"
-"following instructions to fix your eepsite location **before** you update"
-" to 0.9.6.\n"
-"Only original installations of 0.9.5-0 on Windows are affected by this "
-"issue. If your router version\n"
-"is 0.9.5-0-win1, you already have the fix and need not take any action."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34
-msgid "See `this page`_ for instructions."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:38
-msgid "`this page`"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:40
-msgid "Jetty 7 Migration Details"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42
-msgid ""
-"For most people, the update should just work. If you have multiple Jetty "
-"eepsites,\n"
-"OR have made changes to jetty.xml or other Jetty configuration files, "
-"including changing the port\n"
-"from 7658, you MUST take manual action AFTER updating."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48
-msgid ""
-"After update, the router will migrate your jetty.xml files to the new "
-"Jetty 7 format."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50
-msgid ""
-"The migration resets the port to 7658. If you have more than one Jetty "
-"eepsite, OR your eepsite\n"
-"  is NOT on port 7658, OR you have made other modifications to jetty.xml "
-"(for example changing the\n"
-"  listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml "
-"file for each eepsite to fix them up\n"
-"  after updating, and restart again."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55
-msgid ""
-"**The following files will be backed up with a ".jetty6" suffix"
-" and then migrated.**\n"
-"If you have made local changes, you may have to edit them manually and "
-"restart.\n"
-"See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69
-#: i2p2www/pages/global/nav.html:75 i2p2www/pages/global/nav.html:91
-#: i2p2www/pages/site/docs/plugins.html:2
-#: i2p2www/pages/site/docs/spec/configuration.html:65
-msgid "Plugins"
-msgstr "Plugins"
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:71
-msgid "Most plugins should work fine with Jetty 7."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:75
-msgid ""
-"The I2PControl and zzzot plugins must be updated. Your router should "
-"download and install the new versions shortly after starting 0.9.6."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77
-msgid "If a plugin does not work, please contact the maintainer for that plugin."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83
-msgid "Several bugs with Windows installation (see above)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:84
-msgid "Fix default form action in i2ptunnel"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85
-msgid "Fix links on iframed console pages"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86
-msgid "Better detection of 64-bit Windows to prevent crashes by systray"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87
-msgid "Fix bug preventing router update via torrent"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88
-msgid "Several SSU fixes for NATs that change UDP ports"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89
-msgid ""
-"Ignore unsupported IPs in RouterInfos when selecting an address (prep for"
-" IPv6)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90
-msgid ""
-"Ignore unused option bits in Database Lookup Message (prep for requesting"
-" encrypted response)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91
-msgid "Fix HTTP proxy error response for malformed URIs"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92
-msgid "Recognize UPnP devices without port forwarding capability"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96
-msgid "Jetty 7.6.10 (see above for migration information)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97
-msgid "Limit page size in i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98
-msgid "Add data directory and page size configuration to i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99
-msgid "Support multiple i2psnark instances"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100
-msgid "Piece size adjustments in i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101
-msgid "Add more graphing support for combined bandwidth graph"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102
-msgid "Block b32.i2p supercookies"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103
-msgid "Allow stopping clients on /configclients"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104
-msgid "Check for nonce count replays in HTTP client"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105
-msgid "Support SASL authentication in IRC proxy"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106
-msgid "Several cleanups and minor fixes in the update manager"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107
-msgid "Translation updates: German, Portuguese, Russian, Spanish, and Swedish"
-msgstr ""
-
-#: i2p2www/pages/blog/category.html:2
-msgid "Blog Category"
-msgstr ""
-
-#: i2p2www/pages/blog/category.html:4
-#, python-format
-msgid "I2P Blog ATOM Feed for Category: %(category)s"
-msgstr ""
-
-#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
-#: i2p2www/pages/global/nav.html:95
-msgid "Blog"
-msgstr "Blog"
-
-#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:75
-msgid "I2P Blog ATOM Feed"
-msgstr "Flux ATOM du Blog I2P"
-
-#: i2p2www/pages/blog/index.html:17
-#, python-format
-msgid "Posted %(date)s by %(author)s"
-msgstr ""
-
-#: i2p2www/pages/blog/latest.html:5
-msgid "More blog posts…"
-msgstr "Davantage de posts de blog…"
-
-#: i2p2www/pages/blog/post.html:6
-msgid "Posted:"
-msgstr ""
-
-#: i2p2www/pages/blog/post.html:7
-msgid "Author:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:4
-msgid "Debian I2P Packages"
-msgstr "Packages I2P Debian"
-
-#: i2p2www/pages/downloads/debian.html:6
-#, python-format
-msgid ""
-"The packages hosted on the I2P Launchpad site\n"
-"have been tested and should work on x86/x86_64 platforms running:"
-msgstr ""
-"Les paquetages hébergés sur the I2P Launchpad site⏎\n"
-"ont étés testés et devraientmarcher sur les plateformes "
-"x86/x86_64 utilisant :"
-
-#: i2p2www/pages/downloads/debian.html:11
-msgid "Ubuntu (Precise 12.04 and newer)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:13
-msgid ""
-"Debian Linux (Wheezy and newer) & kFreeBSD"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:17
-#, python-format
-msgid ""
-"The I2P packages may work on systems not listed above. Please "
-"report any issues\n"
-"with these packages on Trac at\n"
-"http://%(trac)s."
-msgstr ""
-"Les paquetages I2P peuvent fonctionner sur des systèmes non "
-"listés ci-dessus . Veuillez rapporter tous problèmes⏎\n"
-"avec ces paquetages surTrac à⏎\n"
-"http://%(trac)s."
-
-#: i2p2www/pages/downloads/debian.html:23
-msgid ""
-"Option 1: Recent versions of Ubuntu and its "
-"derivatives (Try this if you're not using Debian)"
-msgstr ""
-"Option 1: Versions récentes de Ubuntu et ses "
-"dérivées (Essayez ceci si vous n'utilisez pas Debian)"
-
-#: i2p2www/pages/downloads/debian.html:24
-msgid "Option 2: Debian (including Debian-derivatives)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:25
-msgid ""
-"Option 3: Non-Linux (and possibly Non-x86 "
-"architectures)"
-msgstr ""
-"Option 3: Non-Linux (et probablement les "
-"architectures Non-x86)"
-
-#: i2p2www/pages/downloads/debian.html:28
-msgid ""
-"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
-" Linux Mint & Trisquel"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:29
-msgid "Adding the PPA via the command line and installing I2P"
-msgstr "Ajouter le PPA via la ligne de commande et installer I2P"
-
-#: i2p2www/pages/downloads/debian.html:32
-msgid "Open a terminal and enter:"
-msgstr "Ouvrir un terminal et entrer :"
-
-#: i2p2www/pages/downloads/debian.html:34
-msgid ""
-"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
-"gpg key that the repository has been signed with. The GPG key ensures\n"
-"that the packages have not been tampered with since being built."
-msgstr ""
-"Cette commande va ajouter le PPA à /etc/apt/sources.list.d et rapporter "
-"la⏎\n"
-"clé GPG avec laquelle le dépôt a été signé. La clé GPG assure ⏎\n"
-"que les paquetages n'ont pas été altérés depuis leur construction."
-
-#: i2p2www/pages/downloads/debian.html:41
-msgid "Notify your package manager of the new PPA by entering:"
-msgstr "Avertissez votre gestionnaire de paquets de la nouvelle PPA en entrant :"
-
-#: i2p2www/pages/downloads/debian.html:43
-msgid ""
-"This command will retrieve the latest list of software from each\n"
-"repository that is enabled on your system, including the I2P PPA that\n"
-"was added with the earlier command."
-msgstr ""
-"Cette commande va récupérer la plus récente liste de logiciels de chaque "
-"⏎\n"
-"déôt qui soit activé sur votre système, y compris le PPA I2P qui ⏎\n"
-"a été ajouté avec la commande antérieure."
-
-#: i2p2www/pages/downloads/debian.html:49
-#: i2p2www/pages/downloads/debian.html:112
-#: i2p2www/pages/downloads/debian.html:137
-msgid "You are now ready to install I2P!"
-msgstr "Vous êtes maintenant prêt à installer I2P !"
-
-#: i2p2www/pages/downloads/debian.html:53
-msgid "Adding the PPA Using Synaptic"
-msgstr "Ajouter le PPA en utilisant Synaptic"
-
-#: i2p2www/pages/downloads/debian.html:56
-msgid ""
-"Open Synaptic (System -> Administration -> Synaptic Package "
-"Manager)."
-msgstr ""
-"Ouvrir Synaptic (System -> Administration -> Synaptic Package "
-"Manager)."
-
-#: i2p2www/pages/downloads/debian.html:61
-msgid ""
-"Once Synaptic opens, select Repositories from the "
-"Settings menu."
-msgstr ""
-"Une fois Synaptic ouvert, sélectionnez Repositories depuis le "
-"menu Settings."
-
-#: i2p2www/pages/downloads/debian.html:66
-msgid ""
-"Click the Other Sources tab and click Add. Paste "
-"ppa:i2p-maintainers/i2p into the APT-line field and click "
-"Add Source. Click the Close button then "
-"Reload."
-msgstr ""
-"Cliquer l'onglet Autres sources et cliquez Ajouter. "
-"Coller ppa:i2p-maintainers/i2p dans le champ ligne-APT et "
-"cliquez Ajouter source. Cliquez le bouton Fermer puis "
-"Recharger."
-
-#: i2p2www/pages/downloads/debian.html:71
-msgid ""
-"In the Quick Filter box, type in i2p and press enter. When "
-"i2p is returned in the results list, right click "
-"i2p and select Mark for Installation. After doing "
-"so you may see a Mark additional required changes? popup. If so,"
-" click Mark then Apply."
-msgstr ""
-"Dans la boîte \"filtre rapide\", tapez i2p et pressez "
-"entrée. Quand i2p est retournée dans la liste des résultats,"
-" faites un clic droit sur i2p et sélectionneez Marquer "
-"pour installation. Après avoir fait cela vous devirez voir un popup "
-"Marquer les changements additionnels requis ?. Si c'est le cas, "
-"cliquez Marquer puis Appliquer."
-
-#: i2p2www/pages/downloads/debian.html:77
-msgid ""
-"After the installation process completes you can move on to the next\n"
-"part of starting I2P and configuring "
-"it for your system."
-msgstr ""
-"Après que le processus d'installation soit terminé, vous pouvez passer à "
-"la prochaine ⏎\n"
-"partie de démarrer I2P et le "
-"configurer pour votre système."
-
-#: i2p2www/pages/downloads/debian.html:82
-msgid "Instructions for Debian Lenny and newer"
-msgstr "Instructions pour Debian Lenny et plus récentes"
-
-#: i2p2www/pages/downloads/debian.html:84
-msgid ""
-"For Squeeze you can follow the instructions here."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:86
-msgid ""
-"The steps below should be performed with root access (i.e., switching\n"
-"user to root with \"su\" or by prefixing each command with \"sudo\")."
-msgstr ""
-"Les étapes suivantes doivent être effectuées avec un accès root (ex: "
-"commuter⏎ \n"
-"de utilisateur vers root avec \"su\", ou en faisant précéder chaque "
-"commande par \"sudo\")."
-
-#: i2p2www/pages/downloads/debian.html:92
-msgid "Add the GPG key that signs the repository with the following command:"
-msgstr "Ajoutez la clé GPG qui signe le référentiel avec la commande suivante :"
-
-#: i2p2www/pages/downloads/debian.html:94
-msgid "You'll have output like the following if the command was successful:"
-msgstr "Si la commande a réussi, vous aurez une sortie comme celle-ci :"
-
-#: i2p2www/pages/downloads/debian.html:98
-msgid "Add the following entries to /etc/apt/sources.list.d/i2p.list"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:103
-msgid "Notify your package manager of the new PPA by entering"
-msgstr "Avertissez votre gestionnaire de paquets de la nouvelle PPA en entrant"
-
-#: i2p2www/pages/downloads/debian.html:105
-msgid ""
-"This command will retrieve the latest list of software from every\n"
-"repository enabled on your system, including the I2P PPA added in step\n"
-"1."
-msgstr ""
-"Cette commande va récupérer la dernière liste de logiciels depuis chaque "
-"⏎\n"
-"dépôt activé sur votre système, y compris le PPA I2P ajouté à l'étape ⏎ \n"
-"1."
-
-#: i2p2www/pages/downloads/debian.html:116
-#: i2p2www/pages/downloads/debian.html:147
-msgid ""
-"After the installation process completes you can move on to the next part"
-" of starting I2P and configuring it "
-"for your system."
-msgstr ""
-"Après la procédure d'installation terminée, vous pouvez passer à la "
-"partie suivante de  démarrer I2P  et "
-"le configurer pour votre système."
-
-#: i2p2www/pages/downloads/debian.html:120
-msgid "Instructions for Non-Linux / Non-x86"
-msgstr "Instructions pour non-Linux / non-x86"
-
-#: i2p2www/pages/downloads/debian.html:122
-msgid ""
-"The steps below should be performed with root access (i.e., switching\n"
-"user to root with \"su\" or by prefixing each command with "
-"\"sudo\")."
-msgstr ""
-"Les étapes ci-dessus devraient être faites en accès root (ex: basculer⏎\n"
-"user vers root avec \"su\" ou en précédant chaque commande "
-"par \"sudo\")."
-
-#: i2p2www/pages/downloads/debian.html:128
-#, python-format
-msgid ""
-"Download the i2p-router package from the PPA.\n"
-"Alternatively, there are unofficial packages available here for armel, armhf, and kfreebsd."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:135
-msgid ""
-"Make sure that you have Java installed. Running apt-get install"
-" default-jre should be sufficient."
-msgstr ""
-"Assurez-vous que vous avez Java d'installé. Lancer apt-get "
-"install default-jre devrait être suffisant."
-
-#: i2p2www/pages/downloads/debian.html:141
-#, python-format
-msgid ""
-"It is recommended to compile jbigi for your "
-"system to achieve better performance. Instructions are available here."
-msgstr ""
-"Il est recommendé de compiler jbigi pour votre "
-"système, afin d'obtenir de meilleures performances. Instructions "
-"disponibles içi."
-
-#: i2p2www/pages/downloads/debian.html:151
-#: i2p2www/pages/downloads/list.html:167
-msgid "Post-install work"
-msgstr "Travail post-installation"
-
-#: i2p2www/pages/downloads/debian.html:154
-msgid ""
-"Using these I2P packages the I2P router can be started in the following\n"
-"three ways:"
-msgstr ""
-"En utilisant ces paquetages I2P, le routeur I2P peut être lancé⏎\n"
-"des trois façons suivantes :"
-
-#: i2p2www/pages/downloads/debian.html:160
-msgid ""
-""on demand" using the i2prouter script. Simply run "
-""i2prouter\n"
-"start" from a command prompt. (Note: Do "
-"not use\n"
-"sudo or run it as root!)"
-msgstr ""
-"utiliser le script i2prouter "à la demande". Lancez simplement "
-""i2prouter⏎\n"
-"start" depuis une invite de commande. (Note: ne "
-"pas utiliser⏎\n"
-"sudo ni le lancer en tant que root !)"
-
-#: i2p2www/pages/downloads/debian.html:167
-msgid ""
-""on demand" without the java service wrapper\n"
-"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
-"nowrapper\".\n"
-"(Note: Do not\n"
-"use sudo or run it as root!)"
-msgstr ""
-""sur demande" sans le java service wrapper⏎\n"
-"(requis sur les systèmes non-Linux/non-x86) en lançant \"i2prouter-"
-"nowrapper\".⏎\n"
-"(Note: ne pas⏎\n"
-"utiliser sudo ni le lancer en tant que root !)"
-
-#: i2p2www/pages/downloads/debian.html:175
-msgid ""
-"as a service that automatically runs when your system boots, even\n"
-"before logging in. The service can be enabled with \"dpkg-"
-"reconfigure\n"
-"i2p\" as root or using sudo. This is the recommended means of "
-"operation."
-msgstr ""
-"en tant que service est lancé automatiquement quand le système boote, "
-"avant⏎\n"
-"même d'être loggé. Le service peut être activé avec \"dpkg-"
-"reconfigure⏎\n"
-" i2p\" en tant que root ou en utilisant sudo. C'est le moyen "
-"d'opération recommandé."
-
-#: i2p2www/pages/downloads/debian.html:183
-msgid ""
-"When installing for the first time, please remember to adjust your "
-"NAT/firewall\n"
-"if you can. The ports to forward can be found on the \n"
-"network configuration page in the router console. If guidance with "
-"respect to forwarding ports is needed,\n"
-"you may find portforward.com to be"
-" helpful."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:190
-msgid ""
-"Please review and adjust the bandwidth settings on the\n"
-"configuration page,\n"
-"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
-"conservative."
-msgstr ""
-"S'il vous plaît examinez etajustez les paramètres de bande "
-"passante sur la⏎\n"
-"page de configuration,⏎\n"
-"car les paramètres par défaut de 96 KB/s down / 40 KB/s up sont assez "
-"conservateurs."
-
-#: i2p2www/pages/downloads/debian.html:196
-#: i2p2www/pages/downloads/list.html:200
-#, python-format
-msgid ""
-"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
-"howto."
-msgstr ""
-"Si vous voulez atteindre des eepsites via votre navigateur, jettez un "
-"oeil sur la page configuration de proxy du "
-"navigateur pour un tutoriel facile."
-
-#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
-#: i2p2www/pages/global/nav.html:3
-msgid "Download"
-msgstr "Télécharger"
-
-#: i2p2www/pages/downloads/list.html:4
-msgid "Download I2P"
-msgstr "Télécharger I2P"
-
-#: i2p2www/pages/downloads/list.html:6
-msgid "Dependency"
-msgstr "Dépendance"
-
-#: i2p2www/pages/downloads/list.html:7
-#, python-format
-msgid ""
-"\n"
-"Java Runtime 1.5 or higher.\n"
-"(Oracle Java Version 6/7,\n"
-"OpenJDK 6/7, or\n"
-"IcedTea6/7\n"
-" recommended)\n"
-"
            \n"
-"Determine"
-" your installed Java version here\n"
-"or type java -version at your command prompt.\n"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:20
-msgid "Clean installs"
-msgstr "Installations propres"
-
-#: i2p2www/pages/downloads/list.html:27 i2p2www/pages/downloads/list.html:45
-#: i2p2www/pages/downloads/list.html:73 i2p2www/pages/downloads/list.html:135
-#: i2p2www/pages/downloads/list.html:265
-msgid "select alternate link"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:35
-msgid "Download that file and run it."
-msgstr "Télécharger ce fichier et l'exécuter."
-
-#: i2p2www/pages/downloads/list.html:53
-#, python-format
-msgid ""
-"Download that file and double-click it (if that works) or\n"
-"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
-"terminal to run the\n"
-"    installer.\n"
-"    You may be able to right-click and select\n"
-"    "Open with Java"."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:61 i2p2www/pages/downloads/list.html:89
-msgid "Command line (headless) install:"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:62
-#, python-format
-msgid ""
-"Download the %(i2pversion)s OSX graphical installer file above and\n"
-"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
-"from the command line."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:81
-#, python-format
-msgid ""
-"Download that file and double-click it (if that works) or\n"
-"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
-"terminal to run the\n"
-"    installer.\n"
-"    On some platforms you may be able to right-click and select\n"
-"    "Open with Java"."
-msgstr ""
-"Téléchargez ce fichier et double-cliquez le (si cela marche) ou⏎\n"
-"tapez java -jar i2pinstall_%(i2pversion)s.jar dans un "
-"terminal our lancez⏎\n"
-"l'installeur.⏎\n"
-"Sur certaines platformes vous pourriez pouvoir faire clic droit et "
-"sélectionner⏎\n"
-" "Open with Java"."
-
-#: i2p2www/pages/downloads/list.html:90
-#, python-format
-msgid ""
-"Download the graphical installer file above and\n"
-"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
-"from the command line."
-msgstr ""
-"Téléchargez l'installateur graphique depuis ci-dessus et⏎\n"
-"lancez java -jar i2pinstall_%(i2pversion)s.jar -console "
-"depuis la ligne de commande."
-
-#: i2p2www/pages/downloads/list.html:100
-msgid "Packages for Debian & Ubuntu are available."
-msgstr "Des packages pour Debian & Ubuntu sont disponibles."
-
-#: i2p2www/pages/downloads/list.html:115
-#, python-format
-msgid ""
-"The Android version of I2P is being actively developed.\n"
-"    The latest dev build is version 0.9.3-5_b2-API8, and is available "
-"from\n"
-"    sponge's eepsite -\n"
-"    scan or click the QR code."
-msgstr ""
-"La version Android de I2P est en cours de développement.⏎\n"
-"La build dev la plus récente est version 0.9.3-5_b2-API8, et est "
-"disponible depuis⏎\n"
-"sponge's eepsite -⏎\n"
-"scannez ou cliquez le code QR."
-
-#: i2p2www/pages/downloads/list.html:122
-msgid ""
-"The release and dev versions of the I2P APK are not compatible, as they\n"
-"      are signed by zzz and sponge respectively. Uninstall one before "
-"installing\n"
-"      the other."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:132
-msgid "Source package"
-msgstr "À partir des sources:"
-
-#: i2p2www/pages/downloads/list.html:143
-#, python-format
-msgid ""
-"Alternately, you can fetch the source from monotone\n"
-"    or via Git from git.repo.i2p or Github.\n"
-"    
            \n"
-"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
-"i2p-%(i2pversion)s ; ant pkg) then either\n"
-"    run the GUI installer or headless install as above."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:158
-#, python-format
-msgid ""
-"The files are signed by zzz,\n"
-"whose key is here."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:163
-msgid ""
-"I2P can also be downloaded from our project pages on Launchpad and Google Code."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:169
-msgid ""
-"After running the installer on windows, simply click on the \"Start I2P\""
-" button\n"
-"which will bring up the router console,\n"
-"which has further instructions."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:175
-msgid ""
-"On Unix-like systems, I2P can be started as a service\n"
-"using the \"i2prouter\" script, located in the directory you selected for"
-" I2P.\n"
-"Changing to that directory in a console and issuing \"sh i2prouter "
-"status\"\n"
-"should tell you the router's status. The arguments \"start\", \"stop\" "
-"and \"restart\"\n"
-"control the service. The router console\n"
-"can be accessed at its usual location.\n"
-"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
-" is not supported,\n"
-"start the router with \"sh runplain.sh\" instead."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:186
-#, python-format
-msgid ""
-"When installing for the first time, please remember to adjust your "
-"NAT/firewall\n"
-"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
-"described here among other ports.\n"
-"If you have successfully opened your port to inbound TCP, also enable "
-"inbound TCP on the\n"
-"configuration page."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:194
-msgid ""
-"Also, please review and adjust the bandwidth settings on the\n"
-"configuration page,\n"
-"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:204
-msgid "Updates from earlier releases:"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:206
-msgid "Both automatic and manual upgrades are available for the release."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:211
-msgid "Automatic updates"
-msgstr "Mises à jour automatiques"
-
-#: i2p2www/pages/downloads/list.html:213
-msgid ""
-"If you are running 0.7.5 or later, your router should detect the\n"
-"new release. To upgrade simply click the 'Download Update' button on your"
-" router console\n"
-"when it appears."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:219
-msgid ""
-"Due to a bug in release 0.7.6, those whose first I2P installation was "
-"that version\n"
-"and have not upgraded manually\n"
-"may get a \"downloaded version is not greater than current version\" "
-"error,\n"
-"and should use the manual update method below."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:227
-#, python-format
-msgid ""
-"If you are running 0.7.4 or earlier, please see\n"
-"the 0.7.5 release notes\n"
-"for important information about how to configure your router to "
-"automatically\n"
-"receive the release."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:235
-#, python-format
-msgid ""
-"If you are running 0.6.1.30 or earlier, please see\n"
-"instructions\n"
-"for important information about how to configure your router to "
-"automatically\n"
-"receive the release."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:244
-#, python-format
-msgid ""
-"If you have reconfigured your router following the instructions, you should see a link on your"
-" \n"
-"    router console "
-"allowing\n"
-"    you to download and install the new release by just clicking on that\n"
-"    link."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:252
-msgid "Alternately, you can use the manual method specified below."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:262
-msgid "Manual updates"
-msgstr "Mises à jour manuelles"
-
-#: i2p2www/pages/downloads/list.html:275
-msgid ""
-"Download that file to your I2P\n"
-"    installation directory and rename as i2pupdate.zip.\n"
-"    (alternately, you can get the source as above and run \"ant "
-"updater\", then copy the\n"
-"    resulting i2pupdate.zip to your I2P installation directory).  You do"
-" \n"
-"    NOT need to unzip that file."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:284
-msgid "Click \"Restart\""
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:289
-msgid "Grab a cup of coffee and come back in 11 minutes"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:297
-#, python-format
-msgid ""
-"The file is signed by zzz,\n"
-"whose key is here."
-msgstr ""
-"Le fichier est signé par zzz,⏎\n"
-"dont la clé est içi."
-
-#: i2p2www/pages/downloads/list.html:302
-msgid "Previous Releases"
-msgstr "Précédentes releases"
-
-#: i2p2www/pages/downloads/list.html:304
-#, python-format
-msgid ""
-"Previous releases are available on Google "
-"Code\n"
-"and Launchpad\n"
-"and within the I2P network on %(echelon)s."
-msgstr ""
-"Les précédentes releases sont disponibles sur Google "
-"Code⏎\n"
-"et Launchpad⏎\n"
-"et à l'intérieur du réseau I2P sur %(echelon)s."
-
-#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
-msgid "Mirror selection"
-msgstr "Sélection de miroir"
-
-#: i2p2www/pages/downloads/select.html:5
-msgid "File:"
-msgstr "Fichier:"
-
-#: i2p2www/pages/downloads/select.html:10
-msgid "Any mirror"
-msgstr "N'importe quel miroir"
-
-#: i2p2www/pages/global/bounty.html:19
-msgid ""
-"To claim the bounty the author must not be paid by other organizations\n"
-"or teams for this work (e.g. GSoC students are not valid)."
-msgstr ""
-"Pour réclamer la récompense, l'auteur ne doit pas être payé par d'autres "
-"organisations ⏎\n"
-"ni des équipes pour ce travail (par exemple, les étudiants GSoC ne sont "
-"pas valides)."
-
-#: i2p2www/pages/global/bounty.html:29
-#, python-format
-msgid ""
-"Bounty amounts may be increased by further donations.  Do\n"
-"you think these are important? Add in your "
-"donation, \n"
-"marking the amount for the %(donatename)s bounty!"
-msgstr ""
-"Les montants des récompenses peuvent être augmentés par de nouveaux dons."
-" Pensez-⏎\n"
-"vous que ceux-ci sont importants? Ajouter votre "
-"donation, ⏎\n"
-"en marquant le montant pour le %(donatename)s récompense-bounty !"
-
-#: i2p2www/pages/global/error_404.html:3
-msgid "Not found"
-msgstr "Pas trouvé"
-
-#: i2p2www/pages/global/error_404.html:9
-msgid ""
-"Yep... the resource, you were searching for, is named differently, "
-"doesn't exist or was removed."
-msgstr ""
-"Oui... la ressource que vous cherchiez, est nommée différemment, n'existe"
-" pas, ou a été supprimée."
-
-#: i2p2www/pages/global/error_500.html:5
-msgid "Server error"
-msgstr "Erreur serveur"
-
-#: i2p2www/pages/global/error_500.html:13
-msgid "500 Server error"
-msgstr "Erreur serveur n°500"
-
-#: i2p2www/pages/global/error_500.html:17
-msgid "Umm... the server encountered some sort of error."
-msgstr "Hum... le serveur a rencontré une sorte d'erreur."
-
-#: i2p2www/pages/global/footer.html:2
-msgid "Mirrors"
-msgstr "Miroirs"
-
-#: i2p2www/pages/global/footer.html:10
-msgid "Secure"
-msgstr "Sécurisé"
-
-#: i2p2www/pages/global/footer.html:16
-msgid "Misc."
-msgstr "Divers."
-
-#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
-msgid "Links"
-msgstr "Liens"
-
-#: i2p2www/pages/global/footer.html:20
-msgid "Impressum"
-msgstr "Impressum"
-
-#: i2p2www/pages/global/footer.html:24
-msgid "T-Shirts!"
-msgstr "T-Shirts!"
-
-#: i2p2www/pages/global/footer.html:26
-msgid "Europe"
-msgstr "Europe"
-
-#: i2p2www/pages/global/footer.html:27
-msgid "USA"
-msgstr "USA"
-
-#: i2p2www/pages/global/footer.html:31
-#: i2p2www/pages/site/get-involved/donate.html:2
-#: i2p2www/pages/site/get-involved/index.html:74
-msgid "Donate"
-msgstr "Faire un don"
-
-#: i2p2www/pages/global/layout.html:29
-msgid "Skip navigation"
-msgstr "Passer la navigation"
-
-#: i2p2www/pages/global/layout.html:32
-msgid "I2P Logo"
-msgstr "Logo I2P"
-
-#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
-#: i2p2www/pages/site/about/intro.html:4
-msgid "The Invisible Internet Project"
-msgstr "The Invisible Internet Project (le projet internet invisible)"
-
-#: i2p2www/pages/global/layout.html:56
-#, python-format
-msgid ""
-"This page was last updated in %(lastupdated)s and is accurate for router "
-"version %(accuratefor)s."
-msgstr ""
-"Cette page a été mise à jour en %(lastupdated)s et est correcte pour la "
-"version de routeur %(accuratefor)s."
-
-#: i2p2www/pages/global/layout.html:60
-#, python-format
-msgid "This page was last updated in %(lastupdated)s."
-msgstr "Cette page a étée mise à jour dernièrement en %(lastupdated)s."
-
-#: i2p2www/pages/global/layout.html:64
-#, python-format
-msgid "This page is accurate for router version %(accuratefor)s."
-msgstr "Cette page est à jour pour la version de routeur %(accuratefor)s."
-
-#: i2p2www/pages/global/macros:19
-msgid "Previous"
-msgstr ""
-
-#: i2p2www/pages/global/macros:34
-msgid "Next"
-msgstr ""
-
-#: i2p2www/pages/global/macros:41
-msgid "Posted in"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:4
-msgid "About"
-msgstr "A propos"
-
-#: i2p2www/pages/global/nav.html:6
-msgid "Introduction to I2P"
-msgstr "Introduction à I2P"
-
-#: i2p2www/pages/global/nav.html:7
-msgid "Comparisons"
-msgstr "Comparaisons"
-
-#: i2p2www/pages/global/nav.html:9
-msgid "Overview of comparisons"
-msgstr "Vue d'ensemble des comparaisons"
-
-#: i2p2www/pages/global/nav.html:13
-msgid "Other anonymous networks"
-msgstr "Autres réseaux anonymes"
-
-#: i2p2www/pages/global/nav.html:16
-#: i2p2www/pages/site/get-involved/index.html:29
-msgid "Documentation"
-msgstr "Documentation"
-
-#: i2p2www/pages/global/nav.html:18
-msgid "Documentation index"
-msgstr "Index documentation"
-
-#: i2p2www/pages/global/nav.html:19 i2p2www/pages/site/about/intro.html:17
-msgid "How does it work?"
-msgstr "Comment ça marche ?"
-
-#: i2p2www/pages/global/nav.html:21
-msgid "Gentle intro"
-msgstr "Intro douce"
-
-#: i2p2www/pages/global/nav.html:22
-msgid "Tech intro"
-msgstr "Intro technique"
-
-#: i2p2www/pages/global/nav.html:23
-msgid "Threat model"
-msgstr "Modèle de menace"
-
-#: i2p2www/pages/global/nav.html:24
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:292
-msgid "Garlic routing"
-msgstr "Routage en oignon"
-
-#: i2p2www/pages/global/nav.html:25
-msgid "Network database"
-msgstr "Base de données réseau"
-
-#: i2p2www/pages/global/nav.html:26
-msgid "Tunnel routing"
-msgstr "Routage tunnel"
-
-#: i2p2www/pages/global/nav.html:27
-#: i2p2www/pages/site/docs/tunnels/unidirectional.html:21
-msgid "Peer selection"
-msgstr "Sélection de pair"
-
-#: i2p2www/pages/global/nav.html:28
-#: i2p2www/pages/site/docs/how/tech-intro.html:17
-#: i2p2www/pages/site/docs/how/tech-intro.html:458
-msgid "Cryptography"
-msgstr "Cryptographie"
-
-#: i2p2www/pages/global/nav.html:29
-msgid "ElGamal/AES+SessionTags"
-msgstr "ElGamal/AES+SessionTags"
-
-#: i2p2www/pages/global/nav.html:32 i2p2www/pages/global/nav.html:116
-#: i2p2www/pages/site/docs/spec/configuration.html:75
-#: i2p2www/pages/site/get-involved/index.html:48
-msgid "Applications"
-msgstr "Applications"
-
-#: i2p2www/pages/global/nav.html:34
-msgid "Supported applications"
-msgstr "Applications supportées"
-
-#: i2p2www/pages/global/nav.html:35
-msgid "Bittorrent"
-msgstr "Bittorrent"
-
-#: i2p2www/pages/global/nav.html:38
-#: i2p2www/pages/site/docs/api/streaming.html:58
-msgid "API"
-msgstr "API"
-
-#: i2p2www/pages/global/nav.html:46 i2p2www/pages/global/nav.html:77
-#: i2p2www/pages/site/docs/how/tech-intro.html:808
-msgid "Streaming library"
-msgstr "Librarie streaming"
-
-#: i2p2www/pages/global/nav.html:47
-msgid "Ministreaming library"
-msgstr "Librarie ministreaming"
-
-#: i2p2www/pages/global/nav.html:48 i2p2www/pages/global/nav.html:71
-#: i2p2www/pages/site/docs/index.html:88
-#: i2p2www/pages/site/docs/api/datagrams.html:2
-#: i2p2www/pages/site/get-involved/develop/applications.html:277
-msgid "Datagrams"
-msgstr "Datagrammes"
-
-#: i2p2www/pages/global/nav.html:52
-msgid "Protocols"
-msgstr "Protocoles"
-
-#: i2p2www/pages/global/nav.html:54
-msgid "Protocol stack"
-msgstr "La pile de protocole"
-
-#: i2p2www/pages/global/nav.html:59
-#: i2p2www/pages/site/docs/how/cryptography.html:394
-msgid "Transports"
-msgstr "Transports"
-
-#: i2p2www/pages/global/nav.html:61 i2p2www/pages/site/docs/index.html:158
-msgid "Transport layer overview"
-msgstr "Aperçu couche transport"
-
-#: i2p2www/pages/global/nav.html:66
-msgid "Specifications"
-msgstr "Spécifications"
-
-#: i2p2www/pages/global/nav.html:68
-msgid "Blockfile"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:69
-msgid "Common structures"
-msgstr "Structures communes"
-
-#: i2p2www/pages/global/nav.html:70
-msgid "Configuration files"
-msgstr "Fichiers de configuration"
-
-#: i2p2www/pages/global/nav.html:72
-msgid "GeoIP files"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:78
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:230
-msgid "Tunnel creation"
-msgstr "Création de tunnel"
-
-#: i2p2www/pages/global/nav.html:79
-msgid "Tunnel messages"
-msgstr "Messages tunnel "
-
-#: i2p2www/pages/global/nav.html:80
-msgid "Software updates"
-msgstr "Mises à jour logicielles"
-
-#: i2p2www/pages/global/nav.html:83 i2p2www/pages/site/docs/index.html:139
-#: i2p2www/pages/site/docs/how/tech-intro.html:14
-#: i2p2www/pages/site/docs/how/tech-intro.html:228
-msgid "Tunnels"
-msgstr "Tunnels"
-
-#: i2p2www/pages/global/nav.html:85
-msgid "Tunnel implementation"
-msgstr "Implémentation tunnel"
-
-#: i2p2www/pages/global/nav.html:86
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:288
-msgid "Unidirectional tunnels"
-msgstr "Tunnels unidirectionels"
-
-#: i2p2www/pages/global/nav.html:87
-msgid "Old implementation"
-msgstr "Ancienne implémentation"
-
-#: i2p2www/pages/global/nav.html:90
-msgid "Naming and addressbook"
-msgstr "Nomination et carnet d'adresses"
-
-#: i2p2www/pages/global/nav.html:94 i2p2www/pages/site/about/team.html:2
-msgid "Team"
-msgstr "Équipe"
-
-#: i2p2www/pages/global/nav.html:96
-msgid "Hall of Fame"
-msgstr "Temple de la renommée - hall of fame"
-
-#: i2p2www/pages/global/nav.html:97
-msgid "Academic papers and peer review"
-msgstr "Documents universitaires et examen par des pairs"
-
-#: i2p2www/pages/global/nav.html:98
-msgid "Presentations, tutorials and articles"
-msgstr "Présentations, tutoriels et articles"
-
-#: i2p2www/pages/global/nav.html:99
-msgid "Contact us"
-msgstr "Contactez-nous"
-
-#: i2p2www/pages/global/nav.html:102
-msgid "Help"
-msgstr "Aide"
-
-#: i2p2www/pages/global/nav.html:104
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
-msgid "FAQ"
-msgstr "FAQ"
-
-#: i2p2www/pages/global/nav.html:105
-msgid "How to browse I2P"
-msgstr "Comment naviguer sur I2P"
-
-#: i2p2www/pages/global/nav.html:106 i2p2www/pages/site/about/glossary.html:2
-msgid "Glossary"
-msgstr "Glossaire"
-
-#: i2p2www/pages/global/nav.html:107
-#: i2p2www/pages/site/about/performance/index.html:2
-#: i2p2www/pages/site/docs/index.html:183
-#: i2p2www/pages/site/get-involved/todo.html:52
-#: i2p2www/pages/site/get-involved/todo.html:456
-msgid "Performance"
-msgstr "Performance"
-
-#: i2p2www/pages/global/nav.html:108 i2p2www/pages/site/contact.html:22
-msgid "Forums"
-msgstr "Forums"
-
-#: i2p2www/pages/global/nav.html:111
-msgid "Volunteer"
-msgstr "Volontaire"
-
-#: i2p2www/pages/global/nav.html:113
-msgid "Get involved!"
-msgstr "Impliquez-vous !"
-
-#: i2p2www/pages/global/nav.html:114
-msgid "Develop"
-msgstr "Développer"
-
-#: i2p2www/pages/global/nav.html:117
-#: i2p2www/pages/site/get-involved/develop/licenses.html:2
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115
-msgid "Licenses"
-msgstr "Licenses"
-
-#: i2p2www/pages/global/nav.html:118
-msgid "Release signing keys"
-msgstr "Relâcher clés de signature"
-
-#: i2p2www/pages/global/nav.html:119
-msgid "Signed keys"
-msgstr "Clés signées"
-
-#: i2p2www/pages/global/nav.html:120
-msgid "Developers keys"
-msgstr "Clés des développeurs"
-
-#: i2p2www/pages/global/nav.html:121 i2p2www/pages/site/docs/index.html:223
-msgid "Bug tracker"
-msgstr "Traqueur de bugs"
-
-#: i2p2www/pages/global/nav.html:124
-msgid "Academic research"
-msgstr "Recherche universitaire"
-
-#: i2p2www/pages/global/nav.html:125
-msgid "Guides"
-msgstr "Guides"
-
-#: i2p2www/pages/global/nav.html:127
-msgid "New developers"
-msgstr "Nouveaux développeurs"
-
-#: i2p2www/pages/global/nav.html:128
-#: i2p2www/pages/site/get-involved/guides/ides.html:2
-msgid "Using an IDE with I2P"
-msgstr "Utiliser un IDE avec I2P"
-
-#: i2p2www/pages/global/nav.html:129
-msgid "Developer guidelines and coding style"
-msgstr "Guide du développeur et style de programmation"
-
-#: i2p2www/pages/global/nav.html:130
-#: i2p2www/pages/site/get-involved/guides/monotone.html:2
-msgid "Monotone"
-msgstr "Monotone"
-
-#: i2p2www/pages/global/nav.html:131
-msgid "New translators"
-msgstr "Nouveaux traducteurs"
-
-#: i2p2www/pages/global/nav.html:134
-#: i2p2www/pages/site/get-involved/bounties/index.html:2
-msgid "Bounties"
-msgstr "Projets récompensés - bounties"
-
-#: i2p2www/pages/global/nav.html:135 i2p2www/pages/meetings/index.html:2
-msgid "Meetings"
-msgstr "Meetings"
-
-#: i2p2www/pages/global/nav.html:136
-#: i2p2www/pages/site/get-involved/roadmap.html:2
-msgid "Roadmap"
-msgstr "Feuille de route (roadmap)"
-
-#: i2p2www/pages/global/nav.html:137
-msgid "Task list"
-msgstr "Liste de tâches"
-
-#: i2p2www/pages/global/nav.html:140
-msgid "Language"
-msgstr "Langue"
-
-#: i2p2www/pages/meetings/index.html:4
-msgid "I2P Meetings ATOM Feed"
-msgstr "Flux ATOM des meetings I2P"
-
-#: i2p2www/pages/meetings/index.html:7
-msgid "Logs of past I2P meetings"
-msgstr "Logs des meetings I2P précédents"
-
-#: i2p2www/pages/meetings/index.html:9
-msgid "Meetings are currently on hold until a more suitable time can be chosen."
-msgstr ""
-
-#: i2p2www/pages/meetings/index.html:13
-#, python-format
-msgid ""
-"If you have something to discuss, please find the developers on IRC in "
-"#i2p-dev.\n"
-"Status updates from developers are also "
-"available."
-msgstr ""
-"Si vous avez quelque chose à discuter, s'il vous plaît trouver les "
-"développeurs sur IRC dans #I2P-dev. ⏎ Status "
-"updates dans lequel des développeurs sont également disponibles."
-
-#: i2p2www/pages/meetings/show.html:2
-#, python-format
-msgid "I2P Development Meeting %(id)s"
-msgstr ""
-
-#: i2p2www/pages/meetings/show.html:10
-msgid "Full IRC Log"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:2
-msgid "Contact"
-msgstr "Contac"
-
-#: i2p2www/pages/site/contact.html:5
-msgid ""
-"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
-" to this network is set up with new router installs.\n"
-"  We are also present on multiple standard networks like OFTC,\n"
-"  EIN and Freenode.\n"
-"  All I2P-related channels on all these network are linked to the main "
-"channels on Irc2P via relay bots."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:13
-msgid "Channel list:"
-msgstr "Liste canal :"
-
-#: i2p2www/pages/site/contact.html:15
-msgid "General i2p discussion"
-msgstr "Discussion i2p générale"
-
-#: i2p2www/pages/site/contact.html:16
-msgid "Offtopic"
-msgstr "Hors sujet"
-
-#: i2p2www/pages/site/contact.html:17
-msgid "Development talk"
-msgstr "Discussion développement"
-
-#: i2p2www/pages/site/contact.html:18
-msgid "Help channel"
-msgstr "Canal d'aide"
-
-#: i2p2www/pages/site/contact.html:23
-#, python-format
-msgid ""
-"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
-" place to start with inquiries, if the dev IRC channel is inactive."
-msgstr ""
-"La plupart des discussions sur le développement de I2P se passe sur le I2P developper forum. C'est généralement le "
-"meilleur endroit pour commencer avec requêtes, si le canal IRC dev est "
-"inactif."
-
-#: i2p2www/pages/site/contact.html:27
-msgid "Mailing lists"
-msgstr "Mailing lists"
-
-#: i2p2www/pages/site/contact.html:28
-msgid ""
-"I2P does have a mailing list, but it is rarely used as the current small "
-"team of developers prefer to communicate via IRC or the developer forum. "
-"This may change in future."
-msgstr ""
-"I2P a une liste de diffusion, mais elle est rarement utilisée car "
-"l'actuelle petite équipe de développeurs préfèrent communiquer via IRC ou"
-" le forum des développeurs. Cela pourrait changer à l'avenir."
-
-#: i2p2www/pages/site/contact.html:33
-msgid "Subscribing"
-msgstr "S'abonner"
-
-#: i2p2www/pages/site/contact.html:34
-msgid ""
-"To subscribe to a mailing list, go to the list information page (linked "
-"below) and fill out the form. I2P-internal email addresses "
-"(foobar@mail.i2p) can be used."
-msgstr ""
-"Pour vous abonner à une mailing list, allez à la page d'information de la"
-" liste (lien ci-dessous) et remplissez le formulaire. Les adresses e-mail"
-" internes à I2P (ex: foobar@mail.i2p) peuvent être utilisées."
-
-#: i2p2www/pages/site/contact.html:38
-msgid "Unsubscribing"
-msgstr "Se désinscrire"
-
-#: i2p2www/pages/site/contact.html:39
-msgid ""
-"To unsubscribe from a mailing list or edit your subscription options, go "
-"to the list information page (linked below) and enter your subscription "
-"email address."
-msgstr ""
-"Pour vous désabonner d'une mailing list ou modifier vos options "
-"d'abonnement, allez à la page d'information de la liste (lien ci-dessous)"
-" et entrez votre adresse courriel d'abonnement."
-
-#: i2p2www/pages/site/contact.html:43
-msgid "Lists"
-msgstr "Listes"
-
-#: i2p2www/pages/site/contact.html:46
-msgid "Archive"
-msgstr "Archive"
-
-#: i2p2www/pages/site/contact.html:47
-msgid ""
-"General I2P discussion - anything that doesn't fit in a different list "
-"goes here."
-msgstr ""
-"Discussions générales I2P - tout ce qui ne rentre pas dans une autre "
-"liste va ici."
-
-#: i2p2www/pages/site/contact.html:53
-msgid ""
-"You don't like mailing lists? Then this is for you. All mailing lists are"
-" available via NNTP as well."
-msgstr ""
-"Vous n'aimez pas les listes de diffusion? Alors ceci est pour vous. Tous "
-"les listes de diffusion sont disponibles via NNTP aussi."
-
-#: i2p2www/pages/site/contact.html:58
-msgid "Group-List-mapping:"
-msgstr "Cartographie-group-list :"
-
-#: i2p2www/pages/site/contact.html:62
-msgid "Servers:"
-msgstr "Serveurs:"
-
-#: i2p2www/pages/site/faq.html:2
-msgid "Frequently Asked Questions"
-msgstr "Foire Aux Questions (Frequently Asked Questions)"
-
-#: i2p2www/pages/site/faq.html:4
-#: i2p2www/pages/site/docs/how/threat-model.html:121
-msgid "Index"
-msgstr "Index"
-
-#: i2p2www/pages/site/faq.html:7
-msgid "General"
-msgstr "Général"
-
-#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
-msgid "What systems will I2P run on?"
-msgstr "Sur quels systèmes I2P va fonctionner ?"
-
-#: i2p2www/pages/site/faq.html:10
-msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
-msgstr ""
-"Qu'est-ce qu'un \"eepsite\" et comment dois-je configurer mon navigateur "
-"pour pouvoir les utiliser ?"
-
-#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:263
-msgid "My router has very few active peers, is this OK?"
-msgstr "Mon routeur a très peu de pairs actifs, est-ce OK ?"
-
-#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:498
-msgid "What do the Active x/y numbers mean in the router console?"
-msgstr ""
-"Qu'est-ce que le nombre \"Actifs: x / y\" signifie dans la console du "
-"routeur ?"
-
-#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:225
-msgid ""
-"My active peers / known peers / participating tunnels / connections / "
-"bandwidth vary dramatically over time! Is anything wrong?"
-msgstr ""
-"Mes pairs actifs / pairs connus / tunnels participants / connexions / "
-"bande passante  varient considérablement au fil du temps ! Est-ce quelque"
-" chose va mal ?"
-
-#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:348
-msgid "Is using an outproxy safe?"
-msgstr "Est-t-il risqué d'utiliser un proxy sortant (outproxy) ?"
-
-#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:374
-msgid "Most of the eepsites within I2P are down?"
-msgstr "La plupart des eepsites dans I2P sont hors d'accès ?"
-
-#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:527
-msgid "What ports does I2P use?"
-msgstr "Quels ports I2P utilise ?"
-
-#: i2p2www/pages/site/faq.html:17
-msgid "Why is I2P listening for connections on port 32000?"
-msgstr "Pourquoi est-ce que I2P écoute des connexions sur le port 32000 ?"
-
-#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
-msgid "I think I found a bug, where can I report it?"
-msgstr "Je pense avoir trouvé un bug, où puis-je le signaler?"
-
-#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:107
-msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
-msgstr ""
-"Qu'est-il arrivé à *.i2p.net ? Qu'est-il arrivé à jrandom? I2P est-il "
-"mort?"
-
-#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:845
-msgid "I have a question!"
-msgstr "J'ai une question !"
-
-#: i2p2www/pages/site/faq.html:22
-#: i2p2www/pages/site/docs/api/streaming.html:292
-msgid "Setup"
-msgstr "Paramétrage"
-
-#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:232
-msgid ""
-"My router has been up for several minutes and has zero or very few "
-"connections"
-msgstr ""
-"Mon routeur est en ligne depuis plusieurs minutes mais a zéro ou très peu"
-" de connexions"
-
-#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:390
-msgid "Why is I2P so slow?"
-msgstr "Pourquoi I2P est-il si lent ?"
-
-#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
-msgid ""
-"I'm missing lots of hosts in my addressbook. What are some good "
-"subscription links?"
-msgstr ""
-"Il me manque beaucoup d'hôtes dans mon carnet d'adresses. Quels sont les "
-"bons liens d'abonnement ?"
-
-#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:383
-msgid "How do I set up my own eepsite?"
-msgstr "Comment puis-je créer mon propre eepsite ?"
-
-#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:416
-msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
-msgstr "Questions sur les plugins I2P pour Bittorrent / I2PSnark / Azureus"
-
-#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:423
-msgid "How do I connect to IRC within I2P?"
-msgstr "Comment puis-je me connecter à IRC au sein de I2P ?"
-
-#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:281
-msgid "I can't access regular Internet sites through I2P."
-msgstr "Je ne peux pas accéder à des sites réguliers d'Internet à travers I2P."
-
-#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:296
-msgid "I can't access https:// or ftp:// sites through I2P."
-msgstr "Je ne peux pas accéder à des sites https:// ni ftp:// par I2P."
-
-#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:506
-msgid "Is it possible to use I2P as a SOCKS proxy?"
-msgstr "Est-il possible d'utiliser I2P en tant que proxy SOCKS ?"
-
-#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:489
-msgid "How do I configure my browser?"
-msgstr "Comment dois-je configurer mon navigateur ?"
-
-#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:434
-msgid ""
-"How can I access the web console from my other machines or password "
-"protect it?"
-msgstr ""
-"Comment puis-je accéder à la console Web à partir de mes autres machines,"
-" ou la protéger par mot de passe ?"
-
-#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:474
-msgid "How can I use applications from my other machines?"
-msgstr "Comment puis-je utiliser des applications depuis mes autres machines?"
-
-#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:748
-msgid "How do I reseed manually?"
-msgstr "Comment puis-je réensemencer (reseed) manuellement ?"
-
-#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:124
-msgid "My router is using too much CPU?!?"
-msgstr "Mon routeur utilise trop de CPU ?!?"
-
-#: i2p2www/pages/site/faq.html:39
-msgid "Misconception"
-msgstr "Méprise"
-
-#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:366
-msgid ""
-"How do I access IRC, BitTorrent, or other services on the regular "
-"Internet?"
-msgstr ""
-"Comment puis-je accéder à IRC, BitTorrent, ou d'autres services sur "
-"l'Internet régulier ?"
-
-#: i2p2www/pages/site/faq.html:42
-msgid ""
-"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
-"want it to be."
-msgstr ""
-"Est-ce que mon routeur est un \"nœud de sortie\" (outproxy) vers "
-"l'Internet régulier ? Je ne veux pas qu'il le soit."
-
-#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:188
-msgid ""
-"I am opposed to certain types of content. How do I keep from "
-"distributing, storing, or accessing them?"
-msgstr ""
-"Je suis opposé à certains types de contenus. Comment puis-je éviter d'en "
-"distribuer, d'en stocker ou d'y accéder ?"
-
-#: i2p2www/pages/site/faq.html:45
-msgid "Errors and Their Solutions"
-msgstr "Erreurs et leurs solutions"
-
-#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:784
-msgid ""
-"I'm using FreeBSD and when I start I2P I receive an error about "
-"libm.so.4!"
-msgstr ""
-"J'utilise FreeBSD et quand je lance I2P, je reçois une erreur concernant "
-"libm.so.4 !"
-
-#: i2p2www/pages/site/faq.html:48
-msgid ""
-"In wrapper.log I see an error stating Protocol family "
-"unavailable when I2P is loading"
-msgstr ""
-"Dans wrapper.log je vois une erreur communiquant "
-"Protocol family unavailable lorsque I2P se lance"
-
-#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
-#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:108
-#: i2p2www/pages/site/faq.html:125 i2p2www/pages/site/faq.html:189
-#: i2p2www/pages/site/faq.html:226 i2p2www/pages/site/faq.html:233
-#: i2p2www/pages/site/faq.html:264 i2p2www/pages/site/faq.html:273
-#: i2p2www/pages/site/faq.html:282 i2p2www/pages/site/faq.html:297
-#: i2p2www/pages/site/faq.html:349 i2p2www/pages/site/faq.html:367
-#: i2p2www/pages/site/faq.html:375 i2p2www/pages/site/faq.html:384
-#: i2p2www/pages/site/faq.html:391 i2p2www/pages/site/faq.html:417
-#: i2p2www/pages/site/faq.html:424 i2p2www/pages/site/faq.html:435
-#: i2p2www/pages/site/faq.html:475 i2p2www/pages/site/faq.html:482
-#: i2p2www/pages/site/faq.html:490 i2p2www/pages/site/faq.html:499
-#: i2p2www/pages/site/faq.html:507 i2p2www/pages/site/faq.html:528
-#: i2p2www/pages/site/faq.html:736 i2p2www/pages/site/faq.html:749
-#: i2p2www/pages/site/faq.html:785 i2p2www/pages/site/faq.html:817
-#: i2p2www/pages/site/faq.html:846 i2p2www/pages/site/get-involved/todo.html:16
-#: i2p2www/pages/site/get-involved/todo.html:28
-#: i2p2www/pages/site/get-involved/todo.html:52
-msgid "link"
-msgstr "lien"
-
-#: i2p2www/pages/site/faq.html:53
-#, python-format
-msgid ""
-"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
-"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
-"(or better) with 128MB of RAM (or more). A chart comparing the performance of"
-" the various JREs can be found at http://%(trac)s/wiki/java, but in "
-"short: it's at all possible, use Sun/Oracle Java or OpenJDK."
-msgstr ""
-"Bien qu'il ai été rapporté que I2P puisse fonctionner sur un maigre PC "
-"tel qu'un Pentium II bas de gamme avec 64 Mo de RAM, vous aurez une bien "
-"meilleure expérience sur un Pentium III (ou mieux) avec 128 Mo de RAM (ou"
-" plus). Un document chart comparing"
-" the performance des différents JRE peut être trouvé à l'adresse http://%(trac)s/wiki/java, mais en"
-" bref : c'est possible, utiliser le Java de Sun/Oracle ou OpenJDK."
-
-#: i2p2www/pages/site/faq.html:57
-msgid ""
-"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
-"underway to bring I2P to the Android platform."
-msgstr ""
-"I2P a été testé sur Windows, Linux, FreeBSD (voir la note ci-dessous), OSX, et OpenSolaris. Il ya des "
-"travaux en cours pour porter I2P sur la plate-forme Android."
-
-#: i2p2www/pages/site/faq.html:65
-msgid "Here are some places, pick one or more."
-msgstr "Voici quelques endroits, choisissez un ou plusieurs."
-
-#: i2p2www/pages/site/faq.html:71
-msgid "Discuss with the developers on IRC in #i2p-dev"
-msgstr "Discutez avec les développeurs sur IRC dans #I2P-dev"
-
-#: i2p2www/pages/site/faq.html:75
-msgid "Please include relevant information from the router logs and wrapper logs."
-msgstr ""
-"S'il vous plaît inclure des informations pertinentes à partir des "
-"journaux de routage (router logs) et les journaux d'encapsulation "
-"(wrapper logs)."
-
-#: i2p2www/pages/site/faq.html:81
-msgid ""
-"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
-"updated rarely.\n"
-"If you don't have another subscription, you may often have to use "
-"\"jump\" links which\n"
-"is annoying."
-msgstr ""
-"L'abonnement par défaut est à http://www.i2p2.i2p/hosts.txt qui est "
-"rarement mis à jour.⏎\n"
-"Si vous n'avez pas d'autre abonnement, vous risquez d'avoir souvent à "
-"utiliser des liens «jump»⏎\n"
-"ce qui est ennuyeux."
-
-#: i2p2www/pages/site/faq.html:87
-msgid ""
-"Here are some other public addressbook subscription links. You may wish "
-"to add one or two\n"
-"to your susidns "
-"subscription list.\n"
-"You don't need to add all of them, as they sync with each other "
-"periodically.\n"
-"The links using a cgi-bin application employ various strategies to "
-"minimize\n"
-"the number of duplicate addresses delivered, so they should be more "
-"efficient.\n"
-"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
-" malicious\n"
-"subscription could give you incorrect addresses. So think about whether "
-"you\n"
-"want to trust any of these.\n"
-"The operators of these services may have various policies for listing "
-"hosts.\n"
-"Presence on this list does not imply endorsement."
-msgstr ""
-"Voici quelques autres liens d'abonnement du carnet d'adresses publiques. "
-"Vous pouvez ajouter un ou deux ⏎ \n"
-"à votre liste"
-" de souscription susidns. ⏎\n"
-"Vous n'avez pas besoin de les ajouter tous, car ils se synchronisent "
-"mutuellement à intervalles réguliers. ⏎ \n"
-"Les liens utilisant une application cgi-bin emploient diverses stratégies"
-" pour réduire ⏎ \n"
-"le nombre d'adresses livrées en double, elles doivent donc être plus "
-"efficace. ⏎ \n"
-"Notez que l'abonnement à un service de hosts.txt est un acte de "
-"«confiance», car un ⏎\n"
-"abonnement malveillant pourrait vous donner des adresses incorrectes. "
-"Alors, pensez-y si vous⏎\n"
-"voulez faire confiance à l'un d'eux. ⏎\n"
-"Les opérateurs de ces services peuvent avoir diverses politiques de "
-"listage des hôtes. ⏎ \n"
-"Ëtre présent sur cette listes n'implique pas l'approbation."
-
-#: i2p2www/pages/site/faq.html:109
-msgid ""
-"Jrandom was the lead developer of I2P and\n"
-"Syndie for several years.\n"
-"We do not know if or when jrandom will return.\n"
-"The *.i2p.net domains were left in a non-functioning state after a power\n"
-"outage at the hosting company."
-msgstr ""
-"Jrandom était le principal développeur de I2P et ⏎\n"
-"Syndie durant plusieurs années. ⏎"
-"\n"
-"Nous ne savons pas si ou quand jrandom reviendra. ⏎\n"
-"Les domaines *.i2p.net ont été laissés en dans un état de non-"
-"fonctionnement après une panne⏎\n"
-"électrique chez l'entreprise d'hébergement."
-
-#: i2p2www/pages/site/faq.html:117
-#, python-format
-msgid ""
-"See this page for jrandom's parting message "
-"and additional information\n"
-"on the migration of *.i2p.net to this website."
-msgstr ""
-"Voir cette page pour le message d'adieu de "
-"jrandom et⏎\n"
-"des informations supplémentaires sur la migration des *.i2p.net vers ce site web."
-
-#: i2p2www/pages/site/faq.html:122
-msgid "I2P remains in active development."
-msgstr "I2P reste en développement actif."
-
-#: i2p2www/pages/site/faq.html:126
-msgid "There are many possible causes of high CPU usage. Here is a checklist:"
-msgstr ""
-"Il ya beaucoup de causes possibles de l'utilisation élevée du processeur."
-" Voici une liste de choses à vérifier :"
-
-#: i2p2www/pages/site/faq.html:131
-msgid ""
-"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
-"system. You can check \n"
-"which version of java you have installed by typing java "
-"-version at a \n"
-"command/shell prompt. Performance tends to suffer with other "
-"implementations of java."
-msgstr ""
-"Essayez d'utiliser OpenJDK ou Sun/Oracle Java si il est disponible pour "
-"votre système. Vous pouvez vérifier⏎\n"
-"quelle version de Java vous avez installé en tapant java-version dans une ⏎ \n"
-"commande / invite du shell. La performance a tendance à souffrir avec "
-"d'autres implémentations de Java."
-
-#: i2p2www/pages/site/faq.html:138
-msgid ""
-"Are you running a BitTorrent client over I2P? Try reducing the number of "
-"torrents, the bandwidth limits,\n"
-"or try turning it off completely to see if that helps."
-msgstr ""
-"Faites vous tourner un client BitTorrent sur ​​I2P ? Essayez de réduire :"
-" le nombre de torrents,⏎\n"
-"les limites de bande passante, ou essayez de l'éteindre complètement pour"
-" voir si cela aide."
-
-#: i2p2www/pages/site/faq.html:144
-msgid ""
-"Are your bandwidth limits set too high? It is possible that too much "
-"traffic is going through your\n"
-"I2P router and it is overloaded. Try reducing the setting for share "
-"bandwidth percentage on the configuration page."
-msgstr ""
-"Est-ce que vos limites de bande passante trop élevées ? Il est possible "
-"que trop de trafic passe par votre ⏎ \n"
-"routeur I2P et qu'il soit surchargé. Essayez de réduire le réglage de "
-"pourcentage de bande passante partagée sur la page configuration."
-
-#: i2p2www/pages/site/faq.html:149
-msgid ""
-"Make sure that you're running the latest version of I2P to get the "
-"benefits of increased performance and bug fixes."
-msgstr ""
-"Assurez-vous que vous utilisez la dernière version de I2P afin d'obtenir "
-"les avantages de l'augmentation de la performance et des corrections de "
-"bugs."
-
-#: i2p2www/pages/site/faq.html:154
-msgid ""
-"Has enough memory been set aside for use by I2P? Look at the memory graph"
-" on the graphs page to see\n"
-"if the memory usage is \"pegged\"—the JVM is spending most of its "
-"time in\n"
-"garbage collection. Increase the setting "
-"wrapper.java.maxmemory in wrapper.config."
-msgstr ""
-"Est-ce que suffisamment de mémoire a été mise de côté pour une "
-"utilisation par I2P ? Regardez le graphique de la mémoire sur la page des"
-" graphiques de performance I2P pour voir ⏎\n"
-"si l'utilisation de la mémoire est \"rattachée\"— la JVM est en "
-"train de passer la plupart de son temps à faire de la⏎\n"
-"garbage collection. Augmentez le réglage "
-"wrapper.java.maxmemory dans wrapper.config ."
-
-#: i2p2www/pages/site/faq.html:161
-#, python-format
-msgid ""
-"Is the CPU usage simply higher than you would like, or is it pegged at "
-"100% for a long time?\n"
-"If it's pegged, this could be a bug. Look in the logs for clues."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:167
-#, python-format
-msgid ""
-"You may be using the Java-based BigInteger library instead of the native "
-"version,\n"
-"especially if you are running on a new or unusual OS or hardware "
-"(OpenSolaris, mipsel, etc.).\n"
-"See the jbigi page for instructions on\n"
-"diagnosing, building, and testing methods."
-msgstr ""
-"Vous utilisez peut-être la bibliothèque BigInteger basée sur Java au lieu"
-" de la version native, ⏎ \n"
-"en particulier si vous êtes sur un nouveau ou inhabituel OS ou matériel "
-"(OpenSolaris, mips, etc.) ⏎ \n"
-"Voir la page jbigi pour obtenir des "
-"instructions sur ⏎ \n"
-"le diagnostic, la construction et les méthodes d'essai."
-
-#: i2p2www/pages/site/faq.html:175
-msgid ""
-"If your native jbigi library is working fine, the biggest user of\n"
-"CPU may be routing traffic for participating tunnels. This uses CPU\n"
-"because at each hop a layer of encryption must be decoded.\n"
-"You can limit participating traffic in two ways - by reducing the\n"
-"share bandwidth on\n"
-"confignet.jsp,\n"
-"or by setting router.maxParticipatingTunnels=nnn on\n"
-"configadvanced.jsp."
-msgstr ""
-"Si votre bibliothèque native jbigi fonctionne bien, le plus grand "
-"utilisateur de \n"
-"CPU peut être l'acheminement du trafic dans les tunnels participants. "
-"Celui-ci utilise du CPU\n"
-"parce que à chaque saut une couche de chiffrement doit être décodée.\n"
-"Vous pouvez limiter la participation trafic de deux façons - en réduisant"
-" le\n"
-"partage de bande passante sur\n"
-"confignet.jsp,\n"
-"ou en paramétrant router.maxParticipatingTunnels=nnn sur\n"
-"configadvanced.jsp."
-
-#: i2p2www/pages/site/faq.html:190
-msgid ""
-"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
-"I2P is designed to withstand censorship, providing a means for everyone "
-"to communicate freely. \n"
-"The best way to keep your PC free of (encrypted) traffic that you dislike"
-" is to not use I2P.\n"
-"Freedom of speech has some costs.\n"
-"But let's address your question in three parts:"
-msgstr ""
-"Hmm, I2P est un réseau anonyme, de sorte que c'est une question délicate."
-" ⏎ \n"
-"I2P est conçu pour résister à la censure, en fournissant un moyen pour "
-"chacun de communiquer librement. ⏎\n"
-"La meilleure façon de garder votre PC à l'écart de trafic (crypté) que "
-"vous n'aimez pas, est de ne pas utiliser I2P. ⏎\n"
-"La liberté d'expression a des coûts. ⏎\n"
-"Mais nous allons répondre à votre question en trois parties :"
-
-#: i2p2www/pages/site/faq.html:199
-#, python-format
-msgid ""
-"Distribution - All traffic on I2P is encrypted in multiple layers."
-" You don't know\n"
-"a message's contents, source, or destination.\n"
-"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
-"Your only alternative is to refuse to route\n"
-"any traffic, by setting your share bandwidth or maximum "
-"participating tunnels to 0 (see above).\n"
-"It would be nice if you didn't do this, you should help the network by "
-"routing traffic for others.\n"
-"Over 95% of users route traffic for others."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:210
-msgid ""
-"Storage - I2P does not do distributed storage of content. You must"
-" be thinking of\n"
-"Freenet.\n"
-"Nobody's content is being stored on your computer by running I2P."
-msgstr ""
-"Stockage - I2P ne fait pas de stockage de contenu distribué. Vous "
-"deviez penser à ⏎\n"
-"Freenet. ⏎\n"
-"En exécutant I2P, le contenu de personne n'est stocké sur votre "
-"ordinateur."
-
-#: i2p2www/pages/site/faq.html:217
-msgid ""
-"Access - If there are some eepsites you don't like, don't go "
-"there.\n"
-"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
-msgstr ""
-"Accès - S'il ya des eepsites vous n'aimez pas, n'y allez pas ⏎ \n"
-"Ou, utilisez un proxy bloquant tel que Privoxy ou certains type de \"Net "
-"Nanny\" (logiciels de contrôle parental)."
-
-#: i2p2www/pages/site/faq.html:227
-msgid ""
-"No. This is normal.\n"
-"All routers adjust dynamically to changing network conditions and demands."
-msgstr ""
-"Non, c'est normal. ⏎\n"
-"Tous les routeurs s'adapter dynamiquement à l'évolution des conditions du"
-" réseau et des demandes."
-
-#: i2p2www/pages/site/faq.html:234
-msgid ""
-"You may need to reseed your I2P router. With recent versions of I2P you "
-"can go to http://localhost:7657/configreseed"
-" and click the Save Changes and Reseed Now button. If this "
-"method doesn't work—or you're using a very old version—you "
-"may need to reseed manually."
-msgstr ""
-"Vous devrez peut-être réamorcer (reseed) votre routeur I2P. Avec les "
-"versions récentes de I2P vous pouvez aller sur http://localhost:7657/configreseed"
-" et cliquer sur le bouton Sauvegarder et réamorcer. Si cette "
-"méthode ne fonctionne pas ou que vous utilisez une très ancienne version,"
-" vous devrez peut-être réamorcer "
-"manuellement."
-
-#: i2p2www/pages/site/faq.html:237
-msgid ""
-"The reseed URL changed a few years ago. If this is your first install and"
-" you have installed\n"
-"an old (0.6.1.30 or earlier) release, or\n"
-"you have not run I2P in a long time, you must change the URL and then\n"
-"click \"Reseed\" on the console to find other routers.\n"
-"After your router is running,\n"
-"on configadvanced.jsp,"
-"\n"
-"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
-"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
-"work),\n"
-"then click \"Apply\", then click the \"reseed\" link on the left."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:248
-#, python-format
-msgid ""
-"This works if you are running 0.6.1.27 or later.\n"
-"If you are running release 0.6.1.31 or later, you probably don't need to "
-"do this.\n"
-"If you are running release 0.6.1.26 or earlier, either follow the\n"
-"manual reseed instructions below\n"
-"or install the latest release.\n"
-"Possible alternate method - add\n"
-"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
-"to wrapper.config, shutdown the router completely, then start again, then"
-" click \"reseed\".\n"
-"Let us know if this works."
-msgstr ""
-"Cela marche si vous utilisez 0.6.1.27 ou plus ancienne.⏎\n"
-"Si vous utilisez la release 0.6.1.31 ou plus ancienne, vous n'aurez "
-"probablement pas besoin de faire cela.⏎\n"
-"Si vous utilisez la release 0.6.1.26 ou plus récente, soit suivez les⏎\n"
-"instructions de réamorçage manuel ci-"
-"dessous⏎\n"
-"ou installez la release la plus "
-"récente.⏎\n"
-"Méthode alternative possible - ajouter⏎\n"
-"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/⏎"
-"\n"
-"à wrapper.config, arrêter le routeur complètement, puis le redémarrer, et"
-" cliquer \"reseed\".⏎\n"
-"Faites nous savoir si cela fonctionne."
-
-#: i2p2www/pages/site/faq.html:259
-#, python-format
-msgid ""
-"...but you *really* should upgrade to "
-"the latest version."
-msgstr ""
-"...mais vous devriez *vraiment* mettre à "
-"niveau vers la version la plus récente."
-
-#: i2p2www/pages/site/faq.html:265
-msgid ""
-"If your router has 10 or more active peers, everything is fine. Changes "
-"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
-"efficiency of the router and effectively reduced the number of active "
-"peers.\n"
-"The router should maintain connections to a few peers at all "
-"times.\n"
-"The best way to stay \"better-connected\" to the network is to share more bandwidth."
-msgstr ""
-"Si vous routeur a 10 pairs actifs ou davantage, tout va bien. Des "
-"changements dans les releases 0.6.1.31 et 0.6.1.32 ont amélioré⏎\n"
-"l'efficacité  de votre router et réduit efficacement le nombre de pairs "
-"actifs.⏎\n"
-"Le router devrait maintenir des connexions vers quelques pairs "
-"tout le temps.⏎\n"
-"La meilleure façon de rester \"mieux connecté\" au réseau est de partager davantage de bande "
-"passante."
-
-#: i2p2www/pages/site/faq.html:272
-msgid ""
-"Is my router an \"exit node\" to the regular Internet? I don't want it to"
-" be."
-msgstr ""
-"Est-ce que mon routeur est un \"nœud de sortie\" (outproxy) vers "
-"l'Internet régulier ? Je ne veux pas qu'il le soit."
-
-#: i2p2www/pages/site/faq.html:274
-msgid ""
-"No. Unlike Tor,\n"
-"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
-"\n"
-"Only volunteers who set up and run separate applications will relay "
-"traffic to the regular Internet.\n"
-"There are very, very few of these."
-msgstr ""
-"Non, contrairement Tor, ⏎ \n"
-"\"nœuds de sortie\" ou \"outproxies\" ne sont pas une partie intégrante "
-"du réseau. ⏎\n"
-"Seuls les volontaires qui ont mis en place et exécutent des applications "
-"distinctes vont relayer le traffic vers l'Internet régulier. ⏎\n"
-"Il y a très, très peu de ces ceux-là."
-
-#: i2p2www/pages/site/faq.html:283
-msgid ""
-"See above. There are very few HTTP \"outproxies\", they are not an "
-"inherent part of the network,\n"
-"and they may not be up.\n"
-"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
-"vanished.\n"
-"The only outproxy at the moment is false.i2p.\n"
-"To use it, edit your i2ptunnel "
-"settings for eepProxy\n"
-"and set your outproxy list to 'false.i2p' (only).\n"
-"Then stop and restart the eepProxy.\n"
-"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
-"If your primary reason to use an anonymous network is to anonymously "
-"access sites\n"
-"on the regular Internet, you should probably try Tor."
-msgstr ""
-"Voir ci-dessus. Il ya très peu de \"outproxies\" HTTP, ils ne sont pas "
-"une partie intégrante du réseau, ⏎ \n"
-"et ils peuvent ne pas être en service. ⏎ \n"
-"En outre, les anciens outproxies squid.i2p, true.i2p et krabs.i2p ont "
-"disparu. ⏎\n"
-"Le seul outproxy en ce moment est false.i2p. ⏎\n"
-"Pour l'utiliser, modifiez vos "
-"paramètres "
-"i2ptunnel pour eepProxy  ⏎ \n"
-"et de définissez votre liste de outproxy à 'false.i2p' (seulement). ⏎\n"
-"Puis arrêtez et redémarrez le eepProxy. ⏎\n"
-"Si cela ne fonctionne pas, le outproxy n'est pas en place. Ce n'est pas "
-"la faute de I2P. ⏎\n"
-"Si votre principale raison d'utiliser un réseau anonyme est d'accéder "
-"anonymement aux sites ⏎\n"
-"de l'Internet régulier, vous devriez probablement essayer Tor."
-
-#: i2p2www/pages/site/faq.html:298
-msgid ""
-"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
-"to-end.\n"
-"FTP is not supported for technical reasons."
-msgstr ""
-"Dans I2P, il n'y a pas besoin de HTTPS, comme tout le trafic est chiffré "
-"de bout en bout. ⏎\n"
-"FTP n'est pas pris en charge pour des raisons techniques."
-
-#: i2p2www/pages/site/faq.html:302
-msgid ""
-"There are no FTP \"outproxies\" to the Internet—it may not even be "
-"possible to set up one.\n"
-"Any other kind of outproxy may work if it's set up with a standard "
-"tunnel. \n"
-"If you would like to set up some type of outproxy, carefully research the"
-" potential risks.\n"
-"The I2P community may or may not be able to help with the technical "
-"aspects, feel free to ask."
-msgstr ""
-"Il n'y a pas de \"outproxies\" FTP vers l'internet, il est même à "
-"craindre qu'il ne soit pas possible d'en mettre un en place. ⏎\n"
-"Tout autre type de outproxy peut fonctionner s'il est mis en place avec "
-"un tunnel standard. ⏎\n"
-"Si vous souhaitez mettre en place un certain type de outproxy, étudiez "
-"soigneusement les risques potentiels. ⏎\n"
-"La communauté I2P peut, ou peut ne pas être, en mesure d'aider concernant"
-" les aspects techniques, n'hésitez pas à demander."
-
-#: i2p2www/pages/site/faq.html:308
-msgid ""
-"As explained several times above, any existing outproxy isn't a core part"
-" of the network.\n"
-"They are services run by individuals and they may or may not\n"
-"be operational at any given time."
-msgstr ""
-"Comme expliqué à plusieurs reprises ci-dessus, tout outproxy existant "
-"n'est pas un élément essentiel du réseau. ⏎\n"
-"Ce sont des services gérés par des individus particuliers et ils peuvent "
-"ou non ⏎ \n"
-"être opérationnels à tout moment donné."
-
-#: i2p2www/pages/site/faq.html:313
-msgid ""
-"Update: Thanks to the work of h2ik, there is an https outproxy "
-"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
-"configured out of the box.
            \n"
-"In case the https outproxy is not available in your version of I2P, you "
-"can add it easily by doing the following:"
-msgstr ""
-"Mise à jour: grâce au travail de H2ik, il ya un outproxy https "
-"disponible pour être utilisé via I2P.\n"
-"Depuis I2P 0.8.4  le tunnel est"
-" configuré d'origine. 
            \n"
-"Dans le cas où le outproxy https n'est pas disponible dans votre version "
-"de I2P, vous pouvez l'ajouter facilement de la manière suivante :"
-
-#: i2p2www/pages/site/faq.html:319
-msgid ""
-"Open i2p tunnel "
-"manager. Scroll down to the bottom."
-msgstr ""
-"Ouvrir Gestionnaire"
-" de tunnels I2P. Défilez jusqu'en bas."
-
-#: i2p2www/pages/site/faq.html:324
-msgid ""
-"Choose CONNECT from New Client Tunnel dropdown list, click "
-"Create"
-msgstr ""
-"Dans Nouveau tunnel client, choisir dans la liste : CONNECT, "
-"cliquer Créer"
-
-#: i2p2www/pages/site/faq.html:329
-#, python-format
-msgid ""
-"In the new page, name and describe your new https tunnel as"
-" you like.\n"
-"The Access Point is your local port for the new https proxy "
-"recommended port's 4445.\n"
-"Outproxy should be the outproxy's .i2p address which supports "
-"https. \n"
-"See this forum post of h2ik's for the "
-"address. \n"
-"Make sure Shared Client, Delay Connect, AutoStart "
-"are checked.\n"
-"Other options should be left at the defaults. Click Save. In tunnel "
-"manger, click the Start button next to your new tunnel."
-msgstr ""
-"Dans la nouvelle page, nommez et décrivez votre nouveau "
-"tunnel https comme vous le souhaitez. ⏎\n"
-"Le point d'accès est votre port local vers le nouveau proxy https "
-"recommandé 4445. ⏎\n"
-"outproxy devrait être l'adresse .i2p de l'outproxy, qui prend en "
-"charge le protocole HTTPS. ⏎\n"
-"Voir ce post sur le forum de h2ik pour "
-"l'adresse. ⏎\n"
-"Assurez-vous que sont cochées : Client partagé, Délai "
-"Connect, Autostart. ⏎\n"
-"Les autres options devraient être laissées aux valeurs par défaut. "
-"Cliquez sur Enregistrer. Dans gestionnaire tunnel, cliquez sur le bouton "
-"Démarrer à côté de votre nouveau tunnel."
-
-#: i2p2www/pages/site/faq.html:339
-msgid ""
-"In firefox, click through "
-"Tools>Options>Advanced>Network>Setting."
-"\n"
-"Untick Use this proxy for all protocol, set SSL proxy: to "
-"localhost:4445."
-msgstr ""
-"Dans Firefox, cliquez sur Outils (ou Options) > Options > "
-"Avancé > Réseau > Paramètres.⏎\n"
-"Décochez Utiliser ce serveur proxy pour tous les protocoles, "
-"mettez Proxy SSL : à localhost:4445."
-
-#: i2p2www/pages/site/faq.html:344
-msgid "Done."
-msgstr "Fait."
-
-#: i2p2www/pages/site/faq.html:350
-#, python-format
-msgid ""
-"\n"
-"This is a question that only you can answer because the correct answer "
-"depends on your behaviours, your\n"
-"threat model, and how much you trust the "
-"outproxy operator."
-msgstr ""
-"\n"
-"C'est une question à laquelle vous seulement pouvez répondre parce que la"
-" réponse correcte  dépend de vos comportements, votre\n"
-"modèle de menace, et combien vous faites "
-"confiance en l'opérateur de l'outproxy."
-
-#: i2p2www/pages/site/faq.html:354
-msgid ""
-"Like Tor, I2P does not magically encrypt the Internet.\n"
-"You are vulnerable to snooping by the outproxy operators.\n"
-"The Tor"
-" FAQ\n"
-"does a good job of explaining this."
-msgstr ""
-"Comme Tor, I2P ne chiffre pas l'Internet de façon magique.\n"
-"Vous êtes vulnérables à l'espionnage par les opérateurs de outproxy.\n"
-"La FAQ"
-" Tor\n"
-"fait un bon travail pour expliquer cela."
-
-#: i2p2www/pages/site/faq.html:360
-#, python-format
-msgid ""
-"In addition, you may be vulnerable to collusion between the outproxy "
-"operator\n"
-"and operators of other I2P services, if you use the same tunnels "
-"(\"shared clients\").\n"
-"There is additional discussion about this on %(zzz)s."
-msgstr ""
-"De plus, vous pouvez être vulnérable à une complicité entre l'opérateur "
-"de l'outproxy\n"
-"et les opérateurs d'autres services I2P, si vous utilisez les mêmes "
-"tunnels (\"clients partagés\").\n"
-"Il y a une discussion complémentaire sur ceci, sur %(zzz)s."
-
-#: i2p2www/pages/site/faq.html:368
-msgid ""
-"Unless an outproxy has been set up for the service you want to connect "
-"to, this cannot be done.\n"
-"There are only three types of outproxies running right now: HTTP, HTTPS, "
-"and email. Note that there is not a SOCKS outproxy.\n"
-"If this type of service is required, try Tor."
-msgstr ""
-"A moins qu'un outproxy aie été mis en place pour le service auquel vous "
-"souhaitez vous connecter, cela ne peut être fait.\n"
-"Il ya seulement trois types de outproxies exécutés maintenant : HTTP, "
-"HTTPS, et le courrier électronique. Notez qu'il n'y a pas de outproxy "
-"SOCKS.\n"
-"Si ce type de service est nécessaire, essayez Tor."
-
-#: i2p2www/pages/site/faq.html:376
-#, python-format
-msgid ""
-"If you consider every eepsite that has ever been created, yes, most of "
-"them are down.\n"
-"People and eepsites come and go.\n"
-"A good way to get started in I2P is check out a list of eepsites that are"
-" currently up.\n"
-"%(perv)s tracks active eepsites."
-msgstr ""
-"Si vous considérez chaque eepsite qui aie jamais été créé, oui, la "
-"plupart d'entre eux sont en hors d'accès (down).\n"
-"Les gens et les eepsites vont et viennent.\n"
-"Une bonne façon de se lancer dans I2P est de vérifier une liste de "
-"eepsites qui sont actuellement en place.\n"
-"%(perv)s trace les eepsites "
-"actifs."
-
-#: i2p2www/pages/site/faq.html:385
-msgid ""
-"Click on the Website link\n"
-"at the top of your router console for instructions."
-msgstr ""
-"Cliquez sur le lien Site web\n"
-"en haut de la console de votre routeur pour obtenir des instructions."
-
-#: i2p2www/pages/site/faq.html:392
-msgid ""
-"Why are downloads, torrents, web browsing, and everything else so slow on"
-" I2P?\n"
-"The encryption and routing within the I2P network adds a substantial "
-"amount of overhead and limits bandwidth.\n"
-"Anonymity isn't free."
-msgstr ""
-"Pourquoi est-ce que les téléchargements, les torrents, la navigation Web,"
-" et tout le reste sont si lent sur ​​I2P ?\n"
-"Le chiffrement et le routage dans le réseau I2P ajoutent une quantité "
-"importante de surplus de données (overhead),  cela limite la bande "
-"passante.\n"
-"L'anonymat n'est pas gratuit."
-
-#: i2p2www/pages/site/faq.html:397
-msgid ""
-"In addition, you and everybody else probably need to increase your "
-"bandwidth limits.\n"
-"Two key settings are the inbound and outbound bandwidth limiters on\n"
-"the configuration page.\n"
-"With the default settings of 32KBps you will generally get no better than"
-" 15KBps data transfer in I2PSnark.\n"
-"Increasing the settings (but keeping within your actual connection "
-"limitations)\n"
-"will increase the potential transfer rate for I2PSnark and all other "
-"applications."
-msgstr ""
-"En outre, vous et tout le monde avez probablement besoin d'augmenter vos "
-"limites de bande passante.\n"
-"Deux paramètres principaux sont les limiteurs de débit entrant et sortant"
-" sur\n"
-"la page de configuration "
-".\n"
-"Avec les réglages par défaut de 32 KBps vous n'obtiendrez généralement "
-"pas mieux que 15 KBps de transfert de données dans I2PSnark.\n"
-"Augmenter les paramètres (mais en restant dans les limites de votre "
-"connexion actuelle)\n"
-"augmentera la vitesse potentielle de transfert pour I2PSnark et toutes "
-"les autres applications."
-
-#: i2p2www/pages/site/faq.html:405
-msgid ""
-"Also, do you have sufficient share bandwidth configured to allow "
-"participating tunnels\n"
-"to route through your router? Believe it or not, allowing participating "
-"traffic\n"
-"keeps you well-integrated in the network and helps your own transfer "
-"speeds."
-msgstr ""
-"Aussi, avez-vous configuré suffisament de bande passante partagée, pour "
-"permettre aux tunnels participants\n"
-"d'être acheminés à travers votre routeur ? Croyez-le ou non, autoriser la"
-" circulation de \"traffic participant\"\n"
-"vous permet de rester bien intégré dans le réseau, et aide vos propres "
-"vitesses de transfert."
-
-#: i2p2www/pages/site/faq.html:410
-#, python-format
-msgid ""
-"I2P is a work in progress. Lots of improvements and fixes are being "
-"implemented, and\n"
-"generally speaking, running the latest release will help your "
-"performance.\n"
-"If you haven't, install the latest "
-"release."
-msgstr ""
-"I2P est un travail en cours. Beaucoup d'améliorations et corrections sont"
-" mises en œuvre, et\n"
-"d'une manière générale, utiliser la dernière version aidera votre "
-"performance.\n"
-"Si vous ne l'avez pas, installez la "
-"dernière version."
-
-#: i2p2www/pages/site/faq.html:418
-#, python-format
-msgid ""
-"See the\n"
-"I2P Bittorrent FAQ"
-msgstr ""
-"Voyez la\n"
-"FAQ Bittorrent I2P"
-
-#: i2p2www/pages/site/faq.html:425
-msgid ""
-"\n"
-"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
-" installed (see\n"
-"the I2PTunnel "
-"configuration page),\n"
-"and is automatically started when the I2P router starts. To connect to "
-"it, tell your IRC\n"
-"client to connect to localhost 6668. XChat-like client users"
-" can create a\n"
-"new network with the server localhost/6668 (remember to tick"
-" "Bypass\n"
-"proxy server" if you have a proxy server configured)."
-msgstr ""
-"\n"
-"Un tunnel vers le serveur IRC principal à l'intérieur de I2P, nommé "
-"Irc2P, est créé lorsque I2P est installé (voir\n"
-"la page de "
-"configuration de I2PTunnel), \n"
-"et il est démarré automatiquement lorsque le routeur I2P se lance. Pour "
-"s'y connecter, dites à votre\n"
-"client IRC de se connecter à localhost 6668. Les "
-"utilisateurs de clients comme-XChat peuvent créer un\n"
-"nouveau réseau avec le serveur localhost/6668 (n'oubliez pas"
-" de cocher la case "Bypass\n"
-"proxy serverr" si vous avez un serveur proxy configuré)."
-
-#: i2p2www/pages/site/faq.html:436
-msgid ""
-"For security purposes, the router's admin console by default only listens"
-"\n"
-"for connections on the local interface.  However, with a little hacking,\n"
-"you can make it reachable remotely:"
-msgstr ""
-"Pour des raisons de sécurité, la console d'admin du routeur n'écoute par "
-"défaut que\n"
-"les connexions sur l'interface locale. Cependant, avec un peu de hacking,"
-"\n"
-"vous pouvez la rendre accessible à distance :"
-
-#: i2p2www/pages/site/faq.html:444
-msgid ""
-"Open ~/.i2p/clients.config and replace
            \n"
-"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
-"with 
            \n"
-"clientApp.0.args=7657 0.0.0.0 ./webapps/"
-msgstr ""
-"Ouvrez ~/.i2p/clients.config et remplacez 
            ⏎\n"
-"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            ⏎\n"
-" avec 
            ⏎\n"
-"clientApp.0.args=7657 0.0.0.0 ./webapps/"
-
-#: i2p2www/pages/site/faq.html:452
-msgid ""
-"Go to http://localhost:7657/configadvanced.jsp"
-"\n"
-"and add a new option: consolePassword=foo (or whatever "
-"password you want)"
-msgstr ""
-"Allez à http://localhost:7657/configadvanced.jsp⏎"
-"\n"
-"et ajoutez une nouvelle option: consolePassword=foo (ou le "
-"mot de passe que vous voulez)"
-
-#: i2p2www/pages/site/faq.html:458
-msgid ""
-"Go to http://localhost:7657/index.jsp"
-"\n"
-"and hit \"Graceful restart\", which restarts the JVM and reloads the "
-"client applications"
-msgstr ""
-"Allez à  "
-"http://localhost:7657/index.jsp \n"
-"et cliquez sur \"Redémarrage en douceur\", qui redémarre la JVM et "
-"recharge les applications clientes"
-
-#: i2p2www/pages/site/faq.html:465
-msgid ""
-"After that fires up, you should now be able to reach your console "
-"remotely.\n"
-"You will be prompted for a username and password though - the username is"
-"\n"
-"\"admin\" and the password is whatever you specified in step 2 above.  "
-"Note: the\n"
-"0.0.0.0 above specifies an interface, not a network "
-"or netmask.  0.0.0.0\n"
-"means \"bind to all interfaces\", so it can be reachable on "
-"127.0.0.1:7657 as well as\n"
-"any LAN/WAN IP."
-msgstr ""
-"Après que cela se soit déclenché, vous devriez maintenant être en mesure "
-"d'atteindre votre console à distance. ⏎\n"
-"Vous serez invité à entrer un nom d'utilisateur et mot de passe si - le "
-"nom d'utilisateur est ⏎\n"
-"«admin» et le mot de passe est celui que vous avez spécifié à l'étape 2 "
-"ci-dessus. Remarque: le ⏎\n"
-"0.0.0.0 ci-dessus spécifie une interface, pas un "
-"réseau ou un masque. 0.0.0.0 ⏎\n"
-"signifie \"lier à toutes les interfaces\", de sorte qu'il peut être "
-"accessible sur 127.0.0.1:7657 ainsi que ⏎\n"
-"tout LAN / WAN IP."
-
-#: i2p2www/pages/site/faq.html:476
-msgid ""
-"By default, the router I2CP interface (port 7654) binds to address "
-"127.0.0.1. To bind to 0.0.0.0, set the\n"
-"router advanced configuration option "
-"i2cp.tcp.bindAllInterfaces=true and restart."
-msgstr ""
-"Par défaut, l'interface I2CP du routeur (port 7654) s'attache à l'adresse"
-" 127.0.0.1. Pour lier à 0.0.0.0, réglez⏎\n"
-"l'option de configuration avancée du routeur "
-"i2cp.tcp.bindAllInterfaces=true puis redémarrez."
-
-#: i2p2www/pages/site/faq.html:481
-msgid "Whats an \"eepsite\"?"
-msgstr "Qu'est ce qu'un \"eepsite\" ?"
-
-#: i2p2www/pages/site/faq.html:483
-msgid ""
-"An eepsite is a website that is hosted anonymously - you can access it by"
-"\n"
-"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
-"listens on localhost port 4444), and browsing to the site."
-msgstr ""
-"Un eepsite est un site qui est hébergé anonyme - vous pouvez y accéder en"
-"\n"
-"paramétrant le proxy HTTP de votre navigateur pour utiliser le proxy web "
-"(typiquement, il\n"
-"écoute sur le port localhost 4444), puis naviguer vers le site."
-
-#: i2p2www/pages/site/faq.html:491
-#, python-format
-msgid ""
-"The proxy config for different browsers is on a \n"
-"separate page with screenshots. More advanced configs with external "
-"tools\n"
-"are possible but could introduce leaks in your setup."
-msgstr ""
-"La configuration proxy pour les différents navigateurs est sur une \n"
-"page séparée avec des copies d'écran. Des paramétrages plus avancées "
-"avec des outils externes\n"
-"sont possibles, mais pourraient présenter des fuites dans votre "
-"configuration."
-
-#: i2p2www/pages/site/faq.html:500
-msgid ""
-"x is the number of peers you've sent or received a message from\n"
-"successfully in the last minute, y is the number of peers seen in the "
-"last\n"
-"hour or so."
-msgstr ""
-"x est le nombre de pairs vers lesquels vous avez envoyé ou reçu un "
-"message⏎\n"
-"avec succès durant la dernière minute, y est le nombre de pairs vu dans "
-"la dernière ⏎\n"
-"heure environ."
-
-#: i2p2www/pages/site/faq.html:508
-msgid ""
-"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
-"supported.\n"
-"There is no SOCKS outproxy so it is of limited use."
-msgstr ""
-"Le proxy SOCKS fonctionne à partir de la release 0.7.1. SOCKS 4/4a/5 sont"
-" pris en charge. \n"
-"Il n'y a pas d'outproxy SOCKS donc il est d'une utilité limitée."
-
-#: i2p2www/pages/site/faq.html:512
-msgid ""
-"In addition, many applications leak sensitive\n"
-"information that could identify you on the Internet. I2P only filters\n"
-"connection data, but if the program you intend to run sends this\n"
-"information as content, I2P has no way to protect your anonymity.  For\n"
-"example, some mail applications will send the IP address of the machine\n"
-"they are running on to a mail server. There is no way for I2P to filter\n"
-"this, thus using I2P to 'socksify' existing applications is possible, but"
-"\n"
-"extremely dangerous."
-msgstr ""
-"En outre, de nombreuses applications font fuire des informations\n"
-"sensibles qui pourraient vous identifier sur l'Internet. I2P filtre "
-"uniquement\n"
-"les données de connexion, mais si le logiciel que vous souhaitez exécuter"
-" envoie cette\n"
-"information en tant que contenu, I2P n'a aucun moyen de protéger votre "
-"anonymat.\n"
-"Par exemple certaines applications de messagerie envoient l'adresse IP de"
-" la machine\n"
-"sur laquelle elles sont en cours d'exécution vers un serveur de "
-"messagerie. Il n'existe\n"
-"aucun moyen pour I2P de filtrer ceci, utiliser I2P pour 'socksifier' des "
-"applications existantes\n"
-"est possible, mais extrêmement dangereux."
-
-#: i2p2www/pages/site/faq.html:522
-#, python-format
-msgid ""
-"If you would like more information on the socks proxy application anyway,"
-"\n"
-"there are some helpful hints on the socks page."
-msgstr ""
-"Si vous souhaitez plus d'informations sur l'application de proxy socks "
-"malgré tout,\n"
-"il ya quelques conseils utiles sur la page socks "
-"."
-
-#: i2p2www/pages/site/faq.html:529
-msgid ""
-"Okay, here's a rundown of the default ports (everything is configurable\n"
-"through various settings, of course):"
-msgstr ""
-"Ok, voici un récapitulatif des ports par défaut (tout est configurable⏎\n"
-"à travers différents réglages, bien sûr) :"
-
-#: i2p2www/pages/site/faq.html:538
-msgid ""
-"Internet-facing ports\n"
-"Note: New installs as of release 0.7.8 do not use port 8887; they select "
-"a random port\n"
-"between 9000 and 31000 when the program is run for the first time.\n"
-"The selected port is shown on the router configuration page."
-msgstr ""
-" ⏎\n"
-"Remarque : les nouvelles installations depuis la release 0.7.8 "
-"n'utilisent pas le port 8887; elles sélectionnent un port aléatoire ⏎\n"
-"entre 9000 et 31000, lorsque le programme est exécuté pour la première "
-"fois. ⏎\n"
-"Le port sélectionné est affiché sur la page de configuration du"
-" routeur."
-
-#: i2p2www/pages/site/faq.html:546
-msgid ""
-"Outbound UDP from the random port noted on the configuration page to "
-"arbitrary remote UDP ports, allowing replies\n"
-"    "
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:551
-msgid ""
-"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
-"    "
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:556
-msgid ""
-"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
-"arbitrary locations\n"
-"    "
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:561
-msgid ""
-"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
-"arbitrary locations
            \n"
-"Inbound TCP may be disabled on the configuration page."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:567
-msgid ""
-"Outbound UDP on port 123, allowing replies
            \n"
-"This is necessary for I2P's internal time sync (via SNTP - \n"
-"querying a random SNTP host in pool.ntp.org or another\n"
-"server you specify)"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:578
-msgid ""
-"Local I2P ports, listening only to local connections by default,\n"
-"except where noted:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:584
-msgid ""
-"1900: UPnP SSDP UDP multicast listener.\n"
-"Cannot be changed. Binds to all interfaces.\n"
-"May be disabled on confignet.jsp."
-msgstr ""
-"1900: UPnP SSDP UDP multicast listener.⏎\n"
-"Ne peut pas être changé. Lié à toutes les interfaces.⏎\n"
-"Il peut être désactivé sur confignet.jsp."
-
-#: i2p2www/pages/site/faq.html:591
-msgid ""
-"2827: BOB bridge, a higher level socket API for clients\n"
-"Disabled by default.\n"
-"May be enabled/disabled on configclients.jsp.\n"
-"May be changed in the bob.config file."
-msgstr ""
-"2827: pont BOB, un plus haut niveau de socket API pour les "
-"clients⏎\n"
-"Désactivé par défaut.⏎\n"
-"Il peut être activé/désactivé sur configclients.jsp.⏎"
-"\n"
-"Il peut être changé dans le fichier bob.config ."
-
-#: i2p2www/pages/site/faq.html:599
-msgid ""
-"4444: HTTP proxy\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-"4444: proxy HTTP⏎\n"
-"Il peut être désactivé ou changé, sur la console routeur dans la page "
-"i2ptunnel.⏎\n"
-"Il peut aussi être configuré pour être lié à une interface spécifique ou "
-"à toutes les interfaces."
-
-#: i2p2www/pages/site/faq.html:606
-msgid ""
-"4445: HTTPS proxy\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-"4445: proxy HTTPS⏎\n"
-"Il peut être désactivé ou changé, sur la console routeur dans la page "
-"i2ptunnel.⏎\n"
-"Il peut aussi être configuré pour être lié à une interface spécifique ou "
-"à toutes les interfaces."
-
-#: i2p2www/pages/site/faq.html:613
-msgid ""
-"6668: IRC proxy\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-"6668: proxy IRC⏎\n"
-"Il peut être désactivé ou changé, sur la console routeur dans la page "
-"i2ptunnel.⏎\n"
-"Il peut aussi être configuré pour être lié à une interface spécifique ou "
-"à toutes les interfaces."
-
-#: i2p2www/pages/site/faq.html:620
-msgid ""
-"7652: UPnP HTTP TCP event listener.\n"
-"Binds to the LAN address.\n"
-"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
-"May be disabled on confignet.jsp."
-msgstr ""
-"7652: UPnP HTTP TCP event listener.⏎\n"
-"Lié aux adresses LAN.⏎\n"
-"Il peut être changé  avec la config avancée i2np.upnp.HTTPPort=nnnn.⏎\n"
-"Il peut être désactivé sur confignet.jsp."
-
-#: i2p2www/pages/site/faq.html:628
-msgid ""
-"7653: UPnP SSDP UDP search response listener.\n"
-"Binds to all interfaces.\n"
-"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
-"May be disabled on confignet.jsp."
-msgstr ""
-"7653: UPnP SSDP UDP search response listener.⏎\n"
-"Lié à toutes les interfaces.⏎\n"
-"Il peut être changé dansavec la config avancée i2np.upnp.SSDPPort=nnnn.⏎\n"
-"Il peut être désactivé sur confignet.jsp"
-
-#: i2p2www/pages/site/faq.html:636
-msgid ""
-"7654: I2P Client Protocol port, used by client apps.\n"
-"May be changed to a different port on\n"
-"configclients.jsp"
-"\n"
-"but this is not recommended.\n"
-"May be to bind to a different interface or all interfaces, or disabled, "
-"on\n"
-"configclients.jsp."
-msgstr ""
-"7654: port protocole client I2P, utilisé par les apps clientes.⏎\n"
-"Il peut être changé vers un port différent sur⏎\n"
-"configclients.jsp⏎\n"
-"mais ce n'est pas recommandé.⏎\n"
-"Il peut être lié à une interface différente ou à toutes les interfaces, "
-"ou désactivé, sur⏎\n"
-"configclients.jsp."
-
-#: i2p2www/pages/site/faq.html:646
-msgid ""
-"7655: UDP for SAM bridge, a higher level socket API for clients\n"
-"Only opened when a SAM V3 client requests a UDP session.\n"
-"May be enabled/disabled on configclients.jsp.\n"
-"May be changed in the clients.config file with the SAM command line "
-"option sam.udp.port=nnnn."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:654
-msgid ""
-"7656: SAM bridge, a higher level socket API for clients\n"
-"Disabled by default for new installs as of release 0.6.5.\n"
-"May be enabled/disabled on configclients.jsp.\n"
-"May be changed in the clients.config file."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:662
-msgid ""
-"7657: Your router console\n"
-"May be disabled in the clients.config file.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces in that file."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:669
-msgid ""
-"7658: Your eepsite\n"
-"May be disabled in the clients.config file.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces in the jetty.xml file."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:676
-msgid ""
-"7659: Outgoing mail to smtp.postman.i2p\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:683
-msgid ""
-"7660: Incoming mail from pop.postman.i2p\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:690
-msgid ""
-"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:697
-msgid ""
-"31000: Local connection to the wrapper control channel port.\n"
-"Outbound to 32000 only, does not listen on this port.\n"
-"Starts at 31000 and will increment until 31999 looking for a free port.\n"
-"To change, see the\n"
-"wrapper documentation.\n"
-"For more information see below."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:707
-msgid ""
-"32000: Local control channel for the service wrapper.\n"
-"To change, see the\n"
-"wrapper documentation.\n"
-"For more information see below."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:719
-msgid ""
-"The local I2P ports and the I2PTunnel ports do not need to be reachable "
-"from \n"
-"remote machines, but *should* be reachable locally.  You can also create"
-" \n"
-"additional ports for I2PTunnel instances via "
-"http://localhost:7657/i2ptunnel/ \n"
-"(and in turn, would need to get your firewall to allow you local access, "
-"but \n"
-"not remote access, unless desired)."
-msgstr ""
-"Les ports locaux I2P et les ports de i2ptunnel n'ont pas besoin d'être "
-"accessibles à partir ⏎\n"
-"des machines distantes, mais *devraient* être accessibles localement. "
-"Vous pouvez également créer ⏎\n"
-"des ports supplémentaires pour les instances de i2ptunnel via "
-"http://localhost:7657/i2ptunnel/ ⏎\n"
-"(et, en retour, pouvoir nécessiter d'obtenir que votre pare-feu permette "
-"l'accès local, mais ⏎ \n"
-"pas l'accès à distance, à moins que vous le souhaitiez)."
-
-#: i2p2www/pages/site/faq.html:727
-msgid ""
-"So, to summarize, nothing needs to be reachable by unsolicited remote "
-"peers, but\n"
-"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
-"outbound facing port, you'll"
-"\n"
-"get better performance.  You will also need to be able to send outbound "
-"UDP packets\n"
-"to arbitrary remote peers (blocking IPs randomly with something like "
-"PeerGuardian\n"
-"only hurts you - don't do it)."
-msgstr ""
-"Alors, pour résumer, ien ne doit être accessible par des pairs distants "
-"non sollicités, mais⏎\n"
-"si vous pouvez configurer votre NAT / pare-feu pour l'entée de données "
-"UDP et TCP outbound facing "
-"port, vous⏎\n"
-"obtiendrez une meilleure performance. Vous aurez aussi besoin d'être en "
-"mesure d'envoyer des paquets UDP sortants\n"
-"à des pairs distants arbitraires (bloquer des IP au hasard avec quelque "
-"chose comme PeerGuardian ⏎ \n"
-"vous blesse seulement vous seul - ne pas le faire)."
-
-#: i2p2www/pages/site/faq.html:735
-msgid "Why is I2P listening on port 32000?"
-msgstr "Pourquoi est-ce que I2P écoute le port 32000 ?"
-
-#: i2p2www/pages/site/faq.html:737
-msgid ""
-"The Tanuki java service wrapper that we use opens this port—bound "
-"to localhost—in order \n"
-"to communicate with software running inside the JVM. When the JVM is "
-"launched it is given a key \n"
-"so it can connect to the wrapper. After the JVM establishes its "
-"connection \n"
-"to the wrapper, the wrapper refuses any additional connections."
-msgstr ""
-"Le wrapper service Java Tanuki que nous utilisons ouvre ce port-lié au "
-"localhost-afin ⏎\n"
-"de communiquer avec le logiciel en cours d'exécution à l'intérieur de la "
-"JVM. Lorsque la JVM est lancé, il est donné une clé ⏎\n"
-"de sorte qu'il puisse se connecter au wrapper. Ensuite la JVM établit sa "
-"connexion ⏎\n"
-"au wrapper, le wrapper refuse toutes connexions supplémentaires."
-
-#: i2p2www/pages/site/faq.html:743
-msgid ""
-"More information can be found in the  \n"
-"wrapper documentation."
-msgstr ""
-"Davantage d'information peut être trouvée dans la\n"
-"documentation wrapper."
-
-#: i2p2www/pages/site/faq.html:750
-msgid ""
-"An I2P router only needs to be seeded once, to join the network for the "
-"first time.\n"
-"Reseeding is nothing more than sending plain HTTP GET requests\n"
-"to fetch a directory listing and download multiple \"routerInfo\" files\n"
-"from a predefined reseed URL."
-msgstr ""
-"Un routeur I2P nécessite seulement d'être amorcé une fois pour se joindre"
-" au réseau pour la première fois. ⏎  Réamorcer n'est rien de plus "
-"qu'envoyer des requêtes HTTP GET ⏎\n"
-"pour récupérer la liste répertoire et télécharger plusieurs fichiers "
-"\"routerInfo\" ⏎\n"
-"à partir d'une URL d'amorçage prédéfinie."
-
-#: i2p2www/pages/site/faq.html:757
-msgid ""
-"A typical symptom of a failed reseed is the \"Known\" indicator\n"
-"(on the left sidebar of the router console) displaying a very small value"
-"\n"
-"(often less than 5) which does not increase. This can occur, among other "
-"things,\n"
-"if your firewall limits outbound traffic, and blocked the reseed request."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:764
-msgid "To reseed an I2P router manually, do the following:"
-msgstr "Pour réamorcer un routeur I2P manuellement, procédez comme suit :"
-
-#: i2p2www/pages/site/faq.html:767
-msgid "Stop your I2P router"
-msgstr "Stoppez votre routeur I2P"
-
-#: i2p2www/pages/site/faq.html:770
-msgid ""
-"Open http://netdb.i2p2.de/ using a "
-"web browser"
-msgstr ""
-"Ouvrez http://netdb.i2p2.de/ en "
-"utilisant un navigateur web"
-
-#: i2p2www/pages/site/faq.html:773
-msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
-msgstr ""
-"Sauvegardez une douzaine de fichiers \"routerInfo\" vers votre répertoire"
-" \"netDb\" dans I2P"
-
-#: i2p2www/pages/site/faq.html:780
-msgid "Start your I2P router"
-msgstr "Lancer votre routeur I2P"
-
-#: i2p2www/pages/site/faq.html:787
-msgid ""
-"When trying to start the router using \"i2prouter start\", you may see "
-"output like the following:"
-msgstr ""
-"Lorsque vous essayez de démarrer le routeur à l'aide \"start i2prouter\","
-" vous pourriez voir la sortie suivante:"
-
-#: i2p2www/pages/site/faq.html:792
-msgid ""
-"\n"
-"In order to be inclusive and try to ensure that I2P will run on as many "
-"systems \n"
-"as possible, up until I2P 0.8.9 we used a java wrapper \n"
-"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
-"are missing the necessary compatibility libraries.\n"
-"These libraries may be installed by performing the following steps:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:800
-msgid ""
-"Switch to the root user with su or log in as "
-"root."
-msgstr ""
-"Basculer vers l'utilisateur root au moyen de su ou se logger"
-" comme root."
-
-#: i2p2www/pages/site/faq.html:806
-#, python-format
-msgid ""
-"If you cannot install these compatibility libraries (or do not want to), "
-"other\n"
-"possibilities would be to compile the wrapper for your\n"
-"system, starting I2P with the runplain.sh script, or you"
-" can\n"
-"replace the wrapper with one from the source tarball."
-msgstr ""
-"Si vous ne pouvez pas installer ces ces libraries de compatibilité (ou ne"
-" le voulez pas), d'autres⏎\n"
-"possibilités seraient de compiler le wrapper pour votre⏎\n"
-"système, en lançant I2P avec le script runplain.sh, ou "
-"vous pouvez⏎\n"
-"remplacer le wrapper avec un issu du tarball source."
-
-#: i2p2www/pages/site/faq.html:812
-msgid ""
-"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
-"compiled on systems running FreeBSD 7.2."
-msgstr ""
-"Pour la release 0.8.9 de I2P, le wrapper was upgraded to v3.5.12 and "
-"compiled on systems running FreeBSD 7.2."
-
-#: i2p2www/pages/site/faq.html:816
-msgid ""
-"In wrapper.log I see an error that states \"Protocol "
-"family unavailable\" when loading the Router Console"
-msgstr ""
-"Dans wrapper.log je vois une erreur qui indique "
-"\"Famille de protocole indisponible\" quand la console "
-"routeur se charge"
-
-#: i2p2www/pages/site/faq.html:818
-msgid ""
-"Often this error will occur with any network enabled java software on "
-"some systems that are configured to use IPv6 by default. There are a few "
-"ways to solve this:"
-msgstr ""
-"Fréquemment, cette erreur se produit avec n'importe quel logiciel Java "
-"activé réseau, sur certains systèmes qui sont configurés pour utiliser "
-"IPv6 par défaut. Il ya quelques façons de résoudre cela :"
-
-#: i2p2www/pages/site/faq.html:823
-msgid ""
-"On Linux based systems, you can echo 0 > "
-"/proc/sys/net/ipv6/bindv6only"
-msgstr ""
-"Sur le systèmes basés Linux, vous pouvez echo 0 > "
-"/proc/sys/net/ipv6/bindv6only"
-
-#: i2p2www/pages/site/faq.html:825
-msgid "Look for the following lines in wrapper.config."
-msgstr "Regarder les lignes suivantes dans wrapper.config."
-
-#: i2p2www/pages/site/faq.html:829
-msgid ""
-"If the lines are there, uncomment them by removing the \"#\"s. If the "
-"lines are not there, add them without the \"#\"s."
-msgstr ""
-"Si les lignes sont là, mettez-les hors commentaire en supprimant les "
-"\"#\". Si les lignes ne sont pas là, ajoutez les, sans les \"#\"."
-
-#: i2p2www/pages/site/faq.html:832
-msgid ""
-"Another option would be to remove the ::1 from "
-"~/.i2p/clients.config"
-msgstr ""
-"Une autre option serait de retirer le(s) ::1 depuis "
-"~/.i2p/clients.config"
-
-#: i2p2www/pages/site/faq.html:836
-msgid ""
-"WARNING: For any changes to wrapper.config "
-"to take effect, you must completely\n"
-"stop the router and the wrapper. Clicking Restart on your\n"
-"router console will NOT reread this file! You must\n"
-"click Shutdown, wait 11 minutes, then start I2P."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:847
-#, python-format
-msgid ""
-"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
-"the forum and we'll post it here (with\n"
-"the answer, hopefully)."
-msgstr ""
-
-#: i2p2www/pages/site/impressum.html:4
-msgid "German laws"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:2
-msgid "I2P Anonymous Network"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:4
-msgid ""
-"Anonymous peer-to-peer distributed communication layer built with open "
-"source tools and designed to run any traditional Internet service such as"
-" email, IRC or web hosting."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:7
-msgid "What does I2P do for you?"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:8
-msgid ""
-"The I2P network provides strong privacy protections for communication "
-"over the Internet. Many activities that would risk your privacy on the "
-"public Internet can be conducted anonymously inside I2P."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:9
-#, python-format
-msgid "Get I2P %(version)s"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:13
-msgid "What is I2P?"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:15
-msgid ""
-"I2P is a full darknet implementation - a network within a network, and is"
-" intended to protect against monitoring by third parties, such as hostile"
-" governments or ISPs.\n"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:18
-msgid ""
-"I2P is used by many people who care about their privacy, as well as those"
-" in high-risk situations. It is designed to protect activists, oppressed "
-"people, journalists and whistle-blowers - as well as the average person."
-"\n"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:21
-msgid ""
-"I2P runs on Java and is therefore available anywhere Java will run, "
-"including desktops, embedded systems (like the Raspberry Pi)  and Android"
-" phones.\n"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:25
-msgid "Read more…"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:30
-msgid "What can you do with I2P?"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:33
-#, python-format
-msgid ""
-"Email Integrated web mail interface, "
-"plugin for serverless email."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:38
-#, python-format
-msgid ""
-"Web browsing Anonymous "
-"websites, gateways to and from the public Internet."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:43
-#, python-format
-msgid ""
-"Blogging and forums "
-"Blogging and Syndie plugins."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:48
-#, python-format
-msgid ""
-"Website hosting Integrated "
-"anonymous web server."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:53
-#, python-format
-msgid ""
-"Real-time chat Instant "
-"messaging and IRC clients."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:58
-#, python-format
-msgid ""
-"File sharing ED2K and Gnutella"
-" clients, integrated BitTorrent client."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:63
-#, python-format
-msgid ""
-"Decentralized file "
-"storage Tahoe-LAFS distributed filesystem plugin."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:68
-#, python-format
-msgid "More supported applications…"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:76
-msgid "News & Updates"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:4
-msgid "Recommended Links & Resources"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:5
-#, python-format
-msgid ""
-"See also the page with\n"
-"links to presentations, videos, and tutorials about"
-" I2P."
-msgstr ""
-
-#: i2p2www/pages/site/links.html:12
-msgid "Friends of I2P"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:24
-msgid "More Projects and Documentation"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:34
-msgid "Press"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:38
-msgid "Boards, newssite, others"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:42
-msgid "Very Old Stuff"
-msgstr ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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
-msgid ""
-"By default, I2P comes with two outproxies configured: "
-"false.i2p\n"
-"(an HTTP-only proxy) and outproxyng.h2ik.i2p (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
-#, python-format
-msgid ""
-"Filtering is active on these outproxies (for example, mibbit and torrent\n"
-"tracker access is blocked). Note that even though the pirate bay is "
-"blocked\n"
-"they host an official eepsite at %(tpb)s. "
-"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:101
-msgid ""
-"Tor is good application to use"
-" as an\n"
-"outproxy to the Internet."
-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:137
-#: i2p2www/pages/site/about/hall-of-fame.html:138
-#: i2p2www/pages/site/about/hall-of-fame.html:139
-#: i2p2www/pages/site/about/hall-of-fame.html:140
-#: i2p2www/pages/site/about/hall-of-fame.html:142
-#: i2p2www/pages/site/about/hall-of-fame.html:143
-#: i2p2www/pages/site/about/hall-of-fame.html:144
-#: i2p2www/pages/site/about/hall-of-fame.html:147
-#: i2p2www/pages/site/about/hall-of-fame.html:148
-#: i2p2www/pages/site/about/hall-of-fame.html:149
-#: i2p2www/pages/site/about/hall-of-fame.html:152
-#: i2p2www/pages/site/about/hall-of-fame.html:153
-#: i2p2www/pages/site/about/hall-of-fame.html:154
-#: i2p2www/pages/site/about/hall-of-fame.html:155
-#: i2p2www/pages/site/about/hall-of-fame.html:156
-#: i2p2www/pages/site/about/hall-of-fame.html:157
-#: i2p2www/pages/site/about/hall-of-fame.html:158
-#: i2p2www/pages/site/about/hall-of-fame.html:159
-#: i2p2www/pages/site/about/hall-of-fame.html:160
-#: i2p2www/pages/site/about/hall-of-fame.html:161
-#: i2p2www/pages/site/about/hall-of-fame.html:162
-#: i2p2www/pages/site/about/hall-of-fame.html:163
-#: i2p2www/pages/site/about/hall-of-fame.html:164
-#: i2p2www/pages/site/about/hall-of-fame.html:167
-#: i2p2www/pages/site/about/hall-of-fame.html:168
-#: i2p2www/pages/site/about/hall-of-fame.html:169
-#: i2p2www/pages/site/about/hall-of-fame.html:170
-#: i2p2www/pages/site/about/hall-of-fame.html:171
-#: i2p2www/pages/site/about/hall-of-fame.html:172
-#: 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: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:181
-#: i2p2www/pages/site/about/hall-of-fame.html:182
-#: 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:186
-#: i2p2www/pages/site/about/hall-of-fame.html:187
-#: 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: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: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:208
-#: i2p2www/pages/site/about/hall-of-fame.html:209
-#: i2p2www/pages/site/about/hall-of-fame.html:210
-#: i2p2www/pages/site/about/hall-of-fame.html:212
-#: i2p2www/pages/site/about/hall-of-fame.html:213
-#: 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:217
-#: i2p2www/pages/site/about/hall-of-fame.html:218
-#: i2p2www/pages/site/about/hall-of-fame.html:219
-#: 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:227
-#: i2p2www/pages/site/about/hall-of-fame.html:230
-#: i2p2www/pages/site/about/hall-of-fame.html:231
-#: 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:236
-#: i2p2www/pages/site/about/hall-of-fame.html:237
-#: i2p2www/pages/site/about/hall-of-fame.html:238
-#: i2p2www/pages/site/about/hall-of-fame.html:243
-#: 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:247
-#: 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:252
-#: 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:265
-#: 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:271
-#: 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:275
-#: i2p2www/pages/site/about/hall-of-fame.html:276
-#: i2p2www/pages/site/about/hall-of-fame.html:277
-#: i2p2www/pages/site/about/hall-of-fame.html:278
-#: 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:289
-#: 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:292
-#: i2p2www/pages/site/about/hall-of-fame.html:293
-#: i2p2www/pages/site/about/hall-of-fame.html:294
-#: i2p2www/pages/site/about/hall-of-fame.html:295
-#: i2p2www/pages/site/about/hall-of-fame.html:297
-#: i2p2www/pages/site/about/hall-of-fame.html:298
-#: i2p2www/pages/site/about/hall-of-fame.html:299
-#: i2p2www/pages/site/about/hall-of-fame.html:300
-#: 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: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:314
-#: 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:322
-#: i2p2www/pages/site/about/hall-of-fame.html:324
-#: 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:332
-#: 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: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:348
-#: i2p2www/pages/site/about/hall-of-fame.html:349
-#: i2p2www/pages/site/about/hall-of-fame.html:351
-#: i2p2www/pages/site/about/hall-of-fame.html:352
-#: 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:374
-#: 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:378
-#: i2p2www/pages/site/about/hall-of-fame.html:379
-#: 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:382
-#: i2p2www/pages/site/about/hall-of-fame.html:383
-#: 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:386
-#: 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:389
-#: i2p2www/pages/site/about/hall-of-fame.html:390
-#: i2p2www/pages/site/about/hall-of-fame.html:391
-#: i2p2www/pages/site/about/hall-of-fame.html:392
-#: i2p2www/pages/site/about/hall-of-fame.html:393
-#: i2p2www/pages/site/about/hall-of-fame.html:394
-#: i2p2www/pages/site/about/hall-of-fame.html:395
-#: i2p2www/pages/site/about/hall-of-fame.html:396
-#: i2p2www/pages/site/about/hall-of-fame.html:397
-#: i2p2www/pages/site/about/hall-of-fame.html:398
-#: i2p2www/pages/site/about/hall-of-fame.html:399
-#: 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: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: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:420
-#: 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:436
-#: 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:442
-#: i2p2www/pages/site/about/hall-of-fame.html:445
-#: 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:449
-#: 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:455
-#: i2p2www/pages/site/about/hall-of-fame.html:456
-#: i2p2www/pages/site/about/hall-of-fame.html:457
-#: i2p2www/pages/site/about/hall-of-fame.html:458
-#: 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:465
-#: i2p2www/pages/site/about/hall-of-fame.html:466
-#: i2p2www/pages/site/about/hall-of-fame.html:467
-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
-#, 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
-#: i2p2www/pages/site/get-involved/bounties/index.html:67
-msgid "Bitcoin client for I2P"
-msgstr ""
-
-#: i2p2www/pages/site/about/hall-of-fame.html:20
-#, python-format
-msgid "%(btcval)s BTC"
-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:134
-msgid "2012 donations and costs:"
-msgstr ""
-
-#: i2p2www/pages/site/about/hall-of-fame.html:262
-msgid "2011 donations and costs:"
-msgstr ""
-
-#: i2p2www/pages/site/about/hall-of-fame.html:363
-msgid "Previous to 2011 donations:"
-msgstr ""
-
-#: i2p2www/pages/site/about/intro.html:2
-msgid "Intro"
-msgstr ""
-
-#: i2p2www/pages/site/about/intro.html:5
-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 \n"
-"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:19
-#, 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:33
-#, 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:44
-#, python-format
-msgid "More details about how I2P works are available."
-msgstr ""
-
-#: i2p2www/pages/site/about/intro.html:48
-msgid "What can you do with it?"
-msgstr ""
-
-#: i2p2www/pages/site/about/intro.html:50
-#, 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:60
-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:76
-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:90
-#, 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
-#: i2p2www/pages/site/research/papers.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\n"
-"Russian translation"
-msgstr ""
-
-#: i2p2www/pages/site/about/media.html:204
-#, python-format
-msgid ""
-"zzz interviewed on the InfoSec Daily Podcast Ep. 454 "
-"(mp3)\n"
-"August 18, 2011"
-msgstr ""
-
-#: i2p2www/pages/site/about/media.html:209
-#, python-format
-msgid ""
-"I2P - Anonymity for the Masses,\n"
-"Jonathan Cox,\n"
-"November 11, 2011."
-msgstr ""
-
-#: i2p2www/pages/site/about/media.html:215
-#, 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: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:76
-#: i2p2www/pages/site/about/team.html:81 i2p2www/pages/site/about/team.html:101
-#: i2p2www/pages/site/about/team.html:138
-#: i2p2www/pages/site/about/team.html:148
-#: i2p2www/pages/site/about/team.html:153
-#: 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:206
-#: i2p2www/pages/site/about/team.html:228
-#: i2p2www/pages/site/get-involved/bounties/index.html:35
-#: i2p2www/pages/site/get-involved/bounties/index.html:42
-#: i2p2www/pages/site/get-involved/bounties/index.html:49
-#: i2p2www/pages/site/get-involved/bounties/index.html:56
-#: i2p2www/pages/site/get-involved/bounties/index.html:63
-#: i2p2www/pages/site/get-involved/bounties/index.html:84
-#: i2p2www/pages/site/get-involved/bounties/index.html:104
-msgid "vacant"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:72
-msgid "threat model / crypto expert"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:75
-msgid "User Advocate"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:77
-msgid "gather, prioritize, advocate for user needs"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:80
-msgid "Web Designer"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:82
-msgid "manage the public project website content design"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:85
-#, python-format
-msgid "Webserver admin"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:87
-msgid "manage the public project webservers"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:90
-#, python-format
-msgid "Website admin"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:92
-msgid "manage the public project website content"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:95
-msgid "News Admin"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:97
-msgid "manage router console news feed"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:100
-msgid "Director of passion"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:102
-msgid "community motivator"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:106
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-msgid "Dev"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:107
-msgid "Core Lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:109
-msgid "lead dev for the SDK and router"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:112
-#, python-format
-msgid "I2P mail lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:114
-msgid "organize and develop the i2p mail system"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:117
-#, python-format
-msgid "I2Host lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:119
-msgid "I2Host addressbook application"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:122
-#, python-format
-msgid "BOB lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:124
-msgid "Basic Open Bridge"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:127
-#, python-format
-msgid "I2P-Bote lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:129
-msgid "I2PBote plugin"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:132
-#, python-format
-msgid "Robert lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:134
-msgid "Robert BitTorrent client"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:137
-#, python-format
-msgid "I2Phex lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:139
-msgid "I2Phex Gnutella client"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:142
-#, python-format
-msgid "I2PSnark lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:144
-msgid "Maintains the integrated Bittorrent client"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:147
-#, python-format
-msgid "iMule lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:149
-msgid "eMule client over I2P"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:152
-#, python-format
-msgid "Syndie lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:154
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3
-msgid "Syndie development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:157
-msgid "Susimail lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:159
-msgid "Susimail development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:162
-msgid "Console"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:164
-msgid "Router console HTML/CSS design"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:167
-msgid "SAM"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:169
-msgid "SAM maintainer"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:172
-msgid "I2PCPP lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:174
-msgid "C++ Router"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:177
-msgid "Console Translations"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:179
-msgid "Chinese"
-msgstr "Chinois"
-
-#: i2p2www/pages/site/about/team.html:183
-msgid "Dutch"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:187
-msgid "French"
-msgstr "Français"
-
-#: i2p2www/pages/site/about/team.html:191
-msgid "German"
-msgstr "Allemand"
-
-#: i2p2www/pages/site/about/team.html:195
-msgid "Russian"
-msgstr "Russe"
-
-#: i2p2www/pages/site/about/team.html:199
-msgid "Spanish"
-msgstr "Espagnol"
-
-#: i2p2www/pages/site/about/team.html:203
-msgid "Arabic"
-msgstr "Arabe"
-
-#: i2p2www/pages/site/about/team.html:207
-msgid "Other languages"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:210
-msgid "Contributors"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:212
-msgid "fire2pe dev, console enhancements"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:216
-msgid "desktopgui, dijjer port"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:220
-msgid "Debian/Ubuntu Packager and PPA maintainer"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:224
-msgid "Routerconsole backend and UI work, website revamp, unit tests work"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:229
-msgid "Help needed on many fronts!"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:233
-msgid "Past contributors"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:235
-msgid "I2PTunnel development, ministreaming library"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:239
-msgid "Project lead, Syndie lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:243
-msgid "Project lead, Syndie lead, I2Phex, support guru"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:247
-msgid "iMule lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:251
-#: i2p2www/pages/site/about/team.html:255
-#: i2p2www/pages/site/about/team.html:259
-msgid "I2Phex work"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:263
-msgid "Python SAM library, attack simulations"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:267
-msgid "i2pmail development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:271
-msgid "Syndie help"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:275
-msgid "i2p mail,susimail and susidns apps"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:279
-msgid "I2Phex (port of Phex to I2P)"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:283
-msgid "addressbook,i2p-bt,syndie client"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:287
-msgid "organize and develop the i2p-bt BitTorrent port"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:291
-msgid "addressbook, i2p-bt, syndie client development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:295
-msgid "encryption and signature routines, I2PIM"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:299
-msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:303
-msgid "installer, systray, bogobot"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:307
-msgid "jbigi development, wiki migration, doc cleanup"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:311
-msgid "java debugging and client development on I2PTunnel and the router console"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:315
-msgid "SAM perl module"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:319
-msgid "i2psnark work"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:323
-msgid "java cleanup"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:327
-msgid "docs. wiki migration"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:331
-msgid "translations into French"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:335
-msgid "C port of jcpuid"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:339
-msgid "C# SAM library, pants, fortuna integration"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:343
-msgid "libSAM"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:347
-#: i2p2www/pages/site/about/team.html:351
-msgid "i2p-bt tracker development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:355
-msgid "Console and website themes"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:358
-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
-#: i2p2www/pages/site/docs/api/bob.html:3
-#: i2p2www/pages/site/docs/api/datagrams.html:3
-#: i2p2www/pages/site/docs/how/garlic-routing.html:3
-#: i2p2www/pages/site/docs/protocol/index.html:3
-#: i2p2www/pages/site/docs/transport/ntcp.html:3
-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
-#, python-format
-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
-#, python-format
-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 shitlist) 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: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 ""
-
-#: i2p2www/pages/site/comparison/freenet.html:2
-msgid "I2P Compared to Freenet"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/freenet.html:8
-msgid ""
-"Freenet is a fully distributed, peer to peer anonymous publishing "
-"network, offering \n"
-"secure ways to store data, as well as some approaches attempting to "
-"address the loads\n"
-"of a flash flood.  While Freenet is designed as a distributed data store,"
-" people have\n"
-"built applications on top of it to do more generic anonymous "
-"communication, such as \n"
-"static websites and message boards."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/freenet.html:16
-#, python-format
-msgid ""
-"Compared to I2P, Freenet offers some substantial benefits - it is a "
-"distributed data\n"
-"store, while I2P is not, allowing people to retrieve the content "
-"published by others \n"
-"even when the publisher is no longer online.  In addition, it should be "
-"able to \n"
-"distribute popular data fairly efficiently.  I2P itself does not and will"
-" not provide \n"
-"this functionality.  On the other hand, there is overlap for users who "
-"simply want to \n"
-"communicate with each other anonymously through websites, message boards,"
-" file sharing\n"
-"programs, etc.  There have also been some attempts to develop a "
-"distributed data \n"
-"store to run on top of I2P,\n"
-"(most recently a port of Tahoe-LAFS)\n"
-"but nothing is yet ready for general use."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/freenet.html:29
-msgid ""
-"However, even ignoring any implementations issues, there are some "
-"concerns \n"
-"about Freenet's algorithms from both a scalability and anonymity "
-"perspective, owing \n"
-"largely to Freenet's heuristic driven routing.  The interactions of "
-"various techniques \n"
-"certainly may successfully deter various attacks, and perhaps some "
-"aspects of the \n"
-"routing algorithms will provide the hoped for scalability.  "
-"Unfortunately, not much\n"
-"analysis of the algorithms involved has resulted in positive results, but"
-" there is still\n"
-"hope.  At the very least, Freenet does provide substantial anonymity "
-"against an attacker\n"
-"who does not have the resources necessary to analyze it further."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:2
-msgid "Comparing I2P to other projects"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:4
-msgid ""
-"There are a great many other applications and projects working on "
-"anonymous \n"
-"communication and I2P has been inspired by much of their efforts.  This "
-"is not \n"
-"a comprehensive list of anonymity resources - both freehaven's \n"
-"Anonymity "
-"Bibliography\n"
-"and GNUnet's related "
-"projects\n"
-"serve that purpose well.  That said, a few systems stand out for further\n"
-"comparison. The following have individual comparison pages:"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:20
-#, python-format
-msgid ""
-"The following are discussed on the other "
-"networks page:"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:32
-#, python-format
-msgid ""
-"The content of this page is subject to update, discussion and dispute, "
-"and we welcome comments and additions.\n"
-"You may contribute an analysis by entering a new ticket on Trac."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:2
-msgid "I2P Compared to Other Anonymous Networks"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:5
-msgid "The following networks are discussed on this page."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:16
-#, python-format
-msgid ""
-"Most of the following sections are fairly old, and may not be accurate.\n"
-"For an overview of available comparisons, see the\n"
-"main network comparisons page.\n"
-"You may contribute an analysis by entering a\n"
-"new ticket on %(trac)s."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:29
-#, python-format
-msgid ""
-"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
-" \n"
-"anonymizing proxies, allowing people to tunnel out through the low "
-"latency \n"
-"mix network.  Morphmix includes some very interesting collusion detection"
-" \n"
-"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
-"IP\n"
-"addresses to accomplish the same.  The two primary differences between \n"
-"these systems and I2P are related to I2P's threat model \n"
-"and their out-proxy design (as opposed to providing both sender and "
-"receiver \n"
-"anonymity).  There is source code available to both systems, but we are "
-"not aware \n"
-"of their use outside of academic environments."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:153
-msgid ""
-"\n"
-"Mixminion and Mixmaster are networks to support anonymous email against a"
-" very\n"
-"powerful adversary.\n"
-"High-latency messaging applications running on top of I2P\n"
-"(for example\n"
-"Syndie or\n"
-"I2PBote)\n"
-"may perhaps prove adequate to meet the threat\n"
-"model of those adversaries, while running in parallel along side the "
-"needs of low latency users, to provide\n"
-"a significantly larger anonymity set.\n"
-"High-latency support within the I2P router itself may or may not be added"
-" in a distant future release.\n"
-"It is too early to say if I2P will meet the needs of users requiring "
-"extreme protection for email."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:167
-msgid ""
-"As with Tor and Onion Routing, \n"
-"both Mixminion and Mixmaster take the directory based approach as well."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:177
-#, python-format
-msgid ""
-"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
-"web requests,\n"
-"and as such it has a few centralized nodes (participants in the cascade) "
-"that blend\n"
-"and mix requests from clients through the sequence of nodes (the cascade)"
-" before \n"
-"proxying out onto the web.  The scope, threat model, and security is "
-"substantially \n"
-"different from I2P, but for those who don't require significant anonymity"
-" but still\n"
-"are not satisfied with an Anonymizer-like service, JAP is worth "
-"reviewing.  One\n"
-"caution to note is that anyone under the jurisdiction of the German "
-"courts may want\n"
-"to take care, as the German Federal Bureau of Criminal Investigation "
-"(FBCI) has \n"
-"successfully mounted an \n"
-"attack \n"
-"on the network.  Even though the method of this attack was later found to"
-" be illegal \n"
-"in the German courts, the fact that the data was successfully collected "
-"is the \n"
-"concern.  Courts change their minds based upon circumstance, and this is "
-"evidence that \n"
-"if a government body or intelligence agency wanted to, they could gather "
-"the data, even \n"
-"if it may be found inadmissible in some courts later)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:199
-#, python-format
-msgid ""
-"Both of these systems work through the same basic \n"
-"antnet routing, providing some degree of\n"
-"anonymity based on the threat model of providing plausible deniability "
-"against a simple \n"
-"non-colluding adversary.  With the antnet routing, they first either do a"
-" random walk or a \n"
-"broadcast search to find some peer with the data or identity desired, and"
-" then use a feedback\n"
-"algorithm to optimize that found path.  This works well for applications "
-"that merely want to know \n"
-"what other people around them have to offer - \"How are y'all doing\" vs."
-" \"Hey Alice, how are you\" - \n"
-"you basically get a local cluster of nodes that can share files with and "
-"maintain some degree of \n"
-"anonymity (though you don't have much control over who is in that group "
-"of peers)."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:211
-msgid ""
-"However, the algorithm does not scale well at all - if the application "
-"wants to speak with a \n"
-"particular peer it ends up doing a broadcast search or random walk "
-"(though if they are lucky enough\n"
-"for that to succeed, the antnet routing should optimize that found "
-"connection).  This means that \n"
-"while these networks can work great at small scales, they are not "
-"suitable for large networks where\n"
-"someone wants to get in touch with another specific peer.  That does not "
-"mean that there is no \n"
-"value in these systems, just that their applicability is limited to "
-"situations where their \n"
-"particular issues can be addressed."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:222
-#, python-format
-msgid ""
-"This was a closed-source network targeted at Iranian users.\n"
-"Tor did a\n"
-"good writeup on what to look for in a circumvention tool.\n"
-"Suffice it to say that being closed source and publicly targeting a "
-"specific country are not good ideas.\n"
-"I2P is, of course, open source. However, that source, and our\n"
-"technical documentation, need much more review."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:231
-msgid "Paid VPN Services"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:232
-#: i2p2www/pages/site/comparison/other-networks.html:238
-#, python-format
-msgid ""
-"You may contribute an analysis by entering a\n"
-"new ticket on %(trac)s."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:237
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
-msgid "Others"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:2
-msgid "I2P Compared to Tor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:8
-#, python-format
-msgid ""
-"Tor and Onion Routing are both anonymizing proxy networks, \n"
-"allowing people to tunnel out through their low latency mix \n"
-"network. The two primary differences between Tor / \n"
-"Onion-Routing and I2P are again related to differences in \n"
-"the threat model and the out-proxy design (though Tor\n"
-"supports hidden services as well).  In addition, Tor\n"
-"takes the directory-based approach - providing a \n"
-"centralized point to manage the overall 'view' of the \n"
-"network, as well as gather and report statistics, as \n"
-"opposed to I2P's distributed network \n"
-"database and peer selection."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:22
-msgid ""
-"The I2P/Tor outproxy functionality does have a few \n"
-"substantial weaknesses against certain attackers - \n"
-"once the communication leaves the mixnet, global passive\n"
-"adversaries can more easily mount traffic analysis.  In \n"
-"addition, the outproxies have access to the cleartext \n"
-"of the data transferred in both directions, and \n"
-"outproxies are prone to abuse, along with all of the \n"
-"other security issues we've come to know and love with \n"
-"normal Internet traffic."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:34
-msgid ""
-"However, many people don't need to worry about those \n"
-"situations, as they are outside their threat model.  It\n"
-"is, also, outside I2P's (formal) functional scope (if people want\n"
-"to build outproxy functionality on top of an anonymous\n"
-"communication layer, they can).  In fact, some I2P users\n"
-"currently take advantage of Tor to outproxy."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:48
-msgid "Comparison of Tor and I2P Terminology"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:49
-msgid ""
-"While Tor and I2P are similar in many ways, much of the terminology is "
-"different."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:54
-msgid "Cell"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:54
-#: i2p2www/pages/site/docs/protocol/i2np.html:91
-msgid "Message"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:55
-msgid "Client"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:55
-msgid "Router or Client"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:56
-msgid "Circuit"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:56
-msgid "Tunnel"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:57
-msgid "Directory"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:57
-msgid "NetDb"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:58
-msgid "Directory Server"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:58
-msgid "Floodfill Router"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:59
-msgid "Entry Guards"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:59
-msgid "Fast Peers"
-msgstr "Pairs rapides"
-
-#: i2p2www/pages/site/comparison/tor.html:60
-msgid "Entry Node"
-msgstr "Noeud d'entrée"
-
-#: i2p2www/pages/site/comparison/tor.html:60
-msgid "Inproxy"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:61
-msgid "Exit Node"
-msgstr "Noeud de sortie"
-
-#: i2p2www/pages/site/comparison/tor.html:61
-msgid "Outproxy"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:62
-msgid "Hidden Service"
-msgstr "Service caché"
-
-#: i2p2www/pages/site/comparison/tor.html:62
-msgid "Eepsite or Destination"
-msgstr "Eepsite ou Destination"
-
-#: i2p2www/pages/site/comparison/tor.html:63
-msgid "Hidden Service Descriptor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:63
-msgid "LeaseSet"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:64
-msgid "Introduction point"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:64
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
-#: i2p2www/pages/site/docs/tunnels/implementation.html:140
-msgid "Inbound Gateway"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:65
-msgid "Node"
-msgstr "Noeud"
-
-#: i2p2www/pages/site/comparison/tor.html:65
-#: i2p2www/pages/site/comparison/tor.html:67
-#: i2p2www/pages/site/comparison/tor.html:70
-#: i2p2www/pages/site/docs/spec/configuration.html:70
-msgid "Router"
-msgstr "Routeur"
-
-#: i2p2www/pages/site/comparison/tor.html:66
-msgid "Onion Proxy"
-msgstr "Proxy Onion"
-
-#: i2p2www/pages/site/comparison/tor.html:66
-msgid "I2PTunnel Client (more or less)"
-msgstr "Client I2PTunnel (plus ou moins)"
-
-#: i2p2www/pages/site/comparison/tor.html:67
-msgid "Relay"
-msgstr "Relai"
-
-#: i2p2www/pages/site/comparison/tor.html:68
-msgid "Rendezvous Point"
-msgstr "Point Rendezvous"
-
-#: i2p2www/pages/site/comparison/tor.html:68
-msgid "somewhat like Inbound Gateway + Outbound Endpoint"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:69
-msgid "Router Descriptor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:69
-msgid "RouterInfo"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:70
-msgid "Server"
-msgstr "Serveur"
-
-#: i2p2www/pages/site/comparison/tor.html:73
-msgid "Benefits of Tor over I2P"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:76
-msgid ""
-"Much bigger user base; much more visibility in the academic and hacker "
-"communities; benefits from\n"
-"formal studies of anonymity, resistance, and performance;\n"
-"has a non-anonymous, visible, university-based leader"
-msgstr ""
-"Plus grand nombre d'utilisateurs; beaucoup plus de visibilité dans les "
-"communautés académiques et hacker; bénéficie\n"
-"d'études formelles d'anonymat, de résistance, et performance;\n"
-"a un chef de file universitaire non-anonyme, visible"
-
-#: i2p2www/pages/site/comparison/tor.html:82
-msgid "Has already solved some scaling issues I2P has yet to address"
-msgstr ""
-"A déjà résolu certains problèmes d'échelle que I2P n'a pas eu encore à "
-"aborder"
-
-#: i2p2www/pages/site/comparison/tor.html:83
-msgid "Has significant funding"
-msgstr "A un financement important"
-
-#: i2p2www/pages/site/comparison/tor.html:84
-msgid "Has more developers, including several that are funded"
-msgstr "A davantage de développeurs, dont plusieurs sont financés"
-
-#: i2p2www/pages/site/comparison/tor.html:86
-msgid ""
-"More resistant to state-level blocking due to TLS transport layer and "
-"bridges\n"
-"(I2P has proposals for \"full restricted routes\" but these are not yet "
-"implemented)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:91
-msgid "Big enough that it has had to adapt to blocking and DOS attempts"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:92
-msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:94
-msgid ""
-"Better documentation, has formal papers and specifications,\n"
-"better website, many more translations"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:99
-msgid "More efficient with memory usage"
-msgstr "Utilisation de la mémoire plus efficace"
-
-#: i2p2www/pages/site/comparison/tor.html:100
-msgid "Tor client nodes have very low bandwidth overhead"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:102
-msgid ""
-"Centralized control reduces the complexity at each\n"
-"node and can efficiently address Sybil attacks"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:108
-msgid ""
-"A core of high capacity nodes provides higher\n"
-"throughput and lower latency"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:113
-msgid "C, not Java (ewww)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:116
-msgid "Benefits of I2P over Tor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:118
-msgid ""
-"Designed and optimized for hidden services, which are much faster than in"
-" Tor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:119
-msgid "Fully distributed and self organizing"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:121
-msgid ""
-"Peers are selected by continuously profiling and ranking performance,\n"
-"rather than trusting claimed capacity"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:127
-msgid ""
-"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
-"rather than hardcoded"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:132
-msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:133
-msgid "Peer-to-peer friendly"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:134
-msgid "Packet switched instead of circuit switched"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:137
-msgid ""
-"implicit transparent load balancing of messages \n"
-"across multiple peers, rather than a single path"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:143
-msgid ""
-"resilience vs. failures by running multiple \n"
-"tunnels in parallel, plus rotating tunnels"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:149
-msgid ""
-"scale each client's connections at O(1) instead \n"
-"of O(N) (Alice has e.g. 2 inbound tunnels that are \n"
-"used by all of the peers Alice is talking with, \n"
-"rather than a circuit for each)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:159
-msgid ""
-"Unidirectional tunnels instead of bidirectional\n"
-"circuits, doubling the number of nodes a peer has to\n"
-"compromise to get the same information."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:166
-msgid ""
-"Protection against detecting client activity, even\n"
-"when an attacker is participating in the tunnel, as\n"
-"tunnels are used for more than simply passing end \n"
-"to end messages (e.g. netDb, tunnel management, \n"
-"tunnel testing)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:175
-msgid ""
-"Tunnels in I2P are short lived, decreasing the number\n"
-"of samples that an attacker can use to mount an \n"
-"active attack with, unlike circuits in Tor, which are\n"
-"typically long lived."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:183
-msgid ""
-"I2P APIs are designed specifically for anonymity and\n"
-"security, while SOCKS is designed for functionality."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:188
-msgid "Essentially all peers participate in routing for others"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:190
-msgid ""
-"The bandwidth overhead of being a full peer is low, \n"
-"while in Tor, while client nodes don't require much\n"
-"bandwidth, they don't fully participate in the mixnet."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:196
-msgid "Integrated automatic update mechanism"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:197
-msgid "Both TCP and UDP transports"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:198
-msgid "Java, not C (ewww)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:201
-msgid "Other potential benefits of I2P but not yet implemented"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:202
-msgid "...and may never be implemented, so don't count on them!"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:205
-msgid ""
-"Defense vs. message count analysis by garlic wrapping \n"
-"multiple messages"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:211
-msgid ""
-"Defense vs. long term intersection by adding delays \n"
-"at various hops (where the delays are not discernible\n"
-"by other hops)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:218
-msgid ""
-"Various mixing strategies at the tunnel level (e.g.\n"
-"create a tunnel that will handle 500 messages / minute,\n"
-"where the endpoint will inject dummy messages if there\n"
-"are insufficient messages, etc)"
-msgstr ""
-
 #: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:25
 msgid "Index to Technical Documentation"
-msgstr ""
+msgstr "Index de la documentation technique"
 
 #: i2p2www/pages/site/docs/index.html:3 i2p2www/pages/site/docs/ports.html:3
 #: i2p2www/pages/site/docs/spec/datagrams.html:3
-#: i2p2www/pages/site/docs/spec/geoip.html:3
-#: i2p2www/pages/site/docs/spec/updates.html:3
-#: i2p2www/pages/site/docs/transport/ssu.html:3
-#: i2p2www/pages/site/get-involved/develop/applications.html:3
 msgid "May 2013"
-msgstr ""
+msgstr "Mai 2013"
 
 #: i2p2www/pages/site/docs/index.html:6
 msgid "How does I2P work"
-msgstr ""
+msgstr "Comment fonctionne I2P"
 
 #: i2p2www/pages/site/docs/index.html:8
 msgid "Following is an index to the technical documentation for I2P."
-msgstr ""
+msgstr "Ce qui suit est un index de la documentation technique pour I2P."
 
 #: i2p2www/pages/site/docs/index.html:12
 msgid ""
@@ -6960,6 +47,11 @@ msgid ""
 "The interface between applications and the router is the I2CP (I2P "
 "Control Protocol) API."
 msgstr ""
+"Cette table des matières est organisée selon le niveau des couches "
+"réseau, de la plus haute à la plus basse. Les plus hautes couches sont "
+"celles des \"clients\" ou \"applications\"; les plus basses sont dans le "
+"routeur lu-même. L'interface entre les applications et le routeur est "
+"l'API I2CP (I2P Control Protocol)."
 
 #: i2p2www/pages/site/docs/index.html:19
 #, python-format
@@ -6967,8 +59,7 @@ msgid ""
 "The I2P Project is committed to maintaining accurate, current "
 "documentation.\n"
 "If you find any inaccuracies in the documents linked below, please\n"
-"enter a ticket identifying the "
-"problem."
+"enter a ticket identifying the problem."
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:27 i2p2www/pages/site/docs/naming.html:7
@@ -6985,35 +76,32 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/updates.html:6
 #: i2p2www/pages/site/docs/tunnels/implementation.html:67
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:6
-#: i2p2www/pages/site/misc/jbigi.html:6
 msgid "Overview"
-msgstr ""
+msgstr "Aperçu"
 
 #: i2p2www/pages/site/docs/index.html:29
 msgid "Technical Introduction"
-msgstr ""
+msgstr "Introduction technique"
 
 #: i2p2www/pages/site/docs/index.html:30
 msgid "A Less-Technical Introduction"
-msgstr ""
+msgstr "Une introduction moins technique"
 
 #: i2p2www/pages/site/docs/index.html:31
 msgid "Threat model and analysis"
-msgstr ""
+msgstr "Modèle de menace et analyses"
 
 #: i2p2www/pages/site/docs/index.html:32
 msgid "Comparisons to other anonymous networks"
-msgstr ""
+msgstr "Comparaison avec d'autres réseaux anonymes"
 
 #: i2p2www/pages/site/docs/index.html:33
 msgid "Protocol stack chart"
-msgstr ""
+msgstr "Diagramme de la pile du protocole"
 
 #: i2p2www/pages/site/docs/index.html:34
-#: i2p2www/pages/site/research/papers.html:2
-#: i2p2www/pages/site/research/papers.html:4
 msgid "Papers on I2P"
-msgstr ""
+msgstr "Papiers sur I2P"
 
 #: i2p2www/pages/site/docs/index.html:35
 #, python-format
@@ -7021,57 +109,61 @@ msgid ""
 "Invisible Internet Project (I2P) Project Overview"
 " August 28, 2003 (pdf)"
 msgstr ""
+"Invisible Internet Project (I2P) Project Overview"
+" 28 août, 2003 (pdf)"
 
 #: i2p2www/pages/site/docs/index.html:38
 msgid "Application-Layer Topics"
-msgstr ""
+msgstr "Sujets couche d'application"
 
 #: i2p2www/pages/site/docs/index.html:41 i2p2www/pages/site/docs/naming.html:2
 msgid "Naming and Addressbook"
-msgstr ""
+msgstr "Nomination et carnet d'adresses"
 
 #: i2p2www/pages/site/docs/index.html:42
 msgid "Plugins Overview"
-msgstr ""
+msgstr "Aperçu des plugins"
 
 #: i2p2www/pages/site/docs/index.html:43
 msgid "Plugin Specification"
-msgstr ""
+msgstr "Specification Plugin"
 
 #: i2p2www/pages/site/docs/index.html:44
 msgid "Router software updates"
-msgstr ""
+msgstr "Mises à jour de logiciel routeur"
 
 #: i2p2www/pages/site/docs/index.html:45
 #: i2p2www/pages/site/docs/applications/bittorrent.html:2
 msgid "Bittorrent over I2P"
-msgstr ""
+msgstr "Bittorrent par-dessus I2P"
 
 #: i2p2www/pages/site/docs/index.html:46
 msgid "I2PControl Plugin API"
-msgstr ""
+msgstr "API plugin I2PControl"
 
 #: i2p2www/pages/site/docs/index.html:47
 msgid "hostsdb.blockfile Format"
-msgstr ""
+msgstr "Format hostsdb.blockfile"
 
 #: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:185
 msgid "Configuration File Format"
-msgstr ""
+msgstr "Format de fichier de configuration"
 
 #: i2p2www/pages/site/docs/index.html:51
 msgid "Application Layer API and Protocols"
-msgstr ""
+msgstr "Couche d'application : API et protocoles"
 
 #: i2p2www/pages/site/docs/index.html:52
 msgid ""
 "High-level, easy-to-use APIs for applications written in any language to "
 "send and receive data."
 msgstr ""
+"Des API de haut niveau, faciles à utiliser pour des applications écrites "
+"dans n'importe quelle langue pour envoyer et recevoir des données."
 
 #: i2p2www/pages/site/docs/index.html:54
 msgid "Application Development Overview and Guide"
-msgstr ""
+msgstr "Vue d'ensemble et guide de développement d'application"
 
 #: i2p2www/pages/site/docs/index.html:72
 msgid "SAM Protocol"
@@ -7091,26 +183,33 @@ msgstr "Protocole  BOB"
 
 #: i2p2www/pages/site/docs/index.html:81
 msgid "End-to-End Transport API and Protocols"
-msgstr ""
+msgstr "API et protocoles de transport de bout en bout "
 
 #: i2p2www/pages/site/docs/index.html:82
 msgid ""
 "The end-to-end protocols used by clients for reliable and unreliable "
 "communication."
 msgstr ""
+"Les protocoles de bout en bout utilisés par les clients pour des "
+"communications fiables et non fiables."
 
 #: i2p2www/pages/site/docs/index.html:84
 #: i2p2www/pages/site/docs/api/streaming.html:2
 msgid "Streaming Library"
-msgstr ""
+msgstr "Bibliothèque streaming"
 
 #: i2p2www/pages/site/docs/index.html:86
 msgid "Streaming Javadoc"
-msgstr ""
+msgstr "Javadoc streaming"
+
+#: i2p2www/pages/site/docs/index.html:88
+#: i2p2www/pages/site/docs/api/datagrams.html:2
+msgid "Datagrams"
+msgstr "Datagrammes"
 
 #: i2p2www/pages/site/docs/index.html:90
 msgid "Datagram Javadoc"
-msgstr ""
+msgstr "Javadoc datagramme"
 
 #: i2p2www/pages/site/docs/index.html:93
 msgid "Client-to-Router Interface API and Protocol"
@@ -7210,6 +309,12 @@ msgstr ""
 msgid "I2NP Javadoc"
 msgstr ""
 
+#: i2p2www/pages/site/docs/index.html:139
+#: i2p2www/pages/site/docs/how/tech-intro.html:14
+#: i2p2www/pages/site/docs/how/tech-intro.html:228
+msgid "Tunnels"
+msgstr "Tunnels"
+
 #: i2p2www/pages/site/docs/index.html:140
 msgid ""
 "Selecting peers, requesting tunnels through those peers, and encrypting "
@@ -7264,12 +369,16 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:155
 msgid "Transport Layer"
-msgstr ""
+msgstr "Couche transport"
 
 #: i2p2www/pages/site/docs/index.html:156
 msgid "The protocols for direct (point-to-point) router to router communication."
 msgstr ""
 
+#: i2p2www/pages/site/docs/index.html:158
+msgid "Transport layer overview"
+msgstr "Aperçu couche transport"
+
 #: i2p2www/pages/site/docs/index.html:160
 msgid "TCP-based transport overview and specification"
 msgstr ""
@@ -7314,22 +423,23 @@ msgstr ""
 msgid "Time synchronization and NTP"
 msgstr ""
 
+#: i2p2www/pages/site/docs/index.html:183
+msgid "Performance"
+msgstr "Performance"
+
 #: i2p2www/pages/site/docs/index.html:190
 msgid "Developer's Guides and Resources"
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:192
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
 msgid "New Developer's Guide"
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:194
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
 msgid "New Translator's Guide"
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:196
-#: i2p2www/pages/site/get-involved/guides/monotone.html:4
 msgid "Monotone Guide"
 msgstr ""
 
@@ -7362,7 +472,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:213
 msgid "Ports used by I2P"
-msgstr ""
+msgstr "Ports utilisés par I2P"
 
 #: i2p2www/pages/site/docs/index.html:215
 msgid "Automatic updates to development builds inside I2P"
@@ -7374,11 +484,15 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:219
 msgid "User forum"
-msgstr ""
+msgstr "Forum utilisateur"
 
 #: i2p2www/pages/site/docs/index.html:221
 msgid "Developer forum inside I2P"
-msgstr ""
+msgstr "Forum développeur à l'intérieur de I2P"
+
+#: i2p2www/pages/site/docs/index.html:223
+msgid "Bug tracker"
+msgstr "Traqueur de bugs"
 
 #: i2p2www/pages/site/docs/index.html:225
 msgid "Viewmtn inside I2P"
@@ -7394,7 +508,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:231
 msgid "Source translation at Transifex"
-msgstr ""
+msgstr "Traduction source chez Transifex"
 
 #: i2p2www/pages/site/docs/index.html:233
 msgid "Roadmap wiki"
@@ -7410,13 +524,20 @@ msgid "not current"
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:237
-#: i2p2www/pages/site/get-involved/todo.html:2
 msgid "To Do List"
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:3
+#: i2p2www/pages/site/docs/api/streaming.html:3
 #: i2p2www/pages/site/docs/how/cryptography.html:3
-msgid "March 2012"
+#: i2p2www/pages/site/docs/protocol/i2cp.html:3
+#: i2p2www/pages/site/docs/spec/common-structures.html:3
+#: i2p2www/pages/site/docs/spec/geoip.html:3
+#: i2p2www/pages/site/docs/spec/streaming.html:3
+#: i2p2www/pages/site/docs/transport/index.html:3
+#: i2p2www/pages/site/docs/transport/ntcp.html:3
+#: i2p2www/pages/site/docs/transport/ssu.html:3
+msgid "December 2013"
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:6
@@ -7486,9 +607,8 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:52
 msgid ""
-"The client application which does local lookups "
-"in hosts.txt\n"
-"and also takes care of the Base32 hostnames."
+"The local naming service which does lookups\n"
+"and also handles Base32 hostnames."
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:56
@@ -7525,7 +645,7 @@ msgid ""
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:77
-msgid "Naming Files and Lookups"
+msgid "Naming Services"
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:79
@@ -7546,37 +666,113 @@ msgstr ""
 msgid ""
 "If an application (i2ptunnel or the HTTP proxy) wishes to access\n"
 "a destination by name, the router does a very simple local lookup\n"
-"to resolve that name.\n"
-"The client application (technically, the client side of I2CP in the I2P "
-"API)\n"
-"does a linear search through three local files, in order, to\n"
-"look up host names and convert them to a 516-byte destination key:"
+"to resolve that name."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:94
+msgid "Hosts.txt Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:96
+msgid ""
+"The hosts.txt Naming Service does a simple linear search through\n"
+"text files. This naming service was the default until\n"
+"release 0.8.8 when it was replaced by the Blockfile Naming Service.\n"
+"The hosts.txt format had become too slow after the file grew to thousands"
+" of entries."
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:103
+#, python-format
+msgid ""
+"It does a linear search through three local files, in order, to\n"
+"look up host names and convert them to a 516-byte destination key.\n"
+"Each file is in a simple configuration file"
+" format, with hostname=base64, one per line.\n"
+"The files are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:115
+msgid "Blockfile Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:117
+msgid ""
+"The Blockfile Naming Service stores multiple \"addressbooks\" in a single"
+"\n"
+"database file named hostsdb.blockfile.\n"
+"This Naming Service is the default since release 0.8.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:123
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is specified on the Blockfile page.\n"
+"It provides fast Destination lookup in a compact format. While the "
+"blockfile overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry to implement "
+"advanced addressbook features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:135
+msgid ""
+"On creation, the naming service imports entries from the three files used"
+" by the hosts.txt Naming Service.\n"
+"The blockfile mimics the previous implementation by maintaining three "
+"maps that\n"
+"are searched in-order, named privatehosts.txt, userhosts.txt, and "
+"hosts.txt.\n"
+"It also maintains a reverse-lookup map to implement rapid reverse lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:142
+msgid "Other Naming Service Facilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:144
+#, python-format
 msgid ""
 "The lookup is case-insensitive.\n"
 "The first match is used, and conflicts are not detected.\n"
-"There is no enforcement of naming rules in lookups."
+"There is no enforcement of naming rules in lookups.\n"
+"Lookups are cached for a few minutes.\n"
+"Base 32 resolution is described below.\n"
+"For a full description of the Naming Service API see the\n"
+"Naming Service Javadocs.\n"
+"This API was significantly expanded in release 0.8.7 to provide\n"
+"adds and removes, storage of arbitrary properties with the hostname,\n"
+"and other features."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:109
+#: i2p2www/pages/site/docs/naming.html:157
+msgid "Alternatives and Experimental Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:159
 #, python-format
 msgid ""
-"Lookups are cached for a few minutes.\n"
-"There is an experimental facility for real-time lookups (a la DNS) over "
-"the network within the router,\n"
-"although it is not enabled by default\n"
-"(see \"EepGet\" under Alternatives on the discussion"
-" page)."
+"The naming service is specified with the configuration property "
+"i2p.naming.impl=class.\n"
+"Other implementations are possible. For example,\n"
+"there is an experimental facility for real-time lookups (a la DNS) over "
+"the network within the router.\n"
+"For more information see the alternatives on the discussion"
+" page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:116
-msgid "HTTP Proxy"
-msgstr ""
-
-#: i2p2www/pages/site/docs/naming.html:118
+#: i2p2www/pages/site/docs/naming.html:166
 msgid ""
 "The HTTP proxy does a lookup via the router for all hostnames ending in "
 "'.i2p'.\n"
@@ -7585,23 +781,31 @@ msgid ""
 "Top Level Domain '.i2p'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:124
+#: i2p2www/pages/site/docs/naming.html:172
+#, python-format
+msgid ""
+"We have applied to reserve the .i2p TLD\n"
+"following the procedures specified in RFC "
+"6761."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:178
 msgid ""
 "If the router fails to resolve the hostname, the HTTP proxy returns\n"
 "an error page to the user with links to several \"jump\" services.\n"
 "See below for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:130
+#: i2p2www/pages/site/docs/naming.html:184
 #: i2p2www/pages/site/docs/spec/configuration.html:77
 msgid "Addressbook"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:131
+#: i2p2www/pages/site/docs/naming.html:185
 msgid "Incoming Subscriptions and Merging"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:133
+#: i2p2www/pages/site/docs/naming.html:187
 msgid ""
 "The addressbook application periodically\n"
 "retrieves other users' hosts.txt files and merges\n"
@@ -7610,7 +814,7 @@ msgid ""
 "basis."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:141
+#: i2p2www/pages/site/docs/naming.html:195
 msgid ""
 "Subscribing to another user's hosts.txt file involves\n"
 "giving them a certain amount of trust.\n"
@@ -7619,7 +823,7 @@ msgid ""
 "passing the new host/key entry to you."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:149
+#: i2p2www/pages/site/docs/naming.html:203
 msgid ""
 "For this reason, the only subscription configured by\n"
 "default is http://www.i2p2.i2p/hosts.txt,\n"
@@ -7630,23 +834,23 @@ msgid ""
 "href=\"#susidns\">SusiDNS)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:158
+#: i2p2www/pages/site/docs/naming.html:212
 msgid "Some other public addressbook subscription links:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:165
+#: i2p2www/pages/site/docs/naming.html:219
 msgid ""
 "The operators of these services may have various policies for listing "
 "hosts.\n"
 "Presence on this list does not imply endorsement."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:170
-#: i2p2www/pages/site/docs/naming.html:182
+#: i2p2www/pages/site/docs/naming.html:224
+#: i2p2www/pages/site/docs/naming.html:236
 msgid "Naming Rules"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:171
+#: i2p2www/pages/site/docs/naming.html:225
 msgid ""
 "While there are hopefully not any technical limitations within I2P on "
 "host names,\n"
@@ -7660,83 +864,85 @@ msgid ""
 "to other routers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:186
+#: i2p2www/pages/site/docs/naming.html:240
 msgid "Names are converted to lower case on import."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:190
+#: i2p2www/pages/site/docs/naming.html:244
 msgid ""
 "Names are checked for conflict with existing names in the existing "
 "userhosts.txt and hosts.txt\n"
 "(but not privatehosts.txt) after conversion to lower case."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:195
+#: i2p2www/pages/site/docs/naming.html:249
 msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:199
+#: i2p2www/pages/site/docs/naming.html:253
 msgid "Must not start with '.' or '-'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:203
+#: i2p2www/pages/site/docs/naming.html:257
 msgid "Must end with '.i2p'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:207
+#: i2p2www/pages/site/docs/naming.html:261
 msgid "67 characters maximum, including the '.i2p'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:211
+#: i2p2www/pages/site/docs/naming.html:265
 msgid "Must not contain '..'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:215
+#: i2p2www/pages/site/docs/naming.html:269
 msgid "Must not contain '.-' or '-.' (as of 0.6.1.33)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:219
+#: i2p2www/pages/site/docs/naming.html:273
 msgid "Must not contain '--' except in 'xn--' for IDN."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:223
-msgid "Base32 hostnames (*.b32.i2p) are not allowed."
+#: i2p2www/pages/site/docs/naming.html:277
+msgid ""
+"Base32 hostnames (*.b32.i2p) are reserved for base 32 use and so are not "
+"allowed to be imported."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:227
+#: i2p2www/pages/site/docs/naming.html:281
 msgid ""
 "Certain hostnames reserved for project use are not allowed\n"
 "(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
 "*.console.i2p, and others)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:232
+#: i2p2www/pages/site/docs/naming.html:286
 msgid "Keys are checked for base64 validity."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:236
+#: i2p2www/pages/site/docs/naming.html:290
 msgid ""
 "Keys are checked for conflict with existing keys in hosts.txt (but not "
 "privatehosts.txt)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:240
+#: i2p2www/pages/site/docs/naming.html:294
 msgid "Minimum key length 516 bytes."
 msgstr "Longueur minimum de clé : 516 octets."
 
-#: i2p2www/pages/site/docs/naming.html:244
+#: i2p2www/pages/site/docs/naming.html:298
 msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)."
 msgstr ""
 "Longueur maximum de clé : 616 octets (pour tenir compte des certs jusqu'à"
 " 100 octets)."
 
-#: i2p2www/pages/site/docs/naming.html:249
+#: i2p2www/pages/site/docs/naming.html:303
 msgid ""
-"Any name received via subscription that passes all the checks is added to"
-" the local hosts.txt."
+"Any name received via subscription that passes all the checks is added "
+"via the local naming service."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:253
+#: i2p2www/pages/site/docs/naming.html:307
 msgid ""
 "Note that the '.' symbols in a host name are of no significance,\n"
 "and do not denote any actual naming or trust hierarchy.\n"
@@ -7748,7 +954,7 @@ msgid ""
 "are topics for future discussion."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:264
+#: i2p2www/pages/site/docs/naming.html:318
 msgid ""
 "International Domain Names (IDN) also work in i2p (using punycode 'xn--' "
 "form).\n"
@@ -7757,7 +963,7 @@ msgid ""
 "add 'network.IDN.whitelist.i2p (boolean) = true' in about:config."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:270
+#: i2p2www/pages/site/docs/naming.html:324
 msgid ""
 "As the addressbook application does not use privatehosts.txt at all, in "
 "practice\n"
@@ -7766,11 +972,11 @@ msgid ""
 "\"pet names\" for sites already in hosts.txt."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:276
+#: i2p2www/pages/site/docs/naming.html:330
 msgid "Outgoing Subscriptions"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:277
+#: i2p2www/pages/site/docs/naming.html:331
 msgid ""
 "Addressbook will publish the merged hosts.txt to a location\n"
 "(traditionally hosts.txt in the local eepsite's home directory) to be "
@@ -7779,7 +985,7 @@ msgid ""
 "This step is optional and is disabled by default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:285
+#: i2p2www/pages/site/docs/naming.html:339
 msgid ""
 "The addressbook application, together with eepget, saves the Etag and/or "
 "Last-Modified\n"
@@ -7788,13 +994,13 @@ msgid ""
 "return a '304 Not Modified' on the next fetch if nothing has changed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:292
+#: i2p2www/pages/site/docs/naming.html:346
 msgid ""
 "However the entire hosts.txt is downloaded if it has changed.\n"
 "See below for discussion on this issue."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:297
+#: i2p2www/pages/site/docs/naming.html:351
 msgid ""
 "Hosts serving a static hosts.txt or an equivalent CGI application\n"
 "are strongly encouraged to deliver\n"
@@ -7805,11 +1011,11 @@ msgid ""
 "reduce chances of corruption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:306
+#: i2p2www/pages/site/docs/naming.html:360
 msgid "Host Add Services"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:307
+#: i2p2www/pages/site/docs/naming.html:361
 msgid ""
 "A host add service is a simple CGI application that takes a hostname and "
 "a Base64 key as parameters\n"
@@ -7818,7 +1024,7 @@ msgid ""
 "will be propagated through the network."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:314
+#: i2p2www/pages/site/docs/naming.html:368
 msgid ""
 "It is recommended that host add services impose, at a minimum, the "
 "restrictions imposed by the addressbook application listed above.\n"
@@ -7826,55 +1032,55 @@ msgid ""
 "keys, for example:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:319
+#: i2p2www/pages/site/docs/naming.html:373
 msgid "A limit on number of 'subdomains'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:323
+#: i2p2www/pages/site/docs/naming.html:377
 msgid "Authorization for 'subdomains' through various methods."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:327
+#: i2p2www/pages/site/docs/naming.html:381
 msgid "Hashcash or signed certificates."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:331
+#: i2p2www/pages/site/docs/naming.html:385
 msgid "Editorial review of host names and/or content."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:335
+#: i2p2www/pages/site/docs/naming.html:389
 msgid "Categorization of hosts by content."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:339
+#: i2p2www/pages/site/docs/naming.html:393
 msgid "Reservation or rejection of certain host names."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:343
+#: i2p2www/pages/site/docs/naming.html:397
 msgid "Restrictions on the number of names registered in a given time period."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:347
+#: i2p2www/pages/site/docs/naming.html:401
 msgid "Delays between registration and publication."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:351
+#: i2p2www/pages/site/docs/naming.html:405
 msgid "Requirement that the host be up for verification."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:355
+#: i2p2www/pages/site/docs/naming.html:409
 msgid "Expiration and/or revocation."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:359
+#: i2p2www/pages/site/docs/naming.html:413
 msgid "IDN spoof rejection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:364
+#: i2p2www/pages/site/docs/naming.html:418
 msgid "Jump Services"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:365
+#: i2p2www/pages/site/docs/naming.html:419
 msgid ""
 "A jump service is a simple CGI application that takes a hostname as a "
 "parameter\n"
@@ -7887,20 +1093,20 @@ msgid ""
 "address helper is not necessary until restart."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:375
+#: i2p2www/pages/site/docs/naming.html:429
 msgid ""
 "Note that, like with subscriptions, using a jump service\n"
 "implies a certain amount of trust, as a jump service could maliciously\n"
 "redirect a user to an incorrect destination."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:381
+#: i2p2www/pages/site/docs/naming.html:435
 msgid ""
 "To provide the best service, a jump service should be subscribed to\n"
 "several hosts.txt providers so that its local host list is current."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:387
+#: i2p2www/pages/site/docs/naming.html:441
 msgid ""
 "SusiDNS is simply a web interface front-end to configuring addressbook "
 "subscriptions\n"
@@ -7908,7 +1114,7 @@ msgid ""
 "All the real work is done by the 'addressbook' application."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:393
+#: i2p2www/pages/site/docs/naming.html:447
 msgid ""
 "Currently, there is little enforcement of addressbook naming rules within"
 " SusiDNS,\n"
@@ -7916,11 +1122,11 @@ msgid ""
 "the addressbook subscription rules."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:399
+#: i2p2www/pages/site/docs/naming.html:453
 msgid "Base32 Names"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:400
+#: i2p2www/pages/site/docs/naming.html:454
 msgid ""
 "I2P supports Base32 hostnames similar to Tor's .onion addresses.\n"
 "Base32 addresses are much shorter and easier to handle than the\n"
@@ -7929,12 +1135,18 @@ msgid ""
 "ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p"
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:407
+#: i2p2www/pages/site/docs/naming.html:461
+#, python-format
 msgid ""
 "In Tor, the address is 16 characters (80 bits), or half of the SHA-1 "
 "hash.\n"
 "I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n"
 "The form is {52 chars}.b32.i2p.\n"
+"Tor has recently published a\n"
+"proposal\n"
+"to convert to an identical format of {52 chars}.onion for their hidden "
+"services.\n"
 "Base32 is implemented in the naming service, which queries the\n"
 "router over I2CP to lookup the LeaseSet to get the full Destination.\n"
 "Base32 lookups will only be successful when the Destination is up and "
@@ -7945,7 +1157,7 @@ msgid ""
 "longer than a local address book lookup."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:419
+#: i2p2www/pages/site/docs/naming.html:476
 msgid ""
 "Base32 addresses can be used in most places where hostnames or full "
 "destinations\n"
@@ -7954,6 +1166,11 @@ msgid ""
 "the name does not resolve to a destination."
 msgstr ""
 
+#: i2p2www/pages/site/docs/plugins.html:2
+#: i2p2www/pages/site/docs/spec/configuration.html:65
+msgid "Plugins"
+msgstr "Plugins"
+
 #: i2p2www/pages/site/docs/plugins.html:3
 msgid "June 2012"
 msgstr ""
@@ -8065,7 +1282,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/plugins.html:93
 msgid "Non-java applications also supported"
-msgstr ""
+msgstr "Applications non Java également prises en charge"
 
 #: i2p2www/pages/site/docs/plugins.html:99
 msgid "Required I2P version"
@@ -8213,7 +1430,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/ports.html:2
 msgid "Ports Used by I2P"
-msgstr ""
+msgstr "Ports utilisés par I2P"
 
 #: i2p2www/pages/site/docs/ports.html:7
 msgid ""
@@ -8222,6 +1439,10 @@ msgid ""
 "common alternates,\n"
 "and some typical related applications."
 msgstr ""
+"Ce sont les ports utilisés ou réservés par I2P, y compris ceux pour les "
+"plugins connus, \n"
+"alternatifs communs,\n"
+"et certaines applications liées typiques."
 
 #: i2p2www/pages/site/docs/ports.html:13
 #, python-format
@@ -8233,11 +1454,25 @@ msgid ""
 "For new plugins, we recommend using the next available port\n"
 "in the 766x range."
 msgstr ""
+"Notez que la plupart d'entre eux ne sont pas activés par défaut.\n"
+"Il ya plus d'informations dans la FAQ .\n"
+"Voir aussi la documentation indivuelle des plugins.\n"
+"Auteurs de plugins veuillez ajouter dedans les ports que vous utilisez.\n"
+"Pour les nouveaux plugins, nous vous recommandons d'utiliser le port "
+"disponible suivant\n"
+"parmi la plage 766x."
 
 #: i2p2www/pages/site/docs/ports.html:53
 msgid "recommended spot for new plugins/applications"
 msgstr ""
 
+#: i2p2www/pages/site/docs/api/bob.html:3
+#: i2p2www/pages/site/docs/api/datagrams.html:3
+#: i2p2www/pages/site/docs/how/garlic-routing.html:3
+#: i2p2www/pages/site/docs/protocol/index.html:3
+msgid "August 2010"
+msgstr ""
+
 #: i2p2www/pages/site/docs/api/bob.html:5
 msgid "BOB - Basic Open Bridge"
 msgstr ""
@@ -8683,7 +1918,7 @@ msgid ""
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/datagrams.html:93
-#: i2p2www/pages/site/docs/api/streaming.html:325
+#: i2p2www/pages/site/docs/api/streaming.html:381
 msgid "Data Integrity"
 msgstr ""
 
@@ -8696,7 +1931,7 @@ msgid ""
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/datagrams.html:100
-#: i2p2www/pages/site/docs/api/streaming.html:333
+#: i2p2www/pages/site/docs/api/streaming.html:389
 msgid "Packet Encapsulation"
 msgstr ""
 
@@ -8716,7 +1951,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/api/datagrams.html:114
 #: i2p2www/pages/site/docs/spec/datagrams.html:10
-#: i2p2www/pages/site/docs/transport/ssu.html:567
+#: i2p2www/pages/site/docs/transport/ssu.html:571
 msgid "Specification"
 msgstr ""
 
@@ -8789,8 +2024,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:29
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:33
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:34
-#: i2p2www/pages/site/docs/protocol/i2cp.html:99
-#: i2p2www/pages/site/docs/protocol/i2cp.html:442
+#: i2p2www/pages/site/docs/protocol/i2cp.html:107
+#: i2p2www/pages/site/docs/protocol/i2cp.html:450
 #: i2p2www/pages/site/docs/spec/common-structures.html:16
 #: i2p2www/pages/site/docs/spec/common-structures.html:26
 #: i2p2www/pages/site/docs/spec/common-structures.html:37
@@ -8806,12 +2041,12 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/common-structures.html:162
 #: i2p2www/pages/site/docs/spec/common-structures.html:174
 #: i2p2www/pages/site/docs/spec/common-structures.html:227
-#: i2p2www/pages/site/docs/spec/common-structures.html:294
-#: i2p2www/pages/site/docs/spec/common-structures.html:343
-#: i2p2www/pages/site/docs/spec/common-structures.html:387
-#: i2p2www/pages/site/docs/spec/common-structures.html:432
-#: i2p2www/pages/site/docs/spec/common-structures.html:569
-#: i2p2www/pages/site/docs/spec/common-structures.html:625
+#: i2p2www/pages/site/docs/spec/common-structures.html:310
+#: i2p2www/pages/site/docs/spec/common-structures.html:359
+#: i2p2www/pages/site/docs/spec/common-structures.html:411
+#: i2p2www/pages/site/docs/spec/common-structures.html:456
+#: i2p2www/pages/site/docs/spec/common-structures.html:593
+#: i2p2www/pages/site/docs/spec/common-structures.html:655
 msgid "Description"
 msgstr ""
 
@@ -9207,36 +2442,40 @@ msgid "Method not found."
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:194
+msgid "Invalid parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:195
 msgid "Internal error."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:196
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
 msgid "I2PControl specific error codes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
 msgid "Invalid password provided."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
 msgid "No authentication token presented."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
 msgid "Authentication token doesn't exist."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
 msgid "The provided authentication token was expired and will be removed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
 msgid ""
 "The version of the I2PControl API used wasn't specified, but is required "
 "to be specified."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:203
 msgid ""
 "The version of the I2PControl API specified is not supported by "
 "I2PControl."
@@ -9297,9 +2536,7 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:43
 #, python-format
 msgid ""
-"The anonymous monotone"
-"\n"
+"The anonymous monotone\n"
 "sourcecode repository for I2P"
 msgstr ""
 
@@ -9621,12 +2858,6 @@ msgid ""
 "risks of socks proxies."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:3
-#: i2p2www/pages/site/docs/protocol/i2cp.html:3
-#: i2p2www/pages/site/docs/spec/streaming.html:3
-msgid "November 2012"
-msgstr ""
-
 #: i2p2www/pages/site/docs/api/streaming.html:8
 #, python-format
 msgid ""
@@ -9696,6 +2927,10 @@ msgid ""
 "it contains a full windowing implementation."
 msgstr ""
 
+#: i2p2www/pages/site/docs/api/streaming.html:58
+msgid "API"
+msgstr "API"
+
 #: i2p2www/pages/site/docs/api/streaming.html:60
 #, python-format
 msgid ""
@@ -9775,14 +3010,14 @@ msgid ""
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/streaming.html:117
-#: i2p2www/pages/site/docs/protocol/i2cp.html:94
-#: i2p2www/pages/site/docs/protocol/i2cp.html:437
+#: i2p2www/pages/site/docs/protocol/i2cp.html:102
+#: i2p2www/pages/site/docs/protocol/i2cp.html:445
 msgid "Option"
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/streaming.html:117
-#: i2p2www/pages/site/docs/protocol/i2cp.html:98
-#: i2p2www/pages/site/docs/protocol/i2cp.html:441
+#: i2p2www/pages/site/docs/protocol/i2cp.html:106
+#: i2p2www/pages/site/docs/protocol/i2cp.html:449
 msgid "Default"
 msgstr ""
 
@@ -9792,11 +3027,11 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/common-structures.html:58
 #: i2p2www/pages/site/docs/spec/common-structures.html:203
 #: i2p2www/pages/site/docs/spec/common-structures.html:257
-#: i2p2www/pages/site/docs/spec/common-structures.html:335
-#: i2p2www/pages/site/docs/spec/common-structures.html:421
-#: i2p2www/pages/site/docs/spec/common-structures.html:529
-#: i2p2www/pages/site/docs/spec/common-structures.html:607
-#: i2p2www/pages/site/docs/spec/common-structures.html:709
+#: i2p2www/pages/site/docs/spec/common-structures.html:351
+#: i2p2www/pages/site/docs/spec/common-structures.html:445
+#: i2p2www/pages/site/docs/spec/common-structures.html:553
+#: i2p2www/pages/site/docs/spec/common-structures.html:631
+#: i2p2www/pages/site/docs/spec/common-structures.html:739
 #: i2p2www/pages/site/docs/spec/datagrams.html:30
 #: i2p2www/pages/site/docs/spec/datagrams.html:89
 msgid "Notes"
@@ -9811,15 +3046,22 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/streaming.html:121
 #: i2p2www/pages/site/docs/api/streaming.html:127
 #: i2p2www/pages/site/docs/api/streaming.html:133
-#: i2p2www/pages/site/docs/api/streaming.html:147
-#: i2p2www/pages/site/docs/api/streaming.html:176
-#: i2p2www/pages/site/docs/api/streaming.html:184
-#: i2p2www/pages/site/docs/api/streaming.html:214
+#: i2p2www/pages/site/docs/api/streaming.html:140
+#: i2p2www/pages/site/docs/api/streaming.html:152
+#: i2p2www/pages/site/docs/api/streaming.html:163
+#: i2p2www/pages/site/docs/api/streaming.html:192
+#: i2p2www/pages/site/docs/api/streaming.html:200
 #: i2p2www/pages/site/docs/api/streaming.html:220
-#: i2p2www/pages/site/docs/api/streaming.html:226
-#: i2p2www/pages/site/docs/api/streaming.html:240
-#: i2p2www/pages/site/docs/api/streaming.html:247
-#: i2p2www/pages/site/docs/api/streaming.html:254
+#: i2p2www/pages/site/docs/api/streaming.html:237
+#: i2p2www/pages/site/docs/api/streaming.html:249
+#: i2p2www/pages/site/docs/api/streaming.html:255
+#: i2p2www/pages/site/docs/api/streaming.html:261
+#: i2p2www/pages/site/docs/api/streaming.html:275
+#: i2p2www/pages/site/docs/api/streaming.html:282
+#: i2p2www/pages/site/docs/api/streaming.html:289
+#: i2p2www/pages/site/docs/api/streaming.html:314
+#: i2p2www/pages/site/docs/api/streaming.html:321
+#: i2p2www/pages/site/docs/api/streaming.html:328
 #, python-format
 msgid "As of release %(release)s."
 msgstr ""
@@ -9832,11 +3074,11 @@ msgstr ""
 msgid "Use the access list as a blacklist for incoming connections."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:137
+#: i2p2www/pages/site/docs/api/streaming.html:145
 msgid "Whether to respond to incoming pings"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:141
+#: i2p2www/pages/site/docs/api/streaming.html:157
 msgid ""
 "Comma- or space-separated list of Base64 peer Hashes to be\n"
 "blacklisted for incoming connections to ALL destinations in the context.\n"
@@ -9847,13 +3089,13 @@ msgid ""
 "router in a separate JVM and context."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:151
+#: i2p2www/pages/site/docs/api/streaming.html:167
 msgid ""
 "How much transmit data (in bytes) will be accepted that hasn't been "
 "written out yet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:155
+#: i2p2www/pages/site/docs/api/streaming.html:171
 msgid ""
 "When we're in congestion avoidance, we grow the window size at the rate\n"
 "of 1/(windowSize*factor).  In standard TCP, window sizes are"
@@ -9862,7 +3104,7 @@ msgid ""
 "A higher number means slower growth."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:162
+#: i2p2www/pages/site/docs/api/streaming.html:178
 msgid ""
 "How long to wait after instantiating a new con \n"
 "before actually attempting to connect.  If this is\n"
@@ -9872,19 +3114,19 @@ msgid ""
 "or that many milliseconds pass, and include any initial data with the SYN."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:170
+#: i2p2www/pages/site/docs/api/streaming.html:186
 msgid ""
 "How long to block on connect, in milliseconds. Negative means "
 "indefinitely. Default is 5 minutes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:174
+#: i2p2www/pages/site/docs/api/streaming.html:190
 msgid ""
 "Whether to disable warnings in the logs when an incoming connection is "
 "rejected due to connection limits."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:180
+#: i2p2www/pages/site/docs/api/streaming.html:196
 msgid ""
 "Whether to listen only for the streaming protocol.\n"
 "Setting to true will prohibit communication with Destinations earlier "
@@ -9893,77 +3135,89 @@ msgid ""
 "Destination."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:188
+#: i2p2www/pages/site/docs/api/streaming.html:204
 msgid ""
 "(0=noop, 1=disconnect)\n"
 "What to do on an inactivity timeout - do nothing, disconnect, or send a "
 "duplicate ack."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:196
+#: i2p2www/pages/site/docs/api/streaming.html:212
 msgid ""
 "The initial value of the resend delay field in the packet header, times "
 "1000.\n"
 "Not fully implemented; see below."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:201
-#: i2p2www/pages/site/docs/api/streaming.html:203
+#: i2p2www/pages/site/docs/api/streaming.html:217
+msgid ""
+"Initial timeout\n"
+"(if no sharing data available)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:224
+msgid ""
+"Initial round trip time estimate\n"
+"(if no sharing data available).\n"
+"Disabled as of release 0.9.8; uses actual RTT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
 msgid "if no sharing data available"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:203
+#: i2p2www/pages/site/docs/api/streaming.html:230
 msgid ""
 "In standard TCP, window sizes are in bytes, while in I2P, window sizes "
 "are in messages."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:207
+#: i2p2www/pages/site/docs/api/streaming.html:242
 msgid ""
 "(0 or negative value means unlimited)\n"
 "This is a total limit for incoming and outgoing combined."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:212
+#: i2p2www/pages/site/docs/api/streaming.html:247
 msgid "Incoming connection limit (per peer; 0 means disabled)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:218
-#: i2p2www/pages/site/docs/api/streaming.html:224
+#: i2p2www/pages/site/docs/api/streaming.html:253
+#: i2p2www/pages/site/docs/api/streaming.html:259
 msgid "(per peer; 0 means disabled)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:230
+#: i2p2www/pages/site/docs/api/streaming.html:265
 msgid "The MTU in bytes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:234
+#: i2p2www/pages/site/docs/api/streaming.html:269
 msgid "Maximum number of retransmissions before failure."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:238
+#: i2p2www/pages/site/docs/api/streaming.html:273
 msgid "Incoming connection limit (all peers; 0 means disabled)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:244
-#: i2p2www/pages/site/docs/api/streaming.html:251
+#: i2p2www/pages/site/docs/api/streaming.html:279
+#: i2p2www/pages/site/docs/api/streaming.html:286
 msgid ""
 "(all peers; 0 means disabled)\n"
 "Use with caution as exceeding this will disable a server for a long time."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:260
+#: i2p2www/pages/site/docs/api/streaming.html:295
 msgid ""
 "(2=interactive not supported)\n"
 "This doesn't currently do anything, but setting it to a value other than "
 "1 will cause an error."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:265
+#: i2p2www/pages/site/docs/api/streaming.html:300
 msgid "How long to block on read, in milliseconds. Negative means indefinitely."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:269
+#: i2p2www/pages/site/docs/api/streaming.html:304
 msgid ""
 "When we're in slow start, we grow the window size at the rate\n"
 "of 1/(factor).  In standard TCP, window sizes are in bytes,\n"
@@ -9971,26 +3225,38 @@ msgid ""
 "A higher number means slower growth."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:276
+#: i2p2www/pages/site/docs/api/streaming.html:311
+#: i2p2www/pages/site/docs/api/streaming.html:318
+#: i2p2www/pages/site/docs/api/streaming.html:325
+msgid ""
+"Ref: RFC 2140. Floating point value.\n"
+"May be set only via context properties, not connection options."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:332
 msgid ""
 "How long to block on write/flush, in milliseconds. Negative means "
 "indefinitely."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:284
+#: i2p2www/pages/site/docs/api/streaming.html:340
 #: i2p2www/pages/site/docs/spec/streaming.html:10
 msgid "Protocol Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:286
+#: i2p2www/pages/site/docs/api/streaming.html:342
 msgid "See the Streaming Library Specification page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:290
+#: i2p2www/pages/site/docs/api/streaming.html:346
 msgid "Implementation Details"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:293
+#: i2p2www/pages/site/docs/api/streaming.html:348
+msgid "Setup"
+msgstr "Paramétrage"
+
+#: i2p2www/pages/site/docs/api/streaming.html:349
 msgid ""
 "The initiator sends a packet with the SYNCHRONIZE flag set. This packet "
 "may contain the initial data as well.\n"
@@ -9998,7 +3264,7 @@ msgid ""
 " may contain the initial response data as well."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:298
+#: i2p2www/pages/site/docs/api/streaming.html:354
 msgid ""
 "The initiator may send additional data packets, up to the initial window "
 "size, before receiving the SYNCHRONIZE response.\n"
@@ -10008,11 +3274,11 @@ msgid ""
 "arrive out of order, in advance of the SYNCHRONIZE packet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:305
+#: i2p2www/pages/site/docs/api/streaming.html:361
 msgid "MTU Selection and Negotiation"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:306
+#: i2p2www/pages/site/docs/api/streaming.html:362
 msgid ""
 "The maximum message size (also called the MTU / MRU) is negotiated to the"
 " lower value supported by\n"
@@ -10025,7 +3291,7 @@ msgid ""
 "including overhead for the typical case."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:315
+#: i2p2www/pages/site/docs/api/streaming.html:371
 msgid ""
 "The first message in a connection includes a 387 byte (typical) "
 "Destination added by the streaming layer,\n"
@@ -10043,7 +3309,7 @@ msgid ""
 "connections."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:326
+#: i2p2www/pages/site/docs/api/streaming.html:382
 #, python-format
 msgid ""
 "Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
@@ -10051,7 +3317,7 @@ msgid ""
 "There is no checksum field in the streaming protocol."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:334
+#: i2p2www/pages/site/docs/api/streaming.html:390
 #, python-format
 msgid ""
 "Each packet is sent through I2P as a single message (or as an individual "
@@ -10065,11 +3331,11 @@ msgid ""
 "mechanism or payload length field in the streaming protocol."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:344
+#: i2p2www/pages/site/docs/api/streaming.html:400
 msgid "Windowing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:345
+#: i2p2www/pages/site/docs/api/streaming.html:401
 msgid ""
 "The streaming lib uses standard slow-start (exponential window growth) "
 "and congestion avoidance (linear window growth)\n"
@@ -10077,11 +3343,11 @@ msgid ""
 "Windowing and acknowledgments use packet count, not byte count."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:352
+#: i2p2www/pages/site/docs/api/streaming.html:408
 msgid "Close"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:353
+#: i2p2www/pages/site/docs/api/streaming.html:409
 msgid ""
 "Any packet, including one with the SYNCHRONIZE flag set, may have the "
 "CLOSE flag sent as well.\n"
@@ -10090,15 +3356,50 @@ msgid ""
 "CLOSE packets may contain data as well."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:360
+#: i2p2www/pages/site/docs/api/streaming.html:417
+msgid ""
+"There is no ping function at the I2CP layer (equivalent to ICMP echo) or "
+"in datagrams.\n"
+"This function is provided in streaming.\n"
+"Pings and pongs may not be combined with a standard streaming packet;\n"
+"if the ECHO option is set, then\n"
+"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. "
+"are ignored."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:425
+msgid ""
+"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED "
+"flags set.\n"
+"The sendStreamId must be greater than zero, and the receiveStreamId is "
+"ignored.\n"
+"The sendStreamId may or may not correspond to an existing connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:431
+msgid ""
+"A pong packet must have the ECHO flag set.\n"
+"The sendStreamId must be zero, and the receiveStreamId is the "
+"sendStreamId from the ping.\n"
+"The pong packet does not include any payload that was contained in the "
+"ping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:437
+msgid ""
+"Streaming may be configured to disable sending pongs with the "
+"configuration i2p.streaming.answerPings=false."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:442
 msgid "Control Block Sharing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:361
+#: i2p2www/pages/site/docs/api/streaming.html:443
 msgid ""
 "The streaming lib supports \"TCP\" Control Block sharing.\n"
-"This shares two important streaming lib parameters\n"
-"(window size and round trip time)\n"
+"This shares three important streaming lib parameters\n"
+"(window size, round trip time, round trip time variance)\n"
 "across connections to the same remote peer.\n"
 "This is used for \"temporal\" sharing at connection open/close time,\n"
 "not \"ensemble\" sharing during a connection (See\n"
@@ -10107,25 +3408,26 @@ msgid ""
 "Destination)\n"
 "so that there is no information leakage to other Destinations on the\n"
 "same router.\n"
-"The share data for a given peer expires after a few minutes."
+"The share data for a given peer expires after a few minutes.\n"
+"The following Control Block Sharing parameters can be set per router:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:375
+#: i2p2www/pages/site/docs/api/streaming.html:464
 msgid "Other Parameters"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:376
+#: i2p2www/pages/site/docs/api/streaming.html:465
 msgid ""
 "The following parameters are hardcoded, but may be of interest for "
 "analysis:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:393
-#: i2p2www/pages/site/docs/how/network-database.html:831
+#: i2p2www/pages/site/docs/api/streaming.html:484
+#: i2p2www/pages/site/docs/how/network-database.html:843
 msgid "History"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:394
+#: i2p2www/pages/site/docs/api/streaming.html:485
 msgid ""
 "The streaming library has grown organically for I2P - first mihi "
 "implemented the\n"
@@ -10148,33 +3450,33 @@ msgid ""
 "messages."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:408
+#: i2p2www/pages/site/docs/api/streaming.html:499
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:331
 #: i2p2www/pages/site/docs/how/garlic-routing.html:242
-#: i2p2www/pages/site/docs/how/network-database.html:836
+#: i2p2www/pages/site/docs/how/network-database.html:848
 #: i2p2www/pages/site/docs/how/peer-selection.html:265
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:255
-#: i2p2www/pages/site/docs/protocol/i2cp.html:646
+#: i2p2www/pages/site/docs/protocol/i2cp.html:654
 #: i2p2www/pages/site/docs/protocol/i2np.html:227
-#: i2p2www/pages/site/docs/spec/updates.html:222
-#: i2p2www/pages/site/docs/transport/ntcp.html:443
-#: i2p2www/pages/site/docs/transport/ssu.html:502
+#: i2p2www/pages/site/docs/spec/updates.html:280
+#: i2p2www/pages/site/docs/transport/ntcp.html:446
+#: i2p2www/pages/site/docs/transport/ssu.html:506
 #: i2p2www/pages/site/docs/tunnels/implementation.html:503
 msgid "Future Work"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:409
+#: i2p2www/pages/site/docs/api/streaming.html:500
 msgid ""
 "The behavior of the streaming library has a profound impact on\n"
 "application-level performance, and as such, is an important\n"
 "area for further analysis."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:415
+#: i2p2www/pages/site/docs/api/streaming.html:506
 msgid "Additional tuning of the streaming lib parameters may be necessary."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:418
+#: i2p2www/pages/site/docs/api/streaming.html:509
 #, python-format
 msgid ""
 "Another area for research is the interaction of the streaming lib with "
@@ -10183,7 +3485,7 @@ msgid ""
 "See the NTCP discussion page for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:423
+#: i2p2www/pages/site/docs/api/streaming.html:514
 msgid ""
 "The interaction of the routing algorithms with the streaming lib strongly"
 " affects performance.\n"
@@ -10198,32 +3500,32 @@ msgid ""
 "improvements."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:433
+#: i2p2www/pages/site/docs/api/streaming.html:524
 msgid "The data in the first SYN packet may exceed the receiver's MTU."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:436
+#: i2p2www/pages/site/docs/api/streaming.html:527
 msgid "The DELAY_REQUESTED field could be used more."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:439
+#: i2p2www/pages/site/docs/api/streaming.html:530
 msgid ""
 "Duplicate initial SYNCHRONIZE packets on short-lived streams may not be "
 "recognized and removed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:442
+#: i2p2www/pages/site/docs/api/streaming.html:533
 msgid "Don't send the MTU in a retransmission."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:445
+#: i2p2www/pages/site/docs/api/streaming.html:536
 msgid ""
 "Data is sent along unless the outbound window is full.\n"
 "(i.e. no-Nagle or TCP_NODELAY)\n"
 "Probably should have a configuration option for this."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:450
+#: i2p2www/pages/site/docs/api/streaming.html:541
 msgid ""
 "zzz has added debug code to the streaming library to log packets in a "
 "wireshark-compatible\n"
@@ -10232,7 +3534,7 @@ msgid ""
 "to TCP fields."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:455
+#: i2p2www/pages/site/docs/api/streaming.html:546
 msgid ""
 "There are proposals to replace the streaming lib with standard TCP\n"
 "(or perhaps a null layer together with raw sockets).\n"
@@ -10389,7 +3691,7 @@ msgstr ""
 msgid ""
 "While compact response support is optional for both clients and trackers,"
 " it is highly\n"
-"recommended as it reduces the nominal response size by over 90%."
+"recommended as it reduces the nominal response size by over 90%."
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:116
@@ -10682,82 +3984,82 @@ msgid "Email"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:26
-#: i2p2www/pages/site/docs/applications/supported.html:315
+#: i2p2www/pages/site/docs/applications/supported.html:328
 msgid "File Sharing"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:29
-#: i2p2www/pages/site/docs/applications/supported.html:317
+#: i2p2www/pages/site/docs/applications/supported.html:330
 msgid "BitTorrent clients"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:31
-#: i2p2www/pages/site/docs/applications/supported.html:359
+#: i2p2www/pages/site/docs/applications/supported.html:372
 msgid "BitTorrent trackers and indexers"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:40
-#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:439
 msgid "Network Administration"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:43
-#: i2p2www/pages/site/docs/applications/supported.html:428
+#: i2p2www/pages/site/docs/applications/supported.html:441
 msgid "General-purpose socket utilities"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:50
-#: i2p2www/pages/site/docs/applications/supported.html:469
+#: i2p2www/pages/site/docs/applications/supported.html:482
 msgid "Real-time Chat"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:53
-#: i2p2www/pages/site/docs/applications/supported.html:471
+#: i2p2www/pages/site/docs/applications/supported.html:484
 msgid "Instant messaging clients"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:55
-#: i2p2www/pages/site/docs/applications/supported.html:481
+#: i2p2www/pages/site/docs/applications/supported.html:494
 msgid "IRC clients"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:57
-#: i2p2www/pages/site/docs/applications/supported.html:532
+#: i2p2www/pages/site/docs/applications/supported.html:545
 msgid "IRC servers"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:62
-#: i2p2www/pages/site/docs/applications/supported.html:548
+#: i2p2www/pages/site/docs/applications/supported.html:561
 msgid "Web Browsing"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:65
-#: i2p2www/pages/site/docs/applications/supported.html:550
+#: i2p2www/pages/site/docs/applications/supported.html:563
 msgid "Anonymous websites"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:67
-#: i2p2www/pages/site/docs/applications/supported.html:599
+#: i2p2www/pages/site/docs/applications/supported.html:612
 msgid "Proxy software"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:69
-#: i2p2www/pages/site/docs/applications/supported.html:624
+#: i2p2www/pages/site/docs/applications/supported.html:637
 msgid "Inproxies"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:71
-#: i2p2www/pages/site/docs/applications/supported.html:640
+#: i2p2www/pages/site/docs/applications/supported.html:669
 msgid "Outproxies"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:76
-#: i2p2www/pages/site/docs/applications/supported.html:654
+#: i2p2www/pages/site/docs/applications/supported.html:683
 msgid "Website Hosting"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:79
-#: i2p2www/pages/site/docs/applications/supported.html:669
+#: i2p2www/pages/site/docs/applications/supported.html:698
 msgid "Web servers"
 msgstr ""
 
@@ -10766,8 +4068,7 @@ msgstr ""
 msgid ""
 "This is intended to be a comprehensive listing of applications used with\n"
 "I2P. If you know of something that's missing please submit a ticket on\n"
-"Trac, and be sure to select the"
-"\n"
+"Trac, and be sure to select the\n"
 "“www” component in the submission form."
 msgstr ""
 
@@ -10780,8 +4081,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:97
 #: i2p2www/pages/site/docs/applications/supported.html:279
 #: i2p2www/pages/site/docs/applications/supported.html:311
-#: i2p2www/pages/site/docs/applications/supported.html:323
-#: i2p2www/pages/site/docs/applications/supported.html:666
+#: i2p2www/pages/site/docs/applications/supported.html:336
+#: i2p2www/pages/site/docs/applications/supported.html:695
 msgid "bundled"
 msgstr ""
 
@@ -10799,10 +4100,10 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:228
 #: i2p2www/pages/site/docs/applications/supported.html:241
 #: i2p2www/pages/site/docs/applications/supported.html:292
-#: i2p2www/pages/site/docs/applications/supported.html:391
-#: i2p2www/pages/site/docs/applications/supported.html:413
-#: i2p2www/pages/site/docs/applications/supported.html:422
-#: i2p2www/pages/site/docs/applications/supported.html:510
+#: i2p2www/pages/site/docs/applications/supported.html:404
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:523
 msgid "plugin"
 msgstr ""
 
@@ -10822,30 +4123,31 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:241
 #: i2p2www/pages/site/docs/applications/supported.html:252
 #: i2p2www/pages/site/docs/applications/supported.html:261
-#: i2p2www/pages/site/docs/applications/supported.html:329
-#: i2p2www/pages/site/docs/applications/supported.html:340
-#: i2p2www/pages/site/docs/applications/supported.html:355
-#: i2p2www/pages/site/docs/applications/supported.html:401
-#: i2p2www/pages/site/docs/applications/supported.html:413
-#: i2p2www/pages/site/docs/applications/supported.html:422
-#: i2p2www/pages/site/docs/applications/supported.html:437
-#: i2p2www/pages/site/docs/applications/supported.html:443
-#: i2p2www/pages/site/docs/applications/supported.html:449
-#: i2p2www/pages/site/docs/applications/supported.html:459
-#: i2p2www/pages/site/docs/applications/supported.html:465
-#: i2p2www/pages/site/docs/applications/supported.html:477
-#: i2p2www/pages/site/docs/applications/supported.html:510
-#: i2p2www/pages/site/docs/applications/supported.html:516
-#: i2p2www/pages/site/docs/applications/supported.html:522
-#: i2p2www/pages/site/docs/applications/supported.html:528
-#: i2p2www/pages/site/docs/applications/supported.html:605
-#: i2p2www/pages/site/docs/applications/supported.html:614
-#: i2p2www/pages/site/docs/applications/supported.html:620
-#: i2p2www/pages/site/docs/applications/supported.html:666
-#: i2p2www/pages/site/docs/applications/supported.html:681
-#: i2p2www/pages/site/docs/applications/supported.html:687
-#: i2p2www/pages/site/docs/applications/supported.html:693
-#: i2p2www/pages/site/docs/applications/supported.html:699
+#: i2p2www/pages/site/docs/applications/supported.html:324
+#: i2p2www/pages/site/docs/applications/supported.html:342
+#: i2p2www/pages/site/docs/applications/supported.html:353
+#: i2p2www/pages/site/docs/applications/supported.html:368
+#: i2p2www/pages/site/docs/applications/supported.html:414
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:450
+#: i2p2www/pages/site/docs/applications/supported.html:456
+#: i2p2www/pages/site/docs/applications/supported.html:462
+#: i2p2www/pages/site/docs/applications/supported.html:472
+#: i2p2www/pages/site/docs/applications/supported.html:478
+#: i2p2www/pages/site/docs/applications/supported.html:490
+#: i2p2www/pages/site/docs/applications/supported.html:523
+#: i2p2www/pages/site/docs/applications/supported.html:529
+#: i2p2www/pages/site/docs/applications/supported.html:535
+#: i2p2www/pages/site/docs/applications/supported.html:541
+#: i2p2www/pages/site/docs/applications/supported.html:618
+#: i2p2www/pages/site/docs/applications/supported.html:627
+#: i2p2www/pages/site/docs/applications/supported.html:633
+#: i2p2www/pages/site/docs/applications/supported.html:695
+#: i2p2www/pages/site/docs/applications/supported.html:710
+#: i2p2www/pages/site/docs/applications/supported.html:716
+#: i2p2www/pages/site/docs/applications/supported.html:722
+#: i2p2www/pages/site/docs/applications/supported.html:728
 msgid "standalone"
 msgstr ""
 
@@ -10854,11 +4156,11 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:202
 #: i2p2www/pages/site/docs/applications/supported.html:208
 #: i2p2www/pages/site/docs/applications/supported.html:214
-#: i2p2www/pages/site/docs/applications/supported.html:349
-#: i2p2www/pages/site/docs/applications/supported.html:373
-#: i2p2www/pages/site/docs/applications/supported.html:382
-#: i2p2www/pages/site/docs/applications/supported.html:538
-#: i2p2www/pages/site/docs/applications/supported.html:544
+#: i2p2www/pages/site/docs/applications/supported.html:362
+#: i2p2www/pages/site/docs/applications/supported.html:386
+#: i2p2www/pages/site/docs/applications/supported.html:395
+#: i2p2www/pages/site/docs/applications/supported.html:551
+#: i2p2www/pages/site/docs/applications/supported.html:557
 msgid "standalone/mod"
 msgstr ""
 
@@ -10875,14 +4177,16 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:135
 #: i2p2www/pages/site/docs/applications/supported.html:302
-#: i2p2www/pages/site/docs/applications/supported.html:558
-#: i2p2www/pages/site/docs/applications/supported.html:568
-#: i2p2www/pages/site/docs/applications/supported.html:577
-#: i2p2www/pages/site/docs/applications/supported.html:583
-#: i2p2www/pages/site/docs/applications/supported.html:589
-#: i2p2www/pages/site/docs/applications/supported.html:595
-#: i2p2www/pages/site/docs/applications/supported.html:636
-#: i2p2www/pages/site/docs/applications/supported.html:650
+#: i2p2www/pages/site/docs/applications/supported.html:571
+#: i2p2www/pages/site/docs/applications/supported.html:581
+#: i2p2www/pages/site/docs/applications/supported.html:590
+#: i2p2www/pages/site/docs/applications/supported.html:596
+#: i2p2www/pages/site/docs/applications/supported.html:602
+#: i2p2www/pages/site/docs/applications/supported.html:608
+#: i2p2www/pages/site/docs/applications/supported.html:649
+#: i2p2www/pages/site/docs/applications/supported.html:657
+#: i2p2www/pages/site/docs/applications/supported.html:665
+#: i2p2www/pages/site/docs/applications/supported.html:679
 msgid "service"
 msgstr ""
 
@@ -10898,7 +4202,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:148
 #: i2p2www/pages/site/docs/applications/supported.html:220
-#: i2p2www/pages/site/docs/applications/supported.html:355
+#: i2p2www/pages/site/docs/applications/supported.html:368
 msgid "unmaintained"
 msgstr ""
 
@@ -11026,15 +4330,24 @@ msgid ""
 "email service by default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:322
+#: i2p2www/pages/site/docs/applications/supported.html:316
+#, python-format
+msgid ""
+"Can be configured to use Postman's email service. See\n"
+"this comparison of MUAs,\n"
+"and configuration settings for\n"
+"SMTP and POP3."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:335
 msgid "I2P's integrated BitTorrent client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:328
+#: i2p2www/pages/site/docs/applications/supported.html:341
 msgid "Modified version of I2PSnark."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:334
+#: i2p2www/pages/site/docs/applications/supported.html:347
 msgid ""
 "\n"
 "A fork of rufus that uses the Basic Open Bridge (BOB) and has many\n"
@@ -11043,49 +4356,49 @@ msgid ""
 "magnet-link like fetching of torrents within I2P.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:345
+#: i2p2www/pages/site/docs/applications/supported.html:358
 msgid ""
 "Clean, full-featured cross-platform BitTorrent client with official\n"
 "ports for several GUI toolkits."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:354
+#: i2p2www/pages/site/docs/applications/supported.html:367
 msgid "Has a plugin providing I2P support."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:361
+#: i2p2www/pages/site/docs/applications/supported.html:374
 #, python-format
 msgid ""
 "For a detailed feature comparison of I2P-enabled trackers/indexers, see\n"
 "here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:369
+#: i2p2www/pages/site/docs/applications/supported.html:382
 msgid ""
 "The code that powered one of the first major tracker/indexer sites on the"
 "\n"
 "Internet. Patched for I2P."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:378
+#: i2p2www/pages/site/docs/applications/supported.html:391
 #, python-format
 msgid ""
 "Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n"
 "branch of the I2P Monotone repository."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:387
+#: i2p2www/pages/site/docs/applications/supported.html:400
 #, python-format
 msgid ""
 "zzz's Java-based open tracker. More info\n"
 "here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:400
+#: i2p2www/pages/site/docs/applications/supported.html:413
 msgid "I2P port of the aMule ED2K client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:409
+#: i2p2www/pages/site/docs/applications/supported.html:422
 #, python-format
 msgid ""
 "Port of the Phex Gnutella "
@@ -11093,44 +4406,44 @@ msgid ""
 "for plugin version here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:418
+#: i2p2www/pages/site/docs/applications/supported.html:431
 #, python-format
 msgid ""
 "Cache for Gnutella peers on I2P. Website for plugin version\n"
 "here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:433
+#: i2p2www/pages/site/docs/applications/supported.html:446
 msgid ""
 "Unix standard tool for socket relaying. Several clones, ports, and forks\n"
 "have appeared over the years."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:442
+#: i2p2www/pages/site/docs/applications/supported.html:455
 msgid "Like netcat but more powerful."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:448
+#: i2p2www/pages/site/docs/applications/supported.html:461
 msgid ""
 "Proxy providing simple, transparent SOCKS-ification of network "
 "applications."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:458
+#: i2p2www/pages/site/docs/applications/supported.html:471
 msgid ""
 "Most popular implementation of the Secure Shell (SSH) protocol and "
 "related tools."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:464
+#: i2p2www/pages/site/docs/applications/supported.html:477
 msgid "Open source Secure Shell (SSH) client for Windows."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:476
+#: i2p2www/pages/site/docs/applications/supported.html:489
 msgid "IM client with multiple incarnations."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:483
+#: i2p2www/pages/site/docs/applications/supported.html:496
 msgid ""
 "Many IRC clients leak identifying information to servers or other\n"
 "clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound"
@@ -11147,7 +4460,7 @@ msgid ""
 "/me command) which isn't inherently dangerous."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:494
+#: i2p2www/pages/site/docs/applications/supported.html:507
 msgid ""
 "I2P's IRC filtering may not cover every possible leak — users should also"
 "\n"
@@ -11160,100 +4473,105 @@ msgid ""
 "developers; they may be able to solve it via additional filtering."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:506
+#: i2p2www/pages/site/docs/applications/supported.html:519
 #, python-format
 msgid ""
 "Small Java-based IRC client. Plugin available here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:515
+#: i2p2www/pages/site/docs/applications/supported.html:528
 msgid "Cross-platform graphical IRC client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:521
+#: i2p2www/pages/site/docs/applications/supported.html:534
 msgid "Unixy terminal-based IRC client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:527
+#: i2p2www/pages/site/docs/applications/supported.html:540
 msgid "Another Unixy terminal-based IRC client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:537
+#: i2p2www/pages/site/docs/applications/supported.html:550
 msgid "IRC server developed from scratch."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:543
+#: i2p2www/pages/site/docs/applications/supported.html:556
 msgid "Most popular IRC server."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:555
+#: i2p2www/pages/site/docs/applications/supported.html:568
 msgid ""
 "Any website hosted anonymously on I2P, reachable through the I2P router's"
 " HTTP proxy."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:563
+#: i2p2www/pages/site/docs/applications/supported.html:576
 msgid ""
 "Distributed anonymous websites hosted\n"
 "using Tahoe-LAFS-I2P, currently only reachable with Tahoe-LAFS-I2P\n"
 "clients or through the Tahoe-LAFS-I2P HTTP proxy."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:573
+#: i2p2www/pages/site/docs/applications/supported.html:586
 #, python-format
 msgid ""
 "Website for sponge's jump service.\n"
 "Source code available."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:582
+#: i2p2www/pages/site/docs/applications/supported.html:595
 msgid "Another jump service."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:588
+#: i2p2www/pages/site/docs/applications/supported.html:601
 msgid "Dynamically updated eepsite index."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:594
+#: i2p2www/pages/site/docs/applications/supported.html:607
 #, python-format
 msgid "Website for zzz's jump service."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:604
+#: i2p2www/pages/site/docs/applications/supported.html:617
 msgid "SOCKS-enabled caching web proxy with basic filtering capabilities."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:610
+#: i2p2www/pages/site/docs/applications/supported.html:623
 msgid ""
 "Privacy-focused non-caching web proxy with advanced filtering\n"
 "capabilities. Excels at removing ads and other junk."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:619
+#: i2p2www/pages/site/docs/applications/supported.html:632
 msgid "Venerable caching web proxy."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:626
+#: i2p2www/pages/site/docs/applications/supported.html:639
 msgid "Gateways allowing users on the public Internet to access eepsites."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:633
+#: i2p2www/pages/site/docs/applications/supported.html:646
 #, python-format
 msgid "tino's inproxy on the public Internet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:642
+#: i2p2www/pages/site/docs/applications/supported.html:654
+#: i2p2www/pages/site/docs/applications/supported.html:662
+msgid "Another inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:671
 msgid ""
 "Gateways allowing I2P users to access content hosted on the public "
 "Internet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:649
+#: i2p2www/pages/site/docs/applications/supported.html:678
 msgid "Publicly advertised outproxy running Squid, located in Germany."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:659
+#: i2p2www/pages/site/docs/applications/supported.html:688
 msgid ""
 "Lightweight web server and Java servlet container. I2P is tightly\n"
 "integrated with a bundled copy of Jetty which by default is configured to"
@@ -11265,26 +4583,26 @@ msgid ""
 "I2P."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:671
+#: i2p2www/pages/site/docs/applications/supported.html:700
 msgid ""
 "In addition to Jetty, any web server should function over I2P without\n"
 "modification so long as it's HTTP-compliant. Some web servers known to\n"
 "currently serve content on the I2P network are:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:680
+#: i2p2www/pages/site/docs/applications/supported.html:709
 msgid "Most popular web server on the public WWW."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:686
+#: i2p2www/pages/site/docs/applications/supported.html:715
 msgid "Web server and Java servlet container. More features than Jetty."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:692
+#: i2p2www/pages/site/docs/applications/supported.html:721
 msgid "Fast lightweight web server."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:698
+#: i2p2www/pages/site/docs/applications/supported.html:727
 msgid "High-performance lightweight web server."
 msgstr ""
 
@@ -11784,7 +5102,7 @@ msgid ""
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/cryptography.html:34
-#: i2p2www/pages/site/docs/how/cryptography.html:189
+#: i2p2www/pages/site/docs/how/cryptography.html:198
 #, python-format
 msgid ""
 "For encryption of some netDb stores and "
@@ -11865,19 +5183,25 @@ msgstr ""
 msgid ""
 "While the standard exponent size is 2048 bits (256 bytes) and the I2P\n"
 "PrivateKey\n"
-"is a full 256 bytes,\n"
-"we use the short exponent size of 226 bits (28.25 bytes).\n"
+"is a full 256 bytes, in some cases\n"
+"we use the short exponent size of 226 bits (28.25 bytes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:150
+#, python-format
+msgid ""
 "This should be safe for use with the Oakley primes, per\n"
 "On Diffie-Hellman Key Agreement with Short Exponents "
 "- van Oorschot, Weiner\n"
 "at EuroCrypt 96, and crypto++'s "
 "benchmarks.\n"
-"Benchmarks originally at %(oldbenchmarks)s (now dead),\n"
+"Benchmarks originally at this link, now dead,\n"
 "rescued from the wayback machine,"
 " dated Apr 23, 2008."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:158
+#: i2p2www/pages/site/docs/how/cryptography.html:160
 #, python-format
 msgid ""
 "Also, Koshiba & Kurosawa: Short Exponent Diffie-"
@@ -11888,36 +5212,46 @@ msgid ""
 "The remainder of the PrivateKey is padded with zeroes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:167
-#: i2p2www/pages/site/docs/how/cryptography.html:264
-#: i2p2www/pages/site/docs/how/cryptography.html:343
-#: i2p2www/pages/site/docs/how/cryptography.html:382
+#: i2p2www/pages/site/docs/how/cryptography.html:169
+msgid ""
+"Prior to release 0.9.8, all routers used the short exponent.\n"
+"As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent.\n"
+"Other routers continue to use the short exponent due to concerns about "
+"processor load.\n"
+"The transition to a longer exponent for these platforms is a topic for "
+"further study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:176
+#: i2p2www/pages/site/docs/how/cryptography.html:273
+#: i2p2www/pages/site/docs/how/cryptography.html:352
+#: i2p2www/pages/site/docs/how/cryptography.html:391
 msgid "Obsolescence"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:168
+#: i2p2www/pages/site/docs/how/cryptography.html:177
 msgid ""
 "The vulnerability of the network to an ElGamal attack and the impact of "
 "transitioning to a longer bit length is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:176
+#: i2p2www/pages/site/docs/how/cryptography.html:185
 msgid "AES is used for symmetric encryption, in several cases:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:181
+#: i2p2www/pages/site/docs/how/cryptography.html:190
 msgid "For transport encryption after DH key exchange"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:185
+#: i2p2www/pages/site/docs/how/cryptography.html:194
 #, python-format
 msgid ""
 "For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:195
+#: i2p2www/pages/site/docs/how/cryptography.html:204
 #, python-format
 msgid ""
 "For encryption of periodic tunnel "
@@ -11925,7 +5259,7 @@ msgid ""
 "tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:200
+#: i2p2www/pages/site/docs/how/cryptography.html:209
 #, python-format
 msgid ""
 "We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n"
@@ -11940,27 +5274,27 @@ msgid ""
 "ElGamalAESEngine.getPadding function."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:265
+#: i2p2www/pages/site/docs/how/cryptography.html:274
 msgid ""
 "The vulnerability of the network to an AES attack and the impact of "
 "transitioning to a longer bit length is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:270
-#: i2p2www/pages/site/docs/how/cryptography.html:362
-#: i2p2www/pages/site/docs/how/cryptography.html:388
-#: i2p2www/pages/site/docs/how/cryptography.html:456
+#: i2p2www/pages/site/docs/how/cryptography.html:279
+#: i2p2www/pages/site/docs/how/cryptography.html:371
+#: i2p2www/pages/site/docs/how/cryptography.html:397
+#: i2p2www/pages/site/docs/how/cryptography.html:465
 #: i2p2www/pages/site/docs/how/garlic-routing.html:281
 #: i2p2www/pages/site/docs/how/peer-selection.html:296
 msgid "References"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:273
+#: i2p2www/pages/site/docs/how/cryptography.html:282
 msgid "Feb. 7, 2006 Status Notes"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:280
+#: i2p2www/pages/site/docs/how/cryptography.html:289
 #, python-format
 msgid ""
 "Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), "
@@ -11969,11 +5303,11 @@ msgid ""
 "DSA was chosen because it is much faster for signatures than ElGamal."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:286
+#: i2p2www/pages/site/docs/how/cryptography.html:295
 msgid "The DSA constants"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:337
+#: i2p2www/pages/site/docs/how/cryptography.html:346
 #, python-format
 msgid ""
 "The Signing Public"
@@ -11982,7 +5316,7 @@ msgid ""
 "Private Key is 160 bits."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:344
+#: i2p2www/pages/site/docs/how/cryptography.html:353
 #, python-format
 msgid ""
 "NIST 800-57\n"
@@ -11991,7 +5325,7 @@ msgid ""
 "given key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:350
+#: i2p2www/pages/site/docs/how/cryptography.html:359
 msgid ""
 "The prime number was chosen in 2003,\n"
 "and the person that chose the number (TheCrypto) is currently no longer "
@@ -12001,38 +5335,42 @@ msgid ""
 "prime, and we will document the construction process."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:357
+#: i2p2www/pages/site/docs/how/cryptography.html:366
 msgid ""
 "The vulnerability of the network to a DSA attack and the impact of "
 "transitioning to longer keys is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:365
-#: i2p2www/pages/site/docs/how/cryptography.html:367
+#: i2p2www/pages/site/docs/how/cryptography.html:374
+#: i2p2www/pages/site/docs/how/cryptography.html:376
 #, python-format
 msgid "Meeting %(num)s"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:369
+#: i2p2www/pages/site/docs/how/cryptography.html:378
 msgid "Choosing the constants"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:377
+#: i2p2www/pages/site/docs/how/cryptography.html:386
 #, python-format
 msgid ""
 "Hashes within I2P are plain old SHA256, as implemented in\n"
 "[SHA256Generator]"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:383
+#: i2p2www/pages/site/docs/how/cryptography.html:392
 msgid ""
 "The vulnerability of the network to a SHA-256 attack and the impact of "
 "transitioning to a longer hash is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:395
+#: i2p2www/pages/site/docs/how/cryptography.html:403
+msgid "Transports"
+msgstr "Transports"
+
+#: i2p2www/pages/site/docs/how/cryptography.html:404
 msgid ""
 "At the lowest protocol layer,\n"
 "point-to-point inter-router communication is protected by the transport "
@@ -12048,11 +5386,11 @@ msgid ""
 "on the transport links."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:407
+#: i2p2www/pages/site/docs/how/cryptography.html:416
 msgid "NTCP connections"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:409
+#: i2p2www/pages/site/docs/how/cryptography.html:418
 #, python-format
 msgid ""
 "NTCP connections are negotiated with a 2048 Diffie-Hellman "
@@ -12069,35 +5407,35 @@ msgid ""
 "href=\"%(elgamalaes)s\">ElGamalAES+SessionTag does not."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:417
+#: i2p2www/pages/site/docs/how/cryptography.html:426
 msgid ""
 "In order to migrate to a more standardized implementation (TLS/SSL or "
 "even SSH), the following issues must be addressed:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:421
+#: i2p2www/pages/site/docs/how/cryptography.html:430
 msgid ""
 "Can we somehow reestablish sessions securely (ala session tags) or do we "
 "need to do full negotiation each time?"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:424
+#: i2p2www/pages/site/docs/how/cryptography.html:433
 msgid ""
 "Can we simplify/avoid the x509 or other certificate formats and use our "
 "own RouterInfo structure (which \n"
 "contains the ElGamal and DSA keys)?"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:429
+#: i2p2www/pages/site/docs/how/cryptography.html:438
 #, python-format
 msgid "See the NTCP specification for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:433
+#: i2p2www/pages/site/docs/how/cryptography.html:442
 msgid "UDP connections"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:434
+#: i2p2www/pages/site/docs/how/cryptography.html:443
 msgid ""
 "SSU (the UDP transport) encrypts each packet with AES256/CBC with both an"
 " explicit IV and MAC \n"
@@ -12110,12 +5448,12 @@ msgid ""
 "checking."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:442
+#: i2p2www/pages/site/docs/how/cryptography.html:451
 #, python-format
 msgid "See the SSU specification for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:446
+#: i2p2www/pages/site/docs/how/cryptography.html:455
 #, python-format
 msgid ""
 "WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n"
@@ -13509,9 +6847,8 @@ msgid "The Network Database"
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/network-database.html:3
-#: i2p2www/pages/site/docs/protocol/i2np.html:3
-#: i2p2www/pages/site/docs/spec/common-structures.html:3
-msgid "June 2013"
+#: i2p2www/pages/site/docs/spec/updates.html:3
+msgid "October 2013"
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/network-database.html:8
@@ -13582,28 +6919,74 @@ msgid ""
 "approximate bandwidth, and perceived reachability"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/network-database.html:47
+msgid "SSU Testing"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/network-database.html:48
-msgid "The core library version, always the same as the router version"
+msgid "SSU Introducer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:49
+#: i2p2www/pages/site/docs/how/network-database.html:246
+msgid "Floodfill"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:50
+msgid "Hidden"
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/network-database.html:51
+#, python-format
+msgid "Under %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+#: i2p2www/pages/site/docs/how/network-database.html:53
+#: i2p2www/pages/site/docs/how/network-database.html:54
+#, python-format
+msgid "%(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+msgid "default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:55
+#, python-format
+msgid "Over %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:56
+msgid "Reachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:57
+msgid "Unreachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:62
+msgid "The core library version, always the same as the router version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:65
 msgid ""
 "Basic network compatibility - A router will refuse to communicate with a "
 "peer having a different netId"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:54
+#: i2p2www/pages/site/docs/how/network-database.html:68
 msgid "Used to determine compatibility with newer features and messages"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:57
+#: i2p2www/pages/site/docs/how/network-database.html:71
 msgid ""
 "Always sent as 90m, for compatibility with an older scheme where routers "
 "published their actual uptime,\n"
 "and only sent tunnel requests to peers whose was more than 60m"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:62
+#: i2p2www/pages/site/docs/how/network-database.html:76
 msgid ""
 "These values are used by other routers for basic decisions.\n"
 "Should we connect to this router? Should we attempt to route a tunnel "
@@ -13617,7 +7000,7 @@ msgid ""
 " and network analysis."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:72
+#: i2p2www/pages/site/docs/how/network-database.html:86
 #, python-format
 msgid ""
 "Additional text options include\n"
@@ -13632,15 +7015,15 @@ msgid ""
 "Current statistics are limited to:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:83
+#: i2p2www/pages/site/docs/how/network-database.html:97
 msgid "Client and exploratory tunnel build success, reject, and timeout rates"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:84
+#: i2p2www/pages/site/docs/how/network-database.html:98
 msgid "1 hour average number of participating tunnels"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:87
+#: i2p2www/pages/site/docs/how/network-database.html:101
 msgid ""
 "The data published can be seen in the router's user interface,\n"
 "but is not used or trusted within the router.\n"
@@ -13650,19 +7033,19 @@ msgid ""
 "releases."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:95
+#: i2p2www/pages/site/docs/how/network-database.html:109
 msgid "RouterInfo specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:98
+#: i2p2www/pages/site/docs/how/network-database.html:112
 msgid "RouterInfo Javadoc"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:101
+#: i2p2www/pages/site/docs/how/network-database.html:115
 msgid "RouterInfo Expiration"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:102
+#: i2p2www/pages/site/docs/how/network-database.html:116
 msgid ""
 "RouterInfos have no set expiration time.\n"
 "Each router is free to maintain its own local policy to trade off the "
@@ -13671,17 +7054,17 @@ msgid ""
 "In the current implementation, there are the following general policies:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:109
+#: i2p2www/pages/site/docs/how/network-database.html:123
 msgid ""
 "There is no expiration during the first hour of uptime, as the persistent"
 " stored data may be old."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:112
+#: i2p2www/pages/site/docs/how/network-database.html:126
 msgid "There is no expiration if there are 25 or less RouterInfos."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:115
+#: i2p2www/pages/site/docs/how/network-database.html:129
 msgid ""
 "As the number of local RouterInfos grows, the expiration time shrinks, in"
 " an attempt to maintain\n"
@@ -13690,7 +7073,7 @@ msgid ""
 "while expiration time with 300 routers is around 30 hours."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:120
+#: i2p2www/pages/site/docs/how/network-database.html:134
 #, python-format
 msgid ""
 "RouterInfos containing SSU introducers expire in "
@@ -13698,24 +7081,24 @@ msgid ""
 "the introducer list expires in about that time."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:124
+#: i2p2www/pages/site/docs/how/network-database.html:138
 msgid ""
 "Floodfills use a short expiration time (1 hour) for all local "
 "RouterInfos, as valid RouterInfos will\n"
 "be frequently republished to them."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:130
+#: i2p2www/pages/site/docs/how/network-database.html:144
 msgid "RouterInfo Persistent Storage"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:132
+#: i2p2www/pages/site/docs/how/network-database.html:146
 msgid ""
 "RouterInfos are periodically written to disk so that they are available "
 "after a restart."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:139
+#: i2p2www/pages/site/docs/how/network-database.html:153
 msgid ""
 "The second piece of data distributed in the netDb is a \"LeaseSet\" - "
 "documenting\n"
@@ -13724,73 +7107,73 @@ msgid ""
 "Each of these leases specify the following information:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:145
+#: i2p2www/pages/site/docs/how/network-database.html:159
 msgid "The tunnel gateway router (by specifying its identity)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:146
+#: i2p2www/pages/site/docs/how/network-database.html:160
 msgid "The tunnel ID on that router to send messages with (a 4 byte number)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:147
+#: i2p2www/pages/site/docs/how/network-database.html:161
 msgid "When that tunnel will expire."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:149
+#: i2p2www/pages/site/docs/how/network-database.html:163
 msgid ""
 "The LeaseSet itself is stored in the netDb under\n"
 "the key derived from the SHA256 of the destination."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:154
+#: i2p2www/pages/site/docs/how/network-database.html:168
 msgid "In addition to these leases, the LeaseSet includes:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:158
+#: i2p2www/pages/site/docs/how/network-database.html:172
 msgid ""
 "The destination itself (a 2048bit ElGamal encryption key, 1024bit DSA "
 "signing key and a certificate)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:159
+#: i2p2www/pages/site/docs/how/network-database.html:173
 msgid ""
 "Additional encryption public key: used for end-to-end encryption of "
 "garlic messages"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:160
+#: i2p2www/pages/site/docs/how/network-database.html:174
 msgid ""
 "Additional signing public key: intended for LeaseSet revocation, but is "
 "currently unused."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:161
+#: i2p2www/pages/site/docs/how/network-database.html:175
 msgid ""
 "Signature of all the LeaseSet data, to make sure the Destination "
 "published the LeaseSet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:165
+#: i2p2www/pages/site/docs/how/network-database.html:179
 msgid "Lease specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:167
+#: i2p2www/pages/site/docs/how/network-database.html:181
 msgid "LeaseSet specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:170
+#: i2p2www/pages/site/docs/how/network-database.html:184
 msgid "Lease Javadoc"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:172
+#: i2p2www/pages/site/docs/how/network-database.html:186
 msgid "LeaseSet Javadoc"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:176
+#: i2p2www/pages/site/docs/how/network-database.html:190
 msgid "Unpublished LeaseSets"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:177
+#: i2p2www/pages/site/docs/how/network-database.html:191
 msgid ""
 "A LeaseSet for a destination used only for outgoing connections is "
 "unpublished.\n"
@@ -13802,11 +7185,11 @@ msgid ""
 "because of I2NP storage messages."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:187
+#: i2p2www/pages/site/docs/how/network-database.html:201
 msgid "Revoked LeaseSets"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:188
+#: i2p2www/pages/site/docs/how/network-database.html:202
 msgid ""
 "A LeaseSet may be revoked by publishing a new LeaseSet with zero "
 "leases.\n"
@@ -13818,11 +7201,11 @@ msgid ""
 "unused."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:195
+#: i2p2www/pages/site/docs/how/network-database.html:209
 msgid "Encrypted LeaseSets"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:196
+#: i2p2www/pages/site/docs/how/network-database.html:210
 msgid ""
 "In an encrypted LeaseSet, all Leases are encrypted with a separate"
 " DSA key.\n"
@@ -13837,32 +7220,32 @@ msgid ""
 "LeaseSets could be improved."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:205
+#: i2p2www/pages/site/docs/how/network-database.html:219
 msgid "LeaseSet Expiration"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:206
+#: i2p2www/pages/site/docs/how/network-database.html:220
 msgid ""
 "All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet "
 "expires\n"
 "10 minutes after the earliest creation time of all its Leases."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:211
+#: i2p2www/pages/site/docs/how/network-database.html:225
 msgid "LeaseSet Persistent Storage"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:212
+#: i2p2www/pages/site/docs/how/network-database.html:226
 msgid ""
 "There is no persistent storage of LeaseSet data since they expire so "
 "quickly."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:217
+#: i2p2www/pages/site/docs/how/network-database.html:231
 msgid "Bootstrapping"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:218
+#: i2p2www/pages/site/docs/how/network-database.html:232
 msgid ""
 "The netDb is decentralized, however you do need at\n"
 "least one reference to a peer so that the integration process\n"
@@ -13883,11 +7266,7 @@ msgid ""
 "one of these URLs, selected at random."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:232
-msgid "Floodfill"
-msgstr ""
-
-#: i2p2www/pages/site/docs/how/network-database.html:233
+#: i2p2www/pages/site/docs/how/network-database.html:247
 msgid ""
 "The floodfill netDb is a simple distributed storage mechanism.\n"
 "The storage algorithm is simple: send the data to the closest peer that "
@@ -13906,24 +7285,24 @@ msgid ""
 "href=\"#kademlia_closeness\">XOR-metric) to a specific key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:244
+#: i2p2www/pages/site/docs/how/network-database.html:258
 msgid ""
 "Determining who is part of the floodfill netDb is trivial - it is exposed"
 " in each \n"
 "router's published routerInfo as a capability."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:249
+#: i2p2www/pages/site/docs/how/network-database.html:263
 msgid ""
 "Floodfills have no central authority and do not form a \"consensus\" -\n"
 "they only implement a simple DHT overlay."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:256
+#: i2p2www/pages/site/docs/how/network-database.html:270
 msgid "Floodfill Router Opt-in"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:258
+#: i2p2www/pages/site/docs/how/network-database.html:272
 msgid ""
 "Unlike Tor, where the directory servers are hardcoded and trusted,\n"
 "and operated by known entities,\n"
@@ -13931,7 +7310,7 @@ msgid ""
 "change over time."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:265
+#: i2p2www/pages/site/docs/how/network-database.html:279
 msgid ""
 "To increase reliability of the netDb, and minimize the impact\n"
 "of netDb traffic on a router, floodfill is automatically enabled\n"
@@ -13943,7 +7322,7 @@ msgid ""
 "KBytes/sec."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:275
+#: i2p2www/pages/site/docs/how/network-database.html:289
 msgid ""
 "In addition, a router must pass several additional tests for health\n"
 "(outbound message queue time, job lag, etc.) before floodfill operation "
@@ -13951,14 +7330,13 @@ msgid ""
 "automatically enabled."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:281
-#, python-format
+#: i2p2www/pages/site/docs/how/network-database.html:295
 msgid ""
-"With the current rules for automatic opt-in, approximately 6% of\n"
+"With the current rules for automatic opt-in, approximately 6% of\n"
 "the routers in the network are floodfill routers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:286
+#: i2p2www/pages/site/docs/how/network-database.html:300
 msgid ""
 "While some peers are manually configured to be floodfill,\n"
 "others are simply high-bandwidth routers who automatically volunteer\n"
@@ -13969,11 +7347,11 @@ msgid ""
 "too many floodfills outstanding."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:296
+#: i2p2www/pages/site/docs/how/network-database.html:310
 msgid "Floodfill Router Roles"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:297
+#: i2p2www/pages/site/docs/how/network-database.html:311
 msgid ""
 "A floodfill router's only services that are in addition to those of non-"
 "floodfill routers\n"
@@ -13984,11 +7362,11 @@ msgid ""
 "their distributed database services."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:305
+#: i2p2www/pages/site/docs/how/network-database.html:319
 msgid "Kademlia Closeness Metric"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:306
+#: i2p2www/pages/site/docs/how/network-database.html:320
 msgid ""
 "The netDb uses a simple Kademlia-style XOR metric to determine closeness."
 "\n"
@@ -14007,22 +7385,22 @@ msgid ""
 "although it isn't strictly a rotation."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:318
+#: i2p2www/pages/site/docs/how/network-database.html:332
 msgid ""
 "Routing keys are never sent on-the-wire in any I2NP message, they are "
 "only used locally for\n"
 "determination of distance."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:325
+#: i2p2www/pages/site/docs/how/network-database.html:339
 msgid "Storage, Verification, and Lookup Mechanics"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:327
+#: i2p2www/pages/site/docs/how/network-database.html:341
 msgid "RouterInfo Storage to Peers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:328
+#: i2p2www/pages/site/docs/how/network-database.html:342
 #, python-format
 msgid ""
 "I2NP DatabaseStoreMessages containing the local "
@@ -14031,11 +7409,11 @@ msgid ""
 "or SSU transport connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:335
+#: i2p2www/pages/site/docs/how/network-database.html:349
 msgid "LeaseSet Storage to Peers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:336
+#: i2p2www/pages/site/docs/how/network-database.html:350
 #, python-format
 msgid ""
 "I2NP DatabaseStoreMessages containing the local "
@@ -14048,7 +7426,7 @@ msgid ""
 "Destinations to have published LeaseSets at all."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:344
+#: i2p2www/pages/site/docs/how/network-database.html:358
 msgid ""
 "The DatabaseStoreMessage should be sent to the floodfill that is closest\n"
 "to the current routing key for the RouterInfo or LeaseSet being stored.\n"
@@ -14060,7 +7438,7 @@ msgid ""
 "This provides a high degree of fault-tolerance."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:353
+#: i2p2www/pages/site/docs/how/network-database.html:367
 msgid ""
 "In traditional Kademlia, a peer would do a \"find-closest\" search before"
 " inserting\n"
@@ -14081,11 +7459,11 @@ msgid ""
 "the netdb item."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:366
+#: i2p2www/pages/site/docs/how/network-database.html:380
 msgid "RouterInfo Storage to Floodfills"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:367
+#: i2p2www/pages/site/docs/how/network-database.html:381
 #, python-format
 msgid ""
 "A router publishes its own RouterInfo by directly connecting to a "
@@ -14100,18 +7478,18 @@ msgid ""
 "with the Message ID set to the value of the Reply Token."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:381
+#: i2p2www/pages/site/docs/how/network-database.html:395
 msgid "LeaseSet Storage to Floodfills"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:382
+#: i2p2www/pages/site/docs/how/network-database.html:396
 msgid ""
 "Storage of LeaseSets is much more sensitive than for RouterInfos, as a "
 "router\n"
 "must take care that the LeaseSet cannot be associated with the router."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:387
+#: i2p2www/pages/site/docs/how/network-database.html:401
 #, python-format
 msgid ""
 "A router publishes a local LeaseSet by\n"
@@ -14127,18 +7505,19 @@ msgid ""
 "This message is sent back to one of the client's inbound tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:400
+#: i2p2www/pages/site/docs/how/network-database.html:414
 msgid "Flooding"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:401
+#: i2p2www/pages/site/docs/how/network-database.html:415
+#, python-format
 msgid ""
 "After a floodfill router receives a DatabaseStoreMessage containing a\n"
 "valid RouterInfo or LeaseSet which is newer than that previously stored "
 "in its\n"
 "local NetDb, it \"floods\" it.\n"
-"To flood a NetDb entry, it looks up several (currently 4) floodfill "
-"routers closest to the routing key\n"
+"To flood a NetDb entry, it looks up several (currently %(floodsize)s) "
+"floodfill routers closest to the routing key\n"
 "of the NetDb entry. (The routing key is the SHA256 Hash of the "
 "RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n"
 "By flooding to those closest to the key, not closest to itself, the "
@@ -14148,7 +7527,7 @@ msgid ""
 "DHT \"neighborhood\" for the routing key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:412
+#: i2p2www/pages/site/docs/how/network-database.html:426
 #, python-format
 msgid ""
 "The floodfill then directly connects to each of those peers\n"
@@ -14159,11 +7538,11 @@ msgid ""
 "The other routers do not reply or re-flood, as the Reply Token is zero."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:422
+#: i2p2www/pages/site/docs/how/network-database.html:436
 msgid "RouterInfo and LeaseSet Lookup"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:423
+#: i2p2www/pages/site/docs/how/network-database.html:437
 #, python-format
 msgid ""
 "The I2NP DatabaseLookupMessage is used to "
@@ -14173,13 +7552,13 @@ msgid ""
 "exploratory tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:429
+#: i2p2www/pages/site/docs/how/network-database.html:443
 msgid ""
 "Lookups are generally sent to the two \"good\" (the connection doesn't "
 "fail) floodfill routers closest to the requested key, in parallel."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:433
+#: i2p2www/pages/site/docs/how/network-database.html:447
 #, python-format
 msgid ""
 "If the key is found locally by the floodfill router, it responds with a\n"
@@ -14190,7 +7569,7 @@ msgid ""
 "containing a list of other floodfill routers close to the key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:441
+#: i2p2www/pages/site/docs/how/network-database.html:455
 msgid ""
 "LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n"
 "RouterInfo lookups are not encrypted and thus are vulnerable to snooping "
@@ -14200,7 +7579,7 @@ msgid ""
 "RouterInfo lookup encryption may be enabled in a future release."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:448
+#: i2p2www/pages/site/docs/how/network-database.html:462
 msgid ""
 "As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage"
 " or a DatabaseSearchReplyMessage)\n"
@@ -14211,14 +7590,14 @@ msgid ""
 " encryption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:455
+#: i2p2www/pages/site/docs/how/network-database.html:469
 #, python-format
 msgid ""
 "(Reference: Hashing it out in Public Sections "
 "2.2-2.3 for terms below in italics)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:459
+#: i2p2www/pages/site/docs/how/network-database.html:473
 msgid ""
 "Due to the relatively small size of the network and the flooding "
 "redundancy of 8x,\n"
@@ -14234,7 +7613,7 @@ msgid ""
 "to reduce the chance of query failure."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:470
+#: i2p2www/pages/site/docs/how/network-database.html:484
 msgid ""
 "As of release 0.8.9, iterative lookups are implemented with no "
 "lookup redundancy.\n"
@@ -14252,7 +7631,7 @@ msgid ""
 "or the maximum number of peers is queried."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:482
+#: i2p2www/pages/site/docs/how/network-database.html:496
 msgid ""
 "Node IDs are verifiable in that we use the router hash "
 "directly as both the node ID and the Kademlia key.\n"
@@ -14262,11 +7641,21 @@ msgid ""
 "detailed knowledge of the neighborhood of the destination ID space."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:491
+#: i2p2www/pages/site/docs/how/network-database.html:505
 msgid "RouterInfo Storage Verification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:492
+#: i2p2www/pages/site/docs/how/network-database.html:506
+#, python-format
+msgid ""
+"Note: RouterInfo verification is disabled as of release 0.9.7.1 to "
+"prevent\n"
+"the attack described in the paper\n"
+"Practical Attacks Against the I2P Network.\n"
+"It is not clear if verification can be redesigned to be done safely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:513
 msgid ""
 "To verify a storage was successful, a router simply waits about 10 "
 "seconds,\n"
@@ -14277,11 +7666,11 @@ msgid ""
 "outbound endpoint(OBEP)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:500
+#: i2p2www/pages/site/docs/how/network-database.html:521
 msgid "LeaseSet Storage Verification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:501
+#: i2p2www/pages/site/docs/how/network-database.html:522
 msgid ""
 "To verify a storage was successful, a router simply waits about 10 "
 "seconds,\n"
@@ -14295,7 +7684,7 @@ msgid ""
 "tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:511
+#: i2p2www/pages/site/docs/how/network-database.html:532
 msgid ""
 "As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a "
 "DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n"
@@ -14303,11 +7692,11 @@ msgid ""
 "to hide the reply from the inbound gateway (IBGW) of the reply tunnel."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:519
+#: i2p2www/pages/site/docs/how/network-database.html:540
 msgid "Exploration"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:520
+#: i2p2www/pages/site/docs/how/network-database.html:541
 #, python-format
 msgid ""
 "Exploration is a special form of netdb lookup, where a router "
@@ -14330,11 +7719,11 @@ msgid ""
 "the requested key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:534
+#: i2p2www/pages/site/docs/how/network-database.html:555
 msgid "Notes on Lookup Responses"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:535
+#: i2p2www/pages/site/docs/how/network-database.html:556
 msgid ""
 "The response to a lookup request is either a Database Store Message (on "
 "success) or a\n"
@@ -14347,11 +7736,11 @@ msgid ""
 "difficult to monitor the performance of the various floodfill routers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:545
+#: i2p2www/pages/site/docs/how/network-database.html:566
 msgid "MultiHoming"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:547
+#: i2p2www/pages/site/docs/how/network-database.html:568
 msgid ""
 "Destinations may be hosted on multiple routers simultaneously, by using "
 "the same\n"
@@ -14368,18 +7757,18 @@ msgid ""
 "services on the network."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:557
+#: i2p2www/pages/site/docs/how/network-database.html:578
 msgid "Threat Analysis"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:558
+#: i2p2www/pages/site/docs/how/network-database.html:579
 #, python-format
 msgid ""
 "Also discussed on the threat model "
 "page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:562
+#: i2p2www/pages/site/docs/how/network-database.html:583
 msgid ""
 "A hostile user may attempt to harm the network by\n"
 "creating one or more floodfill routers and crafting them to offer\n"
@@ -14387,43 +7776,45 @@ msgid ""
 "Some scenarios are discussed below."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:569
+#: i2p2www/pages/site/docs/how/network-database.html:590
 msgid "General Mitigation Through Growth"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:570
+#: i2p2www/pages/site/docs/how/network-database.html:591
+#, python-format
 msgid ""
-"There are currently hundreds of floodfill routers in the network.\n"
+"There are currently around %(ffcount)s floodfill routers in the network.\n"
 "Most of the following attacks will become more difficult, or have less "
 "impact,\n"
 "as the network size and number of floodfill routers increase."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:577
+#: i2p2www/pages/site/docs/how/network-database.html:598
 msgid "General Mitigation Through Redundancy"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:578
+#: i2p2www/pages/site/docs/how/network-database.html:599
+#, python-format
 msgid ""
-"Via flooding, all netdb entries are stored on the 8 floodfill routers "
-"closest to the key."
+"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill"
+" routers closest to the key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:583
+#: i2p2www/pages/site/docs/how/network-database.html:604
 msgid "Forgeries"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:584
+#: i2p2www/pages/site/docs/how/network-database.html:605
 msgid ""
 "All netdb entries are signed by their creators, so no router may forge a\n"
 "RouterInfo or LeaseSet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:589
+#: i2p2www/pages/site/docs/how/network-database.html:610
 msgid "Slow or Unresponsive"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:590
+#: i2p2www/pages/site/docs/how/network-database.html:611
 #, python-format
 msgid ""
 "Each router maintains an expanded set of statistics in the\n"
@@ -14433,31 +7824,31 @@ msgid ""
 "The set includes:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:597
+#: i2p2www/pages/site/docs/how/network-database.html:618
 msgid "Average response time"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:598
+#: i2p2www/pages/site/docs/how/network-database.html:619
 msgid "Percentage of queries answered with the data requested"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:599
+#: i2p2www/pages/site/docs/how/network-database.html:620
 msgid "Percentage of stores that were successfully verified"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:600
+#: i2p2www/pages/site/docs/how/network-database.html:621
 msgid "Last successful store"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:601
+#: i2p2www/pages/site/docs/how/network-database.html:622
 msgid "Last successful lookup"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:602
+#: i2p2www/pages/site/docs/how/network-database.html:623
 msgid "Last response"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:605
+#: i2p2www/pages/site/docs/how/network-database.html:626
 msgid ""
 "Each time a router needs to make a determination on which floodfill "
 "router is closest to a key,\n"
@@ -14470,11 +7861,11 @@ msgid ""
 "routers that are only sometimes malicious may be much harder to deal with."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:615
+#: i2p2www/pages/site/docs/how/network-database.html:636
 msgid "Sybil Attack (Full Keyspace)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:616
+#: i2p2www/pages/site/docs/how/network-database.html:637
 #, python-format
 msgid ""
 "An attacker may mount a Sybil attack\n"
@@ -14482,7 +7873,7 @@ msgid ""
 "keyspace."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:621
+#: i2p2www/pages/site/docs/how/network-database.html:642
 #, python-format
 msgid ""
 "(In a related example, a researcher recently created a\n"
@@ -14491,7 +7882,7 @@ msgid ""
 "network."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:627
+#: i2p2www/pages/site/docs/how/network-database.html:648
 msgid ""
 "If the floodfills are not sufficiently misbehaving to be marked as "
 "\"bad\" using the peer profile\n"
@@ -14503,7 +7894,7 @@ msgid ""
 "none of them is completely satisfactory:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:635
+#: i2p2www/pages/site/docs/how/network-database.html:656
 msgid ""
 "Compile a list of bad router hashes or IPs, and announce the list through"
 " various means\n"
@@ -14512,30 +7903,30 @@ msgid ""
 "add it to their local \"blacklist\"."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:640
+#: i2p2www/pages/site/docs/how/network-database.html:661
 msgid ""
 "Ask everyone in the network to enable floodfill manually (fight Sybil "
 "with more Sybil)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:641
+#: i2p2www/pages/site/docs/how/network-database.html:662
 msgid "Release a new software version that includes the hardcoded \"bad\" list"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:642
+#: i2p2www/pages/site/docs/how/network-database.html:663
 msgid ""
 "Release a new software version that improves the peer profile metrics and"
 " thresholds,\n"
 "in an attempt to automatically identify the \"bad\" peers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:646
+#: i2p2www/pages/site/docs/how/network-database.html:667
 msgid ""
 "Add software that disqualifies floodfills if too many of them are in a "
 "single IP block"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:647
+#: i2p2www/pages/site/docs/how/network-database.html:668
 msgid ""
 "Implement an automatic subscription-based blacklist controlled by a "
 "single individual or group.\n"
@@ -14547,15 +7938,15 @@ msgid ""
 "or even to completely shutdown or destroy the entire network."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:656
+#: i2p2www/pages/site/docs/how/network-database.html:677
 msgid "This attack becomes more difficult as the network size grows."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:662
+#: i2p2www/pages/site/docs/how/network-database.html:683
 msgid "Sybil Attack (Partial Keyspace)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:663
+#: i2p2www/pages/site/docs/how/network-database.html:684
 #, python-format
 msgid ""
 "An attacker may mount a Sybil attack\n"
@@ -14569,7 +7960,7 @@ msgid ""
 "eepsite, for example."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:672
+#: i2p2www/pages/site/docs/how/network-database.html:693
 msgid ""
 "As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,"
 "\n"
@@ -14581,7 +7972,7 @@ msgid ""
 "size, is unknown."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:680
+#: i2p2www/pages/site/docs/how/network-database.html:701
 msgid ""
 "As a partial defense against this attack,\n"
 "the algorithm used to determine Kademlia \"closeness\" varies over time.\n"
@@ -14598,7 +7989,7 @@ msgid ""
 "to the target key, or to each other."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:692
+#: i2p2www/pages/site/docs/how/network-database.html:713
 msgid ""
 "This attack becomes more difficult as the network size grows.\n"
 "However, recent research demonstrates that the keyspace rotation is not "
@@ -14608,8 +7999,7 @@ msgid ""
 "of the keyspace within a half hour after rotation."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:700
-#: i2p2www/pages/site/docs/how/network-database.html:709
+#: i2p2www/pages/site/docs/how/network-database.html:721
 msgid ""
 "One consequence of daily keyspace rotation is that the distributed "
 "network database\n"
@@ -14621,11 +8011,11 @@ msgid ""
 "are a topic for further study."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:719
+#: i2p2www/pages/site/docs/how/network-database.html:731
 msgid "Bootstrap Attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:720
+#: i2p2www/pages/site/docs/how/network-database.html:732
 msgid ""
 "An attacker could attempt to boot new routers into an isolated\n"
 "or majority-controlled network by taking over a reseed website,\n"
@@ -14633,38 +8023,38 @@ msgid ""
 "to the hardcoded list in the router."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:727
+#: i2p2www/pages/site/docs/how/network-database.html:739
 msgid "Several defenses are possible, and most of these are planned:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:731
+#: i2p2www/pages/site/docs/how/network-database.html:743
 msgid ""
 "Disallow fallback from HTTPS to HTTP for reseeding.\n"
 "A MITM attacker could simply block HTTPS, then respond to the HTTP."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:735
+#: i2p2www/pages/site/docs/how/network-database.html:747
 msgid ""
 "Changing the reseed task to fetch a subset of RouterInfos from\n"
 "each of several reseed sites rather than using only a single site"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:739
+#: i2p2www/pages/site/docs/how/network-database.html:751
 msgid ""
 "Creating an out-of-network reseed monitoring service that\n"
 "periodically polls reseed websites and verifies that the\n"
 "data are not stale or inconsistent with other views of the network"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:744
+#: i2p2www/pages/site/docs/how/network-database.html:756
 msgid "Bundling reseed data in the installer"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:747
+#: i2p2www/pages/site/docs/how/network-database.html:759
 msgid "Query Capture"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:748
+#: i2p2www/pages/site/docs/how/network-database.html:760
 #, python-format
 msgid ""
 "See also lookup\n"
@@ -14672,7 +8062,7 @@ msgid ""
 "2.2-2.3 for terms below in italics)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:753
+#: i2p2www/pages/site/docs/how/network-database.html:765
 msgid ""
 "Similar to a bootstrap attack, an attacker using a floodfill router could"
 " attempt to \"steer\"\n"
@@ -14680,7 +8070,7 @@ msgid ""
 "references."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:758
+#: i2p2www/pages/site/docs/how/network-database.html:770
 msgid ""
 "This is unlikely to work via exploration, because exploration is a low-"
 "frequency task.\n"
@@ -14690,7 +8080,7 @@ msgid ""
 "and each exploration query is directed to a random floodfill router."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:765
+#: i2p2www/pages/site/docs/how/network-database.html:777
 #, python-format
 msgid ""
 "As of release 0.8.9, iterative lookups are implemented.\n"
@@ -14715,16 +8105,16 @@ msgid ""
 "is much more difficult."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:784
+#: i2p2www/pages/site/docs/how/network-database.html:796
 msgid "DHT-Based Relay Selection"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:785
+#: i2p2www/pages/site/docs/how/network-database.html:797
 #, python-format
 msgid "(Reference: Hashing it out in Public Section 3)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:789
+#: i2p2www/pages/site/docs/how/network-database.html:801
 #, python-format
 msgid ""
 "This doesn't have much to do with floodfill, but see\n"
@@ -14732,18 +8122,18 @@ msgid ""
 "for a discussion of the vulnerabilities of peer selection for tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:795
+#: i2p2www/pages/site/docs/how/network-database.html:807
 msgid "Information Leaks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:796
+#: i2p2www/pages/site/docs/how/network-database.html:808
 #, python-format
 msgid ""
 "(Reference: In Search of an Anonymous and Secure "
 "Lookup Section 3)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:800
+#: i2p2www/pages/site/docs/how/network-database.html:812
 #, python-format
 msgid ""
 "This paper addresses weaknesses in the \"Finger Table\" DHT lookups used "
@@ -14760,7 +8150,7 @@ msgid ""
 "Also, peer selection is unrelated to any notion of DHT key-closeness."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:811
+#: i2p2www/pages/site/docs/how/network-database.html:823
 msgid ""
 "Some of this may actually be more interesting when the I2P network gets "
 "much larger.\n"
@@ -14774,14 +8164,14 @@ msgid ""
 "much harder."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:819
+#: i2p2www/pages/site/docs/how/network-database.html:831
 #, python-format
 msgid ""
 "However, the general issue of DHT information leakage in I2P needs "
 "further investigation.\n"
 "The floodfill routers are in a position to observe queries and gather "
 "information.\n"
-"Certainly, at a level of f = 0.2 (20%% malicious nodes, as "
+"Certainly, at a level of f = 0.2 (20% malicious nodes, as "
 "specifed in the paper)\n"
 "we expect that many of the Sybil threats we describe\n"
 "(here,\n"
@@ -14790,15 +8180,15 @@ msgid ""
 "become problematic for several reasons."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:833
+#: i2p2www/pages/site/docs/how/network-database.html:845
 msgid "Moved to the netdb discussion page"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:837
+#: i2p2www/pages/site/docs/how/network-database.html:849
 msgid "End-to-end encryption of additional netDb lookups and responses."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:841
+#: i2p2www/pages/site/docs/how/network-database.html:853
 msgid "Better methods for tracking lookup responses."
 msgstr ""
 
@@ -15162,10 +8552,9 @@ msgid "Two peers from the same /16 IP space may not be in the same tunnel."
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:239
-#, python-format
 msgid ""
-"A peer may participate in a maximum of 33% of all tunnels created by the "
-"router."
+"A peer may participate in a maximum of 33% of all tunnels created by "
+"the router."
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:242
@@ -15268,7 +8657,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/how/tech-intro.html:9
 #: i2p2www/pages/site/docs/how/tech-intro.html:24
-#: i2p2www/pages/site/docs/transport/ssu.html:278
+#: i2p2www/pages/site/docs/transport/ssu.html:281
 msgid "Introduction"
 msgstr ""
 
@@ -15281,6 +8670,11 @@ msgstr ""
 msgid "Transport protocols"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tech-intro.html:17
+#: i2p2www/pages/site/docs/how/tech-intro.html:458
+msgid "Cryptography"
+msgstr "Cryptographie"
+
 #: i2p2www/pages/site/docs/how/tech-intro.html:25
 msgid ""
 "I2P is a scalable, self organizing, resilient packet switched anonymous \n"
@@ -16599,6 +9993,10 @@ msgid ""
 "network applications provide further functionality for end users."
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tech-intro.html:808
+msgid "Streaming library"
+msgstr "Librarie streaming"
+
 #: i2p2www/pages/site/docs/how/tech-intro.html:809
 msgid ""
 "The I2P streaming library can be viewed as a generic streaming interface "
@@ -16928,8 +10326,7 @@ msgstr ""
 #, python-format
 msgid ""
 "PyBit is a Bittorrent client written in Python.\n"
-"It is hosted on http://%(pebcache)s/"
-" "
+"It is hosted on %(pybit)s "
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/tech-intro.html:1015
@@ -17018,11 +10415,52 @@ msgstr ""
 msgid "November 2010"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:6
-msgid "What do we mean by \"anonymous\"?"
+#: i2p2www/pages/site/docs/how/threat-model.html:7
+msgid "low"
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/threat-model.html:8
+msgid "medium"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:9
+msgid "high"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:34
+msgid "Damage Potential"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:35
+msgid "Reliability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:36
+msgid "Exploitability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:37
+msgid "Affected Users"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:38
+msgid "Discoverability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:39
+msgid "Severity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:40
+#: i2p2www/pages/site/docs/protocol/i2np.html:94
+msgid "Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:45
+msgid "What do we mean by \"anonymous\"?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:47
 msgid ""
 "Your level of anonymity can be described as \"how hard it is for someone\n"
 "to find out information you don't want them to know?\" - who you are, "
@@ -17040,7 +10478,7 @@ msgid ""
 "data, to those fearful of discovery by powerful organizations or states."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:19
+#: i2p2www/pages/site/docs/how/threat-model.html:58
 msgid ""
 "The question of whether I2P provides sufficient anonymity for your \n"
 "particular needs is a hard one, but this page will hopefully assist in \n"
@@ -17049,7 +10487,7 @@ msgid ""
 "so that you may decide whether it meets your needs."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:26
+#: i2p2www/pages/site/docs/how/threat-model.html:65
 msgid ""
 "We welcome further research and analysis on I2P's resistance to the "
 "threats described below.\n"
@@ -17058,11 +10496,11 @@ msgid ""
 "work focused on I2P is needed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:32
+#: i2p2www/pages/site/docs/how/threat-model.html:71
 msgid "Network Topology Summary"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:33
+#: i2p2www/pages/site/docs/how/threat-model.html:72
 #, python-format
 msgid ""
 "I2P builds off the ideas of many other \n"
@@ -17071,7 +10509,7 @@ msgid ""
 "reviewing related literature:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:39
+#: i2p2www/pages/site/docs/how/threat-model.html:78
 msgid ""
 "I2P is a free route mixnet - the message creator explicitly "
 "defines the\n"
@@ -17082,7 +10520,7 @@ msgid ""
 "inbound tunnel)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:45
+#: i2p2www/pages/site/docs/how/threat-model.html:84
 msgid ""
 "I2P has no official entry and exit points - all peers fully "
 "participate in the \n"
@@ -17090,7 +10528,7 @@ msgid ""
 "application layer, a few proxies do exist)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:50
+#: i2p2www/pages/site/docs/how/threat-model.html:89
 msgid ""
 "I2P is fully distributed - there are no central controls or "
 "authorities.\n"
@@ -17105,7 +10543,7 @@ msgid ""
 "anonymity)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:60
+#: i2p2www/pages/site/docs/how/threat-model.html:99
 #, python-format
 msgid ""
 "We have documented plans to implement [Onion Routing],\n"
 "[Freenet], and\n"
-"[Tor].\n"
+"[Tor].\n"
 "Our design benefits substantially from the research published around that"
 " time.\n"
 "I2P uses several onion routing techniques, so we continue to benefit\n"
 "from the significant academic interest in Tor."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:89
+#: i2p2www/pages/site/docs/how/threat-model.html:128
 msgid ""
 "Taking from the attacks and analysis put forth in the \n"
 "anonymity "
@@ -17161,14 +10599,14 @@ msgid ""
 "this list to include new attacks as they are identified."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:98
+#: i2p2www/pages/site/docs/how/threat-model.html:137
 msgid ""
 "Included are some attacks that may be unique to I2P.\n"
 "We do not have good answers for all these attacks, however\n"
 "we continue to do research and improve our defenses."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:104
+#: i2p2www/pages/site/docs/how/threat-model.html:143
 msgid ""
 "In addition, many of these attacks are significantly easier than\n"
 "they should be, due to the modest size of the current network.\n"
@@ -17179,7 +10617,7 @@ msgid ""
 "these attacks will become much harder."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:114
+#: i2p2www/pages/site/docs/how/threat-model.html:153
 #, python-format
 msgid ""
 "The\n"
@@ -17189,94 +10627,98 @@ msgid ""
 "to review."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:123
-#: i2p2www/pages/site/docs/how/threat-model.html:143
+#: i2p2www/pages/site/docs/how/threat-model.html:182
+msgid "Index of Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:184
+#: i2p2www/pages/site/docs/how/threat-model.html:204
 msgid "Brute force attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:124
 #: i2p2www/pages/site/docs/how/threat-model.html:185
+#: i2p2www/pages/site/docs/how/threat-model.html:248
 msgid "Timing attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:125
-#: i2p2www/pages/site/docs/how/threat-model.html:220
+#: i2p2www/pages/site/docs/how/threat-model.html:186
+#: i2p2www/pages/site/docs/how/threat-model.html:285
 msgid "Intersection attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:126
-#: i2p2www/pages/site/docs/how/threat-model.html:298
+#: i2p2www/pages/site/docs/how/threat-model.html:187
+#: i2p2www/pages/site/docs/how/threat-model.html:365
 msgid "Denial of service attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:127
-#: i2p2www/pages/site/docs/how/threat-model.html:385
+#: i2p2www/pages/site/docs/how/threat-model.html:188
+#: i2p2www/pages/site/docs/how/threat-model.html:464
 msgid "Tagging attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:128
-#: i2p2www/pages/site/docs/how/threat-model.html:400
+#: i2p2www/pages/site/docs/how/threat-model.html:189
+#: i2p2www/pages/site/docs/how/threat-model.html:482
 msgid "Partitioning attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:129
-#: i2p2www/pages/site/docs/how/threat-model.html:438
+#: i2p2www/pages/site/docs/how/threat-model.html:190
+#: i2p2www/pages/site/docs/how/threat-model.html:522
 msgid "Predecessor attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:130
-#: i2p2www/pages/site/docs/how/threat-model.html:481
+#: i2p2www/pages/site/docs/how/threat-model.html:191
+#: i2p2www/pages/site/docs/how/threat-model.html:567
 msgid "Harvesting attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:131
-#: i2p2www/pages/site/docs/how/threat-model.html:525
+#: i2p2www/pages/site/docs/how/threat-model.html:192
+#: i2p2www/pages/site/docs/how/threat-model.html:614
 msgid "Identification Through Traffic Analysis"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:132
-#: i2p2www/pages/site/docs/how/threat-model.html:582
+#: i2p2www/pages/site/docs/how/threat-model.html:193
+#: i2p2www/pages/site/docs/how/threat-model.html:674
 msgid "Sybil attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:133
-#: i2p2www/pages/site/docs/how/threat-model.html:629
+#: i2p2www/pages/site/docs/how/threat-model.html:194
+#: i2p2www/pages/site/docs/how/threat-model.html:723
 msgid "Buddy Exhaustion attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:134
-#: i2p2www/pages/site/docs/how/threat-model.html:651
+#: i2p2www/pages/site/docs/how/threat-model.html:195
+#: i2p2www/pages/site/docs/how/threat-model.html:748
 msgid "Cryptographic attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:135
+#: i2p2www/pages/site/docs/how/threat-model.html:196
 msgid "Floodfill attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:136
-#: i2p2www/pages/site/docs/how/threat-model.html:707
+#: i2p2www/pages/site/docs/how/threat-model.html:197
+#: i2p2www/pages/site/docs/how/threat-model.html:809
 msgid "Other Network Database attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:137
+#: i2p2www/pages/site/docs/how/threat-model.html:198
 msgid "Attacks on centralized resources"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:138
-#: i2p2www/pages/site/docs/how/threat-model.html:770
+#: i2p2www/pages/site/docs/how/threat-model.html:199
+#: i2p2www/pages/site/docs/how/threat-model.html:875
 msgid "Development attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:139
+#: i2p2www/pages/site/docs/how/threat-model.html:200
 msgid "Implementation attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:140
-#: i2p2www/pages/site/docs/how/threat-model.html:849
+#: i2p2www/pages/site/docs/how/threat-model.html:201
+#: i2p2www/pages/site/docs/how/threat-model.html:959
 msgid "Other Defenses"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:145
+#: i2p2www/pages/site/docs/how/threat-model.html:208
 msgid ""
 "A brute force attack can be mounted by a global passive or active "
 "adversary, \n"
@@ -17297,7 +10739,7 @@ msgid ""
 "message)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:157
+#: i2p2www/pages/site/docs/how/threat-model.html:220
 msgid ""
 "However, a powerful attacker can use brute force to detect trends - if "
 "they \n"
@@ -17324,7 +10766,7 @@ msgid ""
 "not currently implemented."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:174
+#: i2p2www/pages/site/docs/how/threat-model.html:237
 #, python-format
 msgid ""
 "As a partial defense against a single router or group of routers trying "
@@ -17337,7 +10779,7 @@ msgid ""
 "peer selection page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:187
+#: i2p2www/pages/site/docs/how/threat-model.html:252
 msgid ""
 "I2P's messages are unidirectional and do not necessarily imply that a "
 "reply\n"
@@ -17353,7 +10795,7 @@ msgid ""
 "slow to have passed the message along."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:197
+#: i2p2www/pages/site/docs/how/threat-model.html:262
 msgid ""
 "This sort of attack is powerful, but its applicability to I2P is non "
 "obvious,\n"
@@ -17371,7 +10813,7 @@ msgid ""
 "DataMessage+DeliveryStatusMessage)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:207
+#: i2p2www/pages/site/docs/how/threat-model.html:272
 #, python-format
 msgid ""
 "Without protocol scrubbing or higher latency, global active adversaries "
@@ -17387,14 +10829,14 @@ msgid ""
 "but these are unimplemented in I2P."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:216
+#: i2p2www/pages/site/docs/how/threat-model.html:281
 #, python-format
 msgid ""
 "References: Low-Resource Routing Attacks Against "
 "Anonymous Systems"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:222
+#: i2p2www/pages/site/docs/how/threat-model.html:289
 msgid ""
 "Intersection attacks against low latency systems are extremely powerful -"
 "\n"
@@ -17410,7 +10852,7 @@ msgid ""
 "scenarios."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:232
+#: i2p2www/pages/site/docs/how/threat-model.html:299
 #, python-format
 msgid ""
 "In summary, if an attacker is at both ends of your tunnel at the same "
@@ -17421,61 +10863,61 @@ msgid ""
 "Tor provides a similar disclaimer."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:240
+#: i2p2www/pages/site/docs/how/threat-model.html:307
 msgid "Partial defenses implemented in I2P:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:244
+#: i2p2www/pages/site/docs/how/threat-model.html:311
 #, python-format
 msgid "strict ordering of peers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:247
+#: i2p2www/pages/site/docs/how/threat-model.html:314
 #, python-format
 msgid ""
 "peer profiling and selection from a "
 "small group that changes slowly"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:250
+#: i2p2www/pages/site/docs/how/threat-model.html:317
 msgid "Limits on the number of tunnels routed through a single peer"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:253
+#: i2p2www/pages/site/docs/how/threat-model.html:320
 msgid ""
 "Prevention of peers from the same /16 IP range from being members of a "
 "single tunnel"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:256
+#: i2p2www/pages/site/docs/how/threat-model.html:323
 msgid ""
 "For eepsites or other hosted services, we support\n"
 "simultaneous hosting on multiple routers, or\n"
 "multihoming"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:263
+#: i2p2www/pages/site/docs/how/threat-model.html:330
 msgid ""
 "Even in total, these defenses are not a complete solution.\n"
 "Also, we have made some design choices that may significantly increase "
 "our vulnerability:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:268
+#: i2p2www/pages/site/docs/how/threat-model.html:335
 msgid "We do not use low-bandwidth \"guard nodes\""
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:271
+#: i2p2www/pages/site/docs/how/threat-model.html:338
 msgid ""
 "We use tunnel pools comprised of several tunnels, and traffic can shift "
 "from tunnel to tunnel."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:274
+#: i2p2www/pages/site/docs/how/threat-model.html:341
 msgid "Tunnels are not long-lived; new tunnels are built every 10 minutes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:277
+#: i2p2www/pages/site/docs/how/threat-model.html:344
 msgid ""
 "Tunnel lengths are configurable.\n"
 "While 3-hop tunnels are recommended for full protection, several "
@@ -17483,7 +10925,7 @@ msgid ""
 "services use 2-hop tunnels by default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:284
+#: i2p2www/pages/site/docs/how/threat-model.html:351
 #, python-format
 msgid ""
 "In the future, it could\n"
@@ -17498,35 +10940,35 @@ msgid ""
 "as an adversary can't \"ping\" them to mount the attack.
            "
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:293
+#: i2p2www/pages/site/docs/how/threat-model.html:360
 #, python-format
 msgid "Reference: One Cell Enough"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:300
+#: i2p2www/pages/site/docs/how/threat-model.html:367
 msgid ""
 "There are a whole slew of denial of service attacks available against "
 "I2P,\n"
 "each with different costs and consequences:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:305
+#: i2p2www/pages/site/docs/how/threat-model.html:373
 msgid ""
 "Greedy user attack: This is simply\n"
 "people trying to consume significantly more resources than they are \n"
 "willing to contribute. The defense against this is:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:311
+#: i2p2www/pages/site/docs/how/threat-model.html:379
 #, python-format
 msgid ""
 "Set defaults so that most users provide resources to the network.\n"
 "In I2P, users route traffic by default. In sharp distinction to\n"
 "other networks,\n"
-"over 95%% of I2P users relay traffic for others."
+"over 95% of I2P users relay traffic for others."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:317
+#: i2p2www/pages/site/docs/how/threat-model.html:385
 msgid ""
 "Provide easy configuration options so that users may increase their\n"
 "contribution (share percentage) to the network. Display easy-to-"
@@ -17535,13 +10977,13 @@ msgid ""
 "contributing."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:322
+#: i2p2www/pages/site/docs/how/threat-model.html:390
 msgid ""
 "Maintain a strong community with blogs, forums, IRC, and other means of "
 "communication."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:327
+#: i2p2www/pages/site/docs/how/threat-model.html:397
 #, python-format
 msgid ""
 "Starvation attack: A hostile user may attempt to harm the network "
@@ -17570,7 +11012,7 @@ msgid ""
 "significant efforts required in this area."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:344
+#: i2p2www/pages/site/docs/how/threat-model.html:417
 #, python-format
 msgid ""
 "Flooding attack: A hostile user may attempt to flood the network,\n"
@@ -17601,7 +11043,7 @@ msgid ""
 "operation is implemented)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:360
+#: i2p2www/pages/site/docs/how/threat-model.html:436
 msgid ""
 "CPU load attack: There are currently some methods for people to \n"
 "remotely request that a peer perform some cryptographically expensive \n"
@@ -17616,7 +11058,7 @@ msgid ""
 "bugs in the implementation."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:370
+#: i2p2www/pages/site/docs/how/threat-model.html:449
 #, python-format
 msgid ""
 "Floodfill DOS attack: A hostile user may attempt to harm the "
@@ -17632,7 +11074,7 @@ msgid ""
 "network database page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:386
+#: i2p2www/pages/site/docs/how/threat-model.html:468
 #, python-format
 msgid ""
 "Tagging attacks - modifying a message so that it can later be identified"
@@ -17658,7 +11100,7 @@ msgid ""
 "as the links are encrypted and messages signed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:402
+#: i2p2www/pages/site/docs/how/threat-model.html:486
 msgid ""
 "Partitioning attacks - finding ways to segregate (technically or "
 "analytically)\n"
@@ -17687,7 +11129,7 @@ msgid ""
 "the moment)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:418
+#: i2p2www/pages/site/docs/how/threat-model.html:502
 #, python-format
 msgid ""
 "Partitioning the network analytically by looking for differences in how "
@@ -17717,14 +11159,14 @@ msgid ""
 "which other tunnels or messages have those delays)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:434
+#: i2p2www/pages/site/docs/how/threat-model.html:518
 #, python-format
 msgid ""
 "Also discussed on the network database "
 "page (bootstrap attack)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:440
+#: i2p2www/pages/site/docs/how/threat-model.html:526
 msgid ""
 "The predecessor attack is passively gathering statistics in an attempt to"
 " see\n"
@@ -17741,7 +11183,7 @@ msgid ""
 "target is located."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:450
+#: i2p2www/pages/site/docs/how/threat-model.html:536
 #, python-format
 msgid ""
 "I2P avoids this in four ways: first, the peers selected to participate in"
@@ -17766,7 +11208,7 @@ msgid ""
 "attackers will merely run into that gateway."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:467
+#: i2p2www/pages/site/docs/how/threat-model.html:553
 #, python-format
 msgid ""
 "The current tunnel build method\n"
@@ -17774,7 +11216,7 @@ msgid ""
 "See also the intersection attack."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:473
+#: i2p2www/pages/site/docs/how/threat-model.html:559
 #, python-format
 msgid ""
 "References: %(pdf2008)s\n"
@@ -17782,7 +11224,7 @@ msgid ""
 "%(pdf2004)s."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:482
+#: i2p2www/pages/site/docs/how/threat-model.html:571
 msgid ""
 "\"Harvesting\" means compiling a list of users running I2P.\n"
 "It can be used for legal attacks and to help\n"
@@ -17790,7 +11232,7 @@ msgid ""
 "harvesting whatever references to other peers it can find."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:489
+#: i2p2www/pages/site/docs/how/threat-model.html:578
 msgid ""
 "I2P itself is not designed with effective defenses against\n"
 "this attack, since there is the distributed network database \n"
@@ -17798,17 +11240,17 @@ msgid ""
 "The following factors make the attack somewhat harder in practice:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:496
+#: i2p2www/pages/site/docs/how/threat-model.html:585
 msgid ""
 "Network growth will make it more difficult to obtain a given proportion "
 "of the network"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:499
+#: i2p2www/pages/site/docs/how/threat-model.html:588
 msgid "Floodfill routers implement query limits as DOS protection"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:502
+#: i2p2www/pages/site/docs/how/threat-model.html:591
 msgid ""
 "\"Hidden mode\", which prevents a router from publishing its information "
 "to the netDb,\n"
@@ -17816,7 +11258,7 @@ msgid ""
 "could be."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:508
+#: i2p2www/pages/site/docs/how/threat-model.html:597
 #, python-format
 msgid ""
 "In future implementations,\n"
@@ -17830,7 +11272,7 @@ msgid ""
 "they can be reached (as well as their public keys, etc)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:517
+#: i2p2www/pages/site/docs/how/threat-model.html:606
 msgid ""
 "In the future, routers could use GeoIP to identify if they are in a "
 "particular\n"
@@ -17839,7 +11281,7 @@ msgid ""
 "enact other restricted route methods."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:526
+#: i2p2www/pages/site/docs/how/threat-model.html:618
 #, python-format
 msgid ""
 "By inspecting the traffic into and out of a router, a malicious ISP\n"
@@ -17853,21 +11295,21 @@ msgid ""
 "make it somewhat difficult to identify I2P traffic:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:536
+#: i2p2www/pages/site/docs/how/threat-model.html:628
 msgid "Random port selection"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:539
+#: i2p2www/pages/site/docs/how/threat-model.html:631
 msgid "Point-to-Point Encryption of all traffic"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:542
+#: i2p2www/pages/site/docs/how/threat-model.html:634
 msgid ""
 "DH key exchange with no protocol bytes or other unencrypted constant "
 "fields"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:545
+#: i2p2www/pages/site/docs/how/threat-model.html:637
 #, python-format
 msgid ""
 "Simultaneous use of both\n"
@@ -17877,62 +11319,61 @@ msgid ""
 " track."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:553
+#: i2p2www/pages/site/docs/how/threat-model.html:645
 msgid ""
 "In the near future, we plan to directly address traffic analysis issues "
 "by further obfuscation of I2P transport protocols, possibly including:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:557
+#: i2p2www/pages/site/docs/how/threat-model.html:649
 msgid ""
 "Padding at the transport layer to random lengths, especially during the "
 "connection handshake"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:560
+#: i2p2www/pages/site/docs/how/threat-model.html:652
 msgid ""
 "Study of packet size distribution signatures, and additional padding as "
 "necessary"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:563
+#: i2p2www/pages/site/docs/how/threat-model.html:655
 msgid ""
 "Development of additional transport methods that mimic SSL or other "
 "common protocols"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:566
+#: i2p2www/pages/site/docs/how/threat-model.html:658
 msgid ""
 "Review of padding strategies at higher layers to see how they affect "
 "packet sizes at the transport layer"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:569
+#: i2p2www/pages/site/docs/how/threat-model.html:661
 msgid ""
 "Review of methods implemented by various state-level firewalls to block "
 "Tor"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:572
+#: i2p2www/pages/site/docs/how/threat-model.html:664
 msgid "Working directly with DPI and obfuscation experts"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:577
+#: i2p2www/pages/site/docs/how/threat-model.html:669
 #, python-format
 msgid ""
 "Reference: Breaking and Improving Protocol "
 "Obfuscation"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:584
-#, python-format
+#: i2p2www/pages/site/docs/how/threat-model.html:678
 msgid ""
 "Sybil describes a category of attacks where the adversary creates "
 "arbitrarily\n"
 "large numbers of colluding nodes and uses the increased numbers to help \n"
 "mounting other attacks.  For instance, if an attacker is in a network "
 "where peers\n"
-"are selected randomly and they want an 80% chance to be one of those "
+"are selected randomly and they want an 80% chance to be one of those "
 "peers, they\n"
 "simply create five times the number of nodes that are in the network and "
 "roll \n"
@@ -17955,15 +11396,15 @@ msgid ""
 "scarcity)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:602
+#: i2p2www/pages/site/docs/how/threat-model.html:696
 msgid "Requiring HashCash Certificates in various places has two major problems:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:606
+#: i2p2www/pages/site/docs/how/threat-model.html:700
 msgid "Maintaining backward compatibility"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:609
+#: i2p2www/pages/site/docs/how/threat-model.html:703
 msgid ""
 "The classic HashCash problem -\n"
 "selecting HashCash values that are meaningful proofs of work on high-end "
@@ -17971,7 +11412,7 @@ msgid ""
 "while still being feasible on low-end machines such as mobile devices."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:616
+#: i2p2www/pages/site/docs/how/threat-model.html:710
 msgid ""
 "Various limitations on the number of routers in a given IP range restrict"
 "\n"
@@ -17981,21 +11422,21 @@ msgid ""
 "However, this is not a meaningful defense against a powerful adversary."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:623
+#: i2p2www/pages/site/docs/how/threat-model.html:717
 #, python-format
 msgid ""
 "See the network database page\n"
 "for more Sybil discussion."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:630
+#: i2p2www/pages/site/docs/how/threat-model.html:727
 #, python-format
 msgid ""
 "(Reference: In Search of an Anonymouns and Secure "
 "Lookup Section 5.2)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:634
+#: i2p2www/pages/site/docs/how/threat-model.html:731
 #, python-format
 msgid ""
 "By refusing to accept or forward tunnel build requests, except to a "
@@ -18009,7 +11450,7 @@ msgid ""
 "the performance\n"
 "of peers.\n"
 "However, this is a powerful attack as the number of routers approaches\n"
-"f = 0.2, or 20%% malicious nodes, as specifed in the paper.\n"
+"f = 0.2, or 20% malicious nodes, as specifed in the paper.\n"
 "The malicous routers could also maintain connections to the target router"
 " and provide\n"
 "excellent forwarding bandwidth for traffic over those connections, in an "
@@ -18018,7 +11459,7 @@ msgid ""
 "Further research and defenses may be necessary."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:653
+#: i2p2www/pages/site/docs/how/threat-model.html:752
 #, python-format
 msgid ""
 "We use strong cryptography with long keys, and\n"
@@ -18046,7 +11487,7 @@ msgid ""
 "shared secret values while maintaining backward compatibility."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:672
+#: i2p2www/pages/site/docs/how/threat-model.html:771
 #, python-format
 msgid ""
 "Upgrading the various data structures and protocols to support longer "
@@ -18059,7 +11500,7 @@ msgid ""
 "implement mechanisms to make it easier for future transitions."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:681
+#: i2p2www/pages/site/docs/how/threat-model.html:780
 msgid ""
 "In the future, several I2P protocols and data structures\n"
 "support securely padding messages to arbitrary sizes, so messages could "
@@ -18071,11 +11512,11 @@ msgid ""
 "end to end messages include simple random padding."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:691
+#: i2p2www/pages/site/docs/how/threat-model.html:790
 msgid "Floodfill Anonymity attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:692
+#: i2p2www/pages/site/docs/how/threat-model.html:794
 #, python-format
 msgid ""
 "In addition to the floodfill DOS attacks described\n"
@@ -18095,7 +11536,7 @@ msgid ""
 " future research."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:708
+#: i2p2www/pages/site/docs/how/threat-model.html:810
 #, python-format
 msgid ""
 "A hostile user may attempt to harm the network by\n"
@@ -18105,11 +11546,11 @@ msgid ""
 "network database page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:718
+#: i2p2www/pages/site/docs/how/threat-model.html:820
 msgid "Central Resource Attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:719
+#: i2p2www/pages/site/docs/how/threat-model.html:824
 msgid ""
 "There are a few centralized or limited resources (some inside I2P, some "
 "not)\n"
@@ -18124,14 +11565,14 @@ msgid ""
 "not the operation of the network itself."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:729
+#: i2p2www/pages/site/docs/how/threat-model.html:834
 #, python-format
 msgid ""
 "The website is mirrored and uses DNS round-robin"
 " for external public access."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:732
+#: i2p2www/pages/site/docs/how/threat-model.html:837
 #, python-format
 msgid ""
 "Routers now support multiple external reseed "
@@ -18141,17 +11582,17 @@ msgid ""
 "reseed hosts may need improvement."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:737
+#: i2p2www/pages/site/docs/how/threat-model.html:842
 msgid ""
 "Routers now support multiple update file locations.\n"
 "A malicious update host could feed a huge file, need to limit the size."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:741
+#: i2p2www/pages/site/docs/how/threat-model.html:846
 msgid "Routers now support multiple default trusted update signers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:744
+#: i2p2www/pages/site/docs/how/threat-model.html:849
 msgid ""
 "Routers now better handle multiple unreliable "
 "floodfill peers.\n"
@@ -18159,21 +11600,21 @@ msgid ""
 "href=\"#floodfill\">more study."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:748
+#: i2p2www/pages/site/docs/how/threat-model.html:853
 #, python-format
 msgid ""
 "The code is now stored in a distributed source "
 "control system."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:751
+#: i2p2www/pages/site/docs/how/threat-model.html:856
 msgid ""
 "Routers rely on a single news host, but there is a hardcoded backup URL "
 "pointing to a different host.\n"
 "A malicious news host could feed a huge file, need to limit the size."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:755
+#: i2p2www/pages/site/docs/how/threat-model.html:860
 #, python-format
 msgid ""
 "Naming system services, including addressbook "
@@ -18186,7 +11627,7 @@ msgid ""
 "the naming page for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:762
+#: i2p2www/pages/site/docs/how/threat-model.html:867
 msgid ""
 "We remain reliant on the DNS service for i2p2.de, losing this would cause"
 " substantial\n"
@@ -18195,7 +11636,7 @@ msgid ""
 "loss of i2p.net did."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:772
+#: i2p2www/pages/site/docs/how/threat-model.html:879
 msgid ""
 "These attacks aren't directly on the network, but instead go after its "
 "development team \n"
@@ -18211,11 +11652,11 @@ msgid ""
 "have a big problem."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:781
+#: i2p2www/pages/site/docs/how/threat-model.html:888
 msgid "However, two techniques help defend against these attacks:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:785
+#: i2p2www/pages/site/docs/how/threat-model.html:892
 #, python-format
 msgid ""
 "All components of the network must be open source to enable inspection, "
@@ -18231,7 +11672,7 @@ msgid ""
 "to restrict modifications to those previously approved."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:793
+#: i2p2www/pages/site/docs/how/threat-model.html:900
 #, python-format
 msgid ""
 "Development over the network itself, allowing developers to stay "
@@ -18245,18 +11686,18 @@ msgid ""
 "all available within I2P."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:804
+#: i2p2www/pages/site/docs/how/threat-model.html:911
 msgid ""
 "We also maintain relationships with various organizations that offer "
 "legal advice,\n"
 "should any defense be necessary."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:809
+#: i2p2www/pages/site/docs/how/threat-model.html:916
 msgid "Implementation attacks (bugs)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:810
+#: i2p2www/pages/site/docs/how/threat-model.html:920
 msgid ""
 "Try as we might, most nontrivial applications include errors in the "
 "design or \n"
@@ -18273,7 +11714,7 @@ msgid ""
 "obscurity."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:821
+#: i2p2www/pages/site/docs/how/threat-model.html:931
 msgid ""
 "In addition, the code is being \n"
 "treated the same way, with little aversion towards reworking or throwing "
@@ -18289,7 +11730,7 @@ msgid ""
 "enough to identify shortcomings and bugs."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:831
+#: i2p2www/pages/site/docs/how/threat-model.html:941
 msgid ""
 "Our software is likely, in particular, to contain bugs related to denial "
 "of service\n"
@@ -18299,7 +11740,7 @@ msgid ""
 "protocols."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:837
+#: i2p2www/pages/site/docs/how/threat-model.html:947
 #, python-format
 msgid ""
 "I2P is still a small network with a small development community and "
@@ -18311,11 +11752,11 @@ msgid ""
 "get involved and help."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:850
+#: i2p2www/pages/site/docs/how/threat-model.html:960
 msgid "Blocklists"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:851
+#: i2p2www/pages/site/docs/how/threat-model.html:961
 msgid ""
 "To some extent, I2P could be enhanced to avoid peers operating at IP "
 "addresses\n"
@@ -18325,7 +11766,7 @@ msgid ""
 "others."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:857
+#: i2p2www/pages/site/docs/how/threat-model.html:967
 msgid ""
 "To the extent that active peers actually do show up in the actual "
 "blocklist,\n"
@@ -18335,7 +11776,7 @@ msgid ""
 "enable it by default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:865
+#: i2p2www/pages/site/docs/how/threat-model.html:975
 msgid ""
 "Blocklists are only a part (perhaps a small part) of an array of defenses"
 "\n"
@@ -18346,7 +11787,7 @@ msgid ""
 "list above there are improvements we can make in detecting badness."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:874
+#: i2p2www/pages/site/docs/how/threat-model.html:984
 msgid ""
 "If a blocklist is hosted at a central location with automatic updates\n"
 "the network is vulnerable to a\n"
@@ -18356,7 +11797,7 @@ msgid ""
 "the i2p network down. Completely."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:882
+#: i2p2www/pages/site/docs/how/threat-model.html:992
 msgid ""
 "Currently, a default blocklist is distributed with our software,\n"
 "listing only the IPs of past DOS sources.\n"
@@ -18418,6 +11859,11 @@ msgstr ""
 msgid "Outbound Endpoint"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
+#: i2p2www/pages/site/docs/tunnels/implementation.html:140
+msgid "Inbound Gateway"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:31
 msgid "Inbound Participant"
 msgstr ""
@@ -18771,6 +12217,10 @@ msgid ""
 "profile."
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:230
+msgid "Tunnel creation"
+msgstr "Création de tunnel"
+
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:231
 #, python-format
 msgid ""
@@ -18835,10 +12285,18 @@ msgstr ""
 msgid "Tunnel creation specification"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:288
+msgid "Unidirectional tunnels"
+msgstr "Tunnels unidirectionels"
+
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:290
 msgid "Tunnel message specification"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:292
+msgid "Garlic routing"
+msgstr "Routage en oignon"
+
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:294
 msgid "ElGamal/AES+SessionTag"
 msgstr ""
@@ -18855,10 +12313,8 @@ msgid ""
 "It enables\n"
 "secure and asynchronous messaging by sending and receiving messages over "
 "a \n"
-"single TCP socket, yet never exposing any private keys and authenticating"
-" itself\n"
-"to the router only through signatures.  With I2CP, a client application "
-"tells the\n"
+"single TCP socket.\n"
+"With I2CP, a client application tells the\n"
 "router who they are (their \"destination\"), what anonymity, reliability,"
 " and \n"
 "latency tradeoffs to make, and where to send messages.  In turn the "
@@ -18871,28 +12327,19 @@ msgstr ""
 #: i2p2www/pages/site/docs/protocol/i2cp.html:18
 #, python-format
 msgid ""
-"The protocol itself has only been implemented in Java, to provide the\n"
+"The protocol itself is implemented in Java, to provide the\n"
 "Client SDK.\n"
 "This SDK is exposed in the i2p.jar package, which implements the client-"
 "side of I2CP.\n"
 "Clients should never need to access the router.jar package, which "
 "contains the\n"
-"router itself and the router-side of I2CP."
+"router itself and the router-side of I2CP.\n"
+"There is also a C library implementation.\n"
+"A non-Java client would also have to implement the\n"
+"streaming library for TCP-style connections."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:26
-#, python-format
-msgid ""
-"While implementing the client side of I2CP in a non-Java language is "
-"certainly feasible,\n"
-"a non-Java client would also have to implement the\n"
-"streaming library for TCP-style "
-"connections.\n"
-"Together, implementing I2CP and the streaming library would be a sizable "
-"task."
-msgstr ""
-
-#: i2p2www/pages/site/docs/protocol/i2cp.html:33
+#: i2p2www/pages/site/docs/protocol/i2cp.html:31
 #, python-format
 msgid ""
 "Applications can take advantage of the base I2CP plus the \n"
@@ -18908,7 +12355,7 @@ msgid ""
 "So there are several options for both Java and non-Java applications."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:45
+#: i2p2www/pages/site/docs/protocol/i2cp.html:43
 #, python-format
 msgid ""
 "Client-side end-to-end encryption (encrypting the data over the I2CP "
@@ -18924,7 +12371,7 @@ msgid ""
 " management of those keys."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:58
+#: i2p2www/pages/site/docs/protocol/i2cp.html:56
 msgid ""
 "In a standard I2P installation, port 7654 is used by external java "
 "clients to communicate\n"
@@ -18938,20 +12385,35 @@ msgid ""
 "through an internal JVM interface."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:67
+#: i2p2www/pages/site/docs/protocol/i2cp.html:65
+#, python-format
+msgid ""
+"The router also supports external connections over SSL.\n"
+"While SSL is not the default, it is strongly recommended for any traffic "
+"that may\n"
+"be exposed to the open Internet. The authorization user/password (if "
+"any), the\n"
+"Private Key and\n"
+"Signing Private "
+"Key for the\n"
+"Destination\n"
+"are all transmitted in-the-clear unless SSL is enabled."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:75
 msgid "I2CP Protocol Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:68
+#: i2p2www/pages/site/docs/protocol/i2cp.html:76
 #, python-format
 msgid "Now on the I2CP Specification page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:73
+#: i2p2www/pages/site/docs/protocol/i2cp.html:81
 msgid "I2CP Initialization"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:74
+#: i2p2www/pages/site/docs/protocol/i2cp.html:82
 #, python-format
 msgid ""
 "When a client connects to the router, it first sends a single protocol "
@@ -18969,11 +12431,11 @@ msgid ""
 "destinations."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:83
+#: i2p2www/pages/site/docs/protocol/i2cp.html:91
 msgid "I2CP Options"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:84
+#: i2p2www/pages/site/docs/protocol/i2cp.html:92
 #, python-format
 msgid ""
 "The following options are traditionally passed to the router via\n"
@@ -18983,54 +12445,54 @@ msgid ""
 "Message."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:90
+#: i2p2www/pages/site/docs/protocol/i2cp.html:98
 msgid "Router-side Options"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:95
-#: i2p2www/pages/site/docs/protocol/i2cp.html:438
+#: i2p2www/pages/site/docs/protocol/i2cp.html:103
+#: i2p2www/pages/site/docs/protocol/i2cp.html:446
 msgid "As Of Release"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:96
-#: i2p2www/pages/site/docs/protocol/i2cp.html:439
+#: i2p2www/pages/site/docs/protocol/i2cp.html:104
+#: i2p2www/pages/site/docs/protocol/i2cp.html:447
 msgid "Recommended Arguments"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:97
-#: i2p2www/pages/site/docs/protocol/i2cp.html:440
+#: i2p2www/pages/site/docs/protocol/i2cp.html:105
+#: i2p2www/pages/site/docs/protocol/i2cp.html:448
 msgid "Allowable Range"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:105
-#: i2p2www/pages/site/docs/protocol/i2cp.html:118
-#: i2p2www/pages/site/docs/protocol/i2cp.html:127
-#: i2p2www/pages/site/docs/protocol/i2cp.html:136
-#: i2p2www/pages/site/docs/protocol/i2cp.html:145
-#: i2p2www/pages/site/docs/protocol/i2cp.html:160
-#: i2p2www/pages/site/docs/protocol/i2cp.html:175
-#: i2p2www/pages/site/docs/protocol/i2cp.html:184
-#: i2p2www/pages/site/docs/protocol/i2cp.html:232
-#: i2p2www/pages/site/docs/protocol/i2cp.html:244
-#: i2p2www/pages/site/docs/protocol/i2cp.html:256
+#: i2p2www/pages/site/docs/protocol/i2cp.html:113
+#: i2p2www/pages/site/docs/protocol/i2cp.html:126
+#: i2p2www/pages/site/docs/protocol/i2cp.html:135
+#: i2p2www/pages/site/docs/protocol/i2cp.html:144
+#: i2p2www/pages/site/docs/protocol/i2cp.html:153
+#: i2p2www/pages/site/docs/protocol/i2cp.html:168
+#: i2p2www/pages/site/docs/protocol/i2cp.html:183
+#: i2p2www/pages/site/docs/protocol/i2cp.html:192
+#: i2p2www/pages/site/docs/protocol/i2cp.html:240
+#: i2p2www/pages/site/docs/protocol/i2cp.html:252
+#: i2p2www/pages/site/docs/protocol/i2cp.html:264
 #, python-format
 msgid "number from %(from)s to %(to)s"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:106
-#: i2p2www/pages/site/docs/protocol/i2cp.html:128
-#: i2p2www/pages/site/docs/protocol/i2cp.html:137
-#: i2p2www/pages/site/docs/protocol/i2cp.html:146
-#: i2p2www/pages/site/docs/protocol/i2cp.html:161
-#: i2p2www/pages/site/docs/protocol/i2cp.html:233
-#: i2p2www/pages/site/docs/protocol/i2cp.html:245
-#: i2p2www/pages/site/docs/protocol/i2cp.html:257
-#: i2p2www/pages/site/docs/protocol/i2cp.html:530
+#: i2p2www/pages/site/docs/protocol/i2cp.html:114
+#: i2p2www/pages/site/docs/protocol/i2cp.html:136
+#: i2p2www/pages/site/docs/protocol/i2cp.html:145
+#: i2p2www/pages/site/docs/protocol/i2cp.html:154
+#: i2p2www/pages/site/docs/protocol/i2cp.html:169
+#: i2p2www/pages/site/docs/protocol/i2cp.html:241
+#: i2p2www/pages/site/docs/protocol/i2cp.html:253
+#: i2p2www/pages/site/docs/protocol/i2cp.html:265
+#: i2p2www/pages/site/docs/protocol/i2cp.html:538
 #, python-format
 msgid "%(from)s to %(to)s"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:108
+#: i2p2www/pages/site/docs/protocol/i2cp.html:116
 msgid ""
 "Number of tunnels in.\n"
 "Limit was increased from 6 to 16 in release 0.9; however, numbers higher "
@@ -19039,25 +12501,25 @@ msgid ""
 " releases."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:119
-#: i2p2www/pages/site/docs/protocol/i2cp.html:176
-#: i2p2www/pages/site/docs/protocol/i2cp.html:185
+#: i2p2www/pages/site/docs/protocol/i2cp.html:127
+#: i2p2www/pages/site/docs/protocol/i2cp.html:184
+#: i2p2www/pages/site/docs/protocol/i2cp.html:193
 msgid "No limit"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:121
+#: i2p2www/pages/site/docs/protocol/i2cp.html:129
 msgid "Number of tunnels out"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:130
+#: i2p2www/pages/site/docs/protocol/i2cp.html:138
 msgid "Length of tunnels in"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:139
+#: i2p2www/pages/site/docs/protocol/i2cp.html:147
 msgid "Length of tunnels out"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:148
+#: i2p2www/pages/site/docs/protocol/i2cp.html:156
 msgid ""
 "Random amount to add or subtract to the length of tunnels in.\n"
 "A positive number x means add a random amount from 0 to x inclusive.\n"
@@ -19067,7 +12529,7 @@ msgid ""
 "The default variance was 1 prior to release 0.7.6."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:163
+#: i2p2www/pages/site/docs/protocol/i2cp.html:171
 msgid ""
 "Random amount to add or subtract to the length of tunnels out.\n"
 "A positive number x means add a random amount from 0 to x inclusive.\n"
@@ -19077,92 +12539,94 @@ msgid ""
 "The default variance was 1 prior to release 0.7.6."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:178
+#: i2p2www/pages/site/docs/protocol/i2cp.html:186
 msgid "Number of redundant fail-over for tunnels in"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:187
+#: i2p2www/pages/site/docs/protocol/i2cp.html:195
 msgid "Number of redundant fail-over for tunnels out"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:196
+#: i2p2www/pages/site/docs/protocol/i2cp.html:204
 msgid ""
 "Name of tunnel - generally used in routerconsole, which will\n"
 "use the first few characters of the Base64 hash of the destination by "
 "default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:208
+#: i2p2www/pages/site/docs/protocol/i2cp.html:216
 msgid "Name of tunnel - generally ignored unless inbound.nickname is unset."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:217
+#: i2p2www/pages/site/docs/protocol/i2cp.html:225
 msgid "If incoming zero hop tunnel is allowed"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:226
+#: i2p2www/pages/site/docs/protocol/i2cp.html:234
 msgid "If outgoing zero hop tunnel is allowed"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:235
-#: i2p2www/pages/site/docs/protocol/i2cp.html:247
+#: i2p2www/pages/site/docs/protocol/i2cp.html:243
+#: i2p2www/pages/site/docs/protocol/i2cp.html:255
 msgid ""
 "Number of IP bytes to match to determine if\n"
 "two routers should not be in the same tunnel. 0 to disable."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:259
+#: i2p2www/pages/site/docs/protocol/i2cp.html:267
 msgid ""
 "Priority adjustment for outbound messages.\n"
 "Higher is higher priority."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:271
+#: i2p2www/pages/site/docs/protocol/i2cp.html:279
 msgid "Should generally be set to true for clients and false for servers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:280
+#: i2p2www/pages/site/docs/protocol/i2cp.html:288
 msgid ""
 "Guaranteed is disabled;\n"
 "None implemented in 0.8.1; the streaming lib default is None as of 0.8.1,"
 " the client side default is None as of 0.9.4"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:292
-#: i2p2www/pages/site/docs/protocol/i2cp.html:571
+#: i2p2www/pages/site/docs/protocol/i2cp.html:300
+#: i2p2www/pages/site/docs/protocol/i2cp.html:579
 msgid ""
 "If true, the router just sends the MessagePayload instead\n"
 "of sending a MessageStatus and awaiting a ReceiveMessageBegin."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:304
+#: i2p2www/pages/site/docs/protocol/i2cp.html:312
 msgid ""
 "Comma-separated list of Base 64 Hashes of peers to build tunnels through;"
 " for debugging only"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:313
-#: i2p2www/pages/site/docs/protocol/i2cp.html:325
+#: i2p2www/pages/site/docs/protocol/i2cp.html:321
 msgid ""
 "For authorization, if required by the router.\n"
 "If the client is running in the same JVM as a router, this option is not "
-"required."
+"required.\n"
+"Warning - username and password are sent in the clear to the router, "
+"unless using SSL (i2cp.SSL=true).\n"
+"Authorization is only recommended when using SSL."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:337
+#: i2p2www/pages/site/docs/protocol/i2cp.html:343
 msgid ""
 "Number of ElGamal/AES Session Tags to send at a time.\n"
 "For clients with relatively low bandwidth per-client-pair (IRC, some UDP "
 "apps), this may be set lower."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:349
+#: i2p2www/pages/site/docs/protocol/i2cp.html:355
 msgid ""
 "Minimum number of ElGamal/AES Session Tags before we send more.\n"
 "Recommended: approximately tagsToSend * 2/3"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:361
+#: i2p2www/pages/site/docs/protocol/i2cp.html:367
 msgid ""
 "Set to false to disable ever bundling a reply LeaseSet.\n"
 "For clients that do not publish their LeaseSet, this option must be true\n"
@@ -19171,7 +12635,7 @@ msgid ""
 "with long connection times."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:368
+#: i2p2www/pages/site/docs/protocol/i2cp.html:374
 msgid ""
 "Setting to \"false\" may save significant outbound bandwidth, especially "
 "if\n"
@@ -19182,15 +12646,15 @@ msgid ""
 "There are several cases where \"false\" may be appropriate:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:376
+#: i2p2www/pages/site/docs/protocol/i2cp.html:382
 msgid "Unidirectional communication, no reply required"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:377
+#: i2p2www/pages/site/docs/protocol/i2cp.html:383
 msgid "LeaseSet is published and higher reply latency is acceptable"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:378
+#: i2p2www/pages/site/docs/protocol/i2cp.html:384
 msgid ""
 "LeaseSet is published, client is a \"server\", all connections are "
 "inbound\n"
@@ -19204,35 +12668,41 @@ msgid ""
 "HTTP servers may fit these requirements."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:396
+#: i2p2www/pages/site/docs/protocol/i2cp.html:402
 msgid ""
 "Any other options prefixed with \"inbound.\" are stored\n"
 "in the \"unknown options\" properties of the inbound tunnel pool's "
 "settings."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:408
+#: i2p2www/pages/site/docs/protocol/i2cp.html:414
 msgid ""
 "Any other options prefixed with \"outbound.\" are stored\n"
 "in the \"unknown options\" properties of the outbound tunnel pool's "
 "settings."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:415
+#: i2p2www/pages/site/docs/protocol/i2cp.html:421
 msgid ""
 "Note: Large quantity, length, or variance settings may cause significant "
 "performance or reliability problems."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:419
+#: i2p2www/pages/site/docs/protocol/i2cp.html:425
+#, python-format
 msgid ""
 "Note: As of release 0.7.7, option names and values must use UTF-8 "
 "encoding.\n"
 "This is primarily useful for nicknames.\n"
 "Prior to that release, options with multi-byte characters were corrupted."
+"\n"
+"Since options are encoded in a Mapping,\n"
+"all option names and values are limited to 255 bytes (not characters) "
+"maximum."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:425
+#: i2p2www/pages/site/docs/protocol/i2cp.html:433
 msgid ""
 "The following options are interpreted on the client side,\n"
 "and will be interpreted if passed to the I2PSession via the "
@@ -19241,76 +12711,76 @@ msgid ""
 "Other implementations may have different defaults."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:433
+#: i2p2www/pages/site/docs/protocol/i2cp.html:441
 msgid "Client-side Options"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:451
+#: i2p2www/pages/site/docs/protocol/i2cp.html:459
 msgid ""
 "Router hostname.\n"
 "If the client is running in the same JVM as a router, this option is "
 "ignored, and the client connects to that router internally."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:463
+#: i2p2www/pages/site/docs/protocol/i2cp.html:471
 msgid ""
 "Router I2CP port.\n"
 "If the client is running in the same JVM as a router, this option is "
 "ignored, and the client connects to that router internally."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:475
+#: i2p2www/pages/site/docs/protocol/i2cp.html:483
 msgid ""
 "Connect to the router using SSL.\n"
 "If the client is running in the same JVM as a router, this option is "
 "ignored, and the client connects to that router internally."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:487
+#: i2p2www/pages/site/docs/protocol/i2cp.html:495
 msgid "Gzip outbound data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:496
+#: i2p2www/pages/site/docs/protocol/i2cp.html:504
 msgid "Reduce tunnel quantity when idle"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:505
+#: i2p2www/pages/site/docs/protocol/i2cp.html:513
 msgid "Close I2P session when idle"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:512
-#: i2p2www/pages/site/docs/protocol/i2cp.html:521
+#: i2p2www/pages/site/docs/protocol/i2cp.html:520
+#: i2p2www/pages/site/docs/protocol/i2cp.html:529
 #, python-format
 msgid "%(num)s minimum"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:514
+#: i2p2www/pages/site/docs/protocol/i2cp.html:522
 msgid "(ms) Idle time required (default 20 minutes, minimum 5 minutes)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:523
+#: i2p2www/pages/site/docs/protocol/i2cp.html:531
 msgid "(ms) Idle time required (default 30 minutes)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:532
+#: i2p2www/pages/site/docs/protocol/i2cp.html:540
 msgid "Tunnel quantity when reduced (applies to both inbound and outbound)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:541
+#: i2p2www/pages/site/docs/protocol/i2cp.html:549
 msgid "Encrypt the lease"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:550
+#: i2p2www/pages/site/docs/protocol/i2cp.html:558
 msgid "Base64 SessionKey (44 characters)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:559
+#: i2p2www/pages/site/docs/protocol/i2cp.html:567
 msgid ""
 "Guaranteed is disabled;\n"
 "None implemented in 0.8.1; None is the default as of 0.9.4"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:578
+#: i2p2www/pages/site/docs/protocol/i2cp.html:586
 msgid ""
 "Note: All arguments, including numbers, are strings. True/false values "
 "are case-insensitive strings.\n"
@@ -19318,11 +12788,11 @@ msgid ""
 "All option names are case-sensitive."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:584
+#: i2p2www/pages/site/docs/protocol/i2cp.html:592
 msgid "I2CP Payload Data Format and Multiplexing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:585
+#: i2p2www/pages/site/docs/protocol/i2cp.html:593
 #, python-format
 msgid ""
 "The end-to-end messages handled by I2CP (i.e. the data sent by the client"
@@ -19343,61 +12813,52 @@ msgid ""
 "to work reliably in the presence of multiple channels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:599
+#: i2p2www/pages/site/docs/protocol/i2cp.html:607
 msgid ""
 "The gzip function cannot be completely turned off, however setting "
 "i2cp.gzip=false\n"
 "turns the gzip effort setting to 0, which may save a little CPU."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:605
+#: i2p2www/pages/site/docs/protocol/i2cp.html:613
 #: i2p2www/pages/site/docs/protocol/i2np.html:33
 msgid "Bytes"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:606
-#: i2p2www/pages/site/get-involved/index.html:38
+#: i2p2www/pages/site/docs/protocol/i2cp.html:614
 msgid "Content"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:611
+#: i2p2www/pages/site/docs/protocol/i2cp.html:619
 msgid "Gzip header"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:616
+#: i2p2www/pages/site/docs/protocol/i2cp.html:624
 msgid "Gzip flags"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:621
+#: i2p2www/pages/site/docs/protocol/i2cp.html:629
 msgid "I2P Source port (Gzip mtime)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:626
+#: i2p2www/pages/site/docs/protocol/i2cp.html:634
 msgid "I2P Destination port (Gzip mtime)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:631
+#: i2p2www/pages/site/docs/protocol/i2cp.html:639
 msgid "Gzip xflags"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:636
+#: i2p2www/pages/site/docs/protocol/i2cp.html:644
 msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:640
+#: i2p2www/pages/site/docs/protocol/i2cp.html:648
 msgid ""
 "Data integrity is verified with the standard gzip CRC-32 as\n"
 "specified by RFC 1952."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:648
-msgid "Implement I2CP and the streaming library in another programming language."
-msgstr ""
-
-#: i2p2www/pages/site/docs/protocol/i2cp.html:652
-msgid "Is the initial Get Date / Set Date handshake required?"
-msgstr ""
-
 #: i2p2www/pages/site/docs/protocol/i2cp.html:656
 msgid ""
 "The current authorization mechanism could be modified to use hashed "
@@ -19406,11 +12867,12 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/protocol/i2cp.html:660
 msgid ""
-"Private Keys are included in the Create Lease Set message,\n"
-"are they really required? Revocation is unimplemented."
+"The Signing Private Keys is included in the Create Lease Set message,\n"
+"it is not required. Revocation is unimplemented.\n"
+"It should be replaced with random data or removed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:665
+#: i2p2www/pages/site/docs/protocol/i2cp.html:666
 #, python-format
 msgid ""
 "Some improvements may be able to use messages previously defined but not "
@@ -19422,6 +12884,10 @@ msgid ""
 "Common Data Structures Specification Version 0.9."
 msgstr ""
 
+#: i2p2www/pages/site/docs/protocol/i2np.html:3
+msgid "June 2013"
+msgstr ""
+
 #: i2p2www/pages/site/docs/protocol/i2np.html:6
 msgid "I2P Network Protocol"
 msgstr ""
@@ -19558,12 +13024,12 @@ msgid ""
 "which is wrapped in a DataMessage."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2np.html:92
-msgid "Type"
+#: i2p2www/pages/site/docs/protocol/i2np.html:91
+msgid "Message"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2np.html:94
-msgid "Priority"
+#: i2p2www/pages/site/docs/protocol/i2np.html:92
+msgid "Type"
 msgstr ""
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:95
@@ -20007,8 +13473,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/blockfile.html:172
 #, python-format
 msgid ""
-"\"%%__INFO__%%\" is the master database skiplist with String/Properties "
-"key/value entries containing only one entry:"
+"%(INFO)s is the master database skiplist with String/Properties key/value"
+" entries containing only one entry:"
 msgstr ""
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:184
@@ -20018,8 +13484,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/blockfile.html:185
 #, python-format
 msgid ""
-"\"%%__REVERSE__%%\" is the reverse lookup skiplist with "
-"Integer/Properties key/value entries\n"
+"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties "
+"key/value entries\n"
 "    (as of database version 2):"
 msgstr ""
 
@@ -20078,14 +13544,13 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/common-structures.html:166
 #: i2p2www/pages/site/docs/spec/common-structures.html:178
 #: i2p2www/pages/site/docs/spec/common-structures.html:231
-#: i2p2www/pages/site/docs/spec/common-structures.html:298
-#: i2p2www/pages/site/docs/spec/common-structures.html:347
-#: i2p2www/pages/site/docs/spec/common-structures.html:391
-#: i2p2www/pages/site/docs/spec/common-structures.html:438
-#: i2p2www/pages/site/docs/spec/common-structures.html:573
-#: i2p2www/pages/site/docs/spec/common-structures.html:630
+#: i2p2www/pages/site/docs/spec/common-structures.html:314
+#: i2p2www/pages/site/docs/spec/common-structures.html:363
+#: i2p2www/pages/site/docs/spec/common-structures.html:415
+#: i2p2www/pages/site/docs/spec/common-structures.html:462
+#: i2p2www/pages/site/docs/spec/common-structures.html:597
+#: i2p2www/pages/site/docs/spec/common-structures.html:660
 #: i2p2www/pages/site/docs/spec/streaming.html:35
-#: i2p2www/pages/site/get-involved/develop/applications.html:8
 msgid "Contents"
 msgstr ""
 
@@ -20283,64 +13748,87 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:273
 msgid ""
-"Mappings contained in I2NP messages (i.e. in a RouterAddress or "
-"RouterInfo)\n"
-"must be sorted by key so that the signature will be invariant."
+"The encoding allows duplicate keys, however in any usage where the "
+"mapping is signed,\n"
+"duplicates may cause a signature failure."
 msgstr ""
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:278
 msgid ""
+"Mappings contained in I2NP messages (i.e. in a RouterAddress or "
+"RouterInfo)\n"
+"must be sorted by key so that the signature will be invariant.\n"
+"Duplicate keys are not allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:284
+#, python-format
+msgid ""
+"Mappings contained in an I2CP "
+"SessionConfig\n"
+"must be sorted by key so that the signature will be invariant.\n"
+"Duplicate keys are not allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:290
+msgid ""
+"While it is application-dependent, keys and values are generally case-"
+"sensitive."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:294
+msgid ""
 "Key and value string length limits are 255 bytes (not characters) each, "
 "plus the length byte. Length byte may be 0."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:282
+#: i2p2www/pages/site/docs/spec/common-structures.html:298
 msgid ""
 "Total length limit is 65535 bytes, plus the 2 byte size field, or 65537 "
 "total."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:291
+#: i2p2www/pages/site/docs/spec/common-structures.html:307
 msgid "Common structure specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:295
+#: i2p2www/pages/site/docs/spec/common-structures.html:311
 msgid "Defines the way to uniquely identify a particular router\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:299
+#: i2p2www/pages/site/docs/spec/common-structures.html:315
 msgid ""
 "PublicKey followed by SigningPublicKey and then a Certificate\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:336
+#: i2p2www/pages/site/docs/spec/common-structures.html:352
 msgid ""
 "The certificate for a RouterIdentity is currently unused and is always "
 "NULL."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:344
+#: i2p2www/pages/site/docs/spec/common-structures.html:360
 msgid ""
 "A Destination defines a particular endpoint to which messages can be "
 "directed for secure delivery.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:348
+#: i2p2www/pages/site/docs/spec/common-structures.html:364
 msgid ""
 "PublicKey followed by a SigningPublicKey and then a Certificate\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:388
+#: i2p2www/pages/site/docs/spec/common-structures.html:412
 msgid ""
 "Defines the authorization for a particular tunnel to receive messages "
 "targeting a Destination.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:392
+#: i2p2www/pages/site/docs/spec/common-structures.html:416
 msgid ""
 "SHA256 Hash of the\n"
 "RouterIdentity of the gateway "
@@ -20348,11 +13836,11 @@ msgid ""
 "end Date\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:423
+#: i2p2www/pages/site/docs/spec/common-structures.html:447
 msgid "Total size: 44 bytes"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:433
+#: i2p2www/pages/site/docs/spec/common-structures.html:457
 msgid ""
 "Contains all of the currently authorized Leases for a particular Destination.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:439
+#: i2p2www/pages/site/docs/spec/common-structures.html:463
 msgid ""
 "Destination, followed by a PublicKey for encryption, then a SigningPrivateKey"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:531
+#: i2p2www/pages/site/docs/spec/common-structures.html:555
 msgid ""
 "The public key of the destination was used for the old i2cp-to-i2cp "
 "encryption\n"
-"which was disabled in version 0.6, it is currently unused?"
+"which was disabled in version 0.6, it is currently unused."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:536
+#: i2p2www/pages/site/docs/spec/common-structures.html:560
 #, python-format
 msgid ""
 "The encryption key is used for end-to-end Integer defining the relative cost "
 "of using the address, where 0 is free and 255 is expensive, followed by "
@@ -20456,21 +13944,29 @@ msgid ""
 "IP address, port number, email address, URL, etc.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:609
+#: i2p2www/pages/site/docs/spec/common-structures.html:633
 msgid "Cost is typically 5 or 6 for SSU, and 10 or 11 for NTCP."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:613
+#: i2p2www/pages/site/docs/spec/common-structures.html:637
 msgid ""
 "Expiration is currently unused, always null (all zeroes)).\n"
 "As of release 0.9.3, the expiration is assumed zero and not stored, so "
 "any non-zero expiration\n"
 "will fail in the RouterInfo signature verification.\n"
 "Implementing expiration (or another use for these bytes) will be a "
-"backwards-incompatible change."
+"backwards-incompatible change.\n"
+"Routers MUST set this field to all zeros."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:626
+#: i2p2www/pages/site/docs/spec/common-structures.html:645
+msgid ""
+"The following options, while not required, are standard and expected to "
+"be present in most router addresses:\n"
+"\"host\" (an IPv4 or IPv6 address or host name) and \"port\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:656
 msgid ""
 "Defines all of the data that a router wants to publish for the network to"
 " see. The RouterInfo is one of two "
@@ -20480,27 +13976,34 @@ msgid ""
 "the contained RouterIdentity.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:631
+#: i2p2www/pages/site/docs/spec/common-structures.html:661
 msgid ""
 "RouterIdentity followed by the Date, when the entry was published\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:710
+#: i2p2www/pages/site/docs/spec/common-structures.html:741
 msgid ""
 "The peer_size Integer may be followed by a list of that many router "
 "hashes.\n"
 "This is currently unused. It was intended for a form of restricted "
-"routes, which is unimplemented.\n"
+"routes, which is unimplemented."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:715
+#: i2p2www/pages/site/docs/spec/common-structures.html:746
 msgid ""
 "The signature may be verified using the signing public key of the "
-"router_ident.\n"
+"router_ident."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:723
+#: i2p2www/pages/site/docs/spec/common-structures.html:750
+#, python-format
+msgid ""
+"See the network database page\n"
+"for standard options that are expected to be present in all router infos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:760
 #, python-format
 msgid ""
 "Defined in the Tunnel Message "
@@ -20632,10 +14135,18 @@ msgstr ""
 msgid "Enable/disable for each installed plugin."
 msgstr ""
 
+#: i2p2www/pages/site/docs/spec/configuration.html:70
+msgid "Router"
+msgstr "Routeur"
+
 #: i2p2www/pages/site/docs/spec/configuration.html:71
 msgid "Configured via /configadvanced in the router console."
 msgstr ""
 
+#: i2p2www/pages/site/docs/spec/configuration.html:75
+msgid "Applications"
+msgstr "Applications"
+
 #: i2p2www/pages/site/docs/spec/configuration.html:78
 msgid "See documentation in SusiDNS."
 msgstr ""
@@ -20841,44 +14352,64 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/spec/updates.html:35
 msgid ""
+"Parameters in the i2p.release entry are as follows.\n"
+"All keys are case-insensitive. All values must be enclosed in double "
+"quotes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:73
+msgid ""
 "The elements may be included inside XML comments to prevent "
 "interpretation by browsers.\n"
-"The i2p.release element and version are required. All others are optional"
-" and are\n"
-"currently unused."
+"The i2p.release element and version are required. All others are "
+"optional.\n"
+"NOTE: Due to parser limitations an entire element must be on a single "
+"line."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:41
-msgid ""
-"The news source is trusted only to indicate that a new version is "
-"available.\n"
-"It does not specify the URL of the update, the checksum, or any other "
-"information."
-msgstr ""
-
-#: i2p2www/pages/site/docs/spec/updates.html:47
+#: i2p2www/pages/site/docs/spec/updates.html:80
 msgid "Update File Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:48
+#: i2p2www/pages/site/docs/spec/updates.html:81
+msgid ""
+"As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n"
+"use the \"su3\" file format specified below.\n"
+"Approved release signers will use 4096-bit RSA keys.\n"
+"The X.509 public key certificates for these signers are distributed in "
+"the router installation packages.\n"
+"The updates may contain certificates for new, approved signers, and/or "
+"contain\n"
+"a list of certificates to delete for revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:91
+msgid "Old Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:92
+msgid "This format is obsolte as of release 0.9.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:95
 msgid ""
 "The signed update file, traditionally named i2pupdate.sud,\n"
 "is simply a zip file with a prepended 56 byte header.\n"
 "The header contains:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:54
+#: i2p2www/pages/site/docs/spec/updates.html:101
 #, python-format
 msgid ""
 "A 40-byte DSA "
 "signature"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:57
+#: i2p2www/pages/site/docs/spec/updates.html:104
 msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:62
+#: i2p2www/pages/site/docs/spec/updates.html:109
 #, python-format
 msgid ""
 "The signature covers only the zip archive - not the prepended version.\n"
@@ -20889,14 +14420,14 @@ msgid ""
 " managers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:68
+#: i2p2www/pages/site/docs/spec/updates.html:115
 msgid ""
 "For version comparison purposes, version fields contain [0-9]*, field "
 "separators are\n"
 "'-', '_', and '.', and all other characters are ignored."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:73
+#: i2p2www/pages/site/docs/spec/updates.html:120
 msgid ""
 "As of version 0.8.8, the version must also be specified as a zip file "
 "comment in UTF-8,\n"
@@ -20908,11 +14439,11 @@ msgid ""
 "This prevents spoofing of the version number in the header."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:81
+#: i2p2www/pages/site/docs/spec/updates.html:128
 msgid "Download and Installation"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:82
+#: i2p2www/pages/site/docs/spec/updates.html:129
 msgid ""
 "The router first downloads the header of the update file from one in a "
 "configurable list of I2P URLs,\n"
@@ -20928,21 +14459,21 @@ msgid ""
 "explained above."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:93
+#: i2p2www/pages/site/docs/spec/updates.html:140
 msgid "The zip file is extracted in the base $I2P installation directory."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:97
+#: i2p2www/pages/site/docs/spec/updates.html:144
 msgid ""
 "As of release 0.7.12, the router supports Pack200 decompression.\n"
 "Files inside the zip archive with a .jar.pack or .war.pack suffix\n"
 "are transparently decompressed to a .jar or .war file.\n"
 "Update files containing .pack files are traditionally named with a '.su2'"
 " suffix.\n"
-"Pack200 shrinks the update files by about 60%."
+"Pack200 shrinks the update files by about 60%."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:105
+#: i2p2www/pages/site/docs/spec/updates.html:152
 msgid ""
 "As of release 0.8.7, the router will delete the libjbigi.so and "
 "libjcpuid.so files\n"
@@ -20951,93 +14482,95 @@ msgid ""
 "be extracted from jbigi.jar."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:111
+#: i2p2www/pages/site/docs/spec/updates.html:158
 msgid ""
 "As of release 0.8.12, if the zip archive contains a file deletelist.txt, "
 "the router will\n"
 "delete the files listed there. The format is:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:116
+#: i2p2www/pages/site/docs/spec/updates.html:163
 msgid "One file name per line"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:117
+#: i2p2www/pages/site/docs/spec/updates.html:164
 msgid ""
 "All file names are relative to the installation directory; no absolute "
 "file names allowed, no files starting with \"..\""
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:118
+#: i2p2www/pages/site/docs/spec/updates.html:165
 msgid "Comments start with '#'"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:121
+#: i2p2www/pages/site/docs/spec/updates.html:168
 msgid "The router will then delete the deletelist.txt file."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:126
+#: i2p2www/pages/site/docs/spec/updates.html:173
 msgid "New \"su3\" Update File Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:128
-msgid "This specification is preliminary and is not yet implemented."
+#: i2p2www/pages/site/docs/spec/updates.html:175
+msgid ""
+"This specification is used for router updates and reseed data as of "
+"release 0.9.9."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:132
-msgid "Issues with existing .sud/.su2 format:"
+#: i2p2www/pages/site/docs/spec/updates.html:179
+msgid "Issues with the previous .sud/.su2 format:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:134
+#: i2p2www/pages/site/docs/spec/updates.html:181
 msgid "No magic number or flags"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:137
+#: i2p2www/pages/site/docs/spec/updates.html:184
 msgid "No way to specify compression, pack200 or not, or signing algo"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:140
+#: i2p2www/pages/site/docs/spec/updates.html:187
 msgid ""
 "Version is not covered by signature, so it is enforced by requiring it\n"
 "to be in the zip file comment (for router files) or in the plugin.config\n"
 "file (for plugins)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:145
+#: i2p2www/pages/site/docs/spec/updates.html:192
 msgid "Signer not specified so verifier must try all known keys"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:148
+#: i2p2www/pages/site/docs/spec/updates.html:195
 msgid "Signature-before-data format requires two passes to generate file"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:154
+#: i2p2www/pages/site/docs/spec/updates.html:201
 msgid "Goals:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:157
+#: i2p2www/pages/site/docs/spec/updates.html:204
 msgid "Fix above problems"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:160
+#: i2p2www/pages/site/docs/spec/updates.html:207
 msgid "Migrate to more secure signature algorithm"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:163
+#: i2p2www/pages/site/docs/spec/updates.html:210
 msgid ""
 "Keep version info in same format and offset for compatibility with\n"
 "existing version checkers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:169
+#: i2p2www/pages/site/docs/spec/updates.html:216
 msgid "Specification:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:217
+#: i2p2www/pages/site/docs/spec/updates.html:275
 msgid "All unused fields must be set to 0 for compatibility with future versions."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:224
+#: i2p2www/pages/site/docs/spec/updates.html:282
 msgid ""
 "The network will eventually grow too large for update over HTTP.\n"
 "The built-in BitTorrent client, i2psnark, may be used as a distributed "
@@ -21045,7 +14578,7 @@ msgid ""
 "This development effort is ongoing and should be completed by late 2013."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:229
+#: i2p2www/pages/site/docs/spec/updates.html:287
 msgid ""
 "The router update mechanism is part of the web router console.\n"
 "There is currently no provision for updates of an embedded router lacking"
@@ -21056,10 +14589,6 @@ msgstr ""
 msgid "Transport Overview"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:3
-msgid "April 2013"
-msgstr ""
-
 #: i2p2www/pages/site/docs/transport/index.html:6
 msgid "Transports in I2P"
 msgstr ""
@@ -21106,35 +14635,45 @@ msgid "The transport subsystem in I2P provides the following services:"
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/index.html:37
+#, python-format
 msgid ""
-"Maintain a set of router addresses, one or more for each transport,\n"
-"that the router publishes as its global contact information (the "
-"RouterInfo)"
-msgstr ""
-
-#: i2p2www/pages/site/docs/transport/index.html:41
-msgid "Selection of the best transport for each outgoing message"
+"Reliable delivery of I2NP messages.\n"
+"Transports support I2NP message delivery ONLY.\n"
+"They are not general-purpose data pipes."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/index.html:42
+msgid ""
+"Maintain a set of router addresses, one or more for each transport,\n"
+"that the router publishes as its global contact information (the "
+"RouterInfo).\n"
+"Each transport may connect using one of these addresses, which may be\n"
+"IPv4 or (as of version 0.9.8) IPv6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:48
+msgid "Selection of the best transport for each outgoing message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:49
 msgid "Queueing of outbound messages by priority"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:43
+#: i2p2www/pages/site/docs/transport/index.html:50
 msgid ""
 "Bandwidth limiting, both outbound and inbound, according to router "
 "configuration"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:44
+#: i2p2www/pages/site/docs/transport/index.html:51
 msgid "Setup and teardown of transport connections"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:45
+#: i2p2www/pages/site/docs/transport/index.html:52
 msgid "Encryption of point-to-point communications"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:46
+#: i2p2www/pages/site/docs/transport/index.html:53
 msgid ""
 "Maintenance of connection limits for each transport, implementation of "
 "various thresholds for these limits,\n"
@@ -21142,80 +14681,81 @@ msgid ""
 "operational changes based on the status"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:50
+#: i2p2www/pages/site/docs/transport/index.html:57
 msgid "Firewall port opening using UPnP (Universal Plug and Play)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:51
+#: i2p2www/pages/site/docs/transport/index.html:58
 msgid "Cooperative NAT/Firewall traversal"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:52
+#: i2p2www/pages/site/docs/transport/index.html:59
 msgid ""
 "Local IP detection by various methods, including UPnP, inspection of "
 "incoming connections, and enumeration of network devices"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:53
+#: i2p2www/pages/site/docs/transport/index.html:60
 msgid ""
 "Coordination of firewall status and local IP, and changes to either, "
 "among the transports"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:54
-#: i2p2www/pages/site/docs/transport/ssu.html:32
+#: i2p2www/pages/site/docs/transport/index.html:61
+#: i2p2www/pages/site/docs/transport/ssu.html:33
 msgid ""
 "Communication of firewall status and local IP, and changes to either, to "
 "the router and the user interface"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:55
+#: i2p2www/pages/site/docs/transport/index.html:62
 msgid ""
 "Determination of a consensus clock, which is used to periodically update "
 "the router's clock, as a backup for NTP"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:56
+#: i2p2www/pages/site/docs/transport/index.html:63
 msgid ""
 "Maintenance of status for each peer, including whether it is connected, "
 "whether it was recently connected,\n"
 "and whether it was reachable in the last attempt"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:60
+#: i2p2www/pages/site/docs/transport/index.html:67
 msgid "Qualification of valid IP addresses according to a local rule set"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:61
+#: i2p2www/pages/site/docs/transport/index.html:68
 msgid ""
 "Honoring the automated and manual lists of banned peers maintained by the"
 " router,\n"
 "and refusing outbound and inbound connections to those peers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:68
+#: i2p2www/pages/site/docs/transport/index.html:75
 msgid "Transport Addresses"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:70
+#: i2p2www/pages/site/docs/transport/index.html:77
 msgid ""
 "The transport subsystem maintains a set of router addresses, each of "
 "which lists a transport method, IP, and port.\n"
 "These addresses constitute the advertised contact points, and are "
-"published by the router to the network database."
+"published by the router to the network database.\n"
+"Addresses may also contain an arbitrary set of additional options."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:75
+#: i2p2www/pages/site/docs/transport/index.html:83
 msgid "Typical scenarios are:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:77
+#: i2p2www/pages/site/docs/transport/index.html:85
 msgid ""
 "A router has no published addresses, so it is considered \"hidden\" and "
 "cannot receive incoming connections"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:78
+#: i2p2www/pages/site/docs/transport/index.html:86
 #, python-format
 msgid ""
 "A router is firewalled, and therefore publishes an SSU address which "
@@ -21224,22 +14764,22 @@ msgid ""
 "href=\"%(ssu)s\">the SSU spec for details)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:82
+#: i2p2www/pages/site/docs/transport/index.html:90
 msgid ""
 "A router is not firewalled or its NAT ports  are open; it publishes both "
 "NTCP and SSU addresses containing\n"
 "directly-accessible IP and ports."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:88
+#: i2p2www/pages/site/docs/transport/index.html:96
 msgid "Transport Selection"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:90
+#: i2p2www/pages/site/docs/transport/index.html:98
 #, python-format
 msgid ""
-"The transport system delivers I2NP messages. The"
-" transport selected for any message is\n"
+"The transport system delivers I2NP messages "
+"only. The transport selected for any message is\n"
 "independent of the upper-layer protocols and contents (router or client "
 "messages, whether an external application was using\n"
 "TCP or UDP to connect to I2P, whether the upper layer was using\n"
@@ -21251,7 +14791,7 @@ msgid ""
 "etc.)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:104
+#: i2p2www/pages/site/docs/transport/index.html:112
 msgid ""
 "For each outgoing message, the transport system solicits \"bids\" from "
 "each transport.\n"
@@ -21260,84 +14800,74 @@ msgid ""
 "A transport may refuse to bid."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:110
+#: i2p2www/pages/site/docs/transport/index.html:118
 msgid "Whether a transport bids, and with what value, depend on numerous factors:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:114
+#: i2p2www/pages/site/docs/transport/index.html:122
 msgid "Configuration of transport preferences"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:115
+#: i2p2www/pages/site/docs/transport/index.html:123
 msgid "Whether the transport is already connected to the peer"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:116
+#: i2p2www/pages/site/docs/transport/index.html:124
 msgid ""
 "The number of current connections compared to various connection limit "
 "thresholds"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:117
+#: i2p2www/pages/site/docs/transport/index.html:125
 msgid "Whether recent connection attempts to the peer have failed"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:118
+#: i2p2www/pages/site/docs/transport/index.html:126
 msgid ""
 "The size of the message, as different transports have different size "
 "limits"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:119
+#: i2p2www/pages/site/docs/transport/index.html:127
 msgid ""
 "Whether the peer can accept incoming connections for that transport, as "
 "advertised in its RouterInfo"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:120
+#: i2p2www/pages/site/docs/transport/index.html:128
 msgid "Whether the connection would be indirect (requiring introducers) or direct"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:121
+#: i2p2www/pages/site/docs/transport/index.html:129
 msgid "The peer's transport preference, as advertised in its RouterInfo"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:124
+#: i2p2www/pages/site/docs/transport/index.html:132
 msgid ""
 "In general, the bid values are selected so that two routers are only "
 "connected by a single transport\n"
 "at any one time. However, this is not a requirement."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:131
+#: i2p2www/pages/site/docs/transport/index.html:139
 msgid "New Transports and Future Work"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:133
+#: i2p2www/pages/site/docs/transport/index.html:141
 msgid "Additional transports may be developed, including:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:138
+#: i2p2www/pages/site/docs/transport/index.html:146
 msgid "A TLS/SSH look-alike transport"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:139
+#: i2p2www/pages/site/docs/transport/index.html:147
 msgid ""
 "An \"indirect\" transport for routers that are not reachable by all other"
 " routers (one form of \"restricted routes\")"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:142
-#, python-format
-msgid ""
-"IPv6: The existing transports must be enhanced to support multiple "
-"addresses within a single transport,\n"
-"including IPV6 addresses. Currently, a transport may only advertise a "
-"single IPV4 address.\n"
-"See this thread for discussion."
-msgstr ""
-
-#: i2p2www/pages/site/docs/transport/index.html:148
+#: i2p2www/pages/site/docs/transport/index.html:150
 msgid ""
 "Work continues on adjusting default connection limits for each transport."
 "\n"
@@ -21348,7 +14878,7 @@ msgid ""
 "routers that are behind restrictive state firewalls (restricted routes)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:155
+#: i2p2www/pages/site/docs/transport/index.html:157
 msgid ""
 "The current connection limits are higher for SSU than for NTCP, based on "
 "the assumption that\n"
@@ -21359,7 +14889,7 @@ msgid ""
 "that assumption is difficult to verify."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:162
+#: i2p2www/pages/site/docs/transport/index.html:164
 #, python-format
 msgid ""
 "Analyze Breaking and Improving Protocol "
@@ -21379,10 +14909,11 @@ msgid ""
 "The other is SSU.\n"
 "NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n"
 "Java NIO (new I/O) does not suffer from the 1 thread per connection "
-"issues of the old TCP transport."
+"issues of the old TCP transport.\n"
+"NTCP-over-IPv6 is supported as of version 0.9.8."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:15
+#: i2p2www/pages/site/docs/transport/ntcp.html:16
 msgid ""
 "By default, NTCP uses the IP/Port\n"
 "auto-detected by SSU. When enabled on config.jsp,\n"
@@ -21391,22 +14922,22 @@ msgid ""
 "Now you can enable inbound TCP without a static IP or dyndns service."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:23
+#: i2p2www/pages/site/docs/transport/ntcp.html:24
 msgid ""
 "The NTCP code within I2P is relatively lightweight (1/4 the size of the "
 "SSU code)\n"
 "because it uses the underlying Java TCP transport for reliable delivery."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:29
+#: i2p2www/pages/site/docs/transport/ntcp.html:30
 msgid "NTCP Protocol Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:31
+#: i2p2www/pages/site/docs/transport/ntcp.html:32
 msgid "Standard Message Format"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:32
+#: i2p2www/pages/site/docs/transport/ntcp.html:33
 msgid ""
 "After establishment,\n"
 "the NTCP transport sends individual I2NP messages, with a simple "
@@ -21414,7 +14945,7 @@ msgid ""
 "The unencrypted message is encoded as follows:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:42
+#: i2p2www/pages/site/docs/transport/ntcp.html:43
 msgid ""
 "The data is then AES/256/CBC encrypted. The session key for the "
 "encryption\n"
@@ -21426,7 +14957,7 @@ msgid ""
 "encrypted message."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:50
+#: i2p2www/pages/site/docs/transport/ntcp.html:51
 msgid ""
 "0-15 bytes of padding are required to bring the total message length\n"
 "(including the six size and checksum bytes) to a multiple of 16.\n"
@@ -21435,39 +14966,39 @@ msgid ""
 "The minimum data size is 1."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:58
+#: i2p2www/pages/site/docs/transport/ntcp.html:59
 msgid "Time Sync Message Format"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:59
+#: i2p2www/pages/site/docs/transport/ntcp.html:60
 msgid ""
 "One special case is a metadata message where the sizeof(data) is 0.  In\n"
 "that case, the unencrypted message is encoded as:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:70
+#: i2p2www/pages/site/docs/transport/ntcp.html:71
 msgid ""
 "Total length: 16 bytes. The time sync message is sent at approximately 15"
 " minute intervals.\n"
 "The message is encrypted just as standard messages are."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:76
+#: i2p2www/pages/site/docs/transport/ntcp.html:77
 msgid "Checksums"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:77
+#: i2p2www/pages/site/docs/transport/ntcp.html:78
 #, python-format
 msgid ""
 "The standard and time sync messages use the Adler-32 checksum\n"
 "as defined in the ZLIB Specification."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:83
+#: i2p2www/pages/site/docs/transport/ntcp.html:84
 msgid "Establishment Sequence"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:84
+#: i2p2www/pages/site/docs/transport/ntcp.html:85
 msgid ""
 "In the establish state, there is a 4-phase message sequence to exchange "
 "DH keys and signatures.\n"
@@ -21476,31 +15007,31 @@ msgid ""
 "connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:98
+#: i2p2www/pages/site/docs/transport/ntcp.html:99
 msgid "Legend:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:99
+#: i2p2www/pages/site/docs/transport/ntcp.html:100
 msgid "256 byte DH public keys"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:103
+#: i2p2www/pages/site/docs/transport/ntcp.html:104
 msgid "timestamps (4 bytes, seconds since epoch)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:104
+#: i2p2www/pages/site/docs/transport/ntcp.html:105
 msgid "32 byte Session key"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:105
+#: i2p2www/pages/site/docs/transport/ntcp.html:106
 msgid "2 byte size of Alice identity to follow"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:108
+#: i2p2www/pages/site/docs/transport/ntcp.html:109
 msgid "DH Key Exchange"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:109
+#: i2p2www/pages/site/docs/transport/ntcp.html:110
 #, python-format
 msgid ""
 "The initial 2048-bit DH key exchange\n"
@@ -21508,7 +15039,7 @@ msgid ""
 "ElGamal encryption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:115
+#: i2p2www/pages/site/docs/transport/ntcp.html:116
 msgid ""
 "The DH key exchange consists of a number of steps, displayed below.\n"
 "The mapping between these steps and the messages sent between I2P "
@@ -21516,51 +15047,54 @@ msgid ""
 "is marked in bold."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:121
-msgid ""
-"Alice generates a secret 226-bit integer x. She then calculates X ="
-" g^x mod p."
-msgstr ""
-
 #: i2p2www/pages/site/docs/transport/ntcp.html:122
-msgid "Alice sends X to Bob (Message 1)."
+msgid ""
+"Alice generates a secret integer x. She then calculates X = g^x mod"
+" p."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:123
-msgid ""
-"Bob generates a secret 226-bit integer y. He then calculates Y = "
-"g^y mod p."
+msgid "Alice sends X to Bob (Message 1)."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:124
-msgid "Bob sends Y to Alice.(Message 2)"
+msgid ""
+"Bob generates a secret integer y. He then calculates Y = g^y mod "
+"p."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:125
-msgid "Alice can now compute sessionKey = Y^x mod p."
+msgid "Bob sends Y to Alice.(Message 2)"
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:126
-msgid "Bob can now compute sessionKey = X^y mod p."
+msgid "Alice can now compute sessionKey = Y^x mod p."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:127
+msgid "Bob can now compute sessionKey = X^y mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:128
 msgid ""
 "Both Alice and Bob now have a shared key sessionKey = g^(x*y) mod "
 "p."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:129
+#: i2p2www/pages/site/docs/transport/ntcp.html:130
+#, python-format
 msgid ""
 "The sessionKey is then used to exchange identities in Message 3 "
-"and Message 4."
+"and Message 4.\n"
+"The exponent (x and y) length for the DH exchange is documented on the\n"
+"cryptography page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:133
+#: i2p2www/pages/site/docs/transport/ntcp.html:136
 msgid "Message 1 (Session Request)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:134
+#: i2p2www/pages/site/docs/transport/ntcp.html:137
 #, python-format
 msgid ""
 "This is the DH request. Alice already has Bob's\n"
@@ -21573,79 +15107,79 @@ msgid ""
 "Alice sends Bob:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:147
-#: i2p2www/pages/site/docs/transport/ntcp.html:190
-#: i2p2www/pages/site/docs/transport/ntcp.html:270
-#: i2p2www/pages/site/docs/transport/ntcp.html:353
+#: i2p2www/pages/site/docs/transport/ntcp.html:150
+#: i2p2www/pages/site/docs/transport/ntcp.html:193
+#: i2p2www/pages/site/docs/transport/ntcp.html:273
+#: i2p2www/pages/site/docs/transport/ntcp.html:356
 msgid "Size:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:149
+#: i2p2www/pages/site/docs/transport/ntcp.html:152
 msgid "Contents:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:167
+#: i2p2www/pages/site/docs/transport/ntcp.html:170
 msgid "256 byte X from Diffie Hellman"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:169
+#: i2p2www/pages/site/docs/transport/ntcp.html:172
 #, python-format
 msgid ""
 "SHA256 Hash(X) xored with SHA256 Hash(Bob's Router Identity)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:176
-#: i2p2www/pages/site/docs/transport/ntcp.html:257
-#: i2p2www/pages/site/docs/transport/ntcp.html:334
+#: i2p2www/pages/site/docs/transport/ntcp.html:179
+#: i2p2www/pages/site/docs/transport/ntcp.html:260
+#: i2p2www/pages/site/docs/transport/ntcp.html:337
 msgid "Notes:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:177
+#: i2p2www/pages/site/docs/transport/ntcp.html:180
 msgid ""
 "Bob verifies HXxorHI using his own router hash. If it does not verify,\n"
 "Alice has contacted the wrong router, and Bob drops the connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:183
+#: i2p2www/pages/site/docs/transport/ntcp.html:186
 msgid "Message 2 (Session Created)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:184
+#: i2p2www/pages/site/docs/transport/ntcp.html:187
 msgid "This is the DH reply. Bob sends Alice:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:192
-#: i2p2www/pages/site/docs/transport/ntcp.html:272
-#: i2p2www/pages/site/docs/transport/ntcp.html:355
+#: i2p2www/pages/site/docs/transport/ntcp.html:195
+#: i2p2www/pages/site/docs/transport/ntcp.html:275
+#: i2p2www/pages/site/docs/transport/ntcp.html:358
 msgid "Unencrypted Contents:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:214
-#: i2p2www/pages/site/docs/transport/ntcp.html:248
+#: i2p2www/pages/site/docs/transport/ntcp.html:217
+#: i2p2www/pages/site/docs/transport/ntcp.html:251
 msgid "256 byte Y from Diffie Hellman"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:216
+#: i2p2www/pages/site/docs/transport/ntcp.html:219
 msgid "SHA256 Hash(X concatenated with Y)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:219
-#: i2p2www/pages/site/docs/transport/ntcp.html:304
+#: i2p2www/pages/site/docs/transport/ntcp.html:222
+#: i2p2www/pages/site/docs/transport/ntcp.html:307
 msgid "4 byte timestamp (seconds since the epoch)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:221
+#: i2p2www/pages/site/docs/transport/ntcp.html:224
 msgid "12 bytes random data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:226
-#: i2p2www/pages/site/docs/transport/ntcp.html:316
-#: i2p2www/pages/site/docs/transport/ntcp.html:383
+#: i2p2www/pages/site/docs/transport/ntcp.html:229
+#: i2p2www/pages/site/docs/transport/ntcp.html:319
+#: i2p2www/pages/site/docs/transport/ntcp.html:386
 msgid "Encrypted Contents:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:250
+#: i2p2www/pages/site/docs/transport/ntcp.html:253
 #, python-format
 msgid ""
 "48 bytes AES encrypted using the DH "
@@ -21653,38 +15187,38 @@ msgid ""
 "                  the last 16 bytes of Y as the IV"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:258
+#: i2p2www/pages/site/docs/transport/ntcp.html:261
 msgid ""
 "Alice may drop the connection if the clock skew with Bob is too high as "
 "calculated using tsB."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:263
+#: i2p2www/pages/site/docs/transport/ntcp.html:266
 msgid "Message 3 (Session Confirm A)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:264
+#: i2p2www/pages/site/docs/transport/ntcp.html:267
 msgid ""
 "This contains Alice's router identity, and a DSA signature of the "
 "critical data. Alice sends Bob:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:298
+#: i2p2www/pages/site/docs/transport/ntcp.html:301
 msgid "2 byte size of Alice's router identity to follow (should always be 387)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:300
+#: i2p2www/pages/site/docs/transport/ntcp.html:303
 #, python-format
 msgid ""
 "Alice's 387 byte Router Identity"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:306
+#: i2p2www/pages/site/docs/transport/ntcp.html:309
 msgid "15 bytes random data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:308
+#: i2p2www/pages/site/docs/transport/ntcp.html:311
 #, python-format
 msgid ""
 "the 40 byte DSA "
@@ -21700,7 +15234,7 @@ msgid ""
 "href=\"%(commonstructures)s#struct_RouterIdentity\">Router Identity"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:326
+#: i2p2www/pages/site/docs/transport/ntcp.html:329
 #, python-format
 msgid ""
 "448 bytes AES encrypted using the DH"
@@ -21709,25 +15243,25 @@ msgid ""
 "of message #1) as the IV"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:336
+#: i2p2www/pages/site/docs/transport/ntcp.html:339
 msgid "Bob verifies the signature, and on failure, drops the connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:339
+#: i2p2www/pages/site/docs/transport/ntcp.html:342
 msgid ""
 "Bob may drop the connection if the clock skew with Alice is too high as "
 "calculated using tsA."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:346
+#: i2p2www/pages/site/docs/transport/ntcp.html:349
 msgid "Message 4 (Session Confirm B)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:347
+#: i2p2www/pages/site/docs/transport/ntcp.html:350
 msgid "This is a DSA signature of the critical data. Bob sends Alice:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:372
+#: i2p2www/pages/site/docs/transport/ntcp.html:375
 #, python-format
 msgid ""
 "the 40 byte DSA "
@@ -21743,11 +15277,11 @@ msgid ""
 "href=\"%(commonstructures)s#struct_RouterIdentity\">Router Identity"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:378
+#: i2p2www/pages/site/docs/transport/ntcp.html:381
 msgid "8 bytes random data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:393
+#: i2p2www/pages/site/docs/transport/ntcp.html:396
 #, python-format
 msgid ""
 "48 bytes AES encrypted using the DH "
@@ -21756,15 +15290,15 @@ msgid ""
 "#2 as the IV"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:401
+#: i2p2www/pages/site/docs/transport/ntcp.html:404
 msgid "Alice verifies the signature, and on failure, drops the connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:408
+#: i2p2www/pages/site/docs/transport/ntcp.html:411
 msgid "After Establishment"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:409
+#: i2p2www/pages/site/docs/transport/ntcp.html:412
 msgid ""
 "The connection is established, and standard or time sync messages may be "
 "exchanged.\n"
@@ -21776,11 +15310,11 @@ msgid ""
 " the next IV."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:418
+#: i2p2www/pages/site/docs/transport/ntcp.html:421
 msgid "Check Connection Message"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:419
+#: i2p2www/pages/site/docs/transport/ntcp.html:422
 msgid ""
 "Alternately, when Bob receives a connection, it could be a\n"
 "check connection (perhaps prompted by Bob asking for someone\n"
@@ -21790,54 +15324,54 @@ msgid ""
 "A check info connection will receive 256 bytes containing:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:428
+#: i2p2www/pages/site/docs/transport/ntcp.html:431
 msgid "32 bytes of uninterpreted, ignored data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:429
+#: i2p2www/pages/site/docs/transport/ntcp.html:432
 msgid "1 byte size"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:430
+#: i2p2www/pages/site/docs/transport/ntcp.html:433
 msgid ""
 "that many bytes making up the local router's IP address (as reached by "
 "the remote side)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:431
+#: i2p2www/pages/site/docs/transport/ntcp.html:434
 msgid "2 byte port number that the local router was reached on"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:432
+#: i2p2www/pages/site/docs/transport/ntcp.html:435
 msgid ""
 "4 byte i2p network time as known by the remote side (seconds since the "
 "epoch)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:433
+#: i2p2www/pages/site/docs/transport/ntcp.html:436
 msgid "uninterpreted padding data, up to byte 223"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:434
+#: i2p2www/pages/site/docs/transport/ntcp.html:437
 msgid ""
 "xor of the local router's identity hash and the SHA256 of bytes 32 "
 "through bytes 223"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:438
+#: i2p2www/pages/site/docs/transport/ntcp.html:441
 msgid "Discussion"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:439
+#: i2p2www/pages/site/docs/transport/ntcp.html:442
 #, python-format
 msgid "Now on the NTCP Discussion Page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:445
+#: i2p2www/pages/site/docs/transport/ntcp.html:448
 msgid "The maximum message size should be increased to approximately 32 KB."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:449
+#: i2p2www/pages/site/docs/transport/ntcp.html:452
 msgid ""
 "A set of fixed packet sizes may be appropriate to further hide the data \n"
 "fragmentation to external adversaries, but the tunnel, garlic, and end to"
@@ -21848,19 +15382,19 @@ msgid ""
 "to create a limited number of message sizes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:457
+#: i2p2www/pages/site/docs/transport/ntcp.html:460
 msgid ""
 "Memory utilization (including that of the kernel) for NTCP should be "
 "compared to that for SSU."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:461
+#: i2p2www/pages/site/docs/transport/ntcp.html:464
 msgid ""
 "Can the establishment messages be randomly padded somehow, to frustrate\n"
 "identification of I2P traffic based on initial packet sizes?"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:466
+#: i2p2www/pages/site/docs/transport/ntcp.html:469
 msgid "Review and possibly disable 'check connection'"
 msgstr ""
 
@@ -21887,14 +15421,15 @@ msgid ""
 "SSU is the newer of the two transports,\n"
 "introduced in I2P release 0.6.\n"
 "In a standard I2P installation, the router uses both NTCP and SSU for "
-"outbound connections."
+"outbound connections.\n"
+"SSU-over-IPv6 is supported as of version 0.9.8."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:21
+#: i2p2www/pages/site/docs/transport/ssu.html:22
 msgid "SSU Services"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:23
+#: i2p2www/pages/site/docs/transport/ssu.html:24
 msgid ""
 "Like the NTCP transport, SSU provides reliable, encrypted, connection-"
 "oriented, point-to-point data transport.\n"
@@ -21902,33 +15437,33 @@ msgid ""
 "including:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:29
+#: i2p2www/pages/site/docs/transport/ssu.html:30
 msgid ""
 "Cooperative NAT/Firewall traversal using introducers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:30
+#: i2p2www/pages/site/docs/transport/ssu.html:31
 msgid ""
 "Local IP detection by inspection of incoming packets and peer testing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:31
+#: i2p2www/pages/site/docs/transport/ssu.html:32
 msgid ""
 "Communication of firewall status and local IP, and changes to either to "
 "NTCP"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:36
+#: i2p2www/pages/site/docs/transport/ssu.html:37
 msgid "Protocol Details"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:38
+#: i2p2www/pages/site/docs/transport/ssu.html:39
 msgid "Congestion control"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:40
+#: i2p2www/pages/site/docs/transport/ssu.html:41
 msgid ""
 "SSU's need for only semireliable delivery, TCP-friendly operation,\n"
 "and the capacity for high throughput allows a great deal of latitude in\n"
@@ -21936,7 +15471,7 @@ msgid ""
 "meant to be both efficient in bandwidth as well as simple to implement."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:47
+#: i2p2www/pages/site/docs/transport/ssu.html:48
 msgid ""
 "Packets are scheduled according to the router's policy, taking care\n"
 "not to exceed the router's outbound capacity or to exceed the measured \n"
@@ -21951,7 +15486,7 @@ msgid ""
 "other messages."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:58
+#: i2p2www/pages/site/docs/transport/ssu.html:59
 msgid ""
 "The congestion detection techniques vary from TCP as well, since each \n"
 "message has its own unique and nonsequential identifier, and each message"
@@ -21967,7 +15502,7 @@ msgid ""
 "retransmitted with any new updates."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:70
+#: i2p2www/pages/site/docs/transport/ssu.html:71
 msgid ""
 "The current implementation does not pad the packets to\n"
 "any particular size, but instead just places a single message fragment "
@@ -21975,7 +15510,7 @@ msgid ""
 "a packet and sends it off (careful not to exceed the MTU)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:77
+#: i2p2www/pages/site/docs/transport/ssu.html:78
 msgid ""
 "As of router version 0.8.12,\n"
 "two MTU values are used for IPv4: 620 and 1484.\n"
@@ -21983,21 +15518,21 @@ msgid ""
 "retransmitted."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:83
+#: i2p2www/pages/site/docs/transport/ssu.html:84
 msgid ""
-"For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
+"For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
 "the payload portion after the 28-byte IP/UDP header is a multiple of\n"
 "16 bytes, for encryption purposes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:89
+#: i2p2www/pages/site/docs/transport/ssu.html:90
 msgid ""
 "For the small MTU value, it is desirable to pack a 2646-byte\n"
 "Variable Tunnel Build Message efficiently into multiple packets;\n"
 "with a 620-byte MTU, it fits into 5 packets with nicely."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:95
+#: i2p2www/pages/site/docs/transport/ssu.html:96
 msgid ""
 "Based on measurements, 1492 fits nearly all reasonably small I2NP "
 "messages\n"
@@ -22006,13 +15541,13 @@ msgid ""
 "into a live network MTU anyway)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:101
+#: i2p2www/pages/site/docs/transport/ssu.html:102
 msgid ""
 "The MTU values were 608 and 1492 for releases 0.8.9 - 0.8.11.\n"
 "The large MTU was 1350 prior to release 0.8.9."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:106
+#: i2p2www/pages/site/docs/transport/ssu.html:107
 msgid ""
 "The maximum receive packet size\n"
 "is 1571 bytes as of release 0.8.12.\n"
@@ -22020,7 +15555,7 @@ msgid ""
 "Prior to release 0.8.9 it was 2048 bytes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:113
+#: i2p2www/pages/site/docs/transport/ssu.html:114
 msgid ""
 "As of release 0.9.2, if a router's network interface MTU is less than "
 "1484,\n"
@@ -22028,17 +15563,18 @@ msgid ""
 "honor that when a connection is established."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:119
+#: i2p2www/pages/site/docs/transport/ssu.html:120
 msgid ""
 "For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes,\n"
-"so we use an MTU where (MTN % 16 == 0), which is true for 1280."
+"so we use an MTU where (MTN % 16 == 0), which is true for 1280.\n"
+"The maximum IPv6 MTU is 1472."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:124
+#: i2p2www/pages/site/docs/transport/ssu.html:126
 msgid "Message Size Limits"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:125
+#: i2p2www/pages/site/docs/transport/ssu.html:127
 msgid ""
 "While the maximum message size is nominally 32KB, the practical\n"
 "limit differs. The protocol limits the number of fragments to 7 bits, or "
@@ -22053,11 +15589,11 @@ msgid ""
 "For connections using the larger MTU, larger messages are possible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:136
+#: i2p2www/pages/site/docs/transport/ssu.html:138
 msgid "Keys"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:138
+#: i2p2www/pages/site/docs/transport/ssu.html:140
 msgid ""
 "All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n"
 "The MAC and session keys are negotiated as part of the DH exchange, used\n"
@@ -22065,7 +15601,7 @@ msgid ""
 "the publicly knowable introKey is used for the MAC and encryption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:145
+#: i2p2www/pages/site/docs/transport/ssu.html:147
 msgid ""
 "When using the introKey, both the initial message and any subsequent\n"
 "reply use the introKey of the responder (Bob) - the responder does \n"
@@ -22075,7 +15611,7 @@ msgid ""
 "Bob."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:154
+#: i2p2www/pages/site/docs/transport/ssu.html:156
 msgid ""
 "Upon receiving a message, the receiver checks the \"from\" IP address and"
 " port\n"
@@ -22088,7 +15624,7 @@ msgid ""
 "it may be dropped anyway."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:165
+#: i2p2www/pages/site/docs/transport/ssu.html:167
 msgid ""
 "If Alice and Bob have an established session, but Alice loses the \n"
 "keys for some reason and she wants to contact Bob, she may at any \n"
@@ -22100,7 +15636,7 @@ msgid ""
 "new one."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:176
+#: i2p2www/pages/site/docs/transport/ssu.html:178
 #, python-format
 msgid ""
 "For the DH key agreement,\n"
@@ -22108,18 +15644,18 @@ msgid ""
 "MODP group (#14) is used:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:186
+#: i2p2www/pages/site/docs/transport/ssu.html:188
 #, python-format
 msgid ""
 "These are the same p and g used for I2P's\n"
 "ElGamal encryption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:191
+#: i2p2www/pages/site/docs/transport/ssu.html:193
 msgid "Replay prevention"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:193
+#: i2p2www/pages/site/docs/transport/ssu.html:195
 msgid ""
 "Replay prevention at the SSU layer occurs by rejecting packets \n"
 "with exceedingly old timestamps or those which reuse an IV.  To\n"
@@ -22127,7 +15663,7 @@ msgid ""
 "\"decay\" periodically so that only recently added IVs are detected."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:200
+#: i2p2www/pages/site/docs/transport/ssu.html:202
 msgid ""
 "The messageIds used in DataMessages are defined at layers above\n"
 "the SSU transport and are passed through transparently.  These IDs\n"
@@ -22136,11 +15672,11 @@ msgid ""
 "replay prevention - higher layers should take that into account."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:208
+#: i2p2www/pages/site/docs/transport/ssu.html:210
 msgid "Addressing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:210
+#: i2p2www/pages/site/docs/transport/ssu.html:212
 msgid ""
 "To contact an SSU peer, one of two sets of information is necessary:\n"
 "a direct address, for when the peer is publicly reachable, or an\n"
@@ -22148,40 +15684,42 @@ msgid ""
 "There is no restriction on the number of addresses a peer may have."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:222
+#: i2p2www/pages/site/docs/transport/ssu.html:224
 msgid ""
 "Each of the addresses may also expose a series of options - special\n"
 "capabilities of that particular peer.  For a list of available\n"
 "capabilities, see below."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:228
+#: i2p2www/pages/site/docs/transport/ssu.html:230
 #, python-format
 msgid ""
 "The addresses, options, and capabilities are published in the network database."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:233
+#: i2p2www/pages/site/docs/transport/ssu.html:235
 msgid "Direct Session Establishment"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:234
+#: i2p2www/pages/site/docs/transport/ssu.html:236
 msgid ""
 "Direct session establishment is used when no third party is required for "
 "NAT traversal.\n"
 "The message sequence is as follows:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:239
+#: i2p2www/pages/site/docs/transport/ssu.html:241
 msgid "Connection establishment (direct)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:240
-msgid "Alice connects directly to Bob."
+#: i2p2www/pages/site/docs/transport/ssu.html:242
+msgid ""
+"Alice connects directly to Bob.\n"
+"IPv6 is supported as of version 0.9.8."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:254
+#: i2p2www/pages/site/docs/transport/ssu.html:257
 #, python-format
 msgid ""
 "After the SessionConfirmed message is received, Bob sends a small\n"
@@ -22194,7 +15732,7 @@ msgid ""
 "(i.e. 0x0000000000000002)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:263
+#: i2p2www/pages/site/docs/transport/ssu.html:266
 #, python-format
 msgid ""
 "After the status message is sent, the peers exchange\n"
@@ -22203,7 +15741,7 @@ msgid ""
 "RouterInfos."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:271
+#: i2p2www/pages/site/docs/transport/ssu.html:274
 msgid ""
 "It does not appear that the type of the status message or its contents "
 "matters.\n"
@@ -22212,7 +15750,7 @@ msgid ""
 "the status message can be eliminated."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:280
+#: i2p2www/pages/site/docs/transport/ssu.html:283
 msgid ""
 "Introduction keys are delivered through an external channel \n"
 "(the network database, where they are identical to the router Hash for "
@@ -22228,7 +15766,7 @@ msgid ""
 "not necessary to any intermediary relay peer)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:294
+#: i2p2www/pages/site/docs/transport/ssu.html:297
 msgid ""
 "Indirect session establishment by means of a third party introduction\n"
 "is necessary for efficient NAT traversal.  Charlie, a router behind a\n"
@@ -22256,25 +15794,25 @@ msgid ""
 "full direction session establishment with the specified IP and port."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:321
+#: i2p2www/pages/site/docs/transport/ssu.html:324
 msgid "Connection establishment (indirect using an introducer)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:323
+#: i2p2www/pages/site/docs/transport/ssu.html:326
 msgid "Alice first connects to introducer Bob, who relays the request to Charlie."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:341
+#: i2p2www/pages/site/docs/transport/ssu.html:344
 msgid ""
 "After the hole punch, the session is established between Alice and "
 "Charlie as in a direct establishment."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:352
+#: i2p2www/pages/site/docs/transport/ssu.html:356
 msgid "Peer testing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:354
+#: i2p2www/pages/site/docs/transport/ssu.html:358
 msgid ""
 "The automation of collaborative reachability testing for peers is\n"
 "enabled by a sequence of PeerTest messages.  With its proper \n"
@@ -22283,7 +15821,7 @@ msgid ""
 "quite simple:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:373
+#: i2p2www/pages/site/docs/transport/ssu.html:377
 msgid ""
 "Each of the PeerTest messages carry a nonce identifying the\n"
 "test series itself, as initialized by Alice.  If Alice doesn't \n"
@@ -22293,7 +15831,7 @@ msgid ""
 "that may be reached are as follows:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:383
+#: i2p2www/pages/site/docs/transport/ssu.html:387
 msgid ""
 "If she doesn't receive a response from Bob, she will retransmit\n"
 "up to a certain number of times, but if no response ever arrives,\n"
@@ -22303,7 +15841,7 @@ msgid ""
 "Charlie to reply."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:392
+#: i2p2www/pages/site/docs/transport/ssu.html:396
 msgid ""
 "If Alice doesn't receive a PeerTest message with the \n"
 "expected nonce from a third party (Charlie), she will retransmit\n"
@@ -22315,7 +15853,7 @@ msgid ""
 "IP and port that Bob offered up should be forwarded)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:403
+#: i2p2www/pages/site/docs/transport/ssu.html:407
 msgid ""
 "If Alice receives Bob's PeerTest message and both of Charlie's\n"
 "PeerTest messages but the enclosed IP and port numbers in Bob's \n"
@@ -22326,7 +15864,7 @@ msgid ""
 "remote connectivity, ignoring further port discovery."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:413
+#: i2p2www/pages/site/docs/transport/ssu.html:417
 msgid ""
 "If Alice receives Charlie's first message but not his second,\n"
 "she will retransmit her PeerTest message to Charlie up to a \n"
@@ -22334,7 +15872,7 @@ msgid ""
 "that Charlie is either confused or no longer online."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:421
+#: i2p2www/pages/site/docs/transport/ssu.html:425
 msgid ""
 "Alice should choose Bob arbitrarily from known peers who seem\n"
 "to be capable of participating in peer tests.  Bob in turn should\n"
@@ -22345,7 +15883,7 @@ msgid ""
 "to designate a new peer as Bob and try again with a different nonce."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:431
+#: i2p2www/pages/site/docs/transport/ssu.html:435
 msgid ""
 "Alice's introduction key is included in all of the PeerTest \n"
 "messages so that she doesn't need to already have an established\n"
@@ -22354,11 +15892,11 @@ msgid ""
 "with either Bob or Charlie, but it is not required."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:449
+#: i2p2www/pages/site/docs/transport/ssu.html:453
 msgid "Transmission window, ACKs and Retransmissions"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:450
+#: i2p2www/pages/site/docs/transport/ssu.html:454
 #, python-format
 msgid ""
 "The DATA message may contain ACKs of full messages and\n"
@@ -22368,7 +15906,7 @@ msgid ""
 "for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:458
+#: i2p2www/pages/site/docs/transport/ssu.html:462
 #, python-format
 msgid ""
 "The details of windowing, ACK, and retransmission strategies are not "
@@ -22383,11 +15921,11 @@ msgid ""
 "See the code for initial, min and max parameters."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:470
+#: i2p2www/pages/site/docs/transport/ssu.html:474
 msgid "Security"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:471
+#: i2p2www/pages/site/docs/transport/ssu.html:475
 msgid ""
 "UDP source addresses may, of course, be spoofed.\n"
 "Additionally, the IPs and ports contained inside specific\n"
@@ -22396,31 +15934,31 @@ msgid ""
 "Also, certain actions and responses may need to be rate-limited."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:479
+#: i2p2www/pages/site/docs/transport/ssu.html:483
 msgid ""
 "The details of validation are not specified\n"
 "here. Implementers should add defenses where appropriate."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:485
+#: i2p2www/pages/site/docs/transport/ssu.html:489
 msgid "Peer capabilities"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:489
+#: i2p2www/pages/site/docs/transport/ssu.html:493
 msgid ""
 "If the peer address contains the 'B' capability, that means \n"
 "they are willing and able to participate in peer tests as\n"
 "a 'Bob' or 'Charlie'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:495
+#: i2p2www/pages/site/docs/transport/ssu.html:499
 msgid ""
 "If the peer address contains the 'C' capability, that means\n"
 "they are willing and able to serve as an introducer - serving\n"
 "as a Bob for an otherwise unreachable Alice."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:504
+#: i2p2www/pages/site/docs/transport/ssu.html:508
 msgid ""
 "Analysis of current SSU performance, including assessment of window size "
 "adjustment\n"
@@ -22429,14 +15967,14 @@ msgid ""
 "performance, is a topic for future work."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:510
+#: i2p2www/pages/site/docs/transport/ssu.html:514
 msgid ""
 "The current implementation repeatedly sends acknowledgments for the same "
 "packets,\n"
 "which unnecessarily increases overhead."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:515
+#: i2p2www/pages/site/docs/transport/ssu.html:519
 msgid ""
 "The default small MTU value of 620 should be analyzed and possibly "
 "increased.\n"
@@ -22445,15 +15983,15 @@ msgid ""
 "Probably not."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:521
+#: i2p2www/pages/site/docs/transport/ssu.html:525
 msgid "The protocol should be extended to exchange MTUs during the setup."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:525
+#: i2p2www/pages/site/docs/transport/ssu.html:529
 msgid "Rekeying is currently unimplemented and may never be."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:529
+#: i2p2www/pages/site/docs/transport/ssu.html:533
 msgid ""
 "The potential use of the 'challenge' fields in RelayIntro and "
 "RelayResponse,\n"
@@ -22461,7 +15999,7 @@ msgid ""
 "undocumented."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:534
+#: i2p2www/pages/site/docs/transport/ssu.html:538
 msgid ""
 "Instead of a single fragment per packet, a more efficient\n"
 "strategy may be to bundle multiple message fragments into the same "
@@ -22469,7 +16007,7 @@ msgid ""
 "so long as it doesn't exceed the MTU."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:540
+#: i2p2www/pages/site/docs/transport/ssu.html:544
 msgid ""
 "A set of fixed packet sizes may be appropriate to further hide the data \n"
 "fragmentation to external adversaries, but the tunnel, garlic, and end to"
@@ -22477,34 +16015,34 @@ msgid ""
 "end padding should be sufficient for most needs until then."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:546
+#: i2p2www/pages/site/docs/transport/ssu.html:550
 msgid ""
 "Why are introduction keys the same as the router hash, should it be "
 "changed, would there be any benefit?"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:550
+#: i2p2www/pages/site/docs/transport/ssu.html:554
 msgid "Capacities appear to be unused."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:554
+#: i2p2www/pages/site/docs/transport/ssu.html:558
 msgid ""
 "Signed-on times in SessionCreated and SessionConfirmed appear to be "
 "unused or unverified."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:559
+#: i2p2www/pages/site/docs/transport/ssu.html:563
 msgid "Implementation Diagram"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:560
+#: i2p2www/pages/site/docs/transport/ssu.html:564
 msgid ""
 "This diagram\n"
 "should accurately reflect the current implementation, however there may "
 "be small differences."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:568
+#: i2p2www/pages/site/docs/transport/ssu.html:572
 msgid "Now on the SSU specification page"
 msgstr ""
 
@@ -23300,6 +16838,10 @@ msgstr ""
 msgid "Tunnel design discussion"
 msgstr ""
 
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:21
+msgid "Peer selection"
+msgstr "Sélection de pair"
+
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:23
 msgid "Meeting 125 (~13:12-13:30)"
 msgstr ""
@@ -23475,5202 +17017,3 @@ msgid ""
 "conclusion is not supported by the paper."
 msgstr ""
 
-#: i2p2www/pages/site/get-involved/donate.html:4
-msgid ""
-"Thank you for your interest in contributing to I2P!\n"
-"The details of how you\n"
-"can make your contribution are provided below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:13
-#, python-format
-msgid "You can donate direct via PayPal to the account \"%(account)s\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:19
-msgid "One time donation:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:33
-msgid "Donate 10 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:41
-#: i2p2www/pages/site/get-involved/donate.html:53
-#: i2p2www/pages/site/get-involved/donate.html:65
-#: i2p2www/pages/site/get-involved/donate.html:77
-msgid "I2P donation "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:47
-msgid "Donate 20 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:59
-msgid "Donate 30 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:71
-msgid "Donate 50 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:86
-msgid "Flattr this"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:90
-#, python-format
-msgid ""
-"As of December 2010, eche|on has been running a Bitcoin account for the I2P project. \n"
-"If you'd like to donate using Bitcoin, just transfer your desired amount "
-"of coins to the account \n"
-"%(account)s and leave eche|on a note if you'd like your donation "
-"to be mentioned on the I2P webpage."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:95
-msgid ""
-"If you want to keep more or less anonymous, the option to send money via "
-"mail is also available. But it is less secure\n"
-"as the envelope can be lost on the way to us."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:99
-#, python-format
-msgid ""
-"If you'd like to donate via  snail mail, send an email to %(email)s\n"
-" and you'll receive an email with instructions detailing how to proceed."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:104
-#, python-format
-msgid ""
-"In the meantime, feel free to take a look at the generous donations that "
-"have been\n"
-"given in support of the I2P Project at the hall of fame."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:2
-msgid "Get Involved!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:4
-msgid "We need your help!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:5
-msgid ""
-"To get involved, please feel free to join us on the #i2p IRC channel (on\n"
-"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or "
-"irc.postman.i2p)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:9
-#, python-format
-msgid ""
-"If you're interested in joining our team, please"
-" get in\n"
-"touch as we're always looking for eager contributors!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:13
-msgid ""
-"We need help in many areas, and you don't need to know Java to "
-"contribute!\n"
-"Here's a list to help you get started!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:18
-msgid "Spread the Word!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:19
-msgid ""
-"Tell people about I2P on forums, blogs, and comments to articles.\n"
-"Fix up the Wikipedia article about I2P in your language.\n"
-"Tell your friends."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:24
-msgid "Testing"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:25
-#, python-format
-msgid ""
-"Run the latest builds from monotone\n"
-"and report results on #i2p or as bugs on Trac."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:30
-msgid ""
-"Help fix the parts of the website that are outdated or incomplete.\n"
-"Translate pages into other languages."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:34
-msgid "Pictures"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:35
-msgid "Make some more pictures, fix the old ones on the website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:39
-msgid "Make an eepsite! Add some content! Contribute to the community!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:42
-msgid "Services"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:43
-msgid ""
-"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n"
-"a naming service, a search engine, an eepsite monitor... many of these\n"
-"aren't that hard."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:49
-#, python-format
-msgid ""
-"Write or port applications for I2P! There's some guidelines and\n"
-"a list of ideas on the applications page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:53
-msgid "Coding"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:54
-#, python-format
-msgid ""
-"There's plenty to do if you know Java or are ready to learn.\n"
-"Check for open tickets on Trac\n"
-"or the TODO list on %(zzz)s for\n"
-"some ideas on where to start.\n"
-"See the new developer's guide for details."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:61
-msgid "Translation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:62
-#, python-format
-msgid ""
-"Help translate the website and the software into your language.\n"
-"See the new translator's guide for details."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:66
-msgid "Analysis"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:67
-#, python-format
-msgid ""
-"Study or test the code to look for vulnerabilities.\n"
-"Both anonymity vulnerabilities from the various\n"
-"threat models,\n"
-"and DOS and other weaknesses due to securities holes,\n"
-"need researching."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:7
-msgid ""
-"Include some seed data in the distribution so a central reseed location "
-"isn't required?"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:10
-#, python-format
-msgid ""
-"Reachability Mapping / handle peers partially reachable / enhanced restricted routes"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:13
-msgid "Improve help pages and website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:14
-msgid "More translations"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:15
-msgid "SSU disconnect message"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:16
-msgid "Iterative floodfill lookups"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:21
-msgid "Full review of anonymity issues and other vulnerabilities"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:22
-msgid ""
-"Reduce memory usage, remove debugging overhead, make it run better on "
-"slow and embedded machines"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:25
-msgid "Docs"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:30
-msgid "Full restricted routes"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:35
-msgid "Tunnel mixing and padding"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:36
-msgid "User defined message delays"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:39
-#, python-format
-msgid ""
-"Please see the TODO list for more detailed info "
-"about some of these tasks."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:4
-msgid "I2P Project Targets"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:5
-#, python-format
-msgid ""
-"Below is a more detailed (yet still incomplete) discussion of the major "
-"areas\n"
-"of future development on the core I2P network, spanning the plausibly "
-"planned\n"
-"releases. This does not include stego transports, porting to wireless "
-"devices,\n"
-"or tools to secure the local machine, nor does it include client "
-"applications\n"
-"that will be essential in I2P's success. There are probably other things "
-"that\n"
-"will come up, especially as I2P gets more peer review, but these are the "
-"main\n"
-"'big things'. See also the roadmap. Want to "
-"help?\n"
-"Get involved!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:16
-#: i2p2www/pages/site/get-involved/todo.html:54
-msgid "Core functionality"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:18
-#: i2p2www/pages/site/get-involved/todo.html:57
-msgid "NAT/Firewall bridging via 1-hop restricted routes"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:21
-#: i2p2www/pages/site/get-involved/todo.html:130
-msgid "High degree transport layer with UDP, NBIO, or NIO"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:24
-#: i2p2www/pages/site/get-involved/todo.html:218
-msgid "NetworkDB and profile tuning and ejection policy for large nets"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:28
-#: i2p2www/pages/site/get-involved/todo.html:242
-msgid "Security / anonymity"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:30
-#: i2p2www/pages/site/get-involved/todo.html:245
-msgid ""
-"Per-hop tunnel id & new permuted TunnelVerificationStructure "
-"encryption"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:33
-#: i2p2www/pages/site/get-involved/todo.html:295
-msgid "Strict ordering of participants within tunnels"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:36
-msgid "Randomly permuted tunnel lengths"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:39
-#: i2p2www/pages/site/get-involved/todo.html:357
-msgid "Full blown n-hop restricted routes with optional trusted links"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:42
-#: i2p2www/pages/site/get-involved/todo.html:376
-msgid "Hashcash for routerIdentity, destination, and tunnel request"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:45
-#: i2p2www/pages/site/get-involved/todo.html:405
-msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:48
-#: i2p2www/pages/site/get-involved/todo.html:442
-msgid "Stop & go mix w/ garlics & tunnels"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:62
-msgid "Implemented in I2P 0.6.0.6"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:63
-msgid ""
-"The functionality of allowing routers to fully participate within the "
-"network \n"
-"while behind firewalls and NATs that they do not control requires some "
-"basic \n"
-"restricted route operation (since those peers will not be able to receive"
-" \n"
-"inbound connections). To do this successfully, you consider peers one of"
-" \n"
-"two ways:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:73
-msgid ""
-"Peers who have reachable interfaces - these peers do not need to \n"
-"do anything special"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:77
-msgid ""
-"Peers who do not have reachable interfaces - these peers must "
-"build \n"
-"a tunnel pointing at them where the gateway is one of the peers they have"
-" \n"
-"established a connection with who has both a publicly reachable interface"
-" \n"
-"and who has agreed to serve as their 'introducer'."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:85
-msgid ""
-"To do this, peers who have no IP address simply connect to a few peers, \n"
-"build a tunnel through them, and publish a reference to those tunnels "
-"within \n"
-"their RouterInfo structure in the network database."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:90
-msgid ""
-"When someone wants to contact any particular router, they first must get"
-" \n"
-"its RouterInfo from the network database, which will tell them whether "
-"they \n"
-"can connect directly (e.g. the peer has a publicly reachable interface) \n"
-"or whether they need to contact them indirectly. Direct connections occur"
-" \n"
-"as normal, while indirect connections are done through one of the "
-"published \n"
-"tunnels."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:98
-msgid ""
-"When a router just wants to get a message or two to a specific hidden "
-"peer, \n"
-"they can just use the indirect tunnel for sending the payload. However, \n"
-"if the router wants to talk to the hidden peer often (for instance, as "
-"part \n"
-"of a tunnel), they will send a garlic routed message through the indirect"
-" \n"
-"tunnel to that hidden peer which unwraps to contain a message which "
-"should \n"
-"be sent to the originating router. That hidden peer then establishes an \n"
-"outbound connection to the originating router and from then on, those two"
-" \n"
-"routers can talk to each other directly over that newly established "
-"direct \n"
-"connection."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:109
-msgid ""
-"Of course, that only works if the originating peer can receive "
-"connections \n"
-"(they aren't also hidden). However, if the originating peer is hidden, "
-"they \n"
-"can simply direct the garlic routed message to come back to the "
-"originating \n"
-"peer's inbound tunnel."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:115
-msgid ""
-"This is not meant to provide a way for a peer's IP address to be "
-"concealed, \n"
-"merely as a way to let people behind firewalls and NATs fully operate "
-"within \n"
-"the network. Concealing the peer's IP address adds a little more work, as"
-" \n"
-"described below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:121
-msgid ""
-"With this technique, any router can participate as any part of a tunnel."
-" \n"
-"For efficiency purposes, a hidden peer would be a bad choice for an "
-"inbound \n"
-"gateway, and within any given tunnel, two neighboring peers wouldn't want"
-" \n"
-"to be hidden. But that is not technically necessary."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:133
-msgid "Both UDP and NIO have been Implemented in I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:134
-msgid ""
-"Standard TCP communication in Java generally requires blocking socket \n"
-"calls, and to keep a blocked socket from hanging the entire system, those"
-" \n"
-"blocking calls are done on their own threads. Our current TCP transport \n"
-"is implemented in a naive fashion - for each peer we are talking to, we \n"
-"have one thread reading and one thread writing. The reader thread simply"
-" \n"
-"loops a bunch of read() calls, building I2NP messages and adding them \n"
-"to our internal inbound message queue, and the writer thread pulls "
-"messages \n"
-"off a per-connection outbound message queue and shoves the data through \n"
-"write() calls."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:145
-msgid ""
-"We do this fairly efficiently, from a CPU perspective - at any time, \n"
-"almost all of these threads are sitting idle, blocked waiting for "
-"something \n"
-"to do. However, each thread consumes real resources (on older Linux "
-"kernels, \n"
-"for instance, each thread would often be implemented as a fork()'ed "
-"process). \n"
-"As the network grows, the number of peers each router will want to talk \n"
-"with will increase (remember, I2P is fully connected, meaning that any \n"
-"given peer should know how to get a message to any other peer, and "
-"restricted \n"
-"route support will probably not significantly reduce the number of "
-"connections \n"
-"necessary). This means that with a 100,000 router network, each router \n"
-"will have up to 199,998 threads just to deal with the TCP connections!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:157
-msgid ""
-"Obviously, that just won't work. We need to use a transport layer that \n"
-"can scale. In Java, we have two main camps:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:162
-#, python-format
-msgid ""
-"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:165
-msgid ""
-"Sending and receiving UDP datagrams is a connectionless operation - if \n"
-"we are communicating with 100,000 peers, we simply stick the UDP packets"
-" \n"
-"in a queue and have a single thread pulling them off the queue and "
-"shoving \n"
-"them out the pipe (and to receive, have a single thread pulling in any \n"
-"UDP packets received and adding them to an inbound queue)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:172
-msgid ""
-"However, moving to UDP means losing the benefits of TCP's ordering, "
-"congestion \n"
-"control, MTU discovery, etc. Implementing that code will take significant"
-" \n"
-"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n"
-"a while ago I was taking some measurements in the simulator and on the \n"
-"live net, and the vast majority of messages transferred would fit easily"
-" \n"
-"within a single unfragmented UDP packet, and the largest of the messages"
-" \n"
-"would fit within 20-30 packets. As mule pointed out, TCP adds a "
-"significant \n"
-"overhead when dealing with so many small packets, as the ACKs are within"
-" \n"
-"an order of magnitude in size. With UDP, we can optimize the transport \n"
-"for both efficiency and resilience by taking into account I2P's "
-"particular \n"
-"needs."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:185
-msgid "It will be a lot of work though."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:188
-msgid "NIO or NBIO"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:189
-msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:192
-msgid ""
-"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java"
-" \n"
-"developers to take advantage of the operating system's nonblocking IO \n"
-"capabilities - allowing you to maintain a large number of concurrent IO \n"
-"operations without requiring a separate thread for each. There is much \n"
-"promise with this approach, as we can scalable handle a large number of \n"
-"concurrent connections and we don't have to write a mini-TCP stack with \n"
-"UDP. However, the NIO packages have not proven themselves to be battle-"
-"ready, \n"
-"as the Freenet developer's found. In addition, requiring NIO support "
-"would \n"
-"mean we can't run on any of the open source JVMs like Kaffe, \n"
-"as GNU/Classpath has only "
-"limited \n"
-"support for NIO. (note: this may not be the case anymore, as there \n"
-"has been some progress on Classpath's NIO, but it is an unknown "
-"quantity)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:206
-#, python-format
-msgid ""
-"Another alternative along the same lines is the Non"
-" \n"
-"Blocking I/O package - essentially a cleanroom NIO implementation \n"
-"(written before NIO was around). It works by using some native OS code \n"
-"to do the nonblocking IO, passing off events through Java. It seems to \n"
-"be working with Kaffe, though there doesn't seem to be much development \n"
-"activity on it lately (likely due to 1.4's NIO deployment)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:221
-msgid ""
-"Within the current network database and profile management "
-"implementation, \n"
-"we have taken the liberty of some practical shortcuts. For instance, we \n"
-"don't have the code to drop peer references from the K-buckets, as we \n"
-"don't have enough peers to even plausibly fill any of them, so instead, \n"
-"we just keep the peers in whatever bucket is appropriate. Another example"
-" \n"
-"deals with the peer profiles - the memory required to maintain each "
-"peer's \n"
-"profile is small enough that we can keep thousands of full blown profiles"
-" \n"
-"in memory without problems. While we have the capacity to use trimmed \n"
-"down profiles (which we can maintain 100s of thousands in memory), we \n"
-"don't have any code to deal with moving a profile from a \"minimal "
-"profile\" \n"
-"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to"
-" simply \n"
-"eject a profile altogether. It just wouldn't be practical to write that \n"
-"code yet, since we aren't going to need it for a while."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:236
-msgid ""
-"That said, as the network grows we are going to want to keep these "
-"considerations \n"
-"in mind. We will have some work to do, but we can put it off for later."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:248
-#: i2p2www/pages/site/get-involved/todo.html:332
-#, python-format
-msgid ""
-"Addressed in I2P 0.5 as documented elsewhere"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:251
-msgid ""
-"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n"
-"going to Dave, then to Charlie, then Bob, and finally Alice "
-"(A<--B<--C<--D<--E), \n"
-"all five of them will know they are participating in tunnel \"123\", as \n"
-"the messages are tagged as such. What we want to do is give each hop "
-"their \n"
-"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n"
-"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n"
-"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n"
-"the tunnel had the same tunnel ID, collusion attacks aren't much work."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:261
-msgid ""
-"Adding a unique tunnel ID per hop isn't hard, but by itself, "
-"insufficient. \n"
-"If Dave and Bob are under the control of the same attacker, they wouldn't"
-" \n"
-"be able to tell they are in the same tunnel due to the tunnel ID, but \n"
-"would be able to tell by the message bodies and verification structures \n"
-"by simply comparing them. To prevent that, the tunnel must use layered \n"
-"encryption along the path, both on the payload of the tunneled message \n"
-"and on the verification structure (used to prevent simple tagging "
-"attacks). \n"
-"This requires some simple modifications to the TunnelMessage, as well \n"
-"as the inclusion of per-hop secret keys delivered during tunnel creation"
-" \n"
-"and given to the tunnel's gateway. We must fix a maximum tunnel length \n"
-"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n"
-"of the 16 delivered secret keys, in reverse order, and to encrypt the \n"
-"signature of the hash of the (encrypted) payload at each step. The "
-"gateway \n"
-"then sends that 16-step encrypted message, along with a 16-step and "
-"16-wide \n"
-"encrypted mapping to the first hop, which then decrypts the mapping and \n"
-"the payload with their secret key, looking in the 16-wide mapping for \n"
-"the entry associated with their own hop (keyed by the per-hop tunnel ID)"
-" \n"
-"and verifying the payload by checking it against the associated signed \n"
-"hash."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:282
-msgid ""
-"The tunnel gateway does still have more information than the other peers"
-" \n"
-"in the tunnel, and compromising both the gateway and a tunnel participant"
-" \n"
-"would allow those peers to collude, exposing the fact that they are both"
-" \n"
-"in the same tunnel. In addition, neighboring peers know that they are \n"
-"in the same tunnel anyway, as they know who they send the message to (and"
-" \n"
-"with IP-based transports without restricted routes, they know who they \n"
-"got it from). However, the above two techniques significantly increase \n"
-"the cost of gaining meaningful samples when dealing with longer tunnels."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:298
-msgid "Implemented in release 0.6.2"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:301
-#, python-format
-msgid ""
-"As Connelly proposed to deal with the\n"
-"predecessor attack (2008\n"
-"update), keeping the order of peers within our tunnels consistent \n"
-"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n"
-"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n"
-"get to substantially sample Alice's peer selection group. We may even \n"
-"want to explicitly allow Bob to participate in Alice's tunnels in only \n"
-"one way - receiving a message from Dave and sending it to Charlie - and \n"
-"if any of those peers are not available to participate in the tunnel (due"
-" \n"
-"to overload, network disconnection, etc), avoid asking Bob to participate"
-" \n"
-"in any tunnels until they are back online."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:316
-msgid ""
-"More analysis is necessary for revising the tunnel creation - at the \n"
-"moment, we simply select and order randomly within the peer's top tier \n"
-"of peers (ones with fast + high capacity)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:321
-msgid ""
-"Adding a strict ordering to peers in a tunnel also improves the anonymity"
-" \n"
-"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway"
-" \n"
-"is always the same would be particularly damning. However, peers with \n"
-"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n"
-"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n"
-"duration) minutes, use a 1-hop tunnel)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:338
-msgid ""
-"Without tunnel length permutation, if someone were to somehow detect that"
-" \n"
-"a destination had a particular number of hops, it might be able to use "
-"that \n"
-"information to identify the router the destination is located on, per the"
-" \n"
-"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n"
-"receives a tunnel message from Charlie and forwards it to Alice, Bob "
-"knows \n"
-"Alice is the final router in the tunnel. If Bob were to identify what "
-"destination \n"
-"that tunnel served (by means of colluding with the gateway and harvesting"
-" \n"
-"the network database for all of the LeaseSets), he would know the router"
-" \n"
-"on which that destination is located (and without restricted routes, that"
-" \n"
-"would mean what IP address the destination is on)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:350
-msgid ""
-"It is to counter user behavior that tunnel lengths should be permuted, \n"
-"using algorithms based on the length requested (for example, the 1/MTBF \n"
-"length change for 0-hop tunnels outlined above)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:360
-msgid ""
-"The restricted route functionality described before was simply a "
-"functional \n"
-"issue - how to let peers who would not otherwise be able to communicate \n"
-"do so. However, the concept of allowing restricted routes includes "
-"additional \n"
-"capabilities. For instance, if a router absolutely cannot risk "
-"communicating \n"
-"directly with any untrusted peers, they can set up trusted links through"
-" \n"
-"those peers, using them to both send and receive all of its messages. \n"
-"Those hidden peers who want to be completely isolated would also refuse \n"
-"to connect to peers who attempt to get them to (as demonstrated by the \n"
-"garlic routing technique outlined before) - they can simply take the "
-"garlic \n"
-"clove that has a request for delivery to a particular peer and tunnel \n"
-"route that message out one of the hidden peer's trusted links with "
-"instructions \n"
-"to forward it as requested."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:379
-#, python-format
-msgid ""
-"Within the network, we will want some way to deter people from consuming"
-" \n"
-"too many resources or from creating so many peers to mount a Sybil \n"
-"attack. Traditional techniques such as having a peer see who is "
-"requesting \n"
-"a resource or running a peer aren't appropriate for use within I2P, as \n"
-"doing so would compromise the anonymity of the system. Instead, we want \n"
-"to make certain requests \"expensive\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:387
-msgid ""
-"Hashcash is one technique that \n"
-"we can use to anonymously increase the \"cost\" of doing certain "
-"activities, \n"
-"such as creating a new router identity (done only once on installation),"
-" \n"
-"creating a new destination (done only once when creating a service), or \n"
-"requesting that a peer participate in a tunnel (done often, perhaps 2-300"
-" \n"
-"times per hour). We don't know the \"correct\" cost of each type of "
-"certificate \n"
-"yet, but with some research and experimentation, we could set a base "
-"level \n"
-"that is sufficiently expensive while not an excessive burden for people \n"
-"with few resources."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:398
-msgid ""
-"There are a few other algorithms that we can explore for making those \n"
-"requests for resources \"nonfree\", and further research on that front is"
-" \n"
-"appropriate."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:408
-#, python-format
-msgid ""
-"To powerful passive external observers as well as large colluding "
-"internal \n"
-"observers, standard tunnel routing is vulnerable to traffic analysis "
-"attacks \n"
-"- simply watching the size and frequency of messages being passed between"
-" \n"
-"routers. To defend against these, we will want to essentially turn some \n"
-"of the tunnels into its own mix cascade - delaying messages received at \n"
-"the gateway and passing them in batches, reordering them as necessary, \n"
-"and injecting dummy messages (indistinguishable from other \"real\" "
-"tunnel \n"
-"messages by peers in the path). There has been a significant amount of \n"
-"research \n"
-"on these algorithms that we can lean on prior to implementing the various"
-" \n"
-"tunnel mixing strategies."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:421
-msgid ""
-"In addition to the anonymity aspects of more varied tunnel operation, \n"
-"there is a functional dimension as well. Each peer only has a certain \n"
-"amount of data they can route for the network, and to keep any particular"
-" \n"
-"tunnel from consuming an unreasonable portion of that bandwidth, they \n"
-"will want to include some throttles on the tunnel. For instance, a tunnel"
-" \n"
-"may be configured to throttle itself after passing 600 messages (1 per \n"
-"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n"
-"last minute). Excess messages may be delayed or summarily dropped. With \n"
-"this sort of throttling, peers can provide ATM-like QoS support for their"
-" \n"
-"tunnels, refusing to agree to allocate more bandwidth than the peer has \n"
-"available."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:434
-msgid ""
-"In addition, we may want to implement code to dynamically reroute tunnels"
-" \n"
-"to avoid failed peers or to inject additional hops into the path. This \n"
-"can be done by garlic routing a message to any particular peer in a "
-"tunnel \n"
-"with instructions to redefine the next-hop in the tunnel."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:445
-msgid ""
-"Beyond the per-tunnel batching and mixing strategy, there are further \n"
-"capabilities for protecting against powerful attackers, such as allowing"
-" \n"
-"each step in a garlic routed path to define a delay or window in which \n"
-"it should be forwarded on. This would enable protections against the long"
-" \n"
-"term intersection attack, as a peer could send a message that looks "
-"perfectly \n"
-"standard to most peers that pass it along, except at any peers where the"
-" \n"
-"clove exposed includes delay instructions."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:457
-#, python-format
-msgid ""
-"Performance related improvements are listed on the\n"
-"Performance page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2
-msgid "Bounty Arabic translation of webpage and router console"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3
-#: i2p2www/pages/site/get-involved/bounties/index.html:119
-msgid "Arabic translation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2P echelon set out this bounty for translation\n"
-"of the I2P web page and I2P router console into Arabic."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12
-msgid "This bounty is set into 2 subparts:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14
-msgid "Part 1 is translation of the webpage."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17
-msgid ""
-"For collecting the bounty of 20 BTC you need to translate the following "
-"pages:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25
-msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27
-msgid ""
-"Part 2 is the translation of the router console. The router console was\n"
-"partly translated and the bounty of 80 BTC was paid to hamada."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34
-msgid "Judge is echelon."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2
-msgid "Bounty creating a I2P native Bitcoin client"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3
-msgid "BTC I2P native client"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6
-msgid ""
-"For a future of I2P and attract more people\n"
-"into I2P this bounty is to create a I2P native Bitcoin client. \n"
-"It should integrate with other client via the I2P network and via "
-"gateways to\n"
-"the existant bitcoin network."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15
-msgid "Judge is psychonaut who donated the first 30 € to this bounty."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
-msgid "Bounty datastorage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:3
-msgid "datastore"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:6
-msgid ""
-"To improve I2P's usage and to be independent of routers \n"
-"online status we want a datastorage as a extension to I2P.\n"
-"Like in Freenet the datastorage should be distributed and every\n"
-"participating node should be able to configure his options.\n"
-"The files should be saved in chunks and at least 2-3 times to\n"
-"obtain redundancy. Usage of storage space should be auto balanced.\n"
-"As it is a extra application, it should work flawless within I2P and\n"
-"cooperate nice with the I2P router. Maybe a integration within the\n"
-"webpage/router could be done."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:17
-msgid ""
-"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n"
-"\"eepsites in datastorage\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:21
-msgid ""
-"The frost for I2P datastorage bounty is paid for a frost like program \n"
-"with which files/messages are stored into database and got from database."
-"\n"
-"It needs to work with a GUI."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:26
-msgid ""
-"The eepsite served out of I2P datastorage extends a I2P router to send\n"
-"out eepsites out of the I2P datastorage. All files for eepsites need to "
-"be\n"
-"saved inside of datastorage and are taken from it.\n"
-"Extension:\n"
-"For better integration all datastorage participants could serve that "
-"eepsite."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:36
-msgid ""
-"For bounties to be declared done and paid, we need the program AND the "
-"source.\n"
-"Source and code need to be licensed under a free license (free to change "
-"and \n"
-"free to distribute)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2
-msgid "Bounty I2P package in Debian and Ubuntu mirrors"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3
-msgid "I2P Ubuntu/Debian package"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6
-msgid ""
-"For the future of I2P and in order to attract more people\n"
-"to I2P, this bounty was set for including an I2P package into the Ubuntu "
-"and Debian \n"
-"archive mirrors.\n"
-"To claim this bounty, the I2P router package needs to be available from\n"
-"Ubuntu and Debian archive mirrors and Debian bug \n"
-"448638 \n"
-"needs to be closed successfully."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2
-msgid "Bounty I2PHex code implementation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3
-msgid "i2phex code implementation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2PHex P2P ArneBab setout the bounty for implementing actual\n"
-"Phex code onto I2PHex."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:5
-msgid "Bounties for I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:6
-msgid ""
-"While we always gratefully accept any contributions of code, \n"
-"documentation, and the like, there are other ways to help I2P move \n"
-"forward.  As with any open source project, our goals would be achieved "
-"more \n"
-"rapidly if we were able to support all of our contributors to work on \n"
-"I2P full time.  However, as with any open source project, that's not a \n"
-"possibility.  Instead, we are making use of a bounty system, whereby \n"
-"anyone can get support for working on something that people want \n"
-"implemented, and people who want to contribute to I2P can be assured that"
-" \n"
-"their support goes to what they care about."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:18
-msgid ""
-"We are also keeping open the ability for people who want to support I2P \n"
-"but don't have strong feelings about the bounties available.  Those "
-"people\n"
-"can simply put their trust in the I2P team to do what we feel is best by\n"
-"donating to a catch-all general fund that will be used as deemed \n"
-"necessary - allocated to various bounties, covering incidentals (hosting,"
-" \n"
-"etc), and the like."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:27
-msgid "Current bounties"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-#: i2p2www/pages/site/get-involved/bounties/index.html:112
-msgid "Name"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-#: i2p2www/pages/site/get-involved/bounties/index.html:112
-msgid "Status"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-msgid "Judge"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-msgid "Bounty"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:32
-msgid "Frost for I2P datastorage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:33
-#: i2p2www/pages/site/get-involved/bounties/index.html:40
-#: i2p2www/pages/site/get-involved/bounties/index.html:47
-#: i2p2www/pages/site/get-involved/bounties/index.html:54
-#: i2p2www/pages/site/get-involved/bounties/index.html:61
-#: i2p2www/pages/site/get-involved/bounties/index.html:82
-#: i2p2www/pages/site/get-involved/bounties/index.html:89
-msgid "Proposal in development"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:39
-msgid "Eepsites served out of I2P datastorage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:46
-msgid "Backporting Phex code onto I2PHex"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:53
-msgid "Make I2P IPv6 native"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:60
-msgid "I2P package in Debian and Ubuntu mirrors"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:68
-msgid "Done, phase of verification"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:74
-msgid "Unit tests and Multi-router Simulation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:75
-msgid "Partly done, partly in work, partly still open"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:96
-msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:101
-msgid "Bundling bounties"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:102
-msgid "Proposed"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:109
-msgid "Claimed bounties"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:112
-msgid "Dev team"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:114
-msgid "Setting up a SILC server"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:124
-msgid "Datastore over I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:129
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
-msgid "Russian translation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:134
-msgid "Swarming file transfer"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:139
-msgid "Streaming library window size"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:144
-msgid "IRC connect time monitor"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:149
-msgid "Unit tests (part 1)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:161
-msgid ""
-"Dev lists anyone who may already be working on the bounty - collaboration"
-" is\n"
-"preferred, so if you're interested in working on it, please contact one "
-"of the\n"
-"people listed!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2
-msgid "Bounty I2P IPv6 native"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3
-msgid "native IPv6 I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6
-msgid ""
-"For a future of I2P and attract more people\n"
-"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n"
-"To claim this bounty, the I2P router needs to run full on native\n"
-"IPv6 connections like it does on IPv4."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:15
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
-msgid ""
-"For bounties to be declared done and paid, we need the plugin AND the "
-"source.\n"
-"Source and code need to be licensed under a free license (free to change "
-"and \n"
-"free to distribute)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:2
-msgid "NetDB Backend"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:3
-msgid "netDB backend"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:7
-msgid ""
-"The current NetDB implementation (namely the FloodFill system)\n"
-"needs to be extended with another backend to improve reliability,\n"
-"reduce attack surface and solve the scalability issue for the \n"
-"coming years."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:14
-msgid ""
-"A solution likely based on a DHT will be investigated and \n"
-"finally implemented."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2
-msgid "Bounty russian translation of webpage and router console"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2P a anonymous donator set out the bounty for translation\n"
-"of the I2P web page and I2P router console into russian language."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17
-msgid ""
-"For collecting the bounty of $115 USD you need to translate the following"
-" pages:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30
-msgid ""
-"Part 2 is the translation of the router console. The whole router console"
-" needs\n"
-"to be translated to collect the bounty of $115 USD."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37
-msgid "Judge is the russian donor."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:2
-msgid "Bounty migrate I2P IRC to SILC"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:3
-msgid "I2P silc server"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:7
-msgid ""
-"For a future of I2P and attract more people\n"
-"into I2P this bounty is to setup and host a I2P SILC server.   \n"
-"This will allow people to send files over their messaging servers and "
-"have intrinsic security built into the protocol."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:12
-msgid ""
-"A silc server needs to be set up and run for at least 3 month time to get"
-" payed. \n"
-"A second server should be set up, to."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:16
-msgid ""
-"Bounty was withdrawn and money donated to returningnovice and general "
-"fund."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:22
-msgid "Judge is An Anonymous Secret Society, society@mail.i2p."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7
-msgid ""
-"Beside of I2P we want to encourage users\n"
-"to care more about anonymity and security. As I2P is a low \n"
-"latency network with its natural limits, the software SYNDIE\n"
-"can overcome some of these limits and provide better anonymity\n"
-"for people who really need it."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14
-msgid ""
-"For our bad sake the syndie project was out of development for \n"
-"quite a long time yet (5 years). To get a fresh and new built \n"
-"with needed bugfixes we set out this bounty. Also syndie needs\n"
-"some enhancements and a better GUI for users to work with it.\n"
-"Current bounty sum is 50 Bitcoin."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22
-msgid ""
-"The latest Syndie coding rally did improve the situation of the\n"
-"Syndie package dramatically. A new Syndie package with bugfixes\n"
-"was created and made available on different webpages.\n"
-"As a result of this work, the bounty sum was reduced and\n"
-"the withdrawn money moved to the IPv6 bounty."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2
-msgid "Bounty unittests"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3
-msgid "unit test"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7
-msgid ""
-"To improve I2P's maintainability, we want to have a solid set of\n"
-"automated unit tests for the critical code.  While we do have some\n"
-"unit tests at the moment, they are ad-hoc and partly unfinished.  \n"
-"This bounty is for someone to check the existing tests and move over\n"
-"old ones to jUnit, automate their execution, extend them to provide \n"
-"better code coverage, and publish the report online.  Its a massive \n"
-"effort, but can be broken down into phases, listed below (phase 2 \n"
-"must occur first, but further phases may happen in any order).\n"
-"As this needs some reading of code, it is the best start point for\n"
-"new devs to get a good overview of I2P code and coding. A good job\n"
-"for college students, interns or anyone who is just interested."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20
-msgid ""
-"Take care! Jobs and bounties shuffled a bit!\n"
-"Phase 6,7 and 8 are still open!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112
-#, python-format
-msgid "Phase %(phase)s:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27
-msgid "CI jenkins and IRC bot"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114
-#, python-format
-msgid "Bounty: %(euro)s €"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29
-msgid "server runs and this section is blocked"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31
-msgid ""
-"To collect this bounty, a continuous integration server (Jenkins,\n"
-"old name was Hudson) must be set up and a connected IRC bot needs \n"
-"to set up in the channel #i2p-dev on IRC2p network to print out\n"
-"results of build tests.
            \n"
-"The server needs to be run long term."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41
-msgid "Check existing SDK tests"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69
-msgid "paid to str4d"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45
-#, python-format
-msgid ""
-"To collect this bounty, the existing SDK tests must be checked \n"
-"and made to work again. The need to be integrated into the ant \n"
-"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g."
-" \n"
-"Clover).  The ant script\n"
-"must be capable of generating test status results as a web page, \n"
-"which will be published online."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56
-msgid "SDK test coverage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80
-msgid "paid to unittests dev team"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60
-msgid ""
-"To collect this bounty, the automated unit tests of the SDK \n"
-"(i2p/core/java/src) must work again."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67
-msgid "Router test migration"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71
-msgid ""
-"As with phase 2, the existing unit tests for the router must be\n"
-"moved over to the automated system."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78
-msgid "Router test coverage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82
-msgid ""
-"To collect this bounty, the automated unit tests of the router \n"
-"(i2p/router/java/src) must work again."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89
-msgid "Streaming lib tests"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94
-#, python-format
-msgid ""
-"To collect this bounty, a new set of unit tests must meet a \n"
-"measured code coverage of 90% of the streaming lib \n"
-"(i2p/apps/ministreaming/ and i2p/apps/streaming/)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102
-msgid "Unit tests coverage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106
-msgid ""
-"To collect this bounty, all above unit tests must meet the 100%\n"
-"coverage marker (except for log statements)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113
-msgid "MultiRouter simulation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115
-msgid "will be split in more sub-tasks"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117
-msgid ""
-"To collect this bounty, the existing in-memory multi-router\n"
-"simulation must be checked, made work again and extend to simulate\n"
-"lots of routers in memory on a single machine. This bounty will\n"
-"be split in more fine grained subworks."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126
-msgid ""
-"Judge on all these works is the donor and donor decides if a phase is\n"
-"called succesfull done and money can be paid."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2
-msgid "Bounty I2P vuze plugin"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3
-msgid "vuze plugin"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2P torrent P2P I setout the bounty for a working I2P vuze\n"
-"plugin.\n"
-"The plugin needs to be official and submitted to vuze for publication\n"
-"on their webpage/repository for plugins.\n"
-"It should be easy to install and configured, work smooth and flawless.\n"
-"Configuration should be friendly to starters and made easy to be "
-"anonymous.\n"
-"It should work with *.b32.i2p destinations as with signed (516++ bits) \n"
-"destinations."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:2
-msgid "Application Development"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:6
-msgid "Application Development Guide"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:10
-#: i2p2www/pages/site/get-involved/develop/applications.html:16
-msgid "Why write I2P-specific code?"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:11
-#: i2p2www/pages/site/get-involved/develop/applications.html:102
-msgid "Important concepts"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:12
-#: i2p2www/pages/site/get-involved/develop/applications.html:190
-msgid "Development options"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:13
-#: i2p2www/pages/site/get-involved/develop/applications.html:303
-msgid "Start developing - a simple guide"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:18
-#, python-format
-msgid ""
-"There are multiple ways to use applications in I2P.\n"
-"Using I2PTunnel,\n"
-"you can use regular applications without needing to program explicit I2P "
-"support.\n"
-"This is very effective for client-server scenario's,\n"
-"where you need to connect to a single website.\n"
-"You can simply create a tunnel using I2PTunnel to connect to that "
-"website, as shown in Figure 1."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:26
-msgid ""
-"If your application is distributed, it will require connections to a "
-"large amount of peers.\n"
-"Using I2PTunnel, you will need to create a new tunnel for each peer you "
-"want to contact,\n"
-"as shown in Figure 2.\n"
-"This process can of course be automated, but running a lot of I2PTunnel "
-"instances creates a large amount of overhead.\n"
-"In addition, with many protocols you will need to force everyone to \n"
-"use the same set of ports for all peers - e.g. if you want to reliably "
-"run DCC \n"
-"chat, everyone needs to agree that port 10001 is Alice, port 10002 is "
-"Bob, port \n"
-"10003 is Charlie, and so on, since the protocol includes TCP/IP specific "
-"information\n"
-"(host and port)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:37
-msgid ""
-"General network applications often send a lot of additional data that "
-"could be used to identify users.\n"
-"Hostnames, port numbers, time zones, character sets, etc. are often sent "
-"without informing the user.\n"
-"As such, designing the network protocol specifically with anonymity in "
-"mind\n"
-"can avoid compromising user identities."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:43
-msgid ""
-"There are also efficiency considerations to review when determining how "
-"to \n"
-"interact on top of I2P.  The streaming library and things built on top of"
-" it\n"
-"operate with handshakes similar to TCP, while the core I2P protocols "
-"(I2NP and I2CP)\n"
-"are strictly message based (like UDP or in some instances raw IP).  The "
-"important\n"
-"distinction is that with I2P, communication is operating over a long fat "
-"network - \n"
-"each end to end message will have nontrivial latencies, but may contain "
-"payloads \n"
-"of up to several KB.  An application that needs a simple request and "
-"response can get rid\n"
-"of any state and drop the latency incurred by the startup and teardown "
-"handshakes\n"
-"by using (best effort) datagrams without having to worry about MTU "
-"detection or \n"
-"fragmentation of messages."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:57
-#: i2p2www/pages/site/get-involved/develop/applications.html:59
-msgid ""
-"Creating a server-client connection using I2PTunnel only requires "
-"creating a single tunnel."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:59
-msgid "Figure 1:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:64
-#: i2p2www/pages/site/get-involved/develop/applications.html:66
-msgid ""
-"Setting up connections for a peer-to-peer applications requires a very "
-"large amount of tunnels."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:66
-msgid "Figure 2:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:70
-msgid "In summary, a number of reasons to write I2P-specific code:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:74
-msgid ""
-"Creating a large amount of I2PTunnel instances consumes a non-trivial "
-"amount of resources,\n"
-"which is problematic for distributed applications (a new tunnel is "
-"required for each peer)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:78
-msgid ""
-"General network protocols often send a lot of additional data that can be"
-" used to identify users.\n"
-"Programming specifically for I2P allows the creation of a network "
-"protocol\n"
-"that does not leak such information, keeping users anonymous and secure."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:83
-msgid ""
-"Network protocols designed for use on the regular internet can be "
-"inefficient\n"
-"on I2P, which is a network with a much higher latency."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:90
-#, python-format
-msgid ""
-"I2P supports a standard plugins interface for"
-" developers\n"
-"so that applications may be easily integrated and distributed."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:96
-msgid ""
-"Applications written in Java and accessible/runnable\n"
-"using an HTML interface via the standard webapps/app.war\n"
-"may be considered for inclusion in the i2p distribution."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:104
-msgid "There are a few changes that require adjusting to when using I2P:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:108
-msgid "Destination ~= host+port"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:110
-msgid ""
-"An application running on I2P sends messages from and receives messages "
-"to a\n"
-"unique cryptographically secure end point - a \"destination\".  In TCP or"
-" UDP\n"
-"terms, a destination could (largely) be considered the equivalent of a "
-"hostname\n"
-"plus port number pair, though there are a few differences."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:118
-msgid ""
-"An I2P destination itself is a cryptographic construct - all data sent to"
-" one is \n"
-"encrypted as if there were universal deployment of IPsec with the "
-"(anonymized)\n"
-"location of the end point signed as if there were universal deployment of"
-" DNSSEC."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:123
-msgid ""
-"I2P destinations are mobile identifiers - they can be moved from one I2P "
-"router\n"
-"to another (or it can even \"multihome\" - operate on multiple routers at"
-"\n"
-"once).  This is quite different from the TCP or UDP world where a single "
-"end point (port)\n"
-"must stay on a single host."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:130
-msgid ""
-"I2P destinations are ugly and large - behind the scenes, they contain a "
-"2048 bit ElGamal\n"
-"public key for encryption, a 1024 bit DSA public key for signing, and a "
-"variable size \n"
-"certificate, which may contain proof of work or blinded data."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:135
-#, python-format
-msgid ""
-"There are existing ways to refer to these large and ugly destinations by "
-"short\n"
-"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not "
-"guarantee\n"
-"globally uniqueness (since they're stored locally in a database on each "
-"person's machine)\n"
-"and the current mechanism is not especially scalable nor secure (updates "
-"to the host list are\n"
-"managed using \"subscriptions\" to naming services).\n"
-"There may be some secure, human readable, scalable, and globally \n"
-"unique, naming system some day, but applications shouldn't depend upon it"
-" being in place,\n"
-"since there are those who don't think such a beast is possible.\n"
-"Further information on the naming system is "
-"available."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:149
-#, python-format
-msgid ""
-"While most applications do not need to distinguish protocols and ports,\n"
-"I2P does support them. Complex applications may specify a "
-"protocol,\n"
-"from port, and to port, on a per-message basis, to multiplex traffic on\n"
-"a single destination.\n"
-"See the datagram page for details.\n"
-"Simple applications operate by listening for \"all protocols\" on \"all "
-"ports\" of a destination."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:158
-msgid "Anonymity and confidentiality"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:160
-msgid ""
-"I2P has transparent end to end encryption\n"
-"and authentication for all data passed over the network - if Bob sends to"
-" Alice's destination,\n"
-"only Alice's destination can receive it, and if Bob is using the "
-"datagrams or streaming \n"
-"library, Alice knows for certain that Bob's destination is the one who "
-"sent the data."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:167
-msgid ""
-"Of course, I2P transparently anonymizes the\n"
-"data sent between Alice and Bob, but it does nothing to anonymize the "
-"content of what they\n"
-"send.  For instance, if Alice sends Bob a form with her full name, "
-"government IDs, and \n"
-"credit card numbers, there is nothing I2P can do.  As such, protocols and"
-" applications should \n"
-"keep in mind what information they are trying to protect and what "
-"information they are willing\n"
-"to expose."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:176
-msgid "I2P datagrams can be up to several KB"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:178
-#, python-format
-msgid ""
-"Applications that use I2P datagrams (either raw or repliable ones) can "
-"essentially be thought\n"
-"of in terms of UDP - the datagrams are unordered, best effort, and "
-"connectionless - but unlike\n"
-"UDP, applications don't need to worry about MTU detection and can simply "
-"fire off large datagrams.\n"
-"While the upper limit is nominally 32 KB, the message is fragmented for "
-"transport, thus dropping\n"
-"the reliability of the whole. Datagrams over about 10 KB are not "
-"currently recommended.\n"
-"See the datagram page for details.\n"
-"For many applications, 10 KB of data is sufficient for an\n"
-"entire request or response, allowing them to transparently operate in I2P"
-" as a UDP-like \n"
-"application without having to write fragmentation, resends, etc."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:192
-msgid ""
-"There are several means of sending data over I2P, each with their own "
-"pros and cons.\n"
-"The streaming lib is the recommended interface, used by the majority of "
-"I2P applications."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:197
-msgid "Streaming Lib"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:198
-#, python-format
-msgid ""
-"The full streaming library is now the "
-"standard\n"
-"interface. It allows programming using TCP-like sockets, as explained in "
-"the Streaming development guide."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:204
-#, python-format
-msgid ""
-"BOB is the Basic Open Bridge,\n"
-"allowing an application in any language to make streaming connections \n"
-"to and from I2P. At this point in time it lacks UDP support, but UDP "
-"support\n"
-"is planned in the near future. BOB also contains several tools, such as \n"
-"destination key generation, and verification that an address conforms to"
-" \n"
-"I2P specifications. Up to date info and applications that use BOB can be"
-" \n"
-"found at this eepsite."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:217
-msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:218
-#, python-format
-msgid ""
-"SAM is the Simple Anonymous Messaging protocol, "
-"allowing an\n"
-"application written in any language to talk to a SAM bridge through a "
-"plain TCP socket and have\n"
-"that bridge multiplex all of its I2P traffic, transparently coordinating "
-"the encryption/decryption\n"
-"and event based handling.  SAM supports three styles of operation:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:225
-msgid ""
-"streams, for when Alice and Bob want to send data to each other reliably "
-"and in order"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:228
-msgid ""
-"repliable datagrams, for when Alice wants to send Bob a message that Bob "
-"can reply to"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:231
-msgid ""
-"raw datagrams, for when Alice wants to squeeze the most bandwidth and "
-"performance as possible,\n"
-"and Bob doesn't care whether the data's sender is authenticated or not "
-"(e.g. the data transferred\n"
-"is self authenticating)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:237
-msgid ""
-"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n"
-"multiplexing/demultiplexing. Each I2P stream is handled by its own socket"
-" between the application\n"
-"and the SAM bridge. Besides, datagrams can be sent and received by the "
-"application through datagram\n"
-"communications with the SAM bridge."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:244
-#, python-format
-msgid ""
-"SAM V2 is a new version used by imule\n"
-"that fixes some of the problems in SAM.\n"
-"
            \n"
-"SAM V3 is used by imule since version 1.4.0."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:252
-msgid ""
-"The I2PTunnel application allows applications to build specific TCP-like "
-"tunnels to peers \n"
-"by creating either I2PTunnel 'client' applications (which listen on a "
-"specific port and connect\n"
-"to a specific I2P destination whenever a socket to that port is opened) "
-"or I2PTunnel 'server'\n"
-"applications (which listen to a specific I2P destination and whenever it "
-"gets a new I2P \n"
-"connection it outproxies to a specific TCP host/port).  These streams are"
-" 8-bit clean, and are\n"
-"authenticated and secured through the same streaming library that SAM "
-"uses, but there is a \n"
-"nontrivial overhead involved with creating multiple unique I2PTunnel "
-"instances, since each have\n"
-"their own unique I2P destination and their own set of tunnels, keys, etc."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:264
-msgid ""
-"I2P supports a SOCKS V4 and V5 proxy.\n"
-"Outbound connections work well. Inbound (server) and UDP functionality "
-"may be incomplete\n"
-"and untested."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:271
-msgid "Removed"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:272
-msgid ""
-"There used to be a simple \"ministreaming\" library,\n"
-"but now ministreaming.jar contains only the interfaces for the full "
-"streaming library."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:278
-msgid "Recommended for UDP-like applications"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:279
-#, python-format
-msgid ""
-"The Datagram library allows sending UDP-"
-"like packets.\n"
-"It's possible to use:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:284
-msgid "Repliable datagrams"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:285
-msgid "Raw datagrams"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:289
-msgid "Not recommended"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:290
-#, python-format
-msgid ""
-"I2CP itself is a language independent protocol, "
-"but to implement an I2CP library \n"
-"in something other than Java there is a significant amount of code to be "
-"written (encryption routines, \n"
-"object marshalling, asynchronous message handling, etc).  While someone "
-"could write an I2CP library in \n"
-"C or something else, it would most likely be more useful to use the C SAM"
-" library instead."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:297
-msgid "Web Applications"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:298
-msgid ""
-"I2P comes with the Jetty webserver, and configuring to use the Apache "
-"server instead is straightforward.\n"
-"Any standard web app technology should work."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:304
-msgid ""
-"Developing using I2P requires a working I2P installation and a "
-"development environment of your own choice.\n"
-"If you are using Java, you can start development with the streaming library or datagram library.\n"
-"Using another programming language, SAM or BOB can be used."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:310
-msgid "Developing with the streaming library"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:312
-msgid ""
-"The following example shows how to create TCP-like client and server "
-"applications\n"
-"using the streaming library."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:317
-msgid "This will require the following libraries in your classpath:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:321
-msgid "The streaming library itself"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:322
-msgid "Factory and interfaces for the streaming library"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:323
-msgid "Standard I2P classes, data structures, API, and utilities"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:326
-msgid ""
-"Network communication requires the usage of I2P network sockets.\n"
-"To demonstrate this, we will create an application where a client can "
-"send text messages to a server,\n"
-"who will print the messages and send them back to the client. In other "
-"words, the server will function as an echo."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:331
-msgid ""
-"We will start by initializing the server application. This requires "
-"getting an I2PSocketManager\n"
-"and creating an I2PServerSocket.\n"
-"We will not provide the I2PSocketManagerFactory with the saved keys for "
-"an existing Destination,\n"
-"so it will create a new Destination for us.\n"
-"So we will ask the I2PSocketManager for an I2PSession, so we can find out"
-" the Destination that\n"
-"was created, as we will need to copy and paste that information later so "
-"the client can connect to us."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:362
-msgid "Code example 1: initializing the server application."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:364
-msgid ""
-"Once we have an I2PServerSocket, we can create I2PSocket instances to "
-"accept connections from clients.\n"
-"In this example, we will create a single I2PSocket instance, that can "
-"only handle one client at a time.\n"
-"A real server would have to be able to handle multiple clients.\n"
-"To do this, multiple I2PSocket instances would have to be created, each "
-"in separate threads.\n"
-"Once we have created the I2PSocket instance, we read data, print it and "
-"send it back to the client.\n"
-"The bold code is the new code we add."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:448
-msgid "Code example 2: accepting connections from clients and handling messages."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:452
-msgid ""
-"When you run the above server code, it should print something like this "
-"(but without the line endings, it should just be\n"
-"one huge block of characters):"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:466
-msgid ""
-"This is the base64-representation of the server Destination. The client "
-"will need this string to reach the server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:470
-msgid ""
-"Now, we will create the client application. Again, a number of steps are "
-"required for initialization.\n"
-"Again, we will need to start by getting an I2PSocketManager.\n"
-"We won't use an I2PSession and an I2PServerSocket this time.\n"
-"Instead, we will use the server Destination string to start our "
-"connection.\n"
-"We will ask the user for the Destination string, and create an I2PSocket "
-"using this string.\n"
-"Once we have an I2PSocket, we can start sending and receiving data to and"
-" from the server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:554
-msgid ""
-"Code example 3: starting the client and connecting it to the server "
-"application."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:556
-msgid ""
-"Finally, you can run both the server and the client application.\n"
-"First, start the server application. It will print a Destination string "
-"(like shown above).\n"
-"Next, start the client application. When it requests a Destination "
-"string, you can enter the string printed by the server.\n"
-"The client will then send 'Hello I2P!' (along with a newline) to the "
-"server, who will print the message and send it back to the client."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:562
-msgid "Congratulations, you have successfully communicated over I2P!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:566
-msgid "Existing Applications"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:567
-msgid "Contact us if you would like to contribute."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:588
-msgid "Application Ideas"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:590
-msgid "NNTP server - there have been some in the past, none at the moment"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:593
-msgid ""
-"Jabber server - there have been some in the past, and there is one at the"
-" moment, with access to the public internet"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:596
-msgid "PGP Key server and/or proxy"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:599
-msgid ""
-"Content Distribution / DHT applications - resurrect feedspace,\n"
-"port dijjer, look for alternatives"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:603
-msgid "Help out with Syndie development"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:606
-msgid ""
-"Web-based applications - The sky is the limit for hosting web-server-"
-"based\n"
-"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n"
-"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:611
-msgid ""
-"Resurrect some old apps, several previously in the i2p source package -\n"
-"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2
-msgid "I2P Developer's MTN Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4
-msgid "MTN Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5
-msgid ""
-"Monotone servers used by the I2P project require two types of keys to be "
-"used."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
-msgid ""
-"Commit Keys to sign changes checked-in to the "
-"respository; and"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10
-msgid ""
-"Transport Keys to push changes to remote "
-"servers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13
-#, python-format
-msgid ""
-"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
-"import the\n"
-"developer commit keys, but only Monotone \n"
-"server operators will need to import the transport keys."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20
-msgid "Developer Commit keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:240
-msgid "Developer Transport Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:241
-#, python-format
-msgid ""
-"Note: Transport keys are only needed for setting up a\n"
-"Monotone server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
-msgid "License Agreements"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
-#, python-format
-msgid "For more information see the licenses page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8
-msgid ""
-"Following is a monotonerc file defining the current trust list.\n"
-"Developers must use this file in ~/.monotone/monotonerc or\n"
-"_MTN/montonerc in their i2p.i2p workspace."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17
-msgid "Agreements"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:4
-msgid "I2P Software Licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:5
-#, python-format
-msgid ""
-"As required by our\n"
-"threat model (among other reasons), the \n"
-"software developed to support the anonymous communication \n"
-"network we call I2P must be freely available, open source, \n"
-"and user modifiable.  To meet these criteria, we make use of\n"
-"a variety of legal and software engineering techniques so\n"
-"as to remove as many barriers to entry for those considering\n"
-"making use of or contributing to the I2P effort."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:16
-msgid ""
-"While the information below may be more confusing than just simply \n"
-"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
-"the short answer to the question \"How is I2P licensed?\" is this:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:22
-msgid "All software bundled in the I2P distributions will allow:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:24
-msgid "use without fee"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:25
-msgid ""
-"use with no restrictions on how, when, where, why, or by whom is running "
-"it"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:26
-msgid "access to the source code without fee"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:27
-msgid "modifications to the source"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:30
-msgid ""
-"Most of the software guarantees much more - the ability of anyone "
-"to \n"
-"distribute the modified source however they choose.  However, not all of "
-"the \n"
-"software bundled provides this freedom - the GPL restricts the ability of"
-" \n"
-"developers who wish to integrate I2P with their own applications that are"
-" not \n"
-"themselves open source applications.  While we applaud the noble goals of"
-" \n"
-"increasing the resources in the commons, I2P is best served by removing "
-"any\n"
-"barriers that stand in the way of its adoption - if a developer "
-"considering whether\n"
-"they can integrate I2P with their application has to stop and check with "
-"their lawyer,\n"
-"or conduct a code audit to make sure their own source can be released as "
-"GPL-compatible,\n"
-"we lose out."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:43
-msgid "Component licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:44
-msgid ""
-"The I2P distribution contains several resources, reflecting the "
-"partitioning of \n"
-"the source code into components.  Each component has its own license, "
-"which all \n"
-"developers who contribute to it agree to - either by explicitly declaring"
-" the release\n"
-"of code committed under a license compatible with that component, or by "
-"implicitly\n"
-"releasing the code committed under the component's primary license.  Each"
-" of these \n"
-"components has a lead developer who has the final say as to what license "
-"is compatible\n"
-"with the component's primary license, and the I2P project manager has the"
-" final say as\n"
-"to what licenses meet the above four guarantees for inclusion in the I2P "
-"distribution."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:57
-msgid "Component"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:58
-msgid "Source path"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:59
-msgid "Resource"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:60
-msgid "Primary license"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:61
-msgid "Alternate licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:62
-msgid "Lead developer"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:271
-msgid "GPL + java exception"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:272
-#, python-format
-msgid ""
-"While it may be redundant, just for clarity the\n"
-"GPL'ed code included within\n"
-"I2PTunnel and other apps must be released under the GPL with an "
-"additional \"exception\"\n"
-"explicitly authorizing the use of Java's standard libraries:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:288
-msgid ""
-"All source code under each component will by default be licensed under "
-"the\n"
-"primary license, unless marked otherwise in the code.  All of the above "
-"is\n"
-"summary of the license terms - please see the specific license for the "
-"component\n"
-"or source code in question for authoritative terms.  Component source "
-"locations and\n"
-"resource packaging may be changed if the repository is reorganized."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:296
-msgid "Commit privileges"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:297
-#, python-format
-msgid ""
-"Developers may push changes to a distributed monotone repository if you\n"
-"receive permission from the person running that repository.\n"
-"See the Monotone Page for details."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:303
-msgid ""
-"However, to have changes included in a release, developers\n"
-"must be trusted by the release manager (currently zzz).\n"
-"In addition, they must explicitly agree with the above terms to be "
-"trusted.\n"
-"That means that they must send one of the release managers a signed "
-"message affirming that:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:310
-msgid ""
-"Unless marked otherwise, all code I commit is implicitly licensed under\n"
-"the component's primary license"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:314
-msgid ""
-"If specified in the source, the code may be explicitly licensed under one"
-"\n"
-"of the component's alternate licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:318
-msgid ""
-"I have the right to release the code I commit under the terms I\n"
-"am committing it"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:324
-#, python-format
-msgid ""
-"If anyone is aware of any instances where the above conditions are not "
-"met,\n"
-"please contact the component lead and/or an I2P release manager with "
-"further\n"
-"information.\n"
-"See developers' license agreements."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
-msgid "Release Signing Key"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
-msgid "Releases 0.7.6 and later are signed by zzz. His public key is:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40
-msgid ""
-"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public "
-"key is:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2
-msgid "Signed Developer Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4
-msgid ""
-"Keys for zzz, Complication and welterde are provided clearsigned. The key"
-" for jrandom must be\n"
-"verified differently, since he's away, and only left a binary detached\n"
-"signature for his key."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16
-msgid "Monotone keys for zzz"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47
-msgid "Monotone keys for welterde"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79
-msgid "Monotone keys for Complication"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114
-msgid "Monotone keys for jrandom"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
-msgid ""
-"Tip: To find zzz's GPG key, on his eepsite locate the key "
-"`0xA76E0BED`, with\n"
-"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 "
-"B310 4155\n"
-"76BA A76E 0BED`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49
-msgid ""
-"Tip: To find welterde's GPG key, on public keyservers locate the "
-"key\n"
-"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720"
-" FD81\n"
-"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81
-msgid ""
-"Tip: To find Complication's GPG key, on his eepsite locate the key"
-"\n"
-"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint "
-"`73CF\n"
-"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116
-msgid ""
-"Tip: To find jrandom's GPG key for Syndie releases, on public "
-"keyservers locate\n"
-"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n"
-"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122
-msgid ""
-"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n"
-"deployed in the Syndie Monotone repository, in a file named `mtn-"
-"committers`.\n"
-"That file also had a GPG signature, `mtn-committers.sig`, but it was a "
-"binary\n"
-"detached signature. I am going to supply both files in GPG ASCII-armoured"
-" form\n"
-"below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130
-msgid ""
-"First, the file `mtn-committers` containing jrandom's Monotone key. Save "
-"as\n"
-"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers "
-"--dearmor\n"
-"mtn-committers.asc`:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151
-msgid ""
-"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n"
-"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-"
-"committers.sig\n"
-"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n"
-"`mtn-committers` file:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170
-#, python-format
-msgid ""
-"Some of the developers have included their Monotone keys in their signed license agreement."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2
-msgid "Developer Guidelines and Coding Style"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4
-#, python-format
-msgid "Read the new developers guide first."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8
-msgid "Basic Guidelines and Coding Style"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10
-msgid ""
-"Most of the following should be common sense for anybody who has worked "
-"on open source or in a commercial\n"
-"programming envrionment.\n"
-"The following applies mostly to the main development branch i2p.i2p.\n"
-"Guidelines for other branches, plugins, and external apps may be "
-"substantially different;\n"
-"check with the appropriate developer for guidance."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18
-msgid "Community"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20
-msgid ""
-"Please don't just \"write code\". If you can, participate in other "
-"development activities, including:\n"
-"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
-"testing;\n"
-"bug reporting and responses; documentation; code reviews; etc."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25
-msgid ""
-"Active devs should be available periodically on IRC #i2p-dev.\n"
-"Be aware of the current release cycle.\n"
-"Adhere to release milestones such as feature freeze, tag freeze, and\n"
-"the checkin deadline for a release."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35
-msgid ""
-"Have a basic understanding of distributed source control systems, even if"
-" you haven't\n"
-"used monotone before. Ask for help if you need it.\n"
-"Once pushed, checkins are forever, there is no undo. Please be careful.\n"
-"If you have not used monotone before, start with baby steps.\n"
-"Check in some small changes and see how it goes."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42
-msgid ""
-"Test your changes before checking them in.\n"
-"If you prefer the checkin-before-test development model,\n"
-"use your own development branch (e.g. i2p.i2p.yourname.test)\n"
-"and propagate back to i2p.i2p once it is working well.\n"
-"Do not break the build. Do not cause regressions.\n"
-"In case you do (it happens), please do not vanish for a long period after"
-"\n"
-"you push your change."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51
-msgid ""
-"If your change is non-trivial, or you want people to test it and need "
-"good test reports\n"
-"to know whether your change was tested or not, add a checkin comment to "
-"history.txt\n"
-"and increment the build revision in RouterVersion.java."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56
-msgid ""
-"Ensure that you have the latest monotonerc file in _MTN.\n"
-"Do not check in on top of untrusted revisions."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60
-msgid ""
-"Ensure that you pull the latest revision before you check in.\n"
-"If you inadvertently diverge, merge and push as soon as possible.\n"
-"Don't routinely make others merge for you.\n"
-"Yes, we know that monotone says you should push and then merge,\n"
-"but in our experience, in-workspace merge works just as well as in-"
-"database merge,\n"
-"without creating a merge revision."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
-msgid ""
-"Do not check in major changes into the main i2p.i2p branch late in the "
-"release cycle.\n"
-"If a project will take you more than a couple days, create your own "
-"branch in monotone\n"
-"and do the development there so you do not block releases."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75
-msgid "Coding Style"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77
-msgid ""
-"Coding style throughout most of the code is 4-spaces for indentation. Do "
-"not use tabs.\n"
-"Do not reformat code. If your IDE or editor wants to reformat everything,"
-" get control of it.\n"
-"Yes, we know 4 spaces is a pain, but perhaps you can configure your "
-"editor appropriately.\n"
-"In some places, the coding style is different.\n"
-"Use common sense. Emulate the style in the file you are modifying."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84
-msgid ""
-"New classes and methods require at least brief javadocs. Add @since "
-"release-number."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87
-msgid ""
-"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our "
-"official API.\n"
-"There are several out-of-tree plugins and other applications that rely on"
-" this API.\n"
-"Be careful not to make any changes that break compatibility.\n"
-"Don't add methods to the API unless they are of general utility.\n"
-"Javadocs for API methods should be clear and complete.\n"
-"If you add or change the API, also update the documentation on the "
-"website (i2p.www branch)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95
-msgid ""
-"Tag strings for translation where appropriate.\n"
-"Don't change existing tagged strings unless really necessary, as it will "
-"break existing translations.\n"
-"Do not add or change tagged strings after the \"tag freeze\" in the "
-"release cycle so that\n"
-"translators have a chance to update before the release."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101
-msgid ""
-"Use generics and concurrent classes where possible. I2P is a highly "
-"multi-threaded application."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104
-msgid ""
-"We require Java 6 to build but only Java 5 to run I2P.\n"
-"Do not use Java 6 classes or methods without handling the class not found"
-" exceptions\n"
-"and providing alternate Java 5 code. See classes in net.i2p.util for "
-"examples."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109
-msgid ""
-"Explicitly convert between primitive types and classes;\n"
-"don't rely on autoboxing/unboxing."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117
-msgid ""
-"Only check in code that you wrote yourself.\n"
-"Before checking in any code or library jars from other sources,\n"
-"justify why it is necessary,\n"
-"verify the license is compatible,\n"
-"and obtain approval from the lead developer."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124
-msgid ""
-"For any images checked in from external sources,\n"
-"it is your responsibility to first verify the license is compatible.\n"
-"Include the license and source information in the checkin comment."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131
-msgid "Bugs"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
-#, python-format
-msgid ""
-"Managing Trac tickets is everybody's job, please help.\n"
-"Monitor %(trac)s for tickets you have been assigned or can help with.\n"
-"Assign, categorize, comment on, fix, or close tickets if you can."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138
-msgid ""
-"Close a ticket when you think you've fixed it.\n"
-"We don't have a test department to verify and close tickets.\n"
-"If you arent sure you fixed it, close it and add a note saying\n"
-"\"I think I fixed it, please test and reopen if it's still broken\".\n"
-"Add a comment with the dev build number or revision and set\n"
-"the milestone to the next release."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:4
-msgid ""
-"The main I2P development branch (i2p.i2p) has been set up to"
-" enable developers to easily set up two of the commonly-used IDEs for "
-"Java development: Eclipse and NetBeans."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:10
-msgid ""
-"The main I2P development branches (i2p.i2p and branches from"
-" it) contain .project and .classpath Eclipse files, to enable the branch "
-"to be easily set up in Eclipse."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:16
-msgid ""
-"Check out the I2P branch into some directory (e.g. "
-"$HOME/dev/i2p.i2p)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:20
-msgid ""
-"Open Eclipse and create a new Workspace, based in the directory that the "
-"I2P branch was checked out to."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:24
-msgid ""
-"Select \"File - Import...\" and then under \"General\" select \"Existing "
-"Projects into Workspace\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:28
-msgid ""
-"For \"Select root directory:\" choose the directory that the I2P branch "
-"was checked out to."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:32
-msgid "If necessary, click \"Refresh\" to refresh the list of projects."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:36
-msgid "Select every project in the list, and click \"Finish\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:40
-msgid ""
-"Done! Your workspace should now contain all projects within the I2P "
-"branch, and their build dependencies should be correctly set up."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:48
-msgid ""
-"The main I2P development branches (i2p.i2p and branches from"
-" it) contain NetBeans project files."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:9
-msgid "Operating a Monotone client"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:11
-#: i2p2www/pages/site/get-involved/guides/monotone.html:63
-msgid "Generating Monotone keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:12
-msgid "Trust and initializing your repository"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:13
-#: i2p2www/pages/site/get-involved/guides/monotone.html:196
-msgid "Obtaining and deploying developers' keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:14
-#: i2p2www/pages/site/get-involved/guides/monotone.html:227
-msgid "Setting up trust evaluation hooks"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:15
-#: i2p2www/pages/site/get-involved/guides/monotone.html:268
-msgid ""
-"Pulling the i2p.i2p, i2p.www and "
-"i2p.syndie branches"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:16
-#: i2p2www/pages/site/get-involved/guides/monotone.html:308
-msgid "Verifying that trust evaluation works"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:17
-#: i2p2www/pages/site/get-involved/guides/monotone.html:357
-msgid "Checking out a working copy of the latest version"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:18
-#: i2p2www/pages/site/get-involved/guides/monotone.html:384
-msgid "Updating your working copy to the latest version"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:22
-#: i2p2www/pages/site/get-involved/guides/monotone.html:414
-msgid "Operating a Monotone Server"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:24
-msgid "Obtaining and deploying developers’ transport keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:25
-#: i2p2www/pages/site/get-involved/guides/monotone.html:424
-msgid "Granting push and pull access"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:26
-#: i2p2www/pages/site/get-involved/guides/monotone.html:469
-msgid "Running Monotone in server mode"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:27
-#: i2p2www/pages/site/get-involved/guides/monotone.html:494
-msgid "Differences under Debian GNU/Linux"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:34
-#, python-format
-msgid ""
-"This is a revised version of Complication's original\n"
-"  guide detailing the use of Monotone in I2P development.\n"
-"  For basic instructions see the quick-start "
-"guide."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:42
-#, python-format
-msgid ""
-"I2P has a distributed development model. The source code is replicated "
-"across\n"
-"  independently administered Monotone (\"MTN\") repositories.\n"
-"  Developers with commit rights are able to push their changes to the "
-"repository\n"
-"  (a license agreement needs to be "
-"signed\n"
-"  before commit rights are granted)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:52
-msgid ""
-"Some of Monotone's noteworthy qualities are: distributed\n"
-"  version control, cryptographic authentication, access control, its "
-"small size, having few\n"
-"  dependencies, storage of projects in a compressed SQLite database file,"
-" and\n"
-"  having the ability to resume interrupted synchronization attempts."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:61
-msgid "Operating a Monotone Client"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:66
-msgid ""
-"A transport key grants you the ability to push your changes to a Monotone"
-" repository server.\n"
-"  In order to commit code into Monotone (in essence signing your code), a"
-" commit key is also needed.\n"
-"  None of the public Monotone servers on I2P currently require a key in "
-"order to read (or pull) the source code."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:74
-msgid ""
-"Without a transport key, one cannot:\n"
-"  
              \n"
-"    
            • pull code from a server which doesn't allow global read "
-"access
              • \n"
-"    
            • push code to any server
              • \n"
-"    
            • run a Monotone server
              • \n"
-"  
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:85
-msgid ""
-"Without a commit key, one cannot:\n"
-"  
              \n"
-"    
            • commit any code
              • \n"
-"  
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:94
-msgid ""
-"If you only intend to retrieve code from MTN, feel free to skip to the\n"
-"  next section. "
-"If you want\n"
-"  to generate keys, read the following."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:102
-msgid ""
-"By convention keys are named like an e-mail addresses, but a "
-"corresponding e-mail\n"
-"  address does not need to exist. For example, your keys might be named:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:113
-msgid ""
-"Monotone stores keys under $HOME/.monotone/keys in "
-"text files which\n"
-"  are named identically to the keys. For example:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:123
-msgid ""
-"To generate transport and commit keys, enter the following commands at a "
-"prompt:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:133
-msgid ""
-"Monotone will prompt you for a password to protect your keys. You are "
-"very strongly encouraged to set a password\n"
-"  for the commit key. Many users will leave an empty password for the "
-"transport key, especially those running a\n"
-"  Monotone server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:141
-msgid "Trust, and initializing your repository"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:145
-msgid ""
-"Monotone's security model helps to ensure that nobody can easily "
-"impersonate a developer without\n"
-"  it being noticed. Since developers can make mistakes and become "
-"compromised,only manual review can\n"
-"  ensure quality of code. Monotone's trust model will ensure that you "
-"read the right diffs. It does\n"
-"  not replace reading diffs."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:155
-msgid ""
-"A Monotone repository is a single file (a compressed SQLite database) "
-"which contains all of the project's source code and history."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:161
-msgid ""
-"After importing the "
-"developers' keys into Monotone and\n"
-"  setting up trust "
-"evaluation hooks,\n"
-"  Monotone will prevent untrusted code from being checked out into your "
-"workspace.\n"
-"  There are commands available to clean untrusted code from your "
-"workspace but in practice they've not been\n"
-"  needed due to the push access policies in place."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:171
-msgid ""
-"A repository can hold many branches. For example, our repository holds "
-"the\n"
-"  following main branches:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:176
-msgid "The I2P router and associated programs"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:177
-msgid "The I2P project website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:178
-msgid "Syndie, a distributed forums tool"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:183
-msgid ""
-"By convention, the I2P Monotone repository is named i2p.mtn."
-" Before pulling\n"
-"  source code from servers, a database for your repository will need to "
-"be initialized.\n"
-"  To initialize your local repository, change into the directory that you"
-" want the\n"
-"  i2p.mtn file and branch directories to be stored and issue"
-" the following\n"
-"  command:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:199
-msgid ""
-"Keys which developers use to commit code are essential for trust "
-"evaluation in\n"
-"  Monotone. The other developers' transport keys are only required for "
-"Monotone server operators.\n"
-"  "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:206
-#, python-format
-msgid ""
-"Developers' commit keys are provided GPG-signed on another page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:212
-#, python-format
-msgid ""
-"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
-"  file. Create this file (e.g. keys.txt) in the same "
-"directory where i2p.mtn is located. Import the keys with the"
-" command:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:222
-msgid ""
-"Note: Never add keys to "
-"$HOME/.monotone/keys manually."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:230
-msgid ""
-"The default Monotone trust policy is way too lax for our requirements: "
-"every comitter is trusted by default.\n"
-"  That is not acceptable for I2P development."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:237
-msgid ""
-"Change into the directory $HOME/.monotone and open "
-"the file\n"
-"  monotonerc with a text editor. Copy and paste the "
-"following two functions into this file:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:246
-msgid ""
-"The first function determines an intersection between two sets, in our "
-"case a\n"
-"  revision's signers and trusted signers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:253
-msgid ""
-"The second function determines trust in a given revision, by calling the "
-"first\n"
-"  function with \"signers\" and \"trusted\" as arguments. If the "
-"intersection is\n"
-"  null, the revision is not trusted. If the intersection is not empty, "
-"the\n"
-"  revision is trusted. Otherwise, the revision is not trusted."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:262
-msgid ""
-"More information about Trust Evauluation Hooks can be found in the official Monotone "
-"documentation."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:271
-msgid ""
-"Enter the directory where you initialized i2p.mtn. Depending "
-"on whether you\n"
-"  want only I2P sources, or also sources for the I2P website and Syndie, "
-"you can\n"
-"  perform the pull operation in different ways."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:279
-msgid "If you only want I2P sources:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:288
-msgid "If you want all branches:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:294
-msgid ""
-"If the transfer aborts before completing sucessfully, simply repeating "
-"the pull command will resume the transfer."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:300
-msgid ""
-"Pulling in the above examples is done anonymously by specifying an empty "
-"transport key.\n"
-"  If everyone pulls anonymously it will be harder for an attacker who "
-"gains control of the server\n"
-"  to selectively provide some people with tampered data."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:311
-msgid "To verify that trust evaluation works:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:315
-msgid "Make a backup of your monotonerc file."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:316
-msgid ""
-"Modify monotonerc by setting the trusted_signers "
-"variable in the following way:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:322
-msgid ""
-"With monotonerc configured as above, Monotone will no"
-" longer trust any committers. Confirm this by changing into the\n"
-"directory where i2p.mtn was created and attempt a checkout "
-"of the I2P branch:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:332
-msgid ""
-"A directory named i2p.i2p should not appear. You "
-"should encounter many\n"
-"  error messages like:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:349
-msgid ""
-"If you are satisfied with results, restore the backup of\n"
-"  monotonerc that was created above. If you didn't create a "
-"backup\n"
-"  as advised, re-read Setting up trust evaluation hools."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:360
-msgid ""
-"If you already have a branch checked out, skip to the next\n"
-"  section."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:367
-msgid ""
-"Change into the directory where i2p.mtn is located. Over "
-"there issue:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:376
-msgid ""
-"The checkout should complete without error messages and a directory named"
-"\n"
-"  i2p.i2p should appear in the current directory. "
-"Congratulations! You have\n"
-"  successfully checked out the latest I2P sources, ready to be compiled."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:387
-msgid ""
-"If you haven't done this already, pull fresh code from the server to your"
-" local\n"
-"  Monotone repository. To accomplish this, change into the directory "
-"where\n"
-"  i2p.mtn is located and issue:\n"
-"  
              \n"
-"    
            • $ mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
-"i2p.i2p
              • \n"
-"  
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:398
-msgid "Now change into your i2p.i2p directory, and over there issue:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:407
-msgid ""
-"As long as there were no errors…Congratulations! You have "
-"successfully updated to the latest I2P sources. They\n"
-"  should be ready to compile."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:416
-msgid "Obtaining and deploying developers' transport keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:419
-msgid ""
-"As a server operator you may want to grant push access to certain "
-"developers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:427
-msgid "By default the Monotone server denies all access."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:433
-msgid "To grant pull access to all clients, set the following in"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:445
-msgid ""
-"No one will not be able to push code to your server without permission "
-"being explicitly granted. To grant push access:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:451
-msgid ""
-"Add the name of the user's transport key to\n"
-"$HOME/.monotone/write-permissions, such as\n"
-"
            \n"
-"    zzz-transport@mail.i2p\n"
-"    complication-transport@mail.i2p\n"
-"
            \n"
-"with one key per line."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:462
-msgid ""
-"Import the transport key(s) into your database. The procedure for "
-"importing transport keys is the same as for\n"
-"importing commit keys, which is described in the section Obtaining and deploying "
-"developers' keys."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:472
-msgid ""
-"A separate database should be used for your Monotone server because "
-"monotone will lock the database while it is served to others.\n"
-"  Make a copy of your development database, then start the server with:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:479
-msgid ""
-"If your key is protected with a passphrase, Monotone may request the "
-"passphrase\n"
-"  when the first client connects. You can work around this by connecting "
-"making the first client connection to your server\n"
-"  (or by clearing the password for your transport key)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:487
-msgid ""
-"For your server to be accessible for others over I2P, you will need to "
-"create a\n"
-"  server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" "
-"profile."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:497
-msgid ""
-"Debian (amongst other distributions) has integrated Monotone into their\n"
-"  framework of daemons/services. Although Monotone servers can still be "
-"run\n"
-"  \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may"
-" be more straightforward."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:505
-msgid ""
-"Permissions are granted by editing the files\n"
-"  /etc/monotone/read-permissions and\n"
-"  /etc/monotone/write-permissions. You'll also need to edit\n"
-"  /etc/default/monotone to enable monotone to start at boot "
-"or to\n"
-"  customize the host, port, or database location."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
-msgid ""
-"\n"
-"So you want to start work on I2P? Great!\n"
-"Here's a quick guide to getting started\n"
-"on contributing to the website or the software, doing development or "
-"creating translations."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
-#, python-format
-msgid ""
-"\n"
-"Not quite ready for coding?\n"
-"Try getting involved first."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
-msgid "Basic study"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
-msgid "Getting the I2P code"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
-msgid "Building I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
-msgid "Development ideas"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
-msgid "Making the results available"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
-msgid "Get to know us!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
-msgid "Translations"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
-msgid "Tools"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
-msgid ""
-"Basic development on the I2P router or the embedded applications uses "
-"Java as the main development language.\n"
-"If you don't have experience with Java, you can always have a look at Thinking in Java."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
-#, python-format
-msgid ""
-"Study the how intro,\n"
-"the other \"how\" documents,\n"
-"the tech intro,\n"
-"and associated documents.\n"
-"These will give you a good overview of how I2P is structured and what "
-"different things it does."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
-msgid ""
-"For development on the i2p router or the embedded applications,\n"
-"get the monotone source repository installed - short instructions:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
-msgid ""
-"Install monotone.\n"
-"Monotone is a version control system.\n"
-"We use it because it allows us to keep track of who does what changes to "
-"the source code (and for a lot of complicated things, but 'keeping track "
-"of changes' is the basic idea)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
-msgid ""
-"Skim over the monotone tutorial,"
-" to make sure you understand the concepts."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
-msgid ""
-"If you want to remain anonymous, you need to do an additional step, to "
-"set up a connection to a monotone server over I2P:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
-#, python-format
-msgid ""
-"Enable the i2ptunnel client tunnel on port "
-"8998 pointing to mtn.i2p2.i2p."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
-msgid ""
-"Pick a directory where you want to put all your I2P files, and create a "
-"monotone database:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
-msgid ""
-"Define the trust list by creating ~/.monotone/monotonerc (or"
-" _MTN/monotonerc in the i2p.i2p workspace) with the "
-"following contents:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
-#, python-format
-msgid ""
-"Copy and paste the developer's commit keys "
-"into a new file (e.g. keys.txt) in the same directory\n"
-"  that i2p.mtn is in. Import the keys into your database "
-"with 
                  mtn -d i2p.mtn read < keys.txt
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:76
-msgid ""
-"Pull the I2P sources to your machine. This may take a long time, "
-"especially if you are doing this over I2P!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:78
-msgid "Anonymously:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:81
-msgid "Non-anonymously:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:83
-msgid ""
-"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn"
-".i2p-projekt.de."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:90
-msgid ""
-"All the sources are now present on your machine, in the database file. To"
-" make them available in a directory, you need to check them out:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:92
-msgid ""
-"The above command creates a directory i2p.i2p, which contains all of the "
-"I2P sources."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:96
-msgid "Remarks"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:97
-msgid ""
-"\n"
-"To download the website files instead of the I2P source files, use "
-"'i2p.www' instead of 'i2p.i2p'."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:100
-msgid ""
-"The initial pull may take several hours using the tunnel.\n"
-"If it fails after a partial pull, simply rerun it, it will start where it"
-" left off.\n"
-"If you are in a hurry, use the non-anonymous access."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:105
-#, python-format
-msgid ""
-"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
-#, python-format
-msgid ""
-"A long explanation about using monotone is available on the monotone page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
-#, python-format
-msgid ""
-"To compile the code, you need the Sun Java Development Kit 6 or higher, "
-"or equivalent JDK\n"
-"(Sun JDK 6 strongly recommended) and\n"
-"Apache ant\n"
-"version 1.7.0 or higher.\n"
-"If you go are working on the main I2P code, you can go into the i2p.i2p "
-"directory and run 'ant' to see the build options."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
-msgid ""
-"To build or work on console translations, you need\n"
-"the xgettext, msgfmt, and msgmerge tools from the\n"
-"GNU gettext package."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
-#, python-format
-msgid ""
-"For development on new applications,\n"
-"see the application development guide."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
-#, python-format
-msgid ""
-"See zzz's TODO lists,\n"
-"this website's TODO list or\n"
-"Trac\n"
-"for ideas."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
-#, python-format
-msgid ""
-"See the bottom of the licenses page "
-"for\n"
-"commit privilege requirements. You need these to put code into i2p.i2p "
-"(not required for the website!)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
-msgid "Short version of how to generate and use keys if you plan to commit:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
-msgid "use an empty passphrase"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
-msgid "enter a passphrase"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
-#, python-format
-msgid ""
-"send this to a mtn repo operator to get "
-"push privileges"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
-#, python-format
-msgid ""
-"send this to a release manager to get "
-"commit privileges - not required for website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
-msgid "check in with this key"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
-msgid "push with this key"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
-#, python-format
-msgid "Long version: see the monotone page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
-#, python-format
-msgid ""
-"The developers hang around on IRC. They can be reached on the Freenode "
-"network, OFTC, and on the I2P internal networks. The usual place to look "
-"is #i2p-dev. Join the channel and say hi!\n"
-"We also have additional guidelines for regular"
-" developers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
-#, python-format
-msgid ""
-"Website and router console translators: See the New Translator's Guide\n"
-"for next steps."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
-msgid ""
-"I2P is open source software that is mostly developed using open sourced\n"
-"toolkits. The I2P project recently acquired a license for the YourKit "
-"Java\n"
-"Profiler. Open source projects are eligible to receive a free license "
-"provided\n"
-"that YourKit is referenced on the project web site. Please get in touch "
-"if you\n"
-"are interested in profiling the I2P codebase."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
-#, python-format
-msgid ""
-"YourKit is kindly supporting open source projects with its full-featured "
-"Java Profiler.\n"
-"YourKit, LLC is the creator of innovative and intelligent tools for "
-"profiling\n"
-"Java and .NET applications. Take a look at YourKit's leading software "
-"products:\n"
-"YourKit Java Profiler and\n"
-"YourKit .NET Profiler."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
-msgid "Here's a very quick guide to getting started."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
-msgid "How to Translate the Website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
-#, python-format
-msgid ""
-"Translation of the website is done with .po files. The easiest way by far"
-" to\n"
-"translate the website is to sign up for an account at \n"
-"Transifex and request to join a translation"
-" team. \n"
-"Alternatively it can be done \"the old way\" as outlined below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
-msgid "Preparation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
-#, python-format
-msgid ""
-"Come to #i2p-dev on irc and talk to people.\n"
-"Claim the language -\n"
-"To make sure other coworkers don't bump onto the files you are working "
-"on,\n"
-"please update the translation status on this wiki "
-"page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
-#, python-format
-msgid ""
-"Follow the new developer's guide,\n"
-"Including the installation of monotone,\n"
-"checking out i2p.www branch, and generate your own monotone keys.\n"
-"It is not required that you sign a dev agreement."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
-msgid ""
-"Create files:\n"
-"If the file for your language does not exist yet:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
-msgid ""
-"Run \"./extract-messages.sh\" to generate a "
-"messages.pot in the base directory.\n"
-"Edit the header of this file, then run \"./init-new-po.sh "
-"locale\" to generate the file\n"
-"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
-"\"mtn add\" this file."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
-msgid ""
-"Edit i2p2www/pages/global/lang.html and add a line for your "
-"language (copy an existing line)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
-msgid ""
-"Add a flag image file to i2p2www/static/images/flags/ for "
-"the menu (copy from the router)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
-msgid ""
-"Edit files:\n"
-"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
-"To work with .po files efficiently, you may wish to use POEdit"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
-msgid ""
-"Check in:\n"
-"\"mtn pull\", \"mtn update\". Then check in by "
-"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
-"This collects the diff info of your changed file into your local repo. "
-"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
-"i2p.i2p\".\n"
-"This synchronizes your local repo with the repo on the target machine."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
-msgid "Repeat. Check in often. Don't wait until it is perfect."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
-msgid "How to Translate the Router Console"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
-#, python-format
-msgid ""
-"The easiest way by far to translate the router console is to sign up for "
-"an account at \n"
-"Transifex and request to join a translation"
-" team. \n"
-"Alternatively it can be done \"the old way\" as outlined below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
-#, python-format
-msgid ""
-"Follow the new developer's guide,\n"
-"including the installation of monotone and the gettext tools,\n"
-"checking out i2p.i2p branch, and generate your own monotone keys."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
-msgid "Generate your own gpg key and sign the dev agreement."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
-msgid ""
-"Before starting a console translation, better help translate some i2p "
-"webpages first.\n"
-"At least an i2p homepage in your language would be great."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
-msgid ""
-"What to translate:\n"
-"There are about 15 files in the i2p.i2p branch that needs translation:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
-msgid ""
-"Where xx is your language code like fr/de/ch/zh/...\n"
-"There may be or may not be files with your lang code. If not, you can "
-"create your own. by copying and renaming other language files you know "
-"with your own lang code."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
-msgid ""
-"Create files:\n"
-"If the file for your language does not exist yet, copy another language "
-"file to a new file foo_xx.bar for your language.\n"
-"Then \"mtn add\" the file.\n"
-"After creating a .po file, edit the headers. Then run \"ant "
-"distclean poupdate\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
-msgid ""
-"Start to work:\n"
-"Edit the HTML files with any text editor.\n"
-"Be sure not to use an editor in HTML mode that reformats everything.\n"
-"To work with .po files efficiently, you may wish to use POEdit"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
-msgid ""
-"As you can see, it's not that difficult.\n"
-"If you have questions about the meaning of the terms in the console, ask "
-"in #i2p-dev on IRC."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
-msgid ""
-"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
-"and html, etc.? Why can't I just do a translation and email it to you?"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
-msgid "A: Several reasons:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
-#, python-format
-msgid ""
-"You might be interested in translating via Transifex. Request to join a "
-"translation team here."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
-msgid ""
-"We don't have anybody who has time to accept manual contributions and "
-"submit them to our source control system on your behalf. Even if we did, "
-"it doesn't scale."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
-msgid ""
-"Maybe you are thinking translation is a one-step process. It isn't. You "
-"can't do it all at once. You will make mistakes. You need to test it and "
-"tweak it to make it look right before you submit it. Developers "
-"will update or add to the English text, thus requiring a translation "
-"update."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
-msgid ""
-"Having translators use a source control system directly provides "
-"authentication and accountablility - we know who is doing what, and we "
-"can track changes, and revert them if necessary."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
-msgid ""
-".po files are not difficult. If you don't want to work directly with "
-"them, we recommend 'poedit'."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
-msgid ""
-"HTML files are not difficult. Just ignore the html stuff and translate "
-"the text."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
-msgid ""
-"Installing and using monotone is not that difficult. Several of the "
-"translators and other contributors to I2P are non-programmers, and they "
-"use monotone regularly. Monotone is simply a source control system, it is"
-" not about \"coding\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
-msgid ""
-"Our items to translate are not \"documents\". They are html files and po "
-"files, with a specific format and character encoding (UTF-8) that must be"
-" maintained, and not corrupted by email programs or other methods of "
-"transfer."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
-msgid ""
-"We looked at 'pootle' as a front-end for translators. It didn't work "
-"well, needed an administrator, and a pootle-based process would suffer "
-"from a number of the above flaws."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
-msgid ""
-"In summary:\n"
-"Yes, we know it is somewhat of a hurdle to get started. It's really the "
-"only possible way we can do it. Give it a try, it really isn't that hard."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
-msgid "More Information"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
-#, python-format
-msgid ""
-"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
-msgstr ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: i2p2www/pages/site/misc/transition-guide.html:21
-msgid "Guide"
-msgstr ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:44
-msgid "Click \"Save\""
-msgstr ""
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:51
-msgid "Add the following line:"
-msgstr ""
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:55
-msgid "Click \"Apply\""
-msgstr ""
-
-#: 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 ""
-
-#: i2p2www/pages/site/research/index.html:2
-msgid "Academic Research"
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:4
-msgid ""
-"Academic research and analysis of I2P is an important part of ensuring "
-"that the software and network performs as expected and is safe for users "
-"in hostile environments."
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:8
-msgid ""
-"I2P can be run as a separate test network by controlling the locations "
-"that a new router reseeds from so that it only finds other test routers. "
-"Additionally, the router can be run on its own in a virtual network mode "
-"to enable testing the router in isolation; to enable this mode, add "
-"i2p.vmCommSystem=true to the router.config before starting."
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:12
-#, python-format
-msgid ""
-"If you are planning on conducting research on the live I2P network, "
-"please contact us before you commence your "
-"testing. While we do not discourage researchers from responsibly testing "
-"their ideas on the live network, if an attack becomes apparent and we "
-"don't have any line of communication then we will end up taking "
-"countermeasures which could interfere with the test."
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:16
-msgid "Prior Research"
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:18
-#, python-format
-msgid ""
-"A list of known published papers about I2P is available here."
-msgstr ""
-
-#: i2p2www/pages/site/research/papers.html:6
-msgid "Following are links to research papers about I2P."
-msgstr ""
-
-#: i2p2www/pages/site/research/papers.html:12
-msgid "Newest links are at the top of the page."
-msgstr ""
-
-#: i2p2www/pages/site/research/papers.html:17
-msgid "Papers and Research"
-msgstr ""
-
diff --git a/i2p2www/translations/fr/LC_MESSAGES/get-involved.po b/i2p2www/translations/fr/LC_MESSAGES/get-involved.po
new file mode 100644
index 00000000..a51a1241
--- /dev/null
+++ b/i2p2www/translations/fr/LC_MESSAGES/get-involved.po
@@ -0,0 +1,4288 @@
+# French translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Boxoa590, 2013
+# magma , 2011
+# syl_, 2013
+# Towatowa441, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-12-06 12:25+0000\n"
+"Last-Translator: syl_\n"
+"Language-Team: French "
+"(http://www.transifex.com/projects/p/I2P/language/fr/)\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/get-involved/donate.html:2
+#: i2p2www/pages/site/get-involved/index.html:77
+msgid "Donate"
+msgstr "Faire un don"
+
+#: i2p2www/pages/site/get-involved/donate.html:4
+msgid ""
+"Thank you for your interest in contributing to I2P!\n"
+"The details of how you\n"
+"can make your contribution are provided below."
+msgstr ""
+"Nous vous remercions de votre intérêt à contribuer à I2P ! \n"
+"Les détails sur la façon dont vous\n"
+"pouvez faire votre contribution sont fournies ci-dessous."
+
+#: i2p2www/pages/site/get-involved/donate.html:11
+#: i2p2www/pages/site/get-involved/donate.html:27
+#, python-format
+msgid ""
+"As of %(date)s, eche|on has been running a\n"
+"%(cointype)s account for the I2P project.\n"
+"If you'd like to donate using %(cointype)s, just transfer your\n"
+"desired amount of coins to the account %(account)s\n"
+"and leave eche|on a note if you'd like your donation to be\n"
+"mentioned on the I2P webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:22
+#: i2p2www/pages/site/get-involved/donate.html:38
+msgid "For easy usage, use the QR code below!"
+msgstr "Pour une utilisation facile, utilisez le code QR ci-dessous !"
+
+#: i2p2www/pages/site/get-involved/donate.html:44
+#, python-format
+msgid "You can donate direct via PayPal to the account \"%(account)s\"."
+msgstr ""
+"Vous pouvez faire un don directement via PayPal vers le compte "
+"\"%(account)s\"."
+
+#: i2p2www/pages/site/get-involved/donate.html:50
+msgid "One time donation:"
+msgstr "Donation en une fois :"
+
+#: i2p2www/pages/site/get-involved/donate.html:64
+msgid "Donate 10 €/month for 12 months:"
+msgstr "Donner 10 €/mois pendant 12 mois:"
+
+#: i2p2www/pages/site/get-involved/donate.html:72
+#: i2p2www/pages/site/get-involved/donate.html:84
+#: i2p2www/pages/site/get-involved/donate.html:96
+#: i2p2www/pages/site/get-involved/donate.html:108
+msgid "I2P donation "
+msgstr "Donation I2P"
+
+#: i2p2www/pages/site/get-involved/donate.html:78
+msgid "Donate 20 €/month for 12 months:"
+msgstr "Donner 20 €/mois pendant 12 mois:"
+
+#: i2p2www/pages/site/get-involved/donate.html:90
+msgid "Donate 30 €/month for 12 months:"
+msgstr "Donner 30 €/mois pendant 12 mois:"
+
+#: i2p2www/pages/site/get-involved/donate.html:102
+msgid "Donate 50 €/month for 12 months:"
+msgstr "Donner 50 €/mois pendant 12 mois:"
+
+#: i2p2www/pages/site/get-involved/donate.html:117
+msgid "Flattr this"
+msgstr "Flattr ceci"
+
+#: i2p2www/pages/site/get-involved/donate.html:122
+msgid ""
+"If you want to keep more or less anonymous, the option to send money via "
+"mail is also available. But it is less secure\n"
+"as the envelope can be lost on the way to us."
+msgstr ""
+"Si vous voulez rester plus ou moins anonyme, la possibilité d'envoyer de "
+"l'argent par courrier postal est également disponible. Mais il est moins "
+"sûr \n"
+"car l'enveloppe peut être perdue sur le chemin vers nous."
+
+#: i2p2www/pages/site/get-involved/donate.html:126
+#, python-format
+msgid ""
+"If you'd like to donate via  snail mail, send an email to %(email)s\n"
+" and you'll receive an email with instructions detailing how to proceed."
+msgstr ""
+"Si vous souhaitez faire un don par courrier postal, envoyer un courriel à"
+" %(email)s\n"
+"et vous recevrez un courriel avec des instructions expliquant comment "
+"procéder."
+
+#: i2p2www/pages/site/get-involved/donate.html:131
+#, python-format
+msgid ""
+"In the meantime, feel free to take a look at the generous donations that "
+"have been\n"
+"given in support of the I2P Project at the hall of fame."
+msgstr ""
+"En attendant, n'hésitez pas à jeter un oeil à aux généreux dons qui ont "
+"été\n"
+"fournis en appui au projet I2P, dans le temple de la renommée"
+
+#: i2p2www/pages/site/get-involved/index.html:2
+msgid "Get Involved!"
+msgstr "Impliquez-vous !"
+
+#: i2p2www/pages/site/get-involved/index.html:4
+msgid "We need your help!"
+msgstr "Nous avons besoin de votre aide !"
+
+#: i2p2www/pages/site/get-involved/index.html:5
+msgid ""
+"To get involved, please feel free to join us on the #i2p IRC channel (on\n"
+"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or "
+"irc.postman.i2p)."
+msgstr ""
+"Pour vous impliquer, n'hésitez pas à nous rejoindre sur le canal IRC #i2p"
+" (sur\n"
+"irc.freenode.net, ou dans I2P sur irc.freshcoffee.i2p ou irc.postman.i2p)."
+
+#: i2p2www/pages/site/get-involved/index.html:9
+#, python-format
+msgid ""
+"If you're interested in joining our team, please"
+" get in\n"
+"touch as we're always looking for eager contributors!"
+msgstr ""
+"Si vous êtes intéressé à vous joindre à notre équipe, veuillez entrer\n"
+"en contact car nous sommes toujours à la recherche de collaborateurs "
+"enthousiastes !"
+
+#: i2p2www/pages/site/get-involved/index.html:13
+msgid ""
+"We need help in many areas, and you don't need to know Java to "
+"contribute!\n"
+"Here's a list to help you get started!"
+msgstr ""
+"Nous avons besoin d'aide dans de nombreux domaines, et vous n'avez pas "
+"besoin de connaître Java pour contribuer !\n"
+"Voici une liste pour vous aider à démarrer !"
+
+#: i2p2www/pages/site/get-involved/index.html:18
+msgid "Spread the Word!"
+msgstr "Passez le mot !"
+
+#: i2p2www/pages/site/get-involved/index.html:19
+msgid ""
+"Tell people about I2P on forums, blogs, and comments to articles.\n"
+"Fix up the Wikipedia article about I2P in your language.\n"
+"Tell your friends."
+msgstr ""
+"Informer les gens au sujet de I2P sur des forums, blogs et des "
+"commentaires à des articles.\n"
+"Complétez l'article de Wikipedia concernant I2P dans votre langue.\n"
+"Dites à vos amis."
+
+#: i2p2www/pages/site/get-involved/index.html:24
+msgid "Testing"
+msgstr "Tester"
+
+#: i2p2www/pages/site/get-involved/index.html:25
+#, python-format
+msgid ""
+"Run the latest builds from monotone\n"
+"and report results on #i2p or as bugs on Trac."
+msgstr ""
+"Exécutez les dernières builds depuis monotone\n"
+"et rapportez les résultats sur #i2p ou comme bugs dans Trac."
+
+#: i2p2www/pages/site/get-involved/index.html:30
+msgid "Documentation"
+msgstr "Documentation"
+
+#: i2p2www/pages/site/get-involved/index.html:31
+msgid ""
+"Help fix the parts of the website that are outdated or incomplete.\n"
+"Translate pages into other languages."
+msgstr ""
+"Aider à réparer les parties du site qui ne sont pas à jour ou "
+"incomplètes.\n"
+"Traduisez des pages dans d'autres langues."
+
+#: i2p2www/pages/site/get-involved/index.html:35
+msgid "Pictures"
+msgstr "Images"
+
+#: i2p2www/pages/site/get-involved/index.html:36
+msgid "Make some more pictures, fix the old ones on the website"
+msgstr "Faites davantage d'images, corrigez les anciennes sur le site"
+
+#: i2p2www/pages/site/get-involved/index.html:39
+msgid "Content"
+msgstr "Contenu"
+
+#: i2p2www/pages/site/get-involved/index.html:40
+msgid "Make an eepsite! Add some content! Contribute to the community!"
+msgstr ""
+"Faites un eepsite ! Ajoutez un peu de contenu ! Contribuez à la "
+"communauté !"
+
+#: i2p2www/pages/site/get-involved/index.html:43
+msgid "Services"
+msgstr "Services"
+
+#: i2p2www/pages/site/get-involved/index.html:44
+msgid ""
+"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n"
+"a naming service, a search engine, an eepsite monitor... many of these\n"
+"aren't that hard."
+msgstr ""
+"Faites tourner un service sur un eepsite. Cela pourrait être un proxy, un"
+" forum, un traqueur,\n"
+"un service de nommage, un moteur de recherche, un moniteur de eepsite ..."
+" beaucoup de ceux-ci\n"
+"ne sont pas si difficiles que cela."
+
+#: i2p2www/pages/site/get-involved/index.html:49
+msgid "Applications"
+msgstr "Applications"
+
+#: i2p2www/pages/site/get-involved/index.html:50
+#, python-format
+msgid ""
+"Write or port applications for I2P! There's some guidelines and\n"
+"a list of ideas on the applications page."
+msgstr ""
+"Écrivez ou portez des applications vers I2P ! Il y a quelques directives "
+"et\n"
+"une liste d'idées sur la page des applications."
+
+#: i2p2www/pages/site/get-involved/index.html:54
+msgid "Coding"
+msgstr "Programmation"
+
+#: i2p2www/pages/site/get-involved/index.html:55
+#, python-format
+msgid ""
+"There's plenty to do if you know Java or are ready to learn.\n"
+"Check for open tickets on Trac\n"
+"or the TODO list on %(zzz)s for\n"
+"some ideas on where to start.\n"
+"See the new developer's guide for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:64
+msgid "Translation"
+msgstr "Traduction"
+
+#: i2p2www/pages/site/get-involved/index.html:65
+#, python-format
+msgid ""
+"Help translate the website and the software into your language.\n"
+"See the new translator's guide for details."
+msgstr ""
+"Aidez à traduire le site et le logiciel dans votre langue. \n"
+"Consultez le guide du nouveau traducteur "
+"pour des détails."
+
+#: i2p2www/pages/site/get-involved/index.html:69
+msgid "Analysis"
+msgstr "Analyse"
+
+#: i2p2www/pages/site/get-involved/index.html:70
+#, python-format
+msgid ""
+"Study or test the code to look for vulnerabilities.\n"
+"Both anonymity vulnerabilities from the various\n"
+"threat models,\n"
+"and DOS and other weaknesses due to securities holes,\n"
+"need researching."
+msgstr ""
+"Étudier ou testez le code afin de chercher des vulnérabilités.\n"
+"Les deux vulnérabilités d'anonymat depuis les différents\n"
+"modèles de menaces,\n"
+"et DOS et d'autres faiblesses dues à des trous de sécurité,\n"
+"ont besoin de recherche."
+
+#: i2p2www/pages/site/get-involved/roadmap.html:2
+msgid "Roadmap"
+msgstr "Feuille de route (roadmap)"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:7
+msgid ""
+"Include some seed data in the distribution so a central reseed location "
+"isn't required?"
+msgstr ""
+"Inclure dans la distribution des données d'amorçage afin qu'un "
+"emplacement de réamorçage central ne soit pas nécessaire ?"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:10
+#, python-format
+msgid ""
+"Reachability Mapping / handle peers partially reachable / enhanced restricted routes"
+msgstr ""
+"Cartographie d'accessibilité / traitement des pairs partiellement "
+"accessible / routes "
+"réservées améliorées"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:13
+msgid "Improve help pages and website"
+msgstr "Améliorer les pages d'aide et le site Web"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:14
+msgid "More translations"
+msgstr "Davantage de tranductions"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:15
+msgid "SSU disconnect message"
+msgstr "Message de déconnexion SSU"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:16
+msgid "Iterative floodfill lookups"
+msgstr "Consultations itérative de la remplissage par diffusion"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:21
+msgid "Full review of anonymity issues and other vulnerabilities"
+msgstr "Examen complet des soucis d'anonymat et des autres fragilités"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:22
+msgid ""
+"Reduce memory usage, remove debugging overhead, make it run better on "
+"slow and embedded machines"
+msgstr ""
+"Réduire l'utilisation de mémoire, enlever le superflu de débogage, le "
+"faire mieux fonctionner sur des machines lentes et incorporées (embedded)"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:25
+msgid "Docs"
+msgstr "Docs"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:30
+msgid "Full restricted routes"
+msgstr "Routes réservées entièrement"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:35
+msgid "Tunnel mixing and padding"
+msgstr "Mixage (mélange) de tunnel et remplissage"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:36
+msgid "User defined message delays"
+msgstr "Retards de message définis par l'utilisateur"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:39
+#, python-format
+msgid ""
+"Please see the TODO list for more detailed info "
+"about some of these tasks."
+msgstr ""
+"Veuillez trouver la liste ÀFAIRE pour des "
+"renseignements plus détaillés sur certaines de ces tâches."
+
+#: i2p2www/pages/site/get-involved/todo.html:2
+msgid "To Do List"
+msgstr "Liste de choses à faire"
+
+#: i2p2www/pages/site/get-involved/todo.html:4
+msgid "I2P Project Targets"
+msgstr "Cibles du projet I2P"
+
+#: i2p2www/pages/site/get-involved/todo.html:5
+#, python-format
+msgid ""
+"Below is a more detailed (yet still incomplete) discussion of the major "
+"areas\n"
+"of future development on the core I2P network, spanning the plausibly "
+"planned\n"
+"releases. This does not include stego transports, porting to wireless "
+"devices,\n"
+"or tools to secure the local machine, nor does it include client "
+"applications\n"
+"that will be essential in I2P's success. There are probably other things "
+"that\n"
+"will come up, especially as I2P gets more peer review, but these are the "
+"main\n"
+"'big things'. See also the roadmap. Want to "
+"help?\n"
+"Get involved!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:54
+msgid "Core functionality"
+msgstr "Fonctionnalité de base"
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:52
+msgid "link"
+msgstr "lien"
+
+#: i2p2www/pages/site/get-involved/todo.html:18
+#: i2p2www/pages/site/get-involved/todo.html:57
+msgid "NAT/Firewall bridging via 1-hop restricted routes"
+msgstr "Pontage NAT/Firewall via des routes restreintes à 1 étape"
+
+#: i2p2www/pages/site/get-involved/todo.html:21
+#: i2p2www/pages/site/get-involved/todo.html:130
+msgid "High degree transport layer with UDP, NBIO, or NIO"
+msgstr "Couche transport de haute niveau avec UDP, NBIO, ou NIO"
+
+#: i2p2www/pages/site/get-involved/todo.html:24
+#: i2p2www/pages/site/get-involved/todo.html:218
+msgid "NetworkDB and profile tuning and ejection policy for large nets"
+msgstr "NetworkDB et réglage de profil et politique d'éjection pour grands réseaux"
+
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:242
+msgid "Security / anonymity"
+msgstr "Sécurité / anonymat"
+
+#: i2p2www/pages/site/get-involved/todo.html:30
+#: i2p2www/pages/site/get-involved/todo.html:245
+msgid ""
+"Per-hop tunnel id & new permuted TunnelVerificationStructure "
+"encryption"
+msgstr ""
+"Id de tunnel par-étape (per-hop) & nouveau chiffrement permuté pour "
+"TunnelVerificationStructure"
+
+#: i2p2www/pages/site/get-involved/todo.html:33
+#: i2p2www/pages/site/get-involved/todo.html:295
+msgid "Strict ordering of participants within tunnels"
+msgstr "Ordonnement strict des participants dans les tunnels"
+
+#: i2p2www/pages/site/get-involved/todo.html:36
+msgid "Randomly permuted tunnel lengths"
+msgstr "Longueurs de tunnel permutées aléatoirement "
+
+#: i2p2www/pages/site/get-involved/todo.html:39
+#: i2p2www/pages/site/get-involved/todo.html:357
+msgid "Full blown n-hop restricted routes with optional trusted links"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:42
+#: i2p2www/pages/site/get-involved/todo.html:376
+msgid "Hashcash for routerIdentity, destination, and tunnel request"
+msgstr "Hashcash pour routerIdentity, destination, et requête de tunnel"
+
+#: i2p2www/pages/site/get-involved/todo.html:45
+#: i2p2www/pages/site/get-involved/todo.html:405
+msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
+msgstr ""
+"Opération avancée de tunnel (traitant par "
+"lot/mixage/étranglement/étoffement)"
+
+#: i2p2www/pages/site/get-involved/todo.html:48
+#: i2p2www/pages/site/get-involved/todo.html:442
+msgid "Stop & go mix w/ garlics & tunnels"
+msgstr "Stop & go mélangé avec tunnels oignon"
+
+#: i2p2www/pages/site/get-involved/todo.html:52
+#: i2p2www/pages/site/get-involved/todo.html:456
+msgid "Performance"
+msgstr "Performance"
+
+#: i2p2www/pages/site/get-involved/todo.html:62
+msgid "Implemented in I2P 0.6.0.6"
+msgstr "Implementé dans I2P 0.6.0.6"
+
+#: i2p2www/pages/site/get-involved/todo.html:63
+msgid ""
+"The functionality of allowing routers to fully participate within the "
+"network \n"
+"while behind firewalls and NATs that they do not control requires some "
+"basic \n"
+"restricted route operation (since those peers will not be able to receive"
+" \n"
+"inbound connections). To do this successfully, you consider peers one of"
+" \n"
+"two ways:"
+msgstr ""
+"La fonctionnalité de permettre à des routeurs de participer entièrement "
+"dans le réseau,\n"
+"tandis qu'ils sont derrière des pare-feu et NATS qu'ils ne contrôlent "
+"pas, exige certaines opérations\n"
+"de la part de routes restreintes basiques (puisque ces pairs ne pourront "
+"pas recevoir\n"
+"des connexions arrivantes). Pour faire ceci avec succès, vous considérez "
+"les pairs de l'une de\n"
+"ces deux façons :"
+
+#: i2p2www/pages/site/get-involved/todo.html:73
+msgid ""
+"Peers who have reachable interfaces - these peers do not need to \n"
+"do anything special"
+msgstr ""
+"Les pairs qui ont des interfaces accessibles - ces pairs n'ont pas"
+" besoin de\n"
+"faire quoi que ce soit de spécial"
+
+#: i2p2www/pages/site/get-involved/todo.html:77
+msgid ""
+"Peers who do not have reachable interfaces - these peers must "
+"build \n"
+"a tunnel pointing at them where the gateway is one of the peers they have"
+" \n"
+"established a connection with who has both a publicly reachable interface"
+" \n"
+"and who has agreed to serve as their 'introducer'."
+msgstr ""
+"Les pairs qui n'ont pas interfaces accessibles - ces pairs doivent"
+" construire\n"
+"un tunnel indiquant à ceux dont la passerelle est un des pairs, qu'ils "
+"ont\n"
+"établi une connexion dont laquelle possède une interface publiquement "
+"accessible\n"
+"et ayant à la fois consenti à leur servir d' 'introducteur'."
+
+#: i2p2www/pages/site/get-involved/todo.html:85
+msgid ""
+"To do this, peers who have no IP address simply connect to a few peers, \n"
+"build a tunnel through them, and publish a reference to those tunnels "
+"within \n"
+"their RouterInfo structure in the network database."
+msgstr ""
+"Pour faire ceci, les pairs qui n'ont aucune adresse IP se connectent "
+"simplement à quelques pairs,\n"
+"construisent un tunnel à travers eux, et publient une référence vers "
+"tunnels dans\n"
+"leur structure RouterInfo dans la base de données de réseau."
+
+#: i2p2www/pages/site/get-involved/todo.html:90
+msgid ""
+"When someone wants to contact any particular router, they first must get"
+" \n"
+"its RouterInfo from the network database, which will tell them whether "
+"they \n"
+"can connect directly (e.g. the peer has a publicly reachable interface) \n"
+"or whether they need to contact them indirectly. Direct connections occur"
+" \n"
+"as normal, while indirect connections are done through one of the "
+"published \n"
+"tunnels."
+msgstr ""
+"Quand quelqu'un veut contacter un routeur particulier, ils doivent "
+"d'abord obtenir\n"
+"son RouterInfo depuis la base de données de réseau, lequel leur dira "
+"s'ils\n"
+"peuvent s'y connecter directement (par exemple le pair a une interface "
+"publiquement accessible) \n"
+"ou s'ils doivent les contacter indirectement. Les connexions directes "
+"arrivent\n"
+"normalement, tandis que les connexions indirectes sont faites à travers "
+"un des\n"
+"tunnels publiés."
+
+#: i2p2www/pages/site/get-involved/todo.html:98
+msgid ""
+"When a router just wants to get a message or two to a specific hidden "
+"peer, \n"
+"they can just use the indirect tunnel for sending the payload. However, \n"
+"if the router wants to talk to the hidden peer often (for instance, as "
+"part \n"
+"of a tunnel), they will send a garlic routed message through the indirect"
+" \n"
+"tunnel to that hidden peer which unwraps to contain a message which "
+"should \n"
+"be sent to the originating router. That hidden peer then establishes an \n"
+"outbound connection to the originating router and from then on, those two"
+" \n"
+"routers can talk to each other directly over that newly established "
+"direct \n"
+"connection."
+msgstr ""
+"Quand un routeur veut juste obtenir un message ou deux à un pair caché "
+"spécifique,\n"
+"ils peuvent juste utiliser le tunnel indirect pour envoyer la charge "
+"utile. Cependant,\n"
+"si le routeur veut parler au pair caché souvent (par exemple, lorsque "
+"faisant partie\n"
+"d'un tunnel), ils enverront le message en oignon acheminé à travers le "
+"tunnel indirect\n"
+"vers ce pair caché lequel déroule pour contenir un message qui devrait\n"
+"être envoyé au routeur originaire. Ce pair caché établit alors une\n"
+"connexion en partance vers le routeur étant originaire et à partir de là,"
+" ces deux\n"
+"routeurs peuvent parler l'un à l'autre directement au moyen de cette "
+"connexion directe\n"
+"nouvellement établie."
+
+#: i2p2www/pages/site/get-involved/todo.html:109
+msgid ""
+"Of course, that only works if the originating peer can receive "
+"connections \n"
+"(they aren't also hidden). However, if the originating peer is hidden, "
+"they \n"
+"can simply direct the garlic routed message to come back to the "
+"originating \n"
+"peer's inbound tunnel."
+msgstr ""
+"Bien sûr, cela ne marche seulement que si le pair peut recevoir des "
+"connexions\n"
+"(si elles ne sont pas cachées elles aussi). Cependant, si le pair étant "
+"originaire est caché, elles\n"
+"peuvent simplement diriger le message acheminé oignon de façon à revenir "
+"au\n"
+"tunnel arrivant du pair originaire."
+
+#: i2p2www/pages/site/get-involved/todo.html:115
+msgid ""
+"This is not meant to provide a way for a peer's IP address to be "
+"concealed, \n"
+"merely as a way to let people behind firewalls and NATs fully operate "
+"within \n"
+"the network. Concealing the peer's IP address adds a little more work, as"
+" \n"
+"described below."
+msgstr ""
+"Ceci n'est pas pensé pas fournir un chemin pour une adresse IP d'un pair "
+"à dissimuler,\n"
+"simplement comme une façon de laisser les gens derrière des pare-feu et "
+"NATs à opérer\n"
+"entièrement dans le réseau. Dissimuler l'adresse IP du pair ajoute un peu"
+" plus de travail, comme\n"
+"décrit ci-dessus."
+
+#: i2p2www/pages/site/get-involved/todo.html:121
+msgid ""
+"With this technique, any router can participate as any part of a tunnel."
+" \n"
+"For efficiency purposes, a hidden peer would be a bad choice for an "
+"inbound \n"
+"gateway, and within any given tunnel, two neighboring peers wouldn't want"
+" \n"
+"to be hidden. But that is not technically necessary."
+msgstr ""
+"Avec cette technique, n'importe quel routeur peut participer comme "
+"n'importe quelle partie d'un tunnel.\n"
+"Pour des buts d'efficacité, un pair caché serait un mauvais choix pour "
+"une passerelle arrivante,\n"
+"et dans n'importe quel tunnel donné, deux pairs voisins ne voudraient pas"
+"\n"
+"être cachés. Mais ce n'est pas nécessaire techniquement."
+
+#: i2p2www/pages/site/get-involved/todo.html:133
+msgid "Both UDP and NIO have been Implemented in I2P"
+msgstr "À la fois UDP et NIO ont étés mis en œuvre dans I2P"
+
+#: i2p2www/pages/site/get-involved/todo.html:134
+msgid ""
+"Standard TCP communication in Java generally requires blocking socket \n"
+"calls, and to keep a blocked socket from hanging the entire system, those"
+" \n"
+"blocking calls are done on their own threads. Our current TCP transport \n"
+"is implemented in a naive fashion - for each peer we are talking to, we \n"
+"have one thread reading and one thread writing. The reader thread simply"
+" \n"
+"loops a bunch of read() calls, building I2NP messages and adding them \n"
+"to our internal inbound message queue, and the writer thread pulls "
+"messages \n"
+"off a per-connection outbound message queue and shoves the data through \n"
+"write() calls."
+msgstr ""
+"La communication TCP standard dans Java exige généralement de bloquer des"
+" appels\n"
+"socket, et d'empêcher une socket bloquée d'accrocher le système entier, "
+"ces\n"
+"appels de blocages sont faits sur leurs propres threads. Notre couche "
+"transport TCP actuelle\n"
+"est mise en œuvre d'une façon naïve - pour chaque pair auquel nous "
+"parlons, nous \n"
+"avons une thread de lecture et une thread d'une écriture. La thread de "
+"lecture boucle simplement\n"
+"une liasse d'apples read(), ceci construisant des messages I2NP et les "
+"ajoutant\n"
+"à notre file d'attente interne de messages arrivants, et la thread "
+"d'écriture tire des messages\n"
+"d'un queue de message en partance par connexion, et pousse les données "
+"via\n"
+"des appels write()."
+
+#: i2p2www/pages/site/get-involved/todo.html:145
+msgid ""
+"We do this fairly efficiently, from a CPU perspective - at any time, \n"
+"almost all of these threads are sitting idle, blocked waiting for "
+"something \n"
+"to do. However, each thread consumes real resources (on older Linux "
+"kernels, \n"
+"for instance, each thread would often be implemented as a fork()'ed "
+"process). \n"
+"As the network grows, the number of peers each router will want to talk \n"
+"with will increase (remember, I2P is fully connected, meaning that any \n"
+"given peer should know how to get a message to any other peer, and "
+"restricted \n"
+"route support will probably not significantly reduce the number of "
+"connections \n"
+"necessary). This means that with a 100,000 router network, each router \n"
+"will have up to 199,998 threads just to deal with the TCP connections!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:157
+msgid ""
+"Obviously, that just won't work. We need to use a transport layer that \n"
+"can scale. In Java, we have two main camps:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:162
+#, python-format
+msgid ""
+"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:165
+msgid ""
+"Sending and receiving UDP datagrams is a connectionless operation - if \n"
+"we are communicating with 100,000 peers, we simply stick the UDP packets"
+" \n"
+"in a queue and have a single thread pulling them off the queue and "
+"shoving \n"
+"them out the pipe (and to receive, have a single thread pulling in any \n"
+"UDP packets received and adding them to an inbound queue)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:172
+msgid ""
+"However, moving to UDP means losing the benefits of TCP's ordering, "
+"congestion \n"
+"control, MTU discovery, etc. Implementing that code will take significant"
+" \n"
+"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n"
+"a while ago I was taking some measurements in the simulator and on the \n"
+"live net, and the vast majority of messages transferred would fit easily"
+" \n"
+"within a single unfragmented UDP packet, and the largest of the messages"
+" \n"
+"would fit within 20-30 packets. As mule pointed out, TCP adds a "
+"significant \n"
+"overhead when dealing with so many small packets, as the ACKs are within"
+" \n"
+"an order of magnitude in size. With UDP, we can optimize the transport \n"
+"for both efficiency and resilience by taking into account I2P's "
+"particular \n"
+"needs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:185
+msgid "It will be a lot of work though."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:188
+msgid "NIO or NBIO"
+msgstr "NIO ou NBIO"
+
+#: i2p2www/pages/site/get-involved/todo.html:189
+msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")"
+msgstr "NIO implémenté dans I2P 0.6.1.22 (\"NTCP\")"
+
+#: i2p2www/pages/site/get-involved/todo.html:192
+msgid ""
+"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java"
+" \n"
+"developers to take advantage of the operating system's nonblocking IO \n"
+"capabilities - allowing you to maintain a large number of concurrent IO \n"
+"operations without requiring a separate thread for each. There is much \n"
+"promise with this approach, as we can scalable handle a large number of \n"
+"concurrent connections and we don't have to write a mini-TCP stack with \n"
+"UDP. However, the NIO packages have not proven themselves to be battle-"
+"ready, \n"
+"as the Freenet developer's found. In addition, requiring NIO support "
+"would \n"
+"mean we can't run on any of the open source JVMs like Kaffe, \n"
+"as GNU/Classpath has only "
+"limited \n"
+"support for NIO. (note: this may not be the case anymore, as there \n"
+"has been some progress on Classpath's NIO, but it is an unknown "
+"quantity)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:206
+#, python-format
+msgid ""
+"Another alternative along the same lines is the Non"
+" \n"
+"Blocking I/O package - essentially a cleanroom NIO implementation \n"
+"(written before NIO was around). It works by using some native OS code \n"
+"to do the nonblocking IO, passing off events through Java. It seems to \n"
+"be working with Kaffe, though there doesn't seem to be much development \n"
+"activity on it lately (likely due to 1.4's NIO deployment)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:221
+msgid ""
+"Within the current network database and profile management "
+"implementation, \n"
+"we have taken the liberty of some practical shortcuts. For instance, we \n"
+"don't have the code to drop peer references from the K-buckets, as we \n"
+"don't have enough peers to even plausibly fill any of them, so instead, \n"
+"we just keep the peers in whatever bucket is appropriate. Another example"
+" \n"
+"deals with the peer profiles - the memory required to maintain each "
+"peer's \n"
+"profile is small enough that we can keep thousands of full blown profiles"
+" \n"
+"in memory without problems. While we have the capacity to use trimmed \n"
+"down profiles (which we can maintain 100s of thousands in memory), we \n"
+"don't have any code to deal with moving a profile from a \"minimal "
+"profile\" \n"
+"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to"
+" simply \n"
+"eject a profile altogether. It just wouldn't be practical to write that \n"
+"code yet, since we aren't going to need it for a while."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:236
+msgid ""
+"That said, as the network grows we are going to want to keep these "
+"considerations \n"
+"in mind. We will have some work to do, but we can put it off for later."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:248
+#: i2p2www/pages/site/get-involved/todo.html:332
+#, python-format
+msgid ""
+"Addressed in I2P 0.5 as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:251
+msgid ""
+"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n"
+"going to Dave, then to Charlie, then Bob, and finally Alice "
+"(A<--B<--C<--D<--E), \n"
+"all five of them will know they are participating in tunnel \"123\", as \n"
+"the messages are tagged as such. What we want to do is give each hop "
+"their \n"
+"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n"
+"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n"
+"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n"
+"the tunnel had the same tunnel ID, collusion attacks aren't much work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:261
+msgid ""
+"Adding a unique tunnel ID per hop isn't hard, but by itself, "
+"insufficient. \n"
+"If Dave and Bob are under the control of the same attacker, they wouldn't"
+" \n"
+"be able to tell they are in the same tunnel due to the tunnel ID, but \n"
+"would be able to tell by the message bodies and verification structures \n"
+"by simply comparing them. To prevent that, the tunnel must use layered \n"
+"encryption along the path, both on the payload of the tunneled message \n"
+"and on the verification structure (used to prevent simple tagging "
+"attacks). \n"
+"This requires some simple modifications to the TunnelMessage, as well \n"
+"as the inclusion of per-hop secret keys delivered during tunnel creation"
+" \n"
+"and given to the tunnel's gateway. We must fix a maximum tunnel length \n"
+"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n"
+"of the 16 delivered secret keys, in reverse order, and to encrypt the \n"
+"signature of the hash of the (encrypted) payload at each step. The "
+"gateway \n"
+"then sends that 16-step encrypted message, along with a 16-step and "
+"16-wide \n"
+"encrypted mapping to the first hop, which then decrypts the mapping and \n"
+"the payload with their secret key, looking in the 16-wide mapping for \n"
+"the entry associated with their own hop (keyed by the per-hop tunnel ID)"
+" \n"
+"and verifying the payload by checking it against the associated signed \n"
+"hash."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:282
+msgid ""
+"The tunnel gateway does still have more information than the other peers"
+" \n"
+"in the tunnel, and compromising both the gateway and a tunnel participant"
+" \n"
+"would allow those peers to collude, exposing the fact that they are both"
+" \n"
+"in the same tunnel. In addition, neighboring peers know that they are \n"
+"in the same tunnel anyway, as they know who they send the message to (and"
+" \n"
+"with IP-based transports without restricted routes, they know who they \n"
+"got it from). However, the above two techniques significantly increase \n"
+"the cost of gaining meaningful samples when dealing with longer tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:298
+msgid "Implemented in release 0.6.2"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:301
+#, python-format
+msgid ""
+"As Connelly proposed to deal with the\n"
+"predecessor attack (2008\n"
+"update), keeping the order of peers within our tunnels consistent \n"
+"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n"
+"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n"
+"get to substantially sample Alice's peer selection group. We may even \n"
+"want to explicitly allow Bob to participate in Alice's tunnels in only \n"
+"one way - receiving a message from Dave and sending it to Charlie - and \n"
+"if any of those peers are not available to participate in the tunnel (due"
+" \n"
+"to overload, network disconnection, etc), avoid asking Bob to participate"
+" \n"
+"in any tunnels until they are back online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:316
+msgid ""
+"More analysis is necessary for revising the tunnel creation - at the \n"
+"moment, we simply select and order randomly within the peer's top tier \n"
+"of peers (ones with fast + high capacity)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:321
+msgid ""
+"Adding a strict ordering to peers in a tunnel also improves the anonymity"
+" \n"
+"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway"
+" \n"
+"is always the same would be particularly damning. However, peers with \n"
+"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n"
+"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n"
+"duration) minutes, use a 1-hop tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:338
+msgid ""
+"Without tunnel length permutation, if someone were to somehow detect that"
+" \n"
+"a destination had a particular number of hops, it might be able to use "
+"that \n"
+"information to identify the router the destination is located on, per the"
+" \n"
+"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n"
+"receives a tunnel message from Charlie and forwards it to Alice, Bob "
+"knows \n"
+"Alice is the final router in the tunnel. If Bob were to identify what "
+"destination \n"
+"that tunnel served (by means of colluding with the gateway and harvesting"
+" \n"
+"the network database for all of the LeaseSets), he would know the router"
+" \n"
+"on which that destination is located (and without restricted routes, that"
+" \n"
+"would mean what IP address the destination is on)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:350
+msgid ""
+"It is to counter user behavior that tunnel lengths should be permuted, \n"
+"using algorithms based on the length requested (for example, the 1/MTBF \n"
+"length change for 0-hop tunnels outlined above)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:360
+msgid ""
+"The restricted route functionality described before was simply a "
+"functional \n"
+"issue - how to let peers who would not otherwise be able to communicate \n"
+"do so. However, the concept of allowing restricted routes includes "
+"additional \n"
+"capabilities. For instance, if a router absolutely cannot risk "
+"communicating \n"
+"directly with any untrusted peers, they can set up trusted links through"
+" \n"
+"those peers, using them to both send and receive all of its messages. \n"
+"Those hidden peers who want to be completely isolated would also refuse \n"
+"to connect to peers who attempt to get them to (as demonstrated by the \n"
+"garlic routing technique outlined before) - they can simply take the "
+"garlic \n"
+"clove that has a request for delivery to a particular peer and tunnel \n"
+"route that message out one of the hidden peer's trusted links with "
+"instructions \n"
+"to forward it as requested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:379
+#, python-format
+msgid ""
+"Within the network, we will want some way to deter people from consuming"
+" \n"
+"too many resources or from creating so many peers to mount a Sybil \n"
+"attack. Traditional techniques such as having a peer see who is "
+"requesting \n"
+"a resource or running a peer aren't appropriate for use within I2P, as \n"
+"doing so would compromise the anonymity of the system. Instead, we want \n"
+"to make certain requests \"expensive\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:387
+msgid ""
+"Hashcash is one technique that \n"
+"we can use to anonymously increase the \"cost\" of doing certain "
+"activities, \n"
+"such as creating a new router identity (done only once on installation),"
+" \n"
+"creating a new destination (done only once when creating a service), or \n"
+"requesting that a peer participate in a tunnel (done often, perhaps 2-300"
+" \n"
+"times per hour). We don't know the \"correct\" cost of each type of "
+"certificate \n"
+"yet, but with some research and experimentation, we could set a base "
+"level \n"
+"that is sufficiently expensive while not an excessive burden for people \n"
+"with few resources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:398
+msgid ""
+"There are a few other algorithms that we can explore for making those \n"
+"requests for resources \"nonfree\", and further research on that front is"
+" \n"
+"appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:408
+#, python-format
+msgid ""
+"To powerful passive external observers as well as large colluding "
+"internal \n"
+"observers, standard tunnel routing is vulnerable to traffic analysis "
+"attacks \n"
+"- simply watching the size and frequency of messages being passed between"
+" \n"
+"routers. To defend against these, we will want to essentially turn some \n"
+"of the tunnels into its own mix cascade - delaying messages received at \n"
+"the gateway and passing them in batches, reordering them as necessary, \n"
+"and injecting dummy messages (indistinguishable from other \"real\" "
+"tunnel \n"
+"messages by peers in the path). There has been a significant amount of \n"
+"research \n"
+"on these algorithms that we can lean on prior to implementing the various"
+" \n"
+"tunnel mixing strategies."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:421
+msgid ""
+"In addition to the anonymity aspects of more varied tunnel operation, \n"
+"there is a functional dimension as well. Each peer only has a certain \n"
+"amount of data they can route for the network, and to keep any particular"
+" \n"
+"tunnel from consuming an unreasonable portion of that bandwidth, they \n"
+"will want to include some throttles on the tunnel. For instance, a tunnel"
+" \n"
+"may be configured to throttle itself after passing 600 messages (1 per \n"
+"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n"
+"last minute). Excess messages may be delayed or summarily dropped. With \n"
+"this sort of throttling, peers can provide ATM-like QoS support for their"
+" \n"
+"tunnels, refusing to agree to allocate more bandwidth than the peer has \n"
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:434
+msgid ""
+"In addition, we may want to implement code to dynamically reroute tunnels"
+" \n"
+"to avoid failed peers or to inject additional hops into the path. This \n"
+"can be done by garlic routing a message to any particular peer in a "
+"tunnel \n"
+"with instructions to redefine the next-hop in the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:445
+msgid ""
+"Beyond the per-tunnel batching and mixing strategy, there are further \n"
+"capabilities for protecting against powerful attackers, such as allowing"
+" \n"
+"each step in a garlic routed path to define a delay or window in which \n"
+"it should be forwarded on. This would enable protections against the long"
+" \n"
+"term intersection attack, as a peer could send a message that looks "
+"perfectly \n"
+"standard to most peers that pass it along, except at any peers where the"
+" \n"
+"clove exposed includes delay instructions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:457
+#, python-format
+msgid ""
+"Performance related improvements are listed on the\n"
+"Performance page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2
+msgid "Bounty Arabic translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3
+#: i2p2www/pages/site/get-involved/bounties/index.html:119
+msgid "Arabic translation"
+msgstr "Traduction en Arabe"
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P echelon set out this bounty for translation\n"
+"of the I2P web page and I2P router console into Arabic."
+msgstr ""
+"Pour améliorer l'utilisation de I2P et attirer davantage de personnes\n"
+"dans I2P, echelon met en place cette prime pour la traduction\n"
+"de la page Web I2P et de la console routeur I2P en Arabe."
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12
+msgid "This bounty is set into 2 subparts:"
+msgstr "Cette prime est composée en 2 sous-parties :"
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14
+msgid "Part 1 is translation of the webpage."
+msgstr "La partie 1 est la traduction de la page Web."
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17
+msgid ""
+"For collecting the bounty of 20 BTC you need to translate the following "
+"pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25
+msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27
+msgid ""
+"Part 2 is the translation of the router console. The router console was\n"
+"partly translated and the bounty of 80 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34
+msgid "Judge is echelon."
+msgstr "Le juge est echelon."
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2
+msgid "Bounty creating a I2P native Bitcoin client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3
+msgid "BTC I2P native client"
+msgstr "Client natif I2P BTC"
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to create a I2P native Bitcoin client. \n"
+"It should integrate with other client via the I2P network and via "
+"gateways to\n"
+"the existant bitcoin network."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15
+msgid "Judge is psychonaut who donated the first 30 € to this bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
+msgid "Bounty datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:3
+msgid "datastore"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:6
+msgid ""
+"To improve I2P's usage and to be independent of routers \n"
+"online status we want a datastorage as a extension to I2P.\n"
+"Like in Freenet the datastorage should be distributed and every\n"
+"participating node should be able to configure his options.\n"
+"The files should be saved in chunks and at least 2-3 times to\n"
+"obtain redundancy. Usage of storage space should be auto balanced.\n"
+"As it is a extra application, it should work flawless within I2P and\n"
+"cooperate nice with the I2P router. Maybe a integration within the\n"
+"webpage/router could be done."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:17
+msgid ""
+"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n"
+"\"eepsites in datastorage\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:21
+msgid ""
+"The frost for I2P datastorage bounty is paid for a frost like program \n"
+"with which files/messages are stored into database and got from database."
+"\n"
+"It needs to work with a GUI."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:26
+msgid ""
+"The eepsite served out of I2P datastorage extends a I2P router to send\n"
+"out eepsites out of the I2P datastorage. All files for eepsites need to "
+"be\n"
+"saved inside of datastorage and are taken from it.\n"
+"Extension:\n"
+"For better integration all datastorage participants could serve that "
+"eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:36
+msgid ""
+"For bounties to be declared done and paid, we need the program AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2
+msgid "Bounty I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3
+msgid "I2P Ubuntu/Debian package"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6
+msgid ""
+"For the future of I2P and in order to attract more people\n"
+"to I2P, this bounty was set for including an I2P package into the Ubuntu "
+"and Debian \n"
+"archive mirrors.\n"
+"To claim this bounty, the I2P router package needs to be available from\n"
+"Ubuntu and Debian archive mirrors and Debian bug \n"
+"448638 \n"
+"needs to be closed successfully."
+msgstr ""
+"Pour l'avenir de I2P et pour attirer plus de personnes\n"
+"à I2P, cette prime-récompense a été mise pour l'inclusion d'un paquet I2P"
+" dans les miroirs d'archives de Ubuntu et de Debian.\n"
+"Pour prétendre à cette prime, le paquet de routeur I2P doit être "
+"disponible depuis\n"
+"les miroirs d'archives de Ubuntu et de Debian et le bogue Debian\n"
+"448638\n"
+"doit être fermé avec succès."
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2
+msgid "Bounty I2PHex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3
+msgid "i2phex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2PHex P2P ArneBab setout the bounty for implementing actual\n"
+"Phex code onto I2PHex."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:2
+msgid "Bounties"
+msgstr "Projets récompensés - bounties"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:5
+msgid "Bounties for I2P"
+msgstr "Primes pour I2P"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:6
+msgid ""
+"While we always gratefully accept any contributions of code, \n"
+"documentation, and the like, there are other ways to help I2P move \n"
+"forward.  As with any open source project, our goals would be achieved "
+"more \n"
+"rapidly if we were able to support all of our contributors to work on \n"
+"I2P full time.  However, as with any open source project, that's not a \n"
+"possibility.  Instead, we are making use of a bounty system, whereby \n"
+"anyone can get support for working on something that people want \n"
+"implemented, and people who want to contribute to I2P can be assured that"
+" \n"
+"their support goes to what they care about."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:18
+msgid ""
+"We are also keeping open the ability for people who want to support I2P \n"
+"but don't have strong feelings about the bounties available.  Those "
+"people\n"
+"can simply put their trust in the I2P team to do what we feel is best by\n"
+"donating to a catch-all general fund that will be used as deemed \n"
+"necessary - allocated to various bounties, covering incidentals (hosting,"
+" \n"
+"etc), and the like."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:27
+msgid "Current bounties"
+msgstr "Primes actuelles"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Name"
+msgstr "Nom"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Status"
+msgstr "Statut"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Judge"
+msgstr "Juge"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Dev"
+msgstr "Dév"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Bounty"
+msgstr "Prime"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:32
+msgid "Frost for I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:33
+#: i2p2www/pages/site/get-involved/bounties/index.html:40
+#: i2p2www/pages/site/get-involved/bounties/index.html:47
+#: i2p2www/pages/site/get-involved/bounties/index.html:54
+#: i2p2www/pages/site/get-involved/bounties/index.html:75
+#: i2p2www/pages/site/get-involved/bounties/index.html:82
+msgid "Proposal in development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:35
+#: i2p2www/pages/site/get-involved/bounties/index.html:42
+#: i2p2www/pages/site/get-involved/bounties/index.html:49
+#: i2p2www/pages/site/get-involved/bounties/index.html:56
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+#: i2p2www/pages/site/get-involved/bounties/index.html:97
+msgid "vacant"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:39
+msgid "Eepsites served out of I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:46
+msgid "Backporting Phex code onto I2PHex"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:53
+msgid "I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:60
+msgid "Bitcoin client for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:61
+msgid "Done, phase of verification"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:67
+msgid "Unit tests and Multi-router Simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:68
+msgid "Partly done, partly in work, partly still open"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:89
+msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:94
+msgid "Bundling bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:95
+msgid "Proposed"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:102
+msgid "Claimed bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:107
+msgid "Make I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:114
+msgid "Setting up a SILC server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:124
+msgid "Datastore over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:129
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
+msgid "Russian translation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:134
+msgid "Swarming file transfer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:139
+msgid "Streaming library window size"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:144
+msgid "IRC connect time monitor"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:149
+msgid "Unit tests (part 1)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:161
+msgid ""
+"Dev lists anyone who may already be working on the bounty - collaboration"
+" is\n"
+"preferred, so if you're interested in working on it, please contact one "
+"of the\n"
+"people listed!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2
+msgid "Bounty I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3
+msgid "native IPv6 I2P"
+msgstr "I2P IPv6 natif"
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n"
+"To claim this bounty, the I2P router needs to run full on native\n"
+"IPv6 connections like it does on IPv4."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:17
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
+msgid ""
+"For bounties to be declared done and paid, we need the plugin AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:2
+msgid "NetDB Backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:3
+msgid "netDB backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:7
+msgid ""
+"The current NetDB implementation (namely the FloodFill system)\n"
+"needs to be extended with another backend to improve reliability,\n"
+"reduce attack surface and solve the scalability issue for the \n"
+"coming years."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:14
+msgid ""
+"A solution likely based on a DHT will be investigated and \n"
+"finally implemented."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2
+msgid "Bounty russian translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P a anonymous donator set out the bounty for translation\n"
+"of the I2P web page and I2P router console into russian language."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17
+msgid ""
+"For collecting the bounty of $115 USD you need to translate the following"
+" pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30
+msgid ""
+"Part 2 is the translation of the router console. The whole router console"
+" needs\n"
+"to be translated to collect the bounty of $115 USD."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37
+msgid "Judge is the russian donor."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:2
+msgid "Bounty migrate I2P IRC to SILC"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:3
+msgid "I2P silc server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:7
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to setup and host a I2P SILC server.   \n"
+"This will allow people to send files over their messaging servers and "
+"have intrinsic security built into the protocol."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:12
+msgid ""
+"A silc server needs to be set up and run for at least 3 month time to get"
+" payed. \n"
+"A second server should be set up, to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:16
+msgid ""
+"Bounty was withdrawn and money donated to returningnovice and general "
+"fund."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:22
+msgid "Judge is An Anonymous Secret Society, society@mail.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3
+msgid "Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7
+msgid ""
+"Beside of I2P we want to encourage users\n"
+"to care more about anonymity and security. As I2P is a low \n"
+"latency network with its natural limits, the software SYNDIE\n"
+"can overcome some of these limits and provide better anonymity\n"
+"for people who really need it."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14
+msgid ""
+"For our bad sake the syndie project was out of development for \n"
+"quite a long time yet (5 years). To get a fresh and new built \n"
+"with needed bugfixes we set out this bounty. Also syndie needs\n"
+"some enhancements and a better GUI for users to work with it.\n"
+"Current bounty sum is 50 Bitcoin."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22
+msgid ""
+"The latest Syndie coding rally did improve the situation of the\n"
+"Syndie package dramatically. A new Syndie package with bugfixes\n"
+"was created and made available on different webpages.\n"
+"As a result of this work, the bounty sum was reduced and\n"
+"the withdrawn money moved to the IPv6 bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2
+msgid "Bounty unittests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3
+msgid "unit test"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7
+msgid ""
+"To improve I2P's maintainability, we want to have a solid set of\n"
+"automated unit tests for the critical code.  While we do have some\n"
+"unit tests at the moment, they are ad-hoc and partly unfinished.  \n"
+"This bounty is for someone to check the existing tests and move over\n"
+"old ones to jUnit, automate their execution, extend them to provide \n"
+"better code coverage, and publish the report online.  Its a massive \n"
+"effort, but can be broken down into phases, listed below (phase 2 \n"
+"must occur first, but further phases may happen in any order).\n"
+"As this needs some reading of code, it is the best start point for\n"
+"new devs to get a good overview of I2P code and coding. A good job\n"
+"for college students, interns or anyone who is just interested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20
+msgid ""
+"Take care! Jobs and bounties shuffled a bit!\n"
+"Phase 6,7 and 8 are still open!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112
+#, python-format
+msgid "Phase %(phase)s:"
+msgstr "Phase %(phase)s:"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27
+msgid "CI jenkins and IRC bot"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114
+#, python-format
+msgid "Bounty: %(euro)s €"
+msgstr "Prime : %(euro)s €"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29
+msgid "server runs and this section is blocked"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31
+msgid ""
+"To collect this bounty, a continuous integration server (Jenkins,\n"
+"old name was Hudson) must be set up and a connected IRC bot needs \n"
+"to set up in the channel #i2p-dev on IRC2p network to print out\n"
+"results of build tests.
            \n"
+"The server needs to be run long term."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41
+msgid "Check existing SDK tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69
+msgid "paid to str4d"
+msgstr "payé à  str4d"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45
+#, python-format
+msgid ""
+"To collect this bounty, the existing SDK tests must be checked \n"
+"and made to work again. The need to be integrated into the ant \n"
+"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g."
+" \n"
+"Clover).  The ant script\n"
+"must be capable of generating test status results as a web page, \n"
+"which will be published online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56
+msgid "SDK test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80
+msgid "paid to unittests dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60
+msgid ""
+"To collect this bounty, the automated unit tests of the SDK \n"
+"(i2p/core/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67
+msgid "Router test migration"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71
+msgid ""
+"As with phase 2, the existing unit tests for the router must be\n"
+"moved over to the automated system."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78
+msgid "Router test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82
+msgid ""
+"To collect this bounty, the automated unit tests of the router \n"
+"(i2p/router/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89
+msgid "Streaming lib tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94
+msgid ""
+"To collect this bounty, a new set of unit tests must meet a \n"
+"measured code coverage of 90% of the streaming lib \n"
+"(i2p/apps/ministreaming/ and i2p/apps/streaming/)."
+msgstr ""
+"Pour rassembler cette prime-récompense, un nouvel ensemble de tests "
+"d'unité doit respecter un e\n"
+"couverture de code mesurée de 90% de la streaming lib\n"
+"(i2p/apps/ministreaming/ et i2p/apps/streaming/)."
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102
+msgid "Unit tests coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106
+msgid ""
+"To collect this bounty, all above unit tests must meet the 100%\n"
+"coverage marker (except for log statements)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113
+msgid "MultiRouter simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115
+msgid "will be split in more sub-tasks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117
+msgid ""
+"To collect this bounty, the existing in-memory multi-router\n"
+"simulation must be checked, made work again and extend to simulate\n"
+"lots of routers in memory on a single machine. This bounty will\n"
+"be split in more fine grained subworks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126
+msgid ""
+"Judge on all these works is the donor and donor decides if a phase is\n"
+"called succesfull done and money can be paid."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2
+msgid "Bounty I2P vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3
+msgid "vuze plugin"
+msgstr "plugin vuze"
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P torrent P2P I setout the bounty for a working I2P vuze\n"
+"plugin.\n"
+"The plugin needs to be official and submitted to vuze for publication\n"
+"on their webpage/repository for plugins.\n"
+"It should be easy to install and configured, work smooth and flawless.\n"
+"Configuration should be friendly to starters and made easy to be "
+"anonymous.\n"
+"It should work with *.b32.i2p destinations as with signed (516++ bits) \n"
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:2
+msgid "Application Development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:3
+msgid "May 2013"
+msgstr "Mai 2013"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:6
+msgid "Application Development Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:8
+msgid "Contents"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:10
+#: i2p2www/pages/site/get-involved/develop/applications.html:16
+msgid "Why write I2P-specific code?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:11
+#: i2p2www/pages/site/get-involved/develop/applications.html:102
+msgid "Important concepts"
+msgstr "Concepts importants"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:12
+#: i2p2www/pages/site/get-involved/develop/applications.html:190
+msgid "Development options"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:13
+#: i2p2www/pages/site/get-involved/develop/applications.html:303
+msgid "Start developing - a simple guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:18
+#, python-format
+msgid ""
+"There are multiple ways to use applications in I2P.\n"
+"Using I2PTunnel,\n"
+"you can use regular applications without needing to program explicit I2P "
+"support.\n"
+"This is very effective for client-server scenario's,\n"
+"where you need to connect to a single website.\n"
+"You can simply create a tunnel using I2PTunnel to connect to that "
+"website, as shown in Figure 1."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:26
+msgid ""
+"If your application is distributed, it will require connections to a "
+"large amount of peers.\n"
+"Using I2PTunnel, you will need to create a new tunnel for each peer you "
+"want to contact,\n"
+"as shown in Figure 2.\n"
+"This process can of course be automated, but running a lot of I2PTunnel "
+"instances creates a large amount of overhead.\n"
+"In addition, with many protocols you will need to force everyone to \n"
+"use the same set of ports for all peers - e.g. if you want to reliably "
+"run DCC \n"
+"chat, everyone needs to agree that port 10001 is Alice, port 10002 is "
+"Bob, port \n"
+"10003 is Charlie, and so on, since the protocol includes TCP/IP specific "
+"information\n"
+"(host and port)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:37
+msgid ""
+"General network applications often send a lot of additional data that "
+"could be used to identify users.\n"
+"Hostnames, port numbers, time zones, character sets, etc. are often sent "
+"without informing the user.\n"
+"As such, designing the network protocol specifically with anonymity in "
+"mind\n"
+"can avoid compromising user identities."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:43
+msgid ""
+"There are also efficiency considerations to review when determining how "
+"to \n"
+"interact on top of I2P.  The streaming library and things built on top of"
+" it\n"
+"operate with handshakes similar to TCP, while the core I2P protocols "
+"(I2NP and I2CP)\n"
+"are strictly message based (like UDP or in some instances raw IP).  The "
+"important\n"
+"distinction is that with I2P, communication is operating over a long fat "
+"network - \n"
+"each end to end message will have nontrivial latencies, but may contain "
+"payloads \n"
+"of up to several KB.  An application that needs a simple request and "
+"response can get rid\n"
+"of any state and drop the latency incurred by the startup and teardown "
+"handshakes\n"
+"by using (best effort) datagrams without having to worry about MTU "
+"detection or \n"
+"fragmentation of messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:57
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid ""
+"Creating a server-client connection using I2PTunnel only requires "
+"creating a single tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid "Figure 1:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:64
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid ""
+"Setting up connections for a peer-to-peer applications requires a very "
+"large amount of tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid "Figure 2:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:70
+msgid "In summary, a number of reasons to write I2P-specific code:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:74
+msgid ""
+"Creating a large amount of I2PTunnel instances consumes a non-trivial "
+"amount of resources,\n"
+"which is problematic for distributed applications (a new tunnel is "
+"required for each peer)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:78
+msgid ""
+"General network protocols often send a lot of additional data that can be"
+" used to identify users.\n"
+"Programming specifically for I2P allows the creation of a network "
+"protocol\n"
+"that does not leak such information, keeping users anonymous and secure."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:83
+msgid ""
+"Network protocols designed for use on the regular internet can be "
+"inefficient\n"
+"on I2P, which is a network with a much higher latency."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:90
+#, python-format
+msgid ""
+"I2P supports a standard plugins interface for"
+" developers\n"
+"so that applications may be easily integrated and distributed."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:96
+msgid ""
+"Applications written in Java and accessible/runnable\n"
+"using an HTML interface via the standard webapps/app.war\n"
+"may be considered for inclusion in the i2p distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:104
+msgid "There are a few changes that require adjusting to when using I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:108
+msgid "Destination ~= host+port"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:110
+msgid ""
+"An application running on I2P sends messages from and receives messages "
+"to a\n"
+"unique cryptographically secure end point - a \"destination\".  In TCP or"
+" UDP\n"
+"terms, a destination could (largely) be considered the equivalent of a "
+"hostname\n"
+"plus port number pair, though there are a few differences."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:118
+msgid ""
+"An I2P destination itself is a cryptographic construct - all data sent to"
+" one is \n"
+"encrypted as if there were universal deployment of IPsec with the "
+"(anonymized)\n"
+"location of the end point signed as if there were universal deployment of"
+" DNSSEC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:123
+msgid ""
+"I2P destinations are mobile identifiers - they can be moved from one I2P "
+"router\n"
+"to another (or it can even \"multihome\" - operate on multiple routers at"
+"\n"
+"once).  This is quite different from the TCP or UDP world where a single "
+"end point (port)\n"
+"must stay on a single host."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:130
+msgid ""
+"I2P destinations are ugly and large - behind the scenes, they contain a "
+"2048 bit ElGamal\n"
+"public key for encryption, a 1024 bit DSA public key for signing, and a "
+"variable size \n"
+"certificate, which may contain proof of work or blinded data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:135
+#, python-format
+msgid ""
+"There are existing ways to refer to these large and ugly destinations by "
+"short\n"
+"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not "
+"guarantee\n"
+"globally uniqueness (since they're stored locally in a database on each "
+"person's machine)\n"
+"and the current mechanism is not especially scalable nor secure (updates "
+"to the host list are\n"
+"managed using \"subscriptions\" to naming services).\n"
+"There may be some secure, human readable, scalable, and globally \n"
+"unique, naming system some day, but applications shouldn't depend upon it"
+" being in place,\n"
+"since there are those who don't think such a beast is possible.\n"
+"Further information on the naming system is "
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:149
+#, python-format
+msgid ""
+"While most applications do not need to distinguish protocols and ports,\n"
+"I2P does support them. Complex applications may specify a "
+"protocol,\n"
+"from port, and to port, on a per-message basis, to multiplex traffic on\n"
+"a single destination.\n"
+"See the datagram page for details.\n"
+"Simple applications operate by listening for \"all protocols\" on \"all "
+"ports\" of a destination."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:158
+msgid "Anonymity and confidentiality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:160
+msgid ""
+"I2P has transparent end to end encryption\n"
+"and authentication for all data passed over the network - if Bob sends to"
+" Alice's destination,\n"
+"only Alice's destination can receive it, and if Bob is using the "
+"datagrams or streaming \n"
+"library, Alice knows for certain that Bob's destination is the one who "
+"sent the data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:167
+msgid ""
+"Of course, I2P transparently anonymizes the\n"
+"data sent between Alice and Bob, but it does nothing to anonymize the "
+"content of what they\n"
+"send.  For instance, if Alice sends Bob a form with her full name, "
+"government IDs, and \n"
+"credit card numbers, there is nothing I2P can do.  As such, protocols and"
+" applications should \n"
+"keep in mind what information they are trying to protect and what "
+"information they are willing\n"
+"to expose."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:176
+msgid "I2P datagrams can be up to several KB"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:178
+#, python-format
+msgid ""
+"Applications that use I2P datagrams (either raw or repliable ones) can "
+"essentially be thought\n"
+"of in terms of UDP - the datagrams are unordered, best effort, and "
+"connectionless - but unlike\n"
+"UDP, applications don't need to worry about MTU detection and can simply "
+"fire off large datagrams.\n"
+"While the upper limit is nominally 32 KB, the message is fragmented for "
+"transport, thus dropping\n"
+"the reliability of the whole. Datagrams over about 10 KB are not "
+"currently recommended.\n"
+"See the datagram page for details.\n"
+"For many applications, 10 KB of data is sufficient for an\n"
+"entire request or response, allowing them to transparently operate in I2P"
+" as a UDP-like \n"
+"application without having to write fragmentation, resends, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:192
+msgid ""
+"There are several means of sending data over I2P, each with their own "
+"pros and cons.\n"
+"The streaming lib is the recommended interface, used by the majority of "
+"I2P applications."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:197
+msgid "Streaming Lib"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:198
+#, python-format
+msgid ""
+"The full streaming library is now the "
+"standard\n"
+"interface. It allows programming using TCP-like sockets, as explained in "
+"the Streaming development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:204
+#, python-format
+msgid ""
+"BOB is the Basic Open Bridge,\n"
+"allowing an application in any language to make streaming connections \n"
+"to and from I2P. At this point in time it lacks UDP support, but UDP "
+"support\n"
+"is planned in the near future. BOB also contains several tools, such as \n"
+"destination key generation, and verification that an address conforms to"
+" \n"
+"I2P specifications. Up to date info and applications that use BOB can be"
+" \n"
+"found at this eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:217
+msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:218
+#, python-format
+msgid ""
+"SAM is the Simple Anonymous Messaging protocol, "
+"allowing an\n"
+"application written in any language to talk to a SAM bridge through a "
+"plain TCP socket and have\n"
+"that bridge multiplex all of its I2P traffic, transparently coordinating "
+"the encryption/decryption\n"
+"and event based handling.  SAM supports three styles of operation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:225
+msgid ""
+"streams, for when Alice and Bob want to send data to each other reliably "
+"and in order"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:228
+msgid ""
+"repliable datagrams, for when Alice wants to send Bob a message that Bob "
+"can reply to"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:231
+msgid ""
+"raw datagrams, for when Alice wants to squeeze the most bandwidth and "
+"performance as possible,\n"
+"and Bob doesn't care whether the data's sender is authenticated or not "
+"(e.g. the data transferred\n"
+"is self authenticating)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:237
+msgid ""
+"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n"
+"multiplexing/demultiplexing. Each I2P stream is handled by its own socket"
+" between the application\n"
+"and the SAM bridge. Besides, datagrams can be sent and received by the "
+"application through datagram\n"
+"communications with the SAM bridge."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:244
+#, python-format
+msgid ""
+"SAM V2 is a new version used by imule\n"
+"that fixes some of the problems in SAM.\n"
+"
            \n"
+"SAM V3 is used by imule since version 1.4.0."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:252
+msgid ""
+"The I2PTunnel application allows applications to build specific TCP-like "
+"tunnels to peers \n"
+"by creating either I2PTunnel 'client' applications (which listen on a "
+"specific port and connect\n"
+"to a specific I2P destination whenever a socket to that port is opened) "
+"or I2PTunnel 'server'\n"
+"applications (which listen to a specific I2P destination and whenever it "
+"gets a new I2P \n"
+"connection it outproxies to a specific TCP host/port).  These streams are"
+" 8-bit clean, and are\n"
+"authenticated and secured through the same streaming library that SAM "
+"uses, but there is a \n"
+"nontrivial overhead involved with creating multiple unique I2PTunnel "
+"instances, since each have\n"
+"their own unique I2P destination and their own set of tunnels, keys, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:264
+msgid ""
+"I2P supports a SOCKS V4 and V5 proxy.\n"
+"Outbound connections work well. Inbound (server) and UDP functionality "
+"may be incomplete\n"
+"and untested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:271
+msgid "Removed"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:272
+msgid ""
+"There used to be a simple \"ministreaming\" library,\n"
+"but now ministreaming.jar contains only the interfaces for the full "
+"streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:277
+msgid "Datagrams"
+msgstr "Datagrammes"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:278
+msgid "Recommended for UDP-like applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:279
+#, python-format
+msgid ""
+"The Datagram library allows sending UDP-"
+"like packets.\n"
+"It's possible to use:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:284
+msgid "Repliable datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:285
+msgid "Raw datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:289
+msgid "Not recommended"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:290
+#, python-format
+msgid ""
+"I2CP itself is a language independent protocol, "
+"but to implement an I2CP library \n"
+"in something other than Java there is a significant amount of code to be "
+"written (encryption routines, \n"
+"object marshalling, asynchronous message handling, etc).  While someone "
+"could write an I2CP library in \n"
+"C or something else, it would most likely be more useful to use the C SAM"
+" library instead."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:297
+msgid "Web Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:298
+msgid ""
+"I2P comes with the Jetty webserver, and configuring to use the Apache "
+"server instead is straightforward.\n"
+"Any standard web app technology should work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:304
+msgid ""
+"Developing using I2P requires a working I2P installation and a "
+"development environment of your own choice.\n"
+"If you are using Java, you can start development with the streaming library or datagram library.\n"
+"Using another programming language, SAM or BOB can be used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:310
+msgid "Developing with the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:312
+msgid ""
+"The following example shows how to create TCP-like client and server "
+"applications\n"
+"using the streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:317
+msgid "This will require the following libraries in your classpath:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:321
+msgid "The streaming library itself"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:322
+msgid "Factory and interfaces for the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:323
+msgid "Standard I2P classes, data structures, API, and utilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:326
+msgid ""
+"Network communication requires the usage of I2P network sockets.\n"
+"To demonstrate this, we will create an application where a client can "
+"send text messages to a server,\n"
+"who will print the messages and send them back to the client. In other "
+"words, the server will function as an echo."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:331
+msgid ""
+"We will start by initializing the server application. This requires "
+"getting an I2PSocketManager\n"
+"and creating an I2PServerSocket.\n"
+"We will not provide the I2PSocketManagerFactory with the saved keys for "
+"an existing Destination,\n"
+"so it will create a new Destination for us.\n"
+"So we will ask the I2PSocketManager for an I2PSession, so we can find out"
+" the Destination that\n"
+"was created, as we will need to copy and paste that information later so "
+"the client can connect to us."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:362
+msgid "Code example 1: initializing the server application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:364
+msgid ""
+"Once we have an I2PServerSocket, we can create I2PSocket instances to "
+"accept connections from clients.\n"
+"In this example, we will create a single I2PSocket instance, that can "
+"only handle one client at a time.\n"
+"A real server would have to be able to handle multiple clients.\n"
+"To do this, multiple I2PSocket instances would have to be created, each "
+"in separate threads.\n"
+"Once we have created the I2PSocket instance, we read data, print it and "
+"send it back to the client.\n"
+"The bold code is the new code we add."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:448
+msgid "Code example 2: accepting connections from clients and handling messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:452
+msgid ""
+"When you run the above server code, it should print something like this "
+"(but without the line endings, it should just be\n"
+"one huge block of characters):"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:466
+msgid ""
+"This is the base64-representation of the server Destination. The client "
+"will need this string to reach the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:470
+msgid ""
+"Now, we will create the client application. Again, a number of steps are "
+"required for initialization.\n"
+"Again, we will need to start by getting an I2PSocketManager.\n"
+"We won't use an I2PSession and an I2PServerSocket this time.\n"
+"Instead, we will use the server Destination string to start our "
+"connection.\n"
+"We will ask the user for the Destination string, and create an I2PSocket "
+"using this string.\n"
+"Once we have an I2PSocket, we can start sending and receiving data to and"
+" from the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:554
+msgid ""
+"Code example 3: starting the client and connecting it to the server "
+"application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:556
+msgid ""
+"Finally, you can run both the server and the client application.\n"
+"First, start the server application. It will print a Destination string "
+"(like shown above).\n"
+"Next, start the client application. When it requests a Destination "
+"string, you can enter the string printed by the server.\n"
+"The client will then send 'Hello I2P!' (along with a newline) to the "
+"server, who will print the message and send it back to the client."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:562
+msgid "Congratulations, you have successfully communicated over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:566
+msgid "Existing Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:567
+msgid "Contact us if you would like to contribute."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:588
+msgid "Application Ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:590
+msgid "NNTP server - there have been some in the past, none at the moment"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:593
+msgid ""
+"Jabber server - there have been some in the past, and there is one at the"
+" moment, with access to the public internet"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:596
+msgid "PGP Key server and/or proxy"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:599
+msgid ""
+"Content Distribution / DHT applications - resurrect feedspace,\n"
+"port dijjer, look for alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:603
+msgid "Help out with Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:606
+msgid ""
+"Web-based applications - The sky is the limit for hosting web-server-"
+"based\n"
+"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n"
+"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:611
+msgid ""
+"Resurrect some old apps, several previously in the i2p source package -\n"
+"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2
+msgid "I2P Developer's MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4
+msgid "MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5
+msgid ""
+"Monotone servers used by the I2P project require two types of keys to be "
+"used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
+msgid ""
+"Commit Keys to sign changes checked-in to the "
+"respository; and"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10
+msgid ""
+"Transport Keys to push changes to remote "
+"servers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13
+#, python-format
+msgid ""
+"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
+"import the\n"
+"developer commit keys, but only Monotone \n"
+"server operators will need to import the transport keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20
+msgid "Developer Commit keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:255
+msgid "Developer Transport Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:256
+#, python-format
+msgid ""
+"Note: Transport keys are only needed for setting up a\n"
+"Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
+msgid "License Agreements"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
+#, python-format
+msgid "For more information see the licenses page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8
+msgid ""
+"Following is a monotonerc file defining the current trust list.\n"
+"Developers must use this file in ~/.monotone/monotonerc or\n"
+"_MTN/montonerc in their i2p.i2p workspace."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17
+msgid "Agreements"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:2
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115
+msgid "Licenses"
+msgstr "Licenses"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:4
+msgid "I2P Software Licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:5
+#, python-format
+msgid ""
+"As required by our\n"
+"threat model (among other reasons), the \n"
+"software developed to support the anonymous communication \n"
+"network we call I2P must be freely available, open source, \n"
+"and user modifiable.  To meet these criteria, we make use of\n"
+"a variety of legal and software engineering techniques so\n"
+"as to remove as many barriers to entry for those considering\n"
+"making use of or contributing to the I2P effort."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:16
+msgid ""
+"While the information below may be more confusing than just simply \n"
+"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
+"the short answer to the question \"How is I2P licensed?\" is this:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:22
+msgid "All software bundled in the I2P distributions will allow:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:24
+msgid "use without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:25
+msgid ""
+"use with no restrictions on how, when, where, why, or by whom is running "
+"it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:26
+msgid "access to the source code without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:27
+msgid "modifications to the source"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:30
+msgid ""
+"Most of the software guarantees much more - the ability of anyone "
+"to \n"
+"distribute the modified source however they choose.  However, not all of "
+"the \n"
+"software bundled provides this freedom - the GPL restricts the ability of"
+" \n"
+"developers who wish to integrate I2P with their own applications that are"
+" not \n"
+"themselves open source applications.  While we applaud the noble goals of"
+" \n"
+"increasing the resources in the commons, I2P is best served by removing "
+"any\n"
+"barriers that stand in the way of its adoption - if a developer "
+"considering whether\n"
+"they can integrate I2P with their application has to stop and check with "
+"their lawyer,\n"
+"or conduct a code audit to make sure their own source can be released as "
+"GPL-compatible,\n"
+"we lose out."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:43
+msgid "Component licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:44
+msgid ""
+"The I2P distribution contains several resources, reflecting the "
+"partitioning of \n"
+"the source code into components.  Each component has its own license, "
+"which all \n"
+"developers who contribute to it agree to - either by explicitly declaring"
+" the release\n"
+"of code committed under a license compatible with that component, or by "
+"implicitly\n"
+"releasing the code committed under the component's primary license.  Each"
+" of these \n"
+"components has a lead developer who has the final say as to what license "
+"is compatible\n"
+"with the component's primary license, and the I2P project manager has the"
+" final say as\n"
+"to what licenses meet the above four guarantees for inclusion in the I2P "
+"distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:57
+msgid "Component"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:58
+msgid "Source path"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:59
+msgid "Resource"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:60
+msgid "Primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:61
+msgid "Alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:62
+msgid "Lead developer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:271
+msgid "GPL + java exception"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:272
+#, python-format
+msgid ""
+"While it may be redundant, just for clarity the\n"
+"GPL'ed code included within\n"
+"I2PTunnel and other apps must be released under the GPL with an "
+"additional \"exception\"\n"
+"explicitly authorizing the use of Java's standard libraries:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:288
+msgid ""
+"All source code under each component will by default be licensed under "
+"the\n"
+"primary license, unless marked otherwise in the code.  All of the above "
+"is\n"
+"summary of the license terms - please see the specific license for the "
+"component\n"
+"or source code in question for authoritative terms.  Component source "
+"locations and\n"
+"resource packaging may be changed if the repository is reorganized."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:296
+msgid "Commit privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:297
+#, python-format
+msgid ""
+"Developers may push changes to a distributed monotone repository if you\n"
+"receive permission from the person running that repository.\n"
+"See the Monotone Page for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:303
+msgid ""
+"However, to have changes included in a release, developers\n"
+"must be trusted by the release manager (currently zzz).\n"
+"In addition, they must explicitly agree with the above terms to be "
+"trusted.\n"
+"That means that they must send one of the release managers a signed "
+"message affirming that:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:310
+msgid ""
+"Unless marked otherwise, all code I commit is implicitly licensed under\n"
+"the component's primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:314
+msgid ""
+"If specified in the source, the code may be explicitly licensed under one"
+"\n"
+"of the component's alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:318
+msgid ""
+"I have the right to release the code I commit under the terms I\n"
+"am committing it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:324
+#, python-format
+msgid ""
+"If anyone is aware of any instances where the above conditions are not "
+"met,\n"
+"please contact the component lead and/or an I2P release manager with "
+"further\n"
+"information.\n"
+"See developers' license agreements."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
+msgid "Release Signing Key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
+msgid "Releases 0.7.6 and later are signed by zzz. His public key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40
+msgid ""
+"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public "
+"key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2
+msgid "Signed Developer Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4
+msgid ""
+"Keys for zzz, Complication and welterde are provided clearsigned. The key"
+" for jrandom must be\n"
+"verified differently, since he's away, and only left a binary detached\n"
+"signature for his key."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16
+msgid "Monotone keys for zzz"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47
+msgid "Monotone keys for welterde"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79
+msgid "Monotone keys for Complication"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114
+msgid "Monotone keys for jrandom"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
+msgid "Others"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
+msgid ""
+"Tip: To find zzz's GPG key, on his eepsite locate the key "
+"`0xA76E0BED`, with\n"
+"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 "
+"B310 4155\n"
+"76BA A76E 0BED`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49
+msgid ""
+"Tip: To find welterde's GPG key, on public keyservers locate the "
+"key\n"
+"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720"
+" FD81\n"
+"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81
+msgid ""
+"Tip: To find Complication's GPG key, on his eepsite locate the key"
+"\n"
+"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint "
+"`73CF\n"
+"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116
+msgid ""
+"Tip: To find jrandom's GPG key for Syndie releases, on public "
+"keyservers locate\n"
+"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n"
+"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122
+msgid ""
+"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n"
+"deployed in the Syndie Monotone repository, in a file named `mtn-"
+"committers`.\n"
+"That file also had a GPG signature, `mtn-committers.sig`, but it was a "
+"binary\n"
+"detached signature. I am going to supply both files in GPG ASCII-armoured"
+" form\n"
+"below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130
+msgid ""
+"First, the file `mtn-committers` containing jrandom's Monotone key. Save "
+"as\n"
+"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers "
+"--dearmor\n"
+"mtn-committers.asc`:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151
+msgid ""
+"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n"
+"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-"
+"committers.sig\n"
+"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n"
+"`mtn-committers` file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170
+#, python-format
+msgid ""
+"Some of the developers have included their Monotone keys in their signed license agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2
+msgid "Developer Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4
+#, python-format
+msgid "Read the new developers guide first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8
+msgid "Basic Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10
+msgid ""
+"Most of the following should be common sense for anybody who has worked "
+"on open source or in a commercial\n"
+"programming envrionment.\n"
+"The following applies mostly to the main development branch i2p.i2p.\n"
+"Guidelines for other branches, plugins, and external apps may be "
+"substantially different;\n"
+"check with the appropriate developer for guidance."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18
+msgid "Community"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20
+msgid ""
+"Please don't just \"write code\". If you can, participate in other "
+"development activities, including:\n"
+"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
+"testing;\n"
+"bug reporting and responses; documentation; code reviews; etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25
+msgid ""
+"Active devs should be available periodically on IRC #i2p-dev.\n"
+"Be aware of the current release cycle.\n"
+"Adhere to release milestones such as feature freeze, tag freeze, and\n"
+"the checkin deadline for a release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35
+msgid ""
+"Have a basic understanding of distributed source control systems, even if"
+" you haven't\n"
+"used monotone before. Ask for help if you need it.\n"
+"Once pushed, checkins are forever, there is no undo. Please be careful.\n"
+"If you have not used monotone before, start with baby steps.\n"
+"Check in some small changes and see how it goes."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42
+msgid ""
+"Test your changes before checking them in.\n"
+"If you prefer the checkin-before-test development model,\n"
+"use your own development branch (e.g. i2p.i2p.yourname.test)\n"
+"and propagate back to i2p.i2p once it is working well.\n"
+"Do not break the build. Do not cause regressions.\n"
+"In case you do (it happens), please do not vanish for a long period after"
+"\n"
+"you push your change."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51
+msgid ""
+"If your change is non-trivial, or you want people to test it and need "
+"good test reports\n"
+"to know whether your change was tested or not, add a checkin comment to "
+"history.txt\n"
+"and increment the build revision in RouterVersion.java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56
+msgid ""
+"Ensure that you have the latest monotonerc file in _MTN.\n"
+"Do not check in on top of untrusted revisions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60
+msgid ""
+"Ensure that you pull the latest revision before you check in.\n"
+"If you inadvertently diverge, merge and push as soon as possible.\n"
+"Don't routinely make others merge for you.\n"
+"Yes, we know that monotone says you should push and then merge,\n"
+"but in our experience, in-workspace merge works just as well as in-"
+"database merge,\n"
+"without creating a merge revision."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
+msgid ""
+"Do not check in major changes into the main i2p.i2p branch late in the "
+"release cycle.\n"
+"If a project will take you more than a couple days, create your own "
+"branch in monotone\n"
+"and do the development there so you do not block releases."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75
+msgid "Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77
+msgid ""
+"Coding style throughout most of the code is 4-spaces for indentation. Do "
+"not use tabs.\n"
+"Do not reformat code. If your IDE or editor wants to reformat everything,"
+" get control of it.\n"
+"Yes, we know 4 spaces is a pain, but perhaps you can configure your "
+"editor appropriately.\n"
+"In some places, the coding style is different.\n"
+"Use common sense. Emulate the style in the file you are modifying."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84
+msgid ""
+"New classes and methods require at least brief javadocs. Add @since "
+"release-number."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87
+msgid ""
+"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our "
+"official API.\n"
+"There are several out-of-tree plugins and other applications that rely on"
+" this API.\n"
+"Be careful not to make any changes that break compatibility.\n"
+"Don't add methods to the API unless they are of general utility.\n"
+"Javadocs for API methods should be clear and complete.\n"
+"If you add or change the API, also update the documentation on the "
+"website (i2p.www branch)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95
+msgid ""
+"Tag strings for translation where appropriate.\n"
+"Don't change existing tagged strings unless really necessary, as it will "
+"break existing translations.\n"
+"Do not add or change tagged strings after the \"tag freeze\" in the "
+"release cycle so that\n"
+"translators have a chance to update before the release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101
+msgid ""
+"Use generics and concurrent classes where possible. I2P is a highly "
+"multi-threaded application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104
+msgid ""
+"We require Java 6 to build but only Java 5 to run I2P.\n"
+"Do not use Java 6 classes or methods without handling the class not found"
+" exceptions\n"
+"and providing alternate Java 5 code. See classes in net.i2p.util for "
+"examples."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109
+msgid ""
+"Explicitly convert between primitive types and classes;\n"
+"don't rely on autoboxing/unboxing."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117
+msgid ""
+"Only check in code that you wrote yourself.\n"
+"Before checking in any code or library jars from other sources,\n"
+"justify why it is necessary,\n"
+"verify the license is compatible,\n"
+"and obtain approval from the lead developer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124
+msgid ""
+"For any images checked in from external sources,\n"
+"it is your responsibility to first verify the license is compatible.\n"
+"Include the license and source information in the checkin comment."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131
+msgid "Bugs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
+#, python-format
+msgid ""
+"Managing Trac tickets is everybody's job, please help.\n"
+"Monitor %(trac)s for tickets you have been assigned or can help with.\n"
+"Assign, categorize, comment on, fix, or close tickets if you can."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138
+msgid ""
+"Close a ticket when you think you've fixed it.\n"
+"We don't have a test department to verify and close tickets.\n"
+"If you arent sure you fixed it, close it and add a note saying\n"
+"\"I think I fixed it, please test and reopen if it's still broken\".\n"
+"Add a comment with the dev build number or revision and set\n"
+"the milestone to the next release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:2
+msgid "Using an IDE with I2P"
+msgstr "Utiliser un IDE avec I2P"
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:4
+msgid ""
+"The main I2P development branch (i2p.i2p) has been set up to"
+" enable developers to easily set up two of the commonly-used IDEs for "
+"Java development: Eclipse and NetBeans."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:10
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain .project and .classpath Eclipse files, to enable the branch "
+"to be easily set up in Eclipse."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:16
+msgid ""
+"Check out the I2P branch into some directory (e.g. "
+"$HOME/dev/i2p.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:20
+msgid ""
+"Open Eclipse and create a new Workspace, based in the directory that the "
+"I2P branch was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:24
+msgid ""
+"Select \"File - Import...\" and then under \"General\" select \"Existing "
+"Projects into Workspace\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:28
+msgid ""
+"For \"Select root directory:\" choose the directory that the I2P branch "
+"was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:32
+msgid "If necessary, click \"Refresh\" to refresh the list of projects."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:36
+msgid "Select every project in the list, and click \"Finish\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:40
+msgid ""
+"Done! Your workspace should now contain all projects within the I2P "
+"branch, and their build dependencies should be correctly set up."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:48
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain NetBeans project files."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:2
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:4
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:9
+msgid "Operating a Monotone client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:11
+#: i2p2www/pages/site/get-involved/guides/monotone.html:63
+msgid "Generating Monotone keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:12
+msgid "Trust and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:13
+#: i2p2www/pages/site/get-involved/guides/monotone.html:196
+msgid "Obtaining and deploying developers' keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:14
+#: i2p2www/pages/site/get-involved/guides/monotone.html:227
+msgid "Setting up trust evaluation hooks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:15
+#: i2p2www/pages/site/get-involved/guides/monotone.html:268
+msgid ""
+"Pulling the i2p.i2p, i2p.www and "
+"i2p.syndie branches"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:16
+#: i2p2www/pages/site/get-involved/guides/monotone.html:308
+msgid "Verifying that trust evaluation works"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:17
+#: i2p2www/pages/site/get-involved/guides/monotone.html:357
+msgid "Checking out a working copy of the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:18
+#: i2p2www/pages/site/get-involved/guides/monotone.html:384
+msgid "Updating your working copy to the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:22
+#: i2p2www/pages/site/get-involved/guides/monotone.html:414
+msgid "Operating a Monotone Server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:24
+msgid "Obtaining and deploying developers’ transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:25
+#: i2p2www/pages/site/get-involved/guides/monotone.html:424
+msgid "Granting push and pull access"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:26
+#: i2p2www/pages/site/get-involved/guides/monotone.html:469
+msgid "Running Monotone in server mode"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:27
+#: i2p2www/pages/site/get-involved/guides/monotone.html:494
+msgid "Differences under Debian GNU/Linux"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:34
+#, python-format
+msgid ""
+"This is a revised version of Complication's original\n"
+"  guide detailing the use of Monotone in I2P development.\n"
+"  For basic instructions see the quick-start "
+"guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:42
+#, python-format
+msgid ""
+"I2P has a distributed development model. The source code is replicated "
+"across\n"
+"  independently administered Monotone (\"MTN\") repositories.\n"
+"  Developers with commit rights are able to push their changes to the "
+"repository\n"
+"  (a license agreement needs to be "
+"signed\n"
+"  before commit rights are granted)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:52
+msgid ""
+"Some of Monotone's noteworthy qualities are: distributed\n"
+"  version control, cryptographic authentication, access control, its "
+"small size, having few\n"
+"  dependencies, storage of projects in a compressed SQLite database file,"
+" and\n"
+"  having the ability to resume interrupted synchronization attempts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:61
+msgid "Operating a Monotone Client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:66
+msgid ""
+"A transport key grants you the ability to push your changes to a Monotone"
+" repository server.\n"
+"  In order to commit code into Monotone (in essence signing your code), a"
+" commit key is also needed.\n"
+"  None of the public Monotone servers on I2P currently require a key in "
+"order to read (or pull) the source code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:74
+msgid ""
+"Without a transport key, one cannot:\n"
+"  
              \n"
+"    
            • pull code from a server which doesn't allow global read "
+"access
              • \n"
+"    
            • push code to any server
              • \n"
+"    
            • run a Monotone server
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:85
+msgid ""
+"Without a commit key, one cannot:\n"
+"  
              \n"
+"    
            • commit any code
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:94
+msgid ""
+"If you only intend to retrieve code from MTN, feel free to skip to the\n"
+"  next section. "
+"If you want\n"
+"  to generate keys, read the following."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:102
+msgid ""
+"By convention keys are named like an e-mail addresses, but a "
+"corresponding e-mail\n"
+"  address does not need to exist. For example, your keys might be named:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:113
+msgid ""
+"Monotone stores keys under $HOME/.monotone/keys in "
+"text files which\n"
+"  are named identically to the keys. For example:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:123
+msgid ""
+"To generate transport and commit keys, enter the following commands at a "
+"prompt:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:133
+msgid ""
+"Monotone will prompt you for a password to protect your keys. You are "
+"very strongly encouraged to set a password\n"
+"  for the commit key. Many users will leave an empty password for the "
+"transport key, especially those running a\n"
+"  Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:141
+msgid "Trust, and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:145
+msgid ""
+"Monotone's security model helps to ensure that nobody can easily "
+"impersonate a developer without\n"
+"  it being noticed. Since developers can make mistakes and become "
+"compromised,only manual review can\n"
+"  ensure quality of code. Monotone's trust model will ensure that you "
+"read the right diffs. It does\n"
+"  not replace reading diffs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:155
+msgid ""
+"A Monotone repository is a single file (a compressed SQLite database) "
+"which contains all of the project's source code and history."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:161
+msgid ""
+"After importing the "
+"developers' keys into Monotone and\n"
+"  setting up trust "
+"evaluation hooks,\n"
+"  Monotone will prevent untrusted code from being checked out into your "
+"workspace.\n"
+"  There are commands available to clean untrusted code from your "
+"workspace but in practice they've not been\n"
+"  needed due to the push access policies in place."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:171
+msgid ""
+"A repository can hold many branches. For example, our repository holds "
+"the\n"
+"  following main branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:176
+msgid "The I2P router and associated programs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:177
+msgid "The I2P project website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:178
+msgid "Syndie, a distributed forums tool"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:183
+msgid ""
+"By convention, the I2P Monotone repository is named i2p.mtn."
+" Before pulling\n"
+"  source code from servers, a database for your repository will need to "
+"be initialized.\n"
+"  To initialize your local repository, change into the directory that you"
+" want the\n"
+"  i2p.mtn file and branch directories to be stored and issue"
+" the following\n"
+"  command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:199
+msgid ""
+"Keys which developers use to commit code are essential for trust "
+"evaluation in\n"
+"  Monotone. The other developers' transport keys are only required for "
+"Monotone server operators.\n"
+"  "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:206
+#, python-format
+msgid ""
+"Developers' commit keys are provided GPG-signed on another page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:212
+#, python-format
+msgid ""
+"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
+"  file. Create this file (e.g. keys.txt) in the same "
+"directory where i2p.mtn is located. Import the keys with the"
+" command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:222
+msgid ""
+"Note: Never add keys to "
+"$HOME/.monotone/keys manually."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:230
+msgid ""
+"The default Monotone trust policy is way too lax for our requirements: "
+"every committer is trusted by default.\n"
+"  That is not acceptable for I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:237
+msgid ""
+"Change into the directory $HOME/.monotone and open "
+"the file\n"
+"  monotonerc with a text editor. Copy and paste the "
+"following two functions into this file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:246
+msgid ""
+"The first function determines an intersection between two sets, in our "
+"case a\n"
+"  revision's signers and trusted signers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:253
+msgid ""
+"The second function determines trust in a given revision, by calling the "
+"first\n"
+"  function with \"signers\" and \"trusted\" as arguments. If the "
+"intersection is\n"
+"  null, the revision is not trusted. If the intersection is not empty, "
+"the\n"
+"  revision is trusted. Otherwise, the revision is not trusted."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:262
+msgid ""
+"More information about Trust Evauluation Hooks can be found in the official Monotone "
+"documentation."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:271
+msgid ""
+"Enter the directory where you initialized i2p.mtn. Depending "
+"on whether you\n"
+"  want only I2P sources, or also sources for the I2P website and Syndie, "
+"you can\n"
+"  perform the pull operation in different ways."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:279
+msgid "If you only want I2P sources:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:288
+msgid "If you want all branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:294
+msgid ""
+"If the transfer aborts before completing sucessfully, simply repeating "
+"the pull command will resume the transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:300
+msgid ""
+"Pulling in the above examples is done anonymously by specifying an empty "
+"transport key.\n"
+"  If everyone pulls anonymously it will be harder for an attacker who "
+"gains control of the server\n"
+"  to selectively provide some people with tampered data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:311
+msgid "To verify that trust evaluation works:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:315
+msgid "Make a backup of your monotonerc file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:316
+msgid ""
+"Modify monotonerc by setting the trusted_signers "
+"variable in the following way:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:322
+msgid ""
+"With monotonerc configured as above, Monotone will no"
+" longer trust any committers. Confirm this by changing into the\n"
+"directory where i2p.mtn was created and attempt a checkout "
+"of the I2P branch:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:332
+msgid ""
+"A directory named i2p.i2p should not appear. You "
+"should encounter many\n"
+"  error messages like:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:349
+msgid ""
+"If you are satisfied with results, restore the backup of\n"
+"  monotonerc that was created above. If you didn't create a "
+"backup\n"
+"  as advised, re-read Setting up trust evaluation hooks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:360
+msgid ""
+"If you already have a branch checked out, skip to the next\n"
+"  section."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:367
+msgid ""
+"Change into the directory where i2p.mtn is located. Over "
+"there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:376
+msgid ""
+"The checkout should complete without error messages and a directory named"
+"\n"
+"  i2p.i2p should appear in the current directory. "
+"Congratulations! You have\n"
+"  successfully checked out the latest I2P sources, ready to be compiled."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:387
+msgid ""
+"If you haven't done this already, pull fresh code from the server to your"
+" local\n"
+"  Monotone repository. To accomplish this, change into the directory "
+"where\n"
+"  i2p.mtn is located and issue:\n"
+"  
              \n"
+"    
            • $ mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
+"i2p.i2p
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:398
+msgid "Now change into your i2p.i2p directory, and over there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:407
+msgid ""
+"As long as there were no errors…Congratulations! You have "
+"successfully updated to the latest I2P sources. They\n"
+"  should be ready to compile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:416
+msgid "Obtaining and deploying developers' transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:419
+msgid ""
+"As a server operator you may want to grant push access to certain "
+"developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:427
+msgid "By default the Monotone server denies all access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:433
+msgid "To grant pull access to all clients, set the following in"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:445
+msgid ""
+"No one will not be able to push code to your server without permission "
+"being explicitly granted. To grant push access:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:451
+msgid ""
+"Add the name of the user's transport key to\n"
+"$HOME/.monotone/write-permissions, such as\n"
+"
            \n"
+"    zzz-transport@mail.i2p\n"
+"    complication-transport@mail.i2p\n"
+"
            \n"
+"with one key per line."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:462
+msgid ""
+"Import the transport key(s) into your database. The procedure for "
+"importing transport keys is the same as for\n"
+"importing commit keys, which is described in the section Obtaining and deploying "
+"developers' keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:472
+msgid ""
+"A separate database should be used for your Monotone server because "
+"monotone will lock the database while it is served to others.\n"
+"  Make a copy of your development database, then start the server with:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:479
+msgid ""
+"If your key is protected with a passphrase, Monotone may request the "
+"passphrase\n"
+"  when the first client connects. You can work around this by connecting "
+"making the first client connection to your server\n"
+"  (or by clearing the password for your transport key)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:487
+msgid ""
+"For your server to be accessible for others over I2P, you will need to "
+"create a\n"
+"  server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" "
+"profile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:497
+msgid ""
+"Debian (amongst other distributions) has integrated Monotone into their\n"
+"  framework of daemons/services. Although Monotone servers can still be "
+"run\n"
+"  \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may"
+" be more straightforward."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:505
+msgid ""
+"Permissions are granted by editing the files\n"
+"  /etc/monotone/read-permissions and\n"
+"  /etc/monotone/write-permissions. You'll also need to edit\n"
+"  /etc/default/monotone to enable monotone to start at boot "
+"or to\n"
+"  customize the host, port, or database location."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
+msgid "New Developer's Guide"
+msgstr "Guide du nouveau développeur"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
+msgid ""
+"\n"
+"So you want to start work on I2P? Great!\n"
+"Here's a quick guide to getting started\n"
+"on contributing to the website or the software, doing development or "
+"creating translations."
+msgstr ""
+"\n"
+"Donc vous voulez commencer à travailler sur I2P ? Très bien !\n"
+"Voici un guide rapide doit pour commencer\n"
+"en contribuant au site Web ou au logiciel, faire du développement ou "
+"créer des traductions."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
+#, python-format
+msgid ""
+"\n"
+"Not quite ready for coding?\n"
+"Try getting involved first."
+msgstr ""
+"\n"
+"Pas tout à fait prêt pour programmer ?\n"
+"essayez d'abord devenir impliqué."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
+msgid "Basic study"
+msgstr "Étude basique"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
+msgid "Getting the I2P code"
+msgstr "Obtenir le code de I2P"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
+msgid "Building I2P"
+msgstr "Construire I2P"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
+msgid "Development ideas"
+msgstr "Idées de développement"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
+msgid "Making the results available"
+msgstr "Rendre disponibles les résultats"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
+msgid "Get to know us!"
+msgstr "Apprenez-nous à connaître !"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
+msgid "Translations"
+msgstr "Traductions"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
+msgid "Tools"
+msgstr "Outils"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
+msgid ""
+"Basic development on the I2P router or the embedded applications uses "
+"Java as the main development language.\n"
+"If you don't have experience with Java, you can always have a look at Thinking in Java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
+#, python-format
+msgid ""
+"Study the how intro,\n"
+"the other \"how\" documents,\n"
+"the tech intro,\n"
+"and associated documents.\n"
+"These will give you a good overview of how I2P is structured and what "
+"different things it does."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
+msgid ""
+"For development on the i2p router or the embedded applications,\n"
+"get the monotone source repository installed - short instructions:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
+msgid ""
+"Install monotone.\n"
+"Monotone is a version control system.\n"
+"We use it because it allows us to keep track of who does what changes to "
+"the source code (and for a lot of complicated things, but 'keeping track "
+"of changes' is the basic idea)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
+msgid ""
+"Skim over the monotone tutorial,"
+" to make sure you understand the concepts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
+msgid ""
+"If you want to remain anonymous, you need to do an additional step, to "
+"set up a connection to a monotone server over I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
+#, python-format
+msgid ""
+"Enable the i2ptunnel client tunnel on port "
+"8998 pointing to mtn.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
+msgid ""
+"Pick a directory where you want to put all your I2P files, and create a "
+"monotone database:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
+msgid ""
+"Define the trust list by creating ~/.monotone/monotonerc (or"
+" _MTN/monotonerc in the i2p.i2p workspace) with the "
+"following contents:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
+#, python-format
+msgid ""
+"Copy and paste the developer's commit keys "
+"into a new file (e.g. keys.txt) in the same directory\n"
+"  that i2p.mtn is in. Import the keys into your database "
+"with 
                  mtn -d i2p.mtn read < keys.txt
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:76
+msgid ""
+"Pull the I2P sources to your machine. This may take a long time, "
+"especially if you are doing this over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:78
+msgid "Anonymously:"
+msgstr "Anonymement :"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:81
+msgid "Non-anonymously:"
+msgstr "Non anonymement :"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:83
+msgid ""
+"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn"
+".i2p-projekt.de."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:90
+msgid ""
+"All the sources are now present on your machine, in the database file. To"
+" make them available in a directory, you need to check them out:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:92
+msgid ""
+"The above command creates a directory i2p.i2p, which contains all of the "
+"I2P sources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:96
+msgid "Remarks"
+msgstr "Remarques"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:97
+msgid ""
+"\n"
+"To download the website files instead of the I2P source files, use "
+"'i2p.www' instead of 'i2p.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:100
+msgid ""
+"The initial pull may take several hours using the tunnel.\n"
+"If it fails after a partial pull, simply rerun it, it will start where it"
+" left off.\n"
+"If you are in a hurry, use the non-anonymous access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:105
+#, python-format
+msgid ""
+"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
+#, python-format
+msgid ""
+"A long explanation about using monotone is available on the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
+#, python-format
+msgid ""
+"To compile the code, you need the Sun Java Development Kit 6 or higher, "
+"or equivalent JDK\n"
+"(Sun JDK 6 strongly recommended) and\n"
+"Apache ant\n"
+"version 1.7.0 or higher.\n"
+"If you go are working on the main I2P code, you can go into the i2p.i2p "
+"directory and run 'ant' to see the build options."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
+msgid ""
+"To build or work on console translations, you need\n"
+"the xgettext, msgfmt, and msgmerge tools from the\n"
+"GNU gettext package."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
+#, python-format
+msgid ""
+"For development on new applications,\n"
+"see the application development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
+#, python-format
+msgid ""
+"See zzz's TODO lists,\n"
+"this website's TODO list or\n"
+"Trac\n"
+"for ideas."
+msgstr ""
+"Voir la liste de zzz de TODO (choses "
+"à faire),\n"
+"liste TODO concernant ce site web ou\n"
+"Trac\n"
+"pour des idées."
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
+#, python-format
+msgid ""
+"See the bottom of the licenses page "
+"for\n"
+"commit privilege requirements. You need these to put code into i2p.i2p "
+"(not required for the website!)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
+msgid "Short version of how to generate and use keys if you plan to commit:"
+msgstr ""
+"Version courte sur la façon de générer et utiliser des clés si vous "
+"planifiez de vous engager :"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
+msgid "use an empty passphrase"
+msgstr "utilise une phrase mot de passe vide"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
+msgid "enter a passphrase"
+msgstr "entrer une phrase mot de passe"
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
+#, python-format
+msgid ""
+"send this to a mtn repo operator to get "
+"push privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
+#, python-format
+msgid ""
+"send this to a release manager to get "
+"commit privileges - not required for website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
+msgid "check in with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
+msgid "push with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
+#, python-format
+msgid "Long version: see the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
+#, python-format
+msgid ""
+"The developers hang around on IRC. They can be reached on the Freenode "
+"network, OFTC, and on the I2P internal networks. The usual place to look "
+"is #i2p-dev. Join the channel and say hi!\n"
+"We also have additional guidelines for regular"
+" developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
+#, python-format
+msgid ""
+"Website and router console translators: See the New Translator's Guide\n"
+"for next steps."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
+msgid ""
+"I2P is open source software that is mostly developed using open sourced\n"
+"toolkits. The I2P project recently acquired a license for the YourKit "
+"Java\n"
+"Profiler. Open source projects are eligible to receive a free license "
+"provided\n"
+"that YourKit is referenced on the project web site. Please get in touch "
+"if you\n"
+"are interested in profiling the I2P codebase."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
+#, python-format
+msgid ""
+"YourKit is kindly supporting open source projects with its full-featured "
+"Java Profiler.\n"
+"YourKit, LLC is the creator of innovative and intelligent tools for "
+"profiling\n"
+"Java and .NET applications. Take a look at YourKit's leading software "
+"products:\n"
+"YourKit Java Profiler and\n"
+"YourKit .NET Profiler."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
+msgid "New Translator's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
+msgid "Here's a very quick guide to getting started."
+msgstr "Voici un guide très rapide pour débuter."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
+msgid "How to Translate the Website"
+msgstr "Comment traduire le site web"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
+#, python-format
+msgid ""
+"Translation of the website is done with .po files. The easiest way by far"
+" to\n"
+"translate the website is to sign up for an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
+msgid "Preparation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
+#, python-format
+msgid ""
+"Come to #i2p-dev on irc and talk to people.\n"
+"Claim the language -\n"
+"To make sure other coworkers don't bump onto the files you are working "
+"on,\n"
+"please update the translation status on this wiki "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"Including the installation of monotone,\n"
+"checking out i2p.www branch, and generate your own monotone keys.\n"
+"It is not required that you sign a dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
+msgid ""
+"Run \"./extract-messages.sh\" to generate a "
+"messages.pot in the base directory.\n"
+"Edit the header of this file, then run \"./init-new-po.sh "
+"locale\" to generate the file\n"
+"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
+"\"mtn add\" this file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
+msgid ""
+"Edit i2p2www/pages/global/lang.html and add a line for your "
+"language (copy an existing line)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
+msgid ""
+"Add a flag image file to i2p2www/static/images/flags/ for "
+"the menu (copy from the router)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
+msgid ""
+"Edit files:\n"
+"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
+msgid ""
+"Check in:\n"
+"\"mtn pull\", \"mtn update\". Then check in by "
+"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
+"This collects the diff info of your changed file into your local repo. "
+"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
+"i2p.i2p\".\n"
+"This synchronizes your local repo with the repo on the target machine."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
+msgid "Repeat. Check in often. Don't wait until it is perfect."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
+msgid "How to Translate the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
+#, python-format
+msgid ""
+"The easiest way by far to translate the router console is to sign up for "
+"an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"including the installation of monotone and the gettext tools,\n"
+"checking out i2p.i2p branch, and generate your own monotone keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
+msgid "Generate your own gpg key and sign the dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
+msgid ""
+"Before starting a console translation, better help translate some i2p "
+"webpages first.\n"
+"At least an i2p homepage in your language would be great."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
+msgid ""
+"What to translate:\n"
+"There are about 15 files in the i2p.i2p branch that needs translation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
+msgid ""
+"Where xx is your language code like fr/de/ch/zh/...\n"
+"There may be or may not be files with your lang code. If not, you can "
+"create your own. by copying and renaming other language files you know "
+"with your own lang code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet, copy another language "
+"file to a new file foo_xx.bar for your language.\n"
+"Then \"mtn add\" the file.\n"
+"After creating a .po file, edit the headers. Then run \"ant "
+"distclean poupdate\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
+msgid ""
+"Start to work:\n"
+"Edit the HTML files with any text editor.\n"
+"Be sure not to use an editor in HTML mode that reformats everything.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
+msgid ""
+"As you can see, it's not that difficult.\n"
+"If you have questions about the meaning of the terms in the console, ask "
+"in #i2p-dev on IRC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
+msgid ""
+"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
+"and html, etc.? Why can't I just do a translation and email it to you?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
+msgid "A: Several reasons:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
+#, python-format
+msgid ""
+"You might be interested in translating via Transifex. Request to join a "
+"translation team here."
+msgstr ""
+"Vous pourriez être intéressé par la traduction via Transifex. Demandez à "
+"joindre une équipe de traduction ici."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
+msgid ""
+"We don't have anybody who has time to accept manual contributions and "
+"submit them to our source control system on your behalf. Even if we did, "
+"it doesn't scale."
+msgstr ""
+"Nous n'avons personne qui aie le temps d'accepter des contributions "
+"manuelles et les soumettre à notre système de contrôle source en votre "
+"nom. Même si nous l'avons eu fait, cela n'est pas possible à grande "
+"échelle."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
+msgid ""
+"Maybe you are thinking translation is a one-step process. It isn't. You "
+"can't do it all at once. You will make mistakes. You need to test it and "
+"tweak it to make it look right before you submit it. Developers "
+"will update or add to the English text, thus requiring a translation "
+"update."
+msgstr ""
+"Peut-être vous pensez que la traduction est un processus en une étape. "
+"Cela ne l'est pas. Vous ne pouvez pas tout faire immédiatement. Vous "
+"ferez des erreurs. Vous devez la tester et l'adapter afin qu'elle "
+"paraisse bien avant que vous la soumettiez. Les développeurs "
+"mettront à jour ou feront des ajouts au texte anglais, exigeant ainsi une"
+" mise à jour de traduction."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
+msgid ""
+"Having translators use a source control system directly provides "
+"authentication and accountablility - we know who is doing what, and we "
+"can track changes, and revert them if necessary."
+msgstr ""
+"Avoir des traducteurs utilisant un système de contrôle source fournit "
+"directement l'authentification et responsabilité - nous savons qui fait "
+"quoi et nous pouvons suivre à la trace les changements, et les retourner "
+"si nécessaire."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
+msgid ""
+".po files are not difficult. If you don't want to work directly with "
+"them, we recommend 'poedit'."
+msgstr ""
+"Les fichiers .po ne sont pas difficiles. Si vous ne voulez pas travailler"
+" directement avec eux, nous recommandons 'poedit'."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
+msgid ""
+"HTML files are not difficult. Just ignore the html stuff and translate "
+"the text."
+msgstr ""
+"Les fichiers HTML ne sont pas difficiles. Ignorez simplement le trucs "
+"HTML et traduisez le texte."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
+msgid ""
+"Installing and using monotone is not that difficult. Several of the "
+"translators and other contributors to I2P are non-programmers, and they "
+"use monotone regularly. Monotone is simply a source control system, it is"
+" not about \"coding\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
+msgid ""
+"Our items to translate are not \"documents\". They are html files and po "
+"files, with a specific format and character encoding (UTF-8) that must be"
+" maintained, and not corrupted by email programs or other methods of "
+"transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
+msgid ""
+"We looked at 'pootle' as a front-end for translators. It didn't work "
+"well, needed an administrator, and a pootle-based process would suffer "
+"from a number of the above flaws."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
+msgid ""
+"In summary:\n"
+"Yes, we know it is somewhat of a hurdle to get started. It's really the "
+"only possible way we can do it. Give it a try, it really isn't that hard."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
+msgid "More Information"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
+#, python-format
+msgid ""
+"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
+msgstr ""
+"Le canal IRC #i2p-dev, ou le forum "
+"translation sur %(zzz)s."
+
diff --git a/i2p2www/translations/fr/LC_MESSAGES/misc.po b/i2p2www/translations/fr/LC_MESSAGES/misc.po
new file mode 100644
index 00000000..bb04f34e
--- /dev/null
+++ b/i2p2www/translations/fr/LC_MESSAGES/misc.po
@@ -0,0 +1,1230 @@
+# French translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Boxoa590, 2013
+# magma , 2011
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-08-30 23:32+0000\n"
+"PO-Revision-Date: 2013-06-29 11:32+0000\n"
+"Last-Translator: Boxoa590\n"
+"Language-Team: French "
+"(http://www.transifex.com/projects/p/I2P/language/fr/)\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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: i2p2www/pages/site/misc/jbigi.html:6
+msgid "Overview"
+msgstr ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: i2p2www/pages/site/misc/transition-guide.html:21
+msgid "Guide"
+msgstr ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:44
+msgid "Click \"Save\""
+msgstr ""
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:51
+msgid "Add the following line:"
+msgstr ""
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:55
+msgid "Click \"Apply\""
+msgstr ""
+
+#: 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/fr/LC_MESSAGES/priority.po b/i2p2www/translations/fr/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..2a28dc93
--- /dev/null
+++ b/i2p2www/translations/fr/LC_MESSAGES/priority.po
@@ -0,0 +1,3497 @@
+# French translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Boxoa590, 2013
+# magma , 2011
+# Towatowa441, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-11-28 15:38+0000\n"
+"Last-Translator: Towatowa441\n"
+"Language-Team: French "
+"(http://www.transifex.com/projects/p/I2P/language/fr/)\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/blog/category.html:2
+msgid "Blog Category"
+msgstr "Catégorie blog"
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr "Flux ATOM du Blog I2P pour la catégorie : %(category)s"
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:92
+msgid "Blog"
+msgstr "Blog"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "Flux ATOM du Blog I2P"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr "Posté %(date)s par %(author)s"
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "Davantage de posts de blog…"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr "Posté :"
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "Auteur :"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Packages I2P Debian"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+"Le paquet Debian \n"
+"a été testé et devrait fonctionner sur plateformes x86/x86_64 "
+"faisant fonctionner :"
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr "Ubuntu (Precise 12.04 et plus récente)"
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+"Linux Debian  (Squeeze et plus récente) & "
+"kFreeBSD"
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+"Les paquets I2P pourraient fonctionner sur des systèmes non "
+"listés ci-dessus. Veuillez rapporter s'il vous plaît toutes questions au "
+"sujet de ces paquets sur Trac à\n"
+"https://trac.i2p2.de."
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Option 1: Versions récentes de Ubuntu et ses "
+"dérivées (Essayez ceci si vous n'utilisez pas Debian)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr "Option 2: Debian (y compris dérivés de Debian)"
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+"Instructions pour Ubuntu Precise Pangolin (et plus récent) et des dérivés"
+" tels que Linux Mint et Ubuntu"
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Ajouter le PPA via la ligne de commande et installer I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Ouvrir un terminal et entrer :"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"Cette commande va ajouter le PPA à /etc/apt/sources.list.d et rapporter "
+"la\n"
+"clé GPG avec laquelle le dépôt a été signé. La clé GPG assure\n"
+"que les paquetages n'ont pas été altérés depuis leur construction."
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "Avertissez votre gestionnaire de paquets de la nouvelle PPA en entrant :"
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+"Cette commande va récupérer la plus récente liste de logiciels de chaque\n"
+"déôt qui soit activé sur votre système, y compris le PPA I2P qui\n"
+"a été ajouté avec la commande antérieure."
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "Vous êtes maintenant prêt à installer I2P !"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "Ajouter le PPA en utilisant Synaptic"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+"Ouvrir Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+"Une fois Synaptic ouvert, sélectionnez Repositories depuis le "
+"menu Settings."
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"Cliquer l'onglet Autres sources et cliquez Ajouter. "
+"Coller ppa:i2p-maintainers/i2p dans le champ ligne-APT et "
+"cliquez Ajouter source. Cliquez le bouton Fermer puis "
+"Recharger."
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+"Dans la boîte \"filtre rapide\", tapez i2p et pressez "
+"entrée. Quand i2p est retournée dans la liste des résultats,"
+" faites un clic droit sur i2p et sélectionneez Marquer "
+"pour installation. Après avoir fait cela vous devirez voir un popup "
+"Marquer les changements additionnels requis ?. Si c'est le cas, "
+"cliquez Marquer puis Appliquer."
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+"Après que le processus d'installation soit terminé, vous pouvez passer à "
+"la prochaine\n"
+"partie de démarrer I2P et le "
+"configurer pour votre système."
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr "Instructions pour Debian"
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+"Notez : les étapes ci-dessous devraient être exécutées avec accès root "
+"(ex: en commutant\n"
+"l'utilisateur en root à l'aide de \"su\" ou en préfixant chaque commande "
+"par \"sudo\")."
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr "Ajoutez des lignes comme la suivante à %(file)s."
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the  key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+"Téléchargez la clé utilisée pour signer le "
+"dépôt et ajoutez-là à apt :"
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr "Notifiez votre gestionnaire de paquet du nouveau dépôt, en entrant"
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+"Cette commande va récupérer la dernière liste de logiciel depuis chaque\n"
+"dépôt permis sur votre système, y compris le dépôt I2P ajouté à l'étape\n"
+"1."
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+"Vous êtes maintenant prêt à installer I2P ! Installer le paquet i2p-keyring            \n"
+"assurera que vous receviez les mises à jour à la clé GPG du dépôt."
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+"Après la procédure d'installation terminée, vous pouvez passer à la "
+"partie suivante de  démarrer I2P  et "
+"le configurer pour votre système."
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "Travail post-installation"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+"En utilisant ces paquetages I2P, le routeur I2P peut être lancé\n"
+"des trois façons suivantes :"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+"utiliser le script i2prouter "à la demande". Lancez simplement "
+""i2prouter\n"
+"start" depuis une invite de commande. (Note: ne "
+"pas utiliser\n"
+"sudo ni le lancer en tant que root !)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""sur demande" sans le java service wrapper\n"
+"(requis sur les systèmes non-Linux/non-x86) en lançant \"i2prouter-"
+"nowrapper\".\n"
+"(Note: ne pas\n"
+"utiliser sudo ni le lancer en tant que root !)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"en tant que service est lancé automatiquement quand le système boote, "
+"avant\n"
+"même d'être loggé. Le service peut être activé avec \"dpkg-"
+"reconfigure\n"
+" i2p\" en tant que root ou en utilisant sudo. C'est le moyen "
+"d'opération recommandé."
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+"Lorsque vous installez pour la première fois, veuillez ne pas oublier de "
+"régler votre NAT / pare-feu\n"
+"si vous le pouvez. Les ports à transmettre peuvent être trouvés sur la \n"
+"Configuration réseau I2P dans la console du routeur. Si, pour "
+"transmettre des ports, de l'aide vous est nécessaire,\n"
+"le site web portforward.com pourra"
+" vous être utile."
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"S'il vous plaît examinez etajustez les paramètres de bande "
+"passante sur la\n"
+"page de configuration,\n"
+"car les paramètres par défaut de 96 KB/s down / 40 KB/s up sont assez "
+"conservateurs."
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"Si vous voulez atteindre des eepsites via votre navigateur, jettez un "
+"oeil sur la page configuration de proxy du "
+"navigateur pour un tutoriel facile."
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Télécharger"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Télécharger I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Dépendance"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+"\n"
+"Java Runtime 1.5 ou plus récent.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, ou\n"
+"IcedTea7\n"
+"recommandé,\n"
+"excepté Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Déterminez ici la version de votre Java "
+"installé\n"
+"ou tapez java -version à votre invite de commande.\n"
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "Installations propres"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr "sélectionner lien alternatif"
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Télécharger ce fichier et l'exécuter."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Téléchargez ce fichier et double-cliquez dessus (si cela fonctionne) ou\n"
+"tapez java -jar i2pinstall_%(i2pversion)s.jar dans un "
+"terminal pour exécuter\n"
+"l'installateur. \n"
+"Vous pourrez peut-être faire un clic droit et sélectionner\n"
+""Ouvrir avec Java"."
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "Installation en ligne de commande (headless) :"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Télécharger la %(i2pversion)s installeur graphique OSX ci-dessus et\n"
+"exécuter java-jar i2pinstall_%(i2pversion)s.jar -console à "
+"partir de la ligne de commande."
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Téléchargez ce fichier et double-cliquez le (si cela marche) ou\n"
+"tapez java -jar i2pinstall_%(i2pversion)s.jar dans un "
+"terminal our lancez\n"
+"l'installeur.\n"
+"Sur certaines platformes vous pourriez pouvoir faire clic droit et "
+"sélectionner\n"
+" "Ouvrir avec Java"."
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Téléchargez l'installateur graphique depuis ci-dessus et\n"
+"lancez java -jar i2pinstall_%(i2pversion)s.jar -console "
+"depuis la ligne de commande."
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Des packages pour Debian & Ubuntu sont disponibles."
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+"    The latest dev build is version %(devbuild)s, and is available from\n"
+"    str4d's eepsite."
+msgstr ""
+"Le fichier ci-dessus est l'actuelle version construite.\n"
+"La version dev la plus récente est la version %(devbuild)s, et est "
+"disponible depuis\n"
+"le Eepsite de str4d."
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+"      are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+"      the other."
+msgstr ""
+"Les versions release et dev des APK de I2P ne sont pas compatibles, car "
+"elles⏎\n"
+"sont signées respectivement par zzz et str4d. Désinstallez l'une avant "
+"d'installer⏎\n"
+"l'autre."
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "À partir des sources :"
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+"    or via Git from git.repo.i2p or Github.\n"
+"    
            \n"
+"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+"Aussi, vous pouvez récupérer le source depuis monotone⏎\n"
+" ou via Git depuis git.repo.i2p ou Github.⏎\n"
+"
            ⏎\n"
+" Lancez (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) puis soit⏎\n"
+" lancez l'installeur GUI ou l'installation facile comme ci-dessus."
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Les fichiers sont signés par zzz,\n"
+"dont la clé est içi."
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"I2P peut aussi être téléchargé depuis nos pages projet sur Launchpad et Google Code."
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"Après avoir exécuté le programme d'installation sur Windows, cliquez sur "
+"le bouton \"Start I2P\"\n"
+"ce qui fera apparaître la console du routeur,\n"
+"qui contient des instructions supplémentaires."
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"Sur les systèmes Unix, I2P peut être lancé en tant que service\n"
+"en utilisant le script \"i2prouter\", situé dans le répertoire que vous "
+"avez choisi pour I2P.\n"
+"Changer vers ce répertoire dans une console et émettre \"sh statut "
+"i2prouter\"\n"
+"devrait vous dire l'état du routeur. Les arguments \"start\", \"stop\" et"
+" \"restart\"\n"
+"contrôlent le service. La console du routeur\n"
+"peut être consultée à son emplacement habituel.\n"
+"Pour les utilisateurs des systèmes OpenSolaris et d'autres systèmes pour "
+"lesquels le wrapper (i2psvc) n'est pas supporté,\n"
+"démarrer le routeur avec \"sh runplain.sh\" à la place."
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"Lorsque vous installez pour la première fois, veuillez vous rappeler de "
+"régler votre NAT/pare-feu\n"
+"si vous le pouvez, en gardant à l'esprit les ports que I2P utilise côté "
+"Internet,\n"
+"décrits içi parmi d'autres ports.\n"
+"Si vous avez ouvert avec succès votre port TCP entrant, activez également"
+" le protocole TCP entrant sur la\n"
+"page de configuration."
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"Aussi,veuillez examiner et ajuster les paramètres de bande "
+"passante sur la\n"
+"page de configuration,\n"
+"car les paramètres par défaut (96 kbps down / 40 kbps up) sont assez "
+"lents."
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "Mises à jour depuis des versions antérieures :"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr ""
+"Les mises à jour automatiques et manuelles sont disponibles pour la "
+"version."
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "Mises à jour automatiques"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+"Si vous utilisez 0.7.5 ou ultérieure, votre routeur doit détecter la\n"
+"nouvelle version. Pour mettre à niveau il suffit de cliquer sur le bouton"
+" 'Télécharger mise à jour' sur votre console routeur\n"
+"quand elle apparaît."
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"En raison d'un bug dans la version 0.7.6, ceux dont la première "
+"installation a été I2P cette version\n"
+"et qui n'ont pas mis à jour manuellement\n"
+"peuvent obtenir une erreur \"la version téléchargée n'est pas supérieure "
+"à la version actuelle\",\n"
+"et devraient utiliser la méthode de mise à jour manuelle ci-dessous."
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Si vous utilisez 0.7.4 ou plus tôt, s'il vous plaît voir\n"
+"les notes de version 0.7.5 \n"
+"pour des informations importantes sur la façon de configurer votre "
+"routeur pour automatiquement\n"
+"recevoir la release."
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Si vous utilisez 0.6.1.30 ou plus récente, s'il vous plaît voir\n"
+"instructions \n"
+"pour des informations importantes sur la façon de configurer votre "
+"routeur pour automatiquement\n"
+"recevoir la release."
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+"    router console "
+"allowing\n"
+"    you to download and install the new release by just clicking on that\n"
+"    link."
+msgstr ""
+"Si vous avez reconfiguré votre routeur en suivant les instructions, vous devriez voir un lien sur"
+" votre\n"
+" console du routeur vous "
+"permettant\n"
+"de télécharger et d'installer la nouvelle version en cliquant simplement "
+"sur ​​ce\n"
+"lien."
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr ""
+"Comme alternative, vous pouvez utiliser la méthode manuelle spécifiée ci-"
+"dessous."
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "Mises à jour manuelles"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and rename as i2pupdate.zip.\n"
+"    (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+"    resulting i2pupdate.zip to your I2P installation directory).  You do"
+" \n"
+"    NOT need to unzip that file."
+msgstr ""
+"Téléchargez ce fichier dans le répertoire d'installation\n"
+"de votre I2P puis  renommez-le en i2pupdate.zip .\n"
+"(alternativement, vous pouvez obtenir le code source comme ci-dessus et "
+"exécuter \"ant updater\", puis copier le\n"
+"résultat i2pupdate.zip dans votre répertoire d'installation de I2P). Vous"
+" n'avez\n"
+"PAS besoin de décompresser ce fichier."
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+"Cliquez \"Redémarrer\""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "Prenez une tasse de café et revenez dans 11 minutes"
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Le fichier est signé par zzz,\n"
+"dont la clé est içi."
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "Précédentes releases"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"Les précédentes releases sont disponibles sur Google "
+"Code\n"
+"et Launchpad\n"
+"et à l'intérieur du réseau I2P sur %(echelon)s."
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "Sélection de miroir"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "Fichier:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "N'importe quel miroir"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+"Pour réclamer la récompense, l'auteur ne doit pas être payé par d'autres "
+"organisations ⏎\n"
+"ni des équipes pour ce travail (par exemple, les étudiants GSoC ne sont "
+"pas valides)."
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations.  Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"Les montants des récompenses peuvent être augmentés par de nouveaux dons."
+" Pensez-⏎\n"
+"vous que ceux-ci sont importants? Ajouter votre "
+"donation, ⏎\n"
+"en marquant le montant pour le %(donatename)s récompense-bounty !"
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "Pas trouvé"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+"Oui... la ressource que vous cherchiez, est nommée différemment, n'existe"
+" pas, ou a été supprimée."
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "Erreur serveur"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "Erreur serveur n°500"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "Hum... le serveur a rencontré une sorte d'erreur."
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "Miroirs"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "Sécurisé"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "Divers."
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Liens"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "Impressum"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "T-Shirts!"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "Europe"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "USA"
+
+#: i2p2www/pages/global/footer.html:31 i2p2www/pages/global/nav.html:133
+msgid "Donate"
+msgstr "Faire un don"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr "Passer la navigation"
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "Logo I2P"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "The Invisible Internet Project (le projet internet invisible)"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+"Cette page a été mise à jour en %(lastupdated)s et est correcte pour la "
+"version de routeur %(accuratefor)s."
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "Cette page a étée mise à jour dernièrement en %(lastupdated)s."
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "Cette page est à jour pour la version de routeur %(accuratefor)s."
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr "Précédent"
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr "Suivant"
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr "Posté dans"
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "A propos"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Introduction à I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "Comparaisons"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "Vue d'ensemble des comparaisons"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Autres réseaux anonymes"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Documentation"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Index documentation"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Comment ça marche ?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "Intro douce"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "Intro technique"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "Modèle de menace"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Routage en oignon"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "Base de données réseau"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "Routage tunnel"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "Sélection de pair"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Cryptographie"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Spécifications"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "Fichier de blocage"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "Structures communes"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "Fichiers de configuration"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:56
+msgid "Datagrams"
+msgstr "Datagrammes"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr "Fichiers GeoIP"
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:88
+msgid "Plugins"
+msgstr "Plugins"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:55
+msgid "Streaming library"
+msgstr "Librarie streaming"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "Création de tunnel"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "Messages tunnel "
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "Mises à jour logicielles"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:60 i2p2www/pages/global/nav.html:113
+msgid "Applications"
+msgstr "Applications"
+
+#: i2p2www/pages/global/nav.html:62
+msgid "Supported applications"
+msgstr "Applications supportées"
+
+#: i2p2www/pages/global/nav.html:63
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Protocols"
+msgstr "Protocoles"
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Protocol stack"
+msgstr "La pile de protocole"
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Transports"
+msgstr "Transports"
+
+#: i2p2www/pages/global/nav.html:75
+msgid "Transport layer overview"
+msgstr "Aperçu couche transport"
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Tunnels"
+msgstr "Tunnels"
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Tunnel implementation"
+msgstr "Implémentation tunnel"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Unidirectional tunnels"
+msgstr "Tunnels unidirectionels"
+
+#: i2p2www/pages/global/nav.html:84
+msgid "Old implementation"
+msgstr "Ancienne implémentation"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Naming and addressbook"
+msgstr "Nomination et carnet d'adresses"
+
+#: i2p2www/pages/global/nav.html:91
+msgid "Team"
+msgstr "Équipe"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Hall of Fame"
+msgstr "Temple de la renommée - hall of fame"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Academic papers and peer review"
+msgstr "Documents universitaires et examen par des pairs"
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Presentations, tutorials and articles"
+msgstr "Présentations, tutoriels et articles"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Contact us"
+msgstr "Contactez-nous"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Help"
+msgstr "Aide"
+
+#: i2p2www/pages/global/nav.html:101
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "How to browse I2P"
+msgstr "Comment naviguer sur I2P"
+
+#: i2p2www/pages/global/nav.html:103
+msgid "Glossary"
+msgstr "Glossaire"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Performance"
+msgstr "Performance"
+
+#: i2p2www/pages/global/nav.html:105 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Forums"
+
+#: i2p2www/pages/global/nav.html:108
+msgid "Volunteer"
+msgstr "Volontaire"
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Get involved!"
+msgstr "Impliquez-vous !"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Develop"
+msgstr "Développer"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Licenses"
+msgstr "Licenses"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Release signing keys"
+msgstr "Relâcher clés de signature"
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Signed keys"
+msgstr "Clés signées"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Developers keys"
+msgstr "Clés des développeurs"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Bug tracker"
+msgstr "Traqueur de bugs"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Academic research"
+msgstr "Recherche universitaire"
+
+#: i2p2www/pages/global/nav.html:122
+msgid "Open research questions"
+msgstr "Questions concernant la recherche ouverte"
+
+#: i2p2www/pages/global/nav.html:123
+msgid "Guides"
+msgstr "Guides"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "New developers"
+msgstr "Nouveaux développeurs"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Using an IDE with I2P"
+msgstr "Utiliser un IDE avec I2P"
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Developer guidelines and coding style"
+msgstr "Guide du développeur et style de programmation"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "New translators"
+msgstr "Nouveaux traducteurs"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Bounties"
+msgstr "Projets récompensés - bounties"
+
+#: i2p2www/pages/global/nav.html:134 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Meetings"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Roadmap"
+msgstr "Feuille de route (roadmap)"
+
+#: i2p2www/pages/global/nav.html:136
+msgid "Task list"
+msgstr "Liste de tâches"
+
+#: i2p2www/pages/global/nav.html:139
+msgid "Language"
+msgstr "Langue"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr "Flux ATOM des meetings I2P"
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "Logs des meetings I2P précédents"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr ""
+"Les réunions sont actuellement en attente jusqu'à ce qu'un moment plus "
+"approprié puisse être choisi."
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"Si vous avez quelque chose à discuter, s'il vous plaît trouver les "
+"développeurs sur IRC dans #I2P-dev. ⏎ Status "
+"updates dans lequel des développeurs sont également disponibles."
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr "Meeting dévelopement I2P %(id)s"
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr "Log IRC plei"
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "Par thème"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "Par date"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "Par auteur"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
            \n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
            \n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+"Veuillez envoyer des entrées nouvelles ou corrigées toclass=\"marksource "
+"newline\" title=\"New line\">\n"
+"class=\"marksource tag\">class=\"marksource "
+"tag\">class=\"marksource "
+"var\">%(email)sclass=\"marksource tag\">class=\"marksource "
+"tag\">.class=\"marksource tag\">
            class=\"marksource newline\" "
+"title=\"New line\">\n"
+" Si vous le pouvez, veuillez les envoyer au format BibTeX, voir "
+"ourclass=\"marksource newline\" title=\"New line\">\n"
+"class=\"marksource tag\">%(bibtex)s\">BibTeX source pageclass=\"marksource tag\"> for "
+"examples.class=\"marksource tag\">
            class=\"marksource newline\" "
+"title=\"New line\">⏎\n"
+" N'oubliez pas d'inclure les URL si possible:class=\"marksource newline\""
+" title=\"New line\">\n"
+"class=\"marksource tag\">%(citeseer)s\">offline papers are less usefulclass=\"marksource "
+"tag\">."
+
+#: i2p2www/pages/papers/list.html:94
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"Free Haven's anonymity bibliography."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Contac"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr "Email"
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like OFTC,\n"
+"  EIN and Freenode.\n"
+"  All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+"Notre réseau IRC primaire est le réseau Irc2P au sein de I2P, un tunnel "
+"par défaut vers ce réseau est mis en place lors des nouvelles "
+"installations de routeurs.\n"
+"Nous sommes également présents sur plusieurs réseaux standards tels que "
+"OFTC,\n"
+"EIN et Freenode.\n"
+"Sur tous ces réseaux tous les canaux au sujet d'I2P sont reliés aux "
+"canaux principaux de Irc2P via des robots de relais."
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Liste canal :"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "Discussion i2p générale"
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "Hors sujet"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "Discussion développement"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Canal d'aide"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"La plupart des discussions sur le développement de I2P se passe sur le I2P developper forum. C'est généralement le "
+"meilleur endroit pour commencer avec requêtes, si le canal IRC dev est "
+"inactif."
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "Mailing lists"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+"I2P a une liste de diffusion, mais elle est rarement utilisée car "
+"l'actuelle petite équipe de développeurs préfèrent communiquer via IRC ou"
+" le forum des développeurs. Cela pourrait changer à l'avenir."
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "S'abonner"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+"Pour vous abonner à une mailing list, allez à la page d'information de la"
+" liste (lien ci-dessous) et remplissez le formulaire. Les adresses e-mail"
+" internes à I2P (ex: foobar@mail.i2p) peuvent être utilisées."
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "Se désinscrire"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+"Pour vous désabonner d'une mailing list ou modifier vos options "
+"d'abonnement, allez à la page d'information de la liste (lien ci-dessous)"
+" et entrez votre adresse courriel d'abonnement."
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Listes"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Archive"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+"Discussions générales I2P - tout ce qui ne rentre pas dans une autre "
+"liste va ici."
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+"Vous n'aimez pas les listes de diffusion? Alors ceci est pour vous. Tous "
+"les listes de diffusion sont disponibles via NNTP aussi."
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr "Cartographie-group-list :"
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Serveurs:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Foire Aux Questions (Frequently Asked Questions)"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Index"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "Général"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "Sur quels systèmes I2P va fonctionner ?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+"Qu'est-ce qu'un \"eepsite\" et comment dois-je configurer mon navigateur "
+"pour pouvoir les utiliser ?"
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "Mon routeur a très peu de pairs actifs, est-ce OK ?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr ""
+"Qu'est-ce que le nombre \"Actifs: x / y\" signifie dans la console du "
+"routeur ?"
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+"Mes pairs actifs / pairs connus / tunnels participants / connexions / "
+"bande passante  varient considérablement au fil du temps ! Est-ce quelque"
+" chose va mal ?"
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "Est-t-il risqué d'utiliser un proxy sortant (outproxy) ?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr "La plupart des eepsites dans I2P sont hors d'accès ?"
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Quels ports I2P utilise ?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "Pourquoi est-ce que I2P écoute des connexions sur le port 32000 ?"
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "Je pense avoir trouvé un bug, où puis-je le signaler?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr ""
+"Qu'est-il arrivé à *.i2p.net ? Qu'est-il arrivé à jrandom? I2P est-il "
+"mort?"
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "J'ai une question !"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr "Paramétrage"
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+"Mon routeur est en ligne depuis plusieurs minutes mais a zéro ou très peu"
+" de connexions"
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "Pourquoi I2P est-il si lent ?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+"Il me manque beaucoup d'hôtes dans mon carnet d'adresses. Quels sont les "
+"bons liens d'abonnement ?"
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "Comment puis-je créer mon propre eepsite ?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "Questions sur les plugins I2P pour Bittorrent / I2PSnark / Azureus"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "Comment puis-je me connecter à IRC au sein de I2P ?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "Je ne peux pas accéder à des sites réguliers d'Internet à travers I2P."
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "Je ne peux pas accéder à des sites https:// ni ftp:// par I2P."
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr "Est-il possible d'utiliser I2P en tant que proxy SOCKS ?"
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Comment dois-je configurer mon navigateur ?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+"Comment puis-je accéder à la console Web à partir de mes autres machines,"
+" ou la protéger par mot de passe ?"
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr "Comment puis-je utiliser des applications depuis mes autres machines?"
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr "Comment puis-je réensemencer (reseed) manuellement ?"
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "Mon routeur utilise trop de CPU ?!?"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "Méprise"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr ""
+"Comment puis-je accéder à IRC, BitTorrent, ou d'autres services sur "
+"l'Internet régulier ?"
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+"Est-ce que mon routeur est un \"nœud de sortie\" (outproxy) vers "
+"l'Internet régulier ? Je ne veux pas qu'il le soit."
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+"Je suis opposé à certains types de contenus. Comment puis-je éviter d'en "
+"distribuer, d'en stocker ou d'y accéder ?"
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Erreurs et leurs solutions"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+"J'utilise FreeBSD et quand je lance I2P, je reçois une erreur concernant "
+"libm.so.4 !"
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+"Dans wrapper.log je vois une erreur communiquant "
+"Protocol family unavailable lorsque I2P se lance"
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "lien"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+"Bien qu'I2P aie été signalé comme capable de fonctionner sur un PC aussi "
+"maigre qu'un Pentium II bas de gamme avec 64 Mo de RAM, vous aurez une "
+"bien meilleure expérience sur un Pentium III (ou mieux) avec 128 Mo de "
+"RAM (ou plus). Un graphique comparant la "
+"performance des diverses JREs peut être trouvé à %(chart)s, mais en bref : c'est à tout possible, "
+"utilisez Sun/Oracle Java ou OpenJDK."
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+"I2P a été testé sur Windows, Linux, FreeBSD (voir la note ci-dessous), OSX, et OpenSolaris. Il ya des "
+"travaux en cours pour porter I2P sur la plate-forme Android."
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr "Voici quelques endroits, choisissez un ou plusieurs."
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "Discutez avec les développeurs sur IRC dans #I2P-dev"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+"S'il vous plaît inclure des informations pertinentes à partir des "
+"journaux de routage (router logs) et les journaux d'encapsulation "
+"(wrapper logs)."
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+"L'abonnement par défaut est à http://www.i2p2.i2p/hosts.txt qui est "
+"rarement mis à jour.⏎\n"
+"Si vous n'avez pas d'autre abonnement, vous risquez d'avoir souvent à "
+"utiliser des liens «jump»⏎\n"
+"ce qui est ennuyeux."
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+"Voici quelques autres liens d'abonnement du carnet d'adresses publiques. "
+"Vous pouvez ajouter un ou deux ⏎ \n"
+"à votre liste"
+" de souscription susidns. ⏎\n"
+"Vous n'avez pas besoin de les ajouter tous, car ils se synchronisent "
+"mutuellement à intervalles réguliers. ⏎ \n"
+"Les liens utilisant une application cgi-bin emploient diverses stratégies"
+" pour réduire ⏎ \n"
+"le nombre d'adresses livrées en double, elles doivent donc être plus "
+"efficace. ⏎ \n"
+"Notez que l'abonnement à un service de hosts.txt est un acte de "
+"«confiance», car un ⏎\n"
+"abonnement malveillant pourrait vous donner des adresses incorrectes. "
+"Alors, pensez-y si vous⏎\n"
+"voulez faire confiance à l'un d'eux. ⏎\n"
+"Les opérateurs de ces services peuvent avoir diverses politiques de "
+"listage des hôtes. ⏎ \n"
+"Ëtre présent sur cette listes n'implique pas l'approbation."
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+"Jrandom était le principal développeur de I2P et ⏎\n"
+"Syndie durant plusieurs années. ⏎"
+"\n"
+"Nous ne savons pas si ou quand jrandom reviendra. ⏎\n"
+"Les domaines *.i2p.net ont été laissés en dans un état de non-"
+"fonctionnement après une panne⏎\n"
+"électrique chez l'entreprise d'hébergement."
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+"Voir cette page pour le message d'adieu de "
+"jrandom et⏎\n"
+"des informations supplémentaires sur la migration des *.i2p.net vers ce site web."
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr "I2P reste en développement actif."
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+"Il ya beaucoup de causes possibles de l'utilisation élevée du processeur."
+" Voici une liste de choses à vérifier :"
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+"Essayez d'utiliser OpenJDK ou Sun/Oracle Java si il est disponible pour "
+"votre système. Vous pouvez vérifier⏎\n"
+"quelle version de Java vous avez installé en tapant java-version dans une ⏎ \n"
+"commande / invite du shell. La performance a tendance à souffrir avec "
+"d'autres implémentations de Java."
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+"Faites vous tourner un client BitTorrent sur ​​I2P ? Essayez de réduire :"
+" le nombre de torrents,⏎\n"
+"les limites de bande passante, ou essayez de l'éteindre complètement pour"
+" voir si cela aide."
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+"Est-ce que vos limites de bande passante trop élevées ? Il est possible "
+"que trop de trafic passe par votre ⏎ \n"
+"routeur I2P et qu'il soit surchargé. Essayez de réduire le réglage de "
+"pourcentage de bande passante partagée sur la page configuration."
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+"Assurez-vous que vous utilisez la dernière version de I2P afin d'obtenir "
+"les avantages de l'augmentation de la performance et des corrections de "
+"bugs."
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+"Est-ce que suffisamment de mémoire a été mise de côté pour une "
+"utilisation par I2P ? Regardez le graphique de la mémoire sur la page des"
+" graphiques de performance I2P pour voir ⏎\n"
+"si l'utilisation de la mémoire est \"rattachée\"— la JVM est en "
+"train de passer la plupart de son temps à faire de la⏎\n"
+"garbage collection. Augmentez le réglage "
+"wrapper.java.maxmemory dans wrapper.config ."
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+"Est-ce que l'usage du CPU est simplement plus élevé que ce que vous "
+"aimeriez, ou est-il rivé à 100% durant longtemps ?\n"
+"Si il est rivé, cela pourrait être un bug. Regarder dans les logs pour "
+"des indices."
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+"Vous utilisez peut-être la bibliothèque BigInteger basée sur Java au lieu"
+" de la version native, ⏎ \n"
+"en particulier si vous êtes sur un nouveau ou inhabituel OS ou matériel "
+"(OpenSolaris, mips, etc.) ⏎ \n"
+"Voir la page jbigi pour obtenir des "
+"instructions sur ⏎ \n"
+"le diagnostic, la construction et les méthodes d'essai."
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+"Si votre bibliothèque native jbigi fonctionne bien, le plus grand "
+"utilisateur de \n"
+"CPU peut être l'acheminement du trafic dans les tunnels participants. "
+"Celui-ci utilise du CPU\n"
+"parce que à chaque saut une couche de chiffrement doit être décodée.\n"
+"Vous pouvez limiter la participation trafic de deux façons - en réduisant"
+" le\n"
+"partage de bande passante sur\n"
+"confignet.jsp,\n"
+"ou en paramétrant router.maxParticipatingTunnels=nnn sur\n"
+"configadvanced.jsp."
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+"Hmm, I2P est un réseau anonyme, de sorte que c'est une question délicate."
+" ⏎ \n"
+"I2P est conçu pour résister à la censure, en fournissant un moyen pour "
+"chacun de communiquer librement. ⏎\n"
+"La meilleure façon de garder votre PC à l'écart de trafic (crypté) que "
+"vous n'aimez pas, est de ne pas utiliser I2P. ⏎\n"
+"La liberté d'expression a des coûts. ⏎\n"
+"Mais nous allons répondre à votre question en trois parties :"
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+"Distribution - Tout le trafic dans I2P est chiffré dans plusieurs "
+"couches. Vous ne savez pas\n"
+"le contenu, la source ou la destination d'un message. \n"
+"Tout le trafic que votre routez - transmettez - est interne au réseau "
+"I2P, vous n'êtes pas un nœud de sortie (outproxy)."
+"\n"
+"Votre seule alternative est de refuser d'acheminer\n"
+"tout trafic, en mettant votre bande passante partagée ou le nombre"
+" maximum de tunnels participants à 0 (voir ci-dessus).\n"
+"Ce serait bien de ne pas le faire, vous devriez aider le réseau en "
+"routant du trafic pour les autres.\n"
+"Plus de 95% des utilisateurs routent du trafic pour les autres."
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+"Stockage - I2P ne fait pas de stockage de contenu distribué. Vous "
+"deviez penser à ⏎\n"
+"Freenet. ⏎\n"
+"En exécutant I2P, le contenu de personne n'est stocké sur votre "
+"ordinateur."
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+"Accès - S'il ya des eepsites vous n'aimez pas, n'y allez pas ⏎ \n"
+"Ou, utilisez un proxy bloquant tel que Privoxy ou certains type de \"Net "
+"Nanny\" (logiciels de contrôle parental)."
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+"Non, c'est normal. ⏎\n"
+"Tous les routeurs s'adapter dynamiquement à l'évolution des conditions du"
+" réseau et des demandes."
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+"Vous devrez peut-être réamorcer (reseed) votre routeur I2P. Avec les "
+"versions récentes de I2P vous pouvez aller sur http://localhost:7657/configreseed"
+" et cliquer sur le bouton Sauvegarder et réamorcer. Si cette "
+"méthode ne fonctionne pas ou que vous utilisez une très ancienne version,"
+" vous devrez peut-être réamorcer "
+"manuellement."
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+"L'URL de réamorçage a changé il y a quelques années. Si ceci est votre "
+"première installation et que vous avez installé\n"
+"une vielle version (0.6.1.30 ou antérieure), ou\n"
+"vous n'avez pas exécuté I2P depuis longtemps, vous devez modifier l'URL "
+"puis\n"
+"cliquer sur \"Reseed\" sur la console afin de trouver d'autres routeurs.\n"
+"Après que votre routeur soit en marche,\n"
+"sur configadvanced.jsp,"
+"\n"
+"ajoutez la ligne i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OU i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (devrait "
+"fonctionner),\n"
+"puis cliquez sur \"Appliquer\", puis cliquez sur le lien \"réamorcer\" ou"
+" \"reseed\" sur la gauche."
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+"Cela marche si vous utilisez 0.6.1.27 ou plus ancienne.⏎\n"
+"Si vous utilisez la release 0.6.1.31 ou plus ancienne, vous n'aurez "
+"probablement pas besoin de faire cela.⏎\n"
+"Si vous utilisez la release 0.6.1.26 ou plus récente, soit suivez les⏎\n"
+"instructions de réamorçage manuel ci-"
+"dessous⏎\n"
+"ou installez la release la plus "
+"récente.⏎\n"
+"Méthode alternative possible - ajouter⏎\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/⏎"
+"\n"
+"à wrapper.config, arrêter le routeur complètement, puis le redémarrer, et"
+" cliquer \"reseed\".⏎\n"
+"Faites nous savoir si cela fonctionne."
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+"...mais vous devriez *vraiment* mettre à "
+"niveau vers la version la plus récente."
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+"Si vous routeur a 10 pairs actifs ou davantage, tout va bien. Des "
+"changements dans les releases 0.6.1.31 et 0.6.1.32 ont amélioré⏎\n"
+"l'efficacité  de votre router et réduit efficacement le nombre de pairs "
+"actifs.⏎\n"
+"Le router devrait maintenir des connexions vers quelques pairs "
+"tout le temps.⏎\n"
+"La meilleure façon de rester \"mieux connecté\" au réseau est de partager davantage de bande "
+"passante."
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+"Est-ce que mon routeur est un \"nœud de sortie\" (outproxy) vers "
+"l'Internet régulier ? Je ne veux pas qu'il le soit."
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+"Non. Contrairement à Tor,\n"
+"les \"noeuds de sortie\" ou \"outproxies\" ne sont pas une partie "
+"inhérente du réseau.\n"
+"Seuls les volontaires qui configurent et font fonctionner des "
+"applications séparées relaieront du trafic vers l'Internet régulier.\n"
+"Il y a très, très peu, de ceux-ci."
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+"Voir ci-dessus. Il y a très peu de \"outproxies\" HTTP, ils ne sont pas "
+"une partie intégrante du réseau,\n"
+"et ils peuvent ne pas être en fonctionnement.\n"
+"En outre, les anciens outproxies squid.i2p, true.i2p et krabs.i2p ont "
+"disparu.\n"
+"Le seul outproxy en ce moment est false.i2p.\n"
+"Pour l'utiliser, modifiez les réglages de "
+"mandataire i2ptunnel pour eepProxy\n"
+"et définissez votre liste de outproxy - mandataires sortants - à "
+"'false.i2p' (seul).\n"
+"Puis arrêtez et redémarrez le eepProxy.\n"
+"Si cela ne fonctionne pas, le outproxy n'est pas en service. Ce n'est pas"
+" la faute de I2P.\n"
+"Si votre principale raison d'utiliser un réseau anonyme est d'accéder aux"
+" sites de l'Internet régulier\n"
+"de façon anonyme, vous devriez probablement essayer Tor."
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+"Dans I2P, il n'y a pas besoin de HTTPS, comme tout le trafic est chiffré "
+"de bout en bout. ⏎\n"
+"FTP n'est pas pris en charge pour des raisons techniques."
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+"Il n'y a pas de \"outproxies\" FTP vers l'internet, il est même à "
+"craindre qu'il ne soit pas possible d'en mettre un en place. ⏎\n"
+"Tout autre type de outproxy peut fonctionner s'il est mis en place avec "
+"un tunnel standard. ⏎\n"
+"Si vous souhaitez mettre en place un certain type de outproxy, étudiez "
+"soigneusement les risques potentiels. ⏎\n"
+"La communauté I2P peut, ou peut ne pas être, en mesure d'aider concernant"
+" les aspects techniques, n'hésitez pas à demander."
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+"Comme expliqué à plusieurs reprises ci-dessus, tout outproxy existant "
+"n'est pas un élément essentiel du réseau. ⏎\n"
+"Ce sont des services gérés par des individus particuliers et ils peuvent "
+"ou non ⏎ \n"
+"être opérationnels à tout moment donné."
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
            \n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+"Mise à jour: grâce au travail de H2ik, il ya un outproxy https "
+"disponible pour être utilisé via I2P.\n"
+"Depuis I2P 0.8.4  le tunnel est"
+" configuré d'origine. 
            \n"
+"Dans le cas où le outproxy https n'est pas disponible dans votre version "
+"de I2P, vous pouvez l'ajouter facilement de la manière suivante :"
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+"Ouvrir Gestionnaire"
+" de tunnels I2P. Défilez jusqu'en bas."
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+"Dans Nouveau tunnel client, choisir dans la liste : CONNECT, "
+"cliquer Créer"
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+"Dans la nouvelle page, nommez et décrivez votre nouveau "
+"tunnel https comme vous le souhaitez. ⏎\n"
+"Le point d'accès est votre port local vers le nouveau proxy https "
+"recommandé 4445. ⏎\n"
+"outproxy devrait être l'adresse .i2p de l'outproxy, qui prend en "
+"charge le protocole HTTPS. ⏎\n"
+"Voir ce post sur le forum de h2ik pour "
+"l'adresse. ⏎\n"
+"Assurez-vous que sont cochées : Client partagé, Délai "
+"Connect, Autostart. ⏎\n"
+"Les autres options devraient être laissées aux valeurs par défaut. "
+"Cliquez sur Enregistrer. Dans gestionnaire tunnel, cliquez sur le bouton "
+"Démarrer à côté de votre nouveau tunnel."
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+"Dans Firefox, cliquez sur Outils (ou Options) > Options > "
+"Avancé > Réseau > Paramètres.⏎\n"
+"Décochez Utiliser ce serveur proxy pour tous les protocoles, "
+"mettez Proxy SSL : à localhost:4445."
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "Fait."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+"\n"
+"C'est une question à laquelle vous seulement pouvez répondre parce que la"
+" réponse correcte  dépend de vos comportements, votre\n"
+"modèle de menace, et combien vous faites "
+"confiance en l'opérateur de l'outproxy."
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+"Comme Tor, I2P ne chiffre pas l'Internet de façon magique.\n"
+"Vous êtes vulnérables à l'espionnage par les opérateurs de outproxy.\n"
+"La FAQ"
+" Tor\n"
+"fait un bon travail pour expliquer cela."
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+"De plus, vous pouvez être vulnérable à une complicité entre l'opérateur "
+"de l'outproxy\n"
+"et les opérateurs d'autres services I2P, si vous utilisez les mêmes "
+"tunnels (\"clients partagés\").\n"
+"Il y a une discussion complémentaire sur ceci, sur %(zzz)s."
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+"À moins qu'un outproxy n'ait été mis en place pour le service auquel vous"
+" voulez vous connecter, ceci ne peut pas être fait.\n"
+"Il y a seulement trois types d'outproxies redirigeant actuellement : "
+"HTTP, HTTP et courrier électronique. Notez qu'il n'y a pas de SOCKS "
+"outproxy.\n"
+"Si ce type de service est exigé, essayez Tor."
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+"Si vous considérez chaque eepsite qui aie jamais été créé, oui, la "
+"plupart d'entre eux sont en hors d'accès  - down -.\n"
+"Les gens et les eepsites vont et viennent.\n"
+"Une bonne façon de se lancer dans I2P est de vérifier une liste de "
+"eepsites qui sont actuellement en place.\n"
+"%(eepstatus)s piste les eepsites actifs."
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+"Cliquez sur le lien Site web\n"
+"en haut de la console de votre routeur pour obtenir des instructions."
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+"Pourquoi est-ce que les téléchargements, les torrents, la navigation Web,"
+" et tout le reste sont si lent sur ​​I2P ?\n"
+"Le chiffrement et le routage dans le réseau I2P ajoutent une quantité "
+"importante de surplus de données (overhead),  cela limite la bande "
+"passante.\n"
+"L'anonymat n'est pas gratuit."
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+"En outre, vous et tout le monde avez probablement besoin d'augmenter vos "
+"limites de bande passante.\n"
+"Deux paramètres principaux sont les limiteurs de débit entrant et sortant"
+" sur\n"
+"la page de configuration "
+".\n"
+"Avec les réglages par défaut de 32 KBps vous n'obtiendrez généralement "
+"pas mieux que 15 KBps de transfert de données dans I2PSnark.\n"
+"Augmenter les paramètres (mais en restant dans les limites de votre "
+"connexion actuelle)\n"
+"augmentera la vitesse potentielle de transfert pour I2PSnark et toutes "
+"les autres applications."
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+"Aussi, avez-vous configuré suffisament de bande passante partagée, pour "
+"permettre aux tunnels participants\n"
+"d'être acheminés à travers votre routeur ? Croyez-le ou non, autoriser la"
+" circulation de \"traffic participant\"\n"
+"vous permet de rester bien intégré dans le réseau, et aide vos propres "
+"vitesses de transfert."
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+"I2P est un travail en cours. Beaucoup d'améliorations et corrections sont"
+" mises en œuvre, et\n"
+"d'une manière générale, utiliser la dernière version aidera votre "
+"performance.\n"
+"Si vous ne l'avez pas, installez la "
+"dernière version."
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+"Voyez la\n"
+"FAQ Bittorrent I2P"
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+"\n"
+"Un tunnel vers le serveur IRC principal à l'intérieur de I2P, nommé "
+"Irc2P, est créé lorsque I2P est installé (voir\n"
+"la page de "
+"configuration de I2PTunnel), \n"
+"et il est démarré automatiquement lorsque le routeur I2P se lance. Pour "
+"s'y connecter, dites à votre\n"
+"client IRC de se connecter à localhost 6668. Les "
+"utilisateurs de clients comme-XChat peuvent créer un\n"
+"nouveau réseau avec le serveur localhost/6668 (n'oubliez pas"
+" de cocher la case "Bypass\n"
+"proxy serverr" si vous avez un serveur proxy configuré)."
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface.  However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+"Pour des raisons de sécurité, la console d'admin du routeur n'écoute par "
+"défaut que\n"
+"les connexions sur l'interface locale. Cependant, avec un peu de hacking,"
+"\n"
+"vous pouvez la rendre accessible à distance :"
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"with 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+"Ouvrez ~/.i2p/clients.config et remplacez 
            ⏎\n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            ⏎\n"
+" avec 
            ⏎\n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+"Allez à http://localhost:7657/configui⏎"
+"\n"
+"et ajoutez un nom d'utilisateur de console et un mot de passe si désiré."
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+"Allez à  "
+"http://localhost:7657/index.jsp \n"
+"et cliquez sur \"Redémarrage en douceur\", qui redémarre la JVM et "
+"recharge les applications clientes"
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+"Après que cela se soit déclenché, vous devriez maintenant être en mesure "
+"d'atteindre votre console à distance. Rechargez le routeur depuis⏎\n"
+"http://127.0.0.1:7657 et vous serez invité à entrer un nom d'utilisateur "
+"et mot de passe que vous avez spécifié à l'étape 2\n"
+"ci-dessus si votre navigateur supporte l'authentification par fenêtre "
+"popup. Note : le\n"
+"0.0.0.0 ci-dessus spécifie une interface, pas un "
+"réseau ou un masque réseau. 0.0.0.0 ⏎\n"
+"signifie \"lier à toutes les interfaces\", de sorte qu'il peut être "
+"accessible sur 127.0.0.1:7657 ainsi que ⏎\n"
+"tout LAN / WAN IP."
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+"Par défaut, l'interface I2CP du routeur (port 7654) s'attache à l'adresse"
+" 127.0.0.1. Pour lier à 0.0.0.0, réglez⏎\n"
+"l'option de configuration avancée du routeur "
+"i2cp.tcp.bindAllInterfaces=true puis redémarrez."
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "Qu'est ce qu'un \"eepsite\" ?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+"Un eepsite est un site qui est hébergé anonyme - vous pouvez y accéder en"
+"\n"
+"paramétrant le proxy HTTP de votre navigateur pour utiliser le proxy web "
+"(typiquement, il\n"
+"écoute sur le port localhost 4444), puis naviguer vers le site."
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+"La configuration proxy pour les différents navigateurs est sur une \n"
+"page séparée avec des copies d'écran. Des paramétrages plus avancées "
+"avec des outils externes\n"
+"sont possibles, mais pourraient présenter des fuites dans votre "
+"configuration."
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+"x est le nombre de pairs vers lesquels vous avez envoyé ou reçu un "
+"message⏎\n"
+"avec succès durant la dernière minute, y est le nombre de pairs vu dans "
+"la dernière ⏎\n"
+"heure environ."
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+"Le proxy SOCKS fonctionne à partir de la release 0.7.1. SOCKS 4/4a/5 sont"
+" pris en charge. \n"
+"Il n'y a pas d'outproxy SOCKS donc il est d'une utilité limitée."
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+"En outre, de nombreuses applications font fuire des informations\n"
+"sensibles qui pourraient vous identifier sur l'Internet. I2P filtre "
+"uniquement\n"
+"les données de connexion, mais si le logiciel que vous souhaitez exécuter"
+" envoie cette\n"
+"information en tant que contenu, I2P n'a aucun moyen de protéger votre "
+"anonymat.\n"
+"Par exemple certaines applications de messagerie envoient l'adresse IP de"
+" la machine\n"
+"sur laquelle elles sont en cours d'exécution vers un serveur de "
+"messagerie. Il n'existe\n"
+"aucun moyen pour I2P de filtrer ceci, utiliser I2P pour 'socksifier' des "
+"applications existantes\n"
+"est possible, mais extrêmement dangereux."
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+"Si vous souhaitez plus d'informations sur l'application de proxy socks "
+"malgré tout,\n"
+"il ya quelques conseils utiles sur la page socks "
+"."
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+"Ok, voici un récapitulatif des ports par défaut (tout est configurable⏎\n"
+"à travers différents réglages, bien sûr) :"
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+" ⏎\n"
+"Remarque : les nouvelles installations depuis la release 0.7.8 "
+"n'utilisent pas le port 8887; elles sélectionnent un port aléatoire ⏎\n"
+"entre 9000 et 31000, lorsque le programme est exécuté pour la première "
+"fois. ⏎\n"
+"Le port sélectionné est affiché sur la page de configuration du"
+" routeur."
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+"    "
+msgstr ""
+"UDP sortant depuis le port aléatoire noté sur la page de configuration "
+"vers des ports UDP distants arbitraires, permettant réponses"
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+"    "
+msgstr ""
+"TCP sortant depuis des ports élevés aléatoires vers des ports TCP "
+"distants arbitraires"
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+"    "
+msgstr ""
+"(facultatif, mais recommandé) UDP entrant vers le port mentionné sur "
+"la page de "
+"configuration à partir d'emplacements arbitraires"
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
            \n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+"(facultatif, mais recommandé) TCP entrant vers le port noté sur cette "
+"page de configuration"
+" à partir de positions arbitraires
            \n"
+"TCP entrant peut être désactive sur la page configuration."
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
            \n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+"UDP sortant sur port 123, permettant réponses  
            \n"
+"Cela est nécessaire pour la synchronisation de l'horloge interne de I2P "
+"(via SNTP - \n"
+"par interrogation d'un hôte SNTP aléatoire dans pool.ntp.org ou autre\n"
+"serveur que vous spécifiez)"
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+"Ports I2P locaux, n'écoutent que les connexions locales par "
+"défaut,\n"
+"sauf indication contraire :"
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"1900: UPnP SSDP UDP multicast listener.⏎\n"
+"Ne peut pas être changé. Lié à toutes les interfaces.⏎\n"
+"Il peut être désactivé sur confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+"2827: pont BOB, un plus haut niveau de socket API pour les "
+"clients⏎\n"
+"Désactivé par défaut.⏎\n"
+"Il peut être activé/désactivé sur configclients.jsp.⏎"
+"\n"
+"Il peut être changé dans le fichier bob.config ."
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4444: proxy HTTP⏎\n"
+"Il peut être désactivé ou changé, sur la console routeur dans la page "
+"i2ptunnel.⏎\n"
+"Il peut aussi être configuré pour être lié à une interface spécifique ou "
+"à toutes les interfaces."
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4445: proxy HTTPS⏎\n"
+"Il peut être désactivé ou changé, sur la console routeur dans la page "
+"i2ptunnel.⏎\n"
+"Il peut aussi être configuré pour être lié à une interface spécifique ou "
+"à toutes les interfaces."
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"6668: proxy IRC⏎\n"
+"Il peut être désactivé ou changé, sur la console routeur dans la page "
+"i2ptunnel.⏎\n"
+"Il peut aussi être configuré pour être lié à une interface spécifique ou "
+"à toutes les interfaces."
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7652: UPnP HTTP TCP event listener.⏎\n"
+"Lié aux adresses LAN.⏎\n"
+"Il peut être changé  avec la config avancée i2np.upnp.HTTPPort=nnnn.⏎\n"
+"Il peut être désactivé sur confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7653: UPnP SSDP UDP search response listener.⏎\n"
+"Lié à toutes les interfaces.⏎\n"
+"Il peut être changé dansavec la config avancée i2np.upnp.SSDPPort=nnnn.⏎\n"
+"Il peut être désactivé sur confignet.jsp"
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+"7654: port protocole client I2P, utilisé par les apps clientes.⏎\n"
+"Il peut être changé vers un port différent sur⏎\n"
+"configclients.jsp⏎\n"
+"mais ce n'est pas recommandé.⏎\n"
+"Il peut être lié à une interface différente ou à toutes les interfaces, "
+"ou désactivé, sur⏎\n"
+"configclients.jsp."
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+"7655: UDP pour pont SAM, un socket API de plus haut niveau pour "
+"clients\n"
+"Seulement ouvert lorsqu'un client SAM V3 demande une session UDP.\n"
+"Peut être activé / désactivé sur configclients.jsp.\n"
+"Il est possible de le modifier dans le fichier clients.config avec une "
+"option dans la ligne de commande de SAM : sam.udp.port = nnnn."
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+"7656: Pont SAM, un socket API de plus haut niveau pour clients\n"
+"Désactivé par défaut pour les nouvelles installations depuis la "
+"release 0.6.5.\n"
+"Peut être activé / désactivé sur configclients.jsp.\n"
+"Peut être modifié dans le fichier clients.config ."
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+"7657: Votre console routeur\n"
+"Il est possible de le désactiver dans le fichier clients.config .\n"
+"Il peut également être configuré pour être lié à une interface spécifique"
+" ou à toutes les interfaces dans ce fichier."
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+"7658: Votre Eepsite\n"
+"Il est possible de le désactiver dans le fichier clients.config .\n"
+"Il peut également être configuré pour être lié à une interface spécifique"
+" ou à toutes les interfaces dans le fichier jetty.xml ."
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7659: Courrier sortant vers smtp.postman.i2p\n"
+"Il est possible de le désactiver ou le modifier sur la page "
+"d'i2ptunnel dans la console du routeur.\n"
+"Il peut également être configuré pour être lié à une interface spécifique"
+" ou à toutes les interfaces."
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7660: Courrier entrant depuis pop.postman.i2p\n"
+"Il est possible de le désactiver ou le modifier sur la page "
+"d'i2ptunnel dans la console du routeur.\n"
+"Il peut également être configuré pour être lié à une interface spécifique"
+" ou à toutes les interfaces. "
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"8998: mtn.i2p2.i2p (Monotone - désactivé par défaut)\n"
+"Il est possible de le désactiver ou de le modifier sur la page "
+"d'i2ptunnel dans la console du routeur.\n"
+"Il est également possible de le configurer pour être lié à une interface "
+"spécifique ou à toutes les interfaces."
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"31000: Connexion locale au port du canal de contrôle wrapper.\n"
+"Sortant à 32000 seulement, n'écoute pas sur ce port. \n"
+"Commence à 31000 et incrémente jusqu'à 31999 à la recherche d'un port "
+"libre.\n"
+"Pour le changer, voir la\n"
+"documentation wrapper.\n"
+"Davantage dinformations ci-dessous."
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"32000: canal de contrôle local pour le service wrapper\n"
+"Pour changer, voir la\n"
+"documentation wrapper.\n"
+"pour davantage d'informations voir ci "
+"dessous."
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally.  You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+"Les ports locaux I2P et les ports de i2ptunnel n'ont pas besoin d'être "
+"accessibles à partir ⏎\n"
+"des machines distantes, mais *devraient* être accessibles localement. "
+"Vous pouvez également créer ⏎\n"
+"des ports supplémentaires pour les instances de i2ptunnel via "
+"http://localhost:7657/i2ptunnel/ ⏎\n"
+"(et, en retour, pouvoir nécessiter d'obtenir que votre pare-feu permette "
+"l'accès local, mais ⏎ \n"
+"pas l'accès à distance, à moins que vous le souhaitiez)."
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance.  You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+"Alors, pour résumer, ien ne doit être accessible par des pairs distants "
+"non sollicités, mais⏎\n"
+"si vous pouvez configurer votre NAT / pare-feu pour l'entée de données "
+"UDP et TCP outbound facing "
+"port, vous⏎\n"
+"obtiendrez une meilleure performance. Vous aurez aussi besoin d'être en "
+"mesure d'envoyer des paquets UDP sortants\n"
+"à des pairs distants arbitraires (bloquer des IP au hasard avec quelque "
+"chose comme PeerGuardian ⏎ \n"
+"vous blesse seulement vous seul - ne pas le faire)."
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr "Pourquoi est-ce que I2P écoute le port 32000 ?"
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+"Le wrapper service Java Tanuki que nous utilisons ouvre ce port-lié au "
+"localhost-afin ⏎\n"
+"de communiquer avec le logiciel en cours d'exécution à l'intérieur de la "
+"JVM. Lorsque la JVM est lancé, il est donné une clé ⏎\n"
+"de sorte qu'il puisse se connecter au wrapper. Ensuite la JVM établit sa "
+"connexion ⏎\n"
+"au wrapper, le wrapper refuse toutes connexions supplémentaires."
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the  \n"
+"wrapper documentation."
+msgstr ""
+"Davantage d'information peut être trouvée dans la\n"
+"documentation wrapper."
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+"Un routeur I2P nécessite seulement d'être amorcé une fois pour se joindre"
+" au réseau pour la première fois. ⏎  Réamorcer n'est rien de plus "
+"qu'envoyer des requêtes HTTP GET ⏎\n"
+"pour récupérer la liste répertoire et télécharger plusieurs fichiers "
+"\"routerInfo\" ⏎\n"
+"à partir d'une URL d'amorçage prédéfinie."
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+"Un symptôme typique d'un réamorçage échoué est l'indicateur \"Connus\"\n"
+"(dans la barre latérale gauche de la console du routeur) affichant une "
+"très faible valeur\n"
+"(souvent moins de 5) qui n'augmente pas. Cela peut se produire, entre "
+"autres choses,\n"
+"si votre pare-feu limite le trafic sortant, et a bloqué la demande de "
+"réamorçage."
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr "Pour réamorcer un routeur I2P manuellement, procédez comme suit :"
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr "Stoppez votre routeur I2P"
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+"Ouvrez http://netdb.i2p2.de/ en "
+"utilisant un navigateur web"
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr ""
+"Sauvegardez une douzaine de fichiers \"routerInfo\" vers votre répertoire"
+" \"netDb\" dans I2P"
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr "Lancer votre routeur I2P"
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+"Lorsque vous essayez de démarrer le routeur à l'aide \"start i2prouter\","
+" vous pourriez voir la sortie suivante:"
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+"\n"
+"Pour être inclusif et essayer de faire en sorte que I2P fonctionne sur "
+"autant de systèmes\n"
+"que possible, jusqu'à I2P 0.8.9, nous avons utilisé un wrapper java\n"
+"compilé pour FreeBSD 6.x. Si vous recevez ce message d'erreur il vous "
+"manque très probablement des bibliothèques de compatibilité nécessaires."
+"\n"
+"Ces bibliothèques peuvent être installées en exécutant les étapes "
+"suivantes :"
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+"Basculer vers l'utilisateur root au moyen de su ou se logger"
+" comme root."
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+"Si vous ne pouvez pas installer ces ces libraries de compatibilité (ou ne"
+" le voulez pas), d'autres⏎\n"
+"possibilités seraient de compiler le wrapper pour votre⏎\n"
+"système, en lançant I2P avec le script runplain.sh, ou "
+"vous pouvez⏎\n"
+"remplacer le wrapper avec un issu du tarball source."
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+"Pour la release 0.8.9 de I2P, le wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+"Dans wrapper.log je vois une erreur qui indique "
+"\"Famille de protocole indisponible\" quand la console "
+"routeur se charge"
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+"Fréquemment, cette erreur se produit avec n'importe quel logiciel Java "
+"activé réseau, sur certains systèmes qui sont configurés pour utiliser "
+"IPv6 par défaut. Il ya quelques façons de résoudre cela :"
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+"Sur le systèmes basés Linux, vous pouvez echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr "Regarder les lignes suivantes dans wrapper.config."
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+"Si les lignes sont là, mettez-les hors commentaire en supprimant les "
+"\"#\". Si les lignes ne sont pas là, ajoutez les, sans les \"#\"."
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+"Une autre option serait de retirer le(s) ::1 depuis "
+"~/.i2p/clients.config"
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+"ATTENTION : pour que des modifications dans "
+"wrapper.config prennent effet, vous devez complètement\n"
+"arrêter le routeur et le wrapper. Cliquer Redémarrer dans votre\n"
+"console du routeur ne relira PAS ce fichier ! Vous devez\n"
+"cliquez cliquer Arrêt, attendre 11 minutes, puis lancer I2P."
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+"Formidable ! retrouvez-nous sur le serveur IRC irc.freenode.net #i2p, ou "
+"postez-les au\n"
+"forum et nous les publierons ici (avec\n"
+"la réponse, nous l'espérons)."
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "Lois allemandes"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr "Réseau anonyme I2P"
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+"Couche de communication distribuée, anonyme, et pair-à-pair, construite "
+"avec des outils open source et conçue pour exécuter n'importe quel "
+"service Internet traditionnel tels que courriel, IRC ou hébergement web."
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr "Que peut faire I2P pour vous ?"
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+"Le réseau I2P fournit une solide protection de la vie privée pour la "
+"communication sur Internet. De nombreuses activités qui risqueraient de "
+"dévoiler votre vie privée sur l'Internet public peuvent être effectuées "
+"anonymement à l'intérieur de I2P."
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr "Obtenir I2P %(version)s"
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "Qu'est-ce que I2P ?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+"I2P est un réseau overlay (superposé) anonyme - un réseau au sein d'un "
+"réseau. Il est destiné à protéger les communications contre la "
+"surveillance par rafle - dragnet surveillance -, et la surveillance par "
+"des tiers tels que les fournisseurs d'accès à Internet.\n"
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+"I2P est utilisé par beaucoup de gens qui se soucient de leur vie privée :"
+" des militants, des peuples opprimés, des journalistes et des "
+"dénonciateurs, ainsi que la personne ordinaire.\n"
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+"Aucun réseau ne peut être \"parfaitement anonyme\".  L'objectif continu "
+"de I2P est de rendre les attaques de plus en plus difficiles à monter. "
+"Son anonymat deviendra plus grand en même temps que la taille augmentera "
+"et avec les recherches universitaires en cours.\n"
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+"I2P est disponible sur ordinateurs de bureau, systèmes incorporés (comme "
+"le Raspberry Pi) et téléphones Android. Aidez à passer le mot !\n"
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr "Lire davantage …"
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr "Que pouvez-vous faire avec I2P ?"
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+"Email Interface web mail intégrée, "
+"plugin pour email sans serveur."
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+"Navigation web : Sites web "
+"anonymes, passerelles vers et depuis l'Internet public."
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+"Blogging et forums "
+"Plugins pour Blogging et Syndie."
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+"Hébergement de sites web : "
+"Serveur web anonyme intégré."
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+"Tchat en temps réel : "
+"Messagerie instantanée et clients IRC."
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+"Partage de fichiers : Clients "
+"ED2K et Gnutella, client BitTorrent intégré."
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+"Stockage de fichiers"
+" décentralisé : Plugin pour système de fichiers distribué Tahoe-LAFS."
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr ""
+"Davantage d'applications supportées "
+"…"
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr "Actualités & mises à jour"
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr "Liens & ressources recommandées"
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+"Voir aussi la page avec\n"
+"liens vers des présentations, des vidéos et des "
+"tutoriels au sujet de I2P."
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr "I2P sur le web"
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr "Amis de I2P"
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr "Davantage de projets et documentation"
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "Presse"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr "Forums, actualités sur ce site web, autres"
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr "Très vieilles choses"
+
diff --git a/i2p2www/translations/fr/LC_MESSAGES/research.po b/i2p2www/translations/fr/LC_MESSAGES/research.po
new file mode 100644
index 00000000..c2422da0
--- /dev/null
+++ b/i2p2www/translations/fr/LC_MESSAGES/research.po
@@ -0,0 +1,158 @@
+# French translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Boxoa590, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-08-11 14:55+0000\n"
+"Last-Translator: Boxoa590\n"
+"Language-Team: French "
+"(http://www.transifex.com/projects/p/I2P/language/fr/)\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/research/index.html:2
+msgid "Academic Research"
+msgstr "Recherche académique"
+
+#: i2p2www/pages/site/research/index.html:4
+msgid ""
+"Academic research and analysis of I2P is an important part of ensuring "
+"that the software and network performs as expected and is safe for users "
+"in hostile environments."
+msgstr ""
+"La recherche académique et l'analyse de I2P est un élément important afin"
+" de s'assurer que le logiciel et le réseau fonctionne comme prévu et est "
+"sans danger pour les utilisateurs dans des environnements hostiles."
+
+#: i2p2www/pages/site/research/index.html:8
+#, python-format
+msgid ""
+"\n"
+"There is a large research community investigating a wide range of aspects"
+" of\n"
+"anonymity. For a current and comprehensive list of relevant papers, see "
+"the\n"
+"Free Haven Anonymity Bibliography.\n"
+"I2P benefits from much of the research into Tor and onion routing, but "
+"there is\n"
+"little dedicated research interest into the theory behind I2P, and the "
+"choices\n"
+"and tradeoffs that the network makes. This presents a unique opportunity "
+"for\n"
+"original research.\n"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:18
+#, python-format
+msgid ""
+"A list of known published papers about I2P is available here."
+msgstr ""
+"Une liste des documents publiés connus sur I2P est disponible içi."
+
+#: i2p2www/pages/site/research/index.html:22
+msgid "Testing Attacks on I2P"
+msgstr "Tester des attaques sur I2P"
+
+#: i2p2www/pages/site/research/index.html:24
+msgid ""
+"I2P can be run as a separate test network by controlling the locations "
+"that a new router reseeds from so that it only finds other test routers."
+msgstr ""
+"I2P peut être exécuté en tant que réseau de test séparé, en contrôlant "
+"les emplacements depuis lesquels un nouveau routeur se réamorce, de sorte"
+" qu'il ne trouve que d'autres routeurs de test."
+
+#: i2p2www/pages/site/research/index.html:28
+msgid ""
+"The standard mode of operation is to have one JVM per router instance; "
+"hence running multiple copies of I2P on a single machine is inadvisable, "
+"both due to the potential resource drain and the certain port conflicts. "
+"To better facilitate setting up small test networks, I2P has a "
+"multirouter mode which enables multiple distinct routers to be run in the"
+" same JVM."
+msgstr ""
+"Le mode de fonctionnement standard, c'est d'avoir une JVM par instance "
+"routeur, par conséquent l'exécution de plusieurs copies d'I2P sur une "
+"seule machine est déconseillé, tant en raison de la fuite des ressources "
+"potentielles et de la certitude de conflits de ports. Pour mieux "
+"faciliter la mise en place de petits réseaux d'essais, I2P a un mode "
+"multirouteur qui permet à plusieurs routeurs distincts d'être exécutés "
+"dans la même JVM."
+
+#: i2p2www/pages/site/research/index.html:32
+msgid ""
+"MultiRouter can be started from the i2p base directory by running the "
+"below command."
+msgstr ""
+"MultiRouteur peut être démarré à partir du répertoire de base I2P en "
+"exécutant la commande ci-dessous."
+
+#: i2p2www/pages/site/research/index.html:37
+msgid ""
+"Additionally, I2P can be started in a virtual network mode. This mode "
+"disables all transports, allowing the router to be tested in isolation "
+"without network traffic. To enable this mode, add "
+"i2p.vmCommSystem=true to the router.config before starting."
+msgstr ""
+"En outre, I2P peut être démarré dans un mode de réseau virtuel. Ce mode "
+"désactive tous les transports, ce qui permet au routeur d'être testé "
+"isolément, sans le trafic réseau. Pour activer ce mode, avant de "
+"commencer, ajouter i2p.vmCommSystem=true à router.config ."
+
+#: i2p2www/pages/site/research/index.html:41
+msgid "Testing the Live I2P Network"
+msgstr "Test en direct du réseau I2P"
+
+#: i2p2www/pages/site/research/index.html:43
+#, python-format
+msgid ""
+"If you are planning on conducting research on the live I2P network, "
+"please contact us before you commence your "
+"testing. While we do not discourage researchers from responsibly testing "
+"their ideas on the live network, if an attack becomes apparent and we "
+"don't have any line of communication then we will end up taking "
+"countermeasures which could interfere with the test."
+msgstr ""
+"Si vous prévoyez de mener des recherches en direct sur le réseau I2P, "
+"s'il vous plaît nous contacter  avant de "
+"commencer vos tests. Bien que nous ne nous décourageons pas les "
+"chercheurs de tester leurs idées de façon responsable sur le réseau "
+"direct, si une attaque devient apparente et que nous n'avons pas de moyen"
+" de communication, nous finirons par prendre des contre-mesures qui "
+"pourraient interférer avec le test."
+
+#: i2p2www/pages/site/research/questions.html:2
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:4
+msgid "Network database"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:6
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:8
+msgid "Tunnels and Destinations"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:10
+msgid "Unidirectional tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:16
+msgid "Multihoming"
+msgstr ""
+
diff --git a/i2p2www/translations/it/LC_MESSAGES/get-involved.po b/i2p2www/translations/it/LC_MESSAGES/get-involved.po
new file mode 100644
index 00000000..c9662221
--- /dev/null
+++ b/i2p2www/translations/it/LC_MESSAGES/get-involved.po
@@ -0,0 +1,4160 @@
+# Italian translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# coso , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-11-24 11:34+0000\n"
+"Last-Translator: coso \n"
+"Language-Team: Italian "
+"(http://www.transifex.com/projects/p/I2P/language/it/)\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/get-involved/donate.html:2
+#: i2p2www/pages/site/get-involved/index.html:77
+msgid "Donate"
+msgstr "Dona"
+
+#: i2p2www/pages/site/get-involved/donate.html:4
+msgid ""
+"Thank you for your interest in contributing to I2P!\n"
+"The details of how you\n"
+"can make your contribution are provided below."
+msgstr ""
+"Grazie per il tuo interesse nel contribuire a I2P!\n"
+"I dettagli su come puoi fornire il tuo\n"
+"contributi sono forniti sotto."
+
+#: i2p2www/pages/site/get-involved/donate.html:11
+#: i2p2www/pages/site/get-involved/donate.html:27
+#, python-format
+msgid ""
+"As of %(date)s, eche|on has been running a\n"
+"%(cointype)s account for the I2P project.\n"
+"If you'd like to donate using %(cointype)s, just transfer your\n"
+"desired amount of coins to the account %(account)s\n"
+"and leave eche|on a note if you'd like your donation to be\n"
+"mentioned on the I2P webpage."
+msgstr ""
+"Al %(date)s,  eche|on  ha tenuto su un account\n"
+"%(cointype)s per il progetto I2P.\n"
+"Se vuoi effettuare una donazione tramite %(cointype)s, trasferisci\n"
+"l'importo desiderato all'account %(account)s\n"
+"e lascia un messaggio a  eche|on  se vuoi che la tua donazione\n"
+"sia citata sulla pagina web di I2P."
+
+#: i2p2www/pages/site/get-involved/donate.html:22
+#: i2p2www/pages/site/get-involved/donate.html:38
+msgid "For easy usage, use the QR code below!"
+msgstr "Per un facile utilizzo, utilizza il QR code qui sotto."
+
+#: i2p2www/pages/site/get-involved/donate.html:44
+#, python-format
+msgid "You can donate direct via PayPal to the account \"%(account)s\"."
+msgstr "Puoi donare direttamente via PayPal all'account  \"%(account)s\"."
+
+#: i2p2www/pages/site/get-involved/donate.html:50
+msgid "One time donation:"
+msgstr "Donazione singola:"
+
+#: i2p2www/pages/site/get-involved/donate.html:64
+msgid "Donate 10 €/month for 12 months:"
+msgstr "Dona 10 €/mese per 12 mesi:"
+
+#: i2p2www/pages/site/get-involved/donate.html:72
+#: i2p2www/pages/site/get-involved/donate.html:84
+#: i2p2www/pages/site/get-involved/donate.html:96
+#: i2p2www/pages/site/get-involved/donate.html:108
+msgid "I2P donation "
+msgstr "Donazioni I2p"
+
+#: i2p2www/pages/site/get-involved/donate.html:78
+msgid "Donate 20 €/month for 12 months:"
+msgstr "Dona 20 €/mese per 12 mesi;"
+
+#: i2p2www/pages/site/get-involved/donate.html:90
+msgid "Donate 30 €/month for 12 months:"
+msgstr "Dona 30 €/mese per 12 mesi;"
+
+#: i2p2www/pages/site/get-involved/donate.html:102
+msgid "Donate 50 €/month for 12 months:"
+msgstr "Dona 50 €/mese per 12 mesi;"
+
+#: i2p2www/pages/site/get-involved/donate.html:117
+msgid "Flattr this"
+msgstr "Usa Flattr"
+
+#: i2p2www/pages/site/get-involved/donate.html:122
+msgid ""
+"If you want to keep more or less anonymous, the option to send money via "
+"mail is also available. But it is less secure\n"
+"as the envelope can be lost on the way to us."
+msgstr ""
+"Se vuoi rimanere più o meno anonimo, c'è l'opzione di effetuare una "
+"donazione tramite posta. Ma questo è meno sicuro\n"
+"visto che la busta potrebbe andare perduta nel tragitto."
+
+#: i2p2www/pages/site/get-involved/donate.html:126
+#, python-format
+msgid ""
+"If you'd like to donate via  snail mail, send an email to %(email)s\n"
+" and you'll receive an email with instructions detailing how to proceed."
+msgstr ""
+"Se vuoi effettuare una donazione tramite posta ordinaria, invia un'email "
+"a %(email)s\n"
+"e riceverai tramite email le istruzioni con i dettagli su come procedere."
+
+#: i2p2www/pages/site/get-involved/donate.html:131
+#, python-format
+msgid ""
+"In the meantime, feel free to take a look at the generous donations that "
+"have been\n"
+"given in support of the I2P Project at the hall of fame."
+msgstr ""
+"Il frattempo, sentiti libero di dare uno sguardo alle donazioni che sono "
+"state effettuate\n"
+"a supporto del Progetto I2P all'indirizzo hall"
+" of fame."
+
+#: i2p2www/pages/site/get-involved/index.html:2
+msgid "Get Involved!"
+msgstr "Unisciti a noi!"
+
+#: i2p2www/pages/site/get-involved/index.html:4
+msgid "We need your help!"
+msgstr "Abbiamo bisogno del tuo aiuto!"
+
+#: i2p2www/pages/site/get-involved/index.html:5
+msgid ""
+"To get involved, please feel free to join us on the #i2p IRC channel (on\n"
+"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or "
+"irc.postman.i2p)."
+msgstr ""
+"Per unirti a noi, sentiti libero di venirci a trovare sul canale IRC #i2p"
+" (su\n"
+"irc.freenode.net, o all'interno di I2P su irc.freeshcoffee.i2p o "
+"irc.postman.i2p)."
+
+#: i2p2www/pages/site/get-involved/index.html:9
+#, python-format
+msgid ""
+"If you're interested in joining our team, please"
+" get in\n"
+"touch as we're always looking for eager contributors!"
+msgstr ""
+"Se sei interessato ad unirti al nostro  team, "
+"resta in\n"
+"contatto con noi: siamo sempre avidi di contributi!"
+
+#: i2p2www/pages/site/get-involved/index.html:13
+msgid ""
+"We need help in many areas, and you don't need to know Java to "
+"contribute!\n"
+"Here's a list to help you get started!"
+msgstr ""
+"Abbiamo bisogno di aiuto in numerose aree, e non hai bisogno di conoscere"
+" Java per contribuire!\n"
+"Qui c'è una lista di cose con cui puoi partire!"
+
+#: i2p2www/pages/site/get-involved/index.html:18
+msgid "Spread the Word!"
+msgstr "Diffondi il Verbo!"
+
+#: i2p2www/pages/site/get-involved/index.html:19
+msgid ""
+"Tell people about I2P on forums, blogs, and comments to articles.\n"
+"Fix up the Wikipedia article about I2P in your language.\n"
+"Tell your friends."
+msgstr ""
+"Parla alle persone di I2P sui forum, sui blog, e nei commenti agli "
+"articoli.\n"
+"Aggiorna la pagina di Wikipedia su I2P nella tua lingua.\n"
+"Dillo ai tuoi amici."
+
+#: i2p2www/pages/site/get-involved/index.html:24
+msgid "Testing"
+msgstr "Test"
+
+#: i2p2www/pages/site/get-involved/index.html:25
+#, python-format
+msgid ""
+"Run the latest builds from monotone\n"
+"and report results on #i2p or as bugs on Trac."
+msgstr ""
+"Esegui la build più aggiornata da monotone\n"
+"e condividi i risultati su #i2p o i bug su Trac."
+
+#: i2p2www/pages/site/get-involved/index.html:30
+msgid "Documentation"
+msgstr "Documentazione"
+
+#: i2p2www/pages/site/get-involved/index.html:31
+msgid ""
+"Help fix the parts of the website that are outdated or incomplete.\n"
+"Translate pages into other languages."
+msgstr ""
+"Aiuta a sistemare le parti del sito che sono obsolete o incomplete.\n"
+"Traduci le pagne in altre lingue."
+
+#: i2p2www/pages/site/get-involved/index.html:35
+msgid "Pictures"
+msgstr "Immagini"
+
+#: i2p2www/pages/site/get-involved/index.html:36
+msgid "Make some more pictures, fix the old ones on the website"
+msgstr "Fa altre foto, sistema le vecchie nel sito web."
+
+#: i2p2www/pages/site/get-involved/index.html:39
+msgid "Content"
+msgstr "Contenuti"
+
+#: i2p2www/pages/site/get-involved/index.html:40
+msgid "Make an eepsite! Add some content! Contribute to the community!"
+msgstr ""
+"Realizza un eepsite! Aggiungi qualche contenuto! Contribuisci alla "
+"comunità!"
+
+#: i2p2www/pages/site/get-involved/index.html:43
+msgid "Services"
+msgstr "Sercizi"
+
+#: i2p2www/pages/site/get-involved/index.html:44
+msgid ""
+"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n"
+"a naming service, a search engine, an eepsite monitor... many of these\n"
+"aren't that hard."
+msgstr ""
+"Fornisci un servizio su un eepsite. Potrebbe essere un proxy, un forum, "
+"un tracker,\n"
+"un server dei nomi, un motore di ricerca, un eepsite monitor.. molti di "
+"questi\n"
+"non sono così complicati."
+
+#: i2p2www/pages/site/get-involved/index.html:49
+msgid "Applications"
+msgstr "Applicazioni"
+
+#: i2p2www/pages/site/get-involved/index.html:50
+#, python-format
+msgid ""
+"Write or port applications for I2P! There's some guidelines and\n"
+"a list of ideas on the applications page."
+msgstr ""
+"Scrivi o porta applicazioni per I2P! Ci sono alcune linee guida e\n"
+"una lista di idee sulla  pagina delle "
+"applicazioni."
+
+#: i2p2www/pages/site/get-involved/index.html:54
+msgid "Coding"
+msgstr "Coding"
+
+#: i2p2www/pages/site/get-involved/index.html:55
+#, python-format
+msgid ""
+"There's plenty to do if you know Java or are ready to learn.\n"
+"Check for open tickets on Trac\n"
+"or the TODO list on %(zzz)s for\n"
+"some ideas on where to start.\n"
+"See the new developer's guide for details."
+msgstr ""
+"E' pieno di cose da fare se conosci Java o sei pronto ad impararlo.\n"
+"Controlla i ticket aperti su Trac\n"
+"o la TODO listi su %(zzz)s per\n"
+"qualche idea su come partire.\n"
+"Visita la guida per nuovi sviluppatori per i "
+"dettagli."
+
+#: i2p2www/pages/site/get-involved/index.html:64
+msgid "Translation"
+msgstr "Traduzione"
+
+#: i2p2www/pages/site/get-involved/index.html:65
+#, python-format
+msgid ""
+"Help translate the website and the software into your language.\n"
+"See the new translator's guide for details."
+msgstr ""
+"Aiuta a tradurre il sito ed il software nella tua lingua.\n"
+"Visita la guida per i nuovi traduttori per i"
+" dettagli."
+
+#: i2p2www/pages/site/get-involved/index.html:69
+msgid "Analysis"
+msgstr "Analisi"
+
+#: i2p2www/pages/site/get-involved/index.html:70
+#, python-format
+msgid ""
+"Study or test the code to look for vulnerabilities.\n"
+"Both anonymity vulnerabilities from the various\n"
+"threat models,\n"
+"and DOS and other weaknesses due to securities holes,\n"
+"need researching."
+msgstr ""
+"Studia o testa il codice alla ricerca di vulnerabilità. Sia vulnerabilità"
+" dal punto di vista dell'anonimato nel nostro modello dei pericoli sia DOS ed altre "
+"debolezze dovute a falle nella sicurezza hanno bisogno di ricerche "
+"approfondite."
+
+#: i2p2www/pages/site/get-involved/roadmap.html:2
+msgid "Roadmap"
+msgstr "Roadma"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:7
+msgid ""
+"Include some seed data in the distribution so a central reseed location "
+"isn't required?"
+msgstr ""
+"Introdurre alcuni dati di seed nella distribuzione affinché non sia "
+"necessario un server di seed centralizzato?"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:10
+#, python-format
+msgid ""
+"Reachability Mapping / handle peers partially reachable / enhanced restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:13
+msgid "Improve help pages and website"
+msgstr "Migliora le pagine di aiuto e il sito"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:14
+msgid "More translations"
+msgstr "Altre traduzioni"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:15
+msgid "SSU disconnect message"
+msgstr "Messaggio di disconnessione SSU"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:16
+msgid "Iterative floodfill lookups"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:21
+msgid "Full review of anonymity issues and other vulnerabilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:22
+msgid ""
+"Reduce memory usage, remove debugging overhead, make it run better on "
+"slow and embedded machines"
+msgstr ""
+"Ridurre il consumo di memoria, rimuovere gli overhead di debug, "
+"migliorare le performance su macchine lente ed embedded."
+
+#: i2p2www/pages/site/get-involved/roadmap.html:25
+msgid "Docs"
+msgstr "Documenti"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:30
+msgid "Full restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:35
+msgid "Tunnel mixing and padding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:36
+msgid "User defined message delays"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:39
+#, python-format
+msgid ""
+"Please see the TODO list for more detailed info "
+"about some of these tasks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:2
+msgid "To Do List"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:4
+msgid "I2P Project Targets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:5
+#, python-format
+msgid ""
+"Below is a more detailed (yet still incomplete) discussion of the major "
+"areas\n"
+"of future development on the core I2P network, spanning the plausibly "
+"planned\n"
+"releases. This does not include stego transports, porting to wireless "
+"devices,\n"
+"or tools to secure the local machine, nor does it include client "
+"applications\n"
+"that will be essential in I2P's success. There are probably other things "
+"that\n"
+"will come up, especially as I2P gets more peer review, but these are the "
+"main\n"
+"'big things'. See also the roadmap. Want to "
+"help?\n"
+"Get involved!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:54
+msgid "Core functionality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:52
+msgid "link"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:18
+#: i2p2www/pages/site/get-involved/todo.html:57
+msgid "NAT/Firewall bridging via 1-hop restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:21
+#: i2p2www/pages/site/get-involved/todo.html:130
+msgid "High degree transport layer with UDP, NBIO, or NIO"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:24
+#: i2p2www/pages/site/get-involved/todo.html:218
+msgid "NetworkDB and profile tuning and ejection policy for large nets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:242
+msgid "Security / anonymity"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:30
+#: i2p2www/pages/site/get-involved/todo.html:245
+msgid ""
+"Per-hop tunnel id & new permuted TunnelVerificationStructure "
+"encryption"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:33
+#: i2p2www/pages/site/get-involved/todo.html:295
+msgid "Strict ordering of participants within tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:36
+msgid "Randomly permuted tunnel lengths"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:39
+#: i2p2www/pages/site/get-involved/todo.html:357
+msgid "Full blown n-hop restricted routes with optional trusted links"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:42
+#: i2p2www/pages/site/get-involved/todo.html:376
+msgid "Hashcash for routerIdentity, destination, and tunnel request"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:45
+#: i2p2www/pages/site/get-involved/todo.html:405
+msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:48
+#: i2p2www/pages/site/get-involved/todo.html:442
+msgid "Stop & go mix w/ garlics & tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:52
+#: i2p2www/pages/site/get-involved/todo.html:456
+msgid "Performance"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:62
+msgid "Implemented in I2P 0.6.0.6"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:63
+msgid ""
+"The functionality of allowing routers to fully participate within the "
+"network \n"
+"while behind firewalls and NATs that they do not control requires some "
+"basic \n"
+"restricted route operation (since those peers will not be able to receive"
+" \n"
+"inbound connections). To do this successfully, you consider peers one of"
+" \n"
+"two ways:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:73
+msgid ""
+"Peers who have reachable interfaces - these peers do not need to \n"
+"do anything special"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:77
+msgid ""
+"Peers who do not have reachable interfaces - these peers must "
+"build \n"
+"a tunnel pointing at them where the gateway is one of the peers they have"
+" \n"
+"established a connection with who has both a publicly reachable interface"
+" \n"
+"and who has agreed to serve as their 'introducer'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:85
+msgid ""
+"To do this, peers who have no IP address simply connect to a few peers, \n"
+"build a tunnel through them, and publish a reference to those tunnels "
+"within \n"
+"their RouterInfo structure in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:90
+msgid ""
+"When someone wants to contact any particular router, they first must get"
+" \n"
+"its RouterInfo from the network database, which will tell them whether "
+"they \n"
+"can connect directly (e.g. the peer has a publicly reachable interface) \n"
+"or whether they need to contact them indirectly. Direct connections occur"
+" \n"
+"as normal, while indirect connections are done through one of the "
+"published \n"
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:98
+msgid ""
+"When a router just wants to get a message or two to a specific hidden "
+"peer, \n"
+"they can just use the indirect tunnel for sending the payload. However, \n"
+"if the router wants to talk to the hidden peer often (for instance, as "
+"part \n"
+"of a tunnel), they will send a garlic routed message through the indirect"
+" \n"
+"tunnel to that hidden peer which unwraps to contain a message which "
+"should \n"
+"be sent to the originating router. That hidden peer then establishes an \n"
+"outbound connection to the originating router and from then on, those two"
+" \n"
+"routers can talk to each other directly over that newly established "
+"direct \n"
+"connection."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:109
+msgid ""
+"Of course, that only works if the originating peer can receive "
+"connections \n"
+"(they aren't also hidden). However, if the originating peer is hidden, "
+"they \n"
+"can simply direct the garlic routed message to come back to the "
+"originating \n"
+"peer's inbound tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:115
+msgid ""
+"This is not meant to provide a way for a peer's IP address to be "
+"concealed, \n"
+"merely as a way to let people behind firewalls and NATs fully operate "
+"within \n"
+"the network. Concealing the peer's IP address adds a little more work, as"
+" \n"
+"described below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:121
+msgid ""
+"With this technique, any router can participate as any part of a tunnel."
+" \n"
+"For efficiency purposes, a hidden peer would be a bad choice for an "
+"inbound \n"
+"gateway, and within any given tunnel, two neighboring peers wouldn't want"
+" \n"
+"to be hidden. But that is not technically necessary."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:133
+msgid "Both UDP and NIO have been Implemented in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:134
+msgid ""
+"Standard TCP communication in Java generally requires blocking socket \n"
+"calls, and to keep a blocked socket from hanging the entire system, those"
+" \n"
+"blocking calls are done on their own threads. Our current TCP transport \n"
+"is implemented in a naive fashion - for each peer we are talking to, we \n"
+"have one thread reading and one thread writing. The reader thread simply"
+" \n"
+"loops a bunch of read() calls, building I2NP messages and adding them \n"
+"to our internal inbound message queue, and the writer thread pulls "
+"messages \n"
+"off a per-connection outbound message queue and shoves the data through \n"
+"write() calls."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:145
+msgid ""
+"We do this fairly efficiently, from a CPU perspective - at any time, \n"
+"almost all of these threads are sitting idle, blocked waiting for "
+"something \n"
+"to do. However, each thread consumes real resources (on older Linux "
+"kernels, \n"
+"for instance, each thread would often be implemented as a fork()'ed "
+"process). \n"
+"As the network grows, the number of peers each router will want to talk \n"
+"with will increase (remember, I2P is fully connected, meaning that any \n"
+"given peer should know how to get a message to any other peer, and "
+"restricted \n"
+"route support will probably not significantly reduce the number of "
+"connections \n"
+"necessary). This means that with a 100,000 router network, each router \n"
+"will have up to 199,998 threads just to deal with the TCP connections!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:157
+msgid ""
+"Obviously, that just won't work. We need to use a transport layer that \n"
+"can scale. In Java, we have two main camps:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:162
+#, python-format
+msgid ""
+"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:165
+msgid ""
+"Sending and receiving UDP datagrams is a connectionless operation - if \n"
+"we are communicating with 100,000 peers, we simply stick the UDP packets"
+" \n"
+"in a queue and have a single thread pulling them off the queue and "
+"shoving \n"
+"them out the pipe (and to receive, have a single thread pulling in any \n"
+"UDP packets received and adding them to an inbound queue)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:172
+msgid ""
+"However, moving to UDP means losing the benefits of TCP's ordering, "
+"congestion \n"
+"control, MTU discovery, etc. Implementing that code will take significant"
+" \n"
+"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n"
+"a while ago I was taking some measurements in the simulator and on the \n"
+"live net, and the vast majority of messages transferred would fit easily"
+" \n"
+"within a single unfragmented UDP packet, and the largest of the messages"
+" \n"
+"would fit within 20-30 packets. As mule pointed out, TCP adds a "
+"significant \n"
+"overhead when dealing with so many small packets, as the ACKs are within"
+" \n"
+"an order of magnitude in size. With UDP, we can optimize the transport \n"
+"for both efficiency and resilience by taking into account I2P's "
+"particular \n"
+"needs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:185
+msgid "It will be a lot of work though."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:188
+msgid "NIO or NBIO"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:189
+msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:192
+msgid ""
+"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java"
+" \n"
+"developers to take advantage of the operating system's nonblocking IO \n"
+"capabilities - allowing you to maintain a large number of concurrent IO \n"
+"operations without requiring a separate thread for each. There is much \n"
+"promise with this approach, as we can scalable handle a large number of \n"
+"concurrent connections and we don't have to write a mini-TCP stack with \n"
+"UDP. However, the NIO packages have not proven themselves to be battle-"
+"ready, \n"
+"as the Freenet developer's found. In addition, requiring NIO support "
+"would \n"
+"mean we can't run on any of the open source JVMs like Kaffe, \n"
+"as GNU/Classpath has only "
+"limited \n"
+"support for NIO. (note: this may not be the case anymore, as there \n"
+"has been some progress on Classpath's NIO, but it is an unknown "
+"quantity)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:206
+#, python-format
+msgid ""
+"Another alternative along the same lines is the Non"
+" \n"
+"Blocking I/O package - essentially a cleanroom NIO implementation \n"
+"(written before NIO was around). It works by using some native OS code \n"
+"to do the nonblocking IO, passing off events through Java. It seems to \n"
+"be working with Kaffe, though there doesn't seem to be much development \n"
+"activity on it lately (likely due to 1.4's NIO deployment)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:221
+msgid ""
+"Within the current network database and profile management "
+"implementation, \n"
+"we have taken the liberty of some practical shortcuts. For instance, we \n"
+"don't have the code to drop peer references from the K-buckets, as we \n"
+"don't have enough peers to even plausibly fill any of them, so instead, \n"
+"we just keep the peers in whatever bucket is appropriate. Another example"
+" \n"
+"deals with the peer profiles - the memory required to maintain each "
+"peer's \n"
+"profile is small enough that we can keep thousands of full blown profiles"
+" \n"
+"in memory without problems. While we have the capacity to use trimmed \n"
+"down profiles (which we can maintain 100s of thousands in memory), we \n"
+"don't have any code to deal with moving a profile from a \"minimal "
+"profile\" \n"
+"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to"
+" simply \n"
+"eject a profile altogether. It just wouldn't be practical to write that \n"
+"code yet, since we aren't going to need it for a while."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:236
+msgid ""
+"That said, as the network grows we are going to want to keep these "
+"considerations \n"
+"in mind. We will have some work to do, but we can put it off for later."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:248
+#: i2p2www/pages/site/get-involved/todo.html:332
+#, python-format
+msgid ""
+"Addressed in I2P 0.5 as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:251
+msgid ""
+"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n"
+"going to Dave, then to Charlie, then Bob, and finally Alice "
+"(A<--B<--C<--D<--E), \n"
+"all five of them will know they are participating in tunnel \"123\", as \n"
+"the messages are tagged as such. What we want to do is give each hop "
+"their \n"
+"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n"
+"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n"
+"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n"
+"the tunnel had the same tunnel ID, collusion attacks aren't much work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:261
+msgid ""
+"Adding a unique tunnel ID per hop isn't hard, but by itself, "
+"insufficient. \n"
+"If Dave and Bob are under the control of the same attacker, they wouldn't"
+" \n"
+"be able to tell they are in the same tunnel due to the tunnel ID, but \n"
+"would be able to tell by the message bodies and verification structures \n"
+"by simply comparing them. To prevent that, the tunnel must use layered \n"
+"encryption along the path, both on the payload of the tunneled message \n"
+"and on the verification structure (used to prevent simple tagging "
+"attacks). \n"
+"This requires some simple modifications to the TunnelMessage, as well \n"
+"as the inclusion of per-hop secret keys delivered during tunnel creation"
+" \n"
+"and given to the tunnel's gateway. We must fix a maximum tunnel length \n"
+"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n"
+"of the 16 delivered secret keys, in reverse order, and to encrypt the \n"
+"signature of the hash of the (encrypted) payload at each step. The "
+"gateway \n"
+"then sends that 16-step encrypted message, along with a 16-step and "
+"16-wide \n"
+"encrypted mapping to the first hop, which then decrypts the mapping and \n"
+"the payload with their secret key, looking in the 16-wide mapping for \n"
+"the entry associated with their own hop (keyed by the per-hop tunnel ID)"
+" \n"
+"and verifying the payload by checking it against the associated signed \n"
+"hash."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:282
+msgid ""
+"The tunnel gateway does still have more information than the other peers"
+" \n"
+"in the tunnel, and compromising both the gateway and a tunnel participant"
+" \n"
+"would allow those peers to collude, exposing the fact that they are both"
+" \n"
+"in the same tunnel. In addition, neighboring peers know that they are \n"
+"in the same tunnel anyway, as they know who they send the message to (and"
+" \n"
+"with IP-based transports without restricted routes, they know who they \n"
+"got it from). However, the above two techniques significantly increase \n"
+"the cost of gaining meaningful samples when dealing with longer tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:298
+msgid "Implemented in release 0.6.2"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:301
+#, python-format
+msgid ""
+"As Connelly proposed to deal with the\n"
+"predecessor attack (2008\n"
+"update), keeping the order of peers within our tunnels consistent \n"
+"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n"
+"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n"
+"get to substantially sample Alice's peer selection group. We may even \n"
+"want to explicitly allow Bob to participate in Alice's tunnels in only \n"
+"one way - receiving a message from Dave and sending it to Charlie - and \n"
+"if any of those peers are not available to participate in the tunnel (due"
+" \n"
+"to overload, network disconnection, etc), avoid asking Bob to participate"
+" \n"
+"in any tunnels until they are back online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:316
+msgid ""
+"More analysis is necessary for revising the tunnel creation - at the \n"
+"moment, we simply select and order randomly within the peer's top tier \n"
+"of peers (ones with fast + high capacity)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:321
+msgid ""
+"Adding a strict ordering to peers in a tunnel also improves the anonymity"
+" \n"
+"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway"
+" \n"
+"is always the same would be particularly damning. However, peers with \n"
+"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n"
+"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n"
+"duration) minutes, use a 1-hop tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:338
+msgid ""
+"Without tunnel length permutation, if someone were to somehow detect that"
+" \n"
+"a destination had a particular number of hops, it might be able to use "
+"that \n"
+"information to identify the router the destination is located on, per the"
+" \n"
+"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n"
+"receives a tunnel message from Charlie and forwards it to Alice, Bob "
+"knows \n"
+"Alice is the final router in the tunnel. If Bob were to identify what "
+"destination \n"
+"that tunnel served (by means of colluding with the gateway and harvesting"
+" \n"
+"the network database for all of the LeaseSets), he would know the router"
+" \n"
+"on which that destination is located (and without restricted routes, that"
+" \n"
+"would mean what IP address the destination is on)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:350
+msgid ""
+"It is to counter user behavior that tunnel lengths should be permuted, \n"
+"using algorithms based on the length requested (for example, the 1/MTBF \n"
+"length change for 0-hop tunnels outlined above)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:360
+msgid ""
+"The restricted route functionality described before was simply a "
+"functional \n"
+"issue - how to let peers who would not otherwise be able to communicate \n"
+"do so. However, the concept of allowing restricted routes includes "
+"additional \n"
+"capabilities. For instance, if a router absolutely cannot risk "
+"communicating \n"
+"directly with any untrusted peers, they can set up trusted links through"
+" \n"
+"those peers, using them to both send and receive all of its messages. \n"
+"Those hidden peers who want to be completely isolated would also refuse \n"
+"to connect to peers who attempt to get them to (as demonstrated by the \n"
+"garlic routing technique outlined before) - they can simply take the "
+"garlic \n"
+"clove that has a request for delivery to a particular peer and tunnel \n"
+"route that message out one of the hidden peer's trusted links with "
+"instructions \n"
+"to forward it as requested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:379
+#, python-format
+msgid ""
+"Within the network, we will want some way to deter people from consuming"
+" \n"
+"too many resources or from creating so many peers to mount a Sybil \n"
+"attack. Traditional techniques such as having a peer see who is "
+"requesting \n"
+"a resource or running a peer aren't appropriate for use within I2P, as \n"
+"doing so would compromise the anonymity of the system. Instead, we want \n"
+"to make certain requests \"expensive\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:387
+msgid ""
+"Hashcash is one technique that \n"
+"we can use to anonymously increase the \"cost\" of doing certain "
+"activities, \n"
+"such as creating a new router identity (done only once on installation),"
+" \n"
+"creating a new destination (done only once when creating a service), or \n"
+"requesting that a peer participate in a tunnel (done often, perhaps 2-300"
+" \n"
+"times per hour). We don't know the \"correct\" cost of each type of "
+"certificate \n"
+"yet, but with some research and experimentation, we could set a base "
+"level \n"
+"that is sufficiently expensive while not an excessive burden for people \n"
+"with few resources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:398
+msgid ""
+"There are a few other algorithms that we can explore for making those \n"
+"requests for resources \"nonfree\", and further research on that front is"
+" \n"
+"appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:408
+#, python-format
+msgid ""
+"To powerful passive external observers as well as large colluding "
+"internal \n"
+"observers, standard tunnel routing is vulnerable to traffic analysis "
+"attacks \n"
+"- simply watching the size and frequency of messages being passed between"
+" \n"
+"routers. To defend against these, we will want to essentially turn some \n"
+"of the tunnels into its own mix cascade - delaying messages received at \n"
+"the gateway and passing them in batches, reordering them as necessary, \n"
+"and injecting dummy messages (indistinguishable from other \"real\" "
+"tunnel \n"
+"messages by peers in the path). There has been a significant amount of \n"
+"research \n"
+"on these algorithms that we can lean on prior to implementing the various"
+" \n"
+"tunnel mixing strategies."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:421
+msgid ""
+"In addition to the anonymity aspects of more varied tunnel operation, \n"
+"there is a functional dimension as well. Each peer only has a certain \n"
+"amount of data they can route for the network, and to keep any particular"
+" \n"
+"tunnel from consuming an unreasonable portion of that bandwidth, they \n"
+"will want to include some throttles on the tunnel. For instance, a tunnel"
+" \n"
+"may be configured to throttle itself after passing 600 messages (1 per \n"
+"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n"
+"last minute). Excess messages may be delayed or summarily dropped. With \n"
+"this sort of throttling, peers can provide ATM-like QoS support for their"
+" \n"
+"tunnels, refusing to agree to allocate more bandwidth than the peer has \n"
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:434
+msgid ""
+"In addition, we may want to implement code to dynamically reroute tunnels"
+" \n"
+"to avoid failed peers or to inject additional hops into the path. This \n"
+"can be done by garlic routing a message to any particular peer in a "
+"tunnel \n"
+"with instructions to redefine the next-hop in the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:445
+msgid ""
+"Beyond the per-tunnel batching and mixing strategy, there are further \n"
+"capabilities for protecting against powerful attackers, such as allowing"
+" \n"
+"each step in a garlic routed path to define a delay or window in which \n"
+"it should be forwarded on. This would enable protections against the long"
+" \n"
+"term intersection attack, as a peer could send a message that looks "
+"perfectly \n"
+"standard to most peers that pass it along, except at any peers where the"
+" \n"
+"clove exposed includes delay instructions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:457
+#, python-format
+msgid ""
+"Performance related improvements are listed on the\n"
+"Performance page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2
+msgid "Bounty Arabic translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3
+#: i2p2www/pages/site/get-involved/bounties/index.html:119
+msgid "Arabic translation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P echelon set out this bounty for translation\n"
+"of the I2P web page and I2P router console into Arabic."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12
+msgid "This bounty is set into 2 subparts:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14
+msgid "Part 1 is translation of the webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17
+msgid ""
+"For collecting the bounty of 20 BTC you need to translate the following "
+"pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25
+msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27
+msgid ""
+"Part 2 is the translation of the router console. The router console was\n"
+"partly translated and the bounty of 80 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34
+msgid "Judge is echelon."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2
+msgid "Bounty creating a I2P native Bitcoin client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3
+msgid "BTC I2P native client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to create a I2P native Bitcoin client. \n"
+"It should integrate with other client via the I2P network and via "
+"gateways to\n"
+"the existant bitcoin network."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15
+msgid "Judge is psychonaut who donated the first 30 € to this bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
+msgid "Bounty datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:3
+msgid "datastore"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:6
+msgid ""
+"To improve I2P's usage and to be independent of routers \n"
+"online status we want a datastorage as a extension to I2P.\n"
+"Like in Freenet the datastorage should be distributed and every\n"
+"participating node should be able to configure his options.\n"
+"The files should be saved in chunks and at least 2-3 times to\n"
+"obtain redundancy. Usage of storage space should be auto balanced.\n"
+"As it is a extra application, it should work flawless within I2P and\n"
+"cooperate nice with the I2P router. Maybe a integration within the\n"
+"webpage/router could be done."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:17
+msgid ""
+"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n"
+"\"eepsites in datastorage\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:21
+msgid ""
+"The frost for I2P datastorage bounty is paid for a frost like program \n"
+"with which files/messages are stored into database and got from database."
+"\n"
+"It needs to work with a GUI."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:26
+msgid ""
+"The eepsite served out of I2P datastorage extends a I2P router to send\n"
+"out eepsites out of the I2P datastorage. All files for eepsites need to "
+"be\n"
+"saved inside of datastorage and are taken from it.\n"
+"Extension:\n"
+"For better integration all datastorage participants could serve that "
+"eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:36
+msgid ""
+"For bounties to be declared done and paid, we need the program AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2
+msgid "Bounty I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3
+msgid "I2P Ubuntu/Debian package"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6
+msgid ""
+"For the future of I2P and in order to attract more people\n"
+"to I2P, this bounty was set for including an I2P package into the Ubuntu "
+"and Debian \n"
+"archive mirrors.\n"
+"To claim this bounty, the I2P router package needs to be available from\n"
+"Ubuntu and Debian archive mirrors and Debian bug \n"
+"448638 \n"
+"needs to be closed successfully."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2
+msgid "Bounty I2PHex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3
+msgid "i2phex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2PHex P2P ArneBab setout the bounty for implementing actual\n"
+"Phex code onto I2PHex."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:2
+msgid "Bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:5
+msgid "Bounties for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:6
+msgid ""
+"While we always gratefully accept any contributions of code, \n"
+"documentation, and the like, there are other ways to help I2P move \n"
+"forward.  As with any open source project, our goals would be achieved "
+"more \n"
+"rapidly if we were able to support all of our contributors to work on \n"
+"I2P full time.  However, as with any open source project, that's not a \n"
+"possibility.  Instead, we are making use of a bounty system, whereby \n"
+"anyone can get support for working on something that people want \n"
+"implemented, and people who want to contribute to I2P can be assured that"
+" \n"
+"their support goes to what they care about."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:18
+msgid ""
+"We are also keeping open the ability for people who want to support I2P \n"
+"but don't have strong feelings about the bounties available.  Those "
+"people\n"
+"can simply put their trust in the I2P team to do what we feel is best by\n"
+"donating to a catch-all general fund that will be used as deemed \n"
+"necessary - allocated to various bounties, covering incidentals (hosting,"
+" \n"
+"etc), and the like."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:27
+msgid "Current bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Name"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Status"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Judge"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Dev"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Bounty"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:32
+msgid "Frost for I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:33
+#: i2p2www/pages/site/get-involved/bounties/index.html:40
+#: i2p2www/pages/site/get-involved/bounties/index.html:47
+#: i2p2www/pages/site/get-involved/bounties/index.html:54
+#: i2p2www/pages/site/get-involved/bounties/index.html:75
+#: i2p2www/pages/site/get-involved/bounties/index.html:82
+msgid "Proposal in development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:35
+#: i2p2www/pages/site/get-involved/bounties/index.html:42
+#: i2p2www/pages/site/get-involved/bounties/index.html:49
+#: i2p2www/pages/site/get-involved/bounties/index.html:56
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+#: i2p2www/pages/site/get-involved/bounties/index.html:97
+msgid "vacant"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:39
+msgid "Eepsites served out of I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:46
+msgid "Backporting Phex code onto I2PHex"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:53
+msgid "I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:60
+msgid "Bitcoin client for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:61
+msgid "Done, phase of verification"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:67
+msgid "Unit tests and Multi-router Simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:68
+msgid "Partly done, partly in work, partly still open"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:89
+msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:94
+msgid "Bundling bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:95
+msgid "Proposed"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:102
+msgid "Claimed bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:107
+msgid "Make I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:114
+msgid "Setting up a SILC server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:124
+msgid "Datastore over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:129
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
+msgid "Russian translation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:134
+msgid "Swarming file transfer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:139
+msgid "Streaming library window size"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:144
+msgid "IRC connect time monitor"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:149
+msgid "Unit tests (part 1)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:161
+msgid ""
+"Dev lists anyone who may already be working on the bounty - collaboration"
+" is\n"
+"preferred, so if you're interested in working on it, please contact one "
+"of the\n"
+"people listed!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2
+msgid "Bounty I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3
+msgid "native IPv6 I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n"
+"To claim this bounty, the I2P router needs to run full on native\n"
+"IPv6 connections like it does on IPv4."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:17
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
+msgid ""
+"For bounties to be declared done and paid, we need the plugin AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:2
+msgid "NetDB Backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:3
+msgid "netDB backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:7
+msgid ""
+"The current NetDB implementation (namely the FloodFill system)\n"
+"needs to be extended with another backend to improve reliability,\n"
+"reduce attack surface and solve the scalability issue for the \n"
+"coming years."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:14
+msgid ""
+"A solution likely based on a DHT will be investigated and \n"
+"finally implemented."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2
+msgid "Bounty russian translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P a anonymous donator set out the bounty for translation\n"
+"of the I2P web page and I2P router console into russian language."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17
+msgid ""
+"For collecting the bounty of $115 USD you need to translate the following"
+" pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30
+msgid ""
+"Part 2 is the translation of the router console. The whole router console"
+" needs\n"
+"to be translated to collect the bounty of $115 USD."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37
+msgid "Judge is the russian donor."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:2
+msgid "Bounty migrate I2P IRC to SILC"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:3
+msgid "I2P silc server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:7
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to setup and host a I2P SILC server.   \n"
+"This will allow people to send files over their messaging servers and "
+"have intrinsic security built into the protocol."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:12
+msgid ""
+"A silc server needs to be set up and run for at least 3 month time to get"
+" payed. \n"
+"A second server should be set up, to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:16
+msgid ""
+"Bounty was withdrawn and money donated to returningnovice and general "
+"fund."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:22
+msgid "Judge is An Anonymous Secret Society, society@mail.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3
+msgid "Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7
+msgid ""
+"Beside of I2P we want to encourage users\n"
+"to care more about anonymity and security. As I2P is a low \n"
+"latency network with its natural limits, the software SYNDIE\n"
+"can overcome some of these limits and provide better anonymity\n"
+"for people who really need it."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14
+msgid ""
+"For our bad sake the syndie project was out of development for \n"
+"quite a long time yet (5 years). To get a fresh and new built \n"
+"with needed bugfixes we set out this bounty. Also syndie needs\n"
+"some enhancements and a better GUI for users to work with it.\n"
+"Current bounty sum is 50 Bitcoin."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22
+msgid ""
+"The latest Syndie coding rally did improve the situation of the\n"
+"Syndie package dramatically. A new Syndie package with bugfixes\n"
+"was created and made available on different webpages.\n"
+"As a result of this work, the bounty sum was reduced and\n"
+"the withdrawn money moved to the IPv6 bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2
+msgid "Bounty unittests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3
+msgid "unit test"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7
+msgid ""
+"To improve I2P's maintainability, we want to have a solid set of\n"
+"automated unit tests for the critical code.  While we do have some\n"
+"unit tests at the moment, they are ad-hoc and partly unfinished.  \n"
+"This bounty is for someone to check the existing tests and move over\n"
+"old ones to jUnit, automate their execution, extend them to provide \n"
+"better code coverage, and publish the report online.  Its a massive \n"
+"effort, but can be broken down into phases, listed below (phase 2 \n"
+"must occur first, but further phases may happen in any order).\n"
+"As this needs some reading of code, it is the best start point for\n"
+"new devs to get a good overview of I2P code and coding. A good job\n"
+"for college students, interns or anyone who is just interested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20
+msgid ""
+"Take care! Jobs and bounties shuffled a bit!\n"
+"Phase 6,7 and 8 are still open!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112
+#, python-format
+msgid "Phase %(phase)s:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27
+msgid "CI jenkins and IRC bot"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114
+#, python-format
+msgid "Bounty: %(euro)s €"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29
+msgid "server runs and this section is blocked"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31
+msgid ""
+"To collect this bounty, a continuous integration server (Jenkins,\n"
+"old name was Hudson) must be set up and a connected IRC bot needs \n"
+"to set up in the channel #i2p-dev on IRC2p network to print out\n"
+"results of build tests.
            \n"
+"The server needs to be run long term."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41
+msgid "Check existing SDK tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69
+msgid "paid to str4d"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45
+#, python-format
+msgid ""
+"To collect this bounty, the existing SDK tests must be checked \n"
+"and made to work again. The need to be integrated into the ant \n"
+"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g."
+" \n"
+"Clover).  The ant script\n"
+"must be capable of generating test status results as a web page, \n"
+"which will be published online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56
+msgid "SDK test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80
+msgid "paid to unittests dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60
+msgid ""
+"To collect this bounty, the automated unit tests of the SDK \n"
+"(i2p/core/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67
+msgid "Router test migration"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71
+msgid ""
+"As with phase 2, the existing unit tests for the router must be\n"
+"moved over to the automated system."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78
+msgid "Router test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82
+msgid ""
+"To collect this bounty, the automated unit tests of the router \n"
+"(i2p/router/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89
+msgid "Streaming lib tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94
+msgid ""
+"To collect this bounty, a new set of unit tests must meet a \n"
+"measured code coverage of 90% of the streaming lib \n"
+"(i2p/apps/ministreaming/ and i2p/apps/streaming/)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102
+msgid "Unit tests coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106
+msgid ""
+"To collect this bounty, all above unit tests must meet the 100%\n"
+"coverage marker (except for log statements)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113
+msgid "MultiRouter simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115
+msgid "will be split in more sub-tasks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117
+msgid ""
+"To collect this bounty, the existing in-memory multi-router\n"
+"simulation must be checked, made work again and extend to simulate\n"
+"lots of routers in memory on a single machine. This bounty will\n"
+"be split in more fine grained subworks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126
+msgid ""
+"Judge on all these works is the donor and donor decides if a phase is\n"
+"called succesfull done and money can be paid."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2
+msgid "Bounty I2P vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3
+msgid "vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P torrent P2P I setout the bounty for a working I2P vuze\n"
+"plugin.\n"
+"The plugin needs to be official and submitted to vuze for publication\n"
+"on their webpage/repository for plugins.\n"
+"It should be easy to install and configured, work smooth and flawless.\n"
+"Configuration should be friendly to starters and made easy to be "
+"anonymous.\n"
+"It should work with *.b32.i2p destinations as with signed (516++ bits) \n"
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:2
+msgid "Application Development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:3
+msgid "May 2013"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:6
+msgid "Application Development Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:8
+msgid "Contents"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:10
+#: i2p2www/pages/site/get-involved/develop/applications.html:16
+msgid "Why write I2P-specific code?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:11
+#: i2p2www/pages/site/get-involved/develop/applications.html:102
+msgid "Important concepts"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:12
+#: i2p2www/pages/site/get-involved/develop/applications.html:190
+msgid "Development options"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:13
+#: i2p2www/pages/site/get-involved/develop/applications.html:303
+msgid "Start developing - a simple guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:18
+#, python-format
+msgid ""
+"There are multiple ways to use applications in I2P.\n"
+"Using I2PTunnel,\n"
+"you can use regular applications without needing to program explicit I2P "
+"support.\n"
+"This is very effective for client-server scenario's,\n"
+"where you need to connect to a single website.\n"
+"You can simply create a tunnel using I2PTunnel to connect to that "
+"website, as shown in Figure 1."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:26
+msgid ""
+"If your application is distributed, it will require connections to a "
+"large amount of peers.\n"
+"Using I2PTunnel, you will need to create a new tunnel for each peer you "
+"want to contact,\n"
+"as shown in Figure 2.\n"
+"This process can of course be automated, but running a lot of I2PTunnel "
+"instances creates a large amount of overhead.\n"
+"In addition, with many protocols you will need to force everyone to \n"
+"use the same set of ports for all peers - e.g. if you want to reliably "
+"run DCC \n"
+"chat, everyone needs to agree that port 10001 is Alice, port 10002 is "
+"Bob, port \n"
+"10003 is Charlie, and so on, since the protocol includes TCP/IP specific "
+"information\n"
+"(host and port)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:37
+msgid ""
+"General network applications often send a lot of additional data that "
+"could be used to identify users.\n"
+"Hostnames, port numbers, time zones, character sets, etc. are often sent "
+"without informing the user.\n"
+"As such, designing the network protocol specifically with anonymity in "
+"mind\n"
+"can avoid compromising user identities."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:43
+msgid ""
+"There are also efficiency considerations to review when determining how "
+"to \n"
+"interact on top of I2P.  The streaming library and things built on top of"
+" it\n"
+"operate with handshakes similar to TCP, while the core I2P protocols "
+"(I2NP and I2CP)\n"
+"are strictly message based (like UDP or in some instances raw IP).  The "
+"important\n"
+"distinction is that with I2P, communication is operating over a long fat "
+"network - \n"
+"each end to end message will have nontrivial latencies, but may contain "
+"payloads \n"
+"of up to several KB.  An application that needs a simple request and "
+"response can get rid\n"
+"of any state and drop the latency incurred by the startup and teardown "
+"handshakes\n"
+"by using (best effort) datagrams without having to worry about MTU "
+"detection or \n"
+"fragmentation of messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:57
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid ""
+"Creating a server-client connection using I2PTunnel only requires "
+"creating a single tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid "Figure 1:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:64
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid ""
+"Setting up connections for a peer-to-peer applications requires a very "
+"large amount of tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid "Figure 2:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:70
+msgid "In summary, a number of reasons to write I2P-specific code:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:74
+msgid ""
+"Creating a large amount of I2PTunnel instances consumes a non-trivial "
+"amount of resources,\n"
+"which is problematic for distributed applications (a new tunnel is "
+"required for each peer)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:78
+msgid ""
+"General network protocols often send a lot of additional data that can be"
+" used to identify users.\n"
+"Programming specifically for I2P allows the creation of a network "
+"protocol\n"
+"that does not leak such information, keeping users anonymous and secure."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:83
+msgid ""
+"Network protocols designed for use on the regular internet can be "
+"inefficient\n"
+"on I2P, which is a network with a much higher latency."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:90
+#, python-format
+msgid ""
+"I2P supports a standard plugins interface for"
+" developers\n"
+"so that applications may be easily integrated and distributed."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:96
+msgid ""
+"Applications written in Java and accessible/runnable\n"
+"using an HTML interface via the standard webapps/app.war\n"
+"may be considered for inclusion in the i2p distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:104
+msgid "There are a few changes that require adjusting to when using I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:108
+msgid "Destination ~= host+port"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:110
+msgid ""
+"An application running on I2P sends messages from and receives messages "
+"to a\n"
+"unique cryptographically secure end point - a \"destination\".  In TCP or"
+" UDP\n"
+"terms, a destination could (largely) be considered the equivalent of a "
+"hostname\n"
+"plus port number pair, though there are a few differences."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:118
+msgid ""
+"An I2P destination itself is a cryptographic construct - all data sent to"
+" one is \n"
+"encrypted as if there were universal deployment of IPsec with the "
+"(anonymized)\n"
+"location of the end point signed as if there were universal deployment of"
+" DNSSEC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:123
+msgid ""
+"I2P destinations are mobile identifiers - they can be moved from one I2P "
+"router\n"
+"to another (or it can even \"multihome\" - operate on multiple routers at"
+"\n"
+"once).  This is quite different from the TCP or UDP world where a single "
+"end point (port)\n"
+"must stay on a single host."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:130
+msgid ""
+"I2P destinations are ugly and large - behind the scenes, they contain a "
+"2048 bit ElGamal\n"
+"public key for encryption, a 1024 bit DSA public key for signing, and a "
+"variable size \n"
+"certificate, which may contain proof of work or blinded data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:135
+#, python-format
+msgid ""
+"There are existing ways to refer to these large and ugly destinations by "
+"short\n"
+"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not "
+"guarantee\n"
+"globally uniqueness (since they're stored locally in a database on each "
+"person's machine)\n"
+"and the current mechanism is not especially scalable nor secure (updates "
+"to the host list are\n"
+"managed using \"subscriptions\" to naming services).\n"
+"There may be some secure, human readable, scalable, and globally \n"
+"unique, naming system some day, but applications shouldn't depend upon it"
+" being in place,\n"
+"since there are those who don't think such a beast is possible.\n"
+"Further information on the naming system is "
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:149
+#, python-format
+msgid ""
+"While most applications do not need to distinguish protocols and ports,\n"
+"I2P does support them. Complex applications may specify a "
+"protocol,\n"
+"from port, and to port, on a per-message basis, to multiplex traffic on\n"
+"a single destination.\n"
+"See the datagram page for details.\n"
+"Simple applications operate by listening for \"all protocols\" on \"all "
+"ports\" of a destination."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:158
+msgid "Anonymity and confidentiality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:160
+msgid ""
+"I2P has transparent end to end encryption\n"
+"and authentication for all data passed over the network - if Bob sends to"
+" Alice's destination,\n"
+"only Alice's destination can receive it, and if Bob is using the "
+"datagrams or streaming \n"
+"library, Alice knows for certain that Bob's destination is the one who "
+"sent the data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:167
+msgid ""
+"Of course, I2P transparently anonymizes the\n"
+"data sent between Alice and Bob, but it does nothing to anonymize the "
+"content of what they\n"
+"send.  For instance, if Alice sends Bob a form with her full name, "
+"government IDs, and \n"
+"credit card numbers, there is nothing I2P can do.  As such, protocols and"
+" applications should \n"
+"keep in mind what information they are trying to protect and what "
+"information they are willing\n"
+"to expose."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:176
+msgid "I2P datagrams can be up to several KB"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:178
+#, python-format
+msgid ""
+"Applications that use I2P datagrams (either raw or repliable ones) can "
+"essentially be thought\n"
+"of in terms of UDP - the datagrams are unordered, best effort, and "
+"connectionless - but unlike\n"
+"UDP, applications don't need to worry about MTU detection and can simply "
+"fire off large datagrams.\n"
+"While the upper limit is nominally 32 KB, the message is fragmented for "
+"transport, thus dropping\n"
+"the reliability of the whole. Datagrams over about 10 KB are not "
+"currently recommended.\n"
+"See the datagram page for details.\n"
+"For many applications, 10 KB of data is sufficient for an\n"
+"entire request or response, allowing them to transparently operate in I2P"
+" as a UDP-like \n"
+"application without having to write fragmentation, resends, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:192
+msgid ""
+"There are several means of sending data over I2P, each with their own "
+"pros and cons.\n"
+"The streaming lib is the recommended interface, used by the majority of "
+"I2P applications."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:197
+msgid "Streaming Lib"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:198
+#, python-format
+msgid ""
+"The full streaming library is now the "
+"standard\n"
+"interface. It allows programming using TCP-like sockets, as explained in "
+"the Streaming development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:204
+#, python-format
+msgid ""
+"BOB is the Basic Open Bridge,\n"
+"allowing an application in any language to make streaming connections \n"
+"to and from I2P. At this point in time it lacks UDP support, but UDP "
+"support\n"
+"is planned in the near future. BOB also contains several tools, such as \n"
+"destination key generation, and verification that an address conforms to"
+" \n"
+"I2P specifications. Up to date info and applications that use BOB can be"
+" \n"
+"found at this eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:217
+msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:218
+#, python-format
+msgid ""
+"SAM is the Simple Anonymous Messaging protocol, "
+"allowing an\n"
+"application written in any language to talk to a SAM bridge through a "
+"plain TCP socket and have\n"
+"that bridge multiplex all of its I2P traffic, transparently coordinating "
+"the encryption/decryption\n"
+"and event based handling.  SAM supports three styles of operation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:225
+msgid ""
+"streams, for when Alice and Bob want to send data to each other reliably "
+"and in order"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:228
+msgid ""
+"repliable datagrams, for when Alice wants to send Bob a message that Bob "
+"can reply to"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:231
+msgid ""
+"raw datagrams, for when Alice wants to squeeze the most bandwidth and "
+"performance as possible,\n"
+"and Bob doesn't care whether the data's sender is authenticated or not "
+"(e.g. the data transferred\n"
+"is self authenticating)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:237
+msgid ""
+"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n"
+"multiplexing/demultiplexing. Each I2P stream is handled by its own socket"
+" between the application\n"
+"and the SAM bridge. Besides, datagrams can be sent and received by the "
+"application through datagram\n"
+"communications with the SAM bridge."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:244
+#, python-format
+msgid ""
+"SAM V2 is a new version used by imule\n"
+"that fixes some of the problems in SAM.\n"
+"
            \n"
+"SAM V3 is used by imule since version 1.4.0."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:252
+msgid ""
+"The I2PTunnel application allows applications to build specific TCP-like "
+"tunnels to peers \n"
+"by creating either I2PTunnel 'client' applications (which listen on a "
+"specific port and connect\n"
+"to a specific I2P destination whenever a socket to that port is opened) "
+"or I2PTunnel 'server'\n"
+"applications (which listen to a specific I2P destination and whenever it "
+"gets a new I2P \n"
+"connection it outproxies to a specific TCP host/port).  These streams are"
+" 8-bit clean, and are\n"
+"authenticated and secured through the same streaming library that SAM "
+"uses, but there is a \n"
+"nontrivial overhead involved with creating multiple unique I2PTunnel "
+"instances, since each have\n"
+"their own unique I2P destination and their own set of tunnels, keys, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:264
+msgid ""
+"I2P supports a SOCKS V4 and V5 proxy.\n"
+"Outbound connections work well. Inbound (server) and UDP functionality "
+"may be incomplete\n"
+"and untested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:271
+msgid "Removed"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:272
+msgid ""
+"There used to be a simple \"ministreaming\" library,\n"
+"but now ministreaming.jar contains only the interfaces for the full "
+"streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:277
+msgid "Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:278
+msgid "Recommended for UDP-like applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:279
+#, python-format
+msgid ""
+"The Datagram library allows sending UDP-"
+"like packets.\n"
+"It's possible to use:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:284
+msgid "Repliable datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:285
+msgid "Raw datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:289
+msgid "Not recommended"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:290
+#, python-format
+msgid ""
+"I2CP itself is a language independent protocol, "
+"but to implement an I2CP library \n"
+"in something other than Java there is a significant amount of code to be "
+"written (encryption routines, \n"
+"object marshalling, asynchronous message handling, etc).  While someone "
+"could write an I2CP library in \n"
+"C or something else, it would most likely be more useful to use the C SAM"
+" library instead."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:297
+msgid "Web Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:298
+msgid ""
+"I2P comes with the Jetty webserver, and configuring to use the Apache "
+"server instead is straightforward.\n"
+"Any standard web app technology should work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:304
+msgid ""
+"Developing using I2P requires a working I2P installation and a "
+"development environment of your own choice.\n"
+"If you are using Java, you can start development with the streaming library or datagram library.\n"
+"Using another programming language, SAM or BOB can be used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:310
+msgid "Developing with the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:312
+msgid ""
+"The following example shows how to create TCP-like client and server "
+"applications\n"
+"using the streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:317
+msgid "This will require the following libraries in your classpath:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:321
+msgid "The streaming library itself"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:322
+msgid "Factory and interfaces for the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:323
+msgid "Standard I2P classes, data structures, API, and utilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:326
+msgid ""
+"Network communication requires the usage of I2P network sockets.\n"
+"To demonstrate this, we will create an application where a client can "
+"send text messages to a server,\n"
+"who will print the messages and send them back to the client. In other "
+"words, the server will function as an echo."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:331
+msgid ""
+"We will start by initializing the server application. This requires "
+"getting an I2PSocketManager\n"
+"and creating an I2PServerSocket.\n"
+"We will not provide the I2PSocketManagerFactory with the saved keys for "
+"an existing Destination,\n"
+"so it will create a new Destination for us.\n"
+"So we will ask the I2PSocketManager for an I2PSession, so we can find out"
+" the Destination that\n"
+"was created, as we will need to copy and paste that information later so "
+"the client can connect to us."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:362
+msgid "Code example 1: initializing the server application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:364
+msgid ""
+"Once we have an I2PServerSocket, we can create I2PSocket instances to "
+"accept connections from clients.\n"
+"In this example, we will create a single I2PSocket instance, that can "
+"only handle one client at a time.\n"
+"A real server would have to be able to handle multiple clients.\n"
+"To do this, multiple I2PSocket instances would have to be created, each "
+"in separate threads.\n"
+"Once we have created the I2PSocket instance, we read data, print it and "
+"send it back to the client.\n"
+"The bold code is the new code we add."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:448
+msgid "Code example 2: accepting connections from clients and handling messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:452
+msgid ""
+"When you run the above server code, it should print something like this "
+"(but without the line endings, it should just be\n"
+"one huge block of characters):"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:466
+msgid ""
+"This is the base64-representation of the server Destination. The client "
+"will need this string to reach the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:470
+msgid ""
+"Now, we will create the client application. Again, a number of steps are "
+"required for initialization.\n"
+"Again, we will need to start by getting an I2PSocketManager.\n"
+"We won't use an I2PSession and an I2PServerSocket this time.\n"
+"Instead, we will use the server Destination string to start our "
+"connection.\n"
+"We will ask the user for the Destination string, and create an I2PSocket "
+"using this string.\n"
+"Once we have an I2PSocket, we can start sending and receiving data to and"
+" from the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:554
+msgid ""
+"Code example 3: starting the client and connecting it to the server "
+"application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:556
+msgid ""
+"Finally, you can run both the server and the client application.\n"
+"First, start the server application. It will print a Destination string "
+"(like shown above).\n"
+"Next, start the client application. When it requests a Destination "
+"string, you can enter the string printed by the server.\n"
+"The client will then send 'Hello I2P!' (along with a newline) to the "
+"server, who will print the message and send it back to the client."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:562
+msgid "Congratulations, you have successfully communicated over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:566
+msgid "Existing Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:567
+msgid "Contact us if you would like to contribute."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:588
+msgid "Application Ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:590
+msgid "NNTP server - there have been some in the past, none at the moment"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:593
+msgid ""
+"Jabber server - there have been some in the past, and there is one at the"
+" moment, with access to the public internet"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:596
+msgid "PGP Key server and/or proxy"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:599
+msgid ""
+"Content Distribution / DHT applications - resurrect feedspace,\n"
+"port dijjer, look for alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:603
+msgid "Help out with Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:606
+msgid ""
+"Web-based applications - The sky is the limit for hosting web-server-"
+"based\n"
+"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n"
+"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:611
+msgid ""
+"Resurrect some old apps, several previously in the i2p source package -\n"
+"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2
+msgid "I2P Developer's MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4
+msgid "MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5
+msgid ""
+"Monotone servers used by the I2P project require two types of keys to be "
+"used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
+msgid ""
+"Commit Keys to sign changes checked-in to the "
+"respository; and"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10
+msgid ""
+"Transport Keys to push changes to remote "
+"servers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13
+#, python-format
+msgid ""
+"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
+"import the\n"
+"developer commit keys, but only Monotone \n"
+"server operators will need to import the transport keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20
+msgid "Developer Commit keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:255
+msgid "Developer Transport Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:256
+#, python-format
+msgid ""
+"Note: Transport keys are only needed for setting up a\n"
+"Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
+msgid "License Agreements"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
+#, python-format
+msgid "For more information see the licenses page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8
+msgid ""
+"Following is a monotonerc file defining the current trust list.\n"
+"Developers must use this file in ~/.monotone/monotonerc or\n"
+"_MTN/montonerc in their i2p.i2p workspace."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17
+msgid "Agreements"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:2
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115
+msgid "Licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:4
+msgid "I2P Software Licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:5
+#, python-format
+msgid ""
+"As required by our\n"
+"threat model (among other reasons), the \n"
+"software developed to support the anonymous communication \n"
+"network we call I2P must be freely available, open source, \n"
+"and user modifiable.  To meet these criteria, we make use of\n"
+"a variety of legal and software engineering techniques so\n"
+"as to remove as many barriers to entry for those considering\n"
+"making use of or contributing to the I2P effort."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:16
+msgid ""
+"While the information below may be more confusing than just simply \n"
+"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
+"the short answer to the question \"How is I2P licensed?\" is this:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:22
+msgid "All software bundled in the I2P distributions will allow:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:24
+msgid "use without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:25
+msgid ""
+"use with no restrictions on how, when, where, why, or by whom is running "
+"it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:26
+msgid "access to the source code without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:27
+msgid "modifications to the source"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:30
+msgid ""
+"Most of the software guarantees much more - the ability of anyone "
+"to \n"
+"distribute the modified source however they choose.  However, not all of "
+"the \n"
+"software bundled provides this freedom - the GPL restricts the ability of"
+" \n"
+"developers who wish to integrate I2P with their own applications that are"
+" not \n"
+"themselves open source applications.  While we applaud the noble goals of"
+" \n"
+"increasing the resources in the commons, I2P is best served by removing "
+"any\n"
+"barriers that stand in the way of its adoption - if a developer "
+"considering whether\n"
+"they can integrate I2P with their application has to stop and check with "
+"their lawyer,\n"
+"or conduct a code audit to make sure their own source can be released as "
+"GPL-compatible,\n"
+"we lose out."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:43
+msgid "Component licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:44
+msgid ""
+"The I2P distribution contains several resources, reflecting the "
+"partitioning of \n"
+"the source code into components.  Each component has its own license, "
+"which all \n"
+"developers who contribute to it agree to - either by explicitly declaring"
+" the release\n"
+"of code committed under a license compatible with that component, or by "
+"implicitly\n"
+"releasing the code committed under the component's primary license.  Each"
+" of these \n"
+"components has a lead developer who has the final say as to what license "
+"is compatible\n"
+"with the component's primary license, and the I2P project manager has the"
+" final say as\n"
+"to what licenses meet the above four guarantees for inclusion in the I2P "
+"distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:57
+msgid "Component"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:58
+msgid "Source path"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:59
+msgid "Resource"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:60
+msgid "Primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:61
+msgid "Alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:62
+msgid "Lead developer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:271
+msgid "GPL + java exception"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:272
+#, python-format
+msgid ""
+"While it may be redundant, just for clarity the\n"
+"GPL'ed code included within\n"
+"I2PTunnel and other apps must be released under the GPL with an "
+"additional \"exception\"\n"
+"explicitly authorizing the use of Java's standard libraries:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:288
+msgid ""
+"All source code under each component will by default be licensed under "
+"the\n"
+"primary license, unless marked otherwise in the code.  All of the above "
+"is\n"
+"summary of the license terms - please see the specific license for the "
+"component\n"
+"or source code in question for authoritative terms.  Component source "
+"locations and\n"
+"resource packaging may be changed if the repository is reorganized."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:296
+msgid "Commit privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:297
+#, python-format
+msgid ""
+"Developers may push changes to a distributed monotone repository if you\n"
+"receive permission from the person running that repository.\n"
+"See the Monotone Page for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:303
+msgid ""
+"However, to have changes included in a release, developers\n"
+"must be trusted by the release manager (currently zzz).\n"
+"In addition, they must explicitly agree with the above terms to be "
+"trusted.\n"
+"That means that they must send one of the release managers a signed "
+"message affirming that:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:310
+msgid ""
+"Unless marked otherwise, all code I commit is implicitly licensed under\n"
+"the component's primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:314
+msgid ""
+"If specified in the source, the code may be explicitly licensed under one"
+"\n"
+"of the component's alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:318
+msgid ""
+"I have the right to release the code I commit under the terms I\n"
+"am committing it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:324
+#, python-format
+msgid ""
+"If anyone is aware of any instances where the above conditions are not "
+"met,\n"
+"please contact the component lead and/or an I2P release manager with "
+"further\n"
+"information.\n"
+"See developers' license agreements."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
+msgid "Release Signing Key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
+msgid "Releases 0.7.6 and later are signed by zzz. His public key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40
+msgid ""
+"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public "
+"key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2
+msgid "Signed Developer Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4
+msgid ""
+"Keys for zzz, Complication and welterde are provided clearsigned. The key"
+" for jrandom must be\n"
+"verified differently, since he's away, and only left a binary detached\n"
+"signature for his key."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16
+msgid "Monotone keys for zzz"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47
+msgid "Monotone keys for welterde"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79
+msgid "Monotone keys for Complication"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114
+msgid "Monotone keys for jrandom"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
+msgid "Others"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
+msgid ""
+"Tip: To find zzz's GPG key, on his eepsite locate the key "
+"`0xA76E0BED`, with\n"
+"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 "
+"B310 4155\n"
+"76BA A76E 0BED`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49
+msgid ""
+"Tip: To find welterde's GPG key, on public keyservers locate the "
+"key\n"
+"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720"
+" FD81\n"
+"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81
+msgid ""
+"Tip: To find Complication's GPG key, on his eepsite locate the key"
+"\n"
+"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint "
+"`73CF\n"
+"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116
+msgid ""
+"Tip: To find jrandom's GPG key for Syndie releases, on public "
+"keyservers locate\n"
+"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n"
+"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122
+msgid ""
+"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n"
+"deployed in the Syndie Monotone repository, in a file named `mtn-"
+"committers`.\n"
+"That file also had a GPG signature, `mtn-committers.sig`, but it was a "
+"binary\n"
+"detached signature. I am going to supply both files in GPG ASCII-armoured"
+" form\n"
+"below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130
+msgid ""
+"First, the file `mtn-committers` containing jrandom's Monotone key. Save "
+"as\n"
+"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers "
+"--dearmor\n"
+"mtn-committers.asc`:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151
+msgid ""
+"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n"
+"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-"
+"committers.sig\n"
+"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n"
+"`mtn-committers` file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170
+#, python-format
+msgid ""
+"Some of the developers have included their Monotone keys in their signed license agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2
+msgid "Developer Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4
+#, python-format
+msgid "Read the new developers guide first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8
+msgid "Basic Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10
+msgid ""
+"Most of the following should be common sense for anybody who has worked "
+"on open source or in a commercial\n"
+"programming envrionment.\n"
+"The following applies mostly to the main development branch i2p.i2p.\n"
+"Guidelines for other branches, plugins, and external apps may be "
+"substantially different;\n"
+"check with the appropriate developer for guidance."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18
+msgid "Community"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20
+msgid ""
+"Please don't just \"write code\". If you can, participate in other "
+"development activities, including:\n"
+"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
+"testing;\n"
+"bug reporting and responses; documentation; code reviews; etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25
+msgid ""
+"Active devs should be available periodically on IRC #i2p-dev.\n"
+"Be aware of the current release cycle.\n"
+"Adhere to release milestones such as feature freeze, tag freeze, and\n"
+"the checkin deadline for a release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35
+msgid ""
+"Have a basic understanding of distributed source control systems, even if"
+" you haven't\n"
+"used monotone before. Ask for help if you need it.\n"
+"Once pushed, checkins are forever, there is no undo. Please be careful.\n"
+"If you have not used monotone before, start with baby steps.\n"
+"Check in some small changes and see how it goes."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42
+msgid ""
+"Test your changes before checking them in.\n"
+"If you prefer the checkin-before-test development model,\n"
+"use your own development branch (e.g. i2p.i2p.yourname.test)\n"
+"and propagate back to i2p.i2p once it is working well.\n"
+"Do not break the build. Do not cause regressions.\n"
+"In case you do (it happens), please do not vanish for a long period after"
+"\n"
+"you push your change."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51
+msgid ""
+"If your change is non-trivial, or you want people to test it and need "
+"good test reports\n"
+"to know whether your change was tested or not, add a checkin comment to "
+"history.txt\n"
+"and increment the build revision in RouterVersion.java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56
+msgid ""
+"Ensure that you have the latest monotonerc file in _MTN.\n"
+"Do not check in on top of untrusted revisions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60
+msgid ""
+"Ensure that you pull the latest revision before you check in.\n"
+"If you inadvertently diverge, merge and push as soon as possible.\n"
+"Don't routinely make others merge for you.\n"
+"Yes, we know that monotone says you should push and then merge,\n"
+"but in our experience, in-workspace merge works just as well as in-"
+"database merge,\n"
+"without creating a merge revision."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
+msgid ""
+"Do not check in major changes into the main i2p.i2p branch late in the "
+"release cycle.\n"
+"If a project will take you more than a couple days, create your own "
+"branch in monotone\n"
+"and do the development there so you do not block releases."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75
+msgid "Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77
+msgid ""
+"Coding style throughout most of the code is 4-spaces for indentation. Do "
+"not use tabs.\n"
+"Do not reformat code. If your IDE or editor wants to reformat everything,"
+" get control of it.\n"
+"Yes, we know 4 spaces is a pain, but perhaps you can configure your "
+"editor appropriately.\n"
+"In some places, the coding style is different.\n"
+"Use common sense. Emulate the style in the file you are modifying."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84
+msgid ""
+"New classes and methods require at least brief javadocs. Add @since "
+"release-number."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87
+msgid ""
+"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our "
+"official API.\n"
+"There are several out-of-tree plugins and other applications that rely on"
+" this API.\n"
+"Be careful not to make any changes that break compatibility.\n"
+"Don't add methods to the API unless they are of general utility.\n"
+"Javadocs for API methods should be clear and complete.\n"
+"If you add or change the API, also update the documentation on the "
+"website (i2p.www branch)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95
+msgid ""
+"Tag strings for translation where appropriate.\n"
+"Don't change existing tagged strings unless really necessary, as it will "
+"break existing translations.\n"
+"Do not add or change tagged strings after the \"tag freeze\" in the "
+"release cycle so that\n"
+"translators have a chance to update before the release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101
+msgid ""
+"Use generics and concurrent classes where possible. I2P is a highly "
+"multi-threaded application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104
+msgid ""
+"We require Java 6 to build but only Java 5 to run I2P.\n"
+"Do not use Java 6 classes or methods without handling the class not found"
+" exceptions\n"
+"and providing alternate Java 5 code. See classes in net.i2p.util for "
+"examples."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109
+msgid ""
+"Explicitly convert between primitive types and classes;\n"
+"don't rely on autoboxing/unboxing."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117
+msgid ""
+"Only check in code that you wrote yourself.\n"
+"Before checking in any code or library jars from other sources,\n"
+"justify why it is necessary,\n"
+"verify the license is compatible,\n"
+"and obtain approval from the lead developer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124
+msgid ""
+"For any images checked in from external sources,\n"
+"it is your responsibility to first verify the license is compatible.\n"
+"Include the license and source information in the checkin comment."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131
+msgid "Bugs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
+#, python-format
+msgid ""
+"Managing Trac tickets is everybody's job, please help.\n"
+"Monitor %(trac)s for tickets you have been assigned or can help with.\n"
+"Assign, categorize, comment on, fix, or close tickets if you can."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138
+msgid ""
+"Close a ticket when you think you've fixed it.\n"
+"We don't have a test department to verify and close tickets.\n"
+"If you arent sure you fixed it, close it and add a note saying\n"
+"\"I think I fixed it, please test and reopen if it's still broken\".\n"
+"Add a comment with the dev build number or revision and set\n"
+"the milestone to the next release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:2
+msgid "Using an IDE with I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:4
+msgid ""
+"The main I2P development branch (i2p.i2p) has been set up to"
+" enable developers to easily set up two of the commonly-used IDEs for "
+"Java development: Eclipse and NetBeans."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:10
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain .project and .classpath Eclipse files, to enable the branch "
+"to be easily set up in Eclipse."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:16
+msgid ""
+"Check out the I2P branch into some directory (e.g. "
+"$HOME/dev/i2p.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:20
+msgid ""
+"Open Eclipse and create a new Workspace, based in the directory that the "
+"I2P branch was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:24
+msgid ""
+"Select \"File - Import...\" and then under \"General\" select \"Existing "
+"Projects into Workspace\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:28
+msgid ""
+"For \"Select root directory:\" choose the directory that the I2P branch "
+"was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:32
+msgid "If necessary, click \"Refresh\" to refresh the list of projects."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:36
+msgid "Select every project in the list, and click \"Finish\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:40
+msgid ""
+"Done! Your workspace should now contain all projects within the I2P "
+"branch, and their build dependencies should be correctly set up."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:48
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain NetBeans project files."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:2
+msgid "Monotone"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:4
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:9
+msgid "Operating a Monotone client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:11
+#: i2p2www/pages/site/get-involved/guides/monotone.html:63
+msgid "Generating Monotone keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:12
+msgid "Trust and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:13
+#: i2p2www/pages/site/get-involved/guides/monotone.html:196
+msgid "Obtaining and deploying developers' keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:14
+#: i2p2www/pages/site/get-involved/guides/monotone.html:227
+msgid "Setting up trust evaluation hooks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:15
+#: i2p2www/pages/site/get-involved/guides/monotone.html:268
+msgid ""
+"Pulling the i2p.i2p, i2p.www and "
+"i2p.syndie branches"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:16
+#: i2p2www/pages/site/get-involved/guides/monotone.html:308
+msgid "Verifying that trust evaluation works"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:17
+#: i2p2www/pages/site/get-involved/guides/monotone.html:357
+msgid "Checking out a working copy of the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:18
+#: i2p2www/pages/site/get-involved/guides/monotone.html:384
+msgid "Updating your working copy to the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:22
+#: i2p2www/pages/site/get-involved/guides/monotone.html:414
+msgid "Operating a Monotone Server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:24
+msgid "Obtaining and deploying developers’ transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:25
+#: i2p2www/pages/site/get-involved/guides/monotone.html:424
+msgid "Granting push and pull access"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:26
+#: i2p2www/pages/site/get-involved/guides/monotone.html:469
+msgid "Running Monotone in server mode"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:27
+#: i2p2www/pages/site/get-involved/guides/monotone.html:494
+msgid "Differences under Debian GNU/Linux"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:34
+#, python-format
+msgid ""
+"This is a revised version of Complication's original\n"
+"  guide detailing the use of Monotone in I2P development.\n"
+"  For basic instructions see the quick-start "
+"guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:42
+#, python-format
+msgid ""
+"I2P has a distributed development model. The source code is replicated "
+"across\n"
+"  independently administered Monotone (\"MTN\") repositories.\n"
+"  Developers with commit rights are able to push their changes to the "
+"repository\n"
+"  (a license agreement needs to be "
+"signed\n"
+"  before commit rights are granted)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:52
+msgid ""
+"Some of Monotone's noteworthy qualities are: distributed\n"
+"  version control, cryptographic authentication, access control, its "
+"small size, having few\n"
+"  dependencies, storage of projects in a compressed SQLite database file,"
+" and\n"
+"  having the ability to resume interrupted synchronization attempts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:61
+msgid "Operating a Monotone Client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:66
+msgid ""
+"A transport key grants you the ability to push your changes to a Monotone"
+" repository server.\n"
+"  In order to commit code into Monotone (in essence signing your code), a"
+" commit key is also needed.\n"
+"  None of the public Monotone servers on I2P currently require a key in "
+"order to read (or pull) the source code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:74
+msgid ""
+"Without a transport key, one cannot:\n"
+"  
              \n"
+"    
            • pull code from a server which doesn't allow global read "
+"access
              • \n"
+"    
            • push code to any server
              • \n"
+"    
            • run a Monotone server
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:85
+msgid ""
+"Without a commit key, one cannot:\n"
+"  
              \n"
+"    
            • commit any code
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:94
+msgid ""
+"If you only intend to retrieve code from MTN, feel free to skip to the\n"
+"  next section. "
+"If you want\n"
+"  to generate keys, read the following."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:102
+msgid ""
+"By convention keys are named like an e-mail addresses, but a "
+"corresponding e-mail\n"
+"  address does not need to exist. For example, your keys might be named:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:113
+msgid ""
+"Monotone stores keys under $HOME/.monotone/keys in "
+"text files which\n"
+"  are named identically to the keys. For example:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:123
+msgid ""
+"To generate transport and commit keys, enter the following commands at a "
+"prompt:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:133
+msgid ""
+"Monotone will prompt you for a password to protect your keys. You are "
+"very strongly encouraged to set a password\n"
+"  for the commit key. Many users will leave an empty password for the "
+"transport key, especially those running a\n"
+"  Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:141
+msgid "Trust, and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:145
+msgid ""
+"Monotone's security model helps to ensure that nobody can easily "
+"impersonate a developer without\n"
+"  it being noticed. Since developers can make mistakes and become "
+"compromised,only manual review can\n"
+"  ensure quality of code. Monotone's trust model will ensure that you "
+"read the right diffs. It does\n"
+"  not replace reading diffs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:155
+msgid ""
+"A Monotone repository is a single file (a compressed SQLite database) "
+"which contains all of the project's source code and history."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:161
+msgid ""
+"After importing the "
+"developers' keys into Monotone and\n"
+"  setting up trust "
+"evaluation hooks,\n"
+"  Monotone will prevent untrusted code from being checked out into your "
+"workspace.\n"
+"  There are commands available to clean untrusted code from your "
+"workspace but in practice they've not been\n"
+"  needed due to the push access policies in place."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:171
+msgid ""
+"A repository can hold many branches. For example, our repository holds "
+"the\n"
+"  following main branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:176
+msgid "The I2P router and associated programs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:177
+msgid "The I2P project website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:178
+msgid "Syndie, a distributed forums tool"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:183
+msgid ""
+"By convention, the I2P Monotone repository is named i2p.mtn."
+" Before pulling\n"
+"  source code from servers, a database for your repository will need to "
+"be initialized.\n"
+"  To initialize your local repository, change into the directory that you"
+" want the\n"
+"  i2p.mtn file and branch directories to be stored and issue"
+" the following\n"
+"  command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:199
+msgid ""
+"Keys which developers use to commit code are essential for trust "
+"evaluation in\n"
+"  Monotone. The other developers' transport keys are only required for "
+"Monotone server operators.\n"
+"  "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:206
+#, python-format
+msgid ""
+"Developers' commit keys are provided GPG-signed on another page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:212
+#, python-format
+msgid ""
+"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
+"  file. Create this file (e.g. keys.txt) in the same "
+"directory where i2p.mtn is located. Import the keys with the"
+" command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:222
+msgid ""
+"Note: Never add keys to "
+"$HOME/.monotone/keys manually."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:230
+msgid ""
+"The default Monotone trust policy is way too lax for our requirements: "
+"every committer is trusted by default.\n"
+"  That is not acceptable for I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:237
+msgid ""
+"Change into the directory $HOME/.monotone and open "
+"the file\n"
+"  monotonerc with a text editor. Copy and paste the "
+"following two functions into this file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:246
+msgid ""
+"The first function determines an intersection between two sets, in our "
+"case a\n"
+"  revision's signers and trusted signers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:253
+msgid ""
+"The second function determines trust in a given revision, by calling the "
+"first\n"
+"  function with \"signers\" and \"trusted\" as arguments. If the "
+"intersection is\n"
+"  null, the revision is not trusted. If the intersection is not empty, "
+"the\n"
+"  revision is trusted. Otherwise, the revision is not trusted."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:262
+msgid ""
+"More information about Trust Evauluation Hooks can be found in the official Monotone "
+"documentation."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:271
+msgid ""
+"Enter the directory where you initialized i2p.mtn. Depending "
+"on whether you\n"
+"  want only I2P sources, or also sources for the I2P website and Syndie, "
+"you can\n"
+"  perform the pull operation in different ways."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:279
+msgid "If you only want I2P sources:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:288
+msgid "If you want all branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:294
+msgid ""
+"If the transfer aborts before completing sucessfully, simply repeating "
+"the pull command will resume the transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:300
+msgid ""
+"Pulling in the above examples is done anonymously by specifying an empty "
+"transport key.\n"
+"  If everyone pulls anonymously it will be harder for an attacker who "
+"gains control of the server\n"
+"  to selectively provide some people with tampered data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:311
+msgid "To verify that trust evaluation works:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:315
+msgid "Make a backup of your monotonerc file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:316
+msgid ""
+"Modify monotonerc by setting the trusted_signers "
+"variable in the following way:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:322
+msgid ""
+"With monotonerc configured as above, Monotone will no"
+" longer trust any committers. Confirm this by changing into the\n"
+"directory where i2p.mtn was created and attempt a checkout "
+"of the I2P branch:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:332
+msgid ""
+"A directory named i2p.i2p should not appear. You "
+"should encounter many\n"
+"  error messages like:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:349
+msgid ""
+"If you are satisfied with results, restore the backup of\n"
+"  monotonerc that was created above. If you didn't create a "
+"backup\n"
+"  as advised, re-read Setting up trust evaluation hooks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:360
+msgid ""
+"If you already have a branch checked out, skip to the next\n"
+"  section."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:367
+msgid ""
+"Change into the directory where i2p.mtn is located. Over "
+"there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:376
+msgid ""
+"The checkout should complete without error messages and a directory named"
+"\n"
+"  i2p.i2p should appear in the current directory. "
+"Congratulations! You have\n"
+"  successfully checked out the latest I2P sources, ready to be compiled."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:387
+msgid ""
+"If you haven't done this already, pull fresh code from the server to your"
+" local\n"
+"  Monotone repository. To accomplish this, change into the directory "
+"where\n"
+"  i2p.mtn is located and issue:\n"
+"  
              \n"
+"    
            • $ mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
+"i2p.i2p
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:398
+msgid "Now change into your i2p.i2p directory, and over there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:407
+msgid ""
+"As long as there were no errors…Congratulations! You have "
+"successfully updated to the latest I2P sources. They\n"
+"  should be ready to compile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:416
+msgid "Obtaining and deploying developers' transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:419
+msgid ""
+"As a server operator you may want to grant push access to certain "
+"developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:427
+msgid "By default the Monotone server denies all access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:433
+msgid "To grant pull access to all clients, set the following in"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:445
+msgid ""
+"No one will not be able to push code to your server without permission "
+"being explicitly granted. To grant push access:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:451
+msgid ""
+"Add the name of the user's transport key to\n"
+"$HOME/.monotone/write-permissions, such as\n"
+"
            \n"
+"    zzz-transport@mail.i2p\n"
+"    complication-transport@mail.i2p\n"
+"
            \n"
+"with one key per line."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:462
+msgid ""
+"Import the transport key(s) into your database. The procedure for "
+"importing transport keys is the same as for\n"
+"importing commit keys, which is described in the section Obtaining and deploying "
+"developers' keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:472
+msgid ""
+"A separate database should be used for your Monotone server because "
+"monotone will lock the database while it is served to others.\n"
+"  Make a copy of your development database, then start the server with:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:479
+msgid ""
+"If your key is protected with a passphrase, Monotone may request the "
+"passphrase\n"
+"  when the first client connects. You can work around this by connecting "
+"making the first client connection to your server\n"
+"  (or by clearing the password for your transport key)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:487
+msgid ""
+"For your server to be accessible for others over I2P, you will need to "
+"create a\n"
+"  server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" "
+"profile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:497
+msgid ""
+"Debian (amongst other distributions) has integrated Monotone into their\n"
+"  framework of daemons/services. Although Monotone servers can still be "
+"run\n"
+"  \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may"
+" be more straightforward."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:505
+msgid ""
+"Permissions are granted by editing the files\n"
+"  /etc/monotone/read-permissions and\n"
+"  /etc/monotone/write-permissions. You'll also need to edit\n"
+"  /etc/default/monotone to enable monotone to start at boot "
+"or to\n"
+"  customize the host, port, or database location."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
+msgid "New Developer's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
+msgid ""
+"\n"
+"So you want to start work on I2P? Great!\n"
+"Here's a quick guide to getting started\n"
+"on contributing to the website or the software, doing development or "
+"creating translations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
+#, python-format
+msgid ""
+"\n"
+"Not quite ready for coding?\n"
+"Try getting involved first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
+msgid "Basic study"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
+msgid "Getting the I2P code"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
+msgid "Building I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
+msgid "Development ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
+msgid "Making the results available"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
+msgid "Get to know us!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
+msgid "Translations"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
+msgid "Tools"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
+msgid ""
+"Basic development on the I2P router or the embedded applications uses "
+"Java as the main development language.\n"
+"If you don't have experience with Java, you can always have a look at Thinking in Java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
+#, python-format
+msgid ""
+"Study the how intro,\n"
+"the other \"how\" documents,\n"
+"the tech intro,\n"
+"and associated documents.\n"
+"These will give you a good overview of how I2P is structured and what "
+"different things it does."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
+msgid ""
+"For development on the i2p router or the embedded applications,\n"
+"get the monotone source repository installed - short instructions:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
+msgid ""
+"Install monotone.\n"
+"Monotone is a version control system.\n"
+"We use it because it allows us to keep track of who does what changes to "
+"the source code (and for a lot of complicated things, but 'keeping track "
+"of changes' is the basic idea)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
+msgid ""
+"Skim over the monotone tutorial,"
+" to make sure you understand the concepts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
+msgid ""
+"If you want to remain anonymous, you need to do an additional step, to "
+"set up a connection to a monotone server over I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
+#, python-format
+msgid ""
+"Enable the i2ptunnel client tunnel on port "
+"8998 pointing to mtn.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
+msgid ""
+"Pick a directory where you want to put all your I2P files, and create a "
+"monotone database:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
+msgid ""
+"Define the trust list by creating ~/.monotone/monotonerc (or"
+" _MTN/monotonerc in the i2p.i2p workspace) with the "
+"following contents:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
+#, python-format
+msgid ""
+"Copy and paste the developer's commit keys "
+"into a new file (e.g. keys.txt) in the same directory\n"
+"  that i2p.mtn is in. Import the keys into your database "
+"with 
                  mtn -d i2p.mtn read < keys.txt
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:76
+msgid ""
+"Pull the I2P sources to your machine. This may take a long time, "
+"especially if you are doing this over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:78
+msgid "Anonymously:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:81
+msgid "Non-anonymously:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:83
+msgid ""
+"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn"
+".i2p-projekt.de."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:90
+msgid ""
+"All the sources are now present on your machine, in the database file. To"
+" make them available in a directory, you need to check them out:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:92
+msgid ""
+"The above command creates a directory i2p.i2p, which contains all of the "
+"I2P sources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:96
+msgid "Remarks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:97
+msgid ""
+"\n"
+"To download the website files instead of the I2P source files, use "
+"'i2p.www' instead of 'i2p.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:100
+msgid ""
+"The initial pull may take several hours using the tunnel.\n"
+"If it fails after a partial pull, simply rerun it, it will start where it"
+" left off.\n"
+"If you are in a hurry, use the non-anonymous access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:105
+#, python-format
+msgid ""
+"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
+#, python-format
+msgid ""
+"A long explanation about using monotone is available on the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
+#, python-format
+msgid ""
+"To compile the code, you need the Sun Java Development Kit 6 or higher, "
+"or equivalent JDK\n"
+"(Sun JDK 6 strongly recommended) and\n"
+"Apache ant\n"
+"version 1.7.0 or higher.\n"
+"If you go are working on the main I2P code, you can go into the i2p.i2p "
+"directory and run 'ant' to see the build options."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
+msgid ""
+"To build or work on console translations, you need\n"
+"the xgettext, msgfmt, and msgmerge tools from the\n"
+"GNU gettext package."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
+#, python-format
+msgid ""
+"For development on new applications,\n"
+"see the application development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
+#, python-format
+msgid ""
+"See zzz's TODO lists,\n"
+"this website's TODO list or\n"
+"Trac\n"
+"for ideas."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
+#, python-format
+msgid ""
+"See the bottom of the licenses page "
+"for\n"
+"commit privilege requirements. You need these to put code into i2p.i2p "
+"(not required for the website!)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
+msgid "Short version of how to generate and use keys if you plan to commit:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
+msgid "use an empty passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
+msgid "enter a passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
+#, python-format
+msgid ""
+"send this to a mtn repo operator to get "
+"push privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
+#, python-format
+msgid ""
+"send this to a release manager to get "
+"commit privileges - not required for website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
+msgid "check in with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
+msgid "push with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
+#, python-format
+msgid "Long version: see the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
+#, python-format
+msgid ""
+"The developers hang around on IRC. They can be reached on the Freenode "
+"network, OFTC, and on the I2P internal networks. The usual place to look "
+"is #i2p-dev. Join the channel and say hi!\n"
+"We also have additional guidelines for regular"
+" developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
+#, python-format
+msgid ""
+"Website and router console translators: See the New Translator's Guide\n"
+"for next steps."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
+msgid ""
+"I2P is open source software that is mostly developed using open sourced\n"
+"toolkits. The I2P project recently acquired a license for the YourKit "
+"Java\n"
+"Profiler. Open source projects are eligible to receive a free license "
+"provided\n"
+"that YourKit is referenced on the project web site. Please get in touch "
+"if you\n"
+"are interested in profiling the I2P codebase."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
+#, python-format
+msgid ""
+"YourKit is kindly supporting open source projects with its full-featured "
+"Java Profiler.\n"
+"YourKit, LLC is the creator of innovative and intelligent tools for "
+"profiling\n"
+"Java and .NET applications. Take a look at YourKit's leading software "
+"products:\n"
+"YourKit Java Profiler and\n"
+"YourKit .NET Profiler."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
+msgid "New Translator's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
+msgid "Here's a very quick guide to getting started."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
+msgid "How to Translate the Website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
+#, python-format
+msgid ""
+"Translation of the website is done with .po files. The easiest way by far"
+" to\n"
+"translate the website is to sign up for an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
+msgid "Preparation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
+#, python-format
+msgid ""
+"Come to #i2p-dev on irc and talk to people.\n"
+"Claim the language -\n"
+"To make sure other coworkers don't bump onto the files you are working "
+"on,\n"
+"please update the translation status on this wiki "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"Including the installation of monotone,\n"
+"checking out i2p.www branch, and generate your own monotone keys.\n"
+"It is not required that you sign a dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
+msgid ""
+"Run \"./extract-messages.sh\" to generate a "
+"messages.pot in the base directory.\n"
+"Edit the header of this file, then run \"./init-new-po.sh "
+"locale\" to generate the file\n"
+"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
+"\"mtn add\" this file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
+msgid ""
+"Edit i2p2www/pages/global/lang.html and add a line for your "
+"language (copy an existing line)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
+msgid ""
+"Add a flag image file to i2p2www/static/images/flags/ for "
+"the menu (copy from the router)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
+msgid ""
+"Edit files:\n"
+"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
+msgid ""
+"Check in:\n"
+"\"mtn pull\", \"mtn update\". Then check in by "
+"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
+"This collects the diff info of your changed file into your local repo. "
+"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
+"i2p.i2p\".\n"
+"This synchronizes your local repo with the repo on the target machine."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
+msgid "Repeat. Check in often. Don't wait until it is perfect."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
+msgid "How to Translate the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
+#, python-format
+msgid ""
+"The easiest way by far to translate the router console is to sign up for "
+"an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"including the installation of monotone and the gettext tools,\n"
+"checking out i2p.i2p branch, and generate your own monotone keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
+msgid "Generate your own gpg key and sign the dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
+msgid ""
+"Before starting a console translation, better help translate some i2p "
+"webpages first.\n"
+"At least an i2p homepage in your language would be great."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
+msgid ""
+"What to translate:\n"
+"There are about 15 files in the i2p.i2p branch that needs translation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
+msgid ""
+"Where xx is your language code like fr/de/ch/zh/...\n"
+"There may be or may not be files with your lang code. If not, you can "
+"create your own. by copying and renaming other language files you know "
+"with your own lang code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet, copy another language "
+"file to a new file foo_xx.bar for your language.\n"
+"Then \"mtn add\" the file.\n"
+"After creating a .po file, edit the headers. Then run \"ant "
+"distclean poupdate\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
+msgid ""
+"Start to work:\n"
+"Edit the HTML files with any text editor.\n"
+"Be sure not to use an editor in HTML mode that reformats everything.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
+msgid ""
+"As you can see, it's not that difficult.\n"
+"If you have questions about the meaning of the terms in the console, ask "
+"in #i2p-dev on IRC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
+msgid "FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
+msgid ""
+"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
+"and html, etc.? Why can't I just do a translation and email it to you?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
+msgid "A: Several reasons:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
+#, python-format
+msgid ""
+"You might be interested in translating via Transifex. Request to join a "
+"translation team here."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
+msgid ""
+"We don't have anybody who has time to accept manual contributions and "
+"submit them to our source control system on your behalf. Even if we did, "
+"it doesn't scale."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
+msgid ""
+"Maybe you are thinking translation is a one-step process. It isn't. You "
+"can't do it all at once. You will make mistakes. You need to test it and "
+"tweak it to make it look right before you submit it. Developers "
+"will update or add to the English text, thus requiring a translation "
+"update."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
+msgid ""
+"Having translators use a source control system directly provides "
+"authentication and accountablility - we know who is doing what, and we "
+"can track changes, and revert them if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
+msgid ""
+".po files are not difficult. If you don't want to work directly with "
+"them, we recommend 'poedit'."
+msgstr ""
+"I file .po non sono difficili. Se non vuoi lavorare direttamente con "
+"loro, ti raccomandiamo 'poedit'."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
+msgid ""
+"HTML files are not difficult. Just ignore the html stuff and translate "
+"the text."
+msgstr ""
+"I file HTML non sono difficili. Semplicemente ignora l'html e traduci il "
+"testo."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
+msgid ""
+"Installing and using monotone is not that difficult. Several of the "
+"translators and other contributors to I2P are non-programmers, and they "
+"use monotone regularly. Monotone is simply a source control system, it is"
+" not about \"coding\"."
+msgstr ""
+"Installare e utilizzare monotone non è così difficile. Alcuni traduttori "
+"ed altri collaboratori di I2P non sono programmatori, eppure usano "
+"monotone regolarmente. Monotone è semplicemente un sistema di controllo "
+"dei sorgenti, ma non ha nulla a che vedere con il \"coding\"."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
+msgid ""
+"Our items to translate are not \"documents\". They are html files and po "
+"files, with a specific format and character encoding (UTF-8) that must be"
+" maintained, and not corrupted by email programs or other methods of "
+"transfer."
+msgstr ""
+"I nostri oggetti di traduzione non sono \"documenti\". Sono file html e "
+"file po, con uno specifico formato e una codifica UTF-8 che deve essere "
+"mantenuta, e non corrotta, nel processo di trasferimento che sia l'email "
+"o altro."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
+msgid ""
+"We looked at 'pootle' as a front-end for translators. It didn't work "
+"well, needed an administrator, and a pootle-based process would suffer "
+"from a number of the above flaws."
+msgstr ""
+"Avevamo dato uno sguardo a 'pootple' come front-end per i traduttori. Non"
+" funzionava bene, aveva bisogno di un amministratore, e il processo "
+"pootle-based avrebbe sofferto di numerosi dei problemi di cui sopra."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
+msgid ""
+"In summary:\n"
+"Yes, we know it is somewhat of a hurdle to get started. It's really the "
+"only possible way we can do it. Give it a try, it really isn't that hard."
+msgstr ""
+"In sintesi:<\\b>\n"
+"Si, sappiamo che può essere un po' ostico partire. E' l'unico modo in cui"
+" possiamo farcela. Provaci, non è poi così difficile."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
+msgid "More Information"
+msgstr "Ulteriori Informazioni"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
+#, python-format
+msgid ""
+"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
+msgstr ""
+"Il canale #i2p'dev su IRC o il forum"
+" di traduzione su %(zzz)s."
+
diff --git a/i2p2www/translations/it/LC_MESSAGES/priority.po b/i2p2www/translations/it/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..9c2b8cbf
--- /dev/null
+++ b/i2p2www/translations/it/LC_MESSAGES/priority.po
@@ -0,0 +1,3479 @@
+# Italian translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# coso , 2013
+# coso , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-11-27 00:30+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: Italian "
+"(http://www.transifex.com/projects/p/I2P/language/it/)\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/blog/category.html:2
+msgid "Blog Category"
+msgstr "Categoria blog"
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr "Feed ATOM blog I2P per categoria: %(category)s"
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:92
+msgid "Blog"
+msgstr "Blog"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "Feed ATOM blog I2P"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr "Pubblicato in data %(date)s da %(author)s"
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "Altri post del blog…"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr "Pubblicato:"
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "Autore:"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Pacchetti I2P di Debian"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+"I pacchetti Debian \n"
+"sono stati testati e dovrebbero funzionare sulle piattaforme "
+"x86/x86_64 su cui gira:"
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr "Ubuntu (Precise 12.04 e più recenti)"
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+"Debian Linux (Squeeze e più recenti) & "
+"kFreeBSD"
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+"I pacchetti I2P potrebbero funzionare su sistemi non elencati "
+"qui sopra. Riporta eventuali problemi \n"
+"con questi pacchetti su Trac all'indirizzo\n"
+"https://trac.i2p2.de."
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Opzione 1: Versioni recenti di Ubuntu e le sue "
+"derivate (Prova questa se non usi Debian)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr "Opzione 2: Debian (incluse le derivate di Debian)"
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+"Istruzioni per Ubuntu Precise Pangolin (e più recenti) e derivate come "
+"Linux Mint & Trisquel"
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Aggiunta di PPA tramite riga di comando e installazione di I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Apri un terminale e inserisci:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"Questo comando aggiungerà il PPA a /etc/apt/sources.list.d e recupererà "
+"la\n"
+"chiave gpg con cui il repository è stato firmato. La chiave GPG "
+"garantisce\n"
+"che quei pacchetti non sono stati manomessi  dopo la loro compilazione."
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "Notifica al tuo gestore di pacchetti il nuovo PPA inserendo:"
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+"Questo comando recupererà l'elenco di programmi più recenti da ciascun\n"
+"repository attivato sul sistema, incluso il PPA \n"
+"aggiuntio con il comando di prima."
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "Adesso sei pronto per l'installazione di I2P!"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "Aggiunta del PPA usando Synaptic"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+"Apri Synaptic (Sistema -> amministrazione -> Gestore dei pacchetti "
+"Synaptic)."
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+"Quando Synaptic si apre, seleziona Repository dal menu "
+"Impostazioni."
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"Fai clc sulla scheda Altre fonti e su Aggiungi. Incolla"
+" ppa:i2p-maintainers/i2p nel campo dedicato alla riga APT e "
+"fai clic su Aggiungi fonte. Fai clic sul pulsante "
+"Chiudi quindi su Ricarica."
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+"Nel riquadro di filtro rapido, digita i2p e premi Invio. "
+"Quando i2p compare nell'elenco dei risultati, fai clic con "
+"il pulsante destro del mouse su i2p e seleziona "
+"Contrassegna per l'installazione. Dopo di che, potrebbe apparire"
+" un messaggio di popup Contrassegna modifiche necessarie "
+"aggiuntive?. Se capita, fai clic su Contrassegna quindi su "
+"Applica."
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+"Dopo il completamento della procedura di installazione, puoi passare alla"
+" sezione\n"
+"successiva per avviare I2P e "
+"configurarlo per il tuo sistema."
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr "Istruzioni per Debian"
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+"Nota: i punti sottostanti dovrebbe essere eseguiti con un accesso di "
+"amministratore (ad esempio, passando da utente normale\n"
+"a root con \"su\" o facendo precedere ogni comando da \"sudo\")."
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr "Aggiungi linee come le seguenti a %(file)s."
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the  key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+"Scarica la chiave usata per firmare il "
+"repository e aggiungila ad apt:"
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr "Notifica al tuo gestore di pacchetti il nuovo repository inserendo"
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+"Questo comando recupererà l'elenco di programmi più recenti da ogni\n"
+"repository attivato sul sistema, incluso quello I2P aggiunto nel punto \n"
+"1."
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+"Sei pronto a installare I2P! L'installazione del pacchetto i2p-"
+"keyring\n"
+"farà in modo di farti ricevere gli aggiornamenti della chiave GPG del "
+"repository."
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+"Dopo il completamento della procedura di installazione, puoi passare alla"
+" sezione successiva per avviare I2P e "
+"configurarlo per il tuo sistema."
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "Post-installazione"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+"Usando questi pacchetti I2P, il router I2P può essere arriavo nei \n"
+"tre modi che seguono:"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+""a richiesta" usando lo script i2prouter. Ti basta eseguire "
+""i2prouter\n"
+"start" da riga di comando. (Nota: non"
+" usare\n"
+"sudo e non eseguirlo con privilegi di amministrazione!)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""a richiesta" senza il wrapper di servizi java\n"
+"(necessario su sistemi diversi da Linux o diversi da x86) eseguendo "
+"\"i2prouter-nowrapper\".\n"
+"(Nota: strong>non/u>\n"
+"usare sudo e non eseguirlo con privilegi di amministrazione!)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"come servizio che viene eseguito automaticamente all'avvio del sistema, "
+"anche \n"
+"prima di effettuare l'accesso. Il servizio può essere attivato con "
+"\"dpkg-reconfigure\n"
+"i2p\" con privilegi di amministrazione o usando sudo. Questa è la "
+"modalità consigliata."
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+"Per la primissima installazione, ricorda di regolare il tuo NAT o "
+"firewall\n"
+"se puoi. Le porte da inoltrare possono essere trovate nella \n"
+"pagina di configurazione di rete nel console router. Se serve aiuto "
+"in merito al port forwarding,\n"
+"è possibile trovare qualche dritta su portforward.com."
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"Esamina e modifica le impostazioni della larghezza di banda nella\n"
+"pagina di "
+"configurazione,\n"
+"perché le impostazioni predefinite di 96 KB/s per il download e 40 KB/s "
+"per l'upload sono abbastanza conservative."
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"Se vuoi raggiungere gli eepsite con il tuo browser, dai un'occhiata alla "
+"pagina impostazione proxy del browser "
+"per delle semplici istruzioni."
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Download"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Download I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Dipendenze"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+"\n"
+"Java Runtime 1.5 o superiore.\n"
+"(Oracle Java versione 7,\n"
+"OpenJDK 7, o\n"
+"IcedTea7\n"
+" consigliati,\n"
+"eccetto che per il Raspberry Pi: Oracle 8 Early "
+"Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determina la versione di Java installata "
+"qui\n"
+"o digita java -version al prompt dei comandi.\n"
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "Pulisci installazioni"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr "seleziona un link alternativo"
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Scarica il file ed eseguilo."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Scarica il fil e fari doppio clic su di esso (se la cosa funziona) oppure"
+"\n"
+"    digita java -jar i2pinstall_%(i2pversion)s.jar in un "
+"terminale per eseguire il\n"
+"    programma di installazione.\n"
+"    Potrebbe essere possibile fare clic con il pulsante destro del mouse "
+"e selezionare\n"
+"    "Apri con Java"."
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "Installazione da riga di comando (non interattiva):"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Scarica il file del programma di installazione grafica per OSX "
+"%(i2pversion)s e\n"
+"    esegui java -jar i2pinstall_%(i2pversion)s.jar -console "
+"da riga di comando."
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Scarica il fil e fari doppio clic su di esso (se la cosa funziona) oppure"
+"\n"
+"    digita java -jar i2pinstall_%(i2pversion)s.jar in un "
+"terminale per eseguire il\n"
+"    programma di installazione.\n"
+"    Su alcune piattaforme potrebbe essere possibile fare clic con il "
+"pulsante destro del mouse e selezionare\n"
+"    "Apri con Java"."
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Scarica il file del programma di installazione grafica e\n"
+"    esegui java -jar i2pinstall_%(i2pversion)s.jar -console "
+"da riga di comando."
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Sono disponibili i pacchetti per Debian & Ubuntu."
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+"    The latest dev build is version %(devbuild)s, and is available from\n"
+"    str4d's eepsite."
+msgstr ""
+"Il file precedente rappresenta la versione attuale.\n"
+"    La build di sviluppo più recente è la versione %(devbuild)s ed è "
+"disponibile\n"
+"    sull'eepsite di str4d."
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+"      are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+"      the other."
+msgstr ""
+"Le versioni per il pubblico e quelle di sviiluppo dell'APK di I2P non "
+"sono compatibili perché \n"
+"      sono firmate rispettivamente da zzz e str4d. Disinstallane una "
+"prima di installare\n"
+"      l'altra."
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "Pacchetto sorgente"
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+"    or via Git from git.repo.i2p or Github.\n"
+"    
            \n"
+"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+"In alternativa, puoi recuperare la fonte su monotone\n"
+"    o tramite Git su git.repo.i2p oppure Github.\n"
+"    
            \n"
+"    Esegui (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) quindi\n"
+"    esegui l'installazione grafica o l'installazione non interattiva come"
+" sopra."
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"I file sono firmati da zzz,\n"
+"la cui chiave si trova qui."
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"I2P può anche essere scaricato dalle nostre pagine del progetto su Launchpad e Google Code."
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"Dopo aver eseguito l'installazione su Windows, fai semplicemente clic sul"
+" pulsante \"Avvia I2P\"\n"
+"che richiama la router "
+"console,\n"
+"che contiene ulteriori istruzioni."
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"Sui sistemi Unix e simili, I2P può essere avviato come un servizio\n"
+"usando lo script \"i2prouter\" che si trova nella cartella che hai "
+"selezionato per I2P.\n"
+"Accedere a quella cartella in un terminale ed eseguire il comando \"sh "
+"i2prouter status\"\n"
+"dovrebbe indicarti lo stato del router. Gli argomenti \"start\", \"stop\""
+" e \"restart\"\n"
+"controllano il servizio. Puoi accedere alla router console\n"
+"nella sua posizione usuale.\n"
+"Gli utenti su OpenSolaris e altri sistemi per i quali il wrapper (i2psvc)"
+" non è supportato\n"
+"dovrebbero invece avviare il router con \"sh runplain.sh\"."
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"Quando lo installi per la prima volta, ricorda di regolare il tuo NAT "
+"o firewall\n"
+"se puoi, tenendo presente le porte usate da I2P per l'accesso a Internet,"
+"\n"
+"descritte qui tra le altre porte.\n"
+"Se hai aperto correttamente la porta per il traffico TCP in entrata, "
+"attiva il traffico TCP in entrata anche nella\n"
+"pagina di "
+"configurazione."
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"Inoltre, esamina e modifica le impostazioni della larghezza di "
+"banda nella\n"
+"pagina di "
+"configurazione,\n"
+"perché le impostazioni predefinitie di of 96 KBps per il download e 40 "
+"KBps per l'upload sono abbastanza lente."
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "Aggiornamento da versioni precedenti:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr ""
+"sono disponibili sia gli aggiornamenti automatici che manuali per questa "
+"versione."
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "Aggiornamenti automatici"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+"Se usi la versione 0.7.5 o successiva, il tuo router dovrebber rilevare "
+"la presenza di una \n"
+"nuova versione. Per aggiornare, fai semplicemente clic su 'Scarica "
+"aggiornamento' nel console router\n"
+"quando appare."
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"A causa di un bug nella versione 0.7.6, chi ha installato I2P per la "
+"prima volta con quella versione\n"
+"e non ha aggiornato manualmente\n"
+"potrebbe ricevere un errore \"versione scaricata non maggiore di quella "
+"attuale\",\n"
+"e dovrebbe quindi usare il metodo di aggiornamento manuale qui sotto."
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Se usi la versione 0.7.4 o precedente, consulta le\n"
+"note della versione 0.7.5\n"
+"per informazioni importanti su come configurare il router per ricevere\n"
+"la versione in automatico."
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Se usi la versione 0.6.1.30 o precedente, consulta le\n"
+"istruzioni\n"
+"per informazioni importanti su come configurare il router per ricevere\n"
+"la versione in automatico."
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+"    router console "
+"allowing\n"
+"    you to download and install the new release by just clicking on that\n"
+"    link."
+msgstr ""
+"Se hai riconfigurato il router seguendo le istruzioni, dovresti vedere un link nel \n"
+"    console router che ti"
+" consente di\n"
+"    scaricare e installare la nuova versione semplicemente facendo clic "
+"sul\n"
+"    link."
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr "In alternativa, puoi usare il metodo manuale come spiegato qui sotto."
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "Aggiornamenti manuali"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and rename as i2pupdate.zip.\n"
+"    (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+"    resulting i2pupdate.zip to your I2P installation directory).  You do"
+" \n"
+"    NOT need to unzip that file."
+msgstr ""
+"Scarica il file nella cartella di installazione di I2P\n"
+"    e rinominalo come i2pupdate.zip.\n"
+"    (in alternativa, puoi ottenere il sorgente come sopra ed eseguire "
+"\"ant updater\", quindi copiare il\n"
+"    file risultante nella cartella di installazione di I2P).  \n"
+"    NON occorre scompattare il file."
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+"Fai clic su \"Riavvia\""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "Vai a bere un caffè e ritorna tra 11 minuti"
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Il file è firmato da zzz,\n"
+"la cui chiave si trova qui."
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "Versioni precedenti"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"Le versioni precedenti sono disponibli su Google "
+"Code\n"
+"e Launchpad\n"
+", nonché sulla rete I2P all'indirizzo %(echelon)s."
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "Selezione mirror"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "File:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "Qualsiasi mirror"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+"Per ritirare i premi, l'autore non deve essere pagato da altre "
+"organizzazioni\n"
+"o team per il lavoro svolto (per esempio, non sono valide le domande "
+"degli studenti del Google Summer of Code)."
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations.  Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"L'ammontare dei premi può essere aumentato da ulteriori donazioni. Credi\n"
+"siano importanti? Aggiungi la tua, \n"
+"evidenziando il valore della %(donatename)s sovvenzione!"
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "Non trovato"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+"Già... la risorsa che stavi cercando ha un nome diverso, non esiste "
+"oppure è stata rimossa."
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "Errore del server"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "Errore del server 500"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "Uhm... si è verificato un qualche tipo di errore nel server."
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "Mirror"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "Sicuro"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "Varie"
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Collegamenti"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "Impressum"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "Magliette!"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "Europa"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "Stati Uniti"
+
+#: i2p2www/pages/global/footer.html:31 i2p2www/pages/global/nav.html:133
+msgid "Donate"
+msgstr "Dona"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr "Salta navigazione"
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "Logo I2P"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "Il progetto Internet invisibile"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+"L'aggiornamento più recente di questa pagina risale a %(lastupdated)s e "
+"si riferisce alla versione del router %(accuratefor)s."
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "L'aggiornamento più recente di questa pagina risale a %(lastupdated)s."
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "Questa pagina si riferisce alla versione del router %(accuratefor)s."
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr "Precedente"
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr "Successivo"
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr "Pubblicato in"
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "Informazioni su"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Introduzione a I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "Confronti"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "Riepilogo dei confronti"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Altre reti anonime"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Documentazione"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Indice della documentazione"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Come funziona?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "Introduzione leggera"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "Introduzione tecnica"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "Modello di rischio"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Routing garlic"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "Database di rete"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "Routing tunnel"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "Selezione peer"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Cifratura"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Specifiche"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "File di blocco"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "Strutture comuni"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "File di configurazione"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:56
+msgid "Datagrams"
+msgstr "Datagrammi"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr "File GeoIP"
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:88
+msgid "Plugins"
+msgstr "Plugin"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:55
+msgid "Streaming library"
+msgstr "Libreria di streaming"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "Creazione tunnel"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "Messaggi tunnel"
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "Aggiornamenti software"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:60 i2p2www/pages/global/nav.html:113
+msgid "Applications"
+msgstr "Applicazioni"
+
+#: i2p2www/pages/global/nav.html:62
+msgid "Supported applications"
+msgstr "Applicazioni supportate"
+
+#: i2p2www/pages/global/nav.html:63
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Protocols"
+msgstr "Protocolli"
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Protocol stack"
+msgstr "Stack del protocollo"
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Transports"
+msgstr "Trasporti"
+
+#: i2p2www/pages/global/nav.html:75
+msgid "Transport layer overview"
+msgstr "Informazioni generali sul livello di trasporto"
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Tunnels"
+msgstr "Tunnel"
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Tunnel implementation"
+msgstr "Implementazione tunnel"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Unidirectional tunnels"
+msgstr "Tunnel unidirezionali"
+
+#: i2p2www/pages/global/nav.html:84
+msgid "Old implementation"
+msgstr "Implementazione precedente"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Naming and addressbook"
+msgstr "Nominativi e rubrica"
+
+#: i2p2www/pages/global/nav.html:91
+msgid "Team"
+msgstr "Squara"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Hall of Fame"
+msgstr "Galleria dei migliori"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Academic papers and peer review"
+msgstr "Saggi accademici e recensioni dei peer"
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Presentations, tutorials and articles"
+msgstr "Presentazioni, tutorial e articoli"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Contact us"
+msgstr "Contattaci"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Help"
+msgstr "Aiuto"
+
+#: i2p2www/pages/global/nav.html:101
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "How to browse I2P"
+msgstr "Come sfogliare I2P"
+
+#: i2p2www/pages/global/nav.html:103
+msgid "Glossary"
+msgstr "Glossario"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Performance"
+msgstr "Prestazioni"
+
+#: i2p2www/pages/global/nav.html:105 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Forum"
+
+#: i2p2www/pages/global/nav.html:108
+msgid "Volunteer"
+msgstr "Volontario"
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Get involved!"
+msgstr "Partecipa anche tu!"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Develop"
+msgstr "Sviluppo"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Licenses"
+msgstr "Licenze"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Release signing keys"
+msgstr "Chiavi di firma per il pubblico"
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Signed keys"
+msgstr "Chiavi firmate"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Developers keys"
+msgstr "Chiavi per gli sviluppatori"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Bug tracker"
+msgstr "Tracker dei bug "
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Academic research"
+msgstr "Ricerca accademica"
+
+#: i2p2www/pages/global/nav.html:122
+msgid "Open research questions"
+msgstr "Domande di ricerca aperte"
+
+#: i2p2www/pages/global/nav.html:123
+msgid "Guides"
+msgstr "Guide"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "New developers"
+msgstr "Nuovi sviluppatori"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Using an IDE with I2P"
+msgstr "Utilizzo di IDE con I2P"
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Developer guidelines and coding style"
+msgstr "Linee guida di sviluppo e stile di programmazione"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "New translators"
+msgstr "Nuovi traduttori"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Bounties"
+msgstr "Premi"
+
+#: i2p2www/pages/global/nav.html:134 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Riunioni"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Roadmap"
+msgstr "Roadmap"
+
+#: i2p2www/pages/global/nav.html:136
+msgid "Task list"
+msgstr "Attività"
+
+#: i2p2www/pages/global/nav.html:139
+msgid "Language"
+msgstr "Lingua"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr "Feed ATOM riunioni I2P"
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "Log delle riunioni I2P precedenti"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr ""
+"Le riunioni sono attualmente in attesa fino a quando potrà essere scelto "
+"un momento più appropriato."
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"Se hai qulcosa da discutere, cerca gli sviluppatori su IRC nel canale "
+"#i2p-dev.\n"
+"Sono disponibili anche gli Aggiornamenti di "
+"stato degli sviluppatori."
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr "Riunione di sviluppo I2P %(id)s"
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr "Log IRC completo"
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "Per argomento"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "Per data"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "Per autore"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
            \n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
            \n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+"Invia voci nuove o corrette a\n"
+"%(email)s.
            \n"
+"Se puoi, formattale come BibTeX; consulta la nostra\n"
+"pagina di risorse BibTeX con qualche "
+"esempio.
            \n"
+"Ricorda di includere gli URL se possibile:\n"
+"i documenti offline sono meno utili."
+
+#: i2p2www/pages/papers/list.html:94
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"Free Haven's anonymity bibliography."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Contatto"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like OFTC,\n"
+"  EIN and Freenode.\n"
+"  All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+"Le nostre reti IRC principali sono la rete Irc2 presente all'interno di "
+"I2P; un tunnel predefinito a questa rete viene impostato al momento "
+"dell'installazoine di un nuovo router.\n"
+"  Siamo anche prsenti su molteplici reti standard come OFTC,\n"
+"  EIN e Freenode.\n"
+" Tutti i canali relativi a I2P su tutte queste reti sono collegati ai "
+"canali principali su Irc2P tramite dei bot di ripetizione."
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Elenco canali:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "Discussione generali su i2p"
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "Off-topic"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "Conferenza di sviluppo"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Canale di aiuto"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"La maggior parte delle discussioni sullo sviluppo di I2P ha luogo sul forum degli sviluppatori I2P. Questo è "
+"solitamente il miglior luogo dove cominciare a fare domande, se il canale"
+" IRC degli sviluppatori non è attivo."
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "Liste di distribuzione"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+"I2P dispone di una lista di distribuzione, ma viene raramente usata "
+"perché il team di sviluppo attuale è relativamente piccolo e preferisce "
+"comunicare tramite IRC o sul forum. Questa situazione potrebbe cambiare "
+"in futuro."
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "Iscrizione"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+"Per iscriversi a una lista di distribuzione, accedi alla pagina "
+"informativa della lista (il link è indicato qui sotto) e compila il "
+"modulo. Possono essere usati indirizzi di posta elettronica interni di "
+"I2P (foobar@mail.i2p)."
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "Annullamento dell'iscrizione"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+"Per annullare la propria iscrizione alla lista di distribuzione o "
+"modificare le opzioni di iscrizione, accedi alla pagina informativa della"
+" lista (il link è indicato qui sotto) e inserisci l'indirizzo di posta "
+"elettronica usato per iscriverti."
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Liste"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Archivio"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+"Discussione generale I2P, qualunque cosa che non si adatta a una lista "
+"diversa finisce qui."
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+"Non ti piacciono le liste di distribuzione? Allora questa opzione fa per "
+"te: tutte le liste di distribuzione sono disponibili anche tramite NNTP."
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr "Mappatura gruppi-liste:"
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Server:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Domande poste frequentemente"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Indice"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "Generale"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "Su quali sistemi gira I2P?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr "Che cos'è un \"eepsite\" e come configura il browser per accedervi?"
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "Il mio router ha pochissimi peer attivi, è normale?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr "Che cosa significano i numeri relativi a x/y attivi nel console router?"
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+"I miei peer attivi / peer conosciuti / tunnel partecipanti / connessioni "
+"/ larghezza di banda variano in modo drammatico nel tempo! C'è qualcosa "
+"che non va?"
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "L'utilizzo di un outproxy è sicuro?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr "La maggior parte degli eepsite all'interno di I2P non funziona?"
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Quali porte usa I2P?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "Perché I2P si mette in ascolto per le connessioni sulla porta 32000?"
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "Credo di aver trovare un bug, dove lo segnalo?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr "Che cos'è successo a *.i2p.net? Che cos'è successo a jrandom? I2P è morto?"
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "Ho una domanda!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr "Impostazione"
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+"Il mio router è stato impostato da diversi minuti e ha zero o pochissime "
+"connessioni."
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "Perché I2P è così lento?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+"Mi mancano un sacco di host nella rubrica. Potete suggerirmi qualche buon"
+" link a cui iscrivermi?"
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "Come posso impostare il mio eepsite personale?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "Domande sui plugin Bittorrent / I2PSnark / Azureus per I2P?"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "Come mi connetto a IRC all'interno di I2P?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "Non riesco ad accedere a siti Internet normali tramite I2P."
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "Non riesco ad accedere a siti https:// o ftp:// tramite I2P."
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr "È possibile usare I2P come proxy SOCKS?"
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Come devo configurare il browser?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+"Come posso accedere alla web console dagli altri miei computer o "
+"proteggerla con una password?"
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr "Come posso usare le applicazioni dagli altri miei computer?"
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr "Come posso effettuare il reseed manualmente?"
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "Il mio router usa troppa CPU?!?"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "Equivoci"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr ""
+"Come posso accedere a IRC, Bittorrent o altri servizi sull'Internet "
+"normale?"
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+"Il mio router è un \"nodo di uscita\" (outproxy) sull'Internet normale? "
+"Non voglio che lo sia."
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+"Sono contro a determinati tipi di contenuti. Come posso evitare di "
+"distribuirli, immagazzinarli o accedervi?"
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Errori e relative soluzioni"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+"Uso FreeBSD e quando avvio I2P ricevo un errore relativo a "
+"libm.so.4!"
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+"Nel wrapper.log osservo un errore relativo alla "
+"famiglia di protocolli non disponibile quando I2P viene "
+"caricato"
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "collegamento"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+"Sebbene ci siano riscontri di I2P funzionante su PC con basse prestazioni"
+" addirittura come i Pentium II con 64 MB di RAM, l'esperienza sarà "
+"migliore sui Pentium III (o superiori) con 128 MB di RAM (o di più). Un "
+"grafico con il confronto delle prestazioni dei "
+"vari ambienti JRE può essere repirto all'indirizzo %(chart)s, ma per dirla in breve: se possibile, "
+"usa Sun/Oracle Java o OpenJDK."
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+"I2P è stato testato su Windows, Linux, FreeBSD (leggere la nota qui sotto), OSX e OpenSolaris. Esistono progetti "
+"in corso per portare I2P sulla piattaforma Android."
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr "Ecco qualche luogo, scegline uno o di più."
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "Discuti con gli sviluppatori su IRC nel canale #i2p-dev"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr "Includi le relative informazioni prese dai log del router e del wrapper."
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+"L'iscrizione predefinita è a http://www.i2p2.i2p/hosts.txt che viene "
+"raramente aggiornato.\n"
+"Se non disponi di un'altra iscrizione, potresti dover usare spesso i "
+"collegamenti \"jump\", il che è\n"
+"seccante."
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+"Ecco qualche altro collegamento per la rubrica pubblica. Potresti "
+"aggioungerne uno o due\n"
+"al tuo elenco"
+" di iscrizioni susidns.\n"
+"Non c'è bisogno di aggiungerli tutti, perché si sincronizzano l'uno con "
+"l'altro periodicamente.\n"
+"I collegamenti che usano un applicazione cgi-bin application si avvalgono"
+" di svariate strategie per minimizzare\n"
+"il numero di indirizzi duplicati, per cui dovrebbero essere più "
+"efficienti.\n"
+"Ricorda che iscriversi a un servizio hosts.txt è un atto di \"fiducia\" "
+"perché un'iscrizione\n"
+"malevola potrebbe fornirti indirizzi sbagliati. Per cui rifletti se "
+"intendi\n"
+"fidarti o no.\n"
+"Gli operatori di tali servizi potrebbero avere diverse regole per gli "
+"host elencati.\n"
+"La presenza di un sito in questa lista non implica approvazione."
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+"Jrandom è stato lo sviluppatore capo di I2P e\n"
+"Syndie per diversi anni.\n"
+"Non sappiamo se jrandom farà ritorno o no.\n"
+"I dominii *.i2p.net sono stati lasciati in uno stato di non funzionamento"
+" dopo un blackout\n"
+"capitato all'azienda che si occupa del loro hosting."
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+"Consulta questa pagina con il messaggio di "
+"addio di jrandom e informazioni aggiuntive\n"
+"sulla migrazione di *.i2p.net a questo sito web."
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr "I2P rimane in attivo sviluppo."
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+"Esistono numerose possibile cause di un elevato utilizzo della CPU. Ecco "
+"un elenco di controllo:"
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+"Prova a usare OpenJDK oppure Java di Sun/Oracle se sono disponibili sul "
+"tuo sistema. Puoi controllare \n"
+"la versione di java installata digitando java -version al "
+"prompt dei \n"
+"comandi o in un terminale. Le prestazioni tendono a soffrire con "
+"implementazioni di java diverse."
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+"Hai un client BitTorrent in esecuzione su I2P? Prova a ridurre il numero "
+"di torrent, i limiti di banda\n"
+"oppure spegnerlo completamente per vedere se aiuta a risolvere il "
+"problema."
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+"I limiti della larghezza di banda sono impostati troppo in alto? È "
+"possibile che stia passando troppo traffico nel tuo\n"
+"router I2P che è quindi sovraccarico. Prova ad abbassare l'impostazione "
+"dellapercentuale di condivisione della banda nella pagina di configurazione."
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+"Assicurati di avere la versione più recente di I2P in esecuzione per "
+"avvantaggiarti delle prestazioni migliorate e dei problemi risolti."
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+"C'è memoria sufficiente destinata all'uso di I2P? Osserva il grafico "
+"della memoria nella pagina dei "
+"grafici per controllare se\n"
+"l'uso di memoria è \"fisso\"—la JVM passa la maggior parte del "
+"proprio tempo nell'attività di\n"
+"garbage collection. Aumenta l'impostazione "
+"wrapper.java.maxmemory in wrapper.config."
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+"L'utilizzo della CPU è semplicemente più elevato di quanto vorresti "
+"oppure rimane fisso su 100% per un periodo di tempo molto lungo?\n"
+"Se è fisso, ciò potrebbe essere dovuto a un bug. Cerca nei log per "
+"eventuali indizi."
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+"Forse stai usando la libreria BigInteger basata su Java invece della "
+"versione originale,\n"
+"specialmente se stai usandoo un sistema operativo o un hardware insolito "
+"o nuovo (OpenSolaris, mipsel, ecc.).\n"
+"Consulta la pagina jbigi per istruzioni sui\n"
+"metodi di diagnosi, compilazione e collaudo."
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+"Se la tua libreria jbigi originale funziona senza problemi, l'utente più "
+"esoso di \n"
+"CPU potrebbe instradare il traffico per i tunnel partecipanti. Questo fa "
+"uso di CPU\n"
+"perché con ciascun salto uno strato di cifratura deve essere "
+"decodificato.\n"
+"Puoi limitare il traffico partecipanti in due modi: riducendo la\n"
+"banda condivisa su\n"
+"confignet.jsp,\n"
+"oppure impostando router.maxParticipatingTunnels=nnn su\n"
+"configadvanced.jsp."
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+"Uhm. I2P è una rete anonima, quindi questa è una questione complicata.\n"
+"I2P è progettato per resistere alla censura offrendo un mezzo che tutti "
+"possono usare per comunicare liberamente. \n"
+"Il modo migliore di tenere il tuo computere libero da traffico (criptato)"
+" che non è di tuo gradimento è quello di non usare affatto I2P.\n"
+"La libertà di parola ha dei costi.\n"
+"Ma vediamo di analizzare il problema dividendolo in tre parti:"
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+"Distribuzione - Tutto il traffico I2P è cifrato a strati multipli."
+" Non si può sapere \n"
+"il contenuto di un messaggio, la sua fonte e la sua destinazione.\n"
+"Tutto il traffico che indirizzi è interno alla rete I2P, tu non sei un nodo di uscita (outproxy).\n"
+"La tua unica alternativa è di rifiutare di indirizzare\n"
+"qualsivoglia traffico, impostando a 0 la larghezza di banda "
+"condivisa o il numero massimo di tunnel partecipanti (vedi sopra).\n"
+"Ti saremmo grati se evitassi di assumere un comportamento del genere, "
+"dovresti invece dare una mano alla rete indirizzando il traffico per "
+"altri.\n"
+"Più del 95% degli utenti lo fa."
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+"Deposito - I2P non effettua la distribuzione di depositi di "
+"contenuti. Devi pensare a \n"
+"Freenet.\n"
+"Sul tuo computer non viene depositato il contenuto di nessuno eseguendo "
+"I2P."
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+"Accesso - Se ci sono degli eepsite che non ti piacciono, non "
+"visitarli.\n"
+"Altrimenti usa un proxy di blocco come Privoxy o qualche tipo di \"balia "
+"della rete\"."
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+"No. Questo è normale.Tutti i router si regolano in maniera dinamica al "
+"cambiare delle condizioni della rete e delle richieste."
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+"Potrebbe essere necessario fare il reseed del tuo router I2P. Con le "
+"versioni recenti di I2P, puoi accedere a http://localhost:7657/configreseed"
+" e fare clic sul pulsante Salva modifiche e fail il reseed "
+"adesso. Se questo metodo non funziona—o se stai usando una "
+"versione molto vecchia—potrebbe rendersi necessario fare il reseed manualmente."
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+"L'URL del reseed cambiò qualche anno fa. Se questa è la tua prima "
+"installazione e hai installato\n"
+"auan versione vecchia (0.6.1.30 o precedente), oppure\n"
+"se non hai eseguito I2P da tanto tempo, devi cambiare l'URL e quindi\n"
+"fare clic su \"Reseed\" nella console per trovare altri router.\n"
+"Una volta che il tuo router è in esecuzione,\n"
+"in configadvanced.jsp,"
+"\n"
+"aggiungi la riga i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OPPURE i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (sia una che "
+"l'latra dovrebbero funzionare),\n"
+"quindi fai clic su \"Applica\", e sul link \"reseed\" sulla sinistra."
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+"Questo funziona se stai eseguendo la versione 0.6.1.27 o successiva.\n"
+"Se usi la versione 0.6.1.31 o successiva, probabilmente non ti serve.\n"
+"Se stai eseguendo la versinoe 0.6.1.26 o precedente, segui le\n"
+"istruzioni per reseed manuale qui sotto\n"
+"oppure installa la versione più "
+"recente.\n"
+"Un possibile metodo alternativo - aggiungi\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"a wrapper.config, arresta completamente il router, quindi riavvialo e fai"
+" clic su \"reseed\".\n"
+"Facci sapere se funziona."
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+"...ma dovresti *davvero* aggiornare "
+"passando alla versione più recente."
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+"Se il tuo router ha 10 o più peer attivi, tutto va bene. Le modifiche "
+"nelle versioni 0.6.1.31 e 0.6.1.32 hanno migliorato\n"
+"l'efficienza del router e hanno ridotto in modo efficace il numero di "
+"peer attivi.\n"
+"Il router dovrebbe mantenere le connessioni verso pochi peer in "
+"ogni momento.\n"
+"Il modo migliore per avere una \"connessione migliore\" alla rete è di condividere più banda."
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+"Il mio router è un \"nodo di uscita\" sull'Internet normale? Non voglio "
+"che lo sia."
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+"No. A differenza di Tor,\n"
+"i \"nodi di uscita\" o \"outproxies\" non sono una parte intrinseca della"
+" rete.\n"
+"Solo i volontari che impostano ed eseguono applicazioni separate "
+"ripeteranno il traffico verso la rete Internet solita.\n"
+"Ne esitono pochi, anzi, pochissimi."
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+"Vedi sopra. Esistono pochissimi \"outproxy\" HTTP \"outproxies\", non "
+"fanno intrinsecamente parte della rete\n"
+"e potrebbero non funzionare.\n"
+"Inoltre, i vecchi outproxy squid.i2p, true.i2p, e krabs.i2p sono "
+"scomparsi.\n"
+"L'unico outproxy al momento è false.i2p.\n"
+"Per usarlo, modifica le tue impostazioni "
+"i2ptunnel per eepProxy\n"
+"e imposta il tuo elenco di outproxy su 'false.i2p' (only).\n"
+"Quindi interrompi e riavvia l'eepProxy.\n"
+"Se non funziona, significa che l'outproxy non funziona. Non è colpa di "
+"I2P.\n"
+"Se il motivo principale per usare una rete anonima è quello di accedere "
+"ai siti anonimamente\n"
+"sull'Internet normale, forse dovresti provare Tor."
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+"All'interno di I2P non c'è bisogno di HTTPS perché tutto il traffico è "
+"criptato punto-a-punto.\n"
+"FTP non è supportato per motivi tecnici."
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+"Non ci sono \"outproxy\" FTP verso Internet—potrebbe addirittura "
+"non essere possibile impostarne uno.\n"
+"Qualunque altro tipo di outproxy potrebbe funzionare se viene impostato "
+"con il tunnel standard. \n"
+"Se desideri impostare qualche tipo di outproxy, cerca con attenzione i "
+"rischi potenziali in cui potresti incorrere.\n"
+"La comunità I2P potrebbe, o non potrebbe, essere in grado di darti una "
+"mano con gli aspetti tecnici, sentiti libero di porre domande."
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+"Come spiegato tante volte in precedenza, qualunque outproxy esistente non"
+" fa parte della rete in quanto tale.\n"
+"Si tratta di servizi messi a disposizione da singoli individue e, come "
+"tali,\n"
+"potrebbero essere operativi o no in un dato momento."
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
            \n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+"Aggiornamento: grazie al lavoro di h2ik, esiste un outproxy https "
+"outproxy disponibile all'uso tramite I2P. A partire dalla versione di I2P"
+" 0.8.4 il "
+"tunnel è configurato senza dover intervenire.
            \n"
+"Se l'outproxy https non fosse disponibile nella tua versione di I2P, puoi"
+" aggiugerlo facilmente facendo così:"
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+"Apri il gestore dei"
+" tunnel i2p. Scorri la pagina fino in fondo."
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+"Scegli CONNETTI nella menu a comparsa Nuovo tunnel client, "
+"fai clic su Crea"
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+"Nella nuova pagina, dai un nome e una descrizione al nuovo "
+"tunnel https a piacere.\n"
+"Il punto di accesso è la tua porta locale consigliata 4445 "
+"per il nuovo proxy https.\n"
+"L'outproxy dovrebbe essere l'indirizzo .i2p dell'outproxy che "
+"supporta https. \n"
+"Consulta questo articolo del forum di h2ik per "
+"l'indirizzo. \n"
+"Assicurati che siano impostate le opzioni Client condiviso, "
+"Ritarda connessione, Avvio automatico.\n"
+"Le altre opzioni dovrebbero essere lasciate sui loro valori predefiniti. "
+"Fai clic su Salva. Nel gestore dei tunnel, fai clic sul pulsante "
+"Avvia accanto al tuo nuovo tunnel."
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+"In Firefox, fai clic su "
+"Strumenti>Opzioni>Avanzate>Rete>Impostazione."
+"\n"
+"Togli il segno di spunta a Usa questo proxy per tutti i "
+"protocolli, imposta il proxy SSL: su localhost:4445."
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "Fine."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+"\n"
+"Questa è una domanda a cui solo tu puoi dare risposta perché quella "
+"corretta dipende dal tuo comportamento, \n"
+"dal tipo di minaccia e dal tuo livello di"
+" fiducia in cui fa funzionare l'outproxy."
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+"Al pari di Tor, I2P non cripta Internet con la magia.\n"
+"Sei vulnerabile ai tentativi di spionaggio messi in atto dagli operatori "
+"dell'outproxy.\n"
+"La FAQ"
+" di TOR\n"
+"offre spiegazioni adeguate a questa problematica."
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+"Inoltre, potresti essere vulnerabile alle collusione tra l'operatore "
+"dell'outproxy e\n"
+"quelli di altri servizi I2P, se usi gli stessi tunnel (\"client "
+"condivisi\").\n"
+"Esiste una discussione aggiuntiva in merito su %(zzz)s."
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+"A meno che non sia stato impostato un outproxy per il servizio a cui vuoi"
+" collegarti, non è possibile farlo.\n"
+"Ci sono solo tre tipi di outproxy in funzione al momento: HTTP, HTTPS e "
+"e-mail. Ricorda che non c'è un outproxy SOCKS.\n"
+"Se è questo il servizio che ti serve, prova Tor."
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+"Se prendi in considerazione ogni singolo eepsite che sia mai stato "
+"creato, sì, la maggior parte di essi non funziona.\n"
+"Gli utenti e gli eepsite vanno e vengono.\n"
+"Un buon modo per cominciare dentro I2P è di controllare l'elenco di "
+"eepsites attualmente attivi.\n"
+"%(eepstatus)s tiene traccia degli eepsite "
+"attivi."
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+"Fai clic sul link Website\n"
+"in alto nella pagina del router per le istruzioni."
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+"Perché i download, i torrent, la navigazione web e tutto il resto sono "
+"così lenti su I2P?\n"
+"La cifratura e l'instradamento all'interno della rete I2P aggiungono una "
+"quantità sostanziale di informazione aggiuntiva e limitano la banda.\n"
+"L'anonimato ha il suo prezzo da pagare."
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+"Inoltre, sia tu che tutti gli utenti dovreste probablimente aumentare i "
+"limiti che avete impostato per la larghezza di banda.\n"
+"Le due impostazioni chiave sono i limiti di banda per il traffico in "
+"entrata e in uscita nella\n"
+"pagina di "
+"configurazione.\n"
+"Con le impostazioni predefinite di 32 KBps, di solito non si va oltre i "
+"15KBps come velocità di trasferimento in I2PSnark.\n"
+"L'aumento delle impostazioni (mantenendole entro i limiti della "
+"connessione attuale)\n"
+"farà crescere la velocità potenziale di trasferimento per I2PSnark e "
+"tutte le altre applicazioni."
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+"Come se non bastasse, disponi di sufficiente banda condivisa configurata "
+"per consentire ai tunnel coinvolti\n"
+"l'instradamento tramite il tuo router? Credici o meno, consentire il "
+"passaggi di traffico\n"
+"ti mantiene ben integrato nella rete e giova alla velocità dei tuoi "
+"trasferimenti."
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+"I lavori su I2P sono tuttora in corso. Ci sono tanti miglioramenti e "
+"risoluzoni di problemi che vengono implementati e, \n"
+"di solito, eseguire la versione più recente aiuta a migliorare le "
+"prestazioni.\n"
+"Se non l'hai già fatto, installa la "
+"versione più recente."
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+"Consulta la\n"
+"FAQ per Bittorrent di "
+"I2P"
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+"\n"
+"Un tunnel verso il server IRC principale all'interno di I2P, Irc2P, viene"
+" creato al momento dell'installazione di I2P (consulta\n"
+"la pagina di "
+"configurazione di I2PTunnel)\n"
+"ed è avviato automaticamente quando si avvia il router I2P. Per "
+"connetterti, istruisci il tuo client\n"
+"IRC a connettersi a localhost 6668. I client simili a XCha "
+"possono creare una nuova\n"
+"rete con il server localhost/6668 (ricorda di mettere il "
+"segno di spunta sull'opzione "Bypassa\n"
+"il server proxyr" nel caso in cui tu abbia un server proxy "
+"preconfigurato)."
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface.  However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+"Per motivi di sicurezza, la console admin del router di default rimane in"
+" ascolto soltanto\n"
+"delle connessioni sull'interfaccia locale. Tuttavia, con qualche "
+"intervento,\n"
+"puoi fare in modo che sia accessibile da remoto:"
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"with 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+"Apri ~/.i2p/clients.config e sostituisci
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"con 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+"Accedi a http://localhost:7657/configui"
+"\n"
+"e aggiungi un nome utente e password per la console se vuoi."
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+"Accedi a http://localhost:7657/index.jsp"
+"\n"
+"e fai clic su \"Riavvia garbatamente\", un'opzione che riavvia la JVM e "
+"ricaricare le applicazioni client."
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+"Dopo d che, dovresti essere in grado di raggiungere la console da remote."
+" Ricarica il router at\n"
+"http://127.0.0.1:7657 e ti sarà richiesto il nome utente e la password "
+"che indicato al punto 2\n"
+"qui sopra se il tuo browser supporta i popup di autenticazione. Nota: "
+"l'indirizzo\n"
+"0.0.0.0 qui sopra indica l'interfaccia, non la rete o"
+" il netmask. 0.0.0.0\n"
+"significa \"lega a tutte le interfacce\", per cui può essere raggiunto su"
+" 127.0.0.1:7657 e anche da qualunque indirizzo internet di\n"
+"LAN o WAN."
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+"Come impostazione predefinita, l'interfaccia I2CP del router (porta 7654)"
+" si lega all'indirizzo 127.0.0.1. Per legarla a 0.0.0.0, imposta "
+"l'opzione di configurazione avanzata del router su\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true e riavvia."
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "Cos'è un \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+"Un eepsite è un sito web ospitato in maniera anonima: puoi accedervi\n"
+"impostando il tuo proxy HTTP del browser per usare un proxy web (che di "
+"solito è in ascolto\n"
+"su localhost port 4444) e navigando verso il sito."
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+"La configurazione del proxy per browser differenti si trova su una \n"
+"pagina separata con i relativi screenshot. Sono possibili "
+"configurazioni più avanzate con strumenti esterni\n"
+"ma potrebbero introdurre delle falle nella tua impostazione."
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+"x è il numero di peer a cui hai inviato o da cui ha ricevuto un messaggio"
+" con successo\n"
+"nell'ultimo minuto, y è il numero di peer visti nell'ultima\n"
+"ora all'incirca."
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+"Il proxy SOCKS funziona a partire dalla versione 0.7.1. Sono supportati i"
+" SOCKS 4/4a/5.\n"
+"Non c'è alcun outproxy SOCKS per cui il suo uso è limitato."
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+"Inoltre, molte applicazioni rivelano informazioni\n"
+"sensibili che potrebbero farti identificare su Internet. I2P filtra "
+"soltanto\n"
+"i dati di connessione, ma se il programma che pensi di eseguire invia "
+"tali \n"
+"informazioni come contenuti, I2P non ha modo di proteggere il tuo "
+"anonimato. \n"
+"Ad esempio, alcune applicazioni di posta elettronica invieranno al server"
+" di posta elettronica\n"
+"l'indirizzo IP del computer su cui vengono eseguite. Non c'è modo per I2P"
+" di filtrarlo,\n"
+"perciò la 'socksettizzazione' di applicazioni esistenti è possibilethis, "
+"ma\n"
+"pericolosissima."
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+"Se desideri comunque ulteriori informazioni sull'applicazione di proxy "
+"socks,\n"
+"ecco alcuni suggerimenti utili nella pagina di "
+"socks."
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+"Bene, ecco un riepilogo delle porte predefinite (ogni cosa è "
+"configurabileable\n"
+"tramite svariate impostazioni, ovviamente):"
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+"Porte per l'accesso a Internet\n"
+"Nota: le nuove installazioni a partire dalla versione 0.7.8 non usano la "
+"porta 8887, ma selezionano invece una porta casuale\n"
+"compresa tra 9000 e 31000 quando il programma viene eseguito per la prima"
+" volta.\n"
+"Tale porta è mostrata nellla pagina di configurazione"
+" del router."
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+"    "
+msgstr ""
+"UDP in uscita dalla porta casuale indicata nella pagina di configurazione"
+" verso porte UDP remote arbitrarie, per consentire le risposte\n"
+"    "
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+"    "
+msgstr ""
+"TCP in uscita da porte casuali alte verso porte TCP remote "
+"arbitrarie\n"
+"    "
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+"    "
+msgstr ""
+"(facoltativo, ma consigliato) UDP in entrata verso la porta indicata "
+"nella pagina di "
+"configurazione da posizioni arbitrarie\n"
+"    "
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
            \n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+"(facoltativo, ma consigliato) TCP in entrata verso la porta indicata "
+"nella pagina di "
+"configurazione da posizioni arbitrarie\n"
+"
            \n"
+"TCP in entrata potrebbe essere disattivato nella pagina di "
+"configurazione."
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
            \n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+"UDP in uscita sulla porta 123, per consentire le risposte
            \n"
+"Questa è necessaria per la sincronizzazione interna dell'orario in I2P "
+"(tramite SNTP - \n"
+"con query verso un host SNTP casuale sul server pool.ntp.org o u altri di"
+" tua\n"
+"impostazione)"
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+"Porte I2P locali, in ascolto solo delle connessioni locali come "
+"impostazione predefinita,\n"
+"eccetto dove specificato:"
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"1900: ascolto multicast UDP SSDP UPnP.\n"
+"Non può essere cambiata. Si lega a tutte le interfacce.\n"
+"Può essere disattivata su confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+"2827: BOB bridge, un'API socket di livello più alto per i client\n"
+"Disattivata per impostazione predefinita.\n"
+"Può essere attivata/disattivata su configclients.jsp.\n"
+"Può essere modificata nel file the bob.config."
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4444: proxy HTTP\n"
+"Può essere disattivata o modificata nella pagina di i2ptunnel nel "
+"console router.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce."
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4445: proxy HTTPS\n"
+"Può essere disattivata o modificata nella pagina di i2ptunnel nel "
+"console router.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce."
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"6668: proxy IRC\n"
+"Può essere disattivata o modificata nella pagina di i2ptunnel nel "
+"console router.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce."
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7652: ascolto degli eventi TCP HTTP UPnP.\n"
+"Si lega all'indirizzo LAN.\n"
+"Può essere cambiata con la configurazione avanzata "
+"i2np.upnp.HTTPPort=nnnn.\n"
+"Può essere disattivata su confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7653: ascolto risposta ricerca UDP SSDP UPnP.\n"
+"Si lega a tutte le interfacce.\n"
+"Può essere cambiata con la configurazione avanzata "
+"i2np.upnp.SSDPPort=nnnn.\n"
+"Può essere disattivata su confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+"7654: porta di protocollo client I2P, usata dalle applicazione "
+"client.\n"
+"Può essere cambiata con una porta diversa su\n"
+"configclients.jsp"
+"\n"
+"ma non è consigliato.\n"
+"Può essere impostata per legarsi a una interfaccia diversa o a tutte le "
+"interfacce, oppure disattivata su\n"
+"configclients.jsp."
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+"7655: UDP per SAM bridge, un'API socket di più alto livello per i "
+"client\n"
+"Aperta solo quando un client SAM V3 richiede una sessione UDP.\n"
+"Può essere attivata o disattivata su configclients.jsp.\n"
+"Può essere modificata nel file clients.config con l'opzione per riga di "
+"comando SAM sam.udp.port=nnnn."
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+"7656: SAM bridge, un'API socket di livello più alto per i client\n"
+"Disattivata per impostazione predefinita per le nuove installazioni a "
+"partire dalla versione 0.6.5.\n"
+"Può essere attivata/disattivata su configclients.jsp.\n"
+"Può essere modificata nel file the clients.config."
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+"7657: il console router\n"
+"Può essere disattivata o modificata nel file clients.config.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce in quel file."
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+"7657: il console router\n"
+"Può essere disattivata o modificata nel file clients.config.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce in quel file."
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7659: e-mail in uscita verso smtp.postman.i2p\n"
+"Può essere disattivata o modificata nella pagina di i2ptunnel nel "
+"console router.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce."
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7660: e-mail in arrivo da pop.postman.i2p\n"
+"Può essere disattivata o modificata nella pagina di i2ptunnel nel "
+"console router.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce."
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"8998: mtn.i2p2.i2p (Monotone: disattivato come impostazione "
+"predefinita)\n"
+"Può essere disattivata o modificata nella pagina di i2ptunnel nel "
+"console router.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce."
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"31000: connessione locale alla porta del canale di controllo del "
+"wrapper.\n"
+"In uscita solo su 32000, non ascolta su tale porta.\n"
+"Parte a 31000 e incrementa fino a 31999 in cerca di una porta libera.\n"
+"Per modificarla, consulta la\n"
+"documentazione del wrapper .\n"
+"Per ulteriori informazioni, vedi più oltre."
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"32000: canale di controllo locale per il servizio wrapper.\n"
+"Per modificarla, consulta la\n"
+"documentazione del wrapper .\n"
+"Per ulteriori informazioni, vedi più oltre."
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally.  You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+"Non occorre che le porte I2P locali e le porte I2PTunnel siano "
+"raggiungibili \n"
+"da computer remoti, ma *dovrebbero* essere raggiungibili in locale. Puoi "
+"anche creare \n"
+"porte aggiuntive per le istanze I2PTunnel tramite "
+"http://localhost:7657/i2ptunnel/ \n"
+"(e successivamente dovrebbero riuscire a raggiungere il tuo firewall per "
+"consentire l'accesso locale, ma \n"
+"non quello da remoto, a meno di non volerlo)."
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance.  You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+"Quindi, per riassumere, non c'è niente che debba per forza essere "
+"raggiungibile da peer remoti, ma\n"
+"puoi configurare il tuo NAT o firewall per consentire i flussi UDP e TCP "
+"in entrata per la porta verso "
+"l'esterno, otterrai \n"
+"prestazioni migliori. Dovrai anche essere in grado di inviare pacchetti "
+"UDP in uscita\n"
+"verso peer remoti (bloccare indirizzi IP a caso con qualcosa tipo "
+"PeerGuardian\n"
+"ti nuocerà e basta, non farlo)."
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr "Perché I2P rimane in ascolto sulla porta 32000?"
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+"Il wrapper di servizio java Tanuki che usiamo apre questa porta—la "
+"lega a localhost—per poter \n"
+"comunicarecon il software in esecuzione dentro la JVM. Quando la JVM "
+"viene lanciata, le viene assegnata una chiave \n"
+"in modo da potersi collegare al wrapper. Dopo che la JVM stabilisce la "
+"propria connessione \n"
+"al wrapper, quest'ultimo rifiuta qualunque altra eventuale connessione "
+"aggiuntiva."
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the  \n"
+"wrapper documentation."
+msgstr ""
+"Ulteriori informazioni possono essere reperite nella \n"
+"documentazione del wrapper ."
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+"Il seed di un router I2P è sufficiente che avvenga una sola volta per "
+"unirsi alla rete per la prima volta.\n"
+"Il reseed non è altro che l'invio di semplici richieste HTTP GET\n"
+"per ottenere un elenco delle directory e scaricare molteplici file di "
+"\"routerInfo\"\n"
+"da un URL predefinito di reseed."
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+"Un simbolo tipico di un reseed fallito è l'indicatore \"Conosciuti\"\n"
+"(presente nella barra laterale sinistra del console router) indicante un "
+"valore molto piccolo\n"
+"(spesso inferiore a 5) che non aumenta. Ciò può verificarsi, tra le altre"
+" cose,\n"
+"se il tuo firewall limita il traffico in uscita e blocca la richiesta di "
+"reseed."
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr "Per effettuare il reseed di un router IP2 manualmente, segui questi punti:"
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr "Arresta il router I2P"
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+"Apri http://netdb.i2p2.de/ con un "
+"browser web"
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr "Salva una dozzina di file \"routerInfo\" nella cartella I2P \"netDb\""
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr "Avvia il router I2P"
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+"Quando provi ad avviare il router usando \"i2prouter start\", potrebbe "
+"essere visualizzato quanto segue:"
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+"\n"
+"Per essere inclusivo e cercare di assicurare che I2P sia eseguito su "
+"quanti più sistemi possibili, \n"
+"fino alla version I2P 0.8.9 abbiamo usato un wrapper java  \n"
+"compilato per FreeBSD 6.x. Se ricevi questo errore, probabilmente ti "
+"mancano le librerie di compatibilità necessarie.\n"
+"Tali librerie possono essere installate seguendo questi punti:"
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+"Passa all'utente amministratore con su oppure effettua il "
+"login come root."
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+"Se non riesci a installare queste librerie di compatibilità (o non vuoi "
+"farlo), le altre\n"
+"possibilità a tua disposizione potrebbero esser la compilazione del "
+"wrapper per il tuo\n"
+"sistema, l'avvio di I2P con lo script runplain.sh oppure"
+" \n"
+"la sostituzione del wrapper con uno contenuto nel file sorgente compresso"
+" con tar."
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+"Per la versione 0.8.9 di I2P, il wrapper è stato aggiornata alla versione"
+" 3.5.12 e compilato su sistemi FreeBDS 7.2."
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+"Nel wrapper.log osservo un errore relativo alla "
+"famiglia di protocolli non disponibile quando viene caricato"
+" il console router."
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+"Spesso tale errore si verifica con qualunque software java abilitato per "
+"le reti su alcuni sistemi che sono configurati per l'uso di IPv6 come "
+"impostazione predefinita. Esistono alcuni modi per risolvere questo "
+"problema:"
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+"Sui sistemi basati su Linux, è possibile eseguire  echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr "Cerca le seguenti righe nel wrapper.config."
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+"Se tali righe esistono, rimuovi i loro simboli di commento \"#\". Se non "
+"esistono, aggiungile senza i simboli \"#\"."
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+"Un'altra opzione potrebbe essere quella di rimuovere ::1"
+" da ~/.i2p/clients.config"
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+"ATTENZIONE: perché wrapper.config abbia "
+"qualche possibilità di avere effetto, devi interrompere completamento\n"
+"il router e il wrapper. Fare clic su Riavvia nel console\n"
+"router NON eseguirà una rilettura del file! Devi\n"
+"fare clic suArresta, attendere 11 minuti, quindi avviare I2P."
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+"Fantastico! Ci puoi trovare su IRC all'indirizzo irc.freenode.net nel "
+"canale #i2p oppure postare sul\n"
+"forum e noi provvederemo a postare qui "
+"(con\n"
+"la risposta, si spera)."
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "Legislazione tedesca"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr "Rete anonima I2P"
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+"Livello di comunicazione distribuito peer-to-peer anonimo compilato con "
+"strumenti open source e progettato per funzionare con qualunque servizio "
+"Internet come e-mail, IRC o web hosting."
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr "Che cosa fa I2P per te?"
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+"La rete I2P fornisce una forte protezione della privacy per le "
+"comunicazioni su Internet. Molte delle attività che metterebbero in "
+"pericolo la tua privacy su Internet pubblica possono essere condotte in "
+"modo anonimo all'interno di I2P."
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr "Ottieni I2P %(version)s"
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "Cos'è I2P?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+"I2P è una rete di copertura anonima, una rete dentro la rete. Il suo "
+"scopo è di proteggere le comunicazioni dal controllo a tappeto e dal "
+"monitoraggio di terze parti come gli ISP.\n"
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+"I2P è usato da molte persone che ci tengono alla propria privacy: "
+"attivisti, oppressi, giornalisti e gole profonde, e anche persone "
+"normali.\n"
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+"Nessuna rete può essere \"perfettamente anonima\". L'intento continuo di "
+"I2P è di rendere gli attacchi sempre più difficili da lanciare. Il suo "
+"anonimato si rafforzerà all'aumentare delle dimensioni e degli studi "
+"accademici che verranno continuamente condotti.\n"
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+"I2P è disponibile per desktop, sistemi integrati (come il Raspberry Pi) e"
+" i telefonini Android. Dacci una mano con il passaparola!\n"
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr "Leggi tutto…"
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr "Che cosa puoi fare con I2P?"
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+"Email: interfaccia web integrata per "
+"la posta elettronica, plugin per la posta elettronica senza server."
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+"Navigazione web: siti web "
+"anonimi, gateway verso e dallInternet pubblica."
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+"Blog e forum: plugin "
+"per gestire blog e per Syndie."
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+"Host di siti web: web "
+"server anonimo integrato."
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+"Chat in tempo reale: "
+"messaggistica immediata e client IRC."
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+"File sharing: client ED2K e "
+"Gnutella, client BitTorrent integrato."
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+"Deposito file "
+"decentralizzato: plugin per il filesystem distribuito Tahoe-LAFS."
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr ""
+"Altre applicazioni "
+"supportate…"
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr "News & aggiornamenti"
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr "Link e risorse consigliate"
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+"\"Consulta\" anche la pagina con i\n"
+"link alle presentazioni, ai video e ai tutorial "
+"relativi ad I2P."
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr "I2P sul web"
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr "Amici di I2P"
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr "Altri progetti e documentazione"
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "Stampa"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr "Bacheche, siti di notizie, altri"
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr "Materiale molto vecchio"
+
diff --git a/i2p2www/translations/it/LC_MESSAGES/research.po b/i2p2www/translations/it/LC_MESSAGES/research.po
new file mode 100644
index 00000000..63b0e1d1
--- /dev/null
+++ b/i2p2www/translations/it/LC_MESSAGES/research.po
@@ -0,0 +1,173 @@
+# Italian translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# fletcherlynd , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-11-21 23:37+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: Italian "
+"(http://www.transifex.com/projects/p/I2P/language/it/)\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/research/index.html:2
+msgid "Academic Research"
+msgstr "Ricerca accademica"
+
+#: i2p2www/pages/site/research/index.html:4
+msgid ""
+"Academic research and analysis of I2P is an important part of ensuring "
+"that the software and network performs as expected and is safe for users "
+"in hostile environments."
+msgstr ""
+"La ricerca e l'analisi accademica di I2P riveste un ruolo mportante per "
+"assicurarsi che le prestazioni del software e della rete siano quelle "
+"volute e gli utenti siano al riparo da ambienti ostili."
+
+#: i2p2www/pages/site/research/index.html:8
+#, python-format
+msgid ""
+"\n"
+"There is a large research community investigating a wide range of aspects"
+" of\n"
+"anonymity. For a current and comprehensive list of relevant papers, see "
+"the\n"
+"Free Haven Anonymity Bibliography.\n"
+"I2P benefits from much of the research into Tor and onion routing, but "
+"there is\n"
+"little dedicated research interest into the theory behind I2P, and the "
+"choices\n"
+"and tradeoffs that the network makes. This presents a unique opportunity "
+"for\n"
+"original research.\n"
+msgstr ""
+"\n"
+"Esiste una grande comunità di ricerca che indaga una vasta gamma di "
+"aspetti \n"
+"relativi all'anonimato. Per un elenco aggiornato e completo di documenti,"
+"\n"
+"consulta la bibliografia di Free Haven "
+"Anonymity.\n"
+"I2P si avvantaggia di molte delle ricerche relative a Tor e all'onion "
+"routing, \n"
+"ma c'è poco interesse dedicato alla ricerca nel campo della teoria alla "
+"base\n"
+"di I2P e alle scelte e ai compromessi fatti dalla rete. Questo presenta "
+"una\n"
+"opportunità di ricerca originale unica.\n"
+
+#: i2p2www/pages/site/research/index.html:18
+#, python-format
+msgid ""
+"A list of known published papers about I2P is available here."
+msgstr ""
+"Un elenco di documenti pubblicati inerenti a I2P di cui siamo a "
+"conoscenza è disponibile qui."
+
+#: i2p2www/pages/site/research/index.html:22
+msgid "Testing Attacks on I2P"
+msgstr "Collaudo degli attacchi su I2P"
+
+#: i2p2www/pages/site/research/index.html:24
+msgid ""
+"I2P can be run as a separate test network by controlling the locations "
+"that a new router reseeds from so that it only finds other test routers."
+msgstr ""
+"I2P può essere eseguita come una rete di collaudo separata controllando "
+"le posizioni da cui un nuovo router effettua il reseed in modo che trovi "
+"soltanto altri router di collaudo."
+
+#: i2p2www/pages/site/research/index.html:28
+msgid ""
+"The standard mode of operation is to have one JVM per router instance; "
+"hence running multiple copies of I2P on a single machine is inadvisable, "
+"both due to the potential resource drain and the certain port conflicts. "
+"To better facilitate setting up small test networks, I2P has a "
+"multirouter mode which enables multiple distinct routers to be run in the"
+" same JVM."
+msgstr ""
+"La modalità operativa standard è di avere una JVM per ogni istanza di "
+"router; quindi non è consigliabile eseguire copie multiple di I2P su un "
+"solo computer, sia per il potenziale assorbimento di risorse sia per i "
+"conflitti che potrebbero verificarsi su determinate porte. Per facilitare"
+" meglio l'impostazione di piccole reti di collaudo, I2P dispone di una "
+"modalità multirouter che attiva molteplici router separati da eseguire "
+"sulla stessa JVM."
+
+#: i2p2www/pages/site/research/index.html:32
+msgid ""
+"MultiRouter can be started from the i2p base directory by running the "
+"below command."
+msgstr ""
+"Il MultiRouter può essere avviato dalla cartella base di i2p eseguendo il"
+" seguente comando."
+
+#: i2p2www/pages/site/research/index.html:37
+msgid ""
+"Additionally, I2P can be started in a virtual network mode. This mode "
+"disables all transports, allowing the router to be tested in isolation "
+"without network traffic. To enable this mode, add "
+"i2p.vmCommSystem=true to the router.config before starting."
+msgstr ""
+"Inoltre, I2P può essere avviato in modalità di rete virtuale. Tale "
+"modalità disattiva tutti i trasporti, consentendo il collaudo del router "
+"in isolamento senza traffico di rete. Per attivare questa modalità, "
+"aggiungi i2p.vmCommSystem=true a router.config prima di "
+"cominciare."
+
+#: i2p2www/pages/site/research/index.html:41
+msgid "Testing the Live I2P Network"
+msgstr "Collaudo della rete I2P live"
+
+#: i2p2www/pages/site/research/index.html:43
+#, python-format
+msgid ""
+"If you are planning on conducting research on the live I2P network, "
+"please contact us before you commence your "
+"testing. While we do not discourage researchers from responsibly testing "
+"their ideas on the live network, if an attack becomes apparent and we "
+"don't have any line of communication then we will end up taking "
+"countermeasures which could interfere with the test."
+msgstr ""
+"Se stai programmando di condurre una ricerca sulla rete I2P live,  contattaci prima di iniziare il collaudo. "
+"Sebbene non scoraggiamo i ricercatori dal mettere alla prova "
+"responsabilmente le loro idee sulla nostra rete live, se un attacco si "
+"manifesta e non disponiamo di alcuna linea di comunicazione finiremo con "
+"il prendere delle contromisure che potrebbero interferire con il "
+"collaudo."
+
+#: i2p2www/pages/site/research/questions.html:2
+msgid "Open research questions"
+msgstr "Domande di ricerca aperte"
+
+#: i2p2www/pages/site/research/questions.html:4
+msgid "Network database"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:6
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:8
+msgid "Tunnels and Destinations"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:10
+msgid "Unidirectional tunnels"
+msgstr "Tunnel unidirezionali"
+
+#: i2p2www/pages/site/research/questions.html:16
+msgid "Multihoming"
+msgstr ""
+
diff --git a/i2p2www/translations/ja/LC_MESSAGES/priority.po b/i2p2www/translations/ja/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..34cd87fe
--- /dev/null
+++ b/i2p2www/translations/ja/LC_MESSAGES/priority.po
@@ -0,0 +1,2672 @@
+# Japanese translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# plazmism , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-12-18 20:08+0000\n"
+"Last-Translator: plazmism \n"
+"Language-Team: Japanese "
+"(http://www.transifex.com/projects/p/I2P/language/ja/)\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/blog/category.html:2
+msgid "Blog Category"
+msgstr ""
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr ""
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:92
+msgid "Blog"
+msgstr "ブログ"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "I2P ブログ ATOMフィード"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr ""
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "その他のブログ記事hellip;"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr ""
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Debian用 I2P パッケージ"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"選択肢 1: Ubuntu及びその派生 の最新のバージョン "
+"(Debianを使っていなければこれを試してください)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "コマンドライン経由でPPAを追加して、I2Pをインストールする"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "ターミナルを開いて入力:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"このコマンドは /etc/apt/sources.list.d にPPAを追加し、レポジトリが署名された GPG キー を取得します。 GPG "
+"キーはパッケージがビルドされてから改竄されていないか確認します。"
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "入力して、新しいPPAのパッケージマネージャーを通知:"
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+"このコマンドは、システムで有効になっている各レポジトリから、その前のコマンドで追加された I2P PPA "
+"を含む最新のソフトウェアの一覧を取得します。"
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "I2P をインストールする準備が出来ました！"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "PPA に Synaptic の利用 を追加"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr "Synaptic を開く (システム -> 管理 -> Synapticパッケージマネージャ)。"
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr "Synaptic を開いて、 設定 メニューから レポジトリ を選択してください。"
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"その他のソースタブをクリックして、追加をクリックしてください。 ppa:i2p-"
+"maintainers/i2pを APT-line フィールドに貼り付けて、ソースを追加 をクリックしてください。"
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr "クイックフィルタボックスで、i2pを打ち込んで、エンターを押してください。i2pが結果リストで返還された時、i2pを右クリックして、インストールのためマークを選択してください。そうした後に、さらに必要な変更をマークしますか？ポップアップが表示されます。そうなったら、マークをクリックしてから適用をクリックしてください。"
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+"インストールプロセスが完了した後、I2Pを始めるの\n"
+"次のパートに移動して、システムの設定ができます。"
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the  key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+"インストールプロセスが完了した後、I2Pを始めるの次のパートに移動して、システムの設定ができます。"
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "インストール後の作業"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr "これら I2P のパッケージを使用して、以下の3つのやり方で、I2P ルーターを始めることができます。"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+""要求に応じて" i2prouter スクリプトを使用してください。コマンドラインから "
+""i2prouter\n"
+"start" を走らせるだけで構いません。 (注: "
+"sudoを使用したり、rootで起動するのはやめてください！)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""要求に応じて"\"i2prouter-nowrapper\"を走らせて、\n"
+"java "
+"サービスラッパーを無効にしてください(非Linux/非x86システムで必要)。\n"
+"(注: sudoを使用したり、rootで起動するのは\n"
+"やめてください！)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"システムをブートした際に、ログインする前の時点で自動的に起動するサービスとして。サービスは\n"
+"ルートとしてまたはsudoを使用して、\"dpkg-reconfigure i2p\"で有効にできます。"
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"設定ページで、\n"
+"規定の設定である 96KB/s ダウン 40KB/s アップはかなり控えめであるので、\n"
+"帯域幅設定を確認・調整してください。"
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"ブラウザ経由で eepsites  に到達したい場合、簡単なやり方はブラウザのプロキシ設定ページで確認可能です。"
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "ダウンロード"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "I2P をダウンロード"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "依存関係"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "クリーンインストール"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "そのファイルをダウンローして、起動させる"
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "コマンドライン (UIなし) インストール:"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"そのファイルをダウンロードして、ダブルクリック (それで動く場合) または\n"
+"ターミナルで java -jar i2pinstall_%(i2pversion)s.jar を入力して、\n"
+"インストーラーを起動。\n"
+"一部のプラットフォームでは、右クリックして\n"
+""Java で開く"を選択できる場合があります。"
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"上のグラフィカル・インストーラーファイルをダウンロードして\n"
+"コマンドラインから java -jar i2pinstall_%(i2pversion)s.jar -console "
+"を実行してください。"
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Debian 及び Ubuntu 用パッケージが利用可能です。"
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+"    The latest dev build is version %(devbuild)s, and is available from\n"
+"    str4d's eepsite."
+msgstr ""
+"上のファイルは現在のリリースビルドです。\n"
+"    最新の開発ビルドはバージョン %(devbuild)sで、str4dのeepsite\n"
+"    から入手できます。"
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+"      are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+"      the other."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "ソースパッケージ"
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+"    or via Git from git.repo.i2p or Github.\n"
+"    
            \n"
+"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"ファイルはzzzで署名されており、\n"
+"キーはこちらにあります。"
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"I2Pは Launchpad と Google Code "
+"のプロジェクトページからダウンロードすることもできます。"
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"windows でインストーラーを起動した後、「I2P を始める」ボタンをクリックするだけで\n"
+"ルーター・コンソールが現れ\n"
+"さらなる指示が表示されます。"
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"Unixライクなシステムでは、 I2P は I2P 用に選択したディレクトリにある\n"
+"\"i2prouter\" スクリプトを使用するサービスとして起動します。\n"
+"コンソールでそのディレクトリに変更し、 \"sh i2prouter status\" とすることで\n"
+"ルーターの状態が示されるはずです。引数 \"start\" や \"stop\" 、 \"restart\"\n"
+"はサービスをコントロールします。ルーター・コンソール\n"
+"は通常の位置でアクセスできます。\n"
+"OpenSolaris 及びラッパー  (i2psvc) がサポートされていないその他のシステムのユーザーについては、代わりに \"sh "
+"runplain.sh\" でルーターを起動してください。"
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"初めてインストールする際は、 可能であれば、 I2P が使用するインターネッツ接続ポートを念頭に入れて\n"
+"NAT/ファイアーウォールを調整することを忘れないでください。\n"
+"他のポートの中でここで説明されています。\n"
+"正常に入力 TCP にポートを開放できたら、 設定ページでも\n"
+"入力 TCP が有効になります。"
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"また、設定ページにて\n"
+"規定の設定である 96KBps ダウン 40KBps アップはかなり遅いので\n"
+"帯域幅設定を確認・調整してください。"
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "以前のリリースからアップデート:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr "自動手動アップデート双方がこのリリースに利用できます。"
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "自動アップデート"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr "0.7.5以降を起動している場合、ルーターが新リリースを検出するはずです。アップグレードするには、表示時にただルーターコンソールの「アップデートをダウンロード」ボタンをクリックするだけで構いません。"
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"リリース 0.7.6にあるバグのため、最初のI2Pのインストールがそのバージョンで\n"
+"手動でアップグレードしなかったものは\n"
+"「ダウンロードされたバージョンは現在のバージョン以降のものでありません」エラーが出る場合があり、\n"
+"以下の手動アップデート手段を使用するべきです。"
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"0.7.4以前を動作中の場合、\n"
+"ルータが自動的にリリースを受け取るようにさせる\n"
+"設定方法に関する重要な情報について\n"
+"0.7.5のリリースノートをご覧ください。"
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"0.6.1.30以前を動作中の場合、\n"
+"ルータが自動的にリリースを受け取るようにさせる\n"
+"設定方法に関する重要な情報について\n"
+"指示をご覧ください。"
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+"    router console "
+"allowing\n"
+"    you to download and install the new release by just clicking on that\n"
+"    link."
+msgstr ""
+"指示に従って、ルーターを再設定した場合、ルーターコンソールでリンクをご覧になれば、\n"
+"そのリンクをクリックするだけで新リリースをダウンロードし、インストールできるようになるはずです。"
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr "代わりに、以下で示される手動の方法を使用できます。"
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "手動アップデート"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and rename as i2pupdate.zip.\n"
+"    (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+"    resulting i2pupdate.zip to your I2P installation directory).  You do"
+" \n"
+"    NOT need to unzip that file."
+msgstr ""
+"そのファイルを I2P のインストールディレクトリに\n"
+"ダウンロードして、 i2pupdate.zip に名前を変更してください。\n"
+"(代わりに、上記のようにソースを入手して、「ant updater」を起動させてから、 I2P のインストールディレクトリにその結果できた "
+"i2pupdate.zip をコピーすることもできます)。そのファイルを解凍する必要はありません。"
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr "「再起動」をクリック"
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "コーヒーでも飲んで、11分後戻ってきてください"
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"ファイルは zzz で署名されており、\n"
+"キーはこちらにあります。"
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "以前のリリース"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"以前のリリースは Google "
+"Code\n"
+"や Launchpad\n"
+"及び%(echelon)sの I2P ネットワーク内で入手できます。"
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "ミラー選択"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "ファイル:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "すべてのミラー"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+"作者が、この仕事に対して他の組織やチームに支払ってもらってはならない報奨金を\n"
+"主張するには (例: GSoCの学生は有効ではありません)。"
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations.  Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"報奨金の額は、寄付が多ければ増えるかもしれません。\n"
+"これらが重要だと思いませんか？ 寄付を加えてください\n"
+" %(donatename)s の報奨金の額がマークされます！"
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "Not found"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr "あなたが探していたリソースは異なる名前であるか、存在しないか、削除されました。"
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "サーバーエラー"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "500 Server error"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "サーバーになんらかのエラーが発生しました。"
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "ミラー"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "セキュア"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "諸々"
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "リンク"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "奥付(Impressum)"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "Tシャツ！"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "欧州"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "米国"
+
+#: i2p2www/pages/global/footer.html:31 i2p2www/pages/global/nav.html:133
+msgid "Donate"
+msgstr "寄付"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "I2P ロゴ"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "不可視なインターネットプロジェクト"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr "このページは %(lastupdated)s に最終アップデートされ、ルーターバージョン %(accuratefor)s に正確です。"
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "このページは %(lastupdated)s に最終アップデートされました。"
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "このページはルーターバージョン %(accuratefor)s に正確です。"
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr "前へ"
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr "次へ"
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "アバウト"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "I2P入門"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "対照"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "対照要旨"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "その他の匿名ネットワーク"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "ドキュメント"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "ドキュメント 目録"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "どのように動作するのか？"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "やさしい入門"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "技術的入門"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "脅威モデル"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "ガーリックルーティング"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "ネットワークデータベース"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "トンネルルーティング"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "ピア選択"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "暗号法"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "仕様"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "ブロックファイル"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "共通構造"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "設定ファイル"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:56
+msgid "Datagrams"
+msgstr "データグラム"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:88
+msgid "Plugins"
+msgstr "プラグイン"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:55
+msgid "Streaming library"
+msgstr "ストリーミングライブラリ"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "トンネル生成"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "トンネルメッセージ"
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "ソフトウェアアップデート"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:60 i2p2www/pages/global/nav.html:113
+msgid "Applications"
+msgstr "アプリケーション"
+
+#: i2p2www/pages/global/nav.html:62
+msgid "Supported applications"
+msgstr "サポートされるアプリケーション"
+
+#: i2p2www/pages/global/nav.html:63
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Protocols"
+msgstr "プロトコル"
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Protocol stack"
+msgstr "プロトコルスタック"
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Transports"
+msgstr "トランスポート"
+
+#: i2p2www/pages/global/nav.html:75
+msgid "Transport layer overview"
+msgstr "トランスポート層概観"
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Tunnels"
+msgstr "トンネル"
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Tunnel implementation"
+msgstr "トンネル実装"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Unidirectional tunnels"
+msgstr "単方向トンネル"
+
+#: i2p2www/pages/global/nav.html:84
+msgid "Old implementation"
+msgstr "旧実装"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Naming and addressbook"
+msgstr "名前付けとアドレスブック"
+
+#: i2p2www/pages/global/nav.html:91
+msgid "Team"
+msgstr "チーム"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Hall of Fame"
+msgstr "栄誉殿堂"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Academic papers and peer review"
+msgstr "学術論文とピアの精査"
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Presentations, tutorials and articles"
+msgstr "プレゼンテーションとチュートリアル、記事"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Contact us"
+msgstr "お問い合わせ"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Help"
+msgstr "ヘルプ"
+
+#: i2p2www/pages/global/nav.html:101
+msgid "FAQ"
+msgstr "よくある質問"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "How to browse I2P"
+msgstr "I2Pを閲覧するには"
+
+#: i2p2www/pages/global/nav.html:103
+msgid "Glossary"
+msgstr "用語集"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Performance"
+msgstr "パフォーマンス"
+
+#: i2p2www/pages/global/nav.html:105 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "フォーラム"
+
+#: i2p2www/pages/global/nav.html:108
+msgid "Volunteer"
+msgstr "ボランティア"
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Get involved!"
+msgstr "参加しよう！"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Develop"
+msgstr "開発"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Licenses"
+msgstr "ライセンス"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Release signing keys"
+msgstr "署名キーのリリース"
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Signed keys"
+msgstr "署名されるキー"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Developers keys"
+msgstr "開発者のキー"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Bug tracker"
+msgstr "バグトラッカー"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Academic research"
+msgstr "学術研究"
+
+#: i2p2www/pages/global/nav.html:122
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:123
+msgid "Guides"
+msgstr "ガイド"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "New developers"
+msgstr "新しい開発者"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Using an IDE with I2P"
+msgstr "I2PでIDEを使用"
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Developer guidelines and coding style"
+msgstr "開発者ガイドラインとコーディングスタイル"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Monotone"
+msgstr "モノトーン"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "New translators"
+msgstr "新しい翻訳者"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Bounties"
+msgstr "報奨金"
+
+#: i2p2www/pages/global/nav.html:134 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "会合"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Roadmap"
+msgstr "ロードマップ"
+
+#: i2p2www/pages/global/nav.html:136
+msgid "Task list"
+msgstr "タスクリスト"
+
+#: i2p2www/pages/global/nav.html:139
+msgid "Language"
+msgstr "言語"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr "I2P会合 ATOMフィード"
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "過去の I2P 会合の記録"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"議論したいことがあれば、IRC上の #i2p-dev にて開発者が見つかります。\n"
+"開発者からの状況更新も利用できます。"
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr ""
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
            \n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
            \n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:94
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"Free Haven's anonymity bibliography."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "問い合わせ"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like OFTC,\n"
+"  EIN and Freenode.\n"
+"  All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "チャンネルリスト:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "全般的な i2p の議論"
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "主題から外れた話"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "開発話"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "チャンネルのヘルプ"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"I2P の開発に関する議論のほとんどは、 I2P "
+"開発フォーラムで起こっています。ここは IRC チャンネルが機能していない場合、大抵は質問を始めるのに最高の場所です。"
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "メーリングリスト"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+"I2P にはメーリングリストがありますが、現在の小規模な開発チームは IRC "
+"や開発者フォーラムを通じたコミュニケーションを好むために、めったに使われません。これは将来変更される場合があります。"
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "登録"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+"メーリングリストに登録するには、リスト情報ページ(以下にリンク)を開き、フォームを埋めてください。 I2P 内のメールアドレス "
+"(hogehoge@mail.i2p) が使用できます。"
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "登録解除"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr "メーリングリストから登録解除まてゃ登録オプションを編集するには、リスト情報ページ(以下にリンク)を開、登録メールアドレスを入力してください。"
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "リスト"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "アーカイブ"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr "全般的な I2P の議論―別のリストにそぐわないものはすべてここに。"
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr "メーリングリストは好みませんか？それならこれはいかがでしょう。メーリングリストはすべてNTTP経由でも利用できます。"
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr "グループリストマッピング:"
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "サーバー:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "よくある質問 (FAQ)"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "目次"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "全般"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr "高い CPU 使用率のありうる原因は沢山あります。ここにチェックリストがあります。"
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
            \n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface.  However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"with 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+"    "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+"    "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+"    "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
            \n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
            \n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally.  You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance.  You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the  \n"
+"wrapper documentation."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "ドイツ法"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr "I2P 匿名ネットワーク"
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+"匿名 P2P 分散型コミュニケーションレイヤーは、オープンソースのツールで作られ、電子メールや IRC "
+"、ウェブホスティングなどの伝統的なインターネットサービスを動かせるよう設計されました。"
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr "I2P は何に役立つのか"
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+"I2P "
+"ネットワークは、インターネット経由のコミュニケーションに対する強固なプライバシーの保護を提供します。公開インターネット上ではプライバシーを危険に晒してしまう多くの活動は"
+" I2P の内部では匿名に伝達されます。"
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr "I2P %(version)s を入手"
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "I2P とは"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+"I2P "
+"は匿名なオーバーレイネットワーク(ネットワーク内のネットワーク)です。ISPなどのサードパーティーによる地引き網的監視やモニタリングからコミュニケーションを保護するように意図されました。"
+"\n"
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+"I2P "
+"は、活動家や抑圧された人々、ジャーナリスト、内部告発者、さらには普通の人に至るまで、プライバシーを不安に思っている多くの人々に使われています。\n"
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+"「完全に匿名な」ネットワークというものはあるはずがありません。 I2P "
+"の継続的目標は、攻撃をしかけるのをますます困難にすることにあります。その匿名性は、ネットワークの規模が増大し、学術的な精査が進むほど強固になっていきます。"
+"\n"
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+"I2P はデスクトップや、組み込みシステム( Raspberry Pi など)、 Android の携帯で利用できます。I2P "
+"のことをもっと広めてください！\n"
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr "詳細を読む…"
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr "I2P でできること"
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+"Eメール: "
+"統合ウェブメールインターフェース、サーバーレスのEメール用プラグイン"
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+"ウェブホスティング: "
+"匿名のウェブサイト、公開インターネットへの及びからのゲートウェイ"
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+"ブログとフォーラム: ブログ及び Syndie"
+" プラグイン。"
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr "ウェブサイトホスティング: 統合匿名ウェブサーバー。"
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+"リアルタイムチャット: インスタントメッセージと IRC"
+" クライアント。"
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+"ファイル共有: ED2K 及び Gnutella "
+"クライアント、統合 BitTorrent クライアント。"
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+"分散型ファイルストレージ: "
+"Tahoe-LAFS 分散型ファイルシステムプラグイン。"
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr "サポートされているアプリケーションの詳細…"
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr "ニュース & アップデート"
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr ""
+
diff --git a/i2p2www/translations/pl/LC_MESSAGES/priority.po b/i2p2www/translations/pl/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..8cea8b05
--- /dev/null
+++ b/i2p2www/translations/pl/LC_MESSAGES/priority.po
@@ -0,0 +1,2553 @@
+# Polish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Tracerneo , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-11-27 00:30+0000\n"
+"Last-Translator: str4d \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/blog/category.html:2
+msgid "Blog Category"
+msgstr ""
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr ""
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:92
+msgid "Blog"
+msgstr "Blog"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "I2P Blog ATOM Feed"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr ""
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "Więcej postów…"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr ""
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "Autor:"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Paczki I2P Debiana"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Opcja 1: Aktualne wersje Ubuntu i pochodne "
+"(Spróbuj tego jeśli nie używasz Debiana)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Dodawanie PPA z linii komend i instalacja I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Otwórz terminal i wpisz:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr "Instrukcje dla Debiana"
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the  key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Pobierz I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Zależności"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "Czyste instalacje"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Pobierz ten plik i uruchom go."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "Instalacja z linii komend:"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Pobierz ten plik i kliknij dwukrotnie (jeśl działa) lub\n"
+"    wpisz java -jar i2pinstall_%(i2pversion)s.jar w "
+"terminalu, by uruchomić\n"
+"    instalator.\n"
+"    Na niektórych platformach może być dostępna opcja "Open with "
+"Java"\n"
+"    po kliknięciu prawym przyciskiem myszy."
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Pobierz powyższy plik instalatora graficznego i wykonaj\n"
+"    java -jar i2pinstall_%(i2pversion)s.jar -console z linii"
+" komend."
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+"    The latest dev build is version %(devbuild)s, and is available from\n"
+"    str4d's eepsite."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+"      are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+"      the other."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+"    or via Git from git.repo.i2p or Github.\n"
+"    
            \n"
+"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+"    router console "
+"allowing\n"
+"    you to download and install the new release by just clicking on that\n"
+"    link."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and rename as i2pupdate.zip.\n"
+"    (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+"    resulting i2pupdate.zip to your I2P installation directory).  You do"
+" \n"
+"    NOT need to unzip that file."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr ""
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr ""
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr ""
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations.  Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr ""
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr ""
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr ""
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:31 i2p2www/pages/global/nav.html:133
+msgid "Donate"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr ""
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr ""
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr ""
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Wprowadzenie do I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Inne anonimowe sieci"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Dokumentacja"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Indeks dokumentacji"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Jak to działa?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Garlic routing"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Kryptografia"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:56
+msgid "Datagrams"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:88
+msgid "Plugins"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:55
+msgid "Streaming library"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:60 i2p2www/pages/global/nav.html:113
+msgid "Applications"
+msgstr "Aplikacje"
+
+#: i2p2www/pages/global/nav.html:62
+msgid "Supported applications"
+msgstr "Wspierane aplikacje"
+
+#: i2p2www/pages/global/nav.html:63
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Protocols"
+msgstr "Protokoły"
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Protocol stack"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Transports"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:75
+msgid "Transport layer overview"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Tunnels"
+msgstr "Tunele"
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Tunnel implementation"
+msgstr "Implementacje tuneli"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Unidirectional tunnels"
+msgstr "Tunele jednokierunkowe"
+
+#: i2p2www/pages/global/nav.html:84
+msgid "Old implementation"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Naming and addressbook"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:91
+msgid "Team"
+msgstr "Zespół"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Hall of Fame"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Academic papers and peer review"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Presentations, tutorials and articles"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Contact us"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Help"
+msgstr "Pomoc"
+
+#: i2p2www/pages/global/nav.html:101
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "How to browse I2P"
+msgstr "Jak przeglądać I2P"
+
+#: i2p2www/pages/global/nav.html:103
+msgid "Glossary"
+msgstr "Słowniczek pojęć"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Performance"
+msgstr "Wydajność"
+
+#: i2p2www/pages/global/nav.html:105 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Forum"
+
+#: i2p2www/pages/global/nav.html:108
+msgid "Volunteer"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Get involved!"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Develop"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Licenses"
+msgstr "Licencje"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Release signing keys"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Signed keys"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Developers keys"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Bug tracker"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Academic research"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:122
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:123
+msgid "Guides"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:125
+msgid "New developers"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Using an IDE with I2P"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Developer guidelines and coding style"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Monotone"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:129
+msgid "New translators"
+msgstr "Nowi tłumacze"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Bounties"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:134 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Spotkania"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Roadmap"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:136
+msgid "Task list"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:139
+msgid "Language"
+msgstr "Język"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr ""
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "Wg. tematu"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "Wg. daty"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "Wg. autora"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
            \n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
            \n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:94
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"Free Haven's anonymity bibliography."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Kontakt"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like OFTC,\n"
+"  EIN and Freenode.\n"
+"  All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Lista kanałów:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Kanał pomocy"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Listy"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Archiwum"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Serwery:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Najczęściej Zadawane Pytania (FAQ)"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Indeks"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "Na jakich systemach I2P będzie działać?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Jakich portów używa I2P?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "Mam pytanie!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "Dlaczego I2P jest tak wolne?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Jak skonfigurować moją przeglądarkę?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Błędy i ich rozwiązania"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
            \n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface.  However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"with 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "Czym jest \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+"    "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+"    "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+"    "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
            \n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
            \n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally.  You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance.  You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the  \n"
+"wrapper documentation."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "Niemieckie prawo"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "Czym jest I2P?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr "I2P w sieci"
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "Prasa"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr ""
+
diff --git a/i2p2www/translations/pt/LC_MESSAGES/priority.po b/i2p2www/translations/pt/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..af6e7652
--- /dev/null
+++ b/i2p2www/translations/pt/LC_MESSAGES/priority.po
@@ -0,0 +1,3363 @@
+# Portuguese translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Danton Medrado, 2013
+# hxdcmls, 2013
+# blueboy, 2013
+# tuliouel, 2013
+# wicked, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-11-27 00:30+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: Portuguese "
+"(http://www.transifex.com/projects/p/I2P/language/pt/)\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/blog/category.html:2
+msgid "Blog Category"
+msgstr "Categoria de Blog"
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr "Feed ATOM do Blog I2P para a Categoria: %(category)s"
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:92
+msgid "Blog"
+msgstr "Blog"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "Feed ATOM do blog do I2P"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr "Postado %(date)s por %(author)s"
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "Mais postagens do blog…"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr "Postado:"
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "Autor:"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Pacotes I2P para Debian"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr "Ubuntu (Precise 12.04 e mais recente)"
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Opção 1: Versões recentes do Ubuntu e seus "
+"derivados (Tente este se não estiver usando Debian)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr "Opção 2: Debian (incluindo derivados do Debian)"
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+"Instruções para Ubuntu Precise Pangolin (e mais recente) e derivados como"
+" Linux Mint & Trisquel"
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Adicionando o PPA por linha de comando e instalando I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Abra um terminal e digite:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"Este comando vai adicionar o PPA em /etc/apt/sources.list.d e buscar a\n"
+"chave gpg com a qual o repositório foi assinado. A chave GPG assegura\n"
+"que os pacotes não foram violados/alterados após seu empacotamento."
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "Notifique seu gerenciador de pacotes sobre o novo PPA digitando:"
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+"Esse comando vai ler a última lista de software de cada\n"
+"repositório ativado em seu sistema, incluindo o PPA do I2P que\n"
+"foi adicionado com o comando anterior."
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "Agora estás pronto para instalar I2P!"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "Adicionar o PPA usando Synaptic"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+"Abra o Synaptic (Sistema -> Administração -> Gerenciador de Pacotes"
+" Synaptic)."
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+"Assim que o Synaptic abrir, selecione Repositórios no menu "
+"Configurações."
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"Clique na aba Outras fontes e clique em Adicionar. Cole"
+" ppa:i2p-maintainers/i2p no campo APT-line e clique em "
+"Adicionar fonte. Clique no botão Fechar e em "
+"Atualizar."
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+"Na caixa Filtro Rápido, digite i2p e pressione enter. Quando"
+" i2p aparecer na lista, clique com o botão direito em "
+"i2p e selecione Marcar para Instalação. Após isso "
+"você deve ver um popup Marcar mudanças adicionais necessárias? ."
+" Se isso ocorrer, clique Marcar e em Aplicar."
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+"Após completar o processo de instalação, você pode passar para a próxima "
+"parte da inicialização do I2P e da "
+"configuração do I2P em seu sistema."
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr "Instruções para Debian"
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr "Adicione linhas da forna a seguir em %(file)s."
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the  key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+"Após completar o processo de instalação, você pode passar para a próxima "
+"parte de inicialização e configuração "
+"do I2P em seu sistema."
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "Trabalho pós-instalação"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+"Usando estes pacotes do I2P, o roteador I2P pode ser iniciado das "
+"seguintes\n"
+"três formas:"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+""sob demanda" usando o script i2prouter. Basta rodar "
+""i2prouter\n"
+"start" de um prompt de comando. (Atenção: "
+"Não use\n"
+"sudo nem rode como root!)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""Sob demanda" sem o java service wrapper\n"
+"(necessário em sistemas não-Linux/não-x86) rodando \"i2prouter-"
+"nowrapper\".\n"
+"(Atenção: Não\n"
+"use sudo nem rode como root!)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"Como um serviço que automaticamente roda durante o boot, antes mesmo do "
+"login. O serviço pode ser ativado com \"dpkg-reconfigure\n"
+"i2p\" como root ou usando sudo. Este é o modo de operação "
+"recomendado."
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+"Quando estiveres instalando pela primeira vez, lembra-te de ajustar "
+"teu NAT/parede de fogo se puderes. As portas a serem redirecionadas "
+"podem ser encontradas na página de configuração da "
+"rede no painel do roteador. Se precisares de ajuda para entender como"
+" redirecionar portas, talvez portfoward.com pode ser útil."
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"Favor revisar e ajustar as configurações de banda napágina de configuração,\n"
+"tendo em vista que a configuração padrão de 96 KB/s para receber e 40 "
+"KB/s para enviar são bem conservadoras."
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"Se você quer acessar eepsites pelo seu browser, dê uma olhada na opagina "
+"de configuração de proxy do browser "
+"para um fácil manual."
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Baixar"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Baixar I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Dependências"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "Instalações feitas a partir do zero"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr "selecione um link alternativo"
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Baixe o arquivo e rode-o."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Baixe o arquivo e dê duplo clique (se isso funciona) ou\n"
+"digite java -jar i2pinstall_%(i2pversion)s.jar num terminal "
+"para rodar o\n"
+"instalador.\n"
+"Você pode conseguir clicar com botão direito e selecionar\n"
+"    "Abrir com Java"."
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "Instalação pelo prompt de comando:"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Baixe o %(i2pversion)s arquivo instalador gráfico para OSX acima e\n"
+"rode java -jar i2pinstall_%(i2pversion)s.jar -console da "
+"linha de comando."
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Baixe esse arquivo e dê clique-duplo nele (se isso funciona) ou\n"
+"    digite java -jar i2pinstall_%(i2pversion)s.jar num "
+"terminal para rodar\n"
+"    o instalador.\n"
+"    Em algumas plataformas você pode conseguir clicando com botão direito"
+" e selecionando\n"
+"    "Abrir com Java"."
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Baixe o arquivo do instalador gráfico acima e\n"
+"    rode java -jar i2pinstall_%(i2pversion)s.jar -console "
+"pela linha de comando."
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Pacotes para Debian & Ubuntu estão disponíveis."
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+"    The latest dev build is version %(devbuild)s, and is available from\n"
+"    str4d's eepsite."
+msgstr ""
+"O arquivo acima é a versão estável atual.\n"
+"A última versão para desenvolvedores é %(devbuild)s, e está disponível no"
+"\n"
+"eepsite do str4d."
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+"      are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+"      the other."
+msgstr ""
+"O lançamento e versões para desenvolvedores da APK do I2P não são "
+"compatíveis, já que\n"
+"são assinadas pelo zzz e str4d, respectivamente. Desinstale uma antes de "
+"instalar a outra."
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "Pacote originário"
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+"    or via Git from git.repo.i2p or Github.\n"
+"    
            \n"
+"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+"Alternativamente, você pode buscar a fonte no monotone\n"
+"ou via Git em git.repo.i2p ou Github.\n"
+"    
            \n"
+"Rode (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) e em seguida\n"
+"rode ou o instalador gráfico ou a instalação normal, conforme acima."
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Os arquivos são assinados pelo zzz,\n"
+"cuja chave está aqui."
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"O I2P também pode ser baixado da página de nosso projeto no Launchpad e no Google Code."
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"Após rodar o instalador no Windows, basta clicar no botão \"Start I2P\"\n"
+"que trará o console do "
+"roteador,\n"
+"onde há maiores instruções."
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"Em sistemas da família Unix, o I2P pode se iniciar como serviço\n"
+"usando o script \"i2prouter\", localizado no duretório que você "
+"selecionou para o I2P.\n"
+"Indo para esse diretório por um terminal e digitando \"sh i2prouter "
+"status\"\n"
+"exibirá o status do roteador. Os parâmetros \"start\", \"stop\" e "
+"\"restart\"\n"
+"controlam o serviço. O console do roteador\n"
+"pode ser acessado de sua localização usual.\n"
+"Para usuários do OpenSolaris e outros sistemas para os quais o wrapper "
+"(i2psvc) incompatível,\n"
+"dêem partida no roteador com \"sh runplain.sh\"."
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"Ao instalar pela primeira vez, lembre-se de ajustar seu "
+"NAT/firewall\n"
+"Se puder, tendo em mente as portas que o I2P expõe à internet,\n"
+"descritas aqui dentre outras portas.\n"
+"Se você conseguiu abrir sua porta para entrada de TCP, habilite também a "
+"entrada de TCP na\n"
+"página de "
+"configuração."
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"Além disso, reveja e ajuste as configurações de largura de banda "
+"na\n"
+"página de configuração,\n"
+"já que as configurações padrão de 96 KBps para download / 40 KBps para "
+"upload são bem lentas."
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "Informes de lançamentos anteriores:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr ""
+"As atualizações automática e manual estão ambas disponíveis para o "
+"lançamento."
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "Atualizações automáticas"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+"Se você está rodando 0.7.5 ou mais recente, seu servidor deve detectar\n"
+"o novo lançamento. Para atualizar basta clicar no botão 'Baixar "
+"Atualização' no\n"
+"painel do seu roteador\n"
+"quando o botão aparecer."
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"Devido a um defeito no lançamento 0.7.6, aqueles cuja primeira instalação"
+" foram aquela versão\n"
+"e não atualizaram manualmente\n"
+"podem ter um erro \"versão baixada não é maior que a atual versão\",\n"
+"e devem usar o método de atualização manual abaixo."
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Se você está rodando a versão 0.7.4 ou anterior, confira as notas da versão 0.7.5 \n"
+"para informações importantes sobre como configurar seu servidor para "
+"automaticamente\n"
+"receber o lançamento."
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Se você está rodando a versão 0.6.1.30 ou anterior, confira\n"
+"as instruções\n"
+"para informações importantes sobre como configurar seu servidor para "
+"automaticamente\n"
+"receber o lançamento."
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+"    router console "
+"allowing\n"
+"    you to download and install the new release by just clicking on that\n"
+"    link."
+msgstr ""
+"Se você reconfigurou seu servidor seguindo as instruções, você deve ver um link no seu \n"
+"    painel do roteador "
+"permitindo\n"
+"    que você baixe e instale o novo lançamento simplesmente clicando "
+"naquele\n"
+"link."
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr "Alternativamente, você pode usar o método manual explicado abaixo."
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "Atualizações manuais"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and rename as i2pupdate.zip.\n"
+"    (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+"    resulting i2pupdate.zip to your I2P installation directory).  You do"
+" \n"
+"    NOT need to unzip that file."
+msgstr ""
+"Baixe aquele arquivo para o seu\n"
+"    diretório de instalação do I2P e renomeie como i2pupdate.zip.\n"
+"    (alternativamente, você pode pegar o código-fonte da forma acima e "
+"rodar \"ant updater\", então copie o\n"
+"    i2pupdate.zip resultante para seu diretório de instalação do I2P).  "
+"Você NÃO \n"
+"    precisa descompactar esse arquivo."
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+"Clique em \"Reiniciar\""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "Pegue um copo de café e volte em 11 minutos"
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"O arquivo é assinado pelo zzz,\n"
+"cuja chave está aqui."
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "Versões anteriores"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"Versões anteriores estão disponíveis no Google "
+"Code\n"
+"e no Launchpad\n"
+"bem como na rede I2P em %(echelon)s."
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "Seleção do espelho"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "Arquivo:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "Qualquer espelho"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+"Para pedir a recompensa o autor não pode ser pago por outras organizações"
+"\n"
+"ou equipes por este trabalho (ex.: estudantes do GSoC não são válidos)."
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations.  Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"O valor dos prêmios pode ser aumentado por mais doações.  Acreditas que "
+"esses são importantes? Inclua sua doação, "
+"marcando o valor para o prêmio do %(donatename)s!"
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "Não encontrado"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+"Sim... o recurso que você está procurando tem outro nome, não existe ou "
+"foi removido."
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "Erro no servidor"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "500 Erro de servidor"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "Hmm...  o servidor encontrou um tipo de erro."
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "Espelhos"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "Seguro"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "Miscelânea"
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Links"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "Dados de autoria"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "Camisetas!"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "Europa"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "EUA"
+
+#: i2p2www/pages/global/footer.html:31 i2p2www/pages/global/nav.html:133
+msgid "Donate"
+msgstr "Doe"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr "Pular navegação"
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "Logo do I2P"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "O projeto de Internet Invisível"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+"A última atualização desta página foi em %(lastupdated)s e é própria para"
+" a versão de servidor %(accuratefor)s."
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "A última atualização desta página foi em %(lastupdated)s."
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "Esta página está própria para a versão de servidor %(accuratefor)s."
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr "Anterior"
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr "Próximo"
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr "Postado em"
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "Sobre"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Introdução ao I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "Comparações"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "Visão geral de comparações"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Outras redes anônimas"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Documentação"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Índice da documentação"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Como funciona?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "Introdução gentil"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "Introdução técnica"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "Modelo da ameaça"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Roteador de cebola"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "Banco de dados da rede"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "Túnel de roteamento"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "Seleção de pares"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Criptografia"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Especificações"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "Arquivo de bloco"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "Estruturas comuns"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "Arquivos de configuração"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:56
+msgid "Datagrams"
+msgstr "Datagramas"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr "Arquivos GeoIP"
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:88
+msgid "Plugins"
+msgstr "Plugins"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:55
+msgid "Streaming library"
+msgstr "Biblioteca de streaming"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "Criação de túnel"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "Mensagens de túnel"
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "Atualizações de programas"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:60 i2p2www/pages/global/nav.html:113
+msgid "Applications"
+msgstr "Aplicações"
+
+#: i2p2www/pages/global/nav.html:62
+msgid "Supported applications"
+msgstr "Aplicações suportadas"
+
+#: i2p2www/pages/global/nav.html:63
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Protocols"
+msgstr "Protocolos"
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Protocol stack"
+msgstr "Pilha de protocolos"
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Transports"
+msgstr "Transportes"
+
+#: i2p2www/pages/global/nav.html:75
+msgid "Transport layer overview"
+msgstr "Visão geral da camada de transporte"
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Tunnels"
+msgstr "Túneis"
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Tunnel implementation"
+msgstr "Implementação de túnel"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Unidirectional tunnels"
+msgstr "Túneis unidirecionais"
+
+#: i2p2www/pages/global/nav.html:84
+msgid "Old implementation"
+msgstr "Implementação antiga"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Naming and addressbook"
+msgstr "Catálogo de endereços e nomes"
+
+#: i2p2www/pages/global/nav.html:91
+msgid "Team"
+msgstr "Equipe"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Hall of Fame"
+msgstr "Salão da Fama"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Academic papers and peer review"
+msgstr "Trabalhos acadêmicos e revisões/avaliações por especialistas"
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Presentations, tutorials and articles"
+msgstr "Apresentações, tutoriais e artigos"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Contact us"
+msgstr "Contate-nos"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Help"
+msgstr "Ajuda"
+
+#: i2p2www/pages/global/nav.html:101
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "How to browse I2P"
+msgstr "Como navegar I2P"
+
+#: i2p2www/pages/global/nav.html:103
+msgid "Glossary"
+msgstr "Glossário"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Performance"
+msgstr "Atuação"
+
+#: i2p2www/pages/global/nav.html:105 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Foruns"
+
+#: i2p2www/pages/global/nav.html:108
+msgid "Volunteer"
+msgstr "Voluntário"
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Get involved!"
+msgstr "Envolva-se!"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Develop"
+msgstr "Desenvolver"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Licenses"
+msgstr "Licenças"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Release signing keys"
+msgstr "Liberar chaves de assinatura"
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Signed keys"
+msgstr "Chaves assinadas"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Developers keys"
+msgstr "Chaves de desenvolvedores"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Bug tracker"
+msgstr "Administrador de defeitos"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Academic research"
+msgstr "Pesquisa acadêmica"
+
+#: i2p2www/pages/global/nav.html:122
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:123
+msgid "Guides"
+msgstr "Guias"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "New developers"
+msgstr "Novos desenvolvedores"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Using an IDE with I2P"
+msgstr "Usando um IDE com I2P"
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Developer guidelines and coding style"
+msgstr "Diretrizes de desenvolvedor e estilo de codificação"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Monotone"
+msgstr "Monótono"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "New translators"
+msgstr "Novos tradutores"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Bounties"
+msgstr "Generosidades"
+
+#: i2p2www/pages/global/nav.html:134 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Reuniões"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Roadmap"
+msgstr "Roteiro de desenvolvimento"
+
+#: i2p2www/pages/global/nav.html:136
+msgid "Task list"
+msgstr "Lista de tarefas"
+
+#: i2p2www/pages/global/nav.html:139
+msgid "Language"
+msgstr "Linguagem"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr "Feed ATOM dos encontros do I2P"
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "Arquivos dos encontros anteriores do I2P"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr "Encontros estão suspensos até que uma data mais adequada seja escolhida."
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"Se você tem algo a discutir, favor encontrar os desenvolvedores no IRC em"
+" #i2p-dev.\n"
+"Status de atualizações dos desenvolvedores "
+"também estão disponíveis."
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr "Encontro de Desenvolvimento do I2P %(id)s"
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr "Log Completo do IRC"
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "Por tópico"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "Por data"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "Por autor"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
            \n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
            \n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+"Favor enviar verbetes novos ou corrigidos para\n"
+"%(email)s.
            \n"
+"Se possível, formate-os como BibTeX; veja nossa\n"
+"página-fonte BibTeX para exemplos.
            \n"
+"Lembre-se de incluir URLs, se possível:\n"
+"trabalhos offline são menos úteis."
+
+#: i2p2www/pages/papers/list.html:94
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"Free Haven's anonymity bibliography."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Contato"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like OFTC,\n"
+"  EIN and Freenode.\n"
+"  All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+"Nossa rede IRC primária é a rede Irc2P dentro do I2P; um túnel padrão "
+"para esta rede é configurado com instalações novas do roteador.\n"
+"Também estamos presentes em múltiplas redes padrão como OFTC,\n"
+"  EIN and Freenode.\n"
+"Todos os canais relacionados ao I2P em todas essas redes estão ligados "
+"aos principais canais da Irc2P por meio de bots retransmissores."
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Lista de canais:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "Discussão geral do i2p"
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "Offtopic"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "Conversa sobre o desenvolvimento"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Canal de ajuda"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"A maior parte da discussão sobre o desenvolvimento do I2P ocorre no Fórum de desenvolvimento do I2P. Este é "
+"normalmente o melhor lugar para começar com consultas, se o canal IRC dos"
+" desenvolvedores estiver inativo."
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "listas de endereçamento"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+"I2P tem, sim, uma lista de discussão, mas ela raramente é usada porque a "
+"pequena equipe de desenvolvedores prefere se comunicar pelo IRC ou pelo "
+"fórum de desenvolvedores. Isso pode mudar no futuro."
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "Inscrevendo"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+"Para se inscrever-se em uma lista de discussão, acesse a página de "
+"informações da lista (link abaixo) e preencha o formulário. Endereços "
+"I2P-internos (foobar@mail.i2p) podem ser usados."
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "Cancelando inscrição"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+"Para cancelar a inscrição a partir de uma lista de discussão ou editar as"
+" suas opções de inscrição, acesse a página de informações da lista (link "
+"abaixo) e digite o seu endereço de email de inscrição."
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Listas"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Arquivo"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+"Discussão geral I2P - qualquer coisa que não se encaixa em uma lista "
+"diferente vai aqui."
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+"Você não gosta de listas de discussão? Então isto é para você. Todas as "
+"listas de discussão estão disponíveis via NNTP tranquilamente."
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr "Mapa de lista de discussão:"
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Servidores:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Perguntas Mais Frequentes"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Index"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "Geral"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "Quais sistemas I2P serão executados?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr "O que é um \"eepsite\" e como eu configuro meu navegador para usá-los?"
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "Meu roteador tem poucos peers ativos, isso está certo?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr "O que quer dizer os números \"x/y Ativos\" no painel do roteador?"
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+"Meus peers ativos / peers conhecidos / túneis participantes / conexões / "
+"largura de banda variam dramaticamente ao longo do tempo! Tem algo "
+"errado?"
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "Está usando um outproxy seguro?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr "A maioria dos eepsites dentro do I2P estão fora do ar?"
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Quais portas usa o I2P?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "Por que o I2P está aguardando conexões na porta 32000?"
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "Eu acho que encontrei um erro, onde eu posso reportá-lo?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr "O que houve com *.i2p.net? O que houve com jrandom? A I2P está morta?"
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "Eu tenho uma pergunta!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr "Configuração"
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+"Meus roteador está funcionando há vários minutos mas tem zero ou poucas "
+"conexões"
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "Por que o I2P está tão lento?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+"Dei falta de vários hosts em meu catálogo de endereços. Quais são os bons"
+" links de assinatura?"
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "Como eu crio meu próprio eepsite?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "Perguntas sobre Bittorrent / I2PSnark / Plugin I2P para Azureus?"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "Como eu conecto no IRC dentro do I2P?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "Não consigo acessar sites regulares da Internet através do I2P."
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "Não consigo acessar sites https:// ou ftp:// através do I2P."
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr "É possível usar I2P como um proxy SOCKS?"
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Como faço para configurar meu navegador?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+"Como posso acessar o painel web a partir das minhas outras máquinas ou "
+"protegê-lo com senha?"
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr "Como posso usar aplicações a partir das minhas outras máquinas?"
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr "Como realizo propagação manualmente?"
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "Meu roteador está usando muita CPU?!?"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "Equívoco"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr "Como acesso IRC, BitTorrent ou outros serviços na Internet normal?"
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+"Meu roteador é um \"nó de saída\" (proxy de saída) para a internet "
+"regular? Eu não quero que seja."
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+"Eu me oponho a certos tipos de conteúdo. Como posso evitar de distribuir,"
+" armazenar ou acessar esses conteúdos?"
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Erros e Suas Soluções"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+"Estou usando FreeBSD e quando inicio o I2P recebo um erro sobre "
+"libm.so.4!"
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+"Em wrapper.log eu vejo um erro onde diz Protocol "
+"family unavailable quando o I2P está carregando"
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "link"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+"I2P foi testado em Windows, Linus, FreeBSD (veja a nota abaixo), OSX, e OpenSolaris. Há trabalho a ser "
+"feito para trazer o I2P para a plataforma Android."
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr "Aqui estão alguns lugares, escolha um ou mais."
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "Converse com os desenvolvedores no IRC em #i2p-dev"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr "Favor incluir informação relevante dos logs do roteador e do \"wrapper\"."
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+"A assinatura padrão é para http://www.i2p2.i2p/hosts.txt a qual é "
+"raramente atualizada.\n"
+"Se você não tem outra assinatura, você eventualmente terá que usar links "
+"diretos\n"
+"o que é incômodo."
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+"Aqui estão alguns links de assinatura de catálogos de endereços públicos."
+" Você pode querer adicionar um ou dois\n"
+"à sua lista "
+"de assinaturas do susidns.\n"
+"Você não precisa adicionar todas, já que elas sincronizam-se entre si "
+"periodicamente.\n"
+"Os links que usam uma aplicação do tipo cgi-bin empregam várias "
+"estratégias para minimizar\n"
+"o número de endereços duplicados entregues, para que sejam mais "
+"eficientes.\n"
+"Perceba que assinar um serviço de hosts.txt é um ato de \"confiança\", já"
+" que uma\n"
+"assinatura maliciosa pode lhe dar endereços incorretos. Então pense antes"
+" de confiar\n"
+"em qualquer deles.\n"
+"Os operadores destes serviços podem ter várias políticas para listar "
+"hosts.\n"
+"A presença nesta lista não implica apoio ao conteúdo."
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+"Jrandom foi o desenvolvedor líder do I2P e\n"
+"do Syndie por muitos anos.\n"
+"Não sabemos se e quando jrandom vai voltar.\n"
+"Os domínios *.i2p.net foram deixados sem funcionamento após uma queda\n"
+"de energia na empresa de hospedagem."
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+"Veja esta página para ler a mensagem de "
+"despedida do jrandom e informações adicionais\n"
+"sobre a migração de *.i2p.net para este site."
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr "I2P continua em pleno desenvolvimento"
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+"Há muitas causas possíveis de uso acentuado de CPU. Aqui está uma lista "
+"de verificação:"
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+"Tente usar OpenJDK ou Java se estiver disponível para seu sistema. Você "
+"pode verificar \n"
+"qual versão de java você tem instalada digitando java "
+"-version em um \n"
+"prompt de comando. A performance tende a diminuir com outras "
+"implementações de java."
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+"Você está usando um cliente BitTorrent sobre I2P? Experimente reduzir o "
+"número de torrents, os limites de banda,\n"
+"ou tente desativá-lo completamente para ver se ajuda."
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+"Seus limites de largura de banda estão muito altos? É possível que seja "
+"tráfego demais para seu\n"
+"roteador I2P e ele esteja sobrecarregado. Experimente reduzir a "
+"configuração para percentagem de compartilhamento de banda na "
+"página de configuração ."
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+"Certifique-se de que você está rodando a última versão do I2P para "
+"conseguir os melhores benefícios do aumento de performance e correções de"
+" defeitos."
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+"Foi reservada memória suficiente para uso pelo I2P? Veja no gráfico de "
+"memória na página de "
+"gráficos para ver\n"
+"se o uso da memória está \"delimitado\"—a JVM passa a maior parte "
+"do tempo\n"
+"coletando lixo. Aumente a configuração "
+"wrapper.java.maxmemory em wrapper.config."
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+"A carga da CPU está simplesmente mais alta do que você gostaria, ou está "
+"fixa em 100% por muito tempo?\n"
+"Se está presa, isso pode ser um bug. Veja os logs por pistas."
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+"Você pode usar a biblioteca BigInteger, baseada em Java, ao invés da "
+"versão nativa,\n"
+"especialmente se estiver rodando num SO ou hardware novo (OpenSolaris, "
+"mipsel, etc.).\n"
+"Veja a página jbigi para instruções de\n"
+"métodos de diagnóstico, construção e teste."
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+"Se sua biblioteca jbigi nativa funciona bem, quem mais exige da\n"
+"CPU pode ser o roteamento de tráfego para túneis participantes. Isso usa "
+"CPU\n"
+"porque em cada salto uma camada de criptografia é decodificada.\n"
+"Você pode limitar o tráfego participante de duas formas - reduzindo a\n"
+"banda compartilhada em\n"
+"confignet.jsp,\n"
+"ou configurando router.maxParticipatingTunnels=nnn em\n"
+"configadvanced.jsp."
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+"Hmm. I2P é uma rede anônima, então essa é complicada.\n"
+"I2P é projetada para resistir à censura, fornecendo meios para\n"
+"que todos se comuniquem livremente.\n"
+"A melhor forma de manter seu PC livre de tráfego (criptografado) que você"
+" não gosta\n"
+"é não usando I2P.\n"
+"Liberdade de expressão tem seus custos.\n"
+"Mas vamos tratar sua pergunta em três partes:"
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+"Distribuição - Todo o tráfego na I2P é criptografado em múltiplas "
+"camadas. Você não sabe\n"
+"o conteúdo, origem e destino de uma mensagem.\n"
+"Todo o tráfego que você roteia é interno dentro da I2P, você não é um nó de saída (proxy de saída).\n"
+"Sua única alternativa é recusar-se a rotear\n"
+"todo o tráfego, configurando seu compartilhamento de banda ou sua "
+"participação em túneis para 0 (veja acima).\n"
+"Será legal se você não fizer isso, você deve ajudar a rede roteando "
+"tráfego para outros.\n"
+"Mais de 95% usuários roteiam tráfego para outros."
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+"Armazenamento - I2P não pratica armazenamento distribuído de "
+"conteúdo. Você deve estar confundindo com\n"
+"Freenet.\n"
+"Ao rodar I2P, você não armazena o conteúdo de ninguém."
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+"Acesso - Se há alguns eepsites que você não gosta, não vá lá.\n"
+"Ou use um proxy que os bloqueie, como o Privoxy ou algum tipo de "
+"\"controle parental\"."
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+"Não. Isso é normal.\n"
+"Todos os roteadores ajustam-se dinamicamente às mudanças de condições da "
+"rede e suas demandas."
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+"Você pode precisar repropagar seu roteador I2P. Em versões mais recentes "
+"do I2P você pode ir para http://localhost:7657/configreseed"
+" e clicar no botão Salvar Alterações e Repropagar Agora. Se esse"
+" método não funciona—ou você usa uma versão muito velha—você "
+"precisa repropagar manualmente."
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+"A URL para repropagar mudou alguns anos atrás. Se essa é sua primeira "
+"instalação e você instalou\n"
+"uma versão antiga (0.6.1.30 ou anterior), ou\n"
+"você não rodou I2P por muito tempo, você deve mudar a URL e\n"
+"clicar \"Repropagar\" no painel para encontrar outros roteadores.\n"
+"Quando seu roteador estiver rodando,\n"
+"em configadvanced.jsp,"
+"\n"
+"adicione a linha i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (qualquer delas "
+"funciona),\n"
+"então clique \"Aplicar\", depois clique no link \"repropagar\" na "
+"esquerda."
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+"Isso funciona se estiver rodando versão 0.6.1.27 ou mais recente.\n"
+"Se estiver rodando versão 0.6.1.31 ou mais recente, você provavelmente "
+"não precisa fazer isso.\n"
+"Se está rodando versão 0.6.1.26 ou anterior, pode-se tanto seguir\n"
+"as instruções de repropagação manual "
+"abaixo\n"
+"como pode instalar a última versão.\n"
+"Possível método alternativo - adicione\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"ao wrapper.config, desative totalmente o roteador, então ligue de novo, "
+"depois clique em \"repropagar\".\n"
+"Avise-nos se isso funcionar."
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+"...mas você *realmente* deve atualizar "
+"para a última versão."
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+"Se seu roteador tem 10 ou mais peers ativos, tudo está certo. Mudanças "
+"nas versões 0.6.1.31 e 0.6.1.32 melhoraram a\n"
+"eficiência do roteador e de fato reduziram o número de peers ativos.\n"
+"O roteador deve manter conexões com alguns poucos peers em todo o "
+"tempo.\n"
+"A melhor forma de manter-se \"melhor conectado\" à rede é compartilhando mais banda."
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+"Meu roteador é um \"nó de saída\" para a Internet regular? Eu não quero "
+"que seja."
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+"Não. Ao contrário do Tor, "
+"\"portões de saída\" ou \"ligações externas a rede I2P\" não são uma "
+"parte inerente da rede. Apenas voluntários que preparam e rodam "
+"aplicativos em separado irão redirecionar dados para a Internet normal. "
+"Existem poucos, muito poucos desses."
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+"Veja acima. Há muitos poucos \"proxies de saída\" tipo HTTP, eles não são"
+" parte integrante da rede,\n"
+"e eles podem estar desligados.\n"
+"Adicionalmente, os velhos proxies de saída squid.i2p, true.i2p, e "
+"krabs.i2p desapareceram.\n"
+"O único proxy de saída atualmente é false.i2p.\n"
+"Para usar, edite suas configurações "
+"do Túnel I2P para eepProxy\n"
+"e configure sua lista de proxy de saída para 'false.i2p' (apenas).\n"
+"Então pare e reinicie o eepProxy.\n"
+"Se não funcionar, o proxy de saída está desligado. Não é culpa da I2P.\n"
+"Se a razão principal para usar uma rede anônima é acessar sites "
+"anonimamente\n"
+"na Internet regular, você pode experimentar Tor."
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+"Dentro do I2P, não há necessidade de HTTPS, já que o tráfego é "
+"criptografado ponto-a-ponto.\n"
+"FTP não é compatível por razões técnicas."
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+"Não há proxies de saída FTP para a internet—pode nem ser possível "
+"ativar um.\n"
+"Qualquer outro tipo de proxy de saída pode funcionar se for criado com um"
+" túnel padrão. \n"
+"Se você quiser criar um tipo de proxy de saída, pesquise atentamente os "
+"riscos.\n"
+"A comunidade I2P pode ou não se disponibilizar a te ajudar com os "
+"aspectos técnicos, sinta-se à vontade para perguntar."
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+"Conforme já explicado várias vezes acima, qualquer proxy de saída "
+"existente não é parte fundamental da rede.\n"
+"Há vários serviços rodados por indivíduos e eles podem ou não\n"
+"ser operacionais em determinados momentos."
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
            \n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+"Atualização: Graças ao trabalho do h2ik, há um proxy de saída "
+"https disponível para uso via I2P. Iniciando com I2P 0.8.4 o túnel é "
+"configurado desde a instalação.
            \n"
+"Caso do proxy não esteja disponível na sua versão de I2P, você pode "
+"adicionar facilmente fazendo o seguinte:"
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+"Abra o gerenciador "
+"de túnel i2p. Deslize até o fim."
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+"Escolha CONECTAR na lista Novo Túnel de Cliente, clique "
+"Criar"
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+"Na nova página, denomine e descreva seu novo túnel https "
+"como quiser.\n"
+"O Ponto de Acesso é sua porta local para a nova porta 4445 "
+"recomendada para o proxy http.\n"
+"Proxy de saída deve ser o endereço do proxy de saída.i2p "
+"compatível com https. \n"
+"Veja essa publicação de fórum pelo h2ik para o "
+"endereço. \n"
+"Certifique-se de que Cliente compartilhado, Atrasar "
+"conexão, Autoiniciar estejam ativados.\n"
+"Outras opções devem ser deixadas como estão. Clique Salvar. No "
+"gerenciador de túnel, clique no botão Iniciar ao lado do seu novo "
+"túnel."
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+"No firefox, clique em "
+"Ferramentas>Opções>Avançado>Rede>Configuração."
+"\n"
+"Desmarque Use esse proxy para todos os protocolos, ative o "
+"proxy SSL: para localhost:4445."
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "Feito."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+"\n"
+"Esta é uma pergunta que só você pode responder porque a resposta correta "
+"depende do seu comportamento, seu\n"
+"modelo de ameaça, e o quanto você confia "
+"no operador do proxy de saída."
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+"Assim como Tor, I2P não criptografa, magicamente, a Internet.\n"
+"Você é vulnerável à bisbilhotagem dos operadores do proxy de saída.\n"
+"A FAQ"
+" do Tor\n"
+"faz um bom trabalho em explicar isso."
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+"Além disso, você pode estar vulnerável à colusão entre o operador do "
+"proxy de saída\n"
+"e os operadores de outros serviços do I2P, se você usar os mesmos túneis "
+"(\"clientes compartilhados\").\n"
+"Há informação adicional sobre isso em %(zzz)s."
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+"Exceto que haja um proxy de saída para o serviço que você deseja, isso "
+"não pode ser feito.\n"
+"Há apenas três tipos de proxies de saída rodando no momento: HTTP, HTTPS,"
+" e e-mail. Observe que não há um proxy de saída SOCKS.\n"
+"Se esse tipo de serviço é necessário, experimente Tor."
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+"Se você acredita que todo eepsite que já foi criado, sim, a maior parte "
+"deles está desligada.\n"
+"Pessoas e eepsites vêm e vão.\n"
+"Uma boa forma de se iniciar no I2P é verificar uma lista de eepsites que "
+"estão atualmente ativas.\n"
+"%(eepstatus)s registra eepsites ativos."
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+"Clique no link do site \n"
+"no alto do painel do seu roteador para instruções."
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+"Por que os downloads, torrents, navegação e tudo mais está tão lento no "
+"I2P?\n"
+"A criptografia e roteamento dentro da rede I2P adiciona uma quantidade "
+"substancial de sobrepeso e limita a largura de banda.\n"
+"O anonimato não é gratuito."
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+"Adicionalmente, você e todo mundo provavelmente precisam aumentar seus "
+"limites de banda.\n"
+"Duas configurações principais são os limitadores de entrada e de saída de"
+" banda\n"
+"na página de "
+"configuração.\n"
+"Com as configurações padrão de 32KBps você geralmente não consegue mais "
+"que 15KBps de transferência no I2PSnark.\n"
+"Aumentando as configurações (mas respeitando os limites reais da sua "
+"conexão)\n"
+"você aumenta o potencial de transmissão no I2PSnark e todas as outras "
+"aplicações."
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+"Ademais, você tem compartilhamento suficiente de banda configurado para "
+"permitir que túneis participantes\n"
+"roteiem pelo seu roteador? Acredite ou não, permitir tráfego participante"
+"\n"
+"mantém você bem integrado na rede e ajuda suas próprias velocidades de "
+"transferência."
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+"I2P é um trabalho em progresso. Muitas melhorias e consertos estão sendo "
+"implementados, e\n"
+"em geral, rodar a última versão ajudará sua performance.\n"
+"Se você não tem, instale a última "
+"versão."
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+"Veja o⏎\n"
+"I2P Bittorrent FAQ"
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+"\n"
+"Um túnel para o servidor IRC principal dentro do I2P, chamado Irc2P, é "
+"criado quando I2P é instalado (veja\n"
+"a Página de "
+"configuração I2PTunnel),\n"
+"e é automaticamente iniciado quando o roteador I2P inicia. Para conectar,"
+" diga ao seu cliente\n"
+"IRC para conectar em localhost 6668. Usuários de clientes "
+"como XChat podem criar uma\n"
+"nova rede com o servidor localhost/6668 (lembre-se de "
+"assinalar "Ignorar\n"
+"servidor de proxy" se você tem um servidor de proxy configurado)."
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface.  However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+"Por motivo de segurança, o painel administrativo do roteador, por padrão,"
+" apenas aguarda\n"
+"conexões na interface local. Entretanto, com uns ajustes,\n"
+"você pode torná-lo alcançável remotamente:"
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"with 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+"Abra ~/.i2p/clients.config e substitua
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"por 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+"Vá para http://localhost:7657/configui"
+"\n"
+"e adicione nome de usuário e senha para o console, se desejado."
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+"Vá para http://localhost:7657/index.jsp"
+"\n"
+"e clique \"Reiniciar educadamente\", que reinicia a JVM e recarrega as "
+"aplicações do cliente"
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+"Depois que iniciar, você deve conseguir alcançar seu painel remotamente. "
+"Atualize a página do roteador em\n"
+"http://127.0.0.1:7657 e você será solicipado a digitar o usuário e senha "
+"indicados no passo 2\n"
+"acima, se seu navegador for compatível com autenticação pop-up. Observe: "
+"o\n"
+"0.0.0.0 acima indica uma interface, não uma rede ou "
+"máscara de rede. 0.0.0.0\n"
+"significa \"ligar-se a todas as interfaces\", portanto ela é alcançável "
+"em 127.0.0.1:7657, assim como\n"
+"de qualquer IP da LAN/WAN."
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+"Por padrão, a interface I2CP do roteador (porta 7654) se liga ao endereço"
+" 127.0.0.1. Para ligá-la em 0.0.0.0, mude a\n"
+"opção da configuração avançada do roteador como "
+"i2cp.tcp.bindAllInterfaces=true e reinicie."
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "O que é um \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+"Um eepsite é um site hospedado anonimamente - você pode acessá-lo\n"
+"configurando o proxy HTTP do seu navegador para usar o proxy da web "
+"(tipicamente,\n"
+"aguarda conexões em localhost, porta 4444), e navegando para site."
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+"A configuração de proxy para diferentes navegadores está numa \n"
+"página separada com capturas de tela. Configurações mais avançadas "
+"com ferramentas externas\n"
+"são possíveis, mas podem introduzir vazamentos em sua instalação."
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+"x é o nº de peers para/dos quais você enviou/recebeu uma mensagem\n"
+"com sucesso no último minuto, y é o nº de peers vistos na última\n"
+"hora aproximadamente."
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+"O proxy SOCKS está funcionando a partir da versão 0.7.1. Protocolos SOCKS"
+" 4/4a/5 são compatíveis.\n"
+"Não há proxy de saída tipo SOCKS, portanto a funcionalidade é limitada."
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+"Ademais, muitas aplicações vazam informações\n"
+"sensíveis que podem te identificar na Internet. I2P apenas filtra\n"
+"dados de conexão, mas se o programa que você pretende rodar envia essa\n"
+"informação em forma de conteúdo, I2P não tem meios de proteger seu "
+"anonimato. Por\n"
+"exemplo, algumas aplicações de e-mail enviam o endereço IP da máquina\n"
+"onde estão rodando para um servidor de e-mail. Não há meios para o I2P "
+"filtrar\n"
+"isso, portanto usar I2P para \"socksificar\" aplicações existentes é "
+"possível, mas\n"
+"extremamente perigoso."
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+"Se quiser mais informação sobre a aplicação de proxy socks mesmo assim,\n"
+"há algumas dicas úteis na página de socks."
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+"Beleza, aqui está um resumo das portas padrão (tudo é configurável\n"
+"por vários ajustes, claro):"
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+"Portas em contato com a Internet\n"
+"Atenção: Novas instalações a partir da versão 0.7.8 não usam a porta "
+"8887; elas selecionam uma porta aleatória\n"
+"entre 9000 e 31000 quando o programa é rodado pela primeira vez.\n"
+"A porta selecionada é exibida na página de configuração "
+"do roteador."
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+"    "
+msgstr ""
+"Saída de UDP pela porta aleatória mencionada na página de configuração "
+"rumo a indeterminadas portas UDP, permitindo respostas\n"
+"    "
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+"    "
+msgstr ""
+"Saída de TCP por portas altas aleatórias rumo a indeterminadas portas "
+"TCP remotas\n"
+"    "
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+"    "
+msgstr ""
+"(opcional, mas recomendado) Entrada de UDP pela porta mencionada na página de configuração "
+"a partir de indeterminadas localizações\n"
+"    "
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
            \n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+"(opcional, mas recomendado) Entrada de TCP pela porta mencionada na página de configuração "
+"a partir de indeterminadas localizações
            \n"
+"Entrada de TCP pode ser desativada na página de configuração."
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
            \n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+"Saída de UDP pela porta 123, permitindo respostas
            \n"
+"Isso é necessário para sincronização interna do horário do I2P's (via "
+"SNTP - \n"
+"questionando um host aleatório em pool.ntp.org ou outro servidor que você"
+" indicar)"
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+"Portas I2P locais, aguardando apenas conexões locais por padrão,\n"
+"exceto onde indicado:"
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"1900: Escuta multicast de UPnP SSDP UDP.\n"
+"Não pode ser alterada. Liga-se a todas as interfaces.\n"
+"Pode ser desativada em confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+"2827: Ponte BOB, uma API de encaixe de alto nível para clientes\n"
+"Desativada por padrão.\n"
+"Pode ser ativada/desativada em configclients.jsp.\n"
+"Pode ser alterada no arquivo bob.config."
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4444: Proxy HTTP\n"
+"Pode ser desativado ou alterado na página Túnel i2p no painel do "
+"roteador.\n"
+"Também pode ser configurado para se ligar a uma interface específica ou "
+"todas as interfaces."
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4445: Proxy HTTPS\n"
+"Pode ser desativado ou alterado na página Túnel i2p no painel do "
+"roteador.\n"
+"Também pode ser configurado para se ligar a uma interface específica ou a"
+" todas as interfaces."
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"6668: proxy IRC\n"
+"Pode ser desativado ou alterado na página Túnel i2p no painel do "
+"roteador.\n"
+"Também pode ser configurado para se ligar a interfaces específicas ou a "
+"todas as interfaces."
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7652: Escuta de eventos UPnP HTTP TCP.\n"
+"Liga-se ao endereço da LAN.\n"
+"Pode ser alterada com a configuração avançada i2np.upnp.HTTPPort=nnnn.\n"
+"Pode ser desativada em confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7653: Escuta de resposta de pesquisa UPnP SSDP UDP.\n"
+"Liga-se a todas as interfaces.\n"
+"Pode ser alterada na configuração avançada i2np.upnp.SSDPPort=nnnn.\n"
+"Pode ser desativada em confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+"7654: Porta I2P para Protocolo de Cliente, usada por apps "
+"clientes.\n"
+"Pode ser alterada para outra porta em\n"
+"configclients.jsp"
+"\n"
+"mas não é recomendado.\n"
+"Pode ser ligada numa diferente interface, ou em todas, ou desativada, em\n"
+"configclients.jsp."
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+"7655: UDP para a ponte SAM, uma API de encaixe de mais alto nível "
+"para clientes\n"
+"Aberta apenas quando um cliente SAM V3 solicita uma seção UDP.\n"
+"Pode ser ativada/desativada em configclients.jsp.\n"
+"Pode ser alterada no arquivo clients.config com a opção de linha de "
+"comando da SAM sam.udp.port=nnnn."
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+"7656: Ponte SAM, uma API de encaixe de nível mais alto para "
+"clientes\n"
+"Desativada por padrão para novas instalações a partir da versão 0.6.5."
+"\n"
+"Pode ser ativada/desativada em configclients.jsp.\n"
+"Pode ser alterada no arquivo clients.config."
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+"7657: Painel do seu roteador\n"
+"Pode ser desativado no arquivo clients.config.\n"
+"Também pode ser configurado para se ligar numa interface específica ou a "
+"todas as interfaces daquele arquivo."
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+"7658: Seu eepsite\n"
+"Pode ser desativado no arquivo clients.config.\n"
+"Também pode ser configurado para se ligar a uma interface específica ou a"
+" todas as interfaces do arquivo jetty.xml."
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7659: Envio de E-mail para smtp.postman.i2p\n"
+"Pode ser desativada ou alterada na página Túnel i2p no painel do "
+"roteador.\n"
+"Também pode ser configurada para se ligar a uma interface específica ou a"
+" todas elas."
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7660: Recebimento de e-mail por pop.postman.i2p\n"
+"Pode ser desativada ou alterada na página Túnel i2p no painel do "
+"roteador.\n"
+"Também pode ser configurada para se ligar a uma interface específica ou a"
+" todas elas."
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"8998: mtn.i2p2.i2p (Monotone - desativada por padrão)\n"
+"Pode ser desativada ou alterada na página Túnel i2p no painel do "
+"roteador.\n"
+"Também pode ser configurada para se ligar a uma interface específica ou a"
+" todas elas."
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"31000: Conexão local para a porta do canal de controle do "
+"empacotador.\n"
+"Apenas saída para 32000, não escuta nesta porta.\n"
+"Começa em 31000 e aumenta até 31999 a procura de uma porta livre.\n"
+"Para alterar, veja a\n"
+"documentação do empacotador.\n"
+"Para mais informações, veja abaixo."
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"32000: Canal de controle local para o empacotador de serviço.\n"
+"Para alterar, veja a\n"
+"documentação do empacotador.\n"
+"Para mais informação, veja abaixo."
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally.  You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+"As portas locais do I2P e as portas do I2PTunnel não precisam ser "
+"alcançáveis por computadores distantes, mas *devem* ser alcançáveis "
+"localmente. Também é possível criar novas portas para instâncias do "
+"I2PTunnel pelo http://localhost:7657/i2ptunnel/ (Em contrapartida, tua "
+"parede de fogo precisaria permitir o acesso local, mas não acesso remoto,"
+" a menos se desejado)."
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance.  You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+"Então, resumindo, nada precisa ser alcançável por peers remotos não "
+"solicitados, mas\n"
+"se você puder configurar seu NAT/firewall para permitir entrada de UDP e "
+"TCP, a porta exposta à "
+"Internet terá\n"
+"melhor performance. Também será necessário enviar pacotes UDP pela saída\n"
+"para peers remotos indefinidos (bloquear IPs aleatoriamente com algo como"
+" PeerGuardian\n"
+"apenas te prejudicará - não faça isso)."
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr "Por que o I2P está escutando na porta 32000?"
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+"O serviço empacotador Tanuki que usamos abre esta porta—limitada ao"
+" localhost—visando se comunicar com softwares rodando dentro da "
+"JVM. Quando a JVM é lançada, ela recebe uma chave \n"
+"para se conectar ao empacotador. Depois da JVM estabelecer sua conexão \n"
+"com o empacotador, ele recusa quaisquer conexões adicionais."
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the  \n"
+"wrapper documentation."
+msgstr ""
+"Mias informações podem ser encontradas em ⏎\n"
+"documentação da embalagem."
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+"Um roteador I2P só precisa ser propagado uma vez, para entrar na rede "
+"pela primeira vez.\n"
+"Repropagar é nada mais que enviar requisições HTTP GET simples\n"
+"para buscar uma lista de diretórios e baixar vários arquivos "
+"\"routerInfo\"\n"
+"de uma URL predefinida."
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+"Um sintoma típico de repropagação falha é o indicador \"Conhecidos\"\n"
+"(na barra esquerda do painel do roteador) mostrando um um valor muito "
+"baixo\n"
+"(geralmente menor que 5) que não aumenta. Isso pode ocorrer, dentre "
+"outras\n"
+"coisas,\n"
+"se seu firewall limita o tráfego de saída, e bloqueou a solicitação de "
+"repropagação."
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr "Para repropagar um roteador I2P manualmente, faça o seguinte:"
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr "Parar seu roteador I2P"
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+"Abra http://netdb.i2p2.de/ usando "
+"um browser"
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr ""
+"Guarde uma dúzia de arquivos \"routerInfo\" no diretório \"netDb\" do seu"
+" I2P"
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr "Iniciar seu roteador I2P"
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+"Quando tentares iniciar o roteador usando \"i2prouter start\", poderás "
+"ver um resultado como o seguinte:"
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+"\n"
+"Para que o I2P seja inclusivo e visando garantir que ele rodará em "
+"quantos sistemas \n"
+"possíveis, até a versão 0.8.9 nós usamos um empacotador java \n"
+"compilado para FreeBSD 6.x. Se você está recebendo este erro, você "
+"provavelmente não tem as bibliotecas necessárias.\n"
+"Essas bibliotecas podem ser instaladas seguindo os seguintes passos:"
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+"Alterne para usuário root com su ou faça login como "
+"root."
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+"Se não puderes instalar essas bibliotecas de compatibilidade (ou não "
+"quiser), outras possibilidades são compilar o embalador para teu sistema, iniciar I2P com o programa "
+"runplain.sh, ou podes substituir o embalador por outro do "
+"tarball com código-fonte."
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+"Para a versão 0.8.9 do I2P, o empacotador foi atualizado para v3.5.12 e "
+"compilado em sistemas rodando FreeBSD 7.2."
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+"Em wrapper.log vejo um erro que diz \"Protocol family "
+"unavailable\" quando carrego o Painel do Roteador"
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+"Normalmente esse erro ocorrerá em qualquer software que acessa a rede em "
+"alguns sistemas configurados para usar IPv6 por padrão. Há alguns modos "
+"de resolver isso:"
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+"Em sistemas baseados em Linux, podeis usar o seguinte comando: echo"
+" 0 > /proc/sys/net/ipv6/bindv6only"
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr "Procure pelas seguintes linhas no arquivo wrapper.config."
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+"Se essas linhas estiverem lá, remove os \"#\". Se as linhas não estão lá,"
+" adicione-as sem os \"#\"."
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+"Outra opção seria a remoção de ::1 do arquivo "
+"~/.i2p/clients.config"
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+"AVISO: Para quaisquer mudanças no arquivo "
+"wrapper.config fazerem efeito, é necessário parar "
+"completamente o roteador e o embalador. Clicar Reiniciar em teu "
+"painel do roteador NÃO irá reler esse arquivo! É necessário clicar "
+"Desligar, esperar onze minutos, então iniciar o I2P."
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+"Ótimo!  Encontre-nos no IRC pelo irc.freenode.net #i2p ou publique no\n"
+"fórum que nós publicaremos aqui "
+"(possivelmente com a resposta)."
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "Leis alemãs."
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr "I2P Rede Anônima"
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+"Interface para comunicação anónima baseada em mensagens distribuídas "
+"ponto-a-ponto, construída com ferramentas de código aberto, feita para "
+"funcionar com serviços tradicionais da Internet, como e-mail, IRC ou "
+"hospedagem de sites."
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr "O que o I2P faz por você?"
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+"A rede I2P fornece fortes proteções de privacidade para a comunicação "
+"através da Internet. Muitas atividades que arriscam a sua privacidade na "
+"Internet pública pode ser realizada de forma anônima dentro I2P."
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr "Pegue o I2P %(version)s"
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "O que é I2P?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+"A I2P é uma rede overlay anônima - uma rede dentro de outra rede. É "
+"destinada a proteger comunicações da vigilância e monitoramento por "
+"terceiros, tais como provedores de acesso à internet.\n"
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr "Leia mais…"
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr "O que você pode fazer com o I2P?"
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+"E-mail: Interface web para e-mail, "
+"plugin para e-mail sem servidor."
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+"Navegação: Sites anônimos, "
+"acessos (gateways) para e da Internet pública."
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+"Blogging e fórums: "
+"Blogging e plugins Syndie."
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+"Hospedagem de sites: "
+"Servidor web anônimo integrado."
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+"Chat em tempo real: "
+"Mensagens instantâneas e clientes IRC."
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+"Compartilhamento de arquivos: "
+"Clientes ED2K e Gnutella, cliente integrado BitTorrent."
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+"Armazenamento "
+"descentralizado de arquivos: Plugin Tahoe-LAFS para sistema de "
+"arquivos distribuído."
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr "Mais aplicações compatíveis…"
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr "Notícias & Atualizações"
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr "Recursos e Links Recomendados"
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+"Veja também a página com\n"
+"links para apresentações, vídeos, e tutoriais sobre"
+" o I2P."
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr "I2P na web"
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr "Amigos do I2P"
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr "Mais Projetos e Documentação"
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "Imprensa"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr "Conselhos, portal de notícias, outros"
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr "Coisas Muito Antigas"
+
diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/about.po b/i2p2www/translations/pt_BR/LC_MESSAGES/about.po
new file mode 100644
index 00000000..edcaf078
--- /dev/null
+++ b/i2p2www/translations/pt_BR/LC_MESSAGES/about.po
@@ -0,0 +1,2205 @@
+# 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-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-11-25 22:08+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/about/browser-config.html:2
+msgid "Web Browser Configuration"
+msgstr "Configuração do navegador web"
+
+#: 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 "Como configurar o seu navegador"
+
+#: i2p2www/pages/site/about/browser-config.html:17
+#: i2p2www/pages/site/about/browser-config.html:73
+msgid "Outproxy Terms Of Service"
+msgstr "Termos de Serviço do proxy de saída"
+
+#: i2p2www/pages/site/about/browser-config.html:22
+msgid "Internet Explorer 8 or Chrome"
+msgstr "Internet Explorer 8 ou 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 "Opções de Internet do IE"
+
+#: 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 "Especificações de proxy no 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 "Opções de rede no 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 "Especificações de proxy no 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 "Opções de proxy no 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 ""
+
+#: 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 "Glossário"
+
+#: i2p2www/pages/site/about/glossary.html:4
+msgid ""
+"This page lists often-used terminology when discussing I2P and "
+"cryptography."
+msgstr ""
+"Esta página lista os termos mais usados nas discussões sobre a I2P e "
+"criptografia."
+
+#: i2p2www/pages/site/about/hall-of-fame.html:2
+msgid "Hall Of Fame"
+msgstr "Salão da Fama"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:5
+msgid "I2P's Hall of Fame"
+msgstr "Salão da Fama da 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 ""
+
+#: 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 "I2P nos espelhos do Debian"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:19
+msgid "Bitcoin client for I2P"
+msgstr "Cliente Bitcoin para a I2P"
+
+#: 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 "Custos e doações em 2013:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:170
+msgid "2012 donations and costs:"
+msgstr "Custos e doações em 2012:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:298
+msgid "2011 donations and costs:"
+msgstr "Custos e doações em 2011:"
+
+#: 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 "Introdução"
+
+#: i2p2www/pages/site/about/intro.html:4
+msgid "The Invisible Internet Project"
+msgstr "O Projeto Internet Invisível"
+
+#: i2p2www/pages/site/about/intro.html:5
+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 \n"
+"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:17
+msgid "How does it work?"
+msgstr "Como funciona?"
+
+#: i2p2www/pages/site/about/intro.html:19
+#, 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:33
+#, 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:44
+#, python-format
+msgid "More details about how I2P works are available."
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:48
+msgid "What can you do with it?"
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:50
+#, 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:60
+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:76
+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:90
+#, 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 "Exposições sobre a I2P"
+
+#: 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 ""
+"\n"
+"Os linques mais recentes encontram-se relacionados na parte inferior de "
+"cada seção."
+
+#: i2p2www/pages/site/about/media.html:16
+msgid "Presentations"
+msgstr "Exposições"
+
+#: 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 "Tutoriais"
+
+#: 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 "Artigos e Entrevistas"
+
+#: 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 "Time"
+
+#: i2p2www/pages/site/about/team.html:4
+msgid "I2P Project Members"
+msgstr "Membros do Projeto 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 "Gerente do Projeto"
+
+#: 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 "Tesoureiro"
+
+#: 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 "modera o fórum público de usuários"
+
+#: 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 "Reponsável pelas comunicações de lançamento"
+
+#: i2p2www/pages/site/about/team.html:57
+msgid "Builds and signs the releases"
+msgstr "Escreve e assina os comunicados de lançamento"
+
+#: 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 "Especialista em segurança"
+
+#: 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 "Cliente Gnutella I2Phex"
+
+#: 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 "Cliente eMule sobre a I2P"
+
+#: 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 "Desenvolvimento do Susimail"
+
+#: i2p2www/pages/site/about/team.html:172
+msgid "Console"
+msgstr "Painel"
+
+#: i2p2www/pages/site/about/team.html:174
+msgid "Router console HTML/CSS design"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:177
+msgid "SAM"
+msgstr "SAM"
+
+#: i2p2www/pages/site/about/team.html:179
+msgid "SAM maintainer"
+msgstr "Mantenedor do SAM"
+
+#: 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 "Tradutores"
+
+#: 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 "Desenvolvimento do i2pmail"
+
+#: 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 "traduções para o francês"
+
+#: 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 "libSAM"
+
+#: 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 "Agosto de 2010"
+
+#: 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 "Desempenho"
+
+#: 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 "Ganhos de desempenho"
+
+#: 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/blog.po b/i2p2www/translations/pt_BR/LC_MESSAGES/blog.po
new file mode 100644
index 00000000..ff647887
--- /dev/null
+++ b/i2p2www/translations/pt_BR/LC_MESSAGES/blog.po
@@ -0,0 +1,1484 @@
+# 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-12-12 06:16+0000\n"
+"PO-Revision-Date: 2013-12-13 11:43+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/blog/2011/10/11/0.8.9-Release.rst:24
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:25
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:12
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:12
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:17
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:16
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:16
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:26
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:19
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:19
+msgid "Files are available on the `download page`_."
+msgstr "Arquivos disponíveis na `página de downloads`_."
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:28
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:15
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:29
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:16
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:16
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:21
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:20
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:20
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:30
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:23
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:23
+msgid "`download page`"
+msgstr "`página de downloads`"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:30
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:17
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:31
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:18
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:19
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:18
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:22
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:22
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:32
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:25
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:79
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:45
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:13
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:101
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:26
+msgid "RELEASE DETAILS"
+msgstr "DETALHES DO LANÇAMENTO"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:32
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:19
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:33
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:40
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:50
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:24
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:24
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:34
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:103
+msgid "Major Changes"
+msgstr "Maiores modificações"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:44
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:24
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:43
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:55
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:47
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:58
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:43
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:32
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:30
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:39
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:81
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:54
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:112
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:34
+msgid "Bug Fixes"
+msgstr "Correção de falhas"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:54
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:30
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:47
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:69
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:63
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:68
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:54
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:41
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:36
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:51
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:43
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:94
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:63
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:19
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:118
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:52
+msgid "Other"
+msgstr "Outro"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:73
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:36
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:51
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:82
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:75
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:96
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:76
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:52
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:56
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:67
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:56
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:110
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:79
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:30
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:129
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:27
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:76
+msgid "SHA256 Checksums:"
+msgstr "Somas de verificação SHA256:"
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39
+msgid "Major changes"
+msgstr "Maiores alterações"
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47
+msgid "Wrapper Update"
+msgstr "Atualização do Empacotador"
+
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:23
+msgid "Update Info"
+msgstr "Informativo de atualização"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2
+msgid "0.9.2 Release"
+msgstr "Lançamento da versão 0.9.2"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9
+msgid ""
+"0.9.2 includes extensive low-level changes to improve the performance and"
+" efficiency of the router. We have updated our UPnP library, to hopefully"
+" make UPnP work for more people. I2PSnark now has DHT support, but it is "
+"not yet enabled by default, as we plan to do more testing during the "
+"upcoming 0.9.3 development cycle."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12
+msgid ""
+"As usual, there's also lots of bug fixes in this release, so updating is "
+"recommended."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26
+msgid ""
+"SSU: Fix several problems in our UDP transport, to improve efficiency and"
+" reliability for connection setup. Also improve defenses against various "
+"types of bad input."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27
+msgid ""
+"UPnP: Updated our library to fix several issues, should work for more "
+"routers now"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28
+msgid ""
+"Transport: Improve performance in both our TCP and UDP transports, to "
+"benefit high-bandwidth routers"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29
+msgid ""
+"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered "
+"are now much more flexible, which should lessen protocol overhead and "
+"reduce stalls caused by dropped tags."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30
+msgid ""
+"I2PSnark: Add DHT support, not yet enabled by default, will do further "
+"testing and plan to enable by default in 0.9.3."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34
+msgid ""
+"Fix various issues affecting memory usage and performance on high-"
+"bandwidth routers"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35
+msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36
+msgid "Fix i2psnark bug that prevented a completion announcement to the tracker"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37
+msgid "Fix a lock contention problem in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38
+msgid "Fix some OSX installation issues"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39
+msgid "Remove uses of direct byte buffers that may have been leaking"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43
+msgid "Reduce overhead in network messages"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44
+msgid "Add \"universal\" theme support"
+msgstr "Adicionar suporte a tema \"universal\""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45
+msgid "Theme updates"
+msgstr "Atualizações de tema"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46
+msgid "Add a jbigi library for Raspberry Pi"
+msgstr "Adicionar uma biblioteca jbigi para Raspberry Pi"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47
+msgid "New Scala unit test framework"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48
+msgid "Translation updates for Czech, Dutch, German, and Greek"
+msgstr "Traduções atualizadas: tcheco, holandês, alemão e grego"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49
+msgid "Update wrapper to 3.5.15 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:77
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:127
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:74
+msgid "Update GeoIP data (new installs and PPA only)"
+msgstr "Atualizar dados do GeoIP (novas instalações e PPA apenas)"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:2
+msgid "0.9.3 Release"
+msgstr "Lançamento da versão 0.9.3"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9
+msgid ""
+"0.9.3 includes extensive low-level changes to the queueing of messages in"
+" the router.  We implement the CoDel Active Queue Management (AQM) "
+"algorithm.  We also unify the queueing and priority mechanisms in the "
+"transports to aid diagnosis and reduce network latency.  Work continues "
+"on fixing UDP transport bugs and making UDP more resistant to attacks.  "
+"There are more changes to improve the performance of the router and "
+"reduce its memory usage.  Also, we enable i2psnark's DHT support, "
+"introduced last release, by default."
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26
+msgid "Active Queue Management"
+msgstr "Gerenciamento da fila de atividades"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:27
+msgid "Priority queues"
+msgstr "Fila de prioridades"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28
+msgid "I2PSnark DHT: Several bug fixes, enable by default."
+msgstr "DHT I2PSnark: Vários bugs corrigidos, permitido por padrão."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32
+msgid ""
+"Several SSU fixes including memory leak, and better handling of routers "
+"behind firewalls that change UDP ports; additional defenses for malicious"
+" packets."
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33
+msgid "Fix piece selection (rarest-first) bugs in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34
+msgid "Fix bug causing multiple browsers to open at startup"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38
+msgid "Improvements in caching"
+msgstr "Melhorias no caching"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39
+msgid "Several synchronization fixes and lock contention reduction"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40
+msgid "Major reduction in SSU buffers memory use"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41
+msgid ""
+"Fix streaming connection timeout back to 1 minute, was inadvertently "
+"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was"
+" unlimited"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42
+msgid "Improved defenses in i2ptunnel for \"darkloris\""
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:43
+msgid "More validation at torrent creation in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44
+msgid "Several parameter changes in SSU to improve throughput"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45
+msgid ""
+"New event log for major events including restarts; show multiple restart "
+"lines on graphs"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46
+msgid "Remove duplicate messages from logs"
+msgstr "Remover mensagens duplicadas dos registros"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47
+msgid "Don't respond to blocked streaming connections with a reset, just drop"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48
+msgid "Remove all uses of inefficient SimpleTimer"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49
+msgid "More checks for valid IPs and ports entered in console"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50
+msgid "Fix bug that wasted a lot of entropy"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51
+msgid "Translation updates: Italian, Portuguese, Spanish, Swedish"
+msgstr "Atualização de traduções: Italiano, Português, Espanhol e Sueco"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52
+msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2
+msgid "0.9.4 Release"
+msgstr "Lançamento da versão 0.9.4"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9
+msgid ""
+"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, "
+"that was reducing network performance and reliability. It also includes "
+"major changes in the in-network update system, and adds the capability to"
+" update via in-network torrents."
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13
+msgid ""
+"We fixed several bugs in the i2psnark DHT implementation that was "
+"introduced\n"
+"last release. For those of you using console or http proxy passwords,\n"
+"we converted to the more-secure digest method and improved the security "
+"for console forms."
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19
+msgid ""
+"For those of you already running development builds, your router should "
+"automatically\n"
+"update to 0.9.4-0 using the new in-network torrent facility.\n"
+"For those running 0.9.3-0, you will update normally using in-network "
+"HTTP, and\n"
+"we will have more information for you when we release 0.9.5."
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36
+msgid ""
+"Big rework of the update system; Preliminary support for updates via "
+"i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37
+msgid "Add per-destination outbound priorities"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41
+msgid ""
+"Fix major bug that reduced SSU connection limits which reduced tunnel "
+"build success rates"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42
+msgid "Fix bug with external I2CP that prevented some external apps from working"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43
+msgid "Fixed several bugs in i2psnark DHT"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44
+msgid "Fixed bug in i2psnark PEX that inflated peer counts"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45
+msgid "Handle dropped I2CP messages better"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46
+msgid "Reduce overhead of I2CP messages"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47
+msgid "Enforce max size in transport outbound message queues"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48
+msgid "Fixes for Windows eepget.bat (new installs and PPA only)"
+msgstr "Correções para eepget.bat no Windows (novas instalações e PPA apenas)"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49
+msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53
+msgid ""
+"More performance improvements, memory reduction, and object churn "
+"reduction"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54
+msgid "Better detection of network disconnections"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55
+msgid "Further improvements in the SSU transport"
+msgstr "Melhorias adicionais no transporte SSU"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56
+msgid "Add console password form"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57
+msgid ""
+"Convert http proxy and console from basic to digest authentication for "
+"added security"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58
+msgid ""
+"Improved verification of console form submissions, using jsp sessions. "
+"Cookies may now be required on forms, except when the console password is"
+" enabled"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59
+msgid ""
+"Initial work on new interfaces to manage applications started via "
+"clients.config"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60
+msgid "Increase minimum peer port to 1024"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61
+msgid "Increase granularity of bandwidth limiter for smoother transmissions"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62
+msgid ""
+"Translation updates: Chinese, French, German, Italian, Polish, "
+"Portuguese, Swedish, and Ukrainian"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64
+msgid "Update wrapper to 3.5.16 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65
+msgid "New ARMv6 wrapper for Raspberry Pi"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:2
+msgid "0.9.5 Release"
+msgstr "Lançamento da versão 0.9.5"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9
+msgid ""
+"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities"
+" that are being investigated by researchers at UCSB. We continue to work "
+"with them on additional improvements. This is a good opportunity to "
+"remind the community that while our network continues to grow rapidly, it"
+" is still relatively small. There may be multiple weaknesses or bugs that"
+" could compromise your anonymity. Help us grow the network by spreading "
+"the word and contributing where you can."
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13
+#, python-format
+msgid ""
+"In this upgrade cycle, a random 1% of routers, (plus all routers running "
+"a\n"
+"development build) will attempt to update via the experimental in-network"
+" bittorrent\n"
+"with i2psnark. If this doesn't work, it should fall back to standard in-"
+"network HTTP update."
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27
+msgid "Defenses and Bug Fixes"
+msgstr "Defesas e Correções de Falhas"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29
+msgid "Fix router bug causing lockup when using iMule"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30
+msgid "Recognize, handle, reject duplicate tunnel IDs"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31
+msgid "Fix changing of the log file name"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32
+msgid "Prevent hashcode attack in session tags"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33
+msgid "Add build request throttler based on previous hop"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34
+msgid "Limit concurrent next-hop lookups"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35
+msgid "Catch exceptions storing nonces in console"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36
+msgid "Fix saving graph settings in console"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37
+msgid "Fix eepget generation of URLs when not proxied"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38
+msgid ""
+"Encrypt database lookup messages end-to-end when sent through exploratory"
+" tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39
+msgid "Don't use multiple floodfills from the same /16 in a query"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40
+msgid "Randomize delay before verifying floodfill store"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41
+msgid "Increase number of floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:45
+msgid "Improve support for mobile browsers"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46
+msgid "Partial defenses for UCSB attacks"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47
+msgid "Add announce list support to i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48
+msgid "Jetty: upgrade Apache Tomcat to 6.0.36"
+msgstr "Jetty: atualizar Apache Tomcat para 6.0.36"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49
+msgid "Split router info files into multiple subdirectories"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50
+msgid "Add IP to hostname mapping option in SOCKS"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51
+msgid "Improve PRNG seeding"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52
+msgid ""
+"Translation updates: French, German, Hungarian, Italian, Norwegian, "
+"Polish, Portuguese, Russian, Swedish"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54
+msgid "Update wrapper to 3.5.17 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:2
+msgid "0.9.6 Release"
+msgstr "Lançamento da versão 0.9.6"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:7
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9
+msgid ""
+"0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to "
+"Jetty 7.6.10 (2013-03-12). See below for important information on the "
+"Jetty update. The Jetty 7 series is actively maintained and we plan to "
+"stay current with it in future I2P releases."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13
+msgid ""
+"Most users will update via HTTP. Those running development builds will "
+"attempt to update via the\n"
+"experimental in-network bittorrent with i2psnark. We've fixed some bugs "
+"that will enable more users\n"
+"to update via torrent in the 0.9.7 update cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25
+msgid "Important fix for Windows Eepsites, first install 0.9.5 only"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27
+msgid ""
+"If you first installed I2P with version 0.9.5, on Windows only, we "
+"recommend that you follow the\n"
+"following instructions to fix your eepsite location **before** you update"
+" to 0.9.6.\n"
+"Only original installations of 0.9.5-0 on Windows are affected by this "
+"issue. If your router version\n"
+"is 0.9.5-0-win1, you already have the fix and need not take any action."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34
+msgid "See `this page`_ for instructions."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:38
+msgid "`this page`"
+msgstr "`esta página`"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:40
+msgid "Jetty 7 Migration Details"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42
+msgid ""
+"For most people, the update should just work. If you have multiple Jetty "
+"eepsites,\n"
+"OR have made changes to jetty.xml or other Jetty configuration files, "
+"including changing the port\n"
+"from 7658, you MUST take manual action AFTER updating."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48
+msgid ""
+"After update, the router will migrate your jetty.xml files to the new "
+"Jetty 7 format."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50
+msgid ""
+"The migration resets the port to 7658. If you have more than one Jetty "
+"eepsite, OR your eepsite\n"
+"  is NOT on port 7658, OR you have made other modifications to jetty.xml "
+"(for example changing the\n"
+"  listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml "
+"file for each eepsite to fix them up\n"
+"  after updating, and restart again."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55
+msgid ""
+"**The following files will be backed up with a ".jetty6" suffix"
+" and then migrated.**\n"
+"If you have made local changes, you may have to edit them manually and "
+"restart.\n"
+"See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69
+msgid "Plugins"
+msgstr "Extensões"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:71
+msgid "Most plugins should work fine with Jetty 7."
+msgstr "A maioria das extensões deve funcionar bem com Jetty 7."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:75
+msgid ""
+"The I2PControl and zzzot plugins must be updated. Your router should "
+"download and install the new versions shortly after starting 0.9.6."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77
+msgid "If a plugin does not work, please contact the maintainer for that plugin."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83
+msgid "Several bugs with Windows installation (see above)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:84
+msgid "Fix default form action in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85
+msgid "Fix links on iframed console pages"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86
+msgid "Better detection of 64-bit Windows to prevent crashes by systray"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87
+msgid "Fix bug preventing router update via torrent"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88
+msgid "Several SSU fixes for NATs that change UDP ports"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89
+msgid ""
+"Ignore unsupported IPs in RouterInfos when selecting an address (prep for"
+" IPv6)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90
+msgid ""
+"Ignore unused option bits in Database Lookup Message (prep for requesting"
+" encrypted response)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91
+msgid "Fix HTTP proxy error response for malformed URIs"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92
+msgid "Recognize UPnP devices without port forwarding capability"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96
+msgid "Jetty 7.6.10 (see above for migration information)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97
+msgid "Limit page size in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98
+msgid "Add data directory and page size configuration to i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99
+msgid "Support multiple i2psnark instances"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100
+msgid "Piece size adjustments in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101
+msgid "Add more graphing support for combined bandwidth graph"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102
+msgid "Block b32.i2p supercookies"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103
+msgid "Allow stopping clients on /configclients"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104
+msgid "Check for nonce count replays in HTTP client"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105
+msgid "Support SASL authentication in IRC proxy"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106
+msgid "Several cleanups and minor fixes in the update manager"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107
+msgid "Translation updates: German, Portuguese, Russian, Spanish, and Swedish"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:2
+msgid "0.9.7 Release"
+msgstr "Lançamento da versão 0.9.7"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:7
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:9
+msgid "0.9.7 includes significant bug fixes and improvements."
+msgstr "A versão 0.9.7 inclui correções de falhas e melhorias significativas."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:11
+msgid ""
+"For the first time, class 'N' routers (those with a minimumum of 128 "
+"KBytes/sec of shared bandwidth)\n"
+"will automatically become floodfill (previously it was only 'O' routers "
+"with 256 KBps). This will\n"
+"increase the floodfill population for additional resistance to certain "
+"attacks (see below). Floodfill routers\n"
+"don't consume much additional bandwidth, but they do tend to use "
+"additional memory and concurrent\n"
+"connections. If you do not wish your router to become floodfill, set the "
+"advanced configuration\n"
+"router.floodfillParticipant=false ."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:20
+#, python-format
+msgid ""
+"As we think the last release fixed the experimental update-via-torrent "
+"bugs, 3% of routers should\n"
+"update over in-network bittorrent this cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:25
+msgid ""
+"Plugin update checks, possibly broken for several releases, are fixed. "
+"Your plugins should once again\n"
+"auto-update after updating the router."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:30
+msgid ""
+"We fixed a major streaming timer bug that contributed to frequent IRC "
+"disconnects."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:34
+msgid ""
+"This release contains additional mitigations for the `\"practical "
+"attacks\" paper`_.\n"
+"However, we have a lot more work to do to resist Sybil attacks on the "
+"floodfills, and resist\n"
+"traffic analysis at the gateways and endpoints of exploratory tunnels.\n"
+"It's a good reminder for everybody that our network is still relatively "
+"small and vulnerable.\n"
+"We don't currently recommend any uses that would put anybody in serious "
+"jeopardy.\n"
+"We'll keep working to improve it... please keep working to spread the "
+"word. A bigger network is a better network."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:43
+msgid "`\"practical attacks\" paper`"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:47
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:15
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:107
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:28
+msgid "Anonymity Improvements"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:49
+msgid "End-to-end encryption of responses to leaseset lookups"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:50
+msgid "Expand floodfill pool by enabling class 'N' floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:51
+msgid "Randomize padding inside encrypted SSU packets"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:52
+msgid "Preparation for better SSU protocol obfuscation"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:56
+msgid "Fix newer lease sets not getting stored or published"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:57
+msgid ""
+"Fix classpath bug when used with 4-year-old installations, causing the "
+"console not to start"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:58
+msgid "Fix addressbook database bug preventing update of the reverse index"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:59
+msgid ""
+"Fix i2psnark bug that changed the infohash of torrents created by Robert "
+"and fetched via magnet link"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60
+msgid "Fix version checking for plugins"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:61
+msgid ""
+"Fix a streaming timer bug causing frequent IRC disconnects (also affects "
+"other close-on-idle tunnels)"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:65
+msgid "Don't install as a service on Windows by default"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:66
+msgid "Reduce transport idle timeouts"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:67
+msgid "Reduce tunnels on idle in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:68
+msgid "Change default in i2ptunnel GUI to 3 hops"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:69
+msgid "IE 10 support"
+msgstr "Suporte para IE 10"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70
+msgid ""
+"Individual expiration times in leases, for efficiency on destinations "
+"with a high number of tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71
+msgid "Low-level encryption and XOR speedups"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:72
+msgid "Jetty 7.6.11"
+msgstr "Jetty 7.6.11"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:73
+msgid "Tomcat 6.0.37"
+msgstr "Tomcat 6.0.37"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74
+msgid "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75
+msgid "New Turkish translation"
+msgstr "Nova tradução para o turco"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:76
+msgid "Wrapper 3.5.19 (new installs and PPA only)"
+msgstr "Empacotador 3.5.19 (novas instalações e PPA apenas)"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:2
+msgid "0.9.7.1 Release"
+msgstr "Lançamento da versão 0.9.7.1"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:7
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:9
+msgid ""
+"This unscheduled release disables the RouterInfo verification messages "
+"that were used in the attack published in the UCSB paper, which should "
+"make correlating a LeaseSet and a Router much more difficult. We have "
+"also included a limited number of other fixes listed below. Our 0.9.8 "
+"release, which will include IPv6 support, is still on-schedule for late "
+"September."
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:11
+msgid "As usual, we recommend that all users update to this release."
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:17
+msgid "Disable RouterInfo verification messages"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:21
+msgid "Extend inbound tunnel expiration"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:22
+msgid "i2prouter: bashism fix"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:23
+msgid "i2psnark: increase max piece size, mime type updates"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:24
+msgid "New reseed host"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:25
+msgid "New update hosts, thanks Meeh and dg"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:26
+msgid "Streaming: RTO changes"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:27
+msgid "Updater: Increase update-via-torrent to 30 percent"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:28
+msgid "UPnP fix for some hardware"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:2
+msgid "0.9.8 Release"
+msgstr "Lançamento da versão 0.9.8"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9
+msgid ""
+"0.9.8 includes the long-awaited support for IPv6. It's enabled by "
+"default, but of course you need a public IPv6 address to use it. "
+"Configuration is on the 'network' configuration tab in your console. We "
+"also have anonymity improvements including padding of SSU packets and "
+"longer router private keys."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11
+#, python-format
+msgid "30% of you will update via in-network torrent in this update cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13
+msgid "IPv6 Details"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15
+msgid ""
+"IPv6 is enabled and preferred by default. If you have a public IPv6 "
+"address \n"
+"and you are connecting to another router with a published IPv6 address, "
+"it will \n"
+"connect via IPv6. There is a new IPv6 configuration section on /confignet"
+" in \n"
+"the router console. If IPv6 is causing problems you may disable it there."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22
+msgid ""
+"As a part of the IPv6 development effort, I2P now supports multiple \n"
+"published IP addresses. If you have multiple public IP addresses (IPv4, "
+"IPv6, \n"
+"or both), you may enable or disable them individually on /confignet. The"
+" \n"
+"default is to use the first IPv4 and IPv6 addresses it discovers. If you "
+"have \n"
+"multiple addresses you should review the configuration on /confignet and "
+"adjust \n"
+"it if necessary.\n"
+"Note that while you may enable multiple IPv4 and IPv6 addresses on "
+"/confignet,\n"
+"we recommend that you use only one IPv4 and one IPv6 address. There are\n"
+"bugs still to be fixed with multiple addresses of each type."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34
+msgid ""
+"While IPv6 support was designed and developed over several years, it has"
+" \n"
+"only been tested by a limited number of users and is still beta. If you "
+"do have \n"
+"a public IPv6 address, please monitor your router and the logs for "
+"problems, \n"
+"and disable it necessary. Please report any bugs on \n"
+"http://trac.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:42
+msgid "Rekeying Details"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44
+msgid ""
+"For those of you running I2P on faster hardware (generally, 64-bit x86) "
+"the \n"
+"router will generate a new identity using longer keys. This will "
+"substantially \n"
+"reduce your participating traffic for 48 hours or more, while your router"
+" \n"
+"re-integrates into the network. Due to the new keys, the large number of"
+" \n"
+"torrent updates, and the recent network growth, we expect substantial \n"
+"disruption to the network for a week or more after the update is "
+"released. \n"
+"Please be patient and things should start to improve after a few days."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54
+msgid ""
+"These changes may result in higher CPU usage for some of you. We're doing"
+" \n"
+"our best to increase efficiency, but stronger security generally requires"
+" more \n"
+"computation. Performance may also be poor during the first week\n"
+"due to the network churn.\n"
+"We will evaluate the network performace before deciding whether to\n"
+"change the key length on slower hardware in a future release."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63
+msgid ""
+"We are experiencing rapid network growth in the last few weeks, which is"
+" \n"
+"causing a bit of a bumpy ride for some, especially on weekends. However, "
+"the \n"
+"network is still performing fairly well, so keep spreading the word."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69
+msgid "More Changes Coming"
+msgstr "Mais mudanças estão a caminho"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:71
+msgid ""
+"We're in the initial stages of desiging major changes to strengthen our \n"
+"crypto. Stronger crypto will use more CPU and it may possibly \n"
+"require a Java 7 JRE at a minimum. We understand your desire to run I2P "
+"on low-power \n"
+"and/or older hardware. We're working hard to minimize the impacts, but "
+"some \n"
+"loss of performance is inevitable. In addition, Java 5 and 6 are no "
+"longer \n"
+"supported by Oracle. Now is a good time to upgrade to Java 7. Any change "
+"in \n"
+"minimum requirements will be announced well in advance."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:81
+msgid "New Website"
+msgstr "Novo website"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:83
+msgid ""
+"After a heroic effort by str4d, the new website preview is available at \n"
+"http://i2hq.srv.i2p2.de. We hope to see it go live at \n"
+"https://geti2p.net and http://www.i2p2.i2p soon.  Please \n"
+"contribute to the new website translations on Transifex, especially the \n"
+"website_priority resource."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91
+msgid "Community Participation"
+msgstr "Participação da Comunidade"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:93
+msgid ""
+"In early August, hottuna and zzz attended DEFCON 21 in Las Vegas.\n"
+"Last weekend, echelon attended the CTS IV conference in Berlin and\n"
+"psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass.\n"
+"Several of us will be at 30C3 in Hamburg late this year.\n"
+"It's great to see people participating at these events and representing "
+"I2P."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105
+msgid "IPv6 support for both NTCP and SSU"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:109
+msgid "SSU protocol obfuscation by adding random padding"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110
+msgid "Longer encryption and DH private keys for users on faster platforms"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114
+msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:115
+msgid "Fix translation of HTTP proxy error pages"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:116
+msgid "Fix occasional runtime exception in NTCP"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120
+msgid "Big rework of transport code to accommodate multiple addresses and IPv6"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121
+msgid "Streaming: Improved recovery from lost acks, other fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122
+msgid "Use Transifex for translation of initial news and HTTP proxy error pages"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123
+msgid ""
+"Translation updates: Chinese, French, German, Portuguese, Russian, "
+"Swedish, Turkish"
+msgstr ""
+"Atualização de traduções: Chinês, Francês, Alemão, Português, Russo, "
+"Sueco e Turco"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124
+msgid "New Romanian translation"
+msgstr "Nova tradução para o romeno"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:126
+msgid "Wrapper 3.5.20 (new installs and PPA only)"
+msgstr "Empacotador 3.5.20 (novas instalações e PPA apenas)"
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:2
+msgid "0.9.8.1 Release"
+msgstr "Lançamento da versão 0.9.8.1"
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:7
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:9
+msgid ""
+"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some "
+"people. New installs and non-Windows platforms are not affected, however "
+"all platforms will automatically update even if running 0.9.8."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:11
+msgid ""
+"See the `Trac ticket`_ for details and workarounds. See\n"
+"`the 0.9.8 release notes`_ for information on IPv6 and other changes."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:16
+msgid ""
+"Due to recent attacks, logins are disabled on `Trac`_ and new "
+"registrations are\n"
+"disabled on `zzz.i2p`_. Until those services are restored, please report "
+"all\n"
+"bugs on IRC freenode or IRC2P #i2p-dev."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:22
+msgid "`Trac ticket`"
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:23
+msgid "`the 0.9.8 release notes`"
+msgstr "`as notas de lançamento da versão 0.9.8`"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:2
+msgid "0.9.9 Release"
+msgstr "Lançamento da versão 0.9.9"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:7
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:9
+msgid ""
+"0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and "
+"starts work on a year-long plan to increase the strength of the "
+"cryptographic signing algorithms used in the router, and support multiple"
+" algorithms and key lengths simultaneously. Automatic update files will "
+"now be signed with 4096-bit RSA keys."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:11
+msgid ""
+"We now support SSL between your router and your servers for security.\n"
+"See `this development thread`_ for more information."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:16
+msgid "`this development thread`"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:18
+msgid ""
+"As usual, we recommend that you update to this release.\n"
+"The best way to maintain security and help the network is to run the "
+"latest release.\n"
+"Several members of the I2P team will be at 30C3 in Hamburg this year.\n"
+"Come say hello and ask for an I2P sticker.\n"
+"Thanks to everyone for their support this year."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:30
+msgid "Don't build client tunnels through zero-hop exploratory tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:31
+msgid "New \"su3\" file support using stronger keys"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:32
+msgid "Use su3 for updates"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:36
+msgid "Issues with losing data when closing streams"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:37
+msgid "Fix various streaming connection limit issues"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:38
+msgid "Issues with resource usage of closed connections"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:39
+msgid "Clean up timer threads in close-on-idle tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:40
+msgid "Several other streaming fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:41
+msgid "Reject more non-public IPv6 addresses"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:42
+msgid "Fix IPv6 GeoIP"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:43
+msgid "Fix peer selection in first minutes after startup"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:44
+msgid "Several I2PTunnel bug fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:45
+msgid "Fix major i2psnark DHT bug that prevented magnets from working well"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:46
+msgid ""
+"Fix client tunnels that fail due to name resolution failure at startup, "
+"particularly with b32 hostnames"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:47
+msgid "Fix changing client i2ptunnel target list"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:48
+msgid ""
+"Fix major bugs preventing reception of encrypted responses to leaseset "
+"lookups and verifies"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:49
+msgid "Fix bad links on some i2psnark buttons in Opera and text-mode browsers"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:50
+msgid "Fix NPE in Susimail"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:54
+msgid "Start work on supporting stronger signing keys in the router"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:55
+msgid "Reduce thread usage for HTTP Server tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:56
+msgid "Auto-stop update torrent after some time"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:57
+msgid "Add ability to stop webapp via console"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:58
+msgid "New POST throttler in HTTP server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:59
+msgid "Improve connection throttling"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:60
+msgid "More work to reduce number of connections"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:61
+msgid "Re-enable router info expiration job"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:62
+msgid ""
+"Extend router info expiration and other changes to reduce load on "
+"floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:63
+msgid "Support multiple servers through a single server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:64
+msgid "Support specification of server port in i2ptunnel clients"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:65
+msgid "Add support for SSL connections from i2ptunnel to external server"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:66
+msgid "SSL and crypto code refactoring"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:67
+msgid "i2psnark storage code refactoring"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:68
+msgid "New destination cache"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:69
+msgid "Lots of code cleanup and resolution of findbugs warnings"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:70
+msgid "New Japanese translation (partial)"
+msgstr "Nova tradução para o japonês (parcial)"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:71
+msgid ""
+"Translation updates: French, German, Italian, Romanian, Russian, Spanish,"
+" Swedish, and others"
+msgstr ""
+"Atualização de traduções: Francês, Alemão, Italiano, Romeno, Russo, "
+"Espanhol, Sueco e outros idiomas"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:73
+msgid "Wrapper 3.5.22 (new installs and PPA only)"
+msgstr "Empacotador 3.5.22 (novas instalações e PPA apenas)"
+
diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po b/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po
new file mode 100644
index 00000000..696908ee
--- /dev/null
+++ b/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po
@@ -0,0 +1,16809 @@
+# 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-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-12-13 12:10+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/docs/index.html:2 i2p2www/pages/site/docs/index.html:25
+msgid "Index to Technical Documentation"
+msgstr "Índice da Documentação Técnica"
+
+#: i2p2www/pages/site/docs/index.html:3 i2p2www/pages/site/docs/ports.html:3
+#: i2p2www/pages/site/docs/spec/datagrams.html:3
+msgid "May 2013"
+msgstr "Maio de 2013"
+
+#: i2p2www/pages/site/docs/index.html:6
+msgid "How does I2P work"
+msgstr "Como a I2P funciona"
+
+#: i2p2www/pages/site/docs/index.html:8
+msgid "Following is an index to the technical documentation for I2P."
+msgstr "Segue um índice para a documentação técnica da I2P."
+
+#: i2p2www/pages/site/docs/index.html:12
+msgid ""
+"This index is ordered from the highest to lowest layers.\n"
+"The higher layers are for \"clients\" or applications;\n"
+"the lower layers are inside the router itself.\n"
+"The interface between applications and the router is the I2CP (I2P "
+"Control Protocol) API."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:19
+#, python-format
+msgid ""
+"The I2P Project is committed to maintaining accurate, current "
+"documentation.\n"
+"If you find any inaccuracies in the documents linked below, please\n"
+"enter a ticket identifying the problem."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:27 i2p2www/pages/site/docs/naming.html:7
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:12
+#: i2p2www/pages/site/docs/api/streaming.html:6
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:6
+#: i2p2www/pages/site/docs/how/network-database.html:6
+#: i2p2www/pages/site/docs/how/peer-selection.html:6
+#: i2p2www/pages/site/docs/how/tech-intro.html:13
+#: i2p2www/pages/site/docs/how/tech-intro.html:97
+#: i2p2www/pages/site/docs/spec/blockfile.html:7
+#: i2p2www/pages/site/docs/spec/configuration.html:6
+#: i2p2www/pages/site/docs/spec/geoip.html:7
+#: i2p2www/pages/site/docs/spec/updates.html:6
+#: i2p2www/pages/site/docs/tunnels/implementation.html:67
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:6
+msgid "Overview"
+msgstr "Visão geral"
+
+#: i2p2www/pages/site/docs/index.html:29
+msgid "Technical Introduction"
+msgstr "Introdução técnica"
+
+#: i2p2www/pages/site/docs/index.html:30
+msgid "A Less-Technical Introduction"
+msgstr "Uma introdução menos técnica"
+
+#: i2p2www/pages/site/docs/index.html:31
+msgid "Threat model and analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:32
+msgid "Comparisons to other anonymous networks"
+msgstr "Comparações com outras redes anônimas"
+
+#: i2p2www/pages/site/docs/index.html:33
+msgid "Protocol stack chart"
+msgstr "Gráfico da pilha de protocolos"
+
+#: i2p2www/pages/site/docs/index.html:34
+msgid "Papers on I2P"
+msgstr "Publicações sobre a I2P"
+
+#: i2p2www/pages/site/docs/index.html:35
+#, python-format
+msgid ""
+"Invisible Internet Project (I2P) Project Overview"
+" August 28, 2003 (pdf)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:38
+msgid "Application-Layer Topics"
+msgstr "Tópicos sobre a Camada de aplicação"
+
+#: i2p2www/pages/site/docs/index.html:41 i2p2www/pages/site/docs/naming.html:2
+msgid "Naming and Addressbook"
+msgstr "Sistema de nomes e Livro de endereços"
+
+#: i2p2www/pages/site/docs/index.html:42
+msgid "Plugins Overview"
+msgstr "Extensões - Uma visão geral"
+
+#: i2p2www/pages/site/docs/index.html:43
+msgid "Plugin Specification"
+msgstr "Especificações de extensões"
+
+#: i2p2www/pages/site/docs/index.html:44
+msgid "Router software updates"
+msgstr "Atualizações do software do roteador"
+
+#: i2p2www/pages/site/docs/index.html:45
+#: i2p2www/pages/site/docs/applications/bittorrent.html:2
+msgid "Bittorrent over I2P"
+msgstr "Bittorrent sobre a I2P"
+
+#: i2p2www/pages/site/docs/index.html:46
+msgid "I2PControl Plugin API"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:47
+msgid "hostsdb.blockfile Format"
+msgstr "Formato hostsdb.blockfile"
+
+#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:185
+msgid "Configuration File Format"
+msgstr "Formato do arquivo de configuração"
+
+#: i2p2www/pages/site/docs/index.html:51
+msgid "Application Layer API and Protocols"
+msgstr "API da Camada de Aplicação e Protocolos"
+
+#: i2p2www/pages/site/docs/index.html:52
+msgid ""
+"High-level, easy-to-use APIs for applications written in any language to "
+"send and receive data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:54
+msgid "Application Development Overview and Guide"
+msgstr "Guia e Visão Geral do Desenvolvimento de Aplicações"
+
+#: i2p2www/pages/site/docs/index.html:72
+msgid "SAM Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:74
+msgid "SAMv2 Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:76
+msgid "SAMv3 Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:78
+msgid "BOB Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:81
+msgid "End-to-End Transport API and Protocols"
+msgstr "API do transporte ponta-a-ponta e Protocolos"
+
+#: i2p2www/pages/site/docs/index.html:82
+msgid ""
+"The end-to-end protocols used by clients for reliable and unreliable "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:84
+#: i2p2www/pages/site/docs/api/streaming.html:2
+msgid "Streaming Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:86
+msgid "Streaming Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:88
+#: i2p2www/pages/site/docs/api/datagrams.html:2
+msgid "Datagrams"
+msgstr "Datagramas"
+
+#: i2p2www/pages/site/docs/index.html:90
+msgid "Datagram Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:93
+msgid "Client-to-Router Interface API and Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:94
+msgid ""
+"The lowest-level API used for clients (applications) to send and receive "
+"traffic to a router.\n"
+"Traditionally used only by Java applications and higher-level APIs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:99
+msgid "I2CP - I2P Control Protocol / API overview"
+msgstr "I2CP - Protocolo de Controle da I2P / Uma visão geral da API"
+
+#: i2p2www/pages/site/docs/index.html:101
+msgid "I2CP Specification"
+msgstr "Especificação do I2CP"
+
+#: i2p2www/pages/site/docs/index.html:103
+msgid "I2CP API Javadoc"
+msgstr "Javadoc da API do I2CP"
+
+#: i2p2www/pages/site/docs/index.html:105
+#: i2p2www/pages/site/docs/index.html:134
+msgid "Common data structures specification"
+msgstr "Especificação das estruturas de dados comuns"
+
+#: i2p2www/pages/site/docs/index.html:107
+#: i2p2www/pages/site/docs/index.html:136
+msgid "Data Structures Javadoc"
+msgstr "Javadoc das Estruturas de Dados"
+
+#: i2p2www/pages/site/docs/index.html:110
+msgid "End-to-End Encryption"
+msgstr "Criptografia de ponta a ponta"
+
+#: i2p2www/pages/site/docs/index.html:111
+msgid "How client messages are end-to-end encrypted by the router."
+msgstr ""
+"Como as mensagens de cliente são criptografadas de ponta a ponta pelo "
+"roteador"
+
+#: i2p2www/pages/site/docs/index.html:113
+msgid "ElGamal/AES+SessionTag encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:114
+#: i2p2www/pages/site/docs/index.html:147
+msgid "ElGamal and AES cryptography details"
+msgstr "Detalhes sobre as criptografias AES e ElGamal"
+
+#: i2p2www/pages/site/docs/index.html:117
+#: i2p2www/pages/site/docs/how/tech-intro.html:15
+#: i2p2www/pages/site/docs/how/tech-intro.html:329
+msgid "Network Database"
+msgstr "Banco de dados da rede"
+
+#: i2p2www/pages/site/docs/index.html:118
+msgid ""
+"Distributed storage and retrieval of information about routers and "
+"clients."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:120
+msgid "Network database overview, details, and threat analysis"
+msgstr "Uma visão geral do banco de dados da rede, detalhes e análise de risco"
+
+#: i2p2www/pages/site/docs/index.html:121
+msgid "Cryptographic hashes"
+msgstr "Hashes criptográficas"
+
+#: i2p2www/pages/site/docs/index.html:122
+msgid "Cryptographic signatures"
+msgstr "Assinaturas criptográficas"
+
+#: i2p2www/pages/site/docs/index.html:125
+msgid "Router Message Protocol"
+msgstr "Protocolo de mensagens do roteador"
+
+#: i2p2www/pages/site/docs/index.html:126
+msgid ""
+"I2P is a message-oriented router. The messages sent between routers are "
+"defined by the I2NP protocol."
+msgstr ""
+"A I2P é baseada em roteamento orientado-a-mensagens. As mensagens "
+"enviadas entre os roteadores são definidas pelo protocolo I2NP."
+
+#: i2p2www/pages/site/docs/index.html:128
+msgid "I2NP - I2P Network Protocol Overview"
+msgstr "I2NP - Uma visão geral do protocolo de rede I2P"
+
+#: i2p2www/pages/site/docs/index.html:130
+msgid "I2NP Specification"
+msgstr "Especificação do I2NP"
+
+#: i2p2www/pages/site/docs/index.html:132
+msgid "I2NP Javadoc"
+msgstr "Javadoc do I2NP"
+
+#: i2p2www/pages/site/docs/index.html:139
+#: i2p2www/pages/site/docs/how/tech-intro.html:14
+#: i2p2www/pages/site/docs/how/tech-intro.html:228
+msgid "Tunnels"
+msgstr "Túneis"
+
+#: i2p2www/pages/site/docs/index.html:140
+msgid ""
+"Selecting peers, requesting tunnels through those peers, and encrypting "
+"and routing messages through these tunnels."
+msgstr ""
+"Selecionandos nós, pedindo túneis através dos nós, criptografando e "
+"roteando mensagens através desses túneis."
+
+#: i2p2www/pages/site/docs/index.html:142
+msgid "Peer profiling and selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:143
+msgid "Tunnel routing overview"
+msgstr "Uma visão geral do roteamento via túneis"
+
+#: i2p2www/pages/site/docs/index.html:144
+msgid "Garlic routing and \"garlic\" terminology"
+msgstr "Roteamento e terminologia \"garlic\""
+
+#: i2p2www/pages/site/docs/index.html:145
+msgid "Tunnel building and encryption"
+msgstr "Construção de túneis e criptografia"
+
+#: i2p2www/pages/site/docs/index.html:146
+msgid "ElGamal/AES"
+msgstr "ElGamal/AES"
+
+#: i2p2www/pages/site/docs/index.html:146
+msgid "for build request encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:148
+msgid "Tunnel building specification"
+msgstr "Especificação para a construção de túneis"
+
+#: i2p2www/pages/site/docs/index.html:149
+msgid "Low-level tunnel message specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:150
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:2
+msgid "Unidirectional Tunnels"
+msgstr "Túneis unidirecionais"
+
+#: i2p2www/pages/site/docs/index.html:151
+#: i2p2www/pages/site/docs/how/peer-selection.html:299
+msgid "Peer Profiling and Selection in the I2P Anonymous Network"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:152
+msgid "2009 paper (pdf), not current but still generally accurate"
+msgstr "artigo de 2009 (pdf), desatualizado mas, em linhas gerais, ainda correto"
+
+#: i2p2www/pages/site/docs/index.html:155
+msgid "Transport Layer"
+msgstr "Camada de transporte"
+
+#: i2p2www/pages/site/docs/index.html:156
+msgid "The protocols for direct (point-to-point) router to router communication."
+msgstr ""
+"Os protocolos para a comunicação direta (ponto-a-ponto) de roteador para "
+"roteador"
+
+#: i2p2www/pages/site/docs/index.html:158
+msgid "Transport layer overview"
+msgstr "Uma visão geral da camada de transporte"
+
+#: i2p2www/pages/site/docs/index.html:160
+msgid "TCP-based transport overview and specification"
+msgstr "Especificação e visão geral do transporte baseado em TCP"
+
+#: i2p2www/pages/site/docs/index.html:162
+msgid "UDP-based transport overview"
+msgstr "Uma visão geral do transporte baseado em UDP"
+
+#: i2p2www/pages/site/docs/index.html:164
+msgid "SSU specification"
+msgstr "Especificação SSU"
+
+#: i2p2www/pages/site/docs/index.html:166
+msgid "NTCP transport encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:168
+msgid "SSU transport encryption"
+msgstr "Criptografia do transporte SSU"
+
+#: i2p2www/pages/site/docs/index.html:170
+msgid "Transport Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:172
+msgid "NTCP Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:174
+msgid "SSU Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:177
+msgid "Other Router Topics"
+msgstr "Outros tópicos sobre o roteador"
+
+#: i2p2www/pages/site/docs/index.html:179
+msgid "Native BigInteger Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:181
+msgid "Time synchronization and NTP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:183
+msgid "Performance"
+msgstr "Desempenho"
+
+#: i2p2www/pages/site/docs/index.html:190
+msgid "Developer's Guides and Resources"
+msgstr "Guia para Desenvolvedores e Recursos"
+
+#: i2p2www/pages/site/docs/index.html:192
+msgid "New Developer's Guide"
+msgstr "Guia para novos desenvolvedores"
+
+#: i2p2www/pages/site/docs/index.html:194
+msgid "New Translator's Guide"
+msgstr "Guia para os novos tradutores"
+
+#: i2p2www/pages/site/docs/index.html:196
+msgid "Monotone Guide"
+msgstr "Guia do Monotone"
+
+#: i2p2www/pages/site/docs/index.html:198
+msgid "Developer Guidelines"
+msgstr "Diretrizes para os desenvolvedores"
+
+#: i2p2www/pages/site/docs/index.html:200
+msgid "Javadocs on the standard internet:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:201
+#: i2p2www/pages/site/docs/index.html:205
+#: i2p2www/pages/site/docs/index.html:206
+#: i2p2www/pages/site/docs/index.html:207
+#, python-format
+msgid "Server %(num)s"
+msgstr "Servidor %(num)s"
+
+#: i2p2www/pages/site/docs/index.html:202
+#: i2p2www/pages/site/docs/index.html:211
+msgid ""
+"Note: always verify that javadocs are current by checking the release "
+"number."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:204
+msgid "Javadocs inside I2P:"
+msgstr "Javadocs na I2P:"
+
+#: i2p2www/pages/site/docs/index.html:213
+msgid "Ports used by I2P"
+msgstr "Portas usadas pela I2P"
+
+#: i2p2www/pages/site/docs/index.html:215
+msgid "Automatic updates to development builds inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:217
+msgid "Updating the wrapper manually"
+msgstr "Atualizando o empacotador manualmente"
+
+#: i2p2www/pages/site/docs/index.html:219
+msgid "User forum"
+msgstr "Fórum de usuários"
+
+#: i2p2www/pages/site/docs/index.html:221
+msgid "Developer forum inside I2P"
+msgstr "Fórum de desenvolvedores na I2P"
+
+#: i2p2www/pages/site/docs/index.html:223
+msgid "Bug tracker"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:225
+msgid "Viewmtn inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:227
+msgid "I2P Source exported to GitHub"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:229
+msgid "I2P Source Git Repo inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:231
+msgid "Source translation at Transifex"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:233
+msgid "Roadmap wiki"
+msgstr "Wiki do plano de ação"
+
+#: i2p2www/pages/site/docs/index.html:235
+msgid "Old roadmap"
+msgstr "Plano de ação antigo"
+
+#: i2p2www/pages/site/docs/index.html:235
+#: i2p2www/pages/site/docs/index.html:237
+msgid "not current"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:237
+msgid "To Do List"
+msgstr "Lista de tarefas por fazer"
+
+#: i2p2www/pages/site/docs/naming.html:3
+#: i2p2www/pages/site/docs/api/streaming.html:3
+#: i2p2www/pages/site/docs/how/cryptography.html:3
+#: i2p2www/pages/site/docs/protocol/i2cp.html:3
+#: i2p2www/pages/site/docs/spec/common-structures.html:3
+#: i2p2www/pages/site/docs/spec/geoip.html:3
+#: i2p2www/pages/site/docs/spec/streaming.html:3
+#: i2p2www/pages/site/docs/transport/index.html:3
+#: i2p2www/pages/site/docs/transport/ntcp.html:3
+#: i2p2www/pages/site/docs/transport/ssu.html:3
+msgid "December 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:6
+msgid "Naming in I2P"
+msgstr "Sistema de nomes na I2P"
+
+#: i2p2www/pages/site/docs/naming.html:9
+msgid ""
+"I2P ships with a generic naming library and a base implementation \n"
+"designed to work off a local name to destination mapping, as well as an\n"
+"add-on application called the addressbook. \n"
+"I2P also supports Base32 hostnames similar to "
+"Tor's .onion addresses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:16
+msgid ""
+"The addressbook is a web-of-trust\n"
+"driven secure, distributed, and human readable naming system, sacrificing"
+" only\n"
+"the call for all human readable names to be globally unique by mandating "
+"only\n"
+"local uniqueness.  While all messages in I2P are cryptographically "
+"addressed\n"
+"by their destination, different people can have local addressbook entries"
+" for\n"
+"\"Alice\" which refer to different destinations.  People can still "
+"discover new\n"
+"names by importing published addressbooks of peers specified in their web"
+" of trust,\n"
+"by adding in the entries provided through a third party, or (if some "
+"people organize\n"
+"a series of published addressbooks using a first come first serve "
+"registration\n"
+"system) people can choose to treat these addressbooks as name servers, "
+"emulating\n"
+"traditional DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:30
+#, python-format
+msgid ""
+"NOTE: For the reasoning behind the I2P naming system, common arguments "
+"against it\n"
+"and possible alternatives see the naming"
+" discussion\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:37
+msgid "Naming System Components"
+msgstr "Componentes do Sistema de nomes"
+
+#: i2p2www/pages/site/docs/naming.html:39
+msgid ""
+"There is no central naming authority in I2P.\n"
+"All hostnames are local."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:44
+msgid ""
+"The naming system is quite simple and most of it is implemented\n"
+"in applications external to the router, but bundled with\n"
+"the I2P distribution.\n"
+"The components are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:52
+msgid ""
+"The local naming service which does lookups\n"
+"and also handles Base32 hostnames."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:56
+msgid ""
+"The HTTP proxy which asks the router for "
+"lookups and points\n"
+"the user to remote jump services to assist with failed lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:60
+msgid ""
+"HTTP host-add forms which allow users to "
+"add hosts to their local hosts.txt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:63
+msgid ""
+"HTTP jump services which provide their own"
+" lookups and redirection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:66
+msgid ""
+"The addressbook application which merges "
+"external\n"
+"host lists, retrieved via HTTP, with the local list."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:70
+msgid ""
+"The SusiDNS application which is a simple web "
+"front-end\n"
+"for addressbook configuration and viewing of the local host lists."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:77
+msgid "Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:79
+#, python-format
+msgid ""
+"All destinations in I2P are 516-byte (or longer) keys.\n"
+"(To be more precise, it is a 256-byte public key plus a 128-byte signing "
+"key\n"
+"plus a null certificate, which in Base64 representation is 516 bytes.\n"
+"Certificates are not "
+"used now,\n"
+"if they are, the keys will be longer.\n"
+"One possible use of certificates is for proof of work.)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:88
+msgid ""
+"If an application (i2ptunnel or the HTTP proxy) wishes to access\n"
+"a destination by name, the router does a very simple local lookup\n"
+"to resolve that name."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:94
+msgid "Hosts.txt Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:96
+msgid ""
+"The hosts.txt Naming Service does a simple linear search through\n"
+"text files. This naming service was the default until\n"
+"release 0.8.8 when it was replaced by the Blockfile Naming Service.\n"
+"The hosts.txt format had become too slow after the file grew to thousands"
+" of entries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:103
+#, python-format
+msgid ""
+"It does a linear search through three local files, in order, to\n"
+"look up host names and convert them to a 516-byte destination key.\n"
+"Each file is in a simple configuration file"
+" format, with hostname=base64, one per line.\n"
+"The files are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:115
+msgid "Blockfile Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:117
+msgid ""
+"The Blockfile Naming Service stores multiple \"addressbooks\" in a single"
+"\n"
+"database file named hostsdb.blockfile.\n"
+"This Naming Service is the default since release 0.8.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:123
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is specified on the Blockfile page.\n"
+"It provides fast Destination lookup in a compact format. While the "
+"blockfile overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry to implement "
+"advanced addressbook features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:135
+msgid ""
+"On creation, the naming service imports entries from the three files used"
+" by the hosts.txt Naming Service.\n"
+"The blockfile mimics the previous implementation by maintaining three "
+"maps that\n"
+"are searched in-order, named privatehosts.txt, userhosts.txt, and "
+"hosts.txt.\n"
+"It also maintains a reverse-lookup map to implement rapid reverse lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:142
+msgid "Other Naming Service Facilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:144
+#, python-format
+msgid ""
+"The lookup is case-insensitive.\n"
+"The first match is used, and conflicts are not detected.\n"
+"There is no enforcement of naming rules in lookups.\n"
+"Lookups are cached for a few minutes.\n"
+"Base 32 resolution is described below.\n"
+"For a full description of the Naming Service API see the\n"
+"Naming Service Javadocs.\n"
+"This API was significantly expanded in release 0.8.7 to provide\n"
+"adds and removes, storage of arbitrary properties with the hostname,\n"
+"and other features."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:157
+msgid "Alternatives and Experimental Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:159
+#, python-format
+msgid ""
+"The naming service is specified with the configuration property "
+"i2p.naming.impl=class.\n"
+"Other implementations are possible. For example,\n"
+"there is an experimental facility for real-time lookups (a la DNS) over "
+"the network within the router.\n"
+"For more information see the alternatives on the discussion"
+" page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:166
+msgid ""
+"The HTTP proxy does a lookup via the router for all hostnames ending in "
+"'.i2p'.\n"
+"Otherwise, it forwards the request to a configured HTTP outproxy.\n"
+"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-"
+"Top Level Domain '.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:172
+#, python-format
+msgid ""
+"We have applied to reserve the .i2p TLD\n"
+"following the procedures specified in RFC "
+"6761."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:178
+msgid ""
+"If the router fails to resolve the hostname, the HTTP proxy returns\n"
+"an error page to the user with links to several \"jump\" services.\n"
+"See below for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:184
+#: i2p2www/pages/site/docs/spec/configuration.html:77
+msgid "Addressbook"
+msgstr "Livro de endereços"
+
+#: i2p2www/pages/site/docs/naming.html:185
+msgid "Incoming Subscriptions and Merging"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:187
+msgid ""
+"The addressbook application periodically\n"
+"retrieves other users' hosts.txt files and merges\n"
+"them with the local hosts.txt, after several checks.\n"
+"Naming conflicts are resolved on a first-come first-served\n"
+"basis."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:195
+msgid ""
+"Subscribing to another user's hosts.txt file involves\n"
+"giving them a certain amount of trust.\n"
+"You do not want them, for example, 'hijacking' a new site\n"
+"by quickly entering in their own key for a new site before\n"
+"passing the new host/key entry to you."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:203
+msgid ""
+"For this reason, the only subscription configured by\n"
+"default is http://www.i2p2.i2p/hosts.txt,\n"
+"which contains a copy of the hosts.txt included\n"
+"in the I2P release.\n"
+"Users must configure additional subscriptions in their\n"
+"local addressbook application (via subscriptions.txt or SusiDNS)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:212
+msgid "Some other public addressbook subscription links:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:219
+msgid ""
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:224
+#: i2p2www/pages/site/docs/naming.html:236
+msgid "Naming Rules"
+msgstr "Regras de nomenclatura"
+
+#: i2p2www/pages/site/docs/naming.html:225
+msgid ""
+"While there are hopefully not any technical limitations within I2P on "
+"host names,\n"
+"the addressbook enforces several restrictions on host names\n"
+"imported from subscriptions.\n"
+"It does this for basic typographical sanity and compatibility with "
+"browsers,\n"
+"and for security.\n"
+"The rules are essentially the same as those in RFC2396 Section 3.2.2.\n"
+"Any hostnames violating these rules may not be propagated\n"
+"to other routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:240
+msgid "Names are converted to lower case on import."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:244
+msgid ""
+"Names are checked for conflict with existing names in the existing "
+"userhosts.txt and hosts.txt\n"
+"(but not privatehosts.txt) after conversion to lower case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:249
+msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:253
+msgid "Must not start with '.' or '-'."
+msgstr "Não pode começar com '.' ou '-'"
+
+#: i2p2www/pages/site/docs/naming.html:257
+msgid "Must end with '.i2p'."
+msgstr "Deve terminar com '.i2p'."
+
+#: i2p2www/pages/site/docs/naming.html:261
+msgid "67 characters maximum, including the '.i2p'."
+msgstr "No máximo 67 caractéres, incluindo o '.i2p'."
+
+#: i2p2www/pages/site/docs/naming.html:265
+msgid "Must not contain '..'."
+msgstr "Não pode conter '..'."
+
+#: i2p2www/pages/site/docs/naming.html:269
+msgid "Must not contain '.-' or '-.' (as of 0.6.1.33)."
+msgstr "Não pode conter '.-' ou '-.' (tal como 0.6.1.33)."
+
+#: i2p2www/pages/site/docs/naming.html:273
+msgid "Must not contain '--' except in 'xn--' for IDN."
+msgstr "Não pode conter '--' exceto em 'xn--' para IDN."
+
+#: i2p2www/pages/site/docs/naming.html:277
+msgid ""
+"Base32 hostnames (*.b32.i2p) are reserved for base 32 use and so are not "
+"allowed to be imported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:281
+msgid ""
+"Certain hostnames reserved for project use are not allowed\n"
+"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
+"*.console.i2p, and others)"
+msgstr ""
+"Alguns nomes de hosts reservados para uso do projeto não são permitidos\n"
+"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
+"*.console.i2p, and others)"
+
+#: i2p2www/pages/site/docs/naming.html:286
+msgid "Keys are checked for base64 validity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:290
+msgid ""
+"Keys are checked for conflict with existing keys in hosts.txt (but not "
+"privatehosts.txt)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:294
+msgid "Minimum key length 516 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:298
+msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:303
+msgid ""
+"Any name received via subscription that passes all the checks is added "
+"via the local naming service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:307
+msgid ""
+"Note that the '.' symbols in a host name are of no significance,\n"
+"and do not denote any actual naming or trust hierarchy.\n"
+"If the name 'host.i2p' already exists, there is nothing\n"
+"to prevent anybody from adding a name 'a.host.i2p' to their hosts.txt,\n"
+"and this name can be imported by others' addressbook.\n"
+"Methods to deny subdomains to non-domain 'owners' (certificates?),\n"
+"and the desirability and feasibility of these methods,\n"
+"are topics for future discussion."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:318
+msgid ""
+"International Domain Names (IDN) also work in i2p (using punycode 'xn--' "
+"form).\n"
+"To see IDN .i2p domain names rendered correctly in Firefox's location "
+"bar,\n"
+"add 'network.IDN.whitelist.i2p (boolean) = true' in about:config."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:324
+msgid ""
+"As the addressbook application does not use privatehosts.txt at all, in "
+"practice\n"
+"this file is the only place where it is appropriate to place private "
+"aliases or\n"
+"\"pet names\" for sites already in hosts.txt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:330
+msgid "Outgoing Subscriptions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:331
+msgid ""
+"Addressbook will publish the merged hosts.txt to a location\n"
+"(traditionally hosts.txt in the local eepsite's home directory) to be "
+"accessed by others\n"
+"for their subscriptions.\n"
+"This step is optional and is disabled by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:339
+msgid ""
+"The addressbook application, together with eepget, saves the Etag and/or "
+"Last-Modified\n"
+"information returned by the web server of the subscription.\n"
+"This greatly reduces the bandwidth required, as the web server will\n"
+"return a '304 Not Modified' on the next fetch if nothing has changed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:346
+msgid ""
+"However the entire hosts.txt is downloaded if it has changed.\n"
+"See below for discussion on this issue."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:351
+msgid ""
+"Hosts serving a static hosts.txt or an equivalent CGI application\n"
+"are strongly encouraged to deliver\n"
+"a Content-Length header, and either an Etag or Last-Modified header.\n"
+"Also ensure that the server delivers a '304 Not Modified' when "
+"appropriate.\n"
+"This will dramatically reduce the network bandwidth, and\n"
+"reduce chances of corruption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:360
+msgid "Host Add Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:361
+msgid ""
+"A host add service is a simple CGI application that takes a hostname and "
+"a Base64 key as parameters\n"
+"and adds that to its local hosts.txt.\n"
+"If other routers subscribe to that hosts.txt, the new hostname/key\n"
+"will be propagated through the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:368
+msgid ""
+"It is recommended that host add services impose, at a minimum, the "
+"restrictions imposed by the addressbook application listed above.\n"
+"Host add services may impose additional restrictions on hostnames and "
+"keys, for example:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:373
+msgid "A limit on number of 'subdomains'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:377
+msgid "Authorization for 'subdomains' through various methods."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:381
+msgid "Hashcash or signed certificates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:385
+msgid "Editorial review of host names and/or content."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:389
+msgid "Categorization of hosts by content."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:393
+msgid "Reservation or rejection of certain host names."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:397
+msgid "Restrictions on the number of names registered in a given time period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:401
+msgid "Delays between registration and publication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:405
+msgid "Requirement that the host be up for verification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:409
+msgid "Expiration and/or revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:413
+msgid "IDN spoof rejection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:418
+msgid "Jump Services"
+msgstr "Serviços de saltos"
+
+#: i2p2www/pages/site/docs/naming.html:419
+msgid ""
+"A jump service is a simple CGI application that takes a hostname as a "
+"parameter\n"
+"and returns a 301 redirect to the proper URL with a "
+"?i2paddresshelper=key\n"
+"string appended.\n"
+"The HTTP proxy will interpret the appended string and\n"
+"use that key as the actual destination.\n"
+"In addition, the proxy will cache that key so the\n"
+"address helper is not necessary until restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:429
+msgid ""
+"Note that, like with subscriptions, using a jump service\n"
+"implies a certain amount of trust, as a jump service could maliciously\n"
+"redirect a user to an incorrect destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:435
+msgid ""
+"To provide the best service, a jump service should be subscribed to\n"
+"several hosts.txt providers so that its local host list is current."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:441
+msgid ""
+"SusiDNS is simply a web interface front-end to configuring addressbook "
+"subscriptions\n"
+"and accessing the four addressbook files.\n"
+"All the real work is done by the 'addressbook' application."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:447
+msgid ""
+"Currently, there is little enforcement of addressbook naming rules within"
+" SusiDNS,\n"
+"so a user may enter hostnames locally that would be rejected by\n"
+"the addressbook subscription rules."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:453
+msgid "Base32 Names"
+msgstr "Nomes de Base32"
+
+#: i2p2www/pages/site/docs/naming.html:454
+msgid ""
+"I2P supports Base32 hostnames similar to Tor's .onion addresses.\n"
+"Base32 addresses are much shorter and easier to handle than the\n"
+"full 516-character Base64 Destinations or addresshelpers.\n"
+"Example: "
+"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:461
+#, python-format
+msgid ""
+"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 "
+"hash.\n"
+"I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n"
+"The form is {52 chars}.b32.i2p.\n"
+"Tor has recently published a\n"
+"proposal\n"
+"to convert to an identical format of {52 chars}.onion for their hidden "
+"services.\n"
+"Base32 is implemented in the naming service, which queries the\n"
+"router over I2CP to lookup the LeaseSet to get the full Destination.\n"
+"Base32 lookups will only be successful when the Destination is up and "
+"publishing\n"
+"a LeaseSet.\n"
+"Because resolution may require a network database lookup, it may take "
+"significantly\n"
+"longer than a local address book lookup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:476
+msgid ""
+"Base32 addresses can be used in most places where hostnames or full "
+"destinations\n"
+"are used, however there are some exceptions where they may fail if the\n"
+"name does not immediately resolve. I2PTunnel will fail, for example, if\n"
+"the name does not resolve to a destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:2
+#: i2p2www/pages/site/docs/spec/configuration.html:65
+msgid "Plugins"
+msgstr "Extensões"
+
+#: i2p2www/pages/site/docs/plugins.html:3
+msgid "June 2012"
+msgstr "Junho de 2012"
+
+#: i2p2www/pages/site/docs/plugins.html:6
+msgid "I2P Plugins"
+msgstr "Extensões da I2P"
+
+#: i2p2www/pages/site/docs/plugins.html:8
+msgid "General Information"
+msgstr "Informação geral"
+
+#: i2p2www/pages/site/docs/plugins.html:9
+msgid ""
+"I2P includes a plugin architecture\n"
+"to support easy development and installation of additional software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:14
+msgid ""
+"There are now plugins available that support distributed email, blogs, "
+"IRC\n"
+"clients, distributed file storage, wikis, and more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:19
+msgid "Benefits to i2p users and app developers:"
+msgstr "Benefícios para os usuários da I2P e desenvolvedores de aplicações:"
+
+#: i2p2www/pages/site/docs/plugins.html:24
+msgid "Easy distribution of applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:28
+msgid ""
+"Allows innovation and use of additional libraries without worrying about\n"
+"increasing the size of i2pupdate.sud"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:33
+msgid ""
+"Support large or special-purpose applications that would never be bundled"
+"\n"
+"with the I2P installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:38
+msgid "Cryptographically signed and verified applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:42
+msgid "Automatic updates of applications, just like for the router"
+msgstr "Atualizações automática de aplicações, tal como para o roteador"
+
+#: i2p2www/pages/site/docs/plugins.html:46
+msgid ""
+"Separate initial install and update packages, if desired, for smaller "
+"update downloads"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:50
+msgid ""
+"One-click installation of applications. No more asking users to modify\n"
+"wrapper.config or clients.config"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:55
+msgid "Isolate applications from the base $I2P installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:59
+msgid ""
+"Automatic compatibility checking for I2P version, Java version, Jetty\n"
+"version, and previous installed application version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:64
+msgid "Automatic link addition in console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:68
+msgid ""
+"Automatic startup of application, including modifying classpath, without "
+"requiring a restart"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:72
+msgid "Automatic integration and startup of webapps into console Jetty instance"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:76
+#, python-format
+msgid ""
+"Facilitate creation of 'app stores' like the one at\n"
+"%(pluginsite)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:81
+msgid "One-click uninstall"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:85
+msgid "Language and theme packs for the console"
+msgstr "Pacotes de temas e idiomas para o painel"
+
+#: i2p2www/pages/site/docs/plugins.html:89
+msgid "Bring detailed application information to the router console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:93
+msgid "Non-java applications also supported"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:99
+msgid "Required I2P version"
+msgstr "Versão do roteador I2P necessária"
+
+#: i2p2www/pages/site/docs/plugins.html:100
+msgid "0.7.12 or newer."
+msgstr "0.7.12 ou mais recente."
+
+#: i2p2www/pages/site/docs/plugins.html:102
+msgid "Installation"
+msgstr "Instalação"
+
+#: i2p2www/pages/site/docs/plugins.html:103
+msgid ""
+"To install and start a plugin, copy the .xpi2p install link "
+"to\n"
+"the form at the bottom of\n"
+"configclients.jsp"
+" in\n"
+"your router console and click the \"install plugin\" button.  After a"
+"\n"
+"plugin is installed and started, a link to the plugin will usually appear"
+" at\n"
+"the top of your summary bar."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:112
+msgid ""
+"To update a plugin to the latest version, just click the update button on"
+"\n"
+"configclients.jsp."
+"\n"
+"There is also a button to check if the plugin has a more recent version, "
+"as\n"
+"well as a button to check for updates for all plugins.  Plugins will be "
+"checked\n"
+"for updates automatically when updating to a new I2P release (not "
+"including dev\n"
+"builds)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:122
+msgid "Development"
+msgstr "Desenvolvimento"
+
+#: i2p2www/pages/site/docs/plugins.html:123
+#, python-format
+msgid ""
+"See the latest plugin specification and "
+"the\n"
+"plugin forum on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:128
+#, python-format
+msgid ""
+"See also the sources for plugins developed by various people.  Some "
+"plugins, such\n"
+"as snowman, were "
+"developed\n"
+"specifically as examples."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:134
+msgid ""
+"Developers wanted! Plugins are a great way to learn more about I2P"
+"\n"
+"or easily add some feature."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:139
+msgid "Getting Started"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:140
+#, python-format
+msgid ""
+"To create a plugin from an existing binary package you will need to get\n"
+"makeplugin.sh from the i2p.scripts branch in "
+"monotone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:146
+msgid "Known Issues"
+msgstr "Problemas conhecidos"
+
+#: i2p2www/pages/site/docs/plugins.html:147
+msgid ""
+"Note that the router's plugin architecture does NOT currently\n"
+"provide any additional security isolation or sandboxing of plugins."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:153
+msgid ""
+"Updates of a plugin with included jars (not wars) won't be recognized if\n"
+"the plugin was already run, as it requires class loader trickery to flush"
+" the\n"
+"class cache; a full router restart is required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:159
+msgid "The stop button may be displayed even if there is nothing to stop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:163
+msgid ""
+"Plugins running in a separate JVM create a logs/ directory "
+"in\n"
+"$CWD."
+msgstr ""
+"Extensões rodando em Máquina Virtual Java separada criam um diretório de "
+"registros/ em\n"
+"$CWD."
+
+#: i2p2www/pages/site/docs/plugins.html:168
+msgid ""
+"No initial keys are present, except for those of jrandom and zzz (using "
+"the\n"
+"same keys as for router update), so the first key seen for a signer is\n"
+"automatically accepted—there is no signing key authority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:174
+msgid ""
+"When deleting a plugin, the directory is not always deleted, especially "
+"on\n"
+"Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:179
+msgid ""
+"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result "
+"in a\n"
+"\"plugin is corrupt\" message if pack200 compression of the plugin file "
+"is used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:184
+msgid "Theme and translation plugins are untested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:188
+msgid "Disabling autostart doesn't always work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:2
+msgid "Ports Used by I2P"
+msgstr "Portas usadas pela I2P"
+
+#: i2p2www/pages/site/docs/ports.html:7
+msgid ""
+"These are the ports used or reserved by I2P, including those for known "
+"plugins,\n"
+"common alternates,\n"
+"and some typical related applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:13
+#, python-format
+msgid ""
+"Note that many of these are not enabled by default.\n"
+"There is more information in the FAQ.\n"
+"See also the documentation for individual plugins.\n"
+"Plugin authors please add any ports you use here.\n"
+"For new plugins, we recommend using the next available port\n"
+"in the 766x range."
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:53
+msgid "recommended spot for new plugins/applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:3
+#: i2p2www/pages/site/docs/api/datagrams.html:3
+#: i2p2www/pages/site/docs/how/garlic-routing.html:3
+#: i2p2www/pages/site/docs/protocol/index.html:3
+msgid "August 2010"
+msgstr "Agosto de 2010"
+
+#: i2p2www/pages/site/docs/api/bob.html:5
+msgid "BOB - Basic Open Bridge"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:7
+msgid "Technical differences from SAM (for the better?)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:9
+msgid ""
+"BOB has separate command and data channels. \n"
+"One, an application command channel socket to router to configure.\n"
+"Two, the application data sockets to/from router that carry only data.\n"
+"The command channel is only needed for making or setting the initial\n"
+"destination key, and to set the destination key to port bindings. \n"
+"All connections run in parallel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:18
+msgid ""
+"SAM has one connection that does everything, and you need to parse every "
+"packet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:22
+msgid ""
+"BOB does not hold keypair values, nor does the router.\n"
+"Your application holds the keypair values. \n"
+"This is to reduce any extra complexity in the router code, it also adds "
+"to\n"
+"your privacy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:29
+msgid "SAM router stores every keypair you ever make."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:33
+msgid "Those are the important differences."
+msgstr "Tais diferenças são importantes."
+
+#: i2p2www/pages/site/docs/api/bob.html:37
+msgid "KEYS = keypair public+private, these are BASE64"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:40
+msgid "KEY = public key, also BASE64"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:43
+msgid ""
+"ERROR as is implied returns the message \"ERROR "
+"\"+DESCRIPTION+\"\n"
+"\", where the DESCRIPTION is what went wrong."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:46
+msgid ""
+"OK returns \"OK\", and if data is to be "
+"returned, it is on the same line. OK means the command is "
+"finished."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:49
+msgid ""
+"DATA lines contain information that you requested. There may"
+" be multiple DATA lines per request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:53
+msgid ""
+"NOTE: The help command is the ONLY command that has an exception "
+"to\n"
+"the rules... it can actually return nothing! This is intentional, since\n"
+"help is a HUMAN and not an APPLICATION command."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:59
+msgid ""
+"PLEASE NOTE:\n"
+"For CURRENT details on the commands PLEASE use the built-in help command."
+" \n"
+"Just telnet to localhost 2827 and type help and you can get full "
+"documentation on each command."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:65
+msgid ""
+"Commands never get obsoleted or changed, however new commands do get "
+"added from time to time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:69
+msgid "Here are the commands we have as of this writing:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:74
+msgid "COMMAND"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:74
+msgid "OPERAND"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:74
+msgid "RETURNS"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:101
+msgid ""
+"Once set up, all TCP sockets can and will block as needed, and there is "
+"no need for any \n"
+"additional messages to/from the command channel. This allows the router "
+"to pace the\n"
+"stream without exploding with OOM like SAM does as it chokes on "
+"attempting to shove \n"
+"many streams in or out one socket -- that can't scale when you have alot "
+"of connections!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:108
+msgid ""
+"What is also nice about this particular interface is that writing "
+"anything to interface \n"
+"to it, is much much easier than SAM. There is no other processing to do "
+"after the set up.\n"
+"It's configuration is so simple, that very simple tools, such as nc "
+"(netcat) can be used \n"
+"to point to some application. The value there is that one could schedule "
+"up and down times \n"
+"for an application, and not have to change the application to do that, or"
+" to even have \n"
+"to stop that application. Instead, you can literally \"unplug\" the "
+"destination, and \n"
+"\"plug it in\" again. As long as the same IP/port addresses and "
+"destination keys are used \n"
+"when bringing the bridge up, the normal TCP application won't care, and "
+"won't notice.\n"
+"It will simply be fooled -- the destinations are not reachable, and that "
+"nothing is coming in."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:120
+msgid ""
+"For the following example, we'll setup a very simple local loopback "
+"connection, \n"
+"with two destinations. Destination \"mouth\" will be the CHARGEN service "
+"from \n"
+"the INET superserver daemon. Destination \"ear\" will be a local port "
+"that you\n"
+"can telnet into, and watch the pretty ASCII test puke forth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:128
+msgid "EXAMPLE SESSION DIALOGUE -- simple telnet 127.0.0.1 2827 works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:129
+msgid "Application"
+msgstr "Aplicação"
+
+#: i2p2www/pages/site/docs/api/bob.html:130
+msgid "BOB's Command response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:132
+#: i2p2www/pages/site/docs/api/bob.html:144
+#: i2p2www/pages/site/docs/api/bob.html:164
+#: i2p2www/pages/site/docs/api/bob.html:272
+#: i2p2www/pages/site/docs/api/bob.html:284
+#: i2p2www/pages/site/docs/api/bob.html:299
+msgid "FROM"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:132
+#: i2p2www/pages/site/docs/api/bob.html:144
+#: i2p2www/pages/site/docs/api/bob.html:164
+#: i2p2www/pages/site/docs/api/bob.html:272
+#: i2p2www/pages/site/docs/api/bob.html:284
+#: i2p2www/pages/site/docs/api/bob.html:299
+msgid "TO"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:132
+#: i2p2www/pages/site/docs/api/bob.html:144
+#: i2p2www/pages/site/docs/api/bob.html:164
+#: i2p2www/pages/site/docs/api/bob.html:272
+#: i2p2www/pages/site/docs/api/bob.html:284
+#: i2p2www/pages/site/docs/api/bob.html:299
+msgid "DIALOGUE"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:139
+msgid "MAKE NOTE OF THE ABOVE DESTINATION KEY, YOURS WILL BE DIFFERENT!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:153
+msgid ""
+"At this point, there was no error, a destination with a nickname of "
+"\"mouth\" \n"
+"is set up. When you contact the destination provided, you actually "
+"connect \n"
+"to the CHARGEN service on 19/TCP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:159
+msgid "Now for the other half, so that we can actually contact this destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:179
+msgid ""
+"Now all we need to do is telnet into 127.0.0.1, port 37337,\n"
+"send the destination key or host address from addressbook we want to "
+"contact.\n"
+"In this case, we want to contact \"mouth\", all we do is paste in the\n"
+"key and it goes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:186
+msgid ""
+"NOTE: The \"quit\" command in the command channel does NOT "
+"disconnect the tunnels like SAM."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:203
+msgid "After a few virtual miles of this spew, press Control-]"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:215
+msgid "Here is what happened..."
+msgstr "Eis aqui o que acontece..."
+
+#: i2p2www/pages/site/docs/api/bob.html:223
+msgid "You can connect to EEPSITES too!"
+msgstr "Você também pode se conectar a EEPSITES!"
+
+#: i2p2www/pages/site/docs/api/bob.html:256
+msgid ""
+"Pretty cool isn't it? Try some other well known EEPSITES if you like, "
+"nonexistent ones, \n"
+"etc, to get a feel for what kind of output to expect in different "
+"situations. \n"
+"For the most part, it is suggested that you ignore any of the error "
+"messages. \n"
+"They would be meaningless to the application, and are only presented for "
+"human debugging."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:263
+msgid "Let's put down our destinations now that we are all done with them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:267
+msgid "First, lets see what destination nicknames we have."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:279
+msgid "Alright, there they are. First, let's remove \"mouth\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:293
+msgid ""
+"Now to remove \"ear\", note that this is what happens when you type too "
+"fast,\n"
+"and shows you what typical ERROR messages looks like."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:312
+msgid ""
+"I won't bother to show an example of the receiver end of a bridge\n"
+"because it is very simple. There are two possible settings for it, and\n"
+"it is toggled with the \"quiet\" command."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:318
+msgid ""
+"The default is NOT quiet, and the first data to come into your\n"
+"listening socket is the destination that is making the contact. It is a\n"
+"single line consisting of the BASE64 address followed by a newline.\n"
+"Everything after that is for the application to actually consume."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:325
+msgid ""
+"In quiet mode, think of it as a regular Internet connection. No\n"
+"extra data comes in at all. It's just as if you are plain connected to\n"
+"the regular Internet. This mode allows a form of transparency much like\n"
+"is available on the router console tunnel settings pages, so that you\n"
+"can use BOB to point a destination at a web server, for example, and\n"
+"you would not have to modify the web server at all."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:334
+msgid ""
+"The advantage with using BOB for this is as discussed\n"
+"previously. You could schedule random uptimes for the application,\n"
+"redirect to a different machine, etc. One use of this may be something\n"
+"like wanting to try to goof up router-to-destination upness guessing.\n"
+"You could stop and start the destination with a totally different\n"
+"process to make random up and down times on services. That way you\n"
+"would only be stopping the ability to contact such a service, and not\n"
+"have to bother shutting it down and restarting it. You could redirect\n"
+"and point to a different machine on your LAN while you do updates, or\n"
+"point to a set of backup machines depending on what is running, etc,\n"
+"etc. Only your imagination limits what you could do with BOB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:6
+msgid "Datagram Overview"
+msgstr "Uma visão geral do datagrama"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:7
+#, python-format
+msgid ""
+"Datagrams build upon the base I2CP to provide "
+"authenticated\n"
+"and repliable messages in a standard format.  This lets applications "
+"reliably read\n"
+"the \"from\" address out of a datagram and know that the address really "
+"sent the\n"
+"message.  This is necessary for some applications since the base I2P "
+"message is\n"
+"completely raw - it has no \"from\" address (unlike IP packets).  In "
+"addition, the\n"
+"message and sender are authenticated by signing the payload."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:16
+#, python-format
+msgid ""
+"Datagrams, like streaming library packets,\n"
+"are an application-level construct.\n"
+"These protocols are independent of the low-level transports;\n"
+"the protocols are converted to I2NP messages by the router, and\n"
+"either protocol may be carried by either transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:25
+msgid "Application Guide"
+msgstr "Guia de aplicações"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:26
+#, python-format
+msgid ""
+"Applications written in Java may use the \n"
+"datagram API,\n"
+"while applications in other languages \n"
+"can use SAM's datagram support.\n"
+"There is also limited support in i2ptunnel in the SOCKS proxy,\n"
+"the 'streamr' tunnel types, and udpTunnel classes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:37
+msgid "Datagram Length"
+msgstr "Comprimento do datagrama"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:38
+msgid ""
+"The application designer should carefully consider the tradeoff of "
+"repliable vs. non-repliable\n"
+"datagrams. Also, the datagram size will affect reliability, due to tunnel"
+" fragmentation into 1KB\n"
+"tunnel messages. The more message fragments, the more likely that one of "
+"them will be dropped\n"
+"by an intermediate hop. Messages larger than a few KB are not "
+"recommended.\n"
+"Over about 10 KB, the delivery probablility drops dramatically.\n"
+"Messages over 16 KB cannot be delivered over NTCP, dropping delivery "
+"chances even more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:47
+#, python-format
+msgid ""
+"Also note that the various overheads added by lower layers, in particular"
+" asymmetric\n"
+"ElGamal/AES, place a large burden on "
+"intermittent messages\n"
+"such as used by a Kademlia-over-UDP application. The implementations are "
+"currently tuned\n"
+"for frequent traffic using the streaming library. There are a high number"
+"\n"
+"of session tags delivered, and a short session tag lifetime, for example."
+"\n"
+"There are currently no configuration parameters available within I2CP to "
+"tune\n"
+"the ElGamal Session Tag parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:57
+msgid "I2CP Protocol Number and Ports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:58
+msgid ""
+"The standard I2CP protocol number for datagrams is PROTO_DATAGRAM (17).\n"
+"Applications may or may not choose to set the\n"
+"protocol in the I2CP header. It is not set by default.\n"
+"It must be set to demultiplex datagram and streaming traffic received on "
+"the same Destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:65
+#, python-format
+msgid ""
+"As datagrams are not connection-oriented, the application may require\n"
+"port numbers to correlate datagrams with particular peers or "
+"communications sessions,\n"
+"as is traditional with UDP over IP.\n"
+"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as "
+"described in\n"
+"the I2CP page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:73
+#, python-format
+msgid ""
+"There is no method within the datagram API to specify whether it is non-"
+"repliable (raw)\n"
+"or repliable. The application should be designed to expect the "
+"appropriate type.\n"
+"The I2CP protocol number or port should be used by the application to\n"
+"indicate datagram type.\n"
+"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW "
+"are defined in the\n"
+"I2PSession API\n"
+"for this purpose. A common design pattern in client/server datagram "
+"applications is to\n"
+"use signed datagrams for a request which includes a nonce, and use a raw "
+"datagram\n"
+"for the reply, returning the nonce from the request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:85
+#, python-format
+msgid ""
+"The protocols and ports may be set in I2CP's\n"
+"I2PSession API,\n"
+"as implemented in\n"
+"I2PSessionMuxedImpl."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:93
+#: i2p2www/pages/site/docs/api/streaming.html:381
+msgid "Data Integrity"
+msgstr "Integridade dos dados"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:94
+#, python-format
+msgid ""
+"Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
+"the I2CP layer.\n"
+"There is no checksum field in the datagram protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:100
+#: i2p2www/pages/site/docs/api/streaming.html:389
+msgid "Packet Encapsulation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:101
+#, python-format
+msgid ""
+"Each datagram is sent through I2P as a single message (or as an "
+"individual clove in a\n"
+"Garlic Message).\n"
+"Message encapsulation is implemented in the underlying\n"
+"I2CP,\n"
+"I2NP, and\n"
+"tunnel message layers.\n"
+"There is no packet delimiter mechanism or length field in the datagram "
+"protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:114
+#: i2p2www/pages/site/docs/spec/datagrams.html:10
+#: i2p2www/pages/site/docs/transport/ssu.html:571
+msgid "Specification"
+msgstr "Especificação"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:116
+msgid "See the Datagrams Specification page."
+msgstr "Ver a página da Especificação de Datagramas."
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:4
+msgid "I2PControl - Remote Control Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:5
+#, python-format
+msgid ""
+"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n"
+"The aim of the interface is to provide simple way to interface with a "
+"running I2P node. A client, itoopie, has been developed in parallel.\n"
+"The JSONRPC2 implementation for the client as well as the plugin is "
+"provided by the java libraries JSON-RPC 2.0.  \n"
+"A list of implementations of JSON-RPC for various languages can be found "
+"at the JSON-RPC "
+"wiki."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:12
+msgid "I2PControl is by default listening on localhost:7650"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:14
+msgid "API, version 1."
+msgstr "API, versão 1."
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:15
+msgid "Parameters are only provided in a named way (maps)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:19
+msgid "JSON-RPC 2 format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:21
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:27
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:40
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:50
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:59
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:69
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:84
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:137
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:154
+msgid "Request:"
+msgstr "Pedido:"
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:23
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:32
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:44
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:54
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:64
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:75
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:101
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:145
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:169
+msgid "Response:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:26
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:28
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:29
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:33
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:34
+#: i2p2www/pages/site/docs/protocol/i2cp.html:107
+#: i2p2www/pages/site/docs/protocol/i2cp.html:450
+#: i2p2www/pages/site/docs/spec/common-structures.html:16
+#: i2p2www/pages/site/docs/spec/common-structures.html:26
+#: i2p2www/pages/site/docs/spec/common-structures.html:37
+#: i2p2www/pages/site/docs/spec/common-structures.html:49
+#: i2p2www/pages/site/docs/spec/common-structures.html:64
+#: i2p2www/pages/site/docs/spec/common-structures.html:77
+#: i2p2www/pages/site/docs/spec/common-structures.html:90
+#: i2p2www/pages/site/docs/spec/common-structures.html:102
+#: i2p2www/pages/site/docs/spec/common-structures.html:114
+#: i2p2www/pages/site/docs/spec/common-structures.html:126
+#: i2p2www/pages/site/docs/spec/common-structures.html:138
+#: i2p2www/pages/site/docs/spec/common-structures.html:150
+#: i2p2www/pages/site/docs/spec/common-structures.html:162
+#: i2p2www/pages/site/docs/spec/common-structures.html:174
+#: i2p2www/pages/site/docs/spec/common-structures.html:227
+#: i2p2www/pages/site/docs/spec/common-structures.html:310
+#: i2p2www/pages/site/docs/spec/common-structures.html:359
+#: i2p2www/pages/site/docs/spec/common-structures.html:411
+#: i2p2www/pages/site/docs/spec/common-structures.html:456
+#: i2p2www/pages/site/docs/spec/common-structures.html:593
+#: i2p2www/pages/site/docs/spec/common-structures.html:655
+msgid "Description"
+msgstr "Descrição"
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:30
+msgid ""
+"Token used for authenticating every request (excluding the 'Authenticate'"
+" RPC method)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:38
+msgid "Implemented methods"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:39
+msgid ""
+"Creates and returns an authentication token used for further "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:41
+msgid "The version of the I2PControl API used by the client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:42
+msgid "The password used for authenticating against the remote server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:45
+msgid "The primary I2PControl API version implemented by the server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:46
+msgid "The token used for further communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:49
+msgid "Echoes the value of the echo key, used for debugging and testing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:51
+msgid "Value will be returned in response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:52
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:62
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:73
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:99
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:143
+msgid ""
+"Token used for authenticating the client. Is provided by the server via "
+"the 'Authenticate' RPC method."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:55
+msgid "Value of the key 'echo' in the request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:58
+msgid ""
+"Fetches rateStat from router statManager. Creates stat if not already "
+"created."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:60
+#, python-format
+msgid ""
+"Determines which rateStat to fetch, see ratestats."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:61
+msgid "Determines which period a stat is fetched for. Measured in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:65
+msgid "Returns the average value for the reuested rateStat and period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:68
+msgid "Manages I2PControl. Ports, passwords and the like."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:70
+msgid ""
+"Sets a new listen address for I2PControl (only 127.0.0.1 and 0.0.0.0 are "
+"implemented in I2PControl currently)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:71
+msgid ""
+"Sets a new password for I2PControl, all Authentication tokens will be "
+"revoked."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:72
+msgid "Switches which port I2PControl will listen for connections on."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:76
+msgid "Returned if address was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:77
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:78
+msgid "Returned if setting was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:79
+msgid "Returns true if any changes were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:80
+msgid "Returns true if any changes requiring a restart to take effect were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:83
+msgid "Fetches basic information about the I2P router. Uptime, version etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:102
+msgid "What the status of the router is."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:103
+msgid "What the uptime of the router is in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:104
+msgid "What version of I2P the router is running."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:105
+msgid "The 1 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:106
+msgid "The 15 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:107
+msgid "The 1 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:108
+msgid "The 15 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:109
+msgid "What the current network status is. According to the below enum:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:128
+msgid "How many tunnels on the I2P net are we participating in."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:129
+msgid "How many peers have we communicated with recently."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:130
+msgid "How many peers are considered 'fast'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:131
+msgid "How many peers are considered 'high capacity'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:132
+msgid "Is the router reseeding hosts to its NetDB?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:133
+msgid "How many peers are known to us (listed in our NetDB)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:136
+msgid "Manages I2P router restart/shutdown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:138
+msgid ""
+"Initiates a router reseed, fetching peers into our NetDB from a remote "
+"host."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:139
+msgid "Restarts the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:140
+msgid ""
+"Restarts the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:141
+msgid "Shuts down the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:142
+msgid ""
+"Shuts down the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:146
+msgid "If requested, verifies that a reseed has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:147
+msgid "If requested, verifies that a restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:148
+msgid "If requested, verifies that a graceful restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:149
+msgid "If requested, verifies that a shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:150
+msgid "If requested, verifies that a graceful shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:153
+msgid "Fetches or sets various network related settings. Ports, addresses etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:155
+msgid ""
+"What port is used for the TCP transport. If null is submitted, current "
+"setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:156
+msgid ""
+"What hostname is used for the TCP transport. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:157
+msgid ""
+"Use automatically detected ip for TCP transport. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:158
+msgid ""
+"What port is used for the UDP transport. If null is submitted, current "
+"setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:159
+msgid ""
+"What hostname is used for the UDP transport. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:160
+msgid ""
+"Which methods should be used for detecting the ip address of the UDP "
+"transport. If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:161
+msgid "What ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:162
+msgid "Is UPnP enabled. If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:163
+msgid ""
+"How many percent of bandwidth is usable for participating tunnels. If "
+"null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:164
+msgid ""
+"How many KB/s of inbound bandwidth is allowed. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:165
+msgid ""
+"How many KB/s of outbound bandwidth is allowed. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:166
+msgid ""
+"Is laptop mode enabled (change router identity and UDP port when IP "
+"changes ). If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:167
+msgid ""
+"Token used for authenticating the client. Is provided by the server via "
+"the 'Authenticate' RPC method. If null is submitted, current setting will"
+" be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:170
+msgid "If requested, returns the port used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:171
+msgid "If requested, returns the hostname used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:172
+msgid ""
+"If requested, returns the method used for automatically detecting ip for "
+"the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:173
+msgid "If requested, returns the port used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:174
+msgid "If requested, returns the hostname used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:175
+msgid ""
+"If requested, returns methods used for detecting the ip address of the "
+"UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:176
+msgid "If requested, returns what ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:177
+msgid "If requested, returns the UPNP setting."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:178
+msgid ""
+"If requested, returns how many percent of bandwidth is usable for "
+"participating tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:179
+msgid "If requested, returns how many KB/s of inbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:180
+msgid "If requested, returns how many KB/s of outbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:181
+msgid "If requested, returns the laptop mode."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:182
+msgid "Have the provided settings been saved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:183
+msgid "Is a restart needed for the new settings to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:186
+msgid "denotes an optional value."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:187
+msgid "denotes a possibly occuring return value"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:189
+msgid "Error codes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:190
+msgid "Standard JSON-RPC2 error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:191
+msgid "JSON parse error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:192
+msgid "Invalid request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:193
+msgid "Method not found."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:194
+msgid "Invalid parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:195
+msgid "Internal error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
+msgid "I2PControl specific error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
+msgid "Invalid password provided."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
+msgid "No authentication token presented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
+msgid "Authentication token doesn't exist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
+msgid "The provided authentication token was expired and will be removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
+msgid ""
+"The version of the I2PControl API used wasn't specified, but is required "
+"to be specified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:203
+msgid ""
+"The version of the I2PControl API specified is not supported by "
+"I2PControl."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:13
+#, python-format
+msgid ""
+"I2PTunnel is a tool for interfacing with and providing services on I2P.\n"
+"Destination of an I2PTunnel can be defined using a hostname,\n"
+"Base32, or a full 516-byte destination "
+"key.\n"
+"An established I2PTunnel will be available on your client machine as "
+"localhost:port.\n"
+"If you wish to provide a service on I2P network, you simply create "
+"I2PTunnel to the\n"
+"appropriate ip_address:port. A corresponding 516-byte destination key "
+"will be generated\n"
+"for the service and it will become avaliable throughout I2P.\n"
+"A web interface for I2PTunnel management is avaliable on\n"
+"localhost:7657/i2ptunnel/."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:25
+msgid "Default Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:26
+msgid "Server tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:28
+msgid ""
+"I2P Webserver - A tunnel pointed to a Jetty webserver run\n"
+"on localhost:7658 for convenient "
+"and quick hosting on I2P.\n"
+"
            The document root is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:36
+msgid "Client tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:38
+msgid ""
+"A HTTP proxy used for browsing I2P and the regular internet anonymously "
+"through I2P. \n"
+"Browsing internet through I2P uses a random proxy specified by the "
+"\"Outproxies:\" option."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:42
+msgid "An IRC tunnel to the default anonymous IRC network, Irc2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:43
+#, python-format
+msgid ""
+"The anonymous monotone\n"
+"sourcecode repository for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:47
+#, python-format
+msgid ""
+"A SMTP service provided by postman at %(postman)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:50
+#, python-format
+msgid ""
+"The accompanying POP sevice of postman at %(postman)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:55
+msgid "Client Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:56
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:138
+msgid "Standard"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:57
+msgid ""
+"Opens a local TCP port that connects to a service (like HTTP, FTP or "
+"SMTP) on a destination inside of I2P.\n"
+"The tunnel is directed to a random host from the comma seperated (\", \")"
+" list of destinations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:63
+msgid ""
+"A HTTP-client tunnel. The tunnel connects to the destination specified by"
+" the URL\n"
+"in a HTTP request. Supports proxying onto internet if an outproxy is "
+"provided. Strips HTTP connections of the following headers:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:68
+msgid ""
+"Accept, Accept-Charset, Accept-Encoding, Accept-Language\n"
+" and Accept-Ranges as they vary greatly between browsers and can be "
+"used as an identifier."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:76
+msgid ""
+"HTTP client/server tunnels are via I2Ptunnel force-enabling compression "
+"via the following http headers:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:83
+msgid ""
+"Depending on if the tunnel is using an outproxy or not it will append the"
+" following User-Agent:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:87
+msgid "Outproxy:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:88
+msgid "Internal I2P use:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:93
+msgid ""
+"Creates a connection to a random IRC server specified by the comma "
+"seprated (\", \") \n"
+"list of destinations. Only a whitelisted subset of IRC commands are "
+"allowed due to anonymity concerns."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:97
+msgid "Whitelist:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:112
+msgid "Enables using the I2P router as a SOCKS proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:117
+msgid ""
+"Enables using the I2P router as a SOCKS proxy with the command whitelist "
+"specified by\n"
+"IRC client mode."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:123
+msgid ""
+"Creates a HTTP tunnel and uses the HTTP request method \"CONNECT\" \n"
+"to build a TCP tunnel that usually is used for SSL and HTTPS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:129
+msgid ""
+"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr "
+"client tunnel will \n"
+"subscribe to a streamr server tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:137
+msgid "Server Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:139
+msgid "Creates a destination to a local ip:port with an open TCP port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:144
+msgid ""
+"Creates a destination to a local HTTP server ip:port. Supports gzip for "
+"requests with \n"
+"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in"
+" such a request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:150
+msgid ""
+"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client "
+"with no outproxying\n"
+"capabilities. An example application would be a web application that does"
+" client-type\n"
+"requests, or loopback-testing an eepsite as a diagnostic tool."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:157
+msgid ""
+"Creates a destination that filters the reqistration sequence of a client "
+"and passes \n"
+"the clients destination key as a hostname to the IRC-server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:163
+msgid ""
+"A UDP-client that connects to a media server is created. The UDP-Client "
+"is coupled with a Streamr server I2PTunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:2
+#: i2p2www/pages/site/docs/api/ministreaming.html:17
+msgid "Ministreaming Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:5
+msgid "Note"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:7
+#, python-format
+msgid ""
+"The ministreaming library has been enhanced and extended by the\n"
+"\"full\" streaming library.\n"
+"Ministreaming is deprecated and is incompatible with today's "
+"applications.\n"
+"The following documentation is old.\n"
+"Also note that streaming extends ministreaming in the same Java package "
+"(net.i2p.client.streaming),\n"
+"so the current API documentation contains both.\n"
+"Obsolete ministreaming classes and methods are clearly marked as "
+"deprecated in the Javadocs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:19
+#, python-format
+msgid ""
+"\n"
+"The ministreaming library is a layer on top of the core \n"
+"I2CP that allows reliable, in order, and "
+"authenticated streams\n"
+"of messages to operate across an unreliable, unordered, and "
+"unauthenticated \n"
+"message layer.  Just like the TCP to IP relationship, this streaming \n"
+"functionality has a whole series of tradeoffs and optimizations "
+"available, but\n"
+"rather than embed that functionality into the base I2P code, it has been "
+"factored\n"
+"off into its own library both to keep the TCP-esque complexities separate"
+" and to\n"
+"allow alternative optimized implementations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:30
+#, python-format
+msgid ""
+"The ministreaming library was written by mihi as a part of his \n"
+"I2PTunnel application and then factored out"
+" and released\n"
+"under the BSD license.  It is called the \"mini\"streaming library "
+"because it makes\n"
+"some simplifications in the implementation, while a more robust streaming"
+" library\n"
+"could be further optimized for operation over I2P.  The two main issues "
+"with \n"
+"the ministreaming library are its use of the traditional TCP two phase \n"
+"establishment protocol and the current fixed window size of 1.  The "
+"establishment\n"
+"issue is minor for long lived streams, but for short ones, such as quick "
+"HTTP\n"
+"requests, the impact can be significant.  As "
+"for the window\n"
+"size, the ministreaming library doesn't maintain any ID or ordering "
+"within the \n"
+"messages sent (or include any application level ACK or SACK), so it must "
+"wait \n"
+"on average twice the time it takes to send a message before sending "
+"another."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:45
+#, python-format
+msgid ""
+"Even with those issues, the ministreaming library performs quite well in "
+"many\n"
+"situations, and its API\n"
+"is both quite simple and capable of remaining unchanged as different "
+"streaming\n"
+"implementations are introduced.  The library is deployed in its own \n"
+"ministreaming.jar.\n"
+"Developers in Java who would like to use it can\n"
+"access the API directly, while developers in other languages can use it "
+"through\n"
+"SAM's streaming support."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:4
+msgid "SOCKS and SOCKS proxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:5
+msgid ""
+"\n"
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"Enable SOCKS by creating a SOCKS client tunnel in i2ptunnel.\n"
+"Both shared-clients and non-shared are supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:12
+#, python-format
+msgid ""
+"\n"
+"As it says on the FAQ:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:15
+msgid ""
+"Many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:25
+msgid "And quoting from a 2005 email:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:28
+msgid ""
+"... there is a reason why human and\n"
+"others have both built and abandoned the SOCKS proxies.  Forwarding\n"
+"arbitrary traffic is just plain unsafe, and it behooves us as\n"
+"developers of anonymity and security software to have the safety of\n"
+"our end users foremost in our minds."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:36
+msgid ""
+"Hoping that we can simply strap an arbitrary client on top of I2P\n"
+"without auditing both its behavior and its exposed protocols for\n"
+"security and anonymity is naive.  Pretty much *every* application\n"
+"and protocol violates anonymity, unless it was designed for it\n"
+"specifically, and even then, most of those do too.  That's the\n"
+"reality.  End users are better served with systems designed for\n"
+"anonymity and security.  Modifying existing systems to work in\n"
+"anonymous environments is no small feat, orders of magnitude more\n"
+"work that simply using the existing I2P APIs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:48
+msgid ""
+"The SOCKS proxy\n"
+"supports standard addressbook names, but not Base64 destinations.\n"
+"Base32 hashes should work as of release 0.7.\n"
+"It supports outgoing connections only, i.e. an I2PTunnel Client.\n"
+"UDP support is stubbed out but not working yet.\n"
+"Outproxy selection by port number is stubbed out."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:57
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:281
+msgid "See Also"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:59
+#, python-format
+msgid ""
+"The notes for Meeting 81 and\n"
+"Meeting 82 in March 2004."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:69
+msgid "If You Do Get Something Working"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:70
+msgid ""
+"Please let us know. And please provide substantial warnings about the\n"
+"risks of socks proxies."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:8
+#, python-format
+msgid ""
+"The streaming library is technically part of the \"application\" layer,\n"
+"as it is not a core router function.\n"
+"In practice, however, it provides a vital function for almost all\n"
+"existing I2P applications, by providing a TCP-like\n"
+"streams over I2P, and allowing existing apps to be easily ported to I2P.\n"
+"The other end-to-end transport library for client communication is the\n"
+"datagram library."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:18
+#, python-format
+msgid ""
+"The streaming library is a layer on top of the core \n"
+"I2CP API that allows reliable, in-order, and "
+"authenticated streams\n"
+"of messages to operate across an unreliable, unordered, and "
+"unauthenticated \n"
+"message layer.  Just like the TCP to IP relationship, this streaming \n"
+"functionality has a whole series of tradeoffs and optimizations "
+"available, but\n"
+"rather than embed that functionality into the base I2P code, it has been "
+"factored\n"
+"off into its own library both to keep the TCP-esque complexities separate"
+" and to\n"
+"allow alternative optimized implementations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:29
+msgid ""
+"In consideration of the relatively high cost of messages, \n"
+"the streaming library's protocol for scheduling and delivering those "
+"messages has been optimized to\n"
+"allow individual messages passed to contain as much information as is "
+"available.\n"
+"For instance, a small HTTP transaction proxied through the streaming "
+"library can\n"
+"be completed in a single round trip - the first messages bundle a SYN, "
+"FIN, and\n"
+"the small HTTP request payload, and the reply bundles the SYN,\n"
+"FIN, ACK, and the HTTP response payload.  While an additional\n"
+"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has "
+"been\n"
+"received, the local HTTP proxy can often deliver the full response to the"
+" browser \n"
+"immediately."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:42
+msgid ""
+"The streaming library bears much resemblance to an \n"
+"abstraction of TCP, with its sliding windows, congestion control "
+"algorithms\n"
+"(both slow start and congestion avoidance), and general packet behavior "
+"(ACK,\n"
+"SYN, FIN, RST, rto calculation, etc)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:49
+msgid ""
+"The streaming library is\n"
+"a robust library\n"
+"which is optimized for operation over I2P.\n"
+"It has a one-phase setup, and\n"
+"it contains a full windowing implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:58
+msgid "API"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:60
+#, python-format
+msgid ""
+"The streaming library API provides a standard socket paradigm to Java "
+"applications.\n"
+"The lower-level I2CP API is completely hidden, "
+"except that\n"
+"applications may pass I2CP parameters "
+"through the\n"
+"streaming library, to be interpreted by I2CP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:67
+#, python-format
+msgid ""
+"The standard interface to the streaming lib is for the application to use"
+" the\n"
+"I2PSocketManagerFactory to create an\n"
+"I2PSocketManager. The application then asks "
+"the\n"
+"socket manager for an I2PSession, which will "
+"cause\n"
+"a connection to the router via I2CP. The "
+"application\n"
+"can then setup connections with an I2PSocket "
+"or\n"
+"receive connections with an I2PServerSocket."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:82
+#, python-format
+msgid "Here are the full streaming library Javadocs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:86
+msgid "For a good example of usage, see the i2psnark code."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:91
+msgid "Options and Defaults"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:92
+#, python-format
+msgid ""
+"The options and current default values are listed below.\n"
+"Options are case-sensitive and may be set for the whole router, for a "
+"particular client, or for an individual socket on a\n"
+"per-connection basis.\n"
+"Many values are tuned for HTTP performance over typical I2P conditions. "
+"Other applications such\n"
+"as peer-to-peer services are strongly encouraged to\n"
+"modify as necessary, by setting the options and passing them via the call"
+" to\n"
+"I2PSocketManagerFactory.createManager(_i2cpHost,"
+" _i2cpPort, opts).\n"
+"Time values are in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:103
+#, python-format
+msgid ""
+"Note that higher-layer APIs, such as SAM,\n"
+"BOB, and I2PTunnel,"
+"\n"
+"may override these defaults with their own defaults.\n"
+"Also note that many options only apply to servers listening for incoming "
+"connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:110
+msgid ""
+"As of release 0.9.1, most, but not all, options may be changed on an "
+"active socket manager or session.\n"
+"See the javadocs for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/protocol/i2cp.html:102
+#: i2p2www/pages/site/docs/protocol/i2cp.html:445
+msgid "Option"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/protocol/i2cp.html:106
+#: i2p2www/pages/site/docs/protocol/i2cp.html:449
+msgid "Default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:267
+#: i2p2www/pages/site/docs/how/peer-selection.html:282
+#: i2p2www/pages/site/docs/spec/common-structures.html:58
+#: i2p2www/pages/site/docs/spec/common-structures.html:203
+#: i2p2www/pages/site/docs/spec/common-structures.html:257
+#: i2p2www/pages/site/docs/spec/common-structures.html:351
+#: i2p2www/pages/site/docs/spec/common-structures.html:445
+#: i2p2www/pages/site/docs/spec/common-structures.html:553
+#: i2p2www/pages/site/docs/spec/common-structures.html:631
+#: i2p2www/pages/site/docs/spec/common-structures.html:739
+#: i2p2www/pages/site/docs/spec/datagrams.html:30
+#: i2p2www/pages/site/docs/spec/datagrams.html:89
+msgid "Notes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:119
+msgid ""
+"Comma- or space-separated list of Base64 peer Hashes used for either "
+"access list or blacklist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:121
+#: i2p2www/pages/site/docs/api/streaming.html:127
+#: i2p2www/pages/site/docs/api/streaming.html:133
+#: i2p2www/pages/site/docs/api/streaming.html:140
+#: i2p2www/pages/site/docs/api/streaming.html:152
+#: i2p2www/pages/site/docs/api/streaming.html:163
+#: i2p2www/pages/site/docs/api/streaming.html:192
+#: i2p2www/pages/site/docs/api/streaming.html:200
+#: i2p2www/pages/site/docs/api/streaming.html:220
+#: i2p2www/pages/site/docs/api/streaming.html:237
+#: i2p2www/pages/site/docs/api/streaming.html:249
+#: i2p2www/pages/site/docs/api/streaming.html:255
+#: i2p2www/pages/site/docs/api/streaming.html:261
+#: i2p2www/pages/site/docs/api/streaming.html:275
+#: i2p2www/pages/site/docs/api/streaming.html:282
+#: i2p2www/pages/site/docs/api/streaming.html:289
+#: i2p2www/pages/site/docs/api/streaming.html:314
+#: i2p2www/pages/site/docs/api/streaming.html:321
+#: i2p2www/pages/site/docs/api/streaming.html:328
+#, python-format
+msgid "As of release %(release)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:125
+msgid "Use the access list as a whitelist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:131
+msgid "Use the access list as a blacklist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:145
+msgid "Whether to respond to incoming pings"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:157
+msgid ""
+"Comma- or space-separated list of Base64 peer Hashes to be\n"
+"blacklisted for incoming connections to ALL destinations in the context.\n"
+"This option must be set in the context properties, NOT in the "
+"createManager() options argument.\n"
+"Note that setting this in the router context will not affect clients "
+"outside the\n"
+"router in a separate JVM and context."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:167
+msgid ""
+"How much transmit data (in bytes) will be accepted that hasn't been "
+"written out yet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:171
+msgid ""
+"When we're in congestion avoidance, we grow the window size at the rate\n"
+"of 1/(windowSize*factor).  In standard TCP, window sizes are"
+" in bytes,\n"
+"while in I2P, window sizes are in messages.\n"
+"A higher number means slower growth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:178
+msgid ""
+"How long to wait after instantiating a new con \n"
+"before actually attempting to connect.  If this is\n"
+"<= 0, connect immediately with no initial data.  If greater than 0, "
+"wait\n"
+"until the output stream is flushed, the buffer fills, \n"
+"or that many milliseconds pass, and include any initial data with the SYN."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:186
+msgid ""
+"How long to block on connect, in milliseconds. Negative means "
+"indefinitely. Default is 5 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:190
+msgid ""
+"Whether to disable warnings in the logs when an incoming connection is "
+"rejected due to connection limits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:196
+msgid ""
+"Whether to listen only for the streaming protocol.\n"
+"Setting to true will prohibit communication with Destinations earlier "
+"than release 0.7.1\n"
+"(released March 2009). Set to true if running multiple protocols on this "
+"Destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:204
+msgid ""
+"(0=noop, 1=disconnect)\n"
+"What to do on an inactivity timeout - do nothing, disconnect, or send a "
+"duplicate ack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:212
+msgid ""
+"The initial value of the resend delay field in the packet header, times "
+"1000.\n"
+"Not fully implemented; see below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:217
+msgid ""
+"Initial timeout\n"
+"(if no sharing data available)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:224
+msgid ""
+"Initial round trip time estimate\n"
+"(if no sharing data available).\n"
+"Disabled as of release 0.9.8; uses actual RTT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
+msgid "if no sharing data available"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
+msgid ""
+"In standard TCP, window sizes are in bytes, while in I2P, window sizes "
+"are in messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:242
+msgid ""
+"(0 or negative value means unlimited)\n"
+"This is a total limit for incoming and outgoing combined."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:247
+msgid "Incoming connection limit (per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:253
+#: i2p2www/pages/site/docs/api/streaming.html:259
+msgid "(per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:265
+msgid "The MTU in bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:269
+msgid "Maximum number of retransmissions before failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:273
+msgid "Incoming connection limit (all peers; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:279
+#: i2p2www/pages/site/docs/api/streaming.html:286
+msgid ""
+"(all peers; 0 means disabled)\n"
+"Use with caution as exceeding this will disable a server for a long time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:295
+msgid ""
+"(2=interactive not supported)\n"
+"This doesn't currently do anything, but setting it to a value other than "
+"1 will cause an error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:300
+msgid "How long to block on read, in milliseconds. Negative means indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:304
+msgid ""
+"When we're in slow start, we grow the window size at the rate\n"
+"of 1/(factor).  In standard TCP, window sizes are in bytes,\n"
+"while in I2P, window sizes are in messages.\n"
+"A higher number means slower growth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:311
+#: i2p2www/pages/site/docs/api/streaming.html:318
+#: i2p2www/pages/site/docs/api/streaming.html:325
+msgid ""
+"Ref: RFC 2140. Floating point value.\n"
+"May be set only via context properties, not connection options."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:332
+msgid ""
+"How long to block on write/flush, in milliseconds. Negative means "
+"indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:340
+#: i2p2www/pages/site/docs/spec/streaming.html:10
+msgid "Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:342
+msgid "See the Streaming Library Specification page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:346
+msgid "Implementation Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:348
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:349
+msgid ""
+"The initiator sends a packet with the SYNCHRONIZE flag set. This packet "
+"may contain the initial data as well.\n"
+"The peer replies with a packet with the SYNCHRONIZE flag set. This packet"
+" may contain the initial response data as well."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:354
+msgid ""
+"The initiator may send additional data packets, up to the initial window "
+"size, before receiving the SYNCHRONIZE response.\n"
+"These packets will also have the send Stream ID field set to 0.\n"
+"Recipients must buffer packets received on unknown streams for a short "
+"period of time, as they may\n"
+"arrive out of order, in advance of the SYNCHRONIZE packet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:361
+msgid "MTU Selection and Negotiation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:362
+msgid ""
+"The maximum message size (also called the MTU / MRU) is negotiated to the"
+" lower value supported by\n"
+"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection"
+" will lead to\n"
+"a large amount of overhead.\n"
+"The MTU is specified by the option i2p.streaming.maxMessageSize.\n"
+"The current default MTU of 1730 was chosen to fit precisely into two 1K "
+"I2NP tunnel messages,\n"
+"including overhead for the typical case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:371
+msgid ""
+"The first message in a connection includes a 387 byte (typical) "
+"Destination added by the streaming layer,\n"
+"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in "
+"the Garlic message by the router.\n"
+"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session "
+"was previously established).\n"
+"Therefore, the goal of fitting a complete HTTP request in a single 1KB "
+"I2NP message is not always attainable.\n"
+"However, the selection of the MTU, together with careful implementation "
+"of fragmentation\n"
+"and batching strategies in the tunnel gateway processor, are important "
+"factors in network bandwidth,\n"
+"latency, reliability, and efficiency, especially for long-lived "
+"connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:382
+#, python-format
+msgid ""
+"Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
+"the I2CP layer.\n"
+"There is no checksum field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:390
+#, python-format
+msgid ""
+"Each packet is sent through I2P as a single message (or as an individual "
+"clove in a\n"
+"Garlic Message). Message encapsulation "
+"is implemented\n"
+"in the underlying I2CP, I2NP, and\n"
+"tunnel message layers. There is no "
+"packet delimiter\n"
+"mechanism or payload length field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:400
+msgid "Windowing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:401
+msgid ""
+"The streaming lib uses standard slow-start (exponential window growth) "
+"and congestion avoidance (linear window growth)\n"
+"phases, with exponential backoff.\n"
+"Windowing and acknowledgments use packet count, not byte count."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:408
+msgid "Close"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:409
+msgid ""
+"Any packet, including one with the SYNCHRONIZE flag set, may have the "
+"CLOSE flag sent as well.\n"
+"The connection is not closed until the peer responds with the CLOSE flag."
+"\n"
+"CLOSE packets may contain data as well."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:417
+msgid ""
+"There is no ping function at the I2CP layer (equivalent to ICMP echo) or "
+"in datagrams.\n"
+"This function is provided in streaming.\n"
+"Pings and pongs may not be combined with a standard streaming packet;\n"
+"if the ECHO option is set, then\n"
+"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. "
+"are ignored."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:425
+msgid ""
+"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED "
+"flags set.\n"
+"The sendStreamId must be greater than zero, and the receiveStreamId is "
+"ignored.\n"
+"The sendStreamId may or may not correspond to an existing connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:431
+msgid ""
+"A pong packet must have the ECHO flag set.\n"
+"The sendStreamId must be zero, and the receiveStreamId is the "
+"sendStreamId from the ping.\n"
+"The pong packet does not include any payload that was contained in the "
+"ping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:437
+msgid ""
+"Streaming may be configured to disable sending pongs with the "
+"configuration i2p.streaming.answerPings=false."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:442
+msgid "Control Block Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:443
+msgid ""
+"The streaming lib supports \"TCP\" Control Block sharing.\n"
+"This shares three important streaming lib parameters\n"
+"(window size, round trip time, round trip time variance)\n"
+"across connections to the same remote peer.\n"
+"This is used for \"temporal\" sharing at connection open/close time,\n"
+"not \"ensemble\" sharing during a connection (See\n"
+"RFC 2140).\n"
+"There is a separate share per ConnectionManager (i.e. per local "
+"Destination)\n"
+"so that there is no information leakage to other Destinations on the\n"
+"same router.\n"
+"The share data for a given peer expires after a few minutes.\n"
+"The following Control Block Sharing parameters can be set per router:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:464
+msgid "Other Parameters"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:465
+msgid ""
+"The following parameters are hardcoded, but may be of interest for "
+"analysis:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:484
+#: i2p2www/pages/site/docs/how/network-database.html:843
+msgid "History"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:485
+msgid ""
+"The streaming library has grown organically for I2P - first mihi "
+"implemented the\n"
+"\"mini streaming library\" as part of I2PTunnel, which was limited to a "
+"window\n"
+"size of 1 message (requiring an ACK before sending the next one), and "
+"then it was\n"
+"refactored out into a generic streaming interface (mirroring TCP sockets)"
+" and the\n"
+"full streaming implementation was deployed with a sliding window protocol"
+" and \n"
+"optimizations to take into account the high bandwidth x delay product.  "
+"Individual\n"
+"streams may adjust the maximum packet size and other options. The default"
+"\n"
+"message size is selected to fit precisely in two 1K I2NP tunnel messages,"
+"\n"
+"and is a reasonable tradeoff between the bandwidth costs of \n"
+"retransmitting lost messages, and the latency and overhead of multiple "
+"messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:499
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:331
+#: i2p2www/pages/site/docs/how/garlic-routing.html:242
+#: i2p2www/pages/site/docs/how/network-database.html:848
+#: i2p2www/pages/site/docs/how/peer-selection.html:265
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:255
+#: i2p2www/pages/site/docs/protocol/i2cp.html:654
+#: i2p2www/pages/site/docs/protocol/i2np.html:227
+#: i2p2www/pages/site/docs/spec/updates.html:280
+#: i2p2www/pages/site/docs/transport/ntcp.html:446
+#: i2p2www/pages/site/docs/transport/ssu.html:506
+#: i2p2www/pages/site/docs/tunnels/implementation.html:503
+msgid "Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:500
+msgid ""
+"The behavior of the streaming library has a profound impact on\n"
+"application-level performance, and as such, is an important\n"
+"area for further analysis."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:506
+msgid "Additional tuning of the streaming lib parameters may be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:509
+#, python-format
+msgid ""
+"Another area for research is the interaction of the streaming lib with "
+"the\n"
+"NTCP and SSU transport layers.\n"
+"See the NTCP discussion page for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:514
+msgid ""
+"The interaction of the routing algorithms with the streaming lib strongly"
+" affects performance.\n"
+"In particular, random distribution of messages to multiple tunnels in a "
+"pool\n"
+"leads to a high degree of out-of-order delivery which results in smaller "
+"window\n"
+"sizes than would otherwise be the case. The router currently routes \n"
+"messages for a single from/to destination pair through a consistent set \n"
+"of tunnels, until tunnel expiration or delivery failure. The router's \n"
+"failure and tunnel selection algorithms should be reviewed for possible \n"
+"improvements."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:524
+msgid "The data in the first SYN packet may exceed the receiver's MTU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:527
+msgid "The DELAY_REQUESTED field could be used more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:530
+msgid ""
+"Duplicate initial SYNCHRONIZE packets on short-lived streams may not be "
+"recognized and removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:533
+msgid "Don't send the MTU in a retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:536
+msgid ""
+"Data is sent along unless the outbound window is full.\n"
+"(i.e. no-Nagle or TCP_NODELAY)\n"
+"Probably should have a configuration option for this."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:541
+msgid ""
+"zzz has added debug code to the streaming library to log packets in a "
+"wireshark-compatible\n"
+"(pcap) format; Use this to further analyze performance.\n"
+"The format may require enhancement to map more streaming lib parameters "
+"to TCP fields."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:546
+msgid ""
+"There are proposals to replace the streaming lib with standard TCP\n"
+"(or perhaps a null layer together with raw sockets).\n"
+"This would unfortunately be incompatible with the streaming lib\n"
+"but it would be good to compare the performance of the two."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:3
+#: i2p2www/pages/site/docs/spec/configuration.html:3
+msgid "September 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:7
+msgid ""
+"There are several bittorrent clients and trackers on I2P.\n"
+"As I2P addressing uses a Destination instead of an IP and port, minor\n"
+"changes are required to tracker and client software for operation on I2P."
+"\n"
+"These changes are specified below.\n"
+"Note carefully the guidelines for compatibility with older I2P clients "
+"and trackers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:15
+msgid ""
+"This page specifies protocol details common to all clients and trackers.\n"
+"Specific clients and trackers may implement other unique features or "
+"protocols."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:20
+msgid "We welcome additional ports of client and tracker software to I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:26
+msgid "Announces"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:27
+msgid ""
+"Clients generally include a fake port=6881 parameter in the announce, for"
+" compatibility with older trackers.\n"
+"Trackers may ignore the port parameter, and should not require it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:32
+#, python-format
+msgid ""
+"The ip parameter is the base 64 of the client's\n"
+"Destination,\n"
+"using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n"
+"Destinations\n"
+"are 387+ bytes, so the Base 64 is 516+ bytes.\n"
+"Clients generally append \".i2p\" to the Base 64 Destination for "
+"compatibility with older trackers.\n"
+"Trackers should not require an appended \".i2p\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:42
+msgid "Other parameters are the same as in standard bittorrent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:46
+msgid ""
+"While all current Destinations for clients are exactly 387 bytes, a "
+"tracker should not\n"
+"presume that will always be so. A reasonable maximum to assume, for now, "
+"is 475 bytes.\n"
+"As the tracker must decode the Base64 to deliver compact responses (see "
+"below),\n"
+"the tracker should probably decode and reject bad Base64 when announced."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:53
+msgid ""
+"The default response type is non-compact. Clients may request a compact "
+"response with\n"
+"the parameter compact=1. A tracker may, but is not required to, return\n"
+"a compact response when requested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:59
+msgid ""
+"Developers of new I2P clients\n"
+"are strongly encouraged to implemenent announces over their own tunnel "
+"rather than\n"
+"the HTTP client proxy at port 4444. Doing so is both more efficient and "
+"it allows\n"
+"destination enforcement by the tracker (see below)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:66
+msgid ""
+"There are no known I2P clients or trackers that currently support UDP "
+"announce/responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:71
+msgid "Non-Compact Tracker Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:72
+msgid ""
+"The non-compact response is just as in standard bittorrent, with an I2P "
+"\"ip\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:76
+msgid ""
+"Trackers generally include a fake port key, or use the port from the "
+"announce, for compatibility with older clients.\n"
+"Clients must ignore the port parameter, and should not require it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:81
+#, python-format
+msgid ""
+"The value of the ip key is the base 64 of the client's\n"
+"Destination, as "
+"described above.\n"
+"Trackers generally append \".i2p\" to the Base 64 Destination if it "
+"wasn't in the announce ip, for compatibility with older clients.\n"
+"Clients should not require an appended \".i2p\" in the responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:88
+msgid "Other response keys and values are the same as in standard bittorrent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:94
+msgid "Compact Tracker Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:95
+#, python-format
+msgid ""
+"In the compact response, the value of the \"peers\" dictionary key is a "
+"single byte string,\n"
+"whose length is a multiple of 32 bytes.\n"
+"This string contains the concatenated\n"
+"32-byte SHA-256 Hashes\n"
+"of the binary\n"
+"Destinations\n"
+"of the peers.\n"
+"This hash must be computed by the tracker, unless destination enforcement"
+"\n"
+"(see below) is used, in which case the hash delivered in the X-I2P-"
+"DestHash\n"
+"or X-I2P-DestB32 HTTP headers may be converted to binary and stored.\n"
+"The peers key may be absent, or the peers value may be zero-length."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:109
+msgid ""
+"While compact response support is optional for both clients and trackers,"
+" it is highly\n"
+"recommended as it reduces the nominal response size by over 90%."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:116
+msgid "Destination Enforcement"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:117
+#, python-format
+msgid ""
+"Some, but not all, I2P bittorrent clients announce over their own "
+"tunnels.\n"
+"Trackers may choose to prevent spoofing by requiring this, and verifying "
+"the\n"
+"client's\n"
+"Destination\n"
+"using HTTP headers added by the I2PTunnel HTTP Server tunnel.\n"
+"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which "
+"are\n"
+"different formats for the same information.\n"
+"These headers cannot be spoofed by the client.\n"
+"A tracker enforcing destinations need not require the ip announce "
+"parameter at all."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:129
+msgid ""
+"As several clients use the HTTP proxy instead of their own tunnel for "
+"announces,\n"
+"destination enforcement will prevent usage by those clients unless or "
+"until\n"
+"those clients are converted to announcing over their own tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:135
+msgid ""
+"Unfortunately, as the network grows, so will the amount of maliciousness,"
+"\n"
+"so we expect that all trackers will eventually enforce destinations.\n"
+"Both tracker and client developers should anticipate it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:143
+msgid "Announce Host Names"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:144
+#, python-format
+msgid ""
+"Announce URL host names in torrent files generally follow the\n"
+"I2P naming standards.\n"
+"In addition to host names from address books and \".b32.i2p\" Base 32 "
+"hostnames,\n"
+"the full Base 64 Destination (with [or without?] \".i2p\" appended) "
+"should be supported.\n"
+"Non-open trackers should recognize their own host name in any of these "
+"formats."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:152
+msgid ""
+"To preserve anonymity,\n"
+"clients should generally ignore non-I2P announce URLs in torrent files."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:159
+msgid "Client Connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:160
+msgid ""
+"Client-to-client connections use the standard protocol over TCP.\n"
+"There are no known I2P clients that currently support uTP communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:165
+#, python-format
+msgid ""
+"I2P uses 387+ byte Destinations\n"
+"for addresses, as explained above."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:170
+msgid ""
+"If the client has only the hash of the destination (such as from a "
+"compact response or PEX), it must perform a lookup\n"
+"by encoding it with Base 32, appending \".b32.i2p\", and querying the "
+"Naming Service,\n"
+"which will return the full Destination if available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:176
+msgid ""
+"If the client has a peer's full Destination it received in a non-compact "
+"response, it should use it\n"
+"directly in the connection setup.\n"
+"Do not convert a Destination back to a Base 32 hash for lookup, this is "
+"quite inefficient."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:183
+msgid "Cross-Network Prevention"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:184
+msgid ""
+"To preserve anonymity,\n"
+"I2P bittorrent clients generally do not support non-I2P announces or peer"
+" connections.\n"
+"I2P HTTP outproxies often block announces.\n"
+"There are no known SOCKS outproxies supporting bittorrent traffic."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:191
+msgid ""
+"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers "
+"often\n"
+"block accesses or announces that contain an X-Forwarded-For HTTP header.\n"
+"Trackers should reject standard network announces with IPv4 or IPv6 IPs, "
+"and not deliver them in responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:200
+#, python-format
+msgid ""
+"I2P PEX is based on ut_pex.\n"
+"As there does not appear to be a formal specification of ut_pex "
+"available,\n"
+"it may be necessary to review the libtorrent source for assistance.\n"
+"It is an extension message, identified as \"i2p_pex\" in\n"
+"the extension "
+"handshake.\n"
+"It contains a bencoded dictionary with up to 3 keys, \"added\", "
+"\"added.f\", and \"dropped\".\n"
+"The added and dropped values are each a single byte string, whose length "
+"is a multiple of 32 bytes.\n"
+"These byte strings are the concatenated SHA-256 Hashes of the binary\n"
+"Destinations\n"
+"of the peers.\n"
+"This is the same format as the peers dictionary value in the i2p compact "
+"response format specified above.\n"
+"The added.f value, if present, is the same as in ut_pex."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:218
+msgid ""
+"DHT support is included in the i2psnark client as of version 0.9.2.\n"
+"Preliminary differences from\n"
+"BEP 5\n"
+"are described below, and are subject to change.\n"
+"Contact the I2P developers if you wish to develop a client supporting DHT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:226
+msgid ""
+"Unlike standard DHT, I2P DHT does not use a bit in the options handshake,"
+" or the PORT message.\n"
+"It is advertised with an extension message, identified as \"i2p_dht\" in\n"
+"the extension "
+"handshake.\n"
+"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", "
+"both integers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:233
+msgid ""
+"The UDP (datagram) port listed in the compact node info is used\n"
+"to receive repliable (signed) datagrams.\n"
+"This is used for queries, except for announces.\n"
+"We call this the \"query port\".\n"
+"This is the \"port\" value from the extension message.\n"
+"Queries use I2CP protocol number 17."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:242
+msgid ""
+"In addition to that UDP port, we use a second datagram\n"
+"port equal to the query port + 1. This is used to receive\n"
+"unsigned (raw) datagrams for replies, errors, and announces.\n"
+"This port provides increased efficiency since replies\n"
+"contain tokens sent in the query, and need not be signed.\n"
+"We call this the \"response port\".\n"
+"This is the \"rport\" value from the extension message.\n"
+"It must be 1 + the query port.\n"
+"Responses and announces use I2CP protocol number 18."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:254
+msgid ""
+"Compact peer info is 32 bytes (32 byte SHA256 Hash)\n"
+"instead of 4 byte IP + 2 byte port. There is no peer port.\n"
+"In a response, the \"values\" key is a list of strings, each containing a"
+" single compact peer info."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:260
+msgid ""
+"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + "
+"2 byte port)\n"
+"instead of 20 byte SHA1 Hash + 4 byte IP + 2 byte port.\n"
+"In a response, the \"nodes\" key is a\n"
+"single byte string with concatenated compact node info."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:267
+msgid ""
+"Secure node ID requirement: To make various DHT attacks more difficult,\n"
+"the first 4 bytes of the Node ID must match the first 4 bytes of the "
+"destination Hash,\n"
+"and the next two bytes of the Node ID must match the next two bytes of "
+"the\n"
+"destination hash exclusive-ORed with the port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:274
+msgid ""
+"In a torrent file,\n"
+"the trackerless torrent dictionary \"nodes\" key is TBD.\n"
+"It could be a list of\n"
+"32 byte binary strings (SHA256 Hashes) instead of a list of lists\n"
+"containing a host string and a port integer.\n"
+"Alternatives: A single byte string with concatenated hashes,\n"
+"or a list of strings alone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:285
+#: i2p2www/pages/site/docs/how/intro.html:187
+msgid "Additional Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:287
+#, python-format
+msgid ""
+"I2P bittorrent standards are generally discussed on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:290
+#, python-format
+msgid ""
+"A chart of current tracker software capabilities is also available there."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:293
+#, python-format
+msgid ""
+"The\n"
+"I2P bittorrent FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:297
+#, python-format
+msgid "DHT on I2P discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:2
+#: i2p2www/pages/site/docs/applications/supported.html:5
+msgid "Supported Applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:9
+#: i2p2www/pages/site/docs/applications/supported.html:186
+msgid "Blogging, Forums, and Wikis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:11
+#: i2p2www/pages/site/docs/applications/supported.html:232
+msgid "Decentralized File Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:14
+#: i2p2www/pages/site/docs/applications/supported.html:244
+msgid "Development Tools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:17
+#: i2p2www/pages/site/docs/applications/supported.html:246
+msgid "Version control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:21
+#: i2p2www/pages/site/docs/applications/supported.html:265
+msgid "Domain Naming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:23
+#: i2p2www/pages/site/docs/applications/supported.html:283
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:26
+#: i2p2www/pages/site/docs/applications/supported.html:328
+msgid "File Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:29
+#: i2p2www/pages/site/docs/applications/supported.html:330
+msgid "BitTorrent clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:31
+#: i2p2www/pages/site/docs/applications/supported.html:372
+msgid "BitTorrent trackers and indexers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:40
+#: i2p2www/pages/site/docs/applications/supported.html:439
+msgid "Network Administration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:43
+#: i2p2www/pages/site/docs/applications/supported.html:441
+msgid "General-purpose socket utilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:50
+#: i2p2www/pages/site/docs/applications/supported.html:482
+msgid "Real-time Chat"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:53
+#: i2p2www/pages/site/docs/applications/supported.html:484
+msgid "Instant messaging clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:55
+#: i2p2www/pages/site/docs/applications/supported.html:494
+msgid "IRC clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:57
+#: i2p2www/pages/site/docs/applications/supported.html:545
+msgid "IRC servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:62
+#: i2p2www/pages/site/docs/applications/supported.html:561
+msgid "Web Browsing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:65
+#: i2p2www/pages/site/docs/applications/supported.html:563
+msgid "Anonymous websites"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:67
+#: i2p2www/pages/site/docs/applications/supported.html:612
+msgid "Proxy software"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:69
+#: i2p2www/pages/site/docs/applications/supported.html:637
+msgid "Inproxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:71
+#: i2p2www/pages/site/docs/applications/supported.html:669
+msgid "Outproxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:76
+#: i2p2www/pages/site/docs/applications/supported.html:683
+msgid "Website Hosting"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:79
+#: i2p2www/pages/site/docs/applications/supported.html:698
+msgid "Web servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:85
+#, python-format
+msgid ""
+"This is intended to be a comprehensive listing of applications used with\n"
+"I2P. If you know of something that's missing please submit a ticket on\n"
+"Trac, and be sure to select the\n"
+"“www” component in the submission form."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:92
+msgid ""
+"\n"
+"Supported applications are tagged with one or more of the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:97
+#: i2p2www/pages/site/docs/applications/supported.html:279
+#: i2p2www/pages/site/docs/applications/supported.html:311
+#: i2p2www/pages/site/docs/applications/supported.html:336
+#: i2p2www/pages/site/docs/applications/supported.html:695
+msgid "bundled"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:100
+msgid ""
+"Bundled application — I2P ships with a few officially\n"
+"supported applications that let new users take immediate advantage of\n"
+"some of I2P's more useful capabilities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:107
+#: i2p2www/pages/site/docs/applications/supported.html:195
+#: i2p2www/pages/site/docs/applications/supported.html:208
+#: i2p2www/pages/site/docs/applications/supported.html:220
+#: i2p2www/pages/site/docs/applications/supported.html:228
+#: i2p2www/pages/site/docs/applications/supported.html:241
+#: i2p2www/pages/site/docs/applications/supported.html:292
+#: i2p2www/pages/site/docs/applications/supported.html:404
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:523
+msgid "plugin"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:110
+#, python-format
+msgid ""
+"Third-party plugin — I2P's plugin system provides convenient\n"
+"deployment of I2P-enabled applications and allows tighter integration\n"
+"with the router. Plugins are [reviewed by the community](http://%(plugins)s) to identify security and\n"
+"anonymity issues."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:121
+#: i2p2www/pages/site/docs/applications/supported.html:220
+#: i2p2www/pages/site/docs/applications/supported.html:228
+#: i2p2www/pages/site/docs/applications/supported.html:241
+#: i2p2www/pages/site/docs/applications/supported.html:252
+#: i2p2www/pages/site/docs/applications/supported.html:261
+#: i2p2www/pages/site/docs/applications/supported.html:324
+#: i2p2www/pages/site/docs/applications/supported.html:342
+#: i2p2www/pages/site/docs/applications/supported.html:353
+#: i2p2www/pages/site/docs/applications/supported.html:368
+#: i2p2www/pages/site/docs/applications/supported.html:414
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:450
+#: i2p2www/pages/site/docs/applications/supported.html:456
+#: i2p2www/pages/site/docs/applications/supported.html:462
+#: i2p2www/pages/site/docs/applications/supported.html:472
+#: i2p2www/pages/site/docs/applications/supported.html:478
+#: i2p2www/pages/site/docs/applications/supported.html:490
+#: i2p2www/pages/site/docs/applications/supported.html:523
+#: i2p2www/pages/site/docs/applications/supported.html:529
+#: i2p2www/pages/site/docs/applications/supported.html:535
+#: i2p2www/pages/site/docs/applications/supported.html:541
+#: i2p2www/pages/site/docs/applications/supported.html:618
+#: i2p2www/pages/site/docs/applications/supported.html:627
+#: i2p2www/pages/site/docs/applications/supported.html:633
+#: i2p2www/pages/site/docs/applications/supported.html:695
+#: i2p2www/pages/site/docs/applications/supported.html:710
+#: i2p2www/pages/site/docs/applications/supported.html:716
+#: i2p2www/pages/site/docs/applications/supported.html:722
+#: i2p2www/pages/site/docs/applications/supported.html:728
+msgid "standalone"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:121
+#: i2p2www/pages/site/docs/applications/supported.html:195
+#: i2p2www/pages/site/docs/applications/supported.html:202
+#: i2p2www/pages/site/docs/applications/supported.html:208
+#: i2p2www/pages/site/docs/applications/supported.html:214
+#: i2p2www/pages/site/docs/applications/supported.html:362
+#: i2p2www/pages/site/docs/applications/supported.html:386
+#: i2p2www/pages/site/docs/applications/supported.html:395
+#: i2p2www/pages/site/docs/applications/supported.html:551
+#: i2p2www/pages/site/docs/applications/supported.html:557
+msgid "standalone/mod"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:124
+msgid ""
+"Third-party standalone application — Many standard network\n"
+"applications only require careful setup and configuration to communicate\n"
+"anonymously over I2P. These are tagged with standalone. Some\n"
+"applications, tagged with standalone/mod, require patching to\n"
+"function properly over I2P or to prevent inadvertent disclosure of\n"
+"identifying information such as the user's hostname or external IP\n"
+"address."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:135
+#: i2p2www/pages/site/docs/applications/supported.html:302
+#: i2p2www/pages/site/docs/applications/supported.html:571
+#: i2p2www/pages/site/docs/applications/supported.html:581
+#: i2p2www/pages/site/docs/applications/supported.html:590
+#: i2p2www/pages/site/docs/applications/supported.html:596
+#: i2p2www/pages/site/docs/applications/supported.html:602
+#: i2p2www/pages/site/docs/applications/supported.html:608
+#: i2p2www/pages/site/docs/applications/supported.html:649
+#: i2p2www/pages/site/docs/applications/supported.html:657
+#: i2p2www/pages/site/docs/applications/supported.html:665
+#: i2p2www/pages/site/docs/applications/supported.html:679
+msgid "service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:138
+msgid ""
+"Third-party essential network service — Services which on\n"
+"the I2P network are analogous to those provided on the public Internet\n"
+"by hosting providers, ISPs, and Google: eepsite indexes and jump\n"
+"services, search engines, email, DNS-style name services, hosting,\n"
+"proxies, etc. These services focus on boosting the usefulness of the\n"
+"network as a whole, and making network content more discoverable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:148
+#: i2p2www/pages/site/docs/applications/supported.html:220
+#: i2p2www/pages/site/docs/applications/supported.html:368
+msgid "unmaintained"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:151
+msgid ""
+"Unmaintained — This is used to tag plugins, applications,\n"
+"and services which appear to be unmaintained and may be removed from\n"
+"this listing in the future."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:159
+#, python-format
+msgid ""
+"Warning: Using an application, plugin, or service with I2P\n"
+"doesn't automatically protect your anonymity. I2P is merely a set of "
+"tools\n"
+"which can help you mitigate certain identified\n"
+"threats to anonymity. We do not and cannot make any guarantees about "
+"the\n"
+"safety of the applications, plugins, and services listed below. Most\n"
+"applications and plugins must be properly configured, and some will need "
+"to\n"
+"be patched — and even then your anonymity might not be assured. "
+"Similarly,\n"
+"services could put your anonymity at risk, either by design or through\n"
+"carelessness on their part or your own."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:171
+msgid ""
+"If you have doubts about the suitability of an application,\n"
+"plugin, or service for use with I2P, you are urged to inquire about "
+"privacy\n"
+"issues with its maintainers, to search its mailing lists and bug tracker "
+"if\n"
+"one exists, and consult trusted, knowledgeable members of the I2P\n"
+"community."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:179
+msgid ""
+"Take responsibility for your own anonymity and safety — always\n"
+"seek expert advice, educate yourself, practice good judgment, be mindful "
+"of\n"
+"disclosing personally identifying information, and don't take\n"
+"shortcuts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:201
+msgid "Lightweight forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:207
+msgid "Another lightweight blogging platform."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:213
+msgid "Most popular open source forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:219
+msgid "Distributed forums software, originally developed by jrandom."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:224
+#, python-format
+msgid ""
+"A Java-based MediaWiki clone. No external database needed.\n"
+"Plugin available here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:236
+#, python-format
+msgid ""
+"Port of the Tahoe-"
+"LAFS\n"
+"distributed file system to the I2P network. Controller plugin here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:251
+msgid "Most popular distributed version control system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:257
+#, python-format
+msgid ""
+"Another distributed version control system. Currently\n"
+"used in I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:269
+#, python-format
+msgid ""
+"Provides management of addressbooks, which are part of a simple,\n"
+"user-controlled I2P naming system somewhat\n"
+"analogous to the Internet's Domain Name System (DNS). Addressbooks map\n"
+"Base64 destinations to short, usually human-readable “domain” names "
+"ending\n"
+"with a .i2p suffix which the I2P router's HTTP client can resolve back to"
+"\n"
+"Base64 addresses. (Note: While Base64 destinations are globally\n"
+"unique, addressbook “domain” names only resolve to unique destinations\n"
+"locally.)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:288
+msgid ""
+"Serverless peer-to-peer email application using a distributed hash table\n"
+"(DHT) for secure mail storage."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:297
+msgid ""
+"Provides email service within the I2P network via @mail.i2p addresses,\n"
+"and email gateway service between the I2P network and the public Internet"
+"\n"
+"via @i2pmail.org addresses. One of the oldest continuous services on I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:307
+msgid ""
+"Simple web browser-based email interface. Configured to use Postman's\n"
+"email service by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:316
+#, python-format
+msgid ""
+"Can be configured to use Postman's email service. See\n"
+"this comparison of MUAs,\n"
+"and configuration settings for\n"
+"SMTP and POP3."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:335
+msgid "I2P's integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:341
+msgid "Modified version of I2PSnark."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:347
+msgid ""
+"\n"
+"A fork of rufus that uses the Basic Open Bridge (BOB) and has many\n"
+"improvements, including using the latest wxwidgets and python. It also\n"
+"supports use of seedless if installed for trackerless torrents and\n"
+"magnet-link like fetching of torrents within I2P.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:358
+msgid ""
+"Clean, full-featured cross-platform BitTorrent client with official\n"
+"ports for several GUI toolkits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:367
+msgid "Has a plugin providing I2P support."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:374
+#, python-format
+msgid ""
+"For a detailed feature comparison of I2P-enabled trackers/indexers, see\n"
+"here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:382
+msgid ""
+"The code that powered one of the first major tracker/indexer sites on the"
+"\n"
+"Internet. Patched for I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:391
+#, python-format
+msgid ""
+"Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n"
+"branch of the I2P Monotone repository."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:400
+#, python-format
+msgid ""
+"zzz's Java-based open tracker. More info\n"
+"here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:413
+msgid "I2P port of the aMule ED2K client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:422
+#, python-format
+msgid ""
+"Port of the Phex Gnutella "
+"client. Website\n"
+"for plugin version here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:431
+#, python-format
+msgid ""
+"Cache for Gnutella peers on I2P. Website for plugin version\n"
+"here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:446
+msgid ""
+"Unix standard tool for socket relaying. Several clones, ports, and forks\n"
+"have appeared over the years."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:455
+msgid "Like netcat but more powerful."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:461
+msgid ""
+"Proxy providing simple, transparent SOCKS-ification of network "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:471
+msgid ""
+"Most popular implementation of the Secure Shell (SSH) protocol and "
+"related tools."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:477
+msgid "Open source Secure Shell (SSH) client for Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:489
+msgid "IM client with multiple incarnations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:496
+msgid ""
+"Many IRC clients leak identifying information to servers or other\n"
+"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound"
+"\n"
+"and outbound messages to scrub data such as LAN IP addresses, external IP"
+"\n"
+"addresses, local hostnames, and the name and version of the IRC client. "
+"Two\n"
+"message types in particular, DCC and CTCP, can't be sufficiently "
+"anonymized\n"
+"without changes to the protocols or to IRC client/server code, so they "
+"are\n"
+"completely blocked, except for CTCP ACTION (the message emitted by the\n"
+"/me command) which isn't inherently dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:507
+msgid ""
+"I2P's IRC filtering may not cover every possible leak — users should also"
+"\n"
+"check if their client is sending their real name or local username. "
+"Packet\n"
+"sniffers such as Wireshark are\n"
+"useful here. Eliminating remaining leaks may be as simple as changing the"
+"\n"
+"client's default configuration. If that doesn't help, inform the I2P\n"
+"developers; they may be able to solve it via additional filtering."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:519
+#, python-format
+msgid ""
+"Small Java-based IRC client. Plugin available here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:528
+msgid "Cross-platform graphical IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:534
+msgid "Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:540
+msgid "Another Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:550
+msgid "IRC server developed from scratch."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:556
+msgid "Most popular IRC server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:568
+msgid ""
+"Any website hosted anonymously on I2P, reachable through the I2P router's"
+" HTTP proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:576
+msgid ""
+"Distributed anonymous websites hosted\n"
+"using Tahoe-LAFS-I2P, currently only reachable with Tahoe-LAFS-I2P\n"
+"clients or through the Tahoe-LAFS-I2P HTTP proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:586
+#, python-format
+msgid ""
+"Website for sponge's jump service.\n"
+"Source code available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:595
+msgid "Another jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:601
+msgid "Dynamically updated eepsite index."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:607
+#, python-format
+msgid "Website for zzz's jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:617
+msgid "SOCKS-enabled caching web proxy with basic filtering capabilities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:623
+msgid ""
+"Privacy-focused non-caching web proxy with advanced filtering\n"
+"capabilities. Excels at removing ads and other junk."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:632
+msgid "Venerable caching web proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:639
+msgid "Gateways allowing users on the public Internet to access eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:646
+#, python-format
+msgid "tino's inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:654
+#: i2p2www/pages/site/docs/applications/supported.html:662
+msgid "Another inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:671
+msgid ""
+"Gateways allowing I2P users to access content hosted on the public "
+"Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:678
+msgid "Publicly advertised outproxy running Squid, located in Germany."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:688
+msgid ""
+"Lightweight web server and Java servlet container. I2P is tightly\n"
+"integrated with a bundled copy of Jetty which by default is configured to"
+"\n"
+"host the user's eepsite. The "
+"bundled\n"
+"Jetty also serves the I2P router console and web applications bundled "
+"with\n"
+"I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:700
+msgid ""
+"In addition to Jetty, any web server should function over I2P without\n"
+"modification so long as it's HTTP-compliant. Some web servers known to\n"
+"currently serve content on the I2P network are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:709
+msgid "Most popular web server on the public WWW."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:715
+msgid "Web server and Java servlet container. More features than Jetty."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:721
+msgid "Fast lightweight web server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:727
+msgid "High-performance lightweight web server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:2
+msgid "Naming discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:4
+#, python-format
+msgid ""
+"NOTE: The following is a discussion of the reasons behind the I2P naming "
+"system,\n"
+"common arguments and possible alternatives.\n"
+"See the naming page for current documentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:10
+msgid "Discarded alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:12
+msgid ""
+"Naming within I2P has been an oft-debated topic since the very beginning "
+"with\n"
+"advocates across the spectrum of possibilities.  However, given I2P's "
+"inherent\n"
+"demand for secure communication and decentralized operation, the "
+"traditional\n"
+"DNS-style naming system is clearly out, as are \"majority rules\" voting "
+"systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:19
+msgid ""
+"I2P does not promote the use of DNS-like services though, as the damage "
+"done\n"
+"by hijacking a site can be tremendous - and insecure destinations have no"
+"\n"
+"value.  DNSsec itself still falls back on registrars and certificate "
+"authorities,\n"
+"while with I2P, requests sent to a destination cannot be intercepted or "
+"the reply\n"
+"spoofed, as they are encrypted to the destination's public keys, and a "
+"destination\n"
+"itself is just a pair of public keys and a certificate.  DNS-style "
+"systems on the\n"
+"other hand allow any of the name servers on the lookup path to mount "
+"simple denial\n"
+"of service and spoofing attacks.  Adding on a certificate authenticating "
+"the\n"
+"responses as signed by some centralized certificate authority would "
+"address many of\n"
+"the hostile nameserver issues but would leave open replay attacks as well"
+" as \n"
+"hostile certificate authority attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:33
+msgid ""
+"Voting style naming is dangerous as well, especially given the "
+"effectiveness of\n"
+"Sybil attacks in anonymous systems - the attacker can simply create an "
+"arbitrarily\n"
+"high number of peers and \"vote\" with each to take over a given name.  "
+"Proof-of-work\n"
+"methods can be used to make identity non-free, but as the network grows "
+"the load\n"
+"required to contact everyone to conduct online voting is implausible, or "
+"if the\n"
+"full network is not queried, different sets of answers may be reachable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:42
+msgid ""
+"As with the Internet however, I2P is keeping the design and operation of "
+"a \n"
+"naming system out of the (IP-like) communication layer.  The bundled "
+"naming library\n"
+"includes a simple service provider interface which alternate naming systems can\n"
+"plug into, allowing end users to drive what sort of naming tradeoffs they"
+" prefer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:50
+msgid ""
+"See also Names: "
+"Decentralized, Secure, Human-Meaningful: Choose Two."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:55
+msgid "(adapted from a post in the old Syndie, November 26, 2005)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:58
+msgid ""
+"Q:\n"
+"What to do if some hosts \n"
+"do not agree on one address and if some addresses are working, others are"
+" not? \n"
+"Who is the right source of a name?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:64
+msgid ""
+"A:\n"
+"You don't. This is actually a critical difference between names on I2P "
+"and how \n"
+"DNS works - names in I2P are human readable, secure, but not globally"
+" \n"
+"unique.  This is by design, and an inherent part of our need for "
+"security."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:70
+msgid ""
+"If I could somehow convince you to change the destination associated with"
+" some \n"
+"name, I'd successfully \"take over\" the site, and under no circumstances"
+" is that \n"
+"acceptable.  Instead, what we do is make names locally unique: "
+"they are \n"
+"what you use to call a site, just as how you can call things "
+"whatever \n"
+"you want when you add them to your browser's bookmarks, or your IM "
+"client's \n"
+"buddy list.  Who you call \"Boss\" may be who someone else calls "
+"\"Sally\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:78
+msgid "Names will not, ever, be securely human readable and globally unique."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:83
+msgid ""
+"The following from zzz is a review of several common\n"
+"complaints about I2P's naming system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:89
+msgid ""
+"Inefficiency:\n"
+"The whole hosts.txt is downloaded (if it has changed, since eepget uses "
+"the etag and last-modified headers).\n"
+"It's about 400K right now for almost 800 hosts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:94
+msgid ""
+"True, but this isn't a lot of traffic in the context of i2p, which is "
+"itself wildly inefficient\n"
+"(floodfill databases, huge encryption overhead and padding, garlic "
+"routing, etc.).\n"
+"If you downloaded a hosts.txt file from someone every 12 hours it "
+"averages out to about 10 bytes/sec."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:99
+msgid ""
+"As is usually the case in i2p, there is a fundamental tradeoff here "
+"between anonymity and efficiency.\n"
+"Some would say that using the etag and last-modified headers is hazardous"
+" because it exposes when you\n"
+"last requested the data.\n"
+"Others have suggested asking for specific keys only (similar to what jump"
+" services do, but\n"
+"in a more automated fashion), possibly at a further cost in anonymity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:106
+#, python-format
+msgid ""
+"Possible improvements would be a replacement or supplement to addressbook"
+" (see %(i2host)sp),\n"
+"or something simple like subscribing to http://example.i2p/cgi-"
+"bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n"
+"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 "
+"hours, for example,\n"
+"that could be both more efficient and more anonymous than the current "
+"hosts.txt with last-modified and etag."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:112
+#, python-format
+msgid ""
+"A sample implementation is on stats.i2p at\n"
+"%(url)s.\n"
+"This script returns an Etag with a timestamp.\n"
+"When a request comes in with the If-None-Match etag,\n"
+"the script ONLY returns new hosts since that timestamp, or 304 Not "
+"Modified if there are none.\n"
+"In this way, the script efficiently returns only the hosts the subscriber"
+"\n"
+"does not know about, in an addressbook-compatible manner."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:121
+msgid ""
+"So the inefficiency is not a big issue and there are several ways to "
+"improve things without\n"
+"radical change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:127
+msgid ""
+"Not Scalable:\n"
+"The 400K hosts.txt (with linear search) isn't that big at the moment and\n"
+"we can probably grow by 10x or 100x before it's a problem."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:132
+msgid ""
+"As far as network traffic see above.\n"
+"But unless you're going to do a slow real-time query over the network for"
+"\n"
+"a key, you need to have the whole set of keys stored locally, at a cost "
+"of about 500 bytes per key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:139
+msgid ""
+"Requires configuration and \"trust\":\n"
+"Out-of-the-box addressbook is only subscribed to "
+"http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n"
+"leading to poor new-user experience."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:144
+msgid ""
+"This is very much intentional. jrandom wants a user to \"trust\" a "
+"hosts.txt\n"
+"provider, and as he likes to say, \"trust is not a boolean\".\n"
+"The configuration step attempts to force users to think about issues of "
+"trust in an anonymous network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:149
+msgid ""
+"As another example, the \"Eepsite Unknown\" error page in the HTTP Proxy\n"
+"lists some jump services, but doesn't \"recommend\" any one in "
+"particular,\n"
+"and it's up to the user to pick one (or not).\n"
+"jrandom would say we trust the listed providers enough to list them but "
+"not enough to\n"
+"automatically go fetch the key from them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:156
+msgid ""
+"How successful this is, I'm not sure.\n"
+"But there must be some sort of hierarchy of trust for the naming system.\n"
+"To treat everyone equally may increase the risk of hijacking."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:163
+msgid "It isn't DNS"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:166
+msgid ""
+"Unfortunately real-time lookups over i2p would significantly slow down "
+"web browsing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:169
+msgid ""
+"Also, DNS is based on lookups with limited caching and time-to-live, "
+"while i2p\n"
+"keys are permanent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:173
+msgid "Sure, we could make it work, but why? It's a bad fit."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:178
+msgid ""
+"Not reliable:\n"
+"It depends on specific servers for addressbook subscriptions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:182
+msgid ""
+"Yes it depends on a few servers that you have configured.\n"
+"Within i2p, servers and services come and go.\n"
+"Any other centralized system (for example DNS root servers) would\n"
+"have the same problem. A completely decentralized system (everybody is "
+"authoritative)\n"
+"is possible by implementing an \"everybody is a root DNS server\" "
+"solution, or by\n"
+"something even simpler, like a script that adds everybody in your "
+"hosts.txt to your addressbook."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:190
+msgid ""
+"People advocating all-authoritative solutions generally haven't thought "
+"through\n"
+"the issues of conflicts and hijacking, however."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:196
+msgid ""
+"Awkward, not real-time:\n"
+"It's a patchwork of hosts.txt providers, key-add web form providers, jump"
+" service providers,\n"
+"eepsite status reporters.\n"
+"Jump servers and subscriptions are a pain, it should just work like DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:202
+msgid "See the reliability and trust sections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:207
+msgid ""
+"So, in summary, the current system is not horribly broken, inefficient, "
+"or un-scalable,\n"
+"and proposals to \"just use DNS\" aren't well thought-through."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:212
+msgid "Alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:213
+msgid ""
+"The I2P source contains several pluggable naming systems and supports "
+"configuration options\n"
+"to enable experimentation with naming systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:218
+msgid ""
+"Meta - calls two or more other naming systems in order.\n"
+"By default, calls PetName then HostsTxt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:222
+msgid ""
+"PetName - Looks up in a petnames.txt file.\n"
+"The format for this file is NOT the same as hosts.txt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:226
+msgid "HostsTxt - Looks up in the following files, in order:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:234
+msgid ""
+"AddressDB - Each host is listed in a separate file in a addressDb/"
+" directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:237
+msgid ""
+"Eepget - does an HTTP lookup request from an external\n"
+"server - must be stacked after the HostsTxt lookup with Meta.\n"
+"This could augment or replace the jump system.\n"
+"Includes in-memory caching."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:243
+msgid ""
+"Exec - calls an external program for lookup, allows\n"
+"additional experimentation in lookup schemes, independent of java.\n"
+"Can be used after HostsTxt or as the sole naming system.\n"
+"Includes in-memory caching."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:249
+msgid "Dummy - used as a fallback for Base64 names, otherwise fails."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:253
+msgid ""
+"The current naming system can be changed with the advanced config option "
+"'i2p.naming.impl'\n"
+"(restart required).\n"
+"See core/java/src/net/i2p/client/naming for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:258
+msgid ""
+"Any new system should be stacked with HostsTxt, or should\n"
+"implement local storage and/or the addressbook subscription functions, "
+"since addressbook\n"
+"only knows about the hosts.txt files and format."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:264
+msgid "Certificates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:265
+msgid ""
+"I2P destinations contain a certificate, however at the moment that "
+"certificate\n"
+"is always null.\n"
+"With a null certificate, base64 destinations are always 516 bytes ending "
+"in \"AAAA\",\n"
+"and this is checked in the addressbook merge mechanism, and possibly "
+"other places.\n"
+"Also, there is no method available to generate a certificate or add it to"
+" a\n"
+"destination. So these will have to be updated to implement certificates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:273
+#, python-format
+msgid ""
+"One possible use of certificates is for proof of work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:276
+msgid ""
+"Another is for \"subdomains\" (in quotes because there is really no such "
+"thing,\n"
+"i2p uses a flat naming system) to be signed by the 2nd level domain's "
+"keys."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:280
+msgid ""
+"With any certificate implementation must come the method for verifying "
+"the\n"
+"certificates.\n"
+"Presumably this would happen in the addressbook merge code.\n"
+"Is there a method for multiple types of certificates, or multiple "
+"certificates?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:286
+msgid ""
+"Adding on a certificate authenticating the\n"
+"responses as signed by some centralized certificate authority would "
+"address many of\n"
+"the hostile nameserver issues but would leave open replay attacks as well"
+" as \n"
+"hostile certificate authority attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:2
+msgid "Low-level Cryptography Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:6
+msgid "This page specifies the low-level details of the cryptography in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:10
+#, python-format
+msgid ""
+"There are a handful of cryptographic algorithms in use within I2P, but we"
+" have\n"
+"reduced them to a bare minimum to deal with our needs - one symmetric "
+"algorithm\n"
+"one asymmetric algorithm, one signing algorithm, and one hashing "
+"algorithm.  However, \n"
+"we do combine them in some particular ways to provide message integrity "
+"(rather than\n"
+"relying on a MAC).  In addition, as much as we hate doing anything new in"
+" regards to \n"
+"cryptography, we can't seem to find a reference discussing (or even "
+"naming) the \n"
+"technique used in ElGamal/AES+SessionTag "
+"(but we're sure others have done it)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:20
+msgid "ElGamal encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:22
+msgid ""
+"\n"
+"ElGamal is used for asymmetric encryption.\n"
+"ElGamal is used in several places in I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:27
+#, python-format
+msgid ""
+"To encrypt router-to-router Tunnel Build "
+"Messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:30
+#, python-format
+msgid ""
+"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n"
+"using the encryption key in the LeaseSet"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:34
+#: i2p2www/pages/site/docs/how/cryptography.html:198
+#, python-format
+msgid ""
+"For encryption of some netDb stores and "
+"queries sent to floodfill routers\n"
+"as a part of ElGamal/AES+SessionTag\n"
+"(destination-to-router or router-to-router)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:41
+msgid ""
+"We use common primes for 2048 ElGamal encryption and decryption, as given"
+" by IETF RFC-3526.\n"
+"We currently only use ElGamal to encrypt the IV and session key in a "
+"single block, followed by the \n"
+"AES encrypted payload using that key and IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:47
+msgid "The unencrypted ElGamal contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:64
+msgid ""
+"The H(data) is the SHA256 of the data that is encrypted in the ElGamal "
+"block,\n"
+"and is preceded by a nonzero byte. \n"
+"This byte could be random, but as implemented it is always 0xFF.\n"
+"It could possibly be used for flags in the future.\n"
+"The data encrypted in the block may be up to 222 bytes long.\n"
+"As the encrypted data may contain a substantial number of zeros if the\n"
+"cleartext is smaller than 222 bytes, it is recommended that higher layers"
+" pad\n"
+"the cleartext to 222 bytes with random data.\n"
+"Total length: typically 255 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:76
+msgid "The encrypted ElGamal contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:102
+msgid ""
+"Each encrypted part is prepended with zeros to a size of exactly 257 "
+"bytes.\n"
+"Total length: 514 bytes.\n"
+"In typical usage, higher layers pad the cleartext data to 222 bytes,\n"
+"resulting in an unencrypted block of 255 bytes.\n"
+"This is encoded as two 256-byte encrypted parts,\n"
+"and there is a single byte of zero padding before each part at this layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:111
+#, python-format
+msgid "See the ElGamal code."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:115
+msgid ""
+"The shared prime is the \n"
+"[Oakley prime "
+"for 2048 bit keys]"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:122
+msgid "or as a hexadecimal value:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:138
+msgid "Using 2 as the generator."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:142
+msgid "Short Exponent"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:143
+#, python-format
+msgid ""
+"While the standard exponent size is 2048 bits (256 bytes) and the I2P\n"
+"PrivateKey\n"
+"is a full 256 bytes, in some cases\n"
+"we use the short exponent size of 226 bits (28.25 bytes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:150
+#, python-format
+msgid ""
+"This should be safe for use with the Oakley primes, per\n"
+"On Diffie-Hellman Key Agreement with Short Exponents "
+"- van Oorschot, Weiner\n"
+"at EuroCrypt 96, and crypto++'s "
+"benchmarks.\n"
+"Benchmarks originally at this link, now dead,\n"
+"rescued from the wayback machine,"
+" dated Apr 23, 2008."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:160
+#, python-format
+msgid ""
+"Also, Koshiba & Kurosawa: Short Exponent Diffie-"
+"Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n"
+"(full text on Google Books) apparently "
+"supports this, according to\n"
+"this sci.crypt thread.\n"
+"The remainder of the PrivateKey is padded with zeroes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:169
+msgid ""
+"Prior to release 0.9.8, all routers used the short exponent.\n"
+"As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent.\n"
+"Other routers continue to use the short exponent due to concerns about "
+"processor load.\n"
+"The transition to a longer exponent for these platforms is a topic for "
+"further study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:176
+#: i2p2www/pages/site/docs/how/cryptography.html:273
+#: i2p2www/pages/site/docs/how/cryptography.html:352
+#: i2p2www/pages/site/docs/how/cryptography.html:391
+msgid "Obsolescence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:177
+msgid ""
+"The vulnerability of the network to an ElGamal attack and the impact of "
+"transitioning to a longer bit length is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:185
+msgid "AES is used for symmetric encryption, in several cases:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:190
+msgid "For transport encryption after DH key exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:194
+#, python-format
+msgid ""
+"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:204
+#, python-format
+msgid ""
+"For encryption of periodic tunnel "
+"test messages sent from the router to itself, through its own "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:209
+#, python-format
+msgid ""
+"We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n"
+"The padding used is specified in IETF RFC-2313 "
+"(PKCS#5 1.5, section 8.1 (for block type 02)).\n"
+"In this case, padding exists of pseudorandomly generated octets to match "
+"16 byte blocks.\n"
+"Specifically, see [the CBC code] and the "
+"Cryptix AES\n"
+"[implementation], as well as the padding, found"
+" in the\n"
+"ElGamalAESEngine.getPadding function."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:274
+msgid ""
+"The vulnerability of the network to an AES attack and the impact of "
+"transitioning to a longer bit length is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:279
+#: i2p2www/pages/site/docs/how/cryptography.html:371
+#: i2p2www/pages/site/docs/how/cryptography.html:397
+#: i2p2www/pages/site/docs/how/cryptography.html:465
+#: i2p2www/pages/site/docs/how/garlic-routing.html:281
+#: i2p2www/pages/site/docs/how/peer-selection.html:296
+msgid "References"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:282
+msgid "Feb. 7, 2006 Status Notes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:289
+#, python-format
+msgid ""
+"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), "
+"as implemented in\n"
+"[DSAEngine].\n"
+"DSA was chosen because it is much faster for signatures than ElGamal."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:295
+msgid "The DSA constants"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:346
+#, python-format
+msgid ""
+"The Signing Public"
+" Key is 1024 bits.\n"
+"The Signing "
+"Private Key is 160 bits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:353
+#, python-format
+msgid ""
+"NIST 800-57\n"
+"recommends a minimum of (L=2048, N=224) for usage beyond 2010.\n"
+"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a "
+"given key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:359
+msgid ""
+"The prime number was chosen in 2003,\n"
+"and the person that chose the number (TheCrypto) is currently no longer "
+"an I2P developer.\n"
+"As such, we do not know if the prime chosen is a 'strong prime'.\n"
+"If a larger prime is chosen for future purposes, this should be a strong "
+"prime, and we will document the construction process."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:366
+msgid ""
+"The vulnerability of the network to a DSA attack and the impact of "
+"transitioning to longer keys is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:374
+#: i2p2www/pages/site/docs/how/cryptography.html:376
+#, python-format
+msgid "Meeting %(num)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:378
+msgid "Choosing the constants"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:386
+#, python-format
+msgid ""
+"Hashes within I2P are plain old SHA256, as implemented in\n"
+"[SHA256Generator]"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:392
+msgid ""
+"The vulnerability of the network to a SHA-256 attack and the impact of "
+"transitioning to a longer hash is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:403
+msgid "Transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:404
+msgid ""
+"At the lowest protocol layer,\n"
+"point-to-point inter-router communication is protected by the transport "
+"layer security.\n"
+"Both transports use 256 byte (2048 bit) Diffie-Hellman key exchange\n"
+"using\n"
+"the same shared prime and generator as specified "
+"above for ElGamal,\n"
+"followed by symmetric AES encryption as described above.\n"
+"This provides\n"
+"perfect "
+"forward secrecy\n"
+"on the transport links."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:416
+msgid "NTCP connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:418
+#, python-format
+msgid ""
+"NTCP connections are negotiated with a 2048 Diffie-Hellman "
+"implementation,\n"
+"using the router's identity to proceed with a station to station "
+"agreement, followed by\n"
+"some encrypted protocol specific fields, with all subsequent data "
+"encrypted with AES\n"
+"(as above).\n"
+"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) "
+"forward secrecy', while ElGamalAES+SessionTag does not."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:426
+msgid ""
+"In order to migrate to a more standardized implementation (TLS/SSL or "
+"even SSH), the following issues must be addressed:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:430
+msgid ""
+"Can we somehow reestablish sessions securely (ala session tags) or do we "
+"need to do full negotiation each time?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:433
+msgid ""
+"Can we simplify/avoid the x509 or other certificate formats and use our "
+"own RouterInfo structure (which \n"
+"contains the ElGamal and DSA keys)?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:438
+#, python-format
+msgid "See the NTCP specification for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:442
+msgid "UDP connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:443
+msgid ""
+"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an"
+" explicit IV and MAC \n"
+"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a "
+"2048 bit \n"
+"Diffie-Hellman exchange, station-to-station authentication with the other"
+" \n"
+"router's DSA key, plus each network message has their own hash for local "
+"integrity \n"
+"checking."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:451
+#, python-format
+msgid "See the SSU specification for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:455
+#, python-format
+msgid ""
+"WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n"
+"Apparently, an early version of SSU used HMAC-SHA256, and then it was "
+"switched\n"
+"to MD5-128 for performance reasons, but left the 32-byte buffer size "
+"intact.\n"
+"See HMACGenerator.java and\n"
+"the 2005-07-05 status notes\n"
+"for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:2
+msgid "ElGamal/AES + SessionTag Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:3
+msgid "February 2011"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:7
+msgid "ElGamal/AES+SessionTags is used for end-to-end encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:11
+msgid ""
+"As an unreliable, unordered, message based system, I2P uses a simple "
+"combination \n"
+"of asymmetric and symmetric encryption algorithms to provide data "
+"confidentiality \n"
+"and integrity to garlic messages. As a whole, the combination is referred"
+" \n"
+"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to "
+"describe \n"
+"the use of 2048bit ElGamal, AES256, SHA256, and 32 byte nonces."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:19
+#: i2p2www/pages/site/docs/how/tech-intro.html:512
+msgid ""
+"The first time a router wants to encrypt a garlic message to another "
+"router, \n"
+"they encrypt the keying material for an AES256 session key with ElGamal "
+"and \n"
+"append the AES256/CBC encrypted payload after that encrypted ElGamal "
+"block. \n"
+"In addition to the encrypted payload, the AES encrypted section contains "
+"the \n"
+"payload length, the SHA256 hash of the unencrypted payload, as well as a "
+"number \n"
+"of \"session tags\" - random 32 byte nonces. The next time the sender "
+"wants \n"
+"to encrypt a garlic message to another router, rather than ElGamal "
+"encrypt \n"
+"a new session key they simply pick one of the previously delivered "
+"session \n"
+"tags and AES encrypt the payload like before, using the session key used "
+"with \n"
+"that session tag, prepended with the session tag itself. When a router "
+"receives \n"
+"a garlic encrypted message, they check the first 32 bytes to see if it "
+"matches \n"
+"an available session tag - if it does, they simply AES decrypt the "
+"message, \n"
+"but if it does not, they ElGamal decrypt the first block."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:35
+#: i2p2www/pages/site/docs/how/tech-intro.html:528
+msgid ""
+"Each session tag can be used only once so as to prevent internal "
+"adversaries \n"
+"from unnecessarily correlating different messages as being between the "
+"same \n"
+"routers. The sender of an ElGamal/AES+SessionTag encrypted message "
+"chooses \n"
+"when and how many tags to deliver, prestocking the recipient with enough "
+"tags \n"
+"to cover a volley of messages. Garlic messages may detect the successful "
+"tag \n"
+"delivery by bundling a small additional message as a clove (a \"delivery "
+"status \n"
+"message\") - when the garlic message arrives at the intended recipient "
+"and \n"
+"is decrypted successfully, this small delivery status message is one of "
+"the \n"
+"cloves exposed and has instructions for the recipient to send the clove "
+"back \n"
+"to the original sender (through an inbound tunnel, of course). When the "
+"original \n"
+"sender receives this delivery status message, they know that the session "
+"tags \n"
+"bundled in the garlic message were successfully delivered."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:50
+msgid ""
+"Session tags themselves have a short lifetime, after which they are \n"
+"discarded if not used. In addition, the quantity stored for each key is "
+"limited, \n"
+"as are the number of keys themselves - if too many arrive, either new or "
+"old \n"
+"messages may be dropped. The sender keeps track whether messages using "
+"session \n"
+"tags are getting through, and if there isn't sufficient communication it "
+"may \n"
+"drop the ones previously assumed to be properly delivered, reverting back"
+" \n"
+"to the full expensive ElGamal encryption.\n"
+"A session will continue to exist until all its tags are exhausted or "
+"expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:61
+msgid ""
+"Sessions are unidirectional. Tags are delivered from Alice to Bob,\n"
+"and Alice then uses the tags, one by one, in subsequent messages to Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:66
+msgid ""
+"Sessions may be established between Destinations, between Routers, or\n"
+"between a Router and a Destination.\n"
+"Each Router and Destination maintains its own Session Key Manager to\n"
+"keep track of Session Keys and Session Tags.\n"
+"Separate Session Key Managers prevents correlation of multiple "
+"Destinations\n"
+"to each other or a Router by adversaries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:77
+msgid "Message Reception"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:78
+msgid ""
+"Each message received has one of two\n"
+"the two possible conditions:
            "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:84
+msgid ""
+"It is part of an existing session and contains a Session Tag and an AES "
+"encrypted block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:85
+msgid "It is for a new session and contains both ElGamal and AES encrypted blocks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:88
+msgid ""
+"When a router receives a message, it will first assume it is from\n"
+"an existing session and attempt to look up the Session Tag and decrypt "
+"the following data using AES.\n"
+"If that fails, it will assume it is for a new session and attempt to\n"
+"decrypt it using ElGamal."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:97
+msgid "New Session Message Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:98
+msgid ""
+"A New Session ElGamal Message contains two parts, an encrypted ElGamal "
+"block\n"
+"and an encrypted AES block."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:103
+msgid "The encrypted message contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:127
+msgid "ElGamal Block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:128
+msgid "The encrypted ElGamal Block is always 514 bytes long."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:132
+msgid "The unencrypted ElGamal data is 222 bytes long, containing:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:164
+#, python-format
+msgid ""
+"The 32-byte\n"
+"Session Key\n"
+"is the identifier for the session.\n"
+"The 32-byte Pre-IV will be used to generate the IV for the AES block that"
+" follows;\n"
+"the IV is the first 16 bytes of the SHA-256 Hash of the Pre-IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:172
+#, python-format
+msgid ""
+"The 222 byte payload is encrypted\n"
+"using ElGamal\n"
+"and the encrypted block is 514 bytes long.\n"
+"
            "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:179
+msgid "AES Block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:180
+msgid "The unencrypted data in the AES block contains the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:224
+#, python-format
+msgid "2-byte Integer, 0-200"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:228
+#, python-format
+msgid ""
+"That many 32-byte Session Tags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:232
+#, python-format
+msgid "4-byte Integer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:236
+#, python-format
+msgid ""
+"The 32-byte SHA256 Hash of"
+" the payload"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:240
+msgid "A one-byte value. Normally == 0. If == 0x01, a Session Key follows"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:244
+#, python-format
+msgid ""
+"A 32-byte Session "
+"Key,\n"
+"                 to replace the old key, and is only present if preceding"
+" flag is 0x01"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:249
+msgid "the data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:251
+msgid ""
+"Random data to a multiple of 16 bytes for the total length.\n"
+"         May contain more than the minimum required padding."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:256
+msgid "Minimum length: 48 bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:260
+#, python-format
+msgid ""
+"The data is then AES Encrypted,\n"
+"using the session key and IV (calculated from the pre-IV) from the "
+"ElGamal section.\n"
+"The encrypted AES Block length is variable but is always a multiple of 16"
+" bytes.\n"
+"
            "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:269
+#, python-format
+msgid ""
+"Actual max payload length, and max block length, is less than 64 KB; see "
+"the I2NP Overview."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:272
+msgid "New Session Key is currently unused and is never present."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:277
+msgid "Existing Session Message Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:278
+msgid ""
+"The session tags delivered successfully are remembered for a \n"
+"brief period (15 minutes currently) until they are used or discarded.\n"
+"A tag is used by packaging one in an Existing Session Message that\n"
+"contains only an AES encrypted block, and is not preceded by an\n"
+"ElGamal block."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:286
+msgid ""
+"The existing session message is\n"
+"as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:309
+#, python-format
+msgid ""
+"A 32-byte Session "
+"Tag\n"
+"             previously delivered in an AES block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:314
+msgid "As specified above."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:318
+msgid ""
+"The session tag also serves as\n"
+"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the "
+"sessionTag."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:323
+msgid ""
+"To decode a message from an existing session, a router looks up the "
+"Session Tag to find an\n"
+"associated Session Key. If the Session Tag is found, the AES block is "
+"decrypted using the associated Session Key.\n"
+"If the tag is not found, the message is assumed to be a New Session Message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:332
+msgid ""
+"There are many possible areas to tune the Session Key Manager's "
+"algorithms;\n"
+"some may interact with the streaming library behavior, or have "
+"significant\n"
+"impact on overall performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:338
+msgid ""
+"Delivery of too many tags at one time may impose substantial overhead for"
+" brief streaming connections\n"
+"or datagrams, and increase the chance of message loss.\n"
+"We currently deliver 40 tags at a time (1280 bytes).\n"
+"32 (1024 bytes) may be better for tunnel fragmentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:345
+msgid ""
+"A few tags could be delivered in each of several messages, or lots of "
+"tags all at once."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:349
+msgid ""
+"It is also important to study and tune\n"
+"the low-tag thresholds at which more tags are sent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:354
+msgid ""
+"The number of tags delivered could depend on message size, keeping in "
+"mind\n"
+"the eventual padding to 1KB at the tunnel message layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:359
+msgid ""
+"Clients could send an estimate of session lifetime to the router, as an "
+"advisory\n"
+"on the number of tags required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:364
+msgid ""
+"Delivery of too few tags causes the router to fall back to an expensive "
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:368
+msgid ""
+"The router may assume delivery of Session Tags, or await acknowledgement "
+"before using them;\n"
+"there are tradeoffs for each strategy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:373
+msgid ""
+"For very brief messages, almost the full 222 bytes of the pre-IV and "
+"padding fields in the ElGamal block\n"
+"could be used for the entire message, instead of establishing a session."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:378
+msgid ""
+"Evaluate padding strategy; currently we pad to a minimum of 128 bytes.\n"
+"Would be better to add a few tags to small messages than pad."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:383
+msgid ""
+"Perhaps things could be more efficient if the Session Tag system was "
+"bidirectional,\n"
+"so tags delivered in the 'forward' path could be used in the 'reverse' "
+"path,\n"
+"thus avoiding ElGamal in the initial response.\n"
+"The router currently plays some tricks like this when sending\n"
+"tunnel test messages to itself."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:391
+#, python-format
+msgid ""
+"Change from Session Tags to\n"
+"a synchronized PRNG."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:396
+#, python-format
+msgid ""
+"Several of these ideas may require a new I2NP message type, or\n"
+"set a flag in the\n"
+"Delivery Instructions,\n"
+"or set a magic number in the first few bytes of the Session Key field\n"
+"and accept a small risk of the random Session Key matching the magic "
+"number."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:2
+msgid "Garlic Routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:6
+msgid "Garlic Routing and \"Garlic\" Terminology"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:7
+msgid ""
+"The terms \"garlic routing\" and \"garlic encryption\" are often used "
+"rather loosely when referring to I2P's technology.\n"
+"Here, we explain the history of the terms, the various meanings, and\n"
+"the usage of \"garlic\" methods in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:13
+msgid ""
+"\"Garlic routing\" was first coined by\n"
+"Michael J. Freedman\n"
+"in Roger Dingledine's Free Haven \n"
+"Master's thesis "
+"Section 8.1.1 (June 2000), as derived from \n"
+"Onion Routing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:21
+msgid ""
+"\"Garlic\" may have been used originally by I2P developers because I2P "
+"implements a form of\n"
+"bundling as Freedman describes, or simply to emphasize general "
+"differences from Tor.\n"
+"The specific reasoning may be lost to history.\n"
+"Generally, when referring to I2P, the term \"garlic\" may mean one of "
+"three things:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:28
+#: i2p2www/pages/site/docs/how/garlic-routing.html:39
+msgid "Layered Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:29
+msgid "Bundling multiple messages together"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:30
+#: i2p2www/pages/site/docs/how/garlic-routing.html:96
+msgid "ElGamal/AES Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:33
+msgid ""
+"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven "
+"years has not always been precise; therefore the reader is\n"
+"cautioned when encountering the term.\n"
+"Hopefully, the explanation below will make things clear."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:40
+msgid ""
+"Onion routing is a technique for building paths, or tunnels, through a "
+"series of peers,\n"
+"and then using that tunnel.\n"
+"Messages are repeatedly encrypted by the originator, and then decrypted "
+"by each hop.\n"
+"During the building phase, only the routing instructions for the next hop"
+" are exposed to each peer.\n"
+"During the operating phase, messages are passed through the tunnel, and "
+"the\n"
+"message and its routing instructions are only exposed to the endpoint of "
+"the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:49
+#, python-format
+msgid ""
+"This is similar to the way Mixmaster\n"
+"(see network comparisons) sends messages "
+"- taking a message, encrypting it\n"
+"to the recipient's public key, taking that encrypted message and "
+"encrypting\n"
+"it (along with instructions specifying the next hop), and then taking "
+"that\n"
+"resulting encrypted message and so on, until it has one layer of "
+"encryption\n"
+"per hop along the path."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:58
+msgid ""
+"In this sense, \"garlic routing\" as a general concept is identical to "
+"\"onion routing\".\n"
+"As implemented in I2P, of course, there are several differences from the "
+"implementation in Tor; see below.\n"
+"Even so, there are substantial similarities such that I2P benefits from a"
+"\n"
+"large amount of"
+" academic research on onion routing,\n"
+"Tor, and similar "
+"mixnets."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:67
+msgid "Bundling Multiple Messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:68
+msgid ""
+"Michael Freedman defined \"garlic routing\" as an extension to onion "
+"routing,\n"
+"in which multiple messages are bundled together.\n"
+"He called each message a \"bulb\".\n"
+"All the messages, each with its own delivery instructions, are exposed at"
+" the\n"
+"endpoint.\n"
+"This allows the efficient bundling of an onion routing \"reply block\" "
+"with the original message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:77
+msgid ""
+"This concept is implemented in I2P, as described below.\n"
+"Our term for garlic \"bulbs\" is \"cloves\".\n"
+"Any number of messages can be\n"
+"contained, instead of just a single message.\n"
+"This is a significant distinction from the onion routing implemented in "
+"Tor.\n"
+"However, it is only one of many major architectural differences between "
+"I2P and Tor;\n"
+"perhaps it is not, by itself, enough to justify a change in terminology."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:87
+msgid ""
+"Another difference\n"
+"from the method described by Freedman\n"
+"is that the path is unidirectional - there is no \"turning point\" as "
+"seen in onion routing\n"
+"or mixmaster reply blocks, which greatly simplifies the algorithm and "
+"allows for more flexible\n"
+"and reliable delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:97
+#, python-format
+msgid ""
+"In some cases, \"garlic encryption\" may simply mean\n"
+"ElGamal/AES+SessionTag encryption\n"
+"(without multiple layers)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:105
+msgid "\"Garlic\" Methods in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:106
+msgid ""
+"Now that we've defined various \"garlic\" terms, we can say that\n"
+"I2P uses garlic routing, bundling and encryption in three places:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:111
+msgid "For building and routing through tunnels (layered encryption)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:112
+msgid ""
+"For determining the success or failure of end to end message delivery "
+"(bundling)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:113
+msgid ""
+"For publishing some network database entries (dampening the probability "
+"of a successful traffic analysis attack) (ElGamal/AES)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:116
+msgid ""
+"There are also significant ways that this technique can be used to "
+"improve the performance of the network, \n"
+"exploiting transport latency/throughput tradeoffs, and branching data "
+"through redundant paths to increase reliability."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:122
+msgid "Tunnel Building and Routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:123
+msgid ""
+"In I2P, tunnels are unidirectional. Each party builds two tunnels,\n"
+"one for outbound and one for inbound traffic.\n"
+"Therefore, four tunnels are required for a single round-trip message and "
+"reply."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:129
+#, python-format
+msgid ""
+"Tunnels are built, and then used, with layered encryption.\n"
+"This is described on the\n"
+"tunnel implementation page.\n"
+"Tunnel building details are defined on\n"
+"this page.\n"
+"We use\n"
+"ElGamal/AES+SessionTag for the encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:141
+#, python-format
+msgid ""
+"Tunnels are a general-purpose mechanism to transport all\n"
+"I2NP messages, and\n"
+"Garlic Messages are not used to "
+"build tunnels.\n"
+"We do not bundle multiple\n"
+"I2NP messages into a single\n"
+"Garlic Message for unwrapping at "
+"the outbound tunnel endpoint;\n"
+"the tunnel encryption is sufficient."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:152
+msgid "End-to-End Message Bundling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:153
+#, python-format
+msgid ""
+"At the layer above tunnels, I2P delivers end-to-end messages between\n"
+"Destinations.\n"
+"Just as within a single tunnel, we use\n"
+"ElGamal/AES+SessionTag for the encryption."
+"\n"
+"Each client message as delivered to the router through the\n"
+"I2CP interface becomes a single\n"
+"Garlic Clove\n"
+"with its own\n"
+"Delivery Instructions,\n"
+"inside a\n"
+"Garlic Message.\n"
+"Delivery Instructions may specify a Destination, Router, or Tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:172
+msgid ""
+"Generally, a Garlic Message will contain only one clove.\n"
+"However, the router will periodically bundle two additional\n"
+"cloves in the Garlic Message:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:177
+msgid "Garlic Message Cloves"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:180
+#, python-format
+msgid ""
+"A\n"
+"Delivery Status Message,\n"
+"with\n"
+"Delivery Instructions\n"
+"specifying that it be sent back to the originating router as an "
+"acknowledgment.\n"
+"This is similar to the \"reply block\" or \"reply onion\"\n"
+"described in the references.\n"
+"It is used for determining the success or failure of end to end message "
+"delivery.\n"
+"The originating router may, upon failure to receive the Delivery Status "
+"Message\n"
+"within the expected time period, modify the routing to the far-end "
+"Destination,\n"
+"or take other actions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:194
+#, python-format
+msgid ""
+"A\n"
+"Database Store Message,\n"
+"containing a\n"
+"LeaseSet\n"
+"for the originating Destination, with\n"
+"Delivery Instructions\n"
+"specifying the far-end destination's router.\n"
+"By periodically bundling a LeaseSet, the router ensures that the far-end "
+"will be able\n"
+"to maintain communications.\n"
+"Otherwise the far-end would have to query a floodfill router for the "
+"network database entry,\n"
+"and all LeaseSets would have to be published to the network database, as "
+"explained on the\n"
+"network database page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:213
+#, python-format
+msgid ""
+"In the current implementation, the Delivery Status and Database Store "
+"Messages\n"
+"are bundled when the local LeaseSet changes, when additional\n"
+"Session Tags\n"
+"are delivered, or if the messages have not been bundled in the previous "
+"minute."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:220
+msgid ""
+"Obviously, the additional messages are currently bundled for specific "
+"purposes,\n"
+"and not part of a general-purpose routing scheme."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:226
+msgid "Storage to the Floodfill Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:227
+#, python-format
+msgid ""
+"As explained on the\n"
+"network database page,\n"
+"local\n"
+"LeaseSets\n"
+"are sent to floodfill routers in a\n"
+"Database Store Message\n"
+"wrapped in a\n"
+"Garlic Message\n"
+"so it is not visible to the tunnel's outbound gateway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:243
+#, python-format
+msgid ""
+"The Garlic Message mechanism is very flexible and provides a structure "
+"for\n"
+"implementing many types of mixnet delivery methods.\n"
+"Together with the unused delay option in the\n"
+"tunnel message Delivery "
+"Instructions,\n"
+"a wide spectrum of batching, delay, mixing, and routing strategies are "
+"possible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:251
+msgid ""
+"In particular, there is potential for much more flexibility at the "
+"outbound tunnel endpoint.\n"
+"Messages could possibly be routed from there to one of several tunnels\n"
+"(thus minimizing point-to-point connections), or multicast to several "
+"tunnels\n"
+"for redundancy, or streaming audio and video."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:258
+msgid ""
+"Such experiments may conflict with the need to ensure security and "
+"anonymity, such\n"
+"as limiting certain routing paths, restricting the types of I2NP messages"
+" that may\n"
+"be forwarded along various paths, and enforcing certain message "
+"expiration times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:264
+#, python-format
+msgid ""
+"As a part of\n"
+"ElGamal/AES encryption,\n"
+"a garlic message contains a sender\n"
+"specified amount of padding data, allowing the sender to take active "
+"countermeasures \n"
+"against traffic analysis.\n"
+"This is not currently used, beyond the requirement to pad to a multiple "
+"of 16 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:273
+#, python-format
+msgid ""
+"Encryption of additional messages to and from the\n"
+"floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:283
+msgid ""
+"The term garlic routing was first coined in Roger Dingledine's Free Haven"
+" \n"
+"Master's thesis "
+"(June 2000),\n"
+"see Section 8.1.1 authored by\n"
+"Michael J. Freedman."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:290
+msgid "Onion router publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:292
+msgid "Onion Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:294
+msgid "Garlic Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:296
+#, python-format
+msgid ""
+"I2P Meeting 58 (2003) discussing the "
+"implementation of garlic routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:302
+msgid "Free Haven publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:304
+msgid ""
+"Onion routing was first described in Hiding Routing Information\n"
+"by David M. Goldschlag, Michael G. Reed, and Paul F. Syverson in 1996."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:2
+msgid "A Gentle Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:5
+msgid "A Gentle Introduction to How I2P Works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:7
+msgid ""
+"I2P is a project to build, deploy, and maintain a network supporting "
+"secure and anonymous\n"
+"communication. People using I2P are in control of the tradeoffs between "
+"anonymity, reliability,\n"
+"bandwidth usage, and latency. There is no central point in the network on"
+" which pressure can be\n"
+"exerted to compromise the integrity, security, or anonymity of the "
+"system. The network supports\n"
+"dynamic reconfiguration in response to various attacks, and has been "
+"designed to make use of\n"
+"additional resources as they become available. Of course, all aspects of "
+"the network are open and\n"
+"freely available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:17
+msgid ""
+"Unlike many other anonymizing networks, I2P doesn't try to provide "
+"anonymity by hiding the\n"
+"originator of some communication and not the recipient, or the other way "
+"around. I2P is designed to\n"
+"allow peers using I2P to communicate with each other anonymously — "
+"both sender and recipient\n"
+"are unidentifiable to each other as well as to third parties. For "
+"example, today there are both\n"
+"in-I2P web sites (allowing anonymous publishing / hosting) as well as "
+"HTTP proxies to the normal web\n"
+"(allowing anonymous web browsing). Having the ability to run servers "
+"within I2P is essential, as it\n"
+"is quite likely that any outbound proxies to the normal Internet will be "
+"monitored, disabled, or\n"
+"even taken over to attempt more malicious attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:28
+#, python-format
+msgid ""
+"The network itself is message oriented - it is essentially a secure and "
+"anonymous IP layer, where\n"
+"messages are addressed to cryptographic keys (Destinations) and can be "
+"significantly larger than IP\n"
+"packets. Some example uses of the network include \"eepsites\" "
+"(webservers hosting normal web\n"
+"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a "
+"distributed data store. With the\n"
+"help of the I2PTunnel application, we are "
+"able to stream traditional\n"
+"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even "
+"streaming audio. Most people\n"
+"will not use I2P directly, or even need to know they're using it. Instead"
+" their view will be of one\n"
+"of the I2P enabled applications, or perhaps as a little controller app to"
+" turn on and off various\n"
+"proxies to enable the anonymizing functionality."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:40
+#, python-format
+msgid ""
+"An essential part of designing, developing, and testing an anonymizing "
+"network is to define the threat model, since there is no such thing "
+"as \"true\" anonymity, just\n"
+"increasingly expensive costs to identify someone. Briefly, I2P's intent "
+"is to allow people to\n"
+"communicate in arbitrarily hostile environments by providing good "
+"anonymity, mixed in with\n"
+"sufficient cover traffic provided by the activity of people who require "
+"less anonymity. This way,\n"
+"some users can avoid detection by a very powerful adversary, while others"
+" will try to evade a weaker\n"
+"entity, all on the same network, where each one's messages are "
+"essentially indistinguishable\n"
+"from the others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:51
+msgid "Why?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:52
+#, python-format
+msgid ""
+"There are a multitude of reasons why we need a system to support "
+"anonymous communication, and\n"
+"everyone has their own personal rationale. There are many other\n"
+"efforts working on finding ways to provide varying degrees of "
+"anonymity to people through the\n"
+"Internet, but we could not find any that met our needs or threat model."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:59
+msgid "How?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:61
+#, python-format
+msgid ""
+"The network at a glance is made up of a set of nodes (\"routers\") with a"
+" number of unidirectional\n"
+"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is "
+"identified by a cryptographic RouterIdentity which is\n"
+"typically long lived. These routers communicate with each other through "
+"existing transport\n"
+"mechanisms (TCP, UDP, etc), passing various messages. Client applications"
+" have their own\n"
+"cryptographic identifier (\"Destination\") which enables it to send and "
+"receive messages. These\n"
+"clients can connect to any router and authorize the temporary allocation "
+"(\"lease\") of some tunnels\n"
+"that will be used for sending and receiving messages through the network."
+" I2P has its own internal\n"
+"network database (using a modification of the "
+"Kademlia algorithm) for\n"
+"distributing routing and contact information securely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:74
+msgid "Network topology example"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:76
+msgid ""
+"In the above, Alice, Bob, Charlie, and Dave are all running routers with "
+"a single Destination on\n"
+"their local router. They each have a pair of 2-hop inbound tunnels per "
+"destination (labeled 1, 2, 3,\n"
+"4, 5 and 6), and a small subset of each of those router's outbound tunnel"
+" pool is shown with 2-hop\n"
+"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's "
+"outbound tunnels are not\n"
+"shown, nor are the rest of each router's outbound tunnel pool (typically "
+"stocked with a few tunnels\n"
+"at a time). When Alice and Bob talk to each other, Alice sends a message "
+"out one of her (pink)\n"
+"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3"
+" or 4). She knows to send\n"
+"to those tunnels on the correct router by querying the network database, "
+"which is constantly updated\n"
+"as new leases are authorized and old ones expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:88
+#, python-format
+msgid ""
+"If Bob wants to reply to Alice, he simply goes through the same process -"
+" send a message out one of\n"
+"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 "
+"or 2). To make things\n"
+"easier, most messages sent between Alice and Bob are garlic\n"
+"wrapped, bundling the sender's own current lease information so that the "
+"recipient can reply\n"
+"immediately without having to look in the network database for the "
+"current data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:96
+#, python-format
+msgid ""
+"To deal with a wide range of attacks, I2P is fully distributed with no "
+"centralized resources - and\n"
+"hence there are no directory servers keeping statistics regarding the "
+"performance and reliability of\n"
+"routers within the network. As such, each router must keep and maintain "
+"profiles of various routers\n"
+"and is responsible for selecting appropriate peers to meet the anonymity,"
+" performance, and\n"
+"reliability needs of the users, as described in the peer selection\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:105
+#, python-format
+msgid ""
+"The network itself makes use of a significant number of cryptographic\n"
+"techniques and algorithms - a full laundry list includes 2048bit "
+"ElGamal encryption, 256bit AES\n"
+"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, "
+"2048bit Diffie-Hellman\n"
+"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:113
+msgid ""
+"Content sent over I2P is encrypted through three layers garlic encryption"
+" (used to verify the\n"
+"delivery of the message to the recipient), tunnel encryption (all "
+"messages passing through a tunnel\n"
+"is encrypted by the tunnel gateway to the tunnel endpoint), and inter "
+"router transport layer\n"
+"encryption (e.g. the TCP transport uses AES256 with ephemeral keys)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:120
+msgid ""
+"End-to-end (I2CP) encryption (client application to server application) "
+"was disabled in I2P release\n"
+"0.6; end-to-end (garlic) encryption (I2P client router to I2P server "
+"router) from Alice's router \"a\"\n"
+"to Bob's router \"h\" remains. Notice the different use of terms! All "
+"data from a to h is end-to-end\n"
+"encrypted, but the I2CP connection between the I2P router and the "
+"applications is not end-to-end\n"
+"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob "
+"in following chart are the\n"
+"applications running atop of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:129
+msgid "End to end layered encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:131
+#, python-format
+msgid ""
+"The specific use of these algorithms are outlined elsewhere."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:135
+msgid ""
+"The two main mechanisms for allowing people who need strong anonymity to "
+"use the network are\n"
+"explicitly delayed garlic routed messages and more comprehensive tunnels "
+"to include support for\n"
+"pooling and mixing messages. These are currently planned for release 3.0,"
+" but garlic routed messages\n"
+"with no delays and FIFO tunnels are currently in place. Additionally, the"
+" 2.0 release will allow\n"
+"people to set up and operate behind restricted routes (perhaps with "
+"trusted peers), as well as the\n"
+"deployment of more flexible and anonymous transports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:144
+#, python-format
+msgid ""
+"Some questions have been raised with regards to the scalability of I2P, "
+"and reasonably so. There\n"
+"will certainly be more analysis over time, but peer lookup and "
+"integration should be bounded by\n"
+"O(log(N)) due to the network "
+"database's algorithm, while end\n"
+"to end messages should be O(1) (scale free), since messages "
+"go out K hops through the\n"
+"outbound tunnel and another K hops through the inbound tunnel, with K no "
+"longer than 3. The size of\n"
+"the network (N) bears no impact."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:153
+msgid "When?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:154
+#, python-format
+msgid ""
+"I2P initially began in Feb 2003 as a proposed modification to Freenet to allow it to use "
+"alternate transports, such as JMS, then grew into its own as an\n"
+"'anonCommFramework' in April 2003, turning into I2P in July, with code "
+"being written in earnest\n"
+"starting in August '03. I2P is currently under development, following the"
+" roadmap."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:164
+msgid "Who?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:165
+#, python-format
+msgid ""
+"We have a small team spread around several "
+"continents, working to advance\n"
+"different aspects of the project. We are very open to other developers "
+"who want to get involved and\n"
+"anyone else who would like to contribute in other ways, such as "
+"critiques, peer review, testing,\n"
+"writing I2P enabled applications, or documentation. The entire system is "
+"open source - the router\n"
+"and most of the SDK are outright public domain with some BSD and Cryptix "
+"licensed code, while some\n"
+"applications like I2PTunnel and I2PSnark are GPL. Almost everything is "
+"written in Java (1.5+),\n"
+"though some third party applications are being written in Python and "
+"other languages. The code works\n"
+"on Sun Java SE and other Java Virtual"
+" Machines."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:176
+msgid "Where?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:177
+#, python-format
+msgid ""
+"Anyone interested should join us on the IRC channel #i2p (hosted "
+"concurrently on irc.freenode.net,\n"
+"irc.postman.i2p, irc.freshcoffee.i2p, irc.welterde.i2p and "
+"irc.einirc.de). There are currently no\n"
+"scheduled development meetings, however archives"
+" are available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:183
+#, python-format
+msgid "The current source is available in monotone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:188
+#, python-format
+msgid "See the Index to Technical Documentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:2
+msgid "The Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:3
+#: i2p2www/pages/site/docs/spec/updates.html:3
+msgid "October 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:8
+msgid ""
+"I2P's netDb is a specialized distributed database, containing \n"
+"just two types of data - router contact information (RouterInfos) "
+"and destination contact\n"
+"information (LeaseSets). Each piece of data is signed by the "
+"appropriate party and verified\n"
+"by anyone who uses or stores it. In addition, the data has liveliness "
+"information\n"
+"within it, allowing irrelevant entries to be dropped, newer entries to "
+"replace\n"
+"older ones, and protection against certain classes of attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:17
+msgid ""
+"The netDb is distributed with a simple technique called \"floodfill\",\n"
+"where a subset of all routers, called \"floodfill routers\", maintains "
+"the distributed database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:25
+msgid ""
+"When an I2P router wants to contact another router, they need to know "
+"some \n"
+"key pieces of data - all of which are bundled up and signed by the router"
+" into\n"
+"a structure called the \"RouterInfo\", which is distributed with the "
+"SHA256 of the router's identity\n"
+"as the key. The structure itself contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:32
+msgid ""
+"The router's identity (a 2048bit ElGamal encryption key, a 1024bit DSA "
+"signing key, and a certificate)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:33
+msgid ""
+"The contact addresses at which it can be reached (e.g. TCP: example.org "
+"port 4108)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:34
+msgid "When this was published"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:35
+msgid "A set of arbitrary text options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:36
+msgid "The signature of the above, generated by the identity's DSA signing key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:39
+msgid ""
+"The following text options, while not strictly required, are expected\n"
+"to be present:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:45
+msgid ""
+"Capabilities flags - used to indicate floodfill participation, "
+"approximate bandwidth, and perceived reachability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:47
+msgid "SSU Testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:48
+msgid "SSU Introducer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:49
+#: i2p2www/pages/site/docs/how/network-database.html:246
+msgid "Floodfill"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:50
+msgid "Hidden"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:51
+#, python-format
+msgid "Under %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+#: i2p2www/pages/site/docs/how/network-database.html:53
+#: i2p2www/pages/site/docs/how/network-database.html:54
+#, python-format
+msgid "%(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+msgid "default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:55
+#, python-format
+msgid "Over %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:56
+msgid "Reachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:57
+msgid "Unreachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:62
+msgid "The core library version, always the same as the router version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:65
+msgid ""
+"Basic network compatibility - A router will refuse to communicate with a "
+"peer having a different netId"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:68
+msgid "Used to determine compatibility with newer features and messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:71
+msgid ""
+"Always sent as 90m, for compatibility with an older scheme where routers "
+"published their actual uptime,\n"
+"and only sent tunnel requests to peers whose was more than 60m"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:76
+msgid ""
+"These values are used by other routers for basic decisions.\n"
+"Should we connect to this router? Should we attempt to route a tunnel "
+"through this router?\n"
+"The bandwidth capability flag, in particular, is used only to determine "
+"whether\n"
+"the router meets a minimum threshold for routing tunnels.\n"
+"Above the minimum threshold, the advertised bandwidth is not used or "
+"trusted anywhere\n"
+"in the router, except for display in the user interface and for debugging"
+" and network analysis."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:86
+#, python-format
+msgid ""
+"Additional text options include\n"
+"a small number of statistics about the router's health, which are "
+"aggregated by\n"
+"sites such as %(stats)s\n"
+"for network performance analysis and debugging.\n"
+"These statistics were chosen to provide data crucial to the developers,\n"
+"such as tunnel build success rates, while balancing the need for such "
+"data\n"
+"with the side-effects that could result from revealing this data.\n"
+"Current statistics are limited to:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:97
+msgid "Client and exploratory tunnel build success, reject, and timeout rates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:98
+msgid "1 hour average number of participating tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:101
+msgid ""
+"The data published can be seen in the router's user interface,\n"
+"but is not used or trusted within the router.\n"
+"As the network has matured, we have gradually removed most of the "
+"published\n"
+"statistics to improve anonymity, and we plan to remove more in future "
+"releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:109
+msgid "RouterInfo specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:112
+msgid "RouterInfo Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:115
+msgid "RouterInfo Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:116
+msgid ""
+"RouterInfos have no set expiration time.\n"
+"Each router is free to maintain its own local policy to trade off the "
+"frequency of RouterInfo lookups\n"
+"with memory or disk usage.\n"
+"In the current implementation, there are the following general policies:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:123
+msgid ""
+"There is no expiration during the first hour of uptime, as the persistent"
+" stored data may be old."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:126
+msgid "There is no expiration if there are 25 or less RouterInfos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:129
+msgid ""
+"As the number of local RouterInfos grows, the expiration time shrinks, in"
+" an attempt to maintain\n"
+"a reasonable number RouterInfos. The expiration time with less than 120 "
+"routers is 72 hours,\n"
+"while expiration time with 300 routers is around 30 hours."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:134
+#, python-format
+msgid ""
+"RouterInfos containing SSU introducers expire in "
+"about an hour, as\n"
+"the introducer list expires in about that time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:138
+msgid ""
+"Floodfills use a short expiration time (1 hour) for all local "
+"RouterInfos, as valid RouterInfos will\n"
+"be frequently republished to them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:144
+msgid "RouterInfo Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:146
+msgid ""
+"RouterInfos are periodically written to disk so that they are available "
+"after a restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:153
+msgid ""
+"The second piece of data distributed in the netDb is a \"LeaseSet\" - "
+"documenting\n"
+"a group of tunnel entry points (leases) for a particular client "
+"destination.\n"
+"Each of these leases specify the following information:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:159
+msgid "The tunnel gateway router (by specifying its identity)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:160
+msgid "The tunnel ID on that router to send messages with (a 4 byte number)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:161
+msgid "When that tunnel will expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:163
+msgid ""
+"The LeaseSet itself is stored in the netDb under\n"
+"the key derived from the SHA256 of the destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:168
+msgid "In addition to these leases, the LeaseSet includes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:172
+msgid ""
+"The destination itself (a 2048bit ElGamal encryption key, 1024bit DSA "
+"signing key and a certificate)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:173
+msgid ""
+"Additional encryption public key: used for end-to-end encryption of "
+"garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:174
+msgid ""
+"Additional signing public key: intended for LeaseSet revocation, but is "
+"currently unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:175
+msgid ""
+"Signature of all the LeaseSet data, to make sure the Destination "
+"published the LeaseSet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:179
+msgid "Lease specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:181
+msgid "LeaseSet specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:184
+msgid "Lease Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:186
+msgid "LeaseSet Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:190
+msgid "Unpublished LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:191
+msgid ""
+"A LeaseSet for a destination used only for outgoing connections is "
+"unpublished.\n"
+"It is never sent for publication to a floodfill router.\n"
+"\"Client\" tunnels, such as those for web browsing and IRC clients, are "
+"unpublished.\n"
+"Servers will still be able to send messages back to those unpublished "
+"destinations,\n"
+"because of I2NP storage messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:201
+msgid "Revoked LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:202
+msgid ""
+"A LeaseSet may be revoked by publishing a new LeaseSet with zero "
+"leases.\n"
+"Revocations must be signed by the additional signing key in the LeaseSet."
+"\n"
+"Revocations are not fully implemented, and it is unclear if they have any"
+" practical use.\n"
+"This is the only planned use for that signing key, so it is currently "
+"unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:209
+msgid "Encrypted LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:210
+msgid ""
+"In an encrypted LeaseSet, all Leases are encrypted with a separate"
+" DSA key.\n"
+"The leases may only be decoded, and thus the destination may only be "
+"contacted,\n"
+"by those with the key.\n"
+"There is no flag or other direct indication that the LeaseSet is "
+"encrypted.\n"
+"Encrypted LeaseSets are not widely used, and it is a topic for future "
+"work to\n"
+"research whether the user interface and implementation of encrypted "
+"LeaseSets could be improved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:219
+msgid "LeaseSet Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:220
+msgid ""
+"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet "
+"expires\n"
+"10 minutes after the earliest creation time of all its Leases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:225
+msgid "LeaseSet Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:226
+msgid ""
+"There is no persistent storage of LeaseSet data since they expire so "
+"quickly."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:231
+msgid "Bootstrapping"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:232
+msgid ""
+"The netDb is decentralized, however you do need at\n"
+"least one reference to a peer so that the integration process\n"
+"ties you in. This is accomplished by \"reseeding\" your router with the "
+"RouterInfo\n"
+"of an active peer - specifically, by retrieving their "
+"routerInfo-$hash.dat\n"
+"file and storing it in your netDb/ directory. Anyone can "
+"provide\n"
+"you with those files - you can even provide them to others by exposing "
+"your own\n"
+"netDb directory. To simplify the process,\n"
+"volunteers publish their netDb directories (or a subset) on the regular "
+"(non-i2p) network,\n"
+"and the URLs of these directories are hardcoded in I2P.\n"
+"When the router starts up for the first time, it automatically fetches "
+"from\n"
+"one of these URLs, selected at random."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:247
+msgid ""
+"The floodfill netDb is a simple distributed storage mechanism.\n"
+"The storage algorithm is simple: send the data to the closest peer that "
+"has advertised itself\n"
+"as a floodfill router. Then wait 10 seconds, pick another floodfill "
+"router and ask them \n"
+"for the entry to be sent, verifying its proper insertion / distribution. "
+"If the \n"
+"verification peer doesn't reply, or they don't have the entry, the sender"
+" \n"
+"repeats the process. When the peer in the floodfill netDb receives a "
+"netDb \n"
+"store from a peer not in the floodfill netDb, they send it to a subset of"
+" the floodfill netDb-peers.\n"
+"The peers selected are the ones closest (according to the XOR-metric) to a specific key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:258
+msgid ""
+"Determining who is part of the floodfill netDb is trivial - it is exposed"
+" in each \n"
+"router's published routerInfo as a capability."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:263
+msgid ""
+"Floodfills have no central authority and do not form a \"consensus\" -\n"
+"they only implement a simple DHT overlay."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:270
+msgid "Floodfill Router Opt-in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:272
+msgid ""
+"Unlike Tor, where the directory servers are hardcoded and trusted,\n"
+"and operated by known entities,\n"
+"the members of the I2P floodfill peer set need not be trusted, and\n"
+"change over time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:279
+msgid ""
+"To increase reliability of the netDb, and minimize the impact\n"
+"of netDb traffic on a router, floodfill is automatically enabled\n"
+"only on routers that are configured with high bandwidth limits.\n"
+"Routers with high bandwidth limits (which must be manually configured,\n"
+"as the default is much lower) are presumed to be on lower-latency\n"
+"connections, and are more likely to be available 24/7.\n"
+"The current minimum share bandwidth for a floodfill router is 128 "
+"KBytes/sec."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:289
+msgid ""
+"In addition, a router must pass several additional tests for health\n"
+"(outbound message queue time, job lag, etc.) before floodfill operation "
+"is\n"
+"automatically enabled."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:295
+msgid ""
+"With the current rules for automatic opt-in, approximately 6% of\n"
+"the routers in the network are floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:300
+msgid ""
+"While some peers are manually configured to be floodfill,\n"
+"others are simply high-bandwidth routers who automatically volunteer\n"
+"when the number of floodfill peers drops below a threshold.\n"
+"This prevents any long-term network damage from losing most or all\n"
+"floodfills to an attack.\n"
+"In turn, these peers will un-floodfill themselves when there are\n"
+"too many floodfills outstanding."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:310
+msgid "Floodfill Router Roles"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:311
+msgid ""
+"A floodfill router's only services that are in addition to those of non-"
+"floodfill routers\n"
+"are in accepting netDb stores and responding to netDb queries.\n"
+"Since they are generally high-bandwidth, they are more likely to "
+"participate in a high number of tunnels\n"
+"(i.e. be a \"relay\" for others), but this is not directly related to "
+"their distributed database services."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:319
+msgid "Kademlia Closeness Metric"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:320
+msgid ""
+"The netDb uses a simple Kademlia-style XOR metric to determine closeness."
+"\n"
+"The SHA256 hash of the key being looked up or stored is XOR-ed with\n"
+"the hash of the router in question to determine closeness.\n"
+"A modification to this algorithm is done to increase the costs of Sybil attacks.\n"
+"Instead of the SHA256 hash of the key being looked up of stored, the "
+"SHA256 hash is taken\n"
+"of the 32-byte binary key appended with the UTC date represented as an "
+"8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n"
+"This is called the \"routing key\", and it changes every day at midnight "
+"UTC.\n"
+"The daily transformation of the DHT is sometimes called \"keyspace "
+"rotation\",\n"
+"although it isn't strictly a rotation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:332
+msgid ""
+"Routing keys are never sent on-the-wire in any I2NP message, they are "
+"only used locally for\n"
+"determination of distance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:339
+msgid "Storage, Verification, and Lookup Mechanics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:341
+msgid "RouterInfo Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:342
+#, python-format
+msgid ""
+"I2NP DatabaseStoreMessages containing the local "
+"RouterInfo are exchanged with peers\n"
+"as a part of the initialization of a NTCP\n"
+"or SSU transport connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:349
+msgid "LeaseSet Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:350
+#, python-format
+msgid ""
+"I2NP DatabaseStoreMessages containing the local "
+"LeaseSet are periodically exchanged with peers\n"
+"by bundling them in a garlic message along with normal traffic from the "
+"related Destination.\n"
+"This allows an initial response, and later responses, to be sent to an "
+"appropriate Lease,\n"
+"without requiring any LeaseSet lookups, or requiring the communicating "
+"Destinations to have published LeaseSets at all."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:358
+msgid ""
+"The DatabaseStoreMessage should be sent to the floodfill that is closest\n"
+"to the current routing key for the RouterInfo or LeaseSet being stored.\n"
+"Currently, the closest floodfill is found by a search in the local "
+"database.\n"
+"Even if that floodfill is not actually closest, it will flood it "
+"\"closer\" by\n"
+"sending it to multiple other floodfills.\n"
+"This provides a high degree of fault-tolerance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:367
+msgid ""
+"In traditional Kademlia, a peer would do a \"find-closest\" search before"
+" inserting\n"
+"an item in the DHT to the closest target. As the verify operation will "
+"tend to\n"
+"discover closer floodfills if they are present, a router will quickly "
+"improve\n"
+"its knowledge of the DHT \"neighborhood\" for the RouterInfo and "
+"LeaseSets it regularly publishes.\n"
+"While I2NP does not define a \"find-closest\" message, if it becomes "
+"necessary,\n"
+"a router may simply do an iterative search for a key with the least "
+"significant bit flipped\n"
+"(i.e. key ^ 0x01) until no closer peers are received in the "
+"DatabaseSearchReplyMessages.\n"
+"This ensures that the true closest peer will be found even if a more-"
+"distant peer had\n"
+"the netdb item."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:380
+msgid "RouterInfo Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:381
+#, python-format
+msgid ""
+"A router publishes its own RouterInfo by directly connecting to a "
+"floodfill router\n"
+"and sending it a I2NP DatabaseStoreMessage\n"
+"with a nonzero Reply Token. The message is not end-to-end garlic "
+"encrypted,\n"
+"as this is a direct connection, so there are no intervening routers\n"
+"(and no need to hide this data anyway).\n"
+"The floodfill router replies with a\n"
+"I2NP DeliveryStatusMessage,\n"
+"with the Message ID set to the value of the Reply Token."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:395
+msgid "LeaseSet Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:396
+msgid ""
+"Storage of LeaseSets is much more sensitive than for RouterInfos, as a "
+"router\n"
+"must take care that the LeaseSet cannot be associated with the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:401
+#, python-format
+msgid ""
+"A router publishes a local LeaseSet by\n"
+"sending a I2NP DatabaseStoreMessage\n"
+"with a nonzero Reply Token over an outbound client tunnel for that "
+"Destination.\n"
+"The message is end-to-end garlic encrypted using the Destination's "
+"Session Key Manager,\n"
+"to hide the message from the tunnel's outbound endpoint.\n"
+"The floodfill router replies with a\n"
+"I2NP DeliveryStatusMessage,\n"
+"with the Message ID set to the value of the Reply Token.\n"
+"This message is sent back to one of the client's inbound tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:414
+msgid "Flooding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:415
+#, python-format
+msgid ""
+"After a floodfill router receives a DatabaseStoreMessage containing a\n"
+"valid RouterInfo or LeaseSet which is newer than that previously stored "
+"in its\n"
+"local NetDb, it \"floods\" it.\n"
+"To flood a NetDb entry, it looks up several (currently %(floodsize)s) "
+"floodfill routers closest to the routing key\n"
+"of the NetDb entry. (The routing key is the SHA256 Hash of the "
+"RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n"
+"By flooding to those closest to the key, not closest to itself, the "
+"floodfill ensures that the storage\n"
+"gets to the right place, even if the storing router did not have good "
+"knowledge of the\n"
+"DHT \"neighborhood\" for the routing key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:426
+#, python-format
+msgid ""
+"The floodfill then directly connects to each of those peers\n"
+"and sends it a I2NP DatabaseStoreMessage\n"
+"with a zero Reply Token. The message is not end-to-end garlic encrypted,\n"
+"as this is a direct connection, so there are no intervening routers\n"
+"(and no need to hide this data anyway).\n"
+"The other routers do not reply or re-flood, as the Reply Token is zero."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:436
+msgid "RouterInfo and LeaseSet Lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:437
+#, python-format
+msgid ""
+"The I2NP DatabaseLookupMessage is used to "
+"request a netdb entry from a floodfill router.\n"
+"Lookups are sent out one of the router's outbound exploratory tunnels.\n"
+"The replies are specified to return via one of the router's inbound "
+"exploratory tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:443
+msgid ""
+"Lookups are generally sent to the two \"good\" (the connection doesn't "
+"fail) floodfill routers closest to the requested key, in parallel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:447
+#, python-format
+msgid ""
+"If the key is found locally by the floodfill router, it responds with a\n"
+"I2NP DatabaseStoreMessage.\n"
+"If the key is not found locally by the floodfill router, it responds with"
+" a\n"
+"I2NP DatabaseSearchReplyMessage\n"
+"containing a list of other floodfill routers close to the key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:455
+msgid ""
+"LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n"
+"RouterInfo lookups are not encrypted and thus are vulnerable to snooping "
+"by the outbound endpoint\n"
+"(OBEP) of the client tunnel. This is due to the expense of the ElGamal "
+"encryption.\n"
+"RouterInfo lookup encryption may be enabled in a future release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:462
+msgid ""
+"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage"
+" or a DatabaseSearchReplyMessage)\n"
+"will be encrypted by including the session key and tag in the lookup.\n"
+"This hides the reply from the inbound gateway (IBGW) of the reply tunnel."
+"\n"
+"Responses to RouterInfo lookups will be encrypted if we enable the lookup"
+" encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:469
+#, python-format
+msgid ""
+"(Reference: Hashing it out in Public Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:473
+msgid ""
+"Due to the relatively small size of the network and the flooding "
+"redundancy of 8x,\n"
+"lookups are usually O(1) rather than O(log n) --\n"
+"a router is highly likely to know a floodfill router close enough to the "
+"key to get the answer on the first try.\n"
+"In releases prior to 0.8.9, routers used a lookup redundancy of two\n"
+"(that is, two lookups were performed in parallel to different peers), and"
+"\n"
+"neither recursive nor iterative routing for lookups was "
+"implemented.\n"
+"Queries were sent through multiple routes simultaneously\n"
+"to reduce the chance of query failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:484
+msgid ""
+"As of release 0.8.9, iterative lookups are implemented with no "
+"lookup redundancy.\n"
+"This is a more efficient and reliable lookup that will work much better\n"
+"when not all floodfill peers are known, and it removes a serious\n"
+"limitation to network growth. As the network grows and each router knows "
+"only a small\n"
+"subset of the floodfill peers, lookups will become O(log n).\n"
+"Even if the peer does not return references closer to the key, the lookup"
+" continues with\n"
+"the next-closest peer, for added robustness, and to prevent a malicious "
+"floodfill from\n"
+"black-holing a part of the key space. Lookups continue until a total "
+"lookup timeout is reached,\n"
+"or the maximum number of peers is queried."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:496
+msgid ""
+"Node IDs are verifiable in that we use the router hash "
+"directly as both the node ID and the Kademlia key.\n"
+"Incorrect responses that are not closer to the search key are generally "
+"ignored.\n"
+"Given the current size of the network, a router has\n"
+"detailed knowledge of the neighborhood of the destination ID space."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:505
+msgid "RouterInfo Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:506
+#, python-format
+msgid ""
+"Note: RouterInfo verification is disabled as of release 0.9.7.1 to "
+"prevent\n"
+"the attack described in the paper\n"
+"Practical Attacks Against the I2P Network.\n"
+"It is not clear if verification can be redesigned to be done safely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:513
+msgid ""
+"To verify a storage was successful, a router simply waits about 10 "
+"seconds,\n"
+"then sends a lookup to another floodfill router close to the key\n"
+"(but not the one the store was sent to).\n"
+"Lookups sent out one of the router's outbound exploratory tunnels.\n"
+"Lookups are end-to-end garlic encrypted to prevent snooping by the "
+"outbound endpoint(OBEP)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:521
+msgid "LeaseSet Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:522
+msgid ""
+"To verify a storage was successful, a router simply waits about 10 "
+"seconds,\n"
+"then sends a lookup to another floodfill router close to the key\n"
+"(but not the one the store was sent to).\n"
+"Lookups sent out one of the outbound client tunnels for the destination "
+"of the LeaseSet being verified.\n"
+"To prevent snooping by the OBEP of the outbound tunnel,\n"
+"lookups are end-to-end garlic encrypted.\n"
+"The replies are specified to return via one of the client's inbound "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:532
+msgid ""
+"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a "
+"DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n"
+"will be encrypted,\n"
+"to hide the reply from the inbound gateway (IBGW) of the reply tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:540
+msgid "Exploration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:541
+#, python-format
+msgid ""
+"Exploration is a special form of netdb lookup, where a router "
+"attempts to learn about\n"
+"new routers.\n"
+"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random "
+"key.\n"
+"As this lookup will fail, the floodfill would normally respond with a\n"
+"I2NP DatabaseSearchReplyMessage containing "
+"hashes of floodfill routers close to the key.\n"
+"This would not be helpful, as the requesting router probably already "
+"knows those floodfills,\n"
+"and it would be impractical to add ALL floodfill routers to the \"don't "
+"include\" field of the lookup.\n"
+"For an exploration query, the requesting router adds a router hash of all"
+" zeros to the\n"
+"\"don't include\" field of the DatabaseLookupMessage.\n"
+"The floodfill will then respond only with non-floodfill routers close to "
+"the requested key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:555
+msgid "Notes on Lookup Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:556
+msgid ""
+"The response to a lookup request is either a Database Store Message (on "
+"success) or a\n"
+"Database Search Reply Message (on failure). The DSRM contains a 'from' "
+"router hash field\n"
+"to indicate the source of the reply; the DSM does not.\n"
+"The DSRM 'from' field is unauthenticated and may be spoofed or invalid.\n"
+"There are no other response tags. Therefore, when making multiple "
+"requests in parallel, it is\n"
+"difficult to monitor the performance of the various floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:566
+msgid "MultiHoming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:568
+msgid ""
+"Destinations may be hosted on multiple routers simultaneously, by using "
+"the same\n"
+"private and public keys (traditionally stored in eepPriv.dat files).\n"
+"As both instances will periodically publish their signed LeaseSets to the"
+" floodfill peers,\n"
+"the most recently published LeaseSet will be returned to a peer "
+"requesting a database lookup.\n"
+"As LeaseSets have (at most) a 10 minute lifetime, should a particular "
+"instance go down,\n"
+"the outage will be 10 minutes at most, and generally much less than that."
+"\n"
+"The multihoming function has been verified and is in use by several "
+"services on the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:578
+msgid "Threat Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:579
+#, python-format
+msgid ""
+"Also discussed on the threat model "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:583
+msgid ""
+"A hostile user may attempt to harm the network by\n"
+"creating one or more floodfill routers and crafting them to offer\n"
+"bad, slow, or no responses.\n"
+"Some scenarios are discussed below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:590
+msgid "General Mitigation Through Growth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:591
+#, python-format
+msgid ""
+"There are currently around %(ffcount)s floodfill routers in the network.\n"
+"Most of the following attacks will become more difficult, or have less "
+"impact,\n"
+"as the network size and number of floodfill routers increase."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:598
+msgid "General Mitigation Through Redundancy"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:599
+#, python-format
+msgid ""
+"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill"
+" routers closest to the key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:604
+msgid "Forgeries"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:605
+msgid ""
+"All netdb entries are signed by their creators, so no router may forge a\n"
+"RouterInfo or LeaseSet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:610
+msgid "Slow or Unresponsive"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:611
+#, python-format
+msgid ""
+"Each router maintains an expanded set of statistics in the\n"
+"peer profile for each floodfill router,"
+"\n"
+"covering various quality metrics for that peer.\n"
+"The set includes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:618
+msgid "Average response time"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:619
+msgid "Percentage of queries answered with the data requested"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:620
+msgid "Percentage of stores that were successfully verified"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:621
+msgid "Last successful store"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:622
+msgid "Last successful lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:623
+msgid "Last response"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:626
+msgid ""
+"Each time a router needs to make a determination on which floodfill "
+"router is closest to a key,\n"
+"it uses these metrics to determine which floodfill routers are \"good\".\n"
+"The methods, and thresholds, used to determine \"goodness\" are "
+"relatively new, and\n"
+"are subject to further analysis and improvement.\n"
+"While a completely unresponsive router will quickly be identified and "
+"avoided,\n"
+"routers that are only sometimes malicious may be much harder to deal with."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:636
+msgid "Sybil Attack (Full Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:637
+#, python-format
+msgid ""
+"An attacker may mount a Sybil attack\n"
+"by creating a large number of floodfill routers spread throughout the "
+"keyspace."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:642
+#, python-format
+msgid ""
+"(In a related example, a researcher recently created a\n"
+"large number of Tor relays.)\n"
+"If successful, this could be an effective DOS attack on the entire "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:648
+msgid ""
+"If the floodfills are not sufficiently misbehaving to be marked as "
+"\"bad\" using the peer profile\n"
+"metrics described above, this is a difficult scenario to handle.\n"
+"Tor's response can be much more nimble in the relay case, as the "
+"suspicious relays\n"
+"can be manually removed from the consensus.\n"
+"Some possible responses for the I2P network are listed below, however "
+"none of them is completely satisfactory:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:656
+msgid ""
+"Compile a list of bad router hashes or IPs, and announce the list through"
+" various means\n"
+"(console news, website, forum, etc.); users would have to manually "
+"download the list and\n"
+"add it to their local \"blacklist\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:661
+msgid ""
+"Ask everyone in the network to enable floodfill manually (fight Sybil "
+"with more Sybil)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:662
+msgid "Release a new software version that includes the hardcoded \"bad\" list"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:663
+msgid ""
+"Release a new software version that improves the peer profile metrics and"
+" thresholds,\n"
+"in an attempt to automatically identify the \"bad\" peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:667
+msgid ""
+"Add software that disqualifies floodfills if too many of them are in a "
+"single IP block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:668
+msgid ""
+"Implement an automatic subscription-based blacklist controlled by a "
+"single individual or group.\n"
+"This would essentially implement a portion of the Tor \"consensus\" "
+"model.\n"
+"Unfortunately it would also give a single individual or group the power "
+"to\n"
+"block participation of any particular router or IP in the network,\n"
+"or even to completely shutdown or destroy the entire network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:677
+msgid "This attack becomes more difficult as the network size grows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:683
+msgid "Sybil Attack (Partial Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:684
+#, python-format
+msgid ""
+"An attacker may mount a Sybil attack\n"
+"by creating a small number (8-15) of floodfill routers clustered closely "
+"in the keyspace,\n"
+"and distribute the RouterInfos for these routers widely.\n"
+"Then, all lookups and stores for a key in that keyspace would be directed"
+"\n"
+"to one of the attacker's routers.\n"
+"If successful, this could be an effective DOS attack on a particular "
+"eepsite, for example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:693
+msgid ""
+"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,"
+"\n"
+"an attacker must use a brute-force method to repeatedly generate router "
+"hashes\n"
+"until he has enough that are sufficiently close to the key.\n"
+"The amount of computational power required for this, which is dependent "
+"on network\n"
+"size, is unknown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:701
+msgid ""
+"As a partial defense against this attack,\n"
+"the algorithm used to determine Kademlia \"closeness\" varies over time.\n"
+"Rather than using the Hash of the key (i.e. H(k)) to determine closeness,"
+"\n"
+"we use the Hash of the key appended with the current date string, i.e. "
+"H(k + YYYYMMDD).\n"
+"A function called the \"routing key generator\" does this, which "
+"transforms the original key into a \"routing key\".\n"
+"In other words, the entire netdb keyspace \"rotates\" every day at UTC "
+"midnight.\n"
+"Any partial-keyspace attack would have to be regenerated every day, for\n"
+"after the rotation, the attacking routers would no longer be close\n"
+"to the target key, or to each other."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:713
+msgid ""
+"This attack becomes more difficult as the network size grows.\n"
+"However, recent research demonstrates that the keyspace rotation is not "
+"particularly effective.\n"
+"An attacker can precompute numerous router hashes in advance,\n"
+"and only a few routers are sufficient to \"eclipse\" a portion\n"
+"of the keyspace within a half hour after rotation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:721
+msgid ""
+"One consequence of daily keyspace rotation is that the distributed "
+"network database\n"
+"may become unreliable for a few minutes after the rotation --\n"
+"lookups will fail because the new \"closest\" router has not received a "
+"store yet.\n"
+"The extent of the issue, and methods for mitigation\n"
+"(for example netdb \"handoffs\" at midnight)\n"
+"are a topic for further study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:731
+msgid "Bootstrap Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:732
+msgid ""
+"An attacker could attempt to boot new routers into an isolated\n"
+"or majority-controlled network by taking over a reseed website,\n"
+"or tricking the developers into adding his reseed website\n"
+"to the hardcoded list in the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:739
+msgid "Several defenses are possible, and most of these are planned:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:743
+msgid ""
+"Disallow fallback from HTTPS to HTTP for reseeding.\n"
+"A MITM attacker could simply block HTTPS, then respond to the HTTP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:747
+msgid ""
+"Changing the reseed task to fetch a subset of RouterInfos from\n"
+"each of several reseed sites rather than using only a single site"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:751
+msgid ""
+"Creating an out-of-network reseed monitoring service that\n"
+"periodically polls reseed websites and verifies that the\n"
+"data are not stale or inconsistent with other views of the network"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:756
+msgid "Bundling reseed data in the installer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:759
+msgid "Query Capture"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:760
+#, python-format
+msgid ""
+"See also lookup\n"
+"(Reference: Hashing it out in Public Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:765
+msgid ""
+"Similar to a bootstrap attack, an attacker using a floodfill router could"
+" attempt to \"steer\"\n"
+"peers to a subset of routers controlled by him by returning their "
+"references."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:770
+msgid ""
+"This is unlikely to work via exploration, because exploration is a low-"
+"frequency task.\n"
+"Routers acquire a majority of their peer references through normal tunnel"
+" building activity.\n"
+"Exploration results are generally limited to a few router hashes,\n"
+"and each exploration query is directed to a random floodfill router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:777
+#, python-format
+msgid ""
+"As of release 0.8.9, iterative lookups are implemented.\n"
+"For floodfill router references returned in a\n"
+"I2NP DatabaseSearchReplyMessage\n"
+"response to a lookup,\n"
+"these references are followed if they are closer (or the next closest) to"
+" the lookup key.\n"
+"The requesting router does not trust that the references are\n"
+"closer to the key (i.e. they are verifiably correct.\n"
+"The lookup also does not stop when no closer key is found, but continues "
+"by querying the\n"
+"next-closet node, until the timeout or maximum number of queries is "
+"reached.\n"
+"This prevents a malicious floodfill from black-holing a part of the key "
+"space.\n"
+"Also, the daily keyspace rotation requires an attacker to regenerate a "
+"router info\n"
+"within the desired key space region.\n"
+"This design ensures that the query capture attack described in\n"
+"Hashing it out in Public\n"
+"is much more difficult."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:796
+msgid "DHT-Based Relay Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:797
+#, python-format
+msgid "(Reference: Hashing it out in Public Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:801
+#, python-format
+msgid ""
+"This doesn't have much to do with floodfill, but see\n"
+"the peer selection page\n"
+"for a discussion of the vulnerabilities of peer selection for tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:807
+msgid "Information Leaks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:808
+#, python-format
+msgid ""
+"(Reference: In Search of an Anonymous and Secure "
+"Lookup Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:812
+#, python-format
+msgid ""
+"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used "
+"by Torsk and NISAN.\n"
+"At first glance, these do not appear to apply to I2P. First, the use of "
+"DHT by Torsk and NISAN\n"
+"is significantly different from that in I2P. Second, I2P's network "
+"database lookups are only\n"
+"loosely correlated to the peer "
+"selection and\n"
+"tunnel building processes; only "
+"previously-known peers\n"
+"are used for tunnels.\n"
+"Also, peer selection is unrelated to any notion of DHT key-closeness."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:823
+msgid ""
+"Some of this may actually be more interesting when the I2P network gets "
+"much larger.\n"
+"Right now, each router knows a large proportion of the network, so "
+"looking up a particular\n"
+"Router Info in the network database is not strongly indicative of a "
+"future intent to use\n"
+"that router in a tunnel. Perhaps when the network is 100 times larger, "
+"the lookup may be\n"
+"more correlative. Of course, a larger network makes a Sybil attack that "
+"much harder."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:831
+#, python-format
+msgid ""
+"However, the general issue of DHT information leakage in I2P needs "
+"further investigation.\n"
+"The floodfill routers are in a position to observe queries and gather "
+"information.\n"
+"Certainly, at a level of f = 0.2 (20% malicious nodes, as "
+"specifed in the paper)\n"
+"we expect that many of the Sybil threats we describe\n"
+"(here,\n"
+"here and\n"
+"here)\n"
+"become problematic for several reasons."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:845
+msgid "Moved to the netdb discussion page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:849
+msgid "End-to-end encryption of additional netDb lookups and responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:853
+msgid "Better methods for tracking lookup responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:2
+msgid "Peer Profiling and Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:3
+msgid "July 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:8
+msgid "Peer Profiling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:10
+#, python-format
+msgid ""
+"Peer profiling is the process of collecting data based on the "
+"observed performance\n"
+"of other routers or peers, and classifying those peers into groups.\n"
+"Profiling does not use any claimed performance data published by "
+"the peer itself\n"
+"in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:17
+msgid "Profiles are used for two purposes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:19
+msgid "Selecting peers to relay our traffic through, which is discussed below"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:20
+#, python-format
+msgid ""
+"Choosing peers from the set of floodfill routers to use for network "
+"database storage and queries,\n"
+"which is discussed on the network database page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:27
+#: i2p2www/pages/site/docs/how/peer-selection.html:187
+#: i2p2www/pages/site/docs/tunnels/implementation.html:286
+msgid "Peer Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:28
+msgid ""
+"Peer selection is the process of choosing which routers\n"
+"on the network we want to relay our messages to go through (which peers "
+"will we \n"
+"ask to join our tunnels).  To accomplish this, we keep track of how each\n"
+"peer performs (the peer's \"profile\") and use that data to estimate how"
+" \n"
+"fast they are, how often they will be able to accept our requests, and \n"
+"whether they seem to be overloaded or otherwise unable to perform what\n"
+"they agree to reliably."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:38
+#, python-format
+msgid ""
+"Unlike some other anonymous networks, in I2P,\n"
+"claimed bandwidth is untrusted and is only used to avoid those "
+"peers\n"
+"advertising very low bandwidth insufficient for routing tunnels.\n"
+"All peer selection is done through profiling.\n"
+"This prevents simple attacks based on peers claiming high bandwidth\n"
+"in order to capture large numbers of tunnels.\n"
+"It also makes\n"
+"timing attacks\n"
+"more difficult."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:50
+msgid ""
+"Peer selection is done quite frequently, as a router may maintain a large"
+" number\n"
+"of client and exploratory tunnels, and a tunnel lifetime is only 10 "
+"minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:56
+msgid "Further Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:57
+#, python-format
+msgid ""
+"For more information see the paper\n"
+"Peer Profiling and Selection in the I2P Anonymous "
+"Network\n"
+"presented at PET-CON 2009.1.\n"
+"See below for notes on minor changes since the "
+"paper was published."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:65
+msgid "Profiles"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:66
+#, python-format
+msgid ""
+"Each peer has a set of data points collected about them, including "
+"statistics \n"
+"about how long it takes for them to reply to a network database query, "
+"how \n"
+"often their tunnels fail, and how many new peers they are able to "
+"introduce \n"
+"us to, as well as simple data points such as when we last heard from them"
+" or\n"
+"when the last communication error occurred.  The specific data points "
+"gathered\n"
+"can be found in the code."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:75
+msgid ""
+"Profiles are fairly small, a few KB. To control memory usage, the profile"
+" expiration time\n"
+"lessens as the number of profiles grows.\n"
+"Profiles are kept in memory until router shutdown, when they are written "
+"to disk.\n"
+"At startup, the profiles are read so the router need not reinitialize all"
+" profiles,\n"
+"thus allowing a router to quickly re-integrate into the network after "
+"startup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:85
+msgid "Peer Summaries"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:86
+msgid ""
+"While the profiles themselves can be considered a summary of a peer's \n"
+"performance, to allow for effective peer selection we break each summary "
+"down \n"
+"into four simple values, representing the peer's speed, its capacity, how"
+" well \n"
+"integrated into the network it is, and whether it is failing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:93
+msgid "Speed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:94
+msgid ""
+"The speed calculation\n"
+"simply goes through the profile and estimates how much data we can\n"
+"send or receive on a single tunnel through the peer in a minute.  For "
+"this estimate it just looks at\n"
+"performance in the previous minute."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:101
+msgid "Capacity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:102
+msgid ""
+"The capacity calculation\n"
+"simply goes through the profile and estimates how many tunnels the peer\n"
+"would agree to participate in over a given time period.  For this "
+"estimate it looks at \n"
+"how many tunnel build requests\n"
+"the peer has accepted, rejected, and dropped, and how many\n"
+"of the agreed-to tunnels later failed.\n"
+"While the calculation is time-weighted so that recent activity counts "
+"more than later activity,\n"
+"statistics up to 48 hours old may be included."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:113
+msgid ""
+"Recognizing and avoiding unreliable and unreachable\n"
+"peers is critically important.\n"
+"Unfortunately, as the tunnel building and testing require the "
+"participation of several peers,\n"
+"it is difficult to positively identify the cause of a dropped build "
+"request or test failure.\n"
+"The router assigns a probability of failure to each of the\n"
+"peers, and uses that probability in the capacity calculation.\n"
+"Drops and test failures are weighted much higher than rejections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:123
+msgid "Peer organization"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:124
+msgid ""
+"As mentioned above, we drill through each peer's profile to come up with "
+"a \n"
+"few key calculations, and based upon those, we organize each peer into "
+"three\n"
+"groups - fast, high capacity, and standard."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:130
+msgid "The groupings are not mutually exclusive, nor are they unrelated:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:134
+msgid ""
+"A peer is considered \"high capacity\" if its capacity calculation meets "
+"or \n"
+"exceeds the median of all peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:138
+msgid ""
+"A peer is considered \"fast\" if they are already \"high capacity\" and "
+"their \n"
+"speed calculation meets or exceeds the median of all peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:142
+msgid "A peer is considered \"standard\" if it is not \"high capacity\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:145
+#, python-format
+msgid ""
+"These groupings are implemented in the router's\n"
+"ProfileOrganizer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:150
+msgid "Group size limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:151
+msgid "The size of the groups may be limited."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:156
+msgid ""
+"The fast group is limited to 30 peers.\n"
+"If there would be more, only the ones with the highest speed rating are "
+"placed in the group."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:160
+msgid ""
+"The high capacity group is limited to 75 peers (including the fast group)"
+"\n"
+"If there would be more, only the ones with the highest capacity rating "
+"are placed in the group."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:164
+msgid ""
+"The standard group has no fixed limit, but is somewhat smaller than the "
+"number of RouterInfos\n"
+"stored in the local network database.\n"
+"On an active router in today's network, there may be about 1000 "
+"RouterInfos and 500 peer profiles\n"
+"(including those in the fast and high capacity groups)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:172
+msgid "Recalculation and Stability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:173
+msgid ""
+"Summaries are recalculated, and peers are resorted into groups, every 45 "
+"seconds."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:177
+msgid ""
+"The groups tend to be fairly stable, that is, there is not much \"churn\""
+" in the rankings\n"
+"at each recalculation.\n"
+"Peers in the fast and high capacity groups get more tunnels build through"
+" them, which increases their speed and capacity ratings,\n"
+"which reinforces their presence in the group."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:188
+msgid "The router selects peers from the above groups to build tunnels through."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:193
+msgid "Peer Selection for Client Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:194
+msgid ""
+"Client tunnels are used for application traffic, such as for HTTP proxies"
+" and web servers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:198
+msgid ""
+"To reduce the susceptibility to some attacks,\n"
+"and increase performance,\n"
+"peers for building client tunnels are chosen randomly from the smallest "
+"group, which is the \"fast\" group.\n"
+"There is no bias toward selecting peers that were previously participants"
+" in a tunnel for the same client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:206
+msgid "Peer Selection for Exploratory Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:207
+msgid ""
+"Exploratory tunnels are used for router administrative purposes, such as "
+"network database traffic\n"
+"and testing client tunnels.\n"
+"Exploratory tunnels are also used to contact previously unconnected "
+"routers, which is why\n"
+"they are called \"exploratory\".\n"
+"These tunnels are usually low-bandwidth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:215
+msgid ""
+"Peers for building exploratory tunnels are generally chosen randomly from"
+" the standard group.\n"
+"If the success rate of these build attempts is low compared to the client"
+" tunnel build success rate,\n"
+"the router will select a weighted average of peers randomly from the high"
+" capacity group instead.\n"
+"This helps maintain a satisfactory build success rate even when network "
+"performance is poor.\n"
+"There is no bias toward selecting peers that were previously participants"
+" in an exploratory tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:223
+msgid ""
+"As the standard group includes a very large subset of all peers the "
+"router knows about,\n"
+"exploratory tunnels are essentially built through a random selection of "
+"all peers,\n"
+"until the build success rate becomes too low."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:231
+msgid "Restrictions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:232
+msgid ""
+"To prevent some simple attacks, and for performance, there are the "
+"following restrictions:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:236
+msgid "Two peers from the same /16 IP space may not be in the same tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:239
+msgid ""
+"A peer may participate in a maximum of 33% of all tunnels created by "
+"the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:242
+msgid "Peers with extremely low bandwidth are not used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:245
+msgid "Peers for which a recent connection attempt failed are not used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:252
+msgid "Peer Ordering in Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:253
+#, python-format
+msgid ""
+"Peers are ordered within tunnels to\n"
+"to deal with the predecessor attack\n"
+"(2008 update).\n"
+"More information is on the tunnel "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:268
+msgid "Continue to analyze an tune speed and capacity calculations as necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:271
+msgid ""
+"Implement a more aggressive ejection strategy if necessary to control "
+"memory usage as the network grows"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:274
+msgid "Evaluate group size limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:277
+msgid "Use GeoIP data to include or exclude certain peers, if configured"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:283
+#, python-format
+msgid ""
+"For those reading the paper\n"
+"Peer Profiling and Selection in the I2P Anonymous "
+"Network,\n"
+"please keep in mind the following minor changes in I2P since the paper's "
+"publication:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:289
+msgid "The Integration calculation is still not used"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:290
+msgid "In the paper, \"groups\" are called \"tiers\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:291
+msgid "The \"Failing\" tier is no longer used"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:292
+msgid "The \"Not Failing\" tier is now named \"Standard\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:301
+msgid "One Cell Enough"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:303
+msgid "Tor Entry Guards"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:305
+msgid "Murdoch 2007 Paper"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:307
+msgid "Tune-up for Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:309
+msgid "Low-resource Routing Attacks Against Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:2
+msgid "Introducing I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:5
+msgid "I2P: A scalable framework for anonymous communication"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:7
+msgid "Table of Contents"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:9
+#: i2p2www/pages/site/docs/how/tech-intro.html:24
+#: i2p2www/pages/site/docs/transport/ssu.html:281
+msgid "Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:11
+msgid "I2P Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:16
+#: i2p2www/pages/site/docs/how/tech-intro.html:401
+msgid "Transport protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:17
+#: i2p2www/pages/site/docs/how/tech-intro.html:458
+msgid "Cryptography"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:25
+msgid ""
+"I2P is a scalable, self organizing, resilient packet switched anonymous \n"
+"network layer, upon which any number of different anonymity or security "
+"conscious \n"
+"applications can operate. Each of these applications may make their own "
+"anonymity, \n"
+"latency, and throughput tradeoffs without worrying about the proper "
+"implementation \n"
+"of a free route mixnet, allowing them to blend their activity with the "
+"larger \n"
+"anonymity set of users already running on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:34
+msgid ""
+"Applications available already provide the full range of typical Internet"
+" activities -\n"
+"anonymous web browsing, web hosting, chat, file sharing, e-mail,\n"
+"blogging and content syndication, newsgroups, as well as several other "
+"applications under development."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:40
+msgid "Web browsing: using any existing browser that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:41
+msgid "Chat: IRC, Jabber, I2P-Messenger."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:42
+msgid ""
+"File sharing: I2PSnark, Robert, iMule, \n"
+"I2Phex, PyBit, I2P-bt\n"
+"and others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:47
+msgid ""
+"E-mail: susimail and I2P-Bote."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:48
+msgid ""
+"Blog: using e.g. the pebble plugin or the distributed blogging software "
+"Syndie."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:49
+msgid ""
+"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS "
+"cloud over I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:50
+msgid "Newsgroups: using any newsgroup reader that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:53
+msgid ""
+"Unlike web sites hosted within content distribution networks like Freenet \n"
+"or GNUnet, the services "
+"hosted on \n"
+"I2P are fully interactive - there are traditional web-style search "
+"engines, \n"
+"bulletin boards, blogs you can comment on, database driven sites, and "
+"bridges \n"
+"to query static systems like Freenet without needing to install it "
+"locally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:61
+msgid ""
+"With all of these anonymity enabled applications, I2P takes on the role \n"
+"of the message oriented middleware - applications say that they want to "
+"send \n"
+"some data to a cryptographic identifier (a \"destination\") and I2P takes"
+" care \n"
+"of making sure it gets there securely and anonymously. I2P also bundles a"
+" \n"
+"simple streaming library to allow I2P's "
+"anonymous \n"
+"best-effort messages to transfer as reliable, in-order streams, "
+"transparently \n"
+"offering a TCP based congestion control algorithm tuned for the high "
+"bandwidth \n"
+"delay product of the network. While there have been several simple SOCKS "
+"proxies \n"
+"available to tie existing applications into the network, their value has "
+"been \n"
+"limited as nearly every application routinely exposes what, in an "
+"anonymous \n"
+"context, is sensitive information. The only safe way to go is to fully "
+"audit \n"
+"an application to ensure proper operation and to assist in that we "
+"provide \n"
+"a series of APIs in various languages which can be used to make the most "
+"out \n"
+"of the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:78
+#, python-format
+msgid ""
+"I2P is not a research project - academic, commercial, or governmental, "
+"but \n"
+"is instead an engineering effort aimed at doing whatever is necessary to "
+"provide \n"
+"a sufficient level of anonymity to those who need it. It has been in "
+"active \n"
+"development since early 2003 with one full time developer and a dedicated"
+" \n"
+"group of part time contributors from all over the world. All of the work "
+"done \n"
+"on I2P is open source and freely available on the website, \n"
+"with the majority of the code released outright into the public domain, "
+"though \n"
+"making use of a few cryptographic routines under BSD-style licenses. The "
+"people \n"
+"working on I2P do not control what people release client applications "
+"under, \n"
+"and there are several GPL'ed applications available (I2PTunnel, \n"
+"susimail, I2PSnark, I2P-"
+"Bote, \n"
+"I2Phex and others.).\n"
+"Funding for I2P comes entirely from "
+"donations,\n"
+"and does not receive any tax breaks in any jurisdiction at this time,\n"
+"as many of the developers are themselves anonymous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:96
+msgid "Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:98
+msgid ""
+"To understand I2P's operation, it is essential to understand a few key "
+"concepts. \n"
+"First, I2P makes a strict separation between the software participating "
+"in \n"
+"the network (a \"router\") and the anonymous endpoints (\"destinations\")"
+" associated \n"
+"with individual applications. The fact that someone is running I2P is not"
+" \n"
+"usually a secret. What is hidden is information on what the user is "
+"doing, \n"
+"if anything at all, as well as what router a particular destination is "
+"connected \n"
+"to. End users will typically have several local destinations on their "
+"router \n"
+"- for instance, one proxying in to IRC servers, another supporting the "
+"user's \n"
+"anonymous webserver (\"eepsite\"), another for an I2Phex instance, "
+"another for \n"
+"torrents, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:111
+msgid ""
+"Another critical concept to understand is the \"tunnel\".\n"
+"A tunnel is a directed path through an explicitly selected list of "
+"routers.\n"
+"Layered encryption is used, so each of the routers can only decrypt a "
+"single layer.\n"
+"The decrypted information contains the IP of the next router, along with\n"
+"the encrypted information to be forwarded.\n"
+"Each tunnel has a starting point (the first router, also known as "
+"\"gateway\")\n"
+"and an end point. Messages can be sent only in one way. To send messages "
+"back,\n"
+"another tunnel is required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:122
+#: i2p2www/pages/site/docs/tunnels/implementation.html:105
+msgid "Inbound and outbound tunnel schematic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:124
+msgid "Figure 1: Two types of tunnels exist: inbound and outbound."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:127
+msgid ""
+"Two types of tunnels exist:\n"
+"\"outbound\" tunnels send messages away from the tunnel creator,\n"
+"while \"inbound\" tunnels bring messages to the tunnel creator.\n"
+"Combining these two tunnels allows users to send messages to each other.\n"
+"The sender (\"Alice\" in the above image) sets up an outbound tunnel,\n"
+"while the receiver (\"Bob\" in the above image) creates an inbound "
+"tunnel.\n"
+"The gateway of an inbound tunnel can receive messages from any other user"
+"\n"
+"and will send them on until the endpoint (\"Bob\").\n"
+"The endpoint of the outbound tunnel will need to send the message\n"
+"on to the gateway of the inbound tunnel.\n"
+"To do this, the sender (\"Alice\") adds instructions to her encrypted "
+"message.\n"
+"Once the endpoint of the outbound tunnel decrypts the message,\n"
+"it will have instructions to forward the message to the correct\n"
+"inbound gateway (the gateway to \"Bob\")."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:144
+msgid ""
+"A third critical concept to understand is I2P's \"network "
+"database\" (or \"netDb\") \n"
+"- a pair of algorithms used to share network metadata. The two types of "
+"metadata \n"
+"carried are \"routerInfo\" and \"leaseSets\" - the "
+"routerInfo gives routers the \n"
+"data necessary for contacting a particular router (their public keys, "
+"transport \n"
+"addresses, etc), while the leaseSet gives routers the information "
+"necessary \n"
+"for contacting a particular destination. A leaseSet contains a number of "
+"\"leases\".\n"
+"Each of this leases specifies a tunnel gateway, which allows reaching a "
+"specific destination.\n"
+"The full information contained in a lease:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:155
+msgid "Inbound gateway for a tunnel that allows reaching a specific destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:156
+msgid "Time when a tunnel expires."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:157
+msgid ""
+"Pair of public keys to be able to encrypt messages (to send through the "
+"tunnel and reach the destination)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:159
+msgid ""
+"Routers themselves send their routerInfo to the netDb directly, while "
+"leaseSets are sent through outbound tunnels\n"
+"(leaseSets need to be sent anonymously, to avoid correlating a router "
+"with his leaseSets)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:164
+msgid ""
+"We can combine the above concepts to build successful connections in the "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:168
+msgid ""
+"To build up her own inbound and outbound tunnels, Alice does a lookup in "
+"the netDb to collect routerInfo.\n"
+"This way, she gathers lists of peers she can use as hops in her tunnels.\n"
+"She can then send a build message to the first hop, requesting the "
+"construction of a tunnel and asking\n"
+"that router to send the construction message onward, until the tunnel has"
+" been constructed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:175
+msgid "Request information on other routers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:177
+msgid "Build tunnel using router information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:179
+msgid "Figure 2: Router information is used to build tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:182
+msgid ""
+"When Alice wants to send a message to Bob, she first does a lookup in the"
+" \n"
+"netDb to find Bob's leaseSet, giving her his current inbound tunnel "
+"gateways. \n"
+"She then picks one of her outbound tunnels and sends the message down it "
+"with \n"
+"instructions for the outbound tunnel's endpoint to forward the message on"
+" \n"
+"to one of Bob's inbound tunnel gateways. When the outbound tunnel "
+"endpoint \n"
+"receives those instructions, it forwards the message as requested, and "
+"when \n"
+"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel"
+" \n"
+"to Bob's router. If Alice wants Bob to be able to reply to the message, "
+"she \n"
+"needs to transmit her own destination explicitly as part of the message "
+"itself.\n"
+"This can be done by introducing a higher-level layer, which is done in "
+"the\n"
+"streaming library.\n"
+"Alice may also cut down on the response time by bundling her most \n"
+"recent LeaseSet with the message so that Bob doesn't need to do a netDb "
+"lookup \n"
+"for it when he wants to reply, but this is optional."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:199
+msgid "Connect tunnels using LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:199
+msgid "Connect tunnels using leaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:201
+msgid "Figure 3: LeaseSets are used to connect outbound and inbound tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:204
+msgid ""
+"While the tunnels themselves have layered encryption to prevent "
+"unauthorized \n"
+"disclosure to peers inside the network (as the transport layer itself "
+"does \n"
+"to prevent unauthorized disclosure to peers outside the network), it is "
+"necessary \n"
+"to add an additional end to end layer of encryption to hide the message "
+"from \n"
+"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n"
+"encryption\" lets Alice's router wrap up multiple messages into a "
+"single \n"
+"\"garlic message\", encrypted to a particular public key so that "
+"intermediary \n"
+"peers cannot determine either how many messages are within the garlic, "
+"what \n"
+"those messages say, or where those individual cloves are destined. For "
+"typical \n"
+"end to end communication between Alice and Bob, the garlic will be "
+"encrypted \n"
+"to the public key published in Bob's leaseSet, allowing the message to be"
+" \n"
+"encrypted without giving out the public key to Bob's own router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:219
+msgid ""
+"Another important fact to keep in mind is that I2P is entirely message "
+"based \n"
+"and that some messages may be lost along the way. Applications using I2P "
+"can \n"
+"use the message oriented interfaces and take care of their own congestion"
+" \n"
+"control and reliability needs, but most would be best served by reusing "
+"the \n"
+"provided streaming library to view I2P as "
+"a streams \n"
+"based network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:229
+msgid ""
+"Both inbound and outbound tunnels work along similar principles.\n"
+"The tunnel gateway accumulates a number of tunnel messages, eventually "
+"preprocessing \n"
+"them into something for tunnel delivery. Next, the gateway encrypts that "
+"preprocessed \n"
+"data and forwards it to the first hop. That peer and subsequent tunnel "
+"participants \n"
+"add on a layer of encryption after verifying that it isn't a duplicate "
+"before \n"
+"forward it on to the next peer. Eventually, the message arrives at the "
+"endpoint \n"
+"where the messages are split out again and forwarded on as requested. The"
+" \n"
+"difference arises in what the tunnel's creator does - for inbound "
+"tunnels, \n"
+"the creator is the endpoint and they simply decrypt all of the layers "
+"added, \n"
+"while for outbound tunnels, the creator is the gateway and they pre-"
+"decrypt \n"
+"all of the layers so that after all of the layers of per-hop encryption "
+"are \n"
+"added, the message arrives in the clear at the tunnel endpoint."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:244
+msgid ""
+"The choice of specific peers to pass on messages as well as their "
+"particular \n"
+"ordering is important to understanding both I2P's anonymity and "
+"performance \n"
+"characteristics. While the network database (below) has its own criteria "
+"for \n"
+"picking what peers to query and store entries on, tunnel creators may use"
+" any peers \n"
+"in the network in any order (and even any number of times) in a single "
+"tunnel. \n"
+"If perfect latency and capacity data were globally known, selection and "
+"ordering \n"
+"would be driven by the particular needs of the client in tandem with "
+"their \n"
+"threat model. Unfortunately, latency and capacity data is not trivial to "
+"gather \n"
+"anonymously, and depending upon untrusted peers to provide this "
+"information \n"
+"has its own serious anonymity implications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:257
+msgid ""
+"From an anonymity perspective, the simplest technique would be to pick "
+"peers \n"
+"randomly from the entire network, order them randomly and use those peers"
+" \n"
+"in that order for all eternity. From a performance perspective, the "
+"simplest \n"
+"technique would be to pick the fastest peers with the necessary spare "
+"capacity, \n"
+"spreading the load across different peers to handle transparent failover,"
+" \n"
+"and to rebuild the tunnel whenever capacity information changes. While "
+"the \n"
+"former is both brittle and inefficient, the later requires inaccessible "
+"information \n"
+"and offers insufficient anonymity. I2P is instead working on offering a "
+"range \n"
+"of peer selection strategies, coupled with anonymity aware measurement "
+"code \n"
+"to organize the peers by their profiles."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:270
+msgid ""
+"As a base, I2P is constantly profiling the peers with which it interacts"
+" \n"
+"with by measuring their indirect behavior - for instance, when a peer "
+"responds \n"
+"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in "
+"the \n"
+"profiles for all of the routers involved in the two tunnels (inbound and "
+"outbound) \n"
+"through which the request and response passed, as well as the queried "
+"peer's \n"
+"profile. Direct measurement, such as transport layer latency or "
+"congestion, \n"
+"is not used as part of the profile, as it can be manipulated and "
+"associated \n"
+"with the measuring router, exposing them to trivial attacks. While "
+"gathering \n"
+"these profiles, a series of calculations are run on each to summarize its"
+" \n"
+"performance - its latency, capacity to handle lots of activity, whether "
+"they \n"
+"are currently overloaded, and how well integrated into the network they "
+"seem \n"
+"to be. These calculations are then compared for active peers to organize "
+"the \n"
+"routers into four tiers - fast and high capacity, high capacity, not "
+"failing, \n"
+"and failing. The thresholds for those tiers are determined dynamically, "
+"and \n"
+"while they currently use fairly simple algorithms, alternatives exist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:288
+msgid ""
+"Using this profile data, the simplest reasonable peer selection strategy"
+" \n"
+"is to pick peers randomly from the top tier (fast and high capacity), and"
+" \n"
+"this is currently deployed for client tunnels. Exploratory tunnels (used "
+"for \n"
+"netDb and tunnel management) pick peers randomly from the \"not failing\""
+" tier \n"
+"(which includes routers in 'better' tiers as well), allowing the peer to "
+"sample \n"
+"routers more widely, in effect optimizing the peer selection through "
+"randomized \n"
+"hill climbing. These strategies alone do however leak information "
+"regarding \n"
+"the peers in the router's top tier through predecessor and netDb "
+"harvesting \n"
+"attacks. In turn, several alternatives exist which, while not balancing "
+"the \n"
+"load as evenly, will address the attacks mounted by particular classes of"
+" \n"
+"adversaries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:302
+msgid ""
+"By picking a random key and ordering the peers according to their XOR "
+"distance \n"
+"from it, the information leaked is reduced in predecessor and harvesting "
+"attacks \n"
+"according to the peers' failure rate and the tier's churn. Another simple"
+" \n"
+"strategy for dealing with netDb harvesting attacks is to simply fix the "
+"inbound \n"
+"tunnel gateway(s) yet randomize the peers further on in the tunnels. To "
+"deal \n"
+"with predecessor attacks for adversaries which the client contacts, the "
+"outbound \n"
+"tunnel endpoints would also remain fixed. The selection of which peer to "
+"fix \n"
+"on the most exposed point would of course need to have a limit to the "
+"duration, \n"
+"as all peers fail eventually, so it could either be reactively adjusted "
+"or \n"
+"proactively avoided to mimic a measured mean time between failures of "
+"other \n"
+"routers. These two strategies can in turn be combined, using a fixed "
+"exposed \n"
+"peer and an XOR based ordering within the tunnels themselves. A more "
+"rigid \n"
+"strategy would fix the exact peers and ordering of a potential tunnel, "
+"only \n"
+"using individual peers if all of them agree to participate in the same "
+"way \n"
+"each time. This varies from the XOR based ordering in that the "
+"predecessor \n"
+"and successor of each peer is always the same, while the XOR only makes "
+"sure \n"
+"their order doesn't change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:322
+#, python-format
+msgid ""
+"As mentioned before, I2P currently (release 0.8) includes the tiered \n"
+"random strategy above, with XOR-based ordering. A \n"
+"more detailed discussion of the mechanics involved in tunnel operation, "
+"management, \n"
+"and peer selection can be found in the tunnel "
+"spec."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:330
+#, python-format
+msgid ""
+"As mentioned earlier, I2P's netDb works to share the network's metadata.\n"
+"This is detailed in the network database page,\n"
+"but a basic explanation is available below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:336
+msgid ""
+"A percentage of I2P users are appointed as 'floodfill peers'.\n"
+"Currently, I2P installations that have a lot of bandwidth and are fast "
+"enough,\n"
+"will appoint themselves as floodfill as soon as the number of existing "
+"floodfill routers\n"
+"drops too low."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:343
+#, python-format
+msgid ""
+"Other I2P routers will store their data and lookup data by sending simple"
+" 'store' and 'lookup' queries to the floodfills.\n"
+"If a floodfill router receives a 'store' query, it will spread the "
+"information to other floodfill routers\n"
+"using the Kademlia "
+"algorithm.\n"
+"The 'lookup' queries currently function differently, to avoid an "
+"important\n"
+"security issue.\n"
+"When a lookup is done, the floodfill router will not forward the lookup "
+"to other peers,\n"
+"but will always answer by itself (if it has the requested data)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:353
+msgid "Two types of information are stored in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:357
+msgid ""
+"A RouterInfo stores information on a specific I2P router and how "
+"to contact it"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:358
+msgid ""
+"A LeaseSet stores information on a specific destination (e.g. I2P "
+"website, e-mail server...)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:360
+msgid ""
+"All of this information is signed by the publishing party and verified by"
+" any I2P router using or storing the information.\n"
+"In addition, the data contains timing information, to avoid storage of "
+"old entries and possible attacks.\n"
+"This is also why I2P bundles the necessary code for maintaining the "
+"correct time, occasionally querying some SNTP servers \n"
+"(the pool.ntp.org round robin by"
+" default)\n"
+"and detecting skew between routers at the transport layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:368
+msgid "Some additional remarks are also important."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:373
+msgid "Unpublished and encrypted leasesets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:374
+msgid ""
+"One could only want specific people to be able to reach a destination.\n"
+"This is possible by not publishing the destination in the netDb. You will"
+" however have to transmit the destination by other means.\n"
+"An alternative are the 'encrypted leaseSets'. These leaseSets can only be"
+" decoded by people with access to the decryption key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:381
+msgid "Bootstrapping:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:382
+msgid ""
+"Bootstrapping the netDb is quite simple. Once a router manages to receive"
+" a single routerInfo of a reachable peer,\n"
+"it can query that router for references to other routers in the network.\n"
+"Currently, a number of users post their routerInfo files to a website to "
+"make this information available.\n"
+"I2P automatically connects to one of these websites to gather routerInfo "
+"files and bootstrap."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:390
+msgid "Lookup scalability:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:391
+msgid ""
+"Lookups in the I2P network are not forwarded to other netDb routers.\n"
+"Currently, this is not a major problem, since the network is not very "
+"large.\n"
+"However, as the network grows, not all routerInfo and leaseSet files will"
+" be present\n"
+"on each netDb router. This will cause a deterioration of the percentage "
+"of successful lookups.\n"
+"Because of this, refinements to the netDb will be done in the next "
+"releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:402
+msgid ""
+"Communication between routers needs to provide confidentiality and "
+"integrity \n"
+"against external adversaries while authenticating that the router "
+"contacted \n"
+"is the one who should receive a given message. The particulars of how "
+"routers \n"
+"communicate with other routers aren't critical - three separate protocols"
+" \n"
+"have been used at different points to provide those bare necessities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:410
+#, python-format
+msgid ""
+"I2P started with a TCP-based protocol which \n"
+"has since been disabled. Then, to accommodate the need for high degree "
+"communication \n"
+"(as a number of routers will end up speaking with many others), I2P moved"
+" \n"
+"from a TCP based transport to a UDP-based one - "
+"\"Secure \n"
+"Semireliable UDP\", or \"SSU\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:418
+#, python-format
+msgid "As described in the SSU spec:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:422
+msgid ""
+"The goal of this protocol is to provide secure, authenticated, \n"
+"semireliable and unordered message delivery, exposing only a minimal "
+"amount \n"
+"of data easily discernible to third parties. It should support high "
+"degree \n"
+"communication as well as TCP-friendly congestion control and may include"
+" \n"
+"PMTU detection. It should be capable of efficiently moving bulk data at "
+"rates \n"
+"sufficient for home users. In addition, it should support techniques for "
+"addressing \n"
+"network obstacles, like most NATs or firewalls."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:432
+#, python-format
+msgid ""
+"Following the introduction of SSU, after issues with congestion collapse"
+" \n"
+"appeared, a new NIO-based TCP transport called NTCP \n"
+"was implemented. It is enabled by default for outbound connections only. "
+"Those \n"
+"who configure their NAT/firewall to allow inbound connections and specify"
+" \n"
+"the external host and port (dyndns/etc is ok) on /config.jsp can receive "
+"inbound \n"
+"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread"
+" \n"
+"per connection issues of the old TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:442
+msgid ""
+"I2P supports multiple transports simultaneously. A particular transport \n"
+"for an outbound connection is selected with \"bids\". Each transport bids"
+" for \n"
+"the connection and the relative value of these bids assigns the priority."
+" \n"
+"Transports may reply with different bids, depending on whether there is "
+"already \n"
+"an established connection to the peer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:450
+#, python-format
+msgid ""
+"The current implementation ranks NTCP as the highest-priority transport \n"
+"for outbound connections in most situations. SSU is enabled for both "
+"outbound \n"
+"and inbound connections. Your firewall and your I2P router must be "
+"configured \n"
+"to allow inbound NTCP connections. For further information see the NTCP \n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:459
+msgid ""
+"A bare minimum set of cryptographic primitives are combined together to \n"
+"provide I2P's layered defenses against a variety of adversaries. At the "
+"lowest \n"
+"level, inter router communication is protected by the transport layer "
+"security \n"
+"- SSU encrypts each packet with AES256/CBC with both an explicit IV and "
+"MAC \n"
+"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a "
+"2048bit \n"
+"Diffie-Hellman exchange, station-to-station authentication with the other"
+" \n"
+"router's DSA key, plus each network message has their own hash for local "
+"integrity \n"
+"checking. Tunnel messages passed over the "
+"transports \n"
+"have their own layered AES256/CBC encryption with an explicit IV and "
+"verified \n"
+"at the tunnel endpoint with an additional SHA256 hash. Various other "
+"messages \n"
+"are passed along inside \"garlic messages\", which are encrypted with "
+"ElGamal/AES+SessionTags \n"
+"(explained below)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:474
+msgid "Garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:475
+msgid ""
+"Garlic messages are an extension of \"onion\" layered encryption, "
+"allowing \n"
+"the contents of a single message to contain multiple \"cloves\" - fully "
+"formed \n"
+"messages alongside their own instructions for delivery. Messages are "
+"wrapped \n"
+"into a garlic message whenever the message would otherwise be passing in "
+"cleartext \n"
+"through a peer who should not have access to the information - for "
+"instance, \n"
+"when a router wants to ask another router to participate in a tunnel, "
+"they \n"
+"wrap the request inside a garlic, encrypt that garlic to the receiving "
+"router's \n"
+"2048bit ElGamal public key, and forward it through a tunnel. Another "
+"example \n"
+"is when a client wants to send a message to a destination - the sender's "
+"router \n"
+"will wrap up that data message (alongside some other messages) into a "
+"garlic, \n"
+"encrypt that garlic to the 2048bit ElGamal public key published in the "
+"recipient's \n"
+"leaseSet, and forward it through the appropriate tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:490
+msgid ""
+"The \"instructions\" attached to each clove inside the encryption layer "
+"includes \n"
+"the ability to request that the clove be forwarded locally, to a remote "
+"router, \n"
+"or to a remote tunnel on a remote router. There are fields in those "
+"instructions \n"
+"allowing a peer to request that the delivery be delayed until a certain "
+"time \n"
+"or condition has been met, though they won't be honored until the nontrivial \n"
+"delays are deployed. It is possible to explicitly route garlic "
+"messages \n"
+"any number of hops without building tunnels, or even to reroute tunnel "
+"messages \n"
+"by wrapping them in garlic messages and forwarding them a number of hops "
+"prior \n"
+"to delivering them to the next hop in the tunnel, but those techniques "
+"are \n"
+"not currently used in the existing implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:503
+msgid "Session tags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:504
+msgid ""
+"As an unreliable, unordered, message based system, I2P uses a simple "
+"combination \n"
+"of asymmetric and symmetric encryption algorithms to provide data "
+"confidentiality \n"
+"and integrity to garlic messages. As a whole, the combination is referred"
+" \n"
+"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to "
+"describe \n"
+"the simple use of 2048bit ElGamal, AES256, SHA256 and 32 byte nonces."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:543
+msgid ""
+"Session tags themselves have a very short lifetime, after which they are"
+" \n"
+"discarded if not used. In addition, the quantity stored for each key is "
+"limited, \n"
+"as are the number of keys themselves - if too many arrive, either new or "
+"old \n"
+"messages may be dropped. The sender keeps track whether messages using "
+"session \n"
+"tags are getting through, and if there isn't sufficient communication it "
+"may \n"
+"drop the ones previously assumed to be properly delivered, reverting back"
+" \n"
+"to the full expensive ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:553
+msgid ""
+"One alternative is to transmit only a single session tag, and from that,"
+" \n"
+"seed a deterministic PRNG for determining what tags to use or expect. By "
+"keeping \n"
+"this PRNG roughly synchronized between the sender and recipient (the "
+"recipient \n"
+"precomputes a window of the next e.g. 50 tags), the overhead of "
+"periodically \n"
+"bundling a large number of tags is removed, allowing more options in the "
+"space/time \n"
+"tradeoff, and perhaps reducing the number of ElGamal encryptions "
+"necessary. \n"
+"However, it would depend upon the strength of the PRNG to provide the "
+"necessary \n"
+"cover against internal adversaries, though perhaps by limiting the amount"
+" \n"
+"of times each PRNG is used, any weaknesses can be minimized. At the "
+"moment, \n"
+"there are no immediate plans to move towards these synchronized PRNGs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:566
+msgid "Future"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:567
+msgid ""
+"While I2P is currently functional and sufficient for many scenarios, "
+"there \n"
+"are several areas which require further improvement to meet the needs of "
+"those \n"
+"facing more powerful adversaries as well as substantial user experience "
+"optimization."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:573
+msgid "Restricted route operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:574
+msgid ""
+"I2P is an overlay network designed to be run on top of a functional "
+"packet \n"
+"switched network, exploiting the end to end principle to offer anonymity "
+"and \n"
+"security. While the Internet no longer fully embraces the end to end "
+"principle\n"
+"(due to the usage of NAT), \n"
+"I2P does require a substantial portion of the network to be reachable - "
+"there \n"
+"may be a number of peers along the edges running using restricted routes,"
+" \n"
+"but I2P does not include an appropriate routing algorithm for the "
+"degenerate \n"
+"case where most peers are unreachable. It would, however work on top of a"
+" \n"
+"network employing such an algorithm."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:586
+msgid ""
+"Restricted route operation, where there are limits to what peers are "
+"reachable \n"
+"directly, has several different functional and anonymity implications, "
+"dependent \n"
+"upon how the restricted routes are handled. At the most basic level, "
+"restricted \n"
+"routes exist when a peer is behind a NAT or firewall which does not allow"
+" \n"
+"inbound connections. This was largely addressed in I2P 0.6.0.6 by "
+"integrating \n"
+"distributed hole punching into the transport layer, allowing people "
+"behind \n"
+"most NATs and firewalls to receive unsolicited connections without any "
+"configuration. \n"
+"However, this does not limit the exposure of the peer's IP address to "
+"routers \n"
+"inside the network, as they can simply get introduced to the peer through"
+" \n"
+"the published introducer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:599
+msgid ""
+"Beyond the functional handling of restricted routes, there are two levels"
+" \n"
+"of restricted operation that can be used to limit the exposure of one's "
+"IP \n"
+"address - using router-specific tunnels for communication, and offering "
+"'client \n"
+"routers'. For the former, routers can either build a new pool of tunnels "
+"or \n"
+"reuse their exploratory pool, publishing the inbound gateways to some of "
+"them \n"
+"as part of their routerInfo in place of their transport addresses. When a"
+" \n"
+"peer wants to get in touch with them, they see those tunnel gateways in "
+"the \n"
+"netDb and simply send the relevant message to them through one of the "
+"published \n"
+"tunnels. If the peer behind the restricted route wants to reply, it may "
+"do \n"
+"so either directly (if they are willing to expose their IP to the peer) "
+"or \n"
+"indirectly through their outbound tunnels. When the routers that the peer"
+" \n"
+"has direct connections to want to reach it (to forward tunnel messages, "
+"for \n"
+"instance), they simply prioritize their direct connection over the "
+"published \n"
+"tunnel gateway. The concept of 'client routers' simply extends the "
+"restricted \n"
+"route by not publishing any router addresses. Such a router would not "
+"even \n"
+"need to publish their routerInfo in the netDb, merely providing their "
+"self \n"
+"signed routerInfo to the peers that it contacts (necessary to pass the "
+"router's \n"
+"public keys). Both levels of restricted route operation are planned for "
+"I2P \n"
+"2.0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:621
+msgid ""
+"There are tradeoffs for those behind restricted routes, as they would "
+"likely \n"
+"participate in other people's tunnels less frequently, and the routers "
+"which \n"
+"they are connected to would be able to infer traffic patterns that would "
+"not \n"
+"otherwise be exposed. On the other hand, if the cost of that exposure is "
+"less \n"
+"than the cost of an IP being made available, it may be worthwhile. This, "
+"of \n"
+"course, assumes that the peers that the router behind a restricted route "
+"contacts \n"
+"are not hostile - either the network is large enough that the probability"
+" \n"
+"of using a hostile peer to get connected is small enough, or trusted (and"
+" \n"
+"perhaps temporary) peers are used instead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:633
+msgid "Variable latency"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:634
+msgid ""
+"Even though the bulk of I2P's initial efforts have been on low latency "
+"communication, \n"
+"it was designed with variable latency services in mind from the "
+"beginning. \n"
+"At the most basic level, applications running on top of I2P can offer the"
+" \n"
+"anonymity of medium and high latency communication while still blending "
+"their \n"
+"traffic patterns in with low latency traffic. Internally though, I2P can "
+"offer \n"
+"its own medium and high latency communication through the garlic "
+"encryption \n"
+"- specifying that the message should be sent after a certain delay, at a "
+"certain \n"
+"time, after a certain number of messages have passed, or another mix "
+"strategy. \n"
+"With the layered encryption, only the router that the clove exposed the "
+"delay \n"
+"request would know that the message requires high latency, allowing the "
+"traffic \n"
+"to blend in further with the low latency traffic. Once the transmission "
+"precondition \n"
+"is met, the router holding on to the clove (which itself would likely be "
+"a \n"
+"garlic message) simply forwards it as requested - to a router, to a "
+"tunnel, \n"
+"or, most likely, to a remote client destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:651
+msgid ""
+"There are a substantial number of ways to exploit this capacity for high"
+" \n"
+"latency comm in I2P, but for the moment, doing so has been scheduled for "
+"the \n"
+"I2P 3.0 release. In the meantime, those requiring the anonymity that high"
+" \n"
+"latency comm can offer should look towards the application layer to "
+"provide \n"
+"it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:659
+msgid "Open questions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:661
+msgid "How to get rid of the timing constraint?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:662
+msgid "Can we deal with the sessionTags more efficiently?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:663
+msgid ""
+"What, if any, batching/mixing strategies should be made available on the "
+"tunnels?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:664
+msgid ""
+"What other tunnel peer selection and ordering strategies should be "
+"available?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:667
+msgid "Similar systems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:669
+msgid ""
+"I2P's architecture builds on the concepts of message oriented middleware,"
+" \n"
+"the topology of DHTs, the anonymity and cryptography of free route "
+"mixnets, \n"
+"and the adaptability of packet switched networking. The value comes not "
+"from \n"
+"novel concepts of algorithms though, but from careful engineering "
+"combining \n"
+"the research results of existing systems and papers. While there are a "
+"few \n"
+"similar efforts worth reviewing, both for technical and functional "
+"comparisons, \n"
+"two in particular are pulled out here - Tor and Freenet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:679
+#, python-format
+msgid "See also the Network Comparisons Page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:684
+#: i2p2www/pages/site/docs/how/tech-intro.html:749
+msgid "website"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:686
+msgid ""
+"At first glance, Tor and I2P have many functional and anonymity related \n"
+"similarities. While I2P's development began before we were aware of the "
+"early \n"
+"stage efforts on Tor, many of the lessons of the original onion routing "
+"and \n"
+"ZKS efforts were integrated into I2P's design. Rather than building an "
+"essentially \n"
+"trusted, centralized system with directory servers, I2P has a self "
+"organizing \n"
+"network database with each peer taking on the responsibility of profiling"
+" \n"
+"other routers to determine how best to exploit available resources. "
+"Another \n"
+"key difference is that while both I2P and Tor use layered and ordered "
+"paths \n"
+"(tunnels and circuits/streams), I2P is fundamentally a packet switched "
+"network, \n"
+"while Tor is fundamentally a circuit switched one, allowing I2P to "
+"transparently \n"
+"route around congestion or other network failures, operate redundant "
+"pathways, \n"
+"and load balance the data across available resources. While Tor offers "
+"the \n"
+"useful outproxy functionality by offering integrated outproxy discovery "
+"and \n"
+"selection, I2P leaves such application layer decisions up to applications"
+" \n"
+"running on top of I2P - in fact, I2P has even externalized the TCP-like "
+"streaming \n"
+"library itself to the application layer, allowing developers to "
+"experiment \n"
+"with different strategies, exploiting their domain specific knowledge to "
+"offer \n"
+"better performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:707
+msgid ""
+"From an anonymity perspective, there is much similarity when the core "
+"networks \n"
+"are compared. However, there are a few key differences. When dealing with"
+" \n"
+"an internal adversary or most external adversaries, I2P's simplex tunnels"
+" \n"
+"expose half as much traffic data than would be exposed with Tor's duplex "
+"circuits \n"
+"by simply looking at the flows themselves - an HTTP request and response "
+"would \n"
+"follow the same path in Tor, while in I2P the packets making up the "
+"request \n"
+"would go out through one or more outbound tunnels and the packets making "
+"up \n"
+"the response would come back through one or more different inbound "
+"tunnels. \n"
+"While I2P's peer selection and ordering strategies should sufficiently "
+"address \n"
+"predecessor attacks, should a switch to bidirectional tunnels be "
+"necessary,\n"
+"we could simply build an inbound and outbound tunnel along the same "
+"routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:721
+msgid ""
+"Another anonymity issue comes up in Tor's use of telescopic tunnel "
+"creation, \n"
+"as simple packet counting and timing measurements as the cells in a "
+"circuit \n"
+"pass through an adversary's node exposes statistical information "
+"regarding \n"
+"where the adversary is within the circuit. I2P's unidirectional tunnel "
+"creation \n"
+"with a single message so that this data is not exposed. Protecting the "
+"position \n"
+"in a tunnel is important, as an adversary would otherwise be able to "
+"mount \n"
+"a series of powerful predecessor, intersection, and traffic confirmation "
+"attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:731
+msgid ""
+"Tor's support for a second tier of \"onion proxies\" does offer a non-"
+"trivial \n"
+"degree of anonymity while requiring a low cost of entry, while I2P will "
+"not \n"
+"offer this topology until 2.0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:737
+msgid ""
+"On the whole, Tor and I2P complement each other in their focus - Tor "
+"works \n"
+"towards offering high speed anonymous Internet outproxying, while I2P "
+"works \n"
+"towards offering a decentralized resilient network in itself. In theory, "
+"both \n"
+"can be used to achieve both purposes, but given limited development "
+"resources, \n"
+"they both have their strengths and weaknesses. The I2P developers have "
+"considered \n"
+"the steps necessary to modify Tor to take advantage of I2P's design, but "
+"concerns \n"
+"of Tor's viability under resource scarcity suggest that I2P's packet "
+"switching \n"
+"architecture will be able to exploit scarce resources more effectively."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:751
+msgid ""
+"Freenet played a large part in the initial stages of I2P's design - "
+"giving \n"
+"proof to the viability of a vibrant pseudonymous community completely "
+"contained \n"
+"within the network, demonstrating that the dangers inherent in outproxies"
+" \n"
+"could be avoided. The first seed of I2P began as a replacement "
+"communication \n"
+"layer for Freenet, attempting to factor out the complexities of a "
+"scalable, \n"
+"anonymous and secure point to point communication from the complexities "
+"of \n"
+"a censorship resistant distributed data store. Over time however, some of"
+" \n"
+"the anonymity and scalability issues inherent in Freenet's algorithms "
+"made \n"
+"it clear that I2P's focus should stay strictly on providing a generic "
+"anonymous \n"
+"communication layer, rather than as a component of Freenet. Over the "
+"years, \n"
+"the Freenet developers have come to see the weaknesses in the older "
+"design, \n"
+"prompting them to suggest that they will require a \"premix\" layer to "
+"offer \n"
+"substantial anonymity. In other words, Freenet needs to run on top of a "
+"mixnet \n"
+"such as I2P or Tor, with \"client nodes\" requesting and publishing data "
+"through \n"
+"the mixnet to the \"server nodes\" which then fetch and store the data "
+"according \n"
+"to Freenet's heuristic distributed data storage algorithms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:770
+msgid ""
+"Freenet's functionality is very complementary to I2P's, as Freenet "
+"natively \n"
+"provides many of the tools for operating medium and high latency systems,"
+" \n"
+"while I2P natively provides the low latency mix network suitable for "
+"offering \n"
+"adequate anonymity. The logic of separating the mixnet from the "
+"censorship-\n"
+"resistant distributed data store still seems self-evident from an "
+"engineering, \n"
+"anonymity, security, and resource allocation perspective, so hopefully "
+"the \n"
+"Freenet team will pursue efforts in that direction, if not simply reusing"
+" \n"
+"(or helping to improve, as necessary) existing mixnets like I2P or Tor."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:781
+msgid ""
+"It is worth mentioning that there has recently been discussion and work \n"
+"by the Freenet developers on a \"globally scalable darknet\" using "
+"restricted \n"
+"routes between peers of various trust. While insufficient information has"
+" \n"
+"been made publicly available regarding how such a system would operate "
+"for \n"
+"a full review, from what has been said the anonymity and scalability "
+"claims \n"
+"seem highly dubious. In particular, the appropriateness for use in "
+"hostile \n"
+"regimes against state level adversaries has been tremendously overstated,"
+" \n"
+"and any analysis on the implications of resource scarcity upon the "
+"scalability \n"
+"of the network has seemingly been avoided. Further questions regarding "
+"susceptibility \n"
+"to traffic analysis, trust and other topics do exist, but a more in-depth"
+" \n"
+"review of this \"globally scalable darknet\" will have to wait until the "
+"Freenet \n"
+"team makes more information available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:797
+msgid ""
+"I2P itself doesn't really do much - it simply sends messages to remote "
+"destinations \n"
+"and receives messages targeting local destinations - most of the "
+"interesting \n"
+"work goes on at the layers above it. By itself, I2P could be seen as an "
+"anonymous \n"
+"and secure IP layer, and the bundled streaming"
+" library \n"
+"as an implementation of an anonymous and secure TCP layer on top of it. "
+"Beyond \n"
+"that, I2PTunnel exposes a generic TCP "
+"proxying \n"
+"system for either getting into or out of the I2P network, plus a variety "
+"of \n"
+"network applications provide further functionality for end users."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:808
+msgid "Streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:809
+msgid ""
+"The I2P streaming library can be viewed as a generic streaming interface "
+"(mirroring TCP sockets),\n"
+"and the implementation supports a sliding "
+"window protocol\n"
+"with several optimizations, to take into account the high delay over I2P."
+"\n"
+"Individual streams may adjust the maximum packet size and \n"
+"other options, though the default of 4KB compressed seems a reasonable "
+"tradeoff \n"
+"between the bandwidth costs of retransmitting lost messages and the "
+"latency \n"
+"of multiple messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:819
+msgid ""
+"In addition, in consideration of the relatively high cost of subsequent \n"
+"messages, the streaming library's protocol for scheduling and delivering "
+"messages \n"
+"has been optimized to allow individual messages passed to contain as much"
+" \n"
+"information as is available. For instance, a small HTTP transaction "
+"proxied \n"
+"through the streaming library can be completed in a single round trip - "
+"the \n"
+"first message bundles a SYN, FIN and the small payload (an HTTP request "
+"typically \n"
+"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many"
+" \n"
+"HTTP responses fit). While an additional ACK must be transmitted to tell "
+"the \n"
+"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy "
+"can \n"
+"deliver the full response to the browser immediately."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:832
+msgid ""
+"On the whole, however, the streaming library bears much resemblance to an"
+" \n"
+"abstraction of TCP, with its sliding windows, congestion control "
+"algorithms \n"
+"(both slow start and congestion avoidance), and general packet behavior "
+"(ACK, \n"
+"SYN, FIN, RST, etc)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:839
+msgid "Naming library and addressbook"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:840
+#, python-format
+msgid ""
+"For more information see the Naming and "
+"Addressbook page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:844
+#: i2p2www/pages/site/docs/how/tech-intro.html:918
+#: i2p2www/pages/site/docs/how/tech-intro.html:965
+#: i2p2www/pages/site/docs/how/tech-intro.html:997
+#: i2p2www/pages/site/docs/how/tech-intro.html:1005
+#: i2p2www/pages/site/docs/how/tech-intro.html:1013
+#: i2p2www/pages/site/docs/how/tech-intro.html:1023
+#: i2p2www/pages/site/docs/how/tech-intro.html:1031
+#: i2p2www/pages/site/docs/how/tech-intro.html:1053
+#, python-format
+msgid "Developed by: %(dev)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:846
+msgid ""
+"Naming within I2P has been an oft-debated topic since the very beginning"
+" \n"
+"with advocates across the spectrum of possibilities. However, given I2P's"
+" \n"
+"inherent demand for secure communication and decentralized operation, the"
+" \n"
+"traditional DNS-style naming system is clearly out, as are \"majority "
+"rules\" \n"
+"voting systems. Instead, I2P ships with a generic naming library and a "
+"base \n"
+"implementation designed to work off a local name to destination mapping, "
+"as \n"
+"well as an optional add-on application called the \"addressbook\". The "
+"addressbook \n"
+"is a web-of-trust-driven secure, distributed, and human readable naming "
+"system, \n"
+"sacrificing only the call for all human readable names to be globally "
+"unique \n"
+"by mandating only local uniqueness. While all messages in I2P are "
+"cryptographically \n"
+"addressed by their destination, different people can have local "
+"addressbook \n"
+"entries for \"Alice\" which refer to different destinations. People can "
+"still \n"
+"discover new names by importing published addressbooks of peers specified"
+" \n"
+"in their web of trust, by adding in the entries provided through a third "
+"party, \n"
+"or (if some people organize a series of published addressbooks using a "
+"first \n"
+"come first serve registration system) people can choose to treat these "
+"addressbooks \n"
+"as name servers, emulating traditional DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:866
+msgid ""
+"I2P does not promote the use of DNS-like services though, as the damage \n"
+"done by hijacking a site can be tremendous - and insecure destinations "
+"have \n"
+"no value. DNSsec itself still falls back on registrars and certificate "
+"authorities, \n"
+"while with I2P, requests sent to a destination cannot be intercepted or "
+"the \n"
+"reply spoofed, as they are encrypted to the destination's public keys, "
+"and \n"
+"a destination itself is just a pair of public keys and a certificate. "
+"DNS-style \n"
+"systems on the other hand allow any of the name servers on the lookup "
+"path \n"
+"to mount simple denial of service and spoofing attacks. Adding on a "
+"certificate \n"
+"authenticating the responses as signed by some centralized certificate "
+"authority \n"
+"would address many of the hostile nameserver issues but would leave open "
+"replay \n"
+"attacks as well as hostile certificate authority attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:880
+msgid ""
+"Voting style naming is dangerous as well, especially given the "
+"effectiveness \n"
+"of Sybil attacks in anonymous systems - the attacker can simply create an"
+" \n"
+"arbitrarily high number of peers and \"vote\" with each to take over a "
+"given \n"
+"name. Proof-of-work methods can be used to make identity non-free, but as"
+" \n"
+"the network grows the load required to contact everyone to conduct online"
+" \n"
+"voting is implausible, or if the full network is not queried, different "
+"sets \n"
+"of answers may be reachable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:890
+msgid ""
+"As with the Internet however, I2P is keeping the design and operation of"
+" \n"
+"a naming system out of the (IP-like) communication layer. The bundled "
+"naming \n"
+"library includes a simple service provider interface which alternate "
+"naming \n"
+"systems can plug into, allowing end users to drive what sort of naming "
+"tradeoffs \n"
+"they prefer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:899
+msgid ""
+"The old Syndie bundled with I2P has been replaced by the new Syndie which"
+"\n"
+"is distributed separately. For more information see the Syndie\n"
+"pages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:905
+msgid ""
+"Syndie is a safe, anonymous blogging / content publication / content "
+"aggregation \n"
+"system. It lets you create information, share it with others, and read "
+"posts \n"
+"from those you're interested in, all while taking into consideration your"
+" \n"
+"needs for security and anonymity. Rather than building its own content "
+"distribution \n"
+"network, Syndie is designed to run on top of existing networks, "
+"syndicating \n"
+"content through eepsites, Tor hidden services, Freenet freesites, normal "
+"websites, \n"
+"usenet newsgroups, email lists, RSS feeds, etc. Data published with "
+"Syndie \n"
+"is done so as to offer pseudonymous authentication to anyone reading or "
+"archiving \n"
+"it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:920
+msgid ""
+"I2PTunnel is probably I2P's most popular and versatile client "
+"application, \n"
+"allowing generic proxying both into and out of the I2P network. I2PTunnel"
+" \n"
+"can be viewed as four separate proxying applications - a \"client\" which"
+" receives \n"
+"inbound TCP connections and forwards them to a given I2P destination, an "
+"\"httpclient\" \n"
+"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the "
+"requests to \n"
+"the appropriate I2P destination (after querying the naming service if "
+"necessary), \n"
+"a \"server\" which receives inbound I2P streaming connections on a "
+"destination \n"
+"and forwards them to a given TCP host+port, and an \"httpserver\" which "
+"extends \n"
+"the \"server\" by parsing the HTTP request and responses to allow safer "
+"operation. \n"
+"There is an additional \"socksclient\" application, but its use is not "
+"encouraged \n"
+"for reasons previously mentioned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:934
+msgid ""
+"I2P itself is not an outproxy network - the anonymity and security "
+"concerns \n"
+"inherent in a mix net which forwards data into and out of the mix have "
+"kept \n"
+"I2P's design focused on providing an anonymous network which capable of "
+"meeting \n"
+"the user's needs without requiring external resources. However, the "
+"I2PTunnel \n"
+"\"httpclient\" application offers a hook for outproxying - if the "
+"hostname requested \n"
+"doesn't end in \".i2p\", it picks a random destination from a user-"
+"provided \n"
+"set of outproxies and forwards the request to them. These destinations "
+"are \n"
+"simply I2PTunnel \"server\" instances run by volunteers who have "
+"explicitly \n"
+"chosen to run outproxies - no one is an outproxy by default, and running "
+"an \n"
+"outproxy doesn't automatically tell other people to proxy through you. "
+"While \n"
+"outproxies do have inherent weaknesses, they offer a simple proof of "
+"concept \n"
+"for using I2P and provide some functionality under a threat model which "
+"may \n"
+"be sufficient for some users."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:950
+msgid ""
+"I2PTunnel enables most of the applications in use. An \"httpserver\" "
+"pointing \n"
+"at a webserver lets anyone run their own anonymous website (or "
+"\"eepsite\") \n"
+"- a webserver is bundled with I2P for this purpose, but any webserver can"
+" \n"
+"be used. Anyone may run a \"client\" pointing at one of the anonymously "
+"hosted \n"
+"IRC servers, each of which are running a \"server\" pointing at their "
+"local \n"
+"IRCd and communicating between IRCds over their own \"client\" tunnels. "
+"End \n"
+"users also have \"client\" tunnels pointing at I2Pmail's \n"
+"POP3 and SMTP destinations (which in turn are simply \"server\" instances"
+" pointing \n"
+"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at "
+"I2P's CVS \n"
+"server, allowing anonymous development. At times people have even run "
+"\"client\" \n"
+"proxies to access the \"server\" instances pointing at an NNTP server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:967
+msgid ""
+"i2p-bt is a port of the mainline python BitTorrent client to run both the"
+" \n"
+"tracker and peer communication over I2P. Tracker requests are forwarded "
+"through \n"
+"the eepproxy to eepsites specified in the torrent file while tracker "
+"responses \n"
+"refer to peers by their destination explicitly, allowing i2p-bt to open "
+"up \n"
+"a streaming lib connection to query them "
+"for \n"
+"blocks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:976
+msgid ""
+"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making"
+" \n"
+"a few modifications as necessary to strip any anonymity-compromising "
+"information \n"
+"from the application and to take into consideration the fact that IPs "
+"cannot \n"
+"be used for identifying peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:984
+msgid ""
+"I2PSnark developed: jrandom, et al, ported from mjw's Snark client"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:990
+msgid ""
+"Bundled with the I2P install, I2PSnark offers a simple anonymous "
+"BitTorrent \n"
+"client with multitorrent capabilities, exposing all of the functionality "
+"through \n"
+"a plain HTML web interface."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:999
+#, python-format
+msgid ""
+"Robert is a Bittorrent client written in Python.\n"
+"It is hosted on http://%(bob)s/Robert.html "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1007
+#, python-format
+msgid ""
+"PyBit is a Bittorrent client written in Python.\n"
+"It is hosted on %(pybit)s "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1015
+msgid ""
+"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to"
+" \n"
+"run entirely on top of I2P. While it has disabled some of Phex's "
+"functionality, \n"
+"such as integration with Gnutella webcaches, the basic file sharing and "
+"chatting \n"
+"system is fully functional."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1025
+msgid ""
+"iMule is a fairly direct port of the aMule filesharing client \n"
+"running entirely inside I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1033
+#, python-format
+msgid ""
+"I2Pmail is more a service than an application - postman offers both "
+"internal \n"
+"and external email with POP3 and SMTP service through I2PTunnel instances"
+" \n"
+"accessing a series of components developed with mastiejaner, allowing "
+"people \n"
+"to use their preferred mail clients to send and receive mail "
+"pseudonymously. \n"
+"However, as most mail clients expose substantial identifying information,"
+" \n"
+"I2P bundles susi23's web based susimail client which has been built "
+"specifically \n"
+"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers "
+"transparent \n"
+"virus filtering as well as denial of service prevention with hashcash "
+"augmented \n"
+"quotas. In addition, each user has control of their batching strategy "
+"prior \n"
+"to delivery through the mail.i2p outproxies, which are separate from the "
+"mail.i2p \n"
+"SMTP and POP3 servers - both the outproxies and inproxies communicate "
+"with \n"
+"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising "
+"those \n"
+"non-anonymous locations does not give access to the mail accounts or "
+"activity \n"
+"patterns of the user. At the moment the developers work on a "
+"decentralized \n"
+"mailsystem, called \"v2mail\". More information can be found on the "
+"eepsite \n"
+"%(postman)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1055
+msgid ""
+"I2P-Bote is a distributed e-mail application. It does not use the "
+"traditional\n"
+"e-mail concept of sending an e-mail to a server and retrieving it from a "
+"server.\n"
+"Instead, it uses a Kademlia Distributed Hash Table to store mails.\n"
+"One user can push a mail into the DHT, while another can request the "
+"e-mail from the DHT.\n"
+"And all the mails sent within the I2P-Bote network are automatically "
+"encrypted end-to-end. 
            \n"
+"Furthermore, I2P-Bote offers a remailer function on top of I2P, for "
+"increased high-latency anonymity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1065
+msgid ""
+"I2P-Messenger is an end-to-end encrypted serverless communication "
+"application.\n"
+"For communication between two users, they need to give each other their "
+"destination keys, to allow the other to connect.\n"
+"It supports file transfer and has a search for other users, based on "
+"Seedless."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:2
+msgid "I2P's Threat Model"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:3
+msgid "November 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:7
+msgid "low"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:8
+msgid "medium"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:9
+msgid "high"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:34
+msgid "Damage Potential"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:35
+msgid "Reliability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:36
+msgid "Exploitability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:37
+msgid "Affected Users"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:38
+msgid "Discoverability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:39
+msgid "Severity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:40
+#: i2p2www/pages/site/docs/protocol/i2np.html:94
+msgid "Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:45
+msgid "What do we mean by \"anonymous\"?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:47
+msgid ""
+"Your level of anonymity can be described as \"how hard it is for someone\n"
+"to find out information you don't want them to know?\" - who you are, "
+"where\n"
+"you are located, who you communicate with, or even when you communicate."
+"  \n"
+"\"Perfect\" anonymity is not a useful concept here - software will not "
+"make \n"
+"you indistinguishable from people that don't use computers or who are not"
+" on\n"
+"the Internet.  Instead, we are working to provide sufficient anonymity to"
+" meet the\n"
+"real needs of whomever we can - from those simply browsing websites, to "
+"those exchanging\n"
+"data, to those fearful of discovery by powerful organizations or states."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:58
+msgid ""
+"The question of whether I2P provides sufficient anonymity for your \n"
+"particular needs is a hard one, but this page will hopefully assist in \n"
+"answering that question by exploring how I2P operates under various "
+"attacks\n"
+"so that you may decide whether it meets your needs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:65
+msgid ""
+"We welcome further research and analysis on I2P's resistance to the "
+"threats described below.\n"
+"More review of existing literature (much of it focused on Tor) and "
+"original\n"
+"work focused on I2P is needed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:71
+msgid "Network Topology Summary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:72
+#, python-format
+msgid ""
+"I2P builds off the ideas of many other \n"
+"systems, but a few key points should be kept in"
+" mind when \n"
+"reviewing related literature:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:78
+msgid ""
+"I2P is a free route mixnet - the message creator explicitly "
+"defines the\n"
+"path that messages will be sent out (the outbound tunnel), and the "
+"message \n"
+"recipient explicitly defines the path that messages will be received on "
+"(the\n"
+"inbound tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:84
+msgid ""
+"I2P has no official entry and exit points - all peers fully "
+"participate in the \n"
+"mix, and there are no network layer in- or out-proxies (however, at the \n"
+"application layer, a few proxies do exist)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:89
+msgid ""
+"I2P is fully distributed - there are no central controls or "
+"authorities.\n"
+"One could modify some routers to operate mix cascades (building tunnels "
+"and giving\n"
+"out the keys necessary to control the forwarding at the tunnel endpoint) "
+"or directory \n"
+"based profiling and selection, all without breaking compatibility with "
+"the rest of \n"
+"the network, but doing so is of course not necessary (and may even harm "
+"one's\n"
+"anonymity)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:99
+#, python-format
+msgid ""
+"We have documented plans to implement nontrivial delays\n"
+"and batching strategies \n"
+"whose existence is only known to the particular hop or tunnel gateway "
+"that \n"
+"receives the message, allowing a mostly low latency mixnet to provide "
+"cover \n"
+"traffic for higher latency communication (e.g. email).\n"
+"However we are aware that significant delays are required to provide "
+"meaningful\n"
+"protection, and that implementation of such delays will be a significant "
+"challenge.\n"
+"It is not clear at this time whether we will actually implement these "
+"delay features."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:110
+msgid ""
+"In theory, routers along the message path may inject an \n"
+"arbitrary number of hops before forwarding the message to the next peer, "
+"though\n"
+"the current implementation does not."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:117
+msgid "The Threat Model"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:118
+msgid ""
+"I2P design started in 2003, not long after the advent of\n"
+"[Onion Routing],\n"
+"[Freenet], and\n"
+"[Tor].\n"
+"Our design benefits substantially from the research published around that"
+" time.\n"
+"I2P uses several onion routing techniques, so we continue to benefit\n"
+"from the significant academic interest in Tor."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:128
+msgid ""
+"Taking from the attacks and analysis put forth in the \n"
+"anonymity "
+"literature (largely \n"
+"Traffic Analysis: "
+"Protocols, Attacks, Design \n"
+"Issues and Open Problems), the following briefly describes a wide "
+"variety \n"
+"of attacks as well as many of I2Ps defenses.  We update\n"
+"this list to include new attacks as they are identified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:137
+msgid ""
+"Included are some attacks that may be unique to I2P.\n"
+"We do not have good answers for all these attacks, however\n"
+"we continue to do research and improve our defenses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:143
+msgid ""
+"In addition, many of these attacks are significantly easier than\n"
+"they should be, due to the modest size of the current network.\n"
+"While we are aware of some limitations that need to be addressed,\n"
+"I2P is designed to support hundreds of thousands, or millions, of\n"
+"participants.\n"
+"As we continue to spread the word and grow the network,\n"
+"these attacks will become much harder."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:153
+#, python-format
+msgid ""
+"The\n"
+"network comparisons and\n"
+"\"garlic\" terminology pages may also "
+"be helpful\n"
+"to review."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:182
+msgid "Index of Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:184
+#: i2p2www/pages/site/docs/how/threat-model.html:204
+msgid "Brute force attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:185
+#: i2p2www/pages/site/docs/how/threat-model.html:248
+msgid "Timing attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:186
+#: i2p2www/pages/site/docs/how/threat-model.html:285
+msgid "Intersection attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:187
+#: i2p2www/pages/site/docs/how/threat-model.html:365
+msgid "Denial of service attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:188
+#: i2p2www/pages/site/docs/how/threat-model.html:464
+msgid "Tagging attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:189
+#: i2p2www/pages/site/docs/how/threat-model.html:482
+msgid "Partitioning attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:190
+#: i2p2www/pages/site/docs/how/threat-model.html:522
+msgid "Predecessor attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:191
+#: i2p2www/pages/site/docs/how/threat-model.html:567
+msgid "Harvesting attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:192
+#: i2p2www/pages/site/docs/how/threat-model.html:614
+msgid "Identification Through Traffic Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:193
+#: i2p2www/pages/site/docs/how/threat-model.html:674
+msgid "Sybil attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:194
+#: i2p2www/pages/site/docs/how/threat-model.html:723
+msgid "Buddy Exhaustion attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:195
+#: i2p2www/pages/site/docs/how/threat-model.html:748
+msgid "Cryptographic attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:196
+msgid "Floodfill attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:197
+#: i2p2www/pages/site/docs/how/threat-model.html:809
+msgid "Other Network Database attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:198
+msgid "Attacks on centralized resources"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:199
+#: i2p2www/pages/site/docs/how/threat-model.html:875
+msgid "Development attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:200
+msgid "Implementation attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:201
+#: i2p2www/pages/site/docs/how/threat-model.html:959
+msgid "Other Defenses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:208
+msgid ""
+"A brute force attack can be mounted by a global passive or active "
+"adversary, \n"
+"watching all the messages pass between all of the nodes and attempting to"
+" correlate\n"
+"which message follows which path.  Mounting this attack against I2P "
+"should be \n"
+"nontrivial, as all peers in the network are frequently sending messages "
+"(both\n"
+"end to end and network maintenance messages), plus an end to end message "
+"changes\n"
+"size and data along its path.  In addition, the external adversary does "
+"not have\n"
+"access to the messages either, as inter-router communication is both "
+"encrypted\n"
+"and streamed (making two 1024 byte messages indistinguishable from one "
+"2048 byte\n"
+"message)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:220
+msgid ""
+"However, a powerful attacker can use brute force to detect trends - if "
+"they \n"
+"can send 5GB to an I2P destination and monitor everyone's network "
+"connection,\n"
+"they can eliminate all peers who did not receive 5GB of data.  Techniques"
+" to \n"
+"defeat this attack exist, but may be prohibitively expensive (see: \n"
+"Tarzan's "
+"mimics\n"
+"or constant rate traffic).  Most users are not concerned with this "
+"attack, as \n"
+"the cost of mounting it are extreme (and often require illegal activity)."
+"  \n"
+"However, the attack is still possible, for example by an observer at\n"
+"a large ISP or an Internet exchange point.\n"
+"Those who want to defend against it \n"
+"would want to take appropriate countermeasures, such as\n"
+"setting low bandwidth limits, and using unpublished or encrypted "
+"leasesets for eepsites.\n"
+"Other countermeasures, such as nontrivial delays and restricted routes, "
+"are\n"
+"not currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:237
+#, python-format
+msgid ""
+"As a partial defense against a single router or group of routers trying "
+"to route all the network's traffic,\n"
+"routers contain limits as to how many tunnels can be routed through a "
+"single peer.\n"
+"As the network grows, these limits are subject to further adjustment.\n"
+"Other mechanisms for peer rating, selection and avoidance\n"
+"are discussed on the\n"
+"peer selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:252
+msgid ""
+"I2P's messages are unidirectional and do not necessarily imply that a "
+"reply\n"
+"will be sent.  However, applications on top of I2P will most likely have\n"
+"recognizable patterns within the frequency of their messages - for "
+"instance, an \n"
+"HTTP request will be a small message with a large sequence of reply "
+"messages \n"
+"containing the HTTP response.  Using this data as well as a broad view of"
+" the \n"
+"network topology, an attacker may be able to disqualify some links as "
+"being too \n"
+"slow to have passed the message along."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:262
+msgid ""
+"This sort of attack is powerful, but its applicability to I2P is non "
+"obvious,\n"
+"as the variation on message delays due to queuing, message processing, "
+"and \n"
+"throttling will often meet or exceed the time of passing a message along "
+"a \n"
+"single link - even when the attacker knows that a reply will be sent as "
+"soon as\n"
+"the message is received.  There are some scenarios which will expose "
+"fairly \n"
+"automatic replies though - the streaming library does (with the SYN+ACK) "
+"as does the \n"
+"message mode of guaranteed delivery (with the "
+"DataMessage+DeliveryStatusMessage)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:272
+#, python-format
+msgid ""
+"Without protocol scrubbing or higher latency, global active adversaries "
+"can \n"
+"gain substantial information.  As such, people concerned with these "
+"attacks could\n"
+"increase the latency (using nontrivial "
+"delays or \n"
+"batching strategies), include protocol "
+"scrubbing, or\n"
+"other advanced tunnel routing techniques,\n"
+"but these are unimplemented in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:281
+#, python-format
+msgid ""
+"References: Low-Resource Routing Attacks Against "
+"Anonymous Systems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:289
+msgid ""
+"Intersection attacks against low latency systems are extremely powerful -"
+"\n"
+"periodically make contact with the target and keep track of what peers "
+"are on\n"
+"the network.  Over time, as node churn occurs the attacker will gain \n"
+"significant information about the target by simply intersecting the sets "
+"of\n"
+"peers that are online when a message successfully goes through.  The cost"
+" of \n"
+"this attack is significant as the network grows, but may be feasible in "
+"some\n"
+"scenarios."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:299
+#, python-format
+msgid ""
+"In summary, if an attacker is at both ends of your tunnel at the same "
+"time,\n"
+"he may be successful.\n"
+"I2P does not have a full defense to this for low latency communication.\n"
+"This is an inherent weakness of low-latency onion routing.\n"
+"Tor provides a similar disclaimer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:307
+msgid "Partial defenses implemented in I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:311
+#, python-format
+msgid "strict ordering of peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:314
+#, python-format
+msgid ""
+"peer profiling and selection from a "
+"small group that changes slowly"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:317
+msgid "Limits on the number of tunnels routed through a single peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:320
+msgid ""
+"Prevention of peers from the same /16 IP range from being members of a "
+"single tunnel"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:323
+msgid ""
+"For eepsites or other hosted services, we support\n"
+"simultaneous hosting on multiple routers, or\n"
+"multihoming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:330
+msgid ""
+"Even in total, these defenses are not a complete solution.\n"
+"Also, we have made some design choices that may significantly increase "
+"our vulnerability:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:335
+msgid "We do not use low-bandwidth \"guard nodes\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:338
+msgid ""
+"We use tunnel pools comprised of several tunnels, and traffic can shift "
+"from tunnel to tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:341
+msgid "Tunnels are not long-lived; new tunnels are built every 10 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:344
+msgid ""
+"Tunnel lengths are configurable.\n"
+"While 3-hop tunnels are recommended for full protection, several "
+"applications and\n"
+"services use 2-hop tunnels by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:351
+#, python-format
+msgid ""
+"In the future, it could\n"
+"for peers who can afford significant delays (per nontrivial\n"
+"delays and batching strategies).  "
+"In addition,\n"
+"this is only relevant for destinations that other people know about - a "
+"private\n"
+"group whose destination is only known to trusted peers does not have to "
+"worry,\n"
+"as an adversary can't \"ping\" them to mount the attack.
            "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:360
+#, python-format
+msgid "Reference: One Cell Enough"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:367
+msgid ""
+"There are a whole slew of denial of service attacks available against "
+"I2P,\n"
+"each with different costs and consequences:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:373
+msgid ""
+"Greedy user attack: This is simply\n"
+"people trying to consume significantly more resources than they are \n"
+"willing to contribute. The defense against this is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:379
+#, python-format
+msgid ""
+"Set defaults so that most users provide resources to the network.\n"
+"In I2P, users route traffic by default. In sharp distinction to\n"
+"other networks,\n"
+"over 95% of I2P users relay traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:385
+msgid ""
+"Provide easy configuration options so that users may increase their\n"
+"contribution (share percentage) to the network. Display easy-to-"
+"understand\n"
+"metrics such as \"share ratio\" so that users may see what they are "
+"contributing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:390
+msgid ""
+"Maintain a strong community with blogs, forums, IRC, and other means of "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:397
+#, python-format
+msgid ""
+"Starvation attack: A hostile user may attempt to harm the network "
+"by\n"
+"creating a significant number of peers in the network who are not "
+"identified as\n"
+"being under control of the same entity (as with Sybil). These nodes then"
+" \n"
+"decide not to provide any resources to the network, causing existing "
+"peers \n"
+"to search through a larger network database or request more tunnels than"
+" \n"
+"should be necessary. \n"
+"Alternatively, the nodes may provide intermittent service by periodically"
+"\n"
+"dropping selected traffic, or refusing connections to certain peers.\n"
+"This behavior may be indistinguishable from that of a heavily-loaded or "
+"failing node.\n"
+"I2P addresses these issues by maintaining profiles on the \n"
+"peers, attempting to identify underperforming ones and simply ignoring \n"
+"them, or using them rarely.\n"
+"We have significantly enhanced the\n"
+"ability to recognize and avoid troublesome peers; however there are still"
+"\n"
+"significant efforts required in this area."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:417
+#, python-format
+msgid ""
+"Flooding attack: A hostile user may attempt to flood the network,\n"
+"a peer, a destination, or a tunnel.  Network and peer flooding is "
+"possible,\n"
+"and I2P does nothing to prevent standard IP layer flooding.  The flooding"
+" of\n"
+"a destination with messages by sending a large number to the target's "
+"various\n"
+"inbound tunnel gateways is possible, but the destination will know this "
+"both\n"
+"by the contents of the message and because the tunnel's tests will fail."
+"  The\n"
+"same goes for flooding just a single tunnel.  I2P has no defenses for a "
+"network\n"
+"flooding attack.  For a destination and tunnel flooding attack, the "
+"target\n"
+"identifies which tunnels are unresponsive and builds new ones.  New code "
+"could\n"
+"also be written to add even more tunnels if the client wishes to handle "
+"the\n"
+"larger load.  If, on the other hand, the load is more than the client can"
+"\n"
+"deal with, they can instruct the tunnels to throttle the number of "
+"messages or\n"
+"bytes they should pass on (once the advanced tunnel\n"
+"operation is implemented)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:436
+msgid ""
+"CPU load attack: There are currently some methods for people to \n"
+"remotely request that a peer perform some cryptographically expensive \n"
+"operation, and a hostile attacker could use these to flood that peer with"
+"\n"
+"a large number of them in an attempt to overload the CPU.  Both using "
+"good \n"
+"engineering practices and potentially requiring nontrivial certificates \n"
+"(e.g. HashCash) to be attached to these expensive requests should "
+"mitigate\n"
+"the issue, though there may be room for an attacker to exploit various\n"
+"bugs in the implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:449
+#, python-format
+msgid ""
+"Floodfill DOS attack: A hostile user may attempt to harm the "
+"network by\n"
+"becoming a floodfill router. The current defenses against unreliable,\n"
+"intermittent, or malicious floodfill routers are poor.\n"
+"A floodfill router may provide bad or no response to lookups, and\n"
+"it may also interfere with inter-floodfill communication.\n"
+"Some defenses and\n"
+"peer profiling are implemented,\n"
+"however there is much more to do.\n"
+"For more information see the\n"
+"network database page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:468
+#, python-format
+msgid ""
+"Tagging attacks - modifying a message so that it can later be identified"
+" \n"
+"further along the path - are by themselves impossible in I2P, as messages"
+" \n"
+"passed through tunnels are signed.  However, if an attacker is the "
+"inbound \n"
+"tunnel gateway as well as a participant further along in that tunnel, "
+"with\n"
+"collusion they can identify the fact that they are in the same tunnel "
+"(and \n"
+"prior to adding unique hop ids and "
+"other updates,\n"
+"colluding peers within the same tunnel can recognize that fact without "
+"any \n"
+"effort).  An attacker in an outbound tunnel and any part of an inbound "
+"tunnel cannot \n"
+"collude however, as the tunnel encryption pads and modifies the data "
+"separately\n"
+"for the inbound and outbound tunnels.  External attackers cannot do "
+"anything,\n"
+"as the links are encrypted and messages signed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:486
+msgid ""
+"Partitioning attacks - finding ways to segregate (technically or "
+"analytically)\n"
+"the peers in a network - are important to keep in mind when dealing with "
+"a \n"
+"powerful adversary, since the size of the network plays a key role in "
+"determining\n"
+"your anonymity.  Technical partitioning by cutting links between peers to"
+" create\n"
+"fragmented networks is addressed by I2P's built in network database, "
+"which \n"
+"maintains statistics about various peers so as to allow any existing "
+"connections\n"
+"to other fragmented sections to be exploited so as to heal the network.  "
+"However,\n"
+"if the attacker does disconnect all links to uncontrolled peers, "
+"essentially\n"
+"isolating the target, no amount of network database healing will fix it."
+"  At\n"
+"that point, the only thing the router can hope to do is notice that a "
+"significant\n"
+"number of previously reliable peers have become unavailable and alert the"
+" client\n"
+"that it is temporarily disconnected (this detection code is not "
+"implemented at\n"
+"the moment)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:502
+#, python-format
+msgid ""
+"Partitioning the network analytically by looking for differences in how "
+"routers \n"
+"and destinations behave and grouping them accordingly is also a very "
+"powerful\n"
+"attack.  For instance, an attacker harvesting"
+" the network\n"
+"database will know when a particular destination has 5 inbound tunnels in"
+" their\n"
+"LeaseSet while others have only 2 or 3, allowing the adversary to "
+"potentially \n"
+"partition clients by the number of tunnels selected.  Another partition "
+"is \n"
+"possible when dealing with the nontrivial "
+"delays and \n"
+"batching strategies, as the tunnel "
+"gateways and the\n"
+"particular hops with non-zero delays will likely stand out.  However, "
+"this data\n"
+"is only exposed to those specific hops, so to partition effectively on "
+"that \n"
+"matter, the attacker would need to control a significant portion of the "
+"network\n"
+"(and still that would only be a probabilistic partition, as they wouldn't"
+" know\n"
+"which other tunnels or messages have those delays)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:518
+#, python-format
+msgid ""
+"Also discussed on the network database "
+"page (bootstrap attack)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:526
+msgid ""
+"The predecessor attack is passively gathering statistics in an attempt to"
+" see\n"
+"what peers are 'close' to the destination by participating in their "
+"tunnels and\n"
+"keeping track of the previous or next hop (for outbound or inbound "
+"tunnels, \n"
+"respectively).  Over time, using a perfectly random sample of peers and "
+"random\n"
+"ordering, an attacker would be able to see which peer shows up as "
+"'closer' \n"
+"statistically more than the rest, and that peer would in turn be where "
+"the\n"
+"target is located."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:536
+#, python-format
+msgid ""
+"I2P avoids this in four ways: first, the peers selected to participate in"
+"\n"
+"tunnels are not randomly sampled throughout the network - they are "
+"derived from\n"
+"the peer selection algorithm which "
+"breaks them\n"
+"into tiers.  Second, with strict "
+"ordering of peers\n"
+"in a tunnel, the fact that a peer shows up more frequently does not mean "
+"they're\n"
+"the source.  Third, with permuted "
+"tunnel length\n"
+"(not enabled by default)\n"
+"even 0 hop tunnels can provide plausible deniability as the occasional \n"
+"variation of the gateway will look like normal tunnels.  Fourth, with \n"
+"restricted routes "
+"(unimplemented), only the peer with\n"
+"a restricted connection to the target will ever contact the target, while"
+" \n"
+"attackers will merely run into that gateway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:553
+#, python-format
+msgid ""
+"The current tunnel build method\n"
+"was specifically designed to combat the predecessor attack.\n"
+"See also the intersection attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:559
+#, python-format
+msgid ""
+"References: %(pdf2008)s\n"
+"which is an update to the 2004 predecessor attack paper\n"
+"%(pdf2004)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:571
+msgid ""
+"\"Harvesting\" means compiling a list of users running I2P.\n"
+"It can be used for legal attacks and to help\n"
+"other attacks by simply running a peer, seeing who it connects to, and \n"
+"harvesting whatever references to other peers it can find."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:578
+msgid ""
+"I2P itself is not designed with effective defenses against\n"
+"this attack, since there is the distributed network database \n"
+"containing just this information.\n"
+"The following factors make the attack somewhat harder in practice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:585
+msgid ""
+"Network growth will make it more difficult to obtain a given proportion "
+"of the network"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:588
+msgid "Floodfill routers implement query limits as DOS protection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:591
+msgid ""
+"\"Hidden mode\", which prevents a router from publishing its information "
+"to the netDb,\n"
+"(but also prevents it from relaying data) is not widely used now but "
+"could be."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:597
+#, python-format
+msgid ""
+"In future implementations,\n"
+"basic and \n"
+"comprehensive restricted "
+"routes,\n"
+"this attack loses much of its power, as the \"hidden\" peers do not "
+"publish their\n"
+"contact addresses in the network database - only the tunnels through "
+"which \n"
+"they can be reached (as well as their public keys, etc)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:606
+msgid ""
+"In the future, routers could use GeoIP to identify if they are in a "
+"particular\n"
+"country where identification as an I2P node would be risky.\n"
+"In that case, the router could automatically enable hidden mode, or\n"
+"enact other restricted route methods."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:618
+#, python-format
+msgid ""
+"By inspecting the traffic into and out of a router, a malicious ISP\n"
+"or state-level firewall could identify that a computer is running I2P.\n"
+"As discussed above, I2P is not specifically "
+"designed\n"
+"to hide that a computer is running I2P. However, several design decisions"
+" made\n"
+"in the design of the\n"
+"transport layer and protocols\n"
+"make it somewhat difficult to identify I2P traffic:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:628
+msgid "Random port selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:631
+msgid "Point-to-Point Encryption of all traffic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:634
+msgid ""
+"DH key exchange with no protocol bytes or other unencrypted constant "
+"fields"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:637
+#, python-format
+msgid ""
+"Simultaneous use of both\n"
+"TCP and\n"
+"UDP transports.\n"
+"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to"
+" track."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:645
+msgid ""
+"In the near future, we plan to directly address traffic analysis issues "
+"by further obfuscation of I2P transport protocols, possibly including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:649
+msgid ""
+"Padding at the transport layer to random lengths, especially during the "
+"connection handshake"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:652
+msgid ""
+"Study of packet size distribution signatures, and additional padding as "
+"necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:655
+msgid ""
+"Development of additional transport methods that mimic SSL or other "
+"common protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:658
+msgid ""
+"Review of padding strategies at higher layers to see how they affect "
+"packet sizes at the transport layer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:661
+msgid ""
+"Review of methods implemented by various state-level firewalls to block "
+"Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:664
+msgid "Working directly with DPI and obfuscation experts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:669
+#, python-format
+msgid ""
+"Reference: Breaking and Improving Protocol "
+"Obfuscation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:678
+msgid ""
+"Sybil describes a category of attacks where the adversary creates "
+"arbitrarily\n"
+"large numbers of colluding nodes and uses the increased numbers to help \n"
+"mounting other attacks.  For instance, if an attacker is in a network "
+"where peers\n"
+"are selected randomly and they want an 80% chance to be one of those "
+"peers, they\n"
+"simply create five times the number of nodes that are in the network and "
+"roll \n"
+"the dice.  When identity is free, Sybil can be a very potent technique "
+"for a \n"
+"powerful adversary.  The primary technique to address this is simply to "
+"make \n"
+"identity 'non free' - Tarzan\n"
+"(among others) uses the fact that IP addresses are limited, while \n"
+"IIP used \n"
+"HashCash to 'charge' for "
+"creating a new\n"
+"identity.  We currently have not implemented any particular technique to "
+"address\n"
+"Sybil, but do include placeholder certificates in the router's and \n"
+"destination's data structures which can contain a HashCash certificate of"
+" \n"
+"appropriate value when necessary (or some other certificate proving "
+"scarcity)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:696
+msgid "Requiring HashCash Certificates in various places has two major problems:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:700
+msgid "Maintaining backward compatibility"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:703
+msgid ""
+"The classic HashCash problem -\n"
+"selecting HashCash values that are meaningful proofs of work on high-end "
+"machines,\n"
+"while still being feasible on low-end machines such as mobile devices."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:710
+msgid ""
+"Various limitations on the number of routers in a given IP range restrict"
+"\n"
+"the vulnerability to attackers that don't have the ability to put "
+"machines\n"
+"in several IP blocks.\n"
+"However, this is not a meaningful defense against a powerful adversary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:717
+#, python-format
+msgid ""
+"See the network database page\n"
+"for more Sybil discussion."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:727
+#, python-format
+msgid ""
+"(Reference: In Search of an Anonymouns and Secure "
+"Lookup Section 5.2)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:731
+#, python-format
+msgid ""
+"By refusing to accept or forward tunnel build requests, except to a "
+"colluding peer, a router could ensure\n"
+"that a tunnel is formed wholly from its set of colluding routers.\n"
+"The chances of success are enhanced if there is a large number of "
+"colluding routers,\n"
+"i.e. a Sybil attack.\n"
+"This is somewhat mitigated by our\n"
+"peer profiling methods used to monitor "
+"the performance\n"
+"of peers.\n"
+"However, this is a powerful attack as the number of routers approaches\n"
+"f = 0.2, or 20% malicious nodes, as specifed in the paper.\n"
+"The malicous routers could also maintain connections to the target router"
+" and provide\n"
+"excellent forwarding bandwidth for traffic over those connections, in an "
+"attempt\n"
+"to manipulate the profiles managed by the target and appear attractive.\n"
+"Further research and defenses may be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:752
+#, python-format
+msgid ""
+"We use strong cryptography with long keys, and\n"
+"we assume the security of the industry-standard cryptographic primitives "
+"used in I2P, as documented\n"
+"on the low-level cryptography page. \n"
+"Security features include the immediate detection of \n"
+"altered messages along the path, the inability to decrypt messages not "
+"addressed to you,\n"
+"and defense against man-in-the-middle attacks.\n"
+"The key sizes chosen in 2003 were quite conservative at the time, and are"
+" still longer than\n"
+"those used in other anonymity "
+"networks.\n"
+"We don't think the current key lengths are our biggest weakness,\n"
+"especially for traditional, non-state-level adversaries;\n"
+"bugs and the small size of the network are much more worrisome.\n"
+"Of course, all cryptographic algorithms eventually become obsolete due to"
+"\n"
+"the advent of faster processors, cryptographic research, and advancements"
+" in\n"
+"methods such as rainbow tables, clusters of video game hardware, etc.\n"
+"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys"
+" or change\n"
+"shared secret values while maintaining backward compatibility."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:771
+#, python-format
+msgid ""
+"Upgrading the various data structures and protocols to support longer "
+"keys\n"
+"will have to be tackled eventually, and this will be a\n"
+"major undertaking, just as it will be "
+"for \n"
+"others.\n"
+"Hopefully, through careful planning, we can minimize the disruption, and\n"
+"implement mechanisms to make it easier for future transitions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:780
+msgid ""
+"In the future, several I2P protocols and data structures\n"
+"support securely padding messages to arbitrary sizes, so messages could "
+"be made constant\n"
+"size or garlic messages could be modified randomly so that some cloves "
+"appear to contain\n"
+"more subcloves than they actually do.  At the moment, however, garlic, "
+"tunnel, and \n"
+"end to end messages include simple random padding."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:790
+msgid "Floodfill Anonymity attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:794
+#, python-format
+msgid ""
+"In addition to the floodfill DOS attacks described\n"
+"above, floodfill routers are uniquely positioned\n"
+"to learn about network participants, due to their role\n"
+"in the netDb, and the high frequency of communication with those "
+"participants.\n"
+"This is somewhat mitigated because floodfill routers only manage a "
+"portion\n"
+"of the total keyspace, and the keyspace rotates daily, as explained \n"
+"on the network database page.\n"
+"The specific mechanisms by which routers communicate with floodfills have"
+" been\n"
+"carefully designed.\n"
+"However, these threats should be studied further.\n"
+"The specific potential threats and corresponding defenses are a topic for"
+" future research."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:810
+#, python-format
+msgid ""
+"A hostile user may attempt to harm the network by\n"
+"creating one or more floodfill routers and crafting them to offer\n"
+"bad, slow, or no responses.\n"
+"Several scenarios are discussed on the\n"
+"network database page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:820
+msgid "Central Resource Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:824
+msgid ""
+"There are a few centralized or limited resources (some inside I2P, some "
+"not)\n"
+"that could be attacked or used as a vector for attacks.\n"
+"The absence of jrandom starting November 2007, followed by the loss of "
+"the i2p.net hosting service in January 2008,\n"
+"highlighted numerous centralized resources in the development and "
+"operation of the I2P network,\n"
+"most of which are now distributed.\n"
+"Attacks on externally-reachable resources mainly affect the ability of "
+"new users to find us,\n"
+"not the operation of the network itself."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:834
+#, python-format
+msgid ""
+"The website is mirrored and uses DNS round-robin"
+" for external public access."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:837
+#, python-format
+msgid ""
+"Routers now support multiple external reseed "
+"locations,\n"
+"however more reseed hosts may be needed, and the handling of unreliable "
+"or malicious\n"
+"reseed hosts may need improvement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:842
+msgid ""
+"Routers now support multiple update file locations.\n"
+"A malicious update host could feed a huge file, need to limit the size."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:846
+msgid "Routers now support multiple default trusted update signers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:849
+msgid ""
+"Routers now better handle multiple unreliable "
+"floodfill peers.\n"
+"Malicious floodfills needs more study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:853
+#, python-format
+msgid ""
+"The code is now stored in a distributed source "
+"control system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:856
+msgid ""
+"Routers rely on a single news host, but there is a hardcoded backup URL "
+"pointing to a different host.\n"
+"A malicious news host could feed a huge file, need to limit the size."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:860
+#, python-format
+msgid ""
+"Naming system services, including addressbook "
+"subscription providers, add-host services,\n"
+"and jump services, could be malicious. Substantial protections for "
+"subscriptions were implemented\n"
+"in release 0.6.1.31, with additional enhancements in subsequent releases."
+"\n"
+"However, all naming services require some measure of trust, see\n"
+"the naming page for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:867
+msgid ""
+"We remain reliant on the DNS service for i2p2.de, losing this would cause"
+" substantial\n"
+"disruption in our ability to attract new users,\n"
+"and would shrink the network (in the short-to-medium term), just as the "
+"loss of i2p.net did."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:879
+msgid ""
+"These attacks aren't directly on the network, but instead go after its "
+"development team \n"
+"by either introducing legal hurdles on anyone contributing to the "
+"development\n"
+"of the software, or by using whatever means are available to get the "
+"developers to \n"
+"subvert the software.  Traditional technical measures cannot defeat these"
+" attacks, and\n"
+"if someone threatened the life or livelihood of a developer (or even just"
+" issuing a \n"
+"court order along with a gag order, under threat of prison), we would "
+"have a big problem."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:888
+msgid "However, two techniques help defend against these attacks:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:892
+#, python-format
+msgid ""
+"All components of the network must be open source to enable inspection, "
+"verification, \n"
+"modification, and improvement.  If a developer is compromised, once it is"
+" noticed \n"
+"the community should demand explanation and cease to accept that "
+"developer's work.\n"
+"All checkins to our distributed source control "
+"system\n"
+"are cryptographically signed, and the release packagers use a trust-list "
+"system\n"
+"to restrict modifications to those previously approved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:900
+#, python-format
+msgid ""
+"Development over the network itself, allowing developers to stay "
+"anonymous but still \n"
+"secure the development process.  All I2P development can occur through "
+"I2P - using\n"
+"a distributed source control system,\n"
+"a distributed source control system, IRC chat,\n"
+"public web servers,\n"
+"discussion forums (forum.i2p), and the software distribution sites,\n"
+"all available within I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:911
+msgid ""
+"We also maintain relationships with various organizations that offer "
+"legal advice,\n"
+"should any defense be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:916
+msgid "Implementation attacks (bugs)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:920
+msgid ""
+"Try as we might, most nontrivial applications include errors in the "
+"design or \n"
+"implementation, and I2P is no exception.  There may be bugs that could be"
+" exploited to \n"
+"attack the anonymity or security of the communication running over I2P in"
+" unexpected \n"
+"ways.  To help withstand attacks against the design or protocols in use, "
+"we publish \n"
+"all designs and documentation and solicit review and criticism with \n"
+"the hope that many eyes will improve the system.\n"
+"We do not believe in\n"
+"security through "
+"obscurity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:931
+msgid ""
+"In addition, the code is being \n"
+"treated the same way, with little aversion towards reworking or throwing "
+"out \n"
+"something that isn't meeting the needs of the software system (including "
+"ease of \n"
+"modification).  Documentation for the design and implementation of the "
+"network and \n"
+"the software components are an essential part of security, as without "
+"them it is \n"
+"unlikely that developers would be willing to spend the time to learn the "
+"software \n"
+"enough to identify shortcomings and bugs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:941
+msgid ""
+"Our software is likely, in particular, to contain bugs related to denial "
+"of service\n"
+"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues  "
+"in the router console,\n"
+"and other vulnerabilities to non-standard inputs via the various "
+"protocols."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:947
+#, python-format
+msgid ""
+"I2P is still a small network with a small development community and "
+"almost no\n"
+"interest from academic or research groups.\n"
+"Therefore we lack the analysis that\n"
+"other anonymity networks\n"
+"may have received. We continue to recruit people to\n"
+"get involved and help."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:960
+msgid "Blocklists"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:961
+msgid ""
+"To some extent, I2P could be enhanced to avoid peers operating at IP "
+"addresses\n"
+"listed in a blocklist. Several blocklists are commonly available in "
+"standard formats,\n"
+"listing anti-P2P organizations, potential state-level adversaries, and "
+"others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:967
+msgid ""
+"To the extent that active peers actually do show up in the actual "
+"blocklist,\n"
+"blocking by only a subset of peers would tend to segment the network,\n"
+"exacerbate reachability problems, and decrease overall reliability.\n"
+"Therefore we would want to agree on a particular blocklist and\n"
+"enable it by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:975
+msgid ""
+"Blocklists are only a part (perhaps a small part) of an array of defenses"
+"\n"
+"against maliciousness.\n"
+"In large part the profiling system does a good job of measuring\n"
+"router behavior so that we don't need to trust anything in netDb.\n"
+"However there is more that can be done. For each of the areas in the\n"
+"list above there are improvements we can make in detecting badness."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:984
+msgid ""
+"If a blocklist is hosted at a central location with automatic updates\n"
+"the network is vulnerable to a\n"
+"central resource attack.\n"
+"Automatic subscription to a list gives the list provider the power to "
+"shut\n"
+"the i2p network down. Completely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:992
+msgid ""
+"Currently, a default blocklist is distributed with our software,\n"
+"listing only the IPs of past DOS sources.\n"
+"There is no automatic update mechanism.\n"
+"Should a particular IP range implement serious attacks on the I2P "
+"network,\n"
+"we would have to ask people to update their blocklist manually through\n"
+"out-of-band mechanisms such as forums, blogs, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:2
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:6
+msgid "Tunnel Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:3
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:3
+msgid "July 2011"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:7
+msgid ""
+"This page contains an overview of I2P tunnel terminology and operation, "
+"with\n"
+"links to more technical pages, details, and specifications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:12
+#, python-format
+msgid ""
+"As briefly explained in the introduction, I2P "
+"builds virtual \"tunnels\" -\n"
+"temporary and unidirectional paths through a sequence of routers.  These"
+" \n"
+"tunnels are classified as either inbound tunnels (where everything \n"
+"given to it goes towards the creator of the tunnel) or outbound tunnels\n"
+"(where the tunnel creator shoves messages away from them).  When Alice\n"
+"wants to send a message to Bob, she will (typically) send it out one of\n"
+"her existing outbound tunnels with instructions for that tunnel's "
+"endpoint\n"
+"to forward it to the gateway router for one of Bob's current inbound \n"
+"tunnels, which in turn passes it to Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:25
+msgid "Alice connecting through her outbound tunnel to Bob via his inbound tunnel"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:27
+msgid "Outbound Gateway"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:28
+msgid "Outbound Participant"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:29
+#: i2p2www/pages/site/docs/tunnels/implementation.html:131
+msgid "Outbound Endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
+#: i2p2www/pages/site/docs/tunnels/implementation.html:140
+msgid "Inbound Gateway"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:31
+msgid "Inbound Participant"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:32
+msgid "Inbound Endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:36
+msgid "Tunnel vocabulary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:38
+#, python-format
+msgid ""
+"Tunnel gateway - the first router in a tunnel.  For inbound "
+"tunnels,\n"
+"this is the one mentioned in the LeaseSet published in the\n"
+"network database.  For outbound tunnels, the\n"
+"gateway is the originating router.  (e.g. both A and D above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:44
+msgid ""
+"Tunnel endpoint - the last router in a tunnel.  (e.g. both C and F"
+" above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:45
+msgid ""
+"Tunnel participant - all routers in a tunnel except for the "
+"gateway or\n"
+"endpoint (e.g. both B and E above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:49
+msgid ""
+"n-Hop tunnel - a tunnel with a specific number of inter-router "
+"jumps, e.g.:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:51
+msgid "0-hop tunnel - a tunnel where the gateway is also the endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:52
+msgid ""
+"1-hop tunnel - a tunnel where the gateway talks directly to the "
+"endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:53
+msgid ""
+"2-(or more)-hop tunnel - a tunnel where there is at least one "
+"intermediate\n"
+"tunnel participant. (the above diagram includes two 2-hop tunnels - one\n"
+"outbound from Alice, one inbound to Bob)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:60
+#, python-format
+msgid ""
+"Tunnel ID - A 4 "
+"byte integer\n"
+"different for each hop in a tunnel, and unique among all tunnels on a "
+"router.\n"
+"Chosen randomly by the tunnel creator."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:67
+msgid "Tunnel Build Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:68
+#, python-format
+msgid ""
+"Routers performing the three roles (gateway, participant, endpoint) are "
+"given\n"
+"different pieces of data in the initial\n"
+"Tunnel Build Message\n"
+"to accomplish their tasks:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:75
+msgid "The tunnel gateway gets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:77
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:97
+#, python-format
+msgid ""
+"tunnel encryption key - an AES private key for "
+"encrypting\n"
+"messages and instructions to the next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:81
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:101
+#, python-format
+msgid ""
+"tunnel IV key - an AES private key for "
+"double-encrypting\n"
+"the IV to the next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:85
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:105
+#, python-format
+msgid ""
+"reply key - an AES public key for "
+"encrypting\n"
+"the reply to the tunnel build request"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:89
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:109
+msgid ""
+"reply IV - the IV for encrypting the reply to the tunnel build "
+"request"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:90
+msgid "tunnel id - 4 byte integer (inbound gateways only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:91
+msgid ""
+"next hop - what router is the next one in the path (unless this is"
+" a 0-hop tunnel, and the gateway is also the endpoint)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:92
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:112
+msgid "next tunnel id - The tunnel ID on the next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:95
+msgid "All intermediate tunnel participants get:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:110
+msgid "tunnel id - 4 byte integer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:111
+msgid "next hop - what router is the next one in the path"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:115
+msgid "The tunnel endpoint gets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:117
+#, python-format
+msgid ""
+"tunnel encryption key - an AES private key for "
+"encrypting\n"
+"messages and instructions to the the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:121
+#, python-format
+msgid ""
+"tunnel IV key - an AES private key for "
+"double-encrypting\n"
+"the IV to the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:125
+#, python-format
+msgid ""
+"reply key - an AES public key for "
+"encrypting\n"
+"the reply to the tunnel build request (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:129
+msgid ""
+"reply IV - the IV for encrypting the reply to the tunnel build "
+"request (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:130
+msgid "tunnel id - 4 byte integer (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:131
+msgid ""
+"reply router - the inbound gateway of the tunnel to send the reply"
+" through (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:132
+msgid ""
+"reply tunnel id - The tunnel ID of the reply router (outbound "
+"endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:137
+#, python-format
+msgid ""
+"Details are in the\n"
+"tunnel creation specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:142
+msgid "Tunnel pooling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:143
+#, python-format
+msgid ""
+"Several tunnels for a particular purpose may be grouped into a \"tunnel "
+"pool\",\n"
+"as described in the\n"
+"tunnel specification.\n"
+"This provides redundancy and additional bandwidth.\n"
+"The pools used by the router itself are called \"exploratory tunnels\".\n"
+"The pools used by applications are called \"client tunnels\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:154
+msgid "Tunnel length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:155
+#, python-format
+msgid ""
+"As mentioned above, each client requests that their router provide "
+"tunnels to\n"
+"include at least a certain number of hops.\n"
+"The decision as to how many routers\n"
+"to have in one's outbound and inbound tunnels has an important effect "
+"upon the\n"
+"latency, throughput, reliability, and anonymity provided by I2P - the "
+"more peers\n"
+"that messages have to go through, the longer it takes to get there and "
+"the more\n"
+"likely that one of those routers will fail prematurely.  The less routers"
+" in a\n"
+"tunnel, the easier it is for an adversary to mount traffic analysis "
+"attacks and\n"
+"pierce someone's anonymity.\n"
+"Tunnel lengths are specified by clients via\n"
+"I2CP options.\n"
+"The maximum number of hops in a tunnel is 7."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:171
+msgid "0-hop tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:172
+msgid ""
+"With no remote routers in a tunnel, the user has very basic plausible\n"
+"deniability (since no one knows for sure that the peer that sent them the"
+"\n"
+"message wasn't simply just forwarding it on as part of the tunnel). "
+"However, it\n"
+"would be fairly easy to mount a statistical analysis attack and notice "
+"that\n"
+"messages targeting a specific destination are always sent through a "
+"single\n"
+"gateway.  Statistical analysis against outbound 0-hop tunnels are more "
+"complex,\n"
+"but could show similar information (though would be slightly harder to "
+"mount)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:182
+msgid "1-hop tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:183
+#, python-format
+msgid ""
+"With only one remote router in a tunnel, the user has both plausible\n"
+"deniability and basic anonymity, as long as they are not up against an "
+"internal\n"
+"adversary (as described on threat model)."
+" However,\n"
+"if the adversary ran a sufficient number of routers such that the single "
+"remote\n"
+"router in the tunnel is often one of those compromised ones, they would "
+"be able\n"
+"to mount the above statistical traffic analysis attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:192
+msgid "2-hop tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:193
+msgid ""
+"With two or more remote routers in a tunnel, the costs of mounting the "
+"traffic\n"
+"analysis attack increases, since many remote routers would have to be "
+"compromised\n"
+"to mount it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:199
+msgid "3-hop (or more) tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:200
+#, python-format
+msgid ""
+"To reduce the susceptibility to some attacks,\n"
+"3 or more hops are recommended for the highest level of protection.\n"
+"Recent studies\n"
+"also conclude that more than 3 hops does not provide additional "
+"protection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:208
+msgid "Tunnel default lengths"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:209
+#, python-format
+msgid ""
+"The router uses 2-hop tunnels by default for its exploratory tunnels.\n"
+"Client tunnel defaults are set by the application, using\n"
+"I2CP options.\n"
+"Most applications use 2 or 3 hops as their default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:218
+msgid "Tunnel testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:219
+#, python-format
+msgid ""
+"All tunnels are periodically tested by their creator by sending a\n"
+"DeliveryStatusMessage out an outbound tunnel and bound for another "
+"inbound tunnel\n"
+"(testing both tunnels at once).  If either fails a number of consecutive "
+"tests, it is marked as no longer\n"
+"functional. If it was used for a client's inbound tunnel, a new leaseSet\n"
+"is created.\n"
+"Tunnel test failures are also reflected in the\n"
+"capacity rating in the peer "
+"profile."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:230
+msgid "Tunnel creation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:231
+#, python-format
+msgid ""
+"Tunnel creation is handled by garlic "
+"routing\n"
+"a Tunnel Build Message to a router, requesting that they participate in "
+"the\n"
+"tunnel (providing them with all of the appropriate information, as above,"
+" along\n"
+"with a certificate, which right now is a 'null' cert, but will support "
+"hashcash\n"
+"or other non-free certificates when necessary).\n"
+"That router forwards the message to the next hop in the tunnel.\n"
+"Details are in the\n"
+"tunnel creation specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:245
+#, python-format
+msgid ""
+"Multi-layer encryption is handled by garlic"
+" encryption\n"
+"of tunnel messages.\n"
+"Details are in the\n"
+"tunnel specification.\n"
+"The IV of each hop is encrypted with a separate key as explained there."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:257
+msgid ""
+"Other tunnel test techniques could be used, such as\n"
+"garlic wrapping a number of tests into cloves, testing individual tunnel\n"
+"participants separately, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:263
+msgid "Move to 3-hop exploratory tunnels defaults."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:267
+msgid ""
+"In a distant future release,\n"
+"options specifying the pooling, mixing, and chaff generation settings may"
+" be implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:272
+msgid ""
+"In a distant future release,\n"
+"limits on the quantity and size of messages allowed during the\n"
+"tunnel's lifetime may be implemented (e.g. no more than 300 messages or\n"
+"1MB per minute)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:284
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:15
+msgid "Tunnel specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:286
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:17
+msgid "Tunnel creation specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:288
+msgid "Unidirectional tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:290
+msgid "Tunnel message specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:292
+msgid "Garlic routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:294
+msgid "ElGamal/AES+SessionTag"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:296
+msgid "I2CP options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:6
+msgid ""
+"The I2P Client Protocol (I2CP) exposes a strong separation of concerns "
+"between\n"
+"the router and any client that wishes to communicate over the network.  "
+"It enables\n"
+"secure and asynchronous messaging by sending and receiving messages over "
+"a \n"
+"single TCP socket.\n"
+"With I2CP, a client application tells the\n"
+"router who they are (their \"destination\"), what anonymity, reliability,"
+" and \n"
+"latency tradeoffs to make, and where to send messages.  In turn the "
+"router uses\n"
+"I2CP to tell the client when any messages have arrived, and to request "
+"authorization\n"
+"for some tunnels to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:18
+#, python-format
+msgid ""
+"The protocol itself is implemented in Java, to provide the\n"
+"Client SDK.\n"
+"This SDK is exposed in the i2p.jar package, which implements the client-"
+"side of I2CP.\n"
+"Clients should never need to access the router.jar package, which "
+"contains the\n"
+"router itself and the router-side of I2CP.\n"
+"There is also a C library implementation.\n"
+"A non-Java client would also have to implement the\n"
+"streaming library for TCP-style connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:31
+#, python-format
+msgid ""
+"Applications can take advantage of the base I2CP plus the \n"
+"streaming and datagram libraries\n"
+"by using the Simple Anonymous Messaging or BOB protocols,\n"
+"which do not require clients to deal with any sort of cryptography.\n"
+"Also, clients may access the network by one of several proxies -\n"
+"HTTP, CONNECT, and SOCKS 4/4a/5.\n"
+"Alternatively, Java clients may access those libraries in "
+"ministreaming.jar and streaming.jar.\n"
+"So there are several options for both Java and non-Java applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:43
+#, python-format
+msgid ""
+"Client-side end-to-end encryption (encrypting the data over the I2CP "
+"connection)\n"
+"was disabled in I2P release 0.6,\n"
+"leaving in place the ElGamal/AES end-to-end "
+"encryption\n"
+"which is implemented in the router.\n"
+"The only cryptography that client libraries must still implement is\n"
+"DSA public/private key signing\n"
+"for LeaseSets and\n"
+"Session Configurations, and"
+" management of those keys."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:56
+msgid ""
+"In a standard I2P installation, port 7654 is used by external java "
+"clients to communicate\n"
+"with the local router via I2CP.\n"
+"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, "
+"set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart.\n"
+"Clients in the same JVM as the router pass messages directly to the "
+"router\n"
+"through an internal JVM interface."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:65
+#, python-format
+msgid ""
+"The router also supports external connections over SSL.\n"
+"While SSL is not the default, it is strongly recommended for any traffic "
+"that may\n"
+"be exposed to the open Internet. The authorization user/password (if "
+"any), the\n"
+"Private Key and\n"
+"Signing Private "
+"Key for the\n"
+"Destination\n"
+"are all transmitted in-the-clear unless SSL is enabled."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:75
+msgid "I2CP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:76
+#, python-format
+msgid "Now on the I2CP Specification page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:81
+msgid "I2CP Initialization"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:82
+#, python-format
+msgid ""
+"When a client connects to the router, it first sends a single protocol "
+"version byte (0x2A).\n"
+"Then it sends a GetDate Message and "
+"waits for the SetDate Message "
+"response.\n"
+"Next, it sends a CreateSession "
+"Message containing the session configuration.\n"
+"It next awaits a RequestLeaseSet"
+" Message from the router, indicating that inbound tunnels\n"
+"have been built, and responds with a CreateLeaseSetMessage containing the"
+" signed LeaseSet.\n"
+"The client may now initiate or receive connections from other I2P "
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:91
+msgid "I2CP Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:92
+#, python-format
+msgid ""
+"The following options are traditionally passed to the router via\n"
+"a SessionConfig contained "
+"in a CreateSession Message or "
+"a ReconfigureSession "
+"Message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:98
+msgid "Router-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:103
+#: i2p2www/pages/site/docs/protocol/i2cp.html:446
+msgid "As Of Release"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:104
+#: i2p2www/pages/site/docs/protocol/i2cp.html:447
+msgid "Recommended Arguments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:105
+#: i2p2www/pages/site/docs/protocol/i2cp.html:448
+msgid "Allowable Range"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:113
+#: i2p2www/pages/site/docs/protocol/i2cp.html:126
+#: i2p2www/pages/site/docs/protocol/i2cp.html:135
+#: i2p2www/pages/site/docs/protocol/i2cp.html:144
+#: i2p2www/pages/site/docs/protocol/i2cp.html:153
+#: i2p2www/pages/site/docs/protocol/i2cp.html:168
+#: i2p2www/pages/site/docs/protocol/i2cp.html:183
+#: i2p2www/pages/site/docs/protocol/i2cp.html:192
+#: i2p2www/pages/site/docs/protocol/i2cp.html:240
+#: i2p2www/pages/site/docs/protocol/i2cp.html:252
+#: i2p2www/pages/site/docs/protocol/i2cp.html:264
+#, python-format
+msgid "number from %(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:114
+#: i2p2www/pages/site/docs/protocol/i2cp.html:136
+#: i2p2www/pages/site/docs/protocol/i2cp.html:145
+#: i2p2www/pages/site/docs/protocol/i2cp.html:154
+#: i2p2www/pages/site/docs/protocol/i2cp.html:169
+#: i2p2www/pages/site/docs/protocol/i2cp.html:241
+#: i2p2www/pages/site/docs/protocol/i2cp.html:253
+#: i2p2www/pages/site/docs/protocol/i2cp.html:265
+#: i2p2www/pages/site/docs/protocol/i2cp.html:538
+#, python-format
+msgid "%(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:116
+msgid ""
+"Number of tunnels in.\n"
+"Limit was increased from 6 to 16 in release 0.9; however, numbers higher "
+"than 6 are not\n"
+"currently recommended, as this is untested and is incompatible with older"
+" releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:127
+#: i2p2www/pages/site/docs/protocol/i2cp.html:184
+#: i2p2www/pages/site/docs/protocol/i2cp.html:193
+msgid "No limit"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:129
+msgid "Number of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:138
+msgid "Length of tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:147
+msgid "Length of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:156
+msgid ""
+"Random amount to add or subtract to the length of tunnels in.\n"
+"A positive number x means add a random amount from 0 to x inclusive.\n"
+"A negative number -x means add a random amount from -x to x inclusive.\n"
+"The router will limit the total length of the tunnel to 0 to 7 inclusive."
+"\n"
+"The default variance was 1 prior to release 0.7.6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:171
+msgid ""
+"Random amount to add or subtract to the length of tunnels out.\n"
+"A positive number x means add a random amount from 0 to x inclusive.\n"
+"A negative number -x means add a random amount from -x to x inclusive.\n"
+"The router will limit the total length of the tunnel to 0 to 7 inclusive."
+"\n"
+"The default variance was 1 prior to release 0.7.6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:186
+msgid "Number of redundant fail-over for tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:195
+msgid "Number of redundant fail-over for tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:204
+msgid ""
+"Name of tunnel - generally used in routerconsole, which will\n"
+"use the first few characters of the Base64 hash of the destination by "
+"default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:216
+msgid "Name of tunnel - generally ignored unless inbound.nickname is unset."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:225
+msgid "If incoming zero hop tunnel is allowed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:234
+msgid "If outgoing zero hop tunnel is allowed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:243
+#: i2p2www/pages/site/docs/protocol/i2cp.html:255
+msgid ""
+"Number of IP bytes to match to determine if\n"
+"two routers should not be in the same tunnel. 0 to disable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:267
+msgid ""
+"Priority adjustment for outbound messages.\n"
+"Higher is higher priority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:279
+msgid "Should generally be set to true for clients and false for servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:288
+msgid ""
+"Guaranteed is disabled;\n"
+"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1,"
+" the client side default is None as of 0.9.4"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:300
+#: i2p2www/pages/site/docs/protocol/i2cp.html:579
+msgid ""
+"If true, the router just sends the MessagePayload instead\n"
+"of sending a MessageStatus and awaiting a ReceiveMessageBegin."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:312
+msgid ""
+"Comma-separated list of Base 64 Hashes of peers to build tunnels through;"
+" for debugging only"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:321
+msgid ""
+"For authorization, if required by the router.\n"
+"If the client is running in the same JVM as a router, this option is not "
+"required.\n"
+"Warning - username and password are sent in the clear to the router, "
+"unless using SSL (i2cp.SSL=true).\n"
+"Authorization is only recommended when using SSL."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:343
+msgid ""
+"Number of ElGamal/AES Session Tags to send at a time.\n"
+"For clients with relatively low bandwidth per-client-pair (IRC, some UDP "
+"apps), this may be set lower."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:355
+msgid ""
+"Minimum number of ElGamal/AES Session Tags before we send more.\n"
+"Recommended: approximately tagsToSend * 2/3"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:367
+msgid ""
+"Set to false to disable ever bundling a reply LeaseSet.\n"
+"For clients that do not publish their LeaseSet, this option must be true\n"
+"for any reply to be possible. \"true\" is also recommended for multihomed"
+" servers\n"
+"with long connection times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:374
+msgid ""
+"Setting to \"false\" may save significant outbound bandwidth, especially "
+"if\n"
+"the client is configured with a large number of inbound tunnels (Leases)."
+"\n"
+"If replies are still required, this may shift the bandwidth burden to\n"
+"the far-end client and the floodfill.\n"
+"There are several cases where \"false\" may be appropriate:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:382
+msgid "Unidirectional communication, no reply required"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:383
+msgid "LeaseSet is published and higher reply latency is acceptable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:384
+msgid ""
+"LeaseSet is published, client is a \"server\", all connections are "
+"inbound\n"
+"so the connecting far-end destination obviously has the leaseset already."
+"\n"
+"Connections are either short, or it is acceptable for latency on a long-"
+"lived\n"
+"connection to temporarily increase while the other end re-fetches the "
+"LeaseSet\n"
+"after expiration.\n"
+"HTTP servers may fit these requirements."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:402
+msgid ""
+"Any other options prefixed with \"inbound.\" are stored\n"
+"in the \"unknown options\" properties of the inbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:414
+msgid ""
+"Any other options prefixed with \"outbound.\" are stored\n"
+"in the \"unknown options\" properties of the outbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:421
+msgid ""
+"Note: Large quantity, length, or variance settings may cause significant "
+"performance or reliability problems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:425
+#, python-format
+msgid ""
+"Note: As of release 0.7.7, option names and values must use UTF-8 "
+"encoding.\n"
+"This is primarily useful for nicknames.\n"
+"Prior to that release, options with multi-byte characters were corrupted."
+"\n"
+"Since options are encoded in a Mapping,\n"
+"all option names and values are limited to 255 bytes (not characters) "
+"maximum."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:433
+msgid ""
+"The following options are interpreted on the client side,\n"
+"and will be interpreted if passed to the I2PSession via the "
+"I2PClient.createSession() call.\n"
+"The streaming lib should also pass these options through to I2CP.\n"
+"Other implementations may have different defaults."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:441
+msgid "Client-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:459
+msgid ""
+"Router hostname.\n"
+"If the client is running in the same JVM as a router, this option is "
+"ignored, and the client connects to that router internally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:471
+msgid ""
+"Router I2CP port.\n"
+"If the client is running in the same JVM as a router, this option is "
+"ignored, and the client connects to that router internally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:483
+msgid ""
+"Connect to the router using SSL.\n"
+"If the client is running in the same JVM as a router, this option is "
+"ignored, and the client connects to that router internally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:495
+msgid "Gzip outbound data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:504
+msgid "Reduce tunnel quantity when idle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:513
+msgid "Close I2P session when idle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:520
+#: i2p2www/pages/site/docs/protocol/i2cp.html:529
+#, python-format
+msgid "%(num)s minimum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:522
+msgid "(ms) Idle time required (default 20 minutes, minimum 5 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:531
+msgid "(ms) Idle time required (default 30 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:540
+msgid "Tunnel quantity when reduced (applies to both inbound and outbound)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:549
+msgid "Encrypt the lease"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:558
+msgid "Base64 SessionKey (44 characters)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:567
+msgid ""
+"Guaranteed is disabled;\n"
+"None implemented in 0.8.1; None is the default as of 0.9.4"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:586
+msgid ""
+"Note: All arguments, including numbers, are strings. True/false values "
+"are case-insensitive strings.\n"
+"Anything other than case-insensitive \"true\" is interpreted as false.\n"
+"All option names are case-sensitive."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:592
+msgid "I2CP Payload Data Format and Multiplexing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:593
+#, python-format
+msgid ""
+"The end-to-end messages handled by I2CP (i.e. the data sent by the client"
+" in a\n"
+"SendMessageMessage\n"
+"and received by the client in a\n"
+"MessagePayloadMessage)\n"
+"are gzipped with a standard 10-byte gzip\n"
+"header beginning with 0x1F 0x8B 0x08 as\n"
+"specified by RFC "
+"1952.\n"
+"As of release 0.7.1, I2P uses ignored portions of the gzip header to "
+"include\n"
+"protocol, from-port, and to-port information, thus supporting streaming "
+"and\n"
+"datagrams on the same destination, and allowing query/response using "
+"datagrams\n"
+"to work reliably in the presence of multiple channels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:607
+msgid ""
+"The gzip function cannot be completely turned off, however setting "
+"i2cp.gzip=false\n"
+"turns the gzip effort setting to 0, which may save a little CPU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:613
+#: i2p2www/pages/site/docs/protocol/i2np.html:33
+msgid "Bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:614
+msgid "Content"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:619
+msgid "Gzip header"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:624
+msgid "Gzip flags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:629
+msgid "I2P Source port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:634
+msgid "I2P Destination port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:639
+msgid "Gzip xflags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:644
+msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:648
+msgid ""
+"Data integrity is verified with the standard gzip CRC-32 as\n"
+"specified by RFC 1952."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:656
+msgid ""
+"The current authorization mechanism could be modified to use hashed "
+"passwords."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:660
+msgid ""
+"The Signing Private Keys is included in the Create Lease Set message,\n"
+"it is not required. Revocation is unimplemented.\n"
+"It should be replaced with random data or removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:666
+#, python-format
+msgid ""
+"Some improvements may be able to use messages previously defined but not "
+"implemented.\n"
+"For reference, here is the\n"
+"I2CP Protocol Specification Version 0.9\n"
+"(PDF) dated August 28, 2003.\n"
+"That document also references the\n"
+"Common Data Structures Specification Version 0.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:3
+msgid "June 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:6
+msgid "I2P Network Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:7
+msgid ""
+"The I2P Network Protocol (I2NP),\n"
+"which is sandwiched between I2CP and the various I2P transport protocols,"
+" manages the\n"
+"routing and mixing of messages between routers, as well as the selection "
+"of what\n"
+"transports to use when communicating with a peer for which there are "
+"multiple\n"
+"common transports supported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:15
+msgid "I2NP Definition"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:16
+msgid ""
+"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-"
+"router, point-to-point messages.\n"
+"By encrypting and wrapping messages in other messages, they can be sent "
+"in a secure way\n"
+"through multiple hops to the ultimate destination.\n"
+"Priority is only used locally at the origin, i.e. when queuing for "
+"outbound delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:23
+#, python-format
+msgid ""
+"The priorities listed below may not be current and are subject to change."
+"\n"
+"See the OutNetMessage Javadocs\n"
+"for the current priority settings.\n"
+"Priority queueing implementation may vary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:30
+msgid "Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:33
+#: i2p2www/pages/site/docs/spec/streaming.html:35
+msgid "Field"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:34
+msgid "Unique ID"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:35
+msgid "Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:36
+#: i2p2www/pages/site/docs/protocol/i2np.html:93
+msgid "Payload Length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:37
+msgid "Checksum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:38
+msgid "Payload"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:41
+#, python-format
+msgid ""
+"While the maximum payload size is nominally 64KB, the size is further "
+"constrained by the\n"
+"method of fragmenting I2NP messages into multiple 1KB tunnel messages as "
+"described on\n"
+"the tunnel implementation page.\n"
+"The maximum number of fragments is 64, and the message may not be "
+"perfectly aligned,\n"
+"So the message must nominally fit in 63 fragments."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:49
+msgid ""
+"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL "
+"delivery mode);\n"
+"the maximum size of a follow-on fragment is 996 bytes.\n"
+"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 "
+"bytes, or 61.2 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:55
+msgid ""
+"In addition, the transports may have additional restrictions.\n"
+"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be "
+"increased in a future release.\n"
+"The SSU limit is approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:61
+msgid ""
+"Note that these are not the limits for datagrams that the client sees, as"
+" the\n"
+"router may bundle a reply leaseset and/or session tags together with the "
+"client message\n"
+"in a garlic message. The leaseset and tags together may add about 5.5KB.\n"
+"Therefore the current datagram limit is about 10KB. This limit will be\n"
+"increased in a future release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:69
+msgid "Message Types"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:70
+msgid ""
+"Higher-numbered priority is higher priority.\n"
+"The majority of traffic is TunnelDataMessages (priority 400),\n"
+"so anything above 400 is essentially high priority, and\n"
+"anything below is low priority.\n"
+"Note also that many of the messages are generally routed\n"
+"through exploratory tunnels, not client tunnels, and\n"
+"therefore may not be in the same queue unless the\n"
+"first hops happen to be on the same peer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:81
+msgid ""
+"Also, not all message types are sent unencrypted.\n"
+"For example, when testing a tunnel, the router wraps a\n"
+"DeliveryStatusMessage, which is wrapped in a GarlicMessage,\n"
+"which is wrapped in a DataMessage."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:91
+msgid "Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:92
+msgid "Type"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:95
+msgid "Comments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:103
+msgid "May vary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:109
+msgid ""
+"Size is 65 + 32*(number of hashes) where typically, the hashes for\n"
+"three floodfill routers are returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:118
+msgid "Varies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:120
+msgid ""
+"Priority may vary.\n"
+"Size is 898 bytes for a typical 2-lease leaseSet.\n"
+"RouterInfo structures are compressed, and size varies; however\n"
+"there is a continuing effort to reduce the amount of data published in a "
+"RouterInfo\n"
+"as we approach release 1.0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:134
+msgid "Priority may vary on a per-destination basis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:144
+msgid ""
+"Used for message replies, and for testing tunnels - generally wrapped in "
+"a GarlicMessage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:152
+msgid ""
+"Generally wrapped in a DataMessage -\n"
+"but when unwrapped, given a priority of 100 by the forwarding router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:179
+msgid ""
+"The most common message. Priority for tunnel participants, outbound "
+"endpoints, and inbound gateways was\n"
+"reduced to 200 as of release 0.6.1.33.\n"
+"Outbound gateway messages (i.e. those originated locally) remains at 400."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:199
+msgid "Shorter TunnelBuildMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:207
+msgid "Shorter TunnelBuildReplyMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:210
+#, python-format
+msgid "Others listed in 2003 Spec"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:216
+msgid "Obsolete, Unused"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:220
+msgid "Full Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:221
+#, python-format
+msgid ""
+"On the I2NP Specification page.\n"
+"See also the\n"
+"Common Data Structure Specification "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:228
+msgid ""
+"It isn't clear whether the current priority scheme is generally "
+"effective,\n"
+"and whether the priorities for various messages should be adjusted "
+"further.\n"
+"This is a topic for further research, analysis and testing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:2
+msgid "Protocol Stack"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:7
+#, python-format
+msgid ""
+"Here is the protocol stack for I2P.\n"
+"See also the Index to Technical Documentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:12
+msgid ""
+"Each of the layers in the stack provides extra capabilities.\n"
+"The capabilities are listed below, starting at the bottom of the protocol"
+" stack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:18
+msgid "Internet Layer:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:20
+msgid ""
+"IP: Internet Protocol, allow addressing hosts on the regular internet and"
+" routing packets across the internet using best-effort delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:23
+msgid "Transport Layer:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:25
+msgid ""
+"TCP: Transmission Control Protocol, allow reliable, in-order delivery of "
+"packets across the internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:27
+msgid ""
+"UDP: User Datagram Protocol, allow unreliable, out-of-order delivery of "
+"packets across the internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:30
+msgid ""
+"I2P Transport Layer: provide encrypted connections between 2 I2P "
+"routers. These are not anonymous yet, this is strictly a hop-to-hop "
+"connection.\n"
+"Two protocols are implemented to provide these capabilities. NTCP builds "
+"on top of TCP, while SSU uses UDP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:35
+msgid "NIO-based TCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:37
+msgid "Secure Semi-reliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:40
+msgid "I2P Tunnel Layer: provide full encrypted tunnel connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:42
+#, python-format
+msgid ""
+"Tunnel messages: tunnel messages are "
+"large messages containing encrypted I2NP (see below) messages and "
+"encrypted instructions for their delivery.\n"
+"The encryption is layered. The first hop will decrypt the tunnel message "
+"and read a part. Another part can still be encrypted (with another key),"
+"\n"
+"so it will be forwarded."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:48
+#, python-format
+msgid ""
+"I2NP messages: I2P Network Protocol messages are"
+" used to pass messages through multiple routers. These I2NP messages are "
+"combined in tunnel messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:53
+msgid ""
+"I2P Garlic Layer: provide encrypted and anonymous end-to-end I2P "
+"message delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:55
+#, python-format
+msgid ""
+"I2NP messages: I2P Network Protocol messages are"
+" wrapped in each other and used to ensure encryption between two tunnels "
+"and are passed along from source to destination, keeping both anonymous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:61
+msgid ""
+"The following layers are strictly speaking no longer part of the I2P "
+"Protocol stack, they are not part of the core 'I2P router' functionality."
+"\n"
+"However, each of these layers adds additional functionality, to allow "
+"applications simple and convenient I2P usage."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:67
+msgid ""
+"I2P Client Layer: allow any client to use I2P functionality, "
+"without requiring the direct use of the router API."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:69
+#, python-format
+msgid ""
+"I2CP: I2P Client Protocol, allows secure and "
+"asynchronous messaging over I2P by communicating messages over the I2CP "
+"TCP socket."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:74
+msgid ""
+"I2P End-to-end Transport Layer: allow TCP- or UDP-like "
+"functionality on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:76
+#, python-format
+msgid ""
+"Streaming Library: an implementation of "
+"TCP-like streams over I2P. This allows easier porting of existing "
+"applications to I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:80
+#, python-format
+msgid ""
+"Datagram Library: an implementation of UDP-"
+"like messages over I2P. This allows easier porting of existing "
+"applications to I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:85
+msgid ""
+"I2P Application Interface Layer: additional (optional) libraries "
+"allowing easier implementations on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:93
+msgid "I2P Application Proxy Layer: proxy systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:95
+#, python-format
+msgid "HTTP Client/Server, IRC Client, SOCKS, Streamr"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:99
+msgid ""
+"Finally, what could be considered the 'I2P application layer', is "
+"a large number of applications on top of I2P.\n"
+"We can order this based on the I2P stack layer they use."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:104
+msgid "Streaming/datagram applications: i2psnark, Syndie, i2phex..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:105
+msgid "SAM/BOB applications: IMule, i2p-bt, i2prufus, Robert..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:106
+#, python-format
+msgid ""
+"Other I2P applications: Syndie, EepGet, plugins..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:107
+msgid ""
+"Regular applications: Jetty, Apache, Monotone, CVS, browsers, "
+"e-mail..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:111
+msgid "I2P Network stack"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:113
+msgid "Figure 1: The layers in the I2P Network stack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:118
+msgid "Note: SAM/SAMv2 can use both the streaming lib and datagrams."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:2
+msgid "I2P Blockfile Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:3
+msgid "January 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:6
+msgid "Blockfile and Hosts Database Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:8
+#, python-format
+msgid ""
+"This document specifies\n"
+"the I2P blockfile file format\n"
+"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:14
+msgid ""
+"The blockfile provides fast Destination lookup in a compact format. While"
+" the blockfile page overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry.\n"
+"The metadata may be used in the future to provide advanced addressbook "
+"features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:24
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is adopted from the\n"
+"Metanotion Blockfile Database.\n"
+"First we will define the file format, then the use of that format by the "
+"BlockfileNamingService."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:32
+msgid "Blockfile Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:33
+msgid ""
+"The original blockfile spec was modified to add magic numbers to each "
+"page.\n"
+"The file is structured in 1024-byte pages. Pages are numbered starting "
+"from 1.\n"
+"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the "
+"file.\n"
+"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in"
+" the file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:40
+msgid ""
+"All 2-byte integer values are unsigned.\n"
+"All 4-byte integer values (page numbers) are signed and negative values "
+"are illegal."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:45
+msgid ""
+"The database is designed to be opened and accessed by a single thread.\n"
+"The BlockfileNamingService provides synchronization."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:50
+msgid "Superblock format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:65
+msgid "Skip list block page format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:80
+msgid ""
+"Skip level block page format is as follows.\n"
+"All levels have a span. Not all spans have levels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:95
+msgid ""
+"Skip span block page format is as follows.\n"
+"Key/value structures are sorted by key within each span and across all "
+"spans.\n"
+"Key/value structures are sorted by key within each span.\n"
+"Spans other than the first span may not be empty."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:112
+msgid "Span Continuation block page format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:123
+msgid ""
+"Key/value structure format is as follows.\n"
+"Key and value lengths must not be split across pages, i.e. all 4 bytes "
+"must be on the same page.\n"
+"If there is not enough room the last 1-3 bytes of a page are unused and "
+"the lengths will\n"
+"be at offset 8 in the continuation page.\n"
+"Key and value data may be split across pages.\n"
+"Max key and value lengths are 65535 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:139
+msgid "Free list block page format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:151
+msgid "Free page block format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:160
+msgid ""
+"The metaindex (located at page 2) is a mapping of US-ASCII strings to "
+"4-byte integers.\n"
+"The key is the name of the skiplist and the value is the page index of "
+"the skiplist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:165
+msgid "Blockfile Naming Service Tables"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:166
+msgid ""
+"The tables created and used by the BlockfileNamingService are as follows."
+"\n"
+"The maximum number of entries per span is 16."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:171
+msgid "Properties Skiplist"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:172
+#, python-format
+msgid ""
+"%(INFO)s is the master database skiplist with String/Properties key/value"
+" entries containing only one entry:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:184
+msgid "Reverse Lookup Skiplist"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:185
+#, python-format
+msgid ""
+"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties "
+"key/value entries\n"
+"    (as of database version 2):"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:199
+msgid "hosts.txt, userhosts.txt, and privatehosts.txt Skiplists"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:200
+msgid ""
+"For each host database, there is a skiplist containing\n"
+"the hosts for that database.\n"
+"The keys/values in these skiplists are as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:211
+msgid "The DestEntry Properties typically contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:220
+msgid "Hostname keys are stored in lower-case and always end in \".i2p\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:2
+msgid "Common structure Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:6
+msgid "Data types Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:7
+#, python-format
+msgid ""
+"This document describes some data types common to all I2P protocols, like"
+"\n"
+"I2NP, I2CP,\n"
+"SSU, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:17
+msgid "Represents a non-negative integer.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:20
+#: i2p2www/pages/site/docs/spec/common-structures.html:31
+#: i2p2www/pages/site/docs/spec/common-structures.html:41
+#: i2p2www/pages/site/docs/spec/common-structures.html:54
+#: i2p2www/pages/site/docs/spec/common-structures.html:69
+#: i2p2www/pages/site/docs/spec/common-structures.html:82
+#: i2p2www/pages/site/docs/spec/common-structures.html:94
+#: i2p2www/pages/site/docs/spec/common-structures.html:106
+#: i2p2www/pages/site/docs/spec/common-structures.html:118
+#: i2p2www/pages/site/docs/spec/common-structures.html:130
+#: i2p2www/pages/site/docs/spec/common-structures.html:142
+#: i2p2www/pages/site/docs/spec/common-structures.html:154
+#: i2p2www/pages/site/docs/spec/common-structures.html:166
+#: i2p2www/pages/site/docs/spec/common-structures.html:178
+#: i2p2www/pages/site/docs/spec/common-structures.html:231
+#: i2p2www/pages/site/docs/spec/common-structures.html:314
+#: i2p2www/pages/site/docs/spec/common-structures.html:363
+#: i2p2www/pages/site/docs/spec/common-structures.html:415
+#: i2p2www/pages/site/docs/spec/common-structures.html:462
+#: i2p2www/pages/site/docs/spec/common-structures.html:597
+#: i2p2www/pages/site/docs/spec/common-structures.html:660
+#: i2p2www/pages/site/docs/spec/streaming.html:35
+msgid "Contents"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:21
+msgid "1 to 8 bytes in network byte order representing an unsigned integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:27
+msgid ""
+"The number of milliseconds since midnight on January 1, 1970 in the GMT "
+"timezone.\n"
+"If the number is 0, the date is undefined or null.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:32
+msgid "8 byte Integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:38
+msgid "Represents a UTF-8 encoded string.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:42
+msgid ""
+"1 or more bytes where the first byte is the number of bytes (not "
+"characters!)\n"
+"in the string and the remaining 0-255 bytes are the non-null terminated "
+"UTF-8 encoded character array.\n"
+"Length limit is 255 bytes (not characters). Length may be 0.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:50
+msgid ""
+"A boolean value, supporting null/unknown representation\n"
+"0=false, 1=true, 2=unknown/null\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:55
+msgid "1 byte Integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:59
+msgid "Deprecated - unused\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:65
+#, python-format
+msgid ""
+"This structure is used in ElGamal encryption, representing only the "
+"exponent, not the primes, which are constant and defined in\n"
+"the cryptography specification.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:70
+#: i2p2www/pages/site/docs/spec/common-structures.html:83
+msgid "256 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:78
+#, python-format
+msgid ""
+"This structure is used in ElGamal decryption, representing only the "
+"exponent, not the primes which are constant and defined in\n"
+"the cryptography specification.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:91
+msgid "This structure is used for AES256 encryption and decryption.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:95
+#: i2p2www/pages/site/docs/spec/common-structures.html:143
+#: i2p2www/pages/site/docs/spec/common-structures.html:155
+msgid "32 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:103
+#, python-format
+msgid ""
+"This structure is used for verifying DSA signatures.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:107
+msgid "128 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:115
+#, python-format
+msgid ""
+"This structure is used for creating DSA signatures.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:119
+msgid "20 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:127
+#, python-format
+msgid ""
+"This structure represents the DSA "
+"signature of some data.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:131
+msgid "40 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:139
+msgid "Represents the SHA256 of some data.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:151
+msgid "A random number\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:163
+msgid "Defines an identifier that is unique to each router in a tunnel.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:167
+msgid "4 byte Integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:175
+msgid ""
+"A certificate is a container for various receipts or proof of works used "
+"throughout the I2P network.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:179
+msgid ""
+"1 byte Integer specifying certificate type,"
+" followed by a 2 Integer specifying the "
+"size of the certificate payload, then that many bytes.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:205
+msgid ""
+"For Router Identities, the "
+"Certificate is always NULL, no others are currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:209
+#, python-format
+msgid ""
+"For Garlic Cloves, the "
+"Certificate is always NULL, no others are currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:213
+#, python-format
+msgid ""
+"For Garlic Messages, the Certificate "
+"is always NULL, no others are currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:217
+msgid ""
+"For Destinations, the Certificate may"
+" be non-NULL,\n"
+"however non-NULL certs are not widely used, and any checking is left to "
+"the application-level."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:228
+msgid "A set of key/value mappings or properties\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:232
+msgid "A 2-byte size Integer followed by a series of String=String; pairs\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:259
+msgid ""
+"The encoding isn't optimal - we either need the '=' and ';' characters, "
+"or the string lengths, but not both"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:263
+msgid ""
+"Some documentation says that the strings may not include '=' or ';' but "
+"this encoding supports them"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:267
+msgid ""
+"Strings are defined to be UTF-8 but in the current implementation, I2CP "
+"uses UTF-8 but I2NP does not.\n"
+"For example,\n"
+"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store "
+"Message will be corrupted."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:273
+msgid ""
+"The encoding allows duplicate keys, however in any usage where the "
+"mapping is signed,\n"
+"duplicates may cause a signature failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:278
+msgid ""
+"Mappings contained in I2NP messages (i.e. in a RouterAddress or "
+"RouterInfo)\n"
+"must be sorted by key so that the signature will be invariant.\n"
+"Duplicate keys are not allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:284
+#, python-format
+msgid ""
+"Mappings contained in an I2CP "
+"SessionConfig\n"
+"must be sorted by key so that the signature will be invariant.\n"
+"Duplicate keys are not allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:290
+msgid ""
+"While it is application-dependent, keys and values are generally case-"
+"sensitive."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:294
+msgid ""
+"Key and value string length limits are 255 bytes (not characters) each, "
+"plus the length byte. Length byte may be 0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:298
+msgid ""
+"Total length limit is 65535 bytes, plus the 2 byte size field, or 65537 "
+"total."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:307
+msgid "Common structure specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:311
+msgid "Defines the way to uniquely identify a particular router\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:315
+msgid ""
+"PublicKey followed by SigningPublicKey and then a Certificate\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:352
+msgid ""
+"The certificate for a RouterIdentity is currently unused and is always "
+"NULL."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:360
+msgid ""
+"A Destination defines a particular endpoint to which messages can be "
+"directed for secure delivery.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:364
+msgid ""
+"PublicKey followed by a SigningPublicKey and then a Certificate\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:412
+msgid ""
+"Defines the authorization for a particular tunnel to receive messages "
+"targeting a Destination.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:416
+msgid ""
+"SHA256 Hash of the\n"
+"RouterIdentity of the gateway "
+"router, then the TunnelId, and finally an "
+"end Date\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:447
+msgid "Total size: 44 bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:457
+msgid ""
+"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be "
+"encrypted,\n"
+"and then the public key that can "
+"be used to revoke this particular version of the structure. The LeaseSet is one of the two structures "
+"stored in the network database(\n"
+"the other being RouterInfo), and is "
+"keyed under the SHA256 of the contained Destination.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:463
+msgid ""
+"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to"
+" revoke this version of the LeaseSet,\n"
+"then a 1 byte Integer specifying how many "
+"Lease structures are in the set, followed "
+"by the actual Lease structures and finally "
+"a Signature  of the previous\n"
+"bytes signed by the Destination's SigningPrivateKey"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:555
+msgid ""
+"The public key of the destination was used for the old i2cp-to-i2cp "
+"encryption\n"
+"which was disabled in version 0.6, it is currently unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:560
+#, python-format
+msgid ""
+"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n"
+"It is currently generated anew at every router startup, it is not "
+"persistent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:565
+msgid ""
+"The signature may be verified using the signing public key of the "
+"destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:569
+msgid ""
+"The signing_key is currently unused. It was intended for LeaseSet "
+"revocation, which is unimplemented.\n"
+"It is currently generated anew at every router startup, it is not "
+"persistent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:573
+msgid ""
+"The earliest expiration of all the Leases is treated as the timestamp or "
+"version of the LeaseSet.\n"
+"Routers will generally not accept a store of a LeaseSet unless it is "
+"\"newer\" than the current one.\n"
+"Take care when publishing a new LeaseSet where the oldest Lease is the "
+"same as the oldest Lease\n"
+"in the previous LeaseSet. The publishing router should generally "
+"increment the expiration\n"
+"of the oldest Lease by at least 1 ms in that case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:580
+msgid ""
+"Prior to release 0.9.7, when included in a DatabaseStore Message sent by "
+"the originating router,\n"
+"the router set all the published leases' expirations to the same value, "
+"that of the\n"
+"earliest lease. As of release 0.9.7, the router publishes the actual "
+"lease expiration for each lease.\n"
+"This is an implementation detail and not part of the structures "
+"specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:594
+msgid ""
+"This structure defines the means to contact a router through a transport "
+"protocol.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:598
+msgid ""
+"1 byte Integer defining the relative cost "
+"of using the address, where 0 is free and 255 is expensive, followed by "
+"the expiration Date after which the address "
+"should not be used, or if null, the address never expires.\n"
+"After that comes a String defining the "
+"transport protocol this router address uses. Finally there is a Mapping containing all of the transport "
+"specific options necessary to establish the connection, such as\n"
+"IP address, port number, email address, URL, etc.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:633
+msgid "Cost is typically 5 or 6 for SSU, and 10 or 11 for NTCP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:637
+msgid ""
+"Expiration is currently unused, always null (all zeroes)).\n"
+"As of release 0.9.3, the expiration is assumed zero and not stored, so "
+"any non-zero expiration\n"
+"will fail in the RouterInfo signature verification.\n"
+"Implementing expiration (or another use for these bytes) will be a "
+"backwards-incompatible change.\n"
+"Routers MUST set this field to all zeros."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:645
+msgid ""
+"The following options, while not required, are standard and expected to "
+"be present in most router addresses:\n"
+"\"host\" (an IPv4 or IPv6 address or host name) and \"port\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:656
+msgid ""
+"Defines all of the data that a router wants to publish for the network to"
+" see. The RouterInfo is one of two "
+"structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of"
+"\n"
+"the contained RouterIdentity.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:661
+msgid ""
+"RouterIdentity followed by the Date, when the entry was published\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:741
+msgid ""
+"The peer_size Integer may be followed by a list of that many router "
+"hashes.\n"
+"This is currently unused. It was intended for a form of restricted "
+"routes, which is unimplemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:746
+msgid ""
+"The signature may be verified using the signing public key of the "
+"router_ident."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:750
+#, python-format
+msgid ""
+"See the network database page\n"
+"for standard options that are expected to be present in all router infos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:760
+#, python-format
+msgid ""
+"Defined in the Tunnel Message "
+"Specification.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:2
+msgid "Configuration File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:7
+msgid ""
+"This page provides a general specification of I2P configuration files,\n"
+"used by the router and various applications.\n"
+"It also gives an overview of the information contained in the various "
+"files,\n"
+"and links to detailed documentation where available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:15
+msgid "General Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:16
+#, python-format
+msgid ""
+"An I2P configuration file is formatted as specified in\n"
+"Java Properties\n"
+"with the following exceptions:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:22
+msgid "Encoding must be UTF-8"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:23
+msgid ""
+"Does not use or recognize any escapes, including '\\', so lines may not "
+"be continued"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:24
+msgid "'#' or ';' starts a comment, but '!' does not"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:25
+msgid ""
+"'#' starts a comment in any position but ';' must be in column 1 to start"
+" a comment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:26
+msgid "Leading and trailing whitespace is not trimmed on keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:27
+msgid "Leading and trailing whitespace is trimmed on values"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:28
+msgid "'=' is the only key-termination character (not ':' or whitespace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:29
+msgid ""
+"Lines without '=' are ignored. It does not store the key with a value of "
+"\"\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:30
+msgid ""
+"As there are no escapes, keys may not contain '#', '=', or '\n"
+"', or start with ';'"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:31
+msgid ""
+"As there are no escapes, values may not contain '#' or '\n"
+"', or start or end with '\r"
+"' or whitespace"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:34
+msgid ""
+"The file need not be sorted, but most applications do sort by key when\n"
+"writing to the file, for ease of reading and manual editing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:39
+#, python-format
+msgid ""
+"Reads and writes are implemented in\n"
+"DataHelper loadProps() and storeProps().\n"
+"Note that the file format is significantly different than the\n"
+"serialized format for I2P protocols specified in\n"
+"Mapping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:48
+msgid "Core library and router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:50
+msgid "Clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:51
+msgid "Configured via /configclients in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:55
+msgid "Logger"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:56
+msgid "Configured via /configlogging in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:60
+msgid "Individual Plugin"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:61
+#, python-format
+msgid "See the plugin specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:66
+msgid "Enable/disable for each installed plugin."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:70
+msgid "Router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:71
+msgid "Configured via /configadvanced in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:75
+msgid "Applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:78
+msgid "See documentation in SusiDNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:83
+msgid "Configured via the application gui."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:88
+msgid "Configured via the /i2ptunnel application in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:92
+msgid "Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:93
+msgid "The router console uses the router.config file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:98
+msgid "See post on zzz.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:2
+msgid "Datagram Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:6
+msgid "See the Datagrams page for an overview of the Datagrams API."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:12
+msgid "Non-Repliable Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:13
+msgid ""
+"Non-repliable datagrams have no 'from' address and are not authenticated."
+"\n"
+"They are also called \"raw\" datagrams.\n"
+"Strictly speaking, they are not \"datagrams\" at all, they are just raw "
+"data.\n"
+"They are not handled by the datagram API.\n"
+"However, SAM and the I2PTunnel classes support \"raw datagrams\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:21
+msgid "Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:31
+#, python-format
+msgid ""
+"The practical length is limited by lower layers of protocols - the\n"
+"tunnel message spec\n"
+"limits messages to about 61.2 KB and the\n"
+"transports\n"
+"currently limit messages to about 32 KB, although this may be raised in "
+"the future."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:40
+msgid "Repliable Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:41
+msgid ""
+"Repliable datagrams contain a 'from' address and a signature. These add "
+"427 bytes of overhead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:91
+#, python-format
+msgid ""
+"The practical length is limited by lower layers of protocols - the\n"
+"transports\n"
+"currently limit messages to about 32 KB, so the data length here is "
+"limited to about\n"
+"31.5 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:97
+msgid "See important notes above about the reliability of large datagrams."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:2
+msgid "GeoIP File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:8
+msgid ""
+"This page specifies the format of the various GeoIP files,\n"
+"used by the router to look up a country for an IP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:14
+msgid "Country Name (countries.txt) Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:15
+msgid ""
+"This format is easily generated from data files available from many "
+"public sources.\n"
+"For example:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:33
+msgid "IPv4 (geoip.txt) Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:34
+msgid ""
+"This format is borrowed from Tor and is easily generated from data files "
+"available from many public sources.\n"
+"For example:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:54
+msgid "IPv6 (geoipv6.dat.gz) Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:55
+msgid ""
+"This is a compressed binary format designed for I2P.\n"
+"The file is gzipped. Ungzipped format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:71
+msgid "NOTES:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:2
+msgid "Streaming Library Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:6
+msgid "See the Streaming page for an overview of the Streaming Library."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:11
+msgid "Packet Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:12
+msgid "The format of a single packet in the streaming protocol is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:35
+msgid "Length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:83
+msgid "Flags and Option Data Fields"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:84
+msgid ""
+"The flags field above specifies some metadata about the packet, and in\n"
+"turn may require certain additional data to be included.  The flags are\n"
+"as follows. Any data structures specified must be added to the options "
+"area\n"
+"in the given order."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:2
+msgid "I2P Software Update Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:7
+msgid ""
+"I2P uses a simple, yet secure, system for automated software update.\n"
+"The router console periodically pulls a news file from a configurable I2P"
+" URL.\n"
+"There is a hardcoded backup URL pointing to the project website, in case\n"
+"the default project news host goes down."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:14
+msgid ""
+"The contents of the news file are displayed on the home page of the "
+"router console.\n"
+"In addition, the news file contains the most recent version number of the"
+" software.\n"
+"If the version is higher than the router's version number, it will\n"
+"display an indication to the user that an update is available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:21
+msgid ""
+"The router may optionally download, or download and install, the new "
+"version\n"
+"if configured to do so."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:26
+msgid "News File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:27
+msgid "The news.xml file may contain the following elements:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:35
+msgid ""
+"Parameters in the i2p.release entry are as follows.\n"
+"All keys are case-insensitive. All values must be enclosed in double "
+"quotes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:73
+msgid ""
+"The elements may be included inside XML comments to prevent "
+"interpretation by browsers.\n"
+"The i2p.release element and version are required. All others are "
+"optional.\n"
+"NOTE: Due to parser limitations an entire element must be on a single "
+"line."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:80
+msgid "Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:81
+msgid ""
+"As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n"
+"use the \"su3\" file format specified below.\n"
+"Approved release signers will use 4096-bit RSA keys.\n"
+"The X.509 public key certificates for these signers are distributed in "
+"the router installation packages.\n"
+"The updates may contain certificates for new, approved signers, and/or "
+"contain\n"
+"a list of certificates to delete for revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:91
+msgid "Old Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:92
+msgid "This format is obsolte as of release 0.9.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:95
+msgid ""
+"The signed update file, traditionally named i2pupdate.sud,\n"
+"is simply a zip file with a prepended 56 byte header.\n"
+"The header contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:101
+#, python-format
+msgid ""
+"A 40-byte DSA "
+"signature"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:104
+msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:109
+#, python-format
+msgid ""
+"The signature covers only the zip archive - not the prepended version.\n"
+"The signature must match one of the DSA public keys "
+"configured into the router,\n"
+"which has a hardcoded default list of keys of the current project release"
+" managers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:115
+msgid ""
+"For version comparison purposes, version fields contain [0-9]*, field "
+"separators are\n"
+"'-', '_', and '.', and all other characters are ignored."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:120
+msgid ""
+"As of version 0.8.8, the version must also be specified as a zip file "
+"comment in UTF-8,\n"
+"without the trailing zeroes.\n"
+"The updating router verifes that the version in the header (not covered "
+"by the signature)\n"
+"matches the version in the zip file comment, which is covered by the "
+"signature.\n"
+"This prevents spoofing of the version number in the header."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:128
+msgid "Download and Installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:129
+msgid ""
+"The router first downloads the header of the update file from one in a "
+"configurable list of I2P URLs,\n"
+"using the built-in HTTP client and proxy,\n"
+"and checks that the version is newer.\n"
+"This prevents the problem of update hosts that do not have the latest "
+"file.\n"
+"The router then downloads the full update file.\n"
+"The router verifies that the update file version is newer before "
+"installation.\n"
+"It also, of course, verifies the signature, and\n"
+"verifes that the zip file comment matches the header version, as "
+"explained above."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:140
+msgid "The zip file is extracted in the base $I2P installation directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:144
+msgid ""
+"As of release 0.7.12, the router supports Pack200 decompression.\n"
+"Files inside the zip archive with a .jar.pack or .war.pack suffix\n"
+"are transparently decompressed to a .jar or .war file.\n"
+"Update files containing .pack files are traditionally named with a '.su2'"
+" suffix.\n"
+"Pack200 shrinks the update files by about 60%."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:152
+msgid ""
+"As of release 0.8.7, the router will delete the libjbigi.so and "
+"libjcpuid.so files\n"
+"if the zip archive contains a lib/jbigi.jar file, so that the new files "
+"will\n"
+"be extracted from jbigi.jar."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:158
+msgid ""
+"As of release 0.8.12, if the zip archive contains a file deletelist.txt, "
+"the router will\n"
+"delete the files listed there. The format is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:163
+msgid "One file name per line"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:164
+msgid ""
+"All file names are relative to the installation directory; no absolute "
+"file names allowed, no files starting with \"..\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:165
+msgid "Comments start with '#'"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:168
+msgid "The router will then delete the deletelist.txt file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:173
+msgid "New \"su3\" Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:175
+msgid ""
+"This specification is used for router updates and reseed data as of "
+"release 0.9.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:179
+msgid "Issues with the previous .sud/.su2 format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:181
+msgid "No magic number or flags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:184
+msgid "No way to specify compression, pack200 or not, or signing algo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:187
+msgid ""
+"Version is not covered by signature, so it is enforced by requiring it\n"
+"to be in the zip file comment (for router files) or in the plugin.config\n"
+"file (for plugins)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:192
+msgid "Signer not specified so verifier must try all known keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:195
+msgid "Signature-before-data format requires two passes to generate file"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:201
+msgid "Goals:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:204
+msgid "Fix above problems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:207
+msgid "Migrate to more secure signature algorithm"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:210
+msgid ""
+"Keep version info in same format and offset for compatibility with\n"
+"existing version checkers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:216
+msgid "Specification:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:275
+msgid "All unused fields must be set to 0 for compatibility with future versions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:282
+msgid ""
+"The network will eventually grow too large for update over HTTP.\n"
+"The built-in BitTorrent client, i2psnark, may be used as a distributed "
+"update method.\n"
+"This development effort is ongoing and should be completed by late 2013."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:287
+msgid ""
+"The router update mechanism is part of the web router console.\n"
+"There is currently no provision for updates of an embedded router lacking"
+" the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:2
+msgid "Transport Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:6
+msgid "Transports in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:8
+msgid ""
+"A \"transport\" in I2P is a method for direct, point-to-point "
+"communication\n"
+"between two routers.\n"
+"Transports must provide confidentiality and integrity \n"
+"against external adversaries while authenticating that the router "
+"contacted \n"
+"is the one who should receive a given message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:16
+msgid ""
+"I2P supports multiple transports simultaneously.\n"
+"There are two transports currently implemented:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:21
+#, python-format
+msgid "NTCP, a Java New I/O (NIO) TCP transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:22
+#, python-format
+msgid " SSU, or Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:25
+msgid ""
+"Each provides a \"connection\" paradigm, with authentication,\n"
+"flow control, acknowledgments and retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:31
+msgid "Transport Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:33
+msgid "The transport subsystem in I2P provides the following services:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:37
+#, python-format
+msgid ""
+"Reliable delivery of I2NP messages.\n"
+"Transports support I2NP message delivery ONLY.\n"
+"They are not general-purpose data pipes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:42
+msgid ""
+"Maintain a set of router addresses, one or more for each transport,\n"
+"that the router publishes as its global contact information (the "
+"RouterInfo).\n"
+"Each transport may connect using one of these addresses, which may be\n"
+"IPv4 or (as of version 0.9.8) IPv6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:48
+msgid "Selection of the best transport for each outgoing message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:49
+msgid "Queueing of outbound messages by priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:50
+msgid ""
+"Bandwidth limiting, both outbound and inbound, according to router "
+"configuration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:51
+msgid "Setup and teardown of transport connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:52
+msgid "Encryption of point-to-point communications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:53
+msgid ""
+"Maintenance of connection limits for each transport, implementation of "
+"various thresholds for these limits,\n"
+"and communication of threshold status to the router so it may make "
+"operational changes based on the status"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:57
+msgid "Firewall port opening using UPnP (Universal Plug and Play)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:58
+msgid "Cooperative NAT/Firewall traversal"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:59
+msgid ""
+"Local IP detection by various methods, including UPnP, inspection of "
+"incoming connections, and enumeration of network devices"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:60
+msgid ""
+"Coordination of firewall status and local IP, and changes to either, "
+"among the transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:61
+#: i2p2www/pages/site/docs/transport/ssu.html:33
+msgid ""
+"Communication of firewall status and local IP, and changes to either, to "
+"the router and the user interface"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:62
+msgid ""
+"Determination of a consensus clock, which is used to periodically update "
+"the router's clock, as a backup for NTP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:63
+msgid ""
+"Maintenance of status for each peer, including whether it is connected, "
+"whether it was recently connected,\n"
+"and whether it was reachable in the last attempt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:67
+msgid "Qualification of valid IP addresses according to a local rule set"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:68
+msgid ""
+"Honoring the automated and manual lists of banned peers maintained by the"
+" router,\n"
+"and refusing outbound and inbound connections to those peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:75
+msgid "Transport Addresses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:77
+msgid ""
+"The transport subsystem maintains a set of router addresses, each of "
+"which lists a transport method, IP, and port.\n"
+"These addresses constitute the advertised contact points, and are "
+"published by the router to the network database.\n"
+"Addresses may also contain an arbitrary set of additional options."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:83
+msgid "Typical scenarios are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:85
+msgid ""
+"A router has no published addresses, so it is considered \"hidden\" and "
+"cannot receive incoming connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:86
+#, python-format
+msgid ""
+"A router is firewalled, and therefore publishes an SSU address which "
+"contains a list of cooperating\n"
+"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:90
+msgid ""
+"A router is not firewalled or its NAT ports  are open; it publishes both "
+"NTCP and SSU addresses containing\n"
+"directly-accessible IP and ports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:96
+msgid "Transport Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:98
+#, python-format
+msgid ""
+"The transport system delivers I2NP messages "
+"only. The transport selected for any message is\n"
+"independent of the upper-layer protocols and contents (router or client "
+"messages, whether an external application was using\n"
+"TCP or UDP to connect to I2P, whether the upper layer was using\n"
+"the streaming library\n"
+"streaming\n"
+"or\n"
+"datagrams,\n"
+"datagrams\n"
+"etc.)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:112
+msgid ""
+"For each outgoing message, the transport system solicits \"bids\" from "
+"each transport.\n"
+"The transport bidding the lowest (best) value wins the bid and receives "
+"the message for delivery.\n"
+"A transport may refuse to bid."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:118
+msgid "Whether a transport bids, and with what value, depend on numerous factors:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:122
+msgid "Configuration of transport preferences"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:123
+msgid "Whether the transport is already connected to the peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:124
+msgid ""
+"The number of current connections compared to various connection limit "
+"thresholds"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:125
+msgid "Whether recent connection attempts to the peer have failed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:126
+msgid ""
+"The size of the message, as different transports have different size "
+"limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:127
+msgid ""
+"Whether the peer can accept incoming connections for that transport, as "
+"advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:128
+msgid "Whether the connection would be indirect (requiring introducers) or direct"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:129
+msgid "The peer's transport preference, as advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:132
+msgid ""
+"In general, the bid values are selected so that two routers are only "
+"connected by a single transport\n"
+"at any one time. However, this is not a requirement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:139
+msgid "New Transports and Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:141
+msgid "Additional transports may be developed, including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:146
+msgid "A TLS/SSH look-alike transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:147
+msgid ""
+"An \"indirect\" transport for routers that are not reachable by all other"
+" routers (one form of \"restricted routes\")"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:150
+msgid ""
+"Work continues on adjusting default connection limits for each transport."
+"\n"
+"I2P is designed as a \"mesh network\", where it is assumed that any "
+"router can connect to any other router.\n"
+"This assumption may be broken by routers that have exceeded their "
+"connection limits, and by\n"
+"routers that are behind restrictive state firewalls (restricted routes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:157
+msgid ""
+"The current connection limits are higher for SSU than for NTCP, based on "
+"the assumption that\n"
+"the memory requirements for an NTCP connection are higher than that for "
+"SSU.\n"
+"However, as NTCP buffers are partially in the kernel and SSU buffers are "
+"on the Java heap,\n"
+"that assumption is difficult to verify."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:164
+#, python-format
+msgid ""
+"Analyze Breaking and Improving Protocol "
+"Obfuscation\n"
+"and see how transport-layer padding may improve things."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:6
+msgid "NTCP (NIO-based TCP)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:8
+#, python-format
+msgid ""
+"NTCP is one of two transports currently "
+"implemented in I2P.\n"
+"The other is SSU.\n"
+"NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n"
+"Java NIO (new I/O) does not suffer from the 1 thread per connection "
+"issues of the old TCP transport.\n"
+"NTCP-over-IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:16
+msgid ""
+"By default, NTCP uses the IP/Port\n"
+"auto-detected by SSU. When enabled on config.jsp,\n"
+"SSU will notify/restart NTCP when the external address changes\n"
+"or when the firewall status changes.\n"
+"Now you can enable inbound TCP without a static IP or dyndns service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:24
+msgid ""
+"The NTCP code within I2P is relatively lightweight (1/4 the size of the "
+"SSU code)\n"
+"because it uses the underlying Java TCP transport for reliable delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:30
+msgid "NTCP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:32
+msgid "Standard Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:33
+msgid ""
+"After establishment,\n"
+"the NTCP transport sends individual I2NP messages, with a simple "
+"checksum.\n"
+"The unencrypted message is encoded as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:43
+msgid ""
+"The data is then AES/256/CBC encrypted. The session key for the "
+"encryption\n"
+"is negotiated during establishment (using Diffie-Hellman 2048 bit).\n"
+"The establishment between two routers is implemented in the "
+"EstablishState class\n"
+"and detailed below.\n"
+"The IV for AES/256/CBC encryption is the last 16 bytes of the previous "
+"encrypted message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:51
+msgid ""
+"0-15 bytes of padding are required to bring the total message length\n"
+"(including the six size and checksum bytes) to a multiple of 16.\n"
+"The maximum message size is currently 16 KB.\n"
+"Therefore the maximum data size is currently 16 KB - 6, or 16378 bytes.\n"
+"The minimum data size is 1."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:59
+msgid "Time Sync Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:60
+msgid ""
+"One special case is a metadata message where the sizeof(data) is 0.  In\n"
+"that case, the unencrypted message is encoded as:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:71
+msgid ""
+"Total length: 16 bytes. The time sync message is sent at approximately 15"
+" minute intervals.\n"
+"The message is encrypted just as standard messages are."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:77
+msgid "Checksums"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:78
+#, python-format
+msgid ""
+"The standard and time sync messages use the Adler-32 checksum\n"
+"as defined in the ZLIB Specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:84
+msgid "Establishment Sequence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:85
+msgid ""
+"In the establish state, there is a 4-phase message sequence to exchange "
+"DH keys and signatures.\n"
+"In the first two messages there is a 2048-bit Diffie Hellman exchange.\n"
+"Then, DSA signatures of the critical data are exchanged to confirm the "
+"connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:99
+msgid "Legend:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:100
+msgid "256 byte DH public keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:104
+msgid "timestamps (4 bytes, seconds since epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:105
+msgid "32 byte Session key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:106
+msgid "2 byte size of Alice identity to follow"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:109
+msgid "DH Key Exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:110
+#, python-format
+msgid ""
+"The initial 2048-bit DH key exchange\n"
+"uses the same shared prime (p) and generator (g) as that used for I2P's\n"
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:116
+msgid ""
+"The DH key exchange consists of a number of steps, displayed below.\n"
+"The mapping between these steps and the messages sent between I2P "
+"routers,\n"
+"is marked in bold."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:122
+msgid ""
+"Alice generates a secret integer x. She then calculates X = g^x mod"
+" p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:123
+msgid "Alice sends X to Bob (Message 1)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:124
+msgid ""
+"Bob generates a secret integer y. He then calculates Y = g^y mod "
+"p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:125
+msgid "Bob sends Y to Alice.(Message 2)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:126
+msgid "Alice can now compute sessionKey = Y^x mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:127
+msgid "Bob can now compute sessionKey = X^y mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:128
+msgid ""
+"Both Alice and Bob now have a shared key sessionKey = g^(x*y) mod "
+"p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:130
+#, python-format
+msgid ""
+"The sessionKey is then used to exchange identities in Message 3 "
+"and Message 4.\n"
+"The exponent (x and y) length for the DH exchange is documented on the\n"
+"cryptography page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:136
+msgid "Message 1 (Session Request)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:137
+#, python-format
+msgid ""
+"This is the DH request. Alice already has Bob's\n"
+"Router "
+"Identity,\n"
+"IP address, and port, as contained in his\n"
+"Router Info,\n"
+"which was published to the\n"
+"network database.\n"
+"Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:150
+#: i2p2www/pages/site/docs/transport/ntcp.html:193
+#: i2p2www/pages/site/docs/transport/ntcp.html:273
+#: i2p2www/pages/site/docs/transport/ntcp.html:356
+msgid "Size:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:152
+msgid "Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:170
+msgid "256 byte X from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:172
+#, python-format
+msgid ""
+"SHA256 Hash(X) xored with SHA256 Hash(Bob's Router Identity)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:179
+#: i2p2www/pages/site/docs/transport/ntcp.html:260
+#: i2p2www/pages/site/docs/transport/ntcp.html:337
+msgid "Notes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:180
+msgid ""
+"Bob verifies HXxorHI using his own router hash. If it does not verify,\n"
+"Alice has contacted the wrong router, and Bob drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:186
+msgid "Message 2 (Session Created)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:187
+msgid "This is the DH reply. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:195
+#: i2p2www/pages/site/docs/transport/ntcp.html:275
+#: i2p2www/pages/site/docs/transport/ntcp.html:358
+msgid "Unencrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:217
+#: i2p2www/pages/site/docs/transport/ntcp.html:251
+msgid "256 byte Y from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:219
+msgid "SHA256 Hash(X concatenated with Y)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:222
+#: i2p2www/pages/site/docs/transport/ntcp.html:307
+msgid "4 byte timestamp (seconds since the epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:224
+msgid "12 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:229
+#: i2p2www/pages/site/docs/transport/ntcp.html:319
+#: i2p2www/pages/site/docs/transport/ntcp.html:386
+msgid "Encrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:253
+#, python-format
+msgid ""
+"48 bytes AES encrypted using the DH "
+"session key and\n"
+"                  the last 16 bytes of Y as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:261
+msgid ""
+"Alice may drop the connection if the clock skew with Bob is too high as "
+"calculated using tsB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:266
+msgid "Message 3 (Session Confirm A)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:267
+msgid ""
+"This contains Alice's router identity, and a DSA signature of the "
+"critical data. Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:301
+msgid "2 byte size of Alice's router identity to follow (should always be 387)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:303
+#, python-format
+msgid ""
+"Alice's 387 byte Router Identity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:309
+msgid "15 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:311
+#, python-format
+msgid ""
+"the 40 byte DSA "
+"signature of the following concatenated data:\n"
+"             X, Y, Bob's Router Identity, "
+"tsA, tsB.\n"
+"             Alice signs it with the private signing "
+"key associated with the public signing "
+"key in her Router Identity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:329
+#, python-format
+msgid ""
+"448 bytes AES encrypted using the DH"
+" session key and\n"
+"                  the last 16 bytes of HXxorHI (i.e., the last 16 bytes "
+"of message #1) as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:339
+msgid "Bob verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:342
+msgid ""
+"Bob may drop the connection if the clock skew with Alice is too high as "
+"calculated using tsA."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:349
+msgid "Message 4 (Session Confirm B)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:350
+msgid "This is a DSA signature of the critical data. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:375
+#, python-format
+msgid ""
+"the 40 byte DSA "
+"signature of the following concatenated data:\n"
+"             X, Y, Alice's Router Identity, "
+"tsA, tsB.\n"
+"             Bob signs it with the private signing "
+"key associated with the public signing "
+"key in his Router Identity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:381
+msgid "8 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:396
+#, python-format
+msgid ""
+"48 bytes AES encrypted using the DH "
+"session key and\n"
+"                  the last 16 bytes of the encrypted contents of message "
+"#2 as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:404
+msgid "Alice verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:411
+msgid "After Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:412
+msgid ""
+"The connection is established, and standard or time sync messages may be "
+"exchanged.\n"
+"All subsequent messages are AES encrypted using the negotiated DH session"
+" key.\n"
+"Alice will use the last 16 bytes of the encrypted contents of message #3 "
+"as the next IV.\n"
+"Bob will use the last 16 bytes of the encrypted contents of message #4 as"
+" the next IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:421
+msgid "Check Connection Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:422
+msgid ""
+"Alternately, when Bob receives a connection, it could be a\n"
+"check connection (perhaps prompted by Bob asking for someone\n"
+"to verify his listener).\n"
+"Check Connection is not currently used.\n"
+"However, for the record, check connections are formatted as follows.\n"
+"A check info connection will receive 256 bytes containing:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:431
+msgid "32 bytes of uninterpreted, ignored data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:432
+msgid "1 byte size"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:433
+msgid ""
+"that many bytes making up the local router's IP address (as reached by "
+"the remote side)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:434
+msgid "2 byte port number that the local router was reached on"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:435
+msgid ""
+"4 byte i2p network time as known by the remote side (seconds since the "
+"epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:436
+msgid "uninterpreted padding data, up to byte 223"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:437
+msgid ""
+"xor of the local router's identity hash and the SHA256 of bytes 32 "
+"through bytes 223"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:441
+msgid "Discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:442
+#, python-format
+msgid "Now on the NTCP Discussion Page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:448
+msgid "The maximum message size should be increased to approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:452
+msgid ""
+"A set of fixed packet sizes may be appropriate to further hide the data \n"
+"fragmentation to external adversaries, but the tunnel, garlic, and end to"
+" \n"
+"end padding should be sufficient for most needs until then.\n"
+"However, there is currently no provision for padding beyond the next "
+"16-byte boundary,\n"
+"to create a limited number of message sizes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:460
+msgid ""
+"Memory utilization (including that of the kernel) for NTCP should be "
+"compared to that for SSU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:464
+msgid ""
+"Can the establishment messages be randomly padded somehow, to frustrate\n"
+"identification of I2P traffic based on initial packet sizes?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:469
+msgid "Review and possibly disable 'check connection'"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:2
+msgid "SSU Transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:6
+msgid "Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:9
+#, python-format
+msgid ""
+"SSU (also called \"UDP\" in much of the I2P documentation and user "
+"interfaces)\n"
+"is one of two transports currently "
+"implemented in I2P.\n"
+"The other is NTCP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:15
+msgid ""
+"SSU is the newer of the two transports,\n"
+"introduced in I2P release 0.6.\n"
+"In a standard I2P installation, the router uses both NTCP and SSU for "
+"outbound connections.\n"
+"SSU-over-IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:22
+msgid "SSU Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:24
+msgid ""
+"Like the NTCP transport, SSU provides reliable, encrypted, connection-"
+"oriented, point-to-point data transport.\n"
+"Unique to SSU, it also provides IP detection and NAT traversal services, "
+"including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:30
+msgid ""
+"Cooperative NAT/Firewall traversal using introducers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:31
+msgid ""
+"Local IP detection by inspection of incoming packets and peer testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:32
+msgid ""
+"Communication of firewall status and local IP, and changes to either to "
+"NTCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:37
+msgid "Protocol Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:39
+msgid "Congestion control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:41
+msgid ""
+"SSU's need for only semireliable delivery, TCP-friendly operation,\n"
+"and the capacity for high throughput allows a great deal of latitude in\n"
+"congestion control.  The congestion control algorithm outlined below is\n"
+"meant to be both efficient in bandwidth as well as simple to implement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:48
+msgid ""
+"Packets are scheduled according to the router's policy, taking care\n"
+"not to exceed the router's outbound capacity or to exceed the measured \n"
+"capacity of the remote peer.  The measured capacity operates along the\n"
+"lines of TCP's slow start and congestion avoidance, with additive "
+"increases\n"
+"to the sending capacity and multiplicative decreases in face of "
+"congestion.\n"
+"Unlike for TCP, routers may give up on some messages after\n"
+"a given period or number of retransmissions while continuing to transmit"
+" \n"
+"other messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:59
+msgid ""
+"The congestion detection techniques vary from TCP as well, since each \n"
+"message has its own unique and nonsequential identifier, and each message"
+"\n"
+"has a limited size - at most, 32KB.  To efficiently transmit this "
+"feedback\n"
+"to the sender, the receiver periodically includes a list of fully ACKed \n"
+"message identifiers and may also include bitfields for partially received"
+"\n"
+"messages, where each bit represents the reception of a fragment.  If \n"
+"duplicate fragments arrive, the message should be ACKed again, or if the\n"
+"message has still not been fully received, the bitfield should be \n"
+"retransmitted with any new updates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:71
+msgid ""
+"The current implementation does not pad the packets to\n"
+"any particular size, but instead just places a single message fragment "
+"into\n"
+"a packet and sends it off (careful not to exceed the MTU)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:78
+msgid ""
+"As of router version 0.8.12,\n"
+"two MTU values are used for IPv4: 620 and 1484.\n"
+"The MTU value is adjusted based on the percentage of packets that are "
+"retransmitted."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:84
+msgid ""
+"For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
+"the payload portion after the 28-byte IP/UDP header is a multiple of\n"
+"16 bytes, for encryption purposes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:90
+msgid ""
+"For the small MTU value, it is desirable to pack a 2646-byte\n"
+"Variable Tunnel Build Message efficiently into multiple packets;\n"
+"with a 620-byte MTU, it fits into 5 packets with nicely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:96
+msgid ""
+"Based on measurements, 1492 fits nearly all reasonably small I2NP "
+"messages\n"
+"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going "
+"to fit\n"
+"into a live network MTU anyway)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:102
+msgid ""
+"The MTU values were 608 and 1492 for releases 0.8.9 - 0.8.11.\n"
+"The large MTU was 1350 prior to release 0.8.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:107
+msgid ""
+"The maximum receive packet size\n"
+"is 1571 bytes as of release 0.8.12.\n"
+"For releases 0.8.9 - 0.8.11 it was 1535 bytes.\n"
+"Prior to release 0.8.9 it was 2048 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:114
+msgid ""
+"As of release 0.9.2, if a router's network interface MTU is less than "
+"1484,\n"
+"it will publish that in the network database, and other routers should\n"
+"honor that when a connection is established."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:120
+msgid ""
+"For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes,\n"
+"so we use an MTU where (MTN % 16 == 0), which is true for 1280.\n"
+"The maximum IPv6 MTU is 1472."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:126
+msgid "Message Size Limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:127
+msgid ""
+"While the maximum message size is nominally 32KB, the practical\n"
+"limit differs. The protocol limits the number of fragments to 7 bits, or "
+"128.\n"
+"The current implementation, however, limits each message to a maximum of "
+"64 fragments,\n"
+"which is sufficient for 64 * 534 = 33.3 KB when using the 608 MTU.\n"
+"Due to overhead for bundled LeaseSets and session keys, the practical "
+"limit\n"
+"at the application level is about 6KB lower, or about 26KB.\n"
+"Further work is necessary to raise the UDP transport limit above 32KB.\n"
+"For connections using the larger MTU, larger messages are possible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:138
+msgid "Keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:140
+msgid ""
+"All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n"
+"The MAC and session keys are negotiated as part of the DH exchange, used\n"
+"for the HMAC and encryption, respectively.  Prior to the DH exchange, \n"
+"the publicly knowable introKey is used for the MAC and encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:147
+msgid ""
+"When using the introKey, both the initial message and any subsequent\n"
+"reply use the introKey of the responder (Bob) - the responder does \n"
+"not need to know the introKey of the requester (Alice).  The DSA \n"
+"signing key used by Bob should already be known to Alice when she \n"
+"contacts him, though Alice's DSA key may not already be known by \n"
+"Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:156
+msgid ""
+"Upon receiving a message, the receiver checks the \"from\" IP address and"
+" port\n"
+"with all established sessions - if there are matches,\n"
+"that session's MAC keys are tested in the HMAC.  If none\n"
+"of those verify or if there are no matching IP addresses, the \n"
+"receiver tries their introKey in the MAC.  If that does not verify,\n"
+"the packet is dropped.  If it does verify, it is interpreted \n"
+"according to the message type, though if the receiver is overloaded,\n"
+"it may be dropped anyway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:167
+msgid ""
+"If Alice and Bob have an established session, but Alice loses the \n"
+"keys for some reason and she wants to contact Bob, she may at any \n"
+"time simply establish a new session through the SessionRequest and\n"
+"related messages.  If Bob has lost the key but Alice does not know\n"
+"that, she will first attempt to prod him to reply, by sending a \n"
+"DataMessage with the wantReply flag set, and if Bob continually \n"
+"fails to reply, she will assume the key is lost and reestablish a \n"
+"new one."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:178
+#, python-format
+msgid ""
+"For the DH key agreement,\n"
+"RFC3526 2048bit\n"
+"MODP group (#14) is used:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:188
+#, python-format
+msgid ""
+"These are the same p and g used for I2P's\n"
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:193
+msgid "Replay prevention"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:195
+msgid ""
+"Replay prevention at the SSU layer occurs by rejecting packets \n"
+"with exceedingly old timestamps or those which reuse an IV.  To\n"
+"detect duplicate IVs, a sequence of Bloom filters are employed to\n"
+"\"decay\" periodically so that only recently added IVs are detected."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:202
+msgid ""
+"The messageIds used in DataMessages are defined at layers above\n"
+"the SSU transport and are passed through transparently.  These IDs\n"
+"are not in any particular order - in fact, they are likely to be\n"
+"entirely random.  The SSU layer makes no attempt at messageId \n"
+"replay prevention - higher layers should take that into account."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:210
+msgid "Addressing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:212
+msgid ""
+"To contact an SSU peer, one of two sets of information is necessary:\n"
+"a direct address, for when the peer is publicly reachable, or an\n"
+"indirect address, for using a third party to introduce the peer.\n"
+"There is no restriction on the number of addresses a peer may have."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:224
+msgid ""
+"Each of the addresses may also expose a series of options - special\n"
+"capabilities of that particular peer.  For a list of available\n"
+"capabilities, see below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:230
+#, python-format
+msgid ""
+"The addresses, options, and capabilities are published in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:235
+msgid "Direct Session Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:236
+msgid ""
+"Direct session establishment is used when no third party is required for "
+"NAT traversal.\n"
+"The message sequence is as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:241
+msgid "Connection establishment (direct)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:242
+msgid ""
+"Alice connects directly to Bob.\n"
+"IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:257
+#, python-format
+msgid ""
+"After the SessionConfirmed message is received, Bob sends a small\n"
+"DeliveryStatus message\n"
+"as a confirmation.\n"
+"In this message, the 4-byte message ID is set to a random number, and the"
+"\n"
+"8-byte \"arrival time\" is set to the current network-wide ID, which is 2"
+"\n"
+"(i.e. 0x0000000000000002)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:266
+#, python-format
+msgid ""
+"After the status message is sent, the peers exchange\n"
+"DatabaseStore messages\n"
+"containing their\n"
+"RouterInfos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:274
+msgid ""
+"It does not appear that the type of the status message or its contents "
+"matters.\n"
+"It was originally added becasue the DatabaseStore message was delayed\n"
+"several seconds; since the store is now sent immediately, perhaps\n"
+"the status message can be eliminated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:283
+msgid ""
+"Introduction keys are delivered through an external channel \n"
+"(the network database, where they are identical to the router Hash for "
+"now)\n"
+"and must be used when establishing a session key.  For the indirect\n"
+"address, the peer must first contact the relayhost and ask them for\n"
+"an introduction to the peer known at that relayhost under the given\n"
+"tag.  If possible, the relayhost sends a message to the addressed\n"
+"peer telling them to contact the requesting peer, and also gives \n"
+"the requesting peer the IP and port on which the addressed peer is\n"
+"located.  In addition, the peer establishing the connection must \n"
+"already know the public keys of the peer they are connecting to (but\n"
+"not necessary to any intermediary relay peer)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:297
+msgid ""
+"Indirect session establishment by means of a third party introduction\n"
+"is necessary for efficient NAT traversal.  Charlie, a router behind a\n"
+"NAT or firewall which does not allow unsolicited inbound UDP packets,\n"
+"first contacts a few peers, choosing some to serve as introducers.  Each\n"
+"of these peers (Bob, Bill, Betty, etc) provide Charlie with an "
+"introduction\n"
+"tag - a 4 byte random number - which he then makes available to the "
+"public\n"
+"as methods of contacting him.  Alice, a router who has Charlie's "
+"published\n"
+"contact methods, first sends a RelayRequest packet to one or more of the"
+" \n"
+"introducers, asking each to introduce her to Charlie (offering the \n"
+"introduction tag to identify Charlie).  Bob then forwards a RelayIntro\n"
+"packet to Charlie including Alice's public IP and port number, then sends"
+"\n"
+"Alice back a RelayResponse packet containing Charlie's public IP and port"
+"\n"
+"number.  When Charlie receives the RelayIntro packet, he sends off a "
+"small\n"
+"random packet to Alice's IP and port (poking a hole in his NAT/firewall),"
+"\n"
+"and when Alice receives Bob's RelayResponse packet, she begins a new \n"
+"full direction session establishment with the specified IP and port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:324
+msgid "Connection establishment (indirect using an introducer)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:326
+msgid "Alice first connects to introducer Bob, who relays the request to Charlie."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:344
+msgid ""
+"After the hole punch, the session is established between Alice and "
+"Charlie as in a direct establishment."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:356
+msgid "Peer testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:358
+msgid ""
+"The automation of collaborative reachability testing for peers is\n"
+"enabled by a sequence of PeerTest messages.  With its proper \n"
+"execution, a peer will be able to determine their own reachability\n"
+"and may update its behavior accordingly.  The testing process is \n"
+"quite simple:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:377
+msgid ""
+"Each of the PeerTest messages carry a nonce identifying the\n"
+"test series itself, as initialized by Alice.  If Alice doesn't \n"
+"get a particular message that she expects, she will retransmit\n"
+"accordingly, and based upon the data received or the messages\n"
+"missing, she will know her reachability.  The various end states\n"
+"that may be reached are as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:387
+msgid ""
+"If she doesn't receive a response from Bob, she will retransmit\n"
+"up to a certain number of times, but if no response ever arrives,\n"
+"she will know that her firewall or NAT is somehow misconfigured, \n"
+"rejecting all inbound UDP packets even in direct response to an\n"
+"outbound packet.  Alternately, Bob may be down or unable to get \n"
+"Charlie to reply."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:396
+msgid ""
+"If Alice doesn't receive a PeerTest message with the \n"
+"expected nonce from a third party (Charlie), she will retransmit\n"
+"her initial request to Bob up to a certain number of times, even\n"
+"if she has received Bob's reply already.  If Charlie's first message \n"
+"still doesn't get through but Bob's does, she knows that she is\n"
+"behind a NAT or firewall that is rejecting unsolicited connection\n"
+"attempts and that port forwarding is not operating properly (the\n"
+"IP and port that Bob offered up should be forwarded)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:407
+msgid ""
+"If Alice receives Bob's PeerTest message and both of Charlie's\n"
+"PeerTest messages but the enclosed IP and port numbers in Bob's \n"
+"and Charlie's second messages don't match, she knows that she is \n"
+"behind a symmetric NAT, rewriting all of her outbound packets with\n"
+"different 'from' ports for each peer contacted.  She will need to\n"
+"explicitly forward a port and always have that port exposed for \n"
+"remote connectivity, ignoring further port discovery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:417
+msgid ""
+"If Alice receives Charlie's first message but not his second,\n"
+"she will retransmit her PeerTest message to Charlie up to a \n"
+"certain number of times, but if no response is received she knows\n"
+"that Charlie is either confused or no longer online."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:425
+msgid ""
+"Alice should choose Bob arbitrarily from known peers who seem\n"
+"to be capable of participating in peer tests.  Bob in turn should\n"
+"choose Charlie arbitrarily from peers that he knows who seem to be\n"
+"capable of participating in peer tests and who are on a different\n"
+"IP from both Bob and Alice.  If the first error condition occurs\n"
+"(Alice doesn't get PeerTest messages from Bob), Alice may decide\n"
+"to designate a new peer as Bob and try again with a different nonce."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:435
+msgid ""
+"Alice's introduction key is included in all of the PeerTest \n"
+"messages so that she doesn't need to already have an established\n"
+"session with Bob and so that Charlie can contact her without knowing\n"
+"any additional information.  Alice may go on to establish a session\n"
+"with either Bob or Charlie, but it is not required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:453
+msgid "Transmission window, ACKs and Retransmissions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:454
+#, python-format
+msgid ""
+"The DATA message may contain ACKs of full messages and\n"
+"partial ACKs of individual fragments of a message. See\n"
+"the data message section of\n"
+"the protocol specification page\n"
+"for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:462
+#, python-format
+msgid ""
+"The details of windowing, ACK, and retransmission strategies are not "
+"specified\n"
+"here. See the Java code for the current implementation.\n"
+"During the establishment phase, and for peer testing, routers\n"
+"should implement exponential backoff for retransmission.\n"
+"For an established connection, routers should implement\n"
+"an adjustable transmission window, RTT estimate and timeout, similar to "
+"TCP\n"
+"or streaming.\n"
+"See the code for initial, min and max parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:474
+msgid "Security"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:475
+msgid ""
+"UDP source addresses may, of course, be spoofed.\n"
+"Additionally, the IPs and ports contained inside specific\n"
+"SSU messages (RelayRequest, RelayResponse, RelayIntro, PeerTest)\n"
+"may not be legitimate.\n"
+"Also, certain actions and responses may need to be rate-limited."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:483
+msgid ""
+"The details of validation are not specified\n"
+"here. Implementers should add defenses where appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:489
+msgid "Peer capabilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:493
+msgid ""
+"If the peer address contains the 'B' capability, that means \n"
+"they are willing and able to participate in peer tests as\n"
+"a 'Bob' or 'Charlie'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:499
+msgid ""
+"If the peer address contains the 'C' capability, that means\n"
+"they are willing and able to serve as an introducer - serving\n"
+"as a Bob for an otherwise unreachable Alice."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:508
+msgid ""
+"Analysis of current SSU performance, including assessment of window size "
+"adjustment\n"
+"and other parameters, and adjustment of the protocol implementation to "
+"improve\n"
+"performance, is a topic for future work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:514
+msgid ""
+"The current implementation repeatedly sends acknowledgments for the same "
+"packets,\n"
+"which unnecessarily increases overhead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:519
+msgid ""
+"The default small MTU value of 620 should be analyzed and possibly "
+"increased.\n"
+"The current MTU adjustment strategy should be evaluated.\n"
+"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? "
+"Probably not."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:525
+msgid "The protocol should be extended to exchange MTUs during the setup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:529
+msgid "Rekeying is currently unimplemented and may never be."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:533
+msgid ""
+"The potential use of the 'challenge' fields in RelayIntro and "
+"RelayResponse,\n"
+"and use of the padding field in SessionRequest and SessionCreated, is "
+"undocumented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:538
+msgid ""
+"Instead of a single fragment per packet, a more efficient\n"
+"strategy may be to bundle multiple message fragments into the same "
+"packet,\n"
+"so long as it doesn't exceed the MTU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:544
+msgid ""
+"A set of fixed packet sizes may be appropriate to further hide the data \n"
+"fragmentation to external adversaries, but the tunnel, garlic, and end to"
+" \n"
+"end padding should be sufficient for most needs until then."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:550
+msgid ""
+"Why are introduction keys the same as the router hash, should it be "
+"changed, would there be any benefit?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:554
+msgid "Capacities appear to be unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:558
+msgid ""
+"Signed-on times in SessionCreated and SessionConfirmed appear to be "
+"unused or unverified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:563
+msgid "Implementation Diagram"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:564
+msgid ""
+"This diagram\n"
+"should accurately reflect the current implementation, however there may "
+"be small differences."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:572
+msgid "Now on the SSU specification page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:2
+msgid "Tunnel Implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:3
+msgid "October 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:7
+msgid "This page documents the current tunnel implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:9
+msgid "Tunnel overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:11
+msgid ""
+"Within I2P, messages are passed in one direction through a virtual\n"
+"tunnel of peers, using whatever means are available to pass the \n"
+"message on to the next hop.  Messages arrive at the tunnel's \n"
+"            gateway            , get bundled up and/or fragmented into fixed-size tunnel "
+"messages, \n"
+"and are forwarded on to the next hop in the tunnel, which processes and "
+"verifies\n"
+"the validity of the message and sends it on to the next hop, and so on, "
+"until\n"
+"it reaches the tunnel endpoint.  That endpoint takes the messages\n"
+"bundled up by the gateway and forwards them as instructed - either\n"
+"to another router, to another tunnel on another router, or locally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:23
+msgid ""
+"Tunnels all work the same, but can be segmented into two different\n"
+"groups - inbound tunnels and outbound tunnels.  The inbound tunnels\n"
+"have an untrusted gateway which passes messages down towards the \n"
+"tunnel creator, which serves as the tunnel endpoint.  For outbound \n"
+"tunnels, the tunnel creator serves as the gateway, passing messages\n"
+"out to the remote endpoint."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:32
+msgid ""
+"The tunnel's creator selects exactly which peers will participate\n"
+"in the tunnel, and provides each with the necessary configuration\n"
+"data.  They may have any number of hops.\n"
+"It is the intent to make\n"
+"it hard for either participants or third parties to determine the length "
+"of \n"
+"a tunnel, or even for colluding participants to determine whether they "
+"are a\n"
+"part of the same tunnel at all (barring the situation where colluding "
+"peers are\n"
+"next to each other in the tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:43
+msgid ""
+"In practice, a series of tunnel pools are used for different\n"
+"purposes - each local client destination has its own set of inbound\n"
+"tunnels and outbound tunnels, configured to meet its anonymity and\n"
+"performance needs.  In addition, the router itself maintains a series\n"
+"of pools for participating in the network database and for managing\n"
+"the tunnels themselves."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:52
+msgid ""
+"I2P is an inherently packet switched network, even with these \n"
+"tunnels, allowing it to take advantage of multiple tunnels running \n"
+"in parallel, increasing resilience and balancing load.  Outside of\n"
+"the core I2P layer, there is an optional end to end streaming library \n"
+"available for client applications, exposing TCP-esque operation,\n"
+"including message reordering, retransmission, congestion control, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:61
+#, python-format
+msgid ""
+"An overview of I2P tunnel terminology is\n"
+"on the tunnel overview page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:66
+msgid "Tunnel Operation (Message Processing)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:69
+#, python-format
+msgid ""
+"After a tunnel is built, I2NP messages are "
+"processed and passed through it.\n"
+"Tunnel operation has four distinct processes, taken on by various \n"
+"peers in the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:75
+msgid ""
+"First, the tunnel gateway accumulates a number\n"
+"of I2NP messages and preprocesses them into tunnel messages for\n"
+"delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:80
+msgid ""
+"Next, that gateway encrypts that preprocessed data, then\n"
+"forwards it to the first hop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:84
+msgid ""
+"That peer, and subsequent tunnel \n"
+"participants, unwrap a layer of the encryption, verifying that it isn't\n"
+"a duplicate, then forward it on to the next peer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:89
+msgid ""
+"Eventually, the tunnel messages arrive at the endpoint where the I2NP "
+"messages\n"
+"originally bundled by the gateway are reassembled and forwarded on as \n"
+"requested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:96
+msgid ""
+"Intermediate tunnel participants do not know whether they are in an\n"
+"inbound or an outbound tunnel; they always \"encrypt\" for the next hop.\n"
+"Therefore, we take advantage of symmetric AES encryption\n"
+"to \"decrypt\" at the outbound tunnel gateway,\n"
+"so that the plaintext is revealed at the outbound endpoint."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:110
+msgid "Role"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:111
+msgid "Preprocessing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:112
+msgid "Encryption Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:113
+msgid "Postprocessing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:117
+msgid "Outbound Gateway (Creator)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:118
+#: i2p2www/pages/site/docs/tunnels/implementation.html:141
+msgid "Fragment, Batch, and Pad"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:119
+msgid "Iteratively encrypt (using decryption operations)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:120
+#: i2p2www/pages/site/docs/tunnels/implementation.html:127
+#: i2p2www/pages/site/docs/tunnels/implementation.html:143
+#: i2p2www/pages/site/docs/tunnels/implementation.html:150
+msgid "Forward to next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:124
+#: i2p2www/pages/site/docs/tunnels/implementation.html:147
+msgid "Participant"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:126
+msgid "Decrypt (using an encryption operation)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:133
+msgid "Decrypt (using an encryption operation) to reveal plaintext tunnel message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:134
+msgid "Reassemble Fragments, Forward as instructed to Inbound Gateway or Router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:142
+#: i2p2www/pages/site/docs/tunnels/implementation.html:149
+msgid "Encrypt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:154
+msgid "Inbound Endpoint (Creator)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:156
+msgid "Iteratively decrypt to reveal plaintext tunnel message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:157
+msgid "Reassemble Fragments, Receive data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:163
+msgid "Gateway Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:164
+msgid "Message Preprocessing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:166
+#, python-format
+msgid ""
+"A tunnel gateway's function is to fragment and pack\n"
+"I2NP messages into fixed-size\n"
+"tunnel messages\n"
+"and encrypt the tunnel messages.\n"
+"Tunnel messages contain the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:174
+msgid "A 4 byte Tunnel ID"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:175
+msgid "A 16 byte IV (initialization vector)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:176
+msgid "A checksum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:177
+msgid "Padding, if necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:178
+msgid "One or more { delivery instruction, I2NP message fragment } pairs"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:181
+msgid ""
+"Tunnel IDs are 4 byte numbers used at each hop - participants know what\n"
+"tunnel ID to listen for messages with and what tunnel ID they should be "
+"forwarded\n"
+"on as to the next hop, and each hop chooses the tunnel ID which they "
+"receive messages\n"
+"on.  Tunnels themselves are short-lived (10 minutes).\n"
+"Even if subsequent tunnels are built using the same sequence of \n"
+"peers, each hop's tunnel ID will change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:190
+msgid ""
+"To prevent adversaries from tagging the messages along the path by "
+"adjusting\n"
+"the message size, all tunnel messages are a fixed 1024 bytes in size.  To"
+" accommodate \n"
+"larger I2NP messages as well as to support smaller ones more efficiently,"
+" the\n"
+"gateway splits up the larger I2NP messages into fragments contained "
+"within each\n"
+"tunnel message.  The endpoint will attempt to rebuild the I2NP message "
+"from the\n"
+"fragments for a short period of time, but will discard them as necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:199
+#, python-format
+msgid ""
+"Details are in the\n"
+"tunnel message specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:205
+msgid "Gateway Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:207
+msgid ""
+"After the preprocessing of messages into a padded payload, the gateway "
+"builds\n"
+"a random 16 byte IV value, iteratively encrypting it and the tunnel "
+"message as\n"
+"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel "
+"message} to the next hop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:213
+msgid ""
+"How encryption at the gateway is done depends on whether the tunnel is an"
+"\n"
+"inbound or an outbound tunnel.  For inbound tunnels, they simply select a"
+" random\n"
+"IV, postprocessing and updating it to generate the IV for the gateway and"
+" using \n"
+"that IV along side their own layer key to encrypt the preprocessed data."
+"  For outbound \n"
+"tunnels they must iteratively decrypt the (unencrypted) IV and "
+"preprocessed \n"
+"data with the IV and layer keys for all hops in the tunnel.  The result "
+"of the outbound\n"
+"tunnel encryption is that when each peer encrypts it, the endpoint will "
+"recover \n"
+"the initial preprocessed data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:225
+msgid "Participant Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:227
+msgid ""
+"When a peer receives a tunnel message, it checks that the message came "
+"from\n"
+"the same previous hop as before (initialized when the first message comes"
+" through\n"
+"the tunnel).  If the previous peer is a different router, or if the "
+"message has\n"
+"already been seen, the message is dropped.  The participant then encrypts"
+" the \n"
+"received IV with AES256/ECB using their IV key to determine the current "
+"IV, uses \n"
+"that IV with the participant's layer key to encrypt the data, encrypts "
+"the \n"
+"current IV with AES256/ECB using their IV key again, then forwards the "
+"tuple \n"
+"{nextTunnelId, nextIV, encryptedData} to the next hop.  This double "
+"encryption\n"
+"of the IV (both before and after use) help address a certain class of\n"
+"confirmation attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:240
+msgid ""
+"Duplicate message detection is handled by a decaying Bloom filter on "
+"message\n"
+"IVs.  Each router maintains a single Bloom filter to contain the XOR of "
+"the IV and\n"
+"the first block of the message received for all of the tunnels it is "
+"participating\n"
+"in, modified to drop seen entries after 10-20 minutes (when the tunnels "
+"will have\n"
+"expired).  The size of the bloom filter and the parameters used are "
+"sufficient to\n"
+"more than saturate the router's network connection with a negligible "
+"chance of \n"
+"false positive.  The unique value fed into the Bloom filter is the XOR of"
+" the IV \n"
+"and the first block so as to prevent nonsequential colluding peers in the"
+" tunnel \n"
+"from tagging a message by resending it with the IV and first block "
+"switched."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:253
+msgid "Endpoint Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:255
+msgid ""
+"After receiving and validating a tunnel message at the last hop in the "
+"tunnel,\n"
+"how the endpoint recovers the data encoded by the gateway depends upon "
+"whether \n"
+"the tunnel is an inbound or an outbound tunnel.  For outbound tunnels, "
+"the \n"
+"endpoint encrypts the message with its layer key just like any other "
+"participant, \n"
+"exposing the preprocessed data.  For inbound tunnels, the endpoint is "
+"also the \n"
+"tunnel creator so they can merely iteratively decrypt the IV and message,"
+" using the \n"
+"layer and IV keys of each step in reverse order."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:265
+msgid ""
+"At this point, the tunnel endpoint has the preprocessed data sent by the "
+"gateway,\n"
+"which it may then parse out into the included I2NP messages and forwards "
+"them as\n"
+"requested in their delivery instructions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:272
+msgid "Tunnel Building"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:274
+msgid ""
+"When building a tunnel, the creator must send a request with the "
+"necessary\n"
+"configuration data to each of the hops and wait for all of them to agree "
+"before\n"
+"enabling the tunnel.  The requests are encrypted so that only the peers "
+"who need\n"
+"to know a piece of information (such as the tunnel layer or IV key) has "
+"that\n"
+"data.  In addition, only the tunnel creator will have access to the "
+"peer's\n"
+"reply.  There are three important dimensions to keep in mind when "
+"producing\n"
+"the tunnels: what peers are used (and where), how the requests are sent "
+"(and \n"
+"replies received), and how they are maintained."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:288
+msgid ""
+"Beyond the two types of tunnels - inbound and outbound - there are two "
+"styles\n"
+"of peer selection used for different tunnels - exploratory and client.\n"
+"Exploratory tunnels are used for both network database maintenance and "
+"tunnel\n"
+"maintenance, while client tunnels are used for end to end client messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:296
+msgid "Exploratory tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:298
+msgid ""
+"Exploratory tunnels are built out of a random selection of peers from a "
+"subset\n"
+"of the network.  The particular subset varies on the local router and on "
+"what their\n"
+"tunnel routing needs are.  In general, the exploratory tunnels are built "
+"out of\n"
+"randomly selected peers who are in the peer's \"not failing but active\" "
+"profile\n"
+"category.  The secondary purpose of the tunnels, beyond merely tunnel "
+"routing,\n"
+"is to find underutilized high capacity peers so that they can be promoted"
+" for\n"
+"use in client tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:308
+#, python-format
+msgid ""
+"Exploratory peer selection is discussed further on the\n"
+"Peer Profiling and Selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:314
+msgid "Client tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:316
+msgid ""
+"Client tunnels are built with a more stringent set of requirements - the "
+"local\n"
+"router will select peers out of its \"fast and high capacity\" profile "
+"category so\n"
+"that performance and reliability will meet the needs of the client "
+"application.\n"
+"However, there are several important details beyond that basic selection "
+"that \n"
+"should be adhered to, depending upon the client's anonymity needs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:324
+#, python-format
+msgid ""
+"Client peer selection is discussed further on the\n"
+"Peer Profiling and Selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:329
+msgid "Peer Ordering within Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:331
+#, python-format
+msgid ""
+"Peers are ordered within tunnels to deal with the\n"
+"predecessor attack\n"
+"(2008 update)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:338
+msgid ""
+"To frustrate the predecessor \n"
+"attack, the tunnel selection keeps the peers selected in a strict order -"
+"\n"
+"if A, B, and C are in a tunnel for a particular tunnel pool, the hop "
+"after A is always B, and the hop after\n"
+"B is always C."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:345
+msgid ""
+"Ordering is implemented by generating a random 32-byte key for each\n"
+"tunnel pool at startup.\n"
+"Peers should not be able to guess the ordering, or an attacker could\n"
+"craft two router hashes far apart to maximize the chance of being at both"
+"\n"
+"ends of a tunnel.\n"
+"Peers are sorted by XOR distance of the\n"
+"SHA256 Hash of (the peer's hash concatenated with the random key) from "
+"the random key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:360
+msgid ""
+"Because each tunnel pool uses a different random key, ordering is "
+"consistent\n"
+"within a single pool but not between different pools.\n"
+"New keys are generated at each router restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:367
+msgid "Request delivery"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:369
+#, python-format
+msgid ""
+"A multi-hop tunnel is built using a single build message which is "
+"repeatedly\n"
+"decrypted and forwarded. In the terminology of\n"
+"Hashing it out in Public,\n"
+"this is \"non-interactive\" telescopic tunnel building."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:376
+#, python-format
+msgid ""
+"This tunnel request preparation, delivery, and response method is\n"
+"designed to reduce the number of\n"
+"predecessors exposed, cuts the number of messages transmitted, verifies "
+"proper\n"
+"connectivity, and avoids the message counting attack of traditional "
+"telescopic\n"
+"tunnel creation.\n"
+"(This method, which sends messages to extend a tunnel through the "
+"already-established\n"
+"part of the tunnel, is termed \"interactive\" telescopic tunnel building "
+"in\n"
+"the \"Hashing it out\" paper.)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:387
+#, python-format
+msgid ""
+"The details of tunnel request and response messages, and their "
+"encryption,\n"
+"are specified here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:392
+msgid ""
+"Peers may reject tunnel creation requests for a variety of reasons, "
+"though\n"
+"a series of four increasingly severe rejections are known: probabilistic "
+"rejection\n"
+"(due to approaching the router's capacity, or in response to a flood of "
+"requests), \n"
+"transient overload, bandwidth overload, and critical failure.  When "
+"received, \n"
+"those four are interpreted by the tunnel creator to help adjust their "
+"profile of\n"
+"the router in question."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:401
+#, python-format
+msgid ""
+"For more information on peer profiling, see the\n"
+"Peer Profiling and Selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:407
+msgid "Tunnel Pools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:409
+#, python-format
+msgid ""
+"To allow efficient operation, the router maintains a series of tunnel "
+"pools,\n"
+"each managing a group of tunnels used for a specific purpose with their "
+"own\n"
+"configuration.  When a tunnel is needed for that purpose, the router "
+"selects one\n"
+"out of the appropriate pool at random.  Overall, there are two "
+"exploratory tunnel\n"
+"pools - one inbound and one outbound - each using the router's default "
+"configuration.\n"
+"In addition, there is a pair of pools for each local destination -\n"
+"one inbound and one outbound tunnel pool.  Those pools use the "
+"configuration specified\n"
+"when the local destination connects to the router via I2CP, or the router's defaults if\n"
+"not specified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:421
+#, python-format
+msgid ""
+"Each pool has within its configuration a few key settings, defining how "
+"many\n"
+"tunnels to keep active, how many backup tunnels to maintain in case of "
+"failure,\n"
+"how long the tunnels should be, whether those\n"
+"lengths should be randomized, as \n"
+"well as any of the other settings allowed when configuring individual "
+"tunnels.\n"
+"Configuration options are specified on the I2CP "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:431
+msgid "Tunnel Lengths and Defaults"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:433
+msgid "On the tunnel overview page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:435
+msgid "Anticipatory Build Strategy and Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:437
+msgid ""
+"Tunnel building is expensive, and tunnels expire a fixed time after they "
+"are built.\n"
+"However, when a pool that runs out of tunnels, the Destination is "
+"essentially dead.\n"
+"In addition, tunnel build success rate may vary greatly with both local "
+"and global\n"
+"network conditions.\n"
+"Therefore, it is important to maintain an anticipatory, adaptive build "
+"strategy\n"
+"to ensure that new tunnels are successfully built before they are needed,"
+"\n"
+"without building an excess of tunnels, building them too soon,\n"
+"or consuming too much CPU or bandwidth creating and sending the encrypted"
+" build messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:448
+msgid ""
+"For each tuple {exploratory/client, in/out, length, length variance}\n"
+"the router maintains statistics on the time required for a successful\n"
+"tunnel build.\n"
+"Using these statistics, it calculates how long before a tunnel's "
+"expiration\n"
+"it should start attempting to build a replacement.\n"
+"As the expiration time approaches without a successful replacement,\n"
+"it starts multiple build attempts in parallel, and then\n"
+"will increase the number of parallel attempts if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:459
+msgid ""
+"To cap bandwidth and CPU usage,\n"
+"the router also limits the maximum number of build attempts outstanding\n"
+"across all pools.\n"
+"Critical builds (those for exploratory tunnels, and for pools that have\n"
+"run out of tunnels) are prioritized."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:468
+msgid "Tunnel Message Throttling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:470
+msgid ""
+"Even though the tunnels within I2P bear a resemblance to a circuit "
+"switched\n"
+"network, everything within I2P is strictly message based - tunnels are "
+"merely\n"
+"accounting tricks to help organize the delivery of messages.  No "
+"assumptions are\n"
+"made regarding reliability or ordering of messages, and retransmissions "
+"are left\n"
+"to higher levels (e.g. I2P's client layer streaming library).  This "
+"allows I2P\n"
+"to take advantage of throttling techniques available to both packet "
+"switched and\n"
+"circuit switched networks.  For instance, each router may keep track of "
+"the \n"
+"moving average of how much data each tunnel is using, combine that with "
+"all of \n"
+"the averages used by other tunnels the router is participating in, and be"
+" able\n"
+"to accept or reject additional tunnel participation requests based on its"
+" \n"
+"capacity and utilization.  On the other hand, each router can simply drop"
+" \n"
+"messages that are beyond its capacity, exploiting the research used on "
+"the \n"
+"normal Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:486
+msgid ""
+"In the current implementation, routers implement a\n"
+"weighted random early discard (WRED) strategy.\n"
+"For all participating routers (internal participant, inbound gateway, and"
+" outbound endpoint),\n"
+"the router will start randomly dropping a portion of messages as the\n"
+"bandwidth limits are approached.\n"
+"As traffic gets closer to, or exceeds, the limits, more messages are "
+"dropped.\n"
+"For an internal participant, all messages are fragmented and padded and "
+"therefore are the same size.\n"
+"At the inbound gateway and outbound endpoint, however, the dropping "
+"decision is made\n"
+"on the full (coalesced) message, and the message size is taken into "
+"account.\n"
+"Larger messages are more likely to be dropped.\n"
+"Also, messages are more likely to be dropped at the outbound endpoint "
+"than the inbound gateway,\n"
+"as those messages are not as \"far along\" in their journey and thus the "
+"network cost of\n"
+"dropping those messages is lower."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:504
+msgid "Mixing/batching"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:506
+msgid ""
+"What strategies could be used at the gateway and at each hop for "
+"delaying,\n"
+"reordering, rerouting, or padding messages?  To what extent should this "
+"be done\n"
+"automatically, how much should be configured as a per tunnel or per hop "
+"setting,\n"
+"and how should the tunnel's creator (and in turn, user) control this "
+"operation?\n"
+"All of this is left as unknown, to be worked out for a distant future "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:515
+msgid "Padding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:516
+msgid ""
+"The padding strategies can be used on a variety of levels, addressing the"
+"\n"
+"exposure of message size information to different adversaries.\n"
+"The current fixed tunnel message size is 1024 bytes.  Within this "
+"however, the fragmented\n"
+"messages themselves are not padded by the tunnel at all, though for end "
+"to end \n"
+"messages, they may be padded as part of the garlic wrapping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:526
+msgid ""
+"WRED strategies have a significant impact on end-to-end performance,\n"
+"and prevention of network congestion collapse.\n"
+"The current WRED strategy should be carefully evaluated and improved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/old-implementation.html:2
+msgid "Old Tunnel Implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/old-implementation.html:5
+#, python-format
+msgid ""
+"Note: Obsolete - NOT used!  Replaced in 0.6.1.10 - see here for the current implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:7
+msgid ""
+"This page describes the origins and design of I2P's unidirectional "
+"tunnels.\n"
+"For further infomrmation see:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:13
+msgid "Tunnel overview page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:19
+msgid "Tunnel design discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:21
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:23
+msgid "Meeting 125 (~13:12-13:30)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:28
+msgid "Review"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:30
+msgid ""
+"While we aren't aware of any published research on the advantages of \n"
+"unidirecdtional tunnels,\n"
+"they appear to make it harder to detect a \n"
+"request/response pattern, which is quite possible to detect over a \n"
+"bidirectional tunnel.\n"
+"Several apps and protocols, notably HTTP,\n"
+"do transfer data in such manner. Having the traffic follow the same \n"
+"route to its destination and back could make it easier for an \n"
+"attacker who has only timing and traffic volume data to infer the path a"
+" \n"
+"tunnel is taking.\n"
+"Having the response come back along a different path arguably \n"
+"makes it harder."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:45
+msgid ""
+"When dealing with \n"
+"an internal adversary or most external adversaries, I2P's undirectional "
+"tunnels\n"
+"expose half as much traffic data than would be exposed with bidirectional"
+" circuits\n"
+"by simply looking at the flows themselves - an HTTP request and response "
+"would \n"
+"follow the same path in Tor, while in I2P the packets making up the "
+"request \n"
+"would go out through one or more outbound tunnels and the packets making "
+"up \n"
+"the response would come back through one or more different inbound "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:55
+msgid ""
+"The strategy of using two separate tunnels for inbound and outbound\n"
+"communication is not the only technique available, and it does have "
+"anonymity\n"
+"implications.  On the positive side, by using separate tunnels it lessens"
+" the\n"
+"traffic data exposed for analysis to participants in a tunnel - for "
+"instance,\n"
+"peers in an outbound tunnel from a web browser would only see the traffic"
+" of\n"
+"an HTTP GET, while the peers in an inbound tunnel would see the payload \n"
+"delivered along the tunnel.  With bidirectional tunnels, all participants"
+" would\n"
+"have access to the fact that e.g. 1KB was sent in one direction, then "
+"100KB\n"
+"in the other.  On the negative side, using unidirectional tunnels means "
+"that\n"
+"there are two sets of peers which need to be profiled and accounted for, "
+"and\n"
+"additional care must be taken to address the increased speed of "
+"predecessor\n"
+"attacks.  The tunnel pooling and building process\n"
+"(peer selection and ordering strategies)\n"
+"should minimize the worries of the predecessor attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:73
+msgid "Anonymity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:75
+#, python-format
+msgid ""
+"A recent paper by Hermann and Grothoff\n"
+"declared that I2P's unidirectional tunnels \"seems to be a bad design "
+"decision\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:80
+msgid ""
+"The paper's main point is that\n"
+"deanonymizations on unidirectional tunnels take a longer time, which is "
+"an \n"
+"advantage, but that an attacker can be more certain in the unidirectional"
+" case. \n"
+"Therefore, the paper claims it isn't an advantage at all, but a "
+"disadvantage, at least\n"
+"with long-living eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:88
+msgid ""
+"This conclusion is not fully supported by the paper. Unidirectional "
+"tunnels clearly \n"
+"mitigate other attacks and it's not clear how to trade off the risk of "
+"the \n"
+"attack in the paper\n"
+"with attacks on a bidirectional tunnel architecture."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:95
+msgid ""
+"This conclusion is based on an arbitrary certainty vs. time weighting \n"
+"(tradeoff) that may not be applicable in all cases. For \n"
+"example, somebody could make a list of possible IPs then issue subpoenas "
+"to \n"
+"each. Or the attacker could DDoS each in turn and via a simple \n"
+"intersection attack see if the eepsite goes down or is slowed down. So "
+"close \n"
+"may be good enough, or time may be more important."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:104
+msgid ""
+"The conclusion is based on a specific weighting of the importance of "
+"certainty \n"
+"vs. time, and that weighting may be wrong, and it's definitely debatable,"
+" \n"
+"especially in a real world with subpoenas, search warrants, and other "
+"methods \n"
+"available for final confirmation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:111
+msgid ""
+"A full analysis of the tradeoffs of unidirectional vs. bidirectional \n"
+"tunnels is clearly outside the scope of the paper, and has not been done"
+" \n"
+"elsewhere. For example, how does this attack compare to the numerous "
+"possible \n"
+"timing attacks published about onion-routed networks? Clearly the authors"
+" have not\n"
+"done that analysis, if it's even possible to do it\n"
+"effectively."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:120
+msgid ""
+"Tor uses bidirectional tunnels and has had a lot of academic review. I2P"
+" \n"
+"uses unidirectional tunnels and has had very little review. Does the lack"
+" of a \n"
+"research paper defending unidirectional tunnels mean that it is a poor "
+"design \n"
+"choice, or just that it needs more study? Timing attacks and \n"
+"distributed attacks are difficult to defend against in both I2P and Tor. "
+"The \n"
+"design intent (see references above) was that unidirectional tunnels are "
+"more \n"
+"resistant to timing attacks. However, the paper presents a somewhat "
+"different type of timing \n"
+"attack. Is this attack, innovative as it is, sufficient to label I2P's \n"
+"tunnel architecture (and thus I2P as a whole) a \"bad design\", and by \n"
+"implication clearly inferior to Tor, or is it just a design alternative "
+"that \n"
+"clearly needs further investigation and analysis? There are several other"
+" reasons \n"
+"to consider I2P currently inferior to Tor and other projects (small "
+"network \n"
+"size, lack of funding, lack of review) but is unidirectional tunnels "
+"really a \n"
+"reason?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:137
+msgid ""
+"In summary, \"bad design decision\" is apparently (since the paper does\n"
+"not label bidirectional tunnels \"bad\") shorthand for \"unidirectional \n"
+"tunnels are unequivocally inferior to bidirectional tunnels\", yet this \n"
+"conclusion is not supported by the paper."
+msgstr ""
+
diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po b/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po
new file mode 100644
index 00000000..4f82af13
--- /dev/null
+++ b/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po
@@ -0,0 +1,4091 @@
+# 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-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-11-24 17:31+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/get-involved/donate.html:2
+#: i2p2www/pages/site/get-involved/index.html:77
+msgid "Donate"
+msgstr "Faça uma doação"
+
+#: i2p2www/pages/site/get-involved/donate.html:4
+msgid ""
+"Thank you for your interest in contributing to I2P!\n"
+"The details of how you\n"
+"can make your contribution are provided below."
+msgstr ""
+"Obrigado pela disposição em contribuir com a I2P! Os detalhes de como "
+"fazer uma doação são fornecidos abaixo."
+
+#: i2p2www/pages/site/get-involved/donate.html:11
+#: i2p2www/pages/site/get-involved/donate.html:27
+#, python-format
+msgid ""
+"As of %(date)s, eche|on has been running a\n"
+"%(cointype)s account for the I2P project.\n"
+"If you'd like to donate using %(cointype)s, just transfer your\n"
+"desired amount of coins to the account %(account)s\n"
+"and leave eche|on a note if you'd like your donation to be\n"
+"mentioned on the I2P webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:22
+#: i2p2www/pages/site/get-involved/donate.html:38
+msgid "For easy usage, use the QR code below!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:44
+#, python-format
+msgid "You can donate direct via PayPal to the account \"%(account)s\"."
+msgstr ""
+"Você pode fazer uma doação diretamente via PayPal para a conta "
+"\"%(account)s\"."
+
+#: i2p2www/pages/site/get-involved/donate.html:50
+msgid "One time donation:"
+msgstr "Doe uma única vez:"
+
+#: i2p2www/pages/site/get-involved/donate.html:64
+msgid "Donate 10 €/month for 12 months:"
+msgstr "Doe 10 €/mês por 12 meses:"
+
+#: i2p2www/pages/site/get-involved/donate.html:72
+#: i2p2www/pages/site/get-involved/donate.html:84
+#: i2p2www/pages/site/get-involved/donate.html:96
+#: i2p2www/pages/site/get-involved/donate.html:108
+msgid "I2P donation "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:78
+msgid "Donate 20 €/month for 12 months:"
+msgstr "Doe 20 €/mês por 12 meses:"
+
+#: i2p2www/pages/site/get-involved/donate.html:90
+msgid "Donate 30 €/month for 12 months:"
+msgstr "Doe 30 €/mês por 12 meses:"
+
+#: i2p2www/pages/site/get-involved/donate.html:102
+msgid "Donate 50 €/month for 12 months:"
+msgstr "Doe 50 €/mês por 12 meses:"
+
+#: i2p2www/pages/site/get-involved/donate.html:117
+msgid "Flattr this"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:122
+msgid ""
+"If you want to keep more or less anonymous, the option to send money via "
+"mail is also available. But it is less secure\n"
+"as the envelope can be lost on the way to us."
+msgstr ""
+"Se você quer manter-se mais ou menos anônimo, enviar dinheiro via correio"
+" é também uma opção. Mas é menos seguro, haja visto que o envelope pode "
+"ser extraviado."
+
+#: i2p2www/pages/site/get-involved/donate.html:126
+#, python-format
+msgid ""
+"If you'd like to donate via  snail mail, send an email to %(email)s\n"
+" and you'll receive an email with instructions detailing how to proceed."
+msgstr ""
+"Se preferir doar via snail mail, envie um email para %(email)s que lhe enviaremos um email com instruções "
+"detalhando como proceder."
+
+#: i2p2www/pages/site/get-involved/donate.html:131
+#, python-format
+msgid ""
+"In the meantime, feel free to take a look at the generous donations that "
+"have been\n"
+"given in support of the I2P Project at the hall of fame."
+msgstr ""
+"Por ora, sinta-se livre para dar uma olhada nas generosas doações que "
+"foram dadas em apoio ao projeto I2P no salão "
+"da fama."
+
+#: i2p2www/pages/site/get-involved/index.html:2
+msgid "Get Involved!"
+msgstr "Envolva-se!"
+
+#: i2p2www/pages/site/get-involved/index.html:4
+msgid "We need your help!"
+msgstr "Nós precisamos da sua ajuda!"
+
+#: i2p2www/pages/site/get-involved/index.html:5
+msgid ""
+"To get involved, please feel free to join us on the #i2p IRC channel (on\n"
+"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or "
+"irc.postman.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:9
+#, python-format
+msgid ""
+"If you're interested in joining our team, please"
+" get in\n"
+"touch as we're always looking for eager contributors!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:13
+msgid ""
+"We need help in many areas, and you don't need to know Java to "
+"contribute!\n"
+"Here's a list to help you get started!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:18
+msgid "Spread the Word!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:19
+msgid ""
+"Tell people about I2P on forums, blogs, and comments to articles.\n"
+"Fix up the Wikipedia article about I2P in your language.\n"
+"Tell your friends."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:24
+msgid "Testing"
+msgstr "Testando"
+
+#: i2p2www/pages/site/get-involved/index.html:25
+#, python-format
+msgid ""
+"Run the latest builds from monotone\n"
+"and report results on #i2p or as bugs on Trac."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:30
+msgid "Documentation"
+msgstr "Documentação"
+
+#: i2p2www/pages/site/get-involved/index.html:31
+msgid ""
+"Help fix the parts of the website that are outdated or incomplete.\n"
+"Translate pages into other languages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:35
+msgid "Pictures"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:36
+msgid "Make some more pictures, fix the old ones on the website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:39
+msgid "Content"
+msgstr "Conteúdo"
+
+#: i2p2www/pages/site/get-involved/index.html:40
+msgid "Make an eepsite! Add some content! Contribute to the community!"
+msgstr "Faça um eepsite! Adicione algum conteúdo! Contribua com a comunidade!"
+
+#: i2p2www/pages/site/get-involved/index.html:43
+msgid "Services"
+msgstr "Serviços"
+
+#: i2p2www/pages/site/get-involved/index.html:44
+msgid ""
+"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n"
+"a naming service, a search engine, an eepsite monitor... many of these\n"
+"aren't that hard."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:49
+msgid "Applications"
+msgstr "Aplicações"
+
+#: i2p2www/pages/site/get-involved/index.html:50
+#, python-format
+msgid ""
+"Write or port applications for I2P! There's some guidelines and\n"
+"a list of ideas on the applications page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:54
+msgid "Coding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:55
+#, python-format
+msgid ""
+"There's plenty to do if you know Java or are ready to learn.\n"
+"Check for open tickets on Trac\n"
+"or the TODO list on %(zzz)s for\n"
+"some ideas on where to start.\n"
+"See the new developer's guide for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:64
+msgid "Translation"
+msgstr "Tradução"
+
+#: i2p2www/pages/site/get-involved/index.html:65
+#, python-format
+msgid ""
+"Help translate the website and the software into your language.\n"
+"See the new translator's guide for details."
+msgstr ""
+"Ajude-nos a traduzir o website e o software para o seu idioma.\n"
+"Veja o guia para novos tradutores para "
+"detalhes."
+
+#: i2p2www/pages/site/get-involved/index.html:69
+msgid "Analysis"
+msgstr "Análise"
+
+#: i2p2www/pages/site/get-involved/index.html:70
+#, python-format
+msgid ""
+"Study or test the code to look for vulnerabilities.\n"
+"Both anonymity vulnerabilities from the various\n"
+"threat models,\n"
+"and DOS and other weaknesses due to securities holes,\n"
+"need researching."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:2
+msgid "Roadmap"
+msgstr "Plano de ação"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:7
+msgid ""
+"Include some seed data in the distribution so a central reseed location "
+"isn't required?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:10
+#, python-format
+msgid ""
+"Reachability Mapping / handle peers partially reachable / enhanced restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:13
+msgid "Improve help pages and website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:14
+msgid "More translations"
+msgstr "Mais traduções"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:15
+msgid "SSU disconnect message"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:16
+msgid "Iterative floodfill lookups"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:21
+msgid "Full review of anonymity issues and other vulnerabilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:22
+msgid ""
+"Reduce memory usage, remove debugging overhead, make it run better on "
+"slow and embedded machines"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:25
+msgid "Docs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:30
+msgid "Full restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:35
+msgid "Tunnel mixing and padding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:36
+msgid "User defined message delays"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:39
+#, python-format
+msgid ""
+"Please see the TODO list for more detailed info "
+"about some of these tasks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:2
+msgid "To Do List"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:4
+msgid "I2P Project Targets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:5
+#, python-format
+msgid ""
+"Below is a more detailed (yet still incomplete) discussion of the major "
+"areas\n"
+"of future development on the core I2P network, spanning the plausibly "
+"planned\n"
+"releases. This does not include stego transports, porting to wireless "
+"devices,\n"
+"or tools to secure the local machine, nor does it include client "
+"applications\n"
+"that will be essential in I2P's success. There are probably other things "
+"that\n"
+"will come up, especially as I2P gets more peer review, but these are the "
+"main\n"
+"'big things'. See also the roadmap. Want to "
+"help?\n"
+"Get involved!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:54
+msgid "Core functionality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:52
+msgid "link"
+msgstr "linque"
+
+#: i2p2www/pages/site/get-involved/todo.html:18
+#: i2p2www/pages/site/get-involved/todo.html:57
+msgid "NAT/Firewall bridging via 1-hop restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:21
+#: i2p2www/pages/site/get-involved/todo.html:130
+msgid "High degree transport layer with UDP, NBIO, or NIO"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:24
+#: i2p2www/pages/site/get-involved/todo.html:218
+msgid "NetworkDB and profile tuning and ejection policy for large nets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:242
+msgid "Security / anonymity"
+msgstr "Segurança / anonimato"
+
+#: i2p2www/pages/site/get-involved/todo.html:30
+#: i2p2www/pages/site/get-involved/todo.html:245
+msgid ""
+"Per-hop tunnel id & new permuted TunnelVerificationStructure "
+"encryption"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:33
+#: i2p2www/pages/site/get-involved/todo.html:295
+msgid "Strict ordering of participants within tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:36
+msgid "Randomly permuted tunnel lengths"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:39
+#: i2p2www/pages/site/get-involved/todo.html:357
+msgid "Full blown n-hop restricted routes with optional trusted links"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:42
+#: i2p2www/pages/site/get-involved/todo.html:376
+msgid "Hashcash for routerIdentity, destination, and tunnel request"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:45
+#: i2p2www/pages/site/get-involved/todo.html:405
+msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:48
+#: i2p2www/pages/site/get-involved/todo.html:442
+msgid "Stop & go mix w/ garlics & tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:52
+#: i2p2www/pages/site/get-involved/todo.html:456
+msgid "Performance"
+msgstr "Desempenho"
+
+#: i2p2www/pages/site/get-involved/todo.html:62
+msgid "Implemented in I2P 0.6.0.6"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:63
+msgid ""
+"The functionality of allowing routers to fully participate within the "
+"network \n"
+"while behind firewalls and NATs that they do not control requires some "
+"basic \n"
+"restricted route operation (since those peers will not be able to receive"
+" \n"
+"inbound connections). To do this successfully, you consider peers one of"
+" \n"
+"two ways:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:73
+msgid ""
+"Peers who have reachable interfaces - these peers do not need to \n"
+"do anything special"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:77
+msgid ""
+"Peers who do not have reachable interfaces - these peers must "
+"build \n"
+"a tunnel pointing at them where the gateway is one of the peers they have"
+" \n"
+"established a connection with who has both a publicly reachable interface"
+" \n"
+"and who has agreed to serve as their 'introducer'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:85
+msgid ""
+"To do this, peers who have no IP address simply connect to a few peers, \n"
+"build a tunnel through them, and publish a reference to those tunnels "
+"within \n"
+"their RouterInfo structure in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:90
+msgid ""
+"When someone wants to contact any particular router, they first must get"
+" \n"
+"its RouterInfo from the network database, which will tell them whether "
+"they \n"
+"can connect directly (e.g. the peer has a publicly reachable interface) \n"
+"or whether they need to contact them indirectly. Direct connections occur"
+" \n"
+"as normal, while indirect connections are done through one of the "
+"published \n"
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:98
+msgid ""
+"When a router just wants to get a message or two to a specific hidden "
+"peer, \n"
+"they can just use the indirect tunnel for sending the payload. However, \n"
+"if the router wants to talk to the hidden peer often (for instance, as "
+"part \n"
+"of a tunnel), they will send a garlic routed message through the indirect"
+" \n"
+"tunnel to that hidden peer which unwraps to contain a message which "
+"should \n"
+"be sent to the originating router. That hidden peer then establishes an \n"
+"outbound connection to the originating router and from then on, those two"
+" \n"
+"routers can talk to each other directly over that newly established "
+"direct \n"
+"connection."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:109
+msgid ""
+"Of course, that only works if the originating peer can receive "
+"connections \n"
+"(they aren't also hidden). However, if the originating peer is hidden, "
+"they \n"
+"can simply direct the garlic routed message to come back to the "
+"originating \n"
+"peer's inbound tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:115
+msgid ""
+"This is not meant to provide a way for a peer's IP address to be "
+"concealed, \n"
+"merely as a way to let people behind firewalls and NATs fully operate "
+"within \n"
+"the network. Concealing the peer's IP address adds a little more work, as"
+" \n"
+"described below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:121
+msgid ""
+"With this technique, any router can participate as any part of a tunnel."
+" \n"
+"For efficiency purposes, a hidden peer would be a bad choice for an "
+"inbound \n"
+"gateway, and within any given tunnel, two neighboring peers wouldn't want"
+" \n"
+"to be hidden. But that is not technically necessary."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:133
+msgid "Both UDP and NIO have been Implemented in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:134
+msgid ""
+"Standard TCP communication in Java generally requires blocking socket \n"
+"calls, and to keep a blocked socket from hanging the entire system, those"
+" \n"
+"blocking calls are done on their own threads. Our current TCP transport \n"
+"is implemented in a naive fashion - for each peer we are talking to, we \n"
+"have one thread reading and one thread writing. The reader thread simply"
+" \n"
+"loops a bunch of read() calls, building I2NP messages and adding them \n"
+"to our internal inbound message queue, and the writer thread pulls "
+"messages \n"
+"off a per-connection outbound message queue and shoves the data through \n"
+"write() calls."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:145
+msgid ""
+"We do this fairly efficiently, from a CPU perspective - at any time, \n"
+"almost all of these threads are sitting idle, blocked waiting for "
+"something \n"
+"to do. However, each thread consumes real resources (on older Linux "
+"kernels, \n"
+"for instance, each thread would often be implemented as a fork()'ed "
+"process). \n"
+"As the network grows, the number of peers each router will want to talk \n"
+"with will increase (remember, I2P is fully connected, meaning that any \n"
+"given peer should know how to get a message to any other peer, and "
+"restricted \n"
+"route support will probably not significantly reduce the number of "
+"connections \n"
+"necessary). This means that with a 100,000 router network, each router \n"
+"will have up to 199,998 threads just to deal with the TCP connections!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:157
+msgid ""
+"Obviously, that just won't work. We need to use a transport layer that \n"
+"can scale. In Java, we have two main camps:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:162
+#, python-format
+msgid ""
+"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:165
+msgid ""
+"Sending and receiving UDP datagrams is a connectionless operation - if \n"
+"we are communicating with 100,000 peers, we simply stick the UDP packets"
+" \n"
+"in a queue and have a single thread pulling them off the queue and "
+"shoving \n"
+"them out the pipe (and to receive, have a single thread pulling in any \n"
+"UDP packets received and adding them to an inbound queue)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:172
+msgid ""
+"However, moving to UDP means losing the benefits of TCP's ordering, "
+"congestion \n"
+"control, MTU discovery, etc. Implementing that code will take significant"
+" \n"
+"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n"
+"a while ago I was taking some measurements in the simulator and on the \n"
+"live net, and the vast majority of messages transferred would fit easily"
+" \n"
+"within a single unfragmented UDP packet, and the largest of the messages"
+" \n"
+"would fit within 20-30 packets. As mule pointed out, TCP adds a "
+"significant \n"
+"overhead when dealing with so many small packets, as the ACKs are within"
+" \n"
+"an order of magnitude in size. With UDP, we can optimize the transport \n"
+"for both efficiency and resilience by taking into account I2P's "
+"particular \n"
+"needs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:185
+msgid "It will be a lot of work though."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:188
+msgid "NIO or NBIO"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:189
+msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:192
+msgid ""
+"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java"
+" \n"
+"developers to take advantage of the operating system's nonblocking IO \n"
+"capabilities - allowing you to maintain a large number of concurrent IO \n"
+"operations without requiring a separate thread for each. There is much \n"
+"promise with this approach, as we can scalable handle a large number of \n"
+"concurrent connections and we don't have to write a mini-TCP stack with \n"
+"UDP. However, the NIO packages have not proven themselves to be battle-"
+"ready, \n"
+"as the Freenet developer's found. In addition, requiring NIO support "
+"would \n"
+"mean we can't run on any of the open source JVMs like Kaffe, \n"
+"as GNU/Classpath has only "
+"limited \n"
+"support for NIO. (note: this may not be the case anymore, as there \n"
+"has been some progress on Classpath's NIO, but it is an unknown "
+"quantity)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:206
+#, python-format
+msgid ""
+"Another alternative along the same lines is the Non"
+" \n"
+"Blocking I/O package - essentially a cleanroom NIO implementation \n"
+"(written before NIO was around). It works by using some native OS code \n"
+"to do the nonblocking IO, passing off events through Java. It seems to \n"
+"be working with Kaffe, though there doesn't seem to be much development \n"
+"activity on it lately (likely due to 1.4's NIO deployment)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:221
+msgid ""
+"Within the current network database and profile management "
+"implementation, \n"
+"we have taken the liberty of some practical shortcuts. For instance, we \n"
+"don't have the code to drop peer references from the K-buckets, as we \n"
+"don't have enough peers to even plausibly fill any of them, so instead, \n"
+"we just keep the peers in whatever bucket is appropriate. Another example"
+" \n"
+"deals with the peer profiles - the memory required to maintain each "
+"peer's \n"
+"profile is small enough that we can keep thousands of full blown profiles"
+" \n"
+"in memory without problems. While we have the capacity to use trimmed \n"
+"down profiles (which we can maintain 100s of thousands in memory), we \n"
+"don't have any code to deal with moving a profile from a \"minimal "
+"profile\" \n"
+"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to"
+" simply \n"
+"eject a profile altogether. It just wouldn't be practical to write that \n"
+"code yet, since we aren't going to need it for a while."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:236
+msgid ""
+"That said, as the network grows we are going to want to keep these "
+"considerations \n"
+"in mind. We will have some work to do, but we can put it off for later."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:248
+#: i2p2www/pages/site/get-involved/todo.html:332
+#, python-format
+msgid ""
+"Addressed in I2P 0.5 as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:251
+msgid ""
+"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n"
+"going to Dave, then to Charlie, then Bob, and finally Alice "
+"(A<--B<--C<--D<--E), \n"
+"all five of them will know they are participating in tunnel \"123\", as \n"
+"the messages are tagged as such. What we want to do is give each hop "
+"their \n"
+"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n"
+"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n"
+"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n"
+"the tunnel had the same tunnel ID, collusion attacks aren't much work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:261
+msgid ""
+"Adding a unique tunnel ID per hop isn't hard, but by itself, "
+"insufficient. \n"
+"If Dave and Bob are under the control of the same attacker, they wouldn't"
+" \n"
+"be able to tell they are in the same tunnel due to the tunnel ID, but \n"
+"would be able to tell by the message bodies and verification structures \n"
+"by simply comparing them. To prevent that, the tunnel must use layered \n"
+"encryption along the path, both on the payload of the tunneled message \n"
+"and on the verification structure (used to prevent simple tagging "
+"attacks). \n"
+"This requires some simple modifications to the TunnelMessage, as well \n"
+"as the inclusion of per-hop secret keys delivered during tunnel creation"
+" \n"
+"and given to the tunnel's gateway. We must fix a maximum tunnel length \n"
+"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n"
+"of the 16 delivered secret keys, in reverse order, and to encrypt the \n"
+"signature of the hash of the (encrypted) payload at each step. The "
+"gateway \n"
+"then sends that 16-step encrypted message, along with a 16-step and "
+"16-wide \n"
+"encrypted mapping to the first hop, which then decrypts the mapping and \n"
+"the payload with their secret key, looking in the 16-wide mapping for \n"
+"the entry associated with their own hop (keyed by the per-hop tunnel ID)"
+" \n"
+"and verifying the payload by checking it against the associated signed \n"
+"hash."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:282
+msgid ""
+"The tunnel gateway does still have more information than the other peers"
+" \n"
+"in the tunnel, and compromising both the gateway and a tunnel participant"
+" \n"
+"would allow those peers to collude, exposing the fact that they are both"
+" \n"
+"in the same tunnel. In addition, neighboring peers know that they are \n"
+"in the same tunnel anyway, as they know who they send the message to (and"
+" \n"
+"with IP-based transports without restricted routes, they know who they \n"
+"got it from). However, the above two techniques significantly increase \n"
+"the cost of gaining meaningful samples when dealing with longer tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:298
+msgid "Implemented in release 0.6.2"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:301
+#, python-format
+msgid ""
+"As Connelly proposed to deal with the\n"
+"predecessor attack (2008\n"
+"update), keeping the order of peers within our tunnels consistent \n"
+"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n"
+"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n"
+"get to substantially sample Alice's peer selection group. We may even \n"
+"want to explicitly allow Bob to participate in Alice's tunnels in only \n"
+"one way - receiving a message from Dave and sending it to Charlie - and \n"
+"if any of those peers are not available to participate in the tunnel (due"
+" \n"
+"to overload, network disconnection, etc), avoid asking Bob to participate"
+" \n"
+"in any tunnels until they are back online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:316
+msgid ""
+"More analysis is necessary for revising the tunnel creation - at the \n"
+"moment, we simply select and order randomly within the peer's top tier \n"
+"of peers (ones with fast + high capacity)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:321
+msgid ""
+"Adding a strict ordering to peers in a tunnel also improves the anonymity"
+" \n"
+"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway"
+" \n"
+"is always the same would be particularly damning. However, peers with \n"
+"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n"
+"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n"
+"duration) minutes, use a 1-hop tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:338
+msgid ""
+"Without tunnel length permutation, if someone were to somehow detect that"
+" \n"
+"a destination had a particular number of hops, it might be able to use "
+"that \n"
+"information to identify the router the destination is located on, per the"
+" \n"
+"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n"
+"receives a tunnel message from Charlie and forwards it to Alice, Bob "
+"knows \n"
+"Alice is the final router in the tunnel. If Bob were to identify what "
+"destination \n"
+"that tunnel served (by means of colluding with the gateway and harvesting"
+" \n"
+"the network database for all of the LeaseSets), he would know the router"
+" \n"
+"on which that destination is located (and without restricted routes, that"
+" \n"
+"would mean what IP address the destination is on)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:350
+msgid ""
+"It is to counter user behavior that tunnel lengths should be permuted, \n"
+"using algorithms based on the length requested (for example, the 1/MTBF \n"
+"length change for 0-hop tunnels outlined above)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:360
+msgid ""
+"The restricted route functionality described before was simply a "
+"functional \n"
+"issue - how to let peers who would not otherwise be able to communicate \n"
+"do so. However, the concept of allowing restricted routes includes "
+"additional \n"
+"capabilities. For instance, if a router absolutely cannot risk "
+"communicating \n"
+"directly with any untrusted peers, they can set up trusted links through"
+" \n"
+"those peers, using them to both send and receive all of its messages. \n"
+"Those hidden peers who want to be completely isolated would also refuse \n"
+"to connect to peers who attempt to get them to (as demonstrated by the \n"
+"garlic routing technique outlined before) - they can simply take the "
+"garlic \n"
+"clove that has a request for delivery to a particular peer and tunnel \n"
+"route that message out one of the hidden peer's trusted links with "
+"instructions \n"
+"to forward it as requested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:379
+#, python-format
+msgid ""
+"Within the network, we will want some way to deter people from consuming"
+" \n"
+"too many resources or from creating so many peers to mount a Sybil \n"
+"attack. Traditional techniques such as having a peer see who is "
+"requesting \n"
+"a resource or running a peer aren't appropriate for use within I2P, as \n"
+"doing so would compromise the anonymity of the system. Instead, we want \n"
+"to make certain requests \"expensive\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:387
+msgid ""
+"Hashcash is one technique that \n"
+"we can use to anonymously increase the \"cost\" of doing certain "
+"activities, \n"
+"such as creating a new router identity (done only once on installation),"
+" \n"
+"creating a new destination (done only once when creating a service), or \n"
+"requesting that a peer participate in a tunnel (done often, perhaps 2-300"
+" \n"
+"times per hour). We don't know the \"correct\" cost of each type of "
+"certificate \n"
+"yet, but with some research and experimentation, we could set a base "
+"level \n"
+"that is sufficiently expensive while not an excessive burden for people \n"
+"with few resources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:398
+msgid ""
+"There are a few other algorithms that we can explore for making those \n"
+"requests for resources \"nonfree\", and further research on that front is"
+" \n"
+"appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:408
+#, python-format
+msgid ""
+"To powerful passive external observers as well as large colluding "
+"internal \n"
+"observers, standard tunnel routing is vulnerable to traffic analysis "
+"attacks \n"
+"- simply watching the size and frequency of messages being passed between"
+" \n"
+"routers. To defend against these, we will want to essentially turn some \n"
+"of the tunnels into its own mix cascade - delaying messages received at \n"
+"the gateway and passing them in batches, reordering them as necessary, \n"
+"and injecting dummy messages (indistinguishable from other \"real\" "
+"tunnel \n"
+"messages by peers in the path). There has been a significant amount of \n"
+"research \n"
+"on these algorithms that we can lean on prior to implementing the various"
+" \n"
+"tunnel mixing strategies."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:421
+msgid ""
+"In addition to the anonymity aspects of more varied tunnel operation, \n"
+"there is a functional dimension as well. Each peer only has a certain \n"
+"amount of data they can route for the network, and to keep any particular"
+" \n"
+"tunnel from consuming an unreasonable portion of that bandwidth, they \n"
+"will want to include some throttles on the tunnel. For instance, a tunnel"
+" \n"
+"may be configured to throttle itself after passing 600 messages (1 per \n"
+"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n"
+"last minute). Excess messages may be delayed or summarily dropped. With \n"
+"this sort of throttling, peers can provide ATM-like QoS support for their"
+" \n"
+"tunnels, refusing to agree to allocate more bandwidth than the peer has \n"
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:434
+msgid ""
+"In addition, we may want to implement code to dynamically reroute tunnels"
+" \n"
+"to avoid failed peers or to inject additional hops into the path. This \n"
+"can be done by garlic routing a message to any particular peer in a "
+"tunnel \n"
+"with instructions to redefine the next-hop in the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:445
+msgid ""
+"Beyond the per-tunnel batching and mixing strategy, there are further \n"
+"capabilities for protecting against powerful attackers, such as allowing"
+" \n"
+"each step in a garlic routed path to define a delay or window in which \n"
+"it should be forwarded on. This would enable protections against the long"
+" \n"
+"term intersection attack, as a peer could send a message that looks "
+"perfectly \n"
+"standard to most peers that pass it along, except at any peers where the"
+" \n"
+"clove exposed includes delay instructions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:457
+#, python-format
+msgid ""
+"Performance related improvements are listed on the\n"
+"Performance page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2
+msgid "Bounty Arabic translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3
+#: i2p2www/pages/site/get-involved/bounties/index.html:119
+msgid "Arabic translation"
+msgstr "Tradução para o árabe"
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P echelon set out this bounty for translation\n"
+"of the I2P web page and I2P router console into Arabic."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12
+msgid "This bounty is set into 2 subparts:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14
+msgid "Part 1 is translation of the webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17
+msgid ""
+"For collecting the bounty of 20 BTC you need to translate the following "
+"pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25
+msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27
+msgid ""
+"Part 2 is the translation of the router console. The router console was\n"
+"partly translated and the bounty of 80 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34
+msgid "Judge is echelon."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2
+msgid "Bounty creating a I2P native Bitcoin client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3
+msgid "BTC I2P native client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to create a I2P native Bitcoin client. \n"
+"It should integrate with other client via the I2P network and via "
+"gateways to\n"
+"the existant bitcoin network."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15
+msgid "Judge is psychonaut who donated the first 30 € to this bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
+msgid "Bounty datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:3
+msgid "datastore"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:6
+msgid ""
+"To improve I2P's usage and to be independent of routers \n"
+"online status we want a datastorage as a extension to I2P.\n"
+"Like in Freenet the datastorage should be distributed and every\n"
+"participating node should be able to configure his options.\n"
+"The files should be saved in chunks and at least 2-3 times to\n"
+"obtain redundancy. Usage of storage space should be auto balanced.\n"
+"As it is a extra application, it should work flawless within I2P and\n"
+"cooperate nice with the I2P router. Maybe a integration within the\n"
+"webpage/router could be done."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:17
+msgid ""
+"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n"
+"\"eepsites in datastorage\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:21
+msgid ""
+"The frost for I2P datastorage bounty is paid for a frost like program \n"
+"with which files/messages are stored into database and got from database."
+"\n"
+"It needs to work with a GUI."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:26
+msgid ""
+"The eepsite served out of I2P datastorage extends a I2P router to send\n"
+"out eepsites out of the I2P datastorage. All files for eepsites need to "
+"be\n"
+"saved inside of datastorage and are taken from it.\n"
+"Extension:\n"
+"For better integration all datastorage participants could serve that "
+"eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:36
+msgid ""
+"For bounties to be declared done and paid, we need the program AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2
+msgid "Bounty I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3
+msgid "I2P Ubuntu/Debian package"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6
+msgid ""
+"For the future of I2P and in order to attract more people\n"
+"to I2P, this bounty was set for including an I2P package into the Ubuntu "
+"and Debian \n"
+"archive mirrors.\n"
+"To claim this bounty, the I2P router package needs to be available from\n"
+"Ubuntu and Debian archive mirrors and Debian bug \n"
+"448638 \n"
+"needs to be closed successfully."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2
+msgid "Bounty I2PHex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3
+msgid "i2phex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2PHex P2P ArneBab setout the bounty for implementing actual\n"
+"Phex code onto I2PHex."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:2
+msgid "Bounties"
+msgstr "Prêmios"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:5
+msgid "Bounties for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:6
+msgid ""
+"While we always gratefully accept any contributions of code, \n"
+"documentation, and the like, there are other ways to help I2P move \n"
+"forward.  As with any open source project, our goals would be achieved "
+"more \n"
+"rapidly if we were able to support all of our contributors to work on \n"
+"I2P full time.  However, as with any open source project, that's not a \n"
+"possibility.  Instead, we are making use of a bounty system, whereby \n"
+"anyone can get support for working on something that people want \n"
+"implemented, and people who want to contribute to I2P can be assured that"
+" \n"
+"their support goes to what they care about."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:18
+msgid ""
+"We are also keeping open the ability for people who want to support I2P \n"
+"but don't have strong feelings about the bounties available.  Those "
+"people\n"
+"can simply put their trust in the I2P team to do what we feel is best by\n"
+"donating to a catch-all general fund that will be used as deemed \n"
+"necessary - allocated to various bounties, covering incidentals (hosting,"
+" \n"
+"etc), and the like."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:27
+msgid "Current bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Name"
+msgstr "Nome"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Status"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Judge"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Dev"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Bounty"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:32
+msgid "Frost for I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:33
+#: i2p2www/pages/site/get-involved/bounties/index.html:40
+#: i2p2www/pages/site/get-involved/bounties/index.html:47
+#: i2p2www/pages/site/get-involved/bounties/index.html:54
+#: i2p2www/pages/site/get-involved/bounties/index.html:75
+#: i2p2www/pages/site/get-involved/bounties/index.html:82
+msgid "Proposal in development"
+msgstr "Propostas em desenvolvimento"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:35
+#: i2p2www/pages/site/get-involved/bounties/index.html:42
+#: i2p2www/pages/site/get-involved/bounties/index.html:49
+#: i2p2www/pages/site/get-involved/bounties/index.html:56
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+#: i2p2www/pages/site/get-involved/bounties/index.html:97
+msgid "vacant"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:39
+msgid "Eepsites served out of I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:46
+msgid "Backporting Phex code onto I2PHex"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:53
+msgid "I2P package in Debian and Ubuntu mirrors"
+msgstr "Pacote I2P nos repositórios do Debian e do Ubuntu"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:60
+msgid "Bitcoin client for I2P"
+msgstr "Cliente Bitcoin para a I2P"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:61
+msgid "Done, phase of verification"
+msgstr "Feito. Em fase de verificação."
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:67
+msgid "Unit tests and Multi-router Simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:68
+msgid "Partly done, partly in work, partly still open"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:89
+msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:94
+msgid "Bundling bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:95
+msgid "Proposed"
+msgstr "Proposto"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:102
+msgid "Claimed bounties"
+msgstr "Prêmios reivindicados"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Dev team"
+msgstr "Time de desenvolvedores"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:107
+msgid "Make I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:114
+msgid "Setting up a SILC server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:124
+msgid "Datastore over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:129
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
+msgid "Russian translation"
+msgstr "Tradução para o russo"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:134
+msgid "Swarming file transfer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:139
+msgid "Streaming library window size"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:144
+msgid "IRC connect time monitor"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:149
+msgid "Unit tests (part 1)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:161
+msgid ""
+"Dev lists anyone who may already be working on the bounty - collaboration"
+" is\n"
+"preferred, so if you're interested in working on it, please contact one "
+"of the\n"
+"people listed!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2
+msgid "Bounty I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3
+msgid "native IPv6 I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n"
+"To claim this bounty, the I2P router needs to run full on native\n"
+"IPv6 connections like it does on IPv4."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:17
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
+msgid ""
+"For bounties to be declared done and paid, we need the plugin AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:2
+msgid "NetDB Backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:3
+msgid "netDB backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:7
+msgid ""
+"The current NetDB implementation (namely the FloodFill system)\n"
+"needs to be extended with another backend to improve reliability,\n"
+"reduce attack surface and solve the scalability issue for the \n"
+"coming years."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:14
+msgid ""
+"A solution likely based on a DHT will be investigated and \n"
+"finally implemented."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2
+msgid "Bounty russian translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P a anonymous donator set out the bounty for translation\n"
+"of the I2P web page and I2P router console into russian language."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17
+msgid ""
+"For collecting the bounty of $115 USD you need to translate the following"
+" pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30
+msgid ""
+"Part 2 is the translation of the router console. The whole router console"
+" needs\n"
+"to be translated to collect the bounty of $115 USD."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37
+msgid "Judge is the russian donor."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:2
+msgid "Bounty migrate I2P IRC to SILC"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:3
+msgid "I2P silc server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:7
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to setup and host a I2P SILC server.   \n"
+"This will allow people to send files over their messaging servers and "
+"have intrinsic security built into the protocol."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:12
+msgid ""
+"A silc server needs to be set up and run for at least 3 month time to get"
+" payed. \n"
+"A second server should be set up, to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:16
+msgid ""
+"Bounty was withdrawn and money donated to returningnovice and general "
+"fund."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:22
+msgid "Judge is An Anonymous Secret Society, society@mail.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3
+msgid "Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7
+msgid ""
+"Beside of I2P we want to encourage users\n"
+"to care more about anonymity and security. As I2P is a low \n"
+"latency network with its natural limits, the software SYNDIE\n"
+"can overcome some of these limits and provide better anonymity\n"
+"for people who really need it."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14
+msgid ""
+"For our bad sake the syndie project was out of development for \n"
+"quite a long time yet (5 years). To get a fresh and new built \n"
+"with needed bugfixes we set out this bounty. Also syndie needs\n"
+"some enhancements and a better GUI for users to work with it.\n"
+"Current bounty sum is 50 Bitcoin."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22
+msgid ""
+"The latest Syndie coding rally did improve the situation of the\n"
+"Syndie package dramatically. A new Syndie package with bugfixes\n"
+"was created and made available on different webpages.\n"
+"As a result of this work, the bounty sum was reduced and\n"
+"the withdrawn money moved to the IPv6 bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2
+msgid "Bounty unittests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3
+msgid "unit test"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7
+msgid ""
+"To improve I2P's maintainability, we want to have a solid set of\n"
+"automated unit tests for the critical code.  While we do have some\n"
+"unit tests at the moment, they are ad-hoc and partly unfinished.  \n"
+"This bounty is for someone to check the existing tests and move over\n"
+"old ones to jUnit, automate their execution, extend them to provide \n"
+"better code coverage, and publish the report online.  Its a massive \n"
+"effort, but can be broken down into phases, listed below (phase 2 \n"
+"must occur first, but further phases may happen in any order).\n"
+"As this needs some reading of code, it is the best start point for\n"
+"new devs to get a good overview of I2P code and coding. A good job\n"
+"for college students, interns or anyone who is just interested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20
+msgid ""
+"Take care! Jobs and bounties shuffled a bit!\n"
+"Phase 6,7 and 8 are still open!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112
+#, python-format
+msgid "Phase %(phase)s:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27
+msgid "CI jenkins and IRC bot"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114
+#, python-format
+msgid "Bounty: %(euro)s €"
+msgstr "Prêmio: %(euro)s €"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29
+msgid "server runs and this section is blocked"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31
+msgid ""
+"To collect this bounty, a continuous integration server (Jenkins,\n"
+"old name was Hudson) must be set up and a connected IRC bot needs \n"
+"to set up in the channel #i2p-dev on IRC2p network to print out\n"
+"results of build tests.
            \n"
+"The server needs to be run long term."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41
+msgid "Check existing SDK tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69
+msgid "paid to str4d"
+msgstr "pago a str4d"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45
+#, python-format
+msgid ""
+"To collect this bounty, the existing SDK tests must be checked \n"
+"and made to work again. The need to be integrated into the ant \n"
+"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g."
+" \n"
+"Clover).  The ant script\n"
+"must be capable of generating test status results as a web page, \n"
+"which will be published online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56
+msgid "SDK test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80
+msgid "paid to unittests dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60
+msgid ""
+"To collect this bounty, the automated unit tests of the SDK \n"
+"(i2p/core/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67
+msgid "Router test migration"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71
+msgid ""
+"As with phase 2, the existing unit tests for the router must be\n"
+"moved over to the automated system."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78
+msgid "Router test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82
+msgid ""
+"To collect this bounty, the automated unit tests of the router \n"
+"(i2p/router/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89
+msgid "Streaming lib tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94
+msgid ""
+"To collect this bounty, a new set of unit tests must meet a \n"
+"measured code coverage of 90% of the streaming lib \n"
+"(i2p/apps/ministreaming/ and i2p/apps/streaming/)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102
+msgid "Unit tests coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106
+msgid ""
+"To collect this bounty, all above unit tests must meet the 100%\n"
+"coverage marker (except for log statements)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113
+msgid "MultiRouter simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115
+msgid "will be split in more sub-tasks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117
+msgid ""
+"To collect this bounty, the existing in-memory multi-router\n"
+"simulation must be checked, made work again and extend to simulate\n"
+"lots of routers in memory on a single machine. This bounty will\n"
+"be split in more fine grained subworks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126
+msgid ""
+"Judge on all these works is the donor and donor decides if a phase is\n"
+"called succesfull done and money can be paid."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2
+msgid "Bounty I2P vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3
+msgid "vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P torrent P2P I setout the bounty for a working I2P vuze\n"
+"plugin.\n"
+"The plugin needs to be official and submitted to vuze for publication\n"
+"on their webpage/repository for plugins.\n"
+"It should be easy to install and configured, work smooth and flawless.\n"
+"Configuration should be friendly to starters and made easy to be "
+"anonymous.\n"
+"It should work with *.b32.i2p destinations as with signed (516++ bits) \n"
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:2
+msgid "Application Development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:3
+msgid "May 2013"
+msgstr "Maio de 2013"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:6
+msgid "Application Development Guide"
+msgstr "Guia para o desenvolvimento de aplicativos"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:8
+msgid "Contents"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:10
+#: i2p2www/pages/site/get-involved/develop/applications.html:16
+msgid "Why write I2P-specific code?"
+msgstr "Por que escrever código especificamente para a I2P?"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:11
+#: i2p2www/pages/site/get-involved/develop/applications.html:102
+msgid "Important concepts"
+msgstr "Conceitos importantes"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:12
+#: i2p2www/pages/site/get-involved/develop/applications.html:190
+msgid "Development options"
+msgstr "Opções de desenvolvimento"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:13
+#: i2p2www/pages/site/get-involved/develop/applications.html:303
+msgid "Start developing - a simple guide"
+msgstr "Comece a desenvolver - um guia simples"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:18
+#, python-format
+msgid ""
+"There are multiple ways to use applications in I2P.\n"
+"Using I2PTunnel,\n"
+"you can use regular applications without needing to program explicit I2P "
+"support.\n"
+"This is very effective for client-server scenario's,\n"
+"where you need to connect to a single website.\n"
+"You can simply create a tunnel using I2PTunnel to connect to that "
+"website, as shown in Figure 1."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:26
+msgid ""
+"If your application is distributed, it will require connections to a "
+"large amount of peers.\n"
+"Using I2PTunnel, you will need to create a new tunnel for each peer you "
+"want to contact,\n"
+"as shown in Figure 2.\n"
+"This process can of course be automated, but running a lot of I2PTunnel "
+"instances creates a large amount of overhead.\n"
+"In addition, with many protocols you will need to force everyone to \n"
+"use the same set of ports for all peers - e.g. if you want to reliably "
+"run DCC \n"
+"chat, everyone needs to agree that port 10001 is Alice, port 10002 is "
+"Bob, port \n"
+"10003 is Charlie, and so on, since the protocol includes TCP/IP specific "
+"information\n"
+"(host and port)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:37
+msgid ""
+"General network applications often send a lot of additional data that "
+"could be used to identify users.\n"
+"Hostnames, port numbers, time zones, character sets, etc. are often sent "
+"without informing the user.\n"
+"As such, designing the network protocol specifically with anonymity in "
+"mind\n"
+"can avoid compromising user identities."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:43
+msgid ""
+"There are also efficiency considerations to review when determining how "
+"to \n"
+"interact on top of I2P.  The streaming library and things built on top of"
+" it\n"
+"operate with handshakes similar to TCP, while the core I2P protocols "
+"(I2NP and I2CP)\n"
+"are strictly message based (like UDP or in some instances raw IP).  The "
+"important\n"
+"distinction is that with I2P, communication is operating over a long fat "
+"network - \n"
+"each end to end message will have nontrivial latencies, but may contain "
+"payloads \n"
+"of up to several KB.  An application that needs a simple request and "
+"response can get rid\n"
+"of any state and drop the latency incurred by the startup and teardown "
+"handshakes\n"
+"by using (best effort) datagrams without having to worry about MTU "
+"detection or \n"
+"fragmentation of messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:57
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid ""
+"Creating a server-client connection using I2PTunnel only requires "
+"creating a single tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid "Figure 1:"
+msgstr "Figura 1:"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:64
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid ""
+"Setting up connections for a peer-to-peer applications requires a very "
+"large amount of tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid "Figure 2:"
+msgstr "Figura 2:"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:70
+msgid "In summary, a number of reasons to write I2P-specific code:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:74
+msgid ""
+"Creating a large amount of I2PTunnel instances consumes a non-trivial "
+"amount of resources,\n"
+"which is problematic for distributed applications (a new tunnel is "
+"required for each peer)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:78
+msgid ""
+"General network protocols often send a lot of additional data that can be"
+" used to identify users.\n"
+"Programming specifically for I2P allows the creation of a network "
+"protocol\n"
+"that does not leak such information, keeping users anonymous and secure."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:83
+msgid ""
+"Network protocols designed for use on the regular internet can be "
+"inefficient\n"
+"on I2P, which is a network with a much higher latency."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:90
+#, python-format
+msgid ""
+"I2P supports a standard plugins interface for"
+" developers\n"
+"so that applications may be easily integrated and distributed."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:96
+msgid ""
+"Applications written in Java and accessible/runnable\n"
+"using an HTML interface via the standard webapps/app.war\n"
+"may be considered for inclusion in the i2p distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:104
+msgid "There are a few changes that require adjusting to when using I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:108
+msgid "Destination ~= host+port"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:110
+msgid ""
+"An application running on I2P sends messages from and receives messages "
+"to a\n"
+"unique cryptographically secure end point - a \"destination\".  In TCP or"
+" UDP\n"
+"terms, a destination could (largely) be considered the equivalent of a "
+"hostname\n"
+"plus port number pair, though there are a few differences."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:118
+msgid ""
+"An I2P destination itself is a cryptographic construct - all data sent to"
+" one is \n"
+"encrypted as if there were universal deployment of IPsec with the "
+"(anonymized)\n"
+"location of the end point signed as if there were universal deployment of"
+" DNSSEC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:123
+msgid ""
+"I2P destinations are mobile identifiers - they can be moved from one I2P "
+"router\n"
+"to another (or it can even \"multihome\" - operate on multiple routers at"
+"\n"
+"once).  This is quite different from the TCP or UDP world where a single "
+"end point (port)\n"
+"must stay on a single host."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:130
+msgid ""
+"I2P destinations are ugly and large - behind the scenes, they contain a "
+"2048 bit ElGamal\n"
+"public key for encryption, a 1024 bit DSA public key for signing, and a "
+"variable size \n"
+"certificate, which may contain proof of work or blinded data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:135
+#, python-format
+msgid ""
+"There are existing ways to refer to these large and ugly destinations by "
+"short\n"
+"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not "
+"guarantee\n"
+"globally uniqueness (since they're stored locally in a database on each "
+"person's machine)\n"
+"and the current mechanism is not especially scalable nor secure (updates "
+"to the host list are\n"
+"managed using \"subscriptions\" to naming services).\n"
+"There may be some secure, human readable, scalable, and globally \n"
+"unique, naming system some day, but applications shouldn't depend upon it"
+" being in place,\n"
+"since there are those who don't think such a beast is possible.\n"
+"Further information on the naming system is "
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:149
+#, python-format
+msgid ""
+"While most applications do not need to distinguish protocols and ports,\n"
+"I2P does support them. Complex applications may specify a "
+"protocol,\n"
+"from port, and to port, on a per-message basis, to multiplex traffic on\n"
+"a single destination.\n"
+"See the datagram page for details.\n"
+"Simple applications operate by listening for \"all protocols\" on \"all "
+"ports\" of a destination."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:158
+msgid "Anonymity and confidentiality"
+msgstr "Anonimato e confidencialidade"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:160
+msgid ""
+"I2P has transparent end to end encryption\n"
+"and authentication for all data passed over the network - if Bob sends to"
+" Alice's destination,\n"
+"only Alice's destination can receive it, and if Bob is using the "
+"datagrams or streaming \n"
+"library, Alice knows for certain that Bob's destination is the one who "
+"sent the data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:167
+msgid ""
+"Of course, I2P transparently anonymizes the\n"
+"data sent between Alice and Bob, but it does nothing to anonymize the "
+"content of what they\n"
+"send.  For instance, if Alice sends Bob a form with her full name, "
+"government IDs, and \n"
+"credit card numbers, there is nothing I2P can do.  As such, protocols and"
+" applications should \n"
+"keep in mind what information they are trying to protect and what "
+"information they are willing\n"
+"to expose."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:176
+msgid "I2P datagrams can be up to several KB"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:178
+#, python-format
+msgid ""
+"Applications that use I2P datagrams (either raw or repliable ones) can "
+"essentially be thought\n"
+"of in terms of UDP - the datagrams are unordered, best effort, and "
+"connectionless - but unlike\n"
+"UDP, applications don't need to worry about MTU detection and can simply "
+"fire off large datagrams.\n"
+"While the upper limit is nominally 32 KB, the message is fragmented for "
+"transport, thus dropping\n"
+"the reliability of the whole. Datagrams over about 10 KB are not "
+"currently recommended.\n"
+"See the datagram page for details.\n"
+"For many applications, 10 KB of data is sufficient for an\n"
+"entire request or response, allowing them to transparently operate in I2P"
+" as a UDP-like \n"
+"application without having to write fragmentation, resends, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:192
+msgid ""
+"There are several means of sending data over I2P, each with their own "
+"pros and cons.\n"
+"The streaming lib is the recommended interface, used by the majority of "
+"I2P applications."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:197
+msgid "Streaming Lib"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:198
+#, python-format
+msgid ""
+"The full streaming library is now the "
+"standard\n"
+"interface. It allows programming using TCP-like sockets, as explained in "
+"the Streaming development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:204
+#, python-format
+msgid ""
+"BOB is the Basic Open Bridge,\n"
+"allowing an application in any language to make streaming connections \n"
+"to and from I2P. At this point in time it lacks UDP support, but UDP "
+"support\n"
+"is planned in the near future. BOB also contains several tools, such as \n"
+"destination key generation, and verification that an address conforms to"
+" \n"
+"I2P specifications. Up to date info and applications that use BOB can be"
+" \n"
+"found at this eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:217
+msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:218
+#, python-format
+msgid ""
+"SAM is the Simple Anonymous Messaging protocol, "
+"allowing an\n"
+"application written in any language to talk to a SAM bridge through a "
+"plain TCP socket and have\n"
+"that bridge multiplex all of its I2P traffic, transparently coordinating "
+"the encryption/decryption\n"
+"and event based handling.  SAM supports three styles of operation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:225
+msgid ""
+"streams, for when Alice and Bob want to send data to each other reliably "
+"and in order"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:228
+msgid ""
+"repliable datagrams, for when Alice wants to send Bob a message that Bob "
+"can reply to"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:231
+msgid ""
+"raw datagrams, for when Alice wants to squeeze the most bandwidth and "
+"performance as possible,\n"
+"and Bob doesn't care whether the data's sender is authenticated or not "
+"(e.g. the data transferred\n"
+"is self authenticating)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:237
+msgid ""
+"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n"
+"multiplexing/demultiplexing. Each I2P stream is handled by its own socket"
+" between the application\n"
+"and the SAM bridge. Besides, datagrams can be sent and received by the "
+"application through datagram\n"
+"communications with the SAM bridge."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:244
+#, python-format
+msgid ""
+"SAM V2 is a new version used by imule\n"
+"that fixes some of the problems in SAM.\n"
+"
            \n"
+"SAM V3 is used by imule since version 1.4.0."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:252
+msgid ""
+"The I2PTunnel application allows applications to build specific TCP-like "
+"tunnels to peers \n"
+"by creating either I2PTunnel 'client' applications (which listen on a "
+"specific port and connect\n"
+"to a specific I2P destination whenever a socket to that port is opened) "
+"or I2PTunnel 'server'\n"
+"applications (which listen to a specific I2P destination and whenever it "
+"gets a new I2P \n"
+"connection it outproxies to a specific TCP host/port).  These streams are"
+" 8-bit clean, and are\n"
+"authenticated and secured through the same streaming library that SAM "
+"uses, but there is a \n"
+"nontrivial overhead involved with creating multiple unique I2PTunnel "
+"instances, since each have\n"
+"their own unique I2P destination and their own set of tunnels, keys, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:264
+msgid ""
+"I2P supports a SOCKS V4 and V5 proxy.\n"
+"Outbound connections work well. Inbound (server) and UDP functionality "
+"may be incomplete\n"
+"and untested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:271
+msgid "Removed"
+msgstr "Removido"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:272
+msgid ""
+"There used to be a simple \"ministreaming\" library,\n"
+"but now ministreaming.jar contains only the interfaces for the full "
+"streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:277
+msgid "Datagrams"
+msgstr "Datagramas"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:278
+msgid "Recommended for UDP-like applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:279
+#, python-format
+msgid ""
+"The Datagram library allows sending UDP-"
+"like packets.\n"
+"It's possible to use:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:284
+msgid "Repliable datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:285
+msgid "Raw datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:289
+msgid "Not recommended"
+msgstr "Não recomendado"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:290
+#, python-format
+msgid ""
+"I2CP itself is a language independent protocol, "
+"but to implement an I2CP library \n"
+"in something other than Java there is a significant amount of code to be "
+"written (encryption routines, \n"
+"object marshalling, asynchronous message handling, etc).  While someone "
+"could write an I2CP library in \n"
+"C or something else, it would most likely be more useful to use the C SAM"
+" library instead."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:297
+msgid "Web Applications"
+msgstr "Aplicações para a Web"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:298
+msgid ""
+"I2P comes with the Jetty webserver, and configuring to use the Apache "
+"server instead is straightforward.\n"
+"Any standard web app technology should work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:304
+msgid ""
+"Developing using I2P requires a working I2P installation and a "
+"development environment of your own choice.\n"
+"If you are using Java, you can start development with the streaming library or datagram library.\n"
+"Using another programming language, SAM or BOB can be used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:310
+msgid "Developing with the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:312
+msgid ""
+"The following example shows how to create TCP-like client and server "
+"applications\n"
+"using the streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:317
+msgid "This will require the following libraries in your classpath:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:321
+msgid "The streaming library itself"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:322
+msgid "Factory and interfaces for the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:323
+msgid "Standard I2P classes, data structures, API, and utilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:326
+msgid ""
+"Network communication requires the usage of I2P network sockets.\n"
+"To demonstrate this, we will create an application where a client can "
+"send text messages to a server,\n"
+"who will print the messages and send them back to the client. In other "
+"words, the server will function as an echo."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:331
+msgid ""
+"We will start by initializing the server application. This requires "
+"getting an I2PSocketManager\n"
+"and creating an I2PServerSocket.\n"
+"We will not provide the I2PSocketManagerFactory with the saved keys for "
+"an existing Destination,\n"
+"so it will create a new Destination for us.\n"
+"So we will ask the I2PSocketManager for an I2PSession, so we can find out"
+" the Destination that\n"
+"was created, as we will need to copy and paste that information later so "
+"the client can connect to us."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:362
+msgid "Code example 1: initializing the server application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:364
+msgid ""
+"Once we have an I2PServerSocket, we can create I2PSocket instances to "
+"accept connections from clients.\n"
+"In this example, we will create a single I2PSocket instance, that can "
+"only handle one client at a time.\n"
+"A real server would have to be able to handle multiple clients.\n"
+"To do this, multiple I2PSocket instances would have to be created, each "
+"in separate threads.\n"
+"Once we have created the I2PSocket instance, we read data, print it and "
+"send it back to the client.\n"
+"The bold code is the new code we add."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:448
+msgid "Code example 2: accepting connections from clients and handling messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:452
+msgid ""
+"When you run the above server code, it should print something like this "
+"(but without the line endings, it should just be\n"
+"one huge block of characters):"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:466
+msgid ""
+"This is the base64-representation of the server Destination. The client "
+"will need this string to reach the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:470
+msgid ""
+"Now, we will create the client application. Again, a number of steps are "
+"required for initialization.\n"
+"Again, we will need to start by getting an I2PSocketManager.\n"
+"We won't use an I2PSession and an I2PServerSocket this time.\n"
+"Instead, we will use the server Destination string to start our "
+"connection.\n"
+"We will ask the user for the Destination string, and create an I2PSocket "
+"using this string.\n"
+"Once we have an I2PSocket, we can start sending and receiving data to and"
+" from the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:554
+msgid ""
+"Code example 3: starting the client and connecting it to the server "
+"application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:556
+msgid ""
+"Finally, you can run both the server and the client application.\n"
+"First, start the server application. It will print a Destination string "
+"(like shown above).\n"
+"Next, start the client application. When it requests a Destination "
+"string, you can enter the string printed by the server.\n"
+"The client will then send 'Hello I2P!' (along with a newline) to the "
+"server, who will print the message and send it back to the client."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:562
+msgid "Congratulations, you have successfully communicated over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:566
+msgid "Existing Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:567
+msgid "Contact us if you would like to contribute."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:588
+msgid "Application Ideas"
+msgstr "Idéias para aplicativos"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:590
+msgid "NNTP server - there have been some in the past, none at the moment"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:593
+msgid ""
+"Jabber server - there have been some in the past, and there is one at the"
+" moment, with access to the public internet"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:596
+msgid "PGP Key server and/or proxy"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:599
+msgid ""
+"Content Distribution / DHT applications - resurrect feedspace,\n"
+"port dijjer, look for alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:603
+msgid "Help out with Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:606
+msgid ""
+"Web-based applications - The sky is the limit for hosting web-server-"
+"based\n"
+"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n"
+"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:611
+msgid ""
+"Resurrect some old apps, several previously in the i2p source package -\n"
+"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2
+msgid "I2P Developer's MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4
+msgid "MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5
+msgid ""
+"Monotone servers used by the I2P project require two types of keys to be "
+"used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
+msgid ""
+"Commit Keys to sign changes checked-in to the "
+"respository; and"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10
+msgid ""
+"Transport Keys to push changes to remote "
+"servers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13
+#, python-format
+msgid ""
+"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
+"import the\n"
+"developer commit keys, but only Monotone \n"
+"server operators will need to import the transport keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20
+msgid "Developer Commit keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:255
+msgid "Developer Transport Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:256
+#, python-format
+msgid ""
+"Note: Transport keys are only needed for setting up a\n"
+"Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
+msgid "License Agreements"
+msgstr "Acordos de Licença"
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
+#, python-format
+msgid "For more information see the licenses page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8
+msgid ""
+"Following is a monotonerc file defining the current trust list.\n"
+"Developers must use this file in ~/.monotone/monotonerc or\n"
+"_MTN/montonerc in their i2p.i2p workspace."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17
+msgid "Agreements"
+msgstr "Acordos"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:2
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115
+msgid "Licenses"
+msgstr "Licenças"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:4
+msgid "I2P Software Licenses"
+msgstr "I2P - Licenças de software"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:5
+#, python-format
+msgid ""
+"As required by our\n"
+"threat model (among other reasons), the \n"
+"software developed to support the anonymous communication \n"
+"network we call I2P must be freely available, open source, \n"
+"and user modifiable.  To meet these criteria, we make use of\n"
+"a variety of legal and software engineering techniques so\n"
+"as to remove as many barriers to entry for those considering\n"
+"making use of or contributing to the I2P effort."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:16
+msgid ""
+"While the information below may be more confusing than just simply \n"
+"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
+"the short answer to the question \"How is I2P licensed?\" is this:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:22
+msgid "All software bundled in the I2P distributions will allow:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:24
+msgid "use without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:25
+msgid ""
+"use with no restrictions on how, when, where, why, or by whom is running "
+"it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:26
+msgid "access to the source code without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:27
+msgid "modifications to the source"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:30
+msgid ""
+"Most of the software guarantees much more - the ability of anyone "
+"to \n"
+"distribute the modified source however they choose.  However, not all of "
+"the \n"
+"software bundled provides this freedom - the GPL restricts the ability of"
+" \n"
+"developers who wish to integrate I2P with their own applications that are"
+" not \n"
+"themselves open source applications.  While we applaud the noble goals of"
+" \n"
+"increasing the resources in the commons, I2P is best served by removing "
+"any\n"
+"barriers that stand in the way of its adoption - if a developer "
+"considering whether\n"
+"they can integrate I2P with their application has to stop and check with "
+"their lawyer,\n"
+"or conduct a code audit to make sure their own source can be released as "
+"GPL-compatible,\n"
+"we lose out."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:43
+msgid "Component licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:44
+msgid ""
+"The I2P distribution contains several resources, reflecting the "
+"partitioning of \n"
+"the source code into components.  Each component has its own license, "
+"which all \n"
+"developers who contribute to it agree to - either by explicitly declaring"
+" the release\n"
+"of code committed under a license compatible with that component, or by "
+"implicitly\n"
+"releasing the code committed under the component's primary license.  Each"
+" of these \n"
+"components has a lead developer who has the final say as to what license "
+"is compatible\n"
+"with the component's primary license, and the I2P project manager has the"
+" final say as\n"
+"to what licenses meet the above four guarantees for inclusion in the I2P "
+"distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:57
+msgid "Component"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:58
+msgid "Source path"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:59
+msgid "Resource"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:60
+msgid "Primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:61
+msgid "Alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:62
+msgid "Lead developer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:271
+msgid "GPL + java exception"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:272
+#, python-format
+msgid ""
+"While it may be redundant, just for clarity the\n"
+"GPL'ed code included within\n"
+"I2PTunnel and other apps must be released under the GPL with an "
+"additional \"exception\"\n"
+"explicitly authorizing the use of Java's standard libraries:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:288
+msgid ""
+"All source code under each component will by default be licensed under "
+"the\n"
+"primary license, unless marked otherwise in the code.  All of the above "
+"is\n"
+"summary of the license terms - please see the specific license for the "
+"component\n"
+"or source code in question for authoritative terms.  Component source "
+"locations and\n"
+"resource packaging may be changed if the repository is reorganized."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:296
+msgid "Commit privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:297
+#, python-format
+msgid ""
+"Developers may push changes to a distributed monotone repository if you\n"
+"receive permission from the person running that repository.\n"
+"See the Monotone Page for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:303
+msgid ""
+"However, to have changes included in a release, developers\n"
+"must be trusted by the release manager (currently zzz).\n"
+"In addition, they must explicitly agree with the above terms to be "
+"trusted.\n"
+"That means that they must send one of the release managers a signed "
+"message affirming that:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:310
+msgid ""
+"Unless marked otherwise, all code I commit is implicitly licensed under\n"
+"the component's primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:314
+msgid ""
+"If specified in the source, the code may be explicitly licensed under one"
+"\n"
+"of the component's alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:318
+msgid ""
+"I have the right to release the code I commit under the terms I\n"
+"am committing it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:324
+#, python-format
+msgid ""
+"If anyone is aware of any instances where the above conditions are not "
+"met,\n"
+"please contact the component lead and/or an I2P release manager with "
+"further\n"
+"information.\n"
+"See developers' license agreements."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
+msgid "Release Signing Key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
+msgid "Releases 0.7.6 and later are signed by zzz. His public key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40
+msgid ""
+"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public "
+"key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2
+msgid "Signed Developer Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4
+msgid ""
+"Keys for zzz, Complication and welterde are provided clearsigned. The key"
+" for jrandom must be\n"
+"verified differently, since he's away, and only left a binary detached\n"
+"signature for his key."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16
+msgid "Monotone keys for zzz"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47
+msgid "Monotone keys for welterde"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79
+msgid "Monotone keys for Complication"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114
+msgid "Monotone keys for jrandom"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
+msgid "Others"
+msgstr "Outros"
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
+msgid ""
+"Tip: To find zzz's GPG key, on his eepsite locate the key "
+"`0xA76E0BED`, with\n"
+"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 "
+"B310 4155\n"
+"76BA A76E 0BED`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49
+msgid ""
+"Tip: To find welterde's GPG key, on public keyservers locate the "
+"key\n"
+"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720"
+" FD81\n"
+"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81
+msgid ""
+"Tip: To find Complication's GPG key, on his eepsite locate the key"
+"\n"
+"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint "
+"`73CF\n"
+"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116
+msgid ""
+"Tip: To find jrandom's GPG key for Syndie releases, on public "
+"keyservers locate\n"
+"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n"
+"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122
+msgid ""
+"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n"
+"deployed in the Syndie Monotone repository, in a file named `mtn-"
+"committers`.\n"
+"That file also had a GPG signature, `mtn-committers.sig`, but it was a "
+"binary\n"
+"detached signature. I am going to supply both files in GPG ASCII-armoured"
+" form\n"
+"below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130
+msgid ""
+"First, the file `mtn-committers` containing jrandom's Monotone key. Save "
+"as\n"
+"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers "
+"--dearmor\n"
+"mtn-committers.asc`:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151
+msgid ""
+"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n"
+"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-"
+"committers.sig\n"
+"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n"
+"`mtn-committers` file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170
+#, python-format
+msgid ""
+"Some of the developers have included their Monotone keys in their signed license agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2
+msgid "Developer Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4
+#, python-format
+msgid "Read the new developers guide first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8
+msgid "Basic Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10
+msgid ""
+"Most of the following should be common sense for anybody who has worked "
+"on open source or in a commercial\n"
+"programming envrionment.\n"
+"The following applies mostly to the main development branch i2p.i2p.\n"
+"Guidelines for other branches, plugins, and external apps may be "
+"substantially different;\n"
+"check with the appropriate developer for guidance."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18
+msgid "Community"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20
+msgid ""
+"Please don't just \"write code\". If you can, participate in other "
+"development activities, including:\n"
+"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
+"testing;\n"
+"bug reporting and responses; documentation; code reviews; etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25
+msgid ""
+"Active devs should be available periodically on IRC #i2p-dev.\n"
+"Be aware of the current release cycle.\n"
+"Adhere to release milestones such as feature freeze, tag freeze, and\n"
+"the checkin deadline for a release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35
+msgid ""
+"Have a basic understanding of distributed source control systems, even if"
+" you haven't\n"
+"used monotone before. Ask for help if you need it.\n"
+"Once pushed, checkins are forever, there is no undo. Please be careful.\n"
+"If you have not used monotone before, start with baby steps.\n"
+"Check in some small changes and see how it goes."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42
+msgid ""
+"Test your changes before checking them in.\n"
+"If you prefer the checkin-before-test development model,\n"
+"use your own development branch (e.g. i2p.i2p.yourname.test)\n"
+"and propagate back to i2p.i2p once it is working well.\n"
+"Do not break the build. Do not cause regressions.\n"
+"In case you do (it happens), please do not vanish for a long period after"
+"\n"
+"you push your change."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51
+msgid ""
+"If your change is non-trivial, or you want people to test it and need "
+"good test reports\n"
+"to know whether your change was tested or not, add a checkin comment to "
+"history.txt\n"
+"and increment the build revision in RouterVersion.java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56
+msgid ""
+"Ensure that you have the latest monotonerc file in _MTN.\n"
+"Do not check in on top of untrusted revisions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60
+msgid ""
+"Ensure that you pull the latest revision before you check in.\n"
+"If you inadvertently diverge, merge and push as soon as possible.\n"
+"Don't routinely make others merge for you.\n"
+"Yes, we know that monotone says you should push and then merge,\n"
+"but in our experience, in-workspace merge works just as well as in-"
+"database merge,\n"
+"without creating a merge revision."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
+msgid ""
+"Do not check in major changes into the main i2p.i2p branch late in the "
+"release cycle.\n"
+"If a project will take you more than a couple days, create your own "
+"branch in monotone\n"
+"and do the development there so you do not block releases."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75
+msgid "Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77
+msgid ""
+"Coding style throughout most of the code is 4-spaces for indentation. Do "
+"not use tabs.\n"
+"Do not reformat code. If your IDE or editor wants to reformat everything,"
+" get control of it.\n"
+"Yes, we know 4 spaces is a pain, but perhaps you can configure your "
+"editor appropriately.\n"
+"In some places, the coding style is different.\n"
+"Use common sense. Emulate the style in the file you are modifying."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84
+msgid ""
+"New classes and methods require at least brief javadocs. Add @since "
+"release-number."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87
+msgid ""
+"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our "
+"official API.\n"
+"There are several out-of-tree plugins and other applications that rely on"
+" this API.\n"
+"Be careful not to make any changes that break compatibility.\n"
+"Don't add methods to the API unless they are of general utility.\n"
+"Javadocs for API methods should be clear and complete.\n"
+"If you add or change the API, also update the documentation on the "
+"website (i2p.www branch)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95
+msgid ""
+"Tag strings for translation where appropriate.\n"
+"Don't change existing tagged strings unless really necessary, as it will "
+"break existing translations.\n"
+"Do not add or change tagged strings after the \"tag freeze\" in the "
+"release cycle so that\n"
+"translators have a chance to update before the release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101
+msgid ""
+"Use generics and concurrent classes where possible. I2P is a highly "
+"multi-threaded application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104
+msgid ""
+"We require Java 6 to build but only Java 5 to run I2P.\n"
+"Do not use Java 6 classes or methods without handling the class not found"
+" exceptions\n"
+"and providing alternate Java 5 code. See classes in net.i2p.util for "
+"examples."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109
+msgid ""
+"Explicitly convert between primitive types and classes;\n"
+"don't rely on autoboxing/unboxing."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117
+msgid ""
+"Only check in code that you wrote yourself.\n"
+"Before checking in any code or library jars from other sources,\n"
+"justify why it is necessary,\n"
+"verify the license is compatible,\n"
+"and obtain approval from the lead developer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124
+msgid ""
+"For any images checked in from external sources,\n"
+"it is your responsibility to first verify the license is compatible.\n"
+"Include the license and source information in the checkin comment."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131
+msgid "Bugs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
+#, python-format
+msgid ""
+"Managing Trac tickets is everybody's job, please help.\n"
+"Monitor %(trac)s for tickets you have been assigned or can help with.\n"
+"Assign, categorize, comment on, fix, or close tickets if you can."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138
+msgid ""
+"Close a ticket when you think you've fixed it.\n"
+"We don't have a test department to verify and close tickets.\n"
+"If you arent sure you fixed it, close it and add a note saying\n"
+"\"I think I fixed it, please test and reopen if it's still broken\".\n"
+"Add a comment with the dev build number or revision and set\n"
+"the milestone to the next release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:2
+msgid "Using an IDE with I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:4
+msgid ""
+"The main I2P development branch (i2p.i2p) has been set up to"
+" enable developers to easily set up two of the commonly-used IDEs for "
+"Java development: Eclipse and NetBeans."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:10
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain .project and .classpath Eclipse files, to enable the branch "
+"to be easily set up in Eclipse."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:16
+msgid ""
+"Check out the I2P branch into some directory (e.g. "
+"$HOME/dev/i2p.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:20
+msgid ""
+"Open Eclipse and create a new Workspace, based in the directory that the "
+"I2P branch was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:24
+msgid ""
+"Select \"File - Import...\" and then under \"General\" select \"Existing "
+"Projects into Workspace\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:28
+msgid ""
+"For \"Select root directory:\" choose the directory that the I2P branch "
+"was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:32
+msgid "If necessary, click \"Refresh\" to refresh the list of projects."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:36
+msgid "Select every project in the list, and click \"Finish\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:40
+msgid ""
+"Done! Your workspace should now contain all projects within the I2P "
+"branch, and their build dependencies should be correctly set up."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:48
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain NetBeans project files."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:2
+msgid "Monotone"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:4
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:9
+msgid "Operating a Monotone client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:11
+#: i2p2www/pages/site/get-involved/guides/monotone.html:63
+msgid "Generating Monotone keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:12
+msgid "Trust and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:13
+#: i2p2www/pages/site/get-involved/guides/monotone.html:196
+msgid "Obtaining and deploying developers' keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:14
+#: i2p2www/pages/site/get-involved/guides/monotone.html:227
+msgid "Setting up trust evaluation hooks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:15
+#: i2p2www/pages/site/get-involved/guides/monotone.html:268
+msgid ""
+"Pulling the i2p.i2p, i2p.www and "
+"i2p.syndie branches"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:16
+#: i2p2www/pages/site/get-involved/guides/monotone.html:308
+msgid "Verifying that trust evaluation works"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:17
+#: i2p2www/pages/site/get-involved/guides/monotone.html:357
+msgid "Checking out a working copy of the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:18
+#: i2p2www/pages/site/get-involved/guides/monotone.html:384
+msgid "Updating your working copy to the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:22
+#: i2p2www/pages/site/get-involved/guides/monotone.html:414
+msgid "Operating a Monotone Server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:24
+msgid "Obtaining and deploying developers’ transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:25
+#: i2p2www/pages/site/get-involved/guides/monotone.html:424
+msgid "Granting push and pull access"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:26
+#: i2p2www/pages/site/get-involved/guides/monotone.html:469
+msgid "Running Monotone in server mode"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:27
+#: i2p2www/pages/site/get-involved/guides/monotone.html:494
+msgid "Differences under Debian GNU/Linux"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:34
+#, python-format
+msgid ""
+"This is a revised version of Complication's original\n"
+"  guide detailing the use of Monotone in I2P development.\n"
+"  For basic instructions see the quick-start "
+"guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:42
+#, python-format
+msgid ""
+"I2P has a distributed development model. The source code is replicated "
+"across\n"
+"  independently administered Monotone (\"MTN\") repositories.\n"
+"  Developers with commit rights are able to push their changes to the "
+"repository\n"
+"  (a license agreement needs to be "
+"signed\n"
+"  before commit rights are granted)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:52
+msgid ""
+"Some of Monotone's noteworthy qualities are: distributed\n"
+"  version control, cryptographic authentication, access control, its "
+"small size, having few\n"
+"  dependencies, storage of projects in a compressed SQLite database file,"
+" and\n"
+"  having the ability to resume interrupted synchronization attempts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:61
+msgid "Operating a Monotone Client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:66
+msgid ""
+"A transport key grants you the ability to push your changes to a Monotone"
+" repository server.\n"
+"  In order to commit code into Monotone (in essence signing your code), a"
+" commit key is also needed.\n"
+"  None of the public Monotone servers on I2P currently require a key in "
+"order to read (or pull) the source code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:74
+msgid ""
+"Without a transport key, one cannot:\n"
+"  
              \n"
+"    
            • pull code from a server which doesn't allow global read "
+"access
              • \n"
+"    
            • push code to any server
              • \n"
+"    
            • run a Monotone server
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:85
+msgid ""
+"Without a commit key, one cannot:\n"
+"  
              \n"
+"    
            • commit any code
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:94
+msgid ""
+"If you only intend to retrieve code from MTN, feel free to skip to the\n"
+"  next section. "
+"If you want\n"
+"  to generate keys, read the following."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:102
+msgid ""
+"By convention keys are named like an e-mail addresses, but a "
+"corresponding e-mail\n"
+"  address does not need to exist. For example, your keys might be named:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:113
+msgid ""
+"Monotone stores keys under $HOME/.monotone/keys in "
+"text files which\n"
+"  are named identically to the keys. For example:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:123
+msgid ""
+"To generate transport and commit keys, enter the following commands at a "
+"prompt:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:133
+msgid ""
+"Monotone will prompt you for a password to protect your keys. You are "
+"very strongly encouraged to set a password\n"
+"  for the commit key. Many users will leave an empty password for the "
+"transport key, especially those running a\n"
+"  Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:141
+msgid "Trust, and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:145
+msgid ""
+"Monotone's security model helps to ensure that nobody can easily "
+"impersonate a developer without\n"
+"  it being noticed. Since developers can make mistakes and become "
+"compromised,only manual review can\n"
+"  ensure quality of code. Monotone's trust model will ensure that you "
+"read the right diffs. It does\n"
+"  not replace reading diffs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:155
+msgid ""
+"A Monotone repository is a single file (a compressed SQLite database) "
+"which contains all of the project's source code and history."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:161
+msgid ""
+"After importing the "
+"developers' keys into Monotone and\n"
+"  setting up trust "
+"evaluation hooks,\n"
+"  Monotone will prevent untrusted code from being checked out into your "
+"workspace.\n"
+"  There are commands available to clean untrusted code from your "
+"workspace but in practice they've not been\n"
+"  needed due to the push access policies in place."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:171
+msgid ""
+"A repository can hold many branches. For example, our repository holds "
+"the\n"
+"  following main branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:176
+msgid "The I2P router and associated programs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:177
+msgid "The I2P project website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:178
+msgid "Syndie, a distributed forums tool"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:183
+msgid ""
+"By convention, the I2P Monotone repository is named i2p.mtn."
+" Before pulling\n"
+"  source code from servers, a database for your repository will need to "
+"be initialized.\n"
+"  To initialize your local repository, change into the directory that you"
+" want the\n"
+"  i2p.mtn file and branch directories to be stored and issue"
+" the following\n"
+"  command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:199
+msgid ""
+"Keys which developers use to commit code are essential for trust "
+"evaluation in\n"
+"  Monotone. The other developers' transport keys are only required for "
+"Monotone server operators.\n"
+"  "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:206
+#, python-format
+msgid ""
+"Developers' commit keys are provided GPG-signed on another page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:212
+#, python-format
+msgid ""
+"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
+"  file. Create this file (e.g. keys.txt) in the same "
+"directory where i2p.mtn is located. Import the keys with the"
+" command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:222
+msgid ""
+"Note: Never add keys to "
+"$HOME/.monotone/keys manually."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:230
+msgid ""
+"The default Monotone trust policy is way too lax for our requirements: "
+"every committer is trusted by default.\n"
+"  That is not acceptable for I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:237
+msgid ""
+"Change into the directory $HOME/.monotone and open "
+"the file\n"
+"  monotonerc with a text editor. Copy and paste the "
+"following two functions into this file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:246
+msgid ""
+"The first function determines an intersection between two sets, in our "
+"case a\n"
+"  revision's signers and trusted signers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:253
+msgid ""
+"The second function determines trust in a given revision, by calling the "
+"first\n"
+"  function with \"signers\" and \"trusted\" as arguments. If the "
+"intersection is\n"
+"  null, the revision is not trusted. If the intersection is not empty, "
+"the\n"
+"  revision is trusted. Otherwise, the revision is not trusted."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:262
+msgid ""
+"More information about Trust Evauluation Hooks can be found in the official Monotone "
+"documentation."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:271
+msgid ""
+"Enter the directory where you initialized i2p.mtn. Depending "
+"on whether you\n"
+"  want only I2P sources, or also sources for the I2P website and Syndie, "
+"you can\n"
+"  perform the pull operation in different ways."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:279
+msgid "If you only want I2P sources:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:288
+msgid "If you want all branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:294
+msgid ""
+"If the transfer aborts before completing sucessfully, simply repeating "
+"the pull command will resume the transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:300
+msgid ""
+"Pulling in the above examples is done anonymously by specifying an empty "
+"transport key.\n"
+"  If everyone pulls anonymously it will be harder for an attacker who "
+"gains control of the server\n"
+"  to selectively provide some people with tampered data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:311
+msgid "To verify that trust evaluation works:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:315
+msgid "Make a backup of your monotonerc file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:316
+msgid ""
+"Modify monotonerc by setting the trusted_signers "
+"variable in the following way:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:322
+msgid ""
+"With monotonerc configured as above, Monotone will no"
+" longer trust any committers. Confirm this by changing into the\n"
+"directory where i2p.mtn was created and attempt a checkout "
+"of the I2P branch:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:332
+msgid ""
+"A directory named i2p.i2p should not appear. You "
+"should encounter many\n"
+"  error messages like:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:349
+msgid ""
+"If you are satisfied with results, restore the backup of\n"
+"  monotonerc that was created above. If you didn't create a "
+"backup\n"
+"  as advised, re-read Setting up trust evaluation hooks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:360
+msgid ""
+"If you already have a branch checked out, skip to the next\n"
+"  section."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:367
+msgid ""
+"Change into the directory where i2p.mtn is located. Over "
+"there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:376
+msgid ""
+"The checkout should complete without error messages and a directory named"
+"\n"
+"  i2p.i2p should appear in the current directory. "
+"Congratulations! You have\n"
+"  successfully checked out the latest I2P sources, ready to be compiled."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:387
+msgid ""
+"If you haven't done this already, pull fresh code from the server to your"
+" local\n"
+"  Monotone repository. To accomplish this, change into the directory "
+"where\n"
+"  i2p.mtn is located and issue:\n"
+"  
              \n"
+"    
            • $ mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
+"i2p.i2p
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:398
+msgid "Now change into your i2p.i2p directory, and over there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:407
+msgid ""
+"As long as there were no errors…Congratulations! You have "
+"successfully updated to the latest I2P sources. They\n"
+"  should be ready to compile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:416
+msgid "Obtaining and deploying developers' transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:419
+msgid ""
+"As a server operator you may want to grant push access to certain "
+"developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:427
+msgid "By default the Monotone server denies all access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:433
+msgid "To grant pull access to all clients, set the following in"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:445
+msgid ""
+"No one will not be able to push code to your server without permission "
+"being explicitly granted. To grant push access:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:451
+msgid ""
+"Add the name of the user's transport key to\n"
+"$HOME/.monotone/write-permissions, such as\n"
+"
            \n"
+"    zzz-transport@mail.i2p\n"
+"    complication-transport@mail.i2p\n"
+"
            \n"
+"with one key per line."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:462
+msgid ""
+"Import the transport key(s) into your database. The procedure for "
+"importing transport keys is the same as for\n"
+"importing commit keys, which is described in the section Obtaining and deploying "
+"developers' keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:472
+msgid ""
+"A separate database should be used for your Monotone server because "
+"monotone will lock the database while it is served to others.\n"
+"  Make a copy of your development database, then start the server with:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:479
+msgid ""
+"If your key is protected with a passphrase, Monotone may request the "
+"passphrase\n"
+"  when the first client connects. You can work around this by connecting "
+"making the first client connection to your server\n"
+"  (or by clearing the password for your transport key)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:487
+msgid ""
+"For your server to be accessible for others over I2P, you will need to "
+"create a\n"
+"  server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" "
+"profile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:497
+msgid ""
+"Debian (amongst other distributions) has integrated Monotone into their\n"
+"  framework of daemons/services. Although Monotone servers can still be "
+"run\n"
+"  \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may"
+" be more straightforward."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:505
+msgid ""
+"Permissions are granted by editing the files\n"
+"  /etc/monotone/read-permissions and\n"
+"  /etc/monotone/write-permissions. You'll also need to edit\n"
+"  /etc/default/monotone to enable monotone to start at boot "
+"or to\n"
+"  customize the host, port, or database location."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
+msgid "New Developer's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
+msgid ""
+"\n"
+"So you want to start work on I2P? Great!\n"
+"Here's a quick guide to getting started\n"
+"on contributing to the website or the software, doing development or "
+"creating translations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
+#, python-format
+msgid ""
+"\n"
+"Not quite ready for coding?\n"
+"Try getting involved first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
+msgid "Basic study"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
+msgid "Getting the I2P code"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
+msgid "Building I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
+msgid "Development ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
+msgid "Making the results available"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
+msgid "Get to know us!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
+msgid "Translations"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
+msgid "Tools"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
+msgid ""
+"Basic development on the I2P router or the embedded applications uses "
+"Java as the main development language.\n"
+"If you don't have experience with Java, you can always have a look at Thinking in Java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
+#, python-format
+msgid ""
+"Study the how intro,\n"
+"the other \"how\" documents,\n"
+"the tech intro,\n"
+"and associated documents.\n"
+"These will give you a good overview of how I2P is structured and what "
+"different things it does."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
+msgid ""
+"For development on the i2p router or the embedded applications,\n"
+"get the monotone source repository installed - short instructions:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
+msgid ""
+"Install monotone.\n"
+"Monotone is a version control system.\n"
+"We use it because it allows us to keep track of who does what changes to "
+"the source code (and for a lot of complicated things, but 'keeping track "
+"of changes' is the basic idea)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
+msgid ""
+"Skim over the monotone tutorial,"
+" to make sure you understand the concepts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
+msgid ""
+"If you want to remain anonymous, you need to do an additional step, to "
+"set up a connection to a monotone server over I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
+#, python-format
+msgid ""
+"Enable the i2ptunnel client tunnel on port "
+"8998 pointing to mtn.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
+msgid ""
+"Pick a directory where you want to put all your I2P files, and create a "
+"monotone database:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
+msgid ""
+"Define the trust list by creating ~/.monotone/monotonerc (or"
+" _MTN/monotonerc in the i2p.i2p workspace) with the "
+"following contents:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
+#, python-format
+msgid ""
+"Copy and paste the developer's commit keys "
+"into a new file (e.g. keys.txt) in the same directory\n"
+"  that i2p.mtn is in. Import the keys into your database "
+"with 
                  mtn -d i2p.mtn read < keys.txt
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:76
+msgid ""
+"Pull the I2P sources to your machine. This may take a long time, "
+"especially if you are doing this over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:78
+msgid "Anonymously:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:81
+msgid "Non-anonymously:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:83
+msgid ""
+"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn"
+".i2p-projekt.de."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:90
+msgid ""
+"All the sources are now present on your machine, in the database file. To"
+" make them available in a directory, you need to check them out:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:92
+msgid ""
+"The above command creates a directory i2p.i2p, which contains all of the "
+"I2P sources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:96
+msgid "Remarks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:97
+msgid ""
+"\n"
+"To download the website files instead of the I2P source files, use "
+"'i2p.www' instead of 'i2p.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:100
+msgid ""
+"The initial pull may take several hours using the tunnel.\n"
+"If it fails after a partial pull, simply rerun it, it will start where it"
+" left off.\n"
+"If you are in a hurry, use the non-anonymous access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:105
+#, python-format
+msgid ""
+"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
+#, python-format
+msgid ""
+"A long explanation about using monotone is available on the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
+#, python-format
+msgid ""
+"To compile the code, you need the Sun Java Development Kit 6 or higher, "
+"or equivalent JDK\n"
+"(Sun JDK 6 strongly recommended) and\n"
+"Apache ant\n"
+"version 1.7.0 or higher.\n"
+"If you go are working on the main I2P code, you can go into the i2p.i2p "
+"directory and run 'ant' to see the build options."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
+msgid ""
+"To build or work on console translations, you need\n"
+"the xgettext, msgfmt, and msgmerge tools from the\n"
+"GNU gettext package."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
+#, python-format
+msgid ""
+"For development on new applications,\n"
+"see the application development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
+#, python-format
+msgid ""
+"See zzz's TODO lists,\n"
+"this website's TODO list or\n"
+"Trac\n"
+"for ideas."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
+#, python-format
+msgid ""
+"See the bottom of the licenses page "
+"for\n"
+"commit privilege requirements. You need these to put code into i2p.i2p "
+"(not required for the website!)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
+msgid "Short version of how to generate and use keys if you plan to commit:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
+msgid "use an empty passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
+msgid "enter a passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
+#, python-format
+msgid ""
+"send this to a mtn repo operator to get "
+"push privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
+#, python-format
+msgid ""
+"send this to a release manager to get "
+"commit privileges - not required for website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
+msgid "check in with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
+msgid "push with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
+#, python-format
+msgid "Long version: see the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
+#, python-format
+msgid ""
+"The developers hang around on IRC. They can be reached on the Freenode "
+"network, OFTC, and on the I2P internal networks. The usual place to look "
+"is #i2p-dev. Join the channel and say hi!\n"
+"We also have additional guidelines for regular"
+" developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
+#, python-format
+msgid ""
+"Website and router console translators: See the New Translator's Guide\n"
+"for next steps."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
+msgid ""
+"I2P is open source software that is mostly developed using open sourced\n"
+"toolkits. The I2P project recently acquired a license for the YourKit "
+"Java\n"
+"Profiler. Open source projects are eligible to receive a free license "
+"provided\n"
+"that YourKit is referenced on the project web site. Please get in touch "
+"if you\n"
+"are interested in profiling the I2P codebase."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
+#, python-format
+msgid ""
+"YourKit is kindly supporting open source projects with its full-featured "
+"Java Profiler.\n"
+"YourKit, LLC is the creator of innovative and intelligent tools for "
+"profiling\n"
+"Java and .NET applications. Take a look at YourKit's leading software "
+"products:\n"
+"YourKit Java Profiler and\n"
+"YourKit .NET Profiler."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
+msgid "New Translator's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
+msgid "Here's a very quick guide to getting started."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
+msgid "How to Translate the Website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
+#, python-format
+msgid ""
+"Translation of the website is done with .po files. The easiest way by far"
+" to\n"
+"translate the website is to sign up for an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
+msgid "Preparation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
+#, python-format
+msgid ""
+"Come to #i2p-dev on irc and talk to people.\n"
+"Claim the language -\n"
+"To make sure other coworkers don't bump onto the files you are working "
+"on,\n"
+"please update the translation status on this wiki "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"Including the installation of monotone,\n"
+"checking out i2p.www branch, and generate your own monotone keys.\n"
+"It is not required that you sign a dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
+msgid ""
+"Run \"./extract-messages.sh\" to generate a "
+"messages.pot in the base directory.\n"
+"Edit the header of this file, then run \"./init-new-po.sh "
+"locale\" to generate the file\n"
+"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
+"\"mtn add\" this file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
+msgid ""
+"Edit i2p2www/pages/global/lang.html and add a line for your "
+"language (copy an existing line)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
+msgid ""
+"Add a flag image file to i2p2www/static/images/flags/ for "
+"the menu (copy from the router)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
+msgid ""
+"Edit files:\n"
+"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
+msgid ""
+"Check in:\n"
+"\"mtn pull\", \"mtn update\". Then check in by "
+"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
+"This collects the diff info of your changed file into your local repo. "
+"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
+"i2p.i2p\".\n"
+"This synchronizes your local repo with the repo on the target machine."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
+msgid "Repeat. Check in often. Don't wait until it is perfect."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
+msgid "How to Translate the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
+#, python-format
+msgid ""
+"The easiest way by far to translate the router console is to sign up for "
+"an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"including the installation of monotone and the gettext tools,\n"
+"checking out i2p.i2p branch, and generate your own monotone keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
+msgid "Generate your own gpg key and sign the dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
+msgid ""
+"Before starting a console translation, better help translate some i2p "
+"webpages first.\n"
+"At least an i2p homepage in your language would be great."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
+msgid ""
+"What to translate:\n"
+"There are about 15 files in the i2p.i2p branch that needs translation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
+msgid ""
+"Where xx is your language code like fr/de/ch/zh/...\n"
+"There may be or may not be files with your lang code. If not, you can "
+"create your own. by copying and renaming other language files you know "
+"with your own lang code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet, copy another language "
+"file to a new file foo_xx.bar for your language.\n"
+"Then \"mtn add\" the file.\n"
+"After creating a .po file, edit the headers. Then run \"ant "
+"distclean poupdate\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
+msgid ""
+"Start to work:\n"
+"Edit the HTML files with any text editor.\n"
+"Be sure not to use an editor in HTML mode that reformats everything.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
+msgid ""
+"As you can see, it's not that difficult.\n"
+"If you have questions about the meaning of the terms in the console, ask "
+"in #i2p-dev on IRC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
+msgid "FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
+msgid ""
+"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
+"and html, etc.? Why can't I just do a translation and email it to you?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
+msgid "A: Several reasons:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
+#, python-format
+msgid ""
+"You might be interested in translating via Transifex. Request to join a "
+"translation team here."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
+msgid ""
+"We don't have anybody who has time to accept manual contributions and "
+"submit them to our source control system on your behalf. Even if we did, "
+"it doesn't scale."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
+msgid ""
+"Maybe you are thinking translation is a one-step process. It isn't. You "
+"can't do it all at once. You will make mistakes. You need to test it and "
+"tweak it to make it look right before you submit it. Developers "
+"will update or add to the English text, thus requiring a translation "
+"update."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
+msgid ""
+"Having translators use a source control system directly provides "
+"authentication and accountablility - we know who is doing what, and we "
+"can track changes, and revert them if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
+msgid ""
+".po files are not difficult. If you don't want to work directly with "
+"them, we recommend 'poedit'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
+msgid ""
+"HTML files are not difficult. Just ignore the html stuff and translate "
+"the text."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
+msgid ""
+"Installing and using monotone is not that difficult. Several of the "
+"translators and other contributors to I2P are non-programmers, and they "
+"use monotone regularly. Monotone is simply a source control system, it is"
+" not about \"coding\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
+msgid ""
+"Our items to translate are not \"documents\". They are html files and po "
+"files, with a specific format and character encoding (UTF-8) that must be"
+" maintained, and not corrupted by email programs or other methods of "
+"transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
+msgid ""
+"We looked at 'pootle' as a front-end for translators. It didn't work "
+"well, needed an administrator, and a pootle-based process would suffer "
+"from a number of the above flaws."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
+msgid ""
+"In summary:\n"
+"Yes, we know it is somewhat of a hurdle to get started. It's really the "
+"only possible way we can do it. Give it a try, it really isn't that hard."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
+msgid "More Information"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
+#, python-format
+msgid ""
+"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
+msgstr ""
+
diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/priority.po b/i2p2www/translations/pt_BR/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..0f3f8ff4
--- /dev/null
+++ b/i2p2www/translations/pt_BR/LC_MESSAGES/priority.po
@@ -0,0 +1,2544 @@
+# 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-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-11-27 02:30+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/blog/category.html:2
+msgid "Blog Category"
+msgstr ""
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr ""
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:92
+msgid "Blog"
+msgstr "Blogue"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "Feed ATOM do Blog da I2P"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr ""
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr ""
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr ""
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Pacotes da I2P no Debian"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Opção 1: Versões recentes do Ubuntu e derivados "
+"(Tente isto se você não está usando o Debian)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Adicionando o PPA via linha de comando e instalando a I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Abra um terminal e digite:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "Você já está pronto para instalar a I2P!"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "Adicionando o PPA usando o Synaptic"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the  key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "Trabalho pós-instalação"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Baixar"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Baixar I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Dependências"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Baixar e executar o arquivo."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Pacotes para Debian & Ubuntu estão disponíveis."
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+"    The latest dev build is version %(devbuild)s, and is available from\n"
+"    str4d's eepsite."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+"      are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+"      the other."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+"    or via Git from git.repo.i2p or Github.\n"
+"    
            \n"
+"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "Atualizações de lançamentos anteriores:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "Atualizações automáticas"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+"    router console "
+"allowing\n"
+"    you to download and install the new release by just clicking on that\n"
+"    link."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "Atualizações manuais"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and rename as i2pupdate.zip.\n"
+"    (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+"    resulting i2pupdate.zip to your I2P installation directory).  You do"
+" \n"
+"    NOT need to unzip that file."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+"Clique em \"Reiniciar\""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "Lançamentos anteriores"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "Seleção do espelho"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "Arquivo:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "Qualquer espelho"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations.  Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "Não encontrado"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "Erro de servidor"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "Erro de servidor 500"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "Espelhos"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "Seguro"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Linques"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "Imprenta"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "Camisetas!"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "Europa"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "EUA"
+
+#: i2p2www/pages/global/footer.html:31 i2p2www/pages/global/nav.html:133
+msgid "Donate"
+msgstr "Faça uma doação"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "Logo da I2P"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "Projeto Internet Invisível"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "Esta página foi atualizada pela última vez em %(lastupdated)s."
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr ""
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr ""
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr ""
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "Sobre"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Introdução à I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "Comparações"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "Uma visão geral das comparações"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Outras redes anônimas"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Documentação"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Índice da documentação"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Como funciona?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "Introdução amigável"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "Introdução técnica"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "Modelo de risco"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Roteamento \"garlic\""
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "Banco de dados da rede"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "Roteamento via túneis"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Criptografia"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Especificações"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "Estruturas comuns"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "Arquivos de configuração"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:56
+msgid "Datagrams"
+msgstr "Datagramas"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:88
+msgid "Plugins"
+msgstr "Extensões"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:55
+msgid "Streaming library"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "Criação de túneis"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "Atualização do software"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:60 i2p2www/pages/global/nav.html:113
+msgid "Applications"
+msgstr "Aplicações"
+
+#: i2p2www/pages/global/nav.html:62
+msgid "Supported applications"
+msgstr "Aplicações suportadas"
+
+#: i2p2www/pages/global/nav.html:63
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Protocols"
+msgstr "Protocolos"
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Protocol stack"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Transports"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:75
+msgid "Transport layer overview"
+msgstr "Uma visão geral da camada de transporte"
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Tunnels"
+msgstr "Túneis"
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Tunnel implementation"
+msgstr "Implementação de túneis"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Unidirectional tunnels"
+msgstr "Túneis unidirecionais"
+
+#: i2p2www/pages/global/nav.html:84
+msgid "Old implementation"
+msgstr "Implementação antiga"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Naming and addressbook"
+msgstr "Sistema de nomes e livro de endereços"
+
+#: i2p2www/pages/global/nav.html:91
+msgid "Team"
+msgstr "Time"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Hall of Fame"
+msgstr "Salão da Fama"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Academic papers and peer review"
+msgstr "Publicações acadêmicas e revisão por pares"
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Presentations, tutorials and articles"
+msgstr "Exposições, tutoriais e artigos"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Contact us"
+msgstr "Contacte-nos"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Help"
+msgstr "Ajuda"
+
+#: i2p2www/pages/global/nav.html:101
+msgid "FAQ"
+msgstr "Perguntas Frequentes"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "How to browse I2P"
+msgstr "Como navegar na I2P"
+
+#: i2p2www/pages/global/nav.html:103
+msgid "Glossary"
+msgstr "Glossário"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Performance"
+msgstr "Desempenho"
+
+#: i2p2www/pages/global/nav.html:105 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Fóruns"
+
+#: i2p2www/pages/global/nav.html:108
+msgid "Volunteer"
+msgstr "Voluntários"
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Get involved!"
+msgstr "Envolva-se!"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Develop"
+msgstr "Desenvolver"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Licenses"
+msgstr "Licenças"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Release signing keys"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Signed keys"
+msgstr "Chaves assinadas"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Developers keys"
+msgstr "Chaves dos desenvolvedores"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Bug tracker"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Academic research"
+msgstr "Pesquisa acadêmica"
+
+#: i2p2www/pages/global/nav.html:122
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:123
+msgid "Guides"
+msgstr "Guias"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "New developers"
+msgstr "Novos desenvolvedores"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Using an IDE with I2P"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Developer guidelines and coding style"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "New translators"
+msgstr "Novos tradutores"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Bounties"
+msgstr "Prêmios"
+
+#: i2p2www/pages/global/nav.html:134 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Encontros"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Roadmap"
+msgstr "Plano de ação"
+
+#: i2p2www/pages/global/nav.html:136
+msgid "Task list"
+msgstr "Lista de tarefas"
+
+#: i2p2www/pages/global/nav.html:139
+msgid "Language"
+msgstr "Idioma"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "I2P - Atas de encontros passados"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr ""
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
            \n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
            \n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:94
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"Free Haven's anonymity bibliography."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Contato"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like OFTC,\n"
+"  EIN and Freenode.\n"
+"  All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Lista de canais:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "I2P - Discussão geral"
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Canal de ajuda"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Listas"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Arquivo"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Servidores:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Perguntas Frequentes"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Índice"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "Meu roteador possui pouquíssimos nós ativos. Tudo bem?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "É seguro usar proxies de saída?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Quais portas a I2P usa?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "Por que a I2P está esperando por conexões na porta 32000?"
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "Acho que encontrei uma falha. Onde posso reportá-la?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "Tenho uma questão!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "Por que a I2P é tão lenta?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "Como faço para ter meu próprio eepsite?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "Alguma questão sobre as extensões Bittorrent / I2PSnark / Azureus I2P?"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "Como faço para me conectar ao IRC dentro da I2P?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "Não consigo acessar os sites comuns da Internet através da I2P."
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "Não consigo acessar endereços https:// ou ftp:// através da I2P."
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Como faço para configurar o meu navegador?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "Meu roteador está exigindo muito da CPU?!?!"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "Equívocos"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Erros e suas soluções"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "linque"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "Dialogue com os desenvolvedores via IRC em #i2p-dev"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr "O projeto I2P encontra-se em desenvolvimento."
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
            \n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "Feito."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface.  However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"with 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "O que é um \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+"    "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+"    "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+"    "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
            \n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
            \n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally.  You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance.  You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the  \n"
+"wrapper documentation."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr ""
+
diff --git a/i2p2www/translations/ro/LC_MESSAGES/comparison.po b/i2p2www/translations/ro/LC_MESSAGES/comparison.po
new file mode 100644
index 00000000..3a837f3e
--- /dev/null
+++ b/i2p2www/translations/ro/LC_MESSAGES/comparison.po
@@ -0,0 +1,872 @@
+# Romanian translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-10-26 22:39+0000\n"
+"PO-Revision-Date: 2013-11-12 14:08+0000\n"
+"Last-Translator: polearnik \n"
+"Language-Team: Romanian "
+"(http://www.transifex.com/projects/p/I2P/language/ro/)\n"
+"Plural-Forms: nplurals=3; "
+"plural=(n==1?0:(((n%100>19)||((n%100==0)&&(n!=0)))?2: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/comparison/freenet.html:2
+msgid "I2P Compared to Freenet"
+msgstr "I2P in comparatie cu Freenet"
+
+#: i2p2www/pages/site/comparison/freenet.html:8
+msgid ""
+"Freenet is a fully distributed, peer to peer anonymous publishing "
+"network, offering \n"
+"secure ways to store data, as well as some approaches attempting to "
+"address the loads\n"
+"of a flash flood.  While Freenet is designed as a distributed data store,"
+" people have\n"
+"built applications on top of it to do more generic anonymous "
+"communication, such as \n"
+"static websites and message boards."
+msgstr ""
+"Freenet este o rețea de publicare anonima distribuita pe deplin, egal la "
+"egal , oferind metode sigure de a stoca date, precum și încearcă să facă "
+"fata inundărilor de trafic. În timp ce Freenet este conceput ca un "
+"depozit de date distribuite, persoane au construit aplicații pentru a "
+"face comunicarea anonimă mai generice, cum ar fi site-uri web statice și "
+"forumuri."
+
+#: i2p2www/pages/site/comparison/freenet.html:16
+#, python-format
+msgid ""
+"Compared to I2P, Freenet offers some substantial benefits - it is a "
+"distributed data\n"
+"store, while I2P is not, allowing people to retrieve the content "
+"published by others \n"
+"even when the publisher is no longer online.  In addition, it should be "
+"able to \n"
+"distribute popular data fairly efficiently.  I2P itself does not and will"
+" not provide \n"
+"this functionality.  On the other hand, there is overlap for users who "
+"simply want to \n"
+"communicate with each other anonymously through websites, message boards,"
+" file sharing\n"
+"programs, etc.  There have also been some attempts to develop a "
+"distributed data \n"
+"store to run on top of I2P,\n"
+"(most recently a port of Tahoe-LAFS)\n"
+"but nothing is yet ready for general use."
+msgstr ""
+"Comparativ cu I2P, Freenet oferă unele avantaje substanțiale - este un "
+"depozit de date distribuite, în timp ce I2P nu este, permite oamenilor "
+"pentru a prelua conținutul publicat de către alte persoane, chiar atunci "
+"când editorul nu mai este on-line. În plus, ar trebui să fie în măsură de"
+" a distribui date populare destul de eficient. I2P în sine nu are și nu "
+"va oferi această funcționalitate. Pe de altă parte, există o suprapunere "
+"utilizatorilor care doar să comunice unul cu celălalt anonim prin "
+"intermediul site-uri, forumuri, programe de file sharing, etc asemenea, "
+"au existat câteva tentative de a elabora un magazin de date distribuite "
+"pentru a rula pe partea de sus a I2P, (cel mai recent un port de   Tahoe-LAFS ), dar nimic nu este inca gata "
+"pentru uz general."
+
+#: i2p2www/pages/site/comparison/freenet.html:29
+msgid ""
+"However, even ignoring any implementations issues, there are some "
+"concerns \n"
+"about Freenet's algorithms from both a scalability and anonymity "
+"perspective, owing \n"
+"largely to Freenet's heuristic driven routing.  The interactions of "
+"various techniques \n"
+"certainly may successfully deter various attacks, and perhaps some "
+"aspects of the \n"
+"routing algorithms will provide the hoped for scalability.  "
+"Unfortunately, not much\n"
+"analysis of the algorithms involved has resulted in positive results, but"
+" there is still\n"
+"hope.  At the very least, Freenet does provide substantial anonymity "
+"against an attacker\n"
+"who does not have the resources necessary to analyze it further."
+msgstr ""
+"Cu toate acestea, chiar și ignorând orice probleme implementării, există "
+"unele preocupări cu privire algoritmi Freenet scalabilitate și de "
+"perspectivă anonimata, datorită în mare parte la euristica Freenet "
+"condusa de rutare. Interacțiunile de diferite tehnici de siguranță pot "
+"descuraja cu succes diferite atacuri, și, probabil, unele aspecte ale "
+"algoritmilor de rutare va oferi sperat pentru scalabilitate. Din păcate, "
+"analiza nu demult a algoritmilor implicate a dus la rezultate pozitive, "
+"dar încă mai există speranță. Cel puțin, Freenet nu oferă anonimatul "
+"substanțial față de un atacator care nu are resursele necesare pentru a "
+"analiza în continuare."
+
+#: i2p2www/pages/site/comparison/index.html:2
+msgid "Comparing I2P to other projects"
+msgstr "I2P in comparatie cu alte proiecte"
+
+#: i2p2www/pages/site/comparison/index.html:4
+msgid ""
+"There are a great many other applications and projects working on "
+"anonymous \n"
+"communication and I2P has been inspired by much of their efforts.  This "
+"is not \n"
+"a comprehensive list of anonymity resources - both freehaven's \n"
+"Anonymity "
+"Bibliography\n"
+"and GNUnet's related "
+"projects\n"
+"serve that purpose well.  That said, a few systems stand out for further\n"
+"comparison. The following have individual comparison pages:"
+msgstr ""
+"Există o mulțime de alte aplicații și proiecte ce lucrează asupra "
+"comunicării anonimă și I2P a fost inspirat de o mare parte a eforturilor "
+"lor. Aceasta nu este o listă completă a resurselor de anonimat - Bibliografie "
+"Anonimatului și de GNUnet  proiecte legate de  servesc acestui scop. Asa spus, câteva "
+"sisteme se disting prin comparație continua. Următoarele pagini au "
+"comparații individuale :"
+
+#: i2p2www/pages/site/comparison/index.html:20
+#, python-format
+msgid ""
+"The following are discussed on the other "
+"networks page:"
+msgstr ""
+"Următoarele sunt discutate pe paginaalte "
+"retele: "
+
+#: i2p2www/pages/site/comparison/index.html:32
+#, python-format
+msgid ""
+"The content of this page is subject to update, discussion and dispute, "
+"and we welcome comments and additions.\n"
+"You may contribute an analysis by entering a new "
+"ticket on Trac."
+msgstr ""
+"Conținutul acestei pagini este subiectul actualizarii, discuții și "
+"dispute, și observații și completări sunt binevenite. Puteți contribui o "
+"analiză prin introducerea unui  bilet nou pe Trac "
+"."
+
+#: i2p2www/pages/site/comparison/other-networks.html:2
+msgid "I2P Compared to Other Anonymous Networks"
+msgstr "I2P Comparativ cu alte rețele anonime"
+
+#: i2p2www/pages/site/comparison/other-networks.html:5
+msgid "The following networks are discussed on this page."
+msgstr "Urmatoarele rețele sunt discutate pe aceasta pagina."
+
+#: i2p2www/pages/site/comparison/other-networks.html:16
+#, python-format
+msgid ""
+"Most of the following sections are fairly old, and may not be accurate.\n"
+"For an overview of available comparisons, see the\n"
+"main network comparisons page.\n"
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+"Cele mai multe dintre următoarele secțiuni sunt destul de vechi, și ar "
+"putea să nu fie exacte. Pentru o privire de ansamblu asupra comparații "
+"disponibile, a se vedea href=\"%(comparison)s\"> pagina principală "
+"comparații rețea . Puteți contribui o analiză prin introducerea unui"
+"  bilet nou pe Trac ."
+
+#: i2p2www/pages/site/comparison/other-networks.html:29
+#, python-format
+msgid ""
+"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
+" \n"
+"anonymizing proxies, allowing people to tunnel out through the low "
+"latency \n"
+"mix network.  Morphmix includes some very interesting collusion detection"
+" \n"
+"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
+"IP\n"
+"addresses to accomplish the same.  The two primary differences between \n"
+"these systems and I2P are related to I2P's threat model \n"
+"and their out-proxy design (as opposed to providing both sender and "
+"receiver \n"
+"anonymity).  There is source code available to both systems, but we are "
+"not aware \n"
+"of their use outside of academic environments."
+msgstr ""
+"Morphmix și Tarzan sunt ambele complet distribuite , de tip peer-to-peer "
+"rețelele de proxy-uri anonime, care permit oamenilor să tunel prin "
+"intermediul rețelei de amestec scăzut latență. Morphmix include unele "
+"algoritmi foarte interesante  de detectare a comploturilor și apărare "
+"Sybil, în timp ce Tarzan face uz de deficitul de adrese IP pentru a "
+"realiza aceasta. Cele două diferențe principale între aceste sisteme și "
+"I2P sunt legate de  modelul amenințare I2P "
+" și proiectarea lor de-proxy (spre deosebire de a oferi atât "
+"anonimare expeditorului și receptorului). Există un cod sursă disponibil "
+"pentru ambele sisteme, dar noi nu sunt constienti de utilizarea lor în "
+"afara mediilor academice."
+
+#: i2p2www/pages/site/comparison/other-networks.html:153
+#, python-format
+msgid ""
+"\n"
+"Mixminion and Mixmaster are networks to support anonymous email against a"
+" very\n"
+"powerful adversary.\n"
+"High-latency messaging applications running on top of I2P\n"
+"(for example Syndie or I2PBote)\n"
+"may perhaps prove adequate to meet the threat\n"
+"model of those adversaries, while running in parallel along side the "
+"needs of low latency users, to provide\n"
+"a significantly larger anonymity set.\n"
+"High-latency support within the I2P router itself may or may not be added"
+" in a distant future release.\n"
+"It is too early to say if I2P will meet the needs of users requiring "
+"extreme protection for email."
+msgstr ""
+"Mixminion și Mixmaster sunt rețele de suport e-mail anonim împotriva unui"
+" adversar foarte puternic. Aplicații high-latență de mesagerie care "
+"rulează pe partea de sus a I2P (de exemplu,  "
+"Syndie  sau I2PBote) se poate dovedi, probabil, suficient pentru a "
+"satisface modelul amenințarea acestor adversari, în timp ce rulează în "
+"paralel de-a lungul partea de nevoile utilizatorilor latență redusă, "
+"pentru a oferi un set de anonimat semnificativ mai mare. Suport de înaltă"
+" latență în router-ul I2P în sine poate sau nu poate fi adăugat într-un "
+"comunicat viitor îndepărtat. Este prea devreme pentru a spune dacă I2P va"
+" satisface nevoile utilizatorilor care necesită protecție extrem de "
+"e-mail."
+
+#: i2p2www/pages/site/comparison/other-networks.html:165
+msgid ""
+"As with Tor and Onion Routing, \n"
+"both Mixminion and Mixmaster take the directory based approach as well."
+msgstr ""
+"Ca și în cazul Tor și ceapa de rutare, atât Mixminion și Mixmaster ia o "
+"abordare bazată pe directorul "
+
+#: i2p2www/pages/site/comparison/other-networks.html:175
+#, python-format
+msgid ""
+"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
+"web requests,\n"
+"and as such it has a few centralized nodes (participants in the cascade) "
+"that blend\n"
+"and mix requests from clients through the sequence of nodes (the cascade)"
+" before \n"
+"proxying out onto the web.  The scope, threat model, and security is "
+"substantially \n"
+"different from I2P, but for those who don't require significant anonymity"
+" but still\n"
+"are not satisfied with an Anonymizer-like service, JAP is worth "
+"reviewing.  One\n"
+"caution to note is that anyone under the jurisdiction of the German "
+"courts may want\n"
+"to take care, as the German Federal Bureau of Criminal Investigation "
+"(FBCI) has \n"
+"successfully mounted an \n"
+"attack \n"
+"on the network.  Even though the method of this attack was later found to"
+" be illegal \n"
+"in the German courts, the fact that the data was successfully collected "
+"is the \n"
+"concern.  Courts change their minds based upon circumstance, and this is "
+"evidence that \n"
+"if a government body or intelligence agency wanted to, they could gather "
+"the data, even \n"
+"if it may be found inadmissible in some courts later)"
+msgstr ""
+"JAP ( Java Proxy Anonim ) este o rețea de cascade de amestece pentru "
+"anonimizarea cererilor de web , și , ca atare, are câteva noduri  "
+"centralizate ( participanții la cascada ), care amesteca cereri de la "
+"clienti prin secvența de noduri (cascadă ) înainte de proxy de pe web . "
+"Domeniul de aplicare , modelul de amenințare , si siguranța este "
+"substanțial diferită de I2P , dar pentru cei care nu au nevoie de "
+"anonimat semnificativ , dar încă nu sunt mulțumit cu un Anonymizer - cum "
+"ar fi serviciu , JAP este în valoare de revizuire . O remarcare de "
+"prudenta este faptul că oricine sub jurisdicția instanțelor germane ar "
+"putea dori să aibă grijă , ca Biroul Federal German de Investigații "
+"Penale ( FBCI ) a montat cu succes un  atac < /a> pe "
+"rețea . Chiar dacă metoda a acestui atac a fost ulterior dovedit a fi "
+"ilegal în instanțele germane , faptul că datele au fost colectate cu "
+"succes  . Instanțele schimba mintea lor bazate pe situație , iar acest "
+"lucru este o dovadă că în cazul în care un organism guvernamental sau "
+"agenția de informații a vrut , ar putea aduna date , chiar dacă acesta "
+"poate fi găsite inadmisibile în unele instanțe mai târziu )\n"
+
+#: i2p2www/pages/site/comparison/other-networks.html:197
+#, python-format
+msgid ""
+"Both of these systems work through the same basic \n"
+"antnet routing, providing some degree of\n"
+"anonymity based on the threat model of providing plausible deniability "
+"against a simple \n"
+"non-colluding adversary.  With the antnet routing, they first either do a"
+" random walk or a \n"
+"broadcast search to find some peer with the data or identity desired, and"
+" then use a feedback\n"
+"algorithm to optimize that found path.  This works well for applications "
+"that merely want to know \n"
+"what other people around them have to offer - \"How are y'all doing\" vs."
+" \"Hey Alice, how are you\" - \n"
+"you basically get a local cluster of nodes that can share files with and "
+"maintain some degree of \n"
+"anonymity (though you don't have much control over who is in that group "
+"of peers)."
+msgstr ""
+"Ambele din aceste sisteme funcționează prin aceeași baza  antnet  de rutare, oferind un anumit grad de "
+"anonimat bazat pe modelul amenințarea de a oferi negare plauzibilă față "
+"de un simplu adversar non-conspiră. Cu rutare antnet, ei în primul rând, "
+"fie fac o plimbare aleatoare sau o căutare difuzata a găsit unii "
+"utilizatori cu datele de identitate sau dorite, iar apoi folosiți un "
+"algoritm de feedback pentru a optimiza această cale gasita. Aceasta "
+"funcționează bine pentru aplicații care pur și simplu doresc să știe ce "
+"alți oameni din jurul lor au de oferit - \"Cum voi face\" vs \"Hei Alice,"
+" ce mai faci\" - veți obține de fapt un grup local, de noduri, care pot "
+"partaja fișiere cu și menține un anumit grad de anonimat (dacă nu aveți "
+"mai mult control asupra cine este în acel grup de colegii)."
+
+#: i2p2www/pages/site/comparison/other-networks.html:209
+msgid ""
+"However, the algorithm does not scale well at all - if the application "
+"wants to speak with a \n"
+"particular peer it ends up doing a broadcast search or random walk "
+"(though if they are lucky enough\n"
+"for that to succeed, the antnet routing should optimize that found "
+"connection).  This means that \n"
+"while these networks can work great at small scales, they are not "
+"suitable for large networks where\n"
+"someone wants to get in touch with another specific peer.  That does not "
+"mean that there is no \n"
+"value in these systems, just that their applicability is limited to "
+"situations where their \n"
+"particular issues can be addressed."
+msgstr ""
+"Cu toate acestea, algoritmul nu scaleaza de bine la toate - în cazul în "
+"care cererea vrea să vorbească cu un anumit utilizator se termină prin a "
+"face o emisiune de căutare  sau de mers aleator (deși, dacă acestea sunt "
+"suficient de norocos pentru a reuși, de rutare antnet ar trebui să "
+"optimizeze găsirea conexiunii). Acest lucru înseamnă că, în timp ce "
+"aceste rețele pot lucra bine la solzi mici, ele nu sunt potrivite pentru "
+"retele mari în cazul în care cineva vrea să intre în contact cu un alt "
+"inter pares. Asta nu înseamnă că nu există nicio valoare în aceste "
+"sisteme, doar că aplicabilitatea lor este limitată la situațiile în care "
+"problemele lor specifice pot fi abordate."
+
+#: i2p2www/pages/site/comparison/other-networks.html:220
+#, python-format
+msgid ""
+"This was a closed-source network targeted at Iranian users.\n"
+"Tor did a good writeup on what to look for in a "
+"circumvention tool.\n"
+"Suffice it to say that being closed source and publicly targeting a "
+"specific country are not good ideas.\n"
+"I2P is, of course, open source. However, that source, and our\n"
+"technical documentation, need much more review."
+msgstr ""
+"Aceasta a fost o rețea închisă-source destinata utilizatorilor iraniene. "
+"Tor a făcut o  writeup bun asupra a ceea ce să "
+"caute într-un instrument de eludare . Este suficient să spunem că "
+"este o sursa închisă și care vizează în mod public o anumită țară nu sunt"
+" idei bune. I2P este, desigur, sursă deschisă. Cu toate acestea, această "
+"sursă, și documentația noastră tehnice , are "
+"nevoie de mult mai multa revizuire."
+
+#: i2p2www/pages/site/comparison/other-networks.html:229
+msgid "Paid VPN Services"
+msgstr "Servicii VPN platite"
+
+#: i2p2www/pages/site/comparison/other-networks.html:230
+#: i2p2www/pages/site/comparison/other-networks.html:236
+#, python-format
+msgid ""
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+"Puteți contribui o analiză prin introducerea unui  "
+"bilet nou pe Trac ."
+
+#: i2p2www/pages/site/comparison/other-networks.html:235
+msgid "Others"
+msgstr "Alții"
+
+#: i2p2www/pages/site/comparison/tor.html:2
+msgid "I2P Compared to Tor"
+msgstr "I2P in comparatie cu Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:8
+#, python-format
+msgid ""
+"Tor and Onion Routing are both anonymizing proxy networks, \n"
+"allowing people to tunnel out through their low latency mix \n"
+"network. The two primary differences between Tor / \n"
+"Onion-Routing and I2P are again related to differences in \n"
+"the threat model and the out-proxy design (though Tor\n"
+"supports hidden services as well).  In addition, Tor\n"
+"takes the directory-based approach - providing a \n"
+"centralized point to manage the overall 'view' of the \n"
+"network, as well as gather and report statistics, as \n"
+"opposed to I2P's distributed network \n"
+"database and peer selection."
+msgstr ""
+"Tor și Onion Routing sunt rețele anonime  proxy, permițând oamenilor să "
+"tuneleze prin intermediul rețelei de  amestec latență scăzuta. Cele două "
+"diferențe principale între Tor/onion-routing  și I2P sunt  în legătură cu"
+" diferențele de model-amenințare și de design de-proxy (deși Tor acceptă "
+"servicii ascunse, de asemenea). În plus, Tor are abordarea directorului "
+"bazat - pe oferirea unui punct centralizat de gestionare a \"vederii\" "
+"generale a rețelei, precum și adunarea și raportarea statistici, spre "
+"deosebire de I2P distribuita  Baza de date "
+"rețea  și   selecție egal la egal ."
+
+#: i2p2www/pages/site/comparison/tor.html:22
+msgid ""
+"The I2P/Tor outproxy functionality does have a few \n"
+"substantial weaknesses against certain attackers - \n"
+"once the communication leaves the mixnet, global passive\n"
+"adversaries can more easily mount traffic analysis.  In \n"
+"addition, the outproxies have access to the cleartext \n"
+"of the data transferred in both directions, and \n"
+"outproxies are prone to abuse, along with all of the \n"
+"other security issues we've come to know and love with \n"
+"normal Internet traffic."
+msgstr ""
+"Funcționalitatea outproxy I2P/Tor are câteva puncte slabe importante "
+"împotriva unor agresori - odata comunicarea părăsește mixnet, adversarea "
+"pasiva la nivel mondial se poate mai ușor monta analiza traficului. În "
+"plus, outproxies au acces la textul datelor transferate în ambele "
+"direcții, și outproxies sunt predispuse la abuz, împreună cu toate "
+"celelalte probleme de securitate le-am venit să-l cunoastem cu trafic "
+"normal din Internet."
+
+#: i2p2www/pages/site/comparison/tor.html:34
+msgid ""
+"However, many people don't need to worry about those \n"
+"situations, as they are outside their threat model.  It\n"
+"is, also, outside I2P's (formal) functional scope (if people want\n"
+"to build outproxy functionality on top of an anonymous\n"
+"communication layer, they can).  In fact, some I2P users\n"
+"currently take advantage of Tor to outproxy."
+msgstr ""
+"Cu toate acestea, majoritatea persoanelor nu trebuie să faca griji cu "
+"privire la aceste situații, deoarece acestea sunt în afara modelului lor "
+"de amenințare. Este, de asemenea, în afara (formal) domeniul de aplicare "
+"funcțională I2P lui (în cazul în care oamenii doresc să construiască "
+"funcționalitate outproxy pe partea de sus a unui strat de comunicare "
+"anonimă, ei pot). De fapt, unii utilizatori de I2P  în prezent profita de"
+" Tor la outproxy."
+
+#: i2p2www/pages/site/comparison/tor.html:48
+msgid "Comparison of Tor and I2P Terminology"
+msgstr "Compararea cu Tor și I2P terminologie"
+
+#: i2p2www/pages/site/comparison/tor.html:49
+msgid ""
+"While Tor and I2P are similar in many ways, much of the terminology is "
+"different."
+msgstr ""
+"În timp ce Tor și I2P sunt similare în multe feluri, o mare parte din "
+"terminologie este diferita."
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Cell"
+msgstr "Celulă"
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Message"
+msgstr "Mesaj"
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Client"
+msgstr "Client"
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Router or Client"
+msgstr "Router sau Client"
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Circuit"
+msgstr "Circuit"
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Tunnel"
+msgstr "Tunel"
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "Directory"
+msgstr "Dosar"
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "NetDb"
+msgstr "NetDB"
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Directory Server"
+msgstr "Server de directoare"
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Floodfill Router"
+msgstr "Floodfill Router"
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Entry Guards"
+msgstr "Gărzile de intrare"
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Fast Peers"
+msgstr "Utilizatori rapizi"
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Entry Node"
+msgstr "Nod de intrare"
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Inproxy"
+msgstr "Inproxy"
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Exit Node"
+msgstr "Nod de ieșire "
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Outproxy"
+msgstr "Outproxy"
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Hidden Service"
+msgstr "Serviciul ascuns"
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Eepsite or Destination"
+msgstr "Eepsite sau Destinatie"
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "Hidden Service Descriptor"
+msgstr "Descriptor de serviciu ascuns"
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "LeaseSet"
+msgstr "LeaseSet"
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Introduction point"
+msgstr "Punct de introducere"
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Inbound Gateway"
+msgstr "Gateway intrare"
+
+#: i2p2www/pages/site/comparison/tor.html:65
+msgid "Node"
+msgstr "Nod"
+
+#: i2p2www/pages/site/comparison/tor.html:65
+#: i2p2www/pages/site/comparison/tor.html:67
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Router"
+msgstr "Ruter"
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "Onion Proxy"
+msgstr "Proxy ceapa"
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "I2PTunnel Client (more or less)"
+msgstr "I2PTunnel client (mai multi sau mai puțini)"
+
+#: i2p2www/pages/site/comparison/tor.html:67
+msgid "Relay"
+msgstr "Intermediere"
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "Rendezvous Point"
+msgstr "Punct de rendezvous"
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "somewhat like Inbound Gateway + Outbound Endpoint"
+msgstr "oarecum ca Gateway intrare + Endpoint ieșire"
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "Router Descriptor"
+msgstr "Descriptor ruter"
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "RouterInfo"
+msgstr "RouterInfo"
+
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Server"
+msgstr "Server"
+
+#: i2p2www/pages/site/comparison/tor.html:73
+msgid "Benefits of Tor over I2P"
+msgstr "Beneficiile Tor peste I2P"
+
+#: i2p2www/pages/site/comparison/tor.html:76
+msgid ""
+"Much bigger user base; much more visibility in the academic and hacker "
+"communities; benefits from\n"
+"formal studies of anonymity, resistance, and performance;\n"
+"has a non-anonymous, visible, university-based leader"
+msgstr ""
+"Baza mult mai mare de utilizatori; vizibilitate mult mai multa în "
+"comunitățile academice și hacker, beneficiaza de studii formale de "
+"anonimat, rezistenta, și de performanță,  vizibila, liderul non-anonim "
+"universitate pe baza de"
+
+#: i2p2www/pages/site/comparison/tor.html:82
+msgid "Has already solved some scaling issues I2P has yet to address"
+msgstr ""
+"S-au rezolvat deja unele probleme de scalare I2P a fost încă pentru "
+"adresare"
+
+#: i2p2www/pages/site/comparison/tor.html:83
+msgid "Has significant funding"
+msgstr "Are fonduri semnificative"
+
+#: i2p2www/pages/site/comparison/tor.html:84
+msgid "Has more developers, including several that are funded"
+msgstr "Are mai multe dezvoltatori, inclusiv câteva care sunt finanțate"
+
+#: i2p2www/pages/site/comparison/tor.html:86
+msgid ""
+"More resistant to state-level blocking due to TLS transport layer and "
+"bridges\n"
+"(I2P has proposals for \"full restricted routes\" but these are not yet "
+"implemented)"
+msgstr ""
+"Mai rezistent la blocarea din cauza stratului transport TLS  și poduri "
+"(I2P are propuneri pentru \"rute restricționate complete\", dar acestea "
+"încă nu sunt puse în aplicare )"
+
+#: i2p2www/pages/site/comparison/tor.html:91
+msgid "Big enough that it has had to adapt to blocking and DOS attempts"
+msgstr ""
+"Suficient de mare pentru că a trebuit să se adapteze la blocarea și DOS "
+"încercări"
+
+#: i2p2www/pages/site/comparison/tor.html:92
+msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
+msgstr ""
+"Concepute și optimizate pentru traficul de ieșire, cu un număr mare de "
+"noduri de ieșire"
+
+#: i2p2www/pages/site/comparison/tor.html:94
+msgid ""
+"Better documentation, has formal papers and specifications,\n"
+"better website, many more translations"
+msgstr ""
+"Documentația mai bună, are acte oficiale și specificațiile, site-ul mai "
+"bun, mult mai multe traduceri"
+
+#: i2p2www/pages/site/comparison/tor.html:99
+msgid "More efficient with memory usage"
+msgstr "Mai eficienta utilizarea memoriei"
+
+#: i2p2www/pages/site/comparison/tor.html:100
+msgid "Tor client nodes have very low bandwidth overhead"
+msgstr "Nodurile client Tor au foarte putin trafic overhead"
+
+#: i2p2www/pages/site/comparison/tor.html:102
+msgid ""
+"Centralized control reduces the complexity at each\n"
+"node and can efficiently address Sybil attacks"
+msgstr ""
+"Control centralizat reduce complexitatea de la fiecare nod și poate "
+"răspunde în mod eficient atacuri Sybil"
+
+#: i2p2www/pages/site/comparison/tor.html:108
+msgid ""
+"A core of high capacity nodes provides higher\n"
+"throughput and lower latency"
+msgstr ""
+"O bază de noduri de mare capacitate oferă transfer mai mare și latență "
+"mai mică"
+
+#: i2p2www/pages/site/comparison/tor.html:113
+msgid "C, not Java (ewww)"
+msgstr "C, nu este Java (ewww)"
+
+#: i2p2www/pages/site/comparison/tor.html:116
+msgid "Benefits of I2P over Tor"
+msgstr "Beneficiile I2P peste Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:118
+msgid ""
+"Designed and optimized for hidden services, which are much faster than in"
+" Tor"
+msgstr ""
+"Concepute și optimizate pentru serviciile ascunse, care sunt mult mai "
+"rapide decât în Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:119
+msgid "Fully distributed and self organizing"
+msgstr "Complet distribuit și de auto organizare"
+
+#: i2p2www/pages/site/comparison/tor.html:121
+msgid ""
+"Peers are selected by continuously profiling and ranking performance,\n"
+"rather than trusting claimed capacity"
+msgstr ""
+"Colegii sunt selectate de către profilare continua  si clasament de "
+"performanță, mai degrabă decât încredere în capacitatea de a pretins"
+
+#: i2p2www/pages/site/comparison/tor.html:127
+msgid ""
+"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
+"rather than hardcoded"
+msgstr ""
+"Colegii Floodfill (\"serverele director\") sunt diferiti și nu sunt de "
+"încredere, mai degrabă decât codate"
+
+#: i2p2www/pages/site/comparison/tor.html:132
+msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
+msgstr ""
+"Suficient de mici pentru că sa nu fie blocati sau administrati demult, "
+"sau  deloc"
+
+#: i2p2www/pages/site/comparison/tor.html:133
+msgid "Peer-to-peer friendly"
+msgstr "Peer-to-peer prietenos"
+
+#: i2p2www/pages/site/comparison/tor.html:134
+msgid "Packet switched instead of circuit switched"
+msgstr "Comutarea pachetelor în loc de comutarea circuitelor"
+
+#: i2p2www/pages/site/comparison/tor.html:137
+msgid ""
+"implicit transparent load balancing of messages \n"
+"across multiple peers, rather than a single path"
+msgstr ""
+"balansare incarcarii implicita si  transparentă a mesajelor pe mai multe "
+"colegii, mai des decât o singură cale"
+
+#: i2p2www/pages/site/comparison/tor.html:143
+msgid ""
+"resilience vs. failures by running multiple \n"
+"tunnels in parallel, plus rotating tunnels"
+msgstr ""
+"rezistența vs eșecurile prin rularea mai multor tuneluri în paralel, plus"
+"  tuneluri rotative"
+
+#: i2p2www/pages/site/comparison/tor.html:149
+msgid ""
+"scale each client's connections at O(1) instead \n"
+"of O(N) (Alice has e.g. 2 inbound tunnels that are \n"
+"used by all of the peers Alice is talking with, \n"
+"rather than a circuit for each)"
+msgstr ""
+"scala conexiuni ale fiecărui client la O (1) în loc de O (N) (Alice de  "
+"exemplu are 2 tuneluri de intrare care sunt utilizate de către toti  "
+"colegi cu care Alice converseaza , mai degrabă decât un circuit pentru "
+"fiecare)"
+
+#: i2p2www/pages/site/comparison/tor.html:159
+msgid ""
+"Unidirectional tunnels instead of bidirectional\n"
+"circuits, doubling the number of nodes a peer has to\n"
+"compromise to get the same information."
+msgstr ""
+"Tuneluri unidirecționale în loc de circuite bidirecționale, dublarea "
+"numărului de noduri colegilor trebuie să facă un compromis pentru a "
+"obține aceleași informații."
+
+#: i2p2www/pages/site/comparison/tor.html:166
+msgid ""
+"Protection against detecting client activity, even\n"
+"when an attacker is participating in the tunnel, as\n"
+"tunnels are used for more than simply passing end \n"
+"to end messages (e.g. netDb, tunnel management, \n"
+"tunnel testing)"
+msgstr ""
+"Protecția împotriva detectarii de activitate clientului, chiar și atunci "
+"când un atacator participă la tunel, așa cum tuneluri sunt folosite "
+"pentru mai multe decât pur și simplu trecerea intr-un capăt mesaje finali"
+" (de exemplu netDb, managementul tunel, tunel"
+
+#: i2p2www/pages/site/comparison/tor.html:175
+msgid ""
+"Tunnels in I2P are short lived, decreasing the number\n"
+"of samples that an attacker can use to mount an \n"
+"active attack with, unlike circuits in Tor, which are\n"
+"typically long lived."
+msgstr ""
+"Tunelurile din I2P sunt de scurtă durată, scăderea numărului de probe "
+"care un atacator poate folosi pentru a monta un atac activ , spre "
+"deosebire de circuite din Tor, care de obicei au viata lunga."
+
+#: i2p2www/pages/site/comparison/tor.html:183
+msgid ""
+"I2P APIs are designed specifically for anonymity and\n"
+"security, while SOCKS is designed for functionality."
+msgstr ""
+"I2P API-uri sunt proiectate special pentru anonimatul și securitate, în "
+"timp ce SOCKS este proiectat pentru funcționalitate."
+
+#: i2p2www/pages/site/comparison/tor.html:188
+msgid "Essentially all peers participate in routing for others"
+msgstr "În esență, toți colegii participa la rutare pentru alții"
+
+#: i2p2www/pages/site/comparison/tor.html:190
+msgid ""
+"The bandwidth overhead of being a full peer is low, \n"
+"while in Tor, while client nodes don't require much\n"
+"bandwidth, they don't fully participate in the mixnet."
+msgstr ""
+"Overhead de bandă a utilizatorului este scăzut, decit în Tor, în timp ce "
+"nodurile client nu necesită mai mult de lățime de bandă, ele nu participă"
+" pe deplin la mixnet."
+
+#: i2p2www/pages/site/comparison/tor.html:196
+msgid "Integrated automatic update mechanism"
+msgstr "Mecanism integrat de actualizare automată"
+
+#: i2p2www/pages/site/comparison/tor.html:197
+msgid "Both TCP and UDP transports"
+msgstr "Atât TCP cit și UDP transporturi"
+
+#: i2p2www/pages/site/comparison/tor.html:198
+msgid "Java, not C (ewww)"
+msgstr "Java nu e C (ewww)"
+
+#: i2p2www/pages/site/comparison/tor.html:201
+msgid "Other potential benefits of I2P but not yet implemented"
+msgstr "Alte beneficii ale I2P dar neimplementate încă"
+
+#: i2p2www/pages/site/comparison/tor.html:202
+msgid "...and may never be implemented, so don't count on them!"
+msgstr "... și  posibil sa nu fie puse în aplicare, astfel încât nu conta pe ei!"
+
+#: i2p2www/pages/site/comparison/tor.html:205
+msgid ""
+"Defense vs. message count analysis by garlic wrapping \n"
+"multiple messages"
+msgstr ""
+"Apărare vs analiza numărului de mesaje de ambalaj usturoi invelite mai "
+"multe mesaje"
+
+#: i2p2www/pages/site/comparison/tor.html:211
+msgid ""
+"Defense vs. long term intersection by adding delays \n"
+"at various hops (where the delays are not discernible\n"
+"by other hops)"
+msgstr ""
+"Apărare vs intersecție pe termen lung prin adăugarea de întârzieri la "
+"diferite hamei (în cazul în care întârzierile nu sunt perceptibile prin "
+"alte hamei)"
+
+#: i2p2www/pages/site/comparison/tor.html:218
+msgid ""
+"Various mixing strategies at the tunnel level (e.g.\n"
+"create a tunnel that will handle 500 messages / minute,\n"
+"where the endpoint will inject dummy messages if there\n"
+"are insufficient messages, etc)"
+msgstr ""
+"Diverse strategii de amestecare la nivel tunel (de exemplu, a crea un "
+"tunel care se va ocupa 500 de mesaje / minut, în cazul în care obiectivul"
+" va injecta mesaje false dacă există mesaje insuficiente, etc)"
+
diff --git a/i2p2www/translations/ro/LC_MESSAGES/priority.po b/i2p2www/translations/ro/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..d6b980c5
--- /dev/null
+++ b/i2p2www/translations/ro/LC_MESSAGES/priority.po
@@ -0,0 +1,3319 @@
+# Romanian translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Admin , 2013
+# oper2 , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-12-05 12:53+0000\n"
+"Last-Translator: polearnik \n"
+"Language-Team: Romanian "
+"(http://www.transifex.com/projects/p/I2P/language/ro/)\n"
+"Plural-Forms: nplurals=3; "
+"plural=(n==1?0:(((n%100>19)||((n%100==0)&&(n!=0)))?2: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/blog/category.html:2
+msgid "Blog Category"
+msgstr "Categorie blog"
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr ""
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:92
+msgid "Blog"
+msgstr "Blog"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "I2P Blog ATOM Feed"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr "Postat %(date)s de %(author)s "
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "Mai multe posturi-blog …"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr "Postat:"
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "Autor:"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Pachet I2P Debian"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+"Pachetele Debian au fost testate și  ar trebui  sa lucreze pe "
+"platforme x86/x86_64:"
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr "Ubuntu (exact 12.04 si mai nou)"
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+"Debian Linux (Squeeze si mai recent) & "
+"kFreeBSD"
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+"Pachetele I2P pot sa lucreze si pe sisteme ce nu sunt enumerate "
+"mai sus.Vă rugăm să raportați orice probleme cu aceste pachete peTracpe\n"
+"https://%(trac)s."
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Optiune 1:Versiunile recente Ubuntu si derivatii "
+"ei (Incercati daca nu folositi Debian)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr "Optiune 2: Debian (inclusiv Debian-derivati)"
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+"Instructii pentru Ubuntu Precise Pangolin( si mai nou) si derivatii de "
+"tip Linux Mint"
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Adaugati PPA prin linia de comanda si instalati I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Deschideti terminal si introduceti:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"Această comandă va adăuga PPA la / etc / apt / sources.list.d și adu\n"
+"cheia GPG cu care depozitul a fost semnat . Cheia GPG asigură\n"
+"că pachetele nu au fost falsificate de cand au fost construite."
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "Anunta managerul de pachete despre nout PPA prin introducerea:"
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+"Această comandă va prelua cea mai recentă listă a software-ului de la "
+"fiecare\n"
+"depozit, care este activat pe sistemul dumneavoastră, inclusiv I2P PPA "
+"care\n"
+"se adaugă cu comanda anterioară."
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "Acum sunteți gata să instalați I2P!"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "Adăugarea PPA Folosind Synaptic"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+"Deshideti Synaptic (Sistem -> Administrarea -> managerul de pachete"
+" Synaptic )."
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+"După ce se deschide Synaptic, selectați  Depozitele  din meniu"
+"  Setări ."
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"clic pe fila alte surse si clic Adauga Lipeste "
+"ppa:i2p-maintainers/i2p in cimp APT-linie si clicAdauga "
+"sursaclic pe butonul Inchide mai apoi restartati."
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+"In caseta filtru rapid, tapati in i2p si apasati "
+"enter.Cindi2p returnat în lista de rezultate, faceți clic "
+"dreapta i2p si selectatiMarcheaza pentru instalare."
+" Dupa aceasta puteti vedea pop-up cu textul: Marcheaza modificările "
+"necesare suplimentare? Dacă este așa clic Marcheaza apoi "
+"Aplica."
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+"După ce procesul de instalare se încheie puteți trece la\n"
+"următoarea parte din start I2P și "
+"configurarea-l pentru sistemul dvs.."
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr "Instrucțiuni pentru Debian"
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+"Note:Pașii de mai jos ar trebui să fie efectuate cu acces root (de "
+"exemplu, de comutare\n"
+"utilizatorului la root cu \"su\" sau prin prefixarea fiecare comandă cu "
+"\"sudo\")."
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr "Adauga linii, cum ar fi cele ce urmează la %(fisier) s ."
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the  key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+"Descărcați  cheia utilizată pentru a semna "
+"depozit  și adăugați-l în apt:"
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr "Anunta managerul de pachete despre depozit nou prin introducerea"
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+"Această comandă va prelua cea mai recentă listă a software-ului de la "
+"fiecare\n"
+"depozit, care este activat pe sistemul dumneavoastră, inclusiv I2P "
+"depozit \n"
+"adăugat in pasul 1."
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+"Acum sunteți gata să instalați I2P! Instalarea  I2P-keyring  pachetul va asigura că veți primi actualizări la cheie GPG "
+"depozitului."
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+"După ce procesul de instalare se încheie puteți trece la următoarea parte"
+" din start I2P și configurarea pentru "
+"sistemul dvs.."
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "Actiunile dupa instalare"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+"Folosind aceste pachete I2P router I2P poate fi pornit în următoarele\n"
+"trei moduri:"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+""la cerere" folositi i2prouter script. Porniti "
+""i2prouter\n"
+"start" din linia de comanda. (Note:  "
+"nu folositi\n"
+"sudo sau porniti de la root!)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""la cerere" fără java service wrapper\n"
+"(necesare pe sisteme non-Linux/non-x86 ) prin rularea \"i2prouter-"
+"nowrapper\".\n"
+"(Nota:  Nu\n"
+"folositi sudo sau porniti-l de la  root!)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"ca un serviciu care ruleaza automat la incarcarea sistemului, chiar\n"
+"înainte de a vă autentifica. Serviciul poate fi activat cu \" dpkg-"
+"reconfigure\n"
+"I2P  \"ca root sau utilizind sudo. Acesta este mijlocul "
+"recomandat de funcționare."
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+"Când instalați pentru prima dată, vă rugăm să nu uitați setati "
+"NAT/firewall daca puteti.Porturile pentru inaintare pot fi gasite "
+"în pagina de configurare a "
+"rețeleidin consola router.Dacă este nevoie de îndrumare în ceea ce "
+"privește porturile de inaintare,ajutorul puteți găsi la portforward.com"
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"Rugam sa examinati si  adaptati setările de lățime de bandăpe \n"
+"pagina de configurare \n"
+"deoarece setări implicite de 96 KB / s download / 40 KB / upload sunt "
+"destul de conservatoare"
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"Dacă doriți să ajungă la eepsites prin intermediul browser-ul "
+"dvs.,aruncati o privire pe pagina configurarea proxy browser-ului pentru un "
+"ghid simplu"
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Descarca"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Descarcă I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Dependență"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+"Java Runtime 1.5 sau mai recent. (Oracle Java "
+"Versiunea 7, OpenJDK 7, or IcedTea7 recomendat, exceptind Raspberry Pi: Oracle 8 Early Access, PowerPC: IBM SDK 7) 
             Determinați versiunea de Java instalata aici "
+"sau tapati java -version in terminal "
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "Instalarea curata"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr "selectați link-ul alternativ"
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Descărca acest fișier și rulați-l."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Descărca acest fișier și dublu-clic (în cazul în care funcționează) sau\n"
+"tapati java -jar i2pinstall_%(i2pversion)s.jarin terminal "
+"pentru a porni instalator.\n"
+"Ați putea să faceți clic dreapta și selectați\n"
+""deschide cu Java"."
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "Instalare prin linie de comandă (headless) :"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Descarcă %(i2pversion)s OSX  fișierul de instalare grafica de mai sus si\n"
+"porneste java -jar i2pinstall_%(i2pversion)s.jar -console in"
+" linie de comanda."
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Descărca acest fișier și dublu-clic (în cazul în care funcționează) sau\n"
+"tapati java -jar i2pinstall_%(i2pversion)s.jarin terminal "
+"pentru a porni instalator.\n"
+"Ați putea să faceți clic dreapta și selectați\n"
+""deschide cu Java"."
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Descarcă fișierul de instalare grafica de mai sus si\n"
+"porneste java -jar i2pinstall_%(i2pversion)s.jar -console in"
+" linie de comanda."
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Sunt disponbile pachete pentru Debian &Ubuntu"
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+"    The latest dev build is version %(devbuild)s, and is available from\n"
+"    str4d's eepsite."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+"      are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+"      the other."
+msgstr ""
+"Release-ul și dev versiuni ale I2P APK nu sunt compatibile, deoarece\n"
+"       sunt semnate de către zzz și str4d respectiv. Dezinstalati-le "
+"înainte de a instala\n"
+"      celălalt."
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "sursă pachete"
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+"    or via Git from git.repo.i2p or Github.\n"
+"    
            \n"
+"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+"Alternativ, puteți descărca sursă din monotone\n"
+"    sau prin Git din git.repo.i2p sau Github.\n"
+"    
            \n"
+"    Porniti (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) atunci \n"
+"     rulati programul de instalare GUI sau de instalare fără cap ca mai "
+"sus"
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Fișierele sunt semnate de către zzz,\n"
+" al cărui cheie este aici."
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"I2P poate fi descărcat de pe paginile noastre proiectului pe Launchpad si Google Code."
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"După rularea instalarii pe Windows, pur și simplu faceți clic pe butonul "
+"\"Start I2P\"\n"
+"care va aduce la a href=\"http://localhost:7657/index.jsp\">consola "
+"router,\n"
+"unde gasiti instrucțiuni suplimentare."
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"Pe sistemele Unix, I2P poate fi pornit ca un serviciu\n"
+"folosind scriptul \"i2prouter\", situat în directorul selectat pentru "
+"I2P.\n"
+"Treceti in aceasta mapa în consolă și comanda \"sh stare i2prouter\"\n"
+"ar trebui să vă spuna statutul a router-ului. Argumentele \"start\", "
+"\"stop\" și \"restart\"\n"
+"controleaza serviciu. consola"
+" router \n"
+"poate fi accesat prin metoda obisnuita\n"
+"Pentru utilizatorii de OpenSolaris și alte  sisteme pentru care nu este "
+"acceptat wrapper (i2psvc),\n"
+"startati router-ul cu comanda \"sh runplain.sh\"."
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"Când instalați pentru prima dată, vă rugăm să nu uitați să adaptati  "
+"NAT / firewall \n"
+"dacă reusiti, ținând cont de porturile Internet-pe  care le utilizeaza "
+"I2P,\n"
+"descris aici printre alte porturi.\n"
+"Dacă ați deschis cu succes portul de intrare TCP, permiteti, de asemenea,"
+" TCP intrare pe\n"
+"pagina de configurare."
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"Rugam sa examinati si  adaptati setările de lățime de bandăpe \n"
+"pagina de configurare \n"
+"deoarece setări implicite de 96 KB / s download / 40 KB / upload sunt "
+"destul de lente"
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "Actualizare de la versiunile anterioare:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr "Ambele upgrade-uri automate și manuale sunt disponibile pentru release."
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "Actualizări automate"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+"Dacă se execută 0.7.5 sau mai noi, router-ul ar trebui să detecteze\n"
+"noua versiune. Pentru a face upgrade pur și simplu faceți clic pe butonul"
+" \"Actualizare Descarca\" pe consola router\n"
+"atunci când apare."
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"Din cauza unui bug în versiune 0.7.6, cele ale caror prima I2P instalare "
+"a fost aceasta versiunea\n"
+"și nu au actualizat manual\n"
+"se poate obține o eroare \"versiune descărcat nu este mai mare decât "
+"versiunea curentă\" ,\n"
+"și ar trebui să folosească metoda de actualizarea manuală de mai jos."
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Dacă se execută 0.7.4 sau anterioară, vă rugăm să consultați 0.7.5 note de publicare pentru informații "
+"importante despre modul de configurare a router-ul pentru primire "
+"automata a publicarii."
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Dacă se execută 0.6.1.30 sau anterioară, vă rugăm să consultați instructiuni pentru informații importante "
+"despre modul de configurare a router-ul pentru primire automata a "
+"publicarii."
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+"    router console "
+"allowing\n"
+"    you to download and install the new release by just clicking on that\n"
+"    link."
+msgstr ""
+"Dacă ați reconfigurat router-ul ca urmarind instructiunilear trebui să vedeți un link "
+"pe dvs.\n"
+"consola "
+"routerpermițând     să descărcați și să instalați noua versiune de "
+"doar clic pe acel     link."
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr ""
+"Alternativ, aveți posibilitatea să utilizați metoda manuală specificate "
+"mai jos."
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "Actualizările manuale"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and rename as i2pupdate.zip.\n"
+"    (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+"    resulting i2pupdate.zip to your I2P installation directory).  You do"
+" \n"
+"    NOT need to unzip that file."
+msgstr ""
+"Descărca acest fișier pentru I2P dvs. in mapa de instalare "
+"șiredenumiti ca i2pupdate.zip\n"
+"(Alternativ, puteți obține sursa ca mai sus și a porni \"ant Updater\", "
+"apoi copiați  i2pupdate.zip la directorul de instalare I2P). NU este "
+"nevoie pentru a dezarhiva acest fișier."
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+"Faceti clic pe \"Restart\""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "Serviti o ceașcă cu cafea și reveniti înapoi în 11 minute"
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Fișierul este semnat de către zzz,\n"
+" al cărui cheie este aici."
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "Versiune precedent"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"Versiune anterioara este disponibila  Google "
+"Code\n"
+"si pe Launchpad\n"
+"si in retea i2p %(echelon)s."
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "Alegerea serverului alternativ"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "Fişier:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "Orice server alternativ"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+"Pentru a pretinde recompense autorul nu trebuie să fie plătit de către "
+"alte organizații\n"
+"sau echipe pentru acest lucru (de exemplu, elevi GSoC nu sunt valabile)."
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations.  Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"Sumele de recompense poate fi majorat prin donatii suplimentare.\n"
+"Credeti ca este important?Adauga in donatia ta"
+"\n"
+"alegeti suma pentru recompense %(donatename)s"
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "Nu s-a găsit"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+"Da ... resursa, le cautati, este numită în mod diferit, nu există sau a "
+"fost eliminata."
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "Eroare server"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "500 Eroare server"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "Hmm ... Serverul a întâlnit ceva greutăți."
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "Servere alternative"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "Sigur"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "Diverse"
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Linkuri"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "Impressum"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "Tricouri!"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "Europa"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "SUA"
+
+#: i2p2www/pages/global/footer.html:31 i2p2www/pages/global/nav.html:133
+msgid "Donate"
+msgstr "Donează"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr "Treci peste navigare"
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "Logo I2P "
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "Proiectul Internet Invizibil"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+"Această pagină a fost actualizat ultima dată în %(lastupdated)s și este "
+"corecta pentru versiunea %(accuratefor)s."
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "Această pagină a fost actualizat ultima dată în %(lastupdated)s ."
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "Această pagină este corecta pentru versiunea router %(accuratefor)s."
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr "înapoi"
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr "Înainte"
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr "Postat în"
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "Despre"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Introducere în I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "Comparații"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "Prezentare generală a comparațiilor"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Alte rețele anonime"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Documentație"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Pagina de start a documentației"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Cum functioneaza?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "Gentle introducere "
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "tehnologie introducere"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "Modelul pericolului"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Rutare de usturoi "
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "Baza de date rețelei"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "rutare tunelurilor"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "Selecție utilizatorului"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Criptografie"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Specificații"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "Blockfile"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "Structuri comune"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "Fișiere de configurare"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:56
+msgid "Datagrams"
+msgstr "Datagramele"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr "Fișiere GeoIP"
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:88
+msgid "Plugins"
+msgstr "Module"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:55
+msgid "Streaming library"
+msgstr "biblioteca Streaming"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "Crearea tunelului"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "Mesajele tunelului"
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "Actualizări software"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:60 i2p2www/pages/global/nav.html:113
+msgid "Applications"
+msgstr "Aplicații"
+
+#: i2p2www/pages/global/nav.html:62
+msgid "Supported applications"
+msgstr "Aplicații acceptate"
+
+#: i2p2www/pages/global/nav.html:63
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Protocols"
+msgstr "Protocoale"
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Protocol stack"
+msgstr "Stiva de protocoale"
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Transports"
+msgstr "Transporturi"
+
+#: i2p2www/pages/global/nav.html:75
+msgid "Transport layer overview"
+msgstr "Prezentare generală stratului de transport"
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Tunnels"
+msgstr "Tuneluri"
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Tunnel implementation"
+msgstr "Implementarea tunel"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Unidirectional tunnels"
+msgstr "Tuneluri unidirecționale"
+
+#: i2p2www/pages/global/nav.html:84
+msgid "Old implementation"
+msgstr "Implementare veche"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Naming and addressbook"
+msgstr "Denumirea și Agenda"
+
+#: i2p2www/pages/global/nav.html:91
+msgid "Team"
+msgstr "Echipa"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Hall of Fame"
+msgstr "Sala de faimă"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Academic papers and peer review"
+msgstr "Lucrări academice și evaluarea utilizatorilor"
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Presentations, tutorials and articles"
+msgstr "Prezentări, tutoriale și articole"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Contact us"
+msgstr "Contactează-ne"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Help"
+msgstr "Ajutor"
+
+#: i2p2www/pages/global/nav.html:101
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "How to browse I2P"
+msgstr "Cum de a naviga I2P"
+
+#: i2p2www/pages/global/nav.html:103
+msgid "Glossary"
+msgstr "Glosar"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Performance"
+msgstr "Performanță"
+
+#: i2p2www/pages/global/nav.html:105 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Forumuri"
+
+#: i2p2www/pages/global/nav.html:108
+msgid "Volunteer"
+msgstr "Voluntar"
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Get involved!"
+msgstr "Implicaţi-vă!"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Develop"
+msgstr "Developează"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Licenses"
+msgstr "Licențe"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Release signing keys"
+msgstr "Eliberarea cheilor de semnare"
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Signed keys"
+msgstr "Chei semnate"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Developers keys"
+msgstr "Cheile dezvoltatorilor"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Bug tracker"
+msgstr "Bug tracker"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Academic research"
+msgstr "Cercetare academică"
+
+#: i2p2www/pages/global/nav.html:122
+msgid "Open research questions"
+msgstr "întrebări de cercetare deschise"
+
+#: i2p2www/pages/global/nav.html:123
+msgid "Guides"
+msgstr "Ghiduri"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "New developers"
+msgstr "Dezvoltatorii noi"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Using an IDE with I2P"
+msgstr "Folosiți un IDE cu I2P"
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Developer guidelines and coding style"
+msgstr "Ghidul dezvoltatorului și stilul de programare"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "New translators"
+msgstr "Noi traducători"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Bounties"
+msgstr "Recompensele"
+
+#: i2p2www/pages/global/nav.html:134 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Ședințe"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Roadmap"
+msgstr "Foaia de parcurs"
+
+#: i2p2www/pages/global/nav.html:136
+msgid "Task list"
+msgstr "Listă de sarcini"
+
+#: i2p2www/pages/global/nav.html:139
+msgid "Language"
+msgstr "Limba"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "Jurnalele întâlnirilor I2P trecute"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr ""
+"Ședințele sunt în prezent în așteptare până la alegerea datei mai "
+"potrivite."
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"Dacă aveți ceva de discutat, puteți să găsiți dezvoltatorii  pe canalul "
+"IRC în #i2p-dev.\n"
+"Actualizări de stare sunt disponibile de la"
+" dezvoltatori"
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr "Intilnirea de dezvoltare a I2P %(id)s"
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr "IRC jurnal complet"
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "După subiect"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "după dată"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "De autor"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
            \n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
            \n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+"Vă rugăm să trimiteți intrări noi sau corectate la\n"
+"%(email)s.
            \n"
+"Dacă se poate, vă rugăm să formatați-le ca BibTeX; vezi\n"
+"Pagina sursă BibTeX pentru exemple.
            \n"
+"Nu uitați să includeți URL-uri, dacă este posibil\n"
+"lucrări offline, sunt mai puțin utile."
+
+#: i2p2www/pages/papers/list.html:94
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"Free Haven's anonymity bibliography."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Contact"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr "Email"
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like OFTC,\n"
+"  EIN and Freenode.\n"
+"  All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+"Rețeaua noastră principala de IRC este rețeaua Irc2P în I2P, un tunel "
+"implicit pentru această rețea este configurat cu instalarea noua a "
+"router-ului.    Suntem, de asemenea, prezenți în mai multe rețele "
+"standard, cum ar fiOFTC, EINsiFreenode. Toate canalele I2P legate "
+"privire la toate aceste rețele sunt legate de principalele canale pe "
+"Irc2P prin intermediul roboții releu."
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Listă de canale"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "Discuții generale I2P "
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "Offtopic"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "Convorbiri despre dezvoltare"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Canal pentru  ajutor"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"Majoritatea discutiilor despre dezvoltarea I2P se intimpla pe I2P forumul dezvoltatorilor.Acesta este, de "
+"obicei, cel mai bun loc pentru a începe cu întrebări, dacă canalul dev "
+"IRC este inactiv."
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "Liste de discuții"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+"I2P are o listă de corespondență, dar este foarte rar folosit deaoarece "
+"echipa mica de dezvoltatori preferă să comunice prin IRC sau forum. Acest"
+" lucru se poate schimba în viitor."
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "Abonează"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+"Pentru a vă abona la o listă de corespondență, mergeți la pagina de "
+"informații lista (legate de mai jos) și completați formularul.Pot fi "
+"utilizate adrese de e-mail I2P-interne (foobar@mail.i2p) ."
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "Dezabonează"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+"Pentru a vă dezabona de la o listă de corespondență sau modifica "
+"opțiunile de abonament, du-te la pagina de informații lista (legate de "
+"mai jos) și introduceți adresa dumneavoastră de abonare."
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Liste"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Arhivă"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+"Discutie I2P generala- ceva care nu se încadrează într-o altă listă merge"
+" aici."
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+"Nu-ți place listele de discuții? Atunci acest lucru este pentru tine. "
+"Toate listele de discuții sunt de asemenea disponibile prin NNTP."
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Servere:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Întrebări frecvente"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Index"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "General"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "Pe ce sisteme va rula I2P ?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+"Ce este un \"eepsite\" și cum pot configura browser-ul meu, pentru ca "
+"sa-l pot folosi ?"
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "Router-ul meu are foarte puține colegii activi, e bine?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr "Ce înseamnă în consola router numere active x/y  ?"
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+"Colegii mei activi / colegii cunoscuți / tunele / conexiuni / lățime de "
+"bandă participante variaza foarte mult ! Este ceva în neregulă?"
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "Folosirea unui outproxy este sigur?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr "Cele mai multe dintre eepsites în I2P nu sunt disponibile?"
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Ce porturi folosește I2P?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "De ce I2P ascultă pentru conexiuni pe portul 32000?"
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "Cred că am găsit un bug, unde pot raporta?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr "Ce sa întâmplat cu *. I2p.net? Ce sa întâmplat cu jrandom? Este I2P mort?"
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "Am o intrebare!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr "Configurare"
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+"Router-ul meu a fost pornit pentru câteva minute și are conexiuni la zero"
+" sau foarte puține"
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "De ce I2P este atât de lent?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+"Îmi lipsește o mulțime de hosturi în Agenda mea. Care sunt link-uri bune "
+"de abonament?"
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "Cum pot configura propriul meu eepsite?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "Bittorrent / I2PSnark / Azureus I2P Plugin intrebari?"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "Cum ma  pot conecta la IRC în I2P?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "Eu nu pot accesa site-uri din internet prin I2P."
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "Eu nu pot accesa site-uri https:// sau ftp:// prin I2P."
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr "Este posibil să se utilizeze I2P ca un proxy SOCKS?"
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Cum pot configura browser-ul meu?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr "Cum pot accesa consola web de la alte mașini sau proteja prin parola  "
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr "Cum pot utiliza aplicații de la alte calculatoare?"
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr "Cum pot reseedui manual?"
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "Router-ul meu utilizează prea mult CPU?!?"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "Neînțelegere"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr "Cum pot accesa IRC, BitTorrent, sau alte servicii de pe Internet obișnuit?"
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+"Este oare router-ul meu un \"nod de ieșire\" (outproxy) la Internet "
+"obișnuit? Nu vreau să fie."
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+"Mă opun la anumite tipuri de conținut. Cum pot ține de la distribuirea, "
+"stocarea, accesarea lor?"
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Erorile și soluțiile lor"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+"Folosesc FreeBSD și atunci când pornesc I2P primesc o eroare cu privire "
+"la  libm.so.4 !"
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+"În  wrapper.log  văd o eroare   Protocol family "
+"unavailable  când se încarcă I2P"
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "link"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+"În timp ce I2P poate fi pornita la  PC-uri slabe ca de ex. un low-end "
+"Pentium II, cu 64 MB de RAM, veti avea o performanta mult mai bună pe un "
+"Pentium III (sau mai performant), cu 128 MB de RAM (sau mai mult).A grafic care compară performanța a diferitelor JRE "
+"pot fi găsite la %(chart)s, dar pe scurt: e "
+"posibil, folositi Sun / Oracle Java sau OpenJDK."
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+"I2P a fost testat pe Windows, Linux, FreeBSD (vezi notade mai jos),OSX,si OpenSolaris.I2P pentru "
+"platforma Android este în curs de desfășurare"
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr "Iata cateva locuri, alege una sau mai multe."
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "Discutați cu dezvoltatorii pe IRC la # I2P-dev"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+"Vă rugăm să includeți informații relevante din jurnalele router și "
+"jurnalele wrapper."
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+"Abonamentul implicit este http://www.i2p2.i2p/hosts.txt care este "
+"actualizat foarte rar.Dacă nu aveți încă un abonament, va trebui de multe"
+" ori să utilizeze \"sarituri\" de link-uri ce este destul de enervant."
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+"Iată câteva alte link-uri de abonament din agenda publică. Poate veți "
+"dori să adăugați una sau două\n"
+"la  lista de "
+"abonamente susidns.\n"
+"Nu aveți nevoie să adăugați toate acestea, așa cum ele se sincronizeaza "
+"intre ele periodic.\n"
+"Link-urile folosite de o aplicație CGI-bin folosesc diferite strategii "
+"pentru a minimiza\n"
+"numărul din adrese duplicate livrate, astfel încât acestea ar trebui să "
+"fie mai eficiente.\n"
+"Rețineți că abonarea la un serviciu Hosts.txt este un act de "
+"\"încredere\", ca un malware\n"
+"abonamentar pot să vă dee adrese incorecte. Deci, gândiți dacă\n"
+"doriti să aveti încredere in oricare dintre acestea.\n"
+"Operatorii acestor servicii pot avea diferite politici pentru gazde "
+"listare.\n"
+"Prezența pe această listă nu implică aprobarea."
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+"Jrandom a fost dezvoltator al I2P și\n"
+" Syndie  pentru mai mulți ani.\n"
+"Noi nu știm dacă sau când jrandom va reveni.\n"
+"*. Domenii i2p.net s-au lăsat într-o stare non-functionare dupa o cadere "
+"de tensiune la compania de găzduire."
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+"Vezi   această pagină  pentru mesajul de "
+"despărțire jrandom și informații suplimentare\n"
+"cu privire la migrația din *. i2p.net la acest site"
+" ."
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr "I2P rămâne în dezvoltare activă."
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+"Există mai multe cauze posibile de utilizare inalta a procesorului. Aici "
+"este o listă:"
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+"Încercați să utilizați  OpenJDK sau Sun / Oracle Java dacă este "
+"disponibilă pentru sistemul dvs. Puteți verifica\n"
+"ce versiune de Java ați instalat prin taparea comenzii  java "
+"-version , \n"
+"in linie de comandă .Altfel performanță va suferi cu alte implementari de"
+" Java."
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+"Este pornit client BitTorrent in retea  I2P? Încercați să reduceți "
+"numărul de torente, limitele de lățime de bandă,\n"
+"sau încercați să opriți-l complet pentru a vedea dacă, daca vă ajută."
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+"Sunt oare limitele de lățime de bandă prea mare? Este posibil ca prea "
+"mult trafic trece prin intermediul I2P router dvs.care este "
+"supraîncărcat. Încercați să reduceți setarea  procentajului lățimii "
+"de bandă  pe pagina de "
+"configurație."
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+"Asigurați-vă că rulați cea mai recentă versiune a I2P pentru a obține "
+"beneficii de performanță crescuta și repararea bug-urilor."
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+"A fost stabilita memorie suficientă  pentru a fi utilizate de către I2P? "
+"Uită-te la graficul de memorie pe   pagina de grafice  În cazul "
+"în care utilizarea memoriei este \"legata\" — -JVM petrece "
+"majoritatea timpului în colectarea gunoiului. Măriți setarea  "
+"wrapper.java.maxmemory  în  wrapper.config ."
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+"Este oare utilizarea procesorului pur și simplu mai mare decât ar dori, "
+"sau este la 100% pentru o perioadă lungă de timp?\n"
+"Dacă este legat, acest lucru ar putea fi un bug. Uită-te în jurnalele "
+"pentru indicii."
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+"Ați putea fi folosi Java bazate pe biblioteca BigInteger în loc de "
+"versiunea nativa,\n"
+"mai ales dacă se execută pe un sistem de operare sau hardware nou sau "
+"neobișnuit (OpenSolaris, Mipsel, etc).\n"
+"Vezi  jbigi pagina  pentru instrucțiuni privind"
+"\n"
+"diagnosticarea, construirea, și metode de testare."
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+"Dacă biblioteca nativă jbigi lucreaza bine, cel mai mare utilizator de\n"
+"CPU poate fi  rutarea de trafic pentru tuneluri participante. Acesta "
+"utilizează CPU\n"
+"deoarece la fiecare hamei trebuie decodificat un strat de criptare.\n"
+"Puteți limita participarea trafic în două moduri - prin reducerea\n"
+"cota de lățime de bandă pe\n"
+" confignet.jsp ,\n"
+"sau prin stabilirea  router.maxParticipatingTunnels = nnn  pe\n"
+" configadvanced.jsp "
+".\n"
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+"Hmm. I2P este o rețea anonimă, astfel încât este si complicată.\n"
+"I2P este proiectat să reziste cenzurii, oferind un mijloc pentru toată "
+"lumea de a comunica liber.\n"
+"Cel mai bun mod de a menține PC-ul liber de trafic (criptat) care nu va "
+"place este de a nu utiliza I2P.\n"
+"Libertatea de exprimare are unele costuri.\n"
+"Dar haideți să vă răspundem la întrebare în trei părți:"
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+" Distribuție  - Tot traficul pe I2P este criptat in mai multe "
+"straturi. Tu nu stii\n"
+"conținutul unui mesaj, sursa, sau destinație.\n"
+"Tot traficul din cale este intern la rețeaua I2P, nu sunteți un   nod de ieșire  (outproxy).\n"
+"Singura ta alternativa este de a refuza să trasezi\n"
+" orice  trafic, prin setarea latimii de banda parte sau tuneluri "
+"maxime participante la 0 (vezi mai sus).\n"
+"Ar fi frumos, dacă sa nu faceti acest lucru, ar trebui să ajutati rețeaua"
+" de rutare de trafic pentru alții.\n"
+"Peste 95% d37in utilizatorii transmit trafic de rută pentru alții.\n"
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+" stocare  - I2P nu face distributie de stocare conținutului. "
+"Altfel trebuie să va gânditi la\n"
+" Freenet .\n"
+"La rularea I2P Conținutul nimănui nu este stocat pe computerul dvs.."
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+" Acces  - Dacă există unele eepsites care nu vă plac, nu le "
+"vizitați.\n"
+"Sau, folosiți un proxy de blocare ca de ex. Privoxy sau un anumit tip de "
+"\"Net Nanny\"."
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+"Nu. Acest lucru este normal.\n"
+"Toate routerele se adapteaza dinamic la schimbarea cerințelor și "
+"condițiilor de rețea  ."
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+"Posibil să aveți nevoie pentru a reseedui router-ul I2P. Cu versiuni "
+"recente ale I2P puteți merge la http://localhost:7657/configreseedși"
+" faceți clic pe Salvați modificările și reseedui acumDacă "
+"această metodă nu funcționează— sau in cazul in care utilizați o "
+"versiune foarte veche, este posibil să trebuiască să reseedui  manual ."
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+"URL-ul reseed este schimbat acum câțiva ani. Dacă aceasta este prima "
+"instalare și ați instalat\n"
+"un vechi (0.6.1.30 sau anterioara) release, sau\n"
+"nu ați rulat I2P într-o lungă perioadă de timp, trebuie să modificați "
+"URL-ul și apoi\n"
+"faceți clic pe \"reseedui\" pe consola pentru a găsiți alte routere.\n"
+"După ce router-ul se execută,\n"
+" configadvanced.jsp "
+",\n"
+"adăugați linia  i2p.reseedURL = http://netdb.i2p2.de/ \n"
+"SAU  i2p.reseedURL = http://i2pdb.tin0.de/netDb/  (oricare ar "
+"trebui să funcționeze),\n"
+"apoi faceți clic pe \"Apply\", apoi faceți clic pe linkul \"reseed\" din "
+"stanga."
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+"Aceasta funcționează dacă ati pornit versiunea 0.6.1.27 sau ulterioara.\n"
+"Dacă ati pornit versiunea 0.6.1.31 sau ulterioara, probabil că nu trebuie"
+" să faci asta.\n"
+"Dacă ati pornit versiunea 0.6.1.26 sau anterioara, urmați\n"
+" instrucțiuni manual de reseedui  de mai "
+"jos\n"
+"sau instalați  versiune recentă .\n"
+"Metodă alternativă posibila - adăugați\n"
+" wrapper.java.additional.5 =-Di2p.reseedURL = http://netdb.i2p2.de/ "
+"\n"
+"la wrapper.config, opriti router-ul complet, apoi porniti din nou, apoi "
+"faceți clic pe \"reseedui\".\n"
+"Să ne dati de știre dacă acest lucru funcționează.\n"
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+"... dar Dvs *chiar* trebuie să  reinnoiti "
+" pina la ultima versiune."
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+"Dacă routerul dvs. are 10 sau mai multe colegii activi, totul este bine. "
+"Modificări în versiuni 0.6.1.31 și 0.6.1.32 au îmbunătățit\n"
+"eficiența router-ului și în mod eficient a redus numărul de colegii "
+"activi.\n"
+" Router-ul ar trebui  menține conexiuni la câteva colegii în orice"
+" moment.\n"
+"Cel mai bun mod de a rămâne \"mai bine-conectat\" la rețea este de a  cota lățimea de bandă mai larga ."
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+"Este oare router-ul meu un \"nod de ieșire\" la Internet obișnuit? Nu "
+"vreau să fie."
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+"Nu. Spre deosebire de  Tor ,"
+"\n"
+"\"noduri de ieșire\" sau \"outproxies\" nu sunt o parte inerentă a "
+"rețelei.\n"
+"Numai voluntari care au înființat și ruleaza aplicații separate dau acces"
+" traficului de releu la Internet regulat.\n"
+"Există foarte, foarte puține dintre acestea."
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+"Vezi mai sus. Există foarte puține HTTP \"outproxies\", ele nu sunt o "
+"parte inerentă a rețelei, și pot să nu fie în sus. În plus, squid.i2p "
+"outproxies vechi, true.i2p, și krabs.i2p au dispărut.Outproxy în acest "
+"moment este numai false.i2p. Pentru a o folosi, modifica setările "
+"i2ptunnel "
+"  pentru eepProxy  și a stabilit lista de outproxy la \"false.i2p\" "
+"(numai). Apoi, opriți și reporniți eepProxy. În cazul în care nu "
+"funcționează, outproxy nu este pornit. Nu este vina I2P. În cazul în care"
+" motivul principal de a utiliza  rețea anonima este de a accesa site-uri "
+"de anonim pe Internet regulat, ar trebui să încercați, probabil  Tor ."
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+"In cadrul I2P, nu este nevoie pentru HTTPS, ca tot traficul este criptat "
+"end-to-end. FTP nu este acceptat din motive tehnice."
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+"Nu există FTP \"outproxies\" la Internet, aceasta nu este posibil de "
+"realizat. Orice alt tip de outproxy poate lucra dacă este configurat cu "
+"un tunel standard. Dacă doriți să creati un anumit tip de outproxy, "
+"cercetati cu atenție riscurile potențiale. Comunitatea I2P poate sau nu "
+"poate fi capabila de a ajuta cu aspectele tehnice, nu ezitați să "
+"întrebați."
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+"Așa cum sa explicat de mai multe ori de mai sus, orice outproxy existent "
+"nu este o parte esențială a rețelei. Acestea sunt servicii exploatate de "
+"către persoane fizice și acestea pot sau nu pot fi disponibile la un "
+"moment dat."
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
            \n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+" Actualizare : Grație muncii de h2ik, există un https outproxy "
+"disponibile pentru utilizare, prin intermediul I2P. Începând cu I2P 0.8.4"
+"  tunel  "
+"este configurat de la inceput. 
             În cazul în care https outproxy nu "
+"este disponibil în versiunea de I2P, puteți adăuga cu ușurință si de a "
+"face următoarele:"
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open             i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+"Deschide  I2P "
+"manager de tunel . Derulați în jos la partea de jos."
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+"Alegeți  CONNECT  de la  New Client Tunnel  listă "
+"verticală, faceți clic pe  Creare "
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+"În noua pagină,  nume  și  descrie tunel nou https cum "
+"doriți. Access Point  este portul local pentru noul https proxy "
+"recomandat portul  4445 .  Outproxy  ar trebui să fie "
+"adresa outproxy . I2P care sprijină https. A se vedea acest post forum de"
+"  h2ik  "
+"pentru adresa. Asigurați-vă că  Client comun ,  Delay Connect "
+",  AutoStart  sunt verificate. Alte opțiuni ar trebui să fie"
+" lăsate la valorile implicite. Faceți clic pe Salvare. În manager de "
+"tunele, faceți clic pe  Start  butonul de lângă noul tunel."
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+"În Firefox, faceți clic pe Tools    Opțiuni   avansata "
+"  rețea   Setarea . Debifați  Utilizați acest "
+"proxy pentru toate protocol , stabilit  proxy SSL:  la "
+"localhost: 4445."
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "Gata."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+"Aceasta este o întrebare pe care numai puteți răspunde, deoarece "
+"răspunsul corect depinde de comportamentul dvs.,  modelul amenințare , și cât de mult aveți "
+"încredere operatorului outproxy."
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+"Ca si Tor, I2P nu cripteaza magic Internet. Sunteti vulnerabili la "
+"snooping de către operatorii outproxy. "
+" Tor FAQ  face o treabă bună de a explica acest lucru."
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+"În plus, s-ar putea fi vulnerabile la înțelegeri secrete între operatorul"
+" outproxy și operatorii de alte servicii I2P, dacă utilizați aceleași "
+"tuneluri (\"clienți comune\"). Există discuții suplimentare cu privire la"
+" acest lucru pe % (zzz) s ."
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+"Cu excepția cazului cînd outproxy a fost creat pentru serviciul pe care "
+"doriți să vă conectați, acest lucru nu poate fi făcut. Există doar trei "
+"tipuri de outproxies ce rulează chiar acum: HTTP, HTTPS, și e-mail. "
+"Rețineți că nu există o outproxy SOCKS. În cazul în care este necesar "
+"acest tip de serviciu, încercați "
+" Tor ."
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+"Dacă luați în considerare fiecare eepsite care a fost vreodata creat, da,"
+" cele mai multe dintre ele sunt inaccesibile. Oamenii și eepsites vin și "
+"pleacă. O modalitate buna de a începe în I2P este să verificați o listă "
+"de eepsites care sunt în prezent accesibile. % "
+"(eepstatus)s  eepsite-uri active."
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+"Faceți clic pe  site-ul  link în "
+"partea de sus a consolei router pentru instrucțiuni."
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+"De ce sunt descărcări, torenți, navigarea pe web, și orice altceva atât "
+"de lent pe I2P? Criptarea și rutare în cadrul rețelei I2P adaugă o sumă "
+"substanțială de lățime de bandă deasupra capului și limite. Anonimatul nu"
+" este gratuit."
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+"În plus, probabil că tu și toți ceilalți au nevoie pentru a crește "
+"limitele  lățimii de bandă. Două setări cheie sunt pe  inbound și "
+"outbound limitatoarele de lățime de bandă pagina de configurare . "
+"Cu setările implicite de 32kbps, în general, veți obține nimic mai bun "
+"decât transfer de date 15KBps în I2PSnark. Creșterea setărilor (dar cu "
+"menținerea în limitele de conectare reale) va crește rata de transfer "
+"potențial pentru I2PSnark și toate celelalte aplicații."
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+"De asemenea, aveti  lățimea de bandă suficienta pentru configurat pentru "
+"a permite tuneluri participa la traseu prin intermediul router-ul? "
+"Credeti sau nu, permițându-trafic participante vă ține bine integrat în "
+"rețea și ajută la propriile viteze de transfer."
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+"I2P este o lucrare în curs de desfășurare. O mulțime de îmbunătățiri și "
+"remedierile sunt implementate, și, în general vorbind, care rulează cea "
+"mai recentă versiune va ajuta la performanta ta. Dacă nu aveți,  instalați cea mai recentă versiune ."
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+"Vedeti I2P Bittorrent "
+"FAQ"
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+"Un tunel la serverul principal IRC în I2P, Irc2P, este creat atunci când "
+"este instalat I2P (a se vedea pagina de   configurare "
+"I2PTunnel ), și este pornit automat atunci când router-ul I2P "
+"starteaza. Pentru a vă conecta la ea, spune clientului tau de IRC să se "
+"conecteze la  localhost:6668 . Utilizatorii de client-Xchat"
+" ca poate crea o nouă rețea cu serverul  localhost:6668  "
+"(nu uitați să bifați \"server proxy Bypass\" dacă aveți un server proxy "
+"configurat)."
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface.  However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+"Din motive de securitate, consola admin a router-ului implicit ascultă "
+"numai interfata locala pentru conexiuni. Cu toate acestea, cu un pic de "
+"hacking, puteți face accesibil aceasta de la distanță:"
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"with 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+"Deschide ~/.i2p/clients.config și înlocuiți
             "
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
             cu 
             clientApp.0.args=7657 0.0.0.0 ./webapps/"
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to             http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+"Du-te la  "
+"http://localhost:7657/configui  și adăugați un nume de utilizator și"
+" o parolă, dacă doriti."
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+"Du-te la  "
+"http://localhost:7657/index.jsp  și apasati \"Restart grațios\", "
+"care repornește JVM și reîncarcă  aplicații client"
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+"După ce porniti, ar trebui să fie acum posibilitatea de a ajunge la "
+"consola de la distanță. Reîncarcă router la http://127.0.0.1:7657 și vi "
+"se va cere  numele de utilizator și parola pe care ați specificat în "
+"pasul 2 de mai sus în cazul în care browser-ul acceptă pop-up de "
+"autentificare. Notă:  0.0.0.0  de mai sus specifica o  "
+"interfață, nu o rețea sau netmask. 0.0.0.0 înseamnă \"se leaga de "
+"toate interfetele\", astfel încât să poată fi accesibile pe "
+"127.0.0.1:7657 precum și orice IP LAN/WAN."
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+"În mod implicit, interfața I2CP router (port 7654) se leaga la adresa "
+"127.0.0.1. Pentru a lega la 0.0.0.0,  setati opțiunea de configurarea "
+"avansata  i2cp.tcp.bindAllInterfaces = true  și restartati."
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "Ce este un \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+"Un eepsite este un site web care este găzduit anonim - îl puteți accesa "
+"prin setarea proxy HTTP browser-ul web pentru folosirea proxy-ul web (de "
+"obicei, se ascultă pe localhost portul 4444),  și navigati site-ul."
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+"Configurare proxy pentru diferite browsere este pe o pagină  separată  cu capturi de ecran. "
+"Configurarea  mai avansata cu instrumente externe sunt posibil, dar ar "
+"putea introduce scurgeri de informații în configurarea."
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+"x este numărul de parteneri care le-ați trimis sau primit un mesaj de "
+"succes în ultimul minut, y este numărul de colegii văzut în ultima oră "
+"sau cam asa ceva."
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+"Proxy-ul SOCKS lucrează din release  0.7.1. SOCKS 4/4a/5 sunt acceptate. "
+"Nu există nici o SOCKS outproxy asa ca este de o utilitate limitată."
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+"În plus, multe aplicații scurg informații sensibile ce poate sa va "
+"identifice pe Internet. I2P doar filtreaza date de conectare, dar dacă "
+"programul pe care intenționați să rulați trimite această informație ca "
+"conținut, I2P nu are nici o modalitate de a proteja anonimatul. De "
+"exemplu, unele aplicații de e-mail va trimite adresa IP a aparatului în "
+"care se execută pe un server de mail. Nu există nici o cale pentru I2P a "
+"filtra acest lucru, folosind astfel I2P la \"socksify\" aplicațiile "
+"existente este posibilă, dar extrem de periculos."
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+"Dacă doriți mai multe informații cu privire la aplicarea proxy socks, "
+"oricum, există câteva sfaturi utile pe   pagina "
+"socks "
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+"Okay, aici este o trecere in revista a porturilor implicite (totul este "
+"configurabil prin diverse setari, desigur):"
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+" porturi cu care se confruntă de internet  Notă: Noi instalari a "
+"release-ului 0.7.8 nu folosesc portul 8887, se alege un port aleator "
+"între 9000 și 31000, atunci când programul este rulat pentru prima dată. "
+"Portul selectat este afișat pe  pagina de configurare a "
+"router. "
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+"    "
+msgstr ""
+" ieșire UDP la portul aleatoriu menționat pe  pagina de configurare "
+"pentru porturi UDP arbitrare si îndepărtate , permițând răspunsuri "
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+"    "
+msgstr ""
+" ieșire TCP de la porturile aleatorii ridicate la porturi TCP "
+"arbitrare si îndepărtate "
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+"    "
+msgstr ""
+" (optional, dar recomandat) Inbound UDP la portul notat pe  pagina de configurare "
+"din mai multe locatii arbitrare "
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
            \n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+" (optional, dar recomandat) Inbound TCP la portul notat pe  pagina de configurare "
+"din mai multe locatii arbitrare  
             Inbound TCP poate fi "
+"dezactivat pe              pagina de "
+"configurare . "
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
            \n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+" ieșire UDP pe portul 123, permițând răspunsuri  
             Acest lucru"
+" este necesar pentru timpul intern sincronizare I2P lui (prin SNTP - "
+"interogarea o serie aleator SNTP în pool.ntp.org sau un alt server le "
+"specificați)"
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+"porturi locale I2P , asculta doar la conexiuni locale în mod "
+"implicit, cu excepția cazului în care a remarcat:"
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on             confignet.jsp."
+msgstr ""
+" 1900:  UPnP SSDP UDP multicast ascultător.  nu poate fi "
+"schimbat. Se leaga de toate interfețele. Pot fi dezactivate la  confignet.jsp "
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+" 2827:  pod BOB, un nivel mai ridicat socket API pentru clienti "
+" Dezactivat implicit. Poate fi activat / dezactivat pe  configclients.jsp . Pot fi modificate în fișierul bob.config. "
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4444: proxy HTTP  pot fi dezactivate sau modificate pe pagina "
+"i2ptunnel în consola router. Poate fi, de asemenea, configurate pentru a "
+"fi legat de o interfață specifică sau toate interfețele. "
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4445: proxy HTTP  pot fi dezactivate sau modificate pe pagina "
+"i2ptunnel în consola router. Poate fi, de asemenea, configurate pentru a "
+"fi legat de o interfață specifică sau toate interfețele. "
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4444: proxy HTTP  pot fi dezactivate sau modificate pe pagina "
+"i2ptunnel în consola router. Poate fi, de asemenea, configurate pentru a "
+"fi legat de o interfață specifică sau toate interfețele. "
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+" 7652:  UPnP HTTP TCP eveniment ascultător.  Leagă la adresa "
+"LAN. Pot fi modificate cu config avansat i2np.upnp.HTTPPort = nnnn. Pot "
+"fi dezactivate pe 7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+" 7652:  UPnP SSDP UDP cautare raspunsului ascultătorului.  "
+"Leagă la adresa LAN. Pot fi modificate cu config avansat "
+"i2np.upnp.HTTPPort = nnnn. Pot fi dezactivate pe 7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+" 7654:   I2P Protocol Client port, utilizat de aplicații client. "
+" poate fi schimbat la un alt port de pe  configclients.jsp , dar acest lucru nu este recomandat. Ar putea fi de a lega de o "
+"interfață diferit sau toate interfețele, sau cu handicap, pe  configclients.jsp ."
+" "
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+"7655: UDP pentru pod SAM, un nivel mai ridicat socket API pentru "
+"clienti  deschis doar atunci când un client SAM V3 solicită o sesiune "
+"UDP. Poate fi activat / dezactivat pe  configclients.jsp . Pot fi modificate în fisierul clients.config cu opțiunea de linie de "
+"comandă SAM sam.udp.port = nnnn. "
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+"7656: pod BOB, un nivel mai ridicat socket API pentru clienti  "
+"Dezactivat implicit. Poate fi activat / dezactivat pe  configclients.jsp . Pot fi modificate în fișierul bob.config. "
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+" 7657:  consola router  poate fi dezactivată în fișierul "
+"clients.config. Poate fi, de asemenea, configurate pentru a fi legat de o"
+" interfață specifică sau toate interfețele în acel fisier. "
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+" 7658:  Eepsite  poate fi dezactivată în fișierul "
+"clients.config. Poate fi, de asemenea, configurate pentru a fi legat de o"
+" interfață specifică sau toate interfețele în acel fisier. "
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"6668: proxy IRC  pot fi dezactivate sau modificate pe pagina "
+"i2ptunnel în consola router. Poate fi, de asemenea, configurate pentru a "
+"fi legat de o interfață specifică sau toate interfețele. "
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7659: E-mail primite de la pop.postman.i2p  pot fi dezactivate "
+"sau modificate pe pagina i2ptunnel în consola router. Poate fi, de "
+"asemenea, configurate pentru a fi legat de o interfață specifică sau "
+"toate interfețele. "
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7659: mtn.i2p2.i2p (Monotone - dezactivată în mod implicit) pot"
+" fi dezactivate sau modificate pe pagina i2ptunnel în consola router. "
+"Poate fi, de asemenea, configurate pentru a fi legat de o interfață "
+"specifică sau toate interfețele. "
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+" 31000:  conexiune locală la portul canal de control înveliș.  "
+"ieșire la 32000 numai, nu asculta pe acest port. Incepind de la 31000 și "
+"va incrementa până la 31999 în căutarea unui port liber. Pentru a "
+"schimba, consultați  "
+"documentația înveliș  . Pentru mai multe informații, consultați   mai jos . "
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+" 32000:  canal de control local pentru ambalajul de servicii. "
+"Pentru a schimba, consultați  documentația înveliș . Pentru mai multe informații, "
+"consultați   mai jos . "
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally.  You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+" porturi locale I2P și porturile I2PTunnel nu trebuie să fie accesibile "
+"de la mașini la distanță, dar *ar trebui să fie accesibile* la nivel "
+"local. Puteți crea, de asemenea, porturi suplimentare pentru cazuri "
+"I2PTunnel prin http://localhost:7657/i2ptunnel/ (și, la rândul său, ar fi"
+" nevoie pentru a obține firewall-ul pentru a vă permite accesul local, "
+"dar nu acces de la distanță, dacă se dorește)."
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance.  You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+"Deci, pentru a rezuma, nimic nu trebuie să fie accesibil de parteneri "
+"îndepărtate nesolicitate, dar dacă puteți configura NAT / firewall pentru"
+" a permite intrarea UDP și TCP outbound port de iesire , veți obține o "
+"performanță mai bună. Veți avea nevoie, de asemenea, să fiti în măsură de"
+" a trimite pachete UDP de ieșire cu colegii îndepărtate arbitrare "
+"(blocarea IP-uri la intamplare cu ceva de genul PeerGuardian numai tu "
+"doare - nu fa)."
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr "De ce I2P asculta pe portul 32000?"
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+"ambalajul serviciu Tanuki java  pe care le folosim se deschide acest "
+"port— legat la localhost, în scopul de a comunica cu software-ul "
+"care rulează în interiorul JVM. Când JVM este lansat este data o cheie, "
+"astfel se poate conecta la înveliș. După JVM stabilește conexiunea la "
+"înveliș, învelișul refuză orice conexiuni suplimentare."
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the  \n"
+"wrapper documentation."
+msgstr ""
+"Mai multe informații pot fi găsite în   "
+"documentația înveliș ."
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+"Un router I2P trebuie doar să fie seedat o dată, să se alăture rețelei "
+"pentru prima dată. Reseedare este nu mai mult decât trimiterea cererilor "
+"GET HTTP simplu să-i aducă un director listare și descărca mai multe "
+"fișiere \"routerInfo\" de la un URL reseed predefinit."
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+"Un simptom tipic ca reseed nu a reușit este indicatorul \"necunoscut\"(pe"
+" bara laterală stânga a consolei router) afișează o valoare foarte mică "
+"(de multe ori mai puțin de 5), care nu crește. Acest lucru poate avea "
+"loc, printre altele, în cazul în care limitele de firewall la ieșire de "
+"trafic, și a blocat cererea reseed."
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr "Pentru a reseedui manual un router I2P, efectuați următoarele:"
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr "Opri router-ul I2P"
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+"Deschideti http://netdb.i2p2.de/ "
+"folosind web browser"
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr "Salvați zeci de fișiere \"routerInfo\" la \"netDb\" directorul I2P"
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr "Opriti router-ul I2P"
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+"Când încercati de a porni router, folosind \"start i2prouter\", este "
+"posibil să vedeți ieșire, cum ar fi următoarele:"
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+"Pentru a fi inclusiv și să încerce să se asigure că I2P va rula pe cât "
+"posibil mai multe sisteme , până I2P 0.8.9 am folosit un   java înveliș  compilat"
+" pentru FreeBSD 6.x. Dacă primiți această eroare cel mai probabil lipsesc"
+" bibliotecile de compatibilitate necesare. Aceste biblioteci pot fi "
+"instalate prin executarea următoarelor etape:"
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+"Comutați la utilizatorul root cu  su  sau autentificați-vă "
+"ca  root ."
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+"Dacă nu se poate instala aceste biblioteci de compatibilitate (sau nu "
+"doriti), alte posibilități ar fi să compileze înveliș pentru  sistemul dvs. , începând I2P cu  "
+"runplain.sh  script, sau puteți înlocui cu un înveliș din "
+"pachetul cu sursa."
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+"Pentru release 0.8.9 de I2P, ambalajul a fost actualizat la v3.5.12 și "
+"compilate pe sisteme care rulează FreeBSD 7.2."
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+"În  wrapper.log  văd o eroare   Protocol family "
+"unavailable  când se încarcă Consola router"
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+"Adesea, această eroare va avea loc cu orice  software java cu rețea "
+"activata pe unele sisteme care sunt configurate pentru a utiliza IPv6 în "
+"mod implicit. Există câteva moduri de a rezolva acest lucru:"
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+"Pe sistemele bazate pe Linux, puteți  echo 0> / "
+"proc/sys/net/ipv6/bindv6only "
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr "Uita-te la următoarele linii în  wrapper.config ."
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+"În cazul în care liniile sunt acolo, le decomentați prin eliminarea "
+"\"#\". În cazul în care liniile nu sunt acolo, adăugați-le fără \"#\"."
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+"O altă opțiune ar fi pentru a elimina ::1 de la  ~"
+" /.i2p/clients.config "
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+" AVERTISMENT : Pentru orice modificare a  "
+"wrapper.config  să aibă efect, trebuie să opriți complet router-"
+"ul și ambalajul. Clic  Restart  pe consola ta router-ul nu va "
+"reciti acest fisier! Trebuie să faceți clic  Shutdown , si sa "
+"asteaptati 11 minute, apoi porniti I2P."
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+"Grozav! Găsiți-ne pe IRC irc.freenode.net #I2P sau postati  pe forum  și vom posta aici (cu "
+"răspunsuri, sperăm )."
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "legile germane"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr "I2P rețea anonima"
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+"Strat anonim de comunicare peer-to-peer  distribuit construit cu "
+"instrumente open source și proiectat pentru a rula orice serviciu "
+"tradițional de Internet, cum ar fi e-mail, IRC sau web hosting."
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr "Ce face I2P pentru tine?"
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+"Rețeaua I2P ofera protectie a confidentialitatii puternice de comunicare "
+"pe Internet. Multe activități care ar risca intimitatea pe internet "
+"publice pot fi efectuate în mod anonim în interiorul I2P."
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr "Ia I2P %(version)i"
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "Ce este I2P?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+"I2P este o rețea de acoperire anonim - o rețea într-o rețea. Acesta este "
+"destinat să protejeze comunicare de supraveghere năvod și monitorizarea "
+"de către părtea a treia, cum ar fi furnizorii de servicii Internet."
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+"I2P este folosit de mai multe persoane care au grija de intimitatea lor: "
+"activiști, oameni oprimați, jurnaliști și avertizorii de integritate, "
+"precum și de o persoană obișnuită."
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+"Nici o rețea nu poate fi \"perfect anonima\". Scopul continuat de I2P "
+"este de a face cit mai multe atacuri și mai greu de montat. Anonimatul "
+"acesteia va deveni mai puternic in timp ce dimensiunea rețelei va crește "
+"și cu revizuirea academica în curs de desfășurare."
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+"I2P este disponibil pe desktop-uri, sisteme integrate (cum ar fi "
+"Raspberry Pi) și telefoanele Android. Ajuta la răspândirea!"
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr "Citește mai mult…"
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr "Ce se poate face cu I2P?"
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+"Email:Interfață integrată ul web, "
+"plugin pentru e-mail fara server."
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+"Web browsing:Site-uri anonime,"
+" gateway-uri către cele publice din Internet."
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+"Blogging-ul și "
+"forumuri: Blogging-ul și plugin-uri Syndie."
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+"Website hosting:Server "
+"integrat web anonim."
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+"Real-time chat:Mesagerie "
+"instant si clientii IRC."
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+"File sharing:Ed2k și Gnutella "
+"clienti,  client BitTorrent integrat ."
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+"Stocarea "
+"descentralizata de fișiere: Tahoe-LAFS  sistem distribuit de fișiere "
+"plugin."
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr ""
+"Mai multe aplicatii "
+"suportate…"
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr "Noutati & Actualizari"
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr "Link-uri & Resurse recomandate"
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+"A se vedea, de asemenea, pagina cu link-uri   la "
+"prezentari, clipuri video, și tutoriale despre I2P . "
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr "I2P pe web"
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr "Prietenii I2P"
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr "Mai multe proiecte și Documentatie"
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "Apasă"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr "Panouri, saituri cu noutati, altele"
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr ""
+
diff --git a/i2p2www/translations/ro/LC_MESSAGES/research.po b/i2p2www/translations/ro/LC_MESSAGES/research.po
new file mode 100644
index 00000000..408c4adf
--- /dev/null
+++ b/i2p2www/translations/ro/LC_MESSAGES/research.po
@@ -0,0 +1,163 @@
+# Romanian translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# polearnik , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-12-05 12:55+0000\n"
+"Last-Translator: polearnik \n"
+"Language-Team: Romanian "
+"(http://www.transifex.com/projects/p/I2P/language/ro/)\n"
+"Plural-Forms: nplurals=3; "
+"plural=(n==1?0:(((n%100>19)||((n%100==0)&&(n!=0)))?2: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/research/index.html:2
+msgid "Academic Research"
+msgstr "Cercetarea academica"
+
+#: i2p2www/pages/site/research/index.html:4
+msgid ""
+"Academic research and analysis of I2P is an important part of ensuring "
+"that the software and network performs as expected and is safe for users "
+"in hostile environments."
+msgstr ""
+"Cercetări și analize a I2P este o parte importantă de a asigura că "
+"software-ul și rețeaua efectuează cum era de așteptat și este sigura "
+"pentru utilizatori în medii ostile."
+
+#: i2p2www/pages/site/research/index.html:8
+#, python-format
+msgid ""
+"\n"
+"There is a large research community investigating a wide range of aspects"
+" of\n"
+"anonymity. For a current and comprehensive list of relevant papers, see "
+"the\n"
+"Free Haven Anonymity Bibliography.\n"
+"I2P benefits from much of the research into Tor and onion routing, but "
+"there is\n"
+"little dedicated research interest into the theory behind I2P, and the "
+"choices\n"
+"and tradeoffs that the network makes. This presents a unique opportunity "
+"for\n"
+"original research.\n"
+msgstr ""
+"Exista o comunitate larga de cercetare ca re investighează o gama larga "
+"de aspecte de anonimitate.Pentru o listă curentă și completă a "
+"documentelor relevante puteti vedeaBibliografie "
+"gratuita adăpostului anonimatBeneficiile I2P reies din cercetările "
+"rețelei Tor și onion-rutarii,dar exista si mici cercetări  dedicate "
+"teorie I2P, alegerilor și compromise rețelei  "
+
+#: i2p2www/pages/site/research/index.html:18
+#, python-format
+msgid ""
+"A list of known published papers about I2P is available here."
+msgstr ""
+"O listă de lucrări cunoscute publicate despre I2P este disponibilaaici."
+
+#: i2p2www/pages/site/research/index.html:22
+msgid "Testing Attacks on I2P"
+msgstr "Testarea atacurilor pe I2P"
+
+#: i2p2www/pages/site/research/index.html:24
+msgid ""
+"I2P can be run as a separate test network by controlling the locations "
+"that a new router reseeds from so that it only finds other test routers."
+msgstr ""
+"I2P poate fi rulat ca o rețea de testare separată prin controlul "
+"locațiilor pe care router-ul  găsește doar alte routere de testare."
+
+#: i2p2www/pages/site/research/index.html:28
+msgid ""
+"The standard mode of operation is to have one JVM per router instance; "
+"hence running multiple copies of I2P on a single machine is inadvisable, "
+"both due to the potential resource drain and the certain port conflicts. "
+"To better facilitate setting up small test networks, I2P has a "
+"multirouter mode which enables multiple distinct routers to be run in the"
+" same JVM."
+msgstr ""
+"Modul standard de funcționare este de a avea un JVM pentru fiecare "
+"instanță router; prin urmare,este  recomandabil  de difuzat mai multe "
+"copii ale I2P pe o singură mașină , atât din cauza scurgerii de resurse "
+"potențiale și a unor conflicte de port. Pentru a facilita crearea mai "
+"buna de rețele-test mici, I2P are un mod de multirouter care permite mai "
+"multor routere distincte de a fi rulate în aceiași JVM."
+
+#: i2p2www/pages/site/research/index.html:32
+msgid ""
+"MultiRouter can be started from the i2p base directory by running the "
+"below command."
+msgstr ""
+"MultiRouter poate fi pornit de la directorul de baza I2P prin rularea "
+"comenzii de mai jos."
+
+#: i2p2www/pages/site/research/index.html:37
+msgid ""
+"Additionally, I2P can be started in a virtual network mode. This mode "
+"disables all transports, allowing the router to be tested in isolation "
+"without network traffic. To enable this mode, add "
+"i2p.vmCommSystem=true to the router.config before starting."
+msgstr ""
+"În plus, I2P poate fi pornit într-un mod special - rețea virtuală. Acest "
+"mod dezactivează toate transporturile, care permite router-ul să fie "
+"testat în mod izolat, fără trafic din rețea. Pentru a activa acest mod, "
+"adaugati i2p.vmCommSystem = true  în router.config înainte "
+"de a începe."
+
+#: i2p2www/pages/site/research/index.html:41
+msgid "Testing the Live I2P Network"
+msgstr "Testarea I2P rețelei Live"
+
+#: i2p2www/pages/site/research/index.html:43
+#, python-format
+msgid ""
+"If you are planning on conducting research on the live I2P network, "
+"please contact us before you commence your "
+"testing. While we do not discourage researchers from responsibly testing "
+"their ideas on the live network, if an attack becomes apparent and we "
+"don't have any line of communication then we will end up taking "
+"countermeasures which could interfere with the test."
+msgstr ""
+"Dacă planificați efectuarea cercetărilor de rețea I2P , vă rugăm să   contactați-ne  înainte de a începe testarea "
+"sa. In timp ce noi nu descurajam cercetatori de la testarea responsabila "
+"a ideilor lor cu privire la rețeaua de viu, în cazul în care un atac "
+"devine evident și nu avem nici o linie de comunicare, atunci vom sfârși "
+"prin luarea contramăsurilor care ar putea interfera cu testul."
+
+#: i2p2www/pages/site/research/questions.html:2
+msgid "Open research questions"
+msgstr "întrebări de cercetare deschise"
+
+#: i2p2www/pages/site/research/questions.html:4
+msgid "Network database"
+msgstr "Baza de date a rețelei"
+
+#: i2p2www/pages/site/research/questions.html:6
+msgid "Peer selection"
+msgstr "Selectarea partenerului"
+
+#: i2p2www/pages/site/research/questions.html:8
+msgid "Tunnels and Destinations"
+msgstr "Tuneluri și Destinații"
+
+#: i2p2www/pages/site/research/questions.html:10
+msgid "Unidirectional tunnels"
+msgstr "Tuneluri unidirecționale"
+
+#: i2p2www/pages/site/research/questions.html:16
+msgid "Multihoming"
+msgstr "Multihoming"
+
diff --git a/i2p2www/translations/ru/LC_MESSAGES/about.po b/i2p2www/translations/ru/LC_MESSAGES/about.po
new file mode 100644
index 00000000..72faee62
--- /dev/null
+++ b/i2p2www/translations/ru/LC_MESSAGES/about.po
@@ -0,0 +1,2901 @@
+# Russian (Russia) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# IOException , 2013
+# Millennium , 2013
+# keedley , 2013
+# sassy , 2013
+# Narengoyn , 2013
+# TrackIt , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-11-12 07:11+0000\n"
+"Last-Translator: sassy \n"
+"Language-Team: Russian (Russia) "
+"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 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 "Конфигурация веб-браузера"
+
+#: 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 ""
+"Ваш браузер нужно настроить, чтобы вы могли пользоваться eep-сайтами и\n"
+"другими I2P-сервисами. Ниже описаны шаги для\n"
+"наиболее популярных браузеров."
+
+#: 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 "Правила пользования Outproxy"
+
+#: i2p2www/pages/site/about/browser-config.html:22
+msgid "Internet Explorer 8 or Chrome"
+msgstr "Internet Explorer 8 или 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 ""
+"Чтобы открыть настройки, в меню Инструменты выберите \"Настройки "
+"Интернет\". В\n"
+"окне настроек перейдите к вкладке параметров соединения и щелкните по "
+"настройкам сети(LAN) для\n"
+"конфигурации порта прокси-сервера."
+
+#: i2p2www/pages/site/about/browser-config.html:28
+msgid "IE Internet Options"
+msgstr "Настройки Интернет в IE"
+
+#: 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 ""
+"Теперь установите флажок \"Использовать прокси-сервер для локальных "
+"подключений\" а так же флажок \"Не использовать прокси-сервер для "
+"локальных адресов\". По нажатии кнопки Дополнительно открывается окно "
+"настроек прокси-сервера. Заполните поля как показано на картинке, адрес "
+"прокси-сервера 127.0.0.1 и порт 4444 для HTTP, порт 4445 для HTTPS. Нажав"
+" кнопку OK вы сохраните настройки тем самым подготовив браузер для "
+"использования I2P прокси-сервера."
+
+#: 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 ""
+"В меню Настройки, выберите пункт Опции, что бы открыть панель настроек "
+"Firefox. Нажмите на иконку с названием Дополнительно, затем "
+"нажмите на закладку Сеть. В секции Соединение, нажмите "
+"кнопку Настройки. Вы увидите окно как показано ниже:"
+
+#: 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 ""
+"В  окне Параметры соединения кликните кружок рядом с Ручная\n"
+"настройка сервиса прокси, затем введите 127.0.0.1, порт 4444 в поле "
+"HTTP\n"
+"прокси. Введите 127.0.0.1, порт 4445 в поле SSL прокси.\n"
+"Убедитесь, что ввели localhost и 127.0.0.1 в поле \"Не использовать "
+"прокси для\"."
+
+#: 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 ""
+"В меню Settings, выберите Configure Konqueror. В группе"
+"\n"
+"Web Browsing левой части окна, выберите Proxy Services.\n"
+"В появившемся окне, выберите опцию \"Manually specify the proxy "
+"settings\" и\n"
+"нажмите кнопку Setup."
+
+#: 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 ""
+"Введите 127.0.0.1 и порт 4444 в соответствующих полях HTTP. Введите "
+"127.0.0.1 и порт 4445 в соответствующих полях HTTPS.\n"
+"Нажмите кнопку New в секции Exceptions. Введите\n"
+"localhost и нажмите OK. Нажмите кнопку New ещё раз и введите\n"
+"127.0.0.1 и нажмите OK. Нажмите OK ещё раз, что бы закрыть окно настроек."
+
+#: 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 ""
+"Помните: I2P не был спроектирован для создания прокси во внешний "
+"интернет.\n"
+"Вместо этого I2P предназначена для использования в качестве внутренней "
+"сети."
+
+#: 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 ""
+"Проект I2P сам по себе не запускает никаких прокси в интернет. Любые\n"
+"такие прокси-сервисы управляются добровольцами и могут отключиться или\n"
+"стать недоступными в любой момент."
+
+#: 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 ""
+"По умолчанию I2P поставляется с двумя сконфигурированными внешними "
+"прокси: %(http)s\n"
+"(только HTTP прокси) и %(https)s (HTTPS прокси \n"
+"с маршрутизацией через Tor."
+
+#: 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 ""
+"Оба эти аутпрокси настроены с ограничениями соединения. Это значит,\n"
+"что только определённое количество доступов разрешено для каждого "
+"клиента. \n"
+"Как только лимит исчерпан, клиент блокируется на срок в 1 минуту/1час/1 "
+"день.\n"
+"Будьте вежливы и не перегружайте эти сервисы слишком многими запросами!"
+
+#: 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 ""
+"На этих внешних прокси включена фильтрация (например, доступ к \n"
+"mibbit и torrent трэкерам запрещен). Eepsites, \n"
+"которые доступны через адреса .i2p также также не доступны через эти "
+"внешние прокси.\n"
+"По договоренности, false.i2p блокирует сервера рекламы."
+
+#: i2p2www/pages/site/about/browser-config.html:100
+msgid ""
+"Tor is good application to use"
+" as an\n"
+"outproxy to the Internet."
+msgstr ""
+"Tor - это хорошее приложение "
+"для\n"
+"использования его как аутпрокси в интернет. "
+
+#: 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 ""
+"На этой странице перечислены термины, часто используемые при обсуждении "
+"I2P и криптографии."
+
+#: 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 "Текущий баланс: по состоянию на %(date)s"
+
+#: 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 "%(euroval)s &евро; и %(btcval)s BTC"
+
+#: 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 "Вознаграждение за Robert"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:24
+msgid "Bounty Syndie"
+msgstr "Вознаграждение за Syndie"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:25
+msgid "Bounty I2P for CCR Microtic Board"
+msgstr "Вознаграждение за I2P для CCR Microtic Board"
+
+#: 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 "Большая благодарность следующим людям, сделавшим пожертвование для I2P!"
+
+#: 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 ""
+"Если вы сделали пожертвование, пожалуйста, пошлите email на echelon\n"
+"с вашим именем или ником (и, по желанию, домашней страницей), чтобы мы "
+"смогли указать вас здесь."
+
+#: 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
+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 \n"
+"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 ""
+"I2P - это анонимная сеть, открывающая простой уровень, который приложения"
+" могут\n"
+"использовать, чтобы анонимно и безопасно обмениваться сообщениями друг\n"
+"с другом. Сеть сама по себе основана строго на обмене сообщениями (вроде"
+" \n"
+"IP), но есть библиотека, "
+"способная\n"
+"разрешать надёжное потоковое соединение поверх них (вроде \n"
+").\n"
+"Все соединения зашифрованы из конца в конец (в сумме, четыре слоя "
+"шифрования\n"
+"используются при отправке сообщения), и даже конечные точки "
+"(\"адресаты\") - \n"
+"это криптографические идентификаторы (по существу, пара открытых"
+" ключей)."
+
+#: i2p2www/pages/site/about/intro.html:17
+msgid "How does it work?"
+msgstr "Как это работает?"
+
+#: i2p2www/pages/site/about/intro.html:19
+#, 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 ""
+"Чтобы анонимизировать отправляемое сообщение, каждое приложение-клиент\n"
+"имеет свой I2P \"маршрутизатор\", строящий несколько входящих и исходящих"
+"\n"
+"\"туннелей\" - последовательность "
+"пиров,\n"
+"передающих сообщения в одном направлении (к и от клиента соответственно)."
+"\n"
+"В свою очередь, когда один клиент хочет послать сообщение другому, он\n"
+"передаёт это сообщение через один из своих исходящих туннелей, "
+"нацеливаясь\n"
+"на один из входящих туннелей другого клиента, в конечном итоге достигая \n"
+"пункта назначения. Каждый участник сети выбирает длину этих туннелей, и\n"
+"таким образом идёт на компромисс между анонимностью, временем ожидания\n"
+"и пропускной способностью в соответствии со своими нуждами. В результате,"
+"\n"
+"количество пиров, ретранслирующих каждое сообщение из конца в конец,\n"
+"сведено к абсолютному минимуму, необходимому, чтобы удовлетворить\n"
+"\"модель угрозы\" (уровень желаемой безопасности) как отправителя, так и "
+"получателя. "
+
+#: i2p2www/pages/site/about/intro.html:33
+#, 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 ""
+"Когда один клиент в первый раз хочет связаться с другим клиентом, они "
+"делают запрос\n"
+"к полностью распределённой \"сетевой ⏎\n"
+"базе данных\" - персонально структурированной\n"
+"распределённой хеш-таблице "
+"(DHT),\n"
+"основанной на  "
+"алгоритме Kademilia. Это сделано\n"
+"для эффективного поиска входящих туннелей других клиентов, но последующие"
+" сообщения\n"
+"между ними обычно включают в себя эти данные, поэтому поиск в сетевой "
+"базе данных\n"
+"больше не требуется. "
+
+#: i2p2www/pages/site/about/intro.html:44
+#, python-format
+msgid "More details about how I2P works are available."
+msgstr "Более подробно о том, как работает I2P."
+
+#: i2p2www/pages/site/about/intro.html:48
+msgid "What can you do with it?"
+msgstr "Как вы можете это использовать?"
+
+#: i2p2www/pages/site/about/intro.html:50
+#, 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 ""
+"Внутри сети I2P приложения не ограничены в способах коммуникации - \n"
+"те, что обычно используют UDP, могут использовать базовый функционал\n"
+"I2P, а те, что обычно используют TCP, могут использовать TCP-подобную \n"
+"потоковую библиотеку. У нас есть приложение общего TCP/IP моста\n"
+"(\"I2PTunnel\"), которое позволяет людям \n"
+"пересылать TCP потоки в I2P сеть также как получать потоки извне сети и \n"
+"пересылать их на определённый TCP/IP адрес."
+
+#: i2p2www/pages/site/about/intro.html:60
+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 ""
+"I2PTunnel в настоящее время используется, чтобы позволить людям создать\n"
+"собственный анонимный вебсайт (\"eepsite\"), запустив нормальный "
+"вебсервер и \n"
+"указав \"серверу\" I2PTunnel на него, который люди смогут посещать "
+"анонимно\n"
+"через I2P и обычный браузер, запуская HTTP прокси I2PTunnel "
+"(\"eeproxy\"). К тому же,\n"
+"мы используем ту же самую технику, чтобы запускать анонимную сеть IRC "
+"(где \n"
+"IRC-сервер хостится анонимно, а стандартный IRC-клиент использует "
+"I2PTunnel, чтобы\n"
+"связать с ним). Прилагаются усилия и для разработки других приложений, "
+"например\n"
+"приложения оптимизированного кооперативного обмена файлами (вроде \n"
+"BitTorrent), распределённого "
+"хранилища данных\n"
+"(вроде Freenet / ⏎\n"
+"MNet), и системы ведения блогов "
+"(полностью\n"
+"распределённый LiveJournal), "
+"но они пока \n"
+"не готовы к использованию."
+
+#: i2p2www/pages/site/about/intro.html:76
+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 ""
+"I2P не является, по сути, сетью \"аутпрокси\": клиент, которому вы "
+"посылаете\n"
+"сообщение, - это криптографический идентификатор, не какой-то IP адрес,\n"
+"поэтому сообщение должно быть адресовано тому, кто использует I2P. "
+"Однако,\n"
+"для этого клиента возможно быть аутпрокси, позволяя вам анонимно "
+"использовать\n"
+"его интернет-соединение. В качестве демонстрации, \"eeproxy\" примет "
+"нормальный\n"
+"не-I2P URL (такой как \"http://www.i2p.net\") и перенаправит его в "
+"определённый пункт,\n"
+"использующий squid HTTP "
+"прокси, позволяя\n"
+"простой анонимный серфинг обычного интернета. Простые аутпрокси как этот "
+"не \n"
+"жизнеспособны в долгосрочной перспективе по нескольким причинам (включая\n"
+"расходы на поддержание работы, также как проблемы с анонимностью и "
+"безопасностью,\n"
+"которые для них характерны), но в определённых обстоятельствах такой "
+"метод может быть\n"
+"целесообразным."
+
+#: i2p2www/pages/site/about/intro.html:90
+#, 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 ""
+"Команда разработчиков I2P - это группа открытая "
+"для всех кто заинтересован принять участие,"
+" и весь код проэкта - это открытый код.  "
+"Ядро I2P SDK и текущая реализация роутера выполнены на языке Java (в "
+"настоящий момент поддерживаются реализации от \n"
+"sun и kaffe, реализация поддержки gcj запланирована на будущее), также "
+"существует\n"
+"простое основанное на сокетах API для доступа к "
+"сети из других языков (библиотека для C уже доступна, а для Python и Perl"
+" в \n"
+"процессе разработки). Проект активно разрабатывается хоть ещё и не достиг"
+" стадии релиза 1.0, но текущий план развития "
+"проекта описывает дальнейший путь нашей команды."
+
+#: i2p2www/pages/site/about/media.html:2 i2p2www/pages/site/about/media.html:4
+msgid "Presentations on I2P"
+msgstr "Презентации в I2P"
+
+#: 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 ""
+"Ниже приведены ссылки на презентации, видео и руководства по I2P. Ссылки "
+"на исследовательские работы по I2P доступны здесь."
+
+#: i2p2www/pages/site/about/media.html:8
+#, python-format
+msgid "To request an addition to this page, please send to %(email)s."
+msgstr "Материалы для добавления на эту страницу отсылайте на %(email)s."
+
+#: i2p2www/pages/site/about/media.html:11
+msgid ""
+"\n"
+"Newest links are at the bottom of each section."
+msgstr ""
+"\n"
+"Свежие ссылки в начале каждого раздела."
+
+#: 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 ""
+"Презентация IIP на конференции CodeCon\n"
+"MP3 audio\n"
+"стенограмма\n"
+"Lance James (0x90), Февраль 2002."
+
+#: 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 ""
+"Презентация IIP на конференции ToorCon\n"
+"MP3 audio\n"
+"слайды\n"
+"Lance James (0x90), Сентябрь 2002."
+
+#: 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 ""
+"Быть или I2P\n"
+"(Youtube Video)\n"
+"Введение в анонимную связь с I2P.\n"
+"Быть или I2P (презентация PDF),\n"
+"Jens Kubieziel, 24C3 Berlin, Декабрь 28, 2007."
+
+#: 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 ""
+"Видеозапись обсуждения I2P на Chemnitz Linux "
+"Tag,\n"
+"Lars Schimmer,\n"
+"Март 14-15, 2009"
+
+#: 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 ""
+"НАВЕРНОЕ New York Июль 17, 2010 - Краткий обзор I2P от zzz, в конце "
+"выступления Adrian Hong's\n"
+"\"Хакеры за Права Человека\".\n"
+"MP3 audio"
+
+#: 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 ""
+"В I2P Darknet: Добро пожаловать в Cipherspace\n"
+"Adrian Crenshaw. Schmoocon Firetalk, Январь 2011"
+
+#: 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 ""
+"Использование технологий для распространения "
+"свободы\n"
+"(Youtube Video)\n"
+"Eric Johnson.\n"
+"Agora I/O Unconference, Март 27, "
+"2011.\n"
+"Информация об I2P с 10:00 до 20:00."
+
+#: i2p2www/pages/site/about/media.html:69
+#, python-format
+msgid ""
+"The Bright side of darknets, FOSSCOMM Patras May "
+"2011"
+msgstr "Светлая сторона darknet, FOSSCOMM Patras Май 2011"
+
+#: 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 ""
+"Общие уязвимости Darknet\n"
+"(Youtube Video)\n"
+"Adrian Crenshaw, AIDE, Июль "
+"11-15, 2011."
+
+#: 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 ""
+"Заметки с семинаров по I2P / Tor\n"
+"Adrian Crenshaw. DEF CON 19, Las Vegas, Август 6, 2011."
+
+#: 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 ""
+"Cipherspaces/Darknets: Обзор стратегий атак -\n"
+"DEF CON Живая версия (Youtube Video),\n"
+"\"Студийная\" версия (Youtube Video),\n"
+"Слайды (ppt)\n"
+"Adrian Crenshaw. DEF CON 19, Las Vegas, Август 7, 2011."
+
+#: i2p2www/pages/site/about/media.html:94
+msgid ""
+"Modern cipherspace ecosystems, 0x375 "
+"0x06 4/11/2011"
+msgstr ""
+"Современные экосистемы cipherspace , "
+"0x375 0x06 4/11/2011"
+
+#: 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 ""
+"Руководство I2P под Windows\n"
+"(Youtube Video)\n"
+"Этот гид объяснит как установить I2P в Windows XP.\n"
+"Автор Telecomix"
+
+#: 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 ""
+"Руководство I2P под Debian\n"
+"(Youtube Video)\n"
+"Этот гид объяснит как установить I2P в Debian Linux System.\n"
+"Автор Telecomix"
+
+#: 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 ""
+"Как поднять анонимный веб-сайт в сети I2P\n"
+"(Youtube Video)\n"
+"Как поднять анонимный веб-сайт в сети I2P.\n"
+"Автор Telecomix"
+
+#: 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 ""
+"Руководство I2P под Mac OS X\n"
+"(Youtube Video)\n"
+"Руководство по запуску i2p под Mac OS X, и как подключиться к "
+"irc.telecomix.i2p.\n"
+"Автор Telecomix"
+
+#: 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 ""
+"Felix Atari объясняет основные принципы I2P\n"
+"(Youtube Video)\n"
+"Felix Atari сотрудник Telecomix Crypto Munitions Bureau.\n"
+"Автор Telecomix"
+
+#: 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 ""
+"Как попасть в I2P, анонимный P2P Darknet (устновка в"
+" Windows)\n"
+"(Youtube Video)\n"
+"Это руководство объяснит как установить и настроить ПО для доступа в I2P."
+
+#: 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 ""
+"Как подключиться к сети I2P\n"
+"(Youtube Video)\n"
+"Как установить I2P в Ubuntu."
+
+#: 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 ""
+"Установка ПО I2P darknet в Linux\n"
+"(Video)\n"
+"Adrian Crenshaw.\n"
+"Январь 2011"
+
+#: i2p2www/pages/site/about/media.html:159
+#, python-format
+msgid ""
+"Short garlic routing animation\n"
+"(Youtube Video)\n"
+"Adrian Crenshaw.\n"
+msgstr ""
+"Короткий роли о чесночной маршрутизации\n"
+"(Youtube Video)\n"
+"Adrian Crenshaw.\n"
+
+#: 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 ""
+"0x90 в интервью DistributedCity\n"
+"Часть 1\n"
+"Часть 2\n"
+"Июль 26, 2002."
+
+#: 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 ""
+"0x90 в интервью El Pais\n"
+"(в оригинале на испанском)\n"
+"английский перевод\n"
+"Октябрь 31, 2002."
+
+#: i2p2www/pages/site/about/media.html:185
+#, python-format
+msgid ""
+"2003 Business Week article referencing "
+"invisiblenet"
+msgstr "2003 Business Week статья о невидимой сети"
+
+#: 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 ""
+"Netzwelt.de статья об анонимности в Интернет\n"
+"(на немецком)\n"
+"Ноябрь 2007."
+
+#: i2p2www/pages/site/about/media.html:195
+#, python-format
+msgid ""
+"zzz interviewed by gulli.com\n"
+"March 2009\n"
+"German translation"
+msgstr ""
+"интервью zzz для gulli.com\n"
+"Март 2009\n"
+"немецкий перевод"
+
+#: 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 ""
+"zzz в интервью на InfoSec Daily Podcast Ep. 454 "
+"(mp3)\n"
+"Август 18, 2011"
+
+#: i2p2www/pages/site/about/media.html:207
+#, python-format
+msgid ""
+"I2P - Anonymity for the Masses,\n"
+"Jonathan Cox,\n"
+"November 11, 2011."
+msgstr ""
+"I2P - Анонимность для Всех,\n"
+"Jonathan Cox,\n"
+"Ноябрь 11, 2011."
+
+#: 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 ""
+"zzz и Lance James в интервью на InfoSec Daily Podcast"
+" Ep. 596 (mp3)\n"
+"Февраль 16, 2012"
+
+#: 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 ""
+"Мы маленькая группа людей, распределенная по нескольким континентам, мы "
+"работаем над\n"
+"продвижением различных частей проекта и обсуждаем архитектуру \n"
+"сети.\n"
+"Присоединяйтесь!"
+
+#: 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 "PR-менеджер"
+
+#: 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 "Упаковщик; Linux"
+
+#: 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 "Упаковщик; Windows"
+
+#: 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
+#, fuzzy
+msgid "Manage the project bug tracker"
+msgstr "управляет зеркалами проекта"
+
+#: i2p2www/pages/site/about/team.html:80
+#, fuzzy
+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 "Web-дизайнер"
+
+#: 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 "Главный разработчик почты I2P"
+
+#: i2p2www/pages/site/about/team.html:124
+msgid "organize and develop the i2p mail system"
+msgstr "организует и разрабатывает почтовую систему i2p"
+
+#: i2p2www/pages/site/about/team.html:127
+#, python-format
+msgid "I2Host lead"
+msgstr "Главный разработчик I2Host"
+
+#: i2p2www/pages/site/about/team.html:129
+msgid "I2Host addressbook application"
+msgstr "адрессная книга I2Host"
+
+#: i2p2www/pages/site/about/team.html:132
+#, python-format
+msgid "BOB lead"
+msgstr "Главный разработчик BOB"
+
+#: i2p2www/pages/site/about/team.html:134
+msgid "Basic Open Bridge"
+msgstr "Basic Open Bridge"
+
+#: i2p2www/pages/site/about/team.html:137
+#, python-format
+msgid "I2P-Bote lead"
+msgstr "Главный разработчик I2P-Bote"
+
+#: i2p2www/pages/site/about/team.html:139
+msgid "I2PBote plugin"
+msgstr "модуль I2PBote"
+
+#: i2p2www/pages/site/about/team.html:142
+#, python-format
+msgid "Robert lead"
+msgstr "Главный разработчик Robert"
+
+#: i2p2www/pages/site/about/team.html:144
+msgid "Robert BitTorrent client"
+msgstr "торрент клиент Robert BitTorrent"
+
+#: i2p2www/pages/site/about/team.html:147
+#, python-format
+msgid "I2Phex lead"
+msgstr "Главный разработчик I2Phex"
+
+#: i2p2www/pages/site/about/team.html:149
+msgid "I2Phex Gnutella client"
+msgstr "клиент I2Phex Gnutella"
+
+#: i2p2www/pages/site/about/team.html:152
+#, python-format
+msgid "I2PSnark lead"
+msgstr ""
+"Главный разработчик I2PSnark"
+
+#: i2p2www/pages/site/about/team.html:154
+msgid "Maintains the integrated Bittorrent client"
+msgstr "Поддерживает интегрированный клиент Bittorrent"
+
+#: i2p2www/pages/site/about/team.html:157
+#, python-format
+msgid "iMule lead"
+msgstr "Главный разработчик iMule"
+
+#: i2p2www/pages/site/about/team.html:159
+msgid "eMule client over I2P"
+msgstr "клиент eMule через I2P"
+
+#: i2p2www/pages/site/about/team.html:162
+#, python-format
+msgid "Syndie lead"
+msgstr "Главный разработчик Syndie"
+
+#: i2p2www/pages/site/about/team.html:164
+msgid "Syndie development"
+msgstr "разработка Syndie"
+
+#: i2p2www/pages/site/about/team.html:167
+msgid "Susimail lead"
+msgstr "Главный разработчик Susimail"
+
+#: i2p2www/pages/site/about/team.html:169
+msgid "Susimail development"
+msgstr "разработка Susimail"
+
+#: i2p2www/pages/site/about/team.html:172
+msgid "Console"
+msgstr "Консоль"
+
+#: i2p2www/pages/site/about/team.html:174
+msgid "Router console HTML/CSS design"
+msgstr "Дизайн HTML/CSS консоли маршрутизатора"
+
+#: i2p2www/pages/site/about/team.html:177
+msgid "SAM"
+msgstr "SAM"
+
+#: i2p2www/pages/site/about/team.html:179
+msgid "SAM maintainer"
+msgstr "сопровождение SAM"
+
+#: i2p2www/pages/site/about/team.html:182
+msgid "I2PCPP lead"
+msgstr "Главный разработчик I2PCPP"
+
+#: i2p2www/pages/site/about/team.html:184
+msgid "C++ Router"
+msgstr "C++ Маршрутизатор"
+
+#: 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 "разработка fire2pe, улучшение консоли"
+
+#: i2p2www/pages/site/about/team.html:199
+msgid "desktopgui, dijjer port"
+msgstr "desktopgui, портирование dijjer"
+
+#: i2p2www/pages/site/about/team.html:203
+msgid "Debian/Ubuntu Packager and PPA maintainer"
+msgstr "Дистрибуция Debian/Ubuntu и поддержка PPA"
+
+#: i2p2www/pages/site/about/team.html:207
+msgid "Routerconsole backend and UI work, website revamp, unit tests work"
+msgstr ""
+"Бэкенд консоли маршрутизатора и работа на UI, исправления по веб-сайту, "
+"юнит-тестирование"
+
+#: 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 "Разработка I2PTunnel, библиотеки минипотоков"
+
+#: i2p2www/pages/site/about/team.html:222
+msgid "Project lead, Syndie lead"
+msgstr "Главный разработчик проекта, главный разработчик Syndie"
+
+#: i2p2www/pages/site/about/team.html:226
+msgid "Project lead, Syndie lead, I2Phex, support guru"
+msgstr ""
+"Главный разработчик проекта, главный разработчик Syndie, I2Phex, гуру "
+"поддержки"
+
+#: i2p2www/pages/site/about/team.html:230
+msgid "iMule lead"
+msgstr "Главный разработчик iMule"
+
+#: 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 "Разработчик I2Phex"
+
+#: i2p2www/pages/site/about/team.html:246
+msgid "Python SAM library, attack simulations"
+msgstr "Python библиотека SAM, эмуляция атак"
+
+#: i2p2www/pages/site/about/team.html:250
+msgid "i2pmail development"
+msgstr "разработка i2pmail"
+
+#: i2p2www/pages/site/about/team.html:254
+msgid "Syndie help"
+msgstr "Файл справки Syndie"
+
+#: i2p2www/pages/site/about/team.html:258
+msgid "i2p mail,susimail and susidns apps"
+msgstr "приложения почты i2p, susimail и susidns"
+
+#: i2p2www/pages/site/about/team.html:262
+msgid "I2Phex (port of Phex to I2P)"
+msgstr "I2Phex (портирование Phex на I2P)"
+
+#: i2p2www/pages/site/about/team.html:266
+msgid "addressbook,i2p-bt,syndie client"
+msgstr "адрессная книга, i2p-bt, клиент syndie"
+
+#: i2p2www/pages/site/about/team.html:270
+msgid "organize and develop the i2p-bt BitTorrent port"
+msgstr "арганизация и разработка порта i2p-bt BitTorrent"
+
+#: i2p2www/pages/site/about/team.html:274
+msgid "addressbook, i2p-bt, syndie client development"
+msgstr "адрессная книга, i2p-bt, разработка клиента syndie"
+
+#: i2p2www/pages/site/about/team.html:278
+msgid "encryption and signature routines, I2PIM"
+msgstr "задачи по шифрованию и подписанию, I2PIM"
+
+#: i2p2www/pages/site/about/team.html:282
+msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)"
+msgstr "кодирование SAM jython, работа над stasher (DHT) и v2v (VoI2P)"
+
+#: i2p2www/pages/site/about/team.html:286
+msgid "installer, systray, bogobot"
+msgstr "инсталлятор, systray, bogobot"
+
+#: i2p2www/pages/site/about/team.html:290
+msgid "jbigi development, wiki migration, doc cleanup"
+msgstr "разработка jbigi, миграция wiki, чистка doc"
+
+#: i2p2www/pages/site/about/team.html:294
+msgid "java debugging and client development on I2PTunnel and the router console"
+msgstr "отладка java и разработка клиента I2PTunnel и консоли маршрутизатора"
+
+#: i2p2www/pages/site/about/team.html:298
+msgid "SAM perl module"
+msgstr "модуль perl для SAM"
+
+#: i2p2www/pages/site/about/team.html:302
+msgid "i2psnark work"
+msgstr "разработка i2psnark"
+
+#: i2p2www/pages/site/about/team.html:306
+msgid "java cleanup"
+msgstr "чистка java"
+
+#: i2p2www/pages/site/about/team.html:310
+msgid "docs. wiki migration"
+msgstr "документация. миграция wiki"
+
+#: 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 "Портирование jcpuid на C "
+
+#: i2p2www/pages/site/about/team.html:322
+msgid "C# SAM library, pants, fortuna integration"
+msgstr "Библиотека C# SAM, pants, интегрирование fortuna"
+
+#: i2p2www/pages/site/about/team.html:326
+msgid "libSAM"
+msgstr "libSAM"
+
+#: i2p2www/pages/site/about/team.html:330
+#: i2p2www/pages/site/about/team.html:334
+msgid "i2p-bt tracker development"
+msgstr "разработка трэкера i2p-bt"
+
+#: 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 "Август 2010"
+
+#: 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 ""
+"Существует несколько основных применимых техник для увеличения видимой\n"
+"производительности I2P - некоторые из них связаны с ЦП, другие связаны с\n"
+"шириной канала, третьи связаны с протоколом. Тем не менее все они\n"
+"оказывают влияние на задержки, пропускную способность и видимую "
+"производительность\n"
+"сети, так как снижают нагрузку на ограниченные ресурсы.  Этот список, "
+"конечно же\n"
+"не является исчерпывающим, однако он охватывает основные доступные методы."
+
+#: 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 ""
+"Для ознакомления с уже реализованными улучшениями производительности "
+"просмотрите \n"
+"Историю Производительности."
+
+#: 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 ""
+"Вероятно самым важным шагом к повышению производительности является\n"
+"улучшение механизма выбора узлов через которые будет строиться тоннель,\n"
+"нужно удостовериться, что не будут использоваться слишком медленные узлы "
+"или быстрые но \n"
+"перегруженные узлы и т.д. В добавок к этому мы должны убедиться, что не "
+"откроемся для атак типа Sybil\n"
+"со стороны сильных противников с множеством быстрых узлов."
+
+#: 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 ""
+"Мы хотим улучшить процесс исправления сетевой базы данных \n"
+"и алгоритмы обслуживания, а не постоянно отслеживать пространство ключей "
+"для новых \n"
+"узлов, провоцируя огромное количество сетевых сообщений и нагрузку на "
+"маршрутизатор - мы \n"
+"можем снизить или, даже, прекратить следить до тех пор пока мы не "
+"обнаружим что-то \n"
+"более плохое (например, снизить частоту слежения, основываясь на "
+"последнем времени когда \n"
+"кто-то дал нам ссылку на кого-то, о ком мы раньше не знали). Также мы "
+"можем оптимизировать \n"
+"то, что мы на самом деле отправляем - сколько узлов участвует в отправке "
+"(или, даже, \n"
+"в получении ответа), и сколько конкурентных поисков мы выполняем."
+
+#: 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 ""
+"Суть алгоритма ElGamal/AES+SessionTag \n"
+"состоит в управлении набором случайных одноразовых 32-байтных массивов, и"
+" в удалении \n"
+"их, если они не были достаточно быстро использованы. Если мы удалим их "
+"слишком рано, мы \n"
+"перейдем к полному (дорогому) шифрованию ElGamal, но если мы не \n"
+"удалим их достаточно быстро, нам придется уменьшить их количество, чтобы "
+"не \n"
+"исчерпать свободную память (и если получатель все таки поломается и "
+"потеряет несколько \n"
+"меток, то может возникнуть даже больше ошибок шифрования до обнаружения "
+"этого). С более \n"
+"активными алгоритмами обнаружения и оповещения мы можем безопаснее и \n"
+"эффективнее управлять жизненным циклом меток, заместив шифрование ElGamal"
+" \n"
+"простой операцией AES."
+
+#: 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 ""
+"Дополнительные идеи улучшения доставки Метки Сессии описаны на\n"
+"странице ElGamal/AES+SessionTag."
+
+#: i2p2www/pages/site/about/performance/future.html:61
+msgid "Migrate sessionTag to synchronized PRNG"
+msgstr "Переход от sessionTag к синхронизированному PRNG"
+
+#: 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 ""
+"Сейчас наш алгоритм ElGamal/AES+SessionTag"
+" \n"
+"помечает каждое шифрованное сообщение уникальными случайными \n"
+"32 байтами (\"метка сессии - session tag\"), определяющего, что сообщение"
+" было зашифровано \n"
+"ассоциированным с сессией AES ключом. Это избавляет узлы от необходимости"
+" помечать \n"
+"сообщения, которые являются частью той же сессии, т.к. у каждого "
+"сообщения есть совершенно \n"
+"новая случайная метка. Чтобы добиться этого, каждые несколько сообщений "
+"связываются \n"
+"новым набором меток сессии вместе с шифрованным сообщением, прозрачно \n"
+"предоставляя способ идентифицировать будущие сообщения. Далее мы должны "
+"следить \n"
+"за тем, какие сообщения были успешно доставлены, чтобы знать какие метки"
+" \n"
+"мы можем использовать."
+
+#: 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 ""
+"Это хорошо и довольно надежно работает, тем не менее, это не эффективно \n"
+"с точки зрения использования пропускной способности, так как для этого "
+"требуется досрочно доставлять \n"
+"метки (и не все метки могут быть важны, некоторые могут быть бесполезны, "
+"в связи с \n"
+"их просрочкой). Хотя, в среднем, досрочная доставка метки сессии занимает"
+" \n"
+"32 байта на сообщение (размер метки). Хотя, как предложил Taral, этот \n"
+"размер можно выиграть, заменив доставку меток синхронизированным \n"
+"PRNG - когда устанавливается новая сессия (через зашифрованный блок "
+"ElGamal), \n"
+"обе стороны используют PRNG и генерируют метки сессии по запросу \n"
+"(и получатель предварительно рассчитывает следующие несколько значений, \n"
+"для обработки очереди доставки)."
+
+#: 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 ""
+"Текущее время жизни туннеля по умолчанию в 10 минут довольно произвольно,"
+" хотя \n"
+"\"вполне подходит\". Когда у нас будет код для лечения туннеля и более "
+"эффективное обнаружение \n"
+"ошибок, мы сможем более безопасно варьировать его длительность, снижая \n"
+"нагрузку на сеть и CPU (из-за дорогих сообщений создания туннеля)."
+
+#: 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 ""
+"Это выглядит простым решением для высоконагруженных маршрутизаторов с "
+"большой пропускной способностью, \n"
+"но не должны на это рассчитывать до тех пор пока не оптимизируем алгоритм"
+" построения туннеля. \n"
+"Тем не менее, 10 минутное время жизни туннеля жестко прописано в коде в "
+"нескольких местах, \n"
+"и для изменения длительности понадобятся значительные усилия. \n"
+"Также, будет сложно обеспечить обратную совместимость такого изменения."
+
+#: 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 ""
+"В настоящем, т.к. средняя частота удачного создания сетевого туннеля "
+"довольно высока, \n"
+"мы не планируем увеличивать время жизни туннеля."
+
+#: 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 ""
+"У нас есть еще одна довольно произвольная, но \"вполне подходящая\" вещь "
+"- это \n"
+"тайм-ауты на различные действия. Почему для \"peer unreachable\" у нас \n"
+"тайм-аут 60 секунд, Почему мы пытаемся отправить извещения LeaseSet \n"
+"через другой туннель спустя 10 секунд? Почему запрос к базе данных не "
+"может \n"
+"длиться дольше 60 или 20 секунд? Почему пункт назначения настроен на "
+"запрос \n"
+"нового набора туннелей каждые 10 минут? Почему мы даем узлу 60 секунд для"
+" \n"
+"ответа на запрос о присоединении к туннелю? Почему мы считаем, что "
+"туннель \"умер\", \n"
+"если он не передал наш тест за 60 секунд?"
+
+#: 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 ""
+"Все эти костыли можно заменить более адаптивным кодом, так же как и \n"
+"параметры туннеля, чтобы достичь компромисса между \n"
+"пропускной способностью, задержками и использованием CPU."
+
+#: 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 ""
+"Возможно возобновление использования профиля интерактивного потока \n"
+"(текущая реализация использует только профиль bulk потока)."
+
+#: 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 ""
+"Ограничение пропускной способности на стороне клиента (в любом или обоих "
+"направлениях потока, \n"
+"или, при возможности, распределение между несколькими потоками). Конечно,"
+" это \n"
+"будет дополнением к общему ограничению пропускной способности "
+"маршрутизатором."
+
+#: i2p2www/pages/site/about/performance/future.html:141
+msgid ""
+"Access control lists (only allowing streams to or from certain other "
+"known \n"
+"destinations)."
+msgstr ""
+"Списки контроля доступа (разрешать потоки только к или из известных \n"
+"пунктов назначения)."
+
+#: 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 ""
+"Веб управление и наблюдение за состоянием различных потоков, наряду с \n"
+"возможностью явного их закрытия или уменьшения."
+
+#: 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 ""
+"Дополнительные идеи улучшения потоковой библиотеки описаны на \n"
+"странице потоковой библиотеки."
+
+#: 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 ""
+"Заметные улучшения производительности были выполнены с использованием "
+"нижеперечисленных техник.\n"
+"Еще многое предстоит сделать, смотри на странице Производительность \n"
+"текущие вопросы и размышления"
+
+#: 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 ""
+"Когда я последний раз профилировал код I2P, большая часть времени "
+"тратилась на \n"
+"одну функцию: java.math.BigInteger \n"
+"modPow. \n"
+"Вместо того чтобы попытаться оптимизировать этот метод, мы будем вызывать"
+" \n"
+"GNU MP - безумно быструю математическую "
+"библиотеку \n"
+"(с отлаженным ассемблером под множество архитектур). (Редактор: смотри"
+"\n"
+"NativeBigInteger для быстрого шифрования публичным "
+"ключом)"
+
+#: 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 ""
+"\n"
+"ugha и duck работают над связующим кодом C/JNI, и существующий код Java \n"
+"уже внедрен соответствующими ловушками, как только он был готов. "
+"Предварительные результаты \n"
+"выглядят потрясающе - запуск маршрутизатора с нативным GMP modPow дает "
+"около \n"
+"800% прироста производительности шифрования и снижает нагрузку "
+"наполовину. Это \n"
+"было проверено только на одном компьютере пользователя, и оно уже готово "
+"для \n"
+"внедрения."
+
+#: i2p2www/pages/site/about/performance/history.html:32
+msgid "Garlic wrapping a \"reply\" LeaseSet"
+msgstr "Garlic упаковка \"ответа\" LeaseSet"
+
+#: 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 ""
+"Этот алгоритмический прием может быть применим только к тем приложениям, "
+"которые хотят \n"
+"получать ответ от своих узлов (хотя он включает в себя все, что "
+"использует I2PTunnel или \n"
+"ministreaming библиотеку mihi):"
+
+#: 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 ""
+"Ранее, когда Alice отправила сообщение Bob'у, когда Bob отвечал, он был "
+"вынужден \n"
+"выполнить поиск в сетевой базе данных - отправляя несколько запросов "
+"чтобы добраться \n"
+"до текущего LeaseSet Alice. Если у него уже есть текущий LeaseSet Alice, "
+"он может вместо этого \n"
+"сразу отправить свой ответ - из-за этого (частично) вы обычно тратите "
+"немного больше \n"
+"времени для обращения к кому-то в первый раз, но последующие обращения \n"
+"проходят быстрее. Сейчас - для всех клиентов - мы упаковываем \n"
+"текущий LeaseSet отправителя в garlic, который доставляется получателю, \n"
+"и когда он соберется ответить, у него всегда будет локально "
+"хранимый LeaseSet - \n"
+"это полностью исключает необходимость поиска по сетевой базе данных при "
+"ответах. \n"
+"Это сохраняет большую часть пропускной полосы отправителя для такого "
+"быстрого ответа.\n"
+"Если мы делаем это не очень часто, \n"
+"общее использование пропускной полосы сети может уменьшиться, т.к. "
+"получателю не нужно \n"
+"выполнять поиск по сетевой базе данных."
+
+#: 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 ""
+"Для неопубликованных LeaseSets, таких как \"shared clients\", есть только"
+" один способ \n"
+"доставить LeaseSets Bob'у. К сожалению, это связывание каждый раз "
+"добавляет \n"
+"почти 100% накладных расходов на высокоскоростное соединение, и "
+"гораздо больше \n"
+"для соединений с меньшими сообщениями."
+
+#: 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 ""
+"Изменения запланированные в релиз 0.6.2 будут отправлять LeaseSet только "
+"при \n"
+"необходимости, в начале соединения или когда изменится LeaseSet.\n"
+"Это значительно уменьшит общие накладные расходы системы сообщений I2P."
+
+#: i2p2www/pages/site/about/performance/history.html:66
+msgid "More efficient TCP rejection"
+msgstr "Более эффективное отклонение TCP запросов"
+
+#: i2p2www/pages/site/about/performance/history.html:68
+#, fuzzy
+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 ""
+"На данный момент все TCP соединения выполняют все проверки узлов после \n"
+"прохождения через полную (избыточную) процедуру рукопожатия Diffie-"
+"Hellman чтобы \n"
+"договориться о закрытом сессионном ключе. Это означает что, если у "
+"кого-то системные часы идут неверно или \n"
+"настройки его NAT/брандмауэра/и т.п. неверны (или у них запущена \n"
+"несовместимая версия маршрутизатора), они будут вынуждены очень часто "
+"(хотя и \n"
+"не постоянно, благодаря shitlist) выполнять бесполезные дорогие операции "
+"шифрования \n"
+"над всеми узлами, которые им известны. В то время как мы захотим "
+"сохранить некоторую \n"
+"верификацию/валидацию в рамках шифрования, мы захотим обновить протокол,"
+" \n"
+"чтобы он выполнял что-то из этого в первую очередь, т.о. мы сможем "
+"запросто отвергать их \n"
+"без траты впустую CPU или его ресурсов."
+
+#: 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 ""
+"Вместо использования теперешней довольно случайной схемы, мы должны \n"
+"использовать более контекстный алгоритм для проверки туннелей, т.к., если"
+" мы уже знаем, что \n"
+"он передает данные корректно, то нет необходимости проверять его, и, если"
+" мы давно \n"
+"не получали из него данных, возможно, стоит воспользоваться им для \n"
+"отправки. Это уменьшит конкуренцию туннелей из-за избытка сообщений, а "
+"также \n"
+"улучшит скорость, с которой мы определяем - и фиксируем - ошибочные "
+"туннели."
+
+#: 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 ""
+"Выбор исходящего туннеля реализован в 0.6.1.30, выбор срока аренды "
+"входящего \n"
+"реализован в релизе 0.6.2."
+
+#: 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 ""
+"Случайны выбор туннелей и сроков аренды для каждого сообщения создает "
+"большое количество \n"
+"случаев доставки не-по-очереди, что мешает потоковой библиотеке \n"
+"увеличивать размер ее окна до максимума. При сохранении \n"
+"выбора для одного соединения скорость передачи намного больше."
+
+#: 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 ""
+"Сообщения I2NP и их содержимое уже определены и имеют довольно \n"
+"компактную структуру, хотя один атрибут структуры RouterInfo не \n"
+"\"настраиваемый\" - это соответствие имя = значение в виде ASCII. Сейчас,"
+" мы заполняем ее \n"
+"публичной статистикой - около 3300 байт на узел. Простое \n"
+"применение сжатия GZip позволит сократить ее размер до 1/3, и когда вы \n"
+"поймете как часто структуры RouterInfo передаются по сети, вы увидите что"
+" \n"
+"это будет значительным выигрышем - каждый раз когда маршрутизатор "
+"запрашивает у другого содержимое \n"
+"сетевой БД, которого нет у узла, он получает 3-10 записей RouterInfo."
+
+#: i2p2www/pages/site/about/performance/history.html:117
+msgid "Update the ministreaming protocol"
+msgstr "Обновление протокола ministreaming"
+
+#: 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 ""
+"Сейчас у библиотеки минипотоков mihi есть довольно простой потоковый "
+"протокол \n"
+"согласования - Alice отправляет Bob'у сообщение SYN, Bob отвечает "
+"сообщением ACK, затем \n"
+"Alice и Bob обмениваются данными, до тех пор пока один из них не отправит"
+" другому \n"
+"сообщение CLOSE. Для длительных подключений (например, для IRC сервера),"
+" \n"
+"эти издержки незначительны, но для некоторых простых ситуаций "
+"запрос-ответ \n"
+"(например, запрос/ответ HTTP), приходится отправлять вдвое больше "
+"сообщений, чем это \n"
+"необходимо. Если, тем не менее, Alice комбинирует свою отправку с "
+"сообщением SYN, \n"
+"и Bob комбинирует его первый ответ с ACK - и, возможно, также включит "
+"флаг CLOSE - \n"
+"временные потоки, такие как запросы HTTP, могут быть сокращены \n"
+"до пары сообщений, вместо SYN+ACK+запрос+ответ+CLOSE."
+
+#: 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 ""
+"Протокол минипотоков унаследовал преимущества плохого проектного решения"
+" \n"
+"клиентского протокола I2P (I2CP) - иллюстрация \"mode=GUARANTEED\", "
+"позволяющая то, \n"
+"что иначе было бы ненадежным, негарантированным, протокол на основе "
+"сообщений \n"
+"используюется для надежной, блокирующей операции (приоткрывая покров, оно"
+" все равно остается \n"
+"ненадежным и основанным на сообщениях, с гарантиями доставки, "
+"предоставляемыми маршрутизатором с помощью \n"
+"чесночной маршрутизации данных с сообщением \"ACK\" внутри, так что когда"
+" данные доходят до получателя, \n"
+"сообщение ACK отправляется обратно к нам [через туннели, естественно])."
+
+#: 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 ""
+"Как я уже сказал, наличие \n"
+"I2PTunnel (и библиотеки минипотоков) было наилучшим путем из всех "
+"возможных,\n"
+"но доступен и более эффективный механизм. Когда мы выпиливаем \n"
+"функциональность \"mode=GUARANTEED\", мы в сущности оставляем себе \n"
+"I2CP, который выглядит как анонимный уровень IP, и, т.о., мы сможем \n"
+"реализовать в потоковой библиотеке преимущества архитектурного опыта \n"
+"слоя TCP - селективные ACK, обнаружение коллизий, nagle и т.д."
+
+#: 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 ""
+"Как работает I2P, почему она медленная, и почему она не использует мой "
+"канал полностью?"
+
+#: 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 ""
+"Вероятно один и самых часто задаваемых вопросов это \"насколько быстра "
+"I2P?\", \n"
+"и похоже никому не нравится ответ - \"это зависит\". После опробования "
+"I2P, \n"
+"следующим вопросом становится \"а быстрее будет?\", и ответом на это "
+"служит \n"
+"самое решительно да."
+
+#: 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 ""
+"I2P это полностью динамическая сеть. Каждый клиент известен другим узлам,"
+" и проверяет локальные известные узлы на доступность и "
+"производительность. \n"
+"Только доступные и производительные узлы добавляются в локальную NetDB (В"
+" основном это только часть сети, около 500-1000).\n"
+"Когда I2P строит туннели, она выбирает лучший ресурс из этого пула. "
+"Например, только маленький набор из 20-50 узлов доступен для постройки "
+"туннелей к ним.\n"
+"Из-за того что проверки выполняются каждую минуту, пул используемых узлов"
+" изменяется каждую минуту.\n"
+"Каждым узлам I2P известны различные части сети, т.о. каждый маршрутизатор"
+" имеет свой набор узлов I2P для туннелей.\n"
+"Даже если два маршрутизатора имеют одинаковый набор известных узлов, "
+"проверка на доступность и производительность покажет, скорее всего, "
+"различные результаты, т.к. другие маршрутизаторы могут быть под нагрузкой"
+" во время проверок первого маршрутизатора, но свободными во время "
+"проверок второго."
+
+#: 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 ""
+"Описанное выше объясняет почему каждый узел I2P имеет отличный от других "
+"набор узлов для постройки туннелей.\n"
+"Из-за того что каждый узел I2P имеет свои задержки и полосу пропускания, "
+"туннели (которые строятся через эти узлы) имеют различные значения "
+"задержки и ширины канала.\n"
+"И из-за того что каждый узел I2P строит свои туннели, нет ни одной пары "
+"узлов I2P с одинаковым набором туннелей."
+
+#: 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 ""
+"Сервер/клиент известны как \"пункт назначения\", и у каждого пункта "
+"назначения есть по крайней мере один входящий и один исходящий туннель. "
+"По умолчанию на туннель приходится 3 участка.\n"
+"Это добавляет до 12 участков (aka 12 различных узлов I2P) в полный путь "
+"клиент-сервер-клиент."
+
+#: 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 ""
+"Каждый пакет данных отправляет через 6 других узлов I2P до того как он "
+"достигнет сервера:"
+
+#: i2p2www/pages/site/about/performance/index.html:40
+msgid "and on way back 6 different I2P nodes:"
+msgstr "и на пути обратно 6 различных узлов I2P:"
+
+#: 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 ""
+"В большинстве случаев трафик в I2P (www, torrent, ...) нуждается в пакете"
+" ack до отправки данных, необходимо дождаться  пока пакет ack вернется с "
+"сервера.\n"
+"В конце: отправка данных, дождаться ack, отправить еще данных, дождаться "
+"ack, ...\n"
+"Т.к. RTT (RoundTripTime) складывается из задержек на каждом конкретном "
+"узле I2P и каждом соединении на этом пути, то обычно время получения "
+"пакета ack обратно на клиенте составляет 1-3 секунды.\n"
+"С некоторыми добавками транспортов TCP и I2P пакет данных имеет "
+"ограничение на размер, и он не может быть таким большим как мы того "
+"хотим.\n"
+"Вместе эти условия накладывают ограничение на максимальную пропускную "
+"способность на туннель - 20-50 Кбайт/с.\n"
+"Но если ТОЛЬКО у ОДНОГО участка туннеля есть 5 свободных кб/с, весь "
+"туннель будет ограничен до 5 кб/с, независимо от \n"
+"задержек и других ограничений."
+
+#: 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 ""
+"Из-за использования шифрования и других надстроек I2P (как то - "
+"построение туннелей, задержки, ...) построение туннеля является "
+"достаточно дорогим для времени CPU. \n"
+"Вот почему пункту назначения разрешено иметь максимум 6 входящих и 6 "
+"исходящих туннелей для передачи данных. С максимальной скоростью 50 кб/с "
+"на туннель пункт назначения может \n"
+"использовать приблизительно 300 кб/с комбинированного трафика (в "
+"действительности, может быть больше, если используются более короткие "
+"туннели с меньшей или отсутствующей анонимностью).\n"
+"Используемые туннели сбрасываются каждые 10 минут и строятся новые.\n"
+"Эти изменения туннелей (и иногда клиенты выполняют жесткое выключение при"
+" использовании \"shut down at once\" или в ситуации с выключением "
+"питания) \n"
+"иногда разрушают туннели и соединения, как это можно увидеть в сети IRC2P"
+" при потере соединения (ping timeout) или при использовании eepget."
+
+#: 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 ""
+"При ограниченном наборе пунктов назначения и туннелей для пункта "
+"назначения один узел I2P использует только ограниченный набор туннелей с "
+"другими узлами I2P.\n"
+"Например, если узел I2P это \"hop1\" и маленьком примере выше, то мы "
+"видим только 1 участвующий туннель порожденный клиентом.\n"
+"Если мы сложим всю сеть I2P, то сможем построить только ограниченное "
+"число участвующих туннелей с ограниченной пропускной способностью.\n"
+"Если кто-то предоставить это ограниченное число туннелей набору узлов "
+"I2P, то только часть пропускной способности/мощности будет доступна для "
+"использования."
+
+#: 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 ""
+"Чтобы остаться анонимным один маршрутизатор не должен быть использован "
+"всей сетью для построения туннелей.\n"
+"Если один маршрутизатор выступает в качестве туннельного маршрутизатора "
+"для ВСЕХ узлов I2P, то он становится как узким местом, так и центром "
+"сбора адресов IP и данных от клиентов. Это не хорошо.\n"
+"По этой причине I2P пытается распределить нагрузку на большое число узлов"
+" I2P."
+
+#: 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 ""
+"Другая цель - это полносвязная сеть. Каждое соединение hop-hop использует"
+" одно соединение TCP или UDP между узлами I2P. При 1000 соединений, видны"
+" \n"
+"1000 соединений TCP. Это довольно много, и какой-нибудь домашний или "
+"маленький офисный маршрутизатор (DSL, кабельный, ...) допускает только "
+"маленькое количество соединений (или даже сойдет с ума при использовании "
+"более чем X соединений).\n"
+"I2P старается ограничить эти соединения до 1500 для UDP или TCP.\n"
+"Также это ограничивает объем трафика через ваш узел I2P."
+
+#: 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 ""
+"В общем, I2P очень сложна и нет простого способа выяснить почему ваш узел"
+" не задействован.\n"
+"Если ваш узел доступен в режиме 24/7 и имеет настройку доступной полосы "
+"пропускания >128 Кбайт/с, он должен быть использован после передачи "
+"некоторого количества трафика.\n"
+"Если есть обрыв связи, проверка вашего I2P узла, выполненная другими "
+"узлами, скажет им: вы не доступны. Это приведет к блокировке вашего узла "
+"по крайней мере \n"
+"на 24 часа на других узлах. Итак, другие узлы, которые пометили вас как "
+"недоступный, не будут использовать ваш узел для постройки туннелей в "
+"течение 24 часов. \n"
+"Вот почему ваш трафик будет меньше после перезапуска/выключения как "
+"минимум в течение 24 часов."
+
+#: 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 ""
+"Также: другим узлам I2P должен быть известен ваш маршрутизатор I2P чтобы "
+"иметь возможность  проверять его доступность и производительность. "
+"Требуется время для того чтобы ваш узел стал известен. \n"
+"Оно станет быстрее, если вы используете I2P и строите больше туннелей, "
+"например, используйте время от времени торрент или www."
+
+#: 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 ""
+"Возможные будущие улучшения производительности смотри на странице \n"
+"Будущие Улучшения Производительности."
+
diff --git a/i2p2www/translations/ru/LC_MESSAGES/blog.po b/i2p2www/translations/ru/LC_MESSAGES/blog.po
new file mode 100644
index 00000000..1bb79840
--- /dev/null
+++ b/i2p2www/translations/ru/LC_MESSAGES/blog.po
@@ -0,0 +1,1793 @@
+# Russian (Russia) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# keedley , 2013
+# sassy , 2013
+# Арефьев Денис , 2013
+# Narengoyn , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-12 06:16+0000\n"
+"PO-Revision-Date: 2013-12-12 06:18+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: Russian (Russia) "
+"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 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/blog/2011/10/11/0.8.9-Release.rst:24
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:25
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:12
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:12
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:17
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:16
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:16
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:26
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:19
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:19
+msgid "Files are available on the `download page`_."
+msgstr "Файлы доступны на `странице загрузки`_."
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:28
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:15
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:29
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:16
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:16
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:21
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:20
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:20
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:30
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:23
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:23
+msgid "`download page`"
+msgstr "`страница загрузки`"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:30
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:17
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:31
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:18
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:19
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:18
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:22
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:22
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:32
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:25
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:79
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:45
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:13
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:101
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:26
+msgid "RELEASE DETAILS"
+msgstr "ПОДРОБНОСТИ РЕЛИЗА"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:32
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:19
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:33
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:40
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:50
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:24
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:24
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:34
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:103
+msgid "Major Changes"
+msgstr "Основные изменения"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:44
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:24
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:43
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:55
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:47
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:58
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:43
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:32
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:30
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:39
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:81
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:54
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:112
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:34
+msgid "Bug Fixes"
+msgstr "Исправлены ошибки"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:54
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:30
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:47
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:69
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:63
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:68
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:54
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:41
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:36
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:51
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:43
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:94
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:63
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:19
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:118
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:52
+msgid "Other"
+msgstr "Другое"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:73
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:36
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:51
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:82
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:75
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:96
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:76
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:52
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:56
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:67
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:56
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:110
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:79
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:30
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:129
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:27
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:76
+msgid "SHA256 Checksums:"
+msgstr "Ключевые суммы SHA256"
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39
+msgid "Major changes"
+msgstr "Основные изменения"
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47
+msgid "Wrapper Update"
+msgstr "Обновление враппера"
+
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:23
+msgid "Update Info"
+msgstr "Информация об обновлении"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2
+msgid "0.9.2 Release"
+msgstr "Релиз 0.9.2"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9
+msgid ""
+"0.9.2 includes extensive low-level changes to improve the performance and"
+" efficiency of the router. We have updated our UPnP library, to hopefully"
+" make UPnP work for more people. I2PSnark now has DHT support, but it is "
+"not yet enabled by default, as we plan to do more testing during the "
+"upcoming 0.9.3 development cycle."
+msgstr ""
+"0.9.2 включает в себя значительное количество изменений для увеличения "
+"производительности и эффективности маршрутизатора. Мы обновили нашу "
+"библиотеку UPnP, надеемся, что она будет работать для большего числа "
+"случаев. I2PSnark получил поддержку DHT, но она по умолчанию выключена, "
+"так как мы надеемся ее активно тестировать в процессе разработки версии "
+"0.9.3."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12
+msgid ""
+"As usual, there's also lots of bug fixes in this release, so updating is "
+"recommended."
+msgstr ""
+"Как обычно, в этой версии исправлено много ошибок, поэтому рекомендуется "
+"обновление."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26
+msgid ""
+"SSU: Fix several problems in our UDP transport, to improve efficiency and"
+" reliability for connection setup. Also improve defenses against various "
+"types of bad input."
+msgstr ""
+"SSU: Исправлено несколько проблем в нашем UDP транспотре, для увеличения "
+"эффективности и надежности при установке соединения. Также улучшили "
+"защиту от разных типов плохих данных."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27
+msgid ""
+"UPnP: Updated our library to fix several issues, should work for more "
+"routers now"
+msgstr ""
+"UPnP: Обновлили нашу библиотеку, теперь должно работать для большего "
+"количества устройств."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28
+msgid ""
+"Transport: Improve performance in both our TCP and UDP transports, to "
+"benefit high-bandwidth routers"
+msgstr ""
+"Транспорт: Улучшили производительность TCP и UDP транспортов, особенно "
+"для маршрутизаторов на широких каналах."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29
+msgid ""
+"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered "
+"are now much more flexible, which should lessen protocol overhead and "
+"reduce stalls caused by dropped tags."
+msgstr ""
+"Crypto: Отсечки и количество меток сессий ElGamal/AES сейчас гораздо "
+"более гибкие, что должно сократить затраты протокола и уменьшить "
+"подвисания, связанные с потерянными метками."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30
+msgid ""
+"I2PSnark: Add DHT support, not yet enabled by default, will do further "
+"testing and plan to enable by default in 0.9.3."
+msgstr ""
+"I2PSnark: Добавлена поддержка DHT, не включена по умолчанию, будет "
+"тестироваться, планируем включить по умолчанию в 0.9.3"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34
+msgid ""
+"Fix various issues affecting memory usage and performance on high-"
+"bandwidth routers"
+msgstr ""
+"Исправления ряда проблем с использованием памяти и производительностью на"
+" маршрутизаторах на широких каналах."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35
+msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN"
+msgstr ""
+"Исправлены проблемы в UDP для маршрутизаторов с уменьшенным MTU, например"
+" на VPN"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36
+msgid "Fix i2psnark bug that prevented a completion announcement to the tracker"
+msgstr ""
+"Исправлена проблема в i2psnark, которая мешала оповещению о завершении "
+"закачки на трекере. "
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37
+msgid "Fix a lock contention problem in i2ptunnel"
+msgstr "Исправлена проблема с блокировками в i2ptunnel"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38
+msgid "Fix some OSX installation issues"
+msgstr "Исправлены некоторые проблемы при инсталляции в OSX"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39
+msgid "Remove uses of direct byte buffers that may have been leaking"
+msgstr ""
+"Избавились от использования direct byte buffers, которые могли утекать по"
+" памяти"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43
+msgid "Reduce overhead in network messages"
+msgstr "Уменьшены затраты протокола в сетевых сообщениях"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44
+msgid "Add \"universal\" theme support"
+msgstr "Добавлена поддержка темы \"universal\""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45
+msgid "Theme updates"
+msgstr "Обновления тем"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46
+msgid "Add a jbigi library for Raspberry Pi"
+msgstr "Добавлена библиотека jbigi, оптимизированная для Rapspberry Pi"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47
+msgid "New Scala unit test framework"
+msgstr "Новая оснастка для юнит тестов Scala"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48
+msgid "Translation updates for Czech, Dutch, German, and Greek"
+msgstr ""
+"Обновления переводов для чешского, голландского, немецкого и греческого "
+"языков"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49
+msgid "Update wrapper to 3.5.15 (new installs and PPA only)"
+msgstr "Враппер обновлен до 3.5.15 (для новых инсталляций и PPA)"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:77
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:127
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:74
+msgid "Update GeoIP data (new installs and PPA only)"
+msgstr "Обновлены данные GeoIP (для новых инсталляций и PPA)"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:2
+msgid "0.9.3 Release"
+msgstr "0.9.3 Релиз"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9
+msgid ""
+"0.9.3 includes extensive low-level changes to the queueing of messages in"
+" the router.  We implement the CoDel Active Queue Management (AQM) "
+"algorithm.  We also unify the queueing and priority mechanisms in the "
+"transports to aid diagnosis and reduce network latency.  Work continues "
+"on fixing UDP transport bugs and making UDP more resistant to attacks.  "
+"There are more changes to improve the performance of the router and "
+"reduce its memory usage.  Also, we enable i2psnark's DHT support, "
+"introduced last release, by default."
+msgstr ""
+"Релиз 0.9.3 включает значительные изменения на низком уровне в работе с "
+"очередями сообщений в маршрутизаторе. Мы реализовали алгоритм CoDel "
+"Active Queue Management (AQM). Унифицировали работу с очередями и "
+"приоритетами в транспортах для облегчения диагностики и снижения сетевых "
+"задержек. Продолжается работа с проблемами в UDP транспорте, чтобы "
+"сделать UDP более устойчивым к возможным атакам. Значительные изменения "
+"сделаны, чтобы роутер работал эффективнее и с меньшей нагрузкой на "
+"память. Также мы включили DHT в i2psnark по умолчанию."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26
+msgid "Active Queue Management"
+msgstr "Active Queue Management"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:27
+msgid "Priority queues"
+msgstr "Приоритетные очереди"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28
+msgid "I2PSnark DHT: Several bug fixes, enable by default."
+msgstr "I2PSnark DHT: исправления нескольких проблем, включили по умолчанию."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32
+msgid ""
+"Several SSU fixes including memory leak, and better handling of routers "
+"behind firewalls that change UDP ports; additional defenses for malicious"
+" packets."
+msgstr ""
+"Ряд исправлений проблем в SSU, включая утечку памяти, более правильная "
+"обработка роутеров за файрволлами которые меняют UDP порты, "
+"дополнительные защиты от намеренно плохих пакетов."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33
+msgid "Fix piece selection (rarest-first) bugs in i2psnark"
+msgstr "Исправлен выбор части (редкие вперед) в i2psnark"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34
+msgid "Fix bug causing multiple browsers to open at startup"
+msgstr "Исправлена проблема, приводящая к открытию нескольких браузеров на старте"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38
+msgid "Improvements in caching"
+msgstr "Улучшения в кэшировании"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39
+msgid "Several synchronization fixes and lock contention reduction"
+msgstr ""
+"Несколько исправлений в синхронизации и уменьшении использования "
+"блокировок"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40
+msgid "Major reduction in SSU buffers memory use"
+msgstr "Большое снижение потребления памяти в SSU буферах"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41
+msgid ""
+"Fix streaming connection timeout back to 1 minute, was inadvertently "
+"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was"
+" unlimited"
+msgstr ""
+"Таймаут потоковых соединений установлен в 1 минуту, ранее был 5 минут. "
+"Таймаут чтения i2ptunnel server установлен в 5 минут, было без "
+"ограничений"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42
+msgid "Improved defenses in i2ptunnel for \"darkloris\""
+msgstr "Улучшили защиту от \"darkloris\" в i2ptunnel"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:43
+msgid "More validation at torrent creation in i2psnark"
+msgstr "Больше проверок при создании торрента в i2psnark"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44
+msgid "Several parameter changes in SSU to improve throughput"
+msgstr "Несколько изменений параметров в SSU для увеличения пропускной способности"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45
+msgid ""
+"New event log for major events including restarts; show multiple restart "
+"lines on graphs"
+msgstr ""
+"Новый журнал для важных событий, включая перезапуски; показываем "
+"несколько моментов перезапусков на графиках"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46
+msgid "Remove duplicate messages from logs"
+msgstr "Удалены повторяющиеся сообщения в журнале"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47
+msgid "Don't respond to blocked streaming connections with a reset, just drop"
+msgstr ""
+"Не отвечать на заблокированные потоковые соединения reset, просто закрыть"
+" соедиение"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48
+msgid "Remove all uses of inefficient SimpleTimer"
+msgstr "Удалить все использование неэффективного SimpleTimer"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49
+msgid "More checks for valid IPs and ports entered in console"
+msgstr "Больше проверок на валидность IP и портов, введенных в консоли"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50
+msgid "Fix bug that wasted a lot of entropy"
+msgstr "Исправлена проблема что приводила к расходу энтропии"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51
+msgid "Translation updates: Italian, Portuguese, Spanish, Swedish"
+msgstr "Обновлены переводы: Итальянский, Португальский, Испанский, Шведский"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52
+msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5"
+msgstr "Добавить не-NIO настройки в jetty.xml, рекомендованные для Java 5"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2
+msgid "0.9.4 Release"
+msgstr "Версия 0.9.4"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9
+msgid ""
+"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, "
+"that was reducing network performance and reliability. It also includes "
+"major changes in the in-network update system, and adds the capability to"
+" update via in-network torrents."
+msgstr ""
+"Версия 0.9.4 включает исправление для проблемы пропускной способности "
+"сети, внесенной в 0.9.2, что приводила к снижению производительности и "
+"надежности сети. Также включае большие изменения в системе обновления и "
+"добавляет возможность обновления через внутрисетевые torrent'ы"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13
+msgid ""
+"We fixed several bugs in the i2psnark DHT implementation that was "
+"introduced\n"
+"last release. For those of you using console or http proxy passwords,\n"
+"we converted to the more-secure digest method and improved the security "
+"for console forms."
+msgstr ""
+"Мы исправили несколько проблем в реализации DHT в i2psnark, которые были "
+"внесены\n"
+"в последнем релизе. Для тех, кто использует пароли на консоль или "
+"прокси-сервер,\n"
+"мы сконвертировали их в более безопасный дайджест, а также улучшили "
+"безопасность форм."
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19
+msgid ""
+"For those of you already running development builds, your router should "
+"automatically\n"
+"update to 0.9.4-0 using the new in-network torrent facility.\n"
+"For those running 0.9.3-0, you will update normally using in-network "
+"HTTP, and\n"
+"we will have more information for you when we release 0.9.5."
+msgstr ""
+"Для тех, кто уже работает с девелоперскими сборками, ваш маршрутизатор "
+"должен автоматически\n"
+"обновиться до 0.9.4.-0, используя новый механизм внутрисетевых торрентов."
+"\n"
+"Для тех, кто пользуется 0.9.3-0, обновитель через внутрисетевой HTTP,  и\n"
+"для вас будет больше информации, когда мы выпустим 0.9.5"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36
+msgid ""
+"Big rework of the update system; Preliminary support for updates via "
+"i2psnark"
+msgstr ""
+"Крупная переделка системы обновлений; Предварительная поддержка для "
+"обновлений через i2psnark"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37
+msgid "Add per-destination outbound priorities"
+msgstr "Добавить исходящие приоритеты для каждого назначения"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41
+msgid ""
+"Fix major bug that reduced SSU connection limits which reduced tunnel "
+"build success rates"
+msgstr ""
+"Исправить крупную проблему, которая уменьшала ограничения на соединения, "
+"что приводило к уменьшению качества построения туннелей"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42
+msgid "Fix bug with external I2CP that prevented some external apps from working"
+msgstr ""
+"Исправить проблему с внешним I2CP, которая мешала ряду внешний приложений"
+" работать"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43
+msgid "Fixed several bugs in i2psnark DHT"
+msgstr "Исправлено несколько проблем в реализации DHT в i2psnark"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44
+msgid "Fixed bug in i2psnark PEX that inflated peer counts"
+msgstr "Исправлена проблема в i2psnark PEX, которые увеличивали счетчик узлов"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45
+msgid "Handle dropped I2CP messages better"
+msgstr "Лучше обрабатывать отбитые I2CP сообщения"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46
+msgid "Reduce overhead of I2CP messages"
+msgstr "Уменьшить затраты протокола в I2CP сообщениях"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47
+msgid "Enforce max size in transport outbound message queues"
+msgstr ""
+"Усилить требования к максимальному размеру в исходящих очередях сообщений"
+" транспорта"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48
+msgid "Fixes for Windows eepget.bat (new installs and PPA only)"
+msgstr "Исправления для Windows eepget.bat (новые инсталляции и PPA)"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49
+msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU"
+msgstr ""
+"Исправить проблему что приводила к потерям сообщений размером ровно 512 "
+"байт"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53
+msgid ""
+"More performance improvements, memory reduction, and object churn "
+"reduction"
+msgstr ""
+"Больше улучшений производительности, уменьшения расхода памяти и расхода "
+"ресурсов на постоянное пересоздание объектов"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54
+msgid "Better detection of network disconnections"
+msgstr "Лучшее определение сетевых рассоединений"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55
+msgid "Further improvements in the SSU transport"
+msgstr "Улучшения в SSU транспорте"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56
+msgid "Add console password form"
+msgstr "Добавить форму консольного пароля"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57
+msgid ""
+"Convert http proxy and console from basic to digest authentication for "
+"added security"
+msgstr ""
+"Для увеличения безопасности перейти к digest авторизации для консоли и "
+"http-прокси"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58
+msgid ""
+"Improved verification of console form submissions, using jsp sessions. "
+"Cookies may now be required on forms, except when the console password is"
+" enabled"
+msgstr ""
+"Улучшенная проверка для форм консоли, используя jsp сессии. Куки могут "
+"быть необходимы на формах, кроме тех случаев, когда включен пароль на "
+"консоль"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59
+msgid ""
+"Initial work on new interfaces to manage applications started via "
+"clients.config"
+msgstr ""
+"Первоначальная работа над новыми интерфейсами управления приложениями, "
+"запускаемыми через clients.config"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60
+msgid "Increase minimum peer port to 1024"
+msgstr "Увеличен минимальный номер порта на узле до 1024"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61
+msgid "Increase granularity of bandwidth limiter for smoother transmissions"
+msgstr ""
+"Увеличение гранулярности ограничителя полосы для более ровной передачи "
+"данных"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62
+msgid ""
+"Translation updates: Chinese, French, German, Italian, Polish, "
+"Portuguese, Swedish, and Ukrainian"
+msgstr ""
+"Обновлены переводы: китайский, французский, немецкий, итальянский, "
+"польский, португальский, шведский и украинский"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64
+msgid "Update wrapper to 3.5.16 (new installs and PPA only)"
+msgstr "Враппер обновлен до 3.5.16 (для новых инсталляций и PPA)"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65
+msgid "New ARMv6 wrapper for Raspberry Pi"
+msgstr "Новый ARMv6 враппер для Raspberry Pi"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:2
+msgid "0.9.5 Release"
+msgstr "Версия 0.9.5"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9
+msgid ""
+"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities"
+" that are being investigated by researchers at UCSB. We continue to work "
+"with them on additional improvements. This is a good opportunity to "
+"remind the community that while our network continues to grow rapidly, it"
+" is still relatively small. There may be multiple weaknesses or bugs that"
+" could compromise your anonymity. Help us grow the network by spreading "
+"the word and contributing where you can."
+msgstr ""
+"Версия 0.9.5 включает исправления проблем и защиту от ряда уязвимостей, "
+"которые были исследованы специалистами в UCSB. Мы продолжаем работу "
+"вместе с ними над дополнительными улучшениями. Это хорошая возможность "
+"напомнить публике, что хотя наша сеть продолжает быстро расти, она все "
+"еще относительно невелика. Возможно, что присутствуют проблемы или "
+"ошибки, которые могут скомпрометировать вашу анонимность. Помогите нам "
+"увеличить сеть, распространяя информацию и принося свой вклад, какой вы "
+"можете сделать."
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13
+#, python-format
+msgid ""
+"In this upgrade cycle, a random 1% of routers, (plus all routers running "
+"a\n"
+"development build) will attempt to update via the experimental in-network"
+" bittorrent\n"
+"with i2psnark. If this doesn't work, it should fall back to standard in-"
+"network HTTP update."
+msgstr ""
+"В этом цикле обновлений 1% o случайных роутеров (плюс все роутеры, "
+"работающие на\n"
+"версии для разработчиков) будут пытаться обновиться через "
+"экспериментальный внетрисетевой bittorent\n"
+"с помощью i2psnark. Если это не сработает, обновление должно произойти "
+"через стандартный внутрисетевой HTTP."
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27
+msgid "Defenses and Bug Fixes"
+msgstr "Защита и исправление ошибок"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29
+msgid "Fix router bug causing lockup when using iMule"
+msgstr ""
+"Исправлена проблема в маршрутизаторе, приводившая к подвисанию при "
+"использовании iMule"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30
+msgid "Recognize, handle, reject duplicate tunnel IDs"
+msgstr "Узнаем, обрабатываем и отклоняем дублированный ID туннелей"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31
+msgid "Fix changing of the log file name"
+msgstr "Исправляем смену имени журнального файла"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32
+msgid "Prevent hashcode attack in session tags"
+msgstr "Предотвращаем hashcode attack в метках сессий"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33
+msgid "Add build request throttler based on previous hop"
+msgstr "Добавить регулятор запроса построения на основании предыдущего прыжка"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34
+msgid "Limit concurrent next-hop lookups"
+msgstr "Ограничиваем конкуррентные поиски следующего узла"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35
+msgid "Catch exceptions storing nonces in console"
+msgstr "Перехватываем исключения при сохранении в консоли"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36
+msgid "Fix saving graph settings in console"
+msgstr "Исправление настроек графиков в консоли"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37
+msgid "Fix eepget generation of URLs when not proxied"
+msgstr "Исправление генерации URL в eepget, когда работаем без прокси"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38
+msgid ""
+"Encrypt database lookup messages end-to-end when sent through exploratory"
+" tunnels"
+msgstr ""
+"Зашифровать сообщения поиска по базе данных от точки до точки при работе "
+"через исследующие туннели"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39
+msgid "Don't use multiple floodfills from the same /16 in a query"
+msgstr "Не использовать множественные floodfills из одной подсети /16  в запросе"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40
+msgid "Randomize delay before verifying floodfill store"
+msgstr "Сделать случайную задержку перед проверкой хранилища floodfill"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41
+msgid "Increase number of floodfills"
+msgstr "Увеличить количество floodfill"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:45
+msgid "Improve support for mobile browsers"
+msgstr "Улучшить поддержку мобильных браузеров"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46
+msgid "Partial defenses for UCSB attacks"
+msgstr "Частичная защита от UCSB аттак"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47
+msgid "Add announce list support to i2psnark"
+msgstr "Добавить поддержку списка анонсов в i2psnark"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48
+msgid "Jetty: upgrade Apache Tomcat to 6.0.36"
+msgstr "jetty: обновить Apache Tomcat до 6.0.36"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49
+msgid "Split router info files into multiple subdirectories"
+msgstr "Разделить файлы маршрутизатора по нескольким поддиректориям"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50
+msgid "Add IP to hostname mapping option in SOCKS"
+msgstr "Добавить в SOCKS возможность распознавать IP в hostname"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51
+msgid "Improve PRNG seeding"
+msgstr "Улучшить запуск генератора случайных чисел"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52
+msgid ""
+"Translation updates: French, German, Hungarian, Italian, Norwegian, "
+"Polish, Portuguese, Russian, Swedish"
+msgstr ""
+"Обновления переводов: французский, немецкий, венгерский, итальянский, "
+"норвежский, польский, португальский, шведский"
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54
+msgid "Update wrapper to 3.5.17 (new installs and PPA only)"
+msgstr "Обновить враппер до 3.5.17 (новые инсталляции и PPA)"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:2
+msgid "0.9.6 Release"
+msgstr "Версия 0.9.6"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:7
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9
+msgid ""
+"0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to "
+"Jetty 7.6.10 (2013-03-12). See below for important information on the "
+"Jetty update. The Jetty 7 series is actively maintained and we plan to "
+"stay current with it in future I2P releases."
+msgstr ""
+"Версия 0.9.6 включает в себя исправления и обновление  jetty c  Jetty "
+"6.1.26 (2010-11-10) до 7.6.10 (2013-03-12). Смотрите ниже важную "
+"информацию про обновление jetty. Jetty версии 7 активно поддерживается и "
+"мы планируем последовательно обновлять версию до последней при будущих "
+"релизах I2P."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13
+msgid ""
+"Most users will update via HTTP. Those running development builds will "
+"attempt to update via the\n"
+"experimental in-network bittorrent with i2psnark. We've fixed some bugs "
+"that will enable more users\n"
+"to update via torrent in the 0.9.7 update cycle."
+msgstr ""
+"Большинство пользователей будут обновляться через HTTP. Те, кто работает "
+"на девелоперских сборках будут пытаться обновляться через внутрисетевой "
+"bittorrent с помошью i2psnark. Мы починили несколько проблем, это "
+"позволит большему количеству пользователей обновиться через torrent в "
+"процессе развития 0.9.7."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25
+msgid "Important fix for Windows Eepsites, first install 0.9.5 only"
+msgstr "Важное исправление для Eepsite под Windows изначально запущенных под 0.9.5"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27
+msgid ""
+"If you first installed I2P with version 0.9.5, on Windows only, we "
+"recommend that you follow the\n"
+"following instructions to fix your eepsite location **before** you update"
+" to 0.9.6.\n"
+"Only original installations of 0.9.5-0 on Windows are affected by this "
+"issue. If your router version\n"
+"is 0.9.5-0-win1, you already have the fix and need not take any action."
+msgstr ""
+"Если вы впервые запустили I2P на версии 0.9.5 под Windows (только это "
+"сочетание), мы рекомендуем \n"
+"проделать действия по инструкции чтобы сменить расположение сайта **до** "
+"обновления на 0.9.6.\n"
+"Только изначально установленные на 0.9.5-0 на Windows сайты подвержены "
+"этой проблеме. Если версия маршрутизатора \n"
+"0.9.5-0-win1, то у вас уже все хорошо и ничего делать дополнительно не "
+"надо."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34
+msgid "See `this page`_ for instructions."
+msgstr "См. `this page`_ для инструкций."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:38
+msgid "`this page`"
+msgstr "`эта страница`"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:40
+msgid "Jetty 7 Migration Details"
+msgstr "Порядок миграции на Jetty 7"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42
+msgid ""
+"For most people, the update should just work. If you have multiple Jetty "
+"eepsites,\n"
+"OR have made changes to jetty.xml or other Jetty configuration files, "
+"including changing the port\n"
+"from 7658, you MUST take manual action AFTER updating."
+msgstr ""
+"Для большинсва людей, просто должен пройти процесс обновления и все. Если"
+" у вас несколько eepsite'ов на jetty?\n"
+"ИЛИ вы сделали изменения в jetty.xml или других конфигурационных файлах "
+"jetty, включая смену порта с 7658,\n"
+"вы ДОЛЖНЫ предпринять действия вручную ПОСЛЕ обновления."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48
+msgid ""
+"After update, the router will migrate your jetty.xml files to the new "
+"Jetty 7 format."
+msgstr ""
+"После обновления, маршрутизатор перенесет ваш jetty.xml в новый формат "
+"для jetty 7."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50
+msgid ""
+"The migration resets the port to 7658. If you have more than one Jetty "
+"eepsite, OR your eepsite\n"
+"  is NOT on port 7658, OR you have made other modifications to jetty.xml "
+"(for example changing the\n"
+"  listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml "
+"file for each eepsite to fix them up\n"
+"  after updating, and restart again."
+msgstr ""
+"Процесс миграции скинет порт на 7658. Если у вас более одного eepsite, "
+"ИЛИ ваш сайт\n"
+"НЕ на порту 7658, ИЛИ вы сделали другие изменения в jetty.xml (например, "
+"сменили адрес сервера с 127.0.0.1 на 0.0.0.0), вы ДОЛЖНЫ отредактировать "
+"jetty.xml для всех eepsite'ов и внести эти изменения снова,\n"
+"после обновления и снова перезапустить сайты. "
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55
+msgid ""
+"**The following files will be backed up with a ".jetty6" suffix"
+" and then migrated.**\n"
+"If you have made local changes, you may have to edit them manually and "
+"restart.\n"
+"See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7."
+msgstr ""
+"**Следующие файлы будут сохранены с суффиксом ".jetty6"  и "
+"затем изменены в новый формат**\n"
+"Если вы ранее делали локальные изменения в них, вы должны повторить эти "
+"изменения в новом формате и перезапуститься\n"
+"См. http://wiki.eclipse.org/Jetty для справки по настройкам Jetty 7."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69
+msgid "Plugins"
+msgstr "Плагины"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:71
+msgid "Most plugins should work fine with Jetty 7."
+msgstr "Большинство плагинов должно нормально работать с Jetty 7"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:75
+msgid ""
+"The I2PControl and zzzot plugins must be updated. Your router should "
+"download and install the new versions shortly after starting 0.9.6."
+msgstr ""
+"Плагины I2PControl и zzzot должны быть обновлены. Ваш маршрутизатор "
+"должен скачать и установить новые версии вскоре после запуска 0.9.6."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77
+msgid "If a plugin does not work, please contact the maintainer for that plugin."
+msgstr "Если плагин не работает, пожалуйста, свяжитесь с автором плагина."
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83
+msgid "Several bugs with Windows installation (see above)"
+msgstr "Несколько проблем на Windows инсталляциях (см. выше)"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:84
+msgid "Fix default form action in i2ptunnel"
+msgstr "Исправить действие в форме по умолчанию в i2ptunnel"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85
+msgid "Fix links on iframed console pages"
+msgstr "Исправлены ссылки на страницах консоли в iframe"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86
+msgid "Better detection of 64-bit Windows to prevent crashes by systray"
+msgstr ""
+"Улучшенное определение 64-битных Windows для предотвращения падений в "
+"systray"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87
+msgid "Fix bug preventing router update via torrent"
+msgstr "Исправить проблему, приводящую к невозможности обновиться через torrent"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88
+msgid "Several SSU fixes for NATs that change UDP ports"
+msgstr "Несколько проблем в SSU для NAT, которые меняют UDP порты"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89
+msgid ""
+"Ignore unsupported IPs in RouterInfos when selecting an address (prep for"
+" IPv6)"
+msgstr ""
+"Игнорировать не поддерживаемые IP в RouterInfo при выборе адреса "
+"(подготовка к IPv6)"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90
+msgid ""
+"Ignore unused option bits in Database Lookup Message (prep for requesting"
+" encrypted response)"
+msgstr ""
+"Игнорировать неиспользуемые биты настроек в Database Lookup Message "
+"(подготовка к запросу зашифрованных ответов)"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91
+msgid "Fix HTTP proxy error response for malformed URIs"
+msgstr "Исправить ответы HTTP прокси при ошибках неправильных URI"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92
+msgid "Recognize UPnP devices without port forwarding capability"
+msgstr "Опознавать устройства UPnP без поддержки порт-форвардинга"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96
+msgid "Jetty 7.6.10 (see above for migration information)"
+msgstr "Jetty 7.6.10 (см. выше инструкции по обновлению)"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97
+msgid "Limit page size in i2psnark"
+msgstr "Ограничение на размер страницы в i2psnark"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98
+msgid "Add data directory and page size configuration to i2psnark"
+msgstr "Добавить настройки директории с данными и размера страницы в i2psnark"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99
+msgid "Support multiple i2psnark instances"
+msgstr "Поддержка нескольких экземпляров i2psnark"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100
+msgid "Piece size adjustments in i2psnark"
+msgstr "Настройки размера части в I2psnark"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101
+msgid "Add more graphing support for combined bandwidth graph"
+msgstr ""
+"Дополнить графическую поддержку для отображения комбинированной полосы "
+"пропускания"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102
+msgid "Block b32.i2p supercookies"
+msgstr "Заблокировать b32.i2p supercookies"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103
+msgid "Allow stopping clients on /configclients"
+msgstr "Разрешить останавливать клиентов на /configclients"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104
+msgid "Check for nonce count replays in HTTP client"
+msgstr "Проверка на одноразовые ответы в клиенте HTTP"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105
+msgid "Support SASL authentication in IRC proxy"
+msgstr "Поддержка SASL авторизации в IRC прокси"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106
+msgid "Several cleanups and minor fixes in the update manager"
+msgstr "Несколько исправлений и мелких правок в управлении обновлением"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107
+msgid "Translation updates: German, Portuguese, Russian, Spanish, and Swedish"
+msgstr "Обновлены переводы: немецкий, португальский, русский, испанский, шведский"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:2
+msgid "0.9.7 Release"
+msgstr "Версия 0.9.7"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:7
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:9
+msgid "0.9.7 includes significant bug fixes and improvements."
+msgstr "Версия включает значимые исправления  и улучшения"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:11
+msgid ""
+"For the first time, class 'N' routers (those with a minimumum of 128 "
+"KBytes/sec of shared bandwidth)\n"
+"will automatically become floodfill (previously it was only 'O' routers "
+"with 256 KBps). This will\n"
+"increase the floodfill population for additional resistance to certain "
+"attacks (see below). Floodfill routers\n"
+"don't consume much additional bandwidth, but they do tend to use "
+"additional memory and concurrent\n"
+"connections. If you do not wish your router to become floodfill, set the "
+"advanced configuration\n"
+"router.floodfillParticipant=false ."
+msgstr ""
+"Впервые, маршрутизаторы класса 'N' ( с минимальной полосой 128 "
+"Kbytes/sec) \n"
+"автоматически становятся floodfill (ранее так себя вели только 'O' "
+"маршрутизаторы с полосой 256 KBps). Это позволит\n"
+"увеличить количество floodfill для дополнительной защиты от некоторых "
+"атак (см. ниже). Floodfill \n"
+"не потребляет слишком много ресурсов сети, но есть тенденция к большему "
+"расходу памяти и\n"
+"соединений. Если вы не хотите чтобы ваш маршрутизатор становился "
+"floodfill, поставьте дополнительно настройку "
+"router.floodfillParticipant=false."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:20
+#, python-format
+msgid ""
+"As we think the last release fixed the experimental update-via-torrent "
+"bugs, 3% of routers should\n"
+"update over in-network bittorrent this cycle."
+msgstr ""
+"Как мы и думали, последний релиз устранил проблемы экспериментального "
+"обновления-через-торрент, 3% o маршрутизаторов должны \n"
+"обновиться через внутресетевой бит-торрент  в этом цикле."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:25
+msgid ""
+"Plugin update checks, possibly broken for several releases, are fixed. "
+"Your plugins should once again\n"
+"auto-update after updating the router."
+msgstr ""
+"Проверки обновления плагинов, возможно испорченные в нескольких релизах, "
+"исправлены. Ваши плагины должны еще раз \n"
+"обновиться автоматически после обновления маршрутизатора."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:30
+msgid ""
+"We fixed a major streaming timer bug that contributed to frequent IRC "
+"disconnects."
+msgstr ""
+"Мы исправили главную ошибку потокового таймера, которая приводила к "
+"частым отключениям IRC."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:34
+msgid ""
+"This release contains additional mitigations for the `\"practical "
+"attacks\" paper`_.\n"
+"However, we have a lot more work to do to resist Sybil attacks on the "
+"floodfills, and resist\n"
+"traffic analysis at the gateways and endpoints of exploratory tunnels.\n"
+"It's a good reminder for everybody that our network is still relatively "
+"small and vulnerable.\n"
+"We don't currently recommend any uses that would put anybody in serious "
+"jeopardy.\n"
+"We'll keep working to improve it... please keep working to spread the "
+"word. A bigger network is a better network."
+msgstr ""
+"Этот релиз содержит дополнительные ослабления по `заметкам о \"практике "
+"атак\"`_.\n"
+"Тем не менее, у нам предстоит выполнить еще много работы для защиты от "
+"атак Sybil с floodfill, и защиты от \n"
+"анализа трафика на шлюзах и конечных точках туннелей разведчиков.\n"
+"Это служит хорошим напоминанием всем о том, что наша сеть все еще "
+"относительно мала и уязвима.\n"
+"Мы не рекомендуем любое ее использование, которое может поставить вас под"
+" серьезную угрозу.\n"
+"Мы работаем над ее улучшением... пожалуйста, продолжайте работу, чтобы "
+"распространиться по миру. Чем больше сеть - тем лучше."
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:43
+msgid "`\"practical attacks\" paper`"
+msgstr "`заметки о \"практике атак\"`"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:47
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:15
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:107
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:28
+msgid "Anonymity Improvements"
+msgstr "Улучшения Анонимности"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:49
+msgid "End-to-end encryption of responses to leaseset lookups"
+msgstr "Непрерывное шифрование ответов на запросы просмотров leaseset"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:50
+msgid "Expand floodfill pool by enabling class 'N' floodfills"
+msgstr "Расширение пула floodfill путем включения класса 'N' floodfill"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:51
+msgid "Randomize padding inside encrypted SSU packets"
+msgstr "Случайное изменение размера внутри зашифрованных пакетов SSU"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:52
+msgid "Preparation for better SSU protocol obfuscation"
+msgstr "Подготовка к улучшению обфускации протокола SSU"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:56
+msgid "Fix newer lease sets not getting stored or published"
+msgstr ""
+"Исправление по проблеме: более новые наборы сроков аренды не сохраняются "
+"и не публикуются"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:57
+msgid ""
+"Fix classpath bug when used with 4-year-old installations, causing the "
+"console not to start"
+msgstr ""
+"Исправление ошибки classpath, используемого с 4-летними установками, "
+"вызывающей отказ запуска консоли"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:58
+msgid "Fix addressbook database bug preventing update of the reverse index"
+msgstr ""
+"Исправление ошибки адресной книги базы данных, предотвращающей обновление"
+" обратного индекса"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:59
+msgid ""
+"Fix i2psnark bug that changed the infohash of torrents created by Robert "
+"and fetched via magnet link"
+msgstr ""
+"Исправление ошибки i2psnark, которая изменяет infohash торретнот, "
+"созданных Robert'ом и полученных через магнет ссылку"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60
+msgid "Fix version checking for plugins"
+msgstr "Исправление проверки версий плагинов"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:61
+msgid ""
+"Fix a streaming timer bug causing frequent IRC disconnects (also affects "
+"other close-on-idle tunnels)"
+msgstr ""
+"Исправление ошибки потокового таймера, вызывающей частые отключения IRC "
+"(также влияющую на другие туннели, закрываемые при простое)"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:65
+msgid "Don't install as a service on Windows by default"
+msgstr "Не устанавливать в качестве сервиса Windows по умолчанию"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:66
+msgid "Reduce transport idle timeouts"
+msgstr "Уменьшение таймаутов простоя транспорта"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:67
+msgid "Reduce tunnels on idle in i2psnark"
+msgstr "Уменьшение каналов в простое в i2psnark"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:68
+msgid "Change default in i2ptunnel GUI to 3 hops"
+msgstr "Изменение настройки по умолчанию в i2ptunnel GUI на 3 прыжка"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:69
+msgid "IE 10 support"
+msgstr "Поддержка IE 10"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70
+msgid ""
+"Individual expiration times in leases, for efficiency on destinations "
+"with a high number of tunnels"
+msgstr ""
+"Индивидуальное время жизни аренд, для повышения эффективности в пунктах "
+"назначения с большим количеством туннелей"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71
+msgid "Low-level encryption and XOR speedups"
+msgstr "Низкоуровневое шифрование и ускорение XOR"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:72
+msgid "Jetty 7.6.11"
+msgstr "Jetty 7.6.11"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:73
+msgid "Tomcat 6.0.37"
+msgstr "Tomcat 6.0.37"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74
+msgid "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish"
+msgstr ""
+"Обновления переводов: Китайский, Французский, Немецкий, Португальский, "
+"Русский, Испанский"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75
+msgid "New Turkish translation"
+msgstr "Новый Турецкий перевод"
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:76
+msgid "Wrapper 3.5.19 (new installs and PPA only)"
+msgstr "Wrapper 3.5.19 (только новые установки и PPA)"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:2
+msgid "0.9.7.1 Release"
+msgstr "0.9.7.1 релиз"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:7
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:9
+msgid ""
+"This unscheduled release disables the RouterInfo verification messages "
+"that were used in the attack published in the UCSB paper, which should "
+"make correlating a LeaseSet and a Router much more difficult. We have "
+"also included a limited number of other fixes listed below. Our 0.9.8 "
+"release, which will include IPv6 support, is still on-schedule for late "
+"September."
+msgstr ""
+"Этот незапланированный релиз отключает проверочные сообщения RouterInfo, "
+"которые использовались в атаках, опубликованных в заметках UCSB, что "
+"должно усложнить нахождение связи между LeaseSet и маршрутизатором. Мы "
+"также включили ограниченное число исправлений, приведенных ниже. Наш "
+"релиз 0.9.8, который будет включать в себя поддержку IPv6, все еще "
+"запланирован на конец сентября."
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:11
+msgid "As usual, we recommend that all users update to this release."
+msgstr "Как обычно, мы рекомендуем всем обновиться до этого релиза."
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:17
+msgid "Disable RouterInfo verification messages"
+msgstr "Отключение проверочных сообщений RouterInfo"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:21
+msgid "Extend inbound tunnel expiration"
+msgstr "Увеличили время жизни входящего туннеля"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:22
+msgid "i2prouter: bashism fix"
+msgstr "i2prouter: исправление bashism"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:23
+msgid "i2psnark: increase max piece size, mime type updates"
+msgstr "i2psnark: увеличили максимальный размер куска, обновление mime типов"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:24
+msgid "New reseed host"
+msgstr "Новый механизм повторного использования хоста"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:25
+msgid "New update hosts, thanks Meeh and dg"
+msgstr "Новый механизм обновления хоста, спасибо Meeh и dg"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:26
+msgid "Streaming: RTO changes"
+msgstr "Потоки: изменения RTO"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:27
+msgid "Updater: Increase update-via-torrent to 30 percent"
+msgstr "Обновление: увеличение обновлений-через-торрент до 30 процентов"
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:28
+msgid "UPnP fix for some hardware"
+msgstr "Исправление UPnP для некоторого оборудования"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:2
+msgid "0.9.8 Release"
+msgstr "Релиз 0.9.8"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9
+msgid ""
+"0.9.8 includes the long-awaited support for IPv6. It's enabled by "
+"default, but of course you need a public IPv6 address to use it. "
+"Configuration is on the 'network' configuration tab in your console. We "
+"also have anonymity improvements including padding of SSU packets and "
+"longer router private keys."
+msgstr ""
+"0.9.8 включает долгожданную поддержку IPv6. Она включена по умолчанию, "
+"но, конечно же, вам нужен публичный IPv6 адрес, чтобы использовать её. "
+"Настраивается во вкладке настроек \"сеть\" в вашей консоли. Мы также "
+"усилили анонимность, включая многослойные SSU пакеты и более длинные "
+"закрытые ключи роутера. "
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11
+#, python-format
+msgid "30% of you will update via in-network torrent in this update cycle."
+msgstr ""
+"В этом цикле обновлений 30% o из вас будут обновлены через внутрисетевой "
+"торрент-клиент."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13
+msgid "IPv6 Details"
+msgstr "Подробности об IPv6."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15
+msgid ""
+"IPv6 is enabled and preferred by default. If you have a public IPv6 "
+"address \n"
+"and you are connecting to another router with a published IPv6 address, "
+"it will \n"
+"connect via IPv6. There is a new IPv6 configuration section on /confignet"
+" in \n"
+"the router console. If IPv6 is causing problems you may disable it there."
+msgstr ""
+"IPv6 включён и предпочитается по умлочанию. Если у вас есть публичный "
+"IPv6 адрес\n"
+"и вы соединяетесь с другим роутером с публичным IPv6 адресом, они\n"
+"соединятся через IPv6. В /confignet в консоли роутера - новая секция\n"
+" настройки IPv6. Если IPv6 вызывает проблемы, вы можете отключить его там."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22
+msgid ""
+"As a part of the IPv6 development effort, I2P now supports multiple \n"
+"published IP addresses. If you have multiple public IP addresses (IPv4, "
+"IPv6, \n"
+"or both), you may enable or disable them individually on /confignet. The"
+" \n"
+"default is to use the first IPv4 and IPv6 addresses it discovers. If you "
+"have \n"
+"multiple addresses you should review the configuration on /confignet and "
+"adjust \n"
+"it if necessary.\n"
+"Note that while you may enable multiple IPv4 and IPv6 addresses on "
+"/confignet,\n"
+"we recommend that you use only one IPv4 and one IPv6 address. There are\n"
+"bugs still to be fixed with multiple addresses of each type."
+msgstr ""
+"Как часть усилий в области развития IPv6, I2P теперь поддерживает "
+"множественные\n"
+"публичные IP адреса. Если у вас есть множественные публичные IP адреса "
+"(IPv4, IPv6,\n"
+"или оба), вы можете включить или выключить каждый из них в /confignet. По"
+"\n"
+"умолчанию, используется сначала IPv4, а IPv6 адреса к нему обращаются. "
+"Если у вас есть\n"
+"множественные адреса, вам стоит проверить настройки в /confignet и "
+"поправить\n"
+"их, если необходимо.\n"
+"Заметьте, что в то время как вы можете включить множественные IPv4 и IPv6"
+" адреса в /confignet,\n"
+"мы рекомендуем использовать только один IPv4 и один IPv6 адреса. Всё ещё\n"
+"есть ошибки с множественными адресами каждого типа, которые нужно "
+"исправить."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34
+msgid ""
+"While IPv6 support was designed and developed over several years, it has"
+" \n"
+"only been tested by a limited number of users and is still beta. If you "
+"do have \n"
+"a public IPv6 address, please monitor your router and the logs for "
+"problems, \n"
+"and disable it necessary. Please report any bugs on \n"
+"http://trac.i2p2.i2p."
+msgstr ""
+"В то время как поддержка IPv6 проектировалась и разрабатывалась в течение"
+" нескольких лет, она\n"
+"была протестирована только ограниченным количеством пользователей и всё "
+"ещё на стадии беты.\n"
+"Если у вас есть публичный IPv6 адрес, пожалуйста, проверяйте ваш "
+"маршрутизатор и логи на предмет проблем,\n"
+"и отключите его, если необходимо. Пожалуйста, сообщайте о любых ошибках "
+"на\n"
+"http://trac.i2p2.i2p"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:42
+msgid "Rekeying Details"
+msgstr "Подробности о Подробном вводе. "
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44
+msgid ""
+"For those of you running I2P on faster hardware (generally, 64-bit x86) "
+"the \n"
+"router will generate a new identity using longer keys. This will "
+"substantially \n"
+"reduce your participating traffic for 48 hours or more, while your router"
+" \n"
+"re-integrates into the network. Due to the new keys, the large number of"
+" \n"
+"torrent updates, and the recent network growth, we expect substantial \n"
+"disruption to the network for a week or more after the update is "
+"released. \n"
+"Please be patient and things should start to improve after a few days."
+msgstr ""
+"Для тех из вас, кто запускает I2P на быстром аппаратном обеспечении\n"
+" (в основном, 64-битном x86), маршрутизатор сгенерирует новый профиль\n"
+"используя более длинные ключи. Это в значительной степени сократит\n"
+"ваш транзитный трафик на 48 часов или более, пока ваш маршрутизатор\n"
+"ре-интегрируется в сеть. По причине новых ключей, большого количества\n"
+"торрент-обновлений и недавнего роста сети мы ожидаем существенных\n"
+"сбоев в сети в течение недели или более после выпуска обновления.\n"
+"Пожалуйста, будьте терпеливы: всё должно начать улучшаться через\n"
+"несколько дней."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54
+msgid ""
+"These changes may result in higher CPU usage for some of you. We're doing"
+" \n"
+"our best to increase efficiency, but stronger security generally requires"
+" more \n"
+"computation. Performance may also be poor during the first week\n"
+"due to the network churn.\n"
+"We will evaluate the network performace before deciding whether to\n"
+"change the key length on slower hardware in a future release."
+msgstr ""
+"Эти изменения для некоторых из вас могут привести к более высокой\n"
+"нагрузке на процессор. Мы делаем всё возможное, чтобы повысить "
+"эффективность,\n"
+"но более высокий уровень безопасности обычно требует больше расчётов.\n"
+"Быстродействие также может быть низким в течение первой недели\n"
+"из-за оттока сети.\n"
+"Мы оценим производительность сети, прежде чем принимать решение об\n"
+"изменении длины ключа на более медленном оборудовании в\n"
+"будущих релизах."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63
+msgid ""
+"We are experiencing rapid network growth in the last few weeks, which is"
+" \n"
+"causing a bit of a bumpy ride for some, especially on weekends. However, "
+"the \n"
+"network is still performing fairly well, so keep spreading the word."
+msgstr ""
+"Мы переживаем быстрый рост сети в посдление несколько недель,\n"
+"который вызывает у некоторых проблемы, особенно по выходным.\n"
+"Однако, сеть всё ещё работает достаточно хорошо, так что продолжайте\n"
+"распространять информацию."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69
+msgid "More Changes Coming"
+msgstr "Впереди Больше Изменений."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:71
+msgid ""
+"We're in the initial stages of desiging major changes to strengthen our \n"
+"crypto. Stronger crypto will use more CPU and it may possibly \n"
+"require a Java 7 JRE at a minimum. We understand your desire to run I2P "
+"on low-power \n"
+"and/or older hardware. We're working hard to minimize the impacts, but "
+"some \n"
+"loss of performance is inevitable. In addition, Java 5 and 6 are no "
+"longer \n"
+"supported by Oracle. Now is a good time to upgrade to Java 7. Any change "
+"in \n"
+"minimum requirements will be announced well in advance."
+msgstr ""
+"Мы находимся на начальной стадии проектирования основных изменений\n"
+"для усиления нашего шифрования. Более сильное шифрование будет "
+"использовать\n"
+"больше ресурсов процессора и возможно потребует Java 7 JRE как минимум. "
+"Мы\n"
+"понимаем, что вы хотите запускать I2P на маломощном и/или старом "
+"оборудовании.\n"
+"Мы прилагаем все усилия, что уменьшить неудобства, но некоторая потеря\n"
+"быстродействия неизбежна. Кроме того, Java 5 и 6 более не поддерживаются\n"
+"Oracle. Сейчас самое время перейти на Java 7. Любые изменения в "
+"минимальных\n"
+"требованиях будут анонсированы заранее."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:81
+msgid "New Website"
+msgstr "Новый Вебсайт"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:83
+msgid ""
+"After a heroic effort by str4d, the new website preview is available at \n"
+"http://i2hq.srv.i2p2.de. We hope to see it go live at \n"
+"https://geti2p.net and http://www.i2p2.i2p soon.  Please \n"
+"contribute to the new website translations on Transifex, especially the \n"
+"website_priority resource."
+msgstr ""
+"После героических усилий str4d предварительный просмотр\n"
+"нового сайта доступен на http://i2hq.srv.i2p2.de. Мы надеемся скоро \n"
+"увидеть его вживую на https://geti2p.net и http://www.i2p2.i2p.\n"
+"Пожалуйста, сделайте свой вклад в новый перевод вебсайта на \n"
+"Transifex, особенно в разделе website_priority."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91
+msgid "Community Participation"
+msgstr "Участие в Сообществе"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:93
+msgid ""
+"In early August, hottuna and zzz attended DEFCON 21 in Las Vegas.\n"
+"Last weekend, echelon attended the CTS IV conference in Berlin and\n"
+"psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass.\n"
+"Several of us will be at 30C3 in Hamburg late this year.\n"
+"It's great to see people participating at these events and representing "
+"I2P."
+msgstr ""
+"В начале августа hottuna и zzz принимали участие в DEFCON 21 в Лас "
+"Вегасе.\n"
+"В минувшие выходные echelon поучаствовал в конференции CTS IV в Берлине,\n"
+"а psi - в хакфесте Tahoe-LAFS на GNU 30 в Кембридже, штат Массачусетс.\n"
+"Некоторые из нас будут на 30C3 в Гамбурге в этом году.\n"
+"Это классно - видеть людей, участвующих в этих мероприятиях и \n"
+"представляющих I2P."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105
+msgid "IPv6 support for both NTCP and SSU"
+msgstr "Поддержка IPv6 для обоих NTCP и SSU"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:109
+msgid "SSU protocol obfuscation by adding random padding"
+msgstr "Затемнение протокола SSU добавлением случайного наполнения"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110
+msgid "Longer encryption and DH private keys for users on faster platforms"
+msgstr ""
+"Более длинные ключи шифрования и закрытые ключи DH для пользователей на "
+"более быстрых платформах."
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114
+msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)"
+msgstr "Исправлены блокировка и дублирование (частично) I2PTunnel / I2C"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:115
+msgid "Fix translation of HTTP proxy error pages"
+msgstr "Исправлен перевод страниц ошибок HTTP прокси"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:116
+msgid "Fix occasional runtime exception in NTCP"
+msgstr "Исправлено случающееся иногда исключение времени выполнения в NTCP"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120
+msgid "Big rework of transport code to accommodate multiple addresses and IPv6"
+msgstr ""
+"Большая переработка транспортного кода для согласования множественных "
+"адресов и IPv6"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121
+msgid "Streaming: Improved recovery from lost acks, other fixes"
+msgstr ""
+"Streaming: улучшено восстановление после потерянных подтверждений, другие"
+" исправления"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122
+msgid "Use Transifex for translation of initial news and HTTP proxy error pages"
+msgstr ""
+"Использование Transifex для перевода начальных новостей и страниц ошибок "
+"HTTP прокси"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123
+msgid ""
+"Translation updates: Chinese, French, German, Portuguese, Russian, "
+"Swedish, Turkish"
+msgstr ""
+"Обновления перевода: китайский, французский, немецкий, португальский, "
+"русский, шведский, турецкий"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124
+msgid "New Romanian translation"
+msgstr "Новый румынский перево"
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:126
+msgid "Wrapper 3.5.20 (new installs and PPA only)"
+msgstr "Wrapper 3.5.20 (только новые установки и PPA)"
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:2
+msgid "0.9.8.1 Release"
+msgstr "Релиз 0.9.8.1"
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:7
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:9
+msgid ""
+"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some "
+"people. New installs and non-Windows platforms are not affected, however "
+"all platforms will automatically update even if running 0.9.8."
+msgstr ""
+"0.9.8.1 исправляет проблему с обновлением до 0.9.8 на Windows у некоторых"
+" людей. Новые установки и не-Windows платформы не затронуты, тем не "
+"менее, все платформы автоматически обновятся, даже если они уже "
+"используют 0.9.8."
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:11
+msgid ""
+"See the `Trac ticket`_ for details and workarounds. See\n"
+"`the 0.9.8 release notes`_ for information on IPv6 and other changes."
+msgstr ""
+"Подробности и обходные пути смотри в `Trac ticket`_. Смотри\n"
+"`заметки по релизу 0.9.8`_ для информации по IPv6 и другим изменениям."
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:16
+msgid ""
+"Due to recent attacks, logins are disabled on `Trac`_ and new "
+"registrations are\n"
+"disabled on `zzz.i2p`_. Until those services are restored, please report "
+"all\n"
+"bugs on IRC freenode or IRC2P #i2p-dev."
+msgstr ""
+"В свете последних атак, учетные записи на `Trac`_ заблокированы, и новые "
+"регистрации на \n"
+"`zzz.i2p`_ заблокированы. Пока сервисы не доступны, пожалуйста, "
+"отправляйте все \n"
+"ошибки на IRC freenode или IRC2P #i2p-dev."
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:22
+msgid "`Trac ticket`"
+msgstr "`Trac ticket`"
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:23
+msgid "`the 0.9.8 release notes`"
+msgstr "`заметки по релизу 0.9.8`"
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:2
+msgid "0.9.9 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:7
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:9
+msgid ""
+"0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and "
+"starts work on a year-long plan to increase the strength of the "
+"cryptographic signing algorithms used in the router, and support multiple"
+" algorithms and key lengths simultaneously. Automatic update files will "
+"now be signed with 4096-bit RSA keys."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:11
+msgid ""
+"We now support SSL between your router and your servers for security.\n"
+"See `this development thread`_ for more information."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:16
+msgid "`this development thread`"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:18
+msgid ""
+"As usual, we recommend that you update to this release.\n"
+"The best way to maintain security and help the network is to run the "
+"latest release.\n"
+"Several members of the I2P team will be at 30C3 in Hamburg this year.\n"
+"Come say hello and ask for an I2P sticker.\n"
+"Thanks to everyone for their support this year."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:30
+msgid "Don't build client tunnels through zero-hop exploratory tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:31
+msgid "New \"su3\" file support using stronger keys"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:32
+msgid "Use su3 for updates"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:36
+msgid "Issues with losing data when closing streams"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:37
+msgid "Fix various streaming connection limit issues"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:38
+msgid "Issues with resource usage of closed connections"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:39
+msgid "Clean up timer threads in close-on-idle tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:40
+msgid "Several other streaming fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:41
+msgid "Reject more non-public IPv6 addresses"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:42
+msgid "Fix IPv6 GeoIP"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:43
+msgid "Fix peer selection in first minutes after startup"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:44
+msgid "Several I2PTunnel bug fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:45
+msgid "Fix major i2psnark DHT bug that prevented magnets from working well"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:46
+msgid ""
+"Fix client tunnels that fail due to name resolution failure at startup, "
+"particularly with b32 hostnames"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:47
+msgid "Fix changing client i2ptunnel target list"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:48
+msgid ""
+"Fix major bugs preventing reception of encrypted responses to leaseset "
+"lookups and verifies"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:49
+msgid "Fix bad links on some i2psnark buttons in Opera and text-mode browsers"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:50
+msgid "Fix NPE in Susimail"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:54
+msgid "Start work on supporting stronger signing keys in the router"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:55
+msgid "Reduce thread usage for HTTP Server tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:56
+msgid "Auto-stop update torrent after some time"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:57
+msgid "Add ability to stop webapp via console"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:58
+msgid "New POST throttler in HTTP server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:59
+msgid "Improve connection throttling"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:60
+msgid "More work to reduce number of connections"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:61
+msgid "Re-enable router info expiration job"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:62
+msgid ""
+"Extend router info expiration and other changes to reduce load on "
+"floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:63
+msgid "Support multiple servers through a single server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:64
+msgid "Support specification of server port in i2ptunnel clients"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:65
+msgid "Add support for SSL connections from i2ptunnel to external server"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:66
+msgid "SSL and crypto code refactoring"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:67
+msgid "i2psnark storage code refactoring"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:68
+msgid "New destination cache"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:69
+msgid "Lots of code cleanup and resolution of findbugs warnings"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:70
+msgid "New Japanese translation (partial)"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:71
+msgid ""
+"Translation updates: French, German, Italian, Romanian, Russian, Spanish,"
+" Swedish, and others"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:73
+msgid "Wrapper 3.5.22 (new installs and PPA only)"
+msgstr ""
+
diff --git a/i2p2www/translations/ru/LC_MESSAGES/comparison.po b/i2p2www/translations/ru/LC_MESSAGES/comparison.po
new file mode 100644
index 00000000..4c90a178
--- /dev/null
+++ b/i2p2www/translations/ru/LC_MESSAGES/comparison.po
@@ -0,0 +1,861 @@
+# Russian (Russia) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# keedley , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-10-26 22:39+0000\n"
+"PO-Revision-Date: 2013-09-21 17:36+0000\n"
+"Last-Translator: keedley \n"
+"Language-Team: Russian (Russia) "
+"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 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/comparison/freenet.html:2
+msgid "I2P Compared to Freenet"
+msgstr "I2P в сравнении с Freenet"
+
+#: i2p2www/pages/site/comparison/freenet.html:8
+msgid ""
+"Freenet is a fully distributed, peer to peer anonymous publishing "
+"network, offering \n"
+"secure ways to store data, as well as some approaches attempting to "
+"address the loads\n"
+"of a flash flood.  While Freenet is designed as a distributed data store,"
+" people have\n"
+"built applications on top of it to do more generic anonymous "
+"communication, such as \n"
+"static websites and message boards."
+msgstr ""
+"Freenetn это полностью распределенная, точка-точка, анонимная сеть для "
+"публикации, предоставляющая безопасный способ хранить данные, как и "
+"некоторые подходы, позволяющие обрабатывать нагрузки\n"
+"в пиках. Хотя Freenet разработан как распределенное хранилище, "
+"пользователи сделали\n"
+"приложения поверх него, которые позволяют другие формы взаимодействия, "
+"такие как статичные\n"
+"веб-сайты и доски сообщений."
+
+#: i2p2www/pages/site/comparison/freenet.html:16
+#, python-format
+msgid ""
+"Compared to I2P, Freenet offers some substantial benefits - it is a "
+"distributed data\n"
+"store, while I2P is not, allowing people to retrieve the content "
+"published by others \n"
+"even when the publisher is no longer online.  In addition, it should be "
+"able to \n"
+"distribute popular data fairly efficiently.  I2P itself does not and will"
+" not provide \n"
+"this functionality.  On the other hand, there is overlap for users who "
+"simply want to \n"
+"communicate with each other anonymously through websites, message boards,"
+" file sharing\n"
+"programs, etc.  There have also been some attempts to develop a "
+"distributed data \n"
+"store to run on top of I2P,\n"
+"(most recently a port of Tahoe-LAFS)\n"
+"but nothing is yet ready for general use."
+msgstr ""
+"По сравнению с I2P, Freenet имеет некоторые преимущества - это "
+"распределенное хранилище\n"
+"данных, чем I2P не является, позволяющее людям обмениваться данными, даже"
+" если оригинальный\n"
+"автор более недоступен. Также сеть позволяет эффективно распределять "
+"даынные. I2P сам по себе не имеет и не будет иметь такой функции. С "
+"другой стороны, здесь есть недостаток для пользователей, которые просто "
+"хотят анонимно общаться через веб-сайты, доски объявлений, программы "
+"файлообмена и т.д\n"
+"В I2P есть варианты реализации таких функций с помошью специальных "
+"приложений (a href=\"%(tahoe)s\">Tahoe-LAFS), но еще ничего для "
+"обычного использования не готово."
+
+#: i2p2www/pages/site/comparison/freenet.html:29
+msgid ""
+"However, even ignoring any implementations issues, there are some "
+"concerns \n"
+"about Freenet's algorithms from both a scalability and anonymity "
+"perspective, owing \n"
+"largely to Freenet's heuristic driven routing.  The interactions of "
+"various techniques \n"
+"certainly may successfully deter various attacks, and perhaps some "
+"aspects of the \n"
+"routing algorithms will provide the hoped for scalability.  "
+"Unfortunately, not much\n"
+"analysis of the algorithms involved has resulted in positive results, but"
+" there is still\n"
+"hope.  At the very least, Freenet does provide substantial anonymity "
+"against an attacker\n"
+"who does not have the resources necessary to analyze it further."
+msgstr ""
+"Тем не менее, даже не обращая внимание на проблемы реализации, есть "
+"определенные соображения\n"
+"об алгоритмах Freenet с точки зрения масштабирования и анонимности, в "
+"области эвристической маршрутизации внутри Freenet. Взаимодействие разных"
+" техник определенно может защитить от ряда аттак, \n"
+"и возможно некоторые аспекты алгоритмов маршрутизации дают надежды на "
+"масштабирование. К сожалению, немного из попыток анализа алгоритмов дали "
+"позитивные результаты, но надежда есть.\n"
+"В конце концов, Freenet предоставляет значительный уровень анонимности "
+"против атакующего, который не обладает достаточными для дальнейшего "
+"анализа ресурсами."
+
+#: i2p2www/pages/site/comparison/index.html:2
+msgid "Comparing I2P to other projects"
+msgstr "Сравнение I2P с другими проектами"
+
+#: i2p2www/pages/site/comparison/index.html:4
+msgid ""
+"There are a great many other applications and projects working on "
+"anonymous \n"
+"communication and I2P has been inspired by much of their efforts.  This "
+"is not \n"
+"a comprehensive list of anonymity resources - both freehaven's \n"
+"Anonymity "
+"Bibliography\n"
+"and GNUnet's related "
+"projects\n"
+"serve that purpose well.  That said, a few systems stand out for further\n"
+"comparison. The following have individual comparison pages:"
+msgstr ""
+"Существует много других хороших приложений и проектов в области анонимных"
+" коммуникаций, и I2P определенно обогащается их опытом.  Это не \n"
+"полный список подобных ресурсов - у freehaven'а  в  \n"
+"Anonymity "
+"Bibliography\n"
+"и в  GNUnet проектах\n"
+"эти списки полнее.  Всего несколько систем имеет смысл сравнивать далее."
+" \n"
+"Ниже перечислены страницы, посвященные сравнениям с этими системами:"
+
+#: i2p2www/pages/site/comparison/index.html:20
+#, python-format
+msgid ""
+"The following are discussed on the other "
+"networks page:"
+msgstr "Обсуждается на странице других сетей:"
+
+#: i2p2www/pages/site/comparison/index.html:32
+#, fuzzy, python-format
+msgid ""
+"The content of this page is subject to update, discussion and dispute, "
+"and we welcome comments and additions.\n"
+"You may contribute an analysis by entering a new "
+"ticket on Trac."
+msgstr ""
+"Содержимое этой страницы может обновляться, обсуждаться и "
+"ниспровершаться, и мы приветствуем комментарии и добавления. \n"
+"Вы можете внести свой вклад, опубликовав  в Trac новую запись"
+
+#: i2p2www/pages/site/comparison/other-networks.html:2
+msgid "I2P Compared to Other Anonymous Networks"
+msgstr "I2P  в сравнении с другими анонимными сетями"
+
+#: i2p2www/pages/site/comparison/other-networks.html:5
+msgid "The following networks are discussed on this page."
+msgstr "Следующие сети обсуждаются на этой странице:"
+
+#: i2p2www/pages/site/comparison/other-networks.html:16
+#, fuzzy, python-format
+msgid ""
+"Most of the following sections are fairly old, and may not be accurate.\n"
+"For an overview of available comparisons, see the\n"
+"main network comparisons page.\n"
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+"Многие из секций довольно старые и могут быть неточными.\n"
+"Для списка известных сравнений, смотрите страницу сравнений сетей.⏎\n"
+"Вы можете опубликовать свой анализ через ⏎\n"
+"тикет-систему %(trac)s."
+
+#: i2p2www/pages/site/comparison/other-networks.html:29
+#, python-format
+msgid ""
+"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
+" \n"
+"anonymizing proxies, allowing people to tunnel out through the low "
+"latency \n"
+"mix network.  Morphmix includes some very interesting collusion detection"
+" \n"
+"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
+"IP\n"
+"addresses to accomplish the same.  The two primary differences between \n"
+"these systems and I2P are related to I2P's threat model \n"
+"and their out-proxy design (as opposed to providing both sender and "
+"receiver \n"
+"anonymity).  There is source code available to both systems, but we are "
+"not aware \n"
+"of their use outside of academic environments."
+msgstr ""
+"Morphmix и Tarzan это полностью распределенные точка-точка сети анонимных"
+" прокси-серверов, позволяющие людям организовывать соединения через "
+"смешанную сеть с низкими задержками.\n"
+"Morphmix  включает интересные алгоритмы обхода коллизий и защиты от атаки"
+" Sybil, а Tarzan  использует для этого недостаток IP адресов. Два "
+"основных отличия таких систем от I2P связаны с моделью угроз I2P \n"
+"и их дизайнов выходящих узлов (в отличии от обеспечения анонимности и "
+"отправителя, и получателя). Для обоих систем доступны исходные коды, но "
+"нам не известно об их использовании за пределами научной деятельности."
+
+#: i2p2www/pages/site/comparison/other-networks.html:153
+#, fuzzy, python-format
+msgid ""
+"\n"
+"Mixminion and Mixmaster are networks to support anonymous email against a"
+" very\n"
+"powerful adversary.\n"
+"High-latency messaging applications running on top of I2P\n"
+"(for example Syndie or I2PBote)\n"
+"may perhaps prove adequate to meet the threat\n"
+"model of those adversaries, while running in parallel along side the "
+"needs of low latency users, to provide\n"
+"a significantly larger anonymity set.\n"
+"High-latency support within the I2P router itself may or may not be added"
+" in a distant future release.\n"
+"It is too early to say if I2P will meet the needs of users requiring "
+"extreme protection for email."
+msgstr ""
+"\n"
+"Mixminion и Mixmaster это сети, обеспечивающие обмен email при "
+"противодействии мощному противнику.\n"
+"Средства обмена сообщениями с высокой задержкой поверх I2P\n"
+"(например, Syndie или\n"
+"I2PBote)\n"
+"возможно окажутся вполне отвечающими модели угроз в таких условиях, "
+"особенно эксплуатируясь на фоне трафика многочисленных пользователей с "
+"низкими задержками, что добавит дополнительный уровень анонимности.\n"
+"Поддержка работы с высокими задержками в I2P-маршрутизаторе может, а "
+"может и не быть добавлена в отдаленном будущем релизе.\n"
+"Пока рано говорить, сможет ли I2P удовлетворить требования пользователей "
+"по экстремальной защите email сообщений."
+
+#: i2p2www/pages/site/comparison/other-networks.html:165
+msgid ""
+"As with Tor and Onion Routing, \n"
+"both Mixminion and Mixmaster take the directory based approach as well."
+msgstr ""
+"Как и в случае Tor и Onion Routing,  Mixminion и Mixmaster применяют "
+"подход на основе справочных директорий."
+
+#: i2p2www/pages/site/comparison/other-networks.html:175
+#, python-format
+msgid ""
+"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
+"web requests,\n"
+"and as such it has a few centralized nodes (participants in the cascade) "
+"that blend\n"
+"and mix requests from clients through the sequence of nodes (the cascade)"
+" before \n"
+"proxying out onto the web.  The scope, threat model, and security is "
+"substantially \n"
+"different from I2P, but for those who don't require significant anonymity"
+" but still\n"
+"are not satisfied with an Anonymizer-like service, JAP is worth "
+"reviewing.  One\n"
+"caution to note is that anyone under the jurisdiction of the German "
+"courts may want\n"
+"to take care, as the German Federal Bureau of Criminal Investigation "
+"(FBCI) has \n"
+"successfully mounted an \n"
+"attack \n"
+"on the network.  Even though the method of this attack was later found to"
+" be illegal \n"
+"in the German courts, the fact that the data was successfully collected "
+"is the \n"
+"concern.  Courts change their minds based upon circumstance, and this is "
+"evidence that \n"
+"if a government body or intelligence agency wanted to, they could gather "
+"the data, even \n"
+"if it may be found inadmissible in some courts later)"
+msgstr ""
+"JAP (Java Anonymous Proxy) это сеть смешанных каскадов для анонимизации "
+"веб-запросов, и для этого применяется несколько централизованных узлов "
+"(участников каскада), которые смешивают и обрабатывают запросы "
+"пользователей через набор узлов (каскад) перед доставкой их в сеть.\n"
+"Задача, модель угроз и безопасности существенно отличаются от принятых в "
+"I2P, но те, кто не нуждается в значительном уровне анонимности, но не "
+"удовлетворен уровнем анонимности существующих анонимайзеров, могут "
+"рассмотреть этот вариант.  Те, кто в зоне ответственности немецкого "
+"законодательства, должны учитывать опасность того, что German Federal "
+"Bureau of Criminal Investigation (FBCI) успешно провело атаку на эту сеть.\n"
+"Хотя методы атаки позже были признаны незаконными в немецком суде, факт "
+"успешного сбора данных стоит учитывать. Суды могут поменять свои решения "
+"по обстоятельствам и техническую возможность сбора информации "
+"правительством или агентствами нельзя сбрасывать со счетов)."
+
+#: i2p2www/pages/site/comparison/other-networks.html:197
+#, python-format
+msgid ""
+"Both of these systems work through the same basic \n"
+"antnet routing, providing some degree of\n"
+"anonymity based on the threat model of providing plausible deniability "
+"against a simple \n"
+"non-colluding adversary.  With the antnet routing, they first either do a"
+" random walk or a \n"
+"broadcast search to find some peer with the data or identity desired, and"
+" then use a feedback\n"
+"algorithm to optimize that found path.  This works well for applications "
+"that merely want to know \n"
+"what other people around them have to offer - \"How are y'all doing\" vs."
+" \"Hey Alice, how are you\" - \n"
+"you basically get a local cluster of nodes that can share files with and "
+"maintain some degree of \n"
+"anonymity (though you don't have much control over who is in that group "
+"of peers)."
+msgstr ""
+"Обе эти системы работают на одном базовом механизме маршрутизации, добиваясь некоторой анонимности, "
+"предоставляя путь отказа при несложном, не организованном противнике. "
+"Используя antnet маршрутизацию, они сначала делают случайный проход, или "
+"широковещательный запрос на поиск пира с нужными данными или адресами, а "
+"затем используют обратную связь для оптимизации найденного пути. Это "
+"нормально работает для приложений, которые собирают информацию о том, что"
+" другие пиры вокруг могут предложить - \"как у вас всех дела?\" против "
+"\"Алиса, привет, ты как?\".  На выходе вы получаете локальный набор "
+"узлов, с которыми можно обмениваться файлами и поддерживать определенный "
+"уровень анонимности (хотя вы не имеете особого контроля над тем, кто "
+"будет в этой группе пиров)."
+
+#: i2p2www/pages/site/comparison/other-networks.html:209
+msgid ""
+"However, the algorithm does not scale well at all - if the application "
+"wants to speak with a \n"
+"particular peer it ends up doing a broadcast search or random walk "
+"(though if they are lucky enough\n"
+"for that to succeed, the antnet routing should optimize that found "
+"connection).  This means that \n"
+"while these networks can work great at small scales, they are not "
+"suitable for large networks where\n"
+"someone wants to get in touch with another specific peer.  That does not "
+"mean that there is no \n"
+"value in these systems, just that their applicability is limited to "
+"situations where their \n"
+"particular issues can be addressed."
+msgstr ""
+"Тем не менее, этот алгоритм не очень хорошо масштабируется - если "
+"приложение хочет говорить с конкретным пиром, оно делает "
+"широковещательный запрос или случайный поик (хотя, если поиск удался, "
+"antnet позволит оптимизировать связб). Это означает, что хотя эти сети "
+"работают на малом числе узлов, для большого числа узлов они не очень "
+"применимы при попытке связаться с конкретным пиром. Это не означает, что "
+"эти системы бесполезны, просто их применимость ограничена сценариями, где"
+" эти недостатки можно обработать другими средствами."
+
+#: i2p2www/pages/site/comparison/other-networks.html:220
+#, python-format
+msgid ""
+"This was a closed-source network targeted at Iranian users.\n"
+"Tor did a good writeup on what to look for in a "
+"circumvention tool.\n"
+"Suffice it to say that being closed source and publicly targeting a "
+"specific country are not good ideas.\n"
+"I2P is, of course, open source. However, that source, and our\n"
+"technical documentation, need much more review."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:229
+msgid "Paid VPN Services"
+msgstr "Платные VPN сервисы"
+
+#: i2p2www/pages/site/comparison/other-networks.html:230
+#: i2p2www/pages/site/comparison/other-networks.html:236
+#, fuzzy, python-format
+msgid ""
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+"Вы можете внести свой вклад, опубликовав новую запись в %(trac)s."
+
+#: i2p2www/pages/site/comparison/other-networks.html:235
+msgid "Others"
+msgstr "Другие"
+
+#: i2p2www/pages/site/comparison/tor.html:2
+msgid "I2P Compared to Tor"
+msgstr "I2P в сравнении с Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:8
+#, python-format
+msgid ""
+"Tor and Onion Routing are both anonymizing proxy networks, \n"
+"allowing people to tunnel out through their low latency mix \n"
+"network. The two primary differences between Tor / \n"
+"Onion-Routing and I2P are again related to differences in \n"
+"the threat model and the out-proxy design (though Tor\n"
+"supports hidden services as well).  In addition, Tor\n"
+"takes the directory-based approach - providing a \n"
+"centralized point to manage the overall 'view' of the \n"
+"network, as well as gather and report statistics, as \n"
+"opposed to I2P's distributed network \n"
+"database and peer selection."
+msgstr ""
+"Tor и Onion Routing это анонимные сети прокси-серверов, позволяющие "
+"пользователям\n"
+"туннелировать данные через их сеть с низкими задержками. Два основных "
+"отличия Tor и I2P \n"
+"основаны на разнице в моделях угроз и дизайне выходных прокси-узлов (хотя"
+" Tor и поддерживает скрытые сервисы, как и I2P). Кроме того, Tor "
+"реализует централизованную точку для управления видимостью сети, а так же"
+" для сбора статистики, в отличие от распределенной модели сети I2P, базы сети и выбора "
+"пира."
+
+#: i2p2www/pages/site/comparison/tor.html:22
+msgid ""
+"The I2P/Tor outproxy functionality does have a few \n"
+"substantial weaknesses against certain attackers - \n"
+"once the communication leaves the mixnet, global passive\n"
+"adversaries can more easily mount traffic analysis.  In \n"
+"addition, the outproxies have access to the cleartext \n"
+"of the data transferred in both directions, and \n"
+"outproxies are prone to abuse, along with all of the \n"
+"other security issues we've come to know and love with \n"
+"normal Internet traffic."
+msgstr ""
+"Функция выходных узлов в  I2P/Tor обладает несколькими явными проблемами "
+"- \n"
+"как только данные покидают сеть, глобальные наблюдатели легко "
+"обеспечивают мониторинг этого траффика.  В добавок, выходные узлы имеют "
+"доступ к незашифрованным данным в обе стороны, а также легко выявляются и"
+" подвержены разного рода атакам реального мира. И это все в добавление к "
+"обычным проблемам безопасности, которые мы знаем. "
+
+#: i2p2www/pages/site/comparison/tor.html:34
+msgid ""
+"However, many people don't need to worry about those \n"
+"situations, as they are outside their threat model.  It\n"
+"is, also, outside I2P's (formal) functional scope (if people want\n"
+"to build outproxy functionality on top of an anonymous\n"
+"communication layer, they can).  In fact, some I2P users\n"
+"currently take advantage of Tor to outproxy."
+msgstr ""
+"Тем не менее, многим людям не стоит беспокоиться на этот счет, т.к. они "
+"за пределами угроз модели. Они также вне (формальной) границы I2P (если "
+"людям нужно сделать выходной узел, они могут его сделать). На самом деле,"
+" ряд пользователей I2P в качестве выходного узла используют Tor."
+
+#: i2p2www/pages/site/comparison/tor.html:48
+msgid "Comparison of Tor and I2P Terminology"
+msgstr "Сравнение терминологии Tor и I2P"
+
+#: i2p2www/pages/site/comparison/tor.html:49
+msgid ""
+"While Tor and I2P are similar in many ways, much of the terminology is "
+"different."
+msgstr ""
+"Хотя Tor и I2P во многом похожи, у них значительно отличается "
+"терминология."
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Cell"
+msgstr "Ячейка"
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Message"
+msgstr "Сообщение"
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Client"
+msgstr "Клиент"
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Router or Client"
+msgstr "Маршрутизатор или Клиент"
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Circuit"
+msgstr "Цепочка"
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Tunnel"
+msgstr "Туннель"
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "Directory"
+msgstr "Справочник"
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "NetDb"
+msgstr "NetDb"
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Directory Server"
+msgstr "Сервер справочников"
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Floodfill Router"
+msgstr "Floodfill маршрутизатор"
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Entry Guards"
+msgstr "Входные стражи"
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Fast Peers"
+msgstr "Быстрые пиры"
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Entry Node"
+msgstr "Входные узлы"
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Inproxy"
+msgstr "Входной прокси"
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Exit Node"
+msgstr "Выходной узел"
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Outproxy"
+msgstr "Выходной прокси"
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Hidden Service"
+msgstr "Скрытый сервис"
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Eepsite or Destination"
+msgstr "Eepsite или Назначение"
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "Hidden Service Descriptor"
+msgstr "Дескриптор скрытого сервиса"
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "LeaseSet"
+msgstr "LeaseSet"
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Introduction point"
+msgstr "Введение"
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Inbound Gateway"
+msgstr "Входной шлюз"
+
+#: i2p2www/pages/site/comparison/tor.html:65
+msgid "Node"
+msgstr "Узел"
+
+#: i2p2www/pages/site/comparison/tor.html:65
+#: i2p2www/pages/site/comparison/tor.html:67
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Router"
+msgstr "Маршрутизатор"
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "Onion Proxy"
+msgstr "Onion Proxy"
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "I2PTunnel Client (more or less)"
+msgstr "I2PTunnel клиент (более-менее)"
+
+#: i2p2www/pages/site/comparison/tor.html:67
+msgid "Relay"
+msgstr "Relay"
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "Rendezvous Point"
+msgstr "Точка встречи"
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "somewhat like Inbound Gateway + Outbound Endpoint"
+msgstr "что-то вроде Входной шлюз + Выходная точка"
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "Router Descriptor"
+msgstr "Дескриптор маршрутизатора"
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "RouterInfo"
+msgstr "RouterInfo"
+
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Server"
+msgstr "Сервер"
+
+#: i2p2www/pages/site/comparison/tor.html:73
+msgid "Benefits of Tor over I2P"
+msgstr "Преимущества Tor перед I2P"
+
+#: i2p2www/pages/site/comparison/tor.html:76
+msgid ""
+"Much bigger user base; much more visibility in the academic and hacker "
+"communities; benefits from\n"
+"formal studies of anonymity, resistance, and performance;\n"
+"has a non-anonymous, visible, university-based leader"
+msgstr ""
+"Значительно большая пользовательская база; Большее внимание со стороны "
+"науки и хакерского сообщества; выгоды от формальных исследований "
+"анонимности, сопротивления и производительности;\n"
+"известен не анонимный, видимый, связанный с университетом лидер"
+
+#: i2p2www/pages/site/comparison/tor.html:82
+msgid "Has already solved some scaling issues I2P has yet to address"
+msgstr ""
+"Уже разрешили ряд проблем масштабирования, к которым I2P еще просто не "
+"подошел"
+
+#: i2p2www/pages/site/comparison/tor.html:83
+msgid "Has significant funding"
+msgstr "Имеет значительное финансирование"
+
+#: i2p2www/pages/site/comparison/tor.html:84
+msgid "Has more developers, including several that are funded"
+msgstr "Больше разработчиков, включая ряд оплачиваемых"
+
+#: i2p2www/pages/site/comparison/tor.html:86
+msgid ""
+"More resistant to state-level blocking due to TLS transport layer and "
+"bridges\n"
+"(I2P has proposals for \"full restricted routes\" but these are not yet "
+"implemented)"
+msgstr ""
+"Более устойчивый к блокировкам на уровне государств, благодаря транспорту"
+" поверх TLS и мостам (I2P имеет предложения по \"полностью закрытым "
+"путям\", но они еще не реализованы)"
+
+#: i2p2www/pages/site/comparison/tor.html:91
+msgid "Big enough that it has had to adapt to blocking and DOS attempts"
+msgstr "Достаточно большая сеть, чтобы адаптироваться к блокировке и попыткам DOS"
+
+#: i2p2www/pages/site/comparison/tor.html:92
+msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
+msgstr ""
+"Разработан и оптимизирован для выхода трафика,  с большим числом выходных"
+" узлов"
+
+#: i2p2www/pages/site/comparison/tor.html:94
+msgid ""
+"Better documentation, has formal papers and specifications,\n"
+"better website, many more translations"
+msgstr ""
+"Лучше документация, есть исследования и спецификации,\n"
+"лучше вебсайт, гораздо больше переведенных данных"
+
+#: i2p2www/pages/site/comparison/tor.html:99
+msgid "More efficient with memory usage"
+msgstr "Более эффективен в использовании памяти"
+
+#: i2p2www/pages/site/comparison/tor.html:100
+msgid "Tor client nodes have very low bandwidth overhead"
+msgstr "Клиенты Tor работают с очень небольшими затратами на протоколе"
+
+#: i2p2www/pages/site/comparison/tor.html:102
+msgid ""
+"Centralized control reduces the complexity at each\n"
+"node and can efficiently address Sybil attacks"
+msgstr ""
+"Централизованный контроль уменьшает сложность каждого узла и может "
+"эффективно работать с атаками Sybil"
+
+#: i2p2www/pages/site/comparison/tor.html:108
+msgid ""
+"A core of high capacity nodes provides higher\n"
+"throughput and lower latency"
+msgstr ""
+"Набор высокопроизводительных узлов обеспечивает высокую "
+"производительность и меньшие задержки"
+
+#: i2p2www/pages/site/comparison/tor.html:113
+msgid "C, not Java (ewww)"
+msgstr "реализация на C, не Java (фу...)"
+
+#: i2p2www/pages/site/comparison/tor.html:116
+msgid "Benefits of I2P over Tor"
+msgstr "Преимущества I2P перед Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:118
+msgid ""
+"Designed and optimized for hidden services, which are much faster than in"
+" Tor"
+msgstr ""
+"Разработан и оптимизирован для работы скрытых сервисов, что гораздо "
+"быстрее, чем в Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:119
+msgid "Fully distributed and self organizing"
+msgstr "Полностью распределенная и самоорганизующаяся сеть"
+
+#: i2p2www/pages/site/comparison/tor.html:121
+msgid ""
+"Peers are selected by continuously profiling and ranking performance,\n"
+"rather than trusting claimed capacity"
+msgstr ""
+"Пиры выбираются на основе постоянного профайлинга и замеров по "
+"производительности,\n"
+"нежели по объявленной пиром пропускной способности"
+
+#: i2p2www/pages/site/comparison/tor.html:127
+msgid ""
+"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
+"rather than hardcoded"
+msgstr ""
+"Пиры Floodfill (\"справочные сервера\") постоянно меняются и не обладают "
+"доверием, в отличие от явно прошитых в Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:132
+msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
+msgstr "Достаточно небольшая, чтобы ее сильно блокировали или DOS'или. "
+
+#: i2p2www/pages/site/comparison/tor.html:133
+msgid "Peer-to-peer friendly"
+msgstr "Обеспечивает пиринговые сервисы"
+
+#: i2p2www/pages/site/comparison/tor.html:134
+msgid "Packet switched instead of circuit switched"
+msgstr "Коммутирует пакеты, нежели соединения"
+
+#: i2p2www/pages/site/comparison/tor.html:137
+msgid ""
+"implicit transparent load balancing of messages \n"
+"across multiple peers, rather than a single path"
+msgstr ""
+"Явная прозрачная балансировка сообщений по многим пирам, в отличие от "
+"использования одного пути"
+
+#: i2p2www/pages/site/comparison/tor.html:143
+msgid ""
+"resilience vs. failures by running multiple \n"
+"tunnels in parallel, plus rotating tunnels"
+msgstr ""
+"Надежность и отказоустойчивость за счет поддержания нескольких "
+"параллельных туннелей и обеспечения ротации туннелей"
+
+#: i2p2www/pages/site/comparison/tor.html:149
+msgid ""
+"scale each client's connections at O(1) instead \n"
+"of O(N) (Alice has e.g. 2 inbound tunnels that are \n"
+"used by all of the peers Alice is talking with, \n"
+"rather than a circuit for each)"
+msgstr ""
+"соединения каждого пользователя масштабируются как  O(1) вместо  O(N) "
+"(например, Алиса держит  2 входящих туннеля, которые может использовать "
+"любой пир, с которым Алиса общается, а не держим по цепочке на каждый "
+"пир)"
+
+#: i2p2www/pages/site/comparison/tor.html:159
+msgid ""
+"Unidirectional tunnels instead of bidirectional\n"
+"circuits, doubling the number of nodes a peer has to\n"
+"compromise to get the same information."
+msgstr ""
+"Односторонние туннели, вместо двусторонних цепочек, удваивая число узлов,"
+" которые пир должен скомпроменировать, чтобы получить ту же информацию"
+
+#: i2p2www/pages/site/comparison/tor.html:166
+msgid ""
+"Protection against detecting client activity, even\n"
+"when an attacker is participating in the tunnel, as\n"
+"tunnels are used for more than simply passing end \n"
+"to end messages (e.g. netDb, tunnel management, \n"
+"tunnel testing)"
+msgstr ""
+"Защита против детектирования клиентской активности, даже если\n"
+"атакующий участвует в туннеле, так как туннели используются не только для"
+" передачи сообщений, но и для работы NetDb, управления туннелями, "
+"проверки работоспособности туннелей)"
+
+#: i2p2www/pages/site/comparison/tor.html:175
+msgid ""
+"Tunnels in I2P are short lived, decreasing the number\n"
+"of samples that an attacker can use to mount an \n"
+"active attack with, unlike circuits in Tor, which are\n"
+"typically long lived."
+msgstr ""
+"В I2P реализованы короткоживущие туннели, что уменьшает количество "
+"примеров, которые атакующий может использовать для атаки, в отличие от "
+"цепочек в Tor'е, которые как правило живут долго. "
+
+#: i2p2www/pages/site/comparison/tor.html:183
+msgid ""
+"I2P APIs are designed specifically for anonymity and\n"
+"security, while SOCKS is designed for functionality."
+msgstr ""
+"API I2P спроектированы под анонимность и безопасность, тогда как SOCKS "
+"сделан для функциональности"
+
+#: i2p2www/pages/site/comparison/tor.html:188
+msgid "Essentially all peers participate in routing for others"
+msgstr ""
+"За редким исключением, все пиры участвуют в маршрутизации трафика для "
+"других"
+
+#: i2p2www/pages/site/comparison/tor.html:190
+msgid ""
+"The bandwidth overhead of being a full peer is low, \n"
+"while in Tor, while client nodes don't require much\n"
+"bandwidth, they don't fully participate in the mixnet."
+msgstr ""
+"Затраты на работу в полном режиме довольно низки, тогда как в Tor, если "
+"клиент сам по себе не требует много полосы, но они еще и не полностью "
+"используют сеть."
+
+#: i2p2www/pages/site/comparison/tor.html:196
+msgid "Integrated automatic update mechanism"
+msgstr "Встроенный механизм автоматических обновлений"
+
+#: i2p2www/pages/site/comparison/tor.html:197
+msgid "Both TCP and UDP transports"
+msgstr "Используется как TCP, так и UDP транспорт"
+
+#: i2p2www/pages/site/comparison/tor.html:198
+msgid "Java, not C (ewww)"
+msgstr "Реализация на Java, не C (фу....)"
+
+#: i2p2www/pages/site/comparison/tor.html:201
+msgid "Other potential benefits of I2P but not yet implemented"
+msgstr "Другие потенциальные, но еще не реализованные преимущества I2P"
+
+#: i2p2www/pages/site/comparison/tor.html:202
+msgid "...and may never be implemented, so don't count on them!"
+msgstr "... и возможно никогда не реализуемые, так что не рассчитывайте на них"
+
+#: i2p2www/pages/site/comparison/tor.html:205
+msgid ""
+"Defense vs. message count analysis by garlic wrapping \n"
+"multiple messages"
+msgstr ""
+"Защита от количественного анализа сообщений за счет\n"
+"заворачивания нескольких сообщений в одно"
+
+#: i2p2www/pages/site/comparison/tor.html:211
+msgid ""
+"Defense vs. long term intersection by adding delays \n"
+"at various hops (where the delays are not discernible\n"
+"by other hops)"
+msgstr ""
+"Защита от статистического анализа за счет добавления задержек на разных "
+"хопах\n"
+"(где задержки не зависят от других хостов)"
+
+#: i2p2www/pages/site/comparison/tor.html:218
+msgid ""
+"Various mixing strategies at the tunnel level (e.g.\n"
+"create a tunnel that will handle 500 messages / minute,\n"
+"where the endpoint will inject dummy messages if there\n"
+"are insufficient messages, etc)"
+msgstr ""
+"Разные стратегии имитовставки на уровне туннелей (например\n"
+"создание туннеля, который будет обрабатывать 500 сообщений в минуту, \n"
+"где эндпойнт посылает случайные данные, если полезный трафик не "
+"передается и т.д)"
+
diff --git a/i2p2www/translations/sv/LC_MESSAGES/messages.po b/i2p2www/translations/ru/LC_MESSAGES/docs.po
similarity index 55%
rename from i2p2www/translations/sv/LC_MESSAGES/messages.po
rename to i2p2www/translations/ru/LC_MESSAGES/docs.po
index b2d44e31..9e66c8a1 100644
--- a/i2p2www/translations/sv/LC_MESSAGES/messages.po
+++ b/i2p2www/translations/ru/LC_MESSAGES/docs.po
@@ -1,6289 +1,42 @@
-# Swedish translations for I2P.
+# Russian (Russia) translations for I2P.
 # Copyright (C) 2013 ORGANIZATION
 # This file is distributed under the same license as the I2P project.
 #
 # Translators:
-# hottuna , 2013
-# Martin Svensson , 2013
+# sassy , 2013
+# TrackIt , 2013
 msgid ""
 msgstr ""
 "Project-Id-Version:  I2P\n"
-"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
-"POT-Creation-Date: 2013-07-03 03:49+0000\n"
-"PO-Revision-Date: 2013-04-27 23:10+0000\n"
-"Last-Translator: Martin Svensson \n"
-"Language-Team: Swedish (Sweden) "
-"(http://www.transifex.com/projects/p/I2P/language/sv_SE/)\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-12-12 06:19+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: Russian (Russia) "
+"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 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/blog/2011/10/11/0.8.9-Release.rst:24
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:25
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:12
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:12
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:17
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:16
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:16
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:26
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:19
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:19
-msgid "Files are available on the `download page`_."
-msgstr "Filerna finns på `nerladdningssidan`_."
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:28
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:15
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:29
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:16
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:16
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:21
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:20
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:20
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:30
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:23
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:23
-msgid "`download page`"
-msgstr "`nerladdningssidan`"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:30
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:17
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:31
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:18
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:19
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:18
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:22
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:22
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:32
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:25
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:79
-msgid "RELEASE DETAILS"
-msgstr "RELEASE DETALJER"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:32
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:19
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:33
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:40
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:50
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:24
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:24
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:34
-msgid "Major Changes"
-msgstr "Stora Förändringar"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:44
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:24
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:43
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:55
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:47
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:58
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:43
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:32
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:30
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:39
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:81
-msgid "Bug Fixes"
-msgstr "Buggfixar"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:54
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:30
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:47
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:69
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:63
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:68
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:54
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:41
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:36
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:51
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:43
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:94
-msgid "Other"
-msgstr "Andra"
-
-#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:73
-#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:36
-#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:51
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:82
-#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:75
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:96
-#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:76
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:52
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:56
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:67
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:56
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:110
-msgid "SHA256 Checksums:"
-msgstr "SHA256 Kontrollsummor:"
-
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39
-msgid "Major changes"
-msgstr ""
-
-#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47
-msgid "Wrapper Update"
-msgstr ""
-
-#: i2p2www/blog/2012/05/02/0.9-Release.rst:23
-msgid "Update Info"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2
-msgid "0.9.2 Release"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9
-msgid ""
-"0.9.2 includes extensive low-level changes to improve the performance and"
-" efficiency of the router. We have updated our UPnP library, to hopefully"
-" make UPnP work for more people. I2PSnark now has DHT support, but it is "
-"not yet enabled by default, as we plan to do more testing during the "
-"upcoming 0.9.3 development cycle."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12
-msgid ""
-"As usual, there's also lots of bug fixes in this release, so updating is "
-"recommended."
-msgstr ""
-"Som vanligt finns även många buggfixar i den här releasen, så uppdatering"
-" rekommenderas."
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26
-msgid ""
-"SSU: Fix several problems in our UDP transport, to improve efficiency and"
-" reliability for connection setup. Also improve defenses against various "
-"types of bad input."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27
-msgid ""
-"UPnP: Updated our library to fix several issues, should work for more "
-"routers now"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28
-msgid ""
-"Transport: Improve performance in both our TCP and UDP transports, to "
-"benefit high-bandwidth routers"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29
-msgid ""
-"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered "
-"are now much more flexible, which should lessen protocol overhead and "
-"reduce stalls caused by dropped tags."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30
-msgid ""
-"I2PSnark: Add DHT support, not yet enabled by default, will do further "
-"testing and plan to enable by default in 0.9.3."
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34
-msgid ""
-"Fix various issues affecting memory usage and performance on high-"
-"bandwidth routers"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35
-msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36
-msgid "Fix i2psnark bug that prevented a completion announcement to the tracker"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37
-msgid "Fix a lock contention problem in i2ptunnel"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38
-msgid "Fix some OSX installation issues"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39
-msgid "Remove uses of direct byte buffers that may have been leaking"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43
-msgid "Reduce overhead in network messages"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44
-msgid "Add \"universal\" theme support"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45
-msgid "Theme updates"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46
-msgid "Add a jbigi library for Raspberry Pi"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47
-msgid "New Scala unit test framework"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48
-msgid "Translation updates for Czech, Dutch, German, and Greek"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49
-msgid "Update wrapper to 3.5.15 (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108
-msgid "Update GeoIP data (new installs and PPA only)"
-msgstr "Uppdatera GeoIP data (enbart nya installationer och PPA)"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:2
-msgid "0.9.3 Release"
-msgstr "0.9.3 Release"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9
-msgid ""
-"0.9.3 includes extensive low-level changes to the queueing of messages in"
-" the router.  We implement the CoDel Active Queue Management (AQM) "
-"algorithm.  We also unify the queueing and priority mechanisms in the "
-"transports to aid diagnosis and reduce network latency.  Work continues "
-"on fixing UDP transport bugs and making UDP more resistant to attacks.  "
-"There are more changes to improve the performance of the router and "
-"reduce its memory usage.  Also, we enable i2psnark's DHT support, "
-"introduced last release, by default."
-msgstr ""
-"0.9.3 inkluderar utförliga låg-nivå förändringar vid köandet av "
-"meddelanden i routern. \n"
-"Vi implementerar CoDel Active Queue Management (AQM) algoritmen. \n"
-"Vi förenar även kö och prioritets mekanismerna i transportlagret för att "
-"underlätta diagnos och reducera nätverksfördröjningar.\n"
-"Arbete fortsätter med att korrigera buggar i UDP transportlagret och att "
-"göra UDP mer motståndskraftigt mot attacker.\n"
-"Det finns fler förändringar som förbättrar prestandan av routern och "
-"reducerar dess minnesanvändning.\n"
-"Vi slår även på i2psnarks DHT-stöd, som introducerades i förra releasen, "
-"som standard."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26
-msgid "Active Queue Management"
-msgstr "Active Queue Management"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:27
-msgid "Priority queues"
-msgstr "Prioritetsköer"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28
-msgid "I2PSnark DHT: Several bug fixes, enable by default."
-msgstr "I2PSnark DHT: Flera buggfixar, påslaget som standard."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32
-msgid ""
-"Several SSU fixes including memory leak, and better handling of routers "
-"behind firewalls that change UDP ports; additional defenses for malicious"
-" packets."
-msgstr ""
-"Flera SSU-fixar inklusive minnesläcka, bättra hantering av routrar bakom "
-"brandväggar som byter UDP-port och ytterliggare försvar mot illvilliga "
-"paket."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33
-msgid "Fix piece selection (rarest-first) bugs in i2psnark"
-msgstr "Fixa del val (ovanligaste först)  buggar i i2psnark"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34
-msgid "Fix bug causing multiple browsers to open at startup"
-msgstr "Fixa bugg som får multipla webbläsare att öppnas vid start"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38
-msgid "Improvements in caching"
-msgstr "Förbättringar i caching."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39
-msgid "Several synchronization fixes and lock contention reduction"
-msgstr "Flera synkroniserings-fixar och minskning i lås-kamp."
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40
-msgid "Major reduction in SSU buffers memory use"
-msgstr "Stor förminskning i SSU-bufferns minnesanvändning"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41
-msgid ""
-"Fix streaming connection timeout back to 1 minute, was inadvertently "
-"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was"
-" unlimited"
-msgstr ""
-"Fixa timeout för strömmande anslutningar tillbaka till 1 minut, råkades "
-"ändras till 5 minuter. Sätt i2ptunnel server timout till 5 minuter, was "
-"obegränsad"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42
-msgid "Improved defenses in i2ptunnel for \"darkloris\""
-msgstr "Förbättra försvaret mot \"darkloris\" attacker i i2ptunnel"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:43
-msgid "More validation at torrent creation in i2psnark"
-msgstr "Mera validering vid torrent-skapning i i2psnark"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44
-msgid "Several parameter changes in SSU to improve throughput"
-msgstr "Flera parameterförändringar i SSU för att förbättra genomströming"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45
-msgid ""
-"New event log for major events including restarts; show multiple restart "
-"lines on graphs"
-msgstr ""
-"Ny händelselogg för stora händelser som omstarter, visa flera "
-"omstartningslinjer på grafer"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46
-msgid "Remove duplicate messages from logs"
-msgstr "Ta bort duplicerade meddelanden från loggar"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47
-msgid "Don't respond to blocked streaming connections with a reset, just drop"
-msgstr ""
-"Svara inte på blockerade strömmande anslutningar med ett 'reset' "
-"kommando, bara släpp"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48
-msgid "Remove all uses of inefficient SimpleTimer"
-msgstr "Ta bort alla användningar av den ineffektiva SimpleTimer"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49
-msgid "More checks for valid IPs and ports entered in console"
-msgstr "Flera kontroller för giltiga IP-adresser och portar inskrivna i konsollen"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50
-msgid "Fix bug that wasted a lot of entropy"
-msgstr "Fixa en bugg som slösade mycket entropi"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51
-msgid "Translation updates: Italian, Portuguese, Spanish, Swedish"
-msgstr "Översättningsuppdateringar: Italienska, Portugisiska, Spanska, Svenska"
-
-#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52
-msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5"
-msgstr "La till icke-NIO konfiguration i jetty.xml, rekommenderas för Java 5"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2
-msgid "0.9.4 Release"
-msgstr "0.9.4 Release"
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9
-msgid ""
-"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, "
-"that was reducing network performance and reliability. It also includes "
-"major changes in the in-network update system, and adds the capability to"
-" update via in-network torrents."
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13
-msgid ""
-"We fixed several bugs in the i2psnark DHT implementation that was "
-"introduced\n"
-"last release. For those of you using console or http proxy passwords,\n"
-"we converted to the more-secure digest method and improved the security "
-"for console forms."
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19
-msgid ""
-"For those of you already running development builds, your router should "
-"automatically\n"
-"update to 0.9.4-0 using the new in-network torrent facility.\n"
-"For those running 0.9.3-0, you will update normally using in-network "
-"HTTP, and\n"
-"we will have more information for you when we release 0.9.5."
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36
-msgid ""
-"Big rework of the update system; Preliminary support for updates via "
-"i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37
-msgid "Add per-destination outbound priorities"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41
-msgid ""
-"Fix major bug that reduced SSU connection limits which reduced tunnel "
-"build success rates"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42
-msgid "Fix bug with external I2CP that prevented some external apps from working"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43
-msgid "Fixed several bugs in i2psnark DHT"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44
-msgid "Fixed bug in i2psnark PEX that inflated peer counts"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45
-msgid "Handle dropped I2CP messages better"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46
-msgid "Reduce overhead of I2CP messages"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47
-msgid "Enforce max size in transport outbound message queues"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48
-msgid "Fixes for Windows eepget.bat (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49
-msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53
-msgid ""
-"More performance improvements, memory reduction, and object churn "
-"reduction"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54
-msgid "Better detection of network disconnections"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55
-msgid "Further improvements in the SSU transport"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56
-msgid "Add console password form"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57
-msgid ""
-"Convert http proxy and console from basic to digest authentication for "
-"added security"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58
-msgid ""
-"Improved verification of console form submissions, using jsp sessions. "
-"Cookies may now be required on forms, except when the console password is"
-" enabled"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59
-msgid ""
-"Initial work on new interfaces to manage applications started via "
-"clients.config"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60
-msgid "Increase minimum peer port to 1024"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61
-msgid "Increase granularity of bandwidth limiter for smoother transmissions"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62
-msgid ""
-"Translation updates: Chinese, French, German, Italian, Polish, "
-"Portuguese, Swedish, and Ukrainian"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64
-msgid "Update wrapper to 3.5.16 (new installs and PPA only)"
-msgstr ""
-
-#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65
-msgid "New ARMv6 wrapper for Raspberry Pi"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:2
-#, fuzzy
-msgid "0.9.5 Release"
-msgstr "0.9.4 Release"
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9
-msgid ""
-"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities"
-" that are being investigated by researchers at UCSB. We continue to work "
-"with them on additional improvements. This is a good opportunity to "
-"remind the community that while our network continues to grow rapidly, it"
-" is still relatively small. There may be multiple weaknesses or bugs that"
-" could compromise your anonymity. Help us grow the network by spreading "
-"the word and contributing where you can."
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13
-#, python-format
-msgid ""
-"In this upgrade cycle, a random 1% of routers, (plus all routers running "
-"a\n"
-"development build) will attempt to update via the experimental in-network"
-" bittorrent\n"
-"with i2psnark. If this doesn't work, it should fall back to standard in-"
-"network HTTP update."
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27
-msgid "Defenses and Bug Fixes"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29
-msgid "Fix router bug causing lockup when using iMule"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30
-msgid "Recognize, handle, reject duplicate tunnel IDs"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31
-msgid "Fix changing of the log file name"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32
-msgid "Prevent hashcode attack in session tags"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33
-msgid "Add build request throttler based on previous hop"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34
-msgid "Limit concurrent next-hop lookups"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35
-msgid "Catch exceptions storing nonces in console"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36
-msgid "Fix saving graph settings in console"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37
-msgid "Fix eepget generation of URLs when not proxied"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38
-msgid ""
-"Encrypt database lookup messages end-to-end when sent through exploratory"
-" tunnels"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39
-msgid "Don't use multiple floodfills from the same /16 in a query"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40
-msgid "Randomize delay before verifying floodfill store"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41
-msgid "Increase number of floodfills"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:45
-msgid "Improve support for mobile browsers"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46
-msgid "Partial defenses for UCSB attacks"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47
-msgid "Add announce list support to i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48
-msgid "Jetty: upgrade Apache Tomcat to 6.0.36"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49
-msgid "Split router info files into multiple subdirectories"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50
-msgid "Add IP to hostname mapping option in SOCKS"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51
-msgid "Improve PRNG seeding"
-msgstr ""
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52
-#, fuzzy
-msgid ""
-"Translation updates: French, German, Hungarian, Italian, Norwegian, "
-"Polish, Portuguese, Russian, Swedish"
-msgstr "Översättningsuppdateringar: Italienska, Portugisiska, Spanska, Svenska"
-
-#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54
-#, fuzzy
-msgid "Update wrapper to 3.5.17 (new installs and PPA only)"
-msgstr "Uppdatera GeoIP data (enbart nya installationer och PPA)"
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:2
-#, fuzzy
-msgid "0.9.6 Release"
-msgstr "0.9.4 Release"
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:7
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9
-msgid ""
-"0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to "
-"Jetty 7.6.10 (2013-03-12). See below for important information on the "
-"Jetty update. The Jetty 7 series is actively maintained and we plan to "
-"stay current with it in future I2P releases."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13
-msgid ""
-"Most users will update via HTTP. Those running development builds will "
-"attempt to update via the\n"
-"experimental in-network bittorrent with i2psnark. We've fixed some bugs "
-"that will enable more users\n"
-"to update via torrent in the 0.9.7 update cycle."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25
-msgid "Important fix for Windows Eepsites, first install 0.9.5 only"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27
-msgid ""
-"If you first installed I2P with version 0.9.5, on Windows only, we "
-"recommend that you follow the\n"
-"following instructions to fix your eepsite location **before** you update"
-" to 0.9.6.\n"
-"Only original installations of 0.9.5-0 on Windows are affected by this "
-"issue. If your router version\n"
-"is 0.9.5-0-win1, you already have the fix and need not take any action."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34
-msgid "See `this page`_ for instructions."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:38
-msgid "`this page`"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:40
-msgid "Jetty 7 Migration Details"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42
-msgid ""
-"For most people, the update should just work. If you have multiple Jetty "
-"eepsites,\n"
-"OR have made changes to jetty.xml or other Jetty configuration files, "
-"including changing the port\n"
-"from 7658, you MUST take manual action AFTER updating."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48
-msgid ""
-"After update, the router will migrate your jetty.xml files to the new "
-"Jetty 7 format."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50
-msgid ""
-"The migration resets the port to 7658. If you have more than one Jetty "
-"eepsite, OR your eepsite\n"
-"  is NOT on port 7658, OR you have made other modifications to jetty.xml "
-"(for example changing the\n"
-"  listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml "
-"file for each eepsite to fix them up\n"
-"  after updating, and restart again."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55
-msgid ""
-"**The following files will be backed up with a ".jetty6" suffix"
-" and then migrated.**\n"
-"If you have made local changes, you may have to edit them manually and "
-"restart.\n"
-"See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69
-#: i2p2www/pages/global/nav.html:75 i2p2www/pages/global/nav.html:91
-#: i2p2www/pages/site/docs/plugins.html:2
-#: i2p2www/pages/site/docs/spec/configuration.html:65
-msgid "Plugins"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:71
-msgid "Most plugins should work fine with Jetty 7."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:75
-msgid ""
-"The I2PControl and zzzot plugins must be updated. Your router should "
-"download and install the new versions shortly after starting 0.9.6."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77
-msgid "If a plugin does not work, please contact the maintainer for that plugin."
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83
-msgid "Several bugs with Windows installation (see above)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:84
-msgid "Fix default form action in i2ptunnel"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85
-msgid "Fix links on iframed console pages"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86
-msgid "Better detection of 64-bit Windows to prevent crashes by systray"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87
-msgid "Fix bug preventing router update via torrent"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88
-msgid "Several SSU fixes for NATs that change UDP ports"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89
-msgid ""
-"Ignore unsupported IPs in RouterInfos when selecting an address (prep for"
-" IPv6)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90
-msgid ""
-"Ignore unused option bits in Database Lookup Message (prep for requesting"
-" encrypted response)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91
-msgid "Fix HTTP proxy error response for malformed URIs"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92
-msgid "Recognize UPnP devices without port forwarding capability"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96
-msgid "Jetty 7.6.10 (see above for migration information)"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97
-msgid "Limit page size in i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98
-msgid "Add data directory and page size configuration to i2psnark"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99
-msgid "Support multiple i2psnark instances"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100
-#, fuzzy
-msgid "Piece size adjustments in i2psnark"
-msgstr "Fixa del val (ovanligaste först)  buggar i i2psnark"
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101
-msgid "Add more graphing support for combined bandwidth graph"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102
-msgid "Block b32.i2p supercookies"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103
-msgid "Allow stopping clients on /configclients"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104
-msgid "Check for nonce count replays in HTTP client"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105
-msgid "Support SASL authentication in IRC proxy"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106
-msgid "Several cleanups and minor fixes in the update manager"
-msgstr ""
-
-#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107
-#, fuzzy
-msgid "Translation updates: German, Portuguese, Russian, Spanish, and Swedish"
-msgstr "Översättningsuppdateringar: Italienska, Portugisiska, Spanska, Svenska"
-
-#: i2p2www/pages/blog/category.html:2
-msgid "Blog Category"
-msgstr ""
-
-#: i2p2www/pages/blog/category.html:4
-#, python-format
-msgid "I2P Blog ATOM Feed for Category: %(category)s"
-msgstr ""
-
-#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
-#: i2p2www/pages/global/nav.html:95
-msgid "Blog"
-msgstr ""
-
-#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:75
-msgid "I2P Blog ATOM Feed"
-msgstr ""
-
-#: i2p2www/pages/blog/index.html:17
-#, python-format
-msgid "Posted %(date)s by %(author)s"
-msgstr ""
-
-#: i2p2www/pages/blog/latest.html:5
-msgid "More blog posts…"
-msgstr ""
-
-#: i2p2www/pages/blog/post.html:6
-msgid "Posted:"
-msgstr ""
-
-#: i2p2www/pages/blog/post.html:7
-msgid "Author:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:4
-msgid "Debian I2P Packages"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:6
-#, python-format
-msgid ""
-"The packages hosted on the I2P Launchpad site\n"
-"have been tested and should work on x86/x86_64 platforms running:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:11
-msgid "Ubuntu (Precise 12.04 and newer)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:13
-msgid ""
-"Debian Linux (Wheezy and newer) & kFreeBSD"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:17
-#, python-format
-msgid ""
-"The I2P packages may work on systems not listed above. Please "
-"report any issues\n"
-"with these packages on Trac at\n"
-"http://%(trac)s."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:23
-msgid ""
-"Option 1: Recent versions of Ubuntu and its "
-"derivatives (Try this if you're not using Debian)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:24
-msgid "Option 2: Debian (including Debian-derivatives)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:25
-msgid ""
-"Option 3: Non-Linux (and possibly Non-x86 "
-"architectures)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:28
-msgid ""
-"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
-" Linux Mint & Trisquel"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:29
-msgid "Adding the PPA via the command line and installing I2P"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:32
-msgid "Open a terminal and enter:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:34
-msgid ""
-"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
-"gpg key that the repository has been signed with. The GPG key ensures\n"
-"that the packages have not been tampered with since being built."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:41
-msgid "Notify your package manager of the new PPA by entering:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:43
-msgid ""
-"This command will retrieve the latest list of software from each\n"
-"repository that is enabled on your system, including the I2P PPA that\n"
-"was added with the earlier command."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:49
-#: i2p2www/pages/downloads/debian.html:112
-#: i2p2www/pages/downloads/debian.html:137
-msgid "You are now ready to install I2P!"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:53
-msgid "Adding the PPA Using Synaptic"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:56
-msgid ""
-"Open Synaptic (System -> Administration -> Synaptic Package "
-"Manager)."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:61
-msgid ""
-"Once Synaptic opens, select Repositories from the "
-"Settings menu."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:66
-msgid ""
-"Click the Other Sources tab and click Add. Paste "
-"ppa:i2p-maintainers/i2p into the APT-line field and click "
-"Add Source. Click the Close button then "
-"Reload."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:71
-msgid ""
-"In the Quick Filter box, type in i2p and press enter. When "
-"i2p is returned in the results list, right click "
-"i2p and select Mark for Installation. After doing "
-"so you may see a Mark additional required changes? popup. If so,"
-" click Mark then Apply."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:77
-msgid ""
-"After the installation process completes you can move on to the next\n"
-"part of starting I2P and configuring "
-"it for your system."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:82
-msgid "Instructions for Debian Lenny and newer"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:84
-msgid ""
-"For Squeeze you can follow the instructions here."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:86
-msgid ""
-"The steps below should be performed with root access (i.e., switching\n"
-"user to root with \"su\" or by prefixing each command with \"sudo\")."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:92
-msgid "Add the GPG key that signs the repository with the following command:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:94
-msgid "You'll have output like the following if the command was successful:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:98
-msgid "Add the following entries to /etc/apt/sources.list.d/i2p.list"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:103
-msgid "Notify your package manager of the new PPA by entering"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:105
-msgid ""
-"This command will retrieve the latest list of software from every\n"
-"repository enabled on your system, including the I2P PPA added in step\n"
-"1."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:116
-#: i2p2www/pages/downloads/debian.html:147
-msgid ""
-"After the installation process completes you can move on to the next part"
-" of starting I2P and configuring it "
-"for your system."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:120
-msgid "Instructions for Non-Linux / Non-x86"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:122
-msgid ""
-"The steps below should be performed with root access (i.e., switching\n"
-"user to root with \"su\" or by prefixing each command with "
-"\"sudo\")."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:128
-#, python-format
-msgid ""
-"Download the i2p-router package from the PPA.\n"
-"Alternatively, there are unofficial packages available here for armel, armhf, and kfreebsd."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:135
-msgid ""
-"Make sure that you have Java installed. Running apt-get install"
-" default-jre should be sufficient."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:141
-#, python-format
-msgid ""
-"It is recommended to compile jbigi for your "
-"system to achieve better performance. Instructions are available here."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:151
-#: i2p2www/pages/downloads/list.html:167
-msgid "Post-install work"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:154
-msgid ""
-"Using these I2P packages the I2P router can be started in the following\n"
-"three ways:"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:160
-msgid ""
-""on demand" using the i2prouter script. Simply run "
-""i2prouter\n"
-"start" from a command prompt. (Note: Do "
-"not use\n"
-"sudo or run it as root!)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:167
-msgid ""
-""on demand" without the java service wrapper\n"
-"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
-"nowrapper\".\n"
-"(Note: Do not\n"
-"use sudo or run it as root!)"
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:175
-msgid ""
-"as a service that automatically runs when your system boots, even\n"
-"before logging in. The service can be enabled with \"dpkg-"
-"reconfigure\n"
-"i2p\" as root or using sudo. This is the recommended means of "
-"operation."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:183
-msgid ""
-"When installing for the first time, please remember to adjust your "
-"NAT/firewall\n"
-"if you can. The ports to forward can be found on the \n"
-"network configuration page in the router console. If guidance with "
-"respect to forwarding ports is needed,\n"
-"you may find portforward.com to be"
-" helpful."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:190
-msgid ""
-"Please review and adjust the bandwidth settings on the\n"
-"configuration page,\n"
-"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
-"conservative."
-msgstr ""
-
-#: i2p2www/pages/downloads/debian.html:196
-#: i2p2www/pages/downloads/list.html:200
-#, python-format
-msgid ""
-"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
-"howto."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
-#: i2p2www/pages/global/nav.html:3
-msgid "Download"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:4
-msgid "Download I2P"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:6
-msgid "Dependency"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:7
-#, python-format
-msgid ""
-"\n"
-"Java Runtime 1.5 or higher.\n"
-"(Oracle Java Version 6/7,\n"
-"OpenJDK 6/7, or\n"
-"IcedTea6/7\n"
-" recommended)\n"
-"
            \n"
-"Determine"
-" your installed Java version here\n"
-"or type java -version at your command prompt.\n"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:20
-msgid "Clean installs"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:27 i2p2www/pages/downloads/list.html:45
-#: i2p2www/pages/downloads/list.html:73 i2p2www/pages/downloads/list.html:135
-#: i2p2www/pages/downloads/list.html:265
-msgid "select alternate link"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:35
-msgid "Download that file and run it."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:53
-#, python-format
-msgid ""
-"Download that file and double-click it (if that works) or\n"
-"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
-"terminal to run the\n"
-"    installer.\n"
-"    You may be able to right-click and select\n"
-"    "Open with Java"."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:61 i2p2www/pages/downloads/list.html:89
-msgid "Command line (headless) install:"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:62
-#, python-format
-msgid ""
-"Download the %(i2pversion)s OSX graphical installer file above and\n"
-"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
-"from the command line."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:81
-#, python-format
-msgid ""
-"Download that file and double-click it (if that works) or\n"
-"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
-"terminal to run the\n"
-"    installer.\n"
-"    On some platforms you may be able to right-click and select\n"
-"    "Open with Java"."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:90
-#, python-format
-msgid ""
-"Download the graphical installer file above and\n"
-"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
-"from the command line."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:100
-msgid "Packages for Debian & Ubuntu are available."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:115
-#, python-format
-msgid ""
-"The Android version of I2P is being actively developed.\n"
-"    The latest dev build is version 0.9.3-5_b2-API8, and is available "
-"from\n"
-"    sponge's eepsite -\n"
-"    scan or click the QR code."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:122
-msgid ""
-"The release and dev versions of the I2P APK are not compatible, as they\n"
-"      are signed by zzz and sponge respectively. Uninstall one before "
-"installing\n"
-"      the other."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:132
-msgid "Source package"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:143
-#, python-format
-msgid ""
-"Alternately, you can fetch the source from monotone\n"
-"    or via Git from git.repo.i2p or Github.\n"
-"    
            \n"
-"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
-"i2p-%(i2pversion)s ; ant pkg) then either\n"
-"    run the GUI installer or headless install as above."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:158
-#, python-format
-msgid ""
-"The files are signed by zzz,\n"
-"whose key is here."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:163
-msgid ""
-"I2P can also be downloaded from our project pages on Launchpad and Google Code."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:169
-msgid ""
-"After running the installer on windows, simply click on the \"Start I2P\""
-" button\n"
-"which will bring up the router console,\n"
-"which has further instructions."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:175
-msgid ""
-"On Unix-like systems, I2P can be started as a service\n"
-"using the \"i2prouter\" script, located in the directory you selected for"
-" I2P.\n"
-"Changing to that directory in a console and issuing \"sh i2prouter "
-"status\"\n"
-"should tell you the router's status. The arguments \"start\", \"stop\" "
-"and \"restart\"\n"
-"control the service. The router console\n"
-"can be accessed at its usual location.\n"
-"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
-" is not supported,\n"
-"start the router with \"sh runplain.sh\" instead."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:186
-#, python-format
-msgid ""
-"When installing for the first time, please remember to adjust your "
-"NAT/firewall\n"
-"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
-"described here among other ports.\n"
-"If you have successfully opened your port to inbound TCP, also enable "
-"inbound TCP on the\n"
-"configuration page."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:194
-msgid ""
-"Also, please review and adjust the bandwidth settings on the\n"
-"configuration page,\n"
-"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:204
-msgid "Updates from earlier releases:"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:206
-msgid "Both automatic and manual upgrades are available for the release."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:211
-msgid "Automatic updates"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:213
-msgid ""
-"If you are running 0.7.5 or later, your router should detect the\n"
-"new release. To upgrade simply click the 'Download Update' button on your"
-" router console\n"
-"when it appears."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:219
-msgid ""
-"Due to a bug in release 0.7.6, those whose first I2P installation was "
-"that version\n"
-"and have not upgraded manually\n"
-"may get a \"downloaded version is not greater than current version\" "
-"error,\n"
-"and should use the manual update method below."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:227
-#, python-format
-msgid ""
-"If you are running 0.7.4 or earlier, please see\n"
-"the 0.7.5 release notes\n"
-"for important information about how to configure your router to "
-"automatically\n"
-"receive the release."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:235
-#, python-format
-msgid ""
-"If you are running 0.6.1.30 or earlier, please see\n"
-"instructions\n"
-"for important information about how to configure your router to "
-"automatically\n"
-"receive the release."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:244
-#, python-format
-msgid ""
-"If you have reconfigured your router following the instructions, you should see a link on your"
-" \n"
-"    router console "
-"allowing\n"
-"    you to download and install the new release by just clicking on that\n"
-"    link."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:252
-msgid "Alternately, you can use the manual method specified below."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:262
-msgid "Manual updates"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:275
-msgid ""
-"Download that file to your I2P\n"
-"    installation directory and rename as i2pupdate.zip.\n"
-"    (alternately, you can get the source as above and run \"ant "
-"updater\", then copy the\n"
-"    resulting i2pupdate.zip to your I2P installation directory).  You do"
-" \n"
-"    NOT need to unzip that file."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:284
-msgid "Click \"Restart\""
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:289
-msgid "Grab a cup of coffee and come back in 11 minutes"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:297
-#, python-format
-msgid ""
-"The file is signed by zzz,\n"
-"whose key is here."
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:302
-msgid "Previous Releases"
-msgstr ""
-
-#: i2p2www/pages/downloads/list.html:304
-#, python-format
-msgid ""
-"Previous releases are available on Google "
-"Code\n"
-"and Launchpad\n"
-"and within the I2P network on %(echelon)s."
-msgstr ""
-
-#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
-msgid "Mirror selection"
-msgstr ""
-
-#: i2p2www/pages/downloads/select.html:5
-msgid "File:"
-msgstr ""
-
-#: i2p2www/pages/downloads/select.html:10
-msgid "Any mirror"
-msgstr ""
-
-#: i2p2www/pages/global/bounty.html:19
-msgid ""
-"To claim the bounty the author must not be paid by other organizations\n"
-"or teams for this work (e.g. GSoC students are not valid)."
-msgstr ""
-
-#: i2p2www/pages/global/bounty.html:29
-#, python-format
-msgid ""
-"Bounty amounts may be increased by further donations.  Do\n"
-"you think these are important? Add in your "
-"donation, \n"
-"marking the amount for the %(donatename)s bounty!"
-msgstr ""
-
-#: i2p2www/pages/global/error_404.html:3
-msgid "Not found"
-msgstr ""
-
-#: i2p2www/pages/global/error_404.html:9
-msgid ""
-"Yep... the resource, you were searching for, is named differently, "
-"doesn't exist or was removed."
-msgstr ""
-
-#: i2p2www/pages/global/error_500.html:5
-msgid "Server error"
-msgstr ""
-
-#: i2p2www/pages/global/error_500.html:13
-msgid "500 Server error"
-msgstr ""
-
-#: i2p2www/pages/global/error_500.html:17
-msgid "Umm... the server encountered some sort of error."
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:2
-msgid "Mirrors"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:10
-msgid "Secure"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:16
-msgid "Misc."
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
-msgid "Links"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:20
-msgid "Impressum"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:24
-msgid "T-Shirts!"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:26
-msgid "Europe"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:27
-msgid "USA"
-msgstr ""
-
-#: i2p2www/pages/global/footer.html:31
-#: i2p2www/pages/site/get-involved/donate.html:2
-#: i2p2www/pages/site/get-involved/index.html:74
-msgid "Donate"
-msgstr ""
-
-#: i2p2www/pages/global/layout.html:29
-msgid "Skip navigation"
-msgstr ""
-
-#: i2p2www/pages/global/layout.html:32
-msgid "I2P Logo"
-msgstr ""
-
-#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
-#: i2p2www/pages/site/about/intro.html:4
-msgid "The Invisible Internet Project"
-msgstr ""
-
-#: i2p2www/pages/global/layout.html:56
-#, python-format
-msgid ""
-"This page was last updated in %(lastupdated)s and is accurate for router "
-"version %(accuratefor)s."
-msgstr ""
-
-#: i2p2www/pages/global/layout.html:60
-#, python-format
-msgid "This page was last updated in %(lastupdated)s."
-msgstr ""
-
-#: i2p2www/pages/global/layout.html:64
-#, python-format
-msgid "This page is accurate for router version %(accuratefor)s."
-msgstr ""
-
-#: i2p2www/pages/global/macros:19
-msgid "Previous"
-msgstr ""
-
-#: i2p2www/pages/global/macros:34
-msgid "Next"
-msgstr ""
-
-#: i2p2www/pages/global/macros:41
-msgid "Posted in"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:4
-msgid "About"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:6
-msgid "Introduction to I2P"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:7
-msgid "Comparisons"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:9
-msgid "Overview of comparisons"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:13
-msgid "Other anonymous networks"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:16
-#: i2p2www/pages/site/get-involved/index.html:29
-msgid "Documentation"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:18
-msgid "Documentation index"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:19 i2p2www/pages/site/about/intro.html:17
-msgid "How does it work?"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:21
-msgid "Gentle intro"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:22
-msgid "Tech intro"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:23
-msgid "Threat model"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:24
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:292
-msgid "Garlic routing"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:25
-msgid "Network database"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:26
-msgid "Tunnel routing"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:27
-#: i2p2www/pages/site/docs/tunnels/unidirectional.html:21
-msgid "Peer selection"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:28
-#: i2p2www/pages/site/docs/how/tech-intro.html:17
-#: i2p2www/pages/site/docs/how/tech-intro.html:458
-msgid "Cryptography"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:29
-msgid "ElGamal/AES+SessionTags"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:32 i2p2www/pages/global/nav.html:116
-#: i2p2www/pages/site/docs/spec/configuration.html:75
-#: i2p2www/pages/site/get-involved/index.html:48
-msgid "Applications"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:34
-msgid "Supported applications"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:35
-msgid "Bittorrent"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:38
-#: i2p2www/pages/site/docs/api/streaming.html:58
-msgid "API"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:46 i2p2www/pages/global/nav.html:77
-#: i2p2www/pages/site/docs/how/tech-intro.html:808
-msgid "Streaming library"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:47
-msgid "Ministreaming library"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:48 i2p2www/pages/global/nav.html:71
-#: i2p2www/pages/site/docs/index.html:88
-#: i2p2www/pages/site/docs/api/datagrams.html:2
-#: i2p2www/pages/site/get-involved/develop/applications.html:277
-msgid "Datagrams"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:52
-msgid "Protocols"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:54
-msgid "Protocol stack"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:59
-#: i2p2www/pages/site/docs/how/cryptography.html:394
-msgid "Transports"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:61 i2p2www/pages/site/docs/index.html:158
-msgid "Transport layer overview"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:66
-msgid "Specifications"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:68
-msgid "Blockfile"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:69
-msgid "Common structures"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:70
-msgid "Configuration files"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:72
-msgid "GeoIP files"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:78
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:230
-msgid "Tunnel creation"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:79
-msgid "Tunnel messages"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:80
-msgid "Software updates"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:83 i2p2www/pages/site/docs/index.html:139
-#: i2p2www/pages/site/docs/how/tech-intro.html:14
-#: i2p2www/pages/site/docs/how/tech-intro.html:228
-msgid "Tunnels"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:85
-msgid "Tunnel implementation"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:86
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:288
-msgid "Unidirectional tunnels"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:87
-msgid "Old implementation"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:90
-msgid "Naming and addressbook"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:94 i2p2www/pages/site/about/team.html:2
-msgid "Team"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:96
-msgid "Hall of Fame"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:97
-msgid "Academic papers and peer review"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:98
-msgid "Presentations, tutorials and articles"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:99
-msgid "Contact us"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:102
-msgid "Help"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:104
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
-msgid "FAQ"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:105
-msgid "How to browse I2P"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:106 i2p2www/pages/site/about/glossary.html:2
-msgid "Glossary"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:107
-#: i2p2www/pages/site/about/performance/index.html:2
-#: i2p2www/pages/site/docs/index.html:183
-#: i2p2www/pages/site/get-involved/todo.html:52
-#: i2p2www/pages/site/get-involved/todo.html:456
-msgid "Performance"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:108 i2p2www/pages/site/contact.html:22
-msgid "Forums"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:111
-msgid "Volunteer"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:113
-msgid "Get involved!"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:114
-msgid "Develop"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:117
-#: i2p2www/pages/site/get-involved/develop/licenses.html:2
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115
-msgid "Licenses"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:118
-msgid "Release signing keys"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:119
-msgid "Signed keys"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:120
-msgid "Developers keys"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:121 i2p2www/pages/site/docs/index.html:223
-msgid "Bug tracker"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:124
-msgid "Academic research"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:125
-msgid "Guides"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:127
-msgid "New developers"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:128
-#: i2p2www/pages/site/get-involved/guides/ides.html:2
-msgid "Using an IDE with I2P"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:129
-msgid "Developer guidelines and coding style"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:130
-#: i2p2www/pages/site/get-involved/guides/monotone.html:2
-msgid "Monotone"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:131
-msgid "New translators"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:134
-#: i2p2www/pages/site/get-involved/bounties/index.html:2
-msgid "Bounties"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:135 i2p2www/pages/meetings/index.html:2
-msgid "Meetings"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:136
-#: i2p2www/pages/site/get-involved/roadmap.html:2
-msgid "Roadmap"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:137
-msgid "Task list"
-msgstr ""
-
-#: i2p2www/pages/global/nav.html:140
-msgid "Language"
-msgstr ""
-
-#: i2p2www/pages/meetings/index.html:4
-msgid "I2P Meetings ATOM Feed"
-msgstr ""
-
-#: i2p2www/pages/meetings/index.html:7
-msgid "Logs of past I2P meetings"
-msgstr ""
-
-#: i2p2www/pages/meetings/index.html:9
-msgid "Meetings are currently on hold until a more suitable time can be chosen."
-msgstr ""
-
-#: i2p2www/pages/meetings/index.html:13
-#, python-format
-msgid ""
-"If you have something to discuss, please find the developers on IRC in "
-"#i2p-dev.\n"
-"Status updates from developers are also "
-"available."
-msgstr ""
-
-#: i2p2www/pages/meetings/show.html:2
-#, python-format
-msgid "I2P Development Meeting %(id)s"
-msgstr ""
-
-#: i2p2www/pages/meetings/show.html:10
-msgid "Full IRC Log"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:2
-msgid "Contact"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:5
-msgid ""
-"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
-" to this network is set up with new router installs.\n"
-"  We are also present on multiple standard networks like OFTC,\n"
-"  EIN and Freenode.\n"
-"  All I2P-related channels on all these network are linked to the main "
-"channels on Irc2P via relay bots."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:13
-msgid "Channel list:"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:15
-msgid "General i2p discussion"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:16
-msgid "Offtopic"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:17
-msgid "Development talk"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:18
-msgid "Help channel"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:23
-#, python-format
-msgid ""
-"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
-" place to start with inquiries, if the dev IRC channel is inactive."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:27
-msgid "Mailing lists"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:28
-msgid ""
-"I2P does have a mailing list, but it is rarely used as the current small "
-"team of developers prefer to communicate via IRC or the developer forum. "
-"This may change in future."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:33
-msgid "Subscribing"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:34
-msgid ""
-"To subscribe to a mailing list, go to the list information page (linked "
-"below) and fill out the form. I2P-internal email addresses "
-"(foobar@mail.i2p) can be used."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:38
-msgid "Unsubscribing"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:39
-msgid ""
-"To unsubscribe from a mailing list or edit your subscription options, go "
-"to the list information page (linked below) and enter your subscription "
-"email address."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:43
-msgid "Lists"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:46
-msgid "Archive"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:47
-msgid ""
-"General I2P discussion - anything that doesn't fit in a different list "
-"goes here."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:53
-msgid ""
-"You don't like mailing lists? Then this is for you. All mailing lists are"
-" available via NNTP as well."
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:58
-msgid "Group-List-mapping:"
-msgstr ""
-
-#: i2p2www/pages/site/contact.html:62
-msgid "Servers:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:2
-msgid "Frequently Asked Questions"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:4
-#: i2p2www/pages/site/docs/how/threat-model.html:121
-msgid "Index"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:7
-msgid "General"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
-msgid "What systems will I2P run on?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:10
-msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:263
-msgid "My router has very few active peers, is this OK?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:498
-msgid "What do the Active x/y numbers mean in the router console?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:225
-msgid ""
-"My active peers / known peers / participating tunnels / connections / "
-"bandwidth vary dramatically over time! Is anything wrong?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:348
-msgid "Is using an outproxy safe?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:374
-msgid "Most of the eepsites within I2P are down?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:527
-msgid "What ports does I2P use?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:17
-msgid "Why is I2P listening for connections on port 32000?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
-msgid "I think I found a bug, where can I report it?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:107
-msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:845
-msgid "I have a question!"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:22
-#: i2p2www/pages/site/docs/api/streaming.html:292
-msgid "Setup"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:232
-msgid ""
-"My router has been up for several minutes and has zero or very few "
-"connections"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:390
-msgid "Why is I2P so slow?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
-msgid ""
-"I'm missing lots of hosts in my addressbook. What are some good "
-"subscription links?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:383
-msgid "How do I set up my own eepsite?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:416
-msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:423
-msgid "How do I connect to IRC within I2P?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:281
-msgid "I can't access regular Internet sites through I2P."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:296
-msgid "I can't access https:// or ftp:// sites through I2P."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:506
-msgid "Is it possible to use I2P as a SOCKS proxy?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:489
-msgid "How do I configure my browser?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:434
-msgid ""
-"How can I access the web console from my other machines or password "
-"protect it?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:474
-msgid "How can I use applications from my other machines?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:748
-msgid "How do I reseed manually?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:124
-msgid "My router is using too much CPU?!?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:39
-msgid "Misconception"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:366
-msgid ""
-"How do I access IRC, BitTorrent, or other services on the regular "
-"Internet?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:42
-msgid ""
-"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
-"want it to be."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:188
-msgid ""
-"I am opposed to certain types of content. How do I keep from "
-"distributing, storing, or accessing them?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:45
-msgid "Errors and Their Solutions"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:784
-msgid ""
-"I'm using FreeBSD and when I start I2P I receive an error about "
-"libm.so.4!"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:48
-msgid ""
-"In wrapper.log I see an error stating Protocol family "
-"unavailable when I2P is loading"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
-#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:108
-#: i2p2www/pages/site/faq.html:125 i2p2www/pages/site/faq.html:189
-#: i2p2www/pages/site/faq.html:226 i2p2www/pages/site/faq.html:233
-#: i2p2www/pages/site/faq.html:264 i2p2www/pages/site/faq.html:273
-#: i2p2www/pages/site/faq.html:282 i2p2www/pages/site/faq.html:297
-#: i2p2www/pages/site/faq.html:349 i2p2www/pages/site/faq.html:367
-#: i2p2www/pages/site/faq.html:375 i2p2www/pages/site/faq.html:384
-#: i2p2www/pages/site/faq.html:391 i2p2www/pages/site/faq.html:417
-#: i2p2www/pages/site/faq.html:424 i2p2www/pages/site/faq.html:435
-#: i2p2www/pages/site/faq.html:475 i2p2www/pages/site/faq.html:482
-#: i2p2www/pages/site/faq.html:490 i2p2www/pages/site/faq.html:499
-#: i2p2www/pages/site/faq.html:507 i2p2www/pages/site/faq.html:528
-#: i2p2www/pages/site/faq.html:736 i2p2www/pages/site/faq.html:749
-#: i2p2www/pages/site/faq.html:785 i2p2www/pages/site/faq.html:817
-#: i2p2www/pages/site/faq.html:846 i2p2www/pages/site/get-involved/todo.html:16
-#: i2p2www/pages/site/get-involved/todo.html:28
-#: i2p2www/pages/site/get-involved/todo.html:52
-msgid "link"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:53
-#, python-format
-msgid ""
-"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
-"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
-"(or better) with 128MB of RAM (or more). A chart comparing the performance of"
-" the various JREs can be found at http://%(trac)s/wiki/java, but in "
-"short: it's at all possible, use Sun/Oracle Java or OpenJDK."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:57
-msgid ""
-"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
-"underway to bring I2P to the Android platform."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:65
-msgid "Here are some places, pick one or more."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:71
-msgid "Discuss with the developers on IRC in #i2p-dev"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:75
-msgid "Please include relevant information from the router logs and wrapper logs."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:81
-msgid ""
-"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
-"updated rarely.\n"
-"If you don't have another subscription, you may often have to use "
-"\"jump\" links which\n"
-"is annoying."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:87
-msgid ""
-"Here are some other public addressbook subscription links. You may wish "
-"to add one or two\n"
-"to your susidns "
-"subscription list.\n"
-"You don't need to add all of them, as they sync with each other "
-"periodically.\n"
-"The links using a cgi-bin application employ various strategies to "
-"minimize\n"
-"the number of duplicate addresses delivered, so they should be more "
-"efficient.\n"
-"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
-" malicious\n"
-"subscription could give you incorrect addresses. So think about whether "
-"you\n"
-"want to trust any of these.\n"
-"The operators of these services may have various policies for listing "
-"hosts.\n"
-"Presence on this list does not imply endorsement."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:109
-msgid ""
-"Jrandom was the lead developer of I2P and\n"
-"Syndie for several years.\n"
-"We do not know if or when jrandom will return.\n"
-"The *.i2p.net domains were left in a non-functioning state after a power\n"
-"outage at the hosting company."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:117
-#, python-format
-msgid ""
-"See this page for jrandom's parting message "
-"and additional information\n"
-"on the migration of *.i2p.net to this website."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:122
-msgid "I2P remains in active development."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:126
-msgid "There are many possible causes of high CPU usage. Here is a checklist:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:131
-msgid ""
-"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
-"system. You can check \n"
-"which version of java you have installed by typing java "
-"-version at a \n"
-"command/shell prompt. Performance tends to suffer with other "
-"implementations of java."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:138
-msgid ""
-"Are you running a BitTorrent client over I2P? Try reducing the number of "
-"torrents, the bandwidth limits,\n"
-"or try turning it off completely to see if that helps."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:144
-msgid ""
-"Are your bandwidth limits set too high? It is possible that too much "
-"traffic is going through your\n"
-"I2P router and it is overloaded. Try reducing the setting for share "
-"bandwidth percentage on the configuration page."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:149
-msgid ""
-"Make sure that you're running the latest version of I2P to get the "
-"benefits of increased performance and bug fixes."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:154
-msgid ""
-"Has enough memory been set aside for use by I2P? Look at the memory graph"
-" on the graphs page to see\n"
-"if the memory usage is \"pegged\"—the JVM is spending most of its "
-"time in\n"
-"garbage collection. Increase the setting "
-"wrapper.java.maxmemory in wrapper.config."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:161
-#, python-format
-msgid ""
-"Is the CPU usage simply higher than you would like, or is it pegged at "
-"100% for a long time?\n"
-"If it's pegged, this could be a bug. Look in the logs for clues."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:167
-#, python-format
-msgid ""
-"You may be using the Java-based BigInteger library instead of the native "
-"version,\n"
-"especially if you are running on a new or unusual OS or hardware "
-"(OpenSolaris, mipsel, etc.).\n"
-"See the jbigi page for instructions on\n"
-"diagnosing, building, and testing methods."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:175
-msgid ""
-"If your native jbigi library is working fine, the biggest user of\n"
-"CPU may be routing traffic for participating tunnels. This uses CPU\n"
-"because at each hop a layer of encryption must be decoded.\n"
-"You can limit participating traffic in two ways - by reducing the\n"
-"share bandwidth on\n"
-"confignet.jsp,\n"
-"or by setting router.maxParticipatingTunnels=nnn on\n"
-"configadvanced.jsp."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:190
-msgid ""
-"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
-"I2P is designed to withstand censorship, providing a means for everyone "
-"to communicate freely. \n"
-"The best way to keep your PC free of (encrypted) traffic that you dislike"
-" is to not use I2P.\n"
-"Freedom of speech has some costs.\n"
-"But let's address your question in three parts:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:199
-#, python-format
-msgid ""
-"Distribution - All traffic on I2P is encrypted in multiple layers."
-" You don't know\n"
-"a message's contents, source, or destination.\n"
-"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
-"Your only alternative is to refuse to route\n"
-"any traffic, by setting your share bandwidth or maximum "
-"participating tunnels to 0 (see above).\n"
-"It would be nice if you didn't do this, you should help the network by "
-"routing traffic for others.\n"
-"Over 95% of users route traffic for others."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:210
-msgid ""
-"Storage - I2P does not do distributed storage of content. You must"
-" be thinking of\n"
-"Freenet.\n"
-"Nobody's content is being stored on your computer by running I2P."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:217
-msgid ""
-"Access - If there are some eepsites you don't like, don't go "
-"there.\n"
-"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:227
-msgid ""
-"No. This is normal.\n"
-"All routers adjust dynamically to changing network conditions and demands."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:234
-msgid ""
-"You may need to reseed your I2P router. With recent versions of I2P you "
-"can go to http://localhost:7657/configreseed"
-" and click the Save Changes and Reseed Now button. If this "
-"method doesn't work—or you're using a very old version—you "
-"may need to reseed manually."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:237
-msgid ""
-"The reseed URL changed a few years ago. If this is your first install and"
-" you have installed\n"
-"an old (0.6.1.30 or earlier) release, or\n"
-"you have not run I2P in a long time, you must change the URL and then\n"
-"click \"Reseed\" on the console to find other routers.\n"
-"After your router is running,\n"
-"on configadvanced.jsp,"
-"\n"
-"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
-"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
-"work),\n"
-"then click \"Apply\", then click the \"reseed\" link on the left."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:248
-#, python-format
-msgid ""
-"This works if you are running 0.6.1.27 or later.\n"
-"If you are running release 0.6.1.31 or later, you probably don't need to "
-"do this.\n"
-"If you are running release 0.6.1.26 or earlier, either follow the\n"
-"manual reseed instructions below\n"
-"or install the latest release.\n"
-"Possible alternate method - add\n"
-"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
-"to wrapper.config, shutdown the router completely, then start again, then"
-" click \"reseed\".\n"
-"Let us know if this works."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:259
-#, python-format
-msgid ""
-"...but you *really* should upgrade to "
-"the latest version."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:265
-msgid ""
-"If your router has 10 or more active peers, everything is fine. Changes "
-"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
-"efficiency of the router and effectively reduced the number of active "
-"peers.\n"
-"The router should maintain connections to a few peers at all "
-"times.\n"
-"The best way to stay \"better-connected\" to the network is to share more bandwidth."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:272
-msgid ""
-"Is my router an \"exit node\" to the regular Internet? I don't want it to"
-" be."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:274
-msgid ""
-"No. Unlike Tor,\n"
-"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
-"\n"
-"Only volunteers who set up and run separate applications will relay "
-"traffic to the regular Internet.\n"
-"There are very, very few of these."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:283
-msgid ""
-"See above. There are very few HTTP \"outproxies\", they are not an "
-"inherent part of the network,\n"
-"and they may not be up.\n"
-"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
-"vanished.\n"
-"The only outproxy at the moment is false.i2p.\n"
-"To use it, edit your i2ptunnel "
-"settings for eepProxy\n"
-"and set your outproxy list to 'false.i2p' (only).\n"
-"Then stop and restart the eepProxy.\n"
-"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
-"If your primary reason to use an anonymous network is to anonymously "
-"access sites\n"
-"on the regular Internet, you should probably try Tor."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:298
-msgid ""
-"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
-"to-end.\n"
-"FTP is not supported for technical reasons."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:302
-msgid ""
-"There are no FTP \"outproxies\" to the Internet—it may not even be "
-"possible to set up one.\n"
-"Any other kind of outproxy may work if it's set up with a standard "
-"tunnel. \n"
-"If you would like to set up some type of outproxy, carefully research the"
-" potential risks.\n"
-"The I2P community may or may not be able to help with the technical "
-"aspects, feel free to ask."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:308
-msgid ""
-"As explained several times above, any existing outproxy isn't a core part"
-" of the network.\n"
-"They are services run by individuals and they may or may not\n"
-"be operational at any given time."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:313
-msgid ""
-"Update: Thanks to the work of h2ik, there is an https outproxy "
-"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
-"configured out of the box.
            \n"
-"In case the https outproxy is not available in your version of I2P, you "
-"can add it easily by doing the following:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:319
-msgid ""
-"Open i2p tunnel "
-"manager. Scroll down to the bottom."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:324
-msgid ""
-"Choose CONNECT from New Client Tunnel dropdown list, click "
-"Create"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:329
-#, python-format
-msgid ""
-"In the new page, name and describe your new https tunnel as"
-" you like.\n"
-"The Access Point is your local port for the new https proxy "
-"recommended port's 4445.\n"
-"Outproxy should be the outproxy's .i2p address which supports "
-"https. \n"
-"See this forum post of h2ik's for the "
-"address. \n"
-"Make sure Shared Client, Delay Connect, AutoStart "
-"are checked.\n"
-"Other options should be left at the defaults. Click Save. In tunnel "
-"manger, click the Start button next to your new tunnel."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:339
-msgid ""
-"In firefox, click through "
-"Tools>Options>Advanced>Network>Setting."
-"\n"
-"Untick Use this proxy for all protocol, set SSL proxy: to "
-"localhost:4445."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:344
-msgid "Done."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:350
-#, python-format
-msgid ""
-"\n"
-"This is a question that only you can answer because the correct answer "
-"depends on your behaviours, your\n"
-"threat model, and how much you trust the "
-"outproxy operator."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:354
-msgid ""
-"Like Tor, I2P does not magically encrypt the Internet.\n"
-"You are vulnerable to snooping by the outproxy operators.\n"
-"The Tor"
-" FAQ\n"
-"does a good job of explaining this."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:360
-#, python-format
-msgid ""
-"In addition, you may be vulnerable to collusion between the outproxy "
-"operator\n"
-"and operators of other I2P services, if you use the same tunnels "
-"(\"shared clients\").\n"
-"There is additional discussion about this on %(zzz)s."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:368
-msgid ""
-"Unless an outproxy has been set up for the service you want to connect "
-"to, this cannot be done.\n"
-"There are only three types of outproxies running right now: HTTP, HTTPS, "
-"and email. Note that there is not a SOCKS outproxy.\n"
-"If this type of service is required, try Tor."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:376
-#, python-format
-msgid ""
-"If you consider every eepsite that has ever been created, yes, most of "
-"them are down.\n"
-"People and eepsites come and go.\n"
-"A good way to get started in I2P is check out a list of eepsites that are"
-" currently up.\n"
-"%(perv)s tracks active eepsites."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:385
-msgid ""
-"Click on the Website link\n"
-"at the top of your router console for instructions."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:392
-msgid ""
-"Why are downloads, torrents, web browsing, and everything else so slow on"
-" I2P?\n"
-"The encryption and routing within the I2P network adds a substantial "
-"amount of overhead and limits bandwidth.\n"
-"Anonymity isn't free."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:397
-msgid ""
-"In addition, you and everybody else probably need to increase your "
-"bandwidth limits.\n"
-"Two key settings are the inbound and outbound bandwidth limiters on\n"
-"the configuration page.\n"
-"With the default settings of 32KBps you will generally get no better than"
-" 15KBps data transfer in I2PSnark.\n"
-"Increasing the settings (but keeping within your actual connection "
-"limitations)\n"
-"will increase the potential transfer rate for I2PSnark and all other "
-"applications."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:405
-msgid ""
-"Also, do you have sufficient share bandwidth configured to allow "
-"participating tunnels\n"
-"to route through your router? Believe it or not, allowing participating "
-"traffic\n"
-"keeps you well-integrated in the network and helps your own transfer "
-"speeds."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:410
-#, python-format
-msgid ""
-"I2P is a work in progress. Lots of improvements and fixes are being "
-"implemented, and\n"
-"generally speaking, running the latest release will help your "
-"performance.\n"
-"If you haven't, install the latest "
-"release."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:418
-#, python-format
-msgid ""
-"See the\n"
-"I2P Bittorrent FAQ"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:425
-msgid ""
-"\n"
-"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
-" installed (see\n"
-"the I2PTunnel "
-"configuration page),\n"
-"and is automatically started when the I2P router starts. To connect to "
-"it, tell your IRC\n"
-"client to connect to localhost 6668. XChat-like client users"
-" can create a\n"
-"new network with the server localhost/6668 (remember to tick"
-" "Bypass\n"
-"proxy server" if you have a proxy server configured)."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:436
-msgid ""
-"For security purposes, the router's admin console by default only listens"
-"\n"
-"for connections on the local interface.  However, with a little hacking,\n"
-"you can make it reachable remotely:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:444
-msgid ""
-"Open ~/.i2p/clients.config and replace
            \n"
-"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
-"with 
            \n"
-"clientApp.0.args=7657 0.0.0.0 ./webapps/"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:452
-msgid ""
-"Go to http://localhost:7657/configadvanced.jsp"
-"\n"
-"and add a new option: consolePassword=foo (or whatever "
-"password you want)"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:458
-msgid ""
-"Go to http://localhost:7657/index.jsp"
-"\n"
-"and hit \"Graceful restart\", which restarts the JVM and reloads the "
-"client applications"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:465
-msgid ""
-"After that fires up, you should now be able to reach your console "
-"remotely.\n"
-"You will be prompted for a username and password though - the username is"
-"\n"
-"\"admin\" and the password is whatever you specified in step 2 above.  "
-"Note: the\n"
-"0.0.0.0 above specifies an interface, not a network "
-"or netmask.  0.0.0.0\n"
-"means \"bind to all interfaces\", so it can be reachable on "
-"127.0.0.1:7657 as well as\n"
-"any LAN/WAN IP."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:476
-msgid ""
-"By default, the router I2CP interface (port 7654) binds to address "
-"127.0.0.1. To bind to 0.0.0.0, set the\n"
-"router advanced configuration option "
-"i2cp.tcp.bindAllInterfaces=true and restart."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:481
-msgid "Whats an \"eepsite\"?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:483
-msgid ""
-"An eepsite is a website that is hosted anonymously - you can access it by"
-"\n"
-"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
-"listens on localhost port 4444), and browsing to the site."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:491
-#, python-format
-msgid ""
-"The proxy config for different browsers is on a \n"
-"separate page with screenshots. More advanced configs with external "
-"tools\n"
-"are possible but could introduce leaks in your setup."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:500
-msgid ""
-"x is the number of peers you've sent or received a message from\n"
-"successfully in the last minute, y is the number of peers seen in the "
-"last\n"
-"hour or so."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:508
-msgid ""
-"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
-"supported.\n"
-"There is no SOCKS outproxy so it is of limited use."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:512
-msgid ""
-"In addition, many applications leak sensitive\n"
-"information that could identify you on the Internet. I2P only filters\n"
-"connection data, but if the program you intend to run sends this\n"
-"information as content, I2P has no way to protect your anonymity.  For\n"
-"example, some mail applications will send the IP address of the machine\n"
-"they are running on to a mail server. There is no way for I2P to filter\n"
-"this, thus using I2P to 'socksify' existing applications is possible, but"
-"\n"
-"extremely dangerous."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:522
-#, python-format
-msgid ""
-"If you would like more information on the socks proxy application anyway,"
-"\n"
-"there are some helpful hints on the socks page."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:529
-msgid ""
-"Okay, here's a rundown of the default ports (everything is configurable\n"
-"through various settings, of course):"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:538
-msgid ""
-"Internet-facing ports\n"
-"Note: New installs as of release 0.7.8 do not use port 8887; they select "
-"a random port\n"
-"between 9000 and 31000 when the program is run for the first time.\n"
-"The selected port is shown on the router configuration page."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:546
-msgid ""
-"Outbound UDP from the random port noted on the configuration page to "
-"arbitrary remote UDP ports, allowing replies\n"
-"    "
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:551
-msgid ""
-"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
-"    "
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:556
-msgid ""
-"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
-"arbitrary locations\n"
-"    "
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:561
-msgid ""
-"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
-"arbitrary locations
            \n"
-"Inbound TCP may be disabled on the configuration page."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:567
-msgid ""
-"Outbound UDP on port 123, allowing replies
            \n"
-"This is necessary for I2P's internal time sync (via SNTP - \n"
-"querying a random SNTP host in pool.ntp.org or another\n"
-"server you specify)"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:578
-msgid ""
-"Local I2P ports, listening only to local connections by default,\n"
-"except where noted:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:584
-msgid ""
-"1900: UPnP SSDP UDP multicast listener.\n"
-"Cannot be changed. Binds to all interfaces.\n"
-"May be disabled on confignet.jsp."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:591
-msgid ""
-"2827: BOB bridge, a higher level socket API for clients\n"
-"Disabled by default.\n"
-"May be enabled/disabled on configclients.jsp.\n"
-"May be changed in the bob.config file."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:599
-msgid ""
-"4444: HTTP proxy\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:606
-msgid ""
-"4445: HTTPS proxy\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:613
-msgid ""
-"6668: IRC proxy\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:620
-msgid ""
-"7652: UPnP HTTP TCP event listener.\n"
-"Binds to the LAN address.\n"
-"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
-"May be disabled on confignet.jsp."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:628
-msgid ""
-"7653: UPnP SSDP UDP search response listener.\n"
-"Binds to all interfaces.\n"
-"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
-"May be disabled on confignet.jsp."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:636
-msgid ""
-"7654: I2P Client Protocol port, used by client apps.\n"
-"May be changed to a different port on\n"
-"configclients.jsp"
-"\n"
-"but this is not recommended.\n"
-"May be to bind to a different interface or all interfaces, or disabled, "
-"on\n"
-"configclients.jsp."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:646
-msgid ""
-"7655: UDP for SAM bridge, a higher level socket API for clients\n"
-"Only opened when a SAM V3 client requests a UDP session.\n"
-"May be enabled/disabled on configclients.jsp.\n"
-"May be changed in the clients.config file with the SAM command line "
-"option sam.udp.port=nnnn."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:654
-msgid ""
-"7656: SAM bridge, a higher level socket API for clients\n"
-"Disabled by default for new installs as of release 0.6.5.\n"
-"May be enabled/disabled on configclients.jsp.\n"
-"May be changed in the clients.config file."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:662
-msgid ""
-"7657: Your router console\n"
-"May be disabled in the clients.config file.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces in that file."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:669
-msgid ""
-"7658: Your eepsite\n"
-"May be disabled in the clients.config file.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces in the jetty.xml file."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:676
-msgid ""
-"7659: Outgoing mail to smtp.postman.i2p\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:683
-msgid ""
-"7660: Incoming mail from pop.postman.i2p\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:690
-msgid ""
-"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
-"May be disabled or changed on the i2ptunnel page in the router "
-"console.\n"
-"May also be configured to be bound to a specific interface or all "
-"interfaces."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:697
-msgid ""
-"31000: Local connection to the wrapper control channel port.\n"
-"Outbound to 32000 only, does not listen on this port.\n"
-"Starts at 31000 and will increment until 31999 looking for a free port.\n"
-"To change, see the\n"
-"wrapper documentation.\n"
-"For more information see below."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:707
-msgid ""
-"32000: Local control channel for the service wrapper.\n"
-"To change, see the\n"
-"wrapper documentation.\n"
-"For more information see below."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:719
-msgid ""
-"The local I2P ports and the I2PTunnel ports do not need to be reachable "
-"from \n"
-"remote machines, but *should* be reachable locally.  You can also create"
-" \n"
-"additional ports for I2PTunnel instances via "
-"http://localhost:7657/i2ptunnel/ \n"
-"(and in turn, would need to get your firewall to allow you local access, "
-"but \n"
-"not remote access, unless desired)."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:727
-msgid ""
-"So, to summarize, nothing needs to be reachable by unsolicited remote "
-"peers, but\n"
-"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
-"outbound facing port, you'll"
-"\n"
-"get better performance.  You will also need to be able to send outbound "
-"UDP packets\n"
-"to arbitrary remote peers (blocking IPs randomly with something like "
-"PeerGuardian\n"
-"only hurts you - don't do it)."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:735
-msgid "Why is I2P listening on port 32000?"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:737
-msgid ""
-"The Tanuki java service wrapper that we use opens this port—bound "
-"to localhost—in order \n"
-"to communicate with software running inside the JVM. When the JVM is "
-"launched it is given a key \n"
-"so it can connect to the wrapper. After the JVM establishes its "
-"connection \n"
-"to the wrapper, the wrapper refuses any additional connections."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:743
-msgid ""
-"More information can be found in the  \n"
-"wrapper documentation."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:750
-msgid ""
-"An I2P router only needs to be seeded once, to join the network for the "
-"first time.\n"
-"Reseeding is nothing more than sending plain HTTP GET requests\n"
-"to fetch a directory listing and download multiple \"routerInfo\" files\n"
-"from a predefined reseed URL."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:757
-msgid ""
-"A typical symptom of a failed reseed is the \"Known\" indicator\n"
-"(on the left sidebar of the router console) displaying a very small value"
-"\n"
-"(often less than 5) which does not increase. This can occur, among other "
-"things,\n"
-"if your firewall limits outbound traffic, and blocked the reseed request."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:764
-msgid "To reseed an I2P router manually, do the following:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:767
-msgid "Stop your I2P router"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:770
-msgid ""
-"Open http://netdb.i2p2.de/ using a "
-"web browser"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:773
-msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:780
-msgid "Start your I2P router"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:787
-msgid ""
-"When trying to start the router using \"i2prouter start\", you may see "
-"output like the following:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:792
-msgid ""
-"\n"
-"In order to be inclusive and try to ensure that I2P will run on as many "
-"systems \n"
-"as possible, up until I2P 0.8.9 we used a java wrapper \n"
-"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
-"are missing the necessary compatibility libraries.\n"
-"These libraries may be installed by performing the following steps:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:800
-msgid ""
-"Switch to the root user with su or log in as "
-"root."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:806
-#, python-format
-msgid ""
-"If you cannot install these compatibility libraries (or do not want to), "
-"other\n"
-"possibilities would be to compile the wrapper for your\n"
-"system, starting I2P with the runplain.sh script, or you"
-" can\n"
-"replace the wrapper with one from the source tarball."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:812
-msgid ""
-"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
-"compiled on systems running FreeBSD 7.2."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:816
-msgid ""
-"In wrapper.log I see an error that states \"Protocol "
-"family unavailable\" when loading the Router Console"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:818
-msgid ""
-"Often this error will occur with any network enabled java software on "
-"some systems that are configured to use IPv6 by default. There are a few "
-"ways to solve this:"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:823
-msgid ""
-"On Linux based systems, you can echo 0 > "
-"/proc/sys/net/ipv6/bindv6only"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:825
-msgid "Look for the following lines in wrapper.config."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:829
-msgid ""
-"If the lines are there, uncomment them by removing the \"#\"s. If the "
-"lines are not there, add them without the \"#\"s."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:832
-msgid ""
-"Another option would be to remove the ::1 from "
-"~/.i2p/clients.config"
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:836
-msgid ""
-"WARNING: For any changes to wrapper.config "
-"to take effect, you must completely\n"
-"stop the router and the wrapper. Clicking Restart on your\n"
-"router console will NOT reread this file! You must\n"
-"click Shutdown, wait 11 minutes, then start I2P."
-msgstr ""
-
-#: i2p2www/pages/site/faq.html:847
-#, python-format
-msgid ""
-"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
-"the forum and we'll post it here (with\n"
-"the answer, hopefully)."
-msgstr ""
-
-#: i2p2www/pages/site/impressum.html:4
-msgid "German laws"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:2
-msgid "I2P Anonymous Network"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:4
-msgid ""
-"Anonymous peer-to-peer distributed communication layer built with open "
-"source tools and designed to run any traditional Internet service such as"
-" email, IRC or web hosting."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:7
-msgid "What does I2P do for you?"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:8
-msgid ""
-"The I2P network provides strong privacy protections for communication "
-"over the Internet. Many activities that would risk your privacy on the "
-"public Internet can be conducted anonymously inside I2P."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:9
-#, python-format
-msgid "Get I2P %(version)s"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:13
-msgid "What is I2P?"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:15
-msgid ""
-"I2P is a full darknet implementation - a network within a network, and is"
-" intended to protect against monitoring by third parties, such as hostile"
-" governments or ISPs.\n"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:18
-msgid ""
-"I2P is used by many people who care about their privacy, as well as those"
-" in high-risk situations. It is designed to protect activists, oppressed "
-"people, journalists and whistle-blowers - as well as the average person."
-"\n"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:21
-msgid ""
-"I2P runs on Java and is therefore available anywhere Java will run, "
-"including desktops, embedded systems (like the Raspberry Pi)  and Android"
-" phones.\n"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:25
-msgid "Read more…"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:30
-msgid "What can you do with I2P?"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:33
-#, python-format
-msgid ""
-"Email Integrated web mail interface, "
-"plugin for serverless email."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:38
-#, python-format
-msgid ""
-"Web browsing Anonymous "
-"websites, gateways to and from the public Internet."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:43
-#, python-format
-msgid ""
-"Blogging and forums "
-"Blogging and Syndie plugins."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:48
-#, python-format
-msgid ""
-"Website hosting Integrated "
-"anonymous web server."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:53
-#, python-format
-msgid ""
-"Real-time chat Instant "
-"messaging and IRC clients."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:58
-#, python-format
-msgid ""
-"File sharing ED2K and Gnutella"
-" clients, integrated BitTorrent client."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:63
-#, python-format
-msgid ""
-"Decentralized file "
-"storage Tahoe-LAFS distributed filesystem plugin."
-msgstr ""
-
-#: i2p2www/pages/site/index.html:68
-#, python-format
-msgid "More supported applications…"
-msgstr ""
-
-#: i2p2www/pages/site/index.html:76
-msgid "News & Updates"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:4
-msgid "Recommended Links & Resources"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:5
-#, python-format
-msgid ""
-"See also the page with\n"
-"links to presentations, videos, and tutorials about"
-" I2P."
-msgstr ""
-
-#: i2p2www/pages/site/links.html:12
-msgid "Friends of I2P"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:24
-msgid "More Projects and Documentation"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:34
-msgid "Press"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:38
-msgid "Boards, newssite, others"
-msgstr ""
-
-#: i2p2www/pages/site/links.html:42
-msgid "Very Old Stuff"
-msgstr ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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
-msgid ""
-"By default, I2P comes with two outproxies configured: "
-"false.i2p\n"
-"(an HTTP-only proxy) and outproxyng.h2ik.i2p (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
-#, python-format
-msgid ""
-"Filtering is active on these outproxies (for example, mibbit and torrent\n"
-"tracker access is blocked). Note that even though the pirate bay is "
-"blocked\n"
-"they host an official eepsite at %(tpb)s. "
-"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:101
-msgid ""
-"Tor is good application to use"
-" as an\n"
-"outproxy to the Internet."
-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:137
-#: i2p2www/pages/site/about/hall-of-fame.html:138
-#: i2p2www/pages/site/about/hall-of-fame.html:139
-#: i2p2www/pages/site/about/hall-of-fame.html:140
-#: i2p2www/pages/site/about/hall-of-fame.html:142
-#: i2p2www/pages/site/about/hall-of-fame.html:143
-#: i2p2www/pages/site/about/hall-of-fame.html:144
-#: i2p2www/pages/site/about/hall-of-fame.html:147
-#: i2p2www/pages/site/about/hall-of-fame.html:148
-#: i2p2www/pages/site/about/hall-of-fame.html:149
-#: i2p2www/pages/site/about/hall-of-fame.html:152
-#: i2p2www/pages/site/about/hall-of-fame.html:153
-#: i2p2www/pages/site/about/hall-of-fame.html:154
-#: i2p2www/pages/site/about/hall-of-fame.html:155
-#: i2p2www/pages/site/about/hall-of-fame.html:156
-#: i2p2www/pages/site/about/hall-of-fame.html:157
-#: i2p2www/pages/site/about/hall-of-fame.html:158
-#: i2p2www/pages/site/about/hall-of-fame.html:159
-#: i2p2www/pages/site/about/hall-of-fame.html:160
-#: i2p2www/pages/site/about/hall-of-fame.html:161
-#: i2p2www/pages/site/about/hall-of-fame.html:162
-#: i2p2www/pages/site/about/hall-of-fame.html:163
-#: i2p2www/pages/site/about/hall-of-fame.html:164
-#: i2p2www/pages/site/about/hall-of-fame.html:167
-#: i2p2www/pages/site/about/hall-of-fame.html:168
-#: i2p2www/pages/site/about/hall-of-fame.html:169
-#: i2p2www/pages/site/about/hall-of-fame.html:170
-#: i2p2www/pages/site/about/hall-of-fame.html:171
-#: i2p2www/pages/site/about/hall-of-fame.html:172
-#: 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: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:181
-#: i2p2www/pages/site/about/hall-of-fame.html:182
-#: 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:186
-#: i2p2www/pages/site/about/hall-of-fame.html:187
-#: 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: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: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:208
-#: i2p2www/pages/site/about/hall-of-fame.html:209
-#: i2p2www/pages/site/about/hall-of-fame.html:210
-#: i2p2www/pages/site/about/hall-of-fame.html:212
-#: i2p2www/pages/site/about/hall-of-fame.html:213
-#: 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:217
-#: i2p2www/pages/site/about/hall-of-fame.html:218
-#: i2p2www/pages/site/about/hall-of-fame.html:219
-#: 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:227
-#: i2p2www/pages/site/about/hall-of-fame.html:230
-#: i2p2www/pages/site/about/hall-of-fame.html:231
-#: 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:236
-#: i2p2www/pages/site/about/hall-of-fame.html:237
-#: i2p2www/pages/site/about/hall-of-fame.html:238
-#: i2p2www/pages/site/about/hall-of-fame.html:243
-#: 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:247
-#: 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:252
-#: 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:265
-#: 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:271
-#: 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:275
-#: i2p2www/pages/site/about/hall-of-fame.html:276
-#: i2p2www/pages/site/about/hall-of-fame.html:277
-#: i2p2www/pages/site/about/hall-of-fame.html:278
-#: 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:289
-#: 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:292
-#: i2p2www/pages/site/about/hall-of-fame.html:293
-#: i2p2www/pages/site/about/hall-of-fame.html:294
-#: i2p2www/pages/site/about/hall-of-fame.html:295
-#: i2p2www/pages/site/about/hall-of-fame.html:297
-#: i2p2www/pages/site/about/hall-of-fame.html:298
-#: i2p2www/pages/site/about/hall-of-fame.html:299
-#: i2p2www/pages/site/about/hall-of-fame.html:300
-#: 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: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:314
-#: 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:322
-#: i2p2www/pages/site/about/hall-of-fame.html:324
-#: 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:332
-#: 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: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:348
-#: i2p2www/pages/site/about/hall-of-fame.html:349
-#: i2p2www/pages/site/about/hall-of-fame.html:351
-#: i2p2www/pages/site/about/hall-of-fame.html:352
-#: 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:374
-#: 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:378
-#: i2p2www/pages/site/about/hall-of-fame.html:379
-#: 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:382
-#: i2p2www/pages/site/about/hall-of-fame.html:383
-#: 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:386
-#: 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:389
-#: i2p2www/pages/site/about/hall-of-fame.html:390
-#: i2p2www/pages/site/about/hall-of-fame.html:391
-#: i2p2www/pages/site/about/hall-of-fame.html:392
-#: i2p2www/pages/site/about/hall-of-fame.html:393
-#: i2p2www/pages/site/about/hall-of-fame.html:394
-#: i2p2www/pages/site/about/hall-of-fame.html:395
-#: i2p2www/pages/site/about/hall-of-fame.html:396
-#: i2p2www/pages/site/about/hall-of-fame.html:397
-#: i2p2www/pages/site/about/hall-of-fame.html:398
-#: i2p2www/pages/site/about/hall-of-fame.html:399
-#: 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: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: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:420
-#: 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:436
-#: 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:442
-#: i2p2www/pages/site/about/hall-of-fame.html:445
-#: 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:449
-#: 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:455
-#: i2p2www/pages/site/about/hall-of-fame.html:456
-#: i2p2www/pages/site/about/hall-of-fame.html:457
-#: i2p2www/pages/site/about/hall-of-fame.html:458
-#: 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:465
-#: i2p2www/pages/site/about/hall-of-fame.html:466
-#: i2p2www/pages/site/about/hall-of-fame.html:467
-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
-#, 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
-#: i2p2www/pages/site/get-involved/bounties/index.html:67
-msgid "Bitcoin client for I2P"
-msgstr ""
-
-#: i2p2www/pages/site/about/hall-of-fame.html:20
-#, python-format
-msgid "%(btcval)s BTC"
-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:134
-msgid "2012 donations and costs:"
-msgstr ""
-
-#: i2p2www/pages/site/about/hall-of-fame.html:262
-msgid "2011 donations and costs:"
-msgstr ""
-
-#: i2p2www/pages/site/about/hall-of-fame.html:363
-msgid "Previous to 2011 donations:"
-msgstr ""
-
-#: i2p2www/pages/site/about/intro.html:2
-msgid "Intro"
-msgstr ""
-
-#: i2p2www/pages/site/about/intro.html:5
-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 \n"
-"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:19
-#, 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:33
-#, 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:44
-#, python-format
-msgid "More details about how I2P works are available."
-msgstr ""
-
-#: i2p2www/pages/site/about/intro.html:48
-msgid "What can you do with it?"
-msgstr ""
-
-#: i2p2www/pages/site/about/intro.html:50
-#, 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:60
-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:76
-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:90
-#, 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
-#: i2p2www/pages/site/research/papers.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\n"
-"Russian translation"
-msgstr ""
-
-#: i2p2www/pages/site/about/media.html:204
-#, python-format
-msgid ""
-"zzz interviewed on the InfoSec Daily Podcast Ep. 454 "
-"(mp3)\n"
-"August 18, 2011"
-msgstr ""
-
-#: i2p2www/pages/site/about/media.html:209
-#, python-format
-msgid ""
-"I2P - Anonymity for the Masses,\n"
-"Jonathan Cox,\n"
-"November 11, 2011."
-msgstr ""
-
-#: i2p2www/pages/site/about/media.html:215
-#, 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: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:76
-#: i2p2www/pages/site/about/team.html:81 i2p2www/pages/site/about/team.html:101
-#: i2p2www/pages/site/about/team.html:138
-#: i2p2www/pages/site/about/team.html:148
-#: i2p2www/pages/site/about/team.html:153
-#: 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:206
-#: i2p2www/pages/site/about/team.html:228
-#: i2p2www/pages/site/get-involved/bounties/index.html:35
-#: i2p2www/pages/site/get-involved/bounties/index.html:42
-#: i2p2www/pages/site/get-involved/bounties/index.html:49
-#: i2p2www/pages/site/get-involved/bounties/index.html:56
-#: i2p2www/pages/site/get-involved/bounties/index.html:63
-#: i2p2www/pages/site/get-involved/bounties/index.html:84
-#: i2p2www/pages/site/get-involved/bounties/index.html:104
-msgid "vacant"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:72
-msgid "threat model / crypto expert"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:75
-msgid "User Advocate"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:77
-msgid "gather, prioritize, advocate for user needs"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:80
-msgid "Web Designer"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:82
-msgid "manage the public project website content design"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:85
-#, python-format
-msgid "Webserver admin"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:87
-msgid "manage the public project webservers"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:90
-#, python-format
-msgid "Website admin"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:92
-msgid "manage the public project website content"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:95
-msgid "News Admin"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:97
-msgid "manage router console news feed"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:100
-msgid "Director of passion"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:102
-msgid "community motivator"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:106
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-msgid "Dev"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:107
-msgid "Core Lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:109
-msgid "lead dev for the SDK and router"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:112
-#, python-format
-msgid "I2P mail lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:114
-msgid "organize and develop the i2p mail system"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:117
-#, python-format
-msgid "I2Host lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:119
-msgid "I2Host addressbook application"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:122
-#, python-format
-msgid "BOB lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:124
-msgid "Basic Open Bridge"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:127
-#, python-format
-msgid "I2P-Bote lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:129
-msgid "I2PBote plugin"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:132
-#, python-format
-msgid "Robert lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:134
-msgid "Robert BitTorrent client"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:137
-#, python-format
-msgid "I2Phex lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:139
-msgid "I2Phex Gnutella client"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:142
-#, python-format
-msgid "I2PSnark lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:144
-msgid "Maintains the integrated Bittorrent client"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:147
-#, python-format
-msgid "iMule lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:149
-msgid "eMule client over I2P"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:152
-#, python-format
-msgid "Syndie lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:154
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3
-msgid "Syndie development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:157
-msgid "Susimail lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:159
-msgid "Susimail development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:162
-msgid "Console"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:164
-msgid "Router console HTML/CSS design"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:167
-msgid "SAM"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:169
-msgid "SAM maintainer"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:172
-msgid "I2PCPP lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:174
-msgid "C++ Router"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:177
-msgid "Console Translations"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:179
-msgid "Chinese"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:183
-msgid "Dutch"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:187
-msgid "French"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:191
-msgid "German"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:195
-msgid "Russian"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:199
-msgid "Spanish"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:203
-msgid "Arabic"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:207
-msgid "Other languages"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:210
-msgid "Contributors"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:212
-msgid "fire2pe dev, console enhancements"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:216
-msgid "desktopgui, dijjer port"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:220
-msgid "Debian/Ubuntu Packager and PPA maintainer"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:224
-msgid "Routerconsole backend and UI work, website revamp, unit tests work"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:229
-msgid "Help needed on many fronts!"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:233
-msgid "Past contributors"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:235
-msgid "I2PTunnel development, ministreaming library"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:239
-msgid "Project lead, Syndie lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:243
-msgid "Project lead, Syndie lead, I2Phex, support guru"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:247
-msgid "iMule lead"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:251
-#: i2p2www/pages/site/about/team.html:255
-#: i2p2www/pages/site/about/team.html:259
-msgid "I2Phex work"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:263
-msgid "Python SAM library, attack simulations"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:267
-msgid "i2pmail development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:271
-msgid "Syndie help"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:275
-msgid "i2p mail,susimail and susidns apps"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:279
-msgid "I2Phex (port of Phex to I2P)"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:283
-msgid "addressbook,i2p-bt,syndie client"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:287
-msgid "organize and develop the i2p-bt BitTorrent port"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:291
-msgid "addressbook, i2p-bt, syndie client development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:295
-msgid "encryption and signature routines, I2PIM"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:299
-msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:303
-msgid "installer, systray, bogobot"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:307
-msgid "jbigi development, wiki migration, doc cleanup"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:311
-msgid "java debugging and client development on I2PTunnel and the router console"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:315
-msgid "SAM perl module"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:319
-msgid "i2psnark work"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:323
-msgid "java cleanup"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:327
-msgid "docs. wiki migration"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:331
-msgid "translations into French"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:335
-msgid "C port of jcpuid"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:339
-msgid "C# SAM library, pants, fortuna integration"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:343
-msgid "libSAM"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:347
-#: i2p2www/pages/site/about/team.html:351
-msgid "i2p-bt tracker development"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:355
-msgid "Console and website themes"
-msgstr ""
-
-#: i2p2www/pages/site/about/team.html:358
-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
-#: i2p2www/pages/site/docs/api/bob.html:3
-#: i2p2www/pages/site/docs/api/datagrams.html:3
-#: i2p2www/pages/site/docs/how/garlic-routing.html:3
-#: i2p2www/pages/site/docs/protocol/index.html:3
-#: i2p2www/pages/site/docs/transport/ntcp.html:3
-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
-#, python-format
-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
-#, python-format
-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 shitlist) 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: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 ""
-
-#: i2p2www/pages/site/comparison/freenet.html:2
-msgid "I2P Compared to Freenet"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/freenet.html:8
-msgid ""
-"Freenet is a fully distributed, peer to peer anonymous publishing "
-"network, offering \n"
-"secure ways to store data, as well as some approaches attempting to "
-"address the loads\n"
-"of a flash flood.  While Freenet is designed as a distributed data store,"
-" people have\n"
-"built applications on top of it to do more generic anonymous "
-"communication, such as \n"
-"static websites and message boards."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/freenet.html:16
-#, python-format
-msgid ""
-"Compared to I2P, Freenet offers some substantial benefits - it is a "
-"distributed data\n"
-"store, while I2P is not, allowing people to retrieve the content "
-"published by others \n"
-"even when the publisher is no longer online.  In addition, it should be "
-"able to \n"
-"distribute popular data fairly efficiently.  I2P itself does not and will"
-" not provide \n"
-"this functionality.  On the other hand, there is overlap for users who "
-"simply want to \n"
-"communicate with each other anonymously through websites, message boards,"
-" file sharing\n"
-"programs, etc.  There have also been some attempts to develop a "
-"distributed data \n"
-"store to run on top of I2P,\n"
-"(most recently a port of Tahoe-LAFS)\n"
-"but nothing is yet ready for general use."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/freenet.html:29
-msgid ""
-"However, even ignoring any implementations issues, there are some "
-"concerns \n"
-"about Freenet's algorithms from both a scalability and anonymity "
-"perspective, owing \n"
-"largely to Freenet's heuristic driven routing.  The interactions of "
-"various techniques \n"
-"certainly may successfully deter various attacks, and perhaps some "
-"aspects of the \n"
-"routing algorithms will provide the hoped for scalability.  "
-"Unfortunately, not much\n"
-"analysis of the algorithms involved has resulted in positive results, but"
-" there is still\n"
-"hope.  At the very least, Freenet does provide substantial anonymity "
-"against an attacker\n"
-"who does not have the resources necessary to analyze it further."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:2
-msgid "Comparing I2P to other projects"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:4
-msgid ""
-"There are a great many other applications and projects working on "
-"anonymous \n"
-"communication and I2P has been inspired by much of their efforts.  This "
-"is not \n"
-"a comprehensive list of anonymity resources - both freehaven's \n"
-"Anonymity "
-"Bibliography\n"
-"and GNUnet's related "
-"projects\n"
-"serve that purpose well.  That said, a few systems stand out for further\n"
-"comparison. The following have individual comparison pages:"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:20
-#, python-format
-msgid ""
-"The following are discussed on the other "
-"networks page:"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/index.html:32
-#, python-format
-msgid ""
-"The content of this page is subject to update, discussion and dispute, "
-"and we welcome comments and additions.\n"
-"You may contribute an analysis by entering a new ticket on Trac."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:2
-msgid "I2P Compared to Other Anonymous Networks"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:5
-msgid "The following networks are discussed on this page."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:16
-#, python-format
-msgid ""
-"Most of the following sections are fairly old, and may not be accurate.\n"
-"For an overview of available comparisons, see the\n"
-"main network comparisons page.\n"
-"You may contribute an analysis by entering a\n"
-"new ticket on %(trac)s."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:29
-#, python-format
-msgid ""
-"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
-" \n"
-"anonymizing proxies, allowing people to tunnel out through the low "
-"latency \n"
-"mix network.  Morphmix includes some very interesting collusion detection"
-" \n"
-"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
-"IP\n"
-"addresses to accomplish the same.  The two primary differences between \n"
-"these systems and I2P are related to I2P's threat model \n"
-"and their out-proxy design (as opposed to providing both sender and "
-"receiver \n"
-"anonymity).  There is source code available to both systems, but we are "
-"not aware \n"
-"of their use outside of academic environments."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:153
-msgid ""
-"\n"
-"Mixminion and Mixmaster are networks to support anonymous email against a"
-" very\n"
-"powerful adversary.\n"
-"High-latency messaging applications running on top of I2P\n"
-"(for example\n"
-"Syndie or\n"
-"I2PBote)\n"
-"may perhaps prove adequate to meet the threat\n"
-"model of those adversaries, while running in parallel along side the "
-"needs of low latency users, to provide\n"
-"a significantly larger anonymity set.\n"
-"High-latency support within the I2P router itself may or may not be added"
-" in a distant future release.\n"
-"It is too early to say if I2P will meet the needs of users requiring "
-"extreme protection for email."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:167
-msgid ""
-"As with Tor and Onion Routing, \n"
-"both Mixminion and Mixmaster take the directory based approach as well."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:177
-#, python-format
-msgid ""
-"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
-"web requests,\n"
-"and as such it has a few centralized nodes (participants in the cascade) "
-"that blend\n"
-"and mix requests from clients through the sequence of nodes (the cascade)"
-" before \n"
-"proxying out onto the web.  The scope, threat model, and security is "
-"substantially \n"
-"different from I2P, but for those who don't require significant anonymity"
-" but still\n"
-"are not satisfied with an Anonymizer-like service, JAP is worth "
-"reviewing.  One\n"
-"caution to note is that anyone under the jurisdiction of the German "
-"courts may want\n"
-"to take care, as the German Federal Bureau of Criminal Investigation "
-"(FBCI) has \n"
-"successfully mounted an \n"
-"attack \n"
-"on the network.  Even though the method of this attack was later found to"
-" be illegal \n"
-"in the German courts, the fact that the data was successfully collected "
-"is the \n"
-"concern.  Courts change their minds based upon circumstance, and this is "
-"evidence that \n"
-"if a government body or intelligence agency wanted to, they could gather "
-"the data, even \n"
-"if it may be found inadmissible in some courts later)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:199
-#, python-format
-msgid ""
-"Both of these systems work through the same basic \n"
-"antnet routing, providing some degree of\n"
-"anonymity based on the threat model of providing plausible deniability "
-"against a simple \n"
-"non-colluding adversary.  With the antnet routing, they first either do a"
-" random walk or a \n"
-"broadcast search to find some peer with the data or identity desired, and"
-" then use a feedback\n"
-"algorithm to optimize that found path.  This works well for applications "
-"that merely want to know \n"
-"what other people around them have to offer - \"How are y'all doing\" vs."
-" \"Hey Alice, how are you\" - \n"
-"you basically get a local cluster of nodes that can share files with and "
-"maintain some degree of \n"
-"anonymity (though you don't have much control over who is in that group "
-"of peers)."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:211
-msgid ""
-"However, the algorithm does not scale well at all - if the application "
-"wants to speak with a \n"
-"particular peer it ends up doing a broadcast search or random walk "
-"(though if they are lucky enough\n"
-"for that to succeed, the antnet routing should optimize that found "
-"connection).  This means that \n"
-"while these networks can work great at small scales, they are not "
-"suitable for large networks where\n"
-"someone wants to get in touch with another specific peer.  That does not "
-"mean that there is no \n"
-"value in these systems, just that their applicability is limited to "
-"situations where their \n"
-"particular issues can be addressed."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:222
-#, python-format
-msgid ""
-"This was a closed-source network targeted at Iranian users.\n"
-"Tor did a\n"
-"good writeup on what to look for in a circumvention tool.\n"
-"Suffice it to say that being closed source and publicly targeting a "
-"specific country are not good ideas.\n"
-"I2P is, of course, open source. However, that source, and our\n"
-"technical documentation, need much more review."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:231
-msgid "Paid VPN Services"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:232
-#: i2p2www/pages/site/comparison/other-networks.html:238
-#, python-format
-msgid ""
-"You may contribute an analysis by entering a\n"
-"new ticket on %(trac)s."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/other-networks.html:237
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
-msgid "Others"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:2
-msgid "I2P Compared to Tor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:8
-#, python-format
-msgid ""
-"Tor and Onion Routing are both anonymizing proxy networks, \n"
-"allowing people to tunnel out through their low latency mix \n"
-"network. The two primary differences between Tor / \n"
-"Onion-Routing and I2P are again related to differences in \n"
-"the threat model and the out-proxy design (though Tor\n"
-"supports hidden services as well).  In addition, Tor\n"
-"takes the directory-based approach - providing a \n"
-"centralized point to manage the overall 'view' of the \n"
-"network, as well as gather and report statistics, as \n"
-"opposed to I2P's distributed network \n"
-"database and peer selection."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:22
-msgid ""
-"The I2P/Tor outproxy functionality does have a few \n"
-"substantial weaknesses against certain attackers - \n"
-"once the communication leaves the mixnet, global passive\n"
-"adversaries can more easily mount traffic analysis.  In \n"
-"addition, the outproxies have access to the cleartext \n"
-"of the data transferred in both directions, and \n"
-"outproxies are prone to abuse, along with all of the \n"
-"other security issues we've come to know and love with \n"
-"normal Internet traffic."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:34
-msgid ""
-"However, many people don't need to worry about those \n"
-"situations, as they are outside their threat model.  It\n"
-"is, also, outside I2P's (formal) functional scope (if people want\n"
-"to build outproxy functionality on top of an anonymous\n"
-"communication layer, they can).  In fact, some I2P users\n"
-"currently take advantage of Tor to outproxy."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:48
-msgid "Comparison of Tor and I2P Terminology"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:49
-msgid ""
-"While Tor and I2P are similar in many ways, much of the terminology is "
-"different."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:54
-msgid "Cell"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:54
-#: i2p2www/pages/site/docs/protocol/i2np.html:91
-msgid "Message"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:55
-msgid "Client"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:55
-msgid "Router or Client"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:56
-msgid "Circuit"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:56
-msgid "Tunnel"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:57
-msgid "Directory"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:57
-msgid "NetDb"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:58
-msgid "Directory Server"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:58
-msgid "Floodfill Router"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:59
-msgid "Entry Guards"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:59
-msgid "Fast Peers"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:60
-msgid "Entry Node"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:60
-msgid "Inproxy"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:61
-msgid "Exit Node"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:61
-msgid "Outproxy"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:62
-msgid "Hidden Service"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:62
-msgid "Eepsite or Destination"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:63
-msgid "Hidden Service Descriptor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:63
-msgid "LeaseSet"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:64
-msgid "Introduction point"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:64
-#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
-#: i2p2www/pages/site/docs/tunnels/implementation.html:140
-msgid "Inbound Gateway"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:65
-msgid "Node"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:65
-#: i2p2www/pages/site/comparison/tor.html:67
-#: i2p2www/pages/site/comparison/tor.html:70
-#: i2p2www/pages/site/docs/spec/configuration.html:70
-msgid "Router"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:66
-msgid "Onion Proxy"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:66
-msgid "I2PTunnel Client (more or less)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:67
-msgid "Relay"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:68
-msgid "Rendezvous Point"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:68
-msgid "somewhat like Inbound Gateway + Outbound Endpoint"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:69
-msgid "Router Descriptor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:69
-msgid "RouterInfo"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:70
-msgid "Server"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:73
-msgid "Benefits of Tor over I2P"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:76
-msgid ""
-"Much bigger user base; much more visibility in the academic and hacker "
-"communities; benefits from\n"
-"formal studies of anonymity, resistance, and performance;\n"
-"has a non-anonymous, visible, university-based leader"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:82
-msgid "Has already solved some scaling issues I2P has yet to address"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:83
-msgid "Has significant funding"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:84
-msgid "Has more developers, including several that are funded"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:86
-msgid ""
-"More resistant to state-level blocking due to TLS transport layer and "
-"bridges\n"
-"(I2P has proposals for \"full restricted routes\" but these are not yet "
-"implemented)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:91
-msgid "Big enough that it has had to adapt to blocking and DOS attempts"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:92
-msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:94
-msgid ""
-"Better documentation, has formal papers and specifications,\n"
-"better website, many more translations"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:99
-msgid "More efficient with memory usage"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:100
-msgid "Tor client nodes have very low bandwidth overhead"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:102
-msgid ""
-"Centralized control reduces the complexity at each\n"
-"node and can efficiently address Sybil attacks"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:108
-msgid ""
-"A core of high capacity nodes provides higher\n"
-"throughput and lower latency"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:113
-msgid "C, not Java (ewww)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:116
-msgid "Benefits of I2P over Tor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:118
-msgid ""
-"Designed and optimized for hidden services, which are much faster than in"
-" Tor"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:119
-msgid "Fully distributed and self organizing"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:121
-msgid ""
-"Peers are selected by continuously profiling and ranking performance,\n"
-"rather than trusting claimed capacity"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:127
-msgid ""
-"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
-"rather than hardcoded"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:132
-msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:133
-msgid "Peer-to-peer friendly"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:134
-msgid "Packet switched instead of circuit switched"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:137
-msgid ""
-"implicit transparent load balancing of messages \n"
-"across multiple peers, rather than a single path"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:143
-msgid ""
-"resilience vs. failures by running multiple \n"
-"tunnels in parallel, plus rotating tunnels"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:149
-msgid ""
-"scale each client's connections at O(1) instead \n"
-"of O(N) (Alice has e.g. 2 inbound tunnels that are \n"
-"used by all of the peers Alice is talking with, \n"
-"rather than a circuit for each)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:159
-msgid ""
-"Unidirectional tunnels instead of bidirectional\n"
-"circuits, doubling the number of nodes a peer has to\n"
-"compromise to get the same information."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:166
-msgid ""
-"Protection against detecting client activity, even\n"
-"when an attacker is participating in the tunnel, as\n"
-"tunnels are used for more than simply passing end \n"
-"to end messages (e.g. netDb, tunnel management, \n"
-"tunnel testing)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:175
-msgid ""
-"Tunnels in I2P are short lived, decreasing the number\n"
-"of samples that an attacker can use to mount an \n"
-"active attack with, unlike circuits in Tor, which are\n"
-"typically long lived."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:183
-msgid ""
-"I2P APIs are designed specifically for anonymity and\n"
-"security, while SOCKS is designed for functionality."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:188
-msgid "Essentially all peers participate in routing for others"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:190
-msgid ""
-"The bandwidth overhead of being a full peer is low, \n"
-"while in Tor, while client nodes don't require much\n"
-"bandwidth, they don't fully participate in the mixnet."
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:196
-msgid "Integrated automatic update mechanism"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:197
-msgid "Both TCP and UDP transports"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:198
-msgid "Java, not C (ewww)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:201
-msgid "Other potential benefits of I2P but not yet implemented"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:202
-msgid "...and may never be implemented, so don't count on them!"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:205
-msgid ""
-"Defense vs. message count analysis by garlic wrapping \n"
-"multiple messages"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:211
-msgid ""
-"Defense vs. long term intersection by adding delays \n"
-"at various hops (where the delays are not discernible\n"
-"by other hops)"
-msgstr ""
-
-#: i2p2www/pages/site/comparison/tor.html:218
-msgid ""
-"Various mixing strategies at the tunnel level (e.g.\n"
-"create a tunnel that will handle 500 messages / minute,\n"
-"where the endpoint will inject dummy messages if there\n"
-"are insufficient messages, etc)"
-msgstr ""
-
 #: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:25
 msgid "Index to Technical Documentation"
-msgstr ""
+msgstr "Указатель для Технической Документации"
 
 #: i2p2www/pages/site/docs/index.html:3 i2p2www/pages/site/docs/ports.html:3
 #: i2p2www/pages/site/docs/spec/datagrams.html:3
-#: i2p2www/pages/site/docs/spec/geoip.html:3
-#: i2p2www/pages/site/docs/spec/updates.html:3
-#: i2p2www/pages/site/docs/transport/ssu.html:3
-#: i2p2www/pages/site/get-involved/develop/applications.html:3
 msgid "May 2013"
-msgstr ""
+msgstr "Май 2013"
 
 #: i2p2www/pages/site/docs/index.html:6
 msgid "How does I2P work"
-msgstr ""
+msgstr "Как работает I2P"
 
 #: i2p2www/pages/site/docs/index.html:8
 msgid "Following is an index to the technical documentation for I2P."
-msgstr ""
+msgstr "Далее приведен указатель для технической документации по I2P."
 
 #: i2p2www/pages/site/docs/index.html:12
 msgid ""
@@ -6293,6 +46,11 @@ msgid ""
 "The interface between applications and the router is the I2CP (I2P "
 "Control Protocol) API."
 msgstr ""
+"Указатель упорядочен от высших до низших уровней.\n"
+"Верхние уровни для \"клиентов\" или приложений;\n"
+"нижние уровни для внутренней части маршрутизатора.\n"
+"Интерфейсом между приложениями и маршрутизатором служит I2CP (I2P Control"
+" Protocol) API."
 
 #: i2p2www/pages/site/docs/index.html:19
 #, python-format
@@ -6300,8 +58,7 @@ msgid ""
 "The I2P Project is committed to maintaining accurate, current "
 "documentation.\n"
 "If you find any inaccuracies in the documents linked below, please\n"
-"enter a ticket identifying the "
-"problem."
+"enter a ticket identifying the problem."
 msgstr ""
 
 #: i2p2www/pages/site/docs/index.html:27 i2p2www/pages/site/docs/naming.html:7
@@ -6318,35 +75,32 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/updates.html:6
 #: i2p2www/pages/site/docs/tunnels/implementation.html:67
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:6
-#: i2p2www/pages/site/misc/jbigi.html:6
 msgid "Overview"
-msgstr ""
+msgstr "Обзор"
 
 #: i2p2www/pages/site/docs/index.html:29
 msgid "Technical Introduction"
-msgstr ""
+msgstr "Техническое Вступление"
 
 #: i2p2www/pages/site/docs/index.html:30
 msgid "A Less-Technical Introduction"
-msgstr ""
+msgstr "Менее Техническое Вступление"
 
 #: i2p2www/pages/site/docs/index.html:31
 msgid "Threat model and analysis"
-msgstr ""
+msgstr "Модель угроз и анализ"
 
 #: i2p2www/pages/site/docs/index.html:32
 msgid "Comparisons to other anonymous networks"
-msgstr ""
+msgstr "Сравнение с другими анонимными сетями"
 
 #: i2p2www/pages/site/docs/index.html:33
 msgid "Protocol stack chart"
-msgstr ""
+msgstr "Схема стека протокола"
 
 #: i2p2www/pages/site/docs/index.html:34
-#: i2p2www/pages/site/research/papers.html:2
-#: i2p2www/pages/site/research/papers.html:4
 msgid "Papers on I2P"
-msgstr ""
+msgstr "Статьи о I2P"
 
 #: i2p2www/pages/site/docs/index.html:35
 #, python-format
@@ -6354,100 +108,111 @@ msgid ""
 "Invisible Internet Project (I2P) Project Overview"
 " August 28, 2003 (pdf)"
 msgstr ""
+"Обзор Проекта Invisible Internet Project (I2P) "
+"Август 28, 2003 (pdf)"
 
 #: i2p2www/pages/site/docs/index.html:38
 msgid "Application-Layer Topics"
-msgstr ""
+msgstr "Темы Уровня Приложений"
 
 #: i2p2www/pages/site/docs/index.html:41 i2p2www/pages/site/docs/naming.html:2
 msgid "Naming and Addressbook"
-msgstr ""
+msgstr "Именование и Адресная Книга"
 
 #: i2p2www/pages/site/docs/index.html:42
 msgid "Plugins Overview"
-msgstr ""
+msgstr "Обзор Плагинов"
 
 #: i2p2www/pages/site/docs/index.html:43
 msgid "Plugin Specification"
-msgstr ""
+msgstr "Спецификация Плагина"
 
 #: i2p2www/pages/site/docs/index.html:44
 msgid "Router software updates"
-msgstr ""
+msgstr "Обновление ПО маршрутизатора"
 
 #: i2p2www/pages/site/docs/index.html:45
 #: i2p2www/pages/site/docs/applications/bittorrent.html:2
 msgid "Bittorrent over I2P"
-msgstr ""
+msgstr "Bittorrent через I2P"
 
 #: i2p2www/pages/site/docs/index.html:46
 msgid "I2PControl Plugin API"
-msgstr ""
+msgstr "I2PControl Plugin API"
 
 #: i2p2www/pages/site/docs/index.html:47
 msgid "hostsdb.blockfile Format"
-msgstr ""
+msgstr "Формат hostsdb.blockfile "
 
 #: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:185
 msgid "Configuration File Format"
-msgstr ""
+msgstr "Формат Файла Конфигурации"
 
 #: i2p2www/pages/site/docs/index.html:51
 msgid "Application Layer API and Protocols"
-msgstr ""
+msgstr "API и Протоколы Уровня Приложений"
 
 #: i2p2www/pages/site/docs/index.html:52
 msgid ""
 "High-level, easy-to-use APIs for applications written in any language to "
 "send and receive data."
 msgstr ""
+"Высокоуровневые, доступные API для приложений, написанных на любом языке,"
+" для отправки и получения данных."
 
 #: i2p2www/pages/site/docs/index.html:54
 msgid "Application Development Overview and Guide"
-msgstr ""
+msgstr "Обзор и Руководство по Разработке Приложений"
 
 #: i2p2www/pages/site/docs/index.html:72
 msgid "SAM Protocol"
-msgstr ""
+msgstr "Протокол SAM"
 
 #: i2p2www/pages/site/docs/index.html:74
 msgid "SAMv2 Protocol"
-msgstr ""
+msgstr "Протокол SAMv2"
 
 #: i2p2www/pages/site/docs/index.html:76
 msgid "SAMv3 Protocol"
-msgstr ""
+msgstr "Протокол SAMv3"
 
 #: i2p2www/pages/site/docs/index.html:78
 msgid "BOB Protocol"
-msgstr ""
+msgstr "Протокол BOB"
 
 #: i2p2www/pages/site/docs/index.html:81
 msgid "End-to-End Transport API and Protocols"
-msgstr ""
+msgstr "API и Протоколы Транспорта точка-точка"
 
 #: i2p2www/pages/site/docs/index.html:82
 msgid ""
 "The end-to-end protocols used by clients for reliable and unreliable "
 "communication."
 msgstr ""
+"Протоколы из-конца-в-конец используются клиентами для надежного и "
+"ненадежного соединения."
 
 #: i2p2www/pages/site/docs/index.html:84
 #: i2p2www/pages/site/docs/api/streaming.html:2
 msgid "Streaming Library"
-msgstr ""
+msgstr "Потоковая Библиотека"
 
 #: i2p2www/pages/site/docs/index.html:86
 msgid "Streaming Javadoc"
-msgstr ""
+msgstr "Javadoc на Потоки"
+
+#: i2p2www/pages/site/docs/index.html:88
+#: i2p2www/pages/site/docs/api/datagrams.html:2
+msgid "Datagrams"
+msgstr "Дейтаграммы"
 
 #: i2p2www/pages/site/docs/index.html:90
 msgid "Datagram Javadoc"
-msgstr ""
+msgstr "Javadoc по Дейтаграммам"
 
 #: i2p2www/pages/site/docs/index.html:93
 msgid "Client-to-Router Interface API and Protocol"
-msgstr ""
+msgstr "API и Протокол Интерфейса Клиент-Маршрутизатор"
 
 #: i2p2www/pages/site/docs/index.html:94
 msgid ""
@@ -6455,222 +220,242 @@ msgid ""
 "traffic to a router.\n"
 "Traditionally used only by Java applications and higher-level APIs."
 msgstr ""
+"Низкоуровневый API используется для клиентов (приложений) для отправка и "
+"получения трафика с маршрутизатора.\n"
+"Традиционно используется только Java приложениями и высокоуровневыми API."
 
 #: i2p2www/pages/site/docs/index.html:99
 msgid "I2CP - I2P Control Protocol / API overview"
-msgstr ""
+msgstr "Обзор I2CP - I2P Control Protocol / API"
 
 #: i2p2www/pages/site/docs/index.html:101
 msgid "I2CP Specification"
-msgstr ""
+msgstr "Спецификация I2CP"
 
 #: i2p2www/pages/site/docs/index.html:103
 msgid "I2CP API Javadoc"
-msgstr ""
+msgstr "Javadoc на I2CP API"
 
 #: i2p2www/pages/site/docs/index.html:105
 #: i2p2www/pages/site/docs/index.html:134
 msgid "Common data structures specification"
-msgstr ""
+msgstr "Спецификация основных структур данных"
 
 #: i2p2www/pages/site/docs/index.html:107
 #: i2p2www/pages/site/docs/index.html:136
 msgid "Data Structures Javadoc"
-msgstr ""
+msgstr "Javadoc по Структурам Данных"
 
 #: i2p2www/pages/site/docs/index.html:110
 msgid "End-to-End Encryption"
-msgstr ""
+msgstr "Шифрование из-конца-в-конец"
 
 #: i2p2www/pages/site/docs/index.html:111
 msgid "How client messages are end-to-end encrypted by the router."
-msgstr ""
+msgstr "Как сообщения клиентов из-конца-в-конец шифруются маршрутизатором"
 
 #: i2p2www/pages/site/docs/index.html:113
 msgid "ElGamal/AES+SessionTag encryption"
-msgstr ""
+msgstr "Шифрование ElGamal/AES+SessionTag"
 
 #: i2p2www/pages/site/docs/index.html:114
 #: i2p2www/pages/site/docs/index.html:147
 msgid "ElGamal and AES cryptography details"
-msgstr ""
+msgstr "Подробности криптографии ElGamal и AES"
 
 #: i2p2www/pages/site/docs/index.html:117
 #: i2p2www/pages/site/docs/how/tech-intro.html:15
 #: i2p2www/pages/site/docs/how/tech-intro.html:329
 msgid "Network Database"
-msgstr ""
+msgstr "Сетевая База Данных"
 
 #: i2p2www/pages/site/docs/index.html:118
 msgid ""
 "Distributed storage and retrieval of information about routers and "
 "clients."
 msgstr ""
+"Распределенное хранилище и получение информации о маршрутизаторах и "
+"клиентах."
 
 #: i2p2www/pages/site/docs/index.html:120
 msgid "Network database overview, details, and threat analysis"
-msgstr ""
+msgstr "Обзор сетевой базы данных, подробности и анализ угроз."
 
 #: i2p2www/pages/site/docs/index.html:121
 msgid "Cryptographic hashes"
-msgstr ""
+msgstr "Криптографические хеши"
 
 #: i2p2www/pages/site/docs/index.html:122
 msgid "Cryptographic signatures"
-msgstr ""
+msgstr "Криптографические подписи"
 
 #: i2p2www/pages/site/docs/index.html:125
 msgid "Router Message Protocol"
-msgstr ""
+msgstr "Протокол Сообщений Маршрутизатора"
 
 #: i2p2www/pages/site/docs/index.html:126
 msgid ""
 "I2P is a message-oriented router. The messages sent between routers are "
 "defined by the I2NP protocol."
 msgstr ""
+"I2P - это маршрутизатор, ориентированный на сообщения. Сообщения "
+"пересылаются между маршрутизаторами и описываются протоколом I2NP."
 
 #: i2p2www/pages/site/docs/index.html:128
 msgid "I2NP - I2P Network Protocol Overview"
-msgstr ""
+msgstr "I2NP - Обзор I2P Network Protocol"
 
 #: i2p2www/pages/site/docs/index.html:130
 msgid "I2NP Specification"
-msgstr ""
+msgstr "Спецификация I2NP"
 
 #: i2p2www/pages/site/docs/index.html:132
 msgid "I2NP Javadoc"
-msgstr ""
+msgstr "Javadoc на I2NP"
+
+#: i2p2www/pages/site/docs/index.html:139
+#: i2p2www/pages/site/docs/how/tech-intro.html:14
+#: i2p2www/pages/site/docs/how/tech-intro.html:228
+msgid "Tunnels"
+msgstr "Туннели"
 
 #: i2p2www/pages/site/docs/index.html:140
 msgid ""
 "Selecting peers, requesting tunnels through those peers, and encrypting "
 "and routing messages through these tunnels."
 msgstr ""
+"Выбор узлов, запрос туннелей через эти узлы, шифрование и маршрутизация "
+"сообщений через эти туннели."
 
 #: i2p2www/pages/site/docs/index.html:142
 msgid "Peer profiling and selection"
-msgstr ""
+msgstr "Профилирование и выбор узлов"
 
 #: i2p2www/pages/site/docs/index.html:143
 msgid "Tunnel routing overview"
-msgstr ""
+msgstr "Обзор туннельной маршрутизации"
 
 #: i2p2www/pages/site/docs/index.html:144
 msgid "Garlic routing and \"garlic\" terminology"
-msgstr ""
+msgstr "Чесночная маршрутизация и \"чесночная\" терминология"
 
 #: i2p2www/pages/site/docs/index.html:145
 msgid "Tunnel building and encryption"
-msgstr ""
+msgstr "Постройка и шифрование туннелей"
 
 #: i2p2www/pages/site/docs/index.html:146
 msgid "ElGamal/AES"
-msgstr ""
+msgstr "ElGamal/AES"
 
 #: i2p2www/pages/site/docs/index.html:146
 msgid "for build request encryption"
-msgstr ""
+msgstr "для шифрования запроса на построение"
 
 #: i2p2www/pages/site/docs/index.html:148
 msgid "Tunnel building specification"
-msgstr ""
+msgstr "Спецификация построения туннеля"
 
 #: i2p2www/pages/site/docs/index.html:149
 msgid "Low-level tunnel message specification"
-msgstr ""
+msgstr "Спецификация низкоуровневых туннельных сообщений"
 
 #: i2p2www/pages/site/docs/index.html:150
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:2
 msgid "Unidirectional Tunnels"
-msgstr ""
+msgstr "Однонаправленные Туннели"
 
 #: i2p2www/pages/site/docs/index.html:151
 #: i2p2www/pages/site/docs/how/peer-selection.html:299
 msgid "Peer Profiling and Selection in the I2P Anonymous Network"
-msgstr ""
+msgstr "Выбор и профилирование узла в Анонимной Сети I2P"
 
 #: i2p2www/pages/site/docs/index.html:152
 msgid "2009 paper (pdf), not current but still generally accurate"
-msgstr ""
+msgstr "Статья 2009 года (pdf), устаревшие, но в цело все еще точные"
 
 #: i2p2www/pages/site/docs/index.html:155
 msgid "Transport Layer"
-msgstr ""
+msgstr "Транспортный Уровень"
 
 #: i2p2www/pages/site/docs/index.html:156
 msgid "The protocols for direct (point-to-point) router to router communication."
-msgstr ""
+msgstr "Протоколы для прямой (точка-точка) связи маршрутизатор-маршрутизатор."
+
+#: i2p2www/pages/site/docs/index.html:158
+msgid "Transport layer overview"
+msgstr "Обзор Транспортного Уровня"
 
 #: i2p2www/pages/site/docs/index.html:160
 msgid "TCP-based transport overview and specification"
-msgstr ""
+msgstr "Обзор и спецификация транспорта на основе TCP"
 
 #: i2p2www/pages/site/docs/index.html:162
 msgid "UDP-based transport overview"
-msgstr ""
+msgstr "Обзор транспорта на основе UDP"
 
 #: i2p2www/pages/site/docs/index.html:164
 msgid "SSU specification"
-msgstr ""
+msgstr "Спецификация SSU"
 
 #: i2p2www/pages/site/docs/index.html:166
 msgid "NTCP transport encryption"
-msgstr ""
+msgstr "Шифрование транспорта NTCP"
 
 #: i2p2www/pages/site/docs/index.html:168
 msgid "SSU transport encryption"
-msgstr ""
+msgstr "Шифрование транспорта SSU"
 
 #: i2p2www/pages/site/docs/index.html:170
 msgid "Transport Javadoc"
-msgstr ""
+msgstr "Javadoc на транспорт"
 
 #: i2p2www/pages/site/docs/index.html:172
 msgid "NTCP Javadoc"
-msgstr ""
+msgstr "Javadoc на NTCP"
 
 #: i2p2www/pages/site/docs/index.html:174
 msgid "SSU Javadoc"
-msgstr ""
+msgstr "Javadoc на SSU"
 
 #: i2p2www/pages/site/docs/index.html:177
 msgid "Other Router Topics"
-msgstr ""
+msgstr "Другие Темы о Маршрутизаторе"
 
 #: i2p2www/pages/site/docs/index.html:179
 msgid "Native BigInteger Library"
-msgstr ""
+msgstr "Нативная Библиотека BigInteger"
 
 #: i2p2www/pages/site/docs/index.html:181
 msgid "Time synchronization and NTP"
-msgstr ""
+msgstr "Синхронизация времени и NTP"
+
+#: i2p2www/pages/site/docs/index.html:183
+msgid "Performance"
+msgstr "Производительноть"
 
 #: i2p2www/pages/site/docs/index.html:190
 msgid "Developer's Guides and Resources"
-msgstr ""
+msgstr "Источники и Руководства Разработчика"
 
 #: i2p2www/pages/site/docs/index.html:192
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
 msgid "New Developer's Guide"
-msgstr ""
+msgstr "Руководство для Нового Разработчика"
 
 #: i2p2www/pages/site/docs/index.html:194
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
 msgid "New Translator's Guide"
-msgstr ""
+msgstr "Руководство для Нового Переводчика"
 
 #: i2p2www/pages/site/docs/index.html:196
-#: i2p2www/pages/site/get-involved/guides/monotone.html:4
 msgid "Monotone Guide"
-msgstr ""
+msgstr "Руководство по Monotone"
 
 #: i2p2www/pages/site/docs/index.html:198
 msgid "Developer Guidelines"
-msgstr ""
+msgstr "Общие Указания по Разработке"
 
 #: i2p2www/pages/site/docs/index.html:200
 msgid "Javadocs on the standard internet:"
-msgstr ""
+msgstr "Javadocs в обычном интернет:"
 
 #: i2p2www/pages/site/docs/index.html:201
 #: i2p2www/pages/site/docs/index.html:205
@@ -6678,7 +463,7 @@ msgstr ""
 #: i2p2www/pages/site/docs/index.html:207
 #, python-format
 msgid "Server %(num)s"
-msgstr ""
+msgstr "Сервер %(num)s"
 
 #: i2p2www/pages/site/docs/index.html:202
 #: i2p2www/pages/site/docs/index.html:211
@@ -6686,73 +471,86 @@ msgid ""
 "Note: always verify that javadocs are current by checking the release "
 "number."
 msgstr ""
+"Примечание: всегда убеждайтесь в том, что все javadoc актуальны, проверяя"
+" номер релиза."
 
 #: i2p2www/pages/site/docs/index.html:204
 msgid "Javadocs inside I2P:"
-msgstr ""
+msgstr "Javadocs внутри I2P:"
 
 #: i2p2www/pages/site/docs/index.html:213
 msgid "Ports used by I2P"
-msgstr ""
+msgstr "Порты, используемые I2P:"
 
 #: i2p2www/pages/site/docs/index.html:215
 msgid "Automatic updates to development builds inside I2P"
-msgstr ""
+msgstr "Автоматическое обновление до тестовых сборок внутри I2P"
 
 #: i2p2www/pages/site/docs/index.html:217
 msgid "Updating the wrapper manually"
-msgstr ""
+msgstr "Ручное обновление wrapper"
 
 #: i2p2www/pages/site/docs/index.html:219
 msgid "User forum"
-msgstr ""
+msgstr "Форум пользователей"
 
 #: i2p2www/pages/site/docs/index.html:221
 msgid "Developer forum inside I2P"
-msgstr ""
+msgstr "Форму разработчиков внутри I2P"
+
+#: i2p2www/pages/site/docs/index.html:223
+msgid "Bug tracker"
+msgstr "Bug tracker"
 
 #: i2p2www/pages/site/docs/index.html:225
 msgid "Viewmtn inside I2P"
-msgstr ""
+msgstr "Viewmtn внутри I2P"
 
 #: i2p2www/pages/site/docs/index.html:227
 msgid "I2P Source exported to GitHub"
-msgstr ""
+msgstr "I2P Source экспортированный в GitHub"
 
 #: i2p2www/pages/site/docs/index.html:229
 msgid "I2P Source Git Repo inside I2P"
-msgstr ""
+msgstr "I2P Source Git Repo внутри I2P"
 
 #: i2p2www/pages/site/docs/index.html:231
 msgid "Source translation at Transifex"
-msgstr ""
+msgstr "Перевод исходников и Transifex"
 
 #: i2p2www/pages/site/docs/index.html:233
 msgid "Roadmap wiki"
-msgstr ""
+msgstr "Roadmap wiki"
 
 #: i2p2www/pages/site/docs/index.html:235
 msgid "Old roadmap"
-msgstr ""
+msgstr "Старый roadmap"
 
 #: i2p2www/pages/site/docs/index.html:235
 #: i2p2www/pages/site/docs/index.html:237
 msgid "not current"
-msgstr ""
+msgstr "устаревшее"
 
 #: i2p2www/pages/site/docs/index.html:237
-#: i2p2www/pages/site/get-involved/todo.html:2
 msgid "To Do List"
-msgstr ""
+msgstr "Список To Do"
 
 #: i2p2www/pages/site/docs/naming.html:3
+#: i2p2www/pages/site/docs/api/streaming.html:3
 #: i2p2www/pages/site/docs/how/cryptography.html:3
-msgid "March 2012"
+#: i2p2www/pages/site/docs/protocol/i2cp.html:3
+#: i2p2www/pages/site/docs/spec/common-structures.html:3
+#: i2p2www/pages/site/docs/spec/geoip.html:3
+#: i2p2www/pages/site/docs/spec/streaming.html:3
+#: i2p2www/pages/site/docs/transport/index.html:3
+#: i2p2www/pages/site/docs/transport/ntcp.html:3
+#: i2p2www/pages/site/docs/transport/ssu.html:3
+msgid "December 2013"
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:6
 msgid "Naming in I2P"
-msgstr ""
+msgstr "Именование в I2P"
 
 #: i2p2www/pages/site/docs/naming.html:9
 msgid ""
@@ -6762,6 +560,12 @@ msgid ""
 "I2P also supports Base32 hostnames similar to "
 "Tor's .onion addresses."
 msgstr ""
+"I2P поставляется с общей библиотекой именования, основное ее применение \n"
+"рассчитано на отображение локальных имен на пункты назначения, также "
+"поставляется \n"
+"дополнительное приложение addressbook. \n"
+"Также I2P поддерживает Base32 hostnames, похожие "
+"на адреса .onion Tor'а."
 
 #: i2p2www/pages/site/docs/naming.html:16
 msgid ""
@@ -6786,6 +590,24 @@ msgid ""
 "emulating\n"
 "traditional DNS."
 msgstr ""
+"\"Адресная книга\" - это сеть доверия, представляющая собой \n"
+"безопасную, распределенную, удобочитаемую систему имен, \n"
+"в которой взамен глобальной  уникальности имен гарантируется \n"
+"только локальная уникальность. Не смотря на то что все сообщения в I2P "
+"криптографически адресуются \n"
+"по их пункту назначения, у разных людей могут быть записи в локальной "
+"адресной книге для \n"
+"\"Alice\", указывающие на разные пункты назначения. Также люди могу "
+"узнавать о новых именах, \n"
+"импортируя опубликованные адресные книги узлов, перечисленных в их сети "
+"доверия, \n"
+"добавляя новые записи предоставленные третьей стороной, или (если кто-то "
+"организует \n"
+"серию опубликованных адресных книг, используя систему регистрации первый "
+"пришел первый \n"
+"обслужен) люди могут использовать эти адресные книги в качестве серверов "
+"имен, эмулирующих \n"
+"традиционные DNS."
 
 #: i2p2www/pages/site/docs/naming.html:30
 #, python-format
@@ -6796,16 +618,21 @@ msgid ""
 " discussion\n"
 "page."
 msgstr ""
+"Примечание: Обоснование системы именования I2P, общие доводы против нее \n"
+"и возможные альтернативы вы можете увидеть на странице \n"
+"обсуждения именования"
 
 #: i2p2www/pages/site/docs/naming.html:37
 msgid "Naming System Components"
-msgstr ""
+msgstr "Компоненты Системы Имен"
 
 #: i2p2www/pages/site/docs/naming.html:39
 msgid ""
 "There is no central naming authority in I2P.\n"
 "All hostnames are local."
 msgstr ""
+"Не существует централизованной системы авторизации имен в I2P.\n"
+"Все имена узлов являются локальными."
 
 #: i2p2www/pages/site/docs/naming.html:44
 msgid ""
@@ -6814,12 +641,16 @@ msgid ""
 "the I2P distribution.\n"
 "The components are:"
 msgstr ""
+"Система имен довольно проста и большей частью представлена \n"
+"внешними, по отношению к маршрутизатору, приложениями, но поставляющимися"
+" с \n"
+"дистрибутивом I2P.\n"
+"Эти компоненты:"
 
 #: i2p2www/pages/site/docs/naming.html:52
 msgid ""
-"The client application which does local lookups "
-"in hosts.txt\n"
-"and also takes care of the Base32 hostnames."
+"The local naming service which does lookups\n"
+"and also handles Base32 hostnames."
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:56
@@ -6828,18 +659,25 @@ msgid ""
 "lookups and points\n"
 "the user to remote jump services to assist with failed lookups."
 msgstr ""
+"HTTP proxy, которое запрашивает поиск у "
+"маршрутизатора, и направляет\n"
+"пользователя в службы удаленных переходов в случае ошибок поиска."
 
 #: i2p2www/pages/site/docs/naming.html:60
 msgid ""
 "HTTP host-add forms which allow users to "
 "add hosts to their local hosts.txt"
 msgstr ""
+"HTTP формы добавления узлов, позволяющие "
+"пользователям добавлять узлы в их локальный hosts.txt"
 
 #: i2p2www/pages/site/docs/naming.html:63
 msgid ""
 "HTTP jump services which provide their own"
 " lookups and redirection."
 msgstr ""
+"HTTP службы переходов, предоставляющие "
+"собственный поиск и перенаправление."
 
 #: i2p2www/pages/site/docs/naming.html:66
 msgid ""
@@ -6847,6 +685,9 @@ msgid ""
 "external\n"
 "host lists, retrieved via HTTP, with the local list."
 msgstr ""
+"Приложение адресная книга, выполняющая "
+"слияние внешних\n"
+"списков узлов, полученных по HTTP, с локальным списком."
 
 #: i2p2www/pages/site/docs/naming.html:70
 msgid ""
@@ -6854,9 +695,12 @@ msgid ""
 "front-end\n"
 "for addressbook configuration and viewing of the local host lists."
 msgstr ""
+"Приложение SusiDNS, являющееся простым веб "
+"интерфейсом \n"
+"для настройки адресной книги и просмотра локального списка узлов."
 
 #: i2p2www/pages/site/docs/naming.html:77
-msgid "Naming Files and Lookups"
+msgid "Naming Services"
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:79
@@ -6872,42 +716,128 @@ msgid ""
 "One possible use of certificates is for proof of work.)"
 msgstr ""
+"Все пункты назначения в I2P - это ключи по 516-байт (или больше). \n"
+"(Если быть более точным, то это публичный ключ 256-байт плюс ключ подписи"
+" 128-байт \n"
+"плюс нулевой сертификат, длина которого в виде Base64 составляет 516 "
+"байт. \n"
+"Сертификаты сейчас не "
+"используются, \n"
+"если будут, то длина ключа будет больше. \n"
+"Сертификаты можно использовать для подтверждения работы.)"
 
 #: i2p2www/pages/site/docs/naming.html:88
 msgid ""
 "If an application (i2ptunnel or the HTTP proxy) wishes to access\n"
 "a destination by name, the router does a very simple local lookup\n"
-"to resolve that name.\n"
-"The client application (technically, the client side of I2CP in the I2P "
-"API)\n"
-"does a linear search through three local files, in order, to\n"
-"look up host names and convert them to a 516-byte destination key:"
+"to resolve that name."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:94
+msgid "Hosts.txt Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:96
+msgid ""
+"The hosts.txt Naming Service does a simple linear search through\n"
+"text files. This naming service was the default until\n"
+"release 0.8.8 when it was replaced by the Blockfile Naming Service.\n"
+"The hosts.txt format had become too slow after the file grew to thousands"
+" of entries."
 msgstr ""
 
 #: i2p2www/pages/site/docs/naming.html:103
+#, python-format
+msgid ""
+"It does a linear search through three local files, in order, to\n"
+"look up host names and convert them to a 516-byte destination key.\n"
+"Each file is in a simple configuration file"
+" format, with hostname=base64, one per line.\n"
+"The files are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:115
+msgid "Blockfile Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:117
+msgid ""
+"The Blockfile Naming Service stores multiple \"addressbooks\" in a single"
+"\n"
+"database file named hostsdb.blockfile.\n"
+"This Naming Service is the default since release 0.8.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:123
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is specified on the Blockfile page.\n"
+"It provides fast Destination lookup in a compact format. While the "
+"blockfile overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry to implement "
+"advanced addressbook features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:135
+msgid ""
+"On creation, the naming service imports entries from the three files used"
+" by the hosts.txt Naming Service.\n"
+"The blockfile mimics the previous implementation by maintaining three "
+"maps that\n"
+"are searched in-order, named privatehosts.txt, userhosts.txt, and "
+"hosts.txt.\n"
+"It also maintains a reverse-lookup map to implement rapid reverse lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:142
+msgid "Other Naming Service Facilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:144
+#, python-format
 msgid ""
 "The lookup is case-insensitive.\n"
 "The first match is used, and conflicts are not detected.\n"
-"There is no enforcement of naming rules in lookups."
+"There is no enforcement of naming rules in lookups.\n"
+"Lookups are cached for a few minutes.\n"
+"Base 32 resolution is described below.\n"
+"For a full description of the Naming Service API see the\n"
+"Naming Service Javadocs.\n"
+"This API was significantly expanded in release 0.8.7 to provide\n"
+"adds and removes, storage of arbitrary properties with the hostname,\n"
+"and other features."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:109
+#: i2p2www/pages/site/docs/naming.html:157
+msgid "Alternatives and Experimental Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:159
 #, python-format
 msgid ""
-"Lookups are cached for a few minutes.\n"
-"There is an experimental facility for real-time lookups (a la DNS) over "
-"the network within the router,\n"
-"although it is not enabled by default\n"
-"(see \"EepGet\" under Alternatives on the discussion"
-" page)."
+"The naming service is specified with the configuration property "
+"i2p.naming.impl=class.\n"
+"Other implementations are possible. For example,\n"
+"there is an experimental facility for real-time lookups (a la DNS) over "
+"the network within the router.\n"
+"For more information see the alternatives on the discussion"
+" page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:116
-msgid "HTTP Proxy"
-msgstr ""
-
-#: i2p2www/pages/site/docs/naming.html:118
+#: i2p2www/pages/site/docs/naming.html:166
 msgid ""
 "The HTTP proxy does a lookup via the router for all hostnames ending in "
 "'.i2p'.\n"
@@ -6915,24 +845,42 @@ msgid ""
 "Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-"
 "Top Level Domain '.i2p'."
 msgstr ""
+"HTTP прокси выполняет поиск через маршрутизатор для всех имен узлов, "
+"заканчивающихся на '.i2p'. \n"
+"Либо перенаправляет запрос на настроенный внешний HTTP прокси. \n"
+"Т.о., на практике, все имена узлов HTTP (eepsite) должны заканчиваться на"
+" псевдо Домен Верхнего Уровня '.i2p'."
 
-#: i2p2www/pages/site/docs/naming.html:124
+#: i2p2www/pages/site/docs/naming.html:172
+#, python-format
+msgid ""
+"We have applied to reserve the .i2p TLD\n"
+"following the procedures specified in RFC "
+"6761."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:178
 msgid ""
 "If the router fails to resolve the hostname, the HTTP proxy returns\n"
 "an error page to the user with links to several \"jump\" services.\n"
 "See below for details."
 msgstr ""
+"Если маршрутизатор не может разрешить имя узла, то HTTP прокси возвращает"
+" \n"
+"пользователю страницу с ошибкой и ссылками на несколько служб "
+"\"переходов\". \n"
+"Подробнее смотри ниже."
 
-#: i2p2www/pages/site/docs/naming.html:130
+#: i2p2www/pages/site/docs/naming.html:184
 #: i2p2www/pages/site/docs/spec/configuration.html:77
 msgid "Addressbook"
-msgstr ""
+msgstr "Адресная книга"
 
-#: i2p2www/pages/site/docs/naming.html:131
+#: i2p2www/pages/site/docs/naming.html:185
 msgid "Incoming Subscriptions and Merging"
-msgstr ""
+msgstr "Входящие Подписки и Слияние"
 
-#: i2p2www/pages/site/docs/naming.html:133
+#: i2p2www/pages/site/docs/naming.html:187
 msgid ""
 "The addressbook application periodically\n"
 "retrieves other users' hosts.txt files and merges\n"
@@ -6940,8 +888,13 @@ msgid ""
 "Naming conflicts are resolved on a first-come first-served\n"
 "basis."
 msgstr ""
+"Приложение адресной книги периодически \n"
+"запрашивает файлы hosts.txt других пользователей и, после нескольких \n"
+"проверок, производит их слияние с локальным hosts.txt. \n"
+"Конфликты имен разрешаются по принципу первый пришел - \n"
+"первый обслужен."
 
-#: i2p2www/pages/site/docs/naming.html:141
+#: i2p2www/pages/site/docs/naming.html:195
 msgid ""
 "Subscribing to another user's hosts.txt file involves\n"
 "giving them a certain amount of trust.\n"
@@ -6949,8 +902,13 @@ msgid ""
 "by quickly entering in their own key for a new site before\n"
 "passing the new host/key entry to you."
 msgstr ""
+"Подписка на файл hosts.txt другого пользователя означает, \n"
+"что мы ему доверяем в этой части отношений.\n"
+"Вы не хотите чтобы он, к примеру, 'взломал' новый сайт, \n"
+"быстро введя свой ключ для нового сайта до того как \n"
+"передать новую пару узел/ключ вам."
 
-#: i2p2www/pages/site/docs/naming.html:149
+#: i2p2www/pages/site/docs/naming.html:203
 msgid ""
 "For this reason, the only subscription configured by\n"
 "default is http://www.i2p2.i2p/hosts.txt,\n"
@@ -6960,24 +918,34 @@ msgid ""
 "local addressbook application (via subscriptions.txt or SusiDNS)."
 msgstr ""
+"По этой причине единственная подписка, настроенная \n"
+"по умолчанию - это http://www.i2p2.i2p/hosts.txt, \n"
+"она содержит копию hosts.txt, включенного \n"
+"в релиз I2P. \n"
+"Пользователи должны настроить дополнительные подписки в своем \n"
+"локальном приложении адресной книги (в subscriptions.txt или SusiDNS)."
 
-#: i2p2www/pages/site/docs/naming.html:158
+#: i2p2www/pages/site/docs/naming.html:212
 msgid "Some other public addressbook subscription links:"
-msgstr ""
+msgstr "Ссылки на некоторые другие подписки публичных адресных книг:"
 
-#: i2p2www/pages/site/docs/naming.html:165
+#: i2p2www/pages/site/docs/naming.html:219
 msgid ""
 "The operators of these services may have various policies for listing "
 "hosts.\n"
 "Presence on this list does not imply endorsement."
 msgstr ""
+"У операторов этих служб могут быть различные политики для просмотра "
+"списка узлов. \n"
+"В соответствии с этим, список может быть не ободрен."
 
-#: i2p2www/pages/site/docs/naming.html:170
-#: i2p2www/pages/site/docs/naming.html:182
+#: i2p2www/pages/site/docs/naming.html:224
+#: i2p2www/pages/site/docs/naming.html:236
 msgid "Naming Rules"
-msgstr ""
+msgstr "Правила Именования"
 
-#: i2p2www/pages/site/docs/naming.html:171
+#: i2p2www/pages/site/docs/naming.html:225
 msgid ""
 "While there are hopefully not any technical limitations within I2P on "
 "host names,\n"
@@ -6990,82 +958,104 @@ msgid ""
 "Any hostnames violating these rules may not be propagated\n"
 "to other routers."
 msgstr ""
+"К счастью, нет никаких технических ограничений на имена узлов в I2P, но \n"
+"адресная книга накладывает некоторые ограничения на имена узлов, \n"
+"импортированные из подписок. \n"
+"Это делается для соблюдения основных правил именования, совместимости с "
+"браузерами и \n"
+"с целью безопасности.\n"
+"Эти правила в сущности такие же, как описанные в Разделе 3.2.2 RFC2396. \n"
+"Любые имена узлов, нарушающие эти правила, не должны распространятся \n"
+"на другие маршрутизаторы."
 
-#: i2p2www/pages/site/docs/naming.html:186
+#: i2p2www/pages/site/docs/naming.html:240
 msgid "Names are converted to lower case on import."
-msgstr ""
+msgstr "При импорте имена приводятся к нижнему регистру."
 
-#: i2p2www/pages/site/docs/naming.html:190
+#: i2p2www/pages/site/docs/naming.html:244
 msgid ""
 "Names are checked for conflict with existing names in the existing "
 "userhosts.txt and hosts.txt\n"
 "(but not privatehosts.txt) after conversion to lower case."
 msgstr ""
+"После приведения к нижнему регистру имена проверяются на конфликты с "
+"имеющимися \n"
+"именами в userhosts.txt и hosts.txt (но не в privatehosts.txt)."
 
-#: i2p2www/pages/site/docs/naming.html:195
+#: i2p2www/pages/site/docs/naming.html:249
 msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case."
 msgstr ""
+"После приведения к нижнему регистру должны содержать только [a-z] [0-9] "
+"'.' и '-'."
 
-#: i2p2www/pages/site/docs/naming.html:199
+#: i2p2www/pages/site/docs/naming.html:253
 msgid "Must not start with '.' or '-'."
-msgstr ""
+msgstr "Не должны начинаться с '.' или '-'."
 
-#: i2p2www/pages/site/docs/naming.html:203
+#: i2p2www/pages/site/docs/naming.html:257
 msgid "Must end with '.i2p'."
-msgstr ""
+msgstr "Должны оканчиваться на '.i2p'."
 
-#: i2p2www/pages/site/docs/naming.html:207
+#: i2p2www/pages/site/docs/naming.html:261
 msgid "67 characters maximum, including the '.i2p'."
-msgstr ""
+msgstr "Максимум 67 символов, включая '.i2p'."
 
-#: i2p2www/pages/site/docs/naming.html:211
+#: i2p2www/pages/site/docs/naming.html:265
 msgid "Must not contain '..'."
-msgstr ""
+msgstr "Не должны содержать '..'."
 
-#: i2p2www/pages/site/docs/naming.html:215
+#: i2p2www/pages/site/docs/naming.html:269
 msgid "Must not contain '.-' or '-.' (as of 0.6.1.33)."
-msgstr ""
+msgstr "Не должны содержать '.-' или '-.' (как в 0.6.1.33)."
 
-#: i2p2www/pages/site/docs/naming.html:219
+#: i2p2www/pages/site/docs/naming.html:273
 msgid "Must not contain '--' except in 'xn--' for IDN."
+msgstr "Не должны содержать '--', исключение -  'xn--' для IDN."
+
+#: i2p2www/pages/site/docs/naming.html:277
+msgid ""
+"Base32 hostnames (*.b32.i2p) are reserved for base 32 use and so are not "
+"allowed to be imported."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:223
-msgid "Base32 hostnames (*.b32.i2p) are not allowed."
-msgstr ""
-
-#: i2p2www/pages/site/docs/naming.html:227
+#: i2p2www/pages/site/docs/naming.html:281
 msgid ""
 "Certain hostnames reserved for project use are not allowed\n"
 "(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
 "*.console.i2p, and others)"
 msgstr ""
+"Определенные имена узлов, зарезервированые для использования проектом, не"
+" допускаются \n"
+"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
+"*.console.i2p, и другие)"
 
-#: i2p2www/pages/site/docs/naming.html:232
+#: i2p2www/pages/site/docs/naming.html:286
 msgid "Keys are checked for base64 validity."
-msgstr ""
+msgstr "Ключи проверяются на соответствие base64."
 
-#: i2p2www/pages/site/docs/naming.html:236
+#: i2p2www/pages/site/docs/naming.html:290
 msgid ""
 "Keys are checked for conflict with existing keys in hosts.txt (but not "
 "privatehosts.txt)."
 msgstr ""
+"Ключи проверяются на конфликты с существующими ключами в hosts.txt (но не"
+" в privatehosts.txt)."
 
-#: i2p2www/pages/site/docs/naming.html:240
+#: i2p2www/pages/site/docs/naming.html:294
 msgid "Minimum key length 516 bytes."
-msgstr ""
+msgstr "Минимальный размер ключа 516 байт."
 
-#: i2p2www/pages/site/docs/naming.html:244
+#: i2p2www/pages/site/docs/naming.html:298
 msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)."
-msgstr ""
+msgstr "Максимальный размер ключа 616 байт (для нужд сертификатов до 100 байт)."
 
-#: i2p2www/pages/site/docs/naming.html:249
+#: i2p2www/pages/site/docs/naming.html:303
 msgid ""
-"Any name received via subscription that passes all the checks is added to"
-" the local hosts.txt."
+"Any name received via subscription that passes all the checks is added "
+"via the local naming service."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:253
+#: i2p2www/pages/site/docs/naming.html:307
 msgid ""
 "Note that the '.' symbols in a host name are of no significance,\n"
 "and do not denote any actual naming or trust hierarchy.\n"
@@ -7076,8 +1066,17 @@ msgid ""
 "and the desirability and feasibility of these methods,\n"
 "are topics for future discussion."
 msgstr ""
+"Учтите, что символ '.' в имени узла не имеет особого смысла, \n"
+"И не говорит о фактической иерархии имен или доверия. \n"
+"Если имя 'host.i2p' уже существует, ничто не мешает \n"
+"кому-нибудь добавить имя 'a.host.i2p' в свой hosts.txt, \n"
+"и это имя может быть импортировано в другие адресные книги. \n"
+"Методы запрета заведения субдоменов не \"владельцами\" домена "
+"(сертификата?), \n"
+"целесообразность и осуществимость этих методов это \n"
+"предмет для будущих обсуждений."
 
-#: i2p2www/pages/site/docs/naming.html:264
+#: i2p2www/pages/site/docs/naming.html:318
 msgid ""
 "International Domain Names (IDN) also work in i2p (using punycode 'xn--' "
 "form).\n"
@@ -7085,8 +1084,13 @@ msgid ""
 "bar,\n"
 "add 'network.IDN.whitelist.i2p (boolean) = true' in about:config."
 msgstr ""
+"Также в I2P работают интернационализованные доменные имена (IDN) "
+"(используя форму punycode 'xn--').\n"
+"Чтобы  IDN имена домена .i2p корректно отображались в адресной строке "
+"Firefox,\n"
+"добавьте 'network.IDN.whitelist.i2p (boolean) = true' в about:config."
 
-#: i2p2www/pages/site/docs/naming.html:270
+#: i2p2www/pages/site/docs/naming.html:324
 msgid ""
 "As the addressbook application does not use privatehosts.txt at all, in "
 "practice\n"
@@ -7094,12 +1098,17 @@ msgid ""
 "aliases or\n"
 "\"pet names\" for sites already in hosts.txt."
 msgstr ""
+"Поскольку приложение адресной книги совсем не использует "
+"privatehosts.txt, то на практике \n"
+"этот файл - единственно верное место, куда стоит поместить личные "
+"синонимы или \n"
+"\"клички\" для сайтов, которые уже есть в hosts.txt."
 
-#: i2p2www/pages/site/docs/naming.html:276
+#: i2p2www/pages/site/docs/naming.html:330
 msgid "Outgoing Subscriptions"
-msgstr ""
+msgstr "Исходящие Подписки"
 
-#: i2p2www/pages/site/docs/naming.html:277
+#: i2p2www/pages/site/docs/naming.html:331
 msgid ""
 "Addressbook will publish the merged hosts.txt to a location\n"
 "(traditionally hosts.txt in the local eepsite's home directory) to be "
@@ -7107,8 +1116,13 @@ msgid ""
 "for their subscriptions.\n"
 "This step is optional and is disabled by default."
 msgstr ""
+"Адресная книга публикует объединенный hosts.txt с местоположении \n"
+"(традиционно это hosts.txt в домашней директории локального eepsite), "
+"доступном другим \n"
+"по их подпискам. \n"
+"Этот шаг необязателен и по умолчанию отключен."
 
-#: i2p2www/pages/site/docs/naming.html:285
+#: i2p2www/pages/site/docs/naming.html:339
 msgid ""
 "The addressbook application, together with eepget, saves the Etag and/or "
 "Last-Modified\n"
@@ -7116,14 +1130,22 @@ msgid ""
 "This greatly reduces the bandwidth required, as the web server will\n"
 "return a '304 Not Modified' on the next fetch if nothing has changed."
 msgstr ""
+"Приложение адресной книги, совместно с eepget, сохраняет Etag и/или "
+"информацию о \n"
+"последнем изменении, полученную веб сервером по подписке. \n"
+"Это существенно снижает требования к полосе пропускания, т.к. веб сервер"
+" \n"
+"вернет '304 Not Modified' при следующем получении, если изменений не было."
 
-#: i2p2www/pages/site/docs/naming.html:292
+#: i2p2www/pages/site/docs/naming.html:346
 msgid ""
 "However the entire hosts.txt is downloaded if it has changed.\n"
 "See below for discussion on this issue."
 msgstr ""
+"Тем не менее, содержимое hosts.txt загружается, если он был изменен. \n"
+"Обсуждение этой темы смотри ниже."
 
-#: i2p2www/pages/site/docs/naming.html:297
+#: i2p2www/pages/site/docs/naming.html:351
 msgid ""
 "Hosts serving a static hosts.txt or an equivalent CGI application\n"
 "are strongly encouraged to deliver\n"
@@ -7133,12 +1155,19 @@ msgid ""
 "This will dramatically reduce the network bandwidth, and\n"
 "reduce chances of corruption."
 msgstr ""
+"Узлу, обслуживающему статичный hosts.txt, или эквивалентному приложению "
+"CGI \n"
+"настоятельно рекомендуется отправлять \n"
+"заголовок Content-Length, либо Etag или заголовок Last-Modified. \n"
+"Убедитесь также, что сервер по необходимости выдает '304 Not Modified'. \n"
+"Это существенно уменьшить пропускную способность сети, и \n"
+"уменьшит вероятность повреждения."
 
-#: i2p2www/pages/site/docs/naming.html:306
+#: i2p2www/pages/site/docs/naming.html:360
 msgid "Host Add Services"
-msgstr ""
+msgstr "Службы Добавления Узла"
 
-#: i2p2www/pages/site/docs/naming.html:307
+#: i2p2www/pages/site/docs/naming.html:361
 msgid ""
 "A host add service is a simple CGI application that takes a hostname and "
 "a Base64 key as parameters\n"
@@ -7146,64 +1175,75 @@ msgid ""
 "If other routers subscribe to that hosts.txt, the new hostname/key\n"
 "will be propagated through the network."
 msgstr ""
+"Служба добавления узла это простое приложение CGI, которое принимает имя "
+"узла и Base64 ключ в качестве параметров, \n"
+"и добавляет их в локальный hosts.txt. \n"
+"Если другие маршрутизаторы подписаны на этот hosts.txt, то новая пара имя"
+" узла/ключ \n"
+"будет передана по сети."
 
-#: i2p2www/pages/site/docs/naming.html:314
+#: i2p2www/pages/site/docs/naming.html:368
 msgid ""
 "It is recommended that host add services impose, at a minimum, the "
 "restrictions imposed by the addressbook application listed above.\n"
 "Host add services may impose additional restrictions on hostnames and "
 "keys, for example:"
 msgstr ""
+"На службу добавления узла, как минимум, рекомендуется наложить "
+"ограничения, совпадающие с ограничениями \n"
+"приложения адресной книги, описанными выше. \n"
+"На службу добавления узла могут быть наложены дополнительные ограничения "
+"на имя узла и ключ, например:"
 
-#: i2p2www/pages/site/docs/naming.html:319
+#: i2p2www/pages/site/docs/naming.html:373
 msgid "A limit on number of 'subdomains'."
-msgstr ""
+msgstr "Ограничение количества 'поддоменов'."
 
-#: i2p2www/pages/site/docs/naming.html:323
+#: i2p2www/pages/site/docs/naming.html:377
 msgid "Authorization for 'subdomains' through various methods."
-msgstr ""
+msgstr "Различные методы авторизации для 'поддоменов'."
 
-#: i2p2www/pages/site/docs/naming.html:327
+#: i2p2www/pages/site/docs/naming.html:381
 msgid "Hashcash or signed certificates."
-msgstr ""
+msgstr "Hashcash или подписанные сертификаты."
 
-#: i2p2www/pages/site/docs/naming.html:331
+#: i2p2www/pages/site/docs/naming.html:385
 msgid "Editorial review of host names and/or content."
-msgstr ""
+msgstr "Экспертная оценка имен узлов и/или содержимого."
 
-#: i2p2www/pages/site/docs/naming.html:335
+#: i2p2www/pages/site/docs/naming.html:389
 msgid "Categorization of hosts by content."
-msgstr ""
+msgstr "Категоризация узлов по содержимому."
 
-#: i2p2www/pages/site/docs/naming.html:339
+#: i2p2www/pages/site/docs/naming.html:393
 msgid "Reservation or rejection of certain host names."
-msgstr ""
+msgstr "Резервирование или исключение определенных имен узлов."
 
-#: i2p2www/pages/site/docs/naming.html:343
+#: i2p2www/pages/site/docs/naming.html:397
 msgid "Restrictions on the number of names registered in a given time period."
-msgstr ""
+msgstr "Ограничение количества имен регистрируемых за определенный период времени."
 
-#: i2p2www/pages/site/docs/naming.html:347
+#: i2p2www/pages/site/docs/naming.html:401
 msgid "Delays between registration and publication."
-msgstr ""
+msgstr "Задержка между регистрацией и публикацией."
 
-#: i2p2www/pages/site/docs/naming.html:351
+#: i2p2www/pages/site/docs/naming.html:405
 msgid "Requirement that the host be up for verification."
-msgstr ""
+msgstr "Необходимость доступности узла для его верификации."
 
-#: i2p2www/pages/site/docs/naming.html:355
+#: i2p2www/pages/site/docs/naming.html:409
 msgid "Expiration and/or revocation."
-msgstr ""
+msgstr "Истечение срока и/или аннулирование."
 
-#: i2p2www/pages/site/docs/naming.html:359
+#: i2p2www/pages/site/docs/naming.html:413
 msgid "IDN spoof rejection."
-msgstr ""
+msgstr "Предотвращение IDN-спуфинга."
 
-#: i2p2www/pages/site/docs/naming.html:364
+#: i2p2www/pages/site/docs/naming.html:418
 msgid "Jump Services"
-msgstr ""
+msgstr "Службы перехода"
 
-#: i2p2www/pages/site/docs/naming.html:365
+#: i2p2www/pages/site/docs/naming.html:419
 msgid ""
 "A jump service is a simple CGI application that takes a hostname as a "
 "parameter\n"
@@ -7215,41 +1255,64 @@ msgid ""
 "In addition, the proxy will cache that key so the\n"
 "address helper is not necessary until restart."
 msgstr ""
+"Служба перехода это простое CGI приложение, которое получает имя узла в "
+"качестве параметра, \n"
+"и возвращает перенаправление 301 на правильный URL с добавлением строки \n"
+"?i2paddresshelper=key. \n"
+"HTTP прокси интерпретирует добавленную строку и \n"
+"использует этот ключ как актуальный пункт назначения. \n"
+"Кроме того, прокси кеширует этот ключ, так что \n"
+"address helper не нужен до перезапуска."
 
-#: i2p2www/pages/site/docs/naming.html:375
+#: i2p2www/pages/site/docs/naming.html:429
 msgid ""
 "Note that, like with subscriptions, using a jump service\n"
 "implies a certain amount of trust, as a jump service could maliciously\n"
 "redirect a user to an incorrect destination."
 msgstr ""
+"Учтите, что как и с подписками, использование службы перехода \n"
+"требует части доверия, так как служба перехода может злонамеренно \n"
+"перенаправить пользователя в некорректный пункт назначения."
 
-#: i2p2www/pages/site/docs/naming.html:381
+#: i2p2www/pages/site/docs/naming.html:435
 msgid ""
 "To provide the best service, a jump service should be subscribed to\n"
 "several hosts.txt providers so that its local host list is current."
 msgstr ""
+"Для предоставления лучшего уровня сервиса служба перехода должна быть "
+"подписана на \n"
+"несколько провайдеров hosts.txt, т.о. локальный список узлов будет "
+"актуальным."
 
-#: i2p2www/pages/site/docs/naming.html:387
+#: i2p2www/pages/site/docs/naming.html:441
 msgid ""
 "SusiDNS is simply a web interface front-end to configuring addressbook "
 "subscriptions\n"
 "and accessing the four addressbook files.\n"
 "All the real work is done by the 'addressbook' application."
 msgstr ""
+"SusiDNS это просто веб-интерфейс для настройки подписок адресной книги\n"
+"и для доступа к четырем ее файлам. \n"
+"Вся настоящая работа выполняется приложением 'адресная книга'."
 
-#: i2p2www/pages/site/docs/naming.html:393
+#: i2p2www/pages/site/docs/naming.html:447
 msgid ""
 "Currently, there is little enforcement of addressbook naming rules within"
 " SusiDNS,\n"
 "so a user may enter hostnames locally that would be rejected by\n"
 "the addressbook subscription rules."
 msgstr ""
+"На данный момент в SusiDNS реализовано мало правил ограничения именования"
+" адресной книги, \n"
+"так что пользователь может локально ввести имя узла, которое будет "
+"отвергнуто \n"
+"в соответствии с правилами подписки адресной книги."
 
-#: i2p2www/pages/site/docs/naming.html:399
+#: i2p2www/pages/site/docs/naming.html:453
 msgid "Base32 Names"
-msgstr ""
+msgstr "Base32 Имена"
 
-#: i2p2www/pages/site/docs/naming.html:400
+#: i2p2www/pages/site/docs/naming.html:454
 msgid ""
 "I2P supports Base32 hostnames similar to Tor's .onion addresses.\n"
 "Base32 addresses are much shorter and easier to handle than the\n"
@@ -7257,13 +1320,24 @@ msgid ""
 "Example: "
 "ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p"
 msgstr ""
+"I2P поддерживает Base32 имена узлов по аналогии с .onion адресами Tor. \n"
+"Base32 адреса гораздо короче и их проще обрабатывать, чем \n"
+"полные 516-символьные Base64 пункты назначения или addresshelper-ы. \n"
+"Пример: "
+"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p"
 
-#: i2p2www/pages/site/docs/naming.html:407
+#: i2p2www/pages/site/docs/naming.html:461
+#, python-format
 msgid ""
 "In Tor, the address is 16 characters (80 bits), or half of the SHA-1 "
 "hash.\n"
 "I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n"
 "The form is {52 chars}.b32.i2p.\n"
+"Tor has recently published a\n"
+"proposal\n"
+"to convert to an identical format of {52 chars}.onion for their hidden "
+"services.\n"
 "Base32 is implemented in the naming service, which queries the\n"
 "router over I2CP to lookup the LeaseSet to get the full Destination.\n"
 "Base32 lookups will only be successful when the Destination is up and "
@@ -7274,7 +1348,7 @@ msgid ""
 "longer than a local address book lookup."
 msgstr ""
 
-#: i2p2www/pages/site/docs/naming.html:419
+#: i2p2www/pages/site/docs/naming.html:476
 msgid ""
 "Base32 addresses can be used in most places where hostnames or full "
 "destinations\n"
@@ -7282,24 +1356,38 @@ msgid ""
 "name does not immediately resolve. I2PTunnel will fail, for example, if\n"
 "the name does not resolve to a destination."
 msgstr ""
+"Base32 адреса могут быть использованы в большинстве случаев, где "
+"используются имена узлов \n"
+"или полные пункты назначения, тем не менее есть несколько исключений, "
+"когда это может вызвать ошибку, если \n"
+"имя не может быть преобразовано в адрес. Например, в I2PTunnel возникнет "
+"ошибка, если \n"
+"имя не разрешается в пункт назначения."
+
+#: i2p2www/pages/site/docs/plugins.html:2
+#: i2p2www/pages/site/docs/spec/configuration.html:65
+msgid "Plugins"
+msgstr "Плагины"
 
 #: i2p2www/pages/site/docs/plugins.html:3
 msgid "June 2012"
-msgstr ""
+msgstr "Июни 2012"
 
 #: i2p2www/pages/site/docs/plugins.html:6
 msgid "I2P Plugins"
-msgstr ""
+msgstr "Плагины I2P"
 
 #: i2p2www/pages/site/docs/plugins.html:8
 msgid "General Information"
-msgstr ""
+msgstr "Основная информация"
 
 #: i2p2www/pages/site/docs/plugins.html:9
 msgid ""
 "I2P includes a plugin architecture\n"
 "to support easy development and installation of additional software."
 msgstr ""
+"В I2P имеется архитектура плагинов \n"
+"для поддержки легкой разработки и установки дополнительного ПО."
 
 #: i2p2www/pages/site/docs/plugins.html:14
 msgid ""
@@ -7307,20 +1395,26 @@ msgid ""
 "IRC\n"
 "clients, distributed file storage, wikis, and more."
 msgstr ""
+"Уже сейчас доступны плагины с поддержкой распределенной электронной "
+"почты, блогов, \n"
+"клиентов IRC, распределенного хранилища файлов, wiki и др."
 
 #: i2p2www/pages/site/docs/plugins.html:19
 msgid "Benefits to i2p users and app developers:"
-msgstr ""
+msgstr "Преимущества для пользователей I2P и разработчиков ПО:"
 
 #: i2p2www/pages/site/docs/plugins.html:24
 msgid "Easy distribution of applications"
-msgstr ""
+msgstr "Простое распространение приложений"
 
 #: i2p2www/pages/site/docs/plugins.html:28
 msgid ""
 "Allows innovation and use of additional libraries without worrying about\n"
 "increasing the size of i2pupdate.sud"
 msgstr ""
+"Позволяет использовать инновации и дополнительные библиотеки, не "
+"беспокоясь об \n"
+"увеличении размера i2pupdate.sud"
 
 #: i2p2www/pages/site/docs/plugins.html:33
 msgid ""
@@ -7328,50 +1422,64 @@ msgid ""
 "\n"
 "with the I2P installation"
 msgstr ""
+"Поддержка больших или специализированных приложений, которые никогда не "
+"будут связаны \n"
+"с установкой I2P"
 
 #: i2p2www/pages/site/docs/plugins.html:38
 msgid "Cryptographically signed and verified applications"
-msgstr ""
+msgstr "Криптографически подписанные и проверенные приложения"
 
 #: i2p2www/pages/site/docs/plugins.html:42
 msgid "Automatic updates of applications, just like for the router"
-msgstr ""
+msgstr "Автоматическое обновление приложений, совсем как для маршрутизатора"
 
 #: i2p2www/pages/site/docs/plugins.html:46
 msgid ""
 "Separate initial install and update packages, if desired, for smaller "
 "update downloads"
 msgstr ""
+"Отдельные начальная установка и пакеты обновлений, по желанию, для "
+"уменьшения размера загружаемых обновлений"
 
 #: i2p2www/pages/site/docs/plugins.html:50
 msgid ""
 "One-click installation of applications. No more asking users to modify\n"
 "wrapper.config or clients.config"
 msgstr ""
+"Установка приложений в один клик. Не спрашивая пользователей об изменении"
+" \n"
+"wrapper.config или clients.config"
 
 #: i2p2www/pages/site/docs/plugins.html:55
 msgid "Isolate applications from the base $I2P installation"
-msgstr ""
+msgstr "Изолирование приложений от базовой установки $I2P"
 
 #: i2p2www/pages/site/docs/plugins.html:59
 msgid ""
 "Automatic compatibility checking for I2P version, Java version, Jetty\n"
 "version, and previous installed application version"
 msgstr ""
+"Автоматическая проверка совместимости с версией I2P, Java, Jetty \n"
+"и предыдущей установленной версией приложения"
 
 #: i2p2www/pages/site/docs/plugins.html:64
 msgid "Automatic link addition in console"
-msgstr ""
+msgstr "Автоматическое добавление ссылки в консоли"
 
 #: i2p2www/pages/site/docs/plugins.html:68
 msgid ""
 "Automatic startup of application, including modifying classpath, without "
 "requiring a restart"
 msgstr ""
+"Автоматический запуск приложения, включая модификацию classpath без "
+"необходимости перезапуска"
 
 #: i2p2www/pages/site/docs/plugins.html:72
 msgid "Automatic integration and startup of webapps into console Jetty instance"
 msgstr ""
+"Автоматическая интеграция и запуск веб-приложения в консольном экземпляре"
+" Jetty"
 
 #: i2p2www/pages/site/docs/plugins.html:76
 #, python-format
@@ -7379,34 +1487,36 @@ msgid ""
 "Facilitate creation of 'app stores' like the one at\n"
 "%(pluginsite)s"
 msgstr ""
+"Облегченное создание 'app stores', как для \n"
+"%(pluginsite)s"
 
 #: i2p2www/pages/site/docs/plugins.html:81
 msgid "One-click uninstall"
-msgstr ""
+msgstr "Удаление в один клик"
 
 #: i2p2www/pages/site/docs/plugins.html:85
 msgid "Language and theme packs for the console"
-msgstr ""
+msgstr "Языковые пакеты и темы для консоли"
 
 #: i2p2www/pages/site/docs/plugins.html:89
 msgid "Bring detailed application information to the router console"
-msgstr ""
+msgstr "Вывод детализированной информации от приложения в консоль маршрутизатора"
 
 #: i2p2www/pages/site/docs/plugins.html:93
 msgid "Non-java applications also supported"
-msgstr ""
+msgstr "Также поддерживаются не-Java приложения"
 
 #: i2p2www/pages/site/docs/plugins.html:99
 msgid "Required I2P version"
-msgstr ""
+msgstr "Требуемая версия I2P"
 
 #: i2p2www/pages/site/docs/plugins.html:100
 msgid "0.7.12 or newer."
-msgstr ""
+msgstr "0.7.12 или новее."
 
 #: i2p2www/pages/site/docs/plugins.html:102
 msgid "Installation"
-msgstr ""
+msgstr "Установка"
 
 #: i2p2www/pages/site/docs/plugins.html:103
 msgid ""
@@ -7422,6 +1532,16 @@ msgid ""
 " at\n"
 "the top of your summary bar."
 msgstr ""
+"Чтобы установить и запустить плагин, скопируйте ссылку на установщик "
+".xpi2p в \n"
+"форму внизу \n"
+"configclients.jsp"
+" в \n"
+"консоли вашего маршрутизатора и нажмите кнопку \"install plugin\". "
+"После \n"
+"установки и запуска плагина ссылка на него обычно появляется вверху \n"
+"вашей строки состояния."
 
 #: i2p2www/pages/site/docs/plugins.html:112
 msgid ""
@@ -7438,10 +1558,21 @@ msgid ""
 "including dev\n"
 "builds)."
 msgstr ""
+"Чтобы обновить плагин до последней версии, просто нажмите кнопку "
+"обновления в \n"
+"configclients.jsp."
+" \n"
+"Также есть кнопка для проверки актуальности версии плагина, как и \n"
+"кнопка проверки наличия обновления для плагина. Проверка наличия "
+"обновлений для\n"
+"плагинов будет выполнена при обновлении I2P до нового релиза (за "
+"исключением \n"
+"тестовых сборок)."
 
 #: i2p2www/pages/site/docs/plugins.html:122
 msgid "Development"
-msgstr ""
+msgstr "Разработка"
 
 #: i2p2www/pages/site/docs/plugins.html:123
 #, python-format
@@ -7450,6 +1581,8 @@ msgid ""
 "the\n"
 "plugin forum on %(zzz)s."
 msgstr ""
+"Смотри актуальную спецификацию плагинов и\n"
+"форум о плагинах на %(zzz)s."
 
 #: i2p2www/pages/site/docs/plugins.html:128
 #, python-format
@@ -7460,6 +1593,11 @@ msgid ""
 "developed\n"
 "specifically as examples."
 msgstr ""
+"Также смотри исходники плагинов, разработанных другими людьми. Некоторые "
+"плагины, такие\n"
+"как snowman, были "
+"разработаны\n"
+"специально в качестве примеров."
 
 #: i2p2www/pages/site/docs/plugins.html:134
 msgid ""
@@ -7467,10 +1605,13 @@ msgid ""
 "\n"
 "or easily add some feature."
 msgstr ""
+"Разыскиваются разработчики! Плагины это замечательная возможность "
+"узнать больше о I2P,\n"
+"или легко добавить новую возможность."
 
 #: i2p2www/pages/site/docs/plugins.html:139
 msgid "Getting Started"
-msgstr ""
+msgstr "С чего начать"
 
 #: i2p2www/pages/site/docs/plugins.html:140
 #, python-format
@@ -7479,16 +1620,22 @@ msgid ""
 "makeplugin.sh from the i2p.scripts branch in "
 "monotone."
 msgstr ""
+"Чтобы сделать плагин из имеющегося исполняемого пакета вам понадобится \n"
+"makeplugin.sh из ветки i2p.scripts в monotone."
 
 #: i2p2www/pages/site/docs/plugins.html:146
 msgid "Known Issues"
-msgstr ""
+msgstr "Известные проблемы"
 
 #: i2p2www/pages/site/docs/plugins.html:147
 msgid ""
 "Note that the router's plugin architecture does NOT currently\n"
 "provide any additional security isolation or sandboxing of plugins."
 msgstr ""
+"Учтите, что архитектура плагинов маршрутизатора на данный момент "
+"НЕ \n"
+"предоставляет дополнительную изоляцию безопасности или запуск плагинов в "
+"песочнице."
 
 #: i2p2www/pages/site/docs/plugins.html:153
 msgid ""
@@ -7497,10 +1644,14 @@ msgid ""
 " the\n"
 "class cache; a full router restart is required."
 msgstr ""
+"Обновление плагина с jar-файлами (но не war) не будет распознано, если \n"
+"плагин уже запущен, т.к. для этого требуется, чтобы загрузчик классов "
+"сбросил \n"
+"кэш классов; необходим полный перезапуск маршрутизатора."
 
 #: i2p2www/pages/site/docs/plugins.html:159
 msgid "The stop button may be displayed even if there is nothing to stop."
-msgstr ""
+msgstr "Кнопка остановки может отображаться, даже если останавливать нечего."
 
 #: i2p2www/pages/site/docs/plugins.html:163
 msgid ""
@@ -7508,6 +1659,9 @@ msgid ""
 "in\n"
 "$CWD."
 msgstr ""
+"Плагины, запущенные в отдельном JVM, создают директорию "
+"logs/ в \n"
+"$CWD."
 
 #: i2p2www/pages/site/docs/plugins.html:168
 msgid ""
@@ -7516,6 +1670,12 @@ msgid ""
 "same keys as for router update), so the first key seen for a signer is\n"
 "automatically accepted—there is no signing key authority."
 msgstr ""
+"Нет никаких первоначальных ключей, за исключением ключей jrandom и zzz "
+"(используются \n"
+"те же ключи, что и для обновления маршрутизатора), так что первый ключ, "
+"доступный для подписания, \n"
+"автоматически принимается—авторизация подписывающих ключей "
+"отсутствует."
 
 #: i2p2www/pages/site/docs/plugins.html:174
 msgid ""
@@ -7523,6 +1683,8 @@ msgid ""
 "on\n"
 "Windows."
 msgstr ""
+"При удалении плагина директории не всегда удаляются, особенно в \n"
+"Windows."
 
 #: i2p2www/pages/site/docs/plugins.html:179
 msgid ""
@@ -7531,18 +1693,21 @@ msgid ""
 "\"plugin is corrupt\" message if pack200 compression of the plugin file "
 "is used."
 msgstr ""
+"При установке плагинов, требующих Java 1.6, на машине с Java 1.5 "
+"возникнет \n"
+"сообщение \"plugin is corrupt\", если используется pack200 сжатие плагина."
 
 #: i2p2www/pages/site/docs/plugins.html:184
 msgid "Theme and translation plugins are untested."
-msgstr ""
+msgstr "Темы и плагины переводов не тестируются."
 
 #: i2p2www/pages/site/docs/plugins.html:188
 msgid "Disabling autostart doesn't always work."
-msgstr ""
+msgstr "Отключение автоматического запуска не всегда срабатывает."
 
 #: i2p2www/pages/site/docs/ports.html:2
 msgid "Ports Used by I2P"
-msgstr ""
+msgstr "Порты, используемые I2P"
 
 #: i2p2www/pages/site/docs/ports.html:7
 msgid ""
@@ -7551,6 +1716,10 @@ msgid ""
 "common alternates,\n"
 "and some typical related applications."
 msgstr ""
+"Ниже приведены порты, используемые или зарезервированные под нужды I2P, "
+"включая порты для \n"
+"известных плагинов, общих альтернатив \n"
+"и некоторых типичных связанных приложений."
 
 #: i2p2www/pages/site/docs/ports.html:13
 #, python-format
@@ -7562,18 +1731,31 @@ msgid ""
 "For new plugins, we recommend using the next available port\n"
 "in the 766x range."
 msgstr ""
+"Учтите, что многие из них не задействованы по умолчанию. \n"
+"Больше информации есть в FAQ. \n"
+"Также смотри документацию по конкретным плагинам. \n"
+"Авторы плагинов, пожалуйста, добавляйте сюда все используемые порты. \n"
+"Для новых плагинов мы рекомендуем использовать следующий доступный порт \n"
+"из диапазона 766x."
 
 #: i2p2www/pages/site/docs/ports.html:53
 msgid "recommended spot for new plugins/applications"
-msgstr ""
+msgstr "рекомендованный диапазон для новых плагинов/приложений"
+
+#: i2p2www/pages/site/docs/api/bob.html:3
+#: i2p2www/pages/site/docs/api/datagrams.html:3
+#: i2p2www/pages/site/docs/how/garlic-routing.html:3
+#: i2p2www/pages/site/docs/protocol/index.html:3
+msgid "August 2010"
+msgstr "Август 2010"
 
 #: i2p2www/pages/site/docs/api/bob.html:5
 msgid "BOB - Basic Open Bridge"
-msgstr ""
+msgstr "BOB - Basic Open Bridge"
 
 #: i2p2www/pages/site/docs/api/bob.html:7
 msgid "Technical differences from SAM (for the better?)"
-msgstr ""
+msgstr "Технические отличия от SAM (для улучшения?)"
 
 #: i2p2www/pages/site/docs/api/bob.html:9
 msgid ""
@@ -7584,12 +1766,22 @@ msgid ""
 "destination key, and to set the destination key to port bindings. \n"
 "All connections run in parallel."
 msgstr ""
+"BOB имеет раздельные каналы для команд и данных. \n"
+"Один - сокет канала команд приложения к маршрутизатору для настройки. \n"
+"Второй - сокеты данных приложения к/от маршрутизатора, только для "
+"передачи данных. \n"
+"Канал команд нужен только для создания или задания начального ключа "
+"пункта назначения, \n"
+"и для установки связи ключа пункта назначения и порта. \n"
+"Все соединения запускаются параллельно."
 
 #: i2p2www/pages/site/docs/api/bob.html:18
 msgid ""
 "SAM has one connection that does everything, and you need to parse every "
 "packet."
 msgstr ""
+"В SAM все выполняется через одно соединение, и вам приходится разбирать "
+"каждый пакет."
 
 #: i2p2www/pages/site/docs/api/bob.html:22
 msgid ""
@@ -7599,22 +1791,26 @@ msgid ""
 "to\n"
 "your privacy."
 msgstr ""
+"BOB не хранит значений пары ключей, как и маршрутизатор. \n"
+"Ваше приложение хранит значения пары ключей. \n"
+"Это сделано для уменьшения сложности кода маршрутизатор, \n"
+"это также добавляет вам приватности."
 
 #: i2p2www/pages/site/docs/api/bob.html:29
 msgid "SAM router stores every keypair you ever make."
-msgstr ""
+msgstr "Маршрутизатор SAM хранит все пары ключей когда либо созданные вами."
 
 #: i2p2www/pages/site/docs/api/bob.html:33
 msgid "Those are the important differences."
-msgstr ""
+msgstr "И это самые важные отличия."
 
 #: i2p2www/pages/site/docs/api/bob.html:37
 msgid "KEYS = keypair public+private, these are BASE64"
-msgstr ""
+msgstr "KEYS = пара ключей public+private, в виде BASE64"
 
 #: i2p2www/pages/site/docs/api/bob.html:40
 msgid "KEY = public key, also BASE64"
-msgstr ""
+msgstr "KEY = public ключ, также BASE64"
 
 #: i2p2www/pages/site/docs/api/bob.html:43
 msgid ""
@@ -7622,6 +1818,9 @@ msgid ""
 "\"+DESCRIPTION+\"\n"
 "\"            , where the DESCRIPTION is what went wrong."
 msgstr ""
+"ERROR как и предполагается, возвращает сообщение "
+"\"ERROR \"+DESCRIPTION+\"\n"
+"\", где DESCRIPTION это описание проблемы."
 
 #: i2p2www/pages/site/docs/api/bob.html:46
 msgid ""
@@ -7629,12 +1828,17 @@ msgid ""
 "returned, it is on the same line. OK means the command is "
 "finished."
 msgstr ""
+"OK возвращает \"OK\", и если есть возвращаемые "
+"данные, они буду расположены в этой же строке. OK означает, "
+"что команда выполнена."
 
 #: i2p2www/pages/site/docs/api/bob.html:49
 msgid ""
 "DATA lines contain information that you requested. There may"
 " be multiple DATA lines per request."
 msgstr ""
+"Строка DATA содержит информацию, которую вы запросили. Может"
+" быть несколько строк DATA на один запрос."
 
 #: i2p2www/pages/site/docs/api/bob.html:53
 msgid ""
@@ -7643,6 +1847,11 @@ msgid ""
 "the rules... it can actually return nothing! This is intentional, since\n"
 "help is a HUMAN and not an APPLICATION command."
 msgstr ""
+"Примечание: Команда help - ЕДИНСТВЕННАЯ команда, для которой есть "
+"исключения из\n"
+"правил... Она может ничего не возвращать! Это сделано намеренно, "
+"поскольку \n"
+"help это команда для ЧЕЛОВЕКА, а не для ПРИЛОЖЕНИЯ."
 
 #: i2p2www/pages/site/docs/api/bob.html:59
 msgid ""
@@ -7652,28 +1861,35 @@ msgid ""
 "Just telnet to localhost 2827 and type help and you can get full "
 "documentation on each command."
 msgstr ""
+"ПОЖАЛУЙСТА УЧТИТЕ:\n"
+"Для получения АКТУАЛЬНЫХ подробностей по командам ПОЖАЛУЙСТА используйте "
+"встроенную команду help.\n"
+"Просто подключитесь по telnet к localhost 2827 и введите help, и вы "
+"получите полную документацию по каждой команде."
 
 #: i2p2www/pages/site/docs/api/bob.html:65
 msgid ""
 "Commands never get obsoleted or changed, however new commands do get "
 "added from time to time."
 msgstr ""
+"Команды никогда не устаревают и не изменяются, тем не менее, новые "
+"команды время от времени появляются."
 
 #: i2p2www/pages/site/docs/api/bob.html:69
 msgid "Here are the commands we have as of this writing:"
-msgstr ""
+msgstr "Вот список команд, которые имеются на момент написания страницы:"
 
 #: i2p2www/pages/site/docs/api/bob.html:74
 msgid "COMMAND"
-msgstr ""
+msgstr "КОМАНДА"
 
 #: i2p2www/pages/site/docs/api/bob.html:74
 msgid "OPERAND"
-msgstr ""
+msgstr "ОПЕРАНД"
 
 #: i2p2www/pages/site/docs/api/bob.html:74
 msgid "RETURNS"
-msgstr ""
+msgstr "ВОЗВРАЩАЕТ"
 
 #: i2p2www/pages/site/docs/api/bob.html:101
 msgid ""
@@ -7686,6 +1902,14 @@ msgid ""
 "many streams in or out one socket -- that can't scale when you have alot "
 "of connections!"
 msgstr ""
+"После установки все необходимые TCP сокеты могут и будут заблокированы, и"
+" нет необходимости в \n"
+"дополнительных сообщениях в/из канал команд. Это позволяет маршрутизатору"
+" проходить \n"
+"поток без разрыва с OOM, в отличие от SAM, который захлебывается при "
+"попытке впихнуть \n"
+"несколько потоков в или из одного сокета -- это не поддается "
+"масштабированию при наличии большого числа подключений!"
 
 #: i2p2www/pages/site/docs/api/bob.html:108
 msgid ""
@@ -7708,6 +1932,22 @@ msgid ""
 "It will simply be fooled -- the destinations are not reachable, and that "
 "nothing is coming in."
 msgstr ""
+"Есть еще одна замечательная вещь в этом специфическом интерфейсе - "
+"написать что угодно, подключающееся к нему, \n"
+"намного проще, чем к SAM. Не нужно делать ничего дополнительного после "
+"установки. \n"
+"Его настройка настолько проста, что любое просто средство, как например "
+"nc (netcat), можно использовать \n"
+"для указания на какое-то приложение. Смысле в том, что можно "
+"запланировать время запуска и остановки \n"
+"приложения, и для этого не нужно изменять его, или, даже, \n"
+"останавливать это приложение. Вместо этого вы можете буквально \"вынуть\""
+" пункт назначения, и \n"
+"\"вставить\" снова. Поскольку для восстановления моста используются та же"
+" пара IP/порт и ключи, \n"
+"то обычному приложению это не важно, и оно не будет даже об этом знать. \n"
+"Оно просто будет обмануто -- пункт назначения недоступен, и ничего не "
+"поступает на вход."
 
 #: i2p2www/pages/site/docs/api/bob.html:120
 msgid ""
@@ -7719,18 +1959,25 @@ msgid ""
 "that you\n"
 "can telnet into, and watch the pretty ASCII test puke forth."
 msgstr ""
+"В следующем примере мы установим очень простое закольцованное  локальное "
+"подключение \n"
+"с двумя пунктами назначения. Пунктом \"mouth\" будет служба CHARGEN \n"
+"демона суперсервера INET. Пунктом \"ear\" будет локальный порт, к "
+"которому \n"
+"вы можете подключиться по telnet и увидеть забавный тест с символами "
+"ASCII."
 
 #: i2p2www/pages/site/docs/api/bob.html:128
 msgid "EXAMPLE SESSION DIALOGUE -- simple telnet 127.0.0.1 2827 works"
-msgstr ""
+msgstr "ПРИМЕР ДИАЛОГА СЕССИИ -- простой telnet 127.0.0.1 2827 работает"
 
 #: i2p2www/pages/site/docs/api/bob.html:129
 msgid "Application"
-msgstr ""
+msgstr "Приложени"
 
 #: i2p2www/pages/site/docs/api/bob.html:130
 msgid "BOB's Command response."
-msgstr ""
+msgstr "Ответ команда от BOB"
 
 #: i2p2www/pages/site/docs/api/bob.html:132
 #: i2p2www/pages/site/docs/api/bob.html:144
@@ -7739,7 +1986,7 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/bob.html:284
 #: i2p2www/pages/site/docs/api/bob.html:299
 msgid "FROM"
-msgstr ""
+msgstr "ОТ"
 
 #: i2p2www/pages/site/docs/api/bob.html:132
 #: i2p2www/pages/site/docs/api/bob.html:144
@@ -7748,7 +1995,7 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/bob.html:284
 #: i2p2www/pages/site/docs/api/bob.html:299
 msgid "TO"
-msgstr ""
+msgstr "К"
 
 #: i2p2www/pages/site/docs/api/bob.html:132
 #: i2p2www/pages/site/docs/api/bob.html:144
@@ -7757,11 +2004,11 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/bob.html:284
 #: i2p2www/pages/site/docs/api/bob.html:299
 msgid "DIALOGUE"
-msgstr ""
+msgstr "ДИАЛОГ"
 
 #: i2p2www/pages/site/docs/api/bob.html:139
 msgid "MAKE NOTE OF THE ABOVE DESTINATION KEY, YOURS WILL BE DIFFERENT!"
-msgstr ""
+msgstr "ОБРАТИТЕ ВНИМАНИЕ НА КЛЮЧ НАЗНАЧЕНИЯ ВЫШЕ, ВАШ БУДЕТ ДРУГИМ!"
 
 #: i2p2www/pages/site/docs/api/bob.html:153
 msgid ""
@@ -7771,10 +2018,16 @@ msgid ""
 "connect \n"
 "to the CHARGEN service on 19/TCP."
 msgstr ""
+"Пока что ошибки не было, пункт назначения с именем \"mouth\" \n"
+"установлен. Когда вы подключаетесь к указанному пункту, вы на самом деле"
+" \n"
+"соединяетесь со службой CHARGEN на порту 19/TCP."
 
 #: i2p2www/pages/site/docs/api/bob.html:159
 msgid "Now for the other half, so that we can actually contact this destination."
 msgstr ""
+"А теперь вторая половина, мы на самом деле подключаемся к пункту "
+"назначения."
 
 #: i2p2www/pages/site/docs/api/bob.html:179
 msgid ""
@@ -7784,24 +2037,33 @@ msgid ""
 "In this case, we want to contact \"mouth\", all we do is paste in the\n"
 "key and it goes."
 msgstr ""
+"Все что нам теперь осталось сделать - подключиться по telnet к 127.0.0.1 "
+"на порт 37337, отправить ключ пункта назначения или адрес узла из "
+"адресной книги, к которому мы хотим подключиться. \n"
+"В нашем случае, мы хотим подключиться к \"mouth\", мы вставляем \n"
+"ключ и понеслась."
 
 #: i2p2www/pages/site/docs/api/bob.html:186
 msgid ""
 "NOTE: The \"quit\" command in the command channel does NOT "
 "disconnect the tunnels like SAM."
 msgstr ""
+"ПРИМЕЧАНИЕ: Команда \"quit\" в канале команд НЕ выполняет разрыв "
+"соединения туннелей, как это делает SAM."
 
 #: i2p2www/pages/site/docs/api/bob.html:203
 msgid "After a few virtual miles of this spew, press Control-]"
 msgstr ""
+"После пары виртуальных километров этой отрыжки нажмите "
+"Control-]"
 
 #: i2p2www/pages/site/docs/api/bob.html:215
 msgid "Here is what happened..."
-msgstr ""
+msgstr "И вот что произошло..."
 
 #: i2p2www/pages/site/docs/api/bob.html:223
 msgid "You can connect to EEPSITES too!"
-msgstr ""
+msgstr "Также вы не можете подключиться к EEPSITE!"
 
 #: i2p2www/pages/site/docs/api/bob.html:256
 msgid ""
@@ -7814,18 +2076,27 @@ msgid ""
 "They would be meaningless to the application, and are only presented for "
 "human debugging."
 msgstr ""
+"Прикольно, правда? Если хотите, попробуйте другие известные EEPSITE, "
+"несуществующие, \n"
+"и т.д., чтобы понять что можно ожидать на выходе в различных ситуациях. \n"
+"По большей части предполагается что вы игнорируете любые сообщения об "
+"ошибках. \n"
+"Они будут бессмысленными для приложения, и выводятся только для отладки "
+"человеком."
 
 #: i2p2www/pages/site/docs/api/bob.html:263
 msgid "Let's put down our destinations now that we are all done with them."
 msgstr ""
+"Давайте теперь отключим наши пункты назначения, т.к. мы уже с ними "
+"закончили."
 
 #: i2p2www/pages/site/docs/api/bob.html:267
 msgid "First, lets see what destination nicknames we have."
-msgstr ""
+msgstr "Для начала посмотрим какие имена пунктов у нас есть."
 
 #: i2p2www/pages/site/docs/api/bob.html:279
 msgid "Alright, there they are. First, let's remove \"mouth\"."
-msgstr ""
+msgstr "Отлично, вот и они. Сначала давайте уберем \"mouth\"."
 
 #: i2p2www/pages/site/docs/api/bob.html:293
 msgid ""
@@ -7833,6 +2104,9 @@ msgid ""
 "fast,\n"
 "and shows you what typical ERROR messages looks like."
 msgstr ""
+"Теперь уберем \"ear\", и вот что происходит когда вы печатаете слишком "
+"быстро, \n"
+"также вы увидите как выглядят типичные сообщения об ОШИБКАХ."
 
 #: i2p2www/pages/site/docs/api/bob.html:312
 msgid ""
@@ -7840,6 +2114,9 @@ msgid ""
 "because it is very simple. There are two possible settings for it, and\n"
 "it is toggled with the \"quiet\" command."
 msgstr ""
+"Я не стану показывать пример получателя моста, \n"
+"потому что это слишком просто. Для него есть два доступных режима, \n"
+"и они переключаются командой \"quiet\"."
 
 #: i2p2www/pages/site/docs/api/bob.html:318
 msgid ""
@@ -7848,6 +2125,11 @@ msgid ""
 "single line consisting of the BASE64 address followed by a newline.\n"
 "Everything after that is for the application to actually consume."
 msgstr ""
+"По умолчанию этот режим отключен, и первые данные, которые приходят на \n"
+"ваш слушающий сокет - это пункт назначения, который к вам подключается. \n"
+"Это одна строка, состоящая из BASE64 адреса, оканчивающаяся переводом "
+"строки. \n"
+"Все остальное после нее предназначено для обработки приложением."
 
 #: i2p2www/pages/site/docs/api/bob.html:325
 msgid ""
@@ -7858,6 +2140,17 @@ msgid ""
 "can use BOB to point a destination at a web server, for example, and\n"
 "you would not have to modify the web server at all."
 msgstr ""
+"Тихий режим можете себе представить в виде обычного интернет подключения."
+" \n"
+"Никаких дополнительных данных не приходит вовсе. Просто как будто вы "
+"подключились \n"
+"к обычному интернету. Этот режим предоставляет такую же форму "
+"прозрачности, какая \n"
+"доступна на странице настроек туннеля консоли маршрутизатора, и поэтому "
+"вы \n"
+"можете использовать BOB, например,  для указания пункта назначения на "
+"веб-сервере, \n"
+"и вам совсем не нужно изменять веб-сервер."
 
 #: i2p2www/pages/site/docs/api/bob.html:334
 msgid ""
@@ -7873,10 +2166,27 @@ msgid ""
 "point to a set of backup machines depending on what is running, etc,\n"
 "etc. Only your imagination limits what you could do with BOB."
 msgstr ""
+"Преимущества использования BOB, как описано ранее. \n"
+"Вы можете запланировать произвольное время работы приложения, \n"
+"перенаправить а другую машину, и т.п. Одним из применений этого может "
+"быть \n"
+"желание попробовать испортить оценку доступности канала "
+"\"маршрутизатор\"-\"пункт назначения\". \n"
+"Вы можете опускать и поднимать пункт назначения совершенно другим \n"
+"способом, чтобы выполнять произвольную остановку и запуск службы. Таким "
+"методом вы \n"
+"будете только отключать возможность подключения к такой службе, и не "
+"будете \n"
+"вынуждены останавливать и перезапускать ее. Вы можете перенаправить \n"
+"или указать на другую машину в вашей LAN пока вы выполняете обновление, \n"
+"или указать на набор запасных машин, в зависимости от того что запущено, "
+"и т.д. \n"
+"Ваши возможности взаимодействия с BOB ограничены только вашим "
+"воображением."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:6
 msgid "Datagram Overview"
-msgstr ""
+msgstr "Обзор Дейтаграмм"
 
 #: i2p2www/pages/site/docs/api/datagrams.html:7
 #, python-format
@@ -7893,6 +2203,17 @@ msgid ""
 "addition, the\n"
 "message and sender are authenticated by signing the payload."
 msgstr ""
+"Дейтаграммы строятся на основе I2CP, и "
+"предоставляют аутентифицированные \n"
+"сообщения в стандартном формате, на которые можно ответить. Это позволяет"
+" приложениям читать \n"
+"достоверный адрес \"От\" в дейтаграмме, и узнать с какого адреса на самом"
+" деле \n"
+"отправлено сообщение. Это важно для некоторых приложений, поскольку "
+"базовое сообщение I2P \n"
+"не форматировано - в нем нет адреса \"от\" (как это есть в IP). Кроме "
+"того, \n"
+"сообщение и отправитель аутентифицируются по подписи на данных."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:16
 #, python-format
@@ -7904,10 +2225,17 @@ msgid ""
 "the protocols are converted to I2NP messages by the router, and\n"
 "either protocol may be carried by either transport."
 msgstr ""
+"Дейтаграммы, как и пакеты потоковой "
+"библиотеки,\n"
+"являются конструкциями уровня приложения.\n"
+"Эти протоколы не зависят от низкоуровневого транспорта;\n"
+"протоколы конвертируются маршрутизатором в сообщения I2NP, \n"
+"каждый протокол может передаваться любым транспортом."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:25
 msgid "Application Guide"
-msgstr ""
+msgstr "Руководство по Приложениям"
 
 #: i2p2www/pages/site/docs/api/datagrams.html:26
 #, python-format
@@ -7920,10 +2248,17 @@ msgid ""
 "href=\"%(socks)s\">SOCKS proxy,\n"
 "the 'streamr' tunnel types, and udpTunnel classes."
 msgstr ""
+"Приложения, написанные на Java, могут использовать \n"
+"API дейтаграмм, \n"
+"приложения на других языках \n"
+"могут использовать поддержку дейтаграмм SAM'а. \n"
+"Также есть ограниченная поддержка в i2ptunnel в SOCKS proxy, \n"
+"'streamr' типы туннеля и классы udpTunnel."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:37
 msgid "Datagram Length"
-msgstr ""
+msgstr "Длина Дейтаграммы"
 
 #: i2p2www/pages/site/docs/api/datagrams.html:38
 msgid ""
@@ -7939,6 +2274,17 @@ msgid ""
 "Messages over 16 KB cannot be delivered over NTCP, dropping delivery "
 "chances even more."
 msgstr ""
+"Проектировщик приложения должен хорошо понимать разницу между "
+"дейтаграммами с ответом \n"
+"и без оных. Также, размер дейтаграммы влияет на надежность, в виду "
+"фрагментации туннелем \n"
+"сообщений по 1 КБ. Чем больше сообщение фрагментируется, тем более "
+"вероятно, что одно из них будет потеряно \n"
+"на промежуточном прыжке. Сообщения размером более нескольких КБ не "
+"рекомендованы для использования. \n"
+"При размере более 10 КБ доставка, возможно, сильно ухудшится. \n"
+"Сообщения более 16 КБ не могут быть доставлены по NTCP, шансы сбоя "
+"доставки сильно увеличиваются."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:47
 #, python-format
@@ -7957,10 +2303,20 @@ msgid ""
 "tune\n"
 "the ElGamal Session Tag parameters."
 msgstr ""
+"Также учитывайте, что различные накладные расходы добавляются на более "
+"низких уровнях, в ассиметричном \n"
+"алгоритме ElGamal/AES, они создают большую"
+" нагрузку на прерывистые сообщения, \n"
+"как в приложении Kademlia-over-UDP. Сейчас реализация отлажена \n"
+"для часто встречающегося трафика с использованием потоковой библиотеки. "
+"Например, доставлено \n"
+"большое количество меток сессии и время жизни меток сессии мало. \n"
+"Сейчас нет конфигурации, доступной в I2CP, для настройки \n"
+"параметров меток сессии ElGamal."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:57
 msgid "I2CP Protocol Number and Ports"
-msgstr ""
+msgstr "Номер Протокола I2CP и Порты"
 
 #: i2p2www/pages/site/docs/api/datagrams.html:58
 msgid ""
@@ -7970,6 +2326,11 @@ msgid ""
 "It must be set to demultiplex datagram and streaming traffic received on "
 "the same Destination."
 msgstr ""
+"Стандартный номер протокола I2CP для дейтаграмм - PROTO_DATAGRAM (17). \n"
+"Приложения могут указывать или не указывать протокол \n"
+"в заголовке I2CP. По умолчанию он не указан. \n"
+"Его нужно указать для демультиплексирования дейтаграммы и потокового "
+"трафика, полученных на одном пункте назначения."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:65
 #, python-format
@@ -7982,6 +2343,13 @@ msgid ""
 "described in\n"
 "the I2CP page."
 msgstr ""
+"Поскольку дейтаграммы не ориентированы на соединение, приложению может \n"
+"понадобиться номер порта для сопоставления дейтаграмм от определенных "
+"узлов или сессий подключения, \n"
+"как и в традиционном UDP над IP. \n"
+"Приложения могут добавить порты 'от' и 'к' в заголовок I2CP (gzip), как "
+"это описано на \n"
+"странице I2CP."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:73
 #, python-format
@@ -8001,6 +2369,19 @@ msgid ""
 "datagram\n"
 "for the reply, returning the nonce from the request."
 msgstr ""
+"В API дейтаграмм нет возможности указать является ли она безответной "
+"(raw) \n"
+"или с возможностью ответа. Приложение должно быть само определять "
+"правильный тип. \n"
+"Номер протокола I2CP или порт могут быть использованы приложением \n"
+"для определения типа дейтаграммы. \n"
+"Для этой цели в I2PSession API \n"
+"определены номера протокола I2CP - PROTO_DATAGRAM (подписанная) и "
+"PROTO_DATAGRAM_RAW. Общим принципом в приложениях клиент/сервер с "
+"дейтаграммами является \n"
+"использование подписанных дейтаграмм для запросов, которые содержат некие"
+" данные, и raw дейтаграммы \n"
+"для ответа, с обратной отправкой тех данных из запроса."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:85
 #, python-format
@@ -8010,11 +2391,15 @@ msgid ""
 "as implemented in\n"
 "I2PSessionMuxedImpl."
 msgstr ""
+"Протоколы и порты могут быть настроены в \n"
+"I2PSession API I2CP, \n"
+"как это реализовано в \n"
+"I2PSessionMuxedImpl."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:93
-#: i2p2www/pages/site/docs/api/streaming.html:325
+#: i2p2www/pages/site/docs/api/streaming.html:381
 msgid "Data Integrity"
-msgstr ""
+msgstr "Целостность данных"
 
 #: i2p2www/pages/site/docs/api/datagrams.html:94
 #, python-format
@@ -8023,11 +2408,15 @@ msgid ""
 "the I2CP layer.\n"
 "There is no checksum field in the datagram protocol."
 msgstr ""
+"Целостность данных, гарантируемая проверкой gzip суммы CRC-32, "
+"реализована на \n"
+"уровне I2CP. \n"
+"В протоколе дейтаграмм нет поля с проверочной суммой."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:100
-#: i2p2www/pages/site/docs/api/streaming.html:333
+#: i2p2www/pages/site/docs/api/streaming.html:389
 msgid "Packet Encapsulation"
-msgstr ""
+msgstr "Инкапсуляция пакета"
 
 #: i2p2www/pages/site/docs/api/datagrams.html:101
 #, python-format
@@ -8042,20 +2431,28 @@ msgid ""
 "There is no packet delimiter mechanism or length field in the datagram "
 "protocol."
 msgstr ""
+"Каждая дейтаграмма отправляется через I2P как отдельное сообщение (или "
+"отдельный зубчик в\n"
+"Чесночном Сообщении).\n"
+"Инкапсуляция сообщения реализована в нижележащих уровнях \n"
+"I2CP,\n"
+"I2NP и \n"
+"туннельном сообщении.\n"
+"В протоколе дейтаграмм нет механизма разделения пакетов или поля длины."
 
 #: i2p2www/pages/site/docs/api/datagrams.html:114
 #: i2p2www/pages/site/docs/spec/datagrams.html:10
-#: i2p2www/pages/site/docs/transport/ssu.html:567
+#: i2p2www/pages/site/docs/transport/ssu.html:571
 msgid "Specification"
-msgstr ""
+msgstr "Спецификация"
 
 #: i2p2www/pages/site/docs/api/datagrams.html:116
 msgid "See the Datagrams Specification page."
-msgstr ""
+msgstr "Смотри страницу Спецификации Дейтаграмм."
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:4
 msgid "I2PControl - Remote Control Service"
-msgstr ""
+msgstr "I2PControl - Служба Удаленного Управления"
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:5
 #, python-format
@@ -8118,8 +2515,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:29
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:33
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:34
-#: i2p2www/pages/site/docs/protocol/i2cp.html:99
-#: i2p2www/pages/site/docs/protocol/i2cp.html:442
+#: i2p2www/pages/site/docs/protocol/i2cp.html:107
+#: i2p2www/pages/site/docs/protocol/i2cp.html:450
 #: i2p2www/pages/site/docs/spec/common-structures.html:16
 #: i2p2www/pages/site/docs/spec/common-structures.html:26
 #: i2p2www/pages/site/docs/spec/common-structures.html:37
@@ -8135,12 +2532,12 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/common-structures.html:162
 #: i2p2www/pages/site/docs/spec/common-structures.html:174
 #: i2p2www/pages/site/docs/spec/common-structures.html:227
-#: i2p2www/pages/site/docs/spec/common-structures.html:294
-#: i2p2www/pages/site/docs/spec/common-structures.html:343
-#: i2p2www/pages/site/docs/spec/common-structures.html:387
-#: i2p2www/pages/site/docs/spec/common-structures.html:432
-#: i2p2www/pages/site/docs/spec/common-structures.html:569
-#: i2p2www/pages/site/docs/spec/common-structures.html:625
+#: i2p2www/pages/site/docs/spec/common-structures.html:310
+#: i2p2www/pages/site/docs/spec/common-structures.html:359
+#: i2p2www/pages/site/docs/spec/common-structures.html:411
+#: i2p2www/pages/site/docs/spec/common-structures.html:456
+#: i2p2www/pages/site/docs/spec/common-structures.html:593
+#: i2p2www/pages/site/docs/spec/common-structures.html:655
 msgid "Description"
 msgstr ""
 
@@ -8536,36 +2933,40 @@ msgid "Method not found."
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/i2pcontrol.html:194
+msgid "Invalid parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:195
 msgid "Internal error."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:196
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
 msgid "I2PControl specific error codes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
 msgid "Invalid password provided."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
 msgid "No authentication token presented."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
 msgid "Authentication token doesn't exist."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
 msgid "The provided authentication token was expired and will be removed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
 msgid ""
 "The version of the I2PControl API used wasn't specified, but is required "
 "to be specified."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:203
 msgid ""
 "The version of the I2PControl API specified is not supported by "
 "I2PControl."
@@ -8626,9 +3027,7 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/i2ptunnel.html:43
 #, python-format
 msgid ""
-"The anonymous monotone"
-"\n"
+"The anonymous monotone\n"
 "sourcecode repository for I2P"
 msgstr ""
 
@@ -8950,12 +3349,6 @@ msgid ""
 "risks of socks proxies."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:3
-#: i2p2www/pages/site/docs/protocol/i2cp.html:3
-#: i2p2www/pages/site/docs/spec/streaming.html:3
-msgid "November 2012"
-msgstr ""
-
 #: i2p2www/pages/site/docs/api/streaming.html:8
 #, python-format
 msgid ""
@@ -9025,6 +3418,10 @@ msgid ""
 "it contains a full windowing implementation."
 msgstr ""
 
+#: i2p2www/pages/site/docs/api/streaming.html:58
+msgid "API"
+msgstr ""
+
 #: i2p2www/pages/site/docs/api/streaming.html:60
 #, python-format
 msgid ""
@@ -9104,14 +3501,14 @@ msgid ""
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/streaming.html:117
-#: i2p2www/pages/site/docs/protocol/i2cp.html:94
-#: i2p2www/pages/site/docs/protocol/i2cp.html:437
+#: i2p2www/pages/site/docs/protocol/i2cp.html:102
+#: i2p2www/pages/site/docs/protocol/i2cp.html:445
 msgid "Option"
 msgstr ""
 
 #: i2p2www/pages/site/docs/api/streaming.html:117
-#: i2p2www/pages/site/docs/protocol/i2cp.html:98
-#: i2p2www/pages/site/docs/protocol/i2cp.html:441
+#: i2p2www/pages/site/docs/protocol/i2cp.html:106
+#: i2p2www/pages/site/docs/protocol/i2cp.html:449
 msgid "Default"
 msgstr ""
 
@@ -9121,11 +3518,11 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/common-structures.html:58
 #: i2p2www/pages/site/docs/spec/common-structures.html:203
 #: i2p2www/pages/site/docs/spec/common-structures.html:257
-#: i2p2www/pages/site/docs/spec/common-structures.html:335
-#: i2p2www/pages/site/docs/spec/common-structures.html:421
-#: i2p2www/pages/site/docs/spec/common-structures.html:529
-#: i2p2www/pages/site/docs/spec/common-structures.html:607
-#: i2p2www/pages/site/docs/spec/common-structures.html:709
+#: i2p2www/pages/site/docs/spec/common-structures.html:351
+#: i2p2www/pages/site/docs/spec/common-structures.html:445
+#: i2p2www/pages/site/docs/spec/common-structures.html:553
+#: i2p2www/pages/site/docs/spec/common-structures.html:631
+#: i2p2www/pages/site/docs/spec/common-structures.html:739
 #: i2p2www/pages/site/docs/spec/datagrams.html:30
 #: i2p2www/pages/site/docs/spec/datagrams.html:89
 msgid "Notes"
@@ -9140,15 +3537,22 @@ msgstr ""
 #: i2p2www/pages/site/docs/api/streaming.html:121
 #: i2p2www/pages/site/docs/api/streaming.html:127
 #: i2p2www/pages/site/docs/api/streaming.html:133
-#: i2p2www/pages/site/docs/api/streaming.html:147
-#: i2p2www/pages/site/docs/api/streaming.html:176
-#: i2p2www/pages/site/docs/api/streaming.html:184
-#: i2p2www/pages/site/docs/api/streaming.html:214
+#: i2p2www/pages/site/docs/api/streaming.html:140
+#: i2p2www/pages/site/docs/api/streaming.html:152
+#: i2p2www/pages/site/docs/api/streaming.html:163
+#: i2p2www/pages/site/docs/api/streaming.html:192
+#: i2p2www/pages/site/docs/api/streaming.html:200
 #: i2p2www/pages/site/docs/api/streaming.html:220
-#: i2p2www/pages/site/docs/api/streaming.html:226
-#: i2p2www/pages/site/docs/api/streaming.html:240
-#: i2p2www/pages/site/docs/api/streaming.html:247
-#: i2p2www/pages/site/docs/api/streaming.html:254
+#: i2p2www/pages/site/docs/api/streaming.html:237
+#: i2p2www/pages/site/docs/api/streaming.html:249
+#: i2p2www/pages/site/docs/api/streaming.html:255
+#: i2p2www/pages/site/docs/api/streaming.html:261
+#: i2p2www/pages/site/docs/api/streaming.html:275
+#: i2p2www/pages/site/docs/api/streaming.html:282
+#: i2p2www/pages/site/docs/api/streaming.html:289
+#: i2p2www/pages/site/docs/api/streaming.html:314
+#: i2p2www/pages/site/docs/api/streaming.html:321
+#: i2p2www/pages/site/docs/api/streaming.html:328
 #, python-format
 msgid "As of release %(release)s."
 msgstr ""
@@ -9161,11 +3565,11 @@ msgstr ""
 msgid "Use the access list as a blacklist for incoming connections."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:137
+#: i2p2www/pages/site/docs/api/streaming.html:145
 msgid "Whether to respond to incoming pings"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:141
+#: i2p2www/pages/site/docs/api/streaming.html:157
 msgid ""
 "Comma- or space-separated list of Base64 peer Hashes to be\n"
 "blacklisted for incoming connections to ALL destinations in the context.\n"
@@ -9176,13 +3580,13 @@ msgid ""
 "router in a separate JVM and context."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:151
+#: i2p2www/pages/site/docs/api/streaming.html:167
 msgid ""
 "How much transmit data (in bytes) will be accepted that hasn't been "
 "written out yet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:155
+#: i2p2www/pages/site/docs/api/streaming.html:171
 msgid ""
 "When we're in congestion avoidance, we grow the window size at the rate\n"
 "of 1/(windowSize*factor).  In standard TCP, window sizes are"
@@ -9191,7 +3595,7 @@ msgid ""
 "A higher number means slower growth."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:162
+#: i2p2www/pages/site/docs/api/streaming.html:178
 msgid ""
 "How long to wait after instantiating a new con \n"
 "before actually attempting to connect.  If this is\n"
@@ -9201,19 +3605,19 @@ msgid ""
 "or that many milliseconds pass, and include any initial data with the SYN."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:170
+#: i2p2www/pages/site/docs/api/streaming.html:186
 msgid ""
 "How long to block on connect, in milliseconds. Negative means "
 "indefinitely. Default is 5 minutes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:174
+#: i2p2www/pages/site/docs/api/streaming.html:190
 msgid ""
 "Whether to disable warnings in the logs when an incoming connection is "
 "rejected due to connection limits."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:180
+#: i2p2www/pages/site/docs/api/streaming.html:196
 msgid ""
 "Whether to listen only for the streaming protocol.\n"
 "Setting to true will prohibit communication with Destinations earlier "
@@ -9222,77 +3626,89 @@ msgid ""
 "Destination."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:188
+#: i2p2www/pages/site/docs/api/streaming.html:204
 msgid ""
 "(0=noop, 1=disconnect)\n"
 "What to do on an inactivity timeout - do nothing, disconnect, or send a "
 "duplicate ack."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:196
+#: i2p2www/pages/site/docs/api/streaming.html:212
 msgid ""
 "The initial value of the resend delay field in the packet header, times "
 "1000.\n"
 "Not fully implemented; see below."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:201
-#: i2p2www/pages/site/docs/api/streaming.html:203
+#: i2p2www/pages/site/docs/api/streaming.html:217
+msgid ""
+"Initial timeout\n"
+"(if no sharing data available)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:224
+msgid ""
+"Initial round trip time estimate\n"
+"(if no sharing data available).\n"
+"Disabled as of release 0.9.8; uses actual RTT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
 msgid "if no sharing data available"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:203
+#: i2p2www/pages/site/docs/api/streaming.html:230
 msgid ""
 "In standard TCP, window sizes are in bytes, while in I2P, window sizes "
 "are in messages."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:207
+#: i2p2www/pages/site/docs/api/streaming.html:242
 msgid ""
 "(0 or negative value means unlimited)\n"
 "This is a total limit for incoming and outgoing combined."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:212
+#: i2p2www/pages/site/docs/api/streaming.html:247
 msgid "Incoming connection limit (per peer; 0 means disabled)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:218
-#: i2p2www/pages/site/docs/api/streaming.html:224
+#: i2p2www/pages/site/docs/api/streaming.html:253
+#: i2p2www/pages/site/docs/api/streaming.html:259
 msgid "(per peer; 0 means disabled)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:230
+#: i2p2www/pages/site/docs/api/streaming.html:265
 msgid "The MTU in bytes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:234
+#: i2p2www/pages/site/docs/api/streaming.html:269
 msgid "Maximum number of retransmissions before failure."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:238
+#: i2p2www/pages/site/docs/api/streaming.html:273
 msgid "Incoming connection limit (all peers; 0 means disabled)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:244
-#: i2p2www/pages/site/docs/api/streaming.html:251
+#: i2p2www/pages/site/docs/api/streaming.html:279
+#: i2p2www/pages/site/docs/api/streaming.html:286
 msgid ""
 "(all peers; 0 means disabled)\n"
 "Use with caution as exceeding this will disable a server for a long time."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:260
+#: i2p2www/pages/site/docs/api/streaming.html:295
 msgid ""
 "(2=interactive not supported)\n"
 "This doesn't currently do anything, but setting it to a value other than "
 "1 will cause an error."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:265
+#: i2p2www/pages/site/docs/api/streaming.html:300
 msgid "How long to block on read, in milliseconds. Negative means indefinitely."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:269
+#: i2p2www/pages/site/docs/api/streaming.html:304
 msgid ""
 "When we're in slow start, we grow the window size at the rate\n"
 "of 1/(factor).  In standard TCP, window sizes are in bytes,\n"
@@ -9300,26 +3716,38 @@ msgid ""
 "A higher number means slower growth."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:276
+#: i2p2www/pages/site/docs/api/streaming.html:311
+#: i2p2www/pages/site/docs/api/streaming.html:318
+#: i2p2www/pages/site/docs/api/streaming.html:325
+msgid ""
+"Ref: RFC 2140. Floating point value.\n"
+"May be set only via context properties, not connection options."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:332
 msgid ""
 "How long to block on write/flush, in milliseconds. Negative means "
 "indefinitely."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:284
+#: i2p2www/pages/site/docs/api/streaming.html:340
 #: i2p2www/pages/site/docs/spec/streaming.html:10
 msgid "Protocol Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:286
+#: i2p2www/pages/site/docs/api/streaming.html:342
 msgid "See the Streaming Library Specification page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:290
+#: i2p2www/pages/site/docs/api/streaming.html:346
 msgid "Implementation Details"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:293
+#: i2p2www/pages/site/docs/api/streaming.html:348
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:349
 msgid ""
 "The initiator sends a packet with the SYNCHRONIZE flag set. This packet "
 "may contain the initial data as well.\n"
@@ -9327,7 +3755,7 @@ msgid ""
 " may contain the initial response data as well."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:298
+#: i2p2www/pages/site/docs/api/streaming.html:354
 msgid ""
 "The initiator may send additional data packets, up to the initial window "
 "size, before receiving the SYNCHRONIZE response.\n"
@@ -9337,11 +3765,11 @@ msgid ""
 "arrive out of order, in advance of the SYNCHRONIZE packet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:305
+#: i2p2www/pages/site/docs/api/streaming.html:361
 msgid "MTU Selection and Negotiation"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:306
+#: i2p2www/pages/site/docs/api/streaming.html:362
 msgid ""
 "The maximum message size (also called the MTU / MRU) is negotiated to the"
 " lower value supported by\n"
@@ -9354,7 +3782,7 @@ msgid ""
 "including overhead for the typical case."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:315
+#: i2p2www/pages/site/docs/api/streaming.html:371
 msgid ""
 "The first message in a connection includes a 387 byte (typical) "
 "Destination added by the streaming layer,\n"
@@ -9372,7 +3800,7 @@ msgid ""
 "connections."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:326
+#: i2p2www/pages/site/docs/api/streaming.html:382
 #, python-format
 msgid ""
 "Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
@@ -9380,7 +3808,7 @@ msgid ""
 "There is no checksum field in the streaming protocol."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:334
+#: i2p2www/pages/site/docs/api/streaming.html:390
 #, python-format
 msgid ""
 "Each packet is sent through I2P as a single message (or as an individual "
@@ -9394,11 +3822,11 @@ msgid ""
 "mechanism or payload length field in the streaming protocol."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:344
+#: i2p2www/pages/site/docs/api/streaming.html:400
 msgid "Windowing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:345
+#: i2p2www/pages/site/docs/api/streaming.html:401
 msgid ""
 "The streaming lib uses standard slow-start (exponential window growth) "
 "and congestion avoidance (linear window growth)\n"
@@ -9406,11 +3834,11 @@ msgid ""
 "Windowing and acknowledgments use packet count, not byte count."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:352
+#: i2p2www/pages/site/docs/api/streaming.html:408
 msgid "Close"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:353
+#: i2p2www/pages/site/docs/api/streaming.html:409
 msgid ""
 "Any packet, including one with the SYNCHRONIZE flag set, may have the "
 "CLOSE flag sent as well.\n"
@@ -9419,15 +3847,50 @@ msgid ""
 "CLOSE packets may contain data as well."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:360
+#: i2p2www/pages/site/docs/api/streaming.html:417
+msgid ""
+"There is no ping function at the I2CP layer (equivalent to ICMP echo) or "
+"in datagrams.\n"
+"This function is provided in streaming.\n"
+"Pings and pongs may not be combined with a standard streaming packet;\n"
+"if the ECHO option is set, then\n"
+"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. "
+"are ignored."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:425
+msgid ""
+"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED "
+"flags set.\n"
+"The sendStreamId must be greater than zero, and the receiveStreamId is "
+"ignored.\n"
+"The sendStreamId may or may not correspond to an existing connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:431
+msgid ""
+"A pong packet must have the ECHO flag set.\n"
+"The sendStreamId must be zero, and the receiveStreamId is the "
+"sendStreamId from the ping.\n"
+"The pong packet does not include any payload that was contained in the "
+"ping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:437
+msgid ""
+"Streaming may be configured to disable sending pongs with the "
+"configuration i2p.streaming.answerPings=false."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:442
 msgid "Control Block Sharing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:361
+#: i2p2www/pages/site/docs/api/streaming.html:443
 msgid ""
 "The streaming lib supports \"TCP\" Control Block sharing.\n"
-"This shares two important streaming lib parameters\n"
-"(window size and round trip time)\n"
+"This shares three important streaming lib parameters\n"
+"(window size, round trip time, round trip time variance)\n"
 "across connections to the same remote peer.\n"
 "This is used for \"temporal\" sharing at connection open/close time,\n"
 "not \"ensemble\" sharing during a connection (See\n"
@@ -9436,25 +3899,26 @@ msgid ""
 "Destination)\n"
 "so that there is no information leakage to other Destinations on the\n"
 "same router.\n"
-"The share data for a given peer expires after a few minutes."
+"The share data for a given peer expires after a few minutes.\n"
+"The following Control Block Sharing parameters can be set per router:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:375
+#: i2p2www/pages/site/docs/api/streaming.html:464
 msgid "Other Parameters"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:376
+#: i2p2www/pages/site/docs/api/streaming.html:465
 msgid ""
 "The following parameters are hardcoded, but may be of interest for "
 "analysis:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:393
-#: i2p2www/pages/site/docs/how/network-database.html:831
+#: i2p2www/pages/site/docs/api/streaming.html:484
+#: i2p2www/pages/site/docs/how/network-database.html:843
 msgid "History"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:394
+#: i2p2www/pages/site/docs/api/streaming.html:485
 msgid ""
 "The streaming library has grown organically for I2P - first mihi "
 "implemented the\n"
@@ -9477,33 +3941,33 @@ msgid ""
 "messages."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:408
+#: i2p2www/pages/site/docs/api/streaming.html:499
 #: i2p2www/pages/site/docs/how/elgamal-aes.html:331
 #: i2p2www/pages/site/docs/how/garlic-routing.html:242
-#: i2p2www/pages/site/docs/how/network-database.html:836
+#: i2p2www/pages/site/docs/how/network-database.html:848
 #: i2p2www/pages/site/docs/how/peer-selection.html:265
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:255
-#: i2p2www/pages/site/docs/protocol/i2cp.html:646
+#: i2p2www/pages/site/docs/protocol/i2cp.html:654
 #: i2p2www/pages/site/docs/protocol/i2np.html:227
-#: i2p2www/pages/site/docs/spec/updates.html:222
-#: i2p2www/pages/site/docs/transport/ntcp.html:443
-#: i2p2www/pages/site/docs/transport/ssu.html:502
+#: i2p2www/pages/site/docs/spec/updates.html:280
+#: i2p2www/pages/site/docs/transport/ntcp.html:446
+#: i2p2www/pages/site/docs/transport/ssu.html:506
 #: i2p2www/pages/site/docs/tunnels/implementation.html:503
 msgid "Future Work"
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:409
+#: i2p2www/pages/site/docs/api/streaming.html:500
 msgid ""
 "The behavior of the streaming library has a profound impact on\n"
 "application-level performance, and as such, is an important\n"
 "area for further analysis."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:415
+#: i2p2www/pages/site/docs/api/streaming.html:506
 msgid "Additional tuning of the streaming lib parameters may be necessary."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:418
+#: i2p2www/pages/site/docs/api/streaming.html:509
 #, python-format
 msgid ""
 "Another area for research is the interaction of the streaming lib with "
@@ -9512,7 +3976,7 @@ msgid ""
 "See the NTCP discussion page for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:423
+#: i2p2www/pages/site/docs/api/streaming.html:514
 msgid ""
 "The interaction of the routing algorithms with the streaming lib strongly"
 " affects performance.\n"
@@ -9527,32 +3991,32 @@ msgid ""
 "improvements."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:433
+#: i2p2www/pages/site/docs/api/streaming.html:524
 msgid "The data in the first SYN packet may exceed the receiver's MTU."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:436
+#: i2p2www/pages/site/docs/api/streaming.html:527
 msgid "The DELAY_REQUESTED field could be used more."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:439
+#: i2p2www/pages/site/docs/api/streaming.html:530
 msgid ""
 "Duplicate initial SYNCHRONIZE packets on short-lived streams may not be "
 "recognized and removed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:442
+#: i2p2www/pages/site/docs/api/streaming.html:533
 msgid "Don't send the MTU in a retransmission."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:445
+#: i2p2www/pages/site/docs/api/streaming.html:536
 msgid ""
 "Data is sent along unless the outbound window is full.\n"
 "(i.e. no-Nagle or TCP_NODELAY)\n"
 "Probably should have a configuration option for this."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:450
+#: i2p2www/pages/site/docs/api/streaming.html:541
 msgid ""
 "zzz has added debug code to the streaming library to log packets in a "
 "wireshark-compatible\n"
@@ -9561,7 +4025,7 @@ msgid ""
 "to TCP fields."
 msgstr ""
 
-#: i2p2www/pages/site/docs/api/streaming.html:455
+#: i2p2www/pages/site/docs/api/streaming.html:546
 msgid ""
 "There are proposals to replace the streaming lib with standard TCP\n"
 "(or perhaps a null layer together with raw sockets).\n"
@@ -9718,7 +4182,7 @@ msgstr ""
 msgid ""
 "While compact response support is optional for both clients and trackers,"
 " it is highly\n"
-"recommended as it reduces the nominal response size by over 90%."
+"recommended as it reduces the nominal response size by over 90%."
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/bittorrent.html:116
@@ -10011,82 +4475,82 @@ msgid "Email"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:26
-#: i2p2www/pages/site/docs/applications/supported.html:315
+#: i2p2www/pages/site/docs/applications/supported.html:328
 msgid "File Sharing"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:29
-#: i2p2www/pages/site/docs/applications/supported.html:317
+#: i2p2www/pages/site/docs/applications/supported.html:330
 msgid "BitTorrent clients"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:31
-#: i2p2www/pages/site/docs/applications/supported.html:359
+#: i2p2www/pages/site/docs/applications/supported.html:372
 msgid "BitTorrent trackers and indexers"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:40
-#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:439
 msgid "Network Administration"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:43
-#: i2p2www/pages/site/docs/applications/supported.html:428
+#: i2p2www/pages/site/docs/applications/supported.html:441
 msgid "General-purpose socket utilities"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:50
-#: i2p2www/pages/site/docs/applications/supported.html:469
+#: i2p2www/pages/site/docs/applications/supported.html:482
 msgid "Real-time Chat"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:53
-#: i2p2www/pages/site/docs/applications/supported.html:471
+#: i2p2www/pages/site/docs/applications/supported.html:484
 msgid "Instant messaging clients"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:55
-#: i2p2www/pages/site/docs/applications/supported.html:481
+#: i2p2www/pages/site/docs/applications/supported.html:494
 msgid "IRC clients"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:57
-#: i2p2www/pages/site/docs/applications/supported.html:532
+#: i2p2www/pages/site/docs/applications/supported.html:545
 msgid "IRC servers"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:62
-#: i2p2www/pages/site/docs/applications/supported.html:548
+#: i2p2www/pages/site/docs/applications/supported.html:561
 msgid "Web Browsing"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:65
-#: i2p2www/pages/site/docs/applications/supported.html:550
+#: i2p2www/pages/site/docs/applications/supported.html:563
 msgid "Anonymous websites"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:67
-#: i2p2www/pages/site/docs/applications/supported.html:599
+#: i2p2www/pages/site/docs/applications/supported.html:612
 msgid "Proxy software"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:69
-#: i2p2www/pages/site/docs/applications/supported.html:624
+#: i2p2www/pages/site/docs/applications/supported.html:637
 msgid "Inproxies"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:71
-#: i2p2www/pages/site/docs/applications/supported.html:640
+#: i2p2www/pages/site/docs/applications/supported.html:669
 msgid "Outproxies"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:76
-#: i2p2www/pages/site/docs/applications/supported.html:654
+#: i2p2www/pages/site/docs/applications/supported.html:683
 msgid "Website Hosting"
 msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:79
-#: i2p2www/pages/site/docs/applications/supported.html:669
+#: i2p2www/pages/site/docs/applications/supported.html:698
 msgid "Web servers"
 msgstr ""
 
@@ -10095,8 +4559,7 @@ msgstr ""
 msgid ""
 "This is intended to be a comprehensive listing of applications used with\n"
 "I2P. If you know of something that's missing please submit a ticket on\n"
-"Trac, and be sure to select the"
-"\n"
+"Trac, and be sure to select the\n"
 "“www” component in the submission form."
 msgstr ""
 
@@ -10109,8 +4572,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:97
 #: i2p2www/pages/site/docs/applications/supported.html:279
 #: i2p2www/pages/site/docs/applications/supported.html:311
-#: i2p2www/pages/site/docs/applications/supported.html:323
-#: i2p2www/pages/site/docs/applications/supported.html:666
+#: i2p2www/pages/site/docs/applications/supported.html:336
+#: i2p2www/pages/site/docs/applications/supported.html:695
 msgid "bundled"
 msgstr ""
 
@@ -10128,10 +4591,10 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:228
 #: i2p2www/pages/site/docs/applications/supported.html:241
 #: i2p2www/pages/site/docs/applications/supported.html:292
-#: i2p2www/pages/site/docs/applications/supported.html:391
-#: i2p2www/pages/site/docs/applications/supported.html:413
-#: i2p2www/pages/site/docs/applications/supported.html:422
-#: i2p2www/pages/site/docs/applications/supported.html:510
+#: i2p2www/pages/site/docs/applications/supported.html:404
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:523
 msgid "plugin"
 msgstr ""
 
@@ -10151,30 +4614,31 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:241
 #: i2p2www/pages/site/docs/applications/supported.html:252
 #: i2p2www/pages/site/docs/applications/supported.html:261
-#: i2p2www/pages/site/docs/applications/supported.html:329
-#: i2p2www/pages/site/docs/applications/supported.html:340
-#: i2p2www/pages/site/docs/applications/supported.html:355
-#: i2p2www/pages/site/docs/applications/supported.html:401
-#: i2p2www/pages/site/docs/applications/supported.html:413
-#: i2p2www/pages/site/docs/applications/supported.html:422
-#: i2p2www/pages/site/docs/applications/supported.html:437
-#: i2p2www/pages/site/docs/applications/supported.html:443
-#: i2p2www/pages/site/docs/applications/supported.html:449
-#: i2p2www/pages/site/docs/applications/supported.html:459
-#: i2p2www/pages/site/docs/applications/supported.html:465
-#: i2p2www/pages/site/docs/applications/supported.html:477
-#: i2p2www/pages/site/docs/applications/supported.html:510
-#: i2p2www/pages/site/docs/applications/supported.html:516
-#: i2p2www/pages/site/docs/applications/supported.html:522
-#: i2p2www/pages/site/docs/applications/supported.html:528
-#: i2p2www/pages/site/docs/applications/supported.html:605
-#: i2p2www/pages/site/docs/applications/supported.html:614
-#: i2p2www/pages/site/docs/applications/supported.html:620
-#: i2p2www/pages/site/docs/applications/supported.html:666
-#: i2p2www/pages/site/docs/applications/supported.html:681
-#: i2p2www/pages/site/docs/applications/supported.html:687
-#: i2p2www/pages/site/docs/applications/supported.html:693
-#: i2p2www/pages/site/docs/applications/supported.html:699
+#: i2p2www/pages/site/docs/applications/supported.html:324
+#: i2p2www/pages/site/docs/applications/supported.html:342
+#: i2p2www/pages/site/docs/applications/supported.html:353
+#: i2p2www/pages/site/docs/applications/supported.html:368
+#: i2p2www/pages/site/docs/applications/supported.html:414
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:450
+#: i2p2www/pages/site/docs/applications/supported.html:456
+#: i2p2www/pages/site/docs/applications/supported.html:462
+#: i2p2www/pages/site/docs/applications/supported.html:472
+#: i2p2www/pages/site/docs/applications/supported.html:478
+#: i2p2www/pages/site/docs/applications/supported.html:490
+#: i2p2www/pages/site/docs/applications/supported.html:523
+#: i2p2www/pages/site/docs/applications/supported.html:529
+#: i2p2www/pages/site/docs/applications/supported.html:535
+#: i2p2www/pages/site/docs/applications/supported.html:541
+#: i2p2www/pages/site/docs/applications/supported.html:618
+#: i2p2www/pages/site/docs/applications/supported.html:627
+#: i2p2www/pages/site/docs/applications/supported.html:633
+#: i2p2www/pages/site/docs/applications/supported.html:695
+#: i2p2www/pages/site/docs/applications/supported.html:710
+#: i2p2www/pages/site/docs/applications/supported.html:716
+#: i2p2www/pages/site/docs/applications/supported.html:722
+#: i2p2www/pages/site/docs/applications/supported.html:728
 msgid "standalone"
 msgstr ""
 
@@ -10183,11 +4647,11 @@ msgstr ""
 #: i2p2www/pages/site/docs/applications/supported.html:202
 #: i2p2www/pages/site/docs/applications/supported.html:208
 #: i2p2www/pages/site/docs/applications/supported.html:214
-#: i2p2www/pages/site/docs/applications/supported.html:349
-#: i2p2www/pages/site/docs/applications/supported.html:373
-#: i2p2www/pages/site/docs/applications/supported.html:382
-#: i2p2www/pages/site/docs/applications/supported.html:538
-#: i2p2www/pages/site/docs/applications/supported.html:544
+#: i2p2www/pages/site/docs/applications/supported.html:362
+#: i2p2www/pages/site/docs/applications/supported.html:386
+#: i2p2www/pages/site/docs/applications/supported.html:395
+#: i2p2www/pages/site/docs/applications/supported.html:551
+#: i2p2www/pages/site/docs/applications/supported.html:557
 msgid "standalone/mod"
 msgstr ""
 
@@ -10204,14 +4668,16 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:135
 #: i2p2www/pages/site/docs/applications/supported.html:302
-#: i2p2www/pages/site/docs/applications/supported.html:558
-#: i2p2www/pages/site/docs/applications/supported.html:568
-#: i2p2www/pages/site/docs/applications/supported.html:577
-#: i2p2www/pages/site/docs/applications/supported.html:583
-#: i2p2www/pages/site/docs/applications/supported.html:589
-#: i2p2www/pages/site/docs/applications/supported.html:595
-#: i2p2www/pages/site/docs/applications/supported.html:636
-#: i2p2www/pages/site/docs/applications/supported.html:650
+#: i2p2www/pages/site/docs/applications/supported.html:571
+#: i2p2www/pages/site/docs/applications/supported.html:581
+#: i2p2www/pages/site/docs/applications/supported.html:590
+#: i2p2www/pages/site/docs/applications/supported.html:596
+#: i2p2www/pages/site/docs/applications/supported.html:602
+#: i2p2www/pages/site/docs/applications/supported.html:608
+#: i2p2www/pages/site/docs/applications/supported.html:649
+#: i2p2www/pages/site/docs/applications/supported.html:657
+#: i2p2www/pages/site/docs/applications/supported.html:665
+#: i2p2www/pages/site/docs/applications/supported.html:679
 msgid "service"
 msgstr ""
 
@@ -10227,7 +4693,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/applications/supported.html:148
 #: i2p2www/pages/site/docs/applications/supported.html:220
-#: i2p2www/pages/site/docs/applications/supported.html:355
+#: i2p2www/pages/site/docs/applications/supported.html:368
 msgid "unmaintained"
 msgstr ""
 
@@ -10355,15 +4821,24 @@ msgid ""
 "email service by default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:322
+#: i2p2www/pages/site/docs/applications/supported.html:316
+#, python-format
+msgid ""
+"Can be configured to use Postman's email service. See\n"
+"this comparison of MUAs,\n"
+"and configuration settings for\n"
+"SMTP and POP3."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:335
 msgid "I2P's integrated BitTorrent client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:328
+#: i2p2www/pages/site/docs/applications/supported.html:341
 msgid "Modified version of I2PSnark."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:334
+#: i2p2www/pages/site/docs/applications/supported.html:347
 msgid ""
 "\n"
 "A fork of rufus that uses the Basic Open Bridge (BOB) and has many\n"
@@ -10372,49 +4847,49 @@ msgid ""
 "magnet-link like fetching of torrents within I2P.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:345
+#: i2p2www/pages/site/docs/applications/supported.html:358
 msgid ""
 "Clean, full-featured cross-platform BitTorrent client with official\n"
 "ports for several GUI toolkits."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:354
+#: i2p2www/pages/site/docs/applications/supported.html:367
 msgid "Has a plugin providing I2P support."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:361
+#: i2p2www/pages/site/docs/applications/supported.html:374
 #, python-format
 msgid ""
 "For a detailed feature comparison of I2P-enabled trackers/indexers, see\n"
 "here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:369
+#: i2p2www/pages/site/docs/applications/supported.html:382
 msgid ""
 "The code that powered one of the first major tracker/indexer sites on the"
 "\n"
 "Internet. Patched for I2P."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:378
+#: i2p2www/pages/site/docs/applications/supported.html:391
 #, python-format
 msgid ""
 "Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n"
 "branch of the I2P Monotone repository."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:387
+#: i2p2www/pages/site/docs/applications/supported.html:400
 #, python-format
 msgid ""
 "zzz's Java-based open tracker. More info\n"
 "here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:400
+#: i2p2www/pages/site/docs/applications/supported.html:413
 msgid "I2P port of the aMule ED2K client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:409
+#: i2p2www/pages/site/docs/applications/supported.html:422
 #, python-format
 msgid ""
 "Port of the Phex Gnutella "
@@ -10422,44 +4897,44 @@ msgid ""
 "for plugin version here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:418
+#: i2p2www/pages/site/docs/applications/supported.html:431
 #, python-format
 msgid ""
 "Cache for Gnutella peers on I2P. Website for plugin version\n"
 "here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:433
+#: i2p2www/pages/site/docs/applications/supported.html:446
 msgid ""
 "Unix standard tool for socket relaying. Several clones, ports, and forks\n"
 "have appeared over the years."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:442
+#: i2p2www/pages/site/docs/applications/supported.html:455
 msgid "Like netcat but more powerful."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:448
+#: i2p2www/pages/site/docs/applications/supported.html:461
 msgid ""
 "Proxy providing simple, transparent SOCKS-ification of network "
 "applications."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:458
+#: i2p2www/pages/site/docs/applications/supported.html:471
 msgid ""
 "Most popular implementation of the Secure Shell (SSH) protocol and "
 "related tools."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:464
+#: i2p2www/pages/site/docs/applications/supported.html:477
 msgid "Open source Secure Shell (SSH) client for Windows."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:476
+#: i2p2www/pages/site/docs/applications/supported.html:489
 msgid "IM client with multiple incarnations."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:483
+#: i2p2www/pages/site/docs/applications/supported.html:496
 msgid ""
 "Many IRC clients leak identifying information to servers or other\n"
 "clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound"
@@ -10476,7 +4951,7 @@ msgid ""
 "/me command) which isn't inherently dangerous."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:494
+#: i2p2www/pages/site/docs/applications/supported.html:507
 msgid ""
 "I2P's IRC filtering may not cover every possible leak — users should also"
 "\n"
@@ -10489,100 +4964,105 @@ msgid ""
 "developers; they may be able to solve it via additional filtering."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:506
+#: i2p2www/pages/site/docs/applications/supported.html:519
 #, python-format
 msgid ""
 "Small Java-based IRC client. Plugin available here."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:515
+#: i2p2www/pages/site/docs/applications/supported.html:528
 msgid "Cross-platform graphical IRC client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:521
+#: i2p2www/pages/site/docs/applications/supported.html:534
 msgid "Unixy terminal-based IRC client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:527
+#: i2p2www/pages/site/docs/applications/supported.html:540
 msgid "Another Unixy terminal-based IRC client."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:537
+#: i2p2www/pages/site/docs/applications/supported.html:550
 msgid "IRC server developed from scratch."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:543
+#: i2p2www/pages/site/docs/applications/supported.html:556
 msgid "Most popular IRC server."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:555
+#: i2p2www/pages/site/docs/applications/supported.html:568
 msgid ""
 "Any website hosted anonymously on I2P, reachable through the I2P router's"
 " HTTP proxy."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:563
+#: i2p2www/pages/site/docs/applications/supported.html:576
 msgid ""
 "Distributed anonymous websites hosted\n"
 "using Tahoe-LAFS-I2P, currently only reachable with Tahoe-LAFS-I2P\n"
 "clients or through the Tahoe-LAFS-I2P HTTP proxy."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:573
+#: i2p2www/pages/site/docs/applications/supported.html:586
 #, python-format
 msgid ""
 "Website for sponge's jump service.\n"
 "Source code available."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:582
+#: i2p2www/pages/site/docs/applications/supported.html:595
 msgid "Another jump service."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:588
+#: i2p2www/pages/site/docs/applications/supported.html:601
 msgid "Dynamically updated eepsite index."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:594
+#: i2p2www/pages/site/docs/applications/supported.html:607
 #, python-format
 msgid "Website for zzz's jump service."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:604
+#: i2p2www/pages/site/docs/applications/supported.html:617
 msgid "SOCKS-enabled caching web proxy with basic filtering capabilities."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:610
+#: i2p2www/pages/site/docs/applications/supported.html:623
 msgid ""
 "Privacy-focused non-caching web proxy with advanced filtering\n"
 "capabilities. Excels at removing ads and other junk."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:619
+#: i2p2www/pages/site/docs/applications/supported.html:632
 msgid "Venerable caching web proxy."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:626
+#: i2p2www/pages/site/docs/applications/supported.html:639
 msgid "Gateways allowing users on the public Internet to access eepsites."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:633
+#: i2p2www/pages/site/docs/applications/supported.html:646
 #, python-format
 msgid "tino's inproxy on the public Internet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:642
+#: i2p2www/pages/site/docs/applications/supported.html:654
+#: i2p2www/pages/site/docs/applications/supported.html:662
+msgid "Another inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:671
 msgid ""
 "Gateways allowing I2P users to access content hosted on the public "
 "Internet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:649
+#: i2p2www/pages/site/docs/applications/supported.html:678
 msgid "Publicly advertised outproxy running Squid, located in Germany."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:659
+#: i2p2www/pages/site/docs/applications/supported.html:688
 msgid ""
 "Lightweight web server and Java servlet container. I2P is tightly\n"
 "integrated with a bundled copy of Jetty which by default is configured to"
@@ -10594,26 +5074,26 @@ msgid ""
 "I2P."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:671
+#: i2p2www/pages/site/docs/applications/supported.html:700
 msgid ""
 "In addition to Jetty, any web server should function over I2P without\n"
 "modification so long as it's HTTP-compliant. Some web servers known to\n"
 "currently serve content on the I2P network are:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:680
+#: i2p2www/pages/site/docs/applications/supported.html:709
 msgid "Most popular web server on the public WWW."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:686
+#: i2p2www/pages/site/docs/applications/supported.html:715
 msgid "Web server and Java servlet container. More features than Jetty."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:692
+#: i2p2www/pages/site/docs/applications/supported.html:721
 msgid "Fast lightweight web server."
 msgstr ""
 
-#: i2p2www/pages/site/docs/applications/supported.html:698
+#: i2p2www/pages/site/docs/applications/supported.html:727
 msgid "High-performance lightweight web server."
 msgstr ""
 
@@ -11113,7 +5593,7 @@ msgid ""
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/cryptography.html:34
-#: i2p2www/pages/site/docs/how/cryptography.html:189
+#: i2p2www/pages/site/docs/how/cryptography.html:198
 #, python-format
 msgid ""
 "For encryption of some netDb stores and "
@@ -11194,19 +5674,25 @@ msgstr ""
 msgid ""
 "While the standard exponent size is 2048 bits (256 bytes) and the I2P\n"
 "PrivateKey\n"
-"is a full 256 bytes,\n"
-"we use the short exponent size of 226 bits (28.25 bytes).\n"
+"is a full 256 bytes, in some cases\n"
+"we use the short exponent size of 226 bits (28.25 bytes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:150
+#, python-format
+msgid ""
 "This should be safe for use with the Oakley primes, per\n"
 "On Diffie-Hellman Key Agreement with Short Exponents "
 "- van Oorschot, Weiner\n"
 "at EuroCrypt 96, and crypto++'s "
 "benchmarks.\n"
-"Benchmarks originally at %(oldbenchmarks)s (now dead),\n"
+"Benchmarks originally at this link, now dead,\n"
 "rescued from the wayback machine,"
 " dated Apr 23, 2008."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:158
+#: i2p2www/pages/site/docs/how/cryptography.html:160
 #, python-format
 msgid ""
 "Also, Koshiba & Kurosawa: Short Exponent Diffie-"
@@ -11217,36 +5703,46 @@ msgid ""
 "The remainder of the PrivateKey is padded with zeroes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:167
-#: i2p2www/pages/site/docs/how/cryptography.html:264
-#: i2p2www/pages/site/docs/how/cryptography.html:343
-#: i2p2www/pages/site/docs/how/cryptography.html:382
+#: i2p2www/pages/site/docs/how/cryptography.html:169
+msgid ""
+"Prior to release 0.9.8, all routers used the short exponent.\n"
+"As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent.\n"
+"Other routers continue to use the short exponent due to concerns about "
+"processor load.\n"
+"The transition to a longer exponent for these platforms is a topic for "
+"further study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:176
+#: i2p2www/pages/site/docs/how/cryptography.html:273
+#: i2p2www/pages/site/docs/how/cryptography.html:352
+#: i2p2www/pages/site/docs/how/cryptography.html:391
 msgid "Obsolescence"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:168
+#: i2p2www/pages/site/docs/how/cryptography.html:177
 msgid ""
 "The vulnerability of the network to an ElGamal attack and the impact of "
 "transitioning to a longer bit length is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:176
+#: i2p2www/pages/site/docs/how/cryptography.html:185
 msgid "AES is used for symmetric encryption, in several cases:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:181
+#: i2p2www/pages/site/docs/how/cryptography.html:190
 msgid "For transport encryption after DH key exchange"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:185
+#: i2p2www/pages/site/docs/how/cryptography.html:194
 #, python-format
 msgid ""
 "For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:195
+#: i2p2www/pages/site/docs/how/cryptography.html:204
 #, python-format
 msgid ""
 "For encryption of periodic tunnel "
@@ -11254,7 +5750,7 @@ msgid ""
 "tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:200
+#: i2p2www/pages/site/docs/how/cryptography.html:209
 #, python-format
 msgid ""
 "We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n"
@@ -11269,27 +5765,27 @@ msgid ""
 "ElGamalAESEngine.getPadding function."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:265
+#: i2p2www/pages/site/docs/how/cryptography.html:274
 msgid ""
 "The vulnerability of the network to an AES attack and the impact of "
 "transitioning to a longer bit length is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:270
-#: i2p2www/pages/site/docs/how/cryptography.html:362
-#: i2p2www/pages/site/docs/how/cryptography.html:388
-#: i2p2www/pages/site/docs/how/cryptography.html:456
+#: i2p2www/pages/site/docs/how/cryptography.html:279
+#: i2p2www/pages/site/docs/how/cryptography.html:371
+#: i2p2www/pages/site/docs/how/cryptography.html:397
+#: i2p2www/pages/site/docs/how/cryptography.html:465
 #: i2p2www/pages/site/docs/how/garlic-routing.html:281
 #: i2p2www/pages/site/docs/how/peer-selection.html:296
 msgid "References"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:273
+#: i2p2www/pages/site/docs/how/cryptography.html:282
 msgid "Feb. 7, 2006 Status Notes"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:280
+#: i2p2www/pages/site/docs/how/cryptography.html:289
 #, python-format
 msgid ""
 "Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), "
@@ -11298,11 +5794,11 @@ msgid ""
 "DSA was chosen because it is much faster for signatures than ElGamal."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:286
+#: i2p2www/pages/site/docs/how/cryptography.html:295
 msgid "The DSA constants"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:337
+#: i2p2www/pages/site/docs/how/cryptography.html:346
 #, python-format
 msgid ""
 "The Signing Public"
@@ -11311,7 +5807,7 @@ msgid ""
 "Private Key is 160 bits."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:344
+#: i2p2www/pages/site/docs/how/cryptography.html:353
 #, python-format
 msgid ""
 "NIST 800-57\n"
@@ -11320,7 +5816,7 @@ msgid ""
 "given key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:350
+#: i2p2www/pages/site/docs/how/cryptography.html:359
 msgid ""
 "The prime number was chosen in 2003,\n"
 "and the person that chose the number (TheCrypto) is currently no longer "
@@ -11330,38 +5826,42 @@ msgid ""
 "prime, and we will document the construction process."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:357
+#: i2p2www/pages/site/docs/how/cryptography.html:366
 msgid ""
 "The vulnerability of the network to a DSA attack and the impact of "
 "transitioning to longer keys is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:365
-#: i2p2www/pages/site/docs/how/cryptography.html:367
+#: i2p2www/pages/site/docs/how/cryptography.html:374
+#: i2p2www/pages/site/docs/how/cryptography.html:376
 #, python-format
 msgid "Meeting %(num)s"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:369
+#: i2p2www/pages/site/docs/how/cryptography.html:378
 msgid "Choosing the constants"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:377
+#: i2p2www/pages/site/docs/how/cryptography.html:386
 #, python-format
 msgid ""
 "Hashes within I2P are plain old SHA256, as implemented in\n"
 "[SHA256Generator]"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:383
+#: i2p2www/pages/site/docs/how/cryptography.html:392
 msgid ""
 "The vulnerability of the network to a SHA-256 attack and the impact of "
 "transitioning to a longer hash is to be studied.\n"
 "It may be quite difficult to make any change backward-compatible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:395
+#: i2p2www/pages/site/docs/how/cryptography.html:403
+msgid "Transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:404
 msgid ""
 "At the lowest protocol layer,\n"
 "point-to-point inter-router communication is protected by the transport "
@@ -11377,11 +5877,11 @@ msgid ""
 "on the transport links."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:407
+#: i2p2www/pages/site/docs/how/cryptography.html:416
 msgid "NTCP connections"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:409
+#: i2p2www/pages/site/docs/how/cryptography.html:418
 #, python-format
 msgid ""
 "NTCP connections are negotiated with a 2048 Diffie-Hellman "
@@ -11398,35 +5898,35 @@ msgid ""
 "href=\"%(elgamalaes)s\">ElGamalAES+SessionTag does not."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:417
+#: i2p2www/pages/site/docs/how/cryptography.html:426
 msgid ""
 "In order to migrate to a more standardized implementation (TLS/SSL or "
 "even SSH), the following issues must be addressed:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:421
+#: i2p2www/pages/site/docs/how/cryptography.html:430
 msgid ""
 "Can we somehow reestablish sessions securely (ala session tags) or do we "
 "need to do full negotiation each time?"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:424
+#: i2p2www/pages/site/docs/how/cryptography.html:433
 msgid ""
 "Can we simplify/avoid the x509 or other certificate formats and use our "
 "own RouterInfo structure (which \n"
 "contains the ElGamal and DSA keys)?"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:429
+#: i2p2www/pages/site/docs/how/cryptography.html:438
 #, python-format
 msgid "See the NTCP specification for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:433
+#: i2p2www/pages/site/docs/how/cryptography.html:442
 msgid "UDP connections"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:434
+#: i2p2www/pages/site/docs/how/cryptography.html:443
 msgid ""
 "SSU (the UDP transport) encrypts each packet with AES256/CBC with both an"
 " explicit IV and MAC \n"
@@ -11439,12 +5939,12 @@ msgid ""
 "checking."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:442
+#: i2p2www/pages/site/docs/how/cryptography.html:451
 #, python-format
 msgid "See the SSU specification for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/cryptography.html:446
+#: i2p2www/pages/site/docs/how/cryptography.html:455
 #, python-format
 msgid ""
 "WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n"
@@ -12643,9 +7143,8 @@ msgid "The Network Database"
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/network-database.html:3
-#: i2p2www/pages/site/docs/protocol/i2np.html:3
-#: i2p2www/pages/site/docs/spec/common-structures.html:3
-msgid "June 2013"
+#: i2p2www/pages/site/docs/spec/updates.html:3
+msgid "October 2013"
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/network-database.html:8
@@ -12716,28 +7215,74 @@ msgid ""
 "approximate bandwidth, and perceived reachability"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/network-database.html:47
+msgid "SSU Testing"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/network-database.html:48
-msgid "The core library version, always the same as the router version"
+msgid "SSU Introducer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:49
+#: i2p2www/pages/site/docs/how/network-database.html:246
+msgid "Floodfill"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:50
+msgid "Hidden"
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/network-database.html:51
+#, python-format
+msgid "Under %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+#: i2p2www/pages/site/docs/how/network-database.html:53
+#: i2p2www/pages/site/docs/how/network-database.html:54
+#, python-format
+msgid "%(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+msgid "default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:55
+#, python-format
+msgid "Over %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:56
+msgid "Reachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:57
+msgid "Unreachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:62
+msgid "The core library version, always the same as the router version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:65
 msgid ""
 "Basic network compatibility - A router will refuse to communicate with a "
 "peer having a different netId"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:54
+#: i2p2www/pages/site/docs/how/network-database.html:68
 msgid "Used to determine compatibility with newer features and messages"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:57
+#: i2p2www/pages/site/docs/how/network-database.html:71
 msgid ""
 "Always sent as 90m, for compatibility with an older scheme where routers "
 "published their actual uptime,\n"
 "and only sent tunnel requests to peers whose was more than 60m"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:62
+#: i2p2www/pages/site/docs/how/network-database.html:76
 msgid ""
 "These values are used by other routers for basic decisions.\n"
 "Should we connect to this router? Should we attempt to route a tunnel "
@@ -12751,7 +7296,7 @@ msgid ""
 " and network analysis."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:72
+#: i2p2www/pages/site/docs/how/network-database.html:86
 #, python-format
 msgid ""
 "Additional text options include\n"
@@ -12766,15 +7311,15 @@ msgid ""
 "Current statistics are limited to:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:83
+#: i2p2www/pages/site/docs/how/network-database.html:97
 msgid "Client and exploratory tunnel build success, reject, and timeout rates"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:84
+#: i2p2www/pages/site/docs/how/network-database.html:98
 msgid "1 hour average number of participating tunnels"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:87
+#: i2p2www/pages/site/docs/how/network-database.html:101
 msgid ""
 "The data published can be seen in the router's user interface,\n"
 "but is not used or trusted within the router.\n"
@@ -12784,19 +7329,19 @@ msgid ""
 "releases."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:95
+#: i2p2www/pages/site/docs/how/network-database.html:109
 msgid "RouterInfo specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:98
+#: i2p2www/pages/site/docs/how/network-database.html:112
 msgid "RouterInfo Javadoc"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:101
+#: i2p2www/pages/site/docs/how/network-database.html:115
 msgid "RouterInfo Expiration"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:102
+#: i2p2www/pages/site/docs/how/network-database.html:116
 msgid ""
 "RouterInfos have no set expiration time.\n"
 "Each router is free to maintain its own local policy to trade off the "
@@ -12805,17 +7350,17 @@ msgid ""
 "In the current implementation, there are the following general policies:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:109
+#: i2p2www/pages/site/docs/how/network-database.html:123
 msgid ""
 "There is no expiration during the first hour of uptime, as the persistent"
 " stored data may be old."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:112
+#: i2p2www/pages/site/docs/how/network-database.html:126
 msgid "There is no expiration if there are 25 or less RouterInfos."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:115
+#: i2p2www/pages/site/docs/how/network-database.html:129
 msgid ""
 "As the number of local RouterInfos grows, the expiration time shrinks, in"
 " an attempt to maintain\n"
@@ -12824,7 +7369,7 @@ msgid ""
 "while expiration time with 300 routers is around 30 hours."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:120
+#: i2p2www/pages/site/docs/how/network-database.html:134
 #, python-format
 msgid ""
 "RouterInfos containing SSU introducers expire in "
@@ -12832,24 +7377,24 @@ msgid ""
 "the introducer list expires in about that time."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:124
+#: i2p2www/pages/site/docs/how/network-database.html:138
 msgid ""
 "Floodfills use a short expiration time (1 hour) for all local "
 "RouterInfos, as valid RouterInfos will\n"
 "be frequently republished to them."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:130
+#: i2p2www/pages/site/docs/how/network-database.html:144
 msgid "RouterInfo Persistent Storage"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:132
+#: i2p2www/pages/site/docs/how/network-database.html:146
 msgid ""
 "RouterInfos are periodically written to disk so that they are available "
 "after a restart."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:139
+#: i2p2www/pages/site/docs/how/network-database.html:153
 msgid ""
 "The second piece of data distributed in the netDb is a \"LeaseSet\" - "
 "documenting\n"
@@ -12858,73 +7403,73 @@ msgid ""
 "Each of these leases specify the following information:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:145
+#: i2p2www/pages/site/docs/how/network-database.html:159
 msgid "The tunnel gateway router (by specifying its identity)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:146
+#: i2p2www/pages/site/docs/how/network-database.html:160
 msgid "The tunnel ID on that router to send messages with (a 4 byte number)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:147
+#: i2p2www/pages/site/docs/how/network-database.html:161
 msgid "When that tunnel will expire."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:149
+#: i2p2www/pages/site/docs/how/network-database.html:163
 msgid ""
 "The LeaseSet itself is stored in the netDb under\n"
 "the key derived from the SHA256 of the destination."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:154
+#: i2p2www/pages/site/docs/how/network-database.html:168
 msgid "In addition to these leases, the LeaseSet includes:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:158
+#: i2p2www/pages/site/docs/how/network-database.html:172
 msgid ""
 "The destination itself (a 2048bit ElGamal encryption key, 1024bit DSA "
 "signing key and a certificate)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:159
+#: i2p2www/pages/site/docs/how/network-database.html:173
 msgid ""
 "Additional encryption public key: used for end-to-end encryption of "
 "garlic messages"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:160
+#: i2p2www/pages/site/docs/how/network-database.html:174
 msgid ""
 "Additional signing public key: intended for LeaseSet revocation, but is "
 "currently unused."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:161
+#: i2p2www/pages/site/docs/how/network-database.html:175
 msgid ""
 "Signature of all the LeaseSet data, to make sure the Destination "
 "published the LeaseSet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:165
+#: i2p2www/pages/site/docs/how/network-database.html:179
 msgid "Lease specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:167
+#: i2p2www/pages/site/docs/how/network-database.html:181
 msgid "LeaseSet specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:170
+#: i2p2www/pages/site/docs/how/network-database.html:184
 msgid "Lease Javadoc"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:172
+#: i2p2www/pages/site/docs/how/network-database.html:186
 msgid "LeaseSet Javadoc"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:176
+#: i2p2www/pages/site/docs/how/network-database.html:190
 msgid "Unpublished LeaseSets"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:177
+#: i2p2www/pages/site/docs/how/network-database.html:191
 msgid ""
 "A LeaseSet for a destination used only for outgoing connections is "
 "unpublished.\n"
@@ -12936,11 +7481,11 @@ msgid ""
 "because of I2NP storage messages."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:187
+#: i2p2www/pages/site/docs/how/network-database.html:201
 msgid "Revoked LeaseSets"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:188
+#: i2p2www/pages/site/docs/how/network-database.html:202
 msgid ""
 "A LeaseSet may be revoked by publishing a new LeaseSet with zero "
 "leases.\n"
@@ -12952,11 +7497,11 @@ msgid ""
 "unused."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:195
+#: i2p2www/pages/site/docs/how/network-database.html:209
 msgid "Encrypted LeaseSets"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:196
+#: i2p2www/pages/site/docs/how/network-database.html:210
 msgid ""
 "In an encrypted LeaseSet, all Leases are encrypted with a separate"
 " DSA key.\n"
@@ -12971,32 +7516,32 @@ msgid ""
 "LeaseSets could be improved."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:205
+#: i2p2www/pages/site/docs/how/network-database.html:219
 msgid "LeaseSet Expiration"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:206
+#: i2p2www/pages/site/docs/how/network-database.html:220
 msgid ""
 "All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet "
 "expires\n"
 "10 minutes after the earliest creation time of all its Leases."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:211
+#: i2p2www/pages/site/docs/how/network-database.html:225
 msgid "LeaseSet Persistent Storage"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:212
+#: i2p2www/pages/site/docs/how/network-database.html:226
 msgid ""
 "There is no persistent storage of LeaseSet data since they expire so "
 "quickly."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:217
+#: i2p2www/pages/site/docs/how/network-database.html:231
 msgid "Bootstrapping"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:218
+#: i2p2www/pages/site/docs/how/network-database.html:232
 msgid ""
 "The netDb is decentralized, however you do need at\n"
 "least one reference to a peer so that the integration process\n"
@@ -13017,11 +7562,7 @@ msgid ""
 "one of these URLs, selected at random."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:232
-msgid "Floodfill"
-msgstr ""
-
-#: i2p2www/pages/site/docs/how/network-database.html:233
+#: i2p2www/pages/site/docs/how/network-database.html:247
 msgid ""
 "The floodfill netDb is a simple distributed storage mechanism.\n"
 "The storage algorithm is simple: send the data to the closest peer that "
@@ -13040,24 +7581,24 @@ msgid ""
 "href=\"#kademlia_closeness\">XOR-metric) to a specific key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:244
+#: i2p2www/pages/site/docs/how/network-database.html:258
 msgid ""
 "Determining who is part of the floodfill netDb is trivial - it is exposed"
 " in each \n"
 "router's published routerInfo as a capability."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:249
+#: i2p2www/pages/site/docs/how/network-database.html:263
 msgid ""
 "Floodfills have no central authority and do not form a \"consensus\" -\n"
 "they only implement a simple DHT overlay."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:256
+#: i2p2www/pages/site/docs/how/network-database.html:270
 msgid "Floodfill Router Opt-in"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:258
+#: i2p2www/pages/site/docs/how/network-database.html:272
 msgid ""
 "Unlike Tor, where the directory servers are hardcoded and trusted,\n"
 "and operated by known entities,\n"
@@ -13065,7 +7606,7 @@ msgid ""
 "change over time."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:265
+#: i2p2www/pages/site/docs/how/network-database.html:279
 msgid ""
 "To increase reliability of the netDb, and minimize the impact\n"
 "of netDb traffic on a router, floodfill is automatically enabled\n"
@@ -13077,7 +7618,7 @@ msgid ""
 "KBytes/sec."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:275
+#: i2p2www/pages/site/docs/how/network-database.html:289
 msgid ""
 "In addition, a router must pass several additional tests for health\n"
 "(outbound message queue time, job lag, etc.) before floodfill operation "
@@ -13085,14 +7626,13 @@ msgid ""
 "automatically enabled."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:281
-#, python-format
+#: i2p2www/pages/site/docs/how/network-database.html:295
 msgid ""
-"With the current rules for automatic opt-in, approximately 6% of\n"
+"With the current rules for automatic opt-in, approximately 6% of\n"
 "the routers in the network are floodfill routers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:286
+#: i2p2www/pages/site/docs/how/network-database.html:300
 msgid ""
 "While some peers are manually configured to be floodfill,\n"
 "others are simply high-bandwidth routers who automatically volunteer\n"
@@ -13103,11 +7643,11 @@ msgid ""
 "too many floodfills outstanding."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:296
+#: i2p2www/pages/site/docs/how/network-database.html:310
 msgid "Floodfill Router Roles"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:297
+#: i2p2www/pages/site/docs/how/network-database.html:311
 msgid ""
 "A floodfill router's only services that are in addition to those of non-"
 "floodfill routers\n"
@@ -13118,11 +7658,11 @@ msgid ""
 "their distributed database services."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:305
+#: i2p2www/pages/site/docs/how/network-database.html:319
 msgid "Kademlia Closeness Metric"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:306
+#: i2p2www/pages/site/docs/how/network-database.html:320
 msgid ""
 "The netDb uses a simple Kademlia-style XOR metric to determine closeness."
 "\n"
@@ -13141,22 +7681,22 @@ msgid ""
 "although it isn't strictly a rotation."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:318
+#: i2p2www/pages/site/docs/how/network-database.html:332
 msgid ""
 "Routing keys are never sent on-the-wire in any I2NP message, they are "
 "only used locally for\n"
 "determination of distance."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:325
+#: i2p2www/pages/site/docs/how/network-database.html:339
 msgid "Storage, Verification, and Lookup Mechanics"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:327
+#: i2p2www/pages/site/docs/how/network-database.html:341
 msgid "RouterInfo Storage to Peers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:328
+#: i2p2www/pages/site/docs/how/network-database.html:342
 #, python-format
 msgid ""
 "I2NP DatabaseStoreMessages containing the local "
@@ -13165,11 +7705,11 @@ msgid ""
 "or SSU transport connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:335
+#: i2p2www/pages/site/docs/how/network-database.html:349
 msgid "LeaseSet Storage to Peers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:336
+#: i2p2www/pages/site/docs/how/network-database.html:350
 #, python-format
 msgid ""
 "I2NP DatabaseStoreMessages containing the local "
@@ -13182,7 +7722,7 @@ msgid ""
 "Destinations to have published LeaseSets at all."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:344
+#: i2p2www/pages/site/docs/how/network-database.html:358
 msgid ""
 "The DatabaseStoreMessage should be sent to the floodfill that is closest\n"
 "to the current routing key for the RouterInfo or LeaseSet being stored.\n"
@@ -13194,7 +7734,7 @@ msgid ""
 "This provides a high degree of fault-tolerance."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:353
+#: i2p2www/pages/site/docs/how/network-database.html:367
 msgid ""
 "In traditional Kademlia, a peer would do a \"find-closest\" search before"
 " inserting\n"
@@ -13215,11 +7755,11 @@ msgid ""
 "the netdb item."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:366
+#: i2p2www/pages/site/docs/how/network-database.html:380
 msgid "RouterInfo Storage to Floodfills"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:367
+#: i2p2www/pages/site/docs/how/network-database.html:381
 #, python-format
 msgid ""
 "A router publishes its own RouterInfo by directly connecting to a "
@@ -13234,18 +7774,18 @@ msgid ""
 "with the Message ID set to the value of the Reply Token."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:381
+#: i2p2www/pages/site/docs/how/network-database.html:395
 msgid "LeaseSet Storage to Floodfills"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:382
+#: i2p2www/pages/site/docs/how/network-database.html:396
 msgid ""
 "Storage of LeaseSets is much more sensitive than for RouterInfos, as a "
 "router\n"
 "must take care that the LeaseSet cannot be associated with the router."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:387
+#: i2p2www/pages/site/docs/how/network-database.html:401
 #, python-format
 msgid ""
 "A router publishes a local LeaseSet by\n"
@@ -13261,18 +7801,19 @@ msgid ""
 "This message is sent back to one of the client's inbound tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:400
+#: i2p2www/pages/site/docs/how/network-database.html:414
 msgid "Flooding"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:401
+#: i2p2www/pages/site/docs/how/network-database.html:415
+#, python-format
 msgid ""
 "After a floodfill router receives a DatabaseStoreMessage containing a\n"
 "valid RouterInfo or LeaseSet which is newer than that previously stored "
 "in its\n"
 "local NetDb, it \"floods\" it.\n"
-"To flood a NetDb entry, it looks up several (currently 4) floodfill "
-"routers closest to the routing key\n"
+"To flood a NetDb entry, it looks up several (currently %(floodsize)s) "
+"floodfill routers closest to the routing key\n"
 "of the NetDb entry. (The routing key is the SHA256 Hash of the "
 "RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n"
 "By flooding to those closest to the key, not closest to itself, the "
@@ -13282,7 +7823,7 @@ msgid ""
 "DHT \"neighborhood\" for the routing key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:412
+#: i2p2www/pages/site/docs/how/network-database.html:426
 #, python-format
 msgid ""
 "The floodfill then directly connects to each of those peers\n"
@@ -13293,11 +7834,11 @@ msgid ""
 "The other routers do not reply or re-flood, as the Reply Token is zero."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:422
+#: i2p2www/pages/site/docs/how/network-database.html:436
 msgid "RouterInfo and LeaseSet Lookup"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:423
+#: i2p2www/pages/site/docs/how/network-database.html:437
 #, python-format
 msgid ""
 "The I2NP DatabaseLookupMessage is used to "
@@ -13307,13 +7848,13 @@ msgid ""
 "exploratory tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:429
+#: i2p2www/pages/site/docs/how/network-database.html:443
 msgid ""
 "Lookups are generally sent to the two \"good\" (the connection doesn't "
 "fail) floodfill routers closest to the requested key, in parallel."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:433
+#: i2p2www/pages/site/docs/how/network-database.html:447
 #, python-format
 msgid ""
 "If the key is found locally by the floodfill router, it responds with a\n"
@@ -13324,7 +7865,7 @@ msgid ""
 "containing a list of other floodfill routers close to the key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:441
+#: i2p2www/pages/site/docs/how/network-database.html:455
 msgid ""
 "LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n"
 "RouterInfo lookups are not encrypted and thus are vulnerable to snooping "
@@ -13334,7 +7875,7 @@ msgid ""
 "RouterInfo lookup encryption may be enabled in a future release."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:448
+#: i2p2www/pages/site/docs/how/network-database.html:462
 msgid ""
 "As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage"
 " or a DatabaseSearchReplyMessage)\n"
@@ -13345,14 +7886,14 @@ msgid ""
 " encryption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:455
+#: i2p2www/pages/site/docs/how/network-database.html:469
 #, python-format
 msgid ""
 "(Reference: Hashing it out in Public Sections "
 "2.2-2.3 for terms below in italics)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:459
+#: i2p2www/pages/site/docs/how/network-database.html:473
 msgid ""
 "Due to the relatively small size of the network and the flooding "
 "redundancy of 8x,\n"
@@ -13368,7 +7909,7 @@ msgid ""
 "to reduce the chance of query failure."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:470
+#: i2p2www/pages/site/docs/how/network-database.html:484
 msgid ""
 "As of release 0.8.9, iterative lookups are implemented with no "
 "lookup redundancy.\n"
@@ -13386,7 +7927,7 @@ msgid ""
 "or the maximum number of peers is queried."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:482
+#: i2p2www/pages/site/docs/how/network-database.html:496
 msgid ""
 "Node IDs are verifiable in that we use the router hash "
 "directly as both the node ID and the Kademlia key.\n"
@@ -13396,11 +7937,21 @@ msgid ""
 "detailed knowledge of the neighborhood of the destination ID space."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:491
+#: i2p2www/pages/site/docs/how/network-database.html:505
 msgid "RouterInfo Storage Verification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:492
+#: i2p2www/pages/site/docs/how/network-database.html:506
+#, python-format
+msgid ""
+"Note: RouterInfo verification is disabled as of release 0.9.7.1 to "
+"prevent\n"
+"the attack described in the paper\n"
+"Practical Attacks Against the I2P Network.\n"
+"It is not clear if verification can be redesigned to be done safely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:513
 msgid ""
 "To verify a storage was successful, a router simply waits about 10 "
 "seconds,\n"
@@ -13411,11 +7962,11 @@ msgid ""
 "outbound endpoint(OBEP)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:500
+#: i2p2www/pages/site/docs/how/network-database.html:521
 msgid "LeaseSet Storage Verification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:501
+#: i2p2www/pages/site/docs/how/network-database.html:522
 msgid ""
 "To verify a storage was successful, a router simply waits about 10 "
 "seconds,\n"
@@ -13429,7 +7980,7 @@ msgid ""
 "tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:511
+#: i2p2www/pages/site/docs/how/network-database.html:532
 msgid ""
 "As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a "
 "DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n"
@@ -13437,11 +7988,11 @@ msgid ""
 "to hide the reply from the inbound gateway (IBGW) of the reply tunnel."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:519
+#: i2p2www/pages/site/docs/how/network-database.html:540
 msgid "Exploration"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:520
+#: i2p2www/pages/site/docs/how/network-database.html:541
 #, python-format
 msgid ""
 "Exploration is a special form of netdb lookup, where a router "
@@ -13464,11 +8015,11 @@ msgid ""
 "the requested key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:534
+#: i2p2www/pages/site/docs/how/network-database.html:555
 msgid "Notes on Lookup Responses"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:535
+#: i2p2www/pages/site/docs/how/network-database.html:556
 msgid ""
 "The response to a lookup request is either a Database Store Message (on "
 "success) or a\n"
@@ -13481,11 +8032,11 @@ msgid ""
 "difficult to monitor the performance of the various floodfill routers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:545
+#: i2p2www/pages/site/docs/how/network-database.html:566
 msgid "MultiHoming"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:547
+#: i2p2www/pages/site/docs/how/network-database.html:568
 msgid ""
 "Destinations may be hosted on multiple routers simultaneously, by using "
 "the same\n"
@@ -13502,18 +8053,18 @@ msgid ""
 "services on the network."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:557
+#: i2p2www/pages/site/docs/how/network-database.html:578
 msgid "Threat Analysis"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:558
+#: i2p2www/pages/site/docs/how/network-database.html:579
 #, python-format
 msgid ""
 "Also discussed on the threat model "
 "page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:562
+#: i2p2www/pages/site/docs/how/network-database.html:583
 msgid ""
 "A hostile user may attempt to harm the network by\n"
 "creating one or more floodfill routers and crafting them to offer\n"
@@ -13521,43 +8072,45 @@ msgid ""
 "Some scenarios are discussed below."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:569
+#: i2p2www/pages/site/docs/how/network-database.html:590
 msgid "General Mitigation Through Growth"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:570
+#: i2p2www/pages/site/docs/how/network-database.html:591
+#, python-format
 msgid ""
-"There are currently hundreds of floodfill routers in the network.\n"
+"There are currently around %(ffcount)s floodfill routers in the network.\n"
 "Most of the following attacks will become more difficult, or have less "
 "impact,\n"
 "as the network size and number of floodfill routers increase."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:577
+#: i2p2www/pages/site/docs/how/network-database.html:598
 msgid "General Mitigation Through Redundancy"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:578
+#: i2p2www/pages/site/docs/how/network-database.html:599
+#, python-format
 msgid ""
-"Via flooding, all netdb entries are stored on the 8 floodfill routers "
-"closest to the key."
+"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill"
+" routers closest to the key."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:583
+#: i2p2www/pages/site/docs/how/network-database.html:604
 msgid "Forgeries"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:584
+#: i2p2www/pages/site/docs/how/network-database.html:605
 msgid ""
 "All netdb entries are signed by their creators, so no router may forge a\n"
 "RouterInfo or LeaseSet."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:589
+#: i2p2www/pages/site/docs/how/network-database.html:610
 msgid "Slow or Unresponsive"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:590
+#: i2p2www/pages/site/docs/how/network-database.html:611
 #, python-format
 msgid ""
 "Each router maintains an expanded set of statistics in the\n"
@@ -13567,31 +8120,31 @@ msgid ""
 "The set includes:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:597
+#: i2p2www/pages/site/docs/how/network-database.html:618
 msgid "Average response time"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:598
+#: i2p2www/pages/site/docs/how/network-database.html:619
 msgid "Percentage of queries answered with the data requested"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:599
+#: i2p2www/pages/site/docs/how/network-database.html:620
 msgid "Percentage of stores that were successfully verified"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:600
+#: i2p2www/pages/site/docs/how/network-database.html:621
 msgid "Last successful store"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:601
+#: i2p2www/pages/site/docs/how/network-database.html:622
 msgid "Last successful lookup"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:602
+#: i2p2www/pages/site/docs/how/network-database.html:623
 msgid "Last response"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:605
+#: i2p2www/pages/site/docs/how/network-database.html:626
 msgid ""
 "Each time a router needs to make a determination on which floodfill "
 "router is closest to a key,\n"
@@ -13604,11 +8157,11 @@ msgid ""
 "routers that are only sometimes malicious may be much harder to deal with."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:615
+#: i2p2www/pages/site/docs/how/network-database.html:636
 msgid "Sybil Attack (Full Keyspace)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:616
+#: i2p2www/pages/site/docs/how/network-database.html:637
 #, python-format
 msgid ""
 "An attacker may mount a Sybil attack\n"
@@ -13616,7 +8169,7 @@ msgid ""
 "keyspace."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:621
+#: i2p2www/pages/site/docs/how/network-database.html:642
 #, python-format
 msgid ""
 "(In a related example, a researcher recently created a\n"
@@ -13625,7 +8178,7 @@ msgid ""
 "network."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:627
+#: i2p2www/pages/site/docs/how/network-database.html:648
 msgid ""
 "If the floodfills are not sufficiently misbehaving to be marked as "
 "\"bad\" using the peer profile\n"
@@ -13637,7 +8190,7 @@ msgid ""
 "none of them is completely satisfactory:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:635
+#: i2p2www/pages/site/docs/how/network-database.html:656
 msgid ""
 "Compile a list of bad router hashes or IPs, and announce the list through"
 " various means\n"
@@ -13646,30 +8199,30 @@ msgid ""
 "add it to their local \"blacklist\"."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:640
+#: i2p2www/pages/site/docs/how/network-database.html:661
 msgid ""
 "Ask everyone in the network to enable floodfill manually (fight Sybil "
 "with more Sybil)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:641
+#: i2p2www/pages/site/docs/how/network-database.html:662
 msgid "Release a new software version that includes the hardcoded \"bad\" list"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:642
+#: i2p2www/pages/site/docs/how/network-database.html:663
 msgid ""
 "Release a new software version that improves the peer profile metrics and"
 " thresholds,\n"
 "in an attempt to automatically identify the \"bad\" peers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:646
+#: i2p2www/pages/site/docs/how/network-database.html:667
 msgid ""
 "Add software that disqualifies floodfills if too many of them are in a "
 "single IP block"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:647
+#: i2p2www/pages/site/docs/how/network-database.html:668
 msgid ""
 "Implement an automatic subscription-based blacklist controlled by a "
 "single individual or group.\n"
@@ -13681,15 +8234,15 @@ msgid ""
 "or even to completely shutdown or destroy the entire network."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:656
+#: i2p2www/pages/site/docs/how/network-database.html:677
 msgid "This attack becomes more difficult as the network size grows."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:662
+#: i2p2www/pages/site/docs/how/network-database.html:683
 msgid "Sybil Attack (Partial Keyspace)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:663
+#: i2p2www/pages/site/docs/how/network-database.html:684
 #, python-format
 msgid ""
 "An attacker may mount a Sybil attack\n"
@@ -13703,7 +8256,7 @@ msgid ""
 "eepsite, for example."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:672
+#: i2p2www/pages/site/docs/how/network-database.html:693
 msgid ""
 "As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,"
 "\n"
@@ -13715,7 +8268,7 @@ msgid ""
 "size, is unknown."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:680
+#: i2p2www/pages/site/docs/how/network-database.html:701
 msgid ""
 "As a partial defense against this attack,\n"
 "the algorithm used to determine Kademlia \"closeness\" varies over time.\n"
@@ -13732,7 +8285,7 @@ msgid ""
 "to the target key, or to each other."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:692
+#: i2p2www/pages/site/docs/how/network-database.html:713
 msgid ""
 "This attack becomes more difficult as the network size grows.\n"
 "However, recent research demonstrates that the keyspace rotation is not "
@@ -13742,8 +8295,7 @@ msgid ""
 "of the keyspace within a half hour after rotation."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:700
-#: i2p2www/pages/site/docs/how/network-database.html:709
+#: i2p2www/pages/site/docs/how/network-database.html:721
 msgid ""
 "One consequence of daily keyspace rotation is that the distributed "
 "network database\n"
@@ -13755,11 +8307,11 @@ msgid ""
 "are a topic for further study."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:719
+#: i2p2www/pages/site/docs/how/network-database.html:731
 msgid "Bootstrap Attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:720
+#: i2p2www/pages/site/docs/how/network-database.html:732
 msgid ""
 "An attacker could attempt to boot new routers into an isolated\n"
 "or majority-controlled network by taking over a reseed website,\n"
@@ -13767,38 +8319,38 @@ msgid ""
 "to the hardcoded list in the router."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:727
+#: i2p2www/pages/site/docs/how/network-database.html:739
 msgid "Several defenses are possible, and most of these are planned:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:731
+#: i2p2www/pages/site/docs/how/network-database.html:743
 msgid ""
 "Disallow fallback from HTTPS to HTTP for reseeding.\n"
 "A MITM attacker could simply block HTTPS, then respond to the HTTP."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:735
+#: i2p2www/pages/site/docs/how/network-database.html:747
 msgid ""
 "Changing the reseed task to fetch a subset of RouterInfos from\n"
 "each of several reseed sites rather than using only a single site"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:739
+#: i2p2www/pages/site/docs/how/network-database.html:751
 msgid ""
 "Creating an out-of-network reseed monitoring service that\n"
 "periodically polls reseed websites and verifies that the\n"
 "data are not stale or inconsistent with other views of the network"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:744
+#: i2p2www/pages/site/docs/how/network-database.html:756
 msgid "Bundling reseed data in the installer"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:747
+#: i2p2www/pages/site/docs/how/network-database.html:759
 msgid "Query Capture"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:748
+#: i2p2www/pages/site/docs/how/network-database.html:760
 #, python-format
 msgid ""
 "See also lookup\n"
@@ -13806,7 +8358,7 @@ msgid ""
 "2.2-2.3 for terms below in italics)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:753
+#: i2p2www/pages/site/docs/how/network-database.html:765
 msgid ""
 "Similar to a bootstrap attack, an attacker using a floodfill router could"
 " attempt to \"steer\"\n"
@@ -13814,7 +8366,7 @@ msgid ""
 "references."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:758
+#: i2p2www/pages/site/docs/how/network-database.html:770
 msgid ""
 "This is unlikely to work via exploration, because exploration is a low-"
 "frequency task.\n"
@@ -13824,7 +8376,7 @@ msgid ""
 "and each exploration query is directed to a random floodfill router."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:765
+#: i2p2www/pages/site/docs/how/network-database.html:777
 #, python-format
 msgid ""
 "As of release 0.8.9, iterative lookups are implemented.\n"
@@ -13849,16 +8401,16 @@ msgid ""
 "is much more difficult."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:784
+#: i2p2www/pages/site/docs/how/network-database.html:796
 msgid "DHT-Based Relay Selection"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:785
+#: i2p2www/pages/site/docs/how/network-database.html:797
 #, python-format
 msgid "(Reference: Hashing it out in Public Section 3)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:789
+#: i2p2www/pages/site/docs/how/network-database.html:801
 #, python-format
 msgid ""
 "This doesn't have much to do with floodfill, but see\n"
@@ -13866,18 +8418,18 @@ msgid ""
 "for a discussion of the vulnerabilities of peer selection for tunnels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:795
+#: i2p2www/pages/site/docs/how/network-database.html:807
 msgid "Information Leaks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:796
+#: i2p2www/pages/site/docs/how/network-database.html:808
 #, python-format
 msgid ""
 "(Reference: In Search of an Anonymous and Secure "
 "Lookup Section 3)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:800
+#: i2p2www/pages/site/docs/how/network-database.html:812
 #, python-format
 msgid ""
 "This paper addresses weaknesses in the \"Finger Table\" DHT lookups used "
@@ -13894,7 +8446,7 @@ msgid ""
 "Also, peer selection is unrelated to any notion of DHT key-closeness."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:811
+#: i2p2www/pages/site/docs/how/network-database.html:823
 msgid ""
 "Some of this may actually be more interesting when the I2P network gets "
 "much larger.\n"
@@ -13908,14 +8460,14 @@ msgid ""
 "much harder."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:819
+#: i2p2www/pages/site/docs/how/network-database.html:831
 #, python-format
 msgid ""
 "However, the general issue of DHT information leakage in I2P needs "
 "further investigation.\n"
 "The floodfill routers are in a position to observe queries and gather "
 "information.\n"
-"Certainly, at a level of f = 0.2 (20%% malicious nodes, as "
+"Certainly, at a level of f = 0.2 (20% malicious nodes, as "
 "specifed in the paper)\n"
 "we expect that many of the Sybil threats we describe\n"
 "(here,\n"
@@ -13924,15 +8476,15 @@ msgid ""
 "become problematic for several reasons."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:833
+#: i2p2www/pages/site/docs/how/network-database.html:845
 msgid "Moved to the netdb discussion page"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:837
+#: i2p2www/pages/site/docs/how/network-database.html:849
 msgid "End-to-end encryption of additional netDb lookups and responses."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/network-database.html:841
+#: i2p2www/pages/site/docs/how/network-database.html:853
 msgid "Better methods for tracking lookup responses."
 msgstr ""
 
@@ -14296,10 +8848,9 @@ msgid "Two peers from the same /16 IP space may not be in the same tunnel."
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:239
-#, python-format
 msgid ""
-"A peer may participate in a maximum of 33% of all tunnels created by the "
-"router."
+"A peer may participate in a maximum of 33% of all tunnels created by "
+"the router."
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/peer-selection.html:242
@@ -14402,7 +8953,7 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/how/tech-intro.html:9
 #: i2p2www/pages/site/docs/how/tech-intro.html:24
-#: i2p2www/pages/site/docs/transport/ssu.html:278
+#: i2p2www/pages/site/docs/transport/ssu.html:281
 msgid "Introduction"
 msgstr ""
 
@@ -14415,6 +8966,11 @@ msgstr ""
 msgid "Transport protocols"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tech-intro.html:17
+#: i2p2www/pages/site/docs/how/tech-intro.html:458
+msgid "Cryptography"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/tech-intro.html:25
 msgid ""
 "I2P is a scalable, self organizing, resilient packet switched anonymous \n"
@@ -15733,6 +10289,10 @@ msgid ""
 "network applications provide further functionality for end users."
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tech-intro.html:808
+msgid "Streaming library"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/tech-intro.html:809
 msgid ""
 "The I2P streaming library can be viewed as a generic streaming interface "
@@ -16062,8 +10622,7 @@ msgstr ""
 #, python-format
 msgid ""
 "PyBit is a Bittorrent client written in Python.\n"
-"It is hosted on http://%(pebcache)s/"
-" "
+"It is hosted on %(pybit)s "
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/tech-intro.html:1015
@@ -16152,11 +10711,52 @@ msgstr ""
 msgid "November 2010"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:6
-msgid "What do we mean by \"anonymous\"?"
+#: i2p2www/pages/site/docs/how/threat-model.html:7
+msgid "low"
 msgstr ""
 
 #: i2p2www/pages/site/docs/how/threat-model.html:8
+msgid "medium"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:9
+msgid "high"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:34
+msgid "Damage Potential"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:35
+msgid "Reliability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:36
+msgid "Exploitability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:37
+msgid "Affected Users"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:38
+msgid "Discoverability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:39
+msgid "Severity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:40
+#: i2p2www/pages/site/docs/protocol/i2np.html:94
+msgid "Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:45
+msgid "What do we mean by \"anonymous\"?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:47
 msgid ""
 "Your level of anonymity can be described as \"how hard it is for someone\n"
 "to find out information you don't want them to know?\" - who you are, "
@@ -16174,7 +10774,7 @@ msgid ""
 "data, to those fearful of discovery by powerful organizations or states."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:19
+#: i2p2www/pages/site/docs/how/threat-model.html:58
 msgid ""
 "The question of whether I2P provides sufficient anonymity for your \n"
 "particular needs is a hard one, but this page will hopefully assist in \n"
@@ -16183,7 +10783,7 @@ msgid ""
 "so that you may decide whether it meets your needs."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:26
+#: i2p2www/pages/site/docs/how/threat-model.html:65
 msgid ""
 "We welcome further research and analysis on I2P's resistance to the "
 "threats described below.\n"
@@ -16192,11 +10792,11 @@ msgid ""
 "work focused on I2P is needed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:32
+#: i2p2www/pages/site/docs/how/threat-model.html:71
 msgid "Network Topology Summary"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:33
+#: i2p2www/pages/site/docs/how/threat-model.html:72
 #, python-format
 msgid ""
 "I2P builds off the ideas of many other \n"
@@ -16205,7 +10805,7 @@ msgid ""
 "reviewing related literature:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:39
+#: i2p2www/pages/site/docs/how/threat-model.html:78
 msgid ""
 "I2P is a free route mixnet - the message creator explicitly "
 "defines the\n"
@@ -16216,7 +10816,7 @@ msgid ""
 "inbound tunnel)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:45
+#: i2p2www/pages/site/docs/how/threat-model.html:84
 msgid ""
 "I2P has no official entry and exit points - all peers fully "
 "participate in the \n"
@@ -16224,7 +10824,7 @@ msgid ""
 "application layer, a few proxies do exist)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:50
+#: i2p2www/pages/site/docs/how/threat-model.html:89
 msgid ""
 "I2P is fully distributed - there are no central controls or "
 "authorities.\n"
@@ -16239,7 +10839,7 @@ msgid ""
 "anonymity)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:60
+#: i2p2www/pages/site/docs/how/threat-model.html:99
 #, python-format
 msgid ""
 "We have documented plans to implement [Onion Routing],\n"
 "[Freenet], and\n"
-"[Tor].\n"
+"[Tor].\n"
 "Our design benefits substantially from the research published around that"
 " time.\n"
 "I2P uses several onion routing techniques, so we continue to benefit\n"
 "from the significant academic interest in Tor."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:89
+#: i2p2www/pages/site/docs/how/threat-model.html:128
 msgid ""
 "Taking from the attacks and analysis put forth in the \n"
 "anonymity "
@@ -16295,14 +10895,14 @@ msgid ""
 "this list to include new attacks as they are identified."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:98
+#: i2p2www/pages/site/docs/how/threat-model.html:137
 msgid ""
 "Included are some attacks that may be unique to I2P.\n"
 "We do not have good answers for all these attacks, however\n"
 "we continue to do research and improve our defenses."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:104
+#: i2p2www/pages/site/docs/how/threat-model.html:143
 msgid ""
 "In addition, many of these attacks are significantly easier than\n"
 "they should be, due to the modest size of the current network.\n"
@@ -16313,7 +10913,7 @@ msgid ""
 "these attacks will become much harder."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:114
+#: i2p2www/pages/site/docs/how/threat-model.html:153
 #, python-format
 msgid ""
 "The\n"
@@ -16323,94 +10923,98 @@ msgid ""
 "to review."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:123
-#: i2p2www/pages/site/docs/how/threat-model.html:143
+#: i2p2www/pages/site/docs/how/threat-model.html:182
+msgid "Index of Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:184
+#: i2p2www/pages/site/docs/how/threat-model.html:204
 msgid "Brute force attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:124
 #: i2p2www/pages/site/docs/how/threat-model.html:185
+#: i2p2www/pages/site/docs/how/threat-model.html:248
 msgid "Timing attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:125
-#: i2p2www/pages/site/docs/how/threat-model.html:220
+#: i2p2www/pages/site/docs/how/threat-model.html:186
+#: i2p2www/pages/site/docs/how/threat-model.html:285
 msgid "Intersection attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:126
-#: i2p2www/pages/site/docs/how/threat-model.html:298
+#: i2p2www/pages/site/docs/how/threat-model.html:187
+#: i2p2www/pages/site/docs/how/threat-model.html:365
 msgid "Denial of service attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:127
-#: i2p2www/pages/site/docs/how/threat-model.html:385
+#: i2p2www/pages/site/docs/how/threat-model.html:188
+#: i2p2www/pages/site/docs/how/threat-model.html:464
 msgid "Tagging attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:128
-#: i2p2www/pages/site/docs/how/threat-model.html:400
+#: i2p2www/pages/site/docs/how/threat-model.html:189
+#: i2p2www/pages/site/docs/how/threat-model.html:482
 msgid "Partitioning attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:129
-#: i2p2www/pages/site/docs/how/threat-model.html:438
+#: i2p2www/pages/site/docs/how/threat-model.html:190
+#: i2p2www/pages/site/docs/how/threat-model.html:522
 msgid "Predecessor attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:130
-#: i2p2www/pages/site/docs/how/threat-model.html:481
+#: i2p2www/pages/site/docs/how/threat-model.html:191
+#: i2p2www/pages/site/docs/how/threat-model.html:567
 msgid "Harvesting attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:131
-#: i2p2www/pages/site/docs/how/threat-model.html:525
+#: i2p2www/pages/site/docs/how/threat-model.html:192
+#: i2p2www/pages/site/docs/how/threat-model.html:614
 msgid "Identification Through Traffic Analysis"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:132
-#: i2p2www/pages/site/docs/how/threat-model.html:582
+#: i2p2www/pages/site/docs/how/threat-model.html:193
+#: i2p2www/pages/site/docs/how/threat-model.html:674
 msgid "Sybil attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:133
-#: i2p2www/pages/site/docs/how/threat-model.html:629
+#: i2p2www/pages/site/docs/how/threat-model.html:194
+#: i2p2www/pages/site/docs/how/threat-model.html:723
 msgid "Buddy Exhaustion attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:134
-#: i2p2www/pages/site/docs/how/threat-model.html:651
+#: i2p2www/pages/site/docs/how/threat-model.html:195
+#: i2p2www/pages/site/docs/how/threat-model.html:748
 msgid "Cryptographic attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:135
+#: i2p2www/pages/site/docs/how/threat-model.html:196
 msgid "Floodfill attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:136
-#: i2p2www/pages/site/docs/how/threat-model.html:707
+#: i2p2www/pages/site/docs/how/threat-model.html:197
+#: i2p2www/pages/site/docs/how/threat-model.html:809
 msgid "Other Network Database attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:137
+#: i2p2www/pages/site/docs/how/threat-model.html:198
 msgid "Attacks on centralized resources"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:138
-#: i2p2www/pages/site/docs/how/threat-model.html:770
+#: i2p2www/pages/site/docs/how/threat-model.html:199
+#: i2p2www/pages/site/docs/how/threat-model.html:875
 msgid "Development attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:139
+#: i2p2www/pages/site/docs/how/threat-model.html:200
 msgid "Implementation attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:140
-#: i2p2www/pages/site/docs/how/threat-model.html:849
+#: i2p2www/pages/site/docs/how/threat-model.html:201
+#: i2p2www/pages/site/docs/how/threat-model.html:959
 msgid "Other Defenses"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:145
+#: i2p2www/pages/site/docs/how/threat-model.html:208
 msgid ""
 "A brute force attack can be mounted by a global passive or active "
 "adversary, \n"
@@ -16431,7 +11035,7 @@ msgid ""
 "message)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:157
+#: i2p2www/pages/site/docs/how/threat-model.html:220
 msgid ""
 "However, a powerful attacker can use brute force to detect trends - if "
 "they \n"
@@ -16458,7 +11062,7 @@ msgid ""
 "not currently implemented."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:174
+#: i2p2www/pages/site/docs/how/threat-model.html:237
 #, python-format
 msgid ""
 "As a partial defense against a single router or group of routers trying "
@@ -16471,7 +11075,7 @@ msgid ""
 "peer selection page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:187
+#: i2p2www/pages/site/docs/how/threat-model.html:252
 msgid ""
 "I2P's messages are unidirectional and do not necessarily imply that a "
 "reply\n"
@@ -16487,7 +11091,7 @@ msgid ""
 "slow to have passed the message along."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:197
+#: i2p2www/pages/site/docs/how/threat-model.html:262
 msgid ""
 "This sort of attack is powerful, but its applicability to I2P is non "
 "obvious,\n"
@@ -16505,7 +11109,7 @@ msgid ""
 "DataMessage+DeliveryStatusMessage)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:207
+#: i2p2www/pages/site/docs/how/threat-model.html:272
 #, python-format
 msgid ""
 "Without protocol scrubbing or higher latency, global active adversaries "
@@ -16521,14 +11125,14 @@ msgid ""
 "but these are unimplemented in I2P."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:216
+#: i2p2www/pages/site/docs/how/threat-model.html:281
 #, python-format
 msgid ""
 "References: Low-Resource Routing Attacks Against "
 "Anonymous Systems"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:222
+#: i2p2www/pages/site/docs/how/threat-model.html:289
 msgid ""
 "Intersection attacks against low latency systems are extremely powerful -"
 "\n"
@@ -16544,7 +11148,7 @@ msgid ""
 "scenarios."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:232
+#: i2p2www/pages/site/docs/how/threat-model.html:299
 #, python-format
 msgid ""
 "In summary, if an attacker is at both ends of your tunnel at the same "
@@ -16555,61 +11159,61 @@ msgid ""
 "Tor provides a similar disclaimer."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:240
+#: i2p2www/pages/site/docs/how/threat-model.html:307
 msgid "Partial defenses implemented in I2P:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:244
+#: i2p2www/pages/site/docs/how/threat-model.html:311
 #, python-format
 msgid "strict ordering of peers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:247
+#: i2p2www/pages/site/docs/how/threat-model.html:314
 #, python-format
 msgid ""
 "peer profiling and selection from a "
 "small group that changes slowly"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:250
+#: i2p2www/pages/site/docs/how/threat-model.html:317
 msgid "Limits on the number of tunnels routed through a single peer"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:253
+#: i2p2www/pages/site/docs/how/threat-model.html:320
 msgid ""
 "Prevention of peers from the same /16 IP range from being members of a "
 "single tunnel"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:256
+#: i2p2www/pages/site/docs/how/threat-model.html:323
 msgid ""
 "For eepsites or other hosted services, we support\n"
 "simultaneous hosting on multiple routers, or\n"
 "multihoming"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:263
+#: i2p2www/pages/site/docs/how/threat-model.html:330
 msgid ""
 "Even in total, these defenses are not a complete solution.\n"
 "Also, we have made some design choices that may significantly increase "
 "our vulnerability:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:268
+#: i2p2www/pages/site/docs/how/threat-model.html:335
 msgid "We do not use low-bandwidth \"guard nodes\""
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:271
+#: i2p2www/pages/site/docs/how/threat-model.html:338
 msgid ""
 "We use tunnel pools comprised of several tunnels, and traffic can shift "
 "from tunnel to tunnel."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:274
+#: i2p2www/pages/site/docs/how/threat-model.html:341
 msgid "Tunnels are not long-lived; new tunnels are built every 10 minutes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:277
+#: i2p2www/pages/site/docs/how/threat-model.html:344
 msgid ""
 "Tunnel lengths are configurable.\n"
 "While 3-hop tunnels are recommended for full protection, several "
@@ -16617,7 +11221,7 @@ msgid ""
 "services use 2-hop tunnels by default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:284
+#: i2p2www/pages/site/docs/how/threat-model.html:351
 #, python-format
 msgid ""
 "In the future, it could\n"
@@ -16632,35 +11236,35 @@ msgid ""
 "as an adversary can't \"ping\" them to mount the attack.
            "
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:293
+#: i2p2www/pages/site/docs/how/threat-model.html:360
 #, python-format
 msgid "Reference: One Cell Enough"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:300
+#: i2p2www/pages/site/docs/how/threat-model.html:367
 msgid ""
 "There are a whole slew of denial of service attacks available against "
 "I2P,\n"
 "each with different costs and consequences:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:305
+#: i2p2www/pages/site/docs/how/threat-model.html:373
 msgid ""
 "Greedy user attack: This is simply\n"
 "people trying to consume significantly more resources than they are \n"
 "willing to contribute. The defense against this is:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:311
+#: i2p2www/pages/site/docs/how/threat-model.html:379
 #, python-format
 msgid ""
 "Set defaults so that most users provide resources to the network.\n"
 "In I2P, users route traffic by default. In sharp distinction to\n"
 "other networks,\n"
-"over 95%% of I2P users relay traffic for others."
+"over 95% of I2P users relay traffic for others."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:317
+#: i2p2www/pages/site/docs/how/threat-model.html:385
 msgid ""
 "Provide easy configuration options so that users may increase their\n"
 "contribution (share percentage) to the network. Display easy-to-"
@@ -16669,13 +11273,13 @@ msgid ""
 "contributing."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:322
+#: i2p2www/pages/site/docs/how/threat-model.html:390
 msgid ""
 "Maintain a strong community with blogs, forums, IRC, and other means of "
 "communication."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:327
+#: i2p2www/pages/site/docs/how/threat-model.html:397
 #, python-format
 msgid ""
 "Starvation attack: A hostile user may attempt to harm the network "
@@ -16704,7 +11308,7 @@ msgid ""
 "significant efforts required in this area."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:344
+#: i2p2www/pages/site/docs/how/threat-model.html:417
 #, python-format
 msgid ""
 "Flooding attack: A hostile user may attempt to flood the network,\n"
@@ -16735,7 +11339,7 @@ msgid ""
 "operation is implemented)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:360
+#: i2p2www/pages/site/docs/how/threat-model.html:436
 msgid ""
 "CPU load attack: There are currently some methods for people to \n"
 "remotely request that a peer perform some cryptographically expensive \n"
@@ -16750,7 +11354,7 @@ msgid ""
 "bugs in the implementation."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:370
+#: i2p2www/pages/site/docs/how/threat-model.html:449
 #, python-format
 msgid ""
 "Floodfill DOS attack: A hostile user may attempt to harm the "
@@ -16766,7 +11370,7 @@ msgid ""
 "network database page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:386
+#: i2p2www/pages/site/docs/how/threat-model.html:468
 #, python-format
 msgid ""
 "Tagging attacks - modifying a message so that it can later be identified"
@@ -16792,7 +11396,7 @@ msgid ""
 "as the links are encrypted and messages signed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:402
+#: i2p2www/pages/site/docs/how/threat-model.html:486
 msgid ""
 "Partitioning attacks - finding ways to segregate (technically or "
 "analytically)\n"
@@ -16821,7 +11425,7 @@ msgid ""
 "the moment)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:418
+#: i2p2www/pages/site/docs/how/threat-model.html:502
 #, python-format
 msgid ""
 "Partitioning the network analytically by looking for differences in how "
@@ -16851,14 +11455,14 @@ msgid ""
 "which other tunnels or messages have those delays)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:434
+#: i2p2www/pages/site/docs/how/threat-model.html:518
 #, python-format
 msgid ""
 "Also discussed on the network database "
 "page (bootstrap attack)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:440
+#: i2p2www/pages/site/docs/how/threat-model.html:526
 msgid ""
 "The predecessor attack is passively gathering statistics in an attempt to"
 " see\n"
@@ -16875,7 +11479,7 @@ msgid ""
 "target is located."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:450
+#: i2p2www/pages/site/docs/how/threat-model.html:536
 #, python-format
 msgid ""
 "I2P avoids this in four ways: first, the peers selected to participate in"
@@ -16900,7 +11504,7 @@ msgid ""
 "attackers will merely run into that gateway."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:467
+#: i2p2www/pages/site/docs/how/threat-model.html:553
 #, python-format
 msgid ""
 "The current tunnel build method\n"
@@ -16908,7 +11512,7 @@ msgid ""
 "See also the intersection attack."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:473
+#: i2p2www/pages/site/docs/how/threat-model.html:559
 #, python-format
 msgid ""
 "References: %(pdf2008)s\n"
@@ -16916,7 +11520,7 @@ msgid ""
 "%(pdf2004)s."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:482
+#: i2p2www/pages/site/docs/how/threat-model.html:571
 msgid ""
 "\"Harvesting\" means compiling a list of users running I2P.\n"
 "It can be used for legal attacks and to help\n"
@@ -16924,7 +11528,7 @@ msgid ""
 "harvesting whatever references to other peers it can find."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:489
+#: i2p2www/pages/site/docs/how/threat-model.html:578
 msgid ""
 "I2P itself is not designed with effective defenses against\n"
 "this attack, since there is the distributed network database \n"
@@ -16932,17 +11536,17 @@ msgid ""
 "The following factors make the attack somewhat harder in practice:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:496
+#: i2p2www/pages/site/docs/how/threat-model.html:585
 msgid ""
 "Network growth will make it more difficult to obtain a given proportion "
 "of the network"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:499
+#: i2p2www/pages/site/docs/how/threat-model.html:588
 msgid "Floodfill routers implement query limits as DOS protection"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:502
+#: i2p2www/pages/site/docs/how/threat-model.html:591
 msgid ""
 "\"Hidden mode\", which prevents a router from publishing its information "
 "to the netDb,\n"
@@ -16950,7 +11554,7 @@ msgid ""
 "could be."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:508
+#: i2p2www/pages/site/docs/how/threat-model.html:597
 #, python-format
 msgid ""
 "In future implementations,\n"
@@ -16964,7 +11568,7 @@ msgid ""
 "they can be reached (as well as their public keys, etc)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:517
+#: i2p2www/pages/site/docs/how/threat-model.html:606
 msgid ""
 "In the future, routers could use GeoIP to identify if they are in a "
 "particular\n"
@@ -16973,7 +11577,7 @@ msgid ""
 "enact other restricted route methods."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:526
+#: i2p2www/pages/site/docs/how/threat-model.html:618
 #, python-format
 msgid ""
 "By inspecting the traffic into and out of a router, a malicious ISP\n"
@@ -16987,21 +11591,21 @@ msgid ""
 "make it somewhat difficult to identify I2P traffic:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:536
+#: i2p2www/pages/site/docs/how/threat-model.html:628
 msgid "Random port selection"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:539
+#: i2p2www/pages/site/docs/how/threat-model.html:631
 msgid "Point-to-Point Encryption of all traffic"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:542
+#: i2p2www/pages/site/docs/how/threat-model.html:634
 msgid ""
 "DH key exchange with no protocol bytes or other unencrypted constant "
 "fields"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:545
+#: i2p2www/pages/site/docs/how/threat-model.html:637
 #, python-format
 msgid ""
 "Simultaneous use of both\n"
@@ -17011,62 +11615,61 @@ msgid ""
 " track."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:553
+#: i2p2www/pages/site/docs/how/threat-model.html:645
 msgid ""
 "In the near future, we plan to directly address traffic analysis issues "
 "by further obfuscation of I2P transport protocols, possibly including:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:557
+#: i2p2www/pages/site/docs/how/threat-model.html:649
 msgid ""
 "Padding at the transport layer to random lengths, especially during the "
 "connection handshake"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:560
+#: i2p2www/pages/site/docs/how/threat-model.html:652
 msgid ""
 "Study of packet size distribution signatures, and additional padding as "
 "necessary"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:563
+#: i2p2www/pages/site/docs/how/threat-model.html:655
 msgid ""
 "Development of additional transport methods that mimic SSL or other "
 "common protocols"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:566
+#: i2p2www/pages/site/docs/how/threat-model.html:658
 msgid ""
 "Review of padding strategies at higher layers to see how they affect "
 "packet sizes at the transport layer"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:569
+#: i2p2www/pages/site/docs/how/threat-model.html:661
 msgid ""
 "Review of methods implemented by various state-level firewalls to block "
 "Tor"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:572
+#: i2p2www/pages/site/docs/how/threat-model.html:664
 msgid "Working directly with DPI and obfuscation experts"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:577
+#: i2p2www/pages/site/docs/how/threat-model.html:669
 #, python-format
 msgid ""
 "Reference: Breaking and Improving Protocol "
 "Obfuscation"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:584
-#, python-format
+#: i2p2www/pages/site/docs/how/threat-model.html:678
 msgid ""
 "Sybil describes a category of attacks where the adversary creates "
 "arbitrarily\n"
 "large numbers of colluding nodes and uses the increased numbers to help \n"
 "mounting other attacks.  For instance, if an attacker is in a network "
 "where peers\n"
-"are selected randomly and they want an 80% chance to be one of those "
+"are selected randomly and they want an 80% chance to be one of those "
 "peers, they\n"
 "simply create five times the number of nodes that are in the network and "
 "roll \n"
@@ -17089,15 +11692,15 @@ msgid ""
 "scarcity)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:602
+#: i2p2www/pages/site/docs/how/threat-model.html:696
 msgid "Requiring HashCash Certificates in various places has two major problems:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:606
+#: i2p2www/pages/site/docs/how/threat-model.html:700
 msgid "Maintaining backward compatibility"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:609
+#: i2p2www/pages/site/docs/how/threat-model.html:703
 msgid ""
 "The classic HashCash problem -\n"
 "selecting HashCash values that are meaningful proofs of work on high-end "
@@ -17105,7 +11708,7 @@ msgid ""
 "while still being feasible on low-end machines such as mobile devices."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:616
+#: i2p2www/pages/site/docs/how/threat-model.html:710
 msgid ""
 "Various limitations on the number of routers in a given IP range restrict"
 "\n"
@@ -17115,21 +11718,21 @@ msgid ""
 "However, this is not a meaningful defense against a powerful adversary."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:623
+#: i2p2www/pages/site/docs/how/threat-model.html:717
 #, python-format
 msgid ""
 "See the network database page\n"
 "for more Sybil discussion."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:630
+#: i2p2www/pages/site/docs/how/threat-model.html:727
 #, python-format
 msgid ""
 "(Reference: In Search of an Anonymouns and Secure "
 "Lookup Section 5.2)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:634
+#: i2p2www/pages/site/docs/how/threat-model.html:731
 #, python-format
 msgid ""
 "By refusing to accept or forward tunnel build requests, except to a "
@@ -17143,7 +11746,7 @@ msgid ""
 "the performance\n"
 "of peers.\n"
 "However, this is a powerful attack as the number of routers approaches\n"
-"f = 0.2, or 20%% malicious nodes, as specifed in the paper.\n"
+"f = 0.2, or 20% malicious nodes, as specifed in the paper.\n"
 "The malicous routers could also maintain connections to the target router"
 " and provide\n"
 "excellent forwarding bandwidth for traffic over those connections, in an "
@@ -17152,7 +11755,7 @@ msgid ""
 "Further research and defenses may be necessary."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:653
+#: i2p2www/pages/site/docs/how/threat-model.html:752
 #, python-format
 msgid ""
 "We use strong cryptography with long keys, and\n"
@@ -17180,7 +11783,7 @@ msgid ""
 "shared secret values while maintaining backward compatibility."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:672
+#: i2p2www/pages/site/docs/how/threat-model.html:771
 #, python-format
 msgid ""
 "Upgrading the various data structures and protocols to support longer "
@@ -17193,7 +11796,7 @@ msgid ""
 "implement mechanisms to make it easier for future transitions."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:681
+#: i2p2www/pages/site/docs/how/threat-model.html:780
 msgid ""
 "In the future, several I2P protocols and data structures\n"
 "support securely padding messages to arbitrary sizes, so messages could "
@@ -17205,11 +11808,11 @@ msgid ""
 "end to end messages include simple random padding."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:691
+#: i2p2www/pages/site/docs/how/threat-model.html:790
 msgid "Floodfill Anonymity attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:692
+#: i2p2www/pages/site/docs/how/threat-model.html:794
 #, python-format
 msgid ""
 "In addition to the floodfill DOS attacks described\n"
@@ -17229,7 +11832,7 @@ msgid ""
 " future research."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:708
+#: i2p2www/pages/site/docs/how/threat-model.html:810
 #, python-format
 msgid ""
 "A hostile user may attempt to harm the network by\n"
@@ -17239,11 +11842,11 @@ msgid ""
 "network database page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:718
+#: i2p2www/pages/site/docs/how/threat-model.html:820
 msgid "Central Resource Attacks"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:719
+#: i2p2www/pages/site/docs/how/threat-model.html:824
 msgid ""
 "There are a few centralized or limited resources (some inside I2P, some "
 "not)\n"
@@ -17258,14 +11861,14 @@ msgid ""
 "not the operation of the network itself."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:729
+#: i2p2www/pages/site/docs/how/threat-model.html:834
 #, python-format
 msgid ""
 "The website is mirrored and uses DNS round-robin"
 " for external public access."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:732
+#: i2p2www/pages/site/docs/how/threat-model.html:837
 #, python-format
 msgid ""
 "Routers now support multiple external reseed "
@@ -17275,17 +11878,17 @@ msgid ""
 "reseed hosts may need improvement."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:737
+#: i2p2www/pages/site/docs/how/threat-model.html:842
 msgid ""
 "Routers now support multiple update file locations.\n"
 "A malicious update host could feed a huge file, need to limit the size."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:741
+#: i2p2www/pages/site/docs/how/threat-model.html:846
 msgid "Routers now support multiple default trusted update signers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:744
+#: i2p2www/pages/site/docs/how/threat-model.html:849
 msgid ""
 "Routers now better handle multiple unreliable "
 "floodfill peers.\n"
@@ -17293,21 +11896,21 @@ msgid ""
 "href=\"#floodfill\">more study."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:748
+#: i2p2www/pages/site/docs/how/threat-model.html:853
 #, python-format
 msgid ""
 "The code is now stored in a distributed source "
 "control system."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:751
+#: i2p2www/pages/site/docs/how/threat-model.html:856
 msgid ""
 "Routers rely on a single news host, but there is a hardcoded backup URL "
 "pointing to a different host.\n"
 "A malicious news host could feed a huge file, need to limit the size."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:755
+#: i2p2www/pages/site/docs/how/threat-model.html:860
 #, python-format
 msgid ""
 "Naming system services, including addressbook "
@@ -17320,7 +11923,7 @@ msgid ""
 "the naming page for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:762
+#: i2p2www/pages/site/docs/how/threat-model.html:867
 msgid ""
 "We remain reliant on the DNS service for i2p2.de, losing this would cause"
 " substantial\n"
@@ -17329,7 +11932,7 @@ msgid ""
 "loss of i2p.net did."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:772
+#: i2p2www/pages/site/docs/how/threat-model.html:879
 msgid ""
 "These attacks aren't directly on the network, but instead go after its "
 "development team \n"
@@ -17345,11 +11948,11 @@ msgid ""
 "have a big problem."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:781
+#: i2p2www/pages/site/docs/how/threat-model.html:888
 msgid "However, two techniques help defend against these attacks:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:785
+#: i2p2www/pages/site/docs/how/threat-model.html:892
 #, python-format
 msgid ""
 "All components of the network must be open source to enable inspection, "
@@ -17365,7 +11968,7 @@ msgid ""
 "to restrict modifications to those previously approved."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:793
+#: i2p2www/pages/site/docs/how/threat-model.html:900
 #, python-format
 msgid ""
 "Development over the network itself, allowing developers to stay "
@@ -17379,18 +11982,18 @@ msgid ""
 "all available within I2P."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:804
+#: i2p2www/pages/site/docs/how/threat-model.html:911
 msgid ""
 "We also maintain relationships with various organizations that offer "
 "legal advice,\n"
 "should any defense be necessary."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:809
+#: i2p2www/pages/site/docs/how/threat-model.html:916
 msgid "Implementation attacks (bugs)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:810
+#: i2p2www/pages/site/docs/how/threat-model.html:920
 msgid ""
 "Try as we might, most nontrivial applications include errors in the "
 "design or \n"
@@ -17407,7 +12010,7 @@ msgid ""
 "obscurity."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:821
+#: i2p2www/pages/site/docs/how/threat-model.html:931
 msgid ""
 "In addition, the code is being \n"
 "treated the same way, with little aversion towards reworking or throwing "
@@ -17423,7 +12026,7 @@ msgid ""
 "enough to identify shortcomings and bugs."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:831
+#: i2p2www/pages/site/docs/how/threat-model.html:941
 msgid ""
 "Our software is likely, in particular, to contain bugs related to denial "
 "of service\n"
@@ -17433,7 +12036,7 @@ msgid ""
 "protocols."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:837
+#: i2p2www/pages/site/docs/how/threat-model.html:947
 #, python-format
 msgid ""
 "I2P is still a small network with a small development community and "
@@ -17445,11 +12048,11 @@ msgid ""
 "get involved and help."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:850
+#: i2p2www/pages/site/docs/how/threat-model.html:960
 msgid "Blocklists"
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:851
+#: i2p2www/pages/site/docs/how/threat-model.html:961
 msgid ""
 "To some extent, I2P could be enhanced to avoid peers operating at IP "
 "addresses\n"
@@ -17459,7 +12062,7 @@ msgid ""
 "others."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:857
+#: i2p2www/pages/site/docs/how/threat-model.html:967
 msgid ""
 "To the extent that active peers actually do show up in the actual "
 "blocklist,\n"
@@ -17469,7 +12072,7 @@ msgid ""
 "enable it by default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:865
+#: i2p2www/pages/site/docs/how/threat-model.html:975
 msgid ""
 "Blocklists are only a part (perhaps a small part) of an array of defenses"
 "\n"
@@ -17480,7 +12083,7 @@ msgid ""
 "list above there are improvements we can make in detecting badness."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:874
+#: i2p2www/pages/site/docs/how/threat-model.html:984
 msgid ""
 "If a blocklist is hosted at a central location with automatic updates\n"
 "the network is vulnerable to a\n"
@@ -17490,7 +12093,7 @@ msgid ""
 "the i2p network down. Completely."
 msgstr ""
 
-#: i2p2www/pages/site/docs/how/threat-model.html:882
+#: i2p2www/pages/site/docs/how/threat-model.html:992
 msgid ""
 "Currently, a default blocklist is distributed with our software,\n"
 "listing only the IPs of past DOS sources.\n"
@@ -17552,6 +12155,11 @@ msgstr ""
 msgid "Outbound Endpoint"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
+#: i2p2www/pages/site/docs/tunnels/implementation.html:140
+msgid "Inbound Gateway"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:31
 msgid "Inbound Participant"
 msgstr ""
@@ -17905,6 +12513,10 @@ msgid ""
 "profile."
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:230
+msgid "Tunnel creation"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:231
 #, python-format
 msgid ""
@@ -17969,10 +12581,18 @@ msgstr ""
 msgid "Tunnel creation specification"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:288
+msgid "Unidirectional tunnels"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:290
 msgid "Tunnel message specification"
 msgstr ""
 
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:292
+msgid "Garlic routing"
+msgstr ""
+
 #: i2p2www/pages/site/docs/how/tunnel-routing.html:294
 msgid "ElGamal/AES+SessionTag"
 msgstr ""
@@ -17989,10 +12609,8 @@ msgid ""
 "It enables\n"
 "secure and asynchronous messaging by sending and receiving messages over "
 "a \n"
-"single TCP socket, yet never exposing any private keys and authenticating"
-" itself\n"
-"to the router only through signatures.  With I2CP, a client application "
-"tells the\n"
+"single TCP socket.\n"
+"With I2CP, a client application tells the\n"
 "router who they are (their \"destination\"), what anonymity, reliability,"
 " and \n"
 "latency tradeoffs to make, and where to send messages.  In turn the "
@@ -18005,28 +12623,19 @@ msgstr ""
 #: i2p2www/pages/site/docs/protocol/i2cp.html:18
 #, python-format
 msgid ""
-"The protocol itself has only been implemented in Java, to provide the\n"
+"The protocol itself is implemented in Java, to provide the\n"
 "Client SDK.\n"
 "This SDK is exposed in the i2p.jar package, which implements the client-"
 "side of I2CP.\n"
 "Clients should never need to access the router.jar package, which "
 "contains the\n"
-"router itself and the router-side of I2CP."
+"router itself and the router-side of I2CP.\n"
+"There is also a C library implementation.\n"
+"A non-Java client would also have to implement the\n"
+"streaming library for TCP-style connections."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:26
-#, python-format
-msgid ""
-"While implementing the client side of I2CP in a non-Java language is "
-"certainly feasible,\n"
-"a non-Java client would also have to implement the\n"
-"streaming library for TCP-style "
-"connections.\n"
-"Together, implementing I2CP and the streaming library would be a sizable "
-"task."
-msgstr ""
-
-#: i2p2www/pages/site/docs/protocol/i2cp.html:33
+#: i2p2www/pages/site/docs/protocol/i2cp.html:31
 #, python-format
 msgid ""
 "Applications can take advantage of the base I2CP plus the \n"
@@ -18042,7 +12651,7 @@ msgid ""
 "So there are several options for both Java and non-Java applications."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:45
+#: i2p2www/pages/site/docs/protocol/i2cp.html:43
 #, python-format
 msgid ""
 "Client-side end-to-end encryption (encrypting the data over the I2CP "
@@ -18058,7 +12667,7 @@ msgid ""
 " management of those keys."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:58
+#: i2p2www/pages/site/docs/protocol/i2cp.html:56
 msgid ""
 "In a standard I2P installation, port 7654 is used by external java "
 "clients to communicate\n"
@@ -18072,20 +12681,35 @@ msgid ""
 "through an internal JVM interface."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:67
+#: i2p2www/pages/site/docs/protocol/i2cp.html:65
+#, python-format
+msgid ""
+"The router also supports external connections over SSL.\n"
+"While SSL is not the default, it is strongly recommended for any traffic "
+"that may\n"
+"be exposed to the open Internet. The authorization user/password (if "
+"any), the\n"
+"Private Key and\n"
+"Signing Private "
+"Key for the\n"
+"Destination\n"
+"are all transmitted in-the-clear unless SSL is enabled."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:75
 msgid "I2CP Protocol Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:68
+#: i2p2www/pages/site/docs/protocol/i2cp.html:76
 #, python-format
 msgid "Now on the I2CP Specification page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:73
+#: i2p2www/pages/site/docs/protocol/i2cp.html:81
 msgid "I2CP Initialization"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:74
+#: i2p2www/pages/site/docs/protocol/i2cp.html:82
 #, python-format
 msgid ""
 "When a client connects to the router, it first sends a single protocol "
@@ -18103,11 +12727,11 @@ msgid ""
 "destinations."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:83
+#: i2p2www/pages/site/docs/protocol/i2cp.html:91
 msgid "I2CP Options"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:84
+#: i2p2www/pages/site/docs/protocol/i2cp.html:92
 #, python-format
 msgid ""
 "The following options are traditionally passed to the router via\n"
@@ -18117,54 +12741,54 @@ msgid ""
 "Message."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:90
+#: i2p2www/pages/site/docs/protocol/i2cp.html:98
 msgid "Router-side Options"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:95
-#: i2p2www/pages/site/docs/protocol/i2cp.html:438
+#: i2p2www/pages/site/docs/protocol/i2cp.html:103
+#: i2p2www/pages/site/docs/protocol/i2cp.html:446
 msgid "As Of Release"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:96
-#: i2p2www/pages/site/docs/protocol/i2cp.html:439
+#: i2p2www/pages/site/docs/protocol/i2cp.html:104
+#: i2p2www/pages/site/docs/protocol/i2cp.html:447
 msgid "Recommended Arguments"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:97
-#: i2p2www/pages/site/docs/protocol/i2cp.html:440
+#: i2p2www/pages/site/docs/protocol/i2cp.html:105
+#: i2p2www/pages/site/docs/protocol/i2cp.html:448
 msgid "Allowable Range"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:105
-#: i2p2www/pages/site/docs/protocol/i2cp.html:118
-#: i2p2www/pages/site/docs/protocol/i2cp.html:127
-#: i2p2www/pages/site/docs/protocol/i2cp.html:136
-#: i2p2www/pages/site/docs/protocol/i2cp.html:145
-#: i2p2www/pages/site/docs/protocol/i2cp.html:160
-#: i2p2www/pages/site/docs/protocol/i2cp.html:175
-#: i2p2www/pages/site/docs/protocol/i2cp.html:184
-#: i2p2www/pages/site/docs/protocol/i2cp.html:232
-#: i2p2www/pages/site/docs/protocol/i2cp.html:244
-#: i2p2www/pages/site/docs/protocol/i2cp.html:256
+#: i2p2www/pages/site/docs/protocol/i2cp.html:113
+#: i2p2www/pages/site/docs/protocol/i2cp.html:126
+#: i2p2www/pages/site/docs/protocol/i2cp.html:135
+#: i2p2www/pages/site/docs/protocol/i2cp.html:144
+#: i2p2www/pages/site/docs/protocol/i2cp.html:153
+#: i2p2www/pages/site/docs/protocol/i2cp.html:168
+#: i2p2www/pages/site/docs/protocol/i2cp.html:183
+#: i2p2www/pages/site/docs/protocol/i2cp.html:192
+#: i2p2www/pages/site/docs/protocol/i2cp.html:240
+#: i2p2www/pages/site/docs/protocol/i2cp.html:252
+#: i2p2www/pages/site/docs/protocol/i2cp.html:264
 #, python-format
 msgid "number from %(from)s to %(to)s"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:106
-#: i2p2www/pages/site/docs/protocol/i2cp.html:128
-#: i2p2www/pages/site/docs/protocol/i2cp.html:137
-#: i2p2www/pages/site/docs/protocol/i2cp.html:146
-#: i2p2www/pages/site/docs/protocol/i2cp.html:161
-#: i2p2www/pages/site/docs/protocol/i2cp.html:233
-#: i2p2www/pages/site/docs/protocol/i2cp.html:245
-#: i2p2www/pages/site/docs/protocol/i2cp.html:257
-#: i2p2www/pages/site/docs/protocol/i2cp.html:530
+#: i2p2www/pages/site/docs/protocol/i2cp.html:114
+#: i2p2www/pages/site/docs/protocol/i2cp.html:136
+#: i2p2www/pages/site/docs/protocol/i2cp.html:145
+#: i2p2www/pages/site/docs/protocol/i2cp.html:154
+#: i2p2www/pages/site/docs/protocol/i2cp.html:169
+#: i2p2www/pages/site/docs/protocol/i2cp.html:241
+#: i2p2www/pages/site/docs/protocol/i2cp.html:253
+#: i2p2www/pages/site/docs/protocol/i2cp.html:265
+#: i2p2www/pages/site/docs/protocol/i2cp.html:538
 #, python-format
 msgid "%(from)s to %(to)s"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:108
+#: i2p2www/pages/site/docs/protocol/i2cp.html:116
 msgid ""
 "Number of tunnels in.\n"
 "Limit was increased from 6 to 16 in release 0.9; however, numbers higher "
@@ -18173,25 +12797,25 @@ msgid ""
 " releases."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:119
-#: i2p2www/pages/site/docs/protocol/i2cp.html:176
-#: i2p2www/pages/site/docs/protocol/i2cp.html:185
+#: i2p2www/pages/site/docs/protocol/i2cp.html:127
+#: i2p2www/pages/site/docs/protocol/i2cp.html:184
+#: i2p2www/pages/site/docs/protocol/i2cp.html:193
 msgid "No limit"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:121
+#: i2p2www/pages/site/docs/protocol/i2cp.html:129
 msgid "Number of tunnels out"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:130
+#: i2p2www/pages/site/docs/protocol/i2cp.html:138
 msgid "Length of tunnels in"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:139
+#: i2p2www/pages/site/docs/protocol/i2cp.html:147
 msgid "Length of tunnels out"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:148
+#: i2p2www/pages/site/docs/protocol/i2cp.html:156
 msgid ""
 "Random amount to add or subtract to the length of tunnels in.\n"
 "A positive number x means add a random amount from 0 to x inclusive.\n"
@@ -18201,7 +12825,7 @@ msgid ""
 "The default variance was 1 prior to release 0.7.6."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:163
+#: i2p2www/pages/site/docs/protocol/i2cp.html:171
 msgid ""
 "Random amount to add or subtract to the length of tunnels out.\n"
 "A positive number x means add a random amount from 0 to x inclusive.\n"
@@ -18211,92 +12835,94 @@ msgid ""
 "The default variance was 1 prior to release 0.7.6."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:178
+#: i2p2www/pages/site/docs/protocol/i2cp.html:186
 msgid "Number of redundant fail-over for tunnels in"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:187
+#: i2p2www/pages/site/docs/protocol/i2cp.html:195
 msgid "Number of redundant fail-over for tunnels out"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:196
+#: i2p2www/pages/site/docs/protocol/i2cp.html:204
 msgid ""
 "Name of tunnel - generally used in routerconsole, which will\n"
 "use the first few characters of the Base64 hash of the destination by "
 "default."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:208
+#: i2p2www/pages/site/docs/protocol/i2cp.html:216
 msgid "Name of tunnel - generally ignored unless inbound.nickname is unset."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:217
+#: i2p2www/pages/site/docs/protocol/i2cp.html:225
 msgid "If incoming zero hop tunnel is allowed"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:226
+#: i2p2www/pages/site/docs/protocol/i2cp.html:234
 msgid "If outgoing zero hop tunnel is allowed"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:235
-#: i2p2www/pages/site/docs/protocol/i2cp.html:247
+#: i2p2www/pages/site/docs/protocol/i2cp.html:243
+#: i2p2www/pages/site/docs/protocol/i2cp.html:255
 msgid ""
 "Number of IP bytes to match to determine if\n"
 "two routers should not be in the same tunnel. 0 to disable."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:259
+#: i2p2www/pages/site/docs/protocol/i2cp.html:267
 msgid ""
 "Priority adjustment for outbound messages.\n"
 "Higher is higher priority."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:271
+#: i2p2www/pages/site/docs/protocol/i2cp.html:279
 msgid "Should generally be set to true for clients and false for servers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:280
+#: i2p2www/pages/site/docs/protocol/i2cp.html:288
 msgid ""
 "Guaranteed is disabled;\n"
 "None implemented in 0.8.1; the streaming lib default is None as of 0.8.1,"
 " the client side default is None as of 0.9.4"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:292
-#: i2p2www/pages/site/docs/protocol/i2cp.html:571
+#: i2p2www/pages/site/docs/protocol/i2cp.html:300
+#: i2p2www/pages/site/docs/protocol/i2cp.html:579
 msgid ""
 "If true, the router just sends the MessagePayload instead\n"
 "of sending a MessageStatus and awaiting a ReceiveMessageBegin."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:304
+#: i2p2www/pages/site/docs/protocol/i2cp.html:312
 msgid ""
 "Comma-separated list of Base 64 Hashes of peers to build tunnels through;"
 " for debugging only"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:313
-#: i2p2www/pages/site/docs/protocol/i2cp.html:325
+#: i2p2www/pages/site/docs/protocol/i2cp.html:321
 msgid ""
 "For authorization, if required by the router.\n"
 "If the client is running in the same JVM as a router, this option is not "
-"required."
+"required.\n"
+"Warning - username and password are sent in the clear to the router, "
+"unless using SSL (i2cp.SSL=true).\n"
+"Authorization is only recommended when using SSL."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:337
+#: i2p2www/pages/site/docs/protocol/i2cp.html:343
 msgid ""
 "Number of ElGamal/AES Session Tags to send at a time.\n"
 "For clients with relatively low bandwidth per-client-pair (IRC, some UDP "
 "apps), this may be set lower."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:349
+#: i2p2www/pages/site/docs/protocol/i2cp.html:355
 msgid ""
 "Minimum number of ElGamal/AES Session Tags before we send more.\n"
 "Recommended: approximately tagsToSend * 2/3"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:361
+#: i2p2www/pages/site/docs/protocol/i2cp.html:367
 msgid ""
 "Set to false to disable ever bundling a reply LeaseSet.\n"
 "For clients that do not publish their LeaseSet, this option must be true\n"
@@ -18305,7 +12931,7 @@ msgid ""
 "with long connection times."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:368
+#: i2p2www/pages/site/docs/protocol/i2cp.html:374
 msgid ""
 "Setting to \"false\" may save significant outbound bandwidth, especially "
 "if\n"
@@ -18316,15 +12942,15 @@ msgid ""
 "There are several cases where \"false\" may be appropriate:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:376
+#: i2p2www/pages/site/docs/protocol/i2cp.html:382
 msgid "Unidirectional communication, no reply required"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:377
+#: i2p2www/pages/site/docs/protocol/i2cp.html:383
 msgid "LeaseSet is published and higher reply latency is acceptable"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:378
+#: i2p2www/pages/site/docs/protocol/i2cp.html:384
 msgid ""
 "LeaseSet is published, client is a \"server\", all connections are "
 "inbound\n"
@@ -18338,35 +12964,41 @@ msgid ""
 "HTTP servers may fit these requirements."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:396
+#: i2p2www/pages/site/docs/protocol/i2cp.html:402
 msgid ""
 "Any other options prefixed with \"inbound.\" are stored\n"
 "in the \"unknown options\" properties of the inbound tunnel pool's "
 "settings."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:408
+#: i2p2www/pages/site/docs/protocol/i2cp.html:414
 msgid ""
 "Any other options prefixed with \"outbound.\" are stored\n"
 "in the \"unknown options\" properties of the outbound tunnel pool's "
 "settings."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:415
+#: i2p2www/pages/site/docs/protocol/i2cp.html:421
 msgid ""
 "Note: Large quantity, length, or variance settings may cause significant "
 "performance or reliability problems."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:419
+#: i2p2www/pages/site/docs/protocol/i2cp.html:425
+#, python-format
 msgid ""
 "Note: As of release 0.7.7, option names and values must use UTF-8 "
 "encoding.\n"
 "This is primarily useful for nicknames.\n"
 "Prior to that release, options with multi-byte characters were corrupted."
+"\n"
+"Since options are encoded in a Mapping,\n"
+"all option names and values are limited to 255 bytes (not characters) "
+"maximum."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:425
+#: i2p2www/pages/site/docs/protocol/i2cp.html:433
 msgid ""
 "The following options are interpreted on the client side,\n"
 "and will be interpreted if passed to the I2PSession via the "
@@ -18375,76 +13007,76 @@ msgid ""
 "Other implementations may have different defaults."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:433
+#: i2p2www/pages/site/docs/protocol/i2cp.html:441
 msgid "Client-side Options"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:451
+#: i2p2www/pages/site/docs/protocol/i2cp.html:459
 msgid ""
 "Router hostname.\n"
 "If the client is running in the same JVM as a router, this option is "
 "ignored, and the client connects to that router internally."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:463
+#: i2p2www/pages/site/docs/protocol/i2cp.html:471
 msgid ""
 "Router I2CP port.\n"
 "If the client is running in the same JVM as a router, this option is "
 "ignored, and the client connects to that router internally."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:475
+#: i2p2www/pages/site/docs/protocol/i2cp.html:483
 msgid ""
 "Connect to the router using SSL.\n"
 "If the client is running in the same JVM as a router, this option is "
 "ignored, and the client connects to that router internally."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:487
+#: i2p2www/pages/site/docs/protocol/i2cp.html:495
 msgid "Gzip outbound data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:496
+#: i2p2www/pages/site/docs/protocol/i2cp.html:504
 msgid "Reduce tunnel quantity when idle"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:505
+#: i2p2www/pages/site/docs/protocol/i2cp.html:513
 msgid "Close I2P session when idle"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:512
-#: i2p2www/pages/site/docs/protocol/i2cp.html:521
+#: i2p2www/pages/site/docs/protocol/i2cp.html:520
+#: i2p2www/pages/site/docs/protocol/i2cp.html:529
 #, python-format
 msgid "%(num)s minimum"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:514
+#: i2p2www/pages/site/docs/protocol/i2cp.html:522
 msgid "(ms) Idle time required (default 20 minutes, minimum 5 minutes)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:523
+#: i2p2www/pages/site/docs/protocol/i2cp.html:531
 msgid "(ms) Idle time required (default 30 minutes)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:532
+#: i2p2www/pages/site/docs/protocol/i2cp.html:540
 msgid "Tunnel quantity when reduced (applies to both inbound and outbound)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:541
+#: i2p2www/pages/site/docs/protocol/i2cp.html:549
 msgid "Encrypt the lease"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:550
+#: i2p2www/pages/site/docs/protocol/i2cp.html:558
 msgid "Base64 SessionKey (44 characters)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:559
+#: i2p2www/pages/site/docs/protocol/i2cp.html:567
 msgid ""
 "Guaranteed is disabled;\n"
 "None implemented in 0.8.1; None is the default as of 0.9.4"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:578
+#: i2p2www/pages/site/docs/protocol/i2cp.html:586
 msgid ""
 "Note: All arguments, including numbers, are strings. True/false values "
 "are case-insensitive strings.\n"
@@ -18452,11 +13084,11 @@ msgid ""
 "All option names are case-sensitive."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:584
+#: i2p2www/pages/site/docs/protocol/i2cp.html:592
 msgid "I2CP Payload Data Format and Multiplexing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:585
+#: i2p2www/pages/site/docs/protocol/i2cp.html:593
 #, python-format
 msgid ""
 "The end-to-end messages handled by I2CP (i.e. the data sent by the client"
@@ -18477,61 +13109,52 @@ msgid ""
 "to work reliably in the presence of multiple channels."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:599
+#: i2p2www/pages/site/docs/protocol/i2cp.html:607
 msgid ""
 "The gzip function cannot be completely turned off, however setting "
 "i2cp.gzip=false\n"
 "turns the gzip effort setting to 0, which may save a little CPU."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:605
+#: i2p2www/pages/site/docs/protocol/i2cp.html:613
 #: i2p2www/pages/site/docs/protocol/i2np.html:33
 msgid "Bytes"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:606
-#: i2p2www/pages/site/get-involved/index.html:38
+#: i2p2www/pages/site/docs/protocol/i2cp.html:614
 msgid "Content"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:611
+#: i2p2www/pages/site/docs/protocol/i2cp.html:619
 msgid "Gzip header"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:616
+#: i2p2www/pages/site/docs/protocol/i2cp.html:624
 msgid "Gzip flags"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:621
+#: i2p2www/pages/site/docs/protocol/i2cp.html:629
 msgid "I2P Source port (Gzip mtime)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:626
+#: i2p2www/pages/site/docs/protocol/i2cp.html:634
 msgid "I2P Destination port (Gzip mtime)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:631
+#: i2p2www/pages/site/docs/protocol/i2cp.html:639
 msgid "Gzip xflags"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:636
+#: i2p2www/pages/site/docs/protocol/i2cp.html:644
 msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:640
+#: i2p2www/pages/site/docs/protocol/i2cp.html:648
 msgid ""
 "Data integrity is verified with the standard gzip CRC-32 as\n"
 "specified by RFC 1952."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:648
-msgid "Implement I2CP and the streaming library in another programming language."
-msgstr ""
-
-#: i2p2www/pages/site/docs/protocol/i2cp.html:652
-msgid "Is the initial Get Date / Set Date handshake required?"
-msgstr ""
-
 #: i2p2www/pages/site/docs/protocol/i2cp.html:656
 msgid ""
 "The current authorization mechanism could be modified to use hashed "
@@ -18540,11 +13163,12 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/protocol/i2cp.html:660
 msgid ""
-"Private Keys are included in the Create Lease Set message,\n"
-"are they really required? Revocation is unimplemented."
+"The Signing Private Keys is included in the Create Lease Set message,\n"
+"it is not required. Revocation is unimplemented.\n"
+"It should be replaced with random data or removed."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2cp.html:665
+#: i2p2www/pages/site/docs/protocol/i2cp.html:666
 #, python-format
 msgid ""
 "Some improvements may be able to use messages previously defined but not "
@@ -18556,6 +13180,10 @@ msgid ""
 "Common Data Structures Specification Version 0.9."
 msgstr ""
 
+#: i2p2www/pages/site/docs/protocol/i2np.html:3
+msgid "June 2013"
+msgstr ""
+
 #: i2p2www/pages/site/docs/protocol/i2np.html:6
 msgid "I2P Network Protocol"
 msgstr ""
@@ -18692,12 +13320,12 @@ msgid ""
 "which is wrapped in a DataMessage."
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2np.html:92
-msgid "Type"
+#: i2p2www/pages/site/docs/protocol/i2np.html:91
+msgid "Message"
 msgstr ""
 
-#: i2p2www/pages/site/docs/protocol/i2np.html:94
-msgid "Priority"
+#: i2p2www/pages/site/docs/protocol/i2np.html:92
+msgid "Type"
 msgstr ""
 
 #: i2p2www/pages/site/docs/protocol/i2np.html:95
@@ -19141,8 +13769,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/blockfile.html:172
 #, python-format
 msgid ""
-"\"%%__INFO__%%\" is the master database skiplist with String/Properties "
-"key/value entries containing only one entry:"
+"%(INFO)s is the master database skiplist with String/Properties key/value"
+" entries containing only one entry:"
 msgstr ""
 
 #: i2p2www/pages/site/docs/spec/blockfile.html:184
@@ -19152,8 +13780,8 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/blockfile.html:185
 #, python-format
 msgid ""
-"\"%%__REVERSE__%%\" is the reverse lookup skiplist with "
-"Integer/Properties key/value entries\n"
+"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties "
+"key/value entries\n"
 "    (as of database version 2):"
 msgstr ""
 
@@ -19212,14 +13840,13 @@ msgstr ""
 #: i2p2www/pages/site/docs/spec/common-structures.html:166
 #: i2p2www/pages/site/docs/spec/common-structures.html:178
 #: i2p2www/pages/site/docs/spec/common-structures.html:231
-#: i2p2www/pages/site/docs/spec/common-structures.html:298
-#: i2p2www/pages/site/docs/spec/common-structures.html:347
-#: i2p2www/pages/site/docs/spec/common-structures.html:391
-#: i2p2www/pages/site/docs/spec/common-structures.html:438
-#: i2p2www/pages/site/docs/spec/common-structures.html:573
-#: i2p2www/pages/site/docs/spec/common-structures.html:630
+#: i2p2www/pages/site/docs/spec/common-structures.html:314
+#: i2p2www/pages/site/docs/spec/common-structures.html:363
+#: i2p2www/pages/site/docs/spec/common-structures.html:415
+#: i2p2www/pages/site/docs/spec/common-structures.html:462
+#: i2p2www/pages/site/docs/spec/common-structures.html:597
+#: i2p2www/pages/site/docs/spec/common-structures.html:660
 #: i2p2www/pages/site/docs/spec/streaming.html:35
-#: i2p2www/pages/site/get-involved/develop/applications.html:8
 msgid "Contents"
 msgstr ""
 
@@ -19417,64 +14044,87 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:273
 msgid ""
-"Mappings contained in I2NP messages (i.e. in a RouterAddress or "
-"RouterInfo)\n"
-"must be sorted by key so that the signature will be invariant."
+"The encoding allows duplicate keys, however in any usage where the "
+"mapping is signed,\n"
+"duplicates may cause a signature failure."
 msgstr ""
 
 #: i2p2www/pages/site/docs/spec/common-structures.html:278
 msgid ""
+"Mappings contained in I2NP messages (i.e. in a RouterAddress or "
+"RouterInfo)\n"
+"must be sorted by key so that the signature will be invariant.\n"
+"Duplicate keys are not allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:284
+#, python-format
+msgid ""
+"Mappings contained in an I2CP "
+"SessionConfig\n"
+"must be sorted by key so that the signature will be invariant.\n"
+"Duplicate keys are not allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:290
+msgid ""
+"While it is application-dependent, keys and values are generally case-"
+"sensitive."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:294
+msgid ""
 "Key and value string length limits are 255 bytes (not characters) each, "
 "plus the length byte. Length byte may be 0."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:282
+#: i2p2www/pages/site/docs/spec/common-structures.html:298
 msgid ""
 "Total length limit is 65535 bytes, plus the 2 byte size field, or 65537 "
 "total."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:291
+#: i2p2www/pages/site/docs/spec/common-structures.html:307
 msgid "Common structure specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:295
+#: i2p2www/pages/site/docs/spec/common-structures.html:311
 msgid "Defines the way to uniquely identify a particular router\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:299
+#: i2p2www/pages/site/docs/spec/common-structures.html:315
 msgid ""
 "PublicKey followed by SigningPublicKey and then a Certificate\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:336
+#: i2p2www/pages/site/docs/spec/common-structures.html:352
 msgid ""
 "The certificate for a RouterIdentity is currently unused and is always "
 "NULL."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:344
+#: i2p2www/pages/site/docs/spec/common-structures.html:360
 msgid ""
 "A Destination defines a particular endpoint to which messages can be "
 "directed for secure delivery.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:348
+#: i2p2www/pages/site/docs/spec/common-structures.html:364
 msgid ""
 "PublicKey followed by a SigningPublicKey and then a Certificate\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:388
+#: i2p2www/pages/site/docs/spec/common-structures.html:412
 msgid ""
 "Defines the authorization for a particular tunnel to receive messages "
 "targeting a Destination.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:392
+#: i2p2www/pages/site/docs/spec/common-structures.html:416
 msgid ""
 "SHA256 Hash of the\n"
 "RouterIdentity of the gateway "
@@ -19482,11 +14132,11 @@ msgid ""
 "end Date\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:423
+#: i2p2www/pages/site/docs/spec/common-structures.html:447
 msgid "Total size: 44 bytes"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:433
+#: i2p2www/pages/site/docs/spec/common-structures.html:457
 msgid ""
 "Contains all of the currently authorized Leases for a particular Destination.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:439
+#: i2p2www/pages/site/docs/spec/common-structures.html:463
 msgid ""
 "Destination, followed by a PublicKey for encryption, then a SigningPrivateKey"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:531
+#: i2p2www/pages/site/docs/spec/common-structures.html:555
 msgid ""
 "The public key of the destination was used for the old i2cp-to-i2cp "
 "encryption\n"
-"which was disabled in version 0.6, it is currently unused?"
+"which was disabled in version 0.6, it is currently unused."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:536
+#: i2p2www/pages/site/docs/spec/common-structures.html:560
 #, python-format
 msgid ""
 "The encryption key is used for end-to-end Integer defining the relative cost "
 "of using the address, where 0 is free and 255 is expensive, followed by "
@@ -19590,21 +14240,29 @@ msgid ""
 "IP address, port number, email address, URL, etc.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:609
+#: i2p2www/pages/site/docs/spec/common-structures.html:633
 msgid "Cost is typically 5 or 6 for SSU, and 10 or 11 for NTCP."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:613
+#: i2p2www/pages/site/docs/spec/common-structures.html:637
 msgid ""
 "Expiration is currently unused, always null (all zeroes)).\n"
 "As of release 0.9.3, the expiration is assumed zero and not stored, so "
 "any non-zero expiration\n"
 "will fail in the RouterInfo signature verification.\n"
 "Implementing expiration (or another use for these bytes) will be a "
-"backwards-incompatible change."
+"backwards-incompatible change.\n"
+"Routers MUST set this field to all zeros."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:626
+#: i2p2www/pages/site/docs/spec/common-structures.html:645
+msgid ""
+"The following options, while not required, are standard and expected to "
+"be present in most router addresses:\n"
+"\"host\" (an IPv4 or IPv6 address or host name) and \"port\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:656
 msgid ""
 "Defines all of the data that a router wants to publish for the network to"
 " see. The RouterInfo is one of two "
@@ -19614,27 +14272,34 @@ msgid ""
 "the contained RouterIdentity.\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:631
+#: i2p2www/pages/site/docs/spec/common-structures.html:661
 msgid ""
 "RouterIdentity followed by the Date, when the entry was published\n"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:710
+#: i2p2www/pages/site/docs/spec/common-structures.html:741
 msgid ""
 "The peer_size Integer may be followed by a list of that many router "
 "hashes.\n"
 "This is currently unused. It was intended for a form of restricted "
-"routes, which is unimplemented.\n"
+"routes, which is unimplemented."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:715
+#: i2p2www/pages/site/docs/spec/common-structures.html:746
 msgid ""
 "The signature may be verified using the signing public key of the "
-"router_ident.\n"
+"router_ident."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/common-structures.html:723
+#: i2p2www/pages/site/docs/spec/common-structures.html:750
+#, python-format
+msgid ""
+"See the network database page\n"
+"for standard options that are expected to be present in all router infos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:760
 #, python-format
 msgid ""
 "Defined in the Tunnel Message "
@@ -19766,10 +14431,18 @@ msgstr ""
 msgid "Enable/disable for each installed plugin."
 msgstr ""
 
+#: i2p2www/pages/site/docs/spec/configuration.html:70
+msgid "Router"
+msgstr ""
+
 #: i2p2www/pages/site/docs/spec/configuration.html:71
 msgid "Configured via /configadvanced in the router console."
 msgstr ""
 
+#: i2p2www/pages/site/docs/spec/configuration.html:75
+msgid "Applications"
+msgstr ""
+
 #: i2p2www/pages/site/docs/spec/configuration.html:78
 msgid "See documentation in SusiDNS."
 msgstr ""
@@ -19975,44 +14648,64 @@ msgstr ""
 
 #: i2p2www/pages/site/docs/spec/updates.html:35
 msgid ""
+"Parameters in the i2p.release entry are as follows.\n"
+"All keys are case-insensitive. All values must be enclosed in double "
+"quotes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:73
+msgid ""
 "The elements may be included inside XML comments to prevent "
 "interpretation by browsers.\n"
-"The i2p.release element and version are required. All others are optional"
-" and are\n"
-"currently unused."
+"The i2p.release element and version are required. All others are "
+"optional.\n"
+"NOTE: Due to parser limitations an entire element must be on a single "
+"line."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:41
-msgid ""
-"The news source is trusted only to indicate that a new version is "
-"available.\n"
-"It does not specify the URL of the update, the checksum, or any other "
-"information."
-msgstr ""
-
-#: i2p2www/pages/site/docs/spec/updates.html:47
+#: i2p2www/pages/site/docs/spec/updates.html:80
 msgid "Update File Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:48
+#: i2p2www/pages/site/docs/spec/updates.html:81
+msgid ""
+"As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n"
+"use the \"su3\" file format specified below.\n"
+"Approved release signers will use 4096-bit RSA keys.\n"
+"The X.509 public key certificates for these signers are distributed in "
+"the router installation packages.\n"
+"The updates may contain certificates for new, approved signers, and/or "
+"contain\n"
+"a list of certificates to delete for revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:91
+msgid "Old Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:92
+msgid "This format is obsolte as of release 0.9.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:95
 msgid ""
 "The signed update file, traditionally named i2pupdate.sud,\n"
 "is simply a zip file with a prepended 56 byte header.\n"
 "The header contains:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:54
+#: i2p2www/pages/site/docs/spec/updates.html:101
 #, python-format
 msgid ""
 "A 40-byte DSA "
 "signature"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:57
+#: i2p2www/pages/site/docs/spec/updates.html:104
 msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:62
+#: i2p2www/pages/site/docs/spec/updates.html:109
 #, python-format
 msgid ""
 "The signature covers only the zip archive - not the prepended version.\n"
@@ -20023,14 +14716,14 @@ msgid ""
 " managers."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:68
+#: i2p2www/pages/site/docs/spec/updates.html:115
 msgid ""
 "For version comparison purposes, version fields contain [0-9]*, field "
 "separators are\n"
 "'-', '_', and '.', and all other characters are ignored."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:73
+#: i2p2www/pages/site/docs/spec/updates.html:120
 msgid ""
 "As of version 0.8.8, the version must also be specified as a zip file "
 "comment in UTF-8,\n"
@@ -20042,11 +14735,11 @@ msgid ""
 "This prevents spoofing of the version number in the header."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:81
+#: i2p2www/pages/site/docs/spec/updates.html:128
 msgid "Download and Installation"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:82
+#: i2p2www/pages/site/docs/spec/updates.html:129
 msgid ""
 "The router first downloads the header of the update file from one in a "
 "configurable list of I2P URLs,\n"
@@ -20062,21 +14755,21 @@ msgid ""
 "explained above."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:93
+#: i2p2www/pages/site/docs/spec/updates.html:140
 msgid "The zip file is extracted in the base $I2P installation directory."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:97
+#: i2p2www/pages/site/docs/spec/updates.html:144
 msgid ""
 "As of release 0.7.12, the router supports Pack200 decompression.\n"
 "Files inside the zip archive with a .jar.pack or .war.pack suffix\n"
 "are transparently decompressed to a .jar or .war file.\n"
 "Update files containing .pack files are traditionally named with a '.su2'"
 " suffix.\n"
-"Pack200 shrinks the update files by about 60%."
+"Pack200 shrinks the update files by about 60%."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:105
+#: i2p2www/pages/site/docs/spec/updates.html:152
 msgid ""
 "As of release 0.8.7, the router will delete the libjbigi.so and "
 "libjcpuid.so files\n"
@@ -20085,93 +14778,95 @@ msgid ""
 "be extracted from jbigi.jar."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:111
+#: i2p2www/pages/site/docs/spec/updates.html:158
 msgid ""
 "As of release 0.8.12, if the zip archive contains a file deletelist.txt, "
 "the router will\n"
 "delete the files listed there. The format is:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:116
+#: i2p2www/pages/site/docs/spec/updates.html:163
 msgid "One file name per line"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:117
+#: i2p2www/pages/site/docs/spec/updates.html:164
 msgid ""
 "All file names are relative to the installation directory; no absolute "
 "file names allowed, no files starting with \"..\""
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:118
+#: i2p2www/pages/site/docs/spec/updates.html:165
 msgid "Comments start with '#'"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:121
+#: i2p2www/pages/site/docs/spec/updates.html:168
 msgid "The router will then delete the deletelist.txt file."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:126
+#: i2p2www/pages/site/docs/spec/updates.html:173
 msgid "New \"su3\" Update File Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:128
-msgid "This specification is preliminary and is not yet implemented."
+#: i2p2www/pages/site/docs/spec/updates.html:175
+msgid ""
+"This specification is used for router updates and reseed data as of "
+"release 0.9.9."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:132
-msgid "Issues with existing .sud/.su2 format:"
+#: i2p2www/pages/site/docs/spec/updates.html:179
+msgid "Issues with the previous .sud/.su2 format:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:134
+#: i2p2www/pages/site/docs/spec/updates.html:181
 msgid "No magic number or flags"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:137
+#: i2p2www/pages/site/docs/spec/updates.html:184
 msgid "No way to specify compression, pack200 or not, or signing algo"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:140
+#: i2p2www/pages/site/docs/spec/updates.html:187
 msgid ""
 "Version is not covered by signature, so it is enforced by requiring it\n"
 "to be in the zip file comment (for router files) or in the plugin.config\n"
 "file (for plugins)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:145
+#: i2p2www/pages/site/docs/spec/updates.html:192
 msgid "Signer not specified so verifier must try all known keys"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:148
+#: i2p2www/pages/site/docs/spec/updates.html:195
 msgid "Signature-before-data format requires two passes to generate file"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:154
+#: i2p2www/pages/site/docs/spec/updates.html:201
 msgid "Goals:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:157
+#: i2p2www/pages/site/docs/spec/updates.html:204
 msgid "Fix above problems"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:160
+#: i2p2www/pages/site/docs/spec/updates.html:207
 msgid "Migrate to more secure signature algorithm"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:163
+#: i2p2www/pages/site/docs/spec/updates.html:210
 msgid ""
 "Keep version info in same format and offset for compatibility with\n"
 "existing version checkers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:169
+#: i2p2www/pages/site/docs/spec/updates.html:216
 msgid "Specification:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:217
+#: i2p2www/pages/site/docs/spec/updates.html:275
 msgid "All unused fields must be set to 0 for compatibility with future versions."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:224
+#: i2p2www/pages/site/docs/spec/updates.html:282
 msgid ""
 "The network will eventually grow too large for update over HTTP.\n"
 "The built-in BitTorrent client, i2psnark, may be used as a distributed "
@@ -20179,7 +14874,7 @@ msgid ""
 "This development effort is ongoing and should be completed by late 2013."
 msgstr ""
 
-#: i2p2www/pages/site/docs/spec/updates.html:229
+#: i2p2www/pages/site/docs/spec/updates.html:287
 msgid ""
 "The router update mechanism is part of the web router console.\n"
 "There is currently no provision for updates of an embedded router lacking"
@@ -20190,10 +14885,6 @@ msgstr ""
 msgid "Transport Overview"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:3
-msgid "April 2013"
-msgstr ""
-
 #: i2p2www/pages/site/docs/transport/index.html:6
 msgid "Transports in I2P"
 msgstr ""
@@ -20240,35 +14931,45 @@ msgid "The transport subsystem in I2P provides the following services:"
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/index.html:37
+#, python-format
 msgid ""
-"Maintain a set of router addresses, one or more for each transport,\n"
-"that the router publishes as its global contact information (the "
-"RouterInfo)"
-msgstr ""
-
-#: i2p2www/pages/site/docs/transport/index.html:41
-msgid "Selection of the best transport for each outgoing message"
+"Reliable delivery of I2NP messages.\n"
+"Transports support I2NP message delivery ONLY.\n"
+"They are not general-purpose data pipes."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/index.html:42
+msgid ""
+"Maintain a set of router addresses, one or more for each transport,\n"
+"that the router publishes as its global contact information (the "
+"RouterInfo).\n"
+"Each transport may connect using one of these addresses, which may be\n"
+"IPv4 or (as of version 0.9.8) IPv6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:48
+msgid "Selection of the best transport for each outgoing message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:49
 msgid "Queueing of outbound messages by priority"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:43
+#: i2p2www/pages/site/docs/transport/index.html:50
 msgid ""
 "Bandwidth limiting, both outbound and inbound, according to router "
 "configuration"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:44
+#: i2p2www/pages/site/docs/transport/index.html:51
 msgid "Setup and teardown of transport connections"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:45
+#: i2p2www/pages/site/docs/transport/index.html:52
 msgid "Encryption of point-to-point communications"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:46
+#: i2p2www/pages/site/docs/transport/index.html:53
 msgid ""
 "Maintenance of connection limits for each transport, implementation of "
 "various thresholds for these limits,\n"
@@ -20276,80 +14977,81 @@ msgid ""
 "operational changes based on the status"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:50
+#: i2p2www/pages/site/docs/transport/index.html:57
 msgid "Firewall port opening using UPnP (Universal Plug and Play)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:51
+#: i2p2www/pages/site/docs/transport/index.html:58
 msgid "Cooperative NAT/Firewall traversal"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:52
+#: i2p2www/pages/site/docs/transport/index.html:59
 msgid ""
 "Local IP detection by various methods, including UPnP, inspection of "
 "incoming connections, and enumeration of network devices"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:53
+#: i2p2www/pages/site/docs/transport/index.html:60
 msgid ""
 "Coordination of firewall status and local IP, and changes to either, "
 "among the transports"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:54
-#: i2p2www/pages/site/docs/transport/ssu.html:32
+#: i2p2www/pages/site/docs/transport/index.html:61
+#: i2p2www/pages/site/docs/transport/ssu.html:33
 msgid ""
 "Communication of firewall status and local IP, and changes to either, to "
 "the router and the user interface"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:55
+#: i2p2www/pages/site/docs/transport/index.html:62
 msgid ""
 "Determination of a consensus clock, which is used to periodically update "
 "the router's clock, as a backup for NTP"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:56
+#: i2p2www/pages/site/docs/transport/index.html:63
 msgid ""
 "Maintenance of status for each peer, including whether it is connected, "
 "whether it was recently connected,\n"
 "and whether it was reachable in the last attempt"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:60
+#: i2p2www/pages/site/docs/transport/index.html:67
 msgid "Qualification of valid IP addresses according to a local rule set"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:61
+#: i2p2www/pages/site/docs/transport/index.html:68
 msgid ""
 "Honoring the automated and manual lists of banned peers maintained by the"
 " router,\n"
 "and refusing outbound and inbound connections to those peers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:68
+#: i2p2www/pages/site/docs/transport/index.html:75
 msgid "Transport Addresses"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:70
+#: i2p2www/pages/site/docs/transport/index.html:77
 msgid ""
 "The transport subsystem maintains a set of router addresses, each of "
 "which lists a transport method, IP, and port.\n"
 "These addresses constitute the advertised contact points, and are "
-"published by the router to the network database."
+"published by the router to the network database.\n"
+"Addresses may also contain an arbitrary set of additional options."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:75
+#: i2p2www/pages/site/docs/transport/index.html:83
 msgid "Typical scenarios are:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:77
+#: i2p2www/pages/site/docs/transport/index.html:85
 msgid ""
 "A router has no published addresses, so it is considered \"hidden\" and "
 "cannot receive incoming connections"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:78
+#: i2p2www/pages/site/docs/transport/index.html:86
 #, python-format
 msgid ""
 "A router is firewalled, and therefore publishes an SSU address which "
@@ -20358,22 +15060,22 @@ msgid ""
 "href=\"%(ssu)s\">the SSU spec for details)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:82
+#: i2p2www/pages/site/docs/transport/index.html:90
 msgid ""
 "A router is not firewalled or its NAT ports  are open; it publishes both "
 "NTCP and SSU addresses containing\n"
 "directly-accessible IP and ports."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:88
+#: i2p2www/pages/site/docs/transport/index.html:96
 msgid "Transport Selection"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:90
+#: i2p2www/pages/site/docs/transport/index.html:98
 #, python-format
 msgid ""
-"The transport system delivers I2NP messages. The"
-" transport selected for any message is\n"
+"The transport system delivers I2NP messages "
+"only. The transport selected for any message is\n"
 "independent of the upper-layer protocols and contents (router or client "
 "messages, whether an external application was using\n"
 "TCP or UDP to connect to I2P, whether the upper layer was using\n"
@@ -20385,7 +15087,7 @@ msgid ""
 "etc.)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:104
+#: i2p2www/pages/site/docs/transport/index.html:112
 msgid ""
 "For each outgoing message, the transport system solicits \"bids\" from "
 "each transport.\n"
@@ -20394,84 +15096,74 @@ msgid ""
 "A transport may refuse to bid."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:110
+#: i2p2www/pages/site/docs/transport/index.html:118
 msgid "Whether a transport bids, and with what value, depend on numerous factors:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:114
+#: i2p2www/pages/site/docs/transport/index.html:122
 msgid "Configuration of transport preferences"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:115
+#: i2p2www/pages/site/docs/transport/index.html:123
 msgid "Whether the transport is already connected to the peer"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:116
+#: i2p2www/pages/site/docs/transport/index.html:124
 msgid ""
 "The number of current connections compared to various connection limit "
 "thresholds"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:117
+#: i2p2www/pages/site/docs/transport/index.html:125
 msgid "Whether recent connection attempts to the peer have failed"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:118
+#: i2p2www/pages/site/docs/transport/index.html:126
 msgid ""
 "The size of the message, as different transports have different size "
 "limits"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:119
+#: i2p2www/pages/site/docs/transport/index.html:127
 msgid ""
 "Whether the peer can accept incoming connections for that transport, as "
 "advertised in its RouterInfo"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:120
+#: i2p2www/pages/site/docs/transport/index.html:128
 msgid "Whether the connection would be indirect (requiring introducers) or direct"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:121
+#: i2p2www/pages/site/docs/transport/index.html:129
 msgid "The peer's transport preference, as advertised in its RouterInfo"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:124
+#: i2p2www/pages/site/docs/transport/index.html:132
 msgid ""
 "In general, the bid values are selected so that two routers are only "
 "connected by a single transport\n"
 "at any one time. However, this is not a requirement."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:131
+#: i2p2www/pages/site/docs/transport/index.html:139
 msgid "New Transports and Future Work"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:133
+#: i2p2www/pages/site/docs/transport/index.html:141
 msgid "Additional transports may be developed, including:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:138
+#: i2p2www/pages/site/docs/transport/index.html:146
 msgid "A TLS/SSH look-alike transport"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:139
+#: i2p2www/pages/site/docs/transport/index.html:147
 msgid ""
 "An \"indirect\" transport for routers that are not reachable by all other"
 " routers (one form of \"restricted routes\")"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:142
-#, python-format
-msgid ""
-"IPv6: The existing transports must be enhanced to support multiple "
-"addresses within a single transport,\n"
-"including IPV6 addresses. Currently, a transport may only advertise a "
-"single IPV4 address.\n"
-"See this thread for discussion."
-msgstr ""
-
-#: i2p2www/pages/site/docs/transport/index.html:148
+#: i2p2www/pages/site/docs/transport/index.html:150
 msgid ""
 "Work continues on adjusting default connection limits for each transport."
 "\n"
@@ -20482,7 +15174,7 @@ msgid ""
 "routers that are behind restrictive state firewalls (restricted routes)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:155
+#: i2p2www/pages/site/docs/transport/index.html:157
 msgid ""
 "The current connection limits are higher for SSU than for NTCP, based on "
 "the assumption that\n"
@@ -20493,7 +15185,7 @@ msgid ""
 "that assumption is difficult to verify."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/index.html:162
+#: i2p2www/pages/site/docs/transport/index.html:164
 #, python-format
 msgid ""
 "Analyze Breaking and Improving Protocol "
@@ -20513,10 +15205,11 @@ msgid ""
 "The other is SSU.\n"
 "NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n"
 "Java NIO (new I/O) does not suffer from the 1 thread per connection "
-"issues of the old TCP transport."
+"issues of the old TCP transport.\n"
+"NTCP-over-IPv6 is supported as of version 0.9.8."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:15
+#: i2p2www/pages/site/docs/transport/ntcp.html:16
 msgid ""
 "By default, NTCP uses the IP/Port\n"
 "auto-detected by SSU. When enabled on config.jsp,\n"
@@ -20525,22 +15218,22 @@ msgid ""
 "Now you can enable inbound TCP without a static IP or dyndns service."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:23
+#: i2p2www/pages/site/docs/transport/ntcp.html:24
 msgid ""
 "The NTCP code within I2P is relatively lightweight (1/4 the size of the "
 "SSU code)\n"
 "because it uses the underlying Java TCP transport for reliable delivery."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:29
+#: i2p2www/pages/site/docs/transport/ntcp.html:30
 msgid "NTCP Protocol Specification"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:31
+#: i2p2www/pages/site/docs/transport/ntcp.html:32
 msgid "Standard Message Format"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:32
+#: i2p2www/pages/site/docs/transport/ntcp.html:33
 msgid ""
 "After establishment,\n"
 "the NTCP transport sends individual I2NP messages, with a simple "
@@ -20548,7 +15241,7 @@ msgid ""
 "The unencrypted message is encoded as follows:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:42
+#: i2p2www/pages/site/docs/transport/ntcp.html:43
 msgid ""
 "The data is then AES/256/CBC encrypted. The session key for the "
 "encryption\n"
@@ -20560,7 +15253,7 @@ msgid ""
 "encrypted message."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:50
+#: i2p2www/pages/site/docs/transport/ntcp.html:51
 msgid ""
 "0-15 bytes of padding are required to bring the total message length\n"
 "(including the six size and checksum bytes) to a multiple of 16.\n"
@@ -20569,39 +15262,39 @@ msgid ""
 "The minimum data size is 1."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:58
+#: i2p2www/pages/site/docs/transport/ntcp.html:59
 msgid "Time Sync Message Format"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:59
+#: i2p2www/pages/site/docs/transport/ntcp.html:60
 msgid ""
 "One special case is a metadata message where the sizeof(data) is 0.  In\n"
 "that case, the unencrypted message is encoded as:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:70
+#: i2p2www/pages/site/docs/transport/ntcp.html:71
 msgid ""
 "Total length: 16 bytes. The time sync message is sent at approximately 15"
 " minute intervals.\n"
 "The message is encrypted just as standard messages are."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:76
+#: i2p2www/pages/site/docs/transport/ntcp.html:77
 msgid "Checksums"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:77
+#: i2p2www/pages/site/docs/transport/ntcp.html:78
 #, python-format
 msgid ""
 "The standard and time sync messages use the Adler-32 checksum\n"
 "as defined in the ZLIB Specification."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:83
+#: i2p2www/pages/site/docs/transport/ntcp.html:84
 msgid "Establishment Sequence"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:84
+#: i2p2www/pages/site/docs/transport/ntcp.html:85
 msgid ""
 "In the establish state, there is a 4-phase message sequence to exchange "
 "DH keys and signatures.\n"
@@ -20610,31 +15303,31 @@ msgid ""
 "connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:98
+#: i2p2www/pages/site/docs/transport/ntcp.html:99
 msgid "Legend:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:99
+#: i2p2www/pages/site/docs/transport/ntcp.html:100
 msgid "256 byte DH public keys"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:103
+#: i2p2www/pages/site/docs/transport/ntcp.html:104
 msgid "timestamps (4 bytes, seconds since epoch)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:104
+#: i2p2www/pages/site/docs/transport/ntcp.html:105
 msgid "32 byte Session key"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:105
+#: i2p2www/pages/site/docs/transport/ntcp.html:106
 msgid "2 byte size of Alice identity to follow"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:108
+#: i2p2www/pages/site/docs/transport/ntcp.html:109
 msgid "DH Key Exchange"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:109
+#: i2p2www/pages/site/docs/transport/ntcp.html:110
 #, python-format
 msgid ""
 "The initial 2048-bit DH key exchange\n"
@@ -20642,7 +15335,7 @@ msgid ""
 "ElGamal encryption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:115
+#: i2p2www/pages/site/docs/transport/ntcp.html:116
 msgid ""
 "The DH key exchange consists of a number of steps, displayed below.\n"
 "The mapping between these steps and the messages sent between I2P "
@@ -20650,51 +15343,54 @@ msgid ""
 "is marked in bold."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:121
-msgid ""
-"Alice generates a secret 226-bit integer x. She then calculates X ="
-" g^x mod p."
-msgstr ""
-
 #: i2p2www/pages/site/docs/transport/ntcp.html:122
-msgid "Alice sends X to Bob (Message 1)."
+msgid ""
+"Alice generates a secret integer x. She then calculates X = g^x mod"
+" p."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:123
-msgid ""
-"Bob generates a secret 226-bit integer y. He then calculates Y = "
-"g^y mod p."
+msgid "Alice sends X to Bob (Message 1)."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:124
-msgid "Bob sends Y to Alice.(Message 2)"
+msgid ""
+"Bob generates a secret integer y. He then calculates Y = g^y mod "
+"p."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:125
-msgid "Alice can now compute sessionKey = Y^x mod p."
+msgid "Bob sends Y to Alice.(Message 2)"
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:126
-msgid "Bob can now compute sessionKey = X^y mod p."
+msgid "Alice can now compute sessionKey = Y^x mod p."
 msgstr ""
 
 #: i2p2www/pages/site/docs/transport/ntcp.html:127
+msgid "Bob can now compute sessionKey = X^y mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:128
 msgid ""
 "Both Alice and Bob now have a shared key sessionKey = g^(x*y) mod "
 "p."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:129
+#: i2p2www/pages/site/docs/transport/ntcp.html:130
+#, python-format
 msgid ""
 "The sessionKey is then used to exchange identities in Message 3 "
-"and Message 4."
+"and Message 4.\n"
+"The exponent (x and y) length for the DH exchange is documented on the\n"
+"cryptography page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:133
+#: i2p2www/pages/site/docs/transport/ntcp.html:136
 msgid "Message 1 (Session Request)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:134
+#: i2p2www/pages/site/docs/transport/ntcp.html:137
 #, python-format
 msgid ""
 "This is the DH request. Alice already has Bob's\n"
@@ -20707,79 +15403,79 @@ msgid ""
 "Alice sends Bob:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:147
-#: i2p2www/pages/site/docs/transport/ntcp.html:190
-#: i2p2www/pages/site/docs/transport/ntcp.html:270
-#: i2p2www/pages/site/docs/transport/ntcp.html:353
+#: i2p2www/pages/site/docs/transport/ntcp.html:150
+#: i2p2www/pages/site/docs/transport/ntcp.html:193
+#: i2p2www/pages/site/docs/transport/ntcp.html:273
+#: i2p2www/pages/site/docs/transport/ntcp.html:356
 msgid "Size:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:149
+#: i2p2www/pages/site/docs/transport/ntcp.html:152
 msgid "Contents:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:167
+#: i2p2www/pages/site/docs/transport/ntcp.html:170
 msgid "256 byte X from Diffie Hellman"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:169
+#: i2p2www/pages/site/docs/transport/ntcp.html:172
 #, python-format
 msgid ""
 "SHA256 Hash(X) xored with SHA256 Hash(Bob's Router Identity)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:176
-#: i2p2www/pages/site/docs/transport/ntcp.html:257
-#: i2p2www/pages/site/docs/transport/ntcp.html:334
+#: i2p2www/pages/site/docs/transport/ntcp.html:179
+#: i2p2www/pages/site/docs/transport/ntcp.html:260
+#: i2p2www/pages/site/docs/transport/ntcp.html:337
 msgid "Notes:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:177
+#: i2p2www/pages/site/docs/transport/ntcp.html:180
 msgid ""
 "Bob verifies HXxorHI using his own router hash. If it does not verify,\n"
 "Alice has contacted the wrong router, and Bob drops the connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:183
+#: i2p2www/pages/site/docs/transport/ntcp.html:186
 msgid "Message 2 (Session Created)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:184
+#: i2p2www/pages/site/docs/transport/ntcp.html:187
 msgid "This is the DH reply. Bob sends Alice:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:192
-#: i2p2www/pages/site/docs/transport/ntcp.html:272
-#: i2p2www/pages/site/docs/transport/ntcp.html:355
+#: i2p2www/pages/site/docs/transport/ntcp.html:195
+#: i2p2www/pages/site/docs/transport/ntcp.html:275
+#: i2p2www/pages/site/docs/transport/ntcp.html:358
 msgid "Unencrypted Contents:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:214
-#: i2p2www/pages/site/docs/transport/ntcp.html:248
+#: i2p2www/pages/site/docs/transport/ntcp.html:217
+#: i2p2www/pages/site/docs/transport/ntcp.html:251
 msgid "256 byte Y from Diffie Hellman"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:216
+#: i2p2www/pages/site/docs/transport/ntcp.html:219
 msgid "SHA256 Hash(X concatenated with Y)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:219
-#: i2p2www/pages/site/docs/transport/ntcp.html:304
+#: i2p2www/pages/site/docs/transport/ntcp.html:222
+#: i2p2www/pages/site/docs/transport/ntcp.html:307
 msgid "4 byte timestamp (seconds since the epoch)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:221
+#: i2p2www/pages/site/docs/transport/ntcp.html:224
 msgid "12 bytes random data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:226
-#: i2p2www/pages/site/docs/transport/ntcp.html:316
-#: i2p2www/pages/site/docs/transport/ntcp.html:383
+#: i2p2www/pages/site/docs/transport/ntcp.html:229
+#: i2p2www/pages/site/docs/transport/ntcp.html:319
+#: i2p2www/pages/site/docs/transport/ntcp.html:386
 msgid "Encrypted Contents:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:250
+#: i2p2www/pages/site/docs/transport/ntcp.html:253
 #, python-format
 msgid ""
 "48 bytes AES encrypted using the DH "
@@ -20787,38 +15483,38 @@ msgid ""
 "                  the last 16 bytes of Y as the IV"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:258
+#: i2p2www/pages/site/docs/transport/ntcp.html:261
 msgid ""
 "Alice may drop the connection if the clock skew with Bob is too high as "
 "calculated using tsB."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:263
+#: i2p2www/pages/site/docs/transport/ntcp.html:266
 msgid "Message 3 (Session Confirm A)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:264
+#: i2p2www/pages/site/docs/transport/ntcp.html:267
 msgid ""
 "This contains Alice's router identity, and a DSA signature of the "
 "critical data. Alice sends Bob:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:298
+#: i2p2www/pages/site/docs/transport/ntcp.html:301
 msgid "2 byte size of Alice's router identity to follow (should always be 387)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:300
+#: i2p2www/pages/site/docs/transport/ntcp.html:303
 #, python-format
 msgid ""
 "Alice's 387 byte Router Identity"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:306
+#: i2p2www/pages/site/docs/transport/ntcp.html:309
 msgid "15 bytes random data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:308
+#: i2p2www/pages/site/docs/transport/ntcp.html:311
 #, python-format
 msgid ""
 "the 40 byte DSA "
@@ -20834,7 +15530,7 @@ msgid ""
 "href=\"%(commonstructures)s#struct_RouterIdentity\">Router Identity"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:326
+#: i2p2www/pages/site/docs/transport/ntcp.html:329
 #, python-format
 msgid ""
 "448 bytes AES encrypted using the DH"
@@ -20843,25 +15539,25 @@ msgid ""
 "of message #1) as the IV"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:336
+#: i2p2www/pages/site/docs/transport/ntcp.html:339
 msgid "Bob verifies the signature, and on failure, drops the connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:339
+#: i2p2www/pages/site/docs/transport/ntcp.html:342
 msgid ""
 "Bob may drop the connection if the clock skew with Alice is too high as "
 "calculated using tsA."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:346
+#: i2p2www/pages/site/docs/transport/ntcp.html:349
 msgid "Message 4 (Session Confirm B)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:347
+#: i2p2www/pages/site/docs/transport/ntcp.html:350
 msgid "This is a DSA signature of the critical data. Bob sends Alice:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:372
+#: i2p2www/pages/site/docs/transport/ntcp.html:375
 #, python-format
 msgid ""
 "the 40 byte DSA "
@@ -20877,11 +15573,11 @@ msgid ""
 "href=\"%(commonstructures)s#struct_RouterIdentity\">Router Identity"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:378
+#: i2p2www/pages/site/docs/transport/ntcp.html:381
 msgid "8 bytes random data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:393
+#: i2p2www/pages/site/docs/transport/ntcp.html:396
 #, python-format
 msgid ""
 "48 bytes AES encrypted using the DH "
@@ -20890,15 +15586,15 @@ msgid ""
 "#2 as the IV"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:401
+#: i2p2www/pages/site/docs/transport/ntcp.html:404
 msgid "Alice verifies the signature, and on failure, drops the connection."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:408
+#: i2p2www/pages/site/docs/transport/ntcp.html:411
 msgid "After Establishment"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:409
+#: i2p2www/pages/site/docs/transport/ntcp.html:412
 msgid ""
 "The connection is established, and standard or time sync messages may be "
 "exchanged.\n"
@@ -20910,11 +15606,11 @@ msgid ""
 " the next IV."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:418
+#: i2p2www/pages/site/docs/transport/ntcp.html:421
 msgid "Check Connection Message"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:419
+#: i2p2www/pages/site/docs/transport/ntcp.html:422
 msgid ""
 "Alternately, when Bob receives a connection, it could be a\n"
 "check connection (perhaps prompted by Bob asking for someone\n"
@@ -20924,54 +15620,54 @@ msgid ""
 "A check info connection will receive 256 bytes containing:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:428
+#: i2p2www/pages/site/docs/transport/ntcp.html:431
 msgid "32 bytes of uninterpreted, ignored data"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:429
+#: i2p2www/pages/site/docs/transport/ntcp.html:432
 msgid "1 byte size"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:430
+#: i2p2www/pages/site/docs/transport/ntcp.html:433
 msgid ""
 "that many bytes making up the local router's IP address (as reached by "
 "the remote side)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:431
+#: i2p2www/pages/site/docs/transport/ntcp.html:434
 msgid "2 byte port number that the local router was reached on"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:432
+#: i2p2www/pages/site/docs/transport/ntcp.html:435
 msgid ""
 "4 byte i2p network time as known by the remote side (seconds since the "
 "epoch)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:433
+#: i2p2www/pages/site/docs/transport/ntcp.html:436
 msgid "uninterpreted padding data, up to byte 223"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:434
+#: i2p2www/pages/site/docs/transport/ntcp.html:437
 msgid ""
 "xor of the local router's identity hash and the SHA256 of bytes 32 "
 "through bytes 223"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:438
+#: i2p2www/pages/site/docs/transport/ntcp.html:441
 msgid "Discussion"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:439
+#: i2p2www/pages/site/docs/transport/ntcp.html:442
 #, python-format
 msgid "Now on the NTCP Discussion Page."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:445
+#: i2p2www/pages/site/docs/transport/ntcp.html:448
 msgid "The maximum message size should be increased to approximately 32 KB."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:449
+#: i2p2www/pages/site/docs/transport/ntcp.html:452
 msgid ""
 "A set of fixed packet sizes may be appropriate to further hide the data \n"
 "fragmentation to external adversaries, but the tunnel, garlic, and end to"
@@ -20982,19 +15678,19 @@ msgid ""
 "to create a limited number of message sizes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:457
+#: i2p2www/pages/site/docs/transport/ntcp.html:460
 msgid ""
 "Memory utilization (including that of the kernel) for NTCP should be "
 "compared to that for SSU."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:461
+#: i2p2www/pages/site/docs/transport/ntcp.html:464
 msgid ""
 "Can the establishment messages be randomly padded somehow, to frustrate\n"
 "identification of I2P traffic based on initial packet sizes?"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ntcp.html:466
+#: i2p2www/pages/site/docs/transport/ntcp.html:469
 msgid "Review and possibly disable 'check connection'"
 msgstr ""
 
@@ -21021,14 +15717,15 @@ msgid ""
 "SSU is the newer of the two transports,\n"
 "introduced in I2P release 0.6.\n"
 "In a standard I2P installation, the router uses both NTCP and SSU for "
-"outbound connections."
+"outbound connections.\n"
+"SSU-over-IPv6 is supported as of version 0.9.8."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:21
+#: i2p2www/pages/site/docs/transport/ssu.html:22
 msgid "SSU Services"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:23
+#: i2p2www/pages/site/docs/transport/ssu.html:24
 msgid ""
 "Like the NTCP transport, SSU provides reliable, encrypted, connection-"
 "oriented, point-to-point data transport.\n"
@@ -21036,33 +15733,33 @@ msgid ""
 "including:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:29
+#: i2p2www/pages/site/docs/transport/ssu.html:30
 msgid ""
 "Cooperative NAT/Firewall traversal using introducers"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:30
+#: i2p2www/pages/site/docs/transport/ssu.html:31
 msgid ""
 "Local IP detection by inspection of incoming packets and peer testing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:31
+#: i2p2www/pages/site/docs/transport/ssu.html:32
 msgid ""
 "Communication of firewall status and local IP, and changes to either to "
 "NTCP"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:36
+#: i2p2www/pages/site/docs/transport/ssu.html:37
 msgid "Protocol Details"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:38
+#: i2p2www/pages/site/docs/transport/ssu.html:39
 msgid "Congestion control"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:40
+#: i2p2www/pages/site/docs/transport/ssu.html:41
 msgid ""
 "SSU's need for only semireliable delivery, TCP-friendly operation,\n"
 "and the capacity for high throughput allows a great deal of latitude in\n"
@@ -21070,7 +15767,7 @@ msgid ""
 "meant to be both efficient in bandwidth as well as simple to implement."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:47
+#: i2p2www/pages/site/docs/transport/ssu.html:48
 msgid ""
 "Packets are scheduled according to the router's policy, taking care\n"
 "not to exceed the router's outbound capacity or to exceed the measured \n"
@@ -21085,7 +15782,7 @@ msgid ""
 "other messages."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:58
+#: i2p2www/pages/site/docs/transport/ssu.html:59
 msgid ""
 "The congestion detection techniques vary from TCP as well, since each \n"
 "message has its own unique and nonsequential identifier, and each message"
@@ -21101,7 +15798,7 @@ msgid ""
 "retransmitted with any new updates."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:70
+#: i2p2www/pages/site/docs/transport/ssu.html:71
 msgid ""
 "The current implementation does not pad the packets to\n"
 "any particular size, but instead just places a single message fragment "
@@ -21109,7 +15806,7 @@ msgid ""
 "a packet and sends it off (careful not to exceed the MTU)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:77
+#: i2p2www/pages/site/docs/transport/ssu.html:78
 msgid ""
 "As of router version 0.8.12,\n"
 "two MTU values are used for IPv4: 620 and 1484.\n"
@@ -21117,21 +15814,21 @@ msgid ""
 "retransmitted."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:83
+#: i2p2www/pages/site/docs/transport/ssu.html:84
 msgid ""
-"For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
+"For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
 "the payload portion after the 28-byte IP/UDP header is a multiple of\n"
 "16 bytes, for encryption purposes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:89
+#: i2p2www/pages/site/docs/transport/ssu.html:90
 msgid ""
 "For the small MTU value, it is desirable to pack a 2646-byte\n"
 "Variable Tunnel Build Message efficiently into multiple packets;\n"
 "with a 620-byte MTU, it fits into 5 packets with nicely."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:95
+#: i2p2www/pages/site/docs/transport/ssu.html:96
 msgid ""
 "Based on measurements, 1492 fits nearly all reasonably small I2NP "
 "messages\n"
@@ -21140,13 +15837,13 @@ msgid ""
 "into a live network MTU anyway)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:101
+#: i2p2www/pages/site/docs/transport/ssu.html:102
 msgid ""
 "The MTU values were 608 and 1492 for releases 0.8.9 - 0.8.11.\n"
 "The large MTU was 1350 prior to release 0.8.9."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:106
+#: i2p2www/pages/site/docs/transport/ssu.html:107
 msgid ""
 "The maximum receive packet size\n"
 "is 1571 bytes as of release 0.8.12.\n"
@@ -21154,7 +15851,7 @@ msgid ""
 "Prior to release 0.8.9 it was 2048 bytes."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:113
+#: i2p2www/pages/site/docs/transport/ssu.html:114
 msgid ""
 "As of release 0.9.2, if a router's network interface MTU is less than "
 "1484,\n"
@@ -21162,17 +15859,18 @@ msgid ""
 "honor that when a connection is established."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:119
+#: i2p2www/pages/site/docs/transport/ssu.html:120
 msgid ""
 "For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes,\n"
-"so we use an MTU where (MTN % 16 == 0), which is true for 1280."
+"so we use an MTU where (MTN % 16 == 0), which is true for 1280.\n"
+"The maximum IPv6 MTU is 1472."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:124
+#: i2p2www/pages/site/docs/transport/ssu.html:126
 msgid "Message Size Limits"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:125
+#: i2p2www/pages/site/docs/transport/ssu.html:127
 msgid ""
 "While the maximum message size is nominally 32KB, the practical\n"
 "limit differs. The protocol limits the number of fragments to 7 bits, or "
@@ -21187,11 +15885,11 @@ msgid ""
 "For connections using the larger MTU, larger messages are possible."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:136
+#: i2p2www/pages/site/docs/transport/ssu.html:138
 msgid "Keys"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:138
+#: i2p2www/pages/site/docs/transport/ssu.html:140
 msgid ""
 "All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n"
 "The MAC and session keys are negotiated as part of the DH exchange, used\n"
@@ -21199,7 +15897,7 @@ msgid ""
 "the publicly knowable introKey is used for the MAC and encryption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:145
+#: i2p2www/pages/site/docs/transport/ssu.html:147
 msgid ""
 "When using the introKey, both the initial message and any subsequent\n"
 "reply use the introKey of the responder (Bob) - the responder does \n"
@@ -21209,7 +15907,7 @@ msgid ""
 "Bob."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:154
+#: i2p2www/pages/site/docs/transport/ssu.html:156
 msgid ""
 "Upon receiving a message, the receiver checks the \"from\" IP address and"
 " port\n"
@@ -21222,7 +15920,7 @@ msgid ""
 "it may be dropped anyway."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:165
+#: i2p2www/pages/site/docs/transport/ssu.html:167
 msgid ""
 "If Alice and Bob have an established session, but Alice loses the \n"
 "keys for some reason and she wants to contact Bob, she may at any \n"
@@ -21234,7 +15932,7 @@ msgid ""
 "new one."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:176
+#: i2p2www/pages/site/docs/transport/ssu.html:178
 #, python-format
 msgid ""
 "For the DH key agreement,\n"
@@ -21242,18 +15940,18 @@ msgid ""
 "MODP group (#14) is used:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:186
+#: i2p2www/pages/site/docs/transport/ssu.html:188
 #, python-format
 msgid ""
 "These are the same p and g used for I2P's\n"
 "ElGamal encryption."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:191
+#: i2p2www/pages/site/docs/transport/ssu.html:193
 msgid "Replay prevention"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:193
+#: i2p2www/pages/site/docs/transport/ssu.html:195
 msgid ""
 "Replay prevention at the SSU layer occurs by rejecting packets \n"
 "with exceedingly old timestamps or those which reuse an IV.  To\n"
@@ -21261,7 +15959,7 @@ msgid ""
 "\"decay\" periodically so that only recently added IVs are detected."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:200
+#: i2p2www/pages/site/docs/transport/ssu.html:202
 msgid ""
 "The messageIds used in DataMessages are defined at layers above\n"
 "the SSU transport and are passed through transparently.  These IDs\n"
@@ -21270,11 +15968,11 @@ msgid ""
 "replay prevention - higher layers should take that into account."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:208
+#: i2p2www/pages/site/docs/transport/ssu.html:210
 msgid "Addressing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:210
+#: i2p2www/pages/site/docs/transport/ssu.html:212
 msgid ""
 "To contact an SSU peer, one of two sets of information is necessary:\n"
 "a direct address, for when the peer is publicly reachable, or an\n"
@@ -21282,40 +15980,42 @@ msgid ""
 "There is no restriction on the number of addresses a peer may have."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:222
+#: i2p2www/pages/site/docs/transport/ssu.html:224
 msgid ""
 "Each of the addresses may also expose a series of options - special\n"
 "capabilities of that particular peer.  For a list of available\n"
 "capabilities, see below."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:228
+#: i2p2www/pages/site/docs/transport/ssu.html:230
 #, python-format
 msgid ""
 "The addresses, options, and capabilities are published in the network database."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:233
+#: i2p2www/pages/site/docs/transport/ssu.html:235
 msgid "Direct Session Establishment"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:234
+#: i2p2www/pages/site/docs/transport/ssu.html:236
 msgid ""
 "Direct session establishment is used when no third party is required for "
 "NAT traversal.\n"
 "The message sequence is as follows:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:239
+#: i2p2www/pages/site/docs/transport/ssu.html:241
 msgid "Connection establishment (direct)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:240
-msgid "Alice connects directly to Bob."
+#: i2p2www/pages/site/docs/transport/ssu.html:242
+msgid ""
+"Alice connects directly to Bob.\n"
+"IPv6 is supported as of version 0.9.8."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:254
+#: i2p2www/pages/site/docs/transport/ssu.html:257
 #, python-format
 msgid ""
 "After the SessionConfirmed message is received, Bob sends a small\n"
@@ -21328,7 +16028,7 @@ msgid ""
 "(i.e. 0x0000000000000002)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:263
+#: i2p2www/pages/site/docs/transport/ssu.html:266
 #, python-format
 msgid ""
 "After the status message is sent, the peers exchange\n"
@@ -21337,7 +16037,7 @@ msgid ""
 "RouterInfos."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:271
+#: i2p2www/pages/site/docs/transport/ssu.html:274
 msgid ""
 "It does not appear that the type of the status message or its contents "
 "matters.\n"
@@ -21346,7 +16046,7 @@ msgid ""
 "the status message can be eliminated."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:280
+#: i2p2www/pages/site/docs/transport/ssu.html:283
 msgid ""
 "Introduction keys are delivered through an external channel \n"
 "(the network database, where they are identical to the router Hash for "
@@ -21362,7 +16062,7 @@ msgid ""
 "not necessary to any intermediary relay peer)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:294
+#: i2p2www/pages/site/docs/transport/ssu.html:297
 msgid ""
 "Indirect session establishment by means of a third party introduction\n"
 "is necessary for efficient NAT traversal.  Charlie, a router behind a\n"
@@ -21390,25 +16090,25 @@ msgid ""
 "full direction session establishment with the specified IP and port."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:321
+#: i2p2www/pages/site/docs/transport/ssu.html:324
 msgid "Connection establishment (indirect using an introducer)"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:323
+#: i2p2www/pages/site/docs/transport/ssu.html:326
 msgid "Alice first connects to introducer Bob, who relays the request to Charlie."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:341
+#: i2p2www/pages/site/docs/transport/ssu.html:344
 msgid ""
 "After the hole punch, the session is established between Alice and "
 "Charlie as in a direct establishment."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:352
+#: i2p2www/pages/site/docs/transport/ssu.html:356
 msgid "Peer testing"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:354
+#: i2p2www/pages/site/docs/transport/ssu.html:358
 msgid ""
 "The automation of collaborative reachability testing for peers is\n"
 "enabled by a sequence of PeerTest messages.  With its proper \n"
@@ -21417,7 +16117,7 @@ msgid ""
 "quite simple:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:373
+#: i2p2www/pages/site/docs/transport/ssu.html:377
 msgid ""
 "Each of the PeerTest messages carry a nonce identifying the\n"
 "test series itself, as initialized by Alice.  If Alice doesn't \n"
@@ -21427,7 +16127,7 @@ msgid ""
 "that may be reached are as follows:"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:383
+#: i2p2www/pages/site/docs/transport/ssu.html:387
 msgid ""
 "If she doesn't receive a response from Bob, she will retransmit\n"
 "up to a certain number of times, but if no response ever arrives,\n"
@@ -21437,7 +16137,7 @@ msgid ""
 "Charlie to reply."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:392
+#: i2p2www/pages/site/docs/transport/ssu.html:396
 msgid ""
 "If Alice doesn't receive a PeerTest message with the \n"
 "expected nonce from a third party (Charlie), she will retransmit\n"
@@ -21449,7 +16149,7 @@ msgid ""
 "IP and port that Bob offered up should be forwarded)."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:403
+#: i2p2www/pages/site/docs/transport/ssu.html:407
 msgid ""
 "If Alice receives Bob's PeerTest message and both of Charlie's\n"
 "PeerTest messages but the enclosed IP and port numbers in Bob's \n"
@@ -21460,7 +16160,7 @@ msgid ""
 "remote connectivity, ignoring further port discovery."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:413
+#: i2p2www/pages/site/docs/transport/ssu.html:417
 msgid ""
 "If Alice receives Charlie's first message but not his second,\n"
 "she will retransmit her PeerTest message to Charlie up to a \n"
@@ -21468,7 +16168,7 @@ msgid ""
 "that Charlie is either confused or no longer online."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:421
+#: i2p2www/pages/site/docs/transport/ssu.html:425
 msgid ""
 "Alice should choose Bob arbitrarily from known peers who seem\n"
 "to be capable of participating in peer tests.  Bob in turn should\n"
@@ -21479,7 +16179,7 @@ msgid ""
 "to designate a new peer as Bob and try again with a different nonce."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:431
+#: i2p2www/pages/site/docs/transport/ssu.html:435
 msgid ""
 "Alice's introduction key is included in all of the PeerTest \n"
 "messages so that she doesn't need to already have an established\n"
@@ -21488,11 +16188,11 @@ msgid ""
 "with either Bob or Charlie, but it is not required."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:449
+#: i2p2www/pages/site/docs/transport/ssu.html:453
 msgid "Transmission window, ACKs and Retransmissions"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:450
+#: i2p2www/pages/site/docs/transport/ssu.html:454
 #, python-format
 msgid ""
 "The DATA message may contain ACKs of full messages and\n"
@@ -21502,7 +16202,7 @@ msgid ""
 "for details."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:458
+#: i2p2www/pages/site/docs/transport/ssu.html:462
 #, python-format
 msgid ""
 "The details of windowing, ACK, and retransmission strategies are not "
@@ -21517,11 +16217,11 @@ msgid ""
 "See the code for initial, min and max parameters."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:470
+#: i2p2www/pages/site/docs/transport/ssu.html:474
 msgid "Security"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:471
+#: i2p2www/pages/site/docs/transport/ssu.html:475
 msgid ""
 "UDP source addresses may, of course, be spoofed.\n"
 "Additionally, the IPs and ports contained inside specific\n"
@@ -21530,31 +16230,31 @@ msgid ""
 "Also, certain actions and responses may need to be rate-limited."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:479
+#: i2p2www/pages/site/docs/transport/ssu.html:483
 msgid ""
 "The details of validation are not specified\n"
 "here. Implementers should add defenses where appropriate."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:485
+#: i2p2www/pages/site/docs/transport/ssu.html:489
 msgid "Peer capabilities"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:489
+#: i2p2www/pages/site/docs/transport/ssu.html:493
 msgid ""
 "If the peer address contains the 'B' capability, that means \n"
 "they are willing and able to participate in peer tests as\n"
 "a 'Bob' or 'Charlie'."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:495
+#: i2p2www/pages/site/docs/transport/ssu.html:499
 msgid ""
 "If the peer address contains the 'C' capability, that means\n"
 "they are willing and able to serve as an introducer - serving\n"
 "as a Bob for an otherwise unreachable Alice."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:504
+#: i2p2www/pages/site/docs/transport/ssu.html:508
 msgid ""
 "Analysis of current SSU performance, including assessment of window size "
 "adjustment\n"
@@ -21563,14 +16263,14 @@ msgid ""
 "performance, is a topic for future work."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:510
+#: i2p2www/pages/site/docs/transport/ssu.html:514
 msgid ""
 "The current implementation repeatedly sends acknowledgments for the same "
 "packets,\n"
 "which unnecessarily increases overhead."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:515
+#: i2p2www/pages/site/docs/transport/ssu.html:519
 msgid ""
 "The default small MTU value of 620 should be analyzed and possibly "
 "increased.\n"
@@ -21579,15 +16279,15 @@ msgid ""
 "Probably not."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:521
+#: i2p2www/pages/site/docs/transport/ssu.html:525
 msgid "The protocol should be extended to exchange MTUs during the setup."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:525
+#: i2p2www/pages/site/docs/transport/ssu.html:529
 msgid "Rekeying is currently unimplemented and may never be."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:529
+#: i2p2www/pages/site/docs/transport/ssu.html:533
 msgid ""
 "The potential use of the 'challenge' fields in RelayIntro and "
 "RelayResponse,\n"
@@ -21595,7 +16295,7 @@ msgid ""
 "undocumented."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:534
+#: i2p2www/pages/site/docs/transport/ssu.html:538
 msgid ""
 "Instead of a single fragment per packet, a more efficient\n"
 "strategy may be to bundle multiple message fragments into the same "
@@ -21603,7 +16303,7 @@ msgid ""
 "so long as it doesn't exceed the MTU."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:540
+#: i2p2www/pages/site/docs/transport/ssu.html:544
 msgid ""
 "A set of fixed packet sizes may be appropriate to further hide the data \n"
 "fragmentation to external adversaries, but the tunnel, garlic, and end to"
@@ -21611,34 +16311,34 @@ msgid ""
 "end padding should be sufficient for most needs until then."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:546
+#: i2p2www/pages/site/docs/transport/ssu.html:550
 msgid ""
 "Why are introduction keys the same as the router hash, should it be "
 "changed, would there be any benefit?"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:550
+#: i2p2www/pages/site/docs/transport/ssu.html:554
 msgid "Capacities appear to be unused."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:554
+#: i2p2www/pages/site/docs/transport/ssu.html:558
 msgid ""
 "Signed-on times in SessionCreated and SessionConfirmed appear to be "
 "unused or unverified."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:559
+#: i2p2www/pages/site/docs/transport/ssu.html:563
 msgid "Implementation Diagram"
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:560
+#: i2p2www/pages/site/docs/transport/ssu.html:564
 msgid ""
 "This diagram\n"
 "should accurately reflect the current implementation, however there may "
 "be small differences."
 msgstr ""
 
-#: i2p2www/pages/site/docs/transport/ssu.html:568
+#: i2p2www/pages/site/docs/transport/ssu.html:572
 msgid "Now on the SSU specification page"
 msgstr ""
 
@@ -22434,6 +17134,10 @@ msgstr ""
 msgid "Tunnel design discussion"
 msgstr ""
 
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:21
+msgid "Peer selection"
+msgstr ""
+
 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:23
 msgid "Meeting 125 (~13:12-13:30)"
 msgstr ""
@@ -22609,5202 +17313,3 @@ msgid ""
 "conclusion is not supported by the paper."
 msgstr ""
 
-#: i2p2www/pages/site/get-involved/donate.html:4
-msgid ""
-"Thank you for your interest in contributing to I2P!\n"
-"The details of how you\n"
-"can make your contribution are provided below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:13
-#, python-format
-msgid "You can donate direct via PayPal to the account \"%(account)s\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:19
-msgid "One time donation:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:33
-msgid "Donate 10 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:41
-#: i2p2www/pages/site/get-involved/donate.html:53
-#: i2p2www/pages/site/get-involved/donate.html:65
-#: i2p2www/pages/site/get-involved/donate.html:77
-msgid "I2P donation "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:47
-msgid "Donate 20 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:59
-msgid "Donate 30 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:71
-msgid "Donate 50 €/month for 12 months:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:86
-msgid "Flattr this"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:90
-#, python-format
-msgid ""
-"As of December 2010, eche|on has been running a Bitcoin account for the I2P project. \n"
-"If you'd like to donate using Bitcoin, just transfer your desired amount "
-"of coins to the account \n"
-"%(account)s and leave eche|on a note if you'd like your donation "
-"to be mentioned on the I2P webpage."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:95
-msgid ""
-"If you want to keep more or less anonymous, the option to send money via "
-"mail is also available. But it is less secure\n"
-"as the envelope can be lost on the way to us."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:99
-#, python-format
-msgid ""
-"If you'd like to donate via  snail mail, send an email to %(email)s\n"
-" and you'll receive an email with instructions detailing how to proceed."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/donate.html:104
-#, python-format
-msgid ""
-"In the meantime, feel free to take a look at the generous donations that "
-"have been\n"
-"given in support of the I2P Project at the hall of fame."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:2
-msgid "Get Involved!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:4
-msgid "We need your help!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:5
-msgid ""
-"To get involved, please feel free to join us on the #i2p IRC channel (on\n"
-"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or "
-"irc.postman.i2p)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:9
-#, python-format
-msgid ""
-"If you're interested in joining our team, please"
-" get in\n"
-"touch as we're always looking for eager contributors!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:13
-msgid ""
-"We need help in many areas, and you don't need to know Java to "
-"contribute!\n"
-"Here's a list to help you get started!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:18
-msgid "Spread the Word!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:19
-msgid ""
-"Tell people about I2P on forums, blogs, and comments to articles.\n"
-"Fix up the Wikipedia article about I2P in your language.\n"
-"Tell your friends."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:24
-msgid "Testing"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:25
-#, python-format
-msgid ""
-"Run the latest builds from monotone\n"
-"and report results on #i2p or as bugs on Trac."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:30
-msgid ""
-"Help fix the parts of the website that are outdated or incomplete.\n"
-"Translate pages into other languages."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:34
-msgid "Pictures"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:35
-msgid "Make some more pictures, fix the old ones on the website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:39
-msgid "Make an eepsite! Add some content! Contribute to the community!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:42
-msgid "Services"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:43
-msgid ""
-"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n"
-"a naming service, a search engine, an eepsite monitor... many of these\n"
-"aren't that hard."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:49
-#, python-format
-msgid ""
-"Write or port applications for I2P! There's some guidelines and\n"
-"a list of ideas on the applications page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:53
-msgid "Coding"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:54
-#, python-format
-msgid ""
-"There's plenty to do if you know Java or are ready to learn.\n"
-"Check for open tickets on Trac\n"
-"or the TODO list on %(zzz)s for\n"
-"some ideas on where to start.\n"
-"See the new developer's guide for details."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:61
-msgid "Translation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:62
-#, python-format
-msgid ""
-"Help translate the website and the software into your language.\n"
-"See the new translator's guide for details."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:66
-msgid "Analysis"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/index.html:67
-#, python-format
-msgid ""
-"Study or test the code to look for vulnerabilities.\n"
-"Both anonymity vulnerabilities from the various\n"
-"threat models,\n"
-"and DOS and other weaknesses due to securities holes,\n"
-"need researching."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:7
-msgid ""
-"Include some seed data in the distribution so a central reseed location "
-"isn't required?"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:10
-#, python-format
-msgid ""
-"Reachability Mapping / handle peers partially reachable / enhanced restricted routes"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:13
-msgid "Improve help pages and website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:14
-msgid "More translations"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:15
-msgid "SSU disconnect message"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:16
-msgid "Iterative floodfill lookups"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:21
-msgid "Full review of anonymity issues and other vulnerabilities"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:22
-msgid ""
-"Reduce memory usage, remove debugging overhead, make it run better on "
-"slow and embedded machines"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:25
-msgid "Docs"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:30
-msgid "Full restricted routes"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:35
-msgid "Tunnel mixing and padding"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:36
-msgid "User defined message delays"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/roadmap.html:39
-#, python-format
-msgid ""
-"Please see the TODO list for more detailed info "
-"about some of these tasks."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:4
-msgid "I2P Project Targets"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:5
-#, python-format
-msgid ""
-"Below is a more detailed (yet still incomplete) discussion of the major "
-"areas\n"
-"of future development on the core I2P network, spanning the plausibly "
-"planned\n"
-"releases. This does not include stego transports, porting to wireless "
-"devices,\n"
-"or tools to secure the local machine, nor does it include client "
-"applications\n"
-"that will be essential in I2P's success. There are probably other things "
-"that\n"
-"will come up, especially as I2P gets more peer review, but these are the "
-"main\n"
-"'big things'. See also the roadmap. Want to "
-"help?\n"
-"Get involved!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:16
-#: i2p2www/pages/site/get-involved/todo.html:54
-msgid "Core functionality"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:18
-#: i2p2www/pages/site/get-involved/todo.html:57
-msgid "NAT/Firewall bridging via 1-hop restricted routes"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:21
-#: i2p2www/pages/site/get-involved/todo.html:130
-msgid "High degree transport layer with UDP, NBIO, or NIO"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:24
-#: i2p2www/pages/site/get-involved/todo.html:218
-msgid "NetworkDB and profile tuning and ejection policy for large nets"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:28
-#: i2p2www/pages/site/get-involved/todo.html:242
-msgid "Security / anonymity"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:30
-#: i2p2www/pages/site/get-involved/todo.html:245
-msgid ""
-"Per-hop tunnel id & new permuted TunnelVerificationStructure "
-"encryption"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:33
-#: i2p2www/pages/site/get-involved/todo.html:295
-msgid "Strict ordering of participants within tunnels"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:36
-msgid "Randomly permuted tunnel lengths"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:39
-#: i2p2www/pages/site/get-involved/todo.html:357
-msgid "Full blown n-hop restricted routes with optional trusted links"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:42
-#: i2p2www/pages/site/get-involved/todo.html:376
-msgid "Hashcash for routerIdentity, destination, and tunnel request"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:45
-#: i2p2www/pages/site/get-involved/todo.html:405
-msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:48
-#: i2p2www/pages/site/get-involved/todo.html:442
-msgid "Stop & go mix w/ garlics & tunnels"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:62
-msgid "Implemented in I2P 0.6.0.6"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:63
-msgid ""
-"The functionality of allowing routers to fully participate within the "
-"network \n"
-"while behind firewalls and NATs that they do not control requires some "
-"basic \n"
-"restricted route operation (since those peers will not be able to receive"
-" \n"
-"inbound connections). To do this successfully, you consider peers one of"
-" \n"
-"two ways:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:73
-msgid ""
-"Peers who have reachable interfaces - these peers do not need to \n"
-"do anything special"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:77
-msgid ""
-"Peers who do not have reachable interfaces - these peers must "
-"build \n"
-"a tunnel pointing at them where the gateway is one of the peers they have"
-" \n"
-"established a connection with who has both a publicly reachable interface"
-" \n"
-"and who has agreed to serve as their 'introducer'."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:85
-msgid ""
-"To do this, peers who have no IP address simply connect to a few peers, \n"
-"build a tunnel through them, and publish a reference to those tunnels "
-"within \n"
-"their RouterInfo structure in the network database."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:90
-msgid ""
-"When someone wants to contact any particular router, they first must get"
-" \n"
-"its RouterInfo from the network database, which will tell them whether "
-"they \n"
-"can connect directly (e.g. the peer has a publicly reachable interface) \n"
-"or whether they need to contact them indirectly. Direct connections occur"
-" \n"
-"as normal, while indirect connections are done through one of the "
-"published \n"
-"tunnels."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:98
-msgid ""
-"When a router just wants to get a message or two to a specific hidden "
-"peer, \n"
-"they can just use the indirect tunnel for sending the payload. However, \n"
-"if the router wants to talk to the hidden peer often (for instance, as "
-"part \n"
-"of a tunnel), they will send a garlic routed message through the indirect"
-" \n"
-"tunnel to that hidden peer which unwraps to contain a message which "
-"should \n"
-"be sent to the originating router. That hidden peer then establishes an \n"
-"outbound connection to the originating router and from then on, those two"
-" \n"
-"routers can talk to each other directly over that newly established "
-"direct \n"
-"connection."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:109
-msgid ""
-"Of course, that only works if the originating peer can receive "
-"connections \n"
-"(they aren't also hidden). However, if the originating peer is hidden, "
-"they \n"
-"can simply direct the garlic routed message to come back to the "
-"originating \n"
-"peer's inbound tunnel."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:115
-msgid ""
-"This is not meant to provide a way for a peer's IP address to be "
-"concealed, \n"
-"merely as a way to let people behind firewalls and NATs fully operate "
-"within \n"
-"the network. Concealing the peer's IP address adds a little more work, as"
-" \n"
-"described below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:121
-msgid ""
-"With this technique, any router can participate as any part of a tunnel."
-" \n"
-"For efficiency purposes, a hidden peer would be a bad choice for an "
-"inbound \n"
-"gateway, and within any given tunnel, two neighboring peers wouldn't want"
-" \n"
-"to be hidden. But that is not technically necessary."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:133
-msgid "Both UDP and NIO have been Implemented in I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:134
-msgid ""
-"Standard TCP communication in Java generally requires blocking socket \n"
-"calls, and to keep a blocked socket from hanging the entire system, those"
-" \n"
-"blocking calls are done on their own threads. Our current TCP transport \n"
-"is implemented in a naive fashion - for each peer we are talking to, we \n"
-"have one thread reading and one thread writing. The reader thread simply"
-" \n"
-"loops a bunch of read() calls, building I2NP messages and adding them \n"
-"to our internal inbound message queue, and the writer thread pulls "
-"messages \n"
-"off a per-connection outbound message queue and shoves the data through \n"
-"write() calls."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:145
-msgid ""
-"We do this fairly efficiently, from a CPU perspective - at any time, \n"
-"almost all of these threads are sitting idle, blocked waiting for "
-"something \n"
-"to do. However, each thread consumes real resources (on older Linux "
-"kernels, \n"
-"for instance, each thread would often be implemented as a fork()'ed "
-"process). \n"
-"As the network grows, the number of peers each router will want to talk \n"
-"with will increase (remember, I2P is fully connected, meaning that any \n"
-"given peer should know how to get a message to any other peer, and "
-"restricted \n"
-"route support will probably not significantly reduce the number of "
-"connections \n"
-"necessary). This means that with a 100,000 router network, each router \n"
-"will have up to 199,998 threads just to deal with the TCP connections!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:157
-msgid ""
-"Obviously, that just won't work. We need to use a transport layer that \n"
-"can scale. In Java, we have two main camps:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:162
-#, python-format
-msgid ""
-"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:165
-msgid ""
-"Sending and receiving UDP datagrams is a connectionless operation - if \n"
-"we are communicating with 100,000 peers, we simply stick the UDP packets"
-" \n"
-"in a queue and have a single thread pulling them off the queue and "
-"shoving \n"
-"them out the pipe (and to receive, have a single thread pulling in any \n"
-"UDP packets received and adding them to an inbound queue)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:172
-msgid ""
-"However, moving to UDP means losing the benefits of TCP's ordering, "
-"congestion \n"
-"control, MTU discovery, etc. Implementing that code will take significant"
-" \n"
-"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n"
-"a while ago I was taking some measurements in the simulator and on the \n"
-"live net, and the vast majority of messages transferred would fit easily"
-" \n"
-"within a single unfragmented UDP packet, and the largest of the messages"
-" \n"
-"would fit within 20-30 packets. As mule pointed out, TCP adds a "
-"significant \n"
-"overhead when dealing with so many small packets, as the ACKs are within"
-" \n"
-"an order of magnitude in size. With UDP, we can optimize the transport \n"
-"for both efficiency and resilience by taking into account I2P's "
-"particular \n"
-"needs."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:185
-msgid "It will be a lot of work though."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:188
-msgid "NIO or NBIO"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:189
-msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:192
-msgid ""
-"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java"
-" \n"
-"developers to take advantage of the operating system's nonblocking IO \n"
-"capabilities - allowing you to maintain a large number of concurrent IO \n"
-"operations without requiring a separate thread for each. There is much \n"
-"promise with this approach, as we can scalable handle a large number of \n"
-"concurrent connections and we don't have to write a mini-TCP stack with \n"
-"UDP. However, the NIO packages have not proven themselves to be battle-"
-"ready, \n"
-"as the Freenet developer's found. In addition, requiring NIO support "
-"would \n"
-"mean we can't run on any of the open source JVMs like Kaffe, \n"
-"as GNU/Classpath has only "
-"limited \n"
-"support for NIO. (note: this may not be the case anymore, as there \n"
-"has been some progress on Classpath's NIO, but it is an unknown "
-"quantity)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:206
-#, python-format
-msgid ""
-"Another alternative along the same lines is the Non"
-" \n"
-"Blocking I/O package - essentially a cleanroom NIO implementation \n"
-"(written before NIO was around). It works by using some native OS code \n"
-"to do the nonblocking IO, passing off events through Java. It seems to \n"
-"be working with Kaffe, though there doesn't seem to be much development \n"
-"activity on it lately (likely due to 1.4's NIO deployment)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:221
-msgid ""
-"Within the current network database and profile management "
-"implementation, \n"
-"we have taken the liberty of some practical shortcuts. For instance, we \n"
-"don't have the code to drop peer references from the K-buckets, as we \n"
-"don't have enough peers to even plausibly fill any of them, so instead, \n"
-"we just keep the peers in whatever bucket is appropriate. Another example"
-" \n"
-"deals with the peer profiles - the memory required to maintain each "
-"peer's \n"
-"profile is small enough that we can keep thousands of full blown profiles"
-" \n"
-"in memory without problems. While we have the capacity to use trimmed \n"
-"down profiles (which we can maintain 100s of thousands in memory), we \n"
-"don't have any code to deal with moving a profile from a \"minimal "
-"profile\" \n"
-"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to"
-" simply \n"
-"eject a profile altogether. It just wouldn't be practical to write that \n"
-"code yet, since we aren't going to need it for a while."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:236
-msgid ""
-"That said, as the network grows we are going to want to keep these "
-"considerations \n"
-"in mind. We will have some work to do, but we can put it off for later."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:248
-#: i2p2www/pages/site/get-involved/todo.html:332
-#, python-format
-msgid ""
-"Addressed in I2P 0.5 as documented elsewhere"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:251
-msgid ""
-"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n"
-"going to Dave, then to Charlie, then Bob, and finally Alice "
-"(A<--B<--C<--D<--E), \n"
-"all five of them will know they are participating in tunnel \"123\", as \n"
-"the messages are tagged as such. What we want to do is give each hop "
-"their \n"
-"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n"
-"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n"
-"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n"
-"the tunnel had the same tunnel ID, collusion attacks aren't much work."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:261
-msgid ""
-"Adding a unique tunnel ID per hop isn't hard, but by itself, "
-"insufficient. \n"
-"If Dave and Bob are under the control of the same attacker, they wouldn't"
-" \n"
-"be able to tell they are in the same tunnel due to the tunnel ID, but \n"
-"would be able to tell by the message bodies and verification structures \n"
-"by simply comparing them. To prevent that, the tunnel must use layered \n"
-"encryption along the path, both on the payload of the tunneled message \n"
-"and on the verification structure (used to prevent simple tagging "
-"attacks). \n"
-"This requires some simple modifications to the TunnelMessage, as well \n"
-"as the inclusion of per-hop secret keys delivered during tunnel creation"
-" \n"
-"and given to the tunnel's gateway. We must fix a maximum tunnel length \n"
-"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n"
-"of the 16 delivered secret keys, in reverse order, and to encrypt the \n"
-"signature of the hash of the (encrypted) payload at each step. The "
-"gateway \n"
-"then sends that 16-step encrypted message, along with a 16-step and "
-"16-wide \n"
-"encrypted mapping to the first hop, which then decrypts the mapping and \n"
-"the payload with their secret key, looking in the 16-wide mapping for \n"
-"the entry associated with their own hop (keyed by the per-hop tunnel ID)"
-" \n"
-"and verifying the payload by checking it against the associated signed \n"
-"hash."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:282
-msgid ""
-"The tunnel gateway does still have more information than the other peers"
-" \n"
-"in the tunnel, and compromising both the gateway and a tunnel participant"
-" \n"
-"would allow those peers to collude, exposing the fact that they are both"
-" \n"
-"in the same tunnel. In addition, neighboring peers know that they are \n"
-"in the same tunnel anyway, as they know who they send the message to (and"
-" \n"
-"with IP-based transports without restricted routes, they know who they \n"
-"got it from). However, the above two techniques significantly increase \n"
-"the cost of gaining meaningful samples when dealing with longer tunnels."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:298
-msgid "Implemented in release 0.6.2"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:301
-#, python-format
-msgid ""
-"As Connelly proposed to deal with the\n"
-"predecessor attack (2008\n"
-"update), keeping the order of peers within our tunnels consistent \n"
-"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n"
-"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n"
-"get to substantially sample Alice's peer selection group. We may even \n"
-"want to explicitly allow Bob to participate in Alice's tunnels in only \n"
-"one way - receiving a message from Dave and sending it to Charlie - and \n"
-"if any of those peers are not available to participate in the tunnel (due"
-" \n"
-"to overload, network disconnection, etc), avoid asking Bob to participate"
-" \n"
-"in any tunnels until they are back online."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:316
-msgid ""
-"More analysis is necessary for revising the tunnel creation - at the \n"
-"moment, we simply select and order randomly within the peer's top tier \n"
-"of peers (ones with fast + high capacity)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:321
-msgid ""
-"Adding a strict ordering to peers in a tunnel also improves the anonymity"
-" \n"
-"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway"
-" \n"
-"is always the same would be particularly damning. However, peers with \n"
-"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n"
-"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n"
-"duration) minutes, use a 1-hop tunnel)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:338
-msgid ""
-"Without tunnel length permutation, if someone were to somehow detect that"
-" \n"
-"a destination had a particular number of hops, it might be able to use "
-"that \n"
-"information to identify the router the destination is located on, per the"
-" \n"
-"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n"
-"receives a tunnel message from Charlie and forwards it to Alice, Bob "
-"knows \n"
-"Alice is the final router in the tunnel. If Bob were to identify what "
-"destination \n"
-"that tunnel served (by means of colluding with the gateway and harvesting"
-" \n"
-"the network database for all of the LeaseSets), he would know the router"
-" \n"
-"on which that destination is located (and without restricted routes, that"
-" \n"
-"would mean what IP address the destination is on)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:350
-msgid ""
-"It is to counter user behavior that tunnel lengths should be permuted, \n"
-"using algorithms based on the length requested (for example, the 1/MTBF \n"
-"length change for 0-hop tunnels outlined above)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:360
-msgid ""
-"The restricted route functionality described before was simply a "
-"functional \n"
-"issue - how to let peers who would not otherwise be able to communicate \n"
-"do so. However, the concept of allowing restricted routes includes "
-"additional \n"
-"capabilities. For instance, if a router absolutely cannot risk "
-"communicating \n"
-"directly with any untrusted peers, they can set up trusted links through"
-" \n"
-"those peers, using them to both send and receive all of its messages. \n"
-"Those hidden peers who want to be completely isolated would also refuse \n"
-"to connect to peers who attempt to get them to (as demonstrated by the \n"
-"garlic routing technique outlined before) - they can simply take the "
-"garlic \n"
-"clove that has a request for delivery to a particular peer and tunnel \n"
-"route that message out one of the hidden peer's trusted links with "
-"instructions \n"
-"to forward it as requested."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:379
-#, python-format
-msgid ""
-"Within the network, we will want some way to deter people from consuming"
-" \n"
-"too many resources or from creating so many peers to mount a Sybil \n"
-"attack. Traditional techniques such as having a peer see who is "
-"requesting \n"
-"a resource or running a peer aren't appropriate for use within I2P, as \n"
-"doing so would compromise the anonymity of the system. Instead, we want \n"
-"to make certain requests \"expensive\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:387
-msgid ""
-"Hashcash is one technique that \n"
-"we can use to anonymously increase the \"cost\" of doing certain "
-"activities, \n"
-"such as creating a new router identity (done only once on installation),"
-" \n"
-"creating a new destination (done only once when creating a service), or \n"
-"requesting that a peer participate in a tunnel (done often, perhaps 2-300"
-" \n"
-"times per hour). We don't know the \"correct\" cost of each type of "
-"certificate \n"
-"yet, but with some research and experimentation, we could set a base "
-"level \n"
-"that is sufficiently expensive while not an excessive burden for people \n"
-"with few resources."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:398
-msgid ""
-"There are a few other algorithms that we can explore for making those \n"
-"requests for resources \"nonfree\", and further research on that front is"
-" \n"
-"appropriate."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:408
-#, python-format
-msgid ""
-"To powerful passive external observers as well as large colluding "
-"internal \n"
-"observers, standard tunnel routing is vulnerable to traffic analysis "
-"attacks \n"
-"- simply watching the size and frequency of messages being passed between"
-" \n"
-"routers. To defend against these, we will want to essentially turn some \n"
-"of the tunnels into its own mix cascade - delaying messages received at \n"
-"the gateway and passing them in batches, reordering them as necessary, \n"
-"and injecting dummy messages (indistinguishable from other \"real\" "
-"tunnel \n"
-"messages by peers in the path). There has been a significant amount of \n"
-"research \n"
-"on these algorithms that we can lean on prior to implementing the various"
-" \n"
-"tunnel mixing strategies."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:421
-msgid ""
-"In addition to the anonymity aspects of more varied tunnel operation, \n"
-"there is a functional dimension as well. Each peer only has a certain \n"
-"amount of data they can route for the network, and to keep any particular"
-" \n"
-"tunnel from consuming an unreasonable portion of that bandwidth, they \n"
-"will want to include some throttles on the tunnel. For instance, a tunnel"
-" \n"
-"may be configured to throttle itself after passing 600 messages (1 per \n"
-"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n"
-"last minute). Excess messages may be delayed or summarily dropped. With \n"
-"this sort of throttling, peers can provide ATM-like QoS support for their"
-" \n"
-"tunnels, refusing to agree to allocate more bandwidth than the peer has \n"
-"available."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:434
-msgid ""
-"In addition, we may want to implement code to dynamically reroute tunnels"
-" \n"
-"to avoid failed peers or to inject additional hops into the path. This \n"
-"can be done by garlic routing a message to any particular peer in a "
-"tunnel \n"
-"with instructions to redefine the next-hop in the tunnel."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:445
-msgid ""
-"Beyond the per-tunnel batching and mixing strategy, there are further \n"
-"capabilities for protecting against powerful attackers, such as allowing"
-" \n"
-"each step in a garlic routed path to define a delay or window in which \n"
-"it should be forwarded on. This would enable protections against the long"
-" \n"
-"term intersection attack, as a peer could send a message that looks "
-"perfectly \n"
-"standard to most peers that pass it along, except at any peers where the"
-" \n"
-"clove exposed includes delay instructions."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/todo.html:457
-#, python-format
-msgid ""
-"Performance related improvements are listed on the\n"
-"Performance page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2
-msgid "Bounty Arabic translation of webpage and router console"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3
-#: i2p2www/pages/site/get-involved/bounties/index.html:119
-msgid "Arabic translation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2P echelon set out this bounty for translation\n"
-"of the I2P web page and I2P router console into Arabic."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12
-msgid "This bounty is set into 2 subparts:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14
-msgid "Part 1 is translation of the webpage."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17
-msgid ""
-"For collecting the bounty of 20 BTC you need to translate the following "
-"pages:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25
-msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27
-msgid ""
-"Part 2 is the translation of the router console. The router console was\n"
-"partly translated and the bounty of 80 BTC was paid to hamada."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34
-msgid "Judge is echelon."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2
-msgid "Bounty creating a I2P native Bitcoin client"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3
-msgid "BTC I2P native client"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6
-msgid ""
-"For a future of I2P and attract more people\n"
-"into I2P this bounty is to create a I2P native Bitcoin client. \n"
-"It should integrate with other client via the I2P network and via "
-"gateways to\n"
-"the existant bitcoin network."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15
-msgid "Judge is psychonaut who donated the first 30 € to this bounty."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
-msgid "Bounty datastorage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:3
-msgid "datastore"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:6
-msgid ""
-"To improve I2P's usage and to be independent of routers \n"
-"online status we want a datastorage as a extension to I2P.\n"
-"Like in Freenet the datastorage should be distributed and every\n"
-"participating node should be able to configure his options.\n"
-"The files should be saved in chunks and at least 2-3 times to\n"
-"obtain redundancy. Usage of storage space should be auto balanced.\n"
-"As it is a extra application, it should work flawless within I2P and\n"
-"cooperate nice with the I2P router. Maybe a integration within the\n"
-"webpage/router could be done."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:17
-msgid ""
-"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n"
-"\"eepsites in datastorage\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:21
-msgid ""
-"The frost for I2P datastorage bounty is paid for a frost like program \n"
-"with which files/messages are stored into database and got from database."
-"\n"
-"It needs to work with a GUI."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:26
-msgid ""
-"The eepsite served out of I2P datastorage extends a I2P router to send\n"
-"out eepsites out of the I2P datastorage. All files for eepsites need to "
-"be\n"
-"saved inside of datastorage and are taken from it.\n"
-"Extension:\n"
-"For better integration all datastorage participants could serve that "
-"eepsite."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/datastore.html:36
-msgid ""
-"For bounties to be declared done and paid, we need the program AND the "
-"source.\n"
-"Source and code need to be licensed under a free license (free to change "
-"and \n"
-"free to distribute)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2
-msgid "Bounty I2P package in Debian and Ubuntu mirrors"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3
-msgid "I2P Ubuntu/Debian package"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6
-msgid ""
-"For the future of I2P and in order to attract more people\n"
-"to I2P, this bounty was set for including an I2P package into the Ubuntu "
-"and Debian \n"
-"archive mirrors.\n"
-"To claim this bounty, the I2P router package needs to be available from\n"
-"Ubuntu and Debian archive mirrors and Debian bug \n"
-"448638 \n"
-"needs to be closed successfully."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2
-msgid "Bounty I2PHex code implementation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3
-msgid "i2phex code implementation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2PHex P2P ArneBab setout the bounty for implementing actual\n"
-"Phex code onto I2PHex."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:5
-msgid "Bounties for I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:6
-msgid ""
-"While we always gratefully accept any contributions of code, \n"
-"documentation, and the like, there are other ways to help I2P move \n"
-"forward.  As with any open source project, our goals would be achieved "
-"more \n"
-"rapidly if we were able to support all of our contributors to work on \n"
-"I2P full time.  However, as with any open source project, that's not a \n"
-"possibility.  Instead, we are making use of a bounty system, whereby \n"
-"anyone can get support for working on something that people want \n"
-"implemented, and people who want to contribute to I2P can be assured that"
-" \n"
-"their support goes to what they care about."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:18
-msgid ""
-"We are also keeping open the ability for people who want to support I2P \n"
-"but don't have strong feelings about the bounties available.  Those "
-"people\n"
-"can simply put their trust in the I2P team to do what we feel is best by\n"
-"donating to a catch-all general fund that will be used as deemed \n"
-"necessary - allocated to various bounties, covering incidentals (hosting,"
-" \n"
-"etc), and the like."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:27
-msgid "Current bounties"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-#: i2p2www/pages/site/get-involved/bounties/index.html:112
-msgid "Name"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-#: i2p2www/pages/site/get-involved/bounties/index.html:112
-msgid "Status"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-msgid "Judge"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:30
-#: i2p2www/pages/site/get-involved/bounties/index.html:99
-msgid "Bounty"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:32
-msgid "Frost for I2P datastorage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:33
-#: i2p2www/pages/site/get-involved/bounties/index.html:40
-#: i2p2www/pages/site/get-involved/bounties/index.html:47
-#: i2p2www/pages/site/get-involved/bounties/index.html:54
-#: i2p2www/pages/site/get-involved/bounties/index.html:61
-#: i2p2www/pages/site/get-involved/bounties/index.html:82
-#: i2p2www/pages/site/get-involved/bounties/index.html:89
-msgid "Proposal in development"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:39
-msgid "Eepsites served out of I2P datastorage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:46
-msgid "Backporting Phex code onto I2PHex"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:53
-msgid "Make I2P IPv6 native"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:60
-msgid "I2P package in Debian and Ubuntu mirrors"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:68
-msgid "Done, phase of verification"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:74
-msgid "Unit tests and Multi-router Simulation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:75
-msgid "Partly done, partly in work, partly still open"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:96
-msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:101
-msgid "Bundling bounties"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:102
-msgid "Proposed"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:109
-msgid "Claimed bounties"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:112
-msgid "Dev team"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:114
-msgid "Setting up a SILC server"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:124
-msgid "Datastore over I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:129
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
-msgid "Russian translation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:134
-msgid "Swarming file transfer"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:139
-msgid "Streaming library window size"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:144
-msgid "IRC connect time monitor"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:149
-msgid "Unit tests (part 1)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/index.html:161
-msgid ""
-"Dev lists anyone who may already be working on the bounty - collaboration"
-" is\n"
-"preferred, so if you're interested in working on it, please contact one "
-"of the\n"
-"people listed!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2
-msgid "Bounty I2P IPv6 native"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3
-msgid "native IPv6 I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6
-msgid ""
-"For a future of I2P and attract more people\n"
-"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n"
-"To claim this bounty, the I2P router needs to run full on native\n"
-"IPv6 connections like it does on IPv4."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/ipv6.html:15
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
-msgid ""
-"For bounties to be declared done and paid, we need the plugin AND the "
-"source.\n"
-"Source and code need to be licensed under a free license (free to change "
-"and \n"
-"free to distribute)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:2
-msgid "NetDB Backend"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:3
-msgid "netDB backend"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:7
-msgid ""
-"The current NetDB implementation (namely the FloodFill system)\n"
-"needs to be extended with another backend to improve reliability,\n"
-"reduce attack surface and solve the scalability issue for the \n"
-"coming years."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/netdb.html:14
-msgid ""
-"A solution likely based on a DHT will be investigated and \n"
-"finally implemented."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2
-msgid "Bounty russian translation of webpage and router console"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2P a anonymous donator set out the bounty for translation\n"
-"of the I2P web page and I2P router console into russian language."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17
-msgid ""
-"For collecting the bounty of $115 USD you need to translate the following"
-" pages:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30
-msgid ""
-"Part 2 is the translation of the router console. The whole router console"
-" needs\n"
-"to be translated to collect the bounty of $115 USD."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37
-msgid "Judge is the russian donor."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:2
-msgid "Bounty migrate I2P IRC to SILC"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:3
-msgid "I2P silc server"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:7
-msgid ""
-"For a future of I2P and attract more people\n"
-"into I2P this bounty is to setup and host a I2P SILC server.   \n"
-"This will allow people to send files over their messaging servers and "
-"have intrinsic security built into the protocol."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:12
-msgid ""
-"A silc server needs to be set up and run for at least 3 month time to get"
-" payed. \n"
-"A second server should be set up, to."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:16
-msgid ""
-"Bounty was withdrawn and money donated to returningnovice and general "
-"fund."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/silc.html:22
-msgid "Judge is An Anonymous Secret Society, society@mail.i2p."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7
-msgid ""
-"Beside of I2P we want to encourage users\n"
-"to care more about anonymity and security. As I2P is a low \n"
-"latency network with its natural limits, the software SYNDIE\n"
-"can overcome some of these limits and provide better anonymity\n"
-"for people who really need it."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14
-msgid ""
-"For our bad sake the syndie project was out of development for \n"
-"quite a long time yet (5 years). To get a fresh and new built \n"
-"with needed bugfixes we set out this bounty. Also syndie needs\n"
-"some enhancements and a better GUI for users to work with it.\n"
-"Current bounty sum is 50 Bitcoin."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22
-msgid ""
-"The latest Syndie coding rally did improve the situation of the\n"
-"Syndie package dramatically. A new Syndie package with bugfixes\n"
-"was created and made available on different webpages.\n"
-"As a result of this work, the bounty sum was reduced and\n"
-"the withdrawn money moved to the IPv6 bounty."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2
-msgid "Bounty unittests"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3
-msgid "unit test"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7
-msgid ""
-"To improve I2P's maintainability, we want to have a solid set of\n"
-"automated unit tests for the critical code.  While we do have some\n"
-"unit tests at the moment, they are ad-hoc and partly unfinished.  \n"
-"This bounty is for someone to check the existing tests and move over\n"
-"old ones to jUnit, automate their execution, extend them to provide \n"
-"better code coverage, and publish the report online.  Its a massive \n"
-"effort, but can be broken down into phases, listed below (phase 2 \n"
-"must occur first, but further phases may happen in any order).\n"
-"As this needs some reading of code, it is the best start point for\n"
-"new devs to get a good overview of I2P code and coding. A good job\n"
-"for college students, interns or anyone who is just interested."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20
-msgid ""
-"Take care! Jobs and bounties shuffled a bit!\n"
-"Phase 6,7 and 8 are still open!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112
-#, python-format
-msgid "Phase %(phase)s:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27
-msgid "CI jenkins and IRC bot"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114
-#, python-format
-msgid "Bounty: %(euro)s €"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29
-msgid "server runs and this section is blocked"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31
-msgid ""
-"To collect this bounty, a continuous integration server (Jenkins,\n"
-"old name was Hudson) must be set up and a connected IRC bot needs \n"
-"to set up in the channel #i2p-dev on IRC2p network to print out\n"
-"results of build tests.
            \n"
-"The server needs to be run long term."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41
-msgid "Check existing SDK tests"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69
-msgid "paid to str4d"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45
-#, python-format
-msgid ""
-"To collect this bounty, the existing SDK tests must be checked \n"
-"and made to work again. The need to be integrated into the ant \n"
-"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g."
-" \n"
-"Clover).  The ant script\n"
-"must be capable of generating test status results as a web page, \n"
-"which will be published online."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56
-msgid "SDK test coverage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80
-msgid "paid to unittests dev team"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60
-msgid ""
-"To collect this bounty, the automated unit tests of the SDK \n"
-"(i2p/core/java/src) must work again."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67
-msgid "Router test migration"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71
-msgid ""
-"As with phase 2, the existing unit tests for the router must be\n"
-"moved over to the automated system."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78
-msgid "Router test coverage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82
-msgid ""
-"To collect this bounty, the automated unit tests of the router \n"
-"(i2p/router/java/src) must work again."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89
-msgid "Streaming lib tests"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94
-#, python-format
-msgid ""
-"To collect this bounty, a new set of unit tests must meet a \n"
-"measured code coverage of 90% of the streaming lib \n"
-"(i2p/apps/ministreaming/ and i2p/apps/streaming/)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102
-msgid "Unit tests coverage"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106
-msgid ""
-"To collect this bounty, all above unit tests must meet the 100%\n"
-"coverage marker (except for log statements)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113
-msgid "MultiRouter simulation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115
-msgid "will be split in more sub-tasks"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117
-msgid ""
-"To collect this bounty, the existing in-memory multi-router\n"
-"simulation must be checked, made work again and extend to simulate\n"
-"lots of routers in memory on a single machine. This bounty will\n"
-"be split in more fine grained subworks."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126
-msgid ""
-"Judge on all these works is the donor and donor decides if a phase is\n"
-"called succesfull done and money can be paid."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2
-msgid "Bounty I2P vuze plugin"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3
-msgid "vuze plugin"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6
-msgid ""
-"To improve I2P usage and attract more people\n"
-"into I2P torrent P2P I setout the bounty for a working I2P vuze\n"
-"plugin.\n"
-"The plugin needs to be official and submitted to vuze for publication\n"
-"on their webpage/repository for plugins.\n"
-"It should be easy to install and configured, work smooth and flawless.\n"
-"Configuration should be friendly to starters and made easy to be "
-"anonymous.\n"
-"It should work with *.b32.i2p destinations as with signed (516++ bits) \n"
-"destinations."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:2
-msgid "Application Development"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:6
-msgid "Application Development Guide"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:10
-#: i2p2www/pages/site/get-involved/develop/applications.html:16
-msgid "Why write I2P-specific code?"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:11
-#: i2p2www/pages/site/get-involved/develop/applications.html:102
-msgid "Important concepts"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:12
-#: i2p2www/pages/site/get-involved/develop/applications.html:190
-msgid "Development options"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:13
-#: i2p2www/pages/site/get-involved/develop/applications.html:303
-msgid "Start developing - a simple guide"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:18
-#, python-format
-msgid ""
-"There are multiple ways to use applications in I2P.\n"
-"Using I2PTunnel,\n"
-"you can use regular applications without needing to program explicit I2P "
-"support.\n"
-"This is very effective for client-server scenario's,\n"
-"where you need to connect to a single website.\n"
-"You can simply create a tunnel using I2PTunnel to connect to that "
-"website, as shown in Figure 1."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:26
-msgid ""
-"If your application is distributed, it will require connections to a "
-"large amount of peers.\n"
-"Using I2PTunnel, you will need to create a new tunnel for each peer you "
-"want to contact,\n"
-"as shown in Figure 2.\n"
-"This process can of course be automated, but running a lot of I2PTunnel "
-"instances creates a large amount of overhead.\n"
-"In addition, with many protocols you will need to force everyone to \n"
-"use the same set of ports for all peers - e.g. if you want to reliably "
-"run DCC \n"
-"chat, everyone needs to agree that port 10001 is Alice, port 10002 is "
-"Bob, port \n"
-"10003 is Charlie, and so on, since the protocol includes TCP/IP specific "
-"information\n"
-"(host and port)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:37
-msgid ""
-"General network applications often send a lot of additional data that "
-"could be used to identify users.\n"
-"Hostnames, port numbers, time zones, character sets, etc. are often sent "
-"without informing the user.\n"
-"As such, designing the network protocol specifically with anonymity in "
-"mind\n"
-"can avoid compromising user identities."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:43
-msgid ""
-"There are also efficiency considerations to review when determining how "
-"to \n"
-"interact on top of I2P.  The streaming library and things built on top of"
-" it\n"
-"operate with handshakes similar to TCP, while the core I2P protocols "
-"(I2NP and I2CP)\n"
-"are strictly message based (like UDP or in some instances raw IP).  The "
-"important\n"
-"distinction is that with I2P, communication is operating over a long fat "
-"network - \n"
-"each end to end message will have nontrivial latencies, but may contain "
-"payloads \n"
-"of up to several KB.  An application that needs a simple request and "
-"response can get rid\n"
-"of any state and drop the latency incurred by the startup and teardown "
-"handshakes\n"
-"by using (best effort) datagrams without having to worry about MTU "
-"detection or \n"
-"fragmentation of messages."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:57
-#: i2p2www/pages/site/get-involved/develop/applications.html:59
-msgid ""
-"Creating a server-client connection using I2PTunnel only requires "
-"creating a single tunnel."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:59
-msgid "Figure 1:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:64
-#: i2p2www/pages/site/get-involved/develop/applications.html:66
-msgid ""
-"Setting up connections for a peer-to-peer applications requires a very "
-"large amount of tunnels."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:66
-msgid "Figure 2:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:70
-msgid "In summary, a number of reasons to write I2P-specific code:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:74
-msgid ""
-"Creating a large amount of I2PTunnel instances consumes a non-trivial "
-"amount of resources,\n"
-"which is problematic for distributed applications (a new tunnel is "
-"required for each peer)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:78
-msgid ""
-"General network protocols often send a lot of additional data that can be"
-" used to identify users.\n"
-"Programming specifically for I2P allows the creation of a network "
-"protocol\n"
-"that does not leak such information, keeping users anonymous and secure."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:83
-msgid ""
-"Network protocols designed for use on the regular internet can be "
-"inefficient\n"
-"on I2P, which is a network with a much higher latency."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:90
-#, python-format
-msgid ""
-"I2P supports a standard plugins interface for"
-" developers\n"
-"so that applications may be easily integrated and distributed."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:96
-msgid ""
-"Applications written in Java and accessible/runnable\n"
-"using an HTML interface via the standard webapps/app.war\n"
-"may be considered for inclusion in the i2p distribution."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:104
-msgid "There are a few changes that require adjusting to when using I2P:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:108
-msgid "Destination ~= host+port"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:110
-msgid ""
-"An application running on I2P sends messages from and receives messages "
-"to a\n"
-"unique cryptographically secure end point - a \"destination\".  In TCP or"
-" UDP\n"
-"terms, a destination could (largely) be considered the equivalent of a "
-"hostname\n"
-"plus port number pair, though there are a few differences."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:118
-msgid ""
-"An I2P destination itself is a cryptographic construct - all data sent to"
-" one is \n"
-"encrypted as if there were universal deployment of IPsec with the "
-"(anonymized)\n"
-"location of the end point signed as if there were universal deployment of"
-" DNSSEC."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:123
-msgid ""
-"I2P destinations are mobile identifiers - they can be moved from one I2P "
-"router\n"
-"to another (or it can even \"multihome\" - operate on multiple routers at"
-"\n"
-"once).  This is quite different from the TCP or UDP world where a single "
-"end point (port)\n"
-"must stay on a single host."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:130
-msgid ""
-"I2P destinations are ugly and large - behind the scenes, they contain a "
-"2048 bit ElGamal\n"
-"public key for encryption, a 1024 bit DSA public key for signing, and a "
-"variable size \n"
-"certificate, which may contain proof of work or blinded data."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:135
-#, python-format
-msgid ""
-"There are existing ways to refer to these large and ugly destinations by "
-"short\n"
-"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not "
-"guarantee\n"
-"globally uniqueness (since they're stored locally in a database on each "
-"person's machine)\n"
-"and the current mechanism is not especially scalable nor secure (updates "
-"to the host list are\n"
-"managed using \"subscriptions\" to naming services).\n"
-"There may be some secure, human readable, scalable, and globally \n"
-"unique, naming system some day, but applications shouldn't depend upon it"
-" being in place,\n"
-"since there are those who don't think such a beast is possible.\n"
-"Further information on the naming system is "
-"available."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:149
-#, python-format
-msgid ""
-"While most applications do not need to distinguish protocols and ports,\n"
-"I2P does support them. Complex applications may specify a "
-"protocol,\n"
-"from port, and to port, on a per-message basis, to multiplex traffic on\n"
-"a single destination.\n"
-"See the datagram page for details.\n"
-"Simple applications operate by listening for \"all protocols\" on \"all "
-"ports\" of a destination."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:158
-msgid "Anonymity and confidentiality"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:160
-msgid ""
-"I2P has transparent end to end encryption\n"
-"and authentication for all data passed over the network - if Bob sends to"
-" Alice's destination,\n"
-"only Alice's destination can receive it, and if Bob is using the "
-"datagrams or streaming \n"
-"library, Alice knows for certain that Bob's destination is the one who "
-"sent the data."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:167
-msgid ""
-"Of course, I2P transparently anonymizes the\n"
-"data sent between Alice and Bob, but it does nothing to anonymize the "
-"content of what they\n"
-"send.  For instance, if Alice sends Bob a form with her full name, "
-"government IDs, and \n"
-"credit card numbers, there is nothing I2P can do.  As such, protocols and"
-" applications should \n"
-"keep in mind what information they are trying to protect and what "
-"information they are willing\n"
-"to expose."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:176
-msgid "I2P datagrams can be up to several KB"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:178
-#, python-format
-msgid ""
-"Applications that use I2P datagrams (either raw or repliable ones) can "
-"essentially be thought\n"
-"of in terms of UDP - the datagrams are unordered, best effort, and "
-"connectionless - but unlike\n"
-"UDP, applications don't need to worry about MTU detection and can simply "
-"fire off large datagrams.\n"
-"While the upper limit is nominally 32 KB, the message is fragmented for "
-"transport, thus dropping\n"
-"the reliability of the whole. Datagrams over about 10 KB are not "
-"currently recommended.\n"
-"See the datagram page for details.\n"
-"For many applications, 10 KB of data is sufficient for an\n"
-"entire request or response, allowing them to transparently operate in I2P"
-" as a UDP-like \n"
-"application without having to write fragmentation, resends, etc."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:192
-msgid ""
-"There are several means of sending data over I2P, each with their own "
-"pros and cons.\n"
-"The streaming lib is the recommended interface, used by the majority of "
-"I2P applications."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:197
-msgid "Streaming Lib"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:198
-#, python-format
-msgid ""
-"The full streaming library is now the "
-"standard\n"
-"interface. It allows programming using TCP-like sockets, as explained in "
-"the Streaming development guide."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:204
-#, python-format
-msgid ""
-"BOB is the Basic Open Bridge,\n"
-"allowing an application in any language to make streaming connections \n"
-"to and from I2P. At this point in time it lacks UDP support, but UDP "
-"support\n"
-"is planned in the near future. BOB also contains several tools, such as \n"
-"destination key generation, and verification that an address conforms to"
-" \n"
-"I2P specifications. Up to date info and applications that use BOB can be"
-" \n"
-"found at this eepsite."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:217
-msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:218
-#, python-format
-msgid ""
-"SAM is the Simple Anonymous Messaging protocol, "
-"allowing an\n"
-"application written in any language to talk to a SAM bridge through a "
-"plain TCP socket and have\n"
-"that bridge multiplex all of its I2P traffic, transparently coordinating "
-"the encryption/decryption\n"
-"and event based handling.  SAM supports three styles of operation:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:225
-msgid ""
-"streams, for when Alice and Bob want to send data to each other reliably "
-"and in order"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:228
-msgid ""
-"repliable datagrams, for when Alice wants to send Bob a message that Bob "
-"can reply to"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:231
-msgid ""
-"raw datagrams, for when Alice wants to squeeze the most bandwidth and "
-"performance as possible,\n"
-"and Bob doesn't care whether the data's sender is authenticated or not "
-"(e.g. the data transferred\n"
-"is self authenticating)"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:237
-msgid ""
-"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n"
-"multiplexing/demultiplexing. Each I2P stream is handled by its own socket"
-" between the application\n"
-"and the SAM bridge. Besides, datagrams can be sent and received by the "
-"application through datagram\n"
-"communications with the SAM bridge."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:244
-#, python-format
-msgid ""
-"SAM V2 is a new version used by imule\n"
-"that fixes some of the problems in SAM.\n"
-"
            \n"
-"SAM V3 is used by imule since version 1.4.0."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:252
-msgid ""
-"The I2PTunnel application allows applications to build specific TCP-like "
-"tunnels to peers \n"
-"by creating either I2PTunnel 'client' applications (which listen on a "
-"specific port and connect\n"
-"to a specific I2P destination whenever a socket to that port is opened) "
-"or I2PTunnel 'server'\n"
-"applications (which listen to a specific I2P destination and whenever it "
-"gets a new I2P \n"
-"connection it outproxies to a specific TCP host/port).  These streams are"
-" 8-bit clean, and are\n"
-"authenticated and secured through the same streaming library that SAM "
-"uses, but there is a \n"
-"nontrivial overhead involved with creating multiple unique I2PTunnel "
-"instances, since each have\n"
-"their own unique I2P destination and their own set of tunnels, keys, etc."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:264
-msgid ""
-"I2P supports a SOCKS V4 and V5 proxy.\n"
-"Outbound connections work well. Inbound (server) and UDP functionality "
-"may be incomplete\n"
-"and untested."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:271
-msgid "Removed"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:272
-msgid ""
-"There used to be a simple \"ministreaming\" library,\n"
-"but now ministreaming.jar contains only the interfaces for the full "
-"streaming library."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:278
-msgid "Recommended for UDP-like applications"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:279
-#, python-format
-msgid ""
-"The Datagram library allows sending UDP-"
-"like packets.\n"
-"It's possible to use:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:284
-msgid "Repliable datagrams"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:285
-msgid "Raw datagrams"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:289
-msgid "Not recommended"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:290
-#, python-format
-msgid ""
-"I2CP itself is a language independent protocol, "
-"but to implement an I2CP library \n"
-"in something other than Java there is a significant amount of code to be "
-"written (encryption routines, \n"
-"object marshalling, asynchronous message handling, etc).  While someone "
-"could write an I2CP library in \n"
-"C or something else, it would most likely be more useful to use the C SAM"
-" library instead."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:297
-msgid "Web Applications"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:298
-msgid ""
-"I2P comes with the Jetty webserver, and configuring to use the Apache "
-"server instead is straightforward.\n"
-"Any standard web app technology should work."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:304
-msgid ""
-"Developing using I2P requires a working I2P installation and a "
-"development environment of your own choice.\n"
-"If you are using Java, you can start development with the streaming library or datagram library.\n"
-"Using another programming language, SAM or BOB can be used."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:310
-msgid "Developing with the streaming library"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:312
-msgid ""
-"The following example shows how to create TCP-like client and server "
-"applications\n"
-"using the streaming library."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:317
-msgid "This will require the following libraries in your classpath:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:321
-msgid "The streaming library itself"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:322
-msgid "Factory and interfaces for the streaming library"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:323
-msgid "Standard I2P classes, data structures, API, and utilities"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:326
-msgid ""
-"Network communication requires the usage of I2P network sockets.\n"
-"To demonstrate this, we will create an application where a client can "
-"send text messages to a server,\n"
-"who will print the messages and send them back to the client. In other "
-"words, the server will function as an echo."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:331
-msgid ""
-"We will start by initializing the server application. This requires "
-"getting an I2PSocketManager\n"
-"and creating an I2PServerSocket.\n"
-"We will not provide the I2PSocketManagerFactory with the saved keys for "
-"an existing Destination,\n"
-"so it will create a new Destination for us.\n"
-"So we will ask the I2PSocketManager for an I2PSession, so we can find out"
-" the Destination that\n"
-"was created, as we will need to copy and paste that information later so "
-"the client can connect to us."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:362
-msgid "Code example 1: initializing the server application."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:364
-msgid ""
-"Once we have an I2PServerSocket, we can create I2PSocket instances to "
-"accept connections from clients.\n"
-"In this example, we will create a single I2PSocket instance, that can "
-"only handle one client at a time.\n"
-"A real server would have to be able to handle multiple clients.\n"
-"To do this, multiple I2PSocket instances would have to be created, each "
-"in separate threads.\n"
-"Once we have created the I2PSocket instance, we read data, print it and "
-"send it back to the client.\n"
-"The bold code is the new code we add."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:448
-msgid "Code example 2: accepting connections from clients and handling messages."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:452
-msgid ""
-"When you run the above server code, it should print something like this "
-"(but without the line endings, it should just be\n"
-"one huge block of characters):"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:466
-msgid ""
-"This is the base64-representation of the server Destination. The client "
-"will need this string to reach the server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:470
-msgid ""
-"Now, we will create the client application. Again, a number of steps are "
-"required for initialization.\n"
-"Again, we will need to start by getting an I2PSocketManager.\n"
-"We won't use an I2PSession and an I2PServerSocket this time.\n"
-"Instead, we will use the server Destination string to start our "
-"connection.\n"
-"We will ask the user for the Destination string, and create an I2PSocket "
-"using this string.\n"
-"Once we have an I2PSocket, we can start sending and receiving data to and"
-" from the server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:554
-msgid ""
-"Code example 3: starting the client and connecting it to the server "
-"application."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:556
-msgid ""
-"Finally, you can run both the server and the client application.\n"
-"First, start the server application. It will print a Destination string "
-"(like shown above).\n"
-"Next, start the client application. When it requests a Destination "
-"string, you can enter the string printed by the server.\n"
-"The client will then send 'Hello I2P!' (along with a newline) to the "
-"server, who will print the message and send it back to the client."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:562
-msgid "Congratulations, you have successfully communicated over I2P!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:566
-msgid "Existing Applications"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:567
-msgid "Contact us if you would like to contribute."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:588
-msgid "Application Ideas"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:590
-msgid "NNTP server - there have been some in the past, none at the moment"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:593
-msgid ""
-"Jabber server - there have been some in the past, and there is one at the"
-" moment, with access to the public internet"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:596
-msgid "PGP Key server and/or proxy"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:599
-msgid ""
-"Content Distribution / DHT applications - resurrect feedspace,\n"
-"port dijjer, look for alternatives"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:603
-msgid "Help out with Syndie development"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:606
-msgid ""
-"Web-based applications - The sky is the limit for hosting web-server-"
-"based\n"
-"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n"
-"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/applications.html:611
-msgid ""
-"Resurrect some old apps, several previously in the i2p source package -\n"
-"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2
-msgid "I2P Developer's MTN Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4
-msgid "MTN Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5
-msgid ""
-"Monotone servers used by the I2P project require two types of keys to be "
-"used."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
-msgid ""
-"Commit Keys to sign changes checked-in to the "
-"respository; and"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10
-msgid ""
-"Transport Keys to push changes to remote "
-"servers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13
-#, python-format
-msgid ""
-"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
-"import the\n"
-"developer commit keys, but only Monotone \n"
-"server operators will need to import the transport keys."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20
-msgid "Developer Commit keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:240
-msgid "Developer Transport Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/developers-keys.html:241
-#, python-format
-msgid ""
-"Note: Transport keys are only needed for setting up a\n"
-"Monotone server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
-msgid "License Agreements"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
-#, python-format
-msgid "For more information see the licenses page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8
-msgid ""
-"Following is a monotonerc file defining the current trust list.\n"
-"Developers must use this file in ~/.monotone/monotonerc or\n"
-"_MTN/montonerc in their i2p.i2p workspace."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17
-msgid "Agreements"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:4
-msgid "I2P Software Licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:5
-#, python-format
-msgid ""
-"As required by our\n"
-"threat model (among other reasons), the \n"
-"software developed to support the anonymous communication \n"
-"network we call I2P must be freely available, open source, \n"
-"and user modifiable.  To meet these criteria, we make use of\n"
-"a variety of legal and software engineering techniques so\n"
-"as to remove as many barriers to entry for those considering\n"
-"making use of or contributing to the I2P effort."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:16
-msgid ""
-"While the information below may be more confusing than just simply \n"
-"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
-"the short answer to the question \"How is I2P licensed?\" is this:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:22
-msgid "All software bundled in the I2P distributions will allow:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:24
-msgid "use without fee"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:25
-msgid ""
-"use with no restrictions on how, when, where, why, or by whom is running "
-"it"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:26
-msgid "access to the source code without fee"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:27
-msgid "modifications to the source"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:30
-msgid ""
-"Most of the software guarantees much more - the ability of anyone "
-"to \n"
-"distribute the modified source however they choose.  However, not all of "
-"the \n"
-"software bundled provides this freedom - the GPL restricts the ability of"
-" \n"
-"developers who wish to integrate I2P with their own applications that are"
-" not \n"
-"themselves open source applications.  While we applaud the noble goals of"
-" \n"
-"increasing the resources in the commons, I2P is best served by removing "
-"any\n"
-"barriers that stand in the way of its adoption - if a developer "
-"considering whether\n"
-"they can integrate I2P with their application has to stop and check with "
-"their lawyer,\n"
-"or conduct a code audit to make sure their own source can be released as "
-"GPL-compatible,\n"
-"we lose out."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:43
-msgid "Component licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:44
-msgid ""
-"The I2P distribution contains several resources, reflecting the "
-"partitioning of \n"
-"the source code into components.  Each component has its own license, "
-"which all \n"
-"developers who contribute to it agree to - either by explicitly declaring"
-" the release\n"
-"of code committed under a license compatible with that component, or by "
-"implicitly\n"
-"releasing the code committed under the component's primary license.  Each"
-" of these \n"
-"components has a lead developer who has the final say as to what license "
-"is compatible\n"
-"with the component's primary license, and the I2P project manager has the"
-" final say as\n"
-"to what licenses meet the above four guarantees for inclusion in the I2P "
-"distribution."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:57
-msgid "Component"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:58
-msgid "Source path"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:59
-msgid "Resource"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:60
-msgid "Primary license"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:61
-msgid "Alternate licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:62
-msgid "Lead developer"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:271
-msgid "GPL + java exception"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:272
-#, python-format
-msgid ""
-"While it may be redundant, just for clarity the\n"
-"GPL'ed code included within\n"
-"I2PTunnel and other apps must be released under the GPL with an "
-"additional \"exception\"\n"
-"explicitly authorizing the use of Java's standard libraries:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:288
-msgid ""
-"All source code under each component will by default be licensed under "
-"the\n"
-"primary license, unless marked otherwise in the code.  All of the above "
-"is\n"
-"summary of the license terms - please see the specific license for the "
-"component\n"
-"or source code in question for authoritative terms.  Component source "
-"locations and\n"
-"resource packaging may be changed if the repository is reorganized."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:296
-msgid "Commit privileges"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:297
-#, python-format
-msgid ""
-"Developers may push changes to a distributed monotone repository if you\n"
-"receive permission from the person running that repository.\n"
-"See the Monotone Page for details."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:303
-msgid ""
-"However, to have changes included in a release, developers\n"
-"must be trusted by the release manager (currently zzz).\n"
-"In addition, they must explicitly agree with the above terms to be "
-"trusted.\n"
-"That means that they must send one of the release managers a signed "
-"message affirming that:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:310
-msgid ""
-"Unless marked otherwise, all code I commit is implicitly licensed under\n"
-"the component's primary license"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:314
-msgid ""
-"If specified in the source, the code may be explicitly licensed under one"
-"\n"
-"of the component's alternate licenses"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:318
-msgid ""
-"I have the right to release the code I commit under the terms I\n"
-"am committing it"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/licenses.html:324
-#, python-format
-msgid ""
-"If anyone is aware of any instances where the above conditions are not "
-"met,\n"
-"please contact the component lead and/or an I2P release manager with "
-"further\n"
-"information.\n"
-"See developers' license agreements."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
-msgid "Release Signing Key"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
-msgid "Releases 0.7.6 and later are signed by zzz. His public key is:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40
-msgid ""
-"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public "
-"key is:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2
-msgid "Signed Developer Keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4
-msgid ""
-"Keys for zzz, Complication and welterde are provided clearsigned. The key"
-" for jrandom must be\n"
-"verified differently, since he's away, and only left a binary detached\n"
-"signature for his key."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16
-msgid "Monotone keys for zzz"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47
-msgid "Monotone keys for welterde"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79
-msgid "Monotone keys for Complication"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114
-msgid "Monotone keys for jrandom"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
-msgid ""
-"Tip: To find zzz's GPG key, on his eepsite locate the key "
-"`0xA76E0BED`, with\n"
-"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 "
-"B310 4155\n"
-"76BA A76E 0BED`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49
-msgid ""
-"Tip: To find welterde's GPG key, on public keyservers locate the "
-"key\n"
-"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720"
-" FD81\n"
-"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81
-msgid ""
-"Tip: To find Complication's GPG key, on his eepsite locate the key"
-"\n"
-"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint "
-"`73CF\n"
-"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116
-msgid ""
-"Tip: To find jrandom's GPG key for Syndie releases, on public "
-"keyservers locate\n"
-"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n"
-"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122
-msgid ""
-"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n"
-"deployed in the Syndie Monotone repository, in a file named `mtn-"
-"committers`.\n"
-"That file also had a GPG signature, `mtn-committers.sig`, but it was a "
-"binary\n"
-"detached signature. I am going to supply both files in GPG ASCII-armoured"
-" form\n"
-"below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130
-msgid ""
-"First, the file `mtn-committers` containing jrandom's Monotone key. Save "
-"as\n"
-"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers "
-"--dearmor\n"
-"mtn-committers.asc`:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151
-msgid ""
-"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n"
-"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-"
-"committers.sig\n"
-"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n"
-"`mtn-committers` file:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170
-#, python-format
-msgid ""
-"Some of the developers have included their Monotone keys in their signed license agreement."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2
-msgid "Developer Guidelines and Coding Style"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4
-#, python-format
-msgid "Read the new developers guide first."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8
-msgid "Basic Guidelines and Coding Style"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10
-msgid ""
-"Most of the following should be common sense for anybody who has worked "
-"on open source or in a commercial\n"
-"programming envrionment.\n"
-"The following applies mostly to the main development branch i2p.i2p.\n"
-"Guidelines for other branches, plugins, and external apps may be "
-"substantially different;\n"
-"check with the appropriate developer for guidance."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18
-msgid "Community"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20
-msgid ""
-"Please don't just \"write code\". If you can, participate in other "
-"development activities, including:\n"
-"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
-"testing;\n"
-"bug reporting and responses; documentation; code reviews; etc."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25
-msgid ""
-"Active devs should be available periodically on IRC #i2p-dev.\n"
-"Be aware of the current release cycle.\n"
-"Adhere to release milestones such as feature freeze, tag freeze, and\n"
-"the checkin deadline for a release."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35
-msgid ""
-"Have a basic understanding of distributed source control systems, even if"
-" you haven't\n"
-"used monotone before. Ask for help if you need it.\n"
-"Once pushed, checkins are forever, there is no undo. Please be careful.\n"
-"If you have not used monotone before, start with baby steps.\n"
-"Check in some small changes and see how it goes."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42
-msgid ""
-"Test your changes before checking them in.\n"
-"If you prefer the checkin-before-test development model,\n"
-"use your own development branch (e.g. i2p.i2p.yourname.test)\n"
-"and propagate back to i2p.i2p once it is working well.\n"
-"Do not break the build. Do not cause regressions.\n"
-"In case you do (it happens), please do not vanish for a long period after"
-"\n"
-"you push your change."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51
-msgid ""
-"If your change is non-trivial, or you want people to test it and need "
-"good test reports\n"
-"to know whether your change was tested or not, add a checkin comment to "
-"history.txt\n"
-"and increment the build revision in RouterVersion.java."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56
-msgid ""
-"Ensure that you have the latest monotonerc file in _MTN.\n"
-"Do not check in on top of untrusted revisions."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60
-msgid ""
-"Ensure that you pull the latest revision before you check in.\n"
-"If you inadvertently diverge, merge and push as soon as possible.\n"
-"Don't routinely make others merge for you.\n"
-"Yes, we know that monotone says you should push and then merge,\n"
-"but in our experience, in-workspace merge works just as well as in-"
-"database merge,\n"
-"without creating a merge revision."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
-msgid ""
-"Do not check in major changes into the main i2p.i2p branch late in the "
-"release cycle.\n"
-"If a project will take you more than a couple days, create your own "
-"branch in monotone\n"
-"and do the development there so you do not block releases."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75
-msgid "Coding Style"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77
-msgid ""
-"Coding style throughout most of the code is 4-spaces for indentation. Do "
-"not use tabs.\n"
-"Do not reformat code. If your IDE or editor wants to reformat everything,"
-" get control of it.\n"
-"Yes, we know 4 spaces is a pain, but perhaps you can configure your "
-"editor appropriately.\n"
-"In some places, the coding style is different.\n"
-"Use common sense. Emulate the style in the file you are modifying."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84
-msgid ""
-"New classes and methods require at least brief javadocs. Add @since "
-"release-number."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87
-msgid ""
-"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our "
-"official API.\n"
-"There are several out-of-tree plugins and other applications that rely on"
-" this API.\n"
-"Be careful not to make any changes that break compatibility.\n"
-"Don't add methods to the API unless they are of general utility.\n"
-"Javadocs for API methods should be clear and complete.\n"
-"If you add or change the API, also update the documentation on the "
-"website (i2p.www branch)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95
-msgid ""
-"Tag strings for translation where appropriate.\n"
-"Don't change existing tagged strings unless really necessary, as it will "
-"break existing translations.\n"
-"Do not add or change tagged strings after the \"tag freeze\" in the "
-"release cycle so that\n"
-"translators have a chance to update before the release."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101
-msgid ""
-"Use generics and concurrent classes where possible. I2P is a highly "
-"multi-threaded application."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104
-msgid ""
-"We require Java 6 to build but only Java 5 to run I2P.\n"
-"Do not use Java 6 classes or methods without handling the class not found"
-" exceptions\n"
-"and providing alternate Java 5 code. See classes in net.i2p.util for "
-"examples."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109
-msgid ""
-"Explicitly convert between primitive types and classes;\n"
-"don't rely on autoboxing/unboxing."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117
-msgid ""
-"Only check in code that you wrote yourself.\n"
-"Before checking in any code or library jars from other sources,\n"
-"justify why it is necessary,\n"
-"verify the license is compatible,\n"
-"and obtain approval from the lead developer."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124
-msgid ""
-"For any images checked in from external sources,\n"
-"it is your responsibility to first verify the license is compatible.\n"
-"Include the license and source information in the checkin comment."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131
-msgid "Bugs"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
-#, python-format
-msgid ""
-"Managing Trac tickets is everybody's job, please help.\n"
-"Monitor %(trac)s for tickets you have been assigned or can help with.\n"
-"Assign, categorize, comment on, fix, or close tickets if you can."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138
-msgid ""
-"Close a ticket when you think you've fixed it.\n"
-"We don't have a test department to verify and close tickets.\n"
-"If you arent sure you fixed it, close it and add a note saying\n"
-"\"I think I fixed it, please test and reopen if it's still broken\".\n"
-"Add a comment with the dev build number or revision and set\n"
-"the milestone to the next release."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:4
-msgid ""
-"The main I2P development branch (i2p.i2p) has been set up to"
-" enable developers to easily set up two of the commonly-used IDEs for "
-"Java development: Eclipse and NetBeans."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:10
-msgid ""
-"The main I2P development branches (i2p.i2p and branches from"
-" it) contain .project and .classpath Eclipse files, to enable the branch "
-"to be easily set up in Eclipse."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:16
-msgid ""
-"Check out the I2P branch into some directory (e.g. "
-"$HOME/dev/i2p.i2p)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:20
-msgid ""
-"Open Eclipse and create a new Workspace, based in the directory that the "
-"I2P branch was checked out to."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:24
-msgid ""
-"Select \"File - Import...\" and then under \"General\" select \"Existing "
-"Projects into Workspace\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:28
-msgid ""
-"For \"Select root directory:\" choose the directory that the I2P branch "
-"was checked out to."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:32
-msgid "If necessary, click \"Refresh\" to refresh the list of projects."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:36
-msgid "Select every project in the list, and click \"Finish\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:40
-msgid ""
-"Done! Your workspace should now contain all projects within the I2P "
-"branch, and their build dependencies should be correctly set up."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/ides.html:48
-msgid ""
-"The main I2P development branches (i2p.i2p and branches from"
-" it) contain NetBeans project files."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:9
-msgid "Operating a Monotone client"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:11
-#: i2p2www/pages/site/get-involved/guides/monotone.html:63
-msgid "Generating Monotone keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:12
-msgid "Trust and initializing your repository"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:13
-#: i2p2www/pages/site/get-involved/guides/monotone.html:196
-msgid "Obtaining and deploying developers' keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:14
-#: i2p2www/pages/site/get-involved/guides/monotone.html:227
-msgid "Setting up trust evaluation hooks"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:15
-#: i2p2www/pages/site/get-involved/guides/monotone.html:268
-msgid ""
-"Pulling the i2p.i2p, i2p.www and "
-"i2p.syndie branches"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:16
-#: i2p2www/pages/site/get-involved/guides/monotone.html:308
-msgid "Verifying that trust evaluation works"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:17
-#: i2p2www/pages/site/get-involved/guides/monotone.html:357
-msgid "Checking out a working copy of the latest version"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:18
-#: i2p2www/pages/site/get-involved/guides/monotone.html:384
-msgid "Updating your working copy to the latest version"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:22
-#: i2p2www/pages/site/get-involved/guides/monotone.html:414
-msgid "Operating a Monotone Server"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:24
-msgid "Obtaining and deploying developers’ transport keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:25
-#: i2p2www/pages/site/get-involved/guides/monotone.html:424
-msgid "Granting push and pull access"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:26
-#: i2p2www/pages/site/get-involved/guides/monotone.html:469
-msgid "Running Monotone in server mode"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:27
-#: i2p2www/pages/site/get-involved/guides/monotone.html:494
-msgid "Differences under Debian GNU/Linux"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:34
-#, python-format
-msgid ""
-"This is a revised version of Complication's original\n"
-"  guide detailing the use of Monotone in I2P development.\n"
-"  For basic instructions see the quick-start "
-"guide."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:42
-#, python-format
-msgid ""
-"I2P has a distributed development model. The source code is replicated "
-"across\n"
-"  independently administered Monotone (\"MTN\") repositories.\n"
-"  Developers with commit rights are able to push their changes to the "
-"repository\n"
-"  (a license agreement needs to be "
-"signed\n"
-"  before commit rights are granted)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:52
-msgid ""
-"Some of Monotone's noteworthy qualities are: distributed\n"
-"  version control, cryptographic authentication, access control, its "
-"small size, having few\n"
-"  dependencies, storage of projects in a compressed SQLite database file,"
-" and\n"
-"  having the ability to resume interrupted synchronization attempts."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:61
-msgid "Operating a Monotone Client"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:66
-msgid ""
-"A transport key grants you the ability to push your changes to a Monotone"
-" repository server.\n"
-"  In order to commit code into Monotone (in essence signing your code), a"
-" commit key is also needed.\n"
-"  None of the public Monotone servers on I2P currently require a key in "
-"order to read (or pull) the source code."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:74
-msgid ""
-"Without a transport key, one cannot:\n"
-"  
              \n"
-"    
            • pull code from a server which doesn't allow global read "
-"access
              • \n"
-"    
            • push code to any server
              • \n"
-"    
            • run a Monotone server
              • \n"
-"  
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:85
-msgid ""
-"Without a commit key, one cannot:\n"
-"  
              \n"
-"    
            • commit any code
              • \n"
-"  
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:94
-msgid ""
-"If you only intend to retrieve code from MTN, feel free to skip to the\n"
-"  next section. "
-"If you want\n"
-"  to generate keys, read the following."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:102
-msgid ""
-"By convention keys are named like an e-mail addresses, but a "
-"corresponding e-mail\n"
-"  address does not need to exist. For example, your keys might be named:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:113
-msgid ""
-"Monotone stores keys under $HOME/.monotone/keys in "
-"text files which\n"
-"  are named identically to the keys. For example:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:123
-msgid ""
-"To generate transport and commit keys, enter the following commands at a "
-"prompt:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:133
-msgid ""
-"Monotone will prompt you for a password to protect your keys. You are "
-"very strongly encouraged to set a password\n"
-"  for the commit key. Many users will leave an empty password for the "
-"transport key, especially those running a\n"
-"  Monotone server."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:141
-msgid "Trust, and initializing your repository"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:145
-msgid ""
-"Monotone's security model helps to ensure that nobody can easily "
-"impersonate a developer without\n"
-"  it being noticed. Since developers can make mistakes and become "
-"compromised,only manual review can\n"
-"  ensure quality of code. Monotone's trust model will ensure that you "
-"read the right diffs. It does\n"
-"  not replace reading diffs."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:155
-msgid ""
-"A Monotone repository is a single file (a compressed SQLite database) "
-"which contains all of the project's source code and history."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:161
-msgid ""
-"After importing the "
-"developers' keys into Monotone and\n"
-"  setting up trust "
-"evaluation hooks,\n"
-"  Monotone will prevent untrusted code from being checked out into your "
-"workspace.\n"
-"  There are commands available to clean untrusted code from your "
-"workspace but in practice they've not been\n"
-"  needed due to the push access policies in place."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:171
-msgid ""
-"A repository can hold many branches. For example, our repository holds "
-"the\n"
-"  following main branches:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:176
-msgid "The I2P router and associated programs"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:177
-msgid "The I2P project website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:178
-msgid "Syndie, a distributed forums tool"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:183
-msgid ""
-"By convention, the I2P Monotone repository is named i2p.mtn."
-" Before pulling\n"
-"  source code from servers, a database for your repository will need to "
-"be initialized.\n"
-"  To initialize your local repository, change into the directory that you"
-" want the\n"
-"  i2p.mtn file and branch directories to be stored and issue"
-" the following\n"
-"  command:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:199
-msgid ""
-"Keys which developers use to commit code are essential for trust "
-"evaluation in\n"
-"  Monotone. The other developers' transport keys are only required for "
-"Monotone server operators.\n"
-"  "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:206
-#, python-format
-msgid ""
-"Developers' commit keys are provided GPG-signed on another page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:212
-#, python-format
-msgid ""
-"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
-"  file. Create this file (e.g. keys.txt) in the same "
-"directory where i2p.mtn is located. Import the keys with the"
-" command:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:222
-msgid ""
-"Note: Never add keys to "
-"$HOME/.monotone/keys manually."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:230
-msgid ""
-"The default Monotone trust policy is way too lax for our requirements: "
-"every comitter is trusted by default.\n"
-"  That is not acceptable for I2P development."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:237
-msgid ""
-"Change into the directory $HOME/.monotone and open "
-"the file\n"
-"  monotonerc with a text editor. Copy and paste the "
-"following two functions into this file:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:246
-msgid ""
-"The first function determines an intersection between two sets, in our "
-"case a\n"
-"  revision's signers and trusted signers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:253
-msgid ""
-"The second function determines trust in a given revision, by calling the "
-"first\n"
-"  function with \"signers\" and \"trusted\" as arguments. If the "
-"intersection is\n"
-"  null, the revision is not trusted. If the intersection is not empty, "
-"the\n"
-"  revision is trusted. Otherwise, the revision is not trusted."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:262
-msgid ""
-"More information about Trust Evauluation Hooks can be found in the official Monotone "
-"documentation."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:271
-msgid ""
-"Enter the directory where you initialized i2p.mtn. Depending "
-"on whether you\n"
-"  want only I2P sources, or also sources for the I2P website and Syndie, "
-"you can\n"
-"  perform the pull operation in different ways."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:279
-msgid "If you only want I2P sources:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:288
-msgid "If you want all branches:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:294
-msgid ""
-"If the transfer aborts before completing sucessfully, simply repeating "
-"the pull command will resume the transfer."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:300
-msgid ""
-"Pulling in the above examples is done anonymously by specifying an empty "
-"transport key.\n"
-"  If everyone pulls anonymously it will be harder for an attacker who "
-"gains control of the server\n"
-"  to selectively provide some people with tampered data."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:311
-msgid "To verify that trust evaluation works:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:315
-msgid "Make a backup of your monotonerc file."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:316
-msgid ""
-"Modify monotonerc by setting the trusted_signers "
-"variable in the following way:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:322
-msgid ""
-"With monotonerc configured as above, Monotone will no"
-" longer trust any committers. Confirm this by changing into the\n"
-"directory where i2p.mtn was created and attempt a checkout "
-"of the I2P branch:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:332
-msgid ""
-"A directory named i2p.i2p should not appear. You "
-"should encounter many\n"
-"  error messages like:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:349
-msgid ""
-"If you are satisfied with results, restore the backup of\n"
-"  monotonerc that was created above. If you didn't create a "
-"backup\n"
-"  as advised, re-read Setting up trust evaluation hools."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:360
-msgid ""
-"If you already have a branch checked out, skip to the next\n"
-"  section."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:367
-msgid ""
-"Change into the directory where i2p.mtn is located. Over "
-"there issue:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:376
-msgid ""
-"The checkout should complete without error messages and a directory named"
-"\n"
-"  i2p.i2p should appear in the current directory. "
-"Congratulations! You have\n"
-"  successfully checked out the latest I2P sources, ready to be compiled."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:387
-msgid ""
-"If you haven't done this already, pull fresh code from the server to your"
-" local\n"
-"  Monotone repository. To accomplish this, change into the directory "
-"where\n"
-"  i2p.mtn is located and issue:\n"
-"  
              \n"
-"    
            • $ mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
-"i2p.i2p
              • \n"
-"  
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:398
-msgid "Now change into your i2p.i2p directory, and over there issue:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:407
-msgid ""
-"As long as there were no errors…Congratulations! You have "
-"successfully updated to the latest I2P sources. They\n"
-"  should be ready to compile."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:416
-msgid "Obtaining and deploying developers' transport keys"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:419
-msgid ""
-"As a server operator you may want to grant push access to certain "
-"developers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:427
-msgid "By default the Monotone server denies all access."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:433
-msgid "To grant pull access to all clients, set the following in"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:445
-msgid ""
-"No one will not be able to push code to your server without permission "
-"being explicitly granted. To grant push access:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:451
-msgid ""
-"Add the name of the user's transport key to\n"
-"$HOME/.monotone/write-permissions, such as\n"
-"
            \n"
-"    zzz-transport@mail.i2p\n"
-"    complication-transport@mail.i2p\n"
-"
            \n"
-"with one key per line."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:462
-msgid ""
-"Import the transport key(s) into your database. The procedure for "
-"importing transport keys is the same as for\n"
-"importing commit keys, which is described in the section Obtaining and deploying "
-"developers' keys."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:472
-msgid ""
-"A separate database should be used for your Monotone server because "
-"monotone will lock the database while it is served to others.\n"
-"  Make a copy of your development database, then start the server with:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:479
-msgid ""
-"If your key is protected with a passphrase, Monotone may request the "
-"passphrase\n"
-"  when the first client connects. You can work around this by connecting "
-"making the first client connection to your server\n"
-"  (or by clearing the password for your transport key)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:487
-msgid ""
-"For your server to be accessible for others over I2P, you will need to "
-"create a\n"
-"  server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" "
-"profile."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:497
-msgid ""
-"Debian (amongst other distributions) has integrated Monotone into their\n"
-"  framework of daemons/services. Although Monotone servers can still be "
-"run\n"
-"  \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may"
-" be more straightforward."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/monotone.html:505
-msgid ""
-"Permissions are granted by editing the files\n"
-"  /etc/monotone/read-permissions and\n"
-"  /etc/monotone/write-permissions. You'll also need to edit\n"
-"  /etc/default/monotone to enable monotone to start at boot "
-"or to\n"
-"  customize the host, port, or database location."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
-msgid ""
-"\n"
-"So you want to start work on I2P? Great!\n"
-"Here's a quick guide to getting started\n"
-"on contributing to the website or the software, doing development or "
-"creating translations."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
-#, python-format
-msgid ""
-"\n"
-"Not quite ready for coding?\n"
-"Try getting involved first."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
-msgid "Basic study"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
-msgid "Getting the I2P code"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
-msgid "Building I2P"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
-msgid "Development ideas"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
-msgid "Making the results available"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
-msgid "Get to know us!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
-msgid "Translations"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
-msgid "Tools"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
-msgid ""
-"Basic development on the I2P router or the embedded applications uses "
-"Java as the main development language.\n"
-"If you don't have experience with Java, you can always have a look at Thinking in Java."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
-#, python-format
-msgid ""
-"Study the how intro,\n"
-"the other \"how\" documents,\n"
-"the tech intro,\n"
-"and associated documents.\n"
-"These will give you a good overview of how I2P is structured and what "
-"different things it does."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
-msgid ""
-"For development on the i2p router or the embedded applications,\n"
-"get the monotone source repository installed - short instructions:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
-msgid ""
-"Install monotone.\n"
-"Monotone is a version control system.\n"
-"We use it because it allows us to keep track of who does what changes to "
-"the source code (and for a lot of complicated things, but 'keeping track "
-"of changes' is the basic idea)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
-msgid ""
-"Skim over the monotone tutorial,"
-" to make sure you understand the concepts."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
-msgid ""
-"If you want to remain anonymous, you need to do an additional step, to "
-"set up a connection to a monotone server over I2P:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
-#, python-format
-msgid ""
-"Enable the i2ptunnel client tunnel on port "
-"8998 pointing to mtn.i2p2.i2p."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
-msgid ""
-"Pick a directory where you want to put all your I2P files, and create a "
-"monotone database:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
-msgid ""
-"Define the trust list by creating ~/.monotone/monotonerc (or"
-" _MTN/monotonerc in the i2p.i2p workspace) with the "
-"following contents:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
-#, python-format
-msgid ""
-"Copy and paste the developer's commit keys "
-"into a new file (e.g. keys.txt) in the same directory\n"
-"  that i2p.mtn is in. Import the keys into your database "
-"with 
                  mtn -d i2p.mtn read < keys.txt
            "
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:76
-msgid ""
-"Pull the I2P sources to your machine. This may take a long time, "
-"especially if you are doing this over I2P!"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:78
-msgid "Anonymously:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:81
-msgid "Non-anonymously:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:83
-msgid ""
-"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn"
-".i2p-projekt.de."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:90
-msgid ""
-"All the sources are now present on your machine, in the database file. To"
-" make them available in a directory, you need to check them out:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:92
-msgid ""
-"The above command creates a directory i2p.i2p, which contains all of the "
-"I2P sources."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:96
-msgid "Remarks"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:97
-msgid ""
-"\n"
-"To download the website files instead of the I2P source files, use "
-"'i2p.www' instead of 'i2p.i2p'."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:100
-msgid ""
-"The initial pull may take several hours using the tunnel.\n"
-"If it fails after a partial pull, simply rerun it, it will start where it"
-" left off.\n"
-"If you are in a hurry, use the non-anonymous access."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:105
-#, python-format
-msgid ""
-"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
-#, python-format
-msgid ""
-"A long explanation about using monotone is available on the monotone page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
-#, python-format
-msgid ""
-"To compile the code, you need the Sun Java Development Kit 6 or higher, "
-"or equivalent JDK\n"
-"(Sun JDK 6 strongly recommended) and\n"
-"Apache ant\n"
-"version 1.7.0 or higher.\n"
-"If you go are working on the main I2P code, you can go into the i2p.i2p "
-"directory and run 'ant' to see the build options."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
-msgid ""
-"To build or work on console translations, you need\n"
-"the xgettext, msgfmt, and msgmerge tools from the\n"
-"GNU gettext package."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
-#, python-format
-msgid ""
-"For development on new applications,\n"
-"see the application development guide."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
-#, python-format
-msgid ""
-"See zzz's TODO lists,\n"
-"this website's TODO list or\n"
-"Trac\n"
-"for ideas."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
-#, python-format
-msgid ""
-"See the bottom of the licenses page "
-"for\n"
-"commit privilege requirements. You need these to put code into i2p.i2p "
-"(not required for the website!)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
-msgid "Short version of how to generate and use keys if you plan to commit:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
-msgid "use an empty passphrase"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
-msgid "enter a passphrase"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
-#, python-format
-msgid ""
-"send this to a mtn repo operator to get "
-"push privileges"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
-#, python-format
-msgid ""
-"send this to a release manager to get "
-"commit privileges - not required for website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
-msgid "check in with this key"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
-msgid "push with this key"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
-#, python-format
-msgid "Long version: see the monotone page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
-#, python-format
-msgid ""
-"The developers hang around on IRC. They can be reached on the Freenode "
-"network, OFTC, and on the I2P internal networks. The usual place to look "
-"is #i2p-dev. Join the channel and say hi!\n"
-"We also have additional guidelines for regular"
-" developers."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
-#, python-format
-msgid ""
-"Website and router console translators: See the New Translator's Guide\n"
-"for next steps."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
-msgid ""
-"I2P is open source software that is mostly developed using open sourced\n"
-"toolkits. The I2P project recently acquired a license for the YourKit "
-"Java\n"
-"Profiler. Open source projects are eligible to receive a free license "
-"provided\n"
-"that YourKit is referenced on the project web site. Please get in touch "
-"if you\n"
-"are interested in profiling the I2P codebase."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
-#, python-format
-msgid ""
-"YourKit is kindly supporting open source projects with its full-featured "
-"Java Profiler.\n"
-"YourKit, LLC is the creator of innovative and intelligent tools for "
-"profiling\n"
-"Java and .NET applications. Take a look at YourKit's leading software "
-"products:\n"
-"YourKit Java Profiler and\n"
-"YourKit .NET Profiler."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
-msgid "Here's a very quick guide to getting started."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
-msgid "How to Translate the Website"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
-#, python-format
-msgid ""
-"Translation of the website is done with .po files. The easiest way by far"
-" to\n"
-"translate the website is to sign up for an account at \n"
-"Transifex and request to join a translation"
-" team. \n"
-"Alternatively it can be done \"the old way\" as outlined below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
-msgid "Preparation"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
-#, python-format
-msgid ""
-"Come to #i2p-dev on irc and talk to people.\n"
-"Claim the language -\n"
-"To make sure other coworkers don't bump onto the files you are working "
-"on,\n"
-"please update the translation status on this wiki "
-"page."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
-#, python-format
-msgid ""
-"Follow the new developer's guide,\n"
-"Including the installation of monotone,\n"
-"checking out i2p.www branch, and generate your own monotone keys.\n"
-"It is not required that you sign a dev agreement."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
-msgid ""
-"Create files:\n"
-"If the file for your language does not exist yet:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
-msgid ""
-"Run \"./extract-messages.sh\" to generate a "
-"messages.pot in the base directory.\n"
-"Edit the header of this file, then run \"./init-new-po.sh "
-"locale\" to generate the file\n"
-"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
-"\"mtn add\" this file."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
-msgid ""
-"Edit i2p2www/pages/global/lang.html and add a line for your "
-"language (copy an existing line)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
-msgid ""
-"Add a flag image file to i2p2www/static/images/flags/ for "
-"the menu (copy from the router)."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
-msgid ""
-"Edit files:\n"
-"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
-"To work with .po files efficiently, you may wish to use POEdit"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
-msgid ""
-"Check in:\n"
-"\"mtn pull\", \"mtn update\". Then check in by "
-"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
-"This collects the diff info of your changed file into your local repo. "
-"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
-"i2p.i2p\".\n"
-"This synchronizes your local repo with the repo on the target machine."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
-msgid "Repeat. Check in often. Don't wait until it is perfect."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
-msgid "How to Translate the Router Console"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
-#, python-format
-msgid ""
-"The easiest way by far to translate the router console is to sign up for "
-"an account at \n"
-"Transifex and request to join a translation"
-" team. \n"
-"Alternatively it can be done \"the old way\" as outlined below."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
-#, python-format
-msgid ""
-"Follow the new developer's guide,\n"
-"including the installation of monotone and the gettext tools,\n"
-"checking out i2p.i2p branch, and generate your own monotone keys."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
-msgid "Generate your own gpg key and sign the dev agreement."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
-msgid ""
-"Before starting a console translation, better help translate some i2p "
-"webpages first.\n"
-"At least an i2p homepage in your language would be great."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
-msgid ""
-"What to translate:\n"
-"There are about 15 files in the i2p.i2p branch that needs translation:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
-msgid ""
-"Where xx is your language code like fr/de/ch/zh/...\n"
-"There may be or may not be files with your lang code. If not, you can "
-"create your own. by copying and renaming other language files you know "
-"with your own lang code."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
-msgid ""
-"Create files:\n"
-"If the file for your language does not exist yet, copy another language "
-"file to a new file foo_xx.bar for your language.\n"
-"Then \"mtn add\" the file.\n"
-"After creating a .po file, edit the headers. Then run \"ant "
-"distclean poupdate\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
-msgid ""
-"Start to work:\n"
-"Edit the HTML files with any text editor.\n"
-"Be sure not to use an editor in HTML mode that reformats everything.\n"
-"To work with .po files efficiently, you may wish to use POEdit"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
-msgid ""
-"As you can see, it's not that difficult.\n"
-"If you have questions about the meaning of the terms in the console, ask "
-"in #i2p-dev on IRC."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
-msgid ""
-"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
-"and html, etc.? Why can't I just do a translation and email it to you?"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
-msgid "A: Several reasons:"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
-#, python-format
-msgid ""
-"You might be interested in translating via Transifex. Request to join a "
-"translation team here."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
-msgid ""
-"We don't have anybody who has time to accept manual contributions and "
-"submit them to our source control system on your behalf. Even if we did, "
-"it doesn't scale."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
-msgid ""
-"Maybe you are thinking translation is a one-step process. It isn't. You "
-"can't do it all at once. You will make mistakes. You need to test it and "
-"tweak it to make it look right before you submit it. Developers "
-"will update or add to the English text, thus requiring a translation "
-"update."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
-msgid ""
-"Having translators use a source control system directly provides "
-"authentication and accountablility - we know who is doing what, and we "
-"can track changes, and revert them if necessary."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
-msgid ""
-".po files are not difficult. If you don't want to work directly with "
-"them, we recommend 'poedit'."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
-msgid ""
-"HTML files are not difficult. Just ignore the html stuff and translate "
-"the text."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
-msgid ""
-"Installing and using monotone is not that difficult. Several of the "
-"translators and other contributors to I2P are non-programmers, and they "
-"use monotone regularly. Monotone is simply a source control system, it is"
-" not about \"coding\"."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
-msgid ""
-"Our items to translate are not \"documents\". They are html files and po "
-"files, with a specific format and character encoding (UTF-8) that must be"
-" maintained, and not corrupted by email programs or other methods of "
-"transfer."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
-msgid ""
-"We looked at 'pootle' as a front-end for translators. It didn't work "
-"well, needed an administrator, and a pootle-based process would suffer "
-"from a number of the above flaws."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
-msgid ""
-"In summary:\n"
-"Yes, we know it is somewhat of a hurdle to get started. It's really the "
-"only possible way we can do it. Give it a try, it really isn't that hard."
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
-msgid "More Information"
-msgstr ""
-
-#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
-#, python-format
-msgid ""
-"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
-msgstr ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: i2p2www/pages/site/misc/transition-guide.html:21
-msgid "Guide"
-msgstr ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: 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 ""
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:44
-msgid "Click \"Save\""
-msgstr ""
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:51
-msgid "Add the following line:"
-msgstr ""
-
-#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:55
-msgid "Click \"Apply\""
-msgstr ""
-
-#: 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 ""
-
-#: i2p2www/pages/site/research/index.html:2
-msgid "Academic Research"
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:4
-msgid ""
-"Academic research and analysis of I2P is an important part of ensuring "
-"that the software and network performs as expected and is safe for users "
-"in hostile environments."
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:8
-msgid ""
-"I2P can be run as a separate test network by controlling the locations "
-"that a new router reseeds from so that it only finds other test routers. "
-"Additionally, the router can be run on its own in a virtual network mode "
-"to enable testing the router in isolation; to enable this mode, add "
-"i2p.vmCommSystem=true to the router.config before starting."
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:12
-#, python-format
-msgid ""
-"If you are planning on conducting research on the live I2P network, "
-"please contact us before you commence your "
-"testing. While we do not discourage researchers from responsibly testing "
-"their ideas on the live network, if an attack becomes apparent and we "
-"don't have any line of communication then we will end up taking "
-"countermeasures which could interfere with the test."
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:16
-msgid "Prior Research"
-msgstr ""
-
-#: i2p2www/pages/site/research/index.html:18
-#, python-format
-msgid ""
-"A list of known published papers about I2P is available here."
-msgstr ""
-
-#: i2p2www/pages/site/research/papers.html:6
-msgid "Following are links to research papers about I2P."
-msgstr ""
-
-#: i2p2www/pages/site/research/papers.html:12
-msgid "Newest links are at the top of the page."
-msgstr ""
-
-#: i2p2www/pages/site/research/papers.html:17
-msgid "Papers and Research"
-msgstr ""
-
diff --git a/i2p2www/translations/ru/LC_MESSAGES/get-involved.po b/i2p2www/translations/ru/LC_MESSAGES/get-involved.po
new file mode 100644
index 00000000..dbd7b30f
--- /dev/null
+++ b/i2p2www/translations/ru/LC_MESSAGES/get-involved.po
@@ -0,0 +1,4128 @@
+# Russian (Russia) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# IOException , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-10-25 17:54+0000\n"
+"Last-Translator: IOException \n"
+"Language-Team: Russian (Russia) "
+"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 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/get-involved/donate.html:2
+#: i2p2www/pages/site/get-involved/index.html:77
+msgid "Donate"
+msgstr "Пожертвовать"
+
+#: i2p2www/pages/site/get-involved/donate.html:4
+msgid ""
+"Thank you for your interest in contributing to I2P!\n"
+"The details of how you\n"
+"can make your contribution are provided below."
+msgstr ""
+"Спасибо за ваш интерес проявленный к поддержке проекта I2P!\n"
+"Подробности о том как вы\n"
+"можете сделать свой вклад приведены ниже."
+
+#: i2p2www/pages/site/get-involved/donate.html:11
+#: i2p2www/pages/site/get-involved/donate.html:27
+#, python-format
+msgid ""
+"As of %(date)s, eche|on has been running a\n"
+"%(cointype)s account for the I2P project.\n"
+"If you'd like to donate using %(cointype)s, just transfer your\n"
+"desired amount of coins to the account %(account)s\n"
+"and leave eche|on a note if you'd like your donation to be\n"
+"mentioned on the I2P webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:22
+#: i2p2www/pages/site/get-involved/donate.html:38
+msgid "For easy usage, use the QR code below!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:44
+#, python-format
+msgid "You can donate direct via PayPal to the account \"%(account)s\"."
+msgstr "Вы можете пожертвовать на прямую через PayPal на аккаунт \"%(account)s\"."
+
+#: i2p2www/pages/site/get-involved/donate.html:50
+msgid "One time donation:"
+msgstr "Разовое пожертвование:"
+
+#: i2p2www/pages/site/get-involved/donate.html:64
+msgid "Donate 10 €/month for 12 months:"
+msgstr "Жертвовать по 10 €/месяц в течение 12 месяцев:"
+
+#: i2p2www/pages/site/get-involved/donate.html:72
+#: i2p2www/pages/site/get-involved/donate.html:84
+#: i2p2www/pages/site/get-involved/donate.html:96
+#: i2p2www/pages/site/get-involved/donate.html:108
+msgid "I2P donation "
+msgstr "пожертвовать I2P"
+
+#: i2p2www/pages/site/get-involved/donate.html:78
+msgid "Donate 20 €/month for 12 months:"
+msgstr "Жертвовать по 20 €/месяц в течение 12 месяцев:"
+
+#: i2p2www/pages/site/get-involved/donate.html:90
+msgid "Donate 30 €/month for 12 months:"
+msgstr "Жертвовать по 30 €/месяц в течение 12 месяцев:"
+
+#: i2p2www/pages/site/get-involved/donate.html:102
+msgid "Donate 50 €/month for 12 months:"
+msgstr "Жертвовать по 50 €/месяц в течение 12 месяцев:"
+
+#: i2p2www/pages/site/get-involved/donate.html:117
+msgid "Flattr this"
+msgstr "Через Flattr"
+
+#: i2p2www/pages/site/get-involved/donate.html:122
+msgid ""
+"If you want to keep more or less anonymous, the option to send money via "
+"mail is also available. But it is less secure\n"
+"as the envelope can be lost on the way to us."
+msgstr ""
+"Если вы хотите более или менее сохранить анонимность, вы можете отправить"
+" деньги почтой. Однако это менее безопасно\n"
+"так как конверт может потеряться по пути к нам. "
+
+#: i2p2www/pages/site/get-involved/donate.html:126
+#, python-format
+msgid ""
+"If you'd like to donate via  snail mail, send an email to %(email)s\n"
+" and you'll receive an email with instructions detailing how to proceed."
+msgstr ""
+"Если вы хотите сделать пожертвование по средствам бумажной почты, "
+"отправьте электронное письмо на адрес %(email)s\n"
+" и в ответ вы получите письмо с подробными инструкциями как это "
+"осуществить."
+
+#: i2p2www/pages/site/get-involved/donate.html:131
+#, python-format
+msgid ""
+"In the meantime, feel free to take a look at the generous donations that "
+"have been\n"
+"given in support of the I2P Project at the hall of fame."
+msgstr ""
+"А пока, вы можете взглянуть на щедрые пожертвования\n"
+"сделанные проекту I2P в зале славы."
+
+#: i2p2www/pages/site/get-involved/index.html:2
+msgid "Get Involved!"
+msgstr "Присоединяйтесь!"
+
+#: i2p2www/pages/site/get-involved/index.html:4
+msgid "We need your help!"
+msgstr "Нам нужна ваша помощь!"
+
+#: i2p2www/pages/site/get-involved/index.html:5
+msgid ""
+"To get involved, please feel free to join us on the #i2p IRC channel (on\n"
+"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or "
+"irc.postman.i2p)."
+msgstr ""
+"Что бы принять участие, не стесняясь заходите на наш IRC канал #i2p (на "
+"сервере\n"
+"irc.freenode.net, или в сети I2P на серверах irc.freshcoffee.i2p или "
+"irc.postman.i2p)."
+
+#: i2p2www/pages/site/get-involved/index.html:9
+#, python-format
+msgid ""
+"If you're interested in joining our team, please"
+" get in\n"
+"touch as we're always looking for eager contributors!"
+msgstr ""
+"Если вы хотите присоединить к нашей команде, "
+"пожалуйста, свяжитесь с нами, так как мы постоянно ищем новых активных "
+"участников."
+
+#: i2p2www/pages/site/get-involved/index.html:13
+msgid ""
+"We need help in many areas, and you don't need to know Java to "
+"contribute!\n"
+"Here's a list to help you get started!"
+msgstr ""
+"Нам нужна помощь по многим направлениям, поэтому вам не обязательно знать"
+" язык Java, чтобы оказать помощь!\n"
+"Вот список, который поможет вам начать!"
+
+#: i2p2www/pages/site/get-involved/index.html:18
+msgid "Spread the Word!"
+msgstr "Расскажите о нас!"
+
+#: i2p2www/pages/site/get-involved/index.html:19
+msgid ""
+"Tell people about I2P on forums, blogs, and comments to articles.\n"
+"Fix up the Wikipedia article about I2P in your language.\n"
+"Tell your friends."
+msgstr ""
+"Рассказывайте людям о I2P на форумах, в блогах и в комментариях к "
+"статьям.\n"
+"Исправляйте и дополняйте статьи о I2P в Википедии на вашем языке.\n"
+"Расскажите своим друзьям."
+
+#: i2p2www/pages/site/get-involved/index.html:24
+msgid "Testing"
+msgstr "Тестирование"
+
+#: i2p2www/pages/site/get-involved/index.html:25
+#, fuzzy, python-format
+msgid ""
+"Run the latest builds from monotone\n"
+"and report results on #i2p or as bugs on Trac."
+msgstr ""
+"Запускайте свежие сборки из репозитория monotone\n"
+"и сообщайте о результатах на канале #i2p или об ошибках в Trac."
+
+#: i2p2www/pages/site/get-involved/index.html:30
+msgid "Documentation"
+msgstr "Документация"
+
+#: i2p2www/pages/site/get-involved/index.html:31
+msgid ""
+"Help fix the parts of the website that are outdated or incomplete.\n"
+"Translate pages into other languages."
+msgstr ""
+"Помогите исправить разделы сайта, содержащие устаревшую или неполную "
+"информацию.\n"
+"Переводите страницы на другие языки."
+
+#: i2p2www/pages/site/get-involved/index.html:35
+msgid "Pictures"
+msgstr "Изображения"
+
+#: i2p2www/pages/site/get-involved/index.html:36
+msgid "Make some more pictures, fix the old ones on the website"
+msgstr "Добавьте больше картинок, обновите устаревшие на сайте"
+
+#: i2p2www/pages/site/get-involved/index.html:39
+msgid "Content"
+msgstr "Контент"
+
+#: i2p2www/pages/site/get-involved/index.html:40
+msgid "Make an eepsite! Add some content! Contribute to the community!"
+msgstr "Создайте eep-сайт! Добавьте содержимое! Сделайте вклад в сообщество!"
+
+#: i2p2www/pages/site/get-involved/index.html:43
+msgid "Services"
+msgstr "Службы"
+
+#: i2p2www/pages/site/get-involved/index.html:44
+msgid ""
+"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n"
+"a naming service, a search engine, an eepsite monitor... many of these\n"
+"aren't that hard."
+msgstr ""
+"Запустите службу на eep-сайте. Это может быть прокси-сервер, форум, "
+"трекер, служба имён, поисковый сервис, мониторинг eep-сайтов... много "
+"всего и это не так уж сложно."
+
+#: i2p2www/pages/site/get-involved/index.html:49
+msgid "Applications"
+msgstr "Программы"
+
+#: i2p2www/pages/site/get-involved/index.html:50
+#, python-format
+msgid ""
+"Write or port applications for I2P! There's some guidelines and\n"
+"a list of ideas on the applications page."
+msgstr ""
+"Создавайте или портируйте программы для I2P! Вы найдёте несколько "
+"руководств и список идей на странице приложений."
+
+#: i2p2www/pages/site/get-involved/index.html:54
+msgid "Coding"
+msgstr "Программируйте"
+
+#: i2p2www/pages/site/get-involved/index.html:55
+#, fuzzy, python-format
+msgid ""
+"There's plenty to do if you know Java or are ready to learn.\n"
+"Check for open tickets on Trac\n"
+"or the TODO list on %(zzz)s for\n"
+"some ideas on where to start.\n"
+"See the new developer's guide for details."
+msgstr ""
+"Есть много задач для реализации если вы знаете Java или готовы учить.\n"
+"Проверьте открытые заявки в Trac"
+"\n"
+"или в списке TODO %(zzz)s\n"
+"что бы определиться с чего можно начать.\n"
+"Просмотрите руководство разработчиков для "
+"выяснения подробностей."
+
+#: i2p2www/pages/site/get-involved/index.html:64
+msgid "Translation"
+msgstr "Перевод"
+
+#: i2p2www/pages/site/get-involved/index.html:65
+#, python-format
+msgid ""
+"Help translate the website and the software into your language.\n"
+"See the new translator's guide for details."
+msgstr ""
+"Помогите перевести веб-сайт и программное обеспечение на ваш язык.\n"
+"Обратитесь к руководству переводчика для "
+"подробностей."
+
+#: i2p2www/pages/site/get-involved/index.html:69
+msgid "Analysis"
+msgstr "Анализ"
+
+#: i2p2www/pages/site/get-involved/index.html:70
+#, python-format
+msgid ""
+"Study or test the code to look for vulnerabilities.\n"
+"Both anonymity vulnerabilities from the various\n"
+"threat models,\n"
+"and DOS and other weaknesses due to securities holes,\n"
+"need researching."
+msgstr ""
+"Изучайте или тестируйте исходный код для выявления уязвимостей.\n"
+"И различные модели угроз деанонимизации,\n"
+"и DOS, и другие проблемы безопасности требуют тщательного изучения."
+
+#: i2p2www/pages/site/get-involved/roadmap.html:2
+msgid "Roadmap"
+msgstr "План разработки"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:7
+msgid ""
+"Include some seed data in the distribution so a central reseed location "
+"isn't required?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:10
+#, python-format
+msgid ""
+"Reachability Mapping / handle peers partially reachable / enhanced restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:13
+msgid "Improve help pages and website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:14
+msgid "More translations"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:15
+msgid "SSU disconnect message"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:16
+msgid "Iterative floodfill lookups"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:21
+msgid "Full review of anonymity issues and other vulnerabilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:22
+msgid ""
+"Reduce memory usage, remove debugging overhead, make it run better on "
+"slow and embedded machines"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:25
+msgid "Docs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:30
+msgid "Full restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:35
+msgid "Tunnel mixing and padding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:36
+msgid "User defined message delays"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:39
+#, python-format
+msgid ""
+"Please see the TODO list for more detailed info "
+"about some of these tasks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:2
+msgid "To Do List"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:4
+msgid "I2P Project Targets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:5
+#, python-format
+msgid ""
+"Below is a more detailed (yet still incomplete) discussion of the major "
+"areas\n"
+"of future development on the core I2P network, spanning the plausibly "
+"planned\n"
+"releases. This does not include stego transports, porting to wireless "
+"devices,\n"
+"or tools to secure the local machine, nor does it include client "
+"applications\n"
+"that will be essential in I2P's success. There are probably other things "
+"that\n"
+"will come up, especially as I2P gets more peer review, but these are the "
+"main\n"
+"'big things'. See also the roadmap. Want to "
+"help?\n"
+"Get involved!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:54
+msgid "Core functionality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:52
+msgid "link"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:18
+#: i2p2www/pages/site/get-involved/todo.html:57
+msgid "NAT/Firewall bridging via 1-hop restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:21
+#: i2p2www/pages/site/get-involved/todo.html:130
+msgid "High degree transport layer with UDP, NBIO, or NIO"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:24
+#: i2p2www/pages/site/get-involved/todo.html:218
+msgid "NetworkDB and profile tuning and ejection policy for large nets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:242
+msgid "Security / anonymity"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:30
+#: i2p2www/pages/site/get-involved/todo.html:245
+msgid ""
+"Per-hop tunnel id & new permuted TunnelVerificationStructure "
+"encryption"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:33
+#: i2p2www/pages/site/get-involved/todo.html:295
+msgid "Strict ordering of participants within tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:36
+msgid "Randomly permuted tunnel lengths"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:39
+#: i2p2www/pages/site/get-involved/todo.html:357
+msgid "Full blown n-hop restricted routes with optional trusted links"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:42
+#: i2p2www/pages/site/get-involved/todo.html:376
+msgid "Hashcash for routerIdentity, destination, and tunnel request"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:45
+#: i2p2www/pages/site/get-involved/todo.html:405
+msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:48
+#: i2p2www/pages/site/get-involved/todo.html:442
+msgid "Stop & go mix w/ garlics & tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:52
+#: i2p2www/pages/site/get-involved/todo.html:456
+msgid "Performance"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:62
+msgid "Implemented in I2P 0.6.0.6"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:63
+msgid ""
+"The functionality of allowing routers to fully participate within the "
+"network \n"
+"while behind firewalls and NATs that they do not control requires some "
+"basic \n"
+"restricted route operation (since those peers will not be able to receive"
+" \n"
+"inbound connections). To do this successfully, you consider peers one of"
+" \n"
+"two ways:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:73
+msgid ""
+"Peers who have reachable interfaces - these peers do not need to \n"
+"do anything special"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:77
+msgid ""
+"Peers who do not have reachable interfaces - these peers must "
+"build \n"
+"a tunnel pointing at them where the gateway is one of the peers they have"
+" \n"
+"established a connection with who has both a publicly reachable interface"
+" \n"
+"and who has agreed to serve as their 'introducer'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:85
+msgid ""
+"To do this, peers who have no IP address simply connect to a few peers, \n"
+"build a tunnel through them, and publish a reference to those tunnels "
+"within \n"
+"their RouterInfo structure in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:90
+msgid ""
+"When someone wants to contact any particular router, they first must get"
+" \n"
+"its RouterInfo from the network database, which will tell them whether "
+"they \n"
+"can connect directly (e.g. the peer has a publicly reachable interface) \n"
+"or whether they need to contact them indirectly. Direct connections occur"
+" \n"
+"as normal, while indirect connections are done through one of the "
+"published \n"
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:98
+msgid ""
+"When a router just wants to get a message or two to a specific hidden "
+"peer, \n"
+"they can just use the indirect tunnel for sending the payload. However, \n"
+"if the router wants to talk to the hidden peer often (for instance, as "
+"part \n"
+"of a tunnel), they will send a garlic routed message through the indirect"
+" \n"
+"tunnel to that hidden peer which unwraps to contain a message which "
+"should \n"
+"be sent to the originating router. That hidden peer then establishes an \n"
+"outbound connection to the originating router and from then on, those two"
+" \n"
+"routers can talk to each other directly over that newly established "
+"direct \n"
+"connection."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:109
+msgid ""
+"Of course, that only works if the originating peer can receive "
+"connections \n"
+"(they aren't also hidden). However, if the originating peer is hidden, "
+"they \n"
+"can simply direct the garlic routed message to come back to the "
+"originating \n"
+"peer's inbound tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:115
+msgid ""
+"This is not meant to provide a way for a peer's IP address to be "
+"concealed, \n"
+"merely as a way to let people behind firewalls and NATs fully operate "
+"within \n"
+"the network. Concealing the peer's IP address adds a little more work, as"
+" \n"
+"described below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:121
+msgid ""
+"With this technique, any router can participate as any part of a tunnel."
+" \n"
+"For efficiency purposes, a hidden peer would be a bad choice for an "
+"inbound \n"
+"gateway, and within any given tunnel, two neighboring peers wouldn't want"
+" \n"
+"to be hidden. But that is not technically necessary."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:133
+msgid "Both UDP and NIO have been Implemented in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:134
+msgid ""
+"Standard TCP communication in Java generally requires blocking socket \n"
+"calls, and to keep a blocked socket from hanging the entire system, those"
+" \n"
+"blocking calls are done on their own threads. Our current TCP transport \n"
+"is implemented in a naive fashion - for each peer we are talking to, we \n"
+"have one thread reading and one thread writing. The reader thread simply"
+" \n"
+"loops a bunch of read() calls, building I2NP messages and adding them \n"
+"to our internal inbound message queue, and the writer thread pulls "
+"messages \n"
+"off a per-connection outbound message queue and shoves the data through \n"
+"write() calls."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:145
+msgid ""
+"We do this fairly efficiently, from a CPU perspective - at any time, \n"
+"almost all of these threads are sitting idle, blocked waiting for "
+"something \n"
+"to do. However, each thread consumes real resources (on older Linux "
+"kernels, \n"
+"for instance, each thread would often be implemented as a fork()'ed "
+"process). \n"
+"As the network grows, the number of peers each router will want to talk \n"
+"with will increase (remember, I2P is fully connected, meaning that any \n"
+"given peer should know how to get a message to any other peer, and "
+"restricted \n"
+"route support will probably not significantly reduce the number of "
+"connections \n"
+"necessary). This means that with a 100,000 router network, each router \n"
+"will have up to 199,998 threads just to deal with the TCP connections!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:157
+msgid ""
+"Obviously, that just won't work. We need to use a transport layer that \n"
+"can scale. In Java, we have two main camps:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:162
+#, python-format
+msgid ""
+"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:165
+msgid ""
+"Sending and receiving UDP datagrams is a connectionless operation - if \n"
+"we are communicating with 100,000 peers, we simply stick the UDP packets"
+" \n"
+"in a queue and have a single thread pulling them off the queue and "
+"shoving \n"
+"them out the pipe (and to receive, have a single thread pulling in any \n"
+"UDP packets received and adding them to an inbound queue)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:172
+msgid ""
+"However, moving to UDP means losing the benefits of TCP's ordering, "
+"congestion \n"
+"control, MTU discovery, etc. Implementing that code will take significant"
+" \n"
+"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n"
+"a while ago I was taking some measurements in the simulator and on the \n"
+"live net, and the vast majority of messages transferred would fit easily"
+" \n"
+"within a single unfragmented UDP packet, and the largest of the messages"
+" \n"
+"would fit within 20-30 packets. As mule pointed out, TCP adds a "
+"significant \n"
+"overhead when dealing with so many small packets, as the ACKs are within"
+" \n"
+"an order of magnitude in size. With UDP, we can optimize the transport \n"
+"for both efficiency and resilience by taking into account I2P's "
+"particular \n"
+"needs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:185
+msgid "It will be a lot of work though."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:188
+msgid "NIO or NBIO"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:189
+msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:192
+msgid ""
+"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java"
+" \n"
+"developers to take advantage of the operating system's nonblocking IO \n"
+"capabilities - allowing you to maintain a large number of concurrent IO \n"
+"operations without requiring a separate thread for each. There is much \n"
+"promise with this approach, as we can scalable handle a large number of \n"
+"concurrent connections and we don't have to write a mini-TCP stack with \n"
+"UDP. However, the NIO packages have not proven themselves to be battle-"
+"ready, \n"
+"as the Freenet developer's found. In addition, requiring NIO support "
+"would \n"
+"mean we can't run on any of the open source JVMs like Kaffe, \n"
+"as GNU/Classpath has only "
+"limited \n"
+"support for NIO. (note: this may not be the case anymore, as there \n"
+"has been some progress on Classpath's NIO, but it is an unknown "
+"quantity)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:206
+#, python-format
+msgid ""
+"Another alternative along the same lines is the Non"
+" \n"
+"Blocking I/O package - essentially a cleanroom NIO implementation \n"
+"(written before NIO was around). It works by using some native OS code \n"
+"to do the nonblocking IO, passing off events through Java. It seems to \n"
+"be working with Kaffe, though there doesn't seem to be much development \n"
+"activity on it lately (likely due to 1.4's NIO deployment)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:221
+msgid ""
+"Within the current network database and profile management "
+"implementation, \n"
+"we have taken the liberty of some practical shortcuts. For instance, we \n"
+"don't have the code to drop peer references from the K-buckets, as we \n"
+"don't have enough peers to even plausibly fill any of them, so instead, \n"
+"we just keep the peers in whatever bucket is appropriate. Another example"
+" \n"
+"deals with the peer profiles - the memory required to maintain each "
+"peer's \n"
+"profile is small enough that we can keep thousands of full blown profiles"
+" \n"
+"in memory without problems. While we have the capacity to use trimmed \n"
+"down profiles (which we can maintain 100s of thousands in memory), we \n"
+"don't have any code to deal with moving a profile from a \"minimal "
+"profile\" \n"
+"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to"
+" simply \n"
+"eject a profile altogether. It just wouldn't be practical to write that \n"
+"code yet, since we aren't going to need it for a while."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:236
+msgid ""
+"That said, as the network grows we are going to want to keep these "
+"considerations \n"
+"in mind. We will have some work to do, but we can put it off for later."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:248
+#: i2p2www/pages/site/get-involved/todo.html:332
+#, python-format
+msgid ""
+"Addressed in I2P 0.5 as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:251
+msgid ""
+"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n"
+"going to Dave, then to Charlie, then Bob, and finally Alice "
+"(A<--B<--C<--D<--E), \n"
+"all five of them will know they are participating in tunnel \"123\", as \n"
+"the messages are tagged as such. What we want to do is give each hop "
+"their \n"
+"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n"
+"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n"
+"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n"
+"the tunnel had the same tunnel ID, collusion attacks aren't much work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:261
+msgid ""
+"Adding a unique tunnel ID per hop isn't hard, but by itself, "
+"insufficient. \n"
+"If Dave and Bob are under the control of the same attacker, they wouldn't"
+" \n"
+"be able to tell they are in the same tunnel due to the tunnel ID, but \n"
+"would be able to tell by the message bodies and verification structures \n"
+"by simply comparing them. To prevent that, the tunnel must use layered \n"
+"encryption along the path, both on the payload of the tunneled message \n"
+"and on the verification structure (used to prevent simple tagging "
+"attacks). \n"
+"This requires some simple modifications to the TunnelMessage, as well \n"
+"as the inclusion of per-hop secret keys delivered during tunnel creation"
+" \n"
+"and given to the tunnel's gateway. We must fix a maximum tunnel length \n"
+"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n"
+"of the 16 delivered secret keys, in reverse order, and to encrypt the \n"
+"signature of the hash of the (encrypted) payload at each step. The "
+"gateway \n"
+"then sends that 16-step encrypted message, along with a 16-step and "
+"16-wide \n"
+"encrypted mapping to the first hop, which then decrypts the mapping and \n"
+"the payload with their secret key, looking in the 16-wide mapping for \n"
+"the entry associated with their own hop (keyed by the per-hop tunnel ID)"
+" \n"
+"and verifying the payload by checking it against the associated signed \n"
+"hash."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:282
+msgid ""
+"The tunnel gateway does still have more information than the other peers"
+" \n"
+"in the tunnel, and compromising both the gateway and a tunnel participant"
+" \n"
+"would allow those peers to collude, exposing the fact that they are both"
+" \n"
+"in the same tunnel. In addition, neighboring peers know that they are \n"
+"in the same tunnel anyway, as they know who they send the message to (and"
+" \n"
+"with IP-based transports without restricted routes, they know who they \n"
+"got it from). However, the above two techniques significantly increase \n"
+"the cost of gaining meaningful samples when dealing with longer tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:298
+msgid "Implemented in release 0.6.2"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:301
+#, python-format
+msgid ""
+"As Connelly proposed to deal with the\n"
+"predecessor attack (2008\n"
+"update), keeping the order of peers within our tunnels consistent \n"
+"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n"
+"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n"
+"get to substantially sample Alice's peer selection group. We may even \n"
+"want to explicitly allow Bob to participate in Alice's tunnels in only \n"
+"one way - receiving a message from Dave and sending it to Charlie - and \n"
+"if any of those peers are not available to participate in the tunnel (due"
+" \n"
+"to overload, network disconnection, etc), avoid asking Bob to participate"
+" \n"
+"in any tunnels until they are back online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:316
+msgid ""
+"More analysis is necessary for revising the tunnel creation - at the \n"
+"moment, we simply select and order randomly within the peer's top tier \n"
+"of peers (ones with fast + high capacity)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:321
+msgid ""
+"Adding a strict ordering to peers in a tunnel also improves the anonymity"
+" \n"
+"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway"
+" \n"
+"is always the same would be particularly damning. However, peers with \n"
+"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n"
+"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n"
+"duration) minutes, use a 1-hop tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:338
+msgid ""
+"Without tunnel length permutation, if someone were to somehow detect that"
+" \n"
+"a destination had a particular number of hops, it might be able to use "
+"that \n"
+"information to identify the router the destination is located on, per the"
+" \n"
+"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n"
+"receives a tunnel message from Charlie and forwards it to Alice, Bob "
+"knows \n"
+"Alice is the final router in the tunnel. If Bob were to identify what "
+"destination \n"
+"that tunnel served (by means of colluding with the gateway and harvesting"
+" \n"
+"the network database for all of the LeaseSets), he would know the router"
+" \n"
+"on which that destination is located (and without restricted routes, that"
+" \n"
+"would mean what IP address the destination is on)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:350
+msgid ""
+"It is to counter user behavior that tunnel lengths should be permuted, \n"
+"using algorithms based on the length requested (for example, the 1/MTBF \n"
+"length change for 0-hop tunnels outlined above)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:360
+msgid ""
+"The restricted route functionality described before was simply a "
+"functional \n"
+"issue - how to let peers who would not otherwise be able to communicate \n"
+"do so. However, the concept of allowing restricted routes includes "
+"additional \n"
+"capabilities. For instance, if a router absolutely cannot risk "
+"communicating \n"
+"directly with any untrusted peers, they can set up trusted links through"
+" \n"
+"those peers, using them to both send and receive all of its messages. \n"
+"Those hidden peers who want to be completely isolated would also refuse \n"
+"to connect to peers who attempt to get them to (as demonstrated by the \n"
+"garlic routing technique outlined before) - they can simply take the "
+"garlic \n"
+"clove that has a request for delivery to a particular peer and tunnel \n"
+"route that message out one of the hidden peer's trusted links with "
+"instructions \n"
+"to forward it as requested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:379
+#, python-format
+msgid ""
+"Within the network, we will want some way to deter people from consuming"
+" \n"
+"too many resources or from creating so many peers to mount a Sybil \n"
+"attack. Traditional techniques such as having a peer see who is "
+"requesting \n"
+"a resource or running a peer aren't appropriate for use within I2P, as \n"
+"doing so would compromise the anonymity of the system. Instead, we want \n"
+"to make certain requests \"expensive\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:387
+msgid ""
+"Hashcash is one technique that \n"
+"we can use to anonymously increase the \"cost\" of doing certain "
+"activities, \n"
+"such as creating a new router identity (done only once on installation),"
+" \n"
+"creating a new destination (done only once when creating a service), or \n"
+"requesting that a peer participate in a tunnel (done often, perhaps 2-300"
+" \n"
+"times per hour). We don't know the \"correct\" cost of each type of "
+"certificate \n"
+"yet, but with some research and experimentation, we could set a base "
+"level \n"
+"that is sufficiently expensive while not an excessive burden for people \n"
+"with few resources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:398
+msgid ""
+"There are a few other algorithms that we can explore for making those \n"
+"requests for resources \"nonfree\", and further research on that front is"
+" \n"
+"appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:408
+#, python-format
+msgid ""
+"To powerful passive external observers as well as large colluding "
+"internal \n"
+"observers, standard tunnel routing is vulnerable to traffic analysis "
+"attacks \n"
+"- simply watching the size and frequency of messages being passed between"
+" \n"
+"routers. To defend against these, we will want to essentially turn some \n"
+"of the tunnels into its own mix cascade - delaying messages received at \n"
+"the gateway and passing them in batches, reordering them as necessary, \n"
+"and injecting dummy messages (indistinguishable from other \"real\" "
+"tunnel \n"
+"messages by peers in the path). There has been a significant amount of \n"
+"research \n"
+"on these algorithms that we can lean on prior to implementing the various"
+" \n"
+"tunnel mixing strategies."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:421
+msgid ""
+"In addition to the anonymity aspects of more varied tunnel operation, \n"
+"there is a functional dimension as well. Each peer only has a certain \n"
+"amount of data they can route for the network, and to keep any particular"
+" \n"
+"tunnel from consuming an unreasonable portion of that bandwidth, they \n"
+"will want to include some throttles on the tunnel. For instance, a tunnel"
+" \n"
+"may be configured to throttle itself after passing 600 messages (1 per \n"
+"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n"
+"last minute). Excess messages may be delayed or summarily dropped. With \n"
+"this sort of throttling, peers can provide ATM-like QoS support for their"
+" \n"
+"tunnels, refusing to agree to allocate more bandwidth than the peer has \n"
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:434
+msgid ""
+"In addition, we may want to implement code to dynamically reroute tunnels"
+" \n"
+"to avoid failed peers or to inject additional hops into the path. This \n"
+"can be done by garlic routing a message to any particular peer in a "
+"tunnel \n"
+"with instructions to redefine the next-hop in the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:445
+msgid ""
+"Beyond the per-tunnel batching and mixing strategy, there are further \n"
+"capabilities for protecting against powerful attackers, such as allowing"
+" \n"
+"each step in a garlic routed path to define a delay or window in which \n"
+"it should be forwarded on. This would enable protections against the long"
+" \n"
+"term intersection attack, as a peer could send a message that looks "
+"perfectly \n"
+"standard to most peers that pass it along, except at any peers where the"
+" \n"
+"clove exposed includes delay instructions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:457
+#, python-format
+msgid ""
+"Performance related improvements are listed on the\n"
+"Performance page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2
+msgid "Bounty Arabic translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3
+#: i2p2www/pages/site/get-involved/bounties/index.html:119
+msgid "Arabic translation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P echelon set out this bounty for translation\n"
+"of the I2P web page and I2P router console into Arabic."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12
+msgid "This bounty is set into 2 subparts:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14
+msgid "Part 1 is translation of the webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17
+msgid ""
+"For collecting the bounty of 20 BTC you need to translate the following "
+"pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25
+msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27
+msgid ""
+"Part 2 is the translation of the router console. The router console was\n"
+"partly translated and the bounty of 80 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34
+msgid "Judge is echelon."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2
+msgid "Bounty creating a I2P native Bitcoin client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3
+msgid "BTC I2P native client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to create a I2P native Bitcoin client. \n"
+"It should integrate with other client via the I2P network and via "
+"gateways to\n"
+"the existant bitcoin network."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15
+msgid "Judge is psychonaut who donated the first 30 € to this bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
+msgid "Bounty datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:3
+msgid "datastore"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:6
+msgid ""
+"To improve I2P's usage and to be independent of routers \n"
+"online status we want a datastorage as a extension to I2P.\n"
+"Like in Freenet the datastorage should be distributed and every\n"
+"participating node should be able to configure his options.\n"
+"The files should be saved in chunks and at least 2-3 times to\n"
+"obtain redundancy. Usage of storage space should be auto balanced.\n"
+"As it is a extra application, it should work flawless within I2P and\n"
+"cooperate nice with the I2P router. Maybe a integration within the\n"
+"webpage/router could be done."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:17
+msgid ""
+"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n"
+"\"eepsites in datastorage\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:21
+msgid ""
+"The frost for I2P datastorage bounty is paid for a frost like program \n"
+"with which files/messages are stored into database and got from database."
+"\n"
+"It needs to work with a GUI."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:26
+msgid ""
+"The eepsite served out of I2P datastorage extends a I2P router to send\n"
+"out eepsites out of the I2P datastorage. All files for eepsites need to "
+"be\n"
+"saved inside of datastorage and are taken from it.\n"
+"Extension:\n"
+"For better integration all datastorage participants could serve that "
+"eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:36
+msgid ""
+"For bounties to be declared done and paid, we need the program AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2
+msgid "Bounty I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3
+msgid "I2P Ubuntu/Debian package"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6
+msgid ""
+"For the future of I2P and in order to attract more people\n"
+"to I2P, this bounty was set for including an I2P package into the Ubuntu "
+"and Debian \n"
+"archive mirrors.\n"
+"To claim this bounty, the I2P router package needs to be available from\n"
+"Ubuntu and Debian archive mirrors and Debian bug \n"
+"448638 \n"
+"needs to be closed successfully."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2
+msgid "Bounty I2PHex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3
+msgid "i2phex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2PHex P2P ArneBab setout the bounty for implementing actual\n"
+"Phex code onto I2PHex."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:2
+msgid "Bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:5
+msgid "Bounties for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:6
+msgid ""
+"While we always gratefully accept any contributions of code, \n"
+"documentation, and the like, there are other ways to help I2P move \n"
+"forward.  As with any open source project, our goals would be achieved "
+"more \n"
+"rapidly if we were able to support all of our contributors to work on \n"
+"I2P full time.  However, as with any open source project, that's not a \n"
+"possibility.  Instead, we are making use of a bounty system, whereby \n"
+"anyone can get support for working on something that people want \n"
+"implemented, and people who want to contribute to I2P can be assured that"
+" \n"
+"their support goes to what they care about."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:18
+msgid ""
+"We are also keeping open the ability for people who want to support I2P \n"
+"but don't have strong feelings about the bounties available.  Those "
+"people\n"
+"can simply put their trust in the I2P team to do what we feel is best by\n"
+"donating to a catch-all general fund that will be used as deemed \n"
+"necessary - allocated to various bounties, covering incidentals (hosting,"
+" \n"
+"etc), and the like."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:27
+msgid "Current bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Name"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Status"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Judge"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Dev"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Bounty"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:32
+msgid "Frost for I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:33
+#: i2p2www/pages/site/get-involved/bounties/index.html:40
+#: i2p2www/pages/site/get-involved/bounties/index.html:47
+#: i2p2www/pages/site/get-involved/bounties/index.html:54
+#: i2p2www/pages/site/get-involved/bounties/index.html:75
+#: i2p2www/pages/site/get-involved/bounties/index.html:82
+msgid "Proposal in development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:35
+#: i2p2www/pages/site/get-involved/bounties/index.html:42
+#: i2p2www/pages/site/get-involved/bounties/index.html:49
+#: i2p2www/pages/site/get-involved/bounties/index.html:56
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+#: i2p2www/pages/site/get-involved/bounties/index.html:97
+msgid "vacant"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:39
+msgid "Eepsites served out of I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:46
+msgid "Backporting Phex code onto I2PHex"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:53
+msgid "I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:60
+msgid "Bitcoin client for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:61
+msgid "Done, phase of verification"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:67
+msgid "Unit tests and Multi-router Simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:68
+msgid "Partly done, partly in work, partly still open"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:89
+msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:94
+msgid "Bundling bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:95
+msgid "Proposed"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:102
+msgid "Claimed bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:107
+msgid "Make I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:114
+msgid "Setting up a SILC server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:124
+msgid "Datastore over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:129
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
+msgid "Russian translation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:134
+msgid "Swarming file transfer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:139
+msgid "Streaming library window size"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:144
+msgid "IRC connect time monitor"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:149
+msgid "Unit tests (part 1)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:161
+msgid ""
+"Dev lists anyone who may already be working on the bounty - collaboration"
+" is\n"
+"preferred, so if you're interested in working on it, please contact one "
+"of the\n"
+"people listed!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2
+msgid "Bounty I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3
+msgid "native IPv6 I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n"
+"To claim this bounty, the I2P router needs to run full on native\n"
+"IPv6 connections like it does on IPv4."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:17
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
+msgid ""
+"For bounties to be declared done and paid, we need the plugin AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:2
+msgid "NetDB Backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:3
+msgid "netDB backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:7
+msgid ""
+"The current NetDB implementation (namely the FloodFill system)\n"
+"needs to be extended with another backend to improve reliability,\n"
+"reduce attack surface and solve the scalability issue for the \n"
+"coming years."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:14
+msgid ""
+"A solution likely based on a DHT will be investigated and \n"
+"finally implemented."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2
+msgid "Bounty russian translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P a anonymous donator set out the bounty for translation\n"
+"of the I2P web page and I2P router console into russian language."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17
+msgid ""
+"For collecting the bounty of $115 USD you need to translate the following"
+" pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30
+msgid ""
+"Part 2 is the translation of the router console. The whole router console"
+" needs\n"
+"to be translated to collect the bounty of $115 USD."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37
+msgid "Judge is the russian donor."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:2
+msgid "Bounty migrate I2P IRC to SILC"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:3
+msgid "I2P silc server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:7
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to setup and host a I2P SILC server.   \n"
+"This will allow people to send files over their messaging servers and "
+"have intrinsic security built into the protocol."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:12
+msgid ""
+"A silc server needs to be set up and run for at least 3 month time to get"
+" payed. \n"
+"A second server should be set up, to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:16
+msgid ""
+"Bounty was withdrawn and money donated to returningnovice and general "
+"fund."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:22
+msgid "Judge is An Anonymous Secret Society, society@mail.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3
+msgid "Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7
+msgid ""
+"Beside of I2P we want to encourage users\n"
+"to care more about anonymity and security. As I2P is a low \n"
+"latency network with its natural limits, the software SYNDIE\n"
+"can overcome some of these limits and provide better anonymity\n"
+"for people who really need it."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14
+msgid ""
+"For our bad sake the syndie project was out of development for \n"
+"quite a long time yet (5 years). To get a fresh and new built \n"
+"with needed bugfixes we set out this bounty. Also syndie needs\n"
+"some enhancements and a better GUI for users to work with it.\n"
+"Current bounty sum is 50 Bitcoin."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22
+msgid ""
+"The latest Syndie coding rally did improve the situation of the\n"
+"Syndie package dramatically. A new Syndie package with bugfixes\n"
+"was created and made available on different webpages.\n"
+"As a result of this work, the bounty sum was reduced and\n"
+"the withdrawn money moved to the IPv6 bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2
+msgid "Bounty unittests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3
+msgid "unit test"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7
+msgid ""
+"To improve I2P's maintainability, we want to have a solid set of\n"
+"automated unit tests for the critical code.  While we do have some\n"
+"unit tests at the moment, they are ad-hoc and partly unfinished.  \n"
+"This bounty is for someone to check the existing tests and move over\n"
+"old ones to jUnit, automate their execution, extend them to provide \n"
+"better code coverage, and publish the report online.  Its a massive \n"
+"effort, but can be broken down into phases, listed below (phase 2 \n"
+"must occur first, but further phases may happen in any order).\n"
+"As this needs some reading of code, it is the best start point for\n"
+"new devs to get a good overview of I2P code and coding. A good job\n"
+"for college students, interns or anyone who is just interested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20
+msgid ""
+"Take care! Jobs and bounties shuffled a bit!\n"
+"Phase 6,7 and 8 are still open!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112
+#, python-format
+msgid "Phase %(phase)s:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27
+msgid "CI jenkins and IRC bot"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114
+#, python-format
+msgid "Bounty: %(euro)s €"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29
+msgid "server runs and this section is blocked"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31
+msgid ""
+"To collect this bounty, a continuous integration server (Jenkins,\n"
+"old name was Hudson) must be set up and a connected IRC bot needs \n"
+"to set up in the channel #i2p-dev on IRC2p network to print out\n"
+"results of build tests.
            \n"
+"The server needs to be run long term."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41
+msgid "Check existing SDK tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69
+msgid "paid to str4d"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45
+#, python-format
+msgid ""
+"To collect this bounty, the existing SDK tests must be checked \n"
+"and made to work again. The need to be integrated into the ant \n"
+"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g."
+" \n"
+"Clover).  The ant script\n"
+"must be capable of generating test status results as a web page, \n"
+"which will be published online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56
+msgid "SDK test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80
+msgid "paid to unittests dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60
+msgid ""
+"To collect this bounty, the automated unit tests of the SDK \n"
+"(i2p/core/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67
+msgid "Router test migration"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71
+msgid ""
+"As with phase 2, the existing unit tests for the router must be\n"
+"moved over to the automated system."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78
+msgid "Router test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82
+msgid ""
+"To collect this bounty, the automated unit tests of the router \n"
+"(i2p/router/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89
+msgid "Streaming lib tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94
+msgid ""
+"To collect this bounty, a new set of unit tests must meet a \n"
+"measured code coverage of 90% of the streaming lib \n"
+"(i2p/apps/ministreaming/ and i2p/apps/streaming/)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102
+msgid "Unit tests coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106
+msgid ""
+"To collect this bounty, all above unit tests must meet the 100%\n"
+"coverage marker (except for log statements)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113
+msgid "MultiRouter simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115
+msgid "will be split in more sub-tasks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117
+msgid ""
+"To collect this bounty, the existing in-memory multi-router\n"
+"simulation must be checked, made work again and extend to simulate\n"
+"lots of routers in memory on a single machine. This bounty will\n"
+"be split in more fine grained subworks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126
+msgid ""
+"Judge on all these works is the donor and donor decides if a phase is\n"
+"called succesfull done and money can be paid."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2
+msgid "Bounty I2P vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3
+msgid "vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P torrent P2P I setout the bounty for a working I2P vuze\n"
+"plugin.\n"
+"The plugin needs to be official and submitted to vuze for publication\n"
+"on their webpage/repository for plugins.\n"
+"It should be easy to install and configured, work smooth and flawless.\n"
+"Configuration should be friendly to starters and made easy to be "
+"anonymous.\n"
+"It should work with *.b32.i2p destinations as with signed (516++ bits) \n"
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:2
+msgid "Application Development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:3
+msgid "May 2013"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:6
+msgid "Application Development Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:8
+msgid "Contents"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:10
+#: i2p2www/pages/site/get-involved/develop/applications.html:16
+msgid "Why write I2P-specific code?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:11
+#: i2p2www/pages/site/get-involved/develop/applications.html:102
+msgid "Important concepts"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:12
+#: i2p2www/pages/site/get-involved/develop/applications.html:190
+msgid "Development options"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:13
+#: i2p2www/pages/site/get-involved/develop/applications.html:303
+msgid "Start developing - a simple guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:18
+#, python-format
+msgid ""
+"There are multiple ways to use applications in I2P.\n"
+"Using I2PTunnel,\n"
+"you can use regular applications without needing to program explicit I2P "
+"support.\n"
+"This is very effective for client-server scenario's,\n"
+"where you need to connect to a single website.\n"
+"You can simply create a tunnel using I2PTunnel to connect to that "
+"website, as shown in Figure 1."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:26
+msgid ""
+"If your application is distributed, it will require connections to a "
+"large amount of peers.\n"
+"Using I2PTunnel, you will need to create a new tunnel for each peer you "
+"want to contact,\n"
+"as shown in Figure 2.\n"
+"This process can of course be automated, but running a lot of I2PTunnel "
+"instances creates a large amount of overhead.\n"
+"In addition, with many protocols you will need to force everyone to \n"
+"use the same set of ports for all peers - e.g. if you want to reliably "
+"run DCC \n"
+"chat, everyone needs to agree that port 10001 is Alice, port 10002 is "
+"Bob, port \n"
+"10003 is Charlie, and so on, since the protocol includes TCP/IP specific "
+"information\n"
+"(host and port)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:37
+msgid ""
+"General network applications often send a lot of additional data that "
+"could be used to identify users.\n"
+"Hostnames, port numbers, time zones, character sets, etc. are often sent "
+"without informing the user.\n"
+"As such, designing the network protocol specifically with anonymity in "
+"mind\n"
+"can avoid compromising user identities."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:43
+msgid ""
+"There are also efficiency considerations to review when determining how "
+"to \n"
+"interact on top of I2P.  The streaming library and things built on top of"
+" it\n"
+"operate with handshakes similar to TCP, while the core I2P protocols "
+"(I2NP and I2CP)\n"
+"are strictly message based (like UDP or in some instances raw IP).  The "
+"important\n"
+"distinction is that with I2P, communication is operating over a long fat "
+"network - \n"
+"each end to end message will have nontrivial latencies, but may contain "
+"payloads \n"
+"of up to several KB.  An application that needs a simple request and "
+"response can get rid\n"
+"of any state and drop the latency incurred by the startup and teardown "
+"handshakes\n"
+"by using (best effort) datagrams without having to worry about MTU "
+"detection or \n"
+"fragmentation of messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:57
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid ""
+"Creating a server-client connection using I2PTunnel only requires "
+"creating a single tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid "Figure 1:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:64
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid ""
+"Setting up connections for a peer-to-peer applications requires a very "
+"large amount of tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid "Figure 2:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:70
+msgid "In summary, a number of reasons to write I2P-specific code:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:74
+msgid ""
+"Creating a large amount of I2PTunnel instances consumes a non-trivial "
+"amount of resources,\n"
+"which is problematic for distributed applications (a new tunnel is "
+"required for each peer)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:78
+msgid ""
+"General network protocols often send a lot of additional data that can be"
+" used to identify users.\n"
+"Programming specifically for I2P allows the creation of a network "
+"protocol\n"
+"that does not leak such information, keeping users anonymous and secure."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:83
+msgid ""
+"Network protocols designed for use on the regular internet can be "
+"inefficient\n"
+"on I2P, which is a network with a much higher latency."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:90
+#, python-format
+msgid ""
+"I2P supports a standard plugins interface for"
+" developers\n"
+"so that applications may be easily integrated and distributed."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:96
+msgid ""
+"Applications written in Java and accessible/runnable\n"
+"using an HTML interface via the standard webapps/app.war\n"
+"may be considered for inclusion in the i2p distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:104
+msgid "There are a few changes that require adjusting to when using I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:108
+msgid "Destination ~= host+port"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:110
+msgid ""
+"An application running on I2P sends messages from and receives messages "
+"to a\n"
+"unique cryptographically secure end point - a \"destination\".  In TCP or"
+" UDP\n"
+"terms, a destination could (largely) be considered the equivalent of a "
+"hostname\n"
+"plus port number pair, though there are a few differences."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:118
+msgid ""
+"An I2P destination itself is a cryptographic construct - all data sent to"
+" one is \n"
+"encrypted as if there were universal deployment of IPsec with the "
+"(anonymized)\n"
+"location of the end point signed as if there were universal deployment of"
+" DNSSEC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:123
+msgid ""
+"I2P destinations are mobile identifiers - they can be moved from one I2P "
+"router\n"
+"to another (or it can even \"multihome\" - operate on multiple routers at"
+"\n"
+"once).  This is quite different from the TCP or UDP world where a single "
+"end point (port)\n"
+"must stay on a single host."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:130
+msgid ""
+"I2P destinations are ugly and large - behind the scenes, they contain a "
+"2048 bit ElGamal\n"
+"public key for encryption, a 1024 bit DSA public key for signing, and a "
+"variable size \n"
+"certificate, which may contain proof of work or blinded data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:135
+#, python-format
+msgid ""
+"There are existing ways to refer to these large and ugly destinations by "
+"short\n"
+"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not "
+"guarantee\n"
+"globally uniqueness (since they're stored locally in a database on each "
+"person's machine)\n"
+"and the current mechanism is not especially scalable nor secure (updates "
+"to the host list are\n"
+"managed using \"subscriptions\" to naming services).\n"
+"There may be some secure, human readable, scalable, and globally \n"
+"unique, naming system some day, but applications shouldn't depend upon it"
+" being in place,\n"
+"since there are those who don't think such a beast is possible.\n"
+"Further information on the naming system is "
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:149
+#, python-format
+msgid ""
+"While most applications do not need to distinguish protocols and ports,\n"
+"I2P does support them. Complex applications may specify a "
+"protocol,\n"
+"from port, and to port, on a per-message basis, to multiplex traffic on\n"
+"a single destination.\n"
+"See the datagram page for details.\n"
+"Simple applications operate by listening for \"all protocols\" on \"all "
+"ports\" of a destination."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:158
+msgid "Anonymity and confidentiality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:160
+msgid ""
+"I2P has transparent end to end encryption\n"
+"and authentication for all data passed over the network - if Bob sends to"
+" Alice's destination,\n"
+"only Alice's destination can receive it, and if Bob is using the "
+"datagrams or streaming \n"
+"library, Alice knows for certain that Bob's destination is the one who "
+"sent the data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:167
+msgid ""
+"Of course, I2P transparently anonymizes the\n"
+"data sent between Alice and Bob, but it does nothing to anonymize the "
+"content of what they\n"
+"send.  For instance, if Alice sends Bob a form with her full name, "
+"government IDs, and \n"
+"credit card numbers, there is nothing I2P can do.  As such, protocols and"
+" applications should \n"
+"keep in mind what information they are trying to protect and what "
+"information they are willing\n"
+"to expose."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:176
+msgid "I2P datagrams can be up to several KB"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:178
+#, python-format
+msgid ""
+"Applications that use I2P datagrams (either raw or repliable ones) can "
+"essentially be thought\n"
+"of in terms of UDP - the datagrams are unordered, best effort, and "
+"connectionless - but unlike\n"
+"UDP, applications don't need to worry about MTU detection and can simply "
+"fire off large datagrams.\n"
+"While the upper limit is nominally 32 KB, the message is fragmented for "
+"transport, thus dropping\n"
+"the reliability of the whole. Datagrams over about 10 KB are not "
+"currently recommended.\n"
+"See the datagram page for details.\n"
+"For many applications, 10 KB of data is sufficient for an\n"
+"entire request or response, allowing them to transparently operate in I2P"
+" as a UDP-like \n"
+"application without having to write fragmentation, resends, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:192
+msgid ""
+"There are several means of sending data over I2P, each with their own "
+"pros and cons.\n"
+"The streaming lib is the recommended interface, used by the majority of "
+"I2P applications."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:197
+msgid "Streaming Lib"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:198
+#, python-format
+msgid ""
+"The full streaming library is now the "
+"standard\n"
+"interface. It allows programming using TCP-like sockets, as explained in "
+"the Streaming development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:204
+#, python-format
+msgid ""
+"BOB is the Basic Open Bridge,\n"
+"allowing an application in any language to make streaming connections \n"
+"to and from I2P. At this point in time it lacks UDP support, but UDP "
+"support\n"
+"is planned in the near future. BOB also contains several tools, such as \n"
+"destination key generation, and verification that an address conforms to"
+" \n"
+"I2P specifications. Up to date info and applications that use BOB can be"
+" \n"
+"found at this eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:217
+msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:218
+#, python-format
+msgid ""
+"SAM is the Simple Anonymous Messaging protocol, "
+"allowing an\n"
+"application written in any language to talk to a SAM bridge through a "
+"plain TCP socket and have\n"
+"that bridge multiplex all of its I2P traffic, transparently coordinating "
+"the encryption/decryption\n"
+"and event based handling.  SAM supports three styles of operation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:225
+msgid ""
+"streams, for when Alice and Bob want to send data to each other reliably "
+"and in order"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:228
+msgid ""
+"repliable datagrams, for when Alice wants to send Bob a message that Bob "
+"can reply to"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:231
+msgid ""
+"raw datagrams, for when Alice wants to squeeze the most bandwidth and "
+"performance as possible,\n"
+"and Bob doesn't care whether the data's sender is authenticated or not "
+"(e.g. the data transferred\n"
+"is self authenticating)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:237
+msgid ""
+"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n"
+"multiplexing/demultiplexing. Each I2P stream is handled by its own socket"
+" between the application\n"
+"and the SAM bridge. Besides, datagrams can be sent and received by the "
+"application through datagram\n"
+"communications with the SAM bridge."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:244
+#, python-format
+msgid ""
+"SAM V2 is a new version used by imule\n"
+"that fixes some of the problems in SAM.\n"
+"
            \n"
+"SAM V3 is used by imule since version 1.4.0."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:252
+msgid ""
+"The I2PTunnel application allows applications to build specific TCP-like "
+"tunnels to peers \n"
+"by creating either I2PTunnel 'client' applications (which listen on a "
+"specific port and connect\n"
+"to a specific I2P destination whenever a socket to that port is opened) "
+"or I2PTunnel 'server'\n"
+"applications (which listen to a specific I2P destination and whenever it "
+"gets a new I2P \n"
+"connection it outproxies to a specific TCP host/port).  These streams are"
+" 8-bit clean, and are\n"
+"authenticated and secured through the same streaming library that SAM "
+"uses, but there is a \n"
+"nontrivial overhead involved with creating multiple unique I2PTunnel "
+"instances, since each have\n"
+"their own unique I2P destination and their own set of tunnels, keys, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:264
+msgid ""
+"I2P supports a SOCKS V4 and V5 proxy.\n"
+"Outbound connections work well. Inbound (server) and UDP functionality "
+"may be incomplete\n"
+"and untested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:271
+msgid "Removed"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:272
+msgid ""
+"There used to be a simple \"ministreaming\" library,\n"
+"but now ministreaming.jar contains only the interfaces for the full "
+"streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:277
+msgid "Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:278
+msgid "Recommended for UDP-like applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:279
+#, python-format
+msgid ""
+"The Datagram library allows sending UDP-"
+"like packets.\n"
+"It's possible to use:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:284
+msgid "Repliable datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:285
+msgid "Raw datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:289
+msgid "Not recommended"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:290
+#, python-format
+msgid ""
+"I2CP itself is a language independent protocol, "
+"but to implement an I2CP library \n"
+"in something other than Java there is a significant amount of code to be "
+"written (encryption routines, \n"
+"object marshalling, asynchronous message handling, etc).  While someone "
+"could write an I2CP library in \n"
+"C or something else, it would most likely be more useful to use the C SAM"
+" library instead."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:297
+msgid "Web Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:298
+msgid ""
+"I2P comes with the Jetty webserver, and configuring to use the Apache "
+"server instead is straightforward.\n"
+"Any standard web app technology should work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:304
+msgid ""
+"Developing using I2P requires a working I2P installation and a "
+"development environment of your own choice.\n"
+"If you are using Java, you can start development with the streaming library or datagram library.\n"
+"Using another programming language, SAM or BOB can be used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:310
+msgid "Developing with the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:312
+msgid ""
+"The following example shows how to create TCP-like client and server "
+"applications\n"
+"using the streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:317
+msgid "This will require the following libraries in your classpath:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:321
+msgid "The streaming library itself"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:322
+msgid "Factory and interfaces for the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:323
+msgid "Standard I2P classes, data structures, API, and utilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:326
+msgid ""
+"Network communication requires the usage of I2P network sockets.\n"
+"To demonstrate this, we will create an application where a client can "
+"send text messages to a server,\n"
+"who will print the messages and send them back to the client. In other "
+"words, the server will function as an echo."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:331
+msgid ""
+"We will start by initializing the server application. This requires "
+"getting an I2PSocketManager\n"
+"and creating an I2PServerSocket.\n"
+"We will not provide the I2PSocketManagerFactory with the saved keys for "
+"an existing Destination,\n"
+"so it will create a new Destination for us.\n"
+"So we will ask the I2PSocketManager for an I2PSession, so we can find out"
+" the Destination that\n"
+"was created, as we will need to copy and paste that information later so "
+"the client can connect to us."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:362
+msgid "Code example 1: initializing the server application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:364
+msgid ""
+"Once we have an I2PServerSocket, we can create I2PSocket instances to "
+"accept connections from clients.\n"
+"In this example, we will create a single I2PSocket instance, that can "
+"only handle one client at a time.\n"
+"A real server would have to be able to handle multiple clients.\n"
+"To do this, multiple I2PSocket instances would have to be created, each "
+"in separate threads.\n"
+"Once we have created the I2PSocket instance, we read data, print it and "
+"send it back to the client.\n"
+"The bold code is the new code we add."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:448
+msgid "Code example 2: accepting connections from clients and handling messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:452
+msgid ""
+"When you run the above server code, it should print something like this "
+"(but without the line endings, it should just be\n"
+"one huge block of characters):"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:466
+msgid ""
+"This is the base64-representation of the server Destination. The client "
+"will need this string to reach the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:470
+msgid ""
+"Now, we will create the client application. Again, a number of steps are "
+"required for initialization.\n"
+"Again, we will need to start by getting an I2PSocketManager.\n"
+"We won't use an I2PSession and an I2PServerSocket this time.\n"
+"Instead, we will use the server Destination string to start our "
+"connection.\n"
+"We will ask the user for the Destination string, and create an I2PSocket "
+"using this string.\n"
+"Once we have an I2PSocket, we can start sending and receiving data to and"
+" from the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:554
+msgid ""
+"Code example 3: starting the client and connecting it to the server "
+"application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:556
+msgid ""
+"Finally, you can run both the server and the client application.\n"
+"First, start the server application. It will print a Destination string "
+"(like shown above).\n"
+"Next, start the client application. When it requests a Destination "
+"string, you can enter the string printed by the server.\n"
+"The client will then send 'Hello I2P!' (along with a newline) to the "
+"server, who will print the message and send it back to the client."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:562
+msgid "Congratulations, you have successfully communicated over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:566
+msgid "Existing Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:567
+msgid "Contact us if you would like to contribute."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:588
+msgid "Application Ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:590
+msgid "NNTP server - there have been some in the past, none at the moment"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:593
+msgid ""
+"Jabber server - there have been some in the past, and there is one at the"
+" moment, with access to the public internet"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:596
+msgid "PGP Key server and/or proxy"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:599
+msgid ""
+"Content Distribution / DHT applications - resurrect feedspace,\n"
+"port dijjer, look for alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:603
+msgid "Help out with Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:606
+msgid ""
+"Web-based applications - The sky is the limit for hosting web-server-"
+"based\n"
+"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n"
+"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:611
+msgid ""
+"Resurrect some old apps, several previously in the i2p source package -\n"
+"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2
+msgid "I2P Developer's MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4
+msgid "MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5
+msgid ""
+"Monotone servers used by the I2P project require two types of keys to be "
+"used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
+msgid ""
+"Commit Keys to sign changes checked-in to the "
+"respository; and"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10
+msgid ""
+"Transport Keys to push changes to remote "
+"servers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13
+#, python-format
+msgid ""
+"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
+"import the\n"
+"developer commit keys, but only Monotone \n"
+"server operators will need to import the transport keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20
+msgid "Developer Commit keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:255
+msgid "Developer Transport Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:256
+#, python-format
+msgid ""
+"Note: Transport keys are only needed for setting up a\n"
+"Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
+msgid "License Agreements"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
+#, python-format
+msgid "For more information see the licenses page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8
+msgid ""
+"Following is a monotonerc file defining the current trust list.\n"
+"Developers must use this file in ~/.monotone/monotonerc or\n"
+"_MTN/montonerc in their i2p.i2p workspace."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17
+msgid "Agreements"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:2
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115
+msgid "Licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:4
+msgid "I2P Software Licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:5
+#, python-format
+msgid ""
+"As required by our\n"
+"threat model (among other reasons), the \n"
+"software developed to support the anonymous communication \n"
+"network we call I2P must be freely available, open source, \n"
+"and user modifiable.  To meet these criteria, we make use of\n"
+"a variety of legal and software engineering techniques so\n"
+"as to remove as many barriers to entry for those considering\n"
+"making use of or contributing to the I2P effort."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:16
+msgid ""
+"While the information below may be more confusing than just simply \n"
+"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
+"the short answer to the question \"How is I2P licensed?\" is this:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:22
+msgid "All software bundled in the I2P distributions will allow:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:24
+msgid "use without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:25
+msgid ""
+"use with no restrictions on how, when, where, why, or by whom is running "
+"it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:26
+msgid "access to the source code without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:27
+msgid "modifications to the source"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:30
+msgid ""
+"Most of the software guarantees much more - the ability of anyone "
+"to \n"
+"distribute the modified source however they choose.  However, not all of "
+"the \n"
+"software bundled provides this freedom - the GPL restricts the ability of"
+" \n"
+"developers who wish to integrate I2P with their own applications that are"
+" not \n"
+"themselves open source applications.  While we applaud the noble goals of"
+" \n"
+"increasing the resources in the commons, I2P is best served by removing "
+"any\n"
+"barriers that stand in the way of its adoption - if a developer "
+"considering whether\n"
+"they can integrate I2P with their application has to stop and check with "
+"their lawyer,\n"
+"or conduct a code audit to make sure their own source can be released as "
+"GPL-compatible,\n"
+"we lose out."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:43
+msgid "Component licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:44
+msgid ""
+"The I2P distribution contains several resources, reflecting the "
+"partitioning of \n"
+"the source code into components.  Each component has its own license, "
+"which all \n"
+"developers who contribute to it agree to - either by explicitly declaring"
+" the release\n"
+"of code committed under a license compatible with that component, or by "
+"implicitly\n"
+"releasing the code committed under the component's primary license.  Each"
+" of these \n"
+"components has a lead developer who has the final say as to what license "
+"is compatible\n"
+"with the component's primary license, and the I2P project manager has the"
+" final say as\n"
+"to what licenses meet the above four guarantees for inclusion in the I2P "
+"distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:57
+msgid "Component"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:58
+msgid "Source path"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:59
+msgid "Resource"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:60
+msgid "Primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:61
+msgid "Alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:62
+msgid "Lead developer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:271
+msgid "GPL + java exception"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:272
+#, python-format
+msgid ""
+"While it may be redundant, just for clarity the\n"
+"GPL'ed code included within\n"
+"I2PTunnel and other apps must be released under the GPL with an "
+"additional \"exception\"\n"
+"explicitly authorizing the use of Java's standard libraries:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:288
+msgid ""
+"All source code under each component will by default be licensed under "
+"the\n"
+"primary license, unless marked otherwise in the code.  All of the above "
+"is\n"
+"summary of the license terms - please see the specific license for the "
+"component\n"
+"or source code in question for authoritative terms.  Component source "
+"locations and\n"
+"resource packaging may be changed if the repository is reorganized."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:296
+msgid "Commit privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:297
+#, python-format
+msgid ""
+"Developers may push changes to a distributed monotone repository if you\n"
+"receive permission from the person running that repository.\n"
+"See the Monotone Page for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:303
+msgid ""
+"However, to have changes included in a release, developers\n"
+"must be trusted by the release manager (currently zzz).\n"
+"In addition, they must explicitly agree with the above terms to be "
+"trusted.\n"
+"That means that they must send one of the release managers a signed "
+"message affirming that:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:310
+msgid ""
+"Unless marked otherwise, all code I commit is implicitly licensed under\n"
+"the component's primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:314
+msgid ""
+"If specified in the source, the code may be explicitly licensed under one"
+"\n"
+"of the component's alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:318
+msgid ""
+"I have the right to release the code I commit under the terms I\n"
+"am committing it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:324
+#, python-format
+msgid ""
+"If anyone is aware of any instances where the above conditions are not "
+"met,\n"
+"please contact the component lead and/or an I2P release manager with "
+"further\n"
+"information.\n"
+"See developers' license agreements."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
+msgid "Release Signing Key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
+msgid "Releases 0.7.6 and later are signed by zzz. His public key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40
+msgid ""
+"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public "
+"key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2
+msgid "Signed Developer Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4
+msgid ""
+"Keys for zzz, Complication and welterde are provided clearsigned. The key"
+" for jrandom must be\n"
+"verified differently, since he's away, and only left a binary detached\n"
+"signature for his key."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16
+msgid "Monotone keys for zzz"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47
+msgid "Monotone keys for welterde"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79
+msgid "Monotone keys for Complication"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114
+msgid "Monotone keys for jrandom"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
+msgid "Others"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
+msgid ""
+"Tip: To find zzz's GPG key, on his eepsite locate the key "
+"`0xA76E0BED`, with\n"
+"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 "
+"B310 4155\n"
+"76BA A76E 0BED`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49
+msgid ""
+"Tip: To find welterde's GPG key, on public keyservers locate the "
+"key\n"
+"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720"
+" FD81\n"
+"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81
+msgid ""
+"Tip: To find Complication's GPG key, on his eepsite locate the key"
+"\n"
+"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint "
+"`73CF\n"
+"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116
+msgid ""
+"Tip: To find jrandom's GPG key for Syndie releases, on public "
+"keyservers locate\n"
+"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n"
+"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122
+msgid ""
+"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n"
+"deployed in the Syndie Monotone repository, in a file named `mtn-"
+"committers`.\n"
+"That file also had a GPG signature, `mtn-committers.sig`, but it was a "
+"binary\n"
+"detached signature. I am going to supply both files in GPG ASCII-armoured"
+" form\n"
+"below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130
+msgid ""
+"First, the file `mtn-committers` containing jrandom's Monotone key. Save "
+"as\n"
+"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers "
+"--dearmor\n"
+"mtn-committers.asc`:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151
+msgid ""
+"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n"
+"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-"
+"committers.sig\n"
+"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n"
+"`mtn-committers` file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170
+#, python-format
+msgid ""
+"Some of the developers have included their Monotone keys in their signed license agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2
+msgid "Developer Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4
+#, python-format
+msgid "Read the new developers guide first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8
+msgid "Basic Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10
+msgid ""
+"Most of the following should be common sense for anybody who has worked "
+"on open source or in a commercial\n"
+"programming envrionment.\n"
+"The following applies mostly to the main development branch i2p.i2p.\n"
+"Guidelines for other branches, plugins, and external apps may be "
+"substantially different;\n"
+"check with the appropriate developer for guidance."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18
+msgid "Community"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20
+msgid ""
+"Please don't just \"write code\". If you can, participate in other "
+"development activities, including:\n"
+"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
+"testing;\n"
+"bug reporting and responses; documentation; code reviews; etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25
+msgid ""
+"Active devs should be available periodically on IRC #i2p-dev.\n"
+"Be aware of the current release cycle.\n"
+"Adhere to release milestones such as feature freeze, tag freeze, and\n"
+"the checkin deadline for a release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35
+msgid ""
+"Have a basic understanding of distributed source control systems, even if"
+" you haven't\n"
+"used monotone before. Ask for help if you need it.\n"
+"Once pushed, checkins are forever, there is no undo. Please be careful.\n"
+"If you have not used monotone before, start with baby steps.\n"
+"Check in some small changes and see how it goes."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42
+msgid ""
+"Test your changes before checking them in.\n"
+"If you prefer the checkin-before-test development model,\n"
+"use your own development branch (e.g. i2p.i2p.yourname.test)\n"
+"and propagate back to i2p.i2p once it is working well.\n"
+"Do not break the build. Do not cause regressions.\n"
+"In case you do (it happens), please do not vanish for a long period after"
+"\n"
+"you push your change."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51
+msgid ""
+"If your change is non-trivial, or you want people to test it and need "
+"good test reports\n"
+"to know whether your change was tested or not, add a checkin comment to "
+"history.txt\n"
+"and increment the build revision in RouterVersion.java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56
+msgid ""
+"Ensure that you have the latest monotonerc file in _MTN.\n"
+"Do not check in on top of untrusted revisions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60
+msgid ""
+"Ensure that you pull the latest revision before you check in.\n"
+"If you inadvertently diverge, merge and push as soon as possible.\n"
+"Don't routinely make others merge for you.\n"
+"Yes, we know that monotone says you should push and then merge,\n"
+"but in our experience, in-workspace merge works just as well as in-"
+"database merge,\n"
+"without creating a merge revision."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
+msgid ""
+"Do not check in major changes into the main i2p.i2p branch late in the "
+"release cycle.\n"
+"If a project will take you more than a couple days, create your own "
+"branch in monotone\n"
+"and do the development there so you do not block releases."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75
+msgid "Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77
+msgid ""
+"Coding style throughout most of the code is 4-spaces for indentation. Do "
+"not use tabs.\n"
+"Do not reformat code. If your IDE or editor wants to reformat everything,"
+" get control of it.\n"
+"Yes, we know 4 spaces is a pain, but perhaps you can configure your "
+"editor appropriately.\n"
+"In some places, the coding style is different.\n"
+"Use common sense. Emulate the style in the file you are modifying."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84
+msgid ""
+"New classes and methods require at least brief javadocs. Add @since "
+"release-number."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87
+msgid ""
+"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our "
+"official API.\n"
+"There are several out-of-tree plugins and other applications that rely on"
+" this API.\n"
+"Be careful not to make any changes that break compatibility.\n"
+"Don't add methods to the API unless they are of general utility.\n"
+"Javadocs for API methods should be clear and complete.\n"
+"If you add or change the API, also update the documentation on the "
+"website (i2p.www branch)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95
+msgid ""
+"Tag strings for translation where appropriate.\n"
+"Don't change existing tagged strings unless really necessary, as it will "
+"break existing translations.\n"
+"Do not add or change tagged strings after the \"tag freeze\" in the "
+"release cycle so that\n"
+"translators have a chance to update before the release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101
+msgid ""
+"Use generics and concurrent classes where possible. I2P is a highly "
+"multi-threaded application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104
+msgid ""
+"We require Java 6 to build but only Java 5 to run I2P.\n"
+"Do not use Java 6 classes or methods without handling the class not found"
+" exceptions\n"
+"and providing alternate Java 5 code. See classes in net.i2p.util for "
+"examples."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109
+msgid ""
+"Explicitly convert between primitive types and classes;\n"
+"don't rely on autoboxing/unboxing."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117
+msgid ""
+"Only check in code that you wrote yourself.\n"
+"Before checking in any code or library jars from other sources,\n"
+"justify why it is necessary,\n"
+"verify the license is compatible,\n"
+"and obtain approval from the lead developer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124
+msgid ""
+"For any images checked in from external sources,\n"
+"it is your responsibility to first verify the license is compatible.\n"
+"Include the license and source information in the checkin comment."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131
+msgid "Bugs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
+#, python-format
+msgid ""
+"Managing Trac tickets is everybody's job, please help.\n"
+"Monitor %(trac)s for tickets you have been assigned or can help with.\n"
+"Assign, categorize, comment on, fix, or close tickets if you can."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138
+msgid ""
+"Close a ticket when you think you've fixed it.\n"
+"We don't have a test department to verify and close tickets.\n"
+"If you arent sure you fixed it, close it and add a note saying\n"
+"\"I think I fixed it, please test and reopen if it's still broken\".\n"
+"Add a comment with the dev build number or revision and set\n"
+"the milestone to the next release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:2
+msgid "Using an IDE with I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:4
+msgid ""
+"The main I2P development branch (i2p.i2p) has been set up to"
+" enable developers to easily set up two of the commonly-used IDEs for "
+"Java development: Eclipse and NetBeans."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:10
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain .project and .classpath Eclipse files, to enable the branch "
+"to be easily set up in Eclipse."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:16
+msgid ""
+"Check out the I2P branch into some directory (e.g. "
+"$HOME/dev/i2p.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:20
+msgid ""
+"Open Eclipse and create a new Workspace, based in the directory that the "
+"I2P branch was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:24
+msgid ""
+"Select \"File - Import...\" and then under \"General\" select \"Existing "
+"Projects into Workspace\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:28
+msgid ""
+"For \"Select root directory:\" choose the directory that the I2P branch "
+"was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:32
+msgid "If necessary, click \"Refresh\" to refresh the list of projects."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:36
+msgid "Select every project in the list, and click \"Finish\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:40
+msgid ""
+"Done! Your workspace should now contain all projects within the I2P "
+"branch, and their build dependencies should be correctly set up."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:48
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain NetBeans project files."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:2
+msgid "Monotone"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:4
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:9
+msgid "Operating a Monotone client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:11
+#: i2p2www/pages/site/get-involved/guides/monotone.html:63
+msgid "Generating Monotone keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:12
+msgid "Trust and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:13
+#: i2p2www/pages/site/get-involved/guides/monotone.html:196
+msgid "Obtaining and deploying developers' keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:14
+#: i2p2www/pages/site/get-involved/guides/monotone.html:227
+msgid "Setting up trust evaluation hooks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:15
+#: i2p2www/pages/site/get-involved/guides/monotone.html:268
+msgid ""
+"Pulling the i2p.i2p, i2p.www and "
+"i2p.syndie branches"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:16
+#: i2p2www/pages/site/get-involved/guides/monotone.html:308
+msgid "Verifying that trust evaluation works"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:17
+#: i2p2www/pages/site/get-involved/guides/monotone.html:357
+msgid "Checking out a working copy of the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:18
+#: i2p2www/pages/site/get-involved/guides/monotone.html:384
+msgid "Updating your working copy to the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:22
+#: i2p2www/pages/site/get-involved/guides/monotone.html:414
+msgid "Operating a Monotone Server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:24
+msgid "Obtaining and deploying developers’ transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:25
+#: i2p2www/pages/site/get-involved/guides/monotone.html:424
+msgid "Granting push and pull access"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:26
+#: i2p2www/pages/site/get-involved/guides/monotone.html:469
+msgid "Running Monotone in server mode"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:27
+#: i2p2www/pages/site/get-involved/guides/monotone.html:494
+msgid "Differences under Debian GNU/Linux"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:34
+#, python-format
+msgid ""
+"This is a revised version of Complication's original\n"
+"  guide detailing the use of Monotone in I2P development.\n"
+"  For basic instructions see the quick-start "
+"guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:42
+#, python-format
+msgid ""
+"I2P has a distributed development model. The source code is replicated "
+"across\n"
+"  independently administered Monotone (\"MTN\") repositories.\n"
+"  Developers with commit rights are able to push their changes to the "
+"repository\n"
+"  (a license agreement needs to be "
+"signed\n"
+"  before commit rights are granted)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:52
+msgid ""
+"Some of Monotone's noteworthy qualities are: distributed\n"
+"  version control, cryptographic authentication, access control, its "
+"small size, having few\n"
+"  dependencies, storage of projects in a compressed SQLite database file,"
+" and\n"
+"  having the ability to resume interrupted synchronization attempts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:61
+msgid "Operating a Monotone Client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:66
+msgid ""
+"A transport key grants you the ability to push your changes to a Monotone"
+" repository server.\n"
+"  In order to commit code into Monotone (in essence signing your code), a"
+" commit key is also needed.\n"
+"  None of the public Monotone servers on I2P currently require a key in "
+"order to read (or pull) the source code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:74
+msgid ""
+"Without a transport key, one cannot:\n"
+"  
              \n"
+"    
            • pull code from a server which doesn't allow global read "
+"access
              • \n"
+"    
            • push code to any server
              • \n"
+"    
            • run a Monotone server
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:85
+msgid ""
+"Without a commit key, one cannot:\n"
+"  
              \n"
+"    
            • commit any code
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:94
+msgid ""
+"If you only intend to retrieve code from MTN, feel free to skip to the\n"
+"  next section. "
+"If you want\n"
+"  to generate keys, read the following."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:102
+msgid ""
+"By convention keys are named like an e-mail addresses, but a "
+"corresponding e-mail\n"
+"  address does not need to exist. For example, your keys might be named:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:113
+msgid ""
+"Monotone stores keys under $HOME/.monotone/keys in "
+"text files which\n"
+"  are named identically to the keys. For example:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:123
+msgid ""
+"To generate transport and commit keys, enter the following commands at a "
+"prompt:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:133
+msgid ""
+"Monotone will prompt you for a password to protect your keys. You are "
+"very strongly encouraged to set a password\n"
+"  for the commit key. Many users will leave an empty password for the "
+"transport key, especially those running a\n"
+"  Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:141
+msgid "Trust, and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:145
+msgid ""
+"Monotone's security model helps to ensure that nobody can easily "
+"impersonate a developer without\n"
+"  it being noticed. Since developers can make mistakes and become "
+"compromised,only manual review can\n"
+"  ensure quality of code. Monotone's trust model will ensure that you "
+"read the right diffs. It does\n"
+"  not replace reading diffs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:155
+msgid ""
+"A Monotone repository is a single file (a compressed SQLite database) "
+"which contains all of the project's source code and history."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:161
+msgid ""
+"After importing the "
+"developers' keys into Monotone and\n"
+"  setting up trust "
+"evaluation hooks,\n"
+"  Monotone will prevent untrusted code from being checked out into your "
+"workspace.\n"
+"  There are commands available to clean untrusted code from your "
+"workspace but in practice they've not been\n"
+"  needed due to the push access policies in place."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:171
+msgid ""
+"A repository can hold many branches. For example, our repository holds "
+"the\n"
+"  following main branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:176
+msgid "The I2P router and associated programs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:177
+msgid "The I2P project website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:178
+msgid "Syndie, a distributed forums tool"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:183
+msgid ""
+"By convention, the I2P Monotone repository is named i2p.mtn."
+" Before pulling\n"
+"  source code from servers, a database for your repository will need to "
+"be initialized.\n"
+"  To initialize your local repository, change into the directory that you"
+" want the\n"
+"  i2p.mtn file and branch directories to be stored and issue"
+" the following\n"
+"  command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:199
+msgid ""
+"Keys which developers use to commit code are essential for trust "
+"evaluation in\n"
+"  Monotone. The other developers' transport keys are only required for "
+"Monotone server operators.\n"
+"  "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:206
+#, python-format
+msgid ""
+"Developers' commit keys are provided GPG-signed on another page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:212
+#, python-format
+msgid ""
+"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
+"  file. Create this file (e.g. keys.txt) in the same "
+"directory where i2p.mtn is located. Import the keys with the"
+" command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:222
+msgid ""
+"Note: Never add keys to "
+"$HOME/.monotone/keys manually."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:230
+msgid ""
+"The default Monotone trust policy is way too lax for our requirements: "
+"every committer is trusted by default.\n"
+"  That is not acceptable for I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:237
+msgid ""
+"Change into the directory $HOME/.monotone and open "
+"the file\n"
+"  monotonerc with a text editor. Copy and paste the "
+"following two functions into this file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:246
+msgid ""
+"The first function determines an intersection between two sets, in our "
+"case a\n"
+"  revision's signers and trusted signers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:253
+msgid ""
+"The second function determines trust in a given revision, by calling the "
+"first\n"
+"  function with \"signers\" and \"trusted\" as arguments. If the "
+"intersection is\n"
+"  null, the revision is not trusted. If the intersection is not empty, "
+"the\n"
+"  revision is trusted. Otherwise, the revision is not trusted."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:262
+msgid ""
+"More information about Trust Evauluation Hooks can be found in the official Monotone "
+"documentation."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:271
+msgid ""
+"Enter the directory where you initialized i2p.mtn. Depending "
+"on whether you\n"
+"  want only I2P sources, or also sources for the I2P website and Syndie, "
+"you can\n"
+"  perform the pull operation in different ways."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:279
+msgid "If you only want I2P sources:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:288
+msgid "If you want all branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:294
+msgid ""
+"If the transfer aborts before completing sucessfully, simply repeating "
+"the pull command will resume the transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:300
+msgid ""
+"Pulling in the above examples is done anonymously by specifying an empty "
+"transport key.\n"
+"  If everyone pulls anonymously it will be harder for an attacker who "
+"gains control of the server\n"
+"  to selectively provide some people with tampered data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:311
+msgid "To verify that trust evaluation works:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:315
+msgid "Make a backup of your monotonerc file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:316
+msgid ""
+"Modify monotonerc by setting the trusted_signers "
+"variable in the following way:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:322
+msgid ""
+"With monotonerc configured as above, Monotone will no"
+" longer trust any committers. Confirm this by changing into the\n"
+"directory where i2p.mtn was created and attempt a checkout "
+"of the I2P branch:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:332
+msgid ""
+"A directory named i2p.i2p should not appear. You "
+"should encounter many\n"
+"  error messages like:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:349
+msgid ""
+"If you are satisfied with results, restore the backup of\n"
+"  monotonerc that was created above. If you didn't create a "
+"backup\n"
+"  as advised, re-read Setting up trust evaluation hooks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:360
+msgid ""
+"If you already have a branch checked out, skip to the next\n"
+"  section."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:367
+msgid ""
+"Change into the directory where i2p.mtn is located. Over "
+"there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:376
+msgid ""
+"The checkout should complete without error messages and a directory named"
+"\n"
+"  i2p.i2p should appear in the current directory. "
+"Congratulations! You have\n"
+"  successfully checked out the latest I2P sources, ready to be compiled."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:387
+msgid ""
+"If you haven't done this already, pull fresh code from the server to your"
+" local\n"
+"  Monotone repository. To accomplish this, change into the directory "
+"where\n"
+"  i2p.mtn is located and issue:\n"
+"  
              \n"
+"    
            • $ mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
+"i2p.i2p
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:398
+msgid "Now change into your i2p.i2p directory, and over there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:407
+msgid ""
+"As long as there were no errors…Congratulations! You have "
+"successfully updated to the latest I2P sources. They\n"
+"  should be ready to compile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:416
+msgid "Obtaining and deploying developers' transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:419
+msgid ""
+"As a server operator you may want to grant push access to certain "
+"developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:427
+msgid "By default the Monotone server denies all access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:433
+msgid "To grant pull access to all clients, set the following in"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:445
+msgid ""
+"No one will not be able to push code to your server without permission "
+"being explicitly granted. To grant push access:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:451
+msgid ""
+"Add the name of the user's transport key to\n"
+"$HOME/.monotone/write-permissions, such as\n"
+"
            \n"
+"    zzz-transport@mail.i2p\n"
+"    complication-transport@mail.i2p\n"
+"
            \n"
+"with one key per line."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:462
+msgid ""
+"Import the transport key(s) into your database. The procedure for "
+"importing transport keys is the same as for\n"
+"importing commit keys, which is described in the section Obtaining and deploying "
+"developers' keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:472
+msgid ""
+"A separate database should be used for your Monotone server because "
+"monotone will lock the database while it is served to others.\n"
+"  Make a copy of your development database, then start the server with:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:479
+msgid ""
+"If your key is protected with a passphrase, Monotone may request the "
+"passphrase\n"
+"  when the first client connects. You can work around this by connecting "
+"making the first client connection to your server\n"
+"  (or by clearing the password for your transport key)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:487
+msgid ""
+"For your server to be accessible for others over I2P, you will need to "
+"create a\n"
+"  server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" "
+"profile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:497
+msgid ""
+"Debian (amongst other distributions) has integrated Monotone into their\n"
+"  framework of daemons/services. Although Monotone servers can still be "
+"run\n"
+"  \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may"
+" be more straightforward."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:505
+msgid ""
+"Permissions are granted by editing the files\n"
+"  /etc/monotone/read-permissions and\n"
+"  /etc/monotone/write-permissions. You'll also need to edit\n"
+"  /etc/default/monotone to enable monotone to start at boot "
+"or to\n"
+"  customize the host, port, or database location."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
+msgid "New Developer's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
+msgid ""
+"\n"
+"So you want to start work on I2P? Great!\n"
+"Here's a quick guide to getting started\n"
+"on contributing to the website or the software, doing development or "
+"creating translations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
+#, python-format
+msgid ""
+"\n"
+"Not quite ready for coding?\n"
+"Try getting involved first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
+msgid "Basic study"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
+msgid "Getting the I2P code"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
+msgid "Building I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
+msgid "Development ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
+msgid "Making the results available"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
+msgid "Get to know us!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
+msgid "Translations"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
+msgid "Tools"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
+msgid ""
+"Basic development on the I2P router or the embedded applications uses "
+"Java as the main development language.\n"
+"If you don't have experience with Java, you can always have a look at Thinking in Java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
+#, python-format
+msgid ""
+"Study the how intro,\n"
+"the other \"how\" documents,\n"
+"the tech intro,\n"
+"and associated documents.\n"
+"These will give you a good overview of how I2P is structured and what "
+"different things it does."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
+msgid ""
+"For development on the i2p router or the embedded applications,\n"
+"get the monotone source repository installed - short instructions:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
+msgid ""
+"Install monotone.\n"
+"Monotone is a version control system.\n"
+"We use it because it allows us to keep track of who does what changes to "
+"the source code (and for a lot of complicated things, but 'keeping track "
+"of changes' is the basic idea)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
+msgid ""
+"Skim over the monotone tutorial,"
+" to make sure you understand the concepts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
+msgid ""
+"If you want to remain anonymous, you need to do an additional step, to "
+"set up a connection to a monotone server over I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
+#, python-format
+msgid ""
+"Enable the i2ptunnel client tunnel on port "
+"8998 pointing to mtn.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
+msgid ""
+"Pick a directory where you want to put all your I2P files, and create a "
+"monotone database:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
+msgid ""
+"Define the trust list by creating ~/.monotone/monotonerc (or"
+" _MTN/monotonerc in the i2p.i2p workspace) with the "
+"following contents:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
+#, python-format
+msgid ""
+"Copy and paste the developer's commit keys "
+"into a new file (e.g. keys.txt) in the same directory\n"
+"  that i2p.mtn is in. Import the keys into your database "
+"with 
                  mtn -d i2p.mtn read < keys.txt
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:76
+msgid ""
+"Pull the I2P sources to your machine. This may take a long time, "
+"especially if you are doing this over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:78
+msgid "Anonymously:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:81
+msgid "Non-anonymously:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:83
+msgid ""
+"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn"
+".i2p-projekt.de."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:90
+msgid ""
+"All the sources are now present on your machine, in the database file. To"
+" make them available in a directory, you need to check them out:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:92
+msgid ""
+"The above command creates a directory i2p.i2p, which contains all of the "
+"I2P sources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:96
+msgid "Remarks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:97
+msgid ""
+"\n"
+"To download the website files instead of the I2P source files, use "
+"'i2p.www' instead of 'i2p.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:100
+msgid ""
+"The initial pull may take several hours using the tunnel.\n"
+"If it fails after a partial pull, simply rerun it, it will start where it"
+" left off.\n"
+"If you are in a hurry, use the non-anonymous access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:105
+#, python-format
+msgid ""
+"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
+#, python-format
+msgid ""
+"A long explanation about using monotone is available on the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
+#, python-format
+msgid ""
+"To compile the code, you need the Sun Java Development Kit 6 or higher, "
+"or equivalent JDK\n"
+"(Sun JDK 6 strongly recommended) and\n"
+"Apache ant\n"
+"version 1.7.0 or higher.\n"
+"If you go are working on the main I2P code, you can go into the i2p.i2p "
+"directory and run 'ant' to see the build options."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
+msgid ""
+"To build or work on console translations, you need\n"
+"the xgettext, msgfmt, and msgmerge tools from the\n"
+"GNU gettext package."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
+#, python-format
+msgid ""
+"For development on new applications,\n"
+"see the application development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
+#, python-format
+msgid ""
+"See zzz's TODO lists,\n"
+"this website's TODO list or\n"
+"Trac\n"
+"for ideas."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
+#, python-format
+msgid ""
+"See the bottom of the licenses page "
+"for\n"
+"commit privilege requirements. You need these to put code into i2p.i2p "
+"(not required for the website!)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
+msgid "Short version of how to generate and use keys if you plan to commit:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
+msgid "use an empty passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
+msgid "enter a passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
+#, python-format
+msgid ""
+"send this to a mtn repo operator to get "
+"push privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
+#, python-format
+msgid ""
+"send this to a release manager to get "
+"commit privileges - not required for website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
+msgid "check in with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
+msgid "push with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
+#, python-format
+msgid "Long version: see the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
+#, python-format
+msgid ""
+"The developers hang around on IRC. They can be reached on the Freenode "
+"network, OFTC, and on the I2P internal networks. The usual place to look "
+"is #i2p-dev. Join the channel and say hi!\n"
+"We also have additional guidelines for regular"
+" developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
+#, python-format
+msgid ""
+"Website and router console translators: See the New Translator's Guide\n"
+"for next steps."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
+msgid ""
+"I2P is open source software that is mostly developed using open sourced\n"
+"toolkits. The I2P project recently acquired a license for the YourKit "
+"Java\n"
+"Profiler. Open source projects are eligible to receive a free license "
+"provided\n"
+"that YourKit is referenced on the project web site. Please get in touch "
+"if you\n"
+"are interested in profiling the I2P codebase."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
+#, python-format
+msgid ""
+"YourKit is kindly supporting open source projects with its full-featured "
+"Java Profiler.\n"
+"YourKit, LLC is the creator of innovative and intelligent tools for "
+"profiling\n"
+"Java and .NET applications. Take a look at YourKit's leading software "
+"products:\n"
+"YourKit Java Profiler and\n"
+"YourKit .NET Profiler."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
+msgid "New Translator's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
+msgid "Here's a very quick guide to getting started."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
+msgid "How to Translate the Website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
+#, python-format
+msgid ""
+"Translation of the website is done with .po files. The easiest way by far"
+" to\n"
+"translate the website is to sign up for an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
+msgid "Preparation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
+#, python-format
+msgid ""
+"Come to #i2p-dev on irc and talk to people.\n"
+"Claim the language -\n"
+"To make sure other coworkers don't bump onto the files you are working "
+"on,\n"
+"please update the translation status on this wiki "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"Including the installation of monotone,\n"
+"checking out i2p.www branch, and generate your own monotone keys.\n"
+"It is not required that you sign a dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
+msgid ""
+"Run \"./extract-messages.sh\" to generate a "
+"messages.pot in the base directory.\n"
+"Edit the header of this file, then run \"./init-new-po.sh "
+"locale\" to generate the file\n"
+"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
+"\"mtn add\" this file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
+msgid ""
+"Edit i2p2www/pages/global/lang.html and add a line for your "
+"language (copy an existing line)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
+msgid ""
+"Add a flag image file to i2p2www/static/images/flags/ for "
+"the menu (copy from the router)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
+msgid ""
+"Edit files:\n"
+"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
+msgid ""
+"Check in:\n"
+"\"mtn pull\", \"mtn update\". Then check in by "
+"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
+"This collects the diff info of your changed file into your local repo. "
+"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
+"i2p.i2p\".\n"
+"This synchronizes your local repo with the repo on the target machine."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
+msgid "Repeat. Check in often. Don't wait until it is perfect."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
+msgid "How to Translate the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
+#, python-format
+msgid ""
+"The easiest way by far to translate the router console is to sign up for "
+"an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"including the installation of monotone and the gettext tools,\n"
+"checking out i2p.i2p branch, and generate your own monotone keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
+msgid "Generate your own gpg key and sign the dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
+msgid ""
+"Before starting a console translation, better help translate some i2p "
+"webpages first.\n"
+"At least an i2p homepage in your language would be great."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
+msgid ""
+"What to translate:\n"
+"There are about 15 files in the i2p.i2p branch that needs translation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
+msgid ""
+"Where xx is your language code like fr/de/ch/zh/...\n"
+"There may be or may not be files with your lang code. If not, you can "
+"create your own. by copying and renaming other language files you know "
+"with your own lang code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet, copy another language "
+"file to a new file foo_xx.bar for your language.\n"
+"Then \"mtn add\" the file.\n"
+"After creating a .po file, edit the headers. Then run \"ant "
+"distclean poupdate\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
+msgid ""
+"Start to work:\n"
+"Edit the HTML files with any text editor.\n"
+"Be sure not to use an editor in HTML mode that reformats everything.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
+msgid ""
+"As you can see, it's not that difficult.\n"
+"If you have questions about the meaning of the terms in the console, ask "
+"in #i2p-dev on IRC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
+msgid "FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
+msgid ""
+"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
+"and html, etc.? Why can't I just do a translation and email it to you?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
+msgid "A: Several reasons:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
+#, python-format
+msgid ""
+"You might be interested in translating via Transifex. Request to join a "
+"translation team here."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
+msgid ""
+"We don't have anybody who has time to accept manual contributions and "
+"submit them to our source control system on your behalf. Even if we did, "
+"it doesn't scale."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
+msgid ""
+"Maybe you are thinking translation is a one-step process. It isn't. You "
+"can't do it all at once. You will make mistakes. You need to test it and "
+"tweak it to make it look right before you submit it. Developers "
+"will update or add to the English text, thus requiring a translation "
+"update."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
+msgid ""
+"Having translators use a source control system directly provides "
+"authentication and accountablility - we know who is doing what, and we "
+"can track changes, and revert them if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
+msgid ""
+".po files are not difficult. If you don't want to work directly with "
+"them, we recommend 'poedit'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
+msgid ""
+"HTML files are not difficult. Just ignore the html stuff and translate "
+"the text."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
+msgid ""
+"Installing and using monotone is not that difficult. Several of the "
+"translators and other contributors to I2P are non-programmers, and they "
+"use monotone regularly. Monotone is simply a source control system, it is"
+" not about \"coding\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
+msgid ""
+"Our items to translate are not \"documents\". They are html files and po "
+"files, with a specific format and character encoding (UTF-8) that must be"
+" maintained, and not corrupted by email programs or other methods of "
+"transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
+msgid ""
+"We looked at 'pootle' as a front-end for translators. It didn't work "
+"well, needed an administrator, and a pootle-based process would suffer "
+"from a number of the above flaws."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
+msgid ""
+"In summary:\n"
+"Yes, we know it is somewhat of a hurdle to get started. It's really the "
+"only possible way we can do it. Give it a try, it really isn't that hard."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
+msgid "More Information"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
+#, python-format
+msgid ""
+"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
+msgstr ""
+
diff --git a/i2p2www/translations/ru/LC_MESSAGES/priority.po b/i2p2www/translations/ru/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..5dcd809d
--- /dev/null
+++ b/i2p2www/translations/ru/LC_MESSAGES/priority.po
@@ -0,0 +1,3386 @@
+# Russian (Russia) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# tengo , 2013
+# IOException , 2013
+# pahom , 2013
+# denixx , 2013
+# keedley , 2013
+# sassy , 2013
+# JD1 , 2013
+# Арефьев Денис , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-11-27 04:36+0000\n"
+"Last-Translator: IOException \n"
+"Language-Team: Russian (Russia) "
+"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 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/blog/category.html:2
+msgid "Blog Category"
+msgstr "Категория блогов"
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr "I2P Blog ATOM По категории: %(category)s"
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:92
+msgid "Blog"
+msgstr "Блог"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "I2P Блог ATOM "
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr "Опубликовано %(date)s от %(author)s"
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "Еще сообщений…"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr "Размещено:"
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "Автор:"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Пакеты I2P для Debian"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+"Пакеты для Debian\n"
+"были протестированы и должны работать на платформах x86/x86_64 "
+"использующих:"
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr "Ubuntu (Точнее 12.04 и новее)"
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr "Debian Linux (Squeeze или новее) & kFreeBSD"
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+"Пакеты I2P могут работать на системах не перечисленных выше. "
+"Пожалуйста сообщайте о любых проблемах\n"
+"с этими пакетами в Trac на\n"
+"https://trac.i2p2.de."
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Вариант 1: Недавние версии Убунту и ее  "
+"родственники (Попробуйте, если не используете Debian"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr ""
+"Вариант 2: Debian (включая основанные на нем "
+"дистрибутивы)"
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+"Шаги для  Ubuntu Precise Pangolin (и новее) и похожих, таких как Linux "
+"Mint & Trisquel"
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Добавление PPA через командную строку и установка I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Откройте терминал и введите:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"Эта команда добавит PPA в /etc/apt/sources.list.d и скачает\n"
+"ключ gpg, которым подписан репозиторий. Этот ключ удостоверяет\n"
+"что пакеты попали к вам в том же виде, как были собраны."
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "Теперь нужно уведомить пакетный менеджер о новом репозитории, введя:"
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+"Эта команда заберет списки последних версий из каждого\n"
+"репозитория, что настроен для вашей системы, включая репозиторий I2P, \n"
+"который мы добавили предыдущей командой."
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "Теперь Вы готовы к установке I2P!"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "Добавление PPA, используя Synaptic"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+"Запустите Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+"Как Synaptic откроется, выберите Repositories из меню  "
+"Settings."
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"Кликните на  закладку Other Sources  и кнопку  Add. "
+"Вставьте ppa:i2p-maintainers/i2p в  поле APT-line  и "
+"кликните Add Source. Закройте с помощью Closeи "
+"перезапустите с помощью Reload."
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+"В диалоге Быстрого фильтра, наберите i2p и нажмите Enter. "
+"Когда i2p будет выведено в результатах, сделайте правый клик"
+" на i2p и выберите Mark for Installation. После "
+"этого вы можете увидеть сообщение Mark additional required "
+"changes?. В таком случае, выберите Mark, а потом - "
+"Apply."
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+"После завершения установки вы можете приступать к следующей части  запуска I2P и его настройки для вашей "
+"системы."
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr "Инструкции для Debian"
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+"Внимание: Шаги перечисленные ниже должны выполняться с правами "
+"пользователя root (то есть, после переключения\n"
+"на пользователя root с помощью \"su\" или предвосхищая каждую команду "
+"префиксом \"sudo\")."
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr "Добавьте следующие строки в %(file)s."
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the  key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+"Скачайте ключ используемый для подписи "
+"репозитория и добавьте его в apt:"
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr "Сообщите вашему менеджеру пакетов о новом репозитории введя"
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+"Эта команда выполнит обновление списка ПО для каждого\n"
+"репозитория активированного в вашей системе, включая репозиторий I2P "
+"добавленный на шаге\n"
+"1."
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+"Теперь вы готовы установить I2P! Установка пакета i2p-"
+"keyring\n"
+"гарантирует, что вы получите обновления GPG ключей репозитория."
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+"После завершения установки вы можете приступать к следующей части  запуска I2P и его настройки для вашей "
+"системы."
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "Действия после установки"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+"Используя эти I2P пакеты, маршрутизатор может быть запущен следующими\n"
+"тремя путями:"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+""по требованию" используя скрипт i2prouter. Просто запустите "
+""i2prouter⏎\n"
+"start" из командной строки. (Важно:  НЕ "
+"НАДО использовать⏎\n"
+"sudo или запускать его от root!)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""по требованию" без java service wrapper\n"
+"(он нужен для  non-Linux/non-x86 систем), запуская \"i2prouter-"
+"nowrapper\".\n"
+"(Важно: НЕ НАДО\n"
+"использовать sudo или запускать от root!)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"как сервис, который автоматически стартует при запуске системы, даже \n"
+"до логина пользователя. Сервис может быть активирован командой \"dpkg-reconfigure\n"
+"i2p            \" от root или с помошью sudo. Этот вариан рекомендован для "
+"использования."
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+"При первой инсталляции не забудьте поправить настройки "
+"NAT/firewall\n"
+"если это возможно. Порты, которые нужно пробросить указаны на \n"
+"странице конфигурации сетив консоли маршрутизатора. Если вам нужно "
+"разобраться, что такое проброс портов,\n"
+"про это можно прочитать на portforward.com."
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"Проверьте и  поправьте настройки полосы пропускания на ⏎\n"
+"странице настроек,⏎\n"
+"так как значения по умолчанию 96 KB/s down / 40 KB/s up довольно "
+"ограничены."
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"Если вы хотите ходить браузером на сайты в I2P (eepsite), обратите "
+"внимание на инструкцию по настройке прокси "
+"для браузера "
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Скачать"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Скачать I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Зависимость"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+"\n"
+"Java Runtime 1.5 или новее.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" рекомендованы,\n"
+"исключая Raspberry Pi: Oracle 8 Early Access,"
+"\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Определите версию установленной Java здесь\n"
+"или наберите java -version в вашей командной строке.\n"
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "Новая инсталляция"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr "выберите альтернативную ссылку"
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Скачайте этот файл и запустите его."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Скачайте и кликните файл (если это применимо), или\n"
+"наберите java -jar i2pinstall_%(i2pversion)s.jar в терминале"
+" для запуска\n"
+"инсталлятора.\n"
+"На некоторых платформах это может быть как правый клик мышкой и выбрать\n"
+""Open with Java"."
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "Установка из командной строки:"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Скачайте графический инсталлятор для OCX %(i2pversion)s выше и запустите\n"
+"     java -jar i2pinstall_%(i2pversion)s.jar -console из "
+"командной строки."
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Скачайте и кликните файл (если это применимо), или\n"
+"наберите java -jar i2pinstall_%(i2pversion)s.jar в терминале"
+" для запуска\n"
+"инсталлятора.\n"
+"На некоторых платформах это может быть как правый клик мышкой и выбрать\n"
+""Open with Java"."
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Скачайте инсталлятор выше и\n"
+"запустите как java -jar i2pinstall_%(i2pversion)s.jar "
+"-console из командной строки."
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Пакеты для Debian & Ubuntu есть и доступны."
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+"    The latest dev build is version %(devbuild)s, and is available from\n"
+"    str4d's eepsite."
+msgstr ""
+"Файл выше это текущая версия.\n"
+"    Последние девелоперские сборки это версия  %(devbuild)s, и она "
+"доступна на \n"
+"    сайте str4d."
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+"      are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+"      the other."
+msgstr ""
+"Релизные и девелоперские версии I2P APK несовместимы, так как\n"
+"они подписаны zzz и str4d соответственно. Удалите тот, что стоит\n"
+"если вы переходите таким образом."
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "Пакет с исходниками"
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+"    or via Git from git.repo.i2p or Github.\n"
+"    
            \n"
+"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+"Еще можно скачать исходники из monotone\n"
+"    или Git с git.repo.i2p или Github.\n"
+"    
            \n"
+"    Запустите (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg), а потом используйте собранный "
+"графический инсталлятор или устанавливайте из коммандной строки, как "
+"выше."
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Эти файлы подписаны zzz,\n"
+"и его ключи вот тут."
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"I2P можно еще скачать с сайтов проекта на Launchpad и Google Code."
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"После успешного запуска инсталлятора на windows, просто щелкните на "
+"кнопку \"Start I2P\",\n"
+"откроется  консоль "
+"роутера,\n"
+"где будут дальнейшие инструкции."
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"На Unix системах, I2P можно запустить как сервис\n"
+"используя \"i2prouter\" скрипт, расположенный в директории, что вы "
+"указали для установки i2p.\n"
+"Перейдите в эту директорию в командной строке и выполните команду \"sh "
+"i2prouter status\",\n"
+"это даст вам текущее состояние маршрутизатора. Параметры скрипта могут "
+"бытьт \"start\", \"stop\" and \"restart\", \n"
+"для запуска, останова и перезапуска, соответственно. Консоль маршрутизкатора⏎\n"
+"доступна в обычном месте.\n"
+"Для пользователей на OpenSolaris и других системах, где враппер (i2psvc) "
+"не поддерживается,\n"
+"запускайте маршрутизатор командой \"sh runplain.sh\"."
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"Устанавливая впервые, не забудьте отредактировать настройки вашего NAT"
+" и firewall\n"
+"если возможно, учитывая те номера портов, которые I2P использует в "
+"интернет.\n"
+"Они описаны здесь, среди остальных портов.\n"
+"Если вам удалось открыть порт для входящего tcp, включите также "
+"использование входящего TCP на\n"
+"странице конфигурации"
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"Пожалуйста, проверьте и поправьте настройки полосы пропускания на⏎"
+"\n"
+"странице конфигурации,⏎\n"
+"так как настройки по умолчанию 96 KBps down / 40 KBps up это, честно "
+"говоря, меееееедленнноооо."
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "Обновления с более ранних релизов:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr "И автоматические, и ручные обновления возможны для версии."
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "Автоматические обновления"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+"Если вы используете 0.7.5 или более новую версию, ваш маршрутизатор "
+"должен определить\n"
+"выпуск нового релиза. Для обновления просто щелкните  кнопку 'Скачать "
+"обновление' на консоли маршрутизатора,\n"
+"когда она появится."
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"Из-за ошибки в версии 0.7.6, первоначально установленные на этой версии "
+"системы\n"
+"и не обновленные позже вручную\n"
+"могут получить сообщение об ошибке \"скачанная версия не новее текущей\","
+"\n"
+"и это означает, что обновляться придется вручную, описано ниже."
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Если вы используете 0.7.4 или более раннюю версию, смотрите \n"
+"the 0.7.5 release notes\n"
+"для описания порядка настройки маршрутизатора на \n"
+"автоматические обновления"
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Если вы используете 0.6.1.30 или более ранние версии, смотрите\n"
+"instructions\n"
+"для получения информации о настройке маршрутизатора на автоматическое "
+"получение обновлений."
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+"    router console "
+"allowing\n"
+"    you to download and install the new release by just clicking on that\n"
+"    link."
+msgstr ""
+"Если вы правильно сконфигурировали маршрутизатор по инструкции, вы должны увидеть ссылку на\n"
+"консоли, которая позволит"
+"\n"
+"вам скачать и установить новую версию, просто кликнув по этой\n"
+"ссылке"
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr "Ну, или попробуйте обновиться вручную по методике, описанной ниже."
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "Обновление вручную"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and rename as i2pupdate.zip.\n"
+"    (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+"    resulting i2pupdate.zip to your I2P installation directory).  You do"
+" \n"
+"    NOT need to unzip that file."
+msgstr ""
+"Скачайте этот файл в директорию установки I2P\n"
+"и переименуйте  его в  i2pupdate.zip.\n"
+"(или вы можете взять исходники, как выше, и запустить \"ant updater\", а "
+"потом скопировать\n"
+"полученный i2pupdate.zip в директорию установки I2P). Нет, \n"
+"этот файл вам НЕ НАДО разархивировать самостоятельно."
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+"Нажмите на  \"Перезапустить\""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "Сходите за чашечкой кофе, можно вернуться минут через 11"
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Эти файлы подписаны zzz,\n"
+"и его ключи вот тут."
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "Предыдущие Версии"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"Предыдущие версии I2P доступны на  Google "
+"Code⏎\n"
+"и  на  Launchpad,⏎\n"
+"а также внутри I2P на %(echelon)s."
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "Выбор зеркала для скачки"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "Файл:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "Любое зеркало"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+"Чтобы получить награду, авторуне должны платить другие организации\n"
+"или команды за эту работу (например, студентам GSoC не будет оплачено)."
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations.  Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"Размер награды может быть увеличен за счет пожертвований. Вы\n"
+"считаете это важным? Внесите свои "
+"пожертвования, ⏎\n"
+"указывая количество на  награду за %(donatename)s!"
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "не найдено"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr "Или вы не так набрали, или мы потеряли или потерли. "
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "Ошибка сервера"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "500 Server error"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "Сервер столкнулся с какой-то ошибкой."
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "Зеркала"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "Безопасно"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "Разное"
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Ссылки"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "Контакты"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "Футболки!"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "Европа"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "США"
+
+#: i2p2www/pages/global/footer.html:31 i2p2www/pages/global/nav.html:133
+msgid "Donate"
+msgstr "Пожертвования"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr "Пропустить "
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "I2P Лого"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "Проект Невидимый Интернет"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+"Эта страница была обновлена  %(lastupdated)s и содержит сведения для "
+"версии маршрутизатора  %(accuratefor)s."
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "Эта страница была обновлена  %(lastupdated)s."
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "Эта страница содержит сведения для версии %(accuratefor)s."
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr "Предыдущее"
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr "Следующее"
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr "Опубликовано в "
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "О проекте"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Введение в I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "Сравнения"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "Обзор сравнений"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Другие анонимные сети"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Документация"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Список документации"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Как работает I2P"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "Легкая вводная часть"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "Технические особенности"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "Модель угроз"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Чесночная маршрутизация"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "I2P сетевая база данных"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "Маршрутизация туннелей"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "Выбор пира"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Криптография"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+Метки сессий"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Спецификации"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "Блокфайл"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "Основные структуры"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "Конфигурационные файлы"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:56
+msgid "Datagrams"
+msgstr "Датаграммы"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr "Данные гео-привязки для IP"
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:88
+msgid "Plugins"
+msgstr "Плагины"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:55
+msgid "Streaming library"
+msgstr "Библиотека потоков"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "Создание туннелей"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "Сообщения туннелей"
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "Обновления програмного обеспечения"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API (програмный интерфейс)"
+
+#: i2p2www/pages/global/nav.html:60 i2p2www/pages/global/nav.html:113
+msgid "Applications"
+msgstr "Приложения для I2P"
+
+#: i2p2www/pages/global/nav.html:62
+msgid "Supported applications"
+msgstr "Поддерживаемые приложения"
+
+#: i2p2www/pages/global/nav.html:63
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Protocols"
+msgstr "Протоколы"
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Protocol stack"
+msgstr "Стек протоколов"
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Transports"
+msgstr "Транспортные протоколы"
+
+#: i2p2www/pages/global/nav.html:75
+msgid "Transport layer overview"
+msgstr "Обзор траспортного уровня"
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Tunnels"
+msgstr "Туннели"
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Tunnel implementation"
+msgstr "Реализация туннелей"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Unidirectional tunnels"
+msgstr "Всенаправленные туннели"
+
+#: i2p2www/pages/global/nav.html:84
+msgid "Old implementation"
+msgstr "Старая реализация"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Naming and addressbook"
+msgstr "Именование и адресная книга"
+
+#: i2p2www/pages/global/nav.html:91
+msgid "Team"
+msgstr "Команда"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Hall of Fame"
+msgstr "Зал славы"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Academic papers and peer review"
+msgstr "Научные публикации и рецензирование"
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Presentations, tutorials and articles"
+msgstr "Презентации, учебные материалы и статьи"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Contact us"
+msgstr "Контакты"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Help"
+msgstr "Справка"
+
+#: i2p2www/pages/global/nav.html:101
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "How to browse I2P"
+msgstr "Как в I2P смотреть страницы"
+
+#: i2p2www/pages/global/nav.html:103
+msgid "Glossary"
+msgstr "Список терминов"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Performance"
+msgstr "Производительность"
+
+#: i2p2www/pages/global/nav.html:105 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Форумы"
+
+#: i2p2www/pages/global/nav.html:108
+msgid "Volunteer"
+msgstr "Волонтерство"
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Get involved!"
+msgstr "Вливайтесь!"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Develop"
+msgstr "Разработка"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Licenses"
+msgstr "Лицензии"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Release signing keys"
+msgstr "Ключи для подписи релизов"
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Signed keys"
+msgstr "Подписанные ключи"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Developers keys"
+msgstr "Ключи разработчиков"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Bug tracker"
+msgstr "Заявки о проблемах"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Academic research"
+msgstr "Научные исследования"
+
+#: i2p2www/pages/global/nav.html:122
+msgid "Open research questions"
+msgstr "Вопросы открытые для исследования"
+
+#: i2p2www/pages/global/nav.html:123
+msgid "Guides"
+msgstr "Руководства"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "New developers"
+msgstr "Новые разработчики"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Using an IDE with I2P"
+msgstr "Использование IDE с I2P"
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Developer guidelines and coding style"
+msgstr "Руководства разработчика и стиль кодирования"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "New translators"
+msgstr "Новые переводчики"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Bounties"
+msgstr "Награды"
+
+#: i2p2www/pages/global/nav.html:134 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Встречи"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Roadmap"
+msgstr "Дорожная карта"
+
+#: i2p2www/pages/global/nav.html:136
+msgid "Task list"
+msgstr "Задачи"
+
+#: i2p2www/pages/global/nav.html:139
+msgid "Language"
+msgstr "Язык"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr "Фид Встречи по I2P (ATOM)"
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "Журналы прежних встреч по I2P"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr "Встречи пока откладываются, пока не найдется время"
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"Если у вас есть необходимость что-то обсудить, найдите разработчиков на "
+"IRC в канале #i2p-dev.\n"
+"Вести от разработчиков на блогах."
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr "Встреча разработчиков I2P  %(id)s"
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr "Полный журнал IRC"
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "По темам"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "По времени"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "По автору"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
            \n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
            \n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+"Отсылайте новые или измененные записи на \n"
+"%(email)s.
            \n"
+"По возможности, оформляйте их как BibTex; Вот тут наши \n"
+"BibTeX данные для примера.
            \n"
+"По возможности включайте URLs:\n"
+"оффлайн публикации сильно менее полезны."
+
+#: i2p2www/pages/papers/list.html:94
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"Free Haven's anonymity bibliography."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Контакты"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr "Email"
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like OFTC,\n"
+"  EIN and Freenode.\n"
+"  All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+"Наш основной IRC сервер это Irc2P внутри сети I2P; При инсталляции I2P до"
+" него создается выделенный туннель.\n"
+"  Мы присутствуем также на многих стандартных IRC сетях, таких как OFTC,\n"
+"  EIN и Freenode.\n"
+"  Все наши I2P разговоры и каналы в этих сетях связаны с основными "
+"каналами в IRC2P с помошью ботов-ретрансляторов."
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Список каналов:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "Общие обсуждения I2P"
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "Оффтопик"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "Общение разработчиков"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Канал помощи"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"Большинство дискуссий по развитию I2P происходят на форуме разработчиков I2P.  Это обычно "
+"наилучшее место для вопросов, если на IRC канале никого нет. "
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "Списки рассылки"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+"Существует список рассылки, но он редко используется, т.к. существующая "
+"команда разработки компактна и предпочитает общение на IRC или форуме. "
+"Возможно, это изменится в будущем."
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "Подписка"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+"Для подписки на список расслыки, перейдите на страницу списка (ниже "
+"ссылка) и заполните форму. Можно использовать внутренние I2P адреса "
+"(foobar@mail.i2p)."
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "Отписаться от списка рассылки"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+"Для того, чтобы отписаться от списка рассылки или изменить настройки, "
+"идите по ссылке (внизу) и введите свой почтовый адрес."
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Списки"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Архив"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr "Общая дискуссия по I2P - все, что не подходит под какой-то другой список."
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+"Вам не нравятся списки рассылки? Тогда это для вас. Все рассылки также "
+"доступны по NNTP."
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr "Соответстие групп и списков:"
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Сервера:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Часто задаваемые вопросы"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Список"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "Общая информация"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "На каких системах работает I2P?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+"Что такое \"eepsite\" и как я могу настроить свой браузер, чтобы до них "
+"дойти?"
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "На моем маршрутизаторе очень мало активных пиров, это нормально?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr "Что означают цифры Активные x/y в консоли маршрутизатора?"
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+"У меня числа активных пиров / известных пиров / туннелей / соединений / "
+"полосы очень сильно меняются! Что нибудь не так?"
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "Безопасно ли использовать outproxy?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr "Большая часть eepsites в I2P - лежат?"
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Какие порты использует I2P?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "Почему I2P слушает на порту 32000?"
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "Я думаю, что нашел баг, где я могу о нем сообщить?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr "Что случилось с  *.i2p.net? Что случилось с jrandom? I2P больше нет?"
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "Имею вопрос!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr "Установка"
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+"Мой маршрутизатор запущен уже несколько минут и у него нет или очень мало"
+" соединений"
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "Почему I2P такой тормозной?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+"У меня в адресной книге отсутствует большинство хостов. Подскажете "
+"хорошие ссылки для подписки?"
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "Как запустить мой собственный eepsite?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "Вопросы по плагинам Bittorrent / I2PSnark / Azureus для I2P"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "Как попасть в IRC внутри сети I2P?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "Я не могу попасть на обычные сайты Internet через I2P."
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "Я не могу попасть на https:// или ftp:// сайты через I2P."
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr "Можно использовать I2P как SOCKS proxy?"
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Как мне настроить мой браузер?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+"Как я могу настроить доступ к консоли маршрутизатора с других машин или "
+"защитить этот доступ паролем?"
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr "Как я могу использовать приложения с других моих машин?"
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr "Как вручную выполнить начальную загрузку маршрутизатора (reseed)?"
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "Мой маршрутизатор использует слишком много процессорного времени?!?"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "Недопонимание"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr ""
+"Как я могу попасть на IRC, BitTorrent или другой сервис в обычном "
+"интернете?"
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+"А мой роутер является \"выходным узлом\" (outproxy) в обычный интернет? Я"
+" не хочу этого."
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+"Я против некоторых типов контента. Как я могу избежать участия в "
+"распространении, хранении или доступе к нему?"
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Ошибки и их успешное решение"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+"Я использую FreeBSD и когда стартую I2P - получаю ошибку про "
+"libm.so.4!"
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+"Внутри wrapper.log я вижу ошибку вида Protocol family "
+"unavailable при запуске I2P"
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "ссылка"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+"В то время как известно о запуске I2P на ПК столь же слабых как Pentium "
+"II с 64 MB RAM, вы получите гораздо лучшие результаты на Pentium III (или"
+" лучше) с 128MB RAM (или больше). Таблицу сравнения"
+" производительности различных JRE можно найти на %(chart)s, но в кратце: Это возможно на чём "
+"угодно, где используется Sun/Oracle Java или OpenJDK."
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+"Работа I2P протестирована на Windows, Linux, FreeBSD (смотрите примечание"
+" ниже), OSX, и OpenSolaris. Работа над версией "
+"I2P для Android идет прямо сейчас."
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr "Есть несколько мест, выберите одно или несколько."
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "Обсудите с разработчиками на IRC в #i2p-dev"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+"Пожалуйста, включите необходимую информацию из журналов маршрутизатора и "
+"приложения-обёртки (wrapper)."
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+"Подписка по умолчанию - это http://www.i2p2.i2p/hosts.txt, которая "
+"обновляется редко.⏎\n"
+"Если других подписок нет, вам довольно часто придется пользоваться "
+"надоедливыми джамп-ссылками."
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+"Существуют другие публичные ссылки на подписки для адресной книги. Вы "
+"можете добавить одну-другую в  свой набор "
+"подписок.\n"
+"Все их добавлять не надо, так как они периодически синхронизируются. \n"
+"Ссылки, использующие cgi-bin приложения как правило более эффективны,\n"
+"т.к. обычно применяют различные стратегии для минимизации количества "
+"дубликатов предоставляемых адресов.\n"
+"Обратите внимание, что добавление списка в подписки - это акт доверия, "
+"так как вредоносная\n"
+"подписка может отдать Вам недостоверные адреса. Поэтому что стоит "
+"подумать,\n"
+"следует ли Вам доверять каждой из них.\n"
+"Операторы этих сервисов могут иметь разные политики по отношению к "
+"содержимому хостов со списками.\n"
+"Наличие в этих списках не  означает поддержку или аффилированность "
+"оператора подписки с сайтом."
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+"Jrandom был ведущим разработчиком I2P и⏎\n"
+"Syndie в течении нескольких лет.⏎\n"
+"Мы не знаем, когда и вернется ли jrandom вообще.⏎\n"
+"Домены *.i2p.net перестали функционировать после⏎\n"
+"отключения питания на хостинге."
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+"Взгляните на этой странице на прощальное "
+"сообщение от  jrandom и дополнительную информацию⏎\n"
+"о миграции *.i2p.net на этот сайт."
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr "I2P продолжает активное развитие."
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr "Есть много причин для высокой нагрузки на CPU. Вот проверочный список:"
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+"Попробуйте использоать OpenJDK или Sun/Oracle Java, если они присутствуют"
+" для Вашей системы. Вы можете проверить\n"
+"установленную версию java командой java -version в командной"
+" строке. \n"
+"Производительность java от других производителей обычно оставляет желать "
+"лучшего."
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+"Вы используете BitTorrent клиент поверх I2P? Пробуйте уменьшить "
+"количество раздач, ограничения по трафику\n"
+"или попробуйте временно выключить раздачи и закачки, чтобы выяснить, "
+"поможет ли это."
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+"В Ваших ограничениях по трафику установлены очень высокие лимиты? "
+"Возможно, что слишком много данных идет через ваш\n"
+"I2P-маршрутизатор и он перегружен. Пробуйте уменьшить настройку Доля "
+"транзитного трафика на  странице конфигурации."
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+"Убедитесь, что используете новейшую версию I2P, чтобы воспользоваться "
+"достижениями в производительности и свежими исправлениями проблем."
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+"Достаточно ли памяти было предоставлено для I2P? Взгляните на график "
+"использования памяти на странице"
+" графиков, возможно, Вы увидите,\n"
+"что использование памяти под завязку \"забивает\" процессор - виртуальная"
+" машина Java тратит большинство своего времени на\n"
+"процесс сборки мусора. Увеличьте значение настройки "
+"wrapper.java.maxmemory в файле wrapper.config."
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+"Загрузка процессора выше, чем Вам хотелось бы, или она уперлась в "
+"100% на долгое время?\n"
+"Если уперлась, это может быть баг, посмотрите в журналах сообщения об "
+"ошибках."
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+"Возможно, вы используете библиотеку для работы с большими числами, "
+"реализованную на Java, а не в виде подгружаемой нативной библиотеки,\n"
+"так бывает, например, если вы работаете на новой или необычной платформе "
+"(ОpenSolaris, mipsel и другие).\n"
+"Обратите внимание на страницу с исходными кодами "
+"библиотеки для инструкций по\n"
+"диагностике, сборке под вашу платформу и методике тестирования."
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+"Если нативная библиотека jbigi работает нормально, наибольшую нагрузку на"
+"\n"
+"процессор может давать маршрутизация трафика по транзитным туннелям. Эта "
+"работа нагружает процессор,\n"
+"так как на каждом хопе должен быть раскодирован очередной слой "
+"шифрования.\n"
+"Вы можете ограничить транзитный трафик двумя способами - уменьшив\n"
+"выделенную системе полосу обменного трафика на\n"
+"странице настроек,\n"
+"или установкой настройки router.maxParticipatingTunnels=nnn на\n"
+"странице "
+"дополнительных настроек."
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+"Гм. I2P - это анонимная сеть, так что вопрос сложный.\n"
+"I2P создан для того, чтобы выдерживать попытки цензурирования, реализуя "
+"возможность всем-всем свободно общаться.\n"
+"Наилучший способ оградить ваш компьютер от (шифрованного) трафика, "
+"который Вас не устраивает - это не использовать I2P вообще.\n"
+"Свобода слова имеет цену.\n"
+"Но давайте разделим ваш вопрос на три части:"
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+"Распространение - Весь трафик в I2P многослойно зашифрован. Вы не "
+"знаете\n"
+"содержимое, источник или адрес назначения сообщений.\n"
+"Весь трафик, который вы передаете - внутренний для I2P сети, вы НЕ "
+"являетесь выходным узлом (outproxy).\n"
+"Единственный остающийся вариант для Вас - отказаться передавать\n"
+"любой трафик, настраивая транзитный поток или максимум транзитных "
+"туннелей в 0 (см. выше).\n"
+"Так делать нехорошо, т.к. сеть выиграет от большего числа "
+"маршрутизаторов, которые передают транзитный трафик друг-другу.\n"
+"Более 95% пользователей участвуют в обмене трафиком с другими."
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+"Хранение - I2P не является распределенным хранилищем данных. Вы, "
+"возможно, имели в виду такую сеть, как\n"
+"Freenet.\n"
+"Ничьи данные не хранятся на вашем компьютере только из-за того, что вы "
+"запускаете I2P."
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+"Доступ - Если есть какие-то сайты в I2P, которые вам не нравятся -"
+" не ходите на них.\n"
+"Или используйте средства автоблокировки, такие как Privoxy или "
+"какой-нибудь вариант \"родительского контроля\"."
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+"Нет, это нормально.\n"
+"Все маршрутизаторы динамически подстраиваются под изменяющиеся условия и "
+"требования сети."
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+"Возможно, Вам нужно выполнить начальную загрузку (reseed) маршрутизатора "
+"I2P. В последних версиях I2P Вы можете пройти на http://localhost:7657/configreseed"
+" и нажать кнопку Сохранить изменения и произвести начальную "
+"загрузку. Если этот метод не поможет (или Вы используете очень "
+"старую версию) — Вам придется выполнить "
+"начальную загрузку вручную."
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+"Адрес для начальной загрузки изменился несколько лет назад. Если это Ваша"
+" первая установка и Вы установили\n"
+"старую (0.6.1.30 или более раннюю) версию, или\n"
+"Вы не запускали I2P длительное время, Вам нужно изменить адрес и потом\n"
+"нажать кнопку \"Reseed\" в консоли, чтобы найти другие маршрутизаторы.\n"
+"После запуска маршрутизатора, \n"
+"на configadvanced.jsp,"
+"\n"
+"добавьте строчку i2p.reseedURL=http://netdb.i2p2.de/\n"
+"ИЛИ i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (любой вариант "
+"подойдёт),\n"
+"потом нажмите \"Apply\" и кликните на ссылку \"reseed\" слева."
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+"Это работает если Вы запустили версию 0.6.1.27 или более позднюю.\n"
+"Если Вы работаете на версии 0.6.1.31 или более поздней, Вам, наверное, не"
+" нужно делать этого.\n"
+"Если Вы работаете с 0.6.1.26 или более ранней версией, используйте "
+"инструкцию по выполнению\n"
+"ручной начальной загрузки, описанную ниже,"
+" или \n"
+"установите последнюю версию.\n"
+"Другой вариант - добавьте\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"в wrapper.config, полностью остановите маршрутизатор и запустите его "
+"заново, потом нажмите на \"reseed\".\n"
+"Сообщите нам, если это сработало."
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+"...но Вам *действительно* нужно обновиться до последней версии."
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+"Если у Вашего маршрутизатора 10 или более активных пиров, то все у Вас "
+"хорошо. Изменения в версиях 0.6.1.31 и 0.6.1.32 улучшили\n"
+"работу маршрутизатора и эффективно уменьшили требуемое ему количество "
+"активных пиров.\n"
+"Маршрутизатор всегда должен поддерживать соединения с несколькими "
+"пирами.\n"
+"Наилучший способ оставаться интегрированным в сеть — это предоставлять сети больше "
+"транзитного трафика."
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+"А мой роутер является \"выходным узлом\" в обычный интернет? Я не хочу "
+"чтобы он был."
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+"Нет. В отличие от Tor,\n"
+"\"выходные узлы\" или \"outproxies\" не являются неотъемлемой частью "
+"сети.\n"
+"Только добровольцы, которые их создают и поддерживают, используют "
+"отдельные приложения чтобы передавать трафик в открытые сети.\n"
+"Таких очень и очень немного."
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+"Смотрите выше. Существует очень немного выходных шлюзов в обычную сеть, "
+"это не часть сети,\n"
+"и они могут не работать.\n"
+"В добавок, старые выходные прокси - squid.i2p, true.i2p, krabs.i2p - "
+"исчезли.\n"
+"Единственный оставшийся на данный момент выходной прокси — это "
+"false.i2p.\n"
+"Чтобы пользоваться им, измените Ваши настройки для "
+"eepProxy\n"
+"и установите список выходных прокси на 'false.i2p' (единственную строку)."
+"\n"
+"После чего остановите и запустите снова eepProxy.\n"
+"Если это не работает, значит выходной прокси лежит. И это не проблема "
+"I2P.\n"
+"Если основной ваш сценарий это анонимный доступ к сайтам\n"
+"обычного интернета, воспользуйтесь Tor."
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+"Внутри I2P нет необходимости в HTTPS, так как весь трафик шифруется от "
+"точки до точки.\n"
+"А FTP не поддерживается по техническим причинам."
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+"Нет никаких выходных прокси для FTP в Интернет — скорее всего даже "
+"невозможно реализовать такое.\n"
+"Другие варианты выходных прокси можно сделать, если воспользоваться "
+"настройками обычных туннелей. \n"
+"Если Вы хотели бы запустить какой-либо тип выходного прокси, осторожно и "
+"внимательно рассмотрите возможные риски. \n"
+"Вы всегда можете спросить о чем-то при необходимости, но Вам следует "
+"учесть, что сообщество I2P не гарантирует помощь в техническом плане."
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+"Как ранее уже несколько раз объяснялось, все существующие выходные прокси"
+" не являются составной частью сети.\n"
+"Это сервисы, поддерживаемые некоторыми особами, и бесперебойная работа\n"
+"в каждый момент времени для этих сервисов не гарантирована."
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
            \n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+"Обновление: Благодаря проделанной h2ik работе, теперь для I2P "
+"доступен выходной прокси для протокола https. Начиная с I2P 0.8.4, туннель для "
+"него выделен по умолчанию.
            \n"
+"В случае, если https прокси отсутсвует в Вашей версии I2P, его можно "
+"легко настроить, выполнив следующее:"
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+"Откройте менеджер "
+"туннелей i2p. Прокрутите страницу в самый низ."
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+"Выберите CONNECT из списка Новый клиентский туннель, "
+"нажмите Создать"
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+"На новой странице задайте Название и Описание Вашему https "
+"туннелю, которые Вы пожелаете.\n"
+"Настройка Точка доступа это Ваш локальный порт для Вашего нового "
+"https прокси, рекомендуемый порт — 4445.\n"
+"В поле Список outproxy тут должен быть .i2p адрес сервера, который"
+" поддерживает https.\n"
+"Смотрите запись h2ik на форуме,"
+" там указан адрес.\n"
+"Удостоверьтесь, что пункты Коллективный клиент, Задержка "
+"соединения и Автозапуск отмечены галкой.\n"
+"Другие опции нужно оставить по умолчанию. Нажмите \"Сохранить\". В "
+"менеджере туннелей, нажмите \"Запустить\" возле записи вашего нового "
+"туннеля."
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+"В Firefox нажмите на "
+"Инструменты>>ОпцииДополнительно>Сеть>Настройки."
+"\n"
+"Снимите галку с опции Использовать этот прокси-сервер для всех "
+"протоколов, в полях SSL прокси: установите localhost:4445."
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "Готово."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+"\n"
+"Это вопрос, на который только Вы сами можете ответить, так как он зависит"
+" от Вашего поведения, Вашей\n"
+"модели угроз, а также от того, насколько "
+"Вы доверяете владельцу выходого прокси."
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+"Как и Tor, I2P не шифрует Интернет магическим образом.\n"
+"Вы уязвимы к тому, что владелец выходного шлюза может за Вами следить.\n"
+"Посмотрите на хорошую статью по этой теме в\n"
+"Tor"
+" FAQ."
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+"Вдобавок, Вы можете быть уязвимы к сговору между владельцем выходного "
+"прокси\n"
+"и владельцами других сервисов в I2P, если используете те же туннели "
+"(\"shared clients\").\n"
+"Подробнее по этой теме можно ознакомиться здесь: %(zzz)s."
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+"Пока нет выходного прокси для сервиса, к которому Вы хотите подключиться,"
+" это невыполнимо.\n"
+"На данный момент есть только три типа выходных прокси: HTTP, HTTPS и "
+"email. Обратите внимание, что SOCKS прокси отсутствует.\n"
+"Если нужны какие-то другие типы сервисов - воспользуйтесь Tor."
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+"Если Вы рассматриваете каждый eepsite, который создавался вообще - да, "
+"большинство из них недоступны.\n"
+"Люди и сайты приходят и уходят.\n"
+"Хороший способ начать работать с I2P - проверить списки eepsite'ов, "
+"которые сейчас доступны.\n"
+"%(eepstatus)s отслеживает доступные "
+"eepsite'ы."
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+"Нажмите на ссылку Веб-сайт\n"
+"наверху интерфейса консоли маршрутизатора."
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+"Почему закачки, торренты, сёрфинг и вообще все такое медленное в I2P?\n"
+"Шифрование и маршрутизация в сети I2P добавляет значительные затраты и "
+"ограничивает полосу пропускания. \n"
+"Анонимность не бывает бесплатной."
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+"В дополнение к этому, Вы и все остальные возможно должны увеличить ваши "
+"ограничения по трафику.\n"
+"Две ключевые настройки это входящее и исходящее ограничение по трафику на"
+"\n"
+"странице конфигурации.\n"
+"С настройками по умолчанию в 32 КБ/с Вы, скорее всего, получите не "
+"более 15 КБ/с полосы в I2PSnark.\n"
+"Увеличение этих настроек (конечно, в рамках ограничений Вашего "
+"подключения к сети)\n"
+"увеличит потенциально возможную пропускную способность для I2PSnark и "
+"других приложений."
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+"И ещё, выделили ли Вы достаточную полосу пропускания для сети, чтобы "
+"транзитные туннели\n"
+"могли нормально проходить Ваш маршрутизатор? Верите или нет, разрешение "
+"транзитного трафика\n"
+"приводит к лучшей интеграции в сеть и позволяет увеличивать уже Вашу "
+"скорость передачи."
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+"I2P находится в процессе развития. Многое меняется и исправляется, и\n"
+"в общем, использование новейших версий помогает увеличить "
+"произодительность.\n"
+"Если Вы работаете на старой версии — поставьте новую."
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+"Смотрите\n"
+"Частые вопросы по "
+"Битторренту в I2P"
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+"\n"
+"Туннель до главного IRC сервера в I2P, Irc2P, создается при установке "
+"системы (см. \n"
+"страницу "
+"настройки),\n"
+"и автоматически запускается вместе с маршрутизатором. Чтобы его "
+"использовать, настройте ваш IRC\n"
+"клиент на соединение с localhost 6668. Те, кто пользуется "
+"XChat и подобными клиентами, могут создать новую сеть с сервером "
+"localhost/6668 (не забудьте выставить крыжик "Не "
+"использовать\n"
+"прокси" если у вас настроен прокси-сервер)."
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface.  However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+"По соображениям безопасности, консоль управления маршрутизатором слушает "
+"только на локальном интерфейсе.\n"
+"Тем не менее, с небольшим усилием вы можете перенастроить ее на удаленный"
+" доступ:"
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"with 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+"Откройте ~/.i2p/clients.config и замените 
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"на 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+"Go to http://localhost:7657/configui"
+"\n"
+"добавьте логин и пароль на консоль, если нужно."
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+"Пройдите на  http://localhost:7657/index.jsp"
+"\n"
+"и нажмите на \"Мягкий перезапуск\", это перезапустит JVM и все приложения."
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+"После запуска вы сможете попасть на консоль удаленно. Перезагрузите "
+"маршрутизатор на \n"
+"http://127.0.0.1:7657 и у вас спросят логин и пароль, введенные на шаге 2"
+"\n"
+"выше, если ваш браузер поддерживает авторизацию. Обратите внимание: \n"
+"0.0.0.0 выше указывает на адрес интерфейса, это не "
+"сеть и не маска сети. 0.0.0.0\n"
+"значит \"слушать на всех интерфейсах\", так что доступ будет и на  "
+"127.0.0.1:7657, и на\n"
+"все другие адреса."
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+"По умолчанию, интерфейс I2CP маршрутизатора (порт 76254) слушает только "
+"на 127.0.0.1. Чтобы он слушал на всех интерфейсах (0.0.0.0), настройте "
+"дополнительно i2cp.tcp.bindAllInterfaces=true и перезапустите "
+"маршрутизатор."
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "Что такое \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+"Eepsite это вебсайт, который работает анонимно - вы можете на него "
+"попасть только\n"
+"настроив ваш браузер на использование прокси I2P (обычно это localhost, "
+"порт 4444)."
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+"Настройка прокси-сервера для разных браузеров описана на \n"
+"этой странице с картинками.  Более продвинутые настройки с внешними "
+"инструментами тоже возможны, но могут представлять риски деанонимизации."
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+"x это число пиров, кому вы послали или от кого приняли сообщение\n"
+"за последнюю минуту, y это число пиров, которых маршрутизатор наблюдал за"
+" последний час или около того."
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+"Можно использовать SOCKS прокси, начиная с релиза 0.7.1. Поддерживается "
+"SOCKS 4/4a/5.\n"
+"Штатной выходной SOCKS прокси в системе нет, так что использование "
+"несколько ограничено."
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+"Дополнительно, многие приложения позволяют утечки\n"
+"чувствительной информации, которая может вас идентифицировать в "
+"интернете. I2P фильтрует только\n"
+"данные соединения, но сами программы, что вы используете, могут "
+"отправлять эту информацию вместе с данными, и I2P никак вам тут не может "
+"помочь.  Например,\n"
+"некоторые приложения почты отправляют IP адрес машины клиента на почтовый"
+" сервер. Для I2P нет возможности защитить от такого, так что использовать"
+" I2P для проксирования стандартных приложений возможно, но крайне "
+"небезопасно. "
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+"Если вы хотите больше информации по поводу SOCKS прокси и приложений, \n"
+"обратите внимание на советы на этой странице "
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+"Вот тут есть список портов по умолчанию (все это можно \n"
+"поменять настройкой):"
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+"Порты в интернет\n"
+"Обратите внимание: Свежие инсталляции, начиная с 0.7.8 не используют порт"
+" 8887; они выбирают случайный порт между 9000 и 31000 при первом запуске."
+"\n"
+"Этот порт показан на странице конфигурации."
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+"    "
+msgstr ""
+"Исходящий UDP с разных портов, указанных на  странице конфигурации до"
+" разных удаленных UDP портов, с получением ответов\n"
+"    "
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+"    "
+msgstr ""
+"Исходящий TCP со случайных высоких портов (выше 1024) до определенных "
+"удаленных TCP портов\n"
+"    "
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+"    "
+msgstr ""
+"(можно обойтись, но желательно) Входящий UDP на порт, указанный в  настройках из разных "
+"источников\n"
+"    "
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
            \n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+"(можно обойтись, но желательно) Входящий TCP на порт в конфигурации из разных "
+"источников
            \n"
+"Можно запретить входящий TCP в  настройках."
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
            \n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+"Исходящий UDP на порт 123, с ответами
            \n"
+"Это необходимый для I2P синхронизатор времени  (через SNTP - \n"
+"запрашивая разные сервера NTP из pool.ntp.org или тот, который \n"
+"вы указали)"
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+"Локальные порты I2P, которые слушают на локальном хосте по "
+"умолчанию,\n"
+"кроме указанных явно:"
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"1900: UPnP SSDP UDP multicast слушатель.\n"
+"Не меняется, слушает на всех интерфейсах.\n"
+"Можно выключить в  confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+"2827: BOB bridge, высокоуровневое API для клиентов.\n"
+"Выключен по умолчанию.\n"
+"Можно включить\\выключить в  configclients.jsp.\n"
+"Можно изменить в  bob.config file."
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4444: HTTP прокси-сервер\n"
+"Можно выключить или изменить на странице настройки туннелей.\n"
+"Можно настроить слушать локально или на выбранных интерфейсах."
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4445: HTTPS прокси-сервер\n"
+"Можно включить и выключить в настройках туннелей.\n"
+"Можно привязать ко всем или конкретным интерфейсам."
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"6668: IRC прокси-сервер\n"
+"Можно включить и выключить в настройках туннелей.\n"
+"Можно привязать ко всем или конкретным интерфейсам."
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7652: UPnP HTTP TCP слушатель.\n"
+"Binds to the LAN address.\n"
+"Можно поменять дополнительной настройкой i2np.upnp.HTTPPort=nnnn.\n"
+"Можно выключить в confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Слушает на всех интерфейсах.\n"
+"Можно поменять доп. настройкой  i2np.upnp.SSDPPort=nnnn.\n"
+"Можно выключить в confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+"7654: Клиентский порт I2P, используемый приложениями.\n"
+"можно поменять на \n"
+"configclients.jsp"
+"\n"
+"но лучше этого не делать.\n"
+"Можно привязать к интерфейсам или выключить на странице \n"
+"configclients.jsp."
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+"7655: UDP for SAM bridge, API высокого уровня для клиентов.\n"
+"Открывается только когда клиент SAM V3 запрашивает сессию UDP.\n"
+"Можно включить-выключить на configclients.jsp.\n"
+"Можно поменять в настройках  clients.config file в  sam.udp.port=nnnn."
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"С версии  0.6.5 по умолчанию отключен.\n"
+"Можно включить-выключить в  configclients.jsp.\n"
+"Можно поменять в clients.config file."
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+"7657: Интерфейс маршрутизатора\n"
+"Можно отключить в  clients.config.\n"
+"Можно настроить на всех или на выбранные интерфейсы."
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+"7658: Ваш eepsite\n"
+"Можно выключить в файле clients.config.\n"
+"Можно привязать к адресам интерфейсов в файле jetty.xml."
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7659: Исходящая почта на smtp.postman.i2p\n"
+"Можно включить и поменять в настройках туннелей.\n"
+"Можно настроить на разные сетевые интерфейсы"
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7660: Входящая почта с pop.postman.i2p\n"
+"Можно выключить или поменять в настройках туннелей.\n"
+"Можно привязать к интерфейсам"
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"8998: mtn.i2p2.i2p (Monotone - по умолчанию выключено)\n"
+"Можно включить и выключить в настройках туннелей. \n"
+"Можно привязать ко всем или конкретным интерфейсам."
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"31000: Локальный порт управления враппером.\n"
+"Исходящие соединения на порт 32000, на этом порту не слушает.\n"
+"Начинает  с порта 31000 и последовательно ищет свободный порт до 31999.\n"
+"Чтобы поменять, см. \n"
+"документацию на враппер.\n"
+"Для доп. информации, смотрите также  ниже."
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"32000: Локальный порт управления враппером сервиса.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally.  You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+"Локальные порты I2P и порты туннелей не должны быть доступны с удаленных\n"
+"машин, но *должны* быть доступны локально. Вы также можете создать "
+"дополнительные порты для\n"
+"I2PTunnel через http://localhost:7657/i2ptunnel/  (и вообще, вам стоит "
+"настроить ваш локальный доступ в\n"
+"файрволле, а удаленный запретить, если вам он не нужен)"
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance.  You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+"В заключение, ничего не должно быть доступно неразрешенным удаленным "
+"соединениям, но стоит разрешить удаленный доступ к интернет-портам, это хорошо "
+"отразится на производительности.  Вам нужно иметь возможность отправлять "
+"UDP наружу, на разные \n"
+"удаленные адреса (Случайное блокирование адресов чем-нибудь вроде "
+"PeerGuardian\n"
+"вам будет только мешать, не делайте так)."
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr "Почему I2P слушает на порту 32000?"
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+"Сервис-враппер Tanuki, который мы используем, использует этот порт, "
+"привязанный только к локальному интерфейсу, чтобы взаимодействовать с "
+"софтом внутри JVM. Когда JVM запускается, ей передается ключ, чтобы она "
+"могла общаться с враппером. После того, как JVM установила соединение с "
+"враппером, враппер более не принимает дополнительных соединений. "
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the  \n"
+"wrapper documentation."
+msgstr ""
+"Дополнительная информация есть в \n"
+"документации на враппер."
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+"I2P маршрутизатор нужно просидировать только раз, чтобы в первый раз "
+"подключиться к сети.\n"
+"Сидирование это ничто иное, как посылка HTTP GET запросов\n"
+"чтобы скачать список роутеров и файлов \"routerinfo\" \n"
+"с заранее известных URL"
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+"Очевидным признаком проблемы неудачного ресида является \n"
+"показатель \"Известно\" (слева на интерфейсе маршрутизатора), который "
+"показывает очень малые значения\n"
+"(часто - меньше 5), и который не увеличивается. Так получается, среди "
+"прочего, \n"
+"когда ваш файрволл блокирует исходящий трафик, а также запросы ресида. "
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr "Чтобы вручную просидировать I2P маршрутизатор, сделайте так:"
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr "Остановите ваш I2P маршрутизатор"
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+"Пойдите обычным браузером на  http://netdb.i2p2.de/ "
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr ""
+"Сохраните десяток файлов \"routerinfo\" в директорию netDb вашего "
+"маршрутизатора"
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr "Запустите ваш маршрутизатор"
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+"При запуске маршрутизатора командой \"i2prouter start\", вы можете "
+"увидеть такие строки:"
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+"\n"
+"Чтобы убедиться, что I2P работает на максимальном количестве платформ, до"
+" версии 0.8.9 I2P мы использовали java wrapper, \n"
+"собранный для FreeBSD 6.x. Если вы столкнулись с такой ошибкой, у вас не "
+"хватает библиотек совместимости.\n"
+"Эти библиотеки можно установить вот так:"
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+"Получите права root с помощью  su или просто залогиньтесь, "
+"как root."
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+"Если у вас не получается установить эти библиотеки (или вы не хотите так "
+"делать),\n"
+"другой вариант это собрать враппер для вашей⏎\n"
+"системы, запускать I2P без враппера командой "
+"runplain.sh,  или⏎\n"
+"заменить враппер на тот, что уж собран под вашу систему из его "
+"дистрибутива."
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+"С версии 0.8.9 I2P, враппер обновлен до v3.5.12 и собирается на системе  "
+"FreeBSD 7.2."
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+"Внутри wrapper.log я вижу ошибку вида Protocol family "
+"unavailable при запуске консоли маршрутизатора."
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+"Эта ошибка часто возникает на сетевых java приложениях на системах, "
+"которые используют IPv6 по умолчанию. Есть несколько вариантов действий:"
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+"На Linux, можно сделать echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr "Ищите следующие строки в wrapper.config."
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+"Если такие строки есть, раскомментируйте их, удалив \"#\". Если таких "
+"строк нет, то добавьте их без \"#\" в начале строк."
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+"Другой вариант - это удалить  ::1 из "
+"~/.i2p/clients.config"
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+"ПРЕДУПРЕЖДЕНИЕ: Чтобы применить любые изменения в  "
+"wrapper.config нужно\n"
+"полностью остановить и маршрутизатор, и враппер. Нажатие "
+"Перезапуск на консоли маршрутизатора не достаточно! Нужно "
+"выполнить Shutdown, подождатьт 11 минут и перезапустить I2P."
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+"Отлично!  Вы найдете нас на IRC irc.freenode.net #i2p или напишите на\n"
+" форум и мы это выложим на сайт "
+"(надеюсь, что с ответом)."
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "Немецкие законы"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr "Анонимная сеть I2P"
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+"Механизм анонимной передачи данных точка-точка, основанный на средствах с"
+" открытым исходным кодом и предназначенный для работы многих стандартных "
+"Интернет-сервисов, таких как электронная почта, IRC или веб-хостинг. "
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr "Что для вас делает I2P?"
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+"Сеть I2P реализует защиту приватности коммуникаций в интернет. Многие "
+"действия, которые могли подвергать риску вашу приватность в открытых "
+"сетях, могут относительно безопасно выполняться в рамках I2P"
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr "Возьмите I2P %(version)s"
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "Что такое I2P?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+"I2P это сеть внутри сети, анонимная оверлейная сеть. Она предназначена "
+"для защиты передачи данных от внешнего наблюдения и подглядывания, "
+"например от наблюдения на провайдере.\n"
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+"I2P используется людьми, которые заботятся о своей приватности, такими "
+"как активисты, угнетенные народы, журналисты и обычные люди.\n"
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+"Ни одна сеть не может быть \"совсем анонимна\". Основная цель I2P - это "
+"сделать атаки максимально сложными. Анонимность будет вырастать с ростом "
+"сети, а также с развитием самой системы, за счет научного анализа "
+"результатов.\n"
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+"I2P доступна на обычных компьютерах, встраиваемых системах (как Raspberry"
+" Pi) и Android устройствах. Расскажите всем!\n"
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr "Дальнейшее чтение и помошь"
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr "Что можно сделать в I2P?"
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+"Email: Встроенный веб-мейл, плагин "
+"для бессерверной почты."
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+"Web browsing: Анонимные "
+"вебсайты, шлюзы в и из публичного интернета."
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+"Блоги и форумы: Блоги и"
+" плагины Syndie."
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+"Хостинг вебсайтов: "
+"Встроенный анонимный веб-сервер."
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr "Чат: Чаты и IRC клиенты."
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+"Файлообмен: ED2K и Gnutella, "
+"встроенный BitTorrent."
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+"Распределенное "
+"хранение файлов: Tahoe-LAFS плагин для распределенной файловой "
+"системы."
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr "Другие поддерживаемые приложения"
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr "Новости и обновления"
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr "Рекомендуемые ссылки и ресурсы"
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+"Вот тут есть страница\n"
+"с презентациями, видео и учебниками о I2P."
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr "I2P в сети"
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr "Друзья проекта I2P"
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr "Другие Проекты и документация"
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "Пресса"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr "Доски, новостные сайты, другое"
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr "Очень старое добро"
+
diff --git a/i2p2www/translations/ru/LC_MESSAGES/research.po b/i2p2www/translations/ru/LC_MESSAGES/research.po
new file mode 100644
index 00000000..45f2eb4f
--- /dev/null
+++ b/i2p2www/translations/ru/LC_MESSAGES/research.po
@@ -0,0 +1,157 @@
+# Russian (Russia) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# keedley , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-09-21 16:10+0000\n"
+"Last-Translator: keedley \n"
+"Language-Team: Russian (Russia) "
+"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 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/research/index.html:2
+msgid "Academic Research"
+msgstr "Научные исследования"
+
+#: i2p2www/pages/site/research/index.html:4
+msgid ""
+"Academic research and analysis of I2P is an important part of ensuring "
+"that the software and network performs as expected and is safe for users "
+"in hostile environments."
+msgstr ""
+"Научное исследование и анализ I2P это важная часть процесса контроля "
+"безопасности програмного обеспечения и сети в целом, в опасных условиях "
+"современного мира."
+
+#: i2p2www/pages/site/research/index.html:8
+#, python-format
+msgid ""
+"\n"
+"There is a large research community investigating a wide range of aspects"
+" of\n"
+"anonymity. For a current and comprehensive list of relevant papers, see "
+"the\n"
+"Free Haven Anonymity Bibliography.\n"
+"I2P benefits from much of the research into Tor and onion routing, but "
+"there is\n"
+"little dedicated research interest into the theory behind I2P, and the "
+"choices\n"
+"and tradeoffs that the network makes. This presents a unique opportunity "
+"for\n"
+"original research.\n"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:18
+#, python-format
+msgid ""
+"A list of known published papers about I2P is available here."
+msgstr ""
+"Список известных публикаций про I2P доступен вот "
+"тут."
+
+#: i2p2www/pages/site/research/index.html:22
+msgid "Testing Attacks on I2P"
+msgstr "Тестовые атаки на I2P"
+
+#: i2p2www/pages/site/research/index.html:24
+msgid ""
+"I2P can be run as a separate test network by controlling the locations "
+"that a new router reseeds from so that it only finds other test routers."
+msgstr ""
+"I2P можно запускать как отдельную сеть, контролируя расположения, откуда "
+"новые маршрутизаторы получают свои сиды, так чтобы тестовые "
+"маршрутизаторы работали только с тестовыми маршрутизаторами."
+
+#: i2p2www/pages/site/research/index.html:28
+msgid ""
+"The standard mode of operation is to have one JVM per router instance; "
+"hence running multiple copies of I2P on a single machine is inadvisable, "
+"both due to the potential resource drain and the certain port conflicts. "
+"To better facilitate setting up small test networks, I2P has a "
+"multirouter mode which enables multiple distinct routers to be run in the"
+" same JVM."
+msgstr ""
+"Стандартный способ работы это использовать одну JVM на один экземпляр "
+"маршрутизатора. Запуск нескольких копий I2P на одной машине не "
+"рекомендуется, как с точки зрения ресурсов, так и с точки зрения "
+"конфликтов по портам. Для лучшего развертывания небольших тестовых сетей,"
+" I2P может работать в режиме multirouter, который реализует запуск "
+"нескольких маршрутизаторов в рамках одной JVM."
+
+#: i2p2www/pages/site/research/index.html:32
+msgid ""
+"MultiRouter can be started from the i2p base directory by running the "
+"below command."
+msgstr ""
+"MultiRouter можно запустить из базовой директории I2P с помощью команды "
+"ниже:"
+
+#: i2p2www/pages/site/research/index.html:37
+msgid ""
+"Additionally, I2P can be started in a virtual network mode. This mode "
+"disables all transports, allowing the router to be tested in isolation "
+"without network traffic. To enable this mode, add "
+"i2p.vmCommSystem=true to the router.config before starting."
+msgstr ""
+"I2P можно также запускать в режиме виртуальной сети. Этот режим отключает"
+" все транспорты, позволяя тестировать маршрутизатор без сетевого доступа."
+" Чтобы включить такой режим, добавьме  i2p.vmCommSystem=true"
+" в router.config до запуска"
+
+#: i2p2www/pages/site/research/index.html:41
+msgid "Testing the Live I2P Network"
+msgstr "Тестирование работающей I2P сети"
+
+#: i2p2www/pages/site/research/index.html:43
+#, python-format
+msgid ""
+"If you are planning on conducting research on the live I2P network, "
+"please contact us before you commence your "
+"testing. While we do not discourage researchers from responsibly testing "
+"their ideas on the live network, if an attack becomes apparent and we "
+"don't have any line of communication then we will end up taking "
+"countermeasures which could interfere with the test."
+msgstr ""
+"Если вы планируете произоводить исследования на живой I2P сети, "
+"пожалуйста, свяжитесь с нами заранее. Хотя мы"
+" не против ответственных исследователей, которые проверяют свои идеи на "
+"живой сети, если мы заметим вмешательство и у нас не будет способа "
+"связаться, исследование может быть испорчено применяемыми нами "
+"контр-мерами."
+
+#: i2p2www/pages/site/research/questions.html:2
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:4
+msgid "Network database"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:6
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:8
+msgid "Tunnels and Destinations"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:10
+msgid "Unidirectional tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:16
+msgid "Multihoming"
+msgstr ""
+
diff --git a/i2p2www/translations/sv_SE/LC_MESSAGES/about.po b/i2p2www/translations/sv_SE/LC_MESSAGES/about.po
new file mode 100644
index 00000000..a7227ba9
--- /dev/null
+++ b/i2p2www/translations/sv_SE/LC_MESSAGES/about.po
@@ -0,0 +1,2691 @@
+# Swedish (Sweden) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# samaire , 2013
+# hottuna , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-11-20 01:43+0000\n"
+"Last-Translator: samaire \n"
+"Language-Team: Swedish (Sweden) "
+"(http://www.transifex.com/projects/p/I2P/language/sv_SE/)\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/about/browser-config.html:2
+msgid "Web Browser Configuration"
+msgstr "Webbläsar-konfiguration"
+
+#: 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 ""
+"Din webbläsare kommer behöva konigureras för att kunna surfa eepsidor och"
+" att kunna\n"
+"använda de utproxys som finns inom I2P. Nedan finns guider för några av "
+"de mest populära webbläsarna."
+
+#: i2p2www/pages/site/about/browser-config.html:11
+msgid "How to configure your browser"
+msgstr "Hur du ställer in din webbläsare"
+
+#: i2p2www/pages/site/about/browser-config.html:17
+#: i2p2www/pages/site/about/browser-config.html:73
+msgid "Outproxy Terms Of Service"
+msgstr "Användarvillkor För utproxyn"
+
+#: i2p2www/pages/site/about/browser-config.html:22
+msgid "Internet Explorer 8 or Chrome"
+msgstr "Internet Explorer 8 eller 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 ""
+"I verktygsmenyn välj \"Internet Alternativ\"-raden för att öppna "
+"inställningarna. I det inställningsfönstret välj anslutnings-tabben och "
+"klicka på LAN inställningar för att nå proxy ports konfigurationen."
+
+#: i2p2www/pages/site/about/browser-config.html:28
+msgid "IE Internet Options"
+msgstr "IE Internet Alternativ"
+
+#: 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 ""
+"Fyll i kryssrutan vid \"använd en proxy-server för ditt LAN\" och vid "
+"\"Kringå\n"
+"proxy-server för lokala adresser\". Med ett klick på Advancerat-knappen "
+"öppnar du fönstret för att öppna portarna. Skriv in värdena som i bilden,"
+" IP 127.0.0.1, port 4444 för HTTP och port 4445 för HTTPS. Med klick på "
+"OK så sparar du inställningar och din webbläsare är inställd på att "
+"använda I2P-proxyn."
+
+#: i2p2www/pages/site/about/browser-config.html:36
+msgid "IE Proxy Settings"
+msgstr "IE Proxy Inställningar"
+
+#: 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 ""
+"Från Verktygs-menyn, välj Alternativ för att öppna inställningspanelen i "
+"Firefox.\n"
+"Klicka på ikonen märkt Advancerat, klicka sedan på "
+"NätverkAnslutningar-delen, klicka på Inställnings-knappen. "
+"Du kommer se ett fönster likt det följande:"
+
+#: i2p2www/pages/site/about/browser-config.html:46
+msgid "Firefox Network Options"
+msgstr "Firefox Nätverks Inställningar"
+
+#: 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 ""
+"I Anslutnings Inställningar-fönstret, klicka på cirkeln bredvid "
+"Manuell\n"
+"proxy inställning, skriv sedan in 127.0.0.1, port 4444 i HTTP Proxy "
+"fältet. Skriv in 127.0.0.1, port 4445 i SSL Proxy fältet.\n"
+"Kom ihåg att skriva in localhost och 127.0.0.1 i \"Ingen Proxy för\" "
+"rutan."
+
+#: i2p2www/pages/site/about/browser-config.html:53
+msgid "Firefox Proxy Settings"
+msgstr "Firefox Proxy Inställningar"
+
+#: 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 ""
+"Välj från Inställningar-menyn, Konfigurera Konqueror. I"
+" Webbläsar-gruppen på vänster sida, välj Proxy Tjänster.\n"
+"I det nya fönstret, välj alternativet \"Ange manuellt proxy "
+"inställningar\" och klicka på Inställningar rutan."
+
+#: i2p2www/pages/site/about/browser-config.html:63
+msgid "Konqueror Proxy Options"
+msgstr "Konqueror Proxy Inställningar"
+
+#: 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 ""
+"Skriv in 127.0.0.1 och port 4444 i HTTP rutan. Skriv in 127.0.0.1 och "
+"port 4445 i HTTPS rutan. Klicka på Ny-knappen i undantags "
+"sektionen. Skriv in localhost och klicka på OK. Klicka på "
+"Ny-knappen en gång till och skriv in 127.0.0.1 och klicka OK. "
+"Tryck på OK en gång till för att stänga konfigurationsfönstret."
+
+#: i2p2www/pages/site/about/browser-config.html:70
+msgid "Konqueror Proxy Ports"
+msgstr "Konqueror Proxy Portar"
+
+#: 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 ""
+"Kom ihåg: I2P är inte designat för att skapa proxys till det vanliga "
+"internet.\n"
+"Istället är det avsett att användas som ett internt nätverk."
+
+#: 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 ""
+"I2P projektet själv kör inga proxys till internet. Alla sådana proxy-"
+"tjänster körs av privata personer och kan stängas av eller vara onådbara "
+"vid vilket tillfälle som helst."
+
+#: 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 ""
+"Båda dessa utproxys är konfigurerade med anslutningsbegränsningar. Det "
+"betyder\n"
+"att bara en bestämd mängd av åtkomster ät tillåtna per klient. När "
+"gränsen är\n"
+"nådd, så blockeras klienten i 1min/1h/1dag. Var\n"
+"respektfull och overbelasta inte domhär tjänsterna med för mångra "
+"förfrågningar!"
+
+#: 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 ""
+"Tor är en bra applikation att "
+"använda som en\n"
+"utproxy till internet."
+
+#: i2p2www/pages/site/about/glossary.html:2
+msgid "Glossary"
+msgstr "Ordlista"
+
+#: i2p2www/pages/site/about/glossary.html:4
+msgid ""
+"This page lists often-used terminology when discussing I2P and "
+"cryptography."
+msgstr ""
+"Denhär sidan listar terminologi som ofta används när I2P och kryptografi "
+"diskuteras."
+
+#: i2p2www/pages/site/about/hall-of-fame.html:2
+msgid "Hall Of Fame"
+msgstr "Hall of Fame"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:5
+msgid "I2P's Hall of Fame"
+msgstr "I2Ps Hall of Fame"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:6
+#, python-format
+msgid "Current balance: as of %(date)s"
+msgstr "Nuvarande saldo: sedan %(date)s"
+
+#: 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 "Generell fond"
+
+#: 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 "%(euroval)s € och %(btcval)s BTC"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:11
+msgid "Datastorage bounty"
+msgstr "Datalagrings belöning"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:13
+msgid "Native IPv6 I2P"
+msgstr "Native IPv6 I2P"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:15
+msgid "I2PHex bounty"
+msgstr "I2Phex belöning"
+
+#: 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 i debian speglar"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:19
+msgid "Bitcoin client for I2P"
+msgstr "Bitcoin klient för I2P"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:21
+msgid "Unit Tests for I2P router"
+msgstr "Enhetstester för I2P routern"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:23
+msgid "Bounty Robert"
+msgstr "Belöning Robert"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:24
+msgid "Bounty Syndie"
+msgstr "Belöning Syndie"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:25
+msgid "Bounty I2P for CCR Microtic Board"
+msgstr "Belöning I2P för CCR Microtic Board"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:28
+msgid "Current monthly running costs:"
+msgstr "Nuvarande månatliga driftkostnader:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:39
+msgid "Big thanks go to the following people who have donated to I2P!"
+msgstr "Stort tack till följande personer som donerat till I2P!"
+
+#: 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 ""
+"Om du har gjort en donation, skicka ett e-post till echelon\n"
+"med ditt namn eller nick (och om du vill hemsida) så vi kan lista dig här."
+
+#: i2p2www/pages/site/about/hall-of-fame.html:45
+msgid "Current monthly subscriptions:"
+msgstr "Nuvarande månatliga prenumerationer:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:51
+msgid "2013 donations and costs:"
+msgstr "2013 donationer och kostnader:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:170
+msgid "2012 donations and costs:"
+msgstr "2012 donationer och kostnader:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:298
+msgid "2011 donations and costs:"
+msgstr "2011 donationer och kostnader:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:399
+msgid "Previous to 2011 donations:"
+msgstr "Donationer för 2011:"
+
+#: i2p2www/pages/site/about/intro.html:2
+msgid "Intro"
+msgstr "Intro"
+
+#: i2p2www/pages/site/about/intro.html:4
+msgid "The Invisible Internet Project"
+msgstr "The Invisible Internet Project"
+
+#: i2p2www/pages/site/about/intro.html:5
+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 \n"
+"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 ""
+"I2P är ett anonymt nätverk, som erbjuder ett enkelt lager som "
+"applikationer kan \n"
+"använda för att anonymt och säkert skicka meddelanden till varandra. "
+"Nätverket själv är \n"
+"strikt meddelande-baserat (a la \n"
+"IP), men "
+"det finns ett \n"
+"bibliotek tillgängligt som erbjuder pålitltlig strömmande kommunikation "
+"ovanpå det (a la \n"
+"TCP)."
+"  \n"
+"All kommunikation är start-till-slut krypterad (totalt finns det fyra "
+"lager \n"
+"av kryptering som används när ett meddelande skickas), och även "
+"slutpunkterna (\"målen\") \n"
+"är kryptografiska identifierare (i princip ett par av publika "
+"nycklar)."
+
+#: i2p2www/pages/site/about/intro.html:17
+msgid "How does it work?"
+msgstr "Hur fungerar det?"
+
+#: i2p2www/pages/site/about/intro.html:19
+#, 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 ""
+"För att anonymisera meddelanden som skickas, så får varje klient-"
+"applikation sin I2P \"router\"\n"
+"att bygga några få ingående och utgående \"tunnlar\" - en \n"
+"sekvens av peers som skickar meddelanden i en riktning (till och från "
+"klienten, \n"
+"respektive). När en klient vill skicka ett meddelande till en annan "
+"klient, \n"
+"så skickas meddelandet ut genom en av dess utgående tunnlar som är "
+"inriktad på en av den \n"
+"andra klientens ingående tunnlar, och eventuellt nås målet. Varje \n"
+"deltagare i nätverket väljer längden på dessa tunnlar och när det \n"
+"väljs så bestäms en balans mellan anonymitet, fördröjning och bandbredd "
+"enligt deras \n"
+"behov. Resultatet är det att ett antalet peers som vidarebefodrar varje "
+"start-till-slut \n"
+"meddelande is det absoluta minimum som krävs för att möta både avsändaren"
+" och \n"
+"mottagarens hotbild."
+
+#: i2p2www/pages/site/about/intro.html:33
+#, 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 ""
+"Första gången en klient vill kontakta en annan klient, så gör den en "
+"förfrågan \n"
+"mot den distribuerade \"nätverksdatabasen\" - "
+"en speciellt strukturerad \n"
+"distribuerad hash tabell (DHT) baserad på \n"
+"Kademlia "
+"algoritmen. Detta görs \n"
+"för att finna de andra klientens inåtgående tunnel effektivt, men "
+"efterföljande meddelanden \n"
+"mellan dom inkluderar den datan så inga efterföljande nätverksdatabas "
+"förfrågor \n"
+"krävs."
+
+#: i2p2www/pages/site/about/intro.html:44
+#, python-format
+msgid "More details about how I2P works are available."
+msgstr ""
+"Mer detaljer om hur I2P fungerar finns tillgängliga "
+"här."
+
+#: i2p2www/pages/site/about/intro.html:48
+msgid "What can you do with it?"
+msgstr "Vad kan du göra med det?"
+
+#: i2p2www/pages/site/about/intro.html:50
+#, 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 ""
+"Inom I2P-nätverket är applikationer inte begränsade i hur de kan "
+"kommunicera - de som typiskt använder UDP kan den grundläggande "
+"funktionaliteten och de som typiskt använder TCP kan använda det TCP-lika"
+" streaming biblioteket. Vi har en generisk TCP/I2P brygg-applikations "
+"(\"I2PTunnel\") som låter folk "
+"vidarebefodra TCP-strömmar in i I2P-nätverket och även mottaga strömmar "
+"från nätverket och vidarebefodra dom till en specifik TCP/IP adress."
+
+#: i2p2www/pages/site/about/intro.html:60
+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 ""
+"I2PTunnel används för närvarande för att låta personer köra sina egna "
+"anonyma webbsidor (\"eepsite\") genom att köra en vanlig webbserver och "
+"att peka en I2PTunnel 'server' mot den, vilken folk kan ny anonymt över "
+"I2P med en vanlig webbläsare\n"
+"genom att köra en I2PTunnel HTTP proxy (\"eepproxy\"). Utöver det, så "
+"använder vi samma teknik för att köra ett anonymt IRC-nätverk (där IRC-"
+"servern är hostad anonymt, och vanliga IRC-klienter använder en I2PTunnel"
+" för att kontakta den). Det finns andra aplikations-utvecklings "
+"ansträngningar som pågår med, t.ex. en för att bygga en optimerad svärm-"
+"filöverförings applikation  (a la \n"
+"BitTorrent), en distribuerad "
+"datalagrare (a la Freenet /"
+" \n"
+"MNet) och ett bloggsystem (ett "
+"fullt\n"
+"distribuerat LiveJournal), "
+"men dessa är inte redo för använding än."
+
+#: i2p2www/pages/site/about/intro.html:76
+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 ""
+"I2P är inte per definition en \"utproxy\"-nätverk - klienten du skickar "
+"ett meddelande\n"
+"till är den kryptografiska identifieraren, inte någon IP-adress, så "
+"meddelande måste vara adresserat till någon som kör I2P. Men, det är "
+"möjligt att den klienten\n"
+"är en utproxy, som låter dig anonymt använda deras interneranslutning. "
+"För att demonstrera detta, accepterar \"eepproxyn\" vanliga icke-I2P "
+"url:er (t.ex. \"http://www.i2p.net\") och vidarebefodrar dom till et "
+"specifikt mål som kör en squid HTTP proxy, som erbjuder enkelt anonymt surfande "
+"på det vanliga internet. Enkla utproxys som dom är inte gångbara i det "
+"långa loppet av flera anledningar (inklusice kostnaden för att köra en "
+"och anonymitet och säkerhets problem de introducerar), men i vissa "
+"situationer kan tekniken vara lämplig."
+
+#: i2p2www/pages/site/about/intro.html:90
+#, 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 ""
+"I2Ps utvecklar-team är en öppen grupp, som "
+"välkomnar alla som är intresserade av att hjälpa till, all källkod är open source. Kärnan av I2P SDK:n och den\n"
+"nuvarande routerimplementationen är gjord i Java (som för närvarande "
+"fungerar med både\n"
+"sun och kaffe, gcj-stöd planeras för senare) och det finns ett simple socket baserat API för att ge tillgång till "
+"nätverket från andra språk (med ett C bibliotek tillgängligt och både "
+"Python och Perl under utveckling). Nätverket är under aktiv utveckling "
+"och har inte ännu nått \n"
+"1.0 releasen, men den nuvarande utvecklingsplanen beskriver \n"
+"vårt tidschema."
+
+#: i2p2www/pages/site/about/media.html:2 i2p2www/pages/site/about/media.html:4
+msgid "Presentations on I2P"
+msgstr "Presentationer om I2P"
+
+#: 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 ""
+"Följande är länkar till presentationer, videor och guider om I2P. Länkar "
+"till akademiska artiklar om I2P är tillgängliga här."
+
+#: i2p2www/pages/site/about/media.html:8
+#, python-format
+msgid "To request an addition to this page, please send to %(email)s."
+msgstr "För att be om tillägg till denhär sidan, skicka till %(email)s."
+
+#: i2p2www/pages/site/about/media.html:11
+msgid ""
+"\n"
+"Newest links are at the bottom of each section."
+msgstr ""
+"\n"
+"De nyaste länkarna är på botten av varje del."
+
+#: i2p2www/pages/site/about/media.html:16
+msgid "Presentations"
+msgstr "Presentationer"
+
+#: 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 ""
+"IIP Presentation op CodeCon\n"
+"MP3 ljud\n"
+"transkript\n"
+"Lance James (0x90), Februari 2002."
+
+#: 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 ""
+"IIP Presentation op ToorCon\n"
+"MP3 ljud\n"
+"slides\n"
+"Lance James (0x90), Februari 2002."
+
+#: 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 ""
+"To Be or I2P\n"
+"(Youtube Video)\n"
+"En introduktion till anonym communication med I2P\n"
+"To Be or I2P (PDF presentation),\n"
+"Jens Kubieziel, 24C3 Berlin, December 28, 2007."
+
+#: 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 ""
+"Video av I2P föreläsning på Chemnitz Linux Tag,"
+"\n"
+"Lars Schimmer,\n"
+"Mars 14-15, 2009"
+
+#: 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 ""
+"HOPE New York Juli 17, 2010 - Kort överblick över I2P av zzz, på slutet "
+"av Adrian Hong's föreläsning\n"
+"\"Hackers for Human Rights\".\n"
+"MP3 ljud"
+
+#: 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 ""
+"Into the I2P Darknet: Welcome to Cipherspace\n"
+"Adrian Crenshaw. Schmoocon Firetalk, Januari 2011"
+
+#: 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 ""
+"Using techhnology to advance liberty\n"
+"(Youtube Video)\n"
+"Eric Johnson.\n"
+"Agora I/O Unconference, Mars 27, "
+"2011.\n"
+"I2P omtalas från 10:00 till 20:00 i videon."
+
+#: i2p2www/pages/site/about/media.html:69
+#, python-format
+msgid ""
+"The Bright side of darknets, FOSSCOMM Patras May "
+"2011"
+msgstr ""
+"The Bright side of darknets, FOSSCOMM Patras Maj "
+"2011"
+
+#: 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 ""
+"Common Darknet Weaknesses\n"
+"(Youtube Video)\n"
+"Adrian Crenshaw, AIDE, Juli "
+"11-15, 2011."
+
+#: 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 ""
+"I2P / Tor Workshop Anteckningar\n"
+"Adrian Crenshaw. DEF CON 19, Las Vegas, August 6, 2011."
+
+#: 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 ""
+"Cipherspaces/Darknets: An Overview Of Attack "
+"Strategies - 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."
+
+#: i2p2www/pages/site/about/media.html:94
+msgid ""
+"Modern cipherspace ecosystems, 0x375 "
+"0x06 4/11/2011"
+msgstr ""
+"Modern cipherspace ecosystems, 0x375 "
+"0x06 4/11/2011"
+
+#: i2p2www/pages/site/about/media.html:100
+msgid "Tutorials"
+msgstr "Guider"
+
+#: 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 ""
+"I2P Windows Guide\n"
+"(Youtube Video)\n"
+"Denhär guiden kommer visa dig hur man installerar I2P i Windows XP.\n"
+"Av Telecomix"
+
+#: 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 ""
+"I2P Debian Guide\n"
+"(Youtube Video)\n"
+"Denhär guiden kommer visa dig hur man installerar I2P på ett Debian Linux"
+" System.\n"
+"Av Telecomix"
+
+#: 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 ""
+"Hur du sätter igång en anonym sajt i I2P\n"
+"(Youtube Video)\n"
+"Hur du sätter igång en anonym sajt i I2P.\n"
+"Av Telecomix"
+
+#: 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 ""
+"I2P Tutorial Mac OS X\n"
+"(Youtube Video)\n"
+"En guide om hur man kör I2P på Mac OS X och hur man ansluter till "
+"irc.telecomix.i2p.\n"
+"Av Telecomix"
+
+#: 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 ""
+"Felix Atari förklarar de grundläggande principerna i"
+" I2P\n"
+"(Youtube Video)\n"
+"Agent Felix Atari från Telecomix Crypto Munitions Bureau.\n"
+"Av Telecomix"
+
+#: 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 ""
+"How kommer in i I2P, det anonyma P2P Darknet:et "
+"(Windows Installation)\n"
+"(Youtube Video)\n"
+"Denhär guiden visar du du installerar och konfigurerar mjukvaran som "
+"behövs för att komma åt I2P."
+
+#: 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 ""
+"Hur du ansluter till I2P\n"
+"(Youtube Video)\n"
+"Hur du installerar I2P på Ubuntu."
+
+#: 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 ""
+"Installera I2P darknet mjukvara i Linux\n"
+"(Video)\n"
+"Adrian Crenshar.\n"
+"Januari 2011"
+
+#: i2p2www/pages/site/about/media.html:159
+#, python-format
+msgid ""
+"Short garlic routing animation\n"
+"(Youtube Video)\n"
+"Adrian Crenshaw.\n"
+msgstr ""
+"Kort garlic-routing animation\n"
+"(Youtube Video)\n"
+"Adrian Cranshar.\n"
+
+#: i2p2www/pages/site/about/media.html:167
+msgid "Articles and Interviews"
+msgstr "Artiklar och Intervjuer"
+
+#: 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 ""
+"0x90 Intervjuad av DistributedCity\n"
+"Del 1\n"
+"Del 2\n"
+"Juli 26, 2002."
+
+#: 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 ""
+"0x90 Intervjuad av El Pais\n"
+"(orginal i Spanska)\n"
+"Engelsk översättning\n"
+"Oktober 31, 2002"
+
+#: i2p2www/pages/site/about/media.html:185
+#, python-format
+msgid ""
+"2003 Business Week article referencing "
+"invisiblenet"
+msgstr ""
+"2003 Business Week artikel som refererar till "
+"invisiblenet"
+
+#: 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 ""
+"Netzwelt.de artikel om att vara anonym på "
+"internet\n"
+"(Tyska)\n"
+"November 2007."
+
+#: i2p2www/pages/site/about/media.html:195
+#, python-format
+msgid ""
+"zzz interviewed by gulli.com\n"
+"March 2009\n"
+"German translation"
+msgstr ""
+"zzz intervjuades av gulli.com\n"
+"Mars 2009\n"
+"Tysk översättning"
+
+#: 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 ""
+"zzz intervjuades på InfoSec Daily Podcast:en Avsnitt "
+"454 (mp3)\n"
+"Augusti 18, 2011"
+
+#: i2p2www/pages/site/about/media.html:207
+#, python-format
+msgid ""
+"I2P - Anonymity for the Masses,\n"
+"Jonathan Cox,\n"
+"November 11, 2011."
+msgstr ""
+"I2P - Anonymitet för Massorna,\n"
+"Jonathan Cox,\n"
+"November 11, 2011."
+
+#: 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 ""
+"zzz och Lance James intervjuades på InfoSec Daily "
+"Podcast:en Avsnitt 596 (mp3)\n"
+"Februari 16, 2012"
+
+#: i2p2www/pages/site/about/team.html:2
+msgid "Team"
+msgstr "Lag"
+
+#: i2p2www/pages/site/about/team.html:4
+msgid "I2P Project Members"
+msgstr "I2P Projekt Medlemmar"
+
+#: 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 ""
+"Vi är en liten grupp av personer spridda runt om flera kontinenter, som "
+"arbetar för att\n"
+"förbättra olika aspekter av projektet och diskutera designen av\n"
+"nätverket.\n"
+"Hjälp till!"
+
+#: i2p2www/pages/site/about/team.html:14
+msgid "Admin"
+msgstr "Admin"
+
+#: i2p2www/pages/site/about/team.html:15
+msgid "Project Manager"
+msgstr "Projekthanterare"
+
+#: i2p2www/pages/site/about/team.html:17
+msgid "point of contact of last resort"
+msgstr "kontaktpunkt som sista utväg"
+
+#: i2p2www/pages/site/about/team.html:20
+msgid "Treasurer"
+msgstr "Bankör"
+
+#: i2p2www/pages/site/about/team.html:22
+msgid "manage donations / accounts / bounties"
+msgstr "hantera donationer / konton / belöningar"
+
+#: i2p2www/pages/site/about/team.html:25
+msgid "PR manager"
+msgstr "PR-hanterare"
+
+#: i2p2www/pages/site/about/team.html:27
+msgid "press contact, manages public relations and affairs"
+msgstr "presskontakt, hanterar publika relationer"
+
+#: i2p2www/pages/site/about/team.html:30
+#, python-format
+msgid "Forum admin"
+msgstr "Forum admin"
+
+#: i2p2www/pages/site/about/team.html:32
+msgid "manage the public user forum"
+msgstr "hantera det publika användarforumet"
+
+#: i2p2www/pages/site/about/team.html:35
+msgid "Mirrors admin"
+msgstr "Spegel admin"
+
+#: i2p2www/pages/site/about/team.html:37
+msgid "manage the project mirrors"
+msgstr "hantera projekt-speglarna"
+
+#: i2p2www/pages/site/about/team.html:40
+#, python-format
+msgid "Monotone guru"
+msgstr "Monotone guru"
+
+#: i2p2www/pages/site/about/team.html:42
+msgid "manage the public monotone repositories"
+msgstr "hantera de publika monotone repositorierna"
+
+#: i2p2www/pages/site/about/team.html:45
+msgid "Packager; Linux"
+msgstr "Packeterare, Linux"
+
+#: i2p2www/pages/site/about/team.html:47
+msgid "Linux (Debian/Ubuntu) distribution packager"
+msgstr "Linux (Debian/Ubuntu) distrubutions packeterare"
+
+#: i2p2www/pages/site/about/team.html:50
+msgid "Packager; Windows"
+msgstr "Packeterare, Windows"
+
+#: i2p2www/pages/site/about/team.html:52
+msgid "Windows installer packager"
+msgstr "Paketerare för Windows installerare"
+
+#: i2p2www/pages/site/about/team.html:55
+msgid "Release Manager"
+msgstr "Releaserhanterare"
+
+#: i2p2www/pages/site/about/team.html:57
+msgid "Builds and signs the releases"
+msgstr "Bygger och signerar releaser"
+
+#: i2p2www/pages/site/about/team.html:60
+msgid "Update admin"
+msgstr "Uppdaterings admin"
+
+#: i2p2www/pages/site/about/team.html:62
+msgid "Monitors and recruits in-network update hosts"
+msgstr "Övervakar och rekryterar uppdateringsvärdar inuti nätverket"
+
+#: i2p2www/pages/site/about/team.html:65
+msgid "Reseed admin"
+msgstr "Reseed admin"
+
+#: i2p2www/pages/site/about/team.html:67
+msgid "Monitors, advises and recruits reseed hosts"
+msgstr "Övervakare, rådgör och rekryterar reseedvärdar"
+
+#: i2p2www/pages/site/about/team.html:70
+msgid "Security expert"
+msgstr "Säkerhetsexpert"
+
+#: 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 "ledig"
+
+#: i2p2www/pages/site/about/team.html:72
+msgid "threat model / crypto expert"
+msgstr "hotbild / kryptoexpert"
+
+#: i2p2www/pages/site/about/team.html:77
+#, fuzzy
+msgid "Manage the project bug tracker"
+msgstr "hantera projekt-speglarna"
+
+#: i2p2www/pages/site/about/team.html:80
+#, fuzzy
+msgid "Translation admins"
+msgstr "översättning till Franska"
+
+#: i2p2www/pages/site/about/team.html:85
+msgid "User Advocate"
+msgstr "Användares förespråkare"
+
+#: i2p2www/pages/site/about/team.html:87
+msgid "gather, prioritize, advocate for user needs"
+msgstr "samla, prioritera, förespråkare för användarbehov"
+
+#: i2p2www/pages/site/about/team.html:90
+msgid "Web Designer"
+msgstr "Webbdesigner"
+
+#: i2p2www/pages/site/about/team.html:92
+msgid "manage the public project website content design"
+msgstr "hantera den publika projektetwebbsidabs design"
+
+#: i2p2www/pages/site/about/team.html:95
+#, python-format
+msgid "Webserver admin"
+msgstr "Webbserver admin"
+
+#: i2p2www/pages/site/about/team.html:97
+msgid "manage the public project webservers"
+msgstr "hantera det publika projektets webbserver"
+
+#: i2p2www/pages/site/about/team.html:100
+#, python-format
+msgid "Website admin"
+msgstr "Webbsida admin"
+
+#: i2p2www/pages/site/about/team.html:102
+msgid "manage the public project website content"
+msgstr "hantera den publika projekt-webbsidans innehåll"
+
+#: i2p2www/pages/site/about/team.html:105
+msgid "News Admin"
+msgstr "Nyhetsadmin"
+
+#: i2p2www/pages/site/about/team.html:107
+msgid "manage router console news feed"
+msgstr "hantera routerkonsolens nyhetsflöde"
+
+#: i2p2www/pages/site/about/team.html:110
+msgid "Director of passion"
+msgstr "Direktör för passion"
+
+#: i2p2www/pages/site/about/team.html:112
+msgid "community motivator"
+msgstr "community motiverare"
+
+#: i2p2www/pages/site/about/team.html:116
+msgid "Dev"
+msgstr "Utvecklare"
+
+#: i2p2www/pages/site/about/team.html:117
+msgid "Core Lead"
+msgstr "Kärn ledare"
+
+#: i2p2www/pages/site/about/team.html:119
+msgid "lead dev for the SDK and router"
+msgstr "ledare utvecklare för SDK och router"
+
+#: i2p2www/pages/site/about/team.html:122
+#, python-format
+msgid "I2P mail lead"
+msgstr "I2P e-post ledare"
+
+#: i2p2www/pages/site/about/team.html:124
+msgid "organize and develop the i2p mail system"
+msgstr "organisera och utveckla e-post systemet för I2P"
+
+#: i2p2www/pages/site/about/team.html:127
+#, python-format
+msgid "I2Host lead"
+msgstr "I2Host ledare"
+
+#: i2p2www/pages/site/about/team.html:129
+msgid "I2Host addressbook application"
+msgstr "I2Host adressboks applikation"
+
+#: i2p2www/pages/site/about/team.html:132
+#, python-format
+msgid "BOB lead"
+msgstr "BOB ledare"
+
+#: i2p2www/pages/site/about/team.html:134
+msgid "Basic Open Bridge"
+msgstr "Basic Open Bridge"
+
+#: i2p2www/pages/site/about/team.html:137
+#, python-format
+msgid "I2P-Bote lead"
+msgstr "I2P-Bote ledare"
+
+#: i2p2www/pages/site/about/team.html:139
+msgid "I2PBote plugin"
+msgstr "I2PBote plugin"
+
+#: i2p2www/pages/site/about/team.html:142
+#, python-format
+msgid "Robert lead"
+msgstr "Robert ledare"
+
+#: i2p2www/pages/site/about/team.html:144
+msgid "Robert BitTorrent client"
+msgstr "Robert BitTorrent klient"
+
+#: i2p2www/pages/site/about/team.html:147
+#, python-format
+msgid "I2Phex lead"
+msgstr "I2Phex ledare"
+
+#: i2p2www/pages/site/about/team.html:149
+msgid "I2Phex Gnutella client"
+msgstr "I2Phex Gnutella klient"
+
+#: i2p2www/pages/site/about/team.html:152
+#, python-format
+msgid "I2PSnark lead"
+msgstr "I2PSnark ledare"
+
+#: i2p2www/pages/site/about/team.html:154
+msgid "Maintains the integrated Bittorrent client"
+msgstr "Underhåller den integrerade BitTorrent klienten"
+
+#: i2p2www/pages/site/about/team.html:157
+#, python-format
+msgid "iMule lead"
+msgstr "iMule ledare"
+
+#: i2p2www/pages/site/about/team.html:159
+msgid "eMule client over I2P"
+msgstr "eMule klient över I2P"
+
+#: i2p2www/pages/site/about/team.html:162
+#, python-format
+msgid "Syndie lead"
+msgstr "Syndie ledare"
+
+#: i2p2www/pages/site/about/team.html:164
+msgid "Syndie development"
+msgstr "Syndie utveckling"
+
+#: i2p2www/pages/site/about/team.html:167
+msgid "Susimail lead"
+msgstr "Susimail ledare"
+
+#: i2p2www/pages/site/about/team.html:169
+msgid "Susimail development"
+msgstr "Susimail utveckling"
+
+#: i2p2www/pages/site/about/team.html:172
+msgid "Console"
+msgstr "Konsol"
+
+#: i2p2www/pages/site/about/team.html:174
+msgid "Router console HTML/CSS design"
+msgstr "Routerkonsol HTML/CSS design"
+
+#: i2p2www/pages/site/about/team.html:177
+msgid "SAM"
+msgstr "SAM"
+
+#: i2p2www/pages/site/about/team.html:179
+msgid "SAM maintainer"
+msgstr "SAM underhållare"
+
+#: i2p2www/pages/site/about/team.html:182
+msgid "I2PCPP lead"
+msgstr "I2PCP ledare"
+
+#: i2p2www/pages/site/about/team.html:184
+msgid "C++ Router"
+msgstr "C++ Router"
+
+#: 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 "Bidragare"
+
+#: i2p2www/pages/site/about/team.html:195
+msgid "fire2pe dev, console enhancements"
+msgstr "fire2pe utvecklare, konsolförbättringar"
+
+#: i2p2www/pages/site/about/team.html:199
+msgid "desktopgui, dijjer port"
+msgstr "desktopgui, dijjer port"
+
+#: i2p2www/pages/site/about/team.html:203
+msgid "Debian/Ubuntu Packager and PPA maintainer"
+msgstr "Debian/Ubuntu Packeterare och PPA underhållare"
+
+#: i2p2www/pages/site/about/team.html:207
+msgid "Routerconsole backend and UI work, website revamp, unit tests work"
+msgstr ""
+"Routerkonsol backend och UI arbete, webbsajt omskrivning, "
+"enhetstestsarbete"
+
+#: i2p2www/pages/site/about/team.html:212
+msgid "Help needed on many fronts!"
+msgstr "Hjälp behövs på många fronter!"
+
+#: i2p2www/pages/site/about/team.html:216
+msgid "Past contributors"
+msgstr "Föredetta bidragare"
+
+#: i2p2www/pages/site/about/team.html:218
+msgid "I2PTunnel development, ministreaming library"
+msgstr "I2PTunnel utveckling, ministreaming biblioteket"
+
+#: i2p2www/pages/site/about/team.html:222
+msgid "Project lead, Syndie lead"
+msgstr "Projektledare, Syndie ledare"
+
+#: i2p2www/pages/site/about/team.html:226
+msgid "Project lead, Syndie lead, I2Phex, support guru"
+msgstr "Projektledare, Syndie ledare, I2Phex, support guru"
+
+#: i2p2www/pages/site/about/team.html:230
+msgid "iMule lead"
+msgstr "iMule ledare"
+
+#: 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 "I2Phex arbete"
+
+#: i2p2www/pages/site/about/team.html:246
+msgid "Python SAM library, attack simulations"
+msgstr "Python SAM bibliotek, attacksimuleringar"
+
+#: i2p2www/pages/site/about/team.html:250
+msgid "i2pmail development"
+msgstr "i2pmail utveckling"
+
+#: i2p2www/pages/site/about/team.html:254
+msgid "Syndie help"
+msgstr "Syndie hjälp"
+
+#: i2p2www/pages/site/about/team.html:258
+msgid "i2p mail,susimail and susidns apps"
+msgstr "i2pmail, susimail och susidns appar"
+
+#: i2p2www/pages/site/about/team.html:262
+msgid "I2Phex (port of Phex to I2P)"
+msgstr "I2Phex (port av Phex till I2P)"
+
+#: i2p2www/pages/site/about/team.html:266
+msgid "addressbook,i2p-bt,syndie client"
+msgstr "adressbok, i2p-bt, syndie klient"
+
+#: i2p2www/pages/site/about/team.html:270
+msgid "organize and develop the i2p-bt BitTorrent port"
+msgstr "organisera och utveckla i2p-bt BitTorrent porten"
+
+#: i2p2www/pages/site/about/team.html:274
+msgid "addressbook, i2p-bt, syndie client development"
+msgstr "adressbok, i2p-bt, syndie klient utveckling"
+
+#: i2p2www/pages/site/about/team.html:278
+msgid "encryption and signature routines, I2PIM"
+msgstr "kryptering och signerings rutiner, I2PIM"
+
+#: i2p2www/pages/site/about/team.html:282
+msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)"
+msgstr "SAM jyrhon kod, arbete på stasher (DHT) oxh v2v (VoI2P)"
+
+#: i2p2www/pages/site/about/team.html:286
+msgid "installer, systray, bogobot"
+msgstr "installerare, systray, bogobot"
+
+#: i2p2www/pages/site/about/team.html:290
+msgid "jbigi development, wiki migration, doc cleanup"
+msgstr "jbigi utveckling, wiki-migration, dokum. rensning"
+
+#: i2p2www/pages/site/about/team.html:294
+msgid "java debugging and client development on I2PTunnel and the router console"
+msgstr "java debugging och klient-utveckling för I2PTunnel och routerkonsolen"
+
+#: i2p2www/pages/site/about/team.html:298
+msgid "SAM perl module"
+msgstr "SAM perl modul"
+
+#: i2p2www/pages/site/about/team.html:302
+msgid "i2psnark work"
+msgstr "i2psnark arbete"
+
+#: i2p2www/pages/site/about/team.html:306
+msgid "java cleanup"
+msgstr "java rensning"
+
+#: i2p2www/pages/site/about/team.html:310
+msgid "docs. wiki migration"
+msgstr "dokum. wiki-migration"
+
+#: i2p2www/pages/site/about/team.html:314
+msgid "translations into French"
+msgstr "översättning till Franska"
+
+#: i2p2www/pages/site/about/team.html:318
+msgid "C port of jcpuid"
+msgstr "C port av jcpuid"
+
+#: i2p2www/pages/site/about/team.html:322
+msgid "C# SAM library, pants, fortuna integration"
+msgstr "C# SAM bibliotek, pants, fortuna integration"
+
+#: i2p2www/pages/site/about/team.html:326
+msgid "libSAM"
+msgstr "libSAM"
+
+#: i2p2www/pages/site/about/team.html:330
+#: i2p2www/pages/site/about/team.html:334
+msgid "i2p-bt tracker development"
+msgstr "i2p-bt tracker utveckling"
+
+#: i2p2www/pages/site/about/team.html:338
+msgid "Console and website themes"
+msgstr "Konsol och webbsajts tema"
+
+#: i2p2www/pages/site/about/team.html:368
+msgid "… and many others"
+msgstr "… och många andra"
+
+#: i2p2www/pages/site/about/performance/future.html:2
+msgid "Future Performance Improvements"
+msgstr "Framtida Prestanda Förbättringar"
+
+#: i2p2www/pages/site/about/performance/future.html:4
+msgid "August 2010"
+msgstr "Augusti 2010"
+
+#: 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 ""
+"Det finns flera viktiga tekniker som kan utföras för att förbättra den "
+"uppfattade\n"
+"prestandan av I2P - vissa av de följande är CPU-relaterade, andra "
+"bandbredds-relaterade \n"
+"och andra är protokoll-relaterade. Dock, så påverkar alla de aspekterna "
+"fördröjning, kapacitet och  uppfattad prestanda av nätverket, eftersom de"
+" minskar kampen om otillräckliga resurser. Denna listan är naturligtvis"
+" \n"
+"inte komplett, men den täcker de viktigaste som tekniker ses."
+
+#: 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 ""
+"För tidigare prestandaförbättringar se Prestanda "
+"Historiken."
+
+#: i2p2www/pages/site/about/performance/future.html:20
+msgid "Better peer profiling and selection"
+msgstr "Bättre peer profilering och urval"
+
+#: 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 ""
+"Troligvis kommer en av de viktigaste delarna för att få bättre prestanda"
+" \n"
+"vara att förbättra hur routrar väljer de peers som de bygger sina tunnlar"
+" igenom\n"
+" - genom att övertyga sig om att de inte använder peers med långsamma "
+"uppkopplingar eller sådana med snabba uppkopplingar men som är "
+"överbelastade, t.ex. Utöver det, så måste vi vara säkra på att vi inte "
+"utsätter oss själva för en Sybil attack från"
+" en kraftfull motståndare med massor av snabba maskiner."
+
+#: i2p2www/pages/site/about/performance/future.html:30
+msgid "Network database tuning"
+msgstr "Inställning av nätverksdatas"
+
+#: 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 ""
+"Vi kommer vilja vara mer effektiva med nätverksdatabasens läkande \n"
+"och underhållande algoritmer - istället för att konstant utforska "
+"nyckelrymden efter nya\n"
+"peers - som orsakar ett stort antal nätverksmeddelanden och "
+"routerbelastning - vi\n"
+"kan sakta ner eller till och med stanna utforskningen tills vi finner "
+"något nytt\n"
+"värt att hitta (t.ex minska utforskningshastigheten baserat på den "
+"senaste gången någon\n"
+"gav oss en referens till någon vi aldrig hört talas om). Vi kan också "
+"göra några\n"
+"inställningar för vad vi faktiskt skickar - hur många peers vi skickar "
+"tillbaka (eller till och med om vi\n"
+"skickar tillbaka ett svar), såväl som hur många samtidiga sökningar vi "
+"utför."
+
+#: i2p2www/pages/site/about/performance/future.html:42
+msgid "Session Tag Tuning and Improvements"
+msgstr "Session Tag Inställning och Förbättring"
+
+#: 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 ""
+"Sättet ElGamal/AES+SessionTag algoritmen\n"
+"fungerar är genom att hantera ett set av slumpmässiga engångsanvändnings "
+"32 bytes arrayer, och att låta deras tidsgiltighet rinna ut om dom inte "
+"används snabbt nog. Om vi låter deras tidsgiltighet rinna ut för snabbt "
+"så faller vi tillbaka till en full (dyr) ElGamal kryptering, men om vi "
+"inte låter deras tidsfrist rinna ut snabbt nog, så måste vi reducera "
+"deras kvantitet så att vi inte tar slut på minne (och om mottagaren på "
+"något vis blir korrupt och förlorar några\n"
+"taggar, så kan ännu fler krypteringsfel inträffa innan det hittas). Med "
+"lite\n"
+"mer aktiv diagnosticering och responsdrivna algoritmer, så kan vi säker "
+"och mer\n"
+"effektivt ställa in lifstiden av taggarna, som ersätter ElGamal-"
+"krypteringen med\n"
+"en enkel AES operation."
+
+#: 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 ""
+"Fler idéer för att förbättra Session Tag utdelningen beskrivs på\n"
+"ElGamal/AES+SessionTag sidan."
+
+#: i2p2www/pages/site/about/performance/future.html:61
+msgid "Migrate sessionTag to synchronized PRNG"
+msgstr "Migrera sessionTag till synkroniserad PRNG"
+
+#: 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 ""
+"Just nu, så fungerar vår ElGamal/AES+SessionTag\n"
+"algoritm genom att tagga varje krypterat meddelande med ett unikt "
+"slumpmässigt\n"
+"32 bytes nonce (en \"session tag\"), som identifierar att meddelandet "
+"krypteras med den associerade AES sessions nyckeln. Detta hindrar peers "
+"från att utskilja meddelanden som är en del av samma session, eftersom "
+"varje meddelande har en helt ny slumpmässig tag. För att uppnå detta, "
+"måste ett nytt set av sessionstaggar skickas med ett meddelandet efter "
+"några få meddelanden, vilket transparent utdelar ett sätt att identifiera"
+" framtida meddelanden. Vi måste sedan hålla koll\n"
+"på vilka meddelanden som lyckats skickas så vi vet vilka taggar vi kan "
+"använda."
+
+#: 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 ""
+"Detta fungerar utmärkt och är tämligen robust, däremot är det ineffektivt"
+" i frågan om bandbreddsanvändning, eftersom det kräver att taggarna "
+"mottages i förväg (och alla taggar behövs kanske inte, vissa är onödiga, "
+"p.g.a. tidsbegränsningar). I det genomsnittliga fallet, kostar det 32 "
+"bytes (storleken av en tagg) att förleverera sessionstaggar per "
+"meddelande. Som Taral föreslog så, kan den storleken undvikas denom att "
+"ersätta skickande av taggarna med en synkroniserad PRNG - när en ny "
+"session etableras (genom ett ElGamal-krypterat block), båda sidorna "
+"seedar ett PRNG som används för att generera sessions taggarna på begäran"
+" (med mottagaren förberäknar de nästkommande möjliga värdna för att "
+"hantera mottagning i annan ordning)."
+
+#: i2p2www/pages/site/about/performance/future.html:87
+msgid "Longer lasting tunnels"
+msgstr "Tunnlar som varar längre"
+
+#: 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 ""
+"Standard-varaktigheten för tunnlar som är 10 minuter är ganska "
+"slumpmässig, men\n"
+"den \"känns okej\". Efter vi har tunnel-reparations kod och mer effektiv "
+"fel\n"
+"detektion, så kommer vi på ett säkrare vis kunna variera de "
+"varaktigheterna och reducera nätverks och CPU-belastning (från dyra "
+"tunnel-byggar meddelande)."
+
+#: 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 ""
+"Detta verkar vara en enkel lösning för hög belastning på routrar med "
+"mycket bandbredd, men\n"
+"vi borde inte använda den utvägen innan vi ställt int algoritmerna för "
+"att bygga tunnlar vidare.\n"
+"Dock, så är livstiden för tunnlar, 10 minuter,  hårdkodad på ett antal "
+"platset, så en stor ansträngning hade krävts för att ändra livstident. "
+"Det hade också varit svårt att bibehålla bakåtkompabilitet med en sådan "
+"förändring."
+
+#: 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 ""
+"Eftersom nätverkets genomsnittliga sannolikthet att lyckas bygga en "
+"tunnel för närvarande är ganska hög,\n"
+"så finns det för tillfället inga planer att förlänga tunnlars livstid."
+
+#: i2p2www/pages/site/about/performance/future.html:108
+msgid "Adjust the timeouts"
+msgstr "Justera timeouterna"
+
+#: 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 ""
+"Ytterligare en av det ganska slumpmässiga sakerna som \"känns okej\" som "
+"vi har är\n"
+"de nuvarande timeouterna för olika aktiviteter. Varför har vi en 60 "
+"sekunders \"onåbar peer\" timeout? Varför försöket vi skicka genom en "
+"annan tunnel som ett LeaseSet annonserar efter 10 sekunder? Varför är "
+"nätverksdatabas förfrågningar begränsade mellan 60 och 20 sekunders "
+"gränser? Varför är mål inställda att fråga efter ett nytt set av tunnlar "
+"var 10:de minute? Varför väntar vi upp till 60 sekunder efter ett svar "
+"från en peer efter vi begärt att dom går med i en tunnel? Varför tycker "
+"vi att en tunnel som inte går igenom våra test inom 60 sekunder är "
+"\"död\"?"
+
+#: 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 ""
+"Var och en av dessa tankeställare kan lösas med mer adaptiv kod, men även"
+"\n"
+"med inställningsbara parametrear för att tillåta mer lämpliga utbyten "
+"mellan bandbredd, fördröjning och CPU-användning."
+
+#: i2p2www/pages/site/about/performance/future.html:125
+msgid "Full streaming protocol improvements"
+msgstr "Förbättringar i det fulla streaming protokollet"
+
+#: 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 ""
+"Kanske återaktivera den interaktiva stream progilen (den \n"
+"nuvarande implementationen använder bara bulk stream profilen)."
+
+#: 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 ""
+"Begränsningar av klient-nivå bandbredd (i antingen eller båda "
+"riktningarna av en stream, eller möjligtvis delat över flera streams). "
+"Detta skulle vara utöver routerns generella bandbredds-begränsningar, så "
+"klart."
+
+#: i2p2www/pages/site/about/performance/future.html:141
+msgid ""
+"Access control lists (only allowing streams to or from certain other "
+"known \n"
+"destinations)."
+msgstr ""
+"Tillgångs kontroll-listor (bara tillåta streams till eller från vissa "
+"andra kända \n"
+"mål)."
+
+#: 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 ""
+"Webbkontroller och övervakning av hälsan av de olika streamarna, men även"
+" möjligheten att explicit stänga eller begränsa dom."
+
+#: 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 ""
+"Ytterligare idéer för att förbättra streaming biblioteket är beskrivna på"
+" \n"
+"streaming biobliotekets sida."
+
+#: i2p2www/pages/site/about/performance/history.html:2
+msgid "Performance History"
+msgstr "Prestanda Historik"
+
+#: 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 ""
+"Bemärkningsvärda prestandaförbättringar har gjorts genom att använda "
+"teknikerna nedan.\n"
+"Det finns mer att göra, se Prestanda "
+"sidan\n"
+"för nuvarande problem och tankar."
+
+#: i2p2www/pages/site/about/performance/history.html:10
+msgid "Native math"
+msgstr "Native matte"
+
+#: 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 "implementerad"
+
+#: 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 ""
+"När jag senast profilerade I2P koden, så spenderades majoriteten av tiden"
+" inom en funktion i java.math.BigInteger,\n"
+"modPow.\n"
+"Hellre än att försöka finjustera denna metod, så kallar vi ut till\n"
+"GNU MP - ett galet snabbt matte-bibliotek\n"
+"(med finjusterad assembler för många arkitekturer). (Redaktör: se\n"
+"NativeBigInteger för snabbare asymmetrisk "
+"kryptografi)"
+
+#: 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 "Garlic inpackning av \"svars\" LeaseSet"
+
+#: i2p2www/pages/site/about/performance/history.html:33
+msgid "implemented but needs tuning"
+msgstr "implementerad men behöver finjustering"
+
+#: 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 ""
+"Denna algoritm-finjustering kommer bara vara relevant för applikationer "
+"som vill att deras\n"
+"peers ska svara dom (men det inkluderar allting som använder I2PTunnel "
+"eller mihis ministreaming bibliotek):"
+
+#: 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 ""
+"Tidigare, när Alice skickade Bob ett meddelande, när Bob svarade var han "
+"tvungen att göra ett uppslag i nätverksdatabasen - genom att skicka ut "
+"några förfrågningar för att få Alices nuvarande LeaseSet. Om han redan "
+"har Alices nuvarande LeaseSet, så kan han istället bara skicka sitt svar "
+"direkt - detta är (en del av) varför det typiskt tar\n"
+"lite längre tid att prata med någon första gången du ansluter, men "
+"efterföljande kommunikation är snabbare. För nuvarande - för alla "
+"klienter - packar vi in avsändarens nuvarande LeasSet i garlic:en som "
+"skickas till mottagaren, så att när dom svarar, så kommer dom "
+"alltid ha ett LeaseSet sparat lokalt - vilket totalt förebygger "
+"alla behov av förfrågningar till nätverksdatabasen vid svar.\n"
+"Detta byter bort en stor del av avsändarens bandbredd för ett snabbare "
+"svar.\n"
+"Om vi inte gjorde detta ofta,\n"
+"så hade den genomsnittliga nätverksbandbredd minska, eftersom mottagaren "
+"inte måste göra förfrågningen mot nätverksdatabasen."
+
+#: 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 ""
+"Förändringar som är planerade för release 0.6.2 kommer skicka med "
+"LeaseSet bara när det behövs, vid början av en anslutning eller när "
+"LeaseSet:et förändras.\n"
+"Detta kommer rejält minska den totala overheaden av I2P meddelanden."
+
+#: i2p2www/pages/site/about/performance/history.html:66
+msgid "More efficient TCP rejection"
+msgstr "Effektivare TCP avslag"
+
+#: i2p2www/pages/site/about/performance/history.html:68
+#, fuzzy
+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 ""
+"Alla TCP anslutningar gör för tillfället all sin peer validering efter\n"
+"hela det fulla (dyra) Diffie-Hellman handslaget gått igenom för att "
+"förhandla en\n"
+"privat sessionsnyckel. Detta betyder att om någons klocka är väldigt fel "
+"eller\n"
+"deras NAT/brandvägg/etc. is felaktigt inställd (eller om de bara kör en "
+"icke-kompatibel version av routern), så kommer de konsekvent (men inte\n"
+"konstant, tack vare shitlist:en) orsaka meningslösa dyra kryptografiska\n"
+"operationen på alla peers de känner till. Medan vi vill behålla en del "
+"verifikation/validering inom krypteringsgränsen, så kommer vi vilja "
+"uppdatera protokollet så att en del görs först, så att vi kan avvisa dom "
+"rent,\n"
+"utan att slösa massor av CPU-tid eller andra resurser."
+
+#: i2p2www/pages/site/about/performance/history.html:81
+msgid "Adjust the tunnel testing"
+msgstr "Justera tunneltestning"
+
+#: 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 ""
+"Istället för att använda den ganska slumpmässiga metod vi har nu, borde "
+"vi använda en\n"
+"mer kontext-medveten algoritm för att testa tunnlar. T.ex. om vi redan "
+"vet att den skickar giltig data korrekt, så finns inget behov för att "
+"testa den, men om vi inte har\n"
+"sett någon data genom den nyligen, så är det kanske meningsfullt att "
+"kasta lite data åt dess håll. Detta kommer minska tunnel tvister från "
+"överflödiga meddelanden, men även \n"
+"förbättra hastigheten med vilken vi hittar - och löser - misslyckade "
+"tunnlar."
+
+#: i2p2www/pages/site/about/performance/history.html:92
+msgid "Persistent Tunnel / Lease Selection"
+msgstr "Beständig Tunnel / Lease-val"
+
+#: 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 ""
+"Utåtgående tunnel-val implementerades i 0.6.1.30, inåtgående lease-val \n"
+"implementerades i release 0.6.2."
+
+#: 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 ""
+"Att välja tunnlar och lease slumpmässigt för varje meddelande skapare en "
+"stor \n"
+"förekomst av meddelande som kommer fram ur ordning, vilket förhindrar "
+"streaming biblioteket från \n"
+"att öka dess fönsterstorlek så mycket som det kunde gjort. Genom att "
+"bibehålla \n"
+"samma val för en given anslutning, är överföringshastigheten mycket "
+"snabbare."
+
+#: i2p2www/pages/site/about/performance/history.html:104
+msgid "Compress some data structures"
+msgstr "Komprimera vissa datastruktuerer"
+
+#: 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 ""
+"I2NP meddelanden och datan de innehåller är redan definierad i en ganska\n"
+"kompakt struktur, men en av attributerna i RouterInfo strukturen är inte "
+"- \n"
+"\"valmöjligheter\" är ett vanligt ASCII namn = värde mappningar. Just nu,"
+" fyller vi det med den publicerade statistiken - runt 3300 bytres per "
+"peer. Det är enkelt att\n"
+"implementera GZip komprimering vilket skulle minska det till 1/3 av sin "
+"storlek och när du tänker på hur ofta RouterInfo strukturer skickas över "
+"nätverket, så är det viktiga besparingar - varje gång en router frågar en"
+" annan router efter något ur nätverksdatabasen som mottagaren inte har, "
+"så skickar den tillbaka 3-10 RouterInfos till förfrågaren."
+
+#: i2p2www/pages/site/about/performance/history.html:117
+msgid "Update the ministreaming protocol"
+msgstr "Uppdatera ministreaming protokollet"
+
+#: i2p2www/pages/site/about/performance/history.html:118
+msgid "replaced by full streaming protocol"
+msgstr "ersatt av fullt streaming protokoll"
+
+#: 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 "Prestanda"
+
+#: 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 ""
+"Hur fungerar I2P, varför är det långsamt, och varför använder det inte "
+"hela min bandbredd? "
+
+#: 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/sv_SE/LC_MESSAGES/blog.po b/i2p2www/translations/sv_SE/LC_MESSAGES/blog.po
new file mode 100644
index 00000000..58756c63
--- /dev/null
+++ b/i2p2www/translations/sv_SE/LC_MESSAGES/blog.po
@@ -0,0 +1,1539 @@
+# Swedish (Sweden) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# samaire , 2013
+# hottuna , 2013
+# Martin Svensson , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-12 06:16+0000\n"
+"PO-Revision-Date: 2013-12-12 06:18+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: Swedish (Sweden) "
+"(http://www.transifex.com/projects/p/I2P/language/sv_SE/)\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/blog/2011/10/11/0.8.9-Release.rst:24
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:25
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:12
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:12
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:17
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:16
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:16
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:26
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:19
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:19
+msgid "Files are available on the `download page`_."
+msgstr "Filerna finns på `nerladdningssidan`_."
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:28
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:15
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:29
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:16
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:16
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:21
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:20
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:20
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:30
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:23
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:23
+msgid "`download page`"
+msgstr "`nerladdningssidan`"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:30
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:17
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:31
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:18
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:19
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:18
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:22
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:22
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:32
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:25
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:79
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:45
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:13
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:101
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:26
+msgid "RELEASE DETAILS"
+msgstr "RELEASE DETALJER"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:32
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:19
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:33
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:40
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:50
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:24
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:24
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:34
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:103
+msgid "Major Changes"
+msgstr "Stora Förändringar"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:44
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:24
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:43
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:55
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:47
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:58
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:43
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:32
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:30
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:39
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:81
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:54
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:112
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:34
+msgid "Bug Fixes"
+msgstr "Buggfixar"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:54
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:30
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:47
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:69
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:63
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:68
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:54
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:41
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:36
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:51
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:43
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:94
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:63
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:19
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:118
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:52
+msgid "Other"
+msgstr "Andra"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:73
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:36
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:51
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:82
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:75
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:96
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:76
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:52
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:56
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:67
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:56
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:110
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:79
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:30
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:129
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:27
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:76
+msgid "SHA256 Checksums:"
+msgstr "SHA256 Kontrollsummor:"
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39
+msgid "Major changes"
+msgstr "Stora förändringar"
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47
+msgid "Wrapper Update"
+msgstr "Wrapper Uppdatering"
+
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:23
+msgid "Update Info"
+msgstr "Uppdaderings Info"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2
+msgid "0.9.2 Release"
+msgstr "0.9.2 Release"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9
+msgid ""
+"0.9.2 includes extensive low-level changes to improve the performance and"
+" efficiency of the router. We have updated our UPnP library, to hopefully"
+" make UPnP work for more people. I2PSnark now has DHT support, but it is "
+"not yet enabled by default, as we plan to do more testing during the "
+"upcoming 0.9.3 development cycle."
+msgstr ""
+"0.9.2 inkluderar utförliga låg-nivå-förändringar för att förbättre "
+"prestandan och effektiviteten hos routern. Vi har uppdaterat vårat UPnP-"
+"bibliotek, för att förhoppningsvis få UPnP att fungera för fler personer."
+" I2PSnark har nu DHT-stöd, men det är inte påslaget som standard, då vi "
+"planerar att utföra fler tester under den komman utvecklingscukeln för "
+"0.9.3."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12
+msgid ""
+"As usual, there's also lots of bug fixes in this release, so updating is "
+"recommended."
+msgstr ""
+"Som vanligt finns även många buggfixar i den här releasen, så uppdatering"
+" rekommenderas."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26
+msgid ""
+"SSU: Fix several problems in our UDP transport, to improve efficiency and"
+" reliability for connection setup. Also improve defenses against various "
+"types of bad input."
+msgstr ""
+"SSU: Fixa flera problem i våran UDP-transport, för att förbättra "
+"effektivtet och pålitlighet för anslutnings-etablering. Förbättra även "
+"försvaret mot olika typer av dålig input."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27
+msgid ""
+"UPnP: Updated our library to fix several issues, should work for more "
+"routers now"
+msgstr ""
+"UPnP: Uppdatera vårat bibliotek för att lösa flera problem, bör fungera "
+"för fler routrar nu"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28
+msgid ""
+"Transport: Improve performance in both our TCP and UDP transports, to "
+"benefit high-bandwidth routers"
+msgstr ""
+"Transport: Förbättre prestanda för både TCP och UDP transporter för "
+"routrar med hög bandbredd."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29
+msgid ""
+"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered "
+"are now much more flexible, which should lessen protocol overhead and "
+"reduce stalls caused by dropped tags."
+msgstr ""
+"Krypto: Gränsvärdena och antalet ElGamal/AES Sessions Taggar som sänds är"
+" nu mycket mer flexibel, vilket bör förbättra protokoll-overhead och "
+"minska uppehåll som från tappade taggar."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30
+msgid ""
+"I2PSnark: Add DHT support, not yet enabled by default, will do further "
+"testing and plan to enable by default in 0.9.3."
+msgstr ""
+"I2PSnark: Lägg till DHT-stöd, ej tillsaget som standard, kommer testas "
+"mera och slås på som standard i 0.9.3."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34
+msgid ""
+"Fix various issues affecting memory usage and performance on high-"
+"bandwidth routers"
+msgstr ""
+"Fixa olika problem som påverkar minnesanvändning och prestanda för "
+"routrar med hög bandbredd"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35
+msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN"
+msgstr ""
+"Fixa problem i UDP för routrar som använder en reducerad-MTU anslutning, "
+"t.ex. VPN"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36
+msgid "Fix i2psnark bug that prevented a completion announcement to the tracker"
+msgstr ""
+"Fixa en I2PSnark-bugg som förhindrade en komplett-annonsering till "
+"trackern"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37
+msgid "Fix a lock contention problem in i2ptunnel"
+msgstr "Fixa ett lås-strids-problem i i2ptunnel"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38
+msgid "Fix some OSX installation issues"
+msgstr "Fixa några OSX installations-problem."
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39
+msgid "Remove uses of direct byte buffers that may have been leaking"
+msgstr "Ta bort användningar av direkta byte-buffrar som kan ha läckt"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43
+msgid "Reduce overhead in network messages"
+msgstr "Minska overhead i nätverks-meddelanden"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44
+msgid "Add \"universal\" theme support"
+msgstr "Lägg till \"universellt\" tema-stöd"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45
+msgid "Theme updates"
+msgstr "Tema-uppdateringar"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46
+msgid "Add a jbigi library for Raspberry Pi"
+msgstr "Lägg till jbigi-bibliotek för Raspberry Pi"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47
+msgid "New Scala unit test framework"
+msgstr "Nytt Scala enhetstests-ramverk"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48
+msgid "Translation updates for Czech, Dutch, German, and Greek"
+msgstr "Översättningsuppdateringar för Tjeckiska, Holländska, Tyska och Grekiska"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49
+msgid "Update wrapper to 3.5.15 (new installs and PPA only)"
+msgstr "Uppdatera wrapper till 3.5.15 (enbart nya installationer or PPA)"
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:77
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:127
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:74
+msgid "Update GeoIP data (new installs and PPA only)"
+msgstr "Uppdatera GeoIP data (enbart nya installationer och PPA)"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:2
+msgid "0.9.3 Release"
+msgstr "0.9.3 Release"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9
+msgid ""
+"0.9.3 includes extensive low-level changes to the queueing of messages in"
+" the router.  We implement the CoDel Active Queue Management (AQM) "
+"algorithm.  We also unify the queueing and priority mechanisms in the "
+"transports to aid diagnosis and reduce network latency.  Work continues "
+"on fixing UDP transport bugs and making UDP more resistant to attacks.  "
+"There are more changes to improve the performance of the router and "
+"reduce its memory usage.  Also, we enable i2psnark's DHT support, "
+"introduced last release, by default."
+msgstr ""
+"0.9.3 inkluderar utförliga låg-nivå förändringar vid köandet av "
+"meddelanden i routern. \n"
+"Vi implementerar CoDel Active Queue Management (AQM) algoritmen. \n"
+"Vi förenar även kö och prioritets mekanismerna i transportlagret för att "
+"underlätta diagnos och reducera nätverksfördröjningar.\n"
+"Arbete fortsätter med att korrigera buggar i UDP transportlagret och att "
+"göra UDP mer motståndskraftigt mot attacker.\n"
+"Det finns fler förändringar som förbättrar prestandan av routern och "
+"reducerar dess minnesanvändning.\n"
+"Vi slår även på i2psnarks DHT-stöd, som introducerades i förra releasen, "
+"som standard."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26
+msgid "Active Queue Management"
+msgstr "Active Queue Management"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:27
+msgid "Priority queues"
+msgstr "Prioritetsköer"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28
+msgid "I2PSnark DHT: Several bug fixes, enable by default."
+msgstr "I2PSnark DHT: Flera buggfixar, påslaget som standard."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32
+msgid ""
+"Several SSU fixes including memory leak, and better handling of routers "
+"behind firewalls that change UDP ports; additional defenses for malicious"
+" packets."
+msgstr ""
+"Flera SSU-fixar inklusive minnesläcka, bättra hantering av routrar bakom "
+"brandväggar som byter UDP-port och ytterliggare försvar mot illvilliga "
+"paket."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33
+msgid "Fix piece selection (rarest-first) bugs in i2psnark"
+msgstr "Fixa del val (ovanligaste först)  buggar i i2psnark"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34
+msgid "Fix bug causing multiple browsers to open at startup"
+msgstr "Fixa bugg som får multipla webbläsare att öppnas vid start"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38
+msgid "Improvements in caching"
+msgstr "Förbättringar i caching."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39
+msgid "Several synchronization fixes and lock contention reduction"
+msgstr "Flera synkroniserings-fixar och minskning i lås-kamp."
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40
+msgid "Major reduction in SSU buffers memory use"
+msgstr "Stor förminskning i SSU-bufferns minnesanvändning"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41
+msgid ""
+"Fix streaming connection timeout back to 1 minute, was inadvertently "
+"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was"
+" unlimited"
+msgstr ""
+"Fixa timeout för strömmande anslutningar tillbaka till 1 minut, råkades "
+"ändras till 5 minuter. Sätt i2ptunnel server timout till 5 minuter, was "
+"obegränsad"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42
+msgid "Improved defenses in i2ptunnel for \"darkloris\""
+msgstr "Förbättra försvaret mot \"darkloris\" attacker i i2ptunnel"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:43
+msgid "More validation at torrent creation in i2psnark"
+msgstr "Mera validering vid torrent-skapning i i2psnark"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44
+msgid "Several parameter changes in SSU to improve throughput"
+msgstr "Flera parameterförändringar i SSU för att förbättra genomströming"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45
+msgid ""
+"New event log for major events including restarts; show multiple restart "
+"lines on graphs"
+msgstr ""
+"Ny händelselogg för stora händelser som omstarter, visa flera "
+"omstartningslinjer på grafer"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46
+msgid "Remove duplicate messages from logs"
+msgstr "Ta bort duplicerade meddelanden från loggar"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47
+msgid "Don't respond to blocked streaming connections with a reset, just drop"
+msgstr ""
+"Svara inte på blockerade strömmande anslutningar med ett 'reset' "
+"kommando, bara släpp"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48
+msgid "Remove all uses of inefficient SimpleTimer"
+msgstr "Ta bort alla användningar av den ineffektiva SimpleTimer"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49
+msgid "More checks for valid IPs and ports entered in console"
+msgstr "Flera kontroller för giltiga IP-adresser och portar inskrivna i konsollen"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50
+msgid "Fix bug that wasted a lot of entropy"
+msgstr "Fixa en bugg som slösade mycket entropi"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51
+msgid "Translation updates: Italian, Portuguese, Spanish, Swedish"
+msgstr "Översättningsuppdateringar: Italienska, Portugisiska, Spanska, Svenska"
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52
+msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5"
+msgstr "La till icke-NIO konfiguration i jetty.xml, rekommenderas för Java 5"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2
+msgid "0.9.4 Release"
+msgstr "0.9.4 Release"
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9
+msgid ""
+"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, "
+"that was reducing network performance and reliability. It also includes "
+"major changes in the in-network update system, and adds the capability to"
+" update via in-network torrents."
+msgstr ""
+"0.9.4 inkluderar en fix för en nätverks-kapacitets-bugg introducerad i "
+"0.9.2, som reducerade nätverksprestanda och tillfölitlighet. Stora "
+"förändingar i det interna uppdateringssystemet och lägger till stöd för "
+"att uppdatera via intena torrents."
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13
+msgid ""
+"We fixed several bugs in the i2psnark DHT implementation that was "
+"introduced\n"
+"last release. For those of you using console or http proxy passwords,\n"
+"we converted to the more-secure digest method and improved the security "
+"for console forms."
+msgstr ""
+"Vi har åtgärdat flera buggar i i2psnark DHT implementationen introducerad"
+"\n"
+"i senaste releasen. För er som använder kommandotolken eller http proxy "
+"lösenord,\n"
+"har vi konverterat till en säkrare digest-metod och förbättrat säkerheten"
+" för konsolapplikationer. "
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19
+msgid ""
+"For those of you already running development builds, your router should "
+"automatically\n"
+"update to 0.9.4-0 using the new in-network torrent facility.\n"
+"For those running 0.9.3-0, you will update normally using in-network "
+"HTTP, and\n"
+"we will have more information for you when we release 0.9.5."
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36
+msgid ""
+"Big rework of the update system; Preliminary support for updates via "
+"i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37
+msgid "Add per-destination outbound priorities"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41
+msgid ""
+"Fix major bug that reduced SSU connection limits which reduced tunnel "
+"build success rates"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42
+msgid "Fix bug with external I2CP that prevented some external apps from working"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43
+msgid "Fixed several bugs in i2psnark DHT"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44
+msgid "Fixed bug in i2psnark PEX that inflated peer counts"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45
+msgid "Handle dropped I2CP messages better"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46
+msgid "Reduce overhead of I2CP messages"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47
+msgid "Enforce max size in transport outbound message queues"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48
+msgid "Fixes for Windows eepget.bat (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49
+msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53
+msgid ""
+"More performance improvements, memory reduction, and object churn "
+"reduction"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54
+msgid "Better detection of network disconnections"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55
+msgid "Further improvements in the SSU transport"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56
+msgid "Add console password form"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57
+msgid ""
+"Convert http proxy and console from basic to digest authentication for "
+"added security"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58
+msgid ""
+"Improved verification of console form submissions, using jsp sessions. "
+"Cookies may now be required on forms, except when the console password is"
+" enabled"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59
+msgid ""
+"Initial work on new interfaces to manage applications started via "
+"clients.config"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60
+msgid "Increase minimum peer port to 1024"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61
+msgid "Increase granularity of bandwidth limiter for smoother transmissions"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62
+msgid ""
+"Translation updates: Chinese, French, German, Italian, Polish, "
+"Portuguese, Swedish, and Ukrainian"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64
+msgid "Update wrapper to 3.5.16 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65
+msgid "New ARMv6 wrapper for Raspberry Pi"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:2
+msgid "0.9.5 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9
+msgid ""
+"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities"
+" that are being investigated by researchers at UCSB. We continue to work "
+"with them on additional improvements. This is a good opportunity to "
+"remind the community that while our network continues to grow rapidly, it"
+" is still relatively small. There may be multiple weaknesses or bugs that"
+" could compromise your anonymity. Help us grow the network by spreading "
+"the word and contributing where you can."
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13
+#, python-format
+msgid ""
+"In this upgrade cycle, a random 1% of routers, (plus all routers running "
+"a\n"
+"development build) will attempt to update via the experimental in-network"
+" bittorrent\n"
+"with i2psnark. If this doesn't work, it should fall back to standard in-"
+"network HTTP update."
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27
+msgid "Defenses and Bug Fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29
+msgid "Fix router bug causing lockup when using iMule"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30
+msgid "Recognize, handle, reject duplicate tunnel IDs"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31
+msgid "Fix changing of the log file name"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32
+msgid "Prevent hashcode attack in session tags"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33
+msgid "Add build request throttler based on previous hop"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34
+msgid "Limit concurrent next-hop lookups"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35
+msgid "Catch exceptions storing nonces in console"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36
+msgid "Fix saving graph settings in console"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37
+msgid "Fix eepget generation of URLs when not proxied"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38
+msgid ""
+"Encrypt database lookup messages end-to-end when sent through exploratory"
+" tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39
+msgid "Don't use multiple floodfills from the same /16 in a query"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40
+msgid "Randomize delay before verifying floodfill store"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41
+msgid "Increase number of floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:45
+msgid "Improve support for mobile browsers"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46
+msgid "Partial defenses for UCSB attacks"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47
+msgid "Add announce list support to i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48
+msgid "Jetty: upgrade Apache Tomcat to 6.0.36"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49
+msgid "Split router info files into multiple subdirectories"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50
+msgid "Add IP to hostname mapping option in SOCKS"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51
+msgid "Improve PRNG seeding"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52
+msgid ""
+"Translation updates: French, German, Hungarian, Italian, Norwegian, "
+"Polish, Portuguese, Russian, Swedish"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54
+msgid "Update wrapper to 3.5.17 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:2
+msgid "0.9.6 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:7
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9
+msgid ""
+"0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to "
+"Jetty 7.6.10 (2013-03-12). See below for important information on the "
+"Jetty update. The Jetty 7 series is actively maintained and we plan to "
+"stay current with it in future I2P releases."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13
+msgid ""
+"Most users will update via HTTP. Those running development builds will "
+"attempt to update via the\n"
+"experimental in-network bittorrent with i2psnark. We've fixed some bugs "
+"that will enable more users\n"
+"to update via torrent in the 0.9.7 update cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25
+msgid "Important fix for Windows Eepsites, first install 0.9.5 only"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27
+msgid ""
+"If you first installed I2P with version 0.9.5, on Windows only, we "
+"recommend that you follow the\n"
+"following instructions to fix your eepsite location **before** you update"
+" to 0.9.6.\n"
+"Only original installations of 0.9.5-0 on Windows are affected by this "
+"issue. If your router version\n"
+"is 0.9.5-0-win1, you already have the fix and need not take any action."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34
+msgid "See `this page`_ for instructions."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:38
+msgid "`this page`"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:40
+msgid "Jetty 7 Migration Details"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42
+msgid ""
+"For most people, the update should just work. If you have multiple Jetty "
+"eepsites,\n"
+"OR have made changes to jetty.xml or other Jetty configuration files, "
+"including changing the port\n"
+"from 7658, you MUST take manual action AFTER updating."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48
+msgid ""
+"After update, the router will migrate your jetty.xml files to the new "
+"Jetty 7 format."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50
+msgid ""
+"The migration resets the port to 7658. If you have more than one Jetty "
+"eepsite, OR your eepsite\n"
+"  is NOT on port 7658, OR you have made other modifications to jetty.xml "
+"(for example changing the\n"
+"  listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml "
+"file for each eepsite to fix them up\n"
+"  after updating, and restart again."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55
+msgid ""
+"**The following files will be backed up with a ".jetty6" suffix"
+" and then migrated.**\n"
+"If you have made local changes, you may have to edit them manually and "
+"restart.\n"
+"See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69
+msgid "Plugins"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:71
+msgid "Most plugins should work fine with Jetty 7."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:75
+msgid ""
+"The I2PControl and zzzot plugins must be updated. Your router should "
+"download and install the new versions shortly after starting 0.9.6."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77
+msgid "If a plugin does not work, please contact the maintainer for that plugin."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83
+msgid "Several bugs with Windows installation (see above)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:84
+msgid "Fix default form action in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85
+msgid "Fix links on iframed console pages"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86
+msgid "Better detection of 64-bit Windows to prevent crashes by systray"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87
+msgid "Fix bug preventing router update via torrent"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88
+msgid "Several SSU fixes for NATs that change UDP ports"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89
+msgid ""
+"Ignore unsupported IPs in RouterInfos when selecting an address (prep for"
+" IPv6)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90
+msgid ""
+"Ignore unused option bits in Database Lookup Message (prep for requesting"
+" encrypted response)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91
+msgid "Fix HTTP proxy error response for malformed URIs"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92
+msgid "Recognize UPnP devices without port forwarding capability"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96
+msgid "Jetty 7.6.10 (see above for migration information)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97
+msgid "Limit page size in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98
+msgid "Add data directory and page size configuration to i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99
+msgid "Support multiple i2psnark instances"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100
+msgid "Piece size adjustments in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101
+msgid "Add more graphing support for combined bandwidth graph"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102
+msgid "Block b32.i2p supercookies"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103
+msgid "Allow stopping clients on /configclients"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104
+msgid "Check for nonce count replays in HTTP client"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105
+msgid "Support SASL authentication in IRC proxy"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106
+msgid "Several cleanups and minor fixes in the update manager"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107
+msgid "Translation updates: German, Portuguese, Russian, Spanish, and Swedish"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:2
+msgid "0.9.7 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:7
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:9
+msgid "0.9.7 includes significant bug fixes and improvements."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:11
+msgid ""
+"For the first time, class 'N' routers (those with a minimumum of 128 "
+"KBytes/sec of shared bandwidth)\n"
+"will automatically become floodfill (previously it was only 'O' routers "
+"with 256 KBps). This will\n"
+"increase the floodfill population for additional resistance to certain "
+"attacks (see below). Floodfill routers\n"
+"don't consume much additional bandwidth, but they do tend to use "
+"additional memory and concurrent\n"
+"connections. If you do not wish your router to become floodfill, set the "
+"advanced configuration\n"
+"router.floodfillParticipant=false ."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:20
+#, python-format
+msgid ""
+"As we think the last release fixed the experimental update-via-torrent "
+"bugs, 3% of routers should\n"
+"update over in-network bittorrent this cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:25
+msgid ""
+"Plugin update checks, possibly broken for several releases, are fixed. "
+"Your plugins should once again\n"
+"auto-update after updating the router."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:30
+msgid ""
+"We fixed a major streaming timer bug that contributed to frequent IRC "
+"disconnects."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:34
+msgid ""
+"This release contains additional mitigations for the `\"practical "
+"attacks\" paper`_.\n"
+"However, we have a lot more work to do to resist Sybil attacks on the "
+"floodfills, and resist\n"
+"traffic analysis at the gateways and endpoints of exploratory tunnels.\n"
+"It's a good reminder for everybody that our network is still relatively "
+"small and vulnerable.\n"
+"We don't currently recommend any uses that would put anybody in serious "
+"jeopardy.\n"
+"We'll keep working to improve it... please keep working to spread the "
+"word. A bigger network is a better network."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:43
+msgid "`\"practical attacks\" paper`"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:47
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:15
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:107
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:28
+msgid "Anonymity Improvements"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:49
+msgid "End-to-end encryption of responses to leaseset lookups"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:50
+msgid "Expand floodfill pool by enabling class 'N' floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:51
+msgid "Randomize padding inside encrypted SSU packets"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:52
+msgid "Preparation for better SSU protocol obfuscation"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:56
+msgid "Fix newer lease sets not getting stored or published"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:57
+msgid ""
+"Fix classpath bug when used with 4-year-old installations, causing the "
+"console not to start"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:58
+msgid "Fix addressbook database bug preventing update of the reverse index"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:59
+msgid ""
+"Fix i2psnark bug that changed the infohash of torrents created by Robert "
+"and fetched via magnet link"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60
+msgid "Fix version checking for plugins"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:61
+msgid ""
+"Fix a streaming timer bug causing frequent IRC disconnects (also affects "
+"other close-on-idle tunnels)"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:65
+msgid "Don't install as a service on Windows by default"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:66
+msgid "Reduce transport idle timeouts"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:67
+msgid "Reduce tunnels on idle in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:68
+msgid "Change default in i2ptunnel GUI to 3 hops"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:69
+msgid "IE 10 support"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70
+msgid ""
+"Individual expiration times in leases, for efficiency on destinations "
+"with a high number of tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71
+msgid "Low-level encryption and XOR speedups"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:72
+msgid "Jetty 7.6.11"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:73
+msgid "Tomcat 6.0.37"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74
+msgid "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75
+msgid "New Turkish translation"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:76
+msgid "Wrapper 3.5.19 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:2
+msgid "0.9.7.1 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:7
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:9
+msgid ""
+"This unscheduled release disables the RouterInfo verification messages "
+"that were used in the attack published in the UCSB paper, which should "
+"make correlating a LeaseSet and a Router much more difficult. We have "
+"also included a limited number of other fixes listed below. Our 0.9.8 "
+"release, which will include IPv6 support, is still on-schedule for late "
+"September."
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:11
+msgid "As usual, we recommend that all users update to this release."
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:17
+msgid "Disable RouterInfo verification messages"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:21
+msgid "Extend inbound tunnel expiration"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:22
+msgid "i2prouter: bashism fix"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:23
+msgid "i2psnark: increase max piece size, mime type updates"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:24
+msgid "New reseed host"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:25
+msgid "New update hosts, thanks Meeh and dg"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:26
+msgid "Streaming: RTO changes"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:27
+msgid "Updater: Increase update-via-torrent to 30 percent"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:28
+msgid "UPnP fix for some hardware"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:2
+msgid "0.9.8 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9
+msgid ""
+"0.9.8 includes the long-awaited support for IPv6. It's enabled by "
+"default, but of course you need a public IPv6 address to use it. "
+"Configuration is on the 'network' configuration tab in your console. We "
+"also have anonymity improvements including padding of SSU packets and "
+"longer router private keys."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11
+#, python-format
+msgid "30% of you will update via in-network torrent in this update cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13
+msgid "IPv6 Details"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15
+msgid ""
+"IPv6 is enabled and preferred by default. If you have a public IPv6 "
+"address \n"
+"and you are connecting to another router with a published IPv6 address, "
+"it will \n"
+"connect via IPv6. There is a new IPv6 configuration section on /confignet"
+" in \n"
+"the router console. If IPv6 is causing problems you may disable it there."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22
+msgid ""
+"As a part of the IPv6 development effort, I2P now supports multiple \n"
+"published IP addresses. If you have multiple public IP addresses (IPv4, "
+"IPv6, \n"
+"or both), you may enable or disable them individually on /confignet. The"
+" \n"
+"default is to use the first IPv4 and IPv6 addresses it discovers. If you "
+"have \n"
+"multiple addresses you should review the configuration on /confignet and "
+"adjust \n"
+"it if necessary.\n"
+"Note that while you may enable multiple IPv4 and IPv6 addresses on "
+"/confignet,\n"
+"we recommend that you use only one IPv4 and one IPv6 address. There are\n"
+"bugs still to be fixed with multiple addresses of each type."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34
+msgid ""
+"While IPv6 support was designed and developed over several years, it has"
+" \n"
+"only been tested by a limited number of users and is still beta. If you "
+"do have \n"
+"a public IPv6 address, please monitor your router and the logs for "
+"problems, \n"
+"and disable it necessary. Please report any bugs on \n"
+"http://trac.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:42
+msgid "Rekeying Details"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44
+msgid ""
+"For those of you running I2P on faster hardware (generally, 64-bit x86) "
+"the \n"
+"router will generate a new identity using longer keys. This will "
+"substantially \n"
+"reduce your participating traffic for 48 hours or more, while your router"
+" \n"
+"re-integrates into the network. Due to the new keys, the large number of"
+" \n"
+"torrent updates, and the recent network growth, we expect substantial \n"
+"disruption to the network for a week or more after the update is "
+"released. \n"
+"Please be patient and things should start to improve after a few days."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54
+msgid ""
+"These changes may result in higher CPU usage for some of you. We're doing"
+" \n"
+"our best to increase efficiency, but stronger security generally requires"
+" more \n"
+"computation. Performance may also be poor during the first week\n"
+"due to the network churn.\n"
+"We will evaluate the network performace before deciding whether to\n"
+"change the key length on slower hardware in a future release."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63
+msgid ""
+"We are experiencing rapid network growth in the last few weeks, which is"
+" \n"
+"causing a bit of a bumpy ride for some, especially on weekends. However, "
+"the \n"
+"network is still performing fairly well, so keep spreading the word."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69
+msgid "More Changes Coming"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:71
+msgid ""
+"We're in the initial stages of desiging major changes to strengthen our \n"
+"crypto. Stronger crypto will use more CPU and it may possibly \n"
+"require a Java 7 JRE at a minimum. We understand your desire to run I2P "
+"on low-power \n"
+"and/or older hardware. We're working hard to minimize the impacts, but "
+"some \n"
+"loss of performance is inevitable. In addition, Java 5 and 6 are no "
+"longer \n"
+"supported by Oracle. Now is a good time to upgrade to Java 7. Any change "
+"in \n"
+"minimum requirements will be announced well in advance."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:81
+msgid "New Website"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:83
+msgid ""
+"After a heroic effort by str4d, the new website preview is available at \n"
+"http://i2hq.srv.i2p2.de. We hope to see it go live at \n"
+"https://geti2p.net and http://www.i2p2.i2p soon.  Please \n"
+"contribute to the new website translations on Transifex, especially the \n"
+"website_priority resource."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91
+msgid "Community Participation"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:93
+msgid ""
+"In early August, hottuna and zzz attended DEFCON 21 in Las Vegas.\n"
+"Last weekend, echelon attended the CTS IV conference in Berlin and\n"
+"psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass.\n"
+"Several of us will be at 30C3 in Hamburg late this year.\n"
+"It's great to see people participating at these events and representing "
+"I2P."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105
+msgid "IPv6 support for both NTCP and SSU"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:109
+msgid "SSU protocol obfuscation by adding random padding"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110
+msgid "Longer encryption and DH private keys for users on faster platforms"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114
+msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:115
+msgid "Fix translation of HTTP proxy error pages"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:116
+msgid "Fix occasional runtime exception in NTCP"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120
+msgid "Big rework of transport code to accommodate multiple addresses and IPv6"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121
+msgid "Streaming: Improved recovery from lost acks, other fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122
+msgid "Use Transifex for translation of initial news and HTTP proxy error pages"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123
+msgid ""
+"Translation updates: Chinese, French, German, Portuguese, Russian, "
+"Swedish, Turkish"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124
+msgid "New Romanian translation"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:126
+msgid "Wrapper 3.5.20 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:2
+msgid "0.9.8.1 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:7
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:9
+msgid ""
+"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some "
+"people. New installs and non-Windows platforms are not affected, however "
+"all platforms will automatically update even if running 0.9.8."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:11
+msgid ""
+"See the `Trac ticket`_ for details and workarounds. See\n"
+"`the 0.9.8 release notes`_ for information on IPv6 and other changes."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:16
+msgid ""
+"Due to recent attacks, logins are disabled on `Trac`_ and new "
+"registrations are\n"
+"disabled on `zzz.i2p`_. Until those services are restored, please report "
+"all\n"
+"bugs on IRC freenode or IRC2P #i2p-dev."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:22
+msgid "`Trac ticket`"
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:23
+msgid "`the 0.9.8 release notes`"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:2
+msgid "0.9.9 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:7
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:9
+msgid ""
+"0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and "
+"starts work on a year-long plan to increase the strength of the "
+"cryptographic signing algorithms used in the router, and support multiple"
+" algorithms and key lengths simultaneously. Automatic update files will "
+"now be signed with 4096-bit RSA keys."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:11
+msgid ""
+"We now support SSL between your router and your servers for security.\n"
+"See `this development thread`_ for more information."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:16
+msgid "`this development thread`"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:18
+msgid ""
+"As usual, we recommend that you update to this release.\n"
+"The best way to maintain security and help the network is to run the "
+"latest release.\n"
+"Several members of the I2P team will be at 30C3 in Hamburg this year.\n"
+"Come say hello and ask for an I2P sticker.\n"
+"Thanks to everyone for their support this year."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:30
+msgid "Don't build client tunnels through zero-hop exploratory tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:31
+msgid "New \"su3\" file support using stronger keys"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:32
+msgid "Use su3 for updates"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:36
+msgid "Issues with losing data when closing streams"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:37
+msgid "Fix various streaming connection limit issues"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:38
+msgid "Issues with resource usage of closed connections"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:39
+msgid "Clean up timer threads in close-on-idle tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:40
+msgid "Several other streaming fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:41
+msgid "Reject more non-public IPv6 addresses"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:42
+msgid "Fix IPv6 GeoIP"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:43
+msgid "Fix peer selection in first minutes after startup"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:44
+msgid "Several I2PTunnel bug fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:45
+msgid "Fix major i2psnark DHT bug that prevented magnets from working well"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:46
+msgid ""
+"Fix client tunnels that fail due to name resolution failure at startup, "
+"particularly with b32 hostnames"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:47
+msgid "Fix changing client i2ptunnel target list"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:48
+msgid ""
+"Fix major bugs preventing reception of encrypted responses to leaseset "
+"lookups and verifies"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:49
+msgid "Fix bad links on some i2psnark buttons in Opera and text-mode browsers"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:50
+msgid "Fix NPE in Susimail"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:54
+msgid "Start work on supporting stronger signing keys in the router"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:55
+msgid "Reduce thread usage for HTTP Server tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:56
+msgid "Auto-stop update torrent after some time"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:57
+msgid "Add ability to stop webapp via console"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:58
+msgid "New POST throttler in HTTP server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:59
+msgid "Improve connection throttling"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:60
+msgid "More work to reduce number of connections"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:61
+msgid "Re-enable router info expiration job"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:62
+msgid ""
+"Extend router info expiration and other changes to reduce load on "
+"floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:63
+msgid "Support multiple servers through a single server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:64
+msgid "Support specification of server port in i2ptunnel clients"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:65
+msgid "Add support for SSL connections from i2ptunnel to external server"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:66
+msgid "SSL and crypto code refactoring"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:67
+msgid "i2psnark storage code refactoring"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:68
+msgid "New destination cache"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:69
+msgid "Lots of code cleanup and resolution of findbugs warnings"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:70
+msgid "New Japanese translation (partial)"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:71
+msgid ""
+"Translation updates: French, German, Italian, Romanian, Russian, Spanish,"
+" Swedish, and others"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:73
+msgid "Wrapper 3.5.22 (new installs and PPA only)"
+msgstr ""
+
diff --git a/i2p2www/translations/sv_SE/LC_MESSAGES/comparison.po b/i2p2www/translations/sv_SE/LC_MESSAGES/comparison.po
new file mode 100644
index 00000000..5c76c52a
--- /dev/null
+++ b/i2p2www/translations/sv_SE/LC_MESSAGES/comparison.po
@@ -0,0 +1,670 @@
+# Swedish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# hottuna , 2013
+# Martin Svensson , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-10-26 22:39+0000\n"
+"PO-Revision-Date: 2013-04-27 23:10+0000\n"
+"Last-Translator: Martin Svensson \n"
+"Language-Team: Swedish (Sweden) "
+"(http://www.transifex.com/projects/p/I2P/language/sv_SE/)\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/comparison/freenet.html:2
+msgid "I2P Compared to Freenet"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/freenet.html:8
+msgid ""
+"Freenet is a fully distributed, peer to peer anonymous publishing "
+"network, offering \n"
+"secure ways to store data, as well as some approaches attempting to "
+"address the loads\n"
+"of a flash flood.  While Freenet is designed as a distributed data store,"
+" people have\n"
+"built applications on top of it to do more generic anonymous "
+"communication, such as \n"
+"static websites and message boards."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/freenet.html:16
+#, python-format
+msgid ""
+"Compared to I2P, Freenet offers some substantial benefits - it is a "
+"distributed data\n"
+"store, while I2P is not, allowing people to retrieve the content "
+"published by others \n"
+"even when the publisher is no longer online.  In addition, it should be "
+"able to \n"
+"distribute popular data fairly efficiently.  I2P itself does not and will"
+" not provide \n"
+"this functionality.  On the other hand, there is overlap for users who "
+"simply want to \n"
+"communicate with each other anonymously through websites, message boards,"
+" file sharing\n"
+"programs, etc.  There have also been some attempts to develop a "
+"distributed data \n"
+"store to run on top of I2P,\n"
+"(most recently a port of Tahoe-LAFS)\n"
+"but nothing is yet ready for general use."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/freenet.html:29
+msgid ""
+"However, even ignoring any implementations issues, there are some "
+"concerns \n"
+"about Freenet's algorithms from both a scalability and anonymity "
+"perspective, owing \n"
+"largely to Freenet's heuristic driven routing.  The interactions of "
+"various techniques \n"
+"certainly may successfully deter various attacks, and perhaps some "
+"aspects of the \n"
+"routing algorithms will provide the hoped for scalability.  "
+"Unfortunately, not much\n"
+"analysis of the algorithms involved has resulted in positive results, but"
+" there is still\n"
+"hope.  At the very least, Freenet does provide substantial anonymity "
+"against an attacker\n"
+"who does not have the resources necessary to analyze it further."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/index.html:2
+msgid "Comparing I2P to other projects"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/index.html:4
+msgid ""
+"There are a great many other applications and projects working on "
+"anonymous \n"
+"communication and I2P has been inspired by much of their efforts.  This "
+"is not \n"
+"a comprehensive list of anonymity resources - both freehaven's \n"
+"Anonymity "
+"Bibliography\n"
+"and GNUnet's related "
+"projects\n"
+"serve that purpose well.  That said, a few systems stand out for further\n"
+"comparison. The following have individual comparison pages:"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/index.html:20
+#, python-format
+msgid ""
+"The following are discussed on the other "
+"networks page:"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/index.html:32
+#, python-format
+msgid ""
+"The content of this page is subject to update, discussion and dispute, "
+"and we welcome comments and additions.\n"
+"You may contribute an analysis by entering a new "
+"ticket on Trac."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:2
+msgid "I2P Compared to Other Anonymous Networks"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:5
+msgid "The following networks are discussed on this page."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:16
+#, python-format
+msgid ""
+"Most of the following sections are fairly old, and may not be accurate.\n"
+"For an overview of available comparisons, see the\n"
+"main network comparisons page.\n"
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:29
+#, python-format
+msgid ""
+"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
+" \n"
+"anonymizing proxies, allowing people to tunnel out through the low "
+"latency \n"
+"mix network.  Morphmix includes some very interesting collusion detection"
+" \n"
+"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
+"IP\n"
+"addresses to accomplish the same.  The two primary differences between \n"
+"these systems and I2P are related to I2P's threat model \n"
+"and their out-proxy design (as opposed to providing both sender and "
+"receiver \n"
+"anonymity).  There is source code available to both systems, but we are "
+"not aware \n"
+"of their use outside of academic environments."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:153
+#, python-format
+msgid ""
+"\n"
+"Mixminion and Mixmaster are networks to support anonymous email against a"
+" very\n"
+"powerful adversary.\n"
+"High-latency messaging applications running on top of I2P\n"
+"(for example Syndie or I2PBote)\n"
+"may perhaps prove adequate to meet the threat\n"
+"model of those adversaries, while running in parallel along side the "
+"needs of low latency users, to provide\n"
+"a significantly larger anonymity set.\n"
+"High-latency support within the I2P router itself may or may not be added"
+" in a distant future release.\n"
+"It is too early to say if I2P will meet the needs of users requiring "
+"extreme protection for email."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:165
+msgid ""
+"As with Tor and Onion Routing, \n"
+"both Mixminion and Mixmaster take the directory based approach as well."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:175
+#, python-format
+msgid ""
+"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
+"web requests,\n"
+"and as such it has a few centralized nodes (participants in the cascade) "
+"that blend\n"
+"and mix requests from clients through the sequence of nodes (the cascade)"
+" before \n"
+"proxying out onto the web.  The scope, threat model, and security is "
+"substantially \n"
+"different from I2P, but for those who don't require significant anonymity"
+" but still\n"
+"are not satisfied with an Anonymizer-like service, JAP is worth "
+"reviewing.  One\n"
+"caution to note is that anyone under the jurisdiction of the German "
+"courts may want\n"
+"to take care, as the German Federal Bureau of Criminal Investigation "
+"(FBCI) has \n"
+"successfully mounted an \n"
+"attack \n"
+"on the network.  Even though the method of this attack was later found to"
+" be illegal \n"
+"in the German courts, the fact that the data was successfully collected "
+"is the \n"
+"concern.  Courts change their minds based upon circumstance, and this is "
+"evidence that \n"
+"if a government body or intelligence agency wanted to, they could gather "
+"the data, even \n"
+"if it may be found inadmissible in some courts later)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:197
+#, python-format
+msgid ""
+"Both of these systems work through the same basic \n"
+"antnet routing, providing some degree of\n"
+"anonymity based on the threat model of providing plausible deniability "
+"against a simple \n"
+"non-colluding adversary.  With the antnet routing, they first either do a"
+" random walk or a \n"
+"broadcast search to find some peer with the data or identity desired, and"
+" then use a feedback\n"
+"algorithm to optimize that found path.  This works well for applications "
+"that merely want to know \n"
+"what other people around them have to offer - \"How are y'all doing\" vs."
+" \"Hey Alice, how are you\" - \n"
+"you basically get a local cluster of nodes that can share files with and "
+"maintain some degree of \n"
+"anonymity (though you don't have much control over who is in that group "
+"of peers)."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:209
+msgid ""
+"However, the algorithm does not scale well at all - if the application "
+"wants to speak with a \n"
+"particular peer it ends up doing a broadcast search or random walk "
+"(though if they are lucky enough\n"
+"for that to succeed, the antnet routing should optimize that found "
+"connection).  This means that \n"
+"while these networks can work great at small scales, they are not "
+"suitable for large networks where\n"
+"someone wants to get in touch with another specific peer.  That does not "
+"mean that there is no \n"
+"value in these systems, just that their applicability is limited to "
+"situations where their \n"
+"particular issues can be addressed."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:220
+#, python-format
+msgid ""
+"This was a closed-source network targeted at Iranian users.\n"
+"Tor did a good writeup on what to look for in a "
+"circumvention tool.\n"
+"Suffice it to say that being closed source and publicly targeting a "
+"specific country are not good ideas.\n"
+"I2P is, of course, open source. However, that source, and our\n"
+"technical documentation, need much more review."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:229
+msgid "Paid VPN Services"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:230
+#: i2p2www/pages/site/comparison/other-networks.html:236
+#, python-format
+msgid ""
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/other-networks.html:235
+msgid "Others"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:2
+msgid "I2P Compared to Tor"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:8
+#, python-format
+msgid ""
+"Tor and Onion Routing are both anonymizing proxy networks, \n"
+"allowing people to tunnel out through their low latency mix \n"
+"network. The two primary differences between Tor / \n"
+"Onion-Routing and I2P are again related to differences in \n"
+"the threat model and the out-proxy design (though Tor\n"
+"supports hidden services as well).  In addition, Tor\n"
+"takes the directory-based approach - providing a \n"
+"centralized point to manage the overall 'view' of the \n"
+"network, as well as gather and report statistics, as \n"
+"opposed to I2P's distributed network \n"
+"database and peer selection."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:22
+msgid ""
+"The I2P/Tor outproxy functionality does have a few \n"
+"substantial weaknesses against certain attackers - \n"
+"once the communication leaves the mixnet, global passive\n"
+"adversaries can more easily mount traffic analysis.  In \n"
+"addition, the outproxies have access to the cleartext \n"
+"of the data transferred in both directions, and \n"
+"outproxies are prone to abuse, along with all of the \n"
+"other security issues we've come to know and love with \n"
+"normal Internet traffic."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:34
+msgid ""
+"However, many people don't need to worry about those \n"
+"situations, as they are outside their threat model.  It\n"
+"is, also, outside I2P's (formal) functional scope (if people want\n"
+"to build outproxy functionality on top of an anonymous\n"
+"communication layer, they can).  In fact, some I2P users\n"
+"currently take advantage of Tor to outproxy."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:48
+msgid "Comparison of Tor and I2P Terminology"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:49
+msgid ""
+"While Tor and I2P are similar in many ways, much of the terminology is "
+"different."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Cell"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Message"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Client"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Router or Client"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Circuit"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Tunnel"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "Directory"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "NetDb"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Directory Server"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Floodfill Router"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Entry Guards"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Fast Peers"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Entry Node"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Inproxy"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Exit Node"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Outproxy"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Hidden Service"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Eepsite or Destination"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "Hidden Service Descriptor"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "LeaseSet"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Introduction point"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Inbound Gateway"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:65
+msgid "Node"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:65
+#: i2p2www/pages/site/comparison/tor.html:67
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Router"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "Onion Proxy"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "I2PTunnel Client (more or less)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:67
+msgid "Relay"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "Rendezvous Point"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "somewhat like Inbound Gateway + Outbound Endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "Router Descriptor"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Server"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:73
+msgid "Benefits of Tor over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:76
+msgid ""
+"Much bigger user base; much more visibility in the academic and hacker "
+"communities; benefits from\n"
+"formal studies of anonymity, resistance, and performance;\n"
+"has a non-anonymous, visible, university-based leader"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:82
+msgid "Has already solved some scaling issues I2P has yet to address"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:83
+msgid "Has significant funding"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:84
+msgid "Has more developers, including several that are funded"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:86
+msgid ""
+"More resistant to state-level blocking due to TLS transport layer and "
+"bridges\n"
+"(I2P has proposals for \"full restricted routes\" but these are not yet "
+"implemented)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:91
+msgid "Big enough that it has had to adapt to blocking and DOS attempts"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:92
+msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:94
+msgid ""
+"Better documentation, has formal papers and specifications,\n"
+"better website, many more translations"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:99
+msgid "More efficient with memory usage"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:100
+msgid "Tor client nodes have very low bandwidth overhead"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:102
+msgid ""
+"Centralized control reduces the complexity at each\n"
+"node and can efficiently address Sybil attacks"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:108
+msgid ""
+"A core of high capacity nodes provides higher\n"
+"throughput and lower latency"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:113
+msgid "C, not Java (ewww)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:116
+msgid "Benefits of I2P over Tor"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:118
+msgid ""
+"Designed and optimized for hidden services, which are much faster than in"
+" Tor"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:119
+msgid "Fully distributed and self organizing"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:121
+msgid ""
+"Peers are selected by continuously profiling and ranking performance,\n"
+"rather than trusting claimed capacity"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:127
+msgid ""
+"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
+"rather than hardcoded"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:132
+msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:133
+msgid "Peer-to-peer friendly"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:134
+msgid "Packet switched instead of circuit switched"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:137
+msgid ""
+"implicit transparent load balancing of messages \n"
+"across multiple peers, rather than a single path"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:143
+msgid ""
+"resilience vs. failures by running multiple \n"
+"tunnels in parallel, plus rotating tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:149
+msgid ""
+"scale each client's connections at O(1) instead \n"
+"of O(N) (Alice has e.g. 2 inbound tunnels that are \n"
+"used by all of the peers Alice is talking with, \n"
+"rather than a circuit for each)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:159
+msgid ""
+"Unidirectional tunnels instead of bidirectional\n"
+"circuits, doubling the number of nodes a peer has to\n"
+"compromise to get the same information."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:166
+msgid ""
+"Protection against detecting client activity, even\n"
+"when an attacker is participating in the tunnel, as\n"
+"tunnels are used for more than simply passing end \n"
+"to end messages (e.g. netDb, tunnel management, \n"
+"tunnel testing)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:175
+msgid ""
+"Tunnels in I2P are short lived, decreasing the number\n"
+"of samples that an attacker can use to mount an \n"
+"active attack with, unlike circuits in Tor, which are\n"
+"typically long lived."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:183
+msgid ""
+"I2P APIs are designed specifically for anonymity and\n"
+"security, while SOCKS is designed for functionality."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:188
+msgid "Essentially all peers participate in routing for others"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:190
+msgid ""
+"The bandwidth overhead of being a full peer is low, \n"
+"while in Tor, while client nodes don't require much\n"
+"bandwidth, they don't fully participate in the mixnet."
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:196
+msgid "Integrated automatic update mechanism"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:197
+msgid "Both TCP and UDP transports"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:198
+msgid "Java, not C (ewww)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:201
+msgid "Other potential benefits of I2P but not yet implemented"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:202
+msgid "...and may never be implemented, so don't count on them!"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:205
+msgid ""
+"Defense vs. message count analysis by garlic wrapping \n"
+"multiple messages"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:211
+msgid ""
+"Defense vs. long term intersection by adding delays \n"
+"at various hops (where the delays are not discernible\n"
+"by other hops)"
+msgstr ""
+
+#: i2p2www/pages/site/comparison/tor.html:218
+msgid ""
+"Various mixing strategies at the tunnel level (e.g.\n"
+"create a tunnel that will handle 500 messages / minute,\n"
+"where the endpoint will inject dummy messages if there\n"
+"are insufficient messages, etc)"
+msgstr ""
+
diff --git a/i2p2www/translations/sv_SE/LC_MESSAGES/docs.po b/i2p2www/translations/sv_SE/LC_MESSAGES/docs.po
new file mode 100644
index 00000000..c61c57f9
--- /dev/null
+++ b/i2p2www/translations/sv_SE/LC_MESSAGES/docs.po
@@ -0,0 +1,16796 @@
+# Swedish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# hottuna , 2013
+# Martin Svensson , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-04-27 23:10+0000\n"
+"Last-Translator: Martin Svensson \n"
+"Language-Team: Swedish (Sweden) "
+"(http://www.transifex.com/projects/p/I2P/language/sv_SE/)\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/docs/index.html:2 i2p2www/pages/site/docs/index.html:25
+msgid "Index to Technical Documentation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:3 i2p2www/pages/site/docs/ports.html:3
+#: i2p2www/pages/site/docs/spec/datagrams.html:3
+msgid "May 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:6
+msgid "How does I2P work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:8
+msgid "Following is an index to the technical documentation for I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:12
+msgid ""
+"This index is ordered from the highest to lowest layers.\n"
+"The higher layers are for \"clients\" or applications;\n"
+"the lower layers are inside the router itself.\n"
+"The interface between applications and the router is the I2CP (I2P "
+"Control Protocol) API."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:19
+#, python-format
+msgid ""
+"The I2P Project is committed to maintaining accurate, current "
+"documentation.\n"
+"If you find any inaccuracies in the documents linked below, please\n"
+"enter a ticket identifying the problem."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:27 i2p2www/pages/site/docs/naming.html:7
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:12
+#: i2p2www/pages/site/docs/api/streaming.html:6
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:6
+#: i2p2www/pages/site/docs/how/network-database.html:6
+#: i2p2www/pages/site/docs/how/peer-selection.html:6
+#: i2p2www/pages/site/docs/how/tech-intro.html:13
+#: i2p2www/pages/site/docs/how/tech-intro.html:97
+#: i2p2www/pages/site/docs/spec/blockfile.html:7
+#: i2p2www/pages/site/docs/spec/configuration.html:6
+#: i2p2www/pages/site/docs/spec/geoip.html:7
+#: i2p2www/pages/site/docs/spec/updates.html:6
+#: i2p2www/pages/site/docs/tunnels/implementation.html:67
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:6
+msgid "Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:29
+msgid "Technical Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:30
+msgid "A Less-Technical Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:31
+msgid "Threat model and analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:32
+msgid "Comparisons to other anonymous networks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:33
+msgid "Protocol stack chart"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:34
+msgid "Papers on I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:35
+#, python-format
+msgid ""
+"Invisible Internet Project (I2P) Project Overview"
+" August 28, 2003 (pdf)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:38
+msgid "Application-Layer Topics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:41 i2p2www/pages/site/docs/naming.html:2
+msgid "Naming and Addressbook"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:42
+msgid "Plugins Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:43
+msgid "Plugin Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:44
+msgid "Router software updates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:45
+#: i2p2www/pages/site/docs/applications/bittorrent.html:2
+msgid "Bittorrent over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:46
+msgid "I2PControl Plugin API"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:47
+msgid "hostsdb.blockfile Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:185
+msgid "Configuration File Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:51
+msgid "Application Layer API and Protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:52
+msgid ""
+"High-level, easy-to-use APIs for applications written in any language to "
+"send and receive data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:54
+msgid "Application Development Overview and Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:72
+msgid "SAM Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:74
+msgid "SAMv2 Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:76
+msgid "SAMv3 Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:78
+msgid "BOB Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:81
+msgid "End-to-End Transport API and Protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:82
+msgid ""
+"The end-to-end protocols used by clients for reliable and unreliable "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:84
+#: i2p2www/pages/site/docs/api/streaming.html:2
+msgid "Streaming Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:86
+msgid "Streaming Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:88
+#: i2p2www/pages/site/docs/api/datagrams.html:2
+msgid "Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:90
+msgid "Datagram Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:93
+msgid "Client-to-Router Interface API and Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:94
+msgid ""
+"The lowest-level API used for clients (applications) to send and receive "
+"traffic to a router.\n"
+"Traditionally used only by Java applications and higher-level APIs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:99
+msgid "I2CP - I2P Control Protocol / API overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:101
+msgid "I2CP Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:103
+msgid "I2CP API Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:105
+#: i2p2www/pages/site/docs/index.html:134
+msgid "Common data structures specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:107
+#: i2p2www/pages/site/docs/index.html:136
+msgid "Data Structures Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:110
+msgid "End-to-End Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:111
+msgid "How client messages are end-to-end encrypted by the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:113
+msgid "ElGamal/AES+SessionTag encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:114
+#: i2p2www/pages/site/docs/index.html:147
+msgid "ElGamal and AES cryptography details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:117
+#: i2p2www/pages/site/docs/how/tech-intro.html:15
+#: i2p2www/pages/site/docs/how/tech-intro.html:329
+msgid "Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:118
+msgid ""
+"Distributed storage and retrieval of information about routers and "
+"clients."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:120
+msgid "Network database overview, details, and threat analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:121
+msgid "Cryptographic hashes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:122
+msgid "Cryptographic signatures"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:125
+msgid "Router Message Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:126
+msgid ""
+"I2P is a message-oriented router. The messages sent between routers are "
+"defined by the I2NP protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:128
+msgid "I2NP - I2P Network Protocol Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:130
+msgid "I2NP Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:132
+msgid "I2NP Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:139
+#: i2p2www/pages/site/docs/how/tech-intro.html:14
+#: i2p2www/pages/site/docs/how/tech-intro.html:228
+msgid "Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:140
+msgid ""
+"Selecting peers, requesting tunnels through those peers, and encrypting "
+"and routing messages through these tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:142
+msgid "Peer profiling and selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:143
+msgid "Tunnel routing overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:144
+msgid "Garlic routing and \"garlic\" terminology"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:145
+msgid "Tunnel building and encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:146
+msgid "ElGamal/AES"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:146
+msgid "for build request encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:148
+msgid "Tunnel building specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:149
+msgid "Low-level tunnel message specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:150
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:2
+msgid "Unidirectional Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:151
+#: i2p2www/pages/site/docs/how/peer-selection.html:299
+msgid "Peer Profiling and Selection in the I2P Anonymous Network"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:152
+msgid "2009 paper (pdf), not current but still generally accurate"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:155
+msgid "Transport Layer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:156
+msgid "The protocols for direct (point-to-point) router to router communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:158
+msgid "Transport layer overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:160
+msgid "TCP-based transport overview and specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:162
+msgid "UDP-based transport overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:164
+msgid "SSU specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:166
+msgid "NTCP transport encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:168
+msgid "SSU transport encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:170
+msgid "Transport Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:172
+msgid "NTCP Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:174
+msgid "SSU Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:177
+msgid "Other Router Topics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:179
+msgid "Native BigInteger Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:181
+msgid "Time synchronization and NTP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:183
+msgid "Performance"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:190
+msgid "Developer's Guides and Resources"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:192
+msgid "New Developer's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:194
+msgid "New Translator's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:196
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:198
+msgid "Developer Guidelines"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:200
+msgid "Javadocs on the standard internet:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:201
+#: i2p2www/pages/site/docs/index.html:205
+#: i2p2www/pages/site/docs/index.html:206
+#: i2p2www/pages/site/docs/index.html:207
+#, python-format
+msgid "Server %(num)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:202
+#: i2p2www/pages/site/docs/index.html:211
+msgid ""
+"Note: always verify that javadocs are current by checking the release "
+"number."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:204
+msgid "Javadocs inside I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:213
+msgid "Ports used by I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:215
+msgid "Automatic updates to development builds inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:217
+msgid "Updating the wrapper manually"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:219
+msgid "User forum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:221
+msgid "Developer forum inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:223
+msgid "Bug tracker"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:225
+msgid "Viewmtn inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:227
+msgid "I2P Source exported to GitHub"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:229
+msgid "I2P Source Git Repo inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:231
+msgid "Source translation at Transifex"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:233
+msgid "Roadmap wiki"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:235
+msgid "Old roadmap"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:235
+#: i2p2www/pages/site/docs/index.html:237
+msgid "not current"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:237
+msgid "To Do List"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:3
+#: i2p2www/pages/site/docs/api/streaming.html:3
+#: i2p2www/pages/site/docs/how/cryptography.html:3
+#: i2p2www/pages/site/docs/protocol/i2cp.html:3
+#: i2p2www/pages/site/docs/spec/common-structures.html:3
+#: i2p2www/pages/site/docs/spec/geoip.html:3
+#: i2p2www/pages/site/docs/spec/streaming.html:3
+#: i2p2www/pages/site/docs/transport/index.html:3
+#: i2p2www/pages/site/docs/transport/ntcp.html:3
+#: i2p2www/pages/site/docs/transport/ssu.html:3
+msgid "December 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:6
+msgid "Naming in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:9
+msgid ""
+"I2P ships with a generic naming library and a base implementation \n"
+"designed to work off a local name to destination mapping, as well as an\n"
+"add-on application called the addressbook. \n"
+"I2P also supports Base32 hostnames similar to "
+"Tor's .onion addresses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:16
+msgid ""
+"The addressbook is a web-of-trust\n"
+"driven secure, distributed, and human readable naming system, sacrificing"
+" only\n"
+"the call for all human readable names to be globally unique by mandating "
+"only\n"
+"local uniqueness.  While all messages in I2P are cryptographically "
+"addressed\n"
+"by their destination, different people can have local addressbook entries"
+" for\n"
+"\"Alice\" which refer to different destinations.  People can still "
+"discover new\n"
+"names by importing published addressbooks of peers specified in their web"
+" of trust,\n"
+"by adding in the entries provided through a third party, or (if some "
+"people organize\n"
+"a series of published addressbooks using a first come first serve "
+"registration\n"
+"system) people can choose to treat these addressbooks as name servers, "
+"emulating\n"
+"traditional DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:30
+#, python-format
+msgid ""
+"NOTE: For the reasoning behind the I2P naming system, common arguments "
+"against it\n"
+"and possible alternatives see the naming"
+" discussion\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:37
+msgid "Naming System Components"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:39
+msgid ""
+"There is no central naming authority in I2P.\n"
+"All hostnames are local."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:44
+msgid ""
+"The naming system is quite simple and most of it is implemented\n"
+"in applications external to the router, but bundled with\n"
+"the I2P distribution.\n"
+"The components are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:52
+msgid ""
+"The local naming service which does lookups\n"
+"and also handles Base32 hostnames."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:56
+msgid ""
+"The HTTP proxy which asks the router for "
+"lookups and points\n"
+"the user to remote jump services to assist with failed lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:60
+msgid ""
+"HTTP host-add forms which allow users to "
+"add hosts to their local hosts.txt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:63
+msgid ""
+"HTTP jump services which provide their own"
+" lookups and redirection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:66
+msgid ""
+"The addressbook application which merges "
+"external\n"
+"host lists, retrieved via HTTP, with the local list."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:70
+msgid ""
+"The SusiDNS application which is a simple web "
+"front-end\n"
+"for addressbook configuration and viewing of the local host lists."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:77
+msgid "Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:79
+#, python-format
+msgid ""
+"All destinations in I2P are 516-byte (or longer) keys.\n"
+"(To be more precise, it is a 256-byte public key plus a 128-byte signing "
+"key\n"
+"plus a null certificate, which in Base64 representation is 516 bytes.\n"
+"Certificates are not "
+"used now,\n"
+"if they are, the keys will be longer.\n"
+"One possible use of certificates is for proof of work.)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:88
+msgid ""
+"If an application (i2ptunnel or the HTTP proxy) wishes to access\n"
+"a destination by name, the router does a very simple local lookup\n"
+"to resolve that name."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:94
+msgid "Hosts.txt Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:96
+msgid ""
+"The hosts.txt Naming Service does a simple linear search through\n"
+"text files. This naming service was the default until\n"
+"release 0.8.8 when it was replaced by the Blockfile Naming Service.\n"
+"The hosts.txt format had become too slow after the file grew to thousands"
+" of entries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:103
+#, python-format
+msgid ""
+"It does a linear search through three local files, in order, to\n"
+"look up host names and convert them to a 516-byte destination key.\n"
+"Each file is in a simple configuration file"
+" format, with hostname=base64, one per line.\n"
+"The files are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:115
+msgid "Blockfile Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:117
+msgid ""
+"The Blockfile Naming Service stores multiple \"addressbooks\" in a single"
+"\n"
+"database file named hostsdb.blockfile.\n"
+"This Naming Service is the default since release 0.8.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:123
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is specified on the Blockfile page.\n"
+"It provides fast Destination lookup in a compact format. While the "
+"blockfile overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry to implement "
+"advanced addressbook features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:135
+msgid ""
+"On creation, the naming service imports entries from the three files used"
+" by the hosts.txt Naming Service.\n"
+"The blockfile mimics the previous implementation by maintaining three "
+"maps that\n"
+"are searched in-order, named privatehosts.txt, userhosts.txt, and "
+"hosts.txt.\n"
+"It also maintains a reverse-lookup map to implement rapid reverse lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:142
+msgid "Other Naming Service Facilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:144
+#, python-format
+msgid ""
+"The lookup is case-insensitive.\n"
+"The first match is used, and conflicts are not detected.\n"
+"There is no enforcement of naming rules in lookups.\n"
+"Lookups are cached for a few minutes.\n"
+"Base 32 resolution is described below.\n"
+"For a full description of the Naming Service API see the\n"
+"Naming Service Javadocs.\n"
+"This API was significantly expanded in release 0.8.7 to provide\n"
+"adds and removes, storage of arbitrary properties with the hostname,\n"
+"and other features."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:157
+msgid "Alternatives and Experimental Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:159
+#, python-format
+msgid ""
+"The naming service is specified with the configuration property "
+"i2p.naming.impl=class.\n"
+"Other implementations are possible. For example,\n"
+"there is an experimental facility for real-time lookups (a la DNS) over "
+"the network within the router.\n"
+"For more information see the alternatives on the discussion"
+" page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:166
+msgid ""
+"The HTTP proxy does a lookup via the router for all hostnames ending in "
+"'.i2p'.\n"
+"Otherwise, it forwards the request to a configured HTTP outproxy.\n"
+"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-"
+"Top Level Domain '.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:172
+#, python-format
+msgid ""
+"We have applied to reserve the .i2p TLD\n"
+"following the procedures specified in RFC "
+"6761."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:178
+msgid ""
+"If the router fails to resolve the hostname, the HTTP proxy returns\n"
+"an error page to the user with links to several \"jump\" services.\n"
+"See below for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:184
+#: i2p2www/pages/site/docs/spec/configuration.html:77
+msgid "Addressbook"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:185
+msgid "Incoming Subscriptions and Merging"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:187
+msgid ""
+"The addressbook application periodically\n"
+"retrieves other users' hosts.txt files and merges\n"
+"them with the local hosts.txt, after several checks.\n"
+"Naming conflicts are resolved on a first-come first-served\n"
+"basis."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:195
+msgid ""
+"Subscribing to another user's hosts.txt file involves\n"
+"giving them a certain amount of trust.\n"
+"You do not want them, for example, 'hijacking' a new site\n"
+"by quickly entering in their own key for a new site before\n"
+"passing the new host/key entry to you."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:203
+msgid ""
+"For this reason, the only subscription configured by\n"
+"default is http://www.i2p2.i2p/hosts.txt,\n"
+"which contains a copy of the hosts.txt included\n"
+"in the I2P release.\n"
+"Users must configure additional subscriptions in their\n"
+"local addressbook application (via subscriptions.txt or SusiDNS)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:212
+msgid "Some other public addressbook subscription links:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:219
+msgid ""
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:224
+#: i2p2www/pages/site/docs/naming.html:236
+msgid "Naming Rules"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:225
+msgid ""
+"While there are hopefully not any technical limitations within I2P on "
+"host names,\n"
+"the addressbook enforces several restrictions on host names\n"
+"imported from subscriptions.\n"
+"It does this for basic typographical sanity and compatibility with "
+"browsers,\n"
+"and for security.\n"
+"The rules are essentially the same as those in RFC2396 Section 3.2.2.\n"
+"Any hostnames violating these rules may not be propagated\n"
+"to other routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:240
+msgid "Names are converted to lower case on import."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:244
+msgid ""
+"Names are checked for conflict with existing names in the existing "
+"userhosts.txt and hosts.txt\n"
+"(but not privatehosts.txt) after conversion to lower case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:249
+msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:253
+msgid "Must not start with '.' or '-'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:257
+msgid "Must end with '.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:261
+msgid "67 characters maximum, including the '.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:265
+msgid "Must not contain '..'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:269
+msgid "Must not contain '.-' or '-.' (as of 0.6.1.33)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:273
+msgid "Must not contain '--' except in 'xn--' for IDN."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:277
+msgid ""
+"Base32 hostnames (*.b32.i2p) are reserved for base 32 use and so are not "
+"allowed to be imported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:281
+msgid ""
+"Certain hostnames reserved for project use are not allowed\n"
+"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
+"*.console.i2p, and others)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:286
+msgid "Keys are checked for base64 validity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:290
+msgid ""
+"Keys are checked for conflict with existing keys in hosts.txt (but not "
+"privatehosts.txt)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:294
+msgid "Minimum key length 516 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:298
+msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:303
+msgid ""
+"Any name received via subscription that passes all the checks is added "
+"via the local naming service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:307
+msgid ""
+"Note that the '.' symbols in a host name are of no significance,\n"
+"and do not denote any actual naming or trust hierarchy.\n"
+"If the name 'host.i2p' already exists, there is nothing\n"
+"to prevent anybody from adding a name 'a.host.i2p' to their hosts.txt,\n"
+"and this name can be imported by others' addressbook.\n"
+"Methods to deny subdomains to non-domain 'owners' (certificates?),\n"
+"and the desirability and feasibility of these methods,\n"
+"are topics for future discussion."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:318
+msgid ""
+"International Domain Names (IDN) also work in i2p (using punycode 'xn--' "
+"form).\n"
+"To see IDN .i2p domain names rendered correctly in Firefox's location "
+"bar,\n"
+"add 'network.IDN.whitelist.i2p (boolean) = true' in about:config."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:324
+msgid ""
+"As the addressbook application does not use privatehosts.txt at all, in "
+"practice\n"
+"this file is the only place where it is appropriate to place private "
+"aliases or\n"
+"\"pet names\" for sites already in hosts.txt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:330
+msgid "Outgoing Subscriptions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:331
+msgid ""
+"Addressbook will publish the merged hosts.txt to a location\n"
+"(traditionally hosts.txt in the local eepsite's home directory) to be "
+"accessed by others\n"
+"for their subscriptions.\n"
+"This step is optional and is disabled by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:339
+msgid ""
+"The addressbook application, together with eepget, saves the Etag and/or "
+"Last-Modified\n"
+"information returned by the web server of the subscription.\n"
+"This greatly reduces the bandwidth required, as the web server will\n"
+"return a '304 Not Modified' on the next fetch if nothing has changed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:346
+msgid ""
+"However the entire hosts.txt is downloaded if it has changed.\n"
+"See below for discussion on this issue."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:351
+msgid ""
+"Hosts serving a static hosts.txt or an equivalent CGI application\n"
+"are strongly encouraged to deliver\n"
+"a Content-Length header, and either an Etag or Last-Modified header.\n"
+"Also ensure that the server delivers a '304 Not Modified' when "
+"appropriate.\n"
+"This will dramatically reduce the network bandwidth, and\n"
+"reduce chances of corruption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:360
+msgid "Host Add Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:361
+msgid ""
+"A host add service is a simple CGI application that takes a hostname and "
+"a Base64 key as parameters\n"
+"and adds that to its local hosts.txt.\n"
+"If other routers subscribe to that hosts.txt, the new hostname/key\n"
+"will be propagated through the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:368
+msgid ""
+"It is recommended that host add services impose, at a minimum, the "
+"restrictions imposed by the addressbook application listed above.\n"
+"Host add services may impose additional restrictions on hostnames and "
+"keys, for example:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:373
+msgid "A limit on number of 'subdomains'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:377
+msgid "Authorization for 'subdomains' through various methods."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:381
+msgid "Hashcash or signed certificates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:385
+msgid "Editorial review of host names and/or content."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:389
+msgid "Categorization of hosts by content."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:393
+msgid "Reservation or rejection of certain host names."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:397
+msgid "Restrictions on the number of names registered in a given time period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:401
+msgid "Delays between registration and publication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:405
+msgid "Requirement that the host be up for verification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:409
+msgid "Expiration and/or revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:413
+msgid "IDN spoof rejection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:418
+msgid "Jump Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:419
+msgid ""
+"A jump service is a simple CGI application that takes a hostname as a "
+"parameter\n"
+"and returns a 301 redirect to the proper URL with a "
+"?i2paddresshelper=key\n"
+"string appended.\n"
+"The HTTP proxy will interpret the appended string and\n"
+"use that key as the actual destination.\n"
+"In addition, the proxy will cache that key so the\n"
+"address helper is not necessary until restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:429
+msgid ""
+"Note that, like with subscriptions, using a jump service\n"
+"implies a certain amount of trust, as a jump service could maliciously\n"
+"redirect a user to an incorrect destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:435
+msgid ""
+"To provide the best service, a jump service should be subscribed to\n"
+"several hosts.txt providers so that its local host list is current."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:441
+msgid ""
+"SusiDNS is simply a web interface front-end to configuring addressbook "
+"subscriptions\n"
+"and accessing the four addressbook files.\n"
+"All the real work is done by the 'addressbook' application."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:447
+msgid ""
+"Currently, there is little enforcement of addressbook naming rules within"
+" SusiDNS,\n"
+"so a user may enter hostnames locally that would be rejected by\n"
+"the addressbook subscription rules."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:453
+msgid "Base32 Names"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:454
+msgid ""
+"I2P supports Base32 hostnames similar to Tor's .onion addresses.\n"
+"Base32 addresses are much shorter and easier to handle than the\n"
+"full 516-character Base64 Destinations or addresshelpers.\n"
+"Example: "
+"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:461
+#, python-format
+msgid ""
+"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 "
+"hash.\n"
+"I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n"
+"The form is {52 chars}.b32.i2p.\n"
+"Tor has recently published a\n"
+"proposal\n"
+"to convert to an identical format of {52 chars}.onion for their hidden "
+"services.\n"
+"Base32 is implemented in the naming service, which queries the\n"
+"router over I2CP to lookup the LeaseSet to get the full Destination.\n"
+"Base32 lookups will only be successful when the Destination is up and "
+"publishing\n"
+"a LeaseSet.\n"
+"Because resolution may require a network database lookup, it may take "
+"significantly\n"
+"longer than a local address book lookup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:476
+msgid ""
+"Base32 addresses can be used in most places where hostnames or full "
+"destinations\n"
+"are used, however there are some exceptions where they may fail if the\n"
+"name does not immediately resolve. I2PTunnel will fail, for example, if\n"
+"the name does not resolve to a destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:2
+#: i2p2www/pages/site/docs/spec/configuration.html:65
+msgid "Plugins"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:3
+msgid "June 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:6
+msgid "I2P Plugins"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:8
+msgid "General Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:9
+msgid ""
+"I2P includes a plugin architecture\n"
+"to support easy development and installation of additional software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:14
+msgid ""
+"There are now plugins available that support distributed email, blogs, "
+"IRC\n"
+"clients, distributed file storage, wikis, and more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:19
+msgid "Benefits to i2p users and app developers:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:24
+msgid "Easy distribution of applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:28
+msgid ""
+"Allows innovation and use of additional libraries without worrying about\n"
+"increasing the size of i2pupdate.sud"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:33
+msgid ""
+"Support large or special-purpose applications that would never be bundled"
+"\n"
+"with the I2P installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:38
+msgid "Cryptographically signed and verified applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:42
+msgid "Automatic updates of applications, just like for the router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:46
+msgid ""
+"Separate initial install and update packages, if desired, for smaller "
+"update downloads"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:50
+msgid ""
+"One-click installation of applications. No more asking users to modify\n"
+"wrapper.config or clients.config"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:55
+msgid "Isolate applications from the base $I2P installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:59
+msgid ""
+"Automatic compatibility checking for I2P version, Java version, Jetty\n"
+"version, and previous installed application version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:64
+msgid "Automatic link addition in console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:68
+msgid ""
+"Automatic startup of application, including modifying classpath, without "
+"requiring a restart"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:72
+msgid "Automatic integration and startup of webapps into console Jetty instance"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:76
+#, python-format
+msgid ""
+"Facilitate creation of 'app stores' like the one at\n"
+"%(pluginsite)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:81
+msgid "One-click uninstall"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:85
+msgid "Language and theme packs for the console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:89
+msgid "Bring detailed application information to the router console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:93
+msgid "Non-java applications also supported"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:99
+msgid "Required I2P version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:100
+msgid "0.7.12 or newer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:102
+msgid "Installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:103
+msgid ""
+"To install and start a plugin, copy the .xpi2p install link "
+"to\n"
+"the form at the bottom of\n"
+"configclients.jsp"
+" in\n"
+"your router console and click the \"install plugin\" button.  After a"
+"\n"
+"plugin is installed and started, a link to the plugin will usually appear"
+" at\n"
+"the top of your summary bar."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:112
+msgid ""
+"To update a plugin to the latest version, just click the update button on"
+"\n"
+"configclients.jsp."
+"\n"
+"There is also a button to check if the plugin has a more recent version, "
+"as\n"
+"well as a button to check for updates for all plugins.  Plugins will be "
+"checked\n"
+"for updates automatically when updating to a new I2P release (not "
+"including dev\n"
+"builds)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:122
+msgid "Development"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:123
+#, python-format
+msgid ""
+"See the latest plugin specification and "
+"the\n"
+"plugin forum on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:128
+#, python-format
+msgid ""
+"See also the sources for plugins developed by various people.  Some "
+"plugins, such\n"
+"as snowman, were "
+"developed\n"
+"specifically as examples."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:134
+msgid ""
+"Developers wanted! Plugins are a great way to learn more about I2P"
+"\n"
+"or easily add some feature."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:139
+msgid "Getting Started"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:140
+#, python-format
+msgid ""
+"To create a plugin from an existing binary package you will need to get\n"
+"makeplugin.sh from the i2p.scripts branch in "
+"monotone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:146
+msgid "Known Issues"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:147
+msgid ""
+"Note that the router's plugin architecture does NOT currently\n"
+"provide any additional security isolation or sandboxing of plugins."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:153
+msgid ""
+"Updates of a plugin with included jars (not wars) won't be recognized if\n"
+"the plugin was already run, as it requires class loader trickery to flush"
+" the\n"
+"class cache; a full router restart is required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:159
+msgid "The stop button may be displayed even if there is nothing to stop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:163
+msgid ""
+"Plugins running in a separate JVM create a logs/ directory "
+"in\n"
+"$CWD."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:168
+msgid ""
+"No initial keys are present, except for those of jrandom and zzz (using "
+"the\n"
+"same keys as for router update), so the first key seen for a signer is\n"
+"automatically accepted—there is no signing key authority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:174
+msgid ""
+"When deleting a plugin, the directory is not always deleted, especially "
+"on\n"
+"Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:179
+msgid ""
+"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result "
+"in a\n"
+"\"plugin is corrupt\" message if pack200 compression of the plugin file "
+"is used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:184
+msgid "Theme and translation plugins are untested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:188
+msgid "Disabling autostart doesn't always work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:2
+msgid "Ports Used by I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:7
+msgid ""
+"These are the ports used or reserved by I2P, including those for known "
+"plugins,\n"
+"common alternates,\n"
+"and some typical related applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:13
+#, python-format
+msgid ""
+"Note that many of these are not enabled by default.\n"
+"There is more information in the FAQ.\n"
+"See also the documentation for individual plugins.\n"
+"Plugin authors please add any ports you use here.\n"
+"For new plugins, we recommend using the next available port\n"
+"in the 766x range."
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:53
+msgid "recommended spot for new plugins/applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:3
+#: i2p2www/pages/site/docs/api/datagrams.html:3
+#: i2p2www/pages/site/docs/how/garlic-routing.html:3
+#: i2p2www/pages/site/docs/protocol/index.html:3
+msgid "August 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:5
+msgid "BOB - Basic Open Bridge"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:7
+msgid "Technical differences from SAM (for the better?)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:9
+msgid ""
+"BOB has separate command and data channels. \n"
+"One, an application command channel socket to router to configure.\n"
+"Two, the application data sockets to/from router that carry only data.\n"
+"The command channel is only needed for making or setting the initial\n"
+"destination key, and to set the destination key to port bindings. \n"
+"All connections run in parallel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:18
+msgid ""
+"SAM has one connection that does everything, and you need to parse every "
+"packet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:22
+msgid ""
+"BOB does not hold keypair values, nor does the router.\n"
+"Your application holds the keypair values. \n"
+"This is to reduce any extra complexity in the router code, it also adds "
+"to\n"
+"your privacy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:29
+msgid "SAM router stores every keypair you ever make."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:33
+msgid "Those are the important differences."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:37
+msgid "KEYS = keypair public+private, these are BASE64"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:40
+msgid "KEY = public key, also BASE64"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:43
+msgid ""
+"ERROR as is implied returns the message \"ERROR "
+"\"+DESCRIPTION+\"\n"
+"\", where the DESCRIPTION is what went wrong."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:46
+msgid ""
+"OK returns \"OK\", and if data is to be "
+"returned, it is on the same line. OK means the command is "
+"finished."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:49
+msgid ""
+"DATA lines contain information that you requested. There may"
+" be multiple DATA lines per request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:53
+msgid ""
+"NOTE: The help command is the ONLY command that has an exception "
+"to\n"
+"the rules... it can actually return nothing! This is intentional, since\n"
+"help is a HUMAN and not an APPLICATION command."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:59
+msgid ""
+"PLEASE NOTE:\n"
+"For CURRENT details on the commands PLEASE use the built-in help command."
+" \n"
+"Just telnet to localhost 2827 and type help and you can get full "
+"documentation on each command."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:65
+msgid ""
+"Commands never get obsoleted or changed, however new commands do get "
+"added from time to time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:69
+msgid "Here are the commands we have as of this writing:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:74
+msgid "COMMAND"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:74
+msgid "OPERAND"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:74
+msgid "RETURNS"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:101
+msgid ""
+"Once set up, all TCP sockets can and will block as needed, and there is "
+"no need for any \n"
+"additional messages to/from the command channel. This allows the router "
+"to pace the\n"
+"stream without exploding with OOM like SAM does as it chokes on "
+"attempting to shove \n"
+"many streams in or out one socket -- that can't scale when you have alot "
+"of connections!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:108
+msgid ""
+"What is also nice about this particular interface is that writing "
+"anything to interface \n"
+"to it, is much much easier than SAM. There is no other processing to do "
+"after the set up.\n"
+"It's configuration is so simple, that very simple tools, such as nc "
+"(netcat) can be used \n"
+"to point to some application. The value there is that one could schedule "
+"up and down times \n"
+"for an application, and not have to change the application to do that, or"
+" to even have \n"
+"to stop that application. Instead, you can literally \"unplug\" the "
+"destination, and \n"
+"\"plug it in\" again. As long as the same IP/port addresses and "
+"destination keys are used \n"
+"when bringing the bridge up, the normal TCP application won't care, and "
+"won't notice.\n"
+"It will simply be fooled -- the destinations are not reachable, and that "
+"nothing is coming in."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:120
+msgid ""
+"For the following example, we'll setup a very simple local loopback "
+"connection, \n"
+"with two destinations. Destination \"mouth\" will be the CHARGEN service "
+"from \n"
+"the INET superserver daemon. Destination \"ear\" will be a local port "
+"that you\n"
+"can telnet into, and watch the pretty ASCII test puke forth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:128
+msgid "EXAMPLE SESSION DIALOGUE -- simple telnet 127.0.0.1 2827 works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:129
+msgid "Application"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:130
+msgid "BOB's Command response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:132
+#: i2p2www/pages/site/docs/api/bob.html:144
+#: i2p2www/pages/site/docs/api/bob.html:164
+#: i2p2www/pages/site/docs/api/bob.html:272
+#: i2p2www/pages/site/docs/api/bob.html:284
+#: i2p2www/pages/site/docs/api/bob.html:299
+msgid "FROM"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:132
+#: i2p2www/pages/site/docs/api/bob.html:144
+#: i2p2www/pages/site/docs/api/bob.html:164
+#: i2p2www/pages/site/docs/api/bob.html:272
+#: i2p2www/pages/site/docs/api/bob.html:284
+#: i2p2www/pages/site/docs/api/bob.html:299
+msgid "TO"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:132
+#: i2p2www/pages/site/docs/api/bob.html:144
+#: i2p2www/pages/site/docs/api/bob.html:164
+#: i2p2www/pages/site/docs/api/bob.html:272
+#: i2p2www/pages/site/docs/api/bob.html:284
+#: i2p2www/pages/site/docs/api/bob.html:299
+msgid "DIALOGUE"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:139
+msgid "MAKE NOTE OF THE ABOVE DESTINATION KEY, YOURS WILL BE DIFFERENT!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:153
+msgid ""
+"At this point, there was no error, a destination with a nickname of "
+"\"mouth\" \n"
+"is set up. When you contact the destination provided, you actually "
+"connect \n"
+"to the CHARGEN service on 19/TCP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:159
+msgid "Now for the other half, so that we can actually contact this destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:179
+msgid ""
+"Now all we need to do is telnet into 127.0.0.1, port 37337,\n"
+"send the destination key or host address from addressbook we want to "
+"contact.\n"
+"In this case, we want to contact \"mouth\", all we do is paste in the\n"
+"key and it goes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:186
+msgid ""
+"NOTE: The \"quit\" command in the command channel does NOT "
+"disconnect the tunnels like SAM."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:203
+msgid "After a few virtual miles of this spew, press Control-]"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:215
+msgid "Here is what happened..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:223
+msgid "You can connect to EEPSITES too!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:256
+msgid ""
+"Pretty cool isn't it? Try some other well known EEPSITES if you like, "
+"nonexistent ones, \n"
+"etc, to get a feel for what kind of output to expect in different "
+"situations. \n"
+"For the most part, it is suggested that you ignore any of the error "
+"messages. \n"
+"They would be meaningless to the application, and are only presented for "
+"human debugging."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:263
+msgid "Let's put down our destinations now that we are all done with them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:267
+msgid "First, lets see what destination nicknames we have."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:279
+msgid "Alright, there they are. First, let's remove \"mouth\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:293
+msgid ""
+"Now to remove \"ear\", note that this is what happens when you type too "
+"fast,\n"
+"and shows you what typical ERROR messages looks like."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:312
+msgid ""
+"I won't bother to show an example of the receiver end of a bridge\n"
+"because it is very simple. There are two possible settings for it, and\n"
+"it is toggled with the \"quiet\" command."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:318
+msgid ""
+"The default is NOT quiet, and the first data to come into your\n"
+"listening socket is the destination that is making the contact. It is a\n"
+"single line consisting of the BASE64 address followed by a newline.\n"
+"Everything after that is for the application to actually consume."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:325
+msgid ""
+"In quiet mode, think of it as a regular Internet connection. No\n"
+"extra data comes in at all. It's just as if you are plain connected to\n"
+"the regular Internet. This mode allows a form of transparency much like\n"
+"is available on the router console tunnel settings pages, so that you\n"
+"can use BOB to point a destination at a web server, for example, and\n"
+"you would not have to modify the web server at all."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:334
+msgid ""
+"The advantage with using BOB for this is as discussed\n"
+"previously. You could schedule random uptimes for the application,\n"
+"redirect to a different machine, etc. One use of this may be something\n"
+"like wanting to try to goof up router-to-destination upness guessing.\n"
+"You could stop and start the destination with a totally different\n"
+"process to make random up and down times on services. That way you\n"
+"would only be stopping the ability to contact such a service, and not\n"
+"have to bother shutting it down and restarting it. You could redirect\n"
+"and point to a different machine on your LAN while you do updates, or\n"
+"point to a set of backup machines depending on what is running, etc,\n"
+"etc. Only your imagination limits what you could do with BOB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:6
+msgid "Datagram Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:7
+#, python-format
+msgid ""
+"Datagrams build upon the base I2CP to provide "
+"authenticated\n"
+"and repliable messages in a standard format.  This lets applications "
+"reliably read\n"
+"the \"from\" address out of a datagram and know that the address really "
+"sent the\n"
+"message.  This is necessary for some applications since the base I2P "
+"message is\n"
+"completely raw - it has no \"from\" address (unlike IP packets).  In "
+"addition, the\n"
+"message and sender are authenticated by signing the payload."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:16
+#, python-format
+msgid ""
+"Datagrams, like streaming library packets,\n"
+"are an application-level construct.\n"
+"These protocols are independent of the low-level transports;\n"
+"the protocols are converted to I2NP messages by the router, and\n"
+"either protocol may be carried by either transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:25
+msgid "Application Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:26
+#, python-format
+msgid ""
+"Applications written in Java may use the \n"
+"datagram API,\n"
+"while applications in other languages \n"
+"can use SAM's datagram support.\n"
+"There is also limited support in i2ptunnel in the SOCKS proxy,\n"
+"the 'streamr' tunnel types, and udpTunnel classes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:37
+msgid "Datagram Length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:38
+msgid ""
+"The application designer should carefully consider the tradeoff of "
+"repliable vs. non-repliable\n"
+"datagrams. Also, the datagram size will affect reliability, due to tunnel"
+" fragmentation into 1KB\n"
+"tunnel messages. The more message fragments, the more likely that one of "
+"them will be dropped\n"
+"by an intermediate hop. Messages larger than a few KB are not "
+"recommended.\n"
+"Over about 10 KB, the delivery probablility drops dramatically.\n"
+"Messages over 16 KB cannot be delivered over NTCP, dropping delivery "
+"chances even more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:47
+#, python-format
+msgid ""
+"Also note that the various overheads added by lower layers, in particular"
+" asymmetric\n"
+"ElGamal/AES, place a large burden on "
+"intermittent messages\n"
+"such as used by a Kademlia-over-UDP application. The implementations are "
+"currently tuned\n"
+"for frequent traffic using the streaming library. There are a high number"
+"\n"
+"of session tags delivered, and a short session tag lifetime, for example."
+"\n"
+"There are currently no configuration parameters available within I2CP to "
+"tune\n"
+"the ElGamal Session Tag parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:57
+msgid "I2CP Protocol Number and Ports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:58
+msgid ""
+"The standard I2CP protocol number for datagrams is PROTO_DATAGRAM (17).\n"
+"Applications may or may not choose to set the\n"
+"protocol in the I2CP header. It is not set by default.\n"
+"It must be set to demultiplex datagram and streaming traffic received on "
+"the same Destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:65
+#, python-format
+msgid ""
+"As datagrams are not connection-oriented, the application may require\n"
+"port numbers to correlate datagrams with particular peers or "
+"communications sessions,\n"
+"as is traditional with UDP over IP.\n"
+"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as "
+"described in\n"
+"the I2CP page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:73
+#, python-format
+msgid ""
+"There is no method within the datagram API to specify whether it is non-"
+"repliable (raw)\n"
+"or repliable. The application should be designed to expect the "
+"appropriate type.\n"
+"The I2CP protocol number or port should be used by the application to\n"
+"indicate datagram type.\n"
+"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW "
+"are defined in the\n"
+"I2PSession API\n"
+"for this purpose. A common design pattern in client/server datagram "
+"applications is to\n"
+"use signed datagrams for a request which includes a nonce, and use a raw "
+"datagram\n"
+"for the reply, returning the nonce from the request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:85
+#, python-format
+msgid ""
+"The protocols and ports may be set in I2CP's\n"
+"I2PSession API,\n"
+"as implemented in\n"
+"I2PSessionMuxedImpl."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:93
+#: i2p2www/pages/site/docs/api/streaming.html:381
+msgid "Data Integrity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:94
+#, python-format
+msgid ""
+"Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
+"the I2CP layer.\n"
+"There is no checksum field in the datagram protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:100
+#: i2p2www/pages/site/docs/api/streaming.html:389
+msgid "Packet Encapsulation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:101
+#, python-format
+msgid ""
+"Each datagram is sent through I2P as a single message (or as an "
+"individual clove in a\n"
+"Garlic Message).\n"
+"Message encapsulation is implemented in the underlying\n"
+"I2CP,\n"
+"I2NP, and\n"
+"tunnel message layers.\n"
+"There is no packet delimiter mechanism or length field in the datagram "
+"protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:114
+#: i2p2www/pages/site/docs/spec/datagrams.html:10
+#: i2p2www/pages/site/docs/transport/ssu.html:571
+msgid "Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:116
+msgid "See the Datagrams Specification page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:4
+msgid "I2PControl - Remote Control Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:5
+#, python-format
+msgid ""
+"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n"
+"The aim of the interface is to provide simple way to interface with a "
+"running I2P node. A client, itoopie, has been developed in parallel.\n"
+"The JSONRPC2 implementation for the client as well as the plugin is "
+"provided by the java libraries JSON-RPC 2.0.  \n"
+"A list of implementations of JSON-RPC for various languages can be found "
+"at the JSON-RPC "
+"wiki."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:12
+msgid "I2PControl is by default listening on localhost:7650"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:14
+msgid "API, version 1."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:15
+msgid "Parameters are only provided in a named way (maps)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:19
+msgid "JSON-RPC 2 format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:21
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:27
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:40
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:50
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:59
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:69
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:84
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:137
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:154
+msgid "Request:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:23
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:32
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:44
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:54
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:64
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:75
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:101
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:145
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:169
+msgid "Response:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:26
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:28
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:29
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:33
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:34
+#: i2p2www/pages/site/docs/protocol/i2cp.html:107
+#: i2p2www/pages/site/docs/protocol/i2cp.html:450
+#: i2p2www/pages/site/docs/spec/common-structures.html:16
+#: i2p2www/pages/site/docs/spec/common-structures.html:26
+#: i2p2www/pages/site/docs/spec/common-structures.html:37
+#: i2p2www/pages/site/docs/spec/common-structures.html:49
+#: i2p2www/pages/site/docs/spec/common-structures.html:64
+#: i2p2www/pages/site/docs/spec/common-structures.html:77
+#: i2p2www/pages/site/docs/spec/common-structures.html:90
+#: i2p2www/pages/site/docs/spec/common-structures.html:102
+#: i2p2www/pages/site/docs/spec/common-structures.html:114
+#: i2p2www/pages/site/docs/spec/common-structures.html:126
+#: i2p2www/pages/site/docs/spec/common-structures.html:138
+#: i2p2www/pages/site/docs/spec/common-structures.html:150
+#: i2p2www/pages/site/docs/spec/common-structures.html:162
+#: i2p2www/pages/site/docs/spec/common-structures.html:174
+#: i2p2www/pages/site/docs/spec/common-structures.html:227
+#: i2p2www/pages/site/docs/spec/common-structures.html:310
+#: i2p2www/pages/site/docs/spec/common-structures.html:359
+#: i2p2www/pages/site/docs/spec/common-structures.html:411
+#: i2p2www/pages/site/docs/spec/common-structures.html:456
+#: i2p2www/pages/site/docs/spec/common-structures.html:593
+#: i2p2www/pages/site/docs/spec/common-structures.html:655
+msgid "Description"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:30
+msgid ""
+"Token used for authenticating every request (excluding the 'Authenticate'"
+" RPC method)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:38
+msgid "Implemented methods"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:39
+msgid ""
+"Creates and returns an authentication token used for further "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:41
+msgid "The version of the I2PControl API used by the client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:42
+msgid "The password used for authenticating against the remote server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:45
+msgid "The primary I2PControl API version implemented by the server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:46
+msgid "The token used for further communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:49
+msgid "Echoes the value of the echo key, used for debugging and testing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:51
+msgid "Value will be returned in response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:52
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:62
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:73
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:99
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:143
+msgid ""
+"Token used for authenticating the client. Is provided by the server via "
+"the 'Authenticate' RPC method."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:55
+msgid "Value of the key 'echo' in the request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:58
+msgid ""
+"Fetches rateStat from router statManager. Creates stat if not already "
+"created."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:60
+#, python-format
+msgid ""
+"Determines which rateStat to fetch, see ratestats."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:61
+msgid "Determines which period a stat is fetched for. Measured in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:65
+msgid "Returns the average value for the reuested rateStat and period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:68
+msgid "Manages I2PControl. Ports, passwords and the like."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:70
+msgid ""
+"Sets a new listen address for I2PControl (only 127.0.0.1 and 0.0.0.0 are "
+"implemented in I2PControl currently)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:71
+msgid ""
+"Sets a new password for I2PControl, all Authentication tokens will be "
+"revoked."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:72
+msgid "Switches which port I2PControl will listen for connections on."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:76
+msgid "Returned if address was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:77
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:78
+msgid "Returned if setting was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:79
+msgid "Returns true if any changes were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:80
+msgid "Returns true if any changes requiring a restart to take effect were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:83
+msgid "Fetches basic information about the I2P router. Uptime, version etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:102
+msgid "What the status of the router is."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:103
+msgid "What the uptime of the router is in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:104
+msgid "What version of I2P the router is running."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:105
+msgid "The 1 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:106
+msgid "The 15 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:107
+msgid "The 1 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:108
+msgid "The 15 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:109
+msgid "What the current network status is. According to the below enum:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:128
+msgid "How many tunnels on the I2P net are we participating in."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:129
+msgid "How many peers have we communicated with recently."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:130
+msgid "How many peers are considered 'fast'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:131
+msgid "How many peers are considered 'high capacity'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:132
+msgid "Is the router reseeding hosts to its NetDB?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:133
+msgid "How many peers are known to us (listed in our NetDB)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:136
+msgid "Manages I2P router restart/shutdown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:138
+msgid ""
+"Initiates a router reseed, fetching peers into our NetDB from a remote "
+"host."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:139
+msgid "Restarts the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:140
+msgid ""
+"Restarts the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:141
+msgid "Shuts down the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:142
+msgid ""
+"Shuts down the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:146
+msgid "If requested, verifies that a reseed has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:147
+msgid "If requested, verifies that a restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:148
+msgid "If requested, verifies that a graceful restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:149
+msgid "If requested, verifies that a shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:150
+msgid "If requested, verifies that a graceful shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:153
+msgid "Fetches or sets various network related settings. Ports, addresses etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:155
+msgid ""
+"What port is used for the TCP transport. If null is submitted, current "
+"setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:156
+msgid ""
+"What hostname is used for the TCP transport. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:157
+msgid ""
+"Use automatically detected ip for TCP transport. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:158
+msgid ""
+"What port is used for the UDP transport. If null is submitted, current "
+"setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:159
+msgid ""
+"What hostname is used for the UDP transport. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:160
+msgid ""
+"Which methods should be used for detecting the ip address of the UDP "
+"transport. If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:161
+msgid "What ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:162
+msgid "Is UPnP enabled. If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:163
+msgid ""
+"How many percent of bandwidth is usable for participating tunnels. If "
+"null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:164
+msgid ""
+"How many KB/s of inbound bandwidth is allowed. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:165
+msgid ""
+"How many KB/s of outbound bandwidth is allowed. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:166
+msgid ""
+"Is laptop mode enabled (change router identity and UDP port when IP "
+"changes ). If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:167
+msgid ""
+"Token used for authenticating the client. Is provided by the server via "
+"the 'Authenticate' RPC method. If null is submitted, current setting will"
+" be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:170
+msgid "If requested, returns the port used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:171
+msgid "If requested, returns the hostname used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:172
+msgid ""
+"If requested, returns the method used for automatically detecting ip for "
+"the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:173
+msgid "If requested, returns the port used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:174
+msgid "If requested, returns the hostname used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:175
+msgid ""
+"If requested, returns methods used for detecting the ip address of the "
+"UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:176
+msgid "If requested, returns what ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:177
+msgid "If requested, returns the UPNP setting."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:178
+msgid ""
+"If requested, returns how many percent of bandwidth is usable for "
+"participating tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:179
+msgid "If requested, returns how many KB/s of inbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:180
+msgid "If requested, returns how many KB/s of outbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:181
+msgid "If requested, returns the laptop mode."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:182
+msgid "Have the provided settings been saved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:183
+msgid "Is a restart needed for the new settings to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:186
+msgid "denotes an optional value."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:187
+msgid "denotes a possibly occuring return value"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:189
+msgid "Error codes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:190
+msgid "Standard JSON-RPC2 error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:191
+msgid "JSON parse error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:192
+msgid "Invalid request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:193
+msgid "Method not found."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:194
+msgid "Invalid parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:195
+msgid "Internal error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
+msgid "I2PControl specific error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
+msgid "Invalid password provided."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
+msgid "No authentication token presented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
+msgid "Authentication token doesn't exist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
+msgid "The provided authentication token was expired and will be removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
+msgid ""
+"The version of the I2PControl API used wasn't specified, but is required "
+"to be specified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:203
+msgid ""
+"The version of the I2PControl API specified is not supported by "
+"I2PControl."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:13
+#, python-format
+msgid ""
+"I2PTunnel is a tool for interfacing with and providing services on I2P.\n"
+"Destination of an I2PTunnel can be defined using a hostname,\n"
+"Base32, or a full 516-byte destination "
+"key.\n"
+"An established I2PTunnel will be available on your client machine as "
+"localhost:port.\n"
+"If you wish to provide a service on I2P network, you simply create "
+"I2PTunnel to the\n"
+"appropriate ip_address:port. A corresponding 516-byte destination key "
+"will be generated\n"
+"for the service and it will become avaliable throughout I2P.\n"
+"A web interface for I2PTunnel management is avaliable on\n"
+"localhost:7657/i2ptunnel/."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:25
+msgid "Default Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:26
+msgid "Server tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:28
+msgid ""
+"I2P Webserver - A tunnel pointed to a Jetty webserver run\n"
+"on localhost:7658 for convenient "
+"and quick hosting on I2P.\n"
+"
            The document root is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:36
+msgid "Client tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:38
+msgid ""
+"A HTTP proxy used for browsing I2P and the regular internet anonymously "
+"through I2P. \n"
+"Browsing internet through I2P uses a random proxy specified by the "
+"\"Outproxies:\" option."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:42
+msgid "An IRC tunnel to the default anonymous IRC network, Irc2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:43
+#, python-format
+msgid ""
+"The anonymous monotone\n"
+"sourcecode repository for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:47
+#, python-format
+msgid ""
+"A SMTP service provided by postman at %(postman)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:50
+#, python-format
+msgid ""
+"The accompanying POP sevice of postman at %(postman)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:55
+msgid "Client Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:56
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:138
+msgid "Standard"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:57
+msgid ""
+"Opens a local TCP port that connects to a service (like HTTP, FTP or "
+"SMTP) on a destination inside of I2P.\n"
+"The tunnel is directed to a random host from the comma seperated (\", \")"
+" list of destinations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:63
+msgid ""
+"A HTTP-client tunnel. The tunnel connects to the destination specified by"
+" the URL\n"
+"in a HTTP request. Supports proxying onto internet if an outproxy is "
+"provided. Strips HTTP connections of the following headers:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:68
+msgid ""
+"Accept, Accept-Charset, Accept-Encoding, Accept-Language\n"
+" and Accept-Ranges as they vary greatly between browsers and can be "
+"used as an identifier."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:76
+msgid ""
+"HTTP client/server tunnels are via I2Ptunnel force-enabling compression "
+"via the following http headers:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:83
+msgid ""
+"Depending on if the tunnel is using an outproxy or not it will append the"
+" following User-Agent:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:87
+msgid "Outproxy:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:88
+msgid "Internal I2P use:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:93
+msgid ""
+"Creates a connection to a random IRC server specified by the comma "
+"seprated (\", \") \n"
+"list of destinations. Only a whitelisted subset of IRC commands are "
+"allowed due to anonymity concerns."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:97
+msgid "Whitelist:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:112
+msgid "Enables using the I2P router as a SOCKS proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:117
+msgid ""
+"Enables using the I2P router as a SOCKS proxy with the command whitelist "
+"specified by\n"
+"IRC client mode."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:123
+msgid ""
+"Creates a HTTP tunnel and uses the HTTP request method \"CONNECT\" \n"
+"to build a TCP tunnel that usually is used for SSL and HTTPS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:129
+msgid ""
+"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr "
+"client tunnel will \n"
+"subscribe to a streamr server tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:137
+msgid "Server Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:139
+msgid "Creates a destination to a local ip:port with an open TCP port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:144
+msgid ""
+"Creates a destination to a local HTTP server ip:port. Supports gzip for "
+"requests with \n"
+"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in"
+" such a request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:150
+msgid ""
+"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client "
+"with no outproxying\n"
+"capabilities. An example application would be a web application that does"
+" client-type\n"
+"requests, or loopback-testing an eepsite as a diagnostic tool."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:157
+msgid ""
+"Creates a destination that filters the reqistration sequence of a client "
+"and passes \n"
+"the clients destination key as a hostname to the IRC-server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:163
+msgid ""
+"A UDP-client that connects to a media server is created. The UDP-Client "
+"is coupled with a Streamr server I2PTunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:2
+#: i2p2www/pages/site/docs/api/ministreaming.html:17
+msgid "Ministreaming Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:5
+msgid "Note"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:7
+#, python-format
+msgid ""
+"The ministreaming library has been enhanced and extended by the\n"
+"\"full\" streaming library.\n"
+"Ministreaming is deprecated and is incompatible with today's "
+"applications.\n"
+"The following documentation is old.\n"
+"Also note that streaming extends ministreaming in the same Java package "
+"(net.i2p.client.streaming),\n"
+"so the current API documentation contains both.\n"
+"Obsolete ministreaming classes and methods are clearly marked as "
+"deprecated in the Javadocs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:19
+#, python-format
+msgid ""
+"\n"
+"The ministreaming library is a layer on top of the core \n"
+"I2CP that allows reliable, in order, and "
+"authenticated streams\n"
+"of messages to operate across an unreliable, unordered, and "
+"unauthenticated \n"
+"message layer.  Just like the TCP to IP relationship, this streaming \n"
+"functionality has a whole series of tradeoffs and optimizations "
+"available, but\n"
+"rather than embed that functionality into the base I2P code, it has been "
+"factored\n"
+"off into its own library both to keep the TCP-esque complexities separate"
+" and to\n"
+"allow alternative optimized implementations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:30
+#, python-format
+msgid ""
+"The ministreaming library was written by mihi as a part of his \n"
+"I2PTunnel application and then factored out"
+" and released\n"
+"under the BSD license.  It is called the \"mini\"streaming library "
+"because it makes\n"
+"some simplifications in the implementation, while a more robust streaming"
+" library\n"
+"could be further optimized for operation over I2P.  The two main issues "
+"with \n"
+"the ministreaming library are its use of the traditional TCP two phase \n"
+"establishment protocol and the current fixed window size of 1.  The "
+"establishment\n"
+"issue is minor for long lived streams, but for short ones, such as quick "
+"HTTP\n"
+"requests, the impact can be significant.  As "
+"for the window\n"
+"size, the ministreaming library doesn't maintain any ID or ordering "
+"within the \n"
+"messages sent (or include any application level ACK or SACK), so it must "
+"wait \n"
+"on average twice the time it takes to send a message before sending "
+"another."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:45
+#, python-format
+msgid ""
+"Even with those issues, the ministreaming library performs quite well in "
+"many\n"
+"situations, and its API\n"
+"is both quite simple and capable of remaining unchanged as different "
+"streaming\n"
+"implementations are introduced.  The library is deployed in its own \n"
+"ministreaming.jar.\n"
+"Developers in Java who would like to use it can\n"
+"access the API directly, while developers in other languages can use it "
+"through\n"
+"SAM's streaming support."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:4
+msgid "SOCKS and SOCKS proxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:5
+msgid ""
+"\n"
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"Enable SOCKS by creating a SOCKS client tunnel in i2ptunnel.\n"
+"Both shared-clients and non-shared are supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:12
+#, python-format
+msgid ""
+"\n"
+"As it says on the FAQ:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:15
+msgid ""
+"Many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:25
+msgid "And quoting from a 2005 email:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:28
+msgid ""
+"... there is a reason why human and\n"
+"others have both built and abandoned the SOCKS proxies.  Forwarding\n"
+"arbitrary traffic is just plain unsafe, and it behooves us as\n"
+"developers of anonymity and security software to have the safety of\n"
+"our end users foremost in our minds."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:36
+msgid ""
+"Hoping that we can simply strap an arbitrary client on top of I2P\n"
+"without auditing both its behavior and its exposed protocols for\n"
+"security and anonymity is naive.  Pretty much *every* application\n"
+"and protocol violates anonymity, unless it was designed for it\n"
+"specifically, and even then, most of those do too.  That's the\n"
+"reality.  End users are better served with systems designed for\n"
+"anonymity and security.  Modifying existing systems to work in\n"
+"anonymous environments is no small feat, orders of magnitude more\n"
+"work that simply using the existing I2P APIs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:48
+msgid ""
+"The SOCKS proxy\n"
+"supports standard addressbook names, but not Base64 destinations.\n"
+"Base32 hashes should work as of release 0.7.\n"
+"It supports outgoing connections only, i.e. an I2PTunnel Client.\n"
+"UDP support is stubbed out but not working yet.\n"
+"Outproxy selection by port number is stubbed out."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:57
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:281
+msgid "See Also"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:59
+#, python-format
+msgid ""
+"The notes for Meeting 81 and\n"
+"Meeting 82 in March 2004."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:69
+msgid "If You Do Get Something Working"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:70
+msgid ""
+"Please let us know. And please provide substantial warnings about the\n"
+"risks of socks proxies."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:8
+#, python-format
+msgid ""
+"The streaming library is technically part of the \"application\" layer,\n"
+"as it is not a core router function.\n"
+"In practice, however, it provides a vital function for almost all\n"
+"existing I2P applications, by providing a TCP-like\n"
+"streams over I2P, and allowing existing apps to be easily ported to I2P.\n"
+"The other end-to-end transport library for client communication is the\n"
+"datagram library."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:18
+#, python-format
+msgid ""
+"The streaming library is a layer on top of the core \n"
+"I2CP API that allows reliable, in-order, and "
+"authenticated streams\n"
+"of messages to operate across an unreliable, unordered, and "
+"unauthenticated \n"
+"message layer.  Just like the TCP to IP relationship, this streaming \n"
+"functionality has a whole series of tradeoffs and optimizations "
+"available, but\n"
+"rather than embed that functionality into the base I2P code, it has been "
+"factored\n"
+"off into its own library both to keep the TCP-esque complexities separate"
+" and to\n"
+"allow alternative optimized implementations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:29
+msgid ""
+"In consideration of the relatively high cost of messages, \n"
+"the streaming library's protocol for scheduling and delivering those "
+"messages has been optimized to\n"
+"allow individual messages passed to contain as much information as is "
+"available.\n"
+"For instance, a small HTTP transaction proxied through the streaming "
+"library can\n"
+"be completed in a single round trip - the first messages bundle a SYN, "
+"FIN, and\n"
+"the small HTTP request payload, and the reply bundles the SYN,\n"
+"FIN, ACK, and the HTTP response payload.  While an additional\n"
+"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has "
+"been\n"
+"received, the local HTTP proxy can often deliver the full response to the"
+" browser \n"
+"immediately."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:42
+msgid ""
+"The streaming library bears much resemblance to an \n"
+"abstraction of TCP, with its sliding windows, congestion control "
+"algorithms\n"
+"(both slow start and congestion avoidance), and general packet behavior "
+"(ACK,\n"
+"SYN, FIN, RST, rto calculation, etc)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:49
+msgid ""
+"The streaming library is\n"
+"a robust library\n"
+"which is optimized for operation over I2P.\n"
+"It has a one-phase setup, and\n"
+"it contains a full windowing implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:58
+msgid "API"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:60
+#, python-format
+msgid ""
+"The streaming library API provides a standard socket paradigm to Java "
+"applications.\n"
+"The lower-level I2CP API is completely hidden, "
+"except that\n"
+"applications may pass I2CP parameters "
+"through the\n"
+"streaming library, to be interpreted by I2CP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:67
+#, python-format
+msgid ""
+"The standard interface to the streaming lib is for the application to use"
+" the\n"
+"I2PSocketManagerFactory to create an\n"
+"I2PSocketManager. The application then asks "
+"the\n"
+"socket manager for an I2PSession, which will "
+"cause\n"
+"a connection to the router via I2CP. The "
+"application\n"
+"can then setup connections with an I2PSocket "
+"or\n"
+"receive connections with an I2PServerSocket."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:82
+#, python-format
+msgid "Here are the full streaming library Javadocs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:86
+msgid "For a good example of usage, see the i2psnark code."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:91
+msgid "Options and Defaults"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:92
+#, python-format
+msgid ""
+"The options and current default values are listed below.\n"
+"Options are case-sensitive and may be set for the whole router, for a "
+"particular client, or for an individual socket on a\n"
+"per-connection basis.\n"
+"Many values are tuned for HTTP performance over typical I2P conditions. "
+"Other applications such\n"
+"as peer-to-peer services are strongly encouraged to\n"
+"modify as necessary, by setting the options and passing them via the call"
+" to\n"
+"I2PSocketManagerFactory.createManager(_i2cpHost,"
+" _i2cpPort, opts).\n"
+"Time values are in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:103
+#, python-format
+msgid ""
+"Note that higher-layer APIs, such as SAM,\n"
+"BOB, and I2PTunnel,"
+"\n"
+"may override these defaults with their own defaults.\n"
+"Also note that many options only apply to servers listening for incoming "
+"connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:110
+msgid ""
+"As of release 0.9.1, most, but not all, options may be changed on an "
+"active socket manager or session.\n"
+"See the javadocs for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/protocol/i2cp.html:102
+#: i2p2www/pages/site/docs/protocol/i2cp.html:445
+msgid "Option"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/protocol/i2cp.html:106
+#: i2p2www/pages/site/docs/protocol/i2cp.html:449
+msgid "Default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:267
+#: i2p2www/pages/site/docs/how/peer-selection.html:282
+#: i2p2www/pages/site/docs/spec/common-structures.html:58
+#: i2p2www/pages/site/docs/spec/common-structures.html:203
+#: i2p2www/pages/site/docs/spec/common-structures.html:257
+#: i2p2www/pages/site/docs/spec/common-structures.html:351
+#: i2p2www/pages/site/docs/spec/common-structures.html:445
+#: i2p2www/pages/site/docs/spec/common-structures.html:553
+#: i2p2www/pages/site/docs/spec/common-structures.html:631
+#: i2p2www/pages/site/docs/spec/common-structures.html:739
+#: i2p2www/pages/site/docs/spec/datagrams.html:30
+#: i2p2www/pages/site/docs/spec/datagrams.html:89
+msgid "Notes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:119
+msgid ""
+"Comma- or space-separated list of Base64 peer Hashes used for either "
+"access list or blacklist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:121
+#: i2p2www/pages/site/docs/api/streaming.html:127
+#: i2p2www/pages/site/docs/api/streaming.html:133
+#: i2p2www/pages/site/docs/api/streaming.html:140
+#: i2p2www/pages/site/docs/api/streaming.html:152
+#: i2p2www/pages/site/docs/api/streaming.html:163
+#: i2p2www/pages/site/docs/api/streaming.html:192
+#: i2p2www/pages/site/docs/api/streaming.html:200
+#: i2p2www/pages/site/docs/api/streaming.html:220
+#: i2p2www/pages/site/docs/api/streaming.html:237
+#: i2p2www/pages/site/docs/api/streaming.html:249
+#: i2p2www/pages/site/docs/api/streaming.html:255
+#: i2p2www/pages/site/docs/api/streaming.html:261
+#: i2p2www/pages/site/docs/api/streaming.html:275
+#: i2p2www/pages/site/docs/api/streaming.html:282
+#: i2p2www/pages/site/docs/api/streaming.html:289
+#: i2p2www/pages/site/docs/api/streaming.html:314
+#: i2p2www/pages/site/docs/api/streaming.html:321
+#: i2p2www/pages/site/docs/api/streaming.html:328
+#, python-format
+msgid "As of release %(release)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:125
+msgid "Use the access list as a whitelist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:131
+msgid "Use the access list as a blacklist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:145
+msgid "Whether to respond to incoming pings"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:157
+msgid ""
+"Comma- or space-separated list of Base64 peer Hashes to be\n"
+"blacklisted for incoming connections to ALL destinations in the context.\n"
+"This option must be set in the context properties, NOT in the "
+"createManager() options argument.\n"
+"Note that setting this in the router context will not affect clients "
+"outside the\n"
+"router in a separate JVM and context."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:167
+msgid ""
+"How much transmit data (in bytes) will be accepted that hasn't been "
+"written out yet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:171
+msgid ""
+"When we're in congestion avoidance, we grow the window size at the rate\n"
+"of 1/(windowSize*factor).  In standard TCP, window sizes are"
+" in bytes,\n"
+"while in I2P, window sizes are in messages.\n"
+"A higher number means slower growth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:178
+msgid ""
+"How long to wait after instantiating a new con \n"
+"before actually attempting to connect.  If this is\n"
+"<= 0, connect immediately with no initial data.  If greater than 0, "
+"wait\n"
+"until the output stream is flushed, the buffer fills, \n"
+"or that many milliseconds pass, and include any initial data with the SYN."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:186
+msgid ""
+"How long to block on connect, in milliseconds. Negative means "
+"indefinitely. Default is 5 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:190
+msgid ""
+"Whether to disable warnings in the logs when an incoming connection is "
+"rejected due to connection limits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:196
+msgid ""
+"Whether to listen only for the streaming protocol.\n"
+"Setting to true will prohibit communication with Destinations earlier "
+"than release 0.7.1\n"
+"(released March 2009). Set to true if running multiple protocols on this "
+"Destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:204
+msgid ""
+"(0=noop, 1=disconnect)\n"
+"What to do on an inactivity timeout - do nothing, disconnect, or send a "
+"duplicate ack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:212
+msgid ""
+"The initial value of the resend delay field in the packet header, times "
+"1000.\n"
+"Not fully implemented; see below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:217
+msgid ""
+"Initial timeout\n"
+"(if no sharing data available)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:224
+msgid ""
+"Initial round trip time estimate\n"
+"(if no sharing data available).\n"
+"Disabled as of release 0.9.8; uses actual RTT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
+msgid "if no sharing data available"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
+msgid ""
+"In standard TCP, window sizes are in bytes, while in I2P, window sizes "
+"are in messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:242
+msgid ""
+"(0 or negative value means unlimited)\n"
+"This is a total limit for incoming and outgoing combined."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:247
+msgid "Incoming connection limit (per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:253
+#: i2p2www/pages/site/docs/api/streaming.html:259
+msgid "(per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:265
+msgid "The MTU in bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:269
+msgid "Maximum number of retransmissions before failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:273
+msgid "Incoming connection limit (all peers; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:279
+#: i2p2www/pages/site/docs/api/streaming.html:286
+msgid ""
+"(all peers; 0 means disabled)\n"
+"Use with caution as exceeding this will disable a server for a long time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:295
+msgid ""
+"(2=interactive not supported)\n"
+"This doesn't currently do anything, but setting it to a value other than "
+"1 will cause an error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:300
+msgid "How long to block on read, in milliseconds. Negative means indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:304
+msgid ""
+"When we're in slow start, we grow the window size at the rate\n"
+"of 1/(factor).  In standard TCP, window sizes are in bytes,\n"
+"while in I2P, window sizes are in messages.\n"
+"A higher number means slower growth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:311
+#: i2p2www/pages/site/docs/api/streaming.html:318
+#: i2p2www/pages/site/docs/api/streaming.html:325
+msgid ""
+"Ref: RFC 2140. Floating point value.\n"
+"May be set only via context properties, not connection options."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:332
+msgid ""
+"How long to block on write/flush, in milliseconds. Negative means "
+"indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:340
+#: i2p2www/pages/site/docs/spec/streaming.html:10
+msgid "Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:342
+msgid "See the Streaming Library Specification page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:346
+msgid "Implementation Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:348
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:349
+msgid ""
+"The initiator sends a packet with the SYNCHRONIZE flag set. This packet "
+"may contain the initial data as well.\n"
+"The peer replies with a packet with the SYNCHRONIZE flag set. This packet"
+" may contain the initial response data as well."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:354
+msgid ""
+"The initiator may send additional data packets, up to the initial window "
+"size, before receiving the SYNCHRONIZE response.\n"
+"These packets will also have the send Stream ID field set to 0.\n"
+"Recipients must buffer packets received on unknown streams for a short "
+"period of time, as they may\n"
+"arrive out of order, in advance of the SYNCHRONIZE packet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:361
+msgid "MTU Selection and Negotiation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:362
+msgid ""
+"The maximum message size (also called the MTU / MRU) is negotiated to the"
+" lower value supported by\n"
+"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection"
+" will lead to\n"
+"a large amount of overhead.\n"
+"The MTU is specified by the option i2p.streaming.maxMessageSize.\n"
+"The current default MTU of 1730 was chosen to fit precisely into two 1K "
+"I2NP tunnel messages,\n"
+"including overhead for the typical case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:371
+msgid ""
+"The first message in a connection includes a 387 byte (typical) "
+"Destination added by the streaming layer,\n"
+"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in "
+"the Garlic message by the router.\n"
+"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session "
+"was previously established).\n"
+"Therefore, the goal of fitting a complete HTTP request in a single 1KB "
+"I2NP message is not always attainable.\n"
+"However, the selection of the MTU, together with careful implementation "
+"of fragmentation\n"
+"and batching strategies in the tunnel gateway processor, are important "
+"factors in network bandwidth,\n"
+"latency, reliability, and efficiency, especially for long-lived "
+"connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:382
+#, python-format
+msgid ""
+"Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
+"the I2CP layer.\n"
+"There is no checksum field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:390
+#, python-format
+msgid ""
+"Each packet is sent through I2P as a single message (or as an individual "
+"clove in a\n"
+"Garlic Message). Message encapsulation "
+"is implemented\n"
+"in the underlying I2CP, I2NP, and\n"
+"tunnel message layers. There is no "
+"packet delimiter\n"
+"mechanism or payload length field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:400
+msgid "Windowing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:401
+msgid ""
+"The streaming lib uses standard slow-start (exponential window growth) "
+"and congestion avoidance (linear window growth)\n"
+"phases, with exponential backoff.\n"
+"Windowing and acknowledgments use packet count, not byte count."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:408
+msgid "Close"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:409
+msgid ""
+"Any packet, including one with the SYNCHRONIZE flag set, may have the "
+"CLOSE flag sent as well.\n"
+"The connection is not closed until the peer responds with the CLOSE flag."
+"\n"
+"CLOSE packets may contain data as well."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:417
+msgid ""
+"There is no ping function at the I2CP layer (equivalent to ICMP echo) or "
+"in datagrams.\n"
+"This function is provided in streaming.\n"
+"Pings and pongs may not be combined with a standard streaming packet;\n"
+"if the ECHO option is set, then\n"
+"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. "
+"are ignored."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:425
+msgid ""
+"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED "
+"flags set.\n"
+"The sendStreamId must be greater than zero, and the receiveStreamId is "
+"ignored.\n"
+"The sendStreamId may or may not correspond to an existing connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:431
+msgid ""
+"A pong packet must have the ECHO flag set.\n"
+"The sendStreamId must be zero, and the receiveStreamId is the "
+"sendStreamId from the ping.\n"
+"The pong packet does not include any payload that was contained in the "
+"ping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:437
+msgid ""
+"Streaming may be configured to disable sending pongs with the "
+"configuration i2p.streaming.answerPings=false."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:442
+msgid "Control Block Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:443
+msgid ""
+"The streaming lib supports \"TCP\" Control Block sharing.\n"
+"This shares three important streaming lib parameters\n"
+"(window size, round trip time, round trip time variance)\n"
+"across connections to the same remote peer.\n"
+"This is used for \"temporal\" sharing at connection open/close time,\n"
+"not \"ensemble\" sharing during a connection (See\n"
+"RFC 2140).\n"
+"There is a separate share per ConnectionManager (i.e. per local "
+"Destination)\n"
+"so that there is no information leakage to other Destinations on the\n"
+"same router.\n"
+"The share data for a given peer expires after a few minutes.\n"
+"The following Control Block Sharing parameters can be set per router:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:464
+msgid "Other Parameters"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:465
+msgid ""
+"The following parameters are hardcoded, but may be of interest for "
+"analysis:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:484
+#: i2p2www/pages/site/docs/how/network-database.html:843
+msgid "History"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:485
+msgid ""
+"The streaming library has grown organically for I2P - first mihi "
+"implemented the\n"
+"\"mini streaming library\" as part of I2PTunnel, which was limited to a "
+"window\n"
+"size of 1 message (requiring an ACK before sending the next one), and "
+"then it was\n"
+"refactored out into a generic streaming interface (mirroring TCP sockets)"
+" and the\n"
+"full streaming implementation was deployed with a sliding window protocol"
+" and \n"
+"optimizations to take into account the high bandwidth x delay product.  "
+"Individual\n"
+"streams may adjust the maximum packet size and other options. The default"
+"\n"
+"message size is selected to fit precisely in two 1K I2NP tunnel messages,"
+"\n"
+"and is a reasonable tradeoff between the bandwidth costs of \n"
+"retransmitting lost messages, and the latency and overhead of multiple "
+"messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:499
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:331
+#: i2p2www/pages/site/docs/how/garlic-routing.html:242
+#: i2p2www/pages/site/docs/how/network-database.html:848
+#: i2p2www/pages/site/docs/how/peer-selection.html:265
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:255
+#: i2p2www/pages/site/docs/protocol/i2cp.html:654
+#: i2p2www/pages/site/docs/protocol/i2np.html:227
+#: i2p2www/pages/site/docs/spec/updates.html:280
+#: i2p2www/pages/site/docs/transport/ntcp.html:446
+#: i2p2www/pages/site/docs/transport/ssu.html:506
+#: i2p2www/pages/site/docs/tunnels/implementation.html:503
+msgid "Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:500
+msgid ""
+"The behavior of the streaming library has a profound impact on\n"
+"application-level performance, and as such, is an important\n"
+"area for further analysis."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:506
+msgid "Additional tuning of the streaming lib parameters may be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:509
+#, python-format
+msgid ""
+"Another area for research is the interaction of the streaming lib with "
+"the\n"
+"NTCP and SSU transport layers.\n"
+"See the NTCP discussion page for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:514
+msgid ""
+"The interaction of the routing algorithms with the streaming lib strongly"
+" affects performance.\n"
+"In particular, random distribution of messages to multiple tunnels in a "
+"pool\n"
+"leads to a high degree of out-of-order delivery which results in smaller "
+"window\n"
+"sizes than would otherwise be the case. The router currently routes \n"
+"messages for a single from/to destination pair through a consistent set \n"
+"of tunnels, until tunnel expiration or delivery failure. The router's \n"
+"failure and tunnel selection algorithms should be reviewed for possible \n"
+"improvements."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:524
+msgid "The data in the first SYN packet may exceed the receiver's MTU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:527
+msgid "The DELAY_REQUESTED field could be used more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:530
+msgid ""
+"Duplicate initial SYNCHRONIZE packets on short-lived streams may not be "
+"recognized and removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:533
+msgid "Don't send the MTU in a retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:536
+msgid ""
+"Data is sent along unless the outbound window is full.\n"
+"(i.e. no-Nagle or TCP_NODELAY)\n"
+"Probably should have a configuration option for this."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:541
+msgid ""
+"zzz has added debug code to the streaming library to log packets in a "
+"wireshark-compatible\n"
+"(pcap) format; Use this to further analyze performance.\n"
+"The format may require enhancement to map more streaming lib parameters "
+"to TCP fields."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:546
+msgid ""
+"There are proposals to replace the streaming lib with standard TCP\n"
+"(or perhaps a null layer together with raw sockets).\n"
+"This would unfortunately be incompatible with the streaming lib\n"
+"but it would be good to compare the performance of the two."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:3
+#: i2p2www/pages/site/docs/spec/configuration.html:3
+msgid "September 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:7
+msgid ""
+"There are several bittorrent clients and trackers on I2P.\n"
+"As I2P addressing uses a Destination instead of an IP and port, minor\n"
+"changes are required to tracker and client software for operation on I2P."
+"\n"
+"These changes are specified below.\n"
+"Note carefully the guidelines for compatibility with older I2P clients "
+"and trackers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:15
+msgid ""
+"This page specifies protocol details common to all clients and trackers.\n"
+"Specific clients and trackers may implement other unique features or "
+"protocols."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:20
+msgid "We welcome additional ports of client and tracker software to I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:26
+msgid "Announces"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:27
+msgid ""
+"Clients generally include a fake port=6881 parameter in the announce, for"
+" compatibility with older trackers.\n"
+"Trackers may ignore the port parameter, and should not require it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:32
+#, python-format
+msgid ""
+"The ip parameter is the base 64 of the client's\n"
+"Destination,\n"
+"using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n"
+"Destinations\n"
+"are 387+ bytes, so the Base 64 is 516+ bytes.\n"
+"Clients generally append \".i2p\" to the Base 64 Destination for "
+"compatibility with older trackers.\n"
+"Trackers should not require an appended \".i2p\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:42
+msgid "Other parameters are the same as in standard bittorrent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:46
+msgid ""
+"While all current Destinations for clients are exactly 387 bytes, a "
+"tracker should not\n"
+"presume that will always be so. A reasonable maximum to assume, for now, "
+"is 475 bytes.\n"
+"As the tracker must decode the Base64 to deliver compact responses (see "
+"below),\n"
+"the tracker should probably decode and reject bad Base64 when announced."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:53
+msgid ""
+"The default response type is non-compact. Clients may request a compact "
+"response with\n"
+"the parameter compact=1. A tracker may, but is not required to, return\n"
+"a compact response when requested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:59
+msgid ""
+"Developers of new I2P clients\n"
+"are strongly encouraged to implemenent announces over their own tunnel "
+"rather than\n"
+"the HTTP client proxy at port 4444. Doing so is both more efficient and "
+"it allows\n"
+"destination enforcement by the tracker (see below)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:66
+msgid ""
+"There are no known I2P clients or trackers that currently support UDP "
+"announce/responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:71
+msgid "Non-Compact Tracker Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:72
+msgid ""
+"The non-compact response is just as in standard bittorrent, with an I2P "
+"\"ip\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:76
+msgid ""
+"Trackers generally include a fake port key, or use the port from the "
+"announce, for compatibility with older clients.\n"
+"Clients must ignore the port parameter, and should not require it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:81
+#, python-format
+msgid ""
+"The value of the ip key is the base 64 of the client's\n"
+"Destination, as "
+"described above.\n"
+"Trackers generally append \".i2p\" to the Base 64 Destination if it "
+"wasn't in the announce ip, for compatibility with older clients.\n"
+"Clients should not require an appended \".i2p\" in the responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:88
+msgid "Other response keys and values are the same as in standard bittorrent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:94
+msgid "Compact Tracker Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:95
+#, python-format
+msgid ""
+"In the compact response, the value of the \"peers\" dictionary key is a "
+"single byte string,\n"
+"whose length is a multiple of 32 bytes.\n"
+"This string contains the concatenated\n"
+"32-byte SHA-256 Hashes\n"
+"of the binary\n"
+"Destinations\n"
+"of the peers.\n"
+"This hash must be computed by the tracker, unless destination enforcement"
+"\n"
+"(see below) is used, in which case the hash delivered in the X-I2P-"
+"DestHash\n"
+"or X-I2P-DestB32 HTTP headers may be converted to binary and stored.\n"
+"The peers key may be absent, or the peers value may be zero-length."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:109
+msgid ""
+"While compact response support is optional for both clients and trackers,"
+" it is highly\n"
+"recommended as it reduces the nominal response size by over 90%."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:116
+msgid "Destination Enforcement"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:117
+#, python-format
+msgid ""
+"Some, but not all, I2P bittorrent clients announce over their own "
+"tunnels.\n"
+"Trackers may choose to prevent spoofing by requiring this, and verifying "
+"the\n"
+"client's\n"
+"Destination\n"
+"using HTTP headers added by the I2PTunnel HTTP Server tunnel.\n"
+"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which "
+"are\n"
+"different formats for the same information.\n"
+"These headers cannot be spoofed by the client.\n"
+"A tracker enforcing destinations need not require the ip announce "
+"parameter at all."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:129
+msgid ""
+"As several clients use the HTTP proxy instead of their own tunnel for "
+"announces,\n"
+"destination enforcement will prevent usage by those clients unless or "
+"until\n"
+"those clients are converted to announcing over their own tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:135
+msgid ""
+"Unfortunately, as the network grows, so will the amount of maliciousness,"
+"\n"
+"so we expect that all trackers will eventually enforce destinations.\n"
+"Both tracker and client developers should anticipate it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:143
+msgid "Announce Host Names"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:144
+#, python-format
+msgid ""
+"Announce URL host names in torrent files generally follow the\n"
+"I2P naming standards.\n"
+"In addition to host names from address books and \".b32.i2p\" Base 32 "
+"hostnames,\n"
+"the full Base 64 Destination (with [or without?] \".i2p\" appended) "
+"should be supported.\n"
+"Non-open trackers should recognize their own host name in any of these "
+"formats."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:152
+msgid ""
+"To preserve anonymity,\n"
+"clients should generally ignore non-I2P announce URLs in torrent files."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:159
+msgid "Client Connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:160
+msgid ""
+"Client-to-client connections use the standard protocol over TCP.\n"
+"There are no known I2P clients that currently support uTP communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:165
+#, python-format
+msgid ""
+"I2P uses 387+ byte Destinations\n"
+"for addresses, as explained above."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:170
+msgid ""
+"If the client has only the hash of the destination (such as from a "
+"compact response or PEX), it must perform a lookup\n"
+"by encoding it with Base 32, appending \".b32.i2p\", and querying the "
+"Naming Service,\n"
+"which will return the full Destination if available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:176
+msgid ""
+"If the client has a peer's full Destination it received in a non-compact "
+"response, it should use it\n"
+"directly in the connection setup.\n"
+"Do not convert a Destination back to a Base 32 hash for lookup, this is "
+"quite inefficient."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:183
+msgid "Cross-Network Prevention"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:184
+msgid ""
+"To preserve anonymity,\n"
+"I2P bittorrent clients generally do not support non-I2P announces or peer"
+" connections.\n"
+"I2P HTTP outproxies often block announces.\n"
+"There are no known SOCKS outproxies supporting bittorrent traffic."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:191
+msgid ""
+"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers "
+"often\n"
+"block accesses or announces that contain an X-Forwarded-For HTTP header.\n"
+"Trackers should reject standard network announces with IPv4 or IPv6 IPs, "
+"and not deliver them in responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:200
+#, python-format
+msgid ""
+"I2P PEX is based on ut_pex.\n"
+"As there does not appear to be a formal specification of ut_pex "
+"available,\n"
+"it may be necessary to review the libtorrent source for assistance.\n"
+"It is an extension message, identified as \"i2p_pex\" in\n"
+"the extension "
+"handshake.\n"
+"It contains a bencoded dictionary with up to 3 keys, \"added\", "
+"\"added.f\", and \"dropped\".\n"
+"The added and dropped values are each a single byte string, whose length "
+"is a multiple of 32 bytes.\n"
+"These byte strings are the concatenated SHA-256 Hashes of the binary\n"
+"Destinations\n"
+"of the peers.\n"
+"This is the same format as the peers dictionary value in the i2p compact "
+"response format specified above.\n"
+"The added.f value, if present, is the same as in ut_pex."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:218
+msgid ""
+"DHT support is included in the i2psnark client as of version 0.9.2.\n"
+"Preliminary differences from\n"
+"BEP 5\n"
+"are described below, and are subject to change.\n"
+"Contact the I2P developers if you wish to develop a client supporting DHT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:226
+msgid ""
+"Unlike standard DHT, I2P DHT does not use a bit in the options handshake,"
+" or the PORT message.\n"
+"It is advertised with an extension message, identified as \"i2p_dht\" in\n"
+"the extension "
+"handshake.\n"
+"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", "
+"both integers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:233
+msgid ""
+"The UDP (datagram) port listed in the compact node info is used\n"
+"to receive repliable (signed) datagrams.\n"
+"This is used for queries, except for announces.\n"
+"We call this the \"query port\".\n"
+"This is the \"port\" value from the extension message.\n"
+"Queries use I2CP protocol number 17."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:242
+msgid ""
+"In addition to that UDP port, we use a second datagram\n"
+"port equal to the query port + 1. This is used to receive\n"
+"unsigned (raw) datagrams for replies, errors, and announces.\n"
+"This port provides increased efficiency since replies\n"
+"contain tokens sent in the query, and need not be signed.\n"
+"We call this the \"response port\".\n"
+"This is the \"rport\" value from the extension message.\n"
+"It must be 1 + the query port.\n"
+"Responses and announces use I2CP protocol number 18."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:254
+msgid ""
+"Compact peer info is 32 bytes (32 byte SHA256 Hash)\n"
+"instead of 4 byte IP + 2 byte port. There is no peer port.\n"
+"In a response, the \"values\" key is a list of strings, each containing a"
+" single compact peer info."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:260
+msgid ""
+"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + "
+"2 byte port)\n"
+"instead of 20 byte SHA1 Hash + 4 byte IP + 2 byte port.\n"
+"In a response, the \"nodes\" key is a\n"
+"single byte string with concatenated compact node info."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:267
+msgid ""
+"Secure node ID requirement: To make various DHT attacks more difficult,\n"
+"the first 4 bytes of the Node ID must match the first 4 bytes of the "
+"destination Hash,\n"
+"and the next two bytes of the Node ID must match the next two bytes of "
+"the\n"
+"destination hash exclusive-ORed with the port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:274
+msgid ""
+"In a torrent file,\n"
+"the trackerless torrent dictionary \"nodes\" key is TBD.\n"
+"It could be a list of\n"
+"32 byte binary strings (SHA256 Hashes) instead of a list of lists\n"
+"containing a host string and a port integer.\n"
+"Alternatives: A single byte string with concatenated hashes,\n"
+"or a list of strings alone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:285
+#: i2p2www/pages/site/docs/how/intro.html:187
+msgid "Additional Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:287
+#, python-format
+msgid ""
+"I2P bittorrent standards are generally discussed on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:290
+#, python-format
+msgid ""
+"A chart of current tracker software capabilities is also available there."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:293
+#, python-format
+msgid ""
+"The\n"
+"I2P bittorrent FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:297
+#, python-format
+msgid "DHT on I2P discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:2
+#: i2p2www/pages/site/docs/applications/supported.html:5
+msgid "Supported Applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:9
+#: i2p2www/pages/site/docs/applications/supported.html:186
+msgid "Blogging, Forums, and Wikis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:11
+#: i2p2www/pages/site/docs/applications/supported.html:232
+msgid "Decentralized File Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:14
+#: i2p2www/pages/site/docs/applications/supported.html:244
+msgid "Development Tools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:17
+#: i2p2www/pages/site/docs/applications/supported.html:246
+msgid "Version control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:21
+#: i2p2www/pages/site/docs/applications/supported.html:265
+msgid "Domain Naming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:23
+#: i2p2www/pages/site/docs/applications/supported.html:283
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:26
+#: i2p2www/pages/site/docs/applications/supported.html:328
+msgid "File Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:29
+#: i2p2www/pages/site/docs/applications/supported.html:330
+msgid "BitTorrent clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:31
+#: i2p2www/pages/site/docs/applications/supported.html:372
+msgid "BitTorrent trackers and indexers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:40
+#: i2p2www/pages/site/docs/applications/supported.html:439
+msgid "Network Administration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:43
+#: i2p2www/pages/site/docs/applications/supported.html:441
+msgid "General-purpose socket utilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:50
+#: i2p2www/pages/site/docs/applications/supported.html:482
+msgid "Real-time Chat"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:53
+#: i2p2www/pages/site/docs/applications/supported.html:484
+msgid "Instant messaging clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:55
+#: i2p2www/pages/site/docs/applications/supported.html:494
+msgid "IRC clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:57
+#: i2p2www/pages/site/docs/applications/supported.html:545
+msgid "IRC servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:62
+#: i2p2www/pages/site/docs/applications/supported.html:561
+msgid "Web Browsing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:65
+#: i2p2www/pages/site/docs/applications/supported.html:563
+msgid "Anonymous websites"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:67
+#: i2p2www/pages/site/docs/applications/supported.html:612
+msgid "Proxy software"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:69
+#: i2p2www/pages/site/docs/applications/supported.html:637
+msgid "Inproxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:71
+#: i2p2www/pages/site/docs/applications/supported.html:669
+msgid "Outproxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:76
+#: i2p2www/pages/site/docs/applications/supported.html:683
+msgid "Website Hosting"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:79
+#: i2p2www/pages/site/docs/applications/supported.html:698
+msgid "Web servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:85
+#, python-format
+msgid ""
+"This is intended to be a comprehensive listing of applications used with\n"
+"I2P. If you know of something that's missing please submit a ticket on\n"
+"Trac, and be sure to select the\n"
+"“www” component in the submission form."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:92
+msgid ""
+"\n"
+"Supported applications are tagged with one or more of the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:97
+#: i2p2www/pages/site/docs/applications/supported.html:279
+#: i2p2www/pages/site/docs/applications/supported.html:311
+#: i2p2www/pages/site/docs/applications/supported.html:336
+#: i2p2www/pages/site/docs/applications/supported.html:695
+msgid "bundled"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:100
+msgid ""
+"Bundled application — I2P ships with a few officially\n"
+"supported applications that let new users take immediate advantage of\n"
+"some of I2P's more useful capabilities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:107
+#: i2p2www/pages/site/docs/applications/supported.html:195
+#: i2p2www/pages/site/docs/applications/supported.html:208
+#: i2p2www/pages/site/docs/applications/supported.html:220
+#: i2p2www/pages/site/docs/applications/supported.html:228
+#: i2p2www/pages/site/docs/applications/supported.html:241
+#: i2p2www/pages/site/docs/applications/supported.html:292
+#: i2p2www/pages/site/docs/applications/supported.html:404
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:523
+msgid "plugin"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:110
+#, python-format
+msgid ""
+"Third-party plugin — I2P's plugin system provides convenient\n"
+"deployment of I2P-enabled applications and allows tighter integration\n"
+"with the router. Plugins are [reviewed by the community](http://%(plugins)s) to identify security and\n"
+"anonymity issues."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:121
+#: i2p2www/pages/site/docs/applications/supported.html:220
+#: i2p2www/pages/site/docs/applications/supported.html:228
+#: i2p2www/pages/site/docs/applications/supported.html:241
+#: i2p2www/pages/site/docs/applications/supported.html:252
+#: i2p2www/pages/site/docs/applications/supported.html:261
+#: i2p2www/pages/site/docs/applications/supported.html:324
+#: i2p2www/pages/site/docs/applications/supported.html:342
+#: i2p2www/pages/site/docs/applications/supported.html:353
+#: i2p2www/pages/site/docs/applications/supported.html:368
+#: i2p2www/pages/site/docs/applications/supported.html:414
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:450
+#: i2p2www/pages/site/docs/applications/supported.html:456
+#: i2p2www/pages/site/docs/applications/supported.html:462
+#: i2p2www/pages/site/docs/applications/supported.html:472
+#: i2p2www/pages/site/docs/applications/supported.html:478
+#: i2p2www/pages/site/docs/applications/supported.html:490
+#: i2p2www/pages/site/docs/applications/supported.html:523
+#: i2p2www/pages/site/docs/applications/supported.html:529
+#: i2p2www/pages/site/docs/applications/supported.html:535
+#: i2p2www/pages/site/docs/applications/supported.html:541
+#: i2p2www/pages/site/docs/applications/supported.html:618
+#: i2p2www/pages/site/docs/applications/supported.html:627
+#: i2p2www/pages/site/docs/applications/supported.html:633
+#: i2p2www/pages/site/docs/applications/supported.html:695
+#: i2p2www/pages/site/docs/applications/supported.html:710
+#: i2p2www/pages/site/docs/applications/supported.html:716
+#: i2p2www/pages/site/docs/applications/supported.html:722
+#: i2p2www/pages/site/docs/applications/supported.html:728
+msgid "standalone"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:121
+#: i2p2www/pages/site/docs/applications/supported.html:195
+#: i2p2www/pages/site/docs/applications/supported.html:202
+#: i2p2www/pages/site/docs/applications/supported.html:208
+#: i2p2www/pages/site/docs/applications/supported.html:214
+#: i2p2www/pages/site/docs/applications/supported.html:362
+#: i2p2www/pages/site/docs/applications/supported.html:386
+#: i2p2www/pages/site/docs/applications/supported.html:395
+#: i2p2www/pages/site/docs/applications/supported.html:551
+#: i2p2www/pages/site/docs/applications/supported.html:557
+msgid "standalone/mod"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:124
+msgid ""
+"Third-party standalone application — Many standard network\n"
+"applications only require careful setup and configuration to communicate\n"
+"anonymously over I2P. These are tagged with standalone. Some\n"
+"applications, tagged with standalone/mod, require patching to\n"
+"function properly over I2P or to prevent inadvertent disclosure of\n"
+"identifying information such as the user's hostname or external IP\n"
+"address."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:135
+#: i2p2www/pages/site/docs/applications/supported.html:302
+#: i2p2www/pages/site/docs/applications/supported.html:571
+#: i2p2www/pages/site/docs/applications/supported.html:581
+#: i2p2www/pages/site/docs/applications/supported.html:590
+#: i2p2www/pages/site/docs/applications/supported.html:596
+#: i2p2www/pages/site/docs/applications/supported.html:602
+#: i2p2www/pages/site/docs/applications/supported.html:608
+#: i2p2www/pages/site/docs/applications/supported.html:649
+#: i2p2www/pages/site/docs/applications/supported.html:657
+#: i2p2www/pages/site/docs/applications/supported.html:665
+#: i2p2www/pages/site/docs/applications/supported.html:679
+msgid "service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:138
+msgid ""
+"Third-party essential network service — Services which on\n"
+"the I2P network are analogous to those provided on the public Internet\n"
+"by hosting providers, ISPs, and Google: eepsite indexes and jump\n"
+"services, search engines, email, DNS-style name services, hosting,\n"
+"proxies, etc. These services focus on boosting the usefulness of the\n"
+"network as a whole, and making network content more discoverable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:148
+#: i2p2www/pages/site/docs/applications/supported.html:220
+#: i2p2www/pages/site/docs/applications/supported.html:368
+msgid "unmaintained"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:151
+msgid ""
+"Unmaintained — This is used to tag plugins, applications,\n"
+"and services which appear to be unmaintained and may be removed from\n"
+"this listing in the future."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:159
+#, python-format
+msgid ""
+"Warning: Using an application, plugin, or service with I2P\n"
+"doesn't automatically protect your anonymity. I2P is merely a set of "
+"tools\n"
+"which can help you mitigate certain identified\n"
+"threats to anonymity. We do not and cannot make any guarantees about "
+"the\n"
+"safety of the applications, plugins, and services listed below. Most\n"
+"applications and plugins must be properly configured, and some will need "
+"to\n"
+"be patched — and even then your anonymity might not be assured. "
+"Similarly,\n"
+"services could put your anonymity at risk, either by design or through\n"
+"carelessness on their part or your own."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:171
+msgid ""
+"If you have doubts about the suitability of an application,\n"
+"plugin, or service for use with I2P, you are urged to inquire about "
+"privacy\n"
+"issues with its maintainers, to search its mailing lists and bug tracker "
+"if\n"
+"one exists, and consult trusted, knowledgeable members of the I2P\n"
+"community."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:179
+msgid ""
+"Take responsibility for your own anonymity and safety — always\n"
+"seek expert advice, educate yourself, practice good judgment, be mindful "
+"of\n"
+"disclosing personally identifying information, and don't take\n"
+"shortcuts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:201
+msgid "Lightweight forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:207
+msgid "Another lightweight blogging platform."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:213
+msgid "Most popular open source forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:219
+msgid "Distributed forums software, originally developed by jrandom."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:224
+#, python-format
+msgid ""
+"A Java-based MediaWiki clone. No external database needed.\n"
+"Plugin available here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:236
+#, python-format
+msgid ""
+"Port of the Tahoe-"
+"LAFS\n"
+"distributed file system to the I2P network. Controller plugin here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:251
+msgid "Most popular distributed version control system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:257
+#, python-format
+msgid ""
+"Another distributed version control system. Currently\n"
+"used in I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:269
+#, python-format
+msgid ""
+"Provides management of addressbooks, which are part of a simple,\n"
+"user-controlled I2P naming system somewhat\n"
+"analogous to the Internet's Domain Name System (DNS). Addressbooks map\n"
+"Base64 destinations to short, usually human-readable “domain” names "
+"ending\n"
+"with a .i2p suffix which the I2P router's HTTP client can resolve back to"
+"\n"
+"Base64 addresses. (Note: While Base64 destinations are globally\n"
+"unique, addressbook “domain” names only resolve to unique destinations\n"
+"locally.)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:288
+msgid ""
+"Serverless peer-to-peer email application using a distributed hash table\n"
+"(DHT) for secure mail storage."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:297
+msgid ""
+"Provides email service within the I2P network via @mail.i2p addresses,\n"
+"and email gateway service between the I2P network and the public Internet"
+"\n"
+"via @i2pmail.org addresses. One of the oldest continuous services on I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:307
+msgid ""
+"Simple web browser-based email interface. Configured to use Postman's\n"
+"email service by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:316
+#, python-format
+msgid ""
+"Can be configured to use Postman's email service. See\n"
+"this comparison of MUAs,\n"
+"and configuration settings for\n"
+"SMTP and POP3."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:335
+msgid "I2P's integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:341
+msgid "Modified version of I2PSnark."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:347
+msgid ""
+"\n"
+"A fork of rufus that uses the Basic Open Bridge (BOB) and has many\n"
+"improvements, including using the latest wxwidgets and python. It also\n"
+"supports use of seedless if installed for trackerless torrents and\n"
+"magnet-link like fetching of torrents within I2P.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:358
+msgid ""
+"Clean, full-featured cross-platform BitTorrent client with official\n"
+"ports for several GUI toolkits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:367
+msgid "Has a plugin providing I2P support."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:374
+#, python-format
+msgid ""
+"For a detailed feature comparison of I2P-enabled trackers/indexers, see\n"
+"here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:382
+msgid ""
+"The code that powered one of the first major tracker/indexer sites on the"
+"\n"
+"Internet. Patched for I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:391
+#, python-format
+msgid ""
+"Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n"
+"branch of the I2P Monotone repository."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:400
+#, python-format
+msgid ""
+"zzz's Java-based open tracker. More info\n"
+"here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:413
+msgid "I2P port of the aMule ED2K client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:422
+#, python-format
+msgid ""
+"Port of the Phex Gnutella "
+"client. Website\n"
+"for plugin version here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:431
+#, python-format
+msgid ""
+"Cache for Gnutella peers on I2P. Website for plugin version\n"
+"here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:446
+msgid ""
+"Unix standard tool for socket relaying. Several clones, ports, and forks\n"
+"have appeared over the years."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:455
+msgid "Like netcat but more powerful."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:461
+msgid ""
+"Proxy providing simple, transparent SOCKS-ification of network "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:471
+msgid ""
+"Most popular implementation of the Secure Shell (SSH) protocol and "
+"related tools."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:477
+msgid "Open source Secure Shell (SSH) client for Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:489
+msgid "IM client with multiple incarnations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:496
+msgid ""
+"Many IRC clients leak identifying information to servers or other\n"
+"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound"
+"\n"
+"and outbound messages to scrub data such as LAN IP addresses, external IP"
+"\n"
+"addresses, local hostnames, and the name and version of the IRC client. "
+"Two\n"
+"message types in particular, DCC and CTCP, can't be sufficiently "
+"anonymized\n"
+"without changes to the protocols or to IRC client/server code, so they "
+"are\n"
+"completely blocked, except for CTCP ACTION (the message emitted by the\n"
+"/me command) which isn't inherently dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:507
+msgid ""
+"I2P's IRC filtering may not cover every possible leak — users should also"
+"\n"
+"check if their client is sending their real name or local username. "
+"Packet\n"
+"sniffers such as Wireshark are\n"
+"useful here. Eliminating remaining leaks may be as simple as changing the"
+"\n"
+"client's default configuration. If that doesn't help, inform the I2P\n"
+"developers; they may be able to solve it via additional filtering."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:519
+#, python-format
+msgid ""
+"Small Java-based IRC client. Plugin available here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:528
+msgid "Cross-platform graphical IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:534
+msgid "Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:540
+msgid "Another Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:550
+msgid "IRC server developed from scratch."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:556
+msgid "Most popular IRC server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:568
+msgid ""
+"Any website hosted anonymously on I2P, reachable through the I2P router's"
+" HTTP proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:576
+msgid ""
+"Distributed anonymous websites hosted\n"
+"using Tahoe-LAFS-I2P, currently only reachable with Tahoe-LAFS-I2P\n"
+"clients or through the Tahoe-LAFS-I2P HTTP proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:586
+#, python-format
+msgid ""
+"Website for sponge's jump service.\n"
+"Source code available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:595
+msgid "Another jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:601
+msgid "Dynamically updated eepsite index."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:607
+#, python-format
+msgid "Website for zzz's jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:617
+msgid "SOCKS-enabled caching web proxy with basic filtering capabilities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:623
+msgid ""
+"Privacy-focused non-caching web proxy with advanced filtering\n"
+"capabilities. Excels at removing ads and other junk."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:632
+msgid "Venerable caching web proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:639
+msgid "Gateways allowing users on the public Internet to access eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:646
+#, python-format
+msgid "tino's inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:654
+#: i2p2www/pages/site/docs/applications/supported.html:662
+msgid "Another inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:671
+msgid ""
+"Gateways allowing I2P users to access content hosted on the public "
+"Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:678
+msgid "Publicly advertised outproxy running Squid, located in Germany."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:688
+msgid ""
+"Lightweight web server and Java servlet container. I2P is tightly\n"
+"integrated with a bundled copy of Jetty which by default is configured to"
+"\n"
+"host the user's eepsite. The "
+"bundled\n"
+"Jetty also serves the I2P router console and web applications bundled "
+"with\n"
+"I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:700
+msgid ""
+"In addition to Jetty, any web server should function over I2P without\n"
+"modification so long as it's HTTP-compliant. Some web servers known to\n"
+"currently serve content on the I2P network are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:709
+msgid "Most popular web server on the public WWW."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:715
+msgid "Web server and Java servlet container. More features than Jetty."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:721
+msgid "Fast lightweight web server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:727
+msgid "High-performance lightweight web server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:2
+msgid "Naming discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:4
+#, python-format
+msgid ""
+"NOTE: The following is a discussion of the reasons behind the I2P naming "
+"system,\n"
+"common arguments and possible alternatives.\n"
+"See the naming page for current documentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:10
+msgid "Discarded alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:12
+msgid ""
+"Naming within I2P has been an oft-debated topic since the very beginning "
+"with\n"
+"advocates across the spectrum of possibilities.  However, given I2P's "
+"inherent\n"
+"demand for secure communication and decentralized operation, the "
+"traditional\n"
+"DNS-style naming system is clearly out, as are \"majority rules\" voting "
+"systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:19
+msgid ""
+"I2P does not promote the use of DNS-like services though, as the damage "
+"done\n"
+"by hijacking a site can be tremendous - and insecure destinations have no"
+"\n"
+"value.  DNSsec itself still falls back on registrars and certificate "
+"authorities,\n"
+"while with I2P, requests sent to a destination cannot be intercepted or "
+"the reply\n"
+"spoofed, as they are encrypted to the destination's public keys, and a "
+"destination\n"
+"itself is just a pair of public keys and a certificate.  DNS-style "
+"systems on the\n"
+"other hand allow any of the name servers on the lookup path to mount "
+"simple denial\n"
+"of service and spoofing attacks.  Adding on a certificate authenticating "
+"the\n"
+"responses as signed by some centralized certificate authority would "
+"address many of\n"
+"the hostile nameserver issues but would leave open replay attacks as well"
+" as \n"
+"hostile certificate authority attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:33
+msgid ""
+"Voting style naming is dangerous as well, especially given the "
+"effectiveness of\n"
+"Sybil attacks in anonymous systems - the attacker can simply create an "
+"arbitrarily\n"
+"high number of peers and \"vote\" with each to take over a given name.  "
+"Proof-of-work\n"
+"methods can be used to make identity non-free, but as the network grows "
+"the load\n"
+"required to contact everyone to conduct online voting is implausible, or "
+"if the\n"
+"full network is not queried, different sets of answers may be reachable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:42
+msgid ""
+"As with the Internet however, I2P is keeping the design and operation of "
+"a \n"
+"naming system out of the (IP-like) communication layer.  The bundled "
+"naming library\n"
+"includes a simple service provider interface which alternate naming systems can\n"
+"plug into, allowing end users to drive what sort of naming tradeoffs they"
+" prefer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:50
+msgid ""
+"See also Names: "
+"Decentralized, Secure, Human-Meaningful: Choose Two."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:55
+msgid "(adapted from a post in the old Syndie, November 26, 2005)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:58
+msgid ""
+"Q:\n"
+"What to do if some hosts \n"
+"do not agree on one address and if some addresses are working, others are"
+" not? \n"
+"Who is the right source of a name?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:64
+msgid ""
+"A:\n"
+"You don't. This is actually a critical difference between names on I2P "
+"and how \n"
+"DNS works - names in I2P are human readable, secure, but not globally"
+" \n"
+"unique.  This is by design, and an inherent part of our need for "
+"security."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:70
+msgid ""
+"If I could somehow convince you to change the destination associated with"
+" some \n"
+"name, I'd successfully \"take over\" the site, and under no circumstances"
+" is that \n"
+"acceptable.  Instead, what we do is make names locally unique: "
+"they are \n"
+"what you use to call a site, just as how you can call things "
+"whatever \n"
+"you want when you add them to your browser's bookmarks, or your IM "
+"client's \n"
+"buddy list.  Who you call \"Boss\" may be who someone else calls "
+"\"Sally\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:78
+msgid "Names will not, ever, be securely human readable and globally unique."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:83
+msgid ""
+"The following from zzz is a review of several common\n"
+"complaints about I2P's naming system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:89
+msgid ""
+"Inefficiency:\n"
+"The whole hosts.txt is downloaded (if it has changed, since eepget uses "
+"the etag and last-modified headers).\n"
+"It's about 400K right now for almost 800 hosts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:94
+msgid ""
+"True, but this isn't a lot of traffic in the context of i2p, which is "
+"itself wildly inefficient\n"
+"(floodfill databases, huge encryption overhead and padding, garlic "
+"routing, etc.).\n"
+"If you downloaded a hosts.txt file from someone every 12 hours it "
+"averages out to about 10 bytes/sec."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:99
+msgid ""
+"As is usually the case in i2p, there is a fundamental tradeoff here "
+"between anonymity and efficiency.\n"
+"Some would say that using the etag and last-modified headers is hazardous"
+" because it exposes when you\n"
+"last requested the data.\n"
+"Others have suggested asking for specific keys only (similar to what jump"
+" services do, but\n"
+"in a more automated fashion), possibly at a further cost in anonymity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:106
+#, python-format
+msgid ""
+"Possible improvements would be a replacement or supplement to addressbook"
+" (see %(i2host)sp),\n"
+"or something simple like subscribing to http://example.i2p/cgi-"
+"bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n"
+"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 "
+"hours, for example,\n"
+"that could be both more efficient and more anonymous than the current "
+"hosts.txt with last-modified and etag."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:112
+#, python-format
+msgid ""
+"A sample implementation is on stats.i2p at\n"
+"%(url)s.\n"
+"This script returns an Etag with a timestamp.\n"
+"When a request comes in with the If-None-Match etag,\n"
+"the script ONLY returns new hosts since that timestamp, or 304 Not "
+"Modified if there are none.\n"
+"In this way, the script efficiently returns only the hosts the subscriber"
+"\n"
+"does not know about, in an addressbook-compatible manner."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:121
+msgid ""
+"So the inefficiency is not a big issue and there are several ways to "
+"improve things without\n"
+"radical change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:127
+msgid ""
+"Not Scalable:\n"
+"The 400K hosts.txt (with linear search) isn't that big at the moment and\n"
+"we can probably grow by 10x or 100x before it's a problem."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:132
+msgid ""
+"As far as network traffic see above.\n"
+"But unless you're going to do a slow real-time query over the network for"
+"\n"
+"a key, you need to have the whole set of keys stored locally, at a cost "
+"of about 500 bytes per key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:139
+msgid ""
+"Requires configuration and \"trust\":\n"
+"Out-of-the-box addressbook is only subscribed to "
+"http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n"
+"leading to poor new-user experience."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:144
+msgid ""
+"This is very much intentional. jrandom wants a user to \"trust\" a "
+"hosts.txt\n"
+"provider, and as he likes to say, \"trust is not a boolean\".\n"
+"The configuration step attempts to force users to think about issues of "
+"trust in an anonymous network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:149
+msgid ""
+"As another example, the \"Eepsite Unknown\" error page in the HTTP Proxy\n"
+"lists some jump services, but doesn't \"recommend\" any one in "
+"particular,\n"
+"and it's up to the user to pick one (or not).\n"
+"jrandom would say we trust the listed providers enough to list them but "
+"not enough to\n"
+"automatically go fetch the key from them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:156
+msgid ""
+"How successful this is, I'm not sure.\n"
+"But there must be some sort of hierarchy of trust for the naming system.\n"
+"To treat everyone equally may increase the risk of hijacking."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:163
+msgid "It isn't DNS"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:166
+msgid ""
+"Unfortunately real-time lookups over i2p would significantly slow down "
+"web browsing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:169
+msgid ""
+"Also, DNS is based on lookups with limited caching and time-to-live, "
+"while i2p\n"
+"keys are permanent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:173
+msgid "Sure, we could make it work, but why? It's a bad fit."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:178
+msgid ""
+"Not reliable:\n"
+"It depends on specific servers for addressbook subscriptions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:182
+msgid ""
+"Yes it depends on a few servers that you have configured.\n"
+"Within i2p, servers and services come and go.\n"
+"Any other centralized system (for example DNS root servers) would\n"
+"have the same problem. A completely decentralized system (everybody is "
+"authoritative)\n"
+"is possible by implementing an \"everybody is a root DNS server\" "
+"solution, or by\n"
+"something even simpler, like a script that adds everybody in your "
+"hosts.txt to your addressbook."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:190
+msgid ""
+"People advocating all-authoritative solutions generally haven't thought "
+"through\n"
+"the issues of conflicts and hijacking, however."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:196
+msgid ""
+"Awkward, not real-time:\n"
+"It's a patchwork of hosts.txt providers, key-add web form providers, jump"
+" service providers,\n"
+"eepsite status reporters.\n"
+"Jump servers and subscriptions are a pain, it should just work like DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:202
+msgid "See the reliability and trust sections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:207
+msgid ""
+"So, in summary, the current system is not horribly broken, inefficient, "
+"or un-scalable,\n"
+"and proposals to \"just use DNS\" aren't well thought-through."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:212
+msgid "Alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:213
+msgid ""
+"The I2P source contains several pluggable naming systems and supports "
+"configuration options\n"
+"to enable experimentation with naming systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:218
+msgid ""
+"Meta - calls two or more other naming systems in order.\n"
+"By default, calls PetName then HostsTxt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:222
+msgid ""
+"PetName - Looks up in a petnames.txt file.\n"
+"The format for this file is NOT the same as hosts.txt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:226
+msgid "HostsTxt - Looks up in the following files, in order:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:234
+msgid ""
+"AddressDB - Each host is listed in a separate file in a addressDb/"
+" directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:237
+msgid ""
+"Eepget - does an HTTP lookup request from an external\n"
+"server - must be stacked after the HostsTxt lookup with Meta.\n"
+"This could augment or replace the jump system.\n"
+"Includes in-memory caching."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:243
+msgid ""
+"Exec - calls an external program for lookup, allows\n"
+"additional experimentation in lookup schemes, independent of java.\n"
+"Can be used after HostsTxt or as the sole naming system.\n"
+"Includes in-memory caching."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:249
+msgid "Dummy - used as a fallback for Base64 names, otherwise fails."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:253
+msgid ""
+"The current naming system can be changed with the advanced config option "
+"'i2p.naming.impl'\n"
+"(restart required).\n"
+"See core/java/src/net/i2p/client/naming for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:258
+msgid ""
+"Any new system should be stacked with HostsTxt, or should\n"
+"implement local storage and/or the addressbook subscription functions, "
+"since addressbook\n"
+"only knows about the hosts.txt files and format."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:264
+msgid "Certificates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:265
+msgid ""
+"I2P destinations contain a certificate, however at the moment that "
+"certificate\n"
+"is always null.\n"
+"With a null certificate, base64 destinations are always 516 bytes ending "
+"in \"AAAA\",\n"
+"and this is checked in the addressbook merge mechanism, and possibly "
+"other places.\n"
+"Also, there is no method available to generate a certificate or add it to"
+" a\n"
+"destination. So these will have to be updated to implement certificates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:273
+#, python-format
+msgid ""
+"One possible use of certificates is for proof of work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:276
+msgid ""
+"Another is for \"subdomains\" (in quotes because there is really no such "
+"thing,\n"
+"i2p uses a flat naming system) to be signed by the 2nd level domain's "
+"keys."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:280
+msgid ""
+"With any certificate implementation must come the method for verifying "
+"the\n"
+"certificates.\n"
+"Presumably this would happen in the addressbook merge code.\n"
+"Is there a method for multiple types of certificates, or multiple "
+"certificates?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:286
+msgid ""
+"Adding on a certificate authenticating the\n"
+"responses as signed by some centralized certificate authority would "
+"address many of\n"
+"the hostile nameserver issues but would leave open replay attacks as well"
+" as \n"
+"hostile certificate authority attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:2
+msgid "Low-level Cryptography Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:6
+msgid "This page specifies the low-level details of the cryptography in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:10
+#, python-format
+msgid ""
+"There are a handful of cryptographic algorithms in use within I2P, but we"
+" have\n"
+"reduced them to a bare minimum to deal with our needs - one symmetric "
+"algorithm\n"
+"one asymmetric algorithm, one signing algorithm, and one hashing "
+"algorithm.  However, \n"
+"we do combine them in some particular ways to provide message integrity "
+"(rather than\n"
+"relying on a MAC).  In addition, as much as we hate doing anything new in"
+" regards to \n"
+"cryptography, we can't seem to find a reference discussing (or even "
+"naming) the \n"
+"technique used in ElGamal/AES+SessionTag "
+"(but we're sure others have done it)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:20
+msgid "ElGamal encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:22
+msgid ""
+"\n"
+"ElGamal is used for asymmetric encryption.\n"
+"ElGamal is used in several places in I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:27
+#, python-format
+msgid ""
+"To encrypt router-to-router Tunnel Build "
+"Messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:30
+#, python-format
+msgid ""
+"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n"
+"using the encryption key in the LeaseSet"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:34
+#: i2p2www/pages/site/docs/how/cryptography.html:198
+#, python-format
+msgid ""
+"For encryption of some netDb stores and "
+"queries sent to floodfill routers\n"
+"as a part of ElGamal/AES+SessionTag\n"
+"(destination-to-router or router-to-router)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:41
+msgid ""
+"We use common primes for 2048 ElGamal encryption and decryption, as given"
+" by IETF RFC-3526.\n"
+"We currently only use ElGamal to encrypt the IV and session key in a "
+"single block, followed by the \n"
+"AES encrypted payload using that key and IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:47
+msgid "The unencrypted ElGamal contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:64
+msgid ""
+"The H(data) is the SHA256 of the data that is encrypted in the ElGamal "
+"block,\n"
+"and is preceded by a nonzero byte. \n"
+"This byte could be random, but as implemented it is always 0xFF.\n"
+"It could possibly be used for flags in the future.\n"
+"The data encrypted in the block may be up to 222 bytes long.\n"
+"As the encrypted data may contain a substantial number of zeros if the\n"
+"cleartext is smaller than 222 bytes, it is recommended that higher layers"
+" pad\n"
+"the cleartext to 222 bytes with random data.\n"
+"Total length: typically 255 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:76
+msgid "The encrypted ElGamal contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:102
+msgid ""
+"Each encrypted part is prepended with zeros to a size of exactly 257 "
+"bytes.\n"
+"Total length: 514 bytes.\n"
+"In typical usage, higher layers pad the cleartext data to 222 bytes,\n"
+"resulting in an unencrypted block of 255 bytes.\n"
+"This is encoded as two 256-byte encrypted parts,\n"
+"and there is a single byte of zero padding before each part at this layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:111
+#, python-format
+msgid "See the ElGamal code."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:115
+msgid ""
+"The shared prime is the \n"
+"[Oakley prime "
+"for 2048 bit keys]"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:122
+msgid "or as a hexadecimal value:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:138
+msgid "Using 2 as the generator."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:142
+msgid "Short Exponent"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:143
+#, python-format
+msgid ""
+"While the standard exponent size is 2048 bits (256 bytes) and the I2P\n"
+"PrivateKey\n"
+"is a full 256 bytes, in some cases\n"
+"we use the short exponent size of 226 bits (28.25 bytes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:150
+#, python-format
+msgid ""
+"This should be safe for use with the Oakley primes, per\n"
+"On Diffie-Hellman Key Agreement with Short Exponents "
+"- van Oorschot, Weiner\n"
+"at EuroCrypt 96, and crypto++'s "
+"benchmarks.\n"
+"Benchmarks originally at this link, now dead,\n"
+"rescued from the wayback machine,"
+" dated Apr 23, 2008."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:160
+#, python-format
+msgid ""
+"Also, Koshiba & Kurosawa: Short Exponent Diffie-"
+"Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n"
+"(full text on Google Books) apparently "
+"supports this, according to\n"
+"this sci.crypt thread.\n"
+"The remainder of the PrivateKey is padded with zeroes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:169
+msgid ""
+"Prior to release 0.9.8, all routers used the short exponent.\n"
+"As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent.\n"
+"Other routers continue to use the short exponent due to concerns about "
+"processor load.\n"
+"The transition to a longer exponent for these platforms is a topic for "
+"further study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:176
+#: i2p2www/pages/site/docs/how/cryptography.html:273
+#: i2p2www/pages/site/docs/how/cryptography.html:352
+#: i2p2www/pages/site/docs/how/cryptography.html:391
+msgid "Obsolescence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:177
+msgid ""
+"The vulnerability of the network to an ElGamal attack and the impact of "
+"transitioning to a longer bit length is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:185
+msgid "AES is used for symmetric encryption, in several cases:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:190
+msgid "For transport encryption after DH key exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:194
+#, python-format
+msgid ""
+"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:204
+#, python-format
+msgid ""
+"For encryption of periodic tunnel "
+"test messages sent from the router to itself, through its own "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:209
+#, python-format
+msgid ""
+"We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n"
+"The padding used is specified in IETF RFC-2313 "
+"(PKCS#5 1.5, section 8.1 (for block type 02)).\n"
+"In this case, padding exists of pseudorandomly generated octets to match "
+"16 byte blocks.\n"
+"Specifically, see [the CBC code] and the "
+"Cryptix AES\n"
+"[implementation], as well as the padding, found"
+" in the\n"
+"ElGamalAESEngine.getPadding function."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:274
+msgid ""
+"The vulnerability of the network to an AES attack and the impact of "
+"transitioning to a longer bit length is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:279
+#: i2p2www/pages/site/docs/how/cryptography.html:371
+#: i2p2www/pages/site/docs/how/cryptography.html:397
+#: i2p2www/pages/site/docs/how/cryptography.html:465
+#: i2p2www/pages/site/docs/how/garlic-routing.html:281
+#: i2p2www/pages/site/docs/how/peer-selection.html:296
+msgid "References"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:282
+msgid "Feb. 7, 2006 Status Notes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:289
+#, python-format
+msgid ""
+"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), "
+"as implemented in\n"
+"[DSAEngine].\n"
+"DSA was chosen because it is much faster for signatures than ElGamal."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:295
+msgid "The DSA constants"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:346
+#, python-format
+msgid ""
+"The Signing Public"
+" Key is 1024 bits.\n"
+"The Signing "
+"Private Key is 160 bits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:353
+#, python-format
+msgid ""
+"NIST 800-57\n"
+"recommends a minimum of (L=2048, N=224) for usage beyond 2010.\n"
+"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a "
+"given key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:359
+msgid ""
+"The prime number was chosen in 2003,\n"
+"and the person that chose the number (TheCrypto) is currently no longer "
+"an I2P developer.\n"
+"As such, we do not know if the prime chosen is a 'strong prime'.\n"
+"If a larger prime is chosen for future purposes, this should be a strong "
+"prime, and we will document the construction process."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:366
+msgid ""
+"The vulnerability of the network to a DSA attack and the impact of "
+"transitioning to longer keys is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:374
+#: i2p2www/pages/site/docs/how/cryptography.html:376
+#, python-format
+msgid "Meeting %(num)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:378
+msgid "Choosing the constants"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:386
+#, python-format
+msgid ""
+"Hashes within I2P are plain old SHA256, as implemented in\n"
+"[SHA256Generator]"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:392
+msgid ""
+"The vulnerability of the network to a SHA-256 attack and the impact of "
+"transitioning to a longer hash is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:403
+msgid "Transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:404
+msgid ""
+"At the lowest protocol layer,\n"
+"point-to-point inter-router communication is protected by the transport "
+"layer security.\n"
+"Both transports use 256 byte (2048 bit) Diffie-Hellman key exchange\n"
+"using\n"
+"the same shared prime and generator as specified "
+"above for ElGamal,\n"
+"followed by symmetric AES encryption as described above.\n"
+"This provides\n"
+"perfect "
+"forward secrecy\n"
+"on the transport links."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:416
+msgid "NTCP connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:418
+#, python-format
+msgid ""
+"NTCP connections are negotiated with a 2048 Diffie-Hellman "
+"implementation,\n"
+"using the router's identity to proceed with a station to station "
+"agreement, followed by\n"
+"some encrypted protocol specific fields, with all subsequent data "
+"encrypted with AES\n"
+"(as above).\n"
+"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) "
+"forward secrecy', while ElGamalAES+SessionTag does not."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:426
+msgid ""
+"In order to migrate to a more standardized implementation (TLS/SSL or "
+"even SSH), the following issues must be addressed:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:430
+msgid ""
+"Can we somehow reestablish sessions securely (ala session tags) or do we "
+"need to do full negotiation each time?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:433
+msgid ""
+"Can we simplify/avoid the x509 or other certificate formats and use our "
+"own RouterInfo structure (which \n"
+"contains the ElGamal and DSA keys)?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:438
+#, python-format
+msgid "See the NTCP specification for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:442
+msgid "UDP connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:443
+msgid ""
+"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an"
+" explicit IV and MAC \n"
+"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a "
+"2048 bit \n"
+"Diffie-Hellman exchange, station-to-station authentication with the other"
+" \n"
+"router's DSA key, plus each network message has their own hash for local "
+"integrity \n"
+"checking."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:451
+#, python-format
+msgid "See the SSU specification for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:455
+#, python-format
+msgid ""
+"WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n"
+"Apparently, an early version of SSU used HMAC-SHA256, and then it was "
+"switched\n"
+"to MD5-128 for performance reasons, but left the 32-byte buffer size "
+"intact.\n"
+"See HMACGenerator.java and\n"
+"the 2005-07-05 status notes\n"
+"for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:2
+msgid "ElGamal/AES + SessionTag Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:3
+msgid "February 2011"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:7
+msgid "ElGamal/AES+SessionTags is used for end-to-end encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:11
+msgid ""
+"As an unreliable, unordered, message based system, I2P uses a simple "
+"combination \n"
+"of asymmetric and symmetric encryption algorithms to provide data "
+"confidentiality \n"
+"and integrity to garlic messages. As a whole, the combination is referred"
+" \n"
+"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to "
+"describe \n"
+"the use of 2048bit ElGamal, AES256, SHA256, and 32 byte nonces."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:19
+#: i2p2www/pages/site/docs/how/tech-intro.html:512
+msgid ""
+"The first time a router wants to encrypt a garlic message to another "
+"router, \n"
+"they encrypt the keying material for an AES256 session key with ElGamal "
+"and \n"
+"append the AES256/CBC encrypted payload after that encrypted ElGamal "
+"block. \n"
+"In addition to the encrypted payload, the AES encrypted section contains "
+"the \n"
+"payload length, the SHA256 hash of the unencrypted payload, as well as a "
+"number \n"
+"of \"session tags\" - random 32 byte nonces. The next time the sender "
+"wants \n"
+"to encrypt a garlic message to another router, rather than ElGamal "
+"encrypt \n"
+"a new session key they simply pick one of the previously delivered "
+"session \n"
+"tags and AES encrypt the payload like before, using the session key used "
+"with \n"
+"that session tag, prepended with the session tag itself. When a router "
+"receives \n"
+"a garlic encrypted message, they check the first 32 bytes to see if it "
+"matches \n"
+"an available session tag - if it does, they simply AES decrypt the "
+"message, \n"
+"but if it does not, they ElGamal decrypt the first block."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:35
+#: i2p2www/pages/site/docs/how/tech-intro.html:528
+msgid ""
+"Each session tag can be used only once so as to prevent internal "
+"adversaries \n"
+"from unnecessarily correlating different messages as being between the "
+"same \n"
+"routers. The sender of an ElGamal/AES+SessionTag encrypted message "
+"chooses \n"
+"when and how many tags to deliver, prestocking the recipient with enough "
+"tags \n"
+"to cover a volley of messages. Garlic messages may detect the successful "
+"tag \n"
+"delivery by bundling a small additional message as a clove (a \"delivery "
+"status \n"
+"message\") - when the garlic message arrives at the intended recipient "
+"and \n"
+"is decrypted successfully, this small delivery status message is one of "
+"the \n"
+"cloves exposed and has instructions for the recipient to send the clove "
+"back \n"
+"to the original sender (through an inbound tunnel, of course). When the "
+"original \n"
+"sender receives this delivery status message, they know that the session "
+"tags \n"
+"bundled in the garlic message were successfully delivered."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:50
+msgid ""
+"Session tags themselves have a short lifetime, after which they are \n"
+"discarded if not used. In addition, the quantity stored for each key is "
+"limited, \n"
+"as are the number of keys themselves - if too many arrive, either new or "
+"old \n"
+"messages may be dropped. The sender keeps track whether messages using "
+"session \n"
+"tags are getting through, and if there isn't sufficient communication it "
+"may \n"
+"drop the ones previously assumed to be properly delivered, reverting back"
+" \n"
+"to the full expensive ElGamal encryption.\n"
+"A session will continue to exist until all its tags are exhausted or "
+"expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:61
+msgid ""
+"Sessions are unidirectional. Tags are delivered from Alice to Bob,\n"
+"and Alice then uses the tags, one by one, in subsequent messages to Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:66
+msgid ""
+"Sessions may be established between Destinations, between Routers, or\n"
+"between a Router and a Destination.\n"
+"Each Router and Destination maintains its own Session Key Manager to\n"
+"keep track of Session Keys and Session Tags.\n"
+"Separate Session Key Managers prevents correlation of multiple "
+"Destinations\n"
+"to each other or a Router by adversaries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:77
+msgid "Message Reception"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:78
+msgid ""
+"Each message received has one of two\n"
+"the two possible conditions:
            "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:84
+msgid ""
+"It is part of an existing session and contains a Session Tag and an AES "
+"encrypted block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:85
+msgid "It is for a new session and contains both ElGamal and AES encrypted blocks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:88
+msgid ""
+"When a router receives a message, it will first assume it is from\n"
+"an existing session and attempt to look up the Session Tag and decrypt "
+"the following data using AES.\n"
+"If that fails, it will assume it is for a new session and attempt to\n"
+"decrypt it using ElGamal."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:97
+msgid "New Session Message Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:98
+msgid ""
+"A New Session ElGamal Message contains two parts, an encrypted ElGamal "
+"block\n"
+"and an encrypted AES block."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:103
+msgid "The encrypted message contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:127
+msgid "ElGamal Block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:128
+msgid "The encrypted ElGamal Block is always 514 bytes long."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:132
+msgid "The unencrypted ElGamal data is 222 bytes long, containing:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:164
+#, python-format
+msgid ""
+"The 32-byte\n"
+"Session Key\n"
+"is the identifier for the session.\n"
+"The 32-byte Pre-IV will be used to generate the IV for the AES block that"
+" follows;\n"
+"the IV is the first 16 bytes of the SHA-256 Hash of the Pre-IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:172
+#, python-format
+msgid ""
+"The 222 byte payload is encrypted\n"
+"using ElGamal\n"
+"and the encrypted block is 514 bytes long.\n"
+"
            "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:179
+msgid "AES Block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:180
+msgid "The unencrypted data in the AES block contains the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:224
+#, python-format
+msgid "2-byte Integer, 0-200"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:228
+#, python-format
+msgid ""
+"That many 32-byte Session Tags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:232
+#, python-format
+msgid "4-byte Integer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:236
+#, python-format
+msgid ""
+"The 32-byte SHA256 Hash of"
+" the payload"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:240
+msgid "A one-byte value. Normally == 0. If == 0x01, a Session Key follows"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:244
+#, python-format
+msgid ""
+"A 32-byte Session "
+"Key,\n"
+"                 to replace the old key, and is only present if preceding"
+" flag is 0x01"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:249
+msgid "the data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:251
+msgid ""
+"Random data to a multiple of 16 bytes for the total length.\n"
+"         May contain more than the minimum required padding."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:256
+msgid "Minimum length: 48 bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:260
+#, python-format
+msgid ""
+"The data is then AES Encrypted,\n"
+"using the session key and IV (calculated from the pre-IV) from the "
+"ElGamal section.\n"
+"The encrypted AES Block length is variable but is always a multiple of 16"
+" bytes.\n"
+"
            "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:269
+#, python-format
+msgid ""
+"Actual max payload length, and max block length, is less than 64 KB; see "
+"the I2NP Overview."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:272
+msgid "New Session Key is currently unused and is never present."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:277
+msgid "Existing Session Message Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:278
+msgid ""
+"The session tags delivered successfully are remembered for a \n"
+"brief period (15 minutes currently) until they are used or discarded.\n"
+"A tag is used by packaging one in an Existing Session Message that\n"
+"contains only an AES encrypted block, and is not preceded by an\n"
+"ElGamal block."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:286
+msgid ""
+"The existing session message is\n"
+"as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:309
+#, python-format
+msgid ""
+"A 32-byte Session "
+"Tag\n"
+"             previously delivered in an AES block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:314
+msgid "As specified above."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:318
+msgid ""
+"The session tag also serves as\n"
+"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the "
+"sessionTag."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:323
+msgid ""
+"To decode a message from an existing session, a router looks up the "
+"Session Tag to find an\n"
+"associated Session Key. If the Session Tag is found, the AES block is "
+"decrypted using the associated Session Key.\n"
+"If the tag is not found, the message is assumed to be a New Session Message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:332
+msgid ""
+"There are many possible areas to tune the Session Key Manager's "
+"algorithms;\n"
+"some may interact with the streaming library behavior, or have "
+"significant\n"
+"impact on overall performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:338
+msgid ""
+"Delivery of too many tags at one time may impose substantial overhead for"
+" brief streaming connections\n"
+"or datagrams, and increase the chance of message loss.\n"
+"We currently deliver 40 tags at a time (1280 bytes).\n"
+"32 (1024 bytes) may be better for tunnel fragmentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:345
+msgid ""
+"A few tags could be delivered in each of several messages, or lots of "
+"tags all at once."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:349
+msgid ""
+"It is also important to study and tune\n"
+"the low-tag thresholds at which more tags are sent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:354
+msgid ""
+"The number of tags delivered could depend on message size, keeping in "
+"mind\n"
+"the eventual padding to 1KB at the tunnel message layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:359
+msgid ""
+"Clients could send an estimate of session lifetime to the router, as an "
+"advisory\n"
+"on the number of tags required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:364
+msgid ""
+"Delivery of too few tags causes the router to fall back to an expensive "
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:368
+msgid ""
+"The router may assume delivery of Session Tags, or await acknowledgement "
+"before using them;\n"
+"there are tradeoffs for each strategy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:373
+msgid ""
+"For very brief messages, almost the full 222 bytes of the pre-IV and "
+"padding fields in the ElGamal block\n"
+"could be used for the entire message, instead of establishing a session."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:378
+msgid ""
+"Evaluate padding strategy; currently we pad to a minimum of 128 bytes.\n"
+"Would be better to add a few tags to small messages than pad."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:383
+msgid ""
+"Perhaps things could be more efficient if the Session Tag system was "
+"bidirectional,\n"
+"so tags delivered in the 'forward' path could be used in the 'reverse' "
+"path,\n"
+"thus avoiding ElGamal in the initial response.\n"
+"The router currently plays some tricks like this when sending\n"
+"tunnel test messages to itself."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:391
+#, python-format
+msgid ""
+"Change from Session Tags to\n"
+"a synchronized PRNG."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:396
+#, python-format
+msgid ""
+"Several of these ideas may require a new I2NP message type, or\n"
+"set a flag in the\n"
+"Delivery Instructions,\n"
+"or set a magic number in the first few bytes of the Session Key field\n"
+"and accept a small risk of the random Session Key matching the magic "
+"number."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:2
+msgid "Garlic Routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:6
+msgid "Garlic Routing and \"Garlic\" Terminology"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:7
+msgid ""
+"The terms \"garlic routing\" and \"garlic encryption\" are often used "
+"rather loosely when referring to I2P's technology.\n"
+"Here, we explain the history of the terms, the various meanings, and\n"
+"the usage of \"garlic\" methods in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:13
+msgid ""
+"\"Garlic routing\" was first coined by\n"
+"Michael J. Freedman\n"
+"in Roger Dingledine's Free Haven \n"
+"Master's thesis "
+"Section 8.1.1 (June 2000), as derived from \n"
+"Onion Routing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:21
+msgid ""
+"\"Garlic\" may have been used originally by I2P developers because I2P "
+"implements a form of\n"
+"bundling as Freedman describes, or simply to emphasize general "
+"differences from Tor.\n"
+"The specific reasoning may be lost to history.\n"
+"Generally, when referring to I2P, the term \"garlic\" may mean one of "
+"three things:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:28
+#: i2p2www/pages/site/docs/how/garlic-routing.html:39
+msgid "Layered Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:29
+msgid "Bundling multiple messages together"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:30
+#: i2p2www/pages/site/docs/how/garlic-routing.html:96
+msgid "ElGamal/AES Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:33
+msgid ""
+"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven "
+"years has not always been precise; therefore the reader is\n"
+"cautioned when encountering the term.\n"
+"Hopefully, the explanation below will make things clear."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:40
+msgid ""
+"Onion routing is a technique for building paths, or tunnels, through a "
+"series of peers,\n"
+"and then using that tunnel.\n"
+"Messages are repeatedly encrypted by the originator, and then decrypted "
+"by each hop.\n"
+"During the building phase, only the routing instructions for the next hop"
+" are exposed to each peer.\n"
+"During the operating phase, messages are passed through the tunnel, and "
+"the\n"
+"message and its routing instructions are only exposed to the endpoint of "
+"the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:49
+#, python-format
+msgid ""
+"This is similar to the way Mixmaster\n"
+"(see network comparisons) sends messages "
+"- taking a message, encrypting it\n"
+"to the recipient's public key, taking that encrypted message and "
+"encrypting\n"
+"it (along with instructions specifying the next hop), and then taking "
+"that\n"
+"resulting encrypted message and so on, until it has one layer of "
+"encryption\n"
+"per hop along the path."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:58
+msgid ""
+"In this sense, \"garlic routing\" as a general concept is identical to "
+"\"onion routing\".\n"
+"As implemented in I2P, of course, there are several differences from the "
+"implementation in Tor; see below.\n"
+"Even so, there are substantial similarities such that I2P benefits from a"
+"\n"
+"large amount of"
+" academic research on onion routing,\n"
+"Tor, and similar "
+"mixnets."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:67
+msgid "Bundling Multiple Messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:68
+msgid ""
+"Michael Freedman defined \"garlic routing\" as an extension to onion "
+"routing,\n"
+"in which multiple messages are bundled together.\n"
+"He called each message a \"bulb\".\n"
+"All the messages, each with its own delivery instructions, are exposed at"
+" the\n"
+"endpoint.\n"
+"This allows the efficient bundling of an onion routing \"reply block\" "
+"with the original message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:77
+msgid ""
+"This concept is implemented in I2P, as described below.\n"
+"Our term for garlic \"bulbs\" is \"cloves\".\n"
+"Any number of messages can be\n"
+"contained, instead of just a single message.\n"
+"This is a significant distinction from the onion routing implemented in "
+"Tor.\n"
+"However, it is only one of many major architectural differences between "
+"I2P and Tor;\n"
+"perhaps it is not, by itself, enough to justify a change in terminology."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:87
+msgid ""
+"Another difference\n"
+"from the method described by Freedman\n"
+"is that the path is unidirectional - there is no \"turning point\" as "
+"seen in onion routing\n"
+"or mixmaster reply blocks, which greatly simplifies the algorithm and "
+"allows for more flexible\n"
+"and reliable delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:97
+#, python-format
+msgid ""
+"In some cases, \"garlic encryption\" may simply mean\n"
+"ElGamal/AES+SessionTag encryption\n"
+"(without multiple layers)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:105
+msgid "\"Garlic\" Methods in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:106
+msgid ""
+"Now that we've defined various \"garlic\" terms, we can say that\n"
+"I2P uses garlic routing, bundling and encryption in three places:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:111
+msgid "For building and routing through tunnels (layered encryption)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:112
+msgid ""
+"For determining the success or failure of end to end message delivery "
+"(bundling)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:113
+msgid ""
+"For publishing some network database entries (dampening the probability "
+"of a successful traffic analysis attack) (ElGamal/AES)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:116
+msgid ""
+"There are also significant ways that this technique can be used to "
+"improve the performance of the network, \n"
+"exploiting transport latency/throughput tradeoffs, and branching data "
+"through redundant paths to increase reliability."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:122
+msgid "Tunnel Building and Routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:123
+msgid ""
+"In I2P, tunnels are unidirectional. Each party builds two tunnels,\n"
+"one for outbound and one for inbound traffic.\n"
+"Therefore, four tunnels are required for a single round-trip message and "
+"reply."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:129
+#, python-format
+msgid ""
+"Tunnels are built, and then used, with layered encryption.\n"
+"This is described on the\n"
+"tunnel implementation page.\n"
+"Tunnel building details are defined on\n"
+"this page.\n"
+"We use\n"
+"ElGamal/AES+SessionTag for the encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:141
+#, python-format
+msgid ""
+"Tunnels are a general-purpose mechanism to transport all\n"
+"I2NP messages, and\n"
+"Garlic Messages are not used to "
+"build tunnels.\n"
+"We do not bundle multiple\n"
+"I2NP messages into a single\n"
+"Garlic Message for unwrapping at "
+"the outbound tunnel endpoint;\n"
+"the tunnel encryption is sufficient."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:152
+msgid "End-to-End Message Bundling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:153
+#, python-format
+msgid ""
+"At the layer above tunnels, I2P delivers end-to-end messages between\n"
+"Destinations.\n"
+"Just as within a single tunnel, we use\n"
+"ElGamal/AES+SessionTag for the encryption."
+"\n"
+"Each client message as delivered to the router through the\n"
+"I2CP interface becomes a single\n"
+"Garlic Clove\n"
+"with its own\n"
+"Delivery Instructions,\n"
+"inside a\n"
+"Garlic Message.\n"
+"Delivery Instructions may specify a Destination, Router, or Tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:172
+msgid ""
+"Generally, a Garlic Message will contain only one clove.\n"
+"However, the router will periodically bundle two additional\n"
+"cloves in the Garlic Message:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:177
+msgid "Garlic Message Cloves"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:180
+#, python-format
+msgid ""
+"A\n"
+"Delivery Status Message,\n"
+"with\n"
+"Delivery Instructions\n"
+"specifying that it be sent back to the originating router as an "
+"acknowledgment.\n"
+"This is similar to the \"reply block\" or \"reply onion\"\n"
+"described in the references.\n"
+"It is used for determining the success or failure of end to end message "
+"delivery.\n"
+"The originating router may, upon failure to receive the Delivery Status "
+"Message\n"
+"within the expected time period, modify the routing to the far-end "
+"Destination,\n"
+"or take other actions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:194
+#, python-format
+msgid ""
+"A\n"
+"Database Store Message,\n"
+"containing a\n"
+"LeaseSet\n"
+"for the originating Destination, with\n"
+"Delivery Instructions\n"
+"specifying the far-end destination's router.\n"
+"By periodically bundling a LeaseSet, the router ensures that the far-end "
+"will be able\n"
+"to maintain communications.\n"
+"Otherwise the far-end would have to query a floodfill router for the "
+"network database entry,\n"
+"and all LeaseSets would have to be published to the network database, as "
+"explained on the\n"
+"network database page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:213
+#, python-format
+msgid ""
+"In the current implementation, the Delivery Status and Database Store "
+"Messages\n"
+"are bundled when the local LeaseSet changes, when additional\n"
+"Session Tags\n"
+"are delivered, or if the messages have not been bundled in the previous "
+"minute."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:220
+msgid ""
+"Obviously, the additional messages are currently bundled for specific "
+"purposes,\n"
+"and not part of a general-purpose routing scheme."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:226
+msgid "Storage to the Floodfill Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:227
+#, python-format
+msgid ""
+"As explained on the\n"
+"network database page,\n"
+"local\n"
+"LeaseSets\n"
+"are sent to floodfill routers in a\n"
+"Database Store Message\n"
+"wrapped in a\n"
+"Garlic Message\n"
+"so it is not visible to the tunnel's outbound gateway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:243
+#, python-format
+msgid ""
+"The Garlic Message mechanism is very flexible and provides a structure "
+"for\n"
+"implementing many types of mixnet delivery methods.\n"
+"Together with the unused delay option in the\n"
+"tunnel message Delivery "
+"Instructions,\n"
+"a wide spectrum of batching, delay, mixing, and routing strategies are "
+"possible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:251
+msgid ""
+"In particular, there is potential for much more flexibility at the "
+"outbound tunnel endpoint.\n"
+"Messages could possibly be routed from there to one of several tunnels\n"
+"(thus minimizing point-to-point connections), or multicast to several "
+"tunnels\n"
+"for redundancy, or streaming audio and video."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:258
+msgid ""
+"Such experiments may conflict with the need to ensure security and "
+"anonymity, such\n"
+"as limiting certain routing paths, restricting the types of I2NP messages"
+" that may\n"
+"be forwarded along various paths, and enforcing certain message "
+"expiration times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:264
+#, python-format
+msgid ""
+"As a part of\n"
+"ElGamal/AES encryption,\n"
+"a garlic message contains a sender\n"
+"specified amount of padding data, allowing the sender to take active "
+"countermeasures \n"
+"against traffic analysis.\n"
+"This is not currently used, beyond the requirement to pad to a multiple "
+"of 16 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:273
+#, python-format
+msgid ""
+"Encryption of additional messages to and from the\n"
+"floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:283
+msgid ""
+"The term garlic routing was first coined in Roger Dingledine's Free Haven"
+" \n"
+"Master's thesis "
+"(June 2000),\n"
+"see Section 8.1.1 authored by\n"
+"Michael J. Freedman."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:290
+msgid "Onion router publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:292
+msgid "Onion Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:294
+msgid "Garlic Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:296
+#, python-format
+msgid ""
+"I2P Meeting 58 (2003) discussing the "
+"implementation of garlic routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:302
+msgid "Free Haven publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:304
+msgid ""
+"Onion routing was first described in Hiding Routing Information\n"
+"by David M. Goldschlag, Michael G. Reed, and Paul F. Syverson in 1996."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:2
+msgid "A Gentle Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:5
+msgid "A Gentle Introduction to How I2P Works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:7
+msgid ""
+"I2P is a project to build, deploy, and maintain a network supporting "
+"secure and anonymous\n"
+"communication. People using I2P are in control of the tradeoffs between "
+"anonymity, reliability,\n"
+"bandwidth usage, and latency. There is no central point in the network on"
+" which pressure can be\n"
+"exerted to compromise the integrity, security, or anonymity of the "
+"system. The network supports\n"
+"dynamic reconfiguration in response to various attacks, and has been "
+"designed to make use of\n"
+"additional resources as they become available. Of course, all aspects of "
+"the network are open and\n"
+"freely available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:17
+msgid ""
+"Unlike many other anonymizing networks, I2P doesn't try to provide "
+"anonymity by hiding the\n"
+"originator of some communication and not the recipient, or the other way "
+"around. I2P is designed to\n"
+"allow peers using I2P to communicate with each other anonymously — "
+"both sender and recipient\n"
+"are unidentifiable to each other as well as to third parties. For "
+"example, today there are both\n"
+"in-I2P web sites (allowing anonymous publishing / hosting) as well as "
+"HTTP proxies to the normal web\n"
+"(allowing anonymous web browsing). Having the ability to run servers "
+"within I2P is essential, as it\n"
+"is quite likely that any outbound proxies to the normal Internet will be "
+"monitored, disabled, or\n"
+"even taken over to attempt more malicious attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:28
+#, python-format
+msgid ""
+"The network itself is message oriented - it is essentially a secure and "
+"anonymous IP layer, where\n"
+"messages are addressed to cryptographic keys (Destinations) and can be "
+"significantly larger than IP\n"
+"packets. Some example uses of the network include \"eepsites\" "
+"(webservers hosting normal web\n"
+"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a "
+"distributed data store. With the\n"
+"help of the I2PTunnel application, we are "
+"able to stream traditional\n"
+"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even "
+"streaming audio. Most people\n"
+"will not use I2P directly, or even need to know they're using it. Instead"
+" their view will be of one\n"
+"of the I2P enabled applications, or perhaps as a little controller app to"
+" turn on and off various\n"
+"proxies to enable the anonymizing functionality."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:40
+#, python-format
+msgid ""
+"An essential part of designing, developing, and testing an anonymizing "
+"network is to define the threat model, since there is no such thing "
+"as \"true\" anonymity, just\n"
+"increasingly expensive costs to identify someone. Briefly, I2P's intent "
+"is to allow people to\n"
+"communicate in arbitrarily hostile environments by providing good "
+"anonymity, mixed in with\n"
+"sufficient cover traffic provided by the activity of people who require "
+"less anonymity. This way,\n"
+"some users can avoid detection by a very powerful adversary, while others"
+" will try to evade a weaker\n"
+"entity, all on the same network, where each one's messages are "
+"essentially indistinguishable\n"
+"from the others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:51
+msgid "Why?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:52
+#, python-format
+msgid ""
+"There are a multitude of reasons why we need a system to support "
+"anonymous communication, and\n"
+"everyone has their own personal rationale. There are many other\n"
+"efforts working on finding ways to provide varying degrees of "
+"anonymity to people through the\n"
+"Internet, but we could not find any that met our needs or threat model."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:59
+msgid "How?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:61
+#, python-format
+msgid ""
+"The network at a glance is made up of a set of nodes (\"routers\") with a"
+" number of unidirectional\n"
+"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is "
+"identified by a cryptographic RouterIdentity which is\n"
+"typically long lived. These routers communicate with each other through "
+"existing transport\n"
+"mechanisms (TCP, UDP, etc), passing various messages. Client applications"
+" have their own\n"
+"cryptographic identifier (\"Destination\") which enables it to send and "
+"receive messages. These\n"
+"clients can connect to any router and authorize the temporary allocation "
+"(\"lease\") of some tunnels\n"
+"that will be used for sending and receiving messages through the network."
+" I2P has its own internal\n"
+"network database (using a modification of the "
+"Kademlia algorithm) for\n"
+"distributing routing and contact information securely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:74
+msgid "Network topology example"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:76
+msgid ""
+"In the above, Alice, Bob, Charlie, and Dave are all running routers with "
+"a single Destination on\n"
+"their local router. They each have a pair of 2-hop inbound tunnels per "
+"destination (labeled 1, 2, 3,\n"
+"4, 5 and 6), and a small subset of each of those router's outbound tunnel"
+" pool is shown with 2-hop\n"
+"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's "
+"outbound tunnels are not\n"
+"shown, nor are the rest of each router's outbound tunnel pool (typically "
+"stocked with a few tunnels\n"
+"at a time). When Alice and Bob talk to each other, Alice sends a message "
+"out one of her (pink)\n"
+"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3"
+" or 4). She knows to send\n"
+"to those tunnels on the correct router by querying the network database, "
+"which is constantly updated\n"
+"as new leases are authorized and old ones expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:88
+#, python-format
+msgid ""
+"If Bob wants to reply to Alice, he simply goes through the same process -"
+" send a message out one of\n"
+"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 "
+"or 2). To make things\n"
+"easier, most messages sent between Alice and Bob are garlic\n"
+"wrapped, bundling the sender's own current lease information so that the "
+"recipient can reply\n"
+"immediately without having to look in the network database for the "
+"current data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:96
+#, python-format
+msgid ""
+"To deal with a wide range of attacks, I2P is fully distributed with no "
+"centralized resources - and\n"
+"hence there are no directory servers keeping statistics regarding the "
+"performance and reliability of\n"
+"routers within the network. As such, each router must keep and maintain "
+"profiles of various routers\n"
+"and is responsible for selecting appropriate peers to meet the anonymity,"
+" performance, and\n"
+"reliability needs of the users, as described in the peer selection\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:105
+#, python-format
+msgid ""
+"The network itself makes use of a significant number of cryptographic\n"
+"techniques and algorithms - a full laundry list includes 2048bit "
+"ElGamal encryption, 256bit AES\n"
+"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, "
+"2048bit Diffie-Hellman\n"
+"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:113
+msgid ""
+"Content sent over I2P is encrypted through three layers garlic encryption"
+" (used to verify the\n"
+"delivery of the message to the recipient), tunnel encryption (all "
+"messages passing through a tunnel\n"
+"is encrypted by the tunnel gateway to the tunnel endpoint), and inter "
+"router transport layer\n"
+"encryption (e.g. the TCP transport uses AES256 with ephemeral keys)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:120
+msgid ""
+"End-to-end (I2CP) encryption (client application to server application) "
+"was disabled in I2P release\n"
+"0.6; end-to-end (garlic) encryption (I2P client router to I2P server "
+"router) from Alice's router \"a\"\n"
+"to Bob's router \"h\" remains. Notice the different use of terms! All "
+"data from a to h is end-to-end\n"
+"encrypted, but the I2CP connection between the I2P router and the "
+"applications is not end-to-end\n"
+"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob "
+"in following chart are the\n"
+"applications running atop of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:129
+msgid "End to end layered encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:131
+#, python-format
+msgid ""
+"The specific use of these algorithms are outlined elsewhere."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:135
+msgid ""
+"The two main mechanisms for allowing people who need strong anonymity to "
+"use the network are\n"
+"explicitly delayed garlic routed messages and more comprehensive tunnels "
+"to include support for\n"
+"pooling and mixing messages. These are currently planned for release 3.0,"
+" but garlic routed messages\n"
+"with no delays and FIFO tunnels are currently in place. Additionally, the"
+" 2.0 release will allow\n"
+"people to set up and operate behind restricted routes (perhaps with "
+"trusted peers), as well as the\n"
+"deployment of more flexible and anonymous transports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:144
+#, python-format
+msgid ""
+"Some questions have been raised with regards to the scalability of I2P, "
+"and reasonably so. There\n"
+"will certainly be more analysis over time, but peer lookup and "
+"integration should be bounded by\n"
+"O(log(N)) due to the network "
+"database's algorithm, while end\n"
+"to end messages should be O(1) (scale free), since messages "
+"go out K hops through the\n"
+"outbound tunnel and another K hops through the inbound tunnel, with K no "
+"longer than 3. The size of\n"
+"the network (N) bears no impact."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:153
+msgid "When?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:154
+#, python-format
+msgid ""
+"I2P initially began in Feb 2003 as a proposed modification to Freenet to allow it to use "
+"alternate transports, such as JMS, then grew into its own as an\n"
+"'anonCommFramework' in April 2003, turning into I2P in July, with code "
+"being written in earnest\n"
+"starting in August '03. I2P is currently under development, following the"
+" roadmap."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:164
+msgid "Who?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:165
+#, python-format
+msgid ""
+"We have a small team spread around several "
+"continents, working to advance\n"
+"different aspects of the project. We are very open to other developers "
+"who want to get involved and\n"
+"anyone else who would like to contribute in other ways, such as "
+"critiques, peer review, testing,\n"
+"writing I2P enabled applications, or documentation. The entire system is "
+"open source - the router\n"
+"and most of the SDK are outright public domain with some BSD and Cryptix "
+"licensed code, while some\n"
+"applications like I2PTunnel and I2PSnark are GPL. Almost everything is "
+"written in Java (1.5+),\n"
+"though some third party applications are being written in Python and "
+"other languages. The code works\n"
+"on Sun Java SE and other Java Virtual"
+" Machines."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:176
+msgid "Where?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:177
+#, python-format
+msgid ""
+"Anyone interested should join us on the IRC channel #i2p (hosted "
+"concurrently on irc.freenode.net,\n"
+"irc.postman.i2p, irc.freshcoffee.i2p, irc.welterde.i2p and "
+"irc.einirc.de). There are currently no\n"
+"scheduled development meetings, however archives"
+" are available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:183
+#, python-format
+msgid "The current source is available in monotone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:188
+#, python-format
+msgid "See the Index to Technical Documentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:2
+msgid "The Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:3
+#: i2p2www/pages/site/docs/spec/updates.html:3
+msgid "October 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:8
+msgid ""
+"I2P's netDb is a specialized distributed database, containing \n"
+"just two types of data - router contact information (RouterInfos) "
+"and destination contact\n"
+"information (LeaseSets). Each piece of data is signed by the "
+"appropriate party and verified\n"
+"by anyone who uses or stores it. In addition, the data has liveliness "
+"information\n"
+"within it, allowing irrelevant entries to be dropped, newer entries to "
+"replace\n"
+"older ones, and protection against certain classes of attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:17
+msgid ""
+"The netDb is distributed with a simple technique called \"floodfill\",\n"
+"where a subset of all routers, called \"floodfill routers\", maintains "
+"the distributed database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:25
+msgid ""
+"When an I2P router wants to contact another router, they need to know "
+"some \n"
+"key pieces of data - all of which are bundled up and signed by the router"
+" into\n"
+"a structure called the \"RouterInfo\", which is distributed with the "
+"SHA256 of the router's identity\n"
+"as the key. The structure itself contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:32
+msgid ""
+"The router's identity (a 2048bit ElGamal encryption key, a 1024bit DSA "
+"signing key, and a certificate)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:33
+msgid ""
+"The contact addresses at which it can be reached (e.g. TCP: example.org "
+"port 4108)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:34
+msgid "When this was published"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:35
+msgid "A set of arbitrary text options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:36
+msgid "The signature of the above, generated by the identity's DSA signing key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:39
+msgid ""
+"The following text options, while not strictly required, are expected\n"
+"to be present:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:45
+msgid ""
+"Capabilities flags - used to indicate floodfill participation, "
+"approximate bandwidth, and perceived reachability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:47
+msgid "SSU Testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:48
+msgid "SSU Introducer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:49
+#: i2p2www/pages/site/docs/how/network-database.html:246
+msgid "Floodfill"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:50
+msgid "Hidden"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:51
+#, python-format
+msgid "Under %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+#: i2p2www/pages/site/docs/how/network-database.html:53
+#: i2p2www/pages/site/docs/how/network-database.html:54
+#, python-format
+msgid "%(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+msgid "default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:55
+#, python-format
+msgid "Over %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:56
+msgid "Reachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:57
+msgid "Unreachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:62
+msgid "The core library version, always the same as the router version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:65
+msgid ""
+"Basic network compatibility - A router will refuse to communicate with a "
+"peer having a different netId"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:68
+msgid "Used to determine compatibility with newer features and messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:71
+msgid ""
+"Always sent as 90m, for compatibility with an older scheme where routers "
+"published their actual uptime,\n"
+"and only sent tunnel requests to peers whose was more than 60m"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:76
+msgid ""
+"These values are used by other routers for basic decisions.\n"
+"Should we connect to this router? Should we attempt to route a tunnel "
+"through this router?\n"
+"The bandwidth capability flag, in particular, is used only to determine "
+"whether\n"
+"the router meets a minimum threshold for routing tunnels.\n"
+"Above the minimum threshold, the advertised bandwidth is not used or "
+"trusted anywhere\n"
+"in the router, except for display in the user interface and for debugging"
+" and network analysis."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:86
+#, python-format
+msgid ""
+"Additional text options include\n"
+"a small number of statistics about the router's health, which are "
+"aggregated by\n"
+"sites such as %(stats)s\n"
+"for network performance analysis and debugging.\n"
+"These statistics were chosen to provide data crucial to the developers,\n"
+"such as tunnel build success rates, while balancing the need for such "
+"data\n"
+"with the side-effects that could result from revealing this data.\n"
+"Current statistics are limited to:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:97
+msgid "Client and exploratory tunnel build success, reject, and timeout rates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:98
+msgid "1 hour average number of participating tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:101
+msgid ""
+"The data published can be seen in the router's user interface,\n"
+"but is not used or trusted within the router.\n"
+"As the network has matured, we have gradually removed most of the "
+"published\n"
+"statistics to improve anonymity, and we plan to remove more in future "
+"releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:109
+msgid "RouterInfo specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:112
+msgid "RouterInfo Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:115
+msgid "RouterInfo Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:116
+msgid ""
+"RouterInfos have no set expiration time.\n"
+"Each router is free to maintain its own local policy to trade off the "
+"frequency of RouterInfo lookups\n"
+"with memory or disk usage.\n"
+"In the current implementation, there are the following general policies:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:123
+msgid ""
+"There is no expiration during the first hour of uptime, as the persistent"
+" stored data may be old."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:126
+msgid "There is no expiration if there are 25 or less RouterInfos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:129
+msgid ""
+"As the number of local RouterInfos grows, the expiration time shrinks, in"
+" an attempt to maintain\n"
+"a reasonable number RouterInfos. The expiration time with less than 120 "
+"routers is 72 hours,\n"
+"while expiration time with 300 routers is around 30 hours."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:134
+#, python-format
+msgid ""
+"RouterInfos containing SSU introducers expire in "
+"about an hour, as\n"
+"the introducer list expires in about that time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:138
+msgid ""
+"Floodfills use a short expiration time (1 hour) for all local "
+"RouterInfos, as valid RouterInfos will\n"
+"be frequently republished to them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:144
+msgid "RouterInfo Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:146
+msgid ""
+"RouterInfos are periodically written to disk so that they are available "
+"after a restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:153
+msgid ""
+"The second piece of data distributed in the netDb is a \"LeaseSet\" - "
+"documenting\n"
+"a group of tunnel entry points (leases) for a particular client "
+"destination.\n"
+"Each of these leases specify the following information:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:159
+msgid "The tunnel gateway router (by specifying its identity)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:160
+msgid "The tunnel ID on that router to send messages with (a 4 byte number)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:161
+msgid "When that tunnel will expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:163
+msgid ""
+"The LeaseSet itself is stored in the netDb under\n"
+"the key derived from the SHA256 of the destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:168
+msgid "In addition to these leases, the LeaseSet includes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:172
+msgid ""
+"The destination itself (a 2048bit ElGamal encryption key, 1024bit DSA "
+"signing key and a certificate)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:173
+msgid ""
+"Additional encryption public key: used for end-to-end encryption of "
+"garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:174
+msgid ""
+"Additional signing public key: intended for LeaseSet revocation, but is "
+"currently unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:175
+msgid ""
+"Signature of all the LeaseSet data, to make sure the Destination "
+"published the LeaseSet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:179
+msgid "Lease specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:181
+msgid "LeaseSet specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:184
+msgid "Lease Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:186
+msgid "LeaseSet Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:190
+msgid "Unpublished LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:191
+msgid ""
+"A LeaseSet for a destination used only for outgoing connections is "
+"unpublished.\n"
+"It is never sent for publication to a floodfill router.\n"
+"\"Client\" tunnels, such as those for web browsing and IRC clients, are "
+"unpublished.\n"
+"Servers will still be able to send messages back to those unpublished "
+"destinations,\n"
+"because of I2NP storage messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:201
+msgid "Revoked LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:202
+msgid ""
+"A LeaseSet may be revoked by publishing a new LeaseSet with zero "
+"leases.\n"
+"Revocations must be signed by the additional signing key in the LeaseSet."
+"\n"
+"Revocations are not fully implemented, and it is unclear if they have any"
+" practical use.\n"
+"This is the only planned use for that signing key, so it is currently "
+"unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:209
+msgid "Encrypted LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:210
+msgid ""
+"In an encrypted LeaseSet, all Leases are encrypted with a separate"
+" DSA key.\n"
+"The leases may only be decoded, and thus the destination may only be "
+"contacted,\n"
+"by those with the key.\n"
+"There is no flag or other direct indication that the LeaseSet is "
+"encrypted.\n"
+"Encrypted LeaseSets are not widely used, and it is a topic for future "
+"work to\n"
+"research whether the user interface and implementation of encrypted "
+"LeaseSets could be improved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:219
+msgid "LeaseSet Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:220
+msgid ""
+"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet "
+"expires\n"
+"10 minutes after the earliest creation time of all its Leases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:225
+msgid "LeaseSet Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:226
+msgid ""
+"There is no persistent storage of LeaseSet data since they expire so "
+"quickly."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:231
+msgid "Bootstrapping"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:232
+msgid ""
+"The netDb is decentralized, however you do need at\n"
+"least one reference to a peer so that the integration process\n"
+"ties you in. This is accomplished by \"reseeding\" your router with the "
+"RouterInfo\n"
+"of an active peer - specifically, by retrieving their "
+"routerInfo-$hash.dat\n"
+"file and storing it in your netDb/ directory. Anyone can "
+"provide\n"
+"you with those files - you can even provide them to others by exposing "
+"your own\n"
+"netDb directory. To simplify the process,\n"
+"volunteers publish their netDb directories (or a subset) on the regular "
+"(non-i2p) network,\n"
+"and the URLs of these directories are hardcoded in I2P.\n"
+"When the router starts up for the first time, it automatically fetches "
+"from\n"
+"one of these URLs, selected at random."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:247
+msgid ""
+"The floodfill netDb is a simple distributed storage mechanism.\n"
+"The storage algorithm is simple: send the data to the closest peer that "
+"has advertised itself\n"
+"as a floodfill router. Then wait 10 seconds, pick another floodfill "
+"router and ask them \n"
+"for the entry to be sent, verifying its proper insertion / distribution. "
+"If the \n"
+"verification peer doesn't reply, or they don't have the entry, the sender"
+" \n"
+"repeats the process. When the peer in the floodfill netDb receives a "
+"netDb \n"
+"store from a peer not in the floodfill netDb, they send it to a subset of"
+" the floodfill netDb-peers.\n"
+"The peers selected are the ones closest (according to the XOR-metric) to a specific key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:258
+msgid ""
+"Determining who is part of the floodfill netDb is trivial - it is exposed"
+" in each \n"
+"router's published routerInfo as a capability."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:263
+msgid ""
+"Floodfills have no central authority and do not form a \"consensus\" -\n"
+"they only implement a simple DHT overlay."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:270
+msgid "Floodfill Router Opt-in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:272
+msgid ""
+"Unlike Tor, where the directory servers are hardcoded and trusted,\n"
+"and operated by known entities,\n"
+"the members of the I2P floodfill peer set need not be trusted, and\n"
+"change over time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:279
+msgid ""
+"To increase reliability of the netDb, and minimize the impact\n"
+"of netDb traffic on a router, floodfill is automatically enabled\n"
+"only on routers that are configured with high bandwidth limits.\n"
+"Routers with high bandwidth limits (which must be manually configured,\n"
+"as the default is much lower) are presumed to be on lower-latency\n"
+"connections, and are more likely to be available 24/7.\n"
+"The current minimum share bandwidth for a floodfill router is 128 "
+"KBytes/sec."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:289
+msgid ""
+"In addition, a router must pass several additional tests for health\n"
+"(outbound message queue time, job lag, etc.) before floodfill operation "
+"is\n"
+"automatically enabled."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:295
+msgid ""
+"With the current rules for automatic opt-in, approximately 6% of\n"
+"the routers in the network are floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:300
+msgid ""
+"While some peers are manually configured to be floodfill,\n"
+"others are simply high-bandwidth routers who automatically volunteer\n"
+"when the number of floodfill peers drops below a threshold.\n"
+"This prevents any long-term network damage from losing most or all\n"
+"floodfills to an attack.\n"
+"In turn, these peers will un-floodfill themselves when there are\n"
+"too many floodfills outstanding."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:310
+msgid "Floodfill Router Roles"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:311
+msgid ""
+"A floodfill router's only services that are in addition to those of non-"
+"floodfill routers\n"
+"are in accepting netDb stores and responding to netDb queries.\n"
+"Since they are generally high-bandwidth, they are more likely to "
+"participate in a high number of tunnels\n"
+"(i.e. be a \"relay\" for others), but this is not directly related to "
+"their distributed database services."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:319
+msgid "Kademlia Closeness Metric"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:320
+msgid ""
+"The netDb uses a simple Kademlia-style XOR metric to determine closeness."
+"\n"
+"The SHA256 hash of the key being looked up or stored is XOR-ed with\n"
+"the hash of the router in question to determine closeness.\n"
+"A modification to this algorithm is done to increase the costs of Sybil attacks.\n"
+"Instead of the SHA256 hash of the key being looked up of stored, the "
+"SHA256 hash is taken\n"
+"of the 32-byte binary key appended with the UTC date represented as an "
+"8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n"
+"This is called the \"routing key\", and it changes every day at midnight "
+"UTC.\n"
+"The daily transformation of the DHT is sometimes called \"keyspace "
+"rotation\",\n"
+"although it isn't strictly a rotation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:332
+msgid ""
+"Routing keys are never sent on-the-wire in any I2NP message, they are "
+"only used locally for\n"
+"determination of distance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:339
+msgid "Storage, Verification, and Lookup Mechanics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:341
+msgid "RouterInfo Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:342
+#, python-format
+msgid ""
+"I2NP DatabaseStoreMessages containing the local "
+"RouterInfo are exchanged with peers\n"
+"as a part of the initialization of a NTCP\n"
+"or SSU transport connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:349
+msgid "LeaseSet Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:350
+#, python-format
+msgid ""
+"I2NP DatabaseStoreMessages containing the local "
+"LeaseSet are periodically exchanged with peers\n"
+"by bundling them in a garlic message along with normal traffic from the "
+"related Destination.\n"
+"This allows an initial response, and later responses, to be sent to an "
+"appropriate Lease,\n"
+"without requiring any LeaseSet lookups, or requiring the communicating "
+"Destinations to have published LeaseSets at all."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:358
+msgid ""
+"The DatabaseStoreMessage should be sent to the floodfill that is closest\n"
+"to the current routing key for the RouterInfo or LeaseSet being stored.\n"
+"Currently, the closest floodfill is found by a search in the local "
+"database.\n"
+"Even if that floodfill is not actually closest, it will flood it "
+"\"closer\" by\n"
+"sending it to multiple other floodfills.\n"
+"This provides a high degree of fault-tolerance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:367
+msgid ""
+"In traditional Kademlia, a peer would do a \"find-closest\" search before"
+" inserting\n"
+"an item in the DHT to the closest target. As the verify operation will "
+"tend to\n"
+"discover closer floodfills if they are present, a router will quickly "
+"improve\n"
+"its knowledge of the DHT \"neighborhood\" for the RouterInfo and "
+"LeaseSets it regularly publishes.\n"
+"While I2NP does not define a \"find-closest\" message, if it becomes "
+"necessary,\n"
+"a router may simply do an iterative search for a key with the least "
+"significant bit flipped\n"
+"(i.e. key ^ 0x01) until no closer peers are received in the "
+"DatabaseSearchReplyMessages.\n"
+"This ensures that the true closest peer will be found even if a more-"
+"distant peer had\n"
+"the netdb item."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:380
+msgid "RouterInfo Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:381
+#, python-format
+msgid ""
+"A router publishes its own RouterInfo by directly connecting to a "
+"floodfill router\n"
+"and sending it a I2NP DatabaseStoreMessage\n"
+"with a nonzero Reply Token. The message is not end-to-end garlic "
+"encrypted,\n"
+"as this is a direct connection, so there are no intervening routers\n"
+"(and no need to hide this data anyway).\n"
+"The floodfill router replies with a\n"
+"I2NP DeliveryStatusMessage,\n"
+"with the Message ID set to the value of the Reply Token."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:395
+msgid "LeaseSet Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:396
+msgid ""
+"Storage of LeaseSets is much more sensitive than for RouterInfos, as a "
+"router\n"
+"must take care that the LeaseSet cannot be associated with the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:401
+#, python-format
+msgid ""
+"A router publishes a local LeaseSet by\n"
+"sending a I2NP DatabaseStoreMessage\n"
+"with a nonzero Reply Token over an outbound client tunnel for that "
+"Destination.\n"
+"The message is end-to-end garlic encrypted using the Destination's "
+"Session Key Manager,\n"
+"to hide the message from the tunnel's outbound endpoint.\n"
+"The floodfill router replies with a\n"
+"I2NP DeliveryStatusMessage,\n"
+"with the Message ID set to the value of the Reply Token.\n"
+"This message is sent back to one of the client's inbound tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:414
+msgid "Flooding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:415
+#, python-format
+msgid ""
+"After a floodfill router receives a DatabaseStoreMessage containing a\n"
+"valid RouterInfo or LeaseSet which is newer than that previously stored "
+"in its\n"
+"local NetDb, it \"floods\" it.\n"
+"To flood a NetDb entry, it looks up several (currently %(floodsize)s) "
+"floodfill routers closest to the routing key\n"
+"of the NetDb entry. (The routing key is the SHA256 Hash of the "
+"RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n"
+"By flooding to those closest to the key, not closest to itself, the "
+"floodfill ensures that the storage\n"
+"gets to the right place, even if the storing router did not have good "
+"knowledge of the\n"
+"DHT \"neighborhood\" for the routing key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:426
+#, python-format
+msgid ""
+"The floodfill then directly connects to each of those peers\n"
+"and sends it a I2NP DatabaseStoreMessage\n"
+"with a zero Reply Token. The message is not end-to-end garlic encrypted,\n"
+"as this is a direct connection, so there are no intervening routers\n"
+"(and no need to hide this data anyway).\n"
+"The other routers do not reply or re-flood, as the Reply Token is zero."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:436
+msgid "RouterInfo and LeaseSet Lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:437
+#, python-format
+msgid ""
+"The I2NP DatabaseLookupMessage is used to "
+"request a netdb entry from a floodfill router.\n"
+"Lookups are sent out one of the router's outbound exploratory tunnels.\n"
+"The replies are specified to return via one of the router's inbound "
+"exploratory tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:443
+msgid ""
+"Lookups are generally sent to the two \"good\" (the connection doesn't "
+"fail) floodfill routers closest to the requested key, in parallel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:447
+#, python-format
+msgid ""
+"If the key is found locally by the floodfill router, it responds with a\n"
+"I2NP DatabaseStoreMessage.\n"
+"If the key is not found locally by the floodfill router, it responds with"
+" a\n"
+"I2NP DatabaseSearchReplyMessage\n"
+"containing a list of other floodfill routers close to the key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:455
+msgid ""
+"LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n"
+"RouterInfo lookups are not encrypted and thus are vulnerable to snooping "
+"by the outbound endpoint\n"
+"(OBEP) of the client tunnel. This is due to the expense of the ElGamal "
+"encryption.\n"
+"RouterInfo lookup encryption may be enabled in a future release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:462
+msgid ""
+"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage"
+" or a DatabaseSearchReplyMessage)\n"
+"will be encrypted by including the session key and tag in the lookup.\n"
+"This hides the reply from the inbound gateway (IBGW) of the reply tunnel."
+"\n"
+"Responses to RouterInfo lookups will be encrypted if we enable the lookup"
+" encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:469
+#, python-format
+msgid ""
+"(Reference: Hashing it out in Public Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:473
+msgid ""
+"Due to the relatively small size of the network and the flooding "
+"redundancy of 8x,\n"
+"lookups are usually O(1) rather than O(log n) --\n"
+"a router is highly likely to know a floodfill router close enough to the "
+"key to get the answer on the first try.\n"
+"In releases prior to 0.8.9, routers used a lookup redundancy of two\n"
+"(that is, two lookups were performed in parallel to different peers), and"
+"\n"
+"neither recursive nor iterative routing for lookups was "
+"implemented.\n"
+"Queries were sent through multiple routes simultaneously\n"
+"to reduce the chance of query failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:484
+msgid ""
+"As of release 0.8.9, iterative lookups are implemented with no "
+"lookup redundancy.\n"
+"This is a more efficient and reliable lookup that will work much better\n"
+"when not all floodfill peers are known, and it removes a serious\n"
+"limitation to network growth. As the network grows and each router knows "
+"only a small\n"
+"subset of the floodfill peers, lookups will become O(log n).\n"
+"Even if the peer does not return references closer to the key, the lookup"
+" continues with\n"
+"the next-closest peer, for added robustness, and to prevent a malicious "
+"floodfill from\n"
+"black-holing a part of the key space. Lookups continue until a total "
+"lookup timeout is reached,\n"
+"or the maximum number of peers is queried."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:496
+msgid ""
+"Node IDs are verifiable in that we use the router hash "
+"directly as both the node ID and the Kademlia key.\n"
+"Incorrect responses that are not closer to the search key are generally "
+"ignored.\n"
+"Given the current size of the network, a router has\n"
+"detailed knowledge of the neighborhood of the destination ID space."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:505
+msgid "RouterInfo Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:506
+#, python-format
+msgid ""
+"Note: RouterInfo verification is disabled as of release 0.9.7.1 to "
+"prevent\n"
+"the attack described in the paper\n"
+"Practical Attacks Against the I2P Network.\n"
+"It is not clear if verification can be redesigned to be done safely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:513
+msgid ""
+"To verify a storage was successful, a router simply waits about 10 "
+"seconds,\n"
+"then sends a lookup to another floodfill router close to the key\n"
+"(but not the one the store was sent to).\n"
+"Lookups sent out one of the router's outbound exploratory tunnels.\n"
+"Lookups are end-to-end garlic encrypted to prevent snooping by the "
+"outbound endpoint(OBEP)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:521
+msgid "LeaseSet Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:522
+msgid ""
+"To verify a storage was successful, a router simply waits about 10 "
+"seconds,\n"
+"then sends a lookup to another floodfill router close to the key\n"
+"(but not the one the store was sent to).\n"
+"Lookups sent out one of the outbound client tunnels for the destination "
+"of the LeaseSet being verified.\n"
+"To prevent snooping by the OBEP of the outbound tunnel,\n"
+"lookups are end-to-end garlic encrypted.\n"
+"The replies are specified to return via one of the client's inbound "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:532
+msgid ""
+"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a "
+"DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n"
+"will be encrypted,\n"
+"to hide the reply from the inbound gateway (IBGW) of the reply tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:540
+msgid "Exploration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:541
+#, python-format
+msgid ""
+"Exploration is a special form of netdb lookup, where a router "
+"attempts to learn about\n"
+"new routers.\n"
+"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random "
+"key.\n"
+"As this lookup will fail, the floodfill would normally respond with a\n"
+"I2NP DatabaseSearchReplyMessage containing "
+"hashes of floodfill routers close to the key.\n"
+"This would not be helpful, as the requesting router probably already "
+"knows those floodfills,\n"
+"and it would be impractical to add ALL floodfill routers to the \"don't "
+"include\" field of the lookup.\n"
+"For an exploration query, the requesting router adds a router hash of all"
+" zeros to the\n"
+"\"don't include\" field of the DatabaseLookupMessage.\n"
+"The floodfill will then respond only with non-floodfill routers close to "
+"the requested key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:555
+msgid "Notes on Lookup Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:556
+msgid ""
+"The response to a lookup request is either a Database Store Message (on "
+"success) or a\n"
+"Database Search Reply Message (on failure). The DSRM contains a 'from' "
+"router hash field\n"
+"to indicate the source of the reply; the DSM does not.\n"
+"The DSRM 'from' field is unauthenticated and may be spoofed or invalid.\n"
+"There are no other response tags. Therefore, when making multiple "
+"requests in parallel, it is\n"
+"difficult to monitor the performance of the various floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:566
+msgid "MultiHoming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:568
+msgid ""
+"Destinations may be hosted on multiple routers simultaneously, by using "
+"the same\n"
+"private and public keys (traditionally stored in eepPriv.dat files).\n"
+"As both instances will periodically publish their signed LeaseSets to the"
+" floodfill peers,\n"
+"the most recently published LeaseSet will be returned to a peer "
+"requesting a database lookup.\n"
+"As LeaseSets have (at most) a 10 minute lifetime, should a particular "
+"instance go down,\n"
+"the outage will be 10 minutes at most, and generally much less than that."
+"\n"
+"The multihoming function has been verified and is in use by several "
+"services on the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:578
+msgid "Threat Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:579
+#, python-format
+msgid ""
+"Also discussed on the threat model "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:583
+msgid ""
+"A hostile user may attempt to harm the network by\n"
+"creating one or more floodfill routers and crafting them to offer\n"
+"bad, slow, or no responses.\n"
+"Some scenarios are discussed below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:590
+msgid "General Mitigation Through Growth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:591
+#, python-format
+msgid ""
+"There are currently around %(ffcount)s floodfill routers in the network.\n"
+"Most of the following attacks will become more difficult, or have less "
+"impact,\n"
+"as the network size and number of floodfill routers increase."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:598
+msgid "General Mitigation Through Redundancy"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:599
+#, python-format
+msgid ""
+"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill"
+" routers closest to the key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:604
+msgid "Forgeries"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:605
+msgid ""
+"All netdb entries are signed by their creators, so no router may forge a\n"
+"RouterInfo or LeaseSet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:610
+msgid "Slow or Unresponsive"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:611
+#, python-format
+msgid ""
+"Each router maintains an expanded set of statistics in the\n"
+"peer profile for each floodfill router,"
+"\n"
+"covering various quality metrics for that peer.\n"
+"The set includes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:618
+msgid "Average response time"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:619
+msgid "Percentage of queries answered with the data requested"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:620
+msgid "Percentage of stores that were successfully verified"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:621
+msgid "Last successful store"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:622
+msgid "Last successful lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:623
+msgid "Last response"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:626
+msgid ""
+"Each time a router needs to make a determination on which floodfill "
+"router is closest to a key,\n"
+"it uses these metrics to determine which floodfill routers are \"good\".\n"
+"The methods, and thresholds, used to determine \"goodness\" are "
+"relatively new, and\n"
+"are subject to further analysis and improvement.\n"
+"While a completely unresponsive router will quickly be identified and "
+"avoided,\n"
+"routers that are only sometimes malicious may be much harder to deal with."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:636
+msgid "Sybil Attack (Full Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:637
+#, python-format
+msgid ""
+"An attacker may mount a Sybil attack\n"
+"by creating a large number of floodfill routers spread throughout the "
+"keyspace."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:642
+#, python-format
+msgid ""
+"(In a related example, a researcher recently created a\n"
+"large number of Tor relays.)\n"
+"If successful, this could be an effective DOS attack on the entire "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:648
+msgid ""
+"If the floodfills are not sufficiently misbehaving to be marked as "
+"\"bad\" using the peer profile\n"
+"metrics described above, this is a difficult scenario to handle.\n"
+"Tor's response can be much more nimble in the relay case, as the "
+"suspicious relays\n"
+"can be manually removed from the consensus.\n"
+"Some possible responses for the I2P network are listed below, however "
+"none of them is completely satisfactory:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:656
+msgid ""
+"Compile a list of bad router hashes or IPs, and announce the list through"
+" various means\n"
+"(console news, website, forum, etc.); users would have to manually "
+"download the list and\n"
+"add it to their local \"blacklist\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:661
+msgid ""
+"Ask everyone in the network to enable floodfill manually (fight Sybil "
+"with more Sybil)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:662
+msgid "Release a new software version that includes the hardcoded \"bad\" list"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:663
+msgid ""
+"Release a new software version that improves the peer profile metrics and"
+" thresholds,\n"
+"in an attempt to automatically identify the \"bad\" peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:667
+msgid ""
+"Add software that disqualifies floodfills if too many of them are in a "
+"single IP block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:668
+msgid ""
+"Implement an automatic subscription-based blacklist controlled by a "
+"single individual or group.\n"
+"This would essentially implement a portion of the Tor \"consensus\" "
+"model.\n"
+"Unfortunately it would also give a single individual or group the power "
+"to\n"
+"block participation of any particular router or IP in the network,\n"
+"or even to completely shutdown or destroy the entire network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:677
+msgid "This attack becomes more difficult as the network size grows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:683
+msgid "Sybil Attack (Partial Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:684
+#, python-format
+msgid ""
+"An attacker may mount a Sybil attack\n"
+"by creating a small number (8-15) of floodfill routers clustered closely "
+"in the keyspace,\n"
+"and distribute the RouterInfos for these routers widely.\n"
+"Then, all lookups and stores for a key in that keyspace would be directed"
+"\n"
+"to one of the attacker's routers.\n"
+"If successful, this could be an effective DOS attack on a particular "
+"eepsite, for example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:693
+msgid ""
+"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,"
+"\n"
+"an attacker must use a brute-force method to repeatedly generate router "
+"hashes\n"
+"until he has enough that are sufficiently close to the key.\n"
+"The amount of computational power required for this, which is dependent "
+"on network\n"
+"size, is unknown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:701
+msgid ""
+"As a partial defense against this attack,\n"
+"the algorithm used to determine Kademlia \"closeness\" varies over time.\n"
+"Rather than using the Hash of the key (i.e. H(k)) to determine closeness,"
+"\n"
+"we use the Hash of the key appended with the current date string, i.e. "
+"H(k + YYYYMMDD).\n"
+"A function called the \"routing key generator\" does this, which "
+"transforms the original key into a \"routing key\".\n"
+"In other words, the entire netdb keyspace \"rotates\" every day at UTC "
+"midnight.\n"
+"Any partial-keyspace attack would have to be regenerated every day, for\n"
+"after the rotation, the attacking routers would no longer be close\n"
+"to the target key, or to each other."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:713
+msgid ""
+"This attack becomes more difficult as the network size grows.\n"
+"However, recent research demonstrates that the keyspace rotation is not "
+"particularly effective.\n"
+"An attacker can precompute numerous router hashes in advance,\n"
+"and only a few routers are sufficient to \"eclipse\" a portion\n"
+"of the keyspace within a half hour after rotation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:721
+msgid ""
+"One consequence of daily keyspace rotation is that the distributed "
+"network database\n"
+"may become unreliable for a few minutes after the rotation --\n"
+"lookups will fail because the new \"closest\" router has not received a "
+"store yet.\n"
+"The extent of the issue, and methods for mitigation\n"
+"(for example netdb \"handoffs\" at midnight)\n"
+"are a topic for further study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:731
+msgid "Bootstrap Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:732
+msgid ""
+"An attacker could attempt to boot new routers into an isolated\n"
+"or majority-controlled network by taking over a reseed website,\n"
+"or tricking the developers into adding his reseed website\n"
+"to the hardcoded list in the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:739
+msgid "Several defenses are possible, and most of these are planned:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:743
+msgid ""
+"Disallow fallback from HTTPS to HTTP for reseeding.\n"
+"A MITM attacker could simply block HTTPS, then respond to the HTTP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:747
+msgid ""
+"Changing the reseed task to fetch a subset of RouterInfos from\n"
+"each of several reseed sites rather than using only a single site"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:751
+msgid ""
+"Creating an out-of-network reseed monitoring service that\n"
+"periodically polls reseed websites and verifies that the\n"
+"data are not stale or inconsistent with other views of the network"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:756
+msgid "Bundling reseed data in the installer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:759
+msgid "Query Capture"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:760
+#, python-format
+msgid ""
+"See also lookup\n"
+"(Reference: Hashing it out in Public Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:765
+msgid ""
+"Similar to a bootstrap attack, an attacker using a floodfill router could"
+" attempt to \"steer\"\n"
+"peers to a subset of routers controlled by him by returning their "
+"references."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:770
+msgid ""
+"This is unlikely to work via exploration, because exploration is a low-"
+"frequency task.\n"
+"Routers acquire a majority of their peer references through normal tunnel"
+" building activity.\n"
+"Exploration results are generally limited to a few router hashes,\n"
+"and each exploration query is directed to a random floodfill router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:777
+#, python-format
+msgid ""
+"As of release 0.8.9, iterative lookups are implemented.\n"
+"For floodfill router references returned in a\n"
+"I2NP DatabaseSearchReplyMessage\n"
+"response to a lookup,\n"
+"these references are followed if they are closer (or the next closest) to"
+" the lookup key.\n"
+"The requesting router does not trust that the references are\n"
+"closer to the key (i.e. they are verifiably correct.\n"
+"The lookup also does not stop when no closer key is found, but continues "
+"by querying the\n"
+"next-closet node, until the timeout or maximum number of queries is "
+"reached.\n"
+"This prevents a malicious floodfill from black-holing a part of the key "
+"space.\n"
+"Also, the daily keyspace rotation requires an attacker to regenerate a "
+"router info\n"
+"within the desired key space region.\n"
+"This design ensures that the query capture attack described in\n"
+"Hashing it out in Public\n"
+"is much more difficult."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:796
+msgid "DHT-Based Relay Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:797
+#, python-format
+msgid "(Reference: Hashing it out in Public Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:801
+#, python-format
+msgid ""
+"This doesn't have much to do with floodfill, but see\n"
+"the peer selection page\n"
+"for a discussion of the vulnerabilities of peer selection for tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:807
+msgid "Information Leaks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:808
+#, python-format
+msgid ""
+"(Reference: In Search of an Anonymous and Secure "
+"Lookup Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:812
+#, python-format
+msgid ""
+"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used "
+"by Torsk and NISAN.\n"
+"At first glance, these do not appear to apply to I2P. First, the use of "
+"DHT by Torsk and NISAN\n"
+"is significantly different from that in I2P. Second, I2P's network "
+"database lookups are only\n"
+"loosely correlated to the peer "
+"selection and\n"
+"tunnel building processes; only "
+"previously-known peers\n"
+"are used for tunnels.\n"
+"Also, peer selection is unrelated to any notion of DHT key-closeness."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:823
+msgid ""
+"Some of this may actually be more interesting when the I2P network gets "
+"much larger.\n"
+"Right now, each router knows a large proportion of the network, so "
+"looking up a particular\n"
+"Router Info in the network database is not strongly indicative of a "
+"future intent to use\n"
+"that router in a tunnel. Perhaps when the network is 100 times larger, "
+"the lookup may be\n"
+"more correlative. Of course, a larger network makes a Sybil attack that "
+"much harder."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:831
+#, python-format
+msgid ""
+"However, the general issue of DHT information leakage in I2P needs "
+"further investigation.\n"
+"The floodfill routers are in a position to observe queries and gather "
+"information.\n"
+"Certainly, at a level of f = 0.2 (20% malicious nodes, as "
+"specifed in the paper)\n"
+"we expect that many of the Sybil threats we describe\n"
+"(here,\n"
+"here and\n"
+"here)\n"
+"become problematic for several reasons."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:845
+msgid "Moved to the netdb discussion page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:849
+msgid "End-to-end encryption of additional netDb lookups and responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:853
+msgid "Better methods for tracking lookup responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:2
+msgid "Peer Profiling and Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:3
+msgid "July 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:8
+msgid "Peer Profiling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:10
+#, python-format
+msgid ""
+"Peer profiling is the process of collecting data based on the "
+"observed performance\n"
+"of other routers or peers, and classifying those peers into groups.\n"
+"Profiling does not use any claimed performance data published by "
+"the peer itself\n"
+"in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:17
+msgid "Profiles are used for two purposes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:19
+msgid "Selecting peers to relay our traffic through, which is discussed below"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:20
+#, python-format
+msgid ""
+"Choosing peers from the set of floodfill routers to use for network "
+"database storage and queries,\n"
+"which is discussed on the network database page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:27
+#: i2p2www/pages/site/docs/how/peer-selection.html:187
+#: i2p2www/pages/site/docs/tunnels/implementation.html:286
+msgid "Peer Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:28
+msgid ""
+"Peer selection is the process of choosing which routers\n"
+"on the network we want to relay our messages to go through (which peers "
+"will we \n"
+"ask to join our tunnels).  To accomplish this, we keep track of how each\n"
+"peer performs (the peer's \"profile\") and use that data to estimate how"
+" \n"
+"fast they are, how often they will be able to accept our requests, and \n"
+"whether they seem to be overloaded or otherwise unable to perform what\n"
+"they agree to reliably."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:38
+#, python-format
+msgid ""
+"Unlike some other anonymous networks, in I2P,\n"
+"claimed bandwidth is untrusted and is only used to avoid those "
+"peers\n"
+"advertising very low bandwidth insufficient for routing tunnels.\n"
+"All peer selection is done through profiling.\n"
+"This prevents simple attacks based on peers claiming high bandwidth\n"
+"in order to capture large numbers of tunnels.\n"
+"It also makes\n"
+"timing attacks\n"
+"more difficult."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:50
+msgid ""
+"Peer selection is done quite frequently, as a router may maintain a large"
+" number\n"
+"of client and exploratory tunnels, and a tunnel lifetime is only 10 "
+"minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:56
+msgid "Further Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:57
+#, python-format
+msgid ""
+"For more information see the paper\n"
+"Peer Profiling and Selection in the I2P Anonymous "
+"Network\n"
+"presented at PET-CON 2009.1.\n"
+"See below for notes on minor changes since the "
+"paper was published."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:65
+msgid "Profiles"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:66
+#, python-format
+msgid ""
+"Each peer has a set of data points collected about them, including "
+"statistics \n"
+"about how long it takes for them to reply to a network database query, "
+"how \n"
+"often their tunnels fail, and how many new peers they are able to "
+"introduce \n"
+"us to, as well as simple data points such as when we last heard from them"
+" or\n"
+"when the last communication error occurred.  The specific data points "
+"gathered\n"
+"can be found in the code."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:75
+msgid ""
+"Profiles are fairly small, a few KB. To control memory usage, the profile"
+" expiration time\n"
+"lessens as the number of profiles grows.\n"
+"Profiles are kept in memory until router shutdown, when they are written "
+"to disk.\n"
+"At startup, the profiles are read so the router need not reinitialize all"
+" profiles,\n"
+"thus allowing a router to quickly re-integrate into the network after "
+"startup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:85
+msgid "Peer Summaries"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:86
+msgid ""
+"While the profiles themselves can be considered a summary of a peer's \n"
+"performance, to allow for effective peer selection we break each summary "
+"down \n"
+"into four simple values, representing the peer's speed, its capacity, how"
+" well \n"
+"integrated into the network it is, and whether it is failing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:93
+msgid "Speed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:94
+msgid ""
+"The speed calculation\n"
+"simply goes through the profile and estimates how much data we can\n"
+"send or receive on a single tunnel through the peer in a minute.  For "
+"this estimate it just looks at\n"
+"performance in the previous minute."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:101
+msgid "Capacity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:102
+msgid ""
+"The capacity calculation\n"
+"simply goes through the profile and estimates how many tunnels the peer\n"
+"would agree to participate in over a given time period.  For this "
+"estimate it looks at \n"
+"how many tunnel build requests\n"
+"the peer has accepted, rejected, and dropped, and how many\n"
+"of the agreed-to tunnels later failed.\n"
+"While the calculation is time-weighted so that recent activity counts "
+"more than later activity,\n"
+"statistics up to 48 hours old may be included."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:113
+msgid ""
+"Recognizing and avoiding unreliable and unreachable\n"
+"peers is critically important.\n"
+"Unfortunately, as the tunnel building and testing require the "
+"participation of several peers,\n"
+"it is difficult to positively identify the cause of a dropped build "
+"request or test failure.\n"
+"The router assigns a probability of failure to each of the\n"
+"peers, and uses that probability in the capacity calculation.\n"
+"Drops and test failures are weighted much higher than rejections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:123
+msgid "Peer organization"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:124
+msgid ""
+"As mentioned above, we drill through each peer's profile to come up with "
+"a \n"
+"few key calculations, and based upon those, we organize each peer into "
+"three\n"
+"groups - fast, high capacity, and standard."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:130
+msgid "The groupings are not mutually exclusive, nor are they unrelated:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:134
+msgid ""
+"A peer is considered \"high capacity\" if its capacity calculation meets "
+"or \n"
+"exceeds the median of all peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:138
+msgid ""
+"A peer is considered \"fast\" if they are already \"high capacity\" and "
+"their \n"
+"speed calculation meets or exceeds the median of all peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:142
+msgid "A peer is considered \"standard\" if it is not \"high capacity\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:145
+#, python-format
+msgid ""
+"These groupings are implemented in the router's\n"
+"ProfileOrganizer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:150
+msgid "Group size limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:151
+msgid "The size of the groups may be limited."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:156
+msgid ""
+"The fast group is limited to 30 peers.\n"
+"If there would be more, only the ones with the highest speed rating are "
+"placed in the group."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:160
+msgid ""
+"The high capacity group is limited to 75 peers (including the fast group)"
+"\n"
+"If there would be more, only the ones with the highest capacity rating "
+"are placed in the group."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:164
+msgid ""
+"The standard group has no fixed limit, but is somewhat smaller than the "
+"number of RouterInfos\n"
+"stored in the local network database.\n"
+"On an active router in today's network, there may be about 1000 "
+"RouterInfos and 500 peer profiles\n"
+"(including those in the fast and high capacity groups)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:172
+msgid "Recalculation and Stability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:173
+msgid ""
+"Summaries are recalculated, and peers are resorted into groups, every 45 "
+"seconds."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:177
+msgid ""
+"The groups tend to be fairly stable, that is, there is not much \"churn\""
+" in the rankings\n"
+"at each recalculation.\n"
+"Peers in the fast and high capacity groups get more tunnels build through"
+" them, which increases their speed and capacity ratings,\n"
+"which reinforces their presence in the group."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:188
+msgid "The router selects peers from the above groups to build tunnels through."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:193
+msgid "Peer Selection for Client Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:194
+msgid ""
+"Client tunnels are used for application traffic, such as for HTTP proxies"
+" and web servers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:198
+msgid ""
+"To reduce the susceptibility to some attacks,\n"
+"and increase performance,\n"
+"peers for building client tunnels are chosen randomly from the smallest "
+"group, which is the \"fast\" group.\n"
+"There is no bias toward selecting peers that were previously participants"
+" in a tunnel for the same client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:206
+msgid "Peer Selection for Exploratory Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:207
+msgid ""
+"Exploratory tunnels are used for router administrative purposes, such as "
+"network database traffic\n"
+"and testing client tunnels.\n"
+"Exploratory tunnels are also used to contact previously unconnected "
+"routers, which is why\n"
+"they are called \"exploratory\".\n"
+"These tunnels are usually low-bandwidth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:215
+msgid ""
+"Peers for building exploratory tunnels are generally chosen randomly from"
+" the standard group.\n"
+"If the success rate of these build attempts is low compared to the client"
+" tunnel build success rate,\n"
+"the router will select a weighted average of peers randomly from the high"
+" capacity group instead.\n"
+"This helps maintain a satisfactory build success rate even when network "
+"performance is poor.\n"
+"There is no bias toward selecting peers that were previously participants"
+" in an exploratory tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:223
+msgid ""
+"As the standard group includes a very large subset of all peers the "
+"router knows about,\n"
+"exploratory tunnels are essentially built through a random selection of "
+"all peers,\n"
+"until the build success rate becomes too low."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:231
+msgid "Restrictions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:232
+msgid ""
+"To prevent some simple attacks, and for performance, there are the "
+"following restrictions:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:236
+msgid "Two peers from the same /16 IP space may not be in the same tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:239
+msgid ""
+"A peer may participate in a maximum of 33% of all tunnels created by "
+"the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:242
+msgid "Peers with extremely low bandwidth are not used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:245
+msgid "Peers for which a recent connection attempt failed are not used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:252
+msgid "Peer Ordering in Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:253
+#, python-format
+msgid ""
+"Peers are ordered within tunnels to\n"
+"to deal with the predecessor attack\n"
+"(2008 update).\n"
+"More information is on the tunnel "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:268
+msgid "Continue to analyze an tune speed and capacity calculations as necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:271
+msgid ""
+"Implement a more aggressive ejection strategy if necessary to control "
+"memory usage as the network grows"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:274
+msgid "Evaluate group size limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:277
+msgid "Use GeoIP data to include or exclude certain peers, if configured"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:283
+#, python-format
+msgid ""
+"For those reading the paper\n"
+"Peer Profiling and Selection in the I2P Anonymous "
+"Network,\n"
+"please keep in mind the following minor changes in I2P since the paper's "
+"publication:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:289
+msgid "The Integration calculation is still not used"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:290
+msgid "In the paper, \"groups\" are called \"tiers\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:291
+msgid "The \"Failing\" tier is no longer used"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:292
+msgid "The \"Not Failing\" tier is now named \"Standard\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:301
+msgid "One Cell Enough"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:303
+msgid "Tor Entry Guards"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:305
+msgid "Murdoch 2007 Paper"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:307
+msgid "Tune-up for Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:309
+msgid "Low-resource Routing Attacks Against Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:2
+msgid "Introducing I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:5
+msgid "I2P: A scalable framework for anonymous communication"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:7
+msgid "Table of Contents"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:9
+#: i2p2www/pages/site/docs/how/tech-intro.html:24
+#: i2p2www/pages/site/docs/transport/ssu.html:281
+msgid "Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:11
+msgid "I2P Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:16
+#: i2p2www/pages/site/docs/how/tech-intro.html:401
+msgid "Transport protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:17
+#: i2p2www/pages/site/docs/how/tech-intro.html:458
+msgid "Cryptography"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:25
+msgid ""
+"I2P is a scalable, self organizing, resilient packet switched anonymous \n"
+"network layer, upon which any number of different anonymity or security "
+"conscious \n"
+"applications can operate. Each of these applications may make their own "
+"anonymity, \n"
+"latency, and throughput tradeoffs without worrying about the proper "
+"implementation \n"
+"of a free route mixnet, allowing them to blend their activity with the "
+"larger \n"
+"anonymity set of users already running on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:34
+msgid ""
+"Applications available already provide the full range of typical Internet"
+" activities -\n"
+"anonymous web browsing, web hosting, chat, file sharing, e-mail,\n"
+"blogging and content syndication, newsgroups, as well as several other "
+"applications under development."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:40
+msgid "Web browsing: using any existing browser that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:41
+msgid "Chat: IRC, Jabber, I2P-Messenger."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:42
+msgid ""
+"File sharing: I2PSnark, Robert, iMule, \n"
+"I2Phex, PyBit, I2P-bt\n"
+"and others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:47
+msgid ""
+"E-mail: susimail and I2P-Bote."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:48
+msgid ""
+"Blog: using e.g. the pebble plugin or the distributed blogging software "
+"Syndie."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:49
+msgid ""
+"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS "
+"cloud over I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:50
+msgid "Newsgroups: using any newsgroup reader that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:53
+msgid ""
+"Unlike web sites hosted within content distribution networks like Freenet \n"
+"or GNUnet, the services "
+"hosted on \n"
+"I2P are fully interactive - there are traditional web-style search "
+"engines, \n"
+"bulletin boards, blogs you can comment on, database driven sites, and "
+"bridges \n"
+"to query static systems like Freenet without needing to install it "
+"locally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:61
+msgid ""
+"With all of these anonymity enabled applications, I2P takes on the role \n"
+"of the message oriented middleware - applications say that they want to "
+"send \n"
+"some data to a cryptographic identifier (a \"destination\") and I2P takes"
+" care \n"
+"of making sure it gets there securely and anonymously. I2P also bundles a"
+" \n"
+"simple streaming library to allow I2P's "
+"anonymous \n"
+"best-effort messages to transfer as reliable, in-order streams, "
+"transparently \n"
+"offering a TCP based congestion control algorithm tuned for the high "
+"bandwidth \n"
+"delay product of the network. While there have been several simple SOCKS "
+"proxies \n"
+"available to tie existing applications into the network, their value has "
+"been \n"
+"limited as nearly every application routinely exposes what, in an "
+"anonymous \n"
+"context, is sensitive information. The only safe way to go is to fully "
+"audit \n"
+"an application to ensure proper operation and to assist in that we "
+"provide \n"
+"a series of APIs in various languages which can be used to make the most "
+"out \n"
+"of the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:78
+#, python-format
+msgid ""
+"I2P is not a research project - academic, commercial, or governmental, "
+"but \n"
+"is instead an engineering effort aimed at doing whatever is necessary to "
+"provide \n"
+"a sufficient level of anonymity to those who need it. It has been in "
+"active \n"
+"development since early 2003 with one full time developer and a dedicated"
+" \n"
+"group of part time contributors from all over the world. All of the work "
+"done \n"
+"on I2P is open source and freely available on the website, \n"
+"with the majority of the code released outright into the public domain, "
+"though \n"
+"making use of a few cryptographic routines under BSD-style licenses. The "
+"people \n"
+"working on I2P do not control what people release client applications "
+"under, \n"
+"and there are several GPL'ed applications available (I2PTunnel, \n"
+"susimail, I2PSnark, I2P-"
+"Bote, \n"
+"I2Phex and others.).\n"
+"Funding for I2P comes entirely from "
+"donations,\n"
+"and does not receive any tax breaks in any jurisdiction at this time,\n"
+"as many of the developers are themselves anonymous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:96
+msgid "Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:98
+msgid ""
+"To understand I2P's operation, it is essential to understand a few key "
+"concepts. \n"
+"First, I2P makes a strict separation between the software participating "
+"in \n"
+"the network (a \"router\") and the anonymous endpoints (\"destinations\")"
+" associated \n"
+"with individual applications. The fact that someone is running I2P is not"
+" \n"
+"usually a secret. What is hidden is information on what the user is "
+"doing, \n"
+"if anything at all, as well as what router a particular destination is "
+"connected \n"
+"to. End users will typically have several local destinations on their "
+"router \n"
+"- for instance, one proxying in to IRC servers, another supporting the "
+"user's \n"
+"anonymous webserver (\"eepsite\"), another for an I2Phex instance, "
+"another for \n"
+"torrents, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:111
+msgid ""
+"Another critical concept to understand is the \"tunnel\".\n"
+"A tunnel is a directed path through an explicitly selected list of "
+"routers.\n"
+"Layered encryption is used, so each of the routers can only decrypt a "
+"single layer.\n"
+"The decrypted information contains the IP of the next router, along with\n"
+"the encrypted information to be forwarded.\n"
+"Each tunnel has a starting point (the first router, also known as "
+"\"gateway\")\n"
+"and an end point. Messages can be sent only in one way. To send messages "
+"back,\n"
+"another tunnel is required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:122
+#: i2p2www/pages/site/docs/tunnels/implementation.html:105
+msgid "Inbound and outbound tunnel schematic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:124
+msgid "Figure 1: Two types of tunnels exist: inbound and outbound."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:127
+msgid ""
+"Two types of tunnels exist:\n"
+"\"outbound\" tunnels send messages away from the tunnel creator,\n"
+"while \"inbound\" tunnels bring messages to the tunnel creator.\n"
+"Combining these two tunnels allows users to send messages to each other.\n"
+"The sender (\"Alice\" in the above image) sets up an outbound tunnel,\n"
+"while the receiver (\"Bob\" in the above image) creates an inbound "
+"tunnel.\n"
+"The gateway of an inbound tunnel can receive messages from any other user"
+"\n"
+"and will send them on until the endpoint (\"Bob\").\n"
+"The endpoint of the outbound tunnel will need to send the message\n"
+"on to the gateway of the inbound tunnel.\n"
+"To do this, the sender (\"Alice\") adds instructions to her encrypted "
+"message.\n"
+"Once the endpoint of the outbound tunnel decrypts the message,\n"
+"it will have instructions to forward the message to the correct\n"
+"inbound gateway (the gateway to \"Bob\")."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:144
+msgid ""
+"A third critical concept to understand is I2P's \"network "
+"database\" (or \"netDb\") \n"
+"- a pair of algorithms used to share network metadata. The two types of "
+"metadata \n"
+"carried are \"routerInfo\" and \"leaseSets\" - the "
+"routerInfo gives routers the \n"
+"data necessary for contacting a particular router (their public keys, "
+"transport \n"
+"addresses, etc), while the leaseSet gives routers the information "
+"necessary \n"
+"for contacting a particular destination. A leaseSet contains a number of "
+"\"leases\".\n"
+"Each of this leases specifies a tunnel gateway, which allows reaching a "
+"specific destination.\n"
+"The full information contained in a lease:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:155
+msgid "Inbound gateway for a tunnel that allows reaching a specific destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:156
+msgid "Time when a tunnel expires."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:157
+msgid ""
+"Pair of public keys to be able to encrypt messages (to send through the "
+"tunnel and reach the destination)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:159
+msgid ""
+"Routers themselves send their routerInfo to the netDb directly, while "
+"leaseSets are sent through outbound tunnels\n"
+"(leaseSets need to be sent anonymously, to avoid correlating a router "
+"with his leaseSets)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:164
+msgid ""
+"We can combine the above concepts to build successful connections in the "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:168
+msgid ""
+"To build up her own inbound and outbound tunnels, Alice does a lookup in "
+"the netDb to collect routerInfo.\n"
+"This way, she gathers lists of peers she can use as hops in her tunnels.\n"
+"She can then send a build message to the first hop, requesting the "
+"construction of a tunnel and asking\n"
+"that router to send the construction message onward, until the tunnel has"
+" been constructed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:175
+msgid "Request information on other routers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:177
+msgid "Build tunnel using router information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:179
+msgid "Figure 2: Router information is used to build tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:182
+msgid ""
+"When Alice wants to send a message to Bob, she first does a lookup in the"
+" \n"
+"netDb to find Bob's leaseSet, giving her his current inbound tunnel "
+"gateways. \n"
+"She then picks one of her outbound tunnels and sends the message down it "
+"with \n"
+"instructions for the outbound tunnel's endpoint to forward the message on"
+" \n"
+"to one of Bob's inbound tunnel gateways. When the outbound tunnel "
+"endpoint \n"
+"receives those instructions, it forwards the message as requested, and "
+"when \n"
+"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel"
+" \n"
+"to Bob's router. If Alice wants Bob to be able to reply to the message, "
+"she \n"
+"needs to transmit her own destination explicitly as part of the message "
+"itself.\n"
+"This can be done by introducing a higher-level layer, which is done in "
+"the\n"
+"streaming library.\n"
+"Alice may also cut down on the response time by bundling her most \n"
+"recent LeaseSet with the message so that Bob doesn't need to do a netDb "
+"lookup \n"
+"for it when he wants to reply, but this is optional."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:199
+msgid "Connect tunnels using LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:199
+msgid "Connect tunnels using leaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:201
+msgid "Figure 3: LeaseSets are used to connect outbound and inbound tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:204
+msgid ""
+"While the tunnels themselves have layered encryption to prevent "
+"unauthorized \n"
+"disclosure to peers inside the network (as the transport layer itself "
+"does \n"
+"to prevent unauthorized disclosure to peers outside the network), it is "
+"necessary \n"
+"to add an additional end to end layer of encryption to hide the message "
+"from \n"
+"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n"
+"encryption\" lets Alice's router wrap up multiple messages into a "
+"single \n"
+"\"garlic message\", encrypted to a particular public key so that "
+"intermediary \n"
+"peers cannot determine either how many messages are within the garlic, "
+"what \n"
+"those messages say, or where those individual cloves are destined. For "
+"typical \n"
+"end to end communication between Alice and Bob, the garlic will be "
+"encrypted \n"
+"to the public key published in Bob's leaseSet, allowing the message to be"
+" \n"
+"encrypted without giving out the public key to Bob's own router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:219
+msgid ""
+"Another important fact to keep in mind is that I2P is entirely message "
+"based \n"
+"and that some messages may be lost along the way. Applications using I2P "
+"can \n"
+"use the message oriented interfaces and take care of their own congestion"
+" \n"
+"control and reliability needs, but most would be best served by reusing "
+"the \n"
+"provided streaming library to view I2P as "
+"a streams \n"
+"based network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:229
+msgid ""
+"Both inbound and outbound tunnels work along similar principles.\n"
+"The tunnel gateway accumulates a number of tunnel messages, eventually "
+"preprocessing \n"
+"them into something for tunnel delivery. Next, the gateway encrypts that "
+"preprocessed \n"
+"data and forwards it to the first hop. That peer and subsequent tunnel "
+"participants \n"
+"add on a layer of encryption after verifying that it isn't a duplicate "
+"before \n"
+"forward it on to the next peer. Eventually, the message arrives at the "
+"endpoint \n"
+"where the messages are split out again and forwarded on as requested. The"
+" \n"
+"difference arises in what the tunnel's creator does - for inbound "
+"tunnels, \n"
+"the creator is the endpoint and they simply decrypt all of the layers "
+"added, \n"
+"while for outbound tunnels, the creator is the gateway and they pre-"
+"decrypt \n"
+"all of the layers so that after all of the layers of per-hop encryption "
+"are \n"
+"added, the message arrives in the clear at the tunnel endpoint."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:244
+msgid ""
+"The choice of specific peers to pass on messages as well as their "
+"particular \n"
+"ordering is important to understanding both I2P's anonymity and "
+"performance \n"
+"characteristics. While the network database (below) has its own criteria "
+"for \n"
+"picking what peers to query and store entries on, tunnel creators may use"
+" any peers \n"
+"in the network in any order (and even any number of times) in a single "
+"tunnel. \n"
+"If perfect latency and capacity data were globally known, selection and "
+"ordering \n"
+"would be driven by the particular needs of the client in tandem with "
+"their \n"
+"threat model. Unfortunately, latency and capacity data is not trivial to "
+"gather \n"
+"anonymously, and depending upon untrusted peers to provide this "
+"information \n"
+"has its own serious anonymity implications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:257
+msgid ""
+"From an anonymity perspective, the simplest technique would be to pick "
+"peers \n"
+"randomly from the entire network, order them randomly and use those peers"
+" \n"
+"in that order for all eternity. From a performance perspective, the "
+"simplest \n"
+"technique would be to pick the fastest peers with the necessary spare "
+"capacity, \n"
+"spreading the load across different peers to handle transparent failover,"
+" \n"
+"and to rebuild the tunnel whenever capacity information changes. While "
+"the \n"
+"former is both brittle and inefficient, the later requires inaccessible "
+"information \n"
+"and offers insufficient anonymity. I2P is instead working on offering a "
+"range \n"
+"of peer selection strategies, coupled with anonymity aware measurement "
+"code \n"
+"to organize the peers by their profiles."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:270
+msgid ""
+"As a base, I2P is constantly profiling the peers with which it interacts"
+" \n"
+"with by measuring their indirect behavior - for instance, when a peer "
+"responds \n"
+"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in "
+"the \n"
+"profiles for all of the routers involved in the two tunnels (inbound and "
+"outbound) \n"
+"through which the request and response passed, as well as the queried "
+"peer's \n"
+"profile. Direct measurement, such as transport layer latency or "
+"congestion, \n"
+"is not used as part of the profile, as it can be manipulated and "
+"associated \n"
+"with the measuring router, exposing them to trivial attacks. While "
+"gathering \n"
+"these profiles, a series of calculations are run on each to summarize its"
+" \n"
+"performance - its latency, capacity to handle lots of activity, whether "
+"they \n"
+"are currently overloaded, and how well integrated into the network they "
+"seem \n"
+"to be. These calculations are then compared for active peers to organize "
+"the \n"
+"routers into four tiers - fast and high capacity, high capacity, not "
+"failing, \n"
+"and failing. The thresholds for those tiers are determined dynamically, "
+"and \n"
+"while they currently use fairly simple algorithms, alternatives exist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:288
+msgid ""
+"Using this profile data, the simplest reasonable peer selection strategy"
+" \n"
+"is to pick peers randomly from the top tier (fast and high capacity), and"
+" \n"
+"this is currently deployed for client tunnels. Exploratory tunnels (used "
+"for \n"
+"netDb and tunnel management) pick peers randomly from the \"not failing\""
+" tier \n"
+"(which includes routers in 'better' tiers as well), allowing the peer to "
+"sample \n"
+"routers more widely, in effect optimizing the peer selection through "
+"randomized \n"
+"hill climbing. These strategies alone do however leak information "
+"regarding \n"
+"the peers in the router's top tier through predecessor and netDb "
+"harvesting \n"
+"attacks. In turn, several alternatives exist which, while not balancing "
+"the \n"
+"load as evenly, will address the attacks mounted by particular classes of"
+" \n"
+"adversaries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:302
+msgid ""
+"By picking a random key and ordering the peers according to their XOR "
+"distance \n"
+"from it, the information leaked is reduced in predecessor and harvesting "
+"attacks \n"
+"according to the peers' failure rate and the tier's churn. Another simple"
+" \n"
+"strategy for dealing with netDb harvesting attacks is to simply fix the "
+"inbound \n"
+"tunnel gateway(s) yet randomize the peers further on in the tunnels. To "
+"deal \n"
+"with predecessor attacks for adversaries which the client contacts, the "
+"outbound \n"
+"tunnel endpoints would also remain fixed. The selection of which peer to "
+"fix \n"
+"on the most exposed point would of course need to have a limit to the "
+"duration, \n"
+"as all peers fail eventually, so it could either be reactively adjusted "
+"or \n"
+"proactively avoided to mimic a measured mean time between failures of "
+"other \n"
+"routers. These two strategies can in turn be combined, using a fixed "
+"exposed \n"
+"peer and an XOR based ordering within the tunnels themselves. A more "
+"rigid \n"
+"strategy would fix the exact peers and ordering of a potential tunnel, "
+"only \n"
+"using individual peers if all of them agree to participate in the same "
+"way \n"
+"each time. This varies from the XOR based ordering in that the "
+"predecessor \n"
+"and successor of each peer is always the same, while the XOR only makes "
+"sure \n"
+"their order doesn't change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:322
+#, python-format
+msgid ""
+"As mentioned before, I2P currently (release 0.8) includes the tiered \n"
+"random strategy above, with XOR-based ordering. A \n"
+"more detailed discussion of the mechanics involved in tunnel operation, "
+"management, \n"
+"and peer selection can be found in the tunnel "
+"spec."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:330
+#, python-format
+msgid ""
+"As mentioned earlier, I2P's netDb works to share the network's metadata.\n"
+"This is detailed in the network database page,\n"
+"but a basic explanation is available below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:336
+msgid ""
+"A percentage of I2P users are appointed as 'floodfill peers'.\n"
+"Currently, I2P installations that have a lot of bandwidth and are fast "
+"enough,\n"
+"will appoint themselves as floodfill as soon as the number of existing "
+"floodfill routers\n"
+"drops too low."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:343
+#, python-format
+msgid ""
+"Other I2P routers will store their data and lookup data by sending simple"
+" 'store' and 'lookup' queries to the floodfills.\n"
+"If a floodfill router receives a 'store' query, it will spread the "
+"information to other floodfill routers\n"
+"using the Kademlia "
+"algorithm.\n"
+"The 'lookup' queries currently function differently, to avoid an "
+"important\n"
+"security issue.\n"
+"When a lookup is done, the floodfill router will not forward the lookup "
+"to other peers,\n"
+"but will always answer by itself (if it has the requested data)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:353
+msgid "Two types of information are stored in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:357
+msgid ""
+"A RouterInfo stores information on a specific I2P router and how "
+"to contact it"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:358
+msgid ""
+"A LeaseSet stores information on a specific destination (e.g. I2P "
+"website, e-mail server...)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:360
+msgid ""
+"All of this information is signed by the publishing party and verified by"
+" any I2P router using or storing the information.\n"
+"In addition, the data contains timing information, to avoid storage of "
+"old entries and possible attacks.\n"
+"This is also why I2P bundles the necessary code for maintaining the "
+"correct time, occasionally querying some SNTP servers \n"
+"(the pool.ntp.org round robin by"
+" default)\n"
+"and detecting skew between routers at the transport layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:368
+msgid "Some additional remarks are also important."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:373
+msgid "Unpublished and encrypted leasesets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:374
+msgid ""
+"One could only want specific people to be able to reach a destination.\n"
+"This is possible by not publishing the destination in the netDb. You will"
+" however have to transmit the destination by other means.\n"
+"An alternative are the 'encrypted leaseSets'. These leaseSets can only be"
+" decoded by people with access to the decryption key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:381
+msgid "Bootstrapping:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:382
+msgid ""
+"Bootstrapping the netDb is quite simple. Once a router manages to receive"
+" a single routerInfo of a reachable peer,\n"
+"it can query that router for references to other routers in the network.\n"
+"Currently, a number of users post their routerInfo files to a website to "
+"make this information available.\n"
+"I2P automatically connects to one of these websites to gather routerInfo "
+"files and bootstrap."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:390
+msgid "Lookup scalability:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:391
+msgid ""
+"Lookups in the I2P network are not forwarded to other netDb routers.\n"
+"Currently, this is not a major problem, since the network is not very "
+"large.\n"
+"However, as the network grows, not all routerInfo and leaseSet files will"
+" be present\n"
+"on each netDb router. This will cause a deterioration of the percentage "
+"of successful lookups.\n"
+"Because of this, refinements to the netDb will be done in the next "
+"releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:402
+msgid ""
+"Communication between routers needs to provide confidentiality and "
+"integrity \n"
+"against external adversaries while authenticating that the router "
+"contacted \n"
+"is the one who should receive a given message. The particulars of how "
+"routers \n"
+"communicate with other routers aren't critical - three separate protocols"
+" \n"
+"have been used at different points to provide those bare necessities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:410
+#, python-format
+msgid ""
+"I2P started with a TCP-based protocol which \n"
+"has since been disabled. Then, to accommodate the need for high degree "
+"communication \n"
+"(as a number of routers will end up speaking with many others), I2P moved"
+" \n"
+"from a TCP based transport to a UDP-based one - "
+"\"Secure \n"
+"Semireliable UDP\", or \"SSU\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:418
+#, python-format
+msgid "As described in the SSU spec:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:422
+msgid ""
+"The goal of this protocol is to provide secure, authenticated, \n"
+"semireliable and unordered message delivery, exposing only a minimal "
+"amount \n"
+"of data easily discernible to third parties. It should support high "
+"degree \n"
+"communication as well as TCP-friendly congestion control and may include"
+" \n"
+"PMTU detection. It should be capable of efficiently moving bulk data at "
+"rates \n"
+"sufficient for home users. In addition, it should support techniques for "
+"addressing \n"
+"network obstacles, like most NATs or firewalls."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:432
+#, python-format
+msgid ""
+"Following the introduction of SSU, after issues with congestion collapse"
+" \n"
+"appeared, a new NIO-based TCP transport called NTCP \n"
+"was implemented. It is enabled by default for outbound connections only. "
+"Those \n"
+"who configure their NAT/firewall to allow inbound connections and specify"
+" \n"
+"the external host and port (dyndns/etc is ok) on /config.jsp can receive "
+"inbound \n"
+"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread"
+" \n"
+"per connection issues of the old TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:442
+msgid ""
+"I2P supports multiple transports simultaneously. A particular transport \n"
+"for an outbound connection is selected with \"bids\". Each transport bids"
+" for \n"
+"the connection and the relative value of these bids assigns the priority."
+" \n"
+"Transports may reply with different bids, depending on whether there is "
+"already \n"
+"an established connection to the peer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:450
+#, python-format
+msgid ""
+"The current implementation ranks NTCP as the highest-priority transport \n"
+"for outbound connections in most situations. SSU is enabled for both "
+"outbound \n"
+"and inbound connections. Your firewall and your I2P router must be "
+"configured \n"
+"to allow inbound NTCP connections. For further information see the NTCP \n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:459
+msgid ""
+"A bare minimum set of cryptographic primitives are combined together to \n"
+"provide I2P's layered defenses against a variety of adversaries. At the "
+"lowest \n"
+"level, inter router communication is protected by the transport layer "
+"security \n"
+"- SSU encrypts each packet with AES256/CBC with both an explicit IV and "
+"MAC \n"
+"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a "
+"2048bit \n"
+"Diffie-Hellman exchange, station-to-station authentication with the other"
+" \n"
+"router's DSA key, plus each network message has their own hash for local "
+"integrity \n"
+"checking. Tunnel messages passed over the "
+"transports \n"
+"have their own layered AES256/CBC encryption with an explicit IV and "
+"verified \n"
+"at the tunnel endpoint with an additional SHA256 hash. Various other "
+"messages \n"
+"are passed along inside \"garlic messages\", which are encrypted with "
+"ElGamal/AES+SessionTags \n"
+"(explained below)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:474
+msgid "Garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:475
+msgid ""
+"Garlic messages are an extension of \"onion\" layered encryption, "
+"allowing \n"
+"the contents of a single message to contain multiple \"cloves\" - fully "
+"formed \n"
+"messages alongside their own instructions for delivery. Messages are "
+"wrapped \n"
+"into a garlic message whenever the message would otherwise be passing in "
+"cleartext \n"
+"through a peer who should not have access to the information - for "
+"instance, \n"
+"when a router wants to ask another router to participate in a tunnel, "
+"they \n"
+"wrap the request inside a garlic, encrypt that garlic to the receiving "
+"router's \n"
+"2048bit ElGamal public key, and forward it through a tunnel. Another "
+"example \n"
+"is when a client wants to send a message to a destination - the sender's "
+"router \n"
+"will wrap up that data message (alongside some other messages) into a "
+"garlic, \n"
+"encrypt that garlic to the 2048bit ElGamal public key published in the "
+"recipient's \n"
+"leaseSet, and forward it through the appropriate tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:490
+msgid ""
+"The \"instructions\" attached to each clove inside the encryption layer "
+"includes \n"
+"the ability to request that the clove be forwarded locally, to a remote "
+"router, \n"
+"or to a remote tunnel on a remote router. There are fields in those "
+"instructions \n"
+"allowing a peer to request that the delivery be delayed until a certain "
+"time \n"
+"or condition has been met, though they won't be honored until the nontrivial \n"
+"delays are deployed. It is possible to explicitly route garlic "
+"messages \n"
+"any number of hops without building tunnels, or even to reroute tunnel "
+"messages \n"
+"by wrapping them in garlic messages and forwarding them a number of hops "
+"prior \n"
+"to delivering them to the next hop in the tunnel, but those techniques "
+"are \n"
+"not currently used in the existing implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:503
+msgid "Session tags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:504
+msgid ""
+"As an unreliable, unordered, message based system, I2P uses a simple "
+"combination \n"
+"of asymmetric and symmetric encryption algorithms to provide data "
+"confidentiality \n"
+"and integrity to garlic messages. As a whole, the combination is referred"
+" \n"
+"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to "
+"describe \n"
+"the simple use of 2048bit ElGamal, AES256, SHA256 and 32 byte nonces."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:543
+msgid ""
+"Session tags themselves have a very short lifetime, after which they are"
+" \n"
+"discarded if not used. In addition, the quantity stored for each key is "
+"limited, \n"
+"as are the number of keys themselves - if too many arrive, either new or "
+"old \n"
+"messages may be dropped. The sender keeps track whether messages using "
+"session \n"
+"tags are getting through, and if there isn't sufficient communication it "
+"may \n"
+"drop the ones previously assumed to be properly delivered, reverting back"
+" \n"
+"to the full expensive ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:553
+msgid ""
+"One alternative is to transmit only a single session tag, and from that,"
+" \n"
+"seed a deterministic PRNG for determining what tags to use or expect. By "
+"keeping \n"
+"this PRNG roughly synchronized between the sender and recipient (the "
+"recipient \n"
+"precomputes a window of the next e.g. 50 tags), the overhead of "
+"periodically \n"
+"bundling a large number of tags is removed, allowing more options in the "
+"space/time \n"
+"tradeoff, and perhaps reducing the number of ElGamal encryptions "
+"necessary. \n"
+"However, it would depend upon the strength of the PRNG to provide the "
+"necessary \n"
+"cover against internal adversaries, though perhaps by limiting the amount"
+" \n"
+"of times each PRNG is used, any weaknesses can be minimized. At the "
+"moment, \n"
+"there are no immediate plans to move towards these synchronized PRNGs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:566
+msgid "Future"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:567
+msgid ""
+"While I2P is currently functional and sufficient for many scenarios, "
+"there \n"
+"are several areas which require further improvement to meet the needs of "
+"those \n"
+"facing more powerful adversaries as well as substantial user experience "
+"optimization."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:573
+msgid "Restricted route operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:574
+msgid ""
+"I2P is an overlay network designed to be run on top of a functional "
+"packet \n"
+"switched network, exploiting the end to end principle to offer anonymity "
+"and \n"
+"security. While the Internet no longer fully embraces the end to end "
+"principle\n"
+"(due to the usage of NAT), \n"
+"I2P does require a substantial portion of the network to be reachable - "
+"there \n"
+"may be a number of peers along the edges running using restricted routes,"
+" \n"
+"but I2P does not include an appropriate routing algorithm for the "
+"degenerate \n"
+"case where most peers are unreachable. It would, however work on top of a"
+" \n"
+"network employing such an algorithm."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:586
+msgid ""
+"Restricted route operation, where there are limits to what peers are "
+"reachable \n"
+"directly, has several different functional and anonymity implications, "
+"dependent \n"
+"upon how the restricted routes are handled. At the most basic level, "
+"restricted \n"
+"routes exist when a peer is behind a NAT or firewall which does not allow"
+" \n"
+"inbound connections. This was largely addressed in I2P 0.6.0.6 by "
+"integrating \n"
+"distributed hole punching into the transport layer, allowing people "
+"behind \n"
+"most NATs and firewalls to receive unsolicited connections without any "
+"configuration. \n"
+"However, this does not limit the exposure of the peer's IP address to "
+"routers \n"
+"inside the network, as they can simply get introduced to the peer through"
+" \n"
+"the published introducer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:599
+msgid ""
+"Beyond the functional handling of restricted routes, there are two levels"
+" \n"
+"of restricted operation that can be used to limit the exposure of one's "
+"IP \n"
+"address - using router-specific tunnels for communication, and offering "
+"'client \n"
+"routers'. For the former, routers can either build a new pool of tunnels "
+"or \n"
+"reuse their exploratory pool, publishing the inbound gateways to some of "
+"them \n"
+"as part of their routerInfo in place of their transport addresses. When a"
+" \n"
+"peer wants to get in touch with them, they see those tunnel gateways in "
+"the \n"
+"netDb and simply send the relevant message to them through one of the "
+"published \n"
+"tunnels. If the peer behind the restricted route wants to reply, it may "
+"do \n"
+"so either directly (if they are willing to expose their IP to the peer) "
+"or \n"
+"indirectly through their outbound tunnels. When the routers that the peer"
+" \n"
+"has direct connections to want to reach it (to forward tunnel messages, "
+"for \n"
+"instance), they simply prioritize their direct connection over the "
+"published \n"
+"tunnel gateway. The concept of 'client routers' simply extends the "
+"restricted \n"
+"route by not publishing any router addresses. Such a router would not "
+"even \n"
+"need to publish their routerInfo in the netDb, merely providing their "
+"self \n"
+"signed routerInfo to the peers that it contacts (necessary to pass the "
+"router's \n"
+"public keys). Both levels of restricted route operation are planned for "
+"I2P \n"
+"2.0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:621
+msgid ""
+"There are tradeoffs for those behind restricted routes, as they would "
+"likely \n"
+"participate in other people's tunnels less frequently, and the routers "
+"which \n"
+"they are connected to would be able to infer traffic patterns that would "
+"not \n"
+"otherwise be exposed. On the other hand, if the cost of that exposure is "
+"less \n"
+"than the cost of an IP being made available, it may be worthwhile. This, "
+"of \n"
+"course, assumes that the peers that the router behind a restricted route "
+"contacts \n"
+"are not hostile - either the network is large enough that the probability"
+" \n"
+"of using a hostile peer to get connected is small enough, or trusted (and"
+" \n"
+"perhaps temporary) peers are used instead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:633
+msgid "Variable latency"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:634
+msgid ""
+"Even though the bulk of I2P's initial efforts have been on low latency "
+"communication, \n"
+"it was designed with variable latency services in mind from the "
+"beginning. \n"
+"At the most basic level, applications running on top of I2P can offer the"
+" \n"
+"anonymity of medium and high latency communication while still blending "
+"their \n"
+"traffic patterns in with low latency traffic. Internally though, I2P can "
+"offer \n"
+"its own medium and high latency communication through the garlic "
+"encryption \n"
+"- specifying that the message should be sent after a certain delay, at a "
+"certain \n"
+"time, after a certain number of messages have passed, or another mix "
+"strategy. \n"
+"With the layered encryption, only the router that the clove exposed the "
+"delay \n"
+"request would know that the message requires high latency, allowing the "
+"traffic \n"
+"to blend in further with the low latency traffic. Once the transmission "
+"precondition \n"
+"is met, the router holding on to the clove (which itself would likely be "
+"a \n"
+"garlic message) simply forwards it as requested - to a router, to a "
+"tunnel, \n"
+"or, most likely, to a remote client destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:651
+msgid ""
+"There are a substantial number of ways to exploit this capacity for high"
+" \n"
+"latency comm in I2P, but for the moment, doing so has been scheduled for "
+"the \n"
+"I2P 3.0 release. In the meantime, those requiring the anonymity that high"
+" \n"
+"latency comm can offer should look towards the application layer to "
+"provide \n"
+"it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:659
+msgid "Open questions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:661
+msgid "How to get rid of the timing constraint?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:662
+msgid "Can we deal with the sessionTags more efficiently?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:663
+msgid ""
+"What, if any, batching/mixing strategies should be made available on the "
+"tunnels?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:664
+msgid ""
+"What other tunnel peer selection and ordering strategies should be "
+"available?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:667
+msgid "Similar systems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:669
+msgid ""
+"I2P's architecture builds on the concepts of message oriented middleware,"
+" \n"
+"the topology of DHTs, the anonymity and cryptography of free route "
+"mixnets, \n"
+"and the adaptability of packet switched networking. The value comes not "
+"from \n"
+"novel concepts of algorithms though, but from careful engineering "
+"combining \n"
+"the research results of existing systems and papers. While there are a "
+"few \n"
+"similar efforts worth reviewing, both for technical and functional "
+"comparisons, \n"
+"two in particular are pulled out here - Tor and Freenet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:679
+#, python-format
+msgid "See also the Network Comparisons Page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:684
+#: i2p2www/pages/site/docs/how/tech-intro.html:749
+msgid "website"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:686
+msgid ""
+"At first glance, Tor and I2P have many functional and anonymity related \n"
+"similarities. While I2P's development began before we were aware of the "
+"early \n"
+"stage efforts on Tor, many of the lessons of the original onion routing "
+"and \n"
+"ZKS efforts were integrated into I2P's design. Rather than building an "
+"essentially \n"
+"trusted, centralized system with directory servers, I2P has a self "
+"organizing \n"
+"network database with each peer taking on the responsibility of profiling"
+" \n"
+"other routers to determine how best to exploit available resources. "
+"Another \n"
+"key difference is that while both I2P and Tor use layered and ordered "
+"paths \n"
+"(tunnels and circuits/streams), I2P is fundamentally a packet switched "
+"network, \n"
+"while Tor is fundamentally a circuit switched one, allowing I2P to "
+"transparently \n"
+"route around congestion or other network failures, operate redundant "
+"pathways, \n"
+"and load balance the data across available resources. While Tor offers "
+"the \n"
+"useful outproxy functionality by offering integrated outproxy discovery "
+"and \n"
+"selection, I2P leaves such application layer decisions up to applications"
+" \n"
+"running on top of I2P - in fact, I2P has even externalized the TCP-like "
+"streaming \n"
+"library itself to the application layer, allowing developers to "
+"experiment \n"
+"with different strategies, exploiting their domain specific knowledge to "
+"offer \n"
+"better performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:707
+msgid ""
+"From an anonymity perspective, there is much similarity when the core "
+"networks \n"
+"are compared. However, there are a few key differences. When dealing with"
+" \n"
+"an internal adversary or most external adversaries, I2P's simplex tunnels"
+" \n"
+"expose half as much traffic data than would be exposed with Tor's duplex "
+"circuits \n"
+"by simply looking at the flows themselves - an HTTP request and response "
+"would \n"
+"follow the same path in Tor, while in I2P the packets making up the "
+"request \n"
+"would go out through one or more outbound tunnels and the packets making "
+"up \n"
+"the response would come back through one or more different inbound "
+"tunnels. \n"
+"While I2P's peer selection and ordering strategies should sufficiently "
+"address \n"
+"predecessor attacks, should a switch to bidirectional tunnels be "
+"necessary,\n"
+"we could simply build an inbound and outbound tunnel along the same "
+"routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:721
+msgid ""
+"Another anonymity issue comes up in Tor's use of telescopic tunnel "
+"creation, \n"
+"as simple packet counting and timing measurements as the cells in a "
+"circuit \n"
+"pass through an adversary's node exposes statistical information "
+"regarding \n"
+"where the adversary is within the circuit. I2P's unidirectional tunnel "
+"creation \n"
+"with a single message so that this data is not exposed. Protecting the "
+"position \n"
+"in a tunnel is important, as an adversary would otherwise be able to "
+"mount \n"
+"a series of powerful predecessor, intersection, and traffic confirmation "
+"attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:731
+msgid ""
+"Tor's support for a second tier of \"onion proxies\" does offer a non-"
+"trivial \n"
+"degree of anonymity while requiring a low cost of entry, while I2P will "
+"not \n"
+"offer this topology until 2.0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:737
+msgid ""
+"On the whole, Tor and I2P complement each other in their focus - Tor "
+"works \n"
+"towards offering high speed anonymous Internet outproxying, while I2P "
+"works \n"
+"towards offering a decentralized resilient network in itself. In theory, "
+"both \n"
+"can be used to achieve both purposes, but given limited development "
+"resources, \n"
+"they both have their strengths and weaknesses. The I2P developers have "
+"considered \n"
+"the steps necessary to modify Tor to take advantage of I2P's design, but "
+"concerns \n"
+"of Tor's viability under resource scarcity suggest that I2P's packet "
+"switching \n"
+"architecture will be able to exploit scarce resources more effectively."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:751
+msgid ""
+"Freenet played a large part in the initial stages of I2P's design - "
+"giving \n"
+"proof to the viability of a vibrant pseudonymous community completely "
+"contained \n"
+"within the network, demonstrating that the dangers inherent in outproxies"
+" \n"
+"could be avoided. The first seed of I2P began as a replacement "
+"communication \n"
+"layer for Freenet, attempting to factor out the complexities of a "
+"scalable, \n"
+"anonymous and secure point to point communication from the complexities "
+"of \n"
+"a censorship resistant distributed data store. Over time however, some of"
+" \n"
+"the anonymity and scalability issues inherent in Freenet's algorithms "
+"made \n"
+"it clear that I2P's focus should stay strictly on providing a generic "
+"anonymous \n"
+"communication layer, rather than as a component of Freenet. Over the "
+"years, \n"
+"the Freenet developers have come to see the weaknesses in the older "
+"design, \n"
+"prompting them to suggest that they will require a \"premix\" layer to "
+"offer \n"
+"substantial anonymity. In other words, Freenet needs to run on top of a "
+"mixnet \n"
+"such as I2P or Tor, with \"client nodes\" requesting and publishing data "
+"through \n"
+"the mixnet to the \"server nodes\" which then fetch and store the data "
+"according \n"
+"to Freenet's heuristic distributed data storage algorithms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:770
+msgid ""
+"Freenet's functionality is very complementary to I2P's, as Freenet "
+"natively \n"
+"provides many of the tools for operating medium and high latency systems,"
+" \n"
+"while I2P natively provides the low latency mix network suitable for "
+"offering \n"
+"adequate anonymity. The logic of separating the mixnet from the "
+"censorship-\n"
+"resistant distributed data store still seems self-evident from an "
+"engineering, \n"
+"anonymity, security, and resource allocation perspective, so hopefully "
+"the \n"
+"Freenet team will pursue efforts in that direction, if not simply reusing"
+" \n"
+"(or helping to improve, as necessary) existing mixnets like I2P or Tor."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:781
+msgid ""
+"It is worth mentioning that there has recently been discussion and work \n"
+"by the Freenet developers on a \"globally scalable darknet\" using "
+"restricted \n"
+"routes between peers of various trust. While insufficient information has"
+" \n"
+"been made publicly available regarding how such a system would operate "
+"for \n"
+"a full review, from what has been said the anonymity and scalability "
+"claims \n"
+"seem highly dubious. In particular, the appropriateness for use in "
+"hostile \n"
+"regimes against state level adversaries has been tremendously overstated,"
+" \n"
+"and any analysis on the implications of resource scarcity upon the "
+"scalability \n"
+"of the network has seemingly been avoided. Further questions regarding "
+"susceptibility \n"
+"to traffic analysis, trust and other topics do exist, but a more in-depth"
+" \n"
+"review of this \"globally scalable darknet\" will have to wait until the "
+"Freenet \n"
+"team makes more information available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:797
+msgid ""
+"I2P itself doesn't really do much - it simply sends messages to remote "
+"destinations \n"
+"and receives messages targeting local destinations - most of the "
+"interesting \n"
+"work goes on at the layers above it. By itself, I2P could be seen as an "
+"anonymous \n"
+"and secure IP layer, and the bundled streaming"
+" library \n"
+"as an implementation of an anonymous and secure TCP layer on top of it. "
+"Beyond \n"
+"that, I2PTunnel exposes a generic TCP "
+"proxying \n"
+"system for either getting into or out of the I2P network, plus a variety "
+"of \n"
+"network applications provide further functionality for end users."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:808
+msgid "Streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:809
+msgid ""
+"The I2P streaming library can be viewed as a generic streaming interface "
+"(mirroring TCP sockets),\n"
+"and the implementation supports a sliding "
+"window protocol\n"
+"with several optimizations, to take into account the high delay over I2P."
+"\n"
+"Individual streams may adjust the maximum packet size and \n"
+"other options, though the default of 4KB compressed seems a reasonable "
+"tradeoff \n"
+"between the bandwidth costs of retransmitting lost messages and the "
+"latency \n"
+"of multiple messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:819
+msgid ""
+"In addition, in consideration of the relatively high cost of subsequent \n"
+"messages, the streaming library's protocol for scheduling and delivering "
+"messages \n"
+"has been optimized to allow individual messages passed to contain as much"
+" \n"
+"information as is available. For instance, a small HTTP transaction "
+"proxied \n"
+"through the streaming library can be completed in a single round trip - "
+"the \n"
+"first message bundles a SYN, FIN and the small payload (an HTTP request "
+"typically \n"
+"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many"
+" \n"
+"HTTP responses fit). While an additional ACK must be transmitted to tell "
+"the \n"
+"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy "
+"can \n"
+"deliver the full response to the browser immediately."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:832
+msgid ""
+"On the whole, however, the streaming library bears much resemblance to an"
+" \n"
+"abstraction of TCP, with its sliding windows, congestion control "
+"algorithms \n"
+"(both slow start and congestion avoidance), and general packet behavior "
+"(ACK, \n"
+"SYN, FIN, RST, etc)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:839
+msgid "Naming library and addressbook"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:840
+#, python-format
+msgid ""
+"For more information see the Naming and "
+"Addressbook page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:844
+#: i2p2www/pages/site/docs/how/tech-intro.html:918
+#: i2p2www/pages/site/docs/how/tech-intro.html:965
+#: i2p2www/pages/site/docs/how/tech-intro.html:997
+#: i2p2www/pages/site/docs/how/tech-intro.html:1005
+#: i2p2www/pages/site/docs/how/tech-intro.html:1013
+#: i2p2www/pages/site/docs/how/tech-intro.html:1023
+#: i2p2www/pages/site/docs/how/tech-intro.html:1031
+#: i2p2www/pages/site/docs/how/tech-intro.html:1053
+#, python-format
+msgid "Developed by: %(dev)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:846
+msgid ""
+"Naming within I2P has been an oft-debated topic since the very beginning"
+" \n"
+"with advocates across the spectrum of possibilities. However, given I2P's"
+" \n"
+"inherent demand for secure communication and decentralized operation, the"
+" \n"
+"traditional DNS-style naming system is clearly out, as are \"majority "
+"rules\" \n"
+"voting systems. Instead, I2P ships with a generic naming library and a "
+"base \n"
+"implementation designed to work off a local name to destination mapping, "
+"as \n"
+"well as an optional add-on application called the \"addressbook\". The "
+"addressbook \n"
+"is a web-of-trust-driven secure, distributed, and human readable naming "
+"system, \n"
+"sacrificing only the call for all human readable names to be globally "
+"unique \n"
+"by mandating only local uniqueness. While all messages in I2P are "
+"cryptographically \n"
+"addressed by their destination, different people can have local "
+"addressbook \n"
+"entries for \"Alice\" which refer to different destinations. People can "
+"still \n"
+"discover new names by importing published addressbooks of peers specified"
+" \n"
+"in their web of trust, by adding in the entries provided through a third "
+"party, \n"
+"or (if some people organize a series of published addressbooks using a "
+"first \n"
+"come first serve registration system) people can choose to treat these "
+"addressbooks \n"
+"as name servers, emulating traditional DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:866
+msgid ""
+"I2P does not promote the use of DNS-like services though, as the damage \n"
+"done by hijacking a site can be tremendous - and insecure destinations "
+"have \n"
+"no value. DNSsec itself still falls back on registrars and certificate "
+"authorities, \n"
+"while with I2P, requests sent to a destination cannot be intercepted or "
+"the \n"
+"reply spoofed, as they are encrypted to the destination's public keys, "
+"and \n"
+"a destination itself is just a pair of public keys and a certificate. "
+"DNS-style \n"
+"systems on the other hand allow any of the name servers on the lookup "
+"path \n"
+"to mount simple denial of service and spoofing attacks. Adding on a "
+"certificate \n"
+"authenticating the responses as signed by some centralized certificate "
+"authority \n"
+"would address many of the hostile nameserver issues but would leave open "
+"replay \n"
+"attacks as well as hostile certificate authority attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:880
+msgid ""
+"Voting style naming is dangerous as well, especially given the "
+"effectiveness \n"
+"of Sybil attacks in anonymous systems - the attacker can simply create an"
+" \n"
+"arbitrarily high number of peers and \"vote\" with each to take over a "
+"given \n"
+"name. Proof-of-work methods can be used to make identity non-free, but as"
+" \n"
+"the network grows the load required to contact everyone to conduct online"
+" \n"
+"voting is implausible, or if the full network is not queried, different "
+"sets \n"
+"of answers may be reachable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:890
+msgid ""
+"As with the Internet however, I2P is keeping the design and operation of"
+" \n"
+"a naming system out of the (IP-like) communication layer. The bundled "
+"naming \n"
+"library includes a simple service provider interface which alternate "
+"naming \n"
+"systems can plug into, allowing end users to drive what sort of naming "
+"tradeoffs \n"
+"they prefer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:899
+msgid ""
+"The old Syndie bundled with I2P has been replaced by the new Syndie which"
+"\n"
+"is distributed separately. For more information see the Syndie\n"
+"pages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:905
+msgid ""
+"Syndie is a safe, anonymous blogging / content publication / content "
+"aggregation \n"
+"system. It lets you create information, share it with others, and read "
+"posts \n"
+"from those you're interested in, all while taking into consideration your"
+" \n"
+"needs for security and anonymity. Rather than building its own content "
+"distribution \n"
+"network, Syndie is designed to run on top of existing networks, "
+"syndicating \n"
+"content through eepsites, Tor hidden services, Freenet freesites, normal "
+"websites, \n"
+"usenet newsgroups, email lists, RSS feeds, etc. Data published with "
+"Syndie \n"
+"is done so as to offer pseudonymous authentication to anyone reading or "
+"archiving \n"
+"it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:920
+msgid ""
+"I2PTunnel is probably I2P's most popular and versatile client "
+"application, \n"
+"allowing generic proxying both into and out of the I2P network. I2PTunnel"
+" \n"
+"can be viewed as four separate proxying applications - a \"client\" which"
+" receives \n"
+"inbound TCP connections and forwards them to a given I2P destination, an "
+"\"httpclient\" \n"
+"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the "
+"requests to \n"
+"the appropriate I2P destination (after querying the naming service if "
+"necessary), \n"
+"a \"server\" which receives inbound I2P streaming connections on a "
+"destination \n"
+"and forwards them to a given TCP host+port, and an \"httpserver\" which "
+"extends \n"
+"the \"server\" by parsing the HTTP request and responses to allow safer "
+"operation. \n"
+"There is an additional \"socksclient\" application, but its use is not "
+"encouraged \n"
+"for reasons previously mentioned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:934
+msgid ""
+"I2P itself is not an outproxy network - the anonymity and security "
+"concerns \n"
+"inherent in a mix net which forwards data into and out of the mix have "
+"kept \n"
+"I2P's design focused on providing an anonymous network which capable of "
+"meeting \n"
+"the user's needs without requiring external resources. However, the "
+"I2PTunnel \n"
+"\"httpclient\" application offers a hook for outproxying - if the "
+"hostname requested \n"
+"doesn't end in \".i2p\", it picks a random destination from a user-"
+"provided \n"
+"set of outproxies and forwards the request to them. These destinations "
+"are \n"
+"simply I2PTunnel \"server\" instances run by volunteers who have "
+"explicitly \n"
+"chosen to run outproxies - no one is an outproxy by default, and running "
+"an \n"
+"outproxy doesn't automatically tell other people to proxy through you. "
+"While \n"
+"outproxies do have inherent weaknesses, they offer a simple proof of "
+"concept \n"
+"for using I2P and provide some functionality under a threat model which "
+"may \n"
+"be sufficient for some users."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:950
+msgid ""
+"I2PTunnel enables most of the applications in use. An \"httpserver\" "
+"pointing \n"
+"at a webserver lets anyone run their own anonymous website (or "
+"\"eepsite\") \n"
+"- a webserver is bundled with I2P for this purpose, but any webserver can"
+" \n"
+"be used. Anyone may run a \"client\" pointing at one of the anonymously "
+"hosted \n"
+"IRC servers, each of which are running a \"server\" pointing at their "
+"local \n"
+"IRCd and communicating between IRCds over their own \"client\" tunnels. "
+"End \n"
+"users also have \"client\" tunnels pointing at I2Pmail's \n"
+"POP3 and SMTP destinations (which in turn are simply \"server\" instances"
+" pointing \n"
+"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at "
+"I2P's CVS \n"
+"server, allowing anonymous development. At times people have even run "
+"\"client\" \n"
+"proxies to access the \"server\" instances pointing at an NNTP server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:967
+msgid ""
+"i2p-bt is a port of the mainline python BitTorrent client to run both the"
+" \n"
+"tracker and peer communication over I2P. Tracker requests are forwarded "
+"through \n"
+"the eepproxy to eepsites specified in the torrent file while tracker "
+"responses \n"
+"refer to peers by their destination explicitly, allowing i2p-bt to open "
+"up \n"
+"a streaming lib connection to query them "
+"for \n"
+"blocks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:976
+msgid ""
+"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making"
+" \n"
+"a few modifications as necessary to strip any anonymity-compromising "
+"information \n"
+"from the application and to take into consideration the fact that IPs "
+"cannot \n"
+"be used for identifying peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:984
+msgid ""
+"I2PSnark developed: jrandom, et al, ported from mjw's Snark client"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:990
+msgid ""
+"Bundled with the I2P install, I2PSnark offers a simple anonymous "
+"BitTorrent \n"
+"client with multitorrent capabilities, exposing all of the functionality "
+"through \n"
+"a plain HTML web interface."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:999
+#, python-format
+msgid ""
+"Robert is a Bittorrent client written in Python.\n"
+"It is hosted on http://%(bob)s/Robert.html "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1007
+#, python-format
+msgid ""
+"PyBit is a Bittorrent client written in Python.\n"
+"It is hosted on %(pybit)s "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1015
+msgid ""
+"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to"
+" \n"
+"run entirely on top of I2P. While it has disabled some of Phex's "
+"functionality, \n"
+"such as integration with Gnutella webcaches, the basic file sharing and "
+"chatting \n"
+"system is fully functional."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1025
+msgid ""
+"iMule is a fairly direct port of the aMule filesharing client \n"
+"running entirely inside I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1033
+#, python-format
+msgid ""
+"I2Pmail is more a service than an application - postman offers both "
+"internal \n"
+"and external email with POP3 and SMTP service through I2PTunnel instances"
+" \n"
+"accessing a series of components developed with mastiejaner, allowing "
+"people \n"
+"to use their preferred mail clients to send and receive mail "
+"pseudonymously. \n"
+"However, as most mail clients expose substantial identifying information,"
+" \n"
+"I2P bundles susi23's web based susimail client which has been built "
+"specifically \n"
+"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers "
+"transparent \n"
+"virus filtering as well as denial of service prevention with hashcash "
+"augmented \n"
+"quotas. In addition, each user has control of their batching strategy "
+"prior \n"
+"to delivery through the mail.i2p outproxies, which are separate from the "
+"mail.i2p \n"
+"SMTP and POP3 servers - both the outproxies and inproxies communicate "
+"with \n"
+"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising "
+"those \n"
+"non-anonymous locations does not give access to the mail accounts or "
+"activity \n"
+"patterns of the user. At the moment the developers work on a "
+"decentralized \n"
+"mailsystem, called \"v2mail\". More information can be found on the "
+"eepsite \n"
+"%(postman)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1055
+msgid ""
+"I2P-Bote is a distributed e-mail application. It does not use the "
+"traditional\n"
+"e-mail concept of sending an e-mail to a server and retrieving it from a "
+"server.\n"
+"Instead, it uses a Kademlia Distributed Hash Table to store mails.\n"
+"One user can push a mail into the DHT, while another can request the "
+"e-mail from the DHT.\n"
+"And all the mails sent within the I2P-Bote network are automatically "
+"encrypted end-to-end. 
            \n"
+"Furthermore, I2P-Bote offers a remailer function on top of I2P, for "
+"increased high-latency anonymity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1065
+msgid ""
+"I2P-Messenger is an end-to-end encrypted serverless communication "
+"application.\n"
+"For communication between two users, they need to give each other their "
+"destination keys, to allow the other to connect.\n"
+"It supports file transfer and has a search for other users, based on "
+"Seedless."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:2
+msgid "I2P's Threat Model"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:3
+msgid "November 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:7
+msgid "low"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:8
+msgid "medium"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:9
+msgid "high"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:34
+msgid "Damage Potential"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:35
+msgid "Reliability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:36
+msgid "Exploitability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:37
+msgid "Affected Users"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:38
+msgid "Discoverability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:39
+msgid "Severity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:40
+#: i2p2www/pages/site/docs/protocol/i2np.html:94
+msgid "Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:45
+msgid "What do we mean by \"anonymous\"?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:47
+msgid ""
+"Your level of anonymity can be described as \"how hard it is for someone\n"
+"to find out information you don't want them to know?\" - who you are, "
+"where\n"
+"you are located, who you communicate with, or even when you communicate."
+"  \n"
+"\"Perfect\" anonymity is not a useful concept here - software will not "
+"make \n"
+"you indistinguishable from people that don't use computers or who are not"
+" on\n"
+"the Internet.  Instead, we are working to provide sufficient anonymity to"
+" meet the\n"
+"real needs of whomever we can - from those simply browsing websites, to "
+"those exchanging\n"
+"data, to those fearful of discovery by powerful organizations or states."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:58
+msgid ""
+"The question of whether I2P provides sufficient anonymity for your \n"
+"particular needs is a hard one, but this page will hopefully assist in \n"
+"answering that question by exploring how I2P operates under various "
+"attacks\n"
+"so that you may decide whether it meets your needs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:65
+msgid ""
+"We welcome further research and analysis on I2P's resistance to the "
+"threats described below.\n"
+"More review of existing literature (much of it focused on Tor) and "
+"original\n"
+"work focused on I2P is needed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:71
+msgid "Network Topology Summary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:72
+#, python-format
+msgid ""
+"I2P builds off the ideas of many other \n"
+"systems, but a few key points should be kept in"
+" mind when \n"
+"reviewing related literature:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:78
+msgid ""
+"I2P is a free route mixnet - the message creator explicitly "
+"defines the\n"
+"path that messages will be sent out (the outbound tunnel), and the "
+"message \n"
+"recipient explicitly defines the path that messages will be received on "
+"(the\n"
+"inbound tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:84
+msgid ""
+"I2P has no official entry and exit points - all peers fully "
+"participate in the \n"
+"mix, and there are no network layer in- or out-proxies (however, at the \n"
+"application layer, a few proxies do exist)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:89
+msgid ""
+"I2P is fully distributed - there are no central controls or "
+"authorities.\n"
+"One could modify some routers to operate mix cascades (building tunnels "
+"and giving\n"
+"out the keys necessary to control the forwarding at the tunnel endpoint) "
+"or directory \n"
+"based profiling and selection, all without breaking compatibility with "
+"the rest of \n"
+"the network, but doing so is of course not necessary (and may even harm "
+"one's\n"
+"anonymity)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:99
+#, python-format
+msgid ""
+"We have documented plans to implement nontrivial delays\n"
+"and batching strategies \n"
+"whose existence is only known to the particular hop or tunnel gateway "
+"that \n"
+"receives the message, allowing a mostly low latency mixnet to provide "
+"cover \n"
+"traffic for higher latency communication (e.g. email).\n"
+"However we are aware that significant delays are required to provide "
+"meaningful\n"
+"protection, and that implementation of such delays will be a significant "
+"challenge.\n"
+"It is not clear at this time whether we will actually implement these "
+"delay features."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:110
+msgid ""
+"In theory, routers along the message path may inject an \n"
+"arbitrary number of hops before forwarding the message to the next peer, "
+"though\n"
+"the current implementation does not."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:117
+msgid "The Threat Model"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:118
+msgid ""
+"I2P design started in 2003, not long after the advent of\n"
+"[Onion Routing],\n"
+"[Freenet], and\n"
+"[Tor].\n"
+"Our design benefits substantially from the research published around that"
+" time.\n"
+"I2P uses several onion routing techniques, so we continue to benefit\n"
+"from the significant academic interest in Tor."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:128
+msgid ""
+"Taking from the attacks and analysis put forth in the \n"
+"anonymity "
+"literature (largely \n"
+"Traffic Analysis: "
+"Protocols, Attacks, Design \n"
+"Issues and Open Problems), the following briefly describes a wide "
+"variety \n"
+"of attacks as well as many of I2Ps defenses.  We update\n"
+"this list to include new attacks as they are identified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:137
+msgid ""
+"Included are some attacks that may be unique to I2P.\n"
+"We do not have good answers for all these attacks, however\n"
+"we continue to do research and improve our defenses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:143
+msgid ""
+"In addition, many of these attacks are significantly easier than\n"
+"they should be, due to the modest size of the current network.\n"
+"While we are aware of some limitations that need to be addressed,\n"
+"I2P is designed to support hundreds of thousands, or millions, of\n"
+"participants.\n"
+"As we continue to spread the word and grow the network,\n"
+"these attacks will become much harder."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:153
+#, python-format
+msgid ""
+"The\n"
+"network comparisons and\n"
+"\"garlic\" terminology pages may also "
+"be helpful\n"
+"to review."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:182
+msgid "Index of Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:184
+#: i2p2www/pages/site/docs/how/threat-model.html:204
+msgid "Brute force attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:185
+#: i2p2www/pages/site/docs/how/threat-model.html:248
+msgid "Timing attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:186
+#: i2p2www/pages/site/docs/how/threat-model.html:285
+msgid "Intersection attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:187
+#: i2p2www/pages/site/docs/how/threat-model.html:365
+msgid "Denial of service attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:188
+#: i2p2www/pages/site/docs/how/threat-model.html:464
+msgid "Tagging attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:189
+#: i2p2www/pages/site/docs/how/threat-model.html:482
+msgid "Partitioning attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:190
+#: i2p2www/pages/site/docs/how/threat-model.html:522
+msgid "Predecessor attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:191
+#: i2p2www/pages/site/docs/how/threat-model.html:567
+msgid "Harvesting attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:192
+#: i2p2www/pages/site/docs/how/threat-model.html:614
+msgid "Identification Through Traffic Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:193
+#: i2p2www/pages/site/docs/how/threat-model.html:674
+msgid "Sybil attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:194
+#: i2p2www/pages/site/docs/how/threat-model.html:723
+msgid "Buddy Exhaustion attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:195
+#: i2p2www/pages/site/docs/how/threat-model.html:748
+msgid "Cryptographic attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:196
+msgid "Floodfill attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:197
+#: i2p2www/pages/site/docs/how/threat-model.html:809
+msgid "Other Network Database attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:198
+msgid "Attacks on centralized resources"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:199
+#: i2p2www/pages/site/docs/how/threat-model.html:875
+msgid "Development attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:200
+msgid "Implementation attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:201
+#: i2p2www/pages/site/docs/how/threat-model.html:959
+msgid "Other Defenses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:208
+msgid ""
+"A brute force attack can be mounted by a global passive or active "
+"adversary, \n"
+"watching all the messages pass between all of the nodes and attempting to"
+" correlate\n"
+"which message follows which path.  Mounting this attack against I2P "
+"should be \n"
+"nontrivial, as all peers in the network are frequently sending messages "
+"(both\n"
+"end to end and network maintenance messages), plus an end to end message "
+"changes\n"
+"size and data along its path.  In addition, the external adversary does "
+"not have\n"
+"access to the messages either, as inter-router communication is both "
+"encrypted\n"
+"and streamed (making two 1024 byte messages indistinguishable from one "
+"2048 byte\n"
+"message)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:220
+msgid ""
+"However, a powerful attacker can use brute force to detect trends - if "
+"they \n"
+"can send 5GB to an I2P destination and monitor everyone's network "
+"connection,\n"
+"they can eliminate all peers who did not receive 5GB of data.  Techniques"
+" to \n"
+"defeat this attack exist, but may be prohibitively expensive (see: \n"
+"Tarzan's "
+"mimics\n"
+"or constant rate traffic).  Most users are not concerned with this "
+"attack, as \n"
+"the cost of mounting it are extreme (and often require illegal activity)."
+"  \n"
+"However, the attack is still possible, for example by an observer at\n"
+"a large ISP or an Internet exchange point.\n"
+"Those who want to defend against it \n"
+"would want to take appropriate countermeasures, such as\n"
+"setting low bandwidth limits, and using unpublished or encrypted "
+"leasesets for eepsites.\n"
+"Other countermeasures, such as nontrivial delays and restricted routes, "
+"are\n"
+"not currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:237
+#, python-format
+msgid ""
+"As a partial defense against a single router or group of routers trying "
+"to route all the network's traffic,\n"
+"routers contain limits as to how many tunnels can be routed through a "
+"single peer.\n"
+"As the network grows, these limits are subject to further adjustment.\n"
+"Other mechanisms for peer rating, selection and avoidance\n"
+"are discussed on the\n"
+"peer selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:252
+msgid ""
+"I2P's messages are unidirectional and do not necessarily imply that a "
+"reply\n"
+"will be sent.  However, applications on top of I2P will most likely have\n"
+"recognizable patterns within the frequency of their messages - for "
+"instance, an \n"
+"HTTP request will be a small message with a large sequence of reply "
+"messages \n"
+"containing the HTTP response.  Using this data as well as a broad view of"
+" the \n"
+"network topology, an attacker may be able to disqualify some links as "
+"being too \n"
+"slow to have passed the message along."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:262
+msgid ""
+"This sort of attack is powerful, but its applicability to I2P is non "
+"obvious,\n"
+"as the variation on message delays due to queuing, message processing, "
+"and \n"
+"throttling will often meet or exceed the time of passing a message along "
+"a \n"
+"single link - even when the attacker knows that a reply will be sent as "
+"soon as\n"
+"the message is received.  There are some scenarios which will expose "
+"fairly \n"
+"automatic replies though - the streaming library does (with the SYN+ACK) "
+"as does the \n"
+"message mode of guaranteed delivery (with the "
+"DataMessage+DeliveryStatusMessage)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:272
+#, python-format
+msgid ""
+"Without protocol scrubbing or higher latency, global active adversaries "
+"can \n"
+"gain substantial information.  As such, people concerned with these "
+"attacks could\n"
+"increase the latency (using nontrivial "
+"delays or \n"
+"batching strategies), include protocol "
+"scrubbing, or\n"
+"other advanced tunnel routing techniques,\n"
+"but these are unimplemented in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:281
+#, python-format
+msgid ""
+"References: Low-Resource Routing Attacks Against "
+"Anonymous Systems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:289
+msgid ""
+"Intersection attacks against low latency systems are extremely powerful -"
+"\n"
+"periodically make contact with the target and keep track of what peers "
+"are on\n"
+"the network.  Over time, as node churn occurs the attacker will gain \n"
+"significant information about the target by simply intersecting the sets "
+"of\n"
+"peers that are online when a message successfully goes through.  The cost"
+" of \n"
+"this attack is significant as the network grows, but may be feasible in "
+"some\n"
+"scenarios."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:299
+#, python-format
+msgid ""
+"In summary, if an attacker is at both ends of your tunnel at the same "
+"time,\n"
+"he may be successful.\n"
+"I2P does not have a full defense to this for low latency communication.\n"
+"This is an inherent weakness of low-latency onion routing.\n"
+"Tor provides a similar disclaimer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:307
+msgid "Partial defenses implemented in I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:311
+#, python-format
+msgid "strict ordering of peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:314
+#, python-format
+msgid ""
+"peer profiling and selection from a "
+"small group that changes slowly"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:317
+msgid "Limits on the number of tunnels routed through a single peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:320
+msgid ""
+"Prevention of peers from the same /16 IP range from being members of a "
+"single tunnel"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:323
+msgid ""
+"For eepsites or other hosted services, we support\n"
+"simultaneous hosting on multiple routers, or\n"
+"multihoming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:330
+msgid ""
+"Even in total, these defenses are not a complete solution.\n"
+"Also, we have made some design choices that may significantly increase "
+"our vulnerability:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:335
+msgid "We do not use low-bandwidth \"guard nodes\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:338
+msgid ""
+"We use tunnel pools comprised of several tunnels, and traffic can shift "
+"from tunnel to tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:341
+msgid "Tunnels are not long-lived; new tunnels are built every 10 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:344
+msgid ""
+"Tunnel lengths are configurable.\n"
+"While 3-hop tunnels are recommended for full protection, several "
+"applications and\n"
+"services use 2-hop tunnels by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:351
+#, python-format
+msgid ""
+"In the future, it could\n"
+"for peers who can afford significant delays (per nontrivial\n"
+"delays and batching strategies).  "
+"In addition,\n"
+"this is only relevant for destinations that other people know about - a "
+"private\n"
+"group whose destination is only known to trusted peers does not have to "
+"worry,\n"
+"as an adversary can't \"ping\" them to mount the attack.
            "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:360
+#, python-format
+msgid "Reference: One Cell Enough"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:367
+msgid ""
+"There are a whole slew of denial of service attacks available against "
+"I2P,\n"
+"each with different costs and consequences:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:373
+msgid ""
+"Greedy user attack: This is simply\n"
+"people trying to consume significantly more resources than they are \n"
+"willing to contribute. The defense against this is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:379
+#, python-format
+msgid ""
+"Set defaults so that most users provide resources to the network.\n"
+"In I2P, users route traffic by default. In sharp distinction to\n"
+"other networks,\n"
+"over 95% of I2P users relay traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:385
+msgid ""
+"Provide easy configuration options so that users may increase their\n"
+"contribution (share percentage) to the network. Display easy-to-"
+"understand\n"
+"metrics such as \"share ratio\" so that users may see what they are "
+"contributing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:390
+msgid ""
+"Maintain a strong community with blogs, forums, IRC, and other means of "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:397
+#, python-format
+msgid ""
+"Starvation attack: A hostile user may attempt to harm the network "
+"by\n"
+"creating a significant number of peers in the network who are not "
+"identified as\n"
+"being under control of the same entity (as with Sybil). These nodes then"
+" \n"
+"decide not to provide any resources to the network, causing existing "
+"peers \n"
+"to search through a larger network database or request more tunnels than"
+" \n"
+"should be necessary. \n"
+"Alternatively, the nodes may provide intermittent service by periodically"
+"\n"
+"dropping selected traffic, or refusing connections to certain peers.\n"
+"This behavior may be indistinguishable from that of a heavily-loaded or "
+"failing node.\n"
+"I2P addresses these issues by maintaining profiles on the \n"
+"peers, attempting to identify underperforming ones and simply ignoring \n"
+"them, or using them rarely.\n"
+"We have significantly enhanced the\n"
+"ability to recognize and avoid troublesome peers; however there are still"
+"\n"
+"significant efforts required in this area."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:417
+#, python-format
+msgid ""
+"Flooding attack: A hostile user may attempt to flood the network,\n"
+"a peer, a destination, or a tunnel.  Network and peer flooding is "
+"possible,\n"
+"and I2P does nothing to prevent standard IP layer flooding.  The flooding"
+" of\n"
+"a destination with messages by sending a large number to the target's "
+"various\n"
+"inbound tunnel gateways is possible, but the destination will know this "
+"both\n"
+"by the contents of the message and because the tunnel's tests will fail."
+"  The\n"
+"same goes for flooding just a single tunnel.  I2P has no defenses for a "
+"network\n"
+"flooding attack.  For a destination and tunnel flooding attack, the "
+"target\n"
+"identifies which tunnels are unresponsive and builds new ones.  New code "
+"could\n"
+"also be written to add even more tunnels if the client wishes to handle "
+"the\n"
+"larger load.  If, on the other hand, the load is more than the client can"
+"\n"
+"deal with, they can instruct the tunnels to throttle the number of "
+"messages or\n"
+"bytes they should pass on (once the advanced tunnel\n"
+"operation is implemented)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:436
+msgid ""
+"CPU load attack: There are currently some methods for people to \n"
+"remotely request that a peer perform some cryptographically expensive \n"
+"operation, and a hostile attacker could use these to flood that peer with"
+"\n"
+"a large number of them in an attempt to overload the CPU.  Both using "
+"good \n"
+"engineering practices and potentially requiring nontrivial certificates \n"
+"(e.g. HashCash) to be attached to these expensive requests should "
+"mitigate\n"
+"the issue, though there may be room for an attacker to exploit various\n"
+"bugs in the implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:449
+#, python-format
+msgid ""
+"Floodfill DOS attack: A hostile user may attempt to harm the "
+"network by\n"
+"becoming a floodfill router. The current defenses against unreliable,\n"
+"intermittent, or malicious floodfill routers are poor.\n"
+"A floodfill router may provide bad or no response to lookups, and\n"
+"it may also interfere with inter-floodfill communication.\n"
+"Some defenses and\n"
+"peer profiling are implemented,\n"
+"however there is much more to do.\n"
+"For more information see the\n"
+"network database page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:468
+#, python-format
+msgid ""
+"Tagging attacks - modifying a message so that it can later be identified"
+" \n"
+"further along the path - are by themselves impossible in I2P, as messages"
+" \n"
+"passed through tunnels are signed.  However, if an attacker is the "
+"inbound \n"
+"tunnel gateway as well as a participant further along in that tunnel, "
+"with\n"
+"collusion they can identify the fact that they are in the same tunnel "
+"(and \n"
+"prior to adding unique hop ids and "
+"other updates,\n"
+"colluding peers within the same tunnel can recognize that fact without "
+"any \n"
+"effort).  An attacker in an outbound tunnel and any part of an inbound "
+"tunnel cannot \n"
+"collude however, as the tunnel encryption pads and modifies the data "
+"separately\n"
+"for the inbound and outbound tunnels.  External attackers cannot do "
+"anything,\n"
+"as the links are encrypted and messages signed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:486
+msgid ""
+"Partitioning attacks - finding ways to segregate (technically or "
+"analytically)\n"
+"the peers in a network - are important to keep in mind when dealing with "
+"a \n"
+"powerful adversary, since the size of the network plays a key role in "
+"determining\n"
+"your anonymity.  Technical partitioning by cutting links between peers to"
+" create\n"
+"fragmented networks is addressed by I2P's built in network database, "
+"which \n"
+"maintains statistics about various peers so as to allow any existing "
+"connections\n"
+"to other fragmented sections to be exploited so as to heal the network.  "
+"However,\n"
+"if the attacker does disconnect all links to uncontrolled peers, "
+"essentially\n"
+"isolating the target, no amount of network database healing will fix it."
+"  At\n"
+"that point, the only thing the router can hope to do is notice that a "
+"significant\n"
+"number of previously reliable peers have become unavailable and alert the"
+" client\n"
+"that it is temporarily disconnected (this detection code is not "
+"implemented at\n"
+"the moment)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:502
+#, python-format
+msgid ""
+"Partitioning the network analytically by looking for differences in how "
+"routers \n"
+"and destinations behave and grouping them accordingly is also a very "
+"powerful\n"
+"attack.  For instance, an attacker harvesting"
+" the network\n"
+"database will know when a particular destination has 5 inbound tunnels in"
+" their\n"
+"LeaseSet while others have only 2 or 3, allowing the adversary to "
+"potentially \n"
+"partition clients by the number of tunnels selected.  Another partition "
+"is \n"
+"possible when dealing with the nontrivial "
+"delays and \n"
+"batching strategies, as the tunnel "
+"gateways and the\n"
+"particular hops with non-zero delays will likely stand out.  However, "
+"this data\n"
+"is only exposed to those specific hops, so to partition effectively on "
+"that \n"
+"matter, the attacker would need to control a significant portion of the "
+"network\n"
+"(and still that would only be a probabilistic partition, as they wouldn't"
+" know\n"
+"which other tunnels or messages have those delays)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:518
+#, python-format
+msgid ""
+"Also discussed on the network database "
+"page (bootstrap attack)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:526
+msgid ""
+"The predecessor attack is passively gathering statistics in an attempt to"
+" see\n"
+"what peers are 'close' to the destination by participating in their "
+"tunnels and\n"
+"keeping track of the previous or next hop (for outbound or inbound "
+"tunnels, \n"
+"respectively).  Over time, using a perfectly random sample of peers and "
+"random\n"
+"ordering, an attacker would be able to see which peer shows up as "
+"'closer' \n"
+"statistically more than the rest, and that peer would in turn be where "
+"the\n"
+"target is located."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:536
+#, python-format
+msgid ""
+"I2P avoids this in four ways: first, the peers selected to participate in"
+"\n"
+"tunnels are not randomly sampled throughout the network - they are "
+"derived from\n"
+"the peer selection algorithm which "
+"breaks them\n"
+"into tiers.  Second, with strict "
+"ordering of peers\n"
+"in a tunnel, the fact that a peer shows up more frequently does not mean "
+"they're\n"
+"the source.  Third, with permuted "
+"tunnel length\n"
+"(not enabled by default)\n"
+"even 0 hop tunnels can provide plausible deniability as the occasional \n"
+"variation of the gateway will look like normal tunnels.  Fourth, with \n"
+"restricted routes "
+"(unimplemented), only the peer with\n"
+"a restricted connection to the target will ever contact the target, while"
+" \n"
+"attackers will merely run into that gateway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:553
+#, python-format
+msgid ""
+"The current tunnel build method\n"
+"was specifically designed to combat the predecessor attack.\n"
+"See also the intersection attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:559
+#, python-format
+msgid ""
+"References: %(pdf2008)s\n"
+"which is an update to the 2004 predecessor attack paper\n"
+"%(pdf2004)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:571
+msgid ""
+"\"Harvesting\" means compiling a list of users running I2P.\n"
+"It can be used for legal attacks and to help\n"
+"other attacks by simply running a peer, seeing who it connects to, and \n"
+"harvesting whatever references to other peers it can find."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:578
+msgid ""
+"I2P itself is not designed with effective defenses against\n"
+"this attack, since there is the distributed network database \n"
+"containing just this information.\n"
+"The following factors make the attack somewhat harder in practice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:585
+msgid ""
+"Network growth will make it more difficult to obtain a given proportion "
+"of the network"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:588
+msgid "Floodfill routers implement query limits as DOS protection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:591
+msgid ""
+"\"Hidden mode\", which prevents a router from publishing its information "
+"to the netDb,\n"
+"(but also prevents it from relaying data) is not widely used now but "
+"could be."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:597
+#, python-format
+msgid ""
+"In future implementations,\n"
+"basic and \n"
+"comprehensive restricted "
+"routes,\n"
+"this attack loses much of its power, as the \"hidden\" peers do not "
+"publish their\n"
+"contact addresses in the network database - only the tunnels through "
+"which \n"
+"they can be reached (as well as their public keys, etc)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:606
+msgid ""
+"In the future, routers could use GeoIP to identify if they are in a "
+"particular\n"
+"country where identification as an I2P node would be risky.\n"
+"In that case, the router could automatically enable hidden mode, or\n"
+"enact other restricted route methods."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:618
+#, python-format
+msgid ""
+"By inspecting the traffic into and out of a router, a malicious ISP\n"
+"or state-level firewall could identify that a computer is running I2P.\n"
+"As discussed above, I2P is not specifically "
+"designed\n"
+"to hide that a computer is running I2P. However, several design decisions"
+" made\n"
+"in the design of the\n"
+"transport layer and protocols\n"
+"make it somewhat difficult to identify I2P traffic:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:628
+msgid "Random port selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:631
+msgid "Point-to-Point Encryption of all traffic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:634
+msgid ""
+"DH key exchange with no protocol bytes or other unencrypted constant "
+"fields"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:637
+#, python-format
+msgid ""
+"Simultaneous use of both\n"
+"TCP and\n"
+"UDP transports.\n"
+"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to"
+" track."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:645
+msgid ""
+"In the near future, we plan to directly address traffic analysis issues "
+"by further obfuscation of I2P transport protocols, possibly including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:649
+msgid ""
+"Padding at the transport layer to random lengths, especially during the "
+"connection handshake"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:652
+msgid ""
+"Study of packet size distribution signatures, and additional padding as "
+"necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:655
+msgid ""
+"Development of additional transport methods that mimic SSL or other "
+"common protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:658
+msgid ""
+"Review of padding strategies at higher layers to see how they affect "
+"packet sizes at the transport layer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:661
+msgid ""
+"Review of methods implemented by various state-level firewalls to block "
+"Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:664
+msgid "Working directly with DPI and obfuscation experts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:669
+#, python-format
+msgid ""
+"Reference: Breaking and Improving Protocol "
+"Obfuscation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:678
+msgid ""
+"Sybil describes a category of attacks where the adversary creates "
+"arbitrarily\n"
+"large numbers of colluding nodes and uses the increased numbers to help \n"
+"mounting other attacks.  For instance, if an attacker is in a network "
+"where peers\n"
+"are selected randomly and they want an 80% chance to be one of those "
+"peers, they\n"
+"simply create five times the number of nodes that are in the network and "
+"roll \n"
+"the dice.  When identity is free, Sybil can be a very potent technique "
+"for a \n"
+"powerful adversary.  The primary technique to address this is simply to "
+"make \n"
+"identity 'non free' - Tarzan\n"
+"(among others) uses the fact that IP addresses are limited, while \n"
+"IIP used \n"
+"HashCash to 'charge' for "
+"creating a new\n"
+"identity.  We currently have not implemented any particular technique to "
+"address\n"
+"Sybil, but do include placeholder certificates in the router's and \n"
+"destination's data structures which can contain a HashCash certificate of"
+" \n"
+"appropriate value when necessary (or some other certificate proving "
+"scarcity)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:696
+msgid "Requiring HashCash Certificates in various places has two major problems:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:700
+msgid "Maintaining backward compatibility"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:703
+msgid ""
+"The classic HashCash problem -\n"
+"selecting HashCash values that are meaningful proofs of work on high-end "
+"machines,\n"
+"while still being feasible on low-end machines such as mobile devices."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:710
+msgid ""
+"Various limitations on the number of routers in a given IP range restrict"
+"\n"
+"the vulnerability to attackers that don't have the ability to put "
+"machines\n"
+"in several IP blocks.\n"
+"However, this is not a meaningful defense against a powerful adversary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:717
+#, python-format
+msgid ""
+"See the network database page\n"
+"for more Sybil discussion."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:727
+#, python-format
+msgid ""
+"(Reference: In Search of an Anonymouns and Secure "
+"Lookup Section 5.2)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:731
+#, python-format
+msgid ""
+"By refusing to accept or forward tunnel build requests, except to a "
+"colluding peer, a router could ensure\n"
+"that a tunnel is formed wholly from its set of colluding routers.\n"
+"The chances of success are enhanced if there is a large number of "
+"colluding routers,\n"
+"i.e. a Sybil attack.\n"
+"This is somewhat mitigated by our\n"
+"peer profiling methods used to monitor "
+"the performance\n"
+"of peers.\n"
+"However, this is a powerful attack as the number of routers approaches\n"
+"f = 0.2, or 20% malicious nodes, as specifed in the paper.\n"
+"The malicous routers could also maintain connections to the target router"
+" and provide\n"
+"excellent forwarding bandwidth for traffic over those connections, in an "
+"attempt\n"
+"to manipulate the profiles managed by the target and appear attractive.\n"
+"Further research and defenses may be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:752
+#, python-format
+msgid ""
+"We use strong cryptography with long keys, and\n"
+"we assume the security of the industry-standard cryptographic primitives "
+"used in I2P, as documented\n"
+"on the low-level cryptography page. \n"
+"Security features include the immediate detection of \n"
+"altered messages along the path, the inability to decrypt messages not "
+"addressed to you,\n"
+"and defense against man-in-the-middle attacks.\n"
+"The key sizes chosen in 2003 were quite conservative at the time, and are"
+" still longer than\n"
+"those used in other anonymity "
+"networks.\n"
+"We don't think the current key lengths are our biggest weakness,\n"
+"especially for traditional, non-state-level adversaries;\n"
+"bugs and the small size of the network are much more worrisome.\n"
+"Of course, all cryptographic algorithms eventually become obsolete due to"
+"\n"
+"the advent of faster processors, cryptographic research, and advancements"
+" in\n"
+"methods such as rainbow tables, clusters of video game hardware, etc.\n"
+"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys"
+" or change\n"
+"shared secret values while maintaining backward compatibility."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:771
+#, python-format
+msgid ""
+"Upgrading the various data structures and protocols to support longer "
+"keys\n"
+"will have to be tackled eventually, and this will be a\n"
+"major undertaking, just as it will be "
+"for \n"
+"others.\n"
+"Hopefully, through careful planning, we can minimize the disruption, and\n"
+"implement mechanisms to make it easier for future transitions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:780
+msgid ""
+"In the future, several I2P protocols and data structures\n"
+"support securely padding messages to arbitrary sizes, so messages could "
+"be made constant\n"
+"size or garlic messages could be modified randomly so that some cloves "
+"appear to contain\n"
+"more subcloves than they actually do.  At the moment, however, garlic, "
+"tunnel, and \n"
+"end to end messages include simple random padding."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:790
+msgid "Floodfill Anonymity attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:794
+#, python-format
+msgid ""
+"In addition to the floodfill DOS attacks described\n"
+"above, floodfill routers are uniquely positioned\n"
+"to learn about network participants, due to their role\n"
+"in the netDb, and the high frequency of communication with those "
+"participants.\n"
+"This is somewhat mitigated because floodfill routers only manage a "
+"portion\n"
+"of the total keyspace, and the keyspace rotates daily, as explained \n"
+"on the network database page.\n"
+"The specific mechanisms by which routers communicate with floodfills have"
+" been\n"
+"carefully designed.\n"
+"However, these threats should be studied further.\n"
+"The specific potential threats and corresponding defenses are a topic for"
+" future research."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:810
+#, python-format
+msgid ""
+"A hostile user may attempt to harm the network by\n"
+"creating one or more floodfill routers and crafting them to offer\n"
+"bad, slow, or no responses.\n"
+"Several scenarios are discussed on the\n"
+"network database page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:820
+msgid "Central Resource Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:824
+msgid ""
+"There are a few centralized or limited resources (some inside I2P, some "
+"not)\n"
+"that could be attacked or used as a vector for attacks.\n"
+"The absence of jrandom starting November 2007, followed by the loss of "
+"the i2p.net hosting service in January 2008,\n"
+"highlighted numerous centralized resources in the development and "
+"operation of the I2P network,\n"
+"most of which are now distributed.\n"
+"Attacks on externally-reachable resources mainly affect the ability of "
+"new users to find us,\n"
+"not the operation of the network itself."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:834
+#, python-format
+msgid ""
+"The website is mirrored and uses DNS round-robin"
+" for external public access."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:837
+#, python-format
+msgid ""
+"Routers now support multiple external reseed "
+"locations,\n"
+"however more reseed hosts may be needed, and the handling of unreliable "
+"or malicious\n"
+"reseed hosts may need improvement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:842
+msgid ""
+"Routers now support multiple update file locations.\n"
+"A malicious update host could feed a huge file, need to limit the size."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:846
+msgid "Routers now support multiple default trusted update signers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:849
+msgid ""
+"Routers now better handle multiple unreliable "
+"floodfill peers.\n"
+"Malicious floodfills needs more study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:853
+#, python-format
+msgid ""
+"The code is now stored in a distributed source "
+"control system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:856
+msgid ""
+"Routers rely on a single news host, but there is a hardcoded backup URL "
+"pointing to a different host.\n"
+"A malicious news host could feed a huge file, need to limit the size."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:860
+#, python-format
+msgid ""
+"Naming system services, including addressbook "
+"subscription providers, add-host services,\n"
+"and jump services, could be malicious. Substantial protections for "
+"subscriptions were implemented\n"
+"in release 0.6.1.31, with additional enhancements in subsequent releases."
+"\n"
+"However, all naming services require some measure of trust, see\n"
+"the naming page for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:867
+msgid ""
+"We remain reliant on the DNS service for i2p2.de, losing this would cause"
+" substantial\n"
+"disruption in our ability to attract new users,\n"
+"and would shrink the network (in the short-to-medium term), just as the "
+"loss of i2p.net did."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:879
+msgid ""
+"These attacks aren't directly on the network, but instead go after its "
+"development team \n"
+"by either introducing legal hurdles on anyone contributing to the "
+"development\n"
+"of the software, or by using whatever means are available to get the "
+"developers to \n"
+"subvert the software.  Traditional technical measures cannot defeat these"
+" attacks, and\n"
+"if someone threatened the life or livelihood of a developer (or even just"
+" issuing a \n"
+"court order along with a gag order, under threat of prison), we would "
+"have a big problem."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:888
+msgid "However, two techniques help defend against these attacks:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:892
+#, python-format
+msgid ""
+"All components of the network must be open source to enable inspection, "
+"verification, \n"
+"modification, and improvement.  If a developer is compromised, once it is"
+" noticed \n"
+"the community should demand explanation and cease to accept that "
+"developer's work.\n"
+"All checkins to our distributed source control "
+"system\n"
+"are cryptographically signed, and the release packagers use a trust-list "
+"system\n"
+"to restrict modifications to those previously approved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:900
+#, python-format
+msgid ""
+"Development over the network itself, allowing developers to stay "
+"anonymous but still \n"
+"secure the development process.  All I2P development can occur through "
+"I2P - using\n"
+"a distributed source control system,\n"
+"a distributed source control system, IRC chat,\n"
+"public web servers,\n"
+"discussion forums (forum.i2p), and the software distribution sites,\n"
+"all available within I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:911
+msgid ""
+"We also maintain relationships with various organizations that offer "
+"legal advice,\n"
+"should any defense be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:916
+msgid "Implementation attacks (bugs)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:920
+msgid ""
+"Try as we might, most nontrivial applications include errors in the "
+"design or \n"
+"implementation, and I2P is no exception.  There may be bugs that could be"
+" exploited to \n"
+"attack the anonymity or security of the communication running over I2P in"
+" unexpected \n"
+"ways.  To help withstand attacks against the design or protocols in use, "
+"we publish \n"
+"all designs and documentation and solicit review and criticism with \n"
+"the hope that many eyes will improve the system.\n"
+"We do not believe in\n"
+"security through "
+"obscurity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:931
+msgid ""
+"In addition, the code is being \n"
+"treated the same way, with little aversion towards reworking or throwing "
+"out \n"
+"something that isn't meeting the needs of the software system (including "
+"ease of \n"
+"modification).  Documentation for the design and implementation of the "
+"network and \n"
+"the software components are an essential part of security, as without "
+"them it is \n"
+"unlikely that developers would be willing to spend the time to learn the "
+"software \n"
+"enough to identify shortcomings and bugs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:941
+msgid ""
+"Our software is likely, in particular, to contain bugs related to denial "
+"of service\n"
+"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues  "
+"in the router console,\n"
+"and other vulnerabilities to non-standard inputs via the various "
+"protocols."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:947
+#, python-format
+msgid ""
+"I2P is still a small network with a small development community and "
+"almost no\n"
+"interest from academic or research groups.\n"
+"Therefore we lack the analysis that\n"
+"other anonymity networks\n"
+"may have received. We continue to recruit people to\n"
+"get involved and help."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:960
+msgid "Blocklists"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:961
+msgid ""
+"To some extent, I2P could be enhanced to avoid peers operating at IP "
+"addresses\n"
+"listed in a blocklist. Several blocklists are commonly available in "
+"standard formats,\n"
+"listing anti-P2P organizations, potential state-level adversaries, and "
+"others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:967
+msgid ""
+"To the extent that active peers actually do show up in the actual "
+"blocklist,\n"
+"blocking by only a subset of peers would tend to segment the network,\n"
+"exacerbate reachability problems, and decrease overall reliability.\n"
+"Therefore we would want to agree on a particular blocklist and\n"
+"enable it by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:975
+msgid ""
+"Blocklists are only a part (perhaps a small part) of an array of defenses"
+"\n"
+"against maliciousness.\n"
+"In large part the profiling system does a good job of measuring\n"
+"router behavior so that we don't need to trust anything in netDb.\n"
+"However there is more that can be done. For each of the areas in the\n"
+"list above there are improvements we can make in detecting badness."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:984
+msgid ""
+"If a blocklist is hosted at a central location with automatic updates\n"
+"the network is vulnerable to a\n"
+"central resource attack.\n"
+"Automatic subscription to a list gives the list provider the power to "
+"shut\n"
+"the i2p network down. Completely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:992
+msgid ""
+"Currently, a default blocklist is distributed with our software,\n"
+"listing only the IPs of past DOS sources.\n"
+"There is no automatic update mechanism.\n"
+"Should a particular IP range implement serious attacks on the I2P "
+"network,\n"
+"we would have to ask people to update their blocklist manually through\n"
+"out-of-band mechanisms such as forums, blogs, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:2
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:6
+msgid "Tunnel Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:3
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:3
+msgid "July 2011"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:7
+msgid ""
+"This page contains an overview of I2P tunnel terminology and operation, "
+"with\n"
+"links to more technical pages, details, and specifications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:12
+#, python-format
+msgid ""
+"As briefly explained in the introduction, I2P "
+"builds virtual \"tunnels\" -\n"
+"temporary and unidirectional paths through a sequence of routers.  These"
+" \n"
+"tunnels are classified as either inbound tunnels (where everything \n"
+"given to it goes towards the creator of the tunnel) or outbound tunnels\n"
+"(where the tunnel creator shoves messages away from them).  When Alice\n"
+"wants to send a message to Bob, she will (typically) send it out one of\n"
+"her existing outbound tunnels with instructions for that tunnel's "
+"endpoint\n"
+"to forward it to the gateway router for one of Bob's current inbound \n"
+"tunnels, which in turn passes it to Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:25
+msgid "Alice connecting through her outbound tunnel to Bob via his inbound tunnel"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:27
+msgid "Outbound Gateway"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:28
+msgid "Outbound Participant"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:29
+#: i2p2www/pages/site/docs/tunnels/implementation.html:131
+msgid "Outbound Endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
+#: i2p2www/pages/site/docs/tunnels/implementation.html:140
+msgid "Inbound Gateway"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:31
+msgid "Inbound Participant"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:32
+msgid "Inbound Endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:36
+msgid "Tunnel vocabulary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:38
+#, python-format
+msgid ""
+"Tunnel gateway - the first router in a tunnel.  For inbound "
+"tunnels,\n"
+"this is the one mentioned in the LeaseSet published in the\n"
+"network database.  For outbound tunnels, the\n"
+"gateway is the originating router.  (e.g. both A and D above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:44
+msgid ""
+"Tunnel endpoint - the last router in a tunnel.  (e.g. both C and F"
+" above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:45
+msgid ""
+"Tunnel participant - all routers in a tunnel except for the "
+"gateway or\n"
+"endpoint (e.g. both B and E above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:49
+msgid ""
+"n-Hop tunnel - a tunnel with a specific number of inter-router "
+"jumps, e.g.:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:51
+msgid "0-hop tunnel - a tunnel where the gateway is also the endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:52
+msgid ""
+"1-hop tunnel - a tunnel where the gateway talks directly to the "
+"endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:53
+msgid ""
+"2-(or more)-hop tunnel - a tunnel where there is at least one "
+"intermediate\n"
+"tunnel participant. (the above diagram includes two 2-hop tunnels - one\n"
+"outbound from Alice, one inbound to Bob)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:60
+#, python-format
+msgid ""
+"Tunnel ID - A 4 "
+"byte integer\n"
+"different for each hop in a tunnel, and unique among all tunnels on a "
+"router.\n"
+"Chosen randomly by the tunnel creator."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:67
+msgid "Tunnel Build Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:68
+#, python-format
+msgid ""
+"Routers performing the three roles (gateway, participant, endpoint) are "
+"given\n"
+"different pieces of data in the initial\n"
+"Tunnel Build Message\n"
+"to accomplish their tasks:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:75
+msgid "The tunnel gateway gets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:77
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:97
+#, python-format
+msgid ""
+"tunnel encryption key - an AES private key for "
+"encrypting\n"
+"messages and instructions to the next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:81
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:101
+#, python-format
+msgid ""
+"tunnel IV key - an AES private key for "
+"double-encrypting\n"
+"the IV to the next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:85
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:105
+#, python-format
+msgid ""
+"reply key - an AES public key for "
+"encrypting\n"
+"the reply to the tunnel build request"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:89
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:109
+msgid ""
+"reply IV - the IV for encrypting the reply to the tunnel build "
+"request"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:90
+msgid "tunnel id - 4 byte integer (inbound gateways only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:91
+msgid ""
+"next hop - what router is the next one in the path (unless this is"
+" a 0-hop tunnel, and the gateway is also the endpoint)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:92
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:112
+msgid "next tunnel id - The tunnel ID on the next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:95
+msgid "All intermediate tunnel participants get:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:110
+msgid "tunnel id - 4 byte integer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:111
+msgid "next hop - what router is the next one in the path"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:115
+msgid "The tunnel endpoint gets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:117
+#, python-format
+msgid ""
+"tunnel encryption key - an AES private key for "
+"encrypting\n"
+"messages and instructions to the the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:121
+#, python-format
+msgid ""
+"tunnel IV key - an AES private key for "
+"double-encrypting\n"
+"the IV to the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:125
+#, python-format
+msgid ""
+"reply key - an AES public key for "
+"encrypting\n"
+"the reply to the tunnel build request (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:129
+msgid ""
+"reply IV - the IV for encrypting the reply to the tunnel build "
+"request (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:130
+msgid "tunnel id - 4 byte integer (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:131
+msgid ""
+"reply router - the inbound gateway of the tunnel to send the reply"
+" through (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:132
+msgid ""
+"reply tunnel id - The tunnel ID of the reply router (outbound "
+"endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:137
+#, python-format
+msgid ""
+"Details are in the\n"
+"tunnel creation specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:142
+msgid "Tunnel pooling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:143
+#, python-format
+msgid ""
+"Several tunnels for a particular purpose may be grouped into a \"tunnel "
+"pool\",\n"
+"as described in the\n"
+"tunnel specification.\n"
+"This provides redundancy and additional bandwidth.\n"
+"The pools used by the router itself are called \"exploratory tunnels\".\n"
+"The pools used by applications are called \"client tunnels\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:154
+msgid "Tunnel length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:155
+#, python-format
+msgid ""
+"As mentioned above, each client requests that their router provide "
+"tunnels to\n"
+"include at least a certain number of hops.\n"
+"The decision as to how many routers\n"
+"to have in one's outbound and inbound tunnels has an important effect "
+"upon the\n"
+"latency, throughput, reliability, and anonymity provided by I2P - the "
+"more peers\n"
+"that messages have to go through, the longer it takes to get there and "
+"the more\n"
+"likely that one of those routers will fail prematurely.  The less routers"
+" in a\n"
+"tunnel, the easier it is for an adversary to mount traffic analysis "
+"attacks and\n"
+"pierce someone's anonymity.\n"
+"Tunnel lengths are specified by clients via\n"
+"I2CP options.\n"
+"The maximum number of hops in a tunnel is 7."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:171
+msgid "0-hop tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:172
+msgid ""
+"With no remote routers in a tunnel, the user has very basic plausible\n"
+"deniability (since no one knows for sure that the peer that sent them the"
+"\n"
+"message wasn't simply just forwarding it on as part of the tunnel). "
+"However, it\n"
+"would be fairly easy to mount a statistical analysis attack and notice "
+"that\n"
+"messages targeting a specific destination are always sent through a "
+"single\n"
+"gateway.  Statistical analysis against outbound 0-hop tunnels are more "
+"complex,\n"
+"but could show similar information (though would be slightly harder to "
+"mount)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:182
+msgid "1-hop tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:183
+#, python-format
+msgid ""
+"With only one remote router in a tunnel, the user has both plausible\n"
+"deniability and basic anonymity, as long as they are not up against an "
+"internal\n"
+"adversary (as described on threat model)."
+" However,\n"
+"if the adversary ran a sufficient number of routers such that the single "
+"remote\n"
+"router in the tunnel is often one of those compromised ones, they would "
+"be able\n"
+"to mount the above statistical traffic analysis attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:192
+msgid "2-hop tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:193
+msgid ""
+"With two or more remote routers in a tunnel, the costs of mounting the "
+"traffic\n"
+"analysis attack increases, since many remote routers would have to be "
+"compromised\n"
+"to mount it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:199
+msgid "3-hop (or more) tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:200
+#, python-format
+msgid ""
+"To reduce the susceptibility to some attacks,\n"
+"3 or more hops are recommended for the highest level of protection.\n"
+"Recent studies\n"
+"also conclude that more than 3 hops does not provide additional "
+"protection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:208
+msgid "Tunnel default lengths"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:209
+#, python-format
+msgid ""
+"The router uses 2-hop tunnels by default for its exploratory tunnels.\n"
+"Client tunnel defaults are set by the application, using\n"
+"I2CP options.\n"
+"Most applications use 2 or 3 hops as their default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:218
+msgid "Tunnel testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:219
+#, python-format
+msgid ""
+"All tunnels are periodically tested by their creator by sending a\n"
+"DeliveryStatusMessage out an outbound tunnel and bound for another "
+"inbound tunnel\n"
+"(testing both tunnels at once).  If either fails a number of consecutive "
+"tests, it is marked as no longer\n"
+"functional. If it was used for a client's inbound tunnel, a new leaseSet\n"
+"is created.\n"
+"Tunnel test failures are also reflected in the\n"
+"capacity rating in the peer "
+"profile."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:230
+msgid "Tunnel creation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:231
+#, python-format
+msgid ""
+"Tunnel creation is handled by garlic "
+"routing\n"
+"a Tunnel Build Message to a router, requesting that they participate in "
+"the\n"
+"tunnel (providing them with all of the appropriate information, as above,"
+" along\n"
+"with a certificate, which right now is a 'null' cert, but will support "
+"hashcash\n"
+"or other non-free certificates when necessary).\n"
+"That router forwards the message to the next hop in the tunnel.\n"
+"Details are in the\n"
+"tunnel creation specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:245
+#, python-format
+msgid ""
+"Multi-layer encryption is handled by garlic"
+" encryption\n"
+"of tunnel messages.\n"
+"Details are in the\n"
+"tunnel specification.\n"
+"The IV of each hop is encrypted with a separate key as explained there."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:257
+msgid ""
+"Other tunnel test techniques could be used, such as\n"
+"garlic wrapping a number of tests into cloves, testing individual tunnel\n"
+"participants separately, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:263
+msgid "Move to 3-hop exploratory tunnels defaults."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:267
+msgid ""
+"In a distant future release,\n"
+"options specifying the pooling, mixing, and chaff generation settings may"
+" be implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:272
+msgid ""
+"In a distant future release,\n"
+"limits on the quantity and size of messages allowed during the\n"
+"tunnel's lifetime may be implemented (e.g. no more than 300 messages or\n"
+"1MB per minute)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:284
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:15
+msgid "Tunnel specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:286
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:17
+msgid "Tunnel creation specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:288
+msgid "Unidirectional tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:290
+msgid "Tunnel message specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:292
+msgid "Garlic routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:294
+msgid "ElGamal/AES+SessionTag"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:296
+msgid "I2CP options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:6
+msgid ""
+"The I2P Client Protocol (I2CP) exposes a strong separation of concerns "
+"between\n"
+"the router and any client that wishes to communicate over the network.  "
+"It enables\n"
+"secure and asynchronous messaging by sending and receiving messages over "
+"a \n"
+"single TCP socket.\n"
+"With I2CP, a client application tells the\n"
+"router who they are (their \"destination\"), what anonymity, reliability,"
+" and \n"
+"latency tradeoffs to make, and where to send messages.  In turn the "
+"router uses\n"
+"I2CP to tell the client when any messages have arrived, and to request "
+"authorization\n"
+"for some tunnels to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:18
+#, python-format
+msgid ""
+"The protocol itself is implemented in Java, to provide the\n"
+"Client SDK.\n"
+"This SDK is exposed in the i2p.jar package, which implements the client-"
+"side of I2CP.\n"
+"Clients should never need to access the router.jar package, which "
+"contains the\n"
+"router itself and the router-side of I2CP.\n"
+"There is also a C library implementation.\n"
+"A non-Java client would also have to implement the\n"
+"streaming library for TCP-style connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:31
+#, python-format
+msgid ""
+"Applications can take advantage of the base I2CP plus the \n"
+"streaming and datagram libraries\n"
+"by using the Simple Anonymous Messaging or BOB protocols,\n"
+"which do not require clients to deal with any sort of cryptography.\n"
+"Also, clients may access the network by one of several proxies -\n"
+"HTTP, CONNECT, and SOCKS 4/4a/5.\n"
+"Alternatively, Java clients may access those libraries in "
+"ministreaming.jar and streaming.jar.\n"
+"So there are several options for both Java and non-Java applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:43
+#, python-format
+msgid ""
+"Client-side end-to-end encryption (encrypting the data over the I2CP "
+"connection)\n"
+"was disabled in I2P release 0.6,\n"
+"leaving in place the ElGamal/AES end-to-end "
+"encryption\n"
+"which is implemented in the router.\n"
+"The only cryptography that client libraries must still implement is\n"
+"DSA public/private key signing\n"
+"for LeaseSets and\n"
+"Session Configurations, and"
+" management of those keys."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:56
+msgid ""
+"In a standard I2P installation, port 7654 is used by external java "
+"clients to communicate\n"
+"with the local router via I2CP.\n"
+"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, "
+"set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart.\n"
+"Clients in the same JVM as the router pass messages directly to the "
+"router\n"
+"through an internal JVM interface."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:65
+#, python-format
+msgid ""
+"The router also supports external connections over SSL.\n"
+"While SSL is not the default, it is strongly recommended for any traffic "
+"that may\n"
+"be exposed to the open Internet. The authorization user/password (if "
+"any), the\n"
+"Private Key and\n"
+"Signing Private "
+"Key for the\n"
+"Destination\n"
+"are all transmitted in-the-clear unless SSL is enabled."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:75
+msgid "I2CP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:76
+#, python-format
+msgid "Now on the I2CP Specification page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:81
+msgid "I2CP Initialization"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:82
+#, python-format
+msgid ""
+"When a client connects to the router, it first sends a single protocol "
+"version byte (0x2A).\n"
+"Then it sends a GetDate Message and "
+"waits for the SetDate Message "
+"response.\n"
+"Next, it sends a CreateSession "
+"Message containing the session configuration.\n"
+"It next awaits a RequestLeaseSet"
+" Message from the router, indicating that inbound tunnels\n"
+"have been built, and responds with a CreateLeaseSetMessage containing the"
+" signed LeaseSet.\n"
+"The client may now initiate or receive connections from other I2P "
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:91
+msgid "I2CP Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:92
+#, python-format
+msgid ""
+"The following options are traditionally passed to the router via\n"
+"a SessionConfig contained "
+"in a CreateSession Message or "
+"a ReconfigureSession "
+"Message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:98
+msgid "Router-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:103
+#: i2p2www/pages/site/docs/protocol/i2cp.html:446
+msgid "As Of Release"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:104
+#: i2p2www/pages/site/docs/protocol/i2cp.html:447
+msgid "Recommended Arguments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:105
+#: i2p2www/pages/site/docs/protocol/i2cp.html:448
+msgid "Allowable Range"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:113
+#: i2p2www/pages/site/docs/protocol/i2cp.html:126
+#: i2p2www/pages/site/docs/protocol/i2cp.html:135
+#: i2p2www/pages/site/docs/protocol/i2cp.html:144
+#: i2p2www/pages/site/docs/protocol/i2cp.html:153
+#: i2p2www/pages/site/docs/protocol/i2cp.html:168
+#: i2p2www/pages/site/docs/protocol/i2cp.html:183
+#: i2p2www/pages/site/docs/protocol/i2cp.html:192
+#: i2p2www/pages/site/docs/protocol/i2cp.html:240
+#: i2p2www/pages/site/docs/protocol/i2cp.html:252
+#: i2p2www/pages/site/docs/protocol/i2cp.html:264
+#, python-format
+msgid "number from %(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:114
+#: i2p2www/pages/site/docs/protocol/i2cp.html:136
+#: i2p2www/pages/site/docs/protocol/i2cp.html:145
+#: i2p2www/pages/site/docs/protocol/i2cp.html:154
+#: i2p2www/pages/site/docs/protocol/i2cp.html:169
+#: i2p2www/pages/site/docs/protocol/i2cp.html:241
+#: i2p2www/pages/site/docs/protocol/i2cp.html:253
+#: i2p2www/pages/site/docs/protocol/i2cp.html:265
+#: i2p2www/pages/site/docs/protocol/i2cp.html:538
+#, python-format
+msgid "%(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:116
+msgid ""
+"Number of tunnels in.\n"
+"Limit was increased from 6 to 16 in release 0.9; however, numbers higher "
+"than 6 are not\n"
+"currently recommended, as this is untested and is incompatible with older"
+" releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:127
+#: i2p2www/pages/site/docs/protocol/i2cp.html:184
+#: i2p2www/pages/site/docs/protocol/i2cp.html:193
+msgid "No limit"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:129
+msgid "Number of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:138
+msgid "Length of tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:147
+msgid "Length of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:156
+msgid ""
+"Random amount to add or subtract to the length of tunnels in.\n"
+"A positive number x means add a random amount from 0 to x inclusive.\n"
+"A negative number -x means add a random amount from -x to x inclusive.\n"
+"The router will limit the total length of the tunnel to 0 to 7 inclusive."
+"\n"
+"The default variance was 1 prior to release 0.7.6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:171
+msgid ""
+"Random amount to add or subtract to the length of tunnels out.\n"
+"A positive number x means add a random amount from 0 to x inclusive.\n"
+"A negative number -x means add a random amount from -x to x inclusive.\n"
+"The router will limit the total length of the tunnel to 0 to 7 inclusive."
+"\n"
+"The default variance was 1 prior to release 0.7.6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:186
+msgid "Number of redundant fail-over for tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:195
+msgid "Number of redundant fail-over for tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:204
+msgid ""
+"Name of tunnel - generally used in routerconsole, which will\n"
+"use the first few characters of the Base64 hash of the destination by "
+"default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:216
+msgid "Name of tunnel - generally ignored unless inbound.nickname is unset."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:225
+msgid "If incoming zero hop tunnel is allowed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:234
+msgid "If outgoing zero hop tunnel is allowed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:243
+#: i2p2www/pages/site/docs/protocol/i2cp.html:255
+msgid ""
+"Number of IP bytes to match to determine if\n"
+"two routers should not be in the same tunnel. 0 to disable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:267
+msgid ""
+"Priority adjustment for outbound messages.\n"
+"Higher is higher priority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:279
+msgid "Should generally be set to true for clients and false for servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:288
+msgid ""
+"Guaranteed is disabled;\n"
+"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1,"
+" the client side default is None as of 0.9.4"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:300
+#: i2p2www/pages/site/docs/protocol/i2cp.html:579
+msgid ""
+"If true, the router just sends the MessagePayload instead\n"
+"of sending a MessageStatus and awaiting a ReceiveMessageBegin."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:312
+msgid ""
+"Comma-separated list of Base 64 Hashes of peers to build tunnels through;"
+" for debugging only"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:321
+msgid ""
+"For authorization, if required by the router.\n"
+"If the client is running in the same JVM as a router, this option is not "
+"required.\n"
+"Warning - username and password are sent in the clear to the router, "
+"unless using SSL (i2cp.SSL=true).\n"
+"Authorization is only recommended when using SSL."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:343
+msgid ""
+"Number of ElGamal/AES Session Tags to send at a time.\n"
+"For clients with relatively low bandwidth per-client-pair (IRC, some UDP "
+"apps), this may be set lower."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:355
+msgid ""
+"Minimum number of ElGamal/AES Session Tags before we send more.\n"
+"Recommended: approximately tagsToSend * 2/3"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:367
+msgid ""
+"Set to false to disable ever bundling a reply LeaseSet.\n"
+"For clients that do not publish their LeaseSet, this option must be true\n"
+"for any reply to be possible. \"true\" is also recommended for multihomed"
+" servers\n"
+"with long connection times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:374
+msgid ""
+"Setting to \"false\" may save significant outbound bandwidth, especially "
+"if\n"
+"the client is configured with a large number of inbound tunnels (Leases)."
+"\n"
+"If replies are still required, this may shift the bandwidth burden to\n"
+"the far-end client and the floodfill.\n"
+"There are several cases where \"false\" may be appropriate:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:382
+msgid "Unidirectional communication, no reply required"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:383
+msgid "LeaseSet is published and higher reply latency is acceptable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:384
+msgid ""
+"LeaseSet is published, client is a \"server\", all connections are "
+"inbound\n"
+"so the connecting far-end destination obviously has the leaseset already."
+"\n"
+"Connections are either short, or it is acceptable for latency on a long-"
+"lived\n"
+"connection to temporarily increase while the other end re-fetches the "
+"LeaseSet\n"
+"after expiration.\n"
+"HTTP servers may fit these requirements."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:402
+msgid ""
+"Any other options prefixed with \"inbound.\" are stored\n"
+"in the \"unknown options\" properties of the inbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:414
+msgid ""
+"Any other options prefixed with \"outbound.\" are stored\n"
+"in the \"unknown options\" properties of the outbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:421
+msgid ""
+"Note: Large quantity, length, or variance settings may cause significant "
+"performance or reliability problems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:425
+#, python-format
+msgid ""
+"Note: As of release 0.7.7, option names and values must use UTF-8 "
+"encoding.\n"
+"This is primarily useful for nicknames.\n"
+"Prior to that release, options with multi-byte characters were corrupted."
+"\n"
+"Since options are encoded in a Mapping,\n"
+"all option names and values are limited to 255 bytes (not characters) "
+"maximum."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:433
+msgid ""
+"The following options are interpreted on the client side,\n"
+"and will be interpreted if passed to the I2PSession via the "
+"I2PClient.createSession() call.\n"
+"The streaming lib should also pass these options through to I2CP.\n"
+"Other implementations may have different defaults."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:441
+msgid "Client-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:459
+msgid ""
+"Router hostname.\n"
+"If the client is running in the same JVM as a router, this option is "
+"ignored, and the client connects to that router internally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:471
+msgid ""
+"Router I2CP port.\n"
+"If the client is running in the same JVM as a router, this option is "
+"ignored, and the client connects to that router internally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:483
+msgid ""
+"Connect to the router using SSL.\n"
+"If the client is running in the same JVM as a router, this option is "
+"ignored, and the client connects to that router internally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:495
+msgid "Gzip outbound data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:504
+msgid "Reduce tunnel quantity when idle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:513
+msgid "Close I2P session when idle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:520
+#: i2p2www/pages/site/docs/protocol/i2cp.html:529
+#, python-format
+msgid "%(num)s minimum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:522
+msgid "(ms) Idle time required (default 20 minutes, minimum 5 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:531
+msgid "(ms) Idle time required (default 30 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:540
+msgid "Tunnel quantity when reduced (applies to both inbound and outbound)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:549
+msgid "Encrypt the lease"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:558
+msgid "Base64 SessionKey (44 characters)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:567
+msgid ""
+"Guaranteed is disabled;\n"
+"None implemented in 0.8.1; None is the default as of 0.9.4"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:586
+msgid ""
+"Note: All arguments, including numbers, are strings. True/false values "
+"are case-insensitive strings.\n"
+"Anything other than case-insensitive \"true\" is interpreted as false.\n"
+"All option names are case-sensitive."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:592
+msgid "I2CP Payload Data Format and Multiplexing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:593
+#, python-format
+msgid ""
+"The end-to-end messages handled by I2CP (i.e. the data sent by the client"
+" in a\n"
+"SendMessageMessage\n"
+"and received by the client in a\n"
+"MessagePayloadMessage)\n"
+"are gzipped with a standard 10-byte gzip\n"
+"header beginning with 0x1F 0x8B 0x08 as\n"
+"specified by RFC "
+"1952.\n"
+"As of release 0.7.1, I2P uses ignored portions of the gzip header to "
+"include\n"
+"protocol, from-port, and to-port information, thus supporting streaming "
+"and\n"
+"datagrams on the same destination, and allowing query/response using "
+"datagrams\n"
+"to work reliably in the presence of multiple channels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:607
+msgid ""
+"The gzip function cannot be completely turned off, however setting "
+"i2cp.gzip=false\n"
+"turns the gzip effort setting to 0, which may save a little CPU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:613
+#: i2p2www/pages/site/docs/protocol/i2np.html:33
+msgid "Bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:614
+msgid "Content"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:619
+msgid "Gzip header"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:624
+msgid "Gzip flags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:629
+msgid "I2P Source port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:634
+msgid "I2P Destination port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:639
+msgid "Gzip xflags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:644
+msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:648
+msgid ""
+"Data integrity is verified with the standard gzip CRC-32 as\n"
+"specified by RFC 1952."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:656
+msgid ""
+"The current authorization mechanism could be modified to use hashed "
+"passwords."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:660
+msgid ""
+"The Signing Private Keys is included in the Create Lease Set message,\n"
+"it is not required. Revocation is unimplemented.\n"
+"It should be replaced with random data or removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:666
+#, python-format
+msgid ""
+"Some improvements may be able to use messages previously defined but not "
+"implemented.\n"
+"For reference, here is the\n"
+"I2CP Protocol Specification Version 0.9\n"
+"(PDF) dated August 28, 2003.\n"
+"That document also references the\n"
+"Common Data Structures Specification Version 0.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:3
+msgid "June 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:6
+msgid "I2P Network Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:7
+msgid ""
+"The I2P Network Protocol (I2NP),\n"
+"which is sandwiched between I2CP and the various I2P transport protocols,"
+" manages the\n"
+"routing and mixing of messages between routers, as well as the selection "
+"of what\n"
+"transports to use when communicating with a peer for which there are "
+"multiple\n"
+"common transports supported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:15
+msgid "I2NP Definition"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:16
+msgid ""
+"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-"
+"router, point-to-point messages.\n"
+"By encrypting and wrapping messages in other messages, they can be sent "
+"in a secure way\n"
+"through multiple hops to the ultimate destination.\n"
+"Priority is only used locally at the origin, i.e. when queuing for "
+"outbound delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:23
+#, python-format
+msgid ""
+"The priorities listed below may not be current and are subject to change."
+"\n"
+"See the OutNetMessage Javadocs\n"
+"for the current priority settings.\n"
+"Priority queueing implementation may vary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:30
+msgid "Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:33
+#: i2p2www/pages/site/docs/spec/streaming.html:35
+msgid "Field"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:34
+msgid "Unique ID"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:35
+msgid "Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:36
+#: i2p2www/pages/site/docs/protocol/i2np.html:93
+msgid "Payload Length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:37
+msgid "Checksum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:38
+msgid "Payload"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:41
+#, python-format
+msgid ""
+"While the maximum payload size is nominally 64KB, the size is further "
+"constrained by the\n"
+"method of fragmenting I2NP messages into multiple 1KB tunnel messages as "
+"described on\n"
+"the tunnel implementation page.\n"
+"The maximum number of fragments is 64, and the message may not be "
+"perfectly aligned,\n"
+"So the message must nominally fit in 63 fragments."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:49
+msgid ""
+"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL "
+"delivery mode);\n"
+"the maximum size of a follow-on fragment is 996 bytes.\n"
+"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 "
+"bytes, or 61.2 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:55
+msgid ""
+"In addition, the transports may have additional restrictions.\n"
+"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be "
+"increased in a future release.\n"
+"The SSU limit is approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:61
+msgid ""
+"Note that these are not the limits for datagrams that the client sees, as"
+" the\n"
+"router may bundle a reply leaseset and/or session tags together with the "
+"client message\n"
+"in a garlic message. The leaseset and tags together may add about 5.5KB.\n"
+"Therefore the current datagram limit is about 10KB. This limit will be\n"
+"increased in a future release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:69
+msgid "Message Types"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:70
+msgid ""
+"Higher-numbered priority is higher priority.\n"
+"The majority of traffic is TunnelDataMessages (priority 400),\n"
+"so anything above 400 is essentially high priority, and\n"
+"anything below is low priority.\n"
+"Note also that many of the messages are generally routed\n"
+"through exploratory tunnels, not client tunnels, and\n"
+"therefore may not be in the same queue unless the\n"
+"first hops happen to be on the same peer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:81
+msgid ""
+"Also, not all message types are sent unencrypted.\n"
+"For example, when testing a tunnel, the router wraps a\n"
+"DeliveryStatusMessage, which is wrapped in a GarlicMessage,\n"
+"which is wrapped in a DataMessage."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:91
+msgid "Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:92
+msgid "Type"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:95
+msgid "Comments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:103
+msgid "May vary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:109
+msgid ""
+"Size is 65 + 32*(number of hashes) where typically, the hashes for\n"
+"three floodfill routers are returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:118
+msgid "Varies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:120
+msgid ""
+"Priority may vary.\n"
+"Size is 898 bytes for a typical 2-lease leaseSet.\n"
+"RouterInfo structures are compressed, and size varies; however\n"
+"there is a continuing effort to reduce the amount of data published in a "
+"RouterInfo\n"
+"as we approach release 1.0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:134
+msgid "Priority may vary on a per-destination basis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:144
+msgid ""
+"Used for message replies, and for testing tunnels - generally wrapped in "
+"a GarlicMessage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:152
+msgid ""
+"Generally wrapped in a DataMessage -\n"
+"but when unwrapped, given a priority of 100 by the forwarding router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:179
+msgid ""
+"The most common message. Priority for tunnel participants, outbound "
+"endpoints, and inbound gateways was\n"
+"reduced to 200 as of release 0.6.1.33.\n"
+"Outbound gateway messages (i.e. those originated locally) remains at 400."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:199
+msgid "Shorter TunnelBuildMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:207
+msgid "Shorter TunnelBuildReplyMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:210
+#, python-format
+msgid "Others listed in 2003 Spec"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:216
+msgid "Obsolete, Unused"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:220
+msgid "Full Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:221
+#, python-format
+msgid ""
+"On the I2NP Specification page.\n"
+"See also the\n"
+"Common Data Structure Specification "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:228
+msgid ""
+"It isn't clear whether the current priority scheme is generally "
+"effective,\n"
+"and whether the priorities for various messages should be adjusted "
+"further.\n"
+"This is a topic for further research, analysis and testing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:2
+msgid "Protocol Stack"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:7
+#, python-format
+msgid ""
+"Here is the protocol stack for I2P.\n"
+"See also the Index to Technical Documentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:12
+msgid ""
+"Each of the layers in the stack provides extra capabilities.\n"
+"The capabilities are listed below, starting at the bottom of the protocol"
+" stack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:18
+msgid "Internet Layer:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:20
+msgid ""
+"IP: Internet Protocol, allow addressing hosts on the regular internet and"
+" routing packets across the internet using best-effort delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:23
+msgid "Transport Layer:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:25
+msgid ""
+"TCP: Transmission Control Protocol, allow reliable, in-order delivery of "
+"packets across the internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:27
+msgid ""
+"UDP: User Datagram Protocol, allow unreliable, out-of-order delivery of "
+"packets across the internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:30
+msgid ""
+"I2P Transport Layer: provide encrypted connections between 2 I2P "
+"routers. These are not anonymous yet, this is strictly a hop-to-hop "
+"connection.\n"
+"Two protocols are implemented to provide these capabilities. NTCP builds "
+"on top of TCP, while SSU uses UDP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:35
+msgid "NIO-based TCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:37
+msgid "Secure Semi-reliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:40
+msgid "I2P Tunnel Layer: provide full encrypted tunnel connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:42
+#, python-format
+msgid ""
+"Tunnel messages: tunnel messages are "
+"large messages containing encrypted I2NP (see below) messages and "
+"encrypted instructions for their delivery.\n"
+"The encryption is layered. The first hop will decrypt the tunnel message "
+"and read a part. Another part can still be encrypted (with another key),"
+"\n"
+"so it will be forwarded."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:48
+#, python-format
+msgid ""
+"I2NP messages: I2P Network Protocol messages are"
+" used to pass messages through multiple routers. These I2NP messages are "
+"combined in tunnel messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:53
+msgid ""
+"I2P Garlic Layer: provide encrypted and anonymous end-to-end I2P "
+"message delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:55
+#, python-format
+msgid ""
+"I2NP messages: I2P Network Protocol messages are"
+" wrapped in each other and used to ensure encryption between two tunnels "
+"and are passed along from source to destination, keeping both anonymous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:61
+msgid ""
+"The following layers are strictly speaking no longer part of the I2P "
+"Protocol stack, they are not part of the core 'I2P router' functionality."
+"\n"
+"However, each of these layers adds additional functionality, to allow "
+"applications simple and convenient I2P usage."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:67
+msgid ""
+"I2P Client Layer: allow any client to use I2P functionality, "
+"without requiring the direct use of the router API."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:69
+#, python-format
+msgid ""
+"I2CP: I2P Client Protocol, allows secure and "
+"asynchronous messaging over I2P by communicating messages over the I2CP "
+"TCP socket."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:74
+msgid ""
+"I2P End-to-end Transport Layer: allow TCP- or UDP-like "
+"functionality on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:76
+#, python-format
+msgid ""
+"Streaming Library: an implementation of "
+"TCP-like streams over I2P. This allows easier porting of existing "
+"applications to I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:80
+#, python-format
+msgid ""
+"Datagram Library: an implementation of UDP-"
+"like messages over I2P. This allows easier porting of existing "
+"applications to I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:85
+msgid ""
+"I2P Application Interface Layer: additional (optional) libraries "
+"allowing easier implementations on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:93
+msgid "I2P Application Proxy Layer: proxy systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:95
+#, python-format
+msgid "HTTP Client/Server, IRC Client, SOCKS, Streamr"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:99
+msgid ""
+"Finally, what could be considered the 'I2P application layer', is "
+"a large number of applications on top of I2P.\n"
+"We can order this based on the I2P stack layer they use."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:104
+msgid "Streaming/datagram applications: i2psnark, Syndie, i2phex..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:105
+msgid "SAM/BOB applications: IMule, i2p-bt, i2prufus, Robert..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:106
+#, python-format
+msgid ""
+"Other I2P applications: Syndie, EepGet, plugins..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:107
+msgid ""
+"Regular applications: Jetty, Apache, Monotone, CVS, browsers, "
+"e-mail..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:111
+msgid "I2P Network stack"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:113
+msgid "Figure 1: The layers in the I2P Network stack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:118
+msgid "Note: SAM/SAMv2 can use both the streaming lib and datagrams."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:2
+msgid "I2P Blockfile Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:3
+msgid "January 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:6
+msgid "Blockfile and Hosts Database Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:8
+#, python-format
+msgid ""
+"This document specifies\n"
+"the I2P blockfile file format\n"
+"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:14
+msgid ""
+"The blockfile provides fast Destination lookup in a compact format. While"
+" the blockfile page overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry.\n"
+"The metadata may be used in the future to provide advanced addressbook "
+"features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:24
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is adopted from the\n"
+"Metanotion Blockfile Database.\n"
+"First we will define the file format, then the use of that format by the "
+"BlockfileNamingService."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:32
+msgid "Blockfile Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:33
+msgid ""
+"The original blockfile spec was modified to add magic numbers to each "
+"page.\n"
+"The file is structured in 1024-byte pages. Pages are numbered starting "
+"from 1.\n"
+"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the "
+"file.\n"
+"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in"
+" the file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:40
+msgid ""
+"All 2-byte integer values are unsigned.\n"
+"All 4-byte integer values (page numbers) are signed and negative values "
+"are illegal."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:45
+msgid ""
+"The database is designed to be opened and accessed by a single thread.\n"
+"The BlockfileNamingService provides synchronization."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:50
+msgid "Superblock format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:65
+msgid "Skip list block page format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:80
+msgid ""
+"Skip level block page format is as follows.\n"
+"All levels have a span. Not all spans have levels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:95
+msgid ""
+"Skip span block page format is as follows.\n"
+"Key/value structures are sorted by key within each span and across all "
+"spans.\n"
+"Key/value structures are sorted by key within each span.\n"
+"Spans other than the first span may not be empty."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:112
+msgid "Span Continuation block page format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:123
+msgid ""
+"Key/value structure format is as follows.\n"
+"Key and value lengths must not be split across pages, i.e. all 4 bytes "
+"must be on the same page.\n"
+"If there is not enough room the last 1-3 bytes of a page are unused and "
+"the lengths will\n"
+"be at offset 8 in the continuation page.\n"
+"Key and value data may be split across pages.\n"
+"Max key and value lengths are 65535 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:139
+msgid "Free list block page format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:151
+msgid "Free page block format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:160
+msgid ""
+"The metaindex (located at page 2) is a mapping of US-ASCII strings to "
+"4-byte integers.\n"
+"The key is the name of the skiplist and the value is the page index of "
+"the skiplist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:165
+msgid "Blockfile Naming Service Tables"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:166
+msgid ""
+"The tables created and used by the BlockfileNamingService are as follows."
+"\n"
+"The maximum number of entries per span is 16."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:171
+msgid "Properties Skiplist"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:172
+#, python-format
+msgid ""
+"%(INFO)s is the master database skiplist with String/Properties key/value"
+" entries containing only one entry:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:184
+msgid "Reverse Lookup Skiplist"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:185
+#, python-format
+msgid ""
+"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties "
+"key/value entries\n"
+"    (as of database version 2):"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:199
+msgid "hosts.txt, userhosts.txt, and privatehosts.txt Skiplists"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:200
+msgid ""
+"For each host database, there is a skiplist containing\n"
+"the hosts for that database.\n"
+"The keys/values in these skiplists are as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:211
+msgid "The DestEntry Properties typically contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:220
+msgid "Hostname keys are stored in lower-case and always end in \".i2p\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:2
+msgid "Common structure Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:6
+msgid "Data types Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:7
+#, python-format
+msgid ""
+"This document describes some data types common to all I2P protocols, like"
+"\n"
+"I2NP, I2CP,\n"
+"SSU, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:17
+msgid "Represents a non-negative integer.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:20
+#: i2p2www/pages/site/docs/spec/common-structures.html:31
+#: i2p2www/pages/site/docs/spec/common-structures.html:41
+#: i2p2www/pages/site/docs/spec/common-structures.html:54
+#: i2p2www/pages/site/docs/spec/common-structures.html:69
+#: i2p2www/pages/site/docs/spec/common-structures.html:82
+#: i2p2www/pages/site/docs/spec/common-structures.html:94
+#: i2p2www/pages/site/docs/spec/common-structures.html:106
+#: i2p2www/pages/site/docs/spec/common-structures.html:118
+#: i2p2www/pages/site/docs/spec/common-structures.html:130
+#: i2p2www/pages/site/docs/spec/common-structures.html:142
+#: i2p2www/pages/site/docs/spec/common-structures.html:154
+#: i2p2www/pages/site/docs/spec/common-structures.html:166
+#: i2p2www/pages/site/docs/spec/common-structures.html:178
+#: i2p2www/pages/site/docs/spec/common-structures.html:231
+#: i2p2www/pages/site/docs/spec/common-structures.html:314
+#: i2p2www/pages/site/docs/spec/common-structures.html:363
+#: i2p2www/pages/site/docs/spec/common-structures.html:415
+#: i2p2www/pages/site/docs/spec/common-structures.html:462
+#: i2p2www/pages/site/docs/spec/common-structures.html:597
+#: i2p2www/pages/site/docs/spec/common-structures.html:660
+#: i2p2www/pages/site/docs/spec/streaming.html:35
+msgid "Contents"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:21
+msgid "1 to 8 bytes in network byte order representing an unsigned integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:27
+msgid ""
+"The number of milliseconds since midnight on January 1, 1970 in the GMT "
+"timezone.\n"
+"If the number is 0, the date is undefined or null.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:32
+msgid "8 byte Integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:38
+msgid "Represents a UTF-8 encoded string.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:42
+msgid ""
+"1 or more bytes where the first byte is the number of bytes (not "
+"characters!)\n"
+"in the string and the remaining 0-255 bytes are the non-null terminated "
+"UTF-8 encoded character array.\n"
+"Length limit is 255 bytes (not characters). Length may be 0.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:50
+msgid ""
+"A boolean value, supporting null/unknown representation\n"
+"0=false, 1=true, 2=unknown/null\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:55
+msgid "1 byte Integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:59
+msgid "Deprecated - unused\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:65
+#, python-format
+msgid ""
+"This structure is used in ElGamal encryption, representing only the "
+"exponent, not the primes, which are constant and defined in\n"
+"the cryptography specification.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:70
+#: i2p2www/pages/site/docs/spec/common-structures.html:83
+msgid "256 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:78
+#, python-format
+msgid ""
+"This structure is used in ElGamal decryption, representing only the "
+"exponent, not the primes which are constant and defined in\n"
+"the cryptography specification.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:91
+msgid "This structure is used for AES256 encryption and decryption.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:95
+#: i2p2www/pages/site/docs/spec/common-structures.html:143
+#: i2p2www/pages/site/docs/spec/common-structures.html:155
+msgid "32 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:103
+#, python-format
+msgid ""
+"This structure is used for verifying DSA signatures.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:107
+msgid "128 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:115
+#, python-format
+msgid ""
+"This structure is used for creating DSA signatures.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:119
+msgid "20 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:127
+#, python-format
+msgid ""
+"This structure represents the DSA "
+"signature of some data.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:131
+msgid "40 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:139
+msgid "Represents the SHA256 of some data.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:151
+msgid "A random number\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:163
+msgid "Defines an identifier that is unique to each router in a tunnel.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:167
+msgid "4 byte Integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:175
+msgid ""
+"A certificate is a container for various receipts or proof of works used "
+"throughout the I2P network.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:179
+msgid ""
+"1 byte Integer specifying certificate type,"
+" followed by a 2 Integer specifying the "
+"size of the certificate payload, then that many bytes.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:205
+msgid ""
+"For Router Identities, the "
+"Certificate is always NULL, no others are currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:209
+#, python-format
+msgid ""
+"For Garlic Cloves, the "
+"Certificate is always NULL, no others are currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:213
+#, python-format
+msgid ""
+"For Garlic Messages, the Certificate "
+"is always NULL, no others are currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:217
+msgid ""
+"For Destinations, the Certificate may"
+" be non-NULL,\n"
+"however non-NULL certs are not widely used, and any checking is left to "
+"the application-level."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:228
+msgid "A set of key/value mappings or properties\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:232
+msgid "A 2-byte size Integer followed by a series of String=String; pairs\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:259
+msgid ""
+"The encoding isn't optimal - we either need the '=' and ';' characters, "
+"or the string lengths, but not both"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:263
+msgid ""
+"Some documentation says that the strings may not include '=' or ';' but "
+"this encoding supports them"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:267
+msgid ""
+"Strings are defined to be UTF-8 but in the current implementation, I2CP "
+"uses UTF-8 but I2NP does not.\n"
+"For example,\n"
+"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store "
+"Message will be corrupted."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:273
+msgid ""
+"The encoding allows duplicate keys, however in any usage where the "
+"mapping is signed,\n"
+"duplicates may cause a signature failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:278
+msgid ""
+"Mappings contained in I2NP messages (i.e. in a RouterAddress or "
+"RouterInfo)\n"
+"must be sorted by key so that the signature will be invariant.\n"
+"Duplicate keys are not allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:284
+#, python-format
+msgid ""
+"Mappings contained in an I2CP "
+"SessionConfig\n"
+"must be sorted by key so that the signature will be invariant.\n"
+"Duplicate keys are not allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:290
+msgid ""
+"While it is application-dependent, keys and values are generally case-"
+"sensitive."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:294
+msgid ""
+"Key and value string length limits are 255 bytes (not characters) each, "
+"plus the length byte. Length byte may be 0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:298
+msgid ""
+"Total length limit is 65535 bytes, plus the 2 byte size field, or 65537 "
+"total."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:307
+msgid "Common structure specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:311
+msgid "Defines the way to uniquely identify a particular router\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:315
+msgid ""
+"PublicKey followed by SigningPublicKey and then a Certificate\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:352
+msgid ""
+"The certificate for a RouterIdentity is currently unused and is always "
+"NULL."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:360
+msgid ""
+"A Destination defines a particular endpoint to which messages can be "
+"directed for secure delivery.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:364
+msgid ""
+"PublicKey followed by a SigningPublicKey and then a Certificate\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:412
+msgid ""
+"Defines the authorization for a particular tunnel to receive messages "
+"targeting a Destination.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:416
+msgid ""
+"SHA256 Hash of the\n"
+"RouterIdentity of the gateway "
+"router, then the TunnelId, and finally an "
+"end Date\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:447
+msgid "Total size: 44 bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:457
+msgid ""
+"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be "
+"encrypted,\n"
+"and then the public key that can "
+"be used to revoke this particular version of the structure. The LeaseSet is one of the two structures "
+"stored in the network database(\n"
+"the other being RouterInfo), and is "
+"keyed under the SHA256 of the contained Destination.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:463
+msgid ""
+"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to"
+" revoke this version of the LeaseSet,\n"
+"then a 1 byte Integer specifying how many "
+"Lease structures are in the set, followed "
+"by the actual Lease structures and finally "
+"a Signature  of the previous\n"
+"bytes signed by the Destination's SigningPrivateKey"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:555
+msgid ""
+"The public key of the destination was used for the old i2cp-to-i2cp "
+"encryption\n"
+"which was disabled in version 0.6, it is currently unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:560
+#, python-format
+msgid ""
+"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n"
+"It is currently generated anew at every router startup, it is not "
+"persistent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:565
+msgid ""
+"The signature may be verified using the signing public key of the "
+"destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:569
+msgid ""
+"The signing_key is currently unused. It was intended for LeaseSet "
+"revocation, which is unimplemented.\n"
+"It is currently generated anew at every router startup, it is not "
+"persistent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:573
+msgid ""
+"The earliest expiration of all the Leases is treated as the timestamp or "
+"version of the LeaseSet.\n"
+"Routers will generally not accept a store of a LeaseSet unless it is "
+"\"newer\" than the current one.\n"
+"Take care when publishing a new LeaseSet where the oldest Lease is the "
+"same as the oldest Lease\n"
+"in the previous LeaseSet. The publishing router should generally "
+"increment the expiration\n"
+"of the oldest Lease by at least 1 ms in that case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:580
+msgid ""
+"Prior to release 0.9.7, when included in a DatabaseStore Message sent by "
+"the originating router,\n"
+"the router set all the published leases' expirations to the same value, "
+"that of the\n"
+"earliest lease. As of release 0.9.7, the router publishes the actual "
+"lease expiration for each lease.\n"
+"This is an implementation detail and not part of the structures "
+"specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:594
+msgid ""
+"This structure defines the means to contact a router through a transport "
+"protocol.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:598
+msgid ""
+"1 byte Integer defining the relative cost "
+"of using the address, where 0 is free and 255 is expensive, followed by "
+"the expiration Date after which the address "
+"should not be used, or if null, the address never expires.\n"
+"After that comes a String defining the "
+"transport protocol this router address uses. Finally there is a Mapping containing all of the transport "
+"specific options necessary to establish the connection, such as\n"
+"IP address, port number, email address, URL, etc.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:633
+msgid "Cost is typically 5 or 6 for SSU, and 10 or 11 for NTCP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:637
+msgid ""
+"Expiration is currently unused, always null (all zeroes)).\n"
+"As of release 0.9.3, the expiration is assumed zero and not stored, so "
+"any non-zero expiration\n"
+"will fail in the RouterInfo signature verification.\n"
+"Implementing expiration (or another use for these bytes) will be a "
+"backwards-incompatible change.\n"
+"Routers MUST set this field to all zeros."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:645
+msgid ""
+"The following options, while not required, are standard and expected to "
+"be present in most router addresses:\n"
+"\"host\" (an IPv4 or IPv6 address or host name) and \"port\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:656
+msgid ""
+"Defines all of the data that a router wants to publish for the network to"
+" see. The RouterInfo is one of two "
+"structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of"
+"\n"
+"the contained RouterIdentity.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:661
+msgid ""
+"RouterIdentity followed by the Date, when the entry was published\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:741
+msgid ""
+"The peer_size Integer may be followed by a list of that many router "
+"hashes.\n"
+"This is currently unused. It was intended for a form of restricted "
+"routes, which is unimplemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:746
+msgid ""
+"The signature may be verified using the signing public key of the "
+"router_ident."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:750
+#, python-format
+msgid ""
+"See the network database page\n"
+"for standard options that are expected to be present in all router infos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:760
+#, python-format
+msgid ""
+"Defined in the Tunnel Message "
+"Specification.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:2
+msgid "Configuration File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:7
+msgid ""
+"This page provides a general specification of I2P configuration files,\n"
+"used by the router and various applications.\n"
+"It also gives an overview of the information contained in the various "
+"files,\n"
+"and links to detailed documentation where available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:15
+msgid "General Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:16
+#, python-format
+msgid ""
+"An I2P configuration file is formatted as specified in\n"
+"Java Properties\n"
+"with the following exceptions:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:22
+msgid "Encoding must be UTF-8"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:23
+msgid ""
+"Does not use or recognize any escapes, including '\\', so lines may not "
+"be continued"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:24
+msgid "'#' or ';' starts a comment, but '!' does not"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:25
+msgid ""
+"'#' starts a comment in any position but ';' must be in column 1 to start"
+" a comment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:26
+msgid "Leading and trailing whitespace is not trimmed on keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:27
+msgid "Leading and trailing whitespace is trimmed on values"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:28
+msgid "'=' is the only key-termination character (not ':' or whitespace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:29
+msgid ""
+"Lines without '=' are ignored. It does not store the key with a value of "
+"\"\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:30
+msgid ""
+"As there are no escapes, keys may not contain '#', '=', or '\n"
+"', or start with ';'"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:31
+msgid ""
+"As there are no escapes, values may not contain '#' or '\n"
+"', or start or end with '\r"
+"' or whitespace"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:34
+msgid ""
+"The file need not be sorted, but most applications do sort by key when\n"
+"writing to the file, for ease of reading and manual editing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:39
+#, python-format
+msgid ""
+"Reads and writes are implemented in\n"
+"DataHelper loadProps() and storeProps().\n"
+"Note that the file format is significantly different than the\n"
+"serialized format for I2P protocols specified in\n"
+"Mapping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:48
+msgid "Core library and router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:50
+msgid "Clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:51
+msgid "Configured via /configclients in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:55
+msgid "Logger"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:56
+msgid "Configured via /configlogging in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:60
+msgid "Individual Plugin"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:61
+#, python-format
+msgid "See the plugin specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:66
+msgid "Enable/disable for each installed plugin."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:70
+msgid "Router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:71
+msgid "Configured via /configadvanced in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:75
+msgid "Applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:78
+msgid "See documentation in SusiDNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:83
+msgid "Configured via the application gui."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:88
+msgid "Configured via the /i2ptunnel application in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:92
+msgid "Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:93
+msgid "The router console uses the router.config file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:98
+msgid "See post on zzz.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:2
+msgid "Datagram Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:6
+msgid "See the Datagrams page for an overview of the Datagrams API."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:12
+msgid "Non-Repliable Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:13
+msgid ""
+"Non-repliable datagrams have no 'from' address and are not authenticated."
+"\n"
+"They are also called \"raw\" datagrams.\n"
+"Strictly speaking, they are not \"datagrams\" at all, they are just raw "
+"data.\n"
+"They are not handled by the datagram API.\n"
+"However, SAM and the I2PTunnel classes support \"raw datagrams\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:21
+msgid "Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:31
+#, python-format
+msgid ""
+"The practical length is limited by lower layers of protocols - the\n"
+"tunnel message spec\n"
+"limits messages to about 61.2 KB and the\n"
+"transports\n"
+"currently limit messages to about 32 KB, although this may be raised in "
+"the future."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:40
+msgid "Repliable Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:41
+msgid ""
+"Repliable datagrams contain a 'from' address and a signature. These add "
+"427 bytes of overhead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:91
+#, python-format
+msgid ""
+"The practical length is limited by lower layers of protocols - the\n"
+"transports\n"
+"currently limit messages to about 32 KB, so the data length here is "
+"limited to about\n"
+"31.5 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:97
+msgid "See important notes above about the reliability of large datagrams."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:2
+msgid "GeoIP File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:8
+msgid ""
+"This page specifies the format of the various GeoIP files,\n"
+"used by the router to look up a country for an IP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:14
+msgid "Country Name (countries.txt) Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:15
+msgid ""
+"This format is easily generated from data files available from many "
+"public sources.\n"
+"For example:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:33
+msgid "IPv4 (geoip.txt) Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:34
+msgid ""
+"This format is borrowed from Tor and is easily generated from data files "
+"available from many public sources.\n"
+"For example:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:54
+msgid "IPv6 (geoipv6.dat.gz) Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:55
+msgid ""
+"This is a compressed binary format designed for I2P.\n"
+"The file is gzipped. Ungzipped format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:71
+msgid "NOTES:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:2
+msgid "Streaming Library Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:6
+msgid "See the Streaming page for an overview of the Streaming Library."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:11
+msgid "Packet Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:12
+msgid "The format of a single packet in the streaming protocol is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:35
+msgid "Length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:83
+msgid "Flags and Option Data Fields"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:84
+msgid ""
+"The flags field above specifies some metadata about the packet, and in\n"
+"turn may require certain additional data to be included.  The flags are\n"
+"as follows. Any data structures specified must be added to the options "
+"area\n"
+"in the given order."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:2
+msgid "I2P Software Update Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:7
+msgid ""
+"I2P uses a simple, yet secure, system for automated software update.\n"
+"The router console periodically pulls a news file from a configurable I2P"
+" URL.\n"
+"There is a hardcoded backup URL pointing to the project website, in case\n"
+"the default project news host goes down."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:14
+msgid ""
+"The contents of the news file are displayed on the home page of the "
+"router console.\n"
+"In addition, the news file contains the most recent version number of the"
+" software.\n"
+"If the version is higher than the router's version number, it will\n"
+"display an indication to the user that an update is available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:21
+msgid ""
+"The router may optionally download, or download and install, the new "
+"version\n"
+"if configured to do so."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:26
+msgid "News File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:27
+msgid "The news.xml file may contain the following elements:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:35
+msgid ""
+"Parameters in the i2p.release entry are as follows.\n"
+"All keys are case-insensitive. All values must be enclosed in double "
+"quotes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:73
+msgid ""
+"The elements may be included inside XML comments to prevent "
+"interpretation by browsers.\n"
+"The i2p.release element and version are required. All others are "
+"optional.\n"
+"NOTE: Due to parser limitations an entire element must be on a single "
+"line."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:80
+msgid "Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:81
+msgid ""
+"As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n"
+"use the \"su3\" file format specified below.\n"
+"Approved release signers will use 4096-bit RSA keys.\n"
+"The X.509 public key certificates for these signers are distributed in "
+"the router installation packages.\n"
+"The updates may contain certificates for new, approved signers, and/or "
+"contain\n"
+"a list of certificates to delete for revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:91
+msgid "Old Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:92
+msgid "This format is obsolte as of release 0.9.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:95
+msgid ""
+"The signed update file, traditionally named i2pupdate.sud,\n"
+"is simply a zip file with a prepended 56 byte header.\n"
+"The header contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:101
+#, python-format
+msgid ""
+"A 40-byte DSA "
+"signature"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:104
+msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:109
+#, python-format
+msgid ""
+"The signature covers only the zip archive - not the prepended version.\n"
+"The signature must match one of the DSA public keys "
+"configured into the router,\n"
+"which has a hardcoded default list of keys of the current project release"
+" managers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:115
+msgid ""
+"For version comparison purposes, version fields contain [0-9]*, field "
+"separators are\n"
+"'-', '_', and '.', and all other characters are ignored."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:120
+msgid ""
+"As of version 0.8.8, the version must also be specified as a zip file "
+"comment in UTF-8,\n"
+"without the trailing zeroes.\n"
+"The updating router verifes that the version in the header (not covered "
+"by the signature)\n"
+"matches the version in the zip file comment, which is covered by the "
+"signature.\n"
+"This prevents spoofing of the version number in the header."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:128
+msgid "Download and Installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:129
+msgid ""
+"The router first downloads the header of the update file from one in a "
+"configurable list of I2P URLs,\n"
+"using the built-in HTTP client and proxy,\n"
+"and checks that the version is newer.\n"
+"This prevents the problem of update hosts that do not have the latest "
+"file.\n"
+"The router then downloads the full update file.\n"
+"The router verifies that the update file version is newer before "
+"installation.\n"
+"It also, of course, verifies the signature, and\n"
+"verifes that the zip file comment matches the header version, as "
+"explained above."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:140
+msgid "The zip file is extracted in the base $I2P installation directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:144
+msgid ""
+"As of release 0.7.12, the router supports Pack200 decompression.\n"
+"Files inside the zip archive with a .jar.pack or .war.pack suffix\n"
+"are transparently decompressed to a .jar or .war file.\n"
+"Update files containing .pack files are traditionally named with a '.su2'"
+" suffix.\n"
+"Pack200 shrinks the update files by about 60%."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:152
+msgid ""
+"As of release 0.8.7, the router will delete the libjbigi.so and "
+"libjcpuid.so files\n"
+"if the zip archive contains a lib/jbigi.jar file, so that the new files "
+"will\n"
+"be extracted from jbigi.jar."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:158
+msgid ""
+"As of release 0.8.12, if the zip archive contains a file deletelist.txt, "
+"the router will\n"
+"delete the files listed there. The format is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:163
+msgid "One file name per line"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:164
+msgid ""
+"All file names are relative to the installation directory; no absolute "
+"file names allowed, no files starting with \"..\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:165
+msgid "Comments start with '#'"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:168
+msgid "The router will then delete the deletelist.txt file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:173
+msgid "New \"su3\" Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:175
+msgid ""
+"This specification is used for router updates and reseed data as of "
+"release 0.9.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:179
+msgid "Issues with the previous .sud/.su2 format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:181
+msgid "No magic number or flags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:184
+msgid "No way to specify compression, pack200 or not, or signing algo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:187
+msgid ""
+"Version is not covered by signature, so it is enforced by requiring it\n"
+"to be in the zip file comment (for router files) or in the plugin.config\n"
+"file (for plugins)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:192
+msgid "Signer not specified so verifier must try all known keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:195
+msgid "Signature-before-data format requires two passes to generate file"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:201
+msgid "Goals:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:204
+msgid "Fix above problems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:207
+msgid "Migrate to more secure signature algorithm"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:210
+msgid ""
+"Keep version info in same format and offset for compatibility with\n"
+"existing version checkers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:216
+msgid "Specification:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:275
+msgid "All unused fields must be set to 0 for compatibility with future versions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:282
+msgid ""
+"The network will eventually grow too large for update over HTTP.\n"
+"The built-in BitTorrent client, i2psnark, may be used as a distributed "
+"update method.\n"
+"This development effort is ongoing and should be completed by late 2013."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:287
+msgid ""
+"The router update mechanism is part of the web router console.\n"
+"There is currently no provision for updates of an embedded router lacking"
+" the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:2
+msgid "Transport Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:6
+msgid "Transports in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:8
+msgid ""
+"A \"transport\" in I2P is a method for direct, point-to-point "
+"communication\n"
+"between two routers.\n"
+"Transports must provide confidentiality and integrity \n"
+"against external adversaries while authenticating that the router "
+"contacted \n"
+"is the one who should receive a given message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:16
+msgid ""
+"I2P supports multiple transports simultaneously.\n"
+"There are two transports currently implemented:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:21
+#, python-format
+msgid "NTCP, a Java New I/O (NIO) TCP transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:22
+#, python-format
+msgid " SSU, or Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:25
+msgid ""
+"Each provides a \"connection\" paradigm, with authentication,\n"
+"flow control, acknowledgments and retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:31
+msgid "Transport Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:33
+msgid "The transport subsystem in I2P provides the following services:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:37
+#, python-format
+msgid ""
+"Reliable delivery of I2NP messages.\n"
+"Transports support I2NP message delivery ONLY.\n"
+"They are not general-purpose data pipes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:42
+msgid ""
+"Maintain a set of router addresses, one or more for each transport,\n"
+"that the router publishes as its global contact information (the "
+"RouterInfo).\n"
+"Each transport may connect using one of these addresses, which may be\n"
+"IPv4 or (as of version 0.9.8) IPv6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:48
+msgid "Selection of the best transport for each outgoing message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:49
+msgid "Queueing of outbound messages by priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:50
+msgid ""
+"Bandwidth limiting, both outbound and inbound, according to router "
+"configuration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:51
+msgid "Setup and teardown of transport connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:52
+msgid "Encryption of point-to-point communications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:53
+msgid ""
+"Maintenance of connection limits for each transport, implementation of "
+"various thresholds for these limits,\n"
+"and communication of threshold status to the router so it may make "
+"operational changes based on the status"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:57
+msgid "Firewall port opening using UPnP (Universal Plug and Play)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:58
+msgid "Cooperative NAT/Firewall traversal"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:59
+msgid ""
+"Local IP detection by various methods, including UPnP, inspection of "
+"incoming connections, and enumeration of network devices"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:60
+msgid ""
+"Coordination of firewall status and local IP, and changes to either, "
+"among the transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:61
+#: i2p2www/pages/site/docs/transport/ssu.html:33
+msgid ""
+"Communication of firewall status and local IP, and changes to either, to "
+"the router and the user interface"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:62
+msgid ""
+"Determination of a consensus clock, which is used to periodically update "
+"the router's clock, as a backup for NTP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:63
+msgid ""
+"Maintenance of status for each peer, including whether it is connected, "
+"whether it was recently connected,\n"
+"and whether it was reachable in the last attempt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:67
+msgid "Qualification of valid IP addresses according to a local rule set"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:68
+msgid ""
+"Honoring the automated and manual lists of banned peers maintained by the"
+" router,\n"
+"and refusing outbound and inbound connections to those peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:75
+msgid "Transport Addresses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:77
+msgid ""
+"The transport subsystem maintains a set of router addresses, each of "
+"which lists a transport method, IP, and port.\n"
+"These addresses constitute the advertised contact points, and are "
+"published by the router to the network database.\n"
+"Addresses may also contain an arbitrary set of additional options."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:83
+msgid "Typical scenarios are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:85
+msgid ""
+"A router has no published addresses, so it is considered \"hidden\" and "
+"cannot receive incoming connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:86
+#, python-format
+msgid ""
+"A router is firewalled, and therefore publishes an SSU address which "
+"contains a list of cooperating\n"
+"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:90
+msgid ""
+"A router is not firewalled or its NAT ports  are open; it publishes both "
+"NTCP and SSU addresses containing\n"
+"directly-accessible IP and ports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:96
+msgid "Transport Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:98
+#, python-format
+msgid ""
+"The transport system delivers I2NP messages "
+"only. The transport selected for any message is\n"
+"independent of the upper-layer protocols and contents (router or client "
+"messages, whether an external application was using\n"
+"TCP or UDP to connect to I2P, whether the upper layer was using\n"
+"the streaming library\n"
+"streaming\n"
+"or\n"
+"datagrams,\n"
+"datagrams\n"
+"etc.)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:112
+msgid ""
+"For each outgoing message, the transport system solicits \"bids\" from "
+"each transport.\n"
+"The transport bidding the lowest (best) value wins the bid and receives "
+"the message for delivery.\n"
+"A transport may refuse to bid."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:118
+msgid "Whether a transport bids, and with what value, depend on numerous factors:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:122
+msgid "Configuration of transport preferences"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:123
+msgid "Whether the transport is already connected to the peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:124
+msgid ""
+"The number of current connections compared to various connection limit "
+"thresholds"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:125
+msgid "Whether recent connection attempts to the peer have failed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:126
+msgid ""
+"The size of the message, as different transports have different size "
+"limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:127
+msgid ""
+"Whether the peer can accept incoming connections for that transport, as "
+"advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:128
+msgid "Whether the connection would be indirect (requiring introducers) or direct"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:129
+msgid "The peer's transport preference, as advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:132
+msgid ""
+"In general, the bid values are selected so that two routers are only "
+"connected by a single transport\n"
+"at any one time. However, this is not a requirement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:139
+msgid "New Transports and Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:141
+msgid "Additional transports may be developed, including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:146
+msgid "A TLS/SSH look-alike transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:147
+msgid ""
+"An \"indirect\" transport for routers that are not reachable by all other"
+" routers (one form of \"restricted routes\")"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:150
+msgid ""
+"Work continues on adjusting default connection limits for each transport."
+"\n"
+"I2P is designed as a \"mesh network\", where it is assumed that any "
+"router can connect to any other router.\n"
+"This assumption may be broken by routers that have exceeded their "
+"connection limits, and by\n"
+"routers that are behind restrictive state firewalls (restricted routes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:157
+msgid ""
+"The current connection limits are higher for SSU than for NTCP, based on "
+"the assumption that\n"
+"the memory requirements for an NTCP connection are higher than that for "
+"SSU.\n"
+"However, as NTCP buffers are partially in the kernel and SSU buffers are "
+"on the Java heap,\n"
+"that assumption is difficult to verify."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:164
+#, python-format
+msgid ""
+"Analyze Breaking and Improving Protocol "
+"Obfuscation\n"
+"and see how transport-layer padding may improve things."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:6
+msgid "NTCP (NIO-based TCP)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:8
+#, python-format
+msgid ""
+"NTCP is one of two transports currently "
+"implemented in I2P.\n"
+"The other is SSU.\n"
+"NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n"
+"Java NIO (new I/O) does not suffer from the 1 thread per connection "
+"issues of the old TCP transport.\n"
+"NTCP-over-IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:16
+msgid ""
+"By default, NTCP uses the IP/Port\n"
+"auto-detected by SSU. When enabled on config.jsp,\n"
+"SSU will notify/restart NTCP when the external address changes\n"
+"or when the firewall status changes.\n"
+"Now you can enable inbound TCP without a static IP or dyndns service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:24
+msgid ""
+"The NTCP code within I2P is relatively lightweight (1/4 the size of the "
+"SSU code)\n"
+"because it uses the underlying Java TCP transport for reliable delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:30
+msgid "NTCP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:32
+msgid "Standard Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:33
+msgid ""
+"After establishment,\n"
+"the NTCP transport sends individual I2NP messages, with a simple "
+"checksum.\n"
+"The unencrypted message is encoded as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:43
+msgid ""
+"The data is then AES/256/CBC encrypted. The session key for the "
+"encryption\n"
+"is negotiated during establishment (using Diffie-Hellman 2048 bit).\n"
+"The establishment between two routers is implemented in the "
+"EstablishState class\n"
+"and detailed below.\n"
+"The IV for AES/256/CBC encryption is the last 16 bytes of the previous "
+"encrypted message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:51
+msgid ""
+"0-15 bytes of padding are required to bring the total message length\n"
+"(including the six size and checksum bytes) to a multiple of 16.\n"
+"The maximum message size is currently 16 KB.\n"
+"Therefore the maximum data size is currently 16 KB - 6, or 16378 bytes.\n"
+"The minimum data size is 1."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:59
+msgid "Time Sync Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:60
+msgid ""
+"One special case is a metadata message where the sizeof(data) is 0.  In\n"
+"that case, the unencrypted message is encoded as:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:71
+msgid ""
+"Total length: 16 bytes. The time sync message is sent at approximately 15"
+" minute intervals.\n"
+"The message is encrypted just as standard messages are."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:77
+msgid "Checksums"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:78
+#, python-format
+msgid ""
+"The standard and time sync messages use the Adler-32 checksum\n"
+"as defined in the ZLIB Specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:84
+msgid "Establishment Sequence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:85
+msgid ""
+"In the establish state, there is a 4-phase message sequence to exchange "
+"DH keys and signatures.\n"
+"In the first two messages there is a 2048-bit Diffie Hellman exchange.\n"
+"Then, DSA signatures of the critical data are exchanged to confirm the "
+"connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:99
+msgid "Legend:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:100
+msgid "256 byte DH public keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:104
+msgid "timestamps (4 bytes, seconds since epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:105
+msgid "32 byte Session key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:106
+msgid "2 byte size of Alice identity to follow"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:109
+msgid "DH Key Exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:110
+#, python-format
+msgid ""
+"The initial 2048-bit DH key exchange\n"
+"uses the same shared prime (p) and generator (g) as that used for I2P's\n"
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:116
+msgid ""
+"The DH key exchange consists of a number of steps, displayed below.\n"
+"The mapping between these steps and the messages sent between I2P "
+"routers,\n"
+"is marked in bold."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:122
+msgid ""
+"Alice generates a secret integer x. She then calculates X = g^x mod"
+" p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:123
+msgid "Alice sends X to Bob (Message 1)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:124
+msgid ""
+"Bob generates a secret integer y. He then calculates Y = g^y mod "
+"p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:125
+msgid "Bob sends Y to Alice.(Message 2)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:126
+msgid "Alice can now compute sessionKey = Y^x mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:127
+msgid "Bob can now compute sessionKey = X^y mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:128
+msgid ""
+"Both Alice and Bob now have a shared key sessionKey = g^(x*y) mod "
+"p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:130
+#, python-format
+msgid ""
+"The sessionKey is then used to exchange identities in Message 3 "
+"and Message 4.\n"
+"The exponent (x and y) length for the DH exchange is documented on the\n"
+"cryptography page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:136
+msgid "Message 1 (Session Request)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:137
+#, python-format
+msgid ""
+"This is the DH request. Alice already has Bob's\n"
+"Router "
+"Identity,\n"
+"IP address, and port, as contained in his\n"
+"Router Info,\n"
+"which was published to the\n"
+"network database.\n"
+"Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:150
+#: i2p2www/pages/site/docs/transport/ntcp.html:193
+#: i2p2www/pages/site/docs/transport/ntcp.html:273
+#: i2p2www/pages/site/docs/transport/ntcp.html:356
+msgid "Size:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:152
+msgid "Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:170
+msgid "256 byte X from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:172
+#, python-format
+msgid ""
+"SHA256 Hash(X) xored with SHA256 Hash(Bob's Router Identity)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:179
+#: i2p2www/pages/site/docs/transport/ntcp.html:260
+#: i2p2www/pages/site/docs/transport/ntcp.html:337
+msgid "Notes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:180
+msgid ""
+"Bob verifies HXxorHI using his own router hash. If it does not verify,\n"
+"Alice has contacted the wrong router, and Bob drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:186
+msgid "Message 2 (Session Created)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:187
+msgid "This is the DH reply. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:195
+#: i2p2www/pages/site/docs/transport/ntcp.html:275
+#: i2p2www/pages/site/docs/transport/ntcp.html:358
+msgid "Unencrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:217
+#: i2p2www/pages/site/docs/transport/ntcp.html:251
+msgid "256 byte Y from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:219
+msgid "SHA256 Hash(X concatenated with Y)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:222
+#: i2p2www/pages/site/docs/transport/ntcp.html:307
+msgid "4 byte timestamp (seconds since the epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:224
+msgid "12 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:229
+#: i2p2www/pages/site/docs/transport/ntcp.html:319
+#: i2p2www/pages/site/docs/transport/ntcp.html:386
+msgid "Encrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:253
+#, python-format
+msgid ""
+"48 bytes AES encrypted using the DH "
+"session key and\n"
+"                  the last 16 bytes of Y as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:261
+msgid ""
+"Alice may drop the connection if the clock skew with Bob is too high as "
+"calculated using tsB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:266
+msgid "Message 3 (Session Confirm A)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:267
+msgid ""
+"This contains Alice's router identity, and a DSA signature of the "
+"critical data. Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:301
+msgid "2 byte size of Alice's router identity to follow (should always be 387)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:303
+#, python-format
+msgid ""
+"Alice's 387 byte Router Identity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:309
+msgid "15 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:311
+#, python-format
+msgid ""
+"the 40 byte DSA "
+"signature of the following concatenated data:\n"
+"             X, Y, Bob's Router Identity, "
+"tsA, tsB.\n"
+"             Alice signs it with the private signing "
+"key associated with the public signing "
+"key in her Router Identity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:329
+#, python-format
+msgid ""
+"448 bytes AES encrypted using the DH"
+" session key and\n"
+"                  the last 16 bytes of HXxorHI (i.e., the last 16 bytes "
+"of message #1) as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:339
+msgid "Bob verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:342
+msgid ""
+"Bob may drop the connection if the clock skew with Alice is too high as "
+"calculated using tsA."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:349
+msgid "Message 4 (Session Confirm B)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:350
+msgid "This is a DSA signature of the critical data. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:375
+#, python-format
+msgid ""
+"the 40 byte DSA "
+"signature of the following concatenated data:\n"
+"             X, Y, Alice's Router Identity, "
+"tsA, tsB.\n"
+"             Bob signs it with the private signing "
+"key associated with the public signing "
+"key in his Router Identity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:381
+msgid "8 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:396
+#, python-format
+msgid ""
+"48 bytes AES encrypted using the DH "
+"session key and\n"
+"                  the last 16 bytes of the encrypted contents of message "
+"#2 as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:404
+msgid "Alice verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:411
+msgid "After Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:412
+msgid ""
+"The connection is established, and standard or time sync messages may be "
+"exchanged.\n"
+"All subsequent messages are AES encrypted using the negotiated DH session"
+" key.\n"
+"Alice will use the last 16 bytes of the encrypted contents of message #3 "
+"as the next IV.\n"
+"Bob will use the last 16 bytes of the encrypted contents of message #4 as"
+" the next IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:421
+msgid "Check Connection Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:422
+msgid ""
+"Alternately, when Bob receives a connection, it could be a\n"
+"check connection (perhaps prompted by Bob asking for someone\n"
+"to verify his listener).\n"
+"Check Connection is not currently used.\n"
+"However, for the record, check connections are formatted as follows.\n"
+"A check info connection will receive 256 bytes containing:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:431
+msgid "32 bytes of uninterpreted, ignored data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:432
+msgid "1 byte size"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:433
+msgid ""
+"that many bytes making up the local router's IP address (as reached by "
+"the remote side)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:434
+msgid "2 byte port number that the local router was reached on"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:435
+msgid ""
+"4 byte i2p network time as known by the remote side (seconds since the "
+"epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:436
+msgid "uninterpreted padding data, up to byte 223"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:437
+msgid ""
+"xor of the local router's identity hash and the SHA256 of bytes 32 "
+"through bytes 223"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:441
+msgid "Discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:442
+#, python-format
+msgid "Now on the NTCP Discussion Page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:448
+msgid "The maximum message size should be increased to approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:452
+msgid ""
+"A set of fixed packet sizes may be appropriate to further hide the data \n"
+"fragmentation to external adversaries, but the tunnel, garlic, and end to"
+" \n"
+"end padding should be sufficient for most needs until then.\n"
+"However, there is currently no provision for padding beyond the next "
+"16-byte boundary,\n"
+"to create a limited number of message sizes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:460
+msgid ""
+"Memory utilization (including that of the kernel) for NTCP should be "
+"compared to that for SSU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:464
+msgid ""
+"Can the establishment messages be randomly padded somehow, to frustrate\n"
+"identification of I2P traffic based on initial packet sizes?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:469
+msgid "Review and possibly disable 'check connection'"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:2
+msgid "SSU Transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:6
+msgid "Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:9
+#, python-format
+msgid ""
+"SSU (also called \"UDP\" in much of the I2P documentation and user "
+"interfaces)\n"
+"is one of two transports currently "
+"implemented in I2P.\n"
+"The other is NTCP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:15
+msgid ""
+"SSU is the newer of the two transports,\n"
+"introduced in I2P release 0.6.\n"
+"In a standard I2P installation, the router uses both NTCP and SSU for "
+"outbound connections.\n"
+"SSU-over-IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:22
+msgid "SSU Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:24
+msgid ""
+"Like the NTCP transport, SSU provides reliable, encrypted, connection-"
+"oriented, point-to-point data transport.\n"
+"Unique to SSU, it also provides IP detection and NAT traversal services, "
+"including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:30
+msgid ""
+"Cooperative NAT/Firewall traversal using introducers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:31
+msgid ""
+"Local IP detection by inspection of incoming packets and peer testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:32
+msgid ""
+"Communication of firewall status and local IP, and changes to either to "
+"NTCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:37
+msgid "Protocol Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:39
+msgid "Congestion control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:41
+msgid ""
+"SSU's need for only semireliable delivery, TCP-friendly operation,\n"
+"and the capacity for high throughput allows a great deal of latitude in\n"
+"congestion control.  The congestion control algorithm outlined below is\n"
+"meant to be both efficient in bandwidth as well as simple to implement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:48
+msgid ""
+"Packets are scheduled according to the router's policy, taking care\n"
+"not to exceed the router's outbound capacity or to exceed the measured \n"
+"capacity of the remote peer.  The measured capacity operates along the\n"
+"lines of TCP's slow start and congestion avoidance, with additive "
+"increases\n"
+"to the sending capacity and multiplicative decreases in face of "
+"congestion.\n"
+"Unlike for TCP, routers may give up on some messages after\n"
+"a given period or number of retransmissions while continuing to transmit"
+" \n"
+"other messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:59
+msgid ""
+"The congestion detection techniques vary from TCP as well, since each \n"
+"message has its own unique and nonsequential identifier, and each message"
+"\n"
+"has a limited size - at most, 32KB.  To efficiently transmit this "
+"feedback\n"
+"to the sender, the receiver periodically includes a list of fully ACKed \n"
+"message identifiers and may also include bitfields for partially received"
+"\n"
+"messages, where each bit represents the reception of a fragment.  If \n"
+"duplicate fragments arrive, the message should be ACKed again, or if the\n"
+"message has still not been fully received, the bitfield should be \n"
+"retransmitted with any new updates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:71
+msgid ""
+"The current implementation does not pad the packets to\n"
+"any particular size, but instead just places a single message fragment "
+"into\n"
+"a packet and sends it off (careful not to exceed the MTU)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:78
+msgid ""
+"As of router version 0.8.12,\n"
+"two MTU values are used for IPv4: 620 and 1484.\n"
+"The MTU value is adjusted based on the percentage of packets that are "
+"retransmitted."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:84
+msgid ""
+"For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
+"the payload portion after the 28-byte IP/UDP header is a multiple of\n"
+"16 bytes, for encryption purposes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:90
+msgid ""
+"For the small MTU value, it is desirable to pack a 2646-byte\n"
+"Variable Tunnel Build Message efficiently into multiple packets;\n"
+"with a 620-byte MTU, it fits into 5 packets with nicely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:96
+msgid ""
+"Based on measurements, 1492 fits nearly all reasonably small I2NP "
+"messages\n"
+"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going "
+"to fit\n"
+"into a live network MTU anyway)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:102
+msgid ""
+"The MTU values were 608 and 1492 for releases 0.8.9 - 0.8.11.\n"
+"The large MTU was 1350 prior to release 0.8.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:107
+msgid ""
+"The maximum receive packet size\n"
+"is 1571 bytes as of release 0.8.12.\n"
+"For releases 0.8.9 - 0.8.11 it was 1535 bytes.\n"
+"Prior to release 0.8.9 it was 2048 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:114
+msgid ""
+"As of release 0.9.2, if a router's network interface MTU is less than "
+"1484,\n"
+"it will publish that in the network database, and other routers should\n"
+"honor that when a connection is established."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:120
+msgid ""
+"For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes,\n"
+"so we use an MTU where (MTN % 16 == 0), which is true for 1280.\n"
+"The maximum IPv6 MTU is 1472."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:126
+msgid "Message Size Limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:127
+msgid ""
+"While the maximum message size is nominally 32KB, the practical\n"
+"limit differs. The protocol limits the number of fragments to 7 bits, or "
+"128.\n"
+"The current implementation, however, limits each message to a maximum of "
+"64 fragments,\n"
+"which is sufficient for 64 * 534 = 33.3 KB when using the 608 MTU.\n"
+"Due to overhead for bundled LeaseSets and session keys, the practical "
+"limit\n"
+"at the application level is about 6KB lower, or about 26KB.\n"
+"Further work is necessary to raise the UDP transport limit above 32KB.\n"
+"For connections using the larger MTU, larger messages are possible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:138
+msgid "Keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:140
+msgid ""
+"All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n"
+"The MAC and session keys are negotiated as part of the DH exchange, used\n"
+"for the HMAC and encryption, respectively.  Prior to the DH exchange, \n"
+"the publicly knowable introKey is used for the MAC and encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:147
+msgid ""
+"When using the introKey, both the initial message and any subsequent\n"
+"reply use the introKey of the responder (Bob) - the responder does \n"
+"not need to know the introKey of the requester (Alice).  The DSA \n"
+"signing key used by Bob should already be known to Alice when she \n"
+"contacts him, though Alice's DSA key may not already be known by \n"
+"Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:156
+msgid ""
+"Upon receiving a message, the receiver checks the \"from\" IP address and"
+" port\n"
+"with all established sessions - if there are matches,\n"
+"that session's MAC keys are tested in the HMAC.  If none\n"
+"of those verify or if there are no matching IP addresses, the \n"
+"receiver tries their introKey in the MAC.  If that does not verify,\n"
+"the packet is dropped.  If it does verify, it is interpreted \n"
+"according to the message type, though if the receiver is overloaded,\n"
+"it may be dropped anyway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:167
+msgid ""
+"If Alice and Bob have an established session, but Alice loses the \n"
+"keys for some reason and she wants to contact Bob, she may at any \n"
+"time simply establish a new session through the SessionRequest and\n"
+"related messages.  If Bob has lost the key but Alice does not know\n"
+"that, she will first attempt to prod him to reply, by sending a \n"
+"DataMessage with the wantReply flag set, and if Bob continually \n"
+"fails to reply, she will assume the key is lost and reestablish a \n"
+"new one."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:178
+#, python-format
+msgid ""
+"For the DH key agreement,\n"
+"RFC3526 2048bit\n"
+"MODP group (#14) is used:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:188
+#, python-format
+msgid ""
+"These are the same p and g used for I2P's\n"
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:193
+msgid "Replay prevention"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:195
+msgid ""
+"Replay prevention at the SSU layer occurs by rejecting packets \n"
+"with exceedingly old timestamps or those which reuse an IV.  To\n"
+"detect duplicate IVs, a sequence of Bloom filters are employed to\n"
+"\"decay\" periodically so that only recently added IVs are detected."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:202
+msgid ""
+"The messageIds used in DataMessages are defined at layers above\n"
+"the SSU transport and are passed through transparently.  These IDs\n"
+"are not in any particular order - in fact, they are likely to be\n"
+"entirely random.  The SSU layer makes no attempt at messageId \n"
+"replay prevention - higher layers should take that into account."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:210
+msgid "Addressing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:212
+msgid ""
+"To contact an SSU peer, one of two sets of information is necessary:\n"
+"a direct address, for when the peer is publicly reachable, or an\n"
+"indirect address, for using a third party to introduce the peer.\n"
+"There is no restriction on the number of addresses a peer may have."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:224
+msgid ""
+"Each of the addresses may also expose a series of options - special\n"
+"capabilities of that particular peer.  For a list of available\n"
+"capabilities, see below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:230
+#, python-format
+msgid ""
+"The addresses, options, and capabilities are published in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:235
+msgid "Direct Session Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:236
+msgid ""
+"Direct session establishment is used when no third party is required for "
+"NAT traversal.\n"
+"The message sequence is as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:241
+msgid "Connection establishment (direct)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:242
+msgid ""
+"Alice connects directly to Bob.\n"
+"IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:257
+#, python-format
+msgid ""
+"After the SessionConfirmed message is received, Bob sends a small\n"
+"DeliveryStatus message\n"
+"as a confirmation.\n"
+"In this message, the 4-byte message ID is set to a random number, and the"
+"\n"
+"8-byte \"arrival time\" is set to the current network-wide ID, which is 2"
+"\n"
+"(i.e. 0x0000000000000002)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:266
+#, python-format
+msgid ""
+"After the status message is sent, the peers exchange\n"
+"DatabaseStore messages\n"
+"containing their\n"
+"RouterInfos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:274
+msgid ""
+"It does not appear that the type of the status message or its contents "
+"matters.\n"
+"It was originally added becasue the DatabaseStore message was delayed\n"
+"several seconds; since the store is now sent immediately, perhaps\n"
+"the status message can be eliminated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:283
+msgid ""
+"Introduction keys are delivered through an external channel \n"
+"(the network database, where they are identical to the router Hash for "
+"now)\n"
+"and must be used when establishing a session key.  For the indirect\n"
+"address, the peer must first contact the relayhost and ask them for\n"
+"an introduction to the peer known at that relayhost under the given\n"
+"tag.  If possible, the relayhost sends a message to the addressed\n"
+"peer telling them to contact the requesting peer, and also gives \n"
+"the requesting peer the IP and port on which the addressed peer is\n"
+"located.  In addition, the peer establishing the connection must \n"
+"already know the public keys of the peer they are connecting to (but\n"
+"not necessary to any intermediary relay peer)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:297
+msgid ""
+"Indirect session establishment by means of a third party introduction\n"
+"is necessary for efficient NAT traversal.  Charlie, a router behind a\n"
+"NAT or firewall which does not allow unsolicited inbound UDP packets,\n"
+"first contacts a few peers, choosing some to serve as introducers.  Each\n"
+"of these peers (Bob, Bill, Betty, etc) provide Charlie with an "
+"introduction\n"
+"tag - a 4 byte random number - which he then makes available to the "
+"public\n"
+"as methods of contacting him.  Alice, a router who has Charlie's "
+"published\n"
+"contact methods, first sends a RelayRequest packet to one or more of the"
+" \n"
+"introducers, asking each to introduce her to Charlie (offering the \n"
+"introduction tag to identify Charlie).  Bob then forwards a RelayIntro\n"
+"packet to Charlie including Alice's public IP and port number, then sends"
+"\n"
+"Alice back a RelayResponse packet containing Charlie's public IP and port"
+"\n"
+"number.  When Charlie receives the RelayIntro packet, he sends off a "
+"small\n"
+"random packet to Alice's IP and port (poking a hole in his NAT/firewall),"
+"\n"
+"and when Alice receives Bob's RelayResponse packet, she begins a new \n"
+"full direction session establishment with the specified IP and port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:324
+msgid "Connection establishment (indirect using an introducer)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:326
+msgid "Alice first connects to introducer Bob, who relays the request to Charlie."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:344
+msgid ""
+"After the hole punch, the session is established between Alice and "
+"Charlie as in a direct establishment."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:356
+msgid "Peer testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:358
+msgid ""
+"The automation of collaborative reachability testing for peers is\n"
+"enabled by a sequence of PeerTest messages.  With its proper \n"
+"execution, a peer will be able to determine their own reachability\n"
+"and may update its behavior accordingly.  The testing process is \n"
+"quite simple:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:377
+msgid ""
+"Each of the PeerTest messages carry a nonce identifying the\n"
+"test series itself, as initialized by Alice.  If Alice doesn't \n"
+"get a particular message that she expects, she will retransmit\n"
+"accordingly, and based upon the data received or the messages\n"
+"missing, she will know her reachability.  The various end states\n"
+"that may be reached are as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:387
+msgid ""
+"If she doesn't receive a response from Bob, she will retransmit\n"
+"up to a certain number of times, but if no response ever arrives,\n"
+"she will know that her firewall or NAT is somehow misconfigured, \n"
+"rejecting all inbound UDP packets even in direct response to an\n"
+"outbound packet.  Alternately, Bob may be down or unable to get \n"
+"Charlie to reply."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:396
+msgid ""
+"If Alice doesn't receive a PeerTest message with the \n"
+"expected nonce from a third party (Charlie), she will retransmit\n"
+"her initial request to Bob up to a certain number of times, even\n"
+"if she has received Bob's reply already.  If Charlie's first message \n"
+"still doesn't get through but Bob's does, she knows that she is\n"
+"behind a NAT or firewall that is rejecting unsolicited connection\n"
+"attempts and that port forwarding is not operating properly (the\n"
+"IP and port that Bob offered up should be forwarded)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:407
+msgid ""
+"If Alice receives Bob's PeerTest message and both of Charlie's\n"
+"PeerTest messages but the enclosed IP and port numbers in Bob's \n"
+"and Charlie's second messages don't match, she knows that she is \n"
+"behind a symmetric NAT, rewriting all of her outbound packets with\n"
+"different 'from' ports for each peer contacted.  She will need to\n"
+"explicitly forward a port and always have that port exposed for \n"
+"remote connectivity, ignoring further port discovery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:417
+msgid ""
+"If Alice receives Charlie's first message but not his second,\n"
+"she will retransmit her PeerTest message to Charlie up to a \n"
+"certain number of times, but if no response is received she knows\n"
+"that Charlie is either confused or no longer online."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:425
+msgid ""
+"Alice should choose Bob arbitrarily from known peers who seem\n"
+"to be capable of participating in peer tests.  Bob in turn should\n"
+"choose Charlie arbitrarily from peers that he knows who seem to be\n"
+"capable of participating in peer tests and who are on a different\n"
+"IP from both Bob and Alice.  If the first error condition occurs\n"
+"(Alice doesn't get PeerTest messages from Bob), Alice may decide\n"
+"to designate a new peer as Bob and try again with a different nonce."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:435
+msgid ""
+"Alice's introduction key is included in all of the PeerTest \n"
+"messages so that she doesn't need to already have an established\n"
+"session with Bob and so that Charlie can contact her without knowing\n"
+"any additional information.  Alice may go on to establish a session\n"
+"with either Bob or Charlie, but it is not required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:453
+msgid "Transmission window, ACKs and Retransmissions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:454
+#, python-format
+msgid ""
+"The DATA message may contain ACKs of full messages and\n"
+"partial ACKs of individual fragments of a message. See\n"
+"the data message section of\n"
+"the protocol specification page\n"
+"for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:462
+#, python-format
+msgid ""
+"The details of windowing, ACK, and retransmission strategies are not "
+"specified\n"
+"here. See the Java code for the current implementation.\n"
+"During the establishment phase, and for peer testing, routers\n"
+"should implement exponential backoff for retransmission.\n"
+"For an established connection, routers should implement\n"
+"an adjustable transmission window, RTT estimate and timeout, similar to "
+"TCP\n"
+"or streaming.\n"
+"See the code for initial, min and max parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:474
+msgid "Security"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:475
+msgid ""
+"UDP source addresses may, of course, be spoofed.\n"
+"Additionally, the IPs and ports contained inside specific\n"
+"SSU messages (RelayRequest, RelayResponse, RelayIntro, PeerTest)\n"
+"may not be legitimate.\n"
+"Also, certain actions and responses may need to be rate-limited."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:483
+msgid ""
+"The details of validation are not specified\n"
+"here. Implementers should add defenses where appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:489
+msgid "Peer capabilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:493
+msgid ""
+"If the peer address contains the 'B' capability, that means \n"
+"they are willing and able to participate in peer tests as\n"
+"a 'Bob' or 'Charlie'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:499
+msgid ""
+"If the peer address contains the 'C' capability, that means\n"
+"they are willing and able to serve as an introducer - serving\n"
+"as a Bob for an otherwise unreachable Alice."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:508
+msgid ""
+"Analysis of current SSU performance, including assessment of window size "
+"adjustment\n"
+"and other parameters, and adjustment of the protocol implementation to "
+"improve\n"
+"performance, is a topic for future work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:514
+msgid ""
+"The current implementation repeatedly sends acknowledgments for the same "
+"packets,\n"
+"which unnecessarily increases overhead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:519
+msgid ""
+"The default small MTU value of 620 should be analyzed and possibly "
+"increased.\n"
+"The current MTU adjustment strategy should be evaluated.\n"
+"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? "
+"Probably not."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:525
+msgid "The protocol should be extended to exchange MTUs during the setup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:529
+msgid "Rekeying is currently unimplemented and may never be."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:533
+msgid ""
+"The potential use of the 'challenge' fields in RelayIntro and "
+"RelayResponse,\n"
+"and use of the padding field in SessionRequest and SessionCreated, is "
+"undocumented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:538
+msgid ""
+"Instead of a single fragment per packet, a more efficient\n"
+"strategy may be to bundle multiple message fragments into the same "
+"packet,\n"
+"so long as it doesn't exceed the MTU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:544
+msgid ""
+"A set of fixed packet sizes may be appropriate to further hide the data \n"
+"fragmentation to external adversaries, but the tunnel, garlic, and end to"
+" \n"
+"end padding should be sufficient for most needs until then."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:550
+msgid ""
+"Why are introduction keys the same as the router hash, should it be "
+"changed, would there be any benefit?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:554
+msgid "Capacities appear to be unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:558
+msgid ""
+"Signed-on times in SessionCreated and SessionConfirmed appear to be "
+"unused or unverified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:563
+msgid "Implementation Diagram"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:564
+msgid ""
+"This diagram\n"
+"should accurately reflect the current implementation, however there may "
+"be small differences."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:572
+msgid "Now on the SSU specification page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:2
+msgid "Tunnel Implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:3
+msgid "October 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:7
+msgid "This page documents the current tunnel implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:9
+msgid "Tunnel overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:11
+msgid ""
+"Within I2P, messages are passed in one direction through a virtual\n"
+"tunnel of peers, using whatever means are available to pass the \n"
+"message on to the next hop.  Messages arrive at the tunnel's \n"
+"            gateway            , get bundled up and/or fragmented into fixed-size tunnel "
+"messages, \n"
+"and are forwarded on to the next hop in the tunnel, which processes and "
+"verifies\n"
+"the validity of the message and sends it on to the next hop, and so on, "
+"until\n"
+"it reaches the tunnel endpoint.  That endpoint takes the messages\n"
+"bundled up by the gateway and forwards them as instructed - either\n"
+"to another router, to another tunnel on another router, or locally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:23
+msgid ""
+"Tunnels all work the same, but can be segmented into two different\n"
+"groups - inbound tunnels and outbound tunnels.  The inbound tunnels\n"
+"have an untrusted gateway which passes messages down towards the \n"
+"tunnel creator, which serves as the tunnel endpoint.  For outbound \n"
+"tunnels, the tunnel creator serves as the gateway, passing messages\n"
+"out to the remote endpoint."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:32
+msgid ""
+"The tunnel's creator selects exactly which peers will participate\n"
+"in the tunnel, and provides each with the necessary configuration\n"
+"data.  They may have any number of hops.\n"
+"It is the intent to make\n"
+"it hard for either participants or third parties to determine the length "
+"of \n"
+"a tunnel, or even for colluding participants to determine whether they "
+"are a\n"
+"part of the same tunnel at all (barring the situation where colluding "
+"peers are\n"
+"next to each other in the tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:43
+msgid ""
+"In practice, a series of tunnel pools are used for different\n"
+"purposes - each local client destination has its own set of inbound\n"
+"tunnels and outbound tunnels, configured to meet its anonymity and\n"
+"performance needs.  In addition, the router itself maintains a series\n"
+"of pools for participating in the network database and for managing\n"
+"the tunnels themselves."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:52
+msgid ""
+"I2P is an inherently packet switched network, even with these \n"
+"tunnels, allowing it to take advantage of multiple tunnels running \n"
+"in parallel, increasing resilience and balancing load.  Outside of\n"
+"the core I2P layer, there is an optional end to end streaming library \n"
+"available for client applications, exposing TCP-esque operation,\n"
+"including message reordering, retransmission, congestion control, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:61
+#, python-format
+msgid ""
+"An overview of I2P tunnel terminology is\n"
+"on the tunnel overview page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:66
+msgid "Tunnel Operation (Message Processing)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:69
+#, python-format
+msgid ""
+"After a tunnel is built, I2NP messages are "
+"processed and passed through it.\n"
+"Tunnel operation has four distinct processes, taken on by various \n"
+"peers in the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:75
+msgid ""
+"First, the tunnel gateway accumulates a number\n"
+"of I2NP messages and preprocesses them into tunnel messages for\n"
+"delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:80
+msgid ""
+"Next, that gateway encrypts that preprocessed data, then\n"
+"forwards it to the first hop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:84
+msgid ""
+"That peer, and subsequent tunnel \n"
+"participants, unwrap a layer of the encryption, verifying that it isn't\n"
+"a duplicate, then forward it on to the next peer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:89
+msgid ""
+"Eventually, the tunnel messages arrive at the endpoint where the I2NP "
+"messages\n"
+"originally bundled by the gateway are reassembled and forwarded on as \n"
+"requested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:96
+msgid ""
+"Intermediate tunnel participants do not know whether they are in an\n"
+"inbound or an outbound tunnel; they always \"encrypt\" for the next hop.\n"
+"Therefore, we take advantage of symmetric AES encryption\n"
+"to \"decrypt\" at the outbound tunnel gateway,\n"
+"so that the plaintext is revealed at the outbound endpoint."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:110
+msgid "Role"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:111
+msgid "Preprocessing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:112
+msgid "Encryption Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:113
+msgid "Postprocessing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:117
+msgid "Outbound Gateway (Creator)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:118
+#: i2p2www/pages/site/docs/tunnels/implementation.html:141
+msgid "Fragment, Batch, and Pad"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:119
+msgid "Iteratively encrypt (using decryption operations)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:120
+#: i2p2www/pages/site/docs/tunnels/implementation.html:127
+#: i2p2www/pages/site/docs/tunnels/implementation.html:143
+#: i2p2www/pages/site/docs/tunnels/implementation.html:150
+msgid "Forward to next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:124
+#: i2p2www/pages/site/docs/tunnels/implementation.html:147
+msgid "Participant"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:126
+msgid "Decrypt (using an encryption operation)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:133
+msgid "Decrypt (using an encryption operation) to reveal plaintext tunnel message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:134
+msgid "Reassemble Fragments, Forward as instructed to Inbound Gateway or Router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:142
+#: i2p2www/pages/site/docs/tunnels/implementation.html:149
+msgid "Encrypt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:154
+msgid "Inbound Endpoint (Creator)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:156
+msgid "Iteratively decrypt to reveal plaintext tunnel message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:157
+msgid "Reassemble Fragments, Receive data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:163
+msgid "Gateway Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:164
+msgid "Message Preprocessing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:166
+#, python-format
+msgid ""
+"A tunnel gateway's function is to fragment and pack\n"
+"I2NP messages into fixed-size\n"
+"tunnel messages\n"
+"and encrypt the tunnel messages.\n"
+"Tunnel messages contain the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:174
+msgid "A 4 byte Tunnel ID"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:175
+msgid "A 16 byte IV (initialization vector)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:176
+msgid "A checksum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:177
+msgid "Padding, if necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:178
+msgid "One or more { delivery instruction, I2NP message fragment } pairs"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:181
+msgid ""
+"Tunnel IDs are 4 byte numbers used at each hop - participants know what\n"
+"tunnel ID to listen for messages with and what tunnel ID they should be "
+"forwarded\n"
+"on as to the next hop, and each hop chooses the tunnel ID which they "
+"receive messages\n"
+"on.  Tunnels themselves are short-lived (10 minutes).\n"
+"Even if subsequent tunnels are built using the same sequence of \n"
+"peers, each hop's tunnel ID will change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:190
+msgid ""
+"To prevent adversaries from tagging the messages along the path by "
+"adjusting\n"
+"the message size, all tunnel messages are a fixed 1024 bytes in size.  To"
+" accommodate \n"
+"larger I2NP messages as well as to support smaller ones more efficiently,"
+" the\n"
+"gateway splits up the larger I2NP messages into fragments contained "
+"within each\n"
+"tunnel message.  The endpoint will attempt to rebuild the I2NP message "
+"from the\n"
+"fragments for a short period of time, but will discard them as necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:199
+#, python-format
+msgid ""
+"Details are in the\n"
+"tunnel message specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:205
+msgid "Gateway Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:207
+msgid ""
+"After the preprocessing of messages into a padded payload, the gateway "
+"builds\n"
+"a random 16 byte IV value, iteratively encrypting it and the tunnel "
+"message as\n"
+"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel "
+"message} to the next hop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:213
+msgid ""
+"How encryption at the gateway is done depends on whether the tunnel is an"
+"\n"
+"inbound or an outbound tunnel.  For inbound tunnels, they simply select a"
+" random\n"
+"IV, postprocessing and updating it to generate the IV for the gateway and"
+" using \n"
+"that IV along side their own layer key to encrypt the preprocessed data."
+"  For outbound \n"
+"tunnels they must iteratively decrypt the (unencrypted) IV and "
+"preprocessed \n"
+"data with the IV and layer keys for all hops in the tunnel.  The result "
+"of the outbound\n"
+"tunnel encryption is that when each peer encrypts it, the endpoint will "
+"recover \n"
+"the initial preprocessed data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:225
+msgid "Participant Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:227
+msgid ""
+"When a peer receives a tunnel message, it checks that the message came "
+"from\n"
+"the same previous hop as before (initialized when the first message comes"
+" through\n"
+"the tunnel).  If the previous peer is a different router, or if the "
+"message has\n"
+"already been seen, the message is dropped.  The participant then encrypts"
+" the \n"
+"received IV with AES256/ECB using their IV key to determine the current "
+"IV, uses \n"
+"that IV with the participant's layer key to encrypt the data, encrypts "
+"the \n"
+"current IV with AES256/ECB using their IV key again, then forwards the "
+"tuple \n"
+"{nextTunnelId, nextIV, encryptedData} to the next hop.  This double "
+"encryption\n"
+"of the IV (both before and after use) help address a certain class of\n"
+"confirmation attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:240
+msgid ""
+"Duplicate message detection is handled by a decaying Bloom filter on "
+"message\n"
+"IVs.  Each router maintains a single Bloom filter to contain the XOR of "
+"the IV and\n"
+"the first block of the message received for all of the tunnels it is "
+"participating\n"
+"in, modified to drop seen entries after 10-20 minutes (when the tunnels "
+"will have\n"
+"expired).  The size of the bloom filter and the parameters used are "
+"sufficient to\n"
+"more than saturate the router's network connection with a negligible "
+"chance of \n"
+"false positive.  The unique value fed into the Bloom filter is the XOR of"
+" the IV \n"
+"and the first block so as to prevent nonsequential colluding peers in the"
+" tunnel \n"
+"from tagging a message by resending it with the IV and first block "
+"switched."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:253
+msgid "Endpoint Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:255
+msgid ""
+"After receiving and validating a tunnel message at the last hop in the "
+"tunnel,\n"
+"how the endpoint recovers the data encoded by the gateway depends upon "
+"whether \n"
+"the tunnel is an inbound or an outbound tunnel.  For outbound tunnels, "
+"the \n"
+"endpoint encrypts the message with its layer key just like any other "
+"participant, \n"
+"exposing the preprocessed data.  For inbound tunnels, the endpoint is "
+"also the \n"
+"tunnel creator so they can merely iteratively decrypt the IV and message,"
+" using the \n"
+"layer and IV keys of each step in reverse order."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:265
+msgid ""
+"At this point, the tunnel endpoint has the preprocessed data sent by the "
+"gateway,\n"
+"which it may then parse out into the included I2NP messages and forwards "
+"them as\n"
+"requested in their delivery instructions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:272
+msgid "Tunnel Building"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:274
+msgid ""
+"When building a tunnel, the creator must send a request with the "
+"necessary\n"
+"configuration data to each of the hops and wait for all of them to agree "
+"before\n"
+"enabling the tunnel.  The requests are encrypted so that only the peers "
+"who need\n"
+"to know a piece of information (such as the tunnel layer or IV key) has "
+"that\n"
+"data.  In addition, only the tunnel creator will have access to the "
+"peer's\n"
+"reply.  There are three important dimensions to keep in mind when "
+"producing\n"
+"the tunnels: what peers are used (and where), how the requests are sent "
+"(and \n"
+"replies received), and how they are maintained."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:288
+msgid ""
+"Beyond the two types of tunnels - inbound and outbound - there are two "
+"styles\n"
+"of peer selection used for different tunnels - exploratory and client.\n"
+"Exploratory tunnels are used for both network database maintenance and "
+"tunnel\n"
+"maintenance, while client tunnels are used for end to end client messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:296
+msgid "Exploratory tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:298
+msgid ""
+"Exploratory tunnels are built out of a random selection of peers from a "
+"subset\n"
+"of the network.  The particular subset varies on the local router and on "
+"what their\n"
+"tunnel routing needs are.  In general, the exploratory tunnels are built "
+"out of\n"
+"randomly selected peers who are in the peer's \"not failing but active\" "
+"profile\n"
+"category.  The secondary purpose of the tunnels, beyond merely tunnel "
+"routing,\n"
+"is to find underutilized high capacity peers so that they can be promoted"
+" for\n"
+"use in client tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:308
+#, python-format
+msgid ""
+"Exploratory peer selection is discussed further on the\n"
+"Peer Profiling and Selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:314
+msgid "Client tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:316
+msgid ""
+"Client tunnels are built with a more stringent set of requirements - the "
+"local\n"
+"router will select peers out of its \"fast and high capacity\" profile "
+"category so\n"
+"that performance and reliability will meet the needs of the client "
+"application.\n"
+"However, there are several important details beyond that basic selection "
+"that \n"
+"should be adhered to, depending upon the client's anonymity needs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:324
+#, python-format
+msgid ""
+"Client peer selection is discussed further on the\n"
+"Peer Profiling and Selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:329
+msgid "Peer Ordering within Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:331
+#, python-format
+msgid ""
+"Peers are ordered within tunnels to deal with the\n"
+"predecessor attack\n"
+"(2008 update)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:338
+msgid ""
+"To frustrate the predecessor \n"
+"attack, the tunnel selection keeps the peers selected in a strict order -"
+"\n"
+"if A, B, and C are in a tunnel for a particular tunnel pool, the hop "
+"after A is always B, and the hop after\n"
+"B is always C."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:345
+msgid ""
+"Ordering is implemented by generating a random 32-byte key for each\n"
+"tunnel pool at startup.\n"
+"Peers should not be able to guess the ordering, or an attacker could\n"
+"craft two router hashes far apart to maximize the chance of being at both"
+"\n"
+"ends of a tunnel.\n"
+"Peers are sorted by XOR distance of the\n"
+"SHA256 Hash of (the peer's hash concatenated with the random key) from "
+"the random key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:360
+msgid ""
+"Because each tunnel pool uses a different random key, ordering is "
+"consistent\n"
+"within a single pool but not between different pools.\n"
+"New keys are generated at each router restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:367
+msgid "Request delivery"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:369
+#, python-format
+msgid ""
+"A multi-hop tunnel is built using a single build message which is "
+"repeatedly\n"
+"decrypted and forwarded. In the terminology of\n"
+"Hashing it out in Public,\n"
+"this is \"non-interactive\" telescopic tunnel building."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:376
+#, python-format
+msgid ""
+"This tunnel request preparation, delivery, and response method is\n"
+"designed to reduce the number of\n"
+"predecessors exposed, cuts the number of messages transmitted, verifies "
+"proper\n"
+"connectivity, and avoids the message counting attack of traditional "
+"telescopic\n"
+"tunnel creation.\n"
+"(This method, which sends messages to extend a tunnel through the "
+"already-established\n"
+"part of the tunnel, is termed \"interactive\" telescopic tunnel building "
+"in\n"
+"the \"Hashing it out\" paper.)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:387
+#, python-format
+msgid ""
+"The details of tunnel request and response messages, and their "
+"encryption,\n"
+"are specified here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:392
+msgid ""
+"Peers may reject tunnel creation requests for a variety of reasons, "
+"though\n"
+"a series of four increasingly severe rejections are known: probabilistic "
+"rejection\n"
+"(due to approaching the router's capacity, or in response to a flood of "
+"requests), \n"
+"transient overload, bandwidth overload, and critical failure.  When "
+"received, \n"
+"those four are interpreted by the tunnel creator to help adjust their "
+"profile of\n"
+"the router in question."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:401
+#, python-format
+msgid ""
+"For more information on peer profiling, see the\n"
+"Peer Profiling and Selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:407
+msgid "Tunnel Pools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:409
+#, python-format
+msgid ""
+"To allow efficient operation, the router maintains a series of tunnel "
+"pools,\n"
+"each managing a group of tunnels used for a specific purpose with their "
+"own\n"
+"configuration.  When a tunnel is needed for that purpose, the router "
+"selects one\n"
+"out of the appropriate pool at random.  Overall, there are two "
+"exploratory tunnel\n"
+"pools - one inbound and one outbound - each using the router's default "
+"configuration.\n"
+"In addition, there is a pair of pools for each local destination -\n"
+"one inbound and one outbound tunnel pool.  Those pools use the "
+"configuration specified\n"
+"when the local destination connects to the router via I2CP, or the router's defaults if\n"
+"not specified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:421
+#, python-format
+msgid ""
+"Each pool has within its configuration a few key settings, defining how "
+"many\n"
+"tunnels to keep active, how many backup tunnels to maintain in case of "
+"failure,\n"
+"how long the tunnels should be, whether those\n"
+"lengths should be randomized, as \n"
+"well as any of the other settings allowed when configuring individual "
+"tunnels.\n"
+"Configuration options are specified on the I2CP "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:431
+msgid "Tunnel Lengths and Defaults"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:433
+msgid "On the tunnel overview page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:435
+msgid "Anticipatory Build Strategy and Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:437
+msgid ""
+"Tunnel building is expensive, and tunnels expire a fixed time after they "
+"are built.\n"
+"However, when a pool that runs out of tunnels, the Destination is "
+"essentially dead.\n"
+"In addition, tunnel build success rate may vary greatly with both local "
+"and global\n"
+"network conditions.\n"
+"Therefore, it is important to maintain an anticipatory, adaptive build "
+"strategy\n"
+"to ensure that new tunnels are successfully built before they are needed,"
+"\n"
+"without building an excess of tunnels, building them too soon,\n"
+"or consuming too much CPU or bandwidth creating and sending the encrypted"
+" build messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:448
+msgid ""
+"For each tuple {exploratory/client, in/out, length, length variance}\n"
+"the router maintains statistics on the time required for a successful\n"
+"tunnel build.\n"
+"Using these statistics, it calculates how long before a tunnel's "
+"expiration\n"
+"it should start attempting to build a replacement.\n"
+"As the expiration time approaches without a successful replacement,\n"
+"it starts multiple build attempts in parallel, and then\n"
+"will increase the number of parallel attempts if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:459
+msgid ""
+"To cap bandwidth and CPU usage,\n"
+"the router also limits the maximum number of build attempts outstanding\n"
+"across all pools.\n"
+"Critical builds (those for exploratory tunnels, and for pools that have\n"
+"run out of tunnels) are prioritized."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:468
+msgid "Tunnel Message Throttling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:470
+msgid ""
+"Even though the tunnels within I2P bear a resemblance to a circuit "
+"switched\n"
+"network, everything within I2P is strictly message based - tunnels are "
+"merely\n"
+"accounting tricks to help organize the delivery of messages.  No "
+"assumptions are\n"
+"made regarding reliability or ordering of messages, and retransmissions "
+"are left\n"
+"to higher levels (e.g. I2P's client layer streaming library).  This "
+"allows I2P\n"
+"to take advantage of throttling techniques available to both packet "
+"switched and\n"
+"circuit switched networks.  For instance, each router may keep track of "
+"the \n"
+"moving average of how much data each tunnel is using, combine that with "
+"all of \n"
+"the averages used by other tunnels the router is participating in, and be"
+" able\n"
+"to accept or reject additional tunnel participation requests based on its"
+" \n"
+"capacity and utilization.  On the other hand, each router can simply drop"
+" \n"
+"messages that are beyond its capacity, exploiting the research used on "
+"the \n"
+"normal Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:486
+msgid ""
+"In the current implementation, routers implement a\n"
+"weighted random early discard (WRED) strategy.\n"
+"For all participating routers (internal participant, inbound gateway, and"
+" outbound endpoint),\n"
+"the router will start randomly dropping a portion of messages as the\n"
+"bandwidth limits are approached.\n"
+"As traffic gets closer to, or exceeds, the limits, more messages are "
+"dropped.\n"
+"For an internal participant, all messages are fragmented and padded and "
+"therefore are the same size.\n"
+"At the inbound gateway and outbound endpoint, however, the dropping "
+"decision is made\n"
+"on the full (coalesced) message, and the message size is taken into "
+"account.\n"
+"Larger messages are more likely to be dropped.\n"
+"Also, messages are more likely to be dropped at the outbound endpoint "
+"than the inbound gateway,\n"
+"as those messages are not as \"far along\" in their journey and thus the "
+"network cost of\n"
+"dropping those messages is lower."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:504
+msgid "Mixing/batching"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:506
+msgid ""
+"What strategies could be used at the gateway and at each hop for "
+"delaying,\n"
+"reordering, rerouting, or padding messages?  To what extent should this "
+"be done\n"
+"automatically, how much should be configured as a per tunnel or per hop "
+"setting,\n"
+"and how should the tunnel's creator (and in turn, user) control this "
+"operation?\n"
+"All of this is left as unknown, to be worked out for a distant future "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:515
+msgid "Padding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:516
+msgid ""
+"The padding strategies can be used on a variety of levels, addressing the"
+"\n"
+"exposure of message size information to different adversaries.\n"
+"The current fixed tunnel message size is 1024 bytes.  Within this "
+"however, the fragmented\n"
+"messages themselves are not padded by the tunnel at all, though for end "
+"to end \n"
+"messages, they may be padded as part of the garlic wrapping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:526
+msgid ""
+"WRED strategies have a significant impact on end-to-end performance,\n"
+"and prevention of network congestion collapse.\n"
+"The current WRED strategy should be carefully evaluated and improved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/old-implementation.html:2
+msgid "Old Tunnel Implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/old-implementation.html:5
+#, python-format
+msgid ""
+"Note: Obsolete - NOT used!  Replaced in 0.6.1.10 - see here for the current implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:7
+msgid ""
+"This page describes the origins and design of I2P's unidirectional "
+"tunnels.\n"
+"For further infomrmation see:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:13
+msgid "Tunnel overview page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:19
+msgid "Tunnel design discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:21
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:23
+msgid "Meeting 125 (~13:12-13:30)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:28
+msgid "Review"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:30
+msgid ""
+"While we aren't aware of any published research on the advantages of \n"
+"unidirecdtional tunnels,\n"
+"they appear to make it harder to detect a \n"
+"request/response pattern, which is quite possible to detect over a \n"
+"bidirectional tunnel.\n"
+"Several apps and protocols, notably HTTP,\n"
+"do transfer data in such manner. Having the traffic follow the same \n"
+"route to its destination and back could make it easier for an \n"
+"attacker who has only timing and traffic volume data to infer the path a"
+" \n"
+"tunnel is taking.\n"
+"Having the response come back along a different path arguably \n"
+"makes it harder."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:45
+msgid ""
+"When dealing with \n"
+"an internal adversary or most external adversaries, I2P's undirectional "
+"tunnels\n"
+"expose half as much traffic data than would be exposed with bidirectional"
+" circuits\n"
+"by simply looking at the flows themselves - an HTTP request and response "
+"would \n"
+"follow the same path in Tor, while in I2P the packets making up the "
+"request \n"
+"would go out through one or more outbound tunnels and the packets making "
+"up \n"
+"the response would come back through one or more different inbound "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:55
+msgid ""
+"The strategy of using two separate tunnels for inbound and outbound\n"
+"communication is not the only technique available, and it does have "
+"anonymity\n"
+"implications.  On the positive side, by using separate tunnels it lessens"
+" the\n"
+"traffic data exposed for analysis to participants in a tunnel - for "
+"instance,\n"
+"peers in an outbound tunnel from a web browser would only see the traffic"
+" of\n"
+"an HTTP GET, while the peers in an inbound tunnel would see the payload \n"
+"delivered along the tunnel.  With bidirectional tunnels, all participants"
+" would\n"
+"have access to the fact that e.g. 1KB was sent in one direction, then "
+"100KB\n"
+"in the other.  On the negative side, using unidirectional tunnels means "
+"that\n"
+"there are two sets of peers which need to be profiled and accounted for, "
+"and\n"
+"additional care must be taken to address the increased speed of "
+"predecessor\n"
+"attacks.  The tunnel pooling and building process\n"
+"(peer selection and ordering strategies)\n"
+"should minimize the worries of the predecessor attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:73
+msgid "Anonymity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:75
+#, python-format
+msgid ""
+"A recent paper by Hermann and Grothoff\n"
+"declared that I2P's unidirectional tunnels \"seems to be a bad design "
+"decision\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:80
+msgid ""
+"The paper's main point is that\n"
+"deanonymizations on unidirectional tunnels take a longer time, which is "
+"an \n"
+"advantage, but that an attacker can be more certain in the unidirectional"
+" case. \n"
+"Therefore, the paper claims it isn't an advantage at all, but a "
+"disadvantage, at least\n"
+"with long-living eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:88
+msgid ""
+"This conclusion is not fully supported by the paper. Unidirectional "
+"tunnels clearly \n"
+"mitigate other attacks and it's not clear how to trade off the risk of "
+"the \n"
+"attack in the paper\n"
+"with attacks on a bidirectional tunnel architecture."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:95
+msgid ""
+"This conclusion is based on an arbitrary certainty vs. time weighting \n"
+"(tradeoff) that may not be applicable in all cases. For \n"
+"example, somebody could make a list of possible IPs then issue subpoenas "
+"to \n"
+"each. Or the attacker could DDoS each in turn and via a simple \n"
+"intersection attack see if the eepsite goes down or is slowed down. So "
+"close \n"
+"may be good enough, or time may be more important."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:104
+msgid ""
+"The conclusion is based on a specific weighting of the importance of "
+"certainty \n"
+"vs. time, and that weighting may be wrong, and it's definitely debatable,"
+" \n"
+"especially in a real world with subpoenas, search warrants, and other "
+"methods \n"
+"available for final confirmation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:111
+msgid ""
+"A full analysis of the tradeoffs of unidirectional vs. bidirectional \n"
+"tunnels is clearly outside the scope of the paper, and has not been done"
+" \n"
+"elsewhere. For example, how does this attack compare to the numerous "
+"possible \n"
+"timing attacks published about onion-routed networks? Clearly the authors"
+" have not\n"
+"done that analysis, if it's even possible to do it\n"
+"effectively."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:120
+msgid ""
+"Tor uses bidirectional tunnels and has had a lot of academic review. I2P"
+" \n"
+"uses unidirectional tunnels and has had very little review. Does the lack"
+" of a \n"
+"research paper defending unidirectional tunnels mean that it is a poor "
+"design \n"
+"choice, or just that it needs more study? Timing attacks and \n"
+"distributed attacks are difficult to defend against in both I2P and Tor. "
+"The \n"
+"design intent (see references above) was that unidirectional tunnels are "
+"more \n"
+"resistant to timing attacks. However, the paper presents a somewhat "
+"different type of timing \n"
+"attack. Is this attack, innovative as it is, sufficient to label I2P's \n"
+"tunnel architecture (and thus I2P as a whole) a \"bad design\", and by \n"
+"implication clearly inferior to Tor, or is it just a design alternative "
+"that \n"
+"clearly needs further investigation and analysis? There are several other"
+" reasons \n"
+"to consider I2P currently inferior to Tor and other projects (small "
+"network \n"
+"size, lack of funding, lack of review) but is unidirectional tunnels "
+"really a \n"
+"reason?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:137
+msgid ""
+"In summary, \"bad design decision\" is apparently (since the paper does\n"
+"not label bidirectional tunnels \"bad\") shorthand for \"unidirectional \n"
+"tunnels are unequivocally inferior to bidirectional tunnels\", yet this \n"
+"conclusion is not supported by the paper."
+msgstr ""
+
diff --git a/i2p2www/translations/sv_SE/LC_MESSAGES/get-involved.po b/i2p2www/translations/sv_SE/LC_MESSAGES/get-involved.po
new file mode 100644
index 00000000..08134c70
--- /dev/null
+++ b/i2p2www/translations/sv_SE/LC_MESSAGES/get-involved.po
@@ -0,0 +1,4075 @@
+# Swedish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# hottuna , 2013
+# Martin Svensson , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-04-27 23:10+0000\n"
+"Last-Translator: Martin Svensson \n"
+"Language-Team: Swedish (Sweden) "
+"(http://www.transifex.com/projects/p/I2P/language/sv_SE/)\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/get-involved/donate.html:2
+#: i2p2www/pages/site/get-involved/index.html:77
+msgid "Donate"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:4
+msgid ""
+"Thank you for your interest in contributing to I2P!\n"
+"The details of how you\n"
+"can make your contribution are provided below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:11
+#: i2p2www/pages/site/get-involved/donate.html:27
+#, python-format
+msgid ""
+"As of %(date)s, eche|on has been running a\n"
+"%(cointype)s account for the I2P project.\n"
+"If you'd like to donate using %(cointype)s, just transfer your\n"
+"desired amount of coins to the account %(account)s\n"
+"and leave eche|on a note if you'd like your donation to be\n"
+"mentioned on the I2P webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:22
+#: i2p2www/pages/site/get-involved/donate.html:38
+msgid "For easy usage, use the QR code below!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:44
+#, python-format
+msgid "You can donate direct via PayPal to the account \"%(account)s\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:50
+msgid "One time donation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:64
+msgid "Donate 10 €/month for 12 months:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:72
+#: i2p2www/pages/site/get-involved/donate.html:84
+#: i2p2www/pages/site/get-involved/donate.html:96
+#: i2p2www/pages/site/get-involved/donate.html:108
+msgid "I2P donation "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:78
+msgid "Donate 20 €/month for 12 months:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:90
+msgid "Donate 30 €/month for 12 months:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:102
+msgid "Donate 50 €/month for 12 months:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:117
+msgid "Flattr this"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:122
+msgid ""
+"If you want to keep more or less anonymous, the option to send money via "
+"mail is also available. But it is less secure\n"
+"as the envelope can be lost on the way to us."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:126
+#, python-format
+msgid ""
+"If you'd like to donate via  snail mail, send an email to %(email)s\n"
+" and you'll receive an email with instructions detailing how to proceed."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:131
+#, python-format
+msgid ""
+"In the meantime, feel free to take a look at the generous donations that "
+"have been\n"
+"given in support of the I2P Project at the hall of fame."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:2
+msgid "Get Involved!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:4
+msgid "We need your help!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:5
+msgid ""
+"To get involved, please feel free to join us on the #i2p IRC channel (on\n"
+"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or "
+"irc.postman.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:9
+#, python-format
+msgid ""
+"If you're interested in joining our team, please"
+" get in\n"
+"touch as we're always looking for eager contributors!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:13
+msgid ""
+"We need help in many areas, and you don't need to know Java to "
+"contribute!\n"
+"Here's a list to help you get started!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:18
+msgid "Spread the Word!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:19
+msgid ""
+"Tell people about I2P on forums, blogs, and comments to articles.\n"
+"Fix up the Wikipedia article about I2P in your language.\n"
+"Tell your friends."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:24
+msgid "Testing"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:25
+#, python-format
+msgid ""
+"Run the latest builds from monotone\n"
+"and report results on #i2p or as bugs on Trac."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:30
+msgid "Documentation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:31
+msgid ""
+"Help fix the parts of the website that are outdated or incomplete.\n"
+"Translate pages into other languages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:35
+msgid "Pictures"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:36
+msgid "Make some more pictures, fix the old ones on the website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:39
+msgid "Content"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:40
+msgid "Make an eepsite! Add some content! Contribute to the community!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:43
+msgid "Services"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:44
+msgid ""
+"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n"
+"a naming service, a search engine, an eepsite monitor... many of these\n"
+"aren't that hard."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:49
+msgid "Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:50
+#, python-format
+msgid ""
+"Write or port applications for I2P! There's some guidelines and\n"
+"a list of ideas on the applications page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:54
+msgid "Coding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:55
+#, python-format
+msgid ""
+"There's plenty to do if you know Java or are ready to learn.\n"
+"Check for open tickets on Trac\n"
+"or the TODO list on %(zzz)s for\n"
+"some ideas on where to start.\n"
+"See the new developer's guide for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:64
+msgid "Translation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:65
+#, python-format
+msgid ""
+"Help translate the website and the software into your language.\n"
+"See the new translator's guide for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:69
+msgid "Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:70
+#, python-format
+msgid ""
+"Study or test the code to look for vulnerabilities.\n"
+"Both anonymity vulnerabilities from the various\n"
+"threat models,\n"
+"and DOS and other weaknesses due to securities holes,\n"
+"need researching."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:2
+msgid "Roadmap"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:7
+msgid ""
+"Include some seed data in the distribution so a central reseed location "
+"isn't required?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:10
+#, python-format
+msgid ""
+"Reachability Mapping / handle peers partially reachable / enhanced restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:13
+msgid "Improve help pages and website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:14
+msgid "More translations"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:15
+msgid "SSU disconnect message"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:16
+msgid "Iterative floodfill lookups"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:21
+msgid "Full review of anonymity issues and other vulnerabilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:22
+msgid ""
+"Reduce memory usage, remove debugging overhead, make it run better on "
+"slow and embedded machines"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:25
+msgid "Docs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:30
+msgid "Full restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:35
+msgid "Tunnel mixing and padding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:36
+msgid "User defined message delays"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:39
+#, python-format
+msgid ""
+"Please see the TODO list for more detailed info "
+"about some of these tasks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:2
+msgid "To Do List"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:4
+msgid "I2P Project Targets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:5
+#, python-format
+msgid ""
+"Below is a more detailed (yet still incomplete) discussion of the major "
+"areas\n"
+"of future development on the core I2P network, spanning the plausibly "
+"planned\n"
+"releases. This does not include stego transports, porting to wireless "
+"devices,\n"
+"or tools to secure the local machine, nor does it include client "
+"applications\n"
+"that will be essential in I2P's success. There are probably other things "
+"that\n"
+"will come up, especially as I2P gets more peer review, but these are the "
+"main\n"
+"'big things'. See also the roadmap. Want to "
+"help?\n"
+"Get involved!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:54
+msgid "Core functionality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:52
+msgid "link"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:18
+#: i2p2www/pages/site/get-involved/todo.html:57
+msgid "NAT/Firewall bridging via 1-hop restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:21
+#: i2p2www/pages/site/get-involved/todo.html:130
+msgid "High degree transport layer with UDP, NBIO, or NIO"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:24
+#: i2p2www/pages/site/get-involved/todo.html:218
+msgid "NetworkDB and profile tuning and ejection policy for large nets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:242
+msgid "Security / anonymity"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:30
+#: i2p2www/pages/site/get-involved/todo.html:245
+msgid ""
+"Per-hop tunnel id & new permuted TunnelVerificationStructure "
+"encryption"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:33
+#: i2p2www/pages/site/get-involved/todo.html:295
+msgid "Strict ordering of participants within tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:36
+msgid "Randomly permuted tunnel lengths"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:39
+#: i2p2www/pages/site/get-involved/todo.html:357
+msgid "Full blown n-hop restricted routes with optional trusted links"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:42
+#: i2p2www/pages/site/get-involved/todo.html:376
+msgid "Hashcash for routerIdentity, destination, and tunnel request"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:45
+#: i2p2www/pages/site/get-involved/todo.html:405
+msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:48
+#: i2p2www/pages/site/get-involved/todo.html:442
+msgid "Stop & go mix w/ garlics & tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:52
+#: i2p2www/pages/site/get-involved/todo.html:456
+msgid "Performance"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:62
+msgid "Implemented in I2P 0.6.0.6"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:63
+msgid ""
+"The functionality of allowing routers to fully participate within the "
+"network \n"
+"while behind firewalls and NATs that they do not control requires some "
+"basic \n"
+"restricted route operation (since those peers will not be able to receive"
+" \n"
+"inbound connections). To do this successfully, you consider peers one of"
+" \n"
+"two ways:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:73
+msgid ""
+"Peers who have reachable interfaces - these peers do not need to \n"
+"do anything special"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:77
+msgid ""
+"Peers who do not have reachable interfaces - these peers must "
+"build \n"
+"a tunnel pointing at them where the gateway is one of the peers they have"
+" \n"
+"established a connection with who has both a publicly reachable interface"
+" \n"
+"and who has agreed to serve as their 'introducer'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:85
+msgid ""
+"To do this, peers who have no IP address simply connect to a few peers, \n"
+"build a tunnel through them, and publish a reference to those tunnels "
+"within \n"
+"their RouterInfo structure in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:90
+msgid ""
+"When someone wants to contact any particular router, they first must get"
+" \n"
+"its RouterInfo from the network database, which will tell them whether "
+"they \n"
+"can connect directly (e.g. the peer has a publicly reachable interface) \n"
+"or whether they need to contact them indirectly. Direct connections occur"
+" \n"
+"as normal, while indirect connections are done through one of the "
+"published \n"
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:98
+msgid ""
+"When a router just wants to get a message or two to a specific hidden "
+"peer, \n"
+"they can just use the indirect tunnel for sending the payload. However, \n"
+"if the router wants to talk to the hidden peer often (for instance, as "
+"part \n"
+"of a tunnel), they will send a garlic routed message through the indirect"
+" \n"
+"tunnel to that hidden peer which unwraps to contain a message which "
+"should \n"
+"be sent to the originating router. That hidden peer then establishes an \n"
+"outbound connection to the originating router and from then on, those two"
+" \n"
+"routers can talk to each other directly over that newly established "
+"direct \n"
+"connection."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:109
+msgid ""
+"Of course, that only works if the originating peer can receive "
+"connections \n"
+"(they aren't also hidden). However, if the originating peer is hidden, "
+"they \n"
+"can simply direct the garlic routed message to come back to the "
+"originating \n"
+"peer's inbound tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:115
+msgid ""
+"This is not meant to provide a way for a peer's IP address to be "
+"concealed, \n"
+"merely as a way to let people behind firewalls and NATs fully operate "
+"within \n"
+"the network. Concealing the peer's IP address adds a little more work, as"
+" \n"
+"described below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:121
+msgid ""
+"With this technique, any router can participate as any part of a tunnel."
+" \n"
+"For efficiency purposes, a hidden peer would be a bad choice for an "
+"inbound \n"
+"gateway, and within any given tunnel, two neighboring peers wouldn't want"
+" \n"
+"to be hidden. But that is not technically necessary."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:133
+msgid "Both UDP and NIO have been Implemented in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:134
+msgid ""
+"Standard TCP communication in Java generally requires blocking socket \n"
+"calls, and to keep a blocked socket from hanging the entire system, those"
+" \n"
+"blocking calls are done on their own threads. Our current TCP transport \n"
+"is implemented in a naive fashion - for each peer we are talking to, we \n"
+"have one thread reading and one thread writing. The reader thread simply"
+" \n"
+"loops a bunch of read() calls, building I2NP messages and adding them \n"
+"to our internal inbound message queue, and the writer thread pulls "
+"messages \n"
+"off a per-connection outbound message queue and shoves the data through \n"
+"write() calls."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:145
+msgid ""
+"We do this fairly efficiently, from a CPU perspective - at any time, \n"
+"almost all of these threads are sitting idle, blocked waiting for "
+"something \n"
+"to do. However, each thread consumes real resources (on older Linux "
+"kernels, \n"
+"for instance, each thread would often be implemented as a fork()'ed "
+"process). \n"
+"As the network grows, the number of peers each router will want to talk \n"
+"with will increase (remember, I2P is fully connected, meaning that any \n"
+"given peer should know how to get a message to any other peer, and "
+"restricted \n"
+"route support will probably not significantly reduce the number of "
+"connections \n"
+"necessary). This means that with a 100,000 router network, each router \n"
+"will have up to 199,998 threads just to deal with the TCP connections!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:157
+msgid ""
+"Obviously, that just won't work. We need to use a transport layer that \n"
+"can scale. In Java, we have two main camps:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:162
+#, python-format
+msgid ""
+"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:165
+msgid ""
+"Sending and receiving UDP datagrams is a connectionless operation - if \n"
+"we are communicating with 100,000 peers, we simply stick the UDP packets"
+" \n"
+"in a queue and have a single thread pulling them off the queue and "
+"shoving \n"
+"them out the pipe (and to receive, have a single thread pulling in any \n"
+"UDP packets received and adding them to an inbound queue)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:172
+msgid ""
+"However, moving to UDP means losing the benefits of TCP's ordering, "
+"congestion \n"
+"control, MTU discovery, etc. Implementing that code will take significant"
+" \n"
+"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n"
+"a while ago I was taking some measurements in the simulator and on the \n"
+"live net, and the vast majority of messages transferred would fit easily"
+" \n"
+"within a single unfragmented UDP packet, and the largest of the messages"
+" \n"
+"would fit within 20-30 packets. As mule pointed out, TCP adds a "
+"significant \n"
+"overhead when dealing with so many small packets, as the ACKs are within"
+" \n"
+"an order of magnitude in size. With UDP, we can optimize the transport \n"
+"for both efficiency and resilience by taking into account I2P's "
+"particular \n"
+"needs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:185
+msgid "It will be a lot of work though."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:188
+msgid "NIO or NBIO"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:189
+msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:192
+msgid ""
+"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java"
+" \n"
+"developers to take advantage of the operating system's nonblocking IO \n"
+"capabilities - allowing you to maintain a large number of concurrent IO \n"
+"operations without requiring a separate thread for each. There is much \n"
+"promise with this approach, as we can scalable handle a large number of \n"
+"concurrent connections and we don't have to write a mini-TCP stack with \n"
+"UDP. However, the NIO packages have not proven themselves to be battle-"
+"ready, \n"
+"as the Freenet developer's found. In addition, requiring NIO support "
+"would \n"
+"mean we can't run on any of the open source JVMs like Kaffe, \n"
+"as GNU/Classpath has only "
+"limited \n"
+"support for NIO. (note: this may not be the case anymore, as there \n"
+"has been some progress on Classpath's NIO, but it is an unknown "
+"quantity)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:206
+#, python-format
+msgid ""
+"Another alternative along the same lines is the Non"
+" \n"
+"Blocking I/O package - essentially a cleanroom NIO implementation \n"
+"(written before NIO was around). It works by using some native OS code \n"
+"to do the nonblocking IO, passing off events through Java. It seems to \n"
+"be working with Kaffe, though there doesn't seem to be much development \n"
+"activity on it lately (likely due to 1.4's NIO deployment)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:221
+msgid ""
+"Within the current network database and profile management "
+"implementation, \n"
+"we have taken the liberty of some practical shortcuts. For instance, we \n"
+"don't have the code to drop peer references from the K-buckets, as we \n"
+"don't have enough peers to even plausibly fill any of them, so instead, \n"
+"we just keep the peers in whatever bucket is appropriate. Another example"
+" \n"
+"deals with the peer profiles - the memory required to maintain each "
+"peer's \n"
+"profile is small enough that we can keep thousands of full blown profiles"
+" \n"
+"in memory without problems. While we have the capacity to use trimmed \n"
+"down profiles (which we can maintain 100s of thousands in memory), we \n"
+"don't have any code to deal with moving a profile from a \"minimal "
+"profile\" \n"
+"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to"
+" simply \n"
+"eject a profile altogether. It just wouldn't be practical to write that \n"
+"code yet, since we aren't going to need it for a while."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:236
+msgid ""
+"That said, as the network grows we are going to want to keep these "
+"considerations \n"
+"in mind. We will have some work to do, but we can put it off for later."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:248
+#: i2p2www/pages/site/get-involved/todo.html:332
+#, python-format
+msgid ""
+"Addressed in I2P 0.5 as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:251
+msgid ""
+"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n"
+"going to Dave, then to Charlie, then Bob, and finally Alice "
+"(A<--B<--C<--D<--E), \n"
+"all five of them will know they are participating in tunnel \"123\", as \n"
+"the messages are tagged as such. What we want to do is give each hop "
+"their \n"
+"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n"
+"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n"
+"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n"
+"the tunnel had the same tunnel ID, collusion attacks aren't much work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:261
+msgid ""
+"Adding a unique tunnel ID per hop isn't hard, but by itself, "
+"insufficient. \n"
+"If Dave and Bob are under the control of the same attacker, they wouldn't"
+" \n"
+"be able to tell they are in the same tunnel due to the tunnel ID, but \n"
+"would be able to tell by the message bodies and verification structures \n"
+"by simply comparing them. To prevent that, the tunnel must use layered \n"
+"encryption along the path, both on the payload of the tunneled message \n"
+"and on the verification structure (used to prevent simple tagging "
+"attacks). \n"
+"This requires some simple modifications to the TunnelMessage, as well \n"
+"as the inclusion of per-hop secret keys delivered during tunnel creation"
+" \n"
+"and given to the tunnel's gateway. We must fix a maximum tunnel length \n"
+"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n"
+"of the 16 delivered secret keys, in reverse order, and to encrypt the \n"
+"signature of the hash of the (encrypted) payload at each step. The "
+"gateway \n"
+"then sends that 16-step encrypted message, along with a 16-step and "
+"16-wide \n"
+"encrypted mapping to the first hop, which then decrypts the mapping and \n"
+"the payload with their secret key, looking in the 16-wide mapping for \n"
+"the entry associated with their own hop (keyed by the per-hop tunnel ID)"
+" \n"
+"and verifying the payload by checking it against the associated signed \n"
+"hash."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:282
+msgid ""
+"The tunnel gateway does still have more information than the other peers"
+" \n"
+"in the tunnel, and compromising both the gateway and a tunnel participant"
+" \n"
+"would allow those peers to collude, exposing the fact that they are both"
+" \n"
+"in the same tunnel. In addition, neighboring peers know that they are \n"
+"in the same tunnel anyway, as they know who they send the message to (and"
+" \n"
+"with IP-based transports without restricted routes, they know who they \n"
+"got it from). However, the above two techniques significantly increase \n"
+"the cost of gaining meaningful samples when dealing with longer tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:298
+msgid "Implemented in release 0.6.2"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:301
+#, python-format
+msgid ""
+"As Connelly proposed to deal with the\n"
+"predecessor attack (2008\n"
+"update), keeping the order of peers within our tunnels consistent \n"
+"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n"
+"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n"
+"get to substantially sample Alice's peer selection group. We may even \n"
+"want to explicitly allow Bob to participate in Alice's tunnels in only \n"
+"one way - receiving a message from Dave and sending it to Charlie - and \n"
+"if any of those peers are not available to participate in the tunnel (due"
+" \n"
+"to overload, network disconnection, etc), avoid asking Bob to participate"
+" \n"
+"in any tunnels until they are back online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:316
+msgid ""
+"More analysis is necessary for revising the tunnel creation - at the \n"
+"moment, we simply select and order randomly within the peer's top tier \n"
+"of peers (ones with fast + high capacity)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:321
+msgid ""
+"Adding a strict ordering to peers in a tunnel also improves the anonymity"
+" \n"
+"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway"
+" \n"
+"is always the same would be particularly damning. However, peers with \n"
+"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n"
+"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n"
+"duration) minutes, use a 1-hop tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:338
+msgid ""
+"Without tunnel length permutation, if someone were to somehow detect that"
+" \n"
+"a destination had a particular number of hops, it might be able to use "
+"that \n"
+"information to identify the router the destination is located on, per the"
+" \n"
+"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n"
+"receives a tunnel message from Charlie and forwards it to Alice, Bob "
+"knows \n"
+"Alice is the final router in the tunnel. If Bob were to identify what "
+"destination \n"
+"that tunnel served (by means of colluding with the gateway and harvesting"
+" \n"
+"the network database for all of the LeaseSets), he would know the router"
+" \n"
+"on which that destination is located (and without restricted routes, that"
+" \n"
+"would mean what IP address the destination is on)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:350
+msgid ""
+"It is to counter user behavior that tunnel lengths should be permuted, \n"
+"using algorithms based on the length requested (for example, the 1/MTBF \n"
+"length change for 0-hop tunnels outlined above)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:360
+msgid ""
+"The restricted route functionality described before was simply a "
+"functional \n"
+"issue - how to let peers who would not otherwise be able to communicate \n"
+"do so. However, the concept of allowing restricted routes includes "
+"additional \n"
+"capabilities. For instance, if a router absolutely cannot risk "
+"communicating \n"
+"directly with any untrusted peers, they can set up trusted links through"
+" \n"
+"those peers, using them to both send and receive all of its messages. \n"
+"Those hidden peers who want to be completely isolated would also refuse \n"
+"to connect to peers who attempt to get them to (as demonstrated by the \n"
+"garlic routing technique outlined before) - they can simply take the "
+"garlic \n"
+"clove that has a request for delivery to a particular peer and tunnel \n"
+"route that message out one of the hidden peer's trusted links with "
+"instructions \n"
+"to forward it as requested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:379
+#, python-format
+msgid ""
+"Within the network, we will want some way to deter people from consuming"
+" \n"
+"too many resources or from creating so many peers to mount a Sybil \n"
+"attack. Traditional techniques such as having a peer see who is "
+"requesting \n"
+"a resource or running a peer aren't appropriate for use within I2P, as \n"
+"doing so would compromise the anonymity of the system. Instead, we want \n"
+"to make certain requests \"expensive\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:387
+msgid ""
+"Hashcash is one technique that \n"
+"we can use to anonymously increase the \"cost\" of doing certain "
+"activities, \n"
+"such as creating a new router identity (done only once on installation),"
+" \n"
+"creating a new destination (done only once when creating a service), or \n"
+"requesting that a peer participate in a tunnel (done often, perhaps 2-300"
+" \n"
+"times per hour). We don't know the \"correct\" cost of each type of "
+"certificate \n"
+"yet, but with some research and experimentation, we could set a base "
+"level \n"
+"that is sufficiently expensive while not an excessive burden for people \n"
+"with few resources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:398
+msgid ""
+"There are a few other algorithms that we can explore for making those \n"
+"requests for resources \"nonfree\", and further research on that front is"
+" \n"
+"appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:408
+#, python-format
+msgid ""
+"To powerful passive external observers as well as large colluding "
+"internal \n"
+"observers, standard tunnel routing is vulnerable to traffic analysis "
+"attacks \n"
+"- simply watching the size and frequency of messages being passed between"
+" \n"
+"routers. To defend against these, we will want to essentially turn some \n"
+"of the tunnels into its own mix cascade - delaying messages received at \n"
+"the gateway and passing them in batches, reordering them as necessary, \n"
+"and injecting dummy messages (indistinguishable from other \"real\" "
+"tunnel \n"
+"messages by peers in the path). There has been a significant amount of \n"
+"research \n"
+"on these algorithms that we can lean on prior to implementing the various"
+" \n"
+"tunnel mixing strategies."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:421
+msgid ""
+"In addition to the anonymity aspects of more varied tunnel operation, \n"
+"there is a functional dimension as well. Each peer only has a certain \n"
+"amount of data they can route for the network, and to keep any particular"
+" \n"
+"tunnel from consuming an unreasonable portion of that bandwidth, they \n"
+"will want to include some throttles on the tunnel. For instance, a tunnel"
+" \n"
+"may be configured to throttle itself after passing 600 messages (1 per \n"
+"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n"
+"last minute). Excess messages may be delayed or summarily dropped. With \n"
+"this sort of throttling, peers can provide ATM-like QoS support for their"
+" \n"
+"tunnels, refusing to agree to allocate more bandwidth than the peer has \n"
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:434
+msgid ""
+"In addition, we may want to implement code to dynamically reroute tunnels"
+" \n"
+"to avoid failed peers or to inject additional hops into the path. This \n"
+"can be done by garlic routing a message to any particular peer in a "
+"tunnel \n"
+"with instructions to redefine the next-hop in the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:445
+msgid ""
+"Beyond the per-tunnel batching and mixing strategy, there are further \n"
+"capabilities for protecting against powerful attackers, such as allowing"
+" \n"
+"each step in a garlic routed path to define a delay or window in which \n"
+"it should be forwarded on. This would enable protections against the long"
+" \n"
+"term intersection attack, as a peer could send a message that looks "
+"perfectly \n"
+"standard to most peers that pass it along, except at any peers where the"
+" \n"
+"clove exposed includes delay instructions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:457
+#, python-format
+msgid ""
+"Performance related improvements are listed on the\n"
+"Performance page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2
+msgid "Bounty Arabic translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3
+#: i2p2www/pages/site/get-involved/bounties/index.html:119
+msgid "Arabic translation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P echelon set out this bounty for translation\n"
+"of the I2P web page and I2P router console into Arabic."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12
+msgid "This bounty is set into 2 subparts:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14
+msgid "Part 1 is translation of the webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17
+msgid ""
+"For collecting the bounty of 20 BTC you need to translate the following "
+"pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25
+msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27
+msgid ""
+"Part 2 is the translation of the router console. The router console was\n"
+"partly translated and the bounty of 80 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34
+msgid "Judge is echelon."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2
+msgid "Bounty creating a I2P native Bitcoin client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3
+msgid "BTC I2P native client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to create a I2P native Bitcoin client. \n"
+"It should integrate with other client via the I2P network and via "
+"gateways to\n"
+"the existant bitcoin network."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15
+msgid "Judge is psychonaut who donated the first 30 € to this bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
+msgid "Bounty datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:3
+msgid "datastore"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:6
+msgid ""
+"To improve I2P's usage and to be independent of routers \n"
+"online status we want a datastorage as a extension to I2P.\n"
+"Like in Freenet the datastorage should be distributed and every\n"
+"participating node should be able to configure his options.\n"
+"The files should be saved in chunks and at least 2-3 times to\n"
+"obtain redundancy. Usage of storage space should be auto balanced.\n"
+"As it is a extra application, it should work flawless within I2P and\n"
+"cooperate nice with the I2P router. Maybe a integration within the\n"
+"webpage/router could be done."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:17
+msgid ""
+"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n"
+"\"eepsites in datastorage\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:21
+msgid ""
+"The frost for I2P datastorage bounty is paid for a frost like program \n"
+"with which files/messages are stored into database and got from database."
+"\n"
+"It needs to work with a GUI."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:26
+msgid ""
+"The eepsite served out of I2P datastorage extends a I2P router to send\n"
+"out eepsites out of the I2P datastorage. All files for eepsites need to "
+"be\n"
+"saved inside of datastorage and are taken from it.\n"
+"Extension:\n"
+"For better integration all datastorage participants could serve that "
+"eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:36
+msgid ""
+"For bounties to be declared done and paid, we need the program AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2
+msgid "Bounty I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3
+msgid "I2P Ubuntu/Debian package"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6
+msgid ""
+"For the future of I2P and in order to attract more people\n"
+"to I2P, this bounty was set for including an I2P package into the Ubuntu "
+"and Debian \n"
+"archive mirrors.\n"
+"To claim this bounty, the I2P router package needs to be available from\n"
+"Ubuntu and Debian archive mirrors and Debian bug \n"
+"448638 \n"
+"needs to be closed successfully."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2
+msgid "Bounty I2PHex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3
+msgid "i2phex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2PHex P2P ArneBab setout the bounty for implementing actual\n"
+"Phex code onto I2PHex."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:2
+msgid "Bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:5
+msgid "Bounties for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:6
+msgid ""
+"While we always gratefully accept any contributions of code, \n"
+"documentation, and the like, there are other ways to help I2P move \n"
+"forward.  As with any open source project, our goals would be achieved "
+"more \n"
+"rapidly if we were able to support all of our contributors to work on \n"
+"I2P full time.  However, as with any open source project, that's not a \n"
+"possibility.  Instead, we are making use of a bounty system, whereby \n"
+"anyone can get support for working on something that people want \n"
+"implemented, and people who want to contribute to I2P can be assured that"
+" \n"
+"their support goes to what they care about."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:18
+msgid ""
+"We are also keeping open the ability for people who want to support I2P \n"
+"but don't have strong feelings about the bounties available.  Those "
+"people\n"
+"can simply put their trust in the I2P team to do what we feel is best by\n"
+"donating to a catch-all general fund that will be used as deemed \n"
+"necessary - allocated to various bounties, covering incidentals (hosting,"
+" \n"
+"etc), and the like."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:27
+msgid "Current bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Name"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Status"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Judge"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Dev"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Bounty"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:32
+msgid "Frost for I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:33
+#: i2p2www/pages/site/get-involved/bounties/index.html:40
+#: i2p2www/pages/site/get-involved/bounties/index.html:47
+#: i2p2www/pages/site/get-involved/bounties/index.html:54
+#: i2p2www/pages/site/get-involved/bounties/index.html:75
+#: i2p2www/pages/site/get-involved/bounties/index.html:82
+msgid "Proposal in development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:35
+#: i2p2www/pages/site/get-involved/bounties/index.html:42
+#: i2p2www/pages/site/get-involved/bounties/index.html:49
+#: i2p2www/pages/site/get-involved/bounties/index.html:56
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+#: i2p2www/pages/site/get-involved/bounties/index.html:97
+msgid "vacant"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:39
+msgid "Eepsites served out of I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:46
+msgid "Backporting Phex code onto I2PHex"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:53
+msgid "I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:60
+msgid "Bitcoin client for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:61
+msgid "Done, phase of verification"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:67
+msgid "Unit tests and Multi-router Simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:68
+msgid "Partly done, partly in work, partly still open"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:89
+msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:94
+msgid "Bundling bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:95
+msgid "Proposed"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:102
+msgid "Claimed bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:107
+msgid "Make I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:114
+msgid "Setting up a SILC server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:124
+msgid "Datastore over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:129
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
+msgid "Russian translation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:134
+msgid "Swarming file transfer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:139
+msgid "Streaming library window size"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:144
+msgid "IRC connect time monitor"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:149
+msgid "Unit tests (part 1)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:161
+msgid ""
+"Dev lists anyone who may already be working on the bounty - collaboration"
+" is\n"
+"preferred, so if you're interested in working on it, please contact one "
+"of the\n"
+"people listed!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2
+msgid "Bounty I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3
+msgid "native IPv6 I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n"
+"To claim this bounty, the I2P router needs to run full on native\n"
+"IPv6 connections like it does on IPv4."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:17
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
+msgid ""
+"For bounties to be declared done and paid, we need the plugin AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:2
+msgid "NetDB Backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:3
+msgid "netDB backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:7
+msgid ""
+"The current NetDB implementation (namely the FloodFill system)\n"
+"needs to be extended with another backend to improve reliability,\n"
+"reduce attack surface and solve the scalability issue for the \n"
+"coming years."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:14
+msgid ""
+"A solution likely based on a DHT will be investigated and \n"
+"finally implemented."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2
+msgid "Bounty russian translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P a anonymous donator set out the bounty for translation\n"
+"of the I2P web page and I2P router console into russian language."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17
+msgid ""
+"For collecting the bounty of $115 USD you need to translate the following"
+" pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30
+msgid ""
+"Part 2 is the translation of the router console. The whole router console"
+" needs\n"
+"to be translated to collect the bounty of $115 USD."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37
+msgid "Judge is the russian donor."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:2
+msgid "Bounty migrate I2P IRC to SILC"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:3
+msgid "I2P silc server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:7
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to setup and host a I2P SILC server.   \n"
+"This will allow people to send files over their messaging servers and "
+"have intrinsic security built into the protocol."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:12
+msgid ""
+"A silc server needs to be set up and run for at least 3 month time to get"
+" payed. \n"
+"A second server should be set up, to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:16
+msgid ""
+"Bounty was withdrawn and money donated to returningnovice and general "
+"fund."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:22
+msgid "Judge is An Anonymous Secret Society, society@mail.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3
+msgid "Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7
+msgid ""
+"Beside of I2P we want to encourage users\n"
+"to care more about anonymity and security. As I2P is a low \n"
+"latency network with its natural limits, the software SYNDIE\n"
+"can overcome some of these limits and provide better anonymity\n"
+"for people who really need it."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14
+msgid ""
+"For our bad sake the syndie project was out of development for \n"
+"quite a long time yet (5 years). To get a fresh and new built \n"
+"with needed bugfixes we set out this bounty. Also syndie needs\n"
+"some enhancements and a better GUI for users to work with it.\n"
+"Current bounty sum is 50 Bitcoin."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22
+msgid ""
+"The latest Syndie coding rally did improve the situation of the\n"
+"Syndie package dramatically. A new Syndie package with bugfixes\n"
+"was created and made available on different webpages.\n"
+"As a result of this work, the bounty sum was reduced and\n"
+"the withdrawn money moved to the IPv6 bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2
+msgid "Bounty unittests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3
+msgid "unit test"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7
+msgid ""
+"To improve I2P's maintainability, we want to have a solid set of\n"
+"automated unit tests for the critical code.  While we do have some\n"
+"unit tests at the moment, they are ad-hoc and partly unfinished.  \n"
+"This bounty is for someone to check the existing tests and move over\n"
+"old ones to jUnit, automate their execution, extend them to provide \n"
+"better code coverage, and publish the report online.  Its a massive \n"
+"effort, but can be broken down into phases, listed below (phase 2 \n"
+"must occur first, but further phases may happen in any order).\n"
+"As this needs some reading of code, it is the best start point for\n"
+"new devs to get a good overview of I2P code and coding. A good job\n"
+"for college students, interns or anyone who is just interested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20
+msgid ""
+"Take care! Jobs and bounties shuffled a bit!\n"
+"Phase 6,7 and 8 are still open!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112
+#, python-format
+msgid "Phase %(phase)s:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27
+msgid "CI jenkins and IRC bot"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114
+#, python-format
+msgid "Bounty: %(euro)s €"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29
+msgid "server runs and this section is blocked"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31
+msgid ""
+"To collect this bounty, a continuous integration server (Jenkins,\n"
+"old name was Hudson) must be set up and a connected IRC bot needs \n"
+"to set up in the channel #i2p-dev on IRC2p network to print out\n"
+"results of build tests.
            \n"
+"The server needs to be run long term."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41
+msgid "Check existing SDK tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69
+msgid "paid to str4d"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45
+#, python-format
+msgid ""
+"To collect this bounty, the existing SDK tests must be checked \n"
+"and made to work again. The need to be integrated into the ant \n"
+"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g."
+" \n"
+"Clover).  The ant script\n"
+"must be capable of generating test status results as a web page, \n"
+"which will be published online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56
+msgid "SDK test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80
+msgid "paid to unittests dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60
+msgid ""
+"To collect this bounty, the automated unit tests of the SDK \n"
+"(i2p/core/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67
+msgid "Router test migration"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71
+msgid ""
+"As with phase 2, the existing unit tests for the router must be\n"
+"moved over to the automated system."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78
+msgid "Router test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82
+msgid ""
+"To collect this bounty, the automated unit tests of the router \n"
+"(i2p/router/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89
+msgid "Streaming lib tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94
+msgid ""
+"To collect this bounty, a new set of unit tests must meet a \n"
+"measured code coverage of 90% of the streaming lib \n"
+"(i2p/apps/ministreaming/ and i2p/apps/streaming/)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102
+msgid "Unit tests coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106
+msgid ""
+"To collect this bounty, all above unit tests must meet the 100%\n"
+"coverage marker (except for log statements)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113
+msgid "MultiRouter simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115
+msgid "will be split in more sub-tasks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117
+msgid ""
+"To collect this bounty, the existing in-memory multi-router\n"
+"simulation must be checked, made work again and extend to simulate\n"
+"lots of routers in memory on a single machine. This bounty will\n"
+"be split in more fine grained subworks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126
+msgid ""
+"Judge on all these works is the donor and donor decides if a phase is\n"
+"called succesfull done and money can be paid."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2
+msgid "Bounty I2P vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3
+msgid "vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P torrent P2P I setout the bounty for a working I2P vuze\n"
+"plugin.\n"
+"The plugin needs to be official and submitted to vuze for publication\n"
+"on their webpage/repository for plugins.\n"
+"It should be easy to install and configured, work smooth and flawless.\n"
+"Configuration should be friendly to starters and made easy to be "
+"anonymous.\n"
+"It should work with *.b32.i2p destinations as with signed (516++ bits) \n"
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:2
+msgid "Application Development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:3
+msgid "May 2013"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:6
+msgid "Application Development Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:8
+msgid "Contents"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:10
+#: i2p2www/pages/site/get-involved/develop/applications.html:16
+msgid "Why write I2P-specific code?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:11
+#: i2p2www/pages/site/get-involved/develop/applications.html:102
+msgid "Important concepts"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:12
+#: i2p2www/pages/site/get-involved/develop/applications.html:190
+msgid "Development options"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:13
+#: i2p2www/pages/site/get-involved/develop/applications.html:303
+msgid "Start developing - a simple guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:18
+#, python-format
+msgid ""
+"There are multiple ways to use applications in I2P.\n"
+"Using I2PTunnel,\n"
+"you can use regular applications without needing to program explicit I2P "
+"support.\n"
+"This is very effective for client-server scenario's,\n"
+"where you need to connect to a single website.\n"
+"You can simply create a tunnel using I2PTunnel to connect to that "
+"website, as shown in Figure 1."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:26
+msgid ""
+"If your application is distributed, it will require connections to a "
+"large amount of peers.\n"
+"Using I2PTunnel, you will need to create a new tunnel for each peer you "
+"want to contact,\n"
+"as shown in Figure 2.\n"
+"This process can of course be automated, but running a lot of I2PTunnel "
+"instances creates a large amount of overhead.\n"
+"In addition, with many protocols you will need to force everyone to \n"
+"use the same set of ports for all peers - e.g. if you want to reliably "
+"run DCC \n"
+"chat, everyone needs to agree that port 10001 is Alice, port 10002 is "
+"Bob, port \n"
+"10003 is Charlie, and so on, since the protocol includes TCP/IP specific "
+"information\n"
+"(host and port)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:37
+msgid ""
+"General network applications often send a lot of additional data that "
+"could be used to identify users.\n"
+"Hostnames, port numbers, time zones, character sets, etc. are often sent "
+"without informing the user.\n"
+"As such, designing the network protocol specifically with anonymity in "
+"mind\n"
+"can avoid compromising user identities."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:43
+msgid ""
+"There are also efficiency considerations to review when determining how "
+"to \n"
+"interact on top of I2P.  The streaming library and things built on top of"
+" it\n"
+"operate with handshakes similar to TCP, while the core I2P protocols "
+"(I2NP and I2CP)\n"
+"are strictly message based (like UDP or in some instances raw IP).  The "
+"important\n"
+"distinction is that with I2P, communication is operating over a long fat "
+"network - \n"
+"each end to end message will have nontrivial latencies, but may contain "
+"payloads \n"
+"of up to several KB.  An application that needs a simple request and "
+"response can get rid\n"
+"of any state and drop the latency incurred by the startup and teardown "
+"handshakes\n"
+"by using (best effort) datagrams without having to worry about MTU "
+"detection or \n"
+"fragmentation of messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:57
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid ""
+"Creating a server-client connection using I2PTunnel only requires "
+"creating a single tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid "Figure 1:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:64
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid ""
+"Setting up connections for a peer-to-peer applications requires a very "
+"large amount of tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid "Figure 2:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:70
+msgid "In summary, a number of reasons to write I2P-specific code:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:74
+msgid ""
+"Creating a large amount of I2PTunnel instances consumes a non-trivial "
+"amount of resources,\n"
+"which is problematic for distributed applications (a new tunnel is "
+"required for each peer)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:78
+msgid ""
+"General network protocols often send a lot of additional data that can be"
+" used to identify users.\n"
+"Programming specifically for I2P allows the creation of a network "
+"protocol\n"
+"that does not leak such information, keeping users anonymous and secure."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:83
+msgid ""
+"Network protocols designed for use on the regular internet can be "
+"inefficient\n"
+"on I2P, which is a network with a much higher latency."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:90
+#, python-format
+msgid ""
+"I2P supports a standard plugins interface for"
+" developers\n"
+"so that applications may be easily integrated and distributed."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:96
+msgid ""
+"Applications written in Java and accessible/runnable\n"
+"using an HTML interface via the standard webapps/app.war\n"
+"may be considered for inclusion in the i2p distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:104
+msgid "There are a few changes that require adjusting to when using I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:108
+msgid "Destination ~= host+port"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:110
+msgid ""
+"An application running on I2P sends messages from and receives messages "
+"to a\n"
+"unique cryptographically secure end point - a \"destination\".  In TCP or"
+" UDP\n"
+"terms, a destination could (largely) be considered the equivalent of a "
+"hostname\n"
+"plus port number pair, though there are a few differences."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:118
+msgid ""
+"An I2P destination itself is a cryptographic construct - all data sent to"
+" one is \n"
+"encrypted as if there were universal deployment of IPsec with the "
+"(anonymized)\n"
+"location of the end point signed as if there were universal deployment of"
+" DNSSEC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:123
+msgid ""
+"I2P destinations are mobile identifiers - they can be moved from one I2P "
+"router\n"
+"to another (or it can even \"multihome\" - operate on multiple routers at"
+"\n"
+"once).  This is quite different from the TCP or UDP world where a single "
+"end point (port)\n"
+"must stay on a single host."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:130
+msgid ""
+"I2P destinations are ugly and large - behind the scenes, they contain a "
+"2048 bit ElGamal\n"
+"public key for encryption, a 1024 bit DSA public key for signing, and a "
+"variable size \n"
+"certificate, which may contain proof of work or blinded data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:135
+#, python-format
+msgid ""
+"There are existing ways to refer to these large and ugly destinations by "
+"short\n"
+"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not "
+"guarantee\n"
+"globally uniqueness (since they're stored locally in a database on each "
+"person's machine)\n"
+"and the current mechanism is not especially scalable nor secure (updates "
+"to the host list are\n"
+"managed using \"subscriptions\" to naming services).\n"
+"There may be some secure, human readable, scalable, and globally \n"
+"unique, naming system some day, but applications shouldn't depend upon it"
+" being in place,\n"
+"since there are those who don't think such a beast is possible.\n"
+"Further information on the naming system is "
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:149
+#, python-format
+msgid ""
+"While most applications do not need to distinguish protocols and ports,\n"
+"I2P does support them. Complex applications may specify a "
+"protocol,\n"
+"from port, and to port, on a per-message basis, to multiplex traffic on\n"
+"a single destination.\n"
+"See the datagram page for details.\n"
+"Simple applications operate by listening for \"all protocols\" on \"all "
+"ports\" of a destination."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:158
+msgid "Anonymity and confidentiality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:160
+msgid ""
+"I2P has transparent end to end encryption\n"
+"and authentication for all data passed over the network - if Bob sends to"
+" Alice's destination,\n"
+"only Alice's destination can receive it, and if Bob is using the "
+"datagrams or streaming \n"
+"library, Alice knows for certain that Bob's destination is the one who "
+"sent the data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:167
+msgid ""
+"Of course, I2P transparently anonymizes the\n"
+"data sent between Alice and Bob, but it does nothing to anonymize the "
+"content of what they\n"
+"send.  For instance, if Alice sends Bob a form with her full name, "
+"government IDs, and \n"
+"credit card numbers, there is nothing I2P can do.  As such, protocols and"
+" applications should \n"
+"keep in mind what information they are trying to protect and what "
+"information they are willing\n"
+"to expose."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:176
+msgid "I2P datagrams can be up to several KB"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:178
+#, python-format
+msgid ""
+"Applications that use I2P datagrams (either raw or repliable ones) can "
+"essentially be thought\n"
+"of in terms of UDP - the datagrams are unordered, best effort, and "
+"connectionless - but unlike\n"
+"UDP, applications don't need to worry about MTU detection and can simply "
+"fire off large datagrams.\n"
+"While the upper limit is nominally 32 KB, the message is fragmented for "
+"transport, thus dropping\n"
+"the reliability of the whole. Datagrams over about 10 KB are not "
+"currently recommended.\n"
+"See the datagram page for details.\n"
+"For many applications, 10 KB of data is sufficient for an\n"
+"entire request or response, allowing them to transparently operate in I2P"
+" as a UDP-like \n"
+"application without having to write fragmentation, resends, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:192
+msgid ""
+"There are several means of sending data over I2P, each with their own "
+"pros and cons.\n"
+"The streaming lib is the recommended interface, used by the majority of "
+"I2P applications."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:197
+msgid "Streaming Lib"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:198
+#, python-format
+msgid ""
+"The full streaming library is now the "
+"standard\n"
+"interface. It allows programming using TCP-like sockets, as explained in "
+"the Streaming development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:204
+#, python-format
+msgid ""
+"BOB is the Basic Open Bridge,\n"
+"allowing an application in any language to make streaming connections \n"
+"to and from I2P. At this point in time it lacks UDP support, but UDP "
+"support\n"
+"is planned in the near future. BOB also contains several tools, such as \n"
+"destination key generation, and verification that an address conforms to"
+" \n"
+"I2P specifications. Up to date info and applications that use BOB can be"
+" \n"
+"found at this eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:217
+msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:218
+#, python-format
+msgid ""
+"SAM is the Simple Anonymous Messaging protocol, "
+"allowing an\n"
+"application written in any language to talk to a SAM bridge through a "
+"plain TCP socket and have\n"
+"that bridge multiplex all of its I2P traffic, transparently coordinating "
+"the encryption/decryption\n"
+"and event based handling.  SAM supports three styles of operation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:225
+msgid ""
+"streams, for when Alice and Bob want to send data to each other reliably "
+"and in order"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:228
+msgid ""
+"repliable datagrams, for when Alice wants to send Bob a message that Bob "
+"can reply to"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:231
+msgid ""
+"raw datagrams, for when Alice wants to squeeze the most bandwidth and "
+"performance as possible,\n"
+"and Bob doesn't care whether the data's sender is authenticated or not "
+"(e.g. the data transferred\n"
+"is self authenticating)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:237
+msgid ""
+"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n"
+"multiplexing/demultiplexing. Each I2P stream is handled by its own socket"
+" between the application\n"
+"and the SAM bridge. Besides, datagrams can be sent and received by the "
+"application through datagram\n"
+"communications with the SAM bridge."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:244
+#, python-format
+msgid ""
+"SAM V2 is a new version used by imule\n"
+"that fixes some of the problems in SAM.\n"
+"
            \n"
+"SAM V3 is used by imule since version 1.4.0."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:252
+msgid ""
+"The I2PTunnel application allows applications to build specific TCP-like "
+"tunnels to peers \n"
+"by creating either I2PTunnel 'client' applications (which listen on a "
+"specific port and connect\n"
+"to a specific I2P destination whenever a socket to that port is opened) "
+"or I2PTunnel 'server'\n"
+"applications (which listen to a specific I2P destination and whenever it "
+"gets a new I2P \n"
+"connection it outproxies to a specific TCP host/port).  These streams are"
+" 8-bit clean, and are\n"
+"authenticated and secured through the same streaming library that SAM "
+"uses, but there is a \n"
+"nontrivial overhead involved with creating multiple unique I2PTunnel "
+"instances, since each have\n"
+"their own unique I2P destination and their own set of tunnels, keys, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:264
+msgid ""
+"I2P supports a SOCKS V4 and V5 proxy.\n"
+"Outbound connections work well. Inbound (server) and UDP functionality "
+"may be incomplete\n"
+"and untested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:271
+msgid "Removed"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:272
+msgid ""
+"There used to be a simple \"ministreaming\" library,\n"
+"but now ministreaming.jar contains only the interfaces for the full "
+"streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:277
+msgid "Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:278
+msgid "Recommended for UDP-like applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:279
+#, python-format
+msgid ""
+"The Datagram library allows sending UDP-"
+"like packets.\n"
+"It's possible to use:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:284
+msgid "Repliable datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:285
+msgid "Raw datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:289
+msgid "Not recommended"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:290
+#, python-format
+msgid ""
+"I2CP itself is a language independent protocol, "
+"but to implement an I2CP library \n"
+"in something other than Java there is a significant amount of code to be "
+"written (encryption routines, \n"
+"object marshalling, asynchronous message handling, etc).  While someone "
+"could write an I2CP library in \n"
+"C or something else, it would most likely be more useful to use the C SAM"
+" library instead."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:297
+msgid "Web Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:298
+msgid ""
+"I2P comes with the Jetty webserver, and configuring to use the Apache "
+"server instead is straightforward.\n"
+"Any standard web app technology should work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:304
+msgid ""
+"Developing using I2P requires a working I2P installation and a "
+"development environment of your own choice.\n"
+"If you are using Java, you can start development with the streaming library or datagram library.\n"
+"Using another programming language, SAM or BOB can be used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:310
+msgid "Developing with the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:312
+msgid ""
+"The following example shows how to create TCP-like client and server "
+"applications\n"
+"using the streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:317
+msgid "This will require the following libraries in your classpath:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:321
+msgid "The streaming library itself"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:322
+msgid "Factory and interfaces for the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:323
+msgid "Standard I2P classes, data structures, API, and utilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:326
+msgid ""
+"Network communication requires the usage of I2P network sockets.\n"
+"To demonstrate this, we will create an application where a client can "
+"send text messages to a server,\n"
+"who will print the messages and send them back to the client. In other "
+"words, the server will function as an echo."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:331
+msgid ""
+"We will start by initializing the server application. This requires "
+"getting an I2PSocketManager\n"
+"and creating an I2PServerSocket.\n"
+"We will not provide the I2PSocketManagerFactory with the saved keys for "
+"an existing Destination,\n"
+"so it will create a new Destination for us.\n"
+"So we will ask the I2PSocketManager for an I2PSession, so we can find out"
+" the Destination that\n"
+"was created, as we will need to copy and paste that information later so "
+"the client can connect to us."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:362
+msgid "Code example 1: initializing the server application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:364
+msgid ""
+"Once we have an I2PServerSocket, we can create I2PSocket instances to "
+"accept connections from clients.\n"
+"In this example, we will create a single I2PSocket instance, that can "
+"only handle one client at a time.\n"
+"A real server would have to be able to handle multiple clients.\n"
+"To do this, multiple I2PSocket instances would have to be created, each "
+"in separate threads.\n"
+"Once we have created the I2PSocket instance, we read data, print it and "
+"send it back to the client.\n"
+"The bold code is the new code we add."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:448
+msgid "Code example 2: accepting connections from clients and handling messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:452
+msgid ""
+"When you run the above server code, it should print something like this "
+"(but without the line endings, it should just be\n"
+"one huge block of characters):"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:466
+msgid ""
+"This is the base64-representation of the server Destination. The client "
+"will need this string to reach the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:470
+msgid ""
+"Now, we will create the client application. Again, a number of steps are "
+"required for initialization.\n"
+"Again, we will need to start by getting an I2PSocketManager.\n"
+"We won't use an I2PSession and an I2PServerSocket this time.\n"
+"Instead, we will use the server Destination string to start our "
+"connection.\n"
+"We will ask the user for the Destination string, and create an I2PSocket "
+"using this string.\n"
+"Once we have an I2PSocket, we can start sending and receiving data to and"
+" from the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:554
+msgid ""
+"Code example 3: starting the client and connecting it to the server "
+"application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:556
+msgid ""
+"Finally, you can run both the server and the client application.\n"
+"First, start the server application. It will print a Destination string "
+"(like shown above).\n"
+"Next, start the client application. When it requests a Destination "
+"string, you can enter the string printed by the server.\n"
+"The client will then send 'Hello I2P!' (along with a newline) to the "
+"server, who will print the message and send it back to the client."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:562
+msgid "Congratulations, you have successfully communicated over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:566
+msgid "Existing Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:567
+msgid "Contact us if you would like to contribute."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:588
+msgid "Application Ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:590
+msgid "NNTP server - there have been some in the past, none at the moment"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:593
+msgid ""
+"Jabber server - there have been some in the past, and there is one at the"
+" moment, with access to the public internet"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:596
+msgid "PGP Key server and/or proxy"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:599
+msgid ""
+"Content Distribution / DHT applications - resurrect feedspace,\n"
+"port dijjer, look for alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:603
+msgid "Help out with Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:606
+msgid ""
+"Web-based applications - The sky is the limit for hosting web-server-"
+"based\n"
+"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n"
+"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:611
+msgid ""
+"Resurrect some old apps, several previously in the i2p source package -\n"
+"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2
+msgid "I2P Developer's MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4
+msgid "MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5
+msgid ""
+"Monotone servers used by the I2P project require two types of keys to be "
+"used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
+msgid ""
+"Commit Keys to sign changes checked-in to the "
+"respository; and"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10
+msgid ""
+"Transport Keys to push changes to remote "
+"servers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13
+#, python-format
+msgid ""
+"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
+"import the\n"
+"developer commit keys, but only Monotone \n"
+"server operators will need to import the transport keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20
+msgid "Developer Commit keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:255
+msgid "Developer Transport Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:256
+#, python-format
+msgid ""
+"Note: Transport keys are only needed for setting up a\n"
+"Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
+msgid "License Agreements"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
+#, python-format
+msgid "For more information see the licenses page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8
+msgid ""
+"Following is a monotonerc file defining the current trust list.\n"
+"Developers must use this file in ~/.monotone/monotonerc or\n"
+"_MTN/montonerc in their i2p.i2p workspace."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17
+msgid "Agreements"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:2
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115
+msgid "Licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:4
+msgid "I2P Software Licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:5
+#, python-format
+msgid ""
+"As required by our\n"
+"threat model (among other reasons), the \n"
+"software developed to support the anonymous communication \n"
+"network we call I2P must be freely available, open source, \n"
+"and user modifiable.  To meet these criteria, we make use of\n"
+"a variety of legal and software engineering techniques so\n"
+"as to remove as many barriers to entry for those considering\n"
+"making use of or contributing to the I2P effort."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:16
+msgid ""
+"While the information below may be more confusing than just simply \n"
+"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
+"the short answer to the question \"How is I2P licensed?\" is this:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:22
+msgid "All software bundled in the I2P distributions will allow:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:24
+msgid "use without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:25
+msgid ""
+"use with no restrictions on how, when, where, why, or by whom is running "
+"it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:26
+msgid "access to the source code without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:27
+msgid "modifications to the source"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:30
+msgid ""
+"Most of the software guarantees much more - the ability of anyone "
+"to \n"
+"distribute the modified source however they choose.  However, not all of "
+"the \n"
+"software bundled provides this freedom - the GPL restricts the ability of"
+" \n"
+"developers who wish to integrate I2P with their own applications that are"
+" not \n"
+"themselves open source applications.  While we applaud the noble goals of"
+" \n"
+"increasing the resources in the commons, I2P is best served by removing "
+"any\n"
+"barriers that stand in the way of its adoption - if a developer "
+"considering whether\n"
+"they can integrate I2P with their application has to stop and check with "
+"their lawyer,\n"
+"or conduct a code audit to make sure their own source can be released as "
+"GPL-compatible,\n"
+"we lose out."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:43
+msgid "Component licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:44
+msgid ""
+"The I2P distribution contains several resources, reflecting the "
+"partitioning of \n"
+"the source code into components.  Each component has its own license, "
+"which all \n"
+"developers who contribute to it agree to - either by explicitly declaring"
+" the release\n"
+"of code committed under a license compatible with that component, or by "
+"implicitly\n"
+"releasing the code committed under the component's primary license.  Each"
+" of these \n"
+"components has a lead developer who has the final say as to what license "
+"is compatible\n"
+"with the component's primary license, and the I2P project manager has the"
+" final say as\n"
+"to what licenses meet the above four guarantees for inclusion in the I2P "
+"distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:57
+msgid "Component"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:58
+msgid "Source path"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:59
+msgid "Resource"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:60
+msgid "Primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:61
+msgid "Alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:62
+msgid "Lead developer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:271
+msgid "GPL + java exception"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:272
+#, python-format
+msgid ""
+"While it may be redundant, just for clarity the\n"
+"GPL'ed code included within\n"
+"I2PTunnel and other apps must be released under the GPL with an "
+"additional \"exception\"\n"
+"explicitly authorizing the use of Java's standard libraries:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:288
+msgid ""
+"All source code under each component will by default be licensed under "
+"the\n"
+"primary license, unless marked otherwise in the code.  All of the above "
+"is\n"
+"summary of the license terms - please see the specific license for the "
+"component\n"
+"or source code in question for authoritative terms.  Component source "
+"locations and\n"
+"resource packaging may be changed if the repository is reorganized."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:296
+msgid "Commit privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:297
+#, python-format
+msgid ""
+"Developers may push changes to a distributed monotone repository if you\n"
+"receive permission from the person running that repository.\n"
+"See the Monotone Page for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:303
+msgid ""
+"However, to have changes included in a release, developers\n"
+"must be trusted by the release manager (currently zzz).\n"
+"In addition, they must explicitly agree with the above terms to be "
+"trusted.\n"
+"That means that they must send one of the release managers a signed "
+"message affirming that:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:310
+msgid ""
+"Unless marked otherwise, all code I commit is implicitly licensed under\n"
+"the component's primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:314
+msgid ""
+"If specified in the source, the code may be explicitly licensed under one"
+"\n"
+"of the component's alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:318
+msgid ""
+"I have the right to release the code I commit under the terms I\n"
+"am committing it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:324
+#, python-format
+msgid ""
+"If anyone is aware of any instances where the above conditions are not "
+"met,\n"
+"please contact the component lead and/or an I2P release manager with "
+"further\n"
+"information.\n"
+"See developers' license agreements."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
+msgid "Release Signing Key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
+msgid "Releases 0.7.6 and later are signed by zzz. His public key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40
+msgid ""
+"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public "
+"key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2
+msgid "Signed Developer Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4
+msgid ""
+"Keys for zzz, Complication and welterde are provided clearsigned. The key"
+" for jrandom must be\n"
+"verified differently, since he's away, and only left a binary detached\n"
+"signature for his key."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16
+msgid "Monotone keys for zzz"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47
+msgid "Monotone keys for welterde"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79
+msgid "Monotone keys for Complication"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114
+msgid "Monotone keys for jrandom"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
+msgid "Others"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
+msgid ""
+"Tip: To find zzz's GPG key, on his eepsite locate the key "
+"`0xA76E0BED`, with\n"
+"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 "
+"B310 4155\n"
+"76BA A76E 0BED`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49
+msgid ""
+"Tip: To find welterde's GPG key, on public keyservers locate the "
+"key\n"
+"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720"
+" FD81\n"
+"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81
+msgid ""
+"Tip: To find Complication's GPG key, on his eepsite locate the key"
+"\n"
+"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint "
+"`73CF\n"
+"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116
+msgid ""
+"Tip: To find jrandom's GPG key for Syndie releases, on public "
+"keyservers locate\n"
+"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n"
+"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122
+msgid ""
+"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n"
+"deployed in the Syndie Monotone repository, in a file named `mtn-"
+"committers`.\n"
+"That file also had a GPG signature, `mtn-committers.sig`, but it was a "
+"binary\n"
+"detached signature. I am going to supply both files in GPG ASCII-armoured"
+" form\n"
+"below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130
+msgid ""
+"First, the file `mtn-committers` containing jrandom's Monotone key. Save "
+"as\n"
+"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers "
+"--dearmor\n"
+"mtn-committers.asc`:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151
+msgid ""
+"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n"
+"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-"
+"committers.sig\n"
+"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n"
+"`mtn-committers` file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170
+#, python-format
+msgid ""
+"Some of the developers have included their Monotone keys in their signed license agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2
+msgid "Developer Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4
+#, python-format
+msgid "Read the new developers guide first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8
+msgid "Basic Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10
+msgid ""
+"Most of the following should be common sense for anybody who has worked "
+"on open source or in a commercial\n"
+"programming envrionment.\n"
+"The following applies mostly to the main development branch i2p.i2p.\n"
+"Guidelines for other branches, plugins, and external apps may be "
+"substantially different;\n"
+"check with the appropriate developer for guidance."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18
+msgid "Community"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20
+msgid ""
+"Please don't just \"write code\". If you can, participate in other "
+"development activities, including:\n"
+"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
+"testing;\n"
+"bug reporting and responses; documentation; code reviews; etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25
+msgid ""
+"Active devs should be available periodically on IRC #i2p-dev.\n"
+"Be aware of the current release cycle.\n"
+"Adhere to release milestones such as feature freeze, tag freeze, and\n"
+"the checkin deadline for a release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35
+msgid ""
+"Have a basic understanding of distributed source control systems, even if"
+" you haven't\n"
+"used monotone before. Ask for help if you need it.\n"
+"Once pushed, checkins are forever, there is no undo. Please be careful.\n"
+"If you have not used monotone before, start with baby steps.\n"
+"Check in some small changes and see how it goes."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42
+msgid ""
+"Test your changes before checking them in.\n"
+"If you prefer the checkin-before-test development model,\n"
+"use your own development branch (e.g. i2p.i2p.yourname.test)\n"
+"and propagate back to i2p.i2p once it is working well.\n"
+"Do not break the build. Do not cause regressions.\n"
+"In case you do (it happens), please do not vanish for a long period after"
+"\n"
+"you push your change."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51
+msgid ""
+"If your change is non-trivial, or you want people to test it and need "
+"good test reports\n"
+"to know whether your change was tested or not, add a checkin comment to "
+"history.txt\n"
+"and increment the build revision in RouterVersion.java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56
+msgid ""
+"Ensure that you have the latest monotonerc file in _MTN.\n"
+"Do not check in on top of untrusted revisions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60
+msgid ""
+"Ensure that you pull the latest revision before you check in.\n"
+"If you inadvertently diverge, merge and push as soon as possible.\n"
+"Don't routinely make others merge for you.\n"
+"Yes, we know that monotone says you should push and then merge,\n"
+"but in our experience, in-workspace merge works just as well as in-"
+"database merge,\n"
+"without creating a merge revision."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
+msgid ""
+"Do not check in major changes into the main i2p.i2p branch late in the "
+"release cycle.\n"
+"If a project will take you more than a couple days, create your own "
+"branch in monotone\n"
+"and do the development there so you do not block releases."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75
+msgid "Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77
+msgid ""
+"Coding style throughout most of the code is 4-spaces for indentation. Do "
+"not use tabs.\n"
+"Do not reformat code. If your IDE or editor wants to reformat everything,"
+" get control of it.\n"
+"Yes, we know 4 spaces is a pain, but perhaps you can configure your "
+"editor appropriately.\n"
+"In some places, the coding style is different.\n"
+"Use common sense. Emulate the style in the file you are modifying."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84
+msgid ""
+"New classes and methods require at least brief javadocs. Add @since "
+"release-number."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87
+msgid ""
+"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our "
+"official API.\n"
+"There are several out-of-tree plugins and other applications that rely on"
+" this API.\n"
+"Be careful not to make any changes that break compatibility.\n"
+"Don't add methods to the API unless they are of general utility.\n"
+"Javadocs for API methods should be clear and complete.\n"
+"If you add or change the API, also update the documentation on the "
+"website (i2p.www branch)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95
+msgid ""
+"Tag strings for translation where appropriate.\n"
+"Don't change existing tagged strings unless really necessary, as it will "
+"break existing translations.\n"
+"Do not add or change tagged strings after the \"tag freeze\" in the "
+"release cycle so that\n"
+"translators have a chance to update before the release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101
+msgid ""
+"Use generics and concurrent classes where possible. I2P is a highly "
+"multi-threaded application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104
+msgid ""
+"We require Java 6 to build but only Java 5 to run I2P.\n"
+"Do not use Java 6 classes or methods without handling the class not found"
+" exceptions\n"
+"and providing alternate Java 5 code. See classes in net.i2p.util for "
+"examples."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109
+msgid ""
+"Explicitly convert between primitive types and classes;\n"
+"don't rely on autoboxing/unboxing."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117
+msgid ""
+"Only check in code that you wrote yourself.\n"
+"Before checking in any code or library jars from other sources,\n"
+"justify why it is necessary,\n"
+"verify the license is compatible,\n"
+"and obtain approval from the lead developer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124
+msgid ""
+"For any images checked in from external sources,\n"
+"it is your responsibility to first verify the license is compatible.\n"
+"Include the license and source information in the checkin comment."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131
+msgid "Bugs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
+#, python-format
+msgid ""
+"Managing Trac tickets is everybody's job, please help.\n"
+"Monitor %(trac)s for tickets you have been assigned or can help with.\n"
+"Assign, categorize, comment on, fix, or close tickets if you can."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138
+msgid ""
+"Close a ticket when you think you've fixed it.\n"
+"We don't have a test department to verify and close tickets.\n"
+"If you arent sure you fixed it, close it and add a note saying\n"
+"\"I think I fixed it, please test and reopen if it's still broken\".\n"
+"Add a comment with the dev build number or revision and set\n"
+"the milestone to the next release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:2
+msgid "Using an IDE with I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:4
+msgid ""
+"The main I2P development branch (i2p.i2p) has been set up to"
+" enable developers to easily set up two of the commonly-used IDEs for "
+"Java development: Eclipse and NetBeans."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:10
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain .project and .classpath Eclipse files, to enable the branch "
+"to be easily set up in Eclipse."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:16
+msgid ""
+"Check out the I2P branch into some directory (e.g. "
+"$HOME/dev/i2p.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:20
+msgid ""
+"Open Eclipse and create a new Workspace, based in the directory that the "
+"I2P branch was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:24
+msgid ""
+"Select \"File - Import...\" and then under \"General\" select \"Existing "
+"Projects into Workspace\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:28
+msgid ""
+"For \"Select root directory:\" choose the directory that the I2P branch "
+"was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:32
+msgid "If necessary, click \"Refresh\" to refresh the list of projects."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:36
+msgid "Select every project in the list, and click \"Finish\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:40
+msgid ""
+"Done! Your workspace should now contain all projects within the I2P "
+"branch, and their build dependencies should be correctly set up."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:48
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain NetBeans project files."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:2
+msgid "Monotone"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:4
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:9
+msgid "Operating a Monotone client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:11
+#: i2p2www/pages/site/get-involved/guides/monotone.html:63
+msgid "Generating Monotone keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:12
+msgid "Trust and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:13
+#: i2p2www/pages/site/get-involved/guides/monotone.html:196
+msgid "Obtaining and deploying developers' keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:14
+#: i2p2www/pages/site/get-involved/guides/monotone.html:227
+msgid "Setting up trust evaluation hooks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:15
+#: i2p2www/pages/site/get-involved/guides/monotone.html:268
+msgid ""
+"Pulling the i2p.i2p, i2p.www and "
+"i2p.syndie branches"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:16
+#: i2p2www/pages/site/get-involved/guides/monotone.html:308
+msgid "Verifying that trust evaluation works"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:17
+#: i2p2www/pages/site/get-involved/guides/monotone.html:357
+msgid "Checking out a working copy of the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:18
+#: i2p2www/pages/site/get-involved/guides/monotone.html:384
+msgid "Updating your working copy to the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:22
+#: i2p2www/pages/site/get-involved/guides/monotone.html:414
+msgid "Operating a Monotone Server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:24
+msgid "Obtaining and deploying developers’ transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:25
+#: i2p2www/pages/site/get-involved/guides/monotone.html:424
+msgid "Granting push and pull access"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:26
+#: i2p2www/pages/site/get-involved/guides/monotone.html:469
+msgid "Running Monotone in server mode"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:27
+#: i2p2www/pages/site/get-involved/guides/monotone.html:494
+msgid "Differences under Debian GNU/Linux"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:34
+#, python-format
+msgid ""
+"This is a revised version of Complication's original\n"
+"  guide detailing the use of Monotone in I2P development.\n"
+"  For basic instructions see the quick-start "
+"guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:42
+#, python-format
+msgid ""
+"I2P has a distributed development model. The source code is replicated "
+"across\n"
+"  independently administered Monotone (\"MTN\") repositories.\n"
+"  Developers with commit rights are able to push their changes to the "
+"repository\n"
+"  (a license agreement needs to be "
+"signed\n"
+"  before commit rights are granted)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:52
+msgid ""
+"Some of Monotone's noteworthy qualities are: distributed\n"
+"  version control, cryptographic authentication, access control, its "
+"small size, having few\n"
+"  dependencies, storage of projects in a compressed SQLite database file,"
+" and\n"
+"  having the ability to resume interrupted synchronization attempts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:61
+msgid "Operating a Monotone Client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:66
+msgid ""
+"A transport key grants you the ability to push your changes to a Monotone"
+" repository server.\n"
+"  In order to commit code into Monotone (in essence signing your code), a"
+" commit key is also needed.\n"
+"  None of the public Monotone servers on I2P currently require a key in "
+"order to read (or pull) the source code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:74
+msgid ""
+"Without a transport key, one cannot:\n"
+"  
              \n"
+"    
            • pull code from a server which doesn't allow global read "
+"access
              • \n"
+"    
            • push code to any server
              • \n"
+"    
            • run a Monotone server
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:85
+msgid ""
+"Without a commit key, one cannot:\n"
+"  
              \n"
+"    
            • commit any code
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:94
+msgid ""
+"If you only intend to retrieve code from MTN, feel free to skip to the\n"
+"  next section. "
+"If you want\n"
+"  to generate keys, read the following."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:102
+msgid ""
+"By convention keys are named like an e-mail addresses, but a "
+"corresponding e-mail\n"
+"  address does not need to exist. For example, your keys might be named:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:113
+msgid ""
+"Monotone stores keys under $HOME/.monotone/keys in "
+"text files which\n"
+"  are named identically to the keys. For example:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:123
+msgid ""
+"To generate transport and commit keys, enter the following commands at a "
+"prompt:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:133
+msgid ""
+"Monotone will prompt you for a password to protect your keys. You are "
+"very strongly encouraged to set a password\n"
+"  for the commit key. Many users will leave an empty password for the "
+"transport key, especially those running a\n"
+"  Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:141
+msgid "Trust, and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:145
+msgid ""
+"Monotone's security model helps to ensure that nobody can easily "
+"impersonate a developer without\n"
+"  it being noticed. Since developers can make mistakes and become "
+"compromised,only manual review can\n"
+"  ensure quality of code. Monotone's trust model will ensure that you "
+"read the right diffs. It does\n"
+"  not replace reading diffs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:155
+msgid ""
+"A Monotone repository is a single file (a compressed SQLite database) "
+"which contains all of the project's source code and history."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:161
+msgid ""
+"After importing the "
+"developers' keys into Monotone and\n"
+"  setting up trust "
+"evaluation hooks,\n"
+"  Monotone will prevent untrusted code from being checked out into your "
+"workspace.\n"
+"  There are commands available to clean untrusted code from your "
+"workspace but in practice they've not been\n"
+"  needed due to the push access policies in place."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:171
+msgid ""
+"A repository can hold many branches. For example, our repository holds "
+"the\n"
+"  following main branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:176
+msgid "The I2P router and associated programs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:177
+msgid "The I2P project website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:178
+msgid "Syndie, a distributed forums tool"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:183
+msgid ""
+"By convention, the I2P Monotone repository is named i2p.mtn."
+" Before pulling\n"
+"  source code from servers, a database for your repository will need to "
+"be initialized.\n"
+"  To initialize your local repository, change into the directory that you"
+" want the\n"
+"  i2p.mtn file and branch directories to be stored and issue"
+" the following\n"
+"  command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:199
+msgid ""
+"Keys which developers use to commit code are essential for trust "
+"evaluation in\n"
+"  Monotone. The other developers' transport keys are only required for "
+"Monotone server operators.\n"
+"  "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:206
+#, python-format
+msgid ""
+"Developers' commit keys are provided GPG-signed on another page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:212
+#, python-format
+msgid ""
+"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
+"  file. Create this file (e.g. keys.txt) in the same "
+"directory where i2p.mtn is located. Import the keys with the"
+" command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:222
+msgid ""
+"Note: Never add keys to "
+"$HOME/.monotone/keys manually."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:230
+msgid ""
+"The default Monotone trust policy is way too lax for our requirements: "
+"every committer is trusted by default.\n"
+"  That is not acceptable for I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:237
+msgid ""
+"Change into the directory $HOME/.monotone and open "
+"the file\n"
+"  monotonerc with a text editor. Copy and paste the "
+"following two functions into this file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:246
+msgid ""
+"The first function determines an intersection between two sets, in our "
+"case a\n"
+"  revision's signers and trusted signers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:253
+msgid ""
+"The second function determines trust in a given revision, by calling the "
+"first\n"
+"  function with \"signers\" and \"trusted\" as arguments. If the "
+"intersection is\n"
+"  null, the revision is not trusted. If the intersection is not empty, "
+"the\n"
+"  revision is trusted. Otherwise, the revision is not trusted."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:262
+msgid ""
+"More information about Trust Evauluation Hooks can be found in the official Monotone "
+"documentation."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:271
+msgid ""
+"Enter the directory where you initialized i2p.mtn. Depending "
+"on whether you\n"
+"  want only I2P sources, or also sources for the I2P website and Syndie, "
+"you can\n"
+"  perform the pull operation in different ways."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:279
+msgid "If you only want I2P sources:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:288
+msgid "If you want all branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:294
+msgid ""
+"If the transfer aborts before completing sucessfully, simply repeating "
+"the pull command will resume the transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:300
+msgid ""
+"Pulling in the above examples is done anonymously by specifying an empty "
+"transport key.\n"
+"  If everyone pulls anonymously it will be harder for an attacker who "
+"gains control of the server\n"
+"  to selectively provide some people with tampered data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:311
+msgid "To verify that trust evaluation works:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:315
+msgid "Make a backup of your monotonerc file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:316
+msgid ""
+"Modify monotonerc by setting the trusted_signers "
+"variable in the following way:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:322
+msgid ""
+"With monotonerc configured as above, Monotone will no"
+" longer trust any committers. Confirm this by changing into the\n"
+"directory where i2p.mtn was created and attempt a checkout "
+"of the I2P branch:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:332
+msgid ""
+"A directory named i2p.i2p should not appear. You "
+"should encounter many\n"
+"  error messages like:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:349
+msgid ""
+"If you are satisfied with results, restore the backup of\n"
+"  monotonerc that was created above. If you didn't create a "
+"backup\n"
+"  as advised, re-read Setting up trust evaluation hooks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:360
+msgid ""
+"If you already have a branch checked out, skip to the next\n"
+"  section."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:367
+msgid ""
+"Change into the directory where i2p.mtn is located. Over "
+"there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:376
+msgid ""
+"The checkout should complete without error messages and a directory named"
+"\n"
+"  i2p.i2p should appear in the current directory. "
+"Congratulations! You have\n"
+"  successfully checked out the latest I2P sources, ready to be compiled."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:387
+msgid ""
+"If you haven't done this already, pull fresh code from the server to your"
+" local\n"
+"  Monotone repository. To accomplish this, change into the directory "
+"where\n"
+"  i2p.mtn is located and issue:\n"
+"  
              \n"
+"    
            • $ mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
+"i2p.i2p
              • \n"
+"  
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:398
+msgid "Now change into your i2p.i2p directory, and over there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:407
+msgid ""
+"As long as there were no errors…Congratulations! You have "
+"successfully updated to the latest I2P sources. They\n"
+"  should be ready to compile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:416
+msgid "Obtaining and deploying developers' transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:419
+msgid ""
+"As a server operator you may want to grant push access to certain "
+"developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:427
+msgid "By default the Monotone server denies all access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:433
+msgid "To grant pull access to all clients, set the following in"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:445
+msgid ""
+"No one will not be able to push code to your server without permission "
+"being explicitly granted. To grant push access:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:451
+msgid ""
+"Add the name of the user's transport key to\n"
+"$HOME/.monotone/write-permissions, such as\n"
+"
            \n"
+"    zzz-transport@mail.i2p\n"
+"    complication-transport@mail.i2p\n"
+"
            \n"
+"with one key per line."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:462
+msgid ""
+"Import the transport key(s) into your database. The procedure for "
+"importing transport keys is the same as for\n"
+"importing commit keys, which is described in the section Obtaining and deploying "
+"developers' keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:472
+msgid ""
+"A separate database should be used for your Monotone server because "
+"monotone will lock the database while it is served to others.\n"
+"  Make a copy of your development database, then start the server with:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:479
+msgid ""
+"If your key is protected with a passphrase, Monotone may request the "
+"passphrase\n"
+"  when the first client connects. You can work around this by connecting "
+"making the first client connection to your server\n"
+"  (or by clearing the password for your transport key)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:487
+msgid ""
+"For your server to be accessible for others over I2P, you will need to "
+"create a\n"
+"  server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" "
+"profile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:497
+msgid ""
+"Debian (amongst other distributions) has integrated Monotone into their\n"
+"  framework of daemons/services. Although Monotone servers can still be "
+"run\n"
+"  \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may"
+" be more straightforward."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:505
+msgid ""
+"Permissions are granted by editing the files\n"
+"  /etc/monotone/read-permissions and\n"
+"  /etc/monotone/write-permissions. You'll also need to edit\n"
+"  /etc/default/monotone to enable monotone to start at boot "
+"or to\n"
+"  customize the host, port, or database location."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
+msgid "New Developer's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
+msgid ""
+"\n"
+"So you want to start work on I2P? Great!\n"
+"Here's a quick guide to getting started\n"
+"on contributing to the website or the software, doing development or "
+"creating translations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
+#, python-format
+msgid ""
+"\n"
+"Not quite ready for coding?\n"
+"Try getting involved first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
+msgid "Basic study"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
+msgid "Getting the I2P code"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
+msgid "Building I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
+msgid "Development ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
+msgid "Making the results available"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
+msgid "Get to know us!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
+msgid "Translations"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
+msgid "Tools"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
+msgid ""
+"Basic development on the I2P router or the embedded applications uses "
+"Java as the main development language.\n"
+"If you don't have experience with Java, you can always have a look at Thinking in Java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
+#, python-format
+msgid ""
+"Study the how intro,\n"
+"the other \"how\" documents,\n"
+"the tech intro,\n"
+"and associated documents.\n"
+"These will give you a good overview of how I2P is structured and what "
+"different things it does."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
+msgid ""
+"For development on the i2p router or the embedded applications,\n"
+"get the monotone source repository installed - short instructions:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
+msgid ""
+"Install monotone.\n"
+"Monotone is a version control system.\n"
+"We use it because it allows us to keep track of who does what changes to "
+"the source code (and for a lot of complicated things, but 'keeping track "
+"of changes' is the basic idea)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
+msgid ""
+"Skim over the monotone tutorial,"
+" to make sure you understand the concepts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
+msgid ""
+"If you want to remain anonymous, you need to do an additional step, to "
+"set up a connection to a monotone server over I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
+#, python-format
+msgid ""
+"Enable the i2ptunnel client tunnel on port "
+"8998 pointing to mtn.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
+msgid ""
+"Pick a directory where you want to put all your I2P files, and create a "
+"monotone database:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
+msgid ""
+"Define the trust list by creating ~/.monotone/monotonerc (or"
+" _MTN/monotonerc in the i2p.i2p workspace) with the "
+"following contents:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
+#, python-format
+msgid ""
+"Copy and paste the developer's commit keys "
+"into a new file (e.g. keys.txt) in the same directory\n"
+"  that i2p.mtn is in. Import the keys into your database "
+"with 
                  mtn -d i2p.mtn read < keys.txt
            "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:76
+msgid ""
+"Pull the I2P sources to your machine. This may take a long time, "
+"especially if you are doing this over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:78
+msgid "Anonymously:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:81
+msgid "Non-anonymously:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:83
+msgid ""
+"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn"
+".i2p-projekt.de."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:90
+msgid ""
+"All the sources are now present on your machine, in the database file. To"
+" make them available in a directory, you need to check them out:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:92
+msgid ""
+"The above command creates a directory i2p.i2p, which contains all of the "
+"I2P sources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:96
+msgid "Remarks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:97
+msgid ""
+"\n"
+"To download the website files instead of the I2P source files, use "
+"'i2p.www' instead of 'i2p.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:100
+msgid ""
+"The initial pull may take several hours using the tunnel.\n"
+"If it fails after a partial pull, simply rerun it, it will start where it"
+" left off.\n"
+"If you are in a hurry, use the non-anonymous access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:105
+#, python-format
+msgid ""
+"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
+#, python-format
+msgid ""
+"A long explanation about using monotone is available on the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
+#, python-format
+msgid ""
+"To compile the code, you need the Sun Java Development Kit 6 or higher, "
+"or equivalent JDK\n"
+"(Sun JDK 6 strongly recommended) and\n"
+"Apache ant\n"
+"version 1.7.0 or higher.\n"
+"If you go are working on the main I2P code, you can go into the i2p.i2p "
+"directory and run 'ant' to see the build options."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
+msgid ""
+"To build or work on console translations, you need\n"
+"the xgettext, msgfmt, and msgmerge tools from the\n"
+"GNU gettext package."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
+#, python-format
+msgid ""
+"For development on new applications,\n"
+"see the application development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
+#, python-format
+msgid ""
+"See zzz's TODO lists,\n"
+"this website's TODO list or\n"
+"Trac\n"
+"for ideas."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
+#, python-format
+msgid ""
+"See the bottom of the licenses page "
+"for\n"
+"commit privilege requirements. You need these to put code into i2p.i2p "
+"(not required for the website!)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
+msgid "Short version of how to generate and use keys if you plan to commit:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
+msgid "use an empty passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
+msgid "enter a passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
+#, python-format
+msgid ""
+"send this to a mtn repo operator to get "
+"push privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
+#, python-format
+msgid ""
+"send this to a release manager to get "
+"commit privileges - not required for website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
+msgid "check in with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
+msgid "push with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
+#, python-format
+msgid "Long version: see the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
+#, python-format
+msgid ""
+"The developers hang around on IRC. They can be reached on the Freenode "
+"network, OFTC, and on the I2P internal networks. The usual place to look "
+"is #i2p-dev. Join the channel and say hi!\n"
+"We also have additional guidelines for regular"
+" developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
+#, python-format
+msgid ""
+"Website and router console translators: See the New Translator's Guide\n"
+"for next steps."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
+msgid ""
+"I2P is open source software that is mostly developed using open sourced\n"
+"toolkits. The I2P project recently acquired a license for the YourKit "
+"Java\n"
+"Profiler. Open source projects are eligible to receive a free license "
+"provided\n"
+"that YourKit is referenced on the project web site. Please get in touch "
+"if you\n"
+"are interested in profiling the I2P codebase."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
+#, python-format
+msgid ""
+"YourKit is kindly supporting open source projects with its full-featured "
+"Java Profiler.\n"
+"YourKit, LLC is the creator of innovative and intelligent tools for "
+"profiling\n"
+"Java and .NET applications. Take a look at YourKit's leading software "
+"products:\n"
+"YourKit Java Profiler and\n"
+"YourKit .NET Profiler."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
+msgid "New Translator's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
+msgid "Here's a very quick guide to getting started."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
+msgid "How to Translate the Website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
+#, python-format
+msgid ""
+"Translation of the website is done with .po files. The easiest way by far"
+" to\n"
+"translate the website is to sign up for an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
+msgid "Preparation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
+#, python-format
+msgid ""
+"Come to #i2p-dev on irc and talk to people.\n"
+"Claim the language -\n"
+"To make sure other coworkers don't bump onto the files you are working "
+"on,\n"
+"please update the translation status on this wiki "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"Including the installation of monotone,\n"
+"checking out i2p.www branch, and generate your own monotone keys.\n"
+"It is not required that you sign a dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
+msgid ""
+"Run \"./extract-messages.sh\" to generate a "
+"messages.pot in the base directory.\n"
+"Edit the header of this file, then run \"./init-new-po.sh "
+"locale\" to generate the file\n"
+"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
+"\"mtn add\" this file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
+msgid ""
+"Edit i2p2www/pages/global/lang.html and add a line for your "
+"language (copy an existing line)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
+msgid ""
+"Add a flag image file to i2p2www/static/images/flags/ for "
+"the menu (copy from the router)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
+msgid ""
+"Edit files:\n"
+"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
+msgid ""
+"Check in:\n"
+"\"mtn pull\", \"mtn update\". Then check in by "
+"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
+"This collects the diff info of your changed file into your local repo. "
+"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
+"i2p.i2p\".\n"
+"This synchronizes your local repo with the repo on the target machine."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
+msgid "Repeat. Check in often. Don't wait until it is perfect."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
+msgid "How to Translate the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
+#, python-format
+msgid ""
+"The easiest way by far to translate the router console is to sign up for "
+"an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"including the installation of monotone and the gettext tools,\n"
+"checking out i2p.i2p branch, and generate your own monotone keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
+msgid "Generate your own gpg key and sign the dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
+msgid ""
+"Before starting a console translation, better help translate some i2p "
+"webpages first.\n"
+"At least an i2p homepage in your language would be great."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
+msgid ""
+"What to translate:\n"
+"There are about 15 files in the i2p.i2p branch that needs translation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
+msgid ""
+"Where xx is your language code like fr/de/ch/zh/...\n"
+"There may be or may not be files with your lang code. If not, you can "
+"create your own. by copying and renaming other language files you know "
+"with your own lang code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet, copy another language "
+"file to a new file foo_xx.bar for your language.\n"
+"Then \"mtn add\" the file.\n"
+"After creating a .po file, edit the headers. Then run \"ant "
+"distclean poupdate\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
+msgid ""
+"Start to work:\n"
+"Edit the HTML files with any text editor.\n"
+"Be sure not to use an editor in HTML mode that reformats everything.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
+msgid ""
+"As you can see, it's not that difficult.\n"
+"If you have questions about the meaning of the terms in the console, ask "
+"in #i2p-dev on IRC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
+msgid "FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
+msgid ""
+"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
+"and html, etc.? Why can't I just do a translation and email it to you?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
+msgid "A: Several reasons:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
+#, python-format
+msgid ""
+"You might be interested in translating via Transifex. Request to join a "
+"translation team here."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
+msgid ""
+"We don't have anybody who has time to accept manual contributions and "
+"submit them to our source control system on your behalf. Even if we did, "
+"it doesn't scale."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
+msgid ""
+"Maybe you are thinking translation is a one-step process. It isn't. You "
+"can't do it all at once. You will make mistakes. You need to test it and "
+"tweak it to make it look right before you submit it. Developers "
+"will update or add to the English text, thus requiring a translation "
+"update."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
+msgid ""
+"Having translators use a source control system directly provides "
+"authentication and accountablility - we know who is doing what, and we "
+"can track changes, and revert them if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
+msgid ""
+".po files are not difficult. If you don't want to work directly with "
+"them, we recommend 'poedit'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
+msgid ""
+"HTML files are not difficult. Just ignore the html stuff and translate "
+"the text."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
+msgid ""
+"Installing and using monotone is not that difficult. Several of the "
+"translators and other contributors to I2P are non-programmers, and they "
+"use monotone regularly. Monotone is simply a source control system, it is"
+" not about \"coding\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
+msgid ""
+"Our items to translate are not \"documents\". They are html files and po "
+"files, with a specific format and character encoding (UTF-8) that must be"
+" maintained, and not corrupted by email programs or other methods of "
+"transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
+msgid ""
+"We looked at 'pootle' as a front-end for translators. It didn't work "
+"well, needed an administrator, and a pootle-based process would suffer "
+"from a number of the above flaws."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
+msgid ""
+"In summary:\n"
+"Yes, we know it is somewhat of a hurdle to get started. It's really the "
+"only possible way we can do it. Give it a try, it really isn't that hard."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
+msgid "More Information"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
+#, python-format
+msgid ""
+"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
+msgstr ""
+
diff --git a/i2p2www/translations/sv_SE/LC_MESSAGES/misc.po b/i2p2www/translations/sv_SE/LC_MESSAGES/misc.po
new file mode 100644
index 00000000..f16f8fad
--- /dev/null
+++ b/i2p2www/translations/sv_SE/LC_MESSAGES/misc.po
@@ -0,0 +1,1230 @@
+# Swedish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# hottuna , 2013
+# Martin Svensson , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-08-30 23:32+0000\n"
+"PO-Revision-Date: 2013-04-27 23:10+0000\n"
+"Last-Translator: Martin Svensson \n"
+"Language-Team: Swedish (Sweden) "
+"(http://www.transifex.com/projects/p/I2P/language/sv_SE/)\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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: i2p2www/pages/site/misc/jbigi.html:6
+msgid "Overview"
+msgstr ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: i2p2www/pages/site/misc/transition-guide.html:21
+msgid "Guide"
+msgstr ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: 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 ""
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:44
+msgid "Click \"Save\""
+msgstr ""
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:51
+msgid "Add the following line:"
+msgstr ""
+
+#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:55
+msgid "Click \"Apply\""
+msgstr ""
+
+#: 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/sv_SE/LC_MESSAGES/priority.po b/i2p2www/translations/sv_SE/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..90076697
--- /dev/null
+++ b/i2p2www/translations/sv_SE/LC_MESSAGES/priority.po
@@ -0,0 +1,3357 @@
+# Swedish (Sweden) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# samaire , 2013
+# hottuna , 2013
+# Martin Svensson , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-12-01 18:32+0000\n"
+"Last-Translator: samaire \n"
+"Language-Team: Swedish (Sweden) "
+"(http://www.transifex.com/projects/p/I2P/language/sv_SE/)\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/blog/category.html:2
+msgid "Blog Category"
+msgstr "Bloggkategori"
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr "I2P Blogg ATOM Flöde för Kategori: %(category)s"
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:92
+msgid "Blog"
+msgstr "Blogg"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "I2P Blogg ATOM flöde"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr "Skriven %(date)s av %(author)s"
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "Fler blogg-poster…"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr "Skrivet:"
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "Författare:"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Debian I2P Packet"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+"Debian paketen\n"
+"har testats och ska  fungera på x86/x86_64 platformer:"
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr "Ubuntu (Precise 12.04 och senare)"
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr "Debian Linux (Packat och nyare) & kFreeBSD"
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+"I2P packeten kanske fungerar på systemen ej listade ovan. "
+"Vänligen rapportera vid problem\n"
+"med paketen här: Trac at\n"
+"https://trac.i2p2.de."
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Alternativ 1: Nya versioner av Ubuntu och dess "
+"derivat(Testa detta om du inte använder Debian)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr "Alternativ 2: Debian (inklusive Debian-derivat)"
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+"Instruktioner fär Ubuntu Precise Pangolin (och senare) ich derivat som "
+"Linux Mint & Trisquel"
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Lägger till PPA via kommandotolken och installerar I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Öppna en terminal ock skriv:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"Dethär kommandor kommer lägga till PPA:n till /etc/apt/sources.list.d och"
+" hämta den\n"
+"gpg-nyckel som repositoriet har signerats med. GPG-nyckeln försäkrar\n"
+"att paketet inte har fifflats med sedan det byggdes."
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "Meddela din packet-hanterar om det nya PPA:et genom att skriva:"
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+"Dethär kommandot kommer hämta den senaste listan av mjukvara från varje\n"
+"repositorie som används av systemet, inklusive I2P PPA:et som\n"
+"lades till med det tidigare kommandot."
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "Du är nu redo att installera I2P!"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "Lägga till PPA:et Med Synaptic"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+"Öppna Synaptic (System -> Administration -> Synaptic Packet "
+"Hanterare)"
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+"När Synaptic öppnas, välj Repositorier från "
+"Inställnings menyn."
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"Klicka på Andra Källor-tabben och klicka Lägg till. "
+"Klista in ppa:i2p-maintainers/i2pi APT-fälter och klicka "
+"Lägg till källa. Klicka Stäng-knappen och sedan "
+"Ladda Om."
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+"I snabb-filter-boxen, skriv i2p och tryck enter. När "
+"i2p returneras i resultat-listan, högerklicka "
+"i2p och välj Markera för installation. Efter det "
+"gjorts kan du eventuellt se Markera ytterliggare nödvändiga "
+"ändringar?-popup:en. Om det händer, klicka på Markera och "
+"sedan Verkställ"
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+"Efter installationsprocessen blivit färdig kan du gå vidare till nästa\n"
+"del av starta I2P och konfigurera I2P "
+"för ditt system."
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr "Instruktioner för Debian"
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+"Observera: Stegen listade nedan ska utföras med root-åtkomst (i.e., ändra"
+"\n"
+"till root med \"su\" eller genom att lägga till \"sudo\" före varje "
+"kommando). "
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr "Lägg till rader som följande till %(file)s."
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the  key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+"Ladd ner  nyckeln som signerar repositoryn "
+"och lägg till den till apt:"
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr "Meddela din pakethanterare om den nya repositoryn genom att skriva in"
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+"Detta kommando kommer hämta den senaste listan mjukvara från alla\n"
+"repositorys aktiverade på ditt system, inklusive I2P repositoryn som "
+"tillsattes i steg\n"
+"1."
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+"Du är nu redo att installera I2P! Genom att installera i2p-"
+"nyckelrings\n"
+"-paketet försäkras du erhålla uppdateringar till repositoryns GPG-nyckel."
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+"Efter installationprocessen avslutas kan du gå vidare till nästa del av "
+"starta I2P och konfigurera det för "
+"ditt system."
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "Efter-installations arbete"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+"Med hjälp av dessa I2P-packet kan I2P routern startas på följande\n"
+" tre sätt:"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+""på begäran" används i2prouter skriptet. Kör "
+""i2prouter\n"
+" start" från kommandotolken. (Notera: Använd "
+"inte\n"
+"sudo eller använd det som root!)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""på begäran" utan java tjänst wrappern\n"
+"(behövs på Icke-Linux / Icke-x86 system) genom att köra \"i2prouter-nowrapper            \".\n"
+"(Uppmärksamma: Används inte\n"
+"sudo eller kör root!)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"som en tjänst som automatiskt körs när systemet startas, även\n"
+"före inloggning. Tjänsten kan slås på med \"dpkg-reconfigure\n"
+"i2p\" som root eller sudo. Detta är det rekommenderade sättet att "
+"köra I2P."
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+"När du installerar för första gången, kom ihåg att justera din "
+"brandvägg/NAT\n"
+"om du kan. Portarna som ska vidarebefodras finns på sidan förnätverkskonfiguration i "
+"routerkonsolen. Om du behöver hjälp med hur man vidarebefodrar portar, så"
+" kan portforward.com vara till "
+"hjälp."
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"Var god läs igenom och justera bandbreddsinställningar på\n"
+"inställiningssidan,\n"
+"eftersom standardinställningarna 96 KB/s ner / 40 KB/s upp är tämligen "
+"konservativa."
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"Om du vill nå en eepsida via din webbläsare, titta på webbläsar-proxy inställnings-sidan för en "
+"enkel guide."
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Hämta"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Hämta I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Beroende"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+"rekomenderas\n"
+"undantaget Raspberry Pi: Oracle 8 Early "
+"Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Ange din installerade Java-version här\n"
+"eller skriv java -version i terminalen.\n"
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "Rena installationer"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr "välj alternativ länk"
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Hämta den filen och kör den."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Hämta den filen genom att dubbelklicka på den (om det fungerar) eller\n"
+"skriva java -jar i2pinstall_%(i2pversion)s.jar i en terminal"
+" för att köra installeraren.\n"
+"Du kan kanske högerklicka och välja "Öppna med Java"."
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "Kommandotolks (utan skärm) installation:"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Hämta release %(i2pversion)s av den grafiska installeraren för OSX och\n"
+"kör java -jar i2pinstall_%(i2pversion)s.jar -console från "
+"kommandotolken."
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"Hämta den filen och dubbel-klicka på den (om det fungerar) eller\n"
+"skriv java -jar i2pinstall%(i2pversion)s.jar i en terminal "
+"och kör\n"
+"installationen.\n"
+"På vissa platformar kan du behöva högerklicka och välj\n"
+""Öppna med"."
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Hämta den grafiska installerar-filen ovan och\n"
+"kör java -jar i2pinstall_%(i2pversion)s.jar -console från "
+"kommandotolken."
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Packet för Debian & Ubuntu finns."
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+"    The latest dev build is version %(devbuild)s, and is available from\n"
+"    str4d's eepsite."
+msgstr ""
+"Den ovanstående filen är den nuvarande releasen.\n"
+"Den senaste utvecklingsversionen %(devbuild)s, är tillgänglig från\n"
+"str4d's eepsite."
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+"      are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+"      the other."
+msgstr ""
+"Releasen och utvecklings-versioner av I2P APK är inte kompatibla, "
+"eftersom dom är signerade av zzz och str4d respektive. Avinstallera en "
+"före du installerar den andra."
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "Källkods-paket"
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+"    or via Git from git.repo.i2p or Github.\n"
+"    
            \n"
+"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+"Alternativt, så kan du hämta källkoden från monotone eller via Git från git.repo.i2p eller Github.\n"
+"
            \n"
+"Kör code>(tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg)             och sedan antingen kör GUI "
+"installeraren eller den icke-grafiska installeraren som ovan."
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Filerna är signerade av zzz,\n"
+" vars nyckel finns här."
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"I2P kan också hämtas från vår projekt-sida på Launchpad och Google Code."
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"Efter installationsmjukvaran körs på windows, klicka helt enkelt på "
+"\"Start I2P\"-knappen\n"
+"som kommer öppna router "
+"konsolen,\n"
+"som har vidare instruktioner."
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"På Unix-lika system, kan I2P startas som en tjänst,\n"
+"med hjälp av \"i2prouter\" skriptet, som finns i mappen du installerade "
+"I2P i.\n"
+"Byt till den mappen i en kommandotolk och skriv \"sh i2prouter status\"\n"
+"bör berätta om routerns status. Argumenten \"start\", \"stop\" och "
+"\"restart\"\n"
+"kontrollerar tjänsten. Routerkonsolen kan nås från "
+"sin vanliga position.\n"
+"För användare av OpenSolares och andra system för vilka wrappern (i2psvc)"
+" inste stöds,\n"
+"starta routern med \"sh runplain.sh\" istället."
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"När du installlerar för förtsa gången, var god kom ihåg att justera "
+"din NAT/brandvägg\n"
+"om du kan, kom ihåg att de internet nåbara portarna I2P använder,\n"
+"beskrivs här bland andra portar.\n"
+"Om du har lyckats öppna din på för inåtgående TCP, slä även på TCP på\n"
+"instälningssidan."
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"Var också god att läs kika på och justera bandbreddinställningarna"
+" på\n"
+"inställningssidan,\n"
+"eftersom standardinställningartna 96/40 KB/s upp/ner är tämligen "
+"långsamma."
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "Uppdateringar från tidigare releaser:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr "Både automatiska och manuella uppdateringatr är tillgängliga för releasen."
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "Automatiska uppdateringar"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+"Om du kör 0.7.5 eller senare, bör din router hitta\n"
+"den nya releasen. För att uppgradera snabbt, klicka helt enkelt på "
+"\"Hämta uppdatering\"-knappen på din routerkonsol\n"
+"när den syns."
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"På grund av en bugg i 0.7.6, de vars första I2P installation var den "
+"versionen\n"
+"och inte har uppdaterat manuellt\n"
+"kan får ett \"nedladdad version är inte nyare är den nuvarande "
+"versionen\"-fel,\n"
+"och bör använda den manuella uppdatering nedan."
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Om du kör 0.7.4 eller tidigare, var god se\n"
+"0.7.5 releasekommentarerna\n"
+"för viktig information om hur du bör konfigurera din router för att "
+"automatiskt\n"
+"ta emot releasen."
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Om du kör 0.6.1.30 eller tidigare, var god se\n"
+" instruktioner\n"
+"för viktig information om hur du konfigurerar din router för att "
+"automatiskt\n"
+"ta emot releasen."
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+"    router console "
+"allowing\n"
+"    you to download and install the new release by just clicking on that\n"
+"    link."
+msgstr ""
+"Om du har omkonfigurerat din router med hjälp avinstruktioner, bör du se en länk på din\n"
+"routerkonsol som låter\n"
+"dig hämta och installera den nya releasen genom klicka på den\n"
+"länken."
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr "Alternativ, kan du använda den manuella metod som visas under."
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "Manuella uppdateringar"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and rename as i2pupdate.zip.\n"
+"    (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+"    resulting i2pupdate.zip to your I2P installation directory).  You do"
+" \n"
+"    NOT need to unzip that file."
+msgstr ""
+"Hämta den filen till din I2P\n"
+"installations-mapp och byt namn till i2pupdate.zip.\n"
+"(alternativt, du kan hämta källkoden som ovan och kör \"ant updater\", "
+"kopiera sedan den\n"
+"resulterande i2pupdate.zip till din I2P installationsmapp). Du behöver\n"
+"INTE unzippa den filen."
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+"Klicka på \"Starta "
+"om\"."
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "Hämta en kopp kaffe och kom tillbaka om 11 minuter."
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Filen är signerad av zzz,\n"
+" vars nyckel finns här."
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "Tidigare Releaser"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"Tidigare releaser finns tillgängliga på Google "
+"Code\n"
+"och Launchpad\n"
+"och inom I2P-nätverket på %(echelon)s."
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "Spegelval"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "Fil:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "Vilken spegel som helst"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+"För att göra anspråk på belöningen måste författaren inte vara betald av "
+"andra organisationer\n"
+"eller team för dethär arbetet (t.ex. GSoC students are not valid)."
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations.  Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"Belöningssummor kan ökas genom vidare donationer. Tycker\n"
+"du att dom är viktiga? Lägg till din donation,"
+"\n"
+"markera summan för %(donatename)s belöning!"
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "Hittades inte"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+"Yep.. resursen du letade efter, heter något annat, finns inte eller har "
+"tagits bort."
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "Serverfel"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "500 Serverfel"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "Ehmm.. servern träffade på någon sorts problem."
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "Speglar"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "Säkert"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "Blandat"
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Länkar"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "Impressum"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "T-Shirtar!"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "Europa"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "USA"
+
+#: i2p2www/pages/global/footer.html:31 i2p2www/pages/global/nav.html:133
+msgid "Donate"
+msgstr "Donera"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr "Hoppa över navigation"
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "I2P Logo"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "The Invisible Internet Project"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+"Denhär sidan uppdaterades senast %(lastupdated)s och är korrekt för "
+"routerversionen %(accuratefor)s."
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "Denhär sidan uppdaterades senast %(lastupdated)s."
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "Denhär sidan är korrekt för routerversion %(accuratefor)s."
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr "Föregående"
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr "Nästa"
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr "Skriven i"
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "Om"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Introduktion till I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "Jämförelser"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "Överblick av jämförelser"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Andra anonyma nätverk"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Dokumentation"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Dokumentationsindex"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Hur fungerar det?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "Försiktig intro"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "Tech intro"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "Hotmodell"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Garlic routing"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "Nätverksdatabas"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "Tunnelrouter"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "Peerval"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Kryptografi"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionsTaggar"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Specifikationer"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "Blockfil"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "Vanliga strukturer"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "Konfigurationsfiler"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:56
+msgid "Datagrams"
+msgstr "Datagram"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr "GeoIP filer"
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:88
+msgid "Plugins"
+msgstr "Plugin:er"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:55
+msgid "Streaming library"
+msgstr "Strömmande bibliotek"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "Tunnelskapelse"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "Tunnelmeddelanden"
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "Mjukvaru-uppdatering"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:60 i2p2www/pages/global/nav.html:113
+msgid "Applications"
+msgstr "Applikationer"
+
+#: i2p2www/pages/global/nav.html:62
+msgid "Supported applications"
+msgstr "Stödda applikationer"
+
+#: i2p2www/pages/global/nav.html:63
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Protocols"
+msgstr "Protokoll"
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Protocol stack"
+msgstr "Protokollstack"
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Transports"
+msgstr "Transporter"
+
+#: i2p2www/pages/global/nav.html:75
+msgid "Transport layer overview"
+msgstr "Transport-nivå överblick"
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Tunnels"
+msgstr "Tunnlar"
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Tunnel implementation"
+msgstr "Tunnelimplementation"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Unidirectional tunnels"
+msgstr "Enkelriktade tunnlar"
+
+#: i2p2www/pages/global/nav.html:84
+msgid "Old implementation"
+msgstr "Gammal implemenation"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Naming and addressbook"
+msgstr "Namn och adressbok"
+
+#: i2p2www/pages/global/nav.html:91
+msgid "Team"
+msgstr "Utvecklargrupp"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Hall of Fame"
+msgstr "Hall of Fame"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Academic papers and peer review"
+msgstr "Akademiska artiklar och sakutlåtande"
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Presentations, tutorials and articles"
+msgstr "Presentationer, guider och artiklar"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Contact us"
+msgstr "Kontakta oss"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Help"
+msgstr "Hjälp"
+
+#: i2p2www/pages/global/nav.html:101
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "How to browse I2P"
+msgstr "Hur du surfar på I2P"
+
+#: i2p2www/pages/global/nav.html:103
+msgid "Glossary"
+msgstr "Ordlista"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Performance"
+msgstr "Prestanda"
+
+#: i2p2www/pages/global/nav.html:105 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Forum"
+
+#: i2p2www/pages/global/nav.html:108
+msgid "Volunteer"
+msgstr "Volontera"
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Get involved!"
+msgstr "Medverka!"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Develop"
+msgstr "Utveckla"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Licenses"
+msgstr "Licenser"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Release signing keys"
+msgstr "Release signeringsnycklar"
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Signed keys"
+msgstr "Signerade nycklar"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Developers keys"
+msgstr "Utvecklares nycklar"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Bug tracker"
+msgstr "Bugg-tracker"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Academic research"
+msgstr "Akademisk forskning"
+
+#: i2p2www/pages/global/nav.html:122
+msgid "Open research questions"
+msgstr "Öppen forsknings-frågor"
+
+#: i2p2www/pages/global/nav.html:123
+msgid "Guides"
+msgstr "Guider"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "New developers"
+msgstr "Nya utvecklare"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Using an IDE with I2P"
+msgstr "Använda en IDE med I2P"
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Developer guidelines and coding style"
+msgstr "Utvecklar-riktlinjer och kodstil"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "New translators"
+msgstr "Nya översättare"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Bounties"
+msgstr "Belöningar"
+
+#: i2p2www/pages/global/nav.html:134 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Möten"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Roadmap"
+msgstr "Utvecklingsplan"
+
+#: i2p2www/pages/global/nav.html:136
+msgid "Task list"
+msgstr "Uppdragslista"
+
+#: i2p2www/pages/global/nav.html:139
+msgid "Language"
+msgstr "Språk"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr "I2P Mötes ATOM flöde"
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "Loggar av tidigare I2P möten"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr "Möten är pausade för tillfället till en mer lämplig tidpunkt kan väljas."
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"Om du har något att diskutera, hitta utvecklarna på IRC i rummt #i2p-dev."
+"\n"
+"Status-uppdateringar från utvecklar är "
+"också tillgängliga."
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr "I2P Utvecklarmöten %(id)s"
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr "Full IRC Logg"
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "Efter ämne"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "Efter datum"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "Efter författare"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
            \n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
            \n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+"Var god att skicka en nya eller korrigerat innehåll till %(email)s.
            \n"
+"Om du kan, var god formatera dom som BibTex, se vår BibTeX källkod till exempel.
            \n"
+"Kom ihåg att inkludera URL:er om möjligt:\n"
+"offline-artiklar är mindre användbara."
+
+#: i2p2www/pages/papers/list.html:94
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"Free Haven's anonymity bibliography."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Kontakt"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr "E-post"
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like OFTC,\n"
+"  EIN and Freenode.\n"
+"  All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+"Vårt primära IRC-nätverk är Irc2P nätverket inom I2P, en standardtunnel "
+"för dethär nätverket är konfigurerat på nya I2P installationer.\n"
+"Vi är och närvarande på flera vanliga IRC-nätverk som OFTC,⏎\n"
+"EIN och Freenode.\n"
+"Alla I2P-relaterade kanaler på dessa nätverk är länkade till huvudkanalen"
+" på Irc2P via relay bottar."
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Kanal-lista"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "Generell I2P-diskussion."
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "Utanför samtalsämnde"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "Utvecklingsprat"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Hjälpkanal"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"De flesta av discussionerna om I2P's utveckling händer på I2Ps utvecklarforum. Detta är ofta det bästa "
+"stället att fråga om #i2p-dev kanalen är inaktiv."
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "E-post-lista"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+"I2P har en mailinglista, men den används sällan eftersom det nuvarande "
+"utvecklarteamet föredrar att kommunicera via IRC eller utvecklar-forumet."
+" Detta kan förändras i framtiden."
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "Prenumerara"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+"För att prenumerera på mailinglista, go till informationssidan för "
+"mailinlinstan (länkad till nedan) och fyll i formuläret. I2P-interna "
+"e-post addresser (foobar@mail.i2p) kan användas."
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "Avprenumerera"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+"För att avprenumerera från mailinglistan eller ändra dina "
+"prenumerationsinställningar, gå till informationssidan för mailinglista "
+"(länkad till nedan) och fyll i dinprenumerations-adress."
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Listor"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Arkiv"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+"Generell I2P discussion - allt som inte hör hemma in andra mailinglistor "
+"hör hemma här."
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+"Gillar du inte mailinglistor? Då är dethär för dig. Alla mailinglistor "
+"finns tillgängliga via NNTP med."
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr "Grupp mailinglists-mappning:"
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Servrar:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Vanliga frågor"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Index"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "Allmänt"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "Vilka system kan I2P köras på?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+"Vad är en \"eepsite\" och hur kan jag konfigurera min webbläsare så att "
+"jag kan använda dom?"
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "Min router har väldigt få aktiva peers, är det OK?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr "Vad betyder Aktiva x/y nummerna i routerkonsolen?"
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+"Mina aktiva peers / kända peers / deltagande tunnlar / anslutningar / "
+"bandbredd varierar dramatisk över tid! Är något fel?"
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "Är det säkert att använda en utproxy?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr "De flesta \"eepsites\" inom I2P är nere?"
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Vilka portar använder I2P?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "Varför lyssnar I2P efter anslutningar på port 32000?"
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "Jag tror jag hittade en bugg, var kan jag rapportera den?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr "Vad hände med *.i2p.net? Vad hände med jrandom? Är I2P dött?"
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "Jag har en fråga!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr "Inställningar"
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+"Min router har var igång i flera minuter och har noll eller väldigt få "
+"anslutningar"
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "Varför är I2P så långsamt?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+"Jag saknar en massa av hosts i min adressbok. Vilka prenumerationslänkar "
+"är bra?"
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "Hur sätter jag igång min egen \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "Bittorrent / I2PSnark / Azureus I2P Plugin Frågor?"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "Hur ansluter jag till IRC inom I2P?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "Jag kan inte nå vanliga internetsidor genom I2P."
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "Jag kan inte nå https:// eller ftp:// -sidor genom I2P."
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr "Är det möjligt att använda I2P som en SOCKS5-proxy?"
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Hur ställer jag in min webbläsare?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+"Hur kan jag nå webkonsolen från mina andra maskiner eller lösenordsskydda"
+" den?"
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr "Hur kan jag använda applikationer från mina andra maskiner?"
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr "Hur reseed:ar jag manuellt?"
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "Min router använder för mycket CPU?!?"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "Missförstånd"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr "Hur kan jag nå IRC, BitTorrent, eller andra tjänster på internet?"
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+"Är min router en \"exit nod\" (utproxy) till det vanliga internet? Jag "
+"vill inte att den ska vara det."
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+"Jag är emot vissa sorters innehåll. Hur kan jag undvika att distribuera, "
+"lagra eller nå dom?"
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Fel och Deras Lösningar"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+"Jag använder FreeBSD och när jag startar I2P får jag ett fel om "
+"libm.so.4!"
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+"I wrapper.log ser jag ett fel som säger Protocol "
+"family unavailable när I2P laddas"
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "länk"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+"Sedan I2P rapporterats köras på Pentium II med 64 MB RAM, kommer din "
+"upplevelse bli bättre\n"
+"med en Pentium III (eller bättre) med 128 MB RAM (eller mer) Ett diagram jämförande\n"
+"prestandan av de olika JRE kan hittas på %(chart)s, kortfattat: det är möjligt, använd\n"
+"Sun/Oracle Java eller OpenJDK."
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+"I2P har testats på Windows, Linux, FreeBSD (se notisen nedan), OSX och OpenSolaris. För tillfället pågår "
+"arbete för att ge stöd för Android-platformen."
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr "Här finns några platser, välj en eller flera."
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "Diskuter med utvecklarna på IRC i #i2p-dev"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+"Var god inkludera relevant information från router-loggarna och wrapper-"
+"loggarna."
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+"Standard-prenumerationen är för http://www.i2p2.i2p/hosts.txt vilken "
+"sällan uppdateras.\n"
+"Om du inte har någon annan prenumeration, kan du behöva använda "
+"\"hopp\"-länkar vilket\n"
+"är irriterande-"
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+"Här är några andra publika adressboks-prenumerations länkar. Du kanske "
+"vill lägga till en eller två till din susidns "
+"prenumerationslista.\n"
+"Du behöver inte lägga till alla, eftersom dom synkroniserar med varandra "
+"periodiskt.\n"
+"Länkarna som använder en cgi-bin applikation använder en del strategier "
+"för att minimera\n"
+"antalet duplicerade adresser som delas ut och borde vara mer effektiv.\n"
+"Uppmärksamma att prenumerera till en hosts.txt tjänst är en handling av "
+"\"tillit\", eftersom illvilliga\n"
+"prenumerationer kan ge dig felaktiga adresser. Så tänk efter om du\n"
+"vill lite på några av dessa.\n"
+"Operatörerna av dessa tjänster kan ha vissa policy:er för att lista "
+"värdar.\n"
+"Närvaro på denna lista implicerar inte vårat stöd."
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+"Jrandom var huvudetvecklaren för I2P och\n"
+"Syndie i flera år.\n"
+"Vi vet inte om eller när jrandom kommer komma tillbaka.\n"
+"*.i2p.net domänen lämnades i ett icke-fungerande tillstånd efter ett "
+"strömavbrott\n"
+"hos hosting-företaget."
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+"Se denhär sidan för jrandoms avskedmeddelande"
+" och ytterliggare information\n"
+"om migrationen av *.i2p.net till den är sajten."
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr "I2P förblir i aktiv utveckling."
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+"Det finns många möjliga anledningar till hög CPU-använding. Här finns en "
+"kontrollista:"
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+"Försök att använda antingen OpenJDK eller Sun/Oracle Java om det finns "
+"tällgängligt för ditt system. Du kan kontrollera\n"
+"vilken version av java du har installerad genom att skriva java "
+"-version i en\n"
+"kommandotolk. Prestanda tenderar att vara värre med andra "
+"implementationer av java."
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+"Kör du en BitTorrent-klient över I2P? Försök att minska antalet torrents,"
+" bandbredds-gränserna\n"
+"eller försök stända av den helt och se om det hjälper."
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+"Är dina bandbredds-gränser för höga? Det är möjligt att för mycket "
+"traffik går igenom din\n"
+"I2P-router och att den är överbelastad. Försök minska inställningarna för"
+" utdelad bandbredds-procent på konfigurations-sidan."
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+"Var säker på att du kör den senaste versionen av I2P för att få tillgång "
+"till förbättrad prestanda och bugg-fixar."
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+"Har tillräkligt med minne reserverats för användning av I2P? Kika på "
+"minnes-grafen på graf-sidan "
+"för att se\n"
+"om minnes-användningen är \"maxad\"—JVM:en spenderar merparten av "
+"sin tid med garbage collection. Öka inställningen "
+"wrapper.java.maxmemory i wrapper.config."
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+"Är CPU-användningen helt enkelt högre än du vill att den ska vara eller "
+"är den fast vid 100% under längre tid?\n"
+"Om den är fast vid 100%, så kan det vara en bug. Titta i loggarna "
+"efter ledtrådar."
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+"Du kanske använder det Java-baserade BigInteger-biblioteket istället för "
+"platforms-specifika versionen,\n"
+"i synnerhet om du kör på ny eller ovanlig hårdvara eller OS (OpenSolaris,"
+" mipsel, etc.).\n"
+"See jbigi-sidan för instruktion om\n"
+"diagnosticering, byggande och test-metoder."
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+"Om ditt platforms-specifika jbigi-bibliotek fungerar, kan den största "
+"användaren av\n"
+"CPU vara routing av trafik fär deltagande tunnlar. Det använder CPU\n"
+"för att för varje hopp avkrypteras ett lager av kryptering.\n"
+"Du kan begränsa din deltagande traffik på två vis - genom att minska den\n"
+"utdelade bandbredden på\n"
+" confignet.jsp,⏎\n"
+"eller genom att sätta router.maxParticipatingTunnels=### på\n"
+" configadvanced.jsp."
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+"Hmm. I2P är ett anonymt nätverk, så det är en svår fråga.\n"
+"I2P är designat för att stå emor censur och att tillhandahålla ett sätt "
+"för alla att kommunicera fritt.\n"
+"Det bästa sättethålla din PC fri från (krypterad) traffik som du ogillar "
+"är att inte använda I2P.\n"
+"Yttrandefrihet har en kostnad.\n"
+"Men vi kan besvara din fråga i tre delar:"
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+"Distribution - All trafik i I2P är krypterad i flera lager. Du kan"
+" inte veta ett meddelandes innehåll, källa eller destination.\n"
+"All trafik du routar är intern för I2P-nätverket, du är inte en utgångsnod (utproxy).\n"
+"Ditt enda alternativ är att vägra att routa all trafik, genom att "
+"ställa in din utdelade bandbredd eller maximalt deltagande tunnlar till 0"
+" (se ovan).\n"
+"Det vore bra om du inte gör detta, du borde hjälpa nätverket genom att "
+"routa trafik åt andra.\n"
+"Över 95% av användare routar trafik åt andra."
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+"Lagring - I2P gör ingen distribuerad lagring av innehåll. Du måste"
+" tänka på\n"
+"Freenet.\n"
+"Ingens innehåll lagras på din dator genom att köra I2P."
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+"Tillgång - om Det finns eepsites som du inte gillar, besök inte "
+"dom.\n"
+"Eller använd en blockerand proxy som Privoxy eller någon sorts \"net "
+"nanny\"."
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+"Nej. Det är normalt.\n"
+"Alla routrar justerar sig dynamiskt efter förändrande nätverksförhållande"
+" och behov."
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+"Du kan behöva reseeda din I2P-router. Med nyare versioner av I2P kan gå "
+"till http://localhost:7657/configreseed"
+" och klicka Spara inställningar och Reseeda Nu-knappen. Om "
+"denhär metoden inte fungerar—eller du använder en väldigt gammal "
+"verion—kan du behöva att reseeda "
+"manuellt."
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+"Reseed URL:en ändrades för några år sedan. Om dethär är din första "
+"installation och du har installerat\n"
+"en gammal (0.6.1.30 eller tidigare) version eller\n"
+"om du inte har kört I2P på länge, behöver du ändra URL:en och sen\n"
+"klicka på \"Reseeda\"-knappen i routerkonsolen för att hitta andra "
+"routrar.\n"
+"När din router kör,\n"
+"på configadvanced.jsp,"
+"\n"
+"lägg till raden i2p.reseedURL=http://netdb.i2p2.de/\n"
+"ELLER i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (båda borde "
+"fungera),\n"
+"klicka sedan \"Apply\", och klicka sedan på \"reseed\"-länken på vänster "
+"sida."
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+"Detta fungerar om du kör 0.6.1.27 eller senare.\n"
+"Om du kör release 0.6.1.31 eller senare, så behöver du trolgitvis inte "
+"göra det.\n"
+"Om du kör release 0.6.1.26 eller tidigare, antingen följ de\n"
+"manuella reseed instruktionerna nedan "
+"eller installera den senaste releasen."
+"\n"
+"En möjlig alternativ metod - lägg till\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"till wrapper.config, stäng av routern helt, starta den sen igen och "
+"klicka slutligen på \"reseed\".\n"
+"Berätta för oss om det fungerar."
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+"...men du *borde* uppgradera till den "
+"senaste versionen."
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+"Om din router har 10 eller fler aktiva peers, så är allting ok. "
+"Förändringar i releaserna 0.6.1.31 och 0.6.1.32 förbättrade\n"
+"effektiviteten hos routern och minskade antalet aktiva peers.\n"
+"Routern borde alltid bibehålla anslutningarna till ett litet antal"
+" peers.\n"
+"Det bästa sättat att vara \"bättre ansluten\" till nätverket är att\n"
+"dela mer bandbredd."
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+"Är min router en \"exit nod\" till det vanliga internet? Jag vill inte "
+"att den ska vara det."
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+"Nej. Till skillnad från Tor, "
+"\"utgångsnoder\" eller \"utproxies\" är inte heller en del av nätverket."
+"\n"
+"Bara frivilliga som ställt in och kör separata applikationer kommer "
+"vidarebefodra trafik till det vanliga internet.\n"
+"Det finns väldigt, väldigt få av dessa."
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+"Se ovan. Det finns väldigt få HTTP \"utproxies\", de är inte integral del"
+" av nätverket och det kan hända att de är nere.\n"
+"Vidare, så har de gamla utproxierna squid.i2p, true.i2p och krabs.i2p "
+"försvunnit.\n"
+"Den enda utproxien för tillfället är false.i2p.\n"
+"För att använda den, ändra dina i2ptunnel "
+"inställningar för eepProxy\n"
+"och sätt din utproxy lista till \"false.i2p\" (enbart).\n"
+"Stanna och starta sedan om eepProxy:n.\n"
+"Om det inte fungerar, så är utproxyn inte uppe. Det är inte I2Ps fel.\n"
+"Om din huvudanledning göt att använda ett anonymt nätverk är att anonymt "
+"nå sajter på det vanliga internet, så borde du nog testa Tor."
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+"Inom I2P finns det inget behov för HTTPS, eftersom all trafik är "
+"krypterad från början till slut. Ftp stöds inte av tekniska skäl."
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+"Det finns inga FTP \"ut-proxies\" till internet—det kanske inte ens"
+" är möjligt konfigurera en.\n"
+"Någon annan sorts ut-proxy kan fungera om det konfigureras med en "
+"standard-tunnel.\n"
+"Om du vill sätta upp någon sorts utproxy, leta noggrant efter potentiella"
+" risker.\n"
+"I2P-communityn kan eventuellt hjälpa till med de tekniska aspekterna, du "
+"är välkommen att fråga."
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+"Som förklarat flera gånger tidigare ovan, inga existernade utproxies är "
+"en integral del av nätverket.\n"
+"Tjänsterna körs av individer och kanske inte fungerar alltid."
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
            \n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+"Uppdatering: Tack vare arbetet av h2ik, så finns det en https "
+"utproxy tillgänglig för som kan användas via I2P. Från och med I2P 0.8.4 "
+"är tunneln "
+"konfigurerad vid installation.
            \n"
+"I fallet av att https utproxyn inte är inställd i din version av I2P, så "
+"kan du lägga till den lätt genom att göra följande:"
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+"Öppna I2Ps tunnel "
+"hanterare. Skrolla ner till botten."
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+"Välj ANSLUT från Ny Klient-Tunnel listan, klicka på "
+"Skapa"
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+"På den nya sidan, namnge och beskriv din nya https tunnel "
+"precis som du vill.\n"
+"Access-punkten är din lokala port för den nya https proxyn, port "
+"4445 rekommenderas.\n"
+"Utproxy borde vara utproxyns .i2p adress som stödjer https.\n"
+"Se forum-posten av h2ik för "
+"adressen.\n"
+"Var säker på att Delad Klient, Försenad Anslutning och "
+"Autostart ikryssade.\n"
+"Andra alternativ bör lämnas med sina standard-värden. Klicka på \"Save\"."
+" I tunnelhanteraren, klicka på Start-knappen bredvid din nya "
+"tunnel."
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+"I Firefox, klicka igenom "
+"Verktyg>Alternativ>Advancerade>Nätverk>Inställningar."
+"\n"
+"Avkryssa Använd denhär proxyn för alla protokoll, sätt SSL "
+"proxy: till localhost:4445."
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "Färdig."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+"\n"
+"Dethär är en fråga som bara du kan besvaras eftersom det korrekta svaret "
+"beror på ditt beteende, din hot-modell "
+"och hur mycket du litar på operatören av utproxyn."
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+"Precis som Tor, kan I2P inte magiskt kryptera internet.\n"
+"Du är sårbar mot avlyssning av operatörerna av utproxyn.\n"
+"Tor"
+" FAQ:en förklarar detta på ett bra vis."
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+"Utöver det, så kan du vara sårbar för sammarbete mellan utproxy "
+"operatörer\n"
+"och operatörerna av andra I2P-tjänster, om du använder samma tunnlar "
+"(\"delade klienter\"). Det finns en ytterliggare diskussion om detta på "
+"%(zzz)s."
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+"Om en utproxy inte har blivit intesälld för tjänsten du vill ansluta "
+"till, så kan det inte göras.\n"
+"Det finns bara tre typer av utproxies som kör nu: HTTP, HTTPS och e-post."
+"\n"
+"Notera att det inte finns en SOCKS utproxy.\n"
+"Om den typen av tjänst behövs, testa Tor."
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+"Om du tittar på alla eepsiter som någonsin skapats, ja, de flesta av dom "
+"är nere.\n"
+"Människor och eepsiter kommer och går.\n"
+"Ett bra sätt att komma igång med I2P är att kika på en lista av eepsiter "
+"som för tillfället är uppe.\n"
+"%(eepstatus)s håller koll på aktiva "
+"eepsiter."
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+"Klicka på länken tillWebbsidan\n"
+"längst upp på din routerkonsol för instruktioner."
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+"Varför är nedladdningar, torrentar, webbsurfande och allt annat så "
+"långsamt i I2P?\n"
+"Krypteringen och routing inom I2P-nätverket lägger till stora mängder "
+"overhead och begränsar bandbredd.\n"
+"Anonymitet är inte gratis."
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+"Utöver det, behöver troligtvis du och alla andra öka dina bandbredds-"
+"inställningar.\n"
+"De två huvudinställningarna är de inåtgående och utåtgående "
+"bandbreddsgränserna på konfigurations-sidan.\n"
+"Med standardinställningen 32KB/s så kommer du nog inte få mer än 15KB/s "
+"överföringshastighet i I2PSnark.\n"
+"Att öka inställningarn (men håll dom inom gränserna för vad din "
+"internetanslutning klarar) kommer öka den potentiella "
+"överföringshastigheten för I2PSnark och alla andra applikationer."
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+"Har du tillräkligt med utdelad bandbredd inställd för att kunna delta i "
+"tunnlar? Tro det eller ej,  genom att delta i andras tunnlar så kommer "
+"din router bli väl integrerad i nätverket, vilket hjälper dina egna "
+"överföringshastigheter."
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+"I2P förbättras hela tiden. Massor av förbättringar och fixar "
+"implementeras och generellt sett, så förbättras din prestanda av att köra"
+" den senaste versionen.\n"
+"Om du inte gjort det redan, installera den "
+"senaste releasen."
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+"Se I2P Bittorrent "
+"FAQ:en"
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+"\n"
+"En tunnel till huvud IRC servern inom I2P, Irc2P, skapas när I2P "
+"installeras\n"
+"(see I2PTunnel "
+"konfigurationssidan),\n"
+"och startas automatiskt när I2P-routern startar. För att ansluta till "
+"den, säg till din IRC-klient att ansluta till "
+"localhost:6668. XChat-lika klienter kan skapa ett nytt "
+"nätverk med servern localhost:6668 (kom ihåg att klicka i "
+""Kringå\n"
+"proxy-server" om du har en proxy-server inställd)."
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface.  However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+"Av säkerhetskäl så lyssnar routerns adminkonsol som default\n"
+"efter anslutningar på det lokala nätverksinterface:t. Dock så kan du med "
+"lite hackande,\n"
+"nå den bortifrån."
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"with 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+"Öppna ~/.i2p/clients.config och ersätt
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"med 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+"Gå till http://localhost:7657/configui"
+" och ställ in ett användarnamn och lösenord om det önskas."
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+"Gå till http://localhost:7657/index.jsp"
+"\n"
+"och klicka på \"Graviös omstart\", vilket startar om JVM:en och laddar om"
+" klient-applikationerna"
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+"Efter det startat, så borde du nu kunna nu kunna nå din konsol från andra"
+" maskiner. Ladda om routerkonsolen på http://127.0.0.1:7657 så kommer du "
+"frågas efter det användarnamn och lösenord du angivet i steg 2\n"
+"ovan om din webbläsare stödjer autentiserings popup:en. Obs: "
+"0.0.0.0 ovan anger ett interface, och inte ett "
+"nätverk eller en nätmask.\n"
+"0.0.0.0 betyder \"bind till alla interface\", så att den kan nås från "
+"127.0.0.1:7657 och alla andra LAN/WAN IP-adresser."
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+"Som standard så binder I2CP interface:t (port 7654) till adressen "
+"127.0.0.1. För att binda den till 0.0.0.0, sätt\n"
+"det advancerade konfigurationsalternativet  "
+"i2cp.tcp.bindAllInterfaces=true och starta om."
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "Var är en \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+"En eepsite är en webbsida som hostas anonymt - du kan nå den genom\n"
+"att ställa in din webbläsare HTTP proxy till att använda webbproxyn "
+"(normalt sett lyssnar den på localhost port 4444) och att surfa till "
+"sajten."
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+"Proxyinställningen för olila webbläsare finns på en separat sida med skärmdumpar. Flera "
+"advancerade inställningar med externa verktyg\n"
+"är gångbara men kan introducera läckor i din installation."
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+"x är antalet peers du har skickat eller mottaget ett meddelande från den "
+"senaste minuten, y är antalet peers som sett på den senaste\n"
+"timmer eller så."
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+"SOCKS-proxyn fungerar från och med 0.7.1 SOCKS 4/4a/5 stöds.\n"
+"Det finns ingen SOCKS-utproxy så det begränsad nytta."
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+"Utöver det, så kan många applikationer läcka känslig\n"
+"information som skulle kunna identifiera dig på internet. I2P filtrerar\n"
+"anslutningsdata, men om programmet du vill köra skickar denhär "
+"informationen som innehåll så kan I2P inte skydda din anonymitet. Till\n"
+"exempel, så skickar vissa e-post program ip-adressen av maskinen\n"
+"de kör som e-post-server. Det finns iget vis I2P kan filtrera\n"
+"detta , därför är det extremt farligt att använda I2P för att "
+"'socksifiera' existeranda applikationer."
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+"Om du vill ha mer information om SOCKS-proxy applikationen iallafall,\n"
+"så finns det fler hjälpsamma tips på SOCKS-sidan."
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+"Okay, här är en kort lista av standardportarna (allt är konfigurerbart\n"
+"genom olika inställningar, så klart):"
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+"Internet nåbara portar\n"
+"Notis: Nya installationer sedan release 0.7.8 avänder inte port 8887, de "
+"väljer en slumpässig port mellan 9000 och 31000 när programmet körs "
+"första gången.\n"
+"Den valda porten visas på routerns konfigurationssida."
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+"    "
+msgstr ""
+"Utåtgående UDP från den slumpmässiga porten visas på  konfigurationssidan till"
+" olika fjärran UDP portar, som gör svar möjligt"
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+"    "
+msgstr ""
+"Utåtgående TCP från slumpmässiga höga portar till olika fjärran TCP "
+"portar"
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+"    "
+msgstr ""
+"(valfri, men rekommenderar) Inåtgående UDP till porten som visas på konfigurationssidan "
+"från olika platser"
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
            \n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+"(valfri, men rekommenderar) Inåtgående UDP till porten som visas på konfigurationssidan "
+"från olika platser
            \n"
+"Inåtgående TCP kan slås av på konfigurationssidan."
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
            \n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+"Utåtgående UDP på port 123, som möjliggör svar
            \n"
+"Detta är nödvändigt för I2Ps interna tidssynkronisering (via SNTP - fråga"
+" en slumpmässig SNTP-värd i pool.ntp.org eller en annan\n"
+"server om du valt det)"
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+"Lokala I2P portar, lyssnar bara på lokala anslutningar som "
+"standard,\n"
+"förutom där det påpekas:"
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"1900: UPnP SSDP UDP multcast-lyssnar.\n"
+"Kan inte ändras. Binder till alla interface.\n"
+"Kan slås av på confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+"2827: BOB bryggan, ett högnivå socket API för klienter\n"
+"Avslagen som standard.\n"
+"Kan slås av/på på configclients.jsp.\n"
+"Kan eventuellt ändras i bob.config filen."
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4444: HTTP proxy\n"
+"Kan slås av eller ändras på i2ptunnel-sidan i routerkonsolen.\n"
+"Kan även konfigureras till att lyssna på ett specifikt interface ller "
+"alla interface."
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4445: HTTPS proxy\n"
+"Kan slås av eller ändras på i2ptunnel-sidan i routerkonsolen.\n"
+"Kan även konfigureras att lysna på ett specifikt interface eller alla "
+"interface."
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"6668: IRC proxy\n"
+"Kan slås av eller ändras på i2ptunnel-sidan i routerkonsolen.\n"
+"Kan även konfigureras till att lyssna på ett specifikt interface eller "
+"alla interfaces."
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7652: UPnP HTTP TCP händelse-lyssnare.\n"
+"Binder till LAN-adressen.\n"
+"Kan ändras med advancerad konfig i2np.upnp.HTTPPort=####.\n"
+"Kan slås av på confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7653: UPnP SSDP UDP sök-svars lyssnare.\n"
+"Binder till alla interface.\n"
+"Kan ändras med advancerad konfig i2np.upnp.SSDPPort=####.\n"
+"Kan slås av på confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+"7654: I2P Klient Protokoll port, används av klient-appar.\n"
+"Kan ändras till en annan port på configclients.jsp\n"
+"men det rekommenderas inte.\n"
+"Kan ändras till ett annat interface eller alla interface, eller slås av, "
+"på configclients.jsp."
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+"7655: UDP för SAM brydda, ett högnivå socket API för klienter\n"
+"Öppnas endast när en SAM V3-klient begär en UDP session.\n"
+"Kan slås på/av på configclients.jsp.\n"
+"Kan ändras i clients.config filen med SAM alternativet "
+"sam.udp.port=####§."
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+"7656: SAM brygga, ett högnivå socket API för klienter\n"
+"Avslaget som standard för nya installationer sedan release 0.6.5.\n"
+"Kan slås av/på på configclients.jsp.\n"
+"Kan ändras i clients.config filen."
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+"7657: Din routerkonsol\n"
+"Kan slås av i clients.config filen.\n"
+"Kan även konfigureras till att binda till ett specifikt interface eller "
+"alla interface i den filen."
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+"7658: Din eepsite\n"
+"Kan slås av i clients.config filen.\n"
+"Kan även konfigureras till att binda till ett specifikt interface eller "
+"alla interface i jetty.xml filen."
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7659:Utåtgående mail till smtp.postman.i2p\n"
+"Kan slås av eller ändras på i2ptunnel-sidan i routerkonsolen.\n"
+"Kan även konfigureras till att binda till ett specifikt interface eller "
+"alla interface."
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7660: Inkommande e-post från pop.postman.i2p\n"
+"Kan slås av eller ändras på i2ptunnel-sidan i routerkonsolen.\n"
+"Kan även ändras till att binda till ett specifikt interface eller alla "
+"interface."
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"8998: mtn.i2p2.i2p (Monotone - avslaget som standard)\n"
+" Kan slås av eller ändras på i2ptunnel-sidan i routerkonsolen.\n"
+"Kan även konfigureras till att binda till ett specifikt interface eller "
+"alla interface."
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"31000: Lokal anslutning till wrapper kontroll kanal porten.\n"
+"Utåtgående till 32000 enbart, lyssnar inte på denna port.\n"
+"Börjar på 31000 och ökar till 31999 letanders efter en ledig port.\n"
+"För att ändra se\n"
+"wrapper dokumentationen.\n"
+"Fär mer information se nedan."
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"32000: Lokal kontroll kanal för tjänstwrappern.\n"
+"För att ändra se wrapper dokumentationen.\n"
+"För mer information se nedan."
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally.  You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+"De lokala I2P-portarna och I2PTunnel-portarna behöver inte vara nåbara "
+"för fjärran maskiner, men *borde* vara nåbara lokalt. Du kan skapa flera "
+"portar för I2PTunnel instanser via http://localhost:7657/i2ptunnel/"
+" (och efter det behöver du få din brandvägg att ge dig lokal åtkomst, men"
+" inte fjärran åtkomst, om det inte önskas)."
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance.  You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+"Så, för att summera, ingenting behöver vara nåbart av ovälkomna fjärran "
+"peers, men\n"
+"om du kan konfigurera din NAT/brandvägg till tillåta inåtgående UDP och "
+"TCP på den utåt öppna "
+"porten, så kommer du få bättre prestanda. Du kommer också behöva "
+"kunna skicka utåtgående UDP-paket till olika fjärrna peers (att blockera "
+"IP-adresser slumpmässigt med något som PeerGuardina skadar bara dig - gör"
+" det inte)."
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr "Varför lyssnar I2P efter anslutningar på port 32000?"
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+"Taniki java service wrappern vi använder öppnar denhär "
+"porten—bunden till localhost—för att kunna kommunicera med "
+"mjukvaran som kör i JVM:en. När JVM:en startas ges den en nyckel\n"
+"så att den kan ansluta till wrappen. Efter JVM:en etablerat sin "
+"anslutning \n"
+"till wrappern, så avvisar wrappern alla efterkommande anslutningar."
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the  \n"
+"wrapper documentation."
+msgstr ""
+"Mer information kan finnas i wrapper dokumentationen."
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+"En I2P router behöver bara seedas en gång, för att kunna gå med i "
+"nätverket första gången.\n"
+"Reseedande är inget mer än att skicka enkla HTTP GET förfrågor\n"
+"för att hämta en lista över en mapp och ladda ner flera \"routerInfo\" "
+"filer\n"
+"från en fördefinierad reseed URL."
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+"Ett typisk symptom för en misslyckad reseed är att \"Kända\" indikatorn\n"
+"(på vänster sida av routerkonsolen) visar ett väldigt lågt värde\n"
+"(ofta färre än 5) och inte ökar. Detta kan hända, bland annat om din "
+"brandvägg begränsar utgående trafik och blockerade reseed förfrågan."
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr "För att reseed en I2P router manuellt, gör följande:"
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr "Stanna din I2P router"
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+"Öppna http://netdb.i2p2.de/ med en "
+"webbläsare"
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr "Spara ett dussin \"routerInfo\" filer till din I2P \"netDb\" mapp"
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr "Starta din I2P router"
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+"När du försöker starta routern med \"i2prouter start\", kan du komma att "
+"se output som den följande:"
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+"\n"
+"För att vara inklusiv och att försöka försäkra att I2P kommer köra på så "
+"många system\n"
+"som möjligt, använde vi till release 0.8.9 en java wrapper\n"
+"kompilerad fär FreeBSD 6.x. Om du får dethär felet så saknar du nog de "
+"kompabilitetsbiblioteken som behövs.\n"
+"Dessa bibliotek kan installeras på följande vis:"
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+"Byt till root användaren med su eller logga in som "
+"root."
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+"Om du inte kan installera dessa kompabilitetsbibliotek (eller inte vill),"
+" så är en annan möjlighet att kompilera wrappern för ditt system, starta I2P med "
+"runplain.sh skriptet, eller att byta ut wrappern med en från"
+" källkods tarball:en."
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+"För 0.8.9 releasen av I2P, uppdaterades wrappern till v3.5.12 och "
+"kompilerades på system som körde FreeBSD 7.2."
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+"I wrapper.log ser jag fel som säger \"Protocol family "
+"unavailable\" när routerkonsolen laddas"
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+"Ofta inträffar dethär felet när ett nätverksanvändande java-program är "
+"konfigurerat att använda IPv6 som standard på vissa system. Det finns "
+"några sätt att lösa detta:"
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+"På Linux-baserade system kan du köra echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr "Leta efter följande rader i wrapper.config."
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+"Om raderna finns där, okommentera dom genom att ta bort \"#\". Om raderna"
+" inte finns där, lägg till dom utan \"#\"."
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+"Ett annat alternativ är att ta bort ::1 från "
+"~/.i2p/clients.config"
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+"VARNING: För alla ändringar i  "
+"wrapper.config krävs en omstart av routern för att de ska "
+"träda i kraft. Att klicka på Starta Om i din \n"
+"routerkonsol kommet *inte* läsa om denhär filen! Du måste klicka på "
+"Stäng ner, vänta i 11 minuter och sedan starta I2P."
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+"Toppen! Hitta oss på IRC irc.freenode.net #i2p eller post:a på forumet så kommer vi skriva det här (med "
+"svaret, förhoppningsvis)."
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "Tyska lagar"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr "I2P Anonymt Nätverk"
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+"Anonymt  peer-to-peer distribuerat kommunikationslager byggt med open "
+"source-verktyg och designat för att köra alla traditionella internet-"
+"tjänster så som e-post, IRC och webb-hosting."
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr "Vad gör I2P för dig?"
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+"I2P-nätverket ger ett starkt intergritets-skydd för kommunikation över "
+"internet. Många aktiviteter som skulle riskera din intergritet på det "
+"publika internet kan göras anonymt inom I2P."
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr "Hämta I2P %(version)s"
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "Vad är I2P?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+"I2P är ett anonymt överdrags-nätverk - ett nätverk inuti ett nätverk. Det"
+" är avsett att skydda kommunikation från massövervakning av 3dje parter "
+"som internet leverantörer.\n"
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+"I2P används av personer i många olika situationer där integritet är "
+"viktigt: aktivister,  journalister, förtryckta människor och "
+"visselblåsare men även vanliga personer.\n"
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+"Inga nätverk kan vara \"totalt anonyma\". Det kontinuerliga målet för I2P"
+" är att göra attacker svårare och svårare att utföra. Dess anonymitet "
+"kommer bli starkare allt eftersom nätverkets storlek ökar och pågående "
+"akademisk undersökning.\n"
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+"I2P är tillgängligt för desktops, inbyggda system (som Raspberry Pi) och "
+"Android telefoner. Hjälp till att sprida order!\n"
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr "Läs mer…"
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr "Vad kan du göra med I2P?"
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+"Skicka e-post: Integrerat webb-"
+"interface för e-post, plugin för serverlös e-post."
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+"Surfa: Anonyma sajter, "
+"portaler till och från det publika internet."
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+"Blogga och forum: "
+"Bloggande och Syndie plugins."
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+"Hosta webbsidor: Integrerad"
+" anonym webbserver."
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+"Realtids chatta: Instant "
+"messaging och IRC klienter."
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+"Fildela: ED2K och Gnutella "
+"klienter, integrerad BitTorrent klient."
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+"Decentraliserad "
+"fillagring:Tahoe-LAFS plugin för distribuerat filsystem."
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr "Fler stödda applikationer…"
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr "Nyheter & Uppdateringar "
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr "Rekommenderade Länkar & Resurser"
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+"Se också sidan med\n"
+"länkar till presentationer, videor och guider om "
+"I2P."
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr "I2P på nätet"
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr "Vänner till I2P"
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr "Fler Projekt och Dokumentation"
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "Press"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr "Anslagstavlor, nyhetssida, annat"
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr "Väldigt Gamla Saker"
+
diff --git a/i2p2www/translations/sv_SE/LC_MESSAGES/research.po b/i2p2www/translations/sv_SE/LC_MESSAGES/research.po
new file mode 100644
index 00000000..2c5dd165
--- /dev/null
+++ b/i2p2www/translations/sv_SE/LC_MESSAGES/research.po
@@ -0,0 +1,156 @@
+# Swedish (Sweden) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# hottuna , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-10-04 03:48+0000\n"
+"Last-Translator: hottuna \n"
+"Language-Team: Swedish (Sweden) "
+"(http://www.transifex.com/projects/p/I2P/language/sv_SE/)\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/research/index.html:2
+msgid "Academic Research"
+msgstr "Akademisk Forskning"
+
+#: i2p2www/pages/site/research/index.html:4
+msgid ""
+"Academic research and analysis of I2P is an important part of ensuring "
+"that the software and network performs as expected and is safe for users "
+"in hostile environments."
+msgstr ""
+"Akademisk forskning och analys av I2P är en viktigt del av att försäkra "
+"att mjukvaran och nätverket presterar som förväntat och är säkert att "
+"använda i fientliga miljöer."
+
+#: i2p2www/pages/site/research/index.html:8
+#, python-format
+msgid ""
+"\n"
+"There is a large research community investigating a wide range of aspects"
+" of\n"
+"anonymity. For a current and comprehensive list of relevant papers, see "
+"the\n"
+"Free Haven Anonymity Bibliography.\n"
+"I2P benefits from much of the research into Tor and onion routing, but "
+"there is\n"
+"little dedicated research interest into the theory behind I2P, and the "
+"choices\n"
+"and tradeoffs that the network makes. This presents a unique opportunity "
+"for\n"
+"original research.\n"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:18
+#, python-format
+msgid ""
+"A list of known published papers about I2P is available here."
+msgstr ""
+"En lista av tidigare kända artiklar om I2P finns tillgänglig här."
+
+#: i2p2www/pages/site/research/index.html:22
+msgid "Testing Attacks on I2P"
+msgstr "Testa Attacker på I2P"
+
+#: i2p2www/pages/site/research/index.html:24
+msgid ""
+"I2P can be run as a separate test network by controlling the locations "
+"that a new router reseeds from so that it only finds other test routers."
+msgstr ""
+"I2P kan köras som ett separat testnätverk genom att kontrollera platserna"
+" som en ny router reseed:ar från så att den bara hittar andra "
+"testroutrar."
+
+#: i2p2www/pages/site/research/index.html:28
+msgid ""
+"The standard mode of operation is to have one JVM per router instance; "
+"hence running multiple copies of I2P on a single machine is inadvisable, "
+"both due to the potential resource drain and the certain port conflicts. "
+"To better facilitate setting up small test networks, I2P has a "
+"multirouter mode which enables multiple distinct routers to be run in the"
+" same JVM."
+msgstr ""
+"Standardsättet att köra är att ha en JVM per routerinstans - därför är "
+"det inte rekommenderat att köra flera kopior av I2P på en ända maskin, "
+"både på grund av potentiell resursåtgång och vissa port-konflikter. För "
+"att bättre hjälpa till med att sätta upp små testnätverk, så har I2P ett "
+"multirouter läge som låter flera olika routrar köras i samma JVM."
+
+#: i2p2www/pages/site/research/index.html:32
+msgid ""
+"MultiRouter can be started from the i2p base directory by running the "
+"below command."
+msgstr ""
+"MultiRouter kan startas från I2Ps bas-mapp genom att köra nedanstående "
+"kommando."
+
+#: i2p2www/pages/site/research/index.html:37
+msgid ""
+"Additionally, I2P can be started in a virtual network mode. This mode "
+"disables all transports, allowing the router to be tested in isolation "
+"without network traffic. To enable this mode, add "
+"i2p.vmCommSystem=true to the router.config before starting."
+msgstr ""
+"Utöver det, så kan I2P startas i ett virtuellt nätverksläge. Detta slår "
+"av alla transporter, vilket låter routern testas isolerad utan "
+"nätverkstrafik. För att slå på detta läget, lägg till "
+"i2p.vmCommSystem=true till router.config filen före du "
+"startar. "
+
+#: i2p2www/pages/site/research/index.html:41
+msgid "Testing the Live I2P Network"
+msgstr "Testande i existerande I2P-nätverket"
+
+#: i2p2www/pages/site/research/index.html:43
+#, python-format
+msgid ""
+"If you are planning on conducting research on the live I2P network, "
+"please contact us before you commence your "
+"testing. While we do not discourage researchers from responsibly testing "
+"their ideas on the live network, if an attack becomes apparent and we "
+"don't have any line of communication then we will end up taking "
+"countermeasures which could interfere with the test."
+msgstr ""
+"Om du planerar att göra forskning på det existerande I2P-nätverket, "
+"snälla kontakta oss före du börjar testa. "
+"Medan vi inte vill förhindra forskare från att ansvarsfullt testa sina "
+"idéer på det existerande nätverket, om den attack blir uppenbar och vi "
+"inte har en komunikationskanal så kommer göra motåtgärder som kan störa "
+"testerna."
+
+#: i2p2www/pages/site/research/questions.html:2
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:4
+msgid "Network database"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:6
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:8
+msgid "Tunnels and Destinations"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:10
+msgid "Unidirectional tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:16
+msgid "Multihoming"
+msgstr ""
+
diff --git a/i2p2www/translations/zh_CN/LC_MESSAGES/priority.po b/i2p2www/translations/zh_CN/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..a4c3fe64
--- /dev/null
+++ b/i2p2www/translations/zh_CN/LC_MESSAGES/priority.po
@@ -0,0 +1,2786 @@
+# 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
+# nametooshort , 2013
+# walking , 2013
+# wwj402 , 2013
+# xtoaster , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-12-25 22:02+0000\n"
+"PO-Revision-Date: 2013-12-21 00:55+0000\n"
+"Last-Translator: kwh <14alpaca@gmail.com>\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/blog/category.html:2
+msgid "Blog Category"
+msgstr "文章分类"
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr "I2P 博客 ATOM 源，文章分类：%(category)s"
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:92
+msgid "Blog"
+msgstr "博客"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "I2P 博客新闻源 (ATOM格式)"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr "发表时间：%(date)s 作者：%(author)s"
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "更多博客文章…"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr "发表时间："
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "文章作者："
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Debian I2P 软件包"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr "Ubuntu (Precise 12.04 或更新)"
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"选择 1:  Ubuntu 最近版本及其衍生版 "
+"(如果您使用的不是Debian，请尝试此项。)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr "选择 2：Debian (包括 Debian 衍生版)"
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr "Ubuntu Precise Pangolin (或更新) 及其衍生版 例如：Linux Mint & Trisquel 的操作说明"
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "通过命令行添加PPA源，安装I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "打开终端窗口并输入："
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"此命令将添加 PPA 至 /etc/apt/source.list.d 中，\n"
+"并获取软件源签名所使用的 GPG 密钥。GPG 密钥保证软件包自编译后没有被篡改。"
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "输入一下命令，通知您的软件包管理器新添加的PPA源："
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr "此命令将从系统中已启用的每个软件源中获取最新的软件列表，包括刚刚通过命令添加的 I2P PPA 源。"
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "您现在可以安装I2P了！"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "使用Synaptic添加PPA"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr "打开 Synaptic (系统 -> 管理 -> Synaptic 软件包管理器)。"
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr "Synaptic 启动后，从 设置 菜单中选择 软件源 。"
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"点击 其他来源 选项卡，单击 添加。\n"
+"粘贴 ppa:i2p-maintainers/i2p 至 APT-行并点击添加来源。\n"
+"点击关闭 按钮，然后 重新载入。"
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+"在快速筛选框中，输入 i2p，按回车键。\n"
+"结果列表中出现 i2p 后，右键点击 i2p 并选择 标记为安装。\n"
+"此后可能会出现 标记其他需要的变更? 弹出窗口，请选择 标记 然后 应用。"
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr "安装过程结束后，您可以继续到下一部分 启动I2P，根据您的系统对其进行配置。"
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the  key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr "安装过程结束后，您可以继续到下一部分 启动I2P，根据您的系统对其进行配置。"
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "安装收尾工作"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr "使用以上 I2P 软件包，I2P 路由可以通过如下方式启动"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+""按需启动" 使用 i2prouter 脚本。从命令行执行 "i2prouter\n"
+"start" 即可。(注意：不要使用 sudo 或以 root 身份运行!)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""按需运行"  执行 \"i2prouter-nowrapper\"，\n"
+"不使用 java "
+"服务封装直接运行(非Linux/非x86系统中需要这样)。\n"
+"(注意：不要使用 sudo 或以 root 身份运行!)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"作为服务在您的系统启动时自动运行，甚至早于用户登录。服务可以通过以root身份或sudo命令执行\"dpkg-reconfigure\n"
+"i2p\"启用。这是推荐的操作方式。"
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+"首次安装时，请不要忘记如果可能请调整您的 NAT/防火墙。\n"
+"需要转发的端口可以通过路由控制台的 网络配置页面查看。\n"
+"如果需要端口转发/端口映射方面的帮助，portforward.com可能会对您有用。"
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"请到配置页面，\n"
+"检查并调整带宽设置，因为默认设置的 96 KB/s 下行 / 40 KB/s 上行相当保守。"
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"如果您希望通过浏览器访问I2P暗网内的网站, 您需要参看 浏览器代理设置 "
+"页面了解基本设置方法。"
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "下载"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "下载 I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "依赖关系"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
            \n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "全新安装"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr "选择备用链接"
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "下载此文件并运行之。"
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"下载此文件并双击它(如果管用)或在终端中输入 java -jar "
+"i2pinstall_%(i2pversion)s.jar启动安装程序 installer。\n"
+"您也许可以从右键菜单中选择 "用 Java 打开"。"
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "命令行安装命令:"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"下载以上的 %(i2pversion)s OSX 图形安装文件并在命令行中执行java -jar "
+"i2pinstall_%(i2pversion)s.jar -console"
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    "Open with Java"."
+msgstr ""
+"下载此文件并双击它(如果管用)或在终端中输入 java -jar "
+"i2pinstall_%(i2pversion)s.jar启动安装程序 installer。\n"
+"在其他一些系统中，您也许可以从右键菜单中选择 "用 Java 打开"。"
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"下载以上的图形安装文件并在命令行中执行java -jar i2pinstall_%(i2pversion)s.jar "
+"-console。"
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Debian & Ubuntu 有官方软件包可用。"
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+"    The latest dev build is version %(devbuild)s, and is available from\n"
+"    str4d's eepsite."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+"      are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+"      the other."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "源码包"
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+"    or via Git from git.repo.i2p or Github.\n"
+"    
            \n"
+"    Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+"另外，您可以通过 monotone 或 "
+"git.repo.i2p 或 Github 获取源码。\n"
+"
            \n"
+"运行 (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ；cd "
+"i2p-%(i2pversion)s ；ant pkg) 然后按前述方式启动图形界面安装程序或进行命令行安装。"
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"文件由 zzz 签名，\n"
+"它的公钥可以从这里下载。"
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"I2P 也可以从我们在 Launchpad \n"
+"或 Google Code 上的项目站点下载。"
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"在Windows下安装程序运行完毕后，只要点击 \"启动 I2P\" 按钮\n"
+"即可打开 路由控制台，其中有更多的介绍内容。"
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"在 Unix 类系统下, I2P 可以通过执行  \"i2prouter\" 脚本作为服务启动，脚本位于您为 I2P 指定的目录中。\n"
+"在终端下进入此目录并执行 \"sh i2prouter status\" 应该可以获得路由器信息。\n"
+"命令参数 \"start\", \"stop\" 及 \"restart\" 可以控制服务状态。\n"
+"路由控制台可以通过与其他平台相同的地址访问。\n"
+"OpenSolaris及其他不支持Java封装程序(i2psvc)的系统用户，需要使用 \"sh runplain.sh\" 启动路由器。"
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"首次安装时请不要忘记如果可能 请调整您的 NAT/防火墙 设置，\n"
+"I2P 使用的外网端口及其它端口的说明在这里。\n"
+"如果您映射了 TCP 端口，请到 配置页面启用入站 TCP 传输。"
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"请到配置页面，检查并调整带宽设置，因为默认设置的"
+" 96 KB/s 下行 / 40 KB/s 上行非常缓慢。"
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "从早期版本中更新至新版："
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr "更新方式有自动更新和手动更新两种。"
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "自动更新"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+"如果您正在运行 0.7.5 或更高版本，您的路由器可以检测到新版本。\n"
+"要更新，只需在按钮出现时，点击路由控制台中的“下载更新”按钮。"
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"因为 0.7.6 版中的错误，第一次使用此版本并没有采取手动更新的路由器\n"
+"会出现“已下载的版本没有现有版本新”\n"
+"(\"downloaded version is not greater than current version\" )的错误。\n"
+"请使用下面的更新方法。"
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"如果您正在使用 0.7.4 或更早的版本，请参见0.7.5 版本说明  "
+"了解关于配置路由器，自动接收更新的重要信息。"
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"如果您正在运行 0.6.1.30 或更早版本请参见 操作说明 "
+"关于如何配置路由器自动接收更新的重要信息。"
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+"    router console "
+"allowing\n"
+"    you to download and install the new release by just clicking on that\n"
+"    link."
+msgstr ""
+"如果您已经根据 操作说明 重新配置了路由器，您应该从 路由控制台 "
+"看到链接，允许您通过点击此链接，下载并安装新的版本。"
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr "或者，您可以通过下面的方法手动更新。"
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "手动更新"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and rename as i2pupdate.zip.\n"
+"    (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+"    resulting i2pupdate.zip to your I2P installation directory).  You do"
+" \n"
+"    NOT need to unzip that file."
+msgstr ""
+"下载此文件到您的 I2P 安装目录并 重命名为 i2pupdate.zip (或者，您可以下载源代码并运行“ant "
+"updater”，然后将得到的 i2pupdate.zip 复制到您的 I2P 安装文件夹)。注意您不需要解压此文件。"
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr "单击 “重启”"
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "喝杯咖啡 11 分钟后回来"
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"此文件由 zzz 签名，\n"
+"公钥可以从这里找到。"
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "之前的版本"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"之前的版本可以通过 Google "
+"Code 和  Launchpad "
+"，或通过 I2P 内的网站%(echelon)s 下载。"
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "镜像选择"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "文件:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "任意镜像"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr "若要赢取赏金，作者(的项目)不能从其它机构获得薪酬或为其它团队工作(例如 GSoC 学生不符合条件)。"
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations.  Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"赏金金额会因后续的捐赠增加。您认为这重要吗? \n"
+"为 %(donatename)s 赏金添加捐赠! "
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "未找到"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr "嗯... 您正搜索的资源，或者使用了不同的名称，或者不存在，或者已经删除。"
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "服务器错误"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "500 服务器错误"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "嗯...服务器出现了某些错误。"
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "镜像"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "安全"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "其它"
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "链接"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "名人堂"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "文化衫"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "欧洲"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "美国"
+
+#: i2p2www/pages/global/footer.html:31 i2p2www/pages/global/nav.html:133
+msgid "Donate"
+msgstr "捐赠"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr "跳过导航"
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "I2P 标识"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "I2P 隐形网项目"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr "本页最后更新于 %(lastupdated)s 针对版本 %(accuratefor)s。"
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "本页最后更新于 %(lastupdated)s。"
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "本页针对版本 %(accuratefor)s。"
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr "前一个"
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr "下一个"
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr "发表于"
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "关于"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "介绍 I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "比较"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "比较概况"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "其它匿名网络"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "文档"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "文档索引"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "工作原理"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "说明性简介"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "技术性介绍"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "威胁模式"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Garlic 路由"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "网络数据库"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "隧道路由"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "节点选择"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "加密系统"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "规格"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "区块文件"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "共同架构"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "配置文件"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:56
+msgid "Datagrams"
+msgstr "数据报"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr "GeoIP 文件"
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:88
+msgid "Plugins"
+msgstr "插件"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:55
+msgid "Streaming library"
+msgstr "Streaming 库"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "隧道创建"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "隧道消息"
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "软件更新"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:60 i2p2www/pages/global/nav.html:113
+msgid "Applications"
+msgstr "应用"
+
+#: i2p2www/pages/global/nav.html:62
+msgid "Supported applications"
+msgstr "支持的应用"
+
+#: i2p2www/pages/global/nav.html:63
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Protocols"
+msgstr "协议"
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Protocol stack"
+msgstr "协议栈"
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Transports"
+msgstr "传输方式"
+
+#: i2p2www/pages/global/nav.html:75
+msgid "Transport layer overview"
+msgstr "传输层概要"
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Tunnels"
+msgstr "隧道"
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Tunnel implementation"
+msgstr "隧道实现"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Unidirectional tunnels"
+msgstr "双向隧道"
+
+#: i2p2www/pages/global/nav.html:84
+msgid "Old implementation"
+msgstr "旧实现"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Naming and addressbook"
+msgstr "节点命名与地址簿"
+
+#: i2p2www/pages/global/nav.html:91
+msgid "Team"
+msgstr "团队"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Hall of Fame"
+msgstr "名人堂"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Academic papers and peer review"
+msgstr "学术报告与同行审查"
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Presentations, tutorials and articles"
+msgstr "报告、教程及文章"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Contact us"
+msgstr "联系我们"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Help"
+msgstr "帮助"
+
+#: i2p2www/pages/global/nav.html:101
+msgid "FAQ"
+msgstr "常见问题"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "How to browse I2P"
+msgstr "如何浏览 I2P"
+
+#: i2p2www/pages/global/nav.html:103
+msgid "Glossary"
+msgstr "词汇表"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Performance"
+msgstr "性能"
+
+#: i2p2www/pages/global/nav.html:105 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "论坛"
+
+#: i2p2www/pages/global/nav.html:108
+msgid "Volunteer"
+msgstr "志愿者"
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Get involved!"
+msgstr "参与!"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Develop"
+msgstr "开发"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Licenses"
+msgstr "许可证"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Release signing keys"
+msgstr "发行版签名公钥"
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Signed keys"
+msgstr "已签名密钥"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Developers keys"
+msgstr "开发者公钥"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Bug tracker"
+msgstr "Bug Tracker"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Academic research"
+msgstr "学术研究"
+
+#: i2p2www/pages/global/nav.html:122
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:123
+msgid "Guides"
+msgstr "向导"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "New developers"
+msgstr "新开发者"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Using an IDE with I2P"
+msgstr "I2P 中使用 IDE"
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Developer guidelines and coding style"
+msgstr "开发者指引与代码风格"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Monotone"
+msgstr "单调"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "New translators"
+msgstr "新翻译人员"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Bounties"
+msgstr "赏金"
+
+#: i2p2www/pages/global/nav.html:134 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "会议"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Roadmap"
+msgstr "路线图"
+
+#: i2p2www/pages/global/nav.html:136
+msgid "Task list"
+msgstr "任务列表"
+
+#: i2p2www/pages/global/nav.html:139
+msgid "Language"
+msgstr "语言"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr "I2P 会议 ATOM 源"
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "过后 I2P 会议记录"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr "直到能找到更合适的时间前，会议目前暂停。"
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"如果您有任何需要讨论的话题，请到 IRC #i2p-dev 找开发者。\n"
+"开发者的状态更新 仍然更新。"
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr "I2P 开发会议 %(id)s"
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr "IRC 完整日志"
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "按主题"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "按日期"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "按作者"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
            \n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
            \n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+"新论文或更正后的论文请发送至 %(email)s。\n"
+"
            如果可能，请使用 BibTeX 格式，示例参见 BibTeX 源页面 。\n"
+"
            如果可能请提供链接: 离线论文帮助有限。"
+
+#: i2p2www/pages/papers/list.html:94
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"Free Haven's anonymity bibliography."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "联系"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr "电子邮件"
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like OFTC,\n"
+"  EIN and Freenode.\n"
+"  All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+"我们的主 IRC 网络是 I2P 中的 IRC2P 网络; 新安装的路由器设置有默认隧道连接至此网络。\n"
+"我们同时也出现在多个标准网络上，例如OFTC，EIN，Freenode。\n"
+"这些网络中所有 I2P 相关的频道都通过 IRC2P 中的中继机器人相互连通。"
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "频道列表:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "一般 i2p 讨论"
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "跑题灌水"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "开发讨论"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "帮助频道"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"大部分有关 I2P 开发的讨论在 I2P 开发者论坛。如果 IRC "
+"太安静，这通常是咨询问题的最佳地方。"
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "邮件列表"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr "I2P 确实有邮件列表，但当前的团队不大倾向使用 IRC 和开发者论坛，很少使用邮件列表。但也许未来会改变。"
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "订阅"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr "要加入邮件列表，请到列表的信息页面(下方链接)，完成表单。可以使用 I2P-内部邮件地址 (例如foobar@mail.i2p)。"
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "取消订阅"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr "要取消订阅或编辑您的订阅选项，请到信息页面(下方链接)输入您的订阅邮件地址。"
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "列表"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "存档"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr "一般性 I2P 讨论 - 任何不属于其它列表类型的话题。"
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr "您不喜欢邮件列表? 那这也许适合你，所有邮件列表都支持 NNTP 新闻组协议。"
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr "分组-列表-映射"
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "服务器:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "常见问题问答"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "索引"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "一般话题"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "I2P 支持运行的系统?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr "什么是 \"eepsite\" ，如何配置我的浏览器使用它们?"
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "我的路由器活动节点很少，正常吗?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr "路由控制台中的活动数值 x/y 是什么意思?"
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr "我的活动节点/已知节点/参加通道/连接数/带宽 变化太大!"
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "使用出口代理安全吗?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr "I2P中的大部分站点都打不开?"
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "I2P 使用哪些端口?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "我什么我的 I2P "
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "我想我发现了一个bug，到那里报告?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr "*.i2p.net 和 jrandom 怎么了? ? I2P 结束了吗?"
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "我有问题要问!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr "设置"
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr "我的路由器已经启动几分钟了，仍然只有 0 或非常少的连接数。"
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "为什么 I2P 如此慢?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr "我的地址簿中缺少很多主机记录。有什么好的订阅链接?"
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "如果设置我的 eepsite?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "Bittorrent / I2PSnark / Azureus I2P 插件的问题?"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "如何使用 I2P 连接至 IRC?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "我无法通过 I2P 访问普通的网站。"
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "我无法通过 I2P 访问 https:// 或 ftp:// 网站。"
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr "是否可以使用 I2P 作为 SOCKS 代理?"
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "如何设置我的浏览器?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr "如何给控制台加密码，通过我的其它电脑访问网页控制台?"
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr "如何从其它电脑使用我的程序?"
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr "如何手工补种(reseed)?"
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "我的路由器占用了过多的CPU!?"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "误区"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr "如何访问公网上的 IRC，BitTorrent，或其它服务?"
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr "我的路由器是公网的“出口节点”吗?我可不想这样。"
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr "我反对某些类型的内容。如何防止对它们的散布、储存或访问?"
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "错误及解决方法"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr "我使用 FreeBSD ，当启动 I2P 时，我收到有关 libm.so.4 的错误信息!"
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+"I2P 载入时，我在 wrapper.log 中看到错误 Protocol family "
+"unavailable"
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "链接"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+"I2P已在Windows, Linux, FreeBSD (见以下注释) OSX, "
+"和OpenSolaris上测试过。I2P Android平台的工作正在进行中。"
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr "这里有一些地方，挑选一个或多个。"
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "与开发者们在IRC频道#i2p-dev上讨论"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr "请包含来自路由器日志以及wrapper服务的日志获取到的相关信息"
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+"默认的订阅源（  http://www.i2p2.i2p/hosts.txt ）很少更新\n"
+"如果你没有其他订阅，你可能会用很多次\"jump\"链接\n"
+"这确实很恼人"
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+"这里有一些其他的公共的地址簿订阅链接，或许您想添加一个或两个到您的 susidns 订阅列表"
+"\n"
+"您不需要全部添加，因为他们会自动互相同步\n"
+"这个链接使用CGI程序以及一些程序策略来确保不会有重复列表更新以增加效率。\n"
+"警告：您应该订阅可信的hosts.txt列表，如果您订阅了恶意的列表，将会导致您访问错误的地址（就像GFW的DNS劫持=。=）"
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+"Jrandom在曾经的几年中是I2P和Syndie "
+"的主要开发者，我们不知道什么时候Jrandom会回来。\n"
+"*.i2p.net的域名曾经在在主机托管公司停电之后一直保持着非正常状态。。。"
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+"点击这个页面来看Jrandom的离别留言（好煽情的感觉..）以及附加信息关于i2p.net迁移到本网站的说明."
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr "I2P项目仍然进行保持开发中。"
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr "这里有许多的可能造成CPU使用量过该。这里来查看："
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+"尝试使用其他的OpenJDK或者Sun/Oracle Java如果其在您的系统上可用，您可以通过命令提示符上使用java "
+"-version来查看您的Java版本，使用其他版本的Java可能导致性能下降。"
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr "您是否通过I2P在使用BitTorrent？尝试减少种子的数量，设置带宽限制或者全都关掉来看看是否有帮助。"
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+"您的带宽限制是不是设置的过高？这可能会导致使用使用过多的流量导致I2P路由器过载。。尝试减少共享流量百分比在配置 页面."
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr "请确保您运行的是最新版本的I2P以增加使用效率和修复的bug。"
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+"是否设置了足够的内存分配给I2P使用？在 图形页面 "
+"来看内存是否是分配过的。JVM经常花费大量时间来“收集垃圾”（这里应该指释放内存），增加这个设置wrapper.java.maxmemory在wrapper.config"
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+"您或许可以使用基于Java的BigInteger库来代替原始版本,尤其是您正在使用新的或者不常用的OS或硬件时,如(OpenSolaris, "
+"mipsel等)\n"
+"看jbigi页面获取有关诊断，构建以及测试方式的说明"
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+"如果您的原生jbigi库工作的很好，使用CPU最大的部分可能是为组建隧道而交换流量的。这要用很多CPU因为每个加密的跃点必须被解密。您可以通过两个方式来减少构建所需要的流量："
+"\n"
+"1.在confignet.jsp减少共享带宽\n"
+"2.在configadvanced.jsp设置router.maxParticipatingTunnels=nnn的值。"
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+"额，I2P是一个匿名网络，这是很严峻的。\n"
+"I2P的设计是为了对抗网络审查(如中国的链接被重置，韩国的KCSC Warning =。=),让所有人都能自由的通讯。\n"
+"让你电脑从这些您不喜欢的信息解放出来的最佳方法就是不用I2P.\n"
+"言论自由总是要有些付出的.\n"
+"但是让我们来从3部分解决您的问题："
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+"存储 - I2P不会分发存储信息。您必须考虑Freenet。没有任何人的信息会因为您运行I2P而保留下来。"
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr "访问 - 如果有一些eepsites您不喜欢，那就不要访问吧～（蛋疼） 或者 阻挡（Privoxy或者绿霸等过滤软件）"
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+"不，这是正常的。\n"
+"所有路由器会动态调节去改变网络条件和需求。"
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+"您或许需要Reseed(就是重新获取节点)您的I2P路由，近期版本的I2P您可以去http://localhost:7657/configreseed并且点击“保存设置并且立即Reseed”按钮。如果这种方式不可以，或者您在使用非常老的版本，您可能需要手动Reseed."
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+"Reseed的网址已经在数年之前修改了，如果您首次安装的是老版本(0.6.1.30或更老)，或者您已经长时间没有运行I2P了，您必须修改Reseed的URL并且点击Reseed按钮去获取其他节点。在运行I2P路由之后，在configadvanced.jsp添加一行i2p.reseedURL=http://netdb.i2p2.de/或i2p.reseedURL=http://i2pdb.tin0.de/netDb/(两个都添加也可以)"
+"\n"
+"然后点击应用之后点击左边的Reseed链接。"
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+"这个在 0.6.1.27 版本之后的I2P工作，如果您正在运行 0.6.1.31 或者之后的，您可能不需要做这些，如果您在运行 0.6.1.26 "
+"或以前的，请看下方的手动Reseed说明或安装最新版本。\n"
+"可能的替代方法 —— 添加 "
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/ "
+"到wrapper.config，完整重启I2P,并且点击Reseed。 如果这个方法工作，请让我们知道。"
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr "...但是您*真的*应该升级到最新版本。"
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+"如果您的I2P路由有10个或更多的活动节点，它会工作的很好。在 0.6.1.31 和 0.6.1.32 提升了I2P的效率，降低了活动节点的数量\n"
+"I2P应该只维护一小部分节点在使用时\n"
+"停留在“更好地链接”最好的方法就是共享更多带宽。"
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr "我的I2P是不是在常规网络上作为一个“出口节点”？我不想作为出口节点。"
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+"在 I2P，没有使用HTTPS的必要，因为所有通信都被端到端加密过。\n"
+"由于技术原因，FTP不被支持。"
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+"这是没有FTP的出口代理到internet的，这或许没有可能去设置一个。其他种类的出口代理在设置正确的情况下或许可以工作\n"
+"如果您想设置一些种类的出口代理，请仔细研究潜在的风险（出口代理=出口节点，外面看到的IP都是您的，查的也是您家的水表）\n"
+"I2P社区可能也可能不能去帮助您的技术问题，如果想问的话请便～（有中文版块额～）"
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+"上面说过很多次了（嗯哼，暴走中..）,任何存在的出口节点都不是I2P网络中的一部分。\n"
+"这些服务是隐藏的运行并且他们可能也可能不能被在任何时候使用。"
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
            \n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+"更新 : 感谢h2ik作出的贡献，从 I2P 0.8.4 开始，我们有了HTTPS的出口代理，该隧道 "
+"已经配置了。如果这个HTTPS出口代理在您的I2P版本中不可用，您可以通过以下步骤简单添加："
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+"打开 i2p "
+"隧道管理器，滑到最下方。"
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr " 从 新建客户隧道 下拉列表中选择 CONNECT ，然后选择创建"
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+"打开新的页面，名称和describe您可以为您的HTTPS隧道自定\n"
+"访问点是您的HTTPS代理的本地地址，建议设置为4445\n"
+"出口代理应该是支持HTTPS的出口代理的.i2p地址看这个链接h2ik来获取这个地址。\n"
+"确保共享的客户端, 延迟链接, 自动启动已被选中\n"
+"其他的选项应该留在默认，点击保存，点击隧道管理器，点击开始按钮启动您添加的新的隧道"
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+"在火狐中，点击工具 > 选项 > 高级 > 网络 > 设置.\n"
+"不选择为所有协议使用该代理, 设置SSL代理到localhost:4445"
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "完成."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+"\n"
+"这个问题只有您能回答，因为这个问题的答案是根据您的个人喜好指定的，您的威胁模型以及您是否信任出口代理的操作者。"
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+"就像Tor , I2P不会神奇般的加密互联网。\n"
+"您可能会被出口代理的运营者所窥探\n"
+"The Tor"
+" FAQ是解释这个问题很好的文档。"
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+"附加，您可能会被如果您使用了相同的隧道(“共享的客户端”)的出口代理的运营者以及其他I2P服务的运营者合谋利用\n"
+"更多附加讨论信息在%(zzz)s."
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr "获取说明，点击网站链接在您的I2P控制台的顶端"
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+"为什么下载，做种，web浏览以及其他事情在I2P下会很慢？\n"
+"在I2P内部的加密和路由增加了大量带宽的开销，并且有流量限制。"
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+"附加，任何人可能都需要添加您的带宽限制\n"
+"两个关键的设置是入口和出口带宽限制，在设置页面\n"
+"默认的32KBps，您将获得不会多于15KBps的数据传输速度在I2PSnark.\n"
+"增加者个设置(但是仍然保持您的真实带宽，就是运营商给您限的速)\n"
+"将增加I2PSnark和其他程序的速度。"
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr "同样，您是否有足够的分享带宽通过您的I2P？无论您是否相信，允许共享流量将会帮助您提高速度"
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+"I2P的工作仍在进行，很多提高与修复正在被实施，一般来说，运行最新的版本可以帮助提高您的性能。如果您没有，请安装最新版."
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr "看I2P Bittorrent 常见问答"
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+"\n"
+"到达I2P内部的IRC服务器，Irc2P已经在I2P被安装的时候创建，(看 I2P隧道设置页面),他会自动启动当I2P路由启动时。如果想去链接他，告诉您的IRC客户端连接到localhost"
+" 6668. 像XChat的客户端用户可以通过服务器localhost/6668新建一个新的网络 "
+"(记住勾选 绕过代理服务器如果您已经设置代理的话)"
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface.  However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr "为了安全原因，I2P的主控制面板只在本地监听。无论如何，通过一点点的改造，您可以让他远程访问。"
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
            \n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
            \n"
+"with 
            \n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+"打开~/.i2p/clients.config并且替换
            \n"
+"clientApp.0.args=7657::1,127.0.0.1 ./webapps/
            \n"
+"为\n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+"到http://localhost:7657/index.jsp，点击“平和重启”"
+" 将会重启JVM并且重载客户端程序。"
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+"在默认情况下，I2P的 I2CP界面(7654端口) 监听到127.0.0.1 . 如果您想监听到0.0.0.0, "
+"设置I2P路由器高级设置选项为i2cp.tcp.bindAllInterfaces=true 并且重启。"
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "什么是 \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr "eepsite是一个匿名托管的网站 —— 您可以把浏览器的HTTP代理设置为(localhost，端口4444)来访问它。"
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+"不同浏览器的代理设置在  分离的页面 "
+"以及屏幕截图，更多通过额外工具的高级设置（如插件）将有可能在您的设置中导致泄漏。"
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+"x 是一个数，显示了您上一分钟成功接受或发送消息的节点的数量\n"
+"y 是上一个小时的数。"
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr "SOCKS代理 4/4a/5 在0.7.1版本中有，现在没有SOCKS出口代理了所以限制使用。"
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity.  For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+"此外，许多应用可能泄露你在互联网上的身份等敏感信息。I2P只能保护连接数据 "
+"如IP地址等，但如果你要运行的程序发送您的敏感信息为内容，I2P将无法保护您的匿名性。例如，一些邮件应用程序将发送运行它的计算机的IP地址到邮件服务器。I2P无法过滤这些信息，但是通过I2P'socksify'来运行应用是可行的，但是这是很危险的。"
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr "如果您仍然想要更多信息关于socks代理应用，这里有一些有用的提示在socks 页面."
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr "好吧。这里是一些默认端口的摘要(每个端口都可以通过设置来改变)"
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+"面向互联网的端口\n"
+"提示：自从0.7.8后的新的版本将不再使用8887端口作为默认通讯端口，现在将会在程序第一次运行时在9000-31000之间自动选择端口，端口将在I2P路由的配置页面"
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+"    "
+msgstr ""
+"出口UDP端口的设置在配置页面中，可以是接受回复的随意UDP端口。"
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+"    "
+msgstr "出口TCP端口来自随机高端口号到随意的TCP端口"
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+"    "
+msgstr ""
+"(可选的，但是建议) 入口UDP端口在 配置页面中已经标记，从随意的地点"
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
            \n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+"(可选的，但是建议) 入口TCP端口在 配置页面中已经标记，从随意的地点
            "
+"\n"
+"人口TCP或许已经在配置页面中被禁用。"
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
            \n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+"在端口123的出口UDP允许回复
            \n"
+"这对于I2P是必要的，用来内部时间同步(通过SNTP - 请求在pool.ntp.org的随记忆台服务器或者其他您指定的服务器)"
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr "本地I2P端口, 默认情况下只在您的本地监听,除非另有说明:"
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"1900: UPnP SSDP UDP 组播监听\n"
+"不可被改变，在所有网卡上监听，可在confignet.jsp中禁用"
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+"2827: BOB桥, 对于客户端更高级的socket API\n"
+"默认被禁用.可在\n"
+"confignet.jsp禁用或启用."
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4444: HTTP代理\n"
+"或许被禁用或改变在i2ptunnel设置页面中 或许同样被配置在在所有网卡上使用"
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally.  You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance.  You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr "为什么 I2P 监听于 32000 端口?"
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the  \n"
+"wrapper documentation."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+"一个典型的补种失败情况是\"已知节点\"指示器 (在路由器控制台的左边栏) 只显示一个非常小的值 (通常小于5) 而且并不增加。 \n"
+"如果没有别的情况发生，这会出现在你的防火墙限制了出站流量并且封锁了补种请求时。"
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr "请按照以下步骤手动Reseed您的I2P"
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr "关闭你的I2P路由器"
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr "用网页浏览器打开http://netdb.i2p2.de/"
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr "启动你的I2P路由器"
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr "使用su切换到 root 用户 或以 root 身份登录。"
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr "在Linux系统下，您可以执行 echo 0 > /proc/sys/net/ipv6/bindv6only "
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great!  Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "德国法律"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr "I2P 匿名网络"
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr "通过开源工具设计建立的匿名点对点分布式通讯层，可以允许任意传统网络服务例如 电邮，IRC 或 Web 托管。"
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr "I2P 能为您做什么?"
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr "I2P 网络为通过 Internet 进行的通讯提供强有力的隐私保护。很多在公网上可能威胁用户隐私的活动可以在 I2P 中匿名进行。"
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr "下载 I2P %(version)s"
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "I2P 是什么?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr "I2P被很多关注自己隐私的人使用，例如活动家，被压迫的人民，记者，爆料者和一般人。\n"
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr "没有网络可以做到完美匿名，I2P的目标是让攻击变得更困难，让匿名性更强以及让匿名网络更大，并且持续进行评测。\n"
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr "I2P在计算机，嵌入式系统(比如树莓派)和安卓手机上可用。帮助我们传播。\n"
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr "了解更多 …"
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr "我能用 I2P 做什么?"
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr "更多支持的应用 …"
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr "新闻 & 更新"
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr "推荐链接 & 资源"
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+"同时请看\n"
+"有关 I2P 的演讲、视频及教程。"
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr "I2P 之友"
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr "更多项目和文档"
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "新闻"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr "论坛，新闻站，其它"
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr "非常老的东西"
+
diff --git a/i2p2www/urls.py b/i2p2www/urls.py
index d77425da..5d81101e 100644
--- a/i2p2www/urls.py
+++ b/i2p2www/urls.py
@@ -38,6 +38,13 @@ url('/', 'views.main_index')
 url('//', 'views.site_show', defaults={'page': 'index'})
 url('//', 'views.site_show')
 
+url('//papers/', 'anonbib.views.papers_list')
+url('//papers/bibtex', 'anonbib.views.papers_bibtex')
+url('//papers/by-', 'anonbib.views.papers_list')
+url('//papers/tag//', 'anonbib.views.papers_list')
+url('//papers/tag//bibtex', 'anonbib.views.papers_bibtex')
+url('//papers/tag//by-', 'anonbib.views.papers_list')
+
 url('//blog/', 'blog.views.blog_index', defaults={'page': 1})
 url('//blog/page/', 'blog.views.blog_index')
 url('//blog/category/', 'blog.views.blog_index', defaults={'page': 1})
@@ -55,6 +62,7 @@ url('//meetings/.rst', 'meetings.views.meetings_show_rst')
 url('//feed/meetings/atom', 'meetings.views.meetings_atom')
 
 url('//download', 'downloads.downloads_list')
+url('//download/debian', 'downloads.downloads_debian')
 url('//download//', 'downloads.downloads_select')
 url('/download///any/', 'downloads.downloads_redirect', defaults={'domain': None})
 url('/download////', 'downloads.downloads_redirect')
@@ -63,10 +71,15 @@ url('/meeting', 'legacy.legacy_meeting')
 url('/meeting.html', 'legacy.legacy_meeting')
 url('/status---', 'legacy.legacy_status')
 url('/status---.html', 'legacy.legacy_status')
+url('/release-_', 'legacy.legacy_release')
+url('/release-_.html', 'legacy.legacy_release')
+url('/release-/', 'legacy.legacy_release')
+url('/release-.html', 'legacy.legacy_release')
 url('/_', 'legacy.legacy_show')
 url('/_.html', 'legacy.legacy_show')
 url('//', 'legacy.legacy_show')
 url('/.html', 'legacy.legacy_show')
+url('/.txt', 'legacy.legacy_show')
 
 url('/hosts.txt', 'views.hosts')
 url('/robots.txt', 'views.robots')
diff --git a/init-new-po.sh b/init-new-po.sh
index 4d9ea0f7..e8395ac2 100755
--- a/init-new-po.sh
+++ b/init-new-po.sh
@@ -1,9 +1,13 @@
 #!/bin/sh
-. ./translation.vars
+. ./etc/translation.vars
+
+export TZ=UTC
 
 if [ $# -ge 1 ]
 then
-    TZ=UTC env/bin/pybabel init -i $POTFILE -d $TRANSDIR -l $1
+    for domain in $(ls $BABELCFG); do
+        $PYBABEL init -D $domain -i $POTDIR/$domain.pot -d $TRANSDIR -l $1
+    done
 else
     echo "Usage: ./init-new-po.sh lang"
 fi
diff --git a/pybabel b/pybabel
deleted file mode 100755
index 0c119a66..00000000
--- a/pybabel
+++ /dev/null
@@ -1,10 +0,0 @@
-#!env/bin/python
-# EASY-INSTALL-ENTRY-SCRIPT: 'Babel==0.9.6','console_scripts','pybabel'
-__requires__ = 'Babel==0.9.6'
-import sys
-from pkg_resources import load_entry_point
-
-if __name__ == '__main__':
-    sys.exit(
-        load_entry_point('Babel==0.9.6', 'console_scripts', 'pybabel')()
-    )
diff --git a/runserver.py b/runserver.py
index 9884e219..2d1a4c9f 100755
--- a/runserver.py
+++ b/runserver.py
@@ -1,3 +1,5 @@
 #!env/bin/python
 from i2p2www import app
-app.run(debug=False)
+
+if __name__ == '__main__':
+    app.run(host='127.0.0.1', port=5000, debug=False)
diff --git a/setup_venv.sh b/setup_venv.sh
index af98f169..9b3b3a40 100755
--- a/setup_venv.sh
+++ b/setup_venv.sh
@@ -1,14 +1,17 @@
 #!/bin/sh
 set -e
-. ./project.vars
+. ./etc/project.vars
 
 if [ ! $venv ]; then
     echo "ERROR: virtualenv not found!" >&2
+    exit 1
 else
     if [ ! -d $venv_dir ] ; then
         $venv --distribute $venv_dir
     fi
 
     . $venv_dir/bin/activate
-    pip install -r reqs.txt
+    pip install -r etc/reqs.txt
+    # Apply multi-domain patch to Flask-Babel
+    patch -p0 -N -r - &1 | tee $TMP
+
+
+if grep "^mtn: \(add\|patch\|dropp\|updat\)\(ed\|ing\) 'i2p2www/translations/" "$TMP" >/dev/null ; then
+  echo "Translations updated, compiling messages"
+  ./compile-messages-i2hq.sh
+fi
+
+if grep "^mtn: updating 'i2p2www/.*\.py\|^mtn: updating 'i2p2www/.*/.*\.py" "$TMP" >/dev/null ; then
+  echo "Python files changed, restarting server"
+  touch $TOUCHFILE
+fi
diff --git a/site-updater.sh b/site-updater.sh
new file mode 100755
index 00000000..73f77c67
--- /dev/null
+++ b/site-updater.sh
@@ -0,0 +1,19 @@
+#!/bin/sh
+. ./etc/update.vars
+
+TMP=$(mktemp XXXXXXXXXX)
+trap 'rm -f $TMP;exit' 0 1 2 15
+
+mtn pull "mtn://$MTNURL?$MTNBRANCH"
+mtn up 2>&1 | tee $TMP
+
+
+if grep "^mtn: \(add\|patch\|dropp\|updat\)\(ed\|ing\) 'i2p2www/translations/" "$TMP" >/dev/null ; then
+  echo "Translations updated, compiling messages"
+  ./compile-messages.sh
+fi
+
+if grep "^mtn: updating 'i2p2www/.*\.py\|^mtn: updating 'i2p2www/.*/.*\.py" "$TMP" >/dev/null ; then
+  echo "Python files changed, restarting server"
+  touch $TOUCHFILE
+fi
diff --git a/translation.vars b/translation.vars
deleted file mode 100644
index 27a7c47e..00000000
--- a/translation.vars
+++ /dev/null
@@ -1,6 +0,0 @@
-PROJECT=I2P
-VERSION=website
-PROJDIR=i2p2www
-BABELCFG=$PROJDIR/babel.cfg
-POTFILE=messages.pot
-TRANSDIR=$PROJDIR/translations
diff --git a/update-existing-po.sh b/update-existing-po.sh
index 6d4d1717..4ddedef2 100755
--- a/update-existing-po.sh
+++ b/update-existing-po.sh
@@ -1,4 +1,12 @@
 #!/bin/sh
-. ./translation.vars
+. ./etc/translation.vars
+export TZ=UTC
 
-TZ=UTC env/bin/pybabel update -i $POTFILE -d $TRANSDIR
+if [ $# -ge 1 ]
+then
+    $PYBABEL update -D $1 -i $POTDIR/$1.pot -d $TRANSDIR
+else
+    for domain in $(ls $BABELCFG); do
+        $PYBABEL update -D $domain -i $POTDIR/$domain.pot -d $TRANSDIR
+    done
+fi
diff --git a/www.i2p2/README b/www.i2p2/README
deleted file mode 100644
index 1b8ba45d..00000000
--- a/www.i2p2/README
+++ /dev/null
@@ -1,14 +0,0 @@
-To run locally (for testing purposes):
-
-$ python app.py
-This will run a webserver on http://localhost:5009/
-
-If you get python import errors when trying to run the local web server, you
-might need to install required dependencies: jinja and werkzeug. If you are
-using Linux, they might be in the repository of your distribution. Otherwise
-you will have to install them yourself. Please see the homepages of these
-projects:
-
-http://jinja.pocoo.org/
-http://werkzeug.pocoo.org/
-
diff --git a/www.i2p2/app.py b/www.i2p2/app.py
deleted file mode 100644
index 76323b41..00000000
--- a/www.i2p2/app.py
+++ /dev/null
@@ -1,74 +0,0 @@
-from werkzeug import BaseRequest, BaseResponse, ETagResponseMixin, escape, run_simple, SharedDataMiddleware
-from werkzeug.exceptions import HTTPException
-from werkzeug.routing import RequestRedirect
-from jinja import Environment, FileSystemLoader, MemcachedFileSystemLoader
-from jinja.exceptions import TemplateNotFound
-import os
-from time import time
-from random import randint
-
-domain = "http://www.i2p2.de"
-
-class Request(BaseRequest):
-    """Useful subclass of the default request that knows how to build urls."""
-
-    def __init__(self, environ):
-        BaseRequest.__init__(self, environ)
-
-
-class Response(BaseResponse, ETagResponseMixin):
-    """Subclass of base response that has a default mimetype of text/html."""
-    default_mimetype = 'text/html'
-
-
-# setup jinja
-try:
-    env = Environment(loader=MemcachedFileSystemLoader('pages', memcache_host=['127.0.0.1:11211'], memcache_time=5*60))
-except RuntimeError:
-    env = Environment(loader=FileSystemLoader('pages', use_memcache=False, auto_reload=True))
-
-def app(environ, start_response):
-    """The WSGI application that connects all together."""
-    req = Request(environ)
-    path = req.path[1:].lower()
-    # do theme handling
-    theme = 'light'
-    if 'style' in req.cookies:
-        theme = req.cookies['style']
-    if 'theme' in req.args.keys():
-        theme = req.args['theme']
-    if not os.path.isfile('static/styles/%s.css' % theme):
-        theme = 'light'
-    if path == '':
-        path = 'index'
-    mime_type='text/html'
-    try:
-        try:
-            path.index('.')
-            if path.split('.')[-1].isdigit() and not path.split('.')[-1].isalpha():
-                raise ValueError()
-            tmpl = env.get_template(path)
-            if path[-3:] == 'txt':
-                mime_type='text/plain'
-            if path[-3:] == 'xml':
-                mime_type='text/xml'
-        except ValueError:
-            tmpl = env.get_template(path + '.html')
-    except TemplateNotFound:
-        tmpl = env.get_template('not_found.html')
-    resp = Response(tmpl.render(static=False, theme=theme, domain=domain, path=path), mimetype=mime_type)
-    # more theme handling
-    if theme == 'light' and 'style' in req.cookies:
-        resp.delete_cookie('style')
-    elif theme != 'light':
-        resp.set_cookie('style', theme)
-    resp.add_etag()
-    resp.make_conditional(req)
-    return resp(environ, start_response)
-
-app = SharedDataMiddleware(app, {
-    '/_static': os.path.join(os.path.dirname(__file__), 'static')
-})
-
-if __name__ == '__main__':
-    run_simple('localhost', 5009, app)
diff --git a/www.i2p2/generate.py b/www.i2p2/generate.py
deleted file mode 100644
index f37b93d7..00000000
--- a/www.i2p2/generate.py
+++ /dev/null
@@ -1,26 +0,0 @@
-#!/usr/bin/env python
-import os
-from jinja import Environment, FileSystemLoader
-#from codecs import open
-
-env = Environment(loader=FileSystemLoader('pages'), trim_blocks=True, friendly_traceback=False)
-
-
-def get_files(folder):
-    for fn in os.listdir(folder):
-        if fn.startswith('_'):
-            continue
-        fn = os.path.join(folder, fn)
-        if os.path.isdir(fn):
-            for item in get_files(fn):
-                yield item
-        else:
-            yield fn
-
-for filename in get_files('pages'):
-    print filename
-    filename = filename.split('/', 2)[1]
-    t = env.get_template(filename)
-    f = open(os.path.join('out', filename), 'w')
-    f.write(t.render(static=True).encode('utf-8'))
-    f.close()
\ No newline at end of file
diff --git a/www.i2p2/generate.sh b/www.i2p2/generate.sh
deleted file mode 100755
index f56989fc..00000000
--- a/www.i2p2/generate.sh
+++ /dev/null
@@ -1,5 +0,0 @@
-#!/bin/sh
-rm -rf out
-mkdir out
-cp -R static out/_static
-python generate.py
diff --git a/www.i2p2/pages/old/announcements.html b/www.i2p2/pages/old/announcements.html
index c82683f2..81355719 100644
--- a/www.i2p2/pages/old/announcements.html
+++ b/www.i2p2/pages/old/announcements.html
@@ -4,6 +4,11 @@
 
            Past I2P Release Announcements
            
 
            2013
            
 
diff --git a/www.i2p2/pages/translations/announcements_ar.html b/www.i2p2/pages/translations/announcements_ar.html
index 7ea52780..7213b020 100644
--- a/www.i2p2/pages/translations/announcements_ar.html
+++ b/www.i2p2/pages/translations/announcements_ar.html
@@ -6,6 +6,11 @@
 
 
            2013
            
 
diff --git a/www.i2p2/pages/translations/announcements_de.html b/www.i2p2/pages/translations/announcements_de.html
index e8454f56..fede06f4 100644
--- a/www.i2p2/pages/translations/announcements_de.html
+++ b/www.i2p2/pages/translations/announcements_de.html
@@ -5,6 +5,11 @@
 
            Hinweis: Da i2p.net nicht erreichbar ist, sind viele Verweise nicht funktional
            
 
            2013
            
 
diff --git a/www.i2p2/pages/translations/announcements_el.html b/www.i2p2/pages/translations/announcements_el.html
index 1f6d23d9..acd25fee 100644
--- a/www.i2p2/pages/translations/announcements_el.html
+++ b/www.i2p2/pages/translations/announcements_el.html
@@ -4,6 +4,11 @@
 
            Προηγουμενες ανακοινωσεις των εκδοσεων του I2P
            
 
            2013
            
 
diff --git a/www.i2p2/pages/translations/announcements_fr.html b/www.i2p2/pages/translations/announcements_fr.html
index a7ebfd40..a2d544c5 100644
--- a/www.i2p2/pages/translations/announcements_fr.html
+++ b/www.i2p2/pages/translations/announcements_fr.html
@@ -4,6 +4,11 @@
 
            Historique des versions publiées
            
 
            2013
            
 
diff --git a/www.i2p2/pages/translations/announcements_it.html b/www.i2p2/pages/translations/announcements_it.html
index efffab01..ac155d70 100644
--- a/www.i2p2/pages/translations/announcements_it.html
+++ b/www.i2p2/pages/translations/announcements_it.html
@@ -4,6 +4,11 @@
 
            Versioni di I2P Rilasciate e Annunciate
            
 
            2013
            
 
diff --git a/www.i2p2/pages/translations/bounties_ar.html b/www.i2p2/pages/translations/bounties_ar.html
index 725bce5f..4a5efc8f 100644
--- a/www.i2p2/pages/translations/bounties_ar.html
+++ b/www.i2p2/pages/translations/bounties_ar.html
@@ -135,7 +135,7 @@
  
  
   
            GCJ دعم
            
-  
            مستعمل
            
+  
            مستعمل
            
   
            jrandom
            
  
 
diff --git a/www.i2p2/pages/translations/bounties_de.html b/www.i2p2/pages/translations/bounties_de.html
index ee179c25..6bf46db3 100644
--- a/www.i2p2/pages/translations/bounties_de.html
+++ b/www.i2p2/pages/translations/bounties_de.html
@@ -48,13 +48,6 @@ etc.) benutzt wird.
            
   
            [vacant]
            
   
            €100 EUR
            
  
- 
-   
            Belohnung für die Anpassung von I2P an IPv6
            
-   
            Entwickler gesucht
            
-   
            Amiga4000
            
-   
            [vacant]
            
-   
            €100 EUR und 50BTC
            
- 
  
   
            I2P Paket in Debian und Ubuntu Spiegelserver
            
   
            Entwickler gesucht
            
@@ -67,7 +60,7 @@ etc.) benutzt wird.
            
   
            Erledigt, Verifikationsphase
            
   
            psychonaut
            
   
            giv
            
-  
            €30 EUR und 118,34BTC
            
+  
            €30 EUR und 118,34BTC, davon 30 EUR und 68 BTC ausgezahlt
            
  
  
   
            Unit tests und Multi-router-Simulation
            
@@ -103,6 +96,13 @@ etc.) benutzt wird.
            
 
 
+  
+   
+   
+   
+   
+   
+ 
@@ -145,7 +145,7 @@ etc.) benutzt wird.
            
-  
+  
            
  
            Name
            Status
            Entwickler Team*
            Belohnung für die Anpassung von I2P an IPv6
            erledigt
            Amiga4000
            I2P team
            €100 EUR und 50BTC
            
  
            
   
            SILC Server in I2P
            		
   
            zurückgezogen, Geld an ReturningNovice und Generelles Konto ausgezahlt
            		
  
            
  
            
   
            GCJ support
            Ausgezahlt
            Ausgezahlt
            		
   
            jrandom
            		
  
            
 
            
diff --git a/www.i2p2/pages/translations/bounties_it.html b/www.i2p2/pages/translations/bounties_it.html
index 3b87db15..08c0a23a 100644
--- a/www.i2p2/pages/translations/bounties_it.html
+++ b/www.i2p2/pages/translations/bounties_it.html
@@ -115,7 +115,7 @@ etc e simili.
            
  
  
   
            GCJ support
            
-  
            Claimed
            
+  
            Claimed
            
   
            jrandom
            
  
 
diff --git a/www.i2p2/pages/translations/bounties_ru.html b/www.i2p2/pages/translations/bounties_ru.html
index d90f4d04..6a16a0fb 100644
--- a/www.i2p2/pages/translations/bounties_ru.html
+++ b/www.i2p2/pages/translations/bounties_ru.html
@@ -104,7 +104,7 @@
  
  
   
            Поддержка GCJ
            
-  
            Востребована
            
+  
            Востребована
            
   
            jrandom
            
  
 
diff --git a/www.i2p2/pages/translations/bounty_ipv6_de.html b/www.i2p2/pages/translations/bounty_ipv6_de.html
index ff6c3a69..4337a6fc 100644
--- a/www.i2p2/pages/translations/bounty_ipv6_de.html
+++ b/www.i2p2/pages/translations/bounty_ipv6_de.html
@@ -9,6 +9,8 @@ Um diese Belohnung zu bekommen, muss I2P auf einer IPv6 Verbindung
 funktionieren wie es derzeitig auf IPv4 funktioniert. 
 
            
 
            
+Belohnung wurde ausgezahlt nachdem I2P mit Version 0.9.8 mit IPv6 funktioniert.
+
 
            
 Hinweis:
 Um die Belohnung für die Anwendungen zu reklamieren, wird das Programm
@@ -19,8 +21,5 @@ Der Autor darf nicht von einer anderen Organisation oder Gruppe bezahlt werden
 für den Quelltext (z.B. GSoC Studenten sind NICHT erlaubt).
            
 
 
-
            Hinweis 2: Die Höhe des Betrags kann durch weitere Spenden steigen.
-Findest Du diese Teile wichtig? Spende einen Betrag
-für die Belohnung zur Fertigstellung diese Software!
            
 
 {% endblock %}
diff --git a/www.i2p2/pages/translations/debian_fr.html b/www.i2p2/pages/translations/debian_fr.html
index f38181c2..af89de76 100644
--- a/www.i2p2/pages/translations/debian_fr.html
+++ b/www.i2p2/pages/translations/debian_fr.html
@@ -8,18 +8,17 @@ ont été testés et devraient fonction
 
 Les paquets I2P peuvent marcher sur des systèmes non listés ci-dessus. 
-Merci de rapporter tout problème avec ces paquets dans Trac sur 
-http://trac.i2p2.de.
+Merci de rapporter tout problème avec ces paquets dans Trac sur 
+http://trac.i2p2.no.
 
              
   
            • Option 1: Versions récentes  d'Ubuntu et ses dérivées 
 (À essayer si vous n'utilisez pas Debian)
              • 
   
            • Option 2: Debian (dont les systèmes basés sur Debian et les anciennes versions 
 d'Ubuntu)
              • 
-  
            • Option 3: Non-Linux (et peut-être les architectures non x-86)
              • 
 
            
 
            Instructions pour Ubuntu Precise Pangolin (et plus récentes) et ses dérivées comme Linux Mint & Trisquel
            
 
            Ajout du PPA via la ligne de commande et installation d'I2P
            
@@ -60,43 +59,50 @@ cliquez sur Ajouter à la sélection pui
 démarrer I2P et le configurer pour votre système.
 
 
            Instructions pour Debian Wheezy et plus récentes
            
+Currently supported architectures include amd64, i386, armel, armhf (for Raspbian), kfreebsd-amd64, kfreebsd-i386, and powerpc.
+
            
 Les étapes suivantes doivent être effectuées avec l'accès root (c.à d. en basculant de l'utilisateur en cours à root 
 avec "su" ou en préfixant chaque commande avec "sudo").
+
            
+
 
              
-  
            1. Ajoutez les entrées suivantes à /etc/apt/sources.list.d/i2p.list
              
-        deb http://ppa.launchpad.net/i2p-maintainers/i2p/ubuntu raring main 
              
-    deb-src http://ppa.launchpad.net/i2p-maintainers/i2p/ubuntu raring main 
              
-Ces deux lignes devraient fonctionner quelle que soit la version de Debian installée.
              2. 
-  
            2. Ajouter la clé GPG de signature du dépôt avec la commande suivante:
              
-    
-apt-key adv --keyserver keyserver.ubuntu.com --recv-keys EB2CC88B
              
-Vous obtiendrez une sortie semblable à la suivante si la commande a réussi: 
              
-    
              3. 
-  
            3. Instruisez votre gestionnaire de paquets de la nouvelle PPA en entrant
              
+
            4. Add lines like the following to /etc/apt/sources.list.d/i2p.list.
              
+For Squeeze:
              
+
              +    deb http://deb.i2p2.no/ squeeze main
+    deb-src http://deb.i2p2.no/ squeeze main
+
              
+
              
+For Wheezy:
              
+
              +    deb http://deb.i2p2.no/ stable main
+    deb-src http://deb.i2p2.no/ stable main
+
              
+
              
+For Testing or Unstable:
              
+
              +     deb http://deb.i2p2.no/ unstable main
+     deb-src http://deb.i2p2.no/ unstable main
+
              
+
              5. 
+
            5. Download the  key used to sign the repository and add it to apt:
              
+    apt-key add debian-repo.pub
+
              6. 
+
+  
            6. Notify your package manager of the new repository by entering
              
         apt-get update
              
-Cette commande va récupérer la dernière liste de logiciels depuis chaque dépôt activé sur votre système, dont ceux de 
-la 
-PPA I2P ajoutée à l'étape 1.
              7. 
-  
            7. Vous êtes maintenant prêt à installer I2P! 
              
-        apt-get install i2p
              8. 
-
            
-À la fin du processus d'installation vous pouvez passer à l'étape suivante pour 
-démarrer I2P et le configurer pour votre système.
-
            Instructions pour Non-Linux / Non-x86
            
-Les étapes suivantes doivent être effectuées avec l'accès root (c.à d. en basculant de l'utilisateur en cours à root 
-avec "su" ou en préfixant chaque commande avec "sudo").
            
-
              
-  
            1. Téléchargez le paquet i2p-router 
-depuis la PPA.
              2. 
-  
            2. Assurez-vous que Java est installé. Lancer 
-apt-get install default-jvm devrait suffire.
              
-Vous êtes maintenant prêt à installer I2P! 
              
-        dpkg -i i2p-router_*.deb
              3. 
-  
            3. On recommande de compiler jbigi pour votre système pour obtenir les meilleures performances. 
-Les instructions sont disponibles ici.
              4. 
+This command will retrieve the latest list of software from every
+repository enabled on your system, including the I2P repository added in step
+1.
+
            4. You are now ready to install I2P! Installing the i2p-keyring
+package will ensure that you receive updates to the repository's
+GPG key.
              
+        apt-get install i2p i2p-keyring
              5. 
 
            
 À la fin du processus d'installation vous pouvez passer à l'étape suivante pour 
 démarrer I2P et le configurer pour votre système.
+
+
 
            Après l'installation
            
 L'utilisation de ces paquets I2P vous permet de lancer le routeur de l'une de ces trois façons:
 
              
diff --git a/www.i2p2/pages/translations/download_ar.html b/www.i2p2/pages/translations/download_ar.html
index 7d8d598c..07b20bfd 100644
--- a/www.i2p2/pages/translations/download_ar.html
+++ b/www.i2p2/pages/translations/download_ar.html
@@ -4,9 +4,11 @@
 
              تحميل I2P
                    
 
              المتطلبات البرمجية
              
 اصدار 1.5 من Java Runtime (أو أعلى)
-(Oracle Java Version 6/7,
-OpenJDK 6/7, or
-IcedTea6/7
+(Oracle Java Version 7,
+OpenJDK 7, or
+IcedTea7,
+except Raspberry Pi: Oracle 8 Early Access,
+PowerPC: IBM SDK 7
  منصوح بهم)
 
              
 اعرف نسخة الجافا المثبتة لديك من هنا
@@ -14,62 +16,62 @@
 
              التثبيت لأول مرة
              
 
                
 
              • Windows التثبيت عن طريق الواجهة الرسومية :
                
-    i2pinstall_0.9.6_windows.exe
+    i2pinstall_0.9.9_windows.exe
     (SHA256
-bf7d11f0a36acff9cd51ad3ef89d66975b0b0de344ca72719a5576159ec965d1
-    sig)
+97dd4326ad8afdea0e78ffcb053b23793dfa79d89458be3fe3a1ed62a2d988e9
+    sig)
 
                • 
   
 
              • Linux / BSD / Solaris التثبيت عن طريق الواجهة الرسومية :
                
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                
     Download that file and double-click it (if that works) or
-    type java -jar i2pinstall_0.9.6.jar in a terminal to run the
+    type java -jar i2pinstall_0.9.9.jar in a terminal to run the
     installer.
     On some platforms you may be able to right-click and select
     "Open with Java".
   حمل الملف و نفّذه ،و اذا كان نظام التشغيل لديك غير ويندوز نفّذ الأمر التالي 
-     java -jar i2pinstall_0.9.6.jar
                • 
+     java -jar i2pinstall_0.9.9.jar
 
 
 
              • Linux / BSD / Solaris التثبيت عن طريق سطر الأوامر :
                
     حمل ملف التثبيت عن طريق الواجهة الرسومية المذكور مسبقاً ثمّ نفذ الأمر
-    java -jar i2pinstall_0.9.6.jar -console في سطر الأوامر لديك
+    java -jar i2pinstall_0.9.9.jar -console في سطر الأوامر لديك
     هذا ينطبق على أنظمة ويندوز و لينكس و ما كنتوش (نعم ،حقاً !) 
 
                • 
 
 
              • Packages for Debian & Ubuntu
                • 
 
 
              • OS X Graphical installer:
                
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                
     Download that file and double-click it (if that works) or
-    type java -jar i2pinstall_0.9.6.jar in a terminal to run the
+    type java -jar i2pinstall_0.9.9.jar in a terminal to run the
     installer.
     You may be able to right-click and select
     "Open with Java"
   حمل الملف و نفّذه ،و اذا كان نظام التشغيل لديك غير ويندوز نفّذ الأمر التالي 
-     java -jar i2pinstall_0.9.6.jar
                • .
+     java -jar i2pinstall_0.9.9.jar.
 
 
 
              • OS X التثبيت عن طريق سطر الأوامر :
                
     حمل ملف التثبيت عن طريق الواجهة الرسومية المذكور مسبقاً ثمّ نفذ الأمر
-    java -jar i2pinstall_0.9.6.jar -console في سطر الأوامر لديك
+    java -jar i2pinstall_0.9.9.jar -console في سطر الأوامر لديك
     هذا ينطبق على أنظمة ويندوز و لينكس و ما كنتوش (نعم ،حقاً !) 
 
                • 
 
 
              • تحميل النص المصدري :
                
-    i2psource_0.9.6.tar.bz2
+    i2psource_0.9.9.tar.bz2
     (SHA256
-fd2aa881d68b3164c43de9d91dcb04a93a36228d416582ada14ae40031436d18
-     sig)
                
+cbbf25dea50a717c3376eb7af226f0b2a653e0372db8782ef37aa8b3d275436c
+     sig)
                
     بشكل بديل ، يمكن الحصول على الرماز المصدري من monotone.
     
                
-    نفّذ الأمر(tar xjvf i2psource_0.9.6.tar.bz2 ; cd i2p-0.9.6 ; ant pkg)ثمّ شغل التثبيت عبر الواجهة الرسومية أو سطر الأوامر كما ذكر مسبقاً
                • 
+    نفّذ الأمر(tar xjvf i2psource_0.9.9.tar.bz2 ; cd i2p-0.9.9 ; ant pkg)ثمّ شغل التثبيت عبر الواجهة الرسومية أو سطر الأوامر كما ذكر مسبقاً
 
              
 
 الملفات موقّعة بواسطة zzz 
@@ -127,12 +129,12 @@ fd2aa881d68b3164c43de9d91dcb04a93a36228d416582ada14ae40031436d18
 
            • يمكنك استخدام الطريقة اليدوية المحددة ادناه
              • 
 
 
-
              (تحديث من اصدار سابق (الطريقة اليدوية:
              
+
              (تحديث من اصدار سابق (الطريقة اليدوية:
              
 
                
-
              1. تحميل i2pupdate_0.9.6.zip
+
              2. تحميل i2pupdate_0.9.9.zip
     (SHA256
-f322de7a9e3e89411d072d983a6577494981da488bb08f839c521ed340d77b92
-     sig الى مجلد التثبيت اعد التسمية الى i2pupdate.zip.
+533b0ce2d9e1bfc8762ba17eef3572ae7355ed8f21d5d3557b718a14b05794f2
+     sig الى مجلد التثبيت اعد التسمية الى i2pupdate.zip.
 او يمكنك تحميل النص المصدري و كتابة في سطر الأوامر ant updater
 ثم تقوم بنسخ الملف i2pupdate.zip الى مجلد الذي اخترته لتنصيب برنامج I2P لتتم الترقية بطريقة آلية.انت لست بحاجة الى فك ضغط هذا الملف.
  
                3. 
diff --git a/www.i2p2/pages/translations/download_cs.html b/www.i2p2/pages/translations/download_cs.html
index 52e16e69..79ddb901 100644
--- a/www.i2p2/pages/translations/download_cs.html
+++ b/www.i2p2/pages/translations/download_cs.html
@@ -3,61 +3,63 @@
 {% block content %}
 
                Stáhnout I2P
                      
 
                Požadavky pro instalaci
                
-Oracle Java 1.5 nebo novější (doporučená verze Oracle Java 6/7), nebo ekvivalentní JRE.
+Oracle Java 1.5 nebo novější (doporučená verze Oracle Java 7,
+except Raspberry Pi: Oracle 8 Early Access,
+PowerPC: IBM SDK 7), nebo ekvivalentní JRE.
 
                
 Svou aktuální nainstalovanou verzi Javy si můžete ověřit na této stránce
 nebo z příkazové řádky pomocí příkazu java -version
 
                Nová instalace
                
 
                  
 
                • Windows Grafický instalační program:
                  
-    i2pinstall_0.9.6_windows.exe
+    i2pinstall_0.9.9_windows.exe
     (SHA256
-bf7d11f0a36acff9cd51ad3ef89d66975b0b0de344ca72719a5576159ec965d1
-    sig) 
                  
+97dd4326ad8afdea0e78ffcb053b23793dfa79d89458be3fe3a1ed62a2d988e9
+    sig) 
                  
     Pod Windows: stáhněte soubor a spusťte ho.
 
                  • 
 
 
                • Linux / BSD / Solaris Grafický instalační program:
                  
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                  
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                  
     Download that file and double-click it (if that works) or
-    type java -jar i2pinstall_0.9.6.jar in a terminal to run the
+    type java -jar i2pinstall_0.9.9.jar in a terminal to run the
     installer.
     On some platforms you may be able to right-click and select
     "Open with Java".
                  • 
 
 
                • Linux / BSD / Solaris Instalace z příkazové řádky:
                  
-    Stáhněte si grafický instalační program (viz výše) a spusťte ho příkazem java -jar i2pinstall_0.9.6.jar -console
+    Stáhněte si grafický instalační program (viz výše) a spusťte ho příkazem java -jar i2pinstall_0.9.9.jar -console
 
                  • 
 
 
                • Packages for Debian & Ubuntu
                  • 
 
 
                • OS X Graphical installer:
                  
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                  
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                  
     Download that file and double-click it (if that works) or
-    type java -jar i2pinstall_0.9.6.jar in a terminal to run the
+    type java -jar i2pinstall_0.9.9.jar in a terminal to run the
     installer.
     You may be able to right-click and select
     "Open with Java".
 
                  • 
 
 
                • OS X Instalace z příkazové řádky:
                  
-    Stáhněte si grafický instalační program (viz výše) a spusťte ho příkazem java -jar i2pinstall_0.9.6.jar -console
+    Stáhněte si grafický instalační program (viz výše) a spusťte ho příkazem java -jar i2pinstall_0.9.9.jar -console
 
                  • 
 
 
                • Instalace ze zdrojového kódu:
                  
-    i2psource_0.9.6.tar.bz2
+    i2psource_0.9.9.tar.bz2
     (SHA256
-fd2aa881d68b3164c43de9d91dcb04a93a36228d416582ada14ae40031436d18
-     sig)
                  
+cbbf25dea50a717c3376eb7af226f0b2a653e0372db8782ef37aa8b3d275436c
+     sig)
                  
     Alternativně lze zdrojový kód stáhnout z repozitáře monotone
     git.repo.i2p Github.
                  
-    Spusťte sestavení programu příkazem (tar xjvf i2psource_0.9.6.tar.bz2 ; cd i2p-0.9.6 ; ant pkg) a potom 
+    Spusťte sestavení programu příkazem (tar xjvf i2psource_0.9.9.tar.bz2 ; cd i2p-0.9.9 ; ant pkg) a potom 
     spusťte grafický instalační program nebo instalaci z příkazové řádky (viz výše).
                  • 
 
                
 
@@ -114,12 +116,12 @@ nových verzí.
 
            
 
            
 
-
            Aktualizace z předchozích verzí (manuální postup):
            
+
            Aktualizace z předchozích verzí (manuální postup):
            
 
              
-
            1. Stáhněte si i2pupdate_0.9.6.zip
+
            2. Stáhněte si i2pupdate_0.9.9.zip
     (SHA256
-f322de7a9e3e89411d072d983a6577494981da488bb08f839c521ed340d77b92
-    sig) a uložte jej do 
+533b0ce2d9e1bfc8762ba17eef3572ae7355ed8f21d5d3557b718a14b05794f2
+    sig) a uložte jej do 
     instalační složky I2P. Přejmenujte tento soubor na i2pupdate.zip.
     (Alternativně si můžete stáhnout zdrojový kód jak je popsáno výše a spustit 
     "ant updater", výsledný soubor i2pupdate.zip pak nakopírovat do instalační složky
diff --git a/www.i2p2/pages/translations/download_de.html b/www.i2p2/pages/translations/download_de.html
index 40c57fb5..d6632e5a 100644
--- a/www.i2p2/pages/translations/download_de.html
+++ b/www.i2p2/pages/translations/download_de.html
@@ -4,47 +4,49 @@
 
              Download I2P
                    
 
              Abhängigkeiten
              
 Java Runtime 1.5 oder neuer.
-(Oracle Java Version 6/7,
-OpenJDK 6/7, oder
-IcedTea6/7
- recommended)
+(Oracle Java Version 7,
+OpenJDK 7, oder
+IcedTea7
+ recommended,
+except Raspberry Pi: Oracle 8 Early Access,
+PowerPC: IBM SDK 7)
 
              
 Bestimme hier deine Java Version
 oder gebe java -version in die Kommandozeile ein.
 
              Frische Installation
              
 
                
 
              • Windows GUI Installer:
                
-    i2pinstall_0.9.6_windows.exe
+    i2pinstall_0.9.9_windows.exe
     (SHA256
-bf7d11f0a36acff9cd51ad3ef89d66975b0b0de344ca72719a5576159ec965d1
-     sig)
                 
+97dd4326ad8afdea0e78ffcb053b23793dfa79d89458be3fe3a1ed62a2d988e9
+     sig)
                 
     Downloade die Datei und führe sie aus. 
                • 
 
 
              • Linux / BSD / Solaris GUI Installer:
                
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                
     Hole die Datei und führe sie mit Doppelklick aus (falls es funktioniert)
-    oder gebe java -jar i2pinstall_0.9.6.jar in einm Terminal ein um
+    oder gebe java -jar i2pinstall_0.9.9.jar in einm Terminal ein um
     die Installation zu starten.
     Auf einigen Plattformen muss die Datei gegebenfall mit Rechts-Klick und der 
     Option "Öffne mit Java" geöffnet werden.
                • 
 
 
              • Linux / BSD / Solaris Kommandozeilen (Headless) Installation:
                
     Downloade die normale Installationsdatei von oben und rufe
-    java -jar i2pinstall_0.9.6.jar -console in der Kommandozeile auf.
+    java -jar i2pinstall_0.9.9.jar -console in der Kommandozeile auf.
 
                • 
 
 
              • Pakete für Debian & Ubuntu
                • 
 
 
              • OS X Graphical installer:
                
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                
     Hole die Datei und führe sie mit Doppelklick aus (falls es funktioniert)
-    oder gebe java -jar i2pinstall_0.9.6.jar in einm Terminal ein um
+    oder gebe java -jar i2pinstall_0.9.9.jar in einm Terminal ein um
     die Installation zu starten.
     Auf einigen Plattformen muss die Datei gegebenfall mit Rechts-Klick und der 
     Option "Öffne mit Java" geöffnet werden.
@@ -52,18 +54,18 @@ bf7d11f0a36acff9cd51ad3ef89d66975b0b0de344ca72719a5576159ec965d1
 
 
              • OS X Kommandozeilen (Headless) Installation:
                
     Downloade die normale Installationsdatei von oben und rufe
-    java -jar i2pinstall_0.9.6.jar -console in der Kommandozeile auf.
+    java -jar i2pinstall_0.9.9.jar -console in der Kommandozeile auf.
 
                • 
 
 
              • Quelltext Installation:
                
-    i2psource_0.9.6.tar.bz2
+    i2psource_0.9.9.tar.bz2
     (SHA256
-fd2aa881d68b3164c43de9d91dcb04a93a36228d416582ada14ae40031436d18
-     sig)
                
+cbbf25dea50a717c3376eb7af226f0b2a653e0372db8782ef37aa8b3d275436c
+     sig)
                
     Alternativ kannst Du den Quelltext aus Monotone
     git.repo.i2p Github kopieren.
                
     
                
-    Führe folgendes aus: (tar xjvf i2psource_0.9.6.tar.bz2 ; cd i2p_0.9.6 ; ant pkg) 
+    Führe folgendes aus: (tar xjvf i2psource_0.9.9.tar.bz2 ; cd i2p_0.9.9 ; ant pkg) 
     und starte dann den GUI Installer oder die headless Installation wie oben beschrieben
                • 
 
              
 
@@ -123,12 +125,12 @@ werden kann.
 
            3. Alternativ kannst Du die manuelle Methode wie unten beschrieben nutzen.
              4. 
 
            
 
-
            Aktualisieren von älteren Versionen (Manuelle Methode):
            
+
            Aktualisieren von älteren Versionen (Manuelle Methode):
            
 
              
-
            1. Downloade i2pupdate_0.9.6.zip
+
            2. Downloade i2pupdate_0.9.9.zip
     (SHA256
-f322de7a9e3e89411d072d983a6577494981da488bb08f839c521ed340d77b92
-     sig) in dein I2P 
+533b0ce2d9e1bfc8762ba17eef3572ae7355ed8f21d5d3557b718a14b05794f2
+     sig) in dein I2P 
     Installationsverzeichnis und bennene es i2pupdate.zip.
     (alternativ kannst den Quelltest besorgen und "ant updater" laufen lassen, kopiere dann
     das erstellte i2pupdate.zip in dein I2P Installationsverzeichnis). Du brauchst
diff --git a/www.i2p2/pages/translations/download_el.html b/www.i2p2/pages/translations/download_el.html
index 0fd1fb54..79bbc5c2 100644
--- a/www.i2p2/pages/translations/download_el.html
+++ b/www.i2p2/pages/translations/download_el.html
@@ -4,48 +4,50 @@
 
              Ληψη I2P
              
 
              Εξάρτηση
              
 Java Runtime 1.5 ή νεότερο.
-(Oracle Java Version 6/7,
-OpenJDK 6/7, ή
-IcedTea6/7
- συνιστάται)
+(Oracle Java Version 7,
+OpenJDK 7, ή
+IcedTea7
+ συνιστάται,
+except Raspberry Pi: Oracle 8 Early Access,
+PowerPC: IBM SDK 7)
 
              
 Βρείτε την έκδοση Java που έχετε εδώ
 ή πληκτρολογήστε java -version στη γραμμή εντολών.
 
              Εγκατάσταση
              
 
                
 
              • Εγκατάσταση με γραφικό περιβάλλον για Windows:
                
-    i2pinstall_0.9.6_windows.exe
+    i2pinstall_0.9.9_windows.exe
     (SHA256
-bf7d11f0a36acff9cd51ad3ef89d66975b0b0de344ca72719a5576159ec965d1
-    sig)
                
+97dd4326ad8afdea0e78ffcb053b23793dfa79d89458be3fe3a1ed62a2d988e9
+    sig)
                
     Κατεβάστε αυτό το αρχείο και εκτελέστε το.
 
                • 
 
 
              • Εγκατάσταση με γραφικό περιβάλλον για Linux / BSD / Solaris:
                
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                
     Κατεβάστε αυτό το αρχείο και κάντε διπλό "κλικ" (εάν δουλεύει) ή
-    πληκτρολογήστε java -jar i2pinstall_0.9.6.jar στη γραμμή εντολών
+    πληκτρολογήστε java -jar i2pinstall_0.9.9.jar στη γραμμή εντολών
     για να τρέξετε την εγκατάσταση.
     Σε μερικές πλατφόρμες μπορείτε να κάνετε δεξιό "κλικ" και να επιλέξετε
     "Open with Java".
                • 
 
 
              • Εγκατάσταση από γραμμή εντολών (headless) για Linux / BSD / Solaris:
                
     Κατεβάστε την εγκατάσταση με γραφικό περιβάλλον από παραπάνω και εκτελέστε
-    java -jar i2pinstall_0.9.6.jar -console στη γραμμή εντολών.
+    java -jar i2pinstall_0.9.9.jar -console στη γραμμή εντολών.
 
                • 
 
 
              • Πακέτα για Debian & Ubuntu
                • 
 
 
              • OS X Graphical installer:
                
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                
     Κατεβάστε αυτό το αρχείο και κάντε διπλό "κλικ" (εάν δουλεύει) ή
-    πληκτρολογήστε java -jar i2pinstall_0.9.6.jar στη γραμμή εντολών
+    πληκτρολογήστε java -jar i2pinstall_0.9.9.jar στη γραμμή εντολών
     για να τρέξετε την εγκατάσταση.
     Σε μερικές πλατφόρμες μπορείτε να κάνετε δεξιό "κλικ" και να επιλέξετε
     "Open with Java".
@@ -53,18 +55,18 @@ bf7d11f0a36acff9cd51ad3ef89d66975b0b0de344ca72719a5576159ec965d1
 
 
              • Εγκατάσταση από γραμμή εντολών (headless) για OS X:
                
     Κατεβάστε την εγκατάσταση με γραφικό περιβάλλον από παραπάνω και εκτελέστε
-    java -jar i2pinstall_0.9.6.jar -console στη γραμμή εντολών.
+    java -jar i2pinstall_0.9.9.jar -console στη γραμμή εντολών.
 
                • 
 
 
              • Εγκατάσταση από πηγαίο κώδικα:
                
-    i2psource_0.9.6.tar.bz2
+    i2psource_0.9.9.tar.bz2
     (SHA256
-fd2aa881d68b3164c43de9d91dcb04a93a36228d416582ada14ae40031436d18
-     sig)
                
+cbbf25dea50a717c3376eb7af226f0b2a653e0372db8782ef37aa8b3d275436c
+     sig)
                
     Εναλλακτικά, μπορείτε να πάρετε τον πηγαίο κώδικα από το monotone
     git.repo.i2p Github.
     
                
-    Εκτελέστε (tar xjvf i2psource_0.9.6.tar.bz2 ; cd i2p-0.9.6 ; ant pkg) και μετά
+    Εκτελέστε (tar xjvf i2psource_0.9.9.tar.bz2 ; cd i2p-0.9.9 ; ant pkg) και μετά
     είτε τρέξτε την εγκατάσταση με γραφικό περιβάλλον είτε από τη γραμμή εντολών όπως παραπάνω.
     
                • 
 
              
@@ -150,12 +152,12 @@ than current version", και θα πρέπει να χρησιμοποιήσο
 
            3. Εναλλακτικά, μπορείτε να χρησιμοποιήσετε την χειροκίνητη μέθοδο που περιγράφεται παρακάτω.
              4. 
 
            
 
-
            Ενημερώσεις από προηγούμενες εκδόσεις (χειροκίνητη μέθοδος):
            
+
            Ενημερώσεις από προηγούμενες εκδόσεις (χειροκίνητη μέθοδος):
            
 
              
-
            1. Κατεβάστε το i2pupdate_0.9.6.zip
+
            2. Κατεβάστε το i2pupdate_0.9.9.zip
     (SHA256
-f322de7a9e3e89411d072d983a6577494981da488bb08f839c521ed340d77b92
-     sig)
+533b0ce2d9e1bfc8762ba17eef3572ae7355ed8f21d5d3557b718a14b05794f2
+     sig)
     στον κατάλογο εγκατάστασης του I2P και μετονομάστε το σε i2pupdate.zip.
     (εναλλακτικά, μπορείτε να πάρετε τον πηγαίο κώδικα και να εκτελέσετε "ant updater", έπειτα
     αντιγράψτε το παραγόμενο i2pupdate.zip στον κατάλογο εγκατάστασης του I2P). ΔΕΝ χρειάζεται να
diff --git a/www.i2p2/pages/translations/download_es.html b/www.i2p2/pages/translations/download_es.html
index 14981861..bf5d3bc2 100644
--- a/www.i2p2/pages/translations/download_es.html
+++ b/www.i2p2/pages/translations/download_es.html
@@ -4,47 +4,49 @@
 
              Descargar I2P
                    
 
              Dependencias
              
 Java Runtime 1.5 o superior.
-(Oracle Java Versión 6/7,
-OpenJDK 6/7, o
-IcedTea6/7
- recomendado)
+(Oracle Java Versión 7,
+OpenJDK 7, o
+IcedTea7
+ recomendado,
+except Raspberry Pi: Oracle 8 Early Access,
+PowerPC: IBM SDK 7)
 
              
 Determina aquí tu versión instalada de Java
 o teclea java -version en tu línea de comandos.
 
              Instalaciones limpias
              
 
                
 
              • Windows Instalador gráfico:
                
-    i2pinstall_0.9.6_windows.exe
+    i2pinstall_0.9.9_windows.exe
     (SHA256
-bf7d11f0a36acff9cd51ad3ef89d66975b0b0de344ca72719a5576159ec965d1
-    sig)
+97dd4326ad8afdea0e78ffcb053b23793dfa79d89458be3fe3a1ed62a2d988e9
+    sig)
 
                • 
 
 
              • Linux / BSD / Solaris Instalador gráfico:
                
-  i2pinstall_0.9.6.jar
+  i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                
     Download that file and double-click it (if that works) or
-    type java -jar i2pinstall_0.9.6.jar in a terminal to run the
+    type java -jar i2pinstall_0.9.9.jar in a terminal to run the
     installer.
     On some platforms you may be able to right-click and select
     "Open with Java".
                • 
 
 
              • Linux / BSD / Solaris Instalación desde la línea de comandos (headless):
                
     Descarga el archivo del instalador gráfico  y
-    arranca java -jar i2pinstall_0.9.6.jar -console desde la línea de comandos.
+    arranca java -jar i2pinstall_0.9.9.jar -console desde la línea de comandos.
 
                • 
 
 
              • Packages for Debian & Ubuntu
                • 
 
 
              • OS X Graphical installer:
                
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                
     Download that file and double-click it (if that works) or
-    type java -jar i2pinstall_0.9.6.jar in a terminal to run the
+    type java -jar i2pinstall_0.9.9.jar in a terminal to run the
     installer.
     You may be able to right-click and select
     "Open with Java".
@@ -52,18 +54,18 @@ bf7d11f0a36acff9cd51ad3ef89d66975b0b0de344ca72719a5576159ec965d1
 
 
              • OS X Instalación desde la línea de comandos (headless):
                
     Descarga el archivo del instalador gráfico  y
-    arranca java -jar i2pinstall_0.9.6.jar -console desde la línea de comandos.
+    arranca java -jar i2pinstall_0.9.9.jar -console desde la línea de comandos.
 
                • 
 
 
              • Instalación desde el código fuente:
                
-    i2psource_0.9.6.tar.bz2
+    i2psource_0.9.9.tar.bz2
     (SHA256
-fd2aa881d68b3164c43de9d91dcb04a93a36228d416582ada14ae40031436d18
-     sig)
                
+cbbf25dea50a717c3376eb7af226f0b2a653e0372db8782ef37aa8b3d275436c
+     sig)
                
     De forma alternativa, puedes obtener las fuentes usando monotone
     git.repo.i2p Github.
     
                
-    Ejecuta tar xjvf i2psource_0.9.6.tar.bz2 ; cd i2p-0.9.6 ; ant pkg ; después puedes arrancar el instalador gráfico o bien hacer la instalación desde la línea de comandos descritas anteriormente.
                • 
+    Ejecuta tar xjvf i2psource_0.9.9.tar.bz2 ; cd i2p-0.9.9 ; ant pkg ; después puedes arrancar el instalador gráfico o bien hacer la instalación desde la línea de comandos descritas anteriormente.
 
              
 
 Los archivos están firmados por zzz,
@@ -123,12 +125,12 @@ la actualización automáticamente.
 
            3. De forma alternativa, puedes usar el método manual como se especifica seguidamente.
              4. 
 
            
 
-
            Actualizar desde versiones anteriores (método manual):
            
+
            Actualizar desde versiones anteriores (método manual):
            
 
              
-
            1. Descarga i2pupdate_0.9.6.zip
+
            2. Descarga i2pupdate_0.9.9.zip
     (SHA256
-f322de7a9e3e89411d072d983a6577494981da488bb08f839c521ed340d77b92
-     sig) 
+533b0ce2d9e1bfc8762ba17eef3572ae7355ed8f21d5d3557b718a14b05794f2
+     sig) 
 a tu directorio de instalación I2P y renómbralo como i2pupdate.zip.
 	(Como alternativa, puedes obtener el código fuente tal y como se explicó anteriormente y ejecutar "ant updater", después copia el i2pupdate.zip resultante en tu directorio de instalación I2P). NO es necesario descomprimir ese archivo.
              3. 
 
            3. Click "Restart"
              4. 
diff --git a/www.i2p2/pages/translations/download_fr.html b/www.i2p2/pages/translations/download_fr.html
index 812104c4..61c3dd60 100644
--- a/www.i2p2/pages/translations/download_fr.html
+++ b/www.i2p2/pages/translations/download_fr.html
@@ -5,62 +5,64 @@ Traduction de juillet 2011. Version anglaise actuelleTélécharger I2P 
 
              Prérequis
              
 Java Runtime 1.5 ou plus récent.
-(Oracle Java Version 6/7,
-OpenJDK 6/7, ou
-IcedTea6/7
- recommandé)
+(Oracle Java Version 7,
+OpenJDK 7, ou
+IcedTea7
+ recommandé,
+except Raspberry Pi: Oracle 8 Early Access,
+PowerPC: IBM SDK 7)
 
              
 Déterminez la version de Java installée
 ou tapez java -version à l'invite de commande.
 
              Installation initiale
              
 
                
 
              • Windows Installeur graphique:
                
-    i2pinstall_0.9.6_windows.exe
-    (SHA256 bf7d11f0a36acff9cd51ad3ef89d66975b0b0de344ca72719a5576159ec965d1
-    sig)
                 
+    i2pinstall_0.9.9_windows.exe
+    (SHA256 97dd4326ad8afdea0e78ffcb053b23793dfa79d89458be3fe3a1ed62a2d988e9
+    sig)
                 
     Téléchargez ce fichier et exécutez-le.  
 
                • 
 
 
              • Linux / BSD / Solaris Installeur graphique:
                
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256 
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                 
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                 
     Téléchargez ce fichier et exécutez-le.  
     Vous pouvez 
-    taper java -jar i2pinstall_0.9.6.jar
+    taper java -jar i2pinstall_0.9.9.jar
 
                • 
 
 
              • Linux / BSD / Solaris  Installation en ligne de commande (facile):
                
     Téléchargez le fichier de l'installeur graphique ci-dessus et
-    exécutez java -jar i2pinstall_0.9.6.jar -console sur la ligne de commande.
+    exécutez java -jar i2pinstall_0.9.9.jar -console sur la ligne de commande.
 
                • 
 
 
              • Packages for Debian & Ubuntu
                • 
 
 
              • OS X Graphical installer:
                
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                
     Téléchargez ce fichier et exécutez-le.  
     Vous pouvez 
-    taper java -jar i2pinstall_0.9.6.jar
+    taper java -jar i2pinstall_0.9.9.jar
 
                • 
 
 
              • OS X Installation en ligne de commande (facile):
                
     Téléchargez le fichier de l'installeur graphique ci-dessus et
-    exécutez java -jar i2pinstall_0.9.6.jar -console sur la ligne de commande.
+    exécutez java -jar i2pinstall_0.9.9.jar -console sur la ligne de commande.
 
                • 
 
 
              • À partir des sources:
                
-    i2psource_0.9.6.tar.bz2
-    (SHA256 fd2aa881d68b3164c43de9d91dcb04a93a36228d416582ada14ae40031436d18
-     sig)
                
+    i2psource_0.9.9.tar.bz2
+    (SHA256 cbbf25dea50a717c3376eb7af226f0b2a653e0372db8782ef37aa8b3d275436c
+     sig)
                
     Vous pouvez si vous préférez récupérer les sources sur  monotone
     git.repo.i2p Github.
     
                
-    Exécuter (tar xjvf i2psource_0.9.6.tar.bz2 ; cd i2p-0.9.6 ; ant pkg) puis, soit
+    Exécuter (tar xjvf i2psource_0.9.9.tar.bz2 ; cd i2p-0.9.9 ; ant pkg) puis, soit
     lancer l'installeur graphique, soit passer par la ligne de commande.
                • 
 
              
 
@@ -134,11 +136,11 @@ cliquant dessus
 
            4. Vous pouvez également utiliser la méthode manuelle décrite ci-dessous.
              5. 
 
            
 
-
            Mises à jour de versions plus anciennes (méthode manuelle):
            
+
            Mises à jour de versions plus anciennes (méthode manuelle):
            
 
              
-
            1. Téléchargez i2pupdate_0.9.6.zip
-    (SHA256 f322de7a9e3e89411d072d983a6577494981da488bb08f839c521ed340d77b92
-     sig) dans votre répertoire d'installation d'I2P 
+
            2. Téléchargez i2pupdate_0.9.9.zip
+    (SHA256 533b0ce2d9e1bfc8762ba17eef3572ae7355ed8f21d5d3557b718a14b05794f2
+     sig) dans votre répertoire d'installation d'I2P 
     et renommez-le i2pupdate.zip.
     (sinon, prenez les sources - voir plus haut - et lancez "ant updater", puis copiez/déplacez le i2pupdate.zip généré 
  vers votre répertoire d'installation d'I2P). Il n'est pas nécessaire de décompresser ce fichier.
              3. 
diff --git a/www.i2p2/pages/translations/download_ru.html b/www.i2p2/pages/translations/download_ru.html
index 15dcba2e..7f2ae08c 100644
--- a/www.i2p2/pages/translations/download_ru.html
+++ b/www.i2p2/pages/translations/download_ru.html
@@ -6,7 +6,9 @@
 
 
              Требования для установки
              
 
-Oracle Java 1.5 или новее (рекомендуется Oracle Java 6/7), либо иная совместимая JRE.
+Oracle Java 1.5 или новее (рекомендуется Oracle Java 7,
+except Raspberry Pi: Oracle 8 Early Access,
+PowerPC: IBM SDK 7), либо иная совместимая JRE.
 
              
 Узнать, какая версия Java установлена на Вашем компьютере можно на этой странице, либо набрав в командной строке java -version
 
@@ -15,57 +17,57 @@
 
                
 
 
              • Графический инсталлятор для Windows:
                
-    i2pinstall_0.9.6_windows.exe
+    i2pinstall_0.9.9_windows.exe
     (SHA256 
-bf7d11f0a36acff9cd51ad3ef89d66975b0b0de344ca72719a5576159ec965d1
-    sig)
                  
+97dd4326ad8afdea0e78ffcb053b23793dfa79d89458be3fe3a1ed62a2d988e9
+    sig)
                  
     Под Windows: скачайте этот файл и запустите его. 
 
                • 
 
 
              • Графический инсталлятор для Linux / BSD / Solaris:
                
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                
     Скачайте этот файл и запустите двойным кликом, или выполните в консоли
-    команду java -jar i2pinstall_0.9.6.jar для запуска инсталлятора.
+    команду java -jar i2pinstall_0.9.9.jar для запуска инсталлятора.
     На некоторых платформах вы можете вызвать контекстное меню и выбрать
     "Open with Java".
 
                •  
 
 
              • Установка из командной строки в Linux / BSD / Solaris:
                 
 
-Скачайте графический инсталлятор по ссылке выше и запустите из командной строки java -jar i2pinstall_0.9.6.jar -console 
                 
+Скачайте графический инсталлятор по ссылке выше и запустите из командной строки java -jar i2pinstall_0.9.9.jar -console 
                 
 
                • 
 
 
              • Packages for Debian & Ubuntu
                • 
 
 
              • OS X Graphical installer:
                
-    i2pinstall_0.9.6.jar
+    i2pinstall_0.9.9.jar
     (SHA256
-2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371
-    sig)
                
+5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f
+    sig)
                
     Скачайте этот файл и запустите двойным кликом, или выполните в консоли
-    команду java -jar i2pinstall_0.9.6.jar для запуска инсталлятора.
+    команду java -jar i2pinstall_0.9.9.jar для запуска инсталлятора.
     На некоторых платформах вы можете вызвать контекстное меню и выбрать
     "Open with Java".
 
                • 
 
 
              • Установка из командной строки в OS X:
                 
 
-Скачайте графический инсталлятор по ссылке выше и запустите из командной строки java -jar i2pinstall_0.9.6.jar -console 
                 
+Скачайте графический инсталлятор по ссылке выше и запустите из командной строки java -jar i2pinstall_0.9.9.jar -console 
                 
 
                • 
 
 
              • Установка из исходного кода:
                
-    i2psource_0.9.6.tar.bz2
+    i2psource_0.9.9.tar.bz2
     (SHA256 
-fd2aa881d68b3164c43de9d91dcb04a93a36228d416582ada14ae40031436d18
-    sig)
                
+cbbf25dea50a717c3376eb7af226f0b2a653e0372db8782ef37aa8b3d275436c
+    sig)
                
     
     (Как вариант, можете скачать текущий исходный код из monotone-репозитория
      git.repo.i2p Github.)
     
                
-    Запустите процесс сборки (tar xjvf i2psource_0.9.6.tar.bz2 ; cd i2p-0.9.6 ; ant pkg), затем воспользуйтесь собранным инсталлятором в графическом или консольном режиме (см. предыдущие способы установки). 
+    Запустите процесс сборки (tar xjvf i2psource_0.9.9.tar.bz2 ; cd i2p-0.9.9 ; ant pkg), затем воспользуйтесь собранным инсталлятором в графическом или консольном режиме (см. предыдущие способы установки). 
 
                • 
 
              
 
@@ -112,14 +114,14 @@ Unix-совместимые системы: I2P можно запустить в

          -

          Обновление ранее установленных версий (вручную):

          +

          Обновление ранее установленных версий (вручную):

          1. Скачайте - i2pupdate_0.9.6.zip + i2pupdate_0.9.9.zip (SHA256 -f322de7a9e3e89411d072d983a6577494981da488bb08f839c521ed340d77b92 - sig) +533b0ce2d9e1bfc8762ba17eef3572ae7355ed8f21d5d3557b718a14b05794f2 + sig) в директорию, где у Вас установлен I2P и переименуйте в i2pupdate.zip. (Как вариант, можно скачать исходный код и запустить сборку командой «ant updater», после чего скопировать полученный i2pupdate.zip в директорию, где у Вас установлен I2P.) Вам НЕ надо распаковывать этот zip-файл.
          2. Нажмите «Перезагрузить плавно»
            3. diff --git a/www.i2p2/pages/translations/download_zh.html b/www.i2p2/pages/translations/download_zh.html index d0e05eb2..8b063b85 100644 --- a/www.i2p2/pages/translations/download_zh.html +++ b/www.i2p2/pages/translations/download_zh.html @@ -4,60 +4,62 @@

            下载 I2P

            依赖关系

            Oracle Java 1.5 或更高版本，或等效的 JRE。 -(推荐使用 Oracle Java 6/7) +(推荐使用 Oracle Java 7, +except Raspberry Pi: Oracle 8 Early Access, +PowerPC: IBM SDK 7)
            确定您安装的 Java 版本可以点这里 或在命令行中输入 java -version 。

            全新安装

            • Windows 图形安装程序:
              - i2pinstall_0.9.6_windows.exe + i2pinstall_0.9.9_windows.exe
              (SHA256 -bf7d11f0a36acff9cd51ad3ef89d66975b0b0de344ca72719a5576159ec965d1 - sig) +97dd4326ad8afdea0e78ffcb053b23793dfa79d89458be3fe3a1ed62a2d988e9 + sig)
            • Linux / BSD / Solaris 图形安装程序:
              - i2pinstall_0.9.6.jar + i2pinstall_0.9.9.jar (SHA256 -2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371 - sig)
              +5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f + sig)
              Download that file and double-click it (if that works) or - type java -jar i2pinstall_0.9.6.jar in a terminal to run the + type java -jar i2pinstall_0.9.9.jar in a terminal to run the installer. On some platforms you may be able to right-click and select "Open with Java". -
              下载以上文件并运行如果你不是 windows 用户，可以输入 java -jar i2pinstall_0.9.6.jar +
              下载以上文件并运行如果你不是 windows 用户，可以输入 java -jar i2pinstall_0.9.9.jar
            • Linux / BSD / Solaris 命令行安装(即无头安装):
              - 下载上面的图形安装程序并在命令行状态下运行 java -jar i2pinstall_0.9.6.jar -console。 + 下载上面的图形安装程序并在命令行状态下运行 java -jar i2pinstall_0.9.9.jar -console。
            • Packages for Debian & Ubuntu
            • OS X Graphical installer:
              - i2pinstall_0.9.6.jar + i2pinstall_0.9.9.jar (SHA256 -2dd5b67920723dd94202a408de31671b1e9543fcd5611bbe79385cc14f93b371 - sig)
              +5028910d3fb9747a6724e39f8eccb6d9ebe0530ef017102c372871badfbf6d9f + sig)
              Download that file and double-click it (if that works) or - type java -jar i2pinstall_0.9.6.jar in a terminal to run the + type java -jar i2pinstall_0.9.9.jar in a terminal to run the installer. On some platforms you may be able to right-click and select "Open with Java". -
              下载以上文件并运行如果你不是 windows 用户，可以输入 java -jar i2pinstall_0.9.6.jar +
              下载以上文件并运行如果你不是 windows 用户，可以输入 java -jar i2pinstall_0.9.9.jar
            • OS X 命令行安装(即无头安装):
              - 下载上面的图形安装程序并在命令行状态下运行 java -jar i2pinstall_0.9.6.jar -console。 + 下载上面的图形安装程序并在命令行状态下运行 java -jar i2pinstall_0.9.9.jar -console。
            • 用源码安装:
              - i2psource_0.9.6.tar.bz2 + i2psource_0.9.9.tar.bz2
              (SHA256 -fd2aa881d68b3164c43de9d91dcb04a93a36228d416582ada14ae40031436d18 - sig)
              此外，你也可以从 monotone 中下载源码。
              执行 (tar xjvf i2psource_0.9.6.tar.bz2 ; cd i2p_0.9.6 ; ant pkg) +cbbf25dea50a717c3376eb7af226f0b2a653e0372db8782ef37aa8b3d275436c + sig)
              此外，你也可以从 monotone 中下载源码。
              执行 (tar xjvf i2psource_0.9.9.tar.bz2 ; cd i2p_0.9.9 ; ant pkg) ，然后运行图形安装程序或进行命令行安装。
            @@ -85,11 +87,11 @@ fd2aa881d68b3164c43de9d91dcb04a93a36228d416582ada14ae40031436d18
          3. 此外，你可以通过下面的方法手动更新。
          -

          旧版升级 (手动方法)：

          +

          旧版升级 (手动方法)：

            -
          1. 下载 i2pupdate_0.9.6.zip
            (SHA256 -f322de7a9e3e89411d072d983a6577494981da488bb08f839c521ed340d77b92 - sig) 放入 I2P 安装文件夹并 改名为 i2pupdate.zip. (此外，您还可以在得到前述的源码包后运行 "ant updater"，将生成的 i2pupdate.zip 复制到您的 I2P 安装目录中)。不要将此文件解压缩。
            2. +
          2. 下载 i2pupdate_0.9.9.zip
            (SHA256 +533b0ce2d9e1bfc8762ba17eef3572ae7355ed8f21d5d3557b718a14b05794f2 + sig) 放入 I2P 安装文件夹并 改名为 i2pupdate.zip. (此外，您还可以在得到前述的源码包后运行 "ant updater"，将生成的 i2pupdate.zip 复制到您的 I2P 安装目录中)。不要将此文件解压缩。
          3. 点击 "Restart"(平滑重启)
          4. 去喝杯咖啡，11分钟后就完成了。
          diff --git a/www.i2p2/pages/translations/faq_ar.html b/www.i2p2/pages/translations/faq_ar.html index 59f1e9d3..dd26905c 100644 --- a/www.i2p2/pages/translations/faq_ar.html +++ b/www.i2p2/pages/translations/faq_ar.html @@ -43,7 +43,7 @@

          هناك عدة مواقع اختر أحدها.

            -
          • trac.i2p2.de ticket (طريقة مفضلة) +
          • trac.i2p2.de ticket (طريقة مفضلة)
          • pastethis.i2p ثم انضم على القناة IRC #i2p
          • تكلم مع المطورين IRC #i2p-dev
          diff --git a/www.i2p2/pages/translations/faq_de.html b/www.i2p2/pages/translations/faq_de.html index d359224a..f8dcfaac 100644 --- a/www.i2p2/pages/translations/faq_de.html +++ b/www.i2p2/pages/translations/faq_de.html @@ -8,7 +8,7 @@ Hier sind ein paar Stellen, wähle einen oder mehrere diff --git a/www.i2p2/pages/translations/faq_el.html b/www.i2p2/pages/translations/faq_el.html index cb8e45bc..dae167ca 100644 --- a/www.i2p2/pages/translations/faq_el.html +++ b/www.i2p2/pages/translations/faq_el.html @@ -52,7 +52,7 @@ (link)

          Ενώ έχει αναφερθεί ότι το I2P τρέχει σε PCs τόσο πενιχρά όσο ένας low-end Pentium II με 64 MB RAM, θα έχετε μία πολύ καλύτερη εμπειρία σε ένα Pentium III (ή καλύτερο) με 128 MB -RAM (ή περισσότερο). Ένας πίνακας που συγκρίνει την απόδοση διάφορων JREs βρίσκεται στο http://trac.i2p2.de/wiki/java, αλλά εν συντομία: όλα είναι δυνατά, χρησιμοποιήστε Sun/Oracle Java ή OpenJDK. +RAM (ή περισσότερο). Ένας πίνακας που συγκρίνει την απόδοση διάφορων JREs βρίσκεται στο https://trac.i2p2.de/wiki/java, αλλά εν συντομία: όλα είναι δυνατά, χρησιμοποιήστε Sun/Oracle Java ή OpenJDK.

          @@ -66,7 +66,7 @@ Android. Δηλώστε το bug σε ένα ή παραπάνω από τα παρακάτω μέρη.

            -
          • trac.i2p2.de ticket (προτιμώμενη μέθοδος)
            • +
          • trac.i2p2.de ticket (προτιμώμενη μέθοδος)
          • pastethis.i2p και επικοινωνήστε μαζί μας στο IRC στο κανάλι #i2p
          • Συζητήστε με τους developers στο IRC στο κανάλι #i2p-dev
          diff --git a/www.i2p2/pages/translations/faq_fr.html b/www.i2p2/pages/translations/faq_fr.html index e4881f60..a4cdbfad 100644 --- a/www.i2p2/pages/translations/faq_fr.html +++ b/www.i2p2/pages/translations/faq_fr.html @@ -48,8 +48,8 @@ Traduction de juillet 2011. Version anglaise actuelle (lien)

          Bien qu'I2P ait réussi à fonctionner sur des PCs aussi anciens que des Pentium II avec 64 Mo de RAM, vous en tirerez plus à partir de Pentium III avec 128Mo de RAM. Un -tableau de performances comparées des divers JREs se trouve sur -http://trac.i2p2.de/wiki/java, mais en bref, utilisez Jave de Sun/Oracle ou +tableau de performances comparées des divers JREs se trouve sur +https://trac.i2p2.de/wiki/java, mais en bref, utilisez Jave de Sun/Oracle ou OpenJDK.

          I2P a été testé sur Windows, Linux, FreeBSD (voir la note plus bas), OSX, et OpenSolaris. Un travail de portage sur Android est en cours.

          @@ -242,7 +242,7 @@ puisse se connecter au Wrapper. Une fois établie cette connexion, le Wrapper re

          Voici les endroits où vous pouvez le faire, utilisez en un ou plus :

            -
          • Postez un ticket sur trac.i2p2.de (méthode préférentielle) +
          • Postez un ticket sur trac.i2p2.de (méthode préférentielle)
          • Sur pastethis.i2p et suivez le canal IRC #i2p
          • Discutez avec les développeurs d'I2P sur IRC #i2p-dev
          diff --git a/www.i2p2/pages/translations/faq_zh.html b/www.i2p2/pages/translations/faq_zh.html index 4154fbc6..7109d6ce 100644 --- a/www.i2p2/pages/translations/faq_zh.html +++ b/www.i2p2/pages/translations/faq_zh.html @@ -42,7 +42,7 @@

          我想我发现了软件的一个错误，到哪报告？(链接)

          以下这些地方都可以，您可以任选其一。

          diff --git a/www.i2p2/pages/translations/getinvolved_ar.html b/www.i2p2/pages/translations/getinvolved_ar.html index cbde2a4c..667d223f 100644 --- a/www.i2p2/pages/translations/getinvolved_ar.html +++ b/www.i2p2/pages/translations/getinvolved_ar.html @@ -14,7 +14,7 @@ أخبر أصدقائك.
        • تجريب - جرب آخر اصدار من monotone - او #i2p ثم عبر عن المشاكل فيTrac. + او #i2p ثم عبر عن المشاكل فيTrac.
        • وثائق ساعد في تكميل الاجزاء الناقصة او الغير كاملة. ترجم الصفحات الى لغات أخرى. @@ -29,7 +29,7 @@ applications page.
        • برمجة هناك العديد من الاشياء التي يمكنك القيام بها اذا كنت تجيد لغة برمجة جافا او مستعد للتعلم. -انظر هنا Trac +انظر هنا Trac وفي قائمة الاعمال zzz.i2p للحصول على بعض الافكار. أنظر دليل المطورين الجدد . diff --git a/www.i2p2/pages/translations/getinvolved_de.html b/www.i2p2/pages/translations/getinvolved_de.html index 5738694f..6fc950d4 100644 --- a/www.i2p2/pages/translations/getinvolved_de.html +++ b/www.i2p2/pages/translations/getinvolved_de.html @@ -14,7 +14,7 @@ dich einzubringen! Hier ist eine Liste die dir beim Start hilft:

          • Testen — Benutze die letzten Versionen aus dem Monotone Archive -und berichte Ergebnisse in #i2p oder Fehler und Bugs auf Trac.
            • +und berichte Ergebnisse in #i2p oder Fehler und Bugs auf Trac.
          • Dokumentation — Hilf mit beim aktualisieren und erstellen der fehlenden Dokumente auf der Webseite, übersetze die Webseite in andere Sprachen!
            • @@ -31,7 +31,7 @@ Schreibe oder portiere eine Anwendung für I2P! Es gibt ein paar Richtlienen und eine Liste von Ideen auf der Anwendungsseite.
          • Coding — Es gibt viel zu tun falls Du Java kannst oder bereit bist, Java zu lernen. -Kontrolliere Trac nach offenen Tickets oder +Kontrolliere Trac nach offenen Tickets oder die TODO Liste auf zzz.i2p für einige Ideen zum Start. Schaue zur Anleitung für neue Entwickler Seite für Details.
          • Analysen — diff --git a/www.i2p2/pages/translations/getinvolved_el.html b/www.i2p2/pages/translations/getinvolved_el.html index e94bc6a9..9ad2fc6b 100644 --- a/www.i2p2/pages/translations/getinvolved_el.html +++ b/www.i2p2/pages/translations/getinvolved_el.html @@ -24,7 +24,7 @@ Πείτε το στους φίλους σας.
          • Testing — Τρέξτε τις τελευταίες εκδόσεις από το monotone -και αναφέρετε τα αποτελέσματα στο #i2p ή σαν bugs στο Trac. +και αναφέρετε τα αποτελέσματα στο #i2p ή σαν bugs στο Trac.
          • Τεκμηρίωση — Βοηθήστε να φτιάξουμε τα μέρη της ιστοσελίδας που είναι παλιά ή ατελή. Μεταφράστε τις σελίδες σε άλλες γλώσσες. @@ -41,7 +41,7 @@ ιδέες στη σελίδα για τις εφαρμογές.
          • Coding — Υπάρχουν αρκετά πράγματα που πρέπει να κάνετε εάν γνωρίζετε Java ή είστε -έτοιμοι να μάθετε. Ελέγξτε για ανοιχτά tickets στο Trac +έτοιμοι να μάθετε. Ελέγξτε για ανοιχτά tickets στο Trac ή την TODO λίστα στο zzz.i2p για μερικές ιδέες για να ξεκινήσετε. Δείτε τον οδηγό για νέους developers για λεπτομέρειες.
          • Μετάφραση — diff --git a/www.i2p2/pages/translations/getinvolved_fr.html b/www.i2p2/pages/translations/getinvolved_fr.html index 86775f6f..2b3dee19 100644 --- a/www.i2p2/pages/translations/getinvolved_fr.html +++ b/www.i2p2/pages/translations/getinvolved_fr.html @@ -17,7 +17,7 @@ Corrigez ou améliorez l'article I2P Parlez-en à vos amis.
          • Du test — Essayez les dernières version à partir de monotone et donnez vos résultats ou remarques sur -#i2p ou en tant que bogues sur Trac. +#i2p ou en tant que bogues sur Trac.
          • Documentation — Aidez-nous à corriger les parties du site obsolètes ou incomplètes. Traduisez les pages dans d'autres langues. @@ -33,7 +33,7 @@ de recherches, un superviseur de site eep... ça n'est pas si difficile pour la la page applications.
          • Programmation — Il y a beaucoup à faire si vous connaissez Java ou si vous êtes prêts à vous y mettre. -Vérifiez les tickets ouverts sur Trac +Vérifiez les tickets ouverts sur Trac ou la liste de zzz.i2p pour avoir des idées sur un point de départ. Voyez le Guide du nouveau développeur.
          • Traduction — diff --git a/www.i2p2/pages/translations/getinvolved_ru.html b/www.i2p2/pages/translations/getinvolved_ru.html index 7175442d..fa5708c3 100644 --- a/www.i2p2/pages/translations/getinvolved_ru.html +++ b/www.i2p2/pages/translations/getinvolved_ru.html @@ -14,7 +14,7 @@
            • Расскажите о нас! — Расскажите знакомым про I2P, дайте ссылку на проект в форумном обсуждении или в комментариях к статье, прорекламируйте в своём блоге. Создайте/обновите статью об I2P в Википедии на Вашем языке.
              • -
            • Тестирование — Обновляйтесь до текущего билда из monotone-репозитория и сообщайте обо всех обнаруженных ошибках на канале #i2p или в багтрекере.
              • +
            • Тестирование — Обновляйтесь до текущего билда из monotone-репозитория и сообщайте обо всех обнаруженных ошибках на канале #i2p или в багтрекере.
            • Документация — Исправьте устаревший текст, дополните незавершенные инструкции, добавьте перевод на свой язык.
              • @@ -26,7 +26,7 @@
            • Приложения — Создавайте новые I2P-программы или переделайте уже существующие под работу через I2P-сеть. Несколько методических рекомендаций и список нереализованных задумок можно посмотреть на странице Application Development Guide.
              • -
            • Разработка — Если Вы Java-программист, то перед Вами широкий фронт работ. Для начала проверьте багтрекер на наличие открытых тикетов или загляните в TODO-список на форуме zzz.i2p. Подробнее смотрите на странице New Developer's Guide
              • +
            • Разработка — Если Вы Java-программист, то перед Вами широкий фронт работ. Для начала проверьте багтрекер на наличие открытых тикетов или загляните в TODO-список на форуме zzz.i2p. Подробнее смотрите на странице New Developer's Guide
            • Поиск уязвимостей — Проанализируйте или протестируйте код на слабые места. Требуют внимания как уязвимости, касающиеся анонимности (см. описание на странице I2P's Threat Model), так и DoS-уязвимости, и прочие потенциальные угрозы.
              • diff --git a/www.i2p2/pages/translations/halloffame_de.html b/www.i2p2/pages/translations/halloffame_de.html index a3a1e03f..5db69595 100644 --- a/www.i2p2/pages/translations/halloffame_de.html +++ b/www.i2p2/pages/translations/halloffame_de.html @@ -1,15 +1,15 @@ {% extends "_layout_de.html" %} {% block title %}Ruhmeshalle{% endblock %} {% block content %} - +

              I2P's Ruhmeshalle

              -Derzeitiger Stand zum 01.05.2013:
              -Generelles Konto: 28078,57 € und 626,04640057 BTC
              +Derzeitiger Stand zum 25.08.2013:
              +Generelles Konto: 28829,12 € und 607,49839100 BTC
              Datencontainer Belohnung: 145.0 € und 2 BTC
              native IPv6-I2P : 100.0 € und 50 BTC
              I2PHex Code Belohnung: 100.0 €
              -I2P in Debian Spiegelserver: 123.0 €
              -Bitcoin Client für I2P: 50,34 BTC
              +I2P in Debian Spiegelserver: 148.0 €
              +Bitcoin Client für I2P: 10 € und 50,34 BTC
              Unit Tests für den I2P Router: 2305 €
              Bounty Robert: 20
              Bounty Syndie: 18 BTC
              @@ -119,7 +119,41 @@ hinzufügen können. May, 2013anonymous50 €Generelles Konto May, 2013anonymous0.3 BTCGenerelles Konto May, 2013anonymous10 €Belohnung CCR Microtic Board + + May, 2013anonymous20 €Generelles Konto + May, 2013anonymous30 €Generelles Konto + May, 2013anonymous3.50 €Generelles Konto + May, 2013anonymous0.0008 BTCGenerelles Konto + May, 2013anonymous0.0991 BTCGenerelles Konto + + June, 2013anonymous10 €Generelles Konto + June, 2013anonymous20 €Generelles Konto + June, 2013anonymous30 €Generelles Konto + June, 2013DHT Belohnung325 €DHT Belohnung + June, 2013anonymous1 €Generelles Konto + June, 2013anonymous0.0000067 BTCGenerelles Konto + June, 2013anonymous0.01 BTCGenerelles Konto + June, 2013anonymous0.031 BTCGenerelles Konto + June, 2013anonymous0.25 BTCGenerelles Konto + July, 2013first-leon1 €Generelles Konto + July, 2013anonymous5 €Generelles Konto + July, 2013anonymous2 €Generelles Konto + July, 2013anonymous20 €Generelles Konto + July, 2013anonymous0.05 €Generelles Konto + July, 2013anonymous30 €Generelles Konto + July, 2013JULLIAN David15 €Generelles Konto + July, 2013anonymous0.00567899 BTCGenerelles Konto + July, 2013anonymous0.00942744 BTCGenerelles Konto + July, 2013anonymous0.01807730 BTCGenerelles Konto + July, 2013fraud loss9 BTCGenerelles Konto + + Aug, 2013anonymous18 €Generelles Konto + Aug, 2013anonymous30 €Generelles Konto + Aug, 2013Verkauf von BTC820 €10 BTCGenerelles Konto + Aug, 2013anonymous20 €Generelles Konto + Aug, 2013anonymous25 €Bounty DEB Paket + Aug, 2013anonymous0.0279 BTCGenerelles Konto

              diff --git a/www.i2p2/pages/translations/how_de.html b/www.i2p2/pages/translations/how_de.html index ad53535d..de24fa4d 100644 --- a/www.i2p2/pages/translations/how_de.html +++ b/www.i2p2/pages/translations/how_de.html @@ -15,7 +15,7 @@ Die Schnittstelle zwischen Anwendungen und dem Router trägt den Namen I2CP

              Das I2P-Projekt ist um eine vollständige und aktuelle Dokumentation bemüht. Wer in einer der unten verlinkten Seiten Ungenauigkeiten oder Unstimmigkeiten findet, -möge diese bitte hier melden.

              +möge diese bitte hier melden.

              Inhaltsverzeichnis

              diff --git a/www.i2p2/pages/translations/how_el.html b/www.i2p2/pages/translations/how_el.html index 804c0cce..91f120ca 100644 --- a/www.i2p2/pages/translations/how_el.html +++ b/www.i2p2/pages/translations/how_el.html @@ -14,7 +14,7 @@ The interface between applications and the router is the I2CP (I2P Control Proto

              The I2P Project is committed to maintaining accurate, current documentation. If you find any inaccuracies in the documents linked below, please -enter a ticket identifying the problem. +enter a ticket identifying the problem.

              Index to Technical Documentation

              @@ -209,9 +209,9 @@ Note: always verify that javadocs are current by checking the release number.
            • Developer forum inside I2P
            • -Bug tracker +Bug tracker
            • -Viewmtn inside I2P. +Viewmtn inside I2P.
            • I2P Source exported to GitHub
            • @@ -219,7 +219,7 @@ Note: always verify that javadocs are current by checking the release number.
            • Source translation at Transifex
            • -0.9 roadmap wiki (not current) +0.9 roadmap wiki (not current)
            • Old roadmap (not current)
            • diff --git a/www.i2p2/pages/translations/how_fr.html b/www.i2p2/pages/translations/how_fr.html index 44c7562b..2359e0f5 100644 --- a/www.i2p2/pages/translations/how_fr.html +++ b/www.i2p2/pages/translations/how_fr.html @@ -14,7 +14,7 @@ L'interface entre les applications et le routeur est l'API I2CP (I2P Control Pro

              Le projet I2P s'engage à maintenir exacte la documentation actuelle. Si vous trouvez des erreur dans les documents liés ci-dessous, merci d'en faire part via un -ticket Trac.

              +ticket Trac.

              Table

              diff --git a/www.i2p2/pages/translations/how_networkcomparisons_fr.html b/www.i2p2/pages/translations/how_networkcomparisons_fr.html index 69d52fc0..9cfbc786 100644 --- a/www.i2p2/pages/translations/how_networkcomparisons_fr.html +++ b/www.i2p2/pages/translations/how_networkcomparisons_fr.html @@ -22,7 +22,7 @@ très peu de systèmes supportent longtemps la comparaison. Ils sont exposés ic

              Le contenu de cette page est susceptible de mises à jour, de discutions et de débats, et nous accueillons les commentaires et les compléments. Vous pouvez contribuer à l'analyse en soumettant un ticket sur -trac.i2p2.de. +trac.i2p2.de.

              Tor / Onion Routing

              diff --git a/www.i2p2/pages/translations/index_ar.html b/www.i2p2/pages/translations/index_ar.html index b80ec012..785432cf 100644 --- a/www.i2p2/pages/translations/index_ar.html +++ b/www.i2p2/pages/translations/index_ar.html @@ -4,7 +4,7 @@
              الإصدار الأحدث
              -2013-05-28 - I2P 0.9.6 - {{ urlify("release-0.9.6", "Announcement", "html")}} +2013-12-07 - I2P 0.9.9 - {{ urlify("release-0.9.9", "Announcement", "html")}} - تحميل
              2013-02-03 - Syndie 1.103b - @@ -12,10 +12,10 @@
              أحدث الأخبار :
              -2013-05-28 - I2P 0.9.6 تمّ اطلاق النسخة
              -2013-03-08 - I2P 0.9.5 تمّ اطلاق النسخة
              -2012-12-17 - I2P 0.9.4 تمّ اطلاق النسخة
              -2012-10-27 - I2P 0.9.3 تمّ اطلاق النسخة
              +2013-12-07 - I2P 0.9.9 تمّ اطلاق النسخة
              +2013-10-02 - I2P 0.9.8.1 تمّ اطلاق النسخة
              +2013-09-30 - I2P 0.9.8 تمّ اطلاق النسخة
              +2013-08-10 - I2P 0.9.7.1 تمّ اطلاق النسخة
              @@ -12,10 +12,10 @@
              Τελευταία Νέα:
              -2013-05-28 - I2P 0.9.6 Εκδόθηκε
              -2013-03-08 - I2P 0.9.5 Εκδόθηκε
              -2012-12-17 - I2P 0.9.4 Εκδόθηκε
              -2012-10-27 - I2P 0.9.3 Εκδόθηκε
              +2013-12-07 - I2P 0.9.9 Εκδόθηκε
              +2013-10-02 - I2P 0.9.8.1 Εκδόθηκε
              +2013-09-30 - I2P 0.9.8 Εκδόθηκε
              +2013-08-10 - I2P 0.9.7.1 Εκδόθηκε
              @@ -12,10 +12,10 @@
              Dernières nouvelles :
              -2013-05-28 - I2P 0.9.6 Publiée
              -2013-03-08 - I2P 0.9.5 Publiée
              -2012-12-17 - I2P 0.9.4 Publiée
              -2012-10-27 - I2P 0.9.3 Publiée
              +2013-12-07 - I2P 0.9.9 Publiée
              +2013-10-02 - I2P 0.9.8.1 Publiée
              +2013-09-30 - I2P 0.9.8 Publiée
              +2013-08-10 - I2P 0.9.7.1 Publiée
              @@ -12,10 +12,10 @@
              Latest News:
              -2013-05-28 - I2P 0.9.6 Rilasciata
              -2013-03-08 - I2P 0.9.5 Rilasciata
              -2012-12-17 - I2P 0.9.4 Rilasciata
              -2012-10-27 - I2P 0.9.3 Rilasciata
              +2013-12-07 - I2P 0.9.9 Rilasciata
              +2013-10-02 - I2P 0.9.8.1 Rilasciata
              +2013-09-30 - I2P 0.9.8 Rilasciata
              +2013-08-10 - I2P 0.9.7.1 Rilasciata
              @@ -12,10 +12,10 @@
              Laatste Nieuws:
              -2013-05-28 - I2P 0.9.6 Release
              -2013-03-08 - I2P 0.9.5 Release
              -2012-12-17 - I2P 0.9.4 Release
              -2012-10-27 - I2P 0.9.3 Release
              +2013-12-07 - I2P 0.9.9 Release
              +2013-10-02 - I2P 0.9.8.1 Release
              +2013-09-30 - I2P 0.9.8 Release
              +2013-08-10 - I2P 0.9.7.1 Release
              - Скачать @@ -14,10 +14,10 @@
              Последние Новости:
              -2013-05-28 - I2P 0.9.6 Released
              -2013-03-08 - I2P 0.9.5 Released
              -2012-12-17 - I2P 0.9.4 Released
              -2012-10-27 - I2P 0.9.3 Released
              +2013-12-07 - I2P 0.9.9 Released
              +2013-10-02 - I2P 0.9.8.1 Released
              +2013-09-30 - I2P 0.9.8 Released
              +2013-08-10 - I2P 0.9.7.1 Released
              diff --git a/www.i2p2/pages/translations/index_zh.html b/www.i2p2/pages/translations/index_zh.html index d8f9af04..f6ba4f8e 100644 --- a/www.i2p2/pages/translations/index_zh.html +++ b/www.i2p2/pages/translations/index_zh.html @@ -5,7 +5,7 @@
              最新版本：
              -2013-05-28 - I2P 0.9.6 - {{ urlify("release-0.9.6", "Announcement", "html")}} +2013-12-07 - I2P 0.9.9 - {{ urlify("release-0.9.9", "Announcement", "html")}} - 下载
              2013-02-03 - Syndie 1.103b - @@ -14,10 +14,10 @@
              最新动态：
              -2013-05-28 - I2P 0.9.6 新版发布
              -2013-03-08 - I2P 0.9.5 新版发布
              -2012-12-17 - I2P 0.9.4 新版发布
              -2012-10-27 - I2P 0.9.3 新版发布
              +2013-12-07 - I2P 0.9.9 新版发布
              +2013-10-02 - I2P 0.9.8.1 新版发布
              +2013-09-30 - I2P 0.9.8 新版发布
              +2013-08-10 - I2P 0.9.7.1 新版发布